diff --git a/raw/rel-18/23_series/23222/raw.md b/raw/rel-18/23_series/23222/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..794419c51c1f34325f6945fa7f1612a09ce92726 --- /dev/null +++ b/raw/rel-18/23_series/23222/raw.md @@ -0,0 +1,5278 @@ + + +# 3GPP TS 23.222 V18.3.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2 (Release 18)** --- + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like graphic 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 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 ..... | 10 | +| Introduction ..... | 10 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Abbreviations ..... | 13 | +| 4 Architectural requirements..... | 13 | +| 4.1 General ..... | 13 | +| 4.1.1 Introduction ..... | 13 | +| 4.1.2 Requirements..... | 13 | +| 4.1.3 Requirements for supporting 3 rd party API providers ..... | 14 | +| 4.2 Service API publish and discover ..... | 14 | +| 4.2.1 Introduction ..... | 14 | +| 4.2.2 Requirements..... | 14 | +| 4.2.3 Requirements for 3 rd party API providers ..... | 14 | +| 4.3 Security..... | 14 | +| 4.3.1 Introduction ..... | 14 | +| 4.3.2 Requirements..... | 14 | +| 4.3.3 Additional requirements for 3 rd party API provider ..... | 15 | +| 4.4 Charging..... | 15 | +| 4.4.1 Introduction ..... | 15 | +| 4.4.2 Requirements..... | 15 | +| 4.4.3 Requirements for 3 rd party API providers ..... | 15 | +| 4.5 Operations, Administration and Maintenance..... | 15 | +| 4.5.1 Introduction ..... | 15 | +| 4.5.2 Requirements..... | 16 | +| 4.5.3 Requirements for 3 rd party API providers ..... | 16 | +| 4.6 Service API invocation monitoring..... | 16 | +| 4.6.1 Introduction ..... | 16 | +| 4.6.2 Requirements..... | 16 | +| 4.7 Logging ..... | 16 | +| 4.7.1 Introduction ..... | 16 | +| 4.7.2 Logging events related to service API invocations ..... | 17 | +| 4.7.3 Logging events related to API invoker onboarding..... | 17 | +| 4.7.4 Logging events related to API invoker interaction with the CAPIF ..... | 17 | +| 4.8 Auditing service API invocation..... | 17 | +| 4.8.1 Introduction ..... | 17 | +| 4.8.2 Requirements..... | 17 | +| 4.9 Onboarding API invoker ..... | 17 | +| 4.9.1 Introduction ..... | 17 | +| 4.9.2 Requirements..... | 17 | +| 4.10 Policy configuration ..... | 18 | +| 4.10.1 Introduction ..... | 18 | +| 4.10.2 Requirements..... | 18 | +| 4.11 Protocol design..... | 18 | +| 4.11.1 Introduction ..... | 18 | +| 4.11.2 Requirements..... | 18 | +| 4.12 Interconnection between the CAPIF providers ..... | 18 | +| 4.12.1 Introduction ..... | 18 | +| 4.12.2 Requirements..... | 19 | +| 4.13 Identities..... | 19 | +| 4.13.1 Introduction ..... | 19 | +| 4.13.2 Requirements..... | 19 | + +| | | | +|--------|--------------------------------------------------------------------------------------------------|----| +| 4.14 | API provider domain interactions ..... | 19 | +| 4.14.1 | Introduction ..... | 19 | +| 4.14.2 | Requirements ..... | 19 | +| 4.15 | Dynamic routing of service API invocation..... | 19 | +| 4.15.1 | Introduction ..... | 19 | +| 4.15.2 | Requirements ..... | 19 | +| 4.16 | Registering API provider domain functions..... | 19 | +| 4.16.1 | Introduction ..... | 19 | +| 4.16.2 | Requirements ..... | 19 | +| 4.17 | Resource owner-aware northbound API invocation ..... | 20 | +| 4.17.1 | Introduction ..... | 20 | +| 4.17.2 | Requirements ..... | 20 | +| 5 | Involved business relationships ..... | 20 | +| 5.1 | Basic CAPIF business relationships..... | 20 | +| 5.2 | CAPIF business relationships for RNAA..... | 21 | +| 6 | Functional model..... | 21 | +| 6.1 | General ..... | 21 | +| 6.2 | Functional model description..... | 22 | +| 6.2.0 | Functional model description for the CAPIF ..... | 22 | +| 6.2.1 | Functional model description to support 3 rd party API providers ..... | 24 | +| 6.2.2 | Functional model description to support CAPIF interconnection..... | 25 | +| 6.2.3 | Functional model description to support RNAA..... | 27 | +| 6.3 | Functional entities description ..... | 28 | +| 6.3.1 | General ..... | 28 | +| 6.3.2 | API invoker ..... | 28 | +| 6.3.3 | CAPIF core function..... | 28 | +| 6.3.4 | API exposing function ..... | 29 | +| 6.3.5 | API publishing function ..... | 29 | +| 6.3.6 | API management function..... | 29 | +| 6.3.7 | Authorization function..... | 29 | +| 6.3.8 | Resource owner client ..... | 30 | +| 6.4 | Reference points..... | 30 | +| 6.4.1 | General ..... | 30 | +| 6.4.2 | Reference point CAPIF-1 (between the API invoker and the CAPIF core function) ..... | 30 | +| 6.4.3 | Reference point CAPIF-1e (between the API invoker and the CAPIF core function)..... | 30 | +| 6.4.4 | Reference point CAPIF-2 (between the API invoker and the API exposing function)..... | 30 | +| 6.4.5 | Reference point CAPIF-2e (between the API invoker and the API exposing function)..... | 31 | +| 6.4.6 | Reference point CAPIF-3 (between the API exposing function and the CAPIF core function)..... | 31 | +| 6.4.7 | Reference point CAPIF-4 (between the API publishing function and the CAPIF core function) ..... | 31 | +| 6.4.8 | Reference point CAPIF-5 (between the API management function and the CAPIF core function)..... | 31 | +| 6.4.9 | Reference point CAPIF-3e (between the API exposing function and the CAPIF core function) ..... | 32 | +| 6.4.10 | Reference point CAPIF-4e (between the API publishing function and the CAPIF core function)..... | 32 | +| 6.4.11 | Reference point CAPIF-5e (between the API management function and the CAPIF core function) ..... | 32 | +| 6.4.12 | Reference point CAPIF-7 (between the API exposing functions) ..... | 32 | +| 6.4.13 | Reference point CAPIF-7e (between the API exposing functions)..... | 33 | +| 6.4.14 | Reference point CAPIF-6 (between the CAPIF core functions of the same CAPIF provider)..... | 33 | +| 6.4.15 | Reference point CAPIF-6e (between the CAPIF core functions of different CAPIF providers) ..... | 33 | +| 6.4.16 | Reference point CAPIF-8 (between the CAPIF core function and the resource owner client)..... | 33 | +| 6.5 | Service-based interfaces..... | 33 | +| 7 | Application of functional model to deployments..... | 34 | +| 7.1 | General ..... | 34 | +| 7.2 | Centralized deployment..... | 34 | +| 7.3 | Distributed deployment..... | 34 | +| 7.4 | Multiple CCFs deployment..... | 38 | +| 7.5 | RNAA deployments ..... | 38 | +| 8 | Procedures and information flows ..... | 39 | +| 8.1 | Onboarding the API invoker to the CAPIF ..... | 39 | +| 8.1.1 | General ..... | 39 | +| 8.1.2 | Information flows ..... | 39 | + +| | | | +|---------|---------------------------------------------------------------------------|----| +| 8.1.2.1 | Onboard API invoker request ..... | 39 | +| 8.1.2.2 | Onboard API invoker response..... | 39 | +| 8.1.3 | Procedure ..... | 40 | +| 8.2 | Offboarding the API invoker from the CAPIF..... | 41 | +| 8.2.1 | General ..... | 41 | +| 8.2.2 | Information flows ..... | 41 | +| 8.2.2.1 | Offboard API invoker request..... | 41 | +| 8.2.2.2 | Offboard API invoker response ..... | 41 | +| 8.2.3 | Procedure ..... | 41 | +| 8.3 | Publish service APIs..... | 42 | +| 8.3.1 | General ..... | 42 | +| 8.3.2 | Information flows ..... | 42 | +| 8.3.2.1 | Service API publish request..... | 42 | +| 8.3.2.2 | Service API publish response ..... | 43 | +| 8.3.3 | Procedure ..... | 44 | +| 8.4 | Unpublish service APIs..... | 44 | +| 8.4.1 | General ..... | 44 | +| 8.4.2 | Information flows ..... | 44 | +| 8.4.2.1 | Service API unpublish request..... | 44 | +| 8.4.2.2 | Service API unpublish response ..... | 45 | +| 8.4.3 | Procedure ..... | 45 | +| 8.5 | Retrieve service APIs..... | 46 | +| 8.5.1 | General ..... | 46 | +| 8.5.2 | Information flows ..... | 46 | +| 8.5.2.1 | Service API get request..... | 46 | +| 8.5.2.2 | Service API get response ..... | 46 | +| 8.5.3 | Procedure ..... | 46 | +| 8.6 | Update service APIs..... | 47 | +| 8.6.1 | General ..... | 47 | +| 8.6.2 | Information flows ..... | 47 | +| 8.6.2.1 | Service API update request..... | 47 | +| 8.6.2.2 | Service API update response ..... | 48 | +| 8.6.3 | Procedure ..... | 48 | +| 8.7 | Discover service APIs ..... | 49 | +| 8.7.1 | General ..... | 49 | +| 8.7.2 | Information flows ..... | 49 | +| 8.7.2.1 | Service API discover request..... | 49 | +| 8.7.2.2 | Service API discover response ..... | 49 | +| 8.7.3 | Procedure ..... | 50 | +| 8.8 | Subscription, unsubscription and notifications for the CAPIF events ..... | 51 | +| 8.8.1 | General ..... | 51 | +| 8.8.2 | Information flows ..... | 51 | +| 8.8.2.1 | Event subscription request..... | 51 | +| 8.8.2.2 | Event subscription response..... | 51 | +| 8.8.2.3 | Event notification..... | 52 | +| 8.8.2.4 | Event notification acknowledgement..... | 52 | +| 8.8.2.5 | Event unsubscription request..... | 52 | +| 8.8.2.6 | Event unsubscription response..... | 52 | +| 8.8.2.7 | Event subscription update request ..... | 53 | +| 8.8.2.8 | Event subscription update response..... | 53 | +| 8.8.3 | Procedure for CAPIF event subscription..... | 53 | +| 8.8.4 | Procedure for CAPIF event notifications ..... | 54 | +| 8.8.5 | Procedure for CAPIF event unsubscription..... | 55 | +| 8.8.5a | Procedure for CAPIF event subscription update ..... | 55 | +| 8.8.6 | List of CAPIF events ..... | 56 | +| 8.9 | Revoking subscription of the CAPIF events ..... | 56 | +| 8.9.1 | General ..... | 56 | +| 8.9.2 | Information flows ..... | 57 | +| 8.9.2.1 | Subscription revoke notification..... | 57 | +| 8.9.2.2 | Subscription revoke notification acknowledgement..... | 57 | +| 8.9.3 | Procedure ..... | 57 | +| 8.10 | Authentication between the API invoker and the CAPIF core function..... | 58 | + +| | | | +|----------|------------------------------------------------------------------------------------------|----| +| 8.10.1 | General ..... | 58 | +| 8.10.2 | Information flows ..... | 58 | +| 8.10.3 | Procedure ..... | 58 | +| 8.11 | API invoker obtaining authorization to access service API ..... | 59 | +| 8.11.1 | General ..... | 59 | +| 8.11.2 | Information flows ..... | 59 | +| 8.11.3 | Procedure ..... | 59 | +| 8.12 | AEF obtaining service API access control policy ..... | 59 | +| 8.12.1 | General ..... | 59 | +| 8.12.2 | Information flows ..... | 60 | +| 8.12.2.1 | Obtain access control policy request ..... | 60 | +| 8.12.2.2 | Obtain access control policy response ..... | 60 | +| 8.12.3 | Procedure ..... | 60 | +| 8.13 | Topology hiding ..... | 61 | +| 8.13.1 | General ..... | 61 | +| 8.13.2 | Information flows ..... | 61 | +| 8.13.2.1 | Service API invocation request (API invoker – AEF-1) ..... | 61 | +| 8.13.2.2 | Service API invocation request (AEF-1 – AEF-2) ..... | 61 | +| 8.13.2.3 | Service API invocation response (AEF-2 – AEF-1) ..... | 61 | +| 8.13.2.4 | Service API invocation response (AEF-1 – API invoker) ..... | 62 | +| 8.13.3 | Procedure ..... | 62 | +| 8.14 | Authentication between the API invoker and the AEF prior to service API invocation ..... | 63 | +| 8.14.1 | General ..... | 63 | +| 8.14.2 | Information flows ..... | 63 | +| 8.14.3 | Procedure ..... | 63 | +| 8.15 | Authentication between the API invoker and the AEF upon the service API invocation ..... | 64 | +| 8.15.1 | General ..... | 64 | +| 8.15.2 | Information flows ..... | 64 | +| 8.15.2.1 | Service API invocation request with authentication information ..... | 64 | +| 8.15.2.2 | Service API invocation response ..... | 64 | +| 8.15.3 | Procedure ..... | 64 | +| 8.16 | Service API invocation with AEF authorization ..... | 65 | +| 8.16.1 | General ..... | 65 | +| 8.16.2 | Information flows ..... | 65 | +| 8.16.2.1 | Service API invocation request ..... | 65 | +| 8.16.2.2 | Service API invocation response ..... | 66 | +| 8.16.3 | Procedure ..... | 66 | +| 8.17 | CAPIF access control ..... | 67 | +| 8.17.1 | General ..... | 67 | +| 8.17.2 | Information flows ..... | 68 | +| 8.17.2.1 | Service API invocation request ..... | 68 | +| 8.17.2.2 | Service API invocation response ..... | 68 | +| 8.17.3 | Procedure ..... | 68 | +| 8.18 | CAPIF access control with cascaded AEFs ..... | 69 | +| 8.18.1 | General ..... | 69 | +| 8.18.2 | Information flows ..... | 69 | +| 8.18.2.1 | Service API invocation request ..... | 69 | +| 8.18.2.2 | Service API invocation response ..... | 69 | +| 8.18.3 | Procedure ..... | 70 | +| 8.19 | Logging service API invocations ..... | 70 | +| 8.19.1 | General ..... | 70 | +| 8.19.2 | Information flows ..... | 71 | +| 8.19.2.1 | API invocation log request ..... | 71 | +| 8.19.2.2 | API invocation log response ..... | 71 | +| 8.19.3 | Procedure ..... | 71 | +| 8.20 | Charging the invocation of service APIs ..... | 72 | +| 8.20.1 | General ..... | 72 | +| 8.20.2 | Information flows ..... | 72 | +| 8.20.3 | Procedure ..... | 72 | +| 8.21 | Monitoring service API invocation ..... | 73 | +| 8.21.1 | General ..... | 73 | +| 8.21.2 | Information flows ..... | 73 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------|----| +| 8.21.2.1 | Monitoring service API event notification ..... | 73 | +| 8.21.2.2 | Monitoring service API event notification acknowledgement ..... | 73 | +| 8.21.3 | Procedure ..... | 73 | +| 8.22 | Auditing service API invocation ..... | 74 | +| 8.22.1 | General ..... | 74 | +| 8.22.2 | Information flows ..... | 74 | +| 8.22.2.1 | Query service API log request ..... | 74 | +| 8.22.2.2 | Query service API log response ..... | 74 | +| 8.22.3 | Procedure ..... | 74 | +| 8.23 | CAPIF revoking API invoker authorization ..... | 75 | +| 8.23.1 | General ..... | 75 | +| 8.23.2 | Information flows ..... | 75 | +| 8.23.2.1 | Revoke API invoker authorization request ..... | 75 | +| 8.23.2.2 | Revoke API invoker authorization response ..... | 76 | +| 8.23.2.3 | Revoke API invoker authorization notify ..... | 76 | +| 8.23.3 | Procedure for CAPIF revoking API invoker authorization initiated by AEF ..... | 76 | +| 8.23.4 | Procedure for CAPIF revoking API invoker authorization initiated by CAPIF core function ..... | 77 | +| 8.24 | API topology hiding management ..... | 78 | +| 8.24.1 | General ..... | 78 | +| 8.24.2 | Information flows ..... | 78 | +| 8.24.2.1 | API topology hiding notify ..... | 78 | +| 8.24.3 | Procedure ..... | 79 | +| 8.25 | Support for CAPIF interconnection ..... | 80 | +| 8.25.1 | General ..... | 80 | +| 8.25.2 | Information flows ..... | 80 | +| 8.25.2.1 | Interconnection API publish request ..... | 80 | +| 8.25.2.2 | Interconnection API publish response ..... | 80 | +| 8.25.2.3 | Interconnection service API discover request ..... | 80 | +| 8.25.2.4 | Interconnection service API discover response ..... | 81 | +| 8.25.3 | Procedure ..... | 81 | +| 8.25.3.1 | Service API publish for CAPIF interconnection ..... | 81 | +| 8.25.3.2 | Service API discovery involving multiple CCFs ..... | 82 | +| 8.25.3.3 | Service API discovery for CAPIF interconnection ..... | 83 | +| 8.26 | Update API invoker's API list ..... | 84 | +| 8.26.1 | General ..... | 84 | +| 8.26.2 | Information flows ..... | 84 | +| 8.26.2.1 | Update API invoker API list request ..... | 84 | +| 8.26.2.2 | Update API invoker API list response ..... | 85 | +| 8.26.3 | Procedure ..... | 85 | +| 8.27 | Dynamically routing service API invocation ..... | 86 | +| 8.27.1 | General ..... | 86 | +| 8.27.2 | Information flows ..... | 86 | +| 8.27.2.1 | Obtain routing information request ..... | 86 | +| 8.27.2.2 | Obtain routing information response ..... | 86 | +| 8.27.3 | Procedure ..... | 86 | +| 8.28 | Registering the API provider domain functions on the CAPIF ..... | 87 | +| 8.28.1 | General ..... | 87 | +| 8.28.2 | Information flows ..... | 87 | +| 8.28.2.1 | Registration request ..... | 87 | +| 8.28.2.2 | Registration response ..... | 88 | +| 8.28.3 | Procedure ..... | 88 | +| 8.29 | Update registration information of the API provider domain functions on the CAPIF ..... | 89 | +| 8.29.1 | General ..... | 89 | +| 8.29.2 | Information flows ..... | 89 | +| 8.29.2.1 | Registration update request ..... | 89 | +| 8.29.2.2 | Registration update response ..... | 89 | +| 8.29.3 | Procedure ..... | 90 | +| 8.30 | Deregistering the API provider domain functions on the CAPIF ..... | 91 | +| 8.30.1 | General ..... | 91 | +| 8.30.2 | Information flows ..... | 91 | +| 8.30.2.1 | Deregistration request ..... | 91 | +| 8.30.2.2 | Deregistration response ..... | 91 | + +| | | | +|--------|-----------------------------------------------------------------------------|-----| +| 8.30.3 | Procedure ..... | 91 | +| 8.31 | API invoker obtaining authorization from resource owner ..... | 92 | +| 8.31.1 | General ..... | 92 | +| 8.31.2 | Information flows ..... | 92 | +| 8.31.3 | Procedure ..... | 92 | +| 8.32 | Reducing authorization information inquiry in a nested API invocation ..... | 93 | +| 8.32.1 | General ..... | 93 | +| 8.32.2 | Information flows ..... | 93 | +| 8.32.3 | Procedure ..... | 93 | +| 9 | API consistency guidelines ..... | 94 | +| 9.1 | General ..... | 94 | +| 9.2 | Fundamental API Guidelines ..... | 95 | +| 9.3 | Architecture design considerations ..... | 95 | +| 10 | CAPIF core function APIs ..... | 96 | +| 10.1 | General ..... | 96 | +| 10.2 | CAPIF_Discover_Service_API API ..... | 98 | +| 10.2.1 | General ..... | 98 | +| 10.2.2 | Discover_Service_API operation ..... | 98 | +| 10.2.3 | Subscribe_Event operation ..... | 98 | +| 10.2.4 | Notify_Event operation ..... | 98 | +| 10.2.5 | Unsubscribe_Event operation ..... | 98 | +| 10.2.6 | Update_Event_Subscription operation ..... | 99 | +| 10.3 | CAPIF_Publish_Service_API API ..... | 99 | +| 10.3.1 | General ..... | 99 | +| 10.3.2 | Publish_Service_API operation ..... | 99 | +| 10.3.3 | Unpublish_Service_API operation ..... | 99 | +| 10.3.4 | Update_Service_API operation ..... | 99 | +| 10.3.5 | Get_Service_API operation ..... | 100 | +| 10.3.6 | Subscribe_Event operation ..... | 100 | +| 10.3.7 | Notify_Event operation ..... | 100 | +| 10.3.8 | Unsubscribe_Event operation ..... | 100 | +| 10.3.9 | Update_Event_Subscription operation ..... | 101 | +| 10.4 | CAPIF_Events API ..... | 101 | +| 10.4.1 | General ..... | 101 | +| 10.4.2 | Subscribe_Event operation ..... | 101 | +| 10.4.3 | Notify_Event operation ..... | 102 | +| 10.4.4 | Unsubscribe_Event operation ..... | 102 | +| 10.4.5 | Update_Event_Subscription operation ..... | 102 | +| 10.5 | CAPIF_API_invoker_management API ..... | 102 | +| 10.5.1 | General ..... | 102 | +| 10.5.2 | Onboard_API_Invoker operation ..... | 102 | +| 10.5.3 | Offboard_API_Invoker operation ..... | 103 | +| 10.5.4 | Subscribe_Event operation ..... | 103 | +| 10.5.5 | Notify_Event operation ..... | 103 | +| 10.5.6 | Unsubscribe_Event operation ..... | 103 | +| 10.5.7 | Update_Event_Subscription operation ..... | 104 | +| 10.6 | CAPIF_Security API ..... | 104 | +| 10.6.1 | General ..... | 104 | +| 10.6.2 | Obtain_Security_Method operation ..... | 104 | +| 10.6.3 | Obtain_Authorization operation ..... | 104 | +| 10.6.4 | Obtain_API_Invoker_Info operation ..... | 104 | +| 10.6.5 | Revoke_Authorization operation ..... | 105 | +| 10.7 | CAPIF_Monitoring API ..... | 105 | +| 10.7.1 | General ..... | 105 | +| 10.7.2 | Subscribe_Event operation ..... | 105 | +| 10.7.3 | Notify_Monitoring_Service_Event operation ..... | 105 | +| 10.7.4 | Unsubscribe_Event operation ..... | 105 | +| 10.7.5 | Update_Event_Subscription operation ..... | 106 | +| 10.8 | CAPIF_Logging_API_Invocation API ..... | 106 | +| 10.8.1 | General ..... | 106 | + +| | | | +|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------| +| 10.8.2 | Log_API_Invocation operation ..... | 106 | +| 10.9 | CAPIF_Auditing API..... | 106 | +| 10.9.1 | General ..... | 106 | +| 10.9.2 | Query_API_Invocation_Log operation ..... | 106 | +| 10.10 | CAPIF_Access_Control_Policy API ..... | 107 | +| 10.10.1 | General ..... | 107 | +| 10.10.2 | Obtain_Access_Control_Policy operation ..... | 107 | +| 10.11 | CAPIF_Routing_Info API..... | 107 | +| 10.11.1 | General ..... | 107 | +| 10.11.2 | Obtain_Routing_Info operation..... | 107 | +| 10.12 | CAPIF_API_provider_management API..... | 107 | +| 10.12.1 | General ..... | 107 | +| 10.12.2 | Register_API_Provider operation ..... | 107 | +| 10.12.3 | Update_API_Provider operation ..... | 108 | +| 10.12.4 | Deregister_API_Provider operation ..... | 108 | +| 11 | API exposing function APIs ..... | 108 | +| 11.1 | General ..... | 108 | +| 11.2 | AEF_Security API..... | 108 | +| 11.2.1 | General ..... | 108 | +| 11.2.2 | Revoke_Authorization operation..... | 109 | +| 11.2.3 | Initiate_Authentication operation..... | 109 | +| Annex A (informative): Overview of CAPIF operations ..... | | 110 | +| Annex B (informative): CAPIF relationship with network exposure aspects of 3GPP systems..... | | 112 | +| B.0 | CAPIF utilization by service API provider..... | 112 | +| B.1 | CAPIF relationship with 3GPP EPS network exposure..... | 113 | +| B.1.1 | General ..... | 113 | +| B.1.2 | Deployment models..... | 113 | +| B.1.2.1 | General ..... | 113 | +| B.1.2.2 | SCEF implements the CAPIF architecture..... | 113 | +| B.1.2.3 | SCEF implements the service specific aspect compliant with the CAPIF architecture ..... | 114 | +| B.1.2.4 | Distributed deployment of the SCEF compliant with the CAPIF architecture ..... | 115 | +| B.2 | CAPIF relationship with 3GPP 5GS network exposure ..... | 116 | +| B.2.1 | General ..... | 116 | +| B.2.2 | Deployment models..... | 117 | +| B.2.2.1 | General ..... | 117 | +| B.2.2.2 | NEF implements the CAPIF architecture..... | 117 | +| B.2.2.3 | NEF implements the service specific aspect compliant with the CAPIF architecture ..... | 118 | +| B.2.2.4 | Distributed deployment of the NEF compliant with the CAPIF architecture ..... | 119 | +| B.3 | Integrated deployment of 3GPP network exposure systems with the CAPIF ..... | 120 | +| B.3.1 | General ..... | 120 | +| B.3.2 | Deployment model ..... | 121 | +| B.3.2.1 | General ..... | 121 | +| B.3.2.2 | Integrated deployment of the SCEF and the NEF with the CAPIF..... | 121 | +| Annex C (informative): CAPIF role in charging..... | | 122 | +| C.1 | General..... | 122 | +| C.2 | CAPIF role in online charging..... | 123 | +| C.3 | CAPIF role in offline charging ..... | 123 | +| Annex D (informative): CAPIF relationship with external API frameworks ..... | | 124 | +| Annex E (normative): Configuration data for CAPIF ..... | | 125 | +| Annex F (informative): Change history ..... | | 126 | + +--- + +## 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 + +In 3GPP, there are multiple northbound API-related specifications (e.g. APIs for Service Capability Exposure Function (SCEF) functionalities defined in 3GPP TS 23.682 [2], API for the interface between MBMS service provider and BM-SC defined in 3GPP TR 26.981 [5]). To avoid duplication and inconsistency of approach between different API specifications, 3GPP has considered the development of a common API framework (CAPIF) that includes common aspects applicable to any northbound service APIs. + +The present document specifies the functional model, procedures and information flows needed to support the CAPIF, and the guidelines for consistent northbound API (service and CAPIF APIs) development in 3GPP. + +NOTE: It is possible to use the CAPIF defined common aspects for other APIs as well, apart from northbound APIs. + +--- + +# 1 Scope + +The present document specifies the architecture, procedures and information flows necessary for the CAPIF. The aspects of this specification include identifying architecture requirements for the CAPIF (e.g. registration, discovery, identity management) that are applicable to any service APIs when used by northbound entities, as well as any interactions between the CAPIF and the service APIs themselves. The common API framework applies to both EPS and 5GS, can be hosted within a PLMN or SNPN, and is independent of the underlying 3GPP access (e.g. E-UTRA, NR). + +--- + +# 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.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [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 TR 26.981: "MBMS Extensions for Provisioning and Content Ingestion". +- [6] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [7] ETSI GS MEC 011 (V1.1.1): "Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement". +- [8] ETSI GS MEC 009 (V1.1.1): "Mobile Edge Computing (MEC); General Principles for Mobile Edge Service APIs". +- [9] OMA-ER\_Autho4API-V1\_0-20141209-A: "Authorization Framework for Network APIs". +- [10] OMA-TS-REST\_NetAPI\_Common-V1\_0-20180116-A: "Common definitions for RESTful Network APIs". +- [11] OMA-TS-NGSI\_Registration\_and\_Discovery-V1\_0-20120529-A: "NGSI Registration and Discovery". +- [12] 3GPP TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs". + +## 3 Definitions 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]. + +**API:** The means by which an API invoker can access the service. + +**API invoker:** The entity which invokes the CAPIF or service APIs. + +**API invoker profile:** The set of information associated to an API invoker that allows that API invoker to utilize CAPIF APIs and service APIs. + +**API exposing function:** The entity which provides the service communication entry point for the service APIs. + +**API exposing function location:** The location information (e.g. civic address, GPS coordinates, data center ID) where the API exposing function providing the service API is located. + +**CAPIF administrator:** An authorized user with special permissions for CAPIF operations. + +**Common API framework:** A framework comprising common API aspects that are required to support service APIs. + +**Designated CAPIF core function:** The CAPIF core function which is configured as the serving CAPIF core function for interconnection. + +**Northbound API:** A service API exposed to higher-layer API invokers. + +**Onboarding:** One time registration process that enables the API invoker to subsequently access the CAPIF and the service APIs. + +**Resource:** The object or component of the API on which the operations are acted upon. + +**Resource owner:** An entity (either a UE user or an MNO subscriber) capable of granting access to a protected resource related to the invoked API. + +**Resource owner-aware northbound API access:** An API invocation scenario where the API invoker needs an authorization from the resource owner. + +**Service API:** The interface through which a component of the system exposes its services to API invokers by abstracting the services from the underlying mechanisms. + +**Serving Area Information:** The location information for which the service APIs are being offered to. + +**CAPIF provider domain:** A domain that contains an instance of CAPIF core function and may contain API provider domains and API invokers. The CAPIF provider could be a PLMN, SNPN or 3rd party. Throughout this document, PLMN trust domain is often used as the typical deployment of a CAPIF provider domain however SNPN trust domain or 3rd party trust domain are applicable as well. + +**PLMN trust domain:** The entities protected by adequate security and controlled by the PLMN operator or a trusted 3rd party of the PLMN. + +**SNPN trust domain:** The entities protected by adequate security and controlled by the SNPN operator or a trusted 3rd party of the SNPN. **3rd party trust domain:** The entities protected by adequate security and controlled by the 3rd party. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.240 [6] apply: + +**Offline charging** +**Online charging** + +## 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]. + +| | | +|--------|--------------------------------------------------| +| 5GS | 5G System | +| AEF | API Exposing Function | +| AF | Application Function | +| AMF | API Management Function | +| APF | API Publishing Function | +| API | Application Program Interface | +| AS | Application Server | +| BM-SC | Broadcast Multicast Service Centre | +| CAPIF | Common API Framework | +| CDR | Charging Data Record | +| CRUD | Create, Read, Update, Delete | +| DDoS | Distributed Denial of Service | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| EPS | Evolved Packet System | +| ETSI | European Telecommunications Standards Institute | +| GS | Group Specification | +| IP | Internet Protocol | +| MBMS | Multimedia Broadcast and Multicast Service | +| MEC | Multi-access Edge Computing | +| NEF | Network Exposure Function | +| NGSI | Next Generation Service Interfaces | +| NR | New Radio | +| OMA | Open Mobile Alliance | +| OAM | Operations, Administration and Maintenance | +| OWSER | OMA Web Services | +| PC | Protocol Converter | +| PLMN | Public Land Mobile Network | +| REST | REpresentational State Transfer | +| RNAA | Resource owner-aware Northbound API Access | +| RPC | Remote Procedure Call | +| SCEF | Service Capability Exposure Function | +| SCS | Service Capability Server | +| SNPN | Stand-alone Non-Public Network | +| UDDI | Universal Description, Discovery and Integration | +| URI | Uniform Resource Identifier | +| WSDL | Web Services Description Language | + +--- + +## 4 Architectural requirements + +### 4.1 General + +#### 4.1.1 Introduction + +This subclause specifies the general requirements for CAPIF architecture. + +#### 4.1.2 Requirements + +[AR-4.1.2-a] The CAPIF shall provide mechanisms (e.g. publish service APIs, authorization, logging, charging) to support service API operations. + +[AR-4.1.2-b] The CAPIF shall enable API invoker(s) to discover and communicate with service APIs from the API providers. + +[AR-4.1.2-c] Reference points between CAPIF and external applications shall be provided as APIs. + +[AR-4.1.2-d] Reference points internal to CAPIF may be provided as APIs. + +### 4.1.3 Requirements for supporting 3rd party API providers + +[AR-4.1.3-a] The CAPIF shall provide mechanisms (e.g. publish service APIs, authorization, logging, charging) to support service API operations from trusted 3rd party API providers. + +[AR-4.1.3-b] The CAPIF shall enable API invoker(s) to discover and communicate with service APIs from trusted 3rd party API providers. + +## 4.2 Service API publish and discover + +### 4.2.1 Introduction + +This subclause specifies the service API publish and discover related requirements. + +### 4.2.2 Requirements + +[AR-4.2.2-a] The CAPIF shall provide a mechanism to publish the service API information to be used by the API invokers to discover and subsequently invoke the service API. + +[AR-4.2.2-b] The CAPIF shall provide a mechanism for the API invokers to discover the published service API information as specified in [AR-4.2.2-a] according to the API invokers' interest. + +[AR-4.2.2-c] The CAPIF shall provide a mechanism to restrict the discovery of the published service API information by the API invokers, based on configured policies. + +[AR-4.2.2-d] The CAPIF shall provide a mechanism to configure policies to restrict the discovery of the published service API information. + +[AR-4.2.2-e] The CAPIF shall provide mechanism to support Serving Area Information related to service APIs. + +### 4.2.3 Requirements for 3rd party API providers + +[AR-4.2.3-a] The CAPIF shall provide a mechanism to publish the service API information of the 3rd party API providers. + +## 4.3 Security + +### 4.3.1 Introduction + +This subclause specifies the security related requirements for API invokers. + +### 4.3.2 Requirements + +[AR-4.3.2-a] The CAPIF shall provide mechanisms to hide the topology of the PLMN trust domain from the API invokers accessing the service APIs from outside the PLMN trust domain. + +[AR-4.3.2-b] The CAPIF shall provide mechanisms to authenticate API invokers prior to accessing the service APIs. + +[AR-4.3.2-c] The CAPIF shall provide mechanisms to authenticate API invokers upon the service API invocation. + +[AR-4.3.2-d] The CAPIF shall provide mechanisms to authorize API invokers to access the service APIs. + +[AR-4.3.2-e] The CAPIF shall provide mechanisms to validate authorization of the API invokers upon the service API invocation. + +[AR-4.3.2-f] The CAPIF shall provide mechanisms for mutual authentication between the CAPIF and the API invoker. + +[AR-4.3.2-g] The CAPIF shall provide mechanisms to control the service API access for every API invocation. + +[AR-4.3.2-h] The communication between the CAPIF and the API invoker shall be confidentiality protected. + +[AR-4.3.2-i] The communication between the CAPIF and the API invoker shall be integrity protected. + +[AR-4.3.2-j] The CAPIF shall provide mechanisms to authenticate the service API publishers to publish and manage the service API information. + +[AR-4.3.2-k] The CAPIF shall provide mechanisms to authorize the service API publishers to publish and manage service API information. + +[AR-4.3.2-l] The CAPIF shall provide mechanisms to validate authorization of the service API publishers to publish and manage service API information. + +### 4.3.3 Additional requirements for 3rd party API provider + +[AR-4.3.3-a] The CAPIF shall provide mechanisms to hide the topology of the 3rd party API provider trust domain from the API invokers accessing the service APIs from outside the 3rd party API provider trust domain. + +[AR-4.3.3-b] The CAPIF shall provide authorization mechanism for service APIs from the 3rd party API providers. + +[AR-4.3.3-c] The CAPIF shall provide data confidentiality (across API providers) for data (e.g. logging, charging) related to service APIs from multiple API providers. + +## 4.4 Charging + +### 4.4.1 Introduction + +This subclause specifies the charging related requirements for the usage of service APIs. + +### 4.4.2 Requirements + +[AR-4.4.2-a] The CAPIF shall support online and offline charging for service APIs usage. + +[AR-4.4.2-b] The CAPIF shall provide mechanisms to record the usage (e.g. invocation count) of the service APIs for charging purpose, on a per API invoker basis. + +[AR-4.4.2-c] The CAPIF shall provide mechanisms to record timestamp of the service API invocation. + +[AR-4.4.2-d] The CAPIF shall provide mechanisms to record the service API related information, e.g. API location. + +### 4.4.3 Requirements for 3rd party API providers + +[AR-4.4.3-a] The CAPIF shall support online and offline charging for 3rd party API providers' service APIs usage. + +[AR-4.4.3-b] The CAPIF shall provide mechanisms to query charging related information of the 3rd party service APIs by the authorized users. + +## 4.5 Operations, Administration and Maintenance + +### 4.5.1 Introduction + +This subclause specifies the OAM aspects including performance monitoring, fault monitoring, policy configurations, and certain lifecycle management aspects such as monitoring the running status of service APIs and related operations. + +## 4.5.2 Requirements + +[AR-4.5.2-a] The CAPIF shall provide mechanisms to monitor the status of service APIs, e.g. starting and stopping access of the service APIs. + +[AR-4.5.2-b] The CAPIF shall provide mechanisms to monitor and report the performance of the service APIs. + +[AR-4.5.2-c] The CAPIF shall provide mechanisms to monitor and report the fault information about the service APIs. + +[AR-4.5.2-d] The CAPIF shall provide mechanisms to record change events of service APIs, e.g. service APIs relocation. + +[AR-4.5.2-e] The CAPIF shall provide mechanisms to configure policies related to service APIs. + +## 4.5.3 Requirements for 3rd party API providers + +[AR-4.5.3-a] The CAPIF shall provide mechanisms to configure policies related to 3rd party service APIs by the authorized users. + +[AR-4.5.3-b] The CAPIF shall provide mechanisms to monitor faults, performance and status of the 3rd party service APIs by the authorized users. + +# 4.6 Service API invocation monitoring + +## 4.6.1 Introduction + +The CAPIF includes monitoring functions. This enables API provider to monitor service API invocations, to determine critical aspects such as system load, API usage information, uncover potential overload and attacks (e.g. DDoS) conditions. + +## 4.6.2 Requirements + +[AR-4.6.2-a] The CAPIF shall provide mechanisms to capture service API invocation events and make them available to service API provider. + +[AR-4.6.2-b] The CAPIF shall provide mechanisms to notify events related to overload and threat conditions (e.g. system load, resource usage information). + +[AR-4.6.2-c] The CAPIF shall provide mechanisms to allow service API provider to apply monitoring filters based on criteria such as API invoker's ID and IP address, service API name and version, invoked operation, input parameters, and invocation result. + +# 4.7 Logging + +## 4.7.1 Introduction + +The CAPIF supports the ability to log events and store the corresponding logs. This enables the API providers to use the logs for the purpose of tracing back and statistical analysis. + +The following events in CAPIF are supported for logging: + +- Service API invocation events; +- API invoker onboarding events; and +- API invoker interactions with the CAPIF (e.g. authentication, authorization, discover service APIs). + +## 4.7.2 Logging events related to service API invocations + +[AR-4.7.2-a] The CAPIF shall provide mechanisms for service API invocation event logging and storage functionality. + +[AR-4.7.2-b] The service API invocation log shall be stored for a configurable time period, according to the service API provider's policy. + +[AR-4.7.2-c] The service API invocation log shall be stored securely, and shall only be accessed by CAPIF administrators of the service API provider. + +## 4.7.3 Logging events related to API invoker onboarding + +[AR-4.7.3-a] The CAPIF shall provide mechanisms for API invoker onboarding event logging and storage functionality. + +[AR-4.7.3-b] The API invoker onboarding log shall be stored at least for the duration during which the onboarding is valid. + +[AR-4.7.3-c] The API invoker onboarding log shall be stored securely, and shall only be accessed by CAPIF administrators. + +## 4.7.4 Logging events related to API invoker interaction with the CAPIF + +[AR-4.7.4-a] The CAPIF shall provide mechanisms for the event logging of API invoker interactions with the CAPIF (e.g. authentication, authorization, discover service APIs). + +[AR-4.7.4-b] The API invoker interactions log shall be stored for a configurable time period. + +[AR-4.7.4-c] The API invoker interactions log shall be stored securely, accessed only by CAPIF administrators. + +# 4.8 Auditing service API invocation + +## 4.8.1 Introduction + +The CAPIF includes auditing capabilities. This enables the service API provider to identify illegal service API invocations e.g. by querying the service API invocation log. + +## 4.8.2 Requirements + +[AR-4.8.2-a] The CAPIF shall provide mechanisms to query the service API invocation log, by CAPIF administrators. + +# 4.9 Onboarding API invoker + +## 4.9.1 Introduction + +This subclause specifies the requirements related to onboarding API invoker to the CAPIF. + +## 4.9.2 Requirements + +[AR-4.9.2-a] The CAPIF shall provide the capability to onboard new API invokers. + +[AR-4.9.2-b] The CAPIF shall support granting an API invoker's request to onboard with the CAPIF administrator. + +[AR-4.9.2-c] The CAPIF shall support offboarding an API invoker from the CAPIF. + +[AR-4.9.2-d] The CAPIF shall support updating an API invoker's API list e.g., subsequent to discovery of new API(s). + +## 4.10 Policy configuration + +### 4.10.1 Introduction + +This subclause specifies the policy configuration related requirements. + +### 4.10.2 Requirements + +[AR-4.10.2-a] The CAPIF shall support policy configurations (e.g. related to the protection of platforms and network, specific functionalities exposed, message payload size or throughput). + +## 4.11 Protocol design + +### 4.11.1 Introduction + +In order for the CAPIF to be common across all present and future API invokers for various usages and purposes, a minimum common protocol stack model is necessary so that all API invokers that use the common-framework-based API need to support only one and the same set of protocols, e.g. security layer protocol(s). Extensibility of this model allows evolution and re-use. + +### 4.11.2 Requirements + +[AR-4.11.2-a] The CAPIF shall support a minimum common protocol stack model common for all API implementations to be based on. + +[AR-4.11.2-b] The CAPIF shall support a common security mechanism for all API implementations to provide confidentiality and integrity protection. + +[AR-4.11.2-c] The CAPIF shall be extensible to support different protocol stack models, including related security mechanisms, in addition to the minimum common protocol stack model. + +NOTE: Potentially, Stage 3 needs to consider all CAPIF APIs for protocol extensibility. + +[AR-4.11.2-d] CAPIF APIs and associated information flows shall be extensible to support vendor-specific functionality. + +## 4.12 Interconnection between the CAPIF providers + +### 4.12.1 Introduction + +Two organizations with a business relationship that have each deployed CAPIF may need to interoperate to allow API invokers in each trust domain to utilize service APIs from both CAPIFs as illustrated in figure 4.12.1-1. + +![Diagram illustrating the interconnection between two CAPIF providers, A and B. Each provider contains an API invoker connected to Service APIs. The two Service APIs are interconnected.](c923e830926610e73d6cbcdedb9e5ea4_img.jpg) + +The diagram shows two separate boxes representing CAPIF provider A and CAPIF provider B. Inside each box, there is a rectangular box labeled 'API invoker' connected by a vertical line to an oval labeled 'Service APIs'. A horizontal line connects the 'Service APIs' oval in provider A to the 'Service APIs' oval in provider B, indicating an interconnection between the two providers' service APIs. + +Diagram illustrating the interconnection between two CAPIF providers, A and B. Each provider contains an API invoker connected to Service APIs. The two Service APIs are interconnected. + +**Figure 4.12.1-1: Interconnection between the CAPIF providers** + +NOTE: From each CAPIF provider's perspective the other CAPIF provider is a 3rd party. + +## 4.12.2 Requirements + +[AR-4.12.2-a] The CAPIF shall provide mechanisms to enable the API invokers of the CAPIF provider to discover and invoke the service APIs of the 3rd party CAPIF provider. + +## 4.13 Identities + +### 4.13.1 Introduction + +This subclause specifies the identities related requirements. + +### 4.13.2 Requirements + +[AR-4.13.2-a] The CAPIF shall support uniform addressing (e.g. identity) for communication within the same trust domain or from the 3rd party trust domain. + +[AR-4.13.2-b] The CAPIF shall support identities for uniquely identifying each API. + +## 4.14 API provider domain interactions + +### 4.14.1 Introduction + +This subclause specifies the API provider domain interactions related requirements. + +### 4.14.2 Requirements + +[AR-4.14.2-a] The CAPIF shall enable interactions between multiple API exposing functional entities within the same trust domain. + +[AR-4.14.2-b] The CAPIF shall enable interactions of multiple API exposing functional entities between trust domains. + +**Editor's note:** Adding architectural requirements for interactions between other functions within the API provider domain is FFS. + +## 4.15 Dynamic routing of service API invocation + +### 4.15.1 Introduction + +This subclause specifies the dynamic routing of service API invocation related requirements. + +### 4.15.2 Requirements + +[AR-4.15.2-a] The CAPIF shall provide a mechanism to support the dynamic routing of service API invocation. + +## 4.16 Registering API provider domain functions + +### 4.16.1 Introduction + +This subclause specifies the requirements related to registration of API provider domain functions on the CAPIF core function. + +### 4.16.2 Requirements + +[AR-4.16.2-a] The CAPIF shall provide the capability to register API provider domain functions. + +[AR-4.16.2-b] The CAPIF shall support the capability to update the registration information of the API provider domain functions. + +## 4.17 Resource owner-aware northbound API invocation + +### 4.17.1 Introduction + +This subclause specifies requirements related to the resource owner-aware northbound API invocation. In the current release, the scope of API invoker on a UE in Resource owner-aware northbound API access is limited to accessing its own resources only, i.e., resource owner is a user of the UE hosting the API invoker that can authorize the API access. + +### 4.17.2 Requirements + +[AR-4.17.2-a] The CAPIF shall support applications on the UE acting as an API invoker. + +[AR-4.17.2-b] The CAPIF shall support the authentication of the resource owner. + +[AR-4.17.2-c] The CAPIF shall enable the resource owner(s) to provide and revoke the authorization information for the resource exposure by API provider. + +--- + +## 5 Involved business relationships + +### 5.1 Basic CAPIF business relationships + +Figure 5.1-1 shows the typical business relationships in CAPIF. + +![Diagram illustrating the business relationships in CAPIF. It shows three entities: API invoker, CAPIF provider, and API provider. The API invoker is connected to the CAPIF provider via a double-headed arrow labeled 'Service Agreement'. The CAPIF provider is connected to the API provider via a double-headed arrow labeled 'Service API arrangement'.](1bf34e86af3591c80bfbc1c318f811c0_img.jpg) + +``` +graph TD; API_invoker((API invoker)) <--> |Service Agreement| CAPIF_provider((CAPIF provider)); CAPIF_provider <--> |Service API arrangement| API_provider((API provider)); +``` + +Diagram illustrating the business relationships in CAPIF. It shows three entities: API invoker, CAPIF provider, and API provider. The API invoker is connected to the CAPIF provider via a double-headed arrow labeled 'Service Agreement'. The CAPIF provider is connected to the API provider via a double-headed arrow labeled 'Service API arrangement'. + +**Figure 5.1-1: Business relationships in CAPIF** + +The API invoker is typically provided by a 3rd party application provider who has service agreement with a CAPIF provider. + +The API provider hosts one or more service APIs and has a service API arrangement with CAPIF provider to offer the service APIs to the API invoker. + +The CAPIF provider and the API provider can be part of the same organization (e.g. PLMN operator), in which case the business relationship between the two is internal to a single organization. The CAPIF provider and the API provider can be part of different organizations, in which case the business relationship between the two must exist. + +## 5.2 CAPIF business relationships for RNAA + +Figure 5.2-1 shows the CAPIF business relationships for the resource owner-aware northbound API access (RNAA). + +![Diagram of CAPIF business relationships for RNAA](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +The diagram illustrates the business relationships for RNAA. At the top, two ovals represent the 'API invoker' and the 'Resource owner'. Below them, a dashed rectangular box contains two more ovals: the 'CAPIF provider' on the left and the 'API provider' on the right. A double-headed vertical arrow labeled 'Service Agreement' connects the 'API invoker' to the 'CAPIF provider'. A double-headed vertical arrow labeled 'Resource Access Arrangement' connects the 'Resource owner' to the 'API provider'. A double-headed horizontal arrow labeled 'Service API arrangement' connects the 'CAPIF provider' and the 'API provider' within the dashed box. + +Diagram of CAPIF business relationships for RNAA + +**Figure 5.2-1: CAPIF business relationships for RNAA** + +The business relationships the API invoker, the CAPIF provider, and the API provider follow the description in the clause 5.1. In addition to them, the resource owner is an entity capable of granting access to a protected resource related to the resource exposed by the API provider. The API invoker and the resource owner can be the same entity or separate entities. In the current release, the resource owner is a user of a UE and can provide authorization information using the UE. + +NOTE: In the current release, both the CAPIF provider and the API provider should belong to the same organization (e.g., PLMN operator) and the service API arrangement is not required explicitly. + +# 6 Functional model + +## 6.1 General + +The Common API framework (CAPIF) functional architecture is described in this subclause. The CAPIF architecture is defined as service-based and interactions between the CAPIF functions are represented in two ways: + +- A service-based representation, where CAPIF functions enable other authorized CAPIF functions to access their services; + +- A reference point representation, where interactions between any two CAPIF functions (e.g. CCF, AEF) is shown by an appropriate point-to-point reference point (e.g. CAPIF-3). + +The CAPIF functional architecture can be adopted by any 3GPP functionality providing 3GPP northbound service APIs. + +NOTE 1: The terms “functional architecture” and “functional model” mean the same and have been used interchangeably in this specification. + +NOTE 2: The functional model described in this specification applies to both PLMN(s) and to SNPN(s). + +## 6.2 Functional model description + +### 6.2.0 Functional model description for the CAPIF + +Figure 6.2.0-1 shows the reference point based functional model for the CAPIF. + +![Functional model diagram for the CAPIF showing interactions between an API invoker, CAPIF core function, and API provider domain functions within a PLMN Trust Domain.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +The diagram illustrates the functional model for the CAPIF. It is contained within a dashed box labeled 'PLMN Trust Domain'. Inside this domain, there are two 'API invoker' blocks. The left 'API invoker' connects to 'CAPIF APIs' (represented by an oval) via reference point 'CAPIF-1e'. The right 'API invoker' connects to 'Service APIs' (represented by an oval) via reference point 'CAPIF-2'. Both 'CAPIF APIs' and 'Service APIs' connect to the 'CAPIF core function' (a large rectangle) via reference point 'CAPIF-1'. The 'CAPIF core function' connects to three functions in the 'API provider domain' (a dashed box) via reference points 'CAPIF-3', 'CAPIF-4', and 'CAPIF-5' respectively. These functions are 'API exposing function', 'API publishing function', and 'API management function'. The 'Service APIs' also connect to the 'API exposing function' via reference point 'CAPIF-2e'. A vertical double-headed arrow on the left side of the 'PLMN Trust Domain' box is labeled 'PLMN Trust Domain'. + +Functional model diagram for the CAPIF showing interactions between an API invoker, CAPIF core function, and API provider domain functions within a PLMN Trust Domain. + +**Figure 6.2.0-1: Functional model for the CAPIF** + +The CAPIF is hosted within the PLMN operator network (or even an SNPN). The API invoker is typically provided by a 3rd party application provider who has service agreement with PLMN operator. The API invoker may reside within the same trust domain as the PLMN operator network. + +In a reference point based model, the API invoker within the PLMN trust domain interacts with the CAPIF via CAPIF-1 and CAPIF-2. The API invoker from outside the PLMN trust domain interacts with the CAPIF via CAPIF-1e and CAPIF-2e. The API exposing function, the API publishing function and the API management function of the API provider domain (together known as API provider domain functions) within the PLMN trust domain interacts with the CAPIF core function via CAPIF-3, CAPIF-4 and CAPIF-5 respectively. + +![Functional model for interactions between API exposing functions](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the functional model for interactions between API exposing functions within the PLMN Trust Domain. A vertical double-headed arrow on the left is labeled 'PLMN Trust Domain'. At the top, an 'API invoker' block is connected via a vertical line labeled 'CAPIF-2' to a middle block. This middle block contains two stacked ovals labeled 'Service APIs' and a rectangle labeled 'API exposing function'. Below this middle block is another vertical line labeled 'CAPIF-7', which connects to a bottom block. The bottom block also contains two stacked ovals labeled 'Service APIs' and a rectangle labeled 'API exposing function'. A dashed rectangular box labeled 'API provider domain' encloses the middle and bottom blocks. + +Functional model for interactions between API exposing functions + +**Figure 6.2.0-2: Functional model for interactions between API exposing functions** + +As illustrated in figure 6.2.0-2, the interactions between the API exposing functions within the PLMN trust domain is via CAPIF-7. + +The CAPIF core function provides CAPIF APIs to the API invoker over CAPIF-1 and CAPIF-1e. The API exposing function provides the service APIs to the API invoker over CAPIF-2 and CAPIF-2e. + +NOTE 1: The communication between the API exposing function and the CAPIF core function, between the API publishing function and the CAPIF core function and between the API management function and the CAPIF core function over CAPIF-3, CAPIF-4 and CAPIF-5 respectively can be API based. + +The detailed information of the APIs provided by the CAPIF core function is specified in clause 10. + +The security aspects of CAPIF reference points are specified in 3GPP TS 33.122 [12]. + +Figure 6.2.0-3 illustrates the CAPIF functional model using service-based interfaces. + +![Figure 6.2.0-3: CAPIF functional model representation using service-based interfaces. The diagram shows a 'CAPIF core function' and an 'API invoker' at the top. Below them is a horizontal line representing a service-based interface. The 'CAPIF core function' connects to this interface via a 'Ccaf' interface. Below the interface line, there are three boxes: 'API exposing function', 'API publishing function', and 'API management function'. The 'API exposing function' connects to the interface line via a 'Caef' interface. The 'API publishing function' and 'API management function' are connected to the interface line by vertical lines.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Figure 6.2.0-3: CAPIF functional model representation using service-based interfaces. The diagram shows a 'CAPIF core function' and an 'API invoker' at the top. Below them is a horizontal line representing a service-based interface. The 'CAPIF core function' connects to this interface via a 'Ccaf' interface. Below the interface line, there are three boxes: 'API exposing function', 'API publishing function', and 'API management function'. The 'API exposing function' connects to the interface line via a 'Caef' interface. The 'API publishing function' and 'API management function' are connected to the interface line by vertical lines. + +Figure 6.2.0-3: CAPIF functional model representation using service-based interfaces + +Table 6.2.0-1 specifies the service-based interfaces supported by CAPIF. + +Table 6.2.0-1: Service-based interfaces supported by CAPIF + +| Service-based interface | Entity | APIs offered | +|-------------------------|-----------------------|---------------------------| +| Ccaf | CAPIF core function | Specified in subclause 10 | +| Caef | API exposing function | Specified in subclause 11 | + +## 6.2.1 Functional model description to support 3rd party API providers + +Figure 6.2.1-1 shows the functional model for the CAPIF to support 3rd party API providers. + +![Figure 6.2.1-1: Functional model for the CAPIF to support 3rd party API providers. This complex diagram shows the interaction between an 'API invoker' and a 'CAPIF core function' within a 'PLMN Trust Domain', and multiple 'API provider domains' within a '3rd party Trust Domain'. 'API invoker 1' connects to 'CAPIF APIs' via 'CAPIF-1e'. 'CAPIF APIs' connects to the 'CAPIF core function' via 'CAPIF-3', 'CAPIF-4', 'CAPIF-5', 'CAPIF-3e', 'CAPIF-4e', and 'CAPIF-5e'. The 'CAPIF core function' connects to 'API invoker 2' via 'CAPIF-1' and 'CAPIF-2'. 'API invoker 2' connects to 'Service APIs' (API exposing function) via 'CAPIF-2e'. 'Service APIs' connects to the 'CAPIF core function' via 'CAPIF-7e'. 'API invoker 3' connects to 'Service APIs' (API exposing function) via 'CAPIF-1e' and 'CAPIF-2e'. 'Service APIs' connects to the 'CAPIF core function' via 'CAPIF-2'. The diagram is divided into two trust domains: 'PLMN Trust Domain' (left) and '3rd party Trust Domain' (right). The '3rd party Trust Domain' contains two 'API provider domain' boxes, each containing 'Service APIs' (API exposing function), 'API publishing function', and 'API management function'.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +Figure 6.2.1-1: Functional model for the CAPIF to support 3rd party API providers. This complex diagram shows the interaction between an 'API invoker' and a 'CAPIF core function' within a 'PLMN Trust Domain', and multiple 'API provider domains' within a '3rd party Trust Domain'. 'API invoker 1' connects to 'CAPIF APIs' via 'CAPIF-1e'. 'CAPIF APIs' connects to the 'CAPIF core function' via 'CAPIF-3', 'CAPIF-4', 'CAPIF-5', 'CAPIF-3e', 'CAPIF-4e', and 'CAPIF-5e'. The 'CAPIF core function' connects to 'API invoker 2' via 'CAPIF-1' and 'CAPIF-2'. 'API invoker 2' connects to 'Service APIs' (API exposing function) via 'CAPIF-2e'. 'Service APIs' connects to the 'CAPIF core function' via 'CAPIF-7e'. 'API invoker 3' connects to 'Service APIs' (API exposing function) via 'CAPIF-1e' and 'CAPIF-2e'. 'Service APIs' connects to the 'CAPIF core function' via 'CAPIF-2'. The diagram is divided into two trust domains: 'PLMN Trust Domain' (left) and '3rd party Trust Domain' (right). The '3rd party Trust Domain' contains two 'API provider domain' boxes, each containing 'Service APIs' (API exposing function), 'API publishing function', and 'API management function'. + +Figure 6.2.1-1: Functional model for the CAPIF to support 3rd party API providers + +The CAPIF core function in the PLMN trust domain supports service APIs from both the PLMN trust domain and the 3rd party trust domain having business relationship with PLMN. The API invokers may exist within the PLMN trust domain, or within the 3rd party trust domain or outside of both the PLMN trust domain and the 3rd party trust domain. The API provider domain 1 offers the service APIs from the PLMN operator. The API provider domain 2 offers the service APIs from the 3rd party. When the 3rd party API provider is a trusted 3rd party of the PLMN, the API provider domain 1 also offers the service APIs from the 3rd party. + +The API invoker 2 within the PLMN trust domain interacts with the CAPIF core function via CAPIF-1, and invokes the service APIs in the PLMN trust domain via CAPIF-2 and invokes the service APIs in the 3rd party trust domain via CAPIF-2e. The API invoker 3 within the 3rd party trust domain interacts with the CAPIF core function via CAPIF-1e, and invokes the service APIs in the PLMN trust domain via CAPIF-2e and invokes the service APIs in 3rd party trust domain via CAPIF-2. The API invoker 1 from outside the PLMN trust domain and 3rd party trust domain, interacts with the CAPIF core function via CAPIF-1e and invokes the service APIs in the PLMN trust domain and the service APIs in the 3rd party trust domain via CAPIF-2e. + +The API exposing function, the API publishing function and the API management function of the API provider domain 1 within the PLMN trust domain interacts with the CAPIF core function via CAPIF-3, CAPIF-4 and CAPIF-5 respectively. The API exposing function, the API publishing function and the API management function of the API provider domain 2 within the 3rd party trust domain interacts with the CAPIF core function in the PLMN trust domain via CAPIF-3e, CAPIF-4e and CAPIF-5e respectively. The API exposing function within the PLMN trust domain and the 3rd party trust domain provides the service APIs to the API invoker, offered by the respective trust domains. + +The interactions between the API exposing functions within the PLMN trust domain is via CAPIF-7 (not shown in the figure 6.2.1-1 for simplicity). The API exposing function within the PLMN trust domain interacts with the API exposing function in the 3rd party trust domain via CAPIF-7e. + +NOTE 1: The communication between the API exposing function and the CAPIF core function, between the API publishing function and the CAPIF core function and between the API management function and the CAPIF core function over CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e respectively can be API based. + +The detailed information of the APIs provided by the CAPIF core function is specified in clause 10. + +NOTE 2: The security aspects of CAPIF reference points are under SA3 responsibility and out of scope of the present document. + +## 6.2.2 Functional model description to support CAPIF interconnection + +Figure 6.2.2-1 shows the architectural model for the CAPIF interconnection which allows API invokers of a CAPIF provider to utilize the service APIs from the 3rd party CAPIF provider. + +![Figure 6.2.2-1: High level functional architecture for CAPIF interconnection with multiple CAPIF provider domains. The diagram shows two trust domains, 'Trust domain of CAPIF provider A' and 'Trust domain of CAPIF provider B', connected via CAPIF-6e. Each domain contains an API invoker, a CAPIF core function, and an API provider domain. Within the API provider domains, there are Service APIs, API exposing, publishing, and management functions. Reference points CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, CAPIF-5, CAPIF-1e, CAPIF-2e, CAPIF-3e, CAPIF-4e, and CAPIF-5e are shown connecting these components within and across domains.](b6b53a74ad203c01b81e5427e9d6a898_img.jpg) + +Figure 6.2.2-1: High level functional architecture for CAPIF interconnection with multiple CAPIF provider domains. The diagram shows two trust domains, 'Trust domain of CAPIF provider A' and 'Trust domain of CAPIF provider B', connected via CAPIF-6e. Each domain contains an API invoker, a CAPIF core function, and an API provider domain. Within the API provider domains, there are Service APIs, API exposing, publishing, and management functions. Reference points CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, CAPIF-5, CAPIF-1e, CAPIF-2e, CAPIF-3e, CAPIF-4e, and CAPIF-5e are shown connecting these components within and across domains. + +**Figure 6.2.2-1: High level functional architecture for CAPIF interconnection with multiple CAPIF provider domains** + +Figure 6.2.2-2 shows the architectural model for the CAPIF interconnection within the same CAPIF provider domain, which allows API invokers of CAPIF core function 1 to utilize the service APIs from CAPIF core function 2, where both CAPIF core function 1 and CAPIF core function 2 are hosted within the trust domain of the CAPIF provider A. + +![Figure 6.2.2-2: High level functional architecture for CAPIF interconnection within a CAPIF provider domain. The diagram shows two CAPIF core functions, CAPIF core function 1 and CAPIF core function 2, connected via the CAPIF-6 reference point. Both are within the 'Trust domain of CAPIF provider A'. CAPIF core function 1 is connected to an 'API provider domain' containing 'Service APIs', 'API exposing function', 'API publishing function', and 'API management function' via CAPIF-3, CAPIF-4, and CAPIF-5. CAPIF core function 2 is similarly connected to another 'API provider domain' via CAPIF-3, CAPIF-4, and CAPIF-5. API invokers are shown interacting with the core functions: one invoker connects to CAPIF core function 1 via CAPIF-1 and CAPIF-2; another connects to CAPIF core function 2 via CAPIF-2e; a third connects to CAPIF core function 1 via CAPIF-2e and CAPIF-1e. The entire system is enclosed in a dashed box labeled 'Trust domain of CAPIF provider A'.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +Figure 6.2.2-2: High level functional architecture for CAPIF interconnection within a CAPIF provider domain. The diagram shows two CAPIF core functions, CAPIF core function 1 and CAPIF core function 2, connected via the CAPIF-6 reference point. Both are within the 'Trust domain of CAPIF provider A'. CAPIF core function 1 is connected to an 'API provider domain' containing 'Service APIs', 'API exposing function', 'API publishing function', and 'API management function' via CAPIF-3, CAPIF-4, and CAPIF-5. CAPIF core function 2 is similarly connected to another 'API provider domain' via CAPIF-3, CAPIF-4, and CAPIF-5. API invokers are shown interacting with the core functions: one invoker connects to CAPIF core function 1 via CAPIF-1 and CAPIF-2; another connects to CAPIF core function 2 via CAPIF-2e; a third connects to CAPIF core function 1 via CAPIF-2e and CAPIF-1e. The entire system is enclosed in a dashed box labeled 'Trust domain of CAPIF provider A'. + +**Figure 6.2.2-2: High level functional architecture for CAPIF interconnection within a CAPIF provider domain** + +The CAPIF provider A and CAPIF provider B host the CAPIF in their trust domains. A business relationship exists between the CAPIF providers. + +The CAPIF providers in their respective trust domain hosts multiple CAPIF instances where each CAPIF instance consists of the CAPIF core function (local), the API provider domain and the API invokers. All interactions within the CAPIF instance is according to the functional model specified in clause 6.2.0. + +When multiple CAPIF instances are deployed by a CAPIF provider there may be a hierarchy associated with the multiple CAPIF core function deployed which allows: + +- the designated CAPIF core function of the CAPIF provider A to interconnect with the designated CAPIF core function of the CAPIF provider B; and +- within CAPIF provider A, one or more CAPIF core function interacts with the designated CAPIF core function 1. + +The designated CAPIF core function of the CAPIF provider A provides the information about the CAPIF instances and service APIs deployed by the CAPIF provider A to the designated CAPIF core function of the CAPIF provider B and vice versa over CAPIF-6e reference point. + +The CAPIF core function 2 of CAPIF provider A provides the information about the service APIs to the CAPIF core function 1 over CAPIF-6 reference point. + +NOTE 1: Void + +The API invokers may exist within the trust domain of CAPIF provider A, or within the trust domain of CAPIF provider B or outside of the trust domains of both CAPIF provider A and CAPIF provider B. The API invoker of a CAPIF provider is onboarded with the CAPIF core function in the corresponding trust domain of the CAPIF provider. + +NOTE 2: For sake of simplicity, the service API interactions of API invokers of the CAPIF provider B are not shown. From each CAPIF provider's perspective the other CAPIF provider is a 3rd party. + +One or more CAPIF core function can publish service APIs to the designated CAPIF core function over CAPIF-6 reference point and, also discover the service APIs from the designated CAPIF core function and vice versa over CAPIF-6 reference point. + +The API invoker within the trust domain of CAPIF provider A interacts with the CAPIF core function of the CAPIF provider A via CAPIF-1 and discovers the service APIs of both CAPIF providers, and invokes the service APIs in the trust domain of CAPIF provider A via CAPIF-2 and invokes the service APIs in the trust domain of CAPIF provider B via CAPIF-2e. The API invoker from outside the trust domain of CAPIF providers, interacts with the CAPIF core function of the CAPIF provider A via CAPIF-1e and invokes the service APIs in the trust domain of the CAPIF providers via CAPIF-2e. + +NOTE 3: The communication between the CAPIF core function of the CAPIF providers over CAPIF-6 or CAPIF-6e can be API based. + +The detailed information of the APIs provided by the CAPIF core function is specified in clause 10. + +NOTE 4: The security aspects of CAPIF reference points are under SA3 responsibility and out of scope of the present document. + +NOTE 5: All interactions among entities within the CAPIF provider domains (regardless if CAPIF is deployed in a PLMN, SNPN or 3rd party network) are ruled by the functional model in clause 6.2.0, the support of 3rd party API providers is as in clause 6.2.1, whereas the interconnection among CCFs is according to this clause. + +### 6.2.3 Functional model description to support RNAA + +Figure 6.2.3-1 shows the architectural model for the RNAA which allows the resource owner to provide authorization to the API invocation. + +![High level functional architecture for CAPIF supporting RNAA diagram](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +The diagram illustrates the functional architecture for CAPIF supporting RNAA. It features a central 'CAPIF core function' block containing an 'Authorization function' (dashed box) and 'CAPIF APIs'. To the left, 'Resource owner client(s)' connect to the 'Authorization function' via 'CAPIF-8'. Above the core function, an 'API invoker' connects via 'CAPIF-1e'. To the right, an 'API provider domain' contains 'Service APIs', an 'API exposing function', an 'API publishing function', and an 'API management function'. Connections include 'CAPIF-1' (API invoker to CAPIF APIs), 'CAPIF-2' (API invoker to Service APIs), 'CAPIF-2e' (API invoker to Service APIs), 'CAPIF-3' (CAPIF APIs to API exposing function), 'CAPIF-4' (Authorization function to API publishing function), and 'CAPIF-5' (CAPIF core function to API management function). A vertical double-headed arrow on the left is labeled 'PLMN Trust Domain'. + +High level functional architecture for CAPIF supporting RNAA diagram + +Figure 6.2.3-1: High level functional architecture for CAPIF supporting RNAA + +The authorization function is an internal entity of the CAPIF core function. + +The resource owner client(s) interacts with the authorization function in the CAPIF core function via CAPIF-8. The resource owner communicates with the authorization function in the CAPIF core function to manage resource owner consent. + +The API exposing function (e.g. NEF, SCEF) acts as a resource owner consent enforcement point as specified in 3GPP TS 33.501 [8] and interacts with the authorization function in the CAPIF core function via CAPIF-3. The API exposing function can retrieve the resource owner consent parameters from the authorization function. + +NOTE 1: RNAA is supported for both 4G and 5G network. + +The API invoker interacts with authorization function in the CAPIF core function via CAPIF-1/CAPIF-1e. + +NOTE 2: In the current release, 3rd party API providers (i.e., API providers outside the PLMN trust domain) are not supported for RNAA. + +NOTE 3: The interaction between Resource Owner Client and CCF over CAPIF-8 is not specified in the current release of the specification. + +The security aspects of CAPIF supporting RNAA are specified in 3GPP TS 33.122 [12]. + +## 6.3 Functional entities description + +### 6.3.1 General + +Each subclause is a description of a functional entity and does not imply a physical entity. + +### 6.3.2 API invoker + +The API invoker is typically provided by a 3rd party application provider who has service agreement with PLMN operator. The API invoker may reside within the same trust domain as the PLMN operator network. The API invoker may be either an application on a server or an application on a UE. + +The API invoker supports the following capabilities: + +- Triggering API invoker onboarding/offboarding; +- Supporting the authentication by providing the API invoker identity and other information required for authentication of the API invoker; +- Supporting mutual authentication with CAPIF; +- Obtaining the authorization prior to accessing the service API; +- Discovering service APIs information; and +- Invoking the service APIs. + +NOTE: The details of the specific service APIs are out of scope of the present document. + +### 6.3.3 CAPIF core function + +The CAPIF core function consists of the following capabilities: + +- Authenticating the API invoker based on the identity and other information required for authentication of the API invoker; +- Supporting mutual authentication with the API invoker; +- Providing authorization for the API invoker prior to accessing the service API; +- Publishing, storing and supporting the discovery of service APIs information; +- Controlling the service API access based on PLMN operator configured policies; +- Storing the logs for the service API invocations and providing the service API invocation logs to authorized entities; + +- Charging based on the logs of the service API invocations; +- Monitoring the service API invocations; +- Onboarding a new API invoker and offboarding an API invoker; +- Storing policy configurations related to CAPIF and service APIs; +- Support accessing the logs for auditing (e.g. detecting abuse); and +- Supports publishing, discovery of service APIs information with another CAPIF core function in CAPIF interconnection. + +### 6.3.4 API exposing function + +The API exposing function is the provider of the service APIs and is also the service communication entry point of the service API to the API invokers. The API exposing function consists of the following capabilities: + +- Authenticating the API invoker based on the identity and other information required for authentication of the API invoker provided by the CAPIF core function; +- Validating the authorization provided by the CAPIF core function; and +- Logging the service API invocations at the CAPIF core function. + +### 6.3.5 API publishing function + +The API publishing function enables the API provider to publish the service APIs information in order to enable the discovery of service APIs by the API invoker. The API publishing function consists of the following capability: + +- Publishing the service API information of the API provider to the CAPIF core function. + +### 6.3.6 API management function + +The API management function enables the API provider to perform administration of the service APIs. The API management function consists of the following capabilities: + +- Auditing the service API invocation logs received from the CAPIF core function; +- Monitoring the events reported by the CAPIF core function; +- Configuring the API provider policies to the CAPIF core function; +- Monitoring the status of the service APIs; +- Onboarding the new API invokers and offboarding API invokers; and +- Registering and maintaining registration information of the API provider domain functions on the CAPIF core function. + +NOTE: The API invoker onboarding/offboarding in the API management function is out of the scope of the current release. + +### 6.3.7 Authorization function + +The authorization function consists of the following capabilities: + +- Receiving authorization from the resource owner; and +- Providing the API invoker with the authorization information which is needed to access the resource owner's resources. + +NOTE: In the current release, the authorization function is an internal entity of the CAPIF core function. + +### 6.3.8 Resource owner client + +The resource owner client consists of the following capabilities: + +- Providing authorization for resource access; and +- Managing and revoking authorization for resource access. + +NOTE: The procedures corresponding to these capabilities of Resource owner client are FFS and out of scope of the current release of the specification. + +## 6.4 Reference points + +### 6.4.1 General + +The reference points for CAPIF are described in the following subclauses. + +### 6.4.2 Reference point CAPIF-1 (between the API invoker and the CAPIF core function) + +The CAPIF-1 reference point, which exists between the API invoker and the CAPIF core function, is used for the API invoker within the PLMN trust domain to discover service APIs, to authenticate and to get authorization. + +The CAPIF-1 reference point supports: + +- Onboarding the new API invokers and offboarding API invokers; +- Authenticating the API invoker based on the identity and credentials of the API invoker; +- Mutual authentication between the API invoker and the CAPIF core function; +- Providing authorization for the API invoker prior to accessing the service API; +- Providing authorization for the API invoker based on RNAA; and +- Discovering the service APIs information. + +NOTE: The security aspects of CAPIF-1 are specified in subclause 6.2 of 3GPP TS 33.122 [12]. + +### 6.4.3 Reference point CAPIF-1e (between the API invoker and the CAPIF core function) + +The CAPIF-1e reference point, which exists between the API invoker and the CAPIF core function, is used for the API invoker outside the PLMN trust domain to discover service APIs, to authenticate and to get authorization. + +The CAPIF-1e reference point supports all the functions of CAPIF-1. + +NOTE: The security aspects of CAPIF-1e are specified in subclause 6.3 of 3GPP TS 33.122 [12]. + +### 6.4.4 Reference point CAPIF-2 (between the API invoker and the API exposing function) + +The CAPIF-2 reference point, which exists between the API invoker and the API exposing function belonging to the same trust domain, is used for the API invoker to communicate with the service APIs. + +The CAPIF-2 reference point supports: + +- Authenticating the API invoker based on the identity and credentials of the API invoker; +- Authorization verification for the API invoker upon accessing the service API; and + +- Invocation of service APIs. + +NOTE 1: The aspects related to the specific service API invocation in reference point CAPIF-2 are out of scope of the present document. + +NOTE 2: The security aspects of CAPIF-2 are specified in subclause 6.4 of 3GPP TS 33.122 [12]. + +#### 6.4.5 Reference point CAPIF-2e (between the API invoker and the API exposing function) + +The CAPIF-2e reference point, which exists between the API invoker and the API exposing function belonging to a different trust domain, is used for the API invoker to communicate with the service APIs. + +The CAPIF-2e reference point supports all the functions of CAPIF-2. + +NOTE: The security aspects of CAPIF-2e are specified in subclause 6.5 of 3GPP TS 33.122 [12]. + +#### 6.4.6 Reference point CAPIF-3 (between the API exposing function and the CAPIF core function) + +The CAPIF-3 reference point, which exists between the API exposing function and the CAPIF core function, is used for exercising access and policy related control for service API communications initiated by the API invoker. + +The CAPIF-3 reference point supports: + +- Authenticating the API invoker based on the identity and credentials of the API invoker; +- Providing authorization for the API invoker prior to accessing the service API; +- Authorization verification for the API invoker upon accessing the service API; +- Authorization verification for the API invoker based on RNAA; +- Controlling the service API access based on PLMN operator configured policies; +- Logging the service API invocations; and +- Charging the service API invocations. + +NOTE: The security aspects of CAPIF-3 are specified in subclause 6.6 of 3GPP TS 33.122 [12]. + +#### 6.4.7 Reference point CAPIF-4 (between the API publishing function and the CAPIF core function) + +The CAPIF-4 reference point, which exists between the API publishing function and the CAPIF core function, is used for publishing the service API information. + +The CAPIF-4 reference point supports: + +- Publishing the service APIs information by the API publishing function. + +NOTE: The security aspects of CAPIF-4 are specified in subclause 6.6 of 3GPP TS 33.122 [12]. + +#### 6.4.8 Reference point CAPIF-5 (between the API management function and the CAPIF core function) + +The CAPIF-5 reference point, which exists between the API management function and the CAPIF core function, is used for management of service API, API invoker and API provider domain function information. + +The CAPIF-5 reference point supports: + +- Accessing the service API invocation logs by the API management function; + +- Enabling the API management function to monitor the events reported due to the service APIs invocations; +- Onboarding new API invokers by provisioning the API invoker information at the CAPIF core function, requesting explicit grant of new API invokers onboarding and confirming onboarding success; +- Offboarding API invokers; +- Enabling the API management function to configure policies at the CAPIF core function e.g. service API invocation throttling, blocking API invocation for certain duration; +- Enabling the API provider to monitor the status of service APIs (e.g. pilot or live status, start or stop status of service API); +- Registering API provider domain functions on the CAPIF core function; and +- Update of the registration information of API provider domain functions on the CAPIF core function. + +NOTE 1: The security aspects of CAPIF-5 are specified in subclause 6.6 of 3GPP TS 33.122 [12]. + +NOTE 2: The API invoker onboarding/offboarding over CAPIF-5 is out of the scope of the current release. + +#### 6.4.9 Reference point CAPIF-3e (between the API exposing function and the CAPIF core function) + +The CAPIF-3e reference point, which exists between the API exposing function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain, is used for exercising access and policy related control for service API communications initiated by the API invoker. + +The CAPIF-3e supports all the functions of CAPIF-3. + +NOTE: The security aspects of CAPIF-3e are specified in clause 6.10 of 3GPP TS 33.122 [12]. + +#### 6.4.10 Reference point CAPIF-4e (between the API publishing function and the CAPIF core function) + +The CAPIF-4e reference point, which exists between the API publishing function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain, is used for publishing the service API information. + +The CAPIF-4e reference point supports all the functions of CAPIF-4. + +NOTE: The security aspects of CAPIF-4e are specified in clause 6.10 of 3GPP TS 33.122 [12]. + +#### 6.4.11 Reference point CAPIF-5e (between the API management function and the CAPIF core function) + +The CAPIF-5e reference point, which exists between the API management function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain, is used for management of service API, API invoker and API provider domain function information. + +The CAPIF-5e reference point supports all the functions of CAPIF-5. + +NOTE: The security aspects of CAPIF-5e are specified in clause 6.10 of 3GPP TS 33.122 [12]. + +#### 6.4.12 Reference point CAPIF-7 (between the API exposing functions) + +The CAPIF-7 reference point, which exists between the API exposing functions belonging to the same trust domain, is used for the forwarding or routing of the API invoker's service API invocation from one API exposing function to the other API exposing function deployed in the PLMN trust domain. + +The CAPIF-7 reference point supports all the functions of CAPIF-2. + +The CAPIF-7 reference point supports invocation of service APIs originated by the API invoker using CAPIF-2. + +NOTE 1: The aspects related to the specific service API invocation in reference point CAPIF-7 are out of scope of the present document. + +NOTE 2: The security aspects of CAPIF-7 are the responsibility of SA3. + +#### 6.4.13 Reference point CAPIF-7e (between the API exposing functions) + +The CAPIF-7e reference point, which exists between the API exposing functions belonging to different trust domains, is used for the forwarding or routing of the API invoker's service API invocation from one API exposing function to the other API exposing function between different trust domains. + +The CAPIF-7e reference point supports all the functions of CAPIF-2e. + +NOTE: The security aspects of CAPIF-7e are the responsibility of SA3. + +#### 6.4.14 Reference point CAPIF-6 (between the CAPIF core functions of the same CAPIF provider) + +The CAPIF-6 reference point exists between the CAPIF core functions within the same trust domain of CAPIF provider. + +The CAPIF-6 reference point supports: + +- Publishing the service APIs information; and +- Discovering the service APIs information. + +#### 6.4.15 Reference point CAPIF-6e (between the CAPIF core functions of different CAPIF providers) + +The CAPIF-6e reference point exists between the CAPIF core function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain. + +The CAPIF-6e reference point supports all the functions of CAPIF-6. + +NOTE: The security aspects of CAPIF-6e will be specified by SA3. + +**Editor's note:** Reference to the appropriate SA3 specification is needed. + +#### 6.4.16 Reference point CAPIF-8 (between the CAPIF core function and the resource owner client) + +The CAPIF-8 reference point exists between the CAPIF core function and the resource owner client. + +The CAPIF-8 reference point supports: + +- Providing authorization for resource access; and +- Managing and revoking the provided authorization. + +NOTE: The functionalities over CAPIF-8 is FFS and out of scope of the current release of the specification. + +### 6.5 Service-based interfaces + +The CAPIF architecture contains the following service-based interfaces: + +- Cccf: Service-based interface exhibited by CAPIF core function. +- Caef: Service-based interface exhibited by API exposing function. + +## 7 Application of functional model to deployments + +### 7.1 General + +The CAPIF deployments in centralized and distributed models are described in clause 7.2 and clause 7.3. The multiple CCFs deployment is described in clause 7.4. + +The RNAA deployments are described in clause 7.5. + +The CAPIF deployment models shown are not exhaustive. + +### 7.2 Centralized deployment + +The CAPIF can be deployed centrally as illustrated in the figure 7.2-1. + +![Diagram of centralized deployment of CAPIF. An API invoker at the top connects to two interfaces: CAPIF-1 and CAPIF-2. CAPIF-1 leads to a box containing 'CAPIF APIs' and 'CAPIF core function'. CAPIF-2 leads to a box containing 'Service APIs', 'API exposing function', 'API publishing function', 'API management function', and 'API provider domain'. The 'CAPIF APIs' and 'Service APIs' are shown as ovals within their respective boxes.](f732d3320afe06d979aabbd366184254_img.jpg) + +``` +graph TD; API_Invoker[API invoker] -- CAPIF-1 --> CAPIF_Interfaces[CAPIF APIs]; API_Invoker -- CAPIF-2 --> Service_Interfaces[Service APIs]; subgraph CAPIF_Core [CAPIF core function]; CAPIF_Interfaces; end; subgraph API_Provider_Domain [API provider domain]; Service_Interfaces; API_Exposing[API exposing function]; API_Publishing[API publishing function]; API_Management[API management function]; end; +``` + +Diagram of centralized deployment of CAPIF. An API invoker at the top connects to two interfaces: CAPIF-1 and CAPIF-2. CAPIF-1 leads to a box containing 'CAPIF APIs' and 'CAPIF core function'. CAPIF-2 leads to a box containing 'Service APIs', 'API exposing function', 'API publishing function', 'API management function', and 'API provider domain'. The 'CAPIF APIs' and 'Service APIs' are shown as ovals within their respective boxes. + +**Figure 7.2-1: Centralized deployment of CAPIF** + +In one centralized deployment, the CAPIF core function and the API provider domain functions are co-located. The API invoker can interact independently with the CAPIF core function and the API exposing function including the service APIs. The CAPIF appears as a gateway for all API invoker interactions. The API invoker obtains the service API information and its entry point details from the CAPIF core function via CAPIF-1. The service communication point of entry for the service API is the API exposing function which also applies any access control or policy control to the internal interactions between the API invoker and the service API in coordination with the CAPIF core function. + +**NOTE:** The API invoker can be outside the PLMN trust domain and will access the CAPIF via CAPIF-1e and CAPIF-2e instead of CAPIF-1 and CAPIF-2. + +Another variation of the centralized deployment is where the CAPIF core function and the API exposing function is co-located where as other API provider domain functions (API publishing function and API management function) are not co-located with the API exposing function. In such deployment scenario, the CAPIF core function interacts with the API publishing function and the API management function via CAPIF-4 and CAPIF-5 reference points respectively. + +### 7.3 Distributed deployment + +The CAPIF can be deployed in a distributed manner illustrated in the figure 7.3-1. + +![Diagram illustrating the distributed deployment of the CAPIF within the PLMN trust domain. The diagram shows an API invoker at the top connected to a CAPIF core function on the left and an API provider domain on the right. The CAPIF core function contains a CAPIF APIs component. The API provider domain contains Service APIs, an API exposing function, an API publishing function, and an API management function. Reference points CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, and CAPIF-5 are shown between the components.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` +graph TD; API_Invoker[API invoker] -- CAPIF-1 --> CAPIF_APIs((CAPIF APIs)); API_Invoker -- CAPIF-2 --> Service_APIs((Service APIs)); CAPIF_Core[CAPIF core function] --- CAPIF_APIs; subgraph API_Provider_Domain [API provider domain]; API_Exposing[API exposing function]; API_Publishing[API publishing function]; API_Management[API management function]; end; Service_APIs --- API_Exposing; CAPIF_Core ---|CAPIF-3| API_Exposing; CAPIF_Core ---|CAPIF-4| API_Publishing; CAPIF_Core ---|CAPIF-5| API_Management; +``` + +Diagram illustrating the distributed deployment of the CAPIF within the PLMN trust domain. The diagram shows an API invoker at the top connected to a CAPIF core function on the left and an API provider domain on the right. The CAPIF core function contains a CAPIF APIs component. The API provider domain contains Service APIs, an API exposing function, an API publishing function, and an API management function. Reference points CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, and CAPIF-5 are shown between the components. + +**Figure 7.3-1: Distributed deployment of the CAPIF within PLMN trust domain** + +In distributed deployment, the CAPIF core function and the API provider domain functions are not co-located. The CAPIF core function interacts with the API exposing function, the API publishing function and the API management function via CAPIF-3, CAPIF-4 and CAPIF-5 reference points respectively. The API invoker can interact independently with the CAPIF core function and the API exposing function including the service APIs. In this deployment, the API exposing function appears as an agent for all service API invocations from the API invoker. The API invoker obtains the service API information and its entry point details from the CAPIF core function via CAPIF-1 interface. The first point of entry for the service API is the API exposing function during API invocation. The API exposing function acts as agent for service API applying any access control or policy control to the interactions between the API invoker and the service API in coordination with the CAPIF core function via CAPIF-3 interface. + +The CAPIF can be deployed by splitting the functionality of the API exposing function among multiple API exposing function entities, of which one acts as the entry point. However there will be single API publishing function and single API management function in the API provider domain although there could be multiple API exposing function entities. The CAPIF deployment with cascading API exposing functions is as illustrated in the figure 7.3-2. + +![Diagram illustrating the distributed deployment of the CAPIF with cascading API exposing functions. The diagram shows an API invoker connected to a CAPIF core function and an API exposing function (AEF-1). The CAPIF core function is connected to the API invoker via CAPIF-1 and to the API provider domain via CAPIF-3, CAPIF-4, and CAPIF-5. The API provider domain contains AEF-1, AEF-2, and AEF-3. AEF-1 is connected to the API invoker via CAPIF-2 and to the CAPIF core function via CAPIF-3. AEF-1 is also connected to AEF-2 and AEF-3 via CAPIF-7 (CAPIF-2 compliant). AEF-2 and AEF-3 are connected to the API provider domain via CAPIF-4 and CAPIF-5.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +graph TD + subgraph API_provider_domain [API provider domain] + AEF1[Service X & Y APIs +API exposing function +(AEF-1)] + AEF2[Service X APIs +API exposing function +(AEF-2)] + AEF3[Service Y APIs +API exposing function +(AEF-3)] + APF[API publishing function] + AMF[API management function] + end + CAPIF_core[CAPIF core function] + API_invoker[API invoker] + + API_invoker -- CAPIF-1 --> CAPIF_core + API_invoker -- CAPIF-2 --> AEF1 + CAPIF_core -- CAPIF-3 --> AEF1 + CAPIF_core -- CAPIF-4 --> APF + CAPIF_core -- CAPIF-5 --> AMF + AEF1 -- "CAPIF-7 (CAPIF-2 compliant)" --> AEF2 + AEF1 -- "CAPIF-7 (CAPIF-2 compliant)" --> AEF3 + +``` + +Diagram illustrating the distributed deployment of the CAPIF with cascading API exposing functions. The diagram shows an API invoker connected to a CAPIF core function and an API exposing function (AEF-1). The CAPIF core function is connected to the API invoker via CAPIF-1 and to the API provider domain via CAPIF-3, CAPIF-4, and CAPIF-5. The API provider domain contains AEF-1, AEF-2, and AEF-3. AEF-1 is connected to the API invoker via CAPIF-2 and to the CAPIF core function via CAPIF-3. AEF-1 is also connected to AEF-2 and AEF-3 via CAPIF-7 (CAPIF-2 compliant). AEF-2 and AEF-3 are connected to the API provider domain via CAPIF-4 and CAPIF-5. + +**Figure 7.3-2: Distributed deployment of the CAPIF with cascading API exposing functions** + +In this deployment option, the API exposing function can have several instances like AEF-1, AEF-2 and AEF-3 which can be assigned with different roles. The roles for each API exposing function are decided by the operator. In this illustration, the API exposing functions AEF-2 and AEF-3 provide service APIs for service X and service Y respectively. The API exposing function AEF-1 provides the service communication entry point to the service APIs for service X APIs and service Y APIs. The API exposing function AEF-1 for instance can hide the topology of service X APIs and service Y APIs from the API invoker. The API exposing function AEF-1 also applies any access control or policy control to the interactions between the API invoker and service X APIs and between the API invoker and service Y APIs, in coordination with the CAPIF core function using CAPIF-3. + +The API invoker interacts with the CAPIF core function via CAPIF-1. The API invoker interacts with service (X&Y) APIs on the API exposing function AEF-1 via CAPIF-2. The API exposing function AEF-1 forwards the invocation of the service X API or service Y API from the API invoker to the API exposing functions AEF-2 or AEF-3 respectively via CAPIF-2. The API messages are forwarded via CAPIF-7 (in compliance with CAPIF-2 interaction between the API invoker and the AEF-1) in the interactions between API exposing functions. The API invoker cannot directly interact with service X APIs and service Y APIs provided by API exposing functions AEF-2 and AEF-3 respectively. + +Different splits of responsibility are possible. In another example illustrated in figure 7.3-3, the API exposing function AEF-1 could provide topology hiding for API exposing functions AEF-2 and AEF-3, plus access control for AEF-3. The API exposing function AEF-2 would provide its own access control, interacting with the CAPIF core function via CAPIF-3. + +![Figure 7.3-3: Another example of distributed deployment of the CAPIF with cascading API exposing functions](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +graph TD + Invoker[API invoker] + subgraph Core[CAPIF core function] + CAPIF_APIs((CAPIF APIs)) + end + subgraph Provider[API provider domain] + AEF1[API exposing function +(AEF-1)] + AEF2[API exposing function +(AEF-2)] + AEF3[API exposing function +(AEF-3)] + APF[API publishing function] + AMF[API management function] + SXY((Service (X & Y) APIs)) + SX((Service X APIs)) + SY((Service Y APIs)) + end + + Invoker -- CAPIF-1 --- CAPIF_APIs + Invoker -- CAPIF-2 --- SXY + CAPIF_APIs -- CAPIF-3 --- AEF1 + CAPIF_APIs -- CAPIF-3 --- AEF2 + CAPIF_APIs -- CAPIF-4 --- APF + CAPIF_APIs -- CAPIF-5 --- AMF + AEF1 -- "CAPIF-7 +(CAPIF-2 compliant)" --- SX + AEF1 -- "CAPIF-7 +(CAPIF-2 compliant)" --- SY + AEF2 -.-> SX + AEF3 -.-> SY + +``` + +Figure 7.3-3: Another example of distributed deployment of the CAPIF with cascading API exposing functions + +**Figure 7.3-3: Another example of distributed deployment of the CAPIF with cascading API exposing functions** + +NOTE 1: The API invoker can be outside the PLMN trust domain and will access the CAPIF via CAPIF-1e and CAPIF-2e instead of CAPIF-1 and CAPIF-2. + +When considering the 3rd party trust domain deployment, the API provider domain belongs to a 3rd party trust domain, the CAPIF core function belongs to PLMN trust domain and the API invoker belongs to PLMN trust domain as illustrated in figure 7.3-4. + +![Figure 7.3-4: Distributed deployment of CAPIF considering PLMN trust domain and 3rd party trust domain](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +``` + +graph TD + Invoker[API invoker +(PLMN trust domain)] + subgraph Core[CAPIF core function +(PLMN trust domain)] + CAPIF_APIs((CAPIF APIs)) + end + subgraph Provider[API provider domain +(3rd party trust domain)] + AEF[API exposing function] + APF[API publishing function] + AMF[API management function] + S_APIs((Service APIs)) + end + + Invoker -- CAPIF-1 --- CAPIF_APIs + Invoker -- CAPIF-2e --- S_APIs + CAPIF_APIs -- CAPIF-3e --- AEF + Core -- CAPIF-4e --- APF + Core -- CAPIF-5e --- AMF + +``` + +Figure 7.3-4: Distributed deployment of CAPIF considering PLMN trust domain and 3rd party trust domain + +**Figure 7.3-4: Distributed deployment of CAPIF considering PLMN trust domain and 3rd party trust domain** + +The interactions between the AEF and the CAPIF core function is based on CAPIF-3e. The interactions between the API publisher function and the CAPIF core function is based on CAPIF-4e. The interactions between the API management function and the CAPIF core functions are based on CAPIF-5e. The interactions between the API invoker and the AEF are based on CAPIF-2e. The API provider domain functions may be deployed in the PLMN trust domain and the interactions of the API provider domain functions within CAPIF of the PLMN trust domain is not shown in the figure 7.3-4 and is as illustrated in figure 7.3-1. + +NOTE 2: For deployments illustrated in figure 7.3-2 and figure 7.3-3, when the API provider domain belongs to the 3rd party trust domain, the interactions between the AEF of the API provider domain and API invoker belonging to the PLMN trust domain are carried over CAPIF-2e reference point and the interactions between the entities of the API provider domain and the CAPIF core function belonging to the PLMN trust domain are carried over CAPIF-3e, CAPIF-4e and CAPIF-5e as illustrated in figure 7.3-4. + +## 7.4 Multiple CCFs deployment + +Multiple CAPIF core functions may be deployed within the PLMN trust domain as illustrated in the figure 7.4-1. For simplicity, the API invoker is not shown. + +![Diagram illustrating Multiple CCFs deployment within the PLMN trust domain. The diagram shows three CAPIF core functions (CF1, CF2, CF3) and their interactions. CAPIF core function 3 is a central repository of Service APIs. CAPIF core functions 1 and 2 interact with CAPIF core function 3 via the CAPIF-6 reference point. CAPIF core functions 1 and 2 also interact with Service APIs (API exposing function, API publishing function, and API management function) via the CAPIF-3, CAPIF-4, and CAPIF-5 reference points respectively. Each CAPIF core function has its own set of CAPIF APIs.](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +``` + +graph LR + subgraph CF3 [CAPIF core function 3] + CAPIF3_APIs((CAPIF APIs)) + CF3_Repo[Service APIs] + end + subgraph CF1 [CAPIF core function 1] + CAPIF1_APIs((CAPIF APIs)) + CF1_EF[API exposing function] + CF1_PF[API publishing function] + CF1_MF[API management function] + end + subgraph CF2 [CAPIF core function 2] + CAPIF2_APIs((CAPIF APIs)) + CF2_EF[API exposing function] + CF2_PF[API publishing function] + CF2_MF[API management function] + end + CAPIF3_APIs --- CF3_Repo + CAPIF1_APIs --- CF1_EF + CAPIF1_APIs --- CF1_PF + CAPIF1_APIs --- CF1_MF + CAPIF2_APIs --- CF2_EF + CAPIF2_APIs --- CF2_PF + CAPIF2_APIs --- CF2_MF + CF3_Repo -- CAPIF-6 --> CF1 + CF3_Repo -- CAPIF-6 --> CF2 + CF1_EF -- CAPIF-3 --> CF3_Repo + CF1_PF -- CAPIF-4 --> CF3_Repo + CF1_MF -- CAPIF-5 --> CF3_Repo + CF2_EF -- CAPIF-3 --> CF3_Repo + CF2_PF -- CAPIF-4 --> CF3_Repo + CF2_MF -- CAPIF-5 --> CF3_Repo + +``` + +Diagram illustrating Multiple CCFs deployment within the PLMN trust domain. The diagram shows three CAPIF core functions (CF1, CF2, CF3) and their interactions. CAPIF core function 3 is a central repository of Service APIs. CAPIF core functions 1 and 2 interact with CAPIF core function 3 via the CAPIF-6 reference point. CAPIF core functions 1 and 2 also interact with Service APIs (API exposing function, API publishing function, and API management function) via the CAPIF-3, CAPIF-4, and CAPIF-5 reference points respectively. Each CAPIF core function has its own set of CAPIF APIs. + +Figure 7.4-1: Multiple CCFs deployment within the PLMN trust domain + +In the distributed deployment, the CAPIF core function 1 and the CAPIF core function 2 interact with CAPIF core function 3 via CAPIF-6 reference point. The CAPIF core function 3 assumes the role of a centralized repository of service APIs in the PLMN trust domain. + +NOTE: The CAPIF core function 3 can be connected with the API exposing function(s) and API invokers. + +The CAPIF core function 1 and the CAPIF core function 2 publishes the service API provided by its connected API exposing function(s) to the CAPIF core function 3, and obtains the service API information provided by other CAPIF core function(s). + +An API invoker (not shown in the figure for simplicity) connected to the CAPIF core function 1 is able to discover and invoke the service APIs provided by the API exposing function connected to the CAPIF core function 2. + +## 7.5 RNAA deployments + +CAPIF supports RNAA and has enabled API invoker(s) to have authorized access to resources of a resource owner provided by service APIs offered by the AEF. The CCF acts as the Authorization Function and supports the authentication and authorization of the resource owner. Based on resource owner's authorization, the CCF provides the access token for a service API access to the API invoker. The API invoker performs service API invocations on the AEF by utilizing the access token. + +The API invoker may be deployed in the following ways: + +- a. API invoker may be deployed as AF on the UE (i.e. 3rd party application). +- b. API invoker may be deployed as AF on the UE supporting several other 3rd party applications deployed on the UE. +- c. API invoker may be deployed on the network as AF. + +The resource owner is considered to be connected via a UE and can interact using a Resource Owner Client deployed on the UE with the CCF acting as the Authorization Function for authentication and authorization i.e., granting permission to the API invoker to access resource(s) of the resource owner provided by the service API. + +NOTE: The details of the protocol for CAPIF supporting RNAA is specified in 3GPP TS 33.122 [12]. + +When API invoker is deployed on a UE (cases a and b), the API invoker is allowed to access the resources of the resource owner corresponding to the UE. + +## 8 Procedures and information flows + +### 8.1 Onboarding the API invoker to the CAPIF + +#### 8.1.1 General + +The procedure in this subclause corresponds to the architectural requirements for onboarding the API invoker to the CAPIF. The CAPIF enables a one time onboarding process that enrolls the API invoker as a recognized user of the CAPIF, which may be triggered by the API invoker via CAPIF-1 or CAPIF-1e, or may be based on provisioning. + +#### 8.1.2 Information flows + +##### 8.1.2.1 Onboard API invoker request + +Table 8.1.2.1-1 describes the information flow onboard API invoker request from the API invoker to the CAPIF core function. + +**Table 8.1.2.1-1: Onboard API invoker request** + +| Information element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------| +| Onboarding information | M | The information of the API invoker including enrolment details, required for onboarding | +| APIs for enrollment | O | List of APIs being enrolled for. | +| Proposed expiration time | O | Proposed expiration time for the onboarding. | + +##### 8.1.2.2 Onboard API invoker response + +Table 8.1.2.2-1 describes the information flow onboard API invoker response from the CAPIF core function to the API invoker. + +Table 8.1.2.2-1: Onboard API invoker response + +| 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, Service KPIs (optional). | +| Reason | O
(see NOTE 3) | This element indicates the reason when onboarding status is failure. | +| Expiration time | O | Indicates the expiration time of the onboarding. At expiration, CCF cancels the enrollment of the API invoker from CAPIF. If omitted, it indicates the onboarding does not expire. | +| 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. | | | + +### 8.1.3 Procedure + +Figure 8.1.3-1 illustrates the procedure for onboarding the API invoker to the CAPIF. The security aspects of this procedure are specified in subclause 6.1 of 3GPP TS 33.122 [12]. + +Pre-conditions: + +1. The API invoker is not a recognized user of the CAPIF. +2. The API invoker has visibility to APIs information (e.g., API catalogue or dashboard - central place for the API provider to manage which APIs are displayed, giving API invokers the ability to enroll for). + +![Sequence diagram illustrating the procedure for onboarding the API invoker to the CAPIF. The diagram shows four steps: 1. Onboard API invoker request from API invoker to CAPIF core function; 2. Onboarding approval from CAPIF core function to API invoker; 3. Onboard API invoker response from CAPIF core function to API invoker; 4. API invoker is onboarded (indicated by a box on the API invoker lifeline).](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant CAPIF core function + Note right of API invoker: 4. API invoker is onboarded + API invoker->>CAPIF core function: 1. Onboard API invoker request + CAPIF core function-->>API invoker: 2. Onboarding approval + CAPIF core function-->>API invoker: 3. Onboard API invoker response + +``` + +Sequence diagram illustrating the procedure for onboarding the API invoker to the CAPIF. The diagram shows four steps: 1. Onboard API invoker request from API invoker to CAPIF core function; 2. Onboarding approval from CAPIF core function to API invoker; 3. Onboard API invoker response from CAPIF core function to API invoker; 4. API invoker is onboarded (indicated by a box on the API invoker lifeline). + +Figure 8.1.3-1: Procedure for onboarding the API invoker to the CAPIF + +1. For enrollment of the API invoker to be a recognized user of the CAPIF, the API invoker triggers onboard API invoker request towards the CAPIF core function, providing the information as required for the API management. +2. The CAPIF core function begins the onboarding process by verifying whether all the necessary information has been provided to onboard the API invoker, and further initiates a grant process. Successful onboarding results in provisioning API invoker profile which includes identity for the API invoker. The authorization information and + +the list of APIs and the types of APIs that the API invoker can access subsequent to successful onboarding may also be created. + +NOTE 1: Completion of onboarding process can require explicit grant by the CAPIF administrator or the API management, which is left out-of-scope of this solution. CAPIF can handle the grant process internally without the need of explicit grant by the CAPIF administrator. + +NOTE 2: The API invoker profile consists of at least the identity information for the API invoker, information required for the authentication and authorization by the CAPIF and the CAPIF identity information. + +3. If the API invoker has triggered the onboard API invoker request and is granted permission, the onboard API invoker response provides success indication including 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. +4. As a result of successful onboarding process, the CAPIF core function is able to authenticate and authorize the API invoker. + +## 8.2 Offboarding the API invoker from the CAPIF + +### 8.2.1 General + +This subclause defines the procedure for offboarding the API invoker from the CAPIF. The offboarding process makes the API invoker no longer a recognized user of the CAPIF. The procedure is triggered by the API invoker over CAPIF-1 or CAPIF-1e. + +### 8.2.2 Information flows + +This subclause describes the information flows for the API invoker offboarding. + +#### 8.2.2.1 Offboard API invoker request + +Table 8.2.2.1-1 describes the information flow offboard API invoker request from the API invoker to the CAPIF core function. + +**Table 8.2.2.1-1: Offboard API invoker request** + +| Information element | Status | Description | +|----------------------------------|--------|----------------------------------------------------------------| +| API invoker identity information | M | Identity information of the API invoker requesting offboarding | +| Reason | O | Indicate the reason of offboarding | + +#### 8.2.2.2 Offboard API invoker response + +Table 8.2.2.2-1 describes the information flow offboard API invoker response from the CAPIF core function to the API invoker. + +**Table 8.2.2.2-1: Offboard API invoker response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| Result | M | Indicates the success or failure of the offboarding operation | + +### 8.2.3 Procedure + +Figure 8.2.3-1 illustrates the procedure for offboarding the API invoker from the CAPIF, triggered by the API invoker. The security aspects of this procedure are specified in subclause 6.8 of 3GPP TS 33.122 [12]. + +Pre-conditions: + +1. The API invoker has been onboarded as a recognized user of the CAPIF. + +![Sequence diagram showing the procedure for offboarding the API invoker from the CAPIF. The diagram involves two lifelines: API invoker and CAPIF core function. The sequence of messages is: 1. Offboard API invoker request from API invoker to CAPIF core function; 2. Cancel the API invoker enrollment from CAPIF (shown in a box); 3. Offboard API invoker response from CAPIF core function to API invoker.](e05122559f56af5699789b7118d8fe87_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF core function + Note right of CAPIF core function: 2. Cancel the API invoker enrollment from CAPIF + API invoker->>CAPIF core function: 1. Offboard API invoker request + CAPIF core function-->>API invoker: 3. Offboard API invoker response +``` + +Sequence diagram showing the procedure for offboarding the API invoker from the CAPIF. The diagram involves two lifelines: API invoker and CAPIF core function. The sequence of messages is: 1. Offboard API invoker request from API invoker to CAPIF core function; 2. Cancel the API invoker enrollment from CAPIF (shown in a box); 3. Offboard API invoker response from CAPIF core function to API invoker. + +**Figure 8.2.3-1: Procedure for offboarding the API invoker from the CAPIF** + +1. The API invoker triggers offboard API invoker request to the CAPIF core function, providing the information as required for the API management. +2. The CAPIF core function cancels the enrollment of the API invoker from CAPIF. The API invoker ceases to be a recognized user of the CAPIF. All the authorizations corresponding to the API invoker are revoked from CAPIF. Optionally, the information of the API invoker may be retained at the CAPIF core function as per the operator policy. + +NOTE: Completion of offboarding process can require explicit notification to the CAPIF administrator or the API management, which is left out-of-scope of this solution. CAPIF can handle the de-provisioning process internally without the need of explicit grant by the CAPIF administrator. + +3. The CAPIF core function returns the offboard API invoker response providing successful offboarding indication. + +## 8.3 Publish service APIs + +### 8.3.1 General + +The CAPIF supports publishing service APIs by the API provider. The API publishing function can be within PLMN trust domain or within 3rd party trust domain. + +### 8.3.2 Information flows + +#### 8.3.2.1 Service API publish request + +Table 8.3.2.1-1 describes the information flow service API publish request from the API publishing function to the CAPIF core function. + +**Table 8.3.2.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, API provider name (optional), List of public IP ranges of UEs (optional), 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, Service KPIs (optional). | +| 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. | | | + +The Service KPIs is defined as below: + +**Table 8.3.2.1-2: 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. | + +### 8.3.2.2 Service API publish response + +Table 8.3.2.2-1 describes the information flow service API publish response from the CAPIF core function to the API publishing function. + +**Table 8.3.2.2-1: Service API publish response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of publishing the service API information | +| Service API published information reference | O (see NOTE) | The information which can be used for referencing the information (set) about the published service API by the API publishing function. | +| Service API information | O (see NOTE) | The authorized service API information. | +| NOTE: This information element is included when the Result indicates success. | | | + +### 8.3.3 Procedure + +Figure 8.3.3-1 illustrates the procedure for publishing the service APIs. The service API publish mechanism is supported by the CAPIF core function. + +Pre-conditions: + +1. Authorization details of the APF are available with the CAPIF core function. +2. API invokers may have subscribed with the CAPIF core function to obtain new service API information. + +![Sequence diagram illustrating the procedure for publishing service APIs. The diagram shows two lifelines: 'API publishing function' and 'CAPIF core function'. The sequence of messages is: 1. Service API publish request from API publishing function to CAPIF core function; 2. Store API information (internal message within CAPIF core function); 3. Service API publish response from CAPIF core function to API publishing function.](24a89bcaba787f2bc1721356480a4a01_img.jpg) + +``` +sequenceDiagram + participant APF as API publishing function + participant CCF as CAPIF core function + Note right of CCF: 2.Store API information + APF->>CCF: 1.Service API publish request + CCF-->>APF: 3.Service API publish response +``` + +Sequence diagram illustrating the procedure for publishing service APIs. The diagram shows two lifelines: 'API publishing function' and 'CAPIF core function'. The sequence of messages is: 1. Service API publish request from API publishing function to CAPIF core function; 2. Store API information (internal message within CAPIF core function); 3. Service API publish response from CAPIF core function to API publishing function. + +**Figure 8.3.3-1: Publish service APIs** + +1. The API publishing function sends a service API publish request to the CAPIF core function, with the details of the service API. If the service API is to be shared to other CAPIF core functions, the shareable information and the CAPIF provider domain information are included. +2. Upon receiving the service API publish request, the CAPIF core function checks whether the API publishing function is authorized to publish service APIs. If the check is successful, the service API information provided by the API publishing function is stored at the CAPIF core function (API registry). +3. The CAPIF core function provides a service API publish response to the API publishing function indicating success or failure result and triggers notifications to subscribed API invokers as described in subclause 8.8.4. + +## 8.4 Unpublish service APIs + +### 8.4.1 General + +The CAPIF supports unpublishing service APIs by the API provider. Once the service API information is unpublished, it is no more available to be discovered by API invokers. The API publishing function can be within PLMN trust domain or within 3rd party trust domain. + +### 8.4.2 Information flows + +#### 8.4.2.1 Service API unpublish request + +Table 8.4.2.1-1 describes the information flow service API unpublish request from the API publishing function to the CAPIF core function. + +**Table 8.4.2.1-1: Service API unpublish request** + +| Information element | Status | Description | +|---------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API publisher information | M | The information of the API publisher may include identity, authentication and authorization information | +| Service API published information reference | M | The information provided by the CAPIF core function which can be for referencing the information (set) about the published service API by the API publishing function. | + +#### 8.4.2.2 Service API unpublish response + +Table 8.4.2.2-1 describes the information flow service API unpublish response from the CAPIF core function to the API publishing function. + +**Table 8.4.2.2-1: Service API unpublish response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of unpublishing the service API information | + +### 8.4.3 Procedure + +Figure 8.4.3-1 illustrates the procedure for unpublishing the service APIs. The service API unpublish mechanism is supported by the CAPIF core function. + +Pre-conditions: + +1. Authorization details of the APF are available with the CAPIF core function. +2. API invokers may have subscribed with the CAPIF core function to obtain notification regarding service API unpublish. + +![Sequence diagram illustrating the procedure for unpublishing service APIs. The diagram shows three steps: 1. Service API unpublish request from API publishing function to CAPIF core function; 2. Remove API information within CAPIF core function; 3. Service API unpublish response from CAPIF core function to API publishing function.](d6015fcef74bce83d04acd2e17b4fc15_img.jpg) + +``` + +sequenceDiagram + participant APF as API publishing function + participant CCF as CAPIF core function + Note right of CCF: 2.Remove API information + APF->>CCF: 1.Service API unpublish request + CCF-->>APF: 3.Service API unpublish response + +``` + +Sequence diagram illustrating the procedure for unpublishing service APIs. The diagram shows three steps: 1. Service API unpublish request from API publishing function to CAPIF core function; 2. Remove API information within CAPIF core function; 3. Service API unpublish response from CAPIF core function to API publishing function. + +**Figure 8.4.3-1: Unpublish service APIs** + +1. The API publishing function sends a service API unpublish request to the CAPIF core function, with service API published information reference provided by the CAPIF core function when the service API was published. +2. Upon receiving the service API unpublish request, the CAPIF core function checks whether the API publishing function is authorized to unpublish service APIs. If the check is successful, the service API information provided by the API publishing function is removed at the CAPIF core function (API registry). +3. The CAPIF core function provides a service API unpublish response to the API publishing function and triggers notifications to subscribed API invokers as described in subclause 8.8.4. + +## 8.5 Retrieve service APIs + +### 8.5.1 General + +The CAPIF supports retrieving the published service APIs information by the API provider. The API publishing function can be within PLMN trust domain or within 3rd party trust domain. + +### 8.5.2 Information flows + +#### 8.5.2.1 Service API get request + +Table 8.5.2.1-1 describes the information flow service API get request from the API publishing function to the CAPIF core function. + +**Table 8.5.2.1-1: Service API get request** + +| Information element | Status | Description | +|---------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API publisher information | M | The information of the API publisher may include identity, authentication and authorization information | +| Service API published information reference | M | The information provided by the CAPIF core function which can be for referencing the information (set) about the published service API by the API publishing function. | + +#### 8.5.2.2 Service API get response + +Table 8.5.2.2-1 describes the information flow service API get response from the CAPIF core function to the API publishing function. + +**Table 8.5.2.2-1: Service API get response** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of retrieving the service API information | +| Service API information | O (see NOTE) | 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. | +| NOTE: Shall be present if the Result information element indicates that the service API get request is successful. Otherwise service API information shall not be present. | | | + +### 8.5.3 Procedure + +Figure 8.5.3-1 illustrates the procedure for retrieving the service APIs. The service API retrieval mechanism is supported by the CAPIF core function. + +Pre-condition: + +1. Authorization details of the APF are available with the CAPIF core function. + +![Sequence diagram for Retrieve service APIs](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` +sequenceDiagram + participant API publishing function + participant CAPIF core function + Note right of CAPIF core function: 2.Retrieve API information + API publishing function->>CAPIF core function: 1.Service API get request + CAPIF core function-->>API publishing function: 3.Service API get response +``` + +The diagram illustrates a sequence of interactions between two entities: 'API publishing function' and 'CAPIF core function'. The sequence starts with the 'API publishing function' sending a '1.Service API get request' to the 'CAPIF core function'. The 'CAPIF core function' then performs an internal action labeled '2.Retrieve API information' and sends a '3.Service API get response' back to the 'API publishing function'. + +Sequence diagram for Retrieve service APIs + +**Figure 8.5.3-1: Retrieve service APIs** + +1. The API publishing function sends a service API get request to the CAPIF core function, with service API published information reference provided by the CAPIF core function when the service API was published. +2. Upon receiving the service API get request, the CAPIF core function checks whether the API publishing function is authorized to get published service APIs information. If the check is successful, the corresponding service API information is retrieved from the CAPIF core function (API registry). +3. The CAPIF core function provides a service API get response to the API publishing function which includes the service API information. + +## 8.6 Update service APIs + +### 8.6.1 General + +The CAPIF core function allows the service API provider to update the information related to the published service API, e.g. a change in the characteristics of the service API. This procedure is initiated by the API publishing function to the CAPIF core function. The API publishing function can be within PLMN trust domain or within 3rd party trust domain. + +### 8.6.2 Information flows + +#### 8.6.2.1 Service API update request + +Table 8.6.2.1-1 describes the information flow service API update request from the API publishing function to the CAPIF core function. + +**Table 8.6.2.1-1: Service API update request** + +| Information element | Status | Description | +|---------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API publisher information | M | The information of the API publisher may include identity, authentication and authorization information | +| Service API published information reference | M | The information (set) provided by the CAPIF core function about the published service API which can be used for reference by the API publishing function. | +| 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, List of public IP ranges of UEs (optional), Serving Area Information (optional), AEF location (optional), interface details (e.g. IP address, port number, URI), protocols, version numbers, and data format which is required to replace the existing service API information | +| Reason | O | The reason of the update (e.g. change log) | + +NOTE: How to monitor service API status when the APF is unable to update service API status is not specified in this release. + +## 8.6.2.2 Service API update response + +Table 8.6.2.2-1 describes the information flow service API update response from the CAPIF core function to the API publishing function. + +**Table 8.6.2.2-1: Service API update response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of updating the service API information | +| Service API information | O | The authorized service API information during update, applicable when the update result is success. | + +## 8.6.3 Procedure + +Figure 8.6.3-1 illustrates the procedure for updating the published service APIs information. The service API update mechanism is supported by the CAPIF core function. + +Pre-conditions: + +1. Authorization details of the APF are available with the CAPIF core function. +2. API invokers may have subscribed with the CAPIF core function to obtain notification regarding update to service API information. + +![Sequence diagram for Figure 8.6.3-1: Update service APIs. The diagram shows two lifelines: 'API publishing function' and 'CAPIF core function'. The sequence of messages is: 1. Service API update request from API publishing function to CAPIF core function; 2. Update and store API information (internal message to CAPIF core function); 3. Service API update response from CAPIF core function to API publishing function.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant API publishing function + participant CAPIF core function + Note right of CAPIF core function: 2. Update and store API information + API publishing function->>CAPIF core function: 1. Service API update request + CAPIF core function-->>API publishing function: 3. Service API update response + +``` + +Sequence diagram for Figure 8.6.3-1: Update service APIs. The diagram shows two lifelines: 'API publishing function' and 'CAPIF core function'. The sequence of messages is: 1. Service API update request from API publishing function to CAPIF core function; 2. Update and store API information (internal message to CAPIF core function); 3. Service API update response from CAPIF core function to API publishing function. + +**Figure 8.6.3-1: Update service APIs** + +1. The API publishing function sends a service API update request to the CAPIF core function, which includes the service API published information reference provided by the CAPIF core function when the service API was published and the new service API information which is to be updated. +2. Upon receiving the service API update request, the CAPIF core function checks whether the API publishing function is authorized to update the published service APIs information. If the check is successful, the service API information provided by the API publishing function is updated at the CAPIF core function (API registry). +3. The CAPIF core function provides a service API update response to the API publishing function and triggers notifications to subscribed API invokers as described in subclause 8.8.4. + +## 8.7 Discover service APIs + +### 8.7.1 General + +The following procedure in this subclause corresponds to the architectural requirements on discover service APIs. + +### 8.7.2 Information flows + +#### 8.7.2.1 Service API discover request + +Table 8.7.2.1-1 describes the information flow service API discover request from the API invoker to the CAPIF core function. + +**Table 8.7.2.1-1: Service API discover request** + +| 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), required API provider name (optional), UE IP address (optional), interfaces, protocols), Service KPIs (optional) (see NOTE) | +| NOTE: It should be possible to discover all the service APIs. | | | + +#### 8.7.2.2 Service API discover response + +Table 8.7.2.2-1 describes the information flow service API discover response from the CAPIF core function to the API invoker. + +Table 8.7.2.2-1: Service API discover response + +| 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, Service KPIs (optional). | +| 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. | | | + +### 8.7.3 Procedure + +Figure 8.7.3-1 illustrates the procedure for discover service APIs. + +The service API discovery mechanism is supported by the CAPIF core function. + +Pre-conditions: + +1. The API invoker is onboarded and has received an API invoker identity. +2. The CAPIF core function is configured with a discovery policy information (e.g. to restrict discovery to category of APIs) for API invoker(s). + +![Sequence diagram illustrating the procedure for discover service APIs. The diagram shows two lifelines: API invoker and CAPIF core function. The sequence of messages is: 1. Service API discover request from API invoker to CAPIF core function; 2. Retrieve service API(s) information from CAPIF core function to itself; 3. Service API discover response from CAPIF core function to API invoker.](042af54276c75e7b7b48a3af1f0a84e5_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant CAPIF core function + Note right of CAPIF core function: 2.Retrieve service API(s) information + API invoker->>CAPIF core function: 1.Service API discover request + CAPIF core function->>CAPIF core function: 2.Retrieve service API(s) information + CAPIF core function->>API invoker: 3.Service API discover response + +``` + +Sequence diagram illustrating the procedure for discover service APIs. The diagram shows two lifelines: API invoker and CAPIF core function. The sequence of messages is: 1. Service API discover request from API invoker to CAPIF core function; 2. Retrieve service API(s) information from CAPIF core function to itself; 3. Service API discover response from CAPIF core function to API invoker. + +Figure 8.7.3-1: Discover service APIs + +1. The API invoker sends a service API discover request to the CAPIF core function. It includes the API invoker identity, and may include query information. +2. Upon receiving the service API discover request, the CAPIF core function verifies the identity of the API invoker (via authentication). The CAPIF core function retrieves the stored service API(s) information from the CAPIF core function (API registry) as per the query information in the service API discover request. Further, the CAPIF core function applies the discovery policy and performs filtering of service APIs information retrieved from the CAPIF core function. +3. The CAPIF core function sends a service API discover response to the API invoker with the list of service API information for which the API invoker has the required authorization. + +## 8.8 Subscription, unsubscription and notifications for the CAPIF events + +### 8.8.1 General + +The CAPIF core function enables the subscribing entity (i.e. the API invoker, the API exposing function, the API publishing function, the API management function) to subscribe to and unsubscribe from the CAPIF events such as availability events of service APIs, change in service API information, monitoring service API invocations, API invoker onboarding events, etc. The subscription, unsubscription and notification for the CAPIF events are enabled on the following CAPIF reference points: + +- CAPIF-1 or CAPIF-1e: the API invoker can subscribe to and unsubscribe from CAPIF events and receive notifications from the CAPIF core function; +- CAPIF-3 or CAPIF-3e: the AEF can subscribe to and unsubscribe from CAPIF events and receive notifications from the CAPIF core function; +- CAPIF-4 or CAPIF-4e: the API publishing function can subscribe to and unsubscribe from CAPIF events and receive notifications from the CAPIF core function; and +- CAPIF-5 or CAPIF-5e: the API management function can subscribe to and unsubscribe from CAPIF events and receive notifications from the CAPIF core function. + +NOTE: Support for subscriptions and notifications can also be part of the actual service APIs. That type of subscriptions and notifications is not covered by the provisions in this clause. + +### 8.8.2 Information flows + +#### 8.8.2.1 Event subscription request + +Table 8.8.2.1-1 describes the information flow for event subscription request from the subscribing entity to the CAPIF core function. + +**Table 8.8.2.1-1: Event subscription request** + +| Information element | Status | Description | +|------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identity information | M | The information to determine the identity of the subscribing entity | +| Event criteria | M | The event criteria include event type information like failure API invocation event, new API available event, API version change event, API location change event, etc and other query information like service API identifier, service API name, etc. | +| Notification reception information | O | The information of the subscribing entity for receiving the notifications for the event. | + +#### 8.8.2.2 Event subscription response + +Table 8.8.2.2-1 describes the information flow for event subscription response from the CAPIF core function to the subscribing entity. + +**Table 8.8.2.2-1: Event subscription response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the event subscription operation | +| Subscription identifier | O
(see NOTE) | The unique identifier for the event subscription. | +| NOTE: Shall be present if the Result information element indicates that the event subscription operation is successful. Otherwise subscription identifier shall not be present. | | | + +### 8.8.2.3 Event notification + +Table 8.8.2.3-1 describes the information flow for event notification from the CAPIF core function to the subscribing entity. A notification about an event is sent to a subscribing entity if the event criteria in the related subscription match the corresponding attributes of the event content. + +**Table 8.8.2.3-1: Event notification** + +| Information element | Status | Description | +|---------------------------|--------|--------------------------------------------------------------------------------------------| +| Subscription identifier | M | The unique identifier of the event subscription | +| Event identifier | M | The unique identifier for the event. For the list of events, refer subclause 8.8.6 | +| Event related information | M | The event related information (e.g. time at which the event originated, location of event) | +| Event content | M | The content of the event information. | + +### 8.8.2.4 Event notification acknowledgement + +Table 8.8.2.4-1 describes the information flow event notification acknowledgement from the subscribing entity to the CAPIF core function. + +**Table 8.8.2.4-1: Event notification acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| Acknowledgement | M | Acknowledgement for the event notification received. | + +### 8.8.2.5 Event unsubscription request + +Table 8.8.2.5-1 describes the information flow for event unsubscription request from the subscribing entity to the CAPIF core function. + +**Table 8.8.2.5-1: Event unsubscription request** + +| Information element | Status | Description | +|-------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Identity information | M | The information to determine the identity of the subscribing entity | +| Subscription identifier | M | The unique identifier for the event subscription that was provided to the subscribing entity during the CAPIF event subscription operation. | + +### 8.8.2.6 Event unsubscription response + +Table 8.8.2.6-1 describes the information flow for event unsubscription response from the CAPIF core function to the subscribing entity. + +**Table 8.8.2.6-1: Event unsubscription response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the event unsubscription operation | + +### 8.8.2.7 Event subscription update request + +Table 8.8.2.7-1 describes the information flow for event subscription update request from the subscribing entity to the CAPIF core function. + +**Table 8.8.2.7-1: Event subscription update request** + +| Information element | Status | Description | +|--------------------------------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Identity information | M | The information to determine the identity of the subscribing entity | +| Subscription identifier | M | The unique identifier for the event subscription that was provided to the subscribing entity during the CAPIF event subscription operation. | +| Event criteria changes | O (NOTE) | Updates to the event criteria which are defined in clause 8.8.2.1 | +| Notification reception information changes | O (NOTE) | Updates to the information of the subscribing entity for receiving the notifications for the event | +| NOTE: At least one of these information elements shall be present. | | | + +### 8.8.2.8 Event subscription update response + +Table 8.8.2.8-1 describes the information flow for event subscription update response from the CAPIF core function to the subscribing entity. + +**Table 8.8.2.8-1: Event subscription update response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the event subscription update operation | + +## 8.8.3 Procedure for CAPIF event subscription + +Figure 8.8.3-1 illustrates the procedure for CAPIF events subscription. + +Pre-conditions: + +1. The subscribing entity has the authorization to subscribe for the CAPIF events. + +![Sequence diagram for CAPIF event subscription procedure](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` +sequenceDiagram + participant SE as Subscribing entity + participant CF as CAPIF core function + Note right of CF: 2. Check authorization for subscription + Note right of CF: 3. Store subscription information + SE->>CF: 1. Event subscription request + CF-->>SE: 4. Event subscription response +``` + +The diagram illustrates the procedure for CAPIF event subscription. It features two lifelines: 'Subscribing entity' and 'CAPIF core function'. The sequence of interactions is as follows: 1. The 'Subscribing entity' sends an 'Event subscription request' to the 'CAPIF core function'. 2. The 'CAPIF core function' performs an internal step 'Check authorization for subscription'. 3. The 'CAPIF core function' performs an internal step 'Store subscription information'. 4. The 'CAPIF core function' sends an 'Event subscription response' back to the 'Subscribing entity'. + +Sequence diagram for CAPIF event subscription procedure + +**Figure 8.8.3-1: Procedure for CAPIF event subscription** + +1. The subscribing entity sends an event subscription request to the CAPIF core function in order to receive notification of events. +2. Upon receiving the event subscription request from the subscribing entity, the CAPIF core function checks for the relevant authorization for the event subscription. +3. If the authorization is successful, the CAPIF core function stores the subscription information. +4. The CAPIF core function sends an event subscription response indicating successful operation. + +## 8.8.4 Procedure for CAPIF event notifications + +Figure 8.8.4-1 illustrates the procedure for CAPIF event notifications. + +Pre-conditions: + +1. The subscription procedure as illustrated in figure 8.8.3-1 is performed by the subscribing entity. + +![Sequence diagram for CAPIF event notifications procedure](e3eebf9854831ba50eca8b26c468f65e_img.jpg) + +``` +sequenceDiagram + participant SE1 as Subscribing entity + participant CF as CAPIF core function + participant SE2 as Subscribing entity + Note right of CF: 1. Event is generated + Note right of CF: 2. Retrieve application subscriptions + CF->>SE1: 3. Event notification + CF->>SE2: 3. Event notification + SE1-->>CF: 4. Event notification acknowledgement + SE2-->>CF: 4. Event notification acknowledgement +``` + +The diagram illustrates the procedure for CAPIF event notifications. It features three lifelines: 'Subscribing entity', 'CAPIF core function', and 'Subscribing entity'. The sequence of interactions is as follows: 1. The 'CAPIF core function' performs an internal step 'Event is generated'. 2. The 'CAPIF core function' performs an internal step 'Retrieve application subscriptions'. 3. The 'CAPIF core function' sends an 'Event notification' to both 'Subscribing entity' lifelines. 4. Both 'Subscribing entity' lifelines send an 'Event notification acknowledgement' back to the 'CAPIF core function'. + +Sequence diagram for CAPIF event notifications procedure + +**Figure 8.8.4-1: Procedure for CAPIF event notifications** + +1. The CAPIF core function generates events to be consumed by the subscribing entity(s). +2. For the generated event, the CAPIF core function retrieves the list of corresponding subscriptions. + +3. The CAPIF core function sends event notifications to all the subscribing entity(s) 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 CAPIF core function to send event notifications to the subscribing entity. +4. The subscribing entity sends an event notification acknowledgement to the CAPIF core function for the event notification received. + +## 8.8.5 Procedure for CAPIF event unsubscription + +Figure 8.8.5-1 illustrates the procedure for CAPIF event unsubscription. + +Pre-condition: + +1. The subscribing entity has subscribed to the CAPIF events. + +![Sequence diagram for CAPIF event unsubscription procedure](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +``` +sequenceDiagram + participant SE as Subscribing entity + participant CCF as CAPIF core function + Note right of CCF: 2. Check if CAPIF entity has authorization and a corresponding subscription + Note right of CCF: 3. Remove subscription information + SE->>CCF: 1. Event unsubscription request + CCF-->>SE: 4. Event unsubscription response +``` + +The diagram is a sequence diagram showing the interaction between a 'Subscribing entity' and a 'CAPIF core function'. The process consists of four steps: 1. The Subscribing entity sends an 'Event unsubscription request' to the CAPIF core function. 2. The CAPIF core function checks if it has authorization and a corresponding subscription (shown in a box). 3. The CAPIF core function removes the subscription information (shown in a box). 4. The CAPIF core function sends an 'Event unsubscription response' back to the Subscribing entity. + +Sequence diagram for CAPIF event unsubscription procedure + +**Figure 8.8.5-1: Procedure for CAPIF event unsubscription** + +1. The subscribing entity sends an event unsubscription request to the CAPIF core function with the information of the subscribed CAPIF event. +2. Upon receiving the event unsubscription request from the subscribing entity, the CAPIF core function checks for the event subscription corresponding to the subscribing entity and further checks if the subscribing entity is authorized to unsubscribe from the CAPIF event. +3. If the event subscription information corresponding to the subscribing entity is available and the subscribing entity is authorized to unsubscribe for the CAPIF event, the CAPIF core function removes the subscription information. +4. The CAPIF core function sends an event unsubscription response indicating successful operation. + +## 8.8.5a Procedure for CAPIF event subscription update + +Figure 8.8.5a-1 illustrates the procedure for CAPIF events subscription update. + +Pre-conditions: + +1. The subscribing entity has the authorization to update subscriptions for CAPIF events. +2. The subscribing entity has created subscriptions for CAPIF events. + +![Sequence diagram showing the procedure for CAPIF event subscription. A 'Subscribing entity' sends a '1. Event subscription update request' to a 'CAPIF core function'. The CAPIF core function then performs two internal steps: '2. Check authorization for subscription update' and '3. Modify stored subscription information'. Finally, it sends a '4. Event subscription update response' back to the subscribing entity.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant SE as Subscribing entity + participant CCF as CAPIF core function + Note right of CCF: 2. Check authorization for subscription update + Note right of CCF: 3. Modify stored subscription information + SE->>CCF: 1. Event subscription update request + CCF-->>SE: 4. Event subscription update response + +``` + +Sequence diagram showing the procedure for CAPIF event subscription. A 'Subscribing entity' sends a '1. Event subscription update request' to a 'CAPIF core function'. The CAPIF core function then performs two internal steps: '2. Check authorization for subscription update' and '3. Modify stored subscription information'. Finally, it sends a '4. Event subscription update response' back to the subscribing entity. + +**Figure 8.8.5a-1: Procedure for CAPIF event subscription** + +1. The subscribing entity sends an event subscription update request to the CAPIF core function in order update a previous subscription to receive notification of events. +2. Upon receiving the event subscription update request from the subscribing entity, the CAPIF core function checks for the relevant authorization for the event subscription update. +3. If the authorization is successful, the CAPIF core function updates the subscription information. +4. The CAPIF core function sends an event subscription update response indicating successful operation. + +## 8.8.6 List of CAPIF events + +Table 8.8.6-1 provides a non-exhaustive list of CAPIF events. + +**Table 8.8.6-1: List of CAPIF events** + +| Events | Events Description | +|------------------------------------|--------------------------------------------------------------------------| +| Availability of service APIs | Availability events of service APIs (e.g. active, inactive) | +| Service API updated | Events related to change in service API information | +| Monitoring service API invocations | Events corresponding to service API invocations | +| API invoker status | Events related to API invoker status in CAPIF (onboarded, offboarded) | +| API topology hiding status | Events related to API topology hiding status in CAPIF (created, revoked) | +| System related events | Alarm events providing fault information | +| Performance related events | Events related to system load conditions | + +## 8.9 Revoking subscription of the CAPIF events + +### 8.9.1 General + +The CAPIF core function allows to revoke subscription of CAPIF events for the subscribing entity related to the service API changes, such as availability events of service APIs, change in service API information, monitoring service API invocations, API invoker onboarding events, etc. This procedure is initiated by the CAPIF core function. + +NOTE: It is optional to trigger notification by the CAPIF core function for revocation of subscription for CAPIF event(s). + +## 8.9.2 Information flows + +This subclause describes the information flows for CAPIF event subscription revocation. + +### 8.9.2.1 Subscription revoke notification + +Table 8.9.2.1-1 describes the information flow for subscription revoke notification from the CAPIF core function to the subscribing entity. + +**Table 8.9.2.1-1: Subscription revoke notification** + +| Information element | Status | Description | +|-------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Identity information | M | The information to determine the identity of the subscribing entity | +| Subscription identifier | M | The unique identifier for the event subscription that was provided to the subscribing entity during the CAPIF event subscription operation. | +| Reason | O | Indicate the reason of subscription revocation | + +### 8.9.2.2 Subscription revoke notification acknowledgement + +Table 8.9.2.2-1 describes the information flow for subscription revoke notification acknowledgement from the subscribing entity to the CAPIF core function. + +**Table 8.9.2.2-1: Subscription revoke notification acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| Acknowledgement | M | The acknowledgement for the received notification. | + +## 8.9.3 Procedure + +Figure 8.9.3-1 illustrates the procedure for subscription revocation, triggered by the CAPIF core function. + +Pre-conditions: + +1. The subscribing entity has previously subscribed to CAPIF event(s) to the CAPIF core function. + +![Sequence diagram illustrating the procedure for revoking subscription of the CAPIF events. The diagram shows two lifelines: 'Subscribing entity' and 'CAPIF core function'. The process starts with a decision box '1. Decision to revoke subscription for the subscribing entity' within the CAPIF core function lifeline. This is followed by a message '2. Subscription revoke notification' from the CAPIF core function to the Subscribing entity. Finally, a message '3. Subscription revoke notification acknowledgement' is sent from the Subscribing entity back to the CAPIF core function.](926e16abf793df297dae7b334069f69b_img.jpg) + +``` + +sequenceDiagram + participant SE as Subscribing entity + participant CCF as CAPIF core function + Note right of CCF: 1. Decision to revoke subscription for the subscribing entity + CCF->>SE: 2. Subscription revoke notification + SE->>CCF: 3. Subscription revoke notification acknowledgement + +``` + +Sequence diagram illustrating the procedure for revoking subscription of the CAPIF events. The diagram shows two lifelines: 'Subscribing entity' and 'CAPIF core function'. The process starts with a decision box '1. Decision to revoke subscription for the subscribing entity' within the CAPIF core function lifeline. This is followed by a message '2. Subscription revoke notification' from the CAPIF core function to the Subscribing entity. Finally, a message '3. Subscription revoke notification acknowledgement' is sent from the Subscribing entity back to the CAPIF core function. + +**Figure 8.9.3-1: Procedure for revoking subscription of the CAPIF events** + +1. The CAPIF core function decides to revoke subscription of CAPIF event(s) for the subscribing entity. +2. The CAPIF core function sends subscription revoke notification to the subscribing entity. +3. The subscribing entity provides a subscription revoke notification acknowledgement to the CAPIF core function. + +## 8.10 Authentication between the API invoker and the CAPIF core function + +### 8.10.1 General + +The procedure in this subclause corresponds to the architectural requirements for authentication between the API invoker and the CAPIF core function. + +### 8.10.2 Information flows + +NOTE: The security aspects of this procedure are specified in subclause 6.2 and subclause 6.3.1 of 3GPP TS 33.122 [12]. + +### 8.10.3 Procedure + +Figure 8.10.3-1 illustrates the procedure for authentication between the API invoker and the CAPIF core function. + +Pre-conditions: + +1. The API invoker is onboarded with the CAPIF core function and the API invoker profile is created. + +![Sequence diagram illustrating the authentication procedure between the API invoker and the CAPIF core function.](3bd9d303382ff0566369ed81a9226ade_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF core function + Note right of CAPIF core function: 2. Identity verification and authentication + API invoker->>CAPIF core function: 1. Authentication request + CAPIF core function-->>API invoker: 3. Authentication response +``` + +The diagram is a sequence diagram with two lifelines: 'API invoker' on the left and 'CAPIF core function' on the right. The interaction consists of three steps: 1. The API invoker sends an 'Authentication request' to the CAPIF core function. 2. The CAPIF core function performs 'Identity verification and authentication', indicated by a self-call message. 3. The CAPIF core function sends an 'Authentication response' back to the API invoker. + +Sequence diagram illustrating the authentication procedure between the API invoker and the CAPIF core function. + +**Figure 8.10.3-1: Procedure for authentication between the API invoker and the CAPIF core function** + +1. The API invoker triggers authentication to the CAPIF core function, including the identity confirmed after successful onboarding. +2. Upon receiving the authentication request, the CAPIF core function verifies the identity with the API invoker profile and authenticates the API invoker. + +NOTE 1: The authentication process is specified in subclause 6.2 and subclause 6.3.1 of 3GPP TS 33.122 [12]. + +3. The CAPIF core function returns the result of the API invoker identity verification in the authentication response. + +NOTE 2: The CAPIF core function can share the information required for authentication of the API invoker at the AEF. + +## 8.11 API invoker obtaining authorization to access service API + +### 8.11.1 General + +The API invoker requires to execute this procedure when it needs to obtain or re-obtain (e.g. upon expiry of the authorization information) the authorization to access the service API. Once the API invoker receives the authorization to access the service API, the API invoker can perform one or multiple service API invocations as per the permission limit. This procedure may be performed during the API invoker onboarding process. + +### 8.11.2 Information flows + +NOTE: The security aspects of this procedure are specified in subclause 6.5.2.3 of 3GPP TS 33.122 [12]. + +### 8.11.3 Procedure + +Figure 8.11.3-1 illustrates the procedure for obtaining authorization to access the service API. + +Pre-condition: + +1. The API invoker is onboarded and has received an API invoker identity. + +![Sequence diagram illustrating the procedure for the API invoker obtaining authorization for service API access. The diagram shows three steps: 1. Obtain service API authorization request (API invoker to CAPIF core function), 2. Validate and authenticate the API invoker (internal to CAPIF core function), and 3. Obtain service API authorization response (CAPIF core function to API invoker).](ccf6853c7291703cb04568057fef5849_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF core function + Note right of CAPIF core function: 2.Validate and authenticate the API invoker + API invoker->>CAPIF core function: 1. Obtain service API authorization request + CAPIF core function-->>API invoker: 3. Obtain service API authorization response +``` + +Sequence diagram illustrating the procedure for the API invoker obtaining authorization for service API access. The diagram shows three steps: 1. Obtain service API authorization request (API invoker to CAPIF core function), 2. Validate and authenticate the API invoker (internal to CAPIF core function), and 3. Obtain service API authorization response (CAPIF core function to API invoker). + +**Figure 8.11.3-1: Procedure for the API invoker obtaining authorization for service API access** + +1. The API invoker sends an obtain service API authorization request to the CAPIF core function for obtaining permission to access the service API by including the API invoker identity information and any information required for authentication of the API invoker. +2. The CAPIF core function validates the authentication of the API invoker (using authentication information) and checks whether the API invoker is permitted to access the requested service API. + +NOTE 1: The authentication process is specified in subclause 6.5.2.3 of 3GPP TS 33.122 [12]. + +3. Based on the API invoker's subscription information the authorization information to access the service APIs is sent to the API invoker in the obtain service API authorization response. + +NOTE 2: The mechanism for distribution of the authorization information for the API invoker to the API exposing function is specified in subclause 6.5.2.3 of 3GPP TS 33.122 [12]. + +## 8.12 AEF obtaining service API access control policy + +### 8.12.1 General + +The CAPIF core function is the central repository of all the policies related to service APIs. The AEF executes this procedure when it needs to obtain the policy to perform access control on the service API invocations (e.g. when policy + +for performing access control on service API is unavailable at the AEF). The AEF can be within PLMN trust domain or within 3rd party trust domain. + +## 8.12.2 Information flows + +### 8.12.2.1 Obtain access control policy request + +Table 8.12.2.1-1 describes the information flow obtain access control policy request from the AEF to the CAPIF core function. + +**Table 8.12.2.1-1: Obtain access control policy request** + +| Information element | Status | Description | +|----------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| Identity information | M | Identity information of the entity requesting the access control policy | +| Service API identification | M | The identification information of the service API for which the access control policy is being requested. | + +### 8.12.2.2 Obtain access control policy response + +Table 8.12.2.2-1 describes the information flow obtain access control policy response from the CAPIF core function to the AEF. + +**Table 8.12.2.2-1: Obtain access control policy response** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the obtain access control policy operation | +| Access control policy information | O (see NOTE) | The access control policy information corresponding to the requested service API. | +| NOTE: Shall be present if the Result information element indicates that the obtain access control policy operation is successful. Otherwise access control policy information shall not be present. | | | + +## 8.12.3 Procedure + +Figure 8.12.3-1 illustrates the procedure for obtaining policy to perform access control on the service API invocations. + +Pre-conditions: + +1. The AEF is hosting the service API but the policy to perform access control is not available with AEF. +2. The CAPIF core function is configured with the access control policies corresponding to one or more service APIs. +3. Authorization details of the AEF are available with the CAPIF core function. + +![Sequence diagram showing the procedure for the AEF obtaining service API access control policy. The diagram involves two main participants: AEF and CAPIF core function. The sequence of messages is: 1. Obtain access control policy request from AEF to CAPIF core function; 2. Check whether AEF is authorized to receive the access control policy for service API (internal to CAPIF core function); 3. Obtain access control policy response from CAPIF core function to AEF.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant AEF + participant CAPIF core function + Note right of CAPIF core function: 2. Check whether AEF is authorized to receive the access control policy for service API + AEF->>CAPIF core function: 1. Obtain access control policy request + CAPIF core function-->>AEF: 3. Obtain access control policy response + +``` + +Sequence diagram showing the procedure for the AEF obtaining service API access control policy. The diagram involves two main participants: AEF and CAPIF core function. The sequence of messages is: 1. Obtain access control policy request from AEF to CAPIF core function; 2. Check whether AEF is authorized to receive the access control policy for service API (internal to CAPIF core function); 3. Obtain access control policy response from CAPIF core function to AEF. + +**Figure 8.12.3-1: Procedure for the AEF obtaining service API access control policy** + +1. The AEF sends an obtain access control policy request to the CAPIF core function for obtaining the policy to perform the access control on service API invocations by including the details of the hosted service API. +2. The CAPIF core function checks whether the AEF is authorized to receive the access control policy corresponding to the service APIs requested. +3. If authorization check is successful, the AEF is provided the access control policy for the service API via an obtain access control policy response. If authorization check is not successful, the AEF is provided with a failure indication via a obtain access control policy response. + +**NOTE:** To maintain synchronization between the AEF and the CAPIF core function for the policy cached at AEF, the AEF can subscribe to the policy update event at CAPIF core function according to the procedure in subclause 8.8.3 and receive notifications about any updated policy at CAPIF core function according to the procedure in subclause 8.8.4. + +## 8.13 Topology hiding + +### 8.13.1 General + +The procedure in this subclause corresponds to the architectural requirements for hiding the topology of the PLMN trust domain from the API invokers accessing the service APIs from outside the PLMN trust domain. + +### 8.13.2 Information flows + +#### 8.13.2.1 Service API invocation request (API invoker – AEF-1) + +The information flow service API invocation request from the API invoker to AEF-1 (AEF acting as service communication entry point) is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes the CAPIF related information elements which are included in the service API invocation request. + +#### 8.13.2.2 Service API invocation request (AEF-1 – AEF-2) + +The information flow service API invocation request from AEF-1 (AEF acting as service communication entry point) to AEF-2 (destination AEF for handling service API) is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes the CAPIF related information elements which are included in the service API invocation request. + +#### 8.13.2.3 Service API invocation response (AEF-2 – AEF-1) + +The information flow service API invocation response from AEF-2 (destination AEF for handling service API) to AEF-1 (AEF acting as service communication entry point) is service API specific and the complete detail of the service API + +invocation response is out of scope of the present document. Table 8.17.2.2-1 describes the CAPIF related information elements which are included in the service API invocation response. + +#### 8.13.2.4 Service API invocation response (AEF-1 – API invoker) + +The information flow service API invocation response from AEF-1 (AEF acting as service communication entry point) to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.17.2.2-1 describes the CAPIF related information elements which are included in the service API invocation response. + +### 8.13.3 Procedure + +Figure 8.13.3-1 illustrates the procedure for CAPIF topology hiding. + +Pre-conditions: + +1. The API invoker has performed the service discovery and received the details of the service API which includes the information about the service communication entry point of the AEF-1 in the CAPIF. +2. The API invoker is authenticated and authorized to use the service API. +3. The AEF-1 in the CAPIF is configured with a policy for topology hiding including the entry point address of the service API (provided via AEF-2). + +![Sequence diagram illustrating the procedure for CAPIF topology hiding. The diagram shows four lifelines: API invoker, AEF-1 (Service API), CAPIF core function, and AEF-2 (Service API). The sequence of messages is: 1. Service API invocation request from API invoker to AEF-1; 2. Service API invocation request from AEF-1 to AEF-2; 3. Service API invocation response from AEF-2 to AEF-1; 4. Service API invocation response from AEF-1 to API invoker.](faa6766e9ed23a192edcbbbbb753e88c_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant AEF-1 as AEF-1 (Service API) + participant CAPIF core function + participant AEF-2 as AEF-2 (Service API) + Note left of API invoker: Pre-conditions + API invoker->>AEF-1: 1. Service API invocation request + AEF-1->>AEF-2: 2. Service API invocation request + AEF-2-->>AEF-1: 3. Service API invocation response + AEF-1-->>API invoker: 4. Service API invocation response +``` + +Sequence diagram illustrating the procedure for CAPIF topology hiding. The diagram shows four lifelines: API invoker, AEF-1 (Service API), CAPIF core function, and AEF-2 (Service API). The sequence of messages is: 1. Service API invocation request from API invoker to AEF-1; 2. Service API invocation request from AEF-1 to AEF-2; 3. Service API invocation response from AEF-2 to AEF-1; 4. Service API invocation response from AEF-1 to API invoker. + +**Figure 8.13.3-1: Procedure for CAPIF topology hiding** + +1. The API invoker performs service API invocation according to the interface of the service API by sending a service API invocation request towards the AEF-1 which exposes the service API towards the API invoker, and acts as topology hiding entity. +- NOTE: Steps 2 and 3 are not necessary when the AEF-1 is capable to serve the service API invocation request. +2. The AEF-1 further resolves the actual destination service API address information according to the topology hiding policy and forwards the incoming service API invocation request to the service API of the related AEF-2. + 3. The AEF-1 receives a response request for service API invocation from service API provided by AEF-2. + 4. The AEF-1 resolves the destination API invoker address and also modifies the source address information of the AEF-2 within the response request as per topology hiding policy and forwards the response request to the API invoker. + +## 8.14 Authentication between the API invoker and the AEF prior to service API invocation + +### 8.14.1 General + +The procedure in this subclause corresponds to the architectural requirements for authentication of the API invoker by the AEF. + +To reduce latency during API invocation, the API invoker associated authentication information can be made available at the AEF after authentication between the API invoker and the CAPIF core function. + +### 8.14.2 Information flows + +NOTE: The security aspects of this procedure are specified in subclause 6.4 and subclause 6.5.2 of 3GPP TS 33.122 [12]. + +### 8.14.3 Procedure + +Figure 8.14.3-1 illustrates the procedure for authentication between the API invoker and the AEF. + +Pre-conditions: + +1. Optionally, the CAPIF core function has shared the information required for authentication of the API invoker with the AEF. + +![Sequence diagram illustrating the procedure for authentication between the API invoker and the AEF prior to service API invocation. The diagram shows four steps: 1. Authentication Initiation request from API invoker to API exposing function; 2. Obtain API invoker information for authentication (dashed box) from API exposing function to CAPIF core function; 3. Authentication Initiation response from CAPIF core function to API exposing function; 4. Identity verification and authentication (solid box) from API exposing function to API invoker.](cbefcea7209aad70adeda96999ecffde_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF core function + participant API exposing function + Note right of API exposing function: 2. Obtain API invoker information for authentication + Note right of API exposing function: 4. Identity verification and authentication + API invoker->>API exposing function: 1. Authentication Initiation request + API exposing function-->>CAPIF core function: 2. Obtain API invoker information for authentication + CAPIF core function-->>API exposing function: 3. Authentication Initiation response + API exposing function-->>API invoker: 4. Identity verification and authentication +``` + +Sequence diagram illustrating the procedure for authentication between the API invoker and the AEF prior to service API invocation. The diagram shows four steps: 1. Authentication Initiation request from API invoker to API exposing function; 2. Obtain API invoker information for authentication (dashed box) from API exposing function to CAPIF core function; 3. Authentication Initiation response from CAPIF core function to API exposing function; 4. Identity verification and authentication (solid box) from API exposing function to API invoker. + +**Figure 8.14.3-1: Procedure for authentication between the API invoker and the AEF prior to service API invocation** + +1. The API invoker triggers authentication initiation to the AEF, including the API invoker identity. +2. The AEF obtains the API invoker information required for authentication by the AEF, if not available. +3. The AEF returns the result of authentication initiation in the authentication initiation response. +4. The AEF verifies the identity of the API invoker and authenticates the API invoker. + +NOTE 1: The authentication process is specified in subclause 6.4 and subclause 6.5.2 of 3GPP TS 33.122 [12]. + +NOTE 2: The authentication is terminated at the AEF acting as the service communication entry point when topology hiding is enabled for the service API. + +## 8.15 Authentication between the API invoker and the AEF upon the service API invocation + +### 8.15.1 General + +The procedure in this subclause corresponds to the architectural requirements for authentication of the API invoker by the AEF upon the service API invocation. + +To reduce latency during API invocation, the API invoker associated authentication information can be made available at the AEF after authentication between the API invoker and the CAPIF core function. + +### 8.15.2 Information flows + +NOTE: The security aspects of this procedure are specified in subclause 6.5.2.3 of 3GPP TS 33.122 [12]. + +#### 8.15.2.1 Service API invocation request with authentication information + +The information flow service API invocation request with authentication information from the API invoker to the AEF is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.15.2.1-1 describes only the CAPIF related information elements which are included in the service API invocation request. + +**Table 8.15.2.1-1: Service API invocation request with authentication information** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API invoker identity information | M | The information that determines the identity of the API invoker | +| Authentication information | M
(see NOTE) | The authentication information obtained before initiating the service API invocation request | +| Service API identification | M | The identification information of the service API for which invocation is requested. The service API identification is part of the specific service API invocation request. | +| NOTE: The specific aspect of this information element is specified in subclause 6.5.2.3 of 3GPP TS 33.122 [12]. | | | + +#### 8.15.2.2 Service API invocation response + +The information flow service API invocation response from the AEF to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.15.2.2-1 describes only the CAPIF related information elements which are included in the service API invocation response. + +**Table 8.15.2.2-1: Service API invocation response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| Result | M | Indicates the success or failure of service API invocation. | + +### 8.15.3 Procedure + +Figure 8.15.3-1 illustrates the procedure for authentication of the API invoker by the AEF, where the authentication information is carried in the API invocation request. + +Pre-conditions: + +- Optionally, the CAPIF core function has shared the information required for authentication of the API invoker with the AEF. + +![Sequence diagram showing the procedure for authentication between the API invoker and the AEF upon the service API invocation. The diagram involves three lifelines: API invoker, CAPIF core function, and API exposing function. The sequence of messages is: 1. Service API invocation request with authentication information from API invoker to API exposing function; 2. Obtain API invoker information for authentication (dashed box) from API exposing function to CAPIF core function; 3. Identity verification and authentication (solid box) from CAPIF core function to API exposing function; 4. Service API invocation response from API exposing function to API invoker.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF core function + participant API exposing function + Note right of CAPIF core function: 2. Obtain API invoker information for authentication + Note right of CAPIF core function: 3. Identity verification and authentication + API invoker->>API exposing function: 1. Service API invocation request with authentication information + API exposing function-->>CAPIF core function: 2. Obtain API invoker information for authentication + CAPIF core function-->>API exposing function: 3. Identity verification and authentication + API exposing function-->>API invoker: 4. Service API invocation response +``` + +Sequence diagram showing the procedure for authentication between the API invoker and the AEF upon the service API invocation. The diagram involves three lifelines: API invoker, CAPIF core function, and API exposing function. The sequence of messages is: 1. Service API invocation request with authentication information from API invoker to API exposing function; 2. Obtain API invoker information for authentication (dashed box) from API exposing function to CAPIF core function; 3. Identity verification and authentication (solid box) from CAPIF core function to API exposing function; 4. Service API invocation response from API exposing function to API invoker. + +**Figure 8.15.3-1: Procedure for authentication between the API invoker and the AEF upon the service API invocation** + +1. The API invoker invokes a service API invocation request with authentication information to the AEF, and includes in this request authentication information, including the API invoker identity. +2. The AEF obtains the API invoker information required for authentication by the AEF, if not available. +3. The AEF verifies the identity of the API invoker and authenticates the API invoker. + +NOTE 1: The authentication process is specified in subclause 6.5.2.3 of 3GPP TS 33.122 [12]. + +4. If the verification was successful, the AEF returns the result of the service API invocation in the Service API invocation response. + +NOTE 2: The authentication is terminated at the AEF acting as the service communication entry point when topology hiding is enabled for the service API. + +## 8.16 Service API invocation with AEF authorization + +### 8.16.1 General + +The procedure in this subclause corresponds to the architectural requirements to validate authorization of API invokers upon the service API invocation. + +To reduce latency during API invocation, the API invoker associated authorization information can be made available at the AEF after authentication between the API invoker and the CAPIF core function. + +NOTE: The security aspects of service API invocation are specified in TS 33.122 [12] clause 6.4 (CAPIF-2) and 6.5 (CAPIF-2e). + +### 8.16.2 Information flows + +#### 8.16.2.1 Service API invocation request + +The information flow service API invocation request from the API invoker to the AEF is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.16.2.1-1 describes only the CAPIF related information elements which are included in the service API invocation request. + +**Table 8.16.2.1-1: Service API invocation request** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API invoker identity information | M | The information that determines the identity of the API invoker | +| Authorization information | O
(see NOTE) | The authorization information obtained before initiating the service API invocation request | +| Service API identification | M | The identification information of the service API for which invocation is requested. The service API identification is part of the specific service API invocation request. | +| NOTE: The inclusion of this information element depends on the chosen solution for authorization. | | | + +## 8.16.2.2 Service API invocation response + +The information flow service API invocation response from the AEF to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.16.2.2-1 describes only the CAPIF related information elements which are included in the service API invocation response. + +**Table 8.16.2.2-1: Service API invocation response** + +| Information element | Status | Description | +|----------------------------|---------------|-------------------------------------------------------------| +| Result | M | Indicates the success or failure of service API invocation. | + +## 8.16.3 Procedure + +Figure 8.16.3-1 illustrates the procedure for API invoker authorization to access service APIs. + +Pre-conditions: + +1. The API invoker has been authenticated. +2. The API invoker associated authorization information is available at AEF. + +![Sequence diagram illustrating the procedure for API invoker authorization to access service APIs. The diagram shows three lifelines: API invoker, CAPIF core function, and API exposing function. The sequence of messages is: 1. Service API invocation request from API invoker to API exposing function; 2. Check authorization from API exposing function to CAPIF core function; 2a. Obtain Authorization information (dashed box) from CAPIF core function to API exposing function; 3. Execute API logic from API exposing function; 4. Service API invocation response from API exposing function to API invoker.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF core function + participant API exposing function + Note right of API exposing function: 2.Check authorization + Note right of CAPIF core function: 2a. Obtain Authorization information + Note right of API exposing function: 3.Execute API logic + API invoker->>API exposing function: 1. Service API invocation request + API exposing function->>CAPIF core function: 2.Check authorization + CAPIF core function-->>API exposing function: 2a. Obtain Authorization information + API exposing function->>API exposing function: 3.Execute API logic + API exposing function->>API invoker: 4. Service API invocation response +``` + +Sequence diagram illustrating the procedure for API invoker authorization to access service APIs. The diagram shows three lifelines: API invoker, CAPIF core function, and API exposing function. The sequence of messages is: 1. Service API invocation request from API invoker to API exposing function; 2. Check authorization from API exposing function to CAPIF core function; 2a. Obtain Authorization information (dashed box) from CAPIF core function to API exposing function; 3. Execute API logic from API exposing function; 4. Service API invocation response from API exposing function to API invoker. + +**Figure 8.16.3-1: Procedure for API invoker authorization to access service APIs** + +1. The API invoker triggers service API invocation request to the AEF, including the service API to be invoked. + +NOTE 1: Authentication can also be performed if not authenticated previously. + +NOTE 2: The API invoker can trigger several service API invocations asynchronously. + +2. Upon receiving the service API invocation request, the AEF checks whether the API invoker is authorized to invoke that service API, based on the authorization information. + - 2a. If the AEF does not have information required to authorize service API invocation, the AEF obtains the authorization information from the CAPIF core function. +3. The AEF executes the service logic for the invoked service API. +4. The API invoker receives the service API invocation response as a result of the service API invocation. + +## 8.17 CAPIF access control + +### 8.17.1 General + +The CAPIF controls the access of service API by the API invoker based on policy or usage limits. + +## 8.17.2 Information flows + +### 8.17.2.1 Service API invocation request + +The information flow service API invocation request from the API invoker to the AEF is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes only the CAPIF related information elements which are included in the service API invocation request. + +**Table 8.17.2.1-1: Service API invocation request** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API invoker identity information | M | The information that determines the identity of the API invoker | +| Authorization information | O
(see NOTE) | The authorization information obtained before initiating the service API invocation request | +| Service API identification | M | The identification information of the service API for which invocation is requested. The service API identification is part of the specific service API invocation request. | +| NOTE: The inclusion of this information element depends on the chosen solution for authorization. | | | + +### 8.17.2.2 Service API invocation response + +The information flow service API invocation response from the AEF to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.17.2.2-1 describes only the CAPIF related information elements which are included in the service API invocation response. + +**Table 8.17.2.2-1: Service API invocation response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| Result | M | Indicates the success or failure of service API invocation. | + +## 8.17.3 Procedure + +Figure 8.17.3-1 illustrates the procedure for service API access control. + +Pre-conditions: + +1. The API invoker has performed the service API discovery and received the details of the service API which includes the information about the service communication entry point of the AEF in the CAPIF. +2. The API invoker is authenticated and authorized to use the service API. +3. The AEF in the CAPIF is configured with at least one access policy to be applied to the service API invocation corresponding to the API invoker and service API. + +![Sequence diagram illustrating the procedure for service API access control. The diagram shows three lifelines: API invoker, AEF (Service API), and CAPIF core function. The sequence of messages is: 1. Service API invocation request from API invoker to AEF; 2. Obtain the policy for access control from AEF to CAPIF core function; 3. Access control on Service API invocation from CAPIF core function to AEF; 4. Service API invocation response from AEF to API invoker.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant AEF as AEF (Service API) + participant CAPIF core function + Note right of AEF: 2. Obtain the policy for access control + Note right of CAPIF core function: 3. Access control on Service API invocation + API invoker->>AEF: 1. Service API invocation request + AEF->>CAPIF core function: 2. Obtain the policy for access control + CAPIF core function->>AEF: 3. Access control on Service API invocation + AEF->>API invoker: 4. Service API invocation response +``` + +Sequence diagram illustrating the procedure for service API access control. The diagram shows three lifelines: API invoker, AEF (Service API), and CAPIF core function. The sequence of messages is: 1. Service API invocation request from API invoker to AEF; 2. Obtain the policy for access control from AEF to CAPIF core function; 3. Access control on Service API invocation from CAPIF core function to AEF; 4. Service API invocation response from AEF to API invoker. + +**Figure 8.17.3-1: Procedure for service API access control** + +1. The API invoker performs service API invocation according to the interface of the service API by sending a service API invocation request towards the AEF which exposes the service API towards the API invoker. The AEF acts as an access control entity. +2. If the access control policy is not configured with AEF, then the AEF may obtain the access control policy configuration from the CAPIF core function. +3. Upon receiving the service API invocation request from the API invoker, the AEF checks for configuration for access control. As per the configuration for access control, the AEF performs access control on the service API invocation request as per the operator policy. +4. The API invoker receives a service API invocation response for service API invocation from the AEF providing the service API. + +## 8.18 CAPIF access control with cascaded AEFs + +### 8.18.1 General + +The procedure in this subclause corresponds to the architectural requirements related to some common access control requirements for service API invocations. It provides access control, based on two cascaded API Exposing Function (AEF) instances. While one AEF instance provides the entry point for the service API and acts as access controller, further AEF instances deliver the functionality of the actual service APIs. + +### 8.18.2 Information flows + +#### 8.18.2.1 Service API invocation request + +The information flow service API invocation request from the API invoker to the AEF and between AEFs is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes the CAPIF related information elements which are included in the service API invocation request. + +#### 8.18.2.2 Service API invocation response + +The information flow service API invocation response from the AEF to the API invoker and between AEFs is service API specific and the complete detail of the service API invocation response is out of scope of the present document. + +Table 8.17.2.2-1 describes the CAPIF related information elements which are included in the service API invocation response. + +### 8.18.3 Procedure + +Figure 8.18.3-1 illustrates the procedure for CAPIF access control. + +Pre-conditions: + +1. The API invoker has performed the service discovery and received the details of the service API which includes the information about the service communication entry point of the AEF-1 in the CAPIF. +2. The API invoker is authenticated and authorized to use the service API. +3. The AEF-1 in the CAPIF is configured with at least one access policy to be applied to the service API invocation corresponding to the API invoker and service API. + +![Sequence diagram illustrating the procedure for CAPIF access control with cascaded AEFs. The diagram shows three participants: API invoker, AEF-1 (Access controller), and AEF-2 (Service API). The sequence of messages is: 1. Service API invocation request from API invoker to AEF-1; 2. Access control on service API invocation (internal to AEF-1); 3. Service API invocation request from AEF-1 to AEF-2; 4. Service API invocation response from AEF-2 to AEF-1; 5. Service API invocation response from AEF-1 to API invoker.](b033fab424e6df728345cfa04df83fcc_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant AEF-1 as AEF-1 (Access controller) + participant AEF-2 as AEF-2 (Service API) + Note right of AEF-1: 2. Access control on service API invocation + API invoker->>AEF-1: 1. Service API invocation request + AEF-1->>AEF-2: 3. Service API invocation request + AEF-2-->>AEF-1: 4. Service API invocation response + AEF-1-->>API invoker: 5. Service API invocation response +``` + +Sequence diagram illustrating the procedure for CAPIF access control with cascaded AEFs. The diagram shows three participants: API invoker, AEF-1 (Access controller), and AEF-2 (Service API). The sequence of messages is: 1. Service API invocation request from API invoker to AEF-1; 2. Access control on service API invocation (internal to AEF-1); 3. Service API invocation request from AEF-1 to AEF-2; 4. Service API invocation response from AEF-2 to AEF-1; 5. Service API invocation response from AEF-1 to API invoker. + +**Figure 8.18.3-1: Procedure for CAPIF access control with cascaded AEFs** + +1. The API invoker performs service API invocation according to the interface of the service API by sending a service API invocation request towards the AEF-1 which exposes the service API towards the API invoker, and acts as access control entity. +2. Upon receiving the service API invocation request from the API invoker, the AEF-1 checks for configuration for access control. As per the configuration for access control, the AEF-1 performs access control on the service API invocation as per the operator policy. +3. The AEF-1 forwards the incoming service API invocation request to the service API provided by AEF-2. +4. The AEF-1 receives a service API invocation response for service API invocation from AEF-2. +5. The AEF-1 resolves the destination API invoker address and modifies the source address information of AEF-2 within the service API invocation response and forwards the service API invocation response to the API invoker. + +## 8.19 Logging service API invocations + +### 8.19.1 General + +The procedure in this subclause corresponds to the architectural requirements for logging service API invocations at AEF. The AEF can be within PLMN trust domain or within 3rd party trust domain. + +## 8.19.2 Information flows + +### 8.19.2.1 API invocation log request + +Table 8.19.2.1-1 describes the information flow API invocation log request from the API exposing function to the CAPIF core function. + +**Table 8.19.2.1-1: API invocation log request** + +| Information element | Status | Description | +|-----------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API exposing identity information | M | Identity information of the AEF logging service API(s) invocations | +| API invocation log information | M | API invocation log information such as API invoker's ID, IP address, service API name, version, invoked operation, input parameters, invocation result, time stamp information | + +### 8.19.2.2 API invocation log response + +Table 8.19.2.2-1 describes the information flow API invocation log response from the CAPIF core function to the API exposing function. + +**Table 8.19.2.2-1: API invocation log response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| Result | M | Indicates the success or failure of API(s) invocation log request | + +## 8.19.3 Procedure + +Figure 8.19.3-1 illustrates the procedure for logging service API invocations at AEF. + +Pre-conditions: + +1. The API invoker(s) has invoked certain service API(s). +2. Authorization details of the AEF are available with the CAPIF core function. + +![Sequence diagram illustrating the procedure for logging service API invocations. The diagram shows two lifelines: 'CAPIF core function' and 'API exposing function'. The sequence of messages is: 1. API invocation log request (from API exposing function to CAPIF core function), 2. Log API invocation (internal message within CAPIF core function), and 3. API invocation log response (from CAPIF core function to API exposing function).](af3d1702fb2fcdf2f9ec1a985afc085f_img.jpg) + +``` + +sequenceDiagram + participant CAPIF core function + participant API exposing function + Note left of CAPIF core function: 2. Log API invocation + API exposing function->>CAPIF core function: 1. API invocation log request + CAPIF core function-->>API exposing function: 3. API invocation log response + +``` + +Sequence diagram illustrating the procedure for logging service API invocations. The diagram shows two lifelines: 'CAPIF core function' and 'API exposing function'. The sequence of messages is: 1. API invocation log request (from API exposing function to CAPIF core function), 2. Log API invocation (internal message within CAPIF core function), and 3. API invocation log response (from CAPIF core function to API exposing function). + +**Figure 8.19.3-1: Procedure for logging service API invocations** + +1. Upon invocation of service API(s) from one more API invokers, the AEF triggers API invocation log request towards the CAPIF core function. + +NOTE 1: The AEF can collect the log information associated to several API invocations before triggering API invocation log request asynchronously. + +2. The CAPIF core function makes a log entry and stores the information e.g. for charging purposes, for access by authorized users and entities. + +NOTE 2: API invocation log is stored for a configured duration. + +3. AEF receives the API invocation log response from the CAPIF core function. + +## 8.20 Charging the invocation of service APIs + +### 8.20.1 General + +The procedure in this subclause corresponds to the architectural requirements for charging the invocation of service APIs. The AEF can be within PLMN trust domain or within 3rd party trust domain. + +### 8.20.2 Information flows + +NOTE: It is in SA5 scope to develop the charging related information flows for this procedure. + +**Editor's note:** Reference to the appropriate SA5 specification is needed. + +### 8.20.3 Procedure + +Figure 8.20.3-1 illustrates the procedure for charging the invocation of service APIs. + +Pre-conditions: + +1. Authorization details of the AEF are available with the CAPIF core function. + +![Sequence diagram illustrating the procedure for charging the invocation of service APIs. The diagram shows two lifelines: 'CAPIF core function' and 'API exposing function'. The sequence of messages is: 1. API invocation charging request (from API exposing function to CAPIF core function), 2. Charging procedure (internal to CAPIF core function), and 3. API invocation charging response (from CAPIF core function to API exposing function).](578160bbc1592eab2db5f845bc95633d_img.jpg) + +``` +sequenceDiagram + participant AEF as AEF + participant CAPIF as CAPIF core function + participant API as API exposing function + Note left of AEF: Pre-conditions: Authorization details of the AEF are available with the CAPIF core function. + API->>CAPIF: 1. API invocation charging request + Note right of CAPIF: 2. Charging procedure + CAPIF->>API: 3. API invocation charging response +``` + +Sequence diagram illustrating the procedure for charging the invocation of service APIs. The diagram shows two lifelines: 'CAPIF core function' and 'API exposing function'. The sequence of messages is: 1. API invocation charging request (from API exposing function to CAPIF core function), 2. Charging procedure (internal to CAPIF core function), and 3. API invocation charging response (from CAPIF core function to API exposing function). + +**Figure 8.20.3-1: Procedure for charging the invocation of service APIs** + +1. Upon invocation of service API(s) from one more API invokers, the AEF triggers an API invocation charging request and includes API invoker information (e.g. invoker's ID and IP address, location, timestamp) and service API information (e.g. service API name and version, invoked operation, input parameters, invocation result) towards the CAPIF core function. + +NOTE: These requests can be triggered asynchronously. + +2. The CAPIF core function performs a charging procedure which includes storing the information for access by authorized API management. +3. The AEF receives the API invocation charging response from the CAPIF core function. + +## 8.21 Monitoring service API invocation + +### 8.21.1 General + +The procedure in this subclause corresponds to the architectural requirements for monitoring service API invocation. + +### 8.21.2 Information flows + +#### 8.21.2.1 Monitoring service API event notification + +The information flow for the monitoring service API event notification from the CAPIF core function to the API management function is same as the event notification from the CAPIF core function to the subscribing entity. Table 8.8.2.3-1 describes the information elements which are included in the monitoring service API event notification. + +#### 8.21.2.2 Monitoring service API event notification acknowledgement + +The information flow for the monitoring service API event notification acknowledgement from the API management function to the CAPIF core function is same as the event notification acknowledgement from subscribing entity to the CAPIF core function. Table 8.8.2.4-1 describes the information elements which are included in the monitoring service API event notification acknowledgement. + +### 8.21.3 Procedure + +Figure 8.21.3-1 illustrates the procedure for monitoring service API invocation. + +Pre-conditions: + +1. The API management function has subscribed to monitoring event including filters such as invoker's ID and IP address, service API name and version, input parameters, and invocation result. + +![Sequence diagram illustrating the procedure for monitoring service API invocation. The diagram shows two lifelines: CAPIF core function and API management function. The process starts with '1. Monitoring event detected' on the CAPIF core function lifeline. Then, '2. Monitoring service API event notification' is sent from the CAPIF core function to the API management function. Finally, '3. Monitoring service API event notification acknowledgement' is sent from the API management function back to the CAPIF core function.](12936f2edb05b1f2f43702086d1de2cc_img.jpg) + +``` +sequenceDiagram + participant CAPIF core function + participant API management function + Note left of CAPIF core function: 1. Monitoring event detected + CAPIF core function->>API management function: 2. Monitoring service API event notification + API management function-->>CAPIF core function: 3. Monitoring service API event notification acknowledgement +``` + +Sequence diagram illustrating the procedure for monitoring service API invocation. The diagram shows two lifelines: CAPIF core function and API management function. The process starts with '1. Monitoring event detected' on the CAPIF core function lifeline. Then, '2. Monitoring service API event notification' is sent from the CAPIF core function to the API management function. Finally, '3. Monitoring service API event notification acknowledgement' is sent from the API management function back to the CAPIF core function. + +**Figure 8.21.3-1: Procedure for monitoring service API invocation** + +1. The CAPIF core function monitors the service API invocations applying the monitoring filters specified before. +2. Detection of a monitoring event by the CAPIF core function triggers notification to the API management function with the details of the monitored event. + +NOTE: API provider action subsequent to monitoring service API notification is out-of-scope of this specification. + +3. The API management function sends a monitoring service API event notification acknowledgement to the CAPIF core function for the notification received. + +## 8.22 Auditing service API invocation + +### 8.22.1 General + +The procedure in this subclause corresponds to the architectural requirements for auditing service API invocation. This procedure can be used for auditing of other CAPIF interactions i.e. service API invocation events, API invoker onboarding events and API invoker interactions with the CAPIF (e.g. authentication, authorization, discover service APIs) as well. The API management function can be within PLMN trust domain or within 3rd party trust domain. + +### 8.22.2 Information flows + +#### 8.22.2.1 Query service API log request + +Table 8.22.2.1-1 describes the information flow query service API log request from the API management function to the CAPIF core function. + +**Table 8.22.2.1-1: Query service API log request** + +| Information element | Status | Description | +|----------------------|--------|----------------------------------------------------------------------------------------------------------------------------------| +| Identity information | M | Identity information of the entity querying service API log request | +| Query information | M | List of query filters such as invoker's ID and IP address, service API name and version, input parameters, and invocation result | + +#### 8.22.2.2 Query service API log response + +Table 8.22.2.2-1 describes the information flow query service API log response from the CAPIF core function to the API management function. + +**Table 8.22.2.2-1: Query service API log response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of query service API log request | +| API invocation log information | O
(see NOTE) | API invocation log information such as API invoker's ID, IP address, service API name, version, invoked operation, input parameters, invocation result, time stamp information | +| NOTE: Information element shall be present when result indicates success. | | | + +### 8.22.3 Procedure + +Figure 8.22.3-1 illustrates the procedure for auditing service API invocation. + +Pre-conditions: + +1. Service API invocation logs are available at the CAPIF core function. +2. Authorization details of the AMF are available with the CAPIF core function. + +![Sequence diagram illustrating the procedure for auditing service API invocation. The diagram shows two lifelines: CAPIF core function and API management function. The sequence of messages is: 1. Query service API log request (from API management function to CAPIF core function), 2. Access service API invocation logs (internal message within CAPIF core function), and 3. Query service API log response (from CAPIF core function to API management function).](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant API management function + participant CAPIF core function + Note right of CAPIF core function: 2. Access service API invocation logs + API management function->>CAPIF core function: 1. Query service API log request + CAPIF core function-->>API management function: 3. Query service API log response + +``` + +Sequence diagram illustrating the procedure for auditing service API invocation. The diagram shows two lifelines: CAPIF core function and API management function. The sequence of messages is: 1. Query service API log request (from API management function to CAPIF core function), 2. Access service API invocation logs (internal message within CAPIF core function), and 3. Query service API log response (from CAPIF core function to API management function). + +**Figure 8.22.3-1: Procedure for auditing service API invocation** + +1. For auditing service API invocations, the API management function triggers query service API log request to the CAPIF core function. +2. Upon receiving the query service API log request, the CAPIF core function accesses the necessary service API log information for auditing purposes. +3. The CAPIF core function returns the log information to the API management function in the query service API log response. + +NOTE: The API management function detecting abuse of the service API invocation and actions, subsequent to query service API log response, are out-of-scope of this specification. + +## 8.23 CAPIF revoking API invoker authorization + +### 8.23.1 General + +The CAPIF controls the access of service API by the API invoker based on policy or usage limits. If the usage limits have exceeded, the authorization of the API invoker for accessing the service APIs is revoked. The decision to revoke the API invoker authorization may be triggered by the AEF or the CAPIF core function. The AEF can be within PLMN trust domain or within 3rd party trust domain. + +In RNAA scenarios, the decision to revoke the API invoker authorization may be initiated by the CAPIF core function based on triggers at the CAPIF core function. + +### 8.23.2 Information flows + +#### 8.23.2.1 Revoke API invoker authorization request + +Table 8.23.2.1-1 describes the information flow revoke API invoker authorization request from the API exposing function to the CAPIF core function or from the CAPIF core function to the API exposing function. + +**Table 8.23.2.1-1: Revoke API invoker authorization request** + +| Information element | Status | Description | +|----------------------------------|--------|-------------------------------------------------------------------------------------------| +| API invoker identity information | M | The information that determines the identity of the API invoker | +| Service API identification | M | The identification information of the service API for which the authorization is revoked. | +| Cause | M | The cause for revoking the API invoker authorization | + +### 8.23.2.2 Revoke API invoker authorization response + +Table 8.23.2.2-1 describes the information flow revoke API invoker authorization response from the CAPIF core function to the API exposing function or from the API exposing function to the CAPIF core function. + +**Table 8.23.2.2-1: Revoke API invoker authorization response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| Result | M | Indicates the success or failure of revoke API invoker authorization. | + +### 8.23.2.3 Revoke API invoker authorization notify + +Table 8.23.2.3-1 describes the information flow revoke API invoker authorization notify from the CAPIF core function to the API invoker. + +**Table 8.23.2.3-1: Revoke API invoker authorization notify** + +| Information element | Status | Description | +|----------------------------------|--------|------------------------------------------------------------------------------------------------------| +| API invoker identity information | M | The information that determines the identity of the API invoker whose authorization has been revoked | +| Service API identification | M | The identification information of the service API for which the authorization is revoked. | +| Cause | M | The cause for revoking the API invoker authorization | + +## 8.23.3 Procedure for CAPIF revoking API invoker authorization initiated by AEF + +Figure 8.23.3-1 illustrates the procedure for revoking API invoker authorization to access service API initiated by the AEF. + +Pre-conditions: + +1. The API invoker is authenticated and authorized to use the service API. +2. The AEF in the CAPIF is configured with the access policy to be applied to the service API invocation corresponding to the API invoker and the service API. +3. Authorization details of the AEF are available with the CAPIF core function. + +![Sequence diagram illustrating the procedure for revoking API invoker authorization initiated by AEF. The diagram shows three lifelines: API invoker, CAPIF Core function, and AEF. The sequence of messages is: 1. AEF triggers the revocation; 2. AEF sends a revoke request to CAPIF Core function; 3. CAPIF Core function invalidates authorization; 4. CAPIF Core function sends a response to AEF; 5. AEF invalidates authorization; 6. CAPIF Core function sends a notify to API invoker.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF Core function + participant AEF + Note right of AEF: 1. Trigger for revoking API invoker authorization + AEF->>CAPIF Core function: 2. Revoke API invoker authorization request + Note left of CAPIF Core function: 3. Invalidate the authorization of the API invoker for service API + CAPIF Core function->>AEF: 4. Revoke API invoker authorization response + Note right of AEF: 5. Invalidate the authorization of the API invoker for service API + CAPIF Core function->>API invoker: 6. Revoke API invoker authorization notify +``` + +Sequence diagram illustrating the procedure for revoking API invoker authorization initiated by AEF. The diagram shows three lifelines: API invoker, CAPIF Core function, and AEF. The sequence of messages is: 1. AEF triggers the revocation; 2. AEF sends a revoke request to CAPIF Core function; 3. CAPIF Core function invalidates authorization; 4. CAPIF Core function sends a response to AEF; 5. AEF invalidates authorization; 6. CAPIF Core function sends a notify to API invoker. + +**Figure 8.23.3-1: Procedure for revoking API invoker authorization initiated by AEF** + +1. The AEF triggers the revocation of the API invoker authorization. +2. The AEF sends revoke API invoker authorization request to the CAPIF core function with the details of the API invoker and the service API. +3. Upon receiving the information to revoke the API invoker's authorization for service API invocation, the CAPIF core function invalidates the API invoker authorization corresponding to the service API. +4. The CAPIF core function sends a revoke API invoker authorization response to the AEF. +5. Upon successful revocation of API invoker authorization corresponding to the service API at the CAPIF core function, the AEF invalidates the API invoker authorization corresponding to the service API. +6. The CAPIF core function sends a revoke API invoker authorization notify to the API invoker whose authorization to access the service API has been revoked. + +#### 8.23.4 Procedure for CAPIF revoking API invoker authorization initiated by CAPIF core function + +Figure 8.23.4-1 illustrates the procedure for revoking API invoker authorization to access service API initiated by the CAPIF core function. This procedure is also used for revoking API invoker authorization supporting RNAA scenarios. + +Pre-conditions: + +1. The API invoker is authenticated and authorized to use the service API. +2. The AEF in the CAPIF is configured with the access policy to be applied to the service API invocation corresponding to the API invoker and the service API. + +![Sequence diagram showing the procedure for revoking API invoker authorization initiated by CAPIF core function. The diagram involves three participants: API invoker, CAPIF Core function, and AEF. The steps are: 1. Trigger for revoking API invoker authorization (internal to CAPIF Core function); 2. Revoke API invoker authorization request (CAPIF Core function to AEF); 3. Invalidate the authorization of the API invoker for service API (internal to AEF); 4. Revoke API invoker authorization response (AEF to CAPIF Core function); 5. Invalidate the authorization of the API invoker for service API (internal to CAPIF Core function); 6. Revoke API invoker authorization notify (CAPIF Core function to API invoker).](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` +sequenceDiagram + participant API invoker + participant CAPIF Core function + participant AEF + Note right of CAPIF Core function: 1. Trigger for revoking API invoker authorization + CAPIF Core function->>AEF: 2. Revoke API invoker authorization request + Note right of AEF: 3. Invalidate the authorization of the API invoker for service API + AEF->>CAPIF Core function: 4. Revoke API invoker authorization response + Note right of CAPIF Core function: 5. Invalidate the authorization of the API invoker for service API + CAPIF Core function->>API invoker: 6. Revoke API invoker authorization notify +``` + +Sequence diagram showing the procedure for revoking API invoker authorization initiated by CAPIF core function. The diagram involves three participants: API invoker, CAPIF Core function, and AEF. The steps are: 1. Trigger for revoking API invoker authorization (internal to CAPIF Core function); 2. Revoke API invoker authorization request (CAPIF Core function to AEF); 3. Invalidate the authorization of the API invoker for service API (internal to AEF); 4. Revoke API invoker authorization response (AEF to CAPIF Core function); 5. Invalidate the authorization of the API invoker for service API (internal to CAPIF Core function); 6. Revoke API invoker authorization notify (CAPIF Core function to API invoker). + +**Figure 8.23.4-1: Procedure for revoking API invoker authorization initiated by CAPIF core function** + +1. The CAPIF core function is triggered to revoke the API invoker authorization. +2. The CAPIF core function sends revoke API invoker authorization request to the AEF with the details of the API invoker and the service API. +3. Upon receiving the information to revoke the API invoker's authorization for service API invocation, the AEF invalidates the API invoker authorization corresponding to the service API. +4. The AEF sends a revoke API invoker authorization response to the CAPIF core function. +5. The CAPIF core function invalidates the API invoker authorization corresponding to the service API. +6. The CAPIF core function sends a revoke API invoker authorization notify to the API invoker whose authorization to access the service API has been revoked. + +## 8.24 API topology hiding management + +### 8.24.1 General + +The following procedure in this subclause corresponds to the architectural requirements on API topology hiding. The procedure in this subclause supports API topology hiding by dynamically configuring the address of the AEF providing the Service API to the AEF entry point providing the topology hiding. The API publishing function and the API exposing function can be within PLMN trust domain or within 3rd party trust domain. + +### 8.24.2 Information flows + +#### 8.24.2.1 API topology hiding notify + +Table 8.24.2.1-1 describes the information flow API topology hiding notify from the CAPIF core function to the API exposing function. + +**Table 8.24.2.1-1: API topology hiding notify** + +| Information element | Status | Description | +|--------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service API identification | M | The identification information of the service API with the API topology hiding | +| API exposing function(s) information | M | Indicates the one or more AEF(s) which provides the service API to apply the topology hiding including the interface details (e.g. IP address, port number, URI). | +| Action | M | Indicates the notification action for the API topology hiding (created or revoked). | + +### 8.24.3 Procedure + +Figure 8.24.3-1 illustrates the procedure for API topology hiding management by API (un)publish function. + +Pre-condition: + +1. Authorization details of the APF are available with the CAPIF core function. +2. The API exposing function has subscribed to CAPIF event for API topology hiding status. + +![Sequence diagram illustrating the API topology hiding procedure via API (un)publish. The diagram shows three lifelines: API publish function, CAPIF core function, and API exposing function. The sequence of messages is: 1. API (un)publish request from API publish function to CAPIF core function; 2. determine the AEF as the entry point of API invocation (internal to CAPIF core function); 3. API topology hiding notify from CAPIF core function to API exposing function; 4. store/remove the information (internal to API exposing function); 5. API (un)publish response from CAPIF core function to API publish function.](bb3063a33c89b248574f64b6d8dfc404_img.jpg) + +``` + +sequenceDiagram + participant APF as API publish function + participant CCF as CAPIF core function + participant AEF as API exposing function + Note right of CCF: 2. determine the AEF as the entry point of API invocation + Note right of AEF: 4. store/remove the information + APF->>CCF: 1. API (un)publish request + CCF->>AEF: 3. API topology hiding notify + CCF->>APF: 5. API (un)publish response + +``` + +Sequence diagram illustrating the API topology hiding procedure via API (un)publish. The diagram shows three lifelines: API publish function, CAPIF core function, and API exposing function. The sequence of messages is: 1. API (un)publish request from API publish function to CAPIF core function; 2. determine the AEF as the entry point of API invocation (internal to CAPIF core function); 3. API topology hiding notify from CAPIF core function to API exposing function; 4. store/remove the information (internal to API exposing function); 5. API (un)publish response from CAPIF core function to API publish function. + +**Figure 8.24.3-1: API topology hiding via API (un)publish** + +1. The API publishing function sends a service API publish request as described in subclause 8.3.2.1 or a service API unpublish request as described in subclause 8.4.2.1 to the CAPIF core function. +2. Upon receiving the service API (un)publish request, the CAPIF core function checks whether the API publishing function is authorized to perform the service API (un)publish. If authorized, based on the service APIs and policy: + - For service API publish, the CCF applies the topology hiding by selecting an AEF providing the topology hiding as the entry point for service API invocation. The selected AEF information is stored with the service API information received from API publish function at the CAPIF core function (API registry). + - For service API unpublish, the previously selected AEF as topology hiding entry point and the associated service API information at the CAPIF core function (API registry) are removed. +3. The CCF sends the API topology notify to the AEF selected as the entry point for service API invocation. The service API identification and the AEF(s) information which provides the service API details are included. +4. Upon receiving the notification, the AEF stores the received information for further service API invocation request forwarding if the action in the API topology notify indicates "created" or removes the stored API forwarding information if the action in the API topology notify indicates "revoked". +5. The CCF sends an API (un)publish response to the API publish function. + +## 8.25 Support for CAPIF interconnection + +### 8.25.1 General + +The procedures in this subclause corresponds to the architectural requirements on CAPIF interconnection. + +### 8.25.2 Information flows + +#### 8.25.2.1 Interconnection API publish request + +Table 8.25.2.1-1 describes the information flow interconnection API publish request from CAPIF core function to CAPIF core function. + +**Table 8.25.2.1-1: Interconnection API publish request** + +| 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, API provider name (optional), List of public IP ranges of UEs (optional and applicable only on CAPIF-6 interface), 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, Service KPIs (optional). | +| 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. | | | + +#### 8.25.2.2 Interconnection API publish response + +Table 8.25.2.2-1 describes the information flow interconnection API publish response from CAPIF core function to CAPIF core function. + +**Table 8.25.2.2-1: Interconnection API publish response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of publishing the service API information | +| Service API published information reference | O
(see NOTE) | The information which can be used for referencing the information (set) about the published service API by the CCF which publishes service APIs | +| NOTE: This information element is included when the Result indicates success. | | | + +#### 8.25.2.3 Interconnection service API discover request + +Table 8.25.2.3-1 describes the information flow interconnection service API discover request from one CAPIF core function to another CAPIF core function. + +**Table 8.25.2.3-1: Interconnection service API discover request** + +| 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), UE IP address (optional), preferred AEF location (optional), required API provider name (optional), interfaces, protocols, service API category, Service KPIs (optional)) (see NOTE) | +| NOTE: It should be possible to discover all the service APIs. | | | + +## 8.25.2.4 Interconnection service API discover response + +Table 8.25.2.4-1 describes the information flow interconnection service API discover response from one CAPIF core function to another CAPIF core function. + +**Table 8.25.2.4-1: Interconnection service API discover response** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the discovery of the service API information | +| Service API information | O
(see NOTE) | List of service APIs corresponding to the request, including API description such as service API name, service API type, Serving Area Information (optional), AEF location (optional), interface details (e.g. IP address, port number, URI), protocols, version, data format | +| CAPIF core function identity information | O
(see NOTE) | Indicates the CAPIF core function matching the service API category in the query criteria | +| NOTE: The service API information or the CAPIF core function identity information or both shall be present, if the Result information element indicates that the interconnection service API discover operation is successful. Otherwise, both shall not be present. | | | + +## 8.25.3 Procedure + +### 8.25.3.1 Service API publish for CAPIF interconnection + +This subclause describes the procedure for service API publish for CAPIF interoperation. + +Pre-condition: + +1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers. +2. CCF-B is configured as the designated CAPIF core function in the trust domain of CAPIF provider A. +3. When CCF-A and CCF-B belong to trust domains of different CAPIF providers, the two CAPIF providers have business agreement for service API sharing. + +![Sequence diagram for Interconnection API publish between CCF-A and CCF-B.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` +sequenceDiagram + participant CCF-A + participant CCF-B + Note left of CCF-A: 1. get the service API information + CCF-A->>CCF-B: 2. Interconnection API publish request + Note right of CCF-B: 3. Store the service API information + CCF-B-->>CCF-A: 4. Interconnection API publish response +``` + +The diagram illustrates a sequence of four steps between two entities, CCF-A and CCF-B. Step 1, 'get the service API information', is an internal action on CCF-A. Step 2, 'Interconnection API publish request', is a message sent from CCF-A to CCF-B. Step 3, 'Store the service API information', is an internal action on CCF-B. Step 4, 'Interconnection API publish response', is a message sent from CCF-B back to CCF-A. + +Sequence diagram for Interconnection API publish between CCF-A and CCF-B. + +**Figure 8.25.3.1-1: Interconnection API publish** + +1. CCF-A gets the service APIs to be shared with CCF-B from the API publish function which is in the same CAPIF provider domain of CCF-A as described in subclause 8.3.3, or from another CCF as described in this procedure. +2. Based on the shareable information for the service API or the service API category information, the CCF-A determines to publish the service API or the service API category information to the CCF-B. The CCF-A sends the interconnection API publish request to CCF-B with the details of at least one of service APIs or the category information of the service APIs, along with the identity information of CCF-A, shareable information and CAPIF provider domain information if allowed to share. The API topology hiding may be enabled. +3. CCF-B stores the service API information or service API category provided by the CCF-A. +4. CCF-B provides an interconnection API publish response to the CCF-A indicating success or failure result and triggers notifications to subscribed API invokers as described in subclause 8.8.4. + +### 8.25.3.2 Service API discovery involving multiple CCFs + +This subclause describes a procedure for service API discovery involving multiple CCFs + +Pre-condition: + +1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers. +2. When CCF-A and CCF-B belong to trust domains of different CAPIF providers, the two CAPIF providers have business agreement for service API sharing. + +![Sequence diagram for Service API discovery involving multiple CCFs. The diagram shows three lifelines: API invoker, CCF-A, and CCF-B. The sequence of messages is: 1. Service API discover request from API invoker to CCF-A; 2. Service API discover response from CCF-A to API invoker; 3. Service API discover request from API invoker to CCF-B; 4. Retrieves service API(s) information (internal message on CCF-B); 5. Service API discover response from CCF-B to API invoker.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant CCF-A + participant CCF-B + Note right of CCF-B: 4. Retrieves service API(s) information + API invoker->>CCF-A: 1. Service API discover request + CCF-A-->>API invoker: 2. Service API discover response + API invoker->>CCF-B: 3. Service API discover request + CCF-B->>CCF-B: 4. Retrieves service API(s) information + CCF-B-->>API invoker: 5. Service API discover response + +``` + +Sequence diagram for Service API discovery involving multiple CCFs. The diagram shows three lifelines: API invoker, CCF-A, and CCF-B. The sequence of messages is: 1. Service API discover request from API invoker to CCF-A; 2. Service API discover response from CCF-A to API invoker; 3. Service API discover request from API invoker to CCF-B; 4. Retrieves service API(s) information (internal message on CCF-B); 5. Service API discover response from CCF-B to API invoker. + +**Figure 8.25.3.2-1: Service API discovery y involving multiple CCFs** + +1. The API invoker sends a service API discover request to the CCF-A. It includes the API invoker identity, and may include query information. +2. The CCF-A verifies the identity of the API invoker and retrieves the stored service API(s) information and service API categories. The information of CCF-B with the service API category matching the discovery criteria is returned to API invoker in the service API discover response. + +NOTE: The remaining steps are only applied when the service API category is included in the interconnection API publish request as described in subclause 8.25.2.1. + +3. The API invoker sends an service API discover request to the CCF-B. The identity of API invoker is included. The query information is also provided. +4. Upon receiving the service API discover request, the CCF-B verifies the identity of the API invoker. The CCF-B retrieves the stored service API(s) information as per the query information in the service API discover request. Further, the CCF-B applies the discovery policy and performs filtering of service APIs information which matches the discovery criteria. +5. The CCF-B sends an service API discover response to the API invoker with the list of service API information for which the API invoker has the required authorization. + +### 8.25.3.3 Service API discovery for CAPIF interconnection + +This subclause describes a procedure for service API discovery for CAPIF interconnection. The CCF-A and the CCF-B may belong to the same CAPIF provider domain or different CAPIF provider domains. When the CCF-A and the CCF-B belong to different CAPIF provider domains, the two CAPIF providers shall have business agreement for service API discovery. + +Pre-conditions: + +1. The CCF-A is configured with the CCF-B information. +2. The CCF-B is configured with the CCF-A information. +3. The CCF-A is triggered (e.g. API invoker service API discovery, periodic service API discovery) to perform service API discovery with the CCF-B. + +![Sequence diagram for Service API discovery for CAPIF interconnection. CCF-A sends a request to CCF-B, which retrieves information and responds.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +``` + +sequenceDiagram + participant CCF-A + participant CCF-B + Note right of CCF-B: 2. Retrieves service API(s) information + CCF-A->>CCF-B: 1. Interconnection service API discover request + CCF-B-->>CCF-A: 3. Interconnection service API discover response + +``` + +Sequence diagram for Service API discovery for CAPIF interconnection. CCF-A sends a request to CCF-B, which retrieves information and responds. + +**Figure 8.25.3.3-1: Service API discovery for CAPIF interconnection** + +1. The CCF-A sends the interconnection service API discover request to the CCF-B. The identity of the CCF-A and the query information are included. +2. The CCF-B upon receiving the interconnection service API discover request verifies the identity of the CCF-A. The CCF-B retrieves the stored service API(s) or the CCF(s) information as per the query information in the interconnection service API discover request. Further, the CCF-B applies the discovery policy and performs the filtering of service APIs or the CCF(s) information. The topology hiding policy may be applied to the retrieved list of service API information. +3. The CCF-B sends the interconnection service API discover response to the CCF-A with the list of service API information for which the CCF-A has the required authorization or the CCF(s) information that matches the discovery criteria. + +## 8.26 Update API invoker's API list + +### 8.26.1 General + +The procedure in this subclause corresponds to the architectural requirements for updating the API invoker's API list on the CAPIF core function. The CAPIF enables API invoker to update its own API list e.g. subsequent to discovering new API(s). + +### 8.26.2 Information flows + +#### 8.26.2.1 Update API invoker API list request + +Table 8.26.2.1-1 describes the information flow update API invoker API list request from the API invoker to the CAPIF core function. + +**Table 8.26.2.1-1: Update API invoker API list request** + +| Information element | Status | Description | +|----------------------------------|--------|---------------------------------------------------------------------------| +| API invoker identity information | M | Identity information of the API invoker requesting update | +| APIs for update | M | List of APIs that need update (e.g. enroll new API(s), disenroll API(s)). | + +## 8.26.2.2 Update API invoker API list response + +Table 8.26.2.2-1 describes the information flow update API invoker API list response from the CAPIF core function to the API invoker. + +**Table 8.26.2.2-1: Update API invoker API list response** + +| Information element | Status | Description | +|---------------------|-------------------|------------------------------------------------------------------------------------------------| +| Result | M | Indicates the completely successful or partially successful or failure of the update operation | +| API information | O
(see NOTE 1) | List of APIs and the types of APIs that the API invoker can access | +| Reason | O
(see NOTE 2) | This element indicates the reason when update status is failure and for which API(s) | + +NOTE 1: Information element shall be present when update API invoker API list status is partial or completely successful. +NOTE 2: Information element shall be present when update API invoker API list status is partial successful or failure. + +## 8.26.3 Procedure + +Figure 8.26.3-1 illustrates the procedure for updating the API invoker API list on the CAPIF. + +Pre-conditions: + +1. The API invoker has been onboarded as a recognized user of the CAPIF and associated API invoker profile is provisioned. +2. The API invoker has visibility to new APIs information (e.g. updates on API catalogue or dashboard, API discovery). + +![Sequence diagram showing the procedure for updating the API invoker profile on the CAPIF. The diagram involves two main entities: API invoker and CAPIF core function. The sequence of messages is: 1. Update API invoker API list request (from API invoker to CAPIF core function), 2. Update API invoker API list (internal message within CAPIF core function), and 3. Update API invoker API list response (from CAPIF core function to API invoker).](e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant CAPIF core function + Note right of CAPIF core function: 2. Update API invoker API list + API invoker->>CAPIF core function: 1. Update API invoker API list request + CAPIF core function-->>API invoker: 3. Update API invoker API list response + +``` + +Sequence diagram showing the procedure for updating the API invoker profile on the CAPIF. The diagram involves two main entities: API invoker and CAPIF core function. The sequence of messages is: 1. Update API invoker API list request (from API invoker to CAPIF core function), 2. Update API invoker API list (internal message within CAPIF core function), and 3. Update API invoker API list response (from CAPIF core function to API invoker). + +**Figure 8.26.3-1: Procedure for updating the API invoker profile on the CAPIF** + +1. For updating of the API invoker API list on the CAPIF, the API invoker triggers update API invoker API list request towards the CAPIF core function, providing the information to be updated (e.g. enroll new APIs, disenroll APIs). +2. The CAPIF core function updates the API invoker API list of the requesting API invoker, according to the grant from the CAPIF administrator or the API management. + +NOTE: Completion of updating process can require explicit grant by the CAPIF administrator or the API management, which is left out-of-scope of this solution. CAPIF can handle the grant process internally without the need of explicit grant by the CAPIF administrator. + +3. The update API invoker API list response provides partial success or complete success or failure indication. Partial success and complete success result will include APIs information that the API invoker can access. When the update status is failure, the reason for failure and information for which API(s) the update operation has failed is included. + +## 8.27 Dynamically routing service API invocation + +### 8.27.1 General + +The procedure in this subclause corresponds to the architectural requirements for dynamic routing of service API invocation. The CAPIF enables dynamically routing the service API invocation request based on the detailed information of the invocation. + +### 8.27.2 Information flows + +#### 8.27.2.1 Obtain routing information request + +Table 8.27.2.1-1 describes the information flow dynamic routing information request from the API exposing function to the CAPIF core function. + +**Table 8.27.2.1-1: Obtain routing information request** + +| Information element | Status | Description | +|----------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service API identification information | M | The identification information of the service API for which invocation is requested. The service API identification is part of the specific service API invocation request. | +| AEF identity information | M | Identity information of the entity requesting the routing information | + +#### 8.27.2.2 Obtain routing information response + +Table 8.27.2.2-1 describes the information flow dynamic routing information response from the CAPIF core function to the API exposing function. + +**Table 8.27.2.2-1: Obtain routing information response** + +| Information element | Status | Description | +|--------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service API identification information | M | The identification information of the service API for which invocation is requested. | +| Routing rule(s) information for service API invocation | M | Indicates the routing rule(s) for service API invocation, e.g., mapping of IP address range and AEF identity, or mapping of area serving the service API and AEF information. | + +### 8.27.3 Procedure + +Figure 8.27.3-1 illustrates the procedure for dynamically routing the service API invocation from the AEF acting as service communication entry point to the destination AEF for handling service API. + +Pre-conditions: + +1. The API invoker has performed the service discovery and received the details of the service API which includes the information about the service communication entry point of the AEF-1 in the CAPIF. +2. The API invoker is authenticated and authorized to use the service API. +3. The AEF-1 is the AEF acting as service communication entry point for the service API, and AEF-2 is one of the multiple destination AEF which provides the service API. + +![Sequence diagram illustrating the procedure for dynamic routing of service API invocation. The diagram shows four lifelines: API invoker, AEF-1, CAPIF core function, and AEF-2. The sequence of messages is: 1. Service API invocation request from API invoker to AEF-1; 2. Obtain routing information request from AEF-1 to CAPIF core function; 3. Obtain routing information response from CAPIF core function to AEF-1; 4. Determine the destination AEF for forwarding the service API invocation request (internal step in AEF-1); 5. Service API invocation request from AEF-1 to AEF-2; 6. Service API invocation response from AEF-2 to AEF-1; 7. Service API invocation response from AEF-1 to API invoker.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant AEF-1 + participant CAPIF core function + participant AEF-2 + Note right of AEF-1: 4. Determine the destination AEF for forwarding the service API invocation request + API invoker->>AEF-1: 1. Service API invocation request + AEF-1->>CAPIF core function: 2. Obtain routing information request + CAPIF core function-->>AEF-1: 3. Obtain routing information response + AEF-1->>AEF-2: 5. Service API invocation request + AEF-2-->>AEF-1: 6. Service API invocation response + AEF-1-->>API invoker: 7. Service API invocation response + +``` + +Sequence diagram illustrating the procedure for dynamic routing of service API invocation. The diagram shows four lifelines: API invoker, AEF-1, CAPIF core function, and AEF-2. The sequence of messages is: 1. Service API invocation request from API invoker to AEF-1; 2. Obtain routing information request from AEF-1 to CAPIF core function; 3. Obtain routing information response from CAPIF core function to AEF-1; 4. Determine the destination AEF for forwarding the service API invocation request (internal step in AEF-1); 5. Service API invocation request from AEF-1 to AEF-2; 6. Service API invocation response from AEF-2 to AEF-1; 7. Service API invocation response from AEF-1 to API invoker. + +**Figure 8.27.3-1: Procedure for dynamic routing of service API invocation** + +1. The API invoker performs service API invocation according to the interface of the service API by sending a service API invocation request towards the AEF-1 which exposes the service API towards the API invoker, and acts as topology hiding entity. +2. If the routing rule information for the service API invocation is not available, the AEF-1 sends obtain routing information request to the CAPIF core function. +3. The CAPIF core function creates routing rule information for the service API and sends obtain routing information response with the routing rule information. + +NOTE: Steps 2 and 3 can be performed before step 1 and after receiving the API topology hiding notify as described in subclause 8.24.3. + +4. The AEF-1 further resolves the actual destination of the service API address information (AEF-2) according to the routing rule information and the invocation parameters in service API invocation request. +5. The AEF-1 forwards the incoming service API invocation request to AEF-2. +6. The AEF-2 returns the service API invocation response to AEF-1. +7. The AEF-1 sends the service API invocation response to the API invoker. + +## 8.28 Registering the API provider domain functions on the CAPIF + +### 8.28.1 General + +The procedure in this subclause corresponds to the architectural requirements for registering the API provider domain functions on the CAPIF. This procedure registers the API provider domain functions as authorized users of the CAPIF functionalities. + +**Editor's Note:** The security aspects of this procedure are FFS in SA3. + +### 8.28.2 Information flows + +#### 8.28.2.1 Registration request + +Table 8.28.2.1-1 describes the information flow, registration request, from the API management function to the CAPIF core function. + +Table 8.28.2.1-1: Registration request + +| Information element | Status | Description | +|---------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------| +| List of API provider domain functions | M | List of API provider domain functions including role (e.g. AEF, APF, AMF) and, if required, specific security information. | +| API provider name | O | The API provider name uniquely identifies an API provider (e.g. Internet Service Provider). | +| Security information | M | Information for CAPIF core function to validate the registration request | + +## 8.28.2.2 Registration response + +Table 8.28.2.2-1 describes the information flow, registration response, from the CAPIF core function to the API management function. + +Table 8.28.2.2-1: Registration response + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| List of identities | M
(see NOTE 1) | List of identities, for each successfully registered API provider domain function and any specific security information. | +| Security information | O | Information to be used by the API provider domain function in subsequent CAPIF API invocations. Provided when registration is successful. | +| Reason | O
(see NOTE 2) | Information related to registration result specific to individual API provider domain functions. Provided when the registration fails. | +| NOTE 1: Information element shall be present when at least one registration request is successful.
NOTE 2: Information element may be present when at least one registration requests fail. | | | + +## 8.28.3 Procedure + +Figure 8.28.3-1 illustrates the procedure for registering API provider domain functions on the CAPIF core function. + +![Sequence diagram illustrating the procedure for registration of API provider domain functions on CAPIF. The diagram shows four lifelines: API provider domain functions (stack), API management function, CAPIF core function, and a block for handling the response. The sequence is: 1. Registration request from API management function to CAPIF core function; 2. Validation of the registration request and subsequent processing of the request by CAPIF core function; 3. Registration response from CAPIF core function to API management function; 4. Handling of registration response by the API management function.](8fe194ec0e70ac418890f8f1ad02a102_img.jpg) + +``` + +sequenceDiagram + participant APDF as API provider domain functions + participant AMF as API management function + participant CCF as CAPIF core function + Note right of AMF: *API provider domain + + AMF->>CCF: 1. Registration request + Note right of CCF: 2. Validation of the registration request and subsequent processing of the request + CCF->>AMF: 3. Registration response + Note right of AMF: 4. Handling of registration response + +``` + +Sequence diagram illustrating the procedure for registration of API provider domain functions on CAPIF. The diagram shows four lifelines: API provider domain functions (stack), API management function, CAPIF core function, and a block for handling the response. The sequence is: 1. Registration request from API management function to CAPIF core function; 2. Validation of the registration request and subsequent processing of the request by CAPIF core function; 3. Registration response from CAPIF core function to API management function; 4. Handling of registration response by the API management function. + +Figure 8.28.3-1: Procedure for registration of API provider domain functions on CAPIF + +1. For registration of API provider domain functions on the CAPIF core function, the API management function sends a registration request to the CAPIF core function. The registration request contains a list of information about all the API provider domain functions, which require registration on the CAPIF core function. +2. The CAPIF core function validates the received request and generates the identity and other security related information for all the API provider domain functions listed in the registration request. +3. The CAPIF core function sends the generated information in the registration response message to the API management function. +4. The API management function configures the received information to the individual API provider domain functions. + +## 8.29 Update registration information of the API provider domain functions on the CAPIF + +### 8.29.1 General + +The procedure in this subclause corresponds to the architectural requirements for update of the registration information of the API provider domain functions on the CAPIF. + +**Editor's Note:** The security aspects of this procedure are FFS in SA3. + +### 8.29.2 Information flows + +#### 8.29.2.1 Registration update request + +Table 8.29.2.1-1 describes the information flow, registration update request, from the API management function to the CAPIF core function. + +**Table 8.29.2.1-1: Registration update request** + +| Information element | Status | Description | +|--------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| List of API provider domain functions requiring update | M | List of API provider domain functions requiring updates, including role (e.g. AEF, APF, AMF) and, if required, specific security information. | +| Security information | M | Information for CAPIF core function to validate the registration request | + +#### 8.29.2.2 Registration update response + +Table 8.29.2.2-1 describes the information flow, registration update response, from the CAPIF core function to the API management function. + +Table 8.29.2.2-1: Registration update response + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| List of identities | M
(see NOTE 1) | List of identities, for each successfully updated API provider domain function and any specific security information. | +| Security information | O | Information to be used by the API provider domain function in subsequent CAPIF API invocations. Provided when registration update is successful. | +| Reason | O
(see NOTE 2) | Information related to registration update result specific to individual API provider domain functions. Provided when the registration fails. | +| NOTE 1: Information element shall be present when at least one registration update request is successful. | | | +| NOTE 2: Information element may be present when at least one registration update requests fail. | | | + +### 8.29.3 Procedure + +Figure 8.29.3-1 illustrates the procedure for updating the registration information of the API provider domain functions on the CAPIF core function. + +![Sequence diagram illustrating the procedure for update of registration information of API provider domain functions on CAPIF. The diagram shows four steps: 1. Registration update request from API management function to CAPIF core function; 2. Validation of the registration update request and subsequent processing of the request by CAPIF core function; 3. Registration update response from CAPIF core function to API management function; 4. Handling of registration update response by API management function. The API management function is associated with multiple API provider domain functions.](832a0ce332e784fe80289e9f00f56574_img.jpg) + +``` + +sequenceDiagram + participant APDF as API provider domain function + participant AMF as API management function + participant CCF as CAPIF core function + Note left of AMF: *API provider domain + AMF->>CCF: 1. Registration update request + CCF->>AMF: 2. Validation of the registration update request and subsequent processing of the request + CCF->>AMF: 3. Registration update response + AMF->>APDF: 4. Handling of registration update response + +``` + +Sequence diagram illustrating the procedure for update of registration information of API provider domain functions on CAPIF. The diagram shows four steps: 1. Registration update request from API management function to CAPIF core function; 2. Validation of the registration update request and subsequent processing of the request by CAPIF core function; 3. Registration update response from CAPIF core function to API management function; 4. Handling of registration update response by API management function. The API management function is associated with multiple API provider domain functions. + +Figure 8.29.3-1: Procedure for update of registration information of API provider domain functions on CAPIF + +1. For updating the registration information of API provider domain functions on the CAPIF core function, the API management function sends a registration update request to the CAPIF core function. The registration update request contains a list of information about all the API provider domain functions, which require registration update on the CAPIF core function. +2. The CAPIF core function validates the received request and updates the identity and other security related information for all the API provider domain functions listed in the registration request. +3. The CAPIF core function sends the updated information in the registration update response message to the API management function. +4. The API management function configures the received information to the individual API provider domain functions. + +## 8.30 Deregistering the API provider domain functions on the CAPIF + +### 8.30.1 General + +The procedure in this subclause corresponds to the architectural requirements for deregistering the API provider domain functions on the CAPIF. This procedure deregisters the API provider domain functions as authorized users of the CAPIF functionalities. + +*Editor's Note: The security aspects of this procedure are FFS in SA3.* + +### 8.30.2 Information flows + +#### 8.30.2.1 Deregistration request + +Table 8.30.2.1-1 describes the information flow, deregistration request, from the API management function to the CAPIF core function. + +**Table 8.30.2.1-1: Deregistration request** + +| Information element | Status | Description | +|----------------------|--------|----------------------------------------------------------------------------| +| Security information | M | Information for CAPIF core function to validate the deregistration request | + +#### 8.30.2.2 Deregistration response + +Table 8.30.2.2-1 describes the information flow, deregistration response, from the CAPIF core function to the API management function. + +**Table 8.30.2.2-1: Deregistration response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the deregistration operation | + +### 8.30.3 Procedure + +Figure 8.30.3-1 illustrates the procedure for deregistering API provider domain functions on the CAPIF core function. + +![Sequence diagram illustrating the procedure for deregistration of API provider domain functions on CAPIF. The diagram shows four steps: 1. Deregistration request from API management function to CAPIF core function; 2. Validation of the request by CAPIF core function; 3. Deregistration response from CAPIF core function to API management function; 4. Handling of the response by the API management function, which then propagates it to individual API provider domain functions.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` + +sequenceDiagram + participant APIMF as API management function + participant CCF as CAPIF core function + participant APDF as API provider domain function + Note left of APDF: *API provider domain + APIMF->>CCF: 1. Deregistration request + CCF->>APDF: 2. Validation of the deregistration request and subsequent processing of the request + CCF->>APIMF: 3. Deregistration response + APIMF->>APDF: 4. Handling of deregistration response + +``` + +Sequence diagram illustrating the procedure for deregistration of API provider domain functions on CAPIF. The diagram shows four steps: 1. Deregistration request from API management function to CAPIF core function; 2. Validation of the request by CAPIF core function; 3. Deregistration response from CAPIF core function to API management function; 4. Handling of the response by the API management function, which then propagates it to individual API provider domain functions. + +**Figure 8.30.3-1: Procedure for deregistration of API provider domain functions on CAPIF** + +1. For deregistration of API provider domain functions on the CAPIF core function, the API management function sends a deregistration request to the CAPIF core function. +2. The CAPIF core function validates the received request and processes the deregistration request. +3. The CAPIF core function sends a deregistration response message to the API management function. +4. The API management function processes the deregistration to the individual API provider domain functions. + +## 8.31 API invoker obtaining authorization from resource owner + +### 8.31.1 General + +CAPIF may authorize the API invoker to invoke the service API based on the authorization information from the resource owner given before the API invocation. + +Clause 8.31.3 shows the procedure for obtaining the authorization information. + +### 8.31.2 Information flows + +NOTE: The security aspects of this procedure are specified in TS 33.122 [12]. + +### 8.31.3 Procedure + +Figure 8.31.3-1 illustrates the procedure for API invoker obtaining authorization from resource owner. + +Pre-conditions: + +1. The resource owner can communicate with the API invoker. +2. The service API access requires obtaining authorization from resource owner. + +![Sequence diagram illustrating the procedure for API invoker obtaining authorization from resource owner. The diagram shows four lifelines: API invoker, Resource Owner, CAPIF core function/Authorization function, and API exposing function. The sequence of messages is: 1. API invoker requests authorization information from the CAPIF core function; 2. The CAPIF core function sends a service API invocation request with the authorization information to the API exposing function; 3. The API exposing function sends a service API invocation response back to the API invoker.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant Resource Owner + participant CAPIF core function/Authorization function + participant API exposing function + Note over API invoker, CAPIF core function/Authorization function: 1. API invoker requests authorization information + Note over CAPIF core function/Authorization function, API exposing function: 2. Service API invocation request with the authorization information + Note over API exposing function, API invoker: 3. Service API invocation response + +``` + +Sequence diagram illustrating the procedure for API invoker obtaining authorization from resource owner. The diagram shows four lifelines: API invoker, Resource Owner, CAPIF core function/Authorization function, and API exposing function. The sequence of messages is: 1. API invoker requests authorization information from the CAPIF core function; 2. The CAPIF core function sends a service API invocation request with the authorization information to the API exposing function; 3. The API exposing function sends a service API invocation response back to the API invoker. + +**Figure 8.31.3-1: Procedure for API invoker obtaining authorization from resource owner** + +1. The API invoker requests to obtain resource owner authorization information to invoke the service API exposed by the API exposing function. The authorization function provides the authorization by involving the resource owner. + +NOTE: The detailed procedure to obtain the resource owner's authorization information is specified in TS 33.122 [12]. + +2. The API invoker sends service API invocation request to the API exposing function with the resource owner authorization information received in step 1. +3. The API invoker receives the service API invocation response resulting from the service API invocation once the API exposing function has checked whether the API invoker is authorized to invoke that service API based on the authorization information. + +## 8.32 Reducing authorization information inquiry in a nested API invocation + +### 8.32.1 General + +The nested API invocation scenario is a scenario where the first API invocation towards the API exposing function 1 triggers this API exposing function to request another API invocation towards the API exposing function 2, which is in the same API provider domain that the API exposing function 1. Some service APIs may require invoking another service APIs. For example, if the API invoker invokes SEAL locationInfoRetrieval API, the location management server (acting as an API exposing server for the API invoker and as an API invoker for the NEF) may invoke NEF API to retrieve UE location information from 5GC. The CAPIF may reduce the authorization information inquiries for a nested API invocation scenario using procedure described in clause 8.32.3. + +### 8.32.2 Information flows + +NOTE: The security aspects of this procedure are specified in TS 33.122 [12]. + +### 8.32.3 Procedure + +Figure 8.32.3-1 illustrates the procedure to obtain authorization information in a nested API invocation, in which an API exposing function receiving the service API invocation request interacts with another API exposing function to provide the service. + +Pre-conditions: + +1. The resource owner can communicate with the API invoker. +2. The API exposing functions 1 and 2 are in the same trust domain. + +![Sequence diagram illustrating the procedure for obtaining authorization information in a nested API invocation. The diagram shows five lifelines: API invoker, Resource owner, CAPIF core function/Authorization function, API exposing function 1, and API exposing function 2. The sequence of messages is: 1. API invoker requests authorization information from CAPIF core function; 2. API invoker sends service API invocation request with authorization information to API exposing function 1; 3. API exposing function 1 decides to invoke a service API provided by API exposing function 2; 4. API exposing function 1 (acting as an API invoker) obtains authorization information from CAPIF core function; 5. API exposing function 1 sends service API invocation request with authorization information to API exposing function 2; 6. API exposing function 2 sends service API invocation response to API exposing function 1; 7. API exposing function 1 sends service API invocation response to API invoker.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +``` + +sequenceDiagram + participant API invoker + participant Resource owner + participant CAPIF core function/Authorization function + participant API exposing function 1 + participant API exposing function 2 + + Note over API invoker, CAPIF core function/Authorization function: 1. API invoker requests authorization information + API invoker->>API exposing function 1: 2. Service API invocation request with the authorization information + Note over API exposing function 1, API exposing function 2: 3. API exposing function 1 decides to invoke a service API provided by the API exposing function 2 + Note over API exposing function 1, CAPIF core function/Authorization function: 4. API exposing function 1 (acting as an API invoker) obtains the authorization information + API exposing function 1->>API exposing function 2: 5. Service API invocation request with the authorization information + API exposing function 2-->>API exposing function 1: 6. Service API invocation response + API exposing function 1-->>API invoker: 7. Service API invocation response + +``` + +Sequence diagram illustrating the procedure for obtaining authorization information in a nested API invocation. The diagram shows five lifelines: API invoker, Resource owner, CAPIF core function/Authorization function, API exposing function 1, and API exposing function 2. The sequence of messages is: 1. API invoker requests authorization information from CAPIF core function; 2. API invoker sends service API invocation request with authorization information to API exposing function 1; 3. API exposing function 1 decides to invoke a service API provided by API exposing function 2; 4. API exposing function 1 (acting as an API invoker) obtains authorization information from CAPIF core function; 5. API exposing function 1 sends service API invocation request with authorization information to API exposing function 2; 6. API exposing function 2 sends service API invocation response to API exposing function 1; 7. API exposing function 1 sends service API invocation response to API invoker. + +**Figure 8.32.3-1: Procedure for obtaining authorization information in a nested API invocation** + +1. The API invoker requests authorization information to invoke the service API exposed by API exposing function 1. + +**NOTE:** This step may use either the existing procedure to obtain authorization to access service API specified in clause 8.11 or the procedure that involves the resource owner client to get authorization information. For the latter case, the mechanisms to support interactions with Resource owner are specified in 3GPP TS 33.122 [12], with further possible CAPIF support for these mechanisms being out of scope of the current release. + +2. The API invoker sends service API invocation request to the API exposing function 1 with the authorization information received in step 1. +3. Based on the service API invocation request, the API exposing function 1 decides to invoke another service API exposed by the API exposing function 2. +4. The API exposing function 1, acting as an API invoker, obtains the authorization information to access the service API exposed by the API exposing function 2. +5. The API invoker sends service API invocation request to API exposing function 2 with the authorization information received in step 4. +6. The API exposing function 2, acting as an API invoker, receives the service API invocation response resulting from the service API invocation once API exposing function 2 has checked whether the API invoker is authorized to invoke that service API based on the authorization information. +7. The API invoker receives the service API invocation response resulting from the service API invocation. + +## 9 API consistency guidelines + +### 9.1 General + +This clause specifies the API consistency guidelines for all northbound APIs utilizing CAPIF architecture. The guidelines are categorized as follows: + +- fundamental API guidelines, applicable to all northbound APIs utilizing CAPIF; and +- architecture design considerations, applicable to all northbound APIs utilizing CAPIF. + +The API guidelines are also applicable for CAPIF APIs specified in the current specification. + +## 9.2 Fundamental API Guidelines + +The specification of each northbound API utilizing the common API framework should define: + +1. the function of the API; +2. the resource(s) or endpoints involved; +3. the list of supported operations and their usage; +4. the list of input and output parameters along with applicable schemas, as required; +5. the list of supported response codes; +6. the behaviour of the network entity exposing the APIs (e.g. the CAPIF core function or the API exposing function) for each supported operation; +7. the list of applicable data types; and +8. the list of applicable protocols and data serialization formats. + +In order to facilitate the consistency of the northbound APIs utilizing the common API framework it is recommended to adopt the guidelines which define the following: + +1. consistent nomenclature for the operations, data structures and resources/endpoints; +2. design principles for the use of operations for common tasks; and +3. a template for the consistent documentation of APIs. + +The northbound APIs utilizing the common API framework should support the following properties: + +1. be extensible, such that it is possible to accommodate future requirements, including vendor-specific needs; + +NOTE: The extension does not replace any existing function in Northbound APIs. + +2. support access control mechanisms; +3. support charging, if applicable; and +4. be backward and forward compatible with different versions of the same API. + +The guidelines above are generic with regard to the API architecture. They are valid for network APIs that follow the RESTful architectural style and that expose resources towards the API invoker, as well as for network APIs of other architectures that expose general network endpoints towards the API invoker. A network endpoint represents one end of a communication channel through which the API consumer communicates with the API producer, using messages of a protocol defined by the API architecture. A resource is identified, and the corresponding endpoint is addressed, by a resource identifier (such as a URI). + +## 9.3 Architecture design considerations + +Northbound APIs utilizing common API framework should adhere to RESTful architecture, whenever possible. Service operations can use custom API operations (RPC-style interaction), when it is seen a better fit for the style of interaction to model, e.g. non-CRUD service operations. + +NOTE: The selection of a particular API style is specific to each API implementation, and subject to Stage 3 scope. + +The API design: + +1. should have a uniform interface that conveys the resource/data model of the API to its client developers and: + - a. the implementation of the resource(s)/operations involved in the APIs should be hidden from the client, and adequate operations should be designed to operate on the resource(s)/data; + - b. any single API should be atomic; + - c. all resources/operations involved in APIs should be accessible through a common approach, and resources/data should be similarly modified using a consistent approach; +2. should allow the client (such as the API invoker) and the server (such as the CAPIF core function or the API exposing function) to evolve independently, i.e. the client should not have to be aware of the execution aspects of the APIs on the server; +3. should be stateless such that each request from the client (such as the API invoker) to the server (such as the CAPIF core function or the API exposing function) contains all of the information necessary for the server to understand the request; +4. should define the usage of standard operations, such as Create, Read, Update and Delete, consistently along with the applicable response codes; +5. should allow to label responses as cacheable or non-cacheable, to improve network efficiency by supporting caching in the client (such as the API invoker), if applicable in the API architecture; +6. should prevent unwanted modification of the resources/data during invocation of APIs; and +7. should support version control. + +--- + +## 10 CAPIF core function APIs + +### 10.1 General + +Table 10.1-1 illustrates the CAPIF core function APIs. + +Table 10.1-1: List of CAPIF core function APIs + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|-----------------------------------|---------------------------------|--------------------------------------------------------------------------------------|--------------------| +| CAPIF_Discover_Service_API | Discover_Service_API | API Invoker, CAPIF core function | Request/ Response | +| | Subscribe_Event | API Invoker | Request/ Response | +| | Update_Event_Subscription | API Invoker | Request/ Response | +| | Notify_Event | API Invoker | Notify | +| | Unsubscribe_Event | API Invoker | Request/ Response | +| CAPIF_Publish_Service_API | Publish_Service_API | API Publishing Function, CAPIF core function | Request/ Response | +| | Unpublish_Service_API | API Publishing Function, CAPIF core function | Request/ Response | +| | Update_Service_API | API Publishing Function, CAPIF core function | Request/ Response | +| | Get_Service_API | API Publishing Function, CAPIF core function | Request/ Response | +| | Subscribe_Event | API Publishing Function | Request/ Response | +| | Update_Event_Subscription | API Publishing Function | Request/ Response | +| | Notify_Event | API Publishing Function | Notify | +| CAPIF_Events API | Unsubscribe_Event | API Publishing Function | Request/ Response | +| | Subscribe_Event | API Invoker, API Publishing Function, API Management Function, API Exposing Function | Request/ Response | +| | Update_Event_Subscription | API Invoker, API Publishing Function, API Management Function, API Exposing Function | Request/ Response | +| | Notify_Event | API Invoker, API Publishing Function, API Management Function, API Exposing Function | Notify | +| CAPIF_API_Invoker_management API | Unsubscribe_Event | API Invoker, API Publishing Function, API Management Function, API Exposing Function | Request/ Response | +| | Onboard_API_Invoker | API Invoker | Request/ Response | +| | Offboard_API_Invoker | API Invoker | Request/ Response | +| | Subscribe_Event | API Management Function | Request/ Response | +| | Update_Event_Subscription | API Management Function | Request/ Response | +| | Notify_Event | API Management Function | Notify | +| CAPIF_API_Provider_Management_API | Unsubscribe_Event | API Management Function | Request/ Response | +| | Register_API_Provider | API Management Function | Request/Response | +| | Update_API_Provider | API Management Function | Request/Response | +| CAPIF_Security API | Deregister_API_Provider | API Management Function | Request/Response | +| | Obtain_Security_Method | API Invoker | Request/ Response | +| | Obtain_Authorization | API Invoker | Request/ Response | +| | Obtain_API_Invoker_Info | API Exposing Function | Request/ Response | +| CAPIF_Monitoring API | Revoke_Authorization | API Exposing Function | Request/ Response | +| | Subscribe_Event | API Management Function | Request/ Response | +| | Update_Event_Subscription | API Management Function | Request/ Response | +| | Notify_Monitoring_Service_Event | API Management Function | Notify | +| CAPIF_Logging_API_Invocation API | Unsubscribe_Event | API Management Function | Request/ Response | +| | Log_API_Invocation | API exposing function | Request/ Response | + +| | | | | +|---------------------------------|------------------------------|-------------------------|-------------------| +| CAPIF_Auditing API | Query_API_Invocation_Log | API management function | Request/ Response | +| CAPIF_Access_Control_Policy API | Obtain_Access_Control_Policy | API exposing function | Request/Response | +| CAPIF_Routing_Info API | Obtain_Routing_Info | API exposing function | Request/Response | + +## 10.2 CAPIF\_Discover\_Service\_API API + +### 10.2.1 General + +**API description:** This API enables the API invoker to communicate with the CAPIF core function to discover the published service API information over CAPIF-1 or CAPIF-1e. + +### 10.2.2 Discover\_Service\_API operation + +**API operation name:** Discover\_Service\_API + +**Description:** Provides the published service APIs information. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.7.2.1. + +**Outputs:** Refer subclause 8.7.2.2. + +See subclause 8.7.3 for the details of usage of this API operation. + +### 10.2.3 Subscribe\_Event operation + +**API operation name:** Subscribe\_Event + +**Description:** Provides subscription to the CAPIF related event information. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.8.2.1. + +**Outputs:** Refer subclause 8.8.2.2. + +See subclause 8.8.3 for the details of usage of this API operation. + +### 10.2.4 Notify\_Event operation + +**API operation name:** Notify\_Event + +**Description:** Provides the relevant CAPIF event information to the subscribed entities. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.8.2.3. + +**Outputs:** Refer subclause 8.8.2.4. + +See subclause 8.8.4 for the details of usage of this API operation. + +### 10.2.5 Unsubscribe\_Event operation + +**API operation name:** Unsubscribe\_Event + +**Description:** Unsubscription to the CAPIF event information. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.8.2.5. + +**Outputs:** Refer subclause 8.8.2.6. + +See subclause 8.8.5 for the details of usage of this API operation. + +## 10.2.6 Update\_Event\_Subscription operation + +**API operation name:** Update\_Event\_Subscription + +**Description:** Updates a subscription to CAPIF related event information. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.8.2.7. + +**Outputs:** Refer subclause 8.8.2.8. + +See subclause 8.8.5a for the details of usage of this API operation. + +## 10.3 CAPIF\_Publish\_Service\_API API + +### 10.3.1 General + +**API description:** This API enables the API publishing function to communicate with the CAPIF core function to publish the service API information and manage the published service API information over CAPIF-4. + +NOTE: Stage 3 can decide whether the API for CAPIF\_Publish\_Service\_API can be enabled over CAPIF-4. + +### 10.3.2 Publish\_Service\_API operation + +**API operation name:** Publish\_Service\_API + +**Description:** Publish the service API information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.3.2.1. + +**Outputs:** Refer subclause 8.3.2.2. + +See subclause 8.3.3 for the details of usage of this API operation. + +### 10.3.3 Unpublish\_Service\_API operation + +**API operation name:** Unpublish\_Service\_API + +**Description:** Remove the published service API information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.4.2.1. + +**Outputs:** Refer subclause 8.4.2.2. + +See subclause 8.4.3 for the details of usage of this API operation. + +### 10.3.4 Update\_Service\_API operation + +**API operation name:** Update\_Service\_API + +**Description:** Update the published service API information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.6.2.1. + +**Outputs:** Refer subclause 8.6.2.2. + +See subclause 8.6.3 for the details of usage of this API operation. + +### 10.3.5 Get\_Service\_API operation + +**API operation name:** Get\_Service\_API + +**Description:** Retrieve the published service API information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.5.2.1. + +**Outputs:** Refer subclause 8.5.2.2. + +See subclause 8.5.3 for the details of usage of this API operation. + +### 10.3.6 Subscribe\_Event operation + +**API operation name:** Subscribe\_Event + +**Description:** Provides subscription to the CAPIF related event information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.8.2.1. + +**Outputs:** Refer subclause 8.8.2.2. + +See subclause 8.8.3 for the details of usage of this API operation. + +### 10.3.7 Notify\_Event operation + +**API operation name:** Notify\_Event + +**Description:** Provides the relevant CAPIF event information to the subscribed entities. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.8.2.3. + +**Outputs:** Refer subclause 8.8.2.4. + +See subclause 8.8.4 for the details of usage of this API operation. + +### 10.3.8 Unsubscribe\_Event operation + +**API operation name:** Unsubscribe\_Event + +**Description:** Unsubscription to the CAPIF event information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.8.2.5. + +**Outputs:** Refer subclause 8.8.2.6. + +See subclause 8.8.5 for the details of usage of this API operation. + +### 10.3.9 Update\_Event\_Subscription operation + +**API operation name:** Update\_Event\_Subscription + +**Description:** Updates a subscription to CAPIF related event information. + +**Known Consumers:** API publishing function. + +**Inputs:** Refer subclause 8.8.2.7. + +**Outputs:** Refer subclause 8.8.2.8. + +See subclause 8.8.5a for the details of usage of this API operation. + +## 10.4 CAPIF\_Events API + +### 10.4.1 General + +**API description:** This API enables the API subscribing entity to communicate with the CAPIF core function to subscribe to and unsubscribe from CAPIF events and receive subsequent notification of CAPIF events. This API is used for the subscription to and notifications of those CAPIF events that are not bound to any of the other CAPIF core function APIs. The following are the key functionalities: + +- API invoker subscribes to CAPIF events over CAPIF-1 or CAPIF-1e. +- API invoker receives notifications for subscribed CAPIF events over CAPIF-1 or CAPIF-1e. +- API invoker unsubscribes from CAPIF events over CAPIF-1 or CAPIF-1e. +- API invoker updates subscriptions for CAPIF events over CAPIF-1 or CAPIF-1e. +- API exposing function subscribes to CAPIF events over CAPIF-3. +- API exposing function receives notifications for subscribed CAPIF events over CAPIF-3. +- API exposing function unsubscribes from CAPIF events over CAPIF-3. +- API exposing function updates subscriptions for CAPIF events over CAPIF-3. +- API publishing function subscribes to CAPIF events over CAPIF-4. +- API publishing function receives notifications for subscribed CAPIF events over CAPIF-4. +- API publishing function unsubscribes from CAPIF events over CAPIF-4. +- API publishing function updates subscriptions for CAPIF events over CAPIF-4. +- API management function subscribes to CAPIF events over CAPIF-5. +- API management function receives notifications for subscribed CAPIF events over CAPIF-5. +- API management function unsubscribes from CAPIF events over CAPIF-5. +- API management function updates subscriptions for CAPIF events over CAPIF-5. + +NOTE: Stage 3 can further decide if CAPIF\_Events API can be further fine grained into more APIs. + +### 10.4.2 Subscribe\_Event operation + +**API operation name:** Subscribe\_Event + +**Description:** Provides subscription to the CAPIF related event information. + +**Known Consumers:** API invoker, API publishing function, API management function, API exposing function. + +**Inputs:** Refer subclause 8.8.2.1. + +**Outputs:** Refer subclause 8.8.2.2. + +See subclause 8.8.3 for the details of usage of this API operation. + +### 10.4.3 Notify\_Event operation + +**API operation name:** Notify\_Event + +**Description:** Provides the relevant CAPIF event information to the subscribed entities. + +**Known Consumers:** API invoker, API publishing function, API management function, API exposing function. + +**Inputs:** Refer subclause 8.8.2.3. + +**Outputs:** Refer subclause 8.8.2.4. + +See subclause 8.8.4 for the details of usage of this API operation. + +### 10.4.4 Unsubscribe\_Event operation + +**API operation name:** Unsubscribe\_Event + +**Description:** Unsubscription to the CAPIF event information. + +**Known Consumers:** API invoker, API publishing function, API management function, API exposing function. + +**Inputs:** Refer subclause 8.8.2.5. + +**Outputs:** Refer subclause 8.8.2.6. + +See subclause 8.8.5 for the details of usage of this API operation. + +### 10.4.5 Update\_Event\_Subscription operation + +**API operation name:** Update\_Event\_Subscription + +**Description:** Updates a subscription to CAPIF related event information. + +**Known Consumers:** API invoker, API publishing function, API management function, API exposing function. + +**Inputs:** Refer subclause 8.8.2.7. + +**Outputs:** Refer subclause 8.8.2.8. + +See subclause 8.8.5a for the details of usage of this API operation. + +## 10.5 CAPIF\_API\_invoker\_management API + +### 10.5.1 General + +**API description:** This API enables the API invoker to communicate with the CAPIF core function to enroll as a registered user of CAPIF and manage the enrollment information over CAPIF-1 or CAPIF-1e. + +### 10.5.2 Onboard\_API\_Invoker operation + +**API operation name:** Onboard\_API\_Invoker + +**Description:** Enrolls the API invoker as a recognized user of the CAPIF. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.1.2.1. + +**Outputs:** Refer subclause 8.1.2.2. + +See subclause 8.1.3 for the details of usage of this API operation. + +### 10.5.3 Offboard\_API\_Invoker operation + +**API operation name:** Offboard\_API\_Invoker + +**Description:** Cancels enrollment of the API invoker as a recognized user of the CAPIF. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.2.2.1. + +**Outputs:** Refer subclause 8.2.2.2. + +See subclause 8.2.3 for the details of usage of this API operation. + +### 10.5.4 Subscribe\_Event operation + +**API operation name:** Subscribe\_Event + +**Description:** Provides subscription to the CAPIF related event information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.1. + +**Outputs:** Refer subclause 8.8.2.2. + +See subclause 8.8.3 for the details of usage of this API operation. + +### 10.5.5 Notify\_Event operation + +**API operation name:** Notify\_Event + +**Description:** Provides the relevant CAPIF event information to the subscribed entities. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.3. + +**Outputs:** Refer subclause 8.8.2.4. + +See subclause 8.8.4 for the details of usage of this API operation. + +### 10.5.6 Unsubscribe\_Event operation + +**API operation name:** Unsubscribe\_Event + +**Description:** Unsubscription to the CAPIF event information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.5. + +**Outputs:** Refer subclause 8.8.2.6. + +See subclause 8.8.5 for the details of usage of this API operation. + +## 10.5.7 Update\_Event\_Subscription operation + +**API operation name:** Update\_Event\_Subscription + +**Description:** Updates a subscription to CAPIF related event information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.7. + +**Outputs:** Refer subclause 8.8.2.8. + +See subclause 8.8.5a for the details of usage of this API operation. + +## 10.6 CAPIF\_Security API + +### 10.6.1 General + +**API description:** This API enables the API invoker to communicate with the CAPIF core function to authenticate and obtain authorization to access service APIs over CAPIF-1 or CAPIF-1e. This API also enables the API exposing function (AEF) to obtain API invoker information and revoke API invoker authorization over CAPIF-3. + +### 10.6.2 Obtain\_Security\_Method operation + +**API operation name:** Obtain\_Security\_Method + +**Description:** Obtain information about service API security method with CAPIF core function for service API invocations. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.10.2. + +**Outputs:** Refer subclause 8.10.2. + +See subclause 8.10.3 for the details of usage of this API operation. + +### 10.6.3 Obtain\_Authorization operation + +**API operation name:** Obtain\_Authorization + +**Description:** Provides the authorization information to access relevant service API. + +**Known Consumers:** API invoker. + +**Inputs:** Refer subclause 8.11.2. + +**Outputs:** Refer subclause 8.11.2. + +See subclause 8.11.3 for the details of usage of this API operation. + +### 10.6.4 Obtain\_API\_Invoker\_Info operation + +**API operation name:** Obtain\_API\_Invoker\_Info + +**Description:** Obtains the API invoker information. + +**Known Consumers:** API exposing function. + +**Inputs:** Refer subclause 8.16.2.1. + +**Outputs:** Refer subclause 8.16.2.2. + +See subclause 8.16.3 for the details of usage of this API operation. + +## 10.6.5 Revoke\_Authorization operation + +**API operation name:** Revoke\_Authorization + +**Description:** Revokes API invoker authorization to access service API. + +**Known Consumers:** API exposing function. + +**Inputs:** Refer subclause 8.23.2. + +**Outputs:** Refer subclause 8.23.2. + +See subclause 8.23.3 for the details of usage of this API operation. + +# 10.7 CAPIF\_Monitoring API + +## 10.7.1 General + +**API description:** This API enables the API management function to communicate with the CAPIF core function to subscribe to and unsubscribe from CAPIF events related to monitoring and receive subsequent notification of CAPIF monitoring events over CAPIF-5. + +NOTE: Stage 3 can decide whether the API for CAPIF\_Monitoring can be enabled over CAPIF-5. + +## 10.7.2 Subscribe\_Event operation + +**API operation name:** Subscribe\_Event + +**Description:** Provides subscription to the CAPIF related event information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.1. + +**Outputs:** Refer subclause 8.8.2.2. + +See subclause 8.8.3 for the details of usage of this API operation. + +## 10.7.3 Notify\_Monitoring\_Service\_Event operation + +**API operation name:** Notify\_Monitoring\_Service\_Event + +**Description:** Provides the notification of the events related to monitoring service API invocations to the subscribed API management function. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.21.2.1. + +**Outputs:** Refer subclause 8.21.2.2. + +See subclause 8.21.3 for the details of usage of this API operation. + +## 10.7.4 Unsubscribe\_Event operation + +**API operation name:** Unsubscribe\_Event + +**Description:** Unsubscription to the CAPIF event information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.5. + +**Outputs:** Refer subclause 8.8.2.6. + +See subclause 8.8.5 for the details of usage of this API operation. + +## 10.7.5 Update\_Event\_Subscription operation + +**API operation name:** Update\_Event\_Subscription + +**Description:** Updates a subscription to CAPIF related event information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.8.2.7. + +**Outputs:** Refer subclause 8.8.2.8. + +See subclause 8.8.5a for the details of usage of this API operation. + +## 10.8 CAPIF\_Logging\_API\_Invocation API + +### 10.8.1 General + +**API description:** This API enables the API exposing function to communicate with the CAPIF core function to log the information related to service API invocation over CAPIF-3. + +NOTE: Stage 3 can decide whether the API for CAPIF\_Logging\_API\_Invocation can be enabled over CAPIF-3. + +### 10.8.2 Log\_API\_Invocation operation + +**API operation name:** Log\_API\_Invocation + +**Description:** Enables to log API invocation information. + +**Known Consumers:** API exposing function. + +**Inputs:** Refer subclause 8.19.2.1. + +**Outputs:** Refer subclause 8.19.2.2. + +See subclause 8.19.3 for the details of usage of this API operation. + +## 10.9 CAPIF\_Auditing API + +### 10.9.1 General + +**API description:** This API enables the API management function to communicate with the CAPIF core function to retrieve the log information related to service API invocation over CAPIF-5. + +NOTE: Stage 3 can decide whether the API for CAPIF\_Auditing can be enabled over CAPIF-5. + +### 10.9.2 Query\_API\_Invocation\_Log operation + +**API operation name:** Query\_API\_Invocation\_Log + +**Description:** Query the API invocation log information. + +**Known Consumers:** API management function. + +**Inputs:** Refer subclause 8.22.2.1. + +**Outputs:** Refer subclause 8.22.2.2. + +See subclause 8.22.3 for the details of usage of this API operation. + +## 10.10 CAPIF\_Access\_Control\_Policy API + +### 10.10.1 General + +**API description:** This API enables the API exposing function to obtain the policy to perform access control on the service API invocations. + +### 10.10.2 Obtain\_Access\_Control\_Policy operation + +**API operation name:** Obtain\_Access\_Control\_Policy + +**Description:** Allows obtaining the policy to perform access control on the service API invocations. + +**Known Consumers:** API exposing function. + +**Inputs:** Refer subclause 8.12.2.1. + +**Outputs:** Refer subclause 8.12.2.2. + +See subclause 8.12.3 for the details of usage of this API operation. + +## 10.11 CAPIF\_Routing\_Info API + +### 10.11.1 General + +**API description:** This API enables the API exposing function to obtain the routing information to forward the API invocation to another API exposing function. + +### 10.11.2 Obtain\_Routing\_Info operation + +**API operation name:** Obtain\_Routing\_Info + +**Description:** Allows obtaining the API routing information. + +**Known Consumers:** API exposing function. + +**Inputs:** Refer subclause 8.27.2.1. + +**Outputs:** Refer subclause 8.27.2.2. + +See subclause 8.27.3 for the details of usage of this API operation. + +## 10.12 CAPIF\_API\_provider\_management API + +### 10.12.1 General + +**API description:** This API enables the API Management Function to communicate with the CAPIF core function to register the API provider domain functions as authorized users of the CAPIF functionalities. + +### 10.12.2 Register\_API\_Provider operation + +**API operation name:** Register\_API\_Provider + +**Description:** Registers the API provider domain functions as authorized users of the CAPIF. + +**Known Consumers:** API Management Function. + +**Inputs:** Refer subclause 8.28.2.1. + +**Outputs:** Refer subclause 8.28.2.2. + +See subclause 8.28.3 for the details of usage of this API operation. + +### 10.12.3 Update\_API\_Provider operation + +**API operation name:** Update\_API\_Provider + +**Description:** Updates registration information of the API provider domain functions. + +**Known Consumers:** API Management Function. + +**Inputs:** Refer subclause 8.29.2.1. + +**Outputs:** Refer subclause 8.29.2.2. + +See subclause 8.29.3 for the details of usage of this API operation. + +### 10.12.4 Deregister\_API\_Provider operation + +**API operation name:** Deregister\_API\_Provider + +**Description:** Registers the API provider domain functions as authorized users of the CAPIF. + +**Known Consumers:** API Management Function. + +**Inputs:** Refer subclause 8.30.2.1. + +**Outputs:** Refer subclause 8.30.2.2. + +See subclause 8.30.3 for the details of usage of this API operation. + +## 11 API exposing function APIs + +### 11.1 General + +Table 11.1-1 illustrates the API exposing function APIs. + +**Table 11.1-1: List of API exposing function APIs** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|------------------|-------------------------|---------------------|--------------------| +| AEF_Security API | Revoke_Authorization | CAPIF Core Function | Request/ Response | +| | Initiate_Authentication | API Invoker | Request/ Response | + +### 11.2 AEF\_Security API + +#### 11.2.1 General + +**API description:** This API allows CAPIF core function to revoke access to service APIs and API invokers to request the authentication parameters necessary for authentication of the API invoker available with the API exposing function. + +## 11.2.2 Revoke\_Authorization operation + +**API operation name:** Revoke\_Authorization + +**Description:** Revokes API invoker authorization to access service API. + +**Known Consumers:** CAPIF core function. + +**Inputs:** Refer subclause 8.23.2. + +**Outputs:** Refer subclause 8.23.2. + +See subclause 8.23.4 for the details of usage of this API operation. + +## 11.2.3 Initiate\_Authentication operation + +**API operation name:** Initiate\_Authentication + +**Description:** Authentication between the API invoker and the AEF prior to service API invocation. + +**Known Consumers:** API Invoker. + +**Inputs:** Refer subclause 8.14.2. + +**Outputs:** Refer subclause 8.14.2. + +See subclause 8.14.3 for the details of usage of this API operation. + +## Annex A (informative): Overview of CAPIF operations + +Depicted in figure A-1 is the overview of CAPIF operations. CAPIF operations occur between different actors involving the API invoker, the CAPIF core function, the API exposing function, the API publishing function and the API management function, and optionally the resource owner client for RNAA. High level CAPIF interactions between the actors are shown in figure A-1. This figure is only provided for illustration purposes, and does not represent the order of operations. + +![Sequence diagram illustrating the overview of CAPIF operations between various functional entities.](1187dbd674a100960ed23efa54ccd6c1_img.jpg) + +The diagram illustrates the interactions between several functional entities over time. The entities are arranged horizontally at the top: 'Resource owner client' (dashed box), 'API invoker', 'CAPIF core function', and a group labeled 'API provider domain' containing 'API publishing function', 'API exposing function (AEF)', and 'API management function'. The sequence of operations is shown as horizontal bars between lifelines: + +- Publish service APIs:** Between 'API publishing function' and 'CAPIF core function'. +- Service API policy configuration:** Between 'CAPIF core function' and 'API invoker'. +- Onboarding API invoker to the CAPIF:** Between 'CAPIF core function' and 'API invoker'. +- Authentication between the API invoker and the CAPIF core function:** Between 'CAPIF core function' and 'API invoker'. +- API invoker discovering service APIs:** Between 'CAPIF core function' and 'API invoker'. +- Subscription and notifications for the CAPIF events:** Between 'CAPIF core function' and 'API invoker'. +- API invoker obtaining authorization to access service API:** Between 'CAPIF core function' and 'API invoker'. +- Authentication between the API invoker and the AEF:** Between 'AEF' and 'API invoker'. +- Service API invocation by the API invoker with access control:** Between 'AEF' and 'API invoker'. +- Logging service API invocations:** Between 'AEF' and 'CAPIF core function'. +- Charging the invocation of service APIs:** Between 'AEF' and 'CAPIF core function'. +- Monitoring API status and service API invocation:** Between 'AEF' and 'CAPIF core function'. +- Querying service API invocation logs:** Between 'AEF' and 'CAPIF core function'. + +Sequence diagram illustrating the overview of CAPIF operations between various functional entities. + +**Figure A-1: Overview of CAPIF operations** + +The CAPIF defines the functional entities in subclause 6.3. + +The CAPIF defines the reference points between the functional entities in subclause 6.4. + +The following operations require the communication between the CAPIF entities: + +1. Publishing service APIs: the API provider utilizes the API publishing function over CAPIF-4 reference point to publish the service APIs on the CAPIF core function, as specified in subclause 8.3 of this specification; +2. Discovering service APIs: the API invoker discovers the service APIs over CAPIF-1/CAPIF-1e reference points, as specified in subclause 8.7 of this specification; +3. API event subscription and notification: the API invoker subscribes to and receive service API event notifications over CAPIF-1/CAPIF-1e reference points, as specified in subclause 8.8 of this specification; +4. Authenticating with CAPIF: the API invoker authenticates itself over CAPIF-1/CAPIF-1e reference points, as specified in subclause 8.10 of this specification; + +5. Authorizing with CAPIF: the API invoker obtains service API authorization over CAPIF-1/CAPIF-1e reference points, as specified in subclause 8.11 of this specification. In RNAA scenarios, API authorization is based on the authorization information obtained from the resource owner, as specified in clause 8.31; +6. Topology hiding: the API provider, to hide the topology, utilizes the API exposing function over CAPIF-3 reference point, as specified in subclause 8.13 of this specification; +7. Authenticating the API invoker prior to service API invocation: the API provider, to authenticate the API invoker prior to the service API invocation, utilizes the API exposing function over CAPIF-2/CAPIF-2e and CAPIF-3, as specified in subclause 8.14 of this specification; +8. Authenticating the API invoker upon the service API invocation: the API provider, to authenticate the API invoker upon invocation of the service APIs, utilizes the API exposing function over CAPIF-2/CAPIF-2e and CAPIF-3, as specified in subclause 8.15 of this specification; +9. Authorizing API invoker: the API provider, to authorize the API invoker to access the service APIs, utilizes the API exposing function over CAPIF-2/CAPIF-2e and CAPIF-3, as specified in subclause 8.16 of this specification; +10. Access control: the API provider, to control the access of the service API by the API invoker based on policy or usage limits, + - utilizes the API exposing function over CAPIF-2/CAPIF-2e and CAPIF-3, as specified in subclause 8.17 of this specification; or + - in a cascaded deployment, utilizes API exposing functions over CAPIF-2/CAPIF-2e, as specified in subclause 8.18 of this specification; +11. Logging service: the API provider, to maintain the log of the API invocations at the CAPIF core function for services such as charging, invocation history, utilizes the API exposing function over CAPIF-3, as specified in subclause 8.19 of this specification; +12. Charging service: the API provider, to facilitate charging of the API invocations, utilizes the API exposing function over CAPIF-3, as specified in subclause 8.20 of this specification; +13. Service monitoring: the API provider, to facilitate monitoring such as API invoker's ID and IP address, utilizes the API management function over CAPIF-5, as specified in subclause 8.21 of this specification; and +14. Auditing: the API provider, for auditing, utilizes the API management function over CAPIF-5, as specified in subclause 8.22 of this specification. + +## Annex B (informative): CAPIF relationship with network exposure aspects of 3GPP systems + +This annex provides the relationship of CAPIF with network exposure aspects of 3GPP systems. Any system exposing capabilities as service APIs can implement CAPIF. Generic model for CAPIF utilization by service API provider is included. Network exposure aspects of EPS and 5GS are considered for illustration. + +NOTE: As there are no impacts on CAPIF's relationship with network exposure aspects of 3GPP systems due to deployment of 3rd party trust domain, it is not illustrated in the figures. + +### B.0 CAPIF utilization by service API provider + +Figure B.0-1 illustrates the service API interaction with the CAPIF for utilizing framework aspects provided by the CAPIF. + +![Diagram illustrating CAPIF utilization by service API provider. The diagram shows the interaction between an API invoker, CAPIF APIs, CAPIF core function, Service APIs, and 3GPP network entity(ies) within a PLMN Trust Domain.](53e80f05e45f132bf76a96442a5507e9_img.jpg) + +The diagram illustrates the architecture for CAPIF utilization by a service API provider within a PLMN Trust Domain (indicated by a dashed box and a vertical double-headed arrow on the left). The components and their interactions are as follows: + +- API invoker:** Located outside the PLMN Trust Domain. It connects to the CAPIF APIs via the CAPIF-1e interface and to the Service APIs via the Service API interface + CAPIF-2e interface. +- CAPIF APIs:** Located inside the PLMN Trust Domain. It connects to the API invoker via CAPIF-1e and to the CAPIF core function via the CAPIF-1 interface. +- CAPIF core function:** Located inside the PLMN Trust Domain. It connects to the CAPIF APIs via CAPIF-1 and provides framework aspects to the Service APIs via three interfaces: CAPIF-3, CAPIF-4, and CAPIF-5. +- Service APIs:** Located inside the PLMN Trust Domain. It connects to the API invoker via the Service API interface + CAPIF-2e interface and receives framework aspects from the CAPIF core function via CAPIF-3, CAPIF-4, and CAPIF-5. The Service APIs box contains four sub-functions: API exposing function, API publishing function, API management function, and Service API exposure function. +- 3GPP network entity(ies):** Located inside the PLMN Trust Domain. It connects to the Service APIs via the 3GPP internal interface. + +Diagram illustrating CAPIF utilization by service API provider. The diagram shows the interaction between an API invoker, CAPIF APIs, CAPIF core function, Service APIs, and 3GPP network entity(ies) within a PLMN Trust Domain. + +**Figure B.0-1: CAPIF utilization by service API provider** + +The service API aspects of the 3GPP network services and capabilities such as subscriber management, mobility management, transport and other communication services can be exposed for consumption by external 3rd party applications (e.g. API invoker). + +Framework aspects typically horizontal in nature caters to common functionality such as onboarding, offboarding, publishing, unpublishing, update service API, discovery, authentication, registration, authorization, logging, charging, monitoring, configuration, topology hiding, that are required to provide service APIs to API invokers. Service APIs can + +utilize the functions of the API provider domain (i.e. API exposing function, API publishing function, API management function) and interfaces CAPIF-3, CAPIF-4 and CAPIF-5 as specified in this specification. + +The service API exposure function is connected to 3GPP network entity(s) via 3GPP internal interface(s). The API publishing function provides the service API information for publishing to the CAPIF core function. + +For consuming service API, the API invoker interacts with the service API exposure function via service API interface and CAPIF-2/2e. While the service API interface is responsible for providing service aspects, CAPIF-2/2e supports service API by providing framework aspects such as authentication of the API invoker, authorization verification for the API invoker upon accessing the service API. + +## B.1 CAPIF relationship with 3GPP EPS network exposure + +### B.1.1 General + +The table B.1.1-1 shows the relationship between CAPIF and EPS network exposure aspects. The details of SCEF and its role in exposing network capabilities of EPS to 3rd party applications are specified in 3GPP TS 23.682 [2] + +**Table B.1.1-1: CAPIF relationship with 3GPP EPS network exposure** + +| Aspects | CAPIF | EPS network exposure | +|-----------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------| +| Entity providing the APIs to external or 3 rd party applications | AEF | SCEF | +| Entity providing framework related services to the applications (discovery, authentication, authorization, etc) | CAPIF core function | SCEF | +| Entity representing the external or 3 rd party applications | API invoker | SCS/AS | +| Entity providing framework related services to support the APIs operation and management (publish, policy enforcements, charging) | CAPIF core function | SCEF | +| Interface/Reference point for exposing network capabilities as APIs | CAPIF-2 and CAPIF-2e (Do not include the service specific aspects) | T8 | +| Interface/Reference point for exposing framework services as APIs to the applications | CAPIF-1 and CAPIF-1e | Not specified. (May be via T8) | +| Interface/Reference point for framework services to support the APIs operation and management | CAPIF-3, CAPIF-4 and CAPIF-5 | Internal to SCEF | + +### B.1.2 Deployment models + +#### B.1.2.1 General + +Based on the relationship captured in table B.1.1-1, the following deployment models for CAPIF are possible to enable EPS network exposure. + +NOTE: The deployment models captured in subclause 7 are possible for the SCEF deployment compliant with CAPIF. Not all deployment models are illustrated in this subclause. + +#### B.1.2.2 SCEF implements the CAPIF architecture + +Figure B.1.2.2-1 illustrates the deployment model where SCEF implements the CAPIF architecture. + +![Diagram of SCEF implementing the CAPIF architecture. The diagram shows the interaction between an API invoker (SCS/AS) and the SCEF, which contains the CAPIF core function and the API provider domain. The SCEF is connected to the PLMN Trust Domain. The API invoker (SCS/AS) connects to the CAPIF APIs via CAPIF-1e and CAPIF-1. The CAPIF APIs connect to the CAPIF core function. The CAPIF core function connects to the API provider domain via CAPIF-3, CAPIF-4, and CAPIF-5. The API provider domain contains the API exposing function, API publishing function, and API management function. The API exposing function connects to the API invoker (SCS/AS) via CAPIF-2 (T8) and CAPIF-2e (T8).](6e9d059430baba0c363e33749f68b107_img.jpg) + +The diagram illustrates the SCEF implementing the CAPIF architecture. At the top, an 'API invoker (SCS/AS)' is shown. Below it, a dashed box labeled 'PLMN Trust Domain' contains the SCEF. Inside the SCEF, there is a 'CAPIF core function' and an 'API provider domain'. The 'CAPIF core function' contains 'CAPIF APIs'. The 'API provider domain' contains 'Service APIs', 'API exposing function', 'API publishing function', and 'API management function'. The 'API invoker (SCS/AS)' connects to the 'CAPIF APIs' via 'CAPIF-1e' and 'CAPIF-1'. The 'CAPIF APIs' connect to the 'CAPIF core function'. The 'CAPIF core function' connects to the 'API provider domain' via 'CAPIF-3', 'CAPIF-4', and 'CAPIF-5'. The 'API exposing function' connects to the 'API invoker (SCS/AS)' via 'CAPIF-2 (T8)' and 'CAPIF-2e (T8)'. The 'API invoker (SCS/AS)' also connects to the 'API exposing function' via 'CAPIF-2 (T8)' and 'CAPIF-2e (T8)'. + +Diagram of SCEF implementing the CAPIF architecture. The diagram shows the interaction between an API invoker (SCS/AS) and the SCEF, which contains the CAPIF core function and the API provider domain. The SCEF is connected to the PLMN Trust Domain. The API invoker (SCS/AS) connects to the CAPIF APIs via CAPIF-1e and CAPIF-1. The CAPIF APIs connect to the CAPIF core function. The CAPIF core function connects to the API provider domain via CAPIF-3, CAPIF-4, and CAPIF-5. The API provider domain contains the API exposing function, API publishing function, and API management function. The API exposing function connects to the API invoker (SCS/AS) via CAPIF-2 (T8) and CAPIF-2e (T8). + +**Figure B.1.2.2-1: SCEF implements the CAPIF architecture** + +The SCEF can implement the functionalities of the CAPIF core function, the API exposing function, the API publishing function and the API management function. + +According to the CAPIF architecture, CAPIF-2 and CAPIF-2e consist of framework aspects and service specific aspects. The service specific aspects are out of scope of CAPIF. T8 can implement the service specific aspects of CAPIF-2 and CAPIF-2e, and can provide the service APIs exposed by SCEF (AEF) to the SCS/AS (API invoker). + +The SCEF can additionally provide CAPIF-1 and CAPIF-1e (CAPIF APIs) to the SCS/AS (API invokers). + +### B.1.2.3 SCEF implements the service specific aspect compliant with the CAPIF architecture + +Figure B.1.2.3-1 illustrates the deployment model where SCEF implements the service specific aspect compliant with the CAPIF architecture. + +![Diagram of SCEF implementing the service specific aspect compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (SCS/AS), CAPIF APIs, CAPIF core function, and the API provider domain (containing Service APIs, API exposing function SCEF, API publishing function, and API management function).](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +The diagram illustrates the architecture where the SCEF implements the service specific aspect compliant with the CAPIF architecture. It is enclosed in a dashed box labeled 'PLMN Trust Domain'. At the top, an 'API invoker (SCS/AS)' is shown. Below it, on the left, is a box for 'CAPIF APIs' and 'CAPIF core function'. On the right, a box labeled 'API provider domain' contains 'Service APIs', 'API exposing function SCEF', 'API publishing function', and 'API management function'. The 'API invoker (SCS/AS)' connects to 'CAPIF APIs' via 'CAPIF-1e' and to 'Service APIs' via 'CAPIF-2e (T8)'. 'CAPIF APIs' connects to 'CAPIF core function' via 'CAPIF-1'. 'CAPIF core function' connects to 'Service APIs' via 'CAPIF-3', to 'API exposing function SCEF' via 'CAPIF-4', and to 'API management function' via 'CAPIF-5'. The 'API invoker (SCS/AS)' also connects to 'API exposing function SCEF' via 'CAPIF-2 (T8)'. + +Diagram of SCEF implementing the service specific aspect compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (SCS/AS), CAPIF APIs, CAPIF core function, and the API provider domain (containing Service APIs, API exposing function SCEF, API publishing function, and API management function). + +**Figure B.1.2.3-1: SCEF implements the service specific aspect compliant with the CAPIF architecture** + +3GPP EPS can deploy the CAPIF core function along with the SCEF. + +The SCEF can implement the functionalities of the API provider domain functions. + +According to the CAPIF architecture, CAPIF-2 and CAPIF-2e consist of framework aspects and service specific aspects. The service specific aspects are out of scope of CAPIF. T8 can implement the service specific aspects of CAPIF-2 and CAPIF-2e, and can provide the service APIs exposed by SCEF (AEF) to the SCS/AS (API invoker). + +The SCEF can implement the CAPIF-3 reference point/interface to the CAPIF core function. + +## B.1.2.4 Distributed deployment of the SCEF compliant with the CAPIF architecture + +Figure B.1.2.4-1 illustrates the distributed deployment model where the SCEF implements the service specific aspect compliant with the CAPIF architecture. + +![Diagram illustrating the distributed deployment of SCEF compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (SCS/AS), CAPIF APIs, CAPIF core function, and various SCEF functions (SCEF-1, SCEF-2) within the API provider domain. Reference points CAPIF-1e, CAPIF-1, CAPIF-2e (T8), CAPIF-2 (T8), CAPIF-3, CAPIF-4, and CAPIF-5 are shown.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +The diagram illustrates the distributed deployment of SCEF compliant with the CAPIF architecture. It shows the following components and interactions: + +- API invoker (SCS/AS):** Located at the top, it connects to the CAPIF APIs via CAPIF-1e and to the Service APIs via CAPIF-2e (T8). +- PLMN Trust Domain:** A dashed box containing the CAPIF core function and the API provider domain. +- CAPIF APIs:** A component that connects to the API invoker (SCS/AS) via CAPIF-1e and to the CAPIF core function via CAPIF-1. +- CAPIF core function:** A large box on the left that connects to the CAPIF APIs via CAPIF-1, to the API exposing function (SCEF-2) via CAPIF-3, to the API publishing function via CAPIF-4, and to the API management function via CAPIF-5. +- API provider domain:** A dashed box on the right containing: + - SCEF-2 (API exposing function):** Contains Service APIs and connects to the CAPIF core function via CAPIF-3 and to the API invoker (SCS/AS) via CAPIF-2e (T8). + - SCEF-1:** Contains the API publishing function and the API management function. It connects to the CAPIF core function via CAPIF-4 and CAPIF-5, and to the Service APIs via CAPIF-2 (T8). + +Diagram illustrating the distributed deployment of SCEF compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (SCS/AS), CAPIF APIs, CAPIF core function, and various SCEF functions (SCEF-1, SCEF-2) within the API provider domain. Reference points CAPIF-1e, CAPIF-1, CAPIF-2e (T8), CAPIF-2 (T8), CAPIF-3, CAPIF-4, and CAPIF-5 are shown. + +**Figure B.1.2.4-1: Distributed deployment of SCEF compliant with the CAPIF architecture** + +The 3GPP EPS can deploy the CAPIF core function, the SCEF-2 (API exposing function as a gateway) along with the SCEF-1 as illustrated in subclause 7.3. + +The SCEF can implement the functionalities of API provider domain functions. + +According to the CAPIF architecture, CAPIF-2 or CAPIF-2e consists of framework aspects and service specific aspects. The service specific aspects are out of scope of the CAPIF. T8 can implement the service specific aspects of CAPIF-2 or CAPIF-2e and can provide the service APIs exposed by the SCEF-2 (AEF as a gateway) to the SCS/AS (API invoker). + +The SCEF-2 can implement the CAPIF-3 reference point to the CAPIF core function and the SCEF-1 can implement the CAPIF-4 and CAPIF-5 reference points to the CAPIF core function. + +*Editor's Note: The illustration of this deployment model requires further study.* + +## B.2 CAPIF relationship with 3GPP 5GS network exposure + +### B.2.1 General + +The table B.2.1-1 shows the relationship between CAPIF and 5GS network exposure aspects. The details of NEF and its role in exposing network capabilities of 5GS to 3rd party applications are specified in 3GPP TS 23.501 [3] and the details of NEF service operations are specified in 3GPP TS 23.502 [4]. + +**Table B.2.1-1: CAPIF relationship with 3GPP 5GS network exposure** + +| Aspects | CAPIF | 5GS network exposure | +|-----------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------| +| Entity providing the APIs to external or 3 rd party applications | AEF | NEF | +| Entity providing framework related services to the applications (discovery, authentication, authorization, etc) | CAPIF core function | NEF (Not specified yet) | +| Entity representing the external or 3 rd party applications | API invoker | AF | +| Entity providing framework related services to support the APIs operation and management (publish, policy enforcements, charging) | CAPIF core function | NEF (Not specified yet) | +| Interface/Reference point for exposing network capabilities as APIs | CAPIF-2 and CAPIF-2e (Do not include the service specific aspects) | Nnef | +| Interface/Reference point for exposing framework services as APIs to the applications | CAPIF-1 and CAPIF-1e | Nnef (Not specified yet) | +| Interface/Reference point for framework services to support the APIs operation and management | CAPIF-3, CAPIF-4 and CAPIF-5 | Internal to NEF | + +## B.2.2 Deployment models + +### B.2.2.1 General + +Based on the relationship captured in table B.2.1-1, the following deployment models for CAPIF are possible to enable 5GS network exposure. + +NOTE: The deployment models captured in subclause 7 are possible for the NEF deployment compliant with CAPIF. Not all deployment models are illustrated in this subclause. + +### B.2.2.2 NEF implements the CAPIF architecture + +Figure B.2.2.2-1 illustrates the deployment model where the NEF implements the CAPIF architecture. + +![Diagram of NEF implementing the CAPIF architecture. The diagram shows the interaction between an API invoker (AF) and the Network Exposure Function (NEF). The NEF contains a CAPIF core function and an API provider domain. The CAPIF core function provides CAPIF APIs to the AF via CAPIF-1e. The API provider domain contains Service APIs, an API exposing function, an API publishing function, and an API management function. The AF connects to the Service APIs via CAPIF-2 (Nnef). The CAPIF core function connects to the Service APIs via CAPIF-3, CAPIF-4, and CAPIF-5. The NEF is part of the PLMN Trust Domain.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +The diagram illustrates the NEF implementing the CAPIF architecture. It is divided into three main components: the API invoker (AF), the NEF, and the API provider domain. The AF is shown at the top, with two instances. The left instance connects to the CAPIF APIs within the NEF via the CAPIF-1e interface. The right instance connects to the Service APIs within the API provider domain via the CAPIF-2 (Nnef) interface. The NEF is a large box containing the CAPIF core function and the API provider domain. The CAPIF core function provides CAPIF APIs to the AF via the CAPIF-1 interface. The API provider domain contains the Service APIs, API exposing function, API publishing function, and API management function. The CAPIF core function connects to these functions via the CAPIF-3, CAPIF-4, and CAPIF-5 interfaces. The entire NEF and API provider domain are enclosed within the PLMN Trust Domain, indicated by a dashed line and a vertical double-headed arrow on the left. + +Diagram of NEF implementing the CAPIF architecture. The diagram shows the interaction between an API invoker (AF) and the Network Exposure Function (NEF). The NEF contains a CAPIF core function and an API provider domain. The CAPIF core function provides CAPIF APIs to the AF via CAPIF-1e. The API provider domain contains Service APIs, an API exposing function, an API publishing function, and an API management function. The AF connects to the Service APIs via CAPIF-2 (Nnef). The CAPIF core function connects to the Service APIs via CAPIF-3, CAPIF-4, and CAPIF-5. The NEF is part of the PLMN Trust Domain. + +**Figure B.2.2.2-1: NEF implements the CAPIF architecture** + +The NEF can implement the functionalities of the CAPIF core function, the API exposing function, the API publishing function and the API management function. + +According to the CAPIF architecture, CAPIF-2 and CAPIF-2e consist of framework aspects and service specific aspects. The service specific aspects are out of scope of CAPIF. Nnef can implement the service specific aspects of CAPIF-2 and CAPIF-2e, and can provide the service APIs exposed by the NEF (AEF) to the AF (API invoker). + +The NEF can additionally provide CAPIF-1 and CAPIF-1e (CAPIF APIs) to the AF (API invokers). + +### B.2.2.3 NEF implements the service specific aspect compliant with the CAPIF architecture + +Figure B.2.2.3-1 illustrates the deployment model where the NEF implements the service specific aspect compliant with the CAPIF architecture. + +![Diagram of NEF implementation of service specific aspect compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (AF), CAPIF core function, and NEF within a PLMN Trust Domain. The AF connects to the CAPIF core function via CAPIF-1e and to the NEF via CAPIF-2e (Nnef). The CAPIF core function connects to the NEF via CAPIF-3, CAPIF-4, and CAPIF-5. The NEF contains Service APIs, API exposing function (NEF), API publishing function, and API management function. The NEF connects to the AF via CAPIF-2 (Nnef).](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +The diagram illustrates the architecture where the Network Exposure Function (NEF) implements the service specific aspect compliant with the CAPIF architecture. It is contained within a dashed box labeled "PLMN Trust Domain". + +- External Entity:** An "API invoker (AF)" is shown at the top left, outside the PLMN Trust Domain. +- Internal Components:** + - CAPIF core function:** A large box on the left containing "CAPIF APIs". + - NEF (Nnef):** A box on the right containing "Service APIs", "API exposing function (NEF)", "API publishing function", and "API management function". This box is part of the "API provider domain". +- Interfaces:** + - CAPIF-1e:** Interface between the AF and the CAPIF APIs. + - CAPIF-1:** Interface between the AF and the CAPIF core function. + - CAPIF-2 (Nnef):** Interface between the AF and the Service APIs. + - CAPIF-2e (Nnef):** Interface between the AF and the NEF. + - CAPIF-3:** Interface between the CAPIF APIs and the Service APIs. + - CAPIF-4:** Interface between the CAPIF core function and the API exposing function (NEF). + - CAPIF-5:** Interface between the CAPIF core function and the API management function. + +Diagram of NEF implementation of service specific aspect compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (AF), CAPIF core function, and NEF within a PLMN Trust Domain. The AF connects to the CAPIF core function via CAPIF-1e and to the NEF via CAPIF-2e (Nnef). The CAPIF core function connects to the NEF via CAPIF-3, CAPIF-4, and CAPIF-5. The NEF contains Service APIs, API exposing function (NEF), API publishing function, and API management function. The NEF connects to the AF via CAPIF-2 (Nnef). + +**Figure B.2.2.3-1: NEF implements the service specific aspect compliant with the CAPIF architecture** + +3GPP 5GS can deploy the CAPIF core function along with the NEF. + +The NEF can implement the functionalities of the API provider domain functions. + +According to the CAPIF architecture, CAPIF-2 and CAPIF-2e consist of framework aspects and service specific aspects. The service specific aspects are out of scope of CAPIF. Nnef can implement the service specific aspects of CAPIF-2 and CAPIF-2e, and can provide the service APIs exposed by NEF (AEF) to the AF (API invoker). + +The NEF can implement the CAPIF-3 reference point/interface to the CAPIF core function. + +## B.2.2.4 Distributed deployment of the NEF compliant with the CAPIF architecture + +Figure B.2.2.4-1 illustrates the distributed deployment model where the NEF implements the service specific aspect compliant with the CAPIF architecture. + +![Figure B.2.2.4-1: Distributed deployment of NEF compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (AF) and the CAPIF architecture components. The CAPIF architecture is divided into the PLMN Trust Domain (left) and the API provider domain (right). The PLMN Trust Domain contains the CAPIF core function and CAPIF APIs. The API provider domain contains the NEF-1 and NEF-2 functions. The AF connects to the CAPIF APIs via CAPIF-1e and CAPIF-1. The CAPIF APIs connect to the NEF-2 via CAPIF-3. The NEF-2 connects to the NEF-1 via CAPIF-2 (Nnef). The NEF-1 connects to the CAPIF core function via CAPIF-4 and CAPIF-5. The AF also connects to the NEF-2 via CAPIF-2e (Nnef).](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +Figure B.2.2.4-1: Distributed deployment of NEF compliant with the CAPIF architecture. The diagram shows the interaction between an API invoker (AF) and the CAPIF architecture components. The CAPIF architecture is divided into the PLMN Trust Domain (left) and the API provider domain (right). The PLMN Trust Domain contains the CAPIF core function and CAPIF APIs. The API provider domain contains the NEF-1 and NEF-2 functions. The AF connects to the CAPIF APIs via CAPIF-1e and CAPIF-1. The CAPIF APIs connect to the NEF-2 via CAPIF-3. The NEF-2 connects to the NEF-1 via CAPIF-2 (Nnef). The NEF-1 connects to the CAPIF core function via CAPIF-4 and CAPIF-5. The AF also connects to the NEF-2 via CAPIF-2e (Nnef). + +**Figure B.2.2.4-1: Distributed deployment of NEF compliant with the CAPIF architecture** + +The 3GPP 5GS can deploy the CAPIF core function, the NEF-2 (API exposing function as a gateway) along with the NEF-1 as illustrated in subclause 7.3. + +The NEF can implement the functionalities of API provider domain functions. + +According to the CAPIF architecture, CAPIF-2 or CAPIF-2e consists of framework aspects and service specific aspects. The service specific aspects are out of scope of the CAPIF. Nnef can implement the service specific aspects of CAPIF-2 and CAPIF-2 or CAPIF-2e can provide the service APIs exposed by the NEF-2 (AEF as a gateway) to the AF (API invoker). + +The NEF-2 (AEF) can implement the CAPIF-3 reference point to the CAPIF core function and the NEF-1 can implement the CAPIF-4 and CAPIF-5 reference points to the CAPIF core function. + +*Editor's Note: The illustration of this deployment model requires further study.* + +## B.3 Integrated deployment of 3GPP network exposure systems with the CAPIF + +### B.3.1 General + +According to 3GPP TS 23.682 [2], when the CAPIF is supported, the SCEF supports the API provider domain functions. According to 3GPP TS 23.501 [3], when the CAPIF is supported, the NEF supports the API provider domain functions. + +## B.3.2 Deployment model + +### B.3.2.1 General + +The SCEF and the NEF may be integrated with a single CAPIF core function to offer their respective service APIs to the API invokers. The following deployment model is possible for integrated deployment of the SCEF and the NEF with the CAPIF core function. + +### B.3.2.2 Integrated deployment of the SCEF and the NEF with the CAPIF + +Figure B.3.2.2-1 illustrates integrated deployment of the SCEF and the NEF with the CAPIF. + +![Diagram showing the integrated deployment of SCEF and NEF with CAPIF. It illustrates the CAPIF core function acting as a central gateway, connected to API invokers (1, 2, 3) and internal functions like SCEF and NEF. Reference points CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, CAPIF-5, CAPIF-1e, CAPIF-2e, CAPIF-3e, CAPIF-4e, and CAPIF-5e are shown connecting these components across different trust domains: PLMN Trust Domain and 3rd party Trust Domain.](4a9454b4354535e1b61423084da1424b_img.jpg) + +The diagram illustrates the integrated deployment of the SCEF and the NEF with the CAPIF. It features a central 'CAPIF core function' within the 'PLMN Trust Domain'. This function connects to three 'API invoker' entities: API invoker 1, API invoker 2, and API invoker 3. API invoker 1 connects via CAPIF-1e and CAPIF-2e (T8). API invoker 2 connects via CAPIF-1, CAPIF-2 (T8), and CAPIF-2e (N33). API invoker 3 connects via CAPIF-1e, CAPIF-2e (T8), and CAPIF-2. The CAPIF core function also connects to the 'SCEF' (Service APIs API exposing function, API publishing function, API management function) in 'API provider domain 1' via CAPIF-3, CAPIF-4, and CAPIF-5. It connects to the 'NEF' (Service APIs API exposing function, API publishing function, API management function) in 'API provider domain 2' via CAPIF-3, CAPIF-4, and CAPIF-5. Additionally, the CAPIF core function connects to 'Service APIs' in 'API provider domain 3' via CAPIF-3e, CAPIF-4e, and CAPIF-5e. The SCEF and NEF are shown with their respective internal functions: API exposing function, API publishing function, and API management function. The '3rd party Trust Domain' is indicated on the right side of the diagram. + +Diagram showing the integrated deployment of SCEF and NEF with CAPIF. It illustrates the CAPIF core function acting as a central gateway, connected to API invokers (1, 2, 3) and internal functions like SCEF and NEF. Reference points CAPIF-1, CAPIF-2, CAPIF-3, CAPIF-4, CAPIF-5, CAPIF-1e, CAPIF-2e, CAPIF-3e, CAPIF-4e, and CAPIF-5e are shown connecting these components across different trust domains: PLMN Trust Domain and 3rd party Trust Domain. + +**Figure B.3.2.2-1: Integrated deployment of the SCEF and the NEF with the CAPIF** + +The CAPIF core function, the SCEF and the NEF are deployed in the PLMN trust domain, where the CAPIF core function takes the role of a unified gateway and provides services to different API invokers. The API invokers obtains the T8 and N33 service API information and the corresponding entry point details from the CAPIF core function via CAPIF-1 or CAPIF-1e reference points. + +The API invokers can interact independently with the SCEF, the NEF and the 3rd party API exposing functions via CAPIF-2 or CAPIF-2e reference points. In this case, T8 and N33 can be reused to implement the service specific aspects of CAPIF-2 or CAPIF-2e reference points for the corresponding service API interactions of the SCEF and the NEF respectively. + +The SCEF and the NEF applies any service API access policy control to the interactions between the API invokers and the T8 and N33 service APIs respectively by communicating with the same CAPIF core function via the CAPIF-3 reference point. + +## Annex C (informative): CAPIF role in charging + +### C.1 General + +This annex provides the information about the role of CAPIF in charging service API invocations. The common architecture for charging is illustrated in clause 4 of 3GPP TS 32.240 [6]. There are two charging mechanisms - offline charging and online charging. The role of CAPIF in both these charging mechanisms is illustrated for informational purpose in this subclause. + +The API invocations are subjected to charging (online, offline) as illustrated in figure C.1-1. + +NOTE: As there are no impacts on CAPIF's role in charging due to deployment of 3rd party trust domain, it is not illustrated in the figures. + +![Diagram illustrating the CAPIF role in charging, showing interactions between an API invoker, CAPIF core function, and charging systems within the PLMN Trust Domain.](a265aba1737da6f0200faac85366b163_img.jpg) + +The diagram illustrates the CAPIF role in charging within the PLMN Trust Domain. It shows the flow of charging information from an API invoker through the CAPIF core function to online and offline charging systems, and finally to billing. + +**Components:** + +- API invoker:** Located outside the PLMN Trust Domain. It connects to the CAPIF APIs via CAPIF-1e and to the Service APIs via CAPIF-2. +- PLMN Trust Domain:** A large dashed box containing the CAPIF core function, charging systems, and the API provider domain. +- CAPIF core function:** Contains the CAPIF APIs. It receives CAPIF-1 from the API invoker and interacts with the charging systems via CAPIF-3, CAPIF-4, and CAPIF-5. +- Service APIs:** Located within the API provider domain. It contains the API exposing function, API publishing function, and API management function. It receives CAPIF-2 from the API invoker and interacts with the CAPIF core function via CAPIF-3, CAPIF-4, and CAPIF-5. +- Charging Systems:** Located within the PLMN Trust Domain. It includes the Online Charging System and the Offline Charging System. Both receive charging information from the CAPIF core function and interact with Billing. + +**Interactions:** + +- CAPIF-1:** API invoker to CAPIF APIs. +- CAPIF-1e:** API invoker to CAPIF APIs (specific to charging). +- CAPIF-2:** API invoker to Service APIs. +- CAPIF-2e:** API invoker to Service APIs (specific to charging). +- CAPIF-3:** CAPIF APIs to Service APIs (API invocation charging information). +- CAPIF-4:** CAPIF core function to API publishing function. +- CAPIF-5:** CAPIF core function to API management function. +- 2. Realtime interaction with online charging system including authorization:** CAPIF core function to Online Charging System. +- 2. Forwarding the charging information to offline charging system:** CAPIF core function to Offline Charging System. +- 3. Charging system interaction with Billing:** Both Online and Offline Charging Systems to Billing. + +Diagram illustrating the CAPIF role in charging, showing interactions between an API invoker, CAPIF core function, and charging systems within the PLMN Trust Domain. + +Figure C.1-1: CAPIF role in charging + +--- + +## C.2 CAPIF role in online charging + +The API invocations are subjected to online charging as illustrated in figure C.1-1. + +The API exposing function provides the API invocation charging information to the CAPIF core function. The CAPIF core function further interacts with an online charging system in real-time by providing the charging information and further the CAPIF core function receives the authorization corresponding to the charging information. + +NOTE: The online charging architecture for CAPIF including specification of online charging system entities and reference points is under the responsibility of SA5. + +--- + +## C.3 CAPIF role in offline charging + +The API invocations are subjected to offline charging as illustrated in figure C.1-1. + +The API exposing function provides the API invocation charging information to the CAPIF core function. The CAPIF core function provides the charging information to the offline charging system. The offline charging system generates the CDRs for the API invocation and further transfers the CDR files to the billing domain. + +NOTE: The offline charging architecture for CAPIF including specification of offline charging system entities and reference points is under the responsibility of SA5. + +## Annex D (informative): CAPIF relationship with external API frameworks + +This annex provides the relationship of CAPIF with the OMA Network APIs and the ETSI MEC API framework. The relationship of CAPIF with these external API frameworks is illustrated in the table D-1. "Yes" means that the external API framework supports the CAPIF functionality, "No" means that the API framework does not support the CAPIF functionality, and "Partial" means that it provides a mechanism that partially supports the CAPIF functionality. + +**Table D-1: CAPIF relationship with external API frameworks** + +| CAPIF functionalities | OMA Network APIs | | ETSI MEC API framework | | +|------------------------------------------------------------|--------------------|----------------------------------------------|------------------------|----------------------------------| +| | Supported | Reference | Supported | Reference | +| Publish and discover service API information | Partial (see NOTE) | OMA-TS-NGSI_Registration_and_D iscovery [11] | Yes | ETSI GS MEC 011 [7] | +| Topology hiding of the service | Yes | Individual API exposing function | Yes | Individual API exposing function | +| API invoker authentication to access service APIs | Partial | OMA-ER_Autho4API [9] | Partial | ETSI GS MEC 009 [8] | +| API invoker authorization to access service APIs | Partial | OMA-ER_Autho4API [9] | Partial | ETSI GS MEC 009 [8] | +| Charging on invocation of service APIs | No | | No | | +| Lifecycle management of service APIs | No | | No | | +| Monitoring service API invocations | No | | No | | +| Logging API invoker onboarding and service API invocations | No | | No | | +| Auditing service API invocations | No | | No | | +| Onboarding API invoker to CAPIF | No | | No | | +| CAPIF authentication of API invokers | No | | No | | +| Service API access control | Partial | OMA-ER_Autho4API [9] | Partial | ETSI GS MEC 009 [8] | +| Secure API communication | Yes | OMA-ER_Autho4API [9] | Yes | ETSI GS MEC 009 [8] | +| Policy configuration | No | | No | | +| API protocol stack model | Partial | for REST: OMA-TS_REST_NetAPI_Comm on [10] | Partial | for REST: ETSI GS MEC 009 [8] | +| API security protocol | Partial | OMA-ER_Autho4API [9] | Partial | ETSI GS MEC 009 [8] | +| CAPIF support for service APIs from multiple providers | No | | No | | + +NOTE: OMA-TS-NGSI\_Registration\_and\_Discovery [11] is only applicable to a specific type of web services (OWSER using UDDI and WSDL). + +## Annex E (normative): Configuration data for CAPIF + +The configuration data is stored in the CAPIF core function and provided by the CAPIF administrator. + +The configuration data for CAPIF is specified in table E-1. + +**Table E-1: Configuration data for CAPIF** + +| Reference | Parameter description | +|-----------------|--------------------------------------------------------------------------------------------------------------------------| +| Subclause 4.2.2 | List of published service API discovery restrictions | +| | > Service API identification | +| | > API invoker identity information | +| Subclause 4.7.2 | List of service API log storage durations | +| | > Service API identification | +| | > Service API log storage duration (in hours) (see NOTE) | +| Subclause 4.7.4 | List of API invoker interactions log storage durations | +| | > Service API identification | +| | API invoker interactions log storage duration (in hours) (see NOTE) | +| Subclause 4.10 | List of access control policy per API invoker | +| | > Volume limit on service API invocations (total number of invocations allowed) | +| | > Time limit on service API invocations (The time range of the day during which the service API invocations are allowed) | +| | > Rate limit on service API invocations (allowed service API invocations per second) | +| | > Service API identification | +| | > API invoker identity information | +| NOTE: | If no value is set for the duration, the duration is assumed to be unlimited. | + +## Annex F (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-10 | SA6#19 | S6-171274 | | | | TS skeleton | 0.0.0 | +| 2017-10 | SA6#19 | | | | | Implementation of the following p-CRs approved by SA6: S6-171444; S6-171343; S6-171445; S6-171446; S6-171466; S6-171448; S6-171348; S6-171449; S6-171359; S6-171467; S6-171451; S6-171452; S6-171362; S6-171463; S6-171356; S6-171355; S6-171453; S6-171454; S6-171455; S6-171464; S6-171468; S6-171350; S6-171349; S6-171407. | 0.1.0 | +| 2017-12 | SA6#20 | | | | | Implementation of the following p-CRs approved by SA6: S6-171630; S6-171631; S6-171633; S6-171648; S6-171650; S6-171658; S6-171659; S6-171692; S6-171693; S6-171694; S6-171695; S6-171698; S6-171699; S6-171700; S6-171702; S6-171704; S6-171705; S6-171706; S6-171711; S6-171712; S6-171713; S6-171819; S6-171820; S6-171821; S6-171822; S6-171823; S6-171848; S6-171855; S6-171865; S6-171876. | 0.2.0 | +| 2017-12 | SA#78 | SP-170901 | | | | Submitted to SA#78 for approval | 1.0.0 | +| 2018-01 | SA#78 | SP-170901 | | | | MCC Editorial update for publication after TSG SA approval (SA#78) | 15.0.0 | +| 2018-04 | SA#79 | SP-180156 | 0001 | 1 | F | Use of specific ETSI and OMA references | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0002 | | F | Corrections for CAPIF-1e and CAPIF-2e | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0003 | | F | Miscellaneous corrections to procedures and information flows | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0004 | 1 | F | Addition of offboarding to functional entities and reference points description | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0005 | 1 | D | Editorial corrections | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0006 | 2 | B | Solution to EN on revoking authorization based on access control | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0007 | 3 | F | Configuration items for CAPIF | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0008 | 3 | F | Update to CAPIF relationship with 3GPP EPS and 5GS | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0009 | 1 | F | Solution to EN on policy synchronization | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0010 | 2 | F | CAPIF utilization by service APIs | 15.1.0 | +| 2018-04 | SA#79 | SP-180156 | 0011 | 1 | F | Proposal for definition for PLMN trust domain | 15.1.0 | +| 2018-06 | SA#80 | SP-180374 | 0013 | 1 | F | Correction for the details of service API information | 15.2.0 | +| 2018-06 | SA#80 | SP-180374 | 0014 | 1 | F | Correction for usage of service API identification information | 15.2.0 | +| 2018-06 | SA#80 | SP-180374 | 0019 | 2 | D | Editorial correction of TS 23.222 (CAPIF stage2) | 15.2.0 | +| 2018-06 | SA#80 | SP-180375 | 0012 | 2 | B | Architecture functional model to support multiple API providers | 16.0.0 | +| 2018-06 | SA#80 | SP-180375 | 0015 | 1 | B | Service API publish and discovery requirements for 3rd party API providers | 16.0.0 | +| 2018-06 | SA#80 | SP-180375 | 0016 | 1 | B | Charging requirements for 3rd party API providers | 16.0.0 | +| 2018-06 | SA#80 | SP-180375 | 0017 | 1 | B | OAM requirements for 3rd party API providers | 16.0.0 | +| 2018-06 | SA#80 | SP-180375 | 0018 | 2 | B | CAPIF interconnection requirements | 16.0.0 | +| 2018-06 | SA#80 | SP-180375 | 0020 | 2 | F | Updating representation of deployment models | 16.0.0 | +| 2018-09 | SA#81 | SP-180675 | 0021 | 2 | B | Integrated CAPIF with 3GPP EPS and 5GS network exposure | 16.1.0 | +| 2018-09 | SA#81 | SP-180675 | 0022 | 1 | C | Enhancement to the functional model deployments | 16.1.0 | +| 2018-09 | SA#81 | SP-180675 | 0023 | 2 | B | Enhancement to reference points for eCAPIF | 16.1.0 | +| 2018-09 | SA#81 | SP-180674 | 0029 | 1 | A | Update API naming convention | 16.1.0 | +| 2018-09 | SA#81 | SP-180674 | 0030 | 2 | A | Alignment of APIs | 16.1.0 | +| 2018-09 | SA#81 | SP-180674 | 0031 | 1 | A | Alignment to SA3 CAPIF TS | 16.1.0 | +| 2018-09 | SA#81 | SP-180674 | 0032 | 1 | | Alignment to SA3 authentication procedure | 16.1.0 | +| 2018-09 | SA#81 | SP-180675 | 0033 | 3 | B | Functional architecture for CAPIF interconnection | 16.1.0 | +| 2018-12 | SA#82 | SP-181176 | 0034 | 3 | B | Topology hiding enhancement | 16.2.0 | +| 2018-12 | SA#82 | SP-181176 | 0035 | 2 | B | API publish and API discover for CAPIF interconnection | 16.2.0 | +| 2018-12 | SA#82 | SP-181176 | 0036 | 1 | C | Architectural requirements for identities | 16.2.0 | +| 2018-12 | SA#82 | SP-181176 | 0038 | 2 | B | Architectural requirements for provider domain entities interaction | 16.2.0 | +| 2018-12 | SA#82 | SP-181176 | 0039 | 2 | B | Update API invoker API list | 16.2.0 | +| 2018-12 | SA#82 | SP-181175 | 0043 | 2 | A | API invoker's onboarding response rel16 | 16.2.0 | +| 2019-03 | SA#83 | SP-190072 | 0044 | 2 | F | Update procedures with topology hiding | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0045 | 2 | B | API sharing for CCF interconnection | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0046 | 2 | B | API invocation request routing with topology hiding | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0048 | 1 | C | Interactions between API exposing functions | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0049 | 1 | B | Service API discovery involving multiple CCFs | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0050 | 2 | B | Multiple CCFs deployment in a PLMN trust domain | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0051 | 2 | B | Service API discover for CAPIF interconnection | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0052 | 1 | B | Architectural requirements for registration of API provider domain functions | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0053 | 2 | B | Procedures for registration of API provider domain functions | 16.3.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------|--------| +| 2019-03 | SA#83 | SP-190072 | 0054 | 1 | B | Updates to AEF procedures for 3rd party trust domain | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0055 | 1 | B | Updates to APF procedures for 3rd party trust domain | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0056 | 1 | B | Updates to AMF procedures for 3rd party trust domain | 16.3.0 | +| 2019-03 | SA#83 | SP-190072 | 0057 | - | B | Updates to CAPIF events procedures for 3rd party trust domain | 16.3.0 | +| 2019-06 | SA#84 | SP-190483 | 0058 | 1 | F | Clarification to routing rule of service API invocation | 16.4.0 | +| 2019-06 | SA#84 | SP-190483 | 0059 | 3 | F | Functional model update with reference points | 16.4.0 | +| 2019-06 | SA#84 | SP-190483 | 0060 | 2 | B | Update to service API publish for CAPIF interconnection | 16.4.0 | +| 2019-06 | SA#84 | SP-190483 | 0061 | 2 | B | Serving area and domain of service API for CAPIF interconnection | 16.4.0 | +| 2019-06 | SA#84 | SP-190483 | 0062 | 1 | B | 3 rd party trust domain with network exposure and charging aspects of 3GPP systems | 16.4.0 | +| 2019-06 | SA#84 | SP-190483 | 0063 | 1 | B | Interface based representation of CAPIF architecture | 16.4.0 | +| 2019-09 | SA#85 | SP-190828 | 0064 | 1 | F | Clarification and alignment with publish request information flows | 16.5.0 | +| 2019-12 | SA#86 | SP-191107 | 0065 | | F | Correction on usage of service API information in access control message | 16.6.0 | +| 2020-03 | SA#87-E | SP-200112 | 0066 | 1 | F | Shared CAPIF provider domain info in interconnection | 16.7.0 | +| 2020-03 | SA#87-E | SP-200116 | 0067 | 2 | B | Serving area information for service APIs to support edge applications | 17.0.0 | +| 2020-07 | SA#88-E | SP-200337 | 0069 | | A | Add consumer for discover and publish service APIs | 17.1.0 | +| 2020-07 | SA#88-E | SP-200337 | 0071 | | A | Add obtaining routing info service API | 17.1.0 | +| 2020-07 | SA#88-E | SP-200337 | 0073 | 1 | A | Correct API topology hiding | 17.1.0 | +| 2020-07 | SA#88-E | SP-200337 | 0075 | 1 | A | Correction for CAPIF interconnection IEs | 17.1.0 | +| 2020-09 | SA#89-E | SP-200840 | 0077 | 3 | F | Correction for API routing information | 17.2.0 | +| 2020-12 | SA#90-E | SP-200997 | 0078 | 2 | B | Support AEF location and API invoker interface for edge application | 17.3.0 | +| 2021-04 | SA#91-E | SP-210183 | 0079 | 4 | F | Clarification of Service-based interfaces interaction within CAPIF | 17.4.0 | +| 2021-06 | SA#92-E | SP-210482 | 0082 | | A | API provider management API | 17.5.0 | +| 2022-06 | SA#96 | SP-220471 | 0084 | 1 | A | Corrections to API invoker onboarding/offboarding in TS 23.222 | 17.6.0 | +| 2022-09 | SA#97 | SP-220918 | 0089 | | A | Corrections to API invoker onboarding/offboarding in TS 23.222 | 17.7.0 | +| 2022-12 | SA#98-e | SP-221250 | 0090 | 1 | B | Additional CAPIF architectural requirements for SNA | 18.0.0 | +| 2022-12 | SA#98-e | SP-221250 | 0091 | 2 | B | CAPIF business relationship updates for SNA | 18.0.0 | +| 2022-12 | SA#98-e | SP-221250 | 0092 | 2 | B | CAPIF functional model updates for SNA | 18.0.0 | +| 2022-12 | SA#98-e | SP-221250 | 0093 | 2 | B | API invoker obtaining authorization from resource owner | 18.0.0 | +| 2022-12 | SA#98-e | SP-221250 | 0094 | 1 | B | Discover a proper AEF with owner information | 18.0.0 | +| 2022-12 | SA#98-e | SP-221250 | 0095 | 2 | B | Reducing resource owner consent inquiry in a nested API invocation | 18.0.0 | +| 2022-12 | SA#98-e | SP-221239 | 0096 | 2 | B | CAPIF extensibility as requested by ETSI ISG MEC | 18.0.0 | +| 2023-03 | SA#99 | SP-230295 | 0098 | | B | Discover proper AEF in interconnection | 18.1.0 | +| 2023-03 | SA#99 | SP-230296 | 0099 | 1 | B | Solve CAPIF extensibility EN | 18.1.0 | +| 2023-03 | SA#99 | SP-230295 | 0100 | 1 | B | API invoker clarification | 18.1.0 | +| 2023-03 | SA#99 | SP-230295 | 0101 | 1 | D | Modify a terminology for SNA | 18.1.0 | +| 2023-03 | SA#99 | SP-230286 | 0102 | 2 | B | New IE(Service KPI) in Service API publish request | 18.1.0 | +| 2023-03 | SA#99 | SP-230295 | 0103 | 2 | B | Discover proper AEF with IP information | 18.1.0 | +| 2023-03 | SA#99 | SP-230292 | 0104 | | B | Support onboarding expiration | 18.1.0 | +| 2023-03 | SA#99 | SP-230296 | 0105 | 2 | F | Resolving editor's notes about TS reference | 18.1.0 | +| 2023-03 | SA#99 | SP-230295 | 0106 | 2 | B | Adding descriptions of new functional entities and reference points | 18.1.0 | +| 2023-06 | SA#100 | SP-230714 | 0109 | 2 | B | Support CAPIF in SNPn | 18.2.0 | +| 2023-06 | SA#100 | SP-230712 | 0111 | 4 | B | Service API status monitoring | 18.2.0 | +| 2023-06 | SA#100 | SP-230713 | 0112 | | B | Clarification that RNAA is for both 4G and 5G | 18.2.0 | +| 2023-06 | SA#100 | SP-230713 | 0113 | 2 | B | SNAAPP alignment with SA3 | 18.2.0 | +| 2023-06 | SA#100 | SP-230713 | 0114 | 2 | B | Overview of CAPIF operations for RNAA scenarios | 18.2.0 | +| 2023-06 | SA#100 | SP-230714 | 0115 | 3 | B | CAPIF add service procedure for update of subscriptions | 18.2.0 | +| 2023-06 | SA#100 | SP-230714 | 0116 | 5 | B | Alignment among CAPIF provider (trust) domains | 18.2.0 | +| 2023-12 | SA#102 | SP-231547 | 0122 | 2 | A | Editorial corrections | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0125 | 1 | F | Solve EN related to SA3 | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0126 | 2 | F | Add response to RNAA procedural flows and correct cross-references | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0128 | 2 | F | Clarify how to monitor service API status when the APF is unable to update service API status | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0129 | 2 | F | Add CAPIF words to Abbreviations | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0133 | 6 | F | CAPIF Architecture alignment with SA3 RNAA aspects | 18.3.0 | +| 2023-12 | SA#102 | SP-231546 | 0136 | | A | API Description Correction | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0137 | 1 | F | API invoker authorization corrections | 18.3.0 | +| 2023-12 | SA#102 | SP-231545 | 0141 | | A | Security API corrections | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0147 | 2 | F | Editorial corrections regarding RNAA | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0149 | 2 | F | Corrections for CAPIF revocation of API Invoker's authorization based on RNAA | 18.3.0 | +| 2023-12 | SA#102 | SP-231569 | 0150 | 1 | F | Corrections for CAPIF deployment models supporting RNAA | 18.3.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23247/0b998e3ad8f9d104768642612605cb35_img.jpg b/raw/rel-18/23_series/23247/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e5628a352164bfadac9f9157a0ecc0312e66a10 --- /dev/null +++ b/raw/rel-18/23_series/23247/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8829e7854476dba69b0c57154c0778f085de2561e695072616821dc568f3cde +size 80667 diff --git a/raw/rel-18/23_series/23247/11f18bf0233d812ad2604f88f3385d60_img.jpg b/raw/rel-18/23_series/23247/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86c8bb6a75be35e07000ca4bcc17d88f11c48849 --- /dev/null +++ b/raw/rel-18/23_series/23247/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4b8c449d1e91bddf283ecec4ab7d9af0f56959fc1f7dd9c8a33cd7b3efddc49 +size 115988 diff --git a/raw/rel-18/23_series/23247/12de9b926df0384ec07702671827c9cd_img.jpg b/raw/rel-18/23_series/23247/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05ad3f3e367b6902ace099ffdffef16bc4c0d30 --- /dev/null +++ b/raw/rel-18/23_series/23247/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baecbf24892585ae021084954d61ca850ebe487c729861d7a711f5e1b5169392 +size 49077 diff --git a/raw/rel-18/23_series/23247/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/23_series/23247/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..037933722047697b7a50678cc8b7342689dba021 --- /dev/null +++ b/raw/rel-18/23_series/23247/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d88f703df9b69454df0268d886d1c6c8e43dd6da9d055d33d238f4f6dfb6eff6 +size 83918 diff --git a/raw/rel-18/23_series/23247/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/raw/rel-18/23_series/23247/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffd7708c2c3dfaa29ffab1928409626ae06334f4 --- /dev/null +++ b/raw/rel-18/23_series/23247/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddbdc95cd2d49e44e3ea990ae11973fce71517d93d409989977038d62ac1ac80 +size 52624 diff --git a/raw/rel-18/23_series/23247/1b2ce053624064d94a4143854da46702_img.jpg b/raw/rel-18/23_series/23247/1b2ce053624064d94a4143854da46702_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81537d968da3884e8b16c83dd99ab835da51caf7 --- /dev/null +++ b/raw/rel-18/23_series/23247/1b2ce053624064d94a4143854da46702_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccf33fbce19c616593e1eae3b3197a4bb5786f93c174efe3e5eca500d8fb970f +size 61581 diff --git a/raw/rel-18/23_series/23247/3337af75dfee8af7687b4f49914d6c93_img.jpg b/raw/rel-18/23_series/23247/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ffcf35b43ace413c664ee8962f82694bc684cdb --- /dev/null +++ b/raw/rel-18/23_series/23247/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef5aba9e7e7dcdce53adae05abbef5d67f4c64954c8745674406d26a25dfa1aa +size 143403 diff --git a/raw/rel-18/23_series/23247/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/raw/rel-18/23_series/23247/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fd2991e2fc61a3d79a010ca7bebe5352a9485ad --- /dev/null +++ b/raw/rel-18/23_series/23247/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d33ab0ece2e9829265fb04deea9b28785c863387de9cadf7a80dba9d10ec773 +size 79341 diff --git a/raw/rel-18/23_series/23247/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/raw/rel-18/23_series/23247/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db7ee5a1b614bacd53bb184a77367847e75c6d3b --- /dev/null +++ b/raw/rel-18/23_series/23247/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31ff8f68140e80f5c3459609902de833598b19ae857f06d4f11d9633a784b0d8 +size 214432 diff --git a/raw/rel-18/23_series/23247/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/raw/rel-18/23_series/23247/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a36237531980b2b5c7011668bbb616ab7b321b2 --- /dev/null +++ b/raw/rel-18/23_series/23247/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92ee0ce4591084b257c30bba9ae457f077d20230801cd136c69b4158ff5535af +size 98073 diff --git a/raw/rel-18/23_series/23247/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg b/raw/rel-18/23_series/23247/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd293a9c075f8bf061d841086481d1d00820d5c9 --- /dev/null +++ b/raw/rel-18/23_series/23247/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3655c7f60dbcec69a3f221ff9704f8512109c57a9d0955d623b12c975ec6f92 +size 51579 diff --git a/raw/rel-18/23_series/23247/45578bd3ed11d45af63ce00e28bab2f8_img.jpg b/raw/rel-18/23_series/23247/45578bd3ed11d45af63ce00e28bab2f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f99e29cb35ce056dba50e74b90e4fd85974e3dcb --- /dev/null +++ b/raw/rel-18/23_series/23247/45578bd3ed11d45af63ce00e28bab2f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26a9a79127c2174b873dd870bb94ba6c6982dc2e4ff36e78d461165b1346c004 +size 132145 diff --git a/raw/rel-18/23_series/23247/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/raw/rel-18/23_series/23247/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..785fbf107ab6211667e888d664c7259a6c576302 --- /dev/null +++ b/raw/rel-18/23_series/23247/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37cef270fe823482ac77b8585a5765a8dfaf71c37a96b673e3ca8dda8242822c +size 175953 diff --git a/raw/rel-18/23_series/23247/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/raw/rel-18/23_series/23247/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78d04e6d2e3aba609f199642ba608779ad2aaba3 --- /dev/null +++ b/raw/rel-18/23_series/23247/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5de11d7bb0211f9909ff654600c14cc584f25a2c4da0c8d6e08746a37e733293 +size 236336 diff --git a/raw/rel-18/23_series/23247/57134800ac3a97b6212b27b93aa196ac_img.jpg b/raw/rel-18/23_series/23247/57134800ac3a97b6212b27b93aa196ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35bdfb8ac7217f630f01d5c2230ba7df20772733 --- /dev/null +++ b/raw/rel-18/23_series/23247/57134800ac3a97b6212b27b93aa196ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fa83776f086dca2356a9ec1eb1fd4a5c9f40eaa9a0d0c519480d55cb3e122b6 +size 53027 diff --git a/raw/rel-18/23_series/23247/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23247/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed9f13484ee66dc5b4ecadedd4cc2a688507da26 --- /dev/null +++ b/raw/rel-18/23_series/23247/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2813459b9d1fb6daed97b5f994e6e8ad17772b63d725998e0bb4c58f14022ab +size 8651 diff --git a/raw/rel-18/23_series/23247/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23247/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d90eae551d71752f50912b0a0f76bc69ff18af --- /dev/null +++ b/raw/rel-18/23_series/23247/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfbb8e44fe3ca4a2eeb8928a4730d55890ced37f5caa44f418904e2fee75b318 +size 5690 diff --git a/raw/rel-18/23_series/23247/6e9d059430baba0c363e33749f68b107_img.jpg b/raw/rel-18/23_series/23247/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d34f37e3cea0f8846beea099cc74a39aba0d6a4b --- /dev/null +++ b/raw/rel-18/23_series/23247/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f775de1d13c7505d85543e01534a829af504ea7d41cfae6542e9e27db30d71ef +size 55737 diff --git a/raw/rel-18/23_series/23247/7355f66b8620d44cf566215621addb74_img.jpg b/raw/rel-18/23_series/23247/7355f66b8620d44cf566215621addb74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0470cf88f367c08188cc1fc6d1bbc81feb493834 --- /dev/null +++ b/raw/rel-18/23_series/23247/7355f66b8620d44cf566215621addb74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dd56bd1dd55b967955ceca70be2649cd6e93305154ef53c33e727d91d748a2b +size 58988 diff --git a/raw/rel-18/23_series/23247/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/23_series/23247/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ff3c20f3d40319afccd2ea8bf4b829209761fe6 --- /dev/null +++ b/raw/rel-18/23_series/23247/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f3ba3495f74c2d01633111f961cb3ee0497d632ce1d173026b315158f62b636 +size 59996 diff --git a/raw/rel-18/23_series/23247/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/23_series/23247/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2e29036252a60779b2bdbad6f74b083d6608d68 --- /dev/null +++ b/raw/rel-18/23_series/23247/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1caf67a97767f9dcca590da7814805a2bd129a2bb68eb359c531190cea35494d +size 39275 diff --git a/raw/rel-18/23_series/23247/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/raw/rel-18/23_series/23247/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d0690ff8acc2fca8e4b45cede5de0684f3e52de --- /dev/null +++ b/raw/rel-18/23_series/23247/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e0b513cd4b678460913d479630745f4f16c609b1cc198519ef524f45659924a +size 43690 diff --git a/raw/rel-18/23_series/23247/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/raw/rel-18/23_series/23247/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe421ce7235720516f3823a0074e91b933edcbf2 --- /dev/null +++ b/raw/rel-18/23_series/23247/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baa422239df885874de7dc1e75e38ebe3e30418689827c3c45f1c3ff1e24e658 +size 40465 diff --git a/raw/rel-18/23_series/23247/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/23_series/23247/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08af3a839007bb5c37bba6d3bcba106813745253 --- /dev/null +++ b/raw/rel-18/23_series/23247/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab6cb963b336f802d53e26ee4d12001aa2abe783a9b11d172dfb57f87fd25836 +size 50684 diff --git a/raw/rel-18/23_series/23247/90df9788d66ecf65abf861caf76be5ca_img.jpg b/raw/rel-18/23_series/23247/90df9788d66ecf65abf861caf76be5ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bc6651ba27dab77d33b0b60eaf1d06404db168d --- /dev/null +++ b/raw/rel-18/23_series/23247/90df9788d66ecf65abf861caf76be5ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e449eb27305a3201aaacbda917119da8e5d43c5e08763347380f99d3685b0d8 +size 73558 diff --git a/raw/rel-18/23_series/23247/9b9262a549828579ab904148450734f6_img.jpg b/raw/rel-18/23_series/23247/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0dd2bd34aa71cd9e863818e0367f70357fd38ad --- /dev/null +++ b/raw/rel-18/23_series/23247/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75cf8d11efcd8d7b143d995742d3f75471d9ec390c8d02c0b73a86cc717156c0 +size 78755 diff --git a/raw/rel-18/23_series/23247/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/raw/rel-18/23_series/23247/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d6e362f04f0232a07a120a0056e9391e5ba889a --- /dev/null +++ b/raw/rel-18/23_series/23247/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b210165bc0d06690a2f79633c45dddf21c08f833d93a934bd5118e163d51db1a +size 154654 diff --git a/raw/rel-18/23_series/23247/a2bbc82e5c6132b0870bd70f6657f919_img.jpg b/raw/rel-18/23_series/23247/a2bbc82e5c6132b0870bd70f6657f919_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbd9d50702a9ff05f0c3a5327eca5397544b6d9f --- /dev/null +++ b/raw/rel-18/23_series/23247/a2bbc82e5c6132b0870bd70f6657f919_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b0bf8ba77937f18c7a1cf30808d7d60a61adc2e7cbc4f962e3fc04c975b9c1c +size 113796 diff --git a/raw/rel-18/23_series/23247/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/23_series/23247/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75be03589abcbd4b26511a01c611608bc5ff1484 --- /dev/null +++ b/raw/rel-18/23_series/23247/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f73b205b98a1c8b97510cec6ed4084ccc6bb15f3378c508894c081a3b499276 +size 75641 diff --git a/raw/rel-18/23_series/23247/a5481fd31c02b525617e70f2de357039_img.jpg b/raw/rel-18/23_series/23247/a5481fd31c02b525617e70f2de357039_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d77e0750975cfa75f88fd0b4cca1bcfdc8ee2a31 --- /dev/null +++ b/raw/rel-18/23_series/23247/a5481fd31c02b525617e70f2de357039_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8231834e115b0d23bb8f989b71df2c35e2e8a0489159a78f7d439d41a9b9fb8b +size 41527 diff --git a/raw/rel-18/23_series/23247/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/raw/rel-18/23_series/23247/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22886f4a6c39ca2c908609339f4e34a886ed997a --- /dev/null +++ b/raw/rel-18/23_series/23247/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5ef8b7caedb3b6e67cd4aaf2b6681199f5afc8dae1adbf6148ffc3f736b2909 +size 50428 diff --git a/raw/rel-18/23_series/23247/a66383962afcd0f0458f0d45c101fabf_img.jpg b/raw/rel-18/23_series/23247/a66383962afcd0f0458f0d45c101fabf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ac322dfcb24c2dbdcc3b8af764b1bbdbad1e0ab --- /dev/null +++ b/raw/rel-18/23_series/23247/a66383962afcd0f0458f0d45c101fabf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:568be03d29661c70a481c3ecafd1cd191798d789873ab6e1b2540398a5914753 +size 88446 diff --git a/raw/rel-18/23_series/23247/aa22da43c463563d3d0035722bd79449_img.jpg b/raw/rel-18/23_series/23247/aa22da43c463563d3d0035722bd79449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..123a4e48c95d11825da57f502e121dc4f23fcacd --- /dev/null +++ b/raw/rel-18/23_series/23247/aa22da43c463563d3d0035722bd79449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f61f3426bf43c89dcc0432f5923c8f81d48563e940b34febd05ad0d909a2c9d1 +size 109712 diff --git a/raw/rel-18/23_series/23247/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg b/raw/rel-18/23_series/23247/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf2dab94cc20bc148a0f9c74804e90b164ba920f --- /dev/null +++ b/raw/rel-18/23_series/23247/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b4e4639538f690070ee80bd4f04ea3bcc48d6d880fd84db4ad02e3750d5240b +size 164169 diff --git a/raw/rel-18/23_series/23247/ca5555bb37f54857199d243feff8479e_img.jpg b/raw/rel-18/23_series/23247/ca5555bb37f54857199d243feff8479e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4570cc0548d9a651a31514bb00ff318631b4c2c5 --- /dev/null +++ b/raw/rel-18/23_series/23247/ca5555bb37f54857199d243feff8479e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98613c4d403e8585427047e7d399ba8d92f786a3c4a05fa46fee49bf84720618 +size 83128 diff --git a/raw/rel-18/23_series/23247/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/raw/rel-18/23_series/23247/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67f6fda4c9146d8623d1f30179ef63eb90a1f79c --- /dev/null +++ b/raw/rel-18/23_series/23247/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c65ee751c47da002fb84ee13015551b00fe199e30ddc5945a7f8b35a208bb20c +size 38647 diff --git a/raw/rel-18/23_series/23247/ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg b/raw/rel-18/23_series/23247/ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd064170efc93cf682eff3cb573538ebbb153022 --- /dev/null +++ b/raw/rel-18/23_series/23247/ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1152657c3d15bebdae9a9ff04348f284c2b81ab36641e4201fb189688a7a1650 +size 37073 diff --git a/raw/rel-18/23_series/23247/ceb967656aa87e9c8a39e8fe063f8f4c_img.jpg b/raw/rel-18/23_series/23247/ceb967656aa87e9c8a39e8fe063f8f4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9808dd2076fe6aae8b924cfdf3b2ba792c912245 --- /dev/null +++ b/raw/rel-18/23_series/23247/ceb967656aa87e9c8a39e8fe063f8f4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3625f2bdb7b451781a6e09c94aa5f5ddc3378d4eff7067571539b6ac0894309 +size 61292 diff --git a/raw/rel-18/23_series/23247/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/raw/rel-18/23_series/23247/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7eabdaf84e162c1ad6c29c07adb4aa9c3f2d71a7 --- /dev/null +++ b/raw/rel-18/23_series/23247/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0de7928be066540144617686af03dccba383d0f422a2e57829747dea29dbe39b +size 107930 diff --git a/raw/rel-18/23_series/23247/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/raw/rel-18/23_series/23247/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..951e8d7f8798f8fa83ec530cd10cdc5da8215390 --- /dev/null +++ b/raw/rel-18/23_series/23247/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a321fbb665e24cc7c5bb49c7c0dc1b060759ec705ac21deda89f9ff12be5dc5 +size 118249 diff --git a/raw/rel-18/23_series/23247/dcd49ce2814873afd15074efc28a661f_img.jpg b/raw/rel-18/23_series/23247/dcd49ce2814873afd15074efc28a661f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4207360add016e6f6d7b21879143c43b47d0924 --- /dev/null +++ b/raw/rel-18/23_series/23247/dcd49ce2814873afd15074efc28a661f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51c76788d1b6f2c5a31cf840eea0cb2ddb4f5e5c46cd09006e6d1cdb7d1f78d3 +size 52583 diff --git a/raw/rel-18/23_series/23247/df1966d80c74bc127f159a48f38b13ee_img.jpg b/raw/rel-18/23_series/23247/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f979b3924d32ab24761692423e0954076af51762 --- /dev/null +++ b/raw/rel-18/23_series/23247/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7af0aab3237c611b144e64a10914c27982de9b5ec0fac241396c165165f04018 +size 94150 diff --git a/raw/rel-18/23_series/23247/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/raw/rel-18/23_series/23247/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efb7e8016080b298516591f6a47506362cac651a --- /dev/null +++ b/raw/rel-18/23_series/23247/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00465a7efa7d36bbda3b26fa7335a59428e1eccd0de9835e4d9eb0880b1ef3ee +size 80672 diff --git a/raw/rel-18/23_series/23247/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/23_series/23247/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..198dc1efcc8ffeb2fe4854f3fb2002b4669306dc --- /dev/null +++ b/raw/rel-18/23_series/23247/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b6f749d9fc0816ab83a4abc8ca7314dbfb55f2161c389a4ad2165df806ed62f +size 68266 diff --git a/raw/rel-18/23_series/23247/e18841eb4a995df8354a793459e12fd0_img.jpg b/raw/rel-18/23_series/23247/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77223040836fddd980ffe4cefd4f0c23c0808407 --- /dev/null +++ b/raw/rel-18/23_series/23247/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d47d8c7acc9a1fe0858b7db5047b5d24743001ddb4b65dd80149068a0c1a960 +size 45203 diff --git a/raw/rel-18/23_series/23247/ff7977984f2552f326b2089d7595fff3_img.jpg b/raw/rel-18/23_series/23247/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a48b7eca492c7d9478835393111a6ab7f13dbe --- /dev/null +++ b/raw/rel-18/23_series/23247/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eaa7d260e7d4c13d731d52ca1123a6c2e9096ce37c9cd2f827f66b4d4343016 +size 59007 diff --git a/raw/rel-18/23_series/23247/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/raw/rel-18/23_series/23247/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a0689993bd0402201c636afbded631574f5e183 --- /dev/null +++ b/raw/rel-18/23_series/23247/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10c762fc93da0aa3f41fc150df2c4ad2e265c48ea5b3788aaa48cb73f49b4ee4 +size 97571 diff --git a/raw/rel-18/23_series/23247/raw.md b/raw/rel-18/23_series/23247/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fdeddb99ff49b975362ca30856b7a60bf37ee299 --- /dev/null +++ b/raw/rel-18/23_series/23247/raw.md @@ -0,0 +1,5137 @@ + + +# 3GPP TS 23.247 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architectural enhancements for 5G multicast-broadcast services; 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 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 letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' 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 ..... | 8 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions of terms and abbreviations ..... | 11 | +| 3.1 Terms..... | 11 | +| 3.2 Abbreviations ..... | 12 | +| 4 General Concept..... | 12 | +| 4.1 Overview of multicast and broadcast communication ..... | 12 | +| 4.2 MB service provisioning..... | 14 | +| 4.2.1 Multicast data provisioning ..... | 14 | +| 4.2.2 Broadcast data provisioning ..... | 16 | +| 4.3 Multicast session state model..... | 17 | +| 5 Architecture model..... | 20 | +| 5.1 General architecture ..... | 20 | +| 5.2 General architecture for interworking with EPS..... | 21 | +| 5.3 Service-based interfaces, Reference point and functional entities ..... | 22 | +| 5.3.0 Service-based interfaces ..... | 22 | +| 5.3.1 Reference point..... | 22 | +| 5.3.2 Functional entities ..... | 23 | +| 5.3.2.1 PCF ..... | 23 | +| 5.3.2.2 MB-SMF ..... | 23 | +| 5.3.2.3 SMF ..... | 24 | +| 5.3.2.4 MB-UPF..... | 24 | +| 5.3.2.5 UPF ..... | 24 | +| 5.3.2.6 AMF..... | 24 | +| 5.3.2.7 NG-RAN ..... | 25 | +| 5.3.2.8 UE ..... | 25 | +| 5.3.2.9 AF ..... | 25 | +| 5.3.2.10 NEF ..... | 26 | +| 5.3.2.11 MBSF..... | 26 | +| 5.3.2.12 MBSTF ..... | 26 | +| 5.3.2.13 UDM ..... | 26 | +| 5.3.2.14 UDR ..... | 27 | +| 5.3.2.15 NRF..... | 27 | +| 5.3.2.15.1 General ..... | 27 | +| 5.3.2.15.2 Extensions to NF profile at NRF..... | 27 | +| 6 Functionalities and features ..... | 27 | +| 6.1 Authorization to MBS service..... | 27 | +| 6.1.1 AF authorization to the service for multicast and broadcast ..... | 27 | +| 6.1.2 UE authorization to the service for multicast ..... | 27 | +| 6.2 Local MBS service and Location dependent MBS service..... | 28 | +| 6.2.1 General ..... | 28 | +| 6.2.2 Local MBS service ..... | 28 | +| 6.2.3 Location dependent MBS service..... | 29 | +| 6.2.4 Void ..... | 29 | +| 6.2.5 Void ..... | 29 | +| 6.3 Mobility support of MBS service..... | 30 | +| 6.3.1 Mobility of Multicast MBS session..... | 30 | +| 6.3.2 Mobility of Broadcast MBS session..... | 30 | +| 6.4 Subscription to multicast services..... | 31 | +| 6.4.1 General ..... | 31 | +| 6.4.2 MBS subscription data in UDM..... | 31 | +| 6.4.3 MBS information in UDR ..... | 32 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------|----| +| 6.5 | Identifiers ..... | 32 | +| 6.5.1 | MBS Session ID ..... | 32 | +| 6.5.2 | Temporary Mobile Group Identity ..... | 32 | +| 6.5.3 | Source Specific IP Multicast Address ..... | 32 | +| 6.5.4 | MBS Frequency Selection Area ID ..... | 32 | +| 6.5.5 | Associated Session ID ..... | 33 | +| 6.6 | QoS Handling for Multicast and Broadcast services ..... | 33 | +| 6.7 | User plane management ..... | 34 | +| 6.8 | Interworking with MBMS over E-UTRAN for public safety services ..... | 36 | +| 6.9 | MBS Session Context ..... | 36 | +| 6.9.1 | MBS Session Context ..... | 36 | +| 6.10 | Policy control for Multicast and Broadcast services ..... | 38 | +| 6.10.1 | General ..... | 38 | +| 6.10.2 | MBS Session policy control data in UDR ..... | 39 | +| 6.11 | Service Announcement ..... | 39 | +| 6.12 | Paging strategy handling ..... | 40 | +| 6.13 | MBS Security function ..... | 41 | +| 6.14 | MBS Service Information ..... | 41 | +| 6.15 | Group Message Delivery ..... | 42 | +| 6.16 | Support of MBS data reception for UEs using power saving functions ..... | 42 | +| 6.17 | Support of Multicast MBS session data reception in UE with RRC_INACTIVE state ..... | 43 | +| 6.18 | Resource sharing across broadcast MBS Sessions during network sharing ..... | 43 | +| 7 | MBS procedures ..... | 45 | +| 7.1 | Common procedure for Multicast and Broadcast ..... | 45 | +| 7.1.1 | MBS Session Management ..... | 45 | +| 7.1.1.1 | General ..... | 45 | +| 7.1.1.2 | MBS Session Creation without PCC ..... | 45 | +| 7.1.1.3 | MBS Session Creation with PCC ..... | 49 | +| 7.1.1.4 | MBS Session Deletion without PCC ..... | 53 | +| 7.1.1.5 | MBS Session Deletion with PCC ..... | 54 | +| 7.1.1.6 | MBS Session Update without PCC ..... | 56 | +| 7.1.1.7 | MBS Session Update with PCC ..... | 57 | +| 7.1.2 | MB-SMF discovery and selection for multicast/broadcast session ..... | 59 | +| 7.1.3 | MB-UPF discovery and selection for multicast/broadcast session ..... | 60 | +| 7.2 | MBS procedures for multicast Session ..... | 60 | +| 7.2.1 | MBS join and Session establishment procedure ..... | 60 | +| 7.2.1.1 | General ..... | 60 | +| 7.2.1.2 | Establishment of a PDU Session that can be associated with multicast session(s) ..... | 61 | +| 7.2.1.3 | Multicast session join and session establishment procedure ..... | 61 | +| 7.2.1.4 | Establishment of shared delivery toward RAN node ..... | 66 | +| 7.2.2 | Multicast MBS Session leave and Multicast MBS Session release procedure ..... | 67 | +| 7.2.2.1 | General ..... | 67 | +| 7.2.2.2 | Multicast Session leave requested by the UE ..... | 67 | +| 7.2.2.3 | Multicast session leave requested by the network or MBS session release ..... | 69 | +| 7.2.2.4 | Release of shared delivery toward RAN node ..... | 71 | +| 7.2.3 | Mobility Procedures for MBS ..... | 72 | +| 7.2.3.1 | General ..... | 72 | +| 7.2.3.2 | Xn based handover from MBS supporting NG-RAN node ..... | 72 | +| 7.2.3.3 | N2 based handover from MBS supporting NG-RAN node ..... | 74 | +| 7.2.3.4 | Xn/N2 based handover from non-MBS supporting NG-RAN node ..... | 75 | +| 7.2.3.5 | Minimization of data loss ..... | 76 | +| 7.2.3.6 | Xn/N2 based handover for inactive MBS session ..... | 76 | +| 7.2.3.7 | Connection Resume in RRC Inactive procedure ..... | 77 | +| 7.2.3.8 | Mobility procedures to enable delivery of multicast MBS session data to UEs in
RRC_INACTIVE state ..... | 77 | +| 7.2.3.8.1 | General ..... | 77 | +| 7.2.3.8.2 | Mobility of UE in RRC_INACTIVE state receiving MBS data within RNA ..... | 78 | +| 7.2.3.8.3 | Mobility of UE in RRC_INACTIVE state receiving MBS data out of RNA and within RA ..... | 78 | +| 7.2.3.8.4 | Mobility of UE in RRC_INACTIVE state receiving MBS data out of RA ..... | 78 | +| 7.2.4 | Support of Local multicast service and Location dependent multicast service ..... | 78 | +| 7.2.4.1 | General ..... | 78 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.2.4.2 | Support of location dependent multicast service ..... | 78 | +| 7.2.4.2.0 | Creation for location dependent MBS session ..... | 78 | +| 7.2.4.2.1 | UE join location dependent Multicast MBS session and establishment procedure ..... | 79 | +| 7.2.4.2.2 | Void..... | 80 | +| 7.2.4.2.3 | Handover procedure ..... | 80 | +| 7.2.4.2.4 | Activation of location dependent MBS session ..... | 82 | +| 7.2.4.2.5 | UE location change handling within the same NG-RAN node between cells belonging to different MBS service areas during Individual delivery ..... | 82 | +| 7.2.4.2.6 | UE location change handling by SMF ..... | 83 | +| 7.2.4.2.7 | UE mobility within the same NG-RAN between cells belonging to different MBS service areas for shared delivery ..... | 83 | +| 7.2.4.2.8 | Void..... | 84 | +| 7.2.4.2.9 | Connection Resume procedure..... | 84 | +| 7.2.4.3 | Support of local MBS for multicast..... | 84 | +| 7.2.4.3.1 | Local MBS service area information provided by AF ..... | 84 | +| 7.2.4.3.2 | Multicast session join and session establishment procedure for local MBS..... | 84 | +| 7.2.4.3.3 | Handover procedure with local MBS session ..... | 85 | +| 7.2.4.3.4 | Activation of local MBS session..... | 86 | +| 7.2.4.3.5 | UE location change handling by SMF ..... | 86 | +| 7.2.4.3.6 | UE mobility within the same NG-RAN between cells in or out of the MBS service area ..... | 87 | +| 7.2.4.3.7 | Void..... | 87 | +| 7.2.4.3.8 | Connection Resume procedure with local MBS session..... | 87 | +| 7.2.5 | MBS session activation and deactivation..... | 87 | +| 7.2.5.1 | General..... | 87 | +| 7.2.5.2 | MBS session activation procedure..... | 88 | +| 7.2.5.3 | MBS session deactivation procedure..... | 91 | +| 7.2.6 | Multicast session update procedure..... | 92 | +| 7.2.7 | Void..... | 95 | +| 7.2.8 | Service request procedure..... | 95 | +| 7.2.9 | AF provisioning multicast MBS Session Authorization information ..... | 95 | +| 7.2.9a | AF provisioning MBS Session assistance information ..... | 96 | +| 7.2.10 | Multicast MBS procedures for UEs using power saving functions ..... | 96 | +| 7.3 | MBS procedures for broadcast Session..... | 97 | +| 7.3.1 | MBS Session Start for Broadcast ..... | 97 | +| 7.3.1a | MBS Session Start for resource sharing across multiple broadcast MBS Sessions during network sharing ..... | 99 | +| 7.3.2 | MBS Session Release for Broadcast ..... | 100 | +| 7.3.2a | MBS Session Release for resource sharing across multiple broadcast MBS Sessions during network sharing ..... | 101 | +| 7.3.3 | MBS Session Update for Broadcast ..... | 102 | +| 7.3.4 | Support for Location dependent Broadcast Service ..... | 104 | +| 7.3.5 | MBS Session Delivery Status Indication for Broadcast..... | 104 | +| 7.3.6 | Broadcast MBS Session Release Require ..... | 105 | +| 7.3.7 | Transport change for resource sharing across broadcast MBS Sessions during network sharing ..... | 106 | +| 7.3.8 | Broadcast MBS procedures for UEs using power saving functions..... | 107 | +| 7.4 | MBS procedures for inter System Mobility ..... | 108 | +| 7.4.1 | Inter-system mobility with interworking at service layer..... | 108 | +| 7.5 | MBS procedures for Group Message Delivery ..... | 109 | +| 7.5.1 | Group Message Delivery via MBS Broadcast..... | 109 | +| 7.5.2 | Modification of previously submitted Group message ..... | 111 | +| 7.5.3 | Cancellation of previously submitted Group message ..... | 112 | +| 8 | Control and user plane stacks..... | 113 | +| 8.1 | Control plane for Multicast and Broadcast services..... | 113 | +| 8.1.1 | General ..... | 113 | +| 8.1.2 | NG-RAN – MB-SMF ..... | 113 | +| 8.2 | User plane for Multicast and Broadcast services ..... | 113 | +| 9 | Network Function Services..... | 115 | +| 9.1 | MB-SMF Services..... | 115 | +| 9.1.1 | General ..... | 115 | +| 9.1.2 | Nmbsmf_TMGI service..... | 115 | + +| | | | +|----------|-------------------------------------------------------------------|-----| +| 9.1.2.1 | General..... | 115 | +| 9.1.2.2 | Nmbsmf_TMGI_Allocate service operation ..... | 115 | +| 9.1.2.3 | Nmbsmf_TMGI_Deallocate service operation..... | 115 | +| 9.1.3 | Nmbsmf_MBSSession service ..... | 116 | +| 9.1.3.1 | General..... | 116 | +| 9.1.3.2 | Nmbsmf_MBSSession_ContextUpdate service operation..... | 116 | +| 9.1.3.3 | Nmbsmf_MBSSession_ContextStatusSubscribe service operation ..... | 117 | +| 9.1.3.4 | Nmbsmf_MBSSession_ContextStatusNotify service operation ..... | 117 | +| 9.1.3.5 | Nmbsmf_MBSSession_ContextStatusUnsubscribe service operation..... | 117 | +| 9.1.3.6 | Nmbsmf_MBSSession_Create service operation..... | 118 | +| 9.1.3.7 | Nmbsmf_MBSSession_Update service operation..... | 118 | +| 9.1.3.8 | Nmbsmf_MBSSession_Delete service operation..... | 118 | +| 9.1.3.9 | Nmbsmf_MBSSession_StatusNotify service operation ..... | 118 | +| 9.1.3.10 | Nmbsmf_MBSSession_StatusSubscribe service operation..... | 119 | +| 9.1.3.11 | Nmbsmf_MBSSession_StatusUnsubscribe service operation..... | 119 | +| 9.2 | PCF Services ..... | 119 | +| 9.2.1 | General ..... | 119 | +| 9.2.2 | Npcf_MBSPolicyControl service..... | 119 | +| 9.2.2.1 | General..... | 119 | +| 9.2.2.2 | Npcf_MBSPolicyControl_Create service operation..... | 120 | +| 9.2.2.3 | Void ..... | 120 | +| 9.2.2.4 | Npcf_MBSPolicyControl_Delete service operation..... | 120 | +| 9.2.2.5 | Npcf_MBSPolicyControl_Update service operation..... | 120 | +| 9.2.3 | Npcf_MBSPolicyAuthorization Service ..... | 121 | +| 9.2.3.1 | General..... | 121 | +| 9.2.3.2 | Npcf_MBSPolicyAuthorization_Create service operation..... | 121 | +| 9.2.3.3 | Npcf_MBSPolicyAuthorization_Update service operation..... | 121 | +| 9.2.3.4 | Npcf_MBSPolicyAuthorization_Delete service operation..... | 121 | +| 9.3 | AMF Services..... | 122 | +| 9.3.1 | General ..... | 122 | +| 9.3.2 | Namf_MBSBroadcast service ..... | 122 | +| 9.3.2.1 | General..... | 122 | +| 9.3.2.2 | Namf_MBSBroadcast_ContextCreate service operation ..... | 122 | +| 9.3.2.3 | Namf_MBSBroadcast_ContextUpdate service operation ..... | 122 | +| 9.3.2.4 | Namf_MBSBroadcast_ContextRelease service operation ..... | 123 | +| 9.3.2.5 | Namf_MBSBroadcast_ContextStatusNotify service operation..... | 123 | +| 9.3.3 | Namf_MBSCommunication Service..... | 123 | +| 9.3.3.1 | General..... | 123 | +| 9.3.3.2 | Namf_MBSCommunication_N2MessageTransfer service operation ..... | 123 | +| 9.4 | NEF Services..... | 123 | +| 9.4.1 | General ..... | 123 | +| 9.4.2 | Nnef_MBSTMGI service ..... | 124 | +| 9.4.2.1 | General..... | 124 | +| 9.4.2.2 | Nnef_MBSTMGI_Allocate service operation..... | 124 | +| 9.4.2.3 | Nnef_MBSTMGI_Deallocate service operation ..... | 124 | +| 9.4.2.4 | Nnef_MBSTMGI_ExpiryNotify service operation ..... | 124 | +| 9.4.3 | Nnef_MBSSession Service ..... | 125 | +| 9.4.3.1 | General..... | 125 | +| 9.4.3.2 | Nnef_MBSSession_Create service operation..... | 125 | +| 9.4.3.3 | Nnef_MBSSession_Update service operation..... | 125 | +| 9.4.3.4 | Nnef_MBSSession_Delete service operation..... | 126 | +| 9.4.3.5 | Nnef_MBSSession_StatusNotify service operation ..... | 126 | +| 9.4.3.6 | Nnef_MBSSession_StatusSubscribe service operation..... | 126 | +| 9.4.3.7 | Nnef_MBSSession_StatusUnsubscribe service operation..... | 126 | +| 9.4.4 | Nnef_MBSGroupMsg Service ..... | 127 | +| 9.4.4.1 | General..... | 127 | +| 9.4.4.2 | Nnef_MBSGroupMsgDelivery_Create service operation..... | 127 | +| 9.4.4.3 | Nnef_MBSGroupMsgDelivery_Update service operation..... | 127 | +| 9.4.4.3a | Nnef_MBSGroupMsgDelivery_Delete service operation..... | 127 | +| 9.4.4.4 | Nnef_MBSGroupMsgDelivery_StatusNotify service operation ..... | 127 | +| 9.5 | MBSF Services..... | 128 | + +**Annex A (normative):** Configuration options at Service and/or Application for MBS ..... 129 + +**Annex B (informative):** Service levels for multicast communication service ..... 131 + +**Annex C (normative):** Interworking at reference points MB2 and xMB..... 132 + +**Annex D (informative):** Change history..... 133 + +# 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 architectural enhancements to the 5G system using NR to support multicast and broadcast communication services, complying to the requirements in TS 22.146 [2], TS 22.246 [3] and TS 22.261 [4]. This document encompasses support for functions such as how to deliver multicast and broadcast communications including support within certain location areas, mobility, MBS session management, policy control and QoS, and support for features e.g. group message delivery. + +The present document also covers interworking with E-UTRAN and EPC based eMBMS for Public Safety (e.g. MCX services). + +# --- 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.146: "Multimedia Broadcast/Multicast Service (MBMS); Stage 1". +- [3] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1". +- [4] 3GPP TS 22.261: "Service requirements for the 5G system". +- [5] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". +- [6] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [7] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [8] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description". +- [9] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [10] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE)". +- [11] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [12] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [13] Void. +- [14] Void. +- [15] 3GPP TS 38.413: "NG Application Protocol (NGAP)". +- [16] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [17] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes; Stage 3". +- [18] 3GPP TS 26.502: "5G Multicast-Broadcast User Service Architecture". + +- [19] 3GPP TS 29.510: "Network Function Repository Services; Stage 3". +- [20] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [21] 3GPP TS 23.289: "Mission Critical services over 5G System; Stage 2". +- [22] 3GPP TS 26.517: "5G Multicast-Broadcast User Services; Protocols and Formats". +- [23] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol; User Plane (GTPv1-U)". +- [24] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". +- [25] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [26] 3GPP TS 24.575: "5G System; Multicast/Broadcast UE pre-configuration; Management Object (MO)". +- [27] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". + +# --- 3 Definitions of terms and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions defined in TR 21.905 [1] and the following apply: + +**5GC Individual MBS traffic delivery:** 5G CN receives a single copy of MBS data packets and delivers separate copies of those MBS data packets to individual UEs via per-UE PDU sessions, hence for each such UE one PDU session is required to be associated with a Multicast MBS Session. + +**5GC Shared MBS traffic delivery:** 5G CN receives a single copy of MBS data packets and delivers a single copy of those MBS data packets to a RAN node. + +**Area Session Identifier:** A unique identifier within an MBS Session used for an MBS session with location dependent content. When present, the Area Session ID, together with the TMGI, is used to uniquely identify the data flow of an MBS Session in a specific MBS service area. + +**Associated PDU Session:** A PDU Session associated to a multicast MBS session that is used for 5GC Individual MBS traffic delivery method and for signalling related to a user's participation in a multicast MBS session such as join and leave requests. + +**Associated QoS Flow:** A unicast QoS Flow that belongs to the associated PDU Session and is used for 5GC Individual MBS traffic delivery method. The associated QoS Flow is mapped from a multicast QoS Flow in a multicast MBS session. + +**Broadcast communication service:** A 5GS communication service in which the same service and the same specific content data are provided simultaneously to all UEs in a geographical area (i.e. all UEs in the broadcast coverage area are authorized to receive the data). + +NOTE 1: For the broadcast communication service, the content provider and network may not be aware whether the authorized UEs are actually receiving the data being delivered. + +**Broadcast MBS session:** An MBS session to deliver the broadcast communication service. A broadcast MBS session is characterised by the content to send and the geographical area where to distribute it. + +**Broadcast service area:** The area within which data of one or multiple Broadcast MBS session(s) are sent. + +**MBS QoS Flow:** The finest granularity for QoS forwarding treatment for MBS data. Providing different QoS forwarding treatment requires separate MBS QoS Flows in 5GS supporting MBS. + +**MBS Service Announcement:** Mechanism to allow users to be informed about the available MBS services. + +**MBS session:** A multicast MBS session or a broadcast MBS session. + +**MBS service area:** The area within which data of one Multicast or Broadcast MBS session may be sent. For location dependent MBS, for each MBS service area, an Area Session ID, which is unique per MBS Session ID, is allocated and the same location dependent content data for an MBS session is delivered to the UE(s) within an MBS service area. + +**Multicast communication service:** A 5GS communication service in which the same service and the same specific content data are provided simultaneously to a dedicated set of UEs (i.e. not all UEs in the coverage of the MBS service area are authorized to receive the data). + +NOTE 2: For multicast communication service, the content provider and network can be aware whether the authorized UEs are actually receiving the data being delivered. + +**Multicast MBS session:** An MBS session to deliver the multicast communication service. A multicast MBS session is characterised by the content to send, by the list of UEs that may receive the service and optionally by a geographical area where to distribute it. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [5] 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]. + +| | | +|--------|--------------------------------------------------| +| AL FEC | Application Level FEC | +| CDN | Content Delivery Network | +| FEC | Forward Error Correction | +| FSA | Frequency Selection Area | +| LL SSM | Lower Layer SSM | +| MBMS | Multimedia Broadcast/Multicast Service | +| MBS | Multicast/Broadcast Service. | +| MBSF | Multicast/Broadcast Service Function. | +| MBSTF | Multicast/Broadcast Service Transport Function. | +| MB-SMF | Multicast/Broadcast Session Management Function. | +| MB-UPF | Multicast/Broadcast User Plane Function | +| MSK | MBS Service Key | +| MTK | MBS Traffic Key | +| PTM | Point To Multipoint | +| PTP | Point To Point | +| PTW | Paging Transmission Window | +| SSM | Source Specific IP Multicast address. | +| TMGI | Temporary Mobile Group Identity | + +# 4 General Concept + +## 4.1 Overview of multicast and broadcast communication + +Multicast and Broadcast Service (MBS) is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients, either to all users in a Broadcast service area, or to users in a multicast group as defined in TS 22.146 [2]. The corresponding types of MBS session are: + +- Broadcast MBS session +- Multicast MBS session. + +The MBS architecture defined in clause 5 follows the 5G System architectural principles as defined in TS 23.501 [5], enabling distribution of the MBS data from the 5GS ingress to NG-RAN node(s) and then to the UE. The MBS architecture provides: + +- Efficient usage of RAN and CN resources, with an emphasis on radio interface efficiency; + +- Efficient transport for a variety of multicast and broadcast services. + +Multicast/Broadcast Service for roaming is not supported in this release. + +Interaction between Multicast/Broadcast Service and support of deployments topologies with specific SMF Service Areas is not specified in this Release. + +NOTE 1: For broadcast service over multiple MB-SMF Service Areas, mechanism of location dependent broadcast MBS Sessions is assumed to be applied. + +The collection and reporting of MBS specific charging information are not specified in this Release. + +The MBS also provides functionalities such as local MBS service and location dependent MBS service, authorization of multicast MBS and QoS differentiation. Refer to clause 6 for more details. + +MBS traffic is delivered from a single data source (e.g. Application Service Provider) to multiple UEs. Depending on many factors, there are several delivery methods which may be used to deliver the MBS traffic in the 5GS. + +NOTE 2: For clarity, delivery methods are not referred to as unicast/multicast/broadcast but as described below. The term "unicast delivery" refers to a mechanism by which application data and signalling between the UE and the application server are delivered using PDU Session within the 3GPP network and using individual UE and application server addresses (e.g. IP addresses) between the 3GPP network and the application server. It is not equivalent to 5GC Individual MBS traffic delivery method defined in this clause. + +Between 5GC and NG-RAN, there are two possible delivery methods to transmit the MBS data: + +- 5GC Individual MBS traffic delivery method: This method is only applied for multicast MBS sessions. 5GC receives a single copy of MBS data packets and delivers separate copies of those MBS data packets to individual UEs via per-UE PDU sessions, hence for each such UE one PDU session is required to be associated with a Multicast MBS session. +- 5GC Shared MBS traffic delivery method: This method is applied for both broadcast and multicast MBS sessions. 5GC receives a single copy of MBS data packets and delivers a single copy of those MBS packets to an NG-RAN node, which then delivers the packets to one or multiple UEs. + +The 5GC Shared MBS traffic delivery method is required in all MBS deployments. The 5GC Individual MBS traffic delivery method is required to enable mobility when there is an NG-RAN deployment with non-homogeneous support of MBS. + +For the Multicast MBS session, a single copy of MBS data packets received by the CN may be delivered via 5GC Individual MBS traffic delivery method for some UE(s) and via 5GC Shared MBS traffic delivery method for other UEs. + +Between the NG-RAN and the UE, two delivery methods are available for the transmission of MBS data packets over radio interface: + +- Point-to-Point (PTP) delivery method: NG-RAN delivers separate copies of MBS data packets over radio interface to individual UE(s). +- Point-to-Multipoint (PTM) delivery method: NG-RAN delivers a single copy of MBS data packets over radio interface to multiple UEs. + +NG-RAN may use a combination of PTP/PTM to deliver an MBS data packets to UEs. + +NOTE 3: The PTP and PTM delivery methods are defined in RAN WGs. + +As depicted in the following figure, 5GC Shared MBS traffic delivery method (with PTP or PTM delivery) and 5GC Individual MBS traffic delivery method may be used at the same time for a multicast MBS session. + +![Diagram illustrating delivery methods for MBS traffic. The diagram shows three delivery paths from the 5GC to UEs via the NG-RAN. 1. 5GC Shared MBS Traffic delivery (Shared Transport) to two UEs via PTM or PTP over radio. 2. 5GC Individual MBS Traffic Delivery (PDU Session) to one UE. 3. 5GC Shared MBS Traffic delivery (PDU Session) to one UE. The 5GC contains a Replication function that receives MBS traffic and distributes it to the NG-RAN.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the delivery methods for MBS traffic. On the right, 'MBS traffic' enters the '5GC' block. Inside the 5GC, there is a 'Replication' function. From the Replication function, three delivery paths are shown: + + +- A top path labeled '5GC Shared MBS Traffic delivery' and 'Shared Transport' leads to the 'NG-RAN' and then to two 'UE' boxes. The delivery over the radio is labeled 'PTM or PTP over radio'. +- A middle path labeled 'PDU Session' leads from the Replication function to a single 'UE' box. +- A bottom path labeled '5GC Individual MBS Traffic Delivery' and 'PDU Session' leads from the Replication function to another single 'UE' box. + + The 'NG-RAN' is shown as a central vertical block between the 5GC and the UEs. + +Diagram illustrating delivery methods for MBS traffic. The diagram shows three delivery paths from the 5GC to UEs via the NG-RAN. 1. 5GC Shared MBS Traffic delivery (Shared Transport) to two UEs via PTM or PTP over radio. 2. 5GC Individual MBS Traffic Delivery (PDU Session) to one UE. 3. 5GC Shared MBS Traffic delivery (PDU Session) to one UE. The 5GC contains a Replication function that receives MBS traffic and distributes it to the NG-RAN. + +**Figure 4.1-1: Delivery methods** + +For MBS broadcast communication, only 5GC Shared MBS traffic delivery method with PTM delivery is applicable. + +For MBS multicast communication, if the NG-RAN node supports MBS, the network shall use the 5GC Shared MBS traffic delivery method for MBS data transmission. + +NOTE 4: The exception is when the UE moves between NG-RAN node not supporting MBS (with 5GC Individual MBS traffic delivery method) and NG-RAN node supporting MBS, there is temporary co-existence between 5GC Shared MBS traffic delivery method and 5GC Individual MBS traffic delivery method. Refer to clause 6.3 for details. + +For MBS multicast communication, the switching between 5GC Shared MBS traffic delivery method and 5GC Individual MBS traffic delivery method is supported. The UE mobility between RAN nodes both supporting MBS, and between a RAN node supporting MBS and a RAN node not supporting MBS is supported, for details see clause 6.3. + +For MBS multicast communication, the switching between PTP and PTM delivery methods for 5GC Shared MBS traffic delivery shall be supported. NG-RAN is the decision point for switching between PTP and PTM delivery methods. + +## 4.2 MB service provisioning + +### 4.2.1 Multicast data provisioning + +An example for the sequence of phases for multicast data provisioning is described in the figure below: + +![Flowchart illustrating the phases of Multicast data provisioning example. The phases are: MBS Session Creation & Service Announcement, UE Session Join & Session Establishment, Data Transfer, UE Session Leave & Session Release, and MBS Session Deletion. The flow is vertical, with a large downward arrow at the bottom indicating continuation.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` +graph TD; A[MBS Session Creation & Service Announcement] --> B[UE Session Join & Session Establishment]; B --> C[Data Transfer]; C --> D[UE Session Leave & Session Release]; D --> E[MBS Session Deletion]; E --> F[ ] style F fill:none,stroke:none; style A fill:#808080,color:white; style B fill:#808080,color:white; style C fill:#808080,color:white; style D fill:#808080,color:white; style E fill:#808080,color:white; +``` + +Flowchart illustrating the phases of Multicast data provisioning example. The phases are: MBS Session Creation & Service Announcement, UE Session Join & Session Establishment, Data Transfer, UE Session Leave & Session Release, and MBS Session Deletion. The flow is vertical, with a large downward arrow at the bottom indicating continuation. + +**Figure 4.2.1-1: Phases of Multicast data provisioning example** + +The following phases are performed for a specific UE: + +- UE Session Join: UE Session Join is the process by which a UE joins an MBS Session, i.e. the UE indicates to 5GC that such UE wants to receive Multicast data identified by a specific MBS Session ID. +- UE Session Leave: UE Session Leave is the process by which a UE leaves a MBS Session, i.e. the UE no longer wants to receive Multicast data identified by a specific MBS Session ID. + +The following phases are performed for a specific service: + +- MBS Session Creation: It is the phase that the information of Multicast MBS session is created as described in clause 4.3. This step is optional. +- Service announcement: Service announcement is used to distribute information toward UEs about the service required for service reception (e.g. IP multicast address(es)) and possibly other service related parameters (e.g. service start time). This step is optional. +- Session Establishment: It is the phase that Multicast MBS session is established as described in clause 4.3. +- No data receiving: It is the phase when no multicast data is received by 5GC. This step is optional. +- Data transfer: It is the phase when Multicast data are transferred to the UEs. +- Session Release: It is the phase that the resources for Multicast MBS session is released as described in clause 4.3. +- Session Deletion: It is the phase that Multicast MBS session is deleted as described in clause 4.3. + +**NOTE:** After session establishment, Multicast MBS session state could be switched between Active and Inactive several times, triggered by AF or User Plane event, see clause 7.2.5. 5GC further updates Multicast MBS session state towards NG-RAN nodes after Session Establishment. + +The phase of Multicast data provisioning is illustrated with the following example of timeline: + +![Figure 4.2.1-2: Multicast service timeline example. This diagram illustrates the timeline of a multicast service across four horizontal axes: UE 1 events, UE 2 events, Multicast Session, and Data volume sent in the air. UE 1 and UE 2 events show 'Session Join' (green dot) and 'Session Leave' (red dot) points. The 'Session established period' for UE 1 is the interval between its join and leave events. The Multicast Session axis shows 'MBS Session Creation and Service Announcement' (blue dot), 'Session Establishment' (blue dot), three 'Data Transfer' intervals (green arrows), 'Session Release' (blue dot), and 'MBS Session Deletion' (blue dot). The 'Session existing period' is the interval from establishment to release. The Data volume axis shows four green blocks representing data sent: 'Data sent to UE1', 'Data sent to UE1 and UE2', 'Data sent to UE1 and UE2', and 'Data sent to UE2'.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 4.2.1-2: Multicast service timeline example. This diagram illustrates the timeline of a multicast service across four horizontal axes: UE 1 events, UE 2 events, Multicast Session, and Data volume sent in the air. UE 1 and UE 2 events show 'Session Join' (green dot) and 'Session Leave' (red dot) points. The 'Session established period' for UE 1 is the interval between its join and leave events. The Multicast Session axis shows 'MBS Session Creation and Service Announcement' (blue dot), 'Session Establishment' (blue dot), three 'Data Transfer' intervals (green arrows), 'Session Release' (blue dot), and 'MBS Session Deletion' (blue dot). The 'Session existing period' is the interval from establishment to release. The Data volume axis shows four green blocks representing data sent: 'Data sent to UE1', 'Data sent to UE1 and UE2', 'Data sent to UE1 and UE2', and 'Data sent to UE2'. + +Figure 4.2.1-2: Multicast service timeline example + +### 4.2.2 Broadcast data provisioning + +An example for the phases of broadcast data provisioning is described in the figure below: + +![Figure 4.2.2-1: Phases of Broadcast data provisioning. This diagram shows three stacked rectangular boxes representing the phases of broadcast data provisioning. The top box is labeled 'Session Creation and establishment & Service Announcement'. The middle box is labeled 'Data Transfer'. The bottom box is labeled 'Session Release and Deletion'. A large grey arrow points downwards from the bottom box, indicating the sequence of phases.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +Figure 4.2.2-1: Phases of Broadcast data provisioning. This diagram shows three stacked rectangular boxes representing the phases of broadcast data provisioning. The top box is labeled 'Session Creation and establishment & Service Announcement'. The middle box is labeled 'Data Transfer'. The bottom box is labeled 'Session Release and Deletion'. A large grey arrow points downwards from the bottom box, indicating the sequence of phases. + +Figure 4.2.2-1: Phases of Broadcast data provisioning + +The following phases are performed for a specific service: + +- MBS Session Creation and establishment: MBS Session Creation is used by the AF to create the MBS Session towards 5GC. MBS session creation can occur in several steps (e.g. TMGI allocation, provisioning information about MBS session, request to activate the MBS session). The last step of the MBS session creation triggers resource establishment for transmitting the DL Broadcast data between 5GC and NG-RAN. + +NOTE: For broadcast communication, after MBS Session Creation and Session Establishment, the established resources are not only between 5GC and NG-RAN, but also between the AF to 5GC. + +- Service announcement: Service announcement is used to distribute information towards UEs about the service required for service reception (e.g. IP multicast address(es)) and possibly other service related parameters (e.g. service start time). This step can occur in parallel or after the MBS session configuration. However, TMGI allocation is required before. The information of the service announcement, is defined in clause 6.11. +- Data transfer: It is the phase when broadcast data are transferred in the air interface. + +- **Session Release and Deletion:** It is the point at which there will be no more need to transmit Broadcast data. At Session Release, the resources in 5GS are released and the broadcast MBS session is deleted. + +The phase of Broadcast data provisioning is illustrated with the following example of timeline: + +![Figure 4.2.2-2: Broadcast service timeline. This diagram illustrates the temporal sequence of events for a broadcast service across two User Equipment (UE) timelines and a central Broadcast Session timeline. The top timeline, 'UE 1 events', shows a green segment for 'UE1 service activation' starting at a green dot and ending at a red dot for 'UE1 service de-activation'. The second timeline, 'UE 2 events', shows a similar green segment for 'UE2 service activation' and 'UE2 service de-activation'. The 'Broadcast Session' timeline below shows a blue line starting with 'Session Creation and establishment & Service Announcement' (blue dot) and ending with 'Session Release and Deletion' (blue dot). A light blue double-headed arrow labeled 'Session existing period' spans this duration. Green arrows labeled 'Data Transfer' point from the session to the UEs. At the bottom, a grey bar labeled 'Data volume received by any service-activated UE' has three green rectangular blocks. A callout box points to these blocks with the text 'Broadcast of Data, received by any UE which is present'. A horizontal axis at the top right is labeled 'Time'.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +Figure 4.2.2-2: Broadcast service timeline. This diagram illustrates the temporal sequence of events for a broadcast service across two User Equipment (UE) timelines and a central Broadcast Session timeline. The top timeline, 'UE 1 events', shows a green segment for 'UE1 service activation' starting at a green dot and ending at a red dot for 'UE1 service de-activation'. The second timeline, 'UE 2 events', shows a similar green segment for 'UE2 service activation' and 'UE2 service de-activation'. The 'Broadcast Session' timeline below shows a blue line starting with 'Session Creation and establishment & Service Announcement' (blue dot) and ending with 'Session Release and Deletion' (blue dot). A light blue double-headed arrow labeled 'Session existing period' spans this duration. Green arrows labeled 'Data Transfer' point from the session to the UEs. At the bottom, a grey bar labeled 'Data volume received by any service-activated UE' has three green rectangular blocks. A callout box points to these blocks with the text 'Broadcast of Data, received by any UE which is present'. A horizontal axis at the top right is labeled 'Time'. + +Figure 4.2.2-2: Broadcast service timeline + +## 4.3 Multicast session state model + +The following illustrate the states for the Multicast MBS session: + +- **Configured state:** Information about the Multicast MBS session (e.g. QoS information) is available in 5GC NFs (e.g. MB-SMF) serving the Multicast MBS session, but no User Plane resources towards NG-RAN are reserved and no MBS data can be transmitted. Only resources at MB-SMF, NEF and MB-UPF are reserved and no multicast data are transmitted. A TMGI can be allocated for the Multicast MBS session. UEs may be allowed to join (subject to authorization check and configuration), but the first accepted UE join request will trigger the Multicast MBS session establishment towards the NG-RAN and the UE, see clause 7.2.1. + +NOTE 1: The SMF is not involved in the Multicast MBS session while the Multicast MBS session is in configured state. + +NOTE 2: There may be several interim states in the configured state, e.g. TMGI requested, or information about the Multicast MBS session provided, but these interim states will not be specified in this release. + +- **Active state:** Multicast MBS session is established and MBS data can be transmitted to the UEs that have joined the Multicast MBS session. Radio resources for the Multicast MBS session are established. To receive multicast MBS session data, UEs that joined the Multicast MBS session shall be in CM-CONNECTED state for receiving data of the Multicast MBS session. UEs are allowed to join the Multicast MBS session (subject to authorization check). 5GC resources and radio resources for the Multicast MBS session are reserved for UEs that joined the Multicast MBS session. + +NOTE 3: When receiving the data of the Multicast MBS session, the joined UEs can be in CM-CONNECTED with RRC\_INACTIVE state as defined in clause 6.17. + +- **Inactive state:** Multicast MBS session is established but no MBS data is transmitted to the UEs that have joined the Multicast MBS session. Radio resources for the Multicast MBS session are released, and the UEs that joined the Multicast MBS session may be in CM-CONNECTED or CM-IDLE state. UEs are allowed to join the Multicast MBS session (subject to authorization check). + +The following procedures are defined which result in transition of the Multicast MBS session state: + +**Multicast Session Creation:** The AF provides information about the Multicast MBS session and optionally requests the allocation of a TMGI, see clause 7.1.1.2 and 7.1.1.3. Alternatively, the information about the Multicast MBS session can be pre-configured in the network. The creation may indicate whether the Multicast MBS session may be established in active or inactive state and when a Multicast MBS session can become active. The AF may perform creation in several steps, e.g. to first request TMGI and then provide full information about the Multicast MBS session and allow it to be established, or to update the information whether the Multicast MBS session is to be in Active or Inactive state after establishment. Multicast MBS session state transitions from "Start (NULL)" to Configured state. + +NOTE 4: A Multicast MBS session can also be created by the operator via OAM configuration or be established without prior creation. + +- **Multicast Session Establishment:** When the join request of the first UE for the Multicast MBS session is accepted, the Multicast MBS session is established towards the NG-RAN node and the UE, see clause 7.2.1. Multicast session state transitions from "Start (NULL)" or Configured state to either Inactive or Active state. + +- **Multicast Session Activation:** See clause 7.2.5.2. Triggered by the 5GC, the radio resources for the Multicast MBS session are established and Multicast MBS session data starts to be transmitted to the UE. UEs in CM-IDLE state and CM-CONNECTED with RRC Inactive state that joined the Multicast MBS session are notified. Activation can be triggered by AF request or data notification from the MB-UPF. Multicast session state transitions from Inactive state to Active state. + +NOTE 5: The AF could not be aware, and the NEF will not be aware, whether a session is in created or established state. An AF may therefore update the session state to request the activation of a session prior to the establishment of the session, and this will determine that the session is subsequently established in Active state when the first UE joins, but will not trigger the Multicast Session Activation state transition. + +- **Multicast Session Deactivation:** See clause 7.2.5.3. Triggered by the 5GC, the radio resources for the Multicast MBS session are released and Multicast MBS session data stops to be transmitted to the UE. Deactivation can be triggered by AF request or no reception of multicast data by the MB-UPF. Multicast session state transitions from Active to Inactive state. +- **Multicast Session Release:** Triggered by the last UE leaving the Multicast MBS session (see clause 7.2.2.2), or Multicast Session Deletion procedure (7.1.1.4 or 7.1.1.5), the resources for the Multicast MBS session are released in both 5GC nodes and RAN nodes, see clause 7.2.2. Multicast session state transitions from Active or Inactive state to Configured. +- **Multicast Session Deletion:** All information about the Multicast MBS session is removed from the 5GC, and the TMGI for the Multicast MBS session (if allocated during Multicast Session Configuration) is deallocated, see clause 7.1.1.4 or 7.1.1.5. The deletion may be triggered by an AF request. Multicast session state transitions from Configured, Active or Inactive state to "End (NULL)". + +![Figure 4.3-1: Multicast session states and state transitions. This state machine diagram shows four states: Start (NULL), Configured Multicast Session, Active Multicast Session, and Inactive Multicast Session, and End (NULL). Transitions include: Start (NULL) to Configured Multicast Session via 'Creation'; Configured Multicast Session to Active Multicast Session via 'Establishment'; Active Multicast Session to Configured Multicast Session via 'Release'; Configured Multicast Session to Inactive Multicast Session via 'Establishment'; Inactive Multicast Session to Configured Multicast Session via 'Release'; Active Multicast Session to Inactive Multicast Session via 'Deactivation'; Inactive Multicast Session to Active Multicast Session via 'Activation'; Active Multicast Session to End (NULL) via 'Deletion'; Inactive Multicast Session to End (NULL) via 'Deletion'; Configured Multicast Session to End (NULL) via 'Deletion'; and a long 'Establishment' transition from Start (NULL) to Active Multicast Session.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 4.3-1: Multicast session states and state transitions. This state machine diagram shows four states: Start (NULL), Configured Multicast Session, Active Multicast Session, and Inactive Multicast Session, and End (NULL). Transitions include: Start (NULL) to Configured Multicast Session via 'Creation'; Configured Multicast Session to Active Multicast Session via 'Establishment'; Active Multicast Session to Configured Multicast Session via 'Release'; Configured Multicast Session to Inactive Multicast Session via 'Establishment'; Inactive Multicast Session to Configured Multicast Session via 'Release'; Active Multicast Session to Inactive Multicast Session via 'Deactivation'; Inactive Multicast Session to Active Multicast Session via 'Activation'; Active Multicast Session to End (NULL) via 'Deletion'; Inactive Multicast Session to End (NULL) via 'Deletion'; Configured Multicast Session to End (NULL) via 'Deletion'; and a long 'Establishment' transition from Start (NULL) to Active Multicast Session. + +Figure 4.3-1: Multicast session states and state transitions + +![Figure 4.3-2: Multicast session states and state transitions in MB-SMF. This state machine diagram shows four states: Start (NULL), Configured, Active, and Inactive, and End (NULL). Transitions include: Start (NULL) to Configured via 'Session Creation'; Configured to Start (NULL) via 'Session Deletion'; Configured to Active via 'Session Establishment'; Active to Configured via 'Session Release'; Configured to Inactive via 'Session Deactivation'; Inactive to Configured via 'Session Establishment'; Active to Inactive via 'Session Deactivation'; Inactive to Active via 'Session Activation'; and End (NULL) to Configured via 'Session Deletion'.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Figure 4.3-2: Multicast session states and state transitions in MB-SMF. This state machine diagram shows four states: Start (NULL), Configured, Active, and Inactive, and End (NULL). Transitions include: Start (NULL) to Configured via 'Session Creation'; Configured to Start (NULL) via 'Session Deletion'; Configured to Active via 'Session Establishment'; Active to Configured via 'Session Release'; Configured to Inactive via 'Session Deactivation'; Inactive to Configured via 'Session Establishment'; Active to Inactive via 'Session Deactivation'; Inactive to Active via 'Session Activation'; and End (NULL) to Configured via 'Session Deletion'. + +Figure 4.3-2: Multicast session states and state transitions in MB-SMF + +![Figure 4.3-3: Multicast session states and state transitions in NG-RAN. This state machine diagram shows four states: Start (NULL), Active, Inactive, and End (NULL). Transitions include: Start (NULL) to Active via 'first UE joins the multicast session in the NG-RAN node'; Start (NULL) to Inactive via 'first UE joins the multicast session in the NG-RAN node'; Active to Inactive via 'Session Deactivation'; Inactive to Active via 'Session Activation'; Active to End (NULL) via 'Last UE leaves the multicast session in the NG-RAN node'; and Inactive to End (NULL) via 'Last UE leaves the multicast session in the NG-RAN node'.](12de9b926df0384ec07702671827c9cd_img.jpg) + +Figure 4.3-3: Multicast session states and state transitions in NG-RAN. This state machine diagram shows four states: Start (NULL), Active, Inactive, and End (NULL). Transitions include: Start (NULL) to Active via 'first UE joins the multicast session in the NG-RAN node'; Start (NULL) to Inactive via 'first UE joins the multicast session in the NG-RAN node'; Active to Inactive via 'Session Deactivation'; Inactive to Active via 'Session Activation'; Active to End (NULL) via 'Last UE leaves the multicast session in the NG-RAN node'; and Inactive to End (NULL) via 'Last UE leaves the multicast session in the NG-RAN node'. + +Figure 4.3-3: Multicast session states and state transitions in NG-RAN + +NOTE 6: Multicast session states and state transitions in NG-RAN is for illustration purpose, normative procedures are provided by RAN WGs. + +![Figure 4.3-4: Multicast session states and state transitions in SMF. The diagram shows three states: Start (NULL), Active, and Inactive. Transitions are: Start to Active (first UE joins the multicast session in SMF), Start to Inactive (first UE joins the multicast session in the SMF), Active to Inactive (Session Deactivation), Inactive to Active (Session Activation), Active to End (NULL) (Last UE leaves the multicast session in SMF), and Inactive to End (NULL) (Last UE leaves the multicast session in SMF).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Active : first UE joins the multicast session in SMF + [*] --> Inactive : first UE joins the multicast session in the SMF + Inactive --> Active : Session Activation + Active --> Inactive : Session Deactivation + Active --> [*] : Last UE leaves the multicast session in SMF + Inactive --> [*] : Last UE leaves the multicast session in SMF + +``` + +Figure 4.3-4: Multicast session states and state transitions in SMF. The diagram shows three states: Start (NULL), Active, and Inactive. Transitions are: Start to Active (first UE joins the multicast session in SMF), Start to Inactive (first UE joins the multicast session in the SMF), Active to Inactive (Session Deactivation), Inactive to Active (Session Activation), Active to End (NULL) (Last UE leaves the multicast session in SMF), and Inactive to End (NULL) (Last UE leaves the multicast session in SMF). + +Figure 4.3-4: Multicast session states and state transitions in SMF + +# 5 Architecture model + +## 5.1 General architecture + +Figure 5.1-1 depicts the MBS reference architecture. Service-based interfaces are used within the Control Plane. Support for interworking at reference points xMB and MB2 is described in Annex C. + +![Figure 5.1-1: 5G System architecture for Multicast and Broadcast Service. The diagram shows the following components and interfaces: UE connected to NG-RAN via Uu; NG-RAN connected to AMF via N1, N2, and N3mb; AMF connected to PCF via Npcf, SMF via Nsmf, MB-SMF via Nmbsmf, MB-SF via Nmb2, NEF via Nnef, and AF/AS via Naf; SMF connected to UPF via N4; UPF connected to MB-UPF via N19mb; MB-UPF connected to MBSTF via Nmb9; MBSTF connected to NEF via Nmb14 and to AF/AS via Nmb8; MBSTF also connected to NG-RAN via N3mb and to MB-UPF via N6mb. NRF is connected to PCF via Nnrf, SMF via Nsmf, MB-SMF via Nmbsmf, MB-SF via Nmb2, NEF via Nnef, and AF/AS via Naf. UDM is connected to PCF via Nudm, SMF via Nsmf, MB-SMF via Nmbsmf, MB-SF via Nmb2, NEF via Nnef, and AF/AS via Naf.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Figure 5.1-1: 5G System architecture for Multicast and Broadcast Service. The diagram shows the following components and interfaces: UE connected to NG-RAN via Uu; NG-RAN connected to AMF via N1, N2, and N3mb; AMF connected to PCF via Npcf, SMF via Nsmf, MB-SMF via Nmbsmf, MB-SF via Nmb2, NEF via Nnef, and AF/AS via Naf; SMF connected to UPF via N4; UPF connected to MB-UPF via N19mb; MB-UPF connected to MBSTF via Nmb9; MBSTF connected to NEF via Nmb14 and to AF/AS via Nmb8; MBSTF also connected to NG-RAN via N3mb and to MB-UPF via N6mb. NRF is connected to PCF via Nnrf, SMF via Nsmf, MB-SMF via Nmbsmf, MB-SF via Nmb2, NEF via Nnef, and AF/AS via Naf. UDM is connected to PCF via Nudm, SMF via Nsmf, MB-SMF via Nmbsmf, MB-SF via Nmb2, NEF via Nnef, and AF/AS via Naf. + +Figure 5.1-1: 5G System architecture for Multicast and Broadcast Service. + +NOTE 1: The MB-SF is optional and may be collocated with the NEF or AF/AS, and the MBSTF is an optional network function. + +NOTE 2: The existing service-based interfaces of Nnrf, Nudm, and Nsmf are enhanced to support MBS. The existing service-based interfaces of Npcf and Nnef are enhanced to support MBS. + +NOTE 3: A MBS-enabled AF uses either Nmb2 or Nnef to interact with the MB-SF. + +Figure 5.1-2 depicts the 5G system architecture for MBS using the reference point representation. + +![Figure 5.1-2: 5G System architecture for Multicast and Broadcast Service in reference point representation. The diagram shows the flow of data and signaling between various 5G network functions (UE, NG-RAN, AMF, SMF, UDM, UPF, MB-SMF, MB-UPF, PCF, MBSF, MBSTF, NEF, AF/AS) via reference points (N1, N2, N3, N4, N5, N6, N7, N10, N11, N16, N19, N29, N30, N33, Nmb1-Nmb14).](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram illustrates the 5G system architecture for Multicast and Broadcast Service (MBS). It shows the following components and their interconnections: + +- UE** (User Equipment) is connected to **NG-RAN** via the **Uu** interface. +- NG-RAN** is connected to **AMF** via **N2** and to **UPF** via **N3**. +- AMF** is connected to **UE** via **N1**, to **SMF** via **N11**, and to **NG-RAN** via **N2**. +- SMF** is connected to **AMF** via **N11**, to **UDM** via **N10**, to **UPF** via **N4**, and to **MB-SMF** via **N16mb**. +- UDM** is connected to **SMF** via **N10**. +- UPF** is connected to **SMF** via **N4**, to **NG-RAN** via **N3**, and to **MB-UPF** via **N19mb**. +- MB-SMF** is connected to **SMF** via **N16mb**, to **UPF** via **N4mb**, to **PCF** via **N29mb**, and to **MBSF** via **Nmb1**. +- PCF** is connected to **MB-SMF** via **N29mb**, to **NEF** via **N30**, and to **MBSF** via **N7mb**. +- NEF** is connected to **PCF** via **N30**, to **AF/AS** via **N33**, and to **MBSF** via **Nmb5**. +- MBSF** is connected to **MB-SMF** via **Nmb1**, to **PCF** via **N7mb**, to **NEF** via **Nmb5**, to **AF/AS** via **N5** and **Nmb10**, and to **MBSTF** via **Nmb2**. +- MBSTF** is connected to **MBSF** via **Nmb2**, to **UPF** via **N6mb**, to **MB-UPF** via **Nmb9**, and to **AF/AS** via **Nmb8**. +- AF/AS** (Application Function/Application Server) is connected to **NEF** via **N33**, to **PCF** via **N5**, to **MBSF** via **N5** and **Nmb10**, and to **MBSTF** via **Nmb8**. +- Additional reference points shown include **N11mb** between AMF and SMF, **N3mb** between NG-RAN and UPF, **Nmb12** between PCF and MBSF, **Nmb13** between MB-SMF and MBSF, and **Nmb14** between NEF and AF/AS. + +Figure 5.1-2: 5G System architecture for Multicast and Broadcast Service in reference point representation. The diagram shows the flow of data and signaling between various 5G network functions (UE, NG-RAN, AMF, SMF, UDM, UPF, MB-SMF, MB-UPF, PCF, MBSF, MBSTF, NEF, AF/AS) via reference points (N1, N2, N3, N4, N5, N6, N7, N10, N11, N16, N19, N29, N30, N33, Nmb1-Nmb14). + +**Figure 5.1-2: 5G System architecture for Multicast and Broadcast Service in reference point representation.** + +NOTE 4: The existing reference points of N1, N2, N4, N5, N10, N11, N30 and N33 are enhanced to support MBS. + +NOTE 5: Regarding the functionalities, Nmb13, N29mb and Nmb1 are identical, Nmb5 and Nmb10 are identical, Nmb9 and N6mb are identical. + +## 5.2 General architecture for interworking with EPS + +Interworking between MBS and eMBMS at service layer functionality applies in cases where the same Multicast/Broadcast service is provided via eMBMS and MBS. Figure 5.2-1 depicts the system architecture for interworking between E-UTRAN/EPC eMBMS and MBS at service layer, with collocated BM-SC and MBSF/MBSTF functionalities. + +![Figure 5.2-1: MBS-eMBMS interworking system architecture at service layer. The diagram shows the interworking between EPS (Evolved Packet System) and 5GS (5G System) for MBS (Multimedia Broadcast Service). In the EPS part, a UE connects to E-UTRAN via Uu, which connects to MME via M3. MME connects to MBMS-GW via Sm. MBMS-GW connects to E-UTRAN via M1 and to MBSF via SGmb. MBSF connects to MBSTF via Nmb2. MBSTF connects to the Joint BM-SC + MBSF Functionality via Nmb8/xMB-U/MB2-U. The Joint BM-SC + MBSF Functionality connects to MBMS-GW via SGi-mb and to MB-UPF via Nmb9. In the 5GS part, a UE connects to NG-RAN via Uu, which connects to AMF via N1. AMF connects to SMF via N11 and to NG-RAN via N2. SMF connects to MB-SMF via N16mb and to UPF via N4. MB-SMF connects to AMF via N11mb and to MB-UPF via N4mb. UPF connects to NG-RAN via N3 and to MB-UPF via N19mb. MB-UPF connects to NG-RAN via N3mb and to the Joint BM-SC + MBSF Functionality via Nmb9. The Joint BM-SC + MBSF Functionality also connects to the NEF and/or AF/AS via Nmb5/Nmb10/xMB-C/MB2-C and Nmb8/xMB-U/MB2-U reference points.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 5.2-1: MBS-eMBMS interworking system architecture at service layer. The diagram shows the interworking between EPS (Evolved Packet System) and 5GS (5G System) for MBS (Multimedia Broadcast Service). In the EPS part, a UE connects to E-UTRAN via Uu, which connects to MME via M3. MME connects to MBMS-GW via Sm. MBMS-GW connects to E-UTRAN via M1 and to MBSF via SGmb. MBSF connects to MBSTF via Nmb2. MBSTF connects to the Joint BM-SC + MBSF Functionality via Nmb8/xMB-U/MB2-U. The Joint BM-SC + MBSF Functionality connects to MBMS-GW via SGi-mb and to MB-UPF via Nmb9. In the 5GS part, a UE connects to NG-RAN via Uu, which connects to AMF via N1. AMF connects to SMF via N11 and to NG-RAN via N2. SMF connects to MB-SMF via N16mb and to UPF via N4. MB-SMF connects to AMF via N11mb and to MB-UPF via N4mb. UPF connects to NG-RAN via N3 and to MB-UPF via N19mb. MB-UPF connects to NG-RAN via N3mb and to the Joint BM-SC + MBSF Functionality via Nmb9. The Joint BM-SC + MBSF Functionality also connects to the NEF and/or AF/AS via Nmb5/Nmb10/xMB-C/MB2-C and Nmb8/xMB-U/MB2-U reference points. + +**Figure 5.2-1: MBS-eMBMS interworking system architecture at service layer** + +The BM-SC+MBSF/MBSTF exposes common Nmb5/Nmb10/xMB-C/MB2-C and Nmb8/xMB-U/MB2-U reference points to the NEF and/or AF/AS. A common TMGI is used towards the AF/AS. The TMGI is also used as identifier for transport over E-UTRAN/EPC. The MBSTF distributes the received data to the MB-UPF at reference point Nmb9 and/or the MBMS-GW at reference point SGi-mb, when supported by operator network configuration. + +NOTE 1: MB2-C/U and xMB-C/U are legacy reference points. + +NOTE 2: In the case of MBSTF providing MB2-C/U, it may be used for the GCS/AS only supporting GC1 and MB2 interfaces, as defined TS 23.468 [10]. + +## 5.3 Service-based interfaces, Reference point and functional entities + +### 5.3.0 Service-based interfaces + +The 5G System Architecture for MBS contains the following service-based interfaces: + +- Nmbsmf:** Service-based interface exhibited by MB-SMF. Further details are described in clause 9.1. +- Npcf:** Service-based interface exhibited by PCF. Further details are described in clause 9.2. +- Namf:** Service-based interface exhibited by AMF. Further details are described in clause 9.3. +- Nnef:** Service-based interface exhibited by NEF. Further details are described in clause 9.4. +- Nmbf:** Service-based interface exhibited by MBSF. Further details are described in clause 9.5. + +### 5.3.1 Reference point + +The 5G System Architecture for MBS contains the following new reference points: + +- N3mb:** Reference point between the RAN and the MB-UPF. +- N4mb:** Reference point between the MB-SMF and the MB-UPF. +- N6mb:** Reference point between the MB-UPF and the AF/AS. +- N7mb:** Reference point between the MB-SMF and the PCF. +- N11mb:** Reference point between the AMF and the MB-SMF. +- N16mb:** Reference point between the SMF and the MB-SMF. +- N19mb:** Reference Point between the UPF and the MB-UPF. +- N29mb:** Reference point between the MB-SMF and the NEF. +- Nmb1:** Reference point between the MB-SMF and the MBSF. +- Nmb2:** Reference point between the MBSF and the MBSTF. +- Nmb5:** Reference point between the MBSF and the NEF. +- Nmb8:** Reference point between the MBSTF and the AF. +- Nmb9:** Reference point between the MB-UPF and the MBSTF. +- Nmb10:** Reference point between the MBSF and the AF. +- Nmb12:** Reference point between the MBSF and the PCF. +- Nmb13:** Reference point between the MB-SMF and the AF. +- Nmb14:** Reference point between the NEF and the MBSTF. + +5G System Architecture for MBS reuses the existing reference points of N1, N2, N4, N10, N11, N30 and N33 with enhancement to support MBS. + +### 5.3.2 Functional entities + +#### 5.3.2.1 PCF + +In addition to the functions defined in TS 23.501 [5], the PCF performs the following functions to support MBS if dynamic PCC for MBS is needed: + +- Supporting QoS handling for MBS Session. +- Providing policy information regarding the MBS Session to MB-SMF for authorizing the related QoS profiles. +- Interacting with UDR for QoS information retrieval. +- The PCF can receive MBS information from AF, NEF or MBSF, e.g. based on the different configuration options in Annex A. + +#### 5.3.2.2 MB-SMF + +The MB-SMF performs the following functions to support MBS: + +- General for Multicast and Broadcast MBS sessions: + - Supporting MBS session management (including QoS control). + - Configuring the MB-UPF for multicast and broadcast data transport, based on the policy rules for multicast and broadcast services from PCF or local policy. + - Allocating and de-allocating TMGIs. + +- Specific for Broadcast MBS sessions: + - Interacting with RAN (via AMF) to control data transport using 5GC Shared MBS traffic delivery method. +- Specific for Multicast MBS sessions: + - Interacting with SMF to provide the SMF with MBS Session Context information. + - Interacting with RAN (via AMF) to establish data transmission resources between MB-UPF and RAN nodes for 5GC Shared MBS traffic delivery method. + - Controlling the MB-UPF for multicast data transport using 5GC Individual MBS traffic delivery method. + +#### 5.3.2.3 SMF + +In addition to the functions defined in TS 23.501 [5], the SMF performs the following functions to support MBS: + +- Discovering MB-SMF for a Multicast MBS session. +- Authorizing Multicast MBS session join operation for served UEs if needed. +- Interacting with MB-SMF to obtain multicast Session Context information used as input to modify the PDU Session associated with MBS session. +- Interacting with RAN to provide information about a Multicast MBS session that a UE is participating in. +- Interacting with RAN and UPF for multicast data transport using 5GC Individual MBS traffic delivery method. +- Interacting with RAN to provide MBS Assistance Information for the MBS session. + +NOTE: SMF and MB-SMF may be co-located or deployed separately. + +#### 5.3.2.4 MB-UPF + +The MB-UPF performs the following functions to support MBS: + +- General for Multicast and Broadcast MBS sessions: + - Packet processing of incoming downlink packets for multicast and broadcast flows. + - QoS enforcement (MFBR) based on existing means. + - Interaction with MB-SMF for receiving multicast and broadcast data. + - Delivery of multicast and broadcast data to RAN nodes for 5GC Shared MBS traffic delivery method. +- Specific for Multicast MBS sessions: + - Delivery of multicast data to UPF for 5GC Individual MBS traffic delivery method. + +#### 5.3.2.5 UPF + +In addition to the functions defined in TS 23.501 [5], the UPF performs the following functions to support MBS: + +- Interacting with SMF for receiving multicast data from MB-UPF for 5GC Individual MBS traffic delivery method. +- Delivering multicast data to UEs via PDU Session for 5GC Individual MBS traffic delivery method. + +NOTE: UPF and MB-UPF may be co-located or deployed separately. + +#### 5.3.2.6 AMF + +In addition to the functions defined in TS 23.501 [5], the AMF performs the following functions to support MBS: + +- Signalling with NG-RAN and MB-SMF for MBS Session management. +- Selection of NG-RANs for notification of multicast session activation toward UEs in CM-IDLE state. +- Selection of NG-RANs for broadcast traffic distribution. + +Additionally, AMF being aware of NG-RAN 5G MBS capability. + +#### 5.3.2.7 NG-RAN + +In addition to the functions defined in TS 23.501 [5], the NG-RAN performs the following functions to support MBS: + +- Management of MBS QoS flows via N2. +- Delivery of MBS data packets for multiple UEs over radio using PTM or PTP. +- Configuration of UE for MBS QoS flow reception at AS layer. +- Control switching between PTM and PTP delivery per UE. +- Support for multicast session service continuity during Xn Handover and N2 Handover. +- Support group paging at multicast session activation over radio toward UEs in CM-IDLE state and CM-CONNECTED with RRC INACTIVE state. +- Reception of MBS data packets from 5GC via shared MBS traffic delivery. +- Support for efficient radio resource utilization for multiple broadcast MBS Sessions via multiple CNs to deliver the same broadcast content in the case of network sharing. +- If supported, determine to move UE(s) receiving multicast MBS data from RRC\_CONNECTED state to CM-CONNECTED with RRC INACTIVE state if the UE(s) are capable of receiving MBS data in RRC\_INACTIVE state. + +#### 5.3.2.8 UE + +In addition to the functions defined in TS 23.501 [5], the UE may perform the following functions to support MBS: + +- Reception of multicast data using PTM/PTP in RRC\_CONNECTED state. +- If supported, reception of multicast data using PTM in RRC\_INACTIVE state. +- Reception of broadcast data using PTM. +- Handling of incoming MBS QoS flows. +- Support of signalling for joining and leaving a Multicast MBS session. +- MBS resource management support at AS layer. +- Reception of notification in CM-IDLE state and CM-CONNECTED with RRC\_INACTIVE state for multicast data transmission. +- Support of the aforementioned functions for UE using power saving functions. + +NOTE : UE functionality for MBS security is provided in TS 33.501 [20]. + +#### 5.3.2.9 AF + +The AF performs the following functions to support MBS: + +- Requesting multicast or broadcast service from the 5GC by providing service information including QoS requirement to 5GC. +- Instructing MBS session operation towards 5GC if needed. + +- Interacting with NEF for MBS related service exposure. +- Interacting with NEF for group message delivery to the UE(s). + +#### 5.3.2.10 NEF + +In addition to the functions defined in TS 23.501 [5], the NEF performs the following functions to support MBS: + +- Providing an interface to AFs for MBS procedures including service provisioning, MBS session and QoS management. +- Interacting with AF and NFs in 5GC, e.g. MB-SMF for MBS session operations, determination of transport parameters. +- Selection of MB-SMF to serve an MBS Session. +- Support of provisioning the optional MBS Session Assistance Information related to the reception of multicast MBS data in RRC\_INACTIVE state. +- Interacting with AF and MBSF/MBSTF for group message delivery. + +#### 5.3.2.11 MBSF + +The MBSF performs the following functions to support MBS: + +- Service level functionality to support MBS, and interworking with LTE MBMS +- Interacting with AF and MB-SMF for MBS session operations, determination of transport parameters, and session transport. +- Selection of MB-SMF to serve an MBS Session. +- Controlling MBSTF if the MBSTF is used. +- Determination of destination IP multicast address for the MBS session if IP multicast address is sourced by MBSTF. + +NOTE 1: MBSF functionality related to service and MBS data handling (e.g. encoding) is specified in TS 26.502 [18]. + +NOTE 2: MBSF functionality for MBS security is provided in TS 33.501 [20]. + +#### 5.3.2.12 MBSTF + +The MBSTF performs the following functions to support MBS if deployed: + +- Media anchor for MBS data traffic if needed. +- Sourcing of IP Multicast if needed. +- Generic packet transport functionalities available to any IP multicast enabled application such as framing, multiple flows, packet FEC (encoding). +- Multicast/broadcast delivery of input files as objects or object flows. + +NOTE 1: MBSTF functionality related to MBS data handling (e.g. encoding) is specified in TS 26.502 [18]. + +NOTE 2: MBSTF functionality for MBS security is provided in TS 33.501 [20]. + +#### 5.3.2.13 UDM + +In addition to the functions defined in TS 23.501 [5], the UDM performs the following functions to support MBS: + +- Support management of subscription for authorization for multicast MBS sessions. + +- Support management of subscription MBS Assistance Information related to the reception of multicast MBS data in RRC\_INACTIVE state. + +#### 5.3.2.14 UDR + +In addition to the functions defined in TS 23.501 [5], the UDR performs the following functions to support MBS if deployed: + +- Support storage or retrieval of MBS subscription data by the UDM for UE authorization information for multicast MBS sessions and MBS Assistance Information. +- Support storage and retrieval of policy data by the PCF for Multicast or Broadcast MBS sessions. + +#### 5.3.2.15 NRF + +##### 5.3.2.15.1 General + +In addition to the functions defined in TS 23.501 [5], the NRF performs the following functions to support MBS: + +- Support of new NF types MB-SMF and MBSF and their corresponding NF profiles. +- For both multicast and broadcast MBS sessions, support of MB-SMF discovery based on parameters such as DNN, S-NSSAI and MBS service area, at MBS Session creation. +- For multicast MBS sessions, support of MB-SMF discovery based on MBS Session ID by SMF serving the multicast Session at UE join. + +NOTE: For broadcast MBS Session, AMF discovery by MB-SMF for an MBS service area is based on tracking area IDs related to that service area, as registered in the AMF profile according to TS 23.501 [5]. + +##### 5.3.2.15.2 Extensions to NF profile at NRF + +In addition to the NF profile contents defined in clause 6.2.6.2 of TS 23.501 [5], the NF profile in the NRF contains the following content: + +- For MB-SMF, the NF profile may include MB-SMF service area, MBS Session ID(s), Area Session ID(s) and corresponding MBS service area(s) if available. + +# --- 6 Functionalities and features + +## 6.1 Authorization to MBS service + +### 6.1.1 AF authorization to the service for multicast and broadcast + +The AF should be authorized by the 5GC for delivering MBS data to the 5GC and/or interacting with the 5GC. For signalling exchange with the 5GC, the NEF perform authorization to the external AF for determination of whether the interaction with the 5GC is allowed or not. + +### 6.1.2 UE authorization to the service for multicast + +The following authorizations are defined: + +- a) Whether the UE is authorized to use the Multicast service in the PLMN. +- b) The authorization for a UE of receiving the content of a specific multicast MBS session. + +A Multicast MBS session may be "open to any UEs". + +NOTE 1: UE authorization for a specific Multicast MBS session can be implicitly performed when UE is configured for a specific Multicast MBS session, e.g. via Service Announcement for public safety use case. + +NOTE 2: The authorization mentioned by a) is required even if an authorization according to b) is available. If the UE is not authorized to use the Multicast service by the PLMN, the UE is not authorized to join any multicast MBS Session even if the Multicast MBS session is "open to any UEs". + +For a Multicast MBS session, it is required that the 5GC authorizes the UE based on the MBS subscription data and whether the Multicast MBS session is "open to any UEs", which are preconfigured, or provided by the AF (see clause 7.2.9). + +The procedure for UE authorization is a part of UE join procedure and is described in clause 7.2.1.3. + +## 6.2 Local MBS service and Location dependent MBS service + +### 6.2.1 General + +A Local MBS service is an MBS service provided in one MBS service area. A location dependent MBS service is an MBS service provided in several MBS service area(s). An MBS service area is identified by a cell list or a tracking area list. The MBS service area could be geographical area information or civic address information, and NEF/MBSF translates the location information to Cell ID list or TAI list as MBS service area, see clause 7.1.1.2. + +The MBS service area may be updated by the AF for both multicast MBS sessions and broadcast MBS sessions as specified in clause 7.1.1.6. + +For more details, refer to clause 7.2.4 for multicast MBS session and refer to clause 7.3.4 for broadcast MBS session. + +### 6.2.2 Local MBS service + +For a local MBS service, only UEs within the MBS service area may receive content data, while UEs outside the MBS service area are not allowed to receive location specific content. For multicast MBS service, UEs outside the MBS service area are not allowed to join the MBS service, and the network shall not deliver location specific content anymore to the UEs moved out of the MBS service area. Depending on policy, for the multicast MBS service the network may remove UEs outside the MBS service area of the MBS session from the MBS Session Context after a grace period. The SMF may subscribe at the AMF to notifications about "UE moving in or out of a subscribed "Area Of Interest"" event. + +For multicast communication, local MBS may be supported via 5GC Individual MBS traffic delivery towards RAN nodes not supporting MBS. If the SMF obtains a notification that the UE is no longer in the MBS service area, the SMF terminates the 5GC Individual MBS traffic delivery towards the UE. + +The UE shall be able to obtain service area information of the local multicast service via MBS service announcement or via NAS signalling (UE Session Join Accept/Reject including Cell ID list or TAI list). If the UE Session Join procedure fails due to the UE being outside the MBS service area, the UE does not attempt to join the Multicast MBS session again until the UE moves inside the MBS service area. When the UE Session Join succeeds and if the Multicast MBS session is inactive, the UE does not perform monitoring the session activation notification and any other information related to the Multicast MBS session identified by an MBS Session ID over the radio if outside the MBS service area. + +NOTE 1: Broadcast communication service is the service provided simultaneously to all UEs in a geographical area, therefore for broadcast it is naturally a local MBS service. If the MBS Service Area consists of areas belonging to multiple MB-SMF Service Areas, the procedure for location dependent MBS Session can be used but the content is the same in all the MB-SMF service areas. + +NOTE 2: In this Release, deployments topologies with specific SMF Service Areas are not supported, as a result, local MBS service over multiple SMF Service Areas (corresponding to multiple MB-SMF Service Areas) using multicast communication is not supported. + +### 6.2.3 Location dependent MBS service + +A location dependent MBS is identified by MBS Session ID, and provided in several MBS service areas. The location dependent MBS service enables distribution of different content data to different MBS service areas. The same MBS Session ID is used but a different Area Session ID is used for each MBS service area. The Area Session ID is used, in combination with MBS Session ID, to uniquely identify the service area specific part of the content data of the MBS service within 5GS. The network supports the location dependent content distribution for the location dependent MBS services, while UEs are only aware of the MBS Session ID (i.e. UEs are not required to be aware of the Area Session IDs). When UE moves to a new MBS service area, content data from the new MBS service area shall be delivered to the UE, and the network ceases to deliver the content data from the old MBS service areas to the UE. For multicast MBS service, UEs outside all MBS service areas of the location dependent MBS session are not allowed to join the MBS service. When UE moves out of an MBS service area and there is no other MBS service area for the MBS session, the network ceases to deliver the content data to the UE. Depending on policy, for the multicast MBS service the network may remove UEs outside all MBS service areas of the location dependent MBS Session from the multicast MBS Session Context after a grace period The SMF may subscribe at the AMF to notifications about UE moving in or out of all MBS service areas of the location dependent MBS session. + +For multicast communication towards an NG-RAN supporting MBS, the NG-RAN node handles mobility of UEs within the MBS session between MBS service areas served by the same NG-RAN without interaction with SMF. + +For multicast communication, location dependent MBS services may be supported via 5GC Individual MBS traffic delivery towards RAN nodes not supporting MBS. If the SMF determines that the UE is in another MBS service area of the Multicast MBS session, the SMF configures the UPF to send multicast data relating to the new MBS service area towards the UE. + +Information about different MBS service areas for a location dependent MBS service may be provided by one or several AFs or may be configured. The MBS Service Information provided is specified in clause 6.14. Different ingress points for location dependent points for the MBS session are supported for different MBS service area dependent content of the MBS session; different MB-UPF may be assigned for different MBS service areas within the same MB-SMF Service Area for an MBS session. + +For broadcast communication, if MBS service areas covering different MB-SMF Service Areas are required, different MB-SMFs should be assigned for different MB-SMF service areas for an MBS session, and in this case the MB-SMF involved in the MBS Session should be able to accept TMGI value allocated by other MB-SMF(s). + +The Area Session ID is allocated by MB-SMF in MBS Session creation procedure. MB-SMF allocates Area Session ID for each MBS services area which is unique within the MBS session. MB-SMF needs to further ensure there is no MBS service area overlapping with other MBS service areas that share the same MBS Session ID. + +The same QoS applies to all MBS service areas of a location dependent MBS Session. + +NOTE 1: In this Release, deployments topologies with specific SMF Service Areas are not supported, as a result, location dependent service using multicast communication is not supported when a UE moves outside its SMF service area. + +NOTE 2: For location dependent service provided in different MBS service areas within the same SMF service area, it is assumed that one MB-SMF is used for an MBS Session. + +NOTE 3: An example of Location dependent MBS is a nationwide weather forecast service with local weather reports. + +NOTE 4: Area Session ID is equivalent to Flow ID as specified in TS 23.246 [8]. + +### 6.2.4 Void + +### 6.2.5 Void + +## 6.3 Mobility support of MBS service + +### 6.3.1 Mobility of Multicast MBS session + +The mobility of multicast MBS service is supported when: + +- The UE moves from a NG-RAN node that supports MBS to a target NG-RAN node that supports MBS; or +- The UE moves from a NG-RAN node that supports MBS to a target NG-RAN node that does not support MBS and vice versa. + +During the mobility from a NG-RAN node that supports MBS to a target NG-RAN node that supports MBS, or between a NG-RAN node that supports MBS and a target NG-RAN node that does not support MBS, minimization of data loss should be supported, see clause 7.2.3.5 for details. + +To support Handover from NG-RAN node that supports MBS to a target NG-RAN node that supports MBS: + +- If the shared delivery for the MBS session has not been established towards target NG-RAN, the target NG-RAN establishes the shared delivery for the MBS Session with MB-SMF and MB-UPF. + +To support Handover from NG-RAN node that supports MBS to a target NG-RAN node that does not support MBS: + +- mapping information about unicast QoS flows for multicast data transmission and the information of associated multicast QoS flows are provided to the NG-RAN node. This is already performed during the PDU session modification procedure for the PDU session associated with the MBS session when the UE joins the MBS Session; +- during the handover procedure, the delivery method is switched from 5GC Shared MBS traffic delivery method to 5GC Individual MBS traffic delivery method, i.e. the N3 tunnel of the PDU Session for 5GC Individual MBS traffic delivery needs to be established towards the target NG-RAN node. The SMF realizes that the target NG-RAN node does not support MBS. +- the SMF and the MB-SMF shall activate the GTP tunnel between the UPF and the MB-UPF for 5GC Individual MBS traffic delivery method, if needed. + +To support Handover from a NG-RAN node that does not support MBS to a target NG-RAN node that supports MBS: + +- The PDU sessions, including the one associated with the MBS session and used for 5GC Individual MBS traffic delivery, are handed over to the target NG-RAN node. +- SMF triggers mode switch, i.e. from 5GC Individual MBS traffic delivery method to 5GC shared MBS traffic delivery method. +- When the MBS Session Context is given to the target NG-RAN node by the SMF, if the shared delivery for the MBS session has not been established towards target NG-RAN, the target NG-RAN establishes the shared delivery for the MBS Session with MB-SMF and MB-UPF. +- The 5GC terminates the 5GC Individual MBS traffic delivery and changes to the 5GC shared MBS traffic delivery. + +### 6.3.2 Mobility of Broadcast MBS session + +The UE receives the same Broadcast MBS service in the target NG-RAN if the same MBS session is established with 5GC Shared MBS traffic delivery method in the target NG-RAN node. + +NOTE: When the UE moves into NG-RAN node not supporting MBS within the Broadcast MBS service area, how the UE get the same content via application level is out scope of this specification. + +## 6.4 Subscription to multicast services + +### 6.4.1 General + +The UDM stores the MBS subscription information. The MBS subscription data for a UE is included within the UE subscription data. + +At any time, the operator may change the subscription for multicast services in the UDM. + +The MBS subscription data in UE subscription data contains the following information: + +- MBS authorization information that gives the user permission to use multicast services + - Whether the UE is authorized to use the multicast MBS service. + - Optionally, MBS Session ID(s) of the Multicast MBS session(s) that the UE is allowed to join. + +NOTE: The MBS Session ID applies only for MBS session which is not "open to any UEs". + +- Optionally, MBS assistance information indicating that a UE is preferred to be kept connected when the related MBS Session the UE joined is active, which contains the following information: + - MBS Session ID(s). + +The MBS subscription data is provided by the UDM to the SMF during or after the establishment procedure of PDU Session associated with Multicast MBS session(s) using Nudm\_SDM service for subscription data type "MBS subscription data" as defined in clause 7.2.1.2. + +During multicast session join procedure, the SMF retrieves MBS Session information from the MB-SMF, and authorizes the MBS Session join request for the UE based on MBS subscription data of the UE received from UDM and the Any UE indication (i.e. whether the Multicast MBS session is "open to any UEs") received from MB-SMF as described in clause 7.2.1.3. + +The UDR stores the MBS data, which may be updated by the UDM or the AF/NEF as specified in clause 4.15.6.2 of TS 23.502 [6], i.e. AF may provision Multicast MBS Session Authorization information for the MBS as described in clause 7.2.9. + +### 6.4.2 MBS subscription data in UDM + +The information stored in the UDM as defined in clause 5.2.3.3.1 of TS 23.502 [6] is extended as follows: + +- MBS subscription data for a UE as part of UE subscription data, as defined in Table 6.4.2-1, with keys defined in Table 6.4.2-2. + +**Table 6.4.2-1: MBS subscription data type** + +| Subscription data type | Field | Description | +|------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBS subscription data | MBS allowed | Indicates whether the UE is authorized to use the multicast MBS service. | +| | Allowed MBS Session ID(s) | Identifies the MBS Session(s) that the UE are allowed to join. | +| | MBS assistance information | Indicates that the UE is preferred to be kept connected when the related MBS session the UE joined is active, which contains the related MBS Session ID(s) | + +**Table 6.4.2-2: MBS subscription data type keys** + +| Subscription Data Types | Data Key | Data Sub Key | +|-------------------------|----------|--------------| +| MBS Subscription data | SUPI | - | + +### 6.4.3 MBS information in UDR + +The MBS information may be stored in the UDR by the UDM as part of the subscription data, as defined in clause 5.2.12.2.1 of TS 23.502 [6]. + +1. MBS data as defined in Tables 6.4.2-1, with keys defined in Table 6.4.3-1. + +**Table 6.4.3-1: MBS data type keys** + +| Data Set | Data Subset | Data Key | Data Sub Key | +|-------------------|-----------------------|----------|--------------| +| Subscription Data | MBS subscription data | SUPI | - | + +## 6.5 Identifiers + +### 6.5.1 MBS Session ID + +The MBS session ID is used to identify a Multicast/Broadcast MBS Session by the 5G system on external interface towards AF and between AF and UE, and towards the UE. + +MBS Session ID may have the following types: + +- TMGI (for broadcast and multicast MBS sessions); +- source specific IP multicast address (for multicast MBS sessions). + +If a multicast MBS session is provided within an SNPN, the multicast MBS session can still be identified by a (globally unique) source specific IP multicast address or TMGI. In 5GS internal signalling the PLMN ID, included in TMGI, is complemented with the NID to identify an SNPN. + +Source specific IP multicast address or TMGI may be used as MBS Session ID in NAS messages exchange between a UE and a CN when the UE requests to join/leave a Multicast MBS session. For multicast MBS sessions that the UE joined with a source specific IP multicast address, a TMGI is also allocated by 5GC and is sent to the UE and used in other signalling messages between RAN, CN and UE. Details see clause 7.2.1.3. + +The UE shall be able to obtain at least one MBS Session ID via MBS service announcement. + +For multicast MBS sessions, a source specific IP multicast address can be assigned by external AFs. + +### 6.5.2 Temporary Mobile Group Identity + +TMGI (Temporary Mobile Group Identity) is defined in TS 23.003 [12] and is used to be able to identify a broadcast MBS Session or a multicast MBS session. + +In SNPN (Stand-alone Non-Public Network), TMGI is used together with NID (Network Identifier) defined in TS 23.003 [12] to identify an MBS Session. + +### 6.5.3 Source Specific IP Multicast Address + +The source specific IP multicast address is used to identify an Multicast MBS session and consists of two IP addresses, one is an IP unicast address used as source address in IP packets for identifying the source of the multicast service (e.g. AF/AS), the other is an IP multicast address used as destination address in related IP packets for identifying a multicast communication service associated with the source. + +### 6.5.4 MBS Frequency Selection Area ID + +The MBS Frequency Selection Area (FSA) ID is used for broadcast MBS session to guide the frequency selection of the UE. + +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 (details see TS 38.300 [9]). MBS FSA ID and their mapping to frequencies are provided to RAN nodes via OAM. + +Based on this configuration, RAN nodes announce in SIBs over the radio interface information about the MBS FSA IDs and frequencies. + +When a broadcast MBS session is created, the AF may provide MBS FSA ID(s) based on the business agreement. If the AF does not provide MBS FSA ID(s), the MB-SMF determines MBS FSA ID(s) based on configured mapping from MBS service area and/or broadcast MBS session information (e.g. application ID) to MBS FSA ID(s) and sends the determined MBS FSA ID(s), to the AF (optionally via NEF). + +NOTE: The same MBS FSA ID(s) can be assigned to multiple Broadcast MBS sessions. + +The MBS FSA ID(s) of a broadcast MBS session are communicated in the service announcement towards the UE. The UE compares those MBS FSA IDs(s) with the MBS FSA ID(s) in SIBs for frequency selection. + +During MBS Session Start for Broadcast in clause 7.3.1 and MBS Session Update for Broadcast in clause 7.3.3, the MB-SMF may include the MBS FSA ID(s) for the MBS session and send them to the NG-RAN nodes via the AMF. The NG-RAN nodes may then use those MBS FSA ID(s) to determine cells/frequencies within the MBS service area to broadcast MBS session data. For details, see TS 38.300 [9] and TS 38.413 [15]. + +### 6.5.5 Associated Session ID + +In the case of network sharing, an Associated Session ID may be used as specified in clause 6.18. When the AF creates multiple broadcast MBS Sessions via different CNs to deliver the same content, it may provide the Associated Session ID which enables the NG-RAN to identify the multiple MBS Sessions delivering the same content. + +Source Specific IP Multicast Address specified in clause 6.5.3 may be used as Associated Session ID. + +## 6.6 QoS Handling for Multicast and Broadcast services + +For MBS services, the network shall support QoS control per MBS session. + +The 5G QoS model and parameters as defined in TS 23.501 [5] clause 5.7 also apply to multicast/broadcast communication services with the following differences: + +- Reflective QoS is not applicable; +- Wireline access network specific 5G QoS parameters do not apply to MBS services; +- Alternative QoS Profile is not applicable; +- QoS Notification Control is not applicable; +- UE-AMBR is not applicable; + +NOTE 1: For multicast communication service, the UE-AMBR applies for associated PDU Session. + +- Session-AMBR if provided is enforced at MB-UPF but not communicated to NG-RAN. + +NOTE 2: Whether Session-AMBR is required in addition to the MBS service data flow bit rate is determined by operator policy and/or agreement with the service provider. + +- For broadcast MBS session, the QoS rule and QoS Flow level QoS parameters are not provided to UE. + +NOTE 3: For broadcast MBS session, the associated QoS Flow(s) are not applicable. + +- For multicast MBS sessions, the QoS rule and QoS Flow level QoS parameters of MBS QoS Flow are not provided to UE. +- For multicast MBS sessions, the handling of QoS rule and QoS Flow level QoS parameters of the associated QoS Flow(s) is the same as for other QoS Flow without UL in a PDU Session. + +NOTE 4: The UE does not need to know a QoS Flow within the PDU session is mapped from MBS QoS Flow. + +The network shall support one or multiple QoS flows, which can be either GBR or non-GBR, for an MBS session. + +If 5GC Individual MBS traffic delivery method is used to deliver multicast data packets, the network may use dedicated QoS Flows for multicast data packets in a PDU session. For the associated QoS Flow in the PDU session, the SMF uses the same QoS parameters (e.g. 5QI) provided by MB-SMF. These dedicated QoS Flows shall be kept separate from QoS Flows unrelated to multicast even if the same 5QI and other QoS parameters are assigned. + +NOTE 5: When there is a need to apply 5GC Individual MBS traffic delivery, the Session-AMBR of the associated PDU Session can be configured with a sufficiently high value to cater for MBS Session-AMBR. + +The MB-SMF may obtain QoS information for multicast and broadcast MBS session in different ways depending on the deployment and use cases. + +If dynamic PCC is not deployed: + +- When an MBS session is started, the MB-SMF is provided with service requirements including QoS information. If MBSF is not used, the service requirement is provided to the MB-SMF by the AF (directly or via the NEF). If the MBSF is used, the MBSF receives request from the AF (or via the NEF) and decides the related QoS requirements (e.g. considering support for FEC) and provides them to the MB-SMF. The MB-SMF determines the QoS profiles and QoS for N4 rules for the MBS session with QoS parameters of the MBS QoS flows, and provides related information to the RAN and the MB-UPF respectively. + +NOTE 6: What information is included in the request from AF to MBSF requires collaboration with SA WG4. + +If dynamic PCC is deployed: + +- It is the PCF that generates policy rules for MBS Session based on the received service requirement and provides the policy rules to the MB-SMF. The MB-SMF, based on the policy rules from the PCF, determines to create, and/or modify MBS QoS Flow(s) including providing QoS information to NG-RAN and MB-UPF, and providing packet detection and forwarding information to MB-UPF. + +## 6.7 User plane management + +The MB-UPF acts as the MBS Session Anchor of an MBS session, and if the MBSTF is involved in the MBS session, then the MBSTF acts as the media anchor of the MBS traffic. The MB-UPF receives only one copy of MBS data packets from AF or MBSTF. + +The user plane between MB-UPF and AF, may use either multicast transport or a unicast tunnel for the MBS session (depending on application and capabilities of control interface). If the transport network does not support multicast transport, the user plane uses a unicast tunnel for the MBS Session. The user plane between MBSTF and AF may use a unicast tunnel, multicast transport or other means (e.g. HTTP download from external CDN). The user plane between MBSTF and MB-UPF uses a unicast tunnel for the MBS session. If a unicast tunnel is used for the MBS Session between MB-UPF and AF or MBSTF, after receiving the downlink MBS data, the MB-UPF forwards the downlink MBS data without the received outer IP header and tunnel header information. + +NOTE 1: For location dependent MBS Session, the user plane towards the MB-UPF can only use unicast tunnel and content to be delivered to different areas are sent to MB-UPF via different tunnels. + +NOTE 2: If the user plane towards the MB-UPF uses a unicast tunnel, all the service data flows for the MBS Session or for an Area Session for a location-dependent MBS session are sent in the same tunnel. + +The user plane from the MB-UPF to NG-RAN(s) (for 5GC Shared MBS traffic delivery) and the user plane from the MB-UPF to UPFs (for 5GC Individual MBS traffic delivery) may use multicast transport via a common GTP-U tunnel per MBS session, or use unicast transport via separate GTP-U tunnels at NG-RAN or at UPF per MBS session in the following way + +- For 5GC Shared MBS traffic delivery (i.e. MB-UPF delivers user plane data to NG-RAN supporting MBS), if the transport network supports IP multicast, the NG-RAN node uses multicast transport via a common GTP-U tunnel per MBS session, otherwise unicast transport via separate GTP-U tunnel per MBS session per NG-RAN node is used. +- For 5GC Individual MBS traffic delivery (i.e. MB-UPF delivers user plane data to UPF), if the transport network supports IP multicast and the UPF supports reception of multicast data over N19mb, UPF use multicast transport + +via a common GTP-U tunnel per MBS session, otherwise unicast transport via separate GTP-U tunnel per MBS session per UPF is used. + +If the user plane uses unicast transport, the transport layer destination is the IP address of the NG-RAN or UPF, each NG-RAN or UPF allocates the tunnel separately and multiple GTP-U tunnels are used for the MBS Session. If the user plane uses multicast transport, a common GTP-U tunnel is used for both RAN and UPF nodes. The GTP-U tunnel is identified by a common tunnel ID and an IP multicast address as the transport layer destination, both assigned by 5GC. + +The above is depicted in Figure 6.7-1. There could be more than one NG-RANs or UPFs that are involved in the MBS traffic delivery. + +![Figure 6.7-1: Schematic showing user plane data transmission. The diagram illustrates two delivery paths for MBS traffic. The top path shows '5GC Shared MBS traffic delivery' where 'Incoming MBS traffic' enters the 'MB-UPF' and is transmitted via 'N3mb transmission' to 'NG-RAN 1'. 'NG-RAN 1' then delivers the traffic to 'UE 1' and 'UE 2' using 'PTP (only for multicast) or PTM over radio'. The bottom path shows '5GC Individual MBS traffic delivery' where the 'MB-UPF' transmits traffic via 'N19mb transmission' to a 'UPF'. The 'UPF' then replicates the traffic to 'NG-RAN 2' and 'NG-RAN 3'. 'NG-RAN 2' delivers it to 'UE 3' via 'PDU Session A of UE 3', and 'NG-RAN 3' delivers it to 'UE 4' via 'PDU Session B of UE 4'.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +Figure 6.7-1: Schematic showing user plane data transmission. The diagram illustrates two delivery paths for MBS traffic. The top path shows '5GC Shared MBS traffic delivery' where 'Incoming MBS traffic' enters the 'MB-UPF' and is transmitted via 'N3mb transmission' to 'NG-RAN 1'. 'NG-RAN 1' then delivers the traffic to 'UE 1' and 'UE 2' using 'PTP (only for multicast) or PTM over radio'. The bottom path shows '5GC Individual MBS traffic delivery' where the 'MB-UPF' transmits traffic via 'N19mb transmission' to a 'UPF'. The 'UPF' then replicates the traffic to 'NG-RAN 2' and 'NG-RAN 3'. 'NG-RAN 2' delivers it to 'UE 3' via 'PDU Session A of UE 3', and 'NG-RAN 3' delivers it to 'UE 4' via 'PDU Session B of UE 4'. + +**Figure 6.7-1: Schematic showing user plane data transmission** + +The MB-SMF instructs the MB-UPF to receive packets related to an MBS session. + +MB-UPF transmits the MBS data with the sequence number for each MBS QoS Flow as defined in TS 29.281 [23]. + +For shared delivery, if unicast transport over N3mb applies, the MB-SMF instructs MB-UPF to replicate the received MBS packets and forward them towards multiple RAN nodes via separate GTP tunnel. For shared delivery, if multicast transport over N3mb applies, the MB-SMF instructs the MB-UPF to replicate the received MBS data and forwards the data via a single GTP tunnel. + +For individual delivery, the MBS data received by the MB-UPF is replicated towards the UPF(s) where individual delivery is performed in the following way: + +- The MB-SMF configures the MB-UPF to receive packets related to an MBS session, to replicate those packets and forward them towards multiple UPFs via GTP tunnels if unicast transport over N19mb is applied, or via a single GTP tunnel if multicast transport over N19mb is applied. +- The SMF(s) instructs the UPF to receive packets related to a Multicast MBS session from an MB-UPF over N19mb, to replicate those packets and to forward them in multiple PDU sessions. + +For the MB-SMF and MB-UPF, packet detection, replication and forwarding for an MBS session is realized by using for each MBS session one PDR that detects the incoming MBS packets and points to one FAR that describes the forwarding of the data towards multiple destinations (UPFs or RAN nodes): + +- A PFCP session is created when the MBS Session is started, regardless of multicast or unicast transport over N3mb and N19mb. +- For Multicast transport over N3mb and N19mb, the destination in the FAR contains the MB-UPF IP Multicast Distribution Info. + +- For unicast transport over N3mb and N19mb, the FAR in the PFCP session may contain multiple destinations represented by the NG-RAN N3mb Tunnel Info and UPF N19mb Tunnel Info (if applicable). + +For the SMF and the UPF (for 5GC individual delivery), packet detection, replication and forwarding for an MBS session is realized by PDR and FAR of the PDU session in which the UE has joined the MBS session: + +- The SMF instructs the UPF to associate the PFCP session of the PDU session with an MBS session. +- A new PDR with Source Interface "Core" is used to detect MBS data from N19mb. + +NOTE 3: This PDR is also containing the MBS Session ID to enable a single detection of the incoming MBS data for multiple PDU sessions at the UPF. + +- For unicast transport over N19mb, the SMF requests UPF to allocate N19mb Tunnel Info if not allocated. +- For multicast transport over N19mb, the SMF includes the low layer source specific multicast address information and C-TEID to UPF. +- If the SMF wants to maintain the MBS data reception over N19mb but suspends the delivery of the data to the UE's PDU session, the Action of FAR set to "drop" (e.g. when the UE is switching from 5GC Individual delivery to 5GC Shared delivery due to the UE moving from MBS non-supporting NG-RAN to MBS supporting NG-RAN). Otherwise the SMF remove the related PDR and FAR. + +See TS 29.244 [17] for the details of user plane handling. + +## 6.8 Interworking with MBMS over E-UTRAN for public safety services + +In order to minimize the interruption of services, upon mobility for MBS service from NR/5GC to E-UTRAN/EPC and vice versa, the following applies: + +- If the same MBS service is provided via eMBMS in E-UTRAN and MBS, interworking is supported at service layer. + - The UE is always configured with a common TMGI regardless of whether the UE is discovering the MBMS/MBS service via E-UTRAN or NR, for both multicast and broadcast MBS services. + - When the UE camps on NR and uses a multicast MBS service, the UE joins a multicast MBS session and uses procedures as defined in clause 7.2 for MBS reception for the TMGI. When the UE camps on E-UTRAN, the UE uses procedures as defined in TS 23.246 [8] for MBMS reception for the TMGI. + - The session context for multicast MBS service transferring is not handed over to E-UTRAN during mobility from 5GS to EPS. + +## 6.9 MBS Session Context + +### 6.9.1 MBS Session Context + +The MBS Session Context contains all information describing a particular MBS session in the 5GS and is created in each node involved in the delivery of the MBS data. + +The content of the Multicast MBS Session Context is described in Table 6.9.1-1. + +Table 6.9.1-1: Multicast MBS Session Context + +| Parameter | Description | NG-RAN | AMF | SMF | MB-SMF | +|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----|---------------|-----------------------| +| State | State of MBS session ('Active' or 'Inactive' or 'Configured') | X
(note 2) | | X
(note 2) | X | +| SSM (source specific IP multicast address) | IP multicast address identifying the MBS session. | | | X
(note 1) | X
(note 1) | +| TMGI | Temporary Mobile Group Identity allocated to the MBS Session. | X | X | x | X | +| Area Session Identifier | Used for MBS session with location dependent content. When present, the Area Session Identifier together with the TMGI uniquely identify the MBS Session in a specific MBS service area. | X
(note 1) | X | X
(note 1) | X
(note 1) | +| MB-SMF | The MB-SMF that handles the MBS session. | | X | X | | +| QoS information | QoS information of the MBS session. | X | | X | X | +| MBS Service Area | Area over which the MBS session data is distributed (i.e. Cell ID list or TAI list). | X
(note 1) | | X
(note 1) | X
(note 1) | +| NG-RAN Node ID(s) | NG-RAN nodes which are involved in the Multicast MBS session | | X | | X
(note 1, note 4) | +| AMF | The AMF(s) which are selected for the MBS session | X | | | X | +| IP multicast and source address for data distribution | IP addresses identifying the SSM user plane transport for shared delivery from MB-UPF to NG-RAN and for individual delivery from MB-UPF to UPF when the IP multicast transport is used. | X (note 1) | | X
(note 1) | X
(note 1) | +| TEID for IP multicast distribution | Tunnel ID allocated by MB-UPF used for receiving the multicast data for shared delivery by NG-RAN and for individual delivery by UPF when the IP multicast transport is used. | X | | X | X
(note 1) | +| SMF | The SMF(s) that manages the associated PDU session. | | | | X | +| UE ID | ID identifying the UE that successfully join the Multicast MBS session. For NG-RAN it is NGAP UE ID and for SMF it is SUPI. | X
(note 3) | | X
(note 3) | | +| NG-RAN IP unicast distribution | The IP addresses and TEID of NG-RAN used for the user plane between NG-RAN and MB-UPF and between MB-UPF and UPF when Point to Point tunnel is used. | X (note 1) | | X
(note 1) | X
(note 1, note 4) | +| PCF | The MB-PCF that provides policy control for the MBS session. | | | | X (note 1) | + +NOTE 1: It is an optional parameter. + +NOTE 2: The value 'Configured' is not applicable for NG-RAN and SMF. + +NOTE 3: the UE ID is available within the UE Context which contains the MBS information. + +NOTE 4: The Parameter needs to be stored in deployments with shared NG-U termination(s) if unicast transport is used. + +In Broadcast MBS session, an MBS Session Context is created in the NG-RAN, AMF, MB-SMF and MBSF as a result of the MBS Session Start procedure. + +The content of the Broadcast MBS Session Context is described in Table 6.9.1-2. + +Table 6.9.1-2: Broadcast MBS Session context + +| Parameter | Description | NG-RAN | AMF | MB-SMF | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-----------------------| +| TMGI | Temporary Mobile Group Identity allocated to the MBS Session. | X | X | X | +| Area Session Identifier | Used for MBS session with location dependent content. When present, the Area Session Identifier together with the TMGI uniquely identify the MBS Session in a specific MBS service area. | X
(note 1) | X
(note 1) | X
(note 1) | +| AMF | The AMF(s) which are selected for the MBS session | X | | X | +| MB-SMF | The MB-SMF that handles the MBS session. | | X | | +| QoS information | QoS information for the MBS Session, including the QoS parameters of QoS flows. | X | | X | +| MBS Service Area | Area over which the MBS session data is distributed (i.e. Cell ID list or TAI list). | X | X | X | +| NG-RAN Node ID(s) | NG-RAN nodes which are selected for the Broadcast MBS session | | X | X
(note 1, note 2) | +| IP multicast address for data distribution | IP addresses identifying the SSM user plane transport used for shared delivery from MB-UPF to NG-RAN when the IP multicast transport is used. | X
(note 1) | | X
(note 1) | +| TEID for IP multicast distribution | Tunnel ID allocated by MB-UPF used for receiving the broadcast data for shared delivery by NG-RAN when the IP multicast transport is used. | X | | X
(note 1) | +| NG-RAN IP unicast distribution | IP address and TEID of NG-RAN used for the user plane from NG-RAN to MB-UPF when Point to Point tunnel is used. | X
(note 1) | | X
(note 1, note 2) | +| PCF | The PCF that provides policy control for the MBS session. | | | X
(note 1) | +| MBS FSA ID | MBS Frequency Selection Area (FSA) ID is used for broadcast MBS sessions to guide the frequency selection of the UE. | X | | X | +| Associated Session ID | Associated Session ID is used by NG-RAN in network sharing to identify MBS sessions via different CNs transmitting the same content. | X
(note 1) | | X
(note 1) | + +NOTE 1: It is an optional parameter. +NOTE 2: The Parameter needs to be stored in deployments with shared NG-U termination(s) if unicast transport is used. + +## 6.10 Policy control for Multicast and Broadcast services + +### 6.10.1 General + +The policy and charging control framework as defined in TS 23.503 [7] applies to Multicast and Broadcast services in the following aspects: + +- MBS Session binding: MBS Session binding is the association of an AF Session information to one and only one MBS Session or a location dependent MBS Session in an MBS Service Area. The PCF shall perform the session binding based on the MBS Session ID, i.e. TMGI or source specific IP multicast address. For location dependent MBS Session, Area Session Policy ID is used together with MBS Session ID to associate the AF Session information with the location dependent MBS Session in a specific MBS service area. +- QoS Flow binding: For an MBS Session, QoS Flow binding is the association of a PCC rule to a QoS Flow within an MBS Session. The MB-SMF performs QoS Flow binding for an MBS Session in the same way as the SMF for a PDU Session. +- The PCF should provision the same MBS policy information for all MBS service areas of a location dependent MBS Session. + +- MBS policy information consists of: + - PCC rules for MBS Session are used to provide policy for QoS flows: The following PCC rule parameters defined in Table 6.3.1 of TS 23.503 [7] are applicable for MBS: + - Rule identifier. + - Service data flow detection: Precedence, Service data flow template (only for IP PDU traffic). +- NOTE: If a unicast tunnel is used over the N6mb/Nmb9 interface to transport MBS data towards the MB-UPF (see Figure 8.2-1), the Service data flow template relates to the inner IP layer within the unicast tunnel. +- Policy Control: 5G QoS Identifier (5QI), DL-maximum bitrate, DL-guaranteed bitrate, ARP, Priority Level, Averaging Window, Maximum Data Burst Volume. + - Policy information can also be applicable for an entire MBS session. The following parameters defined for a PDU session in Table 6.4.1 of TS 23.503 [7] are applicable for an entire MBS session: + - Authorized Session-AMBR. + - Explicitly signalled QoS Characteristics. + - Policy Control Request Triggers for MBS Session are used to define the conditions when the MB-SMF shall interact again with the PCF to request an update of the policy information for the MBS session by providing information on the condition(s) that have been met. The following Policy Control Request Triggers are defined for MBS: + - MBS Session Update. + +### 6.10.2 MBS Session policy control data in UDR + +The policy control profile information may optionally be provided by the UDR at MBS Session establishment, using Nudr service for Data Set "Policy Data" and Data Subset "MBS Session policy control data", with the source specific multicast address used as MBS session ID or with AF Application identifier as data key is described in Table 6.10.2-1. + +**Table 6.10.2-1: MBS Session policy control information** + +| Information element name | Description | Category | +|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|----------| +| 5QI(s) | Allowed 5QI(s) for a PCC rule of an MBS session (NOTE 1) | Optional | +| ARP | Highest ARP for any PCC rule of an MBS session (NOTE 1) | Optional | +| Session-AMBR | Maximum Session-AMBR for all nonGBR QoS Flows of an MBS session (NOTE 1) | Optional | +| GBR | Maximum aggregated bitrate that can be provided across all GBR QoS Flows for an MBS session (NOTE 1) | Optional | +| NOTE 1: This information element may be used to decide whether to authorize received MBS Service Information. | | | + +## 6.11 Service Announcement + +Service Announcement provides the UE with descriptions specifying the multicast or broadcast services to be delivered as part of MBS Session. + +The Service Announcement may be encoded as defined in TS 26.517 [22] or use application specific formats outside the scope of 3GPP. + +Service Announcement information may be delivered to the UE via application specific means or as defined in TS 26.502 [18], using one of the following methods: + +- Pre-configured at UE side; +- Via an MBS Session; or +- Via a regular PDU Session. + +NOTE 1: Pre-configured service announcement is specified in TS 24.575 [26]. + +The Service Announcement includes the MBS Session ID(s), which is represented by TMGI or a Source Specific IP Multicast Address, for the service. When the MBS Session ID is Source Specific IP Multicast Address, the Service Announcement may include the PLMN ID of the PLMN and NID for an SNPN in which the service is delivered. + +The Service Announcement includes an MBS Service Type, which indicates whether the MBS Session for the service is multicast or broadcast. + +NOTE 2: A Source Specific IP Multicast Address as MBS Session ID indicates a Multicast MBS session. + +For local MBS service, the Service Announcement may include the MBS service area. The MBS service area used by AF can be Cell ID list, TAI list, geographical area information or civic address information. Amongst them, Cell ID list and TAI list shall only be used by AFs who reside in trust domain, and when the AFs are aware of such information. + +The service announcement may contain a start time and/or a sequence of scheduled activation times (e.g. a first time and a periodicity) of the MBS session when the AF may activate the MBS session (for multicast only) and transmit MBS data as described in clause 6.16. When the AF decides that the start time and/or scheduled activation times for the MBS session need to be updated and the UE is unreachable (e.g. due to power saving function), the AF can send service announcement containing the updated time information to the UE at the old start time (if earlier than the new start time) or next scheduled activation time previously provided to the UE for the MBS session via multicast or broadcast. + +NOTE 3: The scheduled activation times are intended to assist UEs using power saving mechanisms and apply both for broadcast and multicast MBS. + +NOTE 4: For UEs using power saving function, if the service announcement is provided via unicast PDU Session, the application server can be aware of the UE's reachability by subscribing to the corresponding event defined in clause 4.15.3.1 of TS 23.502 [6]. + +If the MBS Session is for multicast, the Service Announcement may include the DNN and S-NSSAI of the PDU Session to indicate which PDU Session is associated with the MBS Session. + +NOTE 5: For multicast, AF or MBSF provides Service Announcement to the UE only after the MBS information is available to 5GC, to avoid potential rejection sent by SMF of the MBS session join request. + +NOTE 6: The MBS Service related information, e.g. serving PLMN ID, DNN and S-NSSAI can be pre-configured in the UE. + +NOTE 7: If DNN and S-NSSAI information is not provided in the service announcement or pre-configured, how UE determines the PDU session to join the MBS Session is implementation specific. + +If the MBS Session is for broadcast, the Service Announcement may include the MBS FSA ID(s) and optional frequency information associated with the broadcast MBS session. + +The Service Announcement may be provided to a UE by AF or MBSF, or may be retrieved by the UE from those entities. + +NOTE 8: How the UE can get the Service Announcement from other entities is not specified. + +NOTE 9: Service announcement can comply with TS 26.502 [18] and TS 23.289 [21] or follow an application specific format. + +NOTE 10: For supporting MBS security function, information included in Service Announcement is defined in TS 26.502 [18]. + +## 6.12 Paging strategy handling + +Compared to the paging strategy handling specified in clause 5.4.3 of TS 23.501 [5], the following additional functionality for multicast MBS service applies: + +- At multicast MBS Session Activation, the SMF may provide the most demanding ARP and 5QI of all MBS QoS Flow within the MBS session to the AMF. +- The AMF may take the received ARP and 5QI into consideration in paging differentiation. + +## 6.13 MBS Security function + +Security function may be used to protect MBS related signalling/data. Detailed descriptions of security requirements, procedures and handling for 5G Multicast/Broadcast Service (MBS) are provided in TS 33.501 [20]. + +MBS security function is implemented in the MBSF/MBSTF so that it can be applied only when MBSF/MBSTF are used (i.e. Configuration option 2 and 3). For configuration option 1 how to support MBS security is out of scope of this specification. + +The following additions to the MBS procedures for multicast Session in the present specification apply if the functionalities of MBS security for control plane procedure for multicast as defined in TS 33.501 [20] is used: + +- The multicast session security context, as defined in TS 33.501 [20], is used to protect MBS traffic of an MBS session. During the session establishment and when a UE joins, the multicast session security context contains MSK and MTK. +- The UEs in the MBS session use the received multicast session security context to process the protected MBS traffic. +- MBSF distributes the multicast session security context to the MB-SMF via the Nmbsmf\_MBSSession\_Create Request or Nmbsmf\_MBSSession\_Update Request message. +- The SMF interacts with the MB-SMF to obtain the multicast session security context. The MB-SMF provides the security context in the Nmbsmf\_MBSSession\_ContextStatusSubscribe response message and in the Nmbsmf\_MBSSession\_ContextStatusNotify request message. +- If the UE is authorized to join the Multicast MBS session, the SMF shall provide the multicast session security context to the UE in N1 SM container if it received the multicast session security context from the MB-SMF. +- When the MSK needs to be updated, MBSF shall send the updated multicast session security context to the MB-SMF, and then the MB-SMF shall trigger the session update as specified in clause 7.2.6 to provide the updated multicast session security context to the UEs in the related MBS session. The updated multicast session security context shall contain an updated MSK and may contain an updated MTK in addition. + +NOTE 1: If no MSK but only the MTK is to be updated, the session update described in the previous bullet is not triggered and the MTK is updated as defined in TS 33.501 [20]. + +NOTE 2: Interaction between MBSF and MBSTF will be defined in TS 33.501 [20] and TS 26.502 [18]. + +NOTE 3: The additions to the user plane procedure to support the security function for multicast and broadcast can be used as defined in TS 33.501 [20]. + +## 6.14 MBS Service Information + +MBS Service Information is a set of information used by the AF to describe an MBS session. It is directly conveyed from the AF to the MB-SMF or indirectly via NEF and/or MBSF. + +For a location dependent MBS Session, the same MBS Service Information should be provided by the AF for each MBS Service Area. + +In addition, MBS Service Information may be optionally sent from AF/NEF/MBSF to the PCF based on network configuration. + +NOTE 1: Depending on deployment scenarios specified in Annex A, AF, NEF or MBSF interacts with MB-SMF, and optionally that AF, NEF or MBSF interacts with PCF. + +The MBS Service Information consists of an optional AF Application Identifier, an optional Session-AMBR and the description of one or more data flows/media components. For each data flow/media component, the following information may be provided: + +- Flow description; and + +NOTE 2: If a unicast tunnel is used over the N6mb/Nmb9 interface to transport MBS data towards the MB-UPF (see Figure 8.2-1), the Flow description relates to the inner IP layer within the unicast tunnel. + +- one of the following: + - Media information (Media type, Media format, bandwidth) with optional Priority indicator; + - QoS requirements (5G QoS parameters (i.e. 5QI, ARP, GBR, MBR) or QoS reference). + +The following MBS Service Information is mandatory to be supported: 5G QoS parameters (i.e. 5QI, ARP, GBR, MBR) and optional Session-AMBR for one data flow/media component. Additional MBS Service Information is optional to be supported. + +## 6.15 Group Message Delivery + +Group Message Delivery via MBS Session is a feature that allows an AF to deliver a payload to a group of UEs located in a particular geographical area via a broadcast MBS Session, e.g. for Machine-Type communication. The AF may request to deliver group message and the AF may also request to recall (i.e. cancel) or replace a previously submitted group message. + +Group Message Delivery utilizes the Object Distribution Method in MBSTF specified in TS 26.502 [18]. The Object Distribution Method can benefit from Application Layer Forward Error Correction (AL-FEC) to achieve reliable delivery. + +In Group Message Delivery via MBS Session, the NEF is responsible for handling the group message delivery request from the AF, that is, the NEF transforms the group message into a file and determines the meta data information of the file. Over control plane, the NEF provisions Application Service (i.e. MBS User Service creation and MBS User Data Ingest Session creation as specified in TS 26.502 [18]), which then triggers the MBS session creation towards 5GC and NG-RAN. Over user plane, the NEF is responsible for ingesting the file to the MBSTF, which then delivers the file to the UE(s) via 5GC Shared MBS traffic delivery. + +NOTE: The AF can invoke the Nmbsmf service operations offered by the MB-SMF (optionally via the NEF) for Transport Only Mode, as supported in Rel-17. + +## 6.16 Support of MBS data reception for UEs using power saving functions + +MBS provide means to deliver data over MBS Session to multiple UEs at the same time. However, for UEs using power saving functions, e.g. MICO (Mobile Initiated Connection Only) mode with Active Time, or extended DRX (Extended Discontinuous Reception) as defined in clause 5.31.7 of TS 23.501 [5], the UEs are usually unreachable for long periods of time. Moreover, different UEs are likely to be reachable at different times. + +If a UE becomes unreachable for unicast data transfer due to its using power saving functions, the UE may still be involved in MBS specific operations, e.g. activation/deactivation of the MBS service, MBS data transfer reception, reception of service announcement (if needed). + +To receive MBS data, those UEs need to wake up at coordinated times when the MBS data is to be transmitted. The UE is informed via the service announcement about a start time and/or a sequence of scheduled activation times (e.g. a first time and a periodicity) of the MBS Session when the AF may activate the MBS Session and transmit MBS data, as described in clause 6.11. + +The AF may send data starting either at the start time or at any scheduled activation times. If the AF sends data using an multicast MBS Session at a scheduled activation time, it shall first activate the multicast MBS Session at that scheduled activation time. + +NOTE: If the UE does not receive paging for multicast MBS session activation or does not receive MBS data after waking up according to the stored start time and/or scheduled activation times for pre-configured number of times in sequence, the UE can transition to CM-CONNECTED state to retrieve the updated service announcement including start time and/or scheduled activation times for the MBS session from the AF. + +## 6.17 Support of Multicast MBS session data reception in UE with RRC\_INACTIVE state + +To provide multicast MBS service to more UEs in a cell, the NG-RAN may decide to move some UE(s) receiving multicast MBS data from RRC\_CONNECTED to RRC\_INACTIVE state if the UE(s) is capable to receiving MBS data in RRC\_INACTIVE state. + +The decision in NG-RAN may use the following information provided from 5GC: + +- Existing MBS session QoS parameters, e.g. the most demanding ARP and 5QI of all MBS QoS Flow within the MBS session. +- MBS assistance information for the MBS session, the MBS assistance information for the MBS session is an optional parameter and associated with one MBS session, which consists of an indication that the UE is preferred to be kept in connected when the related MBS session that the UE joined is active. When the NG-RAN node receives this information, the NG-RAN may determine to keep the UE in RRC\_CONNECTED state even if the MBS session data is supported to be received in RRC\_INACTIVE state. + +NOTE 1: How the NG-RAN nodes perform those decisions is up to NG-RAN implementation. + +NOTE 2: The "RRC Inactive Assistance Information" in clause 5.3.3.2.5 of TS 23.501 [5] is sent by AMF to NG-RAN, whether and how it is used by NG-RAN for deciding whether to send a UE to RRC\_INACTIVE state is decided by NG-RAN. + +The MBS session QoS parameters (e.g. ARP and 5QI) are provided to NG-RAN by the MB-SMF during user plane establishment for shared delivery. + +Per the MBS session that the UE joined, the related "MBS assistance information for the MBS session" is provided to NG-RAN by the SMF if the MBS assistance information is available in the SMF and the MBS session that the UE joined is included in the MBS assistance information. The SMF gets from the UDM the "MBS assistance information", which is provisioned by the AF via the NEF to the UDM as part of the MBS subscription data and includes all the MBS session ID(s), where the UE is preferred to be kept connected when the related MBS session that the UE joined is active (as specified in clause 6.4). The SMF provides the "MBS assistance information for the MBS session" to the NG-RAN as part of the associated PDU session information within the N2 SM information in the procedures where the associated PDU session information need be sent to NG-RAN node, e.g. PDU Session modification for UE joining, handover procedure. + +When an MBS session is to be activated, if there are UE(s) that joined the MBS session, the 5GC activates the MBS Session in the NG-RANs serving the joined UE(s). When the NG-RAN triggers the group paging to activate the MBS session and decides to enable Multicast MBS session data reception for UE with RRC\_INACTIVE state, it also indicates that the MBS session data is allowed to be received in RRC\_INACTIVE state. Hence the joined UEs in RRC\_INACTIVE state in the cells, where the delivered MBS session is allowed to be received in RRC\_INACTIVE state, may be able to stay in RRC\_INACTIVE state and receive MBS Session data. + +When an UE in RRC\_INACTIVE state is receiving ongoing MBS session data, if the UE moves to a new cell within the RNA, or if the UE moves outside the current RNA but within the current Registration Area, or if the UE moves out of the current Registration Area, the UE should be able to receive the MBS session data if applicable in the new area. + +NOTE 3: The scenario of the UE moving to a new cell within the RAN Notification Area is specified in RAN specifications. + +## 6.18 Resource sharing across broadcast MBS Sessions during network sharing + +In network sharing scenario as specified in clause 5.18 of TS 23.501 [5], the same MBS broadcast service may be delivered via multiple operators' CN participating in the network sharing to a shared NG-RAN, and the shared NG-RAN nodes may broadcast the MBS data only once for resource efficiency. + +When the AF creates multiple broadcast MBS sessions via multiple CNs to deliver the same content, the shared NG-RAN allocates radio resource for one of broadcast MBS Sessions instead of allocating radio resource for all the broadcast MBS Sessions. + +NOTE 1: The same QoS requirements are assumed to be provided by the AF for the broadcast MBS Sessions via multiple CNs delivering the same content. + +The NG-RAN determines the broadcast MBS sessions delivering the same content in one of the following ways: + +- Based on the Associated Session ID (see clause 6.5.5) provided by the AF to the NG-RAN via 5GCs when creating broadcast MBS sessions. +- Based on the association of MBS session identifiers (i.e. TMGIs) configured in NG-RAN, the shared NG-RAN nodes can determine that the multiple broadcast MBS sessions are transmitting the same content for the same MBS service. For the location dependent MBS session, the existing MBS session identifiers are used to identify multiple broadcast MBS Sessions via different CNs delivering the same content. The MB-SMF should be able to accept MBS session creation with TMGIs without prior allocation of those TMGIs. + +For a location dependent MBS session (see Clauses 6.2.3), the AF(s) that create the location dependent MBS sessions towards the participating PLMNs shall supply MBS Service Areas mapped to the same shared radio cells (but that may also be mapped to different non-shared radio cells). + +For location dependent broadcast services, the shared NG-RAN is required to determine that the multiple broadcast MBS Sessions via different CNs deliver the same content for location-dependent MBS session with additionally considering the MBS Service Area. + +NOTE 2: When the association of MBS session identifiers is configured in NG-RAN, there is no requirement on the AF to provide an Associated Session ID. + +NOTE 3: The AFs are configured with TMGIs that are mapped to each other in NG-RAN, and the MB-SMF includes those TMGIs in the NF profile it registers at the NRF, and does not allocate those TMGIs to other MBS services. + +NOTE 4: It is up to NG-RAN implementation whether an NG-RAN node requests to receive multiple copies of MBS data from the core networks of different operators or only a single copy of MBS data. + +Illustrated in Figure 6.18-1 is an example that the AF creates broadcast MBS Sessions via 5GC Operators A, B and C respectively to deliver the same content and N3mb unicast transport is used from 5GC to the NG-RAN. Based on operator policy, the NG-RAN node decides towards which operator(s)' 5GC(s) to establish N3mb tunnel(s), i.e. towards only one, some or all operators' 5GC(s). If N3mb multicast transport is used (not shown in Figure 6.18-1), the NG-RAN node decides which multicast group(s) (i.e. LL SSM(s)) to join.. Over the Uu interface, the NG-RAN allocates radio resource for only one of the established broadcast MBS Sessions regardless of the number of N3mb tunnels established to deliver the MBS packets. + +![Figure 6.18-1: Example of Resource sharing across multiple broadcast MBS Sessions via different CNs to deliver the same content during network sharing. The diagram shows three 5GC Operators (A, B, and C) connected to a central NG-RAN. Each operator's 5GC contains an AMF, an MB-SMF, and an MB-UPF. The NG-RAN is connected to the AMFs via N2 interfaces and to the MB-UPFs via N3mb interfaces. The NG-RAN is also connected to an AF via Nmb2 and N6mb interfaces. The NG-RAN is connected to three User Equipment (UE) devices (UEA, UEB, UEC) via a Uu interface. The diagram illustrates that the NG-RAN can receive multiple N3mb tunnels from different operators and deliver the same content to the UEs via a single Uu interface.](ceb967656aa87e9c8a39e8fe063f8f4c_img.jpg) + +Figure 6.18-1: Example of Resource sharing across multiple broadcast MBS Sessions via different CNs to deliver the same content during network sharing. The diagram shows three 5GC Operators (A, B, and C) connected to a central NG-RAN. Each operator's 5GC contains an AMF, an MB-SMF, and an MB-UPF. The NG-RAN is connected to the AMFs via N2 interfaces and to the MB-UPFs via N3mb interfaces. The NG-RAN is also connected to an AF via Nmb2 and N6mb interfaces. The NG-RAN is connected to three User Equipment (UE) devices (UEA, UEB, UEC) via a Uu interface. The diagram illustrates that the NG-RAN can receive multiple N3mb tunnels from different operators and deliver the same content to the UEs via a single Uu interface. + +**Figure 6.18-1: Example of Resource sharing across multiple broadcast MBS Sessions via different CNs to deliver the same content during network sharing** + +# 7 MBS procedures + +## 7.1 Common procedure for Multicast and Broadcast + +### 7.1.1 MBS Session Management + +#### 7.1.1.1 General + +The call flows in clause 7.1.1 and clause 7.3 show a "NEF/MBSF", but as detailed in Annex A, there can be different related network deployment involving either only NEF, or MBSF, or both. + +The interactions between "NEF/MBSF" and MB-SMF, PCF, BSF and NRF depicted in the call flows apply for NEF, MBSF or a combined NEF and MBSF, depending on network deployment. They may also apply for an AF in the trusted domain where NEF is not mandated. + +However, the interactions between AF and "NEF/MBSF" depicted in the call flows only apply for the NEF. + +Interactions between AF and MBSF based on the MB2 interface follow TS 23.468 [10] (see Annex C). + +Interactions between AF and MBSF based on the xMB interface follow TS 26.348 [11] (see Annex C). + +Services offered by the MBSF and related interactions based on that service between MBSF and AF or NEF (if MBSF and NEF are split as shown in configuration 2) are specified in TS 26.502 [18]. + +Detailed interactions between the MBSF or NEF and the MBSTF are specified in TS 26.502 [18]. + +#### 7.1.1.2 MBS Session Creation without PCC + +This procedure is used by the AF to start the MBS Session towards 5GC and consist of TMGI allocation, and MBS session creation, and they apply to both multicast and broadcast communications unless otherwise stated. + +For multicast, MBS session establishment procedure triggered by UE join requests may follow the MBS session creation procedure to reserve resources towards NG-RAN. For broadcast, the MBS session start procedure to reserve resources towards NG-RAN is triggered by the MBS session creation procedure. + +For both broadcast and multicast communication, the TMGI allocation may be separated from the MBS Session creation request. + +For multicast communication, TMGI allocation procedure is applicable if TMGI is used as MBS Session ID. + +![Sequence diagram for MBS Session Creation without PCC. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, MBSTF, AF. The diagram shows two main flows: one for TMGI allocation (steps 1-6) and one for MBS session creation (steps 8-20), separated by service announcements (steps 7 and 21).](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant NRF + participant MB-SMF + participant MB-UPF + participant MBSTF + + Note right of AF: 1. Nnef_MBSTMGI_Allocate request + AF->>NEF/MBSF: 1. Nnef_MBSTMGI_Allocate request + Note right of NEF/MBSF: 2. Authorization + NEF/MBSF->>NRF: 3. Nnrf_NFDiscovery (MB-SMF) + Note right of MB-SMF: 4. Nmbsmf_TMGI_Allocate Request + MB-SMF-->>NEF/MBSF: 4. Nmbsmf_TMGI_Allocate Request + Note right of NEF/MBSF: 5. Nmbsmf_TMGI_Allocate response(TMGI(s)) + NEF/MBSF-->>MB-SMF: 5. Nmbsmf_TMGI_Allocate response(TMGI(s)) + Note right of NEF/MBSF: 6. Nnef_MBSTMGI_Allocate response(TMGI(s)) + NEF/MBSF->>AF: 6. Nnef_MBSTMGI_Allocate response(TMGI(s)) + + Note right of MB-UPF: 7. Service announcement + MB-UPF-->>AF: 7. Service announcement + + Note right of AF: 8. Nnef_MBSSession_Create Request (MBS Session ID, service type, QoS request) + AF->>NEF/MBSF: 8. Nnef_MBSSession_Create Request (MBS Session ID, service type, QoS request) + Note right of NEF/MBSF: 9. Authorization + NEF/MBSF->>NRF: 10. Nnrf_NFDiscovery (MB-SMF) + Note right of MB-SMF: 11. Nmbsmf_MBSSession_Create Request (MBS Session ID, service type) + MB-SMF-->>NEF/MBSF: 11. Nmbsmf_MBSSession_Create Request (MBS Session ID, service type) + Note right of MB-SMF: 13. Derive QoS parameters + MB-SMF->>MB-UPF: 14. Session Request + MB-UPF-->>MB-SMF: 15. Session Response (Ingress address) + Note right of MB-SMF: 16. Nmbsmf_MBSSession_Create Response (Ingress Address) + MB-SMF->>NEF/MBSF: 16. Nmbsmf_MBSSession_Create Response (Ingress Address) + Note right of MB-SMF: 16a. Nnrf_NFManagement_NFUpdate (MBS Session ID) + MB-SMF-->>NRF: 16a. Nnrf_NFManagement_NFUpdate (MBS Session ID) + Note right of MB-UPF: 17. For broadcast, Procedures toward AMF and NG-RAN in clause 7.3.1 + MB-UPF-->>AF: 17. For broadcast, Procedures toward AMF and NG-RAN in clause 7.3.1 + Note right of NEF/MBSF: 18. Session Request (Ingress address) + NEF/MBSF->>MBSTF: 18. Session Request (Ingress address) + Note right of MBSTF: 19. Session Response (Ingress address) + MBSTF-->>NEF/MBSF: 19. Session Response (Ingress address) + Note right of NEF/MBSF: 20. Nnef_MBSSession_Create Response (Ingress Address) + NEF/MBSF->>AF: 20. Nnef_MBSSession_Create Response (Ingress Address) + + Note right of MB-UPF: 21. Service announcement + MB-UPF-->>AF: 21. Service announcement + + Note right of MB-UPF: 22. For multicast, UE join procedures in clause 7.2.1 + MB-UPF-->>AF: 22. For multicast, UE join procedures in clause 7.2.1 + +``` + +Sequence diagram for MBS Session Creation without PCC. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, MBSTF, AF. The diagram shows two main flows: one for TMGI allocation (steps 1-6) and one for MBS session creation (steps 8-20), separated by service announcements (steps 7 and 21). + +Figure 7.1.1.2-1: MBS Session Creation without PCC + +Steps 1 to 6 are optional and only applicable if TMGI is used as MBS Session ID and required to be pre-allocated. + +1. AF sends Nnef\_MBSTMGI\_Allocate Request (TMGI number, [MBS service area]) message to NEF/MBSF to request allocation of a TMGI(s) to identify new MBS session(s). The MBS service area indicates the possible service area for those TMGI(s) to be allocated, which may be needed for local MBS. + +NOTE 1: Depending on the network deployment and use case, MB-SMF may receive requests from AF directly, or via NEF, or via MBSTF, or via NEF and MBSTF. + +2. NEF/MBSF checks authorization of AF. If geographical area information or civic address information was provided by the AF as MBS service area, NEF/MBSF performs the translation. + +NOTE 2: NEF is not required if AF is in trusted domain. + +3. NEF/MBSF discovers and selects an MB-SMF using NRF or based on local configuration, possibly based on MBS service area. + +If the NEF/MBSF discovers MB-SMF candidates based on MBS service area, and the MBS service area cannot be covered by the MB-SMF service area of a single MB-SMF, the NEF/MBSF rejects the TMGI allocation with an error information indicating that the MBS service area cannot be covered by the MB-SMF service area of a single MB-SMF. The subsequent steps are not executed. + +NOTE 3: It is up to stage 3 to decide whether MBS area information can be provided. + +4. NEF/MBSF sends an Nmbsmf\_TMGI\_Allocate Request (TMGI number) message to the MB-SMF. +5. MB-SMF allocates TMGI(s) and returns the TMGI(s) to the NEF/MBSF via the Nmbsmf\_TMGI\_Allocate response (TMGI(s), expiration time). +6. The NEF or MBSF responds to the AF by sending an Nnef\_MBSTMGI\_Allocate Response (TMGI(s), expiration time). +7. The AF may perform a Service Announcement towards UEs. The AF informs UEs about MBS Session information with MBS Session ID, e.g. TMGI, SSM, and possibly other information e.g. MBS service area, session description information, etc. + +The MBS service area information can be Cell ID list, TAI list, geographical area information or civic address information. Amongst them, Cell ID list and TAI list shall only be used by AFs who reside in trust domain, and when the AFs are aware of such information. + +The UE needs to be aware if the service is broadcast or multicast to decide if JOIN is to be performed. + +8. AF of content provider may provide description for an MBS session (possibly providing information for a previously allocated TMGI to NEF via a Nnef\_MBSSession\_Create request ([MBS Session ID], [MBS service type], [MBS Service Information], [TMGI allocation request], [MBS service area], [Any UE indication], [start and end time of the MBS session], [MBS session state], [ingress transport address request indication], [Request for location-dependent session], [FSA ID(s)], [Associated Session Identifier]). If step 1-6 has not been executed before, the AF may provide an MBS Session ID containing an SSM or it may request that the network allocates an MBS Session ID (i.e. TMGI). The AF provides the MBS service type (i.e. either multicast service or broadcast service) and MBS Service Information (as defined in clause 6.14). The AF may provide the "Any UE indication" (indicating whether a multicast MBS session is "open to any UEs"), MBS service area, start and end time of the MBS session and MBS session state (active/inactive). In addition, the AF request may also indicate that the allocation of an ingress transport address is requested and that the AF request is for a location dependent MBS service. + +If geographical area information or civic address information was provided by the AF as MBS service area, NEF/MBSF translates the MBS service area to Cell ID list or TAI list. + +For broadcast communication, the AF may determine MBS FSA ID(s) for the Broadcast MBS session based on business agreements and include them in the description of the MBS session. + +For broadcast communication, to support resource sharing across MBS Sessions during network sharing (see clause 6.18), the AF may include Associated Session Identifier in this step to enable NG-RAN to identify the broadcast MBS sessions from multiple CNs delivering the same content. + +NOTE 4: The same QoS requirements are assumed to be provided by the AF for the broadcast MBS Sessions via multiple CNs delivering the same content. + +NOTE 5: MBS session state is applicable for multicast MBS Session. + +9. NEF/MBSF checks authorization of content provider. +10. NEF/MBSF discovers MB-SMF candidates and selects MB-SMF as ingress control node, possibly based on MBS service area. If a TMGI is included in step 8, NEF/MBSF finds MB-SMF based on that TMGI. + +If the NEF/MBSF discovers MB-SMF candidates based on MBS service area, and the MBS service area is not covered by the MB-SMF service area of a single MB-SMF, the NEF/MBSF rejects the TMGI allocation with an + +error information indicating that the MBS service area cannot be covered by the MB-SMF service area of a single MB-SMF. The flow continues in step 20 below. + +NOTE 6: It is up to stage 3 to decide whether MBS area information can be provided. + +11. NEF/MBSF sends Nmbsmf\_MBSSession\_Create Request ([MBS Session ID], [MBS service type], [TMGI allocation request], [MBS Service Information (as defined in clause 6.14)], [MBS service area], [Any UE indication], [start and end time of the MBS session], [MBS session state], [ingress transport address request indication], [FSA ID(s)], [Associated Session Identifier], [multicast session security context]) to MB-SMF, to request MB-SMF to reserve ingress resources for a MBS distribution session. The NEF/MBSF forwards all parameters it has received from the AF in step 8. If the MBSF decides to insert an MBSTF into the user plane for the MBS session, it also indicates that the allocation of an ingress transport address is requested even if this was not requested in step 8. The request also includes the Any UE indication if provided in step 8. If the MBSF acts as the MBS security function for multicast as defined in TS 33.501 [20], it provides a multicast session security context for the MBS session. + +If requested to do so, or if a source specific multicast is provided as MBS Session ID in step 11, the MB-SMF allocates a TMGI. + +For broadcast communication, if no MBS FSA ID(s) have been received, the MB-SMF selects MBS FSA ID(s) for the Broadcast MBS session based on local configuration. + +If the MBS service area received in this step cannot be covered by the MB-SMF service area of the MB-SMF, the MB-SMF reduces the MBS service area to be within the MB-SMF service area and continues the procedure using the reduced MBS service area. + +12. Void. + +13. The MB-SMF derives the required QoS parameters locally based on the MBS Service Information. + +14. MB-SMF selects the MB-UPF. If the allocation of an ingress transport address was requested in step 11, the MB-SMF requests the MB-UPF to reserve user plane ingress resources. If multicast transport of the MBS data towards RAN nodes is to be used, the MB-SMF also request the MB-UPF to reserve for the outgoing data a tunnel endpoint and the related identifiers (source IP address, SSM and GTP Tunnel ID) and to forward data received at the user plane ingress resource using that tunnel endpoint. + +If the allocation of an ingress transport address was not requested in step 11, the MB-SMF provides the SSM received as MBS Session ID to the MB-UPF and requests the MB-UPF to join the corresponding multicast tree from the content provider. The MB-SMF may also defer the configuration to join the corresponding multicast tree e.g. based on information that the session is inactive, service requirements and MBS start/end time until receiving the first query for the MBS session as part of the establishment procedure in clause 7.2.1.3, or until receiving a request to activate the MBS session via the MBS Session Update procedure in clause 7.1.1.6. + +15. If requested, MB-UPF selects an ingress address (IP address and port) and a tunnel endpoint for the outgoing data and provides it to MB-SMF. + +16. The MB-SMF sends an Nmbsmf\_MBSSession\_Create response ([TMGI], [Allocated ingress address], [Information of area reduction]). + +MB-SMF indicates the possibly allocated ingress address to the NEF/MBSF. MB-SMF may include TMGI if it is allocated in step 11. For broadcast communication, the MB-SMF includes any MBS FSA ID(s) selected in step 11. + +If the MB-SMF reduces the service area in step 11, the MB-SMF includes result information in the response indicating that the MBS service area cannot be covered by the MB-SMF service area of a single MB-SMF, and includes the Information of area reduction that relates to the reduced MBS service area. + +NOTE 7: Details of the Information of area reduction is defined by stage 3. + +- 16a. If a source specific multicast address is provided as MBS Session ID in step 11, the MB-SMF updates its NF profile at the NRF with the serving MBS Session ID. If an MBS service area was received in step 11, the MB-SMF updates its NF profile at the NRF with that information. + +NOTE 8: If TMGI is used to represent an MBS Session, MB-SMF does not need to update NRF if the TMGI range(s) supported by an MB-SMF is already included in the MB-SMF profile when MB-SMF register itself into NRF. + +17. For broadcast communication, the MB-SMF continues the procedure towards the AMF and NG-RAN as specified in clause 7.3.1 to request the allocation of resources to for the transmission of the broadcast session. +18. [Optional] If the MBSF decides to use an MBSTF, the NEF/MBSF provides the ingress address received in step 16 towards the MBSTF as DL destination. If the allocation of an ingress transport address was requested in step 8, the MBSF requests the MBSTF to allocate the user plane ingress resources. If the allocation of an ingress transport address was not requested in step 8, the MBSF provides the SSM received as Multicast session ID in step 8 and requests the MBSTF to join the corresponding multicast tree from the content provider. +19. [Conditional on step 19] If requested, the MBSTF selects an ingress address (IP address and port) and provides it to NEF/MBSF. +20. The NEF/MBSF indicates the possibly allocated ingress address and other parameters (e.g. TMGI) to the AF via an Nnef\_MBSSession\_Create response ([TMGI], [Allocated ingress address], [Information of area reduction]). If MBS Session ID is not provided in step 8, or the MBS Session ID is SSM, the NEF/MBSF provides the allocated TMGI. If AF requested the allocation of an ingress transport address, the message also includes the allocated ingress address. For broadcast communication, the message also includes any MBS FSA ID(s) received in step 17. + +If the NEF/MBSF rejects the TMGI allocation in step 10, or receives the result information in step 16 indicating that the MBS service area cannot be covered by the MB-SMF service area of the MB-SMF, the NEF/MBSF includes that result information, and forwards the Information of area reduction. + +21. Same as step 7. The AF may also perform a service announcement at this stage. +22. For multicast communication, depending on configuration UEs can join the MBS Session as specified in clause 7.2.1. + +#### 7.1.1.3 MBS Session Creation with PCC + +Deployment of dynamic PCC is optional. This clause describes the procedure when dynamic PCC is deployed. + +![Sequence diagram for MBMS session management involving MB-UPF, MB-SMF, PCF, BSF, UDR, NRF, NEF/MBSF, MBSFT, and AF. The diagram shows the flow of messages for session creation, authorization, and service announcements.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant AF + participant MBSFT + participant NEF/MBSF + participant NRF + participant UDR + participant BSF + participant PCF + participant MB-SMF + participant MB-UPF + + Note right of AF: 1. Nnef_TMGI_Allocate request + AF->>MBSFT: 1. Nnef_TMGI_Allocate request + MBSFT->>NEF/MBSF: 2. Authorization + NEF/MBSF->>NRF: 3. Nnrf_NFDiscovery (MB-SMF) + NRF->>BSF: 4. Nmbsmf_TMGI_Allocate Request + BSF->>MB-SMF: 5. Nmbsmf_TMGI_Allocate reponse(TMGI(s)) + MB-SMF->>NEF/MBSF: 6. Nnef_TMGI_Allocate response(TMGI(s)) + NEF/MBSF->>AF: 7. Service announcement + Note right of AF: 8. Nnef_MBSSession_Create Request (MBS Session ID, service type, QoS request) + AF->>MBSFT: 8. Nnef_MBSSession_Create Request (MBS Session ID, service type, QoS request) + MBSFT->>NEF/MBSF: 9. Authorization + Note right of NEF/MBSF: 10. Decide whether to interact with PCF + Note left of NEF/MBSF: IF NEF/MBSF decides to interact with PCF + NEF/MBSF->>NRF: 11. Nmbsmf_TMGI_Allocate Request + NRF->>BSF: 12. Nbsf_Management_Discovery + BSF->>NRF: 13. Nnrf_NFDiscovery (PCF) + NRF->>PCF: 14. Npcf_MBSPolicyAuthorization_Create Request (MBS Service info) + PCF->>UDR: 15. Nudr_DataManagement_Query + Note right of PCF: 16. Authorize MBS session and derive QoS + PCF->>BSF: 17. Nbsf_Management_register (MBS Session ID, PCF ID) + BSF->>NEF/MBSF: 18. Npcf_MBSPolicyAuthorization_Create Response (MBS session id) + NEF/MBSF->>NRF: 19. Nnrf_NFDiscovery (MB-SMF) + NRF->>BSF: 20. Nmbsmf_MBSSession_Create Request (MBS session Id, service type, MBS Service info) + BSF->>NRF: 21. Nnrf_NFDiscovery (PCF) + NRF->>PCF: 22. Npcf_MBSPolicyControl_Create Request (MBS session ID) + Note right of PCF: IF no policy authorization was performed before + PCF->>BSF: 23. Nbsf_Management_Register + BSF->>UDR: 24. Nudr_DataManagement_Query + Note right of PCF: 25. Authorize MBS session and derive QoS + PCF->>BSF: 26. Nbsf_Management_register (MBS Session ID, PCF ID) + BSF->>PCF: 27. Npcf_MBSPolicyControl_Create Response (PCC rule) + PCF->>MB-UPF: 28. Session Request + MB-UPF->>MB-SMF: 29. Session Response (Ingress address) + MB-SMF->>NEF/MBSF: 30. Nmbsmf_MBSSession_Create Response (Ingress Address) + NEF/MBSF->>NRF: 31. Nnrf_NFManagement_NFUpdate (MBS session ID) + Note left of MB-UPF: 32. For broadcast, Procedures toward AMF and NG-RAN in clause 7.3.1 + NEF/MBSF->>MBSFT: 33. Session Request (Ingress address) + MBSFT->>NEF/MBSF: 34. Session Response (Ingress address) + NEF/MBSF->>AF: 35. Nnef_MBSSession_Create Response (Ingress Address) + AF->>MBSFT: 36. Service announcement + Note left of MB-UPF: 37. For multicast, UE join procedures in clause 7.2.1 + +``` + +Sequence diagram for MBMS session management involving MB-UPF, MB-SMF, PCF, BSF, UDR, NRF, NEF/MBSF, MBSFT, and AF. The diagram shows the flow of messages for session creation, authorization, and service announcements. + +###### **Figure 7.1.1.3-1: MBS Session Creation with PCC** + +Steps 1 to 7 are optional and only applicable if TMGI is used as MBS Session ID and required to be pre-allocated. + +1 to 9: Same as in Figure 7.1.1.2-1. + +10. The NEF/MBSF may optionally, based on local configuration, decide to interact with the PCF. + +NOTE 1: In the deployment without NEF and MBSF, the AF optionally interacts with PCF in steps 11-18. + +If the NEF/MBSF decided to interact with the PCF, steps 11 to 19 are performed, and in step 20 the MBS Service Information is not provided to the MB-SMF. + +If the NEF/MBSF decided not to interact with the PCF, steps 12 to 19 are skipped, and in step 20 the MBS Service Information is provided to the MB-SMF. + +11. [Conditional] If the NEF/MBSF did not receive an MBS Session ID from the AF in step 8, the NEF/MBSF sends an Nmbsmf\_TMGI\_Allocate Request (1) message to the MB-SMF and the MB-SMF allocates a TMGI and returns the TMGI to the NEF/MBSF via the Nmbsmf\_TMGI\_Allocate response (TMGI, expiration time). + +12. [Conditional] If the NEF/MBSF receives the Request for location-dependent session from the AF and if there is a need to select the same PCF for the location dependent MBS Sessions, the NEF/MBSF first uses the BSF Discovery service to discover whether there is a PCF serving the MBS session with the MBS Session ID by using Nbsf\_management\_Discovery operation. If there is a PCF registered for the MBS Session ID, the NEF/MBSF interacts with that PCF and skips the following step 13. + +NOTE 2: This step is not necessary in a deployment with a single PCF. + +13. [Conditional] If step 12 was not executed or the interaction with the BSF revealed that no PCF is registered for the MBS Session ID, the NEF/MBSF discovers the PCF candidates by interacting with the NRF and selects a PCF, possibly based on MBS service area. + +14. The NEF/MBSF sends an Npcf\_MBSPolicy\_Authorization\_Create Request (MBS Session ID, [Area Session Policy ID], [Request for location dependent MBS session], MBS Service Information (as defined in clause 6.14)) to the PCF. + +15. [Optional] The PCF may retrieve authorization information for the MBS session from the UDR (see clause 6.10.2) and takes it into account for the subsequent authorization and QoS allowance check. + +NOTE 3: This step is not necessary in a deployment with a single PCF if authorization data are stored in the PCF. + +16. The PCF determines whether the request is authorized and if the request is authorized, the PCF derives the required QoS parameters based on the received MBS Service Information and determines whether this QoS is allowed. If the required QoS is allowed, the PCF generates the policy information for the MBS session (as defined in clause 6.10) and stores it together with the MBS Session ID. + +17. If the request is authorized and the required QoS is allowed, the PCF registers at the BSF that it handles the MBS session by using Nbsf\_management\_Register Request (MBS Session ID, PCF ID). It provides an identifier that the policy association is for MBS and the MBS Session ID, its own PCF ID and optionally its PCF set ID. + +NOTE 4: This step is not necessary in a deployment with a single PCF. + +18. The PCF sends an Npcf\_MBSPolicy\_Authorization\_Create Response (Result indication, [Area Session Policy ID]) to the NEF/MBSF. + +- The request is authorized for a location dependent MBS Session, the PCF assigns Area Session Policy ID. +- If the request is not authorized or the required QoS is not allowed, the PCF indicates so in the response to the NEF/MBSF which in turn informs the AF about it (by sending the Nnef\_MBSSession\_Create Response) and ends this procedure. + +19. Same as step 10 in Figure 7.1.1.2-1. + +20. Same as step 11 in Figure 7.1.1.2-1 with the following differences: + +- If the optional interaction between AF/NEF/MBSF and PCF has been performed: + +- The MBS Service Information is not present (as it was already provided to the PCF in step 14). +- For location dependent MBS service, the AF/NEF/MBSF also includes Area Session Policy ID (which is assigned by the PCF in step 18) to the MB-SMF. + +21. The MB-SMF discovers the PCF using NRF. + +22. The MB-SMF sends an Npcf\_MBSPolicyControl\_Create Request (MBS Session ID, [Area Session policy ID], [MBS Service Information (as defined in clause 6.14)]) for the MBS session towards the PCF. The MB-SMF forwards the MBS Service Information to the PCF if received from the NEF/MBSF in the previous step 20. + +For location dependent MBS Session, the MB-SMF also sends Area Session Policy ID to the PCF as follows: + +- If the AF/NEF/MBSF does not include Area Session policy ID, (i.e. the AF/NEF/MBSF has not interacted with PCF), the MB-SMF uses its assigned Area Session ID as Area Session Policy ID. +- If AF/NEF/MBSF includes Area Session Policy ID (i.e. AF/NEF/MBSF (i.e. the AF/NEF/MBSF has interacted with PCF), the MB-SMF provides that received Area Session Policy ID (received from AF/NEF/MBSF) as Area Session Policy ID. + +If PCF receives MBS Service Information from the MB-SMF, the PCF performs the subsequent steps 23 to 26. If the PCF does not receive MBS Service Information from the MB-SMF, but has previously determined policy information for the MBS session (see step 16) corresponding to the MBS Session ID (and Area Session Policy ID for location dependent MBS) received from the MB-SMF, the PCF continues with step 27. + +23. If the PCF is not handling the MBS Session ID, the PCF uses the BSF Register service to check whether there is already a PCF serving the MBS session. If so, the PCF skips steps 24 to 26 and indicates in step 27 that the PCF serving the MBS session shall be contacted. + +NOTE 5: This step is not necessary in a deployment with a single PCF. + +24. [Optional] The PCF may retrieve authorization information for the MBS session from the UDR (see clause 6.10.2) and takes it into account for the subsequent authorization and QoS allowance check. + +NOTE 6: This step is not necessary if authorization data are stored in the PCF. + +25. The PCF determines whether the request is authorized and if the request is authorized, the PCF derives the required QoS parameters based on the received MBS Service Information and determines whether this QoS is allowed. If the required QoS is allowed, the PCF generates the policy information for the MBS session (as defined in clause 6.10) and stores it together with the MBS Session ID. + +26. If the request is authorized and the required QoS is allowed the PCF registers at the BSF that it handles the MBS session by using Nbsf\_management\_Register Request (MBS Session ID, PCF ID). It provides an identifier that the policy association is for MBS and the MBS Session ID, its own PCF ID and optionally its PCF set ID. + +NOTE 7: This step is not necessary in a deployment with a single PCF. + +27. The PCF responds with Npcf\_MBSPolicyControl\_Create Response ([policy information for the MBS session (as defined in clause 6.10)], Result indication). + +If the request is not authorized or the required QoS is not allowed, the PCF indicates so in the response to the MB-SMF which in turn informs the AF about it (by sending the Nmbsmf\_MBSSession\_Create Response) and ends this procedure. + +If another PCF is serving the MBS session, the PCF indicates that another PCF serving the MBS session shall be contacted and provides an ID of that other PCF. The MB-SMF then repeats step 22 towards that other PCF. + +28-37: Same as steps 14-22 in Figure 7.1.1.2-1. + +NOTE 8: Steps 33-36 can be executed in parallel to step 32. + +#### 7.1.1.4 MBS Session Deletion without PCC + +This procedure is used by the AF to delete the MBS Session. This procedure may also include TMGI de-allocation. The procedures apply to both multicast and broadcast communications unless otherwise stated. This procedure releases the reserved resources in both 5GC and NG-RAN. + +![Sequence diagram for MBS Session Deletion without PCC. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, MBSTF, AF. The sequence shows the AF sending a delete request to the NEF/MBSF, which then triggers a series of resource releases and profile updates through the MBSTF, MB-SMF, and finally the MB-UPF. The MB-SMF also updates the NRF with the removal of the MBS Session ID from its profile.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant MBSTF + participant NRF + participant MB-SMF + participant MB-UPF + + Note right of NEF/MBSF: 5. For broadcast, see clause 7.3.2 +For multicast, see clause 7.2.2.3 + + AF->>NEF/MBSF: 1. Nnef_MBSSession_Delete Request (MBS Session ID) + NEF/MBSF-->>MBSTF: 2. Session Release Request + MBSTF-->>NEF/MBSF: 3. Session Release Response + NEF/MBSF->>MB-SMF: 4. Nmbsmf_MBSSession_Delete Request (MBS Session ID) + Note right of MB-SMF: 5. For broadcast, see clause 7.3.2 +For multicast, see clause 7.2.2.3 + MB-SMF->>MB-UPF: 6. Session Release Request + MB-UPF-->>MB-SMF: 7. Session Release Response + MB-SMF->>NRF: 8. Nnrf_NFManagement_NFUpdate (Remove MBS Session ID from MB-SMF profile) + MB-SMF->>NEF/MBSF: 9. Nmbsmf_MBSSession_Delete Response + NEF/MBSF-->>AF: 10. Nnef_MBSSession_Delete Response + AF->>NEF/MBSF: 11. Nnef_TMGI_Deallocate Request (TMGI) + NEF/MBSF-->>MB-SMF: 12. Nmbsmf_TMGI_Deallocate request + MB-SMF-->>NEF/MBSF: 13. Nmbsmf_TMGI_Deallocate response + NEF/MBSF-->>AF: 14. Nnef_TMGI_Deallocate response + +``` + +Sequence diagram for MBS Session Deletion without PCC. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, MBSTF, AF. The sequence shows the AF sending a delete request to the NEF/MBSF, which then triggers a series of resource releases and profile updates through the MBSTF, MB-SMF, and finally the MB-UPF. The MB-SMF also updates the NRF with the removal of the MBS Session ID from its profile. + +Figure 7.1.1.4-1: MBS Session Deletion without PCC + +1. AF of content provider may request to delete the MBS session (MBS Session ID). +- 2/3. If an MBSTF was inserted into the user plane, the MBSF request the MBSTF to release user plane resources. +4. NEF/MBSF requests MB-SMF to delete resources for the MBS session. +5. For Broadcast MBS session, the MB-SMF triggers resource release towards the AMFs as specified in clause 7.3.2. For Multicast MBS session, the MB-SMF triggers resource release towards the SMFs as specified in clause 7.2.2.3. +- 6/7. MB-SMF requests the MB-UPF to release user plane resources. +8. [Conditional] If MB-SMF configured the profile with an MBS Session ID when the MBS session was created, the MB-SMF updates its NF profile at NRF to release the MBS Session ID. +9. MB-SMF responds to the NEF/MBSF. + +10. The NEF/MBSF responds to the AF. +11. [Optional] AF requests NEF/MBSF to de-allocate TMGI(s), +12. [Conditional on step 11] NEF/MBSF forwards request to de-allocate TMGI(s) to MB-SMF. +13. [Conditional on step 12] The MB-SMF responds to the NEF or MBSF by sending a de-allocate TMGI Response message. +14. [Conditional on step 13] NEF or MBSF forwards de-allocate TMGI Response message to AF. + +#### 7.1.1.5 MBS Session Deletion with PCC + +This procedure is used by the AF to release the MBS Session. This procedure may also include TMGI de-allocation. The procedures apply to both multicast and broadcast communications unless otherwise stated. This procedure releases the reserved resources in both 5GC and NG-RAN. + +![Sequence diagram for MBS Session Deletion with PCC. Lifelines: MB-UPF, MB-SMF, PCF, BSF, NRF, NEF / MBSF, MBSTF, AF. The diagram shows the interaction between these entities to delete an MBS session. Key steps include: 1. AF sends Nnef_MBSSession_Delete Request to NEF/MBSF; 2-3. NEF/MBSF sends Session Release Request/Response to MBSTF; 4-5. NEF/MBSF sends NpcfMBSPolicyAuthorization_Delete Request/Response to PCF (conditional); 6. NEF/MBSF sends Nmbsmf_MBSSession_Delete Request to MB-SMF; 7-8. MB-SMF sends Npcf_MBS PolicyControl Delete Request/Response to PCF; 9. MB-SMF sends Nbsf_Management_Deregister to BSF; 10. Note for broadcast/multicast; 11-12. MB-SMF sends Session Release Request/Response to MB-UPF; 13. MB-SMF sends Nnrf_NFManagement_NFUpdate to NRF; 14. MB-SMF sends Nmbsmf_MBSSession_Delete Response to NEF/MBSF; 15. NEF/MBSF sends Nnef_MBSSession_Delete Response to AF; 16-19. NEF/MBSF sends Nnef_TMGI_Deallocate Request/Response to AF, and MB-SMF sends Nmbsmf_TMGI_Deallocate request/response to NEF/MBSF.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant MBSTF + participant NRF + participant BSF + participant PCF + participant MB-SMF + participant MB-UPF + + Note right of AF: 1. Nnef_MBSSession_Delete Request (MBS Session ID) + AF->>NEF/MBSF: 1. Nnef_MBSSession_Delete Request (MBS Session ID) + Note right of NEF/MBSF: 2. Session Release Request + NEF/MBSF->>MBSTF: 2. Session Release Request + Note right of MBSTF: 3. Session Release Response + MBSTF-->>NEF/MBSF: 3. Session Release Response + + Note left of NEF/MBSF: IF AF decided to interact with PCF + Note right of NEF/MBSF: 4. NpcfMBSPolicyAuthorization_Delete Request (application session context) + NEF/MBSF->>PCF: 4. NpcfMBSPolicyAuthorization_Delete Request (application session context) + Note right of PCF: 5. NpcfMBSPolicyAuthorization_Delete Response + PCF-->>NEF/MBSF: 5. NpcfMBSPolicyAuthorization_Delete Response + + Note right of NEF/MBSF: 6. Nmbsmf_MBSSession_Delete Request (MBS Session ID) + NEF/MBSF->>MB-SMF: 6. Nmbsmf_MBSSession_Delete Request (MBS Session ID) + Note right of MB-SMF: 7. Npcf_MBS PolicyControl Delete Request + MB-SMF->>PCF: 7. Npcf_MBS PolicyControl Delete Request + Note right of PCF: 8. Npcf_MBS PolicyControl Delete Response + PCF-->>MB-SMF: 8. Npcf_MBS PolicyControl Delete Response + + Note right of MB-SMF: 9. Nbsf_Management_Deregister(MBS session ID, PCF ID) + MB-SMF->>BSF: 9. Nbsf_Management_Deregister(MBS session ID, PCF ID) + + Note left of MB-UPF: 10. For broadcast, see clause 7.3.2 +For multicast, see clause 7.2.2.3 + Note right of MB-SMF: 11. Session Release Request + MB-SMF->>MB-UPF: 11. Session Release Request + Note right of MB-UPF: 12. Session Release Response + MB-UPF-->>MB-SMF: 12. Session Release Response + + Note right of MB-SMF: 13. Nnrf_NFManagement_NFUpdate (Remove MBS Session ID from MB-SMF profile) + MB-SMF->>NRF: 13. Nnrf_NFManagement_NFUpdate (Remove MBS Session ID from MB-SMF profile) + + Note right of MB-SMF: 14. Nmbsmf_MBSSession_Delete Response + MB-SMF-->>NEF/MBSF: 14. Nmbsmf_MBSSession_Delete Response + + Note right of NEF/MBSF: 15. Nnef_MBSSession_Delete Response + NEF/MBSF->>AF: 15. Nnef_MBSSession_Delete Response + + Note right of AF: 16. Nnef_TMGI_Deallocate Request(TMGI) + AF->>NEF/MBSF: 16. Nnef_TMGI_Deallocate Request(TMGI) + Note right of NEF/MBSF: 17. Nmbsmf_TMGI_Deallocate request + NEF/MBSF->>MB-SMF: 17. Nmbsmf_TMGI_Deallocate request + Note right of MB-SMF: 18. Nmbsmf_TMGI_Deallocate response + MB-SMF-->>NEF/MBSF: 18. Nmbsmf_TMGI_Deallocate response + Note right of NEF/MBSF: 19. Nnef_TMGI_Deallocate response + NEF/MBSF->>AF: 19. Nnef_TMGI_Deallocate response + +``` + +Sequence diagram for MBS Session Deletion with PCC. Lifelines: MB-UPF, MB-SMF, PCF, BSF, NRF, NEF / MBSF, MBSTF, AF. The diagram shows the interaction between these entities to delete an MBS session. Key steps include: 1. AF sends Nnef\_MBSSession\_Delete Request to NEF/MBSF; 2-3. NEF/MBSF sends Session Release Request/Response to MBSTF; 4-5. NEF/MBSF sends NpcfMBSPolicyAuthorization\_Delete Request/Response to PCF (conditional); 6. NEF/MBSF sends Nmbsmf\_MBSSession\_Delete Request to MB-SMF; 7-8. MB-SMF sends Npcf\_MBS PolicyControl Delete Request/Response to PCF; 9. MB-SMF sends Nbsf\_Management\_Deregister to BSF; 10. Note for broadcast/multicast; 11-12. MB-SMF sends Session Release Request/Response to MB-UPF; 13. MB-SMF sends Nnrf\_NFManagement\_NFUpdate to NRF; 14. MB-SMF sends Nmbsmf\_MBSSession\_Delete Response to NEF/MBSF; 15. NEF/MBSF sends Nnef\_MBSSession\_Delete Response to AF; 16-19. NEF/MBSF sends Nnef\_TMGI\_Deallocate Request/Response to AF, and MB-SMF sends Nmbsmf\_TMGI\_Deallocate request/response to NEF/MBSF. + +Figure 7.1.1.5-1: MBS Session Deletion with PCC + +1-3. Same as in Figure 7.1.1.4-1. + +For the interaction with the PCF in this procedure, the NEF/MBSF applies the same decision that was taken in step 10 in Figure 7.1.1.3-1 during the MBS Session Creation with PCC procedure: + +If the NEF/MBSF decided to interact with the PCF, steps 4 to 5 are performed. + +If the NEF/MBSF decided not to interact with the PCF, steps 4 to 5 are skipped. + +NOTE 1: If NEF and MBSF is not deployed, the AF optionally interacts with PCF in steps 4 to 5. + +4. The NEF/MBSF sends an Npcf\_MBSPolicyAuthorization\_Delete Request to the PCF that handles the MBS Session. + +5. The PCF sends an Npcf\_MBSPolicyAuthorization\_Delete Response to the NEF/MBSF. +6. Same as step 4 in Figure 7.1.1.4-1. +7. The MB-SMF sends the Npcf\_MBSPolicyControl\_Delete Request to request the deletion of the SM Policy Association with the PCF. +8. The PCF sends the Npcf\_MBSPolicyControl\_Delete Response to the MB-SMF. +9. The PCF de-registers at the BSF that it handles the MBS session. +- 10-19. Same as steps 5-14 in Figure 7.1.1.4-1. + +#### 7.1.1.6 MBS Session Update without PCC + +This procedure is used by the AF to update the MBS service area and/or MBS Service Information. Updating MBS Service Information may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s). The procedure applies to both multicast and broadcast communications unless otherwise stated. + +If the MBSF acts as the MBS security function for multicast as defined in TS 33.501 [20], it may use this procedure to provide an MSK for the MBS session via the control plane. In this case the MBSF may initiate this procedure and steps 1, 2 and 10 do not apply. + +NOTE: The procedure is not applicable if no MSK but only the MTK is to be updated. + +For local multicast services and location dependent multicast services, the AF may perform a Service Announcement towards UEs to update the MBS service area before the MBS Session Update procedure is started or after the MBS Session Update procedure is completed. + +![Sequence diagram for MBS Session Update without PCC. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, AF. The sequence starts with the AF sending an Nnef_MBSSession_Update Request to the NEF/MBSF. The NEF/MBSF performs an Authorization check and then sends an MBS Session Update Request to the MB-SMF. The MB-SMF derives QoS parameters and sends a Session Update Request to the MB-UPF. The MB-UPF sends a Session UpdateResponse. A note indicates that for broadcast, clause 7.3.3 applies, and for multicast, clauses 7.2.5 and 7.2.6 apply. The MB-SMF then sends an Nnrf_NFManagement_NFUpdate to the NRF and an Nmbsmf_MBSSession_Update response to the NEF/MBSF. Finally, the NEF/MBSF sends an Nnef_MBSSession_Update Response to the AF.](90df9788d66ecf65abf861caf76be5ca_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant MB-SMF + participant NRF + participant MB-UPF + + Note right of NEF/MBSF: 2. Authorization + AF->>NEF/MBSF: 1. Nnef_MBSSession_Update Request (MBS Session ID, Update) + NEF/MBSF->>MB-SMF: 3. MBS Session Update Request (QoS flow information, MBS service area, session activity status (active/inactive)) + Note right of MB-SMF: 4. Derive Qos Parameters + MB-SMF->>MB-UPF: 5. Session Update Request + MB-UPF->>MB-SMF: 6. Session UpdateResponse + Note right of MB-SMF: 7. For broadcast, see clause 7.3.3 +For multicast, see clause 7.2.5, 7.2.6 + MB-SMF->>NRF: 8. Nnrf_NFManagement_NFUpdate (MBS session ID, MBS service area) + MB-SMF->>NEF/MBSF: 9. Nmbsmf_MBSSession_Update response + NEF/MBSF->>AF: 10. Nnef_MBSSession_Update Response + +``` + +Sequence diagram for MBS Session Update without PCC. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, AF. The sequence starts with the AF sending an Nnef\_MBSSession\_Update Request to the NEF/MBSF. The NEF/MBSF performs an Authorization check and then sends an MBS Session Update Request to the MB-SMF. The MB-SMF derives QoS parameters and sends a Session Update Request to the MB-UPF. The MB-UPF sends a Session UpdateResponse. A note indicates that for broadcast, clause 7.3.3 applies, and for multicast, clauses 7.2.5 and 7.2.6 apply. The MB-SMF then sends an Nnrf\_NFManagement\_NFUpdate to the NRF and an Nmbsmf\_MBSSession\_Update response to the NEF/MBSF. Finally, the NEF/MBSF sends an Nnef\_MBSSession\_Update Response to the AF. + +Figure 7.1.1.6-1: MBS Session Update without PCC + +1. AF of content provider initiates MBS Session Update to a NEF/MBSF, e.g. to update MBS service area and/or update MBS Service Information (as defined in clause 6.14), or to activate or deactivate an MBS session. AF + +may provide updated information for an MBS session (identified by MBS session ID) by sending an Nnef\_MBSSession\_Update Request (MBS Session ID, [MBS Service Information], [MBS service area], [MBS session state (active/inactive)]). + +If geographical area information or civic address information was provided by the AF as MBS service area, NEF/MBSF translates the MBS service area to Cell ID list or TAI list. + +2. NEF checks authorization of AF. +3. NEF/MBSF sends Nmbsmf\_MBSSession\_Update Request to MB-SMF forwarding the updated information received from the AF in step 1. If the MBSF acts as the MBS security function for multicast as defined in TS 33.501 [20], it may provide an updated multicast session security context for the MBS session in the Nmbsmf\_MBSSession\_Update Request. + +If the MBS service area is not covered by the MB-SMF service area of the MB-SMF, the MB-SMF reduces the MBS service area to be within the MB-SMF service area and continues the procedure with the reduced MBS service area. + +4. The MB-SMF derives any updated QoS parameters locally under consideration of the updated MBS Service Information. This may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s). +- 5-6. MB-SMF may need to update MB-UPF, e.g. if new MBS QoS Flow is to be created, or existing MBS QoS Flow is to be deleted. +7. For broadcast communication, the MB-SMF continues the procedure towards the AMF and NG-RAN as specified in clause 7.3.3. For multicast communication, the MB-SMF continues the procedure towards the AMF and NG-RAN as specified in clause 7.2.5 (for service activation/deactivation), 7.2.6 (for QoS updates and service area updates). +8. If an MBS service area is being updated, the MB-SMF stores the new service area in its profile at the NRF. +9. MB-SMF responds to the NEF/MBSF with a Nmbsmf\_MBSSession\_Update Response ([Information of area reduction]). + +If the MB-SMF reduces the MBS service area in step 3, the MB-SMF includes result information in the response indicating that the MBS service area cannot be covered by the MB-SMF service area of the MB-SMF, and includes the Information of area reduction that relates to the reduced MBS service area. + +NOTE: Details of the Information of area reduction is defined by stage 3. + +10. NEF/MBSF responds to the AF with a Nnef\_MBSSession\_Update Response ([MBS service area information]). + +If the NEF/MBSF receives the result information in step 9 indicating that the MBS service area cannot be covered by the MB-SMF service area of the MB-SMF, the NEF/MBSF includes that result information, and the Information of area reduction. + +#### 7.1.1.7 MBS Session Update with PCC + +For local multicast services and location dependent multicast services, the AF may perform a Service Announcement towards UEs to update the MBS service area before the MBS Session Update procedure is started or after the MBS Session Update procedure is completed. + +![Sequence diagram for MBS Session Update with PCC. Lifelines: MB-UPF, MB-SMF, PCF, NRF, NEF / MBSF, AF. The diagram shows the interaction between these network functions to update an MBS session. Key steps include: 1. AF sends Nnef_MBSSession_Update Request to NEF/MBSF; 2. NEF/MBSF performs Authorization; 3. NEF/MBSF decides whether to interact with PCF; 4. NEF/MBSF sends Npcf_MBSPolicyAuthorization_Update Request to PCF; 5. PCF authorizes updates and derives update QoS; 6. PCF sends Npcf_MBSPolicyAuthorization_Update Response to NEF/MBSF; 7. NEF/MBSF sends Nmbsmf_MBSSession_Update Request to MB-SMF; 8. MB-SMF sends Npcf_MBSPolicyControl_Update Request to PCF; 9. PCF authorizes updates and derives QoS (if it receives MBS Service Information from MB-SMF); 10. PCF sends Npcf_MBSPolicyControl_Update Response to MB-SMF; 11. MB-SMF sends Session Update Request to MB-UPF; 12. MB-UPF sends Session Update Response to MB-SMF; 13. Note: For broadcast, see clause 7.3.3; For multicast, see clause 7.2.5, 7.2.6; 14. MB-SMF sends Nnrf_NFManagement_NFUpdate to NRF; 15. MB-SMF sends Nmbsmf_MBSSession_Update Response to NEF/MBSF; 16. NEF/MBSF sends Nnef_MBSSession_Update Response to AF.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF_MBSF as NEF / MBSF + participant PCF + participant MB_SMF as MB-SMF + participant MB_UPF as MB-UPF + participant NRF + + Note right of NEF_MBSF: 1. Nnef_MBSSession_Update Request + Note right of NEF_MBSF: 2. Authorization + Note right of NEF_MBSF: 3. Decide whether to interact with PCF + + Note left of PCF: IF NEF/MBSF decided to interact with PCF + Note right of NEF_MBSF: 4. Npcf_MBSPolicyAuthorization_Update Request + Note right of PCF: 5. Authorize updates and derive update QoS + Note right of PCF: 6. Npcf_MBSPolicyAuthorization_Update Response + + Note right of NEF_MBSF: 7. Nmbsmf_MBSSession_Update Request + Note right of MB_SMF: 8. Npcf_MBSPolicyControl_Update Request + Note left of PCF: If PCF receives MBS Service Information from the MB-SMF + Note right of PCF: 9. Authorize updates and derive QoS + Note right of PCF: 10. Npcf_MBSPolicyControl_Update Response + Note right of MB_SMF: 11. Session Update Request + Note right of MB_UPF: 12. Session Update Response + Note right of MB_UPF: 13. For broadcast, see clause 7.3.3 +For multicast, see clause 7.2.5, 7.2.6 + Note right of MB_SMF: 14. Nnrf_NFManagement_NFUpdate + Note right of MB_SMF: 15. Nmbsmf_MBSSession_Update Response + Note right of NEF_MBSF: 16. Nnef_MBSSession_Update Response + +``` + +Sequence diagram for MBS Session Update with PCC. Lifelines: MB-UPF, MB-SMF, PCF, NRF, NEF / MBSF, AF. The diagram shows the interaction between these network functions to update an MBS session. Key steps include: 1. AF sends Nnef\_MBSSession\_Update Request to NEF/MBSF; 2. NEF/MBSF performs Authorization; 3. NEF/MBSF decides whether to interact with PCF; 4. NEF/MBSF sends Npcf\_MBSPolicyAuthorization\_Update Request to PCF; 5. PCF authorizes updates and derives update QoS; 6. PCF sends Npcf\_MBSPolicyAuthorization\_Update Response to NEF/MBSF; 7. NEF/MBSF sends Nmbsmf\_MBSSession\_Update Request to MB-SMF; 8. MB-SMF sends Npcf\_MBSPolicyControl\_Update Request to PCF; 9. PCF authorizes updates and derives QoS (if it receives MBS Service Information from MB-SMF); 10. PCF sends Npcf\_MBSPolicyControl\_Update Response to MB-SMF; 11. MB-SMF sends Session Update Request to MB-UPF; 12. MB-UPF sends Session Update Response to MB-SMF; 13. Note: For broadcast, see clause 7.3.3; For multicast, see clause 7.2.5, 7.2.6; 14. MB-SMF sends Nnrf\_NFManagement\_NFUpdate to NRF; 15. MB-SMF sends Nmbsmf\_MBSSession\_Update Response to NEF/MBSF; 16. NEF/MBSF sends Nnef\_MBSSession\_Update Response to AF. + +Figure 7.1.1.7-1: MBS Session Update with PCC + +1-2. Same as in Figure 7.1.1.6-1. + +3. For the interaction with the PCF in this procedure, the NEF/MBSF applies the same decision that was taken in step 10 in Figure 7.1.1.3-1 during the MBS Session Creation with PCC procedure unless the MBS session update only relates to an activation or deactivation of the MBS session and/or an MBS service area update and thus no PCF interactions are required. + +If the NEF/MBSF decided to interact with the PCF, steps 4 to 6 are performed and in step 7 an indication that the PCF has to be contacted is provided, and MBS Service Information is not provided to the MB-SMF. + +If the NEF/MBSF decided not to interact with the PCF, steps 4 to 6 are skipped and MBS Service Information is provided to the MB-SMF in step 7. + +NOTE 1: In the deployment without NEF and MBSF, the AF optionally interacts with PCF in steps 4 - 6. + +4. NEF/MBSF sends an Npcf\_MBSPolicy\_Authorization\_Update Request (application session context, [MBS Service Information]) to the PCF forwarding the updated information received from the AF in step 1. +5. The PCF determines whether the update is authorized and if the update is authorized, the PCF derives the update for the QoS parameters based on the received MBS Service Information and determines whether this new QoS is allowed. If the new QoS is allowed, the PCF updates the policy information for the MBS session (as defined in clause 6.10) accordingly. If the policy information for the MBS session has changed, the PCF shall provide an indication that the PCF has to be contacted. +6. The PCF sends an Npcf\_MBSPolicy\_Authorization\_Update Response (Result indication, [indication that the PCF has to be contacted]) to the NEF/MBSF. + +If the update is not authorized or the new QoS is not allowed, the PCF indicates so in the response to the NEF/MBSF which in turn informs the AF about it (by sending the Nnef\_MBSSession\_Update Response) and ends this procedure. + +7. The NEF/MBSF sends Nmbsmf\_MBSSession\_Update Request to the MB-SMF forwarding the updated information received from the AF in step 1. If the NEF/MBSF has decided not to interact with the PCF, the NEF/MBSF send the indication that the PCF has to be contacted, in addition. + +If the NEF/MBSF has decided to interact with the PCF and thus provided the updated MBS Service Information to the PCF in step 4, the updated MBS Service Information is not forwarded. The NEF/MBSF forwards the indication that the PCF has to be contacted, if received from the PCF. + +8. If the MB-SMF does not receive the indication that the PCF has to be contacted, the MB-SMF decides whether to interact with the PCF. If it decides not to interact with the PCF, it continues with step 11. Otherwise, the MB-SMF sends an Npcf\_MBSPolicyControl\_Update Request (MBS Policy Association ID, [MBS Service Information]) for the MBS session towards the PCF. The MB-SMF forwards the MBS Service Information to the PCF if received from the NEF/MBSF in the previous step 7. + +If PCF receives MBS Service Information from the MB-SMF, the PCF performs the subsequent step 9. If the PCF does not receive MBS Service Information from the MB-SMF, the PCF identifies any updated policy information for the MBS session (as defined in clause 6.10) corresponding to the MBS Session ID received from the MB-SMF and continues with step 10. + +9. The PCF determines whether the update is authorized and if the update is authorized, the PCF derives the update for the QoS parameters based on the received MBS Service Information and determines whether this new QoS is allowed. If the new QoS is allowed, the PCF updates the policy information for the MBS session (as defined in clause 6.10) accordingly. +10. The PCF responds with Npcf\_MBSPolicyControl\_Update Response ([updated policy information for the MBS session], Result indication). + +If the request is not authorized or the required QoS is not allowed, the PCF indicates so in the response to the MB-SMF which in turn informs the AF about it (by sending the Nmbsmf\_MBSSession\_Update Response) and ends this procedure. + +11.-16. Same as steps 5-10 in Figure 7.1.1.6-1. + +### 7.1.2 MB-SMF discovery and selection for multicast/broadcast session + +To facilitate the MB-SMF discovery/selection for one multicast/broadcast MBS session, the following mechanism is used: + +- The MB-SMF registers its capability related to Multicast/Broadcast Service session management (e.g. S-NSSAI(s) and the associated NSI ID(s) (if available), DNN(s), TMGI range, service area) as part of its profile to + +the NRF by invoking Nnrf\_NFManagement\_NFRegister. In addition, when a Multicast MBS session is created and the MBS Session ID is not yet included in the MB-SMF profile, the MB-SMF updates its profile towards the NRF with the MB Session ID (i.e. TMGI or source specific IP multicast address). + +NOTE: The operator can preconfigure MB-SMF for specific source IP multicast address range or TMGI range. + +- When the UE joins the multicast MBS session via PDU session modification procedures, the SMF serving the PDU session invokes the Nnrf\_NFDiscovery\_Request Request including the MBS Session ID for multicast provided by the UE and optionally other information, i.e. the S-NSSAI and the associated NSI ID (if available), DNN, etc. to query the NRF for MB-SMF information. Based on the MBS Session ID and other information for query, the NRF decides whether an MB-SMF serving the MBS session exists (i.e. the NRF decides whether the requested MBS Session ID is in the profile of an MB-SMF, as defined in clause 7.1.1.2 or clause 7.1.1.3 or preconfigured by the operator). If so, the NRF provides in Nnrf\_NFDiscovery\_Request Response the information of the MB-SMF currently serving the MBS session. The SMF serving the PDU session selects the MB-SMF currently serving the multicast MBS session, based on the MB-SMF information provided by the NRF. For local MBS services, the SMF takes MB-SMF service area, UE location into account when selecting the MB-SMF. If no MB-SMF serving the Multicast MBS session exists, the NRF does not provide MB-SMF profiles in the response message to the SMF as defined in TS 29.510 [19]. +- When the shared tunnel for shared delivery is established as described in clause 7.2.1.4, the AMF may invoke the Nnrf\_NFDiscovery\_Request Request including MBS Session ID and Area Session ID (if received from the NG-RAN), to query the NRF for the MB-SMF information. In this case, based on the MBS Session ID and Area Session ID, the NRF provides in Nnrf\_NFDiscovery\_Request Response the MB-SMF information currently serving the MBS session and the Area Session ID. +- When the Multicast MBS Session Context is deleted from the MB-SMF, e.g. due to MBS session release, the MB-SMF updates its profile towards the NRF (i.e. removing the MBS Session ID which is no longer served by the MB-SMF), if the MB-SMF performed NRF registration at multicast MBS Session Creation. +- During MBS session information provisioning procedures defined in clause 7.1.1.2, unless the MB-SMF information is available by other means, e.g. locally configured in the NEF/MBSF/AF, the NEF/MBSF/AF queries the NRF with information of the Multicast/Broadcast Service session (as specified in clause 5.3.2.15.1) and selects the MB-SMF(s) based on the MB-SMF information provided by the NRF. For local MBS services, the NEF/MBSF/AF takes MB-SMF service area into account when selecting the MB-SMF(s). + +### 7.1.3 MB-UPF discovery and selection for multicast/broadcast session + +The selection and reselection of the MB-UPF are performed by the MB-SMF by considering MB-UPF deployment. For the local Broadcast/Multicast MBS session and location dependent MBS session, the service area is taken into consideration for MB-UPF selection. + +MB-SMF may be locally configured with the information about the available MB-UPFs, e.g. by OA&M system when MB-UPF is instantiated or removed. + +The MB-UPF selection functionality in the MB-SMF may optionally utilize the NRF to discover MB-UPF instance(s) which is similar with UPF selection with NRF defined in the TS 23.501 [5] clause 6.3.3.2. + +## 7.2 MBS procedures for multicast Session + +### 7.2.1 MBS join and Session establishment procedure + +#### 7.2.1.1 General + +MBS Session Join procedure is used by UEs to inform the 5GC of the UE interest in joining a multicast MBS session. The first accepted UE join request will trigger the multicast MBS session establishment towards the NG-RAN and the UE. + +#### 7.2.1.2 Establishment of a PDU Session that can be associated with multicast session(s) + +The PDU Session associated with Multicast MBS session(s) (i.e. the associated PDU Session) is established using the procedures as specified in TS 23.502 [6] clause 4.3.2.2 with the following differences: + +NOTE 1: The DNN and S-NSSAI are used to establish the PDU session which can carry the operations related to Multicast MBS session(s), i.e. session join/leave, and can be associated with multicast MBS session(s). + +- In step 2, the AMF selects an SMF capable of handling Multicast MBS sessions based on DNN and S-NSSAI, locally configured data or a corresponding SMF profile stored in the NRF. For indirect discovery, the AMF requests the SCP to select an SMF capable of handling Multicast MBS sessions. +- In step 4, if MBS subscription data for the UE (i.e. corresponding SUPI), DNN and S-NSSAI of the HPLMN or subscribed SNPN is not available, the SMF retrieves the MBS subscription data using Nudm\_SDM\_Get (SUPI, MBS subscription data, selected DNN, S-NSSAI of the HPLMN or subscribed SNPN, Serving PLMN ID (or PLMN ID and NID)) and subscribes to be notified when this subscription data is modified using Nudm\_SDM\_Subscribe (SUPI, MBS subscription data, selected DNN, S-NSSAI of the HPLMN or SNPN, Serving PLMN ID (or PLMN ID and NID)). UDM may get this information from UDR by Nudr\_DM\_Query (SUPI, MBS data, selected DNN, S-NSSAI of the HPLMN or subscribed SNPN, Serving PLMN ID (or PLMN ID and NID)) and may subscribe to notifications from UDR for the same data by Nudr\_DM\_subscribe. The MBS subscription data can also be retrieved along with the Session Management Subscription data, i.e. with additional input parameter for MBS subscription data in the Nudm\_SDM services. + +NOTE 2: In this release, roaming is not supported, i.e. HPLMN and Serving PLMN are the same and subscribed SNPN and serving SNPN are same. + +#### 7.2.1.3 Multicast session join and session establishment procedure + +The following steps are executed before the UE requests to join the MBS session: + +- The MBS Session may have been created in the 5GC (see clause 7.1.1 for details). +- The UE registers in the PLMN or SNPN and may have established a PDU session that can be associated with multicast session(s). +- The UE has known at least the MBS Session ID of a multicast group that the UE can join, e.g. via service announcement. + +![Sequence diagram for PDU Session modification for UE joining Multicast MBS session. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, NRF, PCF, MB-SMF, MB-UPF, and AF. It details the process of sending a PDU Session Modification Request, context updates, and multicast data delivery via shared or individual MBS traffic delivery.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant NRF + participant PCF + participant MB-SMF + participant MB-UPF + participant AF + + Note left of UE: 1a. UL NAS message (N1 SM container (PDU Session Modification Request)) + UE->>AMF: 1a. UL NAS message (N1 SM container (PDU Session Modification Request)) + AMF->>SMF: 1b. Nsmf_PDUSession_UpdateSMContext request + SMF->>NRF: 2. Nnrf_NFDiscovery request/response + SMF->>MB-SMF: 3. Nmbsmf_MBSSession_ContextStatusSubscribe request/response + Note right of SMF: 4. Authorization check, see clause 6.4.1 + SMF->>AMF: 5. Nsmf_PDUSession_UpdateSMContext response + AMF->>NG-RAN: 6. N2 message request + Note right of NG-RAN: 7. Establishment of shared delivery towards RAN node if NG-RAN supports 5G MBS (c.f. 7.2.1.4) + Note left of NG-RAN: 7a. MBS Radio Bearer Configuration + NG-RAN->>UE: 8. RRC message (PDU Session Modification command) + NG-RAN->>AMF: 9. N2 message response + AMF->>SMF: 10. Nsmf_PDUSession_UpdateSMContext request + Note right of SMF: Establishment of 5GC Individual MBS traffic delivery if NG-RAN does not support 5G MBS + SMF->>UPF: 11a. N4 Session Modification + Note right of SMF: Setup unicast transport or request multicast DL tunnel info for multicast transport + SMF->>MB-SMF: 11b. Nmbsmf_MBSSession_ContextUpdate request + MB-SMF->>AF: 11c. N4mb Session Modification/Create + MB-SMF->>SMF: 11d. Nmbsmf_MBSSession_ContextUpdate response + SMF->>UPF: 11e. N4 Session Modification + SMF->>AMF: 12. Nsmf_PDUSession_UpdateSMContext response + AF->>MB-UPF: 13. Multicast data + Note right of MB-UPF: Transmission via 5GC Shared MBS traffic delivery + MB-UPF->>NG-RAN: 14. Multicast data + NG-RAN->>UE: 16. Multicast data via MBS Radio Bearer + Note right of MB-UPF: Transmission via 5GC Individual MBS traffic delivery + MB-UPF->>UPF: 17. Multicast data + UPF->>NG-RAN: 18. Multicast data via PDU Session + NG-RAN->>UE: 19. Multicast data via PDU Session + +``` + +Sequence diagram for PDU Session modification for UE joining Multicast MBS session. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, NRF, PCF, MB-SMF, MB-UPF, and AF. It details the process of sending a PDU Session Modification Request, context updates, and multicast data delivery via shared or individual MBS traffic delivery. + +Figure 7.2.1.3-1: PDU Session modification for UE joining Multicast MBS session + +1. To join a multicast group: + +- if there is an existing PDU session that can be used to send the UE join request for the multicast MBS Session, the UE sends a PDU Session Modification Request over that PDU session (i.e. associated PDU Session) which additionally contains one or several MBS Session ID(s) and join request. The MBS Session ID(s) indicate the multicast MBS session(s) that UE wants to join. +- if the UE has no appropriate PDU session established with the DNN and S-NSSAI for the multicast MBS session, the UE joins the multicast MBS session by sending PDU Session Establishment Request for associated PDU session together with one or several MBS Session ID(s) and join request. In that case, before + +step 2, the network proceeds with establishment of the associated PDU session executing steps 4 to 10 of PDU Session Establishment procedure as specified in TS 23.502 [6] clause 4.3.2.2. + +NOTE 1: To avoid that join requests at the MBS session start time are rejected due to many UEs joining at the same time, UEs can send join requests already before the MBS session start time if provided in service announcement as specified in clause 6.11. + +2. [Conditional] Based on the received MBS Session ID and join request, the SMF determines this is MBS Session join request. + +If SMF has no information about MBS Session Context for the indicated MBS Session ID(s), SMF discovers and selects an MB-SMF for the MBS Session via the NRF as described in clause 7.1.2. If no MB-SMF is assigned for the MBS Session ID (i.e. the NRF provides empty MB-SMF profile), the SMF may select an MB-SMF and request it to configure the multicast MBS session or the SMF may reject the join request and respond to the UE with an appropriate cause value. + +NOTE 2: Details about how the SMF selects an MB-SMF and requests it to configure the multicast MBS session are left to SMF implementation. + +3. [Conditional] For each MBS session in step 1, if the SMF has not subscribed to the MBS Session Context, it invokes Nmbsmf\_MBSSession\_ContextStatusSubscribe request (MBS Session ID) towards the MB-SMF to subscribe to events notifications related to the multicast MBS session and to request information about the MBS Session Context. The MB-SMF responds with the information about the indicated multicast MBS session in Nmbsmf\_MBSSession\_ContextStatusSubscribe response (multicast QoS flow information (e.g. QoS profile(s) for the multicast MBS session), [start time], [session state (Active/Inactive)], [Any UE indication], [multicast DL tunnel info], [multicast session security context]). + +If it is the first time for the MB-SMF to receive Nmbsmf\_MBSSession\_ContextStatusSubscribe request of the indicated MBS Session from any SMF, the MB-SMF learns it is the first UE joining the multicast MBS session. For multicast transport between MB-UPF and content provider, if it is the first UE joining the multicast MBS session, and MB-UPF has not joined the multicast tree in the MBS session creation procedure, described in clause 7.1.1, the MB-SMF requests the MB-UPF to join the multicast tree towards the AF/MBSE, otherwise MB-SMF will not send the request to the MB-UPF. + +NOTE 3: The MB-SMF can answer the Nmbsmf\_MBSSession\_ContextStatusSubscribe request either based on information received in the MBS session creation procedures in clause 7.1.1 or based on preconfigured information. The pre-configuration also includes information about the MBS session stored in the NRF. If the MB-SMF uses preconfigured information, the pre-configuration also includes MB-UPF configuration. + +4. The SMF determines whether the user is authorized to join the Multicast MBS session taking into account the MBS subscription data received from the UDM and the Any UE indication if received from the MB-SMF. The SMF considers the UE as authorized to the Multicast MBS session if the UE is authorized to use multicast MBS services, and if the MBS Session ID(s) in the PDU Session Modification Request is included in the MBS subscription data or Any UE indication is received. If authorization check fails, the SMF rejects the join request with a cause value. If a UE joins prior to the start time of the multicast MBS session, the SMF may accept the join request and indicate to the UE the start time, or it may reject the join request with an appropriate error cause and optionally a back-off timer. If a UE joins while the multicast MBS session is inactive, the SMF accepts the join request. The MBS subscription data from the UDM may also contain MBS assistance information. + +NOTE 4: To avoid that joins requests at the MBS session start time are rejected due to many UEs joining at the same time, the SMF can accept join requests already before the MBS session start time and indicate to the UE the start time. + +5. If the join request is accepted, the SMF responds to the AMF through Nsmf\_PDUSession\_UpdateSMContext response (N2 SM information (PDU Session ID, MBS Session ID, [updated PDU Session information], [mapping information between unicast QoS flow(s) and multicast QoS flow (s)], [MBS Assistance Information for the MBS session]), N1 SM container (PDU Session Modification Command, [multicast session security context])) to: + +- create an MBS Session Context for the indicated MBS session in the RAN, if it does not exist in the RAN already; and + +- inform the NG-RAN about the relation between the Multicast MBS Session Context and the UE's PDU Session context by including the MBS Session ID and the mapping between the multicast QoS flow(s) and associated QoS flow(s). + +Based on operator policy, the SMF may prepare for 5GC Individual MBS traffic delivery fall-back. The SMF maps the received QoS information of the multicast QoS Flow into PDU Session's unicast QoS Flow information, and includes the information of the QoS Flows and the mapping information about the QoS Flows (termed "associated QoS flow information") in the SM information sent to RAN. The SMF compares the QFIs of the multicast QoS Flows received from the MB-SMF with QFIs in use for the PDU Session and assigns unused QFIs to the PDU Session's unicast QoS Flows corresponding to multicast QoS Flows. + +NOTE 5: Detailed information included in N2 SM information will be aligned with by RAN WG3. + +NOTE 6: The SMF uses the same QoS in the received MBS QoS Flow QoS information for the associated QoS Flow in the unicast PDU session. + +If the MBS session join procedure was triggered by the UE together with PDU Session Establishment procedure for the associated PDU session, the SMF provides the N2 SM information and N1 SM container for the associated PDU session in Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF, as described in step 11 of clause 4.3.2.2.1 in TS 23.502 [6]. The N2 SM information also includes the MBS Session ID and, if 5GC individual MBS traffic delivery fall-back is supported, the mapping information between unicast QoS flow(s) and multicast QoS flow(s). + +If the join request is rejected, the SMF responds to the AMF through Nsmf\_PDUSession\_UpdateSMContext response (N1 SM container (PDU Session Modification Reject)) and the message will not contain any MBS Session Context or the N2 SM information for the associated PDU session. The PDU Session Modification Reject message is forwarded to the UE via the NG-RAN, and the following steps are skipped. + +The SMF may also include the MBS assistance information for the MBS session in N2 SM Information, if the MBS subscription data from the UDM contains the MBS assistance information which includes the ID of the MBS session that the UE requests to join. The MBS assistance information for the MBS session sent to NG-RAN is described in clause 6.17. + +6. The N2 message, which includes the MBS Session ID(s) the UE has joined and, if applicable, associated QoS Flow, is sent to the NG-RAN. + +If the MBS is supported by NG-RAN, 5GC Shared MBS traffic delivery is adopted. If the MBS is not supported by NG-RAN, 5GC Individual MBS traffic delivery is used if the PDU Session's unicast QoS Flow include QoS Flows for the multicast session. + +If the NG-RAN supports MBS, the NG-RAN uses the MBS Session ID to determine that the PDU Session identified by the PDU Session ID is associated with the indicated multicast MBS session. + +If the NG-RAN supports MBS, the associated unicast QoS flow information, if provided, is not used to allocate the radio resource and CN resource for corresponding QoS flows. + +NOTE 7: UE join request via PDU Session signalling will fail if NG-RAN rejects the PDU Session Resource setup request (e.g. due to the number of UEs reaching a limit). + +7. [Conditional] If shared tunnel has not been established for the multicast MBS session towards the NG-RAN node, the procedures in clause 7.2.1.4 for the establishment of shared delivery toward NG-RAN node are executed. This step is executed separately for each multicast MBS session. + +- 7a. If the MBS Session is active, the NG-RAN configures radio resources for MBS session. + +8. If the MBS Session is active, the NG-RAN node performs AN specific signalling exchange with the UE to configure the UE with radio resources for the multicast MBS session. If the NG-RAN does not support MBS and the MBS Session is active, radio resources are reconfigured for unicast transmission of the MBS data over the associated PDU session. As part of the AN specific signalling exchange, the N1 SM container (PDU Session Modification Command) is provided to the UE. + +9. The NG-RAN node sends the PDU session modification response. + +If the MBS is not supported by NG-RAN, the accepted unicast QoS flow is included in the N2 SM information. If the MBS is supported by NG-RAN, the N2 SM information further includes the indication of supporting MBS. + +10. The AMF invokes Nsmf\_PDUSession\_UpdateSMContext request ([N2 SM information]) to the SMF. + +Per the indication of whether the NG-RAN supports MBS, the SMF determines whether 5GC Individual MBS traffic delivery is used for multicast data transmission. + +NOTE 8: If the shared tunnel is used, no interaction with UPF is needed for the indicated multicast MBS session + +[Conditional] This step is used for 5GC Individual MBS traffic delivery, if the related NG-RAN does not support MBS. If a shared tunnel between the UPF (PSA) and MB-UPF for 5GC Individual MBS traffic delivery has not yet been established by the SMF for the multicast MBS session, steps 11a to 11d are executed. Step 11e is executed irrespective of that. + +- 11a. The SMF contacts the UPF to request the creation of a tunnel and provides the MBS Session ID. The UPF indicates to the SMF whether the tunnel for this multicast MBS session is newly allocated (as there can be multiple SMFs interacting with the same UPF for the same multicast MBS Session). + +If the UPF determines to use unicast transport over N19mb, the UPF allocates a DL N19mb Tunnel endpoint for the multicast MBS session if the SMF request is the first one to allocate DL N19mb Tunnel endpoint for the multicast MBS Session in the UPF. The UPF includes the DL Tunnel Info in the response to the SMF. The DL tunnel info includes the downlink tunnel ID and the UPF address. + +If the UPF determines to use multicast transport over N19mb, the UPF joins the multicast distribution if the SMF request is the first one for the MBS Session in the UPF. Steps 11b to 11d are skipped. + +- 11b. If the UPF indicates the DL N19mb Tunnel is newly allocated, the SMF invokes Nmbsmf\_MBSSession\_ContextUpdate request (MBS Session ID, [DL tunnel info]) towards the MB-SMF for establishing the multicast MBS session transport between MB-UPF and UPF. +- 11c. If the DL tunnel info of the UPF is received, the MB-SMF configures the MB-UPF to transmit the multicast MBS session data towards UPF using the possibly received downlink tunnel ID. +- 11d. The MB-SMF responds to the SMF through Nmbsmf\_MBSSession\_ContextUpdate response (MBS Session ID, [multicast DL tunnel info]). If the UPF DL tunnel info for unicast transport is not received by the MB-SMF, multicast transport between MB-UPF and UPF is to be used, and the MB-SMF includes the downlink tunnel information with the low layer transport multicast address for the multicast MBS session. +- 11e. The SMF configures the UPF to forward the received multicast MBS session data within the PDU session. (This step may be combined with step 11a). + +12. The SMF responds to the AMF with Nsmf\_PDUSession\_UpdateSMContext response message. + +13. The MB-UPF receives multicast PDUs, either directly from the content provider or via the MBSTF that can manipulate the data. + +Steps 14 to 16 are for 5GC Shared MBS traffic delivery: + +14. The MB-UPF sends multicast PDUs in the N3mb tunnel associated to the multicast MBS session to the NG-RAN. There is only one tunnel per multicast MBS session per MBS service area and NG-RAN node, i.e. all the UEs which have joined the multicast MBS session via the NG-RAN node share this tunnel for reception of the multicast MBS session data. + +15. Void. + +16. The NG-RAN transmits the multicast MBS session data to the UE(s) via the MBS Radio Bearer using either PTP or PTM transmission. + +In this step or at later stage, the NG-RAN may determine to apply delivery enabling reception by UEs in RRC\_INACTIVE state for the MBS session, as defined in clause 6.17. + +NOTE 9: Whether and when the NG-RAN determine to apply delivery enabling reception by UEs in RRC\_INACTIVE state for the MBS session as defined in clause 6.17 is to be decided by NG-RAN. + +Steps 17 to 19 are for 5GC Individual MBS traffic delivery: + +17. The MB-UPF sends multicast PDUs in the N19mb tunnel associated to the multicast MBS session to the UPF. There is only one tunnel per multicast MBS session and destination UPF, i.e. all associated PDU sessions served by the destination UPF share this tunnel. +18. The UPF forwards the multicast data towards the NG-RAN via unicast (i.e. in the N3 tunnel of the associated PDU Session). +19. The NG-RAN forwards the multicast MBS session data to the UE via unicast (i.e. over the radio bearer(s) corresponding to the associated QoS flow(s) of the associated PDU Session). + +NOTE 10: Details of the DL MBS data transmission are described in clause 6.7. + +NOTE 11: When the MBSF is involved in the multicast MBS session, the tunnel between MBSTF and MB-UPF has been established in the MBS session creation procedure. + +#### 7.2.1.4 Establishment of shared delivery toward RAN node + +In the following cases, the shared tunnel for shared delivery is established between the NG-RAN and MB-UPF: + +- The first UE is included in the context of the MBS session in the NG-RAN. + +NOTE 1: When the multicast MBS session is inactive, if there is at least one UE joining the multicast MBS session is in RRC-CONNECTED state in the NG-RAN, the shared delivery is not released. + +NOTE 2: Share delivery establishment procedures are used when MBS supporting NG-RAN node(s) get involved in the multicast MBS session regardless of the state of the multicast MBS session. + +- Handover to the target NG-RAN when the shared delivery tunnel is not established in the target RAN node for this multicast MBS session. + +![Sequence diagram showing the establishment of shared delivery toward NG-RAN node. The diagram involves four entities: NG-RAN, AMF, MB-SMF, and MB-UPF. The sequence of messages is: 1. NG-RAN decides to establish shared delivery; 2. NG-RAN sends N2 MBS message to AMF; 3a. AMF sends Nmbsmf_MBSSession_ContextUpdate request to MB-SMF; 3b. AMF stores RAN node information; 4. MB-SMF sends N4mb Session Modification to MB-UPF; 5. MB-SMF stores AMF information; 6. MB-SMF sends response to AMF; 7. AMF sends N2 MBS message to NG-RAN.](7355f66b8620d44cf566215621addb74_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + + Note left of NG-RAN: 1. Decide to establish shared delivery for a multicast MBS session + NG-RAN->>AMF: 2. N2 MBS message () + AMF->>MB-SMF: 3a. Nmbsmf_MBSSession_ContextUpdate request + Note right of AMF: 3b. Store information of RAN node for the multicast MBS session + MB-SMF->>MB-UPF: 4. N4mb Session Modification + Note right of MB-SMF: 5. Store information of AMF for the multicast MBS session + MB-SMF->>AMF: 6. Nmbsmf_MBSSession_ContextUpdate response + AMF->>NG-RAN: 7. N2 MBS message () + +``` + +Sequence diagram showing the establishment of shared delivery toward NG-RAN node. The diagram involves four entities: NG-RAN, AMF, MB-SMF, and MB-UPF. The sequence of messages is: 1. NG-RAN decides to establish shared delivery; 2. NG-RAN sends N2 MBS message to AMF; 3a. AMF sends Nmbsmf\_MBSSession\_ContextUpdate request to MB-SMF; 3b. AMF stores RAN node information; 4. MB-SMF sends N4mb Session Modification to MB-UPF; 5. MB-SMF stores AMF information; 6. MB-SMF sends response to AMF; 7. AMF sends N2 MBS message to NG-RAN. + +Figure 7.2.1.4-1: Establishment of shared delivery toward NG-RAN node + +1. A NG-RAN node decides to establish shared delivery for a multicast MBS session when it serves at least one UE within the multicast MBS session. For location dependent services, the NG-RAN node needs to establish shared delivery for the location dependent contents of a multicast MBS session if it serves at least one UE assigned to an MBS Session ID and Area Session ID. +2. The NG-RAN sends an N2 MBS Session request message (MBS Session ID, [Area Session ID], N2 SM information ([unicast DL tunnel Info])) towards the AMF. + +If the NG-RAN node is configured to use unicast transport for the shared delivery, it allocates a GTP tunnel endpoint and provides the unicast DL tunnel Info in the request, which includes the GTP tunnel endpoint and NG-RAN node address. For location dependent MBS services, the NG-RAN node also provides the Area Session ID. + +3. The AMF selects the MB-SMF serving the multicast MBS session, e.g. using the NRF discovery service or locally stored information. It invokes Nmbsmf\_MBSSession\_ContextUpdate request (MBS Session ID, [Area Session ID], N2 SM information, NG-RAN Node ID) to the MB-SMF. + +The AMF stores the information of the NG-RAN nodes (e.g. NG-RAN Node ID) for the subsequent signaling related to the multicast MBS Session. + +4. [Conditional] If the MB-SMF receives the unicast DL tunnel Info in step 3 in a deployment where NG-RAN nodes share a common user plane entity, the MB-SMF only establishes the shared tunnel towards the DL GTP tunnel endpoint if the shared tunnel has not yet been established (as determined based on the stored DL GTP Tunnel endpoint(s) for the MBS session). The MB-SMF also stores the received DL GTP Tunnel and corresponding NG-RAN Node ID for the MBS session. + +To establish the shared tunnel towards the DL GTP tunnel endpoint, the MB-SMF configures the MB-UPF to send multicast data for the multicast MBS session (or location dependent content of the multicast MBS session if an Area Session ID was received) towards that GTP tunnel endpoint via unicast transport. + +5. The MB-SMF stores the information of the AMF (e.g. AMF ID) in the MBS Multicast MBS session context (or location dependent part of the Multicast MBS Session Context if an Area Session ID was received) to enable subsequent signalling towards that AMF. +6. The MB-SMF sends Nmbsmf\_MBSSession\_ContextUpdate response (MBS Session ID, [Area Session ID], N2 SM information ([TMGI], multicast QoS flow information, session state (Active/Inactive), [multicast DL tunnel Info], [MBS service areas])) to the AMF. If the MB-SMF did not receive unicast DL tunnel Info in step 3, it provides the multicast DL tunnel info that includes transport multicast address (e.g. a LL SSM) and a GTP tunnel endpoint for multicast transport of the shared delivery. +7. The AMF sends an N2 MBS Session response message (MBS Session ID, [Area Session ID], N2 SM information) to the NG-RAN node. If the NG-RAN node receives the multicast DL tunnel Info of the shared delivery, it uses the transport multicast address included in the multicast DL tunnel info to join the multicast transport distribution. + +### 7.2.2 Multicast MBS Session leave and Multicast MBS Session release procedure + +#### 7.2.2.1 General + +This clause describes Multicast MBS Session leave requested by the UE or by the network. This clause also describes Multicast MBS Session release. + +#### 7.2.2.2 Multicast Session leave requested by the UE + +When the UE determines to leave the Multicast MBS session, it shall send PDU session Modification request to inform the 5GC the leaving operation. The Figure 7.2.2.2-1 describes the procedure. + +![Sequence diagram for UE initiated Multicast MBS Session leave. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF. The sequence shows the UE sending a PDU Session Modification Request, followed by various signaling steps between the AMF, SMF, UPF, MB-SMF, and MB-UPF to handle the session leave, including N4 and N2 messages, and finally the NG-RAN initiating the release of shared delivery.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + participant MB-UPF + + Note right of MB-UPF: For unicast transport + Note right of NG-RAN: 13. NG-RAN initiates the release of shared delivery (c.f. 7.2.2.4) + + UE->>AMF: 1. PDU Session Modification Request + AMF->>SMF: 2. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 3a. N4 Session Modification Request + UPF-->>SMF: 3b. N4 Session Modification Response + SMF->>MB-SMF: 4. Nmbsmf_MBSSession_ContextUpdate request + MB-SMF->>MB-UPF: 5. N4mb Session Modification + MB-UPF-->>MB-SMF: 6. Nmbsmf_MBSSession_ContextUpdate response + SMF->>AMF: 7. Nsmf_PDUSession_UpdateSMContext Response + AMF->>NG-RAN: 8. N2 Message + NG-RAN->>UE: 9. AN-specific resource modification + NG-RAN->>AMF: 10. N2 Message + AMF->>SMF: 11. Nsmf_PDUSession_UpdateSMContext Request/Response + SMF->>MB-SMF: 12. Nmbsmf_MBSSession_ContextStatusUnsubscribe Request/Response + Note right of NG-RAN: 13. NG-RAN initiates the release of shared delivery (c.f. 7.2.2.4) + +``` + +Sequence diagram for UE initiated Multicast MBS Session leave. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF. The sequence shows the UE sending a PDU Session Modification Request, followed by various signaling steps between the AMF, SMF, UPF, MB-SMF, and MB-UPF to handle the session leave, including N4 and N2 messages, and finally the NG-RAN initiating the release of shared delivery. + +**Figure 7.2.2.2-1: UE initiated Multicast MBS Session leave** + +1. The UE sends the PDU Session Modification Request when the UE determine to leave the multicast MBS Session. The PDU Session Modification Request carries leave indication and the MBS Session ID which the UE want to leave. +2. The AMF invokes Nsmf\_PDUSession\_UpdateSMContext (N1 SM container (PDU Session Modification Request)) to the SMF. +- 3a. [Conditional] If 5GC individual MBS traffic delivery is applied towards the UE, the SMF sends an N4 Session Modification Request to the UPF (PSA). The SMF reconfigures the UPF to terminate the distribution of multicast data via the PDU session. +- 3b. [Conditional] The UPF (PSA) sends an N4 Session Modification Response to the SMF. + +If there are no PDU sessions to transmit the multicast MBS session data in the UPF, and unicast transport is used over N19mb, the UPF releases the DL N19mb tunnel endpoint and informs the SMF. + +If there are no PDU sessions to transmit the multicast MBS session data in the UPF, and multicast transport is used over N19mb, the UPF leaves the multicast distribution tree of MB-UPF. + +4. [Conditional] If the UPF indicates the tunnel release (i.e. unicast transport was used), the SMF invokes Nmbsmf\_MBSSession\_ContextUpdate Request (Release, MBS Session ID, tunnel information) to release the tunnel between UPF and MB-UPF for this multicast MBS session. The MB-SMF determines whether the context update is for tunnel release or create based on whether the tunnel information exists in the multicast MBS Session Context stored in the MB-SMF or not. +5. [Conditional] If the MB-SMF determines the context update is for tunnel release, the MB-SMF request to MB-UPF to release the tunnel between UPF and MB-UPF for the multicast MBS session. +6. [Conditional] The MB-SMF responds to the SMF for step 4. +7. The SMF invokes the Nsmf\_PDUSession\_UpdateSMContext Response (PDU Session ID, N2 SM information ([MBS Session ID], [leave indication]), N1 SM container) service operation. In the N2 SM information, the MBS Session ID and the leave indication are included for informing the NG-RAN to remove the UE from this + +MBS session if 5GC Shared MBS traffic delivery method is used towards the UE. If 5GC Individual MBS traffic delivery method is used towards the UE, the N2 SM information does not include MBS related information. + +In the N2 SM information, the SMF also informs the NG-RAN to release the associated QoS Flow(s), which carry or intend to carry the multicast MBS session traffic for 5GC individual MBS traffic delivery. + +The associated QoS Flow(s) are released as defined in TS 23.502 [6] clause 4.3.3.2. + +8. The AMF send N2 message (N2 SM information, N1 SM container) to the NG-RAN +9. The NG-RAN node performs the necessary AN-specific resource modification procedure toward the UE and transports the N1 SM container received in step 7 to the UE. +10. The NG-RAN node removes the UE from this multicast MBS session and sends a N2 message to the AMF. +11. The AMF transfers the N2 message received in step 9 to the SMF via the Nsmf\_PDUSession\_UpdateSMContext service operation. + +The SMF updates the associated PDU session context, e.g. remove the MBS Session ID from the associated PDU session context. In addition, if associated QoS flow is used for the multicast MBS session, the SMF also removes the associated QoS flow information associated with the indicated multicast MBS session from the associated PDU session context. + +12. [Conditional] If the UE is the last joined one of the multicast MBS session in the SMF, The SMF also indicates that the last UE served by the SMF leaves the Multicast MBS Session, the SMF unsubscribes the notifications of the MBS Session Context status updates from the MB-SMF by invoking Nmbsmf\_MBSSession\_ContextStatusUnsubscribe service operation. The MB-SMF will no longer notify the SMF of the further context status updates of the multicast MBS session (e.g. activation, deactivation, update, release, etc.). For multicast transport between MB-UPF and content provider, if the SMF is the last remaining SMF that is subscribed for the MBS Session notification from the MB-SMF, i.e. if it is the last UE leaving the MBS session, the MB-SMF requests the MB-UPF to stop forwarding the multicast MBS session data and may request the MB-UPF to leave the multicast tree towards the AF/MBSF, if the MB-UPF joins the multicast tree when the first UE joins the MBS session. +13. [Conditional] If the UE is the last UE in this RAN node for this multicast MBS session, the NG-RAN release shared delivery between NG-RAN and MB-UPF as described in clause 7.2.2.4. + +If release of the PDU Session associated with a multicast MBS session is triggered, corresponding procedures between UE, NG-RAN, AMF, and SMF are performed as described in clause 4.3.4 of TS 23.502 [6], and SMF triggers the UE leave the multicast MBS session by performing steps 3-6 in Figure 7.2.2.2-1 for each multicast MBS session(s) associated with the PDU Session, and UE considers as left all the multicast MBS sessions associated with the PDU Session. + +NOTE: If the associated PDU Session is released, the UE leaves MBS Session(s) associated with that PDU session implicitly. To resume the reception of the related MBS service(s), the UE needs to initiate the procedures as defined in clause 7.2.1 to re-join the MBS Session(s). + +If the UE deregistration procedure is executed, corresponding procedures between UE, NG-RAN, AMF, and SMF are performed as described in clause 4.2.2.3 of TS 23.502 [6], and SMF performs steps 3-6 in Figure 7.2.2.2-1 for all multicast MBS sessions joined by the UE. When the PDU Session Release procedure or UE deregistration procedure is executed, according to the UE context, NG-RAN performs step 10 for each multicast MBS session associated with the released PDU Session(s). + +#### 7.2.2.3 Multicast session leave requested by the network or MBS session release + +This procedure applies to the following scenarios: + +1. When the MB-SMF decides to release an MBS Session: + - based on a request from the AF (directly or via the NEF/MBSF); + +In this scenario, the MB-SMF notifies the SMF of multicast session release, and the SMF initiates procedures to remove all joined UEs from the MBS session. + +2. When the SMF decides to remove a UE from an MBS session: + +- based on a request from the UDM (subscription change); or +- due to local and location dependent MBS service is described in clause 7.2.4; or +- due to network internal reasons. + +For the active MBS session, to release radio resources as early as possible, the MB-SMF may trigger Multicast Session Deactivation towards the NG-RAN as specified in steps 5-9 of clause 7.2.5.3, prior to or in parallel with triggering MBS Session Release to the SMF. + +![Sequence diagram for MBS Session Release or Multicast session leave requested by the network. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-SMF, and MB-UPF. The process starts with the MB-SMF sending a context status notify to the SMF. The SMF then decides to remove the UE from the MBS session. A dashed box indicates steps 3-7 from figure 7.2.5.2-1. The SMF sends an N1N2 message transfer to the AMF, which then sends an N2 request to the NG-RAN. The NG-RAN sends a PDU session modification command to the UE. A dashed box indicates the NG-RAN initiating the DL tunnel release. The NG-RAN sends an N2 response to the AMF, which then sends a PDUSession_UpdateSMContext request/response to the SMF.](9b9262a549828579ab904148450734f6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + participant MB-UPF + + Note right of SMF: 1a. Nmbsmf_MBSSession_ContextStatusNotify + Note right of SMF: 1b. SMF decides to remove UE from an MBS session + Note right of SMF: 2. step 3-7 of figure 7.2.5.2-1 + Note right of SMF: 3. Namf_Communication_N1N2MessageTransfer + Note right of AMF: 4. N2 Request + Note right of NG-RAN: 5. PDU Session Modification Cmd/Ack + Note right of UE: 6. AN-specific resource modification + Note right of NG-RAN: 7. NG-RAN initiate the DL Tunnel release with the MB-SMF/MB-UPF (clause 7.2.2.4) + Note right of NG-RAN: 8. N2 Response + Note right of AMF: 9. Nsmf_PDUSession_UpdateSMContext request/response + +``` + +Sequence diagram for MBS Session Release or Multicast session leave requested by the network. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-SMF, and MB-UPF. The process starts with the MB-SMF sending a context status notify to the SMF. The SMF then decides to remove the UE from the MBS session. A dashed box indicates steps 3-7 from figure 7.2.5.2-1. The SMF sends an N1N2 message transfer to the AMF, which then sends an N2 request to the NG-RAN. The NG-RAN sends a PDU session modification command to the UE. A dashed box indicates the NG-RAN initiating the DL tunnel release. The NG-RAN sends an N2 response to the AMF, which then sends a PDUSession\_UpdateSMContext request/response to the SMF. + +**Figure 7.2.2.3-1: MBS Session Release or Multicast session leave requested by the network** + +- For MB-SMF triggered MBS session release, the SMF receives Nmbsmf\_MBSSession\_ContextStatusNotify (MBS Session ID, multicast session release) from the MB-SMF with MBS Session ID. The SMF checks all joined UEs and perform step 2 to step 9 for each UE. +- The SMF decides to remove a UE from the MBS session without MBS session release (e.g. due to UE moving out of MBS service area for local or location dependent MBS service as described in clause 7.2.4). +- For UEs without activated UP, the SMF may perform the same procedure as defined in step 3-7 in clause 7.2.5.2. Alternatively, for UEs without activated UP, the SMF does not trigger message to the AMF, instead the SMF marks that the UE is to be informed of the MBS Session release. In this case, the SMF initiates PDU Session Modification to inform the UE of the MBS Session release at next UP activation of the associated PDU Session, if needed. +- For the joined UEs with UP activated, the SMF invokes Namf\_Communication\_N1N2MessageTransfer to the AMF. The N1 SM container indicates UE removed from MBS session with appropriate cause (e.g. MBS session release, out of MBS service area, etc.). In N2 SM information, the SMF informs the NG-RAN to remove the UE from the MBS session. If there are associated QoS Flow(s) for individual delivery, the SMF also releases those QoS Flow(s) as specified in TS 23.502 [6] clause 4.3.3.2. +- The AMF sends N2 Request to the NG-RAN. +- The NG-RAN transports the N1 SM container (PDU Session Modification Command (MBS Session ID, UE removed from MBS session with appropriate cause)) to the UE. + +6. The NG-RAN performs radio resource modification. If there are no joined UEs in the MBS session, the NG-RAN releases the radio resources. +7. If there are no joined UEs in the MBS session, for unicast transport of N3mb, the NG-RAN initiates the DL tunnel release towards MB-UPF via AMF and MB-SMF. For multicast transportation of N3mb, the NG-RAN performs IGMP/MLD Leave for the MBS session. See clause 7.2.2.4 for details. +8. The NG-RAN sends N2 Response to the AMF. If there are no joined UEs in the MBS session, the MBS Session Context is removed from the NG-RAN. +9. The AMF transfers the N2 message received in step 8 to the SMF via the Nsmf\_PDUSession\_UpdateSMContext service operation. The SMF removes the UE from the MBS Session. + +#### 7.2.2.4 Release of shared delivery toward RAN node + +In the following case, the shared delivery tunnel may be released between NG-RAN and MB-UPF: + +- The last UE is excluded from the context of the multicast MBS session in the NG-RAN node; +- Handover to the target NG-RAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node during handover preparation phase known by the source NG-RAN node; +- Handover to the target E-UTRAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node; +- MBS session deletion. + +NOTE: When the multicast MBS session is inactive, the shared delivery is not released if there is at least one UE is in RRC-CONNECTED state for this multicast MBS session. + +![Sequence diagram illustrating the release of shared delivery toward RAN node. The diagram shows interactions between NG-RAN, AMF, MB-SMF, and MB-UPF. The process starts with the NG-RAN deciding to release shared delivery (Step 1). It then sends an N2 MBS session release Request to the AMF (Step 2). The AMF sends an Nmbsmf_MBSSession_ContextUpdate request to the MB-SMF (Step 3). The MB-SMF sends an N4mb session modification/release to the MB-UPF (Step 4). The MB-UPF sends an Nmbsmf_MBSSession_ContextUpdate response back to the AMF (Step 5). The AMF then removes the stored information of the RAN node for the multicast MBS session (Step 6). Finally, the AMF sends an N2 MBS session release response back to the NG-RAN (Step 7).](ff7977984f2552f326b2089d7595fff3_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + Note left of NG-RAN: 1. Decide to release shared delivery for a multicast MBS session + NG-RAN->>AMF: 2. N2 MBS session release Request () + AMF-->>MB-SMF: 3. Nmbsmf_MBSSession_ContextUpdate request + MB-SMF-->>MB-UPF: 4. N4mb session modification/release + MB-UPF-->>AMF: 5. Nmbsmf_MBSSession_ContextUpdate response + Note right of AMF: 6. remove the stored Information of RAN node for the Multicast MBS session + AMF-->>NG-RAN: 7. N2 MBS session release response () + +``` + +Sequence diagram illustrating the release of shared delivery toward RAN node. The diagram shows interactions between NG-RAN, AMF, MB-SMF, and MB-UPF. The process starts with the NG-RAN deciding to release shared delivery (Step 1). It then sends an N2 MBS session release Request to the AMF (Step 2). The AMF sends an Nmbsmf\_MBSSession\_ContextUpdate request to the MB-SMF (Step 3). The MB-SMF sends an N4mb session modification/release to the MB-UPF (Step 4). The MB-UPF sends an Nmbsmf\_MBSSession\_ContextUpdate response back to the AMF (Step 5). The AMF then removes the stored information of the RAN node for the multicast MBS session (Step 6). Finally, the AMF sends an N2 MBS session release response back to the NG-RAN (Step 7). + +Figure 7.2.2.4-1: Release of shared delivery toward RAN node + +1. A RAN node decides to release shared delivery for a multicast MBS session, e.g. because it no longer serves at least one UE within the multicast MBS session. For location dependent services, the NG-RAN node may release shared delivery for the location dependent contents of a multicast MBS session if it no longer serves at least one UE assigned to an MBS Session ID and Area Session ID. +2. The NG-RAN node sends N2 MBS Session release request (MBS Session ID, [Area Session ID], [N2 SM information ([GTP tunnel info], release indication)])) to the AMF. For location dependent services, the NG-RAN node also provides the Area Session ID. The RAN node includes the unicast DL tunnel info if unicast + +transport is used for the shared delivery. If the NG-RAN node was configured to use multicast transport for the 5GC Shared MBS traffic delivery, the NG-RAN node does not include the N2 SM information in the message. + +3. [Conditional] If the N2 SM information is received or it is the last RAN node controlled by the AMF serving the multicast MBS session, the AMF invokes Nmbsmf\_MBSSession\_ContextUpdate request (MBS Session ID [Area Session ID], [leave indication], [N2 SM information ([DL GTP tunnel endpoint ID])], NG-RAN Node ID) to the MB-SMF corresponding to the MB-SMF ID stored in the AMF for the MBS Session ID. If it is the last RAN node controlled by the AMF serving the multicast MBS session identified by the MBS Session ID or both the MBS Session ID and Area Session ID (if exists), the leave indication is included. +4. [Conditional] If unicast transport was used towards the NG-RAN node, the MB-SMF determines whether the context update is for tunnel release or create based on the release indication in the N2 container. If the MB-SMF determines the context update is for tunnel release, , it performs the following: + +If the unicast transport was used towards the NG-RAN in a deployment where NG-RAN nodes share a common user plane entity, the MB-SMF removes the received NG-RAN Node ID and possibly DL GTP tunnel endpoint from the stored NG-RAN Node ID(s) for the DL GTP tunnel endpoint for the MBS session, and checks whether the DL GTP tunnel is in use by other NG-RAN nodes based on the stored NG-RAN Node ID(s) for DL GTP tunnel endpoint for the MBS session. + +For the deployment where NG-RAN nodes do not share a common user plane entity, the DL GTP tunnel will not be used by other NG-RAN nodes. + +If the related DL GTP tunnel is not in use by other NG-RAN nodes the MB-SMF sends N4mb Session Modification to the MB-UPF to release the N3mb tunnel used for the multicast MBS session (or location dependent content of the multicast MBS session if an Area Session ID was received) towards that NG-RAN node using the received GTP tunnel info. + +5. [Conditional] The MB-SMF responses to the AMF with MBS Session ID and Area Session ID if received. If leave indication is received, the MB-SMF also removes the information of the AMF from the context of the multicast MBS session. +6. The AMF removes the information of the RAN node from the context of the multicast MBS session (or location dependent part of the multicast MBS session if an Area Session ID was received). +7. The AMF sends an N2 MBS Session release response (MBS Session ID, [Area Session ID]) to the RAN node. The NG-RAN node deletes the GTP tunnel info (if unicast transport is used for the shared delivery) or sends IGMP/MLD leave message to leave the multicast distribution tree (if multicast transport is used for the shared delivery). The NG-RAN node releases local resources for the multicast MBS session. + +### 7.2.3 Mobility Procedures for MBS + +#### 7.2.3.1 General + +UE may move from one NG-RAN node to another NG-RAN node after UE has joined the MB Session. There are various mobility scenarios possible, depending on whether one of the involved NG-RAN nodes supports MBS. + +During an active MBS Session, mobility between an NG-RAN supporting MBS and an NG-RAN node not supporting MBS requires the mobility procedure to provide the appropriate MBS traffic delivery method at the target NG-RAN node. + +#### 7.2.3.2 Xn based handover from MBS supporting NG-RAN node + +This clause describes an Xn based handover with MBS traffic delivered to the UE at the source NG-RAN node supporting MBS. + +![Sequence diagram for Xn based handover with MBS Session. Lifelines: UE, Source NG-RAN, Target NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF. The diagram shows the flow of messages during a handover, including preparation, execution, and resource establishment for MBS traffic delivery.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + participant MB-UPF + + Note over Source NG-RAN, Target NG-RAN: 0a. Handover preparation + Note over Source NG-RAN, Target NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF: 0b. Establishment of resources for 5GC Shared MBS traffic delivery (c.f. 7.2.1.4) + Note over UE, Source NG-RAN, Target NG-RAN: 0c. Handover execution + + Target NG-RAN->>AMF: 1. Path Switch Request + AMF->>SMF: 2. Nsmf_PDUSession_UpdateSMContext request + Note right of SMF: Case A) Target NG-RAN supports 5G MBS + SMF->>UPF: 3. N4 Session Modification + Note right of SMF: Case B) Target NG-RAN does not support 5G MBS + Note right of SMF: 4. Establishment of 5GC Individual MBS traffic delivery (Step 11 in clause 7.2.1.3) + Source NG-RAN->>Target NG-RAN: End Marker + Target NG-RAN->>Source NG-RAN: End Marker + SMF->>AMF: 5. Nsmf_PDUSession_UpdateSMContext response + AMF->>Target NG-RAN: 6. Path Switch Request ACK + +``` + +Sequence diagram for Xn based handover with MBS Session. Lifelines: UE, Source NG-RAN, Target NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF. The diagram shows the flow of messages during a handover, including preparation, execution, and resource establishment for MBS traffic delivery. + +**Figure 7.2.3.2-1: Xn based handover with MBS Session** + +The following additions apply compared to clause 4.9.1.2 of TS 23.502 [6]: + +##### Before Handover: + +The source NG RAN has been provided with MBS Session Resource information (including the MBS Session ID and multicast QoS flow information) and the UE Context information contains a mapping information within the PDU Session Resource associated with the MBS Session Resource, e.g. including mapped unicast QoS Flows associated with the multicast QoS flow(s) of the MBS Session Resource. + +##### Handover Preparation Phase: + +At Xn handover, the target NG-RAN is provided with MBS session information by the source NG-RAN which causes: + +- an MBS non-supporting target NG-RAN node to prepare the unicast resources according to associated QoS flow(s) information. +- an MBS supporting target NG-RAN node to allocate to the UE shared NG-RAN resources according to the MBS session information. If the 5GC Shared MBS traffic delivery for the indicated multicast MBS Session has not been established in target NG-RAN, target NG-RAN triggers setup of the resources for the 5GC Shared MBS traffic delivery, see clause 7.2.1.4 for details. + +1. Target NG-RAN to AMF: the target NG-RAN sends N2 Path Switch Request to AMF. + +The target NG-RAN node, if MBS-capable, indicates it supports of MBS to SMF in N2 SM information. Per the received N2 SM information, the SMF knows whether the target NG-RAN node supports MBS and determines the delivery method, i.e. whether the 5GC Shared MBS traffic delivery or 5GC Individual MBS traffic delivery is used for MBS data transferring. + +The SMF differentiates two cases: + +Case A) The target NG-RAN supports MBS. Step 3 applies and step 4 is skipped. + +3. SMF to UPF: The SMF invokes N4 Session Modification procedure with the UPF (PSA) only for unicast PDU Session. + +Case B) The target NG-RAN does not support MBS. Step 3 is skipped, step 4 applies. + +- This step is same as described in step 11 of clause 7.2.1.3. + +The details of how to perform data forwarding refers to clause 7.2.3.5. + +- SMF to AMF: The SMF responds to AMF through Nsmf\_PDUSession\_UpdateSMContext response. +- AMF to target NG-RAN: The AMF sends the path switch Ack to target NG-RAN. + +#### 7.2.3.3 N2 based handover from MBS supporting NG-RAN node + +This clause describes the N2 based handover with MBS traffic delivered to the UE at the source NG-RAN node supporting MBS. + +![Sequence diagram for N2 based handover with MBS Session. The diagram shows the interaction between UE, Source NG-RAN, Target NG-RAN, S-AMF, T-AMF, SMF, UPF (PSA), MB-SMF, and MB-UPF. The process involves handover preparation, resource establishment for shared MBS traffic, and subsequent data forwarding and session updates.](45578bd3ed11d45af63ce00e28bab2f8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant S-AMF + participant T-AMF + participant SMF + participant UPF (PSA) + participant MB-SMF + participant MB-UPF + + Note left of Source NG-RAN: 1. Handover Required + Source NG-RAN->>S-AMF: 2. Namf_Communication_CreateUEContext request + S-AMF-->>T-AMF: 3. Nsmf_PDUSession_UpdateSMContext request/response + T-AMF-->>SMF: 4a. Handover Request + Note right of SMF: 4b. Establishment of resources for 5GC Shared MBS traffic delivery (Refer to clause 7.2.1.4) + SMF-->>T-AMF: 5. Handover Request ACK + T-AMF-->>S-AMF: 6. Nsmf_PDUSession_UpdateSMContext request/response + S-AMF-->>Target NG-RAN: 7. Namf_Communication_CreateUEContext response + Target NG-RAN-->>Source NG-RAN: 8. Handover Command + Source NG-RAN-->>UE: 9. Handover Command + UE-->>Source NG-RAN: 10. Handover Confirm + Source NG-RAN-->>Target NG-RAN: 11. Handover Notify + Target NG-RAN-->>SMF: 12. Nsmf_PDUSession_UpdateSMContext request + Note right of SMF: Case A) Target NG-RAN supports 5G MBS + SMF-->>UPF (PSA): 13. N4 Session Modification + Note right of SMF: Case B) Target NG-RAN does not support 5G MBS + Note right of SMF: 14. Establishment of 5GC Individual MBS traffic delivery (Step 11 in clause 7.2.1.3) + Source NG-RAN-->>Target NG-RAN: End Marker + Source NG-RAN-->>UPF (PSA): End Marker Direct Data Forwarding + Source NG-RAN-->>UPF (PSA): End Marker Indirect Data Forwarding + SMF-->>T-AMF: 15. Nsmf_PDUSession_UpdateSMContext response + +``` + +Sequence diagram for N2 based handover with MBS Session. The diagram shows the interaction between UE, Source NG-RAN, Target NG-RAN, S-AMF, T-AMF, SMF, UPF (PSA), MB-SMF, and MB-UPF. The process involves handover preparation, resource establishment for shared MBS traffic, and subsequent data forwarding and session updates. + +Figure 7.2.3.3-1: N2 based handover with MBS Session + +The following additions apply compared to clause 4.9.1.3 of TS 23.502 [6]): + +- Source NG-RAN to S-AMF: Handover Required (RAN container (MBS Session information, associated PDU session information, [associated QoS flow information and corresponding multicast QoS flow information])). +- [Conditional] S-AMF to T-AMF: The T-AMF is provided with associated PDU Session information and the MBS session related information. +- T-AMF and SMF(s): T-AMF interacts with SMF via Nsmf\_PDUSession\_UpdateSMContext request/response. In the response sent by SMF, multicast MBS session related information (i.e. MBS session ID and optionally the mapping between the multicast QoS flow(s) and associated QoS flow(s)), is included in the N2 SM information. +- T-AMF to Target NG-RAN: The Target NG-RAN prepares the radio resource based on the received information: + +- If the Target NG-RAN does not support MBS, the MBS Session related information is not used. The Target NG-RAN uses the associated PDU Session information to allocate resource to deliver MBS data. The MBS data are transmitted via the associated QoS flows within the associated PDU Session. +- If the Target NG-RAN supports MBS, the Target NG-RAN uses the multicast MBS Session related information to allocate RAN resources to deliver the MBS data. If 5GC Shared MBS traffic delivery for the indicated multicast MBS session has not been established towards the Target NG-RAN, the Target NG-RAN initiates the shared delivery establishment towards the MB-SMF via AMF as described in clause 7.2.1.4. + +##### 5. Target NG-RAN to T-AMF: The target NG-RAN sends Handover Request Ack to T-AMF. + +The target NG-RAN node, if MBS-capable, indicates it supports MBS to SMF in N2 SM information. Per the received N2 SM information, the SMF knows whether the target NG-RAN node supports MBS and determines the delivery method, i.e. whether the 5GC Shared MBS traffic delivery or 5GC Individual MBS traffic delivery is used for MBS data transferring. + +##### 12. T-AMF to SMF: The AMF invokes Nsmf\_PDUSession\_UpdateSMContext request towards SMF, the message includes the received N2 SM information received from the target NG-RAN. + +###### 13-14. Same as described in steps 3-4 of clause 7.2.3.2. + +The details of how to perform data forwarding, refers to clause 7.2.3.5. + +##### 15. SMF to T-AMF: The SMF sends the Nsmf\_PDUSession\_UpdateSMContext Response to the T-AMF. + +#### 7.2.3.4 Xn/N2 based handover from non-MBS supporting NG-RAN node + +When the UE has joined the multicast MBS session and the source NG-RAN node does not support MBS, the 5GC Individual MBS traffic delivery method is used for the multicast MBS session data delivery. When the Xn/N2 based handover procedure is triggered, the UE is handed over to the target NG-RAN node per existing Xn /N2 based handover procedure defined in TS 23.502 [6]. + +The following applies for an Xn based handover from an NG-RAN node not supporting 5G MBS: + +- The source NG-RAN node requests the associated QoS Flow(s) in the associated PDU session to be handed over to the target NG-RAN node. +- In the Path Switch Request message, the target NG-RAN node, if MBS-capable, indicates it supports MBS to the SMF in the N2 SM information. +- After successful handover, if the target NG-RAN node supports MBS, the SMF triggers modification of the associated PDU Session at the target NG-RAN node by including the multicast MBS session related information in N2 SM Information as described in step 7 of clause 7.2.1.3, which may trigger the target NG-RAN node to initiate establishment of shared delivery as described in clause 7.2.1.4. NG-RAN provides the response to the request for the modification of the PDU session when the shared delivery of the MBS session data to the related UE (if applicable) is available +- Based on the response of PDU session modification procedure, the SMF changes the MBS session data delivery method from 5GC Individual MBS traffic delivery method to 5GC shared MBS traffic delivery method, and sends N4 Session modification message to UPF to configure UPF to not forward the received multicast MBS session data via the associated PDU Session. If there are no multicast MBS session data forwarding via the associated PDU session(s) needed, the SMF may also release the shared tunnel between the UPF and MB-UPF. + +The following applies for an N2 based handover from an NG-RAN node not supporting MBS: + +- During handover preparation phase, the SMF includes the multicast MBS session related information in N2 SM Information as described in step 7 of clause 7.2.1.3 and sends it to the target NG-RAN. The target NG-RAN, if MBS-capable, indicates it supports MBS to SMF in N2 SM information. If the target NG-RAN node supports MBS, the target NG-RAN node adds the UE into the MBS Session Context. If 5GC Shared MBS traffic delivery for the indicated multicast MBS session has not been established towards the target NG-RAN, the target NG-RAN uses the multicast MBS Session related information to allocate RAN resources to deliver the MBS data and initiates the shared delivery establishment towards the MB-SMF as described in clause 7.2.1.4. +- Based on the received MBS support information in N2 SM information from the target NG-RAN, the SMF determines the MBS data delivery method for the multicast MBS session. The SMF configures UPF to not + +forward the received multicast service data to the associated PDU Session via N4 Session modification message, i.e. SMF changes 5GC individual MBS traffic delivery to 5GC shared MBS traffic delivery. If there are no multicast MBS session data forwarding via the associated PDU session(s), the SMF may also release the shared tunnel between the UPF and MB-UPF. + +#### 7.2.3.5 Minimization of data loss + +To minimize data loss of a multicast MBS session during the handover procedure the following functions apply: + +- For each MBS QoS flow, the MB-UPF adds a sequence number in each data packet of the MBS session sent by the MB-UPF and forwarded to all related NG-RAN nodes and UPFs via GTP-U tunnel. When the UPF forwards the received MBS data packet, the sequence number shall not be changed. +- If both the source NG-RAN node and target NG-RAN node support MBS, to minimize data loss of the MBS session either of, or a combination of, the following methods may be applied, as specified in TS 38.300 [9]: + - Data may be forwarded from source NG-RAN node to target NG-RAN node. In handover preparation phase, the MBS progress information (i.e. PDCP number) is exchanged between source NG-RAN node and target NG-RAN node. + - NG-RAN nodes share a common user plane entity, denoted as shared NG-U termination in TS 38.300 [9], which allows the allocation of identical PDCP numbers to MBS users data when delivered to UEs in cells served by different NG-RAN nodes. +- If source NG-RAN node supports MBS and target NG-RAN node does not support MBS, the multicast MBS session data is forwarded from source NG-RAN node to target NG-RAN node via data forwarding tunnels allocated by the target NG-RAN node associated with the mapped unicast QoS flows within the associated PDU session according to the data forwarding mechanism defined in TS 23.502 [6]. +- If source NG-RAN node does not support MBS and target NG-RAN node supports MBS, for Xn/N2 handover, the multicast MBS session data is forwarded to the target NG-RAN node as the data forwarding mechanism defined in TS 23.502 [6]. Directly after the handover the target NG-RAN node thus still receives MBS session data via individual delivery. The UPF forwards multicast MBS session data within the associated PDU session which includes the sequence number received from the MB-UPF to the target NG-RAN node. Shared delivery of MBS data towards the target RAN node is being established as described in clause 7.2.1.4 and the target RAN node receives sequence numbers as part of the MBS data with sequence numbers via shared delivery. + +NOTE: For N2 handover, the detail mechanism of how to transmit the received forwarded multicast MBS session data to UE is defined by RAN WGs. + +#### 7.2.3.6 Xn/N2 based handover for inactive MBS session + +If the MBS session is in Inactive state, the following differences apply as compared to the handover procedures for the MBS session in Active state: + +- The target NG-RAN is provided with the MBS session ID, but is not provided with Active MBS Session Information by the source NG-RAN as specified in TS 38.423 [24] and in TS 38.413 [15]. +- For Xn/N2 based handover, the information that MBS session is Inactive state is implied by the lack of Active MBS Session Information provided from the source RAN node towards the target RAN node. +- For the MBS supporting NG-RAN node, the target NG-RAN establishes the shared tunnel with the MB-UPF as usual, if it hasn't been established before. However, as the MBS session is in Inactive state, the NG-RAN node will not allocate related radio resource. + +NOTE 1: The MBS Session Inactive state is provided by MB-SMF to NG-RAN in the N2 SM information in step 7 of clause 7.2.1.4. + +- After a handover to a target NG-RAN node not supporting MBS, the SMF removes the associated QoS flow(s) information. + +NOTE 2: Whether the associated QoS Flow(s) are removed from UE, NG-RAN, or only resource in NG-RAN is removed is up to implementation. + +#### 7.2.3.7 Connection Resume in RRC Inactive procedure + +If an MBS session is in Inactive state, the UE may be in CM-CONNECTED with RRC Inactive state. If an MBS Session is in Active state, the UE may also be in CM-CONNECTED with RRC Inactive state as specified in clause 16.10.5.2 of TS 38.300 [9]. + +The UE may resume the connection in a different NG-RAN node as specified in clauses 4.8.2.2 and 4.8.2.2a of TS 23.502 [6], with following enhancement when the context retrieval is successful: + +- For an MBS supporting NG-RAN: + - if the UE context retrieved from the last serving NG-RAN includes MBS session information and the NG-RAN node has not yet established the 5GC Shared MBS traffic delivery for the MBS session, the NG-RAN establishes the 5GC Shared MBS traffic delivery as specified in clause 7.2.1.4. The NG-RAN then sends Path Switch Request indicating the MBS support information; + - if the UE context retrieved from the last serving NG-RAN does not include MBS session information, Path Switch Request sent from NG-RAN includes the MBS support information. Based on the MBS support information, the SMF, after acknowledging the path switch request, provides the MBS related information and if applicable the associated QoS flow(s) information to the NG-RAN as specified in clause 7.2.1.3. The NG-RAN establishes the 5GC Shared MBS traffic delivery as specified in clause 7.2.1.4. +- For an MBS non-supporting NG-RAN, Path Switch Request sent from NG-RAN does not include the MBS support information. If the MBS session is still inactive, the SMF, after acknowledging the path switch request, removes the associated QoS flow(s) information if it was provided before. + +If the UE context retrieval fails, the UE is moved into RRC IDLE state as per TS 38.300 [9]. The UE initiates the NAS signalling recovery including activating PDU Session(s) (see TS 24.501 [25]). When the associated PDU session(s) is activated during registration procedure (see clause 4.2.2.2.2 of TS 23.502 [6]) or service request procedure (see clause 4.2.3.2 of TS 23.502 [6]), clause 7.2.8 applies. + +NOTE: As specified in clause 4.2.2.2.2 of TS 23.502 [6], parts of the service request procedure can also be executed during the Mobility Registration Update procedure. + +###### 7.2.3.8 Mobility procedures to enable delivery of multicast MBS session data to UEs in RRC\_INACTIVE state + +#### 7.2.3.8.1 General + +The procedures in clauses 7.2.3.2, 7.2.3.3, 7.2.3.4, 7.2.3.6 and 7.2.3.7 apply with the following additions: + +- If the MBS assistance information is available at the SMF for an MBS session that the UE joined, + - If there is signalling of MBS session related information from SMF to target RAN node, the SMF includes MBS Assistance Information in the N2 SM information. + - For N2-based handover, when the SMF provides the MBS session related information as part of the associated PDU Session context data as specified in the existing procedures, the SMF also includes the MBS Assistance Information in the N2 SM information. + - For Xn-based handover or Connection Resume from a non-MBS supporting source RAN node towards an MBS supporting target RAN node, the SMF provides MBS session related information as part of the associated PDU Session context data as specified in the existing procedures and the SMF also includes the MBS Assistance Information in the N2 SM information. + - For Xn-based handover or Connection Resume from an MBS supporting source RAN node towards an MBS supporting target RAN node, depending on configuration, the SMF may provide the MBS Assistance Information. + - For Xn-based handover or Connection Resume, the MBS session information transferred from source NG-RAN towards target NG-RAN also include MBS assistance information for the MBS session if such information is available at the source RAN node as specified in TS 38.300 [9]. + +NOTE 1: In deployments where not all the MBS supporting NG RAN nodes support delivery of multicast MBS session data to UEs in RRC\_INACTIVE state, a source NG-RAN node not supporting delivery of multicast MBS session data to UEs in RRC\_INACTIVE state will not provide MBS assistance information for the MBS session to the target NG-RAN node. + +NOTE 2: It is assumed that a RAN node not supporting delivery of multicast MBS session data to UEs in RRC\_INACTIVE state ignores the MBS assistance information for the MBS session. + +For a UE that is receiving multicast MBS data in CM-CONNECTED with RRC\_INACTIVE state, the scenarios for UE mobility are as follows: + +- UE moves to new cell within the RAN Notification Area (RNA). +- UE moves outside the current RAN Notification Area but within the current Registration Area (RA). +- UE moves out of the current Registration Area. + +#### 7.2.3.8.2 Mobility of UE in RRC\_INACTIVE state receiving MBS data within RNA + +When a UE in RRC\_INACTIVE state is receiving ongoing MBS session data and moves to a new cell within the RNA, the UE may receive the MBS session data in RRC\_INACTIVE state or resume the connection as specified in TS 38.300 [9]. + +#### 7.2.3.8.3 Mobility of UE in RRC\_INACTIVE state receiving MBS data out of RNA and within RA + +When a UE in RRC\_INACTIVE state is receiving multicast MBS session data, if the UE moves out of the RNA and within the RA, the UE resumes the connection in the same way as specified in clause 7.2.3.7. + +#### 7.2.3.8.4 Mobility of UE in RRC\_INACTIVE state receiving MBS data out of RA + +When the UE in RRC\_INACTIVE receiving multicast MBS session data, if the UE moves out of the RA, the UE initiates the Mobility Registration Update procedure to activate the associated PDU session(s) as specified in clause 4.2.2.2.2 of TS 23.502 [6]. Hence the shared delivery (if not already established) or the individual delivery can be established towards the NG-RAN node to enable delivery of multicast MBS session data to the UEs. + +### 7.2.4 Support of Local multicast service and Location dependent multicast service + +#### 7.2.4.1 General + +The clause captures the procedural enhancement to support Location dependent MBS service and the Local MBS service described in clause 6.2. + +#### 7.2.4.2 Support of location dependent multicast service + +##### 7.2.4.2.0 Creation for location dependent MBS session + +For location dependent MBS, the MBS session creation procedure is performed as defined in clause 7.1.1.2 with the following additions and difference: + +- Multiple AFs may start the same Multicast MBS session with different content in different MBS service areas. The AF (or NEF/MBSF if involved) selects MB-SMF for different MBS service areas. +- For each MBS service area, the AF creates a location dependent component of an MBS session for that service area towards the MB-SMF and provides the service area, which may be via NEF or MBSF. The MB-SMF additionally returns the Area Session ID allocated by MB-SMF in the response to a request to create a location dependent component of a Multicast MBS session, and the NEF forwards this Area Session ID to the AF. The AF provides the Area Session ID in subsequent requests related to that location dependent component of the MBS session. + +- When requesting the creation of a location dependent component of the MBS session for a service area, the AF provides an indication that the request is for the creation of a location dependent component of the MBS session. +- The NEF, if involved in the MBS Session, maps MBS service areas of external format (if any) to network internal format (list of cells, TAIs). +- MB-SMF allocates Area Session ID, and updates its NF profile towards the NRF with the MBS Session ID, MBS service area and Area Session ID. + +NOTE: For a location dependent service provided in different MBS service areas within the same SMF service area, it is assumed that one MB-SMF is used for an MBS Session. + +- The QoS of Multicast MBS session is determined based on the service requirements per MBS Session. MB-SMF assign the same QFI for MBS QoS Flow with the same QoS requirement in different MBS service areas. +- The MB-SMF configures the MB-UPF separately for each service area. The MB-SMF may select the MB-UPF based on the MBS service area. +- All MBS service area(s) of the location dependent MBS session are indicated to the UE in the Service Announcement as defined in clause 6.11. +- The AF transmits the DL media streams to MB-UPF via tunnels to differentiate the content delivered to different areas. + +#### 7.2.4.2.1 UE join location dependent Multicast MBS session and establishment procedure + +The location dependent multicast session join and establishment procedure is performed as defined in clause 7.2.1 with the following additions: + +- The location dependent Multicast MBS session is created as described in clause 7.2.4.2.0. +- The UE may have information about the location dependent multicast service including all MBS service areas of the location dependent MBS session via Service Announcement as specified in clause 7.2.4.3.1. +- If the UE determines that it is in MBS service area of the location dependent MBS session based on the information about local multicast service e.g. obtained via Service Announcement, the UE sends Join Request to join the multicast group. If the UE determines that it is outside all MBS service area of the location dependent MBS session, the UE does not send the Join Request. +- If SMF requires information about the multicast MBS Session Context for the indicated MBS Session ID, the SMF requests MB-SMF information via Nnrf\_NFDiscovery\_Request Request (MBS Session ID, UE location). The SMF should provide the TAI where the UE is located as input for the MB-SMF discovery. If the NRF does not have information about service areas for an MBS Session ID in the MB-SMF profile but obtains a TAI in combination with MBS Session ID as query parameter, the NRF ignores the TAI and provides the MB-SMF profile matching the MBS Session ID. If the TAI is not included, but the related MB-SMF include the service area, the NRF return all the MB-SMF associated with that MBS Session ID. + +NOTE 1: The AMF provides the User Location Information of the UE (cell ID and current tracking area ID) towards the SMF within Nsmf\_PDUSession\_CreateSMContext request and if the location changed also in Nsmf\_PDUSession\_UpdateSMContext request (as used for the join) as specified in clauses 4.3.2.2.1 and 4.3.3.2 of TS 23.502 [6]. + +- The NRF provides information about the MB-SMF(s) serving the Multicast MBS session at the possible indicated location. The NRF provides the service areas and Area Session IDs for the Multicast MBS session as part of the MB-SMF profile(s), via Nnrf\_NFDiscovery\_Request Response (MB-SMF profile (Area Session ID(s), MBS service area(s)). The SMF selects the MB-SMF based on the location area where the UE is residing (if the TAI is not provided to the NRF) and interacts with MB-SMF to retrieve QoS information of the multicast QoS flow(s) for the MBS Session ID and subscribes to notifications about the MBS Session ID. +- The SMF check whether the UE is inside MBS service areas of the location dependent MBS session by comparing the User Location Information of the UE provided by the AMF with the MBS service areas received from the NRF. If the UE is out of all MBS service area of the location dependent MBS session, the SMF reject the multicast session join request. + +- If the Join Request from the UE is accepted, the SMF may subscribe at the AMF using the Namf\_EventExposure service to notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. The SMF supplies all MBS service areas of the location dependent MBS session as Area Of Interest. +- The SMF requests the AMF to transfer an N2 message to the RAN node using the Nsmf\_PDUSession\_UpdateSMContext response, to provide the NG-RAN with Multicast MBS session information which additionally includes the Area Session ID. +- If the NG-RAN node supports MBS, the NG-RAN uses the received MBS Session ID and Area Session ID to determine the local Multicast MBS session context and whether the user plane for the local Multicast MBS session is already established. If the RAN determines the shared delivery is not established for the MBS Session ID and Area Session ID, the NG-RAN initiates the shared delivery establishment as specified in clause 7.2.1.4 and provides the Area Session ID, tracking area ID(s) concerning the RAN node in addition to MBS Session ID in the request for shared delivery establishment. The MB-SMF provides MBS service area information (Area Session ID(s), MBS service area(s)) associated with the same MBS session to NG-RAN in the shared delivery establishment response. MB-SMF may either provide only the service areas concerning the target RAN node or all service areas associated with the MBS session. If the MB-SMF only provides the service areas concerning the target RAN node, which includes the cell ID(s), the cell ID is included if the tracking area IDs associated with the indicated cell ID is received by the MB-SMF. +- If the NG-RAN node serving the UE does not support MBS and the UE is in the MBS service area, the SMF apply individual delivery towards the UE. The SMF configures the UPF to send data related to the Multicast MBS session and service area via individual delivery within a PDU session of the UE. The SMF additionally subscribes at the AMF using the Namf\_EventExposure service to notifications about UE location changes (e.g. for a small MBS service area), or to notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. In the latter case, the SMF supplies the service area associated with the multicast area session where the UE resides as Area Of Interest. The SMF configures separate ingress terminations at the UPF for each service area and interacts separately for each service area (providing MBS Session ID and Area Session ID) with the MB-SMF to request or terminate the distribution of data for the MBS session and service area towards the UPF. + +#### 7.2.4.2.2 Void + +#### 7.2.4.2.3 Handover procedure + +The Handover procedure for the UE is performed as defined in clause 7.2.3.2, 7.2.3.3, and 7.2.3.4 with the following additions: + +- If the UE is receiving multicast data corresponding to the MBS Session ID and Area Session ID via the 5GC Shared MBS traffic delivery from cells served by the Source NG-RAN before the handover, for the Xn Handover (comparing with the clause 7.2.3.2), the following applies: + - The Source RAN node includes MBS Session ID, Area Session ID and MBS service area associated with the cell where the UE resides to the Target RAN node. + +NOTE 1: During the handover procedure the associated QoS flow is established towards a NG RAN node not supporting MBS regardless whether the UE is still in the MBS service area associated with the original Area Session ID or not + +- If the UE is receiving multicast data corresponding to the MBS Session ID and Area Session ID from cells served by the Source NG-RAN via the 5GC Shared MBS traffic delivery before the handover, for the N2 Handover (comparing with the clause 7.2.3.3), the following applies: + - The source RAN node includes MBS session area information (MBS Session ID, Area Session ID and MBS service area associated with the cell where the UE resides) for delivery to the Target RAN node within the Source to Target transparent container in the Handover Required message. + - The SMF forwards the Source to Target transparent container and may also include MBS session area information (MBS Session ID, Area Session ID and MBS service area) to the Target RAN in Handover request. + +NOTE 2: The SMF cannot determine the UE location and a possible new service area at this stage. + +- If the UE is receiving multicast data corresponding to the MBS Session ID and Area Session ID from cells served by the Source NG-RAN via the 5GC Individual MBS traffic delivery before the Handover, for the Xn/N2 handover procedure (comparing with the clause 7.2.3.4), the following applies: + +NOTE 3: During the Xn handover procedure, the associated QoS flow is established at Target RAN side regardless whether the UE is still in the MBS service area associated with the original Area Session ID or not. + +- For the N2 handover procedure, the SMF includes MBS session area information (MBS Session ID, Area Session ID, and MBS service area) associated with the last known service area of the UE in N2 SM information to the Target RAN node in Handover Request message. +- If the target RAN node supports MBS, it determines whether to establish the resources for multicast distribution and data forwarding for the received MBS Session ID and Area Session ID, based on MBS Session ID, Area Session ID, MBS service area provided by the source RAN (if source RAN support MBS) or SMF (if source RAN not support MBS) and the target location of the UE. If UE is not in the MBS service area provided by the source RAN (if source RAN supports MBS) or SMF (if source RAN does not support MBS), the target RAN does not allocate RAN resources, including the resource for data forwarding, for the multicast MBS Session to the UE. +- If the target RAN node support MBS, when it determines the shared delivery is not established for the multicast session ID and Area Session ID, the target NG-RAN initiates the shared delivery establishment as specified in clause 7.2.1.4 and provides the Area Session ID and tracking area ID(s) concerning the RAN node in addition to MBS Session ID in the request for shared delivery establishment. The MB-SMF provides MBS session area information (Area Session ID(s), MBS service area(s)) associated with the MBS session to the NG-RAN in the shared delivery establishment reply. The MB-SMF may either provide only the service areas concerning the target RAN node or all service areas associated with the MBS session. + +NOTE 4: If the target RAN does not support MBS, the associated QoS flow is established at target RAN side during the handover procedure regardless whether the UE is still in the MBS service area associated with the original Area Session ID or not. + +- If the target RAN supports MBS, but the Source RAN does not support MBS, the SMF configures the UPF to stop sending data related to the Multicast MBS session and service area via the associated PDU session of the UE. The SMF unsubscribes at the AMF using the Namf\_EventExposure service to notifications about UE location changes, or to notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event (for an individual service area). + +NOTE 5: If the UE is still in the MBS session, the subscription for the UE entering or leaving the complete service area does not need to be changed. + +- When the AMF receives the User Location Information from target RAN node via the Path Switch Request message or Handover Notify message, the AMF provide it to the SMF. When the SMF get the User Location Information, the SMF determines the MBS service area of the UE camping cell by comparing the User Location Information received from AMF with the MBS service areas received from the NRF. The SMF uses the determined MBS service area and determined user location as follows: + - The SMF updates the Area Session ID in the locally stored the UE MBS Session Context with the corresponding Area Session ID if the Area Session ID is changed. + - If the target RAN does not support MBS, the Source RAN supported MBS, and the UE is in a service area of the MBS session, the SMF applies individual delivery towards the UE. The SMF configures the UPF to send data related to the Multicast MBS session and service area via the associated PDU session of the UE. The SMF additionally subscribes at the AMF using the Namf\_EventExposure service to notifications about UE location changes, or to notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. In the latter case the SMF supplies the service area of the multicast area session as Area Of Interest. If associated QoS flows are not yet included in the PDU session, the SMF updates the PDU session with associated QoS flows. + - If the UE has moved to another MBS service area of the MBS session: + - If the target NG-RAN node support MBS after the completion of the handover procedure, the SMF provides the MBS session related information including the new Area session ID to NG-RAN via the + +PDU Session Modification procedure. Per the received the MBS session related information, the 5GC shared delivery is established. + +- If the target NG-RAN node does not support MBS, the SMF updates the UPF to forward the MBS data packets which are received from the tunnel associated with the new Area Session ID to the target NG-RAN node. If the SMF did not configure the UPF to receive the MBS data packet from the tunnel associated with the new Area Session ID before, the SMF informs the MB-SMF of the new Area Session ID and UPF DL N19mb Tunnel information. MB-SMF configure the MB-UPF to transmit the Multicast MBS session data towards UPF using the received downlink tunnel ID. If the SMF subscribed to the "Area Of Interest" event, the SMF also updates the subscription with the new service area as "Area Of Interest". +- If the UE has moved out of all the MBS service areas of the MBS session: + - If the target NG-RAN node does not support MBS, the SMF deletes the associated QoS flow from NG-RAN and UPF after the completion of the handover. + - Per operator's policy (e.g. when a local configured timer expires since the UE left the whole MBS service area), the SMF may remove the UE from the MBS session as defined in clause 7.2.2.3. When the UE is removed from the location dependent MBS session, the SMF also unsubscribes to the AMF from the notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. + +#### 7.2.4.2.4 Activation of location dependent MBS session + +When the location dependent MBS session is activated, the MBS session is activated in the whole MBS service area of the MBS session. It is not supported that the same MBS session is in Active state in one MBS service area but in Inactive state in another MBS service area. + +NOTE: As an exception, if the MBS session contains service areas served by several different MB-SMFs, the activation is for all service areas served by the MB-SMF. + +When the MB-SMF is requested by an AF to activate the MBS session in a service area of the MBS session or the MB-UPF reports detection of data for a service area of the MBS session, the MB-SMF triggers the activation for all service areas of the MBS session that it serves, i.e. whole MBS session is activated. + +For the location dependent MBS session activation, the differences comparing to the procedure defined in clause 7.2.5.2 are as below: + +- The SMF invokes Namf\_MT\_EnableGroupReachability service operation to AMF, which includes the whole MBS service area associated with the MBS session, i.e. the sum of all MBS service area associated with the MBS Session ID regardless of the Area Session ID. +- For the UE in CM-IDLE state, when the AMF triggers the paging, it take the receiving MBS service area information into account. Only the NG-RAN nodes which are included in the MBS service area need to be triggered for paging. +- SMF checks whether the UE is in or out of the MBS service area based on the change notification or UE location information included in Nsmf\_PDUSession\_UpdateSMContext Request or Namf\_MT\_UEReachabilityInfoNotify message. Based on that information, the SMF determines how to activate the MBS session in the same way as the handling defined in clause 7.2.4.2.3 +- When the SMF provides the MBS session information to the NG-RAN nodes, it includes the MBS service area, and Area Session ID, in the N2 SM information. + +#### 7.2.4.2.5 UE location change handling within the same NG-RAN node between cells belonging to different MBS service areas during Individual delivery + +If UE has moved out of the MBS service area corresponding to the original Area Session ID, the SMF checks whether UE is in MBS service area corresponding to a new Area Session ID within the same MBS session: + +- For the case UE is out of the original MBS service area but in another MBS service area of the MBS session: + - If the RAN node does not support MBS and the MBS session is active, the SMF updates the UPF to forward the MBS data packets which are received from the tunnel associated with the new Area Session ID to the + +RAN node. If the SMF did not configure the UPF receiving the MBS data packet from the tunnel associated with the new Area Session ID before, the SMF informs the MB-SMF of the new Area Session ID and UPF DL N19mb Tunnel information. The MB-SMF configure the MB-UPF to transmit the Multicast MBS session data towards UPF using the received downlink tunnel ID. + +- The SMF updates the AMF of the area of interest event subscription by supplying the new MBS service area as Area Of Interest. +- For the case UE is out of all the MBS service areas of the MBS session: + - If RAN node does not support MBS, the SMF delete the associated QoS flow from NG-RAN and UPF. + - Per operator's policy (e.g. when a local configured timer expires since the UE left the whole MBS service area), the SMF may remove the UE from the MBS session as defined in clause 7.2.2.3. When the UE is removed from the location dependent MBS session, the SMF also unsubscribes to the AMF from the notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. +- For the case UE comes back to the MBS service area of the multicast MBS session after moving out of the whole MBS service area of the multicast MBS session, e.g. before the local configured timer expires: + - If the UE is still in the multicast MBS session, the SMF adds the associated QoS flow at NG-RAN and UPF. + +#### 7.2.4.2.6 UE location change handling by SMF + +When the SMF receives a notification about a UE location change or is becoming aware of a UE location change (e.g. during handover, Mobility Registration Update and Service Request procedures), the SMF checks whether the new UE location is inside or outside all MBS service areas of the location dependent MBS session: + +- For the case that UE is out of all MBS service area of the location dependent MBS session: + - If RAN node does not support MBS, the SMF delete the associated QoS flow from the RAN node and the UPF. + - Per operator's policy (e.g. when a local configured timer expires since the UE left the whole MBS service area of the MBS session) the SMF may remove the UE from the multicast MBS session as defined in clause 7.2.2.3. The SMF also unsubscribes to the AMF from the notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. +- For the case UE comes back to MBS service area of the location dependent MBS session after moving out of the whole MBS service area of the multicast MBS session, e.g. before the local configured timer expires: + - If the UE is still in the multicast MBS session and the multicast MBS session is in Active state, the SMF tries to activate the multicast MBS session towards the UE. + +#### 7.2.4.2.7 UE mobility within the same NG-RAN between cells belonging to different MBS service areas for shared delivery + +When the UE moves from one service area to another served by the same NG-RAN, the NG-RAN node that supports MBS handles content switching due to mobility between service areas it serves without interaction with SMF. If it is the first that UE enters a new location area the RAN node requests shared delivery from the MB-SMF for the corresponding Area Session ID. If the last UE leaves a location area the RAN node requests the termination of shared delivery from the MB-SMF for the corresponding Area Session ID. + +UE mobility can happen within the same NG-RAN between cells in or out of all the MBS service areas: + +- The NG-RAN detects whether the UE is IN or OUT of all MBS service areas of a location dependent MBS session. If the UE moves in or out of all MBS service areas of a location dependent MBS session, the NG-RAN notifies the SMF. + +NOTE: When the UE joins, the SMF subscribes to the "Area Of Interest" event, and provides the combination of all MBS service areas of location dependent MBS session as "Area Of Interest" (see clause 7.2.4.2.1). + +- When the SMF knows the UE is IN or OUT of all MBS service area of location dependent MBS session, the SMF behaves as in clause 7.2.4.2.6. + +#### 7.2.4.2.8 Void + +#### 7.2.4.2.9 Connection Resume procedure + +The Connection Resume procedure for the UE is performed as defined in clause 7.2.3.7 with the following additions: + +- For an MBS-supporting target NG RAN + - The target RAN node obtains MBS session information including an area session ID from the source RAN node (during the connection retrieval) or the SMF and initiates the shared delivery establishment (if not established yet) as specified in clause 7.2.1.4 providing that area session ID. It obtains information about location areas and related area session IDs during the shared delivery establishment. The target RAN then applies the procedures in clause 7.2.4.2.7. +- For a non MBS-supporting target NG RAN, the SMF subscribes at the AMF using the Namf\_EventExposure service to notifications about UE location changes (if not yet done), and applies the procedures in 7.2.4.2.5. + +#### 7.2.4.3 Support of local MBS for multicast + +##### 7.2.4.3.1 Local MBS service area information provided by AF + +For local multicast services, the MBS service area information is provided to the UE and the 5GC as specified in clauses 7.1.1.2 and 7.1.1.3 with the following differences and clarifications: + +- For the Service Announcement, MBS service area information is included unless it is preconfigured. +- When performing the MBS session creation request to the 5GC, the MBS service area information for a Multicast MBS session is provided by the AF unless it is preconfigured. + +##### 7.2.4.3.2 Multicast session join and session establishment procedure for local MBS + +For the case that the multicast service is only available within a limited area, the UEs outside the MBS service area are not allowed to join the multicast service. + +The Multicast MBS session join and session establishment for multicast service available within a limited area are performed as specified in clause 7.2.1.3 with the following differences and clarifications: + +- The local Multicast MBS session has been created where the AF provided the MBS service area information as specified in clause 7.2.4.3.1. +- The UE may have information about local multicast service including MBS service area via Service Announcement as specified in clause 7.2.4.3.1. +- In step 1, if the UE determines that it is in the MBS service area based on the information about local multicast service e.g. obtained via Service Announcement, the UE sends the PDU Session Modification Request (MBS Session ID) or the PDU Session Establishment Request (MBS Session ID) as a Join Request to join the multicast group. If the UE determines that it is outside the MBS service area, the UE does not send the Join Request. +- In step 3, the SMF obtains the MBS service area (i.e. Cell ID list or TAI list) of the indicated MBS session from the MB-SMF, and the SMF determines the indicated MBS session corresponds to local multicast service based on the MBS service area. +- In step 5, the SMF checks whether the UE is inside or outside the MBS service area. + - The SMF determines whether the UE is inside the MBS service area by comparing the User Location Information of the UE received from the AMF with the MBS service area received from the MB-SMF. + +NOTE 1: The AMF provides the User Location Information of the UE (cell ID and current tracking area ID) towards the SMF within Nsmf\_PDUSession\_CreateSMContext request and if the location changed also in Nsmf\_PDUSession\_UpdateSMContext request (as used for the join) as specified in clauses 4.3.2.2.1 and 4.3.3.2 of TS 23.502 [6]. + +- If the SMF detects that the UE is inside the MBS service area, the SMF continues the process of multicast session join as specified in clause 7.2.1.3 with the following additions: + - The SMF sends the UE a PDU Session Modification Command or a PDU Session Establishment Accept indicating a Join Accept as a response to the Join Request. The Joint Accept includes the MBS service area (i.e. Cell ID list or TAI list). + - The Multicast MBS session information sent by the SMF to the NG-RAN includes the MBS service area (i.e. Cell ID list or TAI list). + - If the RAN node serving the UE does not support MBS the SMF applies individual delivery towards the UE. The SMF configures the UPF to send data related to the Multicast MBS session via individual delivery within a PDU session of the UE. +- If the SMF detects that the UE is outside the MBS service area, the SMF rejects the multicast session join, so sends a Join Reject to the UE indicating that the MBS join is rejected. The Joint Reject includes the reject reason (outside of local service area) and the MBS service area (i.e. Cell ID list or TAI list). + +In this case, the MBS Session establishment (i.e. resources establishment for MBS traffic delivery) for the UE is not performed. + +NOTE 2: There may be the case that the UE determines that it is inside the MBS service area based on the geographical area information or civic address information as MBS service area information provided by the AF, so sends a Join Request but the UE is outside the MBS service area. + +NOTE 3: Which SM NAS message is used to deliver the Join Reject (e.g. PDU Session Modification Reject) is defined in stage 3 specifications. + +- If the Join Request from the UE is accepted, the SMF subscribes to the UE mobility event notification from the AMF (e.g. UE moving into or out of Area Of Interest, which is set by MBS service area), by invoking Namf\_EventExposure\_Subscribe service operation as specified in clause 5.2.2.3.2 of TS 23.502 [6]. The SMF supplies the service area associated with the Multicast MBS session as Area Of Interest. +- For the UE that received the Join Reject from the SMF, later, if the UE detects that it is inside the MBS service area based on the MBS service area provided in the Join Reject, the UE sends the PDU Session Modification Request (MBS Session ID) to join the multicast group. + +### 7.2.4.3.3 Handover procedure with local MBS session + +The Handover procedure for the UE is performed as defined in clause 7.2.3 with the following additions: + +- If the UE is camping at the Source RAN node and receiving multicast data corresponding to the MBS Session ID via the 5GC Shared MBS traffic delivery before the Handover, for Xn based handover in clause 7.2.3.2, the Source RAN node includes MBS Session ID and MBS service area to the Target RAN node during Handover Preparation phase. For N2 based handover in clause 7.2.3.3, this step corresponds to Handover Request and Handover Required message, respectively. + +NOTE: During the Xn or N2 handover procedures, if the target RAN node does not support MBS, the associated QoS flow is established at the Target RAN side regardless whether the UE is still in the MBS service area. + +- If the UE is camping at the Source RAN node and receiving multicast data corresponding to the MBS Session ID via the 5GC individual MBS traffic delivery before the Handover, for the N2 Handover in clause 7.2.3.4, the SMF includes MBS session area information (MBS Session ID and MBS service area) in N2 SM information to the Target RAN node in Handover request. +- If the Target RAN node support MBS, it determines whether to establish the resources for multicast distribution and data forwarding for MBS Session ID, based on the received MBS Session ID provided by the source RAN (if source RAN support MBS) or SMF (if source RAN not support MBS), and target location of the UE. If UE is not in the in the MBS service area provided by the source RAN (if source RAN support MBS) or SMF (if source RAN not support MBS), the Target RAN does not allocate RAN resources, including the resource for data forwarding, for the multicast MBS Session to the UE. + +- If the target RAN node support MBS, when it determines that the UE is in the MBS service area and that the shared delivery is not established for the multicast session ID, the target NG-RAN initiates the shared delivery establishment as specified in clause 7.2.1.4. +- When the AMF receives the User Location Information from target RAN node via the Path Switch Request message or Handover Notify message, the AMF provide it to the SMF. When the SMF get the User Location Information, the SMF check the MBS service area of UE camping cell by comparing the User Location Information received from AMF with the MBS service area received from the MB-SMF. The SMF uses the determined UE location and MBS service area as follows: + - The SMF determines whether the UE is outside the MBS service area by comparing the received Cell ID and tracking area ID with the MBS service area received from the MB-SMF. + - If the UE is inside the MBS service area and target RAN node does not support MBS, the SMF applies individual delivery towards the UE. If associated QoS flows are not yet included in the PDU session, the SMF updates the PDU session with associated QoS flows. If the SMF did not configure the UPF to receive the MBS data packet from the tunnel associated with the Multicast MBS session before, the SMF informs the MB-SMF of the MBS session and UPF DL N19mb Tunnel information. MB-SMF configure the MB-UPF to transmit the Multicast MBS session data towards UPF using the received downlink tunnel ID. +- If the UE is out of the service area of the MBS session: + - If the target NG-RAN node does not support MBS, the SMF deletes the associated QoS flow from NG-RAN node and the UPF after the completion of the handover procedure. + - Per operator's policy (e.g. when a local configured timer expires since the UE left the whole MBS service area of the MBS session) the SMF may remove the UE from the MBS session as defined in clause 7.2.2.3. When the UE is removed from the local MBS session, the SMF also unsubscribes to the AMF from the notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. + +#### 7.2.4.3.4 Activation of local MBS session + +For the local MBS session activation, the differences comparing to the procedure defined in clause 7.2.5.2 are as below. + +- The SMF invokes Namf\_MT\_EnableGroupReachability service operation to AMF, which include the MBS service area associated with the MBS session. +- For the UE in CM-IDLE state, when the AMF triggers the paging, it takes the received MBS service area information into account and only triggers the paging at the NG-RAN nodes which are included in the MBS service area. +- SMF checks whether the UE is in or out of the MBS service area based on the change notification or UE location information included in Nsmf\_PDUSession\_UpdateSMContext Request or Namf\_MT\_UEReachabilityInfoNotify message. Based on that information, the SMF determines how to activate the MBS session same as the handling when the SMF get the User Location Information defined in clause 7.2.4.3.3. +- When the SMF provides the MBS session information to the NG-RAN nodes, it includes the MBS service area in the N2 SM information. + +#### 7.2.4.3.5 UE location change handling by SMF + +When the SMF receives a notification about a UE location change or is becoming aware of a UE location change (e.g. during handover, Mobility Registration Update and Service Request procedures), the SMF checks whether the new UE location is inside or outside the MBS service area of the MBS session. + +- For the case UE is out of the MBS service area of the MBS session: + - If RAN node does not support MBS, the SMF delete the associated QoS flow from the RAN node and the UPF. + - Per operator's policy (e.g. when a local configured timer expires since the UE left the MBS service area of the MBS session) the SMF may remove the UE from the multicast MBS session as defined in clause 7.2.2.3. + +When the UE is removed from the local MBS session, the SMF also unsubscribes to the AMF from the notifications about the "UE moving in or out of a subscribed "Area Of Interest"" event. + +- For the case UE comes back to the MBS service area of the multicast MBS session after moving out of the MBS service area of the multicast MBS session, e.g. before the local configured timer expires: +- If the UE is still in the multicast MBS session and the multicast MBS session is in Active state, the SMF tries to activate the multicast MBS session towards the UE. + +#### 7.2.4.3.6 UE mobility within the same NG-RAN between cells in or out of the MBS service area + +If UE mobility can happen within the same NG-RAN between cells in or out of the service area, + +- The NG-RAN detects whether the UE is IN or OUT of an MBS service area and notifies the SMF if the UE moves in or out of the MBS service area. + +NOTE: When the UE joins, the SMF subscribes to the "Area Of Interest" event (see clause 7.2.4.3.2). + +- When the SMF knows the UE is IN or OUT of an MBS service, the SMF behaves as in clause 7.2.4.3.5. + +#### 7.2.4.3.7 Void + +#### 7.2.4.3.8 Connection Resume procedure with local MBS session + +The Connection Resume procedure for the UE is performed as defined in clause 7.2.3.7 with the following additions: + +- The source RAN, if supporting MBS and if the MBS session is active, provides MBS service area to the target RAN during the UE Context Retrieval procedure; +- An MBS supporting target RAN then applies the procedures in clause 7.2.4.3.6. +- The SMF applies the procedures in clause 7.2.4.3.5. + +### 7.2.5 MBS session activation and deactivation + +#### 7.2.5.1 General + +MBS Session activation procedure is for multicast only. MBS Session activation procedure is triggered by MB-SMF, when it receives the notification from MB-UPF for the downlink MBS DL data, or when it receives the request directly from AF or via NEF. The MBS Session activation procedure is used for activating the resources for MBS data at NG-RAN node. The multicast session state transits from Inactive to Active after MBS Session activation procedure, see clause 4.3. + +MBS Session deactivation procedure is for multicast only. MBS Session deactivation procedure is triggered by MB-SMF, when it receives the notification from MB-UPF in the case that there is no downlink data to be transmitted for some duration, or when it receives the request directly from AF or via NEF. The MBS Session deactivation procedure is used for deactivating the resources for MBS data at NG-RAN node. The multicast session state transits from Active to Inactive after MBS Session deactivation procedure, see clause 4.3. + +NOTE: For services (e.g. Mission Critical service) 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 [27], referenced by TS 23.289 [21]), which are sent over user plane of an MBS session, can be used in order to prevent a deactivation of the MBS session based on MB-UPF notifications and to keep UEs within the MBS session in a state where they can receive the MBS session data without being paged. It is up to implementation that the periodicity of the keep-alive packets configured in the AF needs to consider NG-RAN's configuration. + +### 7.2.5.2 MBS session activation procedure + +The following can trigger the MBS session activation procedure: + +- AF requests MB-SMF to activate the MBS session; +- MB-UPF receives the multicast data and notifies MB-SMF. + +![Sequence diagram of the MBS session activation procedure. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-UPF, MB-SMF. The procedure starts with MB-SMF triggering session activation, followed by Nmbsmf_MBSSession_ContextStatusNotify to SMF. SMF sends Namf_MT_EnableGroupReachability request to AMF, which responds with Namf_MT_EnableGroupReachability response. AMF then pages idle mode UEs. A Service Request is sent from UE to AMF. AMF sends Nsmf_PDUSession_UpdateSMContext request to SMF, which responds with Nsmf_PDUSession_UpdateSMContext response. AMF also sends Namf_MT_UEReachabilityInfo_Notify to SMF. SMF sends Namf_Communication_N1N2MessageTransfer to AMF. AMF sends N2 request to NG-RAN. NG-RAN performs 10a. Establishment of 5GC Shared MBS traffic delivery in clause 7.2.1.4 and 10b. Steps 8-12 as described in clause 7.2.1.3. AMF sends Namf_MBSCCommunication_N2MessageTransfer request (TMGI) to SMF. SMF sends NGAP activation request (TMGI) to NG-RAN. NG-RAN sends NGAP activation response to AMF. AMF sends Namf_MBSCCommunication_N2MessageTransfer response to SMF. SMF sends N4mb Session Modification to MB-UPF.](b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-UPF + participant MB-SMF + + Note right of MB-SMF: 1. MB-SMF triggers session activation + MB-SMF->>SMF: 2. Nmbsmf_MBSSession_ContextStatusNotify + SMF->>AMF: 3. Namf_MT_EnableGroupReachability request + AMF-->>SMF: 4a. Namf_MT_EnableGroupReachability response + AMF->>SMF: 4b. Namf_Communication_N1N2MessageTransfer + Note left of AMF: 5. AMF pages idle mode UEs + UE->>AMF: 6. Service Request + AMF->>SMF: 7a. Nsmf_PDUSession_UpdateSMContext request + SMF-->>AMF: 7b. Nsmf_PDUSession_UpdateSMContext response + AMF->>SMF: 8a. Namf_MT_UEReachabilityInfo_Notify + SMF->>AMF: 8b. Namf_Communication_N1N2MessageTransfer + AMF->>NG-RAN: 9. N2 request + Note left of NG-RAN: 10a. Establishment of 5GC Shared MBS traffic delivery in clause 7.2.1.4 + Note left of NG-RAN: 10b. Steps 8-12 as described in clause 7.2.1.3 + AMF->>SMF: 11. Namf_MBSCCommunication_N2MessageTransfer request (TMGI) + SMF->>NG-RAN: 12. NGAP activation request (TMGI) + NG-RAN-->>AMF: 13. NGAP activation response + AMF->>SMF: 14. Namf_MBSCCommunication_N2MessageTransfer response + SMF->>MB-UPF: 15. N4mb Session Modification + +``` + +Sequence diagram of the MBS session activation procedure. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-UPF, MB-SMF. The procedure starts with MB-SMF triggering session activation, followed by Nmbsmf\_MBSSession\_ContextStatusNotify to SMF. SMF sends Namf\_MT\_EnableGroupReachability request to AMF, which responds with Namf\_MT\_EnableGroupReachability response. AMF then pages idle mode UEs. A Service Request is sent from UE to AMF. AMF sends Nsmf\_PDUSession\_UpdateSMContext request to SMF, which responds with Nsmf\_PDUSession\_UpdateSMContext response. AMF also sends Namf\_MT\_UEReachabilityInfo\_Notify to SMF. SMF sends Namf\_Communication\_N1N2MessageTransfer to AMF. AMF sends N2 request to NG-RAN. NG-RAN performs 10a. Establishment of 5GC Shared MBS traffic delivery in clause 7.2.1.4 and 10b. Steps 8-12 as described in clause 7.2.1.3. AMF sends Namf\_MBSCCommunication\_N2MessageTransfer request (TMGI) to SMF. SMF sends NGAP activation request (TMGI) to NG-RAN. NG-RAN sends NGAP activation response to AMF. AMF sends Namf\_MBSCCommunication\_N2MessageTransfer response to SMF. SMF sends N4mb Session Modification to MB-UPF. + +Figure 7.2.5.2-1: MBS session activation procedure + +In this procedure, steps 11 to 15 are executed if the MB-SMF finds out there are shared tunnel established. Steps 11 to 15, if needed, are executed in parallel with steps 2 to 10. + +1. The procedure may be triggered by the following events: + - When the MB-UPF receives downlink data for a multicast MBS session, based on the instruction from the MB-SMF (as described in clause 7.2.5.3), the MB-UPF sends N4mb Notification (N4 Session ID) to the MB-SMF for indicating the arrival of DL MBS data. + - The AF sends MBS Activation request (TMGI) to the MB-SMF directly or via NEF. +2. MB-SMF sends Nmbsmf\_MBSSession\_ContextStatusNotify (MBS Session ID, multicast session state = Active) to SMF(s). + +The SMF sets the related multicast MBS session state to Active and finds out the list of UEs that joined the multicast MBS session identified by the related TMGI. If the SMF determines the user plane of the associated + +PDU session(s) of the UE(s) with respect to the TMGI are activated already, steps 3-8a will be skipped for those UE(s), i.e. executed from step 8b. + +3. The SMF invokes Namf\_MT\_EnableGroupReachability Request (List of UEs, [PDU Session ID of the associated PDU Sessions], TMGI, [UE reachability Notification Address], [most demanding ARP, 5QI of all MBS QoS Flow within MBS session]) to AMF(s). When later UE is reachable, the UE reachability Notification Address is used by the AMF to identify and notify the related SMF. + +After receiving the request, for each UE in the list, the AMF determines CM state of the UE: see steps 4 - 7. + +- 4a. If there are UEs involved in the multicast MBS Session and in CM-CONNECTED state, the AMF indicates those UEs to the SMF, using Namf\_MT\_EnableGroupReachability Response (UE list). Otherwise, the response does not include UE list. +- 4b. For each UE in the UE list included in step 4a, if the QoS profile(s) for associated PDU Session has not yet been provided, the SMF invokes Namf\_Communication\_N1N2MessageTransfer (N2 SM information (PDU Session ID, MBS Session ID, [QoS profile(s) for associated QoS flow(s)], [mapping information between the unicast QoS flow and multicast QoS flow])) to the AMF for the UE which is identified in step 4a. The associated unicast QoS Flow(s) as well as the mapping information between the unicast QoS Flow(s) and multicast QoS Flow(s) are included to support the 5GC Individual MBS traffic delivery. + +The SMF may also include the MBS assistance information for the MBS session in N2 SM Information, if the MBS subscription data from the UDM contains the MBS assistance information which includes the ID(s) of the MBS session(s) that the UE joined. The MBS assistance information for MBS session sent to the NG-RAN is described in clause 6.17. + +The procedure continues at step 9. + +5. [Conditional] If AMF determines that there are UEs in CM-IDLE state and involved in the multicast MBS Session, the AMF figures out the paging area covering all the registration areas of those UE(s), which need to be paged. The AMF may apply paging differentiation as specified in clause 6.12. The AMF sends a Multicast Group paging request message to the NG-RAN node(s) belonging to this Multicast Paging Area with the involved UE list and TMGI as the identifier to be paged if the related NG-RAN node(s) support MBS. If the AMF knows that the NG-RAN node(s) do not support MBS based on configuration, the AMF sends Paging message(s) to the NG-RAN node(s) per UE as described in step 4b in clause 4.2.3.3 of TS 23.502 [6]. + +NOTE 1: In addition to the paging in clause 6.12, other paging strategies is up to AMF implementation. + +NOTE 2: If NG-RAN performs the Group paging, it can indicate that the MBS session data is allowed to be received in RRC\_INACTIVE state. More details of the paging are specified by the RAN WGs. + +NOTE 3: CM-IDLE UEs using power saving function are included by the AMF in Group paging as specified in clause 7.2.10. + +6. Receiving the paging, the UE(s) in CM-IDLE state sends Service Request message to the AMF, see clause 4.2.3 of TS 23.502 [6]. + +NOTE 4: Step 6 for a UE can be parallel to step 5 for another UE(s), which has not received any paging yet. + +After receiving the Service Request sent by the UE(s), + +- Either based on the received PDU Session ID in step 3, the AMF invokes steps 7a/7b to update the related PDU sessions; or: +- Based on the received UE reachability Notification Address in step 3, the AMF identifies and notifies the related SMF of the UE(s), which are reachable now and the Location Information, by using the Namf\_MT\_UEReachabilityInfoNotify message. In this case, it can be a separated notification or combined with step 8. + +- 7a/7b. Based on the received PDU Session ID in step 3, the AMF identifies the related SMF and invokes Nsmf\_PDUSession\_UpdateSMContext request. The SMF replies with Nsmf\_PDUSession\_UpdateSMContext response. + +The SMF may also include the MBS assistance information for the MBS session in N2 SM Information, if the MBS subscription data from the UDM contains the MBS assistance information which includes the ID(s) of the + +MBS session(s) that the UE joined. The MBS assistance information for MBS session sent to the NG-RAN is described in clause 6.16. The procedure then continues at step 9. + +- 8a. For UE(s) that do not respond to paging, the AMF informs the SMF of the paging failure in Namf\_MT\_UEReachabilityInfoNotify. +- 8b. For UE(s) that is indicated as reachable via the Namf\_MT\_UEReachabilityInfoNotify message, or user plane of the associated PDU session is activated already but the QoS profile(s) for associated QoS flow(s) needs to be provided for the PDU session, the SMF invokes Namf\_Communication\_N1N2MessageTransfer (N2 SM information ()) to the AMF same as described in step 4b. + +The SMF may also include the MBS assistance information for the MBS session in N2 SM Information, if the MBS subscription data from the UDM contains the MBS assistance information which includes the ID(s) of the MBS session(s) that the UE joined. The MBS assistance information for MBS session sent to the NG-RAN is described in clause 6.16. + +9. The AMF sends N2 request message (N2 SM information ()) to the RAN node. + +NOTE 5: A joined UE is not able to receive MBS data if NG-RAN rejects the PDU Session Resource setup request (due to implementation specific reasons, e.g. activation of user plane fails due to the number of UEs reaching a limit). + +- 10a. If the shared tunnel has not been established before, the shared tunnel is established at this step, as defined in clause 7.2.1.4. The NG-RAN configures UE with RRC messages if needed. + +In this step or at later stage, NG-RAN may determine whether to apply delivery enabling reception by UEs in RRC\_INACTIVE state for the MBS session, as defined in clause 6.16. + +NOTE 6: Whether and when the NG-RAN determines to apply delivery enabling reception by UEs in RRC\_INACTIVE state for the MBS session as defined in clause 6.16 is to be decided by NG-RAN. + +- 10b. Steps 8 to 12 defined in clause 7.2.1.3 are performed. If 5GC Individual MBS traffic delivery is used, the SMF configures the UPF for individual delivery and if necessary, requests the MB-SMF to configure the MB-UPF to send multicast data to the UPF. + +11. If the MB-SMF finds out there are shared tunnel established, step 11-15 are performed. The MB-SMF invokes Namf\_MBSCCommunication\_N2MessageTransfer Request (TMGI, N2 SM Information (Activation, TMGI)) to the AMF for those NG-RAN nodes, which have shared tunnel with MB-UPF. This step may be performed in parallel with step 2. + +NOTE 7: The messages in steps 10a, 11 and 12 are MBS-specific and it is possible that the AMF(s) in steps 10a, 11 and 12 are not associate to any UEs involved in the multicast MBS Session. + +12. The AMF sends NGAP activation request message (N2 SM Information ()) to the NG-RAN nodes. For those UEs that have joined in the MBS Session and are in RRC\_INACTIVE state, the RAN nodes perform RAN paging as specified in TS 38.300 [9]. If Group paging is triggered, the NG-RAN may indicate that the MBS session data is allowed to be received in RRC\_INACTIVE state as specified in clause 6.17. + +NOTE 8: UEs in RRC\_INACTIVE state are to be considered for RAN paging related to an MBS session even if those UEs are using power saving functions, e.g. MICO (Mobile Initiated Connection Only) mode with Active Time, or extended DRX (Extended Discontinuous Reception) as defined in clause 5.31.7 of TS 23.501 [5]. + +13. The NG-RAN nodes responses to AMF by NGAP activation response message. The NG-RAN nodes establish radio resources to transmit multicast MBS session data to the UE(s). + +In this step or at later stage, NG-RAN may determine whether to apply delivery enabling reception by UEs in RRC\_INACTIVE state for the MBS session, as defined in clause 6.16. + +NOTE 9: Whether and when the NG-RAN determines to apply delivery enabling reception by UEs in RRC\_INACTIVE state for the MBS session as defined in clause 6.16 is to be decided by the NG-RAN. + +If the NG-RAN determines that a UE receives the multicast MBS data in RRC\_CONNECTED state, the NG-RAN shall not release the radio connection of a UE that has joined into the Multicast MBS session only because no unicast traffic is received for the UE. + +14. AMF to MB-SMF: Namf\_MBSCommunication\_N2MessageTransfer Response (). +15. The MB-SMF sends N4mb Session Modification Request to the MB-UPF to forward the received MBS packets. The MB-UPF responds to the MB-SMF with N4mb Session Modification Response acknowledging the MB-SMF request. + +NOTE 10: Depending on implementation, step 15 can be executed after the first successful response in step 14 to shorten the activation time, or buffering at the MB-UPF can be applied sufficiently long for the majority of RAN nodes to activate the MBS session to reduce packet loss. + +### 7.2.5.3 MBS session deactivation procedure + +![Sequence diagram of the MBS session deactivation procedure. Lifelines: UE, NG-RAN, AMF, UPF, SMF, MB-UPF, MB-SMF. The procedure starts with the MB-SMF triggering session deactivation. It then branches into two parallel paths: one involving the SMF, AMF, and NG-RAN (steps 3, 4a, 4b, 5, 6, 7, 8), and another involving the MB-UPF and MB-SMF (steps 2, 3, 9).](a2bbc82e5c6132b0870bd70f6657f919_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UPF + participant SMF + participant MB-UPF + participant MB-SMF + + Note right of MB-SMF: 1. MB-SMF triggers session deactivation + MB-SMF->>MB-UPF: 2. N4mb Session Modification + MB-SMF->>SMF: 3. Nmbsmf_MBSSession_ContextStatusNotify() + Note left of SMF: 4a. Step 3b and steps 4-8 in clause 4.3.3.2 of TS 23.502 are performed + Note left of SMF: 4b. Step 3 to 6 in clause 7.2.2.2 may be performed + SMF->>AMF: 5. Namf_MBSCommunication_N2MessageTransfer request (TMGI) + AMF->>NG-RAN: 6. NGAP deactivation request message (TMGI) + Note left of NG-RAN: 7. Sets the multicast MBS session state to inactive + NG-RAN->>AMF: 8. NGAP deactivation response message (TMGI) + AMF->>MB-SMF: 9. Namf_MBSCommunication_N2MessageTransfer response + +``` + +Sequence diagram of the MBS session deactivation procedure. Lifelines: UE, NG-RAN, AMF, UPF, SMF, MB-UPF, MB-SMF. The procedure starts with the MB-SMF triggering session deactivation. It then branches into two parallel paths: one involving the SMF, AMF, and NG-RAN (steps 3, 4a, 4b, 5, 6, 7, 8), and another involving the MB-UPF and MB-SMF (steps 2, 3, 9). + +Figure 7.2.5.3-1: MBS session deactivation procedure + +In this procedure, steps 3 to 4 and steps 5 to 9 are executed in parallel. + +1. The procedure may be triggered by the following events: + - When MB-UPF detects there is no data receives for the MBS Session, MB-UPF sends MB-N4 Notification (N4 Session ID) to the MB-SMF for deactivating the MBS session. + - AF sends MBS Deactivation request (TMGI) to the MB-SMF directly or via NEF. +2. The MB-SMF sends an N4mb Session Modification Request (TMGI, [Buffered Downlink Traffic detection]) to the MB-UPF. The Buffered Downlink Traffic detection is requested by MB-SMF to be informed by the MB-UPF about incoming MBS data. The MB-SMF triggers MBS session activation once informed. If the MBS session is to be activated via the AF request directly, the Buffered Downlink traffic detection is not needed, but the MB-SMF still instructs the MB-UPF to stop forwarding and possibly to buffer MBS data. + +MB-UPF to MB-SMF: N4mb Session Modification Response acknowledging the MB-SMF request. + +NOTE 1: It is up to stage 3 to determine whether MB-UPF keeps the DL F-TEID(s) for N3mb and N19mb interfaces. + +3. The MB-SMF sends Nmbsmf\_MBSSession\_ContextStatusNotify request (MBS Session ID) to the SMFs. + +Based on the received MBS Session ID, the SMF sets the indicated multicast MBS session state to Inactive: + +- If the SMF finds out there are UE(s) that joined the indicated multicast MBS session and use 5GC Individual MBS traffic delivery, step 4 is performed for those UE(s). + - If SMF find there are no UE(s) that joined the indicated MBS session and use 5GC Individual MBS traffic delivery, no further operation for SMF is required. +- 4a. [Conditional] For UE(s) for which the 5GC individual delivery is used, step 3b and steps 4-8 in clause 4.3.3.2 of TS 23.502 [6] are performed to remove the associated QoS flow(s) related to the multicast MBS session. + +NOTE 2: Whether the associated QoS Flow(s) are removed from UE, NG-RAN, or only resource in NG-RAN is removed is up to implementation. + +- 4b [Conditional] For UE(s) for which the 5GC individual delivery is used, the related SMF(s) may keep the shared tunnel that is used for Individual MBS traffic delivery over N19mb interface. If the SMF decides to release the shared tunnel, steps 3 to 6 in clause 7.2.2.2 need to be performed. + +5. If the MB-SMF finds out there are shared tunnel established over N3mb interface, the MB-SMF sends Namf\_MBSSCommunication\_N2MessageTransfer Request (TMGI, N2 SM information (Deactivation, TMGI)) to the AMFs. +6. The AMF sends NGAP deactivation request message (N2 SM information ()) to the NG-RAN nodes. +7. The NG-RAN node keeps the multicast MBS Session Context and N3mb shared tunnel for the multicast MBS session. + +If the MBS Session Context indicates no UE for the multicast MBS session (e.g. due to UE becomes CM-IDLE state), the NG-RAN triggers release of the shared delivery as described in clause 7.2.2.4. +8. NG-RAN acknowledges the NGAP deactivation Response message. +9. The AMF invokes Namf\_MBSSCommunication\_N2MessageTransfer Response to acknowledge the service for MB-SMF. + +When the MBS session is in "Inactive" state and handover procedure is triggered, it is defined in clause 7.2.3.6. + +NOTE 3: There is no explicit "deactivation" indication to the UE, how the UE is changed to IDLE state is defined in TS 38.300 [9]. + +## 7.2.6 Multicast session update procedure + +Multicast MBS session update procedure is invoked by the AF to update the service requirement (result in multicast QoS parameters update and/or multicast QoS flow addition/removal) and/or MBS Service Area for an ongoing Multicast MBS session. + +If the MBSF acts as the MBS security function for multicast as defined in TS 33.501 [20], it may use this procedure to provide an updated MSK and optional updated MTK in addition for the MBS session via the control plane. + +NOTE: The procedure is not applicable if no MSK but only the MTK is to be updated. + +For the interaction between AF or MBSF and MB-SMF, see clauses 7.1.1.6 and 7.1.1.7. + +![Sequence diagram of the Multicast MBS Session update procedure. Lifelines: UE, NG-RAN, AMF, SMF, MB-SMF, AF. The procedure starts with an MBS session update trigger in the AF, followed by an AF-to-UE notification. The MB-SMF then invokes Namf_MBSCommunication_N2MessageTransfer to the AMF. The AMF sends an N2 MBS session request to the NG-RAN. The NG-RAN updates MBS parameters and sends an N2 MBS session response to the AMF. The AMF then invokes Nmbsmf_MBSSession_ContextUpdate and Nmbsmf_MBSSession_ContextStatusNotify on the SMF. The SMF determines affected UEs. For each affected UE, a UE location subscription update, UE location inquiry, and PDU Session Modification procedure are performed.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant AF + participant MB-SMF + participant SMF + participant AMF + participant NG-RAN + participant UE + + Note right of AF: 1. MBS session update triggered as in clauses 7.1.1.6 and 7.1.1.7 + AF->>UE: 2. AF informs UE about updated service area for multicast session + Note right of MB-SMF: 3. Namf_MBSCommunication_N2MessageTransfer + MB-SMF->>AMF: 3. Namf_MBSCommunication_N2MessageTransfer + AMF->>NG-RAN: 4. N2 MBS session request + Note left of NG-RAN: 5. RAN updates MBS parameters + NG-RAN->>AMF: 6. N2 MBS session response + AMF->>SMF: 7. Nmbsmf_MBSSession_ContextUpdate + SMF->>AMF: 8. Nmbsmf_MBSSession_ContextStatusNotify + Note right of SMF: 9. Determine affected UEs + loop For each affected UE + Note right of NG-RAN: 10. UE location subscription update + NG-RAN->>SMF: 10. UE location subscription update + Note right of SMF: 11. UE location inquiry + SMF->>AMF: 11. UE location inquiry + Note right of AMF: 12. PDU Session Modification procedure + AMF->>NG-RAN: 12. PDU Session Modification procedure + end + +``` + +Sequence diagram of the Multicast MBS Session update procedure. Lifelines: UE, NG-RAN, AMF, SMF, MB-SMF, AF. The procedure starts with an MBS session update trigger in the AF, followed by an AF-to-UE notification. The MB-SMF then invokes Namf\_MBSCommunication\_N2MessageTransfer to the AMF. The AMF sends an N2 MBS session request to the NG-RAN. The NG-RAN updates MBS parameters and sends an N2 MBS session response to the AMF. The AMF then invokes Nmbsmf\_MBSSession\_ContextUpdate and Nmbsmf\_MBSSession\_ContextStatusNotify on the SMF. The SMF determines affected UEs. For each affected UE, a UE location subscription update, UE location inquiry, and PDU Session Modification procedure are performed. + +**Figure 7.2.6-1: Multicast MBS Session update procedure** + +- This procedure is triggered by the MB-SMF receiving the updated service requirement, an updated multicast session security context from the MBSF and/or MBS Service Area for a multicast MBS Session, see clauses 7.1.1.6 and 7.1.1.7. +- The AF providing the updated service area may also inform UEs at application level about the new service area via a service announcement. + +NOTE 1: If a UE is located in a cell which was previously outside the service area and is now inside the updated service area, the UE can join the multicast service as specified in clause 7.2.1.3. + +For QoS updates steps 3 to 7 are performed. + +For MBS Service Area update steps 3 to 7 may be performed to allow NG-RAN to terminate data transmission in the area which is no longer in the MBS Service Area. + +- The MB-SMF invokes Namf\_MBSCommunication\_N2MessageTransfer service operation (MBS Session ID, [Area Session ID], N2 SM message container (TMGI, [QoS profile(s) for multicast MBS session], [MBS Service Area], [Area Session Id])) to the AMF(s). +- The involved AMF sends N2 MBS session request (N2 SM message container) to NG-RAN nodes handling the multicast MBS session and possible Area Session ID based on the RAN node IDs stored in the AMF for the MBS session. +- The NG-RAN node updates the QoS profile and/or MBS Service Area for the multicast MBS session based on the N2 MBS session request. If only QoS parameters are updated without multicast QoS flows added/removed, the NG-RAN may also update the QoS parameters of the associating PDU Sessions. + +For MBS Service Area update, the NG-RAN updates the MBS Session Context with the updated MBS Service Area. The NG-RAN stops transmission of the related multicast data in the cell(s) which is within the old MBS Service Area but now outside the updated MBS Service Area. The NG-RAN also configures the UE not to receive the MBS data over the radio interface if the NG-RAN detects the UE(s) was in the previous MBS + +Service Area but is outside the updated MBS Service Area. If the NG-RAN node no longer serves any cells within the updated MBS service area, it requests to release shared delivery resource as defined in clause 7.2.2.4. + +6. The NG-RAN node(s) acknowledges N2 MBS session request by sending an N2 MBS session Response message to the AMF. +7. The AMF invokes the Nmbsmf\_MBSSession\_ContextUpdate () to the MB-SMF. +8. The MB-SMF sends Nmbsmf\_MBSSession\_ContextStatusNotify request (MBS Session ID, [QoS profiles for multicast for MBS session], [MBS Service Area], [Area Session ID], [updated multicast session security context]) to the SMFs. For MBS Service Area updates, if an Area Session ID exists, the MB-SMF provides the MBS Service Area corresponding to the Area Session ID to the SMFs involved in the multicast MBS session. For QoS updates, the MB-SMF notifies SMFs handling all MBS service areas. +9. The SMF determines the affected UEs it serves based on the multicast MBS Session ID and Area Session ID (if provided) received in the step 8. + +The subsequent steps 10 to 12 are executed for each affected UE. For QoS updates, steps 10 and 11 are skipped. + +10. [Conditional] For an MBS Service Area update, if the SMF previously subscribed at the AMF to notifications about the UE moving in or out of a subscribed "Area Of Interest", the SMF updates the subscription with the new MBS Service Area as area of interest. +11. [Optional] When the MBS Service Area is updated, if the SMF does not have the latest UE location, the SMF queries AMF which then query the NG-RAN for the current location of the UE to determine whether the UE is within the updated MBS Service Area. +12. [Conditional] For QoS Updates, if the 5GC Individual MBS traffic delivery is used, or if the associated QoS flows is to be added/removed, the SMF triggers PDU Session Modification procedure as defined in TS 23.502 [6]. If the 5GC Individual MBS traffic delivery is used, the SMF may also configure the UPF with the updated QoS and/or updated or removed QoS flows. + +For MSK updates, the SMF also triggers PDU Session Modification procedure and provides the updated multicast session security context in the N1 SM container. + +For MBS Service Area update, the SMF triggers the PDU Session Modification procedure as defined in TS 23.502 [6] with the following enhancement: + +- The SMF also updates the PDU session resources associated to the multicast MBS session with the new MBS service area in an N2 container. The RAN node serving the PDU session starts or terminates transmission of multicast content in cells which are added or removed in the updated service area, respectively, and if necessary, interacts with the MB-SMF to start or terminate the distribution of multicast data to the RAN node. +- Towards the UE, the SMF provides the MBS service area in N1 SM container to the UE. For a UE previously inside the MBS service area but now outside the updated MBS service area of the multicast MBS session, the SMF may alternatively, based on operator policy, inform the UE in the N1 SM container that the UE has been removed from the multicast MBS session. +- Towards the NG-RAN, the SMF provides the updated MBS service area in N2 SM information. For a NG-RAN node supporting MBS, it starts transmission of multicast content in cells which are added in the updated MBS service area if UEs within the Multicast MBS session are within those cells, and if necessary, the NG-RAN interacts with the MB-SMF to start the distribution of multicast data to the RAN node. The RAN node stops transmission of multicast content in cells which are removed from the updated MBS service area, and if necessary, the NG-RAN interacts with the MB-SMF to terminate the distribution of multicast data to the RAN node +- For Individual delivery and a local Multicast MBS session the following applies: For a UE previously inside the service area but now outside the updated MBS service area, the SMF removes associated unicast QoS flows for the multicast MBS session. For a UE previously outside the service area but now inside the updated service area, the SMF adds associated unicast QoS flows for the multicast MBS session to the PDU session resources. + +## 7.2.7 Void + +## 7.2.8 Service request procedure + +If the multicast MBS session is in Inactive state, the UE can go to CM-IDLE state or the user plane of the associated PDU Session may be deactivated even when the UE is in CM-CONNECTED state. When user plane of the associated PDU session is activated again, the SMF sends the MBS session information to NG-RAN during Service Request procedure as specified in TS 23.502 [6]. The MBS session information indicates that this MBS session is in Inactive state; and: + +- For the MBS supporting NG-RAN node, the NG-RAN establish the shared tunnel with the MB-UPF as usual. However, as the MBS session is in Inactive state, the NG-RAN node will not allocate related radio resource. +- For the non-MBS supporting NG-RAN node, the unicast QoS flow associated with the MBS session are not established. + +The service request procedure can also be executed while the multicast MBS session is in Active state: The UE can go to CM-IDLE state due to AN release as specified in TS 23.502 [6]. In addition, to activate the associated PDU session(s) parts of the service request procedure can also be executed during the Mobility Registration Update procedure as specified in clause 4.2.2.2.2 of TS 23.502 [6]. When the service request procedure is executed, the SMF provides the MBS session information indicating that the UE joined the MBS session to the NG-RAN within N2 SM container for the associated PDU Session. + +NOTE: Network triggered Service Request, if triggered for other reason, can also be used by the SMF to provide that MBS session information to NG-RAN. + +## 7.2.9 AF provisioning multicast MBS Session Authorization information + +The AF provisions the multicast MBS session authorization information for multicast MBS sessions that are not open to "any UE". The procedure specified in clause 4.15.6.2 of TS 23.502 [6] is reused with the following enhancements: + +- The AF may provision the MBS Session Authorization information to the 5GC. The MBS Session Authorization information is associated with a group of UEs. + +**Table 7.2.9-1: MBS Session Authorization information** + +| Parameters | Description | +|---------------------------------------|----------------------------------------------------| +| MBS Session Authorization information | One or more MBS Session IDs. | +| | A group of UEs identified by an External Group ID. | + +- The AF may support multicast MBS group membership management and provide parameters as described in Table 7.2.9-2. + +**Table 7.2.9-2: Multicast MBS group membership management parameters** + +| Parameters | Description | +|-------------------|---------------------------------------------------------------------| +| List of GPSI | List of multicast group members, each member is identified by GPSI. | +| External Group ID | Identifier for multicast MBS group. | + +- If a new multicast MBS group is created, the UDM shall assign a unique Internal Group ID for the multicast MBS group and include the newly assigned Internal Group ID in the Nudr\_DM\_Create Request message. +- If the AF is authorised by the UDM to provision the MBS Session Authorization information, the UDM resolves the GPSI of each MBS session group member to SUPI, and requests to create, update or delete the provisioned MBS Session Authorization information as part of the MBS subscription data for each SUPI via Nudr\_DM\_Create/Update/Delete Request message, and the message includes the provisioned MBS Session Authorization information. + +## 7.2.9a AF provisioning MBS Session assistance information + +After the AF obtains the MBS Session ID of a multicast MBS Session as specified in clauses 7.1.1.2 and 7.1.1.3, the AF may provision the MBS Session assistance information for the UE(s) via NEF to UDM using the procedure of external parameter provisioning as specified clause 4.15.6.2 of TS 23.502 [6] with the following enhancements: + +- the AF may provision MBS Session Assistance Information, which indicates that a UE is preferred to be kept connected when the related MBS Session the UE joined is active. + +**Table 7.2.9a-1: MBS Session Assistance information** + +| Parameters | Description | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBS Session Assistance information | A list of UEs represented by GPSIs that are preferred to be kept connected when the MBS Session represented by the indicated MBS session ID the UE joined is active.
MBS Session ID. | + +NOTE 1: MBS Session Assistance information has no effect if the function of UE receiving MBS multicast in RRC\_INACTIVE state is not used. The AF does not provision the MBS Session assistance information if the AF knows that the PLMN does not support the function of UE receiving MBS multicast in RRC\_INACTIVE state. + +NOTE 2: The AF can provide the MBS Session assistance information for the UEs based on observed or expected UE data transmission behaviour, e.g. a frequent talker and/or the group leader of a multicast group represented by an MBS Session ID. + +NOTE 3: If the MBS Assistance Information is already available when a UE joins a multicast MBS Session, the SMF provides the information to the NG-RAN in the UE join procedure as specified in clause 7.2.1.3. If the MBS Assistance Information becomes available in the UDM, the UDM performs procedure of Session Management Subscriber Data Update Notification to SMF as specified in clause 4.5.2 of TS 23.502 [6] per subscription data change notification requested by the SMF. + +If the AF is authorised by the UDM to provision the UE list MBS Assistance information, the UDM resolves the GPSI to SUPI, and requests to create, update or delete the provisioned UE list MBS Assistance information as part of the MBS subscription data for each SUPI. + +## 7.2.10 Multicast MBS procedures for UEs using power saving functions + +**Editor's note:** Alignment may be needed with RAN WG(s). + +For a UE using power saving function to receive multicast MBS Session data, the following applies: + +- For an MBS multicast session, a UE needs to join the multicast session as defined in clause 7.2.1.3 prior to MBS data reception. To join the multicast session, the UE needs to be in RRC\_CONNECTED state. The UE may select any suitable time when it is in RRC\_CONNECTED state or transition to RRC\_CONNECTED state before joining the multicast session. + +NOTE 1: If the UE has not previously joined the MBS multicast session, at the possible scheduled activation time it performs MBS join procedure. Whether the UE performs MBS join procedure in advance and stays "joined" or every time at activation time is left up to UE implementation. + +- If a UE is in RRC\_CONNECTED state or in CM-IDLE state or CM-CONNECTED with RRC\_INACTIVE state, and reachable (e.g. in active time in MICO or PTW for eDRX), due to other reasons at the start time and the scheduled activation times, the UE follows the related MBS procedures (e.g. clause 7.2.1 for UE join and clause 7.2.5.2 for MBS Session Activation) with the following enhancement: + - At MBS Session Activation, when the AMF perform group paging, the AMF also includes the CM-IDLE UEs using power saving function(s). +- If a UE is in CM-IDLE state or CM-CONNECTED with RRC\_INACTIVE and in deep sleep (i.e. unreachable for paging to the network) at the possible start time and the possible scheduled activation times, the UE leaves the deep sleep state at the session start time and the possible scheduled activation times to allow MBS related procedures (e.g. clause 7.2.1 for UE join and clause 7.2.5.2 for MBS Session Activation): + +- At the possible start time, an RRC\_IDLE or CM-CONNECTED with RRC\_INACTIVE UE needs to send a request to transition to RRC\_CONNECTED state and join the MBS multicast session (if not done before). + +NOTE 2: The UE become reachable in the network for the unicast service as well. + +- At the possible scheduled activation times, an RRC\_IDLE UE that already joined the multicast MBS session needs to listen for paging requests and if paged by the network follow the existing procedures in clause 7.2.5.2. How long the device listens to paging is left up to device implementation. + +NOTE 3: How long the UE need to listen to paging is left up to UE implementation. + +- When the UE is in the middle of an MBS data transfer, and the UE is scheduled to move to deep sleep due to power saving, e.g. end of PTW for extended idle mode DRX, expiration of active time for MICO or the UE transitioning from CM-CONNECTED to CM-IDLE in the case of MICO with no active time, then the UE does not go to deep sleep during the remainder of the current MBS data transfer. + +NOTE 4: If at the end of the current MBS data transfer the UE knows there is another MBS data transfer scheduled soon, depending on the time between MBS data transfers, the UE can decide to go to sleep between MBS data transfers. + +## 7.3 MBS procedures for broadcast Session + +NOTE: The interactions between the MBSF, the MBSTF and the AF, for example file delivery and HTTP adaptive streaming, will be defined in TS 26.502 [18] and TS 26.517 [22]. + +### 7.3.1 MBS Session Start for Broadcast + +The Broadcast MBS Session Start follows the common procedure specified in clause 7.1.1.2 or clause 7.1.1.3, which consist of TMGI Allocation and MBS Session Create. It is possible for AF to allocate TMGI once but create the MBS Session for multiple times. A combined procedure to perform both TMGI allocation and MBS Session Create is available. + +The TMGI Allocation is used by AF to obtain the TMGI as MBS Session ID (i.e. TMGI) and perform service announcement towards UEs. + +The MBS Session Create (with MBS service type set to broadcast service) is used by the AF to indicate the impending start of the transmission of MBS data, and to provide the session attributes, so that resources for the MBS Session are set up in the MB-UPF and in the NG-RAN for 5GC Shared MBS traffic delivery. The MBS Session Create can be used if TMGI has not been allocated. In this case, MB-SMF will allocate a unique TMGI for the AF and then start the MBS Session. + +NOTE 1: When the multicast transport between NG-RAN and MB-UPF is described below, source specific multicasting is assumed. + +To receive the data of broadcast communication service, the UE is either preconfigured with needed configuration (see TS 24.575 [26] for UE pre-configuration) for the UE to receive MBS service, or provisioned with the configuration of Broadcast MBS session on application level (service announcement as described in TS 26.502 [18] and TS 26.517 [22]). If the needed configuration is pre-configured, the UE does not need to interact with network. + +![Sequence diagram for MBS Session Establishment for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, AF.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant NEF/MBSF + participant AF + + Note over UE, NG-RAN: 0. NG-RAN advertises FSA ID + rect rgb(255, 255, 255) + Note over UE, AF: 1. TMGI allocation, MBS Session Create and service Announcement: see clause 7.1.1.2 or 7.1.1.3 + end + MB-SMF->>AMF: 2. Namf_MBSBroadcast_ContextCreate Request (TMGI, LL SSM, 5G Authorized QoS Profile, MBS service area) + AMF->>NG-RAN: 3. N2 message Request (TMGI, LL SSM, QoS Profile, MBS service area) + Note over NG-RAN: 4. MBS Session context created + NG-RAN-->MB-UPF: 5a. IGMP/MLD join + Note over NG-RAN: 5b. Unicast DL Tunnel allocated + NG-RAN->>AMF: 6. N2 message Response (TMGI, N3mb DL Tunnel info) + AMF->>MB-SMF: 7. Namf_MBSBroadcast_ContextCreate Response () + Note over UE, NG-RAN: 9. NG-RAN advertises TMGI + MB-SMF->>MB-UPF: 8. N4mb Session Modification (TMGI, N3mb DL Tunnel Info) + MB-UPF-->NEF/MBSF: 8a. Nmbsmf_MBSession_StatusNotify + NEF/MBSF-->AF: 8b. Nnef_MBSession_StatusNotify + NG-RAN->>AMF: 10. N2 message Response (TMGI, N3mb DL Tunnel info) + AMF->>MB-SMF: 11. Namf_MBSBroadcast_ContextStatusNotify Request () + MB-SMF->>MB-UPF: 12. N4mb Session Modification (TMGI, N3mb DL Tunnel Info) + AF->>MB-UPF: 13. Media stream + MB-UPF->>NG-RAN: 14. Media stream + NG-RAN->>UE: 15. PTM transmission + +``` + +Sequence diagram for MBS Session Establishment for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, AF. + +**Figure 7.3.1-1: MBS Session Establishment for Broadcast** + +0. Based on OAM configuration, RAN nodes announce in SIBs over the radio interface information about the MBS FSA IDs and frequencies of neighbouring cells. +1. To establish broadcast MBS session, the AF performs TMGI allocation and MBS session creation as specified in clause 7.1.1.2 or 7.1.1.3. The MBS service type indicates to be broadcast service. The MBS FSA ID(s) of a broadcast MBS session are communicated in the service announcement towards the UE. The UE compares those MBS FSA ID(s) with the MBS FSA ID(s) in SIBs for frequency selection. +2. The MB-SMF may use NRF to discover the AMF(s) supporting MBS based on the MBS service area and select the appropriate one(s). Then the MB-SMF sends the Namf\_MBSBroadcast\_ContextCreate (TMGI, N2 SM information ([LL SSM], 5G QoS Profile), MBS service area, [MBS FSA ID(s)]) messages to the selected AMF(s) in parallel if the service type is broadcast service. The MB-SMF may include a maximum response time in the request. +3. The AMF transfers the MBS Session Resource Setup Request message, which contains the N2 SM information in the received Namf\_MBSBroadcast\_ContextCreate Request to all NG-RANs which support MBS in the MBS service area. The AMF includes the MBS service area. +4. NG-RAN creates a Broadcast MBS Session Context and stores the TMGI and the QoS Profile in the MBS Session Context. The LL SSM are optional parameters and only provided by MB-SMF to NG-RAN if N3mb multicast transport is configured to be used in the 5GC. If MBS FSA ID(s) were received, the NG-RAN may use those MBS FSA ID(s) to determine cells/frequencies within the MBS service area to broadcast MBS session data based on OAM configuration about the MBS FSA IDs and related frequencies. + +Depending on the NG-RAN's preference to use multicast or unicast transport over N3mb and the availability of the LL SSM, step 5a or step 5b is executed. + +- 5a. If NG-RAN prefers to use N3mb multicast transport (and if LL SSM is available in NG-RAN), the NG-RAN joins the multicast group (*i.e.* LL SSM). +- 5b. If NG-RAN prefers to use N3mb unicast transport (or if the LL SSM is not available in NG-RAN) between the NG-RAN and MB-UPF, NG-RAN allocates its N3mb DL Tunnel endpoint to receive downlink MBS session data. +6. The NG-RAN reports successful establishment of the MBS Session resources (which may include multiple MBS QoS Flows) by sending MBS Session Resource Setup Response (TMGI, N2 SM information ([N3mb DL Tunnel Info])) message(s) to the AMF. If NG-RAN prefers to use N3mb unicast transport (or if the LL SSM is not + +available in NG-RAN) between the NG-RAN and MB-UPF, NG-RAN provides its N3mb DL Tunnel Info as part of the N2 SM information. For more details, refer to TS 38.413 [15]. + +7. The AMF transfers the Namf\_MBSBroadcast\_ContextCreate Response () to the MB-SMF. The AMF should respond success when it receives the first success response from the NG-RAN(s). And if all NG-RAN(s) report failure, the AMF should respond failure. The MB-SMF stores the AMF(s) which responds success in the MBS Session Context as the downstream nodes. If the AMF receives the NG-RAN response(s) from all involved NG-RAN(s), the AMF should include an indication of completion of the operation in all NG-RANs. If received from NG-RAN node, the N3mb DL Tunnel Info and NG-RAN ID are included in the response. +8. [Conditional] If N3mb unicast transport is to be used (i.e. N3mb DL Tunnel Info is present in the Namf\_MBSBroadcast\_ContextCreate Response message from AMF) in a deployment where NG-RAN nodes share a common user plane entity, the MB-SMF only establishes the shared tunnel towards the DL GTP tunnel endpoint if the shared tunnel has not yet been established (as determined based on the stored DL GTP Tunnel endpoint(s) for the MBS session). The MB-SMF also stores the received DL GTP Tunnel and corresponding NG-RAN Node ID for the MBS session. For the deployment where NG-RAN nodes do not share a common user plane entity, the DL GTP tunnel will not be used by other NG-RAN nodes. In a deployment where NG-RAN nodes do not share a common user plane entity, the MB-SMF always establishes the shared tunnel towards the DL GTP tunnel endpoint. + +To establish the shared tunnel towards the DL GTP tunnel endpoint, the MB-SMF sends an N4mb Session Modification Request to the MB-UPF to allocate the N3mb unicast transport tunnel for a replicated MBS stream for the MBS Session. + +- 8a-8b. If the AF subscribed to a Delivery Status Indication (see clause 7.3.5), the MB-SMF notifies the AF as specified in step 2 of clause 7.3.5. The MB-SMF notifies the AF directly by invoking Nmbsmf\_MBSsession\_StatusNotify service operation, or the MB-SMF notifies the AF via NEF/MBSF (if deployed) by invoking Nmbsmf\_MBSsession\_StatusNotify service operation to the NEF/MBSF which then invokes Nnef\_MBSsession\_StatusNotify service operation to the AF. + +9. NG-RAN broadcasts the TMGI representing the MBS service over radio interface. Step 9 can take place in parallel with step 6. +10. Another NG-RAN may report successful establishment of the MBS Session resources (which may include multiple MBS QoS Flows) by sending MBS Session Resource Setup Response (TMGI, N2 SM information ([N3mb DL Tunnel Info])) message after the AMF transferred the Namf\_MBSBroadcast\_ContextCreate Response () to the MB-SMF. +11. The AMF transfers the Namf\_MBSBroadcast\_ContextStatusNotify request () to the MB-SMF. When the AMF receives the response from all NG-RAN nodes, the AMF includes an indication of the completion of the operation. If the AMF does not receive responses from all NG-RAN nodes before the maximum response time elapses since the reception of the Namf\_MBSBroadcast\_ContextCreate Request, then the AMF should transfer the Namf\_MBSBroadcast\_ContextStatusNotify request () which indicates partial success or failure. +12. [Conditional] If N3mb unicast transport is to be used (i.e. N3mb DL Tunnel Info is present in the MBS Session Start Response message from AMF), the handling in MB-SMF and MB-UPF is the same as specified in step 8. +13. The AF starts transmitting the DL media stream to MB-UPF using the N6mb Tunnel, or optionally un-tunnelled i.e. as an IP multicast stream using the HL MC address. +14. The MB-UPF transmits the media stream to NG-RAN via N3mb multicast transport or unicast transport. +15. The NG-RAN transmits the received DL media stream using DL PTM resources. + +NOTE 2: Step 6-8 and 2-4 are comparable to step 2-5 and 6-7 in clause 7.2.1.4, respectively. + +### 7.3.1a MBS Session Start for resource sharing across multiple broadcast MBS Sessions during network sharing + +To support resource sharing across multiple broadcast MBS Sessions during network sharing (see clause 6.18), in addition to clause 7.3.1, the following enhancement applies: + +- Step 2: The MB-SMF includes Associated Session ID in the N2 SM information in Namf\_MBSBroadcast\_ContextCreate. + +- Step 4: A shared NG-RAN node identifies the associated MBS sessions as specified in clause 6.18. The associated MBS sessions share radio resource configuration based on the existing Broadcast MBS Session context. +- Step 5a: If the NG-RAN determines there is already an existing broadcast MBS session delivering the same content, the NG-RAN may skip joining the multicast group based on operator policy, i.e. step 5a can be skipped. +- Step 5b: If the NG-RAN determines there is already an existing broadcast MBS session delivering the same content, a shared NG-RAN node may decide not to allocate N3mb DL tunnel endpoint. +- Step 6: + - For N3mb multicast transport, when the NG-RAN node decides to skip joining the multicast group in step 5a, the NG-RAN still reports successful establishment of the MBS Session resource. + - For N3mb unicast transport, when the NG-RAN decides not to allocate N3mb DL Tunnel endpoint in step 5b, the NG-RAN still reports successful establishment of the MBS Session resource but the N3mb DL Tunnel Info is not included in MBS Session Resource Setup Response. +- Step 8: If the N3mb unicast transport is used but N3mb DL Tunnel Info is not present in MBS Session Resource Setup Response, the MB-SMF accepts the response and skips step 8. +- Step 9: If the NG-RAN determines that radio resource has been allocated for another broadcast MBS Session delivering the same content as specified in clause 6.18, the NG-RAN advertises the TMGI of the broadcast MBS session, and reuses such already allocated radio resource for the MBS data transmission for the broadcast MBS session. + +NOTE: The 5G QoS Profile values for the broadcast MBS sessions are assumed to be pre-agreed amongst the multiple operators participating in the network sharing, and are the same irrespective of the PLMN from which the MBS Session Start is sent. + +- Step 10 ~ step 12: + +The handling is the same as steps 5, 6, 7 and 8. + +- Step 14: If the user plane of a broadcast MBS session from its MB-UPF to the shared NG-RAN is not established, the NG-RAN will not receive the MBS packets from the MB-UPF. +- Step 15: If the NG-RAN receives multiple DL media streams for the same content represented by the same Associated Session ID via multiple CNs, the NG-RAN should deliver only one DL media stream. + +### 7.3.2 MBS Session Release for Broadcast + +The MBS Session Release for broadcast follows the MBS Session Deletion (e.g. TMGI De-allocation and MBS Session Deletion) so that resource for shared MBS delivery is released. It is possible for AF to stop MBS Session but keep TMGI allocated. + +![Sequence diagram for MBS Session Release for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, AF. The sequence starts with a media stream from AF to UE via NEF/MBSF, PCF, MB-UPF, MB-SMF, AMF, and NG-RAN. The AF stops the stream and initiates MBS Session Deletion. The MB-SMF sends a context release request to the AMF. The AMF sends a resource release request to the NG-RAN. The NG-RAN stops PTM delivery and sends a Leave message (6a) or releases a unicast DL tunnel (6b). The NG-RAN sends a resource release response to the AMF. The AMF sends a context release response to the MB-SMF. Finally, the AF starts a TMGI de-allocation procedure.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant PCF + participant NEF/MBSF + participant AF + + Note left of UE: 1. PTM + Note right of AF: 1. Media stream + Note right of NEF/MBSF: 1. Media stream + AF->>NEF/MBSF: 2. MBS Session Deletion in Figure 7.1.1.4-1 or 7.1.1.5-1 + NEF/MBSF->>MB-SMF: 3. Namf_MBSBroadcast_ContextRelease Request (TMGI) + MB-SMF->>AMF: 4. MB Session Resource Release Req (TMGI) + AMF->>NG-RAN: 5. Stop PTM delivery + NG-RAN->>MB-UPF: 6a. MLD/IGMP Leave (LL MC addr) + Note right of NG-RAN: 6b. Unicast DL Tunnel released + NG-RAN->>AMF: 7. MB Session Resource Release Resp + AMF->>MB-SMF: 8. Namf_MBSBroadcast_ContextRelease Response + Note right of MB-SMF: 9. TMGI De-allocation in Figure 7.1.1.4-1 or Figure 7.1.1.5-1 + +``` + +Sequence diagram for MBS Session Release for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, AF. The sequence starts with a media stream from AF to UE via NEF/MBSF, PCF, MB-UPF, MB-SMF, AMF, and NG-RAN. The AF stops the stream and initiates MBS Session Deletion. The MB-SMF sends a context release request to the AMF. The AMF sends a resource release request to the NG-RAN. The NG-RAN stops PTM delivery and sends a Leave message (6a) or releases a unicast DL tunnel (6b). The NG-RAN sends a resource release response to the AMF. The AMF sends a context release response to the MB-SMF. Finally, the AF starts a TMGI de-allocation procedure. + +**Figure 7.3.2-1: MBS Session Release for Broadcast** + +1. The AF/AS may stop the media stream before sending the MBS Session Release Request (TMGI) message to the 3GPP network. +2. The AF/AS performs MBS Session Deletion procedure to request release of MBS Session (steps 1 ~ 10 in figure 7.1.1.4-1, or steps 1 ~ 15 in figure 7.1.1.5-1). +3. MB-SMF sends Namf\_MBSBroadcast\_ContextRelease request (TMGI) to the AMF(s) that has been involved in the MBS Session. +4. The AMF sends an N2 message to all RAN nodes that have been involved to release MBS session. If a NG-RAN node receives multiple N2 message to release the MBS Session for the same TMGI (e.g. from several AMFs the NG-RAN is connected to), NG-RAN only performs step 5 and step 6 once. +5. The NG-RAN stops the PTM transmission and stops TMGI advertisement for the MBS Session. + +Depending on whether multicast or unicast transport is used over N3mb, step 6a or step 6b is executed. + +- 6a. If N3mb multicast transport has been used, the NG-RAN sends a Leave message (LL SSM) to stop the media stream to this NG-RAN node. +- 6b. If N3mb unicast transport has been used, the NG-RAN releases its unicast DL N3mb Tunnel endpoint. +7. NG-RAN deletes the MBS Session Context of the broadcast MBS Session. The NG-RAN reports successful release of resources for the MBS Session by sending MBS Session Resource Release Response (TMGI) message(s) to the AMF(s). +8. The AMF sends Namf\_MBSBroadcast\_ContextRelease response (TMGI) to the MB-SMF. +9. The AF may start a TMGI de-allocation procedure (steps 11 ~ 14 in figure 7.1.1.4-1, or steps 16 ~ 19 in figure 7.1.1.5-1). + +### 7.3.2a MBS Session Release for resource sharing across multiple broadcast MBS Sessions during network sharing + +To support resource sharing across multiple broadcast MBS Sessions, in addition to clause 7.3.2, the following enhancement applies: + +- Step 5: + - If the NG-RAN determines there are other associated broadcast MBS Sessions based on the Associated Session Identifier, the step 5 is skipped. + +- Step 6a: + - If the NG-RAN skipped joining the multicast group (LL SSM) in clause 7.3.1a, the NG-RAN does not send a Leave message (LL SSM), + - Otherwise, if the NG-RAN joined the multicast group (LL SSM) previously, and if the NG-RAN determines there are other associated broadcast MBS Sessions based on the Associated Session Identifier, the NG-RAN may trigger procedure of Transport change for resource sharing across broadcast MBS Sessions during network sharing as specified in clause 7.3.7. +- Step 6b: + - If the DL N3mb Tunnel for the broadcast MBS Session was not allocated previously in clause 7.3.1a, step 6b is skipped. + +Otherwise, if the DL N3mb Tunnel for the broadcast MBS Session was allocated previously, and if the NG-RAN determines there are other associated broadcast MBS Sessions based on the Associated Session Identifier, the NG-RAN may trigger the procedure of Transport change for resource sharing across broadcast MBS Sessions during network sharing as specified in clause 7.3.7. + +### 7.3.3 MBS Session Update for Broadcast + +The MBS Session Update for broadcast is used by the AF to update the broadcast area or service requirements of the MBS Session which may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s). + +![Sequence diagram for MBS Session Update for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, AF. The sequence starts with the AF sending an 'MBS session update' request to the NEF/MBSF. The NEF/MBSF then sends a 'Namf_MBSBroadcast_ContextUpdate Request' to the AMF. The AMF sends an 'MBS Session Resource update request' to the NG-RAN. The NG-RAN performs an 'MBS Session Ctx Update' and sends a response back to the AMF. The AMF then sends a 'Namf_MBSBroadcast_ContextUpdate Response' to the NEF/MBSF. The NEF/MBSF sends an 'N4mb Session Modification' to the MB-UPF. The MB-UPF sends an 'MBS Session Resource update rsp' to the AMF. The AMF sends a 'Namf_MBSBroadcast_ContextStatusNotify Request' to the NEF/MBSF. The NEF/MBSF sends another 'N4mb Session Modification' to the MB-UPF. Finally, the NG-RAN updates the MBS Session and sends a response to the AMF.](ca5555bb37f54857199d243feff8479e_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant MB-SMF + participant AMF + participant NG-RAN + participant UE + participant MB-UPF + + Note right of AF: 1. MBS session update in Figure 7.1.1.6-1 or 7.1.1.7-1 + AF->>NEF/MBSF: + NEF/MBSF->>MB-SMF: + MB-SMF->>AMF: 2. Namf_MBSBroadcast_ContextUpdate Request () + AMF->>NG-RAN: 3.MBS Session Resource update request + Note left of NG-RAN: 4. MBS Session Ctx Update + NG-RAN->>AMF: 5.MBS Session Resource update rsp + AMF->>NEF/MBSF: 6. Namf_MBSBroadcast_ContextUpdate Response + Note left of NG-RAN: 7. NG-RAN updates MBS Session + AMF->>MB-UPF: 6a. N4mb Session Modification + MB-UPF-->>AMF: 8.MBS Session Resource update rsp + AMF->>NEF/MBSF: 9. Namf_MBSBroadcast_ContextStatusNotify Request + NEF/MBSF->>MB-UPF: 10. N4mb Session Modification + +``` + +Sequence diagram for MBS Session Update for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, AF. The sequence starts with the AF sending an 'MBS session update' request to the NEF/MBSF. The NEF/MBSF then sends a 'Namf\_MBSBroadcast\_ContextUpdate Request' to the AMF. The AMF sends an 'MBS Session Resource update request' to the NG-RAN. The NG-RAN performs an 'MBS Session Ctx Update' and sends a response back to the AMF. The AMF then sends a 'Namf\_MBSBroadcast\_ContextUpdate Response' to the NEF/MBSF. The NEF/MBSF sends an 'N4mb Session Modification' to the MB-UPF. The MB-UPF sends an 'MBS Session Resource update rsp' to the AMF. The AMF sends a 'Namf\_MBSBroadcast\_ContextStatusNotify Request' to the NEF/MBSF. The NEF/MBSF sends another 'N4mb Session Modification' to the MB-UPF. Finally, the NG-RAN updates the MBS Session and sends a response to the AMF. + +Figure 7.3.3-1: MBS Session Update for Broadcast + +1. The AF starts MBS session update procedure by sending Nnef\_MBSSession\_Update Request to the NEF/MBSF with TMGI (steps 1-6 and steps 9-10 in Figure 7.1.1.6-1, or steps 1-12 and steps 15-16 in Figure 7.1.1.7-1). The AF may adjust service requirement and/or broadcast area. The service requirements adjustment may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s). +2. The MB-SMF sends Namf\_MBSBroadcast\_ContextUpdate Request (TMGI, N2 SM information (MBS Session ID, [MBS QoS profile], [service area(s)], [Area Session ID(s)], [MBS IP Multicast Tunnel Info(s)], [MBS FSA ID(s)], [updated MBS service area]) to the AMFs. For a location dependent service, the MB-SMF may provide information about several location areas. If the broadcast area is updated, the MB-SMF may use NRF to discover + +the AMF(s) based on the new broadcast area and select the appropriate one(s). The MB-SMF may include a maximum response time in the request. + +Depending on the change of the MBS service area, the MB-SMF may send Namf\_MBSBroadcast\_ContextCreate to some AMFs in the new MBS service area, Namf\_MBSBroadcast\_ContextRelease to some other AMFs in the old MBS service area. + +3. The AMF sends MBS Session Resource Update to NG-RANs with TMGI, the updated 5G QoS Profile and the updated MBS service area. + +Depending on the change of the MBS service area, the AMF may send MBS Session Resource Setup to some NG-RANs in new MBS service area (see clause 7.3.1) and MBS Session Resource Release to some other NG-RANs in old MBS service area. + +4. The NG-RAN updates MBS Session Context. + +5. The NG-RAN reports successful update of the MBS Session resources (which may include multiple MBS QoS Flows) by sending MBS Session Resource Update Response (TMGI, N2 SM information ([N3mb DL Tunnel Info])) message(s) to the AMF. N3mb DL Tunnel Info is only available when unicast transport applies between MB-UPF and NG-RAN and the NG-RAN wants the transport to be changed. The NG-RAN should be ready to receive using the N3mb DL tunnel. For more details, refer to TS 38.413 [15]. + +6. The AMF sends Namf\_MBSBroadcast\_ContextUpdate Response to the MB-SMF. If the AMF received the NG-RAN responses from all involved NG-RAN(s), the AMF should include an indication of completion of the operation in all NG-RANs. If received from NG-RAN node, the N3mb DL Tunnel Info and corresponding NG-RAN ID are included in the response. + +- 6a. [Conditional] If MBS service area is changed in such a manner that NG-RAN nodes are added or removed from handling the MBS session, and N3mb unicast transport is used. + +- In a deployment where NG-RAN nodes share a common user plane entity, the MB-SMF perform as following: + - For the NG-RAN node to be added, the MB-SMF only establishes the shared tunnel towards the DL GTP tunnel endpoint if the shared tunnel has not yet been established (as determined based on the stored DL GTP Tunnel endpoint(s) for the MBS session). The MB-SMF also stores the received DL GTP Tunnel and corresponding NG-RAN Node ID for the MBS session. + - For the NG-RAN node to be removed, the MB-SMF removes the received NG-RAN Node ID and possibly DL GTP tunnel endpoint from the stored NG-RAN Node ID(s) for the DL GTP tunnel endpoint for the MBS session, and checks whether the DL GTP tunnel is in use by other NG-RAN nodes based on the stored NG-RAN Node ID(s) for DL GTP tunnel endpoint for the MBS session. If the related DL GTP tunnel is not in use by other NG-RAN nodes, the N3mb unicast transport tunnel shall be removed. +- In a deployment where NG-RAN nodes do not share a common user plane entity, the MB-SMF always establishes or releases the shared tunnel towards the DL GTP tunnel endpoint if NG-RAN nodes are added or removed from handling the MBS session. + +If the N3mb unicast transport tunnel need to be added or removed, the SMF sends an N4mb Session Modification Request to the MB-UPF to establish or release the N3mb unicast transport tunnel for establishing, or releasing the MBS stream for the MBS Session. + +7. The NG-RAN updates the MBS Session. It takes place in parallel with step 5 to step 6. + +- 8 Another NG-RAN may report successful update of the MBS Session resources (which may include multiple MBS QoS Flows) by sending MBS Session Resource Update Response (TMGI, N2 SM information ([N3mb DL Tunnel Info])) message after the AMF transferred the Namf\_MBSBroadcast\_ContextUpdate Response () to the MB-SMF. N3mb DL Tunnel Info is only available when unicast transport applies between MB-UPF and NG-RAN and the NG-RAN wants the transport to be changed. The NG-RAN should be ready to receive using the N3mb DL tunnel. For more details, refer to TS 38.413 [15]. + +9. The AMF transfers the Namf\_MBSBroadcast\_ContextStatusNotify request () to the MB-SMF. When the AMF receives the response from all NG-RAN nodes, the AMF should include an indication of completion of the operation in all NG-RANs. If the AMF does not receive responses from all NG-RAN nodes before the maximum response time elapses since the reception of the Namf\_MBSBroadcast\_ContextUpdate Request, then the AMF + +should transfer the Namf\_MBSBroadcast\_ContextStatusNotify request () which indicates partial success or failure. If received from NG-RAN node, the N3mb DL Tunnel Info and corresponding NG-RAN ID are included in the request. + +10. [Conditional] If MBS service area is changed in such a manner that NG-RAN nodes are added or removed from handling the MBS session, and N3mb unicast transport is used, the MB-SMF establishes or releases the shared delivery tunnel via unicast N3mb transport for the MBS Session in the same manner as described in step 6a. + +### 7.3.4 Support for Location dependent Broadcast Service + +The clause describes procedures to support the Location dependent broadcast service as described in clause 6.2. + +The MBS session creation procedure is performed as defined in clause 7.1.1.2 with the following additions: + +- Multiple AFs may start the same Broadcast MBS session with different content in different MBS service areas. The NEF selects MB-SMF as ingress control node(s) for different MBS service areas. +- If presented, the NEF maps possible external identifiers for MBS service areas to network-internal identifiers (e.g. list of cells, TAIs). +- An NEF/MBSF uses the service area to discover the MB-SMF. + +If different MB-SMFs are assigned for different MBS service areas belonging to different MB-SMF service areas for an MBS session as specified in clause 6.2.3, an MB-SMF shall accept TMGIs allocated by other MB-SMF. + +- For Location dependent Broadcast Service, MB-SMF allocates Area Session ID, and updates its NF profile towards the NRF with the TMGI and Area Session ID. +- The MB-SMF may select the MB-UPF based on the MBS service area. +- The MBS service area(s) are indicated to the UE in the Service Announcement as defined in clause 6.11. + +The MBS session establishment procedure is performed as defined in clauses 7.3.1 and 7.3.1a with the following additions or clarification: + +- MB-SMF requests the AMF to transfer an N2 message (i.e. MBS Session Resource Setup Request) to the NG-RAN nodes of the MBS service area with Broadcast MBS session information which additionally includes the Area Session IDs and MBS service areas. +- The NG-RAN uses the received MBS Session ID and Area Session IDs to determine the local Broadcast MBS session contexts. +- The NG-RAN responds for service areas it handles with the Area Session ID(s) and DL tunnel endpoint(s) for the DL tunnel(s) from MB-SMF if unicast transport applies over N3mb between MB-UPF and NG-RAN. +- According to the Area Session ID(s) and DL tunnel endpoint(s) provided by NG-RAN, the MB-SMF instructs the MB-UPF to send location dependent content. +- The AF transmits the DL media streams to MB-UPF via tunnels to differentiate the content delivered to different areas. + +### 7.3.5 MBS Session Delivery Status Indication for Broadcast + +The MBS Session Delivery Status Indication for broadcast is used by the MB-SMF to notify the AF/AS of conditions affecting the delivery of the MBS session (e.g. MBS session created, MBS session terminated, etc.). The occurrence of the indicated condition may have been detected at the MB-SMF or may have been reported to the MB-SMF by other entities involved in the MBS session delivery. + +![Sequence diagram for MBS Session Delivery Status Indication for Broadcast. Lifelines: MB-SMF, NEF, MBSF, AF, AS. The diagram shows two main paths for delivery status indication. Path 1: AF/AS sends a request to NEF (1a-1), NEF to MB-SMF (1a-2), MB-SMF to NEF (1a-3), and NEF to AF (1a-3). Path 2: AS sends a request to MBSF (1b-1), MBSF to MB-SMF (1b-2), MB-SMF to AF (1c), and MB-SMF to NEF (2a-1). Path 3: NEF sends a notification to AF (2a-2). Path 4: MB-SMF sends a notification to MBSF (2b-1), MBSF to AS (2b-2), and MB-SMF to AF (2c).](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant AF + participant AS + participant MB-SMF + participant NEF + participant MBSF + + Note right of AF: 1a-1. Nnef_MBSSession_Create request (TMGI, Delivery Status) + AF->>NEF: 1a-1. Nnef_MBSSession_Create request (TMGI, Delivery Status) + NEF->>MB-SMF: 1a-2. Nmbsmf_MBSSession_Create (TMGI, Delivery Status) + MB-SMF-->>NEF: 1a-3. Nnef_MBSSession_Create response + NEF-->>AF: 1a-3. Nnef_MBSSession_Create response + + Note right of AS: 1b-1. MBS operation with status report required + AS->>MBSF: 1b-1. MBS operation with status report required + MBSF->>MB-SMF: 1b-2. Nmbsmf_MBSSession_Create (TMGI, Delivery Status) + MB-SMF-->>AF: 1c. Nmbsmf_MBSSession_Create (TMGI, Delivery Status) + + Note right of MB-SMF: 2a-1. Nmbsmf_MBSSession_StatusNotify (TMGI, condition) + MB-SMF->>NEF: 2a-1. Nmbsmf_MBSSession_StatusNotify (TMGI, condition) + NEF-->>AF: 2a-2. Nnef_MBSSession_StatusNotify (TMGI, condition) + + Note right of MB-SMF: 2b-1. Nmbsmf_MBSSession_StatusNotify (TMGI, condition) + MB-SMF->>MBSF: 2b-1. Nmbsmf_MBSSession_StatusNotify (TMGI, condition) + MBSF-->>AS: 2b-2. Delivery Status Indication (TMGI, condition) + + Note right of MB-SMF: 2c. Nmbsmf_MBSSession_StatusNotify (TMGI, condition) + MB-SMF-->>AF: 2c. Nmbsmf_MBSSession_StatusNotify (TMGI, condition) + +``` + +Sequence diagram for MBS Session Delivery Status Indication for Broadcast. Lifelines: MB-SMF, NEF, MBSF, AF, AS. The diagram shows two main paths for delivery status indication. Path 1: AF/AS sends a request to NEF (1a-1), NEF to MB-SMF (1a-2), MB-SMF to NEF (1a-3), and NEF to AF (1a-3). Path 2: AS sends a request to MBSF (1b-1), MBSF to MB-SMF (1b-2), MB-SMF to AF (1c), and MB-SMF to NEF (2a-1). Path 3: NEF sends a notification to AF (2a-2). Path 4: MB-SMF sends a notification to MBSF (2b-1), MBSF to AS (2b-2), and MB-SMF to AF (2c). + +**Figure 7.3.5-1: MBS Session Delivery Status Indication for Broadcast** + +1. The external AF subscribes event for delivery status towards the NEF, and the NEF subscribes corresponding event towards the MB-SMF (step 1a), or the legacy AS request status report towards the MBSF, and the MBSF subscribes event for delivery status towards the MB-SMF (step 1b), or the internal AF subscribes event for delivery status towards the MB-SMF (step 1c). +2. The MB-SMF notifies the TMGI and the event towards the NEF, and the NEF notifies the TMGI and corresponding event towards the external AF (step 2a), or the MB-SMF notifies the TMGI and the event towards the MBSF, and the MBSF sends Delivery Status Indication to legacy AS with the TMGI and the corresponding event (step 2b), or the MB-SMF notifies the TMGI and the event towards the internal AF (step 2c). + +For the "MBS session started" event, after the MB-SMF contacts AMFs to request the establishment of the Broadcast MBS session, the MB-SMF may wait until it has received a Namf\_MBSSession\_CreateResponse or Namf\_MBSSession\_StatusNotify with the indication of the completion of the operation from each AMF (see clause 7.3.1) before determining that the Broadcast MBS session has been started. + +### 7.3.6 Broadcast MBS Session Release Require + +When NG-RAN is not able continue to provide the Broadcast MBS Session, e.g. due to lack of radio resources, NG-RAN may initiate Broadcast Session Release Require procedure. + +![Sequence diagram for Broadcast MBS Session Release Require. The diagram shows the interaction between UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, and AF. The process starts with the NG-RAN sending a 'Broadcast Session Release Require (MBS Session ID)' to the AMF. The AMF then initiates a 'Broadcast Session Release' towards the NG-RAN (steps 4-7 of Figure 7.3.2-1). The AMF then sends a 'Namf_MBSBroadcast_ContextStatusNotify' to the MB-SMF. The MB-SMF sends a 'Nmbsmf_MBSSession_StatusNotify' to the NEF/MBSF, which in turn sends a 'Nnef_MBSSession_StatusNotify' to the AF. Finally, the MB-SMF sends an 'N4mb Session Modification' to the MB-UPF.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant NEF/MBSF + participant AF + + NG-RAN->>AMF: 1. Broadcast Session Release Require (MBS Session ID) + AMF->>NG-RAN: 2. Broadcast Session Release (step 4 – 7 of Figure 7.3.2-1) + AMF->>MB-SMF: 3. Namf_MBSBroadcast_ContextStatusNotify + MB-SMF->>NEF/MBSF: 3a. Nmbsmf_MBSSession_StatusNotify + NEF/MBSF->>AF: 3b. Nnef_MBSSession_StatusNotify + MB-SMF->>MB-UPF: 4. N4mb Session Modification + +``` + +Sequence diagram for Broadcast MBS Session Release Require. The diagram shows the interaction between UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, and AF. The process starts with the NG-RAN sending a 'Broadcast Session Release Require (MBS Session ID)' to the AMF. The AMF then initiates a 'Broadcast Session Release' towards the NG-RAN (steps 4-7 of Figure 7.3.2-1). The AMF then sends a 'Namf\_MBSBroadcast\_ContextStatusNotify' to the MB-SMF. The MB-SMF sends a 'Nmbsmf\_MBSSession\_StatusNotify' to the NEF/MBSF, which in turn sends a 'Nnef\_MBSSession\_StatusNotify' to the AF. Finally, the MB-SMF sends an 'N4mb Session Modification' to the MB-UPF. + +**Figure 7.3.6-1: Broadcast MBS Session Release Require** + +1. If NG-RAN cannot continue to provide the Broadcast MBS session, e.g. due to lack of radio resources, the NG-RAN sends Broadcast Session Release Require (MBS Session ID) to the AMF. +2. The AMF initiates Broadcast Session Release towards the NG-RAN as defined in steps 4 - 7 in clause 7.3.2. +3. If unicast transport applies in N3mb, the AMF receives the DL tunnel Info for the Broadcast MBS Session from the NG-RAN in step 2. The AMF notifies the MB-SMF about the DL tunnel release via Namf\_MBSBroadcast\_ContextStatusNotify with N3mb DL Tunnel Info and corresponding NG-RAN ID. If multicast transport applies in N3mb, only when Broadcast Session Release Require is performed for all the NG-RANs involved in the MBS session which are managed by the AMF, the AMF notifies the MB-SMF about radio resource release via Namf\_MBSBroadcast\_ContextStatusNotify indicating radio resource release. +- 3a-3b. This step applies if the AF subscribed to a Delivery Status Indication (see clause 7.3.5). If Broadcast Session Release Require is performed by all the NG-RANs, i.e. for unicast N3mb transport, the MB-SMF releases all the DL tunnel Info for the broadcast MBS Session, and for multicast N3mb transport, the MB-SMF receives radio resource release from all the AMFs for the broadcast MBS Session, the MB-SMF notifies the AF directly of the situation by invoking Nmbsmf\_MBSSession\_StatusNotify, or the MB-SMF notifies the AF via NEF/MBSF (if deployed) by invoking Nmbsmf\_MBSSession\_StatusNotify service operation to the NEF/MBSF which then invokes Nnef\_MBSSession\_StatusNotify service operation to the AF +4. The MB-SMF performs N4mb Session Modification to let MB-UPF stop the broadcast data forwarding towards the indicated DL tunnel and release the DL tunnel as specified in step 6a of clause 7.3.3. + +### 7.3.7 Transport change for resource sharing across broadcast MBS Sessions during network sharing + +The procedure in this clause is performed when one of the following events occur and resource sharing across broadcast MBS Sessions in network sharing as specified in clause 6.18 is applied: + +- When a broadcast MBS session, from which the shared NG-RAN receives a DL MBS data stream, is released, and the NG-RAN node determines to request to receive an DL MBS data stream from another operator's CN with a remaining broadcast MBS session. +- When the shared NG-RAN fails to receive DL data stream from an operator's CN (e.g. due to failure in the user plane) and the NG-RAN node determines to request to receive the DL MBS data stream via another operator's CN. + +![Sequence diagram illustrating the transport change for resource sharing across broadcast MBS Sessions during network sharing. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, and MB-UPF. The NG-RAN selects a CN to establish user plane, then sends IGMP/MLD Join to MB-UPF. The NG-RAN sends a Broadcast Session Transport Request to the AMF. The AMF sends a Namf_MBSBroadcast_ContextStatusNotify Request to the MB-SMF. The MB-SMF returns a response. The AMF sends a Broadcast Session Transport Response to the NG-RAN. The MB-SMF sends an N4mb Session Modification to the MB-UPF. The NG-RAN receives media streams from the MB-UPF and performs PTM transmission to the UE.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + + Note right of NG-RAN: 1. Select a CN to establish user plane + NG-RAN->>MB-UPF: 2. IGMP/MLD Join + NG-RAN->>AMF: 3. Broadcast Session Transport Request (MBS Session ID, N3mb DL Tunnel Info) + AMF->>MB-SMF: 4. Namf_MBSBroadcast_ContextStatusNotify Request (MBS Session ID, N3mb DL Tunnel Info) + MB-SMF-->>AMF: 4a. Namf_MBSBroadcast_ContextStatusNotify Response + AMF-->>NG-RAN: 6. Broadcast Session Transport Response (MBS Session ID) + MB-SMF->>MB-UPF: 5. N4mb Session Modification + MB-UPF->>NG-RAN: 7. Media Streams + NG-RAN->>UE: 8. PTM transmission + +``` + +Sequence diagram illustrating the transport change for resource sharing across broadcast MBS Sessions during network sharing. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, and MB-UPF. The NG-RAN selects a CN to establish user plane, then sends IGMP/MLD Join to MB-UPF. The NG-RAN sends a Broadcast Session Transport Request to the AMF. The AMF sends a Namf\_MBSBroadcast\_ContextStatusNotify Request to the MB-SMF. The MB-SMF returns a response. The AMF sends a Broadcast Session Transport Response to the NG-RAN. The MB-SMF sends an N4mb Session Modification to the MB-UPF. The NG-RAN receives media streams from the MB-UPF and performs PTM transmission to the UE. + +**Figure 7.3.7-1: Transport change for resource sharing across broadcast MBS Sessions during network sharing** + +1. The NG-RAN selects another broadcast MBS Session that is delivering the same content via another CN to establish user plane, utilizing the broadcast MBS session context stored in the NG-RAN. + +If unicast transport of N3mb applies, continue at step 3. + +NOTE: Which CN is to be selected is up to NG-RAN implementation. + +2. If multicast transport of N3mb applies, the NG-RAN joins the multicast group towards the LL SSM provided by the CN and continues at step 8. +3. If unicast transport of N3mb applies, the NG-RAN allocates N3mb DL Tunnel Info, and sends N2 message (e.g. BROADCAST SESSION TRANSPORT REQUEST) to the AMF, including the MBS Session ID, the N3mb DL Tunnel Info and optional Area session ID. +4. The AMF transfers the Namf\_MBSBroadcast\_ContextStatusNotify request to the MB-SMF, which contains the N2 message. +- 4a. The MB-SMF returns Namf\_MBSBroadcast\_ContextStatusNotify response. +5. The MB-SMF sends an N4mb Session Modification Request to the MB-UPF to allocate the N3mb point-to-point transport tunnel for a replicated MBS stream for the MBS Session. The MB-UPF sends N4mb Session Modification Response to the MB-SMF. +6. The AMF forwards the received N2 information in N2 message (e.g. BROADCAST SESSION TRANSPORT RESPONSE) to the NG-RAN. +7. The NG-RAN receives the media stream from the MB-UPF via N3mb multicast transport or unicast transport. +8. The NG-RAN sends the received packets using the existing radio resource. + +### 7.3.8 Broadcast MBS procedures for UEs using power saving functions + +For a UE using power saving function to receive broadcast MBS Session data, the following apply: + +- If a UE is in RRC\_CONNECTED mode due to other reasons at the start time or the scheduled activation times, the UE follows normal connected mode procedures. + +- If a UE is in RRC\_IDLE state and reachable (e.g. in active time in MICO or PTW for eDRX) at the start time or the scheduled activation times) the UE follows normal idle mode or inactive mode procedures), the UE follows normal idle mode procedure. +- If a UE is in RRC\_IDLE mode or CM-CONNECTED with RRC\_INACTIVE state and not reachable (i.e. in deep sleep) at the start time or the scheduled activation times, the UE leaves the deep sleep state only to perform procedures related to MBS, the UE leaves the deep sleep state only to receive the MBS broadcast service, but should not update the AMF to become reachable for paging to minimize signalling load. + +NOTE 1: UE would therefore still be considered unreachable for paging in the AMF. + +- When the UE is in the middle of an MBS data transfer, and the UE is scheduled to move to deep sleep due to power saving, e.g. end of PTW for extended idle mode DRX, expiration of active time for MICO, or the UE transitioning from CM-CONNECTED to CM-CONNECTED with RRC\_INACTIVE state with eDRX or the UE transitioning from CM-CONNECTED to CM-IDLE in the case of MICO with no active time, then the UE does not go to deep sleep during the remainder of the current MBS data transfer. + +NOTE 2: If at the end of the current MBS data transfer the UE knows there is another MBS data transfer scheduled soon, depending on the time between MBS data transfers, the UE can decide to go to sleep between MBS data transfers. + +## 7.4 MBS procedures for inter System Mobility + +### 7.4.1 Inter-system mobility with interworking at service layer + +For inter-system mobility with interworking at service layer, i.e. the same multicast service is provided via eMBMS in E-UTRAN and MBS, the UE is instructed to switch between MBS and eMBMS: + +NOTE 1: The source network can be configured with the frequencies where the same service is provided in the target network, i.e. the EPC network neighbouring the 5GC network support the same eMBMS service. + +NOTE 2: The UE can be configured, per TMGI, to know that the same service is provided over MBS and eMBMS. + +- Mobility from MBS to eMBMS. + +When moving to E-UTRAN/EPC, the UE initiates procedures as defined in TS 23.246 [8] to receive MBMS service for the TMGI(s). + +If the UE has one or more unicast PDU Sessions (including, but not limited to, the PDU Session used for MBS and for another service (e.g. Public Safety service) with the QoS Flow(s) for the other service) moving to EPS, and if the handover procedure from 5GS to EPS using N26 interface described in clause 4.11.1.2.1 of TS 23.502 [6] is used: + +- For the PDU Session used also for MBS, the SMF+PGW-C removes the UE from the Multicast MBS session context(s), if it exists, upon receiving a Modify Bearer Request of the PDU Session from the SGW (i.e. step 14a of clause 4.11.1.2.1 of TS 23.502 [6]). + +NOTE 3: When 5GS to EPS mobility is complete, if there is pending request of removing a UE from a released MBS Session (see step 2 of clause 7.2.2.3), the pending request is also removed locally. + +- The NG-RAN removes the UE from the Multicast MBS session context(s) if it exists, or removes the whole multicast session context if the UE is the last one for the Multicast MBS session (e.g. after receiving the UE Context Release Command message sent by the AMF). + +For 5GS to EPS Idle mode mobility with no N26, when the UE moves to the EPS and performs E-UTRAN/EPS attach according to step 8 of clause 4.11.2.4.1 of TS 23.502 [6], if the UE does not maintain registration in 5GC, upon reachability time-out, the AMF may implicitly detach the UE and release the possible remaining PDU Session(s) in 5GC. The SMF+PGW-C removes the UE from the Multicast MBS session context(s), if it exists, upon receiving a tracking area update from the UE. + +NOTE 4: When 5GS to EPS mobility is complete, if there is pending request of removing a UE from a released MBS Session (see step 2 of clause 7.2.2.3), the pending request is also removed locally. + +- Mobility from eMBMS to MBS. + +When the UE has moved to NR/5GC, it triggers the multicast context and multicast flow setup/modification via PDU Session Modification procedures as defined in clause 6.8 to receive MBS transport for the TMGI(s). + +## 7.5 MBS procedures for Group Message Delivery + +### 7.5.1 Group Message Delivery via MBS Broadcast + +![Sequence diagram for Group Message Delivery via MBS Broadcast. Lifelines: UE, RAN, 5GC, MBSF, MBSTF, NEF, AF. The process involves request, authorization, file transformation, session creation, provisioning, announcement, delivery, and status notification.](aa22da43c463563d3d0035722bd79449_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant MBSTF + participant MBSF + participant 5GC + participant RAN + participant UE + + Note right of NEF: 1. Nnef_MBSGroupMsg_Create Request + Note right of NEF: 2. Authorization + Note right of NEF: 3. Transforms the group message payload into a file, and determine the user service information + Note right of MBSTF: 4. Application Service Provisioning + Note right of 5GC: 5. MBS Session Creation + Note right of RAN: 7. MBS Session Start for broadcast + Note right of MBSTF: 6. Distribution Session Provisioning + Note right of RAN: 8. MBS User Service Announcement + Note right of AF: 9. Nnef_MBSGroupMsgDelivery_Create Response + Note right of 5GC: 10. Application Service Announcement + Note right of MBSTF: 11. User Data Ingestion + Note right of MBSTF: 12. FEC Encoding and packetization + Note right of RAN: 13. packet delivery over MBS broadcast + Note right of UE: 14. Get group message from file + Note right of MBSTF: 15. User Data distribution status notify and User Data Ingestion Status Notify + Note right of NEF: 16. Nnef_MBSGroupMsgDelivery_StatusNotify + +``` + +Sequence diagram for Group Message Delivery via MBS Broadcast. Lifelines: UE, RAN, 5GC, MBSF, MBSTF, NEF, AF. The process involves request, authorization, file transformation, session creation, provisioning, announcement, delivery, and status notification. + +Figure 7.5.1-1: Group Message Delivery via MBS Broadcast + +NOTE 1: The steps in this clause for group message delivery to the UE(s) follow the procedures specified in TS 26.502 [18], where the NEF acts as an MBS Application Provider. + +1. The AF sends Nnef\_MBSGroupMsgDelivery\_Create Request to the NEF. The Request message contains the Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time and External Group Identifier. +2. The NEF checks authorization of the AF. If geographical area information or civic address information was provided by the AF as MBS service area, the NEF translates the MBS service area to Cell ID list or TAI list. The NEF may further check the MBS capability within the MBS service area. + +NOTE 2: The NEF is mandated for group message delivery. + +3. The NEF transforms the group message payload into a file, and determines the meta data information of the file (e.g. File URL, etc.). The NEF assigns a Group Message Correlation ID that identifies this group message delivery request. + +If Application Service Provisioning specified in TS 26.502 [18] has not been performed, step 4 to step 8 are executed. Otherwise, they can be skipped. + +4. The NEF performs Application Service Provisioning by invoking Nmbf\_MBSUserService\_Create and Nmbf\_MBSUserDataIngestSession\_Create towards the MBSF using Object Distribution Method as specified in TS 26.502 [18]. +5. The MBSF performs MBS Session Creation as specified in clause 7.1.1.2 or clause 7.1.1.3. +6. The MBSF performs Distribution Session Provisioning as specified in TS 26.502 [18]. The MBSF invokes Nmbstf\_MBSDistributionSession\_Create on the MBSTF, passing the parameters of the MBS Distribution Session received in step 4 to the MBSTF. +7. The MB-SMF initiates the MBS Session Start for Broadcast procedure as specified in step 2 to step 9 in clause 7.3.1. +8. If the MBSF performs the service announcement, it initiates the MBS User Service Announcement as specified in TS 26.502 [18]. The application may receive the appropriate information through the MBS-6 API from the MBS Client (see TS 26.502 [18]). The NEF may receive the service announcement information via Nmbf\_MBSUserDataIngestSession\_StatusNotify callback service operation (see TS 26.502 [18]). +9. The NEF sends Nnef\_MBSGroupMsgDelivery\_Create Response (Group Message Correlation ID, Acceptance Status, Cause) to the AF. The Acceptance Status indicates whether the group message delivery request is accepted or not. If not, the Cause is included indicating the appropriate failure reason. If the AF performs the service announcement, the NEF includes in the Group Message Response the service announcement information which contains information such as Session Description parameters (e.g. TMGI) and the object meta data as specified in TS 26.502 [18]. The NEF may further include the area where MBS is not supported within the MBS service area in the Nnef\_MBSGroupMsgDelivery\_Create response to the AF. + +If the AF knows the UEs that are located in the area where MBS is not supported, AF may use unicast to send the group message to those UEs. + +10. If the AF needs to perform the Service Announcement, the AF sends the application service announcement to the UE as specified in TS 26.502 [18]. +11. The NEF performs the User Data Ingestion towards the MBSTF as specified in TS 26.502 [18]. The NEF may push the file to the MBSTF or let MBSTF pull the file from the NEF. +12. The MBSTF performs packetization and optionally FEC encoding as specified in TS 26.502 [18]. +13. The MBSTF delivers the packets to the MB-UPF to NG-RAN, and NG-RAN broadcast to the UE as specified in step 13 to step 15 in clause 7.3.1. +14. Based on the service announcement information received in step 8 or step 10, when the UE receives the packets, the MBS client performs FEC decoding to restore the file and gets the group message from the file, as specified in TS 26.502 [18]. The MBS Client can expose the file towards the application in the UE using the MBS-7 API (see TS 26.502 [18]). +15. The MBSTF notifies the MBSF of User Data distribution status, and the MBSF then notifies the MBSF of the User Data ingestion status as specific in TS 26.502 [18]. +16. The NEF sends Nnef\_MBSGroupMsgDelivery\_StatusNotify to the AF, containing Group Message Correlation ID, Delivery Status. The Delivery Status indicates whether delivery of Group Message Payload is successful or not. The delivery status information is received by the NEF via Nmbf\_MBSUserDataIngestSession\_StatusNotify service operation (see TS 26.502 [18]). + +## 7.5.2 Modification of previously submitted Group message + +![Sequence diagram illustrating the modification of previously submitted Group message delivery via MBS Broadcast. The diagram shows interactions between UE, RAN, 5GC, MBSF, MBSTF, NEF, and AF. It is divided into two main sections: 'Group Message Payload update' and 'MBS Service Area update'.](a66383962afcd0f0458f0d45c101fabf_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant MBSTF + participant MBSF + participant 5GC + participant RAN + participant UE + + Note right of AF: Group Message Payload update + AF->>NEF: 1. Nnef_MBSGroupMsg_Update Request + NEF->>NEF: 2. Authorization + Note right of NEF: 3. Transforms the group message payload into a file + NEF->>MBSF: 4. Update MBSUserDataIngestSession (update file) + MBSF->>MBSTF: 5. Update MBSDistributionSession (update file) + Note right of MBSTF: 6. User Data Ingestion + Note right of AF: MBS Service Area update + NEF->>MBSF: 7. Update MBSUserService (update service area) + Note right of RAN: 8. MBS Session Update procedure (updated MBS service area) + NEF->>AF: 9. Nnef_MBSGroupMsg_Update Response + +``` + +Sequence diagram illustrating the modification of previously submitted Group message delivery via MBS Broadcast. The diagram shows interactions between UE, RAN, 5GC, MBSF, MBSTF, NEF, and AF. It is divided into two main sections: 'Group Message Payload update' and 'MBS Service Area update'. + +**Figure 7.5.2-1: Modify Group Message Delivery via MBS Broadcast** + +NOTE: The steps in this clause for modification of group message delivery to the UE(s) follow the procedures specified in TS 26.502 [18], where the NEF acts as an MBS Application Provider. + +1. The AF sends Nnef\_MBSGroupMsg\_Update Request to the NEF. The Request message contains the Group Message Correlation ID, Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time and External Group Identifier. The NEF identifies the associated MBS Service by the external Group Identifier. The Group Message Correlation ID indicates the transaction to be modified. +2. The NEF checks authorization of AF. If geographical area information or civic address information was provided by the AF as MBS service area, the NEF translates the MBS service area to Cell ID list or TAI list. The NEF may further check the MBS capability within the MBS service area. + +For Group Message Payload update, steps 3 to 6 are executed: + +3. The NEF transforms the group message payload into a file, and use the determined file meta data (e.g. File URL, etc.) in clause 7.5.1. +4. If the NEF pushes the updated file to the MBSTF, step 4 to step 5 can be skipped. If the MBSTF pulls the updated file from the NEF, the NEF updates MBS User Data Ingest Session on the MBSF as specified in TS 26.502 [18]. The update service operation needs to indicate an update of the file containing the updated group message. +5. The MBSF updates MBS Distribution Session on the MBSTF as specified in TS 26.502 [18]. The update service operation needs to indicate an update of the file containing the updated group message. +6. The NEF pushes the update file to the MBSTF or the MBSTF pulls the updated file from the NEF. And the MBSTF delivers the updated file towards the MB-UPF in 5GC as specified in clause 4.3.3.2 of TS 26.502 [18]. + +For MBS service area update, step 7 and step 8 are executed: + +7. The NEF updates MBS User Service on the MBSF as specified in TS 26.502 [18]. The update service operation indicates MBS service area update. +8. The MBSF performs MBS Session Update as specified in clause 7.1.1.6 or clause 7.1.1.7 to update MBS service area, which triggers MBS Session Update for Broadcast as specified in clause 7.3.3. +9. The NEF sends Nnef\_MBSGroupMsgDelivery\_Update Response (Acceptance Status, Cause) to the AF. The Acceptance Status indicates whether the group message update request is accepted or not. If not, the Cause is included indicating the appropriate failure reason. The NEF may further include the area where MBS is not supported in the Nnef\_MBSGroupMsgDelivery\_Update response to the AF. + +After the modified group message is delivered, the NEF sends Nnef\_MBSGroupMsgDelivery\_StatusNotify to the AF as described in step 16 in clause 7.5.1. + +### 7.5.3 Cancellation of previously submitted Group message + +![Sequence diagram for cancelling group message delivery via MBS broadcast. The diagram shows interactions between UE, RAN, 5GC, MBSF, MBSTF, NEF, and AF. The process starts with the AF sending a Delete Request to the NEF, followed by authorization, updates to sessions on the MBSF and MBSTF, and finally the NEF sending a response back to the AF. A separate box indicates the MBS Session Deletion procedure.](dcd49ce2814873afd15074efc28a661f_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant MBSTF + participant MBSF + participant 5GC + participant RAN + participant UE + + Note right of AF: 1. Nnef_MBSGroupMsgDelivery_Delete Request + AF->>NEF: 1. Nnef_MBSGroupMsgDelivery_Delete Request + Note right of NEF: 2. Authorization + NEF->>NEF: 2. Authorization + Note right of NEF: 3. Update MBSUserDataIngestSession (cancel file) + NEF-->>MBSF: 3. Update MBSUserDataIngestSession (cancel file) + Note right of MBSF: 4. Update MBSDistributionSession (cancel file) + MBSF-->>MBSTF: 4. Update MBSDistributionSession (cancel file) + Note right of MBSTF: 5. HTTP DELETE + MBSTF-->>NEF: 5. HTTP DELETE + Note right of NEF: 6. Destroy MBSUserDataIngestSession + NEF-->>MBSF: 6. Destroy MBSUserDataIngestSession + Note right of MBSF: 7. Destroy MBSDistributionSession + MBSF-->>MBSTF: 7. Destroy MBSDistributionSession + Note right of RAN: 8. MBS Session Deletion procedure + RAN->>5GC: 8. MBS Session Deletion procedure + Note right of NEF: 9. Nnef_MBSGroupMsgDelivery_Delete Response + NEF->>AF: 9. Nnef_MBSGroupMsgDelivery_Delete Response + +``` + +Sequence diagram for cancelling group message delivery via MBS broadcast. The diagram shows interactions between UE, RAN, 5GC, MBSF, MBSTF, NEF, and AF. The process starts with the AF sending a Delete Request to the NEF, followed by authorization, updates to sessions on the MBSF and MBSTF, and finally the NEF sending a response back to the AF. A separate box indicates the MBS Session Deletion procedure. + +Figure 7.5.3-1: Cancelling Group Message Delivery via MBS Broadcast + +NOTE: The steps in this clause for cancelling the group message delivery to the UE(s) follow the procedures specified in TS 26.502 [18] where the NEF acts as an MBS Application Provider. + +1. The AF sends Nnef\_MBSGroupMsgDelivery\_Delete Request (Group Message Correlation ID, External Group Identifier) to the NEF. The NEF identifies the associated MBS Service by the External Group Identifier. The Group Message Correlation ID indicates the transaction to be cancelled. +2. The NEF checks authorization of the AF. + +Steps 3 to step 5 are executed if the group message delivery has started and MBSF needs to inform the MBS Client about the cancellation of the file delivery. Otherwise, they can be skipped. + +3. The NEF updates MBS User Data Ingest Session on the MBSF as specified in TS 26.502 [18] indicating the cancellation of the file delivery. +4. If the MBSTF pulled the file from the NEF previously, the MBSF updates MBS Distribution Session on the MBSTF as specified in TS 26.502 [18] indicating cancellation of the file delivery and the MBSTF stops the file delivery. +5. If the NEF pushed the file previously to the MBSTF, the NEF may send HTTP DELETE to the MBSTF to cancel the file delivery. The MBSTF stops the file delivery. +6. The NEF destroys MBS User Data Ingest Session on the MBSF as specified in TS 26.502 [18]. + +7. The MBSF destroys MBS Distribution Session on the MBSTF as specified in TS 26.502 [18]. +8. The MBSF performs MBS Session Deletion as specified in clause 7.1.1.4 or clause 7.1.1.5, which includes MBS Session Release for Broadcast as specified in clause 7.3.2. +9. The NEF sends Nnef\_MBSGroupMsgDelivery\_Delete Response (Acceptance Status, Cause) to the AF. The Acceptance Status indicates whether the Nnef\_MBSGroupMsgDelivery\_Delete Request is accepted or not. Cause is included when the Nnef\_MBSGroupMsgDelivery\_Delete Request is not accepted. + +## 8 Control and user plane stacks + +### 8.1 Control plane for Multicast and Broadcast services + +#### 8.1.1 General + +The control plane protocol stacks for Multicast and Broadcast service between NG-RAN and MB-SMF is defined in the clause 8.1.1 and the other control plane protocol stacks for Multicast and Broadcast service are defined in the TS 23.501 [5] clause 8.2. + +The control plane protocols for N4mb reference point between MB-SMF and MB-UPF are defined in TS 29.244 [17]. + +The reference point Nmb2 between MBSF and MBSTF will be defined in TS 26.502 [18] and TS 26.517 [22]. + +#### 8.1.2 NG-RAN – MB-SMF + +![Diagram of the control plane between the NG-RAN and the MB-SMF. The diagram shows three main entities: NG-RAN, AMF, and MB-SMF. The NG-RAN has a protocol stack with layers: N2 SM information (dashed box), NG-AP, SCTP, IP, L2, and L1. The AMF has a similar stack: NG-AP, SCTP, IP, L2, and L1, with a 'Relay' function at the top. The MB-SMF has a stack with N2 SM information (dashed box) and N11mb. Connections: A vertical line labeled 'N2' connects the NG-RAN's NG-AP to the AMF's NG-AP. A horizontal line labeled 'N11mb' connects the AMF's NG-AP to the MB-SMF's N11mb. Dashed lines indicate the relay of 'N2 SM information' from the NG-RAN through the AMF to the MB-SMF.](ccf5afac93b3c3eabb7adfb2b3c88a75_img.jpg) + +Diagram of the control plane between the NG-RAN and the MB-SMF. The diagram shows three main entities: NG-RAN, AMF, and MB-SMF. The NG-RAN has a protocol stack with layers: N2 SM information (dashed box), NG-AP, SCTP, IP, L2, and L1. The AMF has a similar stack: NG-AP, SCTP, IP, L2, and L1, with a 'Relay' function at the top. The MB-SMF has a stack with N2 SM information (dashed box) and N11mb. Connections: A vertical line labeled 'N2' connects the NG-RAN's NG-AP to the AMF's NG-AP. A horizontal line labeled 'N11mb' connects the AMF's NG-AP to the MB-SMF's N11mb. Dashed lines indicate the relay of 'N2 SM information' from the NG-RAN through the AMF to the MB-SMF. + +#### Legend: + +- **N2 SM information:** This is the subset of NG-AP information that the AMF transparently relays between the NG-RAN and the MB-SMF, and is included in the NG-AP messages and the N11mb related messages, where the NG-RAN node has MBS capability and in this Release the NG-RAN is a 3GPP NR. + +**Figure 8.1.1-1: Control Plane between the NG-RAN and the MB-SMF** + +### 8.2 User plane for Multicast and Broadcast services + +The User plane protocol stack for PDU session which handles the multicast operation is same with the PDU session user plane Protocol Stack defined in the TS 23.501 [5] clause 8.3.1. + +The user plane protocol stack for MBS session in case of shared delivery is described in Figure 8.2-1 and Figure 8.2-2. In Figure 8.2-1, the UDP tunnel applies to N6mb and Nmb9, while in Figure 8.2-2, the plain IP multicast applies to N6mb. The user plane protocol stack for MBS session in case of individual delivery is described in Figure 8.2-3. + +![Figure 8.2-1: User Plane Protocol Stack for MBS session (UDP Tunnel). This diagram shows the protocol stack across four entities: UE, NG-RAN, MB-UPF, and AF/MBSTF. The UE contains Application, UDP, IP (MC), and 5G-AN Protocol Layers. The NG-RAN contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and a 5G-AN Protocol Layers block. The MB-UPF contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and another Relay block with GTP-U, UDP, IP (UC), L2, and L1 layers. The AF/MBSTF contains Application, UDP, IP (MC), UDP, IP (UC), L2, and L1 layers. Interfaces N3mb and N6mb/Nmb9 are indicated between the entities.](6e9d059430baba0c363e33749f68b107_img.jpg) + +Figure 8.2-1: User Plane Protocol Stack for MBS session (UDP Tunnel). This diagram shows the protocol stack across four entities: UE, NG-RAN, MB-UPF, and AF/MBSTF. The UE contains Application, UDP, IP (MC), and 5G-AN Protocol Layers. The NG-RAN contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and a 5G-AN Protocol Layers block. The MB-UPF contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and another Relay block with GTP-U, UDP, IP (UC), L2, and L1 layers. The AF/MBSTF contains Application, UDP, IP (MC), UDP, IP (UC), L2, and L1 layers. Interfaces N3mb and N6mb/Nmb9 are indicated between the entities. + +Figure 8.2-1: User Plane Protocol Stack for MBS session (UDP Tunnel) + +![Figure 8.2-2: User Plane Protocol Stack for MBS session (plain IP multicast). This diagram shows the protocol stack across four entities: UE, NG-RAN, MB-UPF, and AF. The UE contains Application, UDP, IP (MC), and 5G-AN Protocol Layers. The NG-RAN contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and a 5G-AN Protocol Layers block. The MB-UPF contains a Relay block with IP (MC), GTP-U, UDP/IP, L2, and L1 layers, and another Relay block with IP (MC), L2, and L1 layers. The AF contains Application, UDP, IP (MC), L2, and L1 layers. Interfaces N3mb and N6mb are indicated between the entities.](57134800ac3a97b6212b27b93aa196ac_img.jpg) + +Figure 8.2-2: User Plane Protocol Stack for MBS session (plain IP multicast). This diagram shows the protocol stack across four entities: UE, NG-RAN, MB-UPF, and AF. The UE contains Application, UDP, IP (MC), and 5G-AN Protocol Layers. The NG-RAN contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and a 5G-AN Protocol Layers block. The MB-UPF contains a Relay block with IP (MC), GTP-U, UDP/IP, L2, and L1 layers, and another Relay block with IP (MC), L2, and L1 layers. The AF contains Application, UDP, IP (MC), L2, and L1 layers. Interfaces N3mb and N6mb are indicated between the entities. + +Figure 8.2-2: User Plane Protocol Stack for MBS session (plain IP multicast) + +- **5G-AN Protocol Layers:** This set of protocols/layers depends on the AN: + - in this Release, the 5G-AN is a 3GPP NR, these protocols/layers are defined in TS 38.401 [16]. The radio protocol between the UE and the 5G-AN node (gNodeB) is specified in TS 38.300 [9]. + +![Figure 8.2-3: User Plane Protocol Stack for MBS session in case of Individual delivery. This diagram shows the protocol stack across four entities: UE, NG-RAN, UPF (PDU Session Anchor), and MB-UPF. The UE contains Application, IP(multicast)/UDP, and 5G-AN Protocol Layers. The NG-RAN contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and a 5G-AN Protocol Layers block. The UPF contains a Replication/Relay block with GTP-U, UDP/IP, L2, and L1 layers, and another Replication/Relay block with GTP-U, UDP/IP, L2, and L1 layers. The MB-UPF contains GTP-U, UDP/IP, L2, and L1 layers. Interfaces N3, N19mb, and N6mb or Nmb9 are indicated between the entities.](1b2ce053624064d94a4143854da46702_img.jpg) + +Figure 8.2-3: User Plane Protocol Stack for MBS session in case of Individual delivery. This diagram shows the protocol stack across four entities: UE, NG-RAN, UPF (PDU Session Anchor), and MB-UPF. The UE contains Application, IP(multicast)/UDP, and 5G-AN Protocol Layers. The NG-RAN contains a Relay block with GTP-U, UDP/IP, L2, and L1 layers, and a 5G-AN Protocol Layers block. The UPF contains a Replication/Relay block with GTP-U, UDP/IP, L2, and L1 layers, and another Replication/Relay block with GTP-U, UDP/IP, L2, and L1 layers. The MB-UPF contains GTP-U, UDP/IP, L2, and L1 layers. Interfaces N3, N19mb, and N6mb or Nmb9 are indicated between the entities. + +Figure 8.2-3: User Plane Protocol Stack for MBS session in case of Individual delivery + +- **5G-AN Protocol Layers:** This set of protocols/layers depends on the AN: + - in this Release, the 5G-AN is a 3GPP NR, these protocols/layers are defined in TS 38.401 [16]. The radio protocol between the UE and the 5G-AN node (gNodeB) is specified in TS 38.300 [9]. + +NOTE: In Figure 8.2-3, the User Plane Protocol Stack between MB-UPF and AF/MBSTF is shown in Figure 8.2-1 and Figure 8.2-2. + +## 9 Network Function Services + +### 9.1 MB-SMF Services + +#### 9.1.1 General + +The following table illustrates the MB-SMF Services for MBS. + +**Table 9.1.1-1: NF services provided by MB-SMF** + +| Service Name | Service Operations | Operation Semantics | Example Consumer (s) | +|--------------------------|--------------------------|---------------------|----------------------| +| Nmbsmf_TMGI | Allocate | Request/Response | NEF, MBSF, AF | +| | Deallocate | Request/Response | NEF, MBSF, AF | +| | ContextStatusSubscribe | | SMF | +| Nmbsmf_MBSSession | ContextStatusUnsubscribe | Subscribe/Notify | SMF | +| | ContextStatusNotify | | SMF | +| | ContextUpdate | Request/Response | AMF, SMF | +| | StatusSubscribe | Subscribe/Notify | MBSF, NEF, AF | +| | StatusUnsubscribe | | MBSF, NEF, AF | +| | StatusNotify | | MBSF, NEF, AF | +| | Create | Request/Response | MBSF, NEF, AF | +| | Update | Request/Response | MBSF, NEF, AF | +| | Delete | Request/Response | MBSF, NEF, AF | + +#### 9.1.2 Nmbsmf\_TMGI service + +##### 9.1.2.1 General + +**Service description:** NF Service Consumer can use this service to request the allocation of TMGIs and release allocated TMGIs. + +##### 9.1.2.2 Nmbsmf\_TMGI\_Allocate service operation + +**Service operation name:** Nmbsmf\_TMGI\_Allocate + +**Description:** This service is used by the NF Service Consumer to request the allocation of TMGI(s) or request to refresh previously allocated TMGI(s). + +**Inputs, Required:** Number of TMGIs. + +**Inputs, Optional:** TMGI(s) for which the expiry time is to be extended). + +**Outputs, Required:** TMGI(s), Expiry Time of the TMGI(s), Result Indication. + +**Outputs, Optional:** NID. + +##### 9.1.2.3 Nmbsmf\_TMGI\_Deallocate service operation + +**Service operation name:** Nmbsmf\_TMGI\_Deallocate + +**Description:** NF Service Consumer can use this service to request the release of TMGI(s). + +**Inputs, Required:** TMGI(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** Success or not. + +**Outputs, Optional:** None. + +## 9.1.3 Nmbsmf\_MBSSession service + +### 9.1.3.1 General + +**Service description:** The following are the key functionalities of this NF service: + +- (between AMF or SMF and MB-SMF) For multicast, NF Service Consumer can use this service to request the reception of MBS data or to terminate the reception of MBS data of a Multicast MBS session, or for a location dependent Multicast MBS session, the part of the MBS multicast session within a service area; +- (between SMF and MB-SMF) For multicast, allow consumer NFs to query information (e.g. QoS information) about MBS Session. This service will be invoked by SMF for UE join event; +- (between SMF (only for multicast) or MBSF/NEF and MB-SMF) Allow consumer NFs to subscribe and unsubscribe for an Event ID and MBS Session, or for a location dependent MBS session, related to the part of the MBS session within a service area (only for MBSF/NEF); +- (between SMF (only for multicast) or MBSF/NEF and MB-SMF) Notifying events on the MBS Session, or for a location dependent MBS session, related to the part of the MBS session within a service area (only for MBSF/NEF), to the subscribed NFs; +- (between MBSF/NEF/AF and MB-SMF) Creation/Modification/Activation/Deactivation/Release of Multicast MBS session, or for a location dependent Multicast MBS session, the part of the Multicast MBS session within a service area; and +- (between MBSF/NEF and MB-SMF) Creation/Modification/Start/Stop/Release of Broadcast MBS sessions, or for a location dependent Broadcast MBS session, the part of the Broadcast MBS session within a service area. + +The following events related to MBS Session Context can be subscribed by SMF as consumer NF: + +- (between SMF and MB-SMF, only for multicast) QoS change: The event notification is sent when QoS within a Multicast MBS session changes, e.g. adding/removing QoS flow(s); +- (between SMF and MB-SMF only for multicast) multicast session state (Active, Inactive); +- (between SMF and MB-SMF only for multicast) Multicast MBS session service area change (for a location dependent Broadcast MBS session, the notification relates to the part of the Broadcast MBS session within a service area); +- (between SMF and MB-SMF only for multicast) Multicast MBS session release; +- (between SMF and MB-SMF only for multicast) multicast session security context update. + +The following events related to an MBS session, or for a location dependent MBS session, related to the part of the MBS session within a service area, can be subscribed by MBSF, NEF, or AF as consumer NF: + +- (between MBSF/NEF/AF and MB-SMF) MBS session release due to TMGI expiry; +- (between MBSF/NEF/AF and MB-SMF) Broadcast delivery status. + +NOTE: Whether event IDs are needed can be determined by stage 3. + +### 9.1.3.2 Nmbsmf\_MBSSession\_ContextUpdate service operation + +**Service operation name:** Nmbsmf\_MBSSession\_ContextUpdate + +**Description:** NF Service Consumer can use this service to request or terminate the reception of data of a multicast session, or for a location dependent MBS session, related to the part of the MBS session within a service area. + +**Inputs, Required:** MBS Session ID, if consumer is AMF: N2 container (Establishment or Release, MBS Session ID, Possible Area Session ID, Possible GTP Tunnel info for unicast transport, Possible tracking Area IDs), AMF ID, if consumer is SMF: SMF ID, MBS Session ID, Action(Establishment or Release). + +**Inputs, Optional:** if consumer is SMF: Area Session ID, Unicast GTP Tunnel info of the UPF. + +**Outputs, Required:** Success or not. + +**Outputs, Optional:** if consumer is AMF: N2 container (MBS Session ID, Possible Multicast DL tunnel info, multicast QoS flow information, session state (Active/Inactive), [MBS service areas]); if consumer is SMF: Multicast DL tunnel info. + +### 9.1.3.3 Nmbsmf\_MBSSession\_ContextStatusSubscribe service operation + +**Service operation name:** Nmbsmf\_MBSSession\_ContextStatusSubscribe + +**Description:** Service Consumer NF can use this service operation to request information (e.g. QoS information) about a multicast session and to subscribe to notification of events about the multicast session context. + +**Inputs, Required:** MBS Session ID, Notification Target Address, Events ID(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** None. + +**Outputs, Optional:** Event information (e.g. QoS information for multicast session, multicast MBS session state (Active, Inactive), multicast session service area for local multicast service), Start time of multicast MBS session, multicast DL tunnel info, if consumer is SMF: indication that the multicast MBS session allows any UE to join, multicast session security context. + +### 9.1.3.4 Nmbsmf\_MBSSession\_ContextStatusNotify service operation + +**Service operation name:** Nmbsmf\_MBSSession\_ContextStatusNotify + +**Description:** This service operation, which is applicable to multicast MBS session, is used by the MB-SMF to notify its consumers about events of an MBS Session, or for a location dependent MBS session, related to a service area change. + +**Inputs, Required:** MBS Session ID, Event ID. + +**Inputs, Optional:** Event information (e.g. QoS information of MBS Session, MBS service area, Area Session ID, updated multicast session security context). + +**Outputs, Required:** Operation execution result indication. + +**Outputs, Optional:** Cause. + +### 9.1.3.5 Nmbsmf\_MBSSession\_ContextStatusUnsubscribe service operation + +**Service operation name:** Nmbsmf\_MBSSession\_ContextStatusUnsubscribe + +**Description:** This service operation, which is applicable to multicast MBS session, is used by the consumer to unsubscribe to notifications about MBS context events. + +**Inputs, Required:** MBS Session ID. + +**Inputs, Optional:** None. + +**Outputs, Required:** Operation execution result indication. + +**Outputs, Optional:** None. + +### 9.1.3.6 Nmbsmf\_MBSSession\_Create service operation + +**Service operation name:** Nmbsmf\_MBSSession\_Create + +**Description:** Create a new multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. Optionally subscribe to notifications for this MBS session. + +**Input, Required:** MBS Session ID (SSM or TMGI) or TMGI allocation request, MBS Service Type (multicast or broadcast). + +**Input, Optional:** DNN, S-NSSAI, MBS service area, Area Session Policy ID, MBS Service Information (as defined in clause 6.14), Input Transport Address Request, MBS start time, MBS termination time. For a multicast session, indication that any UE may join, multicast session security context. For a broadcast session, MBS FSA ID(s). For subscription to notifications event ID(s), Notification Target Address, Request for location dependent MBS session, Associated Session ID for resource sharing across broadcast MBS Sessions during network sharing. + +**Output, Required:** Result Indication. + +**Output, Optional:** TMGI, NID, Expiry Time of the TMGI, Cause, MB-UPF tunnel info, MBS FSA ID(s), Area Session ID, Information of area reduction. + +### 9.1.3.7 Nmbsmf\_MBSSession\_Update service operation + +**Service operation name:** Nmbsmf\_MBSSession\_Update + +**Description:** Update the established multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area, e.g. QoS update. + +**Input, Required:** MBS Session ID. + +**Input, Optional:** MBS Service Information (as defined in clause 6.14), MBS service area, for a broadcast session, MBS FSA ID(s), Area Session ID, indication that the PCF has to be contacted. For multicast, session state (Active/Inactive), updated multicast session security context. + +**Output, Required:** Result Indication. + +**Output, Optional:** MBS FSA ID(s), Information of area reduction. + +### 9.1.3.8 Nmbsmf\_MBSSession\_Delete service operation + +**Service operation name:** Nmbsmf\_MBSSession\_Delete + +**Description:** Release the multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. The MBS session is deleted and the subscription (if any) to notifications about events related to the status of the MBS session is terminated. + +**Input, Required:** MBS Session ID. + +**Input, Optional:** Area Session ID. + +**Output, Required:** Result Indication. + +**Output, Optional:** Cause. + +### 9.1.3.9 Nmbsmf\_MBSSession\_StatusNotify service operation + +**Service operation name:** Nmbsmf\_MBSSession\_StatusNotify + +**Description:** This service operation is used by the MB-SMF to notify its consumers about the status change of the MBS session, or for a location dependent MBS session, of the part of the MBS session within a service area. + +**Input, Required:** MBS Session ID, Event ID. + +**Input, Optional:** Event information, Area Session ID. + +**Output, Required:** Result Indication. + +#### 9.1.3.10 Nmbsmf\_MBSSession\_StatusSubscribe service operation + +**Service operation name:** Nmbsmf\_MBSSession\_StatusSubscribe + +**Description:** This service operation is used by the NF service consumer (e.g. NEF, MBSF, AF) to subscribe notification about events related to the status of the MBS session, or for a location dependent MBS session, the part of the MBS session within a service area. + +**Input, Required:** MBS Session ID, event ID(s), Notification Target Address. + +**Input, Optional:** Area Session ID. + +**Output, Required:** When the subscription is accepted: Subscription Correlation ID. + +#### 9.1.3.11 Nmbsmf\_MBSSession\_StatusUnsubscribe service operation + +**Service operation name:** Nmbsmf\_MBSSession\_StatusUnsubscribe + +**Description:** This service operation, is used by the NF service consumer (e.g. NEF, MBSF, AF) to unsubscribe to notification about events related to the status of the MBS session, or for a location dependent MBS session, the part of the MBS session within a service area. + +**Input, Required:** Subscription Correlation ID. + +**Input, Optional:** Area Session ID. + +**Output, Required:** Result Indication. + +## 9.2 PCF Services + +### 9.2.1 General + +The following table illustrates the PCF Services for MBS. + +**Table 9.2.1-1: NF services provided by PCF for MBS** + +| Service Name | Service Operations | Operation Semantics | Example Consumer (s) | +|------------------------------------|--------------------|---------------------|----------------------| +| Npcf_MBSPolicyControl | Create | Request/Response | MB-SMF | +| | Update | Request/Response | MB-SMF | +| | Delete | Request/Response | MB-SMF | +| Npcf_MBSPolicyAuthorization | Create | Request/Response | AF, NEF, MBSF | +| | Update | Request/Response | AF, NEF, MBSF | +| | Delete | Request/Response | AF, NEF, MBSF | + +### 9.2.2 Npcf\_MBSPolicyControl service + +#### 9.2.2.1 General + +**Service description:** NF Service Consumer, e.g. MB-SMF, can create and manage a MBS Policy Association in the PCF through which the NF Service Consumer receives policy information for the MBS Session. + +As part of this service, the PCF may provide the NF Service Consumer, e.g. MB-SMF, with policy information for the MBS Session that may contain (the details are defined in clause 6.10): + +- Policy information applicable for an entire MBS Session. +- PCC rule information. +- Policy Control Request Trigger information. + +At MBS Session establishment the NF Service Consumer, e.g. MB-SMF, requests the creation of a corresponding MBS Policy Association with the PCF (Npcf\_MBSPolicyControl\_Create) and provides relevant parameters about the MBS Session to the PCF. + +- When the PCF has created the "MBS Policy Association", the PCF may provide policy information as defined above. + +When a Policy Control Request Trigger condition is met the NF Service Consumer, e.g. MB-SMF, requests the update (Npcf\_MBSPolicyControl\_Update) of the MBS Policy Association by providing information on the condition(s) that have been met. The PCF may provide updated policy information for the MBS session to the NF Service Consumer. + +The PCF may at any time provide updated policy information for the MBS session (Npcf\_MBSPolicyControl\_UpdateNotify). + +At MBS Session Release the NF Service Consumer, e.g. MB-SMF, requests the deletion of the corresponding MBS Policy Association. + +#### 9.2.2.2 Npcf\_MBSPolicyControl\_Create service operation + +**Service operation name:** Npcf\_MBSPolicyControl\_Create + +**Description:** The NF Service Consumer can request the creation of a MBS Policy Association and provide relevant parameters about the MBS Session to the PCF. + +**Inputs, Required:** MBS Session ID. + +**Inputs, Optional:** MBS Service Information (as defined in clause 6.14), Area Session Policy ID, DNN, S-NSSAI. + +**Outputs, Required:** Success or Failure. In the case of Success, MBS Policy Association ID and Policy information for the MBS Session (as defined in clause 6.10). + +**Outputs, Optional:** In the case of Failure, the Service Information that can be accepted by the PCF. In the case of Failure, indication that another PCF shall be contacted and an ID of that other PCF. + +#### 9.2.2.3 Void + +#### 9.2.2.4 Npcf\_MBSPolicyControl\_Delete service operation + +**Service operation name:** Npcf\_MBSPolicyControl\_Delete + +**Description:** The NF Service Consumer (i.e. MB-SMF) can request the deletion of the MBS Policy Association and of the associated resources. + +**Inputs, Required:** MBS Policy Association ID. + +**Inputs, Optional:** None. + +**Outputs, Required:** Success or Failure. + +**Outputs, Optional:** None. + +#### 9.2.2.5 Npcf\_MBSPolicyControl\_Update service operation + +**Service operation name:** Npcf\_MBSPolicyControl\_Update + +**Description:** The NF Service Consumer can request an update of the MBS Policy Association. + +**Inputs, Required:** MBS Policy Association ID. + +**Inputs, Optional:** MBS Service Information (as defined in clause 6.14), Information on the Policy Control Request Trigger condition that has been met. + +**Outputs, Required:** Success or Failure. + +**Outputs, Optional:** In the case of Failure, the Service Information that can be accepted by the PCF. In the case of Success, Policy information for the MBS Session (as defined in clause 6.10). + +## 9.2.3 Npcf\_MBSPolicyAuthorization Service + +### 9.2.3.1 General + +**Service description:** This service is to authorise an AF / NEF / MBSF request for an MBS service and to create policies as requested by the authorized AF for the MBS Service. This service also allows the NF consumer to subscribe/unsubscribe the notification of events. + +### 9.2.3.2 Npcf\_MBSPolicyAuthorization\_Create service operation + +**Service operation name:** Npcf\_MBSPolicyAuthorization\_Create + +**Description:** Authorize the request, and optionally determines and installs MBS Policy Control Data according to the information provided by the NF Consumer. + +**Inputs, Required:** MBS Session ID. + +**Inputs, Optional:** DNN if available, S-NSSAI if available, MBS Service Information (as defined in clause 6.14), Request for location dependent MBS session. + +**Outputs, Required:** Success (application session context) or Failure (reason for failure). + +**Outputs, Optional:** Area Session Policy ID (for location dependent session), in the case of Failure, the MBS Service Information that can be accepted by the PCF. + +### 9.2.3.3 Npcf\_MBSPolicyAuthorization\_Update service operation + +**Service operation name:** Npcf\_MBSPolicyAuthorization\_Update + +**Description:** Provides updated information to the PCF. + +**Inputs, Required:** Identification of the application session context. + +**Inputs, Optional:** MBS Service Information (as defined in clause 6.14). + +**Outputs, Required:** Success or Failure (reason for failure). + +**Outputs, Optional:** In the case of Failure, the MBS Service Information that can be accepted by the PCF. In the case of Success, indication that the PCF has to be contacted. + +Provides updated application level information and communicates with Npcf\_MBSPolicyControl service to determine and install the policy according to the information provided by the NF Consumer. Updates an application context in the PCF. + +### 9.2.3.4 Npcf\_MBSPolicyAuthorization\_Delete service operation + +**Service operation name:** Npcf\_MBSPolicyAuthorization\_Delete + +**Description:** Provides means for the NF Consumer to delete the context of application level session information. + +**Inputs, Required:** Identification of the application session context. + +**Inputs, Optional:** None. + +**Outputs, Required:** Success or Failure. + +**Outputs, Optional:** None. + +## 9.3 AMF Services + +### 9.3.1 General + +The Namf\_MT\_EnableGroupReachability service operation is defined in TS 23.502 [6]. + +The following table illustrates the new AMF Service for broadcast communication. + +**Table 9.3.1-1: NF services provided by AMF** + +| Service Name | Service Operations | Operation Semantics | Example Consumer (s) | +|------------------------------|---------------------|---------------------|----------------------| +| Namf_MBSBroadcast | ContextCreate | Request/Response | MB-SMF | +| | ContextUpdate | Request/Response | MB-SMF | +| | ContextRelease | Request/Response | MB-SMF | +| | ContextStatusNotify | Subscribe/Notify | MB-SMF | +| Namf_MBSCommunication | N2MessageTransfer | Request/Response | MB-SMF | + +### 9.3.2 Namf\_MBSBroadcast service + +#### 9.3.2.1 General + +**Service description:** This service is used by the consumer for broadcast communication. + +#### 9.3.2.2 Namf\_MBSBroadcast\_ContextCreate service operation + +**Service operation name:** Namf\_MBSBroadcast\_ContextCreate + +**Description:** This service operation is used to create the broadcast session context towards the AMF. + +**Inputs, Required:** MBS Session ID, Broadcast service area, N2 container (e.g. MBS Session ID, MBS QoS profile, Broadcast service area), Notification Endpoint. + +**Inputs, Optional:** Area Session ID, Optional parameters in the N2 container (MBS IP Multicast Tunnel Info, Area Session ID, MBS FSA ID(s), Associated Session ID for resource sharing across broadcast MBS Sessions during network sharing). + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** N2 container (MBS Session ID, Area Session ID, NG-RAN MBS Tunnel Info). + +#### 9.3.2.3 Namf\_MBSBroadcast\_ContextUpdate service operation + +**Service operation name:** Namf\_MBSBroadcast\_ContextUpdate + +**Description:** This service operation is used to update the broadcast session context towards the AMF. + +**Inputs, Required:** MBS Session ID. + +**Inputs, Optional:** Broadcast service area, N2 container (MBS Session ID, Possible MBS QoS profile, Possible Broadcast service area, Possible Area Session ID, Possible MBS IP Multicast Tunnel Info, MBS FSA ID(s)), Notification Endpoint. + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** N2 container (MBS Session ID, Area Session ID, NG-RAN MBS Tunnel Info). + +#### 9.3.2.4 Namf\_MBSCroadcast\_ContextRelease service operation + +**Service operation name:** Namf\_MBSCroadcast\_ContextRelease + +**Description:** This service operation is used to release the broadcast session context towards the AMF. + +**Inputs, Required:** MBS Session ID, N2 container (MBS Session ID). + +**Inputs, Optional:** None. + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** None. + +#### 9.3.2.5 Namf\_MBSCroadcast\_ContextStatusNotify service operation + +**Service operation name:** Namf\_MBSCroadcast\_ContextStatusNotify + +**Description:** This service operation is used to notify its consumers about the status change of a broadcast session context. + +**Inputs, Required:** MBS Session ID. + +**Inputs, Optional:** Event ID (e.g. change of NG-RAN MBS Tunnel Info), N2 SM information. + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** None. + +### 9.3.3 Namf\_MBSCommunication Service + +#### 9.3.3.1 General + +**Service description:** This service enables MBS multicast related N2 message transfer towards the NG-RAN via the AMF, during multicast session activation/deactivation/update/release. + +#### 9.3.3.2 Namf\_MBSCommunication\_N2MessageTransfer service operation + +**Service operation name:** Namf\_MBSCommunication\_N2MessageTransfer + +**Description:** This service operation is used by the NF Consumer to request the AMF to transfer the MBS related N2 message to the NG-RAN nodes serving the MBS multicast session. + +**Input, Required:** MBS Session ID, N2 SM information. + +**Input, Optional:** MBS Area Session ID. + +**Output, Required:** Result Indication. + +**Output, Optional:** Cause. + +## 9.4 NEF Services + +### 9.4.1 General + +The following table illustrates the NEF Services for MBS. + +Table 9.4.1-1: NF services provided by NEF + +| Service Name | Service Operations | Operation Semantics | Example Consumer (s) | +|---------------------------------|--------------------|---------------------|----------------------| +| Nnef_MBSTMGI | Allocate | Request/Response | AF | +| | Deallocate | Request/Response | AF | +| | ExpiryNotify | Subscribe/Notify | AF | +| Nnef_MBSSession | Create | Request/Response | AF | +| | Update | Request/Response | AF | +| | Delete | Request/Response | AF | +| | StatusNotify | Subscribe/Notify | AF | +| | StatusSubscribe | | AF | +| | StatusUnsubscribe | | AF | +| Nnef_MBSGroupMsgDelivery | Create | Request/Response | AF | +| | Update | Request/Response | AF | +| | Delete | Request/Response | AF | +| | StatusNotify | Subscribe/Notify | AF | + +## 9.4.2 Nnef\_MBSTMGI service + +### 9.4.2.1 General + +**Service description:** NF Service Consumer can use this service to request the allocation of TMGIs and deallocate TMGIs previously allocated. + +### 9.4.2.2 Nnef\_MBSTMGI\_Allocate service operation + +**Service operation name:** Nnef\_MBSTMGI\_Allocate + +**Description:** This service is used by the NF Service Consumer to request allocation of TMGI(s), or to refresh the expiry time for already allocated TMGI(s). + +**Inputs, Required:** Number of TMGIs (may be zero if only a refresh of expiry time is requested). + +**Inputs, Optional:** TMGI(s) for which the expiry time is to be extended, MBS service area. + +**Outputs, Required:** TMGIs, Expiry Time, Result Indication. + +**Outputs, Optional:** NID. + +### 9.4.2.3 Nnef\_MBSTMGI\_Deallocate service operation + +**Service operation name:** Nnef\_MBSTMGI\_Deallocate + +**Description:** This service is used by the NF Service Consumer to request deallocation the TMGI(s). + +**Inputs, Required:** TMGI(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** Success or not. + +**Outputs, Optional:** None. + +### 9.4.2.4 Nnef\_MBSTMGI\_ExpiryNotify service operation + +**Service operation name:** Nnef\_MBSTMGI\_ExpiryNotify + +**Description:** This service is used by the NEF to notify the NF service consumer of the timer expiry for TMGI(s). + +**Inputs, Required:** TMGI(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +## 9.4.3 Nnef\_MBSSession Service + +### 9.4.3.1 General + +**Service description:** This service operates on the multicast and broadcast MBS sessions. The following are the key functionalities of this NF service: + +- Create/Update Delete for both multicast and broadcast MBS session, or for a location dependent MBS session, the part of the MBS session within a service area; +- Provide a Notification about subscribed events. The following events are supported: + - MBS session release due to TMGI expiry. + - Broadcast delivery status. + +### 9.4.3.2 Nnef\_MBSSession\_Create service operation + +**Service operation name:** Nnef\_MBSSession\_Create + +**Description:** Create a new multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. Optionally implicitly subscribe to notifications for this MBS session. + +**Input, Required:** MBS Session ID (SSM or TMGI) or TMGI allocation request, MBS Service Type (broadcast or multicast). + +**Input, Optional:** MBS service area (mandatory for broadcast. Can be Cell ID list and/or TAI list, or geographical area information, or civic address information), MBS start time, MBS stop time, MBS Service Information (as defined in clause 6.14), Input Transport Address Request, session state (Active/Inactive), for subscription to notifications notification target address. For a multicast session, indication that any UE may join the multicast session. Request for location dependent MBS session. For a broadcast session, MBS FSA ID(s), Associated Session ID for resource sharing across broadcast MBS Sessions during network sharing. + +**Output, Required:** Result Indication. + +**Output, Optional:** TMGI, NID, Cause, MB-UPF tunnel info, MBS FSA ID(s), Area Session ID, Information of area reduction. + +### 9.4.3.3 Nnef\_MBSSession\_Update service operation + +**Service operation name:** Nnef\_MBSSession\_Update + +**Description:** This service is used by the NF service consumer to update the established multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area, e.g. QoS update. For multicast MBS Session, this service is also used to activate or deactivate the MBS Session. + +**Input, Required:** MBS Session ID. + +**Input, Optional:** MBS Service Information (as defined in clause 6.14), MBS service area, session state (Active/Inactive), Area Session ID. For a broadcast session, MBS FSA ID(s). + +**Output, Required:** Result Indication. + +**Output, Optional:** MBS FSA ID(s), Information of area reduction. + +#### 9.4.3.4 Nnef\_MBSSession\_Delete service operation + +**Service operation name:** Nnef\_MBSSession\_Delete + +**Description:** This service is used to delete the multicast or broadcast MBS session, or for a location dependent MBS session, the part of the MBS session within a service area. + +**Input, Required:** MBS Session ID. + +**Input, Optional:** Area Session ID. + +**Output, Required:** Result Indication. + +**Output, Optional:** Cause. + +#### 9.4.3.5 Nnef\_MBSSession\_StatusNotify service operation + +**Service operation name:** Nnef\_MBSSession\_StatusNotify + +**Description:** This service is used by the MB-SMF to notify the NF service consumers of the subscribed events related to an MBS session, or for a location dependent MBS session, related to the part of the MBS session within a service area. + +**Inputs, Required:** Status Information, MBS Session ID. + +**Inputs, Optional:** Area Session ID. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +#### 9.4.3.6 Nnef\_MBSSession\_StatusSubscribe service operation + +**Service operation name:** Nnef\_MBSSession\_StatusSubscribe + +**Description:** This service is used by the NF service consumers to subscribe to the MBS Session status information of an MBS session, or for a location dependent MBS session, of the part of the MBS session within a service area. + +**Inputs, Required:** Status Information, MBS Session ID. + +**Inputs, Optional:** Area Session ID. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +#### 9.4.3.7 Nnef\_MBSSession\_StatusUnsubscribe service operation + +**Service operation name:** Nnef\_MBSSession\_StatusUnsubscribe + +**Description:** This service is used by the NF service consumers to unsubscribe to the MBS Session status information of an MBS session or for a location dependent MBS session, of the part of the MBS session within a service area. + +**Inputs, Required:** Status Information, MBS Session ID. + +**Inputs, Optional:** Area Session ID. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +## 9.4.4 Nnef\_MBSGroupMsg Service + +### 9.4.4.1 General + +**Service description:** NF Service Consumer can use this service to request group message delivery or to modify or to cancel previously submitted group message delivery. + +### 9.4.4.2 Nnef\_MBSGroupMsgDelivery\_Create service operation + +**Service operation name:** Nnef\_MBSGroupMsgDelivery\_Create + +**Description:** This service is used by the NF Service Consumer to request group message delivery. + +**Inputs, Required:** Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time, External Group Identifier, Notification Endpoint. + +**Inputs, Optional:** None. + +**Outputs, Required:** Group Message Correlation ID, Delivery Status, service announcement information. + +**Outputs, Optional:** Cause, service area without MBS capability. + +### 9.4.4.3 Nnef\_MBSGroupMsgDelivery\_Update service operation + +**Service operation name:** Nnef\_MBSGroupMsgDelivery\_Update + +**Description:** This service is used by the NF Service Consumer to replace group message delivery. + +**Inputs, Required:** Group Message Correlation ID. + +**Inputs, Optional:** Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time, Notification Endpoint. + +**Outputs, Required:** Acceptance Status + +**Outputs, Optional:** Cause, service area without MBS capability. + +### 9.4.4.3a Nnef\_MBSGroupMsgDelivery\_Delete service operation + +**Service operation name:** Nnef\_MBSGroupMsgDelivery\_Delete + +**Description:** This service is used by the NF Service Consumer to recall (or cancel) group message delivery. + +**Inputs, Required:** Group Message Correlation ID. + +**Inputs, Optional:** None. + +**Outputs, Required:** Acceptance Status. + +**Outputs, Optional:** Cause. + +### 9.4.4.4 Nnef\_MBSGroupMsgDelivery\_StatusNotify service operation + +**Service operation name:** Nnef\_MBSGroupMsgDelivery\_StatusNotify + +**Description:** This service is used by the NEF to notify the NF service consumers of the status of a group message delivery. + +NOTE: This notification corresponds to an implicit subscription. + +**Inputs, Required:** Status Information, Notification Endpoint. + +**Inputs, Optional:** None. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +## 9.5 MBSF Services + +MBSF services are defined in TS 26.502 [18]. + +## Annex A (normative): Configuration options at Service and/or Application for MBS + +Figure A-1 provides the reference architecture with all configuration variants for Application Function interaction with 5G Core Network, usage of NEF or MBSF in the control plane, and usage of N6, MB2-U or xMB-U in user plane. + +![Figure A-1: Configuration options at Service and/or Application. The diagram shows three configurations for MBS interaction with the 5G Core Network. Configuration 1 (No MBSF) shows the AF/AS connected to the NEF via N33, and the NEF connected to the Transport via N30, N29mb, and N6mb. Configuration 2 (With MBSF, N33 towards AF) shows the AF/AS connected to the NEF via N33, and the NEF connected to the MBSF via Nmb5. The MBSF is connected to the MBSTF via Nmb2, and the MBSTF is connected to the Transport via Nmb8/xMB-U/MB2-U. Configuration 3 (With MBSF, MB2-C/xMB-C/Nmb10 towards AF) shows the AF/AS connected to the MBSF via Nmb10/xMB-C/MB2-C, and the MBSF connected to the MBSTF via Nmb2, and the MBSTF connected to the Transport via Nmb8/xMB-U/MB2-U. In all configurations, the NEF and MBSF are collocated within the AF/AS domain.](3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg) + +Figure A-1: Configuration options at Service and/or Application. The diagram shows three configurations for MBS interaction with the 5G Core Network. Configuration 1 (No MBSF) shows the AF/AS connected to the NEF via N33, and the NEF connected to the Transport via N30, N29mb, and N6mb. Configuration 2 (With MBSF, N33 towards AF) shows the AF/AS connected to the NEF via N33, and the NEF connected to the MBSF via Nmb5. The MBSF is connected to the MBSTF via Nmb2, and the MBSTF is connected to the Transport via Nmb8/xMB-U/MB2-U. Configuration 3 (With MBSF, MB2-C/xMB-C/Nmb10 towards AF) shows the AF/AS connected to the MBSF via Nmb10/xMB-C/MB2-C, and the MBSF connected to the MBSTF via Nmb2, and the MBSTF connected to the Transport via Nmb8/xMB-U/MB2-U. In all configurations, the NEF and MBSF are collocated within the AF/AS domain. + +**Figure A-1: Configuration options at Service and/or Application** + +The following characteristics describe each of the Configuration options: + +- Configuration Option 1: No MBSF: + - This configuration is used for Transport Only Mode (i.e. MBS provides only transport of MBS data in a transparent manner without modifying the data), when the Multicast service or Broadcast service does not require service layer interworking with LTE MBMS. + - The control plane entry point for the Application Function outside the trusted domain towards 5GC to request establishment of an MBS session is the NEF via N33. + - An application function within the trusted domain can directly use the N30, N5 and N29mb service based interfaces. In this case some NEF functionality related to PCF and MB-SMF interaction is incorporated in AF. + +NOTE 1: Application function within the trusted domain selects MB-SMF based on e.g. its local configuration, or query NRF based on location, etc. + +- The user plane entry point for the Application Function towards 5GC is the MB-UPF via N6mb. +- Configuration Option 2: MBSF, N33 towards AF: + - This configuration may be used for Service Mode (i.e. MBS provides service layer capability, allows to modify the data), or when service layer interworking with LTE MBMS is required, or when the functionalities of MBS security is used (see clause 6.13). + - When interworking with LTE MBMS for Transport Only Mode services, N33/Nmb5 and Nmb8 provide the same functionalities as N33/N13mb and N6mb respectively. + - The control plane entry point from the Application Function to request establishment of an MBS session is the NEF via N33. + - The user plane entry point for the Application Function towards 5GC is the MBSTF via MB2-U, xMB-U or Nmb8. + - The NEF and MBSF may be collocated. + - If the MBSF is not collocated with the NEF, the reference point between the NEF and MBSF is Nmb5. + - An application function within the trusted domain may be collocated with MBSF. + +- Configuration Option 3: MBSF, MB2-C/xMB-C/Nmb10 towards AF: + - This configuration may be used for Service Mode (xMB-C or Nmb10), or when interworking with LTE MBMS is required (MB2-C, xMB-C or Nmb10), or when the functionalities of MBS security is used (see clause 6.13). + - When interworking with LTE MBMS for Transport Only Mode services, Nmb10 and Nmb8 provide the same functionalities as Nmb13 and N6mb respectively. + - The control plane entry point from the Application Function to request establishment of an MBS session is the MBSF via MB2-C, xMB-C or Nmb10. + - The user plane entry point for the Application Function is the MBSTF via MB2-U, xMB-U or Nmb8. + +For service mode, MBSF shall be used, i.e. either Configuration 2 or Configuration 3 shall be used. In this case, the MBSF instructs the MBSTF to modify the MBS data (e.g. including the FEC or MBS data transcoding). + +For Configuration Option 2 and Option 3, when interworking with LTE MBMS is used, LTE MBMS and MBS use the same mode (i.e. both use Transport Only Mode or Service Mode). + +For Transport Only mode: + +- If interworking with LTE MBMS at 5GC is required for the service, MBSF and MBSTF shall be used, i.e. either Configuration 2 or Configuration 3 shall be used. +- If interworking with LTE MBMS is not required for the service, MBSF and MBSTF are optional. + +NOTE 2: Interworking providing by AF is out of scope of this specification. + +MBSTF shall be used when MBSF is used. + +Any particular deployment may support any combination of these configurations. + +--- + +## Annex B (informative): Service levels for multicast communication service + +The following service levels for the multicast communication service are defined: + +NOTE 1: Transport Only mode and Full-Service mode of operation as defined in TS 23.246 [8] differ from the service levels defined here. + +- **Basic service level.** The following requirements are defined: + - Media transported transparently through the 5GS. + - Interactions between UE and network for receiving the multicast communication service. + - Packet distribution from the 5GS ingress to NG-RAN node(s). + - Data delivery from NG-RAN node(s) to the UE. +- **Enhanced service level**, with additional requirements on top of basic service level. Different requirements out of the set below may be necessary to address each use case: + - Local MBS service. + - User authentication and authorization for Multicast MBS session. + +NOTE 2: User authentication and authorization is an optional feature in 5GS. + +- Explicit configuration of Multicast MBS session by AF, including group member information. +- Enhanced QoS support. E.g. to differentiate MBS data flow with different QoS over 5GS. + +## Annex C (normative): Interworking at reference points MB2 and xMB + +To allow the MBS System to interwork with a GCS AS supporting the MB2 interfaces defined in TS 23.468 [10]: + +- In addition to supporting the Nmbsf service-based API at Nmb10 (as defined in clause 5.1) the MBSF shall support interfaces MB2 C. +- In addition to supporting content ingest interfaces defined in TS 26.502 [18] at Nmb8 (as defined in clause 5.1) the MBSTF shall support interfaces MB2 U. + +To allow the MBS System to interwork with a Content Provider supporting the xMB interfaces defined in TS 26.348 [11]: + +- In addition to supporting the Nmbsf service-based API at Nmb10 (as defined in clause 5.1) the MBSF shall support interface xMB C. +- In addition to supporting content ingest interfaces defined in TS 26.502 [18] at Nmb8 (as defined in clause 5.1) the MBSTF shall support interface xMB U. + +![Diagram illustrating the interworking of the MBS System with AF/AS, GCS AS, and Content Provider at various reference points.](a5481fd31c02b525617e70f2de357039_img.jpg) + +The diagram shows the interworking of the MBS System (containing MBSF and MBSTF) with three external entities: AF/AS, GCS AS, and Content Provider. The MBS System is represented by a grey box on the left. The AF/AS is connected to the MBS System via Nmb8 (top) and Nmb10 (middle). The GCS AS is connected to the MBS System via MB2-C (middle) and MB2-U (bottom). The Content Provider is connected to the MBS System via xMB-C (bottom) and xMB-U (bottom). The MBSF is connected to the AF/AS via Nmb10 and to the GCS AS via MB2-C. The MBSTF is connected to the AF/AS via Nmb8 and to the GCS AS via MB2-U. The MBSTF is also connected to the Content Provider via xMB-U. + +Diagram illustrating the interworking of the MBS System with AF/AS, GCS AS, and Content Provider at various reference points. + +**Figure C-1: Interworking with GCS AS supporting MB2 interfaces and with Content Provider supporting xMB interfaces** + +--- + +## Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|----|-----------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Ca | Subject/Comment | New version | +| 2021-03 | SA2#143E | S2-2101423 | - | - | - | TS skeleton approved at S2#143E | 0.0.0 | +| 2021-06 | SA#92E | SP-210368 | - | - | - | MCC editorial update for presentation to TSG SA#92E for information | 1.0.0 | +| 2021-09 | SA#93E | SP-210941 | - | - | - | MCC editorial update for presentation to TSG SA#93E for approval | 2.0.0 | +| 2021-09 | SA#93E | - | - | - | - | MCC editorial update for publication after TSG SA#93E approval | 17.0.0 | +| 2021-12 | SA#94E | SP-211285 | 0001 | - | F | Clarification on interworking with EPS | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0002 | 3 | F | MBS Session Management vs Configuration | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0006 | 1 | F | Multicast MBS Session: resolving ENs and cleanup | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0008 | 2 | F | Interworking with MBMS over E-UTRAN for broadcast service | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0010 | 2 | F | Local MBS service and Location dependent MBS service | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0012 | 1 | F | Multicast session join and session establishment | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0014 | 3 | F | Multicast session leave and session release | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0015 | 3 | F | Clarifications on functional entities | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0019 | 2 | F | NRF service operation for broadcast service | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0021 | 4 | F | Clarification of the local MBS service | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0022 | 4 | F | Leftover issue for MBS session activation and deactivation | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0023 | 1 | F | Lossless handover for MBS session | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0025 | 1 | F | When UE joining UE authorization for the multicast MBS session | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0026 | 3 | F | Miscellaneous corrections | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0027 | 1 | F | Clarification on User Plane Management | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0029 | 4 | F | Updates on cases that SMF rejects UE join request | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0031 | 1 | D | Editorial modification on terms, abbreviations | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0032 | 1 | F | Modification on session join and shared tunnel establishment related procedures | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0033 | 1 | F | Modification on session leave and shared tunnel release related procedures | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0035 | 2 | F | Modification on handover procedures | 17.1.0 | +| 2021-12 | SA#94E | SP-211285 | 0038 | 3 | F | Replacement reference architecture figures | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0041 | 1 | F | Update to the Multicast session join and session establishment, and removing procedure. | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0043 | 1 | F | Clarification on the MBS service activation/deactivation/update and related service operation | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0044 | 1 | F | modification on the MBS Broadcast session management | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0045 | 1 | F | Clarification on the Qos handling and Policy control in the clause 6 | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0050 | 2 | F | PCC related MBS corrections | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0051 | 1 | F | Corrections to MBS Broadcast Session Establishment | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0054 | - | F | Clarification on local multicast | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0055 | 1 | F | Minimize multicast service interruption caused by unintended PDU session release | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0057 | 1 | F | Multicast MBS service for SNPN | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0060 | 1 | F | Updates to NF services for MBS | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0062 | 1 | F | Modification on activation procedure | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0064 | 1 | F | Clarification on NF services | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0066 | 1 | F | Clarification on Annex A for transport mode | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0067 | 1 | F | Fixing the EN and Nmbsmf_MBSSession service operation parameters. | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0068 | 1 | F | clarification on PDR and FAR in A-UPF for MBS data traffic in individual delivery | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0073 | 1 | F | Clarification on the input of PCF/NEF/MB-SMF service operation | 17.1.0 | +| 2021-12 | SA#94E | SP-211286 | 0074 | 1 | F | Broadcast Frequency selection Identifier | 17.1.0 | +| 2022-03 | SA#95E | SP-220052 | 0075 | 1 | F | Clarification on MBS Session Update procedures | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0077 | 1 | D | Adding a heading of clause 5 | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0078 | 1 | F | Corrections for Location dependent MBS session | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0079 | - | F | Removing UE from Multicast MBS Session | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0081 | 1 | F | Resolving ENs, cleanup and corrections | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0083 | 1 | F | Corrections to MBS procedures for broadcast Session | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0085 | 1 | F | Paging strategy handling for multicast MBS session | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0086 | 1 | F | Restoration of multicast MBS session following AN release | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0089 | 1 | F | Miscellaneous corrections on TS 23.247 | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0092 | 1 | F | MBS Frequency Selection Area Identifier | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0093 | 1 | F | Indication whether MBS session is active | 17.2.0 | +| 2022-03 | SA#95E | SP-220052 | 0095 | 1 | F | Resolving the PCC related EN and issue | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|---------------| +| 2022-03 | SA#95E | SP-220052 | 0096 | 1 | F | Clarification on the MBS session Create and update procedure. | 17.2.0 | +| 2022-06 | SA#96 | SP-220395 | 0090 | 5 | F | Clarification of MBS data forwarding | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0101 | 1 | F | Correction on the mobility procedures for MBS | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0102 | - | F | Broadcast MBS Session Release Require Procedure | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0103 | 1 | F | MBS Service Area for MB-SMF selection in TMGI Allocation | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0104 | 1 | F | Alignment with RAN3 and other corrections | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0105 | 1 | F | Correction to MBS Session Context and MBS Session Activation procedure | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0106 | 1 | F | Resolve the residual ENs and Clean-up in TS 23.247 | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0107 | 1 | F | Mega CR to clean up | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0110 | - | F | Clarification on MBS security function | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0111 | 1 | F | Usage of NAS message for UE joining procedure | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0112 | - | F | Clarification on MBS session activation procedure | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0113 | - | F | Clarification on Activation procedure | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0115 | 1 | F | Clarification on local dependent MBS session | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0116 | 1 | F | Miscellaneous corrections | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0117 | - | F | Clarifications on traffic usage reporting and charging | 17.3.0 | +| 2022-06 | SA#96 | SP-220395 | 0119 | 1 | F | Tunnel between MBSTF and MB-UPF | 17.3.0 | +| 2022-09 | SA#97E | SP-220775 | 0109 | 4 | F | Update of PCC procedure for 5MBS | 17.4.0 | +| 2022-09 | SA#97E | SP-220775 | 0122 | - | F | MBS Session Status and broadcast MBS Session | 17.4.0 | +| 2022-09 | SA#97E | SP-220775 | 0124 | - | F | Clarification on local multicast | 17.4.0 | +| 2022-09 | SA#97E | SP-220775 | 0126 | 1 | F | Correction to MB-SMF update in NRF | 17.4.0 | +| 2022-09 | SA#97E | SP-220775 | 0127 | 1 | F | Correction and editorial improvement | 17.4.0 | +| 2022-09 | SA#97E | SP-220775 | 0130 | 1 | F | Clarification on the mobility in RRC inactive | 17.4.0 | +| 2022-09 | SA#97E | SP-220775 | 0132 | 1 | F | Removing the EN on the HO | 17.4.0 | +| 2022-12 | SA#98E | SP-221068 | 0129 | 2 | F | Clarification on the traffic handling in MBSTF for interworking | 17.5.0 | +| 2022-12 | SA#98E | SP-221068 | 0134 | 1 | F | Handling of tunnel between UPF and MB-UPF for Multicast MBS session Deactivation and Reactivation | 17.5.0 | +| 2022-12 | SA#98E | SP-221068 | 0135 | - | F | Missing NID in output parameters to AF for SNPN | 17.5.0 | +| 2022-12 | SA#98E | SP-221068 | 0137 | 1 | F | Clean-up of PCC procedures for 5MBS | 17.5.0 | +| 2022-12 | SA#98E | SP-221068 | 0139 | 5 | F | CR on MTK or MSK processing | 17.5.0 | +| 2022-12 | SA#98E | SP-221068 | 0141 | 1 | F | Clarification on the shared delivery tunnel management for common gNB UP case | 17.5.0 | +| 2022-12 | SA#98E | SP-221095 | 0143 | 1 | B | Group Message Delivery | 18.0.0 | +| 2023-03 | SA#99 | SP-230051 | 0146 | 3 | B | Update the scope of TS 23.247 | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0149 | 8 | B | Support of MBS multicast reception by UEs in RRC_INACTIVE state | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0150 | 1 | B | Coexistence with existing power saving mechanisms for capability-limited devices | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0152 | 2 | A | AMF knowing MBS support status of NG-RAN node (s) for Multicast Activation | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0154 | 2 | A | Correction to description of Fig. 7.1.1.3-1 | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0156 | 1 | A | Correction to location dependent service for broadcast | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0158 | 1 | A | Correction to Broadcast MBS Session handling | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0159 | 7 | B | Support RRC_INACTIVE UE receiving multicast MBS data | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0160 | 6 | B | Introducing functionality of resource efficiency in MOCN Network Sharing | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0161 | - | C | Resolve ENs on Group Message Delivery and corrections | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0162 | 1 | B | Support MBS for UEs using power saving functions | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0163 | 1 | B | On the Update of Group Message Delivery | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0164 | 6 | B | On Clarifying the Scenario Considering the Power Saving Mechanism | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0165 | 3 | B | On resource efficiency for MBS reception in RAN sharing scenario | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0166 | 1 | F | Align the MB-SMF discovery enhancement in clause 7.1.2 | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0168 | 6 | B | Support of RRC Inactive state reception for MBS session | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0170 | 3 | A | Clarification shared NG-U Termination among gNBs for Broadcast MBS session | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0171 | 5 | B | KI#1, adding RRC inactive network functionality of NF description | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0176 | 9 | B | KI#2, adding MOCN network sharing for the same content | 18.1.0 | +| 2023-03 | SA#99 | SP-230051 | 0179 | 8 | B | Mobility procedures for UEs receiving multicast MBS session data in RRC Inactive state | 18.1.0 | +| 2023-03 | SA#99 | SP-230037 | 0187 | 2 | A | Update on the security in accordance with SA3 LS | 18.1.0 | +| 2023-06 | SA#100 | SP-230453 | 0205 | 1 | A | Alignment with RAN on Xn/N2 based handover for inactive MBS session | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0207 | 1 | F | KI#1 Correction of mobility procedures for delivery of multicast MBS session data to RRC_INACTIVE UE | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0210 | 1 | C | KI#2 Resolve EN in broadcast procedures for resource sharing in network sharing | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0213 | 1 | F | Update functional entity clauses for group message delivery and power saving functions | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0214 | 1 | F | Update the abbreviation for Release 18 | 18.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| 2023-06 | SA#100 | SP-230454 | 0220 | 1 | B | Update group message delivery procedure | 18.2.0 | +| 2023-06 | SA#100 | SP-230453 | 0224 | 1 | A | Connection resume with local multicast session | 18.2.0 | +| 2023-06 | SA#100 | SP-230453 | 0225 | 1 | A | Connection resume with location dependent multicast session | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0226 | 1 | B | Mobility Registration Update and Service Request procedures for local multicast service | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0227 | 1 | B | Mobility Registration Update and Service Request procedures for location dependent multicast service | 18.2.0 | +| 2023-06 | SA#100 | SP-230453 | 0230 | 1 | A | Clarification on the RRC resume failure for inactive MBS session | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0231 | 1 | B | Resolving the EN on the MOCN enhancement for the location dependent MBS session | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0232 | 1 | F | Resolving the EN on TMGI index and TMGI update for the configuration mechanism in the MOCN enhancement | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0237 | 1 | D | Clarification of applications for Group Message Delivery | 18.2.0 | +| 2023-06 | SA#100 | SP-230453 | 0239 | 1 | A | Handover Procedure correction | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0240 | 1 | F | Open issue related to mobility procedures of RRC Inactivate state UE | 18.2.0 | +| 2023-06 | SA#100 | SP-230453 | 0246 | 1 | A | Corrections for unicast tunnel establishment for MBS broadcast | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0252 | 2 | F | Enabling simultaneous join for high number of UEs that support multicast RRC inactive reception | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0253 | 1 | F | Mobility procedures for RRC inactive UEs | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0258 | 1 | B | Update of MBS service announcement for capability-limited devices | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0259 | 1 | B | MBS session activation for UEs using power saving functions | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0260 | 1 | F | Resolving open issues for Multicast MBS procedures for UEs using power saving functions | 18.2.0 | +| 2023-06 | SA#100 | SP-230454 | 0269 | 2 | F | Clarification on the NEF role and interface for the group message data delivery | 18.2.0 | +| 2023-09 | SA#101 | SP-230834 | 0262 | 5 | A | Corrections related to indicating failure of establishing MBS broadcast transmission resources | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0279 | 1 | F | Corrections for support of MBS data reception for UEs using power saving functions | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0280 | 3 | F | Group Paging for Multicast MBS session data reception in RRC_INACTIVE state | 18.3.0 | +| 2023-09 | SA#101 | SP-230834 | 0284 | 1 | A | Multicast over N6mb not applicable for location dependent MBS session | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0285 | 1 | F | Alignment with stage 3 on Parameter Provisioning of MBS Assistance Information | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0286 | 2 | F | Converting the requirement of AF handling service announcement to a NOTE | 18.3.0 | +| 2023-09 | SA#101 | SP-230834 | 0288 | 2 | A | On the step number correction of 5MBS | 18.3.0 | +| 2023-09 | SA#101 | SP-230834 | 0292 | - | A | Correcting the figure and term | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0297 | 1 | F | Resolving the EN on the RRC inactive assistant information | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0300 | 2 | F | RRC INACTIVE UE Mobility within the same RNA | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0301 | 1 | F | Clarification on the Resource sharing across broadcast MBS Sessions in MOCN | 18.3.0 | +| 2023-09 | SA#101 | SP-230843 | 0303 | 1 | F | Editorial corrections | 18.3.0 | +| 2023-12 | SA#102 | SP-231240 | 0201 | 4 | A | Correction to PCC procedures for location dependent MBS service | 18.4.0 | +| 2023-12 | SA#102 | SP-231240 | 0276 | 4 | A | Handling of unsupported MBS service area | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0278 | 3 | F | Alignment with RAN on transfer of assistance information during handover. | 18.4.0 | +| 2023-12 | SA#102 | SP-231248 | 0307 | - | F | Update UE pre-configuration | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0316 | 1 | F | Correction on the references | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0317 | 1 | F | Correction to the GroupMessage service operation | 18.4.0 | +| 2023-12 | SA#102 | SP-231240 | 0319 | 1 | A | MBS Session deactivation and Mission Critical services | 18.4.0 | +| 2023-12 | SA#102 | SP-231240 | 0321 | 2 | A | Correction to notification target address for context status notify of broadcast MBS | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0322 | 3 | F | Pending MBS Session Release request at 5GS to EPS mobility | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0323 | 3 | F | Resource sharing across broadcast MBS Sessions during network sharing | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0324 | - | F | Context Status Notification during transport change for resource sharing | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0326 | 2 | F | Correction on shared N3mb tunnels towards NG-RAN in network sharing scenarios | 18.4.0 | +| 2023-12 | SA#102 | SP-231240 | 0330 | 1 | A | Flow description within MBS Service Information if MBS data are transported in IP tunnel toward MB-UPF | 18.4.0 | +| 2023-12 | SA#102 | SP-231240 | 0332 | 1 | A | Location Dependent MBS broadcast session with multiple MB-SMFs | 18.4.0 | +| 2023-12 | SA#102 | SP-231251 | 0336 | - | F | Mobility of UE in RRC_INACTIVE state receiving MBS data within RNA | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------|--------| +| 2023-12 | SA#102 | SP-231251 | 0340 | 3 | F | Clarification on MBS session data reception in RRC_INACTIVE state | 18.4.0 | +| 2023-12 | SA#102 | SP-231248 | 0343 | 1 | F | Correction for Multicast session leave procedure | 18.4.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23282/raw.md b/raw/rel-18/23_series/23282/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..91c883d108033d74ec20645ba113284f1f4322da --- /dev/null +++ b/raw/rel-18/23_series/23282/raw.md @@ -0,0 +1,10507 @@ +# 3GPP TS 23.282 V18.6.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional architecture and information flows to support Mission Critical Data (MCData); 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 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 + +| | | +|--------------------------------------------------------------------------------------------------|----| +| TOC \o "1-9" Foreword..... | 15 | +| 1 Scope..... | 16 | +| 2 References..... | 16 | +| 3 Definitions, symbols and abbreviations..... | 17 | +| 3.1 Definitions..... | 17 | +| 3.2 Abbreviations..... | 19 | +| 4 Introduction..... | 19 | +| 5 Architectural requirements..... | 20 | +| 5.1 Transmission control..... | 20 | +| 5.2 Reception control..... | 20 | +| 5.3 Short Data Service capability..... | 21 | +| 5.4 File distribution capability..... | 21 | +| 5.5 Data streaming capability..... | 22 | +| 5.6 MCData group affiliation and MCData group de-affiliation..... | 22 | +| 5.7 Conversation management..... | 22 | +| 5.8 Bearer management..... | 23 | +| 5.8.1 General..... | 23 | +| 5.8.2 EPS bearer considerations..... | 23 | +| 5.8.3 EPS unicast bearer considerations for MCData..... | 23 | +| 5.8.4 MBMS bearer management..... | 23 | +| 5.9 Disposition..... | 23 | +| 5.10 MCData message store..... | 24 | +| 5.11 IP connectivity (IPcon) capability..... | 24 | +| 5.12 MBMS user service architecture requirements..... | 25 | +| 5.13 MBMS delivery via MB2 interface..... | 26 | +| 5.14 Delivery Notification..... | 26 | +| 6 Functional model..... | 26 | +| 6.1 General..... | 26 | +| 6.2 Description of the planes..... | 26 | +| 6.3 Transmission and reception control aspects..... | 26 | +| 6.3.1 General..... | 26 | +| 6.4 Generic functional model..... | 27 | +| 6.4.1 On-network functional model..... | 27 | +| 6.4.2 Off-network functional model..... | 27 | +| 6.4.3 Functional entities description..... | 27 | +| 6.4.3.1 Application plane..... | 28 | +| 6.4.3.1.1 MCData client..... | 28 | +| 6.4.3.1.2 MCData server..... | 28 | +| 6.4.3.1.3 MCData user database..... | 29 | +| 6.4.3.1.4 Interworking function to LMR system..... | 29 | +| 6.4.3.1.5 MC gateway server..... | 29 | +| 6.4.3.2 Signalling control plane..... | 29 | +| 6.4.3.3 MCData message store..... | 29 | +| 6.4.3.4 Message store client..... | 29 | +| 6.4.3.5 MCData notification server..... | 29 | +| 6.4.3.6 Message notification client..... | 30 | +| 6.4.4 Reference points..... | 30 | +| 6.4.4.1 Application plane..... | 30 | +| 6.4.4.1.1 General..... | 30 | +| 6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database)..... | 30 | +| 6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server)..... | 30 | +| 6.4.4.1.3A Reference point MCData-5 (between the MCData server and the EPS)..... | 30 | +| 6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS)..... | 30 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------|----| +| 6.4.4.1.5 | Reference point IWF-2 (between the interworking function to LMR system and the MCData server)..... | 30 | +| 6.4.4.1.6 | Reference point MCData-7 (between the Message store client and MCData message store)..... | 31 | +| 6.4.4.1.7 | Reference point MCData-8 (between the MCData message store and MCData server)..... | 31 | +| 6.4.4.1.8 | Reference point MCData-9 (between the MC gateway server and the MC gateway server in a different MCData system)..... | 31 | +| 6.4.4.1.9 | Reference point MCData-10 (between the Message notification client and MCData notification server) ..... | 31 | +| 6.4.4.1.10 | Reference point MCData-11 (between the MCData message store and the MCData notification server) ..... | 31 | +| 6.5 | Functional model for short data service ..... | 31 | +| 6.5.1 | On-network functional model..... | 31 | +| 6.5.2 | Off-network functional model..... | 32 | +| 6.5.3 | Functional entities description..... | 33 | +| 6.5.3.1 | Application plane..... | 33 | +| 6.5.3.1.1 | SDS function ..... | 33 | +| 6.5.3.1.2 | SDS distribution function..... | 33 | +| 6.5.3.1.3 | Transmission/Reception control..... | 33 | +| 6.5.3.2 | Signalling control plane ..... | 33 | +| 6.5.4 | Reference points ..... | 34 | +| 6.5.4.1 | Application plane..... | 34 | +| 6.5.4.1.1 | Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function) ..... | 34 | +| 6.5.4.1.2 | Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function) ..... | 34 | +| 6.5.4.1.3 | Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function)..... | 34 | +| 6.5.4.2 | Signalling control plane ..... | 34 | +| 6.6 | Functional model for file distribution ..... | 34 | +| 6.6.1 | On-network functional model..... | 34 | +| 6.6.1a | On-network functional model for interconnection ..... | 35 | +| 6.6.2 | Off-network functional model..... | 36 | +| 6.6.3 | Functional entities description..... | 37 | +| 6.6.3.1 | Application plane..... | 37 | +| 6.6.3.1.1 | FD function ..... | 37 | +| 6.6.3.1.2 | Media storage client ..... | 37 | +| 6.6.3.1.3 | Transmission/Reception control..... | 37 | +| 6.6.3.1.4 | Media storage function..... | 38 | +| 6.6.3.1.5 | MCData content server..... | 38 | +| 6.6.3.2 | Signalling control plane ..... | 38 | +| 6.6.4 | Reference points ..... | 38 | +| 6.6.4.1 | Application plane..... | 38 | +| 6.6.4.1.1 | Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server)..... | 38 | +| 6.6.4.1.2 | Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server)..... | 39 | +| 6.6.4.1.3 | Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) ..... | 39 | +| 6.6.4.1.4 | Reference point MCData-FD-4 (media storage function and media storage client)..... | 39 | +| 6.6.4.1.5 | Reference point MCData-FD-5 (FD function and media storage function) ..... | 39 | +| 6.6.4.1.6 | Reference point MCData-FD-7 (media storage function and MCData message store)..... | 39 | +| 6.6.4.2 | Signalling control plane ..... | 39 | +| 6.7 | Functional model for data streaming..... | 39 | +| 6.7.1 | On-network functional model..... | 39 | +| 6.7.2 | Off-network functional model..... | 40 | +| 6.7.3 | Functional entities description..... | 40 | +| 6.7.3.1 | Application plane..... | 40 | +| 6.7.3.1.1 | DS function ..... | 40 | +| 6.7.3.1.2 | Data streaming and distribution function..... | 40 | +| 6.7.3.1.3 | Transmission/Reception control..... | 41 | +| 6.7.3.2 | Signalling control plane ..... | 41 | +| 6.7.4 | Reference points ..... | 41 | + +| | | | +|-------------|------------------------------------------------------------------------------------------------------------------------|----| +| 6.7.4.1 | Application plane..... | 41 | +| 6.7.4.1.1 | Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function) ..... | 41 | +| 6.7.4.1.2 | Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function) ..... | 41 | +| 6.7.4.1.3 | Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) ..... | 42 | +| 6.7.4.2 | Signalling control plane ..... | 42 | +| 6.8 | Functional model for IP connectivity..... | 42 | +| 6.8.1 | On-network functional model..... | 42 | +| 6.8.2 | Off-network functional model..... | 43 | +| 6.8.3 | Functional entities description..... | 43 | +| 6.8.3.1 | Application plane..... | 43 | +| 6.8.3.1.1 | IP connectivity function ..... | 43 | +| 6.8.3.1.2 | IPcon distribution function..... | 43 | +| 6.8.3.1.3 | Transmission/Reception control..... | 43 | +| 6.8.3.2 | Signalling control plane ..... | 43 | +| 6.8.4 | Reference points ..... | 43 | +| 6.8.4.1 | Application plane..... | 43 | +| 6.8.4.1.1 | Reference point MCData-IPcon-1 (between the IPcon distribution function and the U-IPcon function) ..... | 43 | +| 6.8.4.1.2 | Reference point MCData-IPcon-2 (unicast between the U-IPcon distribution function and the U-IPcon function)..... | 43 | +| 6.8.4.1.3 | Reference point MCData-IPcon-3 (multicast between the IPcon distribution function and the IPcon function)..... | 44 | +| 6.8.4.2 | Signalling control plane ..... | 44 | +| 7 | Procedures and information flows ..... | 44 | +| 7.1 | MCData service configuration ..... | 44 | +| 7.2 | Affiliation and de-affiliation to/from MCData group(s) ..... | 44 | +| 7.3 | Use of MBMS transmission (on-network)..... | 45 | +| 7.3.1 | Information flows for MBMS Transmission..... | 45 | +| 7.3.2 | Use of pre-established MBMS bearers..... | 45 | +| 7.3.3 | Use of dynamic MBMS bearer establishment..... | 45 | +| 7.3.4 | Switching from MBMS bearer to unicast bearer..... | 45 | +| 7.3.5 | Use of MBMS user services for file distribution..... | 46 | +| 7.3.5.1 | General ..... | 46 | +| 7.3.5.2 | Information flows for MBMS user service usage..... | 46 | +| 7.3.5.2.1 | MBMS user service announcement..... | 46 | +| 7.3.5.3 | Procedures for MBMS user service usage..... | 46 | +| 7.3.5.3.1 | Use of pre-established MBMS user services..... | 46 | +| 7.3.5.3.1.1 | General ..... | 46 | +| 7.3.5.3.1.2 | Procedure ..... | 46 | +| 7.3.5.3.2 | Use of dynamic MBMS user service establishment..... | 48 | +| 7.3.5.3.3 | Providing stored files in the MCData content server for distribution over MBMS ..... | 49 | +| 7.3.5.3.3.1 | General ..... | 49 | +| 7.3.5.3.3.2 | File fetching by the MCData server ..... | 49 | +| 7.3.5.3.3.3 | File fetching by the BM-SC ..... | 51 | +| 7.3.6 | Group communication connect and disconnect over MBMS bearer procedures ..... | 52 | +| 7.3.6.1 | General ..... | 52 | +| 7.3.6.2 | Procedure ..... | 53 | +| 7.3.6.2.1 | Group communication connect over MBMS bearer ..... | 53 | +| 7.3.6.2.2 | Group communication disconnect from MBMS bearer..... | 54 | +| 7.4 | Short data service ..... | 54 | +| 7.4.1 | General ..... | 54 | +| 7.4.2 | Short data service for on-network ..... | 55 | +| 7.4.2.1 | Information flows for short data service..... | 55 | +| 7.4.2.1.1 | MCData standalone data request..... | 55 | +| 7.4.2.1.2 | MCData data disposition notification ..... | 56 | +| 7.4.2.1.3 | MCData standalone session data request ..... | 56 | +| 7.4.2.1.4 | MCData standalone session data response..... | 58 | +| 7.4.2.1.5 | MCData session data request ..... | 58 | + +| | | | +|------------|-----------------------------------------------------------------------------------------|----| +| 7.4.2.1.6 | MCData session data response..... | 59 | +| 7.4.2.1.7 | MCData group standalone data request (MCData client – MCData server)..... | 59 | +| 7.4.2.1.8 | MCData group standalone data request (MCData server – MCData client)..... | 60 | +| 7.4.2.1.9 | MCData data disposition notification (MCData server – MCData client)..... | 61 | +| 7.4.2.1.9A | MCData aggregated data disposition notification..... | 61 | +| 7.4.2.1.10 | MCData group session standalone data request (MCData client – MCData server) ..... | 62 | +| 7.4.2.1.11 | MCData group session standalone data request (MCData server – MCData client) ..... | 63 | +| 7.4.2.1.12 | MCData group session standalone data response ..... | 63 | +| 7.4.2.1.13 | MCData group data request (MCData client – MCData server)..... | 63 | +| 7.4.2.1.14 | MCData group data request (MCData server – MCData client)..... | 64 | +| 7.4.2.1.15 | MCData group data response ..... | 65 | +| 7.4.2.1.16 | MCData one-to-one SDS communication upgrade request ..... | 65 | +| 7.4.2.1.17 | MCData one-to-one SDS communication upgrade response..... | 66 | +| 7.4.2.1.18 | MCData group SDS communication upgrade request ..... | 66 | +| 7.4.2.1.19 | MCData group SDS communication upgrade response..... | 67 | +| 7.4.2.1.20 | MCData group SDS communication in-progress priority state cancel request ..... | 67 | +| 7.4.2.1.21 | MCData group SDS communication in-progress priority state cancel response ..... | 68 | +| 7.4.2.1.22 | MCData functional alias resolution response..... | 68 | +| 7.4.2.2 | One-to-one standalone short data service using signalling control plane..... | 68 | +| 7.4.2.2.1 | General ..... | 68 | +| 7.4.2.2.2 | Procedure..... | 68 | +| 7.4.2.3 | One-to-one standalone short data service using media plane ..... | 70 | +| 7.4.2.3.1 | General ..... | 70 | +| 7.4.2.3.2 | Procedure..... | 71 | +| 7.4.2.4 | One-to-one short data service session..... | 73 | +| 7.4.2.4.1 | General ..... | 73 | +| 7.4.2.4.2 | Procedure..... | 73 | +| 7.4.2.5 | Group standalone short data service using signalling control plane..... | 75 | +| 7.4.2.5.1 | General ..... | 75 | +| 7.4.2.5.2 | Procedure..... | 75 | +| 7.4.2.6 | Group standalone short data service using media plane ..... | 78 | +| 7.4.2.6.1 | General ..... | 78 | +| 7.4.2.6.2 | Procedure..... | 78 | +| 7.4.2.7 | Group short data service session..... | 81 | +| 7.4.2.7.1 | General ..... | 81 | +| 7.4.2.7.2 | Procedure..... | 81 | +| 7.4.2.8 | One-to-one SDS communication upgrade to an emergency one-to-one SDS communication ..... | 84 | +| 7.4.2.8.1 | General ..... | 84 | +| 7.4.2.8.2 | Procedure..... | 84 | +| 7.4.2.9 | Group SDS communication upgrade to a group emergency SDS communication ..... | 85 | +| 7.4.2.9.1 | General ..... | 85 | +| 7.4.2.9.2 | Procedure..... | 85 | +| 7.4.2.10 | Group SDS communication in-progress emergency group state cancel..... | 87 | +| 7.4.2.10.1 | General ..... | 87 | +| 7.4.2.10.2 | Procedure..... | 87 | +| 7.4.2.11 | Group SDS communication upgrade to an imminent peril group SDS communication ..... | 89 | +| 7.4.2.11.1 | General ..... | 89 | +| 7.4.2.11.2 | Procedure..... | 89 | +| 7.4.2.12 | Group SDS communication in-progress imminent peril group state cancel ..... | 89 | +| 7.4.2.12.1 | General ..... | 89 | +| 7.4.2.12.2 | Procedure..... | 89 | +| 7.4.2.13 | Providing data for a user entering an ongoing MCData group conversation ..... | 89 | +| 7.4.2.13.1 | General ..... | 89 | +| 7.4.2.13.2 | Procedure..... | 89 | +| 7.4.3 | Short data service for off-network..... | 91 | +| 7.4.3.1 | General ..... | 91 | +| 7.4.3.2 | Information flows for short data service..... | 91 | +| 7.4.3.2.1 | MCData standalone data request..... | 91 | +| 7.4.3.2.2 | MCData data disposition notification ..... | 91 | +| 7.4.3.2.3 | MCData group standalone data request ..... | 91 | +| 7.4.3.3 | One-to-one standalone short data service using signalling control plane..... | 92 | +| 7.4.3.3.1 | General ..... | 92 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------|-----| +| 7.4.3.3.2 | Procedure..... | 92 | +| 7.4.3.4 | Group standalone short data service using signalling control plane..... | 93 | +| 7.4.3.4.1 | General ..... | 93 | +| 7.4.3.4.2 | Procedure..... | 94 | +| 7.4.3.5 | Void ..... | 95 | +| 7.4.3.6 | Group standalone short data service with MCData message store ..... | 95 | +| 7.4.3.6.1 | General ..... | 95 | +| 7.4.3.6.2 | Procedure..... | 95 | +| 7.5 | File distribution ..... | 96 | +| 7.5.1 | General ..... | 96 | +| 7.5.2 | File distribution for on-network ..... | 96 | +| 7.5.2.1 | Information flows for file distribution ..... | 96 | +| 7.5.2.1.1 | MCData upload data request..... | 96 | +| 7.5.2.1.2 | MCData upload data response..... | 96 | +| 7.5.2.1.3 | MCData download data request..... | 97 | +| 7.5.2.1.4 | MCData download data response..... | 97 | +| 7.5.2.1.5 | MCData FD request (using HTTP)..... | 97 | +| 7.5.2.1.6 | MCData FD response (using HTTP)..... | 98 | +| 7.5.2.1.7 | MCData download completed report ..... | 99 | +| 7.5.2.1.7A | MCData aggregated download completed report..... | 99 | +| 7.5.2.1.8 | MCData FD request (using media plane)..... | 99 | +| 7.5.2.1.9 | MCData FD response (using media plane) ..... | 101 | +| 7.5.2.1.10 | MCData group standalone FD request (using HTTP)..... | 101 | +| 7.5.2.1.11 | MCData group standalone FD response (using HTTP or MBMS download delivery method) .... | 103 | +| 7.5.2.1.12 | MCData group standalone FD request (using media plane) ..... | 103 | +| 7.5.2.1.13 | MCData group standalone FD response (using media plane)..... | 104 | +| 7.5.2.1.14 | MCData remove file request by user..... | 104 | +| 7.5.2.1.15 | MCData remove file response by user ..... | 105 | +| 7.5.2.1.16 | Void..... | 105 | +| 7.5.2.1.17 | Void..... | 105 | +| 7.5.2.1.18 | MCData remove file notify ..... | 105 | +| 7.5.2.1.19 | MCData file retrieve request ..... | 105 | +| 7.5.2.1.20 | MCData file retrieve response..... | 106 | +| 7.5.2.1.21 | MCData group standalone FD over MBMS request..... | 106 | +| 7.5.2.1.22 | MCData one-to-one FD upgrade request ..... | 106 | +| 7.5.2.1.23 | MCData one-to-one FD upgrade response..... | 106 | +| 7.5.2.1.24 | MCData group FD upgrade request ..... | 107 | +| 7.5.2.1.25 | MCData group FD upgrade response..... | 108 | +| 7.5.2.1.26 | MCData group FD in-progress priority state cancel request..... | 108 | +| 7.5.2.1.27 | MCData group FD in-progress priority state cancel response ..... | 108 | +| 7.5.2.1.28 | MCData file upload request ..... | 109 | +| 7.5.2.1.29 | MCData file upload response..... | 109 | +| 7.5.2.1.30 | MCData file upload completion status..... | 109 | +| 7.5.2.1.31 | MCData file download request ..... | 109 | +| 7.5.2.1.32 | MCData file download response..... | 110 | +| 7.5.2.1.33 | MCData file availability request ..... | 110 | +| 7.5.2.1.34 | MCData file availability response..... | 110 | +| 7.5.2.2 | File upload using HTTP..... | 110 | +| 7.5.2.2.1 | General ..... | 110 | +| 7.5.2.2.2 | Procedure for uploading the file residing in the local storage of the MCData UE without QoS ... | 111 | +| 7.5.2.2.3 | Procedure for uploading the file residing in the MCData message store..... | 111 | +| 7.5.2.2.4 | Procedure for file upload including request of network resources with required QoS ..... | 112 | +| 7.5.2.3 | File download using HTTP..... | 114 | +| 7.5.2.3.1 | General ..... | 114 | +| 7.5.2.3.2 | Procedure for file download from the MCData content server without QoS..... | 114 | +| 7.5.2.3.3 | Procedure for file download including request of network resources with required QoS ..... | 114 | +| 7.5.2.4 | One-to-one file distribution using HTTP..... | 116 | +| 7.5.2.4.1 | General ..... | 116 | +| 7.5.2.4.2 | Procedure for single MCData system..... | 116 | +| 7.5.2.4.3 | Procedure with interconnection between MCData systems ..... | 118 | +| 7.5.2.5 | One-to-one file distribution using media plane ..... | 121 | +| 7.5.2.5.1 | General ..... | 121 | + +| | | | +|------------|----------------------------------------------------------------------------------|-----| +| 7.5.2.5.2 | Procedure..... | 121 | +| 7.5.2.6 | Group standalone file distribution using HTTP..... | 123 | +| 7.5.2.6.1 | General ..... | 123 | +| 7.5.2.6.2 | Procedure..... | 123 | +| 7.5.2.7 | Group standalone file distribution using media plane ..... | 126 | +| 7.5.2.7.1 | General ..... | 126 | +| 7.5.2.7.2 | Procedure..... | 126 | +| 7.5.2.8 | File removal using HTTP by authorized user..... | 129 | +| 7.5.2.8.1 | General ..... | 129 | +| 7.5.2.8.2 | Procedure for single MCData system..... | 129 | +| 7.5.2.8.3 | Procedure for interconnection between MCData systems ..... | 129 | +| 7.5.2.9 | Void ..... | 131 | +| 7.5.2.10 | Group standalone file distribution using the MBMS download delivery method ..... | 131 | +| 7.5.2.10.1 | General ..... | 131 | +| 7.5.2.10.2 | Procedure..... | 131 | +| 7.5.2.11 | One-to-one FD communication upgrade to an emergency FD communication..... | 132 | +| 7.5.2.11.1 | General ..... | 132 | +| 7.5.2.11.2 | Procedure..... | 133 | +| 7.5.2.12 | Group FD communication upgrade to an emergency group FD communication..... | 134 | +| 7.5.2.12.1 | General ..... | 134 | +| 7.5.2.12.2 | Procedure..... | 134 | +| 7.5.2.13 | Group FD communication in-progress emergency group state cancel..... | 136 | +| 7.5.2.13.1 | General ..... | 136 | +| 7.5.2.13.2 | Procedure..... | 136 | +| 7.5.2.14 | Group FD communication upgrade to an imminent peril group FD communication ..... | 138 | +| 7.5.2.14.1 | General ..... | 138 | +| 7.5.2.14.2 | Procedure..... | 138 | +| 7.5.2.15 | Group FD communication in-progress imminent peril group state cancel..... | 138 | +| 7.5.2.15.1 | General ..... | 138 | +| 7.5.2.15.2 | Procedure..... | 138 | +| 7.5.3 | File distribution for off-network..... | 138 | +| 7.5.3.1 | General ..... | 138 | +| 7.5.3.2 | Information flows for file distribution ..... | 138 | +| 7.5.3.2.1 | MCData FD request (using media plane)..... | 138 | +| 7.5.3.2.2 | MCData FD response (using media plane) ..... | 139 | +| 7.5.3.2.3 | MCData download completed report ..... | 139 | +| 7.5.3.2.4 | MCData group standalone FD request (using media plane) ..... | 139 | +| 7.5.3.2.5 | MCData group standalone FD response (using media plane)..... | 140 | +| 7.5.3.3 | One-to-one standalone file distribution using media plane ..... | 140 | +| 7.5.3.3.1 | General ..... | 140 | +| 7.5.3.3.2 | Procedure..... | 140 | +| 7.5.3.4 | Group standalone file distribution using media plane ..... | 141 | +| 7.5.3.4.1 | General ..... | 141 | +| 7.5.3.4.2 | Procedure..... | 141 | +| 7.6 | Transmission and reception control ..... | 143 | +| 7.6.1 | General ..... | 143 | +| 7.6.2 | Transmission and reception control for on-network..... | 143 | +| 7.6.2.1 | Information flows for transmission and reception control..... | 143 | +| 7.6.2.1.1 | MCData control indication..... | 143 | +| 7.6.2.1.2 | MCData indication ..... | 143 | +| 7.6.2.1.3 | MCData get deferred list request ..... | 143 | +| 7.6.2.1.4 | MCData get deferred list response..... | 144 | +| 7.6.2.2 | Automatic transmission for SDS ..... | 144 | +| 7.6.2.2.1 | General ..... | 144 | +| 7.6.2.2.2 | Procedure..... | 144 | +| 7.6.2.3 | Send data with mandatory download..... | 145 | +| 7.6.2.3.1 | General ..... | 145 | +| 7.6.2.3.2 | Procedure..... | 145 | +| 7.6.2.4 | Send data without mandatory download..... | 147 | +| 7.6.2.4.1 | General ..... | 147 | +| 7.6.2.4.2 | Procedure..... | 147 | +| 7.6.2.5 | Accessing list of deferred data group communications ..... | 148 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------------|-----| +| 7.6.2.5.1 | General ..... | 148 | +| 7.6.2.5.2 | Procedure..... | 148 | +| 7.7 | Communication release..... | 149 | +| 7.7.1 | General ..... | 149 | +| 7.7.2 | Communication release for on-network..... | 149 | +| 7.7.2.1 | Information flows for communication release..... | 149 | +| 7.7.2.1.1 | MCData communication release request (one-to-one communication using media plane)..... | 149 | +| 7.7.2.1.2 | MCData communication release response (one-to-one communication using media plane)..... | 149 | +| 7.7.2.1.3 | MCData communication release request (group communication using media plane)..... | 150 | +| 7.7.2.1.4 | MCData communication release response (group communication using media plane)..... | 150 | +| 7.7.2.1.5 | Void..... | 150 | +| 7.7.2.1.6 | Void..... | 150 | +| 7.7.2.1.7 | Void..... | 150 | +| 7.7.2.1.8 | MCData server communication release request (one-to-one communication using media plane)..... | 150 | +| 7.7.2.1.9 | MCData server communication release response (one-to-one communication using media plane)..... | 151 | +| 7.7.2.1.10 | MCData server communication release request (group communication using media plane)..... | 151 | +| 7.7.2.1.11 | MCData server communication release response (group communication using media plane)..... | 151 | +| 7.7.2.1.12 | Void..... | 152 | +| 7.7.2.1.13 | MCData release intent request (one-to-one communication using media plane)..... | 152 | +| 7.7.2.1.14 | MCData more information response (one-to-one communication using media plane)..... | 152 | +| 7.7.2.1.15 | MCData release intent request (group communication using media plane)..... | 152 | +| 7.7.2.1.16 | MCData more information response (group communication using media plane)..... | 152 | +| 7.7.2.1.17 | MCData auth user communication release request (one-to-one communication using media plane)..... | 153 | +| 7.7.2.1.18 | MCData auth user communication release response (one-to-one communication using media plane)..... | 153 | +| 7.7.2.1.19 | MCData auth user communication release request (group communication using media plane)..... | 153 | +| 7.7.2.1.20 | MCData auth user communication release response (group communication using media plane)..... | 154 | +| 7.7.2.1.21 | MCData request for extension..... | 154 | +| 7.7.2.1.22 | MCData response for extension..... | 154 | +| 7.7.2.2 | MCData user initiated communication release..... | 154 | +| 7.7.2.2.1 | General ..... | 154 | +| 7.7.2.2.2 | Release of MCData communication using media plane ..... | 154 | +| 7.7.2.2.2.1 | General ..... | 154 | +| 7.7.2.2.2.2 | Procedure..... | 155 | +| 7.7.2.2.3 | Release of MCData communication using HTTP..... | 155 | +| 7.7.2.3 | MCData server initiated communication release without prior indication..... | 156 | +| 7.7.2.3.1 | General ..... | 156 | +| 7.7.2.3.2 | Release of MCData communication using media plane ..... | 156 | +| 7.7.2.3.2.1 | General ..... | 156 | +| 7.7.2.3.2.2 | Procedure..... | 156 | +| 7.7.2.3.3 | Void..... | 158 | +| 7.7.2.4 | MCData server initiated communication release with prior indication..... | 158 | +| 7.7.2.4.1 | General ..... | 158 | +| 7.7.2.4.2 | Procedure..... | 158 | +| 7.7.2.5 | Authorized MCData user initiated communication release without prior indication ..... | 159 | +| 7.7.2.5.1 | General ..... | 159 | +| 7.7.2.5.2 | Procedure..... | 159 | +| 7.7.2.6 | Authorized MCData user initiated communication release with prior indication ..... | 160 | +| 7.7.2.6.1 | General ..... | 160 | +| 7.7.2.6.2 | Procedure..... | 160 | +| 7.8 | Conversation management..... | 162 | +| 7.8.1 | General ..... | 162 | +| 7.8.2 | Conversation management for on-network ..... | 162 | +| 7.8.2.1 | Information flows for conversation management..... | 162 | +| 7.8.2.2 | One-to-one conversation management ..... | 162 | +| 7.8.2.2.1 | Procedure..... | 162 | +| 7.8.2.3 | Group conversation management ..... | 163 | +| 7.8.2.3.1 | Procedure..... | 163 | + +| | | | +|------------|----------------------------------------------------------------|-----| +| 7.8.3 | Conversation management for off-network..... | 163 | +| 7.8.3.1 | One-to-one conversation management ..... | 163 | +| 7.8.3.1.1 | Procedure..... | 163 | +| 7.8.3.2 | Group conversation management ..... | 164 | +| 7.8.3.2.1 | Procedure..... | 164 | +| 7.9 | Enhanced status ..... | 165 | +| 7.9.1 | General ..... | 165 | +| 7.9.2 | Preset values for enhanced status ..... | 165 | +| 7.9.3 | Enhanced status for on-network ..... | 165 | +| 7.9.3.1 | Sharing enhanced status information ..... | 165 | +| 7.9.3.1.1 | Procedure..... | 165 | +| 7.9.4 | Enhanced status for off-network..... | 166 | +| 7.9.4.1 | Sharing enhanced status information..... | 166 | +| 7.9.4.1.1 | Procedure..... | 166 | +| 7.10 | MCData emergency alert (on-network and off-network) ..... | 167 | +| 7.10a | MCData ad hoc group emergency alert (on-network) ..... | 167 | +| 7.11 | User authentication and authorization for MCData service ..... | 168 | +| 7.12 | MCData resource management (on-network) ..... | 168 | +| 7.12.1 | General ..... | 168 | +| 7.12.2 | Void ..... | 168 | +| 7.13 | Operations on MCData message store ..... | 168 | +| 7.13.1 | MCData message store structure ..... | 169 | +| 7.13.2 | Authentication and authorization ..... | 169 | +| 7.13.3 | Manage MCData message store ..... | 170 | +| 7.13.3.1 | Information flows for managing MCData message store ..... | 170 | +| 7.13.3.1.1 | MCData retrieve a stored object request..... | 170 | + +| | | | +|-------------|-----------------------------------------------------|-----| +| 7.13.3.1.2 | MCData retrieve a stored object response..... | 170 | +| 7.13.3.1.3 | MCData search stored objects request ..... | 170 | +| 7.13.3.1.4 | MCData search stored objects response..... | 170 | +| 7.13.3.1.5 | MCData update a stored object request..... | 171 | +| 7.13.3.1.6 | MCData update a stored object response ..... | 171 | +| 7.13.3.1.7 | MCData delete a stored object request..... | 171 | +| 7.13.3.1.8 | MCData delete a stored object response ..... | 171 | +| 7.13.3.1.9 | MCData synchronization request..... | 171 | +| 7.13.3.1.10 | MCData synchronization response..... | 172 | +| 7.13.3.1.11 | MCData create a user account request ..... | 172 | +| 7.13.3.1.12 | MCData create a user account response..... | 172 | +| 7.13.3.1.13 | MCData deposit an object request ..... | 172 | +| 7.13.3.1.14 | MCData deposit an object response ..... | 173 | +| 7.13.3.1.15 | MCData copy a stored object request ..... | 173 | +| 7.13.3.1.16 | MCData copy a stored object response ..... | 173 | +| 7.13.3.1.17 | MCData move a stored object request ..... | 173 | +| 7.13.3.1.18 | MCData move a stored object response..... | 173 | +| 7.13.3.1.19 | MCData create folder request ..... | 174 | +| 7.13.3.1.20 | MCData create folder response..... | 174 | +| 7.13.3.1.21 | MCData delete folder request ..... | 174 | +| 7.13.3.1.22 | MCData delete folder response..... | 174 | +| 7.13.3.1.23 | MCData copy folder request ..... | 174 | +| 7.13.3.1.24 | MCData copy folder response..... | 175 | +| 7.13.3.1.25 | MCData move folder request..... | 175 | +| 7.13.3.1.26 | MCData move folder response..... | 175 | +| 7.13.3.1.27 | MCData list folder request..... | 175 | +| 7.13.3.1.28 | MCData list folder response..... | 176 | +| 7.13.3.1.29 | MCData upload objects request ..... | 176 | +| 7.13.3.1.30 | MCData upload objects response..... | 176 | +| 7.13.3.1.31 | MCData synchronization notification ..... | 176 | +| 7.13.3.1.32 | Create notification channel request..... | 177 | +| 7.13.3.1.33 | Create notification channel response..... | 177 | +| 7.13.3.1.34 | Open notification channel ..... | 177 | +| 7.13.3.1.35 | Subscribe for notification request ..... | 177 | +| 7.13.3.1.36 | Subscribe for notification response ..... | 178 | +| 7.13.3.1.37 | MCData search folder request..... | 178 | +| 7.13.3.1.38 | MCData search folder response ..... | 178 | +| 7.13.3.1.39 | MCData retrieve folder content request..... | 178 | +| 7.13.3.1.40 | MCData retrieve folder content response..... | 178 | +| 7.13.3.1.41 | MCData retrieve file to store locally request ..... | 179 | +| 7.13.3.1.42 | MCData retrieve file to store locally response..... | 179 | +| 7.13.3.1.43 | Update notification channel request..... | 179 | +| 7.13.3.1.44 | Update notification channel response ..... | 179 | +| 7.13.3.1.45 | Update notification subscription request..... | 180 | +| 7.13.3.1.46 | Update notification subscription response ..... | 180 | +| 7.13.3.1.47 | Delete notification channel request..... | 180 | +| 7.13.3.1.48 | Delete notification channel response..... | 180 | +| 7.13.3.1.49 | Delete notification subscription request..... | 181 | +| 7.13.3.1.50 | Delete notification subscription response ..... | 181 | +| 7.13.3.1.51 | Notification message..... | 181 | +| 7.13.3.2 | Retrieve a stored object..... | 181 | +| 7.13.3.2.1 | General ..... | 181 | +| 7.13.3.2.2 | Procedure..... | 181 | +| 7.13.3.3 | Search stored objects ..... | 182 | +| 7.13.3.3.1 | General ..... | 182 | +| 7.13.3.3.2 | Procedure..... | 182 | +| 7.13.3.4 | Update a stored object..... | 183 | +| 7.13.3.4.1 | General ..... | 183 | +| 7.13.3.4.2 | Procedure..... | 183 | +| 7.13.3.5 | Delete a stored object..... | 184 | +| 7.13.3.5.1 | General ..... | 184 | +| 7.13.3.5.2 | Procedure..... | 184 | + +| | | | +|-------------|---------------------------------------------------------------|-----| +| 7.13.3.6 | Synchronization ..... | 185 | +| 7.13.3.6.1 | General ..... | 185 | +| 7.13.3.6.2 | Procedure..... | 185 | +| 7.13.3.7 | Create a user account ..... | 186 | +| 7.13.3.7.1 | General ..... | 186 | +| 7.13.3.7.2 | Procedure..... | 186 | +| 7.13.3.8 | Deposit an object ..... | 187 | +| 7.13.3.8.1 | General ..... | 187 | +| 7.13.3.8.2 | Procedure..... | 187 | +| 7.13.3.9 | Copy a stored object ..... | 188 | +| 7.13.3.9.1 | General ..... | 188 | +| 7.13.3.9.2 | Procedure..... | 188 | +| 7.13.3.10 | Move a stored object..... | 189 | +| 7.13.3.10.1 | General ..... | 189 | +| 7.13.3.10.2 | Procedure..... | 189 | +| 7.13.3.11 | Folder create operation ..... | 190 | +| 7.13.3.11.1 | General ..... | 190 | +| 7.13.3.11.2 | Procedure..... | 190 | +| 7.13.3.12 | Folder delete operation ..... | 191 | +| 7.13.3.12.1 | General ..... | 191 | +| 7.13.3.12.2 | Procedure..... | 191 | +| 7.13.3.13 | Folder copy operation ..... | 192 | +| 7.13.3.13.1 | General ..... | 192 | +| 7.13.3.13.2 | Procedure..... | 192 | +| 7.13.3.14 | Folder move operation ..... | 193 | +| 7.13.3.14.1 | General ..... | 193 | +| 7.13.3.14.2 | Procedure..... | 193 | +| 7.13.3.15 | Folder list operation ..... | 194 | +| 7.13.3.15.1 | General ..... | 194 | +| 7.13.3.15.2 | Procedure..... | 194 | +| 7.13.3.16 | Upload objects ..... | 195 | +| 7.13.3.16.1 | General ..... | 195 | +| 7.13.3.16.2 | Procedure..... | 195 | +| 7.13.3.17 | Notify client to synchronize..... | 196 | +| 7.13.3.17.1 | General ..... | 196 | +| 7.13.3.17.2 | Procedure using in-band connection ..... | 196 | +| 7.13.3.17.3 | Procedure using MCData notification server ..... | 197 | +| 7.13.3.18 | Search folder ..... | 200 | +| 7.13.3.18.1 | General ..... | 200 | +| 7.13.3.18.2 | Procedure..... | 201 | +| 7.13.3.19 | Retrieve folder content..... | 201 | +| 7.13.3.19.1 | General ..... | 201 | +| 7.13.3.19.2 | Procedure..... | 201 | +| 7.13.3.20 | Store file contents distributed using HTTP..... | 202 | +| 7.13.3.20.1 | General ..... | 202 | +| 7.13.3.20.2 | Procedure for storing the file – receiver side ..... | 202 | +| 7.13.4 | Generic outgoing SDS procedure with MCData message store..... | 203 | +| 7.13.4.1 | General ..... | 203 | +| 7.13.4.2 | Procedure ..... | 203 | +| 7.13.5 | Generic incoming SDS procedure with MCData message store..... | 204 | +| 7.13.5.1 | General ..... | 204 | +| 7.13.5.2 | Procedure ..... | 204 | +| 7.13.6 | Interconnection and migration with MCData message store..... | 205 | +| 7.13.6.1 | Interconnection ..... | 205 | +| 7.13.6.2 | Migration ..... | 205 | +| 7.14 | IP connectivity..... | 205 | +| 7.14.1 | General ..... | 205 | +| 7.14.2 | IP connectivity for on-network..... | 206 | +| 7.14.2.1 | Information flows for IP connectivity ..... | 206 | +| 7.14.2.1.1 | MCData IPcon point-to-point request..... | 206 | +| 7.14.2.1.2 | MCData IPcon point-to-point response..... | 206 | +| 7.14.2.1.3 | MCData remote IPcon point-to-point request..... | 207 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------------|-----| +| 7.14.2.1.4 | MCData remote IPcon point-to-point response ..... | 207 | +| 7.14.2.1.5 | MCData remote IPcon point-to-point tear down request..... | 207 | +| 7.14.2.1.6 | MCData remote IPcon point-to-point tear down response..... | 208 | +| 7.14.2.1.7 | MCData remote IPcon point-to-point application priority change request..... | 208 | +| 7.14.2.1.8 | MCData remote IPcon point-to-point application priority change response ..... | 208 | +| 7.14.2.2 | IP connectivity point-to-point MCData transport service..... | 209 | +| 7.14.2.2.1 | General ..... | 209 | +| 7.14.2.2.2 | Procedure..... | 209 | +| 7.14.2.3 | Remote initiated point-to-point IP connectivity ..... | 211 | +| 7.14.2.3.1 | General ..... | 211 | +| 7.14.2.3.2 | Procedure..... | 211 | +| 7.14.2.4 | MCData user remote initiated tear down point-to-point IP connectivity ..... | 212 | +| 7.14.2.4.1 | General ..... | 212 | +| 7.14.2.4.2 | Procedure..... | 212 | +| 7.14.2.5 | Remote initiated point-to-point IP connectivity application priority change ..... | 213 | +| 7.14.2.5.1 | General ..... | 213 | +| 7.14.2.5.2 | Procedure..... | 213 | +| 7.14.2.6 | Group standalone IP connectivity using media plane..... | 214 | +| 7.14.2.6.1 | General ..... | 214 | +| 7.14.2.6.2 | Procedure..... | 214 | +| 7.15 | Location information (on-network)..... | 216 | +| 7.16 | Use of ProSe capabilities in off-network MCData communications ..... | 216 | +| 7.16.1 | General ..... | 216 | +| 7.16.2 | Procedures ..... | 216 | +| 7.17 | Ad hoc group data communication ..... | 217 | +| 7.17.1 | General ..... | 217 | +| 7.17.2 | Common Information flows ..... | 217 | +| 7.17.2.1 | Ad hoc group data session request (MCData client – MCData server)..... | 217 | +| 7.17.2.2 | Ad hoc group data session request return (MCData server – MCData client) ..... | 220 | +| 7.17.2.3 | Ad hoc group data session request (MCData server – MCData server)..... | 220 | +| 7.17.2.4 | Ad hoc group data session request (MCData server – MCData client)..... | 221 | +| 7.17.2.5 | Ad hoc group data session response (MCData server – MCData client) ..... | 222 | +| 7.17.2.6 | Ad hoc group data session response (MCData server – MCData server) ..... | 222 | +| 7.17.2.7 | Ad hoc group data session response (MCData client – MCData server) ..... | 223 | +| 7.17.2.8 | Ad hoc group data session release request (MCData server – MCData client)..... | 223 | +| 7.17.2.9 | Ad hoc group data session release response (MCData client – MCData server) ..... | 224 | +| 7.17.2.10 | Ad hoc group data session notify (MCData server – MCData client)..... | 224 | +| 7.17.2.11 | Modify ad hoc group data session participants request (MCData client – MCData server) ..... | 224 | +| 7.17.2.12 | Modify ad hoc group data session participants response (MCData server – MCData client)..... | 225 | +| 7.17.2.13 | Ad hoc group data session leave request (MCData server – MCData client) ..... | 225 | +| 7.17.2.14 | Ad hoc group data session leave response (MCData client – MCData server)..... | 226 | +| 7.17.2.15 | Ad hoc group data session get userlist (MCData server – MCData server)..... | 226 | +| 7.17.2.16 | Ad hoc group data session get userlist response (MCData server – MCData server) ..... | 226 | +| 7.17.2.17 | Ad hoc group data session add user notification (MCData server – MCData server)..... | 227 | +| 7.17.2.18 | Ad hoc group data session remove user notification (MCData server – MCData server) ..... | 227 | +| 7.17.2.19 | Ad hoc group data session release notification (MCData server – MCData server)..... | 227 | +| 7.17.3 | Common Ad hoc group data communication procedures ..... | 228 | +| 7.17.3.1 | Ad hoc group data communication procedures in single MCData system..... | 228 | +| 7.17.3.1.1 | Ad hoc group data communication setup..... | 228 | +| 7.17.3.1.2 | Release ad hoc group data communication ..... | 231 | +| 7.17.3.1.3 | Ad hoc group data communication setup with MCData server determining the participants lists ..... | 232 | +| 7.17.3.1.4 | Modification of ad hoc group data communication participants by an authorized user ..... | 235 | +| 7.17.3.1.5 | Modification of ad hoc group data communication participants by the MCData server ..... | 237 | +| 7.17.3.2 | Ad hoc group data communication involving multiple MC systems ..... | 239 | +| 7.17.3.2.1 | Procedure for ad hoc group data communication setup – Participants list provided by the Initiator ..... | 239 | +| 7.17.3.2.2 | Procedure for ad hoc group data communication release by MCData server – Participants list provided by the Initiator ..... | 240 | +| 7.17.3.2.3 | Ad hoc group data communication setup – Participants list determined by the MCData server... | 242 | +| 7.17.3.2.4 | Modifying of ad hoc group data communication participants by the MCData server ..... | 244 | + +| | | | +|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| 7.17.3.2.5 | Release ad hoc group data communication and stop determining the ad hoc group data communication participants by partner MCData system – Participants list determined by the MCData server ..... | 246 | +| 7.17.3.2.6 | Modification of ad hoc group data communication participants by an authorized user ..... | 247 | +| 7.17.4 | Ad hoc group short data service data communication procedures ..... | 249 | +| 7.17.4.1 | General ..... | 249 | +| 7.17.4.2 | Information flows for short data service specific ..... | 249 | +| 7.17.4.3 | Ad hoc group short data service data communication procedures in single MCData system ..... | 250 | +| 7.17.4.3.1 | General ..... | 250 | +| 7.17.4.3.2 | Procedure ..... | 250 | +| 7.17.4.4 | Ad hoc group short data service data communication procedures involving multiple MC systems ... | 251 | +| 7.17.4.4.1 | General ..... | 251 | +| 7.17.4.4.2 | Procedure ..... | 251 | +| 7.17.5 | Ad hoc group file distribution communication procedures ..... | 252 | +| 7.17.5.1 | General ..... | 252 | +| 7.17.5.2 | Information flows for file distribution specific ..... | 252 | +| 7.17.5.3 | Ad hoc group file distribution communication procedures in single MCData system ..... | 252 | +| 7.17.5.3.1 | General ..... | 252 | +| 7.17.5.3.2 | Procedure ..... | 252 | +| 7.17.5.4 | Ad hoc group file distribution communication procedures involving multiple MC systems ..... | 253 | +| 7.17.5.4.1 | General ..... | 253 | +| 7.17.5.4.2 | Procedure ..... | 253 | +| Annex A (normative): MCData related configuration data ..... | | 255 | +| A.1 | General ..... | 255 | +| A.2 | MCData UE configuration data ..... | 255 | +| A.3 | MCData user profile configuration data ..... | 256 | +| A.4 | MCData related Group configuration data ..... | 264 | +| A.5 | MCData service configuration data ..... | 266 | +| Annex B (informative): Transmission control for MCData ..... | | 268 | +| B.1 | Overview of transmission control process ..... | 268 | +| B.2 | Transmission control arbitration ..... | 269 | +| Annex C: | Void ..... | 269 | +| Annex D (informative): Example of a User Message Storage Area ..... | | 270 | +| Annex E (informative): Change history ..... | | 271 | + +# --- 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 + +This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in 3GPP TS 23.280 [5] to support MC services over LTE including the common services core. + +MCData services suite consists of the following sub-services: + +- short data service (SDS); +- file distribution (FD); +- data streaming (DS); and + +NOTE: Procedures for DS are not covered in the current specification. + +- IP connectivity. + +MCData features include: + +- conversation management; +- transmission and reception control; +- communication release; and +- enhanced status. + +The corresponding service requirements are defined in 3GPP TS 22.282 [3] and 3GPP TS 22.280 [2]. + +The present document is applicable primarily to MCData service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [4]. Certain application functions of the MCData service could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +# --- 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.280: "Mission Critical Common Requirements (MCCoRe); Stage 1". +- [3] 3GPP TS 22.282: "Mission Critical Data services". +- [4] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [5] 3GPP TS 23.280: "Common functional architecture and information flows to support mission critical communication services; Stage 2". + +- [6] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [8] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [9] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [10] 3GPP TS 23.002: "Network Architecture". +- [11] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); stage 2". +- [12] 3GPP TS 29.283: "Diameter data management applications". +- [13] 3GPP TS 33.180: "Security of the Mission Critical Service". +- [14] 3GPP TS 23.203: "Policy and charging control architecture". +- [15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [16] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 reference point; Stage 3". +- [17] 3GPP TS 29.214: "Policy and charging control over Rx reference point". +- [18] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2". +- [19] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [20] 3GPP TS 29.116: "Representational state transfer over xMB reference point between content provider and BM-SC". +- [21] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". +- [22] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1". + +# --- 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]. + +**Auto-receive:** A mechanism where data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server i.e. without waiting for the receiving user to indicate a present need for the data. + +**Conversation identifier:** A universally unique identifier that identifies a series of related MCData transactions. + +**Data stream:** A sequence of data that is agnostic to any underlying media (e.g. audio, video, telemetry data), on which processing of data (e.g. semantic, syntactic, save or filter operation) can begin before all the content is received. + +**FD disposition:** is one of "not downloaded" and "download completed". + +**Folder Identifier:** A unique identifier that identifies a folder in the MCData message store + +**IP Data:** Structured or unstructured payload that is transparent to the MCData transport service. + +**MCData client:** An instance of an MC service client that provides the client application function for the MCData service. + +**MCData emergency communication:** An MC service emergency group communication or MC service emergency private communication within the MCData service. + +**MCData group:** An MC service group configured for MCData service. + +**MCData group affiliation:** An MC service group affiliation for MCData. + +**MCData group communication:** A one-to-many communication using an MCData service. + +**MCData group de-affiliation:** An MC service group de-affiliation for MCData. + +**MCData ID:** An instance of an MC service ID within the MCData service. + +**MCData imminent peril communication:** An MC service imminent peril group communication within the MCData service. + +**MCData server:** An instance of an MC service server that provides the server application function for the MCData service. + +**MCData service:** A data communication service comprising at least one underlying generic capability (e.g. SDS, file distribution, data streaming) with strong security, high availability, reliability and priority handling to support applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways). + +**MCData UE:** An MC service UE that can be used to participate in MCData services. + +**MCData user:** An MC service user who is authorized for MCData services suite via an MCData UE. + +**Metadata:** data associated with a transmitted or stored SDS, file or data stream, consisting of information from messages (e.g. MCData IDs, conversation ID) and other related information (e.g. size, type). + +**Object:** An MCData communication information (such as a message or a file) that is stored in the MCData message store with its associated metadata. + +**Object identifier:** A unique identifier that identifies an object stored in the MCData message store. + +**Reception control:** A mechanism that allows the MCData service to regulate data reception to the receiving MCData clients. + +**Reply identifier:** A reference to the original MCData transaction to which the current transaction is a reply. + +**SDS data:** A payload with limited size and variable content type used in SDS transactions. + +**SDS disposition:** is one of "undelivered", "delivered" and "read". + +**Standalone communication:** A unidirectional one-to-one or group data communication completed after one transaction. + +**Transaction identifier:** A unique identifier that identifies a MCData transaction within a conversation. + +**Transmission control:** A mechanism that allows the MCData service to regulate data transmission requests from the sending MCData users, either prior to or after active sending from the MCData UE. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply: + +**Mission Critical** + +**Mission Critical Applications** + +**Mission Critical Service** + +**Mission Critical Organization** + +For the purposes of the present document, the following terms given in 3GPP TS 22.179 [22] apply: + +**Group-broadcast group** + +**User-broadcast group** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.282 [3] apply: + +### **MCData system** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [5] apply: + +### **Ad hoc Group Communication** + +### **MC service client** + +### **MC service group** + +### **MC service group affiliation** + +### **MC service group de-affiliation** + +### **MC service ID** + +### **MC service server** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.203 [14] apply: + +### **Dynamic PCC rule** + +## 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]. + +| | | +|-----------|--------------------------------------| +| DS | Data Streaming | +| E2EE | End to End Encryption | +| FD | File Distribution | +| ITSI | Individual TETRA Subscriber Identity | +| LMR | Land Mobile Radio | +| MC | Mission Critical | +| MCData ID | MCData user identity | +| PCC | Policy and Charging Control | +| PCRF | Policy and Charging Rules Function | +| QCI | QoS Class Identifier | +| RSI | Radio Set Identity | +| SDS | Short Data Service | +| UM | Unacknowledged Mode | + +# --- 4 Introduction + +The MCData service suite provides a set of generic capabilities and specific services to enable one-to-one and group data communications between MCData users. + +The MCData architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [5] and aspects of the IMS architecture defined in 3GPP TS 23.228 [6], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for LTE (GCSE\_LTE) architecture defined in 3GPP TS 23.468 [8] defining MBMS support via the MB2 interface, the MBMS User Service architecture defined in 3GPP TS 26.348 [19], the Security of the Mission Critical Service in 3GPP TS 33.180 [13] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [9] to enable support of the MCData service. + +The MCData UE primarily obtains access to the MCData service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [4]. Certain application functions of MCData service can be accessed using MCData UEs via non-3GPP access networks. + +The MCData system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [18]. + +# --- 5 Architectural requirements + +## 5.1 Transmission control + +The MCData service supports the ability to transmit SDS messages automatically towards the selected recipient user (private communication) or members of the selected MCData group. The MCData server may still reject the sent message (e.g. if there is no authority to send). + +For MCData types other than SDS using signalling control plane, the MCData service invokes a transmission request grant approach before data is permitted to be transmitted. The MCData service provides configurable limits for the maximum amount of data for and/or maximum amount of time that an MCData user can transmit in a single request, which may be configured by the MCData administrator. + +For congestion control, related to transmission requests, the MCData service may perform the following: + +- reject the data transmission requests and then shall notify the MCData user of the rejection; +- queue the data transmission requests; or +- at any time, withhold the permission to transmit data automatically. + +The MCData service shall notify the transmitting MCData group member if there are no other MCData group members affiliated to the MCData group. + +The MCData service supports the lossless communication, and it can be configured by the MCData administrator for the private communication and group communication. The lossless communication can be supported only if the user has a valid and active MCData message store account. If the lossless communication is configured for private communication and if the MCData communication cannot be delivered to the MCData user (e.g. if the recipient is not available at the time of data delivery or network congestion), it shall be made available to the MCData user by storing it in the MCData user's personal account in the MCData message store. If a MCData group is configured for lossless communication, all members of the selected MCData group shall receive the MCData communication, at a time dependent on affiliation status. An affiliated group member of this MCData group shall receive the MCData communication when they are sent. A group member that is not affiliated during MCData communication, the MCData communication shall be made available by storing it in the group member's personal account in the MCData message store. If a MCData group is not configured for lossless communication, only the affiliated members of the selected MCData group shall receive the MCData communication. + +In order to support lossless communication, below are the conditions that needs to be satisfied: + +- Lossless communication is provisioned +- MCData user has the valid MCData message store account +- Store communication into message store configuration parameter is enabled +- MCData user has requested to store the MCData communication into MCData message store + +## 5.2 Reception control + +The MCData service shall support the ability to receive small amounts of data automatically. The MCData service may store data waiting for delivery in a temporary store, and notify availability to the receiving MCData users, i.e. deferred delivery. The data which is temporarily stored may be configured with "time to live" value, and subsequently, the data may be purged from the temporary store upon expiry of "time to live". + +When a MCData user has an active MCData message store account and has activated lossless communication, the MCData service deferred delivery shall not be used when the user is offline. + +The recipient individual user (private communication) or affiliated members of the MCData group(s) shall be notified of the list of available data either on request or periodically. + +The MCData service shall provide a mechanism for the MCData user to select data to be downloaded from the list corresponding to the temporary store, subject to limitations such as expiry time and size. + +The MCData service shall support the ability to automatically deliver files with a size less than a configured threshold value (i.e. auto-receive). The data size for auto-receive shall be configured by the MCData administrator. + +## 5.3 Short Data Service capability + +The MCData service shall support SDS capability for one-to-one and group communications. + +The SDS capability shall support messages with a maximum payload of at least 1000 bytes. The supported message types shall include text, binary, or hyperlinks. Multiple message types may be interleaved within in a single message payload. The payload shall support inclusion of location information of the sending MCData user, with or without user or application provided data. + +The MCData service shall support messages to be sent over the signalling plane or the media plane. + +The SDS capability shall allow for multiple related messages to be correlated and sequenced within the MCData service. + +The MCData user shall be able to selectively request read and delivery receipt indication for the sent messages. The message delivery history information should be made available to an authorized MCData user. + +The MCData service may support aggregation of disposition notifications when SDS messages are sent to multiple recipients. + +## 5.4 File distribution capability + +The MCData service shall support distribution of files for one-to-one and group communications. + +The MCData service shall allow the MCData user to send a file or a URL of a file to another MCData user. The source of the file can originate either from an MCData client or from a network functional entity. The generated URL shall be a reference to a stored file to allow for subsequent retrieval. The file storage policy may determine the availability of the file to be retrieved, and is subject to expiry time and size limitations. + +When the file delivery request is set by the sending user to mandatory download, the MCData service shall proceed to deliver the file to the recipient when possible. The file distribution mechanisms shall support both unicast and broadcast delivery methods. + +The MCData service shall support aggregation of download completed reports when files are distributed to multiple recipients. + +The MCData service shall support mechanisms for detection and recovery of lost data. A receiving MCData client should be able to: + +- detect and report when a transfer did not complete properly and request retransmission; +- identify and re-request the missing parts of an incompletely received file; and +- accept partial retransmissions and use them to reconstitute the original file. + +When employing MBMS delivery: + +- MCData may use the MB2 interface specified in 3GPP TS 23.468 [8]. See also Group Communication Delivery Method in 3GPP TS 26.346 [21]; or +- if MBMS user services and Download Delivery Method (see 3GPP TS 26.346 [21]) are utilized, MCData shall use the xMB interface specified in 3GPP TS 26.348 [19]. + +For the MBMS path, figure 5.4-1 shows both the MB2 and the xMB interfaces. + +![Figure 5.4-1: MCData on-network architecture diagram showing the flow of data from an MCData client in a UE through an E-UTRAN to an MCData server. The diagram illustrates two main delivery paths: a unicast path (highlighted in yellow) and an MBMS path (highlighted in green). The unicast path consists of the Rx, SGi, and MB2-C interfaces. The MBMS path consists of the MB2-U, xMB-C, and xMB-U interfaces. The UE contains an MCData client and connects to the E-UTRAN via the Uu interface. The E-UTRAN connects to the MCData server via the GC1 interface. The MCData server is shown acting as a GCS AS and/or a content provider.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 5.4-1: MCData on-network architecture diagram showing the flow of data from an MCData client in a UE through an E-UTRAN to an MCData server. The diagram illustrates two main delivery paths: a unicast path (highlighted in yellow) and an MBMS path (highlighted in green). The unicast path consists of the Rx, SGi, and MB2-C interfaces. The MBMS path consists of the MB2-U, xMB-C, and xMB-U interfaces. The UE contains an MCData client and connects to the E-UTRAN via the Uu interface. The E-UTRAN connects to the MCData server via the GC1 interface. The MCData server is shown acting as a GCS AS and/or a content provider. + +**Figure 5.4-1 MCData on-network architecture showing the unicast and MBMS delivery paths** + +## 5.5 Data streaming capability + +The MCData service may support data streaming capability for one-to-one and group communications. + +The MCData service may allow the MCData user to send a data stream or a URL of a data stream to another MCData user. The source of the data stream can originate either from an MCData client or from a network functional entity. For a data stream originating at a network functional entity, the data stream may be provided by an MCData user. The data streaming mechanisms shall support both unicast and broadcast delivery methods. + +When the data streaming request is set to automatic reception, the MCData service may not require consent from the receiving MCData user. + +The MCData user may be able to apply controls (i.e. start, stop, cancel) to the streams, and on a per recipient basis. + +The stream may be terminated through an explicit user control (i.e. stop, cancel operation) or by reaching the end of the streamed content. + +## 5.6 MCData group affiliation and MCData group de-affiliation + +MCData groups may be configured with one or more MCData sub-services (e.g. SDS, FD, DS) as specified within the MCData service. When an MCData user affiliates to an MCData group, the MCData user is affiliated to each of those MCData sub-services configured in the MCData group. The list of MCData sub-services configured for an MCData group shall be included in the MCData group configuration data. + +MCData group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [5]. In addition, the following requirements shall be fulfilled by the MCData service for MCData users affiliated to MCData groups: + +- MCData users receive notifications for participating in MCData sub-services and invitations for their affiliated MCData group(s). +- MCData users select an affiliated MCData group to initiate a new message, file distribution, data stream, etc. +- MCData users receive messages, files, data streams, enhanced status updates, etc, from their affiliated MCData group(s). + +## 5.7 Conversation management + +The conversation management: + +1. shall include a service indication for conversation management in each SDS and FD transaction. +2. may be comprised of SDS transactions or FD transactions or a combination of both. +3. shall include a conversation identifier in each SDS and FD transaction. +4. shall treat conversation between different set of users (either in one-to-one or group) as a separate conversation. +5. shall treat conversation between the same set of users (either in one-to-one or group), but with a different conversation identifier as a separate conversation. + +## 5.8 Bearer management + +### 5.8.1 General + +The MCData UE shall use the APNs as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5]. The MCData UE shall use the MC services APN as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5] for the SIP-1 reference point. + +### 5.8.2 EPS bearer considerations + +The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [5] shall apply. + +### 5.8.3 EPS unicast bearer considerations for MCData + +For an MCData session request, resources shall be requested utilising interaction with dynamic PCC. The MCData system shall request resources over Rx to a PCRF. The dedicated bearer for MCData media shall utilise the QCI value of 70 (as specified in 3GPP TS 23.203 [14]). The request of resources over Rx shall include an application identifier for MCData in order for the PCRF to evaluate the correct QCI. + +The UE is required to support at minimum one bearer, which is used for MCData (see annex A in 3GPP TS 36.331 [15]). + +Depending on operator policy, for media plane: + +- the MCData system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer; or +- the allocation of EPS bearers of desired priority for MCData communications may cause the pre-emption of lower priority pre-emptible EPS bearers (for MCData or for other applications), if the maximum number of bearers or maximum traffic capacity has been reached, in favour of the newly initiated MCData EPS bearer. In this case, if the new EPS bearer to be used for MCData communication has higher priority level (ARP) than other bearer(s), is allocated with a capability to pre-empt other bearers and the other bearer(s) are pre-emptible, then the EPS bearer for MCData communication pre-empts one (or more) of the existing EPS bearer(s). + +NOTE: Operator policy takes into account regional/national requirements. + +The EPS bearer(s) for MCData emergency communications shall have highest priority level among MCData communication types. The EPS bearer(s) for MCData imminent peril communications shall have higher priority level than for normal MCData communications but lower than the priority level for MCData emergency communications. + +### 5.8.4 MBMS bearer management + +The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [5]. + +## 5.9 Disposition + +Disposition requests and notifications can be sent "in-band" using the same mechanism used for transport of the data, or can be sent "out-of-band" when the mechanism used for transport of the data is no longer available. + +For standalone SDS and FD, the MCData UE shall use the signalling plane for disposition request and disposition notifications. For session SDS, the MCData UE shall use: + +- the media plane for disposition request and disposition notifications; and +- the signalling plane for disposition notifications when the media plane is no longer available. + +## 5.10 MCData message store + +MCData message store is used by MCData users to store their MCData communications permanently; it shall provide secured storage area for each authorized MCData user having a user account. The storage area is identified by the MCData user's MCData ID. The MCData message store shall allow an MCData user to access only the storage area that he is authorized to access. A user (i.e. a dispatcher) other than the user account holder shall be able to access the account holder's storage area if authorized. + +During an active MCData communication, the participating function on the MCData server of a MCData user participant shall, if the configuration to store the MCData communication is enabled for and if requested by the MCData user, deposit messages and files exchanged in the conversation to the MCData user's storage area in the MCData message store. When depositing the MCData communication into the MCData message store, if no such MCData user account is available on the MCData message store the MCData server shall create the user's account first and then deposit the MCData communications. The MCData message store shall support user account creation and deposit MCData communications operations from the MCData server after successful authentication and authorization. The MCData message store shall support the message store client to retrieve, update, delete, search and synchronize MCData communications stored in the MCData message store, after successful authentication and authorization. + +The MCData user shall have an option if he wants to store the MCData communications in the MCData message store or not. Based on the request from MCData user, messages and files exchanged in an active MCData communication shall be stored as objects in the MCData message store. A stored object shall contain the following information: + +1. The message or file itself; and +2. Associated metadata, consisting of: + +- a. information retrieved from the information elements of the message or file, such as MCData IDs, Conversation identifier etc.; and +- b. other information, such as content type (message or file), status ("seen", "received by", "read by ", "downloaded by " etc). + +If a file is distributed indirectly with a URL in a message, when this message is stored in the MCData user's account in the MCData message store, it could be stored as: + +1. an object as the original message with the URL; or +2. an object as the message with a revised URL that the URL indicates where the file, retrieved from the MCData content server, is stored separately in the MCData user's storage account. With proper security and authorization, this URL can be accessible by other network entities such as the MCData content server. + +NOTE: It is the decision of SA3 on the mechanism to store an encrypted message or file in the MCData message store. + +When a MCData user logs onto a UE with successful authentication and authorization and obtains the user service profile, the message store client on the UE shall synchronize with the user's account on the MCData message store, either automatically or manually (i.e. interacts with the user on which option to synchronize or no synchronization at all), before any MCData service starts. + +## 5.11 IP connectivity (IPcon) capability + +IP connectivity service enables the exchange of IP Data using MCData transport service and provides the transport of IP Data for e.g. data hosts, servers, etc. that do not have mission critical communication capabilities. The exchange of IP Data is not limited in a transaction. + +![Figure 5.11-1: IP connectivity model diagram. The diagram shows a 'Data host' on the left and a 'Server' on the right, both connected to a central '3GPP system'. The 'Data host' connects to an 'IP connectivity MCData client' which is part of an 'MC service UE'. The 'Server' connects to another 'IP connectivity MCData client' which is also part of an 'MC service UE'. Both 'MC service UE' blocks are connected to the '3GPP system', which contains the 'MCData transport service'. A dashed line labeled 'IP connectivity' runs horizontally across the top, connecting the 'Data host' and 'Server' via the 'IP connectivity MCData client' blocks. The 'Data host' and 'Server' are labeled with 'IP_Data' at their connection points to the 'IP connectivity' line.](17b9d89b91e10c3efc38193baedee268_img.jpg) + +Figure 5.11-1: IP connectivity model diagram. The diagram shows a 'Data host' on the left and a 'Server' on the right, both connected to a central '3GPP system'. The 'Data host' connects to an 'IP connectivity MCData client' which is part of an 'MC service UE'. The 'Server' connects to another 'IP connectivity MCData client' which is also part of an 'MC service UE'. Both 'MC service UE' blocks are connected to the '3GPP system', which contains the 'MCData transport service'. A dashed line labeled 'IP connectivity' runs horizontally across the top, connecting the 'Data host' and 'Server' via the 'IP connectivity MCData client' blocks. The 'Data host' and 'Server' are labeled with 'IP\_Data' at their connection points to the 'IP connectivity' line. + +Figure 5.11-1: IP connectivity model + +The corresponding MCData client enables bidirectional IP Data communication with the support of the IP connectivity service and thus forms the gateway to data hosts or servers. Therefore, the IP connectivity MCData client requests the MCData transport service with the associated QoS requirement and communication priority. + +An authorised MCData client supporting IP connectivity capabilities is able to bar incoming IP connectivity requests either on demand or by providing a list of excluded origins identified by the MCData ID and, if available, by the functional alias. + +For IP connectivity, the MCData server may support following limitation to exchange IP Data: + +- limit the total data volume between the authorized MCData clients, divided by transmission and reception; +- max time limit, e.g. total minutes or allow exchange between predefined start and end time. + +IP connectivity MCData service supports MCData transport services for one-to-one and group communication. + +The IP address allocation necessary for user-IP connectivity MCData transport service is independent to the IP address allocation of the individual data hosts attached with the MCData client supporting IP connectivity capabilities. The required IP address pools for the user-IP connectivity MCData service are managed by the IP connectivity MCData transport service. + +NOTE: IP connectivity service on interworking is not covered in the current specification. + +## 5.12 MBMS user service architecture requirements + +The MBMS user service architecture offers a set of delivery methods to applications, specified in 3GPP TS 26.346 [21]. The MBMS download delivery method is used for the delivery of files over MBMS and provides reliability control by means of forward-error-correction. + +The MCData File Distribution capability can use the MBMS download delivery method by including, in the MC service-on network architecture (subclause 5.2.6 from 3GPP TS 23.280 [5]), the MBMS user service architecture (3GPP TS 26.346 [21]), with the MCData server assuming the role of the content provider. + +The MCData server may determine the MBMS broadcast area based on the cell identities of the affiliated group members received over GC1. + +When the xMB interface is used, the MCData server uses the xMB mission critical extension, specified in 3GPP TS 26.348 [19] to control the QoS and the MBMS broadcast area of the MBMS user services. The MCData server also provides a file delivery manifest over xMB-C (see subclause 5.6.2 from 3GPP TS 26.348 [19]) describing the list of files to be broadcasted, and, for each file, the target completion date and the number of repetitions. + +The MBMS user service metadata, which provides the delivery and schedule parameters, are returned to the MCData server after the MBMS session creation or update, under the form of a SA file (annex L.3A from 3GPP TS 26.346 [21]). The MCData server signals this SA file, together with the service id and the uri of the file to be received to the targeted MCData clients. + +NOTE: Use of service announcement channel to deliver MBMS user service metadata is not covered in the current specification. + +## 5.13 MBMS delivery via MB2 interface + +MBMS delivery via MB2 applies to MCData services that use media plane for user traffic delivery. + +## 5.14 Delivery Notification + +A MCData user may request a delivery report (such as delivered, message read, or file downloaded etc.) when sending a MCData data (i.e. a message or a file). The recipient(s) shall respond with the proper delivery status response(s) (such as delivered, message read, or file downloaded etc.) according to what is requested in the delivery report. The sender of the MCData data may include multiple delivery status (such as delivered, message read, or file downloaded etc.) in the delivery report and the recipient(s) shall respond accordingly. + +When the recipient is offline and receives a MCData data with request for delivery report, the delivery status response(s) shall follow one of the two principles below: + +1. If the deferred delivery is used to deliver the MCData data, the delivery status response(s) shall be determined and responded by the recipient when the data is delivered. The MCData server may send a provisional delivery status report (such as the recipient is offline and the data will be delivered when the recipient is online or discarded due to timeout etc.) to inform the sender about the data delivery progress. +2. If the data is delivered with lossless communication, the MCData server shall respond with a delivered status report to the sender once the data is deposited into the recipient's MCData message store account. If the message read or file downloaded status is requested, the recipient shall respond it when the data is synced on the user device and processed by the recipient. + +# --- 5A Involved business relationships + +The description of the involved business relationships for the MCData service is contained in clause 6 of 3GPP TS 23.280 [5]. + +# --- 6 Functional model + +## 6.1 General + +This clause defines the functional model for MCData service. + +The security solution for the MCData service, including end-to-end encryption, is specified in 3GPP TS 33.180 [13]. + +## 6.2 Description of the planes + +The functional model for the support of MCData is defined as a series of planes to allow for the breakdown of the architectural description. + +The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [5]. + +## 6.3 Transmission and reception control aspects + +### 6.3.1 General + +The transmission and reception control are functions of the MCData server. + +For small data transmissions there is no need for prior grant of request to transmit. The procedures in the present document describe when data is automatically sent. + +For large data transmissions, i.e. large files, the data is transmitted only after request to transmit is granted. The data to be transmitted and/or received may be stored in a data repository associated with the transmission and reception control functions. + +NOTE: An overview of transmission control process and possible arbitration mechanisms is provided in the Annex B. + +## 6.4 Generic functional model + +### 6.4.1 On-network functional model + +Figure 6.4.1-1 shows the generic application plane functional model. + +![Figure 6.4.1-1: Generic application plane functional model. This block diagram illustrates the functional architecture of the MCData application plane. On the left, external entities include 'Other MCData server', 'MCData user database', 'Interworking function to LMR system', and two 'MC gateway server' units. These connect to a central 'MCData server' via reference points MCDATA-3, MCDATA-2, IWF-2, and MCDATA-3 respectively. The 'MCData server' contains 'Capability functions (SDS, FD, DS, IPcon)'. It connects to an 'MCData UE' (containing 'MCData client', 'Capability functions (SDS, FD, DS, IPcon)', 'Message store client', and 'Message notification client') via reference points MCDATA-cap-1, MCDATA-cap-n, MCDATA-5 (Rx), and MCDATA-6 (MB2C). The 'MCData server' also connects to an 'MCData message store' via MCDATA-8. The 'MCData message store' connects to the 'Message store client' via MCDATA-7 and to an 'MCData notification server' via MCDATA-11. The 'MCData notification server' connects to the 'Message notification client' via MCDATA-10. A vertical line labeled 'EPS' separates the network-side components from the UE-side components. The second 'MC gateway server' connects to the first via MCDATA-9.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +Figure 6.4.1-1: Generic application plane functional model. This block diagram illustrates the functional architecture of the MCData application plane. On the left, external entities include 'Other MCData server', 'MCData user database', 'Interworking function to LMR system', and two 'MC gateway server' units. These connect to a central 'MCData server' via reference points MCDATA-3, MCDATA-2, IWF-2, and MCDATA-3 respectively. The 'MCData server' contains 'Capability functions (SDS, FD, DS, IPcon)'. It connects to an 'MCData UE' (containing 'MCData client', 'Capability functions (SDS, FD, DS, IPcon)', 'Message store client', and 'Message notification client') via reference points MCDATA-cap-1, MCDATA-cap-n, MCDATA-5 (Rx), and MCDATA-6 (MB2C). The 'MCData server' also connects to an 'MCData message store' via MCDATA-8. The 'MCData message store' connects to the 'Message store client' via MCDATA-7 and to an 'MCData notification server' via MCDATA-11. The 'MCData notification server' connects to the 'Message notification client' via MCDATA-10. A vertical line labeled 'EPS' separates the network-side components from the UE-side components. The second 'MC gateway server' connects to the first via MCDATA-9. + +**Figure 6.4.1-1: Generic application plane functional model** + +In the model shown in figure 6.4.1-1, capability functions (SDS, FD, DS, IPcon) of the MCData client and the MCData server along with their reference points (MCDATA-cap-1 to MCDATA-cap-n) are described in the respective functional models for each capability. + +NOTE 1: The security aspects of new network components (MCData message store, Message store client and MCData notification server) and the associated new reference points are the responsibility of SA3 and thus outside the scope of the present document. + +An MCData server controls the signaling reference points and the corresponding media allowing different paths for media and signalling. The MCData server determines if it needs to stay in the media path based on the feature(s) involved in the MCData communication, e.g., if the MCData message store is required in the MCData communication, the MCData server shall remain in the media path. + +NOTE 2: If the MCData server is not in the MCData communication media path, any implications regarding MC user data logging are left to implementation. + +### 6.4.2 Off-network functional model + +### 6.4.3 Functional entities description + +**Editor's note:** Combining functional models describing each capability into one functional model is FFS. + +#### 6.4.3.1 Application plane + +##### 6.4.3.1.1 MCData client + +The MCData client functional entity acts as the user agent for all MCData application transactions. The client supports SDS, file distribution, data streaming and IP connectivity MCData capabilities utilized by MCData services like conversation management, robots control, enhanced status, database enquiries and secured internet. + +##### 6.4.3.1.2 MCData server + +The MCData server functional entity provides centralised support for MCData services suite. Conversation management, robots, enhanced status, database enquiries and secured internet MCData services requiring one-to-one or group data communication are realized using SDS, file distribution, data streaming and IP connectivity MCData communication capabilities. + +All the MCData clients supporting users belonging to a single group are required to use the same MCData server for that group. An MCData client supporting a user involved in multiple groups can have relationships with multiple MCData servers. + +For MBMS delivery, the MCData server functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [8] to control multicast and unicast operations for group communications. + +If the MBMS user service architecture is utilized, the MCData server functional entity represents a specific instantiation of the content provider as described in 3GPP TS 26.346 [21] to control multicast operations for file distribution. + +The MCData server functional entity is supported by the SIP AS functional entity of the signalling control plane. + +The MCData server shall support the controlling role and the participating role. The MCData server may perform the controlling role for one-to-one and group data communication. The MCData server performing the controlling role for a one-to-one or group data communication may also perform a participating role for the same one-to-one or group data communication. For each one-to-one and group data communication, there shall be only one MCData server assuming the controlling role, while one or more MCData servers in participating role may be involved. + +The MCData server performing the controlling role is responsible for: + +- handling transmission and reception control (e.g. policy enforcement for participation in the MCData group communication) towards all the MCData users of the one-to-one and group data communication; +- interfacing with the group management server for group policy and affiliation status information of this MCData server's served affiliated users; +- managing SDS and FD data distribution during MCData group communication; and +- managing the MCData transport service for IP connectivity. + +The MCData server performing the participating role is responsible for: + +- handling transmission control (e.g. authorization for participation in the MCData group communication) to MCData users of the one-to-one and group data communication; +- group affiliation support for MCData user, including enforcement of maximum Nc2 number of simultaneous group affiliations by a user; +- interfacing with the group management server for group policy and affiliation status information of this MCData server's served affiliated users; +- relaying the MCData communication messages between the MCData client and the MCData server performing the controlling role; and +- handling reception control (e.g. temporarily storing the data to present to the MCData user as required) to its MCData users of the one-to-one and group data communication. + +NOTE: The MCData server in the controlling role and the MCData server in the participating role can belong to the same MCData system. + +##### 6.4.3.1.3 MCData user database + +This functional entity contains information of the MCData user profile associated with an MCData ID that is held by the MCData service provider at the application plane. The MCData user profile is determined by the mission critical organization, the MCData service provider, and potentially the MCData user. + +##### 6.4.3.1.4 Interworking function to LMR system + +The functional entity is specified in 3GPP TS 23.283 [18]. + +##### 6.4.3.1.5 MC gateway server + +The MC gateway server provides support for MCData interconnection services with a partner MCData system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCData servers in the partner MCData system without needing to expose the MCData servers in the primary MCData system outside the + +trusted domain of the primary MCData system. It may be a role of the MCData server described in subclause 6.4.3.1.2 of the present document. + +The MC gateway server is responsible for relaying call control and transmission control signalling messages, and media between MCData servers within the MCData system and the interconnected MCData system. + +#### 6.4.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +#### 6.4.3.3 MCData message store + +The MCData message store is a network base persistent store that allows Mission Critical Organization to configure their MCData users to permanently store their MCData communications. Once configured a MCData user will be allocated a secured storage area (i.e. size) in the MCData message store that is only accessible by that configured MCData user and any authorized users. The MCData user can manage how and what will be stored in his personal message store with the support of management operations such as creating, deleting and merging folders, moving stored messages and files around and synchronization all used devices to provide the same context view etc. + +NOTE: The security aspects of access and management (such as read/write/update/sync etc.) of personal message store are the responsibility of SA3 and thus outside the scope of the present document. + +#### 6.4.3.4 Message store client + +The Message store client is used to support MCData client to manage the MCData communication history stored in MCData message store for a particular MCData user. It supports the secure access to a MCData user's configured MCData message store area and operations relevant to the stored communication history such as folders management and synchronization to the device local message store. + +#### 6.4.3.5 MCData notification server + +The MCData notification server provides the centralized notification function in the network. The MCData notification server allows an application (e.g. resident in the UE) to create a communication channel to receive real-time notifications from the network in either Pull or Push mode. Depending on the channel type created, the MCData notification server provides the application a callback endpoint (i.e. URL) and may also provide a channel endpoint (i.e. URL). The application communicates the callback endpoint information to the application server (i.e. network enabler) for it to use in sending to the MCData notification server the events for delivery to the application. Depending on the type of channel created by the application the delivery of the notifications from the MCData notification server to the application may be via a Pull or Push method. If Pull method is used, then the application shall use the provided channel endpoint to pull the notifications from the MCData notification server. However, if a Push notification delivery is used, then the MCData notification server asynchronously delivers the events received from the application server to the application through a PUSH Enabler server. The MCData notification server provides a consistent way to deliver notifications by all services to reduce the complexity of service logic on the application server. + +It depends on deployment, if multiple MCData notification servers are deployed. + +#### 6.4.3.6 Message notification client + +The Message notification client is used to request the notification service from the MCData notification server. Once the notification service request is authorized by the MCData notification server, the Message notification client will communicate the callback endpoint, received from the MCData notification server, to the MCData message store to be used for notification message delivery. + +When multiple MCData notification servers are deployed, the Message notification client shall select one for notification service at any given time. How the Message notification client selects the appropriate MCData notification server from multiple available MCData notification servers for service is implementation specific. + +### 6.4.4 Reference points + +#### 6.4.4.1 Application plane + +##### 6.4.4.1.1 General + +The reference points for the application plane of MCData service are described in the following subclauses. + +##### 6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database) + +The MCData-2 reference point, which exists between the MCData server and the MCData user database, is used by the MCData server to obtain information about a specific user. The MCData-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [12] and shall be intra-network. + +##### 6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server) + +The MCData-3 reference point, which exists between the MCData server and the MCData server for MCData application signalling for establishing MCData sessions, shall use the SIP-2 reference point for transport and routing of signalling. If each MCData server is served by a different SIP core then the MCData-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Media is also transferred using the MCData-3 reference point. + +##### 6.4.4.1.3A Reference point MCData-5 (between the MCData server and the EPS) + +The MCData-5 reference point, which exists between the MCData server and the EPS, is used, subject to the conditions below, by the MCData server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [14]. + +MCData-5 is not used when the MCData service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCData service provider domain. + +MCData-5 may be used when the MCData service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCData service provider domain. + +NOTE: Any coordination between the P-CSCF use of Rx and the MCData server use of Rx (via MCData-5) from the MCData service provider domain is not specified in this release of this specification. + +##### 6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS) + +The MCData-6 reference point, which exists between the MCData server and the EPS, is used to request the allocation and activation of multicast transport resources for MCData application usage. The MCData-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [16]. The MCData-6 reference point also uses the xMB-C interface as defined in 3GPP TS 29.116 [20] for file distribution. + +##### 6.4.4.1.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server) + +The IWF-2 reference point is specified in 3GPP TS 23.283 [18]. + +##### 6.4.4.1.6 Reference point MCData-7 (between the Message store client and MCData message store) + +The MCData-7 reference point, which exists between the Message store client and the MCData message store, is used by the Message store client to manage the information stored in the MCData message store, to subscribe to changes in the MCData message store and to synchronize between the MCData client and the MCData message store. + +##### 6.4.4.1.7 Reference point MCData-8 (between the MCData message store and MCData server) + +The MCData-8 reference point, which exists between the MCData server and the MCData message store, is used by the MCData server to access and manage the MCData message store such as creating MCData user folders and depositing the communications history. + +##### 6.4.4.1.8 Reference point MCData-9 (between the MC gateway server and the MC gateway server in a different MCData system) + +The MCData-9 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCData system for MCData application signalling for establishing MCData sessions, shall use the SIP-3 reference point for transport and routing of signalling. The MCData-9 reference point also carries application data where the data size is too great to be transferred on the signalling plane. + +##### 6.4.4.1.9 Reference point MCData-10 (between the Message notification client and MCData notification server) + +The MCData-10 reference point, which exists between the Message notification client and the MCData notification server, is used by the Message notification client to create an appropriate notification channel(s) at the MCData notification server in order to direct events from MCData message store to the MCData notification server for subsequent delivery to the Message notification client on the UE. + +##### 6.4.4.1.10 Reference point MCData-11 (between the MCData message store and the MCData notification server) + +The MCData-11 reference point, which exists between the MCData message store and the MCData notification server, is used by the MCData message store to send notification message to the subscribed Message notification client. + +## 6.5 Functional model for short data service + +### 6.5.1 On-network functional model + +Figure 6.5.1-1 shows the application plane functional model for SDS. + +![Figure 6.5.1-1: Application plane functional model for SDS. The diagram shows the functional model for Short Data Service (SDS) across the MCData server, MCData UE, and EPS. The MCData server contains an SDS distribution function and a Transmission/Reception control. The MCData UE contains an MCData client with an SDS function and a Message store client. The MCData Message Store is shown between the server and the UE. Reference points MCData-SDS-1, MCData-SDS-2, and MCData-SDS-3 connect the SDS distribution function to the SDS function. Reference point MCData-8 connects the MCData server to the MCData Message Store. Reference point MCData-7 connects the MCData Message Store to the Message store client. The EPS is shown as a vertical bar between the server and the UE.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg) + +Figure 6.5.1-1: Application plane functional model for SDS. The diagram shows the functional model for Short Data Service (SDS) across the MCData server, MCData UE, and EPS. The MCData server contains an SDS distribution function and a Transmission/Reception control. The MCData UE contains an MCData client with an SDS function and a Message store client. The MCData Message Store is shown between the server and the UE. Reference points MCData-SDS-1, MCData-SDS-2, and MCData-SDS-3 connect the SDS distribution function to the SDS function. Reference point MCData-8 connects the MCData server to the MCData Message Store. Reference point MCData-7 connects the MCData Message Store to the Message store client. The EPS is shown as a vertical bar between the server and the UE. + +**Figure 6.5.1-1: Application plane functional model for SDS** + +In the model shown in figure 6.5.1-1, the following apply: + +- MCData-SDS-1 reference point is primarily used for MCData application signalling during session establishment in support of SDS data transfer. Secondarily, MCData-SDS-1 reference point is used for uplink + +and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. + +- MCData-SDS-2 reference point carries uplink and downlink unicast SDS data over media plane between the SDS distribution function of the MCData server and the SDS function of the MCData client. +- MCData-SDS-3 reference point carries downlink multicast SDS data over media plane from the SDS distribution function of the MCData server to the SDS function of the MCData client. + +Examples of SDS data (in the form of text, binary, application data, URL or combinations of these) are: + +- information pertaining to applications e.g. health parameters of MCData user for situational awareness application; +- information pertaining to enhanced status service; +- text or URL data between MCData users; +- application data (e.g. health parameters) to the MCData user; +- location information (independent or along with user or application provided data); +- command instructions to invoke certain operations on the MCData UE e.g. invoking UE specific applications; and +- application plane identities for the MCData user and MCData application. + +### 6.5.2 Off-network functional model + +Figure 6.5.2-1 shows the off-network application plane functional model for SDS. + +![Diagram of the off-network application plane functional model for SDS, showing two User Equipment (UE) units, UE 1 and UE 2, connected via Media and Signalling planes.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +The diagram illustrates the functional model for SDS between two User Equipment (UE) units, UE 1 and UE 2. Each UE is represented by a vertical stack of functional blocks. At the top of each stack is a box containing 'SDS function' and 'MCData client'. Below this is a dashed box containing 'Configuration management client', 'Group management client', and 'Common services core', with the label 'Application plane' at the bottom. At the bottom of each stack is a box containing 'Signalling user agent' and 'Signalling control plane'. A green horizontal line labeled 'Media' connects the 'SDS function' blocks of UE 1 and UE 2. A red horizontal line labeled 'Signalling' connects the 'Signalling control plane' blocks of UE 1 and UE 2. + +Diagram of the off-network application plane functional model for SDS, showing two User Equipment (UE) units, UE 1 and UE 2, connected via Media and Signalling planes. + +**Figure 6.5.2-1: Application plane functional model for SDS** + +### 6.5.3 Functional entities description + +#### 6.5.3.1 Application plane + +##### 6.5.3.1.1 SDS function + +SDS function of the MCData client is responsible to handle SDS capability related requests and responses. + +##### 6.5.3.1.2 SDS distribution function + +The SDS distribution function of the MCData server is responsible for the SDS data transaction to MCData communication participants. The SDS distribution function of the MCData server provides the following functionality: + +- reception of uplink SDS data transaction by means of the MCData-SDS-1 and MCData-SDS-2 reference points; +- replicate the SDS data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-SDS-1 and MCData-SDS-2 reference points; and +- distribute downlink SDS data using multicast downlink transport by means of the MCData-SDS-3 reference point. + +##### 6.5.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of MCData SDS data transaction between the sending MCData UE, the MCData server, and the receiving MCData UE. For SDS capability, due to small data size, the SDS messages can be automatically sent. + +#### 6.5.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.5.4 Reference points + +#### 6.5.4.1 Application plane + +##### 6.5.4.1.1 Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function) + +MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. This reference point is also used for MCData application signalling during session establishment in support of SDS data transfer. + +The MCData-SDS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-SDS-1 reference point can be used when the SDS payload data size does not exceed the configured maximum payload data size for SDS over signalling control plane, otherwise MCData-SDS-2 and MCData-SDS-3 may be used appropriately. + +Reference point MCData-SDS-1 also provides support to delivered and read requests and notifications as appropriate. + +##### 6.5.4.1.2 Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function) + +The MCData-SDS-2 reference point, which exists between the SDS distribution function and the SDS function of the MCData client, is used unicast SDS data transaction (when the SDS payload data size exceeds the configured maximum payload data size for SDS over signalling control plane) between the MCData server and the MCData client. The MCData-SDS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +Reference point MCData-SDS-2 also provides support to message thread indication using conversation identifier, delivered and read notifications as appropriate. + +##### 6.5.4.1.3 Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function) + +The MCData-SDS-3 reference point, which exists between the SDS distribution function of the MCData server and the SDS function of the MCData client, is used by the SDS distribution function of the MCData server to send downlink + +multicast SDS data to the SDS function of the MCData client. The MCData-SDS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +#### 6.5.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.6 Functional model for file distribution + +### 6.6.1 On-network functional model + +Figure 6.6.1-1 shows the application plane functional model for file distribution. + +![Figure 6.6.1-1: Application plane functional model for file distribution. The diagram shows the functional architecture for file distribution between an MCData server and an MCData UE, mediated by an EPS. The MCData server contains an FD function, a Transmission/Reception control, and an MCData content server (which includes a Media Storage function). The MCData UE contains an MCData client with an FD function, a Media Storage client, and a Message store client. Reference points are defined as follows: MCData-FD-1 (dashed line) between the FD functions; MCData-FD-2 (solid line) between the FD functions for unicast data; MCData-FD-3 (solid line) from the server's FD function to the UE's FD function for multicast data; MCData-FD-4 (solid line) between the Media Storage function and the Media Storage client; MCData-FD-5 (solid line) from the server's FD function to the MCData content server; MCData-8 (solid line) between the Transmission/Reception control and the MCData Message store; and MCData-7 (solid line) between the MCData Message store and the Message store client.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +Figure 6.6.1-1: Application plane functional model for file distribution. The diagram shows the functional architecture for file distribution between an MCData server and an MCData UE, mediated by an EPS. The MCData server contains an FD function, a Transmission/Reception control, and an MCData content server (which includes a Media Storage function). The MCData UE contains an MCData client with an FD function, a Media Storage client, and a Message store client. Reference points are defined as follows: MCData-FD-1 (dashed line) between the FD functions; MCData-FD-2 (solid line) between the FD functions for unicast data; MCData-FD-3 (solid line) from the server's FD function to the UE's FD function for multicast data; MCData-FD-4 (solid line) between the Media Storage function and the Media Storage client; MCData-FD-5 (solid line) from the server's FD function to the MCData content server; MCData-8 (solid line) between the Transmission/Reception control and the MCData Message store; and MCData-7 (solid line) between the MCData Message store and the Message store client. + +**Figure 6.6.1-1: Application plane functional model for file distribution** + +In the model shown in figure 6.6.1-1, the following apply: + +- MCData-FD-1 reference point is primarily used for MCData application signalling for establishing a session in support of MCData file distribution. Secondly, MCData-FD-1 reference point is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). +- MCData-FD-2 reference point carries uplink and downlink unicast file data between the FD functions of the MCData server and the MCData UE. +- MCData-FD-3 reference point carries downlink multicast file data from the FD function of the MCData server to the FD function of the MCData UE. +- MCData-FD-4 reference point carries uplink and downlink unicast file data between the media storage function of the MCData Content server and the media storage client of the MCData UE. +- MCData-FD-5 reference point supports the MCData server to access the stored files in the MCData content server for certain file distribution functions, such as retrieval a file to be distributed through multicast etc. This reference points also supports any necessary operational requirements. + +- MCData-FD-7 reference point supports the upload and download of file data between MCData content server and MCData message store. + +NOTE: The security aspects of MCData-FD-5 and MCData-FD-7 reference points are the responsibility of SA3 and thus outside the scope of the present document. + +### 6.6.1a On-network functional model for interconnection + +Figure 6.6.1a-1 shows the application plane functional model for file distribution with interconnection. + +![Figure 6.6.1a-1: Application plane functional model for file distribution. This diagram illustrates the functional architecture for file distribution across two MCData systems: a Partner MCData system and a Primary MCData system, connected via an EPS. The Partner MCData system contains an MCData content server (with a Media Storage function) and an MCData server (with FD and Transmission/reception control functions). The Primary MCData system contains an MCData server (with FD, Transmission/reception control, and MCData-8 functions), an MC gateway server, and an HTTP proxy. The MCData UE contains an MCData client (with FD, Media Storage, and Message store functions). Reference points are defined as follows: MCData-FD-1, 2, 3 between the Primary MCData server's FD function and the UE's FD function; MCData-FD-4 between the UE's Media Storage client and the Primary MCData server's Media Storage function; MCData-FD-5 between the MCData content server and the MCData server's FD function; MCData-FD-6 between the MCData content server and the HTTP proxy; MCData-FD-7 between the MCData message store and the UE's Message store client; MCData-3 between the MCData server and the MC gateway server; MCData-9 between the MC gateway server and the Primary MCData server; and MCData-8 between the MCData server and the MCData message store.](853f59c89931a666c07903b31d098277_img.jpg) + +Figure 6.6.1a-1: Application plane functional model for file distribution. This diagram illustrates the functional architecture for file distribution across two MCData systems: a Partner MCData system and a Primary MCData system, connected via an EPS. The Partner MCData system contains an MCData content server (with a Media Storage function) and an MCData server (with FD and Transmission/reception control functions). The Primary MCData system contains an MCData server (with FD, Transmission/reception control, and MCData-8 functions), an MC gateway server, and an HTTP proxy. The MCData UE contains an MCData client (with FD, Media Storage, and Message store functions). Reference points are defined as follows: MCData-FD-1, 2, 3 between the Primary MCData server's FD function and the UE's FD function; MCData-FD-4 between the UE's Media Storage client and the Primary MCData server's Media Storage function; MCData-FD-5 between the MCData content server and the MCData server's FD function; MCData-FD-6 between the MCData content server and the HTTP proxy; MCData-FD-7 between the MCData message store and the UE's Message store client; MCData-3 between the MCData server and the MC gateway server; MCData-9 between the MC gateway server and the Primary MCData server; and MCData-8 between the MCData server and the MCData message store. + +**Figure 6.6.1a-1: Application plane functional model for file distribution** + +In the model shown in figure 6.6.1a-1, the following apply: + +- MCData-FD-1, MCData-FD-2, MCData-FD-3, MCData-FD-4, MCData-FD-5 reference points are described in subclause 6.6.1. +- MCData-7 and MCData-8 reference points are described in subclause 6.4.4.1. +- The MC gateway server is described in subclause 6.4.3.1.5. +- MCData-3 and MCData-9 allow the MCData server in the primary MCData system to share URLs related to files for upload and download with the MCData server in the partner MCData system. +- MCData-FD-6 allows file contents and metadata to be shared between the MCData content server in the primary MCData system and the MCData content server in the partner MCData system. MCData-FD-6 is based on HTTP. +- The HTTP proxies are contained in the signalling plane. They provide topology and IP address hiding between MCData systems. + +### 6.6.2 Off-network functional model + +Figure 6.6.2-1 shows the off-network application plane functional model for FD. + +![Figure 6.6.2-1: Application plane functional model for FD. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines: a green line labeled 'Media' and a red line labeled 'Signalling'. Each UE block contains a stack of functional layers. At the top is the 'FD function' and 'MCData client'. Below this is a dashed box containing 'Configuration management client', 'Group management client', and 'Common services core'. This is followed by the 'Application plane'. At the bottom is the 'Signalling user agent' and 'Signalling control plane'.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 6.6.2-1: Application plane functional model for FD. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines: a green line labeled 'Media' and a red line labeled 'Signalling'. Each UE block contains a stack of functional layers. At the top is the 'FD function' and 'MCData client'. Below this is a dashed box containing 'Configuration management client', 'Group management client', and 'Common services core'. This is followed by the 'Application plane'. At the bottom is the 'Signalling user agent' and 'Signalling control plane'. + +**Figure 6.6.2-1: Application plane functional model for FD** + +### 6.6.3 Functional entities description + +#### 6.6.3.1 Application plane + +##### 6.6.3.1.1 FD function + +FD function of the MCData client and the MCData server is responsible to handle file distribution capability related requests and responses. + +The FD function of the MCData server is responsible for the distribution of file to the MCData communication participants. The FD function of the MCData server provides the following functionality: + +- reception of uplink file data by means of the MCData-FD-2 reference point; +- replicate the file data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink file data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-FD-2 reference point; and +- distribute downlink file data using multicast downlink transport by means of the MCData-FD-3 reference point. + +##### 6.6.3.1.2 Media storage client + +The media storage client is used to support FD function of the MCData client for file distribution capability. FD function of the MCData client interacts with media storage client for uploading and downloading file to or from the media storage function of the MCData content server. + +##### 6.6.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of MCData file data between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UE. However, when the file distribution requests are exceeding a certain size, it may be necessary to control the data that is transmitted or received by the MCData UEs. The control is subject to criteria like application level priorities (e.g. user priority, group priority), service type, emergency nature of the communication, etc. + +##### 6.6.3.1.4 Media storage function + +The media storage function is responsible for the storing of media uploaded by the media storage client of the MCData UE in case of MCData file distribution. It also supports download of stored media by the MCData UE in case of file distribution via media storage client. + +The media storage function supports partial download requests of stored media by the MCData UE via media storage client. + +##### 6.6.3.1.5 MCData content server + +The MCData content server functional entity provides a repository area in the MCData trust domain allowing authorized MCData users to temporarily store files that are intended to share to other MCData users. It provides common pool of storage area (i.e. size) to all authorized MCData users to use, no personal space is allocated. An authorized MCData user can use the supported operations on the defined reference point to upload shared files and download the files that are shared to him. The MCData server will use the defined reference point to access the files stored in the MCData content server and support the necessary operational functionalities. As part of the file life cycle management the temporarily stored files will be removed periodically based on the Mission Critical service provider policy. An MCData content server may share files with another MCData content server in another MCData system to support interconnection. + +If the MBMS user service architecture described in 3GPP TS 26.346 [21] is utilized for file distribution, the MCData content server provides the stored file associated to the established MBMS session. + +NOTE: The security aspects of the MCData content server and its operational supports are the responsibility of SA3 and thus outside the scope of the present document. + +#### 6.6.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.6.4 Reference points + +#### 6.6.4.1 Application plane + +##### 6.6.4.1.1 Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server) + +MCData-FD-1 reference point is used for MCData application signalling for establishing a session in support of MCData file distribution. The bearer is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). The MCData-FD-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-FD-1 reference point can be used as long as the file size does not exceed the capabilities (e.g. payload or transmission limits) provided by MCData-FD-1. + +Messages supported on this interface include the uplink and the downlink unicast file transaction between the MCData clients in MCData communication via the MCData server for: + +- metadata (file size, type etc.) of the file being distributed; +- URL of the file being distributed; +- sending download completed report; +- small size file; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +Messages supported on this interface may also include the MCData client providing the MCData server with + +- MCData application signalling for establishing a file distribution session in support of MCData communication. + +##### 6.6.4.1.2 Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server) + +The MCData-FD-2 reference point, which exists between the FD functions of the MCData client and the MCData server, is used for unicast file transaction between MCData server and MCData client. The MCData-FD-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +Reference point MCData-FD-2 supports the following functions: + +- file being distributed from and to the MCData client; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +##### 6.6.4.1.3 Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) + +The MCData-FD-3 reference point, which exists between the FD functions of the MCData client and the MCData server, is used by the FD function of the MCData server to send downlink multicast file data to the FD function of the MCData client. The MCData-FD-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8] or the xMB-U interface as defined in 3GPP TS 26.348 [19]. + +##### 6.6.4.1.4 Reference point MCData-FD-4 (media storage function and media storage client) + +The MCData-FD-4 reference point, which exists between the media storage function and the media storage client, is used by the media storage client of MCData UE to upload and download file to the media storage function of the MCData content server. The MCData-FD-4 reference point uses the HTTP reference point. + +##### 6.6.4.1.5 Reference point MCData-FD-5 (FD function and media storage function) + +The MCData-FD-5 reference point, which exists between FD function and the media storage function, is used by the FD function of MCData server to fetch the file in the MCData content server that was uploaded by the media storage client of a MCData UE for multicast delivery using MBMS. It also supports necessary operational functions such as size check for transmission control etc. The MCData-FD-5 reference point uses the HTTP reference point. + +##### 6.6.4.1.6 Reference point MCData-FD-7 (media storage function and MCData message store) + +The MCData-FD-7 reference point, which exists between media storage function and the MCData message store, is used by the media storage function to fetch the file residing in the MCData message store and store in its repository for distribution. It is also used by the MCData message store to download the file contents from the media storage function. + +#### 6.6.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.7 Functional model for data streaming + +### 6.7.1 On-network functional model + +NOTE: As no detailed procedures are specified in the current specification the DS functional model is for information only. + +Figure 6.7.1-1 shows the application plane functional model for data streaming. + +![Figure 6.7.1-1: Application plane functional model for data streaming. The diagram shows the interaction between an MCData server and an MCData UE, separated by an EPS. The MCData server contains a 'Data streaming and distribution function' and a 'Transmission/Reception control' block. The 'Data streaming and distribution function' is connected to the MCData UE via three reference points: MCData-DS-1, MCData-DS-2, and MCData-DS-3. The 'Transmission/Reception control' block is connected to an 'MCData Message store', which in turn is connected to the MCData UE via the MCData-7 reference point. The MCData UE contains an 'MCData client' with a 'DS function' and a 'Message store client'. The 'DS function' is connected to the MCData server via the MCData-DS-1, MCData-DS-2, and MCData-DS-3 reference points. The 'Message store client' is connected to the 'MCData Message store' via the MCData-7 reference point. The EPS is shown as a vertical line between the server and the UE.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 6.7.1-1: Application plane functional model for data streaming. The diagram shows the interaction between an MCData server and an MCData UE, separated by an EPS. The MCData server contains a 'Data streaming and distribution function' and a 'Transmission/Reception control' block. The 'Data streaming and distribution function' is connected to the MCData UE via three reference points: MCData-DS-1, MCData-DS-2, and MCData-DS-3. The 'Transmission/Reception control' block is connected to an 'MCData Message store', which in turn is connected to the MCData UE via the MCData-7 reference point. The MCData UE contains an 'MCData client' with a 'DS function' and a 'Message store client'. The 'DS function' is connected to the MCData server via the MCData-DS-1, MCData-DS-2, and MCData-DS-3 reference points. The 'Message store client' is connected to the 'MCData Message store' via the MCData-7 reference point. The EPS is shown as a vertical line between the server and the UE. + +**Figure 6.7.1-1: Application plane functional model for data streaming** + +In the model shown in figure 6.7.1-1, the following apply: + +- MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g. stream start and stop records). +- MCData-DS-2 reference point carries unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData UE. The bearer is used for both uplink and downlink unicast data streaming. +- MCData-DS-3 reference point carries multicast data stream from the data streaming and distribution function of the MCData server to the DS function of the MCData UE. The bearer is used for downlink multicast data streaming. + +### 6.7.2 Off-network functional model + +### 6.7.3 Functional entities description + +#### 6.7.3.1 Application plane + +##### 6.7.3.1.1 DS function + +DS function of the MCData client is responsible to handle DS capability related requests and responses for data streaming. FD function may interact with storage entity for retrieving the locally stored data for data streaming. + +##### 6.7.3.1.2 Data streaming and distribution function + +The data streaming and distribution function is responsible for the distribution of data stream to MCData communication participants. The data streaming and distribution function provides the following functionality: + +- reception of uplink data stream transmission by means of the MCData-DS-2 reference point; +- replicate the data stream as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data stream by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of MCData-DS-2 reference point; and +- distribute downlink data stream using multicast downlink transport by means of the MCData-DS-3 reference point. + +##### 6.7.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of data stream between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. + +#### 6.7.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.7.4 Reference points + +#### 6.7.4.1 Application plane + +##### 6.7.4.1.1 Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function) + +MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g., stream start and stop records). The MCData-DS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. + +Messages supported on this interface includes the uplink and the downlink unicast data stream between the MCData clients MCData communication via the MCData server for + +- metadata of the data being streamed; +- URL of the data being streamed; +- sending stream download report; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +Messages supported on this interface may also include the MCData client providing the MCData server with + +- MCData application signalling for establishing a UE data streaming session in support of MCData communication. + +##### 6.7.4.1.2 Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function) + +The MCData-DS-2 reference point, which exists between the data streaming and distribution function and the DS function, is used to unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData client. The MCData-DS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +MCData-DS-2 supports the following functions: + +- stream data from MCData UE; +- stream data from network; +- data stream controls from the authorized MCData UE; +- stream data stream controls from the MCData UE over uplink; +- start and stop data stream from MCData UE over downlink; +- conversation identifier for message thread indication; and + +- application plane identities for the MCData user and MCData application. + +##### 6.7.4.1.3 Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) + +The MCData-DS-3 reference point, which exists between the data streaming and distribution function and the DS function, is used by the data streaming and distribution function of the MCData server to send multicast data stream to the DS function of the MCData client. The MCData-DS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +#### 6.7.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.8 Functional model for IP connectivity + +### 6.8.1 On-network functional model + +Figure 6.8.1-1 shows the application plane functional model for User-IP connectivity. + +![Figure 6.8.1-1: Application plane functional model for IP connectivity. The diagram shows an MCData server on the left and an MCData UE on the right, separated by an EPS. The MCData server contains an IPcon distribution function and a Transmission/Reception control. The MCData UE contains an MCData client and an IPcon function. Three reference points are shown: MCData-IPcon-1 (signalling), MCData-IPcon-2 (bidirectional data), and MCData-IPcon-3 (unidirectional downlink data). An external IPcon-host is connected to the IPcon function in the UE.](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg) + +``` + +graph LR + subgraph MCData_server [MCData server] + IPcon_server[IPcon distribution function] + Transceiver[Transmission/Reception control] + IPcon_server --- Transceiver + end + subgraph EPS [EPS] + end + subgraph MCData_UE [MCData UE] + MCData_client[MCData client] + IPcon_UE[IPcon function] + IPcon_UE --- MCData_client + end + IPcon_server -- MCData-IPcon-1 --> IPcon_UE + IPcon_server -- MCData-IPcon-2 --> IPcon_UE + IPcon_server -- MCData-IPcon-3 --> IPcon_UE + IPcon_UE -- IPcon-host --> IPcon_host[IPcon-host] + +``` + +Figure 6.8.1-1: Application plane functional model for IP connectivity. The diagram shows an MCData server on the left and an MCData UE on the right, separated by an EPS. The MCData server contains an IPcon distribution function and a Transmission/Reception control. The MCData UE contains an MCData client and an IPcon function. Three reference points are shown: MCData-IPcon-1 (signalling), MCData-IPcon-2 (bidirectional data), and MCData-IPcon-3 (unidirectional downlink data). An external IPcon-host is connected to the IPcon function in the UE. + +**Figure 6.8.1-1: Application plane functional model for IP connectivity** + +In the model shown in figure 6.8.1-1, the following apply: + +- MCData-IPcon-1 reference point is used for MCData application signalling for establishing a session in support of MCData IP connectivity. +- MCData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCData IP connectivity over the media plane between the U-IPcon distribution function of the MCData server and the IPcon function of the MCData client(s). +- MCData-IPcon-3 reference point is used by the IP-con distribution function of the MCData server to send unidirectional downlink IP Data to the IP-con function of the MCData clients. +- IPcon-host reference point is used for a data host, e.g. server, to use IP connectivity service capabilities. This reference point is outside the scope of the present document. + +### 6.8.2 Off-network functional model + +### 6.8.3 Functional entities description + +#### 6.8.3.1 Application plane + +##### 6.8.3.1.1 IP connectivity function + +IP connectivity function of the MCData client is responsible to handle IPcon capability related requests and responses. + +##### 6.8.3.1.2 IPcon distribution function + +The IPcon distribution function of the MCData server is responsible for the distribution of IP Data to MCData communication participants. The IPcon distribution function of the MCData server provides the following functionality: + +- reception of uplink IP Data transmission by means of the MCData-IPcon-2 reference points; +- replicate the IP Data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-IPcon-2 reference points; and +- distribute downlink IP Data using multicast downlink transport by means of the MCData-IPcon-3 reference point. + +##### 6.8.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of IP Data transaction between the sending MCData client, the MCData server, and the receiving MCData client. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate IP Data are transmitted between the MCData clients. + +#### 6.8.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.8.4 Reference points + +#### 6.8.4.1 Application plane + +##### 6.8.4.1.1 Reference point MCData-IPcon-1 (between the IPcon distribution function and the U-IPcon function) + +MCData-IPcon-1 reference point is used for MCData application signalling for establishing a session in support of MCData IP connectivity. + +##### 6.8.4.1.2 Reference point MCData-IPcon-2 (unicast between the U-IPcon distribution function and the U-IPcon function) + +MCData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCData IP connectivity over the media plane between the IPcon distribution function of the MCData server and the IPcon function of the MCData client(s). + +##### 6.8.4.1.3 Reference point MCData-IPcon-3 (multicast between the IPcon distribution function and the IPcon function) + +MCData-IPcon-3 reference point carries downlink unidirectional IP Data over the media plane between the IPcon distribution function of the MCData server and the IPcon function of the MCData client(s). + +#### 6.8.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +# --- 6A Identities + +The MCData service specific identities (e.g. MCData ID, MCData group ID) are described in clause 8 of 3GPP TS 23.280 [5]. + +# --- 6B Application of functional model to deployments + +The application of the functional model to deployments, and description of various deployment scenarios for the MCData service, can be found in clause 9 of 3GPP TS 23.280 [5]. + +# --- 7 Procedures and information flows + +## 7.1 MCData service configuration + +The MCData service shall support the procedures and related information flows as specified in subclause 10.1 and Annex A of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service ID is the MCData ID; and +- The MC service user profile index is the MCData user profile index. + +## 7.2 Affiliation and de-affiliation to/from MCData group(s) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group is the MCData group; +- The MC service ID is the MCData ID; and +- The MC service group ID is the MCData group ID. + +When an MCData user has affiliated to an MCData group then the MCData user can send and receive MCData related media for that MCData group. When an MCData user has de affiliated from an MCData group then the MCData user cannot send and receive MCData related media to and from that MCData group. + +## 7.3 Use of MBMS transmission (on-network) + +### 7.3.1 Information flows for MBMS Transmission + +Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [5]. + +### 7.3.2 Use of pre-established MBMS bearers + +The MCData service shall support the procedure for using pre-established MBMS bearers as specified in 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-6, MCData-SDS-1, MCData-SDS-2, MCData-SDS-3, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +MCData may use pre-established MBMS bearer for the MCData features short data service, file distribution and data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel. + +Both the media packets as well as application level control signalling (e.g. transmission control) to the receiving users may be sent on the MBMS bearer. Optionally, a separate MBMS bearer could be used for the application level control signalling (e.g. transmission control), due to different bearer characteristic requirements. + +### 7.3.3 Use of dynamic MBMS bearer establishment + +The MCData service shall support the procedure for using dynamic MBMS bearers as specified 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-6, MCData-SDS-1, MCData-SDS-3, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +MCData may use dynamic MBMS bearer for the MCData features short data service, file distribution and data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel. + +Both the media packets as well as application level control signalling (e.g. transmission control) to the receiving users may be sent on the MBMS bearer. Optionally, a separate MBMS bearer could be used for the application level control signalling (e.g. transmission control), due to different bearer characteristic requirements. + +### 7.3.4 Switching from MBMS bearer to unicast bearer + +The MCData service shall support the procedure for switching from MBMS bearer to unicast bearer as specified 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-SDS-1, MCData-SDS-2, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +### 7.3.5 Use of MBMS user services for file distribution + +#### 7.3.5.1 General + +This subclause defines information flows and procedures for usage of MBMS user services that applies to MCData file distribution. MBMS user services can be used for any MC service group. + +The MBMS user service architecture is described in 3GPP TS 26.346 [21]. + +NOTE: The current specification does not cover MCData end-to-end encryption file distribution using MBMS when the BM-SC is in the MCData system trust domain. + +#### 7.3.5.2 Information flows for MBMS user service usage + +##### 7.3.5.2.1 MBMS user service announcement + +Table 7.3.5.2.1-1 describes the information flow MBMS bearer announcement from the MCData server to the MCData client. + +**Table 7.3.5.2.1-1: MBMS user service announcement** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBMS user service id | M | Id of the MBMS user service | +| SA file | M | The service announcement file as returned in the create/update session response (subclause 5.4 in 3GPP TS 26.348 [19]) (see NOTE) | +| Monitoring state | O | The monitoring state is used to control if the client is actively monitoring the reception quality or the MBMS bearer used by the MBMS user service. | +| Unicast status | O | An indication that the listening status of the unicast bearer is requested. | +| NOTE: | | The SA file provides the TMGI, the list of MBMS service area identifiers, the frequency and the delivery parameters. | + +#### 7.3.5.3 Procedures for MBMS user service usage + +##### 7.3.5.3.1 Use of pre-established MBMS user services + +###### 7.3.5.3.1.1 General + +In this scenario, the MCData server pre-establishes MBMS user service(s) in certain pre-configured areas before the initiation of a group file distribution. When a user originates a request for a file distribution in one of these areas, the MCData server can use the pre-established MBMS user service(s) for the DL media transmission. + +The MBMS user service can be announced prior to the file distribution or within the signalling message for the file distribution. + +The MBMS user service does not transmit application level control signalling. An MBMS bearer could be used for the application level control messages according to the generic MBMS procedures defined in 3GPP TS 23.280 [5]. + +###### 7.3.5.3.1.2 Procedure + +**Editor's note: The procedure in this clause needs to be revised considering that MBMS user services, as specified in 3GPP TS 26.346 [21], cannot be supported over the MB2 interface.** + +The procedure figure 7.3.5.3.1.2-1 shows only one of the receiving MCData clients using an MBMS user service. + +Pre-conditions: + +- The participating users are already affiliated. + +![Sequence diagram illustrating the use of pre-established MBMS user service between an MCData client and an MCData server.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant MCData server + Note right of MCData server: 1. create MBMS user service + Note right of MCData server: 2. create MBMS session + Note right of MCData server: 3a. activate MBMS bearer + Note right of MCData server: 3b. generate SA File + MCData server->>MCData client: 4. MBMS user service announcement + Note left of MCData client: 5. MCData client stores MBMS user service id, TMGI(s), service area and other info about the MBMS User service, the MCData UE starts to monitor the TMGI(s). + MCData client->>MCData server: 6. MBMS listening status report + Note right of MCData server: 7. update MBMS session with new file to be distributed + Note over MCData client, MCData server: 8. Signalling file distribution. + Note over MCData client, MCData server: 9. File distribution over MBMS + +``` + +The diagram shows a sequence of interactions between an MCData client and an MCData server. The process begins with the MCData server performing internal steps: 1. create MBMS user service, 2. create MBMS session, 3a. activate MBMS bearer, and 3b. generate SA File. These are followed by a message 4. MBMS user service announcement from the server to the client. The client then performs step 5: MCData client stores MBMS user service id, TMGI(s), service area and other info about the MBMS User service, the MCData UE starts to monitor the TMGI(s). This is followed by message 6. MBMS listening status report from the client to the server. The server then performs step 7: update MBMS session with new file to be distributed. This is followed by message 8. Signalling file distribution. from the server to the client. Finally, message 9. File distribution over MBMS is shown as a large arrow pointing from the server to the client. + +Sequence diagram illustrating the use of pre-established MBMS user service between an MCData client and an MCData server. + +**Figure 7.3.5.3.1.2-1: Use of pre-established MBMS user service** + +1. The MCData server determines to create an MBMS user service with a given MBMS user service id. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS user service over xMB-C (subclause 5.3 from 3GPP TS 26.348 [19]). + +NOTE 1: The procedure to determine the creation of MBMS user services is implementation specific. + +2. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS session over xMB-C for the MBMS user service (subclause 5.4 from 3GPP TS 26.348 [19]), with the type set to "Files" to use the MBMS download delivery method. Additionally, the MCData server defines the ingest mode, pull or push, to provide the file into the BM-SC via xMB-U. This MBMS session will be used for file distribution. In response, the MCData server gets the TMGI of the MBMS bearer used for the MBMS session, and the SA file containing the metadata of the MBMS user service. When the push ingest mode is used, as part of the response from the BM-SC the MCData server also obtains the URL to be used to push the file. +- 3a. Else, the MCData server activates an MBMS bearer over MB2-C for the MBMS user service. +- 3b. The MCData server, if not already in the possession of the SA file, generates the SA file containing the metadata of the MBMS user service. +4. The MCData server passes using control plane signalling the MBMS user service info for the service description associated with the pre-established MBMS user service to the MCData client. The MCData client obtains the TMGI, identifying the MBMS bearer, from the SA file included in the MBMS user service description. +5. The MCData client stores the information associated with the MBMS user service. The MCData client uses the TMGI and other MBMS user service related information to activate the monitoring of the MBMS bearer. +6. The MCData client that enters or is in the service area of at least one announced TMGI indicates to the MCData server that the MCData client is able to receive file distributed over MBMS, whereby the MCData server may decide to use this MBMS user service instead of unicast bearer for MC communication sessions. + +NOTE 2: Step 4 is optional for the MCData UE on subsequent MBMS user service announcements. + +NOTE 3: The information flow is specified in subclause 10.7.2.2 from 3GPP TS 23.280 [5]. + +7. If the MCData server makes use of the xMB interface and wants to deliver a file to a group, the MCData server updates the MBMS session to provide the file list when the pull ingest mode is defined. As described in 3GPP TS 26.348 [19], the file list includes, among other information, the file URL to be used by the BM-SC to fetch the file and the earliest fetch time. + 8. The MCData server signals the file transmission over the MBMS user service to the targeted MCData clients. +- NOTE 4: After step 8, the file can be provided for distribution over the MBMS session. If the pull ingest mode is defined, the BM-SC fetches the file from the indicated file URL. If the push ingest mode is defined, the MCData server can start pushing the file to the corresponding URL. +9. The file, transmitted with the MBMS download delivery method, is received by the MCData clients. If the MCData server does not make use of the xMB interface, the MCData server fragments the file to be sent, applies error correction according to the MBMS download delivery method (3GPP TS 26.346 [21]) and sent the FLUTE packets over MB2-U. + +##### 7.3.5.3.2 Use of dynamic MBMS user service establishment + +**Editor's note: The procedure in this clause needs to be revised considering that MBMS user services, as specified in 3GPP TS 26.346 [21], cannot be supported over the MB2 interface.** + +In this scenario depicted in figure 7.3.5.3.2-1, the MCData server decides to establish an MBMS user service for the distribution of a given file. The MBMS user service is announced to the MCData client, together with the file information to be received. + +NOTE 1: The MCData server logic for determining when to establish the new MBMS user service is implementation specific. For example, the MCData server could decide to establish the MBMS delivery based on the location of the UE's that are a part of the targeted group. + +![Sequence diagram illustrating the use of dynamic MBMS user service establishment between an MCData client and an MCData server.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant MCData server + Note right of MCData server: 1.Create MBMS user service + Note right of MCData server: 2.Create MBMS session with info of the file to be distributed + Note right of MCData server: 3a. activate MBMS bearer + Note right of MCData server: 3b. generate SA File + MCData server->>MCData client: 4. MBMS user service announcement + Note left of MCData client: 5. MC service client stores MBMS user service ID, TMGI(s), service area and other info about the MBMS user service(s), the MC service UE starts to monitor the TMGI(s). + MCData client->>MCData server: 6. MBMS listening status report + Note over MCData client, MCData server: 7. Signalling file distribution + Note over MCData client, MCData server: 8. File distribution over MBMS + +``` + +The diagram shows a sequence of interactions between an MCData client and an MCData server. The process begins with the MCData server performing internal steps: 1. Create MBMS user service, 2. Create MBMS session with info of the file to be distributed, 3a. activate MBMS bearer, and 3b. generate SA File. These steps are grouped by dashed boxes. The server then sends a 4. MBMS user service announcement to the client. The client responds with 5. MC service client stores MBMS user service ID, TMGI(s), service area and other info about the MBMS user service(s), the MC service UE starts to monitor the TMGI(s). The client then sends a 6. MBMS listening status report to the server. The server performs 7. Signalling file distribution, followed by 8. File distribution over MBMS, which is represented by a large arrow pointing from the server to the client. + +Sequence diagram illustrating the use of dynamic MBMS user service establishment between an MCData client and an MCData server. + +**Figure 7.3.5.3.2-1: Use of dynamic MBMS user service establishment** + +1. The MCData server determines to create a MBMS user service with a given an MBMS user service id for the group communication session. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS user service over xMB-C (subclause 5.3 from 3GPP TS 26.348 [19]). +2. If the MCData server makes use of the xMB interface, the MCData server creates a MBMS session for the MBMS user service (subclause 5.4 from 3GPP TS 26.348 [19]), with the type set to "Files" to use the MBMS download delivery method. Additionally, the MCData server defines the ingest mode, pull or push, to provide the file into the BM-SC via xMB-U. When the pull ingest mode is defined, the MCData server provides the file list. The file list includes, among other information, the file URL to be used by the BM-SC to fetch the file and the earliest fetch time. In response, the MCData server gets the TMGI of the MBMS bearer used for the MBMS session and the SA file containing the metadata of the MBMS user service. When the pull ingest mode is defined, the MCData server also obtains the scheduling parameter for the file delivery. When the push ingest mode is used, as part of the response from the BM-SC the MCData server obtains the URL to be used to push the file. +- 3a. Else, the MCData server activates an MBMS bearer over MB2-C for the MBMS user service. +- 3b. The MCData server, if not already in the possession of the SA file, generates the SA file containing the metadata of the MBMS user service. +4. The MCData server passes using control plane signalling the SA file to the MCData client. The MCData client obtains the TMGI, identifying the MBMS bearer, from the SA file included in the MBMS user service description. +5. The MCData client stores the information associated with the MBMS user service. The MCData client uses the TMGI and other MBMS user service related information to activate the monitoring of the MBMS bearer. +6. The MCData client that enters or is in the service area of at least one announced TMGI indicates to the MCData server that the MCData client is able to receive file distributed over MBMS, whereby the MCData server may decide to use this MBMS user service instead of unicast bearer for MC communication sessions. +7. The MCData server signals the file transmission over the MBMS user service to the targeted MCData clients. + +NOTE 2: After step 7, the file can be provided for distribution over the MBMS session. If the pull ingest mode is defined, the BM-SC fetches the file from the indicated file URL. If the push ingest mode is defined, the MCData server can start pushing the file to the corresponding URL. + +8. The file, transmitted with the MBMS download delivery method, is received by the MCData clients. If the MCData server does not make use of the xMB interface, the MCData server fragments the file to be sent, applies error correction according to the MBMS download delivery method (3GPP TS 26.346 [21]) and sent the FLUTE packets over MB2-U. + +##### 7.3.5.3.3 Providing stored files in the MCData content server for distribution over MBMS + +###### 7.3.5.3.3.1 General + +As described in clause 6.6.3.1.5, the MCData content server provides a repository area where authorized MCData users temporarily store files that are intended to be shared with other MCData users. The distribution of such files targeting a group of MCData users can be performed over MBMS. + +For the case that the MBMS user service architecture is used over the xMB interface (specified in 3GPP TS 26.348 [19]), two ingest modes, push and pull, can be defined by the MCData server to ingest the file into the BM-SC for distribution over the MBMS sessions. + +NOTE: It is implementation specific if the MCData server uses pull or push ingest mode to ingest the file into the BM-SC over the xMB interface. + +###### 7.3.5.3.3.2 File fetching by the MCData server + +A file can be fetched by the MCData server from the MCData content server over the MCData-FD-5 reference point using the file URL provided by MCData users. The MCData server, thus, enables via the xMB-U interface that the file is ingested, either by pull or push, into the BM-SC for distribution over MBMS. + +NOTE 1: The file also becomes available for the case that the MCData server decides to distribute the file over the MB2 interface to MCData users from the target MCData group. + +When the MCData server defines a pull ingest mode, the MCData server provides via the xMB-C interface the resource location from which the BM-SC will fetch the file as well as other session properties (e.g. file earliest fetch time), as described in 3GPP TS 26.348 [19]. + +When the MCData server defines a push ingest mode, the MCData server directly ingests into the BM-SC via the xMB-U interface the file obtained from the MCData content server. The BM-SC provides to the MCData server the URL to be used to push the file(s). + +NOTE 2: For the push ingest mode, the MCData server is always the functional entity ingesting the file content into the BM-SC via the xMB-U interface. + +The procedure in figure 7.3.5.3.3.2-1 describes the case where the file to be distributed over MBMS is fetched by the MCData server from the MCData content server. + +Pre-conditions: + +- The MCData users on the MCData client 1 to n belong to the same MCData group and are already registered and affiliated for receiving MCData service. +- The file to be distributed is uploaded to the MCData content server. +- The BM-SC has the necessary permissions to fetch a file from the MCData system. + +![Sequence diagram illustrating file fetching by the MCData server for file distribution over MBMS. The diagram shows interactions between MCData client 2 to n, BM-SC, MCData client 1, MCData server, and MCData content server. The process involves a file distribution request, fetching the file, creating an MBMS service, signaling, ingesting the file (push or pull mode), and distributing the file over the MBMS session.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 to n + participant BM-SC + participant MCData server + participant MCData content server + + Note right of MCData client 1: 1. File distribution request + MCData client 1->>MCData server: 1. File distribution request + Note right of MCData server: 2. Fetch file + MCData server->>MCData content server: 2. Fetch file + Note right of MCData server: 3. Create MBMS service and session for FD + MCData server->>BM-SC: 3. Create MBMS service and session for FD + Note right of BM-SC: 4. MBMS and FD application signaling + BM-SC->>MCData client 2 to n: 4. MBMS and FD application signaling + Note right of MCData server: 5.a. Ingest File into BM-SC based on push ingest mode (Push File) + MCData server-->>BM-SC: 5.a. Ingest File into BM-SC based on push ingest mode (Push File) + Note right of MCData server: 5.b. Ingest File into BM-SC based on pull ingest mode (Fetch File) + BM-SC-->>MCData server: 5.b. Ingest File into BM-SC based on pull ingest mode (Fetch File) + Note right of BM-SC: 6. File distribution over MBMS session + BM-SC->>MCData client 2 to n: 6. File distribution over MBMS session + +``` + +Sequence diagram illustrating file fetching by the MCData server for file distribution over MBMS. The diagram shows interactions between MCData client 2 to n, BM-SC, MCData client 1, MCData server, and MCData content server. The process involves a file distribution request, fetching the file, creating an MBMS service, signaling, ingesting the file (push or pull mode), and distributing the file over the MBMS session. + +**Figure 7.3.5.3.3.2-1: File fetching by the MCData server for file distribution over MBMS** + +1. The MCData server receives a request from the MCData client 1 to distribute a file to a target MCData group. The MCData file distribution request contains the resource location (i.e. the file URL) in the MCData content server. +2. The MCData server decides to fetch the file from the MCData content server via the MCData-FD-5 reference point. +3. The MCData server creates an MBMS service and session for file delivery using xMB procedures via the xMB-C interface, as described in 3GPP TS 26.348 [19]. The MCData server indicates, among other session properties, the ingest mode. For the case of pull ingest mode, the MCData server provides the file URL from which the BM-SC will fetch the file. For the case of push ingest mode, the BM-SC provides to the MCData server the URL to be used to push the file into the MBMS session. + +NOTE 3: Step 3 may also occur before step 2. + +4. The MCData server provides to the MCData users from the target MCData group the application signalling related to the MBMS session and the file distribution. +- 5a. For the case that the file is ingested into the BM-SC based on the push ingest mode, the MCData server pushes the file to the URL indicated by the BM-SC. +- 5b. For the case that the file is ingested into the BM-SC based on the pull ingest mode, the BM-SC pulls the file from the provided file URL. +6. The BM-SC distributes the file over the established MBMS session. When the target MCData clients have activated the reception for that service and are located within the MBMS area coverage, the MCData clients receive the file. + +###### 7.3.5.3.3.3 File fetching by the BM-SC + +When the MCData server defines a pull ingest mode, the MCData server can alternatively provide to the BM-SC the resource location in the MCData content server (i.e. the file URL contained within the received file distribution request). The BM-SC, thus, will directly fetch the file from the MCData content server. + +NOTE 1: In order to enable that the BM-SC fetches the file from the MCData content server, the MCData content server supports the xMB-U interface to the BM-SC. + +NOTE 2: For the case that the file is ingested into the BM-SC from the MCData content server, only the pull ingest mode is supported. When push ingest mode is required, the procedure is described in clause 7.3.5.3.3.2. + +The procedure in figure 7.3.5.3.3.3-1 describes the case where the file to be distributed over MBMS is fetched by the BM-SC from the MCData content server. + +Pre-conditions: + +- The MCData users on the MCData client 1 to n belong to the same MCData group and are already registered and affiliated for receiving MCData service. +- The file to be distributed is uploaded to the MCData content server. +- The BM-SC has the necessary permissions to fetch a file from the MCData system. + +![Sequence diagram illustrating the file fetching process by the BM-SC for file distribution over MBMS. The diagram shows five steps: 1. MCData client 1 sends a 'File distribution request' to the MCData server. 2. The MCData server sends a 'Create MBMS service and session for FD' message to the BM-SC. 3. The BM-SC sends 'MBMS and FD application signaling' to the MCData client 2 to n. 4. The BM-SC sends a message to fetch the file from the MCData content server (pull ingest mode). 5. The BM-SC sends 'File distribution over MBMS session' to the MCData client 2 to n.](6324b252294c0f5d4e34dad4a1202075_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant BM-SC + participant MCData content server + participant MCData client 2 to n + + Note right of MCData client 1: 1. File distribution request + MCData client 1->>MCData server: 1. File distribution request + Note right of MCData server: 2. Create MBMS service and session for FD + MCData server->>BM-SC: 2. Create MBMS service and session for FD + Note right of BM-SC: 3. MBMS and FD application signaling + BM-SC->>MCData client 2 to n: 3. MBMS and FD application signaling + Note right of BM-SC: 4. BM-SC fetches the File from the MCData content server (pull ingest mode) + BM-SC->>MCData content server: 4. BM-SC fetches the File from the MCData content server (pull ingest mode) + Note right of BM-SC: 5. File distribution over MBMS session + BM-SC->>MCData client 2 to n: 5. File distribution over MBMS session +``` + +Sequence diagram illustrating the file fetching process by the BM-SC for file distribution over MBMS. The diagram shows five steps: 1. MCData client 1 sends a 'File distribution request' to the MCData server. 2. The MCData server sends a 'Create MBMS service and session for FD' message to the BM-SC. 3. The BM-SC sends 'MBMS and FD application signaling' to the MCData client 2 to n. 4. The BM-SC sends a message to fetch the file from the MCData content server (pull ingest mode). 5. The BM-SC sends 'File distribution over MBMS session' to the MCData client 2 to n. + +**Figure 7.3.5.3.3.3-1: File fetching by the BM-SC for file distribution over MBMS** + +1. The MCData server receives a request from the MCData client 1 to distribute a file to a target MCData group. The MCData file distribution request contains the resource location (i.e. the file URL) in the MCData content server. +2. The MCData server creates an MBMS service and session for file delivery using xMB procedures via the xMB-C interface, as described in 3GPP TS 26.348 [19]. The MCData server defines, among other session properties, the ingest mode to pull. The MCData server provides the file URL from which the BM-SC will fetch the file from the MCData content server. +3. The MCData server provides to the MCData users from the target MCData group the application signalling related to the MBMS session and the file distribution. +4. The BM-SC fetches the file from the MCData content server via the xMB-U interface. +5. The BM-SC distributes the file over the established MBMS session. When the target MCData clients have activated the reception for that service and are located within the MBMS area coverage, the MCData clients receive the file. + +### 7.3.6 Group communication connect and disconnect over MBMS bearer procedures + +#### 7.3.6.1 General + +MBMS bearer can be used for MCData group communication. One MBMS bearer is not permanently associated to one specific group or group communication. Before sending data packets of a group communication over MBMS bearer, the MCData server shall send the association information between group communication and the MBMS bearer. The group session setup procedure indicates the media stream within one MBMS bearer that is used for the specific group communication. When the group communication over the MBMS bearer is finished, this temporary association information of an MCPTT group communication to specific resources on a MBMS bearer is undone. The procedure in clause 7.3.6 requires that the group session is setup before the data transmission starts. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to group session setup, the MBMS bearer is activated and announced to the MCData clients. + +NOTE: It is implementation-specific that one MBMS bearer can be re-assigned to different groups, or is associated to only one group. + +#### 7.3.6.2 Procedure + +The procedure in this clause uses an establishment of group communication as described in clause 7.4.2.7. Similarly, the procedure defined in this clause is also applicable for the group communication established as described in clause 7.4.2.6. + +##### 7.3.6.2.1 Group communication connect over MBMS bearer + +Pre-conditions: + +- The MCData clients 1 to n are registered and affiliated to the same MCData group X. +- The MCData server has decided to use an MBMS bearer for the MCData service group communication associated with to the MCData group X. + +![Sequence diagram illustrating the group communication connect over MBMS bearer procedure. The diagram shows interactions between MCData client 1, MCData server, and MCData clients 2-n. The sequence starts with activation and announcement of the MBMS bearer. Client 1 sends a data request to the server, which then requests data from clients 2-n. A 'Notify User' step is shown for clients 2-n. The server receives a response from clients 2-n and sends a response back to client 1. The server then sends a MapGroupToBearer message to clients 2-n, which ACKs. Finally, data is transmitted via unicast PDN connection from client 1 to the server, and then via MBMS bearer from the server to clients 2-n.](84a01685710d24f113b18758ed3c6fcb_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCData client 1 + participant Server as MCData server + participant Clients2n as MCData clients 2-n + + Note over Client1, Server, Clients2n: 1. Activation and announcement of MBMS bearer + Client1->>Server: 2. MCData group data request + Server->>Clients2n: 3. MCData group data request + Note right of Clients2n: 4. Notify User + Clients2n->>Server: 5. MCData group data response + Server->>Clients2n: 6. MapGroupToBearer + Clients2n-->>Server: 7. MapGroupToBearer ACK + Server->>Client1: 8. MCData group data response + Note right of Client1: 9. MC data via unicast PDN connection + Server->>Clients2n: 10. MC data via MBMS bearer + +``` + +Sequence diagram illustrating the group communication connect over MBMS bearer procedure. The diagram shows interactions between MCData client 1, MCData server, and MCData clients 2-n. The sequence starts with activation and announcement of the MBMS bearer. Client 1 sends a data request to the server, which then requests data from clients 2-n. A 'Notify User' step is shown for clients 2-n. The server receives a response from clients 2-n and sends a response back to client 1. The server then sends a MapGroupToBearer message to clients 2-n, which ACKs. Finally, data is transmitted via unicast PDN connection from client 1 to the server, and then via MBMS bearer from the server to clients 2-n. + +Figure 7.3.6.2.1-1: Group communication connect on MBMS bearer. + +1. Activation and announcement of MBMS bearer availability. + +NOTE 1: The procedure does not include the steps for MCData client location reporting, or for MBMS capability information exchange. + +2. The MCData client 1 initiates a group communication by sending a MCData group data request over a unicast PDN connection towards the MCData server. +3. MCData server initiates the MCData group data request towards each MCData clients 2 to n. +4. The receiving MCData clients 2 to n optionally notify the user about the incoming MCData session data request. +5. The receiving MCData client 2 to n accept or reject the MCData group data request and the corresponding result is in the MCData group data response towards MCData server. +6. The MCData server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the communication over an MBMS bearer. The MapGroupToBearer message includes association information between the group communication and MBMS bearer. The MapGroupToBearer message includes MCData group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the communication. +7. The MCData clients 2 to n process the MapGroupToBearer information and may send a MapGroupToBearer Ack back to the MCData server if required. +8. MCData server forwards the MCData group data response received from MCData client 2 to n to the MCData user initiating the MCData session data request. + +NOTE 2: The steps 3 to 5 and steps 6 to 7 can occur in any order, and prior to step 9 depending on the conditions to proceed with the data transmission. + +9. MCData client 1 sends the MC data over uplink unicast PDN connection towards the MCData server. +10. The MCData server sends the MC data over the indicated stream within the associated MBMS bearer to the MCData clients 2 to n. + +##### 7.3.6.2.2 Group communication disconnect from MBMS bearer + +Figure 7.3.6.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCData server to the MCData clients to indicate that the MCData group communication is being dissociated from the MBMS bearer. + +![Sequence diagram illustrating the group communication disconnect from MBMS bearer. The diagram shows three lifelines: MCData client 1, MCData server, and MCData clients 2-n. Step 1: MCData client 1 sends '1. MC data via a unicast PDN connection' to the MCData server. Step 2: The MCData server sends '2. MC data via MBS session' to the MCData clients 2-n. Step 3: The MCData server sends '3. UnMapGroupFromBearer' to the MCData clients 2-n.](5d76c2e9976aaf97001ee189908830fb_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData clients 2-n + Note left of MCData client 1: MC data via unicast PDN + MCData client 1->>MCData server: 1. MC data via a unicast PDN connection + Note right of MCData server: MC data via MBS session + MCData server->>MCData clients 2-n: 2. MC data via MBS session + Note right of MCData server: UnMapGroupFromBearer + MCData server->>MCData clients 2-n: 3. UnMapGroupFromBearer +``` + +Sequence diagram illustrating the group communication disconnect from MBMS bearer. The diagram shows three lifelines: MCData client 1, MCData server, and MCData clients 2-n. Step 1: MCData client 1 sends '1. MC data via a unicast PDN connection' to the MCData server. Step 2: The MCData server sends '2. MC data via MBS session' to the MCData clients 2-n. Step 3: The MCData server sends '3. UnMapGroupFromBearer' to the MCData clients 2-n. + +**Figure 7.3.6.2.2-1: Group communication disconnect on MBMS bearer.** + +1. The MC group communication is taking place over MBMS bearer. MCData client 1 is sending the MC data over a unicast PDN connection to the MCData server. + +2. The MCData server sends the MC data over the MBMS bearer to MCData clients 2 to n. +3. After the MC data transmission is over, i.e., no further data to be sent over the group communication, the MCData server sends an UnMapGroupFromBearer to de-associate the group communication from the MBMS bearer. + +## 7.4 Short data service + +### 7.4.1 General + +There are several procedures how an SDS message can be transported from the sender to the recipient. All of the following factors are used by MCData client for selecting appropriate SDS procedures: + +- Whether the data to transfer is within or outside the SDS data size limit to transport over signalling control plane; +- Whether the MCData user has only one SDS transaction or multiple SDS transactions; +- Whether MCData user, optionally using its associated and activated functional alias, is targeting SDS transaction to another MCData user or MCData group; +- Whether MCData UE is on-network or off-network; and +- Security reasons. + +### 7.4.2 Short data service for on-network + +The procedures described in the following subclauses are limited to single MCData system only. + +#### 7.4.2.1 Information flows for short data service + +##### 7.4.2.1.1 MCData standalone data request + +Table 7.4.2.1.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.1-1: MCData standalone data request (MCData client to MCData server)** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID (see NOTE 1) | O | The identity of the MCData user towards which the data is sent | +| Functional alias (see NOTE 1) | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Payload | M | SDS content | +| NOTE 1: Either the MCData ID or the functional alias must be present. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +**Table 7.4.2.1.1-2: MCData standalone data request (MCData server to MCData client)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Payload | M | SDS content | +| NOTE: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +##### 7.4.2.1.2 MCData data disposition notification + +Table 7.4.2.1.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to the MCData server. + +**Table 7.4.2.1.2-1: MCData data disposition notification** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered or read or both | + +##### 7.4.2.1.3 MCData standalone session data request + +Table 7.4.2.1.3-1 describes the information flow for the MCData standalone session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.3-1: MCData standalone session data request (MCData client to MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID (see NOTE 1) | O | The identity of the MCData user towards which the data is sent | +| Functional alias (see NOTE 1) | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Requested Priority | O | Application priority level requested for this communication. | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| NOTE 1: Either the MCData ID or the functional alias must be present. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +**Table 7.4.2.1.3-2: MCData standalone session data request (MCData server to MCData client)** + +| Information element | Status | Description | +|-----------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| NOTE: | | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | + +##### 7.4.2.1.4 MCData standalone session data response + +Table 7.4.2.1.4-1 describes the information flow for the MCData standalone session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.4-1: MCData standalone session data response** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Establishment reason | M | Reason for establishment or rejection | + +##### 7.4.2.1.5 MCData session data request + +Table 7.4.2.1.5-1 describes the information flow for the MCData session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.5-1: MCData session data request (MCData client to MCData server)** + +| Information element | Status | Description | +|-------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID (see NOTE 1) | O | The identity of the MCData user towards which the data is sent | +| Functional alias (see NOTE 1) | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | + +NOTE 1: Either the MCData ID or the functional alias must be present. +NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. + +**Table 7.4.2.1.5-2: MCData session data request (MCData server to MCData client)** + +| Information element | Status | Description | +|-----------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | O | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | + +NOTE: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. + +##### 7.4.2.1.6 MCData session data response + +Table 7.4.2.1.6-1 describes the information flow for the MCData session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.6-1: MCData session data response** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +##### 7.4.2.1.7 MCData group standalone data request (MCData client – MCData server) + +Table 7.4.2.1.7-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData client to the MCData server. + +**Table 7.4.2.1.7-1: MCData group standalone data request (MCData client – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| MCData ID list (see NOTE 4) | O | The specified MCData users who should send a disposition notification message. | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Payload | M | SDS content | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | +| NOTE 4: If Disposition Type IE is not present, this IE shall not be present. If Disposition Type IE is present but this IE is not, which indicates that all receivers shall respond with disposition notification message. | | | + +##### 7.4.2.1.8 MCData group standalone data request (MCData server – MCData client) + +Table 7.4.2.1.8-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.8-1: MCData group standalone data request (MCData server – MCData client)** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| MCData ID list (see NOTE 4) | O | The specified MCData users who should send disposition notification message. | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Payload | M | SDS content | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: This information element may be present only when Emergency indicator is present.
NOTE 3: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption.
NOTE 4: If Disposition Type IE is not present, this IE shall not be present. If Disposition Type IE is present but this IE is not, which indicates that all receivers shall respond with disposition notification message. | | | + +##### 7.4.2.1.9 MCData data disposition notification (MCData server – MCData client) + +Table 7.4.2.1.9-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.9-1: MCData data disposition notification(s) (MCData server – MCData client)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered or read or both | + +###### 7.4.2.1.9A MCData aggregated data disposition notification + +Table 7.4.2.1.9A-1 describes the information flow for the MCData aggregated data disposition notification sent from the MCData server to the MCData client, indicating the result of a request for an SDS delivery to an MCData group. + +**Table 7.4.2.1.9A-1: MCData aggregated data disposition notification** + +| Information element | Status | Description | +|-------------------------------------|--------|--------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| Number of Aggregated Notifications | M | Total number of received individual notifications | +| Number of "Read" Notifications | O | Number of MCData users who only reported the "read" disposition | +| Number of "Delivered" Notifications | O | Number of MCData users who only reported the "delivered" disposition | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| "Read" MCData ID list | O | List, partial or full, of MCData users who only reported the "read" disposition | +| "Delivered" MCData ID list | O | List, partial or full, of MCData users who only reported the "delivered" disposition | + +##### 7.4.2.1.10 MCData group session standalone data request (MCData client – MCData server) + +Table 7.4.2.1.10-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server. + +**Table 7.4.2.1.10-1: MCData group session standalone data request (MCData client – MCData server)** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI, attached data hosts) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: This information element may be present only when Emergency indicator is present.
NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption or IP data in IP connectivity sessions are for data host consumption. | | | + +##### 7.4.2.1.11 MCData group session standalone data request (MCData server – MCData client) + +Table 7.4.2.1.11-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.11-1: MCData group session standalone data request (MCData server – MCData client)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI, attached data hosts) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption or IP data in IP connectivity sessions are for data host consumption. | | | + +##### 7.4.2.1.12 MCData group session standalone data response + +Table 7.4.2.1.12-1 describes the information flow for the MCData group standalone data response (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.12-1: MCData group session standalone data response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +##### 7.4.2.1.13 MCData group data request (MCData client – MCData server) + +Table 7.4.2.1.13-1 describes the information flow for the MCData group data request sent from the MCData client to the MCData server. + +**Table 7.4.2.1.13-1: MCData group data request (MCData client – MCData server)** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: This information element may be present only when Emergency indicator is present.
NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +##### 7.4.2.1.14 MCData group data request (MCData server – MCData client) + +Table 7.4.2.1.14-1 describes the information flow for the MCData group data request sent from the MCData server to the MCData client. + +**Table 7.4.2.1.14-1: MCData group data request (MCData server – MCData client)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the recipient MCData user | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer | M | Media parameters offered | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +##### 7.4.2.1.15 MCData group data response + +Table 7.4.2.1.15-1 describes the information flow for the MCData group data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.15-1: MCData group data response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +##### 7.4.2.1.16 MCData one-to-one SDS communication upgrade request + +Table 7.4.2.1.16-1 describes the information flow for the MCData one-to-one SDS communication upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.16-1: MCData one-to-one SDS communication upgrade request** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator | M | Indicates that the data request is for MCData emergency communication | + +##### 7.4.2.1.17 MCData one-to-one SDS communication upgrade response + +Table 7.4.2.1.17-1 describes the information flow for the MCData one-to-one SDS communication upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.17-1: MCData one-to-one SDS communication upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| Conversation Identifier | M | Identifies the conversation | + +##### 7.4.2.1.18 MCData group SDS communication upgrade request + +Table 7.4.2.1.18-1 describes the information flow for the MCData group SDS communication upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.18-1: MCData group SDS communication upgrade request (MCData client to MCData server)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending upgrade request | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +**Table 7.4.2.1.18-2: MCData group SDS communication upgrade request (MCData server to MCData client)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending upgrade request | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| MCData ID | M | The identity of the MCData user receiving the upgrade request | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +##### 7.4.2.1.19 MCData group SDS communication upgrade response + +Table 7.4.2.1.19-1 describes the information flow for the MCData group SDS communication upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.19-1: MCData group SDS communication upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | + +##### 7.4.2.1.20 MCData group SDS communication in-progress priority state cancel request + +Table 7.4.2.1.20-1 describes the information for the MCData group SDS communication in-progress priority state cancel request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.20-1: MCData group SDS communication in-progress priority state cancel request (MCData client to MCData server)** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency state is to be cancelled. | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Conversation Identifier | M | Identifies the conversation | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +**Table 7.4.2.1.20-2 MCData group SDS communication in-progress priority state cancel request (MCData server to MCData client)** + +| Information Element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency state is to be cancelled. | +| MCData ID | M | The identity of the recipient MCData user | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Conversation Identifier | M | Identifies the conversation | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +##### 7.4.2.1.21 MCData group SDS communication in-progress priority state cancel response + +Table 7.4.2.1.21-1 describes the information flow for the MCData group SDS communication in-progress priority state cancel response sent from the MCData server to the MCData client. + +**Table 7.4.2.1.21-1: MCData group SDS communication in-progress priority state cancel response** + +| Information Element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency in-progress is to be cancelled. | +| Conversation Identifier | M | Identifies the conversation | + +##### 7.4.2.1.22 MCData functional alias resolution response + +Table 7.4.2.1.22-1 describes the information flow MCData functional alias resolution response from the MCData server to the MCData client. + +**Table 7.4.2.1.22-1: MCData functional alias resolution response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the data | +| MCData ID | M | The corresponding MCData ID of the functional alias resolved by MCData server | + +#### 7.4.2.2 One-to-one standalone short data service using signalling control plane + +##### 7.4.2.2.1 General + +A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer signalling plane is used. The target MCData user may be addressed using the functional alias that can be shared with other MCData users. + +##### 7.4.2.2.2 Procedure + +The procedure in figure 7.4.2.2.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. + +Pre-conditions: + +1. The SDS payload data size is below the configured maximum payload data size for SDS over signalling control plane. +2. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +3. MCData client 1 and MCData client 2 belong to the same MCData system. +4. Optionally, the MCData client may have activated functional alias to be used. +5. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the One-to-one standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2.](a3472689858b068ef469213682965325_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData standalone data request + Note right of MCData server: 3. Authorize request and policy assertion + MCData server-->>MCData client 1: 4. MCData Functional alias resolution response + MCData client 1->>MCData server: 5. MCData standalone data request + MCData server->>MCData client 2: 6. MCData standalone data request + Note right of MCData client 2: 7. Process payload + MCData client 2-->>MCData server: 8. MCData data disposition notification + MCData server-->>MCData client 1: 9. MCData data disposition notification + MCData client 2-->>MCData server: 10. MCData data disposition notification + MCData server-->>MCData client 1: 11. MCData data disposition notification + +``` + +Sequence diagram illustrating the One-to-one standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.4.2.2.2-1: One-to-one standalone short data service using signalling control plane** + +1. The user at MCData client 1 initiates an SDS data transfer for the chosen MCData user. + 2. MCData client 1 sends a MCData standalone data request towards the MCData server. The MCData standalone data request contains conversation identifier for message thread indication. The MCData standalone data request may include additional implementation specific information in the application metadata container. The MCData standalone data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer and addresses the target MCData client 2 using a functional alias. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency short data service communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData standalone data request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. +- NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData standalone data request. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. The MCData server also checks whether any policy is to be asserted to + +limit certain types of message or content to certain members due, for example, to location or user privilege or affiliation. If functional alias is used to address that target MCData user, the MCData server resolves the functional alias to the corresponding MCData ID(s) for which the functional alias is active and proceed with step 4 otherwise proceed with step 6. The MCData server allows only two participating MCData clients for a standalone short data service. + +NOTE 2: The MCData server prioritizes the MCData emergency communication over the other MCData communication. How the MCData server prioritizes MCData emergency communication is not in the scope of the present document. + +NOTE 3: If the MCData server detects that the functional alias used as the target of the SDS data transfer request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the SDS data transfer request, if no suitable MCData ID is selected. + +4. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID. + +5. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 assumes the MCData standalone data request in step 2 is rejected and sends a new MCData standalone data request towards the resolved MCData ID. + +6. MCData server initiates the MCData standalone data request towards the MCData user that is determined based on step 3. The MCData standalone data request towards the MCData user contains the emergency indicator if it is present in the received MCData standalone data request from MCData client 1. + +NOTE 4: MCData client 2 does not set its emergency state as a result of receiving the MCData standalone data request containing the emergency indicator. + +7. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +8. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client initiates a MCData data disposition notification for delivery report. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. + +9. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +10. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. The MCData data disposition notification from MCData client 2 may be stored by the MCData server for disposition history interrogation from authorized MCData users. + +11. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.3 One-to-one standalone short data service using media plane + +##### 7.4.2.3.1 General + +A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer media plane is used. The target MCData user may be addressed using the functional alias that can be shared with other MCData users. + +##### 7.4.2.3.2 Procedure + +The procedure in figure 7.4.2.3.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane. + +Pre-conditions: + +1. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +2. MCData client 1 and MCData client 2 belong to the same MCData system. +3. Optionally, the MCData client may have an activated functional alias to be used. +4. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the one-to-one standalone short data service using media plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The process starts with MCData client 1 initiating a data request, followed by a standalone session data request to the server. The server then authorizes the request and resolves the functional alias. MCData client 1 then sends a standalone session data request to the server, which in turn sends a standalone session data request to MCData client 2. MCData client 2 responds, and the server responds back to MCData client 1. A data transmission phase follows, during which MCData client 2 processes the payload. Finally, MCData client 2 sends data disposition notifications to the server, which then forwards them to MCData client 1.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData standalone session data request + Note right of MCData server: 3. Authorize request and policy assertion + MCData server-->>MCData client 1: 4. MCData Functional alias resolution response + MCData client 1-->>MCData server: 5. MCData standalone session data request + MCData server->>MCData client 2: 6. MCData standalone session data request + MCData client 2-->>MCData server: 7. MCData standalone session data response + MCData server-->>MCData client 1: 8. MCData standalone session data response + Note over MCData client 1, MCData client 2: 9. Data transmission + Note right of MCData client 2: 10. Process payload + MCData client 2-->>MCData server: 11. MCData data disposition notification + MCData server-->>MCData client 1: 12. MCData data disposition notification + MCData client 2-->>MCData server: 13. MCData data disposition notification + MCData server-->>MCData client 1: 14. MCData data disposition notification + +``` + +Sequence diagram illustrating the one-to-one standalone short data service using media plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The process starts with MCData client 1 initiating a data request, followed by a standalone session data request to the server. The server then authorizes the request and resolves the functional alias. MCData client 1 then sends a standalone session data request to the server, which in turn sends a standalone session data request to MCData client 2. MCData client 2 responds, and the server responds back to MCData client 1. A data transmission phase follows, during which MCData client 2 processes the payload. Finally, MCData client 2 sends data disposition notifications to the server, which then forwards them to MCData client 1. + +**Figure 7.4.2.3.2-1: One-to-one standalone short data service using media plane** + +1. User at MCData client 1 would like to initiate an SDS data transfer request for the chosen MCData user. +2. MCData client 1 sends a MCData standalone session data request towards the MCData server. The MCData standalone session data request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData standalone session data request contains conversation identifier for message thread indication. The MCData standalone session data request may include additional implementation specific information in the application metadata container. The MCData data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer and addresses the target MCData client 2 using a functional alias. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency short data service communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + +- i) The MCData standalone session data request shall contain emergency indicator; and +- ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData standalone session data request. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server determines the eligible MCData user(s) after policy assertion for sending the MCData standalone session data request. If functional alias is used to address that target MCData user, the MCData server resolves the functional alias to the corresponding MCData ID(s) for which the functional alias is active and proceed with step 4 otherwise proceed with step 6. The resulting list contains all associated MCData IDs/MCData users that share this functional alias. The MCData server allows only two participating MCData clients for a standalone short data service. + +NOTE 2: The MCData server prioritizes the MCData emergency communication over the other MCData communication. How the MCData server prioritizes MCData emergency communication is not in the scope of the present document. + +4. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID. + +NOTE 3: If the MCData server detects that the functional alias used as the target of the MCData standalone session data request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the MCData standalone session data request, if no suitable MCData ID is selected. + +5. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 abandons the MCData standalone session data request in step 2 and sends a new MCData standalone session data request towards the resolved MCData ID. +6. MCData server initiates the MCData standalone session data request towards the MCData users determined. The MCData standalone session data request towards the MCData user contains an emergency indicator if it is present in the received MCData standalone session data request from MCData client 1. + +NOTE 4: MCData client 2 corresponds to the MCData user(s) after resolution of the functional alias. + +NOTE 5: MCData client 2 does not set its emergency state as a result of receiving the MCData standalone session data request containing the emergency indicator. + +7. The receiving MCData client 2 automatically accepts the MCData standalone session data request and responds with MCData standalone session data response towards MCData server. +8. MCData server forwards the MCData client 2 accepted response to the MCData Client 1 initiating the MCData standalone session data request. +9. MCData client 1 and MCData client 2 have successfully established media plane for data communication and the MCData client 1 transmits the SDS data. +10. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +11. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client initiates a MCData data disposition notification for delivery report. The MCData data disposition + +notification from MCData client 2 may be stored by the MCData server for disposition history interrogation from authorized MCData users. + +12. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. +13. If the MCData disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData disposition notification for read report. The MCData data disposition notification from MCData client 2 may be stored by the MCData server for disposition history interrogation from authorized MCData users. +14. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.4 One-to-one short data service session + +##### 7.4.2.4.1 General + +A MCData user triggers an establishment of a MCData session with another MCData user for the exchange of SDS data. The target MCData user may be addressed using the functional alias that can be shared with other MCData users. + +##### 7.4.2.4.2 Procedure + +The procedure in figure 7.4.2.4.2-1 describes the case where an MCData user is initiating data communication session with another MCData user for exchanging at least one SDS data transaction between them, with or without disposition request using MCData-SDS-1 and MCData-SDS-2 or MCData-SDS-3 reference points. + +Pre-conditions: + +1. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for a one-to-one short data service session. Lifelines: MCData client 1, MCData server, and MCData client 2. The sequence starts with MCData client 1 initiating a session data request. The server authorizes and resolves functional aliases. MCData client 1 then sends a session data request to the server, which forwards it to MCData client 2. Responses are returned from the server and client 2 to client 1. Data transmission and disposition messages are exchanged between client 1 and the server, with optional notify data messages to client 2 and client 1. The session ends with a session data termination message from the server.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. initiate session data request + MCData client 1->>MCData server: 2. MCData session data request + MCData server->>MCData server: 3. Authorize request and policy assertion + MCData server-->>MCData client 1: 4. MCData Functional alias resolution response + MCData client 1->>MCData server: 5. MCData session data request + MCData server->>MCData client 2: 6. MCData session data request + Note right of MCData client 2: 7. Notify request + MCData client 2->>MCData server: 8. MCData session data response + MCData server->>MCData client 1: 9. MCData session data response + Note over MCData client 1, MCData server: 10. Data transmission and disposition + Note right of MCData client 2: 11. Notify data + Note over MCData client 1, MCData server: 12. Data transmission and disposition + Note left of MCData client 1: 13. Notify data + Note over MCData server, MCData client 2: 14. Session data termination + +``` + +Sequence diagram for a one-to-one short data service session. Lifelines: MCData client 1, MCData server, and MCData client 2. The sequence starts with MCData client 1 initiating a session data request. The server authorizes and resolves functional aliases. MCData client 1 then sends a session data request to the server, which forwards it to MCData client 2. Responses are returned from the server and client 2 to client 1. Data transmission and disposition messages are exchanged between client 1 and the server, with optional notify data messages to client 2 and client 1. The session ends with a session data termination message from the server. + +**Figure 7.4.2.4.2-1: One-to-one short data service session** + +1. User at MCData client 1 would like to initiate an SDS data communication session request for the chosen MCData user. +2. MCData client 1 sends a MCData session data request towards the MCData server. The MCData session data request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData session data request contains conversation identifier for message thread indication. The MCData session data request may include additional implementation specific information in the application metadata container. MCData user at MCData client 1 may include a functional alias within the SDS data transfer and addresses the target MCData client 2 using a functional alias. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency short data service communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData session data request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData session data request. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server determines the eligible MCData user(s) after policy assertion for sending the MCData session data request. MCData server also verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. If functional alias is used to address that target MCData user, the MCData server resolves the functional alias to the corresponding MCData ID(s) for which the functional alias is active and proceed with step + +4 otherwise proceed with step 6. The MCData server allows only two participating MCData clients for a standalone short data service. + +NOTE 2: The MCData server prioritizes the MCData emergency communication over the other MCData communication. How the MCData server prioritizes MCData emergency communication is not in the scope of the present document. + +NOTE 3: If the MCData server detects that the functional alias used as the target of the MCData session data request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the SDS data transfer request, if no suitable MCData ID is selected. + +4. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID. + +5. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 abandons the MCData session data request in step 2 and sends a new MCData session data request towards the resolved MCData ID. + +6. MCData server initiates the MCData session data request towards the MCData users determined. The MCData session data request towards the MCData user contains the emergency indicator if it is present in the received MCData session data request from MCData client 1. + +NOTE 4: MCData client 2 corresponds to the MCData user(s) after resolution of the functional alias. + +NOTE 5: MCData client 2 does not set its emergency state as a result of receiving the MCData session data request containing the emergency indicator. + +7. If the emergency indicator is present, the receiving MCData client 2 notifies the user about the incoming MCData session data request. + +8. The receiving MCData client 2 accepts the MCData session data request and responds with MCData session data response towards MCData server. + +9. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData session data request. + +10. and 11. MCData client 1 and MCData client 2 have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If MCData data disposition was requested by the user, then the receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from MCData user may be stored by the MCData server for disposition history interrogation from authorized users. + +12. and 13. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified, otherwise the MCData user of MCData client 2 shall not be notified. + +14. After SDS data transaction is complete, the established media plane is released. + +#### 7.4.2.5 Group standalone short data service using signalling control plane + +##### 7.4.2.5.1 General + +The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane. + +##### 7.4.2.5.2 Procedure + +The procedure in figure 7.4.2.5.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request, to a group. + +Pre-conditions: + +1. MCData users on MCData clients 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating Group standalone SDS using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence starts with MCData client 1 initiating a group standalone data request. The MCData server then affiliates the user to the group, resolves the group ID, and sends a group standalone data request to MCData client 2 to n. MCData client 2 to n processes the payload and sends data disposition notifications back to the MCData server. The MCData server aggregates these notifications and sends an aggregated data disposition notification back to MCData client 1.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate group standalone data request + MCData client 1->>MCData server: 2. MCData group standalone data request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + MCData server->>MCData client 2 to n: 4. MCData group standalone data request + Note right of MCData client 2 to n: 5. Process payload + Note right of MCData client 2 to n: 6. MCData data disposition notification + Note right of MCData client 2 to n: 7. MCData data disposition notification + Note right of MCData server: 8. Aggregate notifications + MCData server->>MCData client 1: 9. MCData [aggregated] data disposition notification(s) + +``` + +Sequence diagram illustrating Group standalone SDS using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence starts with MCData client 1 initiating a group standalone data request. The MCData server then affiliates the user to the group, resolves the group ID, and sends a group standalone data request to MCData client 2 to n. MCData client 2 to n processes the payload and sends data disposition notifications back to the MCData server. The MCData server aggregates these notifications and sends an aggregated data disposition notification back to MCData client 1. + +**Figure 7.4.2.5.2-1: Group standalone SDS using signalling control plane** + +1. The user at MCData client 1 initiates an SDS data transfer to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group standalone data request towards the MCData server. The MCData group data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone data request contains conversation identifier for message thread indication. The MCData session data request may include additional implementation specific information in the application metadata container. The MCData group standalone data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency short data service communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group standalone data request shall contain an emergency indicator; +- ii) the MCData group standalone data request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData standalone data request for the emergency short data service communication; +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCPTT emergency state is retained until explicitly cancelled; and + +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled. + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group standalone data request shall contain imminent peril indicator; and + - ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled. +- 2a. If either emergency indicator or imminent peril indicator is present in the received MCData group standalone data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + - 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege or affiliation. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. + - i) If an emergency indicator is present in the received MCData group standalone data request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; and + - ii) If an imminent peril indicator is present in the received MCData group standalone data request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled. + - 4. MCData server initiates the MCData group standalone data request towards each MCData client determined in Step 3. The MCData ID list shall not be included in a unicast downlink delivery to an individual MCData client. The Disposition Type IE shall not be included in a unicast downlink delivery to MCData clients who are not in the MCData ID list in step 2. The MCData group standalone data request towards each MCData client contains: + - i) an emergency indicator, if it is present in the received MCData group standalone data request from the MCData client 1; + - ii) an imminent peril indicator, if it is present in the received MCData group standalone data request from the MCData client 1; and + - iii) an alert indicator, if requested to initiate an emergency alert in the received MCData group standalone data request from the MCData client 1. + - 5. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData clients 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData clients 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + - 6. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report. + - 7. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +NOTE 1: On receiving MCData group standalone data request over MBMS, the receiving MCData client(s) shall check if the MCData ID list IE is included the receiving MCData client shall check if its own MCData ID is in the list. If not, step 6 and 7 are not required. + +- 8. The MCData data disposition notification(s) from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification(s) from each MCData user may be aggregated. + +9. Aggregated or individual MCData data disposition notification(s) is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.6 Group standalone short data service using media plane + +##### 7.4.2.6.1 General + +The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane. + +##### 7.4.2.6.2 Procedure + +The procedure in figure 7.4.2.6.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request to a group. + +Pre-conditions: + +1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group standalone SDS using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows the initiation of a data request, group session setup, data transmission, and disposition notifications.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group session standalone data request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 3a. Bearer priority configuration + MCData server->>MCData client 2 to n: 4. MCData group session standalone data request + MCData client 2 to n-->>MCData server: 5. MCData group session standalone data response + MCData server-->>MCData client 1: 6. MCData group session standalone data response + Note left of MCData server: 7. Data transmission + Note right of MCData server: 8. Data transmission + Note right of MCData client 2 to n: 9. Process payload + MCData client 2 to n-->>MCData server: 10. MCData data disposition notification + MCData client 2 to n-->>MCData server: 11. MCData data disposition notification + Note right of MCData server: 12. Aggregate notifications + MCData server-->>MCData client 1: 13. MCData [aggregated] data disposition notification(s) + +``` + +Sequence diagram for Group standalone SDS using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows the initiation of a data request, group session setup, data transmission, and disposition notifications. + +**Figure 7.4.2.6.2-1: Group standalone SDS using media plane** + +1. User at MCData client 1 would like to initiate a SDS data transfer request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group session standalone data request towards the MCData server. The MCData group session standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData session group standalone data request contains conversation identifier for message thread indication. The MCData session group standalone data request may include additional implementation specific information in the application metadata container. The MCData session group standalone data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency short data service communication or the MCData emergency state is already set for MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group session standalone data request shall contain an emergency indicator; +- ii) the MCData group session standalone data request shall set the alert indicator if configured to send an MCData emergency alert while initiating an MCData standalone data request for the emergency short data service communication; +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCPTT emergency state is retained until explicitly cancelled; and +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled. + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group session standalone data request shall contain an imminent peril indicator; and + - ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled. +- 2a. If either an emergency indicator or an imminent peril indicator is present in received MCData group session standalone data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData session group standalone data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. + - i) if an emergency indicator is present in the received MCData group session standalone data request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; and + - ii) if an imminent peril indicator is present in the received MCData group session standalone data request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled. +- 3a. The MCData server configures the priority of the underlying bearers for all participants in the MCData group. +4. MCData server initiates the MCData group session standalone data request towards each MCData user determined in Step 3. The MCData ID list shall not be included in a unicast downlink delivery to an individual MCData client. The Disposition Type IE shall not be included in a unicast downlink delivery to MCData clients who are not in the MCData ID list in step 2. The MCData group session standalone data request towards each MCData client contains: + - i) an emergency indicator, if it is present in the received MCData group session standalone data request from the MCData client 1; + - ii) an imminent peril indicator, if it is present in the received MCData group session standalone data request from the MCData client 1; and + - iii) an alert indicator, if requested to initiate an emergency alert in the received MCData group session standalone data request from MCData client 1. +5. The receiving MCData clients 2 to n automatically accepts the MCData group session standalone data request and responds with MCData group standalone data response towards MCData server. +6. MCData server forwards the MCData clients 2 to n accepted response to the MCData user initiating the MCData group session standalone data request. + +NOTE 1: Step 6 can occur at any time following step 4, and prior to step 7 depending on the conditions to proceed with the data transmission. + +7. MCData client 1 and MCData server have successfully established media plane for data communication and the MCData client 1 transmits the SDS data. +8. MCData server distributes the data received from MCData client 1 to MCData clients 2 to n over the established media plane. After completion of the MCData transfer from MCData client 1, media plane resources associated to the data communication are released. + +NOTE 2: MCData server is not required to wait for the complete reception of SDS data from MCData client 1 prior to initiating transmission to MCData client 2 to n. + +9. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. + +Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +10. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report. +11. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +NOTE 3: On receiving MCData group standalone data request over MBMS, the receiving MCData client(s) shall check if the MCData ID list IE is included the receiving MCData client shall check if its own MCData ID is in the list. If not, step 6 and 7 are not required. + +12. The MCData data disposition notification(s) from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification(s) from each MCData user may be aggregated. +13. Aggregated or individual MCData data disposition notification(s) is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.7 Group short data service session + +##### 7.4.2.7.1 General + +The initiation of a group SDS to a selected group results in affiliated group members exchanging SDS data. + +##### 7.4.2.7.2 Procedure + +The procedure in figure 7.4.2.7.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData group for exchanging SDS data transactions between the group participants, with or without disposition request, using MCData-SDS-1 and MCData-SDS-2 reference points. + +Pre-conditions: + +1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group SDS session showing interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group data request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 3a. Bearer priority configuration + MCData server->>MCData client 2 to n: 4. MCData group data request + Note right of MCData client 2 to n: 5. Notify request + MCData client 2 to n->>MCData server: 6. MCData group data response + MCData server->>MCData client 1: 7. MCData group data response + Note right of MCData client 1: 8. Data transmission + Note right of MCData client 1: 9. Disposition notifications + Note right of MCData client 1: 10. Session data termination + +``` + +Sequence diagram for Group SDS session showing interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. + +**Figure 7.4.2.7.2-1: Group SDS session** + +1. User at MCData client 1 would like to initiate a SDS group data transfer request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group data request towards the MCData server. The MCData group data request contains MCData group ID as selected by the user at MCData client 1. The MCData session data request contains conversation identifier for message thread indication. The MCData group data request may include additional implementation specific information in the application metadata container. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency short data service communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group data request shall contain an emergency indicator; +- ii) the MCData group data request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData standalone data request for the emergency short data service communication; and +- iii) if MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCPTT emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group data request shall contain an imminent peril indicator. + +- 2a. If either emergency indicator or imminent peril indicator is present in received MCData group data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. + - i) if an emergency indicator is present in the received MCData group data request and if MCData group is not in in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; +- NOTE 2: While the MCData group is in the in-progress emergency state, all types of MCData communications within the group are processed as emergency group communications by the MCData server. MCData group members that are not in the emergency state do not indicate emergency in group communication requests. +- ii) if an imminent peril indicator is present in the received MCData group data request and if the MCData group is not in the in-progress imminent peril, the MCData group is considered to be in the in-progress imminent peril state until cancelled; + - 3a. The MCData server configures the priority of the underlying bearers for all participants in the MCData group. + 4. MCData server initiates the MCData group data request towards each MCData user determined in Step 3. The MCData group data request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group data request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group data request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group data request from MCData client 1; + 5. The receiving MCData clients 2 to n optionally notify the user about the incoming MCData session data request. + 6. The receiving MCData client 2 to n accept or reject the MCData group data request and the corresponding result is in the MCData group data response towards MCData server. + +7. MCData server forwards the MCData group data response received from MCData client 2 to n to the MCData user initiating the MCData session data request. + +NOTE 3: Step 7 can occur at any time following step 4, and prior to step 8 depending on the conditions to proceed with the data transmission. + +8. MCData client 1 and the MCData group data request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified. + 9. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users. +10. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released. + +#### **7.4.2.8 One-to-one SDS communication upgrade to an emergency one-to-one SDS communication** + +##### **7.4.2.8.1 General** + +This clause is for adding procedures related to upgrading an existing MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. + +##### **7.4.2.8.2 Procedure** + +The procedure in figure 7.4.2.8.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. This procedure is applicable only when MCData one-to-one SDS communication is established as described in subclause 7.4.2.3 "One-to-one standalone short data service using media plane" or as described in subclause 7.4.2.4 "One-to-one short data service session". + +Pre-conditions: + +1. Both members of the MCData one-to-one SDS communication belong to the same MCData system. +2. MCdata one-to-one SDS communication is already in progress. + +![Sequence diagram showing the upgrade of an MCData one-to-one SDS session to an emergency one-to-one SDS session. The diagram involves three lifelines: MCData client 1, MCData server, and MCData client 2, all under the 'Home MCData service provider'. The process starts with a session in progress, followed by an emergency initiation at client 1, upgrade requests to the server and client 2, a notification to client 2, and subsequent responses and bearer priority adjustments leading to an upgraded session.](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note over MCData client 1, MCData server, MCData client 2: Home MCData service provider + Note over MCData client 1, MCData server, MCData client 2: MCData one-to-one SDS session is in progress + MCData client 1->>MCData server: 1. initiate emergency communication + MCData client 1->>MCData server: 2. MCData one-to-one SDS communication upgrade request + MCData server->>MCData client 2: 3. MCData one-to-one SDS communication upgrade request + MCData server->>MCData client 2: 4. Notify emergency communication + MCData client 2->>MCData server: 5. MCData one-to-one SDS communication upgrade response + MCData server->>MCData server: 6. Bearer priority adjustment + MCData server->>MCData client 1: 7. MCData one-to-one SDS communication upgrade response + Note over MCData client 1, MCData server, MCData client 2: 8. MCData one-to-one SDS session over upgraded bearer + +``` + +Sequence diagram showing the upgrade of an MCData one-to-one SDS session to an emergency one-to-one SDS session. The diagram involves three lifelines: MCData client 1, MCData server, and MCData client 2, all under the 'Home MCData service provider'. The process starts with a session in progress, followed by an emergency initiation at client 1, upgrade requests to the server and client 2, a notification to client 2, and subsequent responses and bearer priority adjustments leading to an upgraded session. + +**Figure 7.4.2.8.2-1 MCData one-to-one SDS communication upgraded to MCData emergency one-to-one SDS communication** + +1. The MCData user at MCData client 1 initiates an emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +2. MCData client 1 requests the MCData server to upgrade the one-to-one MCData SDS communication to in-progress emergency by sending a MCData one-to-one SDS communication upgrade request. +3. The MCData server sends the MCData one-to-one SDS communication upgrade request towards MCData client 2, the MCData client of the other participant. + +NOTE 2: MCData client 2 does not set its emergency state as a result of receiving the MCData one-to-one SDS communication upgrade request containing the emergency indicator. + +4. The MCData user is notified of the in-progress emergency of the MCData emergency one-to-one SDS communication. +5. The receiving MCData client acknowledges the MCData one-to-one SDS communication upgrade request and sends MCData one-to-one SDS communication upgrade response to the MCData server. +6. The MCData server adjusts the priority of the underlying bearer for both participants of the MCData one-to-one SDS communication. The priority is retained until the communication session ends. +7. The MCData server sends MCData one-to-one SDS communication upgrade response to MCData client 1. +8. MCData client 1 and MCData client 2 continue with the MCData one-to-one SDS communication, which has been transformed into an MCData emergency one-to-one SDS communication. + +#### 7.4.2.9 Group SDS communication upgrade to a group emergency SDS communication + +##### 7.4.2.9.1 General + +This clause is for adding procedures related to upgrading an existing MCData group SDS communication to an MCData emergency group SDS communication. + +##### 7.4.2.9.2 Procedure + +The procedure in figure 7.4.2.9.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData group SDS communication to an MCData emergency group SDS communication. This procedure is applicable only when group MCData communication is established as described in subclause 7.4.2.6 "Group standalone short data service using media plane" or as described in subclause 7.4.2.7 "Group short data service session". + +NOTE 1: For simplicity, a single MCData server is shown in place of a user home MCData server and a group hosting MCData server. + +##### Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. MCData group SDS communication is already in progress. +4. The initiating MCData client 1 has been configured to send an MCData emergency alert when upgrading an MCData emergency group communication. + +![Sequence diagram showing the upgrade of MCData group SDS communication to an emergency state. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client 3. The process involves initiating an emergency, requesting an upgrade, adjusting bearer priority, notifying clients, and receiving responses.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` + +sequenceDiagram + participant MC1 as MCData client 1 + participant MS as MCData server + participant MC2 as MCData client 2 + participant MC3 as MCData client 3 + + Note over MC1, MC3: Home MCData service provider + + Note over MC1, MC3: MCData group SDS communication is in progress + + MC1->>MS: 1. Initiate group emergency + Note over MC1: 1. Initiate group emergency + MC1->>MS: 2. MCData group SDS communication upgrade request + Note over MS: 3. Bearer priority adjustment + MS->>MC2: 4. MCData group SDS communication upgrade request + MS->>MC3: 4. MCData group SDS communication upgrade request + Note over MC2: 5. Notify group emergency status + Note over MC3: 5. Notify group emergency status + MC2-->>MS: 6. MCData group SDS communication upgrade response + MC3-->>MS: 6. MCData group SDS communication upgrade response + MS-->>MC1: 7. MCData group SDS communication upgrade response + Note over MC1: 7. MCData group SDS communication upgrade response + + Note over MC1, MC3: MCData group SDS communication over upgraded bearer + +``` + +Sequence diagram showing the upgrade of MCData group SDS communication to an emergency state. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client 3. The process involves initiating an emergency, requesting an upgrade, adjusting bearer priority, notifying clients, and receiving responses. + +**Figure 7.4.2.9.2-1: MCData group SDS communication upgraded to MCData emergency group SDS communication** + +1. The MCData user at MCData client 1 initiates a group emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 2: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +2. MCData client 1 requests the MCData server to upgrade the MCData group to an in-progress emergency state by sending a MCData group SDS communication upgrade request. The MCData client 1 sets the emergency indicator in the request. If configured to send an MCData alert when initiating an MCData emergency group SDS upgrade, the request also contains an indication that an MCData alert is to be initiated. + +3. The MCData server sets the emergency state of the MCData group and adjusts the priority of the underlying bearer for all or selected participants in the MCData group SDS communication that receive the communication over unicast. + +NOTE 3: The determination of the selected participants whose bearers have to be upgraded is left to implementation. + +NOTE 4: While the MCData group is in the in-progress emergency state, all types of MCData communications within the group are processed as emergency group communications by the MCData server. MCData group members that are not in the emergency state do not indicate emergency in group communication requests. + +4. MCData server sends the MCData group SDS communication upgrade request towards the MCData clients of each of those affiliated MCData group members. The request contains an indication of an MCData emergency alert if the request from the originator indicated MCData emergency alert. + +5. MCData users are notified of the in-progress emergency state of the MCData group. +6. The receiving MCData clients send the MCData group SDS communication upgrade response to the MCData server to acknowledge the MCData group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCData server sends the MCData group SDS communication upgrade response to the MCData user 1 to confirm the upgrade request. + +NOTE 5: Step 7 can occur at any time following step 3, depending on the conditions to proceed with the call. + +MCData client 1, MCData client 2 and MCData client 3 continue with the MCData group SDS communication, which has been transformed into an MCData emergency group SDS communication. + +#### 7.4.2.10 Group SDS communication in-progress emergency group state cancel + +##### 7.4.2.10.1 General + +This clause describes procedures related to MCData in-progress emergency group state cancel. The emergency state of the group can also be cancelled by the group FD in-progress emergency state cancellation procedure in subclause 7.5.2.13.2, or by the emergency alert cancellation procedure specified in 3GPP TS 23.280 [16], subclause 10.10.1.2.2.2. + +##### 7.4.2.10.2 Procedure + +The procedure in figure 7.4.2.10.2-1 describes the case where an authorized MCData user cancels MCData group's in-progress emergency. + +Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. MCData group members have been notified about the in-progress emergency. +4. The MCData group is in the in-progress emergency state and has prioritized bearer support. +5. MCData client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram titled 'Home MCData service provider' showing the interaction for canceling an emergency group state. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The process starts with a state change to 'in progress', followed by a cancel request from client 1 to the server, a priority adjustment, a request from the server to clients 2 and 3, notifications to clients 2 and 3, responses from clients 2 and 3 to the server, and finally a response from the server to client 1, returning to a 'communication continues' state.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + + Note over MCData client 1, MCData client 3: MCData group SDS emergency communication is in progress + + MCData client 1->>MCData server: 1. Initiate in-progress emergency group state cancel + MCData client 1->>MCData server: 2. MCData group SDS in-progress priority state cancel request + Note over MCData server: 3. Bearer priority adjustment + MCData server->>MCData client 2: 4. MCData group SDS in-progress priority state cancel request + MCData server->>MCData client 3: 4. MCData group SDS in-progress priority state cancel request + Note over MCData client 2: 5. Notify emergency cancel + Note over MCData client 3: 5. Notify emergency cancel + MCData client 2-->>MCData server: 6. MCData group SDS in-progress priority state cancel response + MCData client 3-->>MCData server: 6. MCData group SDS in-progress priority state cancel response + MCData server-->>MCData client 1: 7. MCData group SDS in-progress priority state cancel response + + Note over MCData client 1, MCData client 3: MCData group SDS communication continues + +``` + +Sequence diagram titled 'Home MCData service provider' showing the interaction for canceling an emergency group state. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The process starts with a state change to 'in progress', followed by a cancel request from client 1 to the server, a priority adjustment, a request from the server to clients 2 and 3, notifications to clients 2 and 3, responses from clients 2 and 3 to the server, and finally a response from the server to client 1, returning to a 'communication continues' state. + +**Figure 7.4.2.10.2-1: MCData group SDS in-progress emergency group state cancel** + +1. The user at the MCData client 1 initiates an MCData group SDS in-progress emergency group state cancel. + +NOTE 1: An MCData user authorized to cancel in-progress emergencies on the MCData group can also be authorised to cancel the MCData emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCData emergency state. + +2. The MCData client 1 sends an MCData group SDS communication in-progress priority state cancel request to the MCData server. The MCData client 1 also resets the emergency indicator in the request to inform MCData server about cancellation of in-progress emergency group state. + +NOTE 2: If an MCData emergency alert relating to MCData client 1 is in effect together with an MCData in-progress emergency group state on the MCData group, the MCData emergency alert of MCData client 1 can be cancelled at the same time. In that case, the MCData group SDS in-progress priority group state cancel request carries an indication that the emergency alert of MCData client 1 is also being cancelled. + +NOTE 3: If an MCData group SDS communication in-progress priority state cancel request is received by the MCData server while a group member that is in the emergency state is transmitting, the MCData group SDS communication in-progress priority state cancel request is rejected by the MCData server. + +3. The MCData server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCData server cancels/resets the emergency in-progress state of the MCData group. +4. The MCData server sends an MCData group SDS in-progress priority state cancel request to the MCData group members. +5. MCData group members are notified of the MCData group SDS in-progress emergency state cancel. + +6. The receiving MCData clients send the MCData group SDS in-progress priority state cancel response to the MCData server to acknowledge the MCData in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. +7. The MCData server sends the MCData group SDS in-progress priority state cancel response to the MCData user 1 to confirm the MCData in-progress emergency group state cancel. If the MCData in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCData client 1 resets its local emergency status. + +NOTE 4: Step 7 can occur at any time following step 3, depending on the conditions to proceed with the call. + +#### 7.4.2.11 Group SDS communication upgrade to an imminent peril group SDS communication + +##### 7.4.2.11.1 General + +This clause is for adding procedures related to upgrade to an imminent peril group SDS communication. + +##### 7.4.2.11.2 Procedure + +This procedure is applicable only when group MCData SDS communication is established as described in subclause 7.4.2.6 "Group standalone short data service using media plane" or as described in subclause 7.4.2.7 "Group short data service session". The MCData service shall support the procedures and related information flows as specified in subclause 7.4.2.9 "Group SDS communication upgrade to a group SDS emergency communication" with the following clarifications: + +- In step 2), the MCData client 1 sets the imminent peril indicator; +- In step 3), the bearers' priority is adjusted as necessary, to correspond to an imminent peril priority which could be different than the setting used in the procedure in subclause 7.4.2.9; and +- In step 5), MCData users are notified of the in-progress imminent peril state of the MCData group. + +#### 7.4.2.12 Group SDS communication in-progress imminent peril group state cancel + +##### 7.4.2.12.1 General + +This clause is for adding procedures related to group SDS communication in-progress imminent peril group state cancel. + +##### 7.4.2.12.2 Procedure + +The MCData service shall support the procedures and related information flows as specified in subclause 7.4.2.10 "Group SDS communication in-progress emergency group state cancel" with the following clarifications: + +- In step 2), the MCData client 1 sets imminent peril indicator; and +- In step 5), MCData users are notified of the group SDS communication in-progress imminent peril state cancel. + +#### 7.4.2.13 Providing data for a user entering an ongoing MCData group conversation + +##### 7.4.2.13.1 General + +The MCData service shall support mechanisms that allow a MCData user be presented with the whole content of a group conversation in a group that he is a member of. This includes the content (messages) exchanged before the MCData user joins the group conversation. + +##### 7.4.2.13.2 Procedure + +Figure 7.4.2.13.2-1 describes procedures for a MCData user joining late a group conversation. + +Pre-conditions: + +1. The MCData group is provisioned for lossless communication. +2. All members of the MCData group have an account created in the MCData message store. +3. MCData client 1, MCData client 2 and MCData client 3 are members of the same MCData group, +4. MCData client 1 and 2 are served by MCData server 1 and have registered and affiliated to the MCData group. +5. MCData client 3 is served by MCData server 2 and has not affiliated to the MCData group yet. + +NOTE 1: The interactions of MCData client 1 and MCData client 2 to MCData message store are not shown in the figure. + +![Sequence diagram showing the interaction for providing data for a user entering an ongoing MCData group conversation. Lifelines: MCData Client 1, MCData Server 1, MCData Client 2, MCData server 2, MCData message store, MCData Client 3. The sequence of messages is: 1. Initiate a data group conversation (from Client 1/2 to Server 1/2), 2. The media plane is established (between Server 1/2), 3. Deposit objects (from Server 2 to Message Store), 4. Affiliate to the group (from Client 3 to Message Store), 5. Synchronization (between Client 3 and Message Store), 6. Invite to the group conversation (from Server 2 to Client 3), 7. Group conversations (ongoing interaction between all participants).](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +sequenceDiagram + participant MCData Client 1 + participant MCData Server 1 + participant MCData Client 2 + participant MCData server 2 + participant MCData message store + participant MCData Client 3 + + Note over MCData Client 1, MCData Server 1: 1. Initiate a data group conversation + Note over MCData Client 2, MCData server 2: 2. The media plane is established + Note over MCData server 2, MCData message store: 3. Deposit objects + Note over MCData Client 3, MCData message store: 4.. Affiliate to the group + Note over MCData Client 3, MCData message store: 5. Synchronization + Note over MCData server 2, MCData Client 3: 6. Invite to the group conversation + Note over MCData Client 1, MCData Client 2, MCData server 2, MCData Client 3: 7. Group conversations + +``` + +Sequence diagram showing the interaction for providing data for a user entering an ongoing MCData group conversation. Lifelines: MCData Client 1, MCData Server 1, MCData Client 2, MCData server 2, MCData message store, MCData Client 3. The sequence of messages is: 1. Initiate a data group conversation (from Client 1/2 to Server 1/2), 2. The media plane is established (between Server 1/2), 3. Deposit objects (from Server 2 to Message Store), 4. Affiliate to the group (from Client 3 to Message Store), 5. Synchronization (between Client 3 and Message Store), 6. Invite to the group conversation (from Server 2 to Client 3), 7. Group conversations (ongoing interaction between all participants). + +**Figure 7.4.2.13.2-1: Providing data for a user entering an ongoing MCData group conversation** + +1. A group conversation is initiated according to procedures in subclause 7.4.2.6, and all members of the group are invited into the communication whether affiliated or not. As MCData user 3 is not affiliated at this time, MCData server 2 accepts the invitation to the group conversation on behalf of MCData user 3. + +2. The media plane is established for the group conversation. MCData server 2 is in the media plane to receive the conversation on behalf of MCData user 3. + +3. MCData server 2 stores the received conversation to MCData user 3 account in the MCData message store. + +NOTE 2: If the received conversation requests delivery notification the MCData server 2 will send message delivered to the message sender. If the received conversation requests read notification the MCData client 3 will send message read to the message sender once it has presented the message to the user. + +4. MCData user 3 is online and using MCData client 3 to affiliate to the MCData group. + +5. MCData client 3, through the message store client, synchronizes with the MCData user 3 account in the MCData message store. + +6. MCData server 2 invites MCData client 3 to the MCData group conversation. + +7. MCData user 3 joins the MCData group conversation. + +### 7.4.3 Short data service for off-network + +#### 7.4.3.1 General + +Off-network SDS communications are based on ProSe capabilities as described in clause 7.16. + +#### 7.4.3.2 Information flows for short data service + +##### 7.4.3.2.1 MCData standalone data request + +Table 7.4.3.2.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to another MCData client. + +**Table 7.4.3.2.1-1: MCData standalone data request** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Date and Time | M | Date and time of transmission | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Emergency indicator (see NOTE 1) | O | Indicates that the MCData communication is an MCData emergency communication | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Payload | M | SDS content | +| NOTE 1: This information element shall be included for the MCData emergency communication.
NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +##### 7.4.3.2.2 MCData data disposition notification + +Table 7.4.3.2.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to another MCData client. + +**Table 7.4.3.2.2-1: MCData data disposition notification** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition | M | Disposition which is delivered or read or both | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | + +##### 7.4.3.2.3 MCData group standalone data request + +Table 7.4.3.2.3-1 describes the information flow for the MCData group standalone data request sent from the MCData client to another MCData client. + +**Table 7.4.3.2.3-1: MCData group standalone data request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Date and Time | M | Date and time of transmission | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Emergency indicator (see NOTE 1) | O | Indicates that the MCData communication is an MCData emergency communication | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the MCData communication is an MCData imminent peril communication | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Payload | M | SDS content | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +#### 7.4.3.3 One-to-one standalone short data service using signalling control plane + +##### 7.4.3.3.1 General + +This subclause describes the detailed procedures for the scenario where SDS data is to be sent to MCData user in off-network. + +##### 7.4.3.3.2 Procedure + +Figure 7.4.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone SDS data to other MCData client, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS data size is assumed to be pre-configured. + +Pre-conditions: + +1. MCData user 1 has initiated communication for sending standalone SDS data to other MCData user 2. +2. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable. +3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using ProSe Discovery procedures. + +![Sequence diagram illustrating the one-to-one standalone short data service using signalling control plane. The diagram shows two lifelines: MCData client 1 and MCData client 2. The sequence of messages is: 1. Check authorization (internal to MCData client 1), 2. MCData standalone data request (from MCData client 1 to MCData client 2), 3. Assert policy (internal to MCData client 2), 4. Process payload (internal to MCData client 2), 5. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1), and 6. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note left of MCData client 1: 1. Check authorization + MCData client 1->>MCData client 2: 2. MCData standalone data request + Note right of MCData client 2: 3. Assert policy + Note right of MCData client 2: 4. Process payload + MCData client 2-->>MCData client 1: 5. MCData data disposition notification + MCData client 2-->>MCData client 1: 6. MCData data disposition notification + +``` + +Sequence diagram illustrating the one-to-one standalone short data service using signalling control plane. The diagram shows two lifelines: MCData client 1 and MCData client 2. The sequence of messages is: 1. Check authorization (internal to MCData client 1), 2. MCData standalone data request (from MCData client 1 to MCData client 2), 3. Assert policy (internal to MCData client 2), 4. Process payload (internal to MCData client 2), 5. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1), and 6. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1). + +**Figure 7.4.3.3.2-1: One-to-one standalone short data service using signalling control plane** + +1. MCData client 1 checks whether the MCData user 1 is authorized to send MCData standalone data request. +2. If MCData user 1 is authorised MCData client 1 sends a MCData standalone data request towards the MCData client 2. The MCData standalone data request contains conversation identifier for message thread indication. The MCData standalone data request may include additional implementation specific information in the application metadata container. The MCData standalone data request may contain disposition request if indicated by the user at MCData client 1. If MCData user at the MCData client 1 initiates an MCData emergency communication, then emergency indicator is included in the MCData standalone data request. If an MCData emergency state is not set already when MCData emergency communication is initiated, the MCData client 1 sets its MCData emergency state and is retained until explicitly cancelled. The value of ProSe Per Packet Priority is upgraded according to the state of the MCData communication. +3. On receiving a MCData standalone data request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. +4. If the policy assertion is positive and the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +NOTE: If the policy assertion was negative, the MCData client 2 sends an appropriate notification to MCData client 1. + +5. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client 2 initiates a MCData data disposition notification for delivery report. +6. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +#### 7.4.3.4 Group standalone short data service using signalling control plane + +##### 7.4.3.4.1 General + +The initiation of a group standalone SDS to a selected group results in off-network MCData group members receiving the SDS data. + +##### 7.4.3.4.2 Procedure + +Figure 7.4.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending SDS data to a MCData group, with or without disposition request. The SDS data size limit is pre-configured. + +Pre-conditions: + +1. MCData user 1 has initiated group communication for sending SDS data to the MCData group. +2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +3. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram illustrating the group standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. The process starts with MCData client 1 checking authorization, followed by a group standalone data request. Clients 2 to N then assert policy and process the payload. Finally, disposition notifications are sent from clients 2 to N back to client 1.](853f59c89931a666c07903b31d098277_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client N + Note left of MCData client 1: 1. Check authorization + MCData client 1->>MCData client N: 2. MCData group standalone data request + Note right of MCData client 2: 3. Assert policy + Note right of MCData client N: 3. Assert policy + Note right of MCData client 2: 4. Process payload + Note right of MCData client N: 4. Process payload + MCData client 2-->>MCData client 1: 5. MCData data disposition notification + MCData client N-->>MCData client 1: 5. MCData data disposition notification + MCData client 2-->>MCData client 1: 6. MCData data disposition notification + MCData client N-->>MCData client 1: 6. MCData data disposition notification + +``` + +Sequence diagram illustrating the group standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. The process starts with MCData client 1 checking authorization, followed by a group standalone data request. Clients 2 to N then assert policy and process the payload. Finally, disposition notifications are sent from clients 2 to N back to client 1. + +**Figure 7.4.3.4.2-1: Group standalone short data service using signalling control plane** + +1. MCData client 1 checks whether the MCData user 1 is authorized to send MCData group standalone data request. +2. If MCData user 1 is authorised MCData client 1 sends a MCData group standalone data request towards the MCData group. The MCData group standalone data request contains conversation identifier for message thread indication. The MCData group standalone data request may include additional implementation specific information in the application metadata container. The MCData group standalone data request may contain disposition request if indicated by the user at MCData client 1. If MCData group standalone data request contains disposition request, MCData group standalone data request shall also contain the IP address of the MCData client 1. If MCData user at the MCData client 1 initiates an MCData emergency communication, then the emergency indicator or the imminent peril indicator is included in the MCData standalone data request. If an MCData emergency state is not set already when MCData emergency communication is initiated, the MCData client 1 sets its MCData emergency state and is retained until explicitly cancelled. The value of ProSe Per Packet Priority is upgraded according to the state of the MCData communication. +3. On receiving a MCData group standalone data request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. +4. If the policy assertion is positive and the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData clients 2 to N which is addressed to a known local non-MCData application that is not yet running shall cause the MCData clients 2 to N to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +NOTE: If the policy assertion was negative, the MCData clients sends an appropriate notification to MCData client 1. + +5. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData clients initiate a MCData data disposition notification for delivery report. +6. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData clients 2 to N initiate a MCData data disposition notification for read report. + +#### 7.4.3.5 Void + +#### 7.4.3.6 Group standalone short data service with MCData message store + +##### 7.4.3.6.1 General + +A MCData user's off-network communication needs to be part of his communication history when the MCData user has an account in the MCData message store. + +##### 7.4.3.6.2 Procedure + +Figure 7.4.3.6.2-1 describes procedures of a MCData user, MCData user 2, that has an account in MCData message store and how his off-network SDS group communication is stored in his account in the MCData message store. All other MCData clients in the figure follow the procedures described in subclause 7.4.3.4. + +Pre-conditions: + +1. MCData user 1 to N are in an off-network group communication. +2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured to MCData client 1 to N. +3. MCData client 1 to N are members of the same MCData group. +4. MCData user 2 has an account in the MCData message store. + +![Sequence diagram illustrating the Group standalone short data service with MCData message store. The diagram shows five steps: 1. Off-network SDS group communication, 2. Store object, 3. Off-network SDS group communication ends, 4. MCData user 2 connects to network, 5. Upload objects to MCData message store. Lifelines include MCData client 1, MCData client 2, Message store client 2, MCData client N, and MCData message store.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant Message store client 2 + participant MCData client N + participant MCData message store + + Note over MCData client 1, MCData client N: 1. Off-network SDS group communication + Note over MCData client 2, Message store client 2: 2. Store object + Note over MCData client 1, MCData client N: 3. Off-network SDS group communication ends + Note over MCData client 2: 4. MCData user 2 connects to network + Note over Message store client 2, MCData message store: 5. Upload objects to MCData message store +``` + +Sequence diagram illustrating the Group standalone short data service with MCData message store. The diagram shows five steps: 1. Off-network SDS group communication, 2. Store object, 3. Off-network SDS group communication ends, 4. MCData user 2 connects to network, 5. Upload objects to MCData message store. Lifelines include MCData client 1, MCData client 2, Message store client 2, MCData client N, and MCData message store. + +Figure 7.4.3.6.2-1: Group standalone short data service with MCData message store + +1. MCData client 1 to MCData client N are in an off-network group communication according to the procedures in subclause 7.4.3.4, SDS are exchanged among all MCData clients. +2. If the SDS is for MCData user consumption, the SDS is stored in the local message store on the MCData UE of MCData user 2. + +NOTE: A pre-configured folder for off-network communication objects can be provisioned both on the UE and the user account on the MCData message store to be used for synchronization. + +3. The off-network group communication comes to an end. +4. The MCData user 2 connects back to the network. +5. The MCData user 2 decides to keep the off-network communication in his account on the MCData message store. The message store client 2 uploads the off-network communication objects from the local message store to the MCData message store. + +## 7.5 File distribution + +### 7.5.1 General + +File distribution (mandatory and non-mandatory download) is enabled for both one-to-one and group. + +### 7.5.2 File distribution for on-network + +#### 7.5.2.1 Information flows for file distribution + +##### 7.5.2.1.1 MCData upload data request + +Table 7.5.2.1.1-1 describes the information flow for the MCData upload data request sent from the media storage client to the MCData content server. + +**Table 7.5.2.1.1-1: MCData upload data request** + +| Information element | Status | Description | +|--------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| Content (see NOTE) | O | Content to upload | +| Content reference (see NOTE) | O | URL reference of the content stored in the MCData message store account of the MCData user | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| NOTE: Either the Content or the Content reference must be present. | | | + +##### 7.5.2.1.2 MCData upload data response + +Table 7.5.2.1.2-1 describes the information flow for the MCData upload data response sent from the MCData content server to the media storage client. + +**Table 7.5.2.1.2-1: MCData upload data response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| Upload confirmation | M | An indication whether the upload to the content storage is successful or not | +| Content reference | O | URL reference of the content stored (see NOTE). | +| NOTE: Content reference shall be present when the upload confirmation is successful. | | | + +##### 7.5.2.1.3 MCData download data request + +Table 7.5.2.1.3-1 describes the information flow for the MCData download data request sent from the MCData media storage client to the MCData content server. + +**Table 7.5.2.1.3-1: MCData download data request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user downloading data | +| Content reference | M | URL reference to the content to download | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +##### 7.5.2.1.4 MCData download data response + +Table 7.5.2.1.4-1 describes the information flow for the MCData download data response sent from the MCData content server to the media storage client. + +**Table 7.5.2.1.4-1: MCData download data response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to download data | +| Content (see NOTE) | O | Requested content to download | +| Result | M | Indicates success or failure of MCData download data request | +| NOTE: Content shall be present when the result of the MCData download data request indicates success. | | | + +##### 7.5.2.1.5 MCData FD request (using HTTP) + +Table 7.5.2.1.5-1 describes the information flow for the MCData FD request (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server. + +**Table 7.5.2.1.5-1: MCData FD request (using HTTP) from MCData client to MCData server** + +| Information element | Status | Description | +|---------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The functional alias associated with MCData user sending the file | +| MCData ID (see NOTE) | O | The identity of the MCData user receiving the file | +| Functional alias (see NOTE) | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Deposit file indication | O | Indicates whether the file to be stored into the MCData message store account of the MCData user | +| NOTE: Either the MCData ID or the functional alias must be present. | | | + +Table 7.5.2.1.5-2 describes the information flow for the MCData FD request (in clause 7.5.2.4.2) sent from an MCData server to a partner MCData server. + +**Table 7.5.2.1.5-2: MCData FD request (using HTTP) from an MCData server to MCData server** + +| Information element | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The associated functional alias of the MCData user identity sending the file | +| MCData ID | M | The identity of the MCData user receiving the file | +| Functional alias | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +Table 7.5.2.1.5-3 describes the information flow for the MCData FD request (in clause 7.5.2.4.2) sent from the MCData server to the MCData client. + +**Table 7.5.2.1.5-3: MCData FD request (using HTTP) from MCData server to MCData client** + +| Information element | Status | Description | +|--------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The associated functional alias of the MCData user sending the file | +| MCData ID | M | The identity of the MCData user receiving the file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +##### 7.5.2.1.6 MCData FD response (using HTTP) + +Table 7.5.2.1.6-1 describes the information flow for the MCData FD response (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server. + +**Table 7.5.2.1.6-1: MCData FD response (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Result | O | Indicates if the request is accepted or not | + +##### 7.5.2.1.7 MCData download completed report + +Table 7.5.2.1.7-1 describes the information flow for the MCData download completed report sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server. + +**Table 7.5.2.1.7-1: MCData download completed report** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition confirmation | M | An indication that the client has completed downloading file | + +##### 7.5.2.1.7A MCData aggregated download completed report + +Table 7.5.2.1.7A-1 describes the information flow for the MCData aggregated download completed report sent from the MCData server to the MCData client, indicating the result of a request for a file delivery to an MCData group. + +**Table 7.5.2.1.7A-1: MCData aggregated download completed report** + +| Information element | Status | Description | +|----------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user that sent the FD request | +| Number of Aggregated Reports | M | Total number of received individual completed reports | +| Number of Successful Deliveries | O | Number of received individual completed reports indicating success | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | M | Identifies the original MCData transaction which the current transaction is a reply to | +| Successful MCData ID list | O
(NOTE) | List, partial or full, of MCData users who successfully received the file delivery | +| Unsuccessful MCData ID list | O
(NOTE) | List, partial or full, of MCData users who reported failure to fully receive the file delivery successfully | +| NOTE: No more than one of these information elements may be present. | | | + +##### 7.5.2.1.8 MCData FD request (using media plane) + +Table 7.5.2.1.8-1 describes the information flow for the MCData FD request (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.8-1: MCData FD request (using media plane/MCData client to MCData server)** + +| Information element | Status | Description | +|-----------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The functional alias associated with MCData user sending the file | +| MCData ID (see NOTE 1) | O | The identity of the MCData user receiving the file | +| Functional alias (see NOTE 1) | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE 2) | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| NOTE 1: Either the MCData ID or the functional alias must be present. | | | +| NOTE 2: Includes file metadata. | | | + +**Table 7.5.2.1.8-2: MCData FD request (using media plane/MCData server to MCData server)** + +| Information element | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The associated functional alias of the MCData user identity sending the file | +| MCData ID | M | The identity of the MCData user receiving the file | +| Functional alias | O | The associated functional alias of the MCData user identity towards which the data is sent. | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE) | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| NOTE: Includes file metadata. | | | + +**Table 7.5.2.1.8-3: MCData FD request (using media plane/MCData server to MCData client)** + +| Information element | Status | Description | +|--------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The associated functional alias of the MCData user identity sending the file | +| MCData ID | M | The identity of the MCData user receiving the file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE) | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| NOTE: Includes file metadata. | | | + +##### 7.5.2.1.9 MCData FD response (using media plane) + +Table 7.5.2.1.9-1 describes the information flow for the MCData FD response (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.9-1: MCData FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Establishment reason | O | Reason for establishment or rejection | + +##### 7.5.2.1.10 MCData group standalone FD request (using HTTP) + +Table 7.5.2.1.10-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server. + +**Table 7.5.2.1.10-1: MCData group standalone FD request (using HTTP) from MCData client to MCData server** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The functional alias associated with MCData user sending the file | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +Table 7.5.2.1.10-2 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.5.2.1.10-2: MCData group standalone FD request (using HTTP) from MCData server to MCData client** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The functional alias associated with MCData user sending the file | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user receiving the file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +##### 7.5.2.1.11 MCData group standalone FD response (using HTTP or MBMS download delivery method) + +Table 7.5.2.1.11-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.11-1: MCData group standalone FD response (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Result | M | Indicates if the request is accepted or not | + +##### 7.5.2.1.12 MCData group standalone FD request (using media plane) + +Table 7.5.2.1.12-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.7.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.12-1: MCData group standalone FD request (using media plane/MCData client to MCData server)** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The functional alias associated with MCData user sending the file | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE 3) | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: This information element may be present only when Emergency indicator is present.
NOTE 3: Includes file metadata. | | | + +**Table 7.5.2.1.12-2: MCData group standalone FD request (using media plane/MCData server to MCData client)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| Functional alias | O | The functional alias associated with MCData user sending the file | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user receiving the file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE 3) | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: Includes file metadata. | | | + +##### 7.5.2.1.13 MCData group standalone FD response (using media plane) + +Table 7.5.2.1.13-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.7.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.13-1: MCData group standalone FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +##### 7.5.2.1.14 MCData remove file request by user + +Table 7.5.2.1.14-1 describes the information flow for the MCData remove file request by user sent from the media storage client to the media storage function of the MCData content server, and from the MCData content server to another MCData content server in a partner MCData system. + +**Table 7.5.2.1.14-1: MCData remove file request by user** + +| Information element | Status | Description | +|---------------------------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID (see NOTE 1) | O | The identity of the MCData user removing file | +| Partner MCData system identity (see NOTE 2) | O | The identity of the partner MCData system where the file has also been downloaded | +| Content reference | M | URL of the content to be removed | + +NOTE 1: The identity of the MCData user removing the file is present when sent from MCData client to MCData content server + +NOTE 2: The identity of the partner MCData system is present when sent from MCData content server to MCData content server. + +##### 7.5.2.1.15 MCData remove file response by user + +Table 7.5.2.1.15-1 describes the information flow for the MCData remove file response by user sent from the media storage function of the MCData content server to the media storage client, and from the MCData content server to another MCData content server in a partner MCData system. + +**Table 7.5.2.1.15-1: MCData remove file response by user** + +| Information element | Status | Description | +|---------------------------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID (see NOTE 1) | O | The identity of the MCData user removing file | +| Partner MCData system identity (see NOTE 2) | O | The identity of the partner MCData system where the file has also been downloaded | +| Result | M | Indicates the success or failure of the file removal | + +NOTE 1: The identity of the MCData user removing the file is present when sent from MCData content server to MCData client + +NOTE 2: The identity of the partner MCData system is present when sent from MCData content server to MCData content server. + +##### 7.5.2.1.16 Void + +##### 7.5.2.1.17 Void + +##### 7.5.2.1.18 MCData remove file notify + +Table 7.5.2.1.18-1 describes the information flow for the MCData remove file notify sent from the MCData server to the MCData client that the shared file has been removed. + +**Table 7.5.2.1.18-1: MCData remove file notify** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploaded the file | +| Content reference | M | URL of the content that has been removed | +| Reason | O | The reason the file is removed | + +##### 7.5.2.1.19 MCData file retrieve request + +Table 7.5.2.1.19-1 describes the information flow for the MCData file retrieve request sent from an MCData content server in a partner MCData system to an MCData content server in the primary MCData system of the source of the content. + +**Table 7.5.2.1.19-1: MCData file retrieve request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------| +| Content reference | M | URL reference to the content to download | + +##### 7.5.2.1.20 MCData file retrieve response + +Table 7.5.2.1.20-1 describes the information flow for the MCData file retrieve response sent from the MCData content server in the primary MCData system of the source of the content to an MCData content server in a partner MCData system. + +**Table 7.5.2.1.20-1: MCData file retrieve response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------| +| Content (see NOTE) | O | Requested content to download | +| Result | M | Indicates success or failure of MCData download data request | +| NOTE: Content shall be present when the result of the MCData file retrieve request indicates success. | | | + +##### 7.5.2.1.21 MCData group standalone FD over MBMS request + +Table 7.5.2.1.21-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData server to another MCData client. + +**Table 7.5.2.1.21-1: MCData group standalone FD over MBMS request** + +| Information element | Status | Description | +|--------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | M | Indicates mandatory download | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| Content reference | M | URL reference to the content and file metadata information | +| MBMS user service id | M | Id of the MBMS user service delivering the file | +| MBMS content URI | M | URI upon which the content is delivered in the MBMS user service | + +##### 7.5.2.1.22 MCData one-to-one FD upgrade request + +Table 7.5.2.1.22-1 describes the information flow for the MCData one-to-one FD upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.22-1: MCData one-to-one FD upgrade request** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator | M | Indicates that the data request is for MCData emergency communication | + +##### 7.5.2.1.23 MCData one-to-one FD upgrade response + +Table 7.5.2.1.23-1 describes the information flow for the MCData one-to-one FD upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.23-1: MCData one-to-one FD upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| Conversation Identifier | M | Identifies the conversation | + +##### 7.5.2.1.24 MCData group FD upgrade request + +Table 7.5.2.1.24-1 describes the information flow for the MCData group FD upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.24-1: MCData group FD upgrade request (MCData client to MCData server)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the upgrade request | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +**Table 7.5.2.1.24-2: MCData group FD upgrade request (MCData server to MCData client)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the upgrade request | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| MCData ID | M | The identity of the MCData user receiving the upgrade request | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +##### 7.5.2.1.25 MCDATA group FD upgrade response + +Table 7.5.2.1.25-1 describes the information flow for the MCDATA group FD upgrade response sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.5.2.1.25-1: MCDATA group FD upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending data (when initiated by MCDATA client);
The identity of the MCDATA user receiving data (when initiated by MCDATA server). | +| MCDATA group ID | M | The MCDATA group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | + +##### 7.5.2.1.26 MCDATA group FD in-progress priority state cancel request + +Table 7.5.2.1.26-1 describes the information for the MCDATA group FD in-progress priority state cancel request sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.5.2.1.26-1: MCDATA group FD in-progress priority state cancel request (MCDATA client to MCDATA server)** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the cancelling MCDATA User | +| MCDATA group ID | M | The MCDATA group ID on which the MCDATA in-progress emergency state is to be cancelled. | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCDATA emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCDATA imminent peril communication | +| Conversation Identifier | M | Identifies the conversation | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +**Table 7.5.2.1.26-2: MCDATA group FD in-progress priority state cancel request (MCDATA server to MCDATA client)** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the cancelling MCDATA User | +| MCDATA group ID | M | The MCDATA group ID on which the MCDATA in-progress emergency state is to be cancelled. | +| MCDATA ID | M | The identity of the MCDATA user receiving the cancel request | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCDATA emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCDATA imminent peril communication | +| Conversation Identifier | M | Identifies the conversation | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +##### 7.5.2.1.27 MCDATA group FD in-progress priority state cancel response + +Table 7.5.2.1.27-1 describes the information flow for the MCDATA group FD in-progress priority state cancel response sent from the MCDATA server to the MCDATA client. + +**Table 7.5.2.1.27-1: MCData group FD in-progress priority state cancel response information elements** + +| Information Element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency in-progress is to be cancelled. | +| Conversation Identifier | M | Identifies the conversation | + +##### 7.5.2.1.28 MCData file upload request + +Table 7.5.2.1.28-1 describes the information flow for the MCData file upload request sent from the MCData client to the MCData server. + +**Table 7.5.2.1.28-1: MCData file upload request** + +| Information element | Status | Description | +|-----------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading the file | +| Transaction Identifier | M | Identifies the MCData transaction | +| Access information | M | Provides access resource details to be used by the MCData client for the file upload, e.g. IP address and port | +| MCData content server information | M | Provides information about the target MCData content server, where the file is intended to be uploaded, e.g. URI or IP address, and port (e.g. standard port 80 for HTTP) | +| Emergency indicator | O | Indicates that the request is for an MCData emergency communication | + +##### 7.5.2.1.29 MCData file upload response + +Table 7.5.2.1.29-1 describes the information flow for the MCData file upload response sent from the MCData server to the MCData client. + +**Table 7.5.2.1.29-1: MCData file upload response** + +| Information element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload the file | +| Transaction Identifier | M | Identifies the MCData transaction | +| File upload confirmation | M | Indicates whether the file upload to the MCData content server can proceed or not | + +##### 7.5.2.1.30 MCData file upload completion status + +Table 7.5.2.1.30-1 describes the information flow for the MCData file upload completion status sent from the MCData client to the MCData server. + +**Table 7.5.2.1.30-1: MCData file upload completion status** + +| Information element | Status | Description | +|------------------------|--------|---------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading the file | +| Transaction Identifier | M | Identifies the MCData transaction | +| File upload status | M | Indicates the file upload to the MCData content server is completed | + +##### 7.5.2.1.31 MCData file download request + +Table 7.5.2.1.31-1 describes the information flow for the MCData file download request sent from the MCData client to the MCData server. + +**Table 7.5.2.1.31-1: MCData file download request** + +| Information element | Status | Description | +|-----------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user downloading the file | +| Transaction Identifier | M | Identifies the MCData transaction | +| Access information | M | Provides access resource details to be used by the MCData client for the file download, e.g. IP address and port | +| MCData content server information | M | Provides information about the target MCData content server, where the file is intended to be downloaded from, e.g. URI or IP address, and port (e.g. standard port 80 for HTTP) | +| Content reference | M | URL reference to the content to download | +| Emergency indicator | O | Indicates that the request is for an MCData emergency communication | + +##### 7.5.2.1.32 MCData file download response + +Table 7.5.2.1.32-1 describes the information flow for the MCData file download response sent from the MCData server to the MCData client. + +**Table 7.5.2.1.32-1: MCData file download response** + +| Information element | Status | Description | +|----------------------------|--------|---------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to download the file | +| Transaction Identifier | M | Identifies the MCData transaction | +| File download confirmation | M | Indicates whether the file download from the MCData content server can proceed or not | + +##### 7.5.2.1.33 MCData file availability request + +Table 7.5.2.1.33-1 describes the information flow for the MCData file availability request sent from the MCData server to the MCData content server. + +**Table 7.5.2.1.33-1: MCData file availability request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------| +| Content reference | M | URL reference of the file required to check its availability in the MCData content server | + +##### 7.5.2.1.34 MCData file availability response + +Table 7.5.2.1.34-1 describes the information flow for the MCData file availability response sent from the MCData content server to the MCData server. + +**Table 7.5.2.1.34-1: MCData file availability response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------| +| Content reference | M | URL reference of the file required to check its availability in the MCData content server | +| Result | M | Indicates whether the file is available or not | + +#### 7.5.2.2 File upload using HTTP + +##### 7.5.2.2.1 General + +The media storage client uses HTTP for a standalone data file upload towards the MCData content server. + +##### 7.5.2.2.2 Procedure for uploading the file residing in the local storage of the MCData UE without QoS + +The procedure in figure 7.5.2.2.2-1 describes the case where an MCData user is uploading a file to media storage function on the MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. +2. The MCData content server has the ability to verify if the requesting MCData user is authorised to upload. + +![Sequence diagram showing the procedure for uploading a file from local storage. The Media storage client sends an 'initiate upload request' to the MCData content server. The MCData content server responds with an 'MCData upload data request' and then an 'MCData upload data response'.](55136bc716146672fc680fa05989f1d2_img.jpg) + +``` +sequenceDiagram + participant Media storage client + participant MCData content server + Note left of Media storage client: 1. initiate upload request + Media storage client->>MCData content server: 2. MCData upload data request + MCData content server-->>Media storage client: 3. MCData upload data response +``` + +Sequence diagram showing the procedure for uploading a file from local storage. The Media storage client sends an 'initiate upload request' to the MCData content server. The MCData content server responds with an 'MCData upload data request' and then an 'MCData upload data response'. + +**Figure 7.5.2.2.2-1: Uploading of the file residing in MCData UE using HTTP** + +1. The user at the media storage client initiates a file upload request of the chosen file. If MCData emergency state is already set for the media storage client (due to previously triggered MCData emergency alert), the media storage client sets emergency indicator in the request. The media storage client verifies that the size of the file is within the maximum data size for FD for the intended MCData FD request (by checking the group configuration for a group FD request and by checking the service configuration for a one-to-one FD request). +2. The file to be uploaded is received by the media storage client and sent to the media storage function on the MCData content server for storing using the MCData upload data request. +3. The MCData content server stores the file and provides a MCData upload data response indicating success (along with file URL to the media storage client) or failure. + +##### 7.5.2.2.3 Procedure for uploading the file residing in the MCData message store + +The procedure in figure 7.5.2.2.3-1 describes the case where an MCData user is uploading a file to media storage function on the MCData content server from his or her MCData message store account. + +Pre-conditions: + +1. The Media storage client knows the URL of the file residing in the MCData message store account of the user. + +![Sequence diagram showing the upload of a file from the MCData message store using HTTP. Lifelines: Media storage client, MCData Content Server, MCData Message Store. Steps: 1. Initiate upload request (client to server), 2. MCData upload data request (client to server), 3. Fetch file (server to message store), 4. Stores the file content in its repository (server internal), 5. MCData upload data response (server to client).](dd5771673aececa53d42ece89218299d_img.jpg) + +``` +sequenceDiagram + participant Client as Media storage client + participant Server as MCData Content Server + participant MessageStore as MCData Message Store + Note left of Client: 1.Initiate upload request + Client->>Server: 2.MCData upload data request + Note right of Server: 3.Fetch file + Server->>MessageStore: 3.Fetch file + Note right of MessageStore: 4.Stores the file content in its repository + MessageStore->>Server: 4.Stores the file content in its repository + Server->>Client: 5.MCData upload data response +``` + +Sequence diagram showing the upload of a file from the MCData message store using HTTP. Lifelines: Media storage client, MCData Content Server, MCData Message Store. Steps: 1. Initiate upload request (client to server), 2. MCData upload data request (client to server), 3. Fetch file (server to message store), 4. Stores the file content in its repository (server internal), 5. MCData upload data response (server to client). + +**Figure 7.5.2.2.3-1: Uploading of the file residing in MCData message store using HTTP** + +1. The user at the media storage client initiates a file upload request of the file residing in his MCData message store account. +2. The URL of the file which needs to be retrieved from the MCData message store account of the user is sent to the media storage function on the MCData content server using the MCData upload data request. +3. The MCData content server fetches the file from the MCData message store account of the user using the URL provided in the MCData upload data request. +4. The MCData content server stores the retrieved file content into its repository. +5. The MCData content provides a MCData upload data response indicating success (along with file URL to the media storage client) or failure. + +##### 7.5.2.2.4 Procedure for file upload including request of network resources with required QoS + +The procedure in figure 7.5.2.2.4-1 describes the case where an MCData client sends a request to the MCData server for the upload of a file from the media storage client on the MCData client to the media storage function on the MCData content server. The MCData server can, therefore, request network resources with the required QoS for the corresponding file upload. + +Pre-conditions: + +1. The MCData user on the MCData client is registered on the MCData server for receiving MCData service. +2. The MCData client is required to upload a file to the MCData content server over network resources with required QoS. +3. The MCData client knows its IP address/port to be used for the file upload as well as the URI or IP address/port of the target MCData content server. + +NOTE: How the MCData client knows the IP addresses and ports to be used for the file upload is implementation specific and out of the scope of this specification. + +![Sequence diagram illustrating the file upload process using HTTP over network resources with required QoS. The participants are MCData client, 3GPP system, MCData server, and MCData content server. The process involves 9 steps: 1. Initiate file upload request (MCData client to MCData server); 2. MCData file upload request (MCData client to MCData server); 3. Authorization check (MCData server to MCData server); 4. Request for dedicated resources with required QoS (PCC procedures) (MCData server to 3GPP system); 5. MCData file upload response (MCData server to MCData client); 6. MCData upload data request (MCData client to MCData content server); 7. MCData upload data response (MCData content server to MCData client); 8. MCData file upload completion status (MCData client to MCData server); 9. Release of dedicated resources (PCC procedures) (MCData server to 3GPP system).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant 3GPP system + participant MCData server + participant MCData content server + + Note left of MCData client: 1. Initiate file upload request + MCData client->>MCData server: 2. MCData file upload request + Note right of MCData server: 3. Authorization check + MCData server->>3GPP system: 4. Request for dedicated resources with required QoS (PCC procedures) + MCData server-->>MCData client: 5. MCData file upload response + MCData client->>MCData content server: 6. MCData upload data request + MCData content server-->>MCData client: 7. MCData upload data response + MCData client->>MCData server: 8. MCData file upload completion status + Note right of MCData server: 9. Release of dedicated resources (PCC procedures) + MCData server->>3GPP system: + +``` + +Sequence diagram illustrating the file upload process using HTTP over network resources with required QoS. The participants are MCData client, 3GPP system, MCData server, and MCData content server. The process involves 9 steps: 1. Initiate file upload request (MCData client to MCData server); 2. MCData file upload request (MCData client to MCData server); 3. Authorization check (MCData server to MCData server); 4. Request for dedicated resources with required QoS (PCC procedures) (MCData server to 3GPP system); 5. MCData file upload response (MCData server to MCData client); 6. MCData upload data request (MCData client to MCData content server); 7. MCData upload data response (MCData content server to MCData client); 8. MCData file upload completion status (MCData client to MCData server); 9. Release of dedicated resources (PCC procedures) (MCData server to 3GPP system). + +**Figure 7.5.2.2.4-1: File upload using HTTP over network resources with required QoS** + +1. The MC user on the MCData client intends to upload a file to the MCData content server for file distribution. The MCData client verifies that the size of the file is within the maximum data size for FD for the intended MCData FD request (e.g., by checking the group configuration for a group FD request or the service configuration for a one-to-one FD request). If the MCData emergency state is already set for the MCData client, the MCData client sets the emergency indicator in the request. +2. The MCData client sends the MCData file upload request to the MCData server. This request contains information about the MCData client (including IP address and port to be used for the file upload), and the target MCData content server (including associated URI or IP address, and port). +3. The MCData server verifies that the corresponding MCData client is authorized to upload files to the corresponding MCData content server. +4. If the MCData client is authorized for the file upload, the MCData server sends a request to the 3GPP system for the allocation of network resources with the required QoS for the corresponding file upload communication between the MCData client and the MCData content server. For that, the MCData server performs policy and charging control (PCC) procedures, e.g., over the Rx reference point as described in 3GPP TS 23.203 [14] for the case of an EPS system. +5. The MCData server sends a MCData file upload response to the MCData client indicating if it can proceed with the file upload to the MCData content server. +6. The media storage client on the MCData client sends an MCData upload data request to the media storage function on the MCData content server to upload the file. +7. The MCData content server provides an MCData upload data response to the MCData client indicating if the file was successfully stored (along with file URL) or failure. +8. The MCData client provides to the MCData server an MCData file upload completion status indicating that the file upload is completed. +9. Based on the MCData file upload completion status, the MCData server requests to the 3GPP system to release the network resources allocated for the corresponding file upload. + +#### 7.5.2.3 File download using HTTP + +##### 7.5.2.3.1 General + +The media storage client uses HTTP for a standalone data file download from the MCData content server. + +##### 7.5.2.3.2 Procedure for file download from the MCData content server without QoS + +The procedure in figure 7.5.2.3.2-1 describes the case where an MCData user is downloading a file from the media storage function of the MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. + +![Sequence diagram for Figure 7.5.2.3.2-1: File download using HTTP. The diagram shows two lifelines: 'Media storage client' and 'MCData content server'. The sequence of messages is: 1. initiate download request (from client to client), 2. MCData download data request (from client to server), 3. MCData download data response (from server to client).](54a53f959bb7758332532c1cd5f0ad75_img.jpg) + +``` + +sequenceDiagram + participant Client as Media storage client + participant Server as MCData content server + Note left of Client: 1. initiate download request + Client->>Server: 2. MCData download data request + Server-->>Client: 3. MCData download data response + +``` + +Sequence diagram for Figure 7.5.2.3.2-1: File download using HTTP. The diagram shows two lifelines: 'Media storage client' and 'MCData content server'. The sequence of messages is: 1. initiate download request (from client to client), 2. MCData download data request (from client to server), 3. MCData download data response (from server to client). + +**Figure 7.5.2.3.2-1: File download using HTTP** + +1. The user at the media storage client initiates a file download request available at the indicated URL. +2. The file available at the URL (received in MCData FD request or MCData group standalone FD request) is requested to be downloaded by the media storage client from the media storage function on the MCData content server using a MCData download data request. If emergency indicator is set in received in MCData FD request or MCData group standalone FD request, the media storage client sets emergency indicator in MCData download data request. + +NOTE: The media storage client can perform partial download requests to complete the missing parts after an incomplete file transfer. + +3. The media storage function on the MCData content server may apply reception control policy and provides a MCData download data response including the file to the media storage client. + +##### 7.5.2.3.3 Procedure for file download including request of network resources with required QoS + +The procedure in figure 7.5.2.3.3-1 describes the case where an MCData client sends a request to the MCData server for the download of a file from the media storage client on the MCData client to the media storage function on the MCData content server. The MCData server can, therefore, request network resources with the required QoS for the corresponding file download. + +Pre-conditions: + +1. The MCData user on the MCData client is registered on the MCData server for receiving MCData service. +2. The MCData client has been requested to download a file using HTTP and has received the corresponding file URL (via an MCData FD request or MCData group standalone FD request). +3. The MCData client is required to download a file from the MCData content server over network resources with required QoS. + +NOTE 1: It is implementation specific whether an MCData system enables that network resources with required QoS are required for file downloads. + +4. The MCData client knows its IP address/port to be used for the file download as well as the URI or IP address/port of the target MCData content server. + +NOTE 2: How the MCData client knows the IP addresses and ports to be used for the file download is implementation specific and out of the scope of this specification. + +![Sequence diagram illustrating the file download process using HTTP over network resources with required QoS. The diagram shows interactions between four entities: MCData client, 3GPP system, MCData server, and MCData content server. The process involves 10 steps: 1. Initiate file download request (MCData client to MCData server); 2. MCData file download request (MCData client to MCData server); 3a. MCData file availability request (MCData server to MCData content server); 3b. MCData file availability response (MCData content server to MCData server); 4. Authorization check (MCData server to MCData server); 5. Request for dedicated resources with required QoS (PCC procedures) (MCData server to 3GPP system); 6. MCData file download response (MCData server to MCData client); 7. MCData download data request (MCData client to MCData content server); 8. MCData download data response (MCData content server to MCData client); 9. MCData download completed report (MCData client to MCData server); 10. Release of dedicated resources (PCC procedures) (3GPP system to MCData server).](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant 3GPP system + participant MCData server + participant MCData content server + + Note left of MCData client: 1. Initiate file download request + MCData client->>MCData server: 2. MCData file download request + MCData server->>MCData content server: 3a. MCData file availability request + MCData content server-->>MCData server: 3b. MCData file availability response + Note right of MCData server: 4. Authorization check + MCData server->>3GPP system: 5. Request for dedicated resources with required QoS (PCC procedures) + MCData server-->>MCData client: 6. MCData file download response + MCData client->>MCData content server: 7. MCData download data request + MCData content server-->>MCData client: 8. MCData download data response + MCData client->>MCData server: 9. MCData download completed report + Note right of 3GPP system: 10. Release of dedicated resources (PCC procedures) + +``` + +Sequence diagram illustrating the file download process using HTTP over network resources with required QoS. The diagram shows interactions between four entities: MCData client, 3GPP system, MCData server, and MCData content server. The process involves 10 steps: 1. Initiate file download request (MCData client to MCData server); 2. MCData file download request (MCData client to MCData server); 3a. MCData file availability request (MCData server to MCData content server); 3b. MCData file availability response (MCData content server to MCData server); 4. Authorization check (MCData server to MCData server); 5. Request for dedicated resources with required QoS (PCC procedures) (MCData server to 3GPP system); 6. MCData file download response (MCData server to MCData client); 7. MCData download data request (MCData client to MCData content server); 8. MCData download data response (MCData content server to MCData client); 9. MCData download completed report (MCData client to MCData server); 10. Release of dedicated resources (PCC procedures) (3GPP system to MCData server). + +**Figure 7.5.2.3.3-1: File download using HTTP over network resources with required QoS** + +1. The MC user on the MCData client intends to download a file from the MCData content server based on a received MCData FD request or MCData group standalone FD request. If the MCData emergency state is already set for the MCData client, the MCData client sets the emergency indicator in the request. +2. The MCData client sends the MCData file download request to the MCData server. This request contains information about the MCData client (including IP address and port to be used for the file download), and the target MCData content server (including associated URI or IP address, and port). The request also contains the corresponding file URL on the MCData content server. +3. The MCData server may verify, based on the received file URL, whether the file is available in the MCData content server via the MCData-FD-5 reference point. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the corresponding file is not available in the MCData content server, the MCData server provides a response to the MCData client indicating that the file download request cannot proceed due to the unavailability of the file in the MCData content server. +4. The MCData server verifies that the corresponding MCData client is authorized to download the file from the corresponding MCData content server. +5. If the MCData client is authorized for the file download, the MCData server sends a request to the 3GPP system for the allocation of network resources with the required QoS for the corresponding file download communication between the MCData client and the MCData content server. For that, the MCData server performs policy and charging control (PCC) procedures, e.g., over the Rx reference point as described in 3GPP TS 23.203 [14] for the case of an EPS system. +6. The MCData server sends a MCData file download response to the MCData client indicating whether it can proceed with the file download from the MCData content server. +7. The media storage client on the MCData client sends an MCData download data request to the media storage function on the MCData content server to download the corresponding file. + +8. The MCData content server provides an MCData download data response to the MCData client including the file for the case of a successful response. +9. The MCData client provides to the MCData server an MCData download completed report indicating that the file download is completed. +10. Based on the MCData download completed report, the MCData server requests to the 3GPP system to release the network resources allocated for the corresponding file download. + +#### 7.5.2.4 One-to-one file distribution using HTTP + +##### 7.5.2.4.1 General + +The MCData client uses HTTP file distribution to download a file that is uploaded by another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. The target MCData user may be addressed using the functional alias that can be shared with other MCData users. + +##### 7.5.2.4.2 Procedure for single MCData system + +The procedure in figure 7.5.2.4.2-1 describes the case where a MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service. +2. The file to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2. +3. The MCData client may have activated functional alias to be used. +4. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating one-to-one file distribution using HTTP between MCData client 1, MCData server, and MCData client 2.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant S as MCData server + participant C2 as MCData client 2 + + Note over C1: 1. initiate data request + C1->>S: 2. MCData FD request + Note over S: 3. Authorize request + Note over S: 4. Verify if file is stored in MCData content server + S-->>C1: 5. MCData Functional alias resolution response + C1->>S: 6. MCData FD request + S->>C2: 7. MCData FD request + Note over C2: 8. Notify request + C2-->>S: 9. MCData FD response + S-->>C1: 10. MCData FD response + Note over C2: 11. Download file + C2->>S: 12. MCData download completed report + S->>C1: 13. MCData download completed report + +``` + +Sequence diagram illustrating one-to-one file distribution using HTTP between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.5.2.4.2-1: One-to-one file distribution using HTTP** + +1. The user at the MCData client 1 initiates a file distribution request to the chosen MCData user. + 2. The MCData client 1 sends a MCData FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. The MCData FD request may include additional implementation specific information in the application metadata container. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData FD request contains mandatory download indication. If the MCData user at MCData client has requested to deposit the file content into his/her MCData message store account, then MCData FD request contains deposit file indication set. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. The MCData user at MCData client 1 may include a functional alias within the FD data transfer and may address the target MCData client 2 using a functional alias. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency file distribution using HTTP or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData FD request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. +- NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. If functional alias is used to address that target MCData user, the MCData server resolves the + +functional alias to the corresponding MCData IDs for which the functional alias is active and proceed with step 4 otherwise proceed with step 6. + +NOTE 2: If the MCData server detects that the functional alias used as the target of the MCData FD request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the MCData FD request, if no suitable MCData ID is selected. + +4. The MCData server may verify whether the corresponding file is available in the MCData content server (not shown in the figure) via the MCData-FD-5 reference point using the received file URL in the MCData FD request. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the corresponding file is not available in the MCData content server, the MCData server provides a response to the MCData client 1 indicating that the file distribution request cannot proceed due to the unavailability of the file in the MCData content server. +5. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID. +6. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 assumes the MCData FD request in step 2 is rejected and sends a new MCData FD request towards the resolved MCData ID. +7. MCData server initiates the MCData FD request towards MCData client 2. The MCData FD request towards the MCData user contains an emergency indicator if it is present in the received MCData FD request from MCData client 1. If the deposit file indication information element is set to true in the received MCData FD request, MCData server shall follow the procedure as defined in the subclause 7.13.3.8 with the retrieve file indication element set to true while depositing this MCData communication to the MCData message store account of the user at MCData client 1. + +NOTE 3: MCData client 2 does not set its emergency state as a result of receiving the MCData FD request containing the emergency indicator. + +8. The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted or rejected or ignored. +9. The MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then MCData client 2 sends the MCData FD response to the MCData server. The MCData client 2 automatically sends an accepted MCData FD response when the received request includes a mandatory download indication. +10. The MCData server forwards the MCData FD response to the MCData client 1. +11. The Media storage client on the MCData client 2 downloads the file from the MCData content server using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user 2 subsequent action. The MCData client 2 records file download completed and notifies the MCData user 2. +12. The MCData client 2 provides an MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +13. The received MCData file download completed report from the MCData client 2 may be stored by the MCData server for download history interrogation from authorized MCData users. The MCData download completed report is sent by the MCData server to the MCData user at MCData client 1, if requested by the MCData client 1. + +##### 7.5.2.4.3 Procedure with interconnection between MCData systems + +The procedure in figure 7.5.2.4.3-1 describes the case where a MCData user initiates a one-to-one data communication for sending a file to another MCData user where that other MCData user is receiving MCData service on a partner MCData system, and where interconnection is in use between the two MCData systems. In this procedure, the file has not previously been downloaded in the partner MC system. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already service authorized and receiving MCData service. MCData client 1 is receiving service on its primary MCData system, and MCData client 2 is receiving MCData service in the partner MCData system of MCData client 1. +2. The file to be distributed has been uploaded to the media storage function on the MCData content server in the primary MCData system of MCData client 1 using the procedures defined in subclause 7.5.2.2. +3. There is a service agreement between the primary and partner MCData systems to allow files to be shared between MCData content servers in the two systems. +4. The MCData client may have an activated functional alias to be used. +5. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating one-to-one file distribution using HTTP with interconnection between a Primary MCData system and a Partner MCData system.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData content server (Primary) + participant MCData server FD function (Primary) + participant MCData server FD function (Partner) + participant MCData content server (Partner) + participant MCData client 2 + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server FD function (Primary): 2. MCData FD request + MCData server FD function (Primary)->>MCData content server (Primary): 3. Authorize request + MCData content server (Primary)->>MCData server FD function (Primary): 4a. MCData file availability request + MCData server FD function (Primary)->>MCData content server (Primary): 4b. MCData file availability response + MCData server FD function (Primary)->>MCData server FD function (Partner): 5. MCData FD request + MCData server FD function (Partner)->>MCData content server (Partner): 6. MCData FD request + MCData content server (Partner)->>MCData client 2: 7. Notify request + MCData content server (Partner)->>MCData server FD function (Partner): 8. MCData FD response + MCData server FD function (Partner)->>MCData server FD function (Primary): 9. MCData FD response + MCData server FD function (Primary)->>MCData client 1: 10. MCData FD response + MCData client 2->>MCData content server (Partner): 11. MCData download data request + MCData content server (Partner)->>MCData server FD function (Partner): 12. MCData file retrieve request + MCData server FD function (Partner)->>MCData content server (Partner): 13. MCData file retrieve response + MCData content server (Partner)->>MCData client 2: 14. MCData download data response + MCData content server (Partner)->>MCData server FD function (Partner): 15. MCData download completed report + MCData server FD function (Partner)->>MCData server FD function (Primary): 16. MCData download completed report + MCData server FD function (Primary)->>MCData client 1: 17. MCData download completed report + +``` + +Sequence diagram illustrating one-to-one file distribution using HTTP with interconnection between a Primary MCData system and a Partner MCData system. + +**Figure 7.5.2.4.3-1: One-to-one file distribution using HTTP with interconnection** + +1. The user at the MCData client 1 initiates a file distribution request to the MCData user at MCData client 2. +2. MCData client 1 sends an MCData FD request towards the primary MCData server. The MCData FD request contains content payload in the form of a file URL with the necessary access authorization information and may contain the file metadata information. The MCData FD request indicates the target MCData user for the one-to-one data communication. The MCData FD request contains a conversation identifier for message thread indication. If the MCData user at MCData client 1 has requested to mandatory download at the recipient side, + +then the MCData FD request contains the mandatory download indication. The MCData FD request may contain a request for a download completed report indication if selected by the user at MCData client 1. The MCData user at MCData client 1 may include a functional alias within the FD data transfer and may address the target MCData client 2 using a functional alias. + +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send the MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. +4. The MCData server may verify whether the corresponding file is available in the MCData content server via the MCData-FD-5 reference point using the received file URL in the MCData FD request. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the corresponding file is not available in the MCData content server, the MCData server provides a response to the MCData client 1 indicating that the file distribution request cannot proceed due to the unavailability of the file in the MCData content server. +5. The MCData server in the primary MCData system initiates the MCData FD request towards the MCData server in the partner MCData system, which contains the URL of the file which is stored in the primary MCData content server. The request includes the necessary access authorization information as MCData client 2 will retrieve the file while receiving service in the partner MCData system. + +NOTE 1: The contents of and mechanisms to use the authorization information are outside the scope of the present document. + +NOTE 2: With the use of the functional alias for addressing the target MCData clients, the partner MCData system is to be determined by the primary MCData system. + +6. If functional alias is used to address that target MCData user, the MCData server in the partner MCData system resolves the MCData IDs of the functional alias. The resulting list contains all associated MCData IDs/MCData users that may share this functional alias. The MCData server in the partner MCData system now checks which MCData users have FD capabilities and which are authorized to receive a file. The partner MCData server sends the MCData FD request to the MCData users determined. The file URL being provided in MCData FD request to the MCData users determined is prepended with server URI of the partner MCData content server, such that the URL identifies a file location in the partner MCData content server. + +NOTE 3: Determination of the target MCData client is based on the associated MCData IDs that share a functional alias and other criteria. + +7. The receiving MCData client 2 may notify the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted, rejected or ignored. +8. The MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then the MCData client 2 sends the MCData FD response to the partner MCData server. The MCData client 2 automatically sends an accepted MCData FD response when the received request includes a mandatory download indication. +9. The partner MCData server forwards the MCData FD response to the MCData server in the primary MCData system. +10. The primary MCData server forwards the MCData FD response to MCData client 1. +11. MCData client 2 requests the file from the partner MCData content server. + +NOTE 4: Step 11 may occur any time after step 8, before or after steps 9 and 10. + +12. The partner MCData content server checks whether the file is stored locally, and if this is not the case, sends an MCData file retrieve request to the primary MCData content server. The MCData file retrieve request contains the URL of the file location in the primary MCData system, generated by removing the prepended local path from the requested URL. + +NOTE 5: The means of proving authorization for the request is outside the scope of the present document. + +13. The primary MCData content server responds to the partner MCData content server with an MCData file retrieve response which contains the content of the file to be retrieved. File metadata may include the lifetime of the file. The primary MCData content server records that the file has been sent to the indicated partner MCData system. + +NOTE 6: The partner MCData content server may store the local copy of the file in case future requests arise until the expiry time sent from primary MCData system for the file is reached or until a request is received to delete the file. + +14. The partner MCData content server sends the file to MCData client 2 in the MCData download data response. MCData client 2 records file download completed and notifies MCData user 2. +15. The MCData client 2 provides an MCData download completed report for reporting file download completed, if this was requested by the user at MCData client 1 in the initial MCData FD request. +16. The MCData download completed report is sent to the primary MCData server. The partner MCData server may store the download completed report for download history interrogation from authorized MCData users in the partner MCData system. +17. The received MCData download completed report is sent by the primary MCData server to the MCData user at MCData client 1, if requested by the MCData client 1. The MCData file download completed report from the MCData client 2 may be stored by the primary MCData server for download history interrogation from authorized MCData users in the primary MCData system. + +#### 7.5.2.5 One-to-one file distribution using media plane + +##### 7.5.2.5.1 General + +The MCData client uses the media plane for a standalone data file download from another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. The target MCData user may be addressed using the functional alias that can be shared with other MCData users. + +##### 7.5.2.5.2 Procedure + +The procedure in figure 7.5.2.5.2-1 describes the case where an MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service. +2. Optionally, the MCData client may have an activated functional alias to be used. +3. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for One-to-one file distribution using media plane. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with MCData client 1 initiating a data request (1). It sends an MCData FD request (2) to the server. The server sends an authorize request (3) and a functional alias resolution response (4) back to client 1. Client 1 then sends another MCData FD request (5) to the server. The server performs transmission/reception control (6) and sends an MCData FD request (7) to client 2. Client 2 sends a notify request (8) back to the server. The server sends an MCData FD response (9) to client 1 and an MCData FD response (10) to client 2. Both clients then perform file distribution over the media plane (11 and 12). Finally, both clients send download completed reports (13 and 14) to the server.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData FD request + MCData server->>MCData server: 3. Authorize request + MCData server-->>MCData client 1: 4. MCData Functional alias resolution response + MCData client 1-->>MCData server: 5. MCData FD request + MCData server->>MCData server: 6. Transmission/ Reception control + MCData server->>MCData client 2: 7. MCData FD request + MCData client 2-->>MCData server: 8. Notify request + MCData server-->>MCData client 1: 9. MCData FD response + MCData server-->>MCData client 2: 10. MCData FD response + MCData client 1->>MCData server: 11. file distribution over media plane + MCData client 2->>MCData server: 12. file distribution over media plane + MCData client 1-->>MCData server: 14. MCData download completed report + MCData client 2-->>MCData server: 13. MCData download completed report + +``` + +Sequence diagram for One-to-one file distribution using media plane. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with MCData client 1 initiating a data request (1). It sends an MCData FD request (2) to the server. The server sends an authorize request (3) and a functional alias resolution response (4) back to client 1. Client 1 then sends another MCData FD request (5) to the server. The server performs transmission/reception control (6) and sends an MCData FD request (7) to client 2. Client 2 sends a notify request (8) back to the server. The server sends an MCData FD response (9) to client 1 and an MCData FD response (10) to client 2. Both clients then perform file distribution over the media plane (11 and 12). Finally, both clients send download completed reports (13 and 14) to the server. + +**Figure 7.5.2.5.2-1: One-to-one file distribution using media plane** + +- The user at the MCData client 1 initiates a file distribution request to the chosen MCData user. +- MCData client 1 sends a MCData FD request towards the MCData server. File metadata information is included in the SDP. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. The MCData FD request may include additional implementation specific information in the application metadata container. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the FD data transfer and may address the target MCData client 2 using a functional alias. + - If the MCData user at the MCData client 1 initiates an MCData emergency file distribution communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - The MCData FD request shall contain emergency indicator; and + - If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +- MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request. MCData server verifies whether the provided functional alias of MCData client 1, if present, can be used and has been activated for the user. If functional alias is used to address that target MCData user, the MCData server resolves the functional alias to the corresponding MCData ID(s) for which the functional alias is active and proceed with step 4 otherwise proceed with step 6. + +NOTE 2: If the MCData server detects that the functional alias used as the target of the MCData FD request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the MCData FD request, if no suitable MCData ID is selected. + +4. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID. +5. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 assumes the MCData FD request in step 2 is rejected and sends a new MCData FD request towards the resolved MCData ID. +6. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. +7. MCData server initiates the MCData FD request towards the MCData users determined. The MCData FD request towards the MCData user contains the emergency indicator if it is present in the received MCData FD request from MCData client 1. + +NOTE 3: MCData client 2 does not set its emergency state as a result of receiving the MCData FD request containing the emergency indicator. + +8. The receiving MCData client 2 notifies the user about the incoming MCData FD request which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData FD request an accepted response is assumed. +9. If the target MCData user 2 provides a response (accept or reject) to the notification, then MCData client 2 sends the MCData FD response to the MCData server. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication. +10. MCData server forwards the MCData FD response from MCData client 2 back to MCData client 1. +11. MCData client 1 distributes the file over the established media plane to MCData server. +12. MCData server distributes the file received from MCData client 1 to MCData client 2 over the established media plane. File download report is shared by the MCData client 2, if requested by the user at MCData client 1. After file transaction is completed, the media plane is released. The MCData client 2 records file download completed and notifies MCData user 2. + +NOTE 4: MCData server is not required to wait for the complete download of file from MCData client 1 prior to initiating file distribution to MCData client 2. + +13. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +14. The MCData file download completed report from MCData client may be stored by the MCData server for download history interrogation from the authorized MCData users. MCData download completed report is sent by the MCData server to the user at MCData client 1. + +#### 7.5.2.6 Group standalone file distribution using HTTP + +##### 7.5.2.6.1 General + +The initiation of a group standalone FD using HTTP to a selected group, results in affiliated group members receiving the file data. + +##### 7.5.2.6.2 Procedure + +The procedure in figure 7.5.2.6.2-1 describes the case where a MCData user is initiating group standalone data communication for sending a file to multiple MCData users, with or without download completed report request from the MCData user. + +Pre-conditions: + +1. The MCData users on the MCData clients 1 to n belong to the same MCData group and are already registered for receiving MCData service and affiliated to the group. +2. The file to be distributed is uploaded to the media storage function on the MCData content server using the procedures defined in subclause 7.5.2.2. + +3. The MCData client may have an activated functional alias to be used. +4. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram titled 'Figure 7.5.2.6.2-1: Group standalone FD using HTTP'. The diagram shows interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence of messages is: 1. initiate data request (client 1 to server); 2. MCData group standalone FD request (server to group management server); 2a. Affiliate user to group (dashed box, server to group management server); 3. Authorize request and resolve group id (group management server to server); 4. Verify if file is stored in MCData content server (dashed box, server to group management server); 5. MCData group standalone FD request (server to clients 2 to n); 6. Notify request (dashed box, clients 2 to n to server); 7. MCData group standalone FD response (clients 2 to n to server); 8. MCData group standalone FD response (server to client 1); 9. Download file (clients 2 to n to server); 10. MCData download completed report (clients 2 to n to server); 11. Aggregate download completed report (dashed box, server to group management server); 12. MCData [aggregated] download completed report (server to client 1).](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Sequence diagram titled 'Figure 7.5.2.6.2-1: Group standalone FD using HTTP'. The diagram shows interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence of messages is: 1. initiate data request (client 1 to server); 2. MCData group standalone FD request (server to group management server); 2a. Affiliate user to group (dashed box, server to group management server); 3. Authorize request and resolve group id (group management server to server); 4. Verify if file is stored in MCData content server (dashed box, server to group management server); 5. MCData group standalone FD request (server to clients 2 to n); 6. Notify request (dashed box, clients 2 to n to server); 7. MCData group standalone FD response (clients 2 to n to server); 8. MCData group standalone FD response (server to client 1); 9. Download file (clients 2 to n to server); 10. MCData download completed report (clients 2 to n to server); 11. Aggregate download completed report (dashed box, server to group management server); 12. MCData [aggregated] download completed report (server to client 1). + +**Figure 7.5.2.6.2-1: Group standalone FD using HTTP** + +1. The user at the MCData client 1 initiates a file distribution request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. The MCData client 1 sends a MCData group standalone FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData group standalone data request contains either the selected MCData group ID or the target recipients as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. The MCData group standalone FD request may include additional implementation specific information in the application metadata container. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData group standalone FD request contains mandatory download indication. The MCData group standalone FD request may contain a download completed report indication if selected by the user at MCData client 1. The MCData user at MCData client 1 may include a functional alias within the FD data transfer. If the MCData user at MCData client has requested to deposit the file content into his/her MCData message store account, then MCData FD request contains deposit file indication set. + +If the MCData user at MCData client 1 initiates an MCData emergency FD communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group standalone FD request shall contain an emergency indicator; +- ii) the MCData group standalone FD request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData group standalone FD request for the emergency FD communication; and +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +If the MCData user at MCData client 1 initiates an MCData imminent peril FD communication: + +- i) the MCData group standalone FD request shall contain an imminent peril indicator. +- 2a. If either emergency indicator or imminent peril indicator is present in the received MCData group standalone FD request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send an MCData group standalone FD request and that the size of the file is below maximum data size for FD from the group configuration. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCData group ID is used, the MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. + - i) If an emergency indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; and +- NOTE 2: While the MCData group is in the in-progress emergency state, all types of MCData communications within the group are processed as emergency group communications by the MCData server. MCData group members that are not in the emergency state do not indicate emergency in group communication requests. +- ii) If an imminent peril indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled. + 4. The MCData server may verify whether the corresponding file is available in the MCData content server (not shown in the figure) via the MCData-FD-5 reference point using the received file URL in the MCData group standalone FD request. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the file is not available in the MCData content server, the MCData server provides a response to the MCData client 1 indicating that the file distribution request cannot proceed due to the unavailability of the file in the MCData content server and skip rest of the steps. If the deposit file indication information element is set to true in the received MCData FD request, MCData server shall follow the procedure as defined in the subclause 7.13.3.8 with the retrieve file indication element set to true while depositing this MCData communication to the MCData message store account of the user at MCData client 1. + 5. MCData server initiates the MCData group standalone FD request towards each MCData user determined in step 3. The MCData group standalone FD request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group standalone FD request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group standalone FD request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group standalone FD request from the MCData client 1. + 6. The receiving MCData clients 2 to n notify the user about the incoming MCData group standalone FD request (including file metadata, if present) which may be either accepted or rejected or ignored. + 7. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then respective MCData client sends the MCData group standalone FD response to the MCData server. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. + 8. The MCData server forwards the MCData group standalone FD responses to the MCData client 1. + +NOTE 3: Step 8 can occur at any time following step 5, and prior to step 9 depending on the conditions to proceed with the file transmission. + +9. The media storage client on the MCData client(s) accepting the request downloads the file from the MCData content server (not shown in the figure) using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user subsequent action. The MCData clients successfully receiving the file through the media storage clients, record file download completed and notify the MCData users. +10. The MCData clients, receiving the file through the media storage client, provide MCData download completed reports for reporting file download completed, if requested by the user at MCData client 1. +11. The MCData file download completed reports from MCData clients may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. +12. Aggregated or individual MCData download completed reports are sent by the MCData server to the MCData user at MCData client 1, if requested by the MCData client 1. + +#### 7.5.2.7 Group standalone file distribution using media plane + +##### 7.5.2.7.1 General + +The initiation of a group standalone FD using media plane to a selected group, results in affiliated group members receiving the file data. + +##### 7.5.2.7.2 Procedure + +The procedure in figure 7.5.2.7.2-1 describes the case where an MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have an activated functional alias to be used. +3. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group standalone FD using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The process involves initiating a data request, sending a group standalone FD request, resolving the group ID, transmitting/receiving control, sending the request to other clients, notifying them, receiving responses, distributing files over the media plane, notifying data, and finally aggregating download completed reports.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + Note right of MCData server: 2a. Affiliate user to group + MCData server->>Group management server: 3. Resolve group id + Note right of MCData server: 4. Transmission/ Reception control + MCData server->>MCData client 2 to n: 5. MCData group standalone FD request + Note right of MCData client 2 to n: 6. Notify request + MCData client 2 to n->>MCData server: 7. MCData group standalone FD response + MCData server->>MCData client 1: 8. MCData group standalone FD response + Note left of MCData server: 9. file distribution over media plane + Note right of MCData server: 10. file distribution over media plane + Note right of MCData client 2 to n: 11. Notify data + MCData client 2 to n->>MCData server: 12. MCData download completed report + Note right of MCData server: 13. Aggregate download completed reports + MCData server->>MCData client 1: 14. MCData [aggregated] download completed report + +``` + +Sequence diagram for Group standalone FD using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The process involves initiating a data request, sending a group standalone FD request, resolving the group ID, transmitting/receiving control, sending the request to other clients, notifying them, receiving responses, distributing files over the media plane, notifying data, and finally aggregating download completed reports. + +**Figure 7.5.2.7.2-1: Group standalone FD using media plane** + +1. The user at the MCData client 1 initiates a file distribution request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group standalone FD request towards the MCData server. File metadata information is included in the SDP. The MCData group standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. The MCData group standalone FD request may include additional implementation specific information in the application metadata container. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the FD data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency file distribution communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group standalone FD request shall contain an emergency indicator; +- ii) the MCData group standalone FD request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData group standalone FD request for the emergency file distribution service communication; and +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +If the MCData user at MCData client 1 initiates an MCData imminent peril file distribution communication: + +- i) the MCData group standalone FD request shall contain an imminent peril indicator. + +2a. If either emergency indicator or imminent peril indicator is present in the received MCData group standalone data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone FD request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. + +i) If an emergency indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; and + +NOTE 2: While the MCData group is in the in-progress emergency state, all types of MCData communications within the group are processed as emergency group communications by the MCData server. MCData group members that are not in the emergency state do not indicate emergency in group communication requests. + +ii) If an imminent peril indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled. + +4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. + +5. MCData server initiates the MCData group standalone FD request towards each MCData user determined in step 3. The MCData group standalone data request towards each MCData client contains: + +i) an emergency indicator if it is present in the received MCData group standalone FD request from the MCData client 1; + +ii) an imminent peril indicator if it is present in the received MCData group standalone FD request from the MCData client 1; and + +iii) an alert indicator if requested to initiate an emergency alert in the received MCData group standalone FD request from the MCData client 1. + +6. The receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData group standalone FD request an accepted response is assumed. + +7. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData server. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. + +8. MCData server forwards the MCData group standalone FD response to the MCData client 1. + +NOTE 3: Step 8 can occur at any time following step 5, and prior to step 9 depending on the conditions to proceed with the file transmission. + +9. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. + +10. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s). For distribution via MBMS bearer(s), the procedure described in subclause 7.3 Use of MBMS transmission (on-network) is executed. File download report is shared by the receiving MCData clients, if requested by the user at MCData client 1. After file transaction is completed, the media plane is released. + +NOTE 4: MCData server is not required to wait for the complete download of file from MCData client 1 prior to initiating file distribution to MCData client 2. + +11. The MCData clients successfully receiving the file, records file download completed and notifies MCData user. + +12. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +13. The MCData file download completed report(s) from MCData client(s) may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. +14. Aggregated or individual MCData file download completed report is sent to the disposition requesting user at MCData client 1. + +#### 7.5.2.8 File removal using HTTP by authorized user + +##### 7.5.2.8.1 General + +The media storage client uses HTTP to remove a file that was previously uploaded to the MCData content server. + +##### 7.5.2.8.2 Procedure for single MCData system + +The procedure in figure 7.5.2.8.2-1 describes the case where a MCData user is removing the file that was previously uploaded to the MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. +2. The file has been successfully uploaded by the MCData user using the procedures defined in subclause 7.5.2.2. +3. The MCData content server has the ability to verify if the requesting MCData user is authorised to remove. + +![Sequence diagram for file removal using HTTP by authorized user. The diagram shows two participants: Media storage client and MCData content server. The sequence of messages is: 1. initiate file removal request (from client to server), 2. MCData remove file request by user (from client to server), 3. Using URL to remove the file (from server to client), 4. MCData remove file response by user (from server to client).](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +``` +sequenceDiagram + participant Client as Media storage client + participant Server as MCData content server + Note left of Client: 1. initiate file removal request + Client->>Server: 2. MCData remove file request by user + Note right of Server: 3. Using URL to remove the file + Server->>Client: 4. MCData remove file response by user +``` + +Sequence diagram for file removal using HTTP by authorized user. The diagram shows two participants: Media storage client and MCData content server. The sequence of messages is: 1. initiate file removal request (from client to server), 2. MCData remove file request by user (from client to server), 3. Using URL to remove the file (from server to client), 4. MCData remove file response by user (from server to client). + +**Figure 7.5.2.8.2-1: File removal using HTTP by authorised user** + +1. The user on the media storage client decides to remove a file that was previously uploaded. +2. The URL of the file to be removed is included in the request sent to the media storage function on the MCData content server. +3. The MCData content server remove the file indicated by the URL. +4. The MCData content server informs the media storage client if the file is successfully removed. + +**Editor's note:** It is FFS if and how the recipients of the file URL need to be notified if the file is no longer available to be downloaded. + +##### 7.5.2.8.3 Procedure for interconnection between MCData systems + +The procedure in figure 7.5.2.8.3-1 describes the case where an MCData user removes the file that was previously uploaded to the primary MCData system MCData content server, and where the file has been made available in the partner MCData system MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. +2. The file has previously been uploaded to the MCData content server in the primary MCData system of MCData client 1. +3. The file has been successfully transferred to the MCData content server in the partner MCData system. + +![Sequence diagram illustrating file removal using HTTP by an authorized user. The diagram shows interactions between a Media storage client, MCData content server, and MCData server FD function in both Primary and Partner MCData systems.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` + +sequenceDiagram + participant MSC as Media storage client + participant MCS as MCData content server + participant MSFD as MCData server FD function + + Note left of MSC: Primary MCData system + Note right of MSFD: Partner MCData system + + MSC->>MCS: 1. initiate file removal request + Note over MSC: 2. MCData remove file request by user + Note over MCS: 3. Use URL to remove file + Note right of MSFD: 4. MCData remove file request by user + Note over MSFD: 5. Use URL to remove file + Note right of MSFD: 6. MCData remove file response by user + Note over MSC: 7. MCData remove file response by user + +``` + +Sequence diagram illustrating file removal using HTTP by an authorized user. The diagram shows interactions between a Media storage client, MCData content server, and MCData server FD function in both Primary and Partner MCData systems. + +**Figure 7.5.2.8.3-1: File removal using HTTP by authorized user** + +1. The user on the media storage client decides to remove a file that was previously uploaded. +2. The URL of the file to be removed is included in the request sent to the media storage function on the primary MCData content server. +3. The primary MCData content server removes the file indicated by the URL. + +NOTE: Step 3 may occur at any time following step 2 and before step 6. + +4. As the primary MCData content server has recorded that the file has previously been sent to the partner MCData system, the primary MCData content server sends the MCData remove file request by user to the partner MCData content server, containing the URL of the file which was stored on the primary MCData content server. +5. The partner MCData content server removes the file indicated by the URL. +6. The partner MCData content server informs the primary MCData content server that the file has been successfully removed. +7. The primary MCData content server informs the media storage client if the file is successfully removed. + +**Editor's note:** It is FFS if and how the recipients of the file URL need to be notified if the file is no longer available to be downloaded + +#### 7.5.2.9 Void + +#### 7.5.2.10 Group standalone file distribution using the MBMS download delivery method + +##### 7.5.2.10.1 General + +The initiation of a group standalone FD to a selected group results in affiliated group members receiving the file data over MBMS. + +The first steps of the procedure are identical to the procedure Group standalone file distribution using HTTP (7.5.2.6). Based on the density and distribution of target group members, the MCData server may decide to deliver the file over MBMS. + +The MBMS download delivery method is described in clause 7 of 3GPP TS 26.346 [21]. + +##### 7.5.2.10.2 Procedure + +The procedure in figure 7.5.2.10.2-1 describes the case where a MCData user is initiating group standalone data communication for sending a file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. The file to be distributed is uploaded to the media storage function on the MCData content server using the procedure defined in subclause 7.5.2.2. + +![Sequence diagram for Group standalone FD using the MBMS download delivery method. Lifelines: MCData client 1, MCData server, MCData Content Server, MCData client 2 to n. The sequence shows the initiation of a data request, resolution of group ID, establishment of MBMS bearer, and subsequent file distribution and reporting.](7b8b192e2853ef28d28eff0241ebe86b_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData Content Server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 4. establish MBMS Bearer + MCData server->>MCData Content Server: 5. MCData group standalone FD over MBMS request + Note right of MCData Content Server: 6. Notify request + MCData Content Server->>MCData client 2 to n: 7. MCData group standalone FD response + Note right of MCData client 2 to n: 8. MCData group standalone FD response + Note right of MCData client 2 to n: 9. Receive file + Note right of MCData client 2 to n: 10. Download missing parts + MCData client 2 to n->>MCData server: 11. MCData download completed report + Note right of MCData server: 12. Aggregate download completed report + Note right of MCData server: 13. MCData [aggregated] download completed report + MCData server->>MCData client 1: 13. MCData [aggregated] download completed report + +``` + +Sequence diagram for Group standalone FD using the MBMS download delivery method. Lifelines: MCData client 1, MCData server, MCData Content Server, MCData client 2 to n. The sequence shows the initiation of a data request, resolution of group ID, establishment of MBMS bearer, and subsequent file distribution and reporting. + +Figure 7.5.2.10.2-1: Group standalone FD using the MBMS download delivery method + +1-3. Steps 1-3 are the same as in the procedure for Group standalone FD using HTTP (7.5.2.6). + +4. The MCData server executes the procedure described in subclause 7.3.5. The MCData server defines, in the MBMS session properties (subclause 5.4 of 3GPP TS 26.348 [19]), the ingest mode to provide the file into the BM-SC via xMB-U. As described in clause 7.3.5.3.3, the MCData server decides how the file stored in the MCData content server is provided for distribution over the MBMS session. + +If the pull ingest mode is defined, the MCData server may provide in this step the file list. As described in 3GPP TS 26.348 [19], the file list includes, among other information, the file URL to be used by the BM-SC to fetch the file and the earliest fetch time. The earliest fetch time may be configured with a long enough delay so that the MBMS session is established and steps 6 to 8 are executed before the delivery over MBMS. The MCData server can also update the MBMS session with the file list in a later step. + +If the push ingest mode is defined, the MCData server obtains the URL from the BM-SC to be used to push the file via xMB-U. The MCData server ingests the content into the BM-SC after the MBMS session is established and steps 6 to 8 are performed. + +5. The MCData server initiates the MCData group standalone FD over MBMS request towards each MCData user determined in step 3. The request is sent over unicast or within an MBMS bearer for application level control signalling. +6. The receiving MCData clients 2 to n notify the users about the incoming MCData group standalone FD request (including file metadata, if present). +7. The MCData clients 2 to n automatically send accepted MCData group standalone FD response when the incoming request included mandatory download indication. + +NOTE 1: When the UE is in idle mode, MCData clients may skip step 8. + +NOTE 2: If the pull ingest mode was defined in step 5 and the file list has not been provided yet, the MCData server updates the MBMS session with the file list. If the push ingest mode was defined, the MCData server can start pushing the file for distribution over MBMS. + +8. The MCData server forwards the MCData group standalone FD responses to the MCData client 1. + +NOTE 3: Step 8 can occur at any time following step 6, and prior to step 10 depending on the conditions to proceed with the file transmission. + +9. The MCData clients receive the file delivered over MBMS. + +10. If losses occurred during the file delivery over MBMS, the MCData clients may download the missing parts using the procedures defined in subclause 7.5.2.3. + +NOTE 4: If the file is not successfully received over MBMS, e.g. due to a poor MBMS reception quality, the media storage client of the MCData client(s) can download the file using the procedure defined in subclause 7.5.2.3. + +11. The MCData clients, after reception, initiate MCData download completed reports for reporting file download completed, if requested by the user at MCData client 1. +12. The MCData file download completed reports from the MCData clients may be stored by the MCData server for download history interrogation from authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. + +13. Aggregated or individual MCData download completed reports are sent by the MCData server to the MCData user at MCData client 1. + +#### 7.5.2.11 One-to-one FD communication upgrade to an emergency FD communication + +##### 7.5.2.11.1 General + +This clause is for adding procedures related to upgrading an existing one-to-one FD communication to an emergency one-to-one FD communication. + +##### 7.5.2.11.2 Procedure + +The procedure in figure 7.5.2.11.2-1 describes the case where an authorized MCData user is upgrading a MCData one-to-one FD communication to a MCData emergency one-to-one FD communication. This procedure is applicable only when MCData one-to-one file distribution communication is established as described in subclause 7.5.2.5 "One-to-one file distribution using media plane". + +Pre-conditions: + +1. Both members of the one-to-one FD communication belong to the same MCData system. +2. One-to-one FD communication is already in progress. + +![Sequence diagram illustrating the One-to-one FD communication upgrade to an emergency one-to-one FD communication. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2 within the Home MCData service provider. The process starts with an existing one-to-one FD communication in progress. Client 1 initiates an emergency communication, then sends an upgrade request to the server. The server forwards this request to Client 2. Client 2 notifies its user and sends a response back to the server. The server performs a bearer priority adjustment and sends a final response to Client 1. The communication then continues over the upgraded bearer.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note over MCData client 1, MCData client 2: MCData one-to-one FD communication is in progress + Note left of MCData client 1: 1. initiate emergency communication + MCData client 1->>MCData server: 2. MCData one-to-one FD upgrade request + MCData server->>MCData client 2: 3. MCData one-to-one FD upgrade request + Note right of MCData client 2: 4. Notify emergency communication + MCData client 2->>MCData server: 5. MCData one-to-one FD upgrade response + Note left of MCData server: 6. Bearer priority adjustment + MCData server->>MCData client 1: 7. MCData one-to-one FD upgrade response + Note over MCData client 1, MCData client 2: 8. MCData one-to-one FD communication over upgraded bearer + +``` + +Sequence diagram illustrating the One-to-one FD communication upgrade to an emergency one-to-one FD communication. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2 within the Home MCData service provider. The process starts with an existing one-to-one FD communication in progress. Client 1 initiates an emergency communication, then sends an upgrade request to the server. The server forwards this request to Client 2. Client 2 notifies its user and sends a response back to the server. The server performs a bearer priority adjustment and sends a final response to Client 1. The communication then continues over the upgraded bearer. + +**Figure 7.5.2.11.2-1 One-to-one FD communication upgrade to an emergency one-to-one FD communication** + +1. The MCData user at MCData client 1 initiates an emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 1: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +2. MCData client 1 requests the MCData server to upgrade the MCData one-to-one FD communication to in-progress emergency by sending a MCData one-to-one FD upgrade request. + +3. The MCData server sends the MCData one-to-one FD upgrade request towards MCData client 2. + +NOTE 2: MCData client 2 does not set its emergency state as a result of receiving the MCData one-to-one FD upgrade request containing the emergency indicator. + +4. The MCData user of MCData client 2 is notified of the in-progress emergency of the MCData emergency one-to-one FD communication. + +5. The MCData client 2 acknowledges the MCData one-to-one FD upgrade request and sends MCData one-to-one FD upgrade response to the MCData server. + +6. The MCData server adjusts the priority of the underlying bearer for both participants of the MCData one-to-one FD communication. The priority is retained until the communication ends. +7. The MCData server sends MCData one-to-one FD upgrade response to MCData client 1. +8. MCData client 1 and MCData client 2 continue with the MCData one-to-one FD communication, which has been transformed into an MCData emergency one-to-one FD communication. + +#### 7.5.2.12 Group FD communication upgrade to an emergency group FD communication + +##### 7.5.2.12.1 General + +This clause is for adding procedures related to upgrading an existing MCData group FD communication to an MCData emergency group FD communication. + +##### 7.5.2.12.2 Procedure + +The procedure in figure 7.5.2.12.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData group FD communication to an MCData emergency group FD communication. This procedure is applicable only when group MCData FD communication is established as described in subclause 7.5.2.7 "Group standalone file distribution using media plane". + +NOTE 1: For simplicity, a single MCData server is shown in place of a user home MCData server and a group hosting MCData server. + +Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 are affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. An MCData group FD communication is already in progress. +4. The initiating MCData client 1 has been configured to send an MCData emergency alert when upgrading an MCData emergency group communication. + +![Sequence diagram showing the upgrade of MCData group FD communication to an emergency state. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client 3, and Home MCData service provider. The process involves initiating an emergency, sending upgrade requests, adjusting bearer priority, notifying clients, and receiving responses.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant MC1 as MCData client 1 + participant MS as MCData server + participant MC2 as MCData client 2 + participant MC3 as MCData client 3 + Note over MC1, MC3: MCData group FD communication is in progress + + MC1->>MS: 1. Initiate group emergency + MC1->>MS: 2. MCData group FD upgrade request + Note over MS: 3. Bearer priority adjustment + MS->>MC2: 4. MCData group FD upgrade request + MS->>MC3: 4. MCData group FD upgrade request + Note over MC2: 5. Notify group emergency status + Note over MC3: 5. Notify group emergency status + MC2-->>MS: 6. MCData group FD upgrade response + MC3-->>MS: 6. MCData group FD upgrade response + MS->>MC1: 7. MCData group FD upgrade response + + Note over MC1, MC3: MCData group FD communication over upgraded bearer + +``` + +Sequence diagram showing the upgrade of MCData group FD communication to an emergency state. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client 3, and Home MCData service provider. The process involves initiating an emergency, sending upgrade requests, adjusting bearer priority, notifying clients, and receiving responses. + +**Figure 7.5.2.12.2-1: MCData group FD communication upgraded to an MCData emergency group FD communication** + +1. The MCData user at MCData client 1 initiates a group emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +NOTE 2: While MCData client 1 is in the emergency state, all types of MCData one-to-one and group communications initiated by MCData client 1 are initiated as MCData emergency communications. + +2. MCData client 1 requests the MCData server to upgrade the MCData group to an in-progress emergency state by sending a MCData group FD upgrade request. The MCData client 1 sets the emergency indicator in the request. If configured to send an MCData alert when initiating an MCData emergency upgrade, the request also contains an indication that an MCData alert is to be initiated. +3. The MCData server sets the emergency state of the MCData group and adjusts the priority of the underlying bearer for all or selected participants in the MCData group FD communication that receive the communication over unicast. + +NOTE 3: The determination of the selected participants whose bearers have to be upgraded is left to implementation. + +NOTE 4: While the MCData group is in the in-progress emergency state, all types of MCData communications within the group are processed as emergency group communications by the MCData server. MCData group members that are not in the emergency state do not indicate emergency in group communication requests. + +4. MCData server sends the MCData group FD upgrade request towards the MCData clients of each of those affiliated MCData group members. The request contains an indication of an MCData emergency alert if the request from the originator indicated MCData emergency alert. +5. MCData users are notified of the in-progress emergency state of the MCData group. + +6. The receiving MCData clients send the MCData group FD upgrade response to the MCData server to acknowledge the MCData group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCData server sends the MCData group FD upgrade response to the MCData user 1 to confirm the upgrade request. + +NOTE 5: Step 7 can occur at any time following step 3, depending on the conditions to proceed with the call. + +MCData client 1, MCData client 2 and MCData client 3 continue with the MCData group FD communication, which has been transformed into an MCData emergency group FD communication. + +#### 7.5.2.13 Group FD communication in-progress emergency group state cancel + +##### 7.5.2.13.1 General + +This clause describes procedures related to an MCData in-progress emergency group state cancel. The emergency state of the group can also be cancelled by the group SDS in-progress emergency state cancellation procedure in subclause 7.4.2.10.2, or by the emergency alert cancellation procedure specified in 3GPP TS 23.280 [16], subclause 10.10.1.2.2.2. + +##### 7.5.2.13.2 Procedure + +The procedure in figure 7.5.2.13.2-1 describes the case where an authorized MCData user cancels MCData group's in-progress emergency. + +Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. MCData group members have been notified about the in-progress emergency. +4. The MCData group is in the in-progress emergency state and has prioritized bearer support. +5. MCData client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram illustrating the MCData group FD in-progress emergency group state cancel process. The diagram shows interactions between MCData client 1, MCData server, MCData client 2, and MCData client 3 under the 'Home MCData service provider'. The process starts with a bar 'MCData group FD emergency communication is in progress'. Step 1: MCData client 1 initiates an in-progress emergency group state cancel. Step 2: MCData client 1 sends an in-progress priority state cancel request to the MCData server. Step 3: MCData server performs bearer priority adjustment. Step 4: MCData server sends an in-progress priority state cancel request to MCData client 2 and MCData client 3. Step 5: MCData client 2 and MCData client 3 notify emergency cancel. Step 6: MCData client 2 and MCData client 3 send in-progress priority state cancel responses to the MCData server. Step 7: MCData server sends an in-progress priority state cancel response to MCData client 1. The process ends with a bar 'MCData group FD communication continues'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + Note over MCData client 1, MCData client 3: MCData group FD emergency communication is in progress + MCData client 1->>MCData server: 2. MCData group FD in-progress priority state cancel request + Note over MCData server: 3. Bearer priority adjustment + MCData server->>MCData client 2: 4. MCData group FD in-progress priority state cancel request + MCData server->>MCData client 3: 4. MCData group FD in-progress priority state cancel request + Note over MCData client 2: 5. Notify emergency cancel + Note over MCData client 3: 5. Notify emergency cancel + MCData client 2-->>MCData server: 6. MCData group FD in-progress priority state cancel response + MCData client 3-->>MCData server: 6. MCData group FD in-progress priority state cancel response + MCData server-->>MCData client 1: 7. MCData group FD in-progress priority state cancel response + Note over MCData client 1, MCData client 3: MCData group FD communication continues + +``` + +Sequence diagram illustrating the MCData group FD in-progress emergency group state cancel process. The diagram shows interactions between MCData client 1, MCData server, MCData client 2, and MCData client 3 under the 'Home MCData service provider'. The process starts with a bar 'MCData group FD emergency communication is in progress'. Step 1: MCData client 1 initiates an in-progress emergency group state cancel. Step 2: MCData client 1 sends an in-progress priority state cancel request to the MCData server. Step 3: MCData server performs bearer priority adjustment. Step 4: MCData server sends an in-progress priority state cancel request to MCData client 2 and MCData client 3. Step 5: MCData client 2 and MCData client 3 notify emergency cancel. Step 6: MCData client 2 and MCData client 3 send in-progress priority state cancel responses to the MCData server. Step 7: MCData server sends an in-progress priority state cancel response to MCData client 1. The process ends with a bar 'MCData group FD communication continues'. + +**Figure 7.5.2.13.2-1: MCData group FD in-progress emergency group state cancel** + +1. The user at the MCData client 1 initiates an MCData group FD in-progress emergency group state cancel. + +NOTE 1: An MCData user authorized to cancel in-progress emergencies on the MCData group can also be authorised to cancel the MCData emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCData emergency state. + +2. The MCData client 1 sends an MCData group FD in-progress priority state cancel request to the MCData server. The MCData client 1 also resets emergency indicator in the request to inform MCData server about cancellation of in-progress emergency group state. + +NOTE 2: If an MCData emergency alert relating to MCData client 1 is in effect together with an MCData in-progress emergency group state on the MCData group, the MCData emergency alert of MCData client 1 can be cancelled at the same time. In that case, the MCData group FD in-progress priority group state cancel request carries an indication that the emergency alert of MCData client 1 is also being cancelled. + +NOTE 3: If an MCData group FD in-progress priority state cancel request is received by the MCData server while a group member that is in the emergency state is transmitting, the MCData group FD in-progress priority state cancel request is rejected by the MCData server. + +3. The MCData server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCData server cancels/resets the emergency in-progress state of the MCData group. +4. The MCData server sends an MCData group FD in-progress priority state cancel request to the MCData group members. +5. MCData group members are notified of the MCData group FD in-progress emergency state cancel. +6. The receiving MCData clients send the MCData group FD in-progress priority state cancel response to the MCData server to acknowledge the MCData in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. + +7. The MCData server sends the MCData group FD in-progress priority state cancel response to the MCData user 1 to confirm the MCData in-progress emergency group state cancel. If the MCData in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCData client 1 resets its local emergency status. + +NOTE 4: Step 7 can occur at any time following step 3, depending on the conditions to proceed with the call. + +#### 7.5.2.14 Group FD communication upgrade to an imminent peril group FD communication + +##### 7.5.2.14.1 General + +This clause is for adding procedures related to an imminent peril group FD communication. + +##### 7.5.2.14.2 Procedure + +This procedure is applicable only when group MCData communication is established as described in subclause 7.5.2.7 "Group standalone file distribution using media plane". The MCData service shall support the procedures and related information flows as specified in subclause 7.5.2.12 "Group FD communication upgrade to an emergency group FD communication" with the following clarifications: + +- In step 2), the MCData client 1 sets the imminent peril indicator; +- In step 3), the bearers' priority is adjusted as necessary, to correspond to an imminent peril priority which could be different than the setting used in the procedure in subclause 7.5.2.12; and +- In step 5), MCData users are notified of the in-progress imminent peril state of the MCData group. + +#### 7.5.2.15 Group FD communication in-progress imminent peril group state cancel + +##### 7.5.2.15.1 General + +This clause is for adding procedures related to an imminent peril group state cancel. + +##### 7.5.2.15.2 Procedure + +The MCData service shall support the procedures and related information flows as specified in subclause 7.5.2.13 "Group FD communication in-progress emergency group state cancel" with the following clarifications: + +- In step 2), the MCData client 1 sets the imminent peril indicator; and +- In step 5), MCData users are notified of the in-progress imminent peril state cancel. + +### 7.5.3 File distribution for off-network + +#### 7.5.3.1 General + +Off-network file distribution communications are based on ProSe capabilities as described in clause 7.16. + +#### 7.5.3.2 Information flows for file distribution + +##### 7.5.3.2.1 MCData FD request (using media plane) + +Table 7.5.3.2.1-1 describes the information flow for the MCData FD request sent from the MCData client to another MCData client. + +**Table 7.5.3.2.1-1: MCData FD request (using media plane)** + +| Information element | Status | Description | +|--------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| MCData ID | M | The identity of the MCData user receiving the file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE) | M | Media parameters offered | +| NOTE: Includes file metadata. | | | + +##### 7.5.3.2.2 MCData FD response (using media plane) + +Table 7.5.3.2.2-1 describes the information flow for the MCData FD response sent from the MCData client to another MCData client. + +**Table 7.5.3.2.2-1: MCData FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Acceptance confirmation | M | An indication whether the client has positively accepted the request | + +##### 7.5.3.2.3 MCData download completed report + +Table 7.5.3.2.3-1 describes the information flow for the MCData download completed report sent from the MCData client to another MCData client. + +**Table 7.5.3.2.3-1: MCData download completed report** + +| Information element | Status | Description | +|--------------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Disposition association | M | Identifies the original MCData transaction | +| Disposition confirmation | M | An indication that the client has completed downloading file | + +##### 7.5.3.2.4 MCData group standalone FD request (using media plane) + +Table 7.5.3.2.4-1 describes the information flow for the MCData group standalone FD request sent from the MCData client to another MCData client. + +**Table 7.5.3.2.4-1: MCData group standalone FD request (using media plane)** + +| Information element | Status | Description | +|--------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending the file | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| SDP offer (see NOTE) | M | Media parameters offered | +| NOTE: Includes file metadata. | | | + +##### 7.5.3.2.5 MCData group standalone FD response (using media plane) + +Table 7.5.3.2.5-1 describes the information flow for the MCData group standalone FD response sent from the MCData client to another MCData client. + +**Table 7.5.3.2.5-1: MCData group standalone FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Acceptance confirmation | M | An indication whether the client has positively accepted the request | + +#### 7.5.3.3 One-to-one standalone file distribution using media plane + +##### 7.5.3.3.1 General + +The MCData client uses media plane for a standalone FD download from another MCData client in off-network. + +##### 7.5.3.3.2 Procedure + +Figure 7.5.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone FD data to other MCData client, with or without download completed report request. + +Pre-conditions: + +1. MCData user 1 has initiated communication for sending standalone FD data to other MCData user 2. +2. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable. +3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user 2, using ProSe Discovery procedures. + +![Sequence diagram illustrating one-to-one standalone file distribution using media plane between MCData client 1 and MCData client 2.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note right of MCData client 2: 2. Assert policy + Note right of MCData client 2: 3. Notify request + MCData client 1->>MCData client 2: 1. MCData FD request + MCData client 2-->>MCData client 1: 4. MCData FD response + Note left of MCData client 2: 5. file distribution over media plane + MCData client 2-->>MCData client 1: 6. MCData download completed report + +``` + +The diagram shows a sequence of interactions between MCData client 1 and MCData client 2. + 1. MCData client 1 sends an 'MCData FD request' to MCData client 2. + 2. MCData client 2 performs an 'Assert policy' action (shown in a box). + 3. MCData client 2 sends a 'Notify request' (shown in a dashed box) to MCData client 1. + 4. MCData client 2 sends an 'MCData FD response' back to MCData client 1. + 5. A thick green arrow labeled 'file distribution over media plane' points from MCData client 1 to MCData client 2. + 6. MCData client 2 sends an 'MCData download completed report' back to MCData client 1. + +Sequence diagram illustrating one-to-one standalone file distribution using media plane between MCData client 1 and MCData client 2. + +**Figure 7.5.3.2-1: One-to-one standalone file distribution using media plane** + +1. MCData client 1 sends a MCData FD request towards the MCData client 2. File metadata information is included in the SDP. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. The MCData FD request may include additional implementation specific information in the application metadata container. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. +2. On receiving a MCData FD request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege. +3. The receiving MCData client 2 notifies the user about the incoming MCData FD request which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData FD request and instead only notify the MCData user about file downloading. +4. If the target MCData user 2 provides a response (accept or reject) to the notification, then the MCData client 2 sends the MCData FD response to the MCData client 1. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication. +5. MCData client 1 distributes the file over the established media plane to MCData client 2. +6. The MCData client 2 records file download completed and notifies MCData user 2. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + +#### 7.5.3.4 Group standalone file distribution using media plane + +##### 7.5.3.4.1 General + +The initiation of a group standalone FD to a selected group results in off-network MCData group members receiving the file data. + +##### 7.5.3.4.2 Procedure + +Figure 7.5.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending FD data to a MCData group, with or without download completed report request. + +Pre-conditions: + +1. MCData user 1 has initiated group communication for sending FD data to the MCData group. + +2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +3. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram illustrating Group standalone file distribution using media plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. The sequence of messages is: 1. MCData group standalone FD request from client 1 to client N; 2. Assert policy (internal to clients 2-N); 3. Notify request (internal to clients 2-N); 4. MCData group standalone FD response from clients 2-N back to client 1; 5. File distribution over media plane from client 1 to clients 2-N; 6. Notify data (internal to clients 2-N); 7. MCData download completed report from clients 2-N back to client 1.](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client N + Note right of MCData client 2: 2. Assert policy + Note right of MCData client 2: 3. Notify request + Note right of MCData client N: 2. Assert policy + Note right of MCData client N: 3. Notify request + MCData client 1->>MCData client N: 1. MCData group standalone FD request + MCData client 2->>MCData client 1: 4. MCData group standalone FD response + MCData client N->>MCData client 1: 4. MCData group standalone FD response + Note over MCData client 1, MCData client N: 5. File distribution over media plane + MCData client 1->>MCData client N: 5. file distribution over media plane + Note right of MCData client 2: 6. Notify data + Note right of MCData client N: 6. Notify data + MCData client 2->>MCData client 1: 7. MCData download completed report + MCData client N->>MCData client 1: 7. MCData download completed report + +``` + +Sequence diagram illustrating Group standalone file distribution using media plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. The sequence of messages is: 1. MCData group standalone FD request from client 1 to client N; 2. Assert policy (internal to clients 2-N); 3. Notify request (internal to clients 2-N); 4. MCData group standalone FD response from clients 2-N back to client 1; 5. File distribution over media plane from client 1 to clients 2-N; 6. Notify data (internal to clients 2-N); 7. MCData download completed report from clients 2-N back to client 1. + +**Figure 7.5.3.4.2-1: Group standalone file distribution using media plane** + +1. MCData client 1 sends a MCData FD request towards the MCData group. File metadata information is included in the SDP. The MCData group standalone data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. The MCData group standalone FD request may include additional implementation specific information in the application metadata container. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. +2. On receiving a MCData FD request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege. +3. If the policy assertion is positive, the receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData group standalone FD request and instead only notify the MCData user about file downloading. +4. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData client 1. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. +5. MCData client 1 and MCData client 2 to n have successfully established media plane for file transmission and the MCData client 1 transmits the file data. +6. The MCData client 2 to n successfully receiving the file, records file download completed and notifies MCData users. +7. MCData client 2 to n initiate a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + +## 7.6 Transmission and reception control + +### 7.6.1 General + +Based on the configurations (available in MCData user profile, group configuration and service configuration), the MCData transmission and reception control provides a necessary capability for an authorized user of the MCData service to transmit, receive notification messages due to various trigger conditions, advocates reception mode and terminate transmission when there is no longer a need to transmit. The subclauses below describe the transmission and reception control procedures using signalling control plane. + +### 7.6.2 Transmission and reception control for on-network + +#### 7.6.2.1 Information flows for transmission and reception control + +##### 7.6.2.1.1 MCData control indication + +Table 7.6.2.1.1-1 describes the information flow for the MCData control indication sent from the MCData server to the MCData client. + +**Table 7.6.2.1.1-1: MCData control indication** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the control indication is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Control indication type | M | One of the following:
- No permission to transmit data
- No affiliated members found to the selected MCData group
- Rejected due to exceeding data transmit size
- Rejected due to exceeding data transmit time
- Request to transmit is queued | + +##### 7.6.2.1.2 MCData indication + +Table 7.6.2.1.2-1 describes the information flow for the MCData indication sent from the MCData server to the MCData client. + +**Table 7.6.2.1.2-1: MCData indication** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the MCData indication is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Deferred data list | M | List of references to deferred data awaiting download | + +##### 7.6.2.1.3 MCData get deferred list request + +Table 7.6.2.1.3-1 describes the information flow for the MCData get deferred list request sent from the MCData client to the MCData server. + +**Table 7.6.2.1.3-1: MCData get deferred list request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting deferred list | + +##### 7.6.2.1.4 MCData get deferred list response + +Table 7.6.2.1.4-1 describes the information flow for the MCData get deferred list response sent from the MCData server to the MCData client. + +**Table 7.6.2.1.4-1: MCData get deferred list response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting deferred list | +| Deferred data list | M | List of references to deferred data awaiting download | + +#### 7.6.2.2 Automatic transmission for SDS + +##### 7.6.2.2.1 General + +When SDS message is sent, the data is transferred from the sending MCData client to the receiving MCData client without any request/grant procedure or any explicit actions on the part of the receiving MCData client. + +##### 7.6.2.2.2 Procedure + +The procedure in figure 7.6.2.2.2-1 describes the case where MCData SDS is automatically transmitted to the selected recipient user or affiliated members of the selected MCData group. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. +2. Optionally, MCData client may have an activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Automatic transmission for SDS. Lifelines: MCData client 1, MCData server, MCData client 2. Steps: 1. initiate data transmit (client 1), 2. MCData transmission to MCData server (client 1 to server), 3. Authorize request and size check for auto-send (server), 4. MCData control indication (server to client 1), 5. MCData delivery to recipient(s) (server), 6. MCData indication (server to client 2).](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for auto-send + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. MCData delivery to recipient(s) + MCData server-->>MCData client 2: 6. MCData indication + +``` + +Sequence diagram for Automatic transmission for SDS. Lifelines: MCData client 1, MCData server, MCData client 2. Steps: 1. initiate data transmit (client 1), 2. MCData transmission to MCData server (client 1 to server), 3. Authorize request and size check for auto-send (server), 4. MCData control indication (server to client 1), 5. MCData delivery to recipient(s) (server), 6. MCData indication (server to client 2). + +**Figure 7.6.2.2.2-1: Automatic transmission for SDS** + +1. MCData user selects the data to transmit and the recipient MCData user or MCData group. The MCData user at MCData client 1 may include a functional alias used within the SDS data transmission. + 2. MCData client checks for MCData user's permission to transmit data and checks if the data size is less than the maximum data size for SDS. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.4.2.2, 7.4.2.3, 7.4.2.5 or 7.4.2.6. + 3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit and the data size in the received transmission request does not exceed the maximum data size for SDS. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user. + 4. MCData server may send one of the following MCData control indications: + - a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent. + - b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. + - c) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued". +- Otherwise continue with step 5. +5. MCData server automatically transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2. + 6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval: + - a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list . + - b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list. + +#### 7.6.2.3 Send data with mandatory download + +##### 7.6.2.3.1 General + +The mandatory download procedure allows a sending MCData client to send data to a receiving MCData client, where the receiving MCData client is compelled to download the data. + +##### 7.6.2.3.2 Procedure + +The procedure in figure 7.6.2.3.2-1 describes the case where MCData user is using FD. The FD is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for mandatory download. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. +2. MCData administrator has configured maximum data size for FD. +3. Maximum amount of data that a MCData user can transmit in a single request is configured. +4. Maximum amount of time that a MCData user can transmit in a single request is configured. +5. Optionally, MCData client may have an activated functional alias to be used. +6. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the 'Send data with mandatory download' procedure. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. initiate data transmit (from client 1 to server), 2. MCData transmission to MCData server (from client 1 to server), 3. Authorize request and size check for non automatic transmission (internal server step), 4. MCData control indication (dashed line from server to client 1), 5. Mandatory download transmission to recipient(s) (from server to client 2), and 6. MCData indication (dashed line from server to client 2).](aec7150315249ac202a63cc0e32323b8_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for non automatic transmission + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. Mandatory download transmission to recipient(s) + MCData server-->>MCData client 2: 6. MCData indication + +``` + +Sequence diagram illustrating the 'Send data with mandatory download' procedure. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. initiate data transmit (from client 1 to server), 2. MCData transmission to MCData server (from client 1 to server), 3. Authorize request and size check for non automatic transmission (internal server step), 4. MCData control indication (dashed line from server to client 1), 5. Mandatory download transmission to recipient(s) (from server to client 2), and 6. MCData indication (dashed line from server to client 2). + +**Figure 7.6.2.3.2-1: Send data with mandatory download** + +1. MCData user selects the data to transmit, the recipient MCData user or MCData group and the indication for mandatory download. The MCData user at MCData client 1 may include a functional alias used within the FD data transfer. +2. MCData client has checked for MCData user's permission to transmit data. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.5.2.4, 7.5.2.5, 7.5.2.6 or 7.5.2.7 and including the mandatory download indication. +3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit, the data size in the received transmission request is within the maximum size allowed for FD transmission and is within the maximum amount of time that a MCData user can transmit in a single request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user. +4. MCData server may send one of the following MCData control indications: + +- a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent. +- b) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit size". +- c) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time". +- d) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. +- e) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued". + +Otherwise continue with step 5. + +- 5. MCData server transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client receives the data automatically). +- 6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval: + - a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list . + - b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list. + +#### 7.6.2.4 Send data without mandatory download + +##### 7.6.2.4.1 General + +The send data without mandatory download procedure allows the receiving MCData client to accept download, defer download (i.e. no response) or refuse (e.g. by the user deleting the notification item) the data sent from the sending MCData client. + +##### 7.6.2.4.2 Procedure + +The procedure in figure 7.6.2.4.2-1 describes the case where MCData user selected data is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for downloading with recipient MCData user consent. + +Pre-conditions: + +- 1. MCData user is configured with permission to transmit data. +- 2. Maximum amount of data or time that an MCData user can transmit in a single request is configured. +- 3. Time limit for the temporarily stored data waiting to be delivered to a receiving user is configured. +- 4. Optionally, MCData client may have an activated functional alias to be used. +- 5. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the interaction between MCData client 1, MCData server, and MCData client 2 for sending data without mandatory download. The sequence starts with MCData client 1 sending a '1. initiate data transmit' message to the MCData server. The server responds with '2. MCData transmission to MCData server'. The server then performs '3. Authorize request and size check for non automatic transmission'. A dashed arrow labeled '4. MCData control indication' points from the server to MCData client 1. The server then sends '5. Transmission to recipient(s) for downloading after user consent' to MCData client 2. Finally, a dashed arrow labeled '6. MCData indication' points from the server to MCData client 2.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for non automatic transmission + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. Transmission to recipient(s) for downloading after user consent + MCData server-->>MCData client 2: 6. MCData indication + +``` + +Sequence diagram illustrating the interaction between MCData client 1, MCData server, and MCData client 2 for sending data without mandatory download. The sequence starts with MCData client 1 sending a '1. initiate data transmit' message to the MCData server. The server responds with '2. MCData transmission to MCData server'. The server then performs '3. Authorize request and size check for non automatic transmission'. A dashed arrow labeled '4. MCData control indication' points from the server to MCData client 1. The server then sends '5. Transmission to recipient(s) for downloading after user consent' to MCData client 2. Finally, a dashed arrow labeled '6. MCData indication' points from the server to MCData client 2. + +**Figure 7.6.2.4.2-1: Send data without mandatory download** + +1. MCData user selects the data to transmit and the recipient MCData user or MCData group and does not select the mandatory download indication. The MCData user at MCData client 1 may include a functional alias used within the data transmission. + 2. MCData client has checked for MCData user's permission to transmit data and the data size is within the maximum data size allowed. The MCData client calculates the total transmission request size and determines to select procedure described in subclause 7.5.2.4, 7.5.2.5, 7.5.2.6 or 7.5.2.7 and without including the mandatory download indication. + 3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit, the data size in the received transmission request is within the maximum data size allowed and is within the maximum amount of time that a MCData user can transmit in a single request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user. + 4. MCData server may send one of the following control indications: + - a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent. + - b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. + - c) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission requests and sends the rejection control indication "Rejected due to exceeding data transmit size". + - d) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request (applies to DS only), the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time". + - e) MCData server may queue the data transmit request for later transmission with a control indication "Request to transmit is queued". +- Otherwise, continue with step 5. +5. MCData server transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client may receive the data automatically). + 6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval: + +- a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list . +- b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list. + +#### 7.6.2.5 Accessing list of deferred data group communications + +##### 7.6.2.5.1 General + +This procedure allows an MCData client to obtain a list of deferred data communications. + +##### 7.6.2.5.2 Procedure + +The procedure in figure 7.6.2.5.2-1 describes the case where the recipient MCData client receives the list of available temporarily stored data waiting to download for the deferred data group communications. + +Pre-conditions: + +1. MCData server has temporarily stored data for the deferred data group communications e.g. due to recipient MCData client deferred to download. + +![Sequence diagram showing the procedure for accessing the list of deferred data group communications. The diagram involves two lifelines: MCData client 1 and MCData server. The sequence of messages is: 1. Internal call on MCData client 1: 'Get the list of deferred data group communications'; 2. MCData client 1 sends 'MCData get deferred list request' to MCData server; 3. MCData server returns 'MCData get deferred list response' to MCData client 1; 4. Internal call on MCData client 1: 'Notify'.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + Note left of MCData client 1: 1. Get the list of deferred data group communications + MCData client 1->>MCData server: 2. MCData get deferred list request + MCData server-->>MCData client 1: 3. MCData get deferred list response + Note left of MCData client 1: 4. Notify +``` + +Sequence diagram showing the procedure for accessing the list of deferred data group communications. The diagram involves two lifelines: MCData client 1 and MCData server. The sequence of messages is: 1. Internal call on MCData client 1: 'Get the list of deferred data group communications'; 2. MCData client 1 sends 'MCData get deferred list request' to MCData server; 3. MCData server returns 'MCData get deferred list response' to MCData client 1; 4. Internal call on MCData client 1: 'Notify'. + +**Figure 7.6.2.5.2-1: Accessing list of deferred data group communications** + +1. MCData user initiates the request to get the list of temporarily stored data for the deferred data group communications on the MCData server e.g. due to recipient MCData client deferred to download. +2. MCData client sends a MCData get deferred list request to the MCData server. +3. MCData server generates the list of temporarily stored data for the affiliated group(s), available to download for the requesting MCData client and sends the list in the MCData get deferred list response. +4. MCData client notifies the list of temporarily stored data for the deferred data group communications, upon which the MCData user may decide to retrieve the corresponding data. + +## 7.7 Communication release + +### 7.7.1 General + +The subclauses below describe the MCData communication release procedures, which may be initiated either by the sender or the MCData server or the authorized MCData user. + +### 7.7.2 Communication release for on-network + +#### 7.7.2.1 Information flows for communication release + +##### 7.7.2.1.1 MCData communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.1-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.1-1: MCData communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| MCData ID | M | MCData ID on which the communication is to be released | + +##### 7.7.2.1.2 MCData communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.2-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.2-1: MCData communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| MCData ID | M | MCData ID on which the communication is released | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.3 MCData communication release request (group communication using media plane) + +Table 7.7.2.1.3-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.3-1: MCData communication release request (group communication using media plane)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| MCData group ID | M | MCData group ID on which the communication is to be released | + +##### 7.7.2.1.4 MCData communication release response (group communication using media plane) + +Table 7.7.2.1.4-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.4-1: MCData communication release response (group communication using media plane)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| MCData group ID | M | MCData group ID on which the communication is released | +| Release confirmation | M | Communication released or not indication | + +7.7.2.1.5 Void + +7.7.2.1.6 Void + +7.7.2.1.7 Void + +7.7.2.1.8 MCData server communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.8-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in one-to-one communication. + +**Table 7.7.2.1.8-1: MCData server communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release Reason | M | Indicates reason for the release | + +7.7.2.1.9 MCData server communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.9-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.9-1: MCData server communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------| +| MCData ID | M | MCData ID to which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +7.7.2.1.10 MCData server communication release request (group communication using media plane) + +Table 7.7.2.1.10-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in group communication. + +**Table 7.7.2.1.10-1: MCData server communication release request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| MCData group ID | M | MCData group ID on which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.11 MCData server communication release response (group communication using media plane) + +Table 7.7.2.1.11-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.11-1: MCData server communication release response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------| +| MCData ID | M | MCData ID to which the communication is released | +| MCData group ID | M | MCData group ID on which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.12 Void + +##### 7.7.2.1.13 MCData release intent request (one-to-one communication using media plane) + +Table 7.7.2.1.13-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.7.2.1.13-1: MCData release intent request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the one-to-one communication | +| Conversation Identifier | M | Identifies the conversation | +| Request for more info | O | Indicates what MCData server needs more information (e.g. to know the remaining data volume to transmit) about the communication which has been identified to be released | + +##### 7.7.2.1.14 MCData more information response (one-to-one communication using media plane) + +Table 7.7.2.1.14-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.14-1: MCData more information response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the one-to-one communication | +| Conversation Identifier | M | Identifies the conversation | +| More info | M | Information as requested by MCData server | + +##### 7.7.2.1.15 MCDATA release intent request (group communication using media plane) + +Table 7.7.2.1.15-1 describes the information flow for MCDATA release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCDATA server to the MCDATA client. + +**Table 7.7.2.1.15-1: MCDATA release intent request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user who is the originator of the group communication | +| Conversation Identifier | M | Identifies the conversation | +| MCDATA group ID | M | MCDATA group ID on which the communication is released | +| Request for more info | O | Indicates what MCDATA server needs more information about the communication which has been identified to be released | + +##### 7.7.2.1.16 MCDATA more information response (group communication using media plane) + +Table 7.7.2.1.16-1 describes the information flow for MCDATA more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCDATA client to the MCDATA server and from MCDATA server to authorized MCDATA user. + +**Table 7.7.2.1.16-1: MCDATA more information response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user who is originator of the group communication | +| Conversation Identifier | M | Identifies the conversation | +| MCDATA group ID | M | MCDATA group ID on which the communication is released | +| More info | M | Information as requested by MCDATA server | + +##### 7.7.2.1.17 MCDATA auth user communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.17-1 describes the information flow for MCDATA auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCDATA user to the MCDATA server. + +**Table 7.7.2.1.17-1: MCDATA auth user communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Request for more info | O | Indicates what MCDATA server needs more information about the communication which has been identified to be released | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.18 MCDATA auth user communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.18-1 describes the information flow for the MCDATA server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCDATA server to the authorized MCDATA user. + +**Table 7.7.2.1.18-1: MCData auth user communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.19 MCData auth user communication release request (group communication using media plane) + +Table 7.7.2.1.19-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server. + +**Table 7.7.2.1.19-1: MCData auth user communication release request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is to be released | +| Request for more info | O | Indicates what MCData server needs more information about the communication which has been identified to be released | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.20 MCData auth user communication release response (group communication using media plane) + +Table 7.7.2.1.20-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user. + +**Table 7.7.2.1.20-1: MCData auth user communication release response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is to be released | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.21 MCData request for extension + +Table 7.7.2.1.21-1 describes the information flow for the MCData request for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.21-1: MCData request for extension** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------| +| Conversation Identifier | M | Identifies the conversation | + +##### 7.7.2.1.22 MCData response for extension + +Table 7.7.2.1.22-1 describes the information flow for the MCData response for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server and MCData client to the MCData server and from MCData server to MCData client. + +**Table 7.7.2.1.22-1: MCData response for extension** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Extension response | M | Indicates whether request for extension has been accepted or not | + +#### 7.7.2.2 MCData user initiated communication release + +##### 7.7.2.2.1 General + +During MCData communication, a transmitting participant can at any time indicate to stop transmission to the MCData server. + +##### 7.7.2.2.2 Release of MCData communication using media plane + +###### 7.7.2.2.2.1 General + +The subclause describes the procedure for MCData user initiated MCData communication release where MCData communication is established as SDS using media plane or SDS session or file distribution using media plane. + +NOTE: The release of MCData communication over MBMS is out of scope of the current specification. + +###### 7.7.2.2.2.2 Procedure + +The procedure in figure 7.7.2.2.2.2-1 describes signalling control plane procedure for the case where MCData communication is ongoing and transmitting participant initiates MCData communication release. The procedure is applicable for one-to-one and group MCData communications. + +Pre-conditions: + +1. MCData users on MCData client 1 and client 2 are already registered for receiving MCData service. +2. MCData communication is established between MCData client 1 and MCData client 2 and MCData client1 is the initiator of the MCData communication. + +![Sequence diagram showing the release of MCData communication using media plane. The diagram involves three main entities: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. Initiate communication termination (from client 1 to server), 2. MCData communication release request (from client 1 to server), 3. MCData communication release request (from server to client 2), 4. Notify user (internal to client 2), 5. MCData communication release response (from client 2 to server), 6. MCData communication release response (from server to client 1), 7. Release media plane resources associated with MCData communication (internal to server), 8. Notify user (internal to client 1).](e787e02d9214556476d95941bda1d350_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate communication termination + MCData client 1->>MCData server: 2. MCData communication release request + MCData server->>MCData client 2: 3. MCData communication release request + Note right of MCData client 2: 4. Notify user + MCData client 2->>MCData server: 5. MCData communication release response + MCData server->>MCData client 1: 6. MCData communication release response + Note right of MCData server: 7. Release media plane resources associated with MCData communication + Note left of MCData client 1: 8. Notify user + +``` + +Sequence diagram showing the release of MCData communication using media plane. The diagram involves three main entities: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. Initiate communication termination (from client 1 to server), 2. MCData communication release request (from client 1 to server), 3. MCData communication release request (from server to client 2), 4. Notify user (internal to client 2), 5. MCData communication release response (from client 2 to server), 6. MCData communication release response (from server to client 1), 7. Release media plane resources associated with MCData communication (internal to server), 8. Notify user (internal to client 1). + +**Figure 7.7.2.2.2.2-1: Release of MCData communication using media plane** + +1. MCData user at MCData client 1 requests to release ongoing MCData communication. +2. MCData client 1 sends MCData communication release request towards MCData server, for tearing down the communication with the other MCData client(s). +3. MCData server sends MCData communication release request to all the participants of the MCData communication. +4. Recipient MCData clients notifies respective MCData user about the release of MCData communication. +5. MCData clients receiving the MCData communication release request provide communication release response back towards MCData server. +6. MCData server sends MCData communication release response back to MCData client 1. +7. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released. +8. MCData client 1 notifies the MCData user about the communication release. + +##### 7.7.2.2.3 Release of MCData communication using HTTP + +NOTE: The backward compatibility handling of this procedure is outside the scope of the present document. + +#### 7.7.2.3 MCData server initiated communication release without prior indication + +##### 7.7.2.3.1 General + +MCData server initiates the release of an ongoing MCData communication, since at least one of the communication release conditions are met e.g. lack of bearer capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server either pre-empts the MCData communication without giving prior indication to MCData client or notifies the intent of release to the MCData client initiating communication. Latter scenario allows the MCData user to request for extension of MCData communication and defer the communication release. + +##### 7.7.2.3.2 Release of MCData communication using media plane + +###### 7.7.2.3.2.1 General + +The subclause describes the procedure for MCData server initiated MCData communication release without prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane. + +NOTE: The release of MCData communication over MBMS is out of scope of the current specification. + +###### 7.7.2.3.2.2 Procedure + +The procedure in figure 7.7.2.3.2.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates the communication release. The procedure is applicable for one-to-one and group communication. + +Pre-conditions: + +1. MCData users on MCData client 1, client 2 and client 3 are already registered for receiving MCData service. +2. A MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. A MCData communication is ongoing between MCData client 1, client 2 and client 3. + +![Sequence diagram showing the MCDData server initiated release of MCDData communication using media plane. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client 3. The process involves the server sending release requests to clients, clients notifying users, clients sending release responses, and finally releasing media plane resources.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + + Note right of MCData server: 1. Release MCData communication + Note right of MCData server: 2. Determine MCData communication participants and generate communication release request + MCData server->>MCData client 1: 3a. MCData server communication release request + MCData server->>MCData client 2: 3b. MCData server communication release request + MCData server->>MCData client 3: 3c. MCData server communication release request + Note left of MCData client 1: 4a. Notify user + Note left of MCData client 2: 4b. Notify user + Note left of MCData client 3: 4c. Notify user + MCData client 1->>MCData server: 5a. MCData server communication release response + MCData client 2->>MCData server: 5b. MCData server communication release response + MCData client 3->>MCData server: 5c. MCData server communication release response + Note over all participants: 6. Release media plane resources associated with the MCData communication +``` + +Sequence diagram showing the MCDData server initiated release of MCDData communication using media plane. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client 3. The process involves the server sending release requests to clients, clients notifying users, clients sending release responses, and finally releasing media plane resources. + +**Figure 7.7.2.3.2.2-1: MCData server initiated release of MCData communication using media plane** + +1. MCData server would like to release the ongoing MCData communication, identified by conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on configuration, MCData server decides to pre-empt the MCData communication without giving prior indication to MCData client 1. +2. MCData server identifies the participants of the ongoing MCData communication and generates communication release request to release ongoing MCData communication. +3. MCData server sends server MCData communication release request towards each participant of the MCData communication. +4. MCData users are notified about the release of the MCData communication. +5. MCData client at each MCData communication participant sends server MCData communication release response towards the MCData server. +6. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released. + +##### 7.7.2.3.3 Void + +#### 7.7.2.4 MCData server initiated communication release with prior indication + +##### 7.7.2.4.1 General + +The subclause describes the procedure for MCData server initiated MCData communication release with prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane or file distribution using HTTP. + +##### 7.7.2.4.2 Procedure + +The procedure in figure 7.7.2.4.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates communication release. As a result of configuration check, MCData server notifies the intent to release MCData communication, optionally requesting for more information (e.g. to know the remaining data volume to transmit) from the MCData client initiating MCData communication. + +Pre-conditions: + +1. MCData user on MCData client 1 is already registered for receiving MCData service. +2. MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. MCData communication may be ongoing between MCData participants and MCData client 1 is the initiator of the communication. +4. MCData administrator has configured the time for which MCData server needs to wait for extension request from the MCData user. + +![Sequence diagram showing the procedure for MCData server initiated communication release with prior indication. The diagram involves two lifelines: MCData client 1 and MCData server. The sequence of messages is: 1. Release MCData communication (from server to client), 2. MCData release intent request (from server to client), 3. Notify user (internal to client), 4. MCData more information response (from client to server), 5. Request for extension (internal to client), 6. MCData request for extension (from client to server), 7. Policy assertion (internal to server), 8. MCData response for extension (from server to client).](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + Note right of MCData server: 1. Release MCData communication + MCData server->>MCData client 1: 2. MCData release intent request + Note left of MCData client 1: 3. Notify user + MCData client 1-->>MCData server: 4. MCData more information response + Note left of MCData client 1: 5. Request for extension + MCData client 1->>MCData server: 6. MCData request for extension + Note right of MCData server: 7. Policy assertion + MCData server->>MCData client 1: 8. MCData response for extension +``` + +Sequence diagram showing the procedure for MCData server initiated communication release with prior indication. The diagram involves two lifelines: MCData client 1 and MCData server. The sequence of messages is: 1. Release MCData communication (from server to client), 2. MCData release intent request (from server to client), 3. Notify user (internal to client), 4. MCData more information response (from client to server), 5. Request for extension (internal to client), 6. MCData request for extension (from client to server), 7. Policy assertion (internal to server), 8. MCData response for extension (from server to client). + +**Figure 7.7.2.4.2-1: MCData server initiates communication release with prior indication** + +1. MCData server releases the ongoing MCData communication, identified by the conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server notifies the intent to release MCData communication. + +2. MCData server sends the MCData release intent request towards the communication initiating MCData client 1. MCData server may include request for more information (e.g. to know the remaining data volume to transmit). +3. MCData client 1 informs MCData user about the intent to release communication. +4. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive MCData request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps. +5. MCData user at MCData client 1 requests for extension of the ongoing MCData communication. +6. MCData client 1 sends MCData request for extension of the MCData communication. +7. Upon receiving the MCData request for extension of MCData communication from the MCData client 1, MCData server asserts policies to accept or reject the request for extension. +8. MCData server sends MCData response for extension with success or failure result to MCData client 1. MCData communication will continue if MCData server accepted the request for extension from MCData client 1. Otherwise, MCData communication is released according to procedures described in subclause 7.7.2.3. + +#### 7.7.2.5 Authorized MCData user initiated communication release without prior indication + +##### 7.7.2.5.1 General + +An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication without prior indication to the initiator MCData client. + +##### 7.7.2.5.2 Procedure + +The procedure in figure 7.7.2.5.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release without prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. + +Pre-conditions: + +1. An authorized MCData user on MCData client is already registered for receiving MCData service. +2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication. + +![Sequence diagram showing the release of an ongoing MCData communication initiated by an authorized MCData client without prior indication to the initiator.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant AMC as Authorized MCData client + participant MS as MCData Server + participant MC as MCData client + Note left of AMC: 1. Release MCData communication + AMC->>MS: 2. MCData auth user communication release request + Note right of MS: 3. Validate request + Note right of MS: 4. Release communication + MS->>AMC: 5. MCData auth user communication release response + +``` + +The diagram illustrates a sequence of interactions between three entities: an Authorized MCData client, an MCData Server, and an MCData client. The process begins with the Authorized MCData client sending a 'Release MCData communication' message (1). This is followed by a 'MCData auth user communication release request' (2) from the client to the server. The server then performs a 'Validate request' (3) and a 'Release communication' (4). Finally, the server sends a 'MCData auth user communication release response' (5) back to the client. + +Sequence diagram showing the release of an ongoing MCData communication initiated by an authorized MCData client without prior indication to the initiator. + +**Figure 7.7.2.5.2-1: An authorized MCData user initiates communication release without prior indication** + +1. An authorized MCData user requests to release the ongoing MCData communication, without providing prior indication to the initiator of the MCData communication, MCData client 1. +2. An authorized MCData client sends MCData auth user communication release request towards MCData server identifying the MCData communication to release. The request also includes indication to the MCData server to release MCData communication without prior indication to the initiator of the MCData communication, MCData client 1. +3. MCData server validates the user from whom the MCData communication release request is received and checks whether the requesting MCData user is authorized to release communication or not. +4. If the user is authorized to release communication, then MCData server releases the ongoing MCData communication according to procedures described in subclause 7.7.2.3. +5. MCData server sends MCData auth user communication release response containing the result of MCData communication release back to authorized MCData client 1. + +#### 7.7.2.6 Authorized MCData user initiated communication release with prior indication + +##### 7.7.2.6.1 General + +An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication with prior indication to the initiator MCData client. A prior indication allows initiator MCData client to request for extension for the MCData communication. + +##### 7.7.2.6.2 Procedure + +The procedure in figure 7.7.2.6.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release with prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. An initiator MCData user optionally decides to request for the extension of the ongoing communication. + +Pre-conditions: + +1. An authorized MCData user on MCData client is already registered for receiving MCData service. +2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication +3. MCData client 1 is the initiator of the MCData communication. + +![Sequence diagram showing the interaction between MCData client 1, MCData server, and Authorized MCData Client for a communication release process.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Authorized MCData Client + + Note right of Authorized MCData Client: 1. Release MCData communication + Authorized MCData Client->>MCData server: 2. MCData auth user communication release request + Note right of MCData server: 3. Validate request + MCData server->>MCData client 1: 4. McData release intent request + Note right of MCData client 1: 5. Notify user + MCData client 1-->>MCData server: 6. MCData more information response + MCData server-->>Authorized MCData Client: 7. MCData more information response + Note right of MCData client 1: 8. Request for extension + MCData client 1->>MCData server: 9. MCData request for extension + MCData server->>Authorized MCData Client: 10. MCData request for extension + Note right of Authorized MCData Client: 11. Notify user + Authorized MCData Client->>MCData server: 12. MCData response for extension request + MCData server->>MCData client 1: 13. MCData response for extension request + Note right of MCData client 1: 14. Release communication + MCData server->>Authorized MCData Client: 15. MCData auth user communication release response + +``` + +Sequence diagram showing the interaction between MCData client 1, MCData server, and Authorized MCData Client for a communication release process. + +**Figure 7.7.2.6.2-1: An authorized MCData user initiates communication release with prior indication** + +1. An authorized MCData user requests to release the ongoing MCData communication by providing prior indication to the initiator of MCData communication, MCData client 1. +2. An authorized MCData client sends MCData auth user communication release request towards MCData server including the communication identifier identifying the MCData communication to release. Authorized MCData client may include request for more information (e.g. to know the remaining data volume to transmit). The request also includes indication to MCData server to release MCData communication with prior indication to the initiator MCData client. +3. MCData server validates the user from whom the communication release request is received and checks whether the requesting user is authorized to release communication or not. +4. If the user is authorized to release communication, then the MCData server sends MCData release intent request, may be including the reason for the release. MCData server may include request for more information as received in the request from the authorized MCData client. +5. MCData client informs MCData user about the intent to release communication by the authorized MCData user. +6. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. +7. MCData server forwards the MCData more information response to the authorized MCData client. + +**NOTE:** Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps. + +8. MCData user at MCData client 1 decides to request for extension of the ongoing MCData communication. + +- 9 and 10. MCData client sends MCData request for extension towards MCData server. And MCData server forwards the MCData request for extension towards the authorized MCData client. +11. Authorized MCData client notifies the authorized user about the incoming request for extension. An authorized MCData user decides to accept or reject the request for extension. +- 12 and 13. Authorized MCData user decision is sent in MCData response for extension request towards the MCData server. MCData server forwards the MCData response for extension request to MCData client 1. +14. MCData communication will continue if the authorized user accepted the request for extension from MCData client 1. Otherwise, MCData communication will be released according to procedures described in subclause 7.7.2.3. +15. After MCData communication is released, MCData server sends the MCData auth user communication release response back to the authorized MCData client. + +## 7.8 Conversation management + +### 7.8.1 General + +Conversation management is a collection of related MCData transmissions for a given activity. Conversation management associates SDS and FD communication transmission and present them as a single thread to the user. + +Conversation management for on-network is described in clause 7.8.2 and for off-network in clause 7.8.3. Off-network conversation management is based on ProSe capabilities as described in clause 7.16. + +### 7.8.2 Conversation management for on-network + +#### 7.8.2.1 Information flows for conversation management + +The information flow parameters related to conversation management are as described in the subclauses 7.4.2.1 and subclauses 7.5.2.1.5, 7.5.2.1.6, 7.5.2.1.7, 7.5.2.1.8, 7.5.2.1.9, 7.5.2.1.10, 7.5.2.1.11, 7.5.2.1.12, and 7.5.2.1.13. + +#### 7.8.2.2 One-to-one conversation management + +##### 7.8.2.2.1 Procedure + +The procedure for an MCData user to associate multiple MCData transmissions between a pair of users for a given activity is illustrated in figure 7.8.2.2.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1 and 2 are registered for receiving MCData service. + +![Sequence diagram illustrating one-to-one conversation management between MCData client 1, MCData server, and MCData client 2.](2f58bcce74146d4d983070d93be12291_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate conversation + MCData client 1->>MCData server: + Note right of MCData server: 2. Procedure(s) of one-to-one SDS or one-to-one FD or combination of both + MCData server->>MCData client 2: + MCData server->>MCData client 1: +``` + +The diagram is a sequence diagram with three lifelines: MCData client 1, MCData server, and MCData client 2. The sequence of messages is as follows: 1. MCData client 1 sends a message to MCData server labeled '1. Initiate conversation'. 2. MCData server sends a message to MCData client 2 labeled '2. Procedure(s) of one-to-one SDS or one-to-one FD or combination of both'. 3. MCData server sends a return message to MCData client 1. + +Sequence diagram illustrating one-to-one conversation management between MCData client 1, MCData server, and MCData client 2. + +Figure 7.8.2.2.1-1: One-to-one conversation management + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of one-to-one SDS or one-to-one FD or combination of both these procedures can be executed. + +#### 7.8.2.3 Group conversation management + +##### 7.8.2.3.1 Procedure + +The procedure for an MCData user to associate multiple MCData transmissions between users of a group for a given activity is illustrated in figure 7.8.2.3.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service. +2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service. + +![Sequence diagram for Group conversation management. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client n. Step 1: Initiate conversation from client 1. Step 2: Procedure(s) of Group SDS or Group FD or combination of both, shown as a horizontal bar across all lifelines.](a51105b2031bad93b818b82f071c6add_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Initiate conversation + MCData client 1->>MCData server: + Note right of MCData server: 2. Procedure(s) of Group SDS or Group FD or combination of both + MCData server-->>MCData client 1: + MCData server-->>MCData client 2: + MCData server-->>MCData client n: +``` + +Sequence diagram for Group conversation management. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client n. Step 1: Initiate conversation from client 1. Step 2: Procedure(s) of Group SDS or Group FD or combination of both, shown as a horizontal bar across all lifelines. + +Figure 7.8.2.3.1-1: Group conversation management + +1. The user at MCData client 1 initiates conversation. A unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of group SDS or group FD or combination of both these procedures can be executed. + +### 7.8.3 Conversation management for off-network + +#### 7.8.3.1 One-to-one conversation management + +##### 7.8.3.1.1 Procedure + +The procedure for an MCData user to associate multiple off-network MCData transmissions between a pair of users is illustrated in figure 7.8.3.1.1-1. + +Pre-conditions: + +1. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable. + +2. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using ProSe Discovery procedures. + +![Sequence diagram for one-to-one conversation management between MCData client 1 and MCData client 2.](a3472689858b068ef469213682965325_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note left of MCData client 1: 1. Initiate conversation + Note right of MCData client 2: 2. Procedure(s) of one-to-one SDS or one-to-one FD or both +``` + +The diagram illustrates a sequence of two steps between MCData client 1 and MCData client 2. Step 1, 'Initiate conversation', is initiated by MCData client 1. Step 2, 'Procedure(s) of one-to-one SDS or one-to-one FD or both', is initiated by MCData client 2. + +Sequence diagram for one-to-one conversation management between MCData client 1 and MCData client 2. + +**Figure 7.8.3.1.1-1: One-to-one conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of one-to-one SDS or one-to-one FD or a combination of these can be executed. + +#### 7.8.3.2 Group conversation management + +##### 7.8.3.2.1 Procedure + +The procedure for an MCData user to associate multiple off-network MCData transmissions between users of a group is illustrated in figure 7.8.3.2.1-1. + +Pre-conditions: + +1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +2. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram for group conversation management between MCData client 1, MCData client 2, and MCData client n.](35127fe87029df6f5f0b2ee85f6193f1_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Initiate conversation + Note right of MCData client n: 2. Procedure(s) of Group SDS or Group FD or both +``` + +The diagram illustrates a sequence of two steps between MCData client 1, MCData client 2, and MCData client n. Step 1, 'Initiate conversation', is initiated by MCData client 1. Step 2, 'Procedure(s) of Group SDS or Group FD or both', is initiated by MCData client n. + +Sequence diagram for group conversation management between MCData client 1, MCData client 2, and MCData client n. + +**Figure 7.8.3.2.1-1: Group conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent + +of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. + +2. The procedure of group SDS or group FD or combination of both can be executed. + +## 7.9 Enhanced status + +### 7.9.1 General + +Enhanced status corresponds to information specific to the activities performed by the mission critical service users during their operation(s) e.g. available, in operation on site, going to the operation site, or just arrived. + +Enhanced status for on-network is described in clause 7.9.3 and for off-network in clause 7.9.4. Off-network enhanced status is based on ProSe capabilities as described in clause 7.16. + +### 7.9.2 Preset values for enhanced status + +The enhanced status information i.e. the set of possible values corresponding to the activities of the MCData user, shall be configured by the MCData administrator. The configuration of status values is applicable on a per-group basis, and therefore shall be part of the MCData group configuration data as described in Annex A.4. + +The configuration mechanism shall allow the MCData administrator to configure a minimum of 32 possible values and allow up to 65536 separate values. The set of values may be divided into a fixed set of values defined by 3GPP standards which are common across all MCData systems, and a set which may be freely configured for any purpose. + +### 7.9.3 Enhanced status for on-network + +#### 7.9.3.1 Sharing enhanced status information + +##### 7.9.3.1.1 Procedure + +The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.3.1.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service. +2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service. +3. The MCData group is pre-configured with the possible values for enhanced status information. + +![Sequence diagram illustrating the sharing of enhanced status information. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client n. Step 1: MCData client 1 sends a message '1. Select enhanced status information' to the MCData server. Step 2: A horizontal bar labeled '2. Procedure of group standalone SDS using signalling control plane' spans across all lifelines. Step 3: MCData client 1 sends a message '3. Notify enhanced status information' to MCData client 2. Step 4: MCData client 1 sends a message '3. Notify enhanced status information' to MCData client n.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Select enhanced status information + Note over MCData client 1, MCData server, MCData client 2, MCData client n: 2. Procedure of group standalone SDS using signalling control plane + Note right of MCData client 1: 3. Notify enhanced status information + Note right of MCData client 1: 3. Notify enhanced status information +``` + +Sequence diagram illustrating the sharing of enhanced status information. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client n. Step 1: MCData client 1 sends a message '1. Select enhanced status information' to the MCData server. Step 2: A horizontal bar labeled '2. Procedure of group standalone SDS using signalling control plane' spans across all lifelines. Step 3: MCData client 1 sends a message '3. Notify enhanced status information' to MCData client 2. Step 4: MCData client 1 sends a message '3. Notify enhanced status information' to MCData client n. + +**Figure 7.9.3.1.1-1: Sharing enhanced status information** + +1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group. +2. The procedure of group standalone SDS using signalling control plane as described in subclause 7.4.2.5, is used to deliver the enhanced status information. +3. The MCData users at MCData client 2 and n are notified of the enhanced status information. + +### 7.9.4 Enhanced status for off-network + +#### 7.9.4.1 Sharing enhanced status information + +##### 7.9.4.1.1 Procedure + +The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.4.1.1-1. + +Pre-conditions: + +1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +2. MCData client 1, 2 and n are members of the same MCData group. +3. The MCData group is pre-configured with the possible values for enhanced status information. + +![Sequence diagram showing the sharing of enhanced status information between MCData clients. MCData client 1 initiates the process by selecting enhanced status information. All clients (1, 2, and n) then participate in a procedure of off-network group standalone SDS using the signalling control plane. Finally, MCData clients 2 and n are notified of the enhanced status information.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Select enhanced status information + Note over MCData client 1, MCData client 2, MCData client n: 2. Procedure of off-network group standalone SDS using signalling control plane + Note right of MCData client 2: 3. Notify enhanced status information + Note right of MCData client n: 3. Notify enhanced status information +``` + +Sequence diagram showing the sharing of enhanced status information between MCData clients. MCData client 1 initiates the process by selecting enhanced status information. All clients (1, 2, and n) then participate in a procedure of off-network group standalone SDS using the signalling control plane. Finally, MCData clients 2 and n are notified of the enhanced status information. + +**Figure 7.9.4.1.1-1: Sharing enhanced status information** + +1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group. +2. The procedure of off-network group standalone SDS using signalling control plane as described in subclause 7.4.3.4, is used to deliver the enhanced status information. +3. The MCData users at MCData client 2 and n are notified of the enhanced status information. + +## 7.10 MCData emergency alert (on-network and off-network) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.10 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group ID is the MCData Group ID; and +- The MC service user profile index is the MCData user profile index. + +### 7.10a MCData ad hoc group emergency alert (on-network) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.10.3 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group ID is the MCData Group ID; and +- The MC service user profile index is the MCData user profile index. + +## 7.11 User authentication and authorization for MCData service + +NOTE: Flow 7.11-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [13] defines the specific user authentication and authorization architecture required by the MCData service in order to realize the MCData user authentication and authorization requirements as defined in 3GPP TS 22.280 [2]. + +A procedure for user authentication is illustrated in figure 7.11-1. The user authentication is performed based on the procedure specified in subclause 10.6 of 3GPP TS 23.280 [5]. + +![Sequence diagram illustrating MCData user authentication and registration in a single domain. The diagram shows six lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCData server. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5].', involves the MCData client, Identity management client, Signalling user agent, SIP core, and Identity management server. Step 2, 'The MCData client performs the service authorization with the MCData server.', involves the MCData client and MCData server.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant Identity management client + participant Signalling user agent + participant SIP core + participant Identity management server + participant MCData server + + Note right of Identity management client: 1. User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5]. + Note right of MCData client: 2. The MCData client performs the service authorization with the MCData server. + +``` + +Sequence diagram illustrating MCData user authentication and registration in a single domain. The diagram shows six lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCData server. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5].', involves the MCData client, Identity management client, Signalling user agent, SIP core, and Identity management server. Step 2, 'The MCData client performs the service authorization with the MCData server.', involves the MCData client and MCData server. + +**Figure 7.11-1: MCData user authentication and registration, single domain** + +1. The user authentication is performed as per the general user authentication procedure specified in subclause 10.6 of 3GPP TS 23.280 [5]. +2. MCData client performs the MCData service authorization for the user. Step 2 utilizes the results of step 1. + +## 7.12 MCData resource management (on-network) + +### 7.12.1 General + +Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [5]. + +### 7.12.2 Void + +## 7.13 Operations on MCData message store + +The MCData message store allows an MCData user to deposit his MCData communication information (i.e. messages or files) securely and permanently for later retrieval. During an active MCData communication, a message or a file with its associated metadata is deposited as an object in the MCData message store with an object identifier; this object identifier enabling a direct access to that object. The objects in the MCData message store are managed from both the MCData server and the message store client. + +Each MCData user is allocated a dedicated and secured storage area (i.e. with a user account) in the MCData message store. All MCData communications of a MCData user can be stored in his dedicated storage area. The access to this secured storage area is possible only after successful authentication and authorization procedures. A message store client can create a local copy of the stored objects into the device by synchronizing with the MCData message store for the MCData user using the device. + +### 7.13.1 MCData message store structure + +MCData message store supports a tree like architecture to securely store MCData communications for the MCData users. Figure 7.13.1 below illustrates the high-level structure of a MCData message store: + +![Diagram illustrating the MCData message store structure. At the top is a rectangular box labeled 'MCData message store (Common Root)'. Below it, a horizontal line branches out to three ovals labeled 'MCData User 1', 'MCData User 2', and 'MCData User n', with an ellipsis between User 2 and User n. From each user oval, a vertical line descends to a stack of three overlapping document icons, each labeled 'objects'.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +``` + +graph TD + Root["MCData message store (Common Root)"] --> User1(["MCData User 1"]) + Root --> User2(["MCData User 2"]) + Root --> Dots["..."] + Root --> Usern(["MCData User n"]) + User1 --> Obj1["objects"] + User2 --> Obj2["objects"] + Usern --> Objn["objects"] + +``` + +Diagram illustrating the MCData message store structure. At the top is a rectangular box labeled 'MCData message store (Common Root)'. Below it, a horizontal line branches out to three ovals labeled 'MCData User 1', 'MCData User 2', and 'MCData User n', with an ellipsis between User 2 and User n. From each user oval, a vertical line descends to a stack of three overlapping document icons, each labeled 'objects'. + +**Figure 7.13.1 Message store structure** + +As illustrated in Figure 7.13.1 all MCData user storage areas are accessed only through the common root. The authorized MCData user shall only have the access to the MCData user's storage area after the successful authentication and authorization procedures. A MCData user shall not be able to access objects stored for other MCData users. + +The MCData user shall manage his stored objects using message store client through the MCData-7 reference point. The MCData server shall use the MCData-8 reference point to deposit MCData communication information, during an active MCData communication, into the designated MCData user's storage area in the MCData message store. + +One way to manage user stored objects is using folder hierarchy structure like the popular email system today. Annex D provides a simple example of how it will look like in deployment. When the user account is created in the MCData message store, a default folder (such as Inbox) is also created to capture all the objects during an active communication. To group relevant stored objects together and provide easier navigation interactively, a MCData user can create folders in his user account. Each folder is identified by its unique folder identifier that is composed with the location of the folder and the name of the folder. A folder may have child folders to further group the stored objects in more meaningful ways. For example, the folder identifier of the default Inbox folder is /MCDataMessageStore /MCDatauser1/Inbox. The folder identifier /MCDataMessageStore/MCDatauser1/Squad1/20190225 points to a folder named 20190225 which is a child folder of Squad1 folder in the MCData user1 user account. + +NOTE: The details of how the objects are stored in the MCData message store is out of scope of the present document. + +### 7.13.2 Authentication and authorization + +The MCData message store shall authenticate the credential of MCData server or the authorized MCData user before authorizing access to the MCData user's storage area. The success of authentication and authorization shall allow access to that MCData user's storage area only. + +NOTE: The authentication and authorization aspects of MCData message store access and its operational supports are the responsibility of SA3 and thus outside the scope of the present document. + +### 7.13.3 Manage MCData message store + +#### 7.13.3.1 Information flows for managing MCData message store + +##### 7.13.3.1.1 MCData retrieve a stored object request + +Table 7.13.3.1.1-1 describes the information flow for the MCData retrieve a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.1-1: MCData retrieve a stored object request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | + +##### 7.13.3.1.2 MCData retrieve a stored object response + +Table 7.13.3.1.2-1 describes the information flow for the MCData retrieve a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.2-1: MCData retrieve a stored object response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Stored object | M | The stored object identified by the object identifier in the request. This information element shall be returned as empty when there is no stored object can be identified by the object identifier in the request | + +##### 7.13.3.1.3 MCData search stored objects request + +Table 7.13.3.1.3-1 describes the information flow for the MCData search stored objects request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.3-1: MCData search stored objects request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Search criteria | M | Any part of the stored object can be the search criteria. Linking multiple parts of a stored object as the search criteria is possible | + +##### 7.13.3.1.4 MCData search stored objects response + +Table 7.13.3.1.4-1 describes the information flow for the MCData search stored objects response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.4-1: MCData search stored objects response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Stored object(s) | M | The stored object(s) that meets the search criteria. This information element shall be returned as empty when there is no stored object can be identified by the search criteria in the request | + +##### 7.13.3.1.5 MCData update a stored object request + +Table 7.13.3.1.5-1 describes the information flow for the MCData update a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.5-1: MCData update a stored object request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | +| Metadata | M | The metadata that will be updated | + +##### 7.13.3.1.6 MCData update a stored object response + +Table 7.13.3.1.6-1 describes the information flow for the MCData update a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.6-1: MCData update a stored object response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user storage area in the MCData message store | +| Result | M | The result if the update is success or failure | + +##### 7.13.3.1.7 MCData delete a stored object request + +Table 7.13.3.1.7-1 describes the information flow for the MCData delete a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.7-1: MCData delete a stored object request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | + +##### 7.13.3.1.8 MCData delete a stored object response + +Table 7.13.3.1.8-1 describes the information flow for the MCData delete a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.8-1: MCData delete a stored object response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user storage area in the MCData message store | +| Result | M | The result if the delete is success or failure | + +##### 7.13.3.1.9 MCData synchronization request + +Table 7.13.3.1.9-1 describes the information flow for the MCData synchronization request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.9-1: MCData synchronization request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Synchronization type | M | Indicates the type of synchronization is requested. It can be a full or partial synchronization | +| Filter criteria (see NOTE) | O | The filter criteria indicate what kind of stored objects needs to be synchronized to the device local message store | +| NOTE: Filter criteria information element shall be presented if the Synchronization type is partial. | | | + +##### 7.13.3.1.10 MCData synchronization response + +Table 7.13.3.1.10-1 describes the information flow for the MCData synchronization response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.10-1: MCData synchronization response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Stored objects | M | The stored objects that need to be synchronized with the device local message store. Empty information element means no stored objects need to be synchronized | + +##### 7.13.3.1.11 MCData create a user account request + +Table 7.13.3.1.11-1 describes the information flow for the MCData create a user account request sent from the MCData server to the MCData message store. + +**Table 7.13.3.1.11-1: MCData create a user account request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------| +| MCData ID | M | The identity of the MCData user | + +##### 7.13.3.1.12 MCData create a user account response + +Table 7.13.3.1.12-1 describes the information flow for the MCData create a user account response sent from the MCData message store to the MCData server. + +**Table 7.13.3.1.12-1: MCData create a user account response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the account creation is success or failure | + +##### 7.13.3.1.13 MCData deposit an object request + +Table 7.13.3.1.13-1 describes the information flow for the MCData deposit an object request sent from the MCData server to the MCData message store. + +**Table 7.13.3.1.13-1: MCData deposit an object request** + +| Information element | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Retrieve file indication | O | Flag to instruct the MCData message store to retrieve the file to locally store in the MCData user's account | +| Object | M | The object needs to be stored | + +##### 7.13.3.1.14 MCData deposit an object response + +Table 7.13.3.1.14-1 describes the information flow for the MCData deposit an object response sent from the MCData message store to the MCData server. + +**Table 7.13.3.1.14-1: MCData deposit an object response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object Identifier | M | The object identifier that will be used to retrieve this object in the MCData message store directly. If this information element is empty it means the object is not stored | + +##### 7.13.3.1.15 MCData copy a stored object request + +Table 7.13.3.1.15-1 describes the information flow for the MCData copy a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.15-1: MCData copy a stored object request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | +| Destination folder identifier | M | Indicates where the object will be copied to | + +##### 7.13.3.1.16 MCData copy a stored object response + +Table 7.13.3.1.16-1 describes the information flow for the MCData copy a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.16-1: MCData copy a stored object response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | + +##### 7.13.3.1.17 MCData move a stored object request + +Table 7.13.3.1.17-1 describes the information flow for the MCData move a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.17-1: MCData move a stored object request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | +| Destination folder identifier | M | Indicates where the object will be moved to. | + +##### 7.13.3.1.18 MCData move a stored object response + +Table 7.13.3.1.18-1 describes the information flow for the MCData move a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.18-1: MCData move a stored object response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | + +##### 7.13.3.1.19 MCData create folder request + +Table 7.13.3.1.19-1 describes the information flow for the MCData create folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.19-1: MCData create folder request** + +| Information element | Status | Description | +|--------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Parent folder identifier | O | The parent folder identifier of the created folder | +| Folder name | O | Indicates the name of the new folder | + +##### 7.13.3.1.20 MCData create folder response + +Table 7.13.3.1.20-1 describes the information flow for the MCData create folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.20-1: MCData create folder response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | +| Folder identifier | O | The identifier of the folder that is created | + +##### 7.13.3.1.21 MCData delete folder request + +Table 7.13.3.1.21-1 describes the information flow for the MCData delete folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.21-1: MCData delete folder request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder identifier | M | The identifier of the folder to be deleted | + +##### 7.13.3.1.22 MCData delete folder response + +Table 7.13.3.1.22-1 describes the information flow for the MCData delete folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.22-1: MCData delete folder response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | + +##### 7.13.3.1.23 MCData copy folder request + +Table 7.13.3.1.23-1 describes the information flow for the MCData copy folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.23-1: MCData copy folder request** + +| Information element | Status | Description | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Source folder identifier | M | The identifier of the folder to copy from | +| Destination folder identifier | M | The identifier of the folder to copy to | +| New folder name (see NOTE) | O | Indicates the name of the new folder | +| NOTE: | If no new folder name information element is provided, the new folder name will be the same as the source folder name. | | + +##### 7.13.3.1.24 MCData copy folder response + +Table 7.13.3.1.24-1 describes the information flow for the MCData copy folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.24-1: MCData copy folder response** + +| Information element | Status | Description | +|-----------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | +| New folder identifier | M | Indicates the identifier of the new folder | + +##### 7.13.3.1.25 MCData move folder request + +Table 7.13.3.1.25-1 describes the information flow for the MCData move folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.25-1: MCData move folder request** + +| Information element | Status | Description | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Source folder identifier | M | The identifier of the folder to be moved | +| Destination folder identifier | M | The identifier of the folder to move to | +| New folder name (see NOTE) | O | Indicates the name of the new folder | +| NOTE: | If no new folder name information element is provided, the new folder name will be the same as the source folder name. | | + +##### 7.13.3.1.26 MCData move folder response + +Table 7.13.3.1.26-1 describes the information flow for the MCData move folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.26-1: MCData move folder response** + +| Information element | Status | Description | +|-----------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | +| New folder identifier | M | Indicates the identifier of the new folder | + +##### 7.13.3.1.27 MCData list folder request + +Table 7.13.3.1.27-1 describes the information flow for the MCData list folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.27-1: MCData list folder request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder identifier | O | The identifier of the folder to be listed | + +##### 7.13.3.1.28 MCData list folder response + +Table 7.13.3.1.28-1 describes the information flow for the MCData list folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.28-1: MCData list folder response** + +| Information element | Status | Description | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result (see NOTE) | M | The result of the list operation | +| NOTE: | If no folder identifier information element is provided in the request, the MCData message store returns folders from the root of the user account. If folder identifier information element is provided in the request, the MCData message store returns the child folders from that folder identifier provided. | | + +##### 7.13.3.1.29 MCData upload objects request + +Table 7.13.3.1.29-1 describes the information flow for the MCData upload objects request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.29-1: MCData upload objects request** + +| Information element | Status | Description | +|----------------------------|--------|--------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Targeted folder identifier | M | The folder where the uploaded objects will be stored | +| Uploaded objects | M | The objects in the client that need to be uploaded to the MCData message store | + +##### 7.13.3.1.30 MCData upload objects response + +Table 7.13.3.1.30-1 describes the information flow for the MCData upload objects response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.30-1: MCData upload objects response** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object upload result | M | Indicates if the objects upload is successful or not | + +##### 7.13.3.1.31 MCData synchronization notification + +Table 7.13.3.1.31-1 describes the information flow for the MCData synchronization notification sent from the MCData message store to the message store client. + +**Table 7.13.3.1.31-1: MCData synchronization notification** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user that the notification is for | + +##### 7.13.3.1.32 Create notification channel request + +Table 7.13.3.1.32-1 describes the information flow for the create notification channel request sent from the message notification client to the MCData notification server. + +**Table 7.13.3.1.32-1: Create notification channel request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | O | How long the notification channel is intended to be used (see NOTE) | +| Channel Type | M | Indicates if PULL (e.g. long-polling method) or PUSH method will be used to deliver notification messages | +| NOTE: If this element not present, a default validity duration shall be provided by the server in response | | | + +##### 7.13.3.1.33 Create notification channel response + +Table 7.13.3.1.33-1 describes the information flow for the create notification channel response sent from the MCData notification server to the message notification client. + +**Table 7.13.3.1.33-1: Create notification channel response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | M | How long the notification channel will last (i.e. channel lifetime) as granted by the MCData notification server | +| Notification URL | O | The URL to receive the notification message if a Pull method is requested . For some PUSH method implementation (such as WebSockets) this URL is used to start the PUSH notification service from the MCData notification server | +| Callback URL | M | The URL used by the Message notification client to subscribe to MCData message store notifications | + +##### 7.13.3.1.34 Open notification channel + +Table 7.13.3.1.34-1 describes the information flow for the open notification channel sent from the message notification client to the MCData notification server. + +**Table 7.13.3.1.34-1: Open notification channel request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Notification URL | M | The URL to receive the notification message | + +##### 7.13.3.1.35 Subscribe for notification request + +Table 7.13.3.1.35-1 describes the information flow for the subscribe for notification request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.35-1: Subscribe for notification request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Callback URL | M | The URL where to send the notification message | +| Validity duration | M | How long the subscription to notification will last (i.e. subscription lifetime); this value shall be the returned value in the create notification channel response | + +##### 7.13.3.1.36 Subscribe for notification response + +Table 7.13.3.1.36-1 describes the information flow for the subscribe for notification response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.36-1: Subscribe for notification response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | M | How long the subscription of notification will last (i.e. subscription lifetime) as granted by the server | +| Result | M | Indicates if the subscription is success or failure | + +##### 7.13.3.1.37 MCData search folder request + +Table 7.13.3.1.37-1 describes the information flow for the MCData search folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.37-1: MCData search folder request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Search criteria | M | Any part of the folder information (such as metadata) can be used as the search criteria. Linking multiple parts of the folder information as the search criteria is possible | + +##### 7.13.3.1.38 MCData search folder response + +Table 7.13.3.1.38-1 describes the information flow for the MCData search folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.38-1: MCData search folder response** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder identifier(s) | M | The folder(s) that meets the search criteria. This information element shall be returned as empty if there is no folder matching the search criteria | + +##### 7.13.3.1.39 MCData retrieve folder content request + +Table 7.13.3.1.39-1 describes the information flow for the MCData retrieve folder content request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.39-1: MCData retrieve folder content request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder identifier | M | The identifier of the folder its content is requested to be returned | + +##### 7.13.3.1.40 MCData retrieve folder content response + +Table 7.13.3.1.40-1 describes the information flow for the MCData retrieve folder content response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.40-1: MCData retrieve folder content response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder content | M | The content of the requested folder; such as objects and subfolders. This information element shall be returned as empty if the requested folder is not found. | + +##### 7.13.3.1.41 MCData retrieve file to store locally request + +Table 7.13.3.1.41-1 describes the information flow for the MCData retrieve file to store locally request sent from the message store client to the MCData message store and from the MCData server to the MCData message store. + +**Table 7.13.3.1.41-1: MCData retrieve file to store locally request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the FD communication object stored in the MCData message store | + +##### 7.13.3.1.42 MCData retrieve file to store locally response + +Table 7.13.3.1.42-1 describes the information flow for the MCData retrieve file to store locally response sent from the MCData message store to the message store client and the MCData server. + +**Table 7.13.3.1.42-1: MCData retrieve file to store locally response** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | Indicates success or failure of MCData update FD object with file content request | +| Content reference | O | URL reference to the file content stored in the MCData user's storage area | +| NOTE: Content reference shall be present if the content stored into the MCData user's storage area successfully. | | | + +##### 7.13.3.1.43 Update notification channel request + +Table 7.13.3.1.43 describes the information flow for the update notification channel request sent from the message notification client to the MCData notification server. + +**Table 7.13.3.1.43: Update notification channel request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | M | How long the notification channel will last (i.e. channel lifetime) as requested by the Message notification client. | + +##### 7.13.3.1.44 Update notification channel response + +Table 7.13.3.1.44 describes the information flow for the update notification channel response sent from the MCData notification server to the message notification client. + +**Table 7.13.3.1.44: Update notification channel response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | M | How long the notification channel will last (i.e. channel lifetime) as granted by the MCData notification server | +| Result | M | Indicates if the update is success or failure | + +##### 7.13.3.1.45 Update notification subscription request + +Table 7.13.3.1.45 describes the information flow for the update notification subscription request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.45: Update notification subscription request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | M | How long the notification channel will last (i.e. notification subscription lifetime). This value should be the returned value in the update notification channel response | + +##### 7.13.3.1.46 Update notification subscription response + +Table 7.13.3.1.46 describes the information flow for the update notification subscription response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.46: Update notification subscription response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Validity duration | M | How long the notification channel will last (i.e. notification subscription lifetime) as granted by the MCData message store | +| Result | M | Indicates if the update is success or failure | + +##### 7.13.3.1.47 Delete notification channel request + +Table 7.13.3.1.47 describes the information flow for the delete notification channel request sent from the message notification client to the MCData notification server. + +**Table 7.13.3.1.47: Delete notification channel request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | + +##### 7.13.3.1.48 Delete notification channel response + +Table 7.13.3.1.48 describes the information flow for the delete notification channel response sent from the MCData notification server to the message notification client. + +**Table 7.13.3.1.48: Delete notification channel response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Result | M | Indicates if deletion of notification channel is success or failure | + +##### 7.13.3.1.49 Delete notification subscription request + +Table 7.13.3.1.49 describes the information flow for the delete notification subscription request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.49: Delete notification subscription request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | + +##### 7.13.3.1.50 Delete notification subscription response + +Table 7.13.3.1.50 describes the information flow for the delete notification subscription response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.50: Delete notification subscription response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData client initiating the request | +| Result | M | Indicates if deletion of notification subscription is success or failure | + +##### 7.13.3.1.51 Notification message + +Table 7.13.3.1.51-1 describes the information flow for the notification message sent from the MCData message store to the MCData notification server and from the MCData notification server to the MCData notification client. + +**Table 7.13.3.1.51-1: Notification message** + +| Information element | Status | Description | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Event-data | M | The specific information carried in the notification message to inform the MCData client of changes to the MCData message store. (see NOTE) | +| NOTE: | MCData client uses the event information for actions such as updating its local message store or uses the event as a trigger for inquiring the Message store for desired changes. | | + +#### 7.13.3.2 Retrieve a stored object + +##### 7.13.3.2.1 General + +A stored object can be retrieved from the MCData message store with the known object identifier that is generated by the MCData message store when the object was deposited. + +##### 7.13.3.2.2 Procedure + +The procedure in figure 7.13.3.2.2-1 describes the case when a message store client retrieves a stored object from the MCData message store using the known object identifier. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The message store client knows the object identifier of the stored object. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store to retrieve a stored object.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: + Client->>Store: 1. MCData retrieve a stored object request + Note right of Store: + Store-->>Client: 2. MCData retrieve a stored object response + Note left of Client: +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow points from the client to the store, labeled '1. MCData retrieve a stored object request'. 2. A dashed arrow points from the store back to the client, labeled '2. MCData retrieve a stored object response'. + +Sequence diagram showing the interaction between a Message store client and an MCData message store to retrieve a stored object. + +**Figure 7.13.3.2.2-1: Retrieve a stored object** + +1. The message store client would like to retrieve a stored object from the MCData message store and initiates a MCData retrieve a stored object request toward the MCData message store. The unique object identifier of the stored object is included in the request. +2. The MCData message store returns the stored object that is identified by the object identifier in the MCData retrieve a stored object response. + +#### 7.13.3.3 Search stored objects + +##### 7.13.3.3.1 General + +The message store client can search stored objects in the MCData message store with certain criteria. This procedure allows the message store client to look for stored object(s) without knowing the object identifier(s) of the object. This procedure also allows the message store client to retrieve stored objects that are related to each other; such as all messages and files exchanged in a conversation. + +##### 7.13.3.3.2 Procedure + +The procedure in figure 7.13.3.3.2-1 describes the case when a message store client searches and retrieves relevant stored objects from the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store for searching stored objects.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: + Client->>Store: 1. MCData search stored objects request + Note right of Store: + Store-->>Client: 2. MCData search stored objects response + Note left of Client: +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow points from the client to the store, labeled '1. MCData search stored objects request'. 2. A return arrow points from the store back to the client, labeled '2. MCData search stored objects response'. + +Sequence diagram showing the interaction between a Message store client and an MCData message store for searching stored objects. + +**Figure 7.13.3.3.2-1: Search stored objects** + +1. The message store client would like to retrieve stored objects that meet certain criteria (such as with the same Conversation identifier) and initiates a MCData search objects request toward the MCData message store. The search criteria are included in the request. +2. The MCData message store looks up all stored objects that meet the search criteria and returns them in the MCData search objects response. + +#### 7.13.3.4 Update a stored object + +##### 7.13.3.4.1 General + +The message store client can update the metadata of a stored object (such as mark a stored object as "flagged"). + +##### 7.13.3.4.2 Procedure + +The procedure in figure 7.13.3.4.2-1 describes the case when a message store client updates metadata of a stored object in the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The message store client knows the object identifier of the stored object. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store to update a stored object.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: + Client->>Store: 1. MCData update a stored object request + Note right of Store: + Store-->>Client: 2. MCData update a stored object response +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow points from the client to the store, labeled '1. MCData update a stored object request'. 2. A dashed arrow points from the store back to the client, labeled '2. MCData update a stored object response'. + +Sequence diagram showing the interaction between a Message store client and an MCData message store to update a stored object. + +**Figure 7.13.3.4.2-1: Update a stored object** + +1. The message store client would like to update the metadata of a stored object (such as "flagged") and initiates a MCData update a stored object request toward the MCData message store. The stored object's object identifier and the updated meta data are included in the request. +2. The MCData message store locates the stored object with the object identifier and updates its metadata as carried in the MCData update a stored object request and communicates the result in the MCData update a stored object response. + +#### 7.13.3.5 Delete a stored object + +##### 7.13.3.5.1 General + +The message store client of an authorized user can delete a stored object in the MCData message store. + +##### 7.13.3.5.2 Procedure + +The procedure in figure 7.13.3.5.2-1 describes the case when a stored object in the MCData message store is deleted by the message store client of an authorized MCData user. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The message store client knows the object identifier of the stored object. +3. The MCData user is authorized to delete the stored object. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store to delete a stored object.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: + Client->>Store: 1. MCData delete a stored object request + Note right of Store: + Store-->>Client: 2. MCData delete a stored object response + Note left of Client: +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow points from the client to the store, labeled '1. MCData delete a stored object request'. 2. A dashed arrow points from the store back to the client, labeled '2. MCData delete a stored object response'. + +Sequence diagram showing the interaction between a Message store client and an MCData message store to delete a stored object. + +**Figure 7.13.3.5.2-1: Delete a stored object** + +1. The message store client would like to delete a stored object in the MCData message store and initiates a MCData delete a stored object request toward the MCData message store. The stored object's object identifier is included in the request. +2. The MCData message store locates the stored object with the object identifier and permanently removes it from the MCData message store. It then communicates the result in the MCData delete a stored object response. + +#### 7.13.3.6 Synchronization + +##### 7.13.3.6.1 General + +The message store client can synchronize its local message store with the MCData message store. Different level of synchronization shall be supported with a filter in the request. + +##### 7.13.3.6.2 Procedure + +The procedure in figure 7.13.3.6.2-1 describes the case when a message store client synchronizes its local message store with the MCData message store for a MCData user. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram showing synchronization between a Message store client and an MCData message store.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Server as MCData message store + Note left of Client: + Client->>Server: 1. MCData synchronization request + Note right of Server: + Server-->>Client: 2. MCData synchronization response +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow labeled '1. MCData synchronization request' points from the client to the server. 2. A return arrow labeled '2. MCData synchronization response' points from the server back to the client. + +Sequence diagram showing synchronization between a Message store client and an MCData message store. + +**Figure 7.13.3.6.2-1: Synchronization** + +1. The message store client would like to synchronize its local message store with the MCData message store. It initiates the MCData synchronization request toward the MCData message store. The synchronization type and optional filter criteria are included in the request to indicate the type of synchronization (such as full synchronization, partial synchronization etc.) is requested. +2. The MCData message store returns all the stored objects, based on the synchronization filter criteria, to the message store client in the MCData synchronization response. + +#### 7.13.3.7 Create a user account + +##### 7.13.3.7.1 General + +When the MCData server is ready to deposit an object into the MCData user's storage area in the MCData message store the MCData user's storage area (i.e. user account) needs to be created already. If the user account is not created, the MCData server shall create the user account (i.e. allocate the MCData user's storage area in the MCData message store) first and then deposit the subsequent MCData communications. + +NOTE: Another possible way to create a user account on the MCData message store is through service provisioning which is out of the scope of the present document. + +##### 7.13.3.7.2 Procedure + +The procedure in figure 7.13.3.7.2-1 describes how the MCData server creates a user account (allocate MCData user storage area) in the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization has been performed between the MCData server and the MCData message store. +2. No storage area in the MCData message store has been allocated for the MCData user; i.e. no user account has been created. +3. The MCData server is authorized to create user accounts on the MCData message store. + +![Sequence diagram for 'Create a user account' showing interaction between MCData server and MCData message store.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` +sequenceDiagram + participant MCData server + participant MCData message store + Note left of MCData server: + MCData server->>MCData message store: 1. MCData create a user account request + Note right of MCData message store: + MCData message store-->>MCData server: 2. MCData create a user account response +``` + +The diagram is a sequence diagram with two lifelines: 'MCData server' on the left and 'MCData message store' on the right. A solid arrow labeled '1. MCData create a user account request' points from the MCData server to the MCData message store. A return arrow labeled '2. MCData create a user account response' points from the MCData message store back to the MCData server. + +Sequence diagram for 'Create a user account' showing interaction between MCData server and MCData message store. + +**Figure 7.13.3.7.2-1: Create a user account** + +1. The MCData server would like to create a MCData user account in the MCData message store to store the MCData communication for that MCData user and initiates a MCData create a user account request toward the MCData message store. The MCData ID of the MCData user is included in the request. +2. The MCData message store creates a user account (i.e. allocate dedicated and secured storage area) for the MCData user as specified in the request and communicates the result back to the MCData server in the MCData create a user account response. + +#### 7.13.3.8 Deposit an object + +##### 7.13.3.8.1 General + +MCData server needs to store the communication information (i.e. an object) for a MCData user during an active MCData communication. If there is a file URL in the object for file distribution in the communication, the MCData server may instruct the MCData message store to retrieve a copy of the file to store locally in the MCData user's account. + +##### 7.13.3.8.2 Procedure + +The procedure in figure 7.13.3.8.2-1 describes how the MCData server deposit an object into the MCData message store during an active MCData communication. + +Pre-conditions: + +1. A successful authentication and authorization has been performed between the MCData server and the MCData message store. +2. The MCData user has been allocated a secured storage area in the MCData message store. +3. The configuration to store the MCData communication in MCData message store is enabled for the MCData user. +4. MCData user has requested to store his MCData communication and also store the distributed file content into his MCData message store account if the MCData communication is for file distribution through URL. + +![Sequence diagram for depositing an object. Lifelines: MCData server, MCData message store, MCData Content server. The sequence is: 1. MCData server sends a deposit request to the message store. 2. The message store sends a 'Fetch file' request to the content server (indicated by a dashed box). 3. The message store stores the file content and updates the object with a payload URL (indicated by a dashed box). 4. The message store sends a response back to the MCData server.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MCData server + participant MCData message store + participant MCData Content server + Note right of MCData message store: 2. Fetch file + Note right of MCData message store: 3. Store the file content into MCData user's storage area and update the object with the payload URL referencing the stored file + MCData server->>MCData message store: 1. MCData deposit an object request + MCData message store-->>MCData Content server: 2. Fetch file + MCData message store-->>MCData message store: 3. Store the file content into MCData user's storage area and update the object with the payload URL referencing the stored file + MCData message store-->>MCData server: 4. MCData deposit an object response + +``` + +Sequence diagram for depositing an object. Lifelines: MCData server, MCData message store, MCData Content server. The sequence is: 1. MCData server sends a deposit request to the message store. 2. The message store sends a 'Fetch file' request to the content server (indicated by a dashed box). 3. The message store stores the file content and updates the object with a payload URL (indicated by a dashed box). 4. The message store sends a response back to the MCData server. + +**Figure 7.13.3.8.2-1: Deposit an object** + +1. The MCData server would like to deposit a MCData communication information (i.e. object) to the MCData user's storage area in the MCData message store and initiates a MCData deposit an object request toward the MCData message store. The object is constructed by the MCData server and is included in the request. If the object is a message that carries a URL for file distribution, the MCData server may instruct the MCData message store to retrieve a copy of the file and store locally in the MCData user's account by setting the retrieve file indication information element to true. +2. The MCData message store deposits the object into the MCData user's storage area. If the retrieve file indication is set in the MCData deposit an object request the MCData message store retrieves the file URL from the stored object and fetches the file content from the MCData content server. +3. The MCData message store stores the file content into the MCData user's storage area and update the object with the URL referencing the file content stored in the MCData user's storage area. +4. The MCData message store communicates the result back to the MCData server in the MCData deposit an object response. The object identifier of the stored object is returned. + +#### 7.13.3.9 Copy a stored object + +##### 7.13.3.9.1 General + +A stored object in the MCData message store can be copied to another location (i.e. folder) in the same MCData user account where there is no such object stored. After the successful object copy operation, the object will exist in both the original and destination locations. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.9.2 Procedure + +The procedure in figure 7.13.3.9.2-1 describes the case when a stored object is copied to a different location in the same MCData user account. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. +3. The message store client knows the object identifier of the stored object and the destination folder identifier. + +![Sequence diagram for 'Copy a stored object'](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` +sequenceDiagram + participant MSC as Message store client + participant MMS as MCData message store + Note right of MMS: 2. copy the object to target location + MSC->>MMS: 1. MCData copy a stored object request + MMS-->>MSC: 3. MCData copy a stored object response +``` + +The diagram is a sequence diagram illustrating the interaction between a 'Message store client' and an 'MCData message store'. The client sends a '1. MCData copy a stored object request' to the store. The store then performs an internal action, '2. copy the object to target location', indicated by a self-call message. Finally, the store sends a '3. MCData copy a stored object response' back to the client. + +Sequence diagram for 'Copy a stored object' + +**Figure 7.13.3.9.2-1: Copy a stored object** + +1. The message store client would like to copy a stored object in the MCData message store to a destination folder and initiates a MCData copy a stored object request toward the MCData message store. The unique identifier of the stored object and the destination folder are included in the request. +2. The MCData message store copies the object to the target location. +3. The MCData message store returns the result of the request in the MCData copy a stored object response. + +#### 7.13.3.10 Move a stored object + +##### 7.13.3.10.1 General + +A stored object in the MCData message store can be moved to a different location (i.e. folder) in the same MCData user account. After the successful object move operation the object will only exist in the new location. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.10.2 Procedure + +The procedure in figure 7.13.3.10.2-1 describes the case when a stored object is moved to a different location in the same MCData user account. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. +3. The message store client knows the object identifier of the stored object and the destination folder identifier. + +![Sequence diagram for 'Move a stored object' operation between a Message store client and MCData message store.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. move the object to target location + Client->>Store: 1. MCData move a stored object request + Store-->>Client: 3. MCData move a stored object response +``` + +The diagram is a sequence diagram illustrating the interaction for moving a stored object. It features two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The sequence of messages is as follows: 1. A solid arrow labeled '1. MCData move a stored object request' points from the client to the store. 2. A self-message box labeled '2. move the object to target location' is shown on the store's lifeline. 3. A return arrow labeled '3. MCData move a stored object response' points from the store back to the client. + +Sequence diagram for 'Move a stored object' operation between a Message store client and MCData message store. + +**Figure 7.13.3.10.2-1: Move a stored object** + +1. The message store client would like to move a stored object in the MCData message store to a destination folder and initiates a MCData move a stored object request toward the MCData message store. The unique object identifier of the stored object and the destination folder are included in the request. +2. The MCData message store moves the object to the target location. +3. The MCData message store returns the result of the request in the MCData move a stored object response. + +#### 7.13.3.11 Folder create operation + +##### 7.13.3.11.1 General + +A user can create a new folder in his user account in the MCData message store. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.11.2 Procedure + +The procedure in figure 7.13.3.11.2-1 describes the case when a MCData user creates a new folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for creating a new user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData create folder request' to the store. The store performs an internal action '2. Create new folder' and then sends a '3. MCData create folder response' back to the client.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. Create new folder + Client->>Store: 1. MCData create folder request + Store-->>Client: 3. MCData create folder response +``` + +Sequence diagram for creating a new user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData create folder request' to the store. The store performs an internal action '2. Create new folder' and then sends a '3. MCData create folder response' back to the client. + +**Figure 7.13.3.11.2-1: Create a new user folder** + +1. The MCData user would like to create a new folder in his user account in the MCData message store, the message store client initiates a MCData create folder request toward the MCData message store. The parent folder identifier and the folder name are included in the request to indicate where the new folder will be created. +2. The MCData message store creates the user folder in the location specified in the request. If the folder name is provided in the request, the MCData message store creates the folder with the provided folder name. If the provided folder name has a conflict or no folder name is provided in the request, the MCData message store assigns a name for the new user folder. +3. The MCData message store returns the result in the MCData create folder response. The identifier of the new folder is returned in the response. + +#### 7.13.3.12 Folder delete operation + +##### 7.13.3.12.1 General + +A user can delete an existing folder in his user account in the MCData message store. All the child folders and objects stored in that folder will be deleted. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.12.2 Procedure + +The procedure in figure 7.13.3.12.2-1 describes the case when a MCData user deletes an existing folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for deleting a user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData delete folder request' to the store. The store performs '2. Delete the identified folder and all its objects' and then sends a '3. MCData delete folder response' back to the client.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. Delete the identified folder and all its objects + Client->>Store: 1. MCData delete folder request + Store-->>Client: 3. MCData delete folder response +``` + +Sequence diagram for deleting a user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData delete folder request' to the store. The store performs '2. Delete the identified folder and all its objects' and then sends a '3. MCData delete folder response' back to the client. + +**Figure 7.13.3.12.2-1: Delete a user folder** + +1. The MCData user would like to delete an existing folder in his user account in the MCData message store, the message store client initiates a MCData delete folder request toward the MCData message store. The folder identifier of the folder to be deleted is included in the request. +2. The MCData message store identifies the target folder and deletes it from the user account. All the child folders and objects stored in this folder are also deleted. +3. The MCData message store returns the result in the MCData delete folder response. + +#### 7.13.3.13 Folder copy operation + +##### 7.13.3.13.1 General + +A user can copy an existing folder in his user account to a different location. All the child folders and objects stored in that folder will be copied to the new folder. The name of the new folder will be the same as the folder it copies from or the name provided in the request. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.13.2 Procedure + +The procedure in figure 7.13.3.13.2-1 describes the case when a MCData user copies an existing folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for copying a user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData copy folder request' to the store. The store performs '2. Copy the source folder to the destination' and then sends a '3. MCData copy folder response' back to the client.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. Copy the source folder to the destination + Client->>Store: 1. MCData copy folder request + Store-->>Client: 3. MCData copy folder response +``` + +Sequence diagram for copying a user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData copy folder request' to the store. The store performs '2. Copy the source folder to the destination' and then sends a '3. MCData copy folder response' back to the client. + +**Figure 7.13.3.13.2-1: Copy a user folder** + +1. The MCData user would like to copy an existing folder in his user account in the MCData message store, the message store client initiates a MCData copy folder request toward the MCData message store. The folder identifiers of the source and destination folders and the new folder name are included in the request. +2. The MCData message store copy the source folder to the destination with the new folder name. If no new folder name is provided in the request, the source folder name will be used. All the child folders and objects stored in this folder are also copied to the new folder. +3. The MCData message store returns the result in the MCData copy folder response. The identifier of the new folder is returned in the response. + +#### 7.13.3.14 Folder move operation + +##### 7.13.3.14.1 General + +A user can move an existing folder in his user account to a different location. All the child folders and objects stored in that folder will be moved to the new folder. The name of the new folder will be the same as the folder it moves from or the name provided in the request. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.14.2 Procedure + +The procedure in figure 7.13.3.14.2-1 describes the case when a MCData user moves an existing folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for 'Move a user folder' operation. Lifelines: Message store client and MCData message store. The client sends a '1. MCData move folder request' to the store. The store performs '2. Move the identified folder to the destination' and then sends a '3. MCData move folder response' back to the client.](26d664119ad25250780f554633444e54_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. Move the identified folder to the destination + Client->>Store: 1. MCData move folder request + Store-->>Client: 3. MCData move folder response +``` + +Sequence diagram for 'Move a user folder' operation. Lifelines: Message store client and MCData message store. The client sends a '1. MCData move folder request' to the store. The store performs '2. Move the identified folder to the destination' and then sends a '3. MCData move folder response' back to the client. + +**Figure 7.13.3.14.2-1: Move a user folder** + +1. The MCData user would like to move an existing folder in his user account in the MCData message store to a new location, the message store client initiates a MCData move folder request toward the MCData message store. The folder identifiers of the source and destination folders and the new folder name are included in the request. +2. The MCData message store move the source folder to the destination with the new folder name. If no new folder name is provided in the request, the source folder name will be used. All the child folders and objects stored in this folder are also moved to the new folder. +3. The MCData message store returns the result in the MCData move folder response. The identifier of the new folder is returned in the response. + +#### 7.13.3.15 Folder list operation + +##### 7.13.3.15.1 General + +A user can view the folder structure in his user account in the MCData message store. The target folder hierarchy structure will be presented to the user; i.e. the folder and all its child folders. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.15.2 Procedure + +The procedure in figure 7.13.3.15.2-1 describes the case when a MCData user lists an existing folder's hierarchy structure in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for Folder list operation](868ef3e0abb37916a7af1e923995f329_img.jpg) + +``` +sequenceDiagram + participant MSC as Message store client + participant MMS as MCData message store + Note right of MMS: 2. Generate folder view + MSC->>MMS: 1. MCData list folder request + MMS-->>MSC: 3. MCData list folder response +``` + +The diagram is a sequence diagram illustrating the 'Folder list operation'. It features two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of three steps: 1. The client sends a 'MCData list folder request' to the message store. 2. The message store performs an internal action labeled 'Generate folder view'. 3. The message store returns a 'MCData list folder response' to the client. + +Sequence diagram for Folder list operation + +**Figure 7.13.3.15.2-1: Folder list operation** + +1. The MCData user would like to view the folder structure of a targeted folder in his user account in the MCData message store, the message store client initiates a MCData list folder request toward the MCData message store. The folder identifier of the target folder is included in the request. +2. The MCData message store retrieves the target folder and all its child folders. If no target folder name is provided in the request, the MCData message store will use the root folder as the target folder. +3. The MCData message store returns the result in the MCData list folder response. + +#### 7.13.3.16 Upload objects + +##### 7.13.3.16.1 General + +A MCData user, with an account in the MCData message store, involved in an off-network communication will store the communication as objects in a specific folder in the local message store on his UE. These objects can be uploaded to his user account in the MCData message store once he is connected to the network with MC data service again. + +##### 7.13.3.16.2 Procedure + +The procedure in figure 7.13.3.16.2-1 describes the case when a message store client uploads new objects in its local message store to the MCData message store for a MCData user. + +Pre-conditions: + +1. The MCData user has an account with the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for Upload objects](164d1b48231be457522b31965610ea3b_img.jpg) + +``` +sequenceDiagram + participant MSC as Message store client + participant MMS as MCData message store + Note right of MMS: 2. Process the uploaded objects + MSC->>MMS: 1. MCData upload objects request + MMS-->>MSC: 3. MCData upload objects response +``` + +The diagram is a sequence diagram showing the interaction between a 'Message store client' and an 'MCData message store'. The client sends a '1. MCData upload objects request' to the store. The store then performs an internal action '2. Process the uploaded objects' and returns a '3. MCData upload objects response' to the client. + +Sequence diagram for Upload objects + +**Figure 7.13.3.16.2-1: Upload objects** + +1. The message store client would like to upload new objects in its local message store to the MCData message store. It initiates the MCData upload objects request toward the MCData message store. The uploaded objects and the target folder identifier where the objects will be stored are included in the request. +2. The MCData message store stores the uploaded objects to the target folder. If the target folder doesn't exist, the MCData message store will create it. +3. The MCData message store returns the result in the MCData upload objects response. + +#### 7.13.3.17 Notify client to synchronize + +##### 7.13.3.17.1 General + +MCData message store will send a notification to the MCData user when there are new objects in the MCData message store that need to be synchronized with his local message store. + +##### 7.13.3.17.2 Procedure using in-band connection + +The procedure in figure 7.13.3.17.2-1 describes how the MCData message store notifies the message store client that there are new objects in the MCData message store need to be synchronized. + +Pre-conditions: + +1. The MCData user has an account with the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. +3. The Message store client is in an ongoing session with the MCData message store. + +![Sequence diagram showing notification from MCData message store to Message store client.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` +sequenceDiagram + participant MCData message store + participant Message store client + Note left of MCData message store: 1. New objects received since last synchronization + MCData message store->>Message store client: 2. MCData synchronization notification +``` + +The diagram is a sequence diagram with two lifelines: 'MCData message store' on the left and 'Message store client' on the right. A vertical line descends from each lifeline. A rectangular box labeled '1. New objects received since last synchronization' is positioned on the left lifeline. A horizontal arrow labeled '2. MCData synchronization notification' originates from the left lifeline and points to the right lifeline. + +Sequence diagram showing notification from MCData message store to Message store client. + +**Figure 7.13.3.17.2-1: Notify client to synchronize using in-band connection** + +1. The MCData message store receives new objects for the MCData user and decides to send a notification to inform the MCData user. + +NOTE: How MCData message store determines if a notification needs to be sent to the message store client is out of scope of the present specification. + +2. The MCData message store sends the MCData synchronization notification to the message store client. + +##### 7.13.3.17.3 Procedure using MCData notification server + +The procedure in figure 7.13.3.17.3-1 describes how the MCData message store notifies the message notification client, using a MCData notification server, that there are new objects in the MCData message store needing to be synchronized. This procedure uses a web base notification mechanism in wide deployment today. The Message notification client requests the notification service from the MCData notification server and the MCData notification server returns with two URLs; one used by the service client to inform the service server where to send notification messages and the other one to use by the service client to PULL notification messages from the MCData notification server. + +Pre-conditions: + +1. The MCData user has an account with the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. +3. The Message store client doesn't have an ongoing session with the MCData message store. +4. The trust relationship between the MCData notification server and the MCData message store has been established. +5. The MCData notification server has a trust relationship and connection with the PUSH Enabler server. + +![Sequence diagram showing the interaction between MCData Client, MCData Notification server, and MCData message store for notification synchronization.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` + +sequenceDiagram + participant MCData Client + subgraph MCData Client + MNC[Message notification client] + MSC[Message store client] + end + participant MCData Notification server + participant MCData message store + + Note right of MCData Notification server: 2. Authentication and authorization + Note right of MCData message store: 7. Notification generated + + MNC->>MCData Notification server: 1. Create notification channel request + MCData Notification server-->>MNC: 3. Create notification channel response + MSC-->>MCData Notification server: 4. Open notification channel + MSC->>MCData message store: 5. Subscribe for notification request + MCData message store-->>MSC: 6. Subscribe for notification response + Note right of MCData message store: 7. Notification generated + MCData message store->>MCData Notification server: 8. Notification message + MCData Notification server-->>MNC: 9. Notification message + +``` + +The sequence diagram illustrates the interaction for synchronizing notifications. It begins with the Message notification client (part of the MCData Client) sending a 'Create notification channel request' to the MCData Notification server. The server responds with 'Authentication and authorization' and then a 'Create notification channel response'. Next, the Message store client (part of the MCData Client) sends an 'Open notification channel' request to the server. Simultaneously, the Message store client sends a 'Subscribe for notification request' to the MCData message store, which responds with a 'Subscribe for notification response'. Later, a 'Notification generated' event occurs in the MCData message store, leading to a 'Notification message' being sent to the MCData Notification server, which then forwards it to the Message notification client. + +Sequence diagram showing the interaction between MCData Client, MCData Notification server, and MCData message store for notification synchronization. + +**Figure 7.13.3.17.3-1: Notify client to synchronize through MCData notification server** + +1. The Message notification client wants to create notification channels (i.e. endpoint URLs) to be used by the MCData message store to send notification messages and sends a Create notification channel request to the MCData notification server. The desired validity duration for the channels to be used and the notification channel type (PUSH or PULL) are included in the request. +2. The MCData notification server authenticates the Message notification client and authorizes its request. +3. The MCData notification server sends the Message notification client the Create notification channel response with the endpoint URLs that will be used by the MCData message store to send the notification messages and the Message notification client to receive the notification messages. The MCData notification server also includes what is the valid duration for these endpoint URLs to be used in the response. +4. If the notification type is PULL method, the message notification client sends the Open notification channel to the MCData notification server to start receiving the notification message. For certain PUSH method notification type (such as WebSockets) the message notification client requests the MCData notification server to start the PUSH notification service with its specific protocol that is outside the scope of this specification. +5. The message store client sends the Subscribe for notification request to the MCData message store asking to be notified if there are changes to its message store account. The callback URL returned from the MCData notification server in step 3 is included in the request for the MCData message store to use to send notification messages. +6. The MCData message store sends the Subscribe for notification response to the message store client to acknowledge the request. + +7. The MCData user's message store account has changed and the MCData message store generates a notification message. +8. Using the callback URL, the MCData message store sends the notification message to the MCData notification server. +9. If the delivery method is PULL, the MCData notification server sends the notification message to the message notification client over the opened notification channel. If the delivery method is PUSH, the MCData notification server sends the notification message to the PUSH Enabler server (not shown in the figure) to deliver to the message notification client. + +NOTE: The PUSH Enabler server is implementation specific and outside the scope of this specification. + +The procedure in figure 7.13.3.17.3-2 describes how the message notification client updates the validity duration of a notification channel and subscription to avoid its expiration, i.e. to extend its lifetime. + +Pre-conditions: + +1. A notification channel has already been requested and established between the message notification client and MCData notification server. +2. The message store client has a successful notification subscription with the MCData message store. +3. The validity duration of the notification channel is about to expire. + +![Sequence diagram titled 'Update a notification channel' showing interactions between MCData client (Message notification client, Message store client), MCData notification server, and MCData message store.](d980a3f9608055996a07f31788baf827_img.jpg) + +``` +sequenceDiagram + participant MCData_client as MCData client + subgraph MCData_client [MCData client] + direction TB + MNC[Message notification client] + MSC[Message store client] + end + participant MCData_notification_server as MCData notification server + participant MCData_message_store as MCData message store + + Note left of MNC: Validity duration about to expire + MNC->>MCData_notification_server: 1. Update notification channel request + MCData_notification_server-->>MNC: 2. Update notification channel response + Note right of MNC: New validity duration received + MSC->>MCData_message_store: 3. Update notification subscription request + MCData_message_store-->>MSC: 4. Update notification subscription response + Note right of MSC: Confirmation received +``` + +Sequence diagram titled 'Update a notification channel' showing interactions between MCData client (Message notification client, Message store client), MCData notification server, and MCData message store. + +**Figure 7.13.3.17.3-2: Update a notification channel** + +1. The message notification client sends the Update notification channel request, including the desired new validity duration, to the MCData notification server. +2. The MCData notification server grants the request and sends the Update notification channel response to the message notification client. The new validity duration is included in the response. +3. The message store client sends the Update notification subscription request to the MCData message store with the new validity duration received from the MCData notification server in step 2. +4. The MCData message store sends the Update notification subscription response to the message store client and confirms the new validity duration. + +The procedure in figure 7.13.3.17.3-3 describes how the message notification client delete a notification channel and subscription that is no longer needed. + +Pre-conditions: + +1. A notification channel has already been requested and established between the message notification client and MCData notification server. +2. The message store client has a successful notification subscription with the MCData message store. +3. The MCData user no longer wants to receive notifications from the MCData message store. + +![Sequence diagram for deleting a notification channel. Lifelines: MCData client (containing Message notification client and Message store client), MCData notification server, and MCData message store. The sequence is: 1. Message store client sends 'Delete notification subscription request' to MCData message store. 2. MCData message store sends 'Delete notification subscription response' to Message store client. 3. Message notification client sends 'Delete notification channel request' to MCData notification server. 4. MCData notification server sends 'Delete notification channel response' to Message notification client.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +``` +sequenceDiagram + participant MCData_client as MCData client + subgraph MCData_client [MCData client] + participant Message_notification_client as Message notification client + participant Message_store_client as Message store client + end + participant MCData_notification_server as MCData notification server + participant MCData_message_store as MCData message store + + Message_store_client->>MCData_message_store: 1. Delete notification subscription request + MCData_message_store-->>Message_store_client: 2. Delete notification subscription response + Message_notification_client->>MCData_notification_server: 3. Delete notification channel request + MCData_notification_server-->>Message_notification_client: 4. Delete notification channel response +``` + +Sequence diagram for deleting a notification channel. Lifelines: MCData client (containing Message notification client and Message store client), MCData notification server, and MCData message store. The sequence is: 1. Message store client sends 'Delete notification subscription request' to MCData message store. 2. MCData message store sends 'Delete notification subscription response' to Message store client. 3. Message notification client sends 'Delete notification channel request' to MCData notification server. 4. MCData notification server sends 'Delete notification channel response' to Message notification client. + +**Figure 7.13.3.17.3-3: Delete a notification channel** + +1. The message store client decides to stop receiving notifications from the MCData message store and sends the Delete notification subscription request to the MCData message store. +2. The MCData message store acknowledges the request and sends the Delete notification subscription response to the message store client. +3. The message notification client sends the Delete notification channel request to the MCData notification server. +4. The MCData notification server acknowledges the request and sends the Delete notification channel response to the message notification client. + +#### 7.13.3.18 Search folder + +##### 7.13.3.18.1 General + +The message store client can search stored folder(s) with certain criteria. This procedure allows the message store client to look for folder(s) that meet certain criteria such as when the folder is created. This procedure provides the message store client the ability to locate a specific folder(s) matching the search criteria to perform further operations. + +##### 7.13.3.18.2 Procedure + +The procedure in figure 7.13.3.18.2-1 describes the case when a message store client searches and retrieves relevant stored objects from the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for Search folder procedure](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: + Client->>Store: 1. MCData search folder request + Note right of Store: + Store-->>Client: 2. MCData search folder response + Note left of Client: +``` + +The diagram is a sequence diagram showing the interaction between a 'Message store client' and an 'MCData message store'. The client sends a '1. MCData search folder request' to the store, and the store responds with a '2. MCData search folder response'. + +Sequence diagram for Search folder procedure + +**Figure 7.13.3.18.2-1: Search folder** + +1. The message store client wants to retrieve message store folder(s) that meet certain criteria (such as when the folder(s) was created, certain keywords etc.) and initiates a MCData search folder request toward the MCData message store. The search criteria are included in the request. +2. The MCData message store identifies all folders that match the search criteria and returns them in the MCData search folder response. + +#### 7.13.3.19 Retrieve folder content + +##### 7.13.3.19.1 General + +An MCData user can retrieve the content of a folder in the user's message store account. This procedure allows the message store client to retrieve the specific folder's content from the MCData message store. + +##### 7.13.3.19.2 Procedure + +The procedure in figure 7.13.3.19.2-1 describes the case when a message store client retrieves the content of a specific folder in the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store for retrieving folder content.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant MCData as MCData message store + Note left of Client: + Client->>MCData: 1. MCData retrieve folder content request + Note right of MCData: + MCData-->>Client: 2. MCData retrieve folder content response + Note left of Client: +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow points from the client to the MCData message store, labeled '1. MCData retrieve folder content request'. 2. A dashed arrow points from the MCData message store back to the client, labeled '2. MCData retrieve folder content response'. + +Sequence diagram showing the interaction between a Message store client and an MCData message store for retrieving folder content. + +**Figure 7.13.3.19.2-1: retrieve folder content** + +1. The message store client wants to retrieve the content of a specific folder and initiates a MCData retrieve folder content request toward the MCData message store. The requested folder identifier is included in the request. +2. The MCData message store locates the requested folder and returns the content of the folder (e.g. objects and subfolders) in the MCData retrieve folder content response. + +#### 7.13.3.20 Store file contents distributed using HTTP + +##### 7.13.3.20.1 General + +An MCData user can store the received file content in his message store account. This procedure allows the message store client to request the MCData message store to retrieve the file from the media storage function of MCData content server and store into MCData message store account of the user. + +##### 7.13.3.20.2 Procedure for storing the file – receiver side + +The procedure in figure 7.13.3.20.3-1 describes the case when a message store client requests the MCData message store to retrieve the file from media storage function of MCData content server and store into MCData message store account of the user. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The configuration to store the MCData communication in MCData message store is enabled for the MCData user. +3. MCData user has requested to store his MCData communication. +4. The message store client knows the object identifier of the stored object. + +![Sequence diagram showing the interaction between Message Store Client, MCData message store, and MCData Content server for storing file contents. The steps are: 1. MCData retrieve file to store locally request from Client to Store; 2. Fetch file from Store to Content server; 3. Store the file content into MCData user's storage area and update the object with the payload URL referencing the stored file (internal to Store); 4. MCData retrieve file to store locally response from Store to Client.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant Client as Message Store Client + participant Store as MCData message store + participant ContentServer as MCData Content server + Note right of Store: 2.Fetch file + Note right of Store: 3.Store the file content into MCData user's storage area and update the object with the payload URL referencing the stored file + Client->>Store: 1.MCData retrieve file to store locally request + Store->>ContentServer: 2.Fetch file + Store->>Store: 3.Store the file content into MCData user's storage area and update the object with the payload URL referencing the stored file + Store->>Client: 4.MCData retrieve file to store locally response + +``` + +Sequence diagram showing the interaction between Message Store Client, MCData message store, and MCData Content server for storing file contents. The steps are: 1. MCData retrieve file to store locally request from Client to Store; 2. Fetch file from Store to Content server; 3. Store the file content into MCData user's storage area and update the object with the payload URL referencing the stored file (internal to Store); 4. MCData retrieve file to store locally response from Store to Client. + +**Figure 7.13.3.20.3-1: store file contents distributed using HTTP – receiver side** + +1. The Message store client initiates MCData retrieve file to store locally request towards the MCData message store. The object identifier corresponding to the stored MCData FD communication is included in the request. +2. The MCData message store retrieves the file URL from the stored object and fetches the file content from the MCData content server. +3. The MCData message store stores the file content into the MCData user's storage area and update the object with the URL referencing the file content stored in the MCData user's storage area. +4. The MCData message store provides the MCData retrieve file to store locally response to the message store client. This response includes the URL of the file being stored in the MCData user's storage area. + +### 7.13.4 Generic outgoing SDS procedure with MCData message store + +#### 7.13.4.1 General + +When a MCData user is supported with MCData message store all his outgoing communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication. + +#### 7.13.4.2 Procedure + +The procedure in figure 7.13.4.2-1 describes the generic SDS service where MCData message store is supported. + +Pre-conditions: + +1. MCData user has an account created with MCData message store. +2. The configuration to store the MCData communication in MCData message store is enabled for the MCData user. +3. MCData user has requested to store his MCData communication. + +![Sequence diagram showing the generic outgoing SDS procedure with MCData message store. The diagram involves three lifelines: MCData client, MCData server, and MCData message store. The sequence of messages is: 1. MCData client initiates a MCData SDS service request to MCData server; 2. MCData server deposits the object to MCData message store; 3. MCData server continues with the MCData SDS service request.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` +sequenceDiagram + participant MCData client + participant MCData server + participant MCData message store + Note left of MCData server: 1. Initiates a MCData SDS service request + Note right of MCData message store: 2. Deposit the object + Note left of MCData server: 3. Continue with the MCData SDS service request +``` + +Sequence diagram showing the generic outgoing SDS procedure with MCData message store. The diagram involves three lifelines: MCData client, MCData server, and MCData message store. The sequence of messages is: 1. MCData client initiates a MCData SDS service request to MCData server; 2. MCData server deposits the object to MCData message store; 3. MCData server continues with the MCData SDS service request. + +**Figure 7.13.4.2-1 Generic outgoing SDS procedure with MCData message store** + +1. MCData client initiates an MCData SDS service request; this service request can be a private or group communication. +2. MCData server stores the communication as an object to the MCData user account in the MCData message store. +3. MCData server checks and authorizes the service request and continue the service request toward the targeted recipient(s) as described in subclause 7.4.2. + +### 7.13.5 Generic incoming SDS procedure with MCData message store + +#### 7.13.5.1 General + +When a MCData user is supported with MCData message store all his incoming communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication. + +#### 7.13.5.2 Procedure + +The procedure in figure 7.13.5.2-1 describes the generic SDS service where MCData message store is supported. + +Pre-conditions: + +1. MCData user has an account created with MCData message store. +3. The configuration to store the MCData communication in MCData message store is enabled for the MCData user. +3. MCData user has requested to store his MCData communication. + +![Sequence diagram showing the generic incoming SDS procedure with MCData message store. The diagram involves three lifelines: MCData client, MCData server, and MCData message store. The sequence of messages is: 1. MCData server receives an incoming MCData SDS service request from the MCData message store. 2. MCData server deposits the object into the MCData message store. 3. MCData server delivers the MCData SDS service request to the MCData client.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant MCData server + participant MCData message store + Note right of MCData server: 1. Receives an incoming MCData SDS service request + Note right of MCData server: 2. Deposit the object + Note right of MCData client: 3. Deliver the MCData SDS service request + +``` + +Sequence diagram showing the generic incoming SDS procedure with MCData message store. The diagram involves three lifelines: MCData client, MCData server, and MCData message store. The sequence of messages is: 1. MCData server receives an incoming MCData SDS service request from the MCData message store. 2. MCData server deposits the object into the MCData message store. 3. MCData server delivers the MCData SDS service request to the MCData client. + +**Figure 7.13.5.2-1 Generic incoming SDS procedure with MCData message store** + +1. The MCData server receives an incoming MCData SDS service request for the MCData user. This service request can be a response to an earlier service request sent by the MCData user or a new service request coming from any sender. +2. MCData server stores the communication as an object to the MCData user account in the MCData message store. +3. MCData server delivers the service request to MCData user as described in subclause 7.4.2. + +### 7.13.6 Interconnection and migration with MCData message store + +#### 7.13.6.1 Interconnection + +There is no interconnection of MCData message stores, as there are no defined reference points providing connection between message stores in different MCData systems. + +#### 7.13.6.2 Migration + +A migrated MCData user may be provided with access to a local message store by the partner MCData system of the migrated MCData user. The MCData user is identified by the MCData ID used in the partner MCData system by that migrated MCData user in order to access the message store. There is no connection between this message store in the partner MCData system of the migrated MCData user and any message store that the MCData user has access to in the primary MCData system of that MCData user, and therefore access to a message store in the partner MCData system does not provide a means of accessing stored content in the primary MCData system of the migrated MCData user. + +A migrated MCData user may be provided with a means of access to the message store in the primary MCData system of that MCData user, e.g. by providing the MCData user with a suitable APN and appropriate IP routing, or by use of the MCData IP connectivity service. Such access is outside the scope of the present document. + +## 7.14 IP connectivity + +### 7.14.1 General + +IP data shall be exchanged between two or more data hosts. The MCData client as the link between data host and MC system enables the exchange of IP Data. For addressing the corresponding MCData users either MCData ID or the functional alias can be used independently of each other. The MCData server provides the mechanisms to establish the association between MCData ID and corresponding functional alias. + +### 7.14.2 IP connectivity for on-network + +#### 7.14.2.1 Information flows for IP connectivity + +##### 7.14.2.1.1 MCDATA IPcon point-to-point request + +Table 7.14.2.1.1-1 describes the information flow of the MCDATA IPcon point-to-point request sent from the MCDATA client to the MCDATA server. + +**Table 7.14.2.1.1-1: MCDATA IPcon point-to-point request (MCDATA client to MCDATA server)** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| +| MCDATA ID | M | The MCDATA identity of the originator MCDATA user; | +| Functional alias | O | The associated functional alias of the originator MCDATA user; | +| MCDATA ID | O
(NOTE 2) | The MCDATA identity of the target MCDATA client IP connectivity is requested. | +| Functional alias | O
(NOTE 2) | The functional alias of the target MCDATA client. | +| Requested Priority
(NOTE 3) | O | Application priority level requested for this communication. | +| Location Information | O
(NOTE 1) | Actual location information of the originating MCDATA user; | +| Time Limit | O | Proposed time limit of the requested IP connectivity (1min- infinite); | +| Establishment reason | O | IP connectivity establishment reason | +| NOTE 1: This information contains the latest available location information of the requesting MCDATA user that may be different to the latest available location information in the MC system. | | | +| NOTE 2: Either the MCDATA ID or the functional alias of the target MCDATA user must be present. | | | +| NOTE 3: The predefined priority of the MC service user is applied by the MCDATA server if the requested priority is not present or not accepted by the MCDATA server. | | | + +**Table 7.14.2.1.1-2: MCDATA IPcon point-to-point request (MCDATA server to MCDATA client)** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| +| MCDATA ID | M | The MCDATA identity of the originator MCDATA user; | +| MCDATA ID | M | The MCDATA identity of the target MCDATA client IP connectivity is requested. | +| Location Information | O
(NOTE 1) | Actual location information of the originating MCDATA user; | +| Time Limit | O | Proposed time limit of the requested IP connectivity (1min- infinite); | +| Establishment reason | O | IP connectivity establishment reason | +| NOTE 1: This information contains the latest available location information of the requesting MCDATA user. | | | + +##### 7.14.2.1.2 MCDATA IPcon point-to-point response + +Table 7.14.2.1.2-1 describes the information content of the MCDATA IPcon point-to-point response as answer to MCDATA IPcon point-to-point request. + +**Table 7.14.2.1.2-1: MCDATA IPcon point-to-point response** + +| Information element | Status | Description | +|------------------------|--------|----------------------------------------------------| +| MCDATA ID | M | The MCDATA identity of the targeted MCDATA user. | +| MCDATA ID | M | The MCDATA identity of the requesting MCDATA user. | +| Time Limit | O | Negotiated time (1 min – infinite) | +| IP connectivity status | M | IP connectivity establishment result | + +##### 7.14.2.1.3 MCDATA remote IPcon point-to-point request + +Table 7.14.2.1.3-1 describes the information flow of the MCDATA remote IPcon point-to-point request sent from the remote MCDATA client to the MCDATA server and from the MCDATA server to the asked MCDATA client. + +**Table 7.14.2.1.3-1: MCDATA remote IPcon point-to-point request** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID remote | M | The MCDATA identity of the remote MCDATA client that requests another MCDATA user to establish an IP connectivity point-to-point session. | +| Functional alias remote | O | The associated functional alias of the remote MCDATA user. | +| MCDATA ID asked | M | The MCDATA identity of the MCDATA client that is required to establish an IP connectivity point-to-point session. | +| Functional alias asked | O | The functional alias associated with the MCDATA identity of the MCDATA client that is required to establish an IP connectivity point-to-point session. | +| MCDATA ID targeted (NOTE 1) | O | The MCDATA identity of the MCDATA client that is the target of the requested IP connectivity point-to-point session. | +| Functional alias targeted (NOTE 1) | O | The functional alias associated with the MC MCDATA identity of the MCDATA client that is the target of the requested IP connectivity point-to-point session. | +| Requested Priority (NOTE 2) | O | Application priority level requested for this call. | +| Time Limit | O | Proposed time limit of the requested IP connectivity (1min- infinite). | +| Establishment reason | O | IP connectivity establishment reason | +| NOTE 1: Either the MCDATA ID or the functional alias of the targeted MCDATA user must be present.
NOTE 2: The predefined priority of the MC service user is applied by the MCDATA server if the requested priority is not present or not accepted by the MCDATA server. | | | + +##### 7.14.2.1.4 MCDATA remote IPcon point-to-point response + +Table 7.14.2.1.4-1 describes the information content of the MCDATA remote IPcon point-to-point response as answer to MCDATA remote IPcon point-to-point request. + +**Table 7.14.2.1.4-1: MCDATA remote IPcon point-to-point response** + +| Information element | Status | Description | +|------------------------|--------|-------------------------------------------------------------------------------------| +| MCDATA ID asked | M | The MCDATA identity of the asked MCDATA client in the request message; | +| MCDATA ID targeted | M | The MCDATA identity of the targeted MCDATA client in the request message; | +| IP connectivity status | M | The status information about the IP connectivity session to the remote MCDATA user. | + +##### 7.14.2.1.5 MCDATA remote IPcon point-to-point tear down request + +Table 7.14.2.1.5-1 describes the information flow of the MCDATA remote IPcon point-to-point tear down request sent from the remote MCDATA client to the MCDATA server and from the MCDATA server to the asked MCDATA client. + +**Table 7.14.2.1.5-1: MCData remote IPcon point-to-point tear down request** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID remote | M | The MCData identity of the remote MCData client that requests another MCData user to tear down an IP connectivity point-to-point session. | +| Functional alias remote | O | The associated functional alias of the remote MCData user; | +| MCData ID asked | M | The MCData identity of the MCData client that is asked to tear down an IP connectivity point-to-point session. | +| MCData ID targeted | M | The MCData identity of the MCData client that is the target to be tear down from the IP connectivity point-to-point session. | + +##### 7.14.2.1.6 MCData remote IPcon point-to-point tear down response + +Table 7.14.2.1.6-1 describes the information content of the MCData remote IPcon point-to-point tear down response as answer to MCData remote IPcon point-to-point tear down request. + +**Table 7.14.2.1.6-1: MCData remote IPcon point-to-point tear down response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MCData ID asked | M | The MCData identity of the asked MCData client in the request message. | +| MCData ID targeted | M | The MCData identity of the targeted MCData client in the request message. | +| Tear down status | M | The status information about the IP connectivity tear down status information | + +##### 7.14.2.1.7 MCData remote IPcon point-to-point application priority change request + +Table 7.14.2.1.7-1 describes the information flow of the MCData remote IPcon point-to-point application priority change request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client. + +**Table 7.14.2.1.7-1: MCData remote IPcon point-to-point application priority change request** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID remote | M | The MCData identity of the remote MCData client that requests to change the application priority of an IP connectivity point-to-point session. | +| Functional alias remote | O | The associated functional alias of the remote MCData user; | +| MCData ID | M | The first MCData identity of the MCData client that is involved in the IP connectivity point-to-point session. | +| MCData ID | M | The second MCData identity of the MCData client that is involved in the IP connectivity point-to-point session. | +| Requested Priority | M | Contains the required application priority for the IP data communication between both MCData clients. | + +##### 7.14.2.1.8 MCData remote IPcon point-to-point application priority change response + +Table 7.14.2.1.8-1 describes the information content of the MCData remote IPcon point-to-point application priority change response as answer to MCData remote IPcon point-to-point application priority change request. + +**Table 7.14.2.1.8-1: MCData remote IPcon point-to-point application priority change response** + +| Information element | Status | Description | +|----------------------------------|--------|---------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData identity of the first MCData client involved in the IP connectivity point-to-point session. | +| MCData ID | M | The MCData identity of the second MCData client involved in the IP connectivity point-to-point session. | +| Requested priority change status | M | The status information about the application priority of the addressed IP connectivity session. | + +#### 7.14.2.2 IP connectivity point-to-point MCData transport service + +##### 7.14.2.2.1 General + +IP connectivity service capabilities enables MCData unaware data hosts to use usual MCData service capabilities, e.g. data communication between them. This subclause describes the establishment of a point-to-point connection between two IP connectivity clients using the media plane for IP Data transmission. The target MCData user may be addressed using the functional alias that can be shared by multiple MCData users. + +In order not to violate the point-to-point principle when a functional alias is shared, only two MCData user can participate to a point-to-point IP connectivity session. If the MCData server detects that the functional alias used as the target of the MCData FD request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the IP connectivity request, if no suitable MCData ID is selected. + +##### 7.14.2.2.2 Procedure + +The procedure in figure 7.14.2.2.2-1 describes the case where an IP connectivity capable MCData client is initiating a point-to-point IP connectivity with another IP connectivity capable MCData client. + +Pre-conditions: + +- The total data volume limit, e.g. daily time limit or total data volume per day does not restrict the establishment of an IP connectivity IP data exchange. +- MCData clients are linked with individual data hosts. +- MCData clients belong to the same MCData system. +- The data hosts linked with the MCData clients already have an IP address allocated. +- MCData clients have IP connectivity capabilities. +- The linked data hosts are authorized to use the MCData clients to establish an IP connectivity. + +NOTE: How the data host is authorized to use the MCData client is out of the scope of the present document. + +- The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. +- MCData client 1 understands the correspondence between the IP addresses of target data hosts and MCData client 2. How this relationship is determined is out of scope of the present document. +- Optionally, the MCData clients may have activated a functional alias to be used. + +![Sequence diagram illustrating the establishment of a point-to-point IP connectivity between MCData client 1, MCData server, and MCData client 2.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. Initiate data request + MCData client 1->>MCData server: 2. MCData IPcon point-to-point request + MCData server->>MCData server: 3. Authorize request + MCData server-->>MCData client 1: 4. MCData Functional alias resolution response + MCData client 1->>MCData server: 5. MCData IPcon point-to-point request + MCData server->>MCData client 2: 6. MCData IPcon point-to-point request + MCData client 2-->>MCData server: 7. MCData IPcon point-to-point response + MCData server-->>MCData client 1: 8. MCData IPcon point-to-point response + Note right of MCData server: 9. Transmission/ Reception control + Note bottom: 10. IP Data Transmission + +``` + +Sequence diagram illustrating the establishment of a point-to-point IP connectivity between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.14.2.2.2-1: Establishment of a point-to-point IP connectivity** + +1. MCData client 1 has IP Data to send to MCData client 2 and initiates an IP connectivity point-to-point request. +2. MCData client 1 sends a MCData IPcon point-to-point request towards the MCData server. The MCData IPcon point-to-point request contains either the MCData ID of MCData client 2 or its associated functional alias. MCData user at MCData client 1 may include its associated functional alias +3. MCData server checks whether MCData user at MCData client 1 is authorized to send an MCData IPcon point-to-point request and checks if MCData client 2 is authorised to receive the IP connectivity service. If a functional alias is used to address the target MCData user, the MCData server resolves the functional alias to the corresponding MCData ID(s) for which the functional alias is active and proceed with step 4 otherwise proceed with step 6. +4. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID. +5. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 assumes the MCData IPcon point-to-point request in step 2 is rejected and sends a new MCData IPcon point-to-point request towards the resolved MCData ID. +6. MCData server initiates the MCData IPcon point-to-point request towards the determined MCData client 2. + +NOTE: MCData client 2 corresponds to the MCData user(s) after resolution of the functional alias. + +7. MCData client 2 sends a MCData IPcon point-to-point response to the MCData server that contains the information if the request is accepted or the reason of rejection. If accepted, the MCData client 2 may include the data transmission time limit. +8. MCData server forwards the MCData IPcon point-to-point response of MCData client 2 to MCData client 1. +9. The MCData server applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData clients. +10. MCData client 1 and MCData Client 2 have successfully established media plane for data communication and MCData client 1 and MCData client 2 exchange IP Data. + +#### 7.14.2.3 Remote initiated point-to-point IP connectivity + +##### 7.14.2.3.1 General + +The MCData service shall support mechanisms that allow an authorized MCData user to trigger remotely the establishment of a point-to-point IP connectivity service. This encompasses the procedure of a remote MCData user that addresses the establishment of an IP connectivity between the requested MCData client and the destination MCData client. + +##### 7.14.2.3.2 Procedure + +The procedure in figure 7.14.2.3.2-1 describes the case where an authorised MCData user triggers remotely the establishment of a point-to-point IP connectivity connection between two other MCData users, required MCData user that establish IP connectivity session to the targeted MCData user. + +Pre-conditions: + +- The MCData clients are linked with individual data hosts. +- MCData clients belong to the same MCData system. +- The data hosts linked with the MCData clients already have an IP address allocated. +- MCData clients have IP connectivity capabilities. +- The linked data hosts are authorized to use the MCData clients to establish an IP connectivity. + +NOTE: How the data host is authorized to use the MCData client is out of the scope of the present document. + +- The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. +- MCData clients understands the correspondence between the IP addresses of target data hosts and MCData client 3. How this relationship is determined is out of scope of the present document. +- Optionally, the MCData clients may have activated a functional alias to be used. +- MCData client 1 is authorized to establish remote initiated point-to-point IP connectivity sessions. + +![Sequence diagram showing the establishment of a remote point-to-point IP connectivity session. The participants are (remote) MCData client 1, MCData server, (asked) MCData Client 2, and (targeted) MCData Client 3. The sequence of messages is: 1. Remote initiated data request from client 1 to server; 2. MCData remote IPcon point-to-point request from client 1 to server; 3. Authorize request from server to client 2; 4. MCData remote IPcon point-to-point request from server to client 2; 5. Point-to-Point IP connectivity data establishment (a block spanning client 2 and client 3); 6. MCData remote IPcon point-to-point response from server to client 1; 7. MCData remote IPcon point-to-point response from client 1 to client 2.](9b62a616c7a1097c5da57f001ab6dd64_img.jpg) + +``` + +sequenceDiagram + participant Client1 as (remote) MCData client 1 + participant Server as MCData server + participant Client2 as (asked) MCData Client 2 + participant Client3 as (targeted) MCData Client 3 + + Note left of Client1: 1. Remote initiated data request + Client1->>Server: 2. MCData remote IPcon point-to-point request + Note right of Server: 3. Authorize request + Server->>Client2: 4. MCData remote IPcon point-to-point request + Note right of Client2: 5. Point-to-Point IP connectivity data establishment + Note right of Server: 6. MCData remote IPcon point-to-point response + Server->>Client1: 6. MCData remote IPcon point-to-point response + Note left of Client1: 7. MCData remote IPcon point-to-point response + Client1->>Client2: 7. MCData remote IPcon point-to-point response + +``` + +Sequence diagram showing the establishment of a remote point-to-point IP connectivity session. The participants are (remote) MCData client 1, MCData server, (asked) MCData Client 2, and (targeted) MCData Client 3. The sequence of messages is: 1. Remote initiated data request from client 1 to server; 2. MCData remote IPcon point-to-point request from client 1 to server; 3. Authorize request from server to client 2; 4. MCData remote IPcon point-to-point request from server to client 2; 5. Point-to-Point IP connectivity data establishment (a block spanning client 2 and client 3); 6. MCData remote IPcon point-to-point response from server to client 1; 7. MCData remote IPcon point-to-point response from client 1 to client 2. + +**Figure 7.14.2.3.2-1: Establishment of a remote point-to-point IP connectivity** + +1. MCData client 1 would like to establish a remote point-to-point IP connectivity to allow IP Data exchange between two other MCData clients, the asked MCData client 2 and the targeted MCData client 3. + +2. The MCData client 1 sends an MCData remote IPcon point-to-point request towards the MCData server. The MCData IPcon point-to-point request contains the MCData ID and optionally the corresponding functional aliases of MCData client 2 and either the MCData ID or the functional alias of MCData client 3. MCData user at MCData client 1 may include its associated functional alias. +3. MCData server checks whether MCData user at MCData client 1 is authorized to send a remote MCData IPcon point-to-point request and if MCData client 2 and 3 are authorized to receive the IP connectivity service. +4. MCData server sends the MCData remote IPcon point-to-point request towards the MCData client 2. +5. MCData client 2 considers the provided targeted MCData ID or targeted functional alias to establish the point-to-point IP connectivity to MCData client 3 according to clause 7.14.2.2. The IP connectivity status shall be forwarded by MCData client 2 to MCData client 1. +6. MCData client 2 send an MCData remote IPcon point-to-point response to the MCData server encompassing the IP connectivity status of the point-to-point IP connectivity session between MCData client 2 and MCData client 3. +7. The MCData server forwards the MCData remote IPcon point-to-point response to the remote MCData client 1. + +#### 7.14.2.4 MCData user remote initiated tear down point-to-point IP connectivity + +##### 7.14.2.4.1 General + +The MCData service shall support mechanisms that allow an authorized MCData user to tear down remotely an established point-to-point IP connectivity. This encompasses the procedure of a remote MCData user that addresses the tear down of an IP connectivity between the requested MCData client and the destination MCData client. + +##### 7.14.2.4.2 Procedure + +The procedure in figure 7.14.2.4.2-1 describes the case where an authorised MCData user triggers remotely the tear down of a point-to-point IP connectivity connection between two other MCData users, the asked MCData user that tear down IP connectivity session to the targeted MCData user. + +Pre-conditions: + +- The point-to-point IP connectivity has been established between MCData client 2 and MCData client 3. +- Optionally, the MCData client 1 may have activated a functional alias to be used. +- MCData client 1 is authorized to tear down point-to-point IP connectivity sessions. + +![Sequence diagram illustrating the remote initiated tear down of a point-to-point IP connectivity. Lifelines: (remote) MCData client 1, MCData server, (asked) MCData Client 2, and (targeted) MCData Client 3. The sequence starts with a local '1. Tear down data session' at client 1. Client 1 sends a '2. MCData remote IPcon point-to-point tear down request' to the server. The server sends a '3. Authorize request' to client 2. Client 2 sends a '4. MCData remote IPcon point-to-point tear down request' to client 3. Client 3 performs a '5. MCData user initiated communication release'. Client 2 sends a '6. MCData remote IPcon point-to-point tear down response' to the server. Finally, the server sends a '7. MCData remote IPcon point-to-point tear down response' to client 1.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant C1 as (remote) MCData client 1 + participant S as MCData server + participant C2 as (asked) MCData Client 2 + participant C3 as (targeted) MCData Client 3 + + Note left of C1: 1. Tear down data session + C1->>S: 2. MCData remote IPcon point-to-point tear down request + S->>C2: 3. Authorize request + C2->>C3: 4. MCData remote IPcon point-to-point tear down request + Note right of C3: 5. MCData user initiated communication release + C3->>S: 6. MCData remote IPcon point-to-point tear down response + S->>C1: 7. MCData remote IPcon point-to-point tear down response + +``` + +Sequence diagram illustrating the remote initiated tear down of a point-to-point IP connectivity. Lifelines: (remote) MCData client 1, MCData server, (asked) MCData Client 2, and (targeted) MCData Client 3. The sequence starts with a local '1. Tear down data session' at client 1. Client 1 sends a '2. MCData remote IPcon point-to-point tear down request' to the server. The server sends a '3. Authorize request' to client 2. Client 2 sends a '4. MCData remote IPcon point-to-point tear down request' to client 3. Client 3 performs a '5. MCData user initiated communication release'. Client 2 sends a '6. MCData remote IPcon point-to-point tear down response' to the server. Finally, the server sends a '7. MCData remote IPcon point-to-point tear down response' to client 1. + +**Figure 7.14.2.4.2-1: Remote initiated tear down of a point-to-point IP connectivity** + +1. MCData client 1 would like to tear down a point-to-point IP connectivity between two other MCData clients, the asked MCData client 2 and the targeted MCData client 3. +2. The MCData client 1 sends an MCData remote IPcon point-to-point tear down request towards the MCData server. The MCData remote IPcon point-to-point tear down request contains the MCData IDs of MCData client 2 and MCData client 3. MCData user at MCData client 1 may include its associated functional alias. +3. MCData server checks whether MCData user at MCData client 1 is authorized to send MCData remote IPcon point-to-point tear down request and checks if the asked MCData client 2 is allowed to tear down an IP connectivity point-to-point session. +4. MCData server sends the MCData remote IPcon point-to-point tear down request towards the MCData client 2. +5. MCData client 2 considers the provided targeted MCData ID to tear down the point-to-point IP connectivity to MCData client 3. The status of the IP connectivity tear down request shall be forwarded by MCData client 2 to remote MCData client 1. +6. MCData client 2 sends MCData remote IPcon point-to-point tear down response to the MCData server encompassing the tear down IP connectivity status between MCData client 2 and MCData client 3. +7. The MCData server forwards the MCData remote IPcon point-to-point tear down response to the remote MCData client 1. + +#### 7.14.2.5 Remote initiated point-to-point IP connectivity application priority change + +##### 7.14.2.5.1 General + +The MCData service shall support mechanisms that allow an authorized MCData user to trigger remotely the adaptation of a point-to-point IP connectivity data bearer service priority. This encompasses the procedure of a remote MCData user that addresses the priority change of a point-to-point IP connectivity between the requested MCData clients. + +##### 7.14.2.5.2 Procedure + +The procedure in figure 7.14.2.5.2-1 describes the case where an authorised MCData user triggers remotely the priority change of a point-to-point IP connectivity connection between two other MCData users. + +Pre-conditions: + +- Optionally, the MCData client 1 may have activated a functional alias to be used. + +- A point-to-point IP connectivity is established between MCData client 2 and MCData client 3. +- MCData client 1 is authorized to change remotely communication priority of a point-to-point IP connectivity session. + +![Sequence diagram illustrating the point-to-point IP connectivity application priority change request by a remote MCData client. The diagram shows four lifelines: (remote) MCData client 1, MCData server, (requested) MCData Client 2, and (requested) MCData Client 3. The sequence of messages is: 1. Remote initiated application priority change (internal to client 1); 2. MCData remote IPcon point-to-point application priority change request (client 1 to server); 3. Authorize request (server to client 1); 4. Apply priority change (server to clients 2 and 3, shown as a dashed box); 5. MCData remote IPcon point-to-point application priority change response (server to client 1).](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +sequenceDiagram + participant Client1 as (remote) MCData client 1 + participant Server as MCData server + participant Client2 as (requested) MCData Client 2 + participant Client3 as (requested) MCData Client 3 + Note left of Client1: 1. Remote initiated application priority change + Client1->>Server: 2. MCData remote IPcon point-to-point application priority change request + Note right of Server: 3. Authorize request + Note right of Server: 4. Apply priority change + Server-->>Client1: 5. MCData remote IPcon point-to-point application priority change response + +``` + +Sequence diagram illustrating the point-to-point IP connectivity application priority change request by a remote MCData client. The diagram shows four lifelines: (remote) MCData client 1, MCData server, (requested) MCData Client 2, and (requested) MCData Client 3. The sequence of messages is: 1. Remote initiated application priority change (internal to client 1); 2. MCData remote IPcon point-to-point application priority change request (client 1 to server); 3. Authorize request (server to client 1); 4. Apply priority change (server to clients 2 and 3, shown as a dashed box); 5. MCData remote IPcon point-to-point application priority change response (server to client 1). + +**Figure 7.14.2.5.2-1: Point-to-point IP connectivity application priority change request by a remote MCData client** + +1. MCData client 1 would like to change the priority that corresponds to an established point-to-point IP connectivity between MCData client 2 and MCData client 3. +2. The MCData client 1 sends a remote MCData IPcon point-to-point application priority change request towards the MCData server. The MCData IPcon point-to-point application priority change request contains the MCData IDs of MCData client 2 and MCData client 3. MCData user at MCData client 1 may include its associated functional alias. +3. MCData server checks whether MCData user at MCData client 1 is authorized to send a remote MCData IPcon point-to-point application priority change request. +4. MCData server applies the requested priority to the point-to-point IP connectivity between MCData client 2 and MCData client 3. + +NOTE: Necessary adjustments in the relevant transport system can be included. + +5. MCData server sends the remote MCData IPcon point-to-point application priority change response to MCData client 1 encompassing the priority status of the point-to-point IP connectivity between MCData client 2 and MCData client 3. + +#### 7.14.2.6 Group standalone IP connectivity using media plane + +##### 7.14.2.6.1 General + +IP connectivity service capabilities enables authorized MCData unaware data host to use usual MCData service capabilities, e.g. data communication among them. This subclause describes the establishment of a group standalone IP connectivity to a selected MCData group results in affiliated group members exchanging IP data. + +##### 7.14.2.6.2 Procedure + +The procedure in figure 7.14.2.6.2-1 describes the case where an IP connectivity capable MCData client is initiating group standalone MCData IP connectivity communication session with an MCData group for exchanging IP Data between group participants using MCData IPcon-2 reference point. + +Pre-conditions: + +- MCData client 1 to MCData client n belong to the same MCData group, are registered for receiving MCData service and are affiliated to the corresponding MCData group. +- The total data volume limit, e.g. daily time limit or total data volume per day, does not restrict the establishment of an IP connectivity MCData transmission. +- MCData client 1 to MCData client n are linked with individual data hosts. +- MCData client 1 to MCData client n belong to the same MCData system. +- The data hosts linked with the MCData clients already have an IP address allocated. +- MCData clients have IP connectivity capabilities. +- The linked data hosts are authorized to use the MCData clients to establish an IP connectivity. + +NOTE 1: How the data host is authorized to use the MCData client is out of the scope of the present document. + +- The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. +- MCData clients understand the correspondence between the IP addresses of target data hosts and MCData clients. How this relationship is determined is out of scope of the present document. +- MCData clients understand the relationship between the addressing of IP packets which are intended to be sent to the group and the MCData group address. + +NOTE 2: The allocation of IP addresses for group addressed communication is outside the scope of the present document. + +![Sequence diagram for Figure 7.14.2.6.2-1 showing the interaction between MCData client 1, MCData server, Group management server, and MCData client 2 to n. Step 1 shows MCData client 1 receiving an IP packet. Step 2 is a broad horizontal bar spanning all entities representing the 'Group standalone data service using media plane'. Step 3 shows MCData client 2 to n indicating reception to their attached data hosts.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant S as MCData server + participant GMS as Group management server + participant Cn as MCData client 2 to n + + Note over C1: 1. Receive IP packet addressed to a group + rect rgb(255, 255, 255) + Note over C1, Cn: 2. Group standalone data service using media plane + end + Note over Cn: 3. Indicate reception of IP Data to the attached data host(s) + +``` + +Sequence diagram for Figure 7.14.2.6.2-1 showing the interaction between MCData client 1, MCData server, Group management server, and MCData client 2 to n. Step 1 shows MCData client 1 receiving an IP packet. Step 2 is a broad horizontal bar spanning all entities representing the 'Group standalone data service using media plane'. Step 3 shows MCData client 2 to n indicating reception to their attached data hosts. + +**Figure 7.14.2.6.2-1: Establishment of IPcon group standalone communication session** + +1. MCData client 1 receives an IP packet from the IP data host which is addressed to an IP address that signifies an MCData group destination. +2. MCData client 1 uses the MCData group standalone short data service using media plane procedure in accordance with clause 7.4.2.6 to establish IPcon group standalone communication session to the MCData user that are members of the corresponding MCData group with the following scope: + - IP Data exchange + - The application identifier is used to indicate about the use of a group communication in the IP connectivity context + - Payload destination indicates the consumption by the linked data host + - The use of disposition shall be discarded for the use of IP connectivity +3. MCData clients 2-n recognize that the payload is for IP connectivity service and forward the received IP data to the linked data hosts. + +## 7.15 Location information (on-network) + +The MCData system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [5], utilising the CSC-14 reference point between the location management client and location management server and the CSC-15 reference point between the MCData server and location management server. + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group is the MCData group; +- The MC service ID is the MCData ID; and +- The MC service group ID is the MCData group ID. + +## 7.16 Use of ProSe capabilities in off-network MCData communications + +### 7.16.1 General + +When an MCData user using a ProSe-enabled UE wants to communicate with a specific MCData group or MCData user using ProSe capabilities, the MCData client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7]. + +For an off-network MCData group communication, the MCData client obtains configuration data such as the user info ID of the MCData user sending data and the ProSe Group IP multicast address and ProSe Layer-2 Group ID associated to the target MCData group (as described in clause 8.1.3.2 in 3GPP TS 23.280 [5]), and provides it to the ProSe layer. The ProSe Layer-2 Group ID of the target MCData group may be used by the ProSe layer as the target group info and the discovery group ID (defined in 3GPP TS 23.303 [7]). + +Prior to initiating an off-network MCData group communication, a group member discovery procedure may be initiated to identify whether other members of the target MCData group are in the proximity of the MCData user sending data, as described in the ProSe direct discovery for public safety use procedure in 3GPP TS 23.303 [7]. The off-network MCData group communication using the ProSe capability is based on the one-to-many ProSe direct communication procedure for public safety use described in 3GPP TS 23.303 [7]. + +For an off-network one-to-one MCData communication, the MCData client obtains configuration data such as the ProSe discovery group ID and user info ID of the target MCData user from the "List of MCData users this MCData user is authorized to initiate a one to-one communication" in the MCData user profile and requests the IP address of the MCData UE associated with the target MCData user from the ProSe layer. + +The MCData client enables the ProSe layer to determine the IP address for the communication with the target MCData UE by providing the ProSe discovery group ID and user info ID (as defined in 3GPP TS 23.303 [7]) associated to the target MCData user. This may trigger the ProSe direct discovery for public safety use procedure to identify whether the target MCData user is in the proximity of the MCData user sending data. The user info ID of the target MCData user is used by the ProSe layer as the target info (as defined in 3GPP TS 23.303 [7]). + +The ProSe layer can then provide the IP address related to the target MCData user to the MCData client to initiate the off-network one-to-one MCData communication based on the one-to-one ProSe direct communication procedure described in 3GPP TS 23.303 [7]. + +### 7.16.2 Procedures + +The off-network MCData communication procedures using the ProSe capabilities are described within the corresponding clauses of each MCData capability, e.g. SDS procedures for off-network are described in clause 7.4.3 and file distribution procedures for off-network are described in clause 7.5.3. + +## 7.17 Ad hoc group data communication + +### 7.17.1 General + +This subclause contains procedures for ad hoc group data communication across a single MCData system for both SDS and FD services, and associated functions such as emergency data communication, Imminent peril data communication and others. + +The ad hoc group data communications can use the participants list provided by either an initiator of the data communication or MCData server. The MCData server can use the criteria provided by the initiator of the data communication to determine the participants list along with its own criteria or local policies. The resulting ad hoc group uses the configuration of a separate preconfigured MCData group. + +NOTE 1: A preconfigured group which is intended only to provide configuration for the ad hoc group is identified by a parameter in the group configuration described in 3GPP TS 23.280 [5]. + +The preconfigured MCData group that provides the configuration is not used for the MCData group communication, it only provides configuration for one or more adhoc group data communications. The MCData group ID of the ad hoc group data communication is provided by the MCData server when the ad hoc group data communication is originated. In order to establish security context for the end-to-end secured ad hoc group data communication, the security related information is used from this preconfigured group. + +NOTE 2: The configurations defined for the adhoc group data communication in user profile and service configuration document as described in the Annex A.3 and A.5 is applicable only for single MCData system. + +### 7.17.2 Common Information flows + +#### 7.17.2.1 Ad hoc group data session request (MCData client – MCData server) + +Table 7.17.2.1-1 describes the information flow ad hoc group data session request from the MCData client to the MCData server. + +##### **Table 7.17.2.1-1 Ad hoc group data session request information elements** + +| Information Element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ad hoc group ID (see NOTE 1) | O | The MCData group ID to be associated with the ad hoc group data communication | +| Encryption supported (see NOTE 2) | O | Indicates whether this ad hoc group data communication supports end-to-end encryption | +| MCData ID list (see NOTE 3, NOTE 5, NOTE 6) | O | MCData IDs of the participants being invited for the ad hoc group data communication | +| SDP offer | M | Offered media parameters | +| Imminent peril indicator (see NOTE 4) | O | Indicates that the ad hoc group data communication request is for ad hoc group imminent peril data communication | +| Emergency Indicator (see NOTE 4) | O | Indicates that the ad hoc group data communication request is for ad hoc group emergency data communication | +| Broadcast indicator (see NOTE 4) | O | Indicates that the ad hoc group data communication request is for a broadcast ad hoc group data communication | +| MCData ID list (see NOTE 3) | O | List of participants required to acknowledge the ad hoc group data communication before start of the data transmission | +| Location information | O | Location of the of the MCData user sending data. | +| Criteria for determining the participants (see NOTE 5) | O | Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area | +| Requested priority | O | Application priority level requested for this ad hoc group data communication | +|

NOTE 1: If this information element is not included, the MCData server assigns an MCData ad hoc group ID to be used for the ad hoc group data communication. This information element is returned to the MCData user who is sending the data to use in the ad hoc group data communication. If the request follows an ad hoc group for emergency alert, then this element must be present.

NOTE 2: This information element is present and set to true only if this ad hoc group data communication is encrypted. When the ad hoc group data communication is initiated with participants provided by the initiator this acts as an indicator that subsequent requests follow targeting the individual participants and carrying the relevant key material. If this information element is set to false or not present, then this ad hoc group data communication is unencrypted.

NOTE 3: This element is included only when the data communication initiating client sends the list of participants.

NOTE 4: If used, only one of these information elements is present.

NOTE 5: Only one of these information elements is present.

NOTE 6: If the request follows an ad hoc group for emergency alert, then this element is not present.

| | | + +#### 7.17.2.2 Ad hoc group data session request return (MCData server – MCData client) + +Table 7.17.2.2-1 describes the information flow ad hoc group data session request return from the MCData server to the MCData client. This response could be intermediate response to provide the server assigned MCData ad hoc group ID. + +**Table 7.17.2.2-1 Ad hoc group data session request return information elements** + +| Information Element | Status | Description | +|-------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ad hoc group ID | O | The MCData group ID to be associated with the ad hoc group data communication which is either provided by the group data session initiator or assigned by the MCData server. This information element shall be present if the authorization result is success. | +| Preconfigured MCData group ID | O | Group identity whose configuration is to be applied for this ad hoc group data communication. | +| Authorization result | M | Indicate if authorization is success or failure | + +#### 7.17.2.3 Ad hoc group data session request (MCData server – MCData server) + +Table 7.17.2.3-1 describes the information flow ad hoc group data session request between the MCData servers. + +**Table 7.17.2.3-1 Ad hoc group data session request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ad hoc group ID | M | The MCData group ID to be associated with the ad hoc group data communication | +| MCData ID list (see NOTE 1, NOTE 3) | O | MCData IDs of the participants being invited for the ad hoc group data communication | +| SDP offer | M | Media parameters of MCData server | +| Broadcast indicator (see NOTE 2) | O | Indicates that the ad hoc group data communication request is for a broadcast ad hoc group data communication | +| Imminent peril indicator (see NOTE 2) | O | Indicates that the ad hoc group data communication request is for ad hoc group imminent peril data communication | +| Emergency Indicator (see NOTE 2) | O | Indicates that the ad hoc group data communication request is for ad hoc group emergency data communication | +| Preconfigured MCData group ID | O | Group identity whose configuration is to be applied for this ad hoc group data communication. | +| Criteria for determining the participants (see NOTE 3) | O | Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area | +| Requested priority | O | Application priority level requested for this group data communication | +| NOTE 1: This element is included only when the data communication initiating client sends the list of participants.
NOTE 2: If used, only one of these information elements is present.
NOTE 3: Only one of these information elements is present. | | | + +Editor's Note: It is FFS if the server to server message is needed in a call request or response message. + +#### 7.17.2.4 Ad hoc group data session request (MCData server – MCData client) + +Table 7.17.2.4-1 describes the information flow ad hoc group data session request from the MCData server to the MCData client. + +**Table 7.17.2.4-1 Ad hoc group data session request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the request is sent | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group data communication | +| SDP offer | M | Media parameters of MCData server | +| Broadcast indicator (see NOTE) | O | Indicates that the ad hoc group data communication request is for a broadcast ad hoc group data communication | +| Imminent peril indicator (see NOTE) | O | Indicates that the ad hoc group data communication request is for ad hoc group imminent peril data communication | +| Emergency Indicator (see NOTE) | O | Indicates that the ad hoc group data communication request is for ad hoc group emergency data communication | +| Preconfigured MCData group ID | O | Group identity whose configuration is to be applied for this ad hoc group data communication. | +| NOTE: If used, only one of these information elements is present. | | | + +#### 7.17.2.5 Ad hoc group data session response (MCData server – MCData client) + +Table 7.17.2.5-1 describes the information flow ad hoc group data session response from the MCData server to the MCData client. + +**Table 7.17.2.5-1 Ad hoc group data session response information elements** + +| Information Element | Status | Description | +|------------------------|--------|-------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group data communication | +| SDP answer | O | Media parameters selected and present if the Result is success. | +| Result | M | Result of the group data communication request (success or failure) | + +#### 7.17.2.6 Ad hoc group data session response (MCData server – MCData server) + +Table 7.17.2.6-1 describes the information flow ad hoc group data session response between the MCData servers. + +**Table 7.17.2.6-1: Ad hoc group data session response information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| Functional alias | O | The functional alias of the MCData user receiving data | +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group data communication | +| SDP answer | O | Media parameters selected and present if the Result is success. | +| Result | M | Result of the ad hoc group data communication request (success or failure) | + +Editor's Note: It is FFS if the server to server message is needed in a call request or response message. + +#### 7.17.2.7 Ad hoc group data session response (MCData client – MCData server) + +Table 7.17.2.7-1 describes the information flow ad hoc group data session response from the MCData client to the MCData server. + +**Table 7.17.2.7-1 Ad hoc group data session response information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| Functional alias | O | The functional alias of the MCData user receiving data | +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group data communication | +| SDP answer | O | Media parameters selected and present if the Result is success. | +| Result | M | Result of the ad hoc group data communication request (success or failure) | + +#### 7.17.2.8 Ad hoc group data session release request (MCData server – MCData client) + +Table 7.17.2.8-1 describes the information flow ad hoc group data session release request from the MCData server to the MCData client. + +**Table 7.17.2.8-1 Ad hoc group data session release request information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the ad hoc group data communication participant | +| Functional alias | O | The functional alias of the ad hoc group data communication participant | +| MCData ad hoc group ID | M | The MCData group ID of the ad hoc group data communication on which data communication is released | + +#### 7.17.2.9 Ad hoc group data session release response (MCData client – MCData server) + +Table 7.17.2.9-1 describes the information flow ad hoc group data session release response from the MCData server to the MCData client. + +**Table 7.17.2.9-1 Ad hoc group data session release response information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the ad hoc group data communication participant | +| Functional alias | O | The functional alias of the ad hoc group data communication participant | +| MCData ad hoc group ID | M | The MCData group ID of the ad hoc group data communication on which data communication is released | + +#### 7.17.2.10 Ad hoc group data session notify (MCData server – MCData client) + +Table 7.17.2.10-1 describes the information flow ad hoc group data session notify from MCData server to MCData client. + +**Table 7.17.2.10-1: Ad hoc group data session notify** + +| Information element | Status | Description | +|------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the ad hoc group data communication participant | +| Functional alias | O | The associated functional alias of the MCData user of the ad hoc group data communication participant | +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group data communication | +| MCData ID list | O | The list of the invited MCData users who did not acknowledged the ad hoc group data communication request within a configured time or the list of the invited MCData users who acknowledged the ad hoc group data communication request and joined or the list of the MCData users who joined or left the ongoing MCData ad hoc group data communication. | + +#### 7.17.2.11 Modify ad hoc group data session participants request (MCData client – MCData server) + +Table 7.17.2.11-1 describes the information flow Modify ad hoc group data session participants request from the MCData client to the MCData server. + +**Table 7.17.2.11-1: Modify ad hoc group data session participants request** + +| Information element | Status | Description | +|-------------------------------------------------------------------|---------------|---------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the requesting MCData user who is authorized to modify the ad hoc group data session participants | +| Functional alias | O | The functional alias of the requesting MCData user who is authorized to modify the ad hoc group data session participants | +| MCData ad hoc group ID | M | The MCData group ID of ad hoc group data communication whose participants needs to be modified | +| MCData ID list (see NOTE) | O | List of additional MCData users to be added to the on-going ad hoc group data communication | +| MCData ID list (see NOTE) | O | List of MCData users to be removed from the on-going ad hoc group data communication | +| NOTE: Either one or both of these information elements is present | | | + +#### 7.17.2.12 Modify ad hoc group data session participants response (MCData server – MCData client) + +Table 7.17.2.12-1 describes the information flow Modify ad hoc group data session participants response from the MCData server to the MCData client. + +**Table 7.17.2.12-1: Modify Ad hoc group data session participants response information elements** + +| Information Element | Status | Description | +|----------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the requesting MCData user who is authorized to modify the ad hoc group data session participants | +| Functional alias | O | The functional alias of the requesting MCData user who is authorized to modify the ad hoc group data session participants | +| MCData ad hoc group ID | M | The MCData group ID of ad hoc group data communication whose participants needs to be modified | +| Result | M | Result of the modify ad hoc group data communication participants request (success or failure) | +| MCData ID list | O | List of MCData users who are not allowed to be added to the on-going ad hoc group data communication. This list is provided if the operation is partially success. | + +#### 7.17.2.13 Ad hoc group data session leave request (MCData server – MCData client) + +Table 7.17.2.13-1 describes the information flow ad hoc group data session leave request from the MCData server to the MCData client. + +**Table 7.17.2.13-1 Ad hoc group data session leave request information elements** + +| Information Element | Status | Description | +|----------------------------|---------------|-----------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication | +| MCData ad hoc group ID | M | The MCData group ID of ad hoc group data communication | +| Reason to leave | O | Carries the reason of why the MCData client is being asked to leave the ongoing ad hoc group data communication | + +#### 7.17.2.14 Ad hoc group data session leave response (MCData client – MCData server) + +Table 7.17.2.14-1 describes the information flow Ad hoc group data session leave response from the MCData client to the MCData server. + +**Table 7.17.2.14-1 Ad hoc group data session leave response information elements** + +| Information Element | Status | Description | +|----------------------------|---------------|--------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication | +| MCData ad hoc group ID | M | The MCData group ID of ad hoc group data communication | + +#### 7.17.2.15 Ad hoc group data session get userlist (MCData server – MCData server) + +Table 7.17.2.15-1 describes the information flow ad hoc group data session get userlist from one MCData server to another MCData server. + +**Table 7.17.2.15-1: Ad hoc group data session get userlist** + +| Information element | Status | Description | +|-------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group communication | +| Criteria for determining the participants | M | Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area | + +#### 7.17.2.16 Ad hoc group data session get userlist response (MCData server – MCData server) + +Table 7.17.2.16-1 describes the information flow ad hoc group data session get userlist response from one MCData server to another MCData server. + +**Table 7.17.2.16-1: Ad hoc group data session get userlist response** + +| Information element | Status | Description | +|----------------------------|---------------|-------------------------------------------------------------------------------------------------| +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group communication | +| MCData ID list | M | List of MCData IDs meeting the criteria specified in the ad hoc group data session get userlist | + +#### 7.17.2.17 Ad hoc group data session add user notification (MCData server – MCData server) + +Table 7.17.2.17-1 describes the information flow Ad hoc group data session add user notification from one MCData server to another MCData server. This notification is to provide the list of MCData IDs meeting the criteria specified in the ad hoc group data session get userlist request from one MCData server to another MCData server. + +**Table 7.17.2.17-1: Ad hoc group data session add user notification information elements** + +| Information Element | Status | Description | +|------------------------|--------|-------------------------------------------------------------------------------------------------| +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group communication | +| MCData ID list | M | List of MCData IDs meeting the criteria specified in the ad hoc group data session get userlist | + +#### 7.17.2.18 Ad hoc group data session remove user notification (MCData server – MCData server) + +Table 7.17.2.18-1 describes the information flow Ad hoc group data session remove user notification from one MCData server to another MCData server. This notification is to provide the list of MCData IDs no longer meeting the criteria specified in the ad hoc group data session get userlist request from one MCData server to another MCData server. + +**Table 7.17.2.18-1: Ad hoc group data session remove user notification information elements** + +| Information Element | Status | Description | +|------------------------|--------|-----------------------------------------------------------------------------------------------------------| +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group communication | +| MCData ID list | M | List of MCData IDs no longer meeting the criteria specified in the ad hoc group data session get userlist | + +#### 7.17.2.19 Ad hoc group data session release notification (MCData server – MCData server) + +Table 7.17.2.19 -1 describes the information flow Ad hoc group data session release notification from one MCData server to another MCData server. This notification is to indicate to stop evaluating the criteria to determine the participants list if another MCData server is having the criteria specified in the ad hoc group data session get userlist request. + +**Table 7.17.2.19-1: Ad hoc group data session release notification information elements** + +| Information Element | Status | Description | +|------------------------|--------|--------------------------------------------------------------------| +| MCData ad hoc group ID | M | The MCData group ID associated with the ad hoc group communication | + +## 7.17.3 Common Ad hoc group data communication procedures + +#### 7.17.3.1 Ad hoc group data communication procedures in single MCData system + +##### 7.17.3.1.1 Ad hoc group data communication setup + +Figure 7.17.3.1.1-1 below illustrates the ad hoc group data communication setup procedure initiated by an authorized user. + +Pre-conditions: + +1. The authorized user at MCData client 1 wants to invite MCData users at MCData client 2, MCData client 3 and MCData client 4 for the ad hoc group data communication or to invite the ad hoc group member if the ad hoc group call follows an ad hoc group emergency alert, the MCData client 1 is aware of the ad hoc group ID. +2. Number of participants being invited for the ad hoc group data communication is within the limit. +3. End-to-End encryption is supported for this ad hoc group data communication. +4. MCData client 1 is aware of the MCData IDs of the participants. + +NOTE 1: Selection of MCData IDs of the participants can be manual or from the user profile configuration data or by any other means. This is left for the implementation. + +5. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCData client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication. + +![Sequence diagram for ad hoc group data communication setup between MCData client 1, MCData server, MCData client 2, MCData client 3, and MCData client 4.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + participant MCData client 4 + + Note right of MCData server: 2. Authorise + + MCData client 1->>MCData server: 1. Ad hoc group data session request + MCData server-->>MCData client 1: 3. Ad hoc group data session request return + MCData server->>MCData client 2: 4a. Ad hoc group data session request + MCData client 2->>MCData client 3: 4b. Ad hoc group data session request + MCData client 3->>MCData client 4: 4c. Ad hoc group data session request + Note right of MCData client 2: 5a.Notify ad hoc group data session request + Note right of MCData client 3: 5b.Notify ad hoc group data session request + Note right of MCData client 4: 5c.Notify ad hoc group data session request + MCData client 2->>MCData server: 6a. Ad hoc group data session response + MCData client 3->>MCData server: 6b. Ad hoc group data session response + MCData client 4->>MCData server: 6c. Ad hoc group data session response + MCData server-->>MCData client 1: 7. Ad hoc group data session response + MCData client 1-->>MCData client 1: 8. Ad hoc group data session Notify + Note bottom: 9. Media plane establishment for data transmission + +``` + +Sequence diagram for ad hoc group data communication setup between MCData client 1, MCData server, MCData client 2, MCData client 3, and MCData client 4. + +**Figure 7.17.3.1.1-1: Ad hoc group data communication setup** + +- User at MCData client 1 would like to initiate an ad hoc group data communication. The MCData client 1 initiates the ad hoc group data communication by sending the ad hoc group data session request containing the list of participants or an ad hoc group ID from an ad hoc group emergency alert. Encryption supported information element shall be set to true since end-to-end encryption is supported. An SDP offer containing the MCData client media parameters is included. If the MCData user of MCData client 1 has selected a functional alias, then the ad hoc group data session request contains that functional alias. + +If the MCData user at MCData client 1 initiates an MCData emergency ad hoc group data communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- the MCData ad hoc group data session request shall contain an emergency indicator; + - if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. +- If the ad hoc group communication is supported, the MCData server verifies whether the user at MCData client 1 is authorized to initiate an ad hoc group data session request. If not authorized, the MCData server rejects the ad hoc group data session request as specified in the step 3. The MCData server accepts the ad hoc group data session request if the ad hoc group data communication is supported and authorized. If authorised, it validates whether the number of invited participants is within the configured limit before proceeding with the data communication setup. + +If functional alias is present, the MCData server checks whether the provided functional alias allowed to be used and has been activated for the user. + +If location information was included in the ad hoc group data session request, the MCData server checks the privacy policy of the MCData user to decide if the location information of MCData client 1 can be provided to other users on the ad hoc group data communication (refer to Annex A.3 "Authorisation to provide location information to other MCData users on a data communication when talking"). + +If an emergency indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress emergency state until this ad hoc group data communication is terminated; and + +If an imminent peril indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group data communication is terminated. + +If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCData server forms the ad hoc group by using received information, and determines the preconfigured group to be used for the configuration of the ad hoc group. The MCData server assigns a MCData group ID for the newly formed ad hoc group. + +The MCData server considers the ad hoc group data communication participants as implicitly affiliated to the ad hoc group. + +3. The MCData server shall send the ad hoc group data session request return message to MCData client 1 containing the below: + - i. The MCData ad hoc group ID, either generated by the MCData server, if not included in the ad hoc group call request of step 1, or if the provided MCData ad hoc group ID is not accepted by the MCData server; or provided by the MCData client 1 if the ad hoc group ID is from an ad hoc group emergency alert; + - ii. The group ID of the pre-configured group to be used for the ad hoc group communication (only included when the ad hoc group data session is authorized); and + - iii. Result of whether the ad hoc group data session request is authorized or not + +If the ad hoc group data session request is not authorized, the MCData server and MCData client 1 shall not proceed with the rest of the steps. + +- 4a-4c. The MCData server sends the ad hoc group data session requests towards the MCData clients of the invited users based on step 1. While sending the ad hoc group data session requests, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list of the users who are required to acknowledge) + - 5a-5c. The receiving MCData clients notify their corresponding MCData user about the incoming ad hoc group data session request with the information of the MCData group ID for the ad hoc group. + - 6a-6c. The receiving MCData clients may accept or reject the ad hoc group data session requests and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server. +7. The MCData server sends the ad hoc group data session response to MCData client 1 through the signalling path to inform about successful data communication establishment. + +NOTE 2: Steps 5 to step 7 can start to occur before all of step 4 is completed since the MCData server do not require to wait for the previous ad hoc group data session request to complete before sending the ad hoc group data session request to another participant. + +8. If the initiating MCData user requires the acknowledgement from the invited MCData users, and the required MCData users do not acknowledge the data session setup within a configured time (the "acknowledged data communication setup timeout"), then the MCData server may proceed with or abandon the data session and then notify the initiating MCData user that the acknowledgements did not include all required members according to ad hoc group data communication policy from the user profile configuration. The MCData server may notify the initiating MCData user of all MCData users who did not acknowledge the ad hoc group data session request within the configured time. This notification may be sent to the initiating MCData user by the MCData server + +more than once during the data communication when MCData users join or leave the MCData ad hoc group data communication. + +- MCData client 1, MCData client 2, MCData client 3 and MCData client 4 establish media plane for data communication. + +NOTE 3: Step 9 can occur any time following step 7 if the conditions to proceed with the data communication are met. + +##### 7.17.3.1.2 Release ad hoc group data communication + +The procedure focuses on the case where the MCData server releases an ongoing MCData ad hoc group data communication for all the participants of that ad hoc group data communication, since at least one of the release conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving. + +Figure 7.17.3.1.2-1 below illustrates the signalling control plane procedure for the MCData server initiating termination of an ongoing ad hoc group data communication. + +![Sequence diagram illustrating the release of an ad hoc group data communication. The diagram shows the interaction between a Home MCPTT provider, MCData client 1, MCData server, MCData client 2, and MCData client 3. The process starts with an ongoing ad hoc group data communication between clients 1, 2, and 3. The server initiates the release, determining participants and generating a release request. It then sends release requests to each client, who notify their users and respond. Finally, the server releases the media plane resources.](b4a7906eddfd40aaa750e19e56c94a8b_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + Note over MCData client 1, MCData client 3: Home MCPTT provider + + Note right of MCData client 1: 1. Ad hoc Group data communication ongoing between MCData client 1, client 2 and client 3 + Note right of MCData server: 2. Release Ad hoc group data communication + Note right of MCData server: 3. Determine Ad hoc group data communication participants and generate Ad hoc group call release + + MCData server->>MCData client 1: 4a. Ad hoc Group data session release request + Note right of MCData client 1: 5a. Notify user + MCData server->>MCData client 2: 4b. Ad hoc Group data session release request + MCData server->>MCData client 3: 4c. Ad hoc Group data session release request + Note right of MCData client 2: 5b. Notify user + Note right of MCData client 3: 5c. Notify user + MCData client 1->>MCData server: 6a. Ad hoc Group data session release response + MCData client 2->>MCData server: 6b. Ad hoc Group data session release response + MCData client 3->>MCData server: 6c. Ad hoc Group data session release response + Note right of MCData server: 7. Releasing the media plane resources associated with the Ad hoc group data communication + +``` + +Sequence diagram illustrating the release of an ad hoc group data communication. The diagram shows the interaction between a Home MCPTT provider, MCData client 1, MCData server, MCData client 2, and MCData client 3. The process starts with an ongoing ad hoc group data communication between clients 1, 2, and 3. The server initiates the release, determining participants and generating a release request. It then sends release requests to each client, who notify their users and respond. Finally, the server releases the media plane resources. + +**Figure 7.17.3.1.2-1: Release ad hoc group data communication** + +- It is assumed that MCData users on MCData client 1, client 2 and client 3 are already part of the ongoing ad hoc group data communication. +- MCData server would like to release the MCData ad hoc group data communication which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving. + +3. MCData server identifies the participants of the ongoing ad hoc group data communication and generates ad hoc group data session release request to release ongoing data communication. The MCData server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group data communication is an emergency or imminent peril data communication respectively. +4. MCData server sends ad hoc group data session release request via SIP core towards each participant of the ongoing ad hoc group data communication. +5. MCData users are notified about the release of the ad hoc group data communication. +6. MCData client(s) receiving ad hoc group data session release request, acknowledge towards the MCData server by sending an ad hoc group data session release response. + +NOTE: If the initiator of the ad hoc group data communication does not supply the participants list, the MCData client(s) may choose to store the list of participants for easy re-initiation of another ad hoc group data communication with the same participants. + +7. MCData client 1, client 2 and client 3 have successfully released the media plane resources associated with the ad hoc group data communication that is terminated and the ad hoc group ceases to exist (i.e., further data communication is not possible over the same ad hoc group), otherwise if the ad hoc group data communication follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further data communication is possible over the same ad hoc group). + +##### 7.17.3.1.3 Ad hoc group data communication setup with MCData server determining the participants lists + +Figure 7.17.3.1.3-1 below illustrates the ad hoc group data communication setup procedure initiated by the MCData user and MCData client 1 wherein the list of participants is determined by the MCData server based on the criteria received from the MCData client. + +Pre-conditions: + +1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication. +2. The MCData user at MCData client 1 wants to invite MCData users who are satisfying certain criteria for the ad hoc group data communication. + +![Sequence diagram for ad hoc group data communication participants determined by MCData server. Lifelines: MCData Client 1, MCData server, MCData client 2, MCData client 3. The process involves a request from Client 1, server authorization, participant determination, and subsequent notifications and responses from the server to the clients, followed by media plane establishment.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +``` + +sequenceDiagram + participant MCData Client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + + Note right of MCData server: 2.Authorize the request + Note right of MCData server: 4. Determine the list of participants to be invited for the data communication based on the rule-set specified in step 1 + + MCData Client 1->>MCData server: 1.Ad hoc group data session request + MCData server-->>MCData Client 1: 3.Ad hoc group data session request return + MCData server->>MCData client 2: 5a.Ad hoc Group data session request + Note right of MCData client 2: 6a. Notify adhoc group data participant + MCData client 2->>MCData client 3: 5b.Ad hoc Group data session request + Note right of MCData client 3: 6b. Notify adhoc group data session + MCData client 2->>MCData server: 7a.Ad hoc Group data session response + MCData client 3->>MCData server: 7b.Ad hoc Group data session response + MCData server-->>MCData Client 1: 8.Ad hoc Group data session response + MCData server-->>MCData Client 1: 9. Ad hoc group data session notify + Note bottom of all lifelines: 10. Media Plane establishment + +``` + +Sequence diagram for ad hoc group data communication participants determined by MCData server. Lifelines: MCData Client 1, MCData server, MCData client 2, MCData client 3. The process involves a request from Client 1, server authorization, participant determination, and subsequent notifications and responses from the server to the clients, followed by media plane establishment. + +**Figure 7.17.3.1.3-1: Ad hoc group data communication participants determined by MCData server** + +- User at MCData client 1 would like to initiate an ad hoc group data communication in-order to invite the participants satisfying specific criteria. The MCData client 1 initiates the ad hoc group data communication by sending the ad hoc group data session request containing the details of the criteria to be applied by the MCData server for determining the participants list. If end-to-end encryption is supported, the Encryption supported information element shall be set to true and pre-configured MCData group whose configuration is to be applied is included. An SDP offer containing the MCData client media parameters is included. If the MCData user of MCData client 1 has selected a functional alias, then the ad hoc group data session request contains that functional alias. + +If the MCData user at MCData client 1 initiates an MCData emergency ad hoc group data communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- the MCData ad hoc group data session request shall contain an emergency indicator; +- if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1. + +2. If the ad hoc group data communication is supported, the MCData server verifies whether the user at MCData client 1 is authorized to initiate an ad hoc group data communication. If not authorized, the MCData server rejects the ad hoc group data session request as specified in the step 3. The MCData server accepts the ad hoc group data session request if the ad hoc group data communication is supported and authorized. + +If functional alias is present, the MCData server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +If location information was included in the ad hoc group data session request, the MCData server checks the privacy policy of the MCData user to decide if the location information of MCData client 1 can be provided to other users on the data communication (refer to Annex A.3 "Authorisation to provide location information to other MCData users on a data communication when talking"). + +If an emergency indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress emergency state until this ad hoc group data communication is terminated; + +If an imminent peril indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group data communication is terminated. and + +If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCData server forms the ad hoc group by using received information, and determines the preconfigured group to be used for the configuration of the ad hoc group. The MCData server assigns a MCData group ID for the newly formed ad hoc group. Further, the ad hoc group participants are included to ad hoc group once determined as specified in the step 4. + +3. The MCData server shall send the ad hoc group data session request return message to MCData client 1 containing the below: + - i. The MCData ad hoc group ID, either generated by the MCData server, if not included in the ad hoc group call request of step 1, or if the provided MCData ad hoc group ID is not accepted by the MCData server, or provided by the MCData client 1 if the ad hoc group ID is from an ad hoc group emergency alert; + - ii. The group ID of the pre-configured group to be used for the ad hoc group communication (only included when the ad hoc group data session is authorized); and + - iii. Result of whether the ad hoc group data session request is authorized or not + +If the ad hoc group data session request is not authorized, the MCData server and MCData client 1 shall not proceed with the rest of the steps. + +4. The MCData server determines the list of participants to be invited for the ad hoc group data communication based on the information present in the information element Criteria for determining the participants. This information element could carry either criteria or indicator identifying pre-defined criteria or a combination of both. + +NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how their MCData server determines the list of participants are left to implementation. + +5. The MCData server sends the ad hoc group data session requests towards the MCData clients 2 and 3. While sending the ad hoc group data session requests, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group data communication if end-to-end encryption is requested. The MCData server considers the ad hoc group data communication participants as implicitly affiliated to the ad hoc group. +6. The receiving MCData clients notify their corresponding MCData user about the incoming ad hoc group data communication. +7. The receiving MCData clients may accept or reject the ad hoc group data session requests and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server. + +8. The MCData server sends the ad hoc group data session response to MCData client 1 through the signalling path to inform about successful data communication establishment. +9. The MCData server may notify the initiating MCData user of all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the MCData ad hoc group data communication. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group data communication, the MCData server provides ad hoc group data session notify about all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication, and when MCData users joins or leaves the MCData ad hoc group data communication. + +NOTE 2: The authorized user can learn who is currently affiliated to the current adhoc group data communication. + +10. MCData client 1, MCData client 2 and MCData client 3 establish media plane resources. + +##### 7.17.3.1.4 Modification of ad hoc group data communication participants by an authorized user + +Figure 7.17.3.1.4-1 below illustrates the modification of ad hoc group data communication participants procedure by an authorized user. + +Pre-conditions: + +1. An MCData ad hoc group data communication is already in progress the participants list is provided by the originating MCData user while initiating the MCData ad hoc group data communication. +2. The participants of the MCData ad hoc group call belong to the single MCData system. +3. The MCData users on MCData client 1, MCData client 3 to MCData client n are on an ongoing ad hoc group data communication. +4. The MCData user at MCData client 1 determines to remove the user of MCData client 3 from the ad hoc group data communication and add user of MCData client 2 into the on-going ad hoc group data communication. + +![Sequence diagram showing the modification of ad hoc group data communication participants by an authorized user. Lifelines: MCData client 1 (Authorized user), MCData server, MCData client 3, MCData client n, MCData client 2. The process involves a request to modify participants, authorization, a leave request to client 3, notification of client 3's user, a leave response, a request to client 2, notification of client 2's user, a response to client 1, notification of client 1's user, and a final notification to all participants.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 (Authorized user) + participant MCData server + participant MCData client 3 + participant MCData client n + participant MCData client 2 + + Note over all: Ad hoc group data ccommunication is established and on-going + + MCData client 1->>MCData server: 1. Modify Ad hoc Group data session participants request + MCData server-->>MCData client 1: 2. Authorize the request + MCData server-->>MCData client 1: 3. Modify Ad hoc Group data session participants response + MCData server->>MCData client 3: 4. Ad hoc Group data session leave request + Note right of MCData client 3: 5. Notify user + MCData client 3-->>MCData server: 6. Ad hoc Group data session leave response + MCData server->>MCData client 2: 7. Ad hoc Group data session request + Note right of MCData client 2: 8. Notify user + MCData client 2-->>MCData server: 9. Ad hoc Group data session response + MCData server-->>MCData client 1: 10. Ad hoc group data session notify + Note over all: 11. Notify participants of the on-going ad hoc group data communication regarding the change in the participants + +``` + +Sequence diagram showing the modification of ad hoc group data communication participants by an authorized user. Lifelines: MCData client 1 (Authorized user), MCData server, MCData client 3, MCData client n, MCData client 2. The process involves a request to modify participants, authorization, a leave request to client 3, notification of client 3's user, a leave response, a request to client 2, notification of client 2's user, a response to client 1, notification of client 1's user, and a final notification to all participants. + +**Figure 7.17.3.1.4-1: Modification of ad hoc group data communication participants by an authorized user** + +1. The MCData user at the MCData client 1 is authorized and requests to modify ad hoc group data communication participants. The MCData client 1 sends the modify ad hoc group data session participants request to the MCData server in order to remove MCData client 3 from the ongoing ad hoc group data communication and add MCData client 2 into it. +2. The MCData server verifies whether the MCData client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group data communication. +3. The MCData server sends modify ad hoc group data session participants response to the MCData client 1. +4. The MCData server sends the ad hoc group data session leave request to the MCData client 3 in order to remove it from the on-going ad hoc group data communication. +5. The MCData client 3 notifies the user of the ad hoc group data session leave request. +6. The MCData client 3 sends the ad hoc group data session leave response to the MCData server. + +7. The MCData server sends the ad hoc group data session request towards MCData client 2. + +NOTE: Steps 7 to 9 can occur at any time following step 3. + +99. The receiving MCData client 2 notifies the user about the incoming ad hoc group data communication. + +9. The MCData client 2 accepts the ad hoc group data session request and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server. The MCData server considers the MCData user as implicitly affiliated to the ad hoc group. +10. The MCData server may notify the initiating MCData user of all the users who are added to the on-going ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the ad hoc group data communication. +11. The MCData server may notify the participants about the change in the participants of on-going ad hoc group data communication. + +##### 7.17.3.1.5 Modification of ad hoc group data communication participants by the MCData server + +Figure 7.17.3.1.5-1 below illustrates the modification of ad hoc group data communication participants procedure by the MCData server. + +Pre-conditions: + +1. The MCData client 1 is the initiator of the ad hoc group data communication. +2. MCData server determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication. +3. MCData server continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication. +4. The MCData server detects that the MCData client 5 satisfies the criteria and MCData client 4 stops to meet the criteria specified by the MCData client 1. + +![Sequence diagram illustrating the modification of ad hoc group data communication participants by the MCData server. The diagram shows the interaction between MCData client 1, MCData server, MCData client 2, MCData client 3, MCData client 4, and MCData client 5. The process involves establishing the group, adding MCData client 5, and removing MCData client 4 based on criteria specified by MCData client 1.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + participant MCData client 4 + participant MCData client 5 + + Note right of MCData client 1: 1. Ad hoc group data communication established based on the criteria specified by MCData client 1 + Note right of MCData server: 2. MCData server detects that MCData client 5 now meets criteria + MCData server->>MCData client 5: 3. Ad hoc group data session request + Note right of MCData client 5: 4. Notify User + MCData client 5->>MCData server: 5. Ad hoc group data session response + Note right of MCData client 1: 6. Ad hoc group data communication changed by adding MCData client 5 based on the criteria specified by MCData client 1 + Note right of MCData server: 7. MCData server detects that MCData client 4 does not meet criteria any more + MCData server->>MCData client 4: 8. Ad hoc group data session leave request + Note right of MCData client 4: 9. Notify User + MCData client 4->>MCData server: 10. Ad hoc group data session leave response + Note right of MCData client 1: 11. Ad hoc group data communication changed by removing MCData client 4 based on the criteria specified by MCData client 1 + +``` + +Sequence diagram illustrating the modification of ad hoc group data communication participants by the MCData server. The diagram shows the interaction between MCData client 1, MCData server, MCData client 2, MCData client 3, MCData client 4, and MCData client 5. The process involves establishing the group, adding MCData client 5, and removing MCData client 4 based on criteria specified by MCData client 1. + +**Figure 7.17.3.1.5-1: Modification of ad hoc group data communication participants by the MCData server** + +1. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, MCData client 3 and MCData client 4. The participants list is determined by the MCData server based on the criteria specified by the MCData client 1 while initiating the data communication. +2. The MCData server detects that the MCData client 5 satisfies the criteria specified by the MCData client. +3. The MCData server sends the ad hoc group data session request to the MCData client 5. +4. The MCData client 5 notifies the user about the incoming ad hoc group data communication. +5. The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server. +6. The on-going ad hoc group data communication is updated by adding MCData client 5 which satisfies the criteria specified by the MCData client 1. +7. The MCData server detects that the MCData client 4 is no more satisfying the criteria to be the participant of the ad hoc group data communication. +8. The MCData server sends the ad hoc group data communication leave request to the MCData client 4 and removes it from the on-going ad hoc group data communication. +9. The MCData client 4 notifies the user of the ad hoc group data session leave request. +10. The MCData client 4 sends the ad hoc group data session leave response to the MCData server. +11. The on-going ad hoc group data communication is updated by removing MCData client 4, which no more satisfies the criteria specified by the MCData client 1. + +#### 7.17.3.2 Ad hoc group data communication involving multiple MC systems + +##### 7.17.3.2.1 Procedure for ad hoc group data communication setup – Participants list provided by the Initiator + +Figure 7.17.3.2.1-1 illustrates the procedure for ad hoc group data communication setup procedure initiated by an authorized user wherein either a list of participants or an ad hoc group ID from an ad hoc group emergency alert is provided by the authorised user and the determined MCData users are from multiple MCData systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system shares their users' information to the primary MC system. +2. The authorized MCData user/dispatcher belongs to the primary MC system. +3. The MCData server of the primary MC system is where the authorized MCData user/dispatcher creates the ad hoc group. +4. Some users of the ad hoc group belong to partner MC systems. +5. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication. +6. If an ad hoc group ID from an ad hoc group emergency alert is used to invite the ad hoc group members, MCData client is aware of the ad hoc group ID. + +![Sequence diagram illustrating the ad hoc group data communication setup procedure. The diagram shows interactions between an MCData client (Authorized MCData user), MCData server (Primary), MCData client 1..N (Primary), MCData server (Partner), and MCData client 1..N (Partner). The steps are: 1. Ad hoc group data session request from client to primary server; 2. Authorization check and ad hoc group formation by primary server; 3. Ad hoc group data session request return from primary server to client; 4. Ad hoc group data session request from primary server to partner server; 5a. Notify ad hoc group data communication from partner server to primary client; 5b. Ad hoc group data session response from primary client to primary server; 6. Ad hoc group data session request from primary server to partner client; 7a. Notify ad hoc group data communication from partner client to partner server; 7b. Ad hoc group data session response from partner server to primary server; 8. Ad hoc group data session response from primary server to client; 9. Media plane establishment for data transmission involving all components.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` + +sequenceDiagram + participant Client as MCData client (Authorized MCData user) + participant ServerP as MCData server (Primary) + participant ClientP as MCData client 1..N (Primary) + participant ServerR as MCData server (Partner) + participant ClientR as MCData client 1..N (Partner) + + Client->>ServerP: 1. Ad hoc group data session request + ServerP->>ServerP: 2. Authorization check and ad hoc group formation + ServerP->>Client: 3. Ad hoc group data session request return + ServerP->>ServerR: 4. Ad hoc group data session request + ServerR->>ClientP: 5a. Notify ad hoc group data communication + ClientP->>ServerP: 5b. Ad hoc group data session response + ServerP->>ClientR: 6. Ad hoc group data session request + ClientR->>ServerR: 7a. Notify ad hoc group data communication + ServerR->>ServerP: 7b. Ad hoc group data session response + ServerP->>Client: 8. Ad hoc group data session response + Note over Client, ServerP, ClientP, ServerR, ClientR: 9. Media plane establishment for data transmission + +``` + +Sequence diagram illustrating the ad hoc group data communication setup procedure. The diagram shows interactions between an MCData client (Authorized MCData user), MCData server (Primary), MCData client 1..N (Primary), MCData server (Partner), and MCData client 1..N (Partner). The steps are: 1. Ad hoc group data session request from client to primary server; 2. Authorization check and ad hoc group formation by primary server; 3. Ad hoc group data session request return from primary server to client; 4. Ad hoc group data session request from primary server to partner server; 5a. Notify ad hoc group data communication from partner server to primary client; 5b. Ad hoc group data session response from primary client to primary server; 6. Ad hoc group data session request from primary server to partner client; 7a. Notify ad hoc group data communication from partner client to partner server; 7b. Ad hoc group data session response from partner server to primary server; 8. Ad hoc group data session response from primary server to client; 9. Media plane establishment for data transmission involving all components. + +**Figure 7.17.3.2.1-1: Ad hoc group data communication setup** + +1. The MCData client of the authorized user initiates an ad hoc group data communication with multiple users from primary and partner MC systems. An ad hoc group data session request message with the information of the participants MCData IDs or an ad hoc group ID if the ad hoc group call follows an ad hoc group emergency alert is routed to the MCData server of the primary MC system. +2. If the ad hoc group call is supported, the MCData server of the primary MC system verifies whether the user at MCData client is authorized to initiate an ad hoc group communication. If not authorized, the MCData server of the primary MC system rejects the ad hoc group data session request as specified in the step 3. + +If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCData server of the primary MC system forms the ad hoc group by using information + +received in step 1 and further determines the preconfigured group to be used for the configuration (e.g. security related information). The MCData server assigns an MCData ad hoc group ID for the newly formed ad hoc group. + +If no MCData ad hoc group ID was included in the ad hoc group data session request of step 1, or if the provided MCData ad hoc group ID is not accepted by the MCData server, the MCData server assigns a MCData group ID for the newly formed ad hoc group. The MCData server considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group. + +NOTE 1: The newly formed ad hoc group information including the MCData group ID and the list of users is held in dynamic data in the MCData server. + +3. The MCData server shall send the ad hoc group data session request return message to MCData client containing the below: + +- i. The MCData ad hoc group ID either generated by the MCData server or provided by the MCData client if the ad hoc group ID is from an ad hoc group emergency alert (only included when the ad hoc group data session request is authorized); +- ii. The group ID of the pre-configured group to be used for the ad hoc group data communication (only included when the ad hoc group data session request is authorized); and +- iii. Result of whether the ad hoc group data session request is authorized or not. + +If the ad hoc group data session request is not authorized, MCData client 1 shall not proceed with the rest of the steps. + +4. The MCData server of the primary MC system sends the ad hoc group data session request to the group members of the ad hoc group belonging to the primary MC system. While sending the ad hoc group data session requests, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list of the users who are required to acknowledge). + +5a-5b. The MCData clients receive in the ad hoc group data session request with the information of the MCData group ID for the ad hoc group and further notify their corresponding MCData user. The group members of the ad hoc group of the primary MC system may accept or reject the ad hoc group data session requests and respond with the ad hoc group data session responses. + +6. The primary MCData server further initiates an ad hoc group data session request message to the MCData users of the partner MC system. The ad hoc group data session request message is routed to the MCData users via the MCData server of the partner MC system. + +7a-7b. The MCData clients receive in the ad hoc group data session request the information of the MCData group ID for the ad hoc group and further notify their corresponding MCData user. The MCData users upon receipt of the invitation may accept or reject the ad hoc group data session requests, and respond with the ad hoc group data session responses. The ad hoc group data session response message is routed to the MCData server of the primary MC system via the MCData server of the partner MC system. + +8. The MCData server of the primary MC system provides an ad hoc group data session response message to the MCData client of the authorized MCData user upon receiving response to the corresponding ad hoc group data session request in step 1. The ad hoc group data session response will consist of the success or failure result and/or detailed reason information in case of failure. + +NOTE 2: The ad hoc group data session response messages may be used by The MCData client of the authorized user to determine if the ad hoc group communication will proceed. + +9. Upon successful ad hoc group data session setup, a group data communication is established amongst the group members from primary and partner MC systems. The media plane resources for data communication are established. + +##### 7.17.3.2.2 Procedure for ad hoc group data communication release by MCData server – Participants list provided by the Initiator + +This procedure focuses on the case where an MCData server initiates the termination of an ongoing MCData ad hoc group data communication for all the participants of that group data communication, since at least one of the + +termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCData group members are not present. + +Procedures in figure 7.17.3.2.2-1 are the signalling control plane procedures for the MCData server initiating termination of an ongoing MCData ad hoc group data communication. + +Pre-condition: + +- The MCData client 1 and MCData client 2 belong to primary MC system. The MCData client 3 belongs to partner MC system. +- The MCData users on MCData client 1, client 2 and client 3 are already part of the ongoing ad hoc group data communication (e.g. as a result of ad hoc group data communication setup as specified in clause 7.17.3.2.1). + +![Sequence diagram for Ad hoc group data communication release. Lifelines: MCData Client 1, MCData Server (Primary), MCData Client 2 (Primary), MCData Server (Partner), MCData Client 3 (Partner). The process involves the Primary Server determining to release the communication, identifying participants, sending release requests to clients and the Partner Server, notifying users, receiving responses, and finally releasing media plane resources.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` + +sequenceDiagram + participant MCData Client 1 + participant MCData Server (Primary) + participant MCData Client 2 (Primary) + participant MCData Server (Partner) + participant MCData Client 3 (Partner) + + Note right of MCData Server (Primary): 1. Release Ad hoc group data communication + Note right of MCData Server (Primary): 2. Identifies participants of ongoing group data communication and generate Adhoc group data communication release request + MCData Server (Primary)->>MCData Client 1: 3. Ad hoc group data session release request + MCData Server (Primary)->>MCData Client 2: 3. Ad hoc group data session release request + MCData Server (Primary)->>MCData Server (Partner): 3. Ad hoc group data session release request + MCData Server (Partner)->>MCData Client 3: 3. Ad hoc group data session release request + Note left of MCData Client 1: 4. Notify user + Note left of MCData Client 2: 4. Notify user + Note left of MCData Client 3: 4. Notify user + MCData Client 1->>MCData Server (Primary): 5. Ad hoc group data session release response + MCData Client 2->>MCData Server (Primary): 5. Ad hoc group data session release response + MCData Client 3->>MCData Server (Partner): 5. Ad hoc group data session release response + MCData Server (Partner)->>MCData Server (Primary): 5. Ad hoc group data session release response + Note right of MCData Server (Primary): 6. Releasing media plane resources associated with the group data communication and remove the related ad hoc group information + +``` + +Sequence diagram for Ad hoc group data communication release. Lifelines: MCData Client 1, MCData Server (Primary), MCData Client 2 (Primary), MCData Server (Partner), MCData Client 3 (Partner). The process involves the Primary Server determining to release the communication, identifying participants, sending release requests to clients and the Partner Server, notifying users, receiving responses, and finally releasing media plane resources. + +**Figure 7.17.3.2.2-1: Ad hoc group data communication release** + +1. The MCData server determines to release the ongoing ad hoc group data communication e.g., due to a hang timer expiry, last participant leaving, second last participant leaving, initiator leaving, or a minimum number of affiliated MCData group members not present. +2. The MCData server identifies the participants of the ongoing ad hoc group data communication and generates ad hoc group data session release request to release ongoing data communication. +3. The MCData server sends an ad hoc group data session release request to each participant of the ongoing group data communication. If the participants belong to the partner MC system, then the ad hoc group data session release request is routed to the MCData clients of the partner MC system via the partner MCData server. +4. The MCData users are notified about the release of the ad hoc group data communication. +5. The MCData client(s), send an acknowledgment to the MCData server by sending an ad hoc group data session release response. + +6. The MCData client 1, client 2 and client 3 have successfully released media plane resources associated with the ad hoc group data communication that is terminated. The primary MCData server removes the ad hoc group information from the dynamic data and thus the ad hoc group ceases to exist. + +##### 7.17.3.2.3 Ad hoc group data communication setup – Participants list determined by the MCData server + +Figure 7.17.3.2.3-1 below illustrates the ad hoc group data communication setup procedure initiated by an authorized user wherein the list of participants is determined by the MCData server based on the criteria received from the MCData client and determined MCData users are from multiple MCData systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system share their users' information to the primary MC system. +2. The authorized MCData user/dispatcher belongs to the primary MC system. +3. The MCData server 1 of the primary MC system is where the authorized MCData user/dispatcher creates the ad hoc group. +4. Some users of the ad hoc group may belong to MCData server 2 of the partner MC systems. +5. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCData client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication. + +![Sequence diagram showing ad hoc group data communication setup involving multiple MCData systems. The diagram is divided into two main groups: 'primary MC system' and 'partner MC system'. Lifelines include MCData client 1, MCData server 1 (primary), MCData client 2, MCData server 2 (partner), MCData client 3, and MCData client 4. The sequence starts with MCData client 1 sending an 'Ad hoc group data session request' to MCData server 1. MCData server 1 responds with '2. Authorise' and '3. Ad hoc group data session request return'. MCData server 1 then performs internal steps '4. Determine the list of participants...' and '7. Compile the list of participants...'. It sends '5. Ad hoc group data session get userlist' to MCData server 2, which responds with '6. Ad hoc group data session get userlist response'. MCData server 1 then sends '8a. Ad hoc group data session request' to MCData client 3 and '8b. Ad hoc group data session request' to MCData client 4. MCData client 3 and 4 send '10a.Notify user', '10b.Notify user', and '10c.Notify user' respectively. MCData client 1, 2, 3, and 4 send '11. Ad hoc group data session response', '12. Ad hoc group data session response', '13. Ad hoc group data session response', and '14. Ad hoc group data session response' respectively. MCData server 1 sends '15. Ad hoc group data session notify' to MCData client 1. Finally, a '16. Media plane establishment for data communication' bar spans across all lifelines.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Sequence diagram showing ad hoc group data communication setup involving multiple MCData systems. The diagram is divided into two main groups: 'primary MC system' and 'partner MC system'. Lifelines include MCData client 1, MCData server 1 (primary), MCData client 2, MCData server 2 (partner), MCData client 3, and MCData client 4. The sequence starts with MCData client 1 sending an 'Ad hoc group data session request' to MCData server 1. MCData server 1 responds with '2. Authorise' and '3. Ad hoc group data session request return'. MCData server 1 then performs internal steps '4. Determine the list of participants...' and '7. Compile the list of participants...'. It sends '5. Ad hoc group data session get userlist' to MCData server 2, which responds with '6. Ad hoc group data session get userlist response'. MCData server 1 then sends '8a. Ad hoc group data session request' to MCData client 3 and '8b. Ad hoc group data session request' to MCData client 4. MCData client 3 and 4 send '10a.Notify user', '10b.Notify user', and '10c.Notify user' respectively. MCData client 1, 2, 3, and 4 send '11. Ad hoc group data session response', '12. Ad hoc group data session response', '13. Ad hoc group data session response', and '14. Ad hoc group data session response' respectively. MCData server 1 sends '15. Ad hoc group data session notify' to MCData client 1. Finally, a '16. Media plane establishment for data communication' bar spans across all lifelines. + +**Figure 7.17.3.2.3-1: Ad hoc group data communication setup involving multiple MCData systems** + +1-3. Same as described in subclause 7.17.3.1.1. + +4. The MCData server 1 determines the list of participants from the primary MC system and determines the partner MC system to be involved in the ad hoc group data communication based on the information present in the information element Criteria for determining the participants. This information element carries the criteria, indicator identifying pre-defined criteria, or a combination of both. + +NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how their MCData server determines the list of participants are left to implementation. + +5. The MCData server 1 needs to involve the partner MC system based on the agreement and based on the criteria for determining the participants list, it sends the ad hoc group data session get userlist request to the MCData server 2. This request carries the criteria specified in the step 1. + +6. MCData server 2 evaluates the criteria and determines the participants satisfying the criteria (i.e. MCData client 3 and MCData client 4) and sends the response containing the list of MCData users satisfying the criteria. The MCData server 2 may apply local policies if any while determining the participants satisfying the criteria. + +7. The MCData server 1 compiles the list of participants to be invited for the ad hoc group data communication including the participants from both primary and partner MC system. + +8a-8b. The MCData server 1 sends the ad hoc group data session request towards the MCData client 3 and MCData client 4. While sending the ad hoc group data session request, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group data communication if end-to- + +end encryption is requested. The MCData server 1 considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group. + +9. The MCData server 1 sends the ad hoc group data session request towards the MCData client 2. While sending the ad hoc group data session request, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group data communication if end-to-end encryption is requested. + +10a-10c. The MCData clients receive incoming ad hoc group data communication and further notify their corresponding MCData users. + +11. The MCData client 2 accepts the ad hoc group data session request, and sends ad hoc group data session response to the MCData server 1. + +12. The MCData client 3 accepts the ad hoc group data session request, and sends ad hoc group data session response to the MCData server 1. + +13. The MCData client 4 accepts the ad hoc group data session request, and sends ad hoc group data session response to the MCData server 1. + +14. The MCData server 1 sends the ad hoc group data session response to MCData client 1 through the signalling path to inform about result of the participants responses. + +15. The MCData server 1 may notify the initiating MCData user of all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication. The MCData server 1 more than once during the data communication may send this notification to the initiating MCData user whenever an MCData user joins or leaves the MCData ad hoc group data communication. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group data communication, the MCData server provides ad hoc group data session notify about all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication, and when MCData users joins or leaves the MCData ad hoc group data communication. + +16. The MCData client 1, MCData client 2, MCData client 3 and MCData client 4 establish media plane resources for data communication. + +NOTE 2: The ad hoc group data session request and response exchanged between MCData server 1 of primary MC system and MCData client 3/MCData client 4 will always traversal through the MCData server 2. + +##### 7.17.3.2.4 Modifying of ad hoc group data communication participants by the MCData server + +Figure 7.17.3.2.4-1 below illustrates the MCData server modifying the ad hoc group data communication participants procedure involving multiple MCData systems. + +Pre-conditions: + +1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication. +2. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication. +3. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, and MCData client 4. The participants list is determined by both primary and partner MC systems. +4. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication. +5. The MCData server 1 of the primary MCData system detects that the MCData client 3 meets the criteria and MCData client 2 stops to meet the criteria specified by the MCData client 1. +6. The MCData server 2 of the partner MCData system detects that the MCData client 5 meets the criteria and MCData client 4 stops to meet the criteria specified by the MCData client 1. + +![Sequence diagram showing the modification of ad hoc group data communication participants by the MCData server. The diagram is split into two lifelines: 'primary MC system' and 'partner MC system'. The primary MC system contains MCData client 3, MCData server 1 (primary), MCData client 1, and MCData client 2. The partner MC system contains MCData server 2 (partner), MCData client 4, and MCData client 5. The sequence of events is: 1. MCData server 1 detects MCData client 3 meets criteria and adds it. 2. MCData server 1 detects MCData client 2 does not meet criteria and removes it. 3. MCData server 2 detects MCData client 5 meets criteria. 4. MCData server 2 sends an 'Ad hoc group data session add MCData user notification' to MCData server 1. 5. MCData server 1 sends an 'Ad hoc group data session request' to MCData client 5. 6. MCData client 5 sends a 'Notify User' message (dashed box). 7. MCData client 5 sends an 'Ad hoc group data session response' to MCData server 1. 8. MCData server 1 detects the change and updates the group. 9. MCData server 2 detects MCData client 4 does not meet criteria. 10. MCData server 2 sends an 'Ad hoc group data session remove MCData user notification' to MCData server 1. 11. MCData server 1 sends an 'Ad hoc group data session leave request' to MCData client 4. 12. MCData client 4 sends a 'Notify User' message (dashed box). 13. MCData client 4 sends an 'Ad hoc group data session leave response' to MCData server 1. 14. MCData server 1 detects the change and updates the group.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Sequence diagram showing the modification of ad hoc group data communication participants by the MCData server. The diagram is split into two lifelines: 'primary MC system' and 'partner MC system'. The primary MC system contains MCData client 3, MCData server 1 (primary), MCData client 1, and MCData client 2. The partner MC system contains MCData server 2 (partner), MCData client 4, and MCData client 5. The sequence of events is: 1. MCData server 1 detects MCData client 3 meets criteria and adds it. 2. MCData server 1 detects MCData client 2 does not meet criteria and removes it. 3. MCData server 2 detects MCData client 5 meets criteria. 4. MCData server 2 sends an 'Ad hoc group data session add MCData user notification' to MCData server 1. 5. MCData server 1 sends an 'Ad hoc group data session request' to MCData client 5. 6. MCData client 5 sends a 'Notify User' message (dashed box). 7. MCData client 5 sends an 'Ad hoc group data session response' to MCData server 1. 8. MCData server 1 detects the change and updates the group. 9. MCData server 2 detects MCData client 4 does not meet criteria. 10. MCData server 2 sends an 'Ad hoc group data session remove MCData user notification' to MCData server 1. 11. MCData server 1 sends an 'Ad hoc group data session leave request' to MCData client 4. 12. MCData client 4 sends a 'Notify User' message (dashed box). 13. MCData client 4 sends an 'Ad hoc group data session leave response' to MCData server 1. 14. MCData server 1 detects the change and updates the group. + +**Figure 7.17.3.2.4-1: Modification of ad hoc group data communication participants by the MCData server** + +1. The MCData server 1 detects that MCData client 3 now meets criteria and successfully added to group data communication. +2. The MCData server 1 detects that MCData client 2 does not meet criteria any more and successfully removed from a group data communication. +3. The MCData server 2 detects that the MCData client 5 meets the criteria specified by the MCData client 1. +4. The MCData server 2 sends the notification to MCData server 1 of the primary MCData system to add the MCData user at MCData client 5 to on-going ad hoc group data communication. +5. The MCData server 1 sends the ad hoc group data session request to the MCData client 5. +6. The MCData client 5 notifies the user about the incoming ad hoc group data communication. +7. The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server 1. + +8. The on-going ad hoc group data communication is updated by adding MCData client 5 which meets the criteria specified by the MCData client 1. +9. The MCData server 2 detects that the MCData client 4 is no longer satisfying the criteria to be the participant of the ad hoc group data communication. +10. The MCData server 2 sends the notification to MCData server 1 of the primary MCData system to remove the MCData user at MCData client 4 from on-going ad hoc group data communication. +11. The MCData server 1 sends the ad hoc group data session leave request to the MCData client 4 and removes it from the on-going ad hoc group data communication. +12. The MCData client 4 notifies the user of the ad hoc group data session leave request. +13. The MCData client 4 sends the ad hoc group data session leave response to the MCData server 1. +14. The on-going ad hoc group data communication is updated by removing MCData client 4, which no longer meets the criteria specified by the MCData client 1. + +NOTE: The ad hoc group data session request and response exchanged between MCData server 1 of primary MC system and MCData client 4/MCData client 5 will always traversal through the MCData server 2. + +##### 7.17.3.2.5 Release ad hoc group data communication and stop determining the ad hoc group data communication participants by partner MCData system – Participants list determined by the MCData server + +Figure 7.17.3.2.5-1 below illustrates the release of ad hoc group data communication and stopping of MCData server at the partner MC system from determining the ad hoc group data communication participants' procedure once involving multiple MCData systems. This procedure, in particular describes about how the partner MC system is notified about ad hoc group data communication release to cease the determining of the participants by the partner MC system. + +Pre-conditions: + +1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication. +2. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, MCData client 3, and MCData client 4. +3. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication. +4. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication. + +![Sequence diagram illustrating the release of an ad hoc group data communication across multiple MCData systems. The diagram shows interactions between a primary MC system (MCData client 1, MCData server 1 (primary), MCData client 2) and a partner MC system (MCData server 2 (partner), MCData client 3, MCData client 4). The process involves a release notification from the primary server to the partner server, followed by release requests from the primary server to all clients, user notifications, and release responses from all clients back to the primary server.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server 1 (primary) + participant MCData client 2 + participant MCData server 2 (partner) + participant MCData client 3 + participant MCData client 4 + + Note left of MCData server 1: 1. Release Ad hoc group data communication + MCData server 1->>MCData server 2: 2. Ad hoc group data session release notification + MCData server 1->>MCData client 2: 3a. Ad hoc group data session release request + MCData server 1->>MCData client 1: 3b. Ad hoc group data session release request + MCData server 1->>MCData client 3: 3c. Ad hoc group data session release request + MCData server 1->>MCData client 4: 3d. Ad hoc group data session release request + Note left of MCData client 1: 4b.Notify User + Note left of MCData client 2: 4a.Notify User + Note left of MCData client 3: 4c.Notify User + Note left of MCData client 4: 4d.Notify User + MCData client 1->>MCData server 1: 5a. Ad hoc group data session release response + MCData client 2->>MCData server 1: 5b. Ad hoc group data session release response + MCData client 3->>MCData server 1: 5c. Ad hoc group data session release response + MCData client 4->>MCData server 1: 5d. Ad hoc group data session release response + +``` + +Sequence diagram illustrating the release of an ad hoc group data communication across multiple MCData systems. The diagram shows interactions between a primary MC system (MCData client 1, MCData server 1 (primary), MCData client 2) and a partner MC system (MCData server 2 (partner), MCData client 3, MCData client 4). The process involves a release notification from the primary server to the partner server, followed by release requests from the primary server to all clients, user notifications, and release responses from all clients back to the primary server. + +**Figure 7.17.3.2.5-1: MCData server releases an ad hoc group data communication and stops the determination of ad hoc group data communication participants involving multiple MCData systems** + +1. The MCData server 1 detects that the ad hoc group data communication which is ongoing is to be released e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCData group members are not present. + 2. The MCData server 1 sends the ad hoc group data session release notification to MCData server 2 of the partner MCData system about the ad hoc group data communication release to stop determining the participants list by MCData server 2 of the partner MCData system. + - 3a-3d. The MCData server 1 sends ad hoc group data session release request to all the participants of the ad hoc group data communication. + - 4a-4d. The MCData clients notifies the user about the release of the ad hoc group data communication. + - 5a-5d. All the participants of the ad hoc group data communication receives the ad hoc group data session release request and sends the ad hoc group data session release response to the MCData server 1 of the primary MCData server. +- NOTE: The ad hoc group data session request and response exchanged between MCData server 1 of primary MC system and MCData client 3/MCData client 4 will always traversal through the MCData server 2. + +##### 7.17.3.2.6 Modification of ad hoc group data communication participants by an authorized user + +Figure 7.17.3.2.6-1 below illustrates the MCData user modifying the ad hoc group data communication participants procedure involving multiple MCData systems. + +Pre-conditions: + +1. An MCData ad hoc group data communication is already in progress and the participants list provided by the originating MCData user while initiating the MCData ad hoc group data communication. +2. The participants of the MCData ad hoc group data communication belongs to the multiple MCData system. +3. The MCData user at MCData client 1 determines that the MCData client 3 needs to be invited to on-going ad hoc group data communication and MCData client 2 needs to be removed from the on-going ad hoc group data communication from the primary MCData system. +4. The MCData user at MCData client 1 determines that the MCData client 5 needs to be invited to on-going ad hoc group data communication and MCData client 4 needs to be removed from the on-going ad hoc group data communication from the partner MCData system. + +![Sequence diagram showing the modification of ad hoc group data communication participants. The diagram is split into two systems: 'primary MC system' and 'partner MC system'. Lifelines include MCData client 3, MCData server 1 (primary), MCData client 1, MCData client 2, MCData server 2 (partner), MCData client 4, and MCData client 5. The sequence starts with an established ad hoc group data communication. MCData client 1 sends a 'Modify ad hoc group data session participants request' to MCData server 1. MCData server 1 responds with 'Authorize the request' and then 'Modify ad hoc group data session participants response'. MCData client 1 then sends requests to add MCData client 3 and 5, and remove MCData client 2 and 4. MCData server 1 sends an 'Ad hoc group data session request' to MCData client 5, which receives a response and notifies the user. MCData server 1 then sends a notification to MCData client 1 about the changes. MCData client 1 sends a 'Ad hoc group data session leave request' to MCData server 2, which receives a response and notifies the user. MCData server 2 then sends a notification to MCData client 1 about the changes. Finally, MCData client 1 sends an 'Ad hoc group data session notify' to MCData client 3, and a dashed box indicates that all participants are notified about the changes.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +``` + +sequenceDiagram + participant MCData client 3 + participant MCData server 1 (primary) + participant MCData client 1 + participant MCData client 2 + participant MCData server 2 (partner) + participant MCData client 4 + participant MCData client 5 + + Note over MCData server 1, MCData client 2: Ad hoc group data communication established based on the participants list specified by the initiator of the communication + + MCData client 1->>MCData server 1: 1. Modify ad hoc group data session participants request + MCData server 1-->>MCData client 1: 2. Authorize the request + MCData server 1-->>MCData client 1: 3. Modify ad hoc group data session participants response + + MCData client 1->>MCData server 1: 4. MCData client 1 requested that MCData client 3 to be invited for the ongoing data communication and successfully added to data communication + MCData client 1->>MCData server 1: 5. MCData client 1 requested that MCData client 2 to be removed from the ongoing data communication and successfully removed from data communication + + MCData server 1->>MCData client 5: 6. Ad hoc group data session request + Note right of MCData client 5: 7. Notify User + MCData client 5-->>MCData server 1: 8. Ad hoc group data session response + + Note over MCData server 1, MCData client 2: 9. Ad hoc group data communication changed by adding MCVideo client 5 based on the participant list specified by MCVideo client 1 + + MCData client 1->>MCData server 2: 10. Ad hoc group data session leave request + Note right of MCData server 2: 11. Notify User + MCData server 2-->>MCData client 1: 12. Ad hoc group data session leave response + + Note over MCData server 2, MCData client 4: 13. Ad hoc group data communication changed by removing MCVideo client 4 based on the participant list specified by MCVideo client 1 + + MCData client 1-->>MCData client 3: 14. Ad hoc group data session notify + + Note over MCData client 3, MCData client 5: 15. Notify participants of the on-going ad hoc group data communication regarding the change in the participants + +``` + +Sequence diagram showing the modification of ad hoc group data communication participants. The diagram is split into two systems: 'primary MC system' and 'partner MC system'. Lifelines include MCData client 3, MCData server 1 (primary), MCData client 1, MCData client 2, MCData server 2 (partner), MCData client 4, and MCData client 5. The sequence starts with an established ad hoc group data communication. MCData client 1 sends a 'Modify ad hoc group data session participants request' to MCData server 1. MCData server 1 responds with 'Authorize the request' and then 'Modify ad hoc group data session participants response'. MCData client 1 then sends requests to add MCData client 3 and 5, and remove MCData client 2 and 4. MCData server 1 sends an 'Ad hoc group data session request' to MCData client 5, which receives a response and notifies the user. MCData server 1 then sends a notification to MCData client 1 about the changes. MCData client 1 sends a 'Ad hoc group data session leave request' to MCData server 2, which receives a response and notifies the user. MCData server 2 then sends a notification to MCData client 1 about the changes. Finally, MCData client 1 sends an 'Ad hoc group data session notify' to MCData client 3, and a dashed box indicates that all participants are notified about the changes. + +**Figure 7.17.3.2.6-1: Modification of ad hoc group data communication participants by an authorized user** + +1. The MCData client 1 sends the modify ad hoc group data session participants request to the MCData server 1 to remove both MCData client 2 and MCData client 4 from the on-going ad hoc group data communication and to add both MCData client 3 and MCData client 5 into on-going ad hoc group data communication. + +2. The MCData server 1 verifies whether the MCData client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group data communication. + 3. The MCData server 1 sends modify ad hoc group data session participants response to the MCData client 1. + 4. The MCData server 1 determines that MCData client 1 has requested that MCData client 3 from the primary MC system be invited to an on-going ad hoc group data communication and successfully added to the data communication according to the procedure defined in clause 7.17.3.1.4. + 5. The MCData server 1 determines that MCData client 1 has requested that MCData client 2 from the primary MC system be removed from the on-going ad hoc group data communication and successfully removed from data communication according to the procedure defined in clause 7.17.3.1.4. + 6. The MCData server 1 determines that MCData client 1 has requested that MCData client 5 from the partner MC system be invited to an on-going ad hoc group data communication. The MCData server 1 sends the ad hoc group data session request to the MCData client 5. + 7. The MCData client 5 notifies the user about the incoming ad hoc group data communication. + 8. The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server 1. + 9. The on-going ad hoc group data communication is updated by adding MCData client 5 which is based on the modify participant list provided by the MCData client 1. + 10. The MCData server 1 determines that MCData client 1 has requested that MCData client 4 from the partner MC system be removed from the on-going ad hoc group data communication. The MCData server 1 sends the ad hoc group data session leave request to the MCData client 4. + 11. The MCData client 4 notifies the user of the ad hoc group data session leave request. + 12. The MCData client 4 sends the ad hoc group data session leave response to the MCData server 1. + 13. The on-going ad hoc group data communication is updated by removing MCData client 4, which is based on the modify participant list provided by the MCData client 1. +- NOTE: The ad hoc group data communication request and response exchanged between MCData server 1 of primary MC system and MCData client 4/MCData client 5 will always traversal through the MCData server 2. +14. The MCData server 1 may notify the initiating MCData user of all the users who are added to the on-going ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the ad hoc group data communication. + 15. The MCData server 1 may notify the authorized participants about the change in the participants list of on-going ad hoc group data communication. + +## 7.17.4 Ad hoc group short data service data communication procedures + +### 7.17.4.1 General + +This subclause contains procedures for ad hoc group short data service data communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjunction with the procedures defined in this subclause. Other common procedures specified in the 7.17.3 are used at any time after Ad hoc group short data service data communication establishment based on the need of it. These procedures are applicable for Group standalone short data service using media plane and Group short data service session as specified in the subclause 7.4.2.6 and subclause 7.4.2.7 respectively. + +#### 7.17.4.2 Information flows for short data service specific + +Table 7.17.4.2-1 describes the information elements that are specific to short data service and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. + +These information elements are included when an Ad hoc group data session request sent from the MCData client to the MCData server, between the MCData servers, and from the MCData server to the MCData client. + +**Table 7.17.4.2-1: short data service specific** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE 1) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | +| NOTE 1: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.17.4.3 Ad hoc group short data service data communication procedures in single MCData system + +##### 7.17.4.3.1 General + +The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data. + +##### 7.17.4.3.2 Procedure + +The procedure in figure 7.17.4.3.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request. + +Pre-conditions: + +1. As defined in the subclause 7.17.3.1.1. + +![Sequence diagram showing the Ad hoc group SDS data communication session. The participants are MCData client 1, MCData server, and MCData client 2 to n. The sequence of steps is: 1. Ad hoc group SDS data communication session Establishment as specified in subclause 7.17.3.1.1; 2. Data transmission; 3. Disposition notifications; 4. Ad hoc group SDS data communication session Termination As specified in subclause 7.17.3.1.2.](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 to n + Note right of MCData client 1: 1. Ad hoc group SDS data communication session Establishment as specified in subclause 7.17.3.1.1 + Note right of MCData client 1: 2. Data transmission + Note right of MCData client 1: 3. Disposition notifications + Note right of MCData client 1: 4. Ad hoc group SDS data communication session Termination As specified in subclause 7.17.3.1.2 + +``` + +Sequence diagram showing the Ad hoc group SDS data communication session. The participants are MCData client 1, MCData server, and MCData client 2 to n. The sequence of steps is: 1. Ad hoc group SDS data communication session Establishment as specified in subclause 7.17.3.1.1; 2. Data transmission; 3. Disposition notifications; 4. Ad hoc group SDS data communication session Termination As specified in subclause 7.17.3.1.2. + +**Figure 7.17.4.3.2-1: Ad hoc group SDS data communication session** + +1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.1.1. + +2. MCData client 1 and the ad hoc group data session request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified. +3. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users. +4. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released as specified in the subclause 7.17.3.1.2. + +#### 7.17.4.4 Ad hoc group short data service data communication procedures involving multiple MC systems + +##### 7.17.4.4.1 General + +The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data. + +##### 7.17.4.4.2 Procedure + +The procedure in figure 7.17.4.4.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request. + +Pre-conditions: + +1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.2.1 or subclause 7.17.3.2.3. + +![Sequence diagram for Ad hoc group SDS data communication session. The diagram shows five lifelines: MCData client 1, MCData server 1 (primary), MCData client 2 to n (primary), MCData server 2 (partner), and MCData client 2 to n (partner). The sequence of messages is: 1. Ad hoc group SDS data communication session Establishment involving multiple MC systems; 2. Data transmission; 3. Disposition notifications; 4. Ad hoc group SDS data communication session Termination involving multiple MC systems.](303fadfb9def251d1575d6221199b158_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server 1 (primary) + participant MCData client 2 to n (primary) + participant MCData server 2 (partner) + participant MCData client 2 to n (partner) + + Note over all participants: 1. Ad hoc group SDS data communication session Establishment involving multiple MC systems + Note over all participants: 2. Data transmission + Note over all participants: 3. Disposition notifications + Note over all participants: 4. Ad hoc group SDS data communication session Termination involving multiple MC systems + +``` + +Sequence diagram for Ad hoc group SDS data communication session. The diagram shows five lifelines: MCData client 1, MCData server 1 (primary), MCData client 2 to n (primary), MCData server 2 (partner), and MCData client 2 to n (partner). The sequence of messages is: 1. Ad hoc group SDS data communication session Establishment involving multiple MC systems; 2. Data transmission; 3. Disposition notifications; 4. Ad hoc group SDS data communication session Termination involving multiple MC systems. + +**Figure 7.17.4.4.2-1: Ad hoc group SDS data communication session** + +1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.2.1 or subclause 7.17.3.2.3. +2. MCData client 1 and the ad hoc group data session request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified. +3. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users. + +4. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released as specified in the subclause 7.17.3.2.2 or subclause 7.17.3.2.5. + +## 7.17.5 Ad hoc group file distribution communication procedures + +### 7.17.5.1 General + +This subclause contains procedures for ad hoc group file distribution communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjunction with the procedures defined in this subclause. Other common procedures specified in the 7.17.3 are used at any time after Ad hoc group file distribution communication establishment based on the need of it. + +#### 7.17.5.2 Information flows for file distribution specific + +Table 7.17.5.2-1 describes the information elements that are specific to file distribution and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request sent from the MCData client to the MCData server, between the MCData servers, and from the MCData server to the MCData client. + +**Table 7.17.5.2-1: file distribution specific** + +| Information element | Status | Description | +|--------------------------------|--------|-------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed report is expected or not | +| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) | +| Application metadata container | O | Implementation specific information that is communicated to the recipient | + +#### 7.17.5.3 Ad hoc group file distribution communication procedures in single MCData system + +##### 7.17.5.3.1 General + +The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging SDS data. + +##### 7.17.5.3.2 Procedure + +The procedure in figure 7.17.5.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.1.1. + +![Sequence diagram of an ad hoc group SDS data communication session. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2 to n. The sequence of messages is: 1. Ad hoc group File distribution communication Establishment as specified in subclause 7.17.3.1.1; 2. File distribution over media plane; 3. Disposition notifications; 4. Ad hoc group File distribution communication Termination As specified in subclause 7.17.3.1.2.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 to n + Note right of MCData client 1: 1. Ad hoc group File distribution communication Establishment as specified in subclause 7.17.3.1.1 + Note right of MCData client 1: 2. File distribution over media plane + Note right of MCData client 1: 3. Disposition notifications + Note right of MCData client 1: 4. Ad hoc group File distribution communication Termination As specified in subclause 7.17.3.1.2 + +``` + +Sequence diagram of an ad hoc group SDS data communication session. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2 to n. The sequence of messages is: 1. Ad hoc group File distribution communication Establishment as specified in subclause 7.17.3.1.1; 2. File distribution over media plane; 3. Disposition notifications; 4. Ad hoc group File distribution communication Termination As specified in subclause 7.17.3.1.2. + +**Figure 7.17.5.3.2-1: Ad hoc group SDS data communication session** + +1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.1.1. +2. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s). +3. The dispositions notifications are handled as specified in the subclause 7.5.2.7. +4. Based on the MCData user action or conditions to release, the established media plane for FD communication is released as specified in the subclause 7.17.3.1.2. + +#### 7.17.5.4 Ad hoc group file distribution communication procedures involving multiple MC systems + +##### 7.17.5.4.1 General + +The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging FD data. + +##### 7.17.5.4.2 Procedure + +The procedure in figure 7.17.5.4.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.2.1 or subclause 7.17.3.2.3. + +![Sequence diagram of an ad hoc group FD data communication session.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram illustrates a sequence of four steps in an ad hoc group file distribution (FD) data communication session. At the top, five entities are shown in boxes: MCData client 1, MCData server 1 (primary), MCData client 2 to n (primary), MCData server 2 (partner), and MCData client 2 to n (partner). Vertical lines extend from each box down to a series of four horizontal bars representing the steps: 1. Ad hoc group File distribution communication Establishment involving multiple MC systems, 2. File distribution over media plane, 3. Disposition notifications, and 4. Ad hoc group File distribution communication Termination involving multiple MC systems. Vertical lines continue from the bottom of these bars. + +Sequence diagram of an ad hoc group FD data communication session. + +**Figure 7.17.5.4.2-1: Ad hoc group FD data communication session** + +1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.2.1 or subclause 7.17.3.2.3. +2. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s). +3. The dispositions notifications are handled as specified in the subclause 7.5.2.7. +4. Based on the MCData user action or conditions to release, the established media plane for FD communication is released as specified in the subclause 7.17.3.2.2 or subclause 7.17.3.2.5. + +# --- Annex A (normative): MCData related configuration data + +## A.1 General + +This Annex provides information about the static data needed for configuration for the MCData service, which belongs to one of the following categories: + +- MCData UE configuration data (see subclause A.2); +- MCData user profile configuration data (see subclause A.3); +- MCData related group configuration data (see subclause A.4); and +- MCData service configuration data (see subclause A.5). + +For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCData UE, MCData group, MCData user and MCData service configuration data refers to the information that will be stored against each MCData UE, MCData group, MCData user and MCData service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.282 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. + - When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCData UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## A.2 MCData UE configuration data + +The general aspects of UE configuration are specified in 3GPP TS 23.280 [5]. Data in tables A.2-1 and A.2-2 have to be known by the MCData UE after MCData authorization. + +Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCData service. + +**Table A.2-1: UE configuration data (on and off network)** + +| Reference | Parameter description | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| | Short data service | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous SDS transactions (Nc4) | +| [R-5.4.2-004] of 3GPP TS 22.280 [2] | > Requested presentation priority of SDS messages received (see NOTE) | +| | File distribution | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous file distribution transactions (Nc4) | +| | Transmission control | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous data transmissions (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | > Maximum number of data transmissions (Nc5) in a group | +| | Reception control | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous data receptions (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | > Maximum number of data receptions (Nc5) in a group | +| NOTE: | Priority of SDS messages includes enhanced status updates, since enhanced status updates utilise the SDS mechanism. | + +**Table A.2-2: UE configuration data (on network)** + +| Reference | Parameter description | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | Relay service (Y/N) | +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | List of allowed relayed MCData groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) | +| | > MCData group ID | +| | > Relay service code (as specified in 3GPP TS 23.303 [7]) | +| NOTE: | When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. | + +## A.3 MCData user profile configuration data + +The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [5]. The MCData user profile configuration data is stored in the MCData user database. The MCData server obtains the MCData user profile configuration data from the MCData user database (MCData-2). + +Tables A.3-1 and A.3-2 contain the MCData user profile configuration required to support the use of on-network MCData service. Tables A.3-1 and A.3-3 contain the MCData user profile configuration required to support the use of off-network MCData service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. + +**Table A.3-1: MCData user profile configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| Subclause 8.1.2 of 3GPP TS 23.280 [5] | MCData identity (MCData ID) | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | Pre-selected MCData user profile indication (see NOTE 2) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | MCData user profile index | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | MCData user profile name | Y | Y | Y | Y | +| [R-5.17-007], [R-6.13.4-002] of 3GPP TS 22.280 [2] | User profile status (enabled/disabled) | | Y | Y | Y | +| [R-5.7-001], [R-6.9-003] of 3GPP TS 22.280 [2] | Authorised to create and delete aliases of an MCData user and its associated user profiles. | | | Y | Y | +| [R-5.7-002], [R-6.9-003] of 3GPP TS 22.280 [2] | Alphanumeric aliases of user | Y | Y | Y | Y | +| [R-5.1.1-005], [R-5.9-001] of 3GPP TS 22.280 [2] | Participant type of the user | Y | Y | Y | Y | +| [R-5.1.8-006], [R-5.3-002], [R-5.9-001], [R-5.16.2-001], [R-5.16.2-002] of 3GPP TS 22.280 [2] | User's Mission Critical Organization (i.e. which organization a user belongs to) | Y | Y | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a group-broadcast group | | | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a user-broadcast group | | | Y | Y | +| [R-5.6.2.4.1-002] of 3GPP TS 22.280 [2] | Authorised to activate MCData emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-013] of 3GPP TS 22.280 [17] | Automatically trigger a MCData emergency communication after initiating the MCData emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-004] [R-5.6.2.4.1-008] [R-5.6.2.4.1-012] of 3GPP TS 22.280 [2] | Group used on initiation of an MCData emergency group communication (see NOTE 3) | | | | | +| [R-5.6.2.4.1-004], [R-5.6.2.4.1-008], [R-5.6.2.4.1-012] of 3GPP TS 22.280 [17] | Recipient for an MCData emergency private communication (see NOTE 3) | | | | | +| | > MCData ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | + +| | | | | | | +|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-5.6.2.4.2-002] of 3GPP TS 22.280 [2] | Authorisation to cancel an MCData emergency alert | Y | Y | Y | Y | +| [R-6.15.6.2-002] of 3GPP TS 22.280 [2] | Authorised to activate an MCData ad hoc group emergency alert | Y | Y | Y | Y | +| [R-6.15.6.2-006] of 3GPP TS 22.280 [2] | Authorisation to cancel an MCData ad hoc group emergency alert | Y | Y | Y | Y | +| [R-6.15.6.2-007] of 3GPP TS 22.280 [2] | Authorised to set up an MCData group communication using the ad hoc group used for the alert | Y | Y | Y | Y | +| | Authorised to receive the participants information of an MCData ad hoc group emergency alert | N | Y | Y | Y | +| [R-6.1.1.2-005], [R-6.1.1.2-006], [R-6.1.1.2-007] of 3GPP TS 22.282 [3] | Individual conversation hang time | Y | Y | Y | Y | +| | One-to-one communication | | | | | +| [R-6.3.1.2-007] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13] | > List of MCData users this MCData user is authorized to initiate a one-to-one communication | | | | | +| | >> MCData ID | Y | N | Y | Y | +| | >> Discovery Group ID | Y | N | Y | Y | +| | >> User info ID (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | +| | >> KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| [R-6.7.3-007] of 3GPP TS 22.280 [2] | Authorised to make one-to-one communications towards users not included in "list of MCData user(s) this MCData user is authorized to initiate a one-to-one communication" | Y | Y | Y | Y | +| | File distribution | | | | | +| [R-5.3.2-010] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13] | > List of MCData users this MCData user is allowed to cancel distribution of files being sent or waiting to be sent | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| | >> KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| | Transmission and reception control | | | | | +| [R-6.2.2.1-001] of 3GPP TS 22.282 [3] | > Whether the MCData user is permitted to transmit data | Y | Y | Y | Y | +| [R-6.2.3-005] of 3GPP TS 22.282 [3] | > Maximum amount of data that the MCData user can transmit in a single request during one-to-one communication | Y | Y | Y | Y | +| [R-6.2.3-005] and [R-6.3.1.2-008] of 3GPP TS 22.282 [3] | > Maximum amount of time that the MCData user can transmit in a single request during one-to-one communication | Y | Y | Y | Y | + +| | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-6.2.3-001] of 3GPP TS 22.282 [3] | > List of MCData users this MCData user is allowed to request the release of an ongoing transmission that this MCData user is participating in | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| [R-5.1.7-002] and [R-6.8.7.2-007] and [R-6.8.7.2-008] of 3GPP TS 22.280 [2] | Priority of the user (see NOTE 4) | | Y | Y | Y | +| | Lossless communication for private communication | Y | Y | Y | Y | +| | Store communication in Message Store (see NOTE 5) | Y | Y | Y | Y | +| | Store private communication in Message Store (see NOTE 6) | Y | Y | Y | Y | +| [R-6.12-003] of 3GPP TS 22.280 [17] | Authorised to restrict the dissemination of the location information | Y | Y | Y | Y | +| Subclause 10.9 of 3GPP TS 23.280 [5] | Authorised to request location information of another user in the primary MCData system (see NOTE 7) | Y | Y | Y | Y | +| Subclause 10.9 of 3GPP TS 23.280 [5] | List of partner MCData systems for which user is authorised to request location information for another user | | | | | +| | > Identity of partner MCData system | Y | Y | Y | Y | +| NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | | | | | | +| NOTE 2: As specified in 3GPP TS 23.280 [5], for each MCData user's set of MCData user profiles, only one MCData user profile shall be indicated as being the pre-selected MCData user profile. | | | | | | +| NOTE 3: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCData user's currently selected group will be used. | | | | | | +| NOTE 4: The use of the parameter is left to implementation. | | | | | | +| NOTE 5: This is the top-level control parameter to determine whether MCData communications will be stored or not. When this parameter is set; the second level control parameter is used to determine whether a specific MCData communication (private or which group) will be stored and MCData user can request for all or selected of his/her MCData communication shall be stored in the MCData message store or not. | | | | | | +| NOTE 6: This is the second level control parameter to determine whether a private communication will be stored when the Store communication in Message Store top level control parameter is set. | | | | | | +| NOTE 7 : Further differentiation on authorisation for requesting location information based on detailed characteristics (e.g. MC organization, MC service ID, functional alias) is left to implementation. | | | | | | + +Table A.3-2: MCData user profile configuration data (on network) + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| [R-5.1.5-001], [R-5.1.5-002], [R-5.10-001], [R-6.4.7-002], [R-6.8.1-008], [R-6.7.4-002] of 3GPP TS 22.280 [2] | List of on-network MCData groups for use by an MCData user | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | > Store group communication in Message Store (see NOTE 11) | Y | Y | Y | Y | +| | > Application plane server identity information of group management | | | | | + +| | | | | | | +|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| | server where group is defined | | | | | +| | >> Server URI | Y | Y | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | > KMSUri for security domain of group (see NOTE 2) | Y | Y | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 3) | Y | N | Y | Y | +| | > Transmission and reception control | | | | | +| | >> Whether MCData user is permitted to transmit data in the group | Y | Y | Y | Y | +| | >> Maximum amount of data that the MCData user can transmit in a single request during group communication | Y | Y | Y | Y | +| | >> Maximum amount of time that the MCData user can transmit in a single request during group communication | Y | Y | Y | Y | +| Subclause 5.2.5 of 3GPP TS 23.280 [5] | List of groups user implicitly affiliates to after MCData service authorization for the user | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| [R-6.4.2-006] of 3GPP TS 22.280 [2] | Authorisation of an MCData user to request a list of which MCData groups a user has affiliated to | | Y | Y | Y | +| [R-6.4.6.1-002], [R-6.4.6.1-003] of 3GPP TS 22.280 [2] | Authorisation to change affiliated groups of other specified user(s) | | Y | Y | Y | +| [R-6.4.6.2-001], [R-6.4.6.2-002] of 3GPP TS 22.280 [2] | Authorisation to recommend to specified user(s) to affiliate to specific group(s) | | Y | Y | Y | +| [R-6.6.1-004] of 3GPP TS 22.280 [2] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of 3GPP TS 22.280 [2] | Presence status is available/not available to other users | Y | Y | Y | Y | +| [R-6.7.1-002], [R-6.7.2-002] of 3GPP TS 22.280 [2] | List of MCData users that MCData user is authorised to obtain presence of | | | | | +| | > MCData IDs | Y | Y | Y | Y | +| [R-6.8.7.4.2-001], [R-6.8.7.4.2-002] of 3GPP TS 22.280 [2] | Authorisation of a user to cancel an emergency alert on any MCData UE of any user | | Y | Y | Y | +| [R-6.13.4-001] of 3GPP TS 22.280 [2] | Authorisation for an MCData user to enable/disable an MCData user | | Y | Y | Y | +| [R-6.13.4-003], [R-6.13.4-005], [R-6.13.4-006], [R-6.13.4-007] of 3GPP TS 22.280 [2] | Authorisation for an MCData user to (permanently /temporarily) enable/disable a UE | | Y | Y | Y | +| [R-7.14-002], [R-7.14-003] of 3GPP TS 22.280 [2] | Authorization for manual switch to off-network while in on-network | Y | Y | Y | Y | +| [R-5.1.5-004] of 3GPP TS 22.280 [2] | Limitation of number of affiliations per user (N2) | N | Y | Y | Y | +| [R-6.4.6.1-001], [R-6.4.6.1-004] of 3GPP TS 22.280 [2] | List of MCData users whose selected groups are authorized to be remotely changed | | | | | + +| | | | | | | +|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| | > MCData ID | Y | Y | Y | Y | +| [R-6.7.3-007a] of 3GPP TS 22.280 [2] and 3GPP TS 33.180 [13] | List of MCData users this MCData user is authorized to receive a one-to-one communication | | | | | +| | > MCData ID | Y | Y | Y | Y | +| | > KMSUri for security domain of MCData ID | Y | Y | Y | Y | +| | Conversation management | | | | | +| [R-6.1.1.2-009] of 3GPP TS 22.282 [3]. | > List of MCData users to be sent message delivered disposition notifications in addition to the message sender | N | Y | Y | Y | +| | >> MCData ID | N | Y | Y | Y | +| [R-6.1.1.2-009] of 3GPP TS 22.282 [3]. | > List of MCData users to be sent message read disposition notifications in addition to the message sender | N | Y | Y | Y | +| | >> MCData ID | N | Y | Y | Y | +| 3GPP TS 23.283 [18] | Authorised to use LMR E2EE for interworking | Y | Y | Y | Y | +| 3GPP TS 23.283 [18] | > List of supported LMR technology types | | | | | +| 3GPP TS 23.283 [18] | >> LMR technology type (P25, TETRA etc.) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> URI of LMR key management functional entity (see NOTE 4 ) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> LMR specific identity (RSI for P25 or ITSId for TETRA) (see NOTE 5) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> LMR specific security information (see NOTE 5) | Y | N | Y | Y | +| | List of servers used in the private and group communications | | | | | +| | > MCData content server where the HTTP FD file is uploaded | | | | | +| | >> Server URI | Y | Y | Y | Y | +| | > MCData message store where the communication history stores | | | | | +| | >> Server URI | Y | Y | Y | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | List of partner MCData systems in which this profile is valid for use during migration | | | | | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCData system | Y | Y | Y | Y | +| Subclause 10.1.1 of 3GPP TS 23.280 [16] | > Access information for partner MCData system (see NOTE 6) | Y | | Y | Y | +| [R-5.9a-012] of 3GPP TS 22.280 [2] [R-5.9a-013] of 3GPP TS 22.280 [2] | Authorised to request information query of the association between active functional alias(es) and the MCData ID(s) | | Y | Y | Y | +| [R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [2] | List of groups the client affiliates/de-affiliates when criteria is met | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | >> Criteria for affiliation (see NOTE 7) | Y | Y | Y | Y | +| | >> Criteria for de-affiliation (see NOTE 7) | Y | Y | Y | Y | +| | >> Manual de-affiliation is not allowed if criteria for affiliation are | Y | Y | Y | Y | + +| | | | | | | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| | met | | | | | +| [R-6.6.4.2-002] of 3GPP TS 22.280 [2] | List of groups the client affiliates after receiving an emergency alert | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | >> Manual de-affiliation is not allowed if criteria for affiliation are met | Y | Y | Y | Y | +| | List of functional alias(es) of the MCData user | | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | > Functional alias | Y | Y | Y | Y | +| [R-5.9a-018] of 3GPP TS 22.280 [2] | >> Trigger criteria for activation by the MCData server (see NOTE 8) | N | Y | Y | Y | +| [R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [2] | >> Trigger criteria for de-activation by the MCData server (see NOTE 8) | N | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [2] | >> Trigger criteria for activation by the MCData client (see NOTE 8) | Y | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [2] | >> Trigger criteria for de-activation by the MCData client (see NOTE 8) | Y | Y | Y | Y | +| | >> Manual de-activation is not allowed if the criteria are met (see NOTE 8) | Y | Y | Y | Y | +| [R-5.9a-012] of 3GPP TS 22.280 [2] | Authorised to take over a functional alias from another MCData user | | Y | Y | Y | +| | Authorised to participate in an IP connectivity session | Y | Y | Y | Y | +| [R-5.5.2-003], [R-5.5.2-004] 3GPP TS 22.282 [3] | >List of MCData users which can be included in IP connectivity sessions. | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | >> KMSUri for security domain of the MCData ID | Y | Y | Y | Y | +| | >>List of associated data host IP information | | | | | +| | >>>IP information (see NOTE 9) | Y | Y | Y | Y | +| [R-5.5.2-003] 3GPP TS 22.282 [3] | Authorised to initiate remote point-to-point IP connectivity sessions | N | Y | Y | Y | +| | >List of MCData users which can be addressed in a remote initiated IP connectivity session; | | | | | +| | >> MCData ID | N | Y | Y | Y | +| [R-5.5.2-003] 3GPP TS 22.282 [3] | Authorised to tear down point-to-point IP connectivity sessions | N | Y | Y | Y | +| | >List of MCData users which can be addressed in a remote initiated IP connectivity session tear down; | | | | | +| | >> MCData ID | N | Y | Y | Y | +| [R-5.5.2-006] 3GPP TS 22.282 [3] | Authorised to request remotely application priority modification of established point-to-point IP connectivity sessions; | | | | | +| | >List of MCData users which can be addressed remotely to change the application priority of established IP connectivity sessions; | Y | Y | Y | Y | +| [R-5.10-001b] 3GPP TS 22.280 [2] | Maximum number of successful simultaneous MCData service authorizations for this user (see NOTE 10) | N | Y | Y | Y | +| | ad hoc group data communication authorizations | | | | | + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---|---|---|---| +| [R-6.15.5.3-001] of 3GPP TS 22.280 [2] | > Authorised to initiate ad hoc group data communication | Y | Y | Y | Y | +| R-6.15.5.3-003] of 3GPP TS 22.280 [2] | > Authorised to participate in ad hoc group data communication | Y | Y | Y | Y | +| | > Authorised to initiate emergency ad hoc group data communication | Y | Y | Y | Y | +| | > Authorised to initiate imminent peril ad hoc group data communication | Y | Y | Y | Y | +| | > Authorised to receive the participants information of an ad hoc group communication | N | Y | Y | Y | +| | > Authorised to modify the list of participants for an ad hoc group data communication | Y | Y | Y | Y | +| NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | | | | | | +| NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | | | | | | +| NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document. | | | | | | +| NOTE 4: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. | | | | | | +| NOTE 5: This is an LMR specific parameter with no meaning within MC services. | | | | | | +| NOTE 6: Access information for each partner MCData system comprises the list of information required for initial UE configuration to access an MCData system, as defined in table A.6-1 of 3GPP TS 23.280 [16] | | | | | | +| NOTE 7: The criteria may consist conditions such as the location of the MCData user or the active functional alias of the MCData user. | | | | | | +| NOTE 8: The criteria may consist of conditions such as MCData user location or time. | | | | | | +| NOTE 9: IP information may contain IP addresses, corresponding subnet masks, gateway and DNS settings. | | | | | | +| NOTE 10: If configured, this value has precedence over the system level parameter "maximum number of successful simultaneous service authorisations" in table A.5-2. If not configured, the corresponding parameter from table A.5-2 shall be used. | | | | | | +| NOTE 11: This is the second level control parameter to determine whether this group communication will be stored in the MCData message store when the Store communication in Message Store top level control parameter is set. | | | | | | + +**Table A.3-3: MCData user profile configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [2] | List of off-network MCData groups for use by this MCData user | | | | | +| | > MCData Group ID | Y | N | Y | Y | +| | > Store group communication in Message Store (see NOTE 4) | Y | N | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [13] | > KMSUri for security domain of group (see NOTE 2) | Y | N | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 3) | Y | N | Y | Y | +| [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [2] | Authorization for off-network services | Y | N | Y | Y | +| Subclause 7.16.1 | User info ID (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | + +NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of TS 23.280 [5]. + +NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. + +NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document. + +NOTE 4: This is the second level control parameter to determine whether this group communication will be stored in the MCData message store when the Store communication in Message Store top level control parameter is set. + +## A.4 MCData related Group configuration data + +The general aspects of group configuration are specified in 3GPP TS 23.280 [5]. + +Parameters specified in table A.4-1 are child parameters of the "MCData configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-2 are child parameters of the "MCData configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-3 are child parameters of the "MCData configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [5]. + +**Table A.4-1: Group configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|-----------------------------------------------------------------|-----------------------------------------------------------------------------|-----------|---------------|-------------------------| +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Media confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Transmission control confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Group media protection security material (see NOTE) | Y | N | Y | +| Subclause 5 | >> MCData sub-services and features enabled for the group | | | | +| | >>> Short data service enabled | Y | Y | Y | +| | >>> File distribution enabled | Y | Y | Y | +| | >>> IP connectivity enabled | Y | Y | Y | +| | >>> Conversation management enabled | Y | Y | Y | +| | >>> Transmission control enabled | Y | Y | Y | +| | >>> Reception control enabled | Y | Y | Y | +| | >>> Enhanced status enabled | Y | Y | Y | +| | >> Enhanced status | | | | +| [R-6.1.3.2-002] of 3GPP TS 22.282 [3] | >>> List of operational status values | Y | N | Y | +| [R-6.1.1.2-011] of 3GPP TS 22.282 [2] | >> Lossless communication | Y | Y | Y | +| [R-6.1.1.2-007] of 3GPP TS 22.282 [5] | >> Conversation hang time | Y | Y | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [13]. | | | | | + +**Table A.4-2: Group configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------|---------------|-------------------------| +| [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [2] | >> Authorisation of a user to request a list of affiliated members of a group | Y | Y | Y | +| [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006], [R-6.8.7.2-003] of 3GPP TS 22.280 [2] | >> Priority of the group | N | Y | Y | +| Subclause 6.2.2 of 3GPP TS 22.282 [3] | >> Transmission and reception control | | | | +| | >>> Maximum data size for SDS | Y | Y | Y | +| | >>> Maximum data size for FD | Y | Y | Y | +| | >>> Maximum data size for auto-receive | N | Y | Y | +| 3GPP TS 23.283 [18] | >> Indication whether use of LMR E2EE is permitted on the MCData group | Y | N | Y | +| 3GPP TS 23.283 [18] | >> LMR specific identity for MCData group (see NOTE) | Y | N | Y | +| 3GPP TS 23.283 [18] | >> Group to key binding (see NOTE) | Y | N | Y | +| NOTE: This is an LMR specific parameter with no meaning within MC services. | | | | | + +**Table A.4-3: Group configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|---------------------------------------|----------------------------------------------------------------------------------|------------------|----------------------|--------------------------------| +| Subclause 10.10 of 3GPP TS 23.280 [5] | >> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | >>> MCData group call signalling | Y | N | Y | +| | >>> MCData group call media | Y | N | Y | + +## A.5 MCData service configuration data + +The general aspects of MC service configuration are specified in 3GPP TS 23.280 [5]. The MCData service configuration data is stored in the MCData server. + +Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCData service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCData service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point. + +**Table A.5-1: MCData service configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|------------------|------------------------------|------------------|----------------------|----------------------------------------| +|------------------|------------------------------|------------------|----------------------|----------------------------------------| + +**Table A.5-2: MCData service configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| Subclause 6.2.2 of 3GPP TS 22.282 [3] | Transmission and reception control | | | | +| | > Maximum data size for SDS | Y | Y | Y | +| | > Maximum payload data size for SDS over signalling control plane (see NOTE 1) | Y | Y | Y | +| | > Maximum data size for FD | Y | Y | Y | +| [R-6.2.2.1-002d], [R-6.2.2.4-003] of 3GPP TS 22.282 [3] | > Time limit for the temporarily stored data waiting to be delivered to a receiving user | N | Y | Y | +| [R-6.2.2.3-001] of 3GPP TS 22.282 [3] | > Timer for periodic announcement with the list of available recently invited data group communications | N | Y | Y | +| | > Maximum data size for auto-receive | N | Y | Y | +| | List of functional alias identities | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Functional alias | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >> Limit number of simultaneous activations | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >> This functional alias can be taken over | N | Y | Y | +| | >> List of users who can activate this functional alias | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >>> MCData ID | N | Y | Y | +| [R-5.9a-016] of 3GPP TS 22.280 [17] | >> Communication priority (see NOTE 2) | N | Y | Y | +| [R-5.10-001a] of 3GPP TS 22.280 [2] | Maximum number of successful simultaneous service authorizations of clients from a user | N | Y | Y | +| | MCData notification server | | | | +| | > Server URI(s) | Y | Y | Y | +| Subclause 5.15 of 3GPP TS 22.280 [2] | List of permitted GW MC service ID(s) | | | | +| | > GW MC service ID | Y | Y | Y | +| | Ad hoc group data communication configurations | | | | +| [R-6.15.5.3-005] of 3GPP TS 22.280 [2] | > Support of ad hoc group data communication (enabled/disabled) (see NOTE 3) | Y | Y | Y | +| [R-6.15.5.3-002] of 3GPP TS 22.280 [2] | > Maximum number of participants allowed to participate in an ad hoc group data communication | Y | Y | Y | +| [R-6.15.5.3-004] of 3GPP TS 22.280 [2] | > Hang timer for ad hoc group data communication | N | Y | Y | +| | > Maximum duration for ad hoc group data communication | Y | Y | Y | +| | > List of preferred media codecs for ad hoc group data communication | Y | Y | Y | + +NOTE 1: The maximum payload data size for SDS over signalling control plane shall be less than or equal to the maximum data size for SDS. + +NOTE 2: The usage of this parameter by the MCData server is up to implementation. + +NOTE 3: If the support for ad hoc group data communication is disabled by the MC system then all other configurations related to ad hoc group data communication are not applicable + +**Table A.5-3: MCData service configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|---------------------------------------|-------------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| Subclause 10.10 of 3GPP TS 23.280 [5] | Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | > MCData one-to-one call signalling | Y | N | Y | +| | > MCData one-to-one call media | Y | N | Y | + +# Annex B (informative): Transmission control for MCData + +## B.1 Overview of transmission control process + +The MCData server may receive several simultaneous requests for data transmission, which may be associated with different types of communication e.g. group, private, 1-to-many. For each communication, how the requests are processed may be different. The requests that are not authorized shall be rejected by the transmission control function. For message requests over the signalling control plane, the processing should be immediate and is delivered to the recipients either via unicast or broadcast. However, for message requests over the media plane, transmission control arbitration (see Annex B.2) will be necessary. Subsequent to transmission control arbitration, and subject to the policy e.g. store and forward, the data is either delivered directly to the recipient MCData user or stored in the network repository and a corresponding URL is delivered. The end-to-end transmission control process is illustrated in figure B.1-1. + +![Flowchart of the transmission control process for MCData, showing the flow from a user wanting to send data through various decision points (signaling vs media plane, authorization, store and forward, broadcast vs unicast) to either sending data, sending a URL, or being rejected.](50214d232017279410e9c9db8eb75119_img.jpg) + +``` + +graph TD + subgraph UE + A[MCData user Wants to send data] --> B[Select data to send +Select recipient(s)/group] + B --> C{Use signaling control plane?} + C -- Yes --> D{Max payload Size over Signaling control Plane?} + D -- No --> E[Use signaling control plane to send] + D -- Yes --> F{Authorized To send?} + C -- No --> G[Use media plane to send] + end + G --> H{Authorized To send?} + F -- No --> I[Rejected] + F -- Yes --> J{Store and Forward?} + H -- No --> K[Rejected] + H -- Yes --> L[Transmission control arbitration] + J -- Yes --> M[Send URL to recipient(s)] + J -- No --> N{Broadcast?} + N -- Yes --> O[Send data to recipient(s) via broadcast] + N -- No --> P[Send data to recipient(s) via Unicast] + M --> P + O --> P + +``` + +Flowchart of the transmission control process for MCData, showing the flow from a user wanting to send data through various decision points (signaling vs media plane, authorization, store and forward, broadcast vs unicast) to either sending data, sending a URL, or being rejected. + +**Figure B.1-1: Transmission control process** + +## --- B.2 Transmission control arbitration + +The transmission control arbitration is a central function of the transmission control process and is implementation specific. In a typical deployment, multiple or simultaneous requests can be received at the transmission control arbitration function. Each of these requests may be categorized into different request types with different queuing priorities, and therefore each request type will be maintained with separate queues. Each request shall not be present in more than one queue at any given time. The queue types and the order of queues may be configured by the MCData administrator, as described below. + +- Transmission control queue: It is the primary queue from which the request is processed for transmission e.g. emergency communication requests may result in this queue and processed at the highest priority. +- Communication type queue: This queue may be sorted in the order of the communication type associated with the request. For example, the group communication requests may always take precedence over one-to-many or private communication requests. +- Static attribute queue: This queue may be formed based on the static attributes associated with the request e.g. group priority, user priority, which may be pre-configured by the MCData administrator. +- Dynamic attribute queue: This queue may be formed based on the dynamic attributes associated with the request e.g. location of the sending user, content size, etc. + +# --- Annex C: Void + +# Annex D (informative): Example of a User Message Storage Area + +The figure in subclause 7.13.1 illustrates the high-level structure of the MCData message store where objects are stored in a flat structure in the user storage area. This flat data structure provides maximum flexibility for UI implementation to present stored objects to the user. However, a folder hierarchy structure provides a better visual presentation of the stored objects to the MCData user. + +![Diagram of a user message storage area hierarchy for MCData user 1.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +The diagram illustrates a hierarchical folder structure for a user message storage area. At the top level, an oval labeled "MCData user 1" is connected to a horizontal line. From this line, four folders are shown: "Inbox", "Group 1", "Group 2", and "Group N". The "Inbox" folder contains three overlapping document icons, with the top one labeled "object". The "Group 1" folder contains two overlapping document icons, with the top one labeled "object". The "Group 2" folder contains one document icon labeled "object". The "Group N" folder contains two child folders: "Subject 1" and "Subject 2". The "Subject 1" folder contains three overlapping document icons, with the top one labeled "object". The "Subject 2" folder contains two overlapping document icons, with the top one labeled "object". Below "Subject 1" and "Subject 2" are two more child folders: "Date 1" and "Date 2". The "Date 1" folder contains three overlapping document icons, with the top one labeled "object". The "Date 2" folder contains two overlapping document icons, with the top one labeled "object". + +Diagram of a user message storage area hierarchy for MCData user 1. + +**Figure D-1: User message storage area example** + +In figure D-1 the MCData user 1 message storage area in the MCData message store is constructed in folder hierarchical way. A system default folder, Inbox, is configured to receive all new objects coming from active communications. The MCData user 1 creates Group 1, Group 2 and Group N folders to store communication history for different group communications that he is a member of. Once the Group 1 folder is created the MCData user 1 can then move all the objects related to Group 1 communication from the Inbox to the Group 1 folder. The MCData user 1 can also create child folders in Group 1 folder to further divide the stored objects into different groupings such as with different subjects, Subject 1 and Subject 2. Similarly, the MCData user 1 creates child folders, Date 1 and Date 2, in Group N folder to store communication history in group N occurred in different dates. With this hierarchical folder structure, the MCData user 1 can browse his user account in the MCData message store interactively and navigate to the information he would like to see. For example, the MCData user 1 can start with the top-level root folder and traverse down the folder hierarchy to reach to Date 2 folder and see the communication history of group N in that particular date. + +# --- Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-07 | | | | | | Initial version. | 0.0.0 | +| 2016-08 | | | | | | Update following SA6#12 incorporating the following pCRs:
S6-160810; S6-160875; S6-160876 | 0.1.0 | +| 2016-10 | | | | | | Update following SA6#13 incorporating the following pCRs:
S6-161169; S6-161170; S6-161243; S6-161265; S6-161085; S6-161173; S6-161174; S6-161245; S6-161176; S6-161248; S6-161177; S6-161178; S6-161266; S6-161267; S6-161184 | 0.2.0 | +| 2016-11 | | | | | | Update following SA6#14 incorporating the following pCRs:
S6-161316; S6-161586; S6-161609; S6-161587; S6-161589; S6-161506; S6-161576; S6-161507; S6-161326; S6-161508; S6-161577; S6-161511; S6-161512; S6-161616; S6-161514; S6-161515; S6-161516; S6-161580; S6-161581; S6-161519; S6-161498; S6-161642 | 0.3.0 | +| 2016-11 | SA#74 | SP-160878 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160878 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170071 | 0002 | 2 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0003 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0004 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0005 | 2 | D | Adding descriptive text for the FD procedure section | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0006 | 2 | D | Resolving editor's notes for the short data service feature | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0007 | 1 | D | Adding references for the signalling control plane | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0008 | 2 | D | Adding descriptive text for the transmission and reception control section | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0009 | | F | MCData correction of reference | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0010 | | F | Alignment of business relationships, identities, and application of functional model to deployments | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0011 | 3 | F | file download editorials | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0013 | 1 | F | Off-network conversation management | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0014 | 1 | D | Editorial corrections | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0015 | 1 | F | Resolving EN in Scope | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0016 | 5 | F | Resolving EN in Functional model | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0017 | 1 | F | Resolving EN in SDS procedures | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0018 | | F | Referring generic procedures from CFA | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0020 | 2 | F | Conversation management definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0021 | 2 | F | Disposition alignments and corrections in SDS and FD | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0022 | 1 | F | Tx and Rx control procedure corrections | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0025 | 1 | F | MCData functional model alignment | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0027 | 1 | F | Moving configuration data to on-network only | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0028 | 3 | F | Resolve SDS on-network information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0030 | 1 | F | Resolve FD information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0031 | 2 | F | Adding end-to-end encryption requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0032 | 1 | F | Resolve transmission control information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0033 | 2 | F | Resolve conversation management EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0034 | 1 | F | Addition of definition for MCData ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0035 | | F | Addition of definition for MCData ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0036 | 3 | F | Off-network information flows for SDS | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0037 | 1 | F | Resolve communication release information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0038 | 1 | F | Conditions for using SDS media plane | 14.1.0 | +| 2017-06 | SA#76 | SP-170392 | 0039 | 2 | F | Correction on MCData reference points when using MBMS | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0048 | | D | Additions to Definition and Abbreviations | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0049 | 2 | F | Clarifications to section 5 Architecture requirements | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0051 | 1 | F | Clarifications to section 6.5.1 that SDS Distribution function in MCData server talks to SDS function in MCData client not UE | 14.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2017-06 | SA#76 | SP-170392 | 0052 | | F | Clarifications to section 6.5.3.1.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0054 | 1 | D | Correct wrong reference in section 7.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0056 | 3 | F | Correct the MCData data disposition notification IEs | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0058 | 1 | D | Consistent use of pre-condition in section 7.4.2.2.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0059 | 1 | F | Inconsistent use of MCData group ID or list of recipients in request | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0061 | 3 | F | Content reference URL should be a mandatory IE when uploading a file | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0062 | 5 | F | Addition of new configuration and miscellaneous corrections | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0063 | 5 | F | Addition of identity management server address per group | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0064 | | F | Correction on sending data with mandatory download | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0070 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0071 | 4 | F | Clarification to Auto-send | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0076 | | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0078 | 2 | F | CR to 23.282 on Auto-receive | 14.2.0 | +| 2017-06 | SA#76 | SP-170394 | 0040 | 4 | B | Information flow of File Distribution for off-network | 15.0.0 | +| 2017-06 | SA#76 | SP-170394 | 0041 | 1 | B | Functional model of File Distribution for off-network | 15.0.0 | +| 2017-06 | SA#76 | SP-170394 | 0075 | 1 | C | Functional model of File Distribution for off-network | 15.0.0 | +| 2017-09 | SA#76 | SP-170682 | 0079 | 2 | B | Introduction of SDS application type identifiers | 15.1.0 | +| 2017-09 | SA#76 | SP-170685 | 0080 | 1 | B | Addition of IWF and IWF-2 | 15.1.0 | +| 2017-09 | SA#76 | SP-170681 | 0083 | 1 | A | File size check for FD | 15.1.0 | +| 2017-09 | SA#76 | SP-170681 | 0085 | 1 | A | Correction to configuration for Auto-receive parameter | 15.1.0 | +| 2018-01 | SA#78 | SP-170891 | 0087 | 1 | F | SDS location field: Alignment of Stage 2 with Stage 1 & Stage 3 | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 0088 | 1 | D | Editorial changes to MCData stage 2 | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0089 | 1 | F | Adding application identifier in media plane SDSs | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 0090 | 1 | F | Off-network Conversation Management clarifications | 15.2.0 | +| 2018-01 | SA#78 | SP-170889 | 0094 | 2 | A | PSI configuration for MCData service | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 0095 | 1 | F | Completion of Communication Release | 15.2.0 | +| 2018-01 | SA#78 | SP-170894 | 0096 | 1 | F | MBMS packet recovery | 15.2.0 | +| 2018-04 | SA#79 | SP-180148 | 0099 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180155 | 0100 | 3 | B | LMR E2EE user profile and group parameters | 15.3.0 | +| 2018-04 | SA#79 | SP-180148 | 0102 | 2 | A | Payload size limit for standalone SDS over signalling control plane | 15.3.0 | +| 2018-04 | SA#79 | SP-180151 | 0103 | 1 | F | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180148 | 0107 | 1 | A | Duplicated procedure name for MCData Group SDS | 15.3.0 | +| 2018-06 | SA#80 | SP-180367 | 0109 | | A | Clarification for presentation priority in MCData UE configuration | 15.4.0 | +| 2018-06 | SA#80 | SP-180370 | 0110 | 3 | A | Modify MCData download data response | 15.4.0 | +| 2018-09 | SA#81 | SP-180677 | 0111 | 2 | C | Media storage function in the MCData server | 16.0.0 | +| 2018-09 | SA#81 | SP-180677 | 0113 | 3 | C | Adding the Network base Message Store | 16.0.0 | +| 2018-12 | SA#82 | SP-181178 | 0116 | 1 | F | Corrections on CR implementation errors | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0117 | 1 | F | Configuration parameters to support requirement [R-6.1.1.2-009] are incorrect | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0118 | 2 | F | Corrections to Table A.2-1, Table A.4-2 and Table A.5-2 | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0119 | 4 | F | Corrections to "Release of MCData communication using HTTP" procedures | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0120 | 1 | F | Alignment with the MCData content server | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0121 | 1 | F | There is no file download when using media plane for FD | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0122 | 2 | B | Procedures for MCData message store operations | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0123 | 1 | F | Correct misalignment on MCData user usage | 16.1.0 | +| 2019-03 | SA#83 | SP-190074 | 0124 | - | F | Correct the location of MCData content server and MCData message store configuration parameters in table A.3-2 configuration table | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0125 | - | D | Editorial correction on the term of MCData | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0126 | 2 | B | Additional architecture requirement for MCData message store | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0127 | 2 | B | Generic SDS procedure with MCData message store | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0128 | 3 | B | Providing data for a user entering an ongoing MCData group conversation | 16.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | SA#83 | SP-190075 | 0130 | 1 | B | MCData user profile migration information | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0131 | 2 | F | Message store object and metadata | 16.2.0 | +| 2019-03 | SA#83 | SP-190075 | 0132 | 1 | B | Introduction of gateway MC server for interconnection | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0133 | 2 | B | Example of user storage area with folder hierarchy structure | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0134 | 2 | C | Making data sync between MCData message store and message store client bi-directional | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0135 | 1 | B | Add more operations to the MCData message store | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0136 | 1 | B | Off-network SDS with MCData message store | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0137 | 1 | B | Restricting incoming private communications | 16.3.0 | +| 2019-06 | SA#84 | SP-190486 | 0138 | 2 | B | Interconnection for file distribution | 16.3.0 | +| 2019-06 | SA#84 | SP-190486 | 0139 | 1 | B | Interconnection and migration with message store | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0140 | 2 | B | User configuration for functional alias information query for MCData | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0141 | 1 | B | User requested priority in 23.281 | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0142 | 3 | B | Criteria based automatic group affiliation and deaffiliation | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0143 | 2 | B | MCData configuration for functional alias | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0144 | 4 | B | Functional alias support configuration items | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0145 | 3 | B | Functional alias supplements for the MCData transmission and reception control procedures | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0147 | 2 | B | Functional alias support for Short Data Service (SDS) | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0148 | 3 | B | MC Data User IP connectivity service capability– part 1 Functional Architecture | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0149 | 1 | C | MCData transport capabilities for IP connectivity service | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0150 | 6 | B | MCData File Distribution using the MBMS download delivery method | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0151 | - | C | Remove the procedure in 7.5.2.9 File removal using HTTP by MCData server | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0152 | 2 | F | Remove the duplicated MCData server URI in UE configuration table | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0153 | 3 | F | Add lossless communication to network group configuration and fix missing configuration parameter | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0154 | 2 | F | Resolution proposals for some Editor's Notes | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0155 | | B | MCData client performs automatic activation and deactivation of functional aliases based on location | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0156 | | B | MCData server limits the number of simultaneous successful service authorisations | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0157 | 3 | B | Functional alias support for MCData File Distribution | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0159 | 3 | B | MC Data User IP connectivity service capability– part 2 IP connectivity for Point-to-Point and Group communication | 16.3.0 | +| 2019-09 | SA#85 | SP-190729 | 0161 | 3 | F | Correct the configuration parameters for the MCData emergency alert procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0169 | 1 | F | Fix omission of location services in MCData | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0170 | 2 | B | EPS bearer for emergency | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0171 | 2 | B | Emergency support for one-to-one SDS | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0172 | 2 | B | Emergency and imminent peril support for group SDS | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0173 | 2 | B | Emergency support for off-network SDS | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0174 | 2 | C | Addition of Location information to SDS and Enhance Status | 16.4.0 | +| 2019-09 | SA#85 | SP-190732 | 0177 | 1 | F | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | 16.4.0 | +| 2019-09 | SA#85 | SP-190732 | 0178 | | F | Stage 1 requirement reference correction in the user profile data | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0179 | 2 | F | Clarification and corrections to support transmission control | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0180 | 2 | F | Corrections to the transmission and reception control procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0183 | 1 | B | One-to-one SDS Session upgrade to emergency session | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0184 | 1 | B | Group SDS Session upgrade to emergency/imminent-peril session and cancel in-progress emergency/imminent-peril group state | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0185 | 2 | B | One-to-One Emergency MCData FD | 16.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-09 | SA#85 | SP-190729 | 0186 | 1 | B | Group emergency MCData FD | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0187 | 1 | B | One-to-one FD Session upgrade to emergency session | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0188 | 1 | B | Group FD communication upgrade to emergency/imminent-peril communication and cancel in-progress emergency/imminent-peril group state | 16.4.0 | +| 2019-09 | SA#85 | SP-190735 | 0162 | 2 | B | Point-to-Point IP connectivity using functional alias to address the target MCData user | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0163 | 2 | B | SDS addressing based on functional alias | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0164 | 4 | B | Remote initiation of Point-to-Point IP connectivity | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0165 | 4 | B | Remote tear down of point-to-point IP connectivity | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0166 | 1 | B | Communication priority for functional aliases | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0181 | 3 | B | File distribution addressing based on functional alias | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0182 | 2 | B | IP connectivity for group communication (unicast) | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0189 | 3 | B | Capability to change remotely the priority of the point-to-point IP connectivity communication | 17.0.0 | +| 2019-12 | SA#86 | SP-191113 | 0190 | 2 | F | Requested Priority in IP connectivity point to point communication | 17.1.0 | +| 2019-12 | SA#86 | SP-191113 | 0191 | 1 | B | Enhancing SDS data requests with application priority capabilities in on-network mode | 17.1.0 | +| 2019-12 | SA#86 | SP-191113 | 0193 | 2 | B | Priority of the user | 17.1.0 | +| 2019-12 | SA#86 | SP-191108 | 0196 | | A | File repair with the content storage function | 17.1.0 | +| 2020-03 | SA#87-E | SP-200113 | 0197 | 2 | A | Correction of internal clause references for Enhanced Status transmission | 17.2.0 | +| 2020-03 | SA#87-E | SP-200117 | 0199 | 2 | C | Corrections and enhancements to IP Connectivity | 17.2.0 | +| 2020-03 | SA#87-E | SP-200113 | 0200 | 2 | A | Enhancements and clarifications for file repair and file delivery using MBMS | 17.2.0 | +| 2020-03 | SA#87-E | SP-200113 | 0201 | 2 | A | Clarification on prepending the MCData content server URI | 17.2.0 | +| 2020-03 | SA#87-E | SP-200113 | 0202 | 1 | A | Local policies at Partner MCData system is not applied | 17.2.0 | +| 2020-03 | SA#87-E | SP-200117 | 0208 | 1 | F | Clarifications for MCData file distribution over MBMS | 17.2.0 | +| 2020-04 | - | - | - | - | - | MCC editorial correction, adding missing line break in clause 6.6.2 | 17.2.1 | +| 2020-07 | SA#88-E | SP-200341 | 0212 | 1 | B | Add the network MCData notification Server | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0213 | 1 | B | Add new "search folder" and "retrieve folder content" operations | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0214 | | F | Pre-emption of EPS bearers by a new MCData bearer | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0215 | | F | Miscellaneous small corrections | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0216 | 1 | F | Corrections to the one-to-one SDS information elements | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0217 | 1 | F | Minor editorial corrections | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0218 | | F | Corrections to the one-to-one SDS and FD communication upgrade flows | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0219 | | F | Corrections to the MCData group standalone FD request information elements | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0220 | | F | Corrections to the group SDS informational elements | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0221 | | F | Corrections to the group FD upgrade and FD in-progress priority state cancel request | 17.3.0 | +| 2020-07 | SA#88-E | SP-200341 | 0222 | | F | MCData corrections in off-network SDS procedures | 17.3.0 | +| 2020-09 | SA#89-E | SP-200843 | 0226 | 1 | B | Limit the number of simultaneous logins on per user basis | 17.4.0 | +| 2020-09 | SA#89-E | SP-200839 | 0227 | 1 | A | Removal of content reference IE from the FD requests using media plane | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0228 | 1 | F | Functional alias handling for 1-1 FD requests | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0229 | 1 | F | Functional alias handling for one-one session SDS requests | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0230 | 1 | F | Functional alias handling for one-one standalone SDS requests | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0231 | 1 | F | Functional alias handling for IPCon | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0232 | 1 | B | Providing stored files in MCData content server for FD over MBMS | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0233 | 1 | C | Enhancement of MBMS user service usage procedures | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0234 | 1 | C | Enhancement of Group standalone FD using MBMS | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0236 | 1 | F | MCData emergency group communication clarifications | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0237 | 1 | F | MCData one-to-one emergency communication clarifications | 17.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | SA#89-E | SP-200845 | 0238 | 1 | F | Clarifications on the use of ProSe in off-network MCData communications | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0239 | 1 | F | Apply transmission and reception control to all FD HTTP procedures consistently | 17.4.0 | +| 2020-09 | SA#89-E | SP-200845 | 0240 | | F | Functional alias handling for 1-1 FD requests using HTTP | 17.4.0 | +| 2020-12 | SA#90-E | SP-200989 | 0242 | 1 | A | Align Annex B with changes to "auto-send" | 17.5.0 | +| 2020-12 | SA#90-E | SP-200989 | 0243 | 2 | A | Correction to the transmission control configuration parameters | 17.5.0 | +| 2020-12 | SA#90-E | SP-200996 | 0246 | | F | Various corrections | 17.5.0 | +| 2020-12 | SA#90-E | SP-200989 | 0248 | | A | IP connectivity, SDS and FD functional model correction | 17.5.0 | +| 2020-12 | SA#90-E | SP-200996 | 0249 | | B | Application specific metadata container | 17.5.0 | +| 2020-12 | SA#90-E | SP-200996 | 0250 | 1 | F | Removal of duplicate MCData disposition notification information flow | 17.5.0 | +| 2020-12 | SA#90-E | SP-200996 | 0251 | | F | Corrections to FD using procedures and editorials | 17.5.0 | +| 2020-12 | SA#90-E | SP-200996 | 0252 | 1 | B | Depositing file contents distributed via FD communication using HTTP into MCData message store | 17.5.0 | +| 2020-12 | SA#90-E | SP-200996 | 0253 | 1 | B | Distribution of file residing in MCData message store account of the MCData user | 17.5.0 | +| 2021-04 | SA#91-E | SP-210178 | 0255 | 1 | B | Message Store control | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0256 | 1 | F | Corrections to FD using media plane | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0257 | | F | Correction to Deposit an Object procedure | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0258 | | D | Correct typos on information tables | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0259 | 1 | F | Correction and clarification on file upload using HTTP procedure | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0260 | | F | Correction to message names in some procedures | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0261 | 1 | F | Add the IE of Emergency indicator in the message of MCData FD request | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0263 | 1 | B | Addition of MBMS delivery via MB2 interface for MCData | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0264 | 1 | F | Corrections to the file distribution using HTTP procedures | 17.6.0 | +| 2021-04 | SA#91-E | SP-210178 | 0265 | 1 | B | MCData file upload using HTTP including request of network resources with required QoS | 17.6.0 | +| 2021-06 | SA#92-E | SP-210487 | 0263 | 3 | B | Corrections and enhancements to the Notification procedures | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0269 | 2 | F | Aggregated notifications and reports | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0270 | 1 | F | Correct misuse of the term "transmission control" | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0271 | 1 | B | MCData file download including request of network resources with required QoS | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0272 | 1 | C | Enhancement and corrections to group file distribution using HTTP | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0273 | 1 | C | Enhancement and corrections to one-to-one file distribution using HTTP | 17.7.0 | +| 2021-06 | SA#92-E | SP-210567 | 0274 | 1 | F | Correction to MCData-5 reference point description | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0275 | 1 | F | EN resolutions in clause 5 | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0276 | 1 | F | EN resolutions in clause 6 | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0277 | 1 | F | EN resolutions in clause 7 | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0278 | 1 | F | EN resolution in B.1 | 17.7.0 | +| 2021-06 | SA#92-E | SP-210487 | 0279 | 2 | F | Proposal on Data Streaming service | 17.7.0 | +| 2021-09 | SA#93-E | SP-210962 | 0281 | | F | Various fixes for 23.282 | 17.8.0 | +| 2021-09 | SA#93-E | SP-210962 | 0282 | | F | Notification URL correction | 17.8.0 | +| 2021-09 | SA#93-E | SP-210962 | 0283 | | F | Clarify the supports of stored and forward functionality | 17.8.0 | +| 2021-09 | SA#93-E | SP-210962 | 0284 | 1 | F | Correction of preconditions and statements related to storing of MCData communication into Message store | 17.8.0 | +| 2021-09 | SA#93-E | SP-210962 | 0285 | 1 | F | Clarifying the use of deposit file indication IE in MCData FD request using HTTP | 17.8.0 | +| 2021-09 | SA#93-E | SP-210962 | 0286 | 1 | F | Clarifying the lossless communication | 17.8.0 | +| 2021-12 | SA#94-E | SP-211523 | 0287 | | F | Clarify MCData service delivery for offline users and delivery notification | 17.9.0 | +| 2021-12 | SA#94-E | SP-211523 | 0288 | 1 | F | Missing information table for the notification message | 17.9.0 | +| 2021-12 | SA#94-E | SP-211523 | 0289 | 2 | F | Disposition Type of specified MCData users | 17.9.0 | +| 2021-12 | SA#94-E | SP-211523 | 0291 | 1 | F | Clarification on the use of MCData notification server(s) | 17.9.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-12 | SA#94-E | SP-211529 | 0290 | 1 | B | Connection authorisation configuration data | 18.0.0 | +| 2022-06 | SA#96 | SP-220476 | 0294 | | F | Corrections to the use of MC service system | 18.1.0 | +| 2022-06 | SA#96 | SP-220477 | 0295 | 1 | B | Decoupling signalling and media for MCData service capabilities | 18.1.0 | +| 2022-06 | SA#96 | SP-220476 | 0296 | | B | Allow the user to restrict the dissemination of the location information – MCData Configuration | 18.1.0 | +| 2022-09 | SA#97-E | SP-220924 | 0297 | 1 | F | MCData communication to a FA user | 18.2.0 | +| 2022-09 | SA#97-E | SP-220924 | 0298 | 1 | B | Call connect and disconnect over MBMS for MCData | 18.2.0 | +| 2023-03 | SA#99 | SP-230289 | 0300 | 2 | B | User profile configuration data to support MCData ad hoc group emergency alerts | 18.3.0 | +| 2023-03 | SA#99 | SP-230287 | 0303 | 2 | C | MCData user profile configuration parameters for location information | 18.3.0 | +| 2023-03 | SA#99 | SP-230289 | 0304 | 2 | B | Information flows and procedures for the ad hoc group data communication for SDS and FD services of MCData | 18.3.0 | +| 2023-03 | SA#99 | SP-230289 | 0305 | 1 | B | Description for the terms used in the Ad hoc Group Communication procedures | 18.3.0 | +| 2023-03 | SA#99 | SP-230289 | 0306 | 1 | B | Configuration parameters of Ad hoc group data communication for MCData | 18.3.0 | +| 2023-06 | SA#100 | SP-230709 | 0307 | 1 | B | Adds user profile data for allowing subsequent MCData communications after an adhoc group emergency alert | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0308 | 1 | B | Configuration for receiving the adhoc group emergency alert participants list notification (MCData) | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0309 | 3 | F | Example of MCData services which are not handled by SIP core | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0310 | | B | Notifying authorized user about adhoc group participants list involving single MC systems - MCData | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0311 | 2 | B | Information flows and procedures involving multiple systems for the ad hoc group data session in MCData | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0312 | 2 | F | Corrections for ad hoc group data communication setup | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0313 | 2 | F | Correct MCData ID usage in information flow table | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0314 | 1 | F | MCData ad hoc group ID correction | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0315 | 2 | F | Remove unnecessary information flow tables | 18.4.0 | +| 2023-06 | SA#100 | SP-230709 | 0316 | 1 | B | Updates adhoc group call procedures for allowing a subsequent MCData communication after an adhoc group emergency alert | 18.4.0 | +| 2023-09 | SA#101 | SP-230998 | 0319 | 1 | F | Adding references on group definitions (MCData) | 18.5.0 | +| 2023-09 | SA#101 | SP-231004 | 0323 | 1 | F | Missing configuration for ad hoc group MCData communication | 18.5.0 | +| 2023-09 | SA#101 | SP-231004 | 0324 | 1 | F | Missing pre-conditions and steps for ad hoc group MCData communication | 18.5.0 | +| 2023-12 | SA#102 | SP-231558 | 0330 | 1 | F | Configuration for authorising modification of ad hoc group data communication participants - mcdata | 18.6.0 | +| 2023-12 | SA#102 | SP-231558 | 0335 | 1 | F | Modification of ad hoc group data communication participants involving multiple MCData systems | 18.6.0 | +| 2023-12 | SA#102 | SP-231558 | 0338 | 1 | F | Correction to modification of ad hoc group data communication participants procedure | 18.6.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23283/raw.md b/raw/rel-18/23_series/23283/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..50bd0dd5288d2d2d9e671a0aa1154ec9cf7cd443 --- /dev/null +++ b/raw/rel-18/23_series/23283/raw.md @@ -0,0 +1,7368 @@ + + +# 3GPP TS 23.283 V18.1.0 (2023-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Communication Interworking with Land Mobile Radio Systems; 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, 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. + +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..... | 11 | +| 2 References..... | 11 | +| 3 Definitions, symbols and abbreviations ..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Abbreviations ..... | 12 | +| 4 Introduction..... | 12 | +| 5 Assumptions and architectural requirements ..... | 13 | +| 5.1 Key management..... | 13 | +| 5.2 Packet format..... | 13 | +| 6 Involved business relationships ..... | 13 | +| 7 Functional model..... | 14 | +| 7.1 General ..... | 14 | +| 7.2 Functional model description ..... | 14 | +| 7.3 Functional entities description ..... | 14 | +| 7.3.1 IWF..... | 14 | +| 7.4 Reference points..... | 15 | +| 7.4.1 Reference point IWF-1 (between the IWF and the MCPTT server) ..... | 15 | +| 7.4.2 Reference point IWF-2 (between the IWF and the MCData server)..... | 15 | +| 7.4.3 Reference point IWF-3 (between the IWF and the group management server)..... | 15 | +| 7.4.4 Reference point IWF-4 (between the IWF and the LMS)..... | 15 | +| 8 Identities..... | 15 | +| 8.1 Identity mapping ..... | 15 | +| 9 Application of functional model to deployments..... | 15 | +| 10 Procedures and information flows ..... | 16 | +| 10.1 Affiliation..... | 16 | +| 10.1.1 Information flows for affiliation..... | 16 | +| 10.1.1.1 General..... | 16 | +| 10.1.1.2 IWF group affiliation request ..... | 16 | +| 10.1.1.3 IWF group affiliation response ..... | 16 | +| 10.1.1.4 IWF group de-affiliation request ..... | 16 | +| 10.1.1.5 IWF group de-affiliation response..... | 17 | +| 10.1.2 Affiliation procedures..... | 17 | +| 10.1.2.1 General..... | 17 | +| 10.1.2.2 Group affiliation to a group defined in the MC system..... | 18 | +| 10.1.2.3 Group de-affiliation from a group defined in the MC system ..... | 19 | +| 10.1.2.4 Group affiliation to group defined in the LMR system ..... | 20 | +| 10.1.2.5 Group de-affiliation from a group defined in the LMR system..... | 21 | +| 10.2 Group management ..... | 23 | +| 10.2.1 Information flows for group management..... | 23 | +| 10.2.1.1 General..... | 23 | +| 10.2.1.2 IWF group regroup teardown notification ..... | 23 | +| 10.2.1.3 IWF group regroup teardown notification response ..... | 23 | +| 10.2.1.4 IWF group regroup request..... | 23 | +| 10.2.1.5 IWF group regroup response ..... | 23 | +| 10.2.1.6 IWF group regroup notification..... | 24 | +| 10.2.1.7 IWF group regroup notification response ..... | 24 | +| 10.2.1.8 IWF group information request ..... | 24 | +| 10.2.1.9 IWF group information response..... | 24 | +| 10.2.1.10 IWF group information provision request ..... | 24 | +| 10.2.1.11 IWF group information provision response..... | 25 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------|----| +| 10.2.1.12 | IWF group information subscribe request ..... | 25 | +| 10.2.1.13 | IWF group information subscribe response..... | 25 | +| 10.2.1.14 | IWF group information notify request..... | 25 | +| 10.2.1.15 | IWF group information notify response ..... | 26 | +| 10.2.2 | Group regrouping ..... | 26 | +| 10.2.2.1 | General..... | 26 | +| 10.2.2.2 | MC system initiates the group regroup..... | 26 | +| 10.2.2.3 | IWF initiates the group regroup..... | 28 | +| 10.2.2.4 | Ownership of the group regroup..... | 29 | +| 10.2.2.5 | Simultaneous group regroup requests from each side of the IWF-1 interface ..... | 29 | +| 10.2.2.6 | Resolution of vocoder and encryption mode for the group regroup..... | 29 | +| 10.2.3 | Group configuration for interworking ..... | 29 | +| 10.2.3.1 | Overview..... | 29 | +| 10.2.3.2 | MC system provides group configuration to the IWF ..... | 30 | +| 10.2.3.3 | IWF requests group configuration from the MC system ..... | 30 | +| 10.2.3.4 | IWF provides group configuration to the MC system..... | 31 | +| 10.2.3.5 | MC system requests group configuration from the IWF ..... | 32 | +| 10.2.3.6 | IWF subscribes to group configuration ..... | 32 | +| 10.2.3.7 | MC system notifies group configuration ..... | 33 | +| 10.2.3.8 | MC system subscribes to group configuration ..... | 33 | +| 10.2.3.9 | IWF notifies group configuration ..... | 34 | +| 10.3 | Group call..... | 35 | +| 10.3.1 | General ..... | 35 | +| 10.3.2 | Information flows for group call over interworking group ..... | 35 | +| 10.3.2.1 | General..... | 35 | +| 10.3.2.2 | IWF group call request ..... | 35 | +| 10.3.2.3 | IWF group call response (IWF – MCPTT server)..... | 35 | +| 10.3.2.4 | IWF Group-broadcast group call setup request..... | 36 | +| 10.3.2.5 | IWF Group-broadcast group call setup response..... | 36 | +| 10.3.2.6 | IWF Group-broadcast group call release request ..... | 36 | +| 10.3.2.7 | IWF group-broadcast group call release response..... | 37 | +| 10.3.2.8 | IWF group join request..... | 37 | +| 10.3.2.9 | IWF group join response..... | 37 | +| 10.3.2.10 | IWF group call leave request..... | 38 | +| 10.3.2.11 | IWF group call leave response..... | 38 | +| 10.3.2.12 | IWF group call release request ..... | 38 | +| 10.3.2.13 | IWF group call release response..... | 39 | +| 10.3.2.14 | IWF pre-configured regroup request ..... | 39 | +| 10.3.2.15 | IWF pre-configured regroup response..... | 39 | +| 10.3.2.16 | IWF pre-configured regroup cancel request..... | 39 | +| 10.3.2.17 | IWF pre-configured regroup cancel response..... | 40 | +| 10.3.2.18 | IWF pre-configured regroup reject (IWF – MCPTT server, MCPTT server - IWF) ..... | 40 | +| 10.3.3 | Pre-arranged group call ..... | 40 | +| 10.3.3.1 | General..... | 40 | +| 10.3.3.2 | Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system..... | 41 | +| 10.3.3.3 | Group call setup initiated by LMR user on an interworking group defined in MCPTT system. .... | 42 | +| 10.3.3.4 | Group call setup initiated by MCPTT user on an interworking group defined in the LMR system .... | 43 | +| 10.3.3.5 | Group call setup initiated by LMR user on an interworking group defined in the LMR system. .... | 45 | +| 10.3.3.6 | Encrypted group call with transcoding ..... | 46 | +| 10.3.3.7 | Late Entry ..... | 48 | +| 10.3.3.7.1 | General ..... | 48 | +| 10.3.3.7.2 | Group call late entry on an interworking group defined in the MCPTT system..... | 48 | +| 10.3.3.7.3 | Group call late entry on an interworking group defined in the LMR system ..... | 49 | +| 10.3.3.8 | Interworking group call release ..... | 51 | +| 10.3.3.8.1 | General ..... | 51 | +| 10.3.3.8.2 | Group call release on an interworking group defined in the MCPTT system..... | 51 | +| 10.3.3.8.3 | Group call release on an interworking group defined in the LMR system ..... | 52 | +| 10.3.4 | Group broadcast..... | 53 | +| 10.3.4.1 | General..... | 53 | +| 10.3.4.2 | Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the MCPTT system..... | 53 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------|----| +| 10.3.4.3 | Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the LMR system..... | 56 | +| 10.3.4.4 | Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the MCPTT system..... | 58 | +| 10.3.4.5 | Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the LMR system ..... | 60 | +| 10.3.4.6 | Broadcast group regroup call using pre-configured group ..... | 61 | +| 10.3.4.6.1 | General ..... | 61 | +| 10.3.4.6.2 | Broadcast group regroup call using pre-configured group the MCPTT system ..... | 61 | +| 10.3.4.6.3 | Broadcast group regroup call using pre-configured group in the IWF ..... | 62 | +| 10.3.5 | Chat group call ..... | 63 | +| 10.3.5.1 | General..... | 63 | +| 10.3.5.2 | MCPTT user initiated chat group call in an interworking group defined in LMR system..... | 63 | +| 10.3.5.3 | LMR user initiated chat group call in an interworking group defined in MCPTT system..... | 64 | +| 10.3.5.4 | Release chat group call on an interworking group defined in the LMR system..... | 65 | +| 10.3.5.5 | Release chat group call on an interworking group defined in the MCPTT system ..... | 66 | +| 10.3.5.6 | void ..... | 67 | +| 10.3.5.7 | void ..... | 67 | +| 10.3.5.8 | Newly joined MCPTT group member of a group defined in the LMR system..... | 67 | +| 10.3.5.9 | Newly joined LMR group member of a group defined in the MCPTT system..... | 68 | +| 10.3.5.10 | MCPTT client returning to coverage on a group homed in the LMR system ..... | 69 | +| 10.3.6 | Exiting group call due to de-affiliation..... | 70 | +| 10.3.6.1 | General..... | 70 | +| 10.3.6.2 | Exiting group call defined in the LMR system due to de-affiliation ..... | 70 | +| 10.3.6.3 | Exiting group call defined in the MCPTT system due to de-affiliation ..... | 71 | +| 10.3.7 | Group regroup with pre-configured group ..... | 72 | +| 10.3.7.1 | General..... | 72 | +| 10.3.7.2 | Regroup formation using pre-configured group ..... | 73 | +| 10.3.7.2.1 | Regroup formation using pre-configured group initiated in the MCPTT system ..... | 73 | +| 10.3.7.2.2 | Regroup formation using pre-configured group initiated in the IWF ..... | 75 | +| 10.3.7.3 | Regroup cancellation using pre-configured group regroup ..... | 76 | +| 10.3.7.3.1 | Regroup cancellation using pre-configured group initiated in the MCPTT system ..... | 76 | +| 10.3.7.3.2 | Regroup cancellation using pre-configured group initiated in the IWF..... | 77 | +| 10.3.7.4 | Regroup rejection using pre-configured group ..... | 78 | +| 10.3.7.4.1 | Regroup rejection using pre-configured group for regroup initiated in the MCPTT system..... | 78 | +| 10.3.7.4.2 | Regroup rejection using pre-configured group for regroup initiated in the IWF..... | 79 | +| 10.3.7.5 | Pre-configured regroup update procedures..... | 80 | +| 10.3.7.5.1 | MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup..... | 80 | +| 10.3.7.6 | Call request on pre-configured regroup group after group regroup has been cancelled..... | 82 | +| 10.3.7.6.1 | MCPTT client PTTs on pre-configured regroup group after group regroup has been cancelled ..... | 82 | +| 10.3.7.7 | Adding newly affiliated user to a pre-configured group regroup ..... | 83 | +| 10.3.7.7.1 | Adding newly affiliated MCPTT user to a pre-configured group regroup ..... | 83 | +| 10.3.7.7.2 | Adding newly affiliated user homed in the IWF to a pre-configured group regroup ..... | 84 | +| 10.3.8 | User regroup with pre-configured group ..... | 84 | +| 10.3.8.1 | General..... | 84 | +| 10.3.8.2 | Pre-configured user regroup formation..... | 85 | +| 10.3.8.2.1 | Pre-configured user regroup formation by the MCPTT system..... | 85 | +| 10.3.8.2.2 | Pre-configured user regroup formation by the IWF ..... | 87 | +| 10.3.8.3 | Pre-configured user regroup cancellation ..... | 88 | +| 10.3.8.3.1 | Pre-configured user regroup cancellation by the MCPTT system ..... | 88 | +| 10.3.8.3.2 | Pre-configured user regroup cancellation by the IWF ..... | 89 | +| 10.4 | Private call..... | 89 | +| 10.4.1 | Information flows for private calls ..... | 89 | +| 10.4.1.1 | General..... | 89 | +| 10.4.1.2 | IWF private call request..... | 90 | +| 10.4.1.3 | IWF private call response ..... | 90 | +| 10.4.1.4 | IWF ringing..... | 91 | +| 10.4.1.5 | IWF call end request..... | 91 | +| 10.4.1.6 | IWF call end response..... | 91 | +| 10.4.2 | Private call setup in automatic commencement mode..... | 91 | +| 10.4.2.1 | MCPTT user initiating an MCPTT private call ..... | 91 | +| 10.4.2.2 | LMR user initiating a private call with MCPTT user..... | 93 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------------|-----| +| 10.4.3 | Private call setup in manual commencement mode..... | 94 | +| 10.4.3.1 | MCPTT user is initiating an MCPTT private call ..... | 94 | +| 10.4.3.2 | LMR user initiating a private call with MCPTT user..... | 96 | +| 10.4.4 | Private call release..... | 98 | +| 10.4.4.1 | MCPTT client initiated ..... | 98 | +| 10.4.4.2 | MCPTT server initiated ..... | 99 | +| 10.4.4.3 | LMR user initiated..... | 100 | +| 10.4.5 | Encryption of private calls..... | 101 | +| 10.5 | Floor control..... | 101 | +| 10.5.1 | General ..... | 101 | +| 10.5.2 | Information flows for floor control ..... | 101 | +| 10.5.2.1 | General..... | 101 | +| 10.5.2.2 | IWF floor request..... | 101 | +| 10.5.2.3 | IWF floor granted ..... | 102 | +| 10.5.2.4 | IWF floor rejected..... | 102 | +| 10.5.2.5 | IWF floor request cancel..... | 102 | +| 10.5.2.6 | IWF floor request cancel response..... | 103 | +| 10.5.2.7 | IWF floor request cancel notify ..... | 103 | +| 10.5.2.8 | IWF floor idle ..... | 103 | +| 10.5.2.9 | IWF floor release ..... | 104 | +| 10.5.2.10 | IWF floor taken..... | 104 | +| 10.5.2.11 | IWF floor revoked ..... | 104 | +| 10.5.2.12 | IWF floor acknowledgement ..... | 104 | +| 10.5.2.13 | IWF queue position request..... | 105 | +| 10.5.2.14 | IWF queue position info ..... | 105 | +| 10.5.2.15 | IWF unicast media stop request..... | 105 | +| 10.5.2.16 | IWF unicast media resume request..... | 106 | +| 10.5.2.17 | IWF floor talker ID update ..... | 106 | +| 10.5.3 | Interworking floor control ..... | 106 | +| 10.5.4 | Floor override without using floor revoked on an interworking group..... | 107 | +| 10.5.5 | Floor control on an interworking group homed in the LMR system..... | 108 | +| 10.5.6 | Floor control on an interworking group homed in the MCPTT system..... | 110 | +| 10.5.7 | Floor control without local filtering on an interworking group defined in the LMR system..... | 111 | +| 10.5.8 | Floor control without local filtering on an interworking group defined in the MCPTT system ..... | 113 | +| 10.5.9 | Floor control in private call controlled by the LMR system ..... | 114 | +| 10.5.10 | Floor control in private call controlled by the MCPTT system..... | 115 | +| 10.6 | Emergency and imminent peril ..... | 116 | +| 10.6.1 | Information flows for emergency and imminent peril..... | 116 | +| 10.6.1.1 | IWF emergency group call request..... | 116 | +| 10.6.1.2 | IWF emergency group call response ..... | 116 | +| 10.6.1.3 | IWF imminent peril group call request..... | 117 | +| 10.6.1.4 | IWF imminent peril group call response ..... | 117 | +| 10.6.1.5 | IWF in-progress imminent peril group state cancel request..... | 117 | +| 10.6.1.6 | IWF in-progress imminent peril group state cancel response..... | 118 | +| 10.6.1.7 | IWF emergency alert request..... | 118 | +| 10.6.1.8 | IWF emergency alert response ..... | 118 | +| 10.6.1.9 | IWF emergency alert cancel request..... | 118 | +| 10.6.1.10 | IWF emergency alert cancel response ..... | 119 | +| 10.6.1.11 | IWF in-progress emergency group state cancel request..... | 119 | +| 10.6.1.12 | IWF in-progress emergency group state cancel response..... | 119 | +| 10.6.2 | Emergency calls..... | 120 | +| 10.6.2.1 | General..... | 120 | +| 10.6.2.2 | Emergency group call ..... | 120 | +| 10.6.2.2.1 | Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the MCPTT system ..... | 120 | +| 10.6.2.2.2 | Emergency group call setup initiated by a user in the MCPTT system on an interworking group defined in MCPTT system..... | 122 | +| 10.6.2.2.3 | Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the LMR system..... | 124 | +| 10.6.2.2.4 | Emergency group call setup initiated by a user in the MCPTT system to an interworking group defined in the LMR system..... | 125 | +| 10.6.2.3 | In-progress emergency group state cancel of an interworking group..... | 127 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------------------|-----| +| 10.6.2.3.1 | LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system ..... | 127 | +| 10.6.2.3.2 | MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system ..... | 128 | +| 10.6.2.3.3 | LMR user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system ..... | 129 | +| 10.6.2.3.4 | MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system ..... | 130 | +| 10.6.2.4 | Losing audio ..... | 132 | +| 10.6.2.5 | Default emergency group..... | 132 | +| 10.6.2.6 | Emergency private call ..... | 132 | +| 10.6.2.7 | LMR systems that do not track group emergencies..... | 132 | +| 10.6.3 | Imminent peril calls ..... | 132 | +| 10.6.3.1 | General..... | 132 | +| 10.6.3.2 | Imminent peril group call initiated by an MCPTT user on an interworking group ..... | 132 | +| 10.6.3.3 | Group call initiated by a user in the LMR system on an interworking group in imminent peril state ..... | 134 | +| 10.6.3.4 | In-progress imminent peril state cancel on an interworking group ..... | 136 | +| 10.6.4 | Emergency alerts ..... | 138 | +| 10.6.4.1 | Emergency alert initiated by LMR user..... | 138 | +| 10.6.4.2 | Emergency alert initiated by MC service user..... | 139 | +| 10.6.5 | Emergency alert cancellation..... | 141 | +| 10.6.5.1 | Emergency alert cancellation of an LMR user ..... | 141 | +| 10.6.5.2 | Emergency alert cancellation of an MC service user ..... | 142 | +| 10.7 | Codec..... | 144 | +| 10.7.1 | Information flows for codec ..... | 144 | +| 10.7.1.1 | IWF codec reconciliation request ..... | 144 | +| 10.7.1.2 | IWF codec reconciliation response..... | 144 | +| 10.7.2 | IWF transcoding ..... | 144 | +| 10.7.3 | Codec negotiation by the LMR system ..... | 144 | +| 10.7.3.1 | Description..... | 144 | +| 10.8 | MCDATA short data service ..... | 145 | +| 10.8.1 | General ..... | 145 | +| 10.8.2 | Information flows for the short data service..... | 146 | +| 10.8.2.1 | General..... | 146 | +| 10.8.2.2 | IWF MCDATA standalone data request..... | 146 | +| 10.8.2.3 | IWF MCDATA data disposition notification..... | 146 | +| 10.8.2.4 | IWF MCDATA group standalone data request (IWF – MCDATA server) ..... | 147 | +| 10.8.2.5 | IWF MCDATA group standalone data request (MCDATA server - IWF)..... | 147 | +| 10.8.2.6 | IWF MCDATA data disposition notification(s) (MCDATA server to IWF) ..... | 147 | +| 10.8.2.7 | IWF MCDATA group standalone data request (IWF – MCDATA server) ..... | 148 | +| 10.8.2.8 | IWF MCDATA group standalone data request (MCDATA server – IWF) ..... | 148 | +| 10.8.2.9 | IWF MCDATA group standalone data response ..... | 149 | +| 10.8.3 | Behaviour at the MCDATA Client ..... | 149 | +| 10.8.4 | Behaviour at the IWF ..... | 149 | +| 10.8.5 | Behaviour at the MCDATA server ..... | 149 | +| 10.8.6 | MCDATA user one-to-one SDS request to an LMR user ..... | 149 | +| 10.8.6.1 | Signalling control plane ..... | 149 | +| 10.8.6.2 | Media plane..... | 150 | +| 10.8.7 | LMR user one-to-one SDS request to an MCDATA user ..... | 150 | +| 10.8.7.1 | Signalling control plane ..... | 150 | +| 10.8.7.2 | Media plane..... | 150 | +| 10.8.8 | MCDATA user group SDS request to an MCDATA group including LMR users ..... | 150 | +| 10.8.8.1 | Signalling control plane ..... | 150 | +| 10.8.8.2 | Media plane..... | 150 | +| 10.8.9 | LMR user group SDS request to an MCDATA group..... | 150 | +| 10.8.9.1 | Signalling control plane ..... | 150 | +| 10.8.9.2 | Media plane..... | 151 | +| 10.9 | IWF as a security gateway ..... | 151 | +| 10.9.1 | Support for transcoding with encrypted speech ..... | 151 | +| 10.10 | Simultaneous interworked calls (on-network) ..... | 151 | +| 10.10.1 | General ..... | 151 | + +| | | | +|---------------|----------------------------------------------------------------------------------------------------------------------|-----| +| 10.11 | Location..... | 151 | +| 10.11.1 | Location of current talker ..... | 151 | +| 10.11.2 | Location of current talker (MCPTT server to IWF)..... | 151 | +| 10.11.3 | Location of current talker (IWF to MCPTT server)..... | 152 | +| 10.11.4 | Information flows for location information between the IWF and the LMS ..... | 153 | +| 10.11.4.1 | Location information services between the IWF and the LMS ..... | 153 | +| 10.11.4.1.1 | IWF Location information report ..... | 153 | +| 10.11.4.1.2 | IWF Location information request..... | 153 | +| 10.11.4.1.3 | IWF Location information subscription request ..... | 153 | +| 10.11.4.1.4 | IWF Location information subscription response ..... | 153 | +| 10.11.4.1.5 | IWF Location information notification ..... | 154 | +| 10.11.4.1.6 | IWF Location information cancel subscription request ..... | 154 | +| 10.11.4.1.7 | IWF Location information cancel subscription response..... | 154 | +| 10.11.4.2 | Location information procedures between the IWF and the LMS ..... | 154 | +| 10.11.4.2.1 | On-demand request of location information procedure ..... | 154 | +| 10.11.4.2.1.1 | On-demand request of location information procedure (LMS to IWF) ..... | 154 | +| 10.11.4.2.1.2 | On-demand request of location information procedure (IWF to LMS) ..... | 155 | +| 10.11.4.2.2 | Location information notification procedure ..... | 156 | +| 10.11.4.2.2.1 | Location information notification procedure (IWF to LMS) ..... | 156 | +| 10.11.4.2.2.2 | Location information notification procedure (LMS to IWF) ..... | 157 | +| 10.11.4.2.3 | Location information subscription procedure ..... | 158 | +| 10.11.4.2.3.1 | Location information subscription procedure (LMS to IWF) ..... | 158 | +| 10.11.4.2.3.2 | Location information subscription procedure (IWF to LMS) ..... | 159 | +| 10.11.4.2.4 | Location information cancel subscription procedure ..... | 160 | +| 10.11.4.2.4.1 | Location information cancel subscription procedure (LMS to IWF)..... | 160 | +| 10.11.4.2.4.2 | Location information cancel subscription procedure (IWF to LMS)..... | 161 | +| 10.12 | LMR security transport ..... | 162 | +| 10.12.1 | Information flows for LMR security transport ..... | 162 | +| 10.12.1.1 | Non-3GPP security message request..... | 162 | +| 10.12.1.2 | Non-3GPP security message response..... | 162 | +| 10.12.2 | LMR key management messages ..... | 163 | +| 10.12.2.1 | General..... | 163 | +| 10.12.2.2 | MC service client initiated..... | 163 | +| 10.12.2.3 | IWF initiated ..... | 163 | +| 10.13 | Analogue FM/TIA-603-D and other legacy LMR interworking ..... | 164 | +| 10.13.1 | General ..... | 164 | +| 10.13.2 | Interworking Concepts ..... | 164 | +| 10.13.3 | Procedures ..... | 165 | +| 10.13.3.1 | Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system ..... | 166 | +| 10.13.3.2 | Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system..... | 168 | +| 10.14 | IWF functional alias management..... | 170 | +| 10.14.1 | General ..... | 170 | +| 10.14.2 | IWF information flows for functional alias management ..... | 170 | +| 10.14.2.1 | IWF functional alias information query request ..... | 170 | +| 10.14.2.2 | IWF functional alias information query response..... | 170 | +| 10.14.2.3 | IWF functional alias activation request ..... | 171 | +| 10.14.2.4 | IWF functional alias activation response..... | 171 | +| 10.14.2.5 | IWF functional alias de-activation request..... | 171 | +| 10.14.2.6 | IWF functional alias de-activation response..... | 171 | +| 10.14.2.7 | IWF functional alias status notification ..... | 172 | +| 10.14.2.8 | IWF Functional alias take over request ..... | 172 | +| 10.14.2.9 | IWF Functional alias take over response..... | 172 | +| 10.14.2.10 | IWF Functional alias revoke notification ..... | 172 | +| 10.14.3 | IWF Functional alias management procedures ..... | 173 | +| 10.14.3.1 | General..... | 173 | +| 10.14.3.2 | User homed in the IWF retrieves active functional alias(es) for a certain MC service user ..... | 173 | +| 10.14.3.3 | User homed in the IWF activates functional alias(es) within an MC system..... | 173 | +| 10.14.3.4 | User homed in the IWF de-activates functional alias(es) within an MC system..... | 174 | +| 10.14.3.5 | User homed in the IWF takes over functional alias(es) within an MC system..... | 175 | +| 10.15 | First-to-answer call setup ..... | 176 | + +| | | | +|----------------------------------------------------|----------------------------------------------------|------------| +| 10.15.1 | Description ..... | 176 | +| 10.15.2 | Information flows for first-to-answer call ..... | 176 | +| 10.15.2.1 | IWF first-to-answer call request ..... | 176 | +| 10.15.2.2 | IWF first-to-answer call response ..... | 177 | +| 10.15.2.3 | IWF first-to-answer call cancel request ..... | 177 | +| 10.15.2.4 | IWF first-to-answer call cancel response ..... | 177 | +| 10.15.3 | Procedures ..... | 178 | +| 10.15.3.1 | MCPTT user initiating a first-to-answer call ..... | 178 | +| 10.15.3.2 | LMR user initiating a first-to-answer call ..... | 179 | +| 10.16 | Enhanced status ..... | 180 | +| 10.16.1 | General ..... | 180 | +| 10.16.2 | Preset values for enhanced status ..... | 180 | +| 10.16.3 | Enhanced status for on-network ..... | 180 | +| 10.16.3.1 | Procedure (MCData to IWF) ..... | 180 | +| 10.16.3.2 | Procedure (IWF to MCData) ..... | 181 | +| Annex A (informative): Change history ..... | | 182 | + +--- + +## 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 objective of this technical specification is to specify interworking between MC systems and LMR systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [3], MCCoRe requirements in 3GPP TS 22.280 [2] and the MCData requirements (SDS only) in 3GPP TS 22.282 [4]. + +The present document refers to an InterWorking Function (IWF). The structure and functionality of the IWF is out of scope of the present document. The definition of reference points between the IWF and MC systems and the interactions between the IWF and MC systems are in scope of the present document. + +--- + +# 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.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1". +- [3] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1". +- [4] 3GPP TS 22.282: "Mission Critical Data services". +- [5] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [6] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [7] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [8] 3GPP TS 33.180: "Security of the mission critical service" +- [9] TTA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards". + +--- + +# 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]. + +**End-to-End Encryption:** encryption that is applied by an originating terminal or client and is decrypted only by chosen terminating terminals or clients. + +**User homed in the IWF:** is an MC service ID that represents an LMR user in the MC system. + +**Interworking:** a means of communication between mission critical systems and LMR systems whereby MC users obtaining service from a mission critical system can communicate with LMR users who are obtaining service from one or more LMR systems. + +**Interworking function:** adapts LMR Systems to mission critical systems via the IWF interface and supports interworking between LMR systems and mission critical systems. + +**Interworking group:** a group, which is composed of group members from the MC system and the LMR system and defined in the MC system or the LMR system. + +**LMR system:** the collection of applications, services, and enabling capabilities providing a land mobile radio service offering group and private communications. + +**LMR user:** a user of a device which allows participation in an LMR system. + +NOTE: The term LMR user is defined for discussion purposes only and is out of scope of the present document. + +## 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]. + +| | | +|-------|-------------------------------------| +| E2EE | End-to-End Encryption | +| IWF | InterWorking Function | +| KEK | Key Encryption Key (TETRA) | +| KMS | Key Management Service | +| MC | Mission Critical | +| MCPTT | Mission Critical Push To Talk | +| LMR | Land Mobile Radio | +| LMC | Location Management Client | +| LMS | Location Management Server | +| OTAK | Over-The-Air-Key Management (TETRA) | +| OTAR | Over-The-Air Rekeying (P25) | +| P25 | Project 25 | +| SDS | Short Data Service | +| TETRA | TERrestrial Trunked Radio | +| UE | User Equipment | +| UKEK | Unique Key Encryption Key (P25) | +| URI | Uniform Resource Identifier | + +--- + +## 4 Introduction + +Mission critical users currently employ a wide range of LMR mission critical Push To Talk services, and associated data capabilities where available. + +The present document describes the architecture to support the interworking between the MC system and the LMR system to satisfy interworking requirements specified in 3GPP TS 22.179 [3] and 3GPP TS 22.282 [4]. Other LMR technologies may interwork as long as they conform to the present document. + +The IWF, along with its LMR system, will appear as a peer interconnected MC system. This is meant as an approach for defining interactions on the IWF interface but is not intended to specify the functionality of the IWF nor meant to mandate a deployment model. + +--- + +## 5 Assumptions and architectural requirements + +### 5.1 Key management + +Interworking requirements for key management for encrypted interworking include: + +- a) a mechanism to securely (i.e. authenticity, integrity, confidentiality) share an LMR E2EE traffic key for a private call sessions between a party in an MCPTT system and a party in the LMR system; +- b) a mechanism to securely convey to group members, the LMR E2EE key or set of LMR E2EE keys associated with an MC service group or set of MC service groups, to be used for encryption of interworking group calls spanning the multiple systems; +- c) a mechanism to securely share with temporary group members in MC systems, the LMR E2EE key(s) associated with a temporary MC service group to be used in interworking group calls spanning the multiple systems; +- d) key management solutions shall not preclude the ability of an IWF to allow one or more individual Mission Critical Organizations from having sole control over and sole access to LMR E2EE traffic keys used for the entity's media traffic and users' key encryption keys (UKEKs or KEKs); +- e) key management solutions shall support the ability of the IWF to decrypt/reencrypt the media traffic for zero or more groups; and, +- f) for deployments where Mission Critical Organizations wish to use LMR E2EE mechanisms when interworking with LMR users: + - i) a mechanism to securely provision an MC service client with the user's UKEK or KEK; and, + - ii) a mechanism to convey LMR OTAR or OTAK message contents. + +### 5.2 Packet format + +Each LMR technology defines its own packet format for voice media transmission. For interworking sessions, there might be cases where LMR formatted media is required to be transferred between the IWF and LMR aware MCPTT clients. An example of such a case is where E2EE is used and thus the IWF is not able to decrypt the media. In such cases, media that is sent over the IWF-1 interface needs to be routed within MCPTT systems to/from LMR aware MCPTT clients using methods described in 3GPP TS 23.379 [7]. + +Requirements for media transmission across the IWF-1 interface include: + +- a) media transmission to carry the LMR formatted media between the IWF and LMR aware MCPTT clients; and +- b) the MCPTT system, along with the IWF, may choose to encrypt the LMR formatted media using 3GPP mechanisms. + +NOTE: The contents of the LMR formatted media is out of scope of the present document. + +--- + +## 6 Involved business relationships + +No business relationships have been identified. + +## 7 Functional model + +### 7.1 General + +### 7.2 Functional model description + +Figure 7.2-1 shows the functional model for the application plane for interworking between MC systems and LMR systems. Functional entities and interfaces depicted on the right-hand side of the IWF-x interfaces are defined in 3GPP TS 23.280 [5], 3GPP TS 23.379 [7], and 3GPP TS 23.282 [6]. + +![Functional model for application plane for interworking diagram](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram illustrates the functional model for the application plane for interworking. On the left is a large vertical rectangle labeled 'IWF'. To its right, four interfaces are shown: IWF-1, IWF-3, IWF-4, and IWF-2. IWF-1 connects to an 'MCPTT server'. IWF-3 connects to a dashed box containing four stacked rectangles: 'Group management server', 'Configuration management server', 'Identity management server', and 'Key management server'. IWF-4 connects to a dashed box containing two stacked rectangles: 'Location management server' and 'Common services core'. IWF-2 connects to an 'MCData server'. + +Functional model for application plane for interworking diagram + +Figure 7.2-1: Functional model for application plane for interworking + +### 7.3 Functional entities description + +#### 7.3.1 IWF + +The IWF supports most of the functionality of peer MCPTT and MCData systems, with some differences, as specified in the present document. The IWF supports any necessary protocol translation and identity mapping between the MC systems and the IWF. The internal function of the IWF is out of scope of the present document. + +## 7.4 Reference points + +### 7.4.1 Reference point IWF-1 (between the IWF and the MCPTT server) + +The IWF-1 reference point, which exists between the IWF and the MCPTT server, provides peer to peer interconnection between an LMR system and the MCPTT system. IWF-1 supports a subset of MCPTT-3 as defined in 3GPP TS 23.379 [7], with some differences, as specified in the present document. The IWF-1 interface is supported by the same signalling plane protocol(s) as defined for MCPTT-3 except as specified in the present document. + +### 7.4.2 Reference point IWF-2 (between the IWF and the MCData server) + +The IWF-2 reference point, which exists between the IWF and the MCData server, provides SDS interconnection between an LMR system and the MCData system. IWF-2 supports a subset of the functionality of MCData-SDS-1 and MCData-SDS-2, as defined in 3GPP TS 23.282 [6] with some differences, as specified in the present document. The IWF-2 interface is supported by the same signalling plane protocol(s) as defined for MCData-3 except as specified in the present document. + +### 7.4.3 Reference point IWF-3 (between the IWF and the group management server) + +The IWF-3 reference point, which exists between the IWF and the group management server, provides group management interconnection between an LMR system and the MC system. IWF-3 is based upon CSC-16, as defined in 3GPP TS 23.280 [5] with some differences, as specified in the present document. + +### 7.4.4 Reference point IWF-4 (between the IWF and the LMS) + +The IWF-4 reference point, which exists between the IWF and the LMS, provides location information exchange between an LMR system and the MC system. Support of the IWF-4 reference point is optional, since there is no guarantee that the interworked LMR system can support location information. + +--- + +## 8 Identities + +### 8.1 Identity mapping + +The IWF provides centralised support for interworking between an MCPTT or MCData system and an LMR system. In MCPTT systems, the identity of an LMR user is provided as an MCPTT ID, and the identity of an LMR group is provided as an MCPTT group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system. Similarly, in MCData systems, the identity of an LMR user is provided as an MCData ID, and the identity of an LMR group is provided as an MCData group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system. + +Identities provided on IWF-x reference points are described in clause 8 of 3GPP TS 23.280 [5]. + +The IWF can perform the identity mapping between an MCPTT system or MCData system and an LMR system during exchange of signalling and media messages. + +The assignment of a functional alias that belongs to the MC system to a user homed in the IWF enables the mapping to corresponding role-based addressing schemes applicable in the LMR system. + +--- + +## 9 Application of functional model to deployments + +No applications of functional model to deployments have been identified. + +## 10 Procedures and information flows + +### 10.1 Affiliation + +#### 10.1.1 Information flows for affiliation + +##### 10.1.1.1 General + +The following subclauses define information flows for affiliation on the IWF-1 interface. Affiliation related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5]. + +##### 10.1.1.2 IWF group affiliation request + +Table 10.1.1.2-1 describes the information flow IWF group affiliation request between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.2-1: IWF group affiliation request** + +| Information element | Status | Description | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group affiliation request. (see NOTE) | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system. | +| MC service type | M | The type(s) of service(s) for which the request is intended (e.g. MCData or MCPTT or both) | +| NOTE: | The IWF is configured with an MC service ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. | | + +##### 10.1.1.3 IWF group affiliation response + +Table 10.1.1.3-1 describes the information flow IWF group affiliation response between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.3-1: IWF group affiliation response** + +| Information element | Status | Description | +|--------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggered the MC service group affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system. | +| Affiliation status per MC service group ID | M | Indicates the affiliation result for every MC service group ID in the list. | + +##### 10.1.1.4 IWF group de-affiliation request + +Table 10.1.1.4-1 describes the information flow IWF group de-affiliation request between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.4-1: IWF group de-affiliation request** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group de-affiliation request. (see NOTE) | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | +| MC service type | M | The type(s) of service(s) for which the request is intended (e.g. MCData or MCPTT or both) | +| NOTE: The IWF is configured with an MC service ID for use when the IWF is de-affiliating from the group on behalf of the LMR system. | | | + +### 10.1.1.5 IWF group de-affiliation response + +Table 10.1.1.5-1 describes the information flow IWF group de-affiliation response between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.5-1: IWF group de-affiliation response** + +| Information element | Status | Description | +|-----------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group de-affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | +| De-affiliation status per MC service group ID | M | Indicates the de-affiliation result for every MC service group ID in the list. | + +## 10.1.2 Affiliation procedures + +### 10.1.2.1 General + +When an interworking group is defined in the MCPTT system, the LMR system (via the IWF) informs the MCPTT system of group affiliations in one of the following ways: + +- Every group affiliation in the LMR system results in an affiliation sent to the MCPTT system, which contains the identity (with appropriate translation by the IWF) of the affiliating group member; or +- A group affiliation is sent on behalf of the group's LMR users (via the IWF) to the MCPTT system when the first group member affiliates to the designated group in the LMR system, and a group de-affiliation is sent on behalf of the group's LMR users (via the IWF) to the MCPTT system when the last group member de-affiliates, and no other group affiliation signalling is sent. + +The first and second options may be used at the same time, such that some group members may explicitly affiliate while the IWF may affiliate on behalf of other group members. + +In the second option, when the IWF is configured to affiliate on behalf of the group's LMR members then: + +- a) the group list in the MCPTT system contains the IWF's MCPTT ID. This ID is recognized (through configuration) as having the ability to affiliate on behalf of the group's LMR users associated with this IWF; +- b) the IWF affiliates with its MCPTT ID to the group defined in the MCPTT system; +- c) the MCPTT system recognizes the affiliation as being from an IWF on behalf of the group's LMR users; +- d) when the IWF has affiliated to the group, the MCPTT system: + - i) considers any LMR user associated with the IWF to be affiliated to the group on which the IWF has affiliated. The IWF's users need not be listed ahead of time in the group list for this group in the MCPTT system; + +- ii) allows requests such as call setup or floor request, from MCPTT IDs, with or without functional alias, representing LMR users associated with the IWF for actions on the group to which the IWF has affiliated; + - iii) does not carry out an additional affiliation on behalf of LMR users when those users make call requests, and therefore does not send additional messages to those users (e.g. release messages to both the IWF affiliated identity and the LMR user identity performing the action), via the IWF, during call processing; + - iv) recognizes which LMR users are associated with the IWF because their MCPTT IDs belong to the same system as the IWF; and, + - v) uses special rules for the IWF for limits such as "Limitation of number of affiliations per user (N2)". +- e) requests from LMR users to the MCPTT system are identified with their individual MCPTT IDs (as translated by the IWF): + - i) a user in the LMR system can affiliate on its own (via the IWF) as long as the user is a group member (i.e. in the group list), even if the IWF has affiliated to the group. + - f) the IWF may make requests on behalf of a group's LMR users using the IWF MCPTT ID like a normal group member including, for example, group join requests for groups using the chat model; + - g) the IWF is not allowed to affiliate to a group that is not configured with the IWF's MCPTT ID in the group member list; and, + - h) if the IWF has not affiliated to an MCPTT group, then call requests to this group from LMR users on the system associated with the IWF, can only be accepted if the LMR user's MCPTT ID is in the group list, and has already affiliated. + +MC service group affiliation and de-affiliation can be achieved using explicit or implicit methods as defined in TS 23.280 [5]. When the MC service server uses implicit affiliation/de-affiliation for an interworking group defined in the LMR system, the MC service server informs the IWF of the affiliation/de-affiliation. + +### 10.1.2.2 Group affiliation to a group defined in the MC system + +The LMR system may affiliate its group members to an interworking group defined in the MC system via the IWF. + +For group regroup, the affiliated group members are automatically affiliated to the temporary group. + +The signalling procedure of interworking group affiliation is described in figure 10.1.2.2-1. + +Pre-conditions: + +1. The group to be affiliated to is defined in the MC system. +2. The IWF is connected to and is authorized to interwork with the MC system. +3. The interworking group information is available at the IWF. +4. The mapping relationship of group and user identities between MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Group affiliation to a group defined in the MC system. The diagram shows three participants: IWF, MC services server, and Group management server. The sequence of messages is: 1. IWF group affiliation request (solid arrow from IWF to MC services server); 2a. Subscribe group policy (dashed arrow from MC services server to Group management server); 2b. Notify group policy (dashed arrow from Group management server to MC services server); 3. Authorization check based on group policy (internal message on MC services server); 4. Store the affiliation status (internal message on MC services server); 5. Group affiliation status update (solid arrow from MC services server to Group management server); 6. IWF group affiliation response (solid arrow from MC services server to IWF).](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC as MC services server + participant GMS as Group management server + Note right of MC: 3. Authorization check based on group policy + Note right of MC: 4. Store the affiliation status + IWF->>MC: 1.IWF group affiliation request + MC-->>GMS: 2a.Subscribe group policy + GMS-->>MC: 2b.Notify group policy + MC->>GMS: 5. Group affiliation status update + MC->>IWF: 6. IWF group affiliation response + +``` + +Sequence diagram for Group affiliation to a group defined in the MC system. The diagram shows three participants: IWF, MC services server, and Group management server. The sequence of messages is: 1. IWF group affiliation request (solid arrow from IWF to MC services server); 2a. Subscribe group policy (dashed arrow from MC services server to Group management server); 2b. Notify group policy (dashed arrow from Group management server to MC services server); 3. Authorization check based on group policy (internal message on MC services server); 4. Store the affiliation status (internal message on MC services server); 5. Group affiliation status update (solid arrow from MC services server to Group management server); 6. IWF group affiliation response (solid arrow from MC services server to IWF). + +**Figure 10.1.2.2-1: Group affiliation to a group defined in the MC system** + +1. The IWF sends an IWF group affiliation request to the MC service server on behalf of the LMR system. +- 2a. The MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then the MC service server requests the group policy from the group management server. +- 2b. The MC service server receives the group policy from the group management server. +3. Based on the group policy, the MC service server checks if the MC service group(s) is not disabled and if the user identified by the MCPTT ID supplied by the IWF is authorised to affiliate to the requested MC service group(s). +4. Based on the group policy and user subscription, the MC service server affiliates the IWF to the group. If a separate affiliation for each LMR user is expected, the status of the affiliating user is stored by the MC service server as the status associated with an MC service ID provided by the IWF that corresponds to the identity of that LMR user. If a separate affiliation for each LMR user is not expected, an affiliation status for the group using the MC service ID provided by the IWF is stored. +5. The MCPTT server sends the group affiliation status update message to the group management server, the group management server stores and updates the group affiliation status. +6. The MC service server returns an IWF group affiliation response to the IWF. + +NOTE 2: How the LMR user(s) affiliates to a group is outside the scope of the present document. + +### 10.1.2.3 Group de-affiliation from a group defined in the MC system + +The signalling procedure of interworking group de-affiliation from a group defined in the MC system is described in figure 10.1.2.3-1. + +The LMR system manages the individual de-affiliation requests from the LMR users. The LMR system can de-affiliate its group members from the interworking group via the IWF. + +Pre-conditions: + +1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. +2. The affiliation procedure described in subclause 10.1.2.2 was previously performed. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Group de-affiliation from group defined in the MC system. The diagram shows four steps: 1. IWF sends an IWF group de-affiliation request to the MC service server. 2. The MC service server stores the affiliation status. 3. The MC service server sends a group de-affiliation status update to the Group management server. 4. The MC service server returns an IWF group de-affiliation response to the IWF.](5445597cceefaca1ac89e710fe339325_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC service server + participant Group management server + Note right of MC service server: 2. Store the affiliation status + IWF->>MC service server: 1. IWF group de-affiliation request + MC service server->>Group management server: 3. Group de-affiliation status update + MC service server-->>IWF: 4. IWF group de-affiliation response + +``` + +Sequence diagram for Group de-affiliation from group defined in the MC system. The diagram shows four steps: 1. IWF sends an IWF group de-affiliation request to the MC service server. 2. The MC service server stores the affiliation status. 3. The MC service server sends a group de-affiliation status update to the Group management server. 4. The MC service server returns an IWF group de-affiliation response to the IWF. + +**Figure 10.1.2.3-1: Group de-affiliation from group defined in the MC system** + +1. The IWF sends an IWF group de-affiliation request to the MC service server on behalf of the LMR system. +2. If a separate de-affiliation from each LMR user is expected and based on the group policy and user subscription, the MC service server may de-affiliate the LMR group member from the group. Further, the MC service server may store the affiliation status of the user(s) for the requested MC service group(s). If a separate de-affiliation from each LMR user is not expected, the de-affiliation signalling de-affiliates the IWF and therefore the entire LMR system from the group. +3. The MC service server sends the group de-affiliation status update message to the group management server, the group management server stores and updates the group affiliation status. +4. The MC service server returns an IWF group de-affiliation response to the IWF. + +NOTE 2: How the LMR user(s) de-affiliate from a group is outside the scope of the present document. + +#### 10.1.2.4 Group affiliation to group defined in the LMR system + +The MC system may affiliate its group members to an interworking group defined in the LMR system via the IWF. + +The signalling procedure of group affiliation via the IWF is described in figure 10.1.2.4-1. + +Pre-conditions: + +1. The group to be affiliated to is defined in the LMR system. +2. The IWF is connected to and is authorized to work with the MC system. +3. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for group affiliation to a group defined in the LMR system. The diagram shows three lifelines: MC service client, MC service server, and IWF. The sequence of messages is: 1. MC service group affiliation request from client to server; 2. Resolve group ID (internal server message); 3. IWF group affiliation request from server to IWF; 4. IWF group affiliation response from IWF to server; 5. Store affiliation status (internal server message); 6. MC service group affiliation response from server to client.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant MC service server + participant IWF + Note right of MC service server: 2. Resolve group ID + Note right of MC service server: 5. Store affiliation status + MC service client->>MC service server: 1. MC service group affiliation request + MC service server->>IWF: 3. IWF group affiliation request + IWF-->>MC service server: 4. IWF group affiliation response + MC service server-->>MC service client: 6. MC service group affiliation response + +``` + +Sequence diagram for group affiliation to a group defined in the LMR system. The diagram shows three lifelines: MC service client, MC service server, and IWF. The sequence of messages is: 1. MC service group affiliation request from client to server; 2. Resolve group ID (internal server message); 3. IWF group affiliation request from server to IWF; 4. IWF group affiliation response from IWF to server; 5. Store affiliation status (internal server message); 6. MC service group affiliation response from server to client. + +**Figure 10.1.2.4-1: Group affiliation to group defined in the LMR system** + +1. The MC service client sends a MC service group affiliation request, including the MC service group ID(s), to the MC service server. +2. The MC service server checks if the MC service group ID(s) is an interworking group defined in the LMR system. +3. The MC service server sends an IWF group affiliation request to the IWF. + +NOTE 2: The IWF can forward the request to the LMR system that could check whether the MC service client is authorized to affiliate to this interworking group. + +NOTE 3: The IWF can reject the affiliation if the MC service group ID is either unknown to the IWF or not mapped to an LMR group identity in the IWF configuration. + +4. The IWF returns an IWF group affiliation response to the MC service server, informing the successful affiliation to the LMR group. +5. The MC service server stores the group affiliation status of the MC service client for the requested interworking group. +6. The MC service server sends an MC service group affiliation response to the MC service client. + +NOTE 4: How the affiliation is conducted on the LMR system is outside the scope of the present document. + +NOTE 5: If an MC service client is implicitly affiliated to an MC service group defined in the LMR system the MC service server only performs steps 3, 4, and 5. + +### 10.1.2.5 Group de-affiliation from a group defined in the LMR system + +The signalling procedure of interworking group de-affiliation from a group defined in the LMR system is described in figure 10.1.2.5-1. + +The MC system manages the individual de-affiliation requests from the MC service users. The MC system may de-affiliate its group members from the interworking group via the IWF. + +Pre-conditions: + +1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. +2. The affiliation procedure described in subclause 10.1.2.4 was previously performed. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Group de-affiliation from a group defined in the LMR system. The diagram shows three lifelines: MC service client, MC service server, and IWF. The sequence of messages is: 1. MC service group de-affiliation request from client to server; 2. Authorization check based on group policy and user subscription (internal to server); 3a. IWF group de-affiliation request from server to IWF; 3b. IWF group de-affiliation response from IWF to server; 4. Update the MCPTT group affiliation status (internal to server); 5. MC service group de-affiliation response from server to client.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant MC service server + participant IWF + Note right of MC service server: 2. Authorization check based on group policy and user subscription + MC service client->>MC service server: 1. MC service group de-affiliation request + MC service server->>IWF: 3a. IWF group de-affiliation request + IWF-->>MC service server: 3b. IWF group de-affiliation response + Note right of MC service server: 4. Update the MCPTT group affiliation status + MC service server-->>MC service client: 5. MC service group de-affiliation response + +``` + +Sequence diagram for Group de-affiliation from a group defined in the LMR system. The diagram shows three lifelines: MC service client, MC service server, and IWF. The sequence of messages is: 1. MC service group de-affiliation request from client to server; 2. Authorization check based on group policy and user subscription (internal to server); 3a. IWF group de-affiliation request from server to IWF; 3b. IWF group de-affiliation response from IWF to server; 4. Update the MCPTT group affiliation status (internal to server); 5. MC service group de-affiliation response from server to client. + +**Figure 10.1.2.5-1: Group de-affiliation from a group defined in the LMR system** + +1. The MC service client of the MC service user sends an MC service group de-affiliation request to the MC service server. The MC service client shall provide the initiating MC service ID and the MC service group ID(s) being de-affiliated from. +2. Based on the user subscription and stored group policy, the MC service server checks if the user of the MC service client is affiliated to the requested MC service group(s). The MC service server checks if the MC service group(s) is an interworking group. +- 3a. If the MC service group(s) is an interworking group, the MC service server sends an IWF group de-affiliation request to the IWF. +- 3b. The IWF returns an IWF group de-affiliation response to the MC service server. +4. If the user of the MC service client is authorized to de-affiliate from the requested MC service group(s), the MC service server removes the affiliation status of the user for the requested MC service group(s). +5. The MC service server returns an MC service group de-affiliation response to the MC service client. + +NOTE 2: If an MC service client is implicitly de-affiliated from an MC service group defined in the LMR system the MC service server only performs steps 3a, 3b, and 4. + +## 10.2 Group management + +### 10.2.1 Information flows for group management + +#### 10.2.1.1 General + +The following subclauses define information flows for group management on the IWF-1 interface. Group management related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5]. + +#### 10.2.1.2 IWF group regroup teardown notification + +Table 10.2.1.2-1 describes the information flow IWF group regroup teardown notification between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.2-1: IWF group regroup teardown notification** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which is torn down | + +#### 10.2.1.3 IWF group regroup teardown notification response + +Table 10.2.1.3-1 describes the information flow IWF group regroup teardown notification response between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.3-1: IWF group regroup teardown notification response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which was torn down | +| Result | M | Indicates success or failure of the notification | + +#### 10.2.1.4 IWF group regroup request + +Table 10.2.1.4-1 describes the information flow IWF group regroup request between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.4-1: IWF group regroup request** + +| Information element | Status | Description | +|--------------------------|--------|------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | + +#### 10.2.1.5 IWF group regroup response + +Table 10.2.1.5-1 describes the information flow IWF group regroup response between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.5-1: IWF group regroup response** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------| +| MC service group ID | O (see NOTE) | MC service group ID of the temporary group | +| MC service group ID list | M | List of constituent MC service group IDs. | +| Result | M | Indicates whether the IWF group regroup was accepted or rejected. | +| NOTE: Shall be present if the Result information element indicates that the group regroup operation is successful. Otherwise MC service group ID shall not be present. | | | + +### 10.2.1.6 IWF group regroup notification + +Table 10.2.1.6-1 describes the information flow IWF group regroup notification between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.6-1: IWF group regroup notification** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| Priority level | O | Required priority level for the temporary group | +| Security level (see NOTE) | O | Required security level for the temporary group | +| NOTE: Security level refers to the configuration of media and floor control protection parameters as listed in 3GPP TS 23.280 [5] | | | + +### 10.2.1.7 IWF group regroup notification response + +Table 10.2.1.7-1 describes the information flow IWF group regroup notification response between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.7-1: IWF group regroup notification response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| Priority level | M | Required priority level for the temporary group | +| Security level | M | Required security level for the temporary group | + +### 10.2.1.8 IWF group information request + +Table 10.2.1.8-1 describes the IWF group information request from the IWF to the group management server or from the group management server to the IWF. + +**Table 10.2.1.8-1: IWF group information request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------| +| MC service group ID | M | The identity of the MC service group. | + +### 10.2.1.9 IWF group information response + +Table 10.2.1.9-1 describes the IWF group information response from the group management server to the IWF or the IWF to the group management server. + +**Table 10.2.1.9-1: IWF group information response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The identity of the MC service group. | +| MC service group provisioning information | O (see NOTE 1) | The group information retrieved from the group management server or from the IWF in the case where the IWF is performing the provision. | +| Result | O (see NOTE 2) | Indicates reason for failure to provide MC service group configuration information | +| NOTE 1: Shall be present if the request can be fulfilled.
NOTE 2: Shall be present if the request cannot be fulfilled. | | | + +### 10.2.1.10 IWF group information provision request + +Table 10.2.1.10-1 describes the IWF group information provision request from the group management server to the IWF or the IWF to the group management server. + +**Table 10.2.1.10-1: IWF group information provision request** + +| Information element | Status | Description | +|---------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The identity of the MC service group. | +| MCPTT group configuration information | M | The group information retrieved from the group management server or from the IWF in the case where the group is defined in the IWF. | + +#### 10.2.1.11 IWF group information provision response + +Table 10.2.1.11-1 describes the IWF group information provision response from the IWF to the group management server or from the group management server to the IWF. + +**Table 10.2.1.11-1: IWF group information provision response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The identity of the MC service group. | +| Result | M | Indicates success or failure of reception, modification and storage of MC service group configuration information | + +#### 10.2.1.12 IWF group information subscribe request + +Table 10.2.1.12-1 describes the information flow IWF group information subscribe request from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases where the IWF is the primary system of the group. + +**Table 10.2.1.12-1: IWF group information subscribe request** + +| Information element | Status | Description | +|-----------------------|--------|-------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC services requested | O | Service(s) for which group configuration is requested; one or more of MCPTT, MCData | + +#### 10.2.1.13 IWF group information subscribe response + +Table 10.2.1.13-1 describes the information flow IWF group information subscribe response from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group. + +**Table 10.2.1.13-1: IWF group information subscribe response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of the subscribe request | + +#### 10.2.1.14 IWF group information notify request + +Table 10.2.1.14-1 describes the information flow IWF group information notify request from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group. + +**Table 10.2.1.14-1: IWF group information notify request** + +| Information element | Status | Description | +|--------------------------------------------------------------------|--------|------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group information reference (see NOTE) | O | Reference to information stored relating to the MC service group | +| Group related key material (see NOTE) | O | Key material for use with the MC service group | +| NOTE: At least one of these information elements shall be present. | | | + +## 10.2.1.15 IWF group information notify response + +Table 10.2.1.15-1 describes the information flow IWF group information notify response from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases where the IWF is the primary system of the group. + +**Table 10.2.1.15-1: IWF group information notify response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of the notification request | + +## 10.2.2 Group regrouping + +### 10.2.2.1 General + +The procedures in 3GPP TS 23.280 [5] are followed, but with changes required for interworking. The IWF will behave on the interface as if it is a peer MC service server with a peer group management client and peer group management server. + +Exceptions to the 3GPP TS 23.280 [5] procedures are detailed in the subclauses below. + +### 10.2.2.2 MC system initiates the group regroup + +The MC system can initiate a group regroup that includes groups defined at the IWF. The IWF is informed and may reject the regroup if conditions do not allow it to support the regroup. This is described in figure 10.2.2.2-1. + +Pre-conditions: + +1. The group management client has retrieved the group configurations of the groups to be regrouped. +2. At least one MC service group has been defined in the MC system. +3. At least one MC service group has been defined in the IWF. + +![Sequence diagram for Group regrouping to an IWF. Lifelines: Group management client, Group management server, Group management client (other group members), MC service server, IWF. The sequence shows 11 steps: 1. Group regroup request from client to server; 2. Authorization check on server; 3. IWF group regroup request from server to IWF; 4. IWF group regroup response from IWF to server; 5. Create and store temporary group related information on server; 6. IWF group regroup notification from server to IWF; 7. IWF group regroup notification response from IWF to server; 8. Group regroup notify from server to MC service server; 9. Group regroup notify response from MC service server to server; 10. Notify the group members on server; 11. Group regroup response from server to client.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) + +``` + +sequenceDiagram + participant GMC as Group management client + participant GMS as Group management server + participant GCM as Group management client (other group members) + participant MSS as MC service server + participant IWF as IWF + + Note right of GMS: 2. Authorization check based on group policy and check whether group is a temporary group + Note right of GMS: 5. Create and store temporary group related information + Note right of GMS: 10. Notify the group members + + GMC->>GMS: 1. Group regroup request + GMS->>IWF: 3. IWF group regroup request + IWF-->>GMS: 4. IWF group regroup response + GMS->>IWF: 6. IWF group regroup notification + IWF-->>GMS: 7. IWF group regroup notification response + GMS->>MSS: 8. Group regroup notify + MSS-->>GMS: 9. Group regroup notify response + GMS-->>GMC: 11. Group regroup response + +``` + +Sequence diagram for Group regrouping to an IWF. Lifelines: Group management client, Group management server, Group management client (other group members), MC service server, IWF. The sequence shows 11 steps: 1. Group regroup request from client to server; 2. Authorization check on server; 3. IWF group regroup request from server to IWF; 4. IWF group regroup response from IWF to server; 5. Create and store temporary group related information on server; 6. IWF group regroup notification from server to IWF; 7. IWF group regroup notification response from IWF to server; 8. Group regroup notify from server to MC service server; 9. Group regroup notify response from MC service server to server; 10. Notify the group members on server; 11. Group regroup response from server to client. + +**Figure 10.2.2.2-1: Group regrouping to an IWF** + +1. The group management client of the MC service user (e.g. dispatcher) requests group regroup operation to the group management server (which is the group management server of one of the MC service groups to be regrouped). The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group. +2. The group management server checks whether group regroup operation is performed by an authorised MC service user, based on group policy. The group management server checks whether the group is a temporary group. If the group is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed. +3. The group management server forwards the IWF group regroup request to the IWF with the information about the IWF's groups. +4. The IWF provides an IWF group regroup response. Due to security aspects concerning sharing information among different MC systems, the IWF does not share the users' information of the groups under its management to the group management server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping) +5. The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, off-network information, and the MC service IDs of the groups being combined, the priority level of the temporary group, and the security level of the temporary group. If the + +authorised MC service user does not specify the security level and the priority level, the group management server shall set the lower security level and the higher priority of the constituent groups. + +6. The group management server notifies the IWF about its group regroup operation. + +NOTE: How the IWF uses the MC service group ID that identifies the temporary group is outside the scope of the present document. + +7. The IWF acknowledges the group management server. +8. The group management server notifies the MC service server of the temporary group creation with the information of the constituent groups. +9. The MC service server acknowledges the notification from the group management server. +10. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of lower security level. +11. The group management server provides a group regroup response to the group management client of the authorised MC service user (e.g. dispatcher). + +### 10.2.2.3 IWF initiates the group regroup + +The procedure in 3GPP TS 23.280 [5] is followed, except for steps 1 and 2. The IWF will behave on the interface as if it is a peer MC service server with a peer group management server. This is described in figure 10.2.2.3-1. + +Pre-conditions: + +1. At least one MC service group has been defined in the MC system. +2. At least one MC service group has been defined in the IWF. + +![Sequence diagram for Group regrouping from an IWF. Lifelines: IWF, Group management server, Group management client, MC service server. The sequence starts with the IWF sending a request to the Group management server. The server checks the group status and responds. The IWF then sends a notification to the server, which in turn notifies the MC service server. The MC service server responds, and the server sends a notification response back to the IWF. Finally, the server notifies the group members.](7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant GMS as Group management server + participant GMC as Group management client + participant MSS as MC service server + + Note right of GMS: 2. Check group status + IWF->>GMS: 1. IWF group regroup request + GMS-->>IWF: 3. IWF group regroup response + IWF->>GMS: 4. IWF group regroup notification + GMS->>MSS: 5. Group regroup notify + MSS-->>GMS: 6. Group regroup notify response + GMS-->>IWF: 7. IWF group regroup notification response + Note right of GMS: 8. Notify the group members + +``` + +Sequence diagram for Group regrouping from an IWF. Lifelines: IWF, Group management server, Group management client, MC service server. The sequence starts with the IWF sending a request to the Group management server. The server checks the group status and responds. The IWF then sends a notification to the server, which in turn notifies the MC service server. The MC service server responds, and the server sends a notification response back to the IWF. Finally, the server notifies the group members. + +Figure 10.2.2.3-1: Group regrouping from an IWF + +1. The IWF sends an IWF group regroup request to the group management server. + +2. The group management server checks whether the group can be included in a temporary group. + 3. The group management server provides an IWF group regroup response. +- NOTE: Due to security aspects concerning sharing information among different systems, the group management server does not share the users' information of the groups under its management to the IWF. +4. The IWF notifies the group management server regarding the temporary group creation with information of the constituent groups. + 5. The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups. + 6. The MC service server acknowledges the notification from the group management server. The MC service server may reject the IWF group regroup, e.g. if one of its constituent groups is already in a regroup. + 7. The group management server acknowledges the notification from the IWF. + 8. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of a lower security level. + +#### 10.2.2.4 Ownership of the group regroup + +The group management server that performs the group regroup operation owns the temporary group created by the regroup, as implied in 3GPP TS 23.280 [5]. + +#### 10.2.2.5 Simultaneous group regroup requests from each side of the IWF-1 interface + +To prevent routing issues and complexity that could result from regrouping the same users from both sides of the interface, the following rules can be applied: + +- If group regrouping signalling using temporary groups is used on the MC system, the IWF must prevent the regroup signalling from propagating to the LMR system if the LMR system does not support regrouping; +- the IWF must handle the translation between temporary group identities on the MC system and the original interworking group identities used on the LMR system; and +- the regrouping rules in subclause 10.2.4.4 of 3GPP TS 23.280 [5] also apply. + +#### 10.2.2.6 Resolution of vocoder and encryption mode for the group regroup + +If one of the LMR groups to be included in a group regroup requires the use of LMR E2EE the preferred voice codecs for an MCPTT temporary group should be LMR codecs. If any of the mission critical users to be included in this MCPTT temporary group do not support LMR E2EE or the preferred LMR codecs, voice calls using LMR E2EE will fail for those users. + +NOTE 1: How the MC system determines that the temporary group needs to support LMR E2EE is outside the scope of the present document. + +NOTE 2: How the MC system determines that the temporary group needs to support an LMR codec is outside the scope of the present document. + +### 10.2.3 Group configuration for interworking + +#### 10.2.3.1 Overview + +The procedures in the following subclauses describe the process for sharing group configuration from an MC system to an IWF where the IWF needs to make use of the MC service group and from an IWF to an MC system where the MC system's clients need to make use of the group. The procedures in this subclause are based upon subclause 10.2.7 in 3GPP TS 23.280 [5]. + +### 10.2.3.2 MC system provides group configuration to the IWF + +Figure 10.2.3.2-1 below illustrates the case where the MC system provides the group configuration to the IWF, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the IWF. + +Pre-conditions: + +1. The MC service group is defined in the MC system. +2. One or more LMR users are members of the group. +3. The MC system of the MC service group has been configured with addressing information for the group management function in the IWF. +4. The MC system of the MC service group is authorized to provide group configuration information to the IWF. + +NOTE: The MC system of the MC service group could be configured with an address of the IWF which is a proxy address. + +![Sequence diagram showing the MC system providing group configuration to the IWF. The diagram is titled 'Primary MC system of group' and contains two main components: 'Group management server' and 'IWF'. The sequence of messages is: 1. IWF group Information provision request (from IWF to Group management server) and 2. IWF group information Provision response (from Group management server to IWF).](24c9e038a791677ed33100667b64f7e6_img.jpg) + +``` +sequenceDiagram + participant IWF + participant GMS as Group management server + Note over GMS: Primary MC system of group + IWF->>GMS: 1. IWF group Information provision request + GMS-->>IWF: 2. IWF group information Provision response +``` + +Sequence diagram showing the MC system providing group configuration to the IWF. The diagram is titled 'Primary MC system of group' and contains two main components: 'Group management server' and 'IWF'. The sequence of messages is: 1. IWF group Information provision request (from IWF to Group management server) and 2. IWF group information Provision response (from Group management server to IWF). + +**Figure 10.2.3.2-1: MC system provides group configuration to the IWF** + +1. The group management server in the MC system of the MC service group provides the configuration information related to the MC service group to the IWF. +2. The IWF responds to the group management server of the MC system of the MC service group that the configuration has been received and stored correctly. + +### 10.2.3.3 IWF requests group configuration from the MC system + +Figure 10.2.3.3-1 below illustrates the case where the IWF requests the group configuration from the MC system, for example because a user on the IWF is a member of the group. + +Pre-conditions: + +1. The MC service group is defined in the MC system. +2. One or more LMR users are members of the group. +3. The IWF does not have the configuration for the MC service group stored. + +![Sequence diagram for Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system. The diagram shows two lifelines: IWF and Primary MC system of group (containing Group management server). The IWF sends a '1. IWF group information request' to the Group management server, which responds with '2. IWF group information response'.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant Primary MC system of group + Note right of Primary MC system of group: Group management server + IWF->>Primary MC system of group: 1. IWF group information request + Primary MC system of group-->>IWF: 2. IWF group information response + +``` + +Sequence diagram for Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system. The diagram shows two lifelines: IWF and Primary MC system of group (containing Group management server). The IWF sends a '1. IWF group information request' to the Group management server, which responds with '2. IWF group information response'. + +**Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system** + +1. The IWF requests the group configuration from the group management server in the primary MC system of the MC service group. +2. The group management server in the MC system of the MC service group provides the requested group configuration information. + +#### 10.2.3.4 IWF provides group configuration to the MC system + +Figure 10.2.3.4-1 below illustrates the case where the IWF provides the group configuration to the MC system, e.g. due to an action by an administrator or because some of the IWF's MC service group members are homed on the MC system. + +Pre-conditions: + +1. The group is defined in the IWF. +2. One or more MC service users are members of the group. + +NOTE: The group management server within the MC system is responsible for providing group configuration information to group members for whom the MC system is their serving MC system. + +![Sequence diagram for Figure 10.2.3.4-1: MC system provides group configuration to the IWF. The diagram shows two lifelines: Primary system of group (containing IWF) and Group management server. The IWF sends a '1. IWF group Information provision request' to the Group management server, which responds with '2. IWF group Information provision response'.](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +``` + +sequenceDiagram + participant Primary system of group + Note left of Primary system of group: IWF + participant Group management server + IWF->>Group management server: 1. IWF group Information provision request + Group management server-->>IWF: 2. IWF group Information provision response + +``` + +Sequence diagram for Figure 10.2.3.4-1: MC system provides group configuration to the IWF. The diagram shows two lifelines: Primary system of group (containing IWF) and Group management server. The IWF sends a '1. IWF group Information provision request' to the Group management server, which responds with '2. IWF group Information provision response'. + +**Figure 10.2.3.4-1: MC system provides group configuration to the IWF** + +1. The IWF provides the configuration information related to the group to the group management server in the MC system. +2. The group management server in the MC system responds to the IWF that the configuration has been received and stored correctly. + +### 10.2.3.5 MC system requests group configuration from the IWF + +Figure 10.2.3.5-1 below illustrates the case where the MC system requests the group configuration from the IWF, for example because an MC service user receiving service in the MC system has the group configured in the user profile. + +Pre-conditions: + +1. The MC service group is defined in the IWF. +2. One or more MC service users are members of the group. +3. The group management server in the MC system does not have the configuration for the MC service group stored. +4. The MC system has been configured with addressing information for the group management function in the IWF. + +NOTE: The group management server within the MC system is responsible for providing group configuration information to MC service group members for whom the MC system is their serving MC system. + +![Sequence diagram showing the MC system requesting group configuration from the IWF.](94fd137860c16c8dfd75512f10161fe8_img.jpg) + +``` +sequenceDiagram + participant GMS as Group management server + subgraph PS [Primary system of group] + participant IWF + end + GMS->>IWF: 1. IWF group Information provision request + IWF-->>GMS: 2. IWF group Information provision response +``` + +The diagram illustrates a sequence of interactions between a 'Group management server' and an 'IWF' (Interworking Function). The 'IWF' is part of the 'Primary system of group'. The sequence starts with the 'Group management server' sending a '1. IWF group Information provision request' to the 'IWF'. The 'IWF' then responds with a '2. IWF group Information provision response' back to the 'Group management server'. + +Sequence diagram showing the MC system requesting group configuration from the IWF. + +**Figure 10.2.3.5-1: Partner MC system requests group configuration from primary MC system** + +1. The MC system requests the group configuration from the group management function in the IWF. +2. The IWF provides the requested group configuration information. + +### 10.2.3.6 IWF subscribes to group configuration + +The procedure for subscription from IWF for group configuration information to the group management server in the primary MC system of the MC service group is shown in figure 10.2.3.6-1. + +Pre-conditions: + +1. The MC service group is defined in its MC system. +2. One or more group members are defined in the LMR system. +3. The IWF has received group information from the GMS in the primary MC system of the MC service group. + +![Sequence diagram showing subscription from IWF to Group management server.](318886a86a1dcc59e1fc83db6f157c60_img.jpg) + +``` +sequenceDiagram + participant IWF + participant GMS as Group management server + Note left of IWF: IWF + Note right of GMS: Group management server + IWF->>GMS: 1. IWF group information subscribe request + GMS-->>IWF: 2. IWF group information subscribe response +``` + +A sequence diagram illustrating the subscription process. On the left is a box labeled 'IWF'. On the right is a box labeled 'Group management server'. A solid arrow points from the IWF box to the Group management server box, labeled '1. IWF group information subscribe request'. A dashed arrow points from the Group management server box back to the IWF box, labeled '2. IWF group information subscribe response'. + +Sequence diagram showing subscription from IWF to Group management server. + +**Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration** + +1. The IWF subscribes to the group configuration information stored in the group management server in the primary MC system of the MC service group. +2. The group management server in the primary MC system of the MC service group sends an IWF group information subscribe response to IWF indicating success or failure of the request. + +### 10.2.3.7 MC system notifies group configuration + +The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the IWF is shown in figure 10.2.3.7-1. + +Pre-conditions: + +1. The IWF has subscribed to the group configuration information for the MC service group in the group management server in the primary MC system of the MC service group. +2. The group management server in the primary MC system of the MC service group has received and stored new group configuration information for the MC service group. + +![Sequence diagram showing notification from Group management server to IWF.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +``` +sequenceDiagram + participant GMS as Group management server + participant IWF + Note left of GMS: Group management server + Note right of IWF: IWF + GMS->>IWF: 1. IWF group information notify request + IWF-->>GMS: 2. IWF group information notify response +``` + +A sequence diagram illustrating the notification process. On the left is a box labeled 'Group management server'. On the right is a box labeled 'IWF'. A solid arrow points from the Group management server box to the IWF box, labeled '1. IWF group information notify request'. A dashed arrow points from the IWF box back to the Group management server box, labeled '2. IWF group information notify response'. + +Sequence diagram showing notification from Group management server to IWF. + +**Figure 10.2.3.7-1: Notification of group configuration information to the IWF** + +1. The group management server in the primary MC system of the MC service group sends an IWF group information notify request to the IWF. +2. The IWF sends an IWF group information notify response to the group management server in the primary MC system of the MC service group indicating the success or failure of the notification. + +### 10.2.3.8 MC system subscribes to group configuration + +The procedure for subscription by the group management server in the MC system to the IWF for group configuration information is shown in figure 10.2.3.8-1. + +Pre-conditions: + +1. The group is defined in the LMR system. + +2. One or more group members are defined in the MC system. +3. The group management server in the MC system has received group information from the IWF. + +![Sequence diagram for Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration. The diagram shows two lifelines: 'Group management server' on the left and 'IWF' on the right. A solid arrow labeled '1. IWF group information subscribe request' points from the Group management server to the IWF. A dashed arrow labeled '2. IWF group information subscribe response' points from the IWF back to the Group management server.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` +sequenceDiagram + participant Group management server + participant IWF + Note left of Group management server: 1. IWF group information subscribe request + Group management server->>IWF: 1. IWF group information subscribe request + Note right of IWF: 2. IWF group information subscribe response + IWF-->>Group management server: 2. IWF group information subscribe response +``` + +Sequence diagram for Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration. The diagram shows two lifelines: 'Group management server' on the left and 'IWF' on the right. A solid arrow labeled '1. IWF group information subscribe request' points from the Group management server to the IWF. A dashed arrow labeled '2. IWF group information subscribe response' points from the IWF back to the Group management server. + +**Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration** + +1. The group management server of the MC system subscribes to the group configuration information stored in the IWF. +2. The IWF provides an IWF group information subscribe response to group management server of the MC system indicating success or failure of the request. + +### 10.2.3.9 IWF notifies group configuration + +The procedure for notification of group information from the IWF to the group management server in the MC system is shown in figure 10.2.3.9-1. + +Pre-conditions: + +1. The group management server of the MC system has subscribed to the group configuration information for the group in the IWF. +2. The IWF has new information for the group. + +![Sequence diagram for Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group. The diagram shows two lifelines: 'IWF' on the left and 'Group management server' on the right. A solid arrow labeled '1. IWF group information notify request' points from the IWF to the Group management server. A dashed arrow labeled '2. IWF group information notify response' points from the Group management server back to the IWF.](f732d3320afe06d979aabbd366184254_img.jpg) + +``` +sequenceDiagram + participant IWF + participant Group management server + Note left of IWF: 1. IWF group information notify request + IWF->>Group management server: 1. IWF group information notify request + Note right of Group management server: 2. IWF group information notify response + Group management server-->>IWF: 2. IWF group information notify response +``` + +Sequence diagram for Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group. The diagram shows two lifelines: 'IWF' on the left and 'Group management server' on the right. A solid arrow labeled '1. IWF group information notify request' points from the IWF to the Group management server. A dashed arrow labeled '2. IWF group information notify response' points from the Group management server back to the IWF. + +**Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group** + +1. The IWF sends an IWF group information notify request to the group management server in the MC system. +2. The group management server in the MC system sends an IWF notify group information notify response to the IWF indicating the success or failure of the notification. + +## 10.3 Group call + +### 10.3.1 General + +The following subclauses define information flows and signaling procedures for group calls and broadcast group calls. + +Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF group call request / IWF group call release request message is sent to the IWF at the commencement / release of a group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document. + +Where the group is defined in the LMR system, the IWF shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. + +### 10.3.2 Information flows for group call over interworking group + +#### 10.3.2.1 General + +The following subclauses define information flows for group calls on the IWF-1 interface. Group call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7]. + +#### 10.3.2.2 IWF group call request + +Table 10.3.2.2-1 describes the information flow IWF group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.2-1: IWF group call request information elements** + +| Information Element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID
(see NOTE 1) | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the interworking group on which the call is initiated | +| SDP offer | M | Media parameters of MCPTT server | +| Implicit floor request
(see NOTE 2) | O | Indicates that the originator requests the floor. | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Location | O | Location of the calling party | +| NOTE 1: If the LMR system does not provide the calling party identity when the group call is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for LMR user at the IWF. | | | +| NOTE 2: This element shall be included only when the originating client requests the floor. | | | + +#### 10.3.2.3 IWF group call response (IWF – MCPTT server) + +Table 10.3.2.3-1 describes the information flow IWF group call response from the MCPTT server to the IWF and from the IWF to MCPTT server. + +**Table 10.3.2.3-1: IWF group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | + +### 10.3.2.4 IWF Group-broadcast group call setup request + +Table 10.3.2.4-1 describes the information flow IWF group-broadcast group call setup request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.4-1: IWF Group-broadcast group call setup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| +| MCPTT ID (see NOTE 1) | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Implicit floor request (see NOTE 2) | O | Indicates that the originating client requests the floor | +| Location | O | Location of the calling party | +| NOTE 1: If the LMR system does not provide the calling party identity when the group-broadcast group call setup request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF. | | | +| NOTE 2: This element shall be included only when the originating client requests the floor. | | | + +### 10.3.2.5 IWF Group-broadcast group call setup response + +Table 10.3.2.5-1 describes the information flow IWF group-broadcast group call setup response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.5-1: IWF Group-broadcast group call setup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | + +### 10.3.2.6 IWF Group-broadcast group call release request + +Table 10.3.2.6-1 describes the information flow IWF group-broadcast group call release request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.6-1: IWF Group-broadcast group call release request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------| +| MCPTT ID | M (see NOTE) | The MCPTT ID of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | +| NOTE: If the LMR system does not provide the calling party identity when the group-broadcast group call release request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF. | | | + +### 10.3.2.7 IWF group-broadcast group call release response + +Table 10.3.2.7-1 describes the information flow IWF group-broadcast group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.7-1: IWF Group-broadcast group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +### 10.3.2.8 IWF group join request + +Table 10.3.2.8-1 describes the information flow IWF group join request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.8-1: IWF group join request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the originator of the request. (see NOTE 1) | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP offer | M | Media parameters of originator | +| Implicit floor request (see NOTE 2) | O | Indicates that the originating client requests the floor. | +| NOTE 1: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. | | | +| NOTE 2: This element is included only when the originating client requests the floor. | | | + +### 10.3.2.9 IWF group join response + +Table 10.3.2.9-1 describes the information flow group join response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.9-1: IWF group join response information elements** + +| Information Element | Status | Description | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the originator of the request. (see NOTE) | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP answer | M | Media parameters selected | +| NOTE: | The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. | | + +### 10.3.2.10 IWF group call leave request + +Table 10.3.2.10-1 describes the information flow IWF group call leave request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.10-1: IWF group call leave request information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group from which the user is leaving | + +### 10.3.2.11 IWF group call leave response + +Table 10.3.2.11-1 describes the information flow IWF group call leave response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.11-1: IWF group call leave response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group from which the user is leaving | + +### 10.3.2.12 IWF group call release request + +Table 10.3.2.12-1 describes the information flow IWF group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.12-1: IWF group call release request information elements** + +| Information element | Status | Description | +|---------------------|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| MCPTT ID (see NOTE) | O | The MCPTT ID of the initiating MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | +| Release reason | O | The reason why the call is released | +| NOTE: | This IE is not included if the group call release is initiated by the server (e.g. due to timeout) | | + +### 10.3.2.13 IWF group call release response + +Table 10.3.2.13-1 describes the information flow IWF group call release response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.13-1: IWF group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released. | + +### 10.3.2.14 IWF pre-configured regroup request + +Table 10.3.2.14-1 describes the information flow IWF pre-configured regroup request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.14-1 IWF pre-configured regroup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------|-----------------|------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| MCPTT group ID | M | MCPTT group ID of the MCPTT group from which configuration is to be taken | +| MCPTT group ID list | O
(see NOTE) | List of MCPTT groups to be regrouped into the pre-configured regroup group | +| MCPTT ID list | O
(see NOTE) | List of MCPTT IDs to be regrouped into the pre-configured user regroup group | +| NOTE: One and only one of these shall be present. | | | + +### 10.3.2.15 IWF pre-configured regroup response + +Table 10.3.2.15-1 describes the information flow IWF pre-configured regroup response from IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.15-1 IWF pre-configured regroup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regrouping operation | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +### 10.3.2.16 IWF pre-configured regroup cancel request + +Table 10.3.2.16-1 describes the information flow pre-configured regroup cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.16-1 IWF pre-configured regroup cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | + +### 10.3.2.17 IWF pre-configured regroup cancel response + +Table 10.3.2.17-1 describes the information flow IWF pre-configured regroup cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.17-1 IWF pre-configured regroup cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regroup removal | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regroup removal operation | + +### 10.3.2.18 IWF pre-configured regroup reject (IWF – MCPTT server, MCPTT server - IWF) + +Table 10.3.2.18-1 describes the information flow IWF pre-configured regroup reject from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.18-1 IWF pre-configured regroup reject information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Reject reason | M | Reason for rejecting the regrouping operation | + +## 10.3.3 Pre-arranged group call + +### 10.3.3.1 General + +The subclauses 10.3.3.2 and 10.3.3.3 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the MCPTT system. The subclauses 10.3.3.4 and 10.3.3.5 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the LMR system. The subclause 10.3.3.7 describes the late entry procedures and subclause 10.3.3.8 describes the group call release procedures. Group calls can use MC media encryption between the IWF and the MCPTT clients as described in 3GPP TS 33.180 [8]. A call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys. + +The procedures in the present subclause are applicable to the following non-broadcast group call types: pre-configured group regroup calls, pre-configured user regroup calls and group regroup calls. + +NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE. + +### 10.3.3.2 Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system + +In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.2-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for group call setup initiated by MCPTT user on an interworking group defined in MCPTT system. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence of messages is: 1. Initiate group call (from MCPTT client 1), 2. Group call request (from MCPTT client 1 to MCPTT server), 3. Check authorisation (internal to MCPTT server), 4. Call the affiliated MCPTT users (internal to MCPTT server), 5. IWF Group call request (from MCPTT server to IWF), 6. IWF Group call response (from IWF to MCPTT server), 7. Group call response (from MCPTT server to MCPTT client 1), and 8. Media plane is established (across all lifelines).](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + Note left of MCPTT client 1: 1. Initiate group call + MCPTT client 1->>MCPTT server: 2. Group call request + Note right of MCPTT server: 3. Check authorisation + Note right of MCPTT server: 4. Call the affiliated MCPTT users + MCPTT server->>IWF: 5. IWF Group call request + IWF-->>MCPTT server: 6. IWF Group call response + MCPTT server-->>MCPTT client 1: 7. Group call response + Note over MCPTT client 1, MCPTT client 2, MCPTT server, IWF: 8. Media plane is established + +``` + +Sequence diagram for group call setup initiated by MCPTT user on an interworking group defined in MCPTT system. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence of messages is: 1. Initiate group call (from MCPTT client 1), 2. Group call request (from MCPTT client 1 to MCPTT server), 3. Check authorisation (internal to MCPTT server), 4. Call the affiliated MCPTT users (internal to MCPTT server), 5. IWF Group call request (from MCPTT server to IWF), 6. IWF Group call response (from IWF to MCPTT server), 7. Group call response (from MCPTT server to MCPTT client 1), and 8. Media plane is established (across all lifelines). + +**Figure 10.3.3.2-1: Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system** + +1. MCPTT user at MCPTT client 1 initiates a group call for the selected interworking group identified by MCPTT group ID. +2. MCPTT client 1 sends a group call request to the MCPTT server. +3. MCPTT server checks whether the user of MCPTT client 1 is authorized to initiate a group call on the selected interworking group. + +4. MCPTT server proceeds group call setup procedures towards the affiliated MCPTT system users as described in 3GPP TS 23.379 [7]. +5. MCPTT server sends IWF group call request(s) towards the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call request is sent (to the IWF) for each affiliated LMR user. + +NOTE 2: How the LMR users are called is outside the scope of the present document. + +NOTE 3: Steps 4 and 5 can occur in any order. + +6. The IWF returns IWF group call response(s) to the MCPTT server. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +7. The MCPTT server sends group call response to the MCPTT client 1 about successful call establishment. +8. The group call on the interworking group has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +### 10.3.3.3 Group call setup initiated by LMR user on an interworking group defined in MCPTT system. + +In this procedure, an LMR user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.3-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in MCPTT system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the interworking group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. LMR user initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.3.3.3-1: Group call initiated by LMR user on an interworking group defined in MCPTT system. The diagram shows four lifelines: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1. IWF group call request (solid arrow) from IWF to MCPTT server; 2. Call affiliated MCPTT users (solid arrow) from MCPTT server to MCPTT client 1 and 2; 3. IWF group call request (dashed arrow) from MCPTT server to IWF; 4. IWF group call response (dashed arrow) from IWF to MCPTT server; 5. IWF group call response (solid arrow) from MCPTT server to IWF; 6. Media plane is established (solid arrow) from MCPTT server to IWF.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client1 as MCPTT client 1 + participant MCPTT_client2 as MCPTT client 2 + + Note right of MCPTT_server: 2. Call affiliated MCPTT users + Note right of MCPTT_server: 6. Media plane is established + + IWF->>MCPTT_server: 1. IWF group call request + MCPTT_server->>MCPTT_client1: + MCPTT_server->>MCPTT_client2: + MCPTT_server-->>IWF: 3. IWF group call request + IWF-->>MCPTT_server: 4. IWF group call response + MCPTT_server->>IWF: 5. IWF group call response + +``` + +Sequence diagram for Figure 10.3.3.3-1: Group call initiated by LMR user on an interworking group defined in MCPTT system. The diagram shows four lifelines: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1. IWF group call request (solid arrow) from IWF to MCPTT server; 2. Call affiliated MCPTT users (solid arrow) from MCPTT server to MCPTT client 1 and 2; 3. IWF group call request (dashed arrow) from MCPTT server to IWF; 4. IWF group call response (dashed arrow) from IWF to MCPTT server; 5. IWF group call response (solid arrow) from MCPTT server to IWF; 6. Media plane is established (solid arrow) from MCPTT server to IWF. + +**Figure 10.3.3.3-1: Group call initiated by LMR user on an interworking group defined in MCPTT system** + +1. The IWF sends an IWF group call request to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information. +2. MCPTT server calls the affiliated users from MCPTT system as described in 3GPP TS 23.379 [7]. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user. + +NOTE 2: Steps 2 and 3 can occur in any order. + +NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document. + +4. The IWF returns IWF group call response(s) to the MCPTT server. + +5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF. + +NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document. + +6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document. + +#### 10.3.3.4 Group call setup initiated by MCPTT user on an interworking group defined in the LMR system + +In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.4-1. + +This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram showing the group call initiation process between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF.](a5184899f915014fa38608754efcc9c7_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + Note left of MCPTT client 1: 1. Initiate group call + MCPTT client 1->>MCPTT server: 2. Group call request + MCPTT server->>IWF: 3. IWF group call request + IWF->>MCPTT server: 4. IWF group call request + MCPTT server->>MCPTT client 2: 5. Group call request + MCPTT client 2->>MCPTT server: 6. Group call response + MCPTT server->>IWF: 7. IWF group call response + IWF->>MCPTT server: 8. IWF group call response + MCPTT server->>MCPTT client 1: 9. Group call response + Note right of MCPTT client 1: 10. Media plane is established + +``` + +The sequence diagram illustrates the interaction for initiating a group call. It starts with MCPTT client 1 sending an 'Initiate group call' action. A 'Group call request' (2) is sent from MCPTT client 1 to the MCPTT server. The MCPTT server then sends an 'IWF group call request' (3) to the IWF. The IWF responds with another 'IWF group call request' (4) back to the MCPTT server. The MCPTT server then sends a 'Group call request' (5) to MCPTT client 2. MCPTT client 2 responds with a 'Group call response' (6) to the MCPTT server. The MCPTT server sends an 'IWF group call response' (7) to the IWF, which in turn sends an 'IWF group call response' (8) back to the MCPTT server. Finally, the MCPTT server sends a 'Group call response' (9) to MCPTT client 1. A horizontal bar at the bottom indicates that the 'Media plane is established' (10). + +Sequence diagram showing the group call initiation process between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. + +**Figure 10.3.3.4-1: Group call initiated by MCPTT user on an interworking group defined in the LMR system** + +1. MCPTT user at MCPTT client 1 initiates a group call on the selected interworking group identified by MCPTT group ID. +2. MCPTT client 1 sends a group call request to the MCPTT server. +3. As the interworking group is defined in the LMR system the MCPTT server sends an IWF group call request to the IWF. +4. The IWF sends individual IWF group call request(s) to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the user in MCPTT client 2. + +NOTE 2: How the LMR users are called is outside the scope of the present document. + +5. The MCPTT server sends a group call request to the MCPTT client 2. +6. The MCPTT client 2 acknowledges towards the MCPTT server by sending a group call response. +7. The MCPTT server acknowledges towards the IWF by sending an IWF group call response. +8. The IWF sends an IWF group call response to the MCPTT server to acknowledge the IWF group call request received in step 3. +9. The MCPTT server sends a group call response to the initiating MCPTT user. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +10. The group call over the interworking group has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +### 10.3.3.5 Group call setup initiated by LMR user on an interworking group defined in the LMR system. + +In this procedure, an LMR user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.5-1. + +This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. LMR user initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for group call setup initiated by LMR user. Lifelines: IWF, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence shows request and response messages between IWF and MCPTT server, and between MCPTT server and MCPTT clients, ending with a media plane establishment step.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client1 as MCPTT client 1 + participant MCPTT_client2 as MCPTT client 2 + + Note left of IWF: 5. LMR user initiates a group call + IWF->>MCPTT_server: 1a. IWF group call request + IWF->>MCPTT_server: 1b. IWF group call request + MCPTT_server->>MCPTT_client1: 2a. Group call request + MCPTT_server->>MCPTT_client2: 2b. Group call request + MCPTT_client1->>MCPTT_server: 3a. Group call response + MCPTT_client2->>MCPTT_server: 3b. Group call response + MCPTT_server->>IWF: 4a. IWF group call response + MCPTT_server->>IWF: 4b. IWF group call response + Note right of MCPTT_client2: 5. Media plane is established + +``` + +Sequence diagram for group call setup initiated by LMR user. Lifelines: IWF, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence shows request and response messages between IWF and MCPTT server, and between MCPTT server and MCPTT clients, ending with a media plane establishment step. + +Figure 10.3.3.5-1: Group call initiated by LMR user on an interworking group defined in the LMR system + +1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information. +2. MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7]. +3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response. +4. The MCPTT server acknowledges the IWF group call request(s) by sending a IWF group call response(s) to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. + +NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document. + +5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +### 10.3.3.6 Encrypted group call with transcoding + +Pre-conditions: + +1. An MCPTT session is established between an MCPTT client, the interworked LMR system (represented by the IWF), and the MCPTT server. +2. There is an ongoing media transmission. +3. An SDP negotiation has occurred between the IWF and MCPTT Server to establish both the vocoder and the security parameters for the call. +4. The IWF is configured to perform transcoding of voice media and has obtained key material from the MCPTT system using the procedures in 3GPP TS 33.180 [8]. + +![Sequence diagram illustrating an encrypted group call with transcoding between an MCPTT client, MCPTT server, and IWF.](41aef1f5efab13d4f38f69e86c726062_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT client: 1. Ongoing media transmission. MCPTT client has the floor. + MCPTT client->>MCPTT server: 2. Voice media; MCPTT codec + MCPTT server->>IWF: 3. Voice media; MCPTT codec + Note right of IWF: 4. Decryption and Transcoding + Note right of MCPTT client: 5. Floor becomes idle + Note right of MCPTT client: 6. Floor request/grant from/to IWF + Note right of MCPTT client: 7. Ongoing media transmission. IWF has the floor. + Note right of IWF: 8. Transcoding and Encryption + IWF->>MCPTT server: 9. Voice media; MCPTT codec + MCPTT server->>MCPTT client: 10. Voice media; MCPTT codec + +``` + +The diagram shows a sequence of interactions between three entities: MCPTT client, MCPTT server, and IWF. + 1. The MCPTT client is initially transmitting voice media (Ongoing media transmission. MCPTT client has the floor.). + 2. The MCPTT client sends voice media using the MCPTT codec to the MCPTT server. + 3. The MCPTT server forwards this voice media to the IWF. + 4. The IWF performs decryption and transcoding. + 5. The floor becomes idle. + 6. A floor request/grant is sent from/to the IWF. + 7. The IWF is now transmitting voice media (Ongoing media transmission. IWF has the floor.). + 8. The IWF performs transcoding and encryption. + 9. The IWF sends voice media using the MCPTT codec to the MCPTT server. + 10. The MCPTT server forwards this voice media to the MCPTT client. + +Sequence diagram illustrating an encrypted group call with transcoding between an MCPTT client, MCPTT server, and IWF. + +**Figure 10.3.3.6-1: Encrypted group call with transcoding** + +1. The MCPTT client has been given the floor and is transmitting voice media. +2. The MCPTT client encodes audio using a codec defined for the MCPTT group, encrypts the encoded voice using procedures in 3GPP TS 33.180 [8], and forwards the encrypted voice media to the MCPTT server. +3. The MCPTT server forwards the encrypted voice media to other participants in the group call including the IWF. +4. The IWF decrypts the voice media from the MCPTT client using the procedures in 3GPP TS 33.180 [8]. The IWF transcodes the voice to a LMR codec. If needed, the IWF re-encrypts the transcoded voice media using LMR security procedures (these are out-of-scope of this specification), and forwards the voice media to the LMR system. + +NOTE: Where transcoding occurs is outside the scope of this specification. In this procedure, it is assumed to take place internal to the IWF. + +5. Sometime later the floor becomes idle. +6. The LMR system (represented by the IWF in figure 10.3.3.6-1) requests and is granted the floor. +7. The IWF has been given the floor and is transmitting voice media. +8. The IWF receives voice media from the LMR system. If the voice media is encrypted, the IWF decrypts the voice media using LMR security procedures (these are out-of-scope of this specification). The IWF transcodes the voice to the group's MCPTT codec. The IWF re-encrypts the transcoded voice using the procedures in 3GPP TS 33.180 [8]. +9. The IWF forwards the voice media to the MCPTT server. +10. The MCPTT server forwards the voice media to other participants in the group call. + +### 10.3.3.7 Late Entry + +#### 10.3.3.7.1 General + +Late Entry for an ongoing interworking group call is triggered by a successful group affiliation procedure from the participating system. + +NOTE: These procedures apply to all types of group calls, including, for example, emergency call, imminent peril call and broadcast call. + +#### 10.3.3.7.2 Group call late entry on an interworking group defined in the MCPTT system + +In this procedure, the group affiliation from IWF triggers a late entry procedure in the MCPTT system. The signalling procedure is described in figure 10.3.3.7.2-1. + +For the first affiliating LMR user, this procedure is applicable for both IWF affiliation options (see subclauses 10.1.2.1 and 10.3.1). For the following LMR users affiliating to the same group, this procedure is triggered only if the IWF passes through individual affiliations for each group member. + +This subclause is based upon subclauses in 3GPP TS 23.379 [7] for: + +- Late entry for pre-arranged group call, subclause 10.6.2.3.1.1.4, and +- Group call for an MCPTT group defined in partner MCPTT system, subclause 10.6.2.4.3.1. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +3. There is an on-going group call in the interworking group involving MCPTT clients 1 and 2. +4. First LMR user affiliates to the interworking group. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence starts with a '1. Group affiliation procedure' between IWF and MCPTT server. Then, '2. Initiate late entry' is shown as a message from MCPTT server. Next, '3. IWF group call request' is sent from MCPTT server to IWF, followed by '4. IWF group call response' from IWF to MCPTT server. A large box labeled '5. IWF is added to ongoing group call' spans across all lifelines. Finally, two messages are shown: '6a. IWF floor taken' from MCPTT server to IWF and '6b. IWF floor idle' from MCPTT server to IWF.](01e00200a536673d6cd0e6d8705047a0_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + Note over IWF, MCPTT server: 1. Group affiliation procedure + Note over MCPTT server: 2. Initiate late entry + MCPTT server->>IWF: 3. IWF group call request + IWF->>MCPTT server: 4. IWF group call response + Note over IWF, MCPTT server, MCPTT client 1, MCPTT client 2: 5. IWF is added to ongoing group call + MCPTT server->>IWF: 6a. IWF floor taken / 6b. IWF floor idle + +``` + +Sequence diagram for Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence starts with a '1. Group affiliation procedure' between IWF and MCPTT server. Then, '2. Initiate late entry' is shown as a message from MCPTT server. Next, '3. IWF group call request' is sent from MCPTT server to IWF, followed by '4. IWF group call response' from IWF to MCPTT server. A large box labeled '5. IWF is added to ongoing group call' spans across all lifelines. Finally, two messages are shown: '6a. IWF floor taken' from MCPTT server to IWF and '6b. IWF floor idle' from MCPTT server to IWF. + +**Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system** + +1. The IWF triggers a group affiliation towards the MCPTT server (see subclause 10.1.2.2). +2. The MCPTT server initiates a group call late entry for an interworking group. +3. The MCPTT server sends an IWF group call request to the IWF. + +NOTE 2: How the IWF delivers the group call request to the LMR system is out of the scope of the present document. + +4. The IWF confirms the group call request by sending IWF group call response to the MCPTT server. +5. The IWF (and the LMR user) is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the LMR user joining the group call. +6. If the floor has been granted to another user, the MCPTT server sends a IWF floor taken (6a) to the IWF. If the floor is not granted to any party, an IWF floor idle (6b) is sent to the IWF. + +### 10.3.3.7.3 Group call late entry on an interworking group defined in the LMR system + +In this procedure, the group affiliation from MCPTT system triggers a late entry procedure in the LMR system. The signalling procedure is described in figure 10.3.3.7.3-1. + +This procedure describes the affiliation and late entry of the first MCPTT user into the interworking group, but it is applicable also for all subsequent MCPTT users' affiliations to the same group. + +This subclause is based upon subclauses in 3GPP TS 23.379 [7] for: + +- Late entry pre-arranged group call, subclause 10.6.2.3.1.1.4, and +- Group call setup involving groups from multiple MCPTT systems, subclause 10.6.2.4.1.1. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. + +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +3. There is an on-going group call in the interworking group, involving only LMR users. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram showing group call late entry. Participants are MCPTT client 1, MCPTT server, and IWF. Steps include affiliation, group call request/response, adding client to call, and floor status updates.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant S as MCPTT server + participant IWF as IWF + + Note over C1, IWF: 1. MCPTT user affiliates + IWF->>S: 2. IWF Group call request + Note over C1, S: 3. Group call setup for the affiliated MCPTT user + S->>IWF: 4. IWF Group call response + Note over C1, IWF: 5. MCPTT client 1 is added to the ongoing group call + IWF->>S: 6a. IWF floor taken / 6b. IWF floor idle + S->>C1: 7a. Floor taken / 7b. Floor idle + +``` + +Detailed description: The diagram shows three vertical lifelines for MCPTT client 1, MCPTT server, and IWF. + Step 1 is a box spanning all three: '1. MCPTT user affiliates'. + Step 2 is an arrow from IWF to MCPTT server: '2. IWF Group call request'. + Step 3 is a box spanning MCPTT client 1 and MCPTT server: '3. Group call setup for the affiliated MCPTT user'. + Step 4 is an arrow from MCPTT server to IWF: '4. IWF Group call response'. + Step 5 is a box spanning all three: '5. MCPTT client 1 is added to the ongoing group call'. + Step 6 is an arrow from IWF to MCPTT server: '6a. IWF floor taken / 6b. IWF floor idle'. + Step 7 is an arrow from MCPTT server to MCPTT client 1: '7a. Floor taken / 7b. Floor idle'. + +Sequence diagram showing group call late entry. Participants are MCPTT client 1, MCPTT server, and IWF. Steps include affiliation, group call request/response, adding client to call, and floor status updates. + +**Figure 10.3.3.7.3-1: Group call late entry on an interworking group defined in the LMR system** + +1. MCPTT user (client 1) affiliates to the group (see subclause 10.1.2.4). + +NOTE 2: How the IWF delivers the affiliation to LMR system and how the LMR system handles the late entry is out of scope of the present document. + +2. The IWF sends an IWF group call request to the MCPTT server. +3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7]. +4. The MCPTT server confirms the successful establishment of the group call by sending IWF group call response to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +5. MCPTT client 1 is successfully added to the ongoing group call. +6. If the floor has been granted to another user, the IWF sends an IWF floor taken (6a) to the MCPTT server. If the floor is not granted to any party, an IWF floor idle (6b) is sent. +7. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7]. + +### 10.3.3.8 Interworking group call release + +#### 10.3.3.8.1 General + +The procedures in this subclause define the cases where the group host server releases an ongoing interworking group call for all the participants of that group. + +If the group host server is an MCPTT server, the release conditions are described in 3GPP TS 23.379 [7], subclause 10.6.2.4.1.2. + +If the group host server is an LMR system, represented by an IWF, the release conditions are outside the scope of the present document. + +#### 10.3.3.8.2 Group call release on an interworking group defined in the MCPTT system + +In this procedure, the MCPTT system is releasing a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.8.2-1. + +This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7]. + +Pre-conditions: + +- 1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +- 2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +- 3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram showing the group call release process. Lifelines: MCPTT server, MCPTT client 1, MCPTT client 2, IWF. Steps: 1. Release group call (MCPTT server self-call), 2. Determine group call participants (MCPTT server self-call), 3. IWF Group call release request (MCPTT server to IWF), 4. Release group call from MCPTT clients (MCPTT server to clients), 5. IWF Group call release response (IWF to MCPTT server), 6. Releasing floor control and media plane resources associated with the group call (MCPTT server self-call).](fdc47b9a20953c3611add6122f6831bf_img.jpg) + +``` +sequenceDiagram + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + participant IWF + + Note left of MCPTT server: 1. Release group call + Note left of MCPTT server: 2. Determine group call participants + MCPTT server->>IWF: 3. IWF Group call release request + Note left of MCPTT server: 4. Release group call from MCPTT clients + IWF->>MCPTT server: 5. IWF Group call release response + Note left of MCPTT server: 6. Releasing floor control and media plane resources associated with the group call +``` + +Sequence diagram showing the group call release process. Lifelines: MCPTT server, MCPTT client 1, MCPTT client 2, IWF. Steps: 1. Release group call (MCPTT server self-call), 2. Determine group call participants (MCPTT server self-call), 3. IWF Group call release request (MCPTT server to IWF), 4. Release group call from MCPTT clients (MCPTT server to clients), 5. IWF Group call release response (IWF to MCPTT server), 6. Releasing floor control and media plane resources associated with the group call (MCPTT server self-call). + +Figure 10.3.3.8.2-1: Group call release initiated by MCPTT system on an interworking group + +1. The MCPTT server initiates a group call release on an interworking group. + +NOTE 2: The MCPTT server may decide to release the group call for different reasons, see subclause 10.6.2.4.1.2 in 3GPP TS 23.379 [7]. + +2. The MCPTT server identifies the participants of the ongoing group call, at least one of them being an LMR user, represented by an IWF. +3. The MCPTT server sends IWF group call release request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call release request is sent (to the IWF) for each affiliated LMR user. + +NOTE 3: How the group call release request(s) is(are) forwarded to the LMR system is out of scope of the present document. + +4. The MCPTT server sends the (MCPTT) group call release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7]. + +NOTE 4: Steps 3 and 4 can occur in any order. + +5. The IWF confirms the IWF group call release request(s) received in step 3 by IWF group call release response(s) to the MCPTT server. +6. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released. + +#### 10.3.3.8.3 Group call release on an interworking group defined in the LMR system + +In this procedure, the LMR system is releasing a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.8.3-1. + +This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2. +4. The LMR system initiates release of the group call. + +NOTE 1: The reasons for the LMR system's decision to release the group call are out of scope of the present document. + +NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the group call release initiated by the LMR system on an interworking group. The diagram shows four lifelines: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1a. IWF group call release request (IWF to MCPTT server), 1b. IWF group call release request (IWF to MCPTT server), 2a. Group call release request (MCPTT server to MCPTT client 1), 2b. Group call release request (MCPTT server to MCPTT client 2), 3a. Group call release response (MCPTT client 1 to MCPTT server), 3b. Group call release response (MCPTT client 2 to MCPTT server), 4a. IWF group call release response (MCPTT server to IWF), 4b. IWF group call release response (MCPTT server to IWF). A final step, 5. Releasing floor control and media plane resources associated with the group call, is shown as a horizontal bar at the bottom.](789ee0a267b24f34bd1f45313e86c9a4_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + Note right of MCPTT client 2: 5. Releasing floor control and media plane resources associated with the group call + IWF->>MCPTT server: 1a. IWF group call release request + IWF->>MCPTT server: 1b. IWF group call release request + MCPTT server->>MCPTT client 1: 2a. Group call release request + MCPTT server->>MCPTT client 2: 2b. Group call release request + MCPTT client 1->>MCPTT server: 3a. Group call release response + MCPTT client 2->>MCPTT server: 3b. Group call release response + MCPTT server->>IWF: 4a. IWF group call release response + MCPTT server->>IWF: 4b. IWF group call release response + +``` + +Sequence diagram illustrating the group call release initiated by the LMR system on an interworking group. The diagram shows four lifelines: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1a. IWF group call release request (IWF to MCPTT server), 1b. IWF group call release request (IWF to MCPTT server), 2a. Group call release request (MCPTT server to MCPTT client 1), 2b. Group call release request (MCPTT server to MCPTT client 2), 3a. Group call release response (MCPTT client 1 to MCPTT server), 3b. Group call release response (MCPTT client 2 to MCPTT server), 4a. IWF group call release response (MCPTT server to IWF), 4b. IWF group call release response (MCPTT server to IWF). A final step, 5. Releasing floor control and media plane resources associated with the group call, is shown as a horizontal bar at the bottom. + +**Figure 10.3.3.8.3-1: Group call release initiated by LMR system on an interworking group defined in the LMR system** + +1. The IWF sends IWF group call release requests to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call. +2. The MCPTT server forwards the release requests to the group's MCPTT users (in this example to users in MCPTT clients 1 and 2), as described in 3GPP TS 23.379 [7]. +3. The MCPTT clients respond with group call release response(s). +4. The MCPTT server confirms the IWF group call release requests received in step 1 by IWF group call release responses to the IWF. +5. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released. + +## 10.3.4 Group broadcast + +### 10.3.4.1 General + +A broadcast group call is a special group call where the initiating user expects no response from the receiving users so that when the transmission is complete, so is the call. The initiating user can be an MCPTT user or can be an LMR user. + +The group-broadcast group is defined as a set of groups, not a set of users. The user that originates the group-broadcast group call is the only one transmitting media during this call. + +The group-broadcast group is defined with a hierarchy. For example, groups A and B may be subordinate to a group-broadcast group. All subordinate groups belonging to a group-broadcast group are defined either in the MCPTT system or the LMR system. + +### 10.3.4.2 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the MCPTT system + +3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF. + +In this procedure, the MCPTT server is initiating the broadcast and is the owner of the group-broadcast group. + +The procedure shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden. + +Figure 10.3.4.2-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the MCPTT system). + +Pre-conditions: + +1. The group (e.g. A) to which MCPTT client 2 and the IWF are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call. +3. The call initiator of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). +4. The group-broadcast group and its subordinate groups are defined in the same group management server and served by the same MCPTT server. + +![Sequence diagram illustrating the group-broadcast group call setup procedure involving MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and IWF. The process includes call initiation, ID resolution, group call release, and subsequent setup requests to MCPTT client 2 and IWF, followed by responses and media flow establishment.](a780a960b3f2de2493d5785bedae10ff_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant IWF + + Note left of MCPTT client 1: 1. Initiate group-broadcast group call + MCPTT client 1->>MCPTT server: 2. Group-broadcast group call setup request + MCPTT server->>Group management server: 3. Resolve (group-broadcast) group ID + Note right of MCPTT server: 4. Consider on-going calls on subordinate groups + Note right of MCPTT server: 5. Group call release of groups defined in the MCPTT system + MCPTT server->>MCPTT client 2: 6a. Group-broadcast group call setup request + MCPTT server->>IWF: 6b. IWF Group-broadcast group call setup request + Note right of MCPTT client 2: 7. Notify group broadcast group call + MCPTT client 2->>MCPTT server: 8a. Group-broadcast group call setup response + IWF->>MCPTT server: 8b. IWF Group-broadcast group call setup response + MCPTT server->>MCPTT client 1: 9. Group-broadcast group call response + Note left of MCPTT client 1: 10. Notify User + Note right of MCPTT client 1: Media Flow + Note right of MCPTT server: Media Flow + Note right of MCPTT client 2: Media Flow + +``` + +Sequence diagram illustrating the group-broadcast group call setup procedure involving MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and IWF. The process includes call initiation, ID resolution, group call release, and subsequent setup requests to MCPTT client 2 and IWF, followed by responses and media flow establishment. + +**Figure 10.3.4.2-1: Group-broadcast group call involving IWF (group-broadcast group is defined in the MCPTT system)** + +1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server. +3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT users of those subordinate groups. +4. The MCPTT server then needs to consider any on-going group calls on those subordinate groups because this may affect the behaviour for what happens next. In this case a group call exists on a subordinate group. Thus, the MCPTT users involved in the group call on this subordinate group. +5. The MCPTT server performs group call release procedures of groups defined in the MCPTT system as described in subclause 10.3.3.8.2. + +6. A group-broadcast group call request is sent to MCPTT client 2 and an IWF group-broadcast group call request to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user. + +NOTE 1: How the group-broadcast group call request(s) is(are) forwarded to the LMR system is out of scope of the present document. + +7. MCPTT client 2 is notified of the incoming group-broadcast group call. + +NOTE 2: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document. + +8. MCPTT client 2 and the IWF respond to the IWF group-broadcast group call request by sending an IWF group-broadcast group call response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user. + +9. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response. + +10. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Once the user of MCPTT client 1 completes transmitting, the group-broadcast group call is released. + +#### 10.3.4.3 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the LMR system + +3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF. + +In this procedure, the IWF is the owner of the group-broadcast group and is initiating the group-broadcast group call. + +The procedure only shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden. + +Figure 10.3.4.3-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the LMR system). + +Pre-conditions: + +1. The group (e.g. A) to which MCPTT client 2 is a member is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call. +3. The call initiator, MCPTT client 1, of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). +4. The group-broadcast group and its subordinate groups are defined in the IWF. + +![Sequence diagram for Group-broadcast group call involving IWF (group-broadcast group defined in the LMR system).](255efa1d461fc79b4ed367aaec11637f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant IWF + + Note left of MCPTT client 1: 1. Initiate group-broadcast group call + MCPTT client 1->>MCPTT server: 2. Group-broadcast group call setup request + MCPTT server->>IWF: 3. IWF group-broadcast group call setup request + Note over MCPTT server, IWF: 4. Group call release of groups defined in the LMR system + IWF->>MCPTT server: 5a. IWF group-broadcast group call setup request + MCPTT server->>MCPTT client 2: 5b. Group-broadcast group call setup request + Note right of MCPTT client 2: 6. Notify group broadcast group call + MCPTT client 2->>MCPTT server: 7a. Group-broadcast group call setup response + MCPTT server->>IWF: 7b. IWF group-broadcast group call setup response + MCPTT server->>MCPTT client 1: 8. Group-broadcast group call response + Note left of MCPTT client 1: 9. Notify User + + Note left of MCPTT client 1: Media Flow + MCPTT client 1->>MCPTT server: Media Flow + MCPTT server->>MCPTT client 2: Media Flow + MCPTT server->>IWF: Media Flow + +``` + +The sequence diagram illustrates the interaction for a group-broadcast group call setup. It begins with MCPTT client 1 initiating the call. The client sends a setup request to the MCPTT server, which then forwards an IWF group-broadcast group call setup request to the IWF. A message indicates the group call release of groups defined in the LMR system. The IWF then sends an IWF group-broadcast group call setup request back to the MCPTT server, which in turn sends a group-broadcast group call setup request to MCPTT client 2. MCPTT client 2 notifies the group broadcast group call and sends a group-broadcast group call setup response to the MCPTT server. The MCPTT server then sends an IWF group-broadcast group call setup response to the IWF and a group-broadcast group call response to MCPTT client 1. Finally, MCPTT client 1 notifies the user. Media flows are shown from MCPTT client 1 to the MCPTT server, from the MCPTT server to MCPTT client 2, and from the MCPTT server to the IWF. + +Sequence diagram for Group-broadcast group call involving IWF (group-broadcast group defined in the LMR system). + +**Figure 10.3.4.3-1: Group-broadcast group call involving IWF (group-broadcast group defined in the LMR system)** + +1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server. +3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call setup request to the IWF. + +4. The IWF performs group call release procedures of groups defined in the LMR system as described in subclause 10.3.3.8.3. +5. The IWF issues a group-broadcast group call setup request to establish the group-broadcast call. +6. The MCPTT user of MCPTT client 2 is notified. + +NOTE: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document. + +7. Optionally, MCPTT client 2 respond with a group-broadcast group call response to the MCPTT server and then to the IWF. +8. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response. +9. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Once the user of MCPTT client 1 completes transmitting, the group-broadcast group call is released. + +#### 10.3.4.4 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the MCPTT system + +When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released. + +Figure 10.3.4.4-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group is defined in the MCPTT system). + +Pre-conditions: + +1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists. + +![Sequence diagram showing the termination of a group-broadcast group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The process starts with MCPTT client 1 finishing transmitting, followed by a release request to the server, which then propagates to client 2 and the IWF. Responses are returned from client 2 and the IWF to the server, which finally responds to client 1.](01832e59ebad7ada5e790de6f90cc9b6_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant IWF + + Note left of MCPTT client 1: 1. Finished transmitting + MCPTT client 1->>MCPTT server: 2. Group-broadcast group call release request + MCPTT server->>MCPTT client 2: 3a. Group broadcast group call release request + MCPTT server->>IWF: 3b. IWF group-broadcast group call release request + Note right of MCPTT client 2: 4. Notify user + MCPTT client 2->>MCPTT server: 5a. Group broadcast group call release response + IWF->>MCPTT server: 5b. IWF group-broadcast group call release response + MCPTT server->>MCPTT client 1: 6. Group-broadcast group call release response + +``` + +Sequence diagram showing the termination of a group-broadcast group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The process starts with MCPTT client 1 finishing transmitting, followed by a release request to the server, which then propagates to client 2 and the IWF. Responses are returned from client 2 and the IWF to the server, which finally responds to client 1. + +**Figure 10.3.4.4-1: Group-broadcast group call transmission ended (group-broadcast group is defined in the MCPTT system)** + +1. MCPTT user on MCPTT client 1 finished transmitting. +2. A group-broadcast group call release request is sent to the MCPTT server of the group-broadcast group. +3. The MCPTT users of MCPTT client 2 and the IWF of the group-broadcast group's subordinate groups are sent a group-broadcast group call release request. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user. +4. MCPTT client 2 and the IWF notify their users that the group-broadcast group call has ended. + +NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document. + +5. MCPTT client 2 and the IWF respond to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user. +6. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the call is now ended. + +### 10.3.4.5 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the LMR system + +When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released. + +Figure 10.3.4.5-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group defined in the LMR system). + +Pre-conditions: + +1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists. + +![Sequence diagram illustrating the group-broadcast group call release procedure. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The sequence starts with MCPTT client 1 sending a 'Finished transmitting' message to the MCPTT server. The MCPTT server then sends a 'Group-broadcast group call release request' to the IWF. The IWF sends a 'Group-broadcast group call release request' to the MCPTT server, which in turn sends a 'Group-broadcast group call release request' to MCPTT client 2. MCPTT client 2 sends a 'Notify user' message. The MCPTT server sends a 'Group-broadcast group call release response' to the IWF. The IWF sends a 'Group-broadcast group call release response' to the MCPTT server. Finally, the MCPTT server sends a 'Group-broadcast group call release response' to MCPTT client 1.](802707b774f2d2973b49cea2020e8453_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant IWF + + Note left of MCPTT client 1: 1. Finished transmitting + MCPTT client 1->>MCPTT server: 2. Group-broadcast group call release request + MCPTT server->>IWF: 3. IWF group-broadcast group call release request + IWF->>MCPTT server: 4. IWF group-broadcast group call release request + MCPTT server->>MCPTT client 2: 4a. Group-broadcast group call release request + Note right of MCPTT client 2: 5. Notify user + MCPTT client 2->>MCPTT server: 6. Group-broadcast group call release response + MCPTT server->>IWF: 7. IWF group-broadcast group call release response + IWF->>MCPTT server: 7a. IWF group-broadcast group call release response + MCPTT server->>MCPTT client 1: 8. Group-broadcast group call release response + +``` + +Sequence diagram illustrating the group-broadcast group call release procedure. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The sequence starts with MCPTT client 1 sending a 'Finished transmitting' message to the MCPTT server. The MCPTT server then sends a 'Group-broadcast group call release request' to the IWF. The IWF sends a 'Group-broadcast group call release request' to the MCPTT server, which in turn sends a 'Group-broadcast group call release request' to MCPTT client 2. MCPTT client 2 sends a 'Notify user' message. The MCPTT server sends a 'Group-broadcast group call release response' to the IWF. The IWF sends a 'Group-broadcast group call release response' to the MCPTT server. Finally, the MCPTT server sends a 'Group-broadcast group call release response' to MCPTT client 1. + +**Figure 10.3.4.5-1: Group-broadcast group call transmission ended (group-broadcast group defined in the LMR system)** + +1. The MCPTT user on MCPTT client 1 finished transmitting. +2. A group-broadcast group call release request is sent to the MCPTT server. +3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call release request to the IWF. +4. The IWF sends an IWF group-broadcast group call release request to the MCPTT server hosting client 2. The MCPTT server sends the group-broadcast group call release request to MCPTT client 2. +5. MCPTT client 2 is notified that the group-broadcast group call has ended. + +NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document. + +6. MCPTT client 2 responds to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. + +7. The MCPTT server sends an IWF group-broadcast group call release response to the IWF. The IWF becomes aware that MCPTT client 2 has confirmed the group-broadcast group call release and replies with another IWF group-broadcast group call release response back to the MCPTT server to trigger step 8. +8. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the group-broadcast group call is now ended. + +#### 10.3.4.6 Broadcast group regroup call using pre-configured group + +##### 10.3.4.6.1 General + +The temporary group created using a pre-configured group can be a broadcast group or a non-broadcast group. + +A broadcast group regroup call using pre-configured groups can be achieved by first regrouping users into a pre-configured group regroup, making the broadcast group call on the pre-configured group, and then cancelling the pre-configured group regroup. + +##### 10.3.4.6.2 Broadcast group regroup call using pre-configured group the MCPTT system + +The broadcast group regroup call procedure using pre-configured group allows an authorized MCPTT user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. The regroup is cancelled at the end of the broadcast call to prevent users from talking back on the pre-configured group regroup. This procedure requires that the authorized MCPTT user is a group member of at least one of the MCPTT groups included in the regroup operation. + +Figure 10.3.4.6.2-1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured MCPTT regroup group owned by the MCPTT system. For simplicity, no receiving clients are shown. + +Pre-conditions: + +- The MCPTT client is registered with the MCPTT service. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client and the IWF. The MCPTT client and the IWF have received the relevant security related information to allow them to communicate in the pre-configured group regroup. +- The MCPTT client is authorized to initiate a pre-configured group regroup using the pre-configured group regroup procedure. +- The MCPTT client is aware of a suitable pre-configured group whose configuration has been pre-configured in the IWF and the MC service UEs of the MCPTT users who will be regrouped. +- The MCPTT client is affiliated to group 1. +- The IWF is affiliated to one or more of MCPTT group 1, 2 or 3. +- The pre-configured group regroup is homed in the MCPTT server. +- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup. + +![Sequence diagram showing the broadcast group regroup call using pre-configured group in the MCPTT system. The diagram involves three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Preconfigured group regroup procedure, 2. Broadcast group call, and 3. Preconfigured group regroup cancellation.](fed4a04822c24fb22cca3a14f4ddae83_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT client: 1. Preconfigured group regroup procedure + Note right of MCPTT client: 2. Broadcast group call + Note right of MCPTT client: 3. Preconfigured group regroup cancellation + +``` + +Sequence diagram showing the broadcast group regroup call using pre-configured group in the MCPTT system. The diagram involves three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Preconfigured group regroup procedure, 2. Broadcast group call, and 3. Preconfigured group regroup cancellation. + +**Figure 10.3.4.6.2-1: Broadcast group regroup call using pre-configured group in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the pre-configured group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1, 2, and 3 are regrouped into group 4. +2. The MCPTT user at the MCPTT client performs the broadcast group call procedure as specified in subclause 10.3.4. +3. The MCPTT client initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1. + +#### 10.3.4.6.3 Broadcast group regroup call using pre-configured group in the IWF + +The broadcast group regroup call procedure using a pre-configured group allows an IWF user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. + +Figure 10.3.4.6.3-1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured group owned by the IWF. + +Pre-conditions: + +- MCPTT clients 1 and 2 are registered with the MCPTT service. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in MCPTT clients 1 and 2, and MCPTT clients 1 and 2 have received the relevant security related information to allow them to communicate in the pre-configured group regroup. +- MCPTT client 1 is affiliated to group 1, MCPTT client 2 is affiliated to group 2. Group 3 is used as the pre-configured group regroup. +- The pre-configured group regroup is homed in the IWF. +- The MCPTT server is home to at least one group that's a constituent group of the pre-configured group regroup. + +![Sequence diagram showing the broadcast group regroup call using pre-configured group in the IWF. The diagram involves four entities: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1. Preconfigured group regroup procedure, 2. Broadcast group call, and 3. Preconfigured group regroup cancellation.](107c8e1abcb7033ad244e30e7a910045_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + Note right of MCPTT client 2: 1. Preconfigured group regroup procedure + Note right of MCPTT client 2: 2. Broadcast group call + Note right of MCPTT client 2: 3. Preconfigured group regroup cancellation + +``` + +Sequence diagram showing the broadcast group regroup call using pre-configured group in the IWF. The diagram involves four entities: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1. Preconfigured group regroup procedure, 2. Broadcast group call, and 3. Preconfigured group regroup cancellation. + +**Figure 10.3.4.6.3-1: Broadcast group regroup call using pre-configured group in the IWF** + +1. The IWF initiates the group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1 and 2 are regrouped into group 3. +2. The IWF performs the broadcast group call procedure as specified in subclause 10.3.4. +3. The IWF initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1. + +## 10.3.5 Chat group call + +### 10.3.5.1 General + +This subclause is based upon subclause for chat group call in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.2. For LMR systems that do not support the concept of chat groups, the IWF might still adapt its calls to the MCPTT chat model. + +### 10.3.5.2 MCPTT user initiated chat group call in an interworking group defined in LMR system + +In this procedure, an MCPTT user initiates a chat group call in an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.5.2-1. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for MCPTT user initiated chat group call in an interworking group defined in the LMR system. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. The sequence is: 1. Group join request from MCPTT client to MCPTT server; 2. Enforce privacy policy (internal to MCPTT server); 3. IWF group join request from MCPTT server to IWF; 4. IWF group join response from IWF to MCPTT server; 5. Group join response from MCPTT server to MCPTT client; 6. The MCPTT client requests to transmit causing the media plane to be established (internal to MCPTT client); 7. Media plane signaling using floor control (bidirectional between MCPTT client and IWF).](52c40e2f443985dc63f45dec57d90c8c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT server: 2. Enforce privacy policy + MCPTT client->>MCPTT server: 1. Group join request + MCPTT server->>IWF: 3. IWF group join request + IWF-->>MCPTT server: 4. IWF group join response + MCPTT server-->>MCPTT client: 5. Group join response + Note left of MCPTT client: 6. The MCPTT client requests to transmit causing the media plane to be established + Note right of MCPTT client: 7. Media plane signaling using floor control + +``` + +Sequence diagram for MCPTT user initiated chat group call in an interworking group defined in the LMR system. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. The sequence is: 1. Group join request from MCPTT client to MCPTT server; 2. Enforce privacy policy (internal to MCPTT server); 3. IWF group join request from MCPTT server to IWF; 4. IWF group join response from IWF to MCPTT server; 5. Group join response from MCPTT server to MCPTT client; 6. The MCPTT client requests to transmit causing the media plane to be established (internal to MCPTT client); 7. Media plane signaling using floor control (bidirectional between MCPTT client and IWF). + +**Figure 10.3.5.2-1: MCPTT user initiated chat group call in an interworking group defined in the LMR system** + +1. MCPTT user of the MCPTT client indicates to join the group communication for the group. The MCPTT client joins the group by sending a group join request to the MCPTT server. If there is a request to transmit, then the group join request contains an indication of an implicit floor request and the location of the joining party if required. +2. The MCPTT server inspects the Group join request for presence of location information of the calling party. If location information is included in the join request, the MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. +3. The MCPTT server notices that the interworking group is defined in the LMR system and forwards the group join request with or without location depending on the outcome of the privacy check as an IWF group join request to the IWF. +4. The IWF replies with an IWF group join response indicating the acceptance of the group join request and also returns the IWF selected media parameters for the chat group call in the IWF group join response. +5. The MCPTT server forwards the IWF group join response to the MCPTT client as a group join response. +6. If the MCPTT client requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call. +7. Floor control will continue to be used by the floor participants associated with the MCPTT client and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. + +### 10.3.5.3 LMR user initiated chat group call in an interworking group defined in MCPTT system + +In this procedure, an LMR user initiates a chat group call in an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.5.3-1. + +Pre-conditions: + +1. The interworking group information is known at the IWF by configuration. The interworking group has been defined in the MCPTT system. + +2. MCPTT user 1 and MCPTT user 2 have previously joined (affiliated) to the group. +3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +4. LMR user initiates a join to the group. + +NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the LMR user initiated chat group call in an interworking group defined in the MCPTT system. The diagram shows four lifelines: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1. IWF group join request from IWF to MCPTT server; 2. Check authorization and affiliate the user (internal to MCPTT server); 3. IWF group join response from MCPTT server to IWF; 4. The IWF requests to transmit causing the media plane to be established (from IWF to a horizontal bar spanning all three); 5. Media plane signaling using floor control (indicated by a large double-headed arrow spanning all three lifelines).](30387053b5b3fede6873f6a46a9ca4a9_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note right of MCPTT server: 2. Check authorization and affiliate the user + IWF->>MCPTT server: 1. IWF group join request + MCPTT server-->>IWF: 3. IWF group join response + Note over MCPTT server, MCPTT client 1, MCPTT client 2: 4. The IWF requests to transmit causing the media plane to be established + Note over IWF, MCPTT server, MCPTT client 1, MCPTT client 2: 5. Media plane signaling using floor control + +``` + +Sequence diagram illustrating the LMR user initiated chat group call in an interworking group defined in the MCPTT system. The diagram shows four lifelines: IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence of messages is: 1. IWF group join request from IWF to MCPTT server; 2. Check authorization and affiliate the user (internal to MCPTT server); 3. IWF group join response from MCPTT server to IWF; 4. The IWF requests to transmit causing the media plane to be established (from IWF to a horizontal bar spanning all three); 5. Media plane signaling using floor control (indicated by a large double-headed arrow spanning all three lifelines). + +**Figure 10.3.5.3-1: LMR user initiated chat group call in an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF group join request to the MCPTT server. The request to join may contain location information of the transmitting party. If there is a request to transmit, then the IWF group join request contains an indication of an implicit floor request and the location of the joining party if required. +2. The MCPTT server checks whether the MCPTT ID is authorized to affiliate to the group. MCPTT server generates an implicit affiliation if the MCPTT ID is not already affiliated to the group. +3. The MCPTT server replies with a group join response indicating the acceptance of the group join request and also returns the MCPTT server selected media parameters for the chat group call in the IWF group join response. +4. If the IWF requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call. +5. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. + +#### 10.3.5.4 Release chat group call on an interworking group defined in the LMR system + +This procedure describes the case where the LMR system releases an ongoing MCPTT chat group call on an interworking group defined in the LMR system, for all the participants of that group call. The signalling procedure is described in figure 10.3.5.4-1. + +Pre-conditions: + +1. A chat group call is ongoing involving an MCPTT client and the IWF. + +2. The LMR system initiates release of the chat group call. + +![Sequence diagram showing the release of a chat group call on an interworking group defined in the LMR system. The diagram involves three main entities: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF Group call release request (IWF to MCPTT server); 2. Group call release request (MCPTT server to MCPTT client); 3. Notify user (MCPTT client to MCPTT client); 4. Group call release response (MCPTT client to MCPTT server); 5. IWF group call release response (MCPTT server to IWF); 6. Release floor control and media plane resources associated with the group call (MCPTT client and IWF).](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client + Note right of MCPTT client: 3. Notify user + IWF->>MCPTT server: 1. IWF Group call release request + MCPTT server->>MCPTT client: 2. Group call release request + MCPTT client-->>MCPTT server: 4. Group call release response + MCPTT server-->>IWF: 5. IWF group call release response + Note over MCPTT client, IWF: 6. Release floor control and media plane resources associated with the group call + +``` + +Sequence diagram showing the release of a chat group call on an interworking group defined in the LMR system. The diagram involves three main entities: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF Group call release request (IWF to MCPTT server); 2. Group call release request (MCPTT server to MCPTT client); 3. Notify user (MCPTT client to MCPTT client); 4. Group call release response (MCPTT client to MCPTT server); 5. IWF group call release response (MCPTT server to IWF); 6. Release floor control and media plane resources associated with the group call (MCPTT client and IWF). + +**Figure 10.3.5.4-1: Release chat group call on an interworking group defined in the LMR system** + +1. The IWF sends an IWF group call release request to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call. +2. MCPTT server forwards the release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7]. +3. MCPTT users are notified about the release of the group call. +4. Optionally, the MCPTT client confirms the group call release request received in step 2 with a group call release response to the MCPTT server. +5. The MCPTT server forwards the group call release response to the IWF as an IWF group call release response. +6. The MCPTT client and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients. + +### 10.3.5.5 Release chat group call on an interworking group defined in the MCPTT system + +This procedure describes the case where the MCPTT server releases an ongoing MCPTT chat group call, on an interworking group defined in the MCPTT system, for all the participants of that group call, since at least one of the conditions for release are met e.g. due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or the number of affiliated MCPTT group members is below the minimum number permitted. + +The signalling procedure is described in figure 10.3.5.5-1. + +Pre-conditions: + +1. A chat group call is ongoing involving MCPTT clients 1, 2 and the IWF. + +![Sequence diagram showing the release of a chat group call in an MCPTT system. The participants are IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence starts with the MCPTT server sending a 'Release group call' message. It then sends an 'IWF group call release request' to the IWF and 'Group call release request' messages to both clients. The clients send 'Notify user' messages. The IWF sends an 'IWF group call release response' to the server. The clients send 'Group call release response' messages. Finally, the server sends a 'Release floor control and media plane resources associated with the group call' message.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note right of MCPTT server: 1. Release group call + MCPTT server->>IWF: 2. IWF group call release request + MCPTT server->>MCPTT client 1: 3. Group call release request + MCPTT server->>MCPTT client 2: 3. Group call release request + MCPTT client 1->>MCPTT client 1: 4. Notify user + MCPTT client 2->>MCPTT client 2: 4. Notify user + IWF->>MCPTT server: 5. IWF group call release response + MCPTT client 1->>MCPTT server: 6. Group call release response + MCPTT client 2->>MCPTT server: 6. Group call release response + Note right of MCPTT server: 7. Release floor control and media plane resources associated with the group call + +``` + +Sequence diagram showing the release of a chat group call in an MCPTT system. The participants are IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The sequence starts with the MCPTT server sending a 'Release group call' message. It then sends an 'IWF group call release request' to the IWF and 'Group call release request' messages to both clients. The clients send 'Notify user' messages. The IWF sends an 'IWF group call release response' to the server. The clients send 'Group call release response' messages. Finally, the server sends a 'Release floor control and media plane resources associated with the group call' message. + +**Figure 10.3.5.5-1: Release chat group call on an interworking group defined in the MCPTT system** + +1. The MCPTT server decides to release the MCPTT chat group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +2. The MCPTT server sends an IWF group call release request to the IWF to release the ongoing session. If the IWF has joined itself to this group on behalf of all the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual joins from the group's LMR users, an individual IWF group call release request is sent to the IWF for each joined LMR user. +3. The MCPTT server sends a group call release request towards each MCPTT participant of the ongoing group call. +4. The MCPTT users are notified about the release of the group call. +5. The IWF confirms the IWF group call release request(s) received in step 2 by IWF group call release response(s) to the MCPTT server. +6. Optionally, the MCPTT client(s) receiving a group call release request may send a group call release response to the MCPTT server. +7. MCPTT client 1, client 2 and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients. + +10.3.5.6 void + +10.3.5.7 void + +10.3.5.8 Newly joined MCPTT group member of a group defined in the LMR system + +Procedures in figure 10.3.5.8-1 are those for a group member entering an ongoing MCPTT group call, i.e. performing a late entry. + +Pre-conditions: + +1. The MCPTT client is registered and the MCPTT user has been authenticated and authorized to use the MCPTT service. +2. There is an ongoing group call on the group homed on the LMR system. +3. The MCPTT client has not yet joined the group call. +4. The MCPTT user indicates to join the group call. + +![Sequence diagram illustrating the late entry of a newly joined MCPTT group member. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. Steps include: 1. Group join request from client to server; 2. IWF group join request from server to IWF; 3. IWF group join response from IWF to server; 4. Group join response from server to client; 5. Media plane establishment between client and IWF; 6. Notify users (optional); 7a. IWF Floor taken from IWF to server; 7b. Floor taken from server to client; 8. Media plane signaling using floor control between client and IWF.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of IWF: 6. Notify users + + MCPTT client->>MCPTT server: 1. Group join request + MCPTT server->>IWF: 2. IWF group join request + IWF-->>MCPTT server: 3. IWF group join response + MCPTT server-->>MCPTT client: 4. Group join response + Note over MCPTT client, IWF: 5. Media plane establishment + IWF-->>MCPTT server: 7a. IWF Floor taken + MCPTT server-->>MCPTT client: 7b. Floor taken + Note over MCPTT client, IWF: 8. Media plane signaling using floor control + +``` + +Sequence diagram illustrating the late entry of a newly joined MCPTT group member. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. Steps include: 1. Group join request from client to server; 2. IWF group join request from server to IWF; 3. IWF group join response from IWF to server; 4. Group join response from server to client; 5. Media plane establishment between client and IWF; 6. Notify users (optional); 7a. IWF Floor taken from IWF to server; 7b. Floor taken from server to client; 8. Media plane signaling using floor control between client and IWF. + +**Figure 10.3.5.8-1: Late entry of a newly joined MCPTT group member** + +1. The MCPTT client sends a group join request with the MCPTT group ID of the desired group to the MCPTT server. If there is a request to transmit, then the group joint request contains an indication of an implicit floor request. +2. The MCPTT server forwards the request to the IWF. +3. The IWF replies with a group join response indicating the acceptance of the group join request. +4. The MCPTT server forwards the response to the MCPTT client. +5. The IWF establishes the media plane with the MCPTT client. +6. The IWF may notify its users that an MCPTT user has joined the group. +- 7 a. The IWF sends an IWF floor taken (for the current talker) to the MCPTT server if the floor has been taken. +- 7b. The MCPTT responds to any incoming IWF floor taken message by forwarding a floor taken message to the MCPTT client. +8. Floor control will continue to be used by the floor participants. + +### 10.3.5.9 Newly joined LMR group member of a group defined in the MCPTT system + +Procedures in figure 10.3.5.9-1 are those for the IWF entering an ongoing MCPTT group call, i.e. performing a late entry. + +Pre-conditions: + +1. MCPTT user 1 and MCPTT user 2 have previously joined to the group. +2. MCPTT users using MCPTT client 1 and MCPTT client 2 are in an ongoing group call. +3. The IWF has not yet joined the group call. + +![Sequence diagram illustrating the late entry of a newly joined LMR group member. The diagram shows interactions between IWF, MCPTT server, MCPTT user 1, and MCPTT user 2. The IWF sends a group join request to the server, which performs authorization and establishes a media plane. The server then notifies users and provides floor control information.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT user 1 + participant MCPTT user 2 + Note right of MCPTT server: 2. Perform implicit affiliation and check user authorization + Note left of MCPTT user 1: 4. Media plane establishment + Note right of MCPTT user 2: 5. Notify users + IWF->>MCPTT server: 1. Group join request + MCPTT server-->>IWF: 3. Group join response + MCPTT server->>IWF: 6. Floor taken + Note over MCPTT user 1, MCPTT user 2: 7. Media plane signaling using floor control + +``` + +Sequence diagram illustrating the late entry of a newly joined LMR group member. The diagram shows interactions between IWF, MCPTT server, MCPTT user 1, and MCPTT user 2. The IWF sends a group join request to the server, which performs authorization and establishes a media plane. The server then notifies users and provides floor control information. + +**Figure 10.3.5.9-1: Late entry of a newly joined LMR group member** + +1. The IWF sends a group join request with the MCPTT group ID of the desired group and either using the MCPTT ID corresponding to the LMR group member or using the pre-configured MCPTT ID for use when the IWF is affiliating itself on behalf of the group's LMR users. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. If the group join request includes an implicit floor request it may also include location information. +2. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation using the MCPTT ID used by the IWF (if the IWF or the LMR user is not already affiliated to the group) and verifies that IWF is authorized to affiliate to the group. +3. The MCPTT server replies with a group join response indicating the acceptance of the group join request. +4. The MCPTT server establishes the media plane between the IWF and the MCPTT server. +5. MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the IWF joining the group call. +6. The MCPTT server sends a floor taken (for the current talker) to the IWF. +7. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF. + +### 10.3.5.10 MCPTT client returning to coverage on a group homed in the LMR system + +Procedures in figure 10.3.5.10-1 are those for an MCPTT client returning to coverage during an ongoing MCPTT chat group call. + +Pre-conditions: + +1. The MCPTT user using an MCPTT client is in an ongoing chat group call when the MCPTT client goes out of radio coverage. + +![Sequence diagram illustrating the late entry of an MCPTT client returning from out of coverage. The diagram shows three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT client returns to coverage (from client to server); 2. Re-establish media plane (between client and IWF); 3a. IWF Floor taken (from IWF to server); 3b. Floor taken (from server to client); 4. Media plane signaling using floor control (bidirectional between client and IWF).](b35ea3e304aad7d350a9902270413930_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT client: 1. MCPTT client returns to coverage + MCPTT client->>IWF: 2. Re-establish media plane + IWF->>MCPTT server: 3a. IWF Floor taken + MCPTT server->>MCPTT client: 3b. Floor taken + MCPTT client->>IWF: 4. Media plane signaling using floor control + IWF->>MCPTT client: 4. Media plane signaling using floor control + +``` + +Sequence diagram illustrating the late entry of an MCPTT client returning from out of coverage. The diagram shows three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT client returns to coverage (from client to server); 2. Re-establish media plane (between client and IWF); 3a. IWF Floor taken (from IWF to server); 3b. Floor taken (from server to client); 4. Media plane signaling using floor control (bidirectional between client and IWF). + +**Figure 10.3.5.10-1: Late entry of a MCPTT client returning from out of coverage** + +1. The MCPTT client or MCPTT server detects that MCPTT client has returned to coverage. + +NOTE: How the MCPTT client or MCPTT server detects that the client has returned to coverage is out of scope of the present document. + +2. The media plane between the MCPTT client and the IWF are re-established using media plane control signalling +- 3a. The IWF sends an IWF floor taken to the MCPTT server if anyone currently has the floor. +- 3b. The MCPTT server forwards a floor taken message to the MC Client if anyone currently has the floor. +4. Floor control will continue to be used by the floor participants. + +## 10.3.6 Exiting group call due to de-affiliation + +### 10.3.6.1 General + +The following procedures are applicable both for the pre-arranged and chat group calls. + +### 10.3.6.2 Exiting group call defined in the LMR system due to de-affiliation + +Procedures in figure 10.3.6.2-1 are the signalling control plane procedures for the IWF requesting a newly de-affiliated MCPTT user to leave an ongoing MCPTT group call. + +Pre-conditions: + +1. The MCPTT group is previously defined on the IWF with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID. +2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call. + +![Sequence diagram illustrating the exit from an MCPTT group call due to de-affiliation. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The process starts with an ongoing group call between the MCPTT client and an LMR user. The MCPTT client is de-affiliated from the group. The IWF sends a group call leave request to the MCPTT server, which is forwarded to the MCPTT client. The MCPTT client notifies the user and sends a group call leave response, which is forwarded by the MCPTT server to the IWF. Finally, the MCPTT client is removed from the ongoing group call.](c3254408eadbf152632a8faf16310722_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client + Note right of MCPTT client: 0. Group call ongoing between the MCPTT client and an LMR user + Note left of IWF: 1. The MCPTT client has been de-affiliated from the MCPTT group + IWF->>MCPTT server: 2. IWF group call leave request + MCPTT server->>MCPTT client: 3. Group call leave request + Note right of MCPTT client: 4. Notify user + MCPTT client->>MCPTT server: 5. Group call leave response + MCPTT server->>IWF: 6. IWF group call leave response + Note right of MCPTT client: 7. The MCPTT client is removed from the ongoing group call + +``` + +Sequence diagram illustrating the exit from an MCPTT group call due to de-affiliation. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The process starts with an ongoing group call between the MCPTT client and an LMR user. The MCPTT client is de-affiliated from the group. The IWF sends a group call leave request to the MCPTT server, which is forwarded to the MCPTT client. The MCPTT client notifies the user and sends a group call leave response, which is forwarded by the MCPTT server to the IWF. Finally, the MCPTT client is removed from the ongoing group call. + +**Figure 10.3.6.2-1: Exiting MCPTT group call due to de-affiliation** + +1. The MCPTT client is de-affiliated. +2. The IWF sends an IWF group call leave request to the MCPTT client via the MCPTT server. +3. The MCPTT server forwards the IWF group call leave request as a group call leave request to the MCPTT client. +4. The MCPTT user at the MCPTT client is notified about leaving the group call. +5. The MCPTT client sends the group call leave response to the MCPTT server and leaves the group call. +6. The MCPTT server forwards the group call leave response to the IWF as an IWF group call leave response. +7. The MCPTT client is now removed from the ongoing group call. + +### 10.3.6.3 Exiting group call defined in the MCPTT system due to de-affiliation + +Procedures in figure 10.3.6.3-1 are the signalling control plane procedures for the MCPTT server requesting a newly de-affiliated LMR user to leave an ongoing MCPTT group call. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID. +2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call. + +![Sequence diagram illustrating the exit from an MCPTT group call due to de-affiliation. The diagram shows three participants: IWF, MCPTT server, and MCPTT client. The process starts with an ongoing group call (0). The LMR user is de-affiliated (1). The MCPTT server sends a leave request to the IWF (2). The IWF sends a leave response (3). Finally, the LMR user is removed from the call (4).](24ca460ee3381aee781887e9e586ec67_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note over IWF, MCPTT_server, MCPTT_client: 0. Group call ongoing between the MCPTT client and an LMR user + Note over MCPTT_server: 1. The LMR user has been de-affiliated from the MCPTT group + MCPTT_server->>IWF: 2. IWF group call leave request + IWF-->>MCPTT_server: 3. IWF group call leave response + Note over IWF, MCPTT_server, MCPTT_client: 4. The LMR user is removed from the ongoing group call + +``` + +Sequence diagram illustrating the exit from an MCPTT group call due to de-affiliation. The diagram shows three participants: IWF, MCPTT server, and MCPTT client. The process starts with an ongoing group call (0). The LMR user is de-affiliated (1). The MCPTT server sends a leave request to the IWF (2). The IWF sends a leave response (3). Finally, the LMR user is removed from the call (4). + +**Figure 10.3.6.3-1: Exiting MCPTT group call due to de-affiliation** + +1. The LMR user represented by the IWF has been de-affiliated. +2. The MCPTT server sends an IWF group call leave request to the LMR user via the IWF. +3. The IWF sends an IWF group call leave response to the MCPTT server and leaves the group call. +4. The LMR user represented by the IWF is now removed from the ongoing group call. + +## 10.3.7 Group regroup with pre-configured group + +### 10.3.7.1 General + +A group regroup may be achieved by regrouping MCPTT groups into a new regroup group which uses the configuration of a separate pre-configured MCPTT group. The MCPTT group configuration needs to be provided to the relevant MCPTT group members of the MCPTT groups that will be regrouped in advance of the regrouping operation. + +NOTE 1: A pre-configured group which is intended only to provide configuration for the pre-configured group regroup process is identified by a parameter in group configuration described in 3GPP TS 23.280 [5]. + +NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the IWF and the user profile of all the relevant MCPTT users who will be regrouped. + +NOTE 3: Pre-configured group regroups may be defined according to the organizational structure of a mission critical organization, or by some other means which allows the MCPTT client of an authorized user and the IWF to be aware of an appropriate pre-configured group regroup for sets of MCPTT groups that will be regrouped together. + +The pre-configured MCPTT group that provides the configuration is not used as the pre-configured group regroup itself, it only provides configuration for one or more pre-configured group or user regroup. The MCPTT group ID of the pre-configured group regroup is provided by the authorized user or the IWF (for the case where the IWF owns the pre-configured group regroup) when the pre-configured group regrouping is carried out. + +The pre-configured group regroup can be specified to be a broadcast or non-broadcast type according to the configuration of the MCPTT group whose configuration is specified by the pre-configured group regroup request. The broadcast type of pre-configured group regroup is used for one-way communication where only an authorized user or the IWF (for the case where the IWF owns the pre-configured group regroup) is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast type is used for two-way communication where all regroup members can transmit and receive (i.e., the pre-configured group regroup call behaves like a normal non-broadcast group call). + +These procedures provide a regrouping service for MCPTT only and are independent of group regrouping procedures specified in subclause 10.2.2. If one of the MCPTT groups that has been requested for regrouping by means of this procedure has already been regrouped by the group regrouping procedure specified in 3GPP TS 23.280 [5] or subclause 10.2.2, the request for regrouping shall be rejected. The rules for regrouping set forth in subclause 10.2.2.5 apply. + +## 10.3.7.2 Regroup formation using pre-configured group + +### 10.3.7.2.1 Regroup formation using pre-configured group initiated in the MCPTT system + +Figure 10.3.7.2.1-1 illustrates the procedure to initiate a regroup procedure using a pre-configured MCPTT regroup group, where at least one of the groups to be regrouped is configured in the IWF. The group management server in the MCPTT system of the regroup group shares the necessary security related parameters together with the group configuration of the pre-configured group regroup with the group management server in the IWF; the MCPTT system does not need to be aware of the group members of the pre-configured group regroup that are receiving service in the IWF. + +The procedure takes place prior to the establishment of a group call to the pre-configured group regroup. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is authorized to initiate a pre-configured group regroup procedure, and is receiving MCPTT service in the MCPTT system. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the IWF, and the IWF has received the relevant security related information to allow communication in the pre-configured group regroup. +- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS. +- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in 3GPP TS 23.280 [5]. +- The IWF is affiliated to one or more of the MCPTT groups that will be regrouped; and/or, the IWF may own one or more of MCPTT groups to be regrouped. +- The pre-configured group regroup is homed in the MCPTT server. +- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup. + +NOTE 1: The IWF has the configuration information contained in the pre-configured group regroup, which is normally because at least one member of the pre-configured group regroup is homed on the IWF. + +![Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate Pre-configured regroup (from client to server), 2. Pre-configured regroup request (from client to server), 3. Check authorization and resolve group IDs (internal to server), 4. IWF pre-configured regroup request (from server to IWF), 5. IWF pre-configured regroup response (from IWF to server), and 6. Preconfigured regroup response (from server to client).](c06fd7dbef68a8b788158f2081d9d734_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Initiate Pre-configured regroup + MCPTT client->>MCPTT server: 2. Pre-configured regroup request + Note right of MCPTT server: 3. Check authorization and resolve group IDs + MCPTT server->>IWF: 4. IWF pre-configured regroup request + IWF-->>MCPTT server: 5. IWF pre-configured regroup response + MCPTT server-->>MCPTT client: 6. Preconfigured regroup response + +``` + +Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate Pre-configured regroup (from client to server), 2. Pre-configured regroup request (from client to server), 3. Check authorization and resolve group IDs (internal to server), 4. IWF pre-configured regroup request (from server to IWF), 5. IWF pre-configured regroup response (from IWF to server), and 6. Preconfigured regroup response (from server to client). + +**Figure 10.3.7.2.1-1: Regroup procedure using pre-configured group initiated in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. + 2. The MCPTT client sends the pre-configured regroup request to the MCPTT server. + 3. The MCPTT server checks that the MCPTT client is authorized to initiate a pre-configured group regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the MCPTT system. The MCPTT server identifies any partner systems or IWFs which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server. +- NOTE 2: This procedure does not require that that the authorized user of the MCPTT client is a group member of the MCPTT groups listed in the pre-configured group regroup request, or that the authorized user of the MCPTT client is an affiliated group member of any of the listed MCPTT groups. +4. The MCPTT server sends an IWF pre-configured regroup requests to the IWF. +- NOTE 3: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a pre-configured regroup request. +5. The IWF sends an IWF pre-configured regroup response to the MCPTT server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping) + 6. The MCPTT server sends the pre-configured regroup response to the MCPTT client. + +After the pre-configured group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.7.3. + +Participation by the IWF in the ongoing pre-configured group regroup persists until the IWF is no longer affiliated to any of the regrouped groups. + +### 10.3.7.2.2 Regroup formation using pre-configured group initiated in the IWF + +Figure 10.3.7.2.2-1 illustrates the procedure to initiate a pre-configured group regroup procedure using a pre-configured MCPTT group, where at least one of the groups to be regrouped is configured in an MCPTT system. The group management server in the IWF shares the necessary security related parameters together with the group configuration of the MCPTT regroup group with the group management server in the MCPTT system and the group management server in the MCPTT system distributes this configuration including those security parameters to its served MCPTT users according to the procedures in 3GPP TS 23.280 [5] subclause 10.2.7; the IWF does not need to be aware of the list of group members of the pre-configured group regroup that are receiving service in the MCPTT system. The group can have multiple MCPTT clients, but only one MCPTT client involved in the session is shown for simplicity. + +The procedure takes place prior to the establishment of a group call to the pre-configured group regroup. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the MCPTT system. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow communication in the pre-configured group regroup. +- The pre-configured group regroup is homed in the IWF. +- The MCPTT system is home to at least one group that's a constituent group of the pre-configured group regroup. + +NOTE 1: The MCPTT system has the configuration information contained in the pre-configured group, which is normally because at least one member of the preconfigured group is homed on the MCPTT system. + +![Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the IWF. The diagram shows three participants: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server); 2. Check requested groups and identify affiliated group members (internal MCPTT server step); 3. Pre-configured regroup request (MCPTT server to MCPTT client); 4. Notify user (internal MCPTT client step); 5. Pre-configured regroup response (MCPTT client to MCPTT server, dashed line); 6. Affiliate MCPTT clients to regroup group (internal MCPTT server step); 7. IWF pre-configured regroup response (MCPTT server to IWF).](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_server: 2. Check requested groups and identify affiliated group members + Note right of MCPTT_client: 4. Notify user + Note right of MCPTT_server: 6. Affiliate MCPTT clients to regroup group + IWF->>MCPTT_server: 1. IWF pre-configured regroup request + MCPTT_server-->>MCPTT_client: 3. Pre-configured regroup request + MCPTT_client-->>MCPTT_server: 5. Pre-configured regroup response + MCPTT_server->>IWF: 7. IWF pre-configured regroup response + +``` + +Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the IWF. The diagram shows three participants: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server); 2. Check requested groups and identify affiliated group members (internal MCPTT server step); 3. Pre-configured regroup request (MCPTT server to MCPTT client); 4. Notify user (internal MCPTT client step); 5. Pre-configured regroup response (MCPTT client to MCPTT server, dashed line); 6. Affiliate MCPTT clients to regroup group (internal MCPTT server step); 7. IWF pre-configured regroup response (MCPTT server to IWF). + +**Figure 10.3.7.2.2-1: Regroup procedure using pre-configured group initiated in the IWF** + +1. The IWF initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. The IWF sends the IWF pre-configured regroup request to the MCPTT server in the partner MCPTT system. +2. The MCPTT server checks the status of any MCPTT groups hosted by itself, and identifies affiliated group members of any of the identified MCPTT groups (both MCPTT groups that are hosted in the MCPTT system + +and MCPTT groups that are hosted in the IWF) that are receiving MCPTT service in the MCPTT system, which includes the MCPTT client. + +3. The MCPTT server sends a pre-configured regroup request to the MCPTT client. + +NOTE 2: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a pre-configured regroup request. + +4. The MCPTT client notifies the user of the regrouping. +5. The MCPTT client 2 may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup request. +6. The MCPTT server affiliates the regrouped MCPTT client to the pre-configured group regroup. +7. The MCPTT server sends an IWF pre-configured regroup response to the IWF. + +After the pre-configured group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.7.3. + +MCPTT client participation in the ongoing pre-configured group regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups. + +MCPTT client affiliation to the pre-configured group regroup may cease when the clients MCPTT service ceases, e.g. when the UE is powered down, or by the client performing a log-off operation. + +### 10.3.7.3 Regroup cancellation using pre-configured group regroup + +#### 10.3.7.3.1 Regroup cancellation using pre-configured group initiated in the MCPTT system + +Figure 10.3.7.3.1-1 illustrates the procedure to cancel a regrouping that uses a pre-configured MCPTT regroup group where there the regroup had been initiated in the MCPTT system. + +Pre-conditions: + +- The IWF has been regrouped into the pre-configured group regroup. +- The MCPTT client is authorized to cancel a pre-configured group regroup. +- The GMS has subscribed to the group dynamic data specified in 3GPP TS 23.280 [5] subclause 10.1.5.5.1 from the MCPTT server as specified in 3GPP TS 23.280 [5] subclause 10.1.5.6. + +![Sequence diagram for regroup cancellation using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate Pre-configured regroup (from client to server), 2. Preconfigured regroup cancel request (from client to server), 3. Check authorization (internal to server), 4. IWF pre-configured regroup cancel request (from server to IWF), 5. IWF pre-configured regroup cancel response (from IWF to server), 6. Pre-configured regroup cancel response (from server to client).](3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Initiate Pre-configured regroup + MCPTT client->>MCPTT server: 2. Preconfigured regroup cancel request + Note right of MCPTT server: 3. Check authorization + MCPTT server->>IWF: 4. IWF pre-configured regroup cancel request + IWF-->>MCPTT server: 5. IWF pre-configured regroup cancel response + MCPTT server-->>MCPTT client: 6. Pre-configured regroup cancel response +``` + +Sequence diagram for regroup cancellation using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate Pre-configured regroup (from client to server), 2. Preconfigured regroup cancel request (from client to server), 3. Check authorization (internal to server), 4. IWF pre-configured regroup cancel request (from server to IWF), 5. IWF pre-configured regroup cancel response (from IWF to server), 6. Pre-configured regroup cancel response (from server to client). + +**Figure 10.3.7.3.1-1: Regroup cancellation using pre-configured group initiated in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the cancellation of the pre-configured group regroup. +2. The MCPTT client sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +3. The MCPTT server checks that the MCPTT client is authorized to cancel a pre-configured group regroup. +4. The MCPTT server sends the IWF pre-configured regroup cancel request to the IWF. +5. The IWF sends the IWF pre-configured regroup cancel response to the MCPTT server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping) +6. The MCPTT server sends a pre-configured regroup cancel response to the MCPTT client. + +### 10.3.7.3.2 Regroup cancellation using pre-configured group initiated in the IWF + +Figure 10.3.7.3.2-1 illustrates the procedure to cancel a regrouping that uses a pre-configured MCPTT group where the regroup is initiated in the IWF. Only one MCPTT group member is shown for simplicity. + +Pre-conditions: + +- The MCPTT client has been regrouped into a pre-configured group regroup, and is receiving MCPTT service in the MCPTT system. + +![Sequence diagram illustrating the 'Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system'. The diagram shows interactions between IWF, MCPTT server, and MCPTT client. The steps are: 1. IWF sends a pre-configured regroup cancel request to the MCPTT server. 2. The MCPTT server sends a pre-configured regroup cancel request to the MCPTT client. 3. The MCPTT client notifies the user. 4. The MCPTT client sends a pre-configured regroup cancel response to the MCPTT server. 5. The MCPTT server deaffiliates the MCPTT client. 6. The MCPTT server sends an IWF pre-configured regroup cancel response to the IWF.](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_client: Notify user + IWF->>MCPTT_server: 1. IWF pre-configured regroup cancel request + MCPTT_server->>MCPTT_client: 2. Pre-configured regroup cancel request + MCPTT_client->>MCPTT_server: 4. Pre-configured regroup cancel response + Note over MCPTT_server: 5. Deaffiliate MCPTT client + MCPTT_server->>IWF: 6. IWF pre-configured regroup cancel response + +``` + +Sequence diagram illustrating the 'Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system'. The diagram shows interactions between IWF, MCPTT server, and MCPTT client. The steps are: 1. IWF sends a pre-configured regroup cancel request to the MCPTT server. 2. The MCPTT server sends a pre-configured regroup cancel request to the MCPTT client. 3. The MCPTT client notifies the user. 4. The MCPTT client sends a pre-configured regroup cancel response to the MCPTT server. 5. The MCPTT server deaffiliates the MCPTT client. 6. The MCPTT server sends an IWF pre-configured regroup cancel response to the IWF. + +**Figure 10.3.7.3.2-1: Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system** + +1. The IWF initiates the cancellation of the regrouping that uses a pre-configured MCPTT group. The IWF sends the IWF pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +2. The MCPTT server sends the pre-configured regroup cancel request to the MCPTT client. +3. The MCPTT client notifies the user of the cancellation of the pre-configured group regrouping. +4. The MCPTT client may send the pre-configured regroup remove response to the MCPTT server to acknowledge the cancellation of the pre-configured group regrouping. This acknowledgement is not sent in response to a multi-cast transmission of the pre-configured regroup cancel request. +5. The MCPTT server de-affiliates the MCPTT client from the pre-configured group regroup. +6. The MCPTT server sends the IWF pre-configured regroup cancel response to the IWF. + +#### 10.3.7.4 Regroup rejection using pre-configured group + +##### 10.3.7.4.1 Regroup rejection using pre-configured group for regroup initiated in the MCPTT system + +Figure 10.3.7.4.1-1 illustrates the case where the procedure to initiate a pre-configured group regroup procedure with an MCPTT system and an IWF using a pre-configured MCPTT group described in subclause 10.3.7.3.1 commences, but where the request for the regroup is rejected by the IWF, for example because one of the groups hosted by the IWF is already regrouped by other group regrouping procedures. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is authorized to initiate a pre-configured group regroup procedure. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the IWF, and the IWF has received the relevant security related information to allow communication in the pre-configured group regroup. +- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS. + +- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in 3GPP TS 23.280 [5]. +- The IWF is affiliated to one or more of the MCPTT groups that will be regrouped; and/or, the IWF may own one or more of MCPTT groups to be regrouped. + +![Sequence diagram illustrating regroup rejection using pre-configured group for group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate preconfigured regroup (from MCPTT client), 2. Preconfigured regroup request (from MCPTT client to MCPTT server), 3. Check authorization and resolve group IDs (internal to MCPTT server), 4. IWF pre-configured regroup request (from MCPTT server to IWF), 5. IWF pre-configured regroup reject (from IWF to MCPTT server), and 6. Pre-configured regroup reject (from MCPTT server to MCPTT client).](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Initiate preconfigured regroup + MCPTT client->>MCPTT server: 2. Preconfigured regroup request + Note right of MCPTT server: 3. Check authorization and resolve group IDs + MCPTT server->>IWF: 4. IWF pre-configured regroup request + IWF-->>MCPTT server: 5. IWF pre-configured regroup reject + MCPTT server-->>MCPTT client: 6. Pre-configured regroup reject + +``` + +Sequence diagram illustrating regroup rejection using pre-configured group for group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate preconfigured regroup (from MCPTT client), 2. Preconfigured regroup request (from MCPTT client to MCPTT server), 3. Check authorization and resolve group IDs (internal to MCPTT server), 4. IWF pre-configured regroup request (from MCPTT server to IWF), 5. IWF pre-configured regroup reject (from IWF to MCPTT server), and 6. Pre-configured regroup reject (from MCPTT server to MCPTT client). + +**Figure 10.3.7.4.1-1: Regroup rejection using pre-configured group for group initiated in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. +2. The MCPTT client sends the pre-configured regroup request to the MCPTT server. +3. The MCPTT server checks that the MCPTT client is authorized to initiate a pre-configured group regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the MCPTT system. The MCPTT server identifies any partner systems or IWFs which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the pre-configured group regroup from the GMS if that configuration information is not already known to the MCPTT server. + +NOTE: This procedure does not require that that the authorized user of the MCPTT client is a group member of the MCPTT groups listed in the regroup request, or that the authorized user of the MCPTT client is an affiliated group member of any of the listed MCPTT groups. + +4. The MCPTT server sends the IWF pre-configured regroup requests to the IWF. +5. The IWF sends a pre-configured regroup reject to the MCPTT server, indicating the reason for rejection, for example because one or more of the MCPTT groups has already been regrouped by another group regrouping procedure, either internal to the IWF or in an MCPTT system. +6. The MCPTT server sends a pre-configured regroup reject to the MCPTT client, indicating the reason for the rejection. + +#### 10.3.7.4.2 Regroup rejection using pre-configured group for regroup initiated in the IWF + +Figure 10.3.7.4.2 1 illustrates the case where the procedure to initiate a regroup procedure with an MCPTT system and an IWF using a pre-configured MCPTT group described in subclause 10.3.7.3.2 commences, but where the request for + +the pre-configured group regroup is rejected by the MCPTT system, for example because one of the groups hosted by the MCPTT system is already regrouped by other group regrouping procedures. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the MCPTT system. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow communication in the pre-configured group regroup. + +![Sequence diagram showing the interaction between IWF and MCPTT server for regroup rejection. The IWF sends a '1. IWF pre-configured regroup request' to the MCPTT server. The MCPTT server performs '2. Check requested groups' internally. Finally, the MCPTT server sends a '3. IWF pre-configured regroup reject' back to the IWF.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + Note right of MCPTT_server: 2. Check requested groups + IWF->>MCPTT_server: 1. IWF pre-configured regroup request + MCPTT_server-->>IWF: 3. IWF pre-configured regroup reject + +``` + +Sequence diagram showing the interaction between IWF and MCPTT server for regroup rejection. The IWF sends a '1. IWF pre-configured regroup request' to the MCPTT server. The MCPTT server performs '2. Check requested groups' internally. Finally, the MCPTT server sends a '3. IWF pre-configured regroup reject' back to the IWF. + +**Figure 10.3.7.4.2-1: Regroup rejection using pre-configured group for group initiated in the IWF** + +1. The IWF initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. The IWF sends the IWF pre-configured regroup request to the MCPTT server. +2. The MCPTT server checks the status of any MCPTT groups hosted by that MCPTT server, and determines that one or more requested MCPTT groups has already been regrouped by another group regrouping procedure. +3. The partner MCPTT server sends an IWF pre-configured regroup reject to the IWF, indicating the reason for rejection. + +## 10.3.7.5 Pre-configured regroup update procedures + +### 10.3.7.5.1 MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup + +Figure 10.3.7.5.1-1 illustrates the procedure when a user attempts to set up a MCPTT group call on a group involved in an in-progress pre-configured group regroup, homed in the IWF. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group A that is part of an in-progress pre-configured group regroup with MCPTT groups B and C. MCPTT groups A, B and C can be homed in either the IWF or the MCPTT system. +- MCPTT group D is being used as the pre-configured group regroup. MCPTT group D is homed in the IWF. +- The MCPTT client has missed the pre-configured regroup request message (e.g. poor signalling conditions, race condition). + +![Sequence diagram showing the procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup. The diagram involves three main participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Group call request (MCPTT client to MCPTT server), 2. IWF group call request (MCPTT server to IWF), 3. IWF group call response (IWF to MCPTT server), 4. Group call response (MCPTT server to MCPTT client), 5. IWF preconfigured regroup request (IWF to MCPTT server), 6. Preconfigured regroup request (MCPTT server to MCPTT client), 7. Notify user (MCPTT client internal), 8. Preconfigured regroup response (MCPTT client to MCPTT server), 9. IWF preconfigured regroup response (MCPTT server to IWF).](e93f2f4b0bf7e94139c1a2f1357962da_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 7. Notify user + MCPTT client->>MCPTT server: 1. Group call request + MCPTT server->>IWF: 2. IWF group call request + IWF-->>MCPTT server: 3. IWF group call response + MCPTT server-->>MCPTT client: 4. Group call response + IWF->>MCPTT server: 5. IWF preconfigured regroup request + MCPTT server->>MCPTT client: 6. Preconfigured regroup request + MCPTT client->>MCPTT server: 8. Preconfigured regroup response + MCPTT server->>IWF: 9. IWF preconfigured regroup response + +``` + +Sequence diagram showing the procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup. The diagram involves three main participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Group call request (MCPTT client to MCPTT server), 2. IWF group call request (MCPTT server to IWF), 3. IWF group call response (IWF to MCPTT server), 4. Group call response (MCPTT server to MCPTT client), 5. IWF preconfigured regroup request (IWF to MCPTT server), 6. Preconfigured regroup request (MCPTT server to MCPTT client), 7. Notify user (MCPTT client internal), 8. Preconfigured regroup response (MCPTT client to MCPTT server), 9. IWF preconfigured regroup response (MCPTT server to IWF). + +**Figure 10.3.7.5.1-1: Procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup** + +1. The MCPTT client attempts to start a call on MCPTT group A. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group A as the target group. +2. The MCPTT server forwards the request to the IWF as an IWF group call request. +3. The IWF sends an IWF group call response to the MCPTT server indicating that the call set up is denied because the group is part of an in-progress pre-configured group regroup. +4. The MCPTT server forwards the response to the MCPTT client as a group call response. +5. The IWF sends an IWF pre-configured regroup request to the MCPTT server containing MCPTT group D, the group ID of the pre-configured group regroup. +6. The MCPTT server forwards the request to the MCPTT client as a pre-configured regroup request. +7. The MCPTT client notifies the user of the group call set up failure and of the regrouping procedure. + +NOTE 1: Step 5 can occur prior to step 4 and step 7 can occur after step 4. + +8. The MCPTT client sends the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. +9. The MCPTT server forwards the response to the IWF as an IWF pre-configured regroup response. The IWF affiliates the regrouped MCPTT client to the pre-configured group regroup. + +NOTE 2: If there is a call currently in progress on the pre-configured group regroup then this MCPTT client can be added to the call using the late entry procedure. If there is no call currently in progress, then the MCPTT user can retry the group call set up. + +### 10.3.7.6 Call request on pre-configured regroup group after group regroup has been cancelled + +#### 10.3.7.6.1 MCPTT client PTTs on pre-configured regroup group after group regroup has been cancelled + +Figure 10.3.7.6.1-1 illustrates the procedure when an MCPTT user attempts to set up a MCPTT group call on a pre-configured regroup group after the pre-configured MCPTT group regroup has been cancelled. + +Pre-conditions: + +- The MCPTT client is a member of MCPTT group A that was part of an in-progress pre-configured group regroup with MCPTT groups B and C that has been cancelled. MCPTT group D was used as the pre-configured regroup group. MCPTT group D is homed in the IWF. +- The MCPTT client has missed the pre-configured regroup cancel request message (e.g. poor signalling conditions, race condition). + +![Sequence diagram illustrating the procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled. The diagram shows interactions between MCPTT client, MCPTT server, and IWF.](78de09c382ab51b5c3e87979204228c8_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 7. Notify user + MCPTT client->>MCPTT server: 1. Group call request + MCPTT server->>IWF: 2. IWF group call request + IWF-->>MCPTT server: 3. IWF group call response + MCPTT server-->>MCPTT client: 4. Group call response + IWF-->>MCPTT server: 5. IWF preconfigured regroup cancel request + MCPTT server-->>MCPTT client: 6. Preconfigured regroup cancel request + MCPTT client->>MCPTT server: 8. Preconfigured regroup cancel response + MCPTT server-->>IWF: 9. IWF preconfigured regroup cancel response + +``` + +Sequence diagram illustrating the procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. + +**Figure 10.3.7.6.1-1: Procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled** + +1. The MCPTT client attempts to start a call on MCPTT group D, the pre-configured regroup group. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group D as the target group. +2. The MCPTT server forwards the request to the IWF as an IWF group call request. + +NOTE 1: The pre-configured regroup group D can be a group in the MCPTT client's profile, and the MCPTT client can be a member of group D. + +3. The IWF sends an IWF group call response to the MCPTT server indicating that the call set up is denied because the group regroup is no longer active. +4. The MCPTT server forwards the response to the MCPTT client as a group call response + +NOTE 2: In the following, steps 5, 6, 8 and 9 are optional. + +5. The IWF sends an IWF pre-configured regroup cancel request to the MCPTT server. +6. The MCPTT server forwards the request as a pre-configured regroup cancel request to the MCPTT client. + +NOTE 3: This message should be sent over unicast. + +7. The MCPTT client notifies the user of the group call set up failure and of the regrouping cancellation. +8. The MCPTT client sends a pre-configured regroup cancel response to the MCPTT server to acknowledge the regrouping cancellation. +9. The MCPTT server forwards the response to the IWF as an IWF pre-configured regroup cancel response. + +### 10.3.7.7 Adding newly affiliated user to a pre-configured group regroup + +#### 10.3.7.7.1 Adding newly affiliated MCPTT user to a pre-configured group regroup + +Figure 10.3.7.7.1-1 illustrates the procedure to add a newly affiliated MCPTT user to an in-progress pre-configured group regroup operation. + +Pre-conditions: + +- The MCPTT client is a member of, but not yet affiliated with, a MCPTT group that is part of an in-progress pre-configured group regroup operation. +- The MCPTT group identity and group configuration for the regroup MCPTT group has been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow it to communicate in the pre-configured group regroup. + +![Sequence diagram illustrating the procedure to add a newly affiliated user to a pre-configured group regroup. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Group affiliation (MCPTT client to MCPTT server), 2. IWF pre-configured regroup request (IWF to MCPTT server), 3. Pre-configured regroup request (MCPTT server to MCPTT client), 4. Notify user (MCPTT client internal message), 5. IWF pre-configured regroup response (MCPTT client to MCPTT server), and 6. IWF pre-configured regroup response (MCPTT server to IWF).](4430c1d8e78ac97fda782321410349a9_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT client: 1. Group affiliation + IWF->>MCPTT server: 2. IWF pre-configured regroup request + MCPTT server->>MCPTT client: 3. Pre-configured regroup request + Note left of MCPTT client: 4. Notify user + MCPTT client->>MCPTT server: 5. IWF pre-configured regroup response + MCPTT server->>IWF: 6. IWF pre-configured regroup response +``` + +Sequence diagram illustrating the procedure to add a newly affiliated user to a pre-configured group regroup. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Group affiliation (MCPTT client to MCPTT server), 2. IWF pre-configured regroup request (IWF to MCPTT server), 3. Pre-configured regroup request (MCPTT server to MCPTT client), 4. Notify user (MCPTT client internal message), 5. IWF pre-configured regroup response (MCPTT client to MCPTT server), and 6. IWF pre-configured regroup response (MCPTT server to IWF). + +**Figure 10.3.7.7.1-1: Procedure to add a newly affiliated user to a pre-configured group regroup** + +1. The MCPTT client affiliates to an MCPTT group that is currently part of an in-progress pre-configured group regroup. The affiliation follows the procedure in subclause 10.1.2.4. +2. The IWF sends an IWF pre-configured regroup request to the MCPTT server. +3. The MCPTT server sends a pre-configured regroup request to the MCPTT client. +4. The MCPTT client notifies the user of the regrouping. +5. The MCPTT client may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the pre-configured regroup request. + +6. The MCPTT server sends an IWF pre-configured regroup response to the IWF. The IWF affiliates the MCPTT client to the group regroup. + +### 10.3.7.7.2 Adding newly affiliated user homed in the IWF to a pre-configured group regroup + +Figure 10.3.7.7.2-1 illustrates the procedure to add a newly affiliated user homed in the IWF to an in-progress pre-configured group regroup operation. + +Pre-conditions: + +- The LMR user is a member of, but not yet affiliated to, an MCPTT group that is part of an in-progress pre-configured group regroup operation. +- The MCPTT group identity and group configuration for the pre-configured group regroup has been pre-configured in the IWF, and the IWF has received the relevant security related information to allow it to communicate in the pre-configured group regroup. + +![Sequence diagram illustrating the procedure to add a newly affiliated user to a pre-configured regroup. The diagram shows interactions between the IWF and the MCPTT server. The steps are: 1. Group affiliation (IWF to MCPTT server), 2. Retrieve regroup information (MCPTT server internal), 3. IWF pre-configured regroup request (MCPTT server to IWF), 4. IWF pre-configured regroup response (IWF to MCPTT server), and 5. Affiliate user to the regroup group (MCPTT server internal).](afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg) + +``` +sequenceDiagram + participant IWF + participant MCPTT server + Note right of MCPTT server: 1. Group affiliation + Note right of MCPTT server: 2. Retrieve regroup information + MCPTT server->>IWF: 3. IWF pre-configured regroup request + IWF->>MCPTT server: 4. IWF pre-configured regroup response + Note right of MCPTT server: 5. Affiliate user to the regroup group +``` + +Sequence diagram illustrating the procedure to add a newly affiliated user to a pre-configured regroup. The diagram shows interactions between the IWF and the MCPTT server. The steps are: 1. Group affiliation (IWF to MCPTT server), 2. Retrieve regroup information (MCPTT server internal), 3. IWF pre-configured regroup request (MCPTT server to IWF), 4. IWF pre-configured regroup response (IWF to MCPTT server), and 5. Affiliate user to the regroup group (MCPTT server internal). + +**Figure 10.3.7.7.2-1: Procedure to add a newly affiliated user to a pre-configured regroup** + +1. The IWF affiliates to an MCPTT group that is currently part of an in-progress pre-configured group regroup. The affiliation follows the procedure in subclause 10.1.2.2. +2. The MCPTT server retrieves the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. +3. The MCPTT server sends an IWF pre-configured regroup request to the IWF. +4. The IWF sends an IWF pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. +5. The MCPTT server affiliates the IWF to the group regroup. + +## 10.3.8 User regroup with pre-configured group + +### 10.3.8.1 General + +A user regroup may be achieved by regrouping MCPTT users into a new regroup group which uses the configuration of a separate pre-configured MCPTT group. The MCPTT regroup group configuration needs to be provided to the relevant MCPTT users who will be regrouped in advance of the regrouping operation. A pre-configured user regroup may + +contain users homed in the IWF and the IWF may host pre-configured user regroups which may contain members homed in an MCPTT system. + +NOTE 1: A pre-configured group which is intended only to provide configuration for the pre-configured user regroup process is identified by a parameter in group configuration described in 3GPP TS 23.280 [5]. + +NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the user profile of all of the relevant MCPTT users who will be regrouped and that has also been configured to the IWF for the case where the pre-configured user regroup contains members homed in the IWF. + +The pre-configured user regroup that provides the configuration is not used as the pre-configured user regroup itself, it only provides configuration for one or more pre-configured user regroups. The MCPTT group ID of the pre-configured user regroup is provided by the originating authorized user or the originating IWF when the pre-configured user regrouping is carried out. + +## 10.3.8.2 Pre-configured user regroup formation + +### 10.3.8.2.1 Pre-configured user regroup formation by the MCPTT system + +Figure 10.3.8.2.1-1 illustrates the procedure to initiate a pre-configured user regroup procedure using a pre-configured user regroup. The procedure takes place prior to the establishment of a group call to the pre-configured user regroup. + +Pre-conditions: + +- MCPTT clients 2 and 3 are registered with the MCPTT service. +- An MCPTT group that will be used for configuration of the pre-configured user regroup has been pre-configured in MCPTT clients 2 and 3 and the IWF, and MCPTT clients 2 and 3 and the IWF have received the relevant security related information to allow them to communicate in the pre-configured user regroup. +- MCPTT client 1 is authorized to initiate a pre-configured user regroup using the pre-configured user regroup procedure. +- MCPTT client 1 is aware of a suitable pre-configured group whose configuration has been pre-configured in the MC service clients of the MCPTT users who will be regrouped. +- The pre-configured user regroup is homed in the MCPTT server. + +![Sequence diagram of the user regroup procedure using a pre-configured group by the MCPTT system. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3, and IWF. The sequence starts with MCPTT client 1 initiating a preconfigured user regroup, followed by a request to the server, authorization check, requests to clients 2 and 3, user notifications, responses from clients 2 and 3, a request to the IWF, a response from the IWF, affiliation of clients to the regroup group, and finally a response back to client 1.](2b60ebe01f77d22e53da1fbe73083b01_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + participant IWF + + Note left of MCPTT client 1: 1. Initiate preconfigured User regroup + MCPTT client 1->>MCPTT server: 2. Preconfigured regroup request + Note right of MCPTT server: 3. Check authorizations + MCPTT server->>MCPTT client 2: 4a. Pre-configured regroup request + MCPTT server->>MCPTT client 3: 4b. Pre-configured regroup request + Note right of MCPTT client 2: 5a. Notify user + Note right of MCPTT client 3: 5b. Notify user + MCPTT client 2-->>MCPTT server: 6a. Preconfigured regroup response + MCPTT client 3-->>MCPTT server: 6b. Preconfigured regroup response + MCPTT server->>IWF: 7. IWF pre-configured regroup request + IWF-->>MCPTT server: 8. IWF pre-configured regroup response + Note right of MCPTT server: 9. Affiliate MCPTT clients to regroup group + MCPTT server-->>MCPTT client 1: 10. Preconfigured regroup response + +``` + +Sequence diagram of the user regroup procedure using a pre-configured group by the MCPTT system. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3, and IWF. The sequence starts with MCPTT client 1 initiating a preconfigured user regroup, followed by a request to the server, authorization check, requests to clients 2 and 3, user notifications, responses from clients 2 and 3, a request to the IWF, a response from the IWF, affiliation of clients to the regroup group, and finally a response back to client 1. + +**Figure 10.3.8.2.1-1: User regroup procedure using pre-configured group by the MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the pre-configured user regroup procedure, specifying the list of MCPTT users to be regrouped (MCPTT clients 2, 3 and one or more IWF users), the MCPTT group ID of the pre-configured user regroup, and the MCPTT group ID of the group from which configuration information for the pre-configured user regroup is to be taken. + 2. MCPTT client 1 sends the pre-configured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation. + 3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a pre-configured user regroup procedure. +- NOTE 1: MCPTT clients and users homed in the IWF can be involved in multiple user and group regroups simultaneously. +4. The MCPTT server sends the pre-configured regroup requests to MCPTT clients 2 and 3 in steps 4a and 4b respectively. + 5. MCPTT clients 2 and 3 notify their users of the regrouping in steps 4a and 4b respectively. + 6. MCPTT clients 2 and 3 may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the pre-configured regroup request. + 7. The MCPTT server sends the IWF an IWF pre-configured regroup request. + 8. The IWF sends the MCPTT server and IWF pre-configured regroup response. + 9. The MCPTT server affiliates the regrouped MCPTT clients and the IWF to the pre-configured user regroup. + 10. The MCPTT server sends a pre-configured user regroup response to MCPTT client 1. + +NOTE 2: After the pre-configured user regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.8.3.1. + +### 10.3.8.2.2 Pre-configured user group regroup formation by the IWF + +Figure 10.3.8.2.2-1 illustrates the procedure for the IWF to initiate a pre-configured user regroup procedure using a pre-configured MCPTT group. The procedure takes place prior to the establishment of a pre-configured user regroup call to the pre-configured user regroup. For simplicity, only one receiving MCPTT client is shown. + +Pre-conditions: + +- The MCPTT client is registered with the MCPTT service. +- An MCPTT group that will be used for configuration of the pre-configured user regroup has been pre-configured in the MCPTT client and the IWF, and the MCPTT client has received the relevant security related information to allow it to communicate in the pre-configured user regroup. +- The pre-configured user regroup is homed in the IWF. + +![Sequence diagram illustrating the user regroup procedure using pre-configured group by the IWF. The diagram shows five steps: 1. IWF pre-configured regroup request from IWF to MCPTT server; 2. Pre-configured regroup request from MCPTT server to MCPTT client; 3. Notify user (internal to MCPTT client); 4. Pre-configured regroup response from MCPTT client to MCPTT server; 5. Preconfigured regroup response from MCPTT server to IWF.](da90447206621f137780272a2bf807a4_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_client: 3. Notify user + IWF->>MCPTT_server: 1. IWF pre-configured regroup request + MCPTT_server->>MCPTT_client: 2. Pre-configured regroup request + MCPTT_client-->>MCPTT_server: 4. Pre-configured regroup response + MCPTT_server-->>IWF: 5. Preconfigured regroup response + +``` + +Sequence diagram illustrating the user regroup procedure using pre-configured group by the IWF. The diagram shows five steps: 1. IWF pre-configured regroup request from IWF to MCPTT server; 2. Pre-configured regroup request from MCPTT server to MCPTT client; 3. Notify user (internal to MCPTT client); 4. Pre-configured regroup response from MCPTT client to MCPTT server; 5. Preconfigured regroup response from MCPTT server to IWF. + +**Figure 10.3.8.2.2-1: User regroup procedure using pre-configured group by the IWF** + +1. The IWF initiates the pre-configured user regroup, the IWF sends an IWF pre-configured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation, that are homed in the MCPTT system. + +NOTE 1: MCPTT clients and users homed in the IWF can be involved in multiple user and group regroups simultaneously. + +2. The MCPTT server sends the pre-configured regroup request to the MCPTT client. +3. The MCPTT client notifies the MCPTT users of the regrouping. +4. The MCPTT client may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup request. +5. The MCPTT server sends an IWF pre-configured regroup response to the IWF. + +NOTE 2: After the pre-configured user regroup procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.8.3.2. + +### 10.3.8.3 Pre-configured user regroup cancellation + +#### 10.3.8.3.1 Pre-configured user regroup cancellation by the MCPTT system + +Figure 10.3.8.3.1-1 illustrates the procedure to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. For simplicity, only one receiving MCPTT client is shown. + +Pre-conditions: + +- MCPTT client 2 and at least one user homed in the IWF have been regrouped into the pre-configured user regroup. +- MCPTT client 1 is authorized to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. + +![Sequence diagram illustrating the 'Cancel pre-configured user regroup procedure by the MCPTT system'. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The steps are: 1. MCPTT client 1 initiates cancellation; 2. MCPTT client 1 sends a pre-configured regroup cancel request to the MCPTT server; 3. MCPTT server checks authorization; 4. MCPTT server sends a pre-configured regroup cancel request to MCPTT client 2; 5. MCPTT client 2 notifies the user; 6. MCPTT client 2 sends a pre-configured regroup cancel response to the MCPTT server; 7. MCPTT server sends an IWF pre-configured regroup cancel request to the IWF; 8. IWF sends an IWF pre-configured regroup cancel response to the MCPTT server; 9. MCPTT server deaffiliates MCPTT clients and the IWF; 10. MCPTT server sends a pre-configured regroup cancel response to MCPTT client 1.](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant IWF + + Note left of MCPTT client 1: 1. Cancel pre-configured user regrouping + MCPTT client 1->>MCPTT server: 2. Pre-configured regroup cancel request + Note right of MCPTT server: 3. Check authorization + MCPTT server->>MCPTT client 2: 4. Pre-configured regroup cancel request + Note right of MCPTT client 2: 5. Notify user + MCPTT client 2-->>MCPTT server: 6. Pre-configured regroup cancel response + MCPTT server->>IWF: 7. IWF pre-configured regroup cancel request + IWF-->>MCPTT server: 8. IWF pre-configured regroup cancel response + Note right of MCPTT server: 9. Deaffiliate MCPTT clients and the IWF + MCPTT server->>MCPTT client 1: 10. Pre-configured regroup cancel response + +``` + +Sequence diagram illustrating the 'Cancel pre-configured user regroup procedure by the MCPTT system'. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The steps are: 1. MCPTT client 1 initiates cancellation; 2. MCPTT client 1 sends a pre-configured regroup cancel request to the MCPTT server; 3. MCPTT server checks authorization; 4. MCPTT server sends a pre-configured regroup cancel request to MCPTT client 2; 5. MCPTT client 2 notifies the user; 6. MCPTT client 2 sends a pre-configured regroup cancel response to the MCPTT server; 7. MCPTT server sends an IWF pre-configured regroup cancel request to the IWF; 8. IWF sends an IWF pre-configured regroup cancel response to the MCPTT server; 9. MCPTT server deaffiliates MCPTT clients and the IWF; 10. MCPTT server sends a pre-configured regroup cancel response to MCPTT client 1. + +**Figure 10.3.8.3.1-1: Cancel pre-configured user regroup procedure by the MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the cancellation of the pre-configured user regroup that uses a pre-configured MCPTT group. +2. MCPTT client 1 sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the pre-configured user regroup. +3. The MCPTT server checks that MCPTT client 1 is authorized to cancel a pre-configured user regroup. +4. The MCPTT server sends the pre-configured regroup cancel requests to MCPTT client 2. +5. MCPTT clients 2 notifies the MCPTT user of the cancellation of the pre-configured user regroup. +6. MCPTT client 2 may send the MCPTT server a pre-configured regroup cancel response. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup cancel request. +7. The MCPTT server sends the IWF an IWF pre-configured regroup cancel request. + +8. The IWF sends the MCPTT server an IWF pre-configured regroup cancel response. +9. The MCPTT server de-affiliates MCPTT clients 2 and 3 from the pre-configured user regroup. +10. The MCPTT server sends a pre-configured regroup cancel response to MCPTT client 1. + +### 10.3.8.3.2 Pre-configured user regroup cancellation by the IWF + +Figure 10.3.8.3.2-1 illustrates the procedure to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. For simplicity, only one receiving MCPTT client is shown. + +Pre-conditions: + +- An MCPTT client and at least one user homed in the IWF have been regrouped into the pre-configured user regroup. + +![Sequence diagram illustrating the pre-configured user regroup cancellation procedure by the IWF. The diagram shows five steps: 1. IWF sends a pre-configured regroup cancel request to the MCPTT server. 2. MCPTT server sends a pre-configured regroup cancel request to the MCPTT client. 3. MCPTT client notifies the user. 4. MCPTT client sends a pre-configured regroup cancel response to the MCPTT server. 5. MCPTT server sends an IWF pre-configured regroup cancel response to the IWF.](c020c072c67473d7823d1f9551942732_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_client: user + IWF->>MCPTT_server: 1. IWF pre-configured regroup cancel request + MCPTT_server->>MCPTT_client: 2. Pre-configured regroup cancel request + MCPTT_client->>Note right of MCPTT_client: 3. Notify user + MCPTT_client-->>MCPTT_server: 4. Pre-configured regroup cancel response + MCPTT_server-->>IWF: 5. IWF pre-configured regroup cancel response + +``` + +Sequence diagram illustrating the pre-configured user regroup cancellation procedure by the IWF. The diagram shows five steps: 1. IWF sends a pre-configured regroup cancel request to the MCPTT server. 2. MCPTT server sends a pre-configured regroup cancel request to the MCPTT client. 3. MCPTT client notifies the user. 4. MCPTT client sends a pre-configured regroup cancel response to the MCPTT server. 5. MCPTT server sends an IWF pre-configured regroup cancel response to the IWF. + +**Figure 10.3.8.3.2-1: Cancel pre-configured pre-configured user regroup procedure by the IWF** + +1. The IWF initiates the cancellation of the pre-configured user regroup. The IWF sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the pre-configured user regroup. +2. The MCPTT server sends the pre-configured regroup cancel requests to the MCPTT client. +3. The MCPTT client notifies the MCPTT user of the cancellation of the pre-configured user regroup. +4. The MCPTT client may send the MCPTT server a pre-configured regroup cancel response. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup cancel request. +5. The MCPTT server sends an IWF pre-configured regroup cancel response to the IWF. + +## 10.4 Private call + +### 10.4.1 Information flows for private calls + +#### 10.4.1.1 General + +The following subclauses define information flows for private calls on the IWF-1 interface. Private call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7]. + +### 10.4.1.2 IWF private call request + +Table 10.4.1.2-1 describes the information flow IWF private call request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.2-1: IWF private call request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias associated with the MCPTT ID of the calling party. | +| MCPTT ID | M | The MCPTT ID 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. | +| Encryption Algorithm | O | Encryption algorithm to use for the call. The field can also indicate whether the encryption algorithm choice is determined from information in the media stream. | +| Encryption mode | M | Whether E2EE will be used. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request (see NOTE) | O | An indication that the user is also requesting the floor. | +| Location | O | Location of the calling party | +| NOTE: This element shall be included only when the originating client requests the floor. | | | + +### 10.4.1.3 IWF private call response + +Table 10.4.1.3-1 describes the information flow IWF private call response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.3-1: IWF private call response information elements** + +| Information Element | Status | Description | +|---------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the IWF private call request: success or failure | +| Encryption Algorithm(s) response | O | A list of one or more alternative encryption algorithm(s) to use for the call. | +| Use floor control indication response | O | This element indicates whether the floor control indication in the request is acceptable. | +| Implicit floor request response | O | This element indicates whether the indication that the user is also requesting the floor in the request is acceptable. | + +#### 10.4.1.4 IWF ringing + +Table 10.4.1.4-1 describes the information flow IWF ringing from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.4-1: IWF ringing 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 | +| Ringing indication | O | Indication to the caller. | + +#### 10.4.1.5 IWF call end request + +Table 10.4.1.5-1 describes the information flow IWF call end request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.5-1: IWF call end 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 | + +#### 10.4.1.6 IWF call end response + +Table 10.4.1.6-1 describes the information flow IWF call end response from the IWF to the MCPTT server. + +**Table 10.4.1.6-1: IWF call end response information elements** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------| +| MCPTT ID | M | The MCPTT ID of the responding party | + +### 10.4.2 Private call setup in automatic commencement mode + +#### 10.4.2.1 MCPTT user initiating an MCPTT private call + +In this procedure, an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with a user in an LMR system, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.1. + +In figure 10.4.2.1-1, an MCPTT client initiates establishment of an MCPTT private call with an LMR user. + +Pre-conditions: + +1. The calling MCPTT user has selected automatic commencement mode for the call; +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. Optionally, MCPTT client may use an activated functional alias for the call. +4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the private call setup in automatic commencement mode, initiated by an MCPTT user. The diagram shows three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT private call request from MCPTT client to MCPTT server; 2. Authorize request from MCPTT server to IWF; 3. IWF private call request from IWF to MCPTT server; 4. IWF private call response from MCPTT server to IWF; 5. MCPTT private call response from MCPTT server to MCPTT client; 6. Media plane established (indicated by a horizontal bar across all three participants).](8a781a0a8c956859f63a1ca7f2bb1644_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT server: Authorize request + MCPTT client->>MCPTT server: 1. MCPTT private call request + MCPTT server->>IWF: 2. Authorize request + IWF->>MCPTT server: 3. IWF private call request + MCPTT server->>IWF: 4. IWF private call response + MCPTT server->>MCPTT client: 5. MCPTT private call response + Note over MCPTT client, MCPTT server, IWF: 6. Media plane established + +``` + +Sequence diagram illustrating the private call setup in automatic commencement mode, initiated by an MCPTT user. The diagram shows three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT private call request from MCPTT client to MCPTT server; 2. Authorize request from MCPTT server to IWF; 3. IWF private call request from IWF to MCPTT server; 4. IWF private call response from MCPTT server to IWF; 5. MCPTT private call response from MCPTT server to MCPTT client; 6. Media plane established (indicated by a horizontal bar across all three participants). + +**Figure 10.4.2.1-1: Private call setup in automatic commencement mode, initiated by an MCPTT user** + +1. The MCPTT user at the MCPTT client initiates an MCPTT private call. The MCPTT client sends an MCPTT private call request towards the MCPTT server. The MCPTT private call request contains the MCPTT IDs corresponding to the calling MCPTT party and called LMR party and an SDP offer containing one or more media types. If available, the MCPTT user at the MCPTT client may also include a functional alias. The following parameters are also included that describe the MCPTT client's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not); + - an indication of whether the MCPTT client is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; + - requested commencement mode (automatic in this case); and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). + 2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the private call and whether the provided functional alias, if present, can be used and has been activated for the user. Because the IWF private call request is requesting automatic commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to initiate a call in automatic commencement mode. If location information was included in the MCPTT private call request, the MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. + 3. If authorized, the MCPTT server sends the IWF private call request that may or may not include location of the requestor, depending on the outcome of the privacy check towards the IWF, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. +- NOTE: How the IWF private call request is forwarded to the LMR system is out of scope of the present document. +4. The IWF sends an IWF private call response to the MCPTT server, indicating that the IWF does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3. + 5. The MCPTT server forwards the MCPTT private call response to the MCPTT client. If the result parameter indicates success, then the MCPTT client proceeds to step 6. Otherwise, if the parameters returned in the MCPTT private call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT private call request with the new parameters and behaves according to those parameters. The calling + +MCPTT user may be notified of the change in parameters, for example, that the call is to be without floor control. The MCPTT user can choose to end the call rather than continue with the new parameters. If the parameters returned are not acceptable to the MCPTT client, then the call fails. + +6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +#### 10.4.2.2 LMR user initiating a private call with MCPTT user + +In this procedure, an LMR user is initiating a private call (in automatic commencement mode) for communicating with a user in MCPTT system, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.1. + +In figure 10.4.2.2-1, an LMR user initiates establishment of a private call with an MCPTT user. + +Pre-conditions: + +1. The calling LMR user has selected automatic commencement mode for the call; +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. The LMR user at the LMR system has initiated a private call towards an MCPTT user. +4. Optionally, LMR user may use an activated functional alias (homed in the MCPTT system) for the call. +5. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +NOTE 1: Private call operation between the LMR user and the IWF are out of scope of the present document. + +NOTE 2: The mapping between alternative addressing schemes of the LMR user and the corresponding functional alias is out of scope of the present document. + +![Sequence diagram showing the private call setup in automatic commencement mode, initiated by an LMR user. The diagram involves three main entities: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF private call request from IWF to MCPTT server; 2. Authorize request from MCPTT server to MCPTT client; 3. MCPTT private call request from MCPTT client to MCPTT server; 4. MCPTT private call response from MCPTT server to MCPTT client; 5. IWF private call response from MCPTT server to IWF; 6. Media plane established (indicated by a horizontal bar at the bottom spanning all three entities).](e8f5277dca9bb75e7ba79d96c568db4b_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_server: 2. Authorize request + IWF->>MCPTT_server: 1. IWF private call request + MCPTT_server->>MCPTT_client: 2. Authorize request + MCPTT_client->>MCPTT_server: 3. MCPTT private call request + MCPTT_server->>MCPTT_client: 4. MCPTT private call response + MCPTT_server->>IWF: 5. IWF private call response + Note bottom of MCPTT_client: 6. Media plane established + +``` + +Sequence diagram showing the private call setup in automatic commencement mode, initiated by an LMR user. The diagram involves three main entities: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF private call request from IWF to MCPTT server; 2. Authorize request from MCPTT server to MCPTT client; 3. MCPTT private call request from MCPTT client to MCPTT server; 4. MCPTT private call response from MCPTT server to MCPTT client; 5. IWF private call response from MCPTT server to IWF; 6. Media plane established (indicated by a horizontal bar at the bottom spanning all three entities). + +**Figure 10.4.2.2-1: Private call setup in automatic commencement mode, initiated by an LMR user** + +1. The IWF sends an IWF private call request towards the MCPTT server. The IWF private call request contains the MCPTT IDs corresponding to the calling LMR party and the called MCPTT party and an SDP offer containing one or more media types. If available, the LMR party homed in the IWF may also include a functional alias. The following parameters are also included that describe the MCPTT client's choices: + +- the encryption algorithm; + - the encryption mode (encrypted or not); + - an indication of whether the LMR user is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; + - requested commencement mode (automatic in this case); and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized and able to receive the private call. Because the IWF private call request is requesting automatic commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to receive a call in automatic commencement mode. The MCPTT server also checks whether the provided functional alias, if present, can be used and has been activated for the LMR user homed in the IWF. + 3. If authorized, the MCPTT server sends the MCPTT private call request towards the MCPTT client, including the original parameters with or without the location of the calling party and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + 4. The MCPTT client sends an MCPTT private call response to the MCPTT server indicating that the MCPTT client does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may also include one or more alternatives to the parameter values contained in step 3. + 5. The MCPTT server sends the IWF private call response to the IWF offering the same media type as that sent in step 4. If the parameters returned are not acceptable to the IWF, then the call fails. If the parameters returned in the IWF private call response are different but acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters starting with step 1, which is to essentially restart the call. If there is no change of parameter, then the call proceeds to step 6. +- NOTE 3: The calling LMR user may be notified of the change in parameters, for example, that the call is to be without floor control. +6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The LMR system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +### 10.4.3 Private call setup in manual commencement mode + +#### 10.4.3.1 MCPTT user is initiating an MCPTT private call + +In this procedure, an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with an LMR user via an IWF, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.2. + +In figure 10.4.3.1-1, an MCPTT client initiates establishment of an MCPTT private call with an LMR user. + +Pre-conditions: + +1. The calling MCPTT user has selected manual commencement mode for the call. +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. Optionally, MCPTT client may use an activated functional alias (homed in the MCPTT system) for the call. +4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the private call setup in manual commencement mode initiated by an MCPTT user. The diagram shows interactions between an MCPTT client, an MCPTT server, and an IWF. The sequence of messages is: 1. MCPTT private call request (client to server), 2. Authorize request (server to server), 3. IWF private call request (server to IWF), 4. IWF private call response (IWF to server), 5. MCPTT private call response (server to client), 6. IWF ringing (IWF to server), 7. MCPTT ringing (server to client), 8. IWF private call response (IWF to server), 9. MCPTT private call response (server to client), and 10. Media plane established (a horizontal bar spanning all three entities).](b3d488012fdceacab867cf24c5efef05_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT server: Authorize request + MCPTT client->>MCPTT server: 1. MCPTT private call request + MCPTT server->>MCPTT server: 2. Authorize request + MCPTT server->>IWF: 3. IWF private call request + IWF-->>MCPTT server: 4. IWF private call response + MCPTT server-->>MCPTT client: 5. MCPTT private call response + IWF->>MCPTT server: 6. IWF ringing + MCPTT server->>MCPTT client: 7. MCPTT ringing + IWF-->>MCPTT server: 8. IWF private call response + MCPTT server-->>MCPTT client: 9. MCPTT private call response + Note over MCPTT client, MCPTT server, IWF: 10. Media plane established + +``` + +Sequence diagram illustrating the private call setup in manual commencement mode initiated by an MCPTT user. The diagram shows interactions between an MCPTT client, an MCPTT server, and an IWF. The sequence of messages is: 1. MCPTT private call request (client to server), 2. Authorize request (server to server), 3. IWF private call request (server to IWF), 4. IWF private call response (IWF to server), 5. MCPTT private call response (server to client), 6. IWF ringing (IWF to server), 7. MCPTT ringing (server to client), 8. IWF private call response (IWF to server), 9. MCPTT private call response (server to client), and 10. Media plane established (a horizontal bar spanning all three entities). + +**Figure 10.4.3.1-1: Private call setup in manual commencement mode – initiated by an MCPTT user** + +- The MCPTT user at the MCPTT client would like to initiate an MCPTT private call. The MCPTT client sends an MCPTT private call request towards the MCPTT server. The MCPTT private call request contains the MCPTT IDs corresponding to the calling MCPTT party and called LMR party and an SDP offer containing one or more media types. If available, the MCPTT user at the MCPTT client may also include a functional alias. The following parameters are also included that describe the MCPTT client's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not) + - an indication of whether the MCPTT client is requesting the floor; + - requested commencement mode (manual in this case), and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). + - The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the private call and whether the provided functional alias, if present, can be used and has been activated for the user. Because the IWF private call request is requesting manual commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to initiate a call in manual commencement mode. If location information was included in the MCPTT private call request, the MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. + - If authorized, the MCPTT server sends the IWF private call request towards the IWF, including the original parameters that may or may not include location of the requestor, depending on the outcome of the privacy check, and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. +- NOTE: How the IWF private call request is forwarded to the LMR system is out of scope of the present document. +- The IWF may report failure with an IWF private call response to the MCPTT server. The response may include one or more alternatives to the parameter values contained in step 3. If the IWF does not report failure, the process proceeds with step 6. + +5. The MCPTT server forwards the MCPTT private call response to the MCPTT client. If the result parameter indicates failure, the MCPTT client may abandon the call. If the parameters in the MCPTT private call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT private call request with the new parameters to the MCPTT server and behaves according to those parameters. The calling user may be notified of the change in parameters, for example, that the call is to be without floor control. The calling user may choose to end the call rather than continue with the new parameters. +6. The receiving IWF sends an IWF ringing to the MCPTT server while waiting for the call to be accepted. +7. The MCPTT server forwards the MCPTT ringing to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the LMR user has been notified, e.g. by producing ringback audio. +8. Once the call has been accepted by the called user, the IWF sends an IWF private call response to the MCPTT server. The IWF private call response indicates that the IWF does support one of the requested media types. +9. The MCPTT server forwards the MCPTT private call response to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the call is connected, e.g. by stopping the ringback audio. +10. The MCPTT client has successfully established media plane for communication to the IWF. The MCPTT system initiating the call is responsible of granting the floor and solving the competing floor requests, and floor revoked indications. + +### 10.4.3.2 LMR user initiating a private call with MCPTT user + +In this procedure, an LMR user is initiating a private call (in manual commencement mode) for communicating with an MCPTT user via an IWF, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.2. + +In figure 10.4.3.2-1, an LMR user initiates establishment of a private call with an MCPTT user. + +Pre-conditions: + +1. The calling LMR user has selected manual commencement mode for the call. +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. The LMR user at the LMR system has initiated a private call towards an MCPTT user. +4. Optionally, LMR user may use an activated functional alias (homed in the MCPTT system) for the call. +5. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +NOTE 1: Private call operation between the LMR user and the IWF are out of scope of the present document. + +NOTE 2: The mapping between alternative addressing schemes of the LMR user and the corresponding functional alias is out of scope of the present document + +![Sequence diagram showing the private call setup in manual commencement mode, initiated by an LMR user. The diagram involves three main entities: IWF, MCPTT server, and MCPTT client. The sequence of messages is as follows: 1. IWF private call request (IWF to MCPTT server); 2. Authorize request (MCPTT server to MCPTT client); 3. MCPTT private call request (MCPTT server to MCPTT client); 4. MCPTT private call response (MCPTT client to MCPTT server); 5. IWF private call response (MCPTT server to IWF); 6. MCPTT ringing (MCPTT server to MCPTT client); 7. IWF ringing (MCPTT server to IWF); 8. MCPTT private call response (MCPTT client to MCPTT server); 9. IWF private call response (MCPTT server to IWF); 10. Media plane established (a horizontal bar spanning all three entities).](d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_server: 2. Authorize request + IWF->>MCPTT_server: 1. IWF private call request + MCPTT_server->>MCPTT_client: 3. MCPTT private call request + MCPTT_client-->>MCPTT_server: 4. MCPTT private call response + MCPTT_server-->>IWF: 5. IWF private call response + MCPTT_server->>MCPTT_client: 6. MCPTT ringing + MCPTT_server-->>IWF: 7. IWF ringing + MCPTT_client-->>MCPTT_server: 8. MCPTT private call response + MCPTT_server-->>IWF: 9. IWF private call response + Note over IWF, MCPTT_server, MCPTT_client: 10. Media plane established + +``` + +Sequence diagram showing the private call setup in manual commencement mode, initiated by an LMR user. The diagram involves three main entities: IWF, MCPTT server, and MCPTT client. The sequence of messages is as follows: 1. IWF private call request (IWF to MCPTT server); 2. Authorize request (MCPTT server to MCPTT client); 3. MCPTT private call request (MCPTT server to MCPTT client); 4. MCPTT private call response (MCPTT client to MCPTT server); 5. IWF private call response (MCPTT server to IWF); 6. MCPTT ringing (MCPTT server to MCPTT client); 7. IWF ringing (MCPTT server to IWF); 8. MCPTT private call response (MCPTT client to MCPTT server); 9. IWF private call response (MCPTT server to IWF); 10. Media plane established (a horizontal bar spanning all three entities). + +**Figure 10.4.3.2-1: Private call setup in manual commencement mode, initiated by an LMR user** + +1. The IWF sends an IWF private call request towards the MCPTT server. The IWF private call request contains the MCPTT IDs corresponding to the calling LMR party and called MCPTT party and an SDP offer containing one or more media types. If available, the LMR party homed in the IWF may also include a functional alias. The following parameters are also included that describe the IWF's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not) + - an indication of whether the LMR user is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; + - requested commencement mode (manual in this case); and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized and able to receive the private call. Because the IWF private call request is requesting manual commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to receive a call in manual commencement mode. The MCPTT server also checks whether the provided functional alias, if present, can be used and has been activated for the LMR user homed in the IWF. +3. If authorized, the MCPTT server sends the MCPTT private call request towards the MCPTT client, including the original parameters with or without the location of the calling party and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + +NOTE 3: How the IWF private call request is forwarded to the LMR system is out of scope of the present document. + +4. The MCPTT client may report failure with an MCPTT private call response to the MCPTT server. The response may include one or more alternatives to the parameter values contained in step 3. If the MCPTT client does not report failure, the process proceeds with step 6. +5. The MCPTT server forwards the MCPTT private call response to the IWF. If the result parameter indicates failure, the IWF may abandon the call. If the parameters in the IWF private call response are acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters to the MCPTT server and + +behaves according to those parameters. The IWF may choose to end the call rather than continue with the new parameters. + +6. The MCPTT client sends an MCPTT ringing to the MCPTT server while waiting for the call to be accepted by the MCPTT user. +7. The MCPTT server sends an IWF ringing to IWF while waiting for the call to be accepted. +8. Once the call has been accepted by the called user, the MCPTT client sends an MCPTT private call response to the MCPTT server. The IWF private call response indicates that the IWF does support one of the requested media types. +9. The MCPTT sends the IWF private call response to the IWF. +10. The MCPTT client has successfully established media plane for communication to the IWF. The LMR system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +## 10.4.4 Private call release + +### 10.4.4.1 MCPTT client initiated + +The procedure describes the case where an MCPTT client requests release of an ongoing MCPTT private call (with or without floor control) that was established in either of the two commencement modes (manual or automatic). This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.1 and 10.7.2.3.3. + +Procedures in figure 10.4.4.1-1 are the basic signalling control plane procedures for the MCPTT client initiating the release of an ongoing interworked private call. + +Pre-conditions: + +1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3. + +![Sequence diagram for Private call release – client initiated](987a8ea27d373fa66433e6b8cb2e98ab_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Release private call + MCPTT client->>MCPTT server: 2. MCPTT private call end request + MCPTT server->>IWF: 3. IWF call end request + IWF->>MCPTT server: 4. IWF call end response + MCPTT server->>MCPTT client: 5. MCPTT private call end response + Note right of MCPTT client: 6. Media plane resources released +``` + +The diagram is a sequence diagram illustrating the signaling control plane procedures for a client-initiated private call release. It features three lifelines: MCPTT client, MCPTT server, and IWF. The process begins with a self-call on the MCPTT client labeled '1. Release private call'. The MCPTT client then sends a '2. MCPTT private call end request' to the MCPTT server. The MCPTT server forwards this as a '3. IWF call end request' to the IWF. The IWF responds with a '4. IWF call end response' to the MCPTT server, which in turn sends a '5. MCPTT private call end response' back to the MCPTT client. Finally, a horizontal bar across all lifelines indicates '6. Media plane resources released'. + +Sequence diagram for Private call release – client initiated + +**Figure 10.4.4.1-1: Private call release – client initiated** + +1. The user at the MCPTT client would like to release an ongoing interworked private call with the LMR user. + +2. The MCPTT client sends an MCPTT private call end request towards the MCPTT server (via SIP core) for tearing down the private call with the other client. +3. The MCPTT server sends the corresponding IWF call end request towards the IWF, addressed to the MCPTT client ID specified in the original MCPTT private call end request. + +NOTE: The LMR user is also notified about the release of the private call. How the LMR user is notified is outside the scope of the present document. + +4. The IWF acknowledges the IWF call end request with an IWF call end response sent towards the MCPTT server. +5. After receiving the MCPTT private call end request acknowledgement from the IWF, the MCPTT server generates an acknowledgement for the MCPTT client's MCPTT private call end request. +6. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media. + +#### 10.4.4.2 MCPTT server initiated + +The procedure describes the case where an MCPTT server terminates an ongoing interworked private call (with or without floor control) that was established in either of the two commencement modes (manual or automatic). The conditions causing the MCPTT server to terminate the call could include expiry of the MCPTT administrator configured maximum duration for MCPTT private calls or expiry of the maximum time permitted for an MCPTT private call without transmission/reception. This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.2 and 10.7.2.3.3. + +Procedures in figure 10.4.4.2-1 are the basic signalling control plane procedures for the MCPTT server initiating termination of an ongoing interworked private call. + +Pre-conditions: + +1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3. + +![Sequence diagram for MCPTT server initiated private call termination. Lifelines: MCPTT client, MCPTT server, IWF. The process starts with conditions to trigger termination on the MCPTT server. The MCPTT server sends an MCPTT private call end request (2a) to the MCPTT client and an IWF call end request (2b) to the IWF. The MCPTT client notifies call termination (3). Both the MCPTT client and IWF send responses (4) to the MCPTT server. Finally, media plane resources are released (5) across all entities.](7bfe80acfdafd78f610d8b66e3cc6161_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT server: 1. Conditions to trigger terminate private call + MCPTT server->>MCPTT client: 2a. MCPTT private call end request + MCPTT server->>IWF: 2b. IWF call end request + Note left of MCPTT client: 3. Notify call termination + MCPTT client->>MCPTT server: 4. MCPTT private call end response + IWF->>MCPTT server: 4. IWF call end response + Note bottom: 5. Media plane resources released + +``` + +Sequence diagram for MCPTT server initiated private call termination. Lifelines: MCPTT client, MCPTT server, IWF. The process starts with conditions to trigger termination on the MCPTT server. The MCPTT server sends an MCPTT private call end request (2a) to the MCPTT client and an IWF call end request (2b) to the IWF. The MCPTT client notifies call termination (3). Both the MCPTT client and IWF send responses (4) to the MCPTT server. Finally, media plane resources are released (5) across all entities. + +**Figure 10.4.4.2-1: End private call – server initiated** + +1. Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls expiry or time out due to MCPTT private call without transmission/reception, the MCPTT server decides to initiate termination of an ongoing interworking private call between the MCPTT client and the LMR user. +- 2a. The MCPTT server sends an MCPTT private call end request towards the MCPTT client (via SIP core) for tearing down the private call. + +2b. The MCPTT server sends a corresponding IWF call end request towards the MCPTT client identity associated with the LMR user + +3. The MCPTT user at the MCPTT client is notified about the termination of the private call. + +NOTE: The LMR user is also notified about the termination of the private call. How the LMR user is notified is outside the scope of the present document. + +4. The MCPTT client and the IWF acknowledge the request. + +5. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media. + +#### 10.4.4.3 LMR user initiated + +The procedure describes the case where either an LMR user or the LMR system is requesting to release an ongoing interworked private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic). This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.1 and 10.7.2.3.3. + +Procedures in figure 10.4.4.3-1 are the basic signalling control plane procedures for the LMR user, via the IWF, initiating the release of an ongoing interworked private call. + +Pre-conditions: + +1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3. + +![Sequence diagram for Private call release – IWF initiated. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT Client. The sequence of messages is: 1. Release private call (from IWF to MCPTT server), 2. IWF call end request (from IWF to MCPTT server), 3. MCPTT private call end request (from MCPTT server to MCPTT Client), 4. Notify call termination (from MCPTT Client to MCPTT server), 5. MCPTT private call end response (from MCPTT Client to MCPTT server), 6. IWF call end response (from MCPTT server to IWF), and 7. Media plane resources released (a horizontal bar spanning all three lifelines).](c24164782e328c82ba89b80c0ef8c3d7_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT Client + Note left of IWF: 1. Release private call + IWF->>MCPTT server: 2. IWF call end request + MCPTT server->>MCPTT Client: 3. MCPTT private call end request + Note right of MCPTT Client: 4. Notify call termination + MCPTT Client->>MCPTT server: 5. MCPTT private call end response + MCPTT server->>IWF: 6. IWF call end response + Note bottom: 7. Media plane resources released + +``` + +Sequence diagram for Private call release – IWF initiated. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT Client. The sequence of messages is: 1. Release private call (from IWF to MCPTT server), 2. IWF call end request (from IWF to MCPTT server), 3. MCPTT private call end request (from MCPTT server to MCPTT Client), 4. Notify call termination (from MCPTT Client to MCPTT server), 5. MCPTT private call end response (from MCPTT Client to MCPTT server), 6. IWF call end response (from MCPTT server to IWF), and 7. Media plane resources released (a horizontal bar spanning all three lifelines). + +**Figure 10.4.4.3-1: Private call release – IWF initiated** + +1. The LMR system would like to release an ongoing interworked private call with the MCPTT user. + +2. The IWF sends an IWF call end request towards the MCPTT server for tearing down the private call with the MCPTT client. + +3. The MCPTT server sends the corresponding MCPTT private call end request towards the MCPTT client specified in the original IWF call end request. + +4. The MCPTT user is notified about the release of the private call. +5. The MCPTT client acknowledges the MCPTT private call end request. +6. After receiving the MCPTT private call end request acknowledgement from the MCPTT client, the MCPTT server generates an acknowledgement for the IWF's IWF call end request. +7. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media. + +## 10.4.5 Encryption of private calls + +Private calls can use MC media encryption (see 3GPP TS 33.180 [8]) between the IWF and the MCPTT client. A private call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys. + +NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE. + +## 10.5 Floor control + +### 10.5.1 General + +Floor control for interworking applies to both private call and group call. + +Floor control involving a single MCPTT server is described in 3GPP TS 23.379 [7]. Floor control involving multiple MCPTT servers is also described in 3GPP TS 23.379 [7] in that a primary MCPTT server is interconnected to a partner MCPTT server. Subclause 10.5.2 describes information flows for floor control between an MCPTT server and an IWF, and are based on those defined interconnection in 3GPP TS 23.379 [7]. Subclause 10.5.3 describes aspects of floor control that apply to interworking groups and interworking private calls. Subclauses 10.5.4/10.5.6 and 10.5.5/10.5.7 describe general cases of floor control on an interworking group defined in the LMR system and in the MCPTT system respectively, where the partner system has been configured to apply/not apply local filtering of floor control requests before communicating with the primary system. Subclauses 10.5.9 and 10.5.10 describe general cases of floor control in a private call, where the controlling role is taken by the LMR system and the MCPTT system respectively. + +### 10.5.2 Information flows for floor control + +#### 10.5.2.1 General + +The following sections describe information flows for interworking floor control. + +In the following information flows the MCPTT ID and its associated functional alias represents the LMR user, the IWF, or the MCPTT user depending on the interworking methods being used and the message source/destination. + +#### 10.5.2.2 IWF floor request + +Table 10.5.2.2-1 describes the information flow IWF floor request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request the floor for media transfer. + +**Table 10.5.2.2-1: IWF floor request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Requester identity | +| Functional alias | O | Functional alias of the requester | +| Floor priority | M | Priority of the request | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Location | O | Location information of requester | + +### 10.5.2.3 IWF floor granted + +Table 10.5.2.3-1 describes the information flow IWF floor granted, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a request for floor is granted and media transfer is possible. + +**Table 10.5.2.3-1: IWF floor granted** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Granted party identity | +| Functional alias | O | Functional alias of the granted party identity | +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.4 IWF floor rejected + +Table 10.5.2.4-1 describes the information flow IWF floor rejected, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a request for the floor is rejected. + +**Table 10.5.2.4-1: IWF floor rejected** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Rejected party identity | +| Functional alias | O | Functional alias of the rejected party | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Rejection cause | O | Indicates the cause for floor rejection | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.5 IWF floor request cancel + +Table 10.5.2.5-1 describes the information flow IWF floor request cancel, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request cancelling the floor request from the floor request queue. + +**Table 10.5.2.5-1: IWF floor request cancel** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the requester | +| Functional alias | O | Functional alias of the requester | +| List of MCPTT IDs | M | Target identity (Identities) whose floor request is to be cancelled | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.6 IWF floor request cancel response + +Table 10.5.2.6-1 describes the information flow IWF floor request cancel response, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the response for the floor request cancellation. + +**Table 10.5.2.6-1: IWF floor request cancel response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party that initiated the cancellation request | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.7 IWF floor request cancel notify + +Table 10.5.2.7-1 describes the information flow IWF floor request cancel notify, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor request is cancelled by the administrator/floor control server. + +**Table 10.5.2.7-1: IWF floor request cancel notify** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the administrator | +| Functional alias | O | Functional alias of the administrator | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.8 IWF floor idle + +Table 10.5.2.8-1 describes the information flow IWF floor idle, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a session is in idle status, i.e. the floor is not granted to any party. + +**Table 10.5.2.8-1: IWF floor idle** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.9 IWF floor release + +Table 10.5.2.9-1 describes the information flow IWF floor release, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the media transfer is completed and the floor is released. + +**Table 10.5.2.9-1: IWF floor release** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party that released the floor | +| Functional alias | O | Functional alias of the party that released the floor | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.10 IWF floor taken + +Table 10.5.2.10-1 describes the information flow IWF floor taken, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor is granted to another MCPTT user. + +**Table 10.5.2.10-1: IWF floor taken** + +| Information element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the granted party | +| Functional alias | O | Functional alias for the granted party | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Permission to request the floor | O | Indicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call). | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| Location | O | Location information of the granted party | + +### 10.5.2.11 IWF floor revoked + +Table 10.5.2.11-1 describes the information flow IWF floor revoked, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor is revoked from its current holder (the floor participant who was granted the floor). + +**Table 10.5.2.11-1: IWF floor revoked** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Revoked party identity | +| Functional alias | O | Functional alias of the revoked party | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.12 IWF floor acknowledgement + +Table 10.5.2.12-1 describes the information flow IWF floor acknowledgement, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to provide an acknowledgement if the acknowledgement is required in the received floor control message. + +NOTE: The floor acknowledgement flow can be sent by the floor control server after each floor control information flow that includes an indication that an acknowledgement is required. + +**Table 10.5.2.12-1: IWF floor acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------| +| MCPTT ID | M | Identity of the sender. | +| Functional alias | O | Functional alias of the sender | + +### 10.5.2.13 IWF queue position request + +Table 10.5.2.13-1 describes the information flow IWF queue position request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request the position in the floor request queue. The MCPTT server and the MCPTT client that support queuing of the floor control requests shall support this information flow. + +**Table 10.5.2.13-1: IWF queue position request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party whose floor position is requested | +| Functional alias | O | Functional alias of the party whose floor position is requested | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.14 IWF queue position info + +Table 10.5.2.14-1 describes the information flow IWF queue position info, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor request is queued and the queue position to the floor requesting UE. + +**Table 10.5.2.14-1: IWF queue position info** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party whose floor position is provided | +| Functional alias | O | Functional alias of the party whose floor position is provided | +| Queue position info | M | Position of the queued floor request in the queue | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.15 IWF unicast media stop request + +Table 10.5.2.15-1 describes the information flow IWF unicast media stop request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that the unicast media flow of the designated communication does not need to be sent to the client indicated by the MCPTT ID. + +**Table 10.5.2.15-1: IWF unicast media stop request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication whose media flow is to be stopped, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.16 IWF unicast media resume request + +Table 10.5.2.16-1 describes the information flow IWF unicast media resume request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used by the floor control server to request that the unicast media flow of the designated communication is to be sent to the client indicated by the MCPTT ID. + +**Table 10.5.2.16-1: IWF unicast media resume request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication whose media flow is to be resumed, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.17 IWF floor talker ID update + +Table 10.5.2.17-1 describes the information flow IWF floor talker ID update, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that the talker ID has changed for the current MCPTT user granted the floor. + +**Table 10.5.2.17-1: IWF floor talker ID update** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the party using the floor | +| Functional alias | O | Functional alias associated with the MCPTT ID using the floor | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +## 10.5.3 Interworking floor control + +3GPP TS 23.379 [7], subclause 10.9.1.4.1 describes floor control involving groups in multiple MCPTT systems where floor control arbitration resides with the primary MCPTT server and all floor control messages are routed to that primary MCPTT server. The group is homed on the primary MCPTT server. + +An interworking group can be homed on the MCPTT server or on the LMR system. When the group is homed on the MCPTT server the floor control server is on this MCPTT server. When the group is homed on the LMR system the floor control server is represented by the IWF. + +The primary MCPTT system of an MCPTT group is defined by configuration and identified by the MC service group ID. + +3GPP TS 23.379 [7], subclause 10.9.1.4.2 describes floor control involving groups in multiple MCPTT systems where the partner MCPTT system filters its MCPTT users' floor requests before communicating with the floor control server of the primary MCPTT system. When an MCPTT system is interworking with an IWF, depending on where the group is homed the MCPTT server, or the IWF can filter floor control requests in the same way as an interconnected MCPTT system. + +In a private call, one of the IWF or MCPTT server acts as the controlling floor control server within the call, and manages arbitration of floor control requests received from both users in the call. The entity (MCPTT server or IWF) that does not fulfil the controlling role shall send all floor control requests from its served call participant to the controlling floor control server without filtering. + +NOTE: Allocation of controlling floor control server functionality to the MCPTT server or IWF may be according to the system within which the call originated, or by some other means. + +## 10.5.4 Floor override without using floor revoked on an interworking group + +This procedure describes the case where a transmitting radio cannot be signalled that the floor has been taken or revoked. Within the context of interworking between MCPTT and LMR systems, this condition can occur due to both MCPTT and LMR users obtaining the floor simultaneously, or the floor granted to an LMR user is taken by an MCPTT user. + +Figure 10.5.4-1 shows the high-level procedure where an MCPTT session is already established between the floor participants (with floor granted to an LMR user represented by the IWF) and the floor control server (with an override based on priority and configured to permit the transmission of overridden floor participant from the IWF). The group is defined in the MCPTT system and the MCPTT Server is the floor control server. Only two UEs involved in the session are shown for simplicity. + +Pre-conditions: + +1. The MCPTT floor control server has been configured to support override. +2. The override supported in this case permits both the overridden floor participant and the overriding floor participant to be transmitting. +3. An MCPTT session is established between an MCPTT client, the interworked system, and MCPTT server. +4. Session is ongoing. + +![Sequence diagram illustrating the floor override procedure. The diagram shows three lifelines: MCPTT Floor Participant A, MCPTT Floor Control Server, and IWF. The sequence starts with an established session where floor control is established and floor is granted to the IWF. Then, User A wants to talk and sends a floor request. The floor control server performs floor arbitration by priority. It grants the floor to User A (5a. Floor granted) and takes the floor from the IWF (5b. Floor taken). User A receives a grant notification (6a. Grant notification) and the IWF receives an override notification (6b. Override notification (not received; audio continues)). Finally, voice media is transmitted from User A to the IWF (7. Voice media).](c995e0bb4efc8c0f2994428aa1245709_img.jpg) + +``` + +sequenceDiagram + participant A as MCPTT Floor Participant A + participant S as MCPTT Floor Control Server + participant I as IWF + Note right of I: 1. Session is established. Floor control is established between floor participants and floor control server. +Floor is granted to the IWF. + Note left of A: 2. User A wants to talk + A->>S: 3. Floor request + Note right of S: 4. Floor arbitration by priority + S->>A: 5a. Floor granted + S->>I: 5b. Floor taken + Note left of A: 6a. Grant notification + Note right of I: 6b. Override notification (not received; audio continues) + Note right of I: 7. Voice media + +``` + +Sequence diagram illustrating the floor override procedure. The diagram shows three lifelines: MCPTT Floor Participant A, MCPTT Floor Control Server, and IWF. The sequence starts with an established session where floor control is established and floor is granted to the IWF. Then, User A wants to talk and sends a floor request. The floor control server performs floor arbitration by priority. It grants the floor to User A (5a. Floor granted) and takes the floor from the IWF (5b. Floor taken). User A receives a grant notification (6a. Grant notification) and the IWF receives an override notification (6b. Override notification (not received; audio continues)). Finally, voice media is transmitted from User A to the IWF (7. Voice media). + +**Figure 10.5.4-1: Floor override (overridden continues to transmit) during an interworking session** + +1. It is assumed that the floor participant B (represented by the IWF in figure 10.5.4-1) has been given the floor and is transmitting voice media. +2. Floor participant A, having a floor priority which is relatively higher than that of floor participant B, wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. + +4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the floor priority information that is received in the floor request message. +- 5a. Floor control server responds with a floor granted message to floor participant A. +- 5b. Floor control server sends a floor taken message to the other floor participants (via the IWF). Floor participant B continues transmitting the (overridden) voice media transmission. + +NOTE 1: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn who the newly granted talker (overriding) is. + +- 6a. The floor granted causes the user of floor participant A to be notified. +- 6b. Floor participant B cannot be notified of the status because it is unable to receive the message and continues transmitting. +7. Floor participant A (overriding) starts sending voice media over the session established beforehand. + +NOTE 2: Floor participant B is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration. + +NOTE 3: When floor participant A stops transmitting, if floor participant B is still sending voice, then the floor is granted back to floor participant B and audio is routed to all current floor participants. + +## 10.5.5 Floor control on an interworking group homed in the LMR system + +Figure 10.5.5-1 shows the procedure for floor control on an interworking group homed in the LMR system. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is homed in the LMR system. +2. The MCPTT server is configured to locally filter competing floor control requests before communicating with the IWF. +3. MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) are affiliated to that group. +4. An interworking group call is ongoing involving MCPTT users and LMR users (represented by the IWF). The floor is currently idle. + +![Sequence diagram illustrating floor control on a group homed in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. Steps include: 1. User wants to talk (both clients); 2. Floor request (both clients to server); 3. Filter based on local arbitration result (server); 4. Floor rejected (server to Client 2); 5. IWF Floor request (server to IWF); 6. IWF Floor granted (IWF to server); 7. Floor granted (server to Client 1); 8. Floor taken (server to Client 2); 9. Talker notification (Client 1); 10. Voice media (Client 1 to server, server to IWF, and IWF to Client 2).](81a0abf9a79b27cf9d765553216b173c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + + Note left of MCPTT Client 1: 1. User wants to talk + Note left of MCPTT Client 2: 1. User wants to talk + MCPTT Client 1->>MCPTT server: 2. Floor request + MCPTT Client 2->>MCPTT server: 2. Floor request + Note right of MCPTT server: 3. Filter based on local arbitration result. + MCPTT server->>MCPTT Client 2: 4. Floor rejected + MCPTT server->>IWF: 5. IWF Floor request + IWF->>MCPTT server: 6. IWF Floor granted + MCPTT server->>MCPTT Client 1: 7. Floor granted + MCPTT server->>MCPTT Client 2: 8. Floor taken + Note left of MCPTT Client 1: 9. Talker notification + MCPTT Client 1->>MCPTT server: 10. Voice media + MCPTT server->>IWF: 10. IWF Voice media + MCPTT server->>MCPTT Client 2: 10. Voice media + +``` + +Sequence diagram illustrating floor control on a group homed in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. Steps include: 1. User wants to talk (both clients); 2. Floor request (both clients to server); 3. Filter based on local arbitration result (server); 4. Floor rejected (server to Client 2); 5. IWF Floor request (server to IWF); 6. IWF Floor granted (IWF to server); 7. Floor granted (server to Client 1); 8. Floor taken (server to Client 2); 9. Talker notification (Client 1); 10. Voice media (Client 1 to server, server to IWF, and IWF to Client 2). + +**Figure 10.5.5-1: Floor control on a group homed in the LMR system** + +1. The users of MCPTT Client 1 and MCPTT Client 2 both want to send voice media over the session. +2. MCPTT Clients 1 and 2 send floor request messages to the floor control server. +3. The MCPTT floor control server determines to accept the floor request from MCPTT Client 1 based on local arbitration results (e.g., according to priority information versus the competing request from MCPTT client 2). +4. The user of MCPTT client 2 is notified that their floor request was rejected. +5. Since the group is homed in the LMR system the MCPTT floor control server forwards the floor request to the IWF for final floor control determination. The IWF performs floor arbitration in conjunction with the LMR system (not shown). The IWF determines that the floor can be granted to the MCPTT user. +6. The IWF sends a floor granted message to the MCPTT floor control server. +7. The MCPTT floor control server sends a floor granted message to MCPTT client 1. +8. The MCPTT floor control server sends a floor taken message to MCPTT client 2 to notify the user of who is granted the floor. +9. MCPTT Client 1 notifies the user that he/she has been granted the floor and may begin speaking. +10. MCPTT Client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF. + +## 10.5.6 Floor control on an interworking group homed in the MCPTT system + +Figure 10.5.6-1 shows the procedure for floor control on an interworking group homed in the MCPTT system, and the LMR system is configured for local floor control request filtering. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is homed in the MCPTT system. +2. The interworking group is previously defined on the group management server. +3. MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) are affiliated to that group. +4. An interworking group call is ongoing involving MCPTT users and LMR users (represented by the IWF). The floor is currently idle. + +![Sequence diagram illustrating floor control on a group homed in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 wanting to talk, followed by floor requests from both MCPTT Client 1 and IWF. The MCPTT server performs floor arbitration by policy, granting the floor to MCPTT Client 1 and rejecting the IWF's request. MCPTT Client 1 then notifies the talker, and voice media is exchanged between MCPTT Client 1 and the MCPTT server, which is then forwarded to the IWF.](36e11608a186ec372afec7470985ff56_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + + Note left of MCPTT Client 1: 1. User wants to talk + MCPTT Client 1->>MCPTT server: 2. Floor request + IWF->>MCPTT server: 3. IWF Floor request + Note right of MCPTT server: 4. Floor arbitration by policy + MCPTT server->>IWF: 5. IWF Floor rejected + MCPTT server->>MCPTT Client 1: 6. Floor granted + Note left of MCPTT Client 1: 8. Talker notification + MCPTT server->>MCPTT Client 2: 7. Floor taken + IWF->>MCPTT server: 7. IWF Floor taken + Note right of MCPTT server: 9. Voice media + MCPTT Client 1->>MCPTT server: 9. Voice media + MCPTT server->>IWF: 9. IWF Voice media + IWF->>MCPTT server: 9. Voice media + +``` + +Sequence diagram illustrating floor control on a group homed in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 wanting to talk, followed by floor requests from both MCPTT Client 1 and IWF. The MCPTT server performs floor arbitration by policy, granting the floor to MCPTT Client 1 and rejecting the IWF's request. MCPTT Client 1 then notifies the talker, and voice media is exchanged between MCPTT Client 1 and the MCPTT server, which is then forwarded to the IWF. + +**Figure 10.5.6-1: Floor control on a group homed in the MCPTT system** + +1. The user of MCPTT Client 1 wants to send voice media over the session. At the same time a user in the LMR system (represented by the IWF) wants to also send voice media over the session. +2. MCPTT Client 1 sends a floor request message to the MCPTT floor control server. +3. The IWF sends a floor request message to the MCPTT floor control server. + +NOTE: If multiple LMR users want to speak, it is assumed that the LMR system has arbitrated these requests based on local policies and only presents one floor request to the MCPTT system. + +4. Since the group is homed in the MCPTT system the MCPTT floor control server performs final floor control determination. In this case the MCPTT floor control server determines to accept the floor request from MCPTT + +Client 1 based on local policy and arbitration results (e.g., according to time of arrival of the request versus the competing request from the IWF). + +5. The IWF is notified that its floor request was rejected. +6. The MCPTT floor control server sends a floor granted message to MCPTT client 1. +7. The MCPTT floor control server sends a floor taken message to both MCPTT client 2 and the IWF to inform them of who is granted the floor. +8. MCPTT Client 1 notifies the user that he/she has been granted the floor and may begin speaking. +9. MCPTT Client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF. + +### 10.5.7 Floor control without local filtering on an interworking group defined in the LMR system + +Figure 10.5.7-1 shows the procedure for floor control on an interworking group defined in the LMR system where local filtering is not performed by the MCPTT server. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is defined in the LMR system. +2. The MCPTT system is configured to send competing floor control requests to the LMR system (represented by the IWF) for floor control arbitration. +3. MCPTT client 1, MCPTT client 2, and LMR users are affiliated to that group. +4. An interworking group call is ongoing involving MCPTT users and LMR users. The floor is currently idle. + +![Sequence diagram illustrating floor control without local filtering on a group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. Both clients send floor requests. The server forwards them to the IWF. The IWF grants the floor to client 1, rejects client 2, and sends a floor taken message to client 2. The server then notifies client 1 of the granted floor and client 2 of the taken floor. Finally, client 1 sends voice media, which is distributed by the server and IWF to all participants.](4c1ea859b93043f2fa17a8fe72fb6176_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + + Note left of MCPTT client 1: 1. User wants to talk + Note left of MCPTT client 2: 1. User wants to talk + MCPTT client 1->>MCPTT server: 2. Floor request + MCPTT client 2->>MCPTT server: 2. Floor request + MCPTT server->>IWF: 3. IWF Floor request + MCPTT server->>IWF: 3. IWF Floor request + IWF->>MCPTT server: 4. IWF Floor granted + IWF->>MCPTT server: 4. IWF Floor rejected + IWF->>MCPTT server: 4. IWF Floor taken + MCPTT server->>MCPTT client 2: 5. Floor rejected + MCPTT server->>MCPTT client 1: 6. Floor granted + MCPTT server->>MCPTT client 2: 7. Floor taken + Note right of MCPTT client 1: 8. Talker notification + MCPTT client 1->>MCPTT server: 9. Voice media + MCPTT server->>IWF: 9. IWF Voice media + MCPTT server->>MCPTT client 2: 9. Voice media + +``` + +Sequence diagram illustrating floor control without local filtering on a group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. Both clients send floor requests. The server forwards them to the IWF. The IWF grants the floor to client 1, rejects client 2, and sends a floor taken message to client 2. The server then notifies client 1 of the granted floor and client 2 of the taken floor. Finally, client 1 sends voice media, which is distributed by the server and IWF to all participants. + +**Figure 10.5.7-1: Floor control without local filtering on a group defined in the LMR system** + +1. The users of MCPTT client 1 and MCPTT client 2 both want to send voice media over the session. +2. MCPTT clients 1 and 2 send floor request messages to the MCPTT floor control server. +3. Since the group is defined in the LMR system the MCPTT floor control server forwards these floor requests to the IWF for final floor control determination. The IWF performs floor arbitration in conjunction with the LMR system (not shown). The IWF determines that the floor can be granted to MCPTT client 1. +4. The IWF sends an IWF floor granted message for MCPTT client 1, an IWF floor rejected message for MCPTT client 2, and an IWF floor taken message for MCPTT client 2 to the MCPTT floor control server. + +NOTE: If other MCPTT clients are affiliated to this group, the IWF sends an IWF floor taken message to the MCPTT floor control server for each one of them. + +5. The MCPTT floor control server sends a Floor rejected message to MCPTT client 2 to notify the user that his/her floor request was rejected. +6. The MCPTT floor control server sends a Floor granted message to MCPTT client 1. +7. The MCPTT floor control server sends a Floor taken message to MCPTT client 2 to notify the user of who is granted the floor. +8. MCPTT client 1 notifies the user that he/she has been granted the floor and may begin speaking. +9. MCPTT client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF. + +## 10.5.8 Floor control without local filtering on an interworking group defined in the MCPTT system + +Figure 10.5.8-1 shows the procedure for floor control on an interworking group defined in the MCPTT system where local filtering is not performed by the LMR system. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is defined in the MCPTT system. +2. MCPTT client 1, MCPTT client 2, and LMR users are affiliated to that group. +3. The LMR system (represented by the IWF) is configured to send all competing floor control requests to the MCPTT system for floor control arbitration. +4. The IWF is not affiliating on behalf of LMR users. All LMR group affiliations are passed through the IWF to the MCPTT server. +5. An interworking group call is ongoing involving MCPTT users and LMR users. The floor is currently idle. + +![Sequence diagram illustrating floor control without local filtering on a group defined in the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. MCPTT client 1 sends a floor request. Simultaneously, the IWF sends two floor requests for LMR users. The MCPTT server performs floor arbitration by policy. It grants the floor to MCPTT client 1 and rejects the IWF's requests. MCPTT client 1 receives a floor granted message and notifies its user. The IWF receives floor rejected messages and informs its users. MCPTT client 2 receives a floor taken message. Voice media is then exchanged between MCPTT client 1 and the IWF via the MCPTT server.](29997432244f81212ee1e6c94f308f1b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + + Note left of MCPTT client 1: 1. User wants to talk + MCPTT client 1->>MCPTT server: 2. Floor request + Note right of IWF: 3. IWF floor request + Note right of IWF: 3. IWF floor request + Note right of MCPTT server: 4. Floor arbitration by policy + MCPTT server->>IWF: 5. IWF floor rejected + MCPTT server->>IWF: 5. IWF floor rejected + MCPTT server->>MCPTT client 1: 6. Floor granted + Note left of MCPTT client 1: 8. Talker notification + MCPTT server->>MCPTT client 2: 7. Floor taken + Note right of IWF: 7. IWF floor taken + Note right of IWF: 7. IWF floor taken + MCPTT client 1->>MCPTT server: 9. Voice media + MCPTT server->>IWF: 9. IWF voice media + MCPTT server->>MCPTT client 2: 9. Voice media + +``` + +Sequence diagram illustrating floor control without local filtering on a group defined in the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. MCPTT client 1 sends a floor request. Simultaneously, the IWF sends two floor requests for LMR users. The MCPTT server performs floor arbitration by policy. It grants the floor to MCPTT client 1 and rejects the IWF's requests. MCPTT client 1 receives a floor granted message and notifies its user. The IWF receives floor rejected messages and informs its users. MCPTT client 2 receives a floor taken message. Voice media is then exchanged between MCPTT client 1 and the IWF via the MCPTT server. + +**Figure 10.5.8-1: Floor control without local filtering on a group defined in the MCPTT system** + +1. The user of MCPTT client 1 wants to send voice media over the session. At the same time multiple users in the LMR system (represented by the IWF) want to also send voice media over the session. +2. MCPTT client 1 sends a floor request message to the MCPTT floor control server. +3. The IWF sends floor request messages to the MCPTT floor control server for each LMR user requesting the floor. In this case two LMR users are requesting the floor. These floor requests contain the MCPTT ID of the LMR user (converted by the IWF). + +4. Since the group is defined in the MCPTT system the MCPTT floor control server performs final floor control determination. In this case the MCPTT floor control server determines to accept the floor request from MCPTT client 1 based on local policy and arbitration results (e.g., according to priority of the request versus the competing requests from the IWF). + 5. The IWF is notified that its floor requests were rejected. The MCPTT floor control server sends an IWF floor rejected message to the IWF for each floor request. + 6. The MCPTT floor control server sends a floor granted message to MCPTT client 1. + 7. The MCPTT floor control server sends floor taken messages to MCPTT client 2 and the IWF to inform them of who is granted the floor. In this case a floor taken message is sent to the IWF corresponding to each affiliated LMR user. +- NOTE: If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF floor taken message is sent to the IWF. +8. MCPTT client 1 notifies the user that he/she has been granted the floor and may begin speaking. + 9. MCPTT client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the LMR users. + +### 10.5.9 Floor control in private call controlled by the LMR system + +Figure 10.5.9-1 shows a procedure for a private call with floor control where the LMR system controls the floor. A request for transmission by the MCPTT user while the LMR user has the floor is rejected by the IWF, to show various aspects of interworking floor control. + +Pre-conditions: + +1. A private call has been set up between an LMR user and MCPTT client 1. +2. The LMR system is controlling the floor, via the IWF. +3. MCPTT client 1 has the floor. + +![Sequence diagram illustrating floor control with control by the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a 'Floor release' to the MCPTT server, which then sends 'IWF floor release' to the IWF. The IWF responds with 'IWF floor idle', which the MCPTT server relays as 'Floor idle' to the client. Next, the IWF sends 'IWF floor taken' to the MCPTT server, which relays it as 'Floor taken' to the client. Voice media is then exchanged: '7a. Voice media' from IWF to MCPTT server, and '7b. Voice media' from MCPTT server to MCPTT Client 1. A box indicates '8. User decides to interrupt LMR user transmission'. Then, MCPTT Client 1 sends '9. Floor request' to the MCPTT server, which sends '10. IWF Floor request' to the IWF. The IWF responds with '11. IWF floor rejected' to the MCPTT server, which relays it as '12. Floor rejected' to the client.](365ac42391d8f7b1dac76b967a948788_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 8. User decides to interrupt LMR user transmission + MCPTT Client 1->>MCPTT server: 1. Floor release + MCPTT server->>IWF: 2. IWF floor release + IWF-->>MCPTT server: 3. IWF floor idle + MCPTT server-->>MCPTT Client 1: 4. Floor idle + IWF-->>MCPTT server: 5. IWF floor taken + MCPTT server-->>MCPTT Client 1: 6. Floor taken + IWF-->>MCPTT server: 7a. Voice media + MCPTT server-->>MCPTT Client 1: 7b. Voice media + MCPTT Client 1->>MCPTT server: 9. Floor request + MCPTT server->>IWF: 10. IWF Floor request + IWF-->>MCPTT server: 11. IWF floor rejected + MCPTT server-->>MCPTT Client 1: 12. Floor rejected + +``` + +Sequence diagram illustrating floor control with control by the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a 'Floor release' to the MCPTT server, which then sends 'IWF floor release' to the IWF. The IWF responds with 'IWF floor idle', which the MCPTT server relays as 'Floor idle' to the client. Next, the IWF sends 'IWF floor taken' to the MCPTT server, which relays it as 'Floor taken' to the client. Voice media is then exchanged: '7a. Voice media' from IWF to MCPTT server, and '7b. Voice media' from MCPTT server to MCPTT Client 1. A box indicates '8. User decides to interrupt LMR user transmission'. Then, MCPTT Client 1 sends '9. Floor request' to the MCPTT server, which sends '10. IWF Floor request' to the IWF. The IWF responds with '11. IWF floor rejected' to the MCPTT server, which relays it as '12. Floor rejected' to the client. + +Figure 10.5.9-1: Floor control with control by the LMR system + +1. The user of MCPTT Client 1 finishes transmission and MCPTT client 1 releases the floor. + +2. The MCPTT server informs the IWF of the floor release. + 3. The IWF indicates that the floor is now idle. + 4. MCPTT client 1 is informed that the floor is idle. + 5. The IWF indicates that the floor has been taken by the LMR user. + 6. The MCPTT server informs MCPTT client 1 that the floor has been taken by the LMR user. + 7. Media flows from the LMR user to the IWF (7a) and on to MCPTT client 1 (7b). + 8. The user of MCPTT client 1 decides to interrupt the transmission from the LMR user. + 9. MCPTT Client 1 sends a floor request with an appropriate priority to request interruption of the transmission from the LMR user. + 10. The MCPTT server forwards the floor request to the IWF. + 11. The LMR system rejects the request, and the IWF informs the MCPTT server of the rejection. +- NOTE: The reason that the request is rejected is outside the scope of the present document. +12. The MCPTT server informs MCPTT client 1 that the request for interruption has been rejected. + +## 10.5.10 Floor control in private call controlled by the MCPTT system + +Figure 10.5.10-1 shows a procedure for a private call with floor control where the MCPTT system controls the floor. A request for transmission by the LMR user while the MCPTT user has the floor is accepted by the MCPTT server, to show various aspects of interworking floor control. + +Pre-conditions: + +1. A private call has been set up between the LMR user and MCPTT client 1. +2. The MCPTT server is controlling the floor. +3. The floor is idle. + +![Sequence diagram illustrating floor control in a private call controlled by the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a floor request to the MCPTT server, which is granted. The MCPTT server then informs the IWF that the floor is taken. MCPTT Client 1 sends voice media to the MCPTT server, which is forwarded to the IWF. The IWF receives a request for interruption from the LMR user and sends a floor request to the MCPTT server. The MCPTT server decides to grant the floor to the LMR user, revokes the floor from MCPTT Client 1, and informs the IWF that the floor is granted. The IWF sends voice media to the MCPTT server, which is then forwarded to MCPTT Client 1.](912a57b374babddd0201eecb2e9e1e4b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant IWF + Note right of IWF: 5. IWF receives request for interruption from LMR user + MCPTT Client 1->>MCPTT server: 1. Floor request + MCPTT server-->>MCPTT Client 1: 2. Floor granted + MCPTT server->>IWF: 3. IWF floor taken + MCPTT Client 1->>MCPTT server: 4a. Voice media + MCPTT server->>IWF: 4b. Voice media + Note right of IWF: 5. IWF receives request for interruption from LMR user + IWF->>MCPTT server: 6. IWF floor request + Note right of MCPTT server: 7. MCPTT server decides to grant floor to LMR user + MCPTT server-->>MCPTT Client 1: 8. Floor revoked + MCPTT server->>IWF: 9. IWF floor granted + IWF->>MCPTT server: 10a. Voice media + MCPTT server->>MCPTT Client 1: 10b. Voice media + +``` + +Sequence diagram illustrating floor control in a private call controlled by the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a floor request to the MCPTT server, which is granted. The MCPTT server then informs the IWF that the floor is taken. MCPTT Client 1 sends voice media to the MCPTT server, which is forwarded to the IWF. The IWF receives a request for interruption from the LMR user and sends a floor request to the MCPTT server. The MCPTT server decides to grant the floor to the LMR user, revokes the floor from MCPTT Client 1, and informs the IWF that the floor is granted. The IWF sends voice media to the MCPTT server, which is then forwarded to MCPTT Client 1. + +Figure 10.5.10-1: Floor control with control by the MCPTT system + +1. MCPTT Client 1 requests the floor. +2. The MCPTT server grants the floor to MCPTT Client 1. +3. The MCPTT server informs the IWF that the floor has been granted to MCPTT client 1. + +NOTE 1: Step 3 may occur before or after step 2. + +4. MCPTT client 1 sends voice media to the MCPTT server (4a) which forwards the voice media to the IWF (4b). +5. The LMR user decides to interrupt the transmission from MCPTT client 1, and the IWF is informed. +6. The IWF sends a floor request to the MCPTT server with sufficient priority to interrupt MCPTT client 1. +7. The MCPTT server decides to allow the interruption from the LMR user, based on the priority of the request and on configuration. +8. The MCPTT server informs MCPTT Client 1 that the transmission permission has been revoked. +9. The floor is granted to the LMR user via the IWF. + +NOTE 2: Step 9 may occur before or after step 8. + +10. Voice media is sent from the LMR user via the IWF to the MCPTT server (10a) and on to MCPTT client 1 (10b). + +## 10.6 Emergency and imminent peril + +### 10.6.1 Information flows for emergency and imminent peril + +#### 10.6.1.1 IWF emergency group call request + +Table 10.6.1.1-1 describes the information flow IWF emergency group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.1-1: IWF emergency group call request information elements** + +| Information Element | Status | Description | +|-----------------------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Emergency indicator | M | Indicates that the group call request is an MCPTT emergency call | +| Alert indicator | O | May be used to indicate that an emergency alert is to be sent | +| Location | O | Location, if available | +| Implicit floor request (see NOTE) | O | Indicates that the originating client requests the floor | +| NOTE: | | This element shall be included only when the originating client requests the floor. | + +#### 10.6.1.2 IWF emergency group call response + +Table 10.6.1.2-1 describes the information flow IWF emergency group call response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.6.1.2-1: IWF emergency group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | The IWF emergency group call request may be rejected. | + +### 10.6.1.3 IWF imminent peril group call request + +Table 10.6.1.3-1 describes the information flow IWF imminent peril group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.3-1: IWF imminent peril group call request information elements** + +| Information Element | Status | Description | +|-----------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Imminent peril indicator | M | Indicates that the group call request is an imminent peril call | +| Location | O | Location, if available | +| Implicit floor request (see NOTE) | O | Indicates that the originating client requests the floor | +| NOTE: | | This element shall be included only when this information flow is from the client to the server and the originator requests the floor. | + +### 10.6.1.4 IWF imminent peril group call response + +Table 10.6.1.4-1 describes the information flow IWF imminent peril group call response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.4-1: IWF imminent peril group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | The IWF imminent peril group call request may be rejected. | + +### 10.6.1.5 IWF in-progress imminent peril group state cancel request + +Table 10.6.1.5-1 describes the information flow IWF in-progress imminent peril group state cancel request from the MCPTT server to the IWF. + +**Table 10.6.1.5-1: IWF in-progress imminent peril group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the in-progress imminent peril state is to be cancelled | + +### 10.6.1.6 IWF in-progress imminent peril group state cancel response + +Table 10.6.1.6-1 describes the information flow IWF in-progress imminent peril group state cancel response from the IWF to the MCPTT server. + +**Table 10.6.1.6-1: IWF in-progress imminent peril group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the in-progress imminent peril state is to be cancelled | + +### 10.6.1.7 IWF emergency alert request + +Table 10.6.1.7-1 describes the information flow IWF emergency alert request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.7-1: IWF emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Organization name | O | The alerting MCPTT user's mission critical organization name. | +| Location | O | The alerting MCPTT client's location | + +### 10.6.1.8 IWF emergency alert response + +Table 10.6.1.8-1 describes the information flow IWF emergency alert response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.8-1: IWF emergency alert response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +### 10.6.1.9 IWF emergency alert cancel request + +Table 10.6.1.9-1 describes the information flow IWF emergency alert cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.9-1: IWF emergency alert cancel request information elements** + +| Information Element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity of the cancelling party | +| MCPTT ID (see NOTE) | O | MCPTT user identity whose emergency alert is to be cancelled | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Group's in-progress emergency alert cancel request | O | Requests cancellation of the in-progress emergency alert of the group | +| NOTE: This information shall be present if the message is requesting cancellation of another MCPTT user's alert. If not present, then the alert of the MCPTT ID of the cancelling party is being cancelled | | | + +#### 10.6.1.10 IWF emergency alert cancel response + +Table 10.6.1.10-1 describes the information flow IWF emergency alert cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.10-1: IWF emergency alert cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +#### 10.6.1.11 IWF in-progress emergency group state cancel request + +Table 10.6.1.11-1 describes the information flow IWF in-progress emergency group state cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.11-1: IWF in-progress emergency group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency state is to be cancelled. | +| Alert indicator | O | Indicates whether the emergency alert of the cancelling party is to be cancelled | + +#### 10.6.1.12 IWF in-progress emergency group state cancel response + +Table 10.6.1.12-1 describes the information flow IWF in-progress emergency group state cancel response from the MCPTT server to the IWF and from IWF to MCPTT server. + +**Table 10.6.1.12-1: IWF in-progress emergency group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency in-progress is to be cancelled. | + +## 10.6.2 Emergency calls + +### 10.6.2.1 General + +This subclause addresses various aspects of emergency call interworking. + +Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF emergency group call request / IWF in-progress emergency group state cancel request message is sent to the IWF at the commencement / release of an emergency group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF emergency group call request / IWF in-progress emergency group state cancel request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document. + +Where the group is defined in the LMR system, the IWF shall send individual IWF emergency group call request / IWF in-progress emergency group state cancel request messages to the IWF for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. + +### 10.6.2.2 Emergency group call + +#### 10.6.2.2.1 Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the MCPTT system + +Figure 10.6.2.2.1-1 shows the procedure for an emergency group call setup initiated by a user in the LMR system. The figure is based upon the figure for emergency calls in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the group is an interworking group defined in the MCPTT system. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The emergency interworking call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the MCPTT system +2. MCPTT client 1 and MCPTT client 2 are affiliated to that MCPTT group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between MCPTT system and LMR system has been configured at the IWF. +5. LMR user initiates an emergency group call. + +![Sequence diagram for Emergency group call setup, initiated by LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT Client 2.](c05763eff20551449de1eac378fed769_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT Client 2 + + Note right of MCPTT server: 2. Affiliate the user + Note right of MCPTT server: 3. Check authorization and affiliated group members + Note right of MCPTT server: 4. Bearer priority configuration + Note right of MCPTT server: 5. Record the emergency state of the group + + IWF->>MCPTT server: 1. IWF emergency group call request + MCPTT server-->>MCPTT client 1: 6. Call the affiliated MCPTT clients + MCPTT server-->>MCPTT Client 2: 6. Call the affiliated MCPTT clients + MCPTT server-->>IWF: 7. IWF emergency group call request + IWF-->>MCPTT server: 8. IWF emergency group call response + MCPTT server-->>IWF: 9. IWF emergency group call response + Note right of MCPTT client 1: 10. Media plane is established + Note right of MCPTT Client 2: 10. Media plane is established + +``` + +Sequence diagram for Emergency group call setup, initiated by LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT Client 2. + +**Figure 10.6.2.2.1-1: Emergency group call setup, initiated by LMR user on an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF emergency group call request including a MCPTT group ID to the MCPTT server. The request contains an indication of the MCPTT emergency. The IWF may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request. +2. The MCPTT server implicitly affiliates the MCPTT ID of the LMR user to the MCPTT emergency group if the user is not already affiliated. If the IWF is configured to affiliate on behalf of all of its group members in a single affiliation step, the MC service server affiliates the IWF instead of an individual MC service ID. +3. The MCPTT server checks whether the MCPTT ID of the LMR user is authorized for initiation of MCPTT emergency calls on the indicated MCPTT group. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. +4. The MCPTT server configures the priority of the underlying bearers for all MCPTT participants in the MCPTT group. All successive calls during the MCPTT group's in-progress emergency state will receive the adjusted bearer priority. +5. The MCPTT server records the emergency state of the group. Once an MCPTT emergency call has been initiated, the MCPTT group is in an in-progress emergency state until that state is cancelled. + +NOTE 3: The IWF actions for priority are out of scope of the present document. + +6. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members as defined in 3GPP TS 23.379 [7]. +7. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF emergency group call request is sent (to the IWF) for each affiliated LMR user. +8. The IWF returns IWF emergency group call response(s) to the MCPTT server. + +9. The MCPTT server sends the IWF emergency group call response to the IWF (as a response to the request received in step 1) to inform of the successful MCPTT emergency group call establishment. + +NOTE 4: How the LMR group members are called within the LMR system is out scope of the present document. + +NOTE 5: Step 9 can occur at any time following step 5, but at the latest following step 8 depending on the conditions to proceed with the call. + +10. The LMR users via the IWF and the affiliated MCPTTs have successfully established media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call. + +#### 10.6.2.2.2 Emergency group call setup initiated by a user in the MCPTT system on an interworking group defined in MCPTT system + +Figure 10.6.2.2.2-1 shows the procedure for an emergency group call setup initiated by a user in the MCPTT system. The figure is based upon the figure for emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the MCPTT system. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the MCPTT system. +2. MCPTT client 2 is affiliated to the MCPTT group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between MCPTT system and LMR system has been configured at the IWF. +5. The initiating MCPTT client 1 has been provisioned with the MCPTT group that has been designated via provisioning as the MCPTT emergency group. + +NOTE 3: Alternatively, the client could have been provisioned for emergency behaviour on the selected group. + +![Sequence diagram for Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF.](b0b9bc3067d012eb2fa3539217b9c34d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + + Note left of MCPTT Client 1: 1. Initiate emergency group call + MCPTT Client 1->>MCPTT server: 2.MCPTT emergency group call request + Note right of MCPTT server: 3. Affiliate the user + Note right of MCPTT server: 4. Check authorization and affiliated group members + Note right of MCPTT server: 5. Bearer priority configuration + Note right of MCPTT server: 6. Record the emergency state of the group + MCPTT server->>IWF: 7. IWF emergency group call request + IWF-->>MCPTT server: 8. IWF emergency group call response + Note right of MCPTT server: 9. Call the affiliated MCPTT clients + MCPTT server-->>MCPTT Client 1: 10.MCPTT emergency group call response + Note right of MCPTT Client 1: 11. Media plane is established + +``` + +Sequence diagram for Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. + +**Figure 10.6.2.2.2-1: Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system** + +1. An MCPTT user initiates an emergency group call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. The MCPTT client sends an MCPTT emergency group call request to the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT client may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request. +3. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated. +4. The MCPTT server checks whether the MCPTT user of the MCPTT client 1 is authorized for initiation of MCPTT emergency calls on the indicated interworking group. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. +5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. + +NOTE 4: Successive calls during the group's in-progress emergency state will all receive the adjusted bearer priority. + +6. The MCPTT server records the in-progress emergency state of the group. The MCPTT server also records the identity of the MCPTT user that initiated the MCPTT emergency group call until the MCPTT emergency is cancelled. Once an MCPTT emergency group call has been initiated, the MCPTT group is considered to be in an in-progress emergency state until that state is cancelled. +7. The MCPTT server sends an IWF emergency group call request to IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF emergency group call request is sent (to the IWF) for each affiliated LMR user. + +8. IWF responds with the IWF emergency group call response(s) to MCPTT server to inform of the successful MCPTT emergency call establishment. + +NOTE 5: How the LMR group members are called within the LMR system is out of scope of the present document. + +NOTE 6: Steps 7 to 8 can occur at any time between steps 5 and 10. + +NOTE 7: IWF actions for priority are out of scope of the present document. + +9. The MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members as defined in 3GPP TS 23.379 [7]. + +10. The MCPTT server sends an MCPTT emergency group call response to the MCPTT client to inform of the successful MCPTT emergency call establishment. + +NOTE 8: Step 10 can occur at any time following step 8, but at the latest following step 9, depending on the conditions to proceed with the call. + +11. The LMR users via the IWF and the affiliated MCPTT clients have successfully established media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call. + +### 10.6.2.2.3 Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the LMR system + +Figure 10.6.2.2.3-1 shows the procedure for an emergency group call setup initiated by a user in the LMR system. The figure is based upon the figure for emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the LMR system. + +NOTE 1: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are affiliated to that group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. LMR user initiates an emergency group call. + +![Sequence diagram for Emergency group call setup initiated by LMR user on an interworking group defined in the LMR system. The diagram shows four lifelines: IWF, MCPTT server, MCPTT Client 1, and MCPTT Client 2. The sequence of messages is: 1a. IWF emergency group call request to MCPTT server; 1b. IWF emergency group call request to MCPTT server; 2a. MCPTT emergency group call request from MCPTT server to MCPTT Client 1; 2b. MCPTT emergency group call request from MCPTT server to MCPTT Client 2; 3a. MCPTT emergency group call response from MCPTT Client 1 to MCPTT server; 3b. MCPTT emergency group call response from MCPTT Client 2 to MCPTT server; 4a. IWF emergency group call response from MCPTT server to IWF; 4b. IWF emergency group call response from MCPTT server to IWF; 5. Media plane is established (shown as a horizontal bar at the bottom).](67725cb5fabfd68d3a6e8c12589d4c06_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT Client 1 + participant MCPTT Client 2 + Note left of IWF: 5. Media plane is established + IWF->>MCPTT server: 1a. IWF emergency group call request + IWF->>MCPTT server: 1b. IWF emergency group call request + MCPTT server->>MCPTT Client 1: 2a. MCPTT emergency group call request + MCPTT server->>MCPTT Client 2: 2b. MCPTT emergency group call request + MCPTT Client 1->>MCPTT server: 3a. MCPTT emergency group call response + MCPTT Client 2->>MCPTT server: 3b. MCPTT emergency group call response + MCPTT server->>IWF: 4a. IWF emergency group call response + MCPTT server->>IWF: 4b. IWF emergency group call response + +``` + +Sequence diagram for Emergency group call setup initiated by LMR user on an interworking group defined in the LMR system. The diagram shows four lifelines: IWF, MCPTT server, MCPTT Client 1, and MCPTT Client 2. The sequence of messages is: 1a. IWF emergency group call request to MCPTT server; 1b. IWF emergency group call request to MCPTT server; 2a. MCPTT emergency group call request from MCPTT server to MCPTT Client 1; 2b. MCPTT emergency group call request from MCPTT server to MCPTT Client 2; 3a. MCPTT emergency group call response from MCPTT Client 1 to MCPTT server; 3b. MCPTT emergency group call response from MCPTT Client 2 to MCPTT server; 4a. IWF emergency group call response from MCPTT server to IWF; 4b. IWF emergency group call response from MCPTT server to IWF; 5. Media plane is established (shown as a horizontal bar at the bottom). + +**Figure 10.6.2.2.3-1: Emergency group call setup, initiated by LMR user on an interworking group defined in the LMR system** + +1. The IWF sends an IWF emergency group call request(s) to the MCPTT server. An emergency group call request is sent individually for each affiliated MCPTT user in the group. The request contains an indication of the MCPTT emergency. + +NOTE 2: IWF actions for priority are out of scope of the present document. + +2. The MCPTT server configures the priority of the underlying bearers and sends the MCPTT emergency group call request(s) as defined in 3GPP TS 23.379 [7]. + +NOTE 3: Successive calls during the MCPTT group's in-progress emergency state will all receive the adjusted bearer priority. + +3. The MCPTT clients respond with MCPTT emergency group call response to the MCPTT server. + +4. The MCPTT server sends the IWF emergency group call response(s) to the IWF to inform of the successful MCPTT emergency call establishment. + +NOTE 4: How the LMR group members are called within the LMR system is out of scope of the present document. + +5. The LMR users via the IWF and the affiliated MCPTT clients have successfully established media plane for communication. The LMR system where the interworking group is defined is the controlling system of the group call. + +#### 10.6.2.2.4 Emergency group call setup initiated by a user in the MCPTT system to an interworking group defined in the LMR system + +Figure 10.6.2.2.4-1 shows the procedure for an emergency group call initiated by a user in the MCPTT system. The figure is based upon the figure for MCPTT emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the LMR system. + +NOTE 1: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the LMR system. +2. MCPTT client 2 is affiliated to the MCPTT group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +![Sequence diagram illustrating the emergency group call setup initiated by an MCPTT user to an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF.](5661815043254c37a4e3e4833f51e727_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 1. Initiate emergency group call + MCPTT Client 1->>MCPTT server: 2. MCPTT emergency group call request + MCPTT server->>IWF: 3. IWF emergency group call request + IWF->>MCPTT server: 4. IWF emergency group call request + MCPTT server->>MCPTT Client 2: 5. MCPTT emergency group call request + MCPTT Client 2->>MCPTT server: 6. MCPTT emergency group call response + MCPTT server->>IWF: 7. IWF emergency group call response + IWF->>MCPTT server: 8. IWF emergency group call response + MCPTT server->>MCPTT Client 1: 9. MCPTT emergency group call response + Note right of MCPTT server: 10. Media plane is established + +``` + +Sequence diagram illustrating the emergency group call setup initiated by an MCPTT user to an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. + +**Figure 10.6.2.2.4-1: Emergency group call setup, initiated by MCPTT user to an interworking group defined in the LMR system** + +1. An MCPTT user initiates an emergency group call. +2. The MCPTT client sends an MCPTT emergency group call request to the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT client may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request. +3. The MCPTT server configures the priority of the underlying bearer and sends an IWF emergency group call request to the IWF. +4. The IWF sends an individual IWF emergency group call request to the MCPTT server for each affiliated MCPTT group member, in this example to a user in MCPTT client 2. + +NOTE 2: How the LMR group members are called within the LMR system is outside the scope of the present document. + +NOTE 3: All successive calls during the MCPTT group's in-progress emergency state will receive the adjusted bearer priority. + +NOTE 4: IWF actions for priority are out of scope of the present document. + +5. The MCPTT server configures the priority of the underlying bearer and sends an MCPTT emergency group call request towards the MCPTT clients as defined in 3GPP TS 23.379 [7]. +6. The MCPTT client responds with MCPTT emergency group call response, as defined in 3GPP TS 23.379 [7]. +7. The MCPTT server responds to the IWF emergency group call request(s), received in step 4, with IWF emergency group call response(s). +8. The IWF sends an IWF emergency group call response to the MCPTT server, as a response to the request received in step 3, to inform of the successful MCPTT emergency group call establishment. +9. The MCPTT server sends MCPTT emergency group call response to the initiating user in MCPTT client 1. + +NOTE 5: Step 8 can occur at any time following step 3, but at the latest following step 7. + +10. The LMR users (via the IWF) and the affiliated MCPTT clients have successfully established media plane for communication. The LMR system where the interworking group is defined is the controlling system of the group call. + +### 10.6.2.3 In-progress emergency group state cancel of an interworking group + +#### 10.6.2.3.1 LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system + +Figure 10.6.2.3.1-1 shows the procedure for an in-progress emergency group state cancel initiated by an LMR user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The information flows between MCPTT client and MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 3: The end of an MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +1. The MCPTT group is in an in-progress emergency group state. +2. The MCPTT group is an interworking group defined in the MCPTT system. +3. The MCPTT client is affiliated to the MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +6. An LMR user initiates in-progress emergency group state cancel of an interworking group. + +![Sequence diagram showing the procedure for an LMR user initiated in-progress emergency group state cancel of an interworking group. The diagram involves three participants: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF sends an in-progress emergency group state cancel request to the MCPTT server. 2. The MCPTT server checks authorization. 3. The MCPTT server cancels the in-progress emergency state of the group. 4. The MCPTT server performs bearer priority configuration. 5. The MCPTT server informs the affiliated MCPTT clients. 6. The MCPTT server sends an in-progress emergency group state cancel response back to the IWF.](66b2567aa84dd1d036931b056352e11e_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client + Note right of MCPTT server: 2. Check authorization + Note right of MCPTT server: 3. Cancel the in-progress emergency state of the group + Note right of MCPTT server: 4. Bearer priority configuration + Note right of MCPTT server: 5. Inform the affiliated MCPTT clients + IWF->>MCPTT server: 1. IWF in-progress emergency group state cancel request + MCPTT server-->>IWF: 6. IWF in-progress emergency group state cancel response + +``` + +Sequence diagram showing the procedure for an LMR user initiated in-progress emergency group state cancel of an interworking group. The diagram involves three participants: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF sends an in-progress emergency group state cancel request to the MCPTT server. 2. The MCPTT server checks authorization. 3. The MCPTT server cancels the in-progress emergency state of the group. 4. The MCPTT server performs bearer priority configuration. 5. The MCPTT server informs the affiliated MCPTT clients. 6. The MCPTT server sends an in-progress emergency group state cancel response back to the IWF. + +**Figure 10.6.2.3.1-1: LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF in-progress emergency group state cancel request to the MCPTT server. The IWF in-progress emergency group state cancel request may carry an indication that the emergency alert of the user is also being cancelled. + +2. The MCPTT server checks that the initiator of the request is authorized to cancel the in-progress emergency group state of the group. +3. The MCPTT server cancels the in-progress emergency group state of the MCPTT group. If the emergency alert of the user is also requested to be cancelled, the MCPTT server cancels the emergency alert of the user. +4. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +5. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +6. The MCPTT server sends an IWF in-progress emergency group state cancel response to the IWF to confirm the IWF in-progress emergency group state cancel request. + +NOTE 4: Step 6 can occur at any time following step 3. + +#### 10.6.2.3.2 MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system + +Figure 10.6.2.3.2-1 shows the procedure for an in-progress emergency group state cancel initiated by an MCPTT user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The information flows between an MCPTT client and an MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 3: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +1. MCPTT group is in an in-progress emergency group state. +2. The MCPTT group is an interworking group defined in the MCPTT system. +3. MCPTT client 2 is affiliated to that MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +![Sequence diagram for MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. Steps include: 1. Initiate in-progress emergency group state cancel; 2. MCPTT in-progress emergency group state cancel request; 3. Check authorization; 4. Cancel the in-progress emergency state of the group; 5. Bearer priority configuration; 6. IWF in-progress emergency group state cancel request; 7. IWF in-progress emergency group state cancel response; 8. Inform the affiliated MCPTT clients; 9. MCPTT in-progress emergency group state cancel response.](387a316ca4f909a5260b0c5e232d5cc8_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 1. Initiate in-progress emergency group state cancel + MCPTT Client 1->>MCPTT server: 2. MCPTT in-progress emergency group state cancel request + Note right of MCPTT server: 3. Check authorization + Note right of MCPTT server: 4. Cancel the in-progress emergency state of the group + Note right of MCPTT server: 5. Bearer priority configuration + MCPTT server->>IWF: 6. IWF in-progress emergency group state cancel request + IWF-->>MCPTT server: 7. IWF in-progress emergency group state cancel response + Note right of MCPTT server: 8. Inform the affiliated MCPTT clients + MCPTT server-->>MCPTT Client 1: 9. MCPTT in-progress emergency group state cancel response + +``` + +Sequence diagram for MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. Steps include: 1. Initiate in-progress emergency group state cancel; 2. MCPTT in-progress emergency group state cancel request; 3. Check authorization; 4. Cancel the in-progress emergency state of the group; 5. Bearer priority configuration; 6. IWF in-progress emergency group state cancel request; 7. IWF in-progress emergency group state cancel response; 8. Inform the affiliated MCPTT clients; 9. MCPTT in-progress emergency group state cancel response. + +**Figure 10.6.2.3.2-1: MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system** + +1. The MC user of MCPTT client 1 initiates in-progress emergency group state cancel of an interworking group. +2. The MCPTT client sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. The request may carry an indication that the emergency alert of the user is also being cancelled. +3. The MCPTT server checks that the initiator of the request is authorised to cancel the in-progress emergency group state of the group. +4. The MCPTT server cancels the in-progress emergency group state of the MCPTT group. If the emergency alert of the user is also requested to be cancelled, the MCPTT server cancels the emergency alert of the user. +5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +6. The MCPTT server sends the IWF in-progress emergency group state cancel request to the IWF. + +NOTE 4: IWF actions for cancelling in-progress emergency group state are out of scope of the present document. + +7. The IWF sends the IWF in-progress emergency group state cancel response to the MCPTT server to confirm the IWF in-progress emergency group state cancel request. +8. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +9. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress emergency group state cancel request. + +NOTE 5: Step 9 can occur at any time following step 4, depending on the conditions to proceed with the call. + +### 10.6.2.3.3 LMR user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system + +Figure 10.6.2.3.3-1 shows the procedure for an in-progress emergency group state cancel initiated by an LMR user. + +NOTE 1: The information flows between MCPTT client and MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 2: The end of an MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +1. MCPTT group is in an in-progress emergency group state. +2. The MCPTT group is an interworking group defined in the LMR system. +3. The MCPTT client is affiliated to the MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +6. An LMR user initiates in-progress emergency group state cancel of an interworking group. + +![Sequence diagram showing the LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram involves three participants: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF in-progress emergency group state cancel request from IWF to MCPTT server; 2. Bearer priority configuration from MCPTT server to MCPTT client; 3. Inform the affiliated MCPTT clients from MCPTT server to MCPTT client; 4. IWF in-progress emergency group state cancel response from MCPTT server to IWF.](c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_server: 2. Bearer priority configuration + Note right of MCPTT_server: 3. Inform the affiliated MCPTT clients + IWF->>MCPTT_server: 1. IWF in-progress emergency group state cancel request + MCPTT_server-->>MCPTT_client: 2. Bearer priority configuration + MCPTT_server-->>MCPTT_client: 3. Inform the affiliated MCPTT clients + MCPTT_server-->>IWF: 4. IWF in-progress emergency group state cancel response + +``` + +Sequence diagram showing the LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram involves three participants: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF in-progress emergency group state cancel request from IWF to MCPTT server; 2. Bearer priority configuration from MCPTT server to MCPTT client; 3. Inform the affiliated MCPTT clients from MCPTT server to MCPTT client; 4. IWF in-progress emergency group state cancel response from MCPTT server to IWF. + +**Figure 10.6.2.3.3-1: LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system** + +1. The IWF sends an IWF in-progress emergency group state cancel request to the MCPTT server. +2. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +3. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +4. The MCPTT server sends an IWF in-progress emergency group state cancel response to the IWF to confirm the IWF in-progress emergency group state cancel request. + +NOTE 3: Step 4 can occur at any time following step 1, depending on the conditions to proceed with the call. + +#### 10.6.2.3.4 MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system + +Figure 10.6.2.3.4-1 shows the procedure for an in-progress emergency group state cancel initiated by an MCPTT user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + +NOTE 1: The information flows between an MCPTT client and an MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 2: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +1. MCPTT group is in an in-progress emergency group state. + +2. The MCPTT group is an interworking group defined in the LMR system. +3. MCPTT client 2 is affiliated to that MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +![Sequence diagram illustrating the MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 1. Initiate in-progress emergency group state cancel + MCPTT Client 1->>MCPTT server: 2. MCPTT in-progress emergency group state cancel request + MCPTT server->>IWF: 3. IWF in-progress emergency group state cancel request + IWF-->>MCPTT server: 4. IWF in-progress emergency group state cancel response + Note right of MCPTT server: 5. Bearer priority configuration + Note right of MCPTT server: 6. Inform the affiliated MCPTT clients + MCPTT server-->>MCPTT Client 1: 7. MCPTT in-progress emergency group state cancel response + +``` + +Sequence diagram illustrating the MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. + +**Figure 10.6.2.3.4-1: MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system** + +1. The MC user of MCPTT client 1 initiates in-progress emergency group state cancel of an interworking group. +2. An MCPTT client sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. The request may carry an indication that the emergency alert of the user is also being cancelled. +3. The MCPTT server sends the IWF in-progress emergency group state cancel request to the IWF. + +NOTE 3: IWF actions for checking authorization and cancelling in-progress emergency group state are out of scope of the present document. + +NOTE 4: The LMR system can also reject the request. + +4. The IWF sends the IWF in-progress emergency group state cancel response to the MCPTT server to confirm the IWF in-progress emergency group state cancel request. +5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +6. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +7. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress emergency group state cancel request. + +NOTE 5: Step 7 can occur at any time following step 4, depending on the conditions to proceed with the call. + +#### 10.6.2.4 Losing audio + +For LMR systems where a user cannot be pre-empted, the IWF identifies the audio as losing audio to the system. Subclause 10.5 is applicable to losing audio during emergency calls as well as non-emergency calls. + +#### 10.6.2.5 Default emergency group + +In MCPTT, the user's profile determines whether an emergency is raised on the user's currently selected group or on a configured default emergency group. It's up to the IWF and the LMR system to which it is connected to determine what group the emergency is raised on and whether an alert is also sent when the emergency is raised. From the perspective of the MCPTT system, all emergency behavior by the IWF on behalf of its users mapped to MCPTT shall comply with behaviors defined in 3GPP TS 23.379 [7]. The implementation shall ensure that emergency related parameters of a group or private call are adhered to. For example, an MC service group must be configured in the MC service group management system for emergency alerts in order for an emergency alert to be sent on it. This can be enforced through proper configuration of both LMR and MCPTT systems or can be enforced at run time by the IWF. + +#### 10.6.2.6 Emergency private call + +An emergency private call to an LMR user will have emergency priority for the portion of the call transported in the MCPTT system and the LTE EPS but will not receive priority on the LMR system in LMR systems that do not support emergency treatment for private calls. + +#### 10.6.2.7 LMR systems that do not track group emergencies + +The MCPTT system tracks the emergency state of every group. In interworked LMR systems that do not track the emergency state of groups, only a UE in emergency state will be given emergency priority on the LMR system when talking. For any user talking on an emergency group, the portion of the call transported by the MCPTT system will receive emergency priority. + +### 10.6.3 Imminent peril calls + +#### 10.6.3.1 General + +This subclause addresses various aspects of imminent peril call interworking. + +LMR systems do not support imminent peril. Imminent peril calls can be propagated into the LMR system by the IWF as normal group calls or emergency group calls. The decision of the LMR group call type is outside the scope of the present document. + +Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF imminent peril group call request / IWF imminent peril cancel request message is sent to the IWF at the commencement / cancel of an imminent peril group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF imminent peril group call request / IWF imminent peril cancel request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document. + +Where the group is defined in the LMR system, the IWF shall send individual IWF imminent peril group call request / IWF imminent peril cancel request messages to the MCPTT server for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. + +#### 10.6.3.2 Imminent peril group call initiated by an MCPTT user on an interworking group + +Figure 10.6.3.2-1 shows the procedure for an imminent peril group call initiated by a user in the MCPTT system. The figure is based upon the figure for imminent peril group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.2.1. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The imminent peril interworking group call procedures reuse the information flows defined in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated in the provisioning to be used for imminent peril communications +2. The MCPTT group is an interworking group defined in the MCPTT system. +3. MCPTT client 2 is affiliated to the MCPTT group. +4. The IWF is connected to, and is authorized to, interwork with the MCPTT system. +5. At least one LMR user has affiliated to the MCPTT group. +6. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 3: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.6.3.2-1: Imminent peril group call initiated by a MCPTT user to an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF.](93699fb71e95b4df5a3871fdcf818982_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + + Note left of MCPTT client 1: 1. Initiate imminent peril group call + MCPTT client 1->>MCPTT server: 2. MCPTT imminent peril group call request + Note right of MCPTT server: 3. Affiliate the user + Note right of MCPTT server: 4. Check authorization and affiliated group members + Note right of MCPTT server: 5. Bearer priority configuration + Note right of MCPTT server: 6. Record the imminent peril state of the group + MCPTT server->>IWF: 7. IWF imminent peril group call request + IWF-->>MCPTT server: 8. IWF imminent peril group call response + Note right of MCPTT server: 9. Call the affiliated MCPTT clients + MCPTT server-->>MCPTT client 1: 10. MCPTT imminent peril group call response + Note bottom: 11. Media plane is established + +``` + +Sequence diagram for Figure 10.6.3.2-1: Imminent peril group call initiated by a MCPTT user to an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. + +**Figure 10.6.3.2-1: Imminent peril group call initiated by a MCPTT user to an interworking group defined in the MCPTT system** + +1. An MCPTT user initiates an imminent peril group call. +2. The MCPTT client sends an MCPTT imminent peril group call request to the MCPTT server. The request contains an indication of the in-progress imminent peril. The request may also contain an indication of an implicit floor request and may also contain the location of the calling party. + +3. The MCPTT server implicitly affiliates MCPTT client 1 to the imminent peril group if the client is not already affiliated. +4. The MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of imminent peril group calls on the indicated interworking group defined in the MCPTT system. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. The MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. +5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. + +NOTE 4: Successive calls during the in-progress imminent peril state will all receive the adjusted bearer priority. + +6. The MCPTT server records the imminent peril state of the group. The MCPTT server also records the identity of the MCPTT user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCPTT group is considered to be in an in-progress imminent peril state until that state is cancelled. +7. The MCPTT server sends the IWF imminent peril group call request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF imminent peril group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF imminent peril group call request is sent to the IWF for each affiliated LMR user. +8. The IWF responds with the IWF imminent peril group call response(s) to MCPTT server to inform of the successful MCPTT imminent peril call establishment. + +NOTE 5: The IWF can reject the request if it does not support imminent peril group calls. IWF actions for priority are out of scope of the present document. + +NOTE 6: How the LMR group members are called within the LMR system is out of scope of the present document. + +9. The MCPTT server sends the imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress imminent peril. MCPTT users are notified of the incoming imminent peril call. The MCPTT clients acknowledge the imminent peril call request as specified in 3GPP TS 23.379 [7]. +10. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to inform the successful imminent peril call establishment. + +NOTE 7: Step 10 can occur at any time following step 5, and prior to step 11 depending on the conditions to proceed with the imminent peril call. + +11. The LMR users via the IWF and the affiliated MCPTT clients have successfully established the media plane for communication. The MCPTT system, where the interworking group is defined, is the controlling system of the group call. + +### 10.6.3.3 Group call initiated by a user in the LMR system on an interworking group in imminent peril state + +Figure 10.6.3.3-1 shows the procedure for a group call initiated by an LMR user (represented by the IWF) on an interworking group where the group is currently in imminent peril state within the MCPTT system. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The imminent peril interworking group call procedures reuse the information flows defined in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) affiliated to that MCPTT group. +2. The IWF is connected to, and is authorized to interwork with, the MCPTT system. + +3. The interworking group information is available at the IWF. +4. The interworking group is currently in imminent peril state within the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +6. LMR user initiates a group call. + +NOTE 3: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the group call initiation process. Lifelines: IWF, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence starts with the IWF sending an '1. IWF group call request' to the MCPTT server. The server performs an internal step '2. Determine on-going imminent peril state'. It then sends '3. MCPTT imminent peril group call request' to both clients. Clients respond with '4. MCPTT imminent peril group call response' to the server. The server sends '3a. IWF imminent peril group call request' to the IWF, which in turn sends '4a. IWF imminent peril group call response' back to the server. Finally, the server sends '5. IWF imminent peril group call response' to the IWF. A horizontal bar at the bottom indicates '6. Media plane is established'.](f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note right of MCPTT server: 2. Determine on-going imminent peril state + + IWF->>MCPTT server: 1. IWF group call request + MCPTT server->>MCPTT client 1: 3. MCPTT imminent peril group call request + MCPTT server->>MCPTT client 2: 3. MCPTT imminent peril group call request + MCPTT client 1->>MCPTT server: 4. MCPTT imminent peril group call response + MCPTT client 2->>MCPTT server: 4. MCPTT imminent peril group call response + MCPTT server->>IWF: 3a. IWF imminent peril group call request + IWF->>MCPTT server: 4a. IWF imminent peril group call response + MCPTT server->>IWF: 5. IWF imminent peril group call response + Note bottom: 6. Media plane is established + +``` + +Sequence diagram illustrating the group call initiation process. Lifelines: IWF, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence starts with the IWF sending an '1. IWF group call request' to the MCPTT server. The server performs an internal step '2. Determine on-going imminent peril state'. It then sends '3. MCPTT imminent peril group call request' to both clients. Clients respond with '4. MCPTT imminent peril group call response' to the server. The server sends '3a. IWF imminent peril group call request' to the IWF, which in turn sends '4a. IWF imminent peril group call response' back to the server. Finally, the server sends '5. IWF imminent peril group call response' to the IWF. A horizontal bar at the bottom indicates '6. Media plane is established'. + +**Figure 10.6.3.3-1: Group call initiated by a user in the LMR system on an interworking group in imminent peril state** + +1. The IWF does not track the imminent peril state of the group and sends an IWF group call request including an MCPTT group ID to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included and the location information of the requestor if required. +2. The MCPTT server determines that the MCPTT group is currently in imminent peril state. +3. The MCPTT server converts the request and sends an MCPTT imminent peril group call request to all of the affiliated MCPTT clients. +- 3a. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF imminent peril group call request is sent to the IWF for each affiliated LMR user. +4. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the MCPTT imminent peril group call request. For a multicast call, these acknowledgements are not sent. +- 4a. The IWF returns IWF imminent peril group call response(s) to the MCPTT server. +5. The MCPTT server sends the IWF imminent peril group call response message to the IWF. +6. The LMR users (via the IWF) and the affiliated MCPTT clients have successfully established the media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call. + +The IWF, MCPTT client 1, and MCPTT client 2 continue with the MCPTT group call, which receives adjusted bearer priority within the MCPTT system due to the MCPTT group being in imminent peril state. + +NOTE 4: IWF actions for priority are out of scope of the present document. + +#### 10.6.3.4 In-progress imminent peril state cancel on an interworking group + +This procedure describes the case where an authorized MCPTT user cancels an interworking group's in-progress imminent peril state. + +Figure 10.6.3.4-1 shows the procedures for the MCPTT client cancelling an interworking group's in-progress imminent peril state. + +NOTE 1: The end of an imminent peril call does not cancel the MCPTT group's in-progress imminent peril state. It is explicitly cancelled by an authorized user. + +NOTE 2: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 3: The in-progress imminent peril interworking group state cancel procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) affiliated to that MCPTT group. + 2. The IWF is connected to, and is authorized to interwork with, the MCPTT system. + 3. The interworking group information is available at the IWF. + 4. The interworking group is currently in in-progress imminent peril state within the MCPTT system and has prioritized bearer support. + 5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +- NOTE 4: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. +6. MCPTT client 1 previously initiated the imminent peril group call. + +![Sequence diagram for In-progress imminent peril group state cancel on an interworking group. Lifelines: MCP TT client 1, MCP TT client 2, MCP TT server, IWF. The sequence shows the cancellation of an imminent peril group state, involving authorization checks, bearer priority adjustment, and notifications to group members.](4c63a0e17b54c7e61d512c276932114c_img.jpg) + +``` + +sequenceDiagram + participant MCP TT client 1 + participant MCP TT client 2 + participant MCP TT server + participant IWF + + Note left of MCP TT client 1: 1. Initiate in-progress imminent peril group state cancel + MCP TT client 1->>MCP TT server: 2. MCP TT in-progress imminent peril group state cancel request + Note right of MCP TT server: 3. Check authorization + Note right of MCP TT server: 4. Cancel the in-progress imminent peril state of the group + Note right of MCP TT server: 5. Bearer priority adjustment + MCP TT server->>IWF: 6. IWF in-progress imminent peril group state cancel request + IWF-->>MCP TT server: 7. IWF in-progress imminent peril group state cancel response + MCP TT server->>MCP TT client 2: 8. MCP TT in-progress imminent peril group state cancel request + Note right of MCP TT client 2: 9. Notify Imminent peril cancel + MCP TT client 2->>MCP TT server: 10. MCP TT in-progress imminent peril group state cancel response + MCP TT server->>MCP TT client 1: 11. MCP TT in-progress imminent peril group state cancel response + +``` + +Sequence diagram for In-progress imminent peril group state cancel on an interworking group. Lifelines: MCP TT client 1, MCP TT client 2, MCP TT server, IWF. The sequence shows the cancellation of an imminent peril group state, involving authorization checks, bearer priority adjustment, and notifications to group members. + +**Figure 10.6.3.4-1: In-progress imminent peril group state cancel on an interworking group** + +1. The user at the MCP TT client 1 initiates an in-progress imminent peril state cancel. +2. MCP TT client 1 sends an MCP TT in-progress imminent peril group state cancel request to the MCP TT server. +3. The MCP TT server checks whether the MCP TT user 1 at MCP TT client 1 is authorized to cancel the in-progress imminent peril group state. +4. The MCP TT server cancels/resets the in-progress imminent peril group state. +5. The MCP TT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +6. The MCP TT server sends an IWF in-progress imminent peril group state cancel request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF in-progress imminent peril group state cancel request is sent to the IWF. If the MCP TT server has received individual affiliations from the group's LMR users, an individual IWF in-progress imminent peril group state cancel request is sent (to the IWF) for each affiliated LMR user. +7. The IWF sends the IWF in-progress imminent peril group state cancel response(s) to the MCP TT server. + +NOTE 5: The IWF responds even if it does not support imminent peril group calls. IWF actions for priority are out of scope of the present document. + +8. The MCP TT server sends an MCP TT in-progress imminent peril group state cancel request to the MCP TT group members. + +NOTE 6: Steps 6 and 8 can occur in any order following step 5. + +9. MCP TT group members are notified of the in-progress imminent peril group state cancel. +10. MCP TT client 2 sends the MCP TT in-progress imminent peril group state cancel response to the MCP TT server to acknowledge the in-progress MCP TT in-progress imminent peril group state cancel request. For a multicast scenario, this acknowledgement is not sent. + +11. The MCPTT server sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress imminent peril group state cancel request. + +NOTE 7: Step 11 can occur at any time following step 5. + +## 10.6.4 Emergency alerts + +### 10.6.4.1 Emergency alert initiated by LMR user + +In this procedure, an LMR user is initiating an emergency alert via the IWF. Figure 10.6.4.1-1 shows the procedure for an emergency alert initiated by a user in the LMR system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.1. + +Pre-conditions: + +1. The MC service group is previously defined on the group management server with MC service client 1 and MC service client 2 affiliated to that MC service group. +2. The IWF is connected to and is authorized to interwork with the MC system. +3. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or MC the system). +4. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. +5. The IWF may or may not have carried out an explicit affiliation procedure with the MC service group. +6. An emergency alert is requested on the LMR system. + +NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs identity conversion and protocol translation. + +![Sequence diagram showing the MC service emergency alert initiated by LMR user. Lifelines: IWF, MC service server, MC service client 1, MC service client 2. The process involves an emergency alert initiation from the IWF, authorization checks, notification of clients, and a final affiliation step.](c3d58ba0812530ed8c8a9c9f68c209b1_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCSS as MC service server + participant MCSC1 as MC service client 1 + participant MCSC2 as MC service client 2 + + Note left of IWF: 1. Initiate emergency alert + IWF->>MCSS: 2. IWF emergency alert request + Note right of MCSS: 3. Check alert authorization + MCSS->>IWF: 4. IWF emergency alert response + MCSS->>MCSC1: 5. MC service emergency alert request + MCSS->>MCSC2: 5. MC service emergency alert request + Note right of MCSC1: 6. Notify emergency + Note right of MCSC2: 6. Notify emergency + MCSC1->>MCSS: 7. MC service emergency alert response + MCSC2->>MCSS: 7. MC service emergency alert response + Note right of MCSS: 8. Affiliate to group + +``` + +Sequence diagram showing the MC service emergency alert initiated by LMR user. Lifelines: IWF, MC service server, MC service client 1, MC service client 2. The process involves an emergency alert initiation from the IWF, authorization checks, notification of clients, and a final affiliation step. + +Figure 10.6.4.1-1 MC service emergency alert initiated by LMR user + +1. The LMR user initiates an emergency alert. + +NOTE 2: How the IWF determines the emergency condition from the LMR system is out of scope of the present document. + +2. The IWF sends an IWF emergency alert request to the designated MC service server. If the location of the LMR user is not available to the IWF, the IWF emergency alert request shall contain an indication that location is not available. +3. MC service server checks whether the MC service user ID that represents the LMR user is authorized for initiation of MC service emergency alerts for the indicated MC service group. The MC service server determines the affiliation status of the group members. +4. The MC service server sends an IWF emergency alert response to the IWF to confirm the IWF emergency alert request. + +NOTE 3: Sending the IWF emergency alert request without making a request to also start an emergency call does not put the group into an ongoing emergency condition. + +5. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name. +6. MC service users are notified of the MC service emergency. +7. The receiving MC service clients send an MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert request. +8. If the group is an interworking group defined in the MC system, the MC service server implicitly affiliates the individual MC service ID of the LMR user to the emergency group if not already affiliated. If the IWF is configured to affiliate on behalf of all of its group members in a single affiliation step, the MC service server affiliates the IWF ID instead of an individual MC service ID. + +NOTE 4: Step 8 can be performed any time after step 3 but at the latest immediately after step 7. + +NOTE 5: MC service group calls made to this MC service group will be established as emergency calls if this MC service group has an ongoing emergency condition. + +NOTE 6: Sending the emergency alert does not put the other UEs in the group into an emergency state. + +#### 10.6.4.2 Emergency alert initiated by MC service user + +In this procedure, an MC service user is initiating an emergency alert that is delivered to the LMR system via the IWF. Figure 10.6.4.2-1 shows the procedure for an emergency alert initiated by a user in the MC system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.1. + +Pre-conditions: + +1. The MC service group is previously defined on the group management server with MC service client 1 and MC service client 2 affiliated to that MC service group. +2. The IWF is connected to and is authorized to interwork with the MC system. +3. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system). +4. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs identity conversion and protocol translation. + +![Sequence diagram for MC service emergency alert initiated by MC service user. Lifelines: MC service client 1, MC service client 2, MC service server, IWF. Steps: 1. Initiate emergency alert (client 1); 2. MC service emergency alert request (client 1 to server); 3. Check alert authorization (server); 4. MC service emergency alert response (server to client 1); 5. IWF emergency alert request (server to IWF); 6. IWF emergency alert response (IWF to server); 7. MC service emergency alert request (server to client 2); 8. Notify emergency (client 2); 9. MC service emergency alert response (client 2 to server); 10. Affiliate to group (server).](dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service client 2 + participant MC service server + participant IWF + Note left of MC service client 1: 1. Initiate emergency alert + MC service client 1->>MC service server: 2. MC service emergency alert request + Note right of MC service server: 3. Check alert authorization + MC service server-->>MC service client 1: 4. MC service emergency alert response + MC service server->>IWF: 5. IWF emergency alert request + IWF-->>MC service server: 6. IWF emergency alert response + MC service server->>MC service client 2: 7. MC service emergency alert request + Note right of MC service client 2: 8. Notify emergency + MC service client 2-->>MC service server: 9. MC service emergency alert response + Note right of MC service server: 10. Affiliate to group + +``` + +Sequence diagram for MC service emergency alert initiated by MC service user. Lifelines: MC service client 1, MC service client 2, MC service server, IWF. Steps: 1. Initiate emergency alert (client 1); 2. MC service emergency alert request (client 1 to server); 3. Check alert authorization (server); 4. MC service emergency alert response (server to client 1); 5. IWF emergency alert request (server to IWF); 6. IWF emergency alert response (IWF to server); 7. MC service emergency alert request (server to client 2); 8. Notify emergency (client 2); 9. MC service emergency alert response (client 2 to server); 10. Affiliate to group (server). + +**Figure 10.6.4.2-1 MC service emergency alert initiated by MC service user** + +1. The MC service user 1 initiates an emergency alert. +2. MC service client 1 sends an MC service emergency alert request to the MC service server. +3. The MC service server resolves the group ID, determines the affiliation status of the group members and checks whether the IWF should be informed. In this scenario, the group has affiliated members that are homed on the IWF, thus the IWF shall be involved. MC service server also checks whether the MC service user ID is authorized to initiate MC service emergency alerts for the indicated MC service group. +4. The MC service server sends an MC service emergency alert response to the MC service client 1 to confirm the MC service emergency alert request. + +NOTE 2: Sending the emergency alert without making a request to also start an emergency call does not put the group into an ongoing emergency condition. + +5. MC service server sends an IWF emergency alert request to the IWF. If the location of the MC service client 1 is not available, the IWF emergency alert request shall contain an indication that location is not available. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency alert request is sent to the IWF. If the IWF has sent individual affiliations for each of its LMR users, the MC service server sends an IWF emergency alert request via the IWF to each affiliated LMR group member. +6. The IWF sends an IWF service emergency alert response to the MC service server to confirm the IWF emergency alert request(s). +7. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name. +8. MC service users are notified of the MC service emergency. +9. The receiving MC service clients send an MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert. + +10. The MC service server implicitly affiliates the MC service client 1 to the emergency group if it is not already affiliated. + +NOTE 3: Step 10 can be performed any time after step 3. Steps 5 and 7 can be performed in which ever order. + +NOTE 4: MC service group calls made to this MC service group will be established as emergency calls if the MC service group has an ongoing emergency condition. + +NOTE 5: Sending an emergency alert does not put the other UEs in the group into an emergency state. + +## 10.6.5 Emergency alert cancellation + +### 10.6.5.1 Emergency alert cancellation of an LMR user + +In this procedure, an LMR user is cancelling the emergency alert. Figure 10.6.5.1-1 shows the procedure for emergency alert cancellation of a user in the LMR system. This subclause is based upon subclause for MCPTT emergency alert cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.2. + +Pre-conditions: + +1. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system). +2. The LMR user had previously successfully initiated an emergency alert via the IWF. +3. The MC service client 1 and MC service client 2 are affiliated to the MC service group. +4. The MC service server may have carried out an explicit or implicit affiliation procedure of the LMR user to the MC service group. +5. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. +6. The LMR user initiates an emergency alert cancel. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for MC service emergency alert cancellation of an LMR user](c96780e69fd790e1e62e1c3e5431636a_img.jpg) + +``` +sequenceDiagram + participant IWF + participant MCSS as MC service server + participant MCC1 as MC service client 1 + participant MCC2 as MC service client 2 + + Note right of MCC1: 4. Notify emergency alert cancel + Note right of MCC2: 4. Notify emergency alert cancel + + IWF->>MCSS: 1. IWF emergency alert cancel request + MCSS-->>IWF: 2. IWF emergency alert cancel response + MCSS->>MCC1: 3. MC service emergency alert cancel request + MCSS->>MCC2: 3. MC service emergency alert cancel request + MCC1-->>MCSS: 5. MC service emergency alert cancel response + MCC2-->>MCSS: 5. MC service emergency alert cancel response +``` + +The sequence diagram illustrates the interaction for emergency alert cancellation. It starts with the IWF sending a request to the MC service server. The server responds, then sends a request to both MC service client 1 and 2. Simultaneously, both clients send their own 'Notify emergency alert cancel' messages (shown in boxes). Finally, both clients send their responses back to the MC service server, which in turn sends a response back to the IWF. + +Sequence diagram for MC service emergency alert cancellation of an LMR user + +Figure 10.6.5.1-1 MC service emergency alert cancellation of an LMR user + +1. The IWF sends an IWF emergency alert cancel request to the MC service group to which the IWF had previously successfully sent the IWF emergency alert request on behalf of the LMR user. + +NOTE 2: The IWF emergency alert cancel request may carry an indication to also request that the in-progress emergency state on the group is to be cancelled. + +2. The MC service server sends the IWF emergency alert cancel response to the IWF to confirm the IWF emergency alert cancellation. +3. The MC service server sends an MC service emergency alert cancel request to the MC service clients of the affiliated MC service group members. +4. MC service users are notified of the MC service emergency alert cancellation of the LMR user. +5. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel request. For a multicast call scenario, these acknowledgements are not sent. + +NOTE 3: Steps 2 and 3 can be performed in which ever order. + +### 10.6.5.2 Emergency alert cancellation of an MC service user + +In this procedure, an MC service user is cancelling the emergency alert. Figure 10.6.5.2-1 shows the procedure for emergency alert cancellation from a user in the MC system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.2. + +Pre-conditions: + +1. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system). +2. The MC service client 1 had previously successfully initiated an MC service emergency alert request. +3. The MC service client 1 is still in the emergency state. +4. The MC service client 2 is affiliated to the MC service group. +5. The MC service server may have carried out an explicit or implicit affiliation procedure of the LMR user with the MC service group. +6. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the MC service emergency alert cancellation of an MC service user. The diagram shows interactions between MC service client 1, MC service client 2, MC service server, and IWF. The process starts with client 1 initiating an emergency alert cancel, followed by a request to the server, a response to client 1, a request to the IWF, a response from the IWF, a request to client 2, a notification to client 2, and finally a response from client 2 to the server.](ecae674475cecdd0962200a5d1e2591e_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service client 2 + participant MC service server + participant IWF + Note left of MC service client 1: 1. Initiate emergency alert cancel + MC service client 1->>MC service server: 2. MC service emergency alert cancel request + MC service server-->>MC service client 1: 3. MC service emergency alert cancel response + MC service server->>IWF: 4. IWF emergency alert cancel request + IWF-->>MC service server: 5. IWF emergency alert cancel response + MC service server->>MC service client 2: 6. MC service emergency alert cancel request + Note right of MC service client 2: 7. Notify emergency alert cancel + MC service client 2-->>MC service server: 8. MC service emergency alert cancel response + +``` + +Sequence diagram illustrating the MC service emergency alert cancellation of an MC service user. The diagram shows interactions between MC service client 1, MC service client 2, MC service server, and IWF. The process starts with client 1 initiating an emergency alert cancel, followed by a request to the server, a response to client 1, a request to the IWF, a response from the IWF, a request to client 2, a notification to client 2, and finally a response from client 2 to the server. + +**Figure 10.6.5.2-1 MC service emergency alert cancellation of an MC service user** + +1. The user at the MC service client 1 initiates an emergency alert cancel. + +NOTE 2: The MC service emergency alert cancel request may carry an indication that the in-progress emergency state on the group is to be cancelled. + +2. MC service client 1 requests the MC service server to send an MC service emergency alert cancel to the MC service group to which MC service client 1 had previously sent the emergency alert request. The MC service server resolves the group ID, determines the affiliation status of the group members and checks whether the IWF should be informed. In this scenario, the group has affiliated members that are homed on the IWF, thus the IWF shall be involved. +3. The MC service server sends the MC service emergency alert cancel response to the MC service client 1 to confirm the MC service emergency alert cancel request. MC service client 1 resets its emergency state. +4. The MC service server sends an IWF emergency alert cancel request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency alert cancel request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF emergency alert cancel request message is sent to the IWF for each affiliated LMR user. +5. The IWF sends an IWF emergency alert cancel response(s) to the MC service server to acknowledge the IWF emergency alert cancel request(s). +6. The MC service server sends an MC service emergency alert cancel request towards the MC service clients of the affiliated MC service group members. +7. MC service users are notified of the MC service emergency alert cancellation of MC service client 1. +8. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel request. For a multicast call scenario, these acknowledgements are not sent. + +NOTE 3: Steps 3 and 4 can be performed in which ever order. + +## 10.7 Codec + +### 10.7.1 Information flows for codec + +#### 10.7.1.1 IWF codec reconciliation request + +Table 10.7.1.1-1 describes the information flow IWF codec reconciliation request from the IWF to the MCPTT server. + +**Table 10.7.1.1-1: IWF codec reconciliation request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| MCPTT group ID | M | The MCPTT group ID for which a codec change is requested. | +| Codec type | M | Type of the requested codec | + +#### 10.7.1.2 IWF codec reconciliation response + +Table 10.7.1.2-1 describes the information flow IWF codec reconciliation response from the MCPTT server to the IWF. + +**Table 10.7.1.2-1: IWF codec reconciliation response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------| +| MCPTT group ID | M | The MCPTT group ID for which a codec change was requested. | +| Result | M | Result indicates success or failure of the requested codec change. | + +### 10.7.2 IWF transcoding + +The IWF can be used to transcode voice packets in transit between the LMR and MCPTT systems. In this scenario, the MCPTT system can operate its own vocoder type and the LMR system can operate its own vocoder type. The type of vocoder used on the LMR side is outside the scope of the present document. + +When operating in this mode, the IWF converts voice media formats between the two sides. Vocoder negotiation is according to procedures in the present document. + +### 10.7.3 Codec negotiation by the LMR system + +#### 10.7.3.1 Description + +An MCPTT group may be configured to use an LMR speech codec, such that speech can be carried end to end between all group members in both LMR and MCPTT system without transcoding. + +An LMR system can support more than one speech codec; for example P25 supports both a full rate and a half rate speech codec. Circumstances within the LMR system might require that the codec in use within a group is changed according to the needs of the LMR system. + +Figure 10.7.3.1-1 below illustrates a procedure which allows the LMR system to change the speech codec within an MCPTT group that is connected to the LMR system via the IWF. + +Pre-conditions: + +1. Group members have affiliated to the MCPTT group in both the LMR system and in the MCPTT system +2. A permitted LMR codec has been negotiated for use by MCPTT group members +3. MCPTT group members support the requested second LMR speech codec + +NOTE 1: The exception condition created if the IWF does not support transcoding and the MCPTT client does not support the requested LMR codec is outside the scope of the present document. + +4. The LMR system requires a change to an alternative speech codec. + +![Sequence diagram illustrating the Codec reconciliation procedure. The diagram shows three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. IWF sends a '1. IWF codec reconciliation request' to the MCPTT server. 2. The MCPTT server performs an '2. Authorization check'. 3. The MCPTT server sends a '3. Codec reconciliation request' to the MCPTT client. 4. The MCPTT client sends a '4. Codec reconciliation response' back to the MCPTT server. 5. The MCPTT server sends a '5. IWF codec reconciliation response' to the IWF. 6. A final step, '6. Use new codec for group communication', is shown in a box spanning all three participants.](ceb6fe29e2d57711907569c31182b3c2_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT server: 2. Authorization check + IWF->>MCPTT server: 1. IWF codec reconciliation request + MCPTT server->>MCPTT client: 3. Codec reconciliation request + MCPTT client->>MCPTT server: 4. Codec reconciliation response + MCPTT server->>IWF: 5. IWF codec reconciliation response + Note over MCPTT client, MCPTT server, IWF: 6. Use new codec for group communication + +``` + +Sequence diagram illustrating the Codec reconciliation procedure. The diagram shows three participants: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. IWF sends a '1. IWF codec reconciliation request' to the MCPTT server. 2. The MCPTT server performs an '2. Authorization check'. 3. The MCPTT server sends a '3. Codec reconciliation request' to the MCPTT client. 4. The MCPTT client sends a '4. Codec reconciliation response' back to the MCPTT server. 5. The MCPTT server sends a '5. IWF codec reconciliation response' to the IWF. 6. A final step, '6. Use new codec for group communication', is shown in a box spanning all three participants. + +**Figure 10.7.3.1-1: Codec reconciliation procedure** + +1. The IWF sends a codec reconciliation request to the MCPTT server on behalf of the LMR system. +2. The MCPTT server checks that the requested codec is permitted for the MCPTT group. +3. The MCPTT server sends a codec reconciliation request to all of the affiliated MCPTT client(s) to negotiate the use of the speech codec requested by the LMR system. +4. The MCPTT client replies with a codec reconciliation response to the MCPTT server, indicating acceptance of the new speech codec. +5. The MCPTT server sends a codec reconciliation response to the IWF. +6. Further transmissions in the MCPTT group use the new codec in the media plane. + +NOTE 2: The time at which the new codec is first used by a transmitting party is outside the scope of the present document. + +## 10.8 MCData short data service + +### 10.8.1 General + +The present document specifies short data service (SDS) interworking between LMR users and MCData clients using one-to-one standalone SDS messages and group standalone SDS messages. The IWF behaves as a peer MCData server to other MCData servers. + +When an LMR user attempts to send an LMR message to the MCData service, the IWF converts the LMR message into a request to send an MCData SDS. The method by which the IWF converts the LMR message into a request to send an MCData SDS is outside the scope of the present document. + +When the IWF receives a request to send an MCData SDS to an LMR user or a group of LMR users, the IWF converts the request into one or more LMR messages. The method by which the IWF converts the MCData SDS request into an LMR messages is outside the scope of the present document. + +## 10.8.2 Information flows for the short data service + +### 10.8.2.1 General + +The following subclauses define information flows for MCData SDS on the IWF-2 interface. MCData SDS related information flows on reference points other than IWF-2 are defined in 3GPP TS 23.282 [6], subclause 7.4.2.1. In each case, the LMR users behind the IWF are represented by MCData IDs or a MCData group ID as appropriate and so the MCData server shall be capable of routing messages towards identities located behind the IWF. + +### 10.8.2.2 IWF MCData standalone data request + +Table 10.8.2.2-1 describes the information flow for the MCData standalone data request (in 3GPP TS 23.282 [6] subclauses 7.4.2.2.2 and 7.4.2.3.2) sent from the MCData server to the IWF and from the IWF to a MCData server. + +**Table 10.8.2.2-1: IWF MCData standalone data request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier (see NOTE 1) | M | Identifies the conversation | +| Transaction Identifier (see NOTE 1) | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +### 10.8.2.3 IWF MCData data disposition notification + +Table 10.8.2.3-1 describes the information flow for the MCData data disposition notification sent from the IWF to the MCData server and from the MCData server to the IWF. + +**Table 10.8.2.3-1: IWF MCData data disposition notification** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier (see NOTE) | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered, read, delivered and read, or disposition prevented by system | +| NOTE: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | + +### 10.8.2.4 IWf MCData group standalone data request (IWf – MCData server) + +Table 10.8.2.4-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.5.2) sent from the IWf to the MCData server when the IWf is acting as the initiating MCData client. + +**Table 10.8.2.4-1: IWf MCData group standalone data request (IWf – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier
(see NOTE 1) | M | Identifies the conversation | +| Transaction Identifier
(see NOTE 1) | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier
(see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +### 10.8.2.5 IWf MCData group standalone data request (MCData server - IWf) + +Table 10.8.2.5-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.5.2) sent from the MCData server to the IWf when the IWf is acting as proxy for MCData clients. + +**Table 10.8.2.5-1: IWf MCData group standalone data request (MCData server – IWf)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier
(see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +### 10.8.2.6 IWf MCData data disposition notification(s) (MCData server to IWf) + +Table 10.8.2.6-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the IWf when the IWf is acting as proxy for MCData client(s). + +**Table 10.8.2.6-1: IWF MCData data disposition notification(s) (MCData server – IWF)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered, read, delivered and read, or disposition prevented by system | + +### 10.8.2.7 IWF MCData group standalone data request (IWF – MCData server) + +Table 10.8.2.7-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the IWF representing the MCData client to the MCData server. + +**Table 10.8.2.7-1: IWF MCData group standalone data request (IWF – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier (see NOTE 1) | M | Identifies the conversation | +| Transaction Identifier (see NOTE 1) | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +### 10.8.2.8 IWF MCData group standalone data request (MCData server – IWF) + +Table 10.8.2.8-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the MCData server to the IWF acting as proxy for MCData client(s). + +**Table 10.8.2.8-1: IWF MCData group standalone data request (MCData server – IWF)** + +| Information element | Status | Description | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | + +### 10.8.2.9 IWF MCData group standalone data response + +Table 10.8.2.9-1 describes the information flow for the MCData group standalone data response (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the IWF to the MCData server and from the MCData server to the IWF acting as proxy for other MCData clients. + +**Table 10.8.2.9-1: IWF MCData group standalone data response** + +| Information element | Status | Description | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier (see NOTE) | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| NOTE: | A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | + +## 10.8.3 Behaviour at the MCData Client + +The MCData client interfaces with the MCData server as specified in 3GPP TS 23.282 [6]. + +## 10.8.4 Behaviour at the IWF + +The IWF interfaces with the MCData server via the reference points defined in subclause 7.4 of the present document. + +## 10.8.5 Behaviour at the MCData server + +The MCData server behaves as specified in 3GPP TS 23.282 [6], with the addition that the MCData server shall route SDS messages addressed to MCData IDs and MCData group IDs that lie behind IWFs to the appropriate IWFs. + +## 10.8.6 MCData user one-to-one SDS request to an LMR user + +### 10.8.6.1 Signalling control plane + +The procedure for an MCData user requesting to send a signalling control plane SDS to a single LMR user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.2 for the one-to-one standalone short data service using the signalling + +control plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +### 10.8.6.2 Media plane + +The procedure for an MCData user requesting to send a media plane SDS to a single LMR user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.3 for the one-to-one standalone short data service using the media plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +## 10.8.7 LMR user one-to-one SDS request to an MCData user + +### 10.8.7.1 Signalling control plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a signalling control plane SDS to a single MCData user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.2 for the one-to-one standalone short data service using the signalling control plane, with the exception that MCData client 1 is located behind the IWF. The source address of the SDS is the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +### 10.8.7.2 Media plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a media plane SDS to a single MCData user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.3 for the one-to-one standalone short data service using the media plane, with the exception that MCData client 1 is located behind the IWF. The source address of the SDS is the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +## 10.8.8 MCData user group SDS request to an MCData group including LMR users + +### 10.8.8.1 Signalling control plane + +The procedure for an MCData user requesting to send a signalling control plane SDS to an MCData group that includes one or more LMR users is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.5 for the group standalone short data service using the signalling control plane. In the case of implementation involving an IWF the difference is that one or more of the MCData clients 2 to n are located behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server. The IWF can also respond on behalf of a MCData client located behind the IWF to a disposition request with a disposition of 'disposition prevented by system' for forwarding to the originating MCData client. + +### 10.8.8.2 Media plane + +The procedure for an MCData user requesting to send a media plane SDS to an MCData group that includes one or more LMR users is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.6 for the group standalone short data service using the media plane. In the case of implementation involving an IWF the difference is that one or more of the MCData clients 2 to n can be located behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server. The IWF can also respond on behalf of a MCData client located behind the IWF to a disposition request with a disposition of 'disposition prevented by system' for forwarding to the originating MCData client. + +## 10.8.9 LMR user group SDS request to an MCData group + +### 10.8.9.1 Signalling control plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a signalling control plane SDS to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.5 for the group standalone short data service using the signalling control plane, with the exception that MCData client 1 is located behind an IWF and one or more of the + +MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server to other MCData servers. + +### 10.8.9.2 Media plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a media plane SDS to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.6 for the group standalone short data service using the media plane, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server to other MCData servers. + +## 10.9 IWF as a security gateway + +### 10.9.1 Support for transcoding with encrypted speech + +In some cases when encryption of voice media is required in the MC system, the MCPTT user(s) and the LMR user(s) can use different codecs. In these cases, transcoding is needed and before transcoding can occur, encryption applied to the voice media by the MC system needs to be removed. After transcoding, LMR encryption can be applied (out-of-scope of the present document). An IWF can perform these functions and be deployed as a security gateway between the MCPTT system and the LMR system. When the IWF removes the encryption applied by the MC system, the IWF must perform key management procedures defined in 3GPP TS 33.180 [8] to obtain the key material for the group. + +## 10.10 Simultaneous interworked calls (on-network) + +### 10.10.1 General + +An IWF representing an LMR user may support simultaneous interworked calls for the same LMR user. The LMR user can become involved in simultaneous interworked calls when the IWF invites, joins or accepts more than one interworked call on behalf of the LMR user, or when the IWF affiliates the LMR user to multiple groups. This subclause is based on the subclause for simultaneous session for MCPTT calls in 3GPP TS 23.379 [7], subclause 10.8. + +NOTE: An LMR user affiliating to multiple interworked groups with active calls via the IWF can result in the LMR user being invited simultaneously to multiple interworked calls. + +How the IWF accomodates simultaneous interworked calls to a single LMR user is outside the scope of the present document. + +## 10.11 Location + +### 10.11.1 Location of current talker + +3GPP TS 23.379 [7], subclause 10.6.2.7 describes a high-level procedure to provide the location of the current talker to all the receiving MCPTT users. + +### 10.11.2 Location of current talker (MCPTT server to IWF) + +Figure 10.11.2-1 shows the high-level procedure to for MCPTT service to provide the location information about the current talking user to all the receiving MCPTT users and the IWF. + +Pre-conditions: + +1. There is on-going group call involving MCPTT client 1 and MCPTT client 2 and the IWF. +2. MCPTT client 1 is the current talking user. +3. MCPTT server has obtained the location information of MCPTT client 1. + +![Sequence diagram showing the interaction between MCPTT Client 1, MCPTT server, MCPTT client 2, and IWF for providing location information. Step 1: MCPTT client 1 acquires the floor for transmission. Step 2: MCPTT server checks users' privacy policy for sharing location information. Step 3: MCPTT server provides the location information of the current talker to MCPTT client 2 and IWF.](55f11fbbe5ef616ee7a1814f932acbaa_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant MCPTT client 2 + participant IWF + Note right of MCPTT Client 1: 1.MCPTT client 1 acquires the floor for transmission + Note right of MCPTT server: 2.Check users' privacy policy for sharing location information + Note right of MCPTT server: 3.Provides the location information of the current talker + +``` + +Sequence diagram showing the interaction between MCPTT Client 1, MCPTT server, MCPTT client 2, and IWF for providing location information. Step 1: MCPTT client 1 acquires the floor for transmission. Step 2: MCPTT server checks users' privacy policy for sharing location information. Step 3: MCPTT server provides the location information of the current talker to MCPTT client 2 and IWF. + +**Figure 10.11.2-1: Providing location information of the current talker** + +1. MCPTT client 1 gets the floor to transmit voice media. +2. The MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the current talking MCPTT user to decide if the location information of MCPTT client 1 can be provided to other MCPTT users on the call. +3. If the privacy policy permits, the MCPTT server provides the location information of MCPTT client 1 to MCPTT client 2 and the IWF. The procedures for this are described in 3GPP TS 23.280 [5] subclause 10.9.3.6. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 and the IWF according to 3GPP TS 23.379 [7] subclause 10.9.1.3.1, if the privacy policy permits. + +### 10.11.3 Location of current talker (IWF to MCPTT server) + +Figure 10.11.3-1 shows the high-level procedure to for the IWF to provide the location information about the current LMR talking user to all the receiving MCPTT users. + +Pre-conditions: + +1. There is on-going group call involving MCPTT client 1 and MCPTT client 2 and the IWF. +2. An LMR user is the current talking user through the IWF. + +NOTE: How the MCPTT server acquires the location of the LMR user is outside the scope of the present document. + +![Sequence diagram showing the interaction between MCPTT server, MCPTT client 2, MCPTT client 1, and IWF for providing location information. The sequence is: 1. IWF acquires the floor for transmission; 2. MCPTT server checks user's privacy policy for sharing location information; 3. MCPTT server provides the location information of the current talker to MCPTT client 1 and MCPTT client 2.](92c9263daf7fbd044894e2b273ae21af_img.jpg) + +``` + +sequenceDiagram + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 1 + participant IWF + Note right of IWF: 1.IWF acquires the floor for transmission + Note left of MCPTT server: 2.Check users' privacy policy for sharing location information + Note right of MCPTT server: 3.Provides the location information of the current talker + +``` + +Sequence diagram showing the interaction between MCPTT server, MCPTT client 2, MCPTT client 1, and IWF for providing location information. The sequence is: 1. IWF acquires the floor for transmission; 2. MCPTT server checks user's privacy policy for sharing location information; 3. MCPTT server provides the location information of the current talker to MCPTT client 1 and MCPTT client 2. + +**Figure 10.11.3-1: Providing location information of the current talker** + +1. The IWF gets the floor to transmit voice media. +2. The MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the current talking IWF user to decide if the location information of the user on the IWF can be provided to other MCPTT users on the call. +3. The MCPTT server provides the location information of the IWF user to MCPTT client 1 and MCPTT client 2. The procedures for this are described in 3GPP TS 23.280 [5] subclause 10.9.3.6. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 and the IWF according to 3GPP TS 23.379 [7] subclause 10.9.1.3.1. + +## 10.11.4 Information flows for location information between the IWF and the LMS + +*Editor's Note: It is FFS whether LMR technology type (e.g. TETRA, P25, analogue FM TIA-603-D [9] Standard) will need to be utilized in location messages between the MC system and the IWF.* + +### 10.11.4.1 Location information services between the IWF and the LMS + +#### 10.11.4.1.1 IWF Location information report + +Table 10.9.2.2-4 in 3GPP TS 23.280 [5] describes the information flow to support the handling of a location information report from the LMS to the IWF and from the IWF to the LMS. + +#### 10.11.4.1.2 IWF Location information request + +Table 10.9.2.3-4 in 3GPP TS 23.280 [5] describes the information flow to support the handling of an IWF Location information request from the LMS to the IWF and from the IWF to the LMS. + +#### 10.11.4.1.3 IWF Location information subscription request + +Table 10.9.2.5-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information subscription request. + +#### 10.11.4.1.4 IWF Location information subscription response + +Table 10.9.2.6-1 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information subscription response. + +#### 10.11.4.1.5 IWF Location information notification + +Table 10.9.2.7-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information notification. + +#### 10.11.4.1.6 IWF Location information cancel subscription request + +Table 10.9.2.8-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information cancel subscription request. + +#### 10.11.4.1.7 IWF Location information cancel subscription response + +Table 10.9.2.9-3 in 3GPP TS 23.280 [5] describes the information flow from the LMS to the IWF and from the IWF to the LMS for an IWF Location information cancel subscription response. + +### 10.11.4.2 Location information procedures between the IWF and the LMS + +*Editor's Note: It is FFS how configuration can be added to restrict the reporting and tracking of users in a partner MC system, or users within an LMR system. Configuration for restricting the reporting and tracking of location information in a partner MC system is not present in current stage 2 specifications.* + +#### 10.11.4.2.1 On-demand request of location information procedure + +##### 10.11.4.2.1.1 On-demand request of location information procedure (LMS to IWF) + +The MC service server or location management client in the MC system can request an LMR user's location information, which is in the LMR system, at any time by sending an IWF Location information request to the IWF at the LMR system. + +The LMR user appears to the MC system as an MC service user. The IWF provides interworking to obtain location information for the LMR user associated with the MC service identity it receives. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.1.1-1 illustrates the high level procedure of on-demand request of location information. + +![Sequence diagram illustrating the on-demand request of location information procedure. The diagram shows interactions between the MC system (MC service server or LMC, LMS) and the LMR system (IWF).](53499879d98034410ecba2c386c58f0c_img.jpg) + +``` + +sequenceDiagram + participant MCSS as MC service server or LMC + participant LMS + participant IWF + Note right of LMS: 2. Authorization check + Note right of LMS: 3. Determine partner Location management server + Note right of IWF: 5. Authorization check + Note right of IWF: 6. Obtain the location information + + MCSS->>LMS: 1. Location information Request + LMS->>IWF: 4. IWF Location information request + IWF-->>LMS: 7. IWF Location information report + LMS-->>MCSS: 7. Location information report + +``` + +Sequence diagram illustrating the on-demand request of location information procedure. The diagram shows interactions between the MC system (MC service server or LMC, LMS) and the LMR system (IWF). + +**Figure 10.11.4.2.1.1-1: On-demand request of location information procedure** + +1. The MC service server or a LMC in the MC system requests from the LMS on-demand location information of the LMR user that appears as an MC service user. +2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed. + +NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure. + +3. The LMS in the MC system determines that the request has a target in the LMR system. +4. The LMS in the MC system sends the IWF Location information request to the IWF in the LMR system according to the described information flow in clause 10.11.4.1.2. +5. The IWF in the LMR system can choose to authorize the request. +6. The IWF at the LMR system determines the location information for the LMR user associated with the MC service user identified in the request. +7. The IWF at the LMR system sends the IWF Location information report, described in clause 10.11.4.1.1, to the LMS in the MC system. The LMS forwards the location information report to the MC service server or the LMC. + +#### 10.11.4.2.1.2 On-demand request of location information procedure (IWF to LMS) + +The IWF in the LMR system can request an MC service user's location information, which is in the MC system, at any time by sending an IWF Location information request to the LMS at the MC system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.1.2-1 illustrates the high level procedure of on-demand request of location information. + +![Sequence diagram illustrating the on-demand request of location information procedure between an LMR system (IWF) and an MC system (LMS).](6a2b92323d788c2e7e9e570025885181_img.jpg) + +``` + +sequenceDiagram + participant IWF as IWF (LMR system) + participant LMS as LMS (MC system) + Note right of IWF: 1. Determine need for location information + Note right of IWF: 2. Determine partner LMS + IWF->>LMS: 3. IWF Location information request + Note right of LMS: 4. Authorization check + Note right of LMS: 5. Obtain the location information + LMS->>IWF: 6. IWF Location information response + +``` + +The diagram shows a sequence of interactions between the IWF in the LMR system and the LMS in the MC system. The process starts with the IWF determining the need for location information and identifying the partner LMS. It then sends an IWF Location information request to the LMS. The LMS performs an authorization check and obtains the location information. Finally, the LMS sends an IWF Location information response back to the IWF. + +Sequence diagram illustrating the on-demand request of location information procedure between an LMR system (IWF) and an MC system (LMS). + +**Figure 10.11.4.2.1.2-1: On-demand request of location information procedure** + +1. The IWF in the LMR system determines that location information is needed for an MC service user. +2. The IWF in the LMR system determines that the MC service user is in the MC system. +3. The IWF in the LMR system sends the IWF Location information request to the LMS in the MC system according to the described information flow in clause 10.11.4.1.2. +4. The LMS in the MC system authorizes the request. +5. The LMS in the MC system determines the location information for the MC service user identified in the request. +6. The LMS in the MC system sends the IWF Location information report, described in clause 10.11.4.1.1, to the IWF in the LMR system. + +## 10.11.4.2.2 Location information notification procedure + +### 10.11.4.2.2.1 Location information notification procedure (IWF to LMS) + +The IWF in the LMR system provides location information, based on some decision or event, to the LMS. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.2.1-1 illustrates the high level procedure of notification of location information. + +![Sequence diagram for Figure 10.11.4.2.2.1-1: Event-triggered location information notification procedure (LMR to MC).](3220d3a933797114c1ba20d5c4ec093d_img.jpg) + +The diagram illustrates the interaction between an LMR system and an MC system. The LMR system contains an IWF (Interworking Function) and the MC system contains an LMS (Location Management System). The sequence of events is as follows: + +1. Determine that location information is to be notified. (Internal step in the IWF) +2. IWF Location information notification (Message from IWF to LMS) + +Sequence diagram for Figure 10.11.4.2.2.1-1: Event-triggered location information notification procedure (LMR to MC). + +**Figure 10.11.4.2.2.1-1: Event-triggered location information notification procedure** + +1. The IWF in the LMR system determines that it has location information available that is to be notified to the LMS in the MC system. +2. The IWF in the LMR system sends the IWF Location information notification to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.5. + +#### 10.11.4.2.2.2 Location information notification procedure (LMS to IWF) + +The LMS in the MC system provides location information to the IWF in the LMR system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.2.2-1 illustrates the high level procedure of notification of location information. + +![Sequence diagram for Figure 10.11.4.2.2.2-1: Event-triggered location information notification procedure (MC to LMR).](813ef40a14c7e2a52988a63e33c2b59f_img.jpg) + +The diagram illustrates the interaction between an MC system and an LMR system. The MC system contains an LMS (Location Management System) and the LMR system contains an IWF (Interworking Function). The sequence of events is as follows: + +1. Determine that location information is to be notified. (Internal step in the LMS) +2. IWF Location information notification (Message from LMS to IWF) + +Sequence diagram for Figure 10.11.4.2.2.2-1: Event-triggered location information notification procedure (MC to LMR). + +**Figure 10.11.4.2.2.2-1: Event-triggered location information notification procedure** + +1. The LMS in the MC system determines that it has location information available that is to be notified to the IWF in the LMR system. + +2. The LMS in the MC system sends the IWF Location information notification to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.5. + +### 10.11.4.2.3 Location information subscription procedure + +#### 10.11.4.2.3.1 Location information subscription procedure (LMS to IWF) + +An IWF Location information subscription request is sent from the MC system to the IWF. The IWF in the LMR system sends an IWF location information subscription response. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.3.1-1 illustrates the high level procedure of subscription to location information from the LMS in the MC system to the IWF in the LMR system. + +![Sequence diagram illustrating the Location information subscription procedure (LMS to IWF) between the MC system and the LMR system.](c7e196e0c468cc7b9a84c12c951209a0_img.jpg) + +``` + +sequenceDiagram + participant MCSS as MC service server or LMC + participant LMS + participant IWF + Note right of LMS: 2. Authorization check + Note right of LMS: 3. Determine partner Location management server + Note right of IWF: 5. Authorization check + Note right of IWF: 6. Apply subscription + + MCSS->>LMS: 1. Location information subscription request + LMS->>IWF: 4. IWF Location information subscription request + IWF-->>LMS: 7. IWF Location information subscription response + LMS-->>MCSS: 7. Location information subscription response + +``` + +The diagram shows the interaction between the MC system (containing MC service server or LMC and LMS) and the LMR system (containing IWF). The sequence of steps is as follows: + +- The MC service server or LMC sends a "Location information subscription request" to the LMS. +- The LMS performs an "Authorization check". +- The LMS performs "Determine partner Location management server". +- The LMS sends an "IWF Location information subscription request" to the IWF. +- The IWF performs an "Authorization check". +- The IWF performs "Apply subscription". +- The IWF sends a "7. IWF Location information subscription response" to the LMS, which then forwards it as a "7. Location information subscription response" to the MC service server or LMC. + +Sequence diagram illustrating the Location information subscription procedure (LMS to IWF) between the MC system and the LMR system. + +**Figure 10.11.4.2.3.1-1: Location information subscription procedure** + +1. The MC service server or the LMC in the MC system sends a request for subscription to event-triggered location information of LMR users that appear as MC service users in the LMR system by sending a location information subscription request to the LMS in the MC system, according to the described information flows in clause 10.9.2.5 in 3GPP TS 23.280 [5]. +2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed. + +NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure. + +3. The LMS in the MC system determines that the request has a target in an LMR system. + +4. The LMS in the MC system sends the IWF Location information subscription request to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.3. +5. The IWF in the LMR system can check if the provided information along with the configuration permit the request to proceed. +6. The IWF in the LMR system applies the subscription. +7. The IWF in the LMR system sends the IWF Location information subscription response to the LMS in the MC system according to the described information flow in clause 10.11.4.1.4. The LMS in the MC system can respond to the LMC or MC server in the MC system per the procedures of 3GPP TS 23.280 [5]. + +#### 10.11.4.2.3.2 Location information subscription procedure (IWF to LMS) + +An IWF Location information subscription request is sent from the MC system to the IWF. The IWF in the LMR system sends an IWF Location information subscription response. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.3.2-1 illustrates the high level procedure of subscription to location information from the LMS in the MC system to the IWF in the LMR system. + +![Sequence diagram illustrating the location information subscription procedure between the LMR system and the MC system.](19a8fc45b10957bab04a686521657f46_img.jpg) + +``` +sequenceDiagram + participant LMR system + participant MC system + Note left of LMR: 1. Determine that a location subscription is needed + Note left of LMR: 2. Determine partner LMS + LMR->>MC: 3. IWF Location information subscription request + Note right of MC: 4. Authorization check + Note right of MC: 5. Apply subscription + MC->>LMR: 6. IWF Location information subscription response +``` + +The diagram shows a sequence of steps for the location information subscription procedure. It starts with the LMR system (left) and the MC system (right). The LMR system contains an IWF (Interworking Function) and the MC system contains an LMS (Location Management System). The steps are: 1. Determine that a location subscription is needed (in the LMR system); 2. Determine partner LMS (in the LMR system); 3. IWF Location information subscription request (sent from the IWF in the LMR system to the LMS in the MC system); 4. Authorization check (in the MC system); 5. Apply subscription (in the MC system); 6. IWF Location information subscription response (sent from the LMS in the MC system to the IWF in the LMR system). + +Sequence diagram illustrating the location information subscription procedure between the LMR system and the MC system. + +**Figure 10.11.4.2.3.2-1: Location information subscription procedure** + +1. The IWF in the LMR system determines that it needs to subscribe to location information notifications for an MC service user. +2. The IWF in the LMR system determines that the request has a target in the MC system. +3. The IWF in the LMR system sends the IWF Location information subscription request to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.3. + +4. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed. +5. The LMS in the MC system applies the subscription. +6. The LMS in the MC system sends the IWF Location information subscription response to the LMS in the MC system according to the described information flow in clause 10.11.4.1.4. + +#### 10.11.4.2.4 Location information cancel subscription procedure + +##### 10.11.4.2.4.1 Location information cancel subscription procedure (LMS to IWF) + +The LMC in the MC system receives location information updates according to the subscriptions requested in the LMR system per clause 10.11.4.2.3. Those subscriptions can be cancelled anytime from the MC system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.4.1-1 illustrates the high level procedure of the subscription cancellation to location information from the MC system to the LMR system. + +![Sequence diagram illustrating the Location information cancel subscription procedure between the MC system and the LMR system.](a969a3a831d0967b54efe1400846ed30_img.jpg) + +``` + +sequenceDiagram + participant MCSS as MC service server or LMC + participant LMS + participant IWF + Note right of LMS: 2. Authorization check + Note right of LMS: 3. Determine partner Location management server + Note right of IWF: 5. Authorization check + Note right of IWF: 6. Cancel subscription + + MCSS->>LMS: 1. Location information cancel subscription request + LMS->>IWF: 4. IWF Location information cancel subscription request + IWF->>LMS: 7. IWF Location information cancel subscription response + LMS->>MCSS: 7. Location information cancel subscription response + +``` + +The diagram shows the interaction between the MC system (containing MC service server or LMC and LMS) and the LMR system (containing IWF). The sequence of messages is as follows: + + +- The MC service server or LMC sends a "Location information cancel subscription request" to the LMS. +- The LMS performs an "Authorization check" (step 2). +- The LMS performs a "Determine partner Location management server" (step 3). +- The LMS sends an "IWF Location information cancel subscription request" to the IWF. +- The IWF performs an "Authorization check" (step 5). +- The IWF performs a "Cancel subscription" (step 6). +- The IWF sends an "IWF Location information cancel subscription response" to the LMS. +- The LMS sends a "Location information cancel subscription response" to the MC service server or LMC. + +Sequence diagram illustrating the Location information cancel subscription procedure between the MC system and the LMR system. + +**Figure 10.11.4.2.4.1-1: Location information cancel subscription procedure** + +1. The MC service server or the LMC in the MC system requests the cancellation of subscriptions to event-triggered location information of LMR users that appear as MC service users in the LMR system by sending location information cancel subscription requests to the LMS in the MC system, according to the described information flows in clause 10.9.2.8 in 3GPP TS 23.280 [5]. +2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed. + +NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure. + +3. The LMS in the MC system determines that the request has a target in an LMR system. +4. The LMS in the MC system sends the IWF Location information cancel subscription request to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.6. +5. The IWF in the LMR system can check if the provided information along with the configuration permit the request to proceed. +6. The IWF in the LMR system cancels the subscription. +7. The IWF in the LMR system sends the IWF Location information cancel subscription response to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.7. The LMS can forward the location information cancel subscription response per the procedures in 3GPP TS 23.280 [5]. + +#### 10.11.4.2.4.2 Location information cancel subscription procedure (IWF to LMS) + +The IWF in the LMR system receives location information updates according to the subscriptions requested in the MC system per clause 10.11.4.2.3.2. Those subscriptions can be cancelled anytime from the LMR system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system. + +Figure 10.11.4.2.4.2-1 illustrates the high level procedure of the subscription cancellation to location information from the LMR system to the MC system. + +![Sequence diagram illustrating the Location information cancel subscription procedure (IWF to LMS) between an LMR system and an MC system.](da5916a6e0721dae9522ac5b8abd218f_img.jpg) + +``` +sequenceDiagram + participant LMR system + participant MC system + Note left of LMR system: 1. Determine need to cancel location information subscription + Note left of LMR system: 2. Determine partner LMS + LMR system->>MC system: 3. IWF Location information cancel subscription request + Note right of MC system: 4. Authorization check + Note right of MC system: 5. Cancel subscription + MC system->>LMR system: 6. IWF Location information cancel subscription response +``` + +The diagram shows a sequence of steps for the location information cancel subscription procedure. It starts with the LMR system (left) determining the need to cancel a subscription (step 1) and identifying the partner LMS (step 2). The IWF in the LMR system then sends a 'IWF Location information cancel subscription request' (step 3) to the LMS in the MC system. The LMS performs an authorization check (step 4) and cancels the subscription (step 5). Finally, the LMS sends a 'IWF Location information cancel subscription response' (step 6) back to the IWF in the LMR system. + +Sequence diagram illustrating the Location information cancel subscription procedure (IWF to LMS) between an LMR system and an MC system. + +**Figure 10.11.4.2.4.2-1: Location information cancel subscription procedure** + +1. The IWF in the LMR system determines that a location information subscription is to be cancelled. + +2. The IWF in the LMR system determines that the request has a target in the MC system. +3. The IWF in the LMR system sends the IWF Location information cancel subscription request to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.6. +4. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed. +5. The LMS in the MC system cancels the subscription. +6. The LMS in the MC system sends the IWF Location information cancel subscription response to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.7. + +## 10.12 LMR security transport + +### 10.12.1 Information flows for LMR security transport + +#### 10.12.1.1 Non-3GPP security message request + +Table 10.12.1.1-1 describes the information flow non-3GPP security message request from the MC service server to the IWF, from the IWF to the MC service server, from the MC service server to the MC service client and from the MC service client to the MC service server. + +**Table 10.12.1.1-1: Non-3GPP security message request** + +| Information Element | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user | +| URI of LMR security functional entity | M | URI of LMR key management functional entity user profile parameter defined in 3GPP TS 23.379 [7] | +| LMR type | O | The LMR technology, e.g. TETRA, P25. Required when sent toward the MC service client. | +| Payload | M | Opaque payload. Contents and format are out of 3GPP scope. | + +#### 10.12.1.2 Non-3GPP security message response + +Table 10.12.1.2-1 describes the information flow non-3GPP security message response from the MC service server to the IWF, from the IWF to the MC service server, from the MC service server to the MC service client and from the MC service client to the MC service server. + +**Table 10.12.1.2-1: Non-3GPP security message response** + +| Information Element | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user | +| URI of LMR security functional entity | M | URI of LMR key management functional entity user profile parameter defined in 3GPP TS 23.379 [7] | + +## 10.12.2 LMR key management messages + +### 10.12.2.1 General + +This subclause defines end to end messaging to convey the non-3GPP, LMR security information opaquely (message contents are out of 3GPP's scope) across the MC system, between the IWF and the LMR aware MC service client. The end to end messages are service independent, any MC service may support them. + +### 10.12.2.2 MC service client initiated + +Figure 10.12.2.2-1 describes the case where an MC service client sends LMR security information to the IWF. + +Pre-conditions: + +1. The MC service client is registered and the user is authenticated and authorized to use the MC service server. + +![Sequence diagram showing non-3GPP security messaging from MC service client to IWF via MC service server.](433e43d1c6dedf2fb2bc15a34b656b79_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + participant IWF + Note left of MC service client: MC service client initiates messaging + MC service client->>MC service server: 1. Non-3GPP security message request + MC service server->>IWF: 2. Non-3GPP security message request + IWF-->>MC service server: 3. Non-3GPP security message response + MC service server-->>MC service client: 4. Non-3GPP security message response +``` + +The diagram illustrates a sequence of four messages between three entities: MC service client, MC service server, and IWF. The sequence starts with the MC service client sending a 'Non-3GPP security message request' (labeled 1) to the MC service server. The MC service server then forwards this request (labeled 2) to the IWF. The IWF responds with a 'Non-3GPP security message response' (labeled 3) to the MC service server. Finally, the MC service server sends its own 'Non-3GPP security message response' (labeled 4) back to the MC service client. + +Sequence diagram showing non-3GPP security messaging from MC service client to IWF via MC service server. + +**Figure 10.12.2.2-1: Non-3GPP security messaging, MC service client to the IWF** + +1. The MC service client sends a non-3GPP security message request to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP. +2. The MC service server forwards the contents of the non-3GPP security message request to the IWF. +3. The IWF acknowledges with a non-3GPP security message response to the MC service server. +4. The MC service server acknowledges with a non-3GPP security message response to the MC service client. + +NOTE: The non-3GPP security message response can be asynchronous across the MC service server. + +### 10.12.2.3 IWF initiated + +Figure 10.12.2.3-1 describes the case where the IWF sends LMR security information to an MC service client. + +Pre-conditions: + +1. The MC service client is registered and the user is authenticated and authorized to use the MC service server. + +![Sequence diagram showing Non-3GPP security messaging from the IWF to the MC service client. The diagram involves three participants: IWF, MC service server, and MC service client. The sequence of messages is: 1. IWF sends a non-3GPP security message request to the MC service server; 2. MC service server forwards the request to the MC service client; 3. MC service client sends a non-3GPP security message response to the MC service server; 4. MC service server sends a non-3GPP security message response to the IWF.](c355b8056bdd4728357d7d5ed18792ca_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC service server + participant MC service client + Note left of IWF: 1. Non-3GPP security message request + IWF->>MC service server: 1. Non-3GPP security message request + Note right of MC service server: 2. Non-3GPP security message request + MC service server->>MC service client: 2. Non-3GPP security message request + Note right of MC service client: 3. Non-3GPP security message response + MC service client->>MC service server: 3. Non-3GPP security message response + Note left of MC service server: 4. Non-3GPP security message response + MC service server->>IWF: 4. Non-3GPP security message response + +``` + +Sequence diagram showing Non-3GPP security messaging from the IWF to the MC service client. The diagram involves three participants: IWF, MC service server, and MC service client. The sequence of messages is: 1. IWF sends a non-3GPP security message request to the MC service server; 2. MC service server forwards the request to the MC service client; 3. MC service client sends a non-3GPP security message response to the MC service server; 4. MC service server sends a non-3GPP security message response to the IWF. + +**Figure 10.12.2.3-1: Non-3GPP security messaging, from the IWF to MC service client** + +1. The IWF sends a non-3GPP security message request to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP. +2. The MC service server forwards the contents of non-3GPP security message request to the MC service client. +3. The MC service client acknowledges with a non-3GPP security message response to the MC service server. +4. The MC service server acknowledges with a non-3GPP security message response to the IWF. + +NOTE: The non-3GPP security message response can be asynchronous across the MC service server. + +## 10.13 Analogue FM/TIA-603-D and other legacy LMR interworking + +**Editor's Note:** It is FFS whether clause 10.13 requires updates based on the introduction of location reporting between an MC system and an LMR system. + +### 10.13.1 General + +An IWF representing an LMR user can support interworking with legacy analogue FM radio systems that are compliant with the TIA-603-D [9] Standard. This type of legacy LMR system is sometimes referred to as conventional FM radio. + +Characteristics of legacy conventional FM radio include: + +- Voice media is conveyed without the use of a voice codec. +- There is no possibility of end-to-end encryption between an LMR user and a MC user. +- Group communication is possible using various means to identify a group such as a single channel / FM frequency, or sub-audible data as defined in [3]. The means for identifying groups within the legacy conventional FM system is outside the scope of the present document. +- The ID of the talking party is generally not available. Various means to identify a talker are available in legacy conventional FM systems, but this is outside the scope of the present document. +- Indication of call priority (e.g. emergency) is generally not available. Various means to identify priority are available in legacy conventional FM systems, but this is outside the scope of the present document. + +Other legacy LMR systems such as digital conventional (e.g. P25 conventional), trunked analogue FM systems, non-standard legacy LMR systems, both conventional and trunked, can also be supported as long as they conform to the present document. + +### 10.13.2 Interworking Concepts + +Procedures defined in the present document are applicable to interworking with legacy analogue FM radio systems. + +Architecture concepts for interworking are summarized below, including general information for other legacy conventional radio systems. + +- The IWF is configured with knowledge of groups and users from legacy conventional LMR radio systems. Translations to MCPTT Group and MCPTT User IDs is performed by the IWF as specified in the present document. How the legacy LMR conventional system supports groups, such as mapping a group to a channel/frequency, or using a Group ID (i.e. P25 conventional), or mapping some other protocol element or tone signalling to a group is outside the scope of the present document. +- Interworking to a legacy conventional LMR system can make use of the following procedures as defined in the present document: + - affiliation; + - group management including group regrouping + - group calls including pre-arranged, chat, and broadcast; + - priority calls including emergency and imminent peril; and + - private calls. + +NOTE 1: Some analogue FM conventional LMR systems and digital conventional LMR systems support various schemes for private call. These can be supported as long as they conform to the present document. + +- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document: + - transcoding. +- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document, with some limitations: + - caller ID / talker ID; + - priority indication (e.g. emergency); + - end-to-end encryption; + - location; and + - short data service. + +NOTE 2: Some digital conventional LMR systems, such as P25 Conventional, natively support group IDs, user IDs, short data, and priority indication. In some cases, the talker ID becomes available sometime after the call starts. + +NOTE 3: Some analogue FM conventional LMR systems support various schemes for caller ID, emergency, and other features (e.g. Multi-tone, Type 99). These can be supported as long as they conform to the present document. In some cases, the talker ID becomes available sometime after the call starts. + +NOTE 4: Some digital conventional LMR systems, such as P25 Conventional, can support end-to-end encryption between the LMR user and a MC user. There is no possibility of end-to-end encryption between an analogue FM LMR user and a MC user. + +### 10.13.3 Procedures + +As described above, existing procedures in this document can be used for interworking with legacy conventional LMR radio systems. + +The following procedures describe special cases where the MCPTT ID (i.e. talker ID) is updated during a media transmission within a call. This mechanism of updating the MCPTT ID part way through an MCPTT media transmission may be used for any MCPTT media transmission described elsewhere in the present document. + +### 10.13.3.1 Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system + +In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the MCPTT system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.1-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the interworking group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. The LMR user in a legacy conventional FM radio system initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2.](10f4e3a2f3c016555ee12a5b556ba834_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note right of MCPTT server: 2. Call affiliated MCPTT users + + IWF->>MCPTT server: 1. IWF group call request + MCPTT server->>MCPTT client 1: + MCPTT server->>MCPTT client 2: + MCPTT server-->>IWF: 3. IWF group call request + IWF-->>MCPTT server: 4. IWF group call response + MCPTT server-->>IWF: 5. IWF group call response + Note right of MCPTT server: 6. Media plane is established + MCPTT server->>IWF: 7. IWF floor granted + MCPTT server->>MCPTT client 1: 7. Floor taken + MCPTT server->>MCPTT client 2: 7. Floor taken + MCPTT server-->>IWF: 8. IWF floor taken + Note left of IWF: 9. LMR user talker ID is received by the IWF + IWF->>MCPTT server: 10. IWF Talker ID update + MCPTT server->>MCPTT client 1: 11. Floor taken + MCPTT server->>MCPTT client 2: 11. Floor taken + MCPTT server-->>IWF: 12. IWF floor taken + +``` + +Sequence diagram for Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. + +**Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF group call request to the MCPTT server for call establishment. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request. +2. The MCPTT server calls the affiliated users from the MCPTT system as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF. +3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user. + +NOTE 2: Steps 2 and 3 can occur in any order. + +NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document. + +4. The IWF returns IWF group call response(s) to the MCPTT server. +5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF. + +NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document. + +6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document. + +7. Because the group call request contained an implicit floor request, and no other users are requesting the floor, the MCPTT server sends an IWF floor granted message to the IWF confirming that the IWF has the floor. The MCPTT server also sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID. + +8. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user. + +9. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID. + +NOTE 6: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call. + +10. The IWF sends an IWF talker ID update to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released. + +11. The MCPTT server sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update. + +NOTE 7: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker. + +12. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user. + +### 10.13.3.2 Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system + +In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the LMR system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.2-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the interworking group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. The LMR user in a legacy conventional FM radio system initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating a group call with talker ID update initiated by an LMR user on an interworking group. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The process involves group call requests, responses, media plane establishment, and floor taken messages.](633486b12958f97e062b5cf9e0801e99_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of IWF: 8. LMR user talker ID is received by the IWF + + IWF->>MCPTT server: 1a. IWF group call request + IWF->>MCPTT server: 1b. IWF group call request + MCPTT server->>MCPTT client 1: 2a. Group call request + MCPTT server->>MCPTT client 2: 2b. Group call request + MCPTT client 1->>MCPTT server: 3a. Group call response + MCPTT client 2->>MCPTT server: 3b. Group call response + MCPTT server->>IWF: 4a. IWF group call response + MCPTT server->>IWF: 4b. IWF group call response + + Note over IWF, MCPTT client 2: 5. Media plane is established + + IWF->>MCPTT server: 6a. IWF floor taken + IWF->>MCPTT server: 6b. IWF floor taken + MCPTT server->>MCPTT client 1: 7a. Floor taken + MCPTT server->>MCPTT client 2: 7b. Floor taken + + Note left of IWF: 8. LMR user talker ID is received by the IWF + + IWF->>MCPTT server: 9a. IWF floor taken + IWF->>MCPTT server: 9b. IWF floor taken + MCPTT server->>MCPTT client 1: 10a. Floor taken + MCPTT server->>MCPTT client 2: 10b. Floor taken + +``` + +Sequence diagram illustrating a group call with talker ID update initiated by an LMR user on an interworking group. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The process involves group call requests, responses, media plane establishment, and floor taken messages. + +**Figure 10.13.3.2-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system** + +1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request. +2. The MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF. +3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response. +4. The MCPTT server acknowledges the IWF group call request(s) by sending an IWF group call response(s) to the IWF. + +NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document. + +5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +NOTE 3: How the floor control is managed in the LMR system is outside the scope of the present document. + +6. Because the group call request contained an implicit floor request, and no other users are requesting the floor, the IWF sends an IWF floor taken message to the MCPTT server confirming that the IWF has the floor. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. + +7. The MCPTT server sends Floor taken to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID. + +8. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID. + +NOTE 4: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call. + +9. The IWF sends an IWF floor taken to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2 + +10. The MCPTT server sends Floor taken messages to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update. + +NOTE 5: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker. + +## 10.14 IWF functional alias management + +### 10.14.1 General + +LMR users homed in the IWF shall have the ability to enable, apply, or disable a functional alias in the MC system for the use in communication with MC service users. + +*Editor's Note: The corresponding service profiles in the MC system for LMR user homed to IWF are FFS.* + +*Editor's Note: How the MC service system authorizes the actions of users homed in the IWF is FFS.* + +The functional alias feature is not a requirement in 3GPP TS 22.179 [3] and is therefore an optional feature for systems that support 3GPP TS 22.179 [3]. + +### 10.14.2 IWF information flows for functional alias management + +#### 10.14.2.1 IWF functional alias information query request + +Table 10.14.2.1-1 describes the information flow of the functional alias information query request from the IWF to the MC service server. + +**Table 10.14.2.1-1: IWF functional alias information query request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| MC service ID | M | The identity of the requesting MC service user. | +| MC service ID | O | The identity of the MC service user to be queried. | +| Functional alias | O | The functional alias to be queried. | + +#### 10.14.2.2 IWF functional alias information query response + +Table 10.14.2.2-1 describes the information flow of the functional alias information query response from the MC service server to the user homed in the IWF. + +**Table 10.14.2.2-1: IWF functional alias information query response.** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user that performed the query. | +| MC service ID | O | The identity of the MC service user that was queried. | +| Functional alias | O | The functional alias that was queried. | +| Query result | M | The functional alias or MC service ID information retrieved from the functional alias management server, i.e. the list of activated functional alias identities of the MC service user or the associated MC service IDs and status which correspond to the queried functional alias. | + +### 10.14.2.3 IWF functional alias activation request + +Table 10.14.2.3-1 describes the information flow of the functional alias activation request from the IWF to the MC service server. + +**Table 10.14.2.3-1: IWF functional alias activation request** + +| Information element | Status | Description | +|-----------------------|--------|------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the requesting MC service user. | +| Functional alias list | M | A list of one or more functional aliases which the originator intends to activate. | + +### 10.14.2.4 IWF functional alias activation response + +Table 10.14.2.4-1 describes the information flow of the functional alias activation response from the MC service server to the IWF. + +**Table 10.14.2.4-1: IWF functional alias activation response** + +| Information element | Status | Description | +|----------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user that originated the functional alias activation request. | +| Functional alias list | M | A list of one or more functional aliases which the originating party intended to activate. | +| Activation status per functional alias | M | Indicates the activation result for each functional alias in the list (activated, rejected, can be taken over). | + +### 10.14.2.5 IWF functional alias de-activation request + +Table 10.14.2.5-1 describes the information flow functional alias de-activation request from the IWF to the MC service server. + +**Table 10.14.2.5-1: IWF functional alias de-activation request** + +| Information element | Status | Description | +|-----------------------|--------|-------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the requesting MC service user. | +| Functional alias list | M | A list of one or more functional aliases which the requesting MC service user intends to de-activate. | + +### 10.14.2.6 IWF functional alias de-activation response + +Table 10.14.2.6-1 describes the information flow of the functional alias de-activation response from the MC service server to the user homed in the IWF. + +**Table 10.14.2.6-1: IWF functional alias de-activation response** + +| Information element | Status | Description | +|-------------------------------------------|--------|-------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user that originated the functional alias de-activation request. | +| Functional alias list | M | A list of one or more functional aliases which the originating party intends to de-activate. | +| De-activation status per functional alias | M | Indicates the de-activation result for every functional alias in the list. | + +#### 10.14.2.7 IWF functional alias status notification + +Table 10.14.2.7-1 describes the information flow of the functional alias notification from the MC service server to the IWF. + +**Table 10.14.2.7-1: IWF functional alias status notification** + +| Information element | Status | Description | +|-----------------------|--------|--------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user that originated the functional alias activation, de-activation or take over request. | +| Functional alias list | M | A list of one or more functional aliases. | +| Operational status | M | Activation, de-activation or take over status per functional alias. | + +#### 10.14.2.8 IWF Functional alias take over request + +Table 10.14.2.8-1 describes the information flow of the functional alias take over request from the IWF to the MC service server. + +**Table 10.14.2.8-1: IWF functional alias take over request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MC service ID | M | The identity of the requesting MC service user. | +| Functional alias | M | A functional alias which the requester intends to take over. | + +#### 10.14.2.9 IWF Functional alias take over response + +Table 10.14.2.9-1 describes the information flow of the functional alias take over response from the MC service server to the IWF. + +**Table 10.14.2.9-1: IWF functional alias take over response** + +| Information element | Status | Description | +|----------------------------------------|--------|--------------------------------------------------------------| +| MC service ID | M | The identity of the requesting MC service user. | +| Functional alias | M | A functional alias which the requester intends to take over. | +| Activation status per functional alias | M | Indicates the take over request result (accepted, rejected). | + +#### 10.14.2.10 IWF Functional alias revoke notification + +Table 10.14.2.10-1 describes the information flow of the functional revoke notification from the MC service server to the IWF. + +**Table 10.14.2.10-1: IWF functional alias revoke notification** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| MC service ID | M | The identity of the requesting MC service user. | +| Functional alias | M | The functional alias which is being revoked. | + +## 10.14.3 IWF Functional alias management procedures + +### 10.14.3.1 General + +The following subclauses describe the relevant functional alias management procedures between the MC system and the IWF to enable role based addressing of users homed in the IWF. + +### 10.14.3.2 User homed in the IWF retrieves active functional alias(es) for a certain MC service user + +An user homed in the IWF can request the active functional alias(es) for a certain MC service user. + +Figure 10.14.3.2-1 below illustrates the active functional alias list query for a certain MC service user. + +![Sequence diagram showing the IWF active functional alias list query. The IWF sends a request to the MC service server, which performs an authorization check and retrieves information, then responds back to the IWF.](936af4a8c1a8e4095b87b65c5b79137c_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC service server + Note right of MC service server: 2. Authorization check and retrieve functional alias(es) according to the conditions + IWF->>MC service server: 1. IWF functional alias information query request + MC service server-->>IWF: 3. IWF functional alias information query response + +``` + +Sequence diagram showing the IWF active functional alias list query. The IWF sends a request to the MC service server, which performs an authorization check and retrieves information, then responds back to the IWF. + +**Figure 10.14.3.2-1: IWF active functional alias list query** + +1. The user homed in the IWF requests a list of active functional aliases for a certain MC service ID from the MC service server by sending an IWF functional alias information query request encompassing the MC service ID or the functional alias of the queried user. +2. The MC service server checks whether the querying user homed in the IWF is authorized to perform the query. If authorized, then the MC service server retrieves the requested functional alias information based on the corresponding MC service ID or the MC service IDs based on the functional alias. + +**Editor's note: How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS.** + +3. The MC service server sends an IWF functional alias information query response including the active functional alias or MC service ID information to the user homed in the IWF. + +### 10.14.3.3 User homed in the IWF activates functional alias(es) within an MC system + +The procedure for the user homed in the IWF activates functional alias(es) within an MC system is illustrated in figure 10.14.3.3-1. + +Pre-conditions: + +1. The IWF has already been provisioned (statically or dynamically) with the functional alias(es) information that the user homed in the IWF is allowed to activate. + +- MC service server has retrieved the user subscription and functional alias policy e.g. which user(s) are authorized to activate to what functional alias, priority, and other configuration data. + +![Sequence diagram illustrating the IWF functional alias activation procedure within an MC system. The diagram shows three lifelines: IWF, MC service server, and Other MC service client(s). The sequence of messages is: 1. IWF functional alias activation request from IWF to MC service server; 2. Authorization check based on functional alias(es) policy, user subscription (internal to MC service server); 3. Store functional alias(es) status (internal to MC service server); 4. IWF functional alias(es) activation response from MC service server to IWF; 5. IWF functional alias(es) status notification from MC service server to IWF and from MC service server to Other MC service client(s).](e3e8a926bfe6337a654ecac063ba3682_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC_service_server as MC service server + participant Other_MC_service_client as Other MC service client(s) + Note right of MC_service_server: 2. Authorization check based on functional alias(es) policy, user subscription + Note right of MC_service_server: 3. Store functional alias(es) status + IWF->>MC_service_server: 1. IWF functional alias activation request + MC_service_server-->>IWF: 4. IWF functional alias(es) activation response + MC_service_server-->>IWF: 5. IWF functional alias(es) status notification + MC_service_server-->>Other_MC_service_client: 5. Functional alias(es) status notification + +``` + +Sequence diagram illustrating the IWF functional alias activation procedure within an MC system. The diagram shows three lifelines: IWF, MC service server, and Other MC service client(s). The sequence of messages is: 1. IWF functional alias activation request from IWF to MC service server; 2. Authorization check based on functional alias(es) policy, user subscription (internal to MC service server); 3. Store functional alias(es) status (internal to MC service server); 4. IWF functional alias(es) activation response from MC service server to IWF; 5. IWF functional alias(es) status notification from MC service server to IWF and from MC service server to Other MC service client(s). + +**Figure 10.14.3.3-1: IWF functional alias activation procedure within an MC system** + +- The user homed in the IWF requests the MC service server to activate a functional alias or a set of functional aliases. +- The MC service server checks if there are any conflicts with active functional alias(es). +- If the user homed in the IWF is authorised to activate the requested functional alias(es) then the MC service server stores the functional alias(es) status of the requested functional alias(es). + +**Editor's note:** How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS. + +If a certain functional alias(es) can be simultaneously active for multiple users and the upper limit of number of simultaneous MC service users is not reached, the MC service shall activate the functional alias(es) for the user homed in the IWF and inform all other user(s) with sharing the same functional alias(es) (step 5). If the limit of number of simultaneous users is reached or the functional alias is not allowed to be shared, the request is rejected, and the IWF is notified (step 4). + +**Editor's note:** How the MC service server checks whether a user homed in the IWF is an "authorized" user is FFS. + +If the functional alias(es) is (are) already used by another user(s), an authorized user homed in the IWF gets an offer to take over the functional alias from the user currently using the functional alias(es). + +- MC service server sends an IWF functional alias(es) activation response to the user homed in the IWF. +- The MC service server informs all other MC service user(s) and/or IWF sharing the same functional alias(es). + +#### 10.14.3.4 User homed in the IWF de-activates functional alias(es) within an MC system + +The procedure for the user homed in the IWF de-activates functional alias(es) within an MC system is illustrated in figure 10.14.3.4-1. + +When a user homed in the IWF does not want to use a functional alias(es) anymore, then the user homed in the IWF can de-activate functional alias(es). + +Pre-conditions: + +1. MC service server has already subscribed to the functional alias(es) information from the functional alias management server and has stored the data of the functional alias(es) a user homed in the IWF has activated. + +![Sequence diagram illustrating the IWF functional alias de-activation procedure within an MC system. The diagram shows three lifelines: IWF, MC service server, and Other MC service client(s). The sequence of messages is: 1. IWF functional alias deactivation request (IWF to MC service server); 2. Authorization check based on functional alias(es) policy, user subscription (internal to MC service server); 3. Store functional alias(es) status (internal to MC service server); 4. IWF functional alias(es) deactivation response (MC service server to IWF); 5. IWF functional alias(es) status notification (MC service server to IWF) and 5. Functional alias(es) status notification (MC service server to Other MC service client(s)).](dbe8bef1723acb3e03e8616be4faf939_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC_service_server as MC service server + participant Other_MC_service_client(s) as Other MC service client(s) + Note right of MC_service_server: 2. Authorization check based on functional alias(es) policy, user subscription + Note right of MC_service_server: 3. Store functional alias(es) status + IWF->>MC_service_server: 1. IWF functional alias deactivation request + MC_service_server-->>IWF: 4. IWF functional alias(es) deactivation response + MC_service_server-->>IWF: 5. IWF functional alias(es) status notification + MC_service_server-->>Other_MC_service_client(s): 5. Functional alias(es) status notification + +``` + +Sequence diagram illustrating the IWF functional alias de-activation procedure within an MC system. The diagram shows three lifelines: IWF, MC service server, and Other MC service client(s). The sequence of messages is: 1. IWF functional alias deactivation request (IWF to MC service server); 2. Authorization check based on functional alias(es) policy, user subscription (internal to MC service server); 3. Store functional alias(es) status (internal to MC service server); 4. IWF functional alias(es) deactivation response (MC service server to IWF); 5. IWF functional alias(es) status notification (MC service server to IWF) and 5. Functional alias(es) status notification (MC service server to Other MC service client(s)). + +**Figure 10.14.3.4-1: IWF functional alias de-activation procedure within an MC system** + +1. The user homed in the IWF requests the MC service server to de-activate a functional alias or a set of functional aliases. +2. Based on the MC service user subscription and stored functional alias policy, the MC service server checks if the user homed in the IWF is authorized to de-activate from the requested functional alias(es) and if the user homed in the IWF has activated to the requested functional alias(es). + +**Editor's note:** How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS. + +3. If the user homed in the IWF is authorized to de-activate from the requested functional alias(es) then the MC service server updates the functional alias activation status of the user homed in the IWF. +4. MC service server provides to the user homed in the IWF the functional alias de-activation response. +5. The MC service server informs all other MC service user(s) and/or users homed in the IWF sharing the same functional alias(es). + +### 10.14.3.5 User homed in the IWF takes over functional alias(es) within an MC system + +The procedure for the user homed to IWF takes over functional alias(es) within an MC system is illustrated in figure 10.14.3.5-1. + +During functional alias(es) activation, if the functional alias(es) is (are) already used by another MC service user(s), an authorized user homed in the IWF can get an offer to take over the functional alias(es) from the MC service user currently using the functional alias(es). + +Pre-conditions: + +1. MC service client 1 has performed the functional alias(es) activation procedure. +2. As result of the functional alias(es) activation procedure, the user homed in the IWF is aware which functional alias(es) are already used but can be taken over. +3. The user homed in the IWF decides to take over a functional alias. + +![Sequence diagram illustrating the IWF functional alias taking over procedure within an MC system. The diagram shows four lifelines: IWF, MC service server, MC service client 1, and Other MC service client(s). The sequence of messages is: 1. IWF functional alias take over request (IWF to MC service server); 2. Authorization check based on functional alias(es) policy, user subscription etc. (internal to MC service server); 3. Functional alias revoke notification (MC service server to MC service client 1); 4. Store functional alias(es) status (internal to MC service server); 5. IWF functional alias(es) take over response (MC service server to IWF); 6. Functional alias(es) status notification (MC service server to Other MC service client(s)); 7. IWF functional alias(es) status notification (MC service server to IWF).](04f1a971a602ced3c6096d46de1cf29c_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC service server + participant MC service client 1 + participant Other MC service client(s) + + Note right of MC service server: 2. Authorization check based on functional alias(es) policy, user subscription etc. + Note right of MC service server: 4. Store functional alias(es) status + + IWF->>MC service server: 1. IWF functional alias take over request + MC service server-->>MC service client 1: 3. Functional alias revoke notification + MC service server-->>IWF: 5. IWF functional alias(es) take over response + MC service server-->>Other MC service client(s): 6. Functional alias(es) status notification + MC service server-->>IWF: 7. IWF functional alias(es) status notification + +``` + +Sequence diagram illustrating the IWF functional alias taking over procedure within an MC system. The diagram shows four lifelines: IWF, MC service server, MC service client 1, and Other MC service client(s). The sequence of messages is: 1. IWF functional alias take over request (IWF to MC service server); 2. Authorization check based on functional alias(es) policy, user subscription etc. (internal to MC service server); 3. Functional alias revoke notification (MC service server to MC service client 1); 4. Store functional alias(es) status (internal to MC service server); 5. IWF functional alias(es) take over response (MC service server to IWF); 6. Functional alias(es) status notification (MC service server to Other MC service client(s)); 7. IWF functional alias(es) status notification (MC service server to IWF). + +**Figure 10.14.3.5-1: IWF functional alias taking over procedure within an MC system** + +1. The user homed in the IWF requests the MC service server to take over a functional alias by sending an IWF functional alias take over request. +2. The MC service server checks if there are any conflicts taking over the functional alias. +3. If the user homed in the IWF is authorised to take over the requested functional alias then the MC service server sends a functional alias revoke notification to inform MC service client 1 that the functional alias has been revoked and is not any longer active for the user of MC service client 1. + +**Editor's note:** How the MC service server checks the authorization of the IWF to perform functional alias related actions is FFS. + +4. The MC service server stores the functional alias status of the requested functional alias. +5. MC service server sends an IWF functional alias take over response to the user homed in the IWF. +6. The MC service server informs all other MC service user(s) sharing the same functional alias, of the take over by sending a functional alias status notification. +7. The MC service server informs all user(s) homed in the IWF sharing the same functional alias of the take over by sending an IWF functional alias status notification. + +## 10.15 First-to-answer call setup + +### 10.15.1 Description + +The present document specifies the interworking between LMR users and MCPTT clients for first-to-answer calls. It can be used based on MCPTT IDs, or based on functional alias for interworking with alternative addressing scheme used by the LMR system. + +### 10.15.2 Information flows for first-to-answer call + +#### 10.15.2.1 IWF first-to-answer call request + +Table 10.15.2.1-1 describes the information flow IWF first-to-answer call request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.15.2.1-1: IWF first-to-answer call 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 | +| 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. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Location information | O | Location of the calling party | +| NOTE: One of these information elements must be present. If the information element MCPTT ID is present, it may consist of a set of MCPTT IDs. If the information element functional alias is present it must consist of a single functional alias. | | | + +## 10.15.2.2 IWF first-to-answer call response + +Table 10.15.2.2-1 describes the information flow IWF first-to-answer call response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.15.2.2-1: IWF first-to-answer call 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 | M | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| SDP answer | M | Media parameters selected | + +## 10.15.2.3 IWF first-to-answer call cancel request + +Table 10.15.2.3-1 describes the information flow IWF first-to-answer call cancel request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.15.2.3-1: IWF first-to-answer call cancel 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 | + +## 10.15.2.4 IWF first-to-answer call cancel response + +Table 10.15.2.4-1 describes the information flow IWF first-to-answer call cancel response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.15.2.4-1: MCPTT first-to-answer call cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------| +| MCPTT ID | M | The MCPTT ID of the called party | + +## 10.15.3 Procedures + +### 10.15.3.1 MCPTT user initiating a first-to-answer call + +In this procedure, an MCPTT user is initiating an MCPTT first-to-answer call for communicating with an LMR user via an IWF. + +Pre-conditions: + +1. The calling MCPTT user has selected first-to-answer call. +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for MCPTT first-to-answer call initiated by MCPTT user. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT first-to-answer call request from client to server; 2. Authorize request from server to IWF; 3. IWF first-to-answer call request from server to IWF; 4. IWF first-to-answer call response from IWF to server; 5. MCPTT first-to-answer call response from server to client; 6. Media plane established (indicated by a horizontal bar across all lifelines).](cad41f28af38bf1707891b7ab8746331_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note right of MCPTT server: Authorize request + MCPTT client->>MCPTT server: 1. MCPTT first-to-answer call request + MCPTT server->>IWF: 2. Authorize request + MCPTT server->>IWF: 3. IWF first-to-answer call request + IWF-->>MCPTT server: 4. IWF first-to-answer call response + MCPTT server-->>MCPTT client: 5. MCPTT first-to-answer call response + Note over MCPTT client, MCPTT server, IWF: 6. Media plane established + +``` + +Sequence diagram for MCPTT first-to-answer call initiated by MCPTT user. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT first-to-answer call request from client to server; 2. Authorize request from server to IWF; 3. IWF first-to-answer call request from server to IWF; 4. IWF first-to-answer call response from IWF to server; 5. MCPTT first-to-answer call response from server to client; 6. Media plane established (indicated by a horizontal bar across all lifelines). + +**Figure 10.15.3.1-1: MCPTT first-to-answer call initiated by MCPTT user** + +1. The MCPTT user at the MCPTT client initiates an MCPTT first-to-answer call. The MCPTT client sends an MCPTT first-to-answer call request towards the MCPTT server. The MCPTT first-to-answer call request contains the MCPTT ID corresponding to the calling MCPTT party and called LMR party, and an SDP offer containing one or more media types. The called LMR party can consist of a set of potential target recipients represented by their MCPTT IDs, or a functional alias. The following parameters are also included that describe the MCPTT client's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not); + - an indication of whether the MCPTT client is requesting the floor, and if the MCPTT client is requesting the floor, and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). + +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the first-to-answer call. The MCPTT server checks whether the provided functional alias of the calling user, if present, can be used and has been activated for the MCPTT user. +3. If authorized, the MCPTT server sends the IWF first-to-answer call request that may or may not include location of the requestor, depending on the outcome of the privacy check towards the IWF, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + +NOTE: How the IWF first-to-answer call request is forwarded to the LMR system is out of scope of the present document. + +4. The IWF sends an IWF first-to-answer call response to the MCPTT server, indicating that the IWF does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3. +5. The MCPTT server forwards the MCPTT first-to-answer call response to the MCPTT client. If the result parameter indicates success, then the MCPTT client proceeds to step 6. Otherwise, if the parameters returned in the MCPTT first-to-answer call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT first-to-answer call request with the new parameters and behaves according to those parameters. The calling MCPTT user may be notified of the change in parameters, for example, that the call is to be without floor control. The MCPTT user can choose to end the call rather than continue with the new parameters. If the parameters returned are not acceptable to the MCPTT client, then the call fails. +6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +### 10.15.3.2 LMR user initiating a first-to-answer call + +In this procedure, an MCPTT user is initiating an MCPTT first-to-answer call for communicating with an LMR user via an IWF. + +Pre-conditions: + +1. The calling LMR user has selected first-to-answer call +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for MCPTT first-to-answer call initiated by MCPTT user. The diagram shows interactions between IWF, MCPTT server, and MCPTT client. The sequence is: 1. IWF sends first-to-answer call request to MCPTT server; 2. MCPTT server sends authorize request to IWF; 3. MCPTT server sends first-to-answer call request to MCPTT client; 4. MCPTT client sends first-to-answer call response to MCPTT server; 5. MCPTT server sends first-to-answer call response to IWF; 6. Media plane is established between IWF and MCPTT client.](114a0aef3954cf8b22aa8e081fe1061d_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_server: 2. Authorize request + IWF->>MCPTT_server: 1. IWF first-to-answer call request + MCPTT_server->>IWF: 2. Authorize request + MCPTT_server->>MCPTT_client: 3. MCPTT first-to-answer call request + MCPTT_client->>MCPTT_server: 4. MCPTT first-to-answer call response + MCPTT_server->>IWF: 5. IWF first-to-answer call response + Note over IWF, MCPTT_client: 6. Media plane established + +``` + +Sequence diagram for MCPTT first-to-answer call initiated by MCPTT user. The diagram shows interactions between IWF, MCPTT server, and MCPTT client. The sequence is: 1. IWF sends first-to-answer call request to MCPTT server; 2. MCPTT server sends authorize request to IWF; 3. MCPTT server sends first-to-answer call request to MCPTT client; 4. MCPTT client sends first-to-answer call response to MCPTT server; 5. MCPTT server sends first-to-answer call response to IWF; 6. Media plane is established between IWF and MCPTT client. + +Figure 10.15.3.2-1: MCPTT first-to-answer call initiated by MCPTT user + +1. The IWF sends an IWF first-to-answer call request towards the MCPTT server. The IWF first-to-answer call request contains the MCPTT ID corresponding to the calling LMR party and called MCPTT party, and an SDP offer containing one or more media types. The called MCPTT party can consist of a set of potential target recipients represented by their MCPTT IDs, or a functional alias. The following parameters are also included that describe the LMR party's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not); + - an indication of whether the LMR user is requesting the floor, and if the LMR user is requesting the floor, and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to receive the first-to-answer call. The MCPTT server checks whether the provided functional alias of the calling user, if present, can be used and has been activated for the LMR user. +3. If authorized, the MCPTT server sends the MCPTT first-to-answer call request towards the MCPTT client, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. +4. The MCPTT client sends an MCPTT first-to-answer call response to the MCPTT server, indicating that the MCPTT client does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3. +5. The MCPTT server sends the IWF first-to-answer call response to the IWF offering the same media type as that sent in step 4. If the parameters returned are not acceptable to the IWF, then the call fails. If the parameters returned in the IWF private call response are different but acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters starting with step 1, which is to essentially restart the call. If there is no change of parameter, then the call proceeds to step 6. +6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +## 10.16 Enhanced status + +### 10.16.1 General + +3GPP TS 23.282 [6] clause 7.9 describes a high-level procedure to provide enhanced status information to all the receiving MCData users. + +### 10.16.2 Preset values for enhanced status + +The configuration of preset values into the group configuration data is described in 3GPP TS 23.282 [6] clause 7.9.2. + +### 10.16.3 Enhanced status for on-network + +#### 10.16.3.1 Procedure (MCData to IWF) + +The procedure for an MCData user requesting to share enhanced status to an MCData group is as specified in 3GPP TS 23.282 [6] clause 7.9.3 for the enhanced status for on-network use; one or more users using MCData clients 2-n may be LMR users behind an IWF that has affiliated to the MCData group (see clause 10.1.2 of the present document). The IWF behaves as a peer MCData server. + +### 10.16.3.2 Procedure (IWF to MCData) + +The procedure for an IWF requesting, on behalf of an LMR user, to share enhanced status to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.9.3 for the enhanced status for on-network use, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see clause 10.1.2 of the present document). The IWF behaves as a peer MCData server to other MCData servers. + +## Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2017-06 | - | - | - | - | - | TS template | | 0.0.0 | +| 2017-07 | SA6#18 | | | | | Implementation of the following p-CRs approved by SA6:
S6-170920, S6-170976, S6-170977, S6-170978, S6-170979,
S6-170981, S6-171013, S6-171016, S6-171019, S6-171065,
S6-171066, S6-171067, S6-171068, S6-171069, S6-171070,
S6-171071 and S6-171072. | | 0.1.0 | +| 2017-10 | SA6#19 | | | | | Implementation of the following p-CRs approved by SA6:
S6-171310, S6-171311, S6-171321, S6-171325, S6-171376,
S6-171420, S6-171421, S6-171423, S6-171424, S6-171427,
S6-171428, S6-171429, S6-171430, S6-171431, S6-171433,
S6-171434, S6-171460, S6-171461, S6-171462 and S6-171489. | | 0.2.0 | +| 2017-12 | SA6#20 | | | | | Implementation of the following p-CRs approved by SA6:
S6-171511, S6-171533, S6-171614, S6-171723, S6-171724,
S6-171725, S6-171726, S6-171727, S6-171728, S6-171733,
S6-171735, S6-171738, S6-171740, S6-171741, S6-171749,
S6-171751, S6-171797, S6-171801, S6-171802, S6-171803,
S6-171806, S6-171808, S6-171809, S6-171827, S6-171828,
S6-171853, S6-171854, S6-171875 | | 0.3.0 | +| 2017-12 | SA6#20 | | | | | Rapporteur's editorial changes | | 0.3.1 | +| 2017-12 | SA#78 | SP-170902 | | | | Submitted to SA#78 for information | | 1.0.0 | +| 2018-01 | SA6#21 | | | | | Implementation of the following p-CRs approved by SA6:
S6-180055, S6-180108, S6-180109, S6-180171, S6-180175,
S6-180190, S6-180199, S6-180200, S6-180214 | | 1.1.0 | +| 2018-02 | | | | | | Editorial changes | | 1.1.1 | +| 2018-03 | SA6#22 | | | | | Implementation of the following p-CRs approved by SA6:
S6-180248, S6-180347, S6-180358, S6-180361, S6-180362,
S6-180363, S6-180364, S6-180374, S6-180390, S6-180440,
S6-180442, S6-180444, S6-180446, S6-180447, S6-180449,
S6-180450, S6-180451, S6-180452, S6-180453, S6-180454,
S6-180461, S6-180462, S6-180481, S6-180491. | | 1.2.0 | +| 2018-03 | | | | | | Editorial fixes, missing LMR abbreviation from S6-180364. | | 1.2.1 | +| 2018-03 | SA#79 | SP-180159 | | | | Submitted for approval at SA#79 | | 2.0.0 | +| 2018-04 | SA#79 | SP-180159 | | | | MCC Editorial update for publication after TSG SA approval (SA#79) | | 15.0.0 | +| 2018-06 | SA#80 | SP-180372 | 0001 | 2 | F | Flow name update from MCPTT call end to MCPTT private call end | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0002 | 1 | F | Corrections to Imminent peril group call initiated by MCPTT user | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0003 | 2 | F | Corrections to Imminent peril group call initiated by LMR user | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0004 | | F | Corrections to Imminent peril cancel | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0005 | 3 | F | Corrections to chat group call procedures and information flows | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0006 | 1 | F | Alignment of terminology emergency and imminent peril | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0007 | 1 | F | Alignment of terminology - pre-arranged group call | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0008 | 1 | F | IWF actions on Imminent peril group calls | | 15.1.0 | +| 2018-06 | SA#80 | SP-180372 | 0009 | 1 | F | Corrections to emergency group call procedures | | 15.1.0 | +| 2018-09 | SA#81 | SP-180673 | 0017 | 2 | F | IWF SDS fix | | 15.2.0 | +| 2018-09 | SA#81 | SP-180679 | 0014 | 1 | F | IWF affiliation auth update | | 16.0.0 | +| 2018-09 | SA#81 | SP-180679 | 0015 | 1 | F | IWF broadcast call fixes | | 16.0.0 | +| 2018-09 | SA#81 | SP-180679 | 0016 | 1 | F | IWF alert cancel alignment | | 16.0.0 | +| 2018-12 | SA#82 | SP-181179 | 0019 | | F | IWF group call request broadcast indicator correction | | 16.1.0 | +| 2018-12 | SA#82 | SP-181179 | 0021 | 2 | C | Add Implicit floor request to IWF group call request and IWF imminent peril group call request | | 16.1.0 | +| 2018-12 | SA#82 | SP-181179 | 0022 | | C | Add Location information to IWF floor request and IWF floor taken messages | | 16.1.0 | +| 2019-03 | SA#83 | SP-190076 | 0023 | 1 | F | MCPTT ID in interworking floor control | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0024 | 2 | C | IWF alignment for talker location in requests for Group call and Group-broadcast group call setup | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0025 | 1 | C | IWF alignment for talker location in Chat group | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0026 | 2 | C | IWF alignment for talker location in Private call | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0027 | 1 | C | IWF alignment for talker Location related to Imminent peril groups | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0028 | 1 | C | IWF alignment for current talker location | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0029 | 2 | C | TS 23.379 alignment for late join | | 16.2.0 | +| 2019-03 | SA#83 | SP-190076 | 0030 | 2 | B | Analogue FM interworking | | 16.2.0 | +| 2019-06 | SA#84 | SP-190487 | 0033 | 1 | C | 23.283 location with implicit floor request | | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0035 | 2 | B | Functional Alias management for interworking between MC service system and LMR system | | 16.3.0 | +| 2019-09 | SA#85 | SP-190728 | 0038 | 4 | B | IWF preconfigured groups | | 16.4.0 | +| 2019-09 | SA#85 | SP-190728 | 0039 | 4 | B | IWF add user to temporary pre-configured group regroup | | 16.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| 2019-09 | SA#85 | SP-190728 | 0041 | 2 | B | IWF temporary group calls | 16.4.0 | +| 2019-09 | SA#85 | SP-190728 | 0042 | 4 | B | IWF user regroup with pre-configured group | 16.4.0 | +| 2019-09 | SA#85 | SP-190728 | 0044 | 4 | B | IWF preconfigured broadcast group calls | 16.4.0 | +| 2019-09 | SA#85 | SP-190728 | 0045 | 2 | B | IWF preconfigured broadcast group calls | 16.4.0 | +| 2019-09 | SA#85 | SP-190728 | 0047 | 1 | F | IWF identities wording correction | 16.4.0 | +| 2019-09 | SA#85 | SP-190728 | 0051 | 1 | F | Remove 10.5.2.17 Editor's Note | 16.4.0 | +| 2019-09 | SA#85 | SP-190735 | 0036 | 2 | B | Functional alias for private call interworking between an MC service system and an LMR system | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0037 | 2 | B | Functional alias for floor control interworking between MC service system and LMR system | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0046 | 2 | B | IWF functional alias restoration | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0048 | 2 | B | Add first-to-answer for interworking with GSM-R | 17.0.0 | +| 2019-09 | SA#85 | SP-190735 | 0050 | 1 | B | Add enhancements for interworking of MCData SDS with GSM-R SMS | 17.0.0 | +| 2019-12 | SA#86 | SP-191113 | 0049 | 3 | B | Add enhancements for interworking of MCPTT group calls with GSM-R | 17.1.0 | +| 2019-12 | SA#86 | SP-191113 | 0052 | 1 | F | Text improvements related to functional alias interworking | 17.1.0 | +| 2020-09 | SA#89 | SP-200838 | 0054 | 1 | A | Interworking private call floor control | 17.2.0 | +| 2020-09 | SA#89 | SP-200846 | 0055 | 1 | C | Implicit affiliation and interworking | 17.2.0 | +| 2021-12 | SA#94 | SP-211520 | 0057 | | A | Correction to Disposition Notification handling when LMR system temporarily disables Disposition Notification | 17.3.0 | +| 2021-12 | SA#94 | SP-211527 | 0059 | 2 | F | Correction of Enhanced Status description | 17.3.0 | +| 2022-06 | SA#96 | SP-220476 | 0061 | | F | Corrections to the use of MC service system | 18.0.0 | +| 2023-03 | SA#99 | SP-230287 | 0066 | 2 | B | LMR-3GPP Location Interworking | 18.1.0 | +| 2023-03 | SA#99 | SP-230290 | 0067 | 1 | F | Correction on optional use of Non-3GPP security message response | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23682/raw.md b/raw/rel-18/23_series/23682/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..93d8431a322e55f99a8dfb55f9402c2ee8ea5018 --- /dev/null +++ b/raw/rel-18/23_series/23682/raw.md @@ -0,0 +1,4822 @@ + + +# 3GPP TS 23.682 V18.0.0 (2023-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and 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, black, stylized font. Below 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 ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 Architecture Model and Concepts..... | 11 | +| 4.1 General Concept..... | 11 | +| 4.2 Architectural Reference Model ..... | 11 | +| 4.3 Reference points..... | 16 | +| 4.3.1 General ..... | 16 | +| 4.3.2 List of Reference Points ..... | 17 | +| 4.3.3 Reference Point Requirements ..... | 17 | +| 4.3.3.1 Tsp Reference Point Requirements..... | 17 | +| 4.3.3.2 T4 Reference Point Requirements ..... | 18 | +| 4.3.3.3 Void ..... | 18 | +| 4.3.3.4 S6m Reference Point Requirements ..... | 18 | +| 4.3.3.5 S6n Reference Point Requirements ..... | 18 | +| 4.3.3.6 T6a/T6b Reference Point Requirements..... | 18 | +| 4.3.3.7 S6t Reference Point Requirements ..... | 19 | +| 4.3.3.8 T6ai/T6bi Reference Point Requirements..... | 19 | +| 4.3.3.9 T7 Reference Point Requirements ..... | 19 | +| 4.3.3.10 Ns Reference Point Requirements ..... | 19 | +| 4.3.3.11 Nu Reference Point Requirements..... | 19 | +| 4.3.3.12 T8 Reference Point Requirements ..... | 20 | +| 4.3.3.13 T9a/T9b Reference Point Requirements..... | 20 | +| 4.4 Network Elements ..... | 20 | +| 4.4.1 General ..... | 20 | +| 4.4.2 MTC-IWF..... | 20 | +| 4.4.3 HSS/HLR..... | 21 | +| 4.4.4 GGSN/P-GW ..... | 22 | +| 4.4.5 SGSN/MME/MSC..... | 22 | +| 4.4.6 SMS-SC ..... | 22 | +| 4.4.7 MTC AAA..... | 23 | +| 4.4.8 Service Capability Exposure Function ..... | 23 | +| 4.4.9 Interworking SCEF..... | 25 | +| 4.4.10 RAN Congestion Awareness Function..... | 25 | +| 4.4.11 Packet Flow Description Function ..... | 25 | +| 4.4.12 UE radio Capabilities Management Function ..... | 25 | +| 4.5 High Level Function..... | 26 | +| 4.5.1 Device Triggering Function ..... | 26 | +| 4.5.2 PS-only Service Provision..... | 26 | +| 4.5.3 Core Network assisted RAN parameters tuning..... | 26 | +| 4.5.4 UE Power Saving Mode ..... | 26 | +| 4.5.5 Group Message Delivery..... | 28 | +| 4.5.6 Monitoring Events ..... | 28 | +| 4.5.6.1 General..... | 28 | +| 4.5.6.2 Monitoring Events via HSS and MME/SGSN ..... | 29 | +| 4.5.6.3 Monitoring Events via PCRF..... | 29 | +| 4.5.6.4 Void ..... | 30 | +| 4.5.7 High latency communication..... | 30 | +| 4.5.8 Support of informing about potential network issues..... | 31 | +| 4.5.9 Resource management of background data transfer..... | 31 | +| 4.5.10 E-UTRAN network resource optimizations based on communication patterns provided to the MME..... | 31 | +| 4.5.11 Support of setting up an AS session with required QoS ..... | 32 | + +| | | | +|------------|---------------------------------------------------------------------------|----| +| 4.5.12 | Change the chargeable party at session set-up or during the session ..... | 32 | +| 4.5.13 | Extended idle mode DRX..... | 32 | +| 4.5.13.1 | General..... | 32 | +| 4.5.13.2 | Paging for extended idle mode DRX in UTRAN ..... | 33 | +| 4.5.13.3 | Paging for extended idle mode DRX in E-UTRAN ..... | 34 | +| 4.5.13.3.0 | General ..... | 34 | +| 4.5.13.3.1 | Hyper SFN, Paging Hyperframe and Paging Time Window length ..... | 34 | +| 4.5.13.3.2 | Loose Hyper SFN synchronization ..... | 35 | +| 4.5.13.3.3 | MME paging and paging retransmission strategy..... | 35 | +| 4.5.14 | Non-IP Data Delivery (NIDD) ..... | 35 | +| 4.5.14.1 | General..... | 35 | +| 4.5.14.2 | Enhancements for reliable delivery of NIDD ..... | 36 | +| 4.5.14.3 | Reliable Data Service..... | 36 | +| 4.5.15 | Support of PFD management via SCEF ..... | 37 | +| 4.5.16 | MSISDN-less MO-SMS via T4..... | 37 | +| 4.5.17 | Enhanced Coverage Restriction Control via SCEF ..... | 37 | +| 4.5.18 | MBMS user service for UEs using power saving functions..... | 37 | +| 4.5.19 | Enhancements to Location Services for CIoT ..... | 39 | +| 4.5.20 | MBMS user service for NB or M UE categories ..... | 39 | +| 4.5.21 | Network Parameter Configuration via SCEF ..... | 40 | +| 4.5.22 | RACS information provisioning..... | 40 | +| 4.5.23 | Support of satellite access ..... | 40 | +| 4.6 | Identifiers ..... | 41 | +| 4.6.1 | General ..... | 41 | +| 4.6.2 | External Identifier..... | 41 | +| 4.6.3 | External Group Identifier ..... | 41 | +| 4.7 | Addressing..... | 41 | +| 4.8 | Security Aspects..... | 42 | +| 4.8.1 | Security Requirements..... | 42 | +| 4.8.1.0 | General..... | 42 | +| 4.8.1.1 | Void ..... | 42 | +| 4.8.1.2 | Void ..... | 42 | +| 4.9 | SCEF - SCS/AS API Procedures ..... | 42 | +| 4.9.1 | General ..... | 42 | +| 4.9.2 | Common Parameters ..... | 42 | +| 4.10 | Charging Principles ..... | 42 | +| 5 | Functional Description and Information Flow ..... | 43 | +| 5.1 | Control and user plane..... | 43 | +| 5.1.1 | Control Plane ..... | 43 | +| 5.1.1.1 | HSS – MTC-IWF..... | 43 | +| 5.2 | Device triggering procedures ..... | 44 | +| 5.2.1 | Device triggering procedure over Tsp..... | 44 | +| 5.2.2 | Trigger Delivery using T4 ..... | 45 | +| 5.2.3 | Device triggering recall/replace procedures ..... | 46 | +| 5.2.3.1 | Device trigger recall/replace procedure over Tsp..... | 46 | +| 5.2.3.2 | Replace procedure for trigger delivery using T4 ..... | 48 | +| 5.2.3.3 | Recall procedure for trigger delivery using T4..... | 49 | +| 5.3 | Information Storage..... | 50 | +| 5.3.0 | General ..... | 50 | +| 5.3.1 | Trigger Information in SMS-SC (Triggering with T4) ..... | 50 | +| 5.3.2 | SCEF..... | 50 | +| 5.4 | Security Procedures..... | 51 | +| 5.4.0 | General ..... | 51 | +| 5.4.1 | Void ..... | 51 | +| 5.4.2 | Void ..... | 51 | +| 5.5 | Group message delivery procedures ..... | 52 | +| 5.5.1 | Group message delivery using MBMS..... | 52 | +| 5.5.2 | Modification of previously submitted Group message ..... | 55 | +| 5.5.3 | Group Message Delivery via unicast MT NIDD..... | 56 | +| 5.6 | Monitoring Procedures ..... | 57 | +| 5.6.0 | Common Parameters ..... | 57 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------|----| +| 5.6.1 | Monitoring Event configuration and deletion via HSS ..... | 58 | +| 5.6.1.1 | Configuration Procedure ..... | 58 | +| 5.6.1.2 | Void ..... | 62 | +| 5.6.1.3 | Specific Parameters for Monitoring Event: Loss of connectivity ..... | 62 | +| 5.6.1.4 | Specific Parameters for Monitoring Event: UE reachability ..... | 64 | +| 5.6.1.5 | Specific Parameters for Monitoring Event: Location Reporting ..... | 66 | +| 5.6.1.6 | Specific Parameters for Monitoring Event: Change of IMSI-IMEI(SV) Association ..... | 67 | +| 5.6.1.7 | Specific Parameters for Monitoring Event: Roaming Status ..... | 67 | +| 5.6.1.8 | Specific Parameters for Monitoring Event: Communication failure ..... | 68 | +| 5.6.1.9 | Specific Parameters for Monitoring Event: Availability after DDN Failure ..... | 68 | +| 5.6.1.10 | Specific Parameters for Monitoring Event: PDN Connectivity Status ..... | 68 | +| 5.6.2 | Monitoring Events configuration and deletion directly at the MME/SGSN ..... | 69 | +| 5.6.2.1 | Configuration Procedure ..... | 69 | +| 5.6.2.2 | Void ..... | 70 | +| 5.6.2.3 | Specific Steps for Monitoring Event: Number of UEs present in a geographic area ..... | 70 | +| 5.6.3 | Reporting of Monitoring Events from the HSS or the MME/SGSN ..... | 71 | +| 5.6.3.1 | Reporting Procedure ..... | 71 | +| 5.6.3.2 | Reporting Event: Loss of connectivity ..... | 73 | +| 5.6.3.3 | Reporting Event: UE reachability ..... | 74 | +| 5.6.3.4 | Reporting Event: Location Reporting ..... | 74 | +| 5.6.3.5 | Reporting Event: Change of IMSI-IMEISV association ..... | 74 | +| 5.6.3.6 | Reporting Event: Roaming Status ..... | 74 | +| 5.6.3.7 | Reporting Event: Communication failure ..... | 75 | +| 5.6.3.8 | Reporting Event: Availability after DDN failure ..... | 75 | +| 5.6.3.9 | Reporting Event: PDN Connectivity Status ..... | 75 | +| 5.6.4 | Monitoring events configuration and reporting via PCRF ..... | 75 | +| 5.6.4.1 | Request of monitoring event reporting ..... | 75 | +| 5.6.4.1a | Request of monitoring event reporting for a group of UEs ..... | 76 | +| 5.6.4.2 | Common Parameters of the request reporting procedure ..... | 78 | +| 5.6.4.3 | Specific Parameters for Monitoring Event: Location Reporting ..... | 78 | +| 5.6.4.4 | Specific Parameters for Monitoring Event: Communication Failure ..... | 79 | +| 5.6.5 | Reporting of Monitoring Events from the PCRF ..... | 79 | +| 5.6.6 | Monitoring Event configuration and deletion via HSS for roaming scenarios using an IWK-SCEF ..... | 80 | +| 5.6.6.1 | Configuration Procedure ..... | 80 | +| 5.6.6.2 | Void ..... | 82 | +| 5.6.6.3 | Specific Parameters for Monitoring Event: Loss of connectivity ..... | 82 | +| 5.6.6.4 | Specific Parameters for Monitoring Event: UE reachability ..... | 82 | +| 5.6.6.5 | Specific Parameters for Monitoring Event: Location Reporting ..... | 83 | +| 5.6.6.6 | Specific Parameters for Monitoring Event: Change of IMSI-IMEI(SV) Association ..... | 83 | +| 5.6.6.7 | Specific Parameters for Monitoring Event: Roaming Status ..... | 83 | +| 5.6.6.8 | Specific Parameters for Monitoring Event: Communication failure ..... | 83 | +| 5.6.6.9 | Specific Parameters for Monitoring Event: Availability after DDN Failure ..... | 84 | +| 5.6.7 | Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios ..... | 84 | +| 5.6.8 | Reporting of Monitoring Events from the HSS or the MME/SGSN for roaming scenarios ..... | 84 | +| 5.6.8.1 | Reporting Procedure ..... | 84 | +| 5.6.8.2 | Reporting Event: Loss of connectivity ..... | 86 | +| 5.6.8.3 | Reporting Event: UE reachability ..... | 86 | +| 5.6.8.4 | Reporting Event: Location Reporting ..... | 86 | +| 5.6.8.5 | Reporting Event: Change of IMSI-IMEI(SV) association ..... | 86 | +| 5.6.8.6 | Reporting Event: Roaming Status ..... | 86 | +| 5.6.8.7 | Reporting Event: Communication failure ..... | 86 | +| 5.6.8.8 | Reporting Event: Availability after DDN failure ..... | 87 | +| 5.6.8.9 | Reporting Event: PDN Connectivity Status ..... | 87 | +| 5.6.9 | Network-initiated Explicit Monitoring Event Deletion Procedure ..... | 87 | +| 5.7 | High latency communications procedures ..... | 88 | +| 5.7.1 | Availability Notification after DDN Failure ..... | 88 | +| 5.7.1.1 | General ..... | 88 | +| 5.7.1.2 | Event Configuration ..... | 88 | +| 5.7.1.3 | Notification ..... | 89 | +| 5.7.2 | Notification using Monitoring Event "UE Reachability" ..... | 91 | +| 5.8 | Procedure for Informing about Potential Network Issues ..... | 91 | +| 5.8.1 | General ..... | 91 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------|------------| +| 5.8.2 | Request procedure for one-time or continuous reporting of network status ..... | 92 | +| 5.8.3 | Report procedure for continuous reporting of network status ..... | 93 | +| 5.8.4 | Removal procedure for continuous reporting of network status ..... | 94 | +| 5.9 | Procedure for resource management of background data transfer ..... | 95 | +| 5.10 | Communication Pattern parameters provisioning procedure ..... | 97 | +| 5.10.1 | Communication Pattern parameters ..... | 97 | +| 5.10.2 | Communication Pattern parameters provisioning to the MME ..... | 98 | +| 5.11 | Setting up an AS session with required QoS procedure ..... | 99 | +| 5.12 | Change the chargeable party at session set-up or during the session procedure ..... | 101 | +| 5.12.1 | Set the chargeable party at session set-up ..... | 101 | +| 5.12.2 | Change the chargeable party during the session ..... | 102 | +| 5.13 | Non-IP Data Delivery procedures ..... | 103 | +| 5.13.1 | T6a/T6b Connection Establishment ..... | 103 | +| 5.13.1.1 | General ..... | 103 | +| 5.13.1.2 | T6a/T6b Connection Establishment Procedure ..... | 103 | +| 5.13.2 | NIDD Configuration ..... | 104 | +| 5.13.3 | Mobile Terminated NIDD procedure ..... | 106 | +| 5.13.4 | Mobile Originated NIDD procedure ..... | 109 | +| 5.13.5 | T6a/T6b Connection Release ..... | 110 | +| 5.13.5.1 | General ..... | 110 | +| 5.13.5.2 | MME/SGSN Initiated T6a/T6b Connection Release procedure ..... | 111 | +| 5.13.5.3 | SCEF Initiated T6a/T6b Connection Release procedure ..... | 112 | +| 5.13.6 | Serving node relocation procedure over T6a/T6b ..... | 112 | +| 5.13.6.1 | General ..... | 112 | +| 5.13.6.2 | Successful TAU/RAU procedure with T6a/T6b ..... | 113 | +| 5.13.7 | Void ..... | 113 | +| 5.13.8 | NIDD Authorisation Update ..... | 113 | +| 5.14 | PFD management via SCEF ..... | 114 | +| 5.14.1 | Procedure for PFD management via SCEF ..... | 114 | +| 5.14.2 | PFD definition ..... | 115 | +| 5.15 | Procedure for MSISDN-less MO-SMS via T4 ..... | 116 | +| 5.16 | Procedure for Enhanced Coverage Restriction Control via SCEF ..... | 117 | +| 5.17 | Procedures for accessing MTC-IWF Functionality via SCEF ..... | 118 | +| 5.17.1 | Device triggering procedure via T8 ..... | 118 | +| 5.17.2 | Device triggering recall/replace procedures via T8 ..... | 119 | +| 5.17.3 | Procedure for MSISDN-less MO-SMS via T8 ..... | 120 | +| 5.18 | Procedure for Network Parameter Configuration via SCEF ..... | 121 | +| 5.19 | RACS information provisioning procedures ..... | 125 | +| 5.19.1 | General ..... | 125 | +| 5.19.2 | RACS information provisioning procedures via SCEF ..... | 125 | +| 5.19.3 | RACS information provisioning procedures via T9a ..... | 126 | +| Annex A (informative): | MTC Deployment Scenarios ..... | 127 | +| Annex B (informative): | Void ..... | 129 | +| Annex C (informative): | Triggering with OMA Push ..... | 130 | +| C.1 | General ..... | 130 | +| C.2 | Triggering flow using Service Loading ..... | 130 | +| Annex D (informative): | Device triggering using direct model over user plane ..... | 132 | +| Annex E (informative): | Change history ..... | 133 | + +# --- 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 specifies architecture enhancements to facilitate communications with packet data networks and applications (e.g. Machine Type Communication (MTC) applications on the (external) network/MTC servers) according to the use cases and service requirements defined in TS 22.368 [2], TS 22.101 [3], and related 3GPP requirements specifications. Both roaming and non-roaming scenarios are covered. + +The present document also specifies transmission of non-IP data via SCEF for the CIoT EPS Optimization. + +The present document also specifies the interface between the SCEF and the SCS/AS. + +The present document also specifies provisioning of UCMF with RACS information. + +# --- 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.368: "Service Requirements for Machine-Type Communications (MTC)". +- [3] 3GPP TS 22.101: "Service Aspects; Service Principles". +- [4] 3GPP TS 23.003: "Numbering, addressing and identification". +- [5] 3GPP TS 23.002: "Network architecture". +- [6] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [7] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [8] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)". +- [9] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3". +- [10] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [11] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [12] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [13] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2". +- [14] 3GPP TR 23.039: "Interface Protocols for the Connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs)". +- [15] IETF RFC 3588: "Diameter Base Protocol". +- [16] IETF RFC 4960: "Stream Control Transmission Protocol". + +- [17] WAP-168-ServiceLoad-20010731-a: "Service Loading". +- [18] OMA-TS-Push\_MO-V1\_0-20110809-A: "OMA Push Management Object". +- [19] OMA-TS-Push\_Message-V2\_2-20110809-A: "Push Message". +- [20] OMA-AD-Push-V2\_2-20110809-A: "Push Architecture". +- [21] 3GPP TS 23.221: "Architectural requirements". +- [22] Void. +- [23] 3GPP TS 23.142: "Value-added Services for SMS (VAS4SMS); Interface and signalling flow". +- [24] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)". +- [25] 3GPP TS 33.187: "Security aspects of Machine-Type and other mobile data applications Communications enhancements". +- [26] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [27] 3GPP TS 23.203: "Policy and charging control architecture". +- [28] 3GPP TS 32.240: "Charging architecture and principles". +- [29] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description". +- [30] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [31] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [32] OMA API Inventory: "". +- [33] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [34] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode". +- [35] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode". +- [36] 3GPP TS 23.012: "Location management procedures". +- [37] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications". +- [38] 3GPP TS 26.346: "MBMS: Protocols and Codecs". +- [39] 3GPP TS 32.278: "Monitoring event charging". +- [40] 3GPP TS 32.253: "Control Plane (CP) data transfer domain charging". +- [41] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities". +- [42] 3GPP TS 26.347: "Multimedia Broadcast/Multicast Service (MBMS); Application Programming Interface and URL". +- [43] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs". +- [44] 3GPP TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)". + +- [45] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [46] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [47] 3GPP TS 24.250: "Protocol for Reliable Data Service; Stage 3". +- [48] 3GPP TS 23.502: "Procedures for the 5G System (5GS), Stage 2". +- [49] 3GPP TS 29.675: "User Equipment (UE) radio capability provisioning service; Stage 3". +- [50] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [51] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. + +For the purposes of the present document, the following terms and definitions given in TS 23.401 [7] apply: + +RACS +WB-E-UTRAN +LTE-M + +## 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]. + +| | | +|------------|---------------------------------------------------| +| AS | Application Server | +| CDR | Charging Data Record | +| CDF | Charging Data Function | +| CGF | Charging Gateway Function | +| CIoT | Cellular Internet of Things | +| CP | Communication Pattern | +| DDN | Downlink Data Notification | +| IWK-SCEF | Interworking SCEF | +| MTC | Machine Type Communications | +| MTC-IWF | Machine Type Communications-InterWorking Function | +| NIDD | Non-IP Data Delivery | +| PCRF | Policy and Charging Rules Function | +| P-GW | PDN Gateway | +| PFD | Packet Flow Description Function | +| PSM | Power Saving Mode | +| SCEF | Service Capability Exposure Function | +| SCS | Services Capability Server | +| SLF | Subscriber Location Function | +| SME | Short Message Entities | +| SMS-SC | Short Message Service-Service Centre | +| SRI | Send Routing Information | +| UCMF | UE radio Capability Management Function | +| WB-E-UTRAN | Wide Band E-UTRAN | + +# 4 Architecture Model and Concepts + +## 4.1 General Concept + +The end-to-end communications, between the MTC Application in the UE and the MTC Application in the external network, uses services provided by the 3GPP system, and optionally services provided by a Services Capability Server (SCS). + +The MTC Application in the external network is typically hosted by an Application Server (AS) and may make use of an SCS for additional value added services. The 3GPP system provides transport, subscriber management and other communication services including various architectural enhancements motivated by, but not restricted to, MTC (e.g. control plane device triggering). + +Different models are foreseen for machine type of traffic in what relates to the communication between the AS and the 3GPP system (refer to Annex A) and based on the provider of the SCS. The different architectural models that are supported by the Architectural Reference Model in clause 4.2 include the following: + +- Direct Model - The AS connects directly to the operator network in order to perform direct user plane communications with the UE without the use of any external SCS. The Application in the external network may make use of services offered by the 3GPP system; +- Indirect Model - The AS connects indirectly to the operator network through the services of a SCS in order to utilize additional value added services for MTC (e.g. control plane device triggering). The SCS is either: + - MTC Service Provider controlled: The SCS is an entity that may include value added services for MTC, performing user plane and/or control plane communication with the UE. Tsp is regarded as an inter-domain interface for control plane communication; or + - 3GPP network operator controlled: The SCS is a mobile operator entity that may include value added services for MTC and performs user plane and/or control plane communication with the UE, making Tsp a control plane interface internal to the PLMN; +- Hybrid Model: The AS uses the direct model and indirect models simultaneously in order to connect directly to the operator's network to perform direct user plane communications with the UE while also using a SCS. From the 3GPP network perspective, the direct user plane communication from the AS and any value added control plane related communications from the SCS are independent and have no correlation to each other even though they may be servicing the same MTC Application hosted by the AS. + +When using the hybrid model, the MTC Service provider controlled SCS, and the 3GPP operator controlled SCS may offer different capabilities to the MTC Applications. + +Since the different models are not mutually exclusive, but just complementary, it is possible for a 3GPP operator to combine them for different applications. This may include a combination of both MTC Service Provider and 3GPP network operator controlled SCSs communicating with the same PLMN. + +## 4.2 Architectural Reference Model + +Figures 4.2-1a and 4.2-1b show the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN, WB-E-UTRAN, NB-IoT, GERAN, etc.) via the Um/Uu/LTE-Uu interfaces or satellite access interface for NB-IoT, WB-E-UTRAN and LTE-M. They also show the 3GPP network service capability exposure to SCS and AS. The architecture covers the various architectural models described in clause 4.1. + +![3GPP Architecture for Machine-Type Communication (non-roaming) diagram showing various network components and their interconnections.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +This diagram illustrates the 3GPP architecture for Machine-Type Communication (MTC) in a non-roaming scenario. It shows the flow of control and user plane data between various network elements. + +**Legend:** + +- Control plane: dashed line +- User plane: solid line +- API: dash-dot line + +**Network Components and Connections:** + +- MTC UE Application** is connected to the **UE**. +- UE** is connected to the **RAN** via the **Um/Uu/LTE-Uu** interface. +- RAN** is connected to the **MSC** (via **SGs** interface), **MME**, and **SGSN**. +- MSC** is connected to the **MME** (via **S6a** interface). +- MME** is connected to the **SGSN** (via **S4** interface). +- SGSN** is connected to the **S-GW** (via **S5** interface). +- S-GW** is connected to the **GGSN/P-GW** (via **S5** interface). +- GGSN/P-GW** is connected to the **IP-SM-GW** (via **S8** interface). +- IP-SM-GW** is connected to the **SMS-SC/GMSC/IWMSC** (via **Tsms** interface). +- SMS-SC/GMSC/IWMSC** is connected to the **SME** (via **Tsms** interface). +- SMS-SC/GMSC/IWMSC** is also connected to the **CDF/CGF** (via **T4** interface). +- CDF/CGF** is connected to the **HSS** (via **Rf/Ga** interface). +- HSS** is connected to the **MTC AAA** (via **S6n** interface). +- HSS** is also connected to the **MTC IWF** (via **S6m** interface). +- MTC IWF** is connected to the **SCEF** (via **Tsp** interface). +- SCEF** is connected to the **Services Capability Server (SCS)** (via **S6t** interface). +- Services Capability Server (SCS)** is connected to two **Application Server (AS)** units (via **T8** interface). +- GGSN/P-GW** is also connected to the **SCS** (via **G/SGi** interface). +- GGSN/P-GW** is also connected to two **Application Server (AS)** units (via **G/SGi** interface). + +**Models:** + +- Indirect Model (1) +- Direct Model (2) +- Hybrid Model (1 + 2) + +3GPP Architecture for Machine-Type Communication (non-roaming) diagram showing various network components and their interconnections. + +Figure 4.2-1a: 3GPP Architecture for Machine-Type Communication (non-roaming) + +![3GPP Architecture for Machine-Type Communication (Roaming) diagram showing various network components and interfaces between HPLMN and VPLMN.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the 3GPP architecture for Machine-Type Communication (MTC) during roaming. It is divided into two main network domains: the Home PLMN (HPLMN) and the Visited PLMN (VPLMN), separated by a dashed orange line. + +**Legend:** + +- Control plane: dashed line +- User plane: solid line +- API: dash-dot line + +**Components and Interfaces:** + +- UE (User Equipment):** Contains an 'MTC UE Application'. It connects to the **RAN** via the **Um/Uu/LTE-Uu** interface. +- RAN:** Connects to the **MSC** (via **SGs**), **MME** (via **T6ai**), and **SGSN** (via **T6bi**). +- MSC:** Connects to the **IP-SM-GW** (via **E**), **SMS-SC/GMSC/IWMSC** (via **SGd**), and **IWK-SCEF** (via **T7**). +- MME:** Connects to the **SGSN** (via **T7**). +- SGSN:** Connects to the **S-GW** (via **Gd**). +- S-GW:** Connects to the **GGSN/P-GW** (via **Gd**). +- GGSN/P-GW:** Connects to the **Services Capability Server (SCS)** (via **Gv/SGi**) and to an **Application Server (AS)** (via **Gv/SGi**). +- IP-SM-GW:** Connects to the **SMS-SC/GMSC/IWMSC** (via **Tsms**). +- SMS-SC/GMSC/IWMSC:** Connects to the **SME** (via **Tsms**), **CDF/CGF** (via **T4**), and **MTC-IWF** (via **Rf/Ga**). +- CDF/CGF:** Connects to the **HSS** (via **S6n**). +- HSS:** Connects to the **MTC AAA** (via **S6n**). +- MTC-IWF:** Connects to the **Services Capability Server (SCS)** (via **Tsp**). +- SCEF:** Connects to the **Services Capability Server (SCS)** (via **T8**). +- Services Capability Server (SCS):** Connects to two **Application Servers (AS)** (via **API**). +- Indirect Model:** Indicated by a circle with '1'. +- Direct Model:** Indicated by a circle with '2'. +- Hybrid Model:** Indicated by circles with '1' and '2'. + +3GPP Architecture for Machine-Type Communication (Roaming) diagram showing various network components and interfaces between HPLMN and VPLMN. + +Figure 4.2-1b: 3GPP Architecture for Machine-Type Communication (Roaming) + +Figure 4.2-2 shows the overall architecture for Service Capability Exposure which enables the 3GPP network to securely expose its services and capabilities provided by 3GPP network interfaces to external 3rd party service provider SCS/AS hosting an Application(s). + +![Diagram of 3GPP Architecture for Service Capability Exposure showing the Service Capability Exposure Function (SCEF) connected to various network entities and APIs for external SCS/AS connections.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the 3GPP Architecture for Service Capability Exposure. At the top, three 'SCS/AS' (Service Capability Exposure Function) entities are shown. Two are connected to 'Other SDOs' (Other Service Discovery and Operation) via a 'T8' interface. The third SCS/AS is connected to a central 'Service Capability Exposure Function' (SCEF) block. The SCEF block is connected to multiple APIs: 'API 1', 'API 2', 'API 3', '...', and 'API n'. These APIs are connected to various network entities through specific interfaces: 'S6t' to HSS, 'Rx, Nt' to PCRF, 'Nu' to PFDF, 'T6a/T6b' to MME/SGSN, 'xMB, MB2' to BM-SC, 'ISC' to S-CSCF, 'Ns' to RCAf, and '3GPP interface' to a Network Entity. A vertical double-headed arrow on the left is labeled 'TRUST DOMAIN', indicating the scope of the architecture. + +Diagram of 3GPP Architecture for Service Capability Exposure showing the Service Capability Exposure Function (SCEF) connected to various network entities and APIs for external SCS/AS connections. + +Figure 4.2-2: 3GPP Architecture for Service Capability Exposure + +![Figure 4.2-3: 3GPP roaming Architecture for Service Capability Exposure. The diagram is split into HPLMN (Home PLMN) and VPLMN (Visited PLMN) by a vertical dashed line. In the HPLMN, a Service Capability Exposure Function (SCEF) is connected to an HSS via the S6t interface and to a Network Entity via a 3GPP interface. In the VPLMN, an Interworking Service Capability Exposure Function (IWK-SCEF) is connected to an MME/SGSN via the T6ai/T6bi interface and to a Network Entity via a 3GPP interface. The SCEF and IWK-SCEF are connected to each other via the T7 interface.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 4.2-3: 3GPP roaming Architecture for Service Capability Exposure. The diagram is split into HPLMN (Home PLMN) and VPLMN (Visited PLMN) by a vertical dashed line. In the HPLMN, a Service Capability Exposure Function (SCEF) is connected to an HSS via the S6t interface and to a Network Entity via a 3GPP interface. In the VPLMN, an Interworking Service Capability Exposure Function (IWK-SCEF) is connected to an MME/SGSN via the T6ai/T6bi interface and to a Network Entity via a 3GPP interface. The SCEF and IWK-SCEF are connected to each other via the T7 interface. + +Figure 4.2-3: 3GPP roaming Architecture for Service Capability Exposure + +Figure 4.2-4 shows the overall architecture for RACS which enables provisioning of RACS database information in the 3GPP network. + +![Figure 4.2-4: 3GPP Architecture for RACS. This diagram shows the flow of RACS database information. A UE (User Equipment) is connected to a RAN (Radio Access Network) via the Uu interface. The RAN is connected to an MME via the S1 interface. The MME is connected to a UCMF (User Context Management Function) via the S17 interface. The UCMF is connected to an Application Server (AS) via the T9a interface. The UCMF is also connected to an SCEF (Service Capability Exposure Function) via the T9b interface. The SCEF is connected to a Services Capability Server (SCS) via the T8 interface. The SCS is connected to an Application Server (AS). A legend indicates that control plane interfaces are shown with a dashed line and dots, while API interfaces are shown with a dash-dot line.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +Figure 4.2-4: 3GPP Architecture for RACS. This diagram shows the flow of RACS database information. A UE (User Equipment) is connected to a RAN (Radio Access Network) via the Uu interface. The RAN is connected to an MME via the S1 interface. The MME is connected to a UCMF (User Context Management Function) via the S17 interface. The UCMF is connected to an Application Server (AS) via the T9a interface. The UCMF is also connected to an SCEF (Service Capability Exposure Function) via the T9b interface. The SCEF is connected to a Services Capability Server (SCS) via the T8 interface. The SCS is connected to an Application Server (AS). A legend indicates that control plane interfaces are shown with a dashed line and dots, while API interfaces are shown with a dash-dot line. + +Figure 4.2-4: 3GPP Architecture for RACS + +NOTE 1: Refer to TS 23.002 [5], TS 23.060 [6], TS 23.401 [7], TS 23.272 [11] and TS 23.040 [12] for the details of 3GPP network-internal reference points not specifically shown or labelled in figure 4.2-1a, figure 4.2-1b, figure 4.2-2, or described in this specification. + +NOTE 2: The SCS is controlled by the operator of the HPLMN or by a MTC Service Provider. + +NOTE 3: In the non-roaming case, all 3GPP network entities providing functionality for MTC are in the same PLMN. In the roaming case, 3GPP architecture for MTC supports both the home routed (illustrated in Figures 4.2-1a and 4.2-1b) and the local-breakout roaming (not illustrated) scenarios. For the home routed scenario, the MTC Server/Application User Plane communication is routed through the HPLMN. In the local breakout scenario, the User Plane communication is routed directly through the serving PLMN/VPLMN over deployed GGSN/P-GW. + +NOTE 4: Figure 4.2-2 does not include all the interfaces and network elements that may be connected to SCEF. + +NOTE 5: Figure 4.2-3 does not include all the interfaces and network elements that may be connected to an Interworking SCEF (IWK-SCEF). + +The SCS is an entity which connects to the 3GPP network to communicate with UEs used for MTC and the MTC-IWF and/or SCEF in the HPLMN. The SCS offers capabilities for use by one or multiple MTC Applications. A UE can host one or multiple MTC Applications. The corresponding MTC Applications in the external network are hosted on one or multiple ASs. + +Tsms is the interface that encompasses all the various proprietary SMS-SC to SME interface standards (see TR 23.039 [14]) and is outside the scope of 3GPP specifications. Tsms can be used to send a trigger to a UE encapsulated in a MT-SMS as an over-the-top application by any network entity (e.g. SCS) acting as a SME. Tsp is a 3GPP standardized interface to facilitate value-added services motivated by MTC (e.g. control plane device triggering) and provided by a SCS. + +T8 is the interface between the SCEF and the SCS/AS. SCEF exposed network services can be accessed by SCS/AS through APIs over T8 interface. In the indirect model, the SCS and the Application Server hosting Application(s) can be collocated. + +For the roaming scenario, the MTC-IWF shall have the connection with HSS and SMS-SC within the home network only as shown in the figure 4.2-1b. + +The Service Capability Exposure Function (SCEF) is the key entity within the 3GPP architecture for service capability exposure that provides a means to securely expose the services and capabilities provided by 3GPP network interfaces. In standalone MTC-IWF deployment, MTC-IWF functionality (e.g. T4 triggering) is made available to the SCS/AS via the Tsp interface. In certain deployments, the MTC-IWF may be co-located with the SCEF in which case MTC-IWF functionality is exposed to the SCS/AS via T8 interface (i.e. API). In deployments where MTC-IWF is not co-located with SCEF, interactions between MTC-IWF and SCEF are left up to the implementation. + +The trust domain (see figure 4.2-2) cover entities that are protected by adequate network domain security. The entities and interfaces within the trust domain may all be within one operator's control, or some may be controlled by a trusted business partner which has a trust relationship with the operator e.g. another operator or a 3rd party. The security requirements for the trust domain are out of scope of this specification. + +When the SCEF belongs to a trusted business partner of the HPLMN, it is still seen as an HPLMN entity by other HPLMN or VPLMN functional entities invoked by the SCEF (e.g. HSS, MME). + +Applications operating in the trust domain may require only a subset of functionalities (e.g. authentication, authorization, etc.) provided by the SCEF. Applications operating in the trust domain can also access network entities (e.g. PCRF), wherever the required 3GPP interface(s) are made available, directly without the need to go through the SCEF. + +The Interworking SCEF (IWK-SCEF) is optional. When deployed, the IWK-SCEF is located in the VPLMN as shown in the figure 4.2-1b. + +## 4.3 Reference points + +### 4.3.1 General + +The following 3GPP reference points support the Indirect and Hybrid models of MTC and Service Capability Exposure. + +NOTE: As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further reference points may be added. + +### 4.3.2 List of Reference Points + +The description of the MTC and Service Capability Exposure related reference points: + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------| +| Tsms: | Reference point used by an entity outside the 3GPP network to communicate with UEs used for MTC via SMS. | +| Tsp: | Reference point used by a SCS to communicate with the MTC-IWF related control plane signalling. | +| T4: | Reference point used between MTC-IWF and the SMS-SC in the HPLMN. | +| T6a: | Reference point used between SCEF and serving MME. | +| T6b: | Reference point used between SCEF and serving SGSN. | +| T6ai: | Reference point used between IWK-SCEF and serving MME. | +| T6bi: | Reference point used between IWK-SCEF and serving SGSN. | +| T7: | Reference point used between IWK-SCEF and SCEF. | +| T8: | Reference point used between the SCEF and the SCS/AS. | +| T9a: | Reference point used between UCMF and AS. | +| T9b: | Reference point used between UCMF and SCEF. | +| S6m: | Reference point used by MTC-IWF to interrogate HSS/HLR. | +| S6n: | Reference point used by MTC-AAA to interrogate HSS/HLR. | +| S6t: | Reference point used between SCEF and HSS. | +| Rx: | Reference point used by SCEF and PCRF. Functionality for Rx reference point is specified in TS 23.203 [27]. | +| Ns: | Reference point used between SCEF and RCAF. | +| Nt: | Reference point used by SCEF and PCRF. Functionality for Nt reference point is specified in TS 23.203 [27]. | +| Nu: | Reference point used by SCEF to interact with the PFDF. | + +NOTE 1: Protocol assumption: User plane communication with SCS, for Indirect model, and AS, for Direct and Hybrid models, is achieved using protocols over Gi and SGi reference points. Control plane protocols over those reference points such as RADIUS/Diameter as specified in TS 29.061 [8] can also be supported towards the SCS. + +NOTE 2: It is assumed that interfaces on the T6ai/T6bi/T7 reference points use the same protocol(s) as interfaces on the T6a/T6b reference points. + +### 4.3.3 Reference Point Requirements + +#### 4.3.3.1 Tsp Reference Point Requirements + +The Tsp reference point shall fulfil the following requirements: + +- connects a MTC-IWF to one or more SCSs; +- supports the following device trigger functionality: + - reception of a device trigger request from SCS that includes an Application Port ID used by the UE to route the trigger internally to the appropriate triggering function; + +NOTE 1: The Application Port ID can have different value for different applications. + +- report to the SCS the acceptance or non-acceptance of the device trigger request; +- report to the SCS the success or failure of a device trigger delivery; and +- provides congestion/load control information to SCS as part of the response to device trigger requests. +- deliver a payload and application port ID received from the MTC-IWF and the external ID of the UE to SCS. + +In addition, Domain Name System procedures similar to what is specified in TS 29.303 [9] may be used by the SCS for lookup and selection of which specific MTC-IWF to be used. + +NOTE 2: Security requirements can be found in clause 4.8. + +#### 4.3.3.2 T4 Reference Point Requirements + +The T4 reference point shall fulfil the following requirements: + +- connects the MTC-IWF, taking the role of the SME, to SMS-SC inside HPLMN domain; +- supports the following device trigger functionality: + - transfer of device trigger, addressed by either an MSISDN or the IMSI, from MTC-IWF to SMS-SC inside HPLMN domain; + - transfer to the SMS-SC the serving SGSN/MME/MSC identity(ies) along with device trigger when addressed by IMSI; and + - report to MTC-IWF the submission outcome of a device trigger and the success or failure of delivering the device trigger to the UE. +- supports the delivering of SMS payload to SCS using Short Message Mobile Originated (MO-SMS) procedure via MTC-IWF. + +#### 4.3.3.3 Void + +#### 4.3.3.4 S6m Reference Point Requirements + +The S6m reference point shall fulfil the following requirements: + +- connect the MTC-IWF to HSS/HLR containing subscription and UE related information; and +- support interrogation of HSS/HLR to: + - map E.164 MSISDN or external identifier to IMSI; + - map IMSI and Application Port ID to external identifier; + - retrieve serving node information for the UE (i.e. serving SGSN/MME/MSC/IP-SM-GW identities); and + - determine if a SCS is allowed to send a device trigger to a particular UE. + +NOTE: It is up to stage3 to define interworking between diameter-based s6m and map-based interface to the legacy HLR. + +#### 4.3.3.5 S6n Reference Point Requirements + +The S6n reference point shall fulfil the following requirements: + +- support communication between MTC-AAA and HSS/HLR containing subscription and UE related information; and +- support interrogation of HSS/HLR to: + - map between IMSI and External Identifier(s). + +#### 4.3.3.6 T6a/T6b Reference Point Requirements + +The T6a and T6b reference points shall fulfil the following requirements: + +- T6a connects the SCEF to the serving MME; +- T6b connects the SCEF to the serving SGSN; +- supports the following functionality: + - monitoring event configuration by the SCEF at the serving MME/SGSN; + +- monitoring event reporting by the serving MME/SGSN to the SCEF. +- NIDD to/from the serving MME/SGSN. + +#### 4.3.3.7 S6t Reference Point Requirements + +The S6t reference point shall fulfil the following requirements: + +- connect the SCEF to HSS containing subscription and UE related information; +- monitoring event configuration/deletion by the SCEF at the HSS; and +- monitoring event reporting by the HSS to the SCEF. +- configuration/deletion of communication pattern parameters by the SCEF to HSS. + +#### 4.3.3.8 T6ai/T6bi Reference Point Requirements + +The T6ai and T6bi reference points shall fulfil the following requirements: + +- T6ai connects the IWK-SCEF to the serving MME; +- T6bi connects the IWK-SCEF to the serving SGSN; +- T6ai/T6bi support the following functionality: + - Monitoring Event reporting by the serving MME/SGSN to the IWK-SCEF; + - Forwarding of the Monitoring configuration information from the MME/SGSN to the IWK-SCEF. + - Forwarding of the NIDD configuration information from the MME to the IWK-SCEF; + - NIDD between the serving MME/SGSN and the IWK-SCEF. + +#### 4.3.3.9 T7 Reference Point Requirements + +The T7 reference point shall fulfil the following requirements: + +- connect the IWK-SCEF to the SCEF for Monitoring Event reporting. +- connect the IWK-SCEF to the SCEF for NIDD service. + +#### 4.3.3.10 Ns Reference Point Requirements + +The Ns reference points shall fulfil the following requirements: + +- Ns connects the SCEF to the RCAF; +- Ns supports the following functionality: + - request for network status by the SCEF; + - report of network status by the RCAF to the SCEF. + +#### 4.3.3.11 Nu Reference Point Requirements + +The Nu reference point shall fulfil the following requirements: + +- Nu connects the SCEF to the PFDF; +- Nu supports the following functionality: + - Provision, modification and removal of a subset or all of the Packet Flow Descriptions (PFDs) in the PFDF according to the instructions received from the SCS/AS. + +#### 4.3.3.12 T8 Reference Point Requirements + +The T8 reference points shall fulfil the following requirements: + +- connect one or more SCEF to one or more SCS/AS; +- use API-based communication model; + +NOTE: The details of API aspects are left to Stage 3. + +#### 4.3.3.13 T9a/T9b Reference Point Requirements + +The T9a and T9b reference points shall fulfil the following requirements: + +- T9a connects the UCMF to an AS; +- T9b connects the UCMF to the SCEF; +- supports the following functionality: + - provisioning of RACS database information to the UCMF. + +## 4.4 Network Elements + +### 4.4.1 General + +The following 3GPP network elements provide functionality to support the Indirect and Hybrid models of MTC. + +NOTE: As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further network elements may be defined. + +### 4.4.2 MTC-IWF + +To support the Indirect and Hybrid models of MTC, one or more instances of an MTC InterWorking Function (MTC-IWF) reside in the HPLMN. A MTC-IWF may be a standalone entity or a functional entity of another network element. The MTC-IWF hides the internal PLMN topology and relays or translates signalling protocols used over Tsp to invoke specific functionality in the PLMN. + +The functionality of the MTC-IWF includes the following: + +- termination of the Tsp, T4 and S6m and Rf/Ga reference points; +- ability to authorize the SCS before communication establishment with the 3GPP network; +- ability to authorize control plane requests from an SCS; +- the following device trigger functionalities: + - reception of a device trigger request from SCS that includes an Application Port ID used by the UE to route the trigger internally to the appropriate triggering function; + - report to the SCS the acceptance or non-acceptance of the device trigger request; + - report to the SCS the success or failure of a device trigger delivery; + - may apply MTC-IWF and/or SGSN/MME induced congestion/load control as part of the response to trigger requests; and + - uses a standardised identifier to allow the UE and the network to distinguish an MT message carrying device triggering information from any other type of messages. +- an HSS resolution mechanism for use when multiple and separately addressable HSSs have been deployed by the network operator (see e.g. the SLF / Diameter Proxy agent specified in clause 5.8 TS 23.228 [10]); + +- interrogation of the appropriate HSS, when needed for device triggering, to: + - map E.164 MSISDN or External Identifier to IMSI; + - retrieve serving node information for the UE (e.g. serving SGSN/MME/MSC/IP-SM-GW identifier); and + - determine if a SCS is allowed to send a device trigger to a particular UE. +- reception of a MO data and device identities (i.e. IMSI and Application Port ID) from SMS-SC; +- deliver the MO data, External ID, and application port ID associated with the UE to the SCS; +- report to the SMS-SC the success or failure of a MO data delivery; +- interrogation of the appropriate HSS, when needed for MO delivery, to map IMSI and Application Port ID to External Identifier; +- selection of the most efficient and effective device trigger delivery mechanism and shielding of this detail from SCS based on; + - current UE serving node information from HSS/HLR (e.g. serving MME/SGSN/MSC/IP-SM-GW identifier); + - the device trigger delivery mechanisms supported by the UE; + - the possible device trigger delivery services supported by the HPLMN and, when roaming, VPLMN; + - operator defined device trigger delivery policies, if any; and/or + - optionally, any information received from the SCS. +- protocol translation, if necessary, and forwarding towards the relevant network entity (i.e. serving SGSN/MME/MSC or SMS-SC inside HPLMN domain) of a device trigger request to match the selected trigger delivery mechanism; +- generation of device trigger CDRs with External Identifier and SCS Identifier and forwarding to CDF/CGF over instance of Rf/Ga; and + +NOTE 1: CDR generation with or without a device trigger indication by other network entities is not precluded by CDR generation by the MTC-IWF. + +- ability for secure communications between the 3GPP network and the SCS. + +The architecture shall allow the use of multiple MTC-IWFs within a HPLMN + +NOTE 2: This is useful in particular to maintain service upon single MTC-IWF failure. + +### 4.4.3 HSS/HLR + +An HSS/HLR supporting device triggering shall support the following functionalities: + +- termination of the S6m reference point where MTC-IWFs connect to the HLR/HSS; +- stores and provides to MTC-IWF (and optionally to MTC AAA) the mapping/lookup of E.164 MSISDN or external identifier(s) to IMSI and subscription information used by MTC-IWF for device triggering; +- mapping of IMSI and Application Port ID to external identifier; +- mapping of E.164 MSISDN or external identifiers to IMSI; +- optionally, mapping from External Identifiers to MSISDN is also provided for legacy SMS infrastructure not supporting MSISDN-less SMS; +- HSS stored "Routing information" including serving node information if available for the UE (e.g. serving SGSN/MME/MSC identifier and registered IP-SM-GW identifier); and +- determine if a SCS is allowed to send a device trigger to a particular UE; + +- termination of the S6n reference point; +- provides to MTC-AAA the mapping between IMSI and External Identifier(s). + +An HSS supporting monitoring events feature shall support the following functionalities: + +- termination of the S6t reference point where SCEF connect to the HSS; +- mapping of E.164 MSISDN or external identifiers to IMSI for request received over S6t; +- monitoring event configuration by the SCEF; and +- monitoring event reporting to the SCEF. + +An HSS supporting the feature of handling of CP parameters from SCEF to MME shall support the following functionalities: + +- termination of the S6t reference point where SCEF connect to the HSS; and +- receiving CP parameters with an External ID; and +- storing the received CP parameters with the corresponding subscriber data; and +- forwarding the received CP parameters with the subscriber data to the corresponding MME. + +An HSS supporting non-IP data delivery via SCEF feature shall support the following functionalities: + +- termination of the S6t reference point where SCEF connect to the HSS; and +- mapping of E.164 MSISDN or external identifier to IMSI. + +### 4.4.4 GGSN/P-GW + +A GGSN or P-GW supporting the Indirect or Hybrid model of MTC may support the following functionality + +- Based on APN configuration and unavailability of MSISDN and External Identifiers(s) in the GGSN/PGW, the GGSN/PGW either queries a MTC AAA server for retrieval of External Identifier(s) based on IMSI or routes RADIUS/Diameter requests for AAA servers in external PDNs (as specified in TS 29.061 [8]) via a MTC AAA proxy. + +### 4.4.5 SGSN/MME/MSC + +SGSN and MME specific functionality to support the Indirect and Hybrid models of MTC includes the following: + +- MME terminates the T6a reference point; +- SGSN terminates the T6b reference point; +- may provide SGSN/MME congestion/load information to the MTC-IWF; +- monitoring event configuration by the SCEF; and +- monitoring event reporting to the SCEF. +- The MME and SGSN transfers non-IP data to the UE using a PDN connection to the SCEF as defined in TS 23.401 [7] and TS 23.060 [6] respectively. +- The MME/SGSN transfers non-IP data to the (IWK-)SCEF. +- MME may use the CP parameters for deriving the CN assisted eNodeB parameters. The CP parameters received from the HSS are used by the MME as input to derive the CN assisted eNodeB parameter values. + +### 4.4.6 SMS-SC + +SMS-SC specific functionality to support the Indirect and Hybrid models of MTC includes the following: + +- terminates the T4 reference point where MTC-IWFs connect to the SMS-SC; and +- supports PS-only MT-SMS that can be delivered with IMSI in lieu of E.164 MSISDN; +- provides the routing information it received from MTC-IWF to SMS-GMSC if needed; +- deliver the SMS payload, Application Port ID, IMSI of the UE to MTC-IWF via T4; and +- send SMS delivery report to UE. + +### 4.4.7 MTC AAA + +To support translation of the IMSI to External Identifier(s) at the network egress, an AAA function (MTC AAA) is used in the HPLMN. The MTC AAA may be deployed to return the External Identifier(s) based on IMSI. Alternatively the MTC AAA may be deployed as a RADIUS/Diameter proxy between the GGSN/PGW and the AAA server in the external PDN. + +When deployed as an AAA Server, the MTC AAA shall support the following functionalities: + +- termination of the S6n reference point where the MTC-AAA communicates with the HLR/HSS; +- return the external identifier(s) corresponding to an IMSI; and +- may query the HSS with IMSI to retrieve the External Identifier(s) and may cache IMSI/External Identifier mapping to avoid multiple HSS queries. + +When deployed as an AAA Proxy, the MTC AAA shall support the following functionalities: + +- termination of the S6n reference point where the MTC-AAA communicates with the HLR/HSS; +- replace IMSI with an External Identifier for messages to an external AAA server; +- replace External Identifier with IMSI for messages from an external AAA server; +- identifying the destination external AAA server using standard RADIUS/Diameter procedures; and +- optionally, query the HSS with IMSI to retrieve the external identifier(s) and cache IMSI/External Identifier mapping to avoid multiple HSS queries. + +### 4.4.8 Service Capability Exposure Function + +The Service Capability Exposure Function (SCEF) provides a means to securely expose the services and capabilities provided by 3GPP network interfaces. The SCEF provides a means for the discovery of the exposed services and capabilities. The SCEF provides access to network capabilities through homogenous network application programming interfaces (e.g. Network APIs) defined over T8 interface. The SCEF abstracts the services from the underlying 3GPP network interfaces and protocols. + +Individual instances of SCEF may vary depending on what service capabilities are exposed and what API features are supported. + +The SCEF is always within the trust domain. An application can belong to the trust domain or may lie outside the trust domain. + +The SCEF may support CAPIF. When CAPIF is supported, the SCEF supports the CAPIF API provider domain functions. The CAPIF and associated API provider domain functions are specified in TS 23.222 [43]. + +The functionality of the SCEF may include the following: + +- Authentication and Authorization: + - Identification of the API consumer, + - Profile management, + - ACL (access control list) management. + +NOTE 1: The details of security aspects of T8 interface are outside the scope of this specification. + +- Ability for the external entities to discover the exposed service capabilities +- Policy enforcement: + - Infrastructural Policy: policies to protect platforms and network. An example of which maybe ensuring that a service node such as SMS-SC is not overloaded. + - Business Policy: policies related to the specific functionalities exposed. An example may be number portability, service routing, subscriber consent etc. + - Application Layer Policy: policies that are primarily focused on message payload or throughput provided by an application. An example may be throttling. +- Assurance: + - Integration with O&M systems, + - Assurance process related to usage of APIs. +- Accounting for inter operator settlements. + +NOTE 2: The details of accounting aspects of T8 interface are outside the scope of this specification. + +- Access: issues related to external interconnection and point of contact +- Abstraction: hides the underlying 3GPP network interfaces and protocols to allow full network integration. The following functions are among those that may be supported: + - Underlying protocol connectivity, routing and traffic control, + - Mapping specific APIs onto appropriate network interfaces, + - Protocol translation. + +NOTE 3: Abstraction is applied only in cases where required functionality is not natively provided by 3GPP network + +The services and capabilities offered by SCEF to SCS/AS include: + +- Group Message Delivery (see clause 4.5.5), +- Monitoring events (see clause 4.5.6), +- High latency communication (see clause 4.5.7), +- Informing about potential network issues (see clause 4.5.8), +- Resource management of background data transfer (see clause 4.5.9), +- E-UTRAN network resource optimizations based on communication patterns provided to the MME (see clause 4.5.10), +- Support of setting up an AS session with required QoS (see clause 4.5.11), +- Change the chargeable party at session set-up or during the session (see clause 4.5.12), +- Non-IP Data Delivery (see clause 4.5.14), +- Packet Flow Description management (see clause 4.5.15), +- Enhanced Coverage restriction control (see clause 4.5.17), +- Network Parameter Configuration (see clause 4.5.20), +- Accessing MTC-IWF Functionality via T8 (see clause 5.17), + +The SCEF shall protect the other PLMN entities (e.g. HSS, MME) from requests exceeding the permission arranged in the SLA with the third-party service provider. + +When needed, the SCEF supports mapping between information exchanged with SCS/AS (e.g. geographical identifiers) and information exchanged with internal PLMN functions (e.g. cell-Id / ENB-Id / TAI / MBMS SAI, etc.). This mapping is assumed to be provided by the SCEF based on local configuration data. + +### 4.4.9 Interworking SCEF + +The Interworking SCEF (IWK-SCEF) is optional. When deployed, the IWK-SCEF is located in the VPLMN for interconnection with the SCEF of the HPLMN. The Interworking SCEF receives the Monitoring Event Reports from the underlying entities and sends them to the SCEF. The IWK-SCEF relays the non-IP data between the MME/SGSN and the SCEF. + +NOTE: In this release the only VPLMN network entities connected towards the IWK-SCEF are the MMEs and SGSNs. + +The functionality of the Interworking SCEF includes the following: + +- Storing of state information to identify e.g. the connection to SCEF (see clause 5.6.0); and +- Forwarding messages between the serving PLMN and HPLMN SCEF (see clause 5.13); and +- Authorisation of monitoring request (see clause 5.6.6.1); and +- Storing of monitoring request during its life time (see clause 5.6.6.1); and +- Normalization of reports according to roaming agreement between VPLMN and HPLMN, e.g. change the location granularity (from cell level to a level appropriate for the HPLMN) of Monitoring Event Reports received from the underlying entities; and +- Optionally, generate charging/accounting information: + - For generation of charging/accounting information, the IWK-SCEF receives the Monitoring configuration information as well as the Monitoring Event Report from the underlying nodes; + - For generation of charging/accounting information, the IWK-SCEF receives the NIDD charging ID from the SCEF during the T6a/T6b Connection Establishment Procedure (see clause 5.13.1.2). + +### 4.4.10 RAN Congestion Awareness Function + +A RCAF supporting network status reporting shall support the following functionalities: + +- termination of the Ns reference point where SCEF connects to the RCAF; +- request for one-time or continuous reporting of network status changes by the SCEF; and +- report of one-time or continuous network status changes to the SCEF. + +### 4.4.11 Packet Flow Description Function + +A Packet Flow Description Function (PFDF) shall support the following functionalities: + +- Termination of the Nu reference point where SCEF connects to the PFDF; +- Management of Packet Flow Descriptions (PFDs) (i.e. provision, modification and removal) according to the instructions received from the SCS/AS via the SCEF; +- Provision of Packet Flow Description (PFDs) to the PCEF/TDF as specified in TS 23.203 [27]. + +### 4.4.12 UE radio Capabilities Management Function + +UCMF specific functionality to support provisioning of RACS information includes the following: + +- UCMF terminates the T9a reference point; +- UCMF terminates the T9b reference point. + +The services and capabilities offered by UCMF to SCEF and SCS/AS include: + +- RACS information provisioning. + +## 4.5 High Level Function + +### 4.5.1 Device Triggering Function + +Device Triggering is the means by which a SCS sends information to the UE via the 3GPP network to trigger the UE to perform application specific actions that include initiating communication with the SCS for the indirect model or an AS in the network for the hybrid model. Device Triggering is required when an IP address for the UE is not available or reachable by the SCS/AS. + +Device 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, along with the information to route it, is referred to as the Trigger payload. The UE needs to be able to distinguish an MT message carrying device triggering information from any other type of messages. + +**NOTE:** The Trigger payload, for example, upon the reception by the UE possibly provides information to the application that may trigger application related actions. The application in the UE may perform indicated actions, such as for example to initiate immediate or later communication to the SCS/AS, based on the information contained in the Trigger payload. + +Device Triggering is subscription based. The subscription provides the information whether a UE is allowed to be triggered by a specific SCS. When device triggers are delivered via MT-SMS the serving nodes MME, SGSN and MSC provide the service towards a specific UE based on the UE's subscription for MT-SMS and other subscription parameters affecting MT-SMS service provision. + +Device triggering recall/replace functionality allows a SCS to recall or replace previously submitted trigger messages which are not yet delivered to the UE. + +Charging data are collected for the device triggering. The MTC-IWF generates CDRs for the service requester. When device triggers are delivered via MT-SMS then network entities, like MME, SGSN, MSC or SMS-SC generate CDRs for SMS services provided for the mobile subscriber. + +### 4.5.2 PS-only Service Provision + +PS-only service provision is providing a UE with all subscribed services via PS domain. PS-only service provision implies a subscription that allows only for services exclusively provided by the PS domain, i.e. packet bearer services and SMS services. The support of SMS services via PS domain NAS is a network deployment option and may depend also on roaming agreements. Therefore, a subscription intended for PS-only service provision may allow also for SMS services via CS domain to provide a UE with SMS services in situations when serving node or network don't support SMS via PS domain NAS. The functionality that enables PS-only service provision is described in TS 23.060 [6] and TS 23.272 [11]. + +The functionality that enables PS-only service provision for SMS delivery in IMS is described in TS 23.204 [13]. + +### 4.5.3 Core Network assisted RAN parameters tuning + +Core Network assisted RAN parameters tuning aids the RAN in optimizing the setting of RAN parameters. See TS 23.401 [7] for details. + +### 4.5.4 UE Power Saving Mode + +A UE may adopt the PSM for reducing its power consumption. That mode is similar to power-off, but the UE remains registered with the network and there is no need to re-attach or re-establish PDN connections. A UE in PSM is not + +immediately reachable for mobile terminating services. A UE using PSM is available for mobile terminating services during the time it is in connected mode and for the period of an Active Time that is after the connected mode. The connected mode is caused by a mobile originated event like data transfer or signalling, e.g. after a periodic TAU/RAU procedure. PSM is therefore intended for UEs that are expecting only infrequent mobile originating and terminating services and that can accept a corresponding latency in the mobile terminating communication. + +For mobile terminated data while a UE is in PSM, the functions for High latency communication may be used as described in clause 4.5.7. + +PSM has no support in the CS domain on the network side. PSM should only be used by UEs using the PS domain, SMS and mobile originated IMS or CS services. A UE that uses mobile terminated CS services other than SMS should not use PSM as the CS domain does not provide support for mobile terminated CS voice services to UEs that are in PSM. A UE that uses delay tolerant mobile terminated IMS services other than SMS should not request for PSM unless IMS uses the functions for High latency communication as described in clause 4.5.7. + +NOTE 1: The frequency of keep-alive messages on Gm impacts the possibility to use IMS services for UEs applying PSM. + +Applications that want to use the PSM need to consider specific handling of mobile terminating services or data transfers. A network side application may send an SMS or a device trigger to trigger an application on UE to initiate communication with the SCS/AS, which is delivered when the UE becomes reachable. Alternatively a network side application may request monitoring of reachability for data to receive a notification when it is possible to send downlink data immediately to the UE, which is when the UE becomes reachable for downlink data transfer. Alternatively, if an SCS/AS has periodic downlink data, it is more efficient when the UE initiates communication with the SCS/AS to poll for downlink data with that period. For either of the options to work, the UE should request an Active Time that is together with the time being in connected mode long enough to allow for potential mobile terminated service or data delivery, e.g. to deliver an SMS. + +When the UE wants to use the PSM it shall request an Active Time value during every Attach and TAU/RAU procedures. If the network supports PSM and accepts that the UE uses PSM, the network confirms usage of PSM by allocating an Active Time value to the UE. The network takes the UE requested value, the Maximum Response Time (defined in clause 5.6.1.4), if provided with the Insert Subscriber Data or Update Location Ack message from HSS, and any local MME/SGSN configuration into account for determining the Active Time value that is allocated to the UE. If the UE wants to change the Active Time value, e.g. when the conditions are changed in the UE, the UE consequently requests the value it wants in the TAU/RAU procedure. + +NOTE 2: The minimum recommended length for the Active Time is the time allowing for the 'msg waiting flag' in the MME/SGSN to trigger the SMSC via the HSS to deliver an SMS to the MME/SGSN, e.g. 2 DRX cycles plus 10 seconds. + +NOTE 3: The Maximum Response Time value can be configured as desired Active Time value in the HSS via O&M. + +An Active Time may be shorter than the time estimated for delivering a waiting SMS to the UE in NOTE 2 above, e.g. 0 seconds. If the MME/SGSN allocates such a shorter Active Time to the UE, the MME/SGSN (for signalling only connections and if the 'msg waiting flag' is set) and the RAN (for connections with RAB(s) set up) should be configured to keep the connection with the UE sufficiently long such that a waiting SMS can be delivered. + +NOTE 4: The RAN configuration of RAB connection times need not differentiate between UEs. + +If the MME/SGSN is requested to monitor for Reachability for Data, the MME/SGSN (for signalling only connections) and the RAN (for connections with RAB(s) set up) should keep the connection for the Maximum Response Time less the Active Time, if Maximum Response Time is provided with the Insert Subscriber Data message from HSS. Otherwise a configured default Maximum Response Time is assumed by the MME/SGSN. + +The UE is in PSM until a mobile originated event (e.g. periodic RAU/TAU, mobile originated data or detach) requires the UE to initiate any procedure towards the network. In Attach and RAU/TAU procedures a PSM capable UE may request a periodic TAU/RAU Timer value suitable for the latency/responsiveness of the mobile terminated services. If the UE wants to change the periodic TAU/RAU Timer value, e.g. when the conditions are changed in the UE, the UE consequently requests the value it wants in the TAU/RAU procedure. + +NOTE 5: If the UE or application performs any periodic uplink data transfer with a periodicity similar to the Periodic TAU/RAU Timer value, it preferably requests a Periodic TAU/RAU Timer value that is at least slightly larger than the data transfer period to avoid periodic TAU/RAU procedures that would increase power consumption. + +Any timers and conditions that remain valid during power-off, e.g. NAS-level back-off timers, apply in the same way during PSM. The UE may leave the PSM any time, e.g. for mobile originated communications. + +If the network confirms the usage of PSM to a UE, the network shall not activate the ISR for such UE. + +The specific procedure handling is described in TS 23.060 [6] and TS 23.401 [7]. + +### 4.5.5 Group Message Delivery + +The Group Message Delivery feature allows an SCS/AS to deliver a payload to a group of UEs. Two methods of Group Message Delivery are specified: + +- Group Message Delivery via MBMS which is intended to efficiently distribute the same content to the members of a group that are located in a particular geographical area when MBMS is used; +- Group Message Delivery via unicast MT NIDD for UEs which are part of the same External Group Identifier. + +The specific procedure handling for group message delivery using MBMS is described in clause 5.5.1. The group message delivery using MBMS has limited applicability and does not support all the scenarios, e.g. UEs not supporting MBMS, UEs located in areas where MBMS is not deployed. The SCS/AS may recall or replace a previously submitted MBMS message; this is described in clause 5.5.2. + +The Group MT NIDD procedure for delivering non-IP data to a group via unicast MT NIDD is described in clause 5.5.3. The SCEF uses the SCS/AS Identifier and the External Group Identifier to determine the APN that will be used to send the non-IP data to the group member UEs. This determination is based on local policies. When the SCEF receives a Group MT NIDD request from the SCS/AS, the SCEF queries the HSS to resolve the group members and forks the message by sending it in a unicast manner to all of the individual UEs that are associated with the External Group Identifier. + +NOTE: In order for the non-IP data to reach each group member UE, each group member UE must have a PDN connection established to the APN and the SCS/AS must have performed an NIDD Configuration Procedure for the External Group Identifier. + +### 4.5.6 Monitoring Events + +#### 4.5.6.1 General + +The Monitoring Events feature is intended for monitoring of specific events in 3GPP system and making such monitoring events information available via the SCEF. It is comprised of means that allow the identification of the 3GPP network element suitable for configuring the specific events, the event detection, and the event reporting to the authorised users, e.g. for use by applications or logging, etc. If such an event is detected, the network might be configured to perform special actions, e.g. limit the UE access. Configuration and reporting of the following monitoring events may be supported: + +- Monitoring the association of the UE and UICC and/or new IMSI-IMEI-SV association; +- UE reachability; +- Location of the UE, and change in location of the UE; + +NOTE 1: Location granularity for event request, or event report, or both could be at cell level (CGI/ECGI), TA/RA level or other formats e.g. shapes (e.g. polygons, circles, etc.) or civic addresses (e.g. streets, districts, etc.). + +- Loss of connectivity; +- Communication failure; + +- Roaming status (i.e. Roaming or No Roaming) of the UE, and change in roaming status of the UE; and + +NOTE 2: Roaming status means whether the UE is in HPLMN or VPLMN based on the most recently received registration state in the HSS. + +- Number of UEs present in a geographical area; +- Availability after DDN failure; and +- PDN Connectivity Status. + +To support monitoring features in roaming scenarios, a roaming agreement needs to be made between the HPLMN and the VPLMN. The set of capabilities required for monitoring may be accessible via different 3GPP interfaces/nodes. Selection of 3GPP interface(s) to configure/report the event is dependent on the type of the event, operator configuration, required frequency of event reporting, application provided parameters in monitoring event request, etc. + +Support for Monitoring Events can be offered either via HSS, MME/SGSN (as described in clause 4.5.6.2) or via PCRF (as described in clause 4.5.6.3). Based on operator policies, it shall be possible to configure Monitoring Events such that some Monitoring Event follows procedures in clause 4.5.6.2 while another Monitoring Event follows procedures in clause 4.5.6.3. SCEF shall not enable a given Monitoring Event for the same UE via both HSS/MME/SGSN, and PCRF. For the case of group based Monitoring Events, the SCS/AS (either the same SCS/AS or different SCSs/ASs) may configure a Monitor Event with different External Group Identifiers. If, in such a case, more than one External Group Identifier point to the same UE and no Group Reporting Guard Time was provided with any of the monitoring event configurations, the MME, HSS, and SCEF should not send duplicate reports of the same event for the same UE to the same destination. + +NOTE 3: If the configuration of Monitoring Events uses signalling which was specified as part of another feature than the Monitoring feature, then the requirements on the HSS, MME/SGSN and PCRF as specified by that feature apply e.g. not to generate accounting information, not to verify SLA etc. + +#### 4.5.6.2 Monitoring Events via HSS and MME/SGSN + +Monitoring Events via the HSS and the MME/SGSN enables SCEF to configure a given Monitor Event at HSS or MME/SGSN, and reporting of the event via HSS and/or MME/SGSN. Depending on the specific monitoring event or information, it is either the MME/SGSN or the HSS that is aware of the monitoring event or information and makes it available via the SCEF. + +The procedures for requesting specific monitoring information or event reports as well as the report procedures are described in clause 5.6. + +Some subscription data in HSS for a UE may affect the event monitoring, and such subscription data is set taking the input from the specific parameter(s) of monitoring event(s) as specified in clause 5.6 or from the network parameter configuration(s) as specified in clause 5.18, or from both of them. + +If the Enhanced Multiple Event Monitoring feature is supported, the HSS stores the specific parameters per SCEF Reference ID for the same or different event types from multiple SCS/ASs or the specific parameters for the network parameter configurations from multiple SCS/ASs, or from both of them. + +#### 4.5.6.3 Monitoring Events via PCRF + +Monitoring Events via the PCRF enables the SCEF to retrieve the location information and to report communication failure of a UE. When not performing group monitoring, the SCEF acting as AF shall have an active Rx session to enable the PCRF to report these events. The procedure is defined in clause 6.2.3 of TS 23.203 [27]. The procedure for requesting location information, when not performing group monitoring, is described in clause 5.6.4.1. + +The UE location information, provided over Rx, may include a time stamp to indicate when the UE was last-known to be in that location, i.e. if the current location or the last-known location is provided. The UE location information is reported at the time the Rx session is established, modified or terminated. The subscription to UE location information is not persistent across Rx sessions. The UE location information is provided for 3GPP IP-CAN type, for Trusted WLAN access (S2a) or untrusted WLAN (S2b) as defined in clause 6.2.3 of TS 23.203 [27]. + +The reporting of communication failure refers to the reporting of RAN/NAS release cause codes according to TS 23.401 [7], TS 23.060 [6], and TWAN/UWAN release causes according to TS 23.402 [26]. Once the RAN/NAS or + +TWAN/UWAN release cause codes are reported to the PCRF, the PCRF reports it to the SCEF according to TS 23.203 [27] for applicable IP-CAN types and RAT types listed in TS 23.203 [27]. + +Monitoring Events via the PCRF also enable the SCEF to request the location information of a group of UEs via Nt interface. + +The procedure for requesting monitoring of a group of UEs via the PCRF is described in clause 5.6.4.1a. Group monitoring requests are sent by the SCEF to each PCRF in the operator's network. + +NOTE: The existing PCRF addressing mechanism defined in TS 23.203 [27] does not apply for requesting reporting events for a group of UEs. + +The procedure for reporting the location information for a group of UEs is performed for each UE that has an IP-CAN session established at the time the SCEF requests the UE location for a group of UEs as described in clause 5.6.4.2. + +The UE location information, provided over Nt, may include a time stamp to indicate when the UE was last-known to be in that location, i.e. if the current location or the last-known location is provided. The UE location information is provided for 3GPP IP-CAN type, for Trusted WLAN access (S2a) or untrusted WLAN (S2b). + +#### 4.5.6.4 Void + +### 4.5.7 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 e.g. UE Power Saving Mode (see clause 4.5.4) or extended idle mode DRX (see clause 4.5.13) depending on operator configuration. "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 the initial downlink packet(s). + +High latency communication is handled by an extended buffering of downlink data in the Serving GW controlled by the MME/S4-SGSN or in the Gn/Gp-SGSN. The MME/S4-SGSN asks the Serving GW to buffer downlink data until the UE is expected to wake up from its power saving state. The Gn/Gp-SGSN similarly buffers downlink data until the UE is expected to wake up from its power saving state. If a Serving GW change or a Gn/Gp-SGSN change is invoked, the buffered packets are forwarded and will not be lost. The number of packets to buffer is decided by the Serving GW or Gn/Gp-SGSN, but the MME/S4-SGSN may optionally provide a suggestion for the number of downlink packets to be buffered based on the information received from the HSS. The information received from the HSS may be subscription based or may be based on information provided by the SCS/AS during the configuration of the event, see clause 5.6.1.4. + +For Control Plane CIoT EPS optimisation, High latency communication is handled by the buffering of downlink data in the Serving GW or the MME as described in TS 23.401 [7]. + +High latency communication may also be handled by notification procedures (see clause 5.7), when an MME/S4-SGSN is used (i.e. this procedure does not apply to a Gn/Gp-SGSN). The SCS/AS requests notification when a UE wakes up from its power saving state and sends downlink data to the UE when the UE is reachable. Especially for infrequent mobile terminated communication this may be suitable. This notification procedure is available based on two different monitoring events: + +- Monitoring event: UE Reachability; or +- Monitoring event: Availability after DDN failure. + +An SCS/AS may request a one-time "UE Reachability" notification when it wants to send data to the UE. Alternatively the SCS/AS may request repeated "Availability after DDN failure" notifications where each notification is triggered by a DDN failure i.e. the SCS/AS sends a downlink packet which is discarded by Serving GW but which triggers the MME/SGSN to send an event notification to the SCS/AS next time the UE wakes up. + +When requesting to be informed of either "UE Reachability" or "Availability after DDN failure" notification, the SCS/AS may also request Idle Status Indication. If the HSS and the MME/SGSN support Idle Status Indication, then when the UE for which PSM or extended idle mode DRX is enabled transitions into idle mode, the MME/SGSN includes the time at which the UE transitioned into idle mode, the active time and the periodic TAU/RAU time granted + +to the UE by the MME/SGSN in the notification towards the SCEF, the eDRX cycle length and the Suggested number of downlink packets if a value was provided to the S-GW. + +The length of the power saving intervals used by the network decides the maximum latency for a UE. An SCS/AS, which has a specific requirement on the maximum latency for UEs it communicates with, may provide its maximum latency requirement to the network. This is done either by interaction with the application in the UE and setting of appropriate time values in the UE (e.g. periodic RAU/TAU timer) for the Power Saving Mode, or by providing the maximum latency at the configuration of the "UE reachability" monitoring event (if used) (see clause 5.7). + +The tools for High latency communication make the behaviour of the 3GPP network predictable when sending mobile terminated data to UEs applying power saving functions. The network will deliver downlink packets with high reliability for both stationary and mobile UEs when the UE wakes up from its power saving state. Therefore SCS/AS can adapt its retransmissions to reduce the load on both the SCS/AS itself and the network. + +### 4.5.8 Support of informing about potential network issues + +The SCS/AS may request the SCEF for being notified about the network status in a geographical area. The SCS/AS can request for a one-time reporting of network status or a continuous reporting of network status changes. + +### 4.5.9 Resource management of background data transfer + +The 3rd party SCS/AS requests a time window and related conditions from the SCEF for background data transfer to a set of UEs via the Nt interface. The SCS/AS request shall contain the SCS/AS identifier, SCS/AS Reference ID, the volume of data expected to be transferred per UE, the expected amount of UEs, the desired time window and optionally, network area information. The SCEF passes this information to a selected PCRF. The PCRF shall determine one or more transfer policies each including a recommended time window for the data transfer together with a maximum aggregated bitrate for the expected volume of data and a reference to the applicable charging rate during the time window and provide them to the SCEF together with a Reference ID. The SCEF shall forward the Reference ID and the transfer policies to the 3rd party SCS/AS. If more than one transfer policy was received, the 3rd party SCS/AS needs to select one of them and inform the SCEF about the selected transfer policy (which forwards it to the PCRF). If this is not done, none of the transfer policies provided by the operator will be valid. + +NOTE 1: The maximum aggregated bitrate (optionally provided in a transfer policy) is not enforced in the network. The operator may apply offline CDRs processing (e.g. combining the accounted volume of the involved UEs for the time window) to determine whether the maximum aggregated bitrate for the set of UEs was exceeded by the ASP and charge the excess traffic differently. + +NOTE 2: It is assumed that the 3rd party SCS/AS is configured to understand the reference to a charging rate based on the agreement with the operator. + +After having negotiated the time window, the SCS/AS (acting as an AF), shall provide the Reference ID to the PCRF for each UE individually together with the SCS/AS session information via the Rx interface. Alternatively, the SCS/AS activates the selected transfer policy via the SCEF, for each UE in the group, by using the "Set the chargeable party at session set-up" or "Change the chargeable party during the session" procedure from clauses 5.12.1 and 5.12.2 to provide the Reference ID to the same or different PCRF. The PCRF retrieves the corresponding transfer policy from the SPR. The PCRF derives the PCC rules for the background data transfer according to this transfer policy and triggers PCC procedures according to TS 23.203 [27] to provide the respective policing and charging information to the PCEF. + +NOTE 3: The SCS/AS will typically request sponsored connectivity for the background data transfer to individual UEs. + +NOTE 4: A transfer policy is only valid until the end of its time window. The removal of outdated transfer policies from the SPR is up to implementation. + +NOTE 5: The SCS/AS can contact the PCRF directly or interact with the PCRF via the SCEF. + +### 4.5.10 E-UTRAN network resource optimizations based on communication patterns provided to the MME + +Predictable communication patterns (CP) of a UE may be provided by the Application Server to the SCEF in order to enable network resource optimizations for such UE(s). The SCEF filters the CP parameters and forwards them to the + +HSS, which provides them to the MME. The MME may use the CP parameters as input to derive the CN assisted eNodeB parameters as described in TS 23.401 [7]. This feature is applicable to UEs served over the E-UTRAN access. + +### 4.5.11 Support of setting up an AS session with required QoS + +The 3rd party SCS/AS may request that a data session to a UE that is served by the 3rd party service provider (AS session) is set up with a specific QoS (e.g. low latency or jitter) and priority handling. This functionality is exposed via the SCEF towards the SCS/AS. + +The SCS/AS can request the network to provide QoS for the AS session based on the application and service requirements with the help of a QoS reference parameter which refers to pre-defined QoS information. + +NOTE 1: The pre-defined QoS information is part of the SLA between the operator and the 3rd party SCS/AS. + +When the SCEF receives the request from the SCS/AS to provide QoS for an AS session, the SCEF acts as an AF per TS 23.203 [27] specifications and transfers the request to provide QoS for an AS session to the PCRF via the Rx interface. + +NOTE 2: An SLA has to be in place defining the possible QoS levels and their charging rates. For each of the possible pre-defined QoS information sets, the PCRF needs to be configured with the corresponding QoS parameters and their values as well as the appropriate Rating-Group (or receive this information from the SPR). + +NOTE 3: The QoS reference parameter is transferred by existing Rx parameters. Before the QoS reference parameter is forwarded, the SCEF can perform a mapping from the name space of the 3rd party AS to the name space of the operator. + +If the SCEF gets informed about bearer level events for the Rx session (e.g. transmission resources are released/lost) the SCEF shall inform the SCS/AS about it. + +### 4.5.12 Change the chargeable party at session set-up or during the session + +The SCS/AS may request the SCEF to start or stop sponsoring a data session for a UE that is served by the 3rd party service provider (AS session), i.e. to realize that either the 3rd party service provider is charged for the traffic (start) or not (stop). The SCS/AS may request to be set as the chargeable party, i.e. sponsoring the traffic, either at AS session set-up or to change it during an ongoing AS session. The SCEF acts as an AF and existing functionality defined in TS 23.203 [27] for sponsored data connectivity is used to support this functionality. If the SCEF gets informed that the Rx session terminates (e.g. due to a release of PDN connection) the SCEF shall inform the SCS/AS about it and shall forward any accumulated usage report received from the PCRF. + +### 4.5.13 Extended idle mode DRX + +#### 4.5.13.1 General + +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. + +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. + +A UE that uses mobile terminated CS services other than SMS should not request for extended idle mode DRX as the CS domain does not provide support for mobile terminated CS voice services to UEs that are in extended idle mode DRX. A UE that uses delay tolerant mobile terminated IMS services other than SMS should not request for extended idle mode DRX unless IMS uses the functions for High latency communication as described in clause 4.5.7. + +NOTE 1: The frequency of keep-alive messages on Gm impacts the possibility to use IMS services for UEs applying extended idle mode DRX. + +In order to negotiate the use of extended idle mode DRX, the UE requests extended idle mode DRX parameters during attach procedure and RAU/TAU procedure. The SGSN/MME may reject or accept the UE request for enabling extended idle mode DRX. If the SGSN/MME accepts the extended idle mode DRX, the SGSN/MME based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the HSS, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. If the SGSN/MME accepts the use of extended idle mode DRX, the UE applies extended idle mode DRX based on the received extended idle mode DRX parameters. If the UE does not receive extended idle mode DRX parameters in the relevant accept message because the SGSN/MME rejected its request or because the request was received by SGSN/MME not supporting extended idle mode DRX, the UE shall apply its regular discontinuous reception as defined in clause 5.13 of TS 23.401 [7]. + +NOTE 2: 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. + +The specific negotiation procedure handling is described in TS 23.060 [6] and TS 23.401 [7]. + +If a UE requests via NAS both to enable PSM (requesting an active time and possibly a periodic TAU timer) and extended idle mode DRX (with a specific extended idle mode DRX cycle value), it is up to the SGSN/MME to decide whether to: + +1. Enable only PSM, i.e. not accept the request for extended idle mode DRX. +2. Enable only extended idle mode DRX, i.e. not accept the request for an active time. +3. Enable both PSM (i.e. provide an active time) and extended idle mode DRX (i.e. provide an extended idle mode DRX parameters). + +The decision between the three above, and which active time, periodic TAU timer and/or extended idle mode DRX cycle value to provide to the UE, are implementation dependent, based on local configuration, and possibly other information available in the SGSN/MME. The method selected is then used until the next Attach or RAU/TAU procedure is initiated, when a new decision may be made. If both extended idle mode DRX and PSM are enabled, the extended idle mode DRX cycle should be set in order to have multiple paging occasions while the active timer is running. + +NOTE 3: To maximize the power saving while in the extended idle mode DRX cycle, the Periodic TAU timer needs to be longer than the extended idle mode DRX cycle. + +In the specific case when the PSM active time provided by the UE is greater than the extended idle mode DRX cycle value provided by the UE, the SGSN/MME may enable both PSM and extended idle mode DRX. This allows a UE to minimize power consumption during the active time e.g. when the active time is slightly longer than typical active time values for example in the order of several minutes. + +If extended idle mode DRX is enabled, the network handles mobile terminated data using high latency communication feature, according to clause 4.5.7, GTP-C retransmissions as described in TS 23.060 [6] and TS 23.401 [7], and applies techniques to handle mobile terminated SMS according to TS 23.272 [11] and location services according to TS 23.271 [33]. + +#### 4.5.13.2 Paging for extended idle mode DRX in UTRAN + +The procedure makes use of the regular DRX cycle mechanism for determination of Paging Occasions (POs) (see TS 25.304 [34]) in conjunction with a new TeDRX timer and a means to synchronize the start of the TeDRX timer with a time reference referred to here as Tref. The TeDRX timer is set to the extended Idle mode DRX cycle value negotiated earlier on NAS level. At TeDRX expiry i.e. when the extended Idle mode DRX cycle elapses the UE monitors the network for paging using regular DRX parameters. + +CN and UE start the extended TeDRX timer at transmission and reception, respectively, of the Attach Accept or RAU Accept message where the relevant extended Idle mode DRX parameters are provided. In other words, Tref corresponds in the CN to the instant when RAU Accept message is sent and in the UE to the instant when the respective Accept message is received. + +The TeDRX timer is maintained and used only when the Attach/RAU procedure was successfully executed and independent of UE's PMM state, i.e. transitions between Idle and Connected mode do not affect the TeDRX timer. + +In order to improve paging reliability e.g. to avoid paging misses due to cell reselection or due to imperfect synchronization of the Tref parameter in the UE and the SGSN, a Paging Transmission Window Time (PTW) described by its duration TPTW is introduced. During PTW the UE monitors the network for paging when the extended Idle mode DRX cycle based on the extended Idle mode DRX value expires. During the PTW there may be multiple opportunities to page the UE which monitors the network for paging using regular DRX parameters. + +![Figure 4.5.13.2-1: The usage of PTW and independence of the extended Idle mode DRX cycle from UE state. The diagram shows a timeline with three consecutive extended Idle mode DRX cycles. Each cycle has a duration of TeDRX. Within each cycle, there is a Paging Transmission Window (PTW) of duration TPTW. The start of each cycle is marked by a vertical dashed line. The start of the first cycle is labeled TN = TRef + N * TeDRX. The start of the second cycle is labeled TN+1 = TRef + (N + 1) * TeDRX. The start of the third cycle is labeled TN+2 = TRef + (N + 2) * TeDRX. The start of the fourth cycle is labeled TN+3 = TRef + (N + 3) * TeDRX. The regular DRX cycle duration is labeled TDRX. The diagram illustrates that the PTW occurs at the beginning of each extended Idle mode DRX cycle, regardless of the UE state.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +Figure 4.5.13.2-1: The usage of PTW and independence of the extended Idle mode DRX cycle from UE state. The diagram shows a timeline with three consecutive extended Idle mode DRX cycles. Each cycle has a duration of TeDRX. Within each cycle, there is a Paging Transmission Window (PTW) of duration TPTW. The start of each cycle is marked by a vertical dashed line. The start of the first cycle is labeled TN = TRef + N \* TeDRX. The start of the second cycle is labeled TN+1 = TRef + (N + 1) \* TeDRX. The start of the third cycle is labeled TN+2 = TRef + (N + 2) \* TeDRX. The start of the fourth cycle is labeled TN+3 = TRef + (N + 3) \* TeDRX. The regular DRX cycle duration is labeled TDRX. The diagram illustrates that the PTW occurs at the beginning of each extended Idle mode DRX cycle, regardless of the UE state. + +**Figure 4.5.13.2-1 The usage of PTW and independence of the extended Idle mode DRX cycle from UE state** + +In reference to Figure 4.5.13.2-1, upon expiry of the TeDRX timer in the UE, the UE monitors the network for paging for TPTW seconds. TDRX is the duration of the regular DRX cycle. + +The necessary information for applying the PTW is provided to the UE over NAS when extended Idle mode DRX is negotiated. + +In the case of a paging trigger received in the CN for a UE in PMM Idle state, the CN forwards the paging message towards relevant RAN node(s) immediately if the paging trigger was received within the PTW. Otherwise the CN forwards the paging message shortly ahead of the beginning of the next PTW taking possible imperfections in the synchronization between the CN and the UE into account. + +#### 4.5.13.3 Paging for extended idle mode DRX in E-UTRAN + +##### 4.5.13.3.0 General + +For WB-E-UTRAN, 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 [35]). The extended idle mode DRX cycle length is negotiated via NAS signalling according to clause 4.5.13.1. The MME includes the extended idle mode DRX cycle length for WB-E-UTRAN or NB-IoT in paging message to assist the eNodeB in paging the UE. + +NOTE: Heterogeneous support of extended idle mode DRX in tracking areas assigned by MME in a TAI list can result in significant battery life reduction in the UE as compared to homogeneous support by eNodeBs of extended idle mode DRX. + +For extended idle mode DRX cycle length of 5.12s, regular paging strategy as defined in TS 23.401 [7] is used. + +For extended idle mode DRX cycle length of 10.24s or longer, clauses 4.5.13.3.1, 4.5.13.3.2 and 4.5.13.3.3 apply. + +##### 4.5.13.3.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 [35]. This value can be computed at all UEs and MMEs without need for signalling. The MME includes the extended idle mode DRX cycle length and the PTW length in paging message to assist the eNodeB in paging the UE. + +The MME also assigns a Paging Time Window length, and provides this value to the UE during attach/TAU 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 [35]. 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 [35]. After the Paging Time Window length, the MME considers the UE unreachable for paging until the next Paging Hyperframe. + +##### 4.5.13.3.2 Loose Hyper SFN synchronization + +NOTE: This clause applies for extended DRX cycle lengths of 10.24s or longer. + +In order for the UE to be paged at roughly similar time, the H-SFN of all eNodeBs and MMEs should be loosely synchronized. + +Each eNodeB and MME synchronizes internally the H-SFN counter so that the start of H-SFN=0 coincides with the same a preconfigured time epoch. If eNodeBs and MMEs use different epochs, e.g. due to the use of different time references, the GPS time should be set as the baseline, and the eNodeBs and MMEs 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 eNodeBs and MMEs 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. + +##### 4.5.13.3.3 MME paging and paging retransmission strategy + +NOTE: This clause applies for extended DRX cycle lengths of 10.24s or longer. + +When the MME receives trigger for paging and the UE is reachable for paging, the MME sends the paging request. If the UE is not reachable for paging, then the MME pages the UE just before the next paging occasion. + +The MME determines the Paging Time Window length based on paging retransmission strategy, and uses it to execute the retransmission scheme. + +If the UE is unreachable for paging, then MME may follow clause 4.5.7 "High latency communication" for functionality related to Mobile Terminated communication with high latency. + +### 4.5.14 Non-IP Data Delivery (NIDD) + +#### 4.5.14.1 General + +Functions for NIDD may be used to handle mobile originated (MO) and mobile terminated (MT) communication with UEs, where the data used for the communication is considered unstructured from the EPS standpoint (which we refer to also as Non-IP). The support of Non-IP data is part of the CIoT EPS optimizations. The Non-IP data delivery to SCS/AS is accomplished by one of two mechanisms: + +- Delivery using SCEF; +- Delivery using a Point-to-Point (PtP) SGi tunnel. + +The delivery using a Point-to-Point (PtP) SGi tunnel is further described in TS 23.401 [7]. + +NIDD via the SCEF is handled using a PDN connection to the SCEF. The UE may obtain a Non-IP PDN connection to the SCEF either during the Attach procedure (see clause 5.3.2.1 of TS 23.401 [7]) or via UE requested PDN connectivity (see clause 5.10.2 of TS 23.401 [7]) or via PDP Context Activation Procedure (see clause 9.2.2.1 of TS 23.060 [6]). + +NOTE 1: The UE is not made aware that a particular Non-IP PDN connection is provided via SCEF or via PGW. However, the network informs the UE whether a particular Non-IP PDN connection uses Control plane CIoT Optimization (see TS 23.401 [7]). + +An association between the SCS/AS and a PDN Connection to the SCEF needs to be established to enable transfer of non-IP data between the UE and the SCS/AS. When the Reliable Data Service is not enabled, the SCEF determines the association based on provisioned policies that may be used to map an SCS/AS identity and User identity to an APN. + +When the Reliable Data Service is enabled, the SCEF determines the association based on port numbers and provisioned policies that may be used to map SCS/AS identities and User identity to an APN (see clause 4.5.14.3). + +NOTE 2: When more than one SCS/AS is associated with the same PDN Connection, it is permissible for packets to or from one port number to be associated with more than one SCS/AS. Also, any policies that are applied to the PDN Connection (e.g. APN Rate Control), apply to traffic from all of the SCS/AS's that are associated with the PDN Connection. + +NIDD via SCEF uses the User Identity, APN, and the SCS/AS identity to identify which UE a particular T6a/T6b connection belongs to. The User Identity is the user's IMSI. The user's IMSI shall not be used on the interface between SCEF and SCS/AS. In order to perform NIDD configuration or to send or receive NIDD data, the SCS/AS shall use MSISDN or External Identifier to identify the user. In order to facilitate correlation of SCS/AS requests to T6a/T6b connection for a given UE, the HSS provides to the SCEF (see NIDD Configuration procedure in clause 5.13.2) the user's IMSI, and if available, the MSISDN (when NIDD Configuration Request contains an External Identifier) or if available, External Identifier (when NIDD Configuration Request contains an MSISDN). + +Depending on operator configuration, the SCEF may perform buffering of MO and/or MT Non-IP data. In this release of specification, neither the MME/SGSN nor the IWK-SCEF are expecting to buffer data pertinent to PDN connection to the SCEF. + +The Protocol Configuration Options (PCO) may be used to transfer parameters between the UE and SCEF (e.g. maximum packet size). The PCO's information shall be passed transparently through the MME/SGSN. As specified in TS 23.401 [7] and TS 23.060 [6], the PCO is sent in the EPS Session Management signalling between UE and MME and in GPRS Session Management signalling between UE and SGSN. + +The SCEF applies rate control as described in clause 4.7.7 of TS 23.401 [7]. + +#### 4.5.14.2 Enhancements for reliable delivery of NIDD + +To ensure reliable delivery of Non-IP data (NIDD) between UE and SCEF using the Control Plane CIoT EPS Optimization, the following functions may be supported by the 3GPP system: + +- Reliable delivery by acknowledgements on a hop-by-hop basis, i.e. the link layer protocol on each interface used for NIDD uses acknowledgments and nodes apply retransmissions if needed to ensure reliable delivery. +- The UE may retransmit UL data that was not acknowledged by the RLC on the AS layer in the UE; +- The MME may retransmit DL data for which it got a non-delivery indication from the eNodeB (see e.g. clause 5.3.4B.3, step 15 of TS 23.401 [7]); +- The MME indicates to the SCEF the status of the DL data delivery. The SCEF may forward this status to the AS; +- Disabling/enabling of MME retransmission is handled by a subscription parameter 'Acknowledgements of downlink NAS data PDUs'. + +#### 4.5.14.3 Reliable Data Service + +The Reliable Data Service may be used by the UE and SCEF or P-GW when using PDN Connection of PDN Type 'Non-IP'. The service provides a mechanism for the SCEF or P-GW to determine if the data was successfully delivered to the UE and for UE to determine if the data was successfully delivered to the SCEF. When a requested acknowledgement is not received, the Reliable Data Service retransmits the packet. The service is enabled or disabled based on APN Configuration per SLA. + +When the service is enabled, a protocol is used between the end-points of the Non-IP PDN Connection. 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. Reliable Data Service 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, the SCEF and the P-GW may support reservation of the source and the destination port numbers for their use and subsequent release of the reserved port numbers. Reliable Data Service protocol (as defined in TS 24.250 [47]) 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. + +During NIDD Configuration, the SCS/AS 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 SCEF. When port numbers are reserved by the SCEF, 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 SCS/AS indicated that it supports multiple serialization formats, the SCEF determines the serialization format that it will indicate to the UE based on local policies and previous negotiations with the UE (e.g. the SCEF 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 SCEF stores the serialization formats as part of the Reliable Data Service Configuration and provides the updated Reliable Data Service Configuration to the SCS/AS. + +NOTE: Whether the UE Application or SCS/AS supports a given serialization format is outside the scope of 3GPP specifications. + +The UE indicates its capability of supporting Reliable Data Service in the Protocol Configuration Options (PCO) to the SCEF or P-GW. If SCEF or P-GW supports and accepts Reliable Data Service then it indicates to the UE, in the PCO, that the Reliable Data Service shall be used if enabled in the APN configuration. + +In order to prevent situations where a Reliable Data Service instance needs to interface to both the user and control plane, the Reliable Data Service may only be used with PDN connections for which the "Control Plane Only" indicator is set or with PDN connections using the Control Plane EPS CIoT Optimization when the MME does not move PDN connections to the user plane. The Control Plane CIoT EPS Optimization is defined in TS 23.401 [7]. + +### 4.5.15 Support of PFD management via SCEF + +The PFDs may be managed by the 3rd party SCS/AS via the SCEF, which ensures the secure access to the operator's network even from the 3rd party SCS/AS in untrusted domain. The 3rd party SCS/AS may request to create, update or remove PFDs in the PFDF via the SCEF. + +The specific procedure for PFD management via SCEF is described in clause 5.14.1. + +### 4.5.16 MSISDN-less MO-SMS via T4 + +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. Support for subscription without MSISDN is defined in TS 23.012 [36]. + +The UE is pre-configured with the Service Centre address that points to SMS-SC that performs this MO-SMS delivery via MTC-IWF delivery procedure. The recipient of this short message is set to the pre-configured address of the SCS/AS (i.e. Address of the destination SME). If UE has multiple external IDs associated to the same IMSI, the external ID 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 [12]). The MTC-IWF may obtain the external-ID by querying the HSS with the IMSI and application port ID via S6m. + +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. + +NOTE: This way of communicating small data is considered an intermediate method that will eventually be replaced by Non-IP Data Delivery (NIDD) procedures. + +### 4.5.17 Enhanced Coverage Restriction Control via SCEF + +Restriction of use of the Enhanced Coverage is specified in TS 23.060 [6] and TS 23.401 [7] + +The support for Enhanced Coverage Restriction Control via SCEF enables 3rd party service providers to query status of, enhanced coverage restriction or enable/disable enhanced coverage restriction per individual UEs. The specific procedure for Enhanced Coverage Restriction Control via SCEF is described in clause 5.16. + +### 4.5.18 MBMS user service for UEs using power saving functions + +MBMS Bearer Services as defined in TS 23.246 [29] together with MBMS User Services defined in TS 26.346 [38], or MBMS Bearer Services accessed via the MB2 interface defined in TS 23.468 [30], provide means to deliver data or + +triggering payload over broadcast to multiple UEs at the same time. However, for UEs using power saving functions, e.g. Power Saving Mode (defined in clause 4.5.4) or extended idle mode DRX (defined in clause 4.5.13), the UEs are usually unreachable for long periods of time. Moreover, different UEs are likely to be reachable at different times. Therefore, it is important that the time intervals the UE stays awake to receive MBMS user service or to discover if there is any MBMS user service scheduled for delivery, should not necessarily be the same as the reachable intervals negotiated for extended idle mode DRX or PSM. + +If a UE becomes unreachable for unicast service due to either PSM or extended idle mode DRX, the UE may still perform MBMS specific procedures, e.g. activation/deactivation of the MBMS bearer service, MBMS data transfer reception, reception of service announcement (if needed), as defined in TS 23.246 [29] and TS 26.346 [38]. + +For those intervals the UE needs to be awake for MBMS bearer service, the following cases can be identified: + +1. When the UE's need to be awake due to MBMS coincides with the UE already being in connected mode due to other reasons, the UE follows normal connected mode procedures. +2. When the UE's need to be awake due to MBMS coincides with the UE already being in idle mode and reachable (e.g. in active time for PSM or PTW for eDRX) the UE follows normal idle mode procedure. +3. When the UE's need to be awake due to MBMS coincides with the UE being in idle mode and in deep sleep, i.e. unreachable for paging to the network, the UE leaves the deep sleep state only to perform procedures related to MBMS service. + - If the MBMS user service does not require the UE to transition to connected mode, i.e. the UE receives MBMS user service in idle mode, then the UE does not update the MME to become reachable for paging. The UE would therefore still be considered unreachable for paging in the MME. This minimizes the signalling between the UE and the network. + - If the MBMS user service requires the UE to transition to connected mode (e.g. for HTTP reception reporting, file repair, etc.) then the UE performs regular procedures for ECM connected mode. This would therefore make the UE become reachable in the network for other unicast services. +4. When the UE is in the middle of an MBMS data transfer, and the UE is scheduled to move to deep sleep due to power saving, e.g. end of PTW for extended idle mode DRX or expiration of active time for PSM, then the UE does not go to deep sleep during the remainder of the current MBMS data transfer. + +NOTE 1: If at the end of the current MBMS data transfer, the UE knows there is another MBMS data transfer scheduled soon, in that case depending of the time between MBMS data transfers, the UE can decide to go to sleep between MBMS data transfers. + +There are two possible ways the UE can be notified of an upcoming MBMS broadcast session start: + +1. If MBMS User Services defined in TS 26.346 [38] is used, the UE needs to receive MBMS service announcement while awake (i.e. while in connected mode, or while idle mode during PTW for extended idle mode DRX, or active time for PSM). The UE wakes up if not already awake for MBMS service reception based on the schedule received in the service announcement. For this option, the MBMS service announcement may be provided via MBMS broadcast service announcement or via any of the possible unicast service announcement delivery mechanisms defined in TS 23.246 [29]. If MBMS access via the MB2 interface as defined in TS 23.468 [30] is used, similar mechanisms need to be provided by the application layer using unicast mechanisms. + +NOTE 2: In order to allow all UEs using power saving function to receive the service announcement in time to be able to receive the MBMS broadcast data delivery, the application server needs to be aware of the maximum unreachable period of the UEs. + +2. The UE may be configured by the application server with specific times to perform MBMS procedures, and wakes up from deep-sleep if needed at those times. The UE may also receive MBMS service announcements and/or MBMS broadcast delivery at those times (if needed). + +NOTE 3: The configuration (e.g. TMGI, start time) is out of scope of 3GPP and assumed to be performed between application server and UE at application layer. The application server needs to initiate MBMS bearer service procedures during those time intervals. + +### 4.5.19 Enhancements to Location Services for CIoT + +Location Services (LCS) are defined in TS 23.271 [33]. In order to support Location Services for CIoT UEs, following enhancements to Location Services are defined (refer to TS 23.271 [33] for detailed procedures): + +- Deferred location for the UE availability event: + - When extended idle mode DRX or PSM is used, a deferred location request for UE available event allows an LCS Client to obtain the UE location as soon as the UE becomes available. +- NOTE: Without deferred location for UE available event, an LCS Client can configure a Monitoring Event for UE Reachability and issue a Mobile Terminated Location Request (MT-LR) when the UE reachability is reported, but this will fail if the UE becomes unreachable again before the MT-LR is performed. +- The procedures for deferred location from V-GMLC to the external client and the EPC Mobile Terminating Location Request (EPC-MT-LR) procedure are combined properly in the V-GMLC as specified TS 23.271 [33]. + - Indication of UE RAT type and/or coverage level to Evolved Serving Mobile Location Centre (E-SMLC): + - Providing an E-SMLC with an indication of the RAT type and/or the coverage level may enable the E-SMLC to appropriately determine a maximum size, maximum frequency and maximum transfer delay for positioning messages sent to and from the UE. + - RAT type and coverage level indications from the MME to the E-SMLC are introduced in TS 23.271 [33]. + - For the case of coverage level, and indication of coverage level from eNB to MME is introduced. + - Support of UE positioning measurements in idle mode: + - NB-IoT UEs or Cat-M1 UEs may perform measurements for some positioning methods only when in ECM-IDLE state due to minimal resources. + - An E-SMLC that is aware of this (e.g. from an indication sent by the UE) may allow additional response time to the UE (e.g. in the QoS) to obtain the measurements. An MME that is aware of this (e.g. from the UE access type) may also allow additional time for a location session to complete. + - Addition of Periodic and Triggered Location for EPC: + - A flexible periodic and/or triggered Mobile Terminated Location Request (MT-LR) capability is useful to enable UE location at times other than when a UE normally becomes available and/or with better granularity than a cell ID. + - New procedures are introduced in TS 23.271 [33] to initiate and maintain deferred periodic and triggered event reporting and to cancel reporting by an LCS client, UE or network entity. The area event, periodic event and motion event are clarified in the context of EPC access. Impacts to LCS messages between an LCS Client and GMLC, between GMLCs and between an H-GMLC and PPR are included. + - Support of Last Known Location for a UE that are unreachable for long periods of times: + - For UEs that are unreachable for long periods of time, e.g. using extended idle mode DRX or PSM, last known location support enables an external LCS client to receive some information on UE location without waiting (e.g. a few hours) for the UE to become reachable. + - The EPC-MT-LR procedure defined in TS 23.271 [33] is enhanced to support last known location based on a last known serving cell. + +### 4.5.20 MBMS user service for NB or M UE categories + +TS 36.306 [41] defines UE categories M1, M2 for WB-E-UTRAN and NB1, NB2 for NB-IoT that can only support limited bandwidth and transport block size. In order for UEs of these categories to be able to receive MBMS service, E-UTRAN needs to be able to determine the UE category that applies to the specific service indicated by the TMGI. + +In order for E-UTRAN to know the UE categories for MBMS bearer service, the UE Capability for MBMS (which includes UE Category for MBMS and optionally associated coverage level for MBMS) is provided by SCS/AS to the + +BMSC via the SCEF. Using PLMN specific QCI information, the characteristics are signalled by the BM-SC to E-UTRAN following the procedures described in clause 5.5.1 of the present specification and TS 23.246 [29]. This includes: + +- QCI(s) that are determined taking into account the UE Category for MBMS that indicates the "M" or "NB" category (M1, M2, NB1, NB2) as defined in TS 36.306 [41] that can receive the service indicated by the TMGI. E-UTRAN uses the QCI to determine the radio parameters that would determine the categories of UEs that are required to receive the service. EUTRAN is configured with the QCI to UE Category for MBMS mapping. + +NOTE 1: The way UE Category for MBMS needs to be interpreted is to allow PLMN specific QCI to be derived by the BMSC that would allow the MBMS service to be received by each UE type. For example, for UE Category for MBMS "M1 and M2", a QCI will be derived that will map to radio configuration that would allow M1 and M2 UEs to receive the service over the radio interface. For UE Category Info "NB2", a QCI will be derived that will map to radio configuration that would allow only NB2 UEs to receive the service over the radio interface. + +- Optionally, the SCS/AS may provide additional information regarding the coverage level for the related MBMS service. The coverage level indicates if the MBMS service is intended to be received by UEs located in extended coverage and is used by E-UTRAN to determine the radio configuration required, e.g. determine the number of repetitions, to reach the UEs that receive the MBMS service. Three levels of Coverage Level for MBMS are defined as "normal", "medium" and "high". The coverage level information, when provided, shall be reflected via the QCI. + +NOTE 2: It is up to E-UTRAN implementation how the coverage level information can be used. + +NOTE 3: A single QCI does not allow for both NB and M category UEs to receive the same service indicated by one TMGI. + +### 4.5.21 Network Parameter Configuration via SCEF + +The SCS/AS may issue network parameter configuration requests to the network, via the SCEF, to suggest parameter values that may be used for Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets. By suggesting values for these parameters, the SCS/AS may influence certain aspects of UE/network behaviour such as the UE's PSM, extended idle mode DRX, and extended buffering configurations. Based on operator's configuration, the SCEF and HSS may choose to accept, reject or modify the suggested configuration parameter value. The SCEF indicates accepted/modified values to the SCS/AS. This feature can also be used to suggest parameter values for a group of UEs. + +NOTE: The SCS/AS can observe how the MME ultimately configures the UE for PSM and extended idle mode DRX by configuring "UE Reachability" or "Availability after DDN failure" notifications with the Idle Status Indication option (see clause 4.5.7). + +The specific procedure for Network Parameter Configuration via SCEF is described in clause 5.18. + +### 4.5.22 RACS information provisioning + +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 TS 23.401 [7]. Provisioning of Manufacturer-assigned UE Radio Capability ID entries in the UCMF is performed from an AS that interacts with the UCMF either directly (according to TS 23.502 [48] and TS 29.675 [49]) or via the SCEF (according to TS 29.122 [44] or via Network Management). + +### 4.5.23 Support of satellite access + +Support of satellite access for NB-IoT, WB-E-UTRAN and LTE-M is specified in TS 23.401 [7]. Unless otherwise stated in this specification, MTC functionality applies to NB-IoT, WB-E-UTRAN and LTE-M over satellite access. To support satellite access for NB-IoT, WB-E-UTRAN and LTE-M, the system enhancements including satellite RAT type, network/access selection, verification of UE location and Tracking Area Update, etc., are defined in TS 23.401 [7]. + +## 4.6 Identifiers + +### 4.6.1 General + +Identifiers relevant for the 3GPP network are specified in TS 23.003 [4]. + +### 4.6.2 External Identifier + +A subscription used for MTC has one IMSI and may have one or several External Identifier(s) that are stored in the HSS. If there are several External Identifiers, the HSS shall store one default External Identifier and one or more additional External Identifiers. + +NOTE 1: If several External Identifiers are mapped to one IMSI, some functions might not work in this release of the specification. + +External Identifier shall be globally unique. It shall have the following components: + +- a. Domain Identifier: identifies a domain that is under the control of a Mobile Network Operator (MNO). The Domain Identifier is used to identify where services provided by the operator network can be accessed (e.g. MTC-IWF or SCEF provided services). An operator may use different domain identifiers to provide access to different services and/or MTC Service Providers. +- b. Local Identifier: Identifier used to derive or obtain the IMSI. The Local Identifier shall be unique within the applicable domain. It is managed by the Mobile Network Operator. + +NOTE 1: Use of External Identifiers is not restricted to MTC only. + +NOTE 2: Use of IMSI outside the 3GPP operator domain is dependent on the operator policy. + +### 4.6.3 External Group Identifier + +A subscription used for MTC may be associated to one or several IMSI-Group Identifier(s) (see TS 23.003 [4]) that are stored in the HSS. + +A subscription may be associated to one or several External Group Identifier(s) that are stored in the HSS. The External Group Identifier shall be formatted the same as the External Identifier that is described in clause 4.6.2. The Local Identifier is used to derive or obtain an IMSI-Group Identifier. An External Group Identifier maps to an IMSI-Group Identifier. An IMSI-Group Identifier maps to zero, one or several External Group Identifiers. + +The External Group Identifier is used on the interface between the SCS/AS and the SCEF and on the interface between the SCEF and the HSS. This identifier is used in procedures such as group message delivery, communication pattern provisioning, and monitoring event configuration and deletion. When the External Group Identifier is used in the communication pattern provisioning or monitoring event configuration and deletion procedures, the HSS shall be able to resolve the External Group Identifier to an IMSI-Group Identifier and the associated External Identifier or MSISDN for each of the IMSIs in the IMSI-Group. The purpose of this association is to enable the SCEF to determine what UE Identifier to use (MSISDN or External Identifier) and derive APN from SCS/AS Identifier and the MSISDN or External Identifier to route non-IP data to the UE when non-IP data is sent to an External Group Identifier. + +NOTE: Additional information can assist HSS to resolve the IMSI-Group Identifier to MSISDN or External Identifier for each of the IMSIs in the IMSI-Group, e.g. Provider Information, Service information (e.g. NIDD, MONTE). How the HSS resolves to one of the UE Identifier(s) (MSISDN or External Identifier) in a UE's subscription is implementation specific. + +## 4.7 Addressing + +For UEs used for Machine-Type Communications (MTC) IP Addressing principles and solutions for different scenarios are described in clause 5 of TS 23.221 [21]. + +## 4.8 Security Aspects + +### 4.8.1 Security Requirements + +#### 4.8.1.0 General + +Security requirements are described in TS 33.187 [25]. + +#### 4.8.1.1 Void + +#### 4.8.1.2 Void + +## 4.9 SCEF - SCS/AS API Procedures + +### 4.9.1 General + +This clause identifies commonalities (for both parameters and procedures) found on T8 interface. + +### 4.9.2 Common Parameters + +This clause defines parameters which are required on T8 interface: + +T8 Long Term Transaction Reference ID (TLTRI) is a parameter which refers to long term transaction (e.g. NIDD Configuration, Group Message Request, Monitoring Event configuration) between the SCEF and the SCS/AS when using T8 interface. Long term transactions consist of one or more request messages which may have one or more response messages. TLTRI is assigned by the SCEF and is unique through the duration of the transaction. It is stored on both the SCEF and the SCS/AS for the duration of the transaction. + +NOTE 1: Short term transaction identifiers for the T8 interface are not described in this specification as stage 3 mechanisms (defined in TS 29.122 [44]) ensure the correlation between request and response message. + +T8 Destination Address is a parameter that is included by the SCS/AS in T8 messages where the SCS/AS can request response to a specific address. + +Accuracy is an optional parameter which indicates the desired level of accuracy of the requested location information. It may be at cell level (CGI/ECGI) for GPRS/UTRAN/E-UTRAN, or (eNodeB-ID) eNodeB level, or (TAI/RAI) TA/RA level, or (PLMN-ID) PLMN-level, or TWAN identifier in TWAN access, or other formats, e.g. shapes (e.g. polygons, circles, etc.) or civic addresses (e.g. streets, districts etc.) or geographic co-ordinate (latitude, longitude), etc. + +NOTE 2: The exact definition of other formats such as shapes or civic addresses or geographic coordinate is left up to Stage 3. + +Idle Status Indication is an optional parameter that allows the SCS/AS to retrieve extra information, e.g. as specified in step 5 of clause 5.6.3.3, when a UE, for which PSM or extended idle mode DRX is enabled, transitions into idle mode. + +TLTRI for Deletion identifies the TLTRI of the long-term transaction being requested for deletion. + +## 4.10 Charging Principles + +Depending on operator configuration, accounting functionality for transactions over T8 may be supported by the SCEF. + +NOTE: The details of the required accounting information are outside the scope of the present document. + +Depending on operator configuration the MME, SGSN, SCEF and IWK-SCEF support accounting functionality for Monitoring Events, and NIDD via SCEF feature. + +Accounting and charging information support for Monitoring Events is specified in TS 32.240 [28] and TS 32.278 [39]. + +Accounting and charging information support for NIDD via SCEF feature is specified in TS 32.240 [28] and TS 32.253 [40]. + +# 5 Functional Description and Information Flow + +## 5.1 Control and user plane + +### 5.1.1 Control Plane + +#### 5.1.1.1 HSS – MTC-IWF + +![Diagram of the Control Plane for S6m interface between HSS and MTC-IWF.](9e5d66cdb5112ad5cab89552b126e4b9_img.jpg) + +The diagram illustrates the protocol stack for the S6m interface between the HSS and the MTC-IWF. It consists of two vertical protocol stacks, one for the HSS on the left and one for the MTC-IWF on the right, connected by a central vertical line representing the S6m interface. Both stacks have five layers, which are aligned horizontally across the interface. From top to bottom, the layers are: Diameter, SCTP, IP, L2, and L1. The labels 'HSS', 'S6m', and 'MTC-IWF' are positioned below their respective columns. + +| | | | +|----------|-----|----------| +| Diameter | | Diameter | +| SCTP | | SCTP | +| IP | | IP | +| L2 | | L2 | +| L1 | | L1 | +| HSS | S6m | MTC-IWF | + +Diagram of the Control Plane for S6m interface between HSS and MTC-IWF. + +##### Legend: + +- **Diameter:** This protocol supports transferring of subscription and UE related information for identifier mapping and serving node information retrieval between MTC-IWF and HSS (S6m). Diameter is defined in RFC 3588 [15]. +- **Stream Control Transmission Protocol (SCTP):** This protocol transfers signalling messages. SCTP is defined in RFC 4960 [16]. + +Figure 5.1.1.1-1: Control Plane for S6m interface + +NOTE: It is up to stage3 to define interworking between diameter-based s6m and map-based interface to the legacy HLR. + +## 5.2 Device triggering procedures + +### 5.2.1 Device triggering procedure over Tsp + +![Sequence diagram of the device triggering procedure over Tsp. Lifelines: UE, MSC/SGSN/MME, PGW/GGSN, SMS-SC, HSS/HLR, MTC-IWF, DNS, SCS. The sequence starts with the SCS sending a '1. Query DNS' to the DNS. The DNS responds with '2. Device Trigger Request' to the SCS. The SCS then sends '3. Authorization & load control' to the MTC-IWF. The MTC-IWF sends '4. Subscriber Information Request' to the HSS/HLR, which responds with '5. Subscriber Information Response'. The MTC-IWF then performs '6. T4 Trigger delivery selection'. A large box labeled 'T4 device trigger delivery procedure' spans across the bottom of the main sequence. After this box, the MTC-IWF sends '7. Device Trigger Report' to the SCS. Finally, a box labeled '8. Action in response to Device Trigger' spans across the bottom of the sequence.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +``` + +sequenceDiagram + participant SCS + participant DNS + participant MTC-IWF + participant HSS/HLR + participant UE + Note right of SCS: 1. Query DNS + SCS-->DNS: + Note right of SCS: 2. Device Trigger Request + SCS->>MTC-IWF: 3. Authorization & load control + MTC-IWF->>HSS/HLR: 4. Subscriber Information Request + HSS/HLR-->>MTC-IWF: 5. Subscriber Information Response + Note right of MTC-IWF: 6. T4 Trigger delivery selection + Note over UE, HSS/HLR: T4 device trigger delivery procedure + Note right of MTC-IWF: 7. Device Trigger Report + MTC-IWF->>SCS: + Note over UE, HSS/HLR: 8. Action in response to Device Trigger + +``` + +Sequence diagram of the device triggering procedure over Tsp. Lifelines: UE, MSC/SGSN/MME, PGW/GGSN, SMS-SC, HSS/HLR, MTC-IWF, DNS, SCS. The sequence starts with the SCS sending a '1. Query DNS' to the DNS. The DNS responds with '2. Device Trigger Request' to the SCS. The SCS then sends '3. Authorization & load control' to the MTC-IWF. The MTC-IWF sends '4. Subscriber Information Request' to the HSS/HLR, which responds with '5. Subscriber Information Response'. The MTC-IWF then performs '6. T4 Trigger delivery selection'. A large box labeled 'T4 device trigger delivery procedure' spans across the bottom of the main sequence. After this box, the MTC-IWF sends '7. Device Trigger Report' to the SCS. Finally, a box labeled '8. Action in response to Device Trigger' spans across the bottom of the sequence. + +**Figure 5.2.1-1: Device triggering procedure over Tsp** + +1. The SCS determines the need to trigger the device. If the SCS has no contact details for an MTC-IWF, it may determine the IP address(es)/port(s) of the MTC-IWF by performing a DNS query using the External Identifier or using a locally configured MTC-IWF identifier. +2. The SCS sends the Device Trigger Request (External Identifier or MSISDN, SCS Identifier, trigger reference number, validity period, priority, Application Port ID and trigger payload) message to the MTC-IWF. The SCS includes a trigger payload that contains the information destined for the MTC application, along with the information to route it to the MTC application. The Application Port ID is set to address a triggering function within the UE. + +NOTE 1: The assignment of SCS identifier is out of scope of 3GPP. The SCS identifier should meet the 3GPP / operator requirement. As an example it may be possible to use MSISDN as SCS identifier. + +3. The MTC-IWF checks that the SCS is authorised to send trigger requests and that the SCS has not exceeded its quota or rate of trigger submission over Tsp. If this check fails the MTC-IWF sends a Device Trigger Confirm message with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise, the flow continues with step 4. +4. The MTC-IWF sends a Subscriber Information Request (External Identifier or MSISDN and SCS Identifier) message to the HSS/HLR to determine if SCS is authorized to trigger the UE, to resolve the External Identifier or MSISDN to IMSI and retrieve the related HSS stored "Routing information" including the identities of the UE's serving CN node(s). + +NOTE 2: The MTC-IWF may cache authorization and routing information for the UE. However, this may increase the probability of trigger delivery attempt failures when the cached serving node information is stale. + +NOTE 3: Optionally, mapping from External Identifiers to MSISDN is also provided for legacy SMS infrastructure not supporting MSISDN-less SMS. + +5. The HSS/HLR sends the Subscriber Information Response (IMSI and/or MSISDN and related "Routing information" including the serving node(s) identities, cause) message. HSS/HLR policy (possibly dependent on the VPLMN ID) may influence which serving node identities are returned. If the cause value indicates the SCS is not allowed to send a trigger message to this UE, or there is no valid subscription information, or "Absent subscriber" is received from HSS and the validity period of this trigger message is set to zero, the MTC-IWF sends a Device Trigger Confirm message with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise this flow continues with step 6a. +6. The MTC-IWF attempts T4 trigger delivery procedure according to clause 5.2.2. MTC-IWF may deliver device trigger as DL user data to the UE via SCEF using mobile terminated NIDD procedure as defined in clause 5.13.3. Otherwise, this flow continues with step 7. +7. The MTC-IWF sends the Device Trigger Report (External Identifier or MSISDN and trigger reference number) message to the SCS with a cause value indicating the trigger delivery outcome (e.g. succeeded, unknown or failed and the reason for the failure). The MTC-IWF generates the necessary CDR information including the External Identifier or MSISDN and SCS Identifier. +8. In response to the received device trigger, the UE takes specific actions that take into consideration the content of the trigger payload. This response typically involves initiation of immediate or later communication with the SCS or an AS. + +### 5.2.2 Trigger Delivery using T4 + +![Sequence diagram illustrating the T4 Trigger Delivery Flow between UE, MSC/MME SGSN IP-SM-GW, PGW GGSN, SMS-SC/GMSC/IWMSC, HSS/HLR, MTC-IWF, DNS, and SCS.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MSC/MME_SGSN_IP_SM_GW as MSC/MME SGSN IP-SM-GW + participant PGW_GGSN as PGW GGSN + participant SMS_SC_GMSC_IWMSC as SMS-SC/GMSC/IWMSC + participant HSS_HLR as HSS/HLR + participant MTC_IWF as MTC-IWF + participant DNS + participant SCS + + Note right of SMS_SC_GMSC_IWMSC: 7. CDR Generation + + MTC-IWF->>SMS-SC/GMSC/IWMSC: 1. Submit Trigger + SMS-SC/GMSC/IWMSC->>MTC-IWF: 2. Submit TriggerConfirm + MTC-IWF->>DNS: 3. Device Trigger Confirm + SMS-SC/GMSC/IWMSC->>MSC/MME SGSN IP-SM-GW: 4. Forward Message + MSC/MME SGSN IP-SM-GW->>UE: 5. Transfer Message + MSC/MME SGSN IP-SM-GW->>SMS-SC/GMSC/IWMSC: 6. Delivery Report + Note right of SMS-SC/GMSC/IWMSC: 7. CDR Generation + SMS-SC/GMSC/IWMSC->>HSS/HLR: 8. SM-Delivery Report-Status + SMS-SC/GMSC/IWMSC->>MTC-IWF: 9. Message Delivery Report + +``` + +Sequence diagram illustrating the T4 Trigger Delivery Flow between UE, MSC/MME SGSN IP-SM-GW, PGW GGSN, SMS-SC/GMSC/IWMSC, HSS/HLR, MTC-IWF, DNS, and SCS. + +Figure 5.2.2-1: T4 Trigger Delivery Flow + +1. The MTC-IWF selects a suitable SMS-SC based on configured information. The MTC-IWF sends a Submit Trigger (External Identifier or MSISDN, IMSI, SCS Identifier, trigger reference number, validity period, priority, serving node ID(s) if available from HSS, SMS Application port ID, trigger payload, Trigger Indication) message to the SMS-SC. The SMS-SC should avoid an initial HSS/HLR interrogation (SRI for SM) when it has already received necessary parameters in the Submit Trigger message from the MTC-IWF. The MTC-IWF forwards the Application Port ID received from SCS as the SMS Application port ID which is used to address the triggering function within the UE. The Trigger Indication is a standardised identifier to allow the UE and the + +network to distinguish an MT message carrying device triggering information from any other type of messages. The SMS-SC does any necessary segmentation for larger messages. + +If the MTC-IWF indicates that "Absent subscriber" was received from HSS, the SMS-SC should not submit the message, but store it directly and send Routing Information for SM to request the HSS to add the SMS-SC address to the Message Waiting List. + +2. The SMS-SC sends a Submit Trigger Confirm message to the MTC-IWF to confirm that the submission of the SMS has been accepted by the SMS-SC. +3. The MTC-IWF sends a Device Trigger Confirm message to the SCS to confirm that the Device Trigger Request has been accepted for delivery to the UE. +- 4, 5, 6. The short message is delivered to the UE (see MT-SMS procedures specified in TS 23.040 [12]). This may involve delivery attempts in MSC or MME, SGSN or over IMS via IP-SM-GW (see MT-SMS without MSISDN procedures specified in TS 23.204 [13]). + +The SMS-delivered trigger payload is processed and handled by the triggering function in the UE. Any information contained within the trigger payload is forwarded to the related or addressed UE-application. + +7. The SMS-SC generates the necessary CDR information and includes the SCS Identifier. The SMS Application port ID which is included in the SM User Data Header and the Trigger Indication are included in the CDRs in order to enable differentiated charging. The SMS-SC stores the trigger payload, without routing information. If the message delivery fails and is attempted to be delivered again, HSS interrogation will be performed. +8. If the message delivery fails and the validity period of this trigger message is not set to zero, the SMS-SC shall send a SM Message Delivery Status Report to request the HSS to add the SMS-SC address to the Message Waiting list. When the message delivery is later re-attempted, a new HSS interrogation will be performed by the SMS-GMSC using IMSI or MSISDN. HSS interrogations using IMSI shall not be forwarded or relayed to SMS-Router or IP-SM-GWs. HSS may include up to three serving node identities (MSC or MME, SGSN, IP-SM-GW) in the response to SMS-GMSC. +9. If the message delivery fails and depending on the failure cause either directly or when validity period of the trigger message expires, or when the message delivery succeeds, the SMS-SC shall send a Message Delivery Report (cause code, trigger reference number, SCS Identifier) to the MTC-IWF. + +### 5.2.3 Device triggering recall/replace procedures + +#### 5.2.3.1 Device trigger recall/replace procedure over Tsp + +![Sequence diagram illustrating the Device trigger recall/replace procedure over Tsp. The diagram shows interactions between UE, MSC/MME SGSN IP-SM-GW, SMS-SC/GMSC/IWMSC, HSS/HLR, MTC-IWF, and SCS.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) + +``` + +sequenceDiagram + participant SCS + participant MTC-IWF + participant HSS/HLR + participant SMS-SC/GMSC/IWMSC + participant MSC/MME_SGSN_IP_SM_GW as MSC/MME +SGSN +IP-SM-GW + participant UE + + Note right of SCS: 1. Device Action Request +(Action Type = Recall/Replace) + SCS->>MTC-IWF: 1. Device Action Request +(Action Type = Recall/Replace) + Note right of MTC-IWF: 2. Subscriber Information Request + MTC-IWF->>HSS/HLR: 2. Subscriber Information Request + Note right of HSS/HLR: 3. Subscriber Information Response + HSS/HLR->>MTC-IWF: 3. Subscriber Information Response + Note right of MTC-IWF: 4. T4 Device Trigger Recall/Replace procedure + MTC-IWF->>SMS-SC/GMSC/IWMSC: 4. T4 Device Trigger Recall/Replace procedure + Note right of SMS-SC/GMSC/IWMSC: 5. Device Action Answer +(Result = Failure/Success) + SMS-SC/GMSC/IWMSC->>MTC-IWF: 5. Device Action Answer +(Result = Failure/Success) + Note right of MTC-IWF: 6. For trigger replace request, deliver new trigger message using T4 + MTC-IWF->>UE: 6. For trigger replace request, deliver new trigger message using T4 + +``` + +Sequence diagram illustrating the Device trigger recall/replace procedure over Tsp. The diagram shows interactions between UE, MSC/MME SGSN IP-SM-GW, SMS-SC/GMSC/IWMSC, HSS/HLR, MTC-IWF, and SCS. + +Figure 5.2.3.1-1: Device trigger recall/replace procedure over Tsp + +1. The SCS determines it needs to recall/replace a trigger message that it has previously submitted. The SCS sends Device Action Request (External Identifier or MSISDN, SCS Identifier, old trigger reference number, new trigger reference number, validity period, priority, Application Port ID and trigger payload) message with action type set to "Trigger Recall Request" or "Trigger Replace Request". The SCS needs to include new trigger reference number, validity period, priority, Application Port ID and trigger payload for trigger replace request only. The old trigger reference number indicates the trigger reference number which was assigned to the previously submitted trigger message that the SCS wants to cancel. The new trigger reference number is assigned by the SCS to the newly submitted trigger message. + +If the SCS is not authorized to perform device triggering or the SCS has exceeded its quota or rate of trigger submission over Tsp, the MTC-IWF rejects the Device Action Request message with action type set to "Trigger Recall Request" or "Trigger Replace Request" by sending a Device Action Answer message with a cause value indicating the reason for the failure condition, and the flow stops at this step. + +NOTE 1: The validity period in a trigger replace request needs to be greater than zero for the MTC-IWF to attempt its delivery. + +2. The MTC-IWF sends a Subscriber Information Request (External Identifier or MSISDN and SCS Identifier) message to the HSS/HLR to determine if SCS is authorized to perform device triggering to the UE. This message is also to resolve the External Identifier or MSISDN to IMSI and retrieve the related HSS stored "Routing information" including the identities of the UE's serving CN node(s) which are needed for trigger replace request only. + +NOTE 2: Optionally, mapping from External Identifiers to MSISDN is also provided for legacy SMS infrastructure not supporting MSISDN-less SMS. + +3. The HSS/HLR sends the Subscriber Information Response (IMSI and/or MSISDN and related "Routing information" including the serving node(s) identities, cause) message. The IMSI and/or MSISDN and related "Routing information" including the serving node(s) identities in the Subscriber Information Response message is only needed for trigger replace request and not used by MTC-IWF for trigger recall request. HSS/HLR policy (possibly dependent on the VPLMN ID) may influence which serving node identities are returned. If the cause value indicates the SCS is not allowed to perform device triggering to this UE, or there is no valid subscription information, the MTC-IWF sends a Device Action Answer message with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise this flow continues with step 4. +4. If trigger message which should be recalled or replaced was submitted to a SMS-SC as defined in clause 5.2.2, T4 device trigger replace procedure according to clause 5.2.3.2 or T4 device trigger recall procedure according to clause 5.2.3.3 is performed. +5. The MTC-IWF indicates trigger recall/replace success or failure in Device Action Answer message to the SCS. The MTC-IWF generates the necessary CDR information including the External Identifier or MSISDN and SCS Identifier. + +If recall/replace of a trigger is successful, this is reflected in the "Device Trigger Report" of the original trigger message (per step 7 in clause 5.2.1) with delivery outcome "Recalled"/"Replaced". + +NOTE 3: If recall/replace of a trigger failed because the trigger was already delivered or has expired, a "Device Trigger Report" of the original trigger will already have been created with the appropriate delivery outcome. + +6. For trigger replace request, the new trigger message will be delivered to the UE immediately or when the UE is available following steps 4 - 9 as defined in clause 5.2.2. + +#### 5.2.3.2 Replace procedure for trigger delivery using T4 + +![Sequence diagram for the replace procedure for trigger delivery using T4. The diagram shows interactions between UE, MSC/MME SGSN IP-SM-GW, SMS-SC/GMSC/IWMSC, HSS/HLR, and MTC-IWF. The process starts with the MTC-IWF sending a 'Submit Trigger Replace' message to the SMS-SC. The SMS-SC checks if the trigger message is pending. If pending (Case A), it deletes the old message, stores the new one, generates a CDR, and sends a success response and a delivery report for the original message. If not pending (Case B), it generates a CDR and sends a fail response.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MSC/MME SGSN IP-SM-GW + participant SMS-SC/GMSC/IWMSC + participant HSS/HLR + participant MTC-IWF + + Note right of SMS-SC: 2. Check if the trigger message is pending at SMS-SC + + Note right of MSC/MME: 3a. Delete the stored trigger message and Store the new trigger message + Note right of MSC/MME: 4a. CDR generation + + Note right of MSC/MME: 3b. CDR generation + + Note right of MSC/MME: 5a. Submit Trigger Replace Response (Success) + Note right of MSC/MME: 6a. Trigger Delivery Report for original message (Replaced) + + Note right of MSC/MME: 4b. Submit Trigger Replace Response (Fail) + + MTC-IWF->>SMS-SC: 1. Submit Trigger Replace + SMS-SC->>MSC/MME: 2. Check if the trigger message is pending at SMS-SC + alt A: Pending (Success) + MSC/MME->>MSC/MME: 3a. Delete the stored trigger message and Store the new trigger message + MSC/MME->>MSC/MME: 4a. CDR generation + MSC/MME->>MTC-IWF: 5a. Submit Trigger Replace Response (Success) + MSC/MME->>MTC-IWF: 6a. Trigger Delivery Report for original message (Replaced) + else B: Not Pending (Fail) + MSC/MME->>MSC/MME: 3b. CDR generation + MSC/MME->>MTC-IWF: 4b. Submit Trigger Replace Response (Fail) + end + +``` + +Sequence diagram for the replace procedure for trigger delivery using T4. The diagram shows interactions between UE, MSC/MME SGSN IP-SM-GW, SMS-SC/GMSC/IWMSC, HSS/HLR, and MTC-IWF. The process starts with the MTC-IWF sending a 'Submit Trigger Replace' message to the SMS-SC. The SMS-SC checks if the trigger message is pending. If pending (Case A), it deletes the old message, stores the new one, generates a CDR, and sends a success response and a delivery report for the original message. If not pending (Case B), it generates a CDR and sends a fail response. + +**Figure 5.2.3.2-1: Replace procedure for trigger delivery using T4** + +- Based on the Action type in Device Action Request message, the MTC-IWF sends a Submit Trigger Replace (External Identifier or MSISDN, IMSI, SCS Identifier, old trigger reference number, new trigger reference number, validity period, priority, serving node ID(s) if available from HSS, SMS Application port ID, trigger payload, Trigger Indication) message to the SMS-SC. The MTC-IWF selects the SMS-SC to which the old trigger message was submitted, e.g. based on configured information. +- The SMS-SC determines whether the trigger message identified by the External Identifier or MSISDN, SCS Identifier, and old trigger reference number in the received Submit Trigger Replace message, is pending at SMS-SC. + - If the trigger message is pending at SMS-SC, steps 3a - 6a are performed. + - The SMS-SC deletes the stored trigger message and stores the new trigger message to deliver it when the UE is available. + - The SMS-SC generates the necessary CDR information and includes the SCS Identifier. The SMS Application port ID which is included in the SM User Data Header and the Trigger Indication are included in the CDRs in order to enable differentiated charging. + - The SMS-SC sends a Submit Trigger Replace Response message to the MTC-IWF to inform that the previously submitted trigger message has been successfully replaced by the new one in the SMS-SC. + - The SMS-SC sends a Trigger Delivery Report for the original trigger message indicating that this message has been replaced. + - If the trigger message is not pending at SMS-SC, steps 3b - 4b are performed. In this case, the SMS-SC treats the new trigger message as a trigger message that it has to deliver to the UE. + +NOTE: Step 5a and step 6a are combined in single message in Stage 3. + +- 3b. The SMS-SC generates the necessary CDR information and includes the SCS Identifier. The SMS Application port ID which is included in the SM User Data Header and the Trigger Indication are included in the CDRs in order to enable differentiated charging. +- 4b. The SMS-SC sends a Submit Trigger Replace Response message to the MTC-IWF to inform that the replace request failed and the SMS-SC shall deliver the new trigger message. + +#### 5.2.3.3 Recall procedure for trigger delivery using T4 + +![Sequence diagram illustrating the recall procedure for trigger delivery using T4. The diagram shows interactions between UE, MSC/MME SGSN IP-SM-GW, SMS-SC/GMSC/IWMSC, HSS/HLR, and MTC-IWF. The process starts with the MTC-IWF sending a 'Submit Trigger Recall' to the SMS-SC. The SMS-SC checks if the trigger message is pending. If pending (A), it deletes the message, generates CDRs, and sends a 'Submit Trigger Recall Response (Success)' and a 'Trigger Delivery Report for original message (Recalled)' to the MTC-IWF. If not pending (B), it generates CDRs and sends a 'Submit Trigger Recall Response (Fail)' to the MTC-IWF.](1ce027dfd26183da52137cf990213724_img.jpg) + +``` + +sequenceDiagram + participant MTC-IWF + participant SMS-SC as SMS-SC/GMSC/IWMSC + participant HSS/HLR + participant MSC/MME as MSC/MME SGSN IP-SM-GW + participant UE + + Note right of SMS-SC: 2. Check if the trigger message is pending at SMS-SC + + Note right of MSC/MME: 3a. Delete the stored trigger message + Note right of MSC/MME: 4a. CDR generation + + Note right of MSC/MME: 3b. CDR generation + + Note right of MSC/MME: 4b. Submit Trigger Recall Response (Fail) + + Note right of MSC/MME: 5a. Submit Trigger Recall Response (Success) + Note right of MSC/MME: 6a. Trigger Delivery Report for original message (Recalled) + + MTC-IWF->>SMS-SC: 1. Submit Trigger Recall + SMS-SC->>HSS/HLR: + HSS/HLR-->>SMS-SC: + Note right of SMS-SC: 2. Check if the trigger message is pending at SMS-SC + + alt A: Pending + Note right of MSC/MME: 3a. Delete the stored trigger message + Note right of MSC/MME: 4a. CDR generation + Note right of MSC/MME: 5a. Submit Trigger Recall Response (Success) + Note right of MSC/MME: 6a. Trigger Delivery Report for original message (Recalled) + SMS-SC->>MTC-IWF: 5a. Submit Trigger Recall Response (Success) + SMS-SC->>MTC-IWF: 6a. Trigger Delivery Report for original message (Recalled) + else B: Not Pending + Note right of MSC/MME: 3b. CDR generation + Note right of MSC/MME: 4b. Submit Trigger Recall Response (Fail) + SMS-SC->>MTC-IWF: 4b. Submit Trigger Recall Response (Fail) + end + +``` + +Sequence diagram illustrating the recall procedure for trigger delivery using T4. The diagram shows interactions between UE, MSC/MME SGSN IP-SM-GW, SMS-SC/GMSC/IWMSC, HSS/HLR, and MTC-IWF. The process starts with the MTC-IWF sending a 'Submit Trigger Recall' to the SMS-SC. The SMS-SC checks if the trigger message is pending. If pending (A), it deletes the message, generates CDRs, and sends a 'Submit Trigger Recall Response (Success)' and a 'Trigger Delivery Report for original message (Recalled)' to the MTC-IWF. If not pending (B), it generates CDRs and sends a 'Submit Trigger Recall Response (Fail)' to the MTC-IWF. + +Figure 5.2.3.3-1: Recall procedure for trigger delivery using T4 + +1. Based on the Action type in Device Action Request message, the MTC-IWF sends a Submit Trigger Recall (External Identifier or MSISDN, SCS Identifier, old trigger reference number) message to the SMS-SC. The MTC-IWF selects the SMS-SC to which the old trigger message was submitted, e.g. based on configured information. +2. The SMS-SC determines whether the trigger message identified by External Identifier or MSISDN, SCS Identifier, and old trigger reference number in the received Submit Trigger Recall message, is pending at SMS-SC. + - A) If the trigger message is pending at SMS-SC, steps 3a - 6a are performed. + - 3a. The SMS-SC deletes the stored trigger message. + - 4a. The SMS-SC generates the necessary CDR information and includes the SCS Identifier. The SMS Application port ID which is included in the SM User Data Header and the Trigger Indication are included in the CDRs in order to enable differentiated charging. + - 5a. The SMS-SC sends a Submit Trigger Recall Response message to the MTC-IWF to inform that the previously submitted trigger message has been successfully deleted in the SMS-SC. + +- 6a. The SMS-SC sends a Trigger Delivery Report for the original trigger message indicating that this message has been recalled. + +NOTE: Whether step 5a and step 6a are combined in single message in Stage 3. + +B) If the trigger message is not pending at SMS-SC, steps 3b - 4b are performed. + +- 3b. The SMS-SC generates the necessary CDR information and includes the SCS Identifier. The SMS Application port ID which is included in the SM User Data Header and the Trigger Indication are included in the CDRs in order to enable differentiated charging. +- 4b. The SMS-SC sends a Submit Trigger Recall Response message to the MTC-IWF with a cause value indicating that the recall request failed. + +## 5.3 Information Storage + +### 5.3.0 General + +This clause describes the context information that is stored in the different nodes for MTC device trigger procedure and NIDD procedures. + +### 5.3.1 Trigger Information in SMS-SC (Triggering with T4) + +This table includes information that needs to be stored in SMS-SC for triggering with T4. + +**Table 5.3.1-1: SMS-SC trigger information** + +| Field | Description | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------| +| External Identifier/MSISDN | It is used to identify the corresponding External Identifiers in the delivery report. This can be also the MSISDN if used. | +| IMSI | It is used to indicate the UE used for MTC that is required to be triggered. | +| Trigger reference number | This is to co-relate the trigger request with trigger response. | +| SCS ID | It is used to allow the SMS SC to send the trigger response back to the appropriate SCS. | +| Trigger payload | The SMSC will store the Trigger payload until it receives the delivery confirmation. | +| Routing Information for SMS | The identities of the serving node(s). | +| Priority | It is used to indicate the priority of trigger request. | +| Validity period | To indicate the time period for which the trigger request is valid. | +| SMS Application Port ID | It is used to route the short message to the triggering function in the UE. | + +NOTE 1: The Trigger Payload is stored as user data in SMS-SC. + +NOTE 2: Priority, Validity period and SMS Application Port ID are included in the Trigger payload. + +### 5.3.2 SCEF + +The SCEF maintains the following EPS bearer context information for UEs. Table 5.3.2-1 shows the context fields for one UE. + +**Table 5.3.2-1: SCEF EPS bearer context** + +| Field | Description | T6a | T6b | +|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|---------------| +| User Identity
(Multiple instances of this field may exist) | One of {IMSI, MSISDN, External Identifier}. | X | X | +| APN | An APN that uniquely identifies an SCEF connection. | X | X | +| APN Rate Control | The APN Rate Control limits the maximum number of uplink/downlink packets and the maximum number of additional exception report packets per a specific time unit (e.g. minute, hour, day, week) for this APN. It includes an indication as to whether or not Exception reports may still be sent when the limit has been met (see clause 4.7.7 of TS 23.401 [7]). | X | X | +| NIDD Charging ID | Charging identifier included in charging records generated by the MME/SGSN, the SCEF and IWK-SCEF. | X | X | +| EPS Bearer ID | An EPS bearer identity that uniquely identifies an EPS bearer for the UE and a context in the SCEF. | X | X
(NOTE 1) | +| Serving Node Information | MME/SGSN address being used for the SCEF connection. | X | X | +| Serving PLMN ID | MCC + MNC of the serving PLMN | X | X | +| IMEISV | IMEISV for inclusion in CDR | X | X | +| Serving PLMN Rate Control | The Serving PLMN Rate Control limits the maximum number of uplink/downlink NAS Data PDUs in deci hour.
For SCEF use with APN Rate Control and for inclusion on SCEF CDR to allow post processing of CDRs and permit detection of abusive UEs (see clause 4.7.7 of TS 23.401 [7]). | X | X | + +NOTE 1: The SGSN uses the NSAPI of the PDP Context used for SCEF communication as an EPS Bearer ID when T6b is used. + +## 5.4 Security Procedures + +### 5.4.0 General + +The security procedures are specified in TS 33.187 [25]. + +### 5.4.1 Void + +### 5.4.2 Void + +## 5.5 Group message delivery procedures + +### 5.5.1 Group message delivery using MBMS + +![Sequence diagram for Group message delivery using MBMS. Lifelines: UE, RAN, MBMS-GW/GGSN MME/SGSN, BM-SC, HSS/HLR, SCEF, SCS/AS. The diagram shows the interaction between these entities for group message delivery, including TMGI allocation, bearer activation, and message delivery steps.](aeb2a26a07219661191294dba528067a_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS/HLR + participant BM-SC + participant MBMS-GW/GGSN MME/SGSN + participant RAN + participant UE + + Note right of MBMS-GW/GGSN MME/SGSN: Steps 1-4 only apply if MB2 is used + + SCS/AS->>SCEF: 1. Allocate TMGI Req + Note right of HSS/HLR: 2. Authorization + BM-SC->>SCEF: 3. TMGI Allocation + SCEF->>SCS/AS: 4. Allocate TMGI Resp + Note left of UE: 5. Application level interactions + SCEF->>SCS/AS: 6. Group Message Req + Note right of HSS/HLR: 7. Authorization + BM-SC->>SCEF: 8. Activate MBMS Bearer Request (for MB2) or + Note right of MBMS-GW/GGSN MME/SGSN: 8a. Create Session (for xMB) + SCEF->>BM-SC: 8b. OK (for xMB) + Note right of MBMS-GW/GGSN MME/SGSN: 8b-1. Get Session Properties (for xMB) + SCEF->>BM-SC: 8c. Update Session (for xMB) + RAN->>MBMS-GW/GGSN MME/SGSN: 9. MBMS Session Start Request/Response + BM-SC->>SCEF: 10. Activate MBMS Bearer Response (for MB2) or + Note right of MBMS-GW/GGSN MME/SGSN: OK (for xMB) + SCEF->>SCS/AS: 11. Group Message Response + Note left of UE: 12. Application level interactions + Note left of RAN: 13a. Group message delivery + SCEF->>SCS/AS: 13b. Group Message Delivery + Note right of MBMS-GW/GGSN MME/SGSN: 14. Action in response to group message + +``` + +Sequence diagram for Group message delivery using MBMS. Lifelines: UE, RAN, MBMS-GW/GGSN MME/SGSN, BM-SC, HSS/HLR, SCEF, SCS/AS. The diagram shows the interaction between these entities for group message delivery, including TMGI allocation, bearer activation, and message delivery steps. + +Figure 5.5.1-1: Group message delivery using MBMS + +NOTE 1: Unless the SCS/AS wants to extend the expiration time for an allocated TMGI, steps 1-5 can be skipped if a valid TMGI allocation already exists or if the MBMS bearer activation is performed without TMGI pre-allocation. + +If MB2 is used: + +1. If there is no assigned TMGI for an External Group Id, the SCS/AS sends the Allocate TMGI Request (External Group ID, SCS Identifier, (optional) location information, Accuracy) message to the SCEF. The SCS/AS may determine the IP address(es)/port(s) of the SCEF by performing a DNS query using the External Group Identifier or using a locally configured SCEF identifier/address. The location information restricts the distribution of the group message. It takes the format indicated in Accuracy parameter which can be either a list of cell IDs, or a list of MBMS Service Areas, or civic addresses, or a geographic area, or a combination of any of the above. Using the location information, the SCEF checks whether the SCS/AS is authorized to request TMGI allocation. + +If the expiration time for a previously allocated TMGI is to be extended, in addition to External Group ID, SCS Identifier and location/area information, the previously allocated TMGI is included in the Allocate TMGI Request message. + +NOTE 2: A single SCEF can be connected to multiple BM-SCs in a given PLMN. The location information is used to identify BM-SC(s) to which MB2-C/U messages are to be sent to. + +2. The SCEF determines whether the SCS/AS is authorized to request TMGI allocation. +3. The SCEF initiates TMGI allocation by the BM-SC (see TMGI Allocation Procedure specified in TS 23.468 [30]). In this procedure, if the TMGI is not included in step 1, the SCEF requests allocation of only one TMGI. If a TMGI is included in step 1, the SCEF requests to extend the TMGI expiration time for that TMGI. The SCEF stores TMGI and TMGI expiration received in this step. +4. The SCEF sends Allocate TMGI Response (Cause, TMGI, TMGI expiration) message to the SCS/AS. Cause value indicates success or failure of the requested procedure. In the case of failure, the reason for the failure condition is also included. The TMGI allocated by the BM-SC to which the SCS/AS is expected to send the group message, and TMGI expiration indicating the expiration time for the TMGI are also included. + +NOTE 3: The SCEF may cache the serving BM-SC Identity information and mapping between External Group ID and TMGI. + +Steps 5 to 14 are skipped if the SCS/AS only wants to extend the expiration time of the TMGI (MB2 only). + +5. Application level interactions may be applied for the UEs of specific group to retrieve the related MBMS service information, e.g. TMGI, start time, etc. in the case of MB2. Application level interactions between the UE and the SCS/AS are out of scope of this specification. + +If xMB is used, steps 1 to 5 are skipped. + +6. The SCS/AS sends the Group Message Request (External Group Identifier, SCS Identifier, TMGI (MB2 only), Message Delivery Stop Time (xMB only), optional (Group Message Payload, location information, Accuracy, Message Delivery Start Time) message to the SCEF. + +In the case of xMB, the SCEF creates a service using xMB for the group message and associates the external Group Identifier with the HTTP REST resource identifier of the service provided by the BM-SC upon service creation. The then SCEF forwards either only the ServiceID (see Table 5.4-1 in TS 26.348 [46]) to the SCS/AS or all service announcement. After the service is created, the SCS/AS triggers session creation towards the SCEF. + +The SCEF assigns a TLTRI that identifies this group message delivery request. The location information is included to identify the location over which group message is to be sent. It takes the format indicated in Accuracy parameter which can be either a list of cell IDs, or a list of MBMS Service Areas, or civic addresses, or a geographic area, or a combination of any of the above. + +The Message Delivery Start Time indicates the time at which the group message is to be sent by the network on the MBMS bearer(s). If not included, the group message is expected to be sent immediately. The Message Delivery Stop Time indicates the time at which the group message delivery is expected to be completed. When included, Group Message Payload indicates the payload the SCS/AS intends to deliver to UEs. Absence of Group Message Payload is indicative of the SCS/AS using delivery of group message in step 13a. + +NOTE 4: A single Group Message Payload can be sent to all included TMGIs (MB2 only). + +NOTE 5: Whether actual payload or a reference to the payload (e.g. URI) is sent in this step is left to Stage 3. In the case of the latter, the SCEF downloads the payload prior to step 13. + +In the case of xMB, if the application in the UE receives a ServiceId through application level interaction, the application can activate reception using MBMS APIs (see TS 26.347 [42]). + +7. The SCEF checks that the SCS/AS is authorised to send a group message request. It also checks to see if Message Delivery Start Time doesn't start after the TMGI expiration (MB2 only). In the case of xMB, the SCEF ensures that the xMB session stop time is not before the Message Delivery Start Time. If either of the checks fail, then the SCEF executes step 11 with a cause value indicating the reason for the failure condition and the flow stops at this step. In this case, the SCS/AS may subsequently release the TMGI allocated at step 3 by requesting an explicit de-allocation, or may rely on the expiration timer. +8. If MB2 is used, the Activate MBMS Bearer Procedure (see clause 5.1.2.3.2 of TS 23.468 [30]) is executed with the following changes: + +- In step 1 of this procedure, the SCEF, acting as GCS AS, may include location information from step 6. If no location information is provided in step 6 of this procedure, then the SCEF, based on local configuration, uses either a list of MBMS Service Area Identities, or a list of cell IDs, or both as the MBMS broadcast area. +- In step 2 of this procedure, the BM-SC may map the civic address(es) (if provided) and/or geographic area(s) (if provided) of location information into MBMS Service Area Identities subject to operator policies. + +8a-8c. If xMB is used, the Create Session procedure (see clause 5.4.2 of TS 26.348 [46]), Get Session Properties (see clause 5.4.3 of TS 26.348 [46]) and the Update Session Procedure (see clause 5.4.4 of TS 26.348 [46]) is executed with the following changes and clarification: + +- SCEF acts as a Content Provider. +- After completion of the Get Session Properties procedure, the Session Type value is set to "Files" by the SCEF irrespective of the received value for this parameter. +- In step 1 of Update Session procedure, the SCEF may include location information from step 6, session start and session stop. If no location information is provided in step 6 of this procedure, then the SCEF, based on local configuration, uses either a list of MBMS Service Area Identities, or a list of cell IDs, or both as the MBMS broadcast area. The SCEF shall derive the session start based on the Message Delivery Start Time if provided in step 6 and the session stop based on the Message Delivery Stop Time if provided in step 6. Session Resource ID as defined in TS 26.348 [46] Create Session response sent by the BM-SC to SCEF uniquely identifies an MBMS session during which MBMS service data is sent. Given that an MBMS session can target a certain MBMS Service Area via a TMGI and an MBMS Service Area description, it can be mapped to a specific group (i.e., MBMS UEs belonging to that group and which have received MBMS service announcement information containing the TMGI of the MBMS bearer service associated with this MBMS session can activate reception for that session). +- In step 2 of Update Session procedure, the BM-SC may map the civic address(es) (if provided) and/or geographic area(s) (if provided) of location information into MBMS Service Area Identities subject to operator policies. + +In the case of xMB, depending on the service created, the BM-SC may send the service announcement information to the UE as specified in TS 26.348 [46]. The service announcement information is referenced by the ServiceId which was provided by the BM-SC to the SCEF and then forwarded to the SCS/AS for service identification. + +9. Void. + +10. Void. + +11. The SCEF sends a Group Message Response (TLTRI, TMGI (MB2 only), Acceptance Status, (optional) SCEF Message Delivery IP address/port) message to the SCS/AS to indicate whether the Request has been accepted for delivery to the group. The SCEF sends Acceptance Status of TMGI to indicate whether activation of MBMS bearer corresponding to the TMGI was accepted or rejected. If Group Message Payload was not included in step 6, then the SCEF also sends SCEF Message Delivery IP address and port number to the SCS/AS. + +NOTE 6: The SCEF can map BM-SC address and port number (received in step 8 for MB2 or xMB delivery) to a different IP address and port number to be used between the SCEF and the SCS/AS for delivery of group message payload. + +12. Application level interactions may be applied for the UEs of specific group to retrieve the related MBMS service information, e.g. TMGI, start time. Application level interactions between the UE and the SCS/AS are out of scope of this specification. When using xMB, the application may receive the appropriate information through MBMS APIs from the MBMS Client (see TS 26.347 [42]). + +13a. If Group Message Payload was included in step 6, then at Message Delivery Start Time, the SCEF delivers to BM-SC the Group Message Payload(s) to corresponding to the MB2-U or the xMB-U IP address and port number associated with respective TMGI. If Group Message Payload was not included in step 6, then at or after the requested Group Message Start Time, but before the TMGI Expiration time (if MB2 is used) or Message Delivery Stop Time (if xMB is used), the SCS/AS transfers the content to be delivered to the group to the SCEF using the SCEF Message Delivery IP address and port number received at step 11, and then the SCEF delivers the content to the BM-SC. The BM-SC transfers the corresponding content to UEs. The SCS/AS may repeat Step 13a unless the Message Delivery Stop Time is reached. To avoid that potential responses to the broadcast + +message by high numbers of UEs are sent at almost the same time, it is recommended that the SCS/AS provide the UEs with a response time window if it expects the UEs to respond to the delivered content. + +NOTE 7: Subsequent to this step, it is up to the SCS/AS if the MBMS bearers will be kept active and allocated and for how long. The mechanisms defined in TS 23.468 [30] or TS 26.348 [46] can be used by the SCEF to release the MBMS resources. + +13b. Upon execution of 13a, the SCEF sends a Group Message Delivery (TLTRI, TMGI, Delivery Trigger Status) message to the SCS/AS to indicate whether group message delivery was triggered successful. TLTRI refers to the transaction identified by TLTRI in step 6. For the TMGI, the SCEF sends Delivery Trigger Status to indicate whether delivery of Group Message Payload corresponding to the TMGI was successful or not. + +14. When a UE receives the Group Message Payload it may initiate immediate or later communication with the SCS/AS. + +NOTE 8: It is recommended that the UE application ensures distribution of any responses within the response time window. + +### 5.5.2 Modification of previously submitted Group message + +![Sequence diagram for Modification of previously submitted Group Message. Lifelines: UE, RAN, MBMS-GW/GGSN MME/SGSN, BM-SC, HSS/HLR, SCEF, SCS/AS. The sequence starts with '0. Group Message Delivery submission successful' from BM-SC to SCEF. A dashed line labeled '1. Application level interactions' connects UE and SCS/AS. Step 2 is 'Modify Group Message Req' from SCS/AS to SCEF. Step 3 is 'Validation' within SCEF. Step 4 is 'TS 23.468 or TS 26.346 procedures for MBMS bearers' from SCEF to BM-SC. Step 5 is 'Modify Group Message Response' from SCEF to SCS/AS. Step 6 is 'Steps 12-14 from clause 5.5.1' from BM-SC to SCEF.](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MBMS-GW/GGSN MME/SGSN + participant BM-SC + participant HSS/HLR + participant SCEF + participant SCS/AS + + Note right of BM-SC: 0. Group Message Delivery submission successful + Note left of UE: 1. Application level interactions + Note right of SCS/AS: 2. Modify Group Message Req + Note right of SCEF: 3. Validation + Note right of SCEF: 4. TS 23.468 or TS 26.346 procedures for MBMS bearers + Note right of SCEF: 5. Modify Group Message Response + Note right of BM-SC: 6. Steps 12-14 from clause 5.5.1 + +``` + +Sequence diagram for Modification of previously submitted Group Message. Lifelines: UE, RAN, MBMS-GW/GGSN MME/SGSN, BM-SC, HSS/HLR, SCEF, SCS/AS. The sequence starts with '0. Group Message Delivery submission successful' from BM-SC to SCEF. A dashed line labeled '1. Application level interactions' connects UE and SCS/AS. Step 2 is 'Modify Group Message Req' from SCS/AS to SCEF. Step 3 is 'Validation' within SCEF. Step 4 is 'TS 23.468 or TS 26.346 procedures for MBMS bearers' from SCEF to BM-SC. Step 5 is 'Modify Group Message Response' from SCEF to SCS/AS. Step 6 is 'Steps 12-14 from clause 5.5.1' from BM-SC to SCEF. + +Figure 5.5.2-1: Modification of previously submitted Group Message + +0. The pre-condition for this flow is the successful completion of step 11 from clause 5.5.1. + +1. Application level interactions may be applied for the UEs of specific group to retrieve the related MBMS service information, e.g. TMGI, start time, etc. in the case of MB2 or ServiceId in the case of xMB. When the application receives a ServiceId through application level interaction, the application can activate reception using MBMS APIs (see TS 26.347 [42]). Application level interactions between the UE and the SCS/AS are out of scope of this specification. + +2. The SCS/AS determines that modification of previously accepted Group Message Delivery Request is required. The SCS/AS sends the Modify Group Message Request (TLTRI, Requested Action, Message Delivery Start Time, Message Delivery Stop Time (xMB only), optional (External Group Identifier, SCS Identifier, TMGI (MB2 only), Group Message Payload, location information, Accuracy) message to the SCEF. In the case of xMB, the SCEF identifies the associated MBMS Service using the external Group Identifier. Requested Action is either set to "Modify", or "Cancel". "Modify" indicates the request is to modify the transaction identified by TLTRI. "Cancel" indicates the request is to cancel the transaction identified by TLTRI. When set to "Modify", then the remainder parameters, except Message Delivery Start Time, are optional, and included only if different to that of step 6 from clause 5.5.1. When set to "Cancel", no other parameters are included. + +3. The SCEF uses TLTRI to locate the context of previously accepted Group Message Delivery Request executed in clause 5.5.1. If no associated transaction is found, or if a transaction if found but step 13a from clause 5.5.1 + +was completed, then step 4 is executed with appropriate Cause value, and the flow stops at this step. Otherwise, the flow proceeds. + +4. If Requested Action was set to "Cancel", then if MB2 is used the mechanisms defined in clause 5.1.2.3.3 of TS 23.468 [30] and if xMB is used the mechanisms defined in clause 5.4.5 of TS 26.348 [46] are executed by the SCEF to release the associated MBMS resources. If Requested Action was set to "Modify", then if MB2 is used the mechanisms defined in clause 5.1.2.4 of TS 23.468 [30] are used by the SCEF to modify the associated MBMS resources, whereas if xMB is used the mechanisms defined in clause 5.4.4 of TS 26.348 [46] with the following changes: + - In step 1 of this procedure, the SCEF, acting as GCS AS (if MB2 is used) or Content provider (if xMB is used), may include location information from step 2. If no location information is provided in step 2 of this procedure, then the SCEF, based on local configuration, uses either a list of MBMS Service Area Identities, or a list of cell IDs, or both as the MBMS broadcast area. + - In step 2 of this procedure, the BM-SC may map the civic address(es) (if provided) and/or geographic area(s) (if provided) of location information into MBMS Service Area Identities subject to operator policies. +5. If Requested Action was set to "Cancel", then the SCEF sends a Modify Group Message Response (Cause) message to the SCS/AS with appropriate Cause value depending on whether the cancellation was accepted, and the flow stops at this step. If Requested Action was set to "Modify", then the SCEF sends a Modify Group Message Response (Cause, TMGI, Acceptance Status) message to the SCS/AS to indicate whether the requested modifications were accepted. The usage of parameters is similar to step 11 of clause 5.5.1. +6. Steps 12-14 of clause 5.5.1 are executed. + +### 5.5.3 Group Message Delivery via unicast MT NIDD + +![Sequence diagram for Group Message Delivery via unicast MT NIDD. The diagram shows interactions between UE, MME/SGSN, ROAMING (IWK-SCEF), SCEF, and SCS/AS. The sequence is: 1. SCS/AS sends Group MT NIDD Submit Request to SCEF; 2. SCEF sends Group MT NIDD Submit Response to SCS/AS; 3. Mobile Terminated NIDD Procedure (Steps 2-9, except steps 2b and 5) involving UE, MME/SGSN, and ROAMING; 4. SCEF sends Group MT NIDD Submit Indication to SCS/AS.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant ROAMING as ROAMING (IWK-SCEF) + participant MME/SGSN + participant UE + Note right of SCS/AS: 1. Group MT NIDD Submit Request + SCS/AS->>SCEF: Group MT NIDD Submit Request + Note right of SCEF: 2. Group MT NIDD Submit Response + SCEF->>SCS/AS: Group MT NIDD Submit Response + Note left of ROAMING: 3. Mobile Terminated NIDD Procedure (Steps 2-9, except steps 2b and 5) + ROAMING->>MME/SGSN: + MME/SGSN->>UE: + Note right of SCEF: 4. Group MT NIDD Submit Indication + SCEF->>SCS/AS: Group MT NIDD Submit Indication + +``` + +Sequence diagram for Group Message Delivery via unicast MT NIDD. The diagram shows interactions between UE, MME/SGSN, ROAMING (IWK-SCEF), SCEF, and SCS/AS. The sequence is: 1. SCS/AS sends Group MT NIDD Submit Request to SCEF; 2. SCEF sends Group MT NIDD Submit Response to SCS/AS; 3. Mobile Terminated NIDD Procedure (Steps 2-9, except steps 2b and 5) involving UE, MME/SGSN, and ROAMING; 4. SCEF sends Group MT NIDD Submit Indication to SCS/AS. + +Figure 5.5.3-1: Group Message Delivery via unicast MT NIDD + +1. If SCS/AS has downlink non-IP data to send to a group of UEs, the SCS/AS sends a Group MT NIDD Submit Request (SCS/AS Identifier, External Group Identifier, TLTRI, non-IP data, Reliable Data Service Configuration, Maximum Latency, PDN Connection Establishment Option) message to the SCEF. The SCS/AS may determine the IP address(es)/port(s) of the SCEF by performing a DNS query using the External Group Identifier or using a locally configured SCEF identifier/address. When non-IP data is sent to an External Group Identifier, the Reliable Data Service Configuration shall indicate that no reliable data service acknowledgment is requested. + +The Maximum Latency Parameter provided by the SCS/AS in this procedure is only used by the SCEF to determine the maximum acceptable delay for associated non-IP data and is not propagated further by the SCEF. + +2. Based on the preceding NIDD Configuration of the UE Group (see clause 5.13.2) and the SCEF stored list of authorized External Identifiers associated to the External Group Identifier, the SCEF sends a single Group MT NIDD Submit Response (Cause) message to the SCS/AS to acknowledge acceptance of the Group MT NIDD Submit Request. The Cause may indicate that the non-IP packet size is larger than the Maximum Packet Size determined in the preceding NIDD configuration of the UE Group. + +3. The SCEF performs this step for each External Identifier that belongs to the External Group Identifier. The SCEF stored the list of authorized External Identifiers associated to the External Group Identifier during the preceding NIDD Configuration of the UE Group (see clause 5.13.2). The SCEF determines the EPS Bearer Context based on the NIDD Configuration TLTRI that is associated with the SCS/AS Identifier and the External Identifier. If an SCEF EPS bearer context corresponding to the External Identifier and SCS/AS Identifier is found, then the SCEF checks whether the SCS/AS is authorised to send NIDD requests and that the SCS/AS has not exceeded its rate control quota or rate of data submission to the SCEF EPS bearer. If this check fails, the SCEF does nothing in this step for this UE and the Cause value that is associated with this UE and provided to the SCS/AS in step 4 will indicate the reason for the failure condition for each failed UE. For each UE that passes these checks, the SCEF continues with the flow by executing steps 2-9 (except steps 2b and 5) of the Mobile Terminated NIDD Procedure of clause 5.13.3. +4. After executing step 3 for all UEs, the SCEF sends an aggregated response message Group MT NIDD Submit Indication (TLTRI associated with the Request of step 1, Hop-by-Hop Acknowledgment Indication(s), Re-Transmission time(s), Trigger Indication(s), Cause(s)). The Re-Transmission time(s) report, for UEs that have power saving function and did not receive the MT NIDD message, how long time it will take before they are reachable. Re-Transmission time(s) are not sent for UEs where transmission was successful. The SCEF does not buffer the non-IP data further (if applicable) and provides a Hop-by-Hop Acknowledgment Indication, and a Cause value for each UE in the response to the SCS/AS. See clause 5.13.3 for a description of the Hop-by-Hop Acknowledgment Indication and when it is included. The Trigger Indication(s) is used to indicate UE(s) for which a trigger was sent in order to establish a PDN connection. + +NOTE: The Re-Transmission time is used to inform the SCS/AS when the UE is expected to become reachable again, it is the expected wake up time that MME provided to SCEF when delivery failed for UEs with long sleep time. + +## 5.6 Monitoring Procedures + +### 5.6.0 Common Parameters + +This clause describes the common parameters required for Monitoring Event procedures. + +SCEF Reference ID is a parameter created by the SCEF to associate a Monitoring Event report or a deletion of a Monitoring Event to a specific Monitoring Request and the associated context information within the SCEF. SCEF Reference ID is stored by HSS, MME, SGSN, and IWK-SCEF. + +NOTE 1: For the case of an individual UE, an SCEF may aggregate Monitoring Event configuration requests for the same External identifier/MSISDN from different SCS/AS instances. + +NOTE 2: For the case of groups, an SCEF may aggregate Monitoring Event configuration requests for the same External Group Identifier from different SCS/AS instances. + +SCEF ID indicates the SCEF to which the Monitoring Indication message has to be sent to by the HSS, MME, SGSN, or IWK-SCEF. SCEF ID is stored by the HSS, MME, SGSN, and IWK-SCEF. + +SCEF Reference ID for Deletion identifies the monitoring event configuration that shall be deleted before applying the requested monitoring event configuration. + +Monitoring Type identifies the specific Monitoring Event being requested. + +If the Monitoring Event Configuration requested from the SCEF is for a group of UEs, the HSS includes User Identity in the monitoring event configuration. + +Maximum Number of Reports is an optional parameter that indicates the maximum number of event reports to be generated by the HSS, MME, or SGSN until the associated monitoring event is considered to expire. This parameter can be used when configuring a monitoring event for an individual UE or a group. When the parameter is configured for a group, the configured value is applied to each individual UE's monitoring event configuration. A value of one implies a single event report is to be generated which makes it equivalent to a One-time Monitoring Request. + +Monitoring Duration is an optional parameter that indicates the absolute time at which the related monitoring event request is considered to expire. For Monitoring Requests for a group, this parameter applies to every group member UE. + +Inclusion of either Maximum Number of Reports (with a value higher than one) or Monitoring Duration makes the Monitoring Request a Continuous Monitoring Request. For a Continuous Monitoring Request, a single Monitoring Request may generate more than one Monitoring Indication message. Support of continuous monitoring is optional. + +Absence of both Maximum Number of Reports and Monitoring Duration makes the Monitoring Request a One-time Monitoring Request. For One-time Monitoring Requests, a single Monitoring Request generates only one Monitoring Report for an individual UE and for an individual group member UE. + +If for a given Monitoring Event both Maximum Number of Reports and Monitoring Duration are included then the monitoring request is considered to expire as soon as one of the conditions is met. + +Chargeable Party Identifier is an optional parameter included by the SCEF. It identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements. + +MTC Provider Information is an optional parameter included by the SCEF. It identifies the MTC Service Provider and/or MTC Application. Optionally the MTC Provider Information may also be provided by the SCS/AS. + +Group Reporting Guard Time is an optional parameter for group-based monitoring configuration to indicate the time for which the Monitoring Event Reporting(s) detected by the UEs in a group can be aggregated before sending them to the SCEF/SCS/AS. The value of the Group Reporting Guard time should be set less than the Monitoring Duration. For the continuous monitoring reporting, unless the Monitoring Duration has been reached, the Group Reporting Guard timer is restarted when it expires. If the time left until Monitoring Duration is less than the Group Reporting Guard Time, then the Group Reporting Guard timer shall be set to expire when the Monitoring Duration expires. If the Monitoring Duration is expired, the Group Reporting Guard Time, if running, shall be considered to expire and aggregated Monitoring Event Reporting(s) is sent to destination immediately. + +Number of UEs is a parameter that is provided to the SCEF during group-based monitoring configuration to indicate the number of UEs within the group identified by the External Group Identifier. The SCEF uses this value to determine whether the monitoring event has been reported for all group member UEs. + +### 5.6.1 Monitoring Event configuration and deletion via HSS + +#### 5.6.1.1 Configuration Procedure + +Figure 5.6.1.1-1 illustrates the procedure of configuring monitoring at the HSS or the MME/SGSN. The procedure is common for various Monitoring Event types. Common parameters for this procedure are detailed in clause 5.6.0. The steps and parameters specific to different Monitoring Event types are detailed in clauses 5.6.1.3 to 5.6.1.9. + +The procedure is also used for deleting a previously configured Monitoring Event either as a standalone procedure or together with configuring a new Monitoring Event between the same SCEF and the same SCS/AS, or replacing a previously configured Monitoring Event with a new Monitoring Event of the same type between the same SCEF and the same SCS/AS, or for one-time reporting if the Configured Monitoring Event is available at the configured node or cancelling the event monitoring for certain UEs (i.e. one individual UE or a sub-set of UEs) in a group of UEs for which there is a configured Monitoring Event or adding the event monitoring for certain new UEs (i.e. one individual UE or a sub-set of UEs) in a group of UEs for which there is a configured Monitoring Event. + +![Sequence diagram illustrating the monitoring event configuration and deletion via HSS procedure. The diagram shows interactions between MME/SGSN, HSS, SCEF, and SCS/AS. The process starts with a Monitoring Request from SCS/AS to SCEF, followed by SCEF handling, then a Monitoring Request from SCEF to HSS. HSS handles the request and sends a Monitoring Response to SCEF, which then forwards it to SCS/AS. Next, SCEF sends an Insert Subscriber Data Request to MME/SGSN, which handles it and sends an Insert Subscriber Data Answer to SCEF. Finally, SCEF sends a Monitoring Response or Indication to HSS, which then forwards it to SCS/AS via 9a, 9b, and 9c messages.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + participant MME/SGSN + + Note right of SCEF: 2. SCEF handling + Note right of HSS: 4. HSS handling + Note right of MME/SGSN: 6. MME/SGSN handling + + SCS/AS->>SCEF: 1. Monitoring Request + SCEF->>HSS: 3. Monitoring Request + HSS-->>SCEF: 4a. Monitoring Response + SCEF-->>SCS/AS: 4b. Monitoring Response + SCEF-->>MME/SGSN: 5. Insert Subscriber Data Request + MME/SGSN-->>SCEF: 7. Insert Subscriber Data Answer + HSS->>SCEF: 8. Monitoring Response or Indication + SCEF-->>SCS/AS: 9a. Monitoring Response + SCEF-->>SCS/AS: 9b. Monitoring Indication + SCS/AS-->>SCEF: 9c. Monitoring Indication Response + +``` + +Sequence diagram illustrating the monitoring event configuration and deletion via HSS procedure. The diagram shows interactions between MME/SGSN, HSS, SCEF, and SCS/AS. The process starts with a Monitoring Request from SCS/AS to SCEF, followed by SCEF handling, then a Monitoring Request from SCEF to HSS. HSS handles the request and sends a Monitoring Response to SCEF, which then forwards it to SCS/AS. Next, SCEF sends an Insert Subscriber Data Request to MME/SGSN, which handles it and sends an Insert Subscriber Data Answer to SCEF. Finally, SCEF sends a Monitoring Response or Indication to HSS, which then forwards it to SCS/AS via 9a, 9b, and 9c messages. + +**Figure 5.6.1.1-1: Monitoring event configuration and deletion via HSS procedure** + +- The SCS/AS sends a Monitoring Request (External Identifier or MSISDN or External Group ID, SCS/AS Identifier, Monitoring Type, Maximum Number of Reports, Monitoring Duration, T8 Destination Address, TLTRI for Deletion, TLTRI for Update, the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added for an existing group event, operation indication (cancellation or addition), Group Reporting Guard Time, MTC Provider Information) message to the SCEF. The SCEF assigns a TLTRI that identifies the Monitoring Request, if a new monitoring event is being configured. The SCS/AS may perform deletion of a previously configured Monitoring Event together with configuring a new Monitoring Event. If the SCS/AS wants to perform deletion of a previously configured Monitoring Event, then it shall include TLTRI for Deletion. + +If the SCS/AS wants to configure Monitoring Event for the group of UEs, the SCS/AS can send Monitoring Request message including External Group Identifier and Group Reporting Guard Time. If the SCS/AS includes External Group Identifier in the Monitoring Request message, External Identifier or MSISDN shall be ignored. A Group Reporting Guard Time is an optional parameter to indicate that aggregated Monitoring Event Reporting(s) which have been detected for the UEs in a group needs to be sent to the SCS/AS once the Group Reporting Guard Time is expired. + +If the SCS/AS decides to cancel or add the monitoring event for certain UEs (i.e. one individual UE or a sub-set of UEs) in a group of UEs for which there is a configured Monitoring Event, the SCS/AS can send Monitoring Request message including the TLTRI for Update corresponding to the existing monitoring event configuration and the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added with the operation indication which is either cancellation or addition. + +NOTE 1: A relative priority scheme for the treatment of multiple SCS/AS Monitoring Requests, e.g. for deciding which requests to serve under overload condition, can be applied. This priority scheme is used locally by the SCEF, i.e. it is not used nor translated in procedures towards other functions. + +- The SCEF stores SCS/AS Identifier, T8 Destination Address, Monitoring Duration, Maximum Number of Reports and Group Reporting Guard Time, if provided. If the SCEF assigned a TLTRI, the SCEF stores the TLTRI, and also assigns it to an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Monitoring Request is malformed or the SCS/AS has exceeded its quota or rate of submitting monitoring requests, the SCEF performs step 9 and provides a Cause value appropriately indicating the error. If the SCEF received a TLTRI for Update, the SCEF looks up the SCEF context pointed to by the TLTRI for Update to derive the related SCEF Reference ID. If the + +SCEF received a TLTRI for Deletion, the SCEF looks up the SCEF context pointed to by the TLTRI for Deletion to derive the related SCEF Reference ID for Deletion. + +If the SCEF received a request to cancel the monitoring event for indicated UEs (i.e. one individual UE or a subset of UEs) in a group of UEs for which there is a configured Monitoring Event and if the Maximum Number of Reports applies to the monitoring event configuration, the SCEF sets the stored number of reports of the indicated UE(s) to Maximum Number of Reports. + +The SCEF uses the Group Reporting Guard Time for a Monitoring Event Reporting for the group of UEs when the Monitoring Indication message is sent from the MME/SGSN to the SCEF. The SCEF sets the Group Reporting Guard Time for HSS less than the value for the SCEF received from SCS/AS in order to ensure to receive accumulated Monitoring Indication from HSS before the Group Reporting Guard Timer for SCEF is expired. + +3. The SCEF sends a Monitoring Request (External Identifier or MSISDN or External Group Identifier, SCEF ID, SCEF Reference ID, Monitoring Type, Maximum Number of Reports, Monitoring Duration, SCEF Reference ID for Deletion, the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added, operation indication (cancellation or addition), Chargeable Party Identifier, Group Reporting Guard Time, MTC Provider Information) message to the HSS to configure the given Monitoring Event on the HSS and on the MME/SGSN, if required. If the External Group Identifier is included, External Identifier or MSISDN shall be ignored. For one-time Monitoring Request of Roaming Status, the SCEF does not indicate the Group Reporting Guard Time. + +NOTE 2: The MTC Provider Information in step 1 is an optional parameter. The SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information if not present in step 1 is left to implementation (e.g. based on the requesting SCS/AS). + +4. The HSS examines the Monitoring Request message, e.g. with regard to the existence of External Identifier or MSISDN or External Group Identifier, whether any included parameters are in the range acceptable for the operator, whether the monitoring event(s) is supported by the serving MME/SGSN, whether the group-basis monitoring event feature is supported by the serving MME/SGSN, or whether the monitoring event that shall be deleted or updated is valid. The HSS optionally authorizes the chargeable party identified by Chargeable Party Identifier. If this check fails the HSS follows step 8 and provides a Cause value indicating the reason for the failure condition to the SCEF. + +NOTE 3: The details of the chargeable party authorization are outside the scope of this specification. + +The HSS stores the SCEF Reference ID, the SCEF ID, Maximum Number of Reports, Monitoring Duration and the SCEF Reference ID for Deletion as provided by the SCEF. For a Monitoring Request for a group, such parameters are stored for every group member UE. For a Monitoring Request with the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added as in step 3, such parameters together with the operation indication as provided by the SCEF are stored for every indicated UE. + +The HSS uses the Group Reporting Guard Time for a Monitoring Event Reporting for the group of UEs when the Monitoring Indication message is sent from the HSS to the SCEF. + +- 4a. For group based processing, if the HSS receives the Monitoring Request with an External Group Identifier, the HSS sends a Monitoring Response (SCEF Reference ID, Number of UEs, Cause) message to the SCEF to acknowledge acceptance of the Monitoring Request immediately before beginning the processing of individual UEs indicating that Group processing is in progress. The HSS deletes the monitoring event configuration identified by the SCEF Reference ID, if it was requested. + +If the HSS receives the Monitoring Request with the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added as in step 3 and the event was monitored by the HSS, the HSS cancels or adds the event monitoring for the indicated UE(s). + +- 4b. The SCEF sends a Monitoring Response (TLTRI, Cause) message to the SCS/AS. The Cause value indicates progress of Group processing request. + +5. If required by the specific Monitoring Type and when Monitoring Event(s) is supported by the serving MME/SGSN, the HSS sends an Insert Subscriber Data Request (Monitoring Type, SCEF ID, SCEF Reference ID, Maximum Number of Reports, Monitoring Duration, SCEF Reference ID for Deletion, Chargeable Party Identifier) message to the MME/SGSN for each individual UE and for each individual group member UE. If the + +Monitoring Request message is for a group of UEs, for each UE group member, the HSS includes the selected External ID or the MSISDN in the monitoring event configuration and sends an Insert Subscriber Data Request message per UE to all the MME/SGSN(s) serving the members of the group. If the HSS has received in step 3 Monitoring Request with the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be added, for each indicated UE group member, the HSS includes the corresponding External ID or the MSISDN in the monitoring event configuration and sends an Insert Subscriber Data Request message to the MME/SGSN(s) serving such indicated UE group member. If the HSS has received in step 3 Monitoring Request with the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled and the event is monitored by MME/SGSN, the HSS includes the received value of the SCEF Reference ID within the SCEF Reference ID for Deletion towards to the MME/SGSN. Optionally, the HSS allocates a Provider-Group-ID based on the MTC Provider Information (different from the IMSI-Group-Id) and sends it to the MME/SGSN to assist the serving node(s) when selecting and differentiating configurations for a given MTC Service Provider (e.g. to delete the configurations for a specific MTC Service Provider at the MME/SGSN). + +NOTE 4: How the HSS selects an External ID when multiple External IDs are associated with the same IMSI is left to implementation, e.g. based on the MTC Provider Information (if received) or the default External ID (if not received) + +NOTE 5: The Provider-Group-ID is used for group operations e.g. as specified in clause 4.3.7.4.2 of TS 23.401 [7] NAS level congestion control. + +6. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF then clause 5.6.6 applies. Otherwise, the MME/SGSN verifies the request, e.g. if the Monitoring Type is covered by a roaming agreement when the request is from another PLMN or whether it serves the SCEF Reference ID for Deletion and can delete it. If this check fails, the MME/SGSN follows step 7 and provides a Cause value indicating the reason for the failure condition to the HSS. Based on operator policies, the MME/SGSN may also reject the request due to other reasons (e.g. overload or HSS has exceeded its quota or rate of submitting monitoring requests defined by an SLA). + +The MME/SGSN stores the received parameters and starts to watch for the indicated Monitoring Event unless it is a One-time request and the Monitoring Event is available to the MME/SGSN at the time of sending Insert Subscriber Data Answer. The MME/SGSN deletes the monitoring configuration identified by the SCEF Reference ID for Deletion, if provided. + +NOTE 6: The MME/SGSN will transfer the parameters stored for every monitoring task as part of its context information during an MME/SGSN change. + +7. If the monitoring configuration is successful, the MME/SGSN sends an Insert Subscriber Data Answer (Cause) message to the HSS. If the requested Monitoring Event is available to the MME/SGSN at the time of sending Insert Subscriber Data Answer, then the MME/SGSN includes the Monitoring Event Report in the Insert Subscriber Data Answer message. +8. For single UE processing, the HSS sends a Monitoring Response (SCEF Reference ID, Cause, Monitoring Event Report) message to the SCEF to acknowledge acceptance of the Monitoring Request and the deletion of the identified monitoring event configuration, if it was requested. The HSS deletes the monitoring event configuration identified by the SCEF Reference ID, if it was requested. If the requested Monitoring Event is available to the HSS at the time of sending Monitoring Response message or was received from the MME/SGSN in step 7, then the HSS includes a Monitoring Event Report in the Monitoring Response message. + +If it is a One-time request and the Insert Subscriber Data Answer includes a Monitoring Event Report, the HSS deletes the associated Monitoring Event configuration for the individual UE or for the individual group member UE. + +For group-based processing, if the HSS sent the Monitoring Response in step 4a, i.e. due to having received a Monitoring Request with an External Group Identifier and if the Group Reporting Guard Time was provided in the Monitoring Request, the HSS accumulates multiple responses for the UEs of the group within the Group Reporting Guard Time. After the Group Reporting Guard Time expiration, the HSS sends a Monitoring Indication with the accumulated responses. The HSS includes UE identity(ies) and a Cause value indicating the reason for the failure in the message if the monitoring configuration of the group member failed. + +NOTE 7: For the group-basis Monitoring Event configuration, the HSS may divide the accumulated Monitoring Indications into multiple messages due to e.g. limitation of the message size. + +In the case of UE mobility, the HSS determines whether the new MME/SGSN supports requested Monitoring Event(s). + +- 9a. For single UE processing, the SCEF sends a Monitoring Response (Cause, Monitoring Event Report) message to the SCS/AS to acknowledge acceptance of the Monitoring Request and the deletion of the identified monitoring event configuration, if it was requested. If the SCEF received a Monitoring Event Report then it includes the Monitoring Event Report in the Monitoring Response message. If it is a One-time request for an individual UE and the Monitoring Response includes a Monitoring Event Report for the UE, the SCEF deletes the associated Monitoring Event configuration. +- 9b. For group-based processing, if no Group Reporting Guard Time was set, then the SCEF sends the Monitor Indication (TLTRI, Cause, Monitoring Event Report) message to the SCS/AS as it receives them from the HSS. Otherwise, it accumulates Monitoring Event for the UEs of the group until the expiration of Group Reporting Guard Time. Upon expiration, the SCEF sends a Monitoring Indication (TLTRI, Cause, list of (External Identifier or MSISDN, Monitoring Event Report)) message to the SCS/AS. A list of accumulated Monitoring Event Report for each UE identified by either External Identifier or MSISDN is also included. + +If the Monitoring Request is a one-time request for a group of UEs or if Maximum Number of Reports is included for continuous monitoring of group of UEs, the SCEF uses the list of UE Identities that were received in step 8 and the Number of UEs parameter that was received in step 4a to check if the reports for all the individual group member UEs have been received. If the SCEF determines that all reports for all individual group member UEs have been received, the SCEF sends a request to the HSS to delete the associated Monitoring Event configuration for the group. + +- 9c. For each Monitoring Indication message received in step 9b, the SCS/AS sends a Monitoring Indication Response (Cause) message to the SCEF. Cause value reflects successful or unsuccessful acknowledgement of Monitoring Indication message. + +If the HSS detects that the current serving MME/SGSN cannot support a requested Monitoring Event or the group-basis monitoring event feature (e.g. after a UE mobility event), the HSS performs the procedures given below. + +- Notify the SCEF that the configured Monitoring Event for the UE is considered to be suspended. The SCEF interprets this to mean that the network will temporarily be unable to serve the configured Monitoring Event. In this case: + - When the MME/SGSN for the UE changes (e.g. due to UE mobility), and the new MME/SGSN supports the suspended Monitoring Event, the HSS shall configure the new MME/SGSN with the Monitoring Event and notify the SCEF of resumption of the suspended Monitoring Event; + - If the criteria for Continuous Reporting expire while the Monitoring Event is suspended, the HSS and the SCEF shall independently delete the Monitoring Event. + +#### 5.6.1.2 Void + +#### 5.6.1.3 Specific Parameters for Monitoring Event: Loss of connectivity + +Loss of connectivity indicates when the 3GPP network detects that the UE is no longer reachable for either signalling or user plane communication. Such condition is identified when the mobile reachability timer expires in the MME or SGSN (see TS 23.401 [7], TS 23.060 [6], when the UE detaches and when an active UE is purged (see TS 29.272 [31])). The SCS/AS may provide a Maximum Detection Time, which indicates the maximum period of time without any communication with the UE after which the SCS/AS is to be informed that the UE is considered to be unreachable. + +NOTE 1: As the Maximum Detection Time of loss of connectivity determines the order of magnitude of the Periodic Update timer, the network should ensure that this Maximum Detection Time and thereby the periodic TAU/RAU timers for the UE remain above lower bound values both for preserving the battery of the UE and for managing the signalling load of the network. So for UEs with battery constraints, it should not be a small time (e.g. on the order of only a few minutes). Even for UEs without battery constraints, trying to fulfil a Maximum Detection Time of loss of connectivity on the order of a few minutes can only apply to a limited number of UEs due to the cost of signalling induced by this feature. + +NOTE 2: The Maximum Detection Time of loss of connectivity is on the order of 1 minute to multiple hours. + +1. The SCS/AS sets Monitoring Type to "Loss of Connectivity", and optionally adds Maximum Detection Time prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. +2. The SCEF executes step 2 of clause 5.6.1.1. +3. The SCEF executes step 3 of clause 5.6.1.1. +4. The HSS executes step 4 of clause 5.6.1.1. In addition, it checks whether the Maximum Detection Time is within the range defined by operator policies, and, if acceptable then the HSS sets the subscribed periodic RAU/TAU timer using the value of Maximum Detection Time, if it is provided. If the Maximum Detection Time is not acceptable, the HSS rejects the request by executing step 8, and provides a Cause value indicating the reason for the failure condition to the SCEF. + +If the Enhanced Multiple Event Monitoring feature is not supported and if the subscribed periodic RAU/TAU Timer was previously set by a different Monitoring Request identified by a different SCEF Reference ID for the same UE then, depending on operator configuration, the HSS either performs step 8 to reject the Monitoring Request with an appropriate Cause or accepts the request. If the HSS accepts this request, then it cancels the previously accepted Monitoring Request by including the SCEF Reference ID of that Monitoring Request in step 8. + +For group based processing, if the previously accepted Monitoring Request is associated with a group of UEs and the HSS is not cancelling the previously accepted Monitoring Request for all UEs in the group, then the HSS provides the list of affected UEs (identified by External Identifier or MSISDN) as well as operation indication (cancellation or addition) to the SCEF in step 8. + +If the Enhanced Multiple Event Monitoring feature is supported, and if the subscribed periodic RAU/TAU Timer was previously set by a different Monitoring Request or Network Parameter Configuration identified by a different SCEF Reference ID for the same UE, as long as the Maximum Detection Time is within the range defined by operator policies, the HSS shall accept the request. If the newly received Maximum Detection Time is lower than the provided subscribed periodic RAU/TAU timer, the HSS shall set the subscribed periodic RAU/TAU timer using the newly received Maximum Detection Time as described in clause 4.5.6.2. The HSS may notify the SCEF (which then notifies the SCS/AS) of the actual value that is being applied in the 3GPP network. + +NOTE 3: Since the value of the mobile reachable timer is larger than the value of the periodic RAU/TAU timer (by four minutes as a default), the HSS may set the subscribed periodic RAU/TAU timer to a smaller value than the value of Maximum Detection Time. + +5. The HSS executes step 5 of clause 5.6.1.1. In addition: + - if the Enhanced Multiple Event Monitoring feature is not supported and the HSS accepts new monitoring event configuration and cancel the existing monitoring event configuration, the HSS includes the new monitoring event configuration information, the SCEF Reference ID for Deletion of the cancelled monitoring event configuration with an appropriate Cause, and the subscribed periodic RAU/TAU Timer (if modified). + +When HSS accepts new configured Monitoring Event for UEs in step 4 above, the HSS includes the new monitoring event configuration information and the subscribed periodic RAU/TAU Timer (if modified). + +When HSS removes a previously configured Monitoring Event for UEs in step 4 above, the HSS also deletes the previously configured Monitoring Event in the MME/SGSN, if applicable. + +- If the Enhanced Multiple Event Monitoring feature is supported, the HSS includes the new monitoring event configuration information and the subscribed periodic RAU/TAU Timer (if modified). + +When HSS modifies a previously configured Monitoring Event for UE(s) in step 4 above, the HSS also updates the previously configured Monitoring Event in the MME/SGSN, if applicable. + +6. The MME/SGSN executes step 6 of clause 5.6.1.1. If the MME/SGSN receives a subscribed periodic RAU/TAU timer value from the HSS, it allocates the subscribed value to the UE as the periodic TAU/RAU timer. The MME/SGSN starts watching for the expiration of the mobile reachable timer. +7. Step 7 of clause 5.6.1.1 is executed. + +8. Step 8 of clause 5.6.1.1 is executed. The HSS may include the SCEF Reference ID of previously accepted Monitoring Request which needs to be cancelled and the cancellation cause. If the HSS, in step 4 above, decides to cancel Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS also includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +If the HSS, in step 4 above, decides to add Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +9. Step 9 of clause 5.6.1.1 is executed. If SCEF Reference ID of previously configured Monitoring Event for cancellation is included in step 8, then the SCEF executes steps 2-5 of clause 5.6.9 using the associated TLTRI towards the associated SCS/AS. + +#### 5.6.1.4 Specific Parameters for Monitoring Event: UE reachability + +For UE that is not reachable at the time of monitoring event configuration, UE reachability indicates when the UE becomes reachable for sending either SMS or downlink data to the UE, which is detected when the UE transitions to ECM-CONNECTED mode (for a UE using Power Saving Mode or extended idle mode DRX) or when the UE will become reachable for paging (for a UE using extended idle mode DRX). If the UE is reachable at monitoring event configuration, the MME shall immediately send UE reachability event report. This monitoring event supports Reachability for SMS and Reachability for Data. Only a One-time Monitoring Request for Reachability for SMS is supported. The SCS/AS may include the following parameters in the Monitoring Event configuration request to the SCEF: + +- Reachability Type indicating whether the request is for "Reachability for SMS", or "Reachability for Data", or both. +- Optionally, Maximum Latency indicating maximum delay acceptable for downlink data transfers. Maximum Latency is used for setting the periodic TAU/RAU timer for the UE as it sets the maximum period after which a UE has to connect to the network again and thereby becomes reachable. Determined by the operator, low values for Maximum Latency may deactivate PSM. +- Optionally, Maximum Response Time indicating the time for which the UE stays reachable to allow the SCS/AS to reliably deliver the required downlink data. Maximum Response Time is used for setting the Active Time for the UE. When the UE uses extended idle mode DRX, the Maximum Response Time is used to determine how early this monitoring event should be reported to the SCS/AS before the next Paging Occasion occurs. +- Optionally, Suggested number of downlink packets indicating the number of packets that the Serving Gateway shall buffer if the UE is not reachable. + +NOTE 1: As the Maximum Latency determines the order of magnitude of the Periodic Update timer, the network should ensure that this Maximum Latency and thereby the periodic TAU/RAU timers for the UE remain above lower bound values both for preserving the battery of the UE and for managing the signalling load of the network. So for UEs with battery constraints, it should not be a small time (e.g. on the order of only a few minutes). Even for UEs without battery constraints, trying to fulfil a Maximum Latency on the order of a few minutes can only apply to a limited number of UEs due to the cost of signalling induced by this feature. + +NOTE 2: The Maximum Latency is on the order of 1 minute to multiple hours. + +NOTE 3: The Network Parameter Configuration via SCEF feature (see clause 4.5.21) feature supersedes the option of setting Reachability Type to "configuration" during configuration of the UE Reachability Monitoring Event which is no longer recommended. + +1. The SCS/AS sets Monitoring Type to "UE Reachability", and includes Reachability Type, and any combination of the following optional parameters: Maximum Latency, Maximum Response Time, Suggested number of downlink packets, and Idle Status Indication prior to sending the Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. +2. The SCEF executes step 2 of clause 5.6.1.1. In addition, it checks whether the Maximum Latency (if included), the Maximum Response Time (if included), and the Suggested number of downlink packets (if included) are within the range defined by operator policies. If not, or if the network does not support Idle Status Indication, + +then depending on operator policies, the SCEF rejects the request by performing step 9 of 5.6.1.1 with an appropriate cause value. + +3. When "Reachability for SMS" is requested, the SCEF subscribes with the HSS by executing step 3 of 5.6.1.1 to get notified when the HSS is notified that the UE is reachable. The HSS performs the UE Reachability Notification Request procedure for getting a UE Activity Notification as described in TS 23.401 [7] and/or uses the UE Reachability function as described in TS 23.060 [6]. The Mobile-Station-Not-Reachable-Flag (MNRF) handling is described in TS 23.040 [12]. + +When "Reachability for Data" is requested, the SCEF executes step 3 of 5.6.1.1. In addition, if provided, it includes Maximum Latency, Maximum Response Time, and Idle Status Indication. + +4. The HSS executes step 4 of clause 5.6.1.1. In addition, it checks whether the Maximum Latency, if provided, is within the range defined by operator policies, and if acceptable, the HSS sets the subscribed periodic RAU/TAU timer using the value of Maximum Latency, if it is provided. If the requested timer value is not acceptable, the HSS rejects the request by executing step 8, and provides a Cause value indicating the reason for the failure condition to the SCEF. In addition, the HSS checks whether the Suggested number of downlink packets is within the range defined by operator policies. If it is not, then the HSS rejects the request by executing step 8, and provides a Cause value indicating the reason for failure condition to the SCEF. + +If the Enhanced Multiple Event Monitoring feature is not supported and if the subscribed periodic RAU/TAU timer was previously set by a different Monitoring Request identified by a different SCEF Reference ID for the same UE then, depending on operator configuration, the HSS either performs step 8 to reject the Monitoring Request with an appropriate Cause or accepts the request. In the case that the HSS accepts this request, then it cancels the previously accepted Monitoring Request by including the SCEF Reference ID of that Monitoring Request in step 8. If the HSS supports Idle Status Indication, then it includes it in step 5. + +For group based processing, if the previously accepted Monitoring Request is associated with a group of UEs and the HSS is not cancelling the previously accepted Monitoring Request for all UEs in the group, then the HSS provides the indicated UEs (External Identifier or MSISDN) as well as operation indication (cancellation or addition) to the SCEF in step 8. + +If the Enhanced Multiple Event Monitoring feature is supported, and if the subscribed periodic RAU/TAU Timer, or Active Time, or Suggested number of downlink packets, or any combination were previously set by a different Monitoring Request or Network Parameter Configuration identified by a different SCEF Reference ID for the same UE, as long as the Maximum Latency (if received), and Maximum Response Time (if received) and Suggested number of downlink packets (if received) are within the range defined by operator policies, the HSS shall accept the request as follows: + +- If the newly received Maximum Latency is lower than the provided subscribed periodic RAU/TAU timer, the HSS shall set the subscribed periodic RAU/TAU timer using the newly received Maximum Latency. +- If the newly received Maximum Response Time is higher than the provided subscribed Active Time (i.e. previously provided Maximum Response Time), the HSS shall set the subscribed Active Time using the newly received Maximum Response Time. +- If Suggested number of downlink packets is newly received, the HSS shall add the newly received value to the currently used value of Suggested number of downlink packets if the aggregated value is within the operator defined range. If the aggregated value is not within the operator defined range, the HSS shall set the subscribed Suggested number of downlink packets according to operator defined range. + +The HSS may notify the SCEF (which then notifies the SCS/AS) of the actual value of Maximum Latency and Maximum Response Time that are being applied in the 3GPP network. + +5. The HSS executes step 5 of clause 5.6.1.1. In addition: + +- if the Enhanced Multiple Event Monitoring feature is not supported and the HSS accepts new monitoring event configuration and cancel the existing monitoring event configuration, the HSS includes the subscribed periodic RAU/TAU timer (if modified), new received Maximum Response Time (if provided), new received Suggested number of downlink packets (if configured or provided), Idle Status Indication (if provided) and the SCEF Reference ID for Deletion of the cancelled monitoring event configuration and appropriate Cause. + +When HSS accepts new configured Monitoring Event for UEs in step 4 above, the HSS includes the subscribed periodic RAU/TAU timer (if modified), Maximum Response Time (if provided), Suggested number of downlink packets (if configured or provided) and Idle Status Indication (if provided). + +When HSS removes a previously configured Monitoring Event for UEs in step 4 above, the HSS also deletes the previously configured Monitoring Event in the MME/SGSN, if applicable. + +- If the Enhanced Multiple Event Monitoring feature is supported, the HSS includes the subscribed periodic RAU/TAU timer (if modified), Maximum Response Time (if modified), Suggested number of downlink packets (if modified) and Idle Status Indication. + +When HSS modify a previously configured Monitoring Event for UEs in step 4 above, the HSS also updates the previously configured Monitoring Event in the MME/SGSN, if applicable. + +6. The MME/SGSN executes step 6 of clause 5.6.1.1 and starts watching for the UE entering connected mode. At every subsequent TAU/RAU procedure, the MME/SGSN applies the subscribed periodic RAU/TAU timer. +7. Step 7 of clause 5.6.1.1 is executed. +8. Step 8 of clause 5.6.1.1 is executed. The HSS may include the SCEF Reference ID of previously accepted Monitoring Request which needs to be cancelled and the cancellation cause. If the HSS, in step 4 above, decides to cancel Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS also includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +If the HSS, in step 4 above, decides to add Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +9. Step 9 of clause 5.6.1.1 is executed. If SCEF Reference ID of previously configured Monitoring Event for cancellation is included in step 8, then the SCEF executes steps 2-5 of clause 5.6.9 using the associated TLTRI towards the associated SCS/AS. + +#### 5.6.1.5 Specific Parameters for Monitoring Event: Location Reporting + +This monitoring event allows the SCS/AS to request either the Current Location or the Last Known Location of a UE. The supported Accuracy in the network may be at different levels, which are described in clause 4.9.2. Only One-time Reporting is supported for the Last Known Location. One-time and Continuous Location Reporting are supported for the Current Location. For Continuous Location Reporting, unless a Minimum Reporting Interval was provided, the serving node(s) sends a notification every time it becomes aware of a location change. The granularity depends on the accepted Accuracy. + +Minimum Reporting Interval is an optional parameter that indicates a minimum time interval between Location Reporting notifications. If this parameter was provided to the MME/SGSN, when sending each Location Reporting notification, the MME/SGSN starts a timer which runs for the duration of Minimum Reporting Interval. While the timer is running the MME/SGSN suppresses sending Location Reporting notification(s). If at least one Location Reporting notification was suppressed while the timer was running, on expiry of the timer the MME/SGSN sends location information that was contained in the latest suppressed Location Reporting notification and restarts the timer. If the MME/SGSN is relocated, the source MME/SGSN shall transfer the current value of the timer to the target MME/SGSN. The target MME/SGSN shall start the timer with the transferred value, i.e. with the time remaining from the Minimum Reporting Interval. + +NOTE 1: Due to the potential increase in signalling load, it is recommended that a continuous monitoring of current location on cell level is only applied for a limited number of subscribers and/or that the Minimum Reporting Interval option is used. + +1. The SCS/AS sets Monitoring Type to "Location Reporting", and adds Location Type, optionally Accuracy and optionally Minimum Reporting Interval prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. + +Location Type indicates whether the request is for Current Location or Last Known Location. + +2. The SCEF executes step 2 of clause 5.6.1.1. + +3. If Accuracy is included in step 1 then based on operator configuration the SCEF maps it to permissible granularity. If Accuracy is not included in step 1, the SCEF sets the granularity based on operator configuration. The SCEF adds Location Type, Accuracy and Minimum Reporting Interval (if included in step 1) prior to sending the Monitoring Request to the HSS as in step 3 of clause 5.6.1.1. +4. The HSS executes step 4 of clause 5.6.1.1. +5. Depending on the Location Type the HSS sets the "Current Location Request" (see TS 29.272 [31]), adds Accuracy and Minimum Reporting Interval (if included in step 3) prior to sending the Insert Subscriber Data Request to the MME/SGSN as in step 5 of clause 5.6.1.1. +6. The MME/SGSN executes step 6 of clause 5.6.1.1 and depending on the requested Accuracy invokes the appropriate procedures as defined in TS 23.401 [7] or TS 23.060 [6] for determining the location as requested. Unless it is a One-time request, the MME/SGSN starts watching for cell/RA/TA/eNodeB changes, depending on requested Accuracy. + +If Minimum Reporting Interval is included in step 5, the MME/SGSN sends Location Reporting notifications with Minimum Reporting Interval option. + +- 7-9. Steps 7-9 of clause 5.6.1.1 are executed and include the report of the current or last known location, depending on what was requested. Depending on operator configuration, the SCEF either maps the reported 3GPP system specific location information to the accepted Accuracy format or sends it as-is to the SCS/AS. + +#### 5.6.1.6 Specific Parameters for Monitoring Event: Change of IMSI-IMEI(SV) Association + +Change of IMSI-IMEI(SV) indicates a change of the ME (IMEI(SV)) that uses a specific subscription (IMSI). It is based on the HSS being informed by the MME about the UE's IMEI(SV) according to the procedures defined in TS 23.401 [7]. The support of this Monitoring Event by the SGSN requires the support of the Automatic Device Detection (ADD) function/feature defined in TS 23.060 [6]. + +1. The SCS/AS sets Monitoring Type to "Change of IMSI-IMEI(SV) Association", and adds Association Type prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. + +Association Type indicates whether change of IMEI or IMEISV to IMSI association shall be detected. + +2. The SCEF executes step 2 of clause 5.6.1.1. +3. The SCEF adds Association Type prior to sending the Monitoring Request to the HSS as in step 3 of clause 5.6.1.1. +4. The HSS executes step 4 of clause 5.6.1.1. +- 5-7. Steps 5-7 of clause 5.6.1.1 shall not be executed for this Monitoring Event. +- 8-9. Steps 8-9 of clause 5.6.1.1 are executed. + +#### 5.6.1.7 Specific Parameters for Monitoring Event: Roaming Status + +This monitoring event allows the SCS/AS to query the UE's current roaming status (the serving PLMN and/or whether the UE is in its HPLMN) and to get notified when that status changes. It is based on the HSS being informed of the UE's serving PLMN by the MME according to TS 23.401 [7] and by the SGSN according to TS 23.060 [6]. + +1. The SCS/AS sets Monitoring Type to "Roaming Status" prior to sending the Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. Optionally, it includes the "PLMN Information" parameter to request inclusion of the UE's Serving PLMN ID in the Monitoring Event Report. +2. The SCEF executes step 2 of clause 5.6.1.1. +3. The SCEF includes "PLMN Information", if sent in step 1, prior to sending Monitoring Request to the HSS as in step 3 of clause 5.6.1.1. +4. The HSS executes step 4 of clause 5.6.1.1. +- 5-7. Steps 5-7 of clause 5.6.1.1 shall not be executed for this Monitoring Event. + +- 8-9. Steps 8-9 of clause 5.6.1.1 are executed. The Monitoring Event Report for this event is sent in the Monitoring Response message. The Monitoring Event Report indicates whether the UE is presently roaming or not as specified in clause 5.6.3.6. If PLMN Information was requested in step 1, and the operator policies allow, then the HSS includes for each Roaming Status in the Monitoring Event Report: +- the HPLMN PLMN-Id if the UE is in the HPLMN; or + - the Visited PLMN-Id (see TS 29.272 [31]) if the UE is in the VPLMN. + +#### 5.6.1.8 Specific Parameters for Monitoring Event: Communication failure + +This monitoring event allows the SCS/AS to be notified of communication failure events, identified by RAN/NAS Release Cause codes per TS 23.401 [7]. + +1. The SCS/AS sets Monitoring Type to "Communication Failure" prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. +2. The SCEF executes step 2 of clause 5.6.1.1. +3. The SCEF executes step 3 of clause 5.6.1.1. +4. The HSS executes step 4 of clause 5.6.1.1. +5. The HSS executes step 5 of clause 5.6.1.1. +6. The MME/SGSN executes step 6 of clause 5.6.1.1 and starts watching for communication failure events. +- 7-9. Steps 7-9 of clause 5.6.1.1 are executed. + +#### 5.6.1.9 Specific Parameters for Monitoring Event: Availability after DDN Failure + +This monitoring event allows the SCS/AS to be notified of availability of the UE after a DDN failure has occurred (see clause 5.7.1 Availability Notification after DDN Failure). + +1. The SCS/AS sets Monitoring Type to "Availability after DDN Failure", and optionally Idle Status Indication prior to sending the Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. +2. The SCEF executes step 2 of clause 5.6.1.1. +3. The SCEF executes step 3 of clause 5.6.1.1 without adding Max Number of Reports, since the "Availability after DDN Failure" is an ongoing event that needs explicit deletion (see clause 5.6.1 for a description of Monitoring Event Deletion procedures) to cancel further reports. +- 4-5. Steps 4-5 of clause 5.6.1.1 are executed. +6. The MME/SGSN executes step 6 of clause 5.6.1.1 and starts watching for UE availability after DDN failure events. +- 7-9. Steps 7-9 of clause 5.6.1.1 are executed. + +#### 5.6.1.10 Specific Parameters for Monitoring Event: PDN Connectivity Status + +This monitoring event allows the SCS/AS to be notified of the PDN Connectivity status when PDN Connections are created or deleted for the UE, and the existing PDN Connectivity status at the monitoring event configuration. The PDN Connectivity Status monitoring event report includes for each PDN Connection (that matches the requested APN if an APN has been specified) the IP address(es) allocated for the UE PDN connection(s), the PDN Types and optionally the APNs. This may be used by the SCS/AS to initiate communication with the UE, or to know when communication is no longer possible. Reporting is also done for PDN Connections using T6a/T6b connection towards the SCEF. + +NOTE 1: For UE using a power saving method (e.g. eDRX or PSM), the SCS/AS can also invoke the UE Reachability monitoring event when the SCS/AS has DL data to send. + +1. The SCS/AS sets Monitoring Type to "PDN Connectivity Status" and sends the Monitoring Request to the SCEF as in step 1 of clause 5.6.1.1. + +2. The SCEF executes step 2 of clause 5.6.1.1. +3. The SCEF executes step 3 of clause 5.6.1.1. SCEF includes the APN for which the PDN Connectivity Status is to be monitored in the Monitoring Request to HSS. SCEF may also request PDN Connectivity Status for all PDN Connections regardless of APN (e.g. if APN is unknown in SCEF). + +NOTE 2: The SCEF uses the SCS/AS Identifier and External Group Identifier, External Identifier or MSISDN that was obtained in step 1 to determine what APN will be used to enable PDN Connectivity between the UE and the SCS/AS. This determination is based on local policies. + +- 4-5. Steps 4-5 of clause 5.6.1.1 are executed. The HSS shall check if the SCS/AS is authorized to use the PDN Connectivity Status Monitoring Event and/or if operator policies allow the PDN Connectivity Status Monitoring Event usage for this subscriber (e.g. the subscription/UE is for CIoT). If an External Identifier was included in the authorization request, the HSS maps the external identifier to IMSI and/or MSISDN and updates the SCEF ID field of the PDN subscription context for the provided APN with the requesting SCEF's ID. Otherwise, if an External Group Identifier was included in the authorization request, the HSS authorizes the monitoring event configuration request for the received External Group Identifier, maps the External Group Identifier to a list of External Identifiers and maps the external identifiers to IMSIs and/or MSISDNs and updates the SCEF ID fields of the PDN subscription contexts for the provided APN with the requesting SCEF's ID. If the authorization check fails, then the HSS rejects the request by executing step 8, and provides a Cause value indicating the reason for failure condition to the SCEF. + +6. The MME/SGSN executes step 6 of clause 5.6.1.1 and if PDN Connection(s) already exists (that matches the requested APN if an APN has been specified), the MME shall immediately send a PDN Connectivity Status event report for the existing PDN Connections. The MME/SGSN then starts watching for any further PDN Connectivity Status events. + +- 7-9. Steps 7-9 of clause 5.6.1.1 are executed. + +### 5.6.2 Monitoring Events configuration and deletion directly at the MME/SGSN + +#### 5.6.2.1 Configuration Procedure + +Figure 5.6.2.1-1 illustrates the procedure of configuring monitoring at the MME/SGSN. The procedure is common for various monitoring event types. Common parameters for this procedure are detailed in clause 5.6.2.2. The steps specific to different Monitoring Event types are detailed in clause 5.6.2.3. This procedure is not applicable for group configuration. + +![Sequence diagram illustrating the monitoring event configuration and deletion directly at MME/SGSN procedure. The diagram shows interactions between MME/SGSN, HSS, SCEF, and SCS/AS.](c14d36776b70c47a6bad152b3a8a5ec6_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + participant MME/SGSN + + Note right of SCEF: 2. SCEF handling + SCS/AS->>SCEF: 1. Monitoring Request + SCEF->>HSS: 2a/2b. External Group ID Resolution + SCEF->>MME/SGSN: 3. Monitoring Request + Note left of MME/SGSN: 4. MME/SGSN handling + MME/SGSN->>SCEF: 5. Monitoring Response + SCEF->>SCS/AS: 6. Monitoring Response + +``` + +Sequence diagram illustrating the monitoring event configuration and deletion directly at MME/SGSN procedure. The diagram shows interactions between MME/SGSN, HSS, SCEF, and SCS/AS. + +Figure 5.6.2.1-1: Monitoring event configuration and deletion directly at MME/SGSN procedure + +1. The SCS/AS sends a Monitoring Request (SCS/AS Identifier, Monitoring Type, Monitoring Duration, Maximum Number of Reports, T8 Destination Address, TLTRI for Deletion) message to the SCEF. The SCEF assigns a TLTRI that identifies the Monitoring Request. + +NOTE: A relative priority scheme for the treatment of multiple SCS/AS Monitoring Requests, e.g. for deciding which requests to serve under overload condition, can be applied. This priority scheme is used locally by the SCEF, i.e. it is not used nor translated in procedures towards other functions. + +2. The SCEF stores the TLTRI, and also assigns it to an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Monitoring Request is malformed or the SCS/AS has exceeded its quota or rate of submitting monitoring requests, the SCEF performs step 6 and provides a Cause value appropriately indicating the error. The SCEF stores the Monitoring Duration, the Maximum Number of Reports, the T8 Destination Address, the SCS/AS Identifier. If the SCEF received a TLTRI for Deletion, the SCEF looks up the SCEF context pointed to by the TLTRI to derive the related SCEF Reference ID for Deletion. If an External Group Identifier(s) was included in the request of step 1, then flow proceeds to step 2a, otherwise steps 2a and 2b are skipped. +- 2a. When the SCS/AS includes External Group Identifier(s) in the monitoring request, the SCEF sends an External Group ID Resolution Request (External Group Identifier(s)) message to the HSS. +- 2b. The HSS resolves the External Group Identifier(s) to IMSI-Group Identifier(s) and sends an External Group ID Resolution Response (IMSI-Group Identifier(s)) message to the SCEF. +3. The SCEF sends a Monitoring Request (SCEF ID, SCEF Reference ID, Monitoring Type, Monitoring Duration, Maximum Number of Reports, SCEF Reference ID for Deletion) message to the MME(s)/SGSN(s). +4. The MME/SGSN examines whether it can accept the request from that SCEF based on operator configuration or whether it serves the SCEF Reference ID for Deletion and can delete it. If acceptable, the MME/SGSN stores SCEF ID, SCEF Reference ID, Monitoring Duration, Maximum Number of Reports and other relevant parameters unless it is a One-time request and the Monitoring Event is available to the MME/SGSN at this time. The MME/SGSN deletes the monitoring configuration identified by the SCEF Reference ID for Deletion, if provided. +5. The MME/SGSN sends a Monitoring Response (SCEF Reference ID, Cause, Monitoring Event Report) message to the SCEF to acknowledge acceptance of the Monitoring Request and to provide the requested monitoring information or to acknowledge the deletion of the identified monitoring event configuration, if it was requested. +6. The SCEF sends a Monitoring Response (TLTRI, Cause, Monitoring Event Report) message to the SCS/AS to acknowledge acceptance of the Monitoring Request and to provide the requested monitoring information in Monitoring Event Report parameter or to acknowledge the deletion of the identified monitoring event configuration, if it was requested. + +#### 5.6.2.2 Void + +#### 5.6.2.3 Specific Steps for Monitoring Event: Number of UEs present in a geographic area + +This monitoring event allows the SCS/AS to ask for the number of UEs that are in the geographic area described by the SCS/AS. The SCS/AS may ask for the UEs that the system knows by its normal operation to be within the area (Last Known Location) or the SCS/AS may request the system to also actively look for the UEs within the area (Current Location). Whether the request is for Current Location or Last Known Location is indicated by the parameter Location Type. For this monitoring event only One-time reporting is supported and the Monitoring Duration as well as the Maximum Number of Reports parameters shall be ignored by the SCEF if present in the request. + +In this release only Last Known Location is supported for this monitoring event. + +When the SCS/AS includes External Group Identifier(s) in the monitoring request, the MME/SGSN counts the number of UEs at the requested location that have each IMSI Group Identifier(s) in its subscription information corresponding to the External Group Identifier(s) received from SCS/AS. The report that is provided by the network to the SCS/AS shall include the number of UEs in the geographic area per External Group Identifier. + +NOTE 1: The system load resulting from this request may be highly dependent on Location Type. + +1. The SCS/AS sets Monitoring Type to "Number of UEs present in a geographic area" and adds Location Type and Geographic Area before sending Monitoring Request to the SCEF as in step 1 of clause 5.6.2.1. The request may optionally include External Group Identifier(s). +2. The SCEF executes step 2 of clause 5.6.2.1. In addition, the SCEF maps the Geographic Area to a list of cells, eNodeBs and/or RAI(s)/TAI(s) and identifies the MMEs/SGSNs serving them by resolving the RA(s)/TA(s) to node addresses. + +NOTE 2: The mapping of Geographic Areas to serving operator (MNO) network list of cells, eNodeBs and/or RAs/TAs, and the identity of the associated serving nodes (e.g. MMEs/SGSNs) is configured at the SCEF. + +3. The SCEF adds Monitoring Type, Location Type, list of cells, eNodeBs and/or RAI(s)/TAI(s) before sending the Monitoring Request to those MMEs/SGSNs identified in step 3 of clause 5.6.2.1. If External Group Identifier(s) were included in step 1, then the IMSI-Group Identifier(s) that were obtained in step 2 are included in the request to the MME/SGSN. +4. The MME/SGSN executes step 4 of clause 5.6.2.1. In addition, if the request is for Last Known Location with cell or eNodeB granularity or for a location with RA/TA granularity, the MMEs/SGSNs collect all UEs for which the MME/SGSN stores a last known cell, eNodeB or RA/TA registration information that corresponds to the requested location. + +NOTE 3: For Location Type Last Known Location, how the MME/SGSN determines the candidate set of UEs to be included is left to implementation. + +5. The MME/SGSN executes step 5 of clause 5.6.2.1. The response from the MME/SGSN includes the count of the number of UEs at the requested location. If the request of step 3 included an IMSI-Group Identifier(s), the report from the MME/SGSN shall include the number of UEs in the geographic area per IMSI-Group Identifier(s). When IMSI-Group Identifier(s) were included in the request of step 3, the MME/SGSN may optionally, depending on operator configuration, include either the External Identifiers or the MSISDNs of the UEs that are associated with each IMSI-Group Identifier(s). +6. The SCEF combines the results from all involved MMEs/SGSNs to the total sum, i.e. the Number of UEs, and executes step 6 of clause 5.6.2.1. When External Identifiers or MSISDNs were included in the results that were received from the MME(s)/SGSN(s) in step 5, they are included in the response to the SCS/AS. + +### 5.6.3 Reporting of Monitoring Events from the HSS or the MME/SGSN + +#### 5.6.3.1 Reporting Procedure + +The following figure illustrates the common procedure flow of reporting Monitoring Events that are detected by the MME/SGSN or HSS. The steps specific to different Monitoring Event types are detailed in clauses 5.6.3.2 to 5.6.3.8. + +![Sequence diagram of the monitoring event reporting procedure. Lifelines: MME/SGSN, HSS, SCEF, and Monitoring Destination node. The sequence starts with 1a. Event Detection at MME/SGSN and 1b. Event Detection at HSS. 2a. Monitoring Indication is sent from MME/SGSN to SCEF. 2b. Monitoring Indication is sent from HSS to SCEF. 3a. Monitoring Indication is sent from SCEF to Monitoring Destination node. 3b. Monitoring Indication Response is sent from Monitoring Destination node back to SCEF.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant MME/SGSN + participant HSS + participant SCEF + participant MDN as Monitoring Destination node + + Note left of MME/SGSN: 1a. Event Detection + Note left of HSS: 1b. Event Detection + MME/SGSN->>SCEF: 2a. Monitoring Indication + HSS->>SCEF: 2b. Monitoring Indication + SCEF->>MDN: 3a. Monitoring Indication + MDN-->>SCEF: 3b. Monitoring Indication Response + +``` + +Sequence diagram of the monitoring event reporting procedure. Lifelines: MME/SGSN, HSS, SCEF, and Monitoring Destination node. The sequence starts with 1a. Event Detection at MME/SGSN and 1b. Event Detection at HSS. 2a. Monitoring Indication is sent from MME/SGSN to SCEF. 2b. Monitoring Indication is sent from HSS to SCEF. 3a. Monitoring Indication is sent from SCEF to Monitoring Destination node. 3b. Monitoring Indication Response is sent from Monitoring Destination node back to SCEF. + +**Figure 5.6.3.1-1: Monitoring event reporting procedure** + +1a. A Monitoring Event is detected by the MME/SGSN at which the Monitoring Event is configured. + +1b. Either a Monitoring Event is detected by the HSS, or the HSS needs to inform the SCEF about the change of status (suspend/resume/cancel) of an ongoing monitoring if an event related with the change of monitoring support at the serving node, (e.g. lack of monitoring support in MME/SGSN or revocation of monitoring authorization) is detected in the HSS. The HSS also stores the time when the Event is detected or the status is changed. + +2a. The MME/SGSN sends a Monitoring Indication (SCEF Reference ID(s), Monitoring Event Report, User Identity) message to the SCEF. The SCEF store the time when it receives the Monitoring Indication. + +If the Monitoring Event configuration was triggered by a One-time Monitoring Request, then the Monitoring Event configuration is deleted by the MME/SGSN upon completion of this step. If the MME/SGSN has a Maximum Number of Reports stored for this monitoring task, the MME/SGSN shall decrease its value by one. If the value of remaining number of reports is zero, the MME/SGSN shall locally remove the Monitoring Event Configuration. If the Monitoring Event configuration includes User Identity, the MME/SGSN sends the Monitoring Indication message including the User Identity. So that the SCEF can determine what groups the report pertains to, multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication. + +2b. When reporting for an individual UE or individual Group Member UE, the HSS sends a Monitoring Indication (SCEF Reference ID(s), External ID or MSISDN, Monitoring Event Report) message to the SCEF. External ID or MSISDN are only included if the indication is associated with an individual Group Member UE. If the Monitoring Event configuration was triggered by a One-time Monitoring Request, then the Monitoring Event configuration for the individual UE and for the individual group member UE is deleted by the HSS upon completion of this step. If the HSS has a Maximum Number of Reports stored for this monitoring task, the HSS shall decrease its value by one. Based on SCEF Reference ID, the SCEF can determine what groups the report pertains to. Multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication. + +If Group Reporting Guard Time was provided during the Monitoring Event configuration procedure, the HSS accumulates a Monitoring Event for the UEs of the group within the Group Reporting Guard Time. After the Group Reporting Guard Time expiration, the HSS send a Monitoring Indication (SCEF Reference ID, (Monitoring Event Report(s), External ID or MSISDN) Set, External Group ID) message to the SCEF. For each group member UE all the Monitoring Event Report and the corresponding stored time(s) are sent to the SCEF. + +The External Group ID may be included in the message to indicate that the event has been detected for all group members. When the External Group ID is included in the indication, External ID(s) and MSISDN(s) are optional. + +NOTE: For the group-basis Monitoring Event configuration, the HSS may divide the accumulated Monitoring Event Reports into multiple Monitoring indication messages due to the limitation of the message size. + +3a. Using the SCEF Reference ID, the SCEF retrieves the associated TLTRI along with the T8 Destination Address. + +If the TLTRI refers to a Monitoring Event Configuration for a single UE, the SCEF sends a Monitoring Indication (TLTRI, Cause, Monitoring Event Report) message to the identified destination. If the TLTRI refers to a group-based Monitoring Event configuration, and if no Group Reporting Guard Time was set, then the SCEF sends a Monitoring Indication (TLTRI(s), Cause, Monitoring Event Report) message to the identified destination. So that the SCEF can determine what groups the report pertains to, multiple TLTRIs can be included if the UE is part of multiple groups that require the same monitoring indication. + +If the TLTRI refers to a group-based Monitoring Event Configuration, and if Group Reporting Guard Time was provided during the Monitoring Event configuration procedure, then the SCEF accumulates Monitoring Event for the UEs of the group until the Group Reporting Guard Time expiry. Upon expiration of which, the SCEF sends a Monitoring Indication (TLTRI, Cause, list of (External Identifier or MSISDN, Monitoring Event Report(s))) message to the identified destination. A list of accumulated Monitoring Event Report for each group member UE identified by either External Identifier or MSISDN is also included. For each group member UE all the received Monitoring Event Report, and the corresponding time received at SCEF or the time value sent by HSS, are sent to the SCS/AS. + +For individual UE, if a report is received (step 2a or step 2b) for One-time Monitoring Request or the maximum number of reports is reached for a Continuous Monitoring Request, the SCEF requests the HSS (for monitoring events configured via HSS) to delete the related monitoring event configuration for the individual UE and deletes also its associated Monitoring Event configuration according to the procedure of clause 5.6.1.1 step 3-8. + +For an individual group member UE, if a report is received (step 2a or step 2b) for One-time Monitoring Request or the maximum number of reports is reached for a Continuous Monitoring Request, based on the Number of UEs received in step 4a in clause 5.6.1.1 and local policy, the SCEF shall either: + +- request the HSS (for monitoring events configured via HSS) to delete the related monitoring event configuration for the individual group member UE; or +- wait until reports for all group member UEs are complete and then request the HSS (for monitoring events configured via HSS) to delete the related monitoring event configuration. + +The SCEF uses the identity of individual group member UE(s) (i.e. External Identifier or MSISDN) received in the step 2a or step 2b and the Number of UEs received in step 4a in clause 5.6.1.1 to determine if reporting for the group is complete. If it is complete, the SCEF deletes the associated Monitoring Event configuration for the group. + +3b. For each Monitoring Indication message received in step 3a, the SCS/AS sends a Monitoring Indication Response (Cause) message to the SCEF. Cause value reflects successful or unsuccessful acknowledgement of Monitoring Indication message. + +When the Monitoring Duration expires for a continuous Monitoring Request in the HSS, the MME/SGSN or the SCEF, then each of these nodes shall locally delete the related Monitoring Event configuration associated with the individual UE or group member UE. + +#### 5.6.3.2 Reporting Event: Loss of connectivity + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the mobile reachability timer expires, when an active UE is purged (see TS 29.272 [31]), when ISR is disabled and a UE, MME, SGSN, or HSS initiated detach occurs (see TS 23.401 [7], TS 23.060 [6]), or when ISR is enabled and a UE, MME, SGSN, or HSS initiated detach occurs and the MME or SGSN sends a Detach Notification message to the SGSN or MME with a Cause value that indicates complete, see (TS 23.401 [7]). +- 2a. Step 2a of clause 5.6.3.1 is executed. +3. Step 3 of clause 5.6.3.1 is executed. + +#### 5.6.3.3 Reporting Event: UE reachability + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the UE changes to connected mode or when the UE will become reachable for paging (for a UE using extended idle mode DRX). + +If Maximum Response Time was included in step 5 of clause 5.6.1.4, then the MME/SGSN keeps the corresponding S1-U/Iu-PS connections of the UE for a duration of at least the Maximum Response Time less the UE's PSM Active Timer value. If the UE uses extended idle mode DRX, the MME/SGSN takes the Maximum Response Time into account to determine when to report this monitoring event before the next Paging Occasion occurs. + +- 1b. This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS detects that the UE is reachable for SMS. +- 2a. Step 2a of clause 5.6.3.1 is executed. The Monitoring Event Report indicates if the event was caused by the UE changing to connected mode or by the UE becoming reachable for paging. +- 2b. Step 2b of clause 5.6.3.1 is executed. +3. Steps 3a-3b of clause 5.6.3.1 are executed. The Monitoring Event Report indicates if the event was caused by the UE changing to connected mode or by the UE becoming reachable for paging. If Idle Status Indication was not requested during Monitoring Event configuration, then the flow stops here. +4. UE transitions to idle mode as specified in TS 23.401 [7]. +5. If Idle Status Indication was requested during Monitoring Event configuration, and the MME/SGSN supports Idle Status Indication, then MME executes step 1a, and includes the time at which the UE transitioned into idle mode, its granted active time (if PSM is enabled), the eDRX cycle length (if extended idle mode DRX is enabled), the periodic TAU/RAU timer granted to the UE by the MME and the Suggested number of downlink packets if a value was provided to the S-GW in the message. +6. The SCEF executes steps 3a-3b of clause 5.6.3.1, and includes additional parameters specified in step 5 above. + +#### 5.6.3.4 Reporting Event: Location Reporting + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME/SGSN detects that the UE changes location with the granularity as requested by the monitoring event configuration. +- 2a. Step 2a of clause 5.6.3.1 is executed. +3. Step 3 of clause 5.6.3.1 is executed. Depending on operator configuration, the SCEF either maps the reported 3GPP system specific location information to the accepted Accuracy format, sent in step 9 of clause 5.6.1.5, or sends it as-is to the SCS/AS. + +#### 5.6.3.5 Reporting Event: Change of IMSI-IMEISV association + +- 1b. This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS receives from a serving node an IMEISV that is different from the IMEISV stored by the HSS for the IMSI. +- 2b. Step 2b of clause 5.6.3.1 is executed. +3. Step 3 of clause 5.6.3.1 is executed. The Monitoring Indication message includes the new IMEISV. + +### 5.6.3.6 Reporting Event: Roaming Status + +- 1b. This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS receives from a serving node a serving PLMN ID that is different from the one stored by the HSS. +- 2b. Step 2b of clause 5.6.3.1 is executed. If the UE is registered to different PLMNs via 3GPP and N3GPP Access Type, then the HSS includes two instances of Roaming Status in the Monitoring Indication message. +3. Step 3 of clause 5.6.3.1 is executed. The monitoring information indicates the ID of the serving PLMN and whether it is the home or a roaming PLMN. Operator policies in the SCEF may restrict the report, e.g. to indicate + +only whether the UE is in the home or in a roaming PLMN. The SCEF includes all Roaming Status instances that it received from the HSS. + +### 5.6.3.7 Reporting Event: Communication failure + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME/SGSN becomes aware of a RAN or NAS failure event. +- 2a. Step 2a of clause 5.6.3.1 is executed. +3. Step 3 of clause 5.6.3.1 is executed. Based on operator configuration, the SCEF reports either the received failure cause code(s) as-is or an abstracted value. + +### 5.6.3.8 Reporting Event: Availability after DDN failure + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when the MME/SGSN becomes aware of UE availability after DDN failure. +- 2a. Step 2a of clause 5.6.3.1 is executed. +3. Step 3 of clause 5.6.3.1 is executed. + +### 5.6.3.9 Reporting Event: PDN Connectivity Status + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.3.1, which is when a new PDN connection is created for the UE, or when a PDN connection is deleted for the UE, or for PDN connections that exist when the PDN Connectivity Status monitoring event is configured in the MME/SGSN. Reporting is also done for PDN Connections using T6a/T6b connection towards the SCEF. +- 2a. Step 2a of clause 5.6.3.1 is executed. The Monitoring Event Report indicates if the event was caused by a creation or deletion of a PDN Connection. The Monitoring Event Report indicates IP address, PDN Type, APN, 3GPP Interface Indication, and the new PDN Connectivity Status i.e. "created" or "deleted". For PDN Type Non-IP, the reported IP address may be the address allocated for SGi PtP tunnelling based on UDP/IP (see clause 4.3.17.8.3.3.2 of TS 23.401 [7]). MME leaves the IP address field empty in the Monitoring Event Report if it is not available. When reporting IPv6 address, the MME reports the IPv6 prefix when the full IPv6 address is not available. The 3GPP Interface Indication is set to "API-connectivity" for PDN Connections using T6a/T6b connection towards the SCEF, or set to "IP-connectivity" for SGi connectivity using IP based PDN Types, or set to "Other" for SGi connectivity using PDN Type Non-IP. + +NOTE: If NAT is used, the reported IP Address is the UE's private IP Address which is then different than the UE's public IP Address. If no IP Address is assigned to the UE during PDN connection establishment (e.g. when DHCP is used after PDN connection establishment) no IP Address is included in the report. + +3. Steps 3a-3b of clause 5.6.3.1 are executed. The SCEF sends the Monitoring Event Report to SCS/AS based on APN determined at Monitoring Event configuration (see clause 5.6.1.10). + +## 5.6.4 Monitoring events configuration and reporting via PCRF + +### 5.6.4.1 Request of monitoring event reporting + +Figure 5.6.4-1 illustrates the procedure to request monitoring events reporting via PCRF with a reference to TS 23.203 [27]. The procedure is common for any monitoring event defined in clause 4.5.6.3 "Monitoring Events via PCRF". + +![Sequence diagram illustrating the procedure for requesting monitoring via PCRF. The diagram shows four lifelines: PCEF, PCRF, SCEF, and SCS/AS. The sequence of messages is: 1. SCS/AS sends a Monitoring Request to SCEF; 2. SCEF selects monitoring via PCRF; 3. PCRF initiates an IP-CAN session modification procedure (referenced to TS 23.203); 4. SCEF sends a Monitoring Response to SCS/AS.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` +sequenceDiagram + participant SCS/AS + participant SCEF + participant PCRF + participant PCEF + Note right of SCEF: 2. SCEF selects monitoring via PCRF + SCS/AS->>SCEF: 1. Monitoring Request + Note over PCEF, PCRF: 3. PCRF initiated IP-CAN session modification procedure in 23.203 + SCEF->>SCS/AS: 4. Monitoring Response +``` + +Sequence diagram illustrating the procedure for requesting monitoring via PCRF. The diagram shows four lifelines: PCEF, PCRF, SCEF, and SCS/AS. The sequence of messages is: 1. SCS/AS sends a Monitoring Request to SCEF; 2. SCEF selects monitoring via PCRF; 3. PCRF initiates an IP-CAN session modification procedure (referenced to TS 23.203); 4. SCEF sends a Monitoring Response to SCS/AS. + +**Figure 5.6.4-1: Requesting monitoring via PCRF** + +1. The SCS/AS sends a Monitoring Request to the SCEF, including the information listed in step 1 of clause 5.6.1.1. +2. The SCEF checks that the SCS/AS is authorised to send monitoring request as defined in step 2 of clause 5.6.1.1. If an error is detected, then the message of step 4 is sent to SCS/AS with Cause value appropriately indicating the error and the flow stops at this step. +3. If operator policies indicate that monitoring is performed via PCRF, for the events listed in clause 4.5.6, the SCEF, acting as an Application Function, triggers the PCRF initiated-IP-CAN session modification procedure defined in TS 23.203 [27]. +4. The SCEF sends a Monitoring Response (Cause, Monitoring Event Report) message to the SCS/AS. If the SCEF received a Monitoring Event Report then it includes it in the Monitoring Response message. + +#### 5.6.4.1a Request of monitoring event reporting for a group of UEs + +Figure 5.6.4.1a-1 illustrates the procedure to request monitoring events reporting via PCRF for a group of UEs with a reference to TS 23.203 [27]. + +For monitoring for a group of UEs, the SPR is configured with the External Group Identifier the UE belongs to. + +![Sequence diagram illustrating the process of requesting monitoring via PCRF for a group of UEs. The diagram shows interactions between PCEF, PCRF, SCEF, and SCS/AS. The process starts with a Monitoring Request from SCS/AS to SCEF. SCEF then selects monitoring via PCRF and sends a Monitoring Request to PCRF. PCRF responds with a Monitoring Request ACK. SCEF then sends a Monitoring Response to SCS/AS. A box indicates that for each UE with an active IP-CAN session, the PCRF initiates an IP-CAN session modification procedure. Finally, PCRF sends a Monitoring Indication to SCEF, which then sends 8a. Monitoring Indication to SCS/AS and receives 8b. Monitoring Indication Response from SCS/AS.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant PCRF + participant PCEF + + Note right of SCEF: 2. SCEF selects monitoring via PCRF + + SCS/AS->>SCEF: 1. Monitoring Request + SCEF->>PCRF: 3. Monitoring Request + PCRF->>SCEF: 4. Monitoring Request ACK + SCEF->>SCS/AS: 5. Monitoring Response + Note left of PCEF: 6. For each UE that has an IP-CAN session active, PCRF initiated IP-CAN session modification procedure in 23.203 + PCRF->>SCEF: 7. Monitoring Indication + SCEF->>SCS/AS: 8a. Monitoring Indication + SCS/AS->>SCEF: 8b. Monitoring Indication Response + +``` + +Sequence diagram illustrating the process of requesting monitoring via PCRF for a group of UEs. The diagram shows interactions between PCEF, PCRF, SCEF, and SCS/AS. The process starts with a Monitoring Request from SCS/AS to SCEF. SCEF then selects monitoring via PCRF and sends a Monitoring Request to PCRF. PCRF responds with a Monitoring Request ACK. SCEF then sends a Monitoring Response to SCS/AS. A box indicates that for each UE with an active IP-CAN session, the PCRF initiates an IP-CAN session modification procedure. Finally, PCRF sends a Monitoring Indication to SCEF, which then sends 8a. Monitoring Indication to SCS/AS and receives 8b. Monitoring Indication Response from SCS/AS. + +**Figure 5.6.4.1a-1: Requesting monitoring via PCRF for a group of UEs** + +1. The SCS/AS sends a Monitoring Request to the SCEF, including the information listed in step 1 of clause 5.6.1.1 in figure 5.6.1.1-1. Maximum Number of Reports and Monitoring Duration shall not be included in the request. +2. The SCEF checks that the SCS/AS is authorised to send monitoring request as defined in step 2 of clause 5.6.1.1 in figure 5.6.1.1-1. If an error is detected, steps 3-4 are skipped, the message of step 5 is sent to SCS/AS with Cause value appropriately indicating the error, and the flow stops. +3. If operator policies indicate that monitoring is performed via PCRF, for the events listed in clause 4.5.6 applicable for a group of UEs, the SCEF triggers a Monitoring Request (SCEF Reference ID, External Group Identifier, event to monitor) over Nt interface to each PCRF in the operator's network. +4. Each PCRF that serves a UE that is associated with the External Group Identifier stores the External Group Identifier, the event to monitor, the SCEF Reference ID, and the SCEF that sent the request and then sends a Monitoring Response message to the SCEF. If a PCRF serves no UEs that are associated with the External Group Identifier, the Monitoring Response Indicates that the PCRF is not currently serving any of the group members, and steps 6 and 7 are skipped for that PCRF. +5. The SCEF stores an indication that monitoring has been requested for the group of UEs for each PCRF that did not respond in step 4 with an indication that it is serving no group members. and then Once all PCRFs have responded in step 4, the SCEF and then sends a Monitoring Response (Cause) message to the SCS/AS. +6. Each PCRF that found a UE that has the External Group Identifier associated with it performs the following steps: + - For each UE that has an IP-CAN session established, the PCRF initiated-IP-CAN session modification procedure is triggered as defined in TS 23.203 [27]. Note that if the UE has multiple IP-CAN session established, only one PCRF initiated IP-CAN session modification is needed. The PCRF stored the SCEF address to report monitoring events for this group. + +7. The PCRF sends a Monitoring Indication ((MSISDN or External ID, SCEF Reference ID, Cause) message to the SCEF. The Monitoring Indication may include reports for multiple UEs. If the Monitoring Indication does not include information for all UEs in the group, then the PCRF may send multiple Monitoring Indications to the SCEF. The PCRF indicates to the SCEF when the result for the last UE in the group is sent. The same PCRF will not send duplicate reports for the same UE to the SCEF. + +NOTE: A UE may have established multiple IP-CAN sessions, each IP-CAN session under control of a different PCRFs. + +- 8a. The SCEF sends a Monitoring Indication (TLTRI, MSISDN or External ID, Cause) message to the SCS/AS. The Monitoring Indication may include reports for multiple UEs. If the Monitoring Indication does not include information for all UEs in the group, then the SCEF may send multiple Monitoring Indications to the SCS/AS. The SCEF indicates to the SCS/AS when the result for the last UE is sent. The SCEF may wait for Monitoring Indication messages from multiple PCRFs so that it can send an aggregated response to the SCS/AS. + +- 8b. For each Monitoring Indication message received in step 8a, the SCS/AS sends a Monitoring Indication Response (Cause) message to the SCEF. Cause value reflects successful or unsuccessful acknowledgement of Monitoring Indication message. + +#### 5.6.4.2 Common Parameters of the request reporting procedure + +The following parameters are applicable when the procedure for monitoring via PCRF is used: TLTRI, Monitoring Type, Priority and T8 Destination Address. + +The Monitoring types are defined in clause 4.5.6. The Priority is relevant to the SCEF, not transferred over Rx or Nt. + +For single UE monitoring, the following parameters are not applicable when the procedure for monitoring via PCRF is used: SCEF Address, SCEF Reference ID, and Maximum Number of Reports. The SCEF address is not needed as Rx procedures do not require the AF address to be sent. The Maximum Number of Reports is not needed as only one time report is supported. + +The following parameters are needed for the procedure for monitoring via PCRF for a request for an individual UE: UE IP address and service information (e.g. application identifier or media description or both). + +The following parameters are needed for the procedure for monitoring via PCRF for a request for group of UEs: External Group identifier. + +NOTE: The UE IP address provided by the SCS/AS is assumed to not be NAT'ed from the PDN-GW or GGSN to the SCS/AS at user plane. The UE IP address does not overlap with other UE IP addresses within the operator domain. + +For monitoring for a group of UEs, the SPR is configured with the External Group Identifier the UE belongs to and External Identifier and the SCEF is configured with the list of PCRFs in the operator's domain. The formats of the External Group Identifier and External Identifier are defined in clause 4.6. + +#### 5.6.4.3 Specific Parameters for Monitoring Event: Location Reporting + +This monitoring event allows the SCS/AS to request the Current Location. The supported Accuracy may be at different levels which are described in clause 4.9.2. The Monitoring Event Report delivers the subscriber location and may include a time stamp to indicate when the UE was last-known to be in that location, i.e. if the current location or last-known location is provided. + +NOTE: SCEF can map IP-CAN provided location to the location granularity required by SCS/AS only if it is configured to do so. + +The description below is applicable if SCS/AS request Monitoring Type to "Location Reporting" for a single UE and Location Type is either "current location" or "last known location". + +1. The SCS/AS sets Monitoring Type to "Location Reporting", and adds Location Type in a Monitoring Request to the SCEF as in step 1 of 5.6.4.1. +2. The SCEF executes step 2 of 5.6.4.1. + +3. The SCEF triggers PCRF initiated IP-CAN session modification procedure, including the UE IP address and the Access Network information report request. The PCRF provides the Access Network Information report to the SCEF. +4. Based on operator policies, the SCEF either maps the location information to a geo-location or sends the location information to the SCS/AS. If the time stamp is included indicating that this is the last known location the SCEF indicates in the location type that this is last known location. + +The description below is applicable if SCS/AS request Monitoring Type to "Location Reporting" for a group of UEs and Location Type is either "current location" or "last known location". + +1. The SCS/AS sets Monitoring Type to "Location Reporting", and adds Location Type in a Monitoring Request to the SCEF as in step 1 of 5.6.4.1a. +2. The SCEF executes step 2 of 5.6.4.1a. +3. The SCEF triggers a Monitoring Request (External Group Identifier, Access Network information report request) to the PCRF over Nt interface to each PCRF in the operator's network. +4. Each PCRF executes step 4 of 5.6.4.1a. If a PCRF serves no UEs that are associated with the External Group Identifier, steps 6 and 7 are skipped for that PCRF. +5. The SCEF executes step 5 of 5.6.4.1a. +6. The PCRF executes step 6 of 5.6.4.1a. For those UEs that have an IP-CAN session established, the PCRF initiated IP-CAN session modification procedure, including the Access Network information report request is performed. The PCRF stores the received Access Network Information for each IP-CAN session +7. The PCRF executes step 7 of 5.6.4.1a. The Monitoring Indication includes Access Network Information for each UE. +- 8a. The SCEF executes step 8a of 5.6.4.1a. The response includes location information for each group member UE. Based on operator policies, the SCEF either maps the Access Network Information to a geo-location or sends the Access Network Information to the SCS/AS. If the time stamp is included indicating that this is the last known location the SCEF indicates in the location type that this is last known location. +- 8b. The SCS/AS executes step 8b of 5.6.4.1a. + +#### 5.6.4.4 Specific Parameters for Monitoring Event: Communication Failure + +This monitoring event allows the SCS/AS to be notified of communication failure events, identified by RAN/NAS or TWAN/UWAN Release Cause codes, per TS 23.203 [27]. + +1. The SCS/AS sets Monitoring Type to "Communication Failure" in the Monitoring Request to the SCEF sent as in step 1 of 5.6.4.1. +2. The SCEF executes step 2 of 5.6.4.1. +3. The SCEF triggers PCRF initiated IP-CAN session modification procedure, including the UE IP address and the dynamic session information. The PCRF provisions PCC Rules according to the provided session information. If the PCEF provides either RAN/NAS release code in GPRS/UTRAN/E-UTRAN, TWAN release code in TWAN or Untrusted WLAN release code the PCRF sends it to the SCEF. +4. Based on operation policies the SCEF may normalize the Release code to acceptable values per SLA that the SCS/AS accepts. + +#### 5.6.5 Reporting of Monitoring Events from the PCRF + +The following figure illustrates the procedure to report Monitoring Events via PCRF. This procedure is applicable for reporting both user location information and communication failure for a single UE. This procedure does not apply to group monitoring. It is assumed that PCRF subscribes to Access Network Information report. + +![Sequence diagram illustrating the Reporting event procedure. Lifelines: PCEF, PCRF, SCEF, SCS/AS. Step 1: PCEF initiated IP-CAN session modification or termination procedure in 23.203. Step 2a: SCEF sends Monitoring Indication to SCS/AS. Step 2b: SCS/AS sends Monitoring Indication Response to SCEF.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +``` + +sequenceDiagram + participant PCEF + participant PCRF + participant SCEF + participant SCS/AS + Note over PCEF, PCRF: 1. PCEF initiated IP-CAN session modification or termination procedure in 23.203 + SCEF->>SCS/AS: 2a. Monitoring Indication + SCS/AS-->>SCEF: 2b. Monitoring Indication Response + +``` + +Sequence diagram illustrating the Reporting event procedure. Lifelines: PCEF, PCRF, SCEF, SCS/AS. Step 1: PCEF initiated IP-CAN session modification or termination procedure in 23.203. Step 2a: SCEF sends Monitoring Indication to SCS/AS. Step 2b: SCS/AS sends Monitoring Indication Response to SCEF. + +**Figure 5.6.5-1: Reporting event procedure** + +1. The PCEF reports a monitoring event, either the location reporting stored in MME at Detach or dedicated bearer deactivation or a communication failure at dedicated bearer deactivation to the PCRF using PCEF initiated IP-CAN session modification or termination procedure defined in TS 23.203 [27], then the PCRF to the SCEF over Rx if the event was requested over Rx. Both events terminate the AF session to the SCEF. +- 2a. The SCEF retrieves the TLTRI along with the address of SCS/AS intended for Monitoring Indication message for the associated Rx session. The SCEF sends a Monitoring Indication (TLTRI, UE IP Address, Monitoring Event Report) message to the SCS/AS identified by T8 Destination Address stored in the SCEF. +- 2b. The SCS/AS sends a Monitoring Indication Response (Cause) message to the SCEF. Cause value reflects successful or unsuccessful acknowledgement of Monitoring Indication message. + +## 5.6.6 Monitoring Event configuration and deletion via HSS for roaming scenarios using an IWK-SCEF + +### 5.6.6.1 Configuration Procedure + +Figure 5.6.6.1-1 illustrates the procedure of configuring monitoring events at the HSS or the MME/SGSN. The procedure is common for various Monitoring Event types. The steps and parameters specific to different Monitoring Event types are detailed in clauses 5.6.6.3 to 5.6.6.9. + +The procedure is also used for deleting a previously configured Monitoring Event while configuring a new Monitoring Event between the same SCEF and the same SCS/AS. + +![Sequence diagram for Monitoring event configuration and deletion via HSS procedure. Lifelines: MME/SGSN, IWK-SCEF, HSS, SCEF, SCS/AS. The diagram shows steps 1-5 (clause 5.6.1.1), followed by step 6 (MME/SGSN handling), steps 7-9 (clause 5.6.1.1), step 10 (Inform IWK-SCEF), step 11 (IWK-SCEF handling), step 12 (Authorization from IWK-SCEF), step 13 (MME/SGSN handling), step 14 (Notify Request to HSS), step 15 (Notify Answer from HSS), and step 16 (Notify Report from HSS to SCEF).](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +``` + +sequenceDiagram + participant MME/SGSN + participant IWK-SCEF + participant HSS + participant SCEF + participant SCS/AS + + Note over MME/SGSN, SCS/AS: Step 1 to 5 as specified in clause 5.6.1.1 + Note left of MME/SGSN: 6. MME/SGSN handling + Note over MME/SGSN, SCS/AS: Step 7 to 9 as specified in clause 5.6.1.1 + MME/SGSN-->>IWK-SCEF: 10. Inform IWK-SCEF + Note right of IWK-SCEF: 11. IWK-SCEF handling + IWK-SCEF-->>MME/SGSN: 12. Authorization from IWK-SCEF + Note left of MME/SGSN: 13. MME/SGSN handling + MME/SGSN-->>HSS: 14. Notify Request + HSS-->>MME/SGSN: 15. Notify Answer + HSS-->>SCEF: 16. Notify Report + +``` + +Sequence diagram for Monitoring event configuration and deletion via HSS procedure. Lifelines: MME/SGSN, IWK-SCEF, HSS, SCEF, SCS/AS. The diagram shows steps 1-5 (clause 5.6.1.1), followed by step 6 (MME/SGSN handling), steps 7-9 (clause 5.6.1.1), step 10 (Inform IWK-SCEF), step 11 (IWK-SCEF handling), step 12 (Authorization from IWK-SCEF), step 13 (MME/SGSN handling), step 14 (Notify Request to HSS), step 15 (Notify Answer from HSS), and step 16 (Notify Report from HSS to SCEF). + +**Figure 5.6.6.1-1: Monitoring event configuration and deletion via HSS procedure** + +1-5. Steps of clause 5.6.1.1 are executed. + +6. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF and it is a One-time request and the Monitoring Event is available to the MME/SGSN, then the MME/SGSN collects the Monitoring Event data and includes it as Monitoring Event Report in step 10 so that the IWK-SCEF may perform normalization of Monitoring Event Report(s) according to operator policies, if required. + +7-9. Steps 7-9 of clause 5.6.1.1 are executed. + +10. MME/SGSN may send an Inform IWK-SCEF (Monitoring Type, SCEF ID, SCEF Reference ID, Maximum Number of Reports, Monitoring Duration, SCEF Reference ID for Deletion, Chargeable Party Identifier, Monitoring Event Report) message to the IWK-SCEF. + +11. The IWK-SCEF may authorize the request, e.g. if the Monitoring Type is covered by a roaming agreement and notes the SCEF Reference ID for Deletion if available. If this authorization fails the IWK-SCEF follows step 12 and provides a Cause value indicating the reason for the failure condition to the MME/SGSN. Based on operator policies, the IWK-SCEF may also reject the request due to other reasons (e.g. overload or MME/SGSN has exceeded its quota or rate of submitting monitoring requests defined by an SLA). + +If the request indicates deletion of a Monitoring Event Request, the IWK-SCEF shall perform any final operations necessary, e.g. generation of final charging information, delete any stored parameters, and send an acknowledgement to the MME/SGSN in step 12. + +If the request indicates continuous reporting (new or a modification), the IWK-SCEF may authorize the request and, if authorization is successful, stores the received parameters, sends an acknowledgement to the MME/SGSN in step 12, and starts to watch for the indicated Monitoring Event(s). + +If the request indicates One-time reporting, then the IWK-SCEF may authorize the request and, if authorization is successful, may perform normalization of the data according to operator policies, and sends an acknowledgement to the MME/SGSN in step 12 that contains any such normalized data. + +If the request included Monitoring Event Data then the IWK-SCEF may perform normalization of the data according to operator policies. + +12. If the authorization is successful, the IWK-SCEF sends an Authorization from IWK-SCEF (Cause, Monitoring Event Report) message to MME/SGSN. + +The Monitoring Event Report is included if it was a One-time request, the MME/SGSN provided the Monitoring Event Report in the Inform IWK-SCEF message and the IWK-SCEF is not reporting directly to the SCEF as described clause 5.6.8.1 step 2c. + +13. The MME/SGSN may verify the request, e.g. if the Monitoring Type is covered by a roaming agreement when the request is from another PLMN or whether it serves the SCEF Reference ID for Deletion and can delete it. If this check fails the MME/SGSN follows step 14 and provides a Cause value indicating the reason for the failure condition to the SCEF. Based on operator policies, the MME/SGSN may also reject the request due to other reasons (e.g. overload or HSS has exceeded its quota or rate of submitting monitoring requests defined by an SLA). + +The MME/SGSN starts to watch for the indicated Monitoring Event unless it is a One-time request and the Monitoring Event is available to the MME/SGSN at the time of sending Insert Subscriber Data Answer. The MME/SGSN deletes the monitoring configuration identified by the SCEF Reference ID for Deletion, if provided. + +NOTE 2: The MME/SGSN will transfer the parameters stored for every monitoring task as part of its context information during an MME/SGSN change. + +14. If the monitoring event configuration status received from IWK-SCEF is different than the result reported to the HSS in Step 7, the MME/SGSN shall send the Notify Request to the HSS to inform the monitoring event configuration status received from IWK-SCEF. +15. The HSS send the Notify Answer to the MME/SGSN. +16. If the HSS receives in step 14 the monitoring event configuration status from the MME/SGSN, the HSS shall notify the SCEF that the configured Monitoring Event is cancelled for the individual UE for those monitoring event configurations for which the status received from the MME/SGSN is marked as not accepted. The HSS shall subsequently locally delete the Monitoring Event for the individual UE and for the individual group member UE if the Monitoring Event is configured in the HSS, and steps 1-5 of clause 5.6.9 are executed. + +#### 5.6.6.2 Void + +#### 5.6.6.3 Specific Parameters for Monitoring Event: Loss of connectivity + +The description in clause 5.6.1.3 applies with the following clarifications. + +- 1-5. Steps 1-5 of clause 5.6.1.3 are executed. +6. The MME/SGSN executes step 6 of clause 5.6.1.3, but if the values proposed by HSS is not acceptable to the MME/SGSN the MME/SGSN rejects the request and includes acceptable values in the reject message. +- 7-9. Steps 7-9 of clause 5.6.1.3 are executed. + +#### 5.6.6.4 Specific Parameters for Monitoring Event: UE reachability + +The description in clause 5.6.1.4 applies with the following clarifications. + +- 1-5. Steps 1-5 of clause 5.6.1.4 are executed. +6. The MME/SGSN executes step 6 of clause 5.6.1.4, but if the values proposed by HSS is not acceptable to the MME/SGSN the MME/SGSN rejects the request and includes acceptable values in the reject message. + +- 7-9. Steps 7-9 of clause 5.6.1.4 are executed. + +#### 5.6.6.5 Specific Parameters for Monitoring Event: Location Reporting + +The description in clause 5.6.1.5 applies with the following clarifications. + +- 1-2. Steps 1-2 of clause 5.6.1.5 are executed. +3. If Accuracy is included in step 1 then based on operator configuration the SCEF may map it to permissible granularity at different levels, which are described in clause 4.9.2. If Accuracy is not included in step 1, the SCEF sets the granularity based on operator configuration. The SCEF adds Location Type and Accuracy prior to sending the Monitoring Request to the HSS as in step 3 of clause 5.6.1.5. +- 4-5. Steps 4-5 clause 5.6.1.5 are executed. +6. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF and it is a One-time request, the MME/SGSN starts watching for cell/RA/TA/eNodeB changes, depending on requested Accuracy, and includes the location information as part of the Monitoring Event Data to the IWK-SCEF in step 7. +7. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF, then the MME/SGSN shall execute the step 7 in clause 5.6.6.1. +8. The IWK-SCEF executes step 8 in clause 5.6.6.1, and if the request included Monitoring Event Data then the IWK-SCEF may perform normalization of the data according to operator policies. +9. The IWK-SCEF executes step 9 in clause 5.6.6.1. +10. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF, then the MME/SGSN either starts to watch for the indicated Monitoring Event, or if the IWK-SCEF rejected the request the MME/SGSN rejects the request with the cause provided by the IWK-SCEF. + +If the MME/SGSN is not configured to use an IWK-SCEF for the PLMN of the SCEF, then the MME/SGSN executes step 6 of clause 5.6.1.1 and in addition perform any actions required e.g. generating charging/accounting information. + +- 11-13. Steps 7-9 of clause 5.6.1.1 are executed and include the report of the current or last known location, depending on what was requested. The SCEF, if not already done by the IWK-SCEF, maps eNodeB-ID/cell-ID/RAI/TAI to geo-location before reporting to the SCS/AS. + +#### 5.6.6.6 Specific Parameters for Monitoring Event: Change of IMSI-IMEI(SV) Association + +The description in clause 5.6.1.6 applies as there are no VPLMN changes. + +#### 5.6.6.7 Specific Parameters for Monitoring Event: Roaming Status + +The description in clause 5.6.1.6 applies as there are no VPLMN changes. + +#### 5.6.6.8 Specific Parameters for Monitoring Event: Communication failure + +The description in clause 5.6.1.8 applies with the following clarifications. + +1. The SCS/AS sets Monitoring Type to "Communication Failure" prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.8. +2. The SCEF executes step 2 of clause 5.6.1.8. +3. The SCEF executes step 3 of clause 5.6.1.8. +4. The HSS executes step 4 of clause 5.6.1.8. +5. The HSS executes step 5 of clause 5.6.1.8. +6. Not applicable. + +7. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF, the MME/SGSN executes step 7 of 5.6.6.1. +8. The IWK-SCEF executes step 8 of clause 5.6.6.1. +9. The IWK-SCEF executes step 9 of clause 5.6.6.1. +10. The MME/SGSN executes step 6 of clause 5.6.1.8 and starts watching for communication failure events. +- 11-13. Steps 7-9 of clause 5.6.1.8 are executed. + +#### 5.6.6.9 Specific Parameters for Monitoring Event: Availability after DDN Failure + +The description in clause 5.6.1.5 applies with the following clarifications. + +- 1-5. Steps 1-5 are executed according to clause 5.6.6.9. +6. Not applicable. +7. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF, the MME/SGSN executes step 7 of 5.6.6.1. +8. The IWK-SCEF executes step 8 of clause 5.6.6.1. +9. The IWK-SCEF executes step 9 of clause 5.6.6.1. +10. The MME/SGSN executes step 6 of clause 5.6.1.9. +- 11-13. Steps 7-9 of clause 5.6.1.9 are executed. + +### 5.6.7 Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios + +In this Release there is no support for Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios. + +### 5.6.8 Reporting of Monitoring Events from the HSS or the MME/SGSN for roaming scenarios + +#### 5.6.8.1 Reporting Procedure + +The following figure illustrates the common procedure flow of reporting Monitoring Events that are detected by the MME/SGSN or HSS for roaming scenarios. The steps specific to different Monitoring Event types are detailed in clauses 5.6.8.2 to 5.6.8.8. + +![Sequence diagram illustrating the monitoring event reporting procedure for roaming scenarios. The diagram shows five lifelines: MME/SGSN, IWK-SCEF, HSS, SCEF, and Monitoring Destination node. The sequence of messages is: 1a. Event Detection (MME/SGSN), 1b. Event Detection (HSS), 2a. Monitoring Indication (MME/SGSN to SCEF), 2b. Monitoring Indication (HSS to SCEF), 2c. Monitoring Indication (MME/SGSN to IWK-SCEF), 2c. Monitoring Indication (IWK-SCEF to SCEF), 3a. Monitoring Indication (SCEF to Monitoring Destination node), and 3b. Monitoring Indication Response (Monitoring Destination node to SCEF).](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant MME/SGSN + participant IWK-SCEF + participant HSS + participant SCEF + participant MDN as Monitoring Destination node + + Note left of MME/SGSN: 1a. Event Detection + Note right of HSS: 1b. Event Detection + MME/SGSN->>SCEF: 2a. Monitoring Indication + HSS->>SCEF: 2b. Monitoring Indication + MME/SGSN->>IWK-SCEF: 2c. Monitoring Indication + IWK-SCEF->>SCEF: 2c. Monitoring Indication + SCEF->>MDN: 3a. Monitoring Indication + MDN-->>SCEF: 3b. Monitoring Indication Response + +``` + +Sequence diagram illustrating the monitoring event reporting procedure for roaming scenarios. The diagram shows five lifelines: MME/SGSN, IWK-SCEF, HSS, SCEF, and Monitoring Destination node. The sequence of messages is: 1a. Event Detection (MME/SGSN), 1b. Event Detection (HSS), 2a. Monitoring Indication (MME/SGSN to SCEF), 2b. Monitoring Indication (HSS to SCEF), 2c. Monitoring Indication (MME/SGSN to IWK-SCEF), 2c. Monitoring Indication (IWK-SCEF to SCEF), 3a. Monitoring Indication (SCEF to Monitoring Destination node), and 3b. Monitoring Indication Response (Monitoring Destination node to SCEF). + +**Figure 5.6.8.1-1: Monitoring event reporting procedure for roaming scenarios** + +- 1a. A Monitoring Event is detected by the MME/SGSN at which the Monitoring Event is configured. +- 1b. Either a Monitoring Event is detected by the HSS, or the HSS needs to inform the SCEF about the change of status (suspend/resume/cancel) of an ongoing monitoring if an event related with the change of monitoring support at the serving node, (e.g. lack of monitoring support in MME/SGSN or revocation of monitoring authorization) is detected in the HSS. +- 2a. If the MME/SGSN is not configured to use an IWK-SCEF for the PLMN of the SCEF then the MME/SGSN executes step 2a in clause 5.6.3.1. The MME/SGSN in addition generates any required charging/accounting information. +- 2b. The HSS executes step 2b in clause 5.6.3.1. +- 2c. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF, then the MME/SGSN sends a Monitoring Indication (SCEF Reference ID(s), Monitoring Event Report, User Identity) message to the IWK-SCEF. If the Monitoring Event configuration was triggered by a One-time Monitoring Request, then the Monitoring Event configuration is deleted by the MME/SGSN upon completion of this step. If the MME/SGSN has a Maximum Number of Reports stored for this monitoring task, the MME/SGSN shall decrease its value by one. When the Monitoring Duration expires for a continuous Monitoring Request in the HSS, the MME/SGSN or the SCEF, then each of these nodes shall locally delete the related Monitoring Event configuration associated with the individual UE or group member UE. So that the SCEF can determine what groups the report pertains to, multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication. + The IWK-SCEF sends a Monitoring Indication (SCEF Reference ID(s), Monitoring Event Report, User Identity) message to the SCEF. If the IWK-SCEF has a Maximum Number of Reports stored for this monitoring task, the IWK-SCEF shall decrease its value by one. When the maximum number of reports is reached for a Continuous Monitoring Request or in the case of a One-time Monitoring Request, the IWK-SCEF ends the reporting on the SCEF Reference ID. So that the SCEF can determine what groups the report pertains to, multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication. +3. The SCEF executes step 3 in clause 5.6.3.1. + +When the Monitoring Duration expires for a continuous Monitoring Request in the HSS, the MME/SGSN, the IWK-SCEF (if it is used in the visited PLMN) or the SCEF, then each of these nodes shall locally delete the related Monitoring Event configuration associated with the individual UE or group member UE. + +### 5.6.8.2 Reporting Event: Loss of connectivity + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the mobile reachability timer expires, when an active UE is purged (see TS 29.272 [31]), when ISR is disabled and a UE, MME, SGSN, or HSS initiated detach occurs (see TS 23.401 [7], TS 23.060 [6]), or when ISR is enabled and a UE, MME, SGSN, or HSS initiated detach occurs and the MME or SGSN sends a Detach Notification message to the SGSN or MME with a Cause value that indicates complete, see (TS 23.401 [7]). +2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. +3. Step 3 of clause 5.6.8.1 is executed. + +### 5.6.8.3 Reporting Event: UE reachability + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the UE changes to connected mode or when the UE will become reachable for paging (for a UE using extended idle mode DRX). + +If Maximum Response Time was included in step 5 of clause 5.6.6.4, then the MME/SGSN keeps the corresponding S1-U/Iu-PS connections of the UE for a duration of at least the Maximum Response Time less the UE's PSM Active Timer value. If the UE uses extended idle mode DRX, the MME/SGSN takes the Maximum Response Time into account to determine when to report this monitoring event before the next Paging Occasion occurs. + +2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. The Monitoring Event Report indicates if the event was caused by the UE changing to connected mode or by the UE becoming reachable for paging. +3. Step 3 of clause 5.6.8.1 is executed. + +### 5.6.8.4 Reporting Event: Location Reporting + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the MME/SGSN detects that the UE changes location with the granularity as requested by the monitoring event configuration. +2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. If step 2c is executed, then the IWK-SCEF maps the reported 3GPP system specific location information to a geo-location and forwards it to the SCEF. +3. Step 3 of clause 5.6.8.1 is executed. The SCEF may map the reported 3GPP system specific location information to a geo-location and reports it. + +### 5.6.8.5 Reporting Event: Change of IMSI-IMEI(SV) association + +This monitoring event is executed as in clause 5.6.3.5. + +### 5.6.8.6 Reporting Event: Roaming Status + +This monitoring event is executed as in clause 5.6.3.6. + +### 5.6.8.7 Reporting Event: Communication failure + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the MME/SGSN becomes aware of a RAN or NAS failure event. +2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. If step 2c is executed, then the IWK-SCEF either forwards the received failure cause code(s) as-is or an abstracted value to the SCEF. +3. Step 3 of clause 5.6.8.1 is executed. Based on operator configuration, the SCEF reports either the received failure cause code(s) as-is or an abstracted value. + +### 5.6.8.8 Reporting Event: Availability after DDN failure + +- 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the MME/SGSN becomes aware of UE availability after DDN failure. +2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. +3. Step 3 of clause 5.6.8.1 is executed. + +### 5.6.8.9 Reporting Event: PDN Connectivity Status + +This monitoring event executes as in clause 5.6.3.9. + +## 5.6.9 Network-initiated Explicit Monitoring Event Deletion Procedure + +The procedure is used by the SCEF towards the SCS/AS to delete a previously configured Monitoring Event. + +![Sequence diagram of the Network-initiated Explicit Monitoring Event Deletion Procedure. The diagram shows four lifelines: MME/SGSN, HSS/HLR, SCEF, and SCS/AS. The process starts with a successful monitoring event configuration (step 0). The HSS/HLR sends a Monitoring Response or Monitoring Indication (step 1) to the SCEF. The SCEF performs a Context Lookup (step 2). The SCEF sends a Cancel Monitoring Event Request (step 3) to the SCS/AS. The SCS/AS sends a Cancel Monitoring Event Response (step 4) to the SCEF. Finally, the SCEF performs a Context Cleanup (step 5). A dashed arrow labeled 1b indicates that the HSS/HLR also sends an Insert Subscriber Data message to the MME/SGSN.](f92e919c70b7adda2d0e778889f44fae_img.jpg) + +``` + +sequenceDiagram + participant MME/SGSN + participant HSS/HLR + participant SCEF + participant SCS/AS + + Note over all: 0. Monitoring Event Configuration successful + + HSS/HLR->>SCEF: 1. Monitoring Response or Monitoring Indication + Note right of SCEF: 2. Context Lookup + SCEF->>SCS/AS: 3. Cancel Monitoring Event Request + SCS/AS->>SCEF: 4. Cancel Monitoring Event Response + Note right of SCEF: 5. Context Cleanup + + HSS/HLR-->>MME/SGSN: 1b. Insert Subscriber Data + +``` + +Sequence diagram of the Network-initiated Explicit Monitoring Event Deletion Procedure. The diagram shows four lifelines: MME/SGSN, HSS/HLR, SCEF, and SCS/AS. The process starts with a successful monitoring event configuration (step 0). The HSS/HLR sends a Monitoring Response or Monitoring Indication (step 1) to the SCEF. The SCEF performs a Context Lookup (step 2). The SCEF sends a Cancel Monitoring Event Request (step 3) to the SCS/AS. The SCS/AS sends a Cancel Monitoring Event Response (step 4) to the SCEF. Finally, the SCEF performs a Context Cleanup (step 5). A dashed arrow labeled 1b indicates that the HSS/HLR also sends an Insert Subscriber Data message to the MME/SGSN. + +**Figure 6.5.9-1: Network-initiated Explicit Monitoring Event Deletion Procedure** + +0. A Monitoring Event configuration procedure according to clause 5.6.1 or clause 5.6.6 has already executed successfully. +1. The HSS returns a Monitoring Response message or triggers a Monitoring Indication message towards the SCEF and includes SCEF Reference ID of a previously accepted Monitoring Event which needs cancellation due to certain conditions such as: + - For a single UE or a sub-set of UEs in a group for which there is an active monitoring event configuration, the monitoring event configuration is no longer valid (e.g. the previously subscribed periodic RAU/TAU Timer from one SCS/AS is being overwritten by another SCS/AS and the Enhanced Multiple Event Monitoring is not supported); or + - For group based processing, if a given External Group ID for which a previous group request was accepted is now no longer valid; or + - For group based processing, for UEs belonging to a group for which there is an active group based event configuration, the UE's subscription is deleted from the HSS or the UE's event monitoring is cancelled. +- 1b. The HSS also deletes the previously configured Monitoring Event in the MME/SGSN, if applicable, e.g. at deletion of an External Group ID in the HSS. +2. Based on the SCEF Reference ID for cancellation included in step 1a or local context lookup in step 1b, the SCEF determines TLTRI of the configured Monitoring Event which needs cancellation. + +3. The SCEF sends a Cancel Monitoring Event Request (TLTRI, Cause) message to the T8 Destination Address. Cause value indicates the reason for cancellation of the previously configured Monitoring Event. If SCEF receives MSISDN(s) or External Identifier(s) in step 1 for group based processing and the Maximum Number of Reports applies to the monitoring event configuration, the SCEF sets the stored number of reports of the indicated UE(s) to Maximum Number of Reports and includes such UE identifier(s) in the Cancel Monitoring Event Request to the SCS/AS. If SCEF determines that the reporting for the group is complete based on the update above, the SCEF deletes the associated Monitoring Event configuration and request the HSS to delete the related monitoring event configuration for the group. +4. The SCS/AS sends a Cancel Monitoring Event Response (Cause) message to the SCEF. Cause indicates the result of the procedure. For single UE configuration, the SCS/AS deletes T8 context associated with the TLTRI received in step 3; for group based configuration, the SCS/AS deletes T8 context associated with the TLTRI received in step 3 when the event monitoring of the last UE in the group is cancelled. +5. The SCEF deletes T8 context and the SCEF EPS Bearer context associated with the TLTRI sent in step 3. + +## 5.7 High latency communications procedures + +### 5.7.1 Availability Notification after DDN Failure + +#### 5.7.1.1 General + +In this feature, the AS subscribes once and then gets notification only when there has been some data delivery failure followed by the UE becoming reachable. + +This feature involves an entry in the subscription for a UE for "network application triggering when the UE is available after a DDN failure". This is a different monitoring event from the "UE is reachable" monitoring event. This information is provided to the serving node (MME/SGSN) at registration. The serving node notes this and sets a Notify-on-available-after-DDN-failure flag after a DDN failure. If the flag is set when the UE next contacts the network, the serving node notifies the SCEF that the UE is reachable, and will clear the flag. + +An important use case for this feature is the application that wants to communicate with a UE that sleeps for a long time. If downlink packets from the application are not delivered, the application recognizes that the UE is not available by lack of response within a reasonable time from the UE, and then await notification from the network (i.e. from the MME/S4-SGSN via the SCEF) of UE reachability. This procedure does not apply to a Gn/Gp-SGSN. + +NOTE: The solution is particularly suitable when there is just one SCS/AS. + +#### 5.7.1.2 Event Configuration + +The figure 5.7.1.2-1 below provides the Event configuration procedure. + +![Sequence diagram for Event Configuration - Availability Notification after DDN Failure. Lifelines: UE, MME/S4-SGSN, HSS, SCEF, SCS/AS. The sequence shows the SCS/AS sending a Trigger Request to the SCEF, the SCEF sending a Monitoring Request to the HSS, the HSS providing the request to the MME/S4-SGSN (steps 5-7 in Figure 5.6.1.1-1), the HSS sending a Monitoring Response to the SCEF, and the SCEF sending a Trigger Response to the SCS/AS.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` +sequenceDiagram + participant UE + participant MME/S4-SGSN + participant HSS + participant SCEF + participant SCS/AS + Note right of SCEF: 1. Trigger Request ("notify on available after delivery failure", UEID) + SCEF->>HSS: 2. Monitoring Request ("notify on available after DDN failure", UEID) + Note left of HSS: 3. The HSS provides the monitoring event request to the MME/S4-SGSN per steps 5-7 in Figure 5.6.1.1-1. + HSS->>SCEF: 4. Monitoring Response + SCEF->>SCS/AS: 5. Trigger Response +``` + +Sequence diagram for Event Configuration - Availability Notification after DDN Failure. Lifelines: UE, MME/S4-SGSN, HSS, SCEF, SCS/AS. The sequence shows the SCS/AS sending a Trigger Request to the SCEF, the SCEF sending a Monitoring Request to the HSS, the HSS providing the request to the MME/S4-SGSN (steps 5-7 in Figure 5.6.1.1-1), the HSS sending a Monitoring Response to the SCEF, and the SCEF sending a Trigger Response to the SCS/AS. + +**Figure 5.7.1.2-1: Event Configuration - Availability Notification after DDN Failure** + +1. The SCS/AS executes step 1 of clause 5.6.1.9. + 2. The SCEF sends a Monitoring Request message to the HSS to request notification when the UE becomes available after a DDN failure. +- NOTE: The Monitoring Request message includes the parameters specified in clause 5.6.1.2. +3. The HSS provides the monitoring event request to the MME/SGSN according to steps 5-7 in Figure 5.6.1.1-1. + 4. The HSS internally notes the request, and sends Monitoring Response message to the SCEF. + 5. The SCEF executes step 9 of clause 5.6.1.9. + +### 5.7.1.3 Notification + +The figure 5.7.1.3-1 below provides the notification procedure. This figure is relative to EUTRAN, but the equivalent figure for UTRAN can be directly derived from this. + +![Sequence diagram illustrating the Notification - Availability Notification after DDN Failure process. The diagram shows interactions between UE, EUTRAN, MME, PGW/SGW, HSS, SCEF, and SCS/AS. The process starts with downlink data from SCS/AS to PGW/SGW, followed by a DDN to MME. A DDN failure occurs (step 3), leading to a DDN Failure message from MME to PGW/SGW (step 4). The MME sets a Notify-on-available-after-DDN-failure flag (step 5). Later, the UE contacts the network (step 6), and the MME notes the flag is set and resets it (step 7). The MME sends a Monitoring Indication to SCEF (step 8), which then notifies the SCS/AS (step 9). The application sends data (step 10), and the UE transitions to idle mode (step 11). The MME sends another Monitoring Indication to SCEF (step 12), which triggers Step 3 of 5.6.3.8 (step 13), allowing the application to send data (step 14).](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant PGW/SGW + participant MME + participant EUTRAN + participant UE + participant HSS + participant SCEF + + Note right of SCS/AS: 1. Downlink data + SCS/AS->>PGW/SGW: Downlink data + PGW/SGW->>MME: 2. DDN + Note left of MME: 3. DDN failure e.g. no response from the UE, or UE in PSM or eDRX + MME->>PGW/SGW: 4. DDN Failure + Note right of MME: 5. MME sets a Notify-on-available-after-DDN-failure flag + Note left of EUTRAN: 6. UE contacts the network, or becomes reachable + Note right of MME: 7. MME notes that the Notify-on-available-after-DDN-failure flag is set and resets that flag. + MME->>SCEF: 8. Monitoring Indication (UE ID) + SCEF->>SCS/AS: 9. UE available + Note left of SCS/AS: 10. Application sends data + SCS/AS->>PGW/SGW: Application sends data + Note left of EUTRAN: 11. UE transitions to idle mode + MME->>SCEF: 12. Monitoring Indication (UE ID, ...) + Note right of SCEF: 13. Step 3 of 5.6.3.8 + Note right of SCEF: 14. Application may send data + SCEF->>SCS/AS: Step 3 of 5.6.3.8 + +``` + +Sequence diagram illustrating the Notification - Availability Notification after DDN Failure process. The diagram shows interactions between UE, EUTRAN, MME, PGW/SGW, HSS, SCEF, and SCS/AS. The process starts with downlink data from SCS/AS to PGW/SGW, followed by a DDN to MME. A DDN failure occurs (step 3), leading to a DDN Failure message from MME to PGW/SGW (step 4). The MME sets a Notify-on-available-after-DDN-failure flag (step 5). Later, the UE contacts the network (step 6), and the MME notes the flag is set and resets it (step 7). The MME sends a Monitoring Indication to SCEF (step 8), which then notifies the SCS/AS (step 9). The application sends data (step 10), and the UE transitions to idle mode (step 11). The MME sends another Monitoring Indication to SCEF (step 12), which triggers Step 3 of 5.6.3.8 (step 13), allowing the application to send data (step 14). + +**Figure 5.7.1.3-1: Notification - Availability Notification after DDN Failure** + +1. The application sends downlink data. +2. The PGW forwards the data to the SGW. The SGW sends a Downlink Data Notification (DDN) message to the MME requesting that UE be paged. +3. The UE is in Power Saving Mode or Extended idle mode DRX, or the MME initiates paging for the UE but receives no response. +4. The MME sends a DDN failure indication to the SGW. +5. The MME notes the subscription option for notification of availability after DDN failure for the UE, and sets a Notify-on-available-after-DDN-failure flag. Not every DDN failure triggers this event. This event may be triggered only when the UE is in PSM or Extended idle mode DRX. +6. At some later time, the UE contacts the network (e.g. to perform a TAU, or a service request), or the UE becomes or is about to become reachable for paging (e.g. an eDRX Paging Transmission Window is reached). +7. The MME notes that UE is available and that the Notify-on-available-after-DDN-failure flag for the UE is set. +8. The MME sends a Monitoring Indication to the SCEF that the UE is available, according to clause 5.6.3.1. The MME also resets the Notify-on-available-after-DDN-failure flag for the UE. +9. The SCEF notifies the application that the UE is available. + +10. The application may decide to resend data it has for the UE. +11. UE transitions to idle mode according to TS 23.401 [7], e.g. CM-IDLE with PSM or eDRX. +12. If Idle Status Indication was requested during Monitoring Event configuration, and the MME/SGSN supports Idle Status Indication, then MME executes step 2a of clause 5.6.3.8, and includes the time at which the UE transitioned into idle mode, its granted active time (if PSM is enabled), the periodic TAU/RAU timer granted to the UE by the MME, the eDRX cycle length (if extended idle mode DRX is enabled), and the Suggested number of downlink packets if a value was provided to the S-GW in the message. +13. The SCEF executes step 3 of clause 5.6.3.8, and includes additional parameters specified in step 12 above. +14. The application may send queued data toward the UE. + +## 5.7.2 Notification using Monitoring Event "UE Reachability" + +If an SCS/AS wants to send downlink packet(s), the SCS/AS can request a One-time "UE Reachability" monitoring event by sending Monitoring Request message indicating Reachability Type as "Reachability for Data". The SCS/AS may send the packet data when it receives a notification that the UE has changed to connected mode or the SCS/AS may send a device trigger when it receives a notification that the UE will become reachable for paging. If the SCS/AS optionally wants to fine-tune the delivery of the downlink data within the time-window when the UE is reachable, the SCS/AS can configure optional parameter 'Maximum Response Time' with proper value, and/or request Idle Status Indication (as detailed in clause 5.6.1.4). + +## 5.8 Procedure for Informing about Potential Network Issues + +### 5.8.1 General + +This clause contains the detailed description and the procedures for the service capability exposure feature Informing about Potential Network Issues. + +An SCS/AS may request for being notified about the network status. The following methods are supported: + +- The SCS/AS requests to be informed, one-time, about the network status by providing a geographical area. This procedure is referred to as one-time network status request; +- The SCS/AS requests to be informed, continuously, about the network status by providing a geographical area. This procedure is referred to as continuous network status request. + +The procedures described in this clause use the RAN Congestion Awareness Function (RCAF) and corresponding features as defined in TS 23.401 [7] and TS 23.060 [6]. The SCEF communicates with the RCAF via the Ns reference point. + +After receiving the request for network status notification from the SCS/AS, the SCEF derives the RCAF(s) responsible for the indicated geographical area, and requests congestion reporting from these RCAF(s). + +NOTE 1: The SCEF needs to know the RCAF(s) available in the operator network or the network of the RAN operator in the case of RAN sharing. For every RCAF, the SCEF needs to be configured with the RCAF address and the geographical area the RCAF is responsible for. The Ns reference point does not support roaming. + +The RCAF reports to the SCEF the following information from the RUCI (see TS 23.203 [27]) for every cell or eNodeB belonging to the indicated geographical area: + +- Congestion level or an indication of the "no congestion" state; +- ECGI, or eNodeB-ID, or SAI for which the congestion level is being provided. + +Based on the congestion information the SCEF receives from the identified RCAF(s), the SCEF derives and reports the network status for the geographical area as Network Status Indication (NSI) to the SCS/AS. When reporting to the SCS/AS, the NSI shall not include any 3GPP location information. + +NOTE 2: Either exact values for congestion status, as reported by RCAF(s) to SCEF or abstracted values e.g. (High, Medium, Low) can be reported by the SCEF to the SCS/AS. The calculation and the reporting of the NSI to the SCS/AS depends on operator configuration (SLAs, network topology, usage etc.). + +When an SCS/AS requests One-time Network Status from the SCEF, the SCEF can optionally provide a time interval at which the SCS/AS is allowed to re-issue the same request for network status. + +NOTE 4: The time interval provided by SCEF can be ignored by the SCS/AS if the subsequent request on network status is considerably different wrt. the geographical area. + +The request procedure for one-time or continuous reporting of network status is described in clause 5.8.2 and the report procedure for continuous reporting of network status in clause 5.8.3. Clause 5.8.4 contains the removal procedure for the continuous reporting of network status. + +## 5.8.2 Request procedure for one-time or continuous reporting of network status + +This procedure is used by an SCS/AS to retrieve Network Status Information (NSI) from the network. This procedure can be used to request a one-time or continuous reporting of network status. Figure 5.8.2-1 illustrates the procedure. + +![Sequence diagram illustrating the request procedure for one-time or continuous reporting of network status. The diagram shows interactions between RCAF, SCEF, and SCS/AS. The steps are: 1. SCS/AS sends a Network Status Request (geographic area) to SCEF; 2. SCEF performs Authorization; 3. SCEF sends an Aggregated Congestion Request (SCEF ID, location) to RCAF; 4. RCAF sends an Aggregated Congestion Report (SCEF ID, congestion status list) to SCEF; 5. SCEF performs 'Derive NSI'; 6. SCEF sends a Network Status Report (NSI) to SCS/AS; 7. SCS/AS sends a Network Status Acknowledgement to SCEF.](6116b1a533010c170fc526ec513ba0b8_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant RCAF + Note right of SCEF: 2a. Authorization + Note right of SCEF: 5. Derive NSI + SCS/AS->>SCEF: 1a. Network Status Request (geographic area) + SCEF->>SCS/AS: 2b. Network Status Response + SCEF->>RCAF: 3. Aggregated Congestion Request (SCEF ID, location) + RCAF->>SCEF: 4. Aggregated Congestion Report (SCEF ID, congestion status list) + SCEF->>SCS/AS: 6. Network Status Report (NSI) + SCS/AS->>SCEF: 7. Network Status Acknowledgement + +``` + +Sequence diagram illustrating the request procedure for one-time or continuous reporting of network status. The diagram shows interactions between RCAF, SCEF, and SCS/AS. The steps are: 1. SCS/AS sends a Network Status Request (geographic area) to SCEF; 2. SCEF performs Authorization; 3. SCEF sends an Aggregated Congestion Request (SCEF ID, location) to RCAF; 4. RCAF sends an Aggregated Congestion Report (SCEF ID, congestion status list) to SCEF; 5. SCEF performs 'Derive NSI'; 6. SCEF sends a Network Status Report (NSI) to SCS/AS; 7. SCS/AS sends a Network Status Acknowledgement to SCEF. + +**Figure 5.8.2-1: Request procedure for one-time or continuous reporting of network status** + +1. When the SCS/AS needs to retrieve NSI, the SCS/AS sends a Network Status Request (Geographical area, SCS/AS Identifier, Duration, Threshold) message to the SCEF. Duration indicates the time for which a continuous reporting is requested. The absence of Duration indicates a one-time reporting. Threshold indicates a range at which the SCS/AS wishes to be informed of the network status. Multiple Threshold values may be included. The SCEF assigns a TLTRI that identifies the Network Status Request. + +NOTE 1: Geographical area specified by SCS/AS could be at cell level (CGI/ECGI), TA/RA level or other formats e.g. shapes (e.g. polygons, circles etc.) or civic addresses (e.g. streets, districts etc.) as referenced by OMA Presence API [32]. + +- 2a. The SCEF authorizes the SCS/AS request for notifications about potential network issues. The SCEF stores SCS/AS Address, TLTRI, Duration, if present, and Threshold, if present. The SCEF assigns an SCEF Reference ID. + +- 2b. The SCEF sends a Network Status Response (TLTRI, cause). The cause value indicates that the network has accepted the request in step 1. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the SCS/AS has exceeded its quota or rate of submitting requests, the cause value indicates the error and the flow stops at this step. + 3. The SCEF assigns an SCEF Reference ID and identifies, based on local configuration (as described in clause 5.8.1), the RCAF(s) responsible for the provided Geographical Area. For every identified RCAF, the SCEF derives a Location Area from the Geographical Area provided by the SCS/AS. The Location Area is according to operator configuration either a 3GPP location area (e.g. list of TA/RAs, list of cell(s), list of eNodeBs, etc.) or a sub-area of the Geographical Area provided by the SCS/AS. The SCEF sends an Aggregated Congestion Request (SCEF Reference ID, Location Area, Duration, Threshold) message to the identified RCAF(s). Duration indicates the time for which a continuous reporting is requested. The absence of Duration indicates a one-time reporting. The SCEF, based on operator policies, may choose a different Threshold value than the one indicated by the SCS/AS in step 1. + 4. The RCAF examines the Aggregated Congestion Request message. If the SCEF provided a Duration, the RCAF stores the SCEF instructions and starts to monitor the set of cells or eNodeBs belonging to the Location Area for a change in the congestion status that is crossing a Threshold (if provided by the SCEF). The RCAF sends an Aggregated Congestion Report to the SCEF including the SCEF Reference ID and, depending on the operator configuration and current RCAF knowledge, the congestion status for every cell or eNodeB belonging to the Location Area requested by the SCEF. + 5. The SCEF verifies whether the Network Status Request identified via the SCEF Reference ID is valid and active and stores the report. After receiving reports from all the involved RCAF(s) to which step 3 was executed, the SCEF derives the NSI for the requested Geographical Area by combining all reports with the same SCEF Reference ID in an operator configurable way (governed by SLAs, network topology, usage, etc.). +- NOTE 2: Either exact values for congestion status, as reported by RCAF(s) to SCEF or abstracted values e.g. (High, Medium, Low) can be reported by the SCEF to the SCS/AS. The calculation and the reporting of the NSI to the SCS/AS depends on operator configuration (SLAs, network topology, usage, etc.). +6. The SCEF sends a Network Status Report (TLTRI, NSI) message to the SCS/AS. + 7. The SCS/AS sends a Network Status Acknowledgement to the SCEF. + +### 5.8.3 Report procedure for continuous reporting of network status + +This procedure is used by the SCEF to report a change of Network Status Information (NSI) to the SCS/AS which requested a continuous reporting of network status. Figure 5.8.3-1 illustrates the procedure. + +![Sequence diagram illustrating the report procedure for continuous reporting of network status. The diagram shows three participants: RCAF, SCEF, and SCS/AS. The sequence of messages is: 1. RCAF sends an Aggregated Congestion Report (SCEF ID, congestion status list) to SCEF. 2. SCEF sends an Acknowledgement back to RCAF. 3. SCEF performs an internal step 'Derive NSI'. 4. SCEF sends a Network Status Report (NSI) to SCS/AS. 5. SCS/AS sends a Network Status Acknowledgement back to SCEF.](f2486d5031b55e42b300903a716b0a00_img.jpg) + +``` + +sequenceDiagram + participant RCAF + participant SCEF + participant SCS/AS + Note right of SCEF: 3. Derive NSI + RCAF->>SCEF: 1. Aggregated Congestion Report (SCEF ID, congestion status list) + SCEF-->>RCAF: 2. Acknowledgement + SCEF->>SCS/AS: 4. Network Status Report (NSI) + SCS/AS-->>SCEF: 5. Network Status Acknowledgement + +``` + +Sequence diagram illustrating the report procedure for continuous reporting of network status. The diagram shows three participants: RCAF, SCEF, and SCS/AS. The sequence of messages is: 1. RCAF sends an Aggregated Congestion Report (SCEF ID, congestion status list) to SCEF. 2. SCEF sends an Acknowledgement back to RCAF. 3. SCEF performs an internal step 'Derive NSI'. 4. SCEF sends a Network Status Report (NSI) to SCS/AS. 5. SCS/AS sends a Network Status Acknowledgement back to SCEF. + +Figure 5.8.3-1: Report procedure for continuous reporting of network status + +1. The RCAF detects a change in the congestion status that is crossing a Threshold (if provided by the SCEF) for the set of cells or eNodeBs belonging to the Location Area requested by the SCEF. An Aggregated Congestion Report message is sent to this SCEF including the SCEF Reference ID and, depending on the operator + +configuration, the congestion status for every cell or eNodeB belonging to the Location Area requested by the SCEF. + +2. The SCEF acknowledges the report to the RCAF. + +NOTE 1: Step 1 and 2 can happen multiple times and the Aggregated Congestion Report message can be sent by any of the involved RCAFs. + +3. Whenever a new Aggregated Congestion Report message arrives, the SCEF stores the report and derives a new NSI for the requested geographical area by combining this report with all other reports having the same SCEF Reference ID in an operator configurable way (governed by SLAs, network topology, usage etc.). + +NOTE 2: Either exact values for congestion status, as reported by RCAF(s) to SCEF or abstracted values e.g. (High, Medium, Low) can be reported by the SCEF to the SCS/AS. The calculation and the reporting of the NSI to the SCS/AS depends on operator configuration (SLAs, network topology, usage etc.). + +4. Triggered by a NSI change (derived in step 3) that is crossing a Threshold (if provided by the SCS/AS), the SCEF sends a Network Status Report (TLTRI, NSI) message to the SCS/AS. +5. The SCS/AS sends a Network Status Acknowledgement to the SCEF. + +#### 5.8.4 Removal procedure for continuous reporting of network status + +This procedure is used for termination of the continuous reporting of network status. It can be triggered by the SCS/AS at any time before the Duration is over or if no Duration was provided. The SCEF will trigger this procedure when the Duration is over. Figure 5.8.4-1 illustrates the procedure. + +![Sequence diagram illustrating the removal procedure for continuous reporting of network status. The diagram shows interactions between RCAF, SCEF, and SCS/AS. The SCEF detects the end of duration (1a) or receives a cancel request from the SCS/AS (1b). The SCEF then performs authorization (2b) and sends a cancel aggregated congestion request to the RCAF (4). The RCAF responds (5), and the SCEF removes the state (6).](38257e5215ad672f308f5235780034a2_img.jpg) + +``` + +sequenceDiagram + participant RCAF + participant SCEF + participant SCS/AS + + Note right of SCEF: 1a. Detect end of Duration + Note right of SCEF: 2b. Authorization + + SCS/AS-->>SCEF: 1b. Cancel Network Status Request + SCEF-->>SCS/AS: 3b. Cancel Network Status Response + SCEF->>RCAF: 4. Cancel Aggregated Congestion Request (SCEF ID) + RCAF-->>SCEF: 5. Cancel Aggregated Congestion Response (SCEF ID) + Note right of SCEF: 6. Remove State + +``` + +Sequence diagram illustrating the removal procedure for continuous reporting of network status. The diagram shows interactions between RCAF, SCEF, and SCS/AS. The SCEF detects the end of duration (1a) or receives a cancel request from the SCS/AS (1b). The SCEF then performs authorization (2b) and sends a cancel aggregated congestion request to the RCAF (4). The RCAF responds (5), and the SCEF removes the state (6). + +**Figure 5.8.4-1: Removal procedure for continuous reporting of network status** + +- 1a. The SCEF detects that the requested Duration for an ongoing continuous reporting of network status to an SCS/AS is over and identifies the corresponding SCEF Reference ID. +- 1b. When the SCS/AS needs to terminate an ongoing continuous reporting of network status, the SCS/AS sends a Cancel Network Status Request (SCS/AS Identifier, TLTRI) message to the SCEF. + +- 2b. If the SCS/AS requested to terminate an ongoing continuous reporting of network status in step 1b, the SCEF authorizes the SCS/AS request and identifies the corresponding SCEF Reference ID. +- 3b. If the SCS/AS requested to terminate an ongoing continuous reporting of network status in step 1b, the SCEF sends a Cancel Network Status Response (Cause) message to the SCS/AS. +4. The SCEF identifies the RCAF(s) involved in the continuous reporting represented by the SCEF Reference ID. The SCEF sends a Cancel Aggregated Congestion Request (SCEF Reference ID) message to the identified RCAF(s). +5. The RCAF removes the related SCEF instructions and stops monitoring the set of cells or eNodeBs belonging to the Location Area for a change in the congestion status. Afterwards, a Cancel Aggregated Congestion Response is sent to the SCEF including the SCEF Reference ID. +6. The SCEF removes all state information related to this continuous reporting represented by the SCEF Reference ID. + +## 5.9 Procedure for resource management of background data transfer + +This clause describes the procedure for resource management of background data transfer to a set of UEs, i.e. an SCS/AS requesting a time window and related conditions from the SCEF via the Nt interface. + +The UEs targeted for background data transfer may be served by a single PCRF or may be spread across multiple PCRFs serving the same or different geographic areas. The operator shall ensure that any of the PCRFs in the network is able to make the decision about transfer policy for background data transfer for non-roaming UEs. + +The transfer policy will be stored in the SPR together with a Reference ID. This ensures that the transfer policy is available to every PCRF responsible for a UE which is subject to this background data transfer in the future. In addition, other (or the same) PCRF can take this transfer policy into account during subsequent decisions about transfer policies for background data related to other SCS/AS. + +At a later point in time, when the SCS/AS (acting as an AF), contacts the PCRF for individual UEs, e.g. to request sponsored connectivity for background data transfer, the SCS/AS needs to also provide the Reference ID together with the SCS/AS session information via the Rx interface. Alternatively, the SCS/AS activates the selected transfer policy via the SCEF, for each UE in the group, by using the "Set the chargeable party at session set-up" or "Change the chargeable party during the session" procedure from clauses 5.12.1 and 5.12.2 to provide the Reference ID to the same or different PCRF. The Reference ID enables the PCRF to correlate the SCS/AS request (that is related to the UE) with the transfer policy retrieved from the SPR (that is related to the SCS/AS). The PCRF finally triggers PCC procedures according to TS 23.203 [27] to provide the respective policing and charging information to the PCEF. + +![Sequence diagram for Resource management for background data transfer. Lifelines: PCEF, SPR, PCRF, SCEF, SCS/AS. The sequence starts with a Background data transfer request from SCS/AS to SCEF, followed by Authorization from SCEF. Then PCC procedures (refer to TS 23.203) occur between SPR and PCRF. SCEF sends a Background data transfer response to SCS/AS. SCS/AS sends another Background data transfer request to SCEF, which responds. Then PCC procedures (refer to TS 23.203) occur again between SPR and PCRF. Finally, Selected Policy Activation occurs between PCEF and SPR.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant PCRF + participant SPR + participant PCEF + + Note right of SCEF: 1. Background data transfer request + SCS/AS->>SCEF: 1. Background data transfer request + Note right of SCEF: 2. Authorization + SCEF-->>SCS/AS: 2. Authorization + Note over SPR, PCRF: 3. PCC procedures (refer to TS 23.203) + SPR->>PCRF: 3. PCC procedures (refer to TS 23.203) + PCRF-->>SPR: 3. PCC procedures (refer to TS 23.203) + Note right of SCEF: 4. Background data transfer response + SCEF-->>SCS/AS: 4. Background data transfer response + Note right of SCS/AS: 5. Background data transfer request + SCS/AS-->>SCEF: 5. Background data transfer request + Note right of SCEF: 6. Background data transfer response + SCEF-->>SCS/AS: 6. Background data transfer response + Note over SPR, PCRF: 7. PCC procedures (refer to TS 23.203) + SPR->>PCRF: 7. PCC procedures (refer to TS 23.203) + PCRF-->>SPR: 7. PCC procedures (refer to TS 23.203) + Note over PCEF, SPR: 8. Selected Policy Activation + PCEF->>SPR: 8. Selected Policy Activation + +``` + +Sequence diagram for Resource management for background data transfer. Lifelines: PCEF, SPR, PCRF, SCEF, SCS/AS. The sequence starts with a Background data transfer request from SCS/AS to SCEF, followed by Authorization from SCEF. Then PCC procedures (refer to TS 23.203) occur between SPR and PCRF. SCEF sends a Background data transfer response to SCS/AS. SCS/AS sends another Background data transfer request to SCEF, which responds. Then PCC procedures (refer to TS 23.203) occur again between SPR and PCRF. Finally, Selected Policy Activation occurs between PCEF and SPR. + +**Figure 5.9-1: Resource management for background data transfer** + +1. A 3rd party SCS/AS sends a Background data transfer request (SCS/AS Identifier, Volume per UE, Number of UEs, Desired time window) message to the SCEF. The Volume per UE describes the volume of data the SCS/AS expects to be transferred per UE. Number of UEs describes the expected amount of UEs participating in the data transfer. Desired time window describes the time interval during which the SCS/AS wants to realize the data transfer. Optionally, the SCS/AS can provide a geographic area information. + +NOTE 1: The SCS/AS does not provide any information about the identity of the UEs in this request. + +2. The SCEF authorizes the SCS/AS request. + +NOTE 2: The SCEF notifies the SCS/AS at this point if the authorization fails. + +3. The SCEF selects any of the available PCRFs and triggers the Negotiation for future background data transfer procedure with the PCRF. The SCEF forwards the parameters provided by the SCS/AS. The PCRF responds to the SCEF with the possible transfer policies and a Reference ID. Refer to clause 7.11.1 of TS 23.203 [27]. +4. The SCEF forwards the Reference ID and the transfer policies to the 3rd party SCS/AS by sending a Background data transfer response (Reference ID, Possible transfer policies) message. The SCS/AS stores the Reference ID for the future interaction with the PCRF. +5. If more than one transfer policy was received, the 3rd party SCS/AS shall select one of them and send another Background data transfer request (SCS/AS Identifier, Selected transfer policy) message to inform the SCEF and PCRF about the selected transfer policy. + +NOTE 3: If there is only one transfer policy offered, the SCS/AS is not required to confirm. + +6. The SCEF confirms the transfer policy selection to the 3rd party SCS/AS by sending a Background data transfer response (Cause) message. +7. The SCEF continues the Negotiation for future background data transfer procedure with the PCRF. The PCRF stores the Reference ID and the new transfer policy in the SPR. Refer to clause 7.11.1 of TS 23.203 [27]. +8. The SCS/AS (acting as an AF) contacts the same or a different PCRF for each individual UE (via the Rx interface), the SCS/AS shall provide the Reference ID. Alternatively, the SCS/AS activates the selected transfer policy via the SCEF, for each UE in the group, by using the "Set the chargeable party at session set-up" or "Change the chargeable party during the session" procedure from clauses 5.12.1 and 5.12.2 to provide the + +Reference ID to the same or different PCRF. The PCRF correlates the SCS/AS or SCEF request with the transfer policy retrieved from the SPR via the Reference ID. The PCRF finally triggers PCC procedures according to TS 23.203 [27] to provide the respective policing and charging information to the PCEF for the background data transfer of this UE. + +NOTE 4: The SCS/AS will typically request sponsored connectivity for the background data transfer to individual UEs. + +NOTE 5: The SCS/AS can contact the PCRF directly or interact with the PCRF via the SCEF. + +## 5.10 Communication Pattern parameters provisioning procedure + +### 5.10.1 Communication Pattern parameters + +A set of Communication Pattern (CP) parameters is defined in the table below. All CP parameters are optional. + +These CP parameters are specific for a UE or a group of UEs. Sets of these CP parameters are provided by the SCEF to the HSS which distributes them to the corresponding MME with relevant subscriber data. These CP parameter sets may be related to both PDN connection(s) and SMS transmission. The MME considers the sets of CP parameters (e.g. by merging per CP parameter if multiple sets are present), before using the parameters. Each CP parameter set shall have an associated validity time. The validity time indicates when the CP parameter set expires and shall be deleted by the HSS/MME. The validity time may be set to a value indicating that the particular CP parameter set has no expiration time. When the validity time expires, the involved nodes (SCEF, HSS, and MME) autonomously delete the associated CP parameter set with no additional signalling between the involved nodes. + +NOTE 1: It is expected that the format of validity time, to be defined by Stage 3, is defined in a manner which allows SCEF, HSS and MME/SGSN to consistently and uniformly interpret the expiration of the associated CP parameters set. + +**Table 5.10.1-1: CP parameters** + +| CP parameter | Description | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1) Periodic communication indicator | Identifies whether the UE communicates periodically or not, e.g. only on demand. [optional] | +| 2) Communication duration time | Duration interval time of periodic communication [optional, may be used together with 1)]
Example: 5 minutes | +| 3) Periodic time | Interval Time of periodic communication [optional, may be used together with 1)]
Example: every hour | +| 4) Scheduled communication time | Time zone and Day of the week when the UE is available for communication [optional]
Example: Time: 13:00-20:00, Day: Monday | +| 5) Stationary indication | Identifies whether the UE is stationary or mobile [optional] | +| 6) Battery indication | Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered. [optional] | +| X) Traffic Profile | Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission. [optional] | + +NOTE 2: The Traffic Profile is provided to the eNB for optimisation of RAN resources and how it is used is specified in TS 23.401 [7]. + +## 5.10.2 Communication Pattern parameters provisioning to the MME + +![Sequence diagram for provisioning of CP Parameters. Lifelines: MME, HSS, SCEF, SCS/AS. The sequence starts with an 'Update request (Communication Pattern)' from SCS/AS to SCEF. SCEF responds with 'Select CP parameter'. SCEF then sends an 'Update CP Parameter Request' to HSS. HSS performs an 'Update UE subscription' and sends an 'Update CP Parameter Response' to SCEF. SCEF sends an 'Update Response' to SCS/AS. Finally, HSS sends a 'Provide CP parameters or deletion notice to the MME'.](da06747b80ea0d71593cbbd4c2ea89aa_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + participant MME + Note right of SCEF: 2. Select CP parameter + SCS/AS->>SCEF: 1. Update request (Communication Pattern) + SCEF->>HSS: 3. Update CP Parameter Request + HSS->>HSS: 4. Update UE subscription + HSS->>SCEF: 5. Update CP Parameter Response + SCEF->>SCS/AS: 6. Update Response + HSS->>MME: 7. Provide CP parameters or deletion notice to the MME + +``` + +Sequence diagram for provisioning of CP Parameters. Lifelines: MME, HSS, SCEF, SCS/AS. The sequence starts with an 'Update request (Communication Pattern)' from SCS/AS to SCEF. SCEF responds with 'Select CP parameter'. SCEF then sends an 'Update CP Parameter Request' to HSS. HSS performs an 'Update UE subscription' and sends an 'Update CP Parameter Response' to SCEF. SCEF sends an 'Update Response' to SCS/AS. Finally, HSS sends a 'Provide CP parameters or deletion notice to the MME'. + +**Figure 5.10.2-1: Signalling sequence for provisioning of CP Parameters** + +- The SCS/AS sends an Update Request (External Identifier or MSISDN or External Group Identifier, SCS/AS Identifier, CP parameter Set Id(s), CP parameter set(s), validity time(s), CP parameter Set Id(s) for Deletion, MTC Provider Information) message to the SCEF. The CP parameter set(s) include the parameters defined in Table 5.10.1-1. A CP parameter Set Id is assigned to each CP parameter set by the SCS/AS. + +NOTE 1: The SCS/AS uses this procedure to add, change or delete some or all of the CP parameter sets of the UE, e.g. if the AS is aware that the UE has started or stopped moving for a significant time period, especially if the AS is instructing the UE to do so, then the SCS/AS provides the corresponding CP parameter set(s) and its validity time(s) as well their CP parameter Set Id(s) to the SCEF. If the SCS/AS wants to perform deletion of a previously configured CP parameter set(s) together with configuring a new CP parameter set(s), then it shall include both the new CP parameter set(s), and CP parameter Set Id(s) for Deletion representing the CP parameter set(s) which requires cancellation. If the SCS/AS wants to only perform deletion of a previously configured CP parameter set(s), then it shall include CP parameter Set Id(s) for Deletion. + +- The SCEF checks if the SCS/AS is authorised to send CP requests to the UE or to each UE in the identified group. The SCEF filters and the selects the CP parameter set(s) for add/modify/delete based on operator policy or configuration. The SCEF does not check for potential overlapping of CP parameters if there are multiple CP parameter set(s) for the UE, but this is handled in the MME. + +In this release, to avoid receiving CP parameter sets from multiple SCEFs that might be overlapping, the HSS shall accept CP parameter sets from only a single SCEF for a given UE. + +- The SCEF sends Update CP Parameter Request (External Identifier or MSISDN or External Group Identifier, SCEF Reference ID(s), SCEF Address, CP parameter set(s), validity time(s), SCEF Reference ID(s) for Deletion, MTC Provider Information) message to the HSS for delivering the selected CP parameter set(s) per UE. There may be multiple CP parameter sets included in this message where each CP parameter set for addition or modification has been determined to be non-overlapping with other CP parameter sets either included in the message or already provisioned for a given UE. The SCEF derives the SCEF Reference ID(s) for CP parameter sets to be sent to the HSS based on the CP parameter Set Id(s) from the SCS/AS. + +NOTE 2: A request for deletion of a CP parameter set from the SCS/AS may result in a request for modification of the non-overlapping CP parameter set by the SCEF. + +NOTE 3: The MTC Provider Information in step 1 is an optional parameter. The SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information, if not present in step 1, is left to implementation (e.g. based on the requesting SCS/AS) + +4. The HSS examines the Update CP Parameter Request message, e.g. with regard to the existence of External Identifier or MSISDN or External Group Identifier. If the check fails, the HSS immediately sends a response message back to the SCEF following step 5. The HSS resolves the External Identifier or MSISDN to an IMSI or resolves the External Group Identifier to an IMSI-Group Identifier and stores the CP parameter set(s) and their validity time(s) as part of UE subscription data identified by the IMSI or IMSI-Group Identifier, so that the CP parameter set(s) can be forwarded to the serving MME(s) when the serving MME(s) are changed due to the mobility of the UE. + +The HSS determines that a stored CP parameters set is to be modified by the fact that the SCEF Reference ID associated with the CP parameters set matches an SCEF Reference ID for a CP parameters set already stored for a given UE. If the HSS determines that an existing CP parameter set is to be modified, the HSS discards the already stored CP parameter set and stores the new CP parameter set and validity time under the same SCEF Reference ID. + +The HSS stores a new CP parameter set along with the associated SCEF Reference ID and validity time. + +If CP parameters sets are to be deleted, the HSS removes the CP parameters sets from the subscription. + +If the validity time for a CP parameter set stored in the HSS expires, the HSS autonomously deletes the associated CP parameter set with no additional signalling. + +NOTE 3: The CP parameter set(s) are not provided to the SGSN. + +NOTE 4: The HSS does not need to validate the content of the stored CP parameters set(s). + +5. The HSS sends Update CP Parameter Response (SCEF Reference ID, Cause) message to the SCEF. The cause value indicates successful subscription update or the reason of failed subscription update. +6. The SCEF sends the Update Response (CP parameter Set Id(s), Cause(s)) message to inform the SCS/AS whether the provision of the CP parameter set(s) was successful. +7. The HSS initiates an Insert Subscription Data procedure for each UE to send the CP parameter set(s) with the corresponding validity time(s), SCEF Reference ID(s), and SCEF Reference ID(s) for Deletion to the MME. Optionally, the HSS allocates a Provider-Group-ID (different from the IMSI-Group-Id) based on the MTC Provider Information and sends it to the MME to assist the serving node(s) when selecting and differentiating configurations for a given MTC Service Provider (e.g. to delete the CP Set Id(s) for a specific MTC Service Provider at the MME). + +The MME determines that a stored CP parameters set is to be modified by the fact that the SCEF Reference ID associated with the CP parameters set matches an SCEF Reference ID for a CP parameters set already stored for the UE. If the MME determines that an existing CP parameter set is to be modified, the MME discards the already stored CP parameter set and stores the received CP parameter set with the associated validity time in the UE's (E)MM context under the same SCEF Reference ID. + +The MME stores a new CP parameter set along with the associated SCEF Reference ID and validity time. The MME may use the CP parameter set(s) as described in TS 23.401 [7]. + +If CP parameter sets are to be deleted, the MME removes the CP parameter sets from the subscription. + +If the validity time for a CP parameter set stored in the MME expires, the MME autonomously deletes the associated CP parameter set with no additional signalling. + +## 5.11 Setting up an AS session with required QoS procedure + +This clause describes the signalling flow for setting up a 3rd party AS session with a specific QoS. + +![Sequence diagram illustrating the interaction between PCEF, PCRF, OCS, SCEF, and SCS/AS for setting up an AS session with required QoS. The sequence starts with an On-demand QoS request from SCS/AS to SCEF, followed by Authorization and Parameter mapping. Then, a PCRF initiated IP-CAN Session Modification is triggered. The SCEF sends an On-demand QoS response to SCS/AS. Finally, a PCEF initiated IP-CAN Session Modification is triggered, and the SCEF sends Status information to SCS/AS.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant PCRF + participant PCEF + participant OCS + + Note right of SCEF: 2. Authorization + Note right of SCEF: 3. Parameter mapping + + SCS/AS->>SCEF: 1. On-demand QoS request + SCEF->>PCRF: 4. PCRF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.2 + Note left of PCRF: 4. PCRF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.2 + SCEF->>SCS/AS: 5. On-demand QoS response + Note right of PCEF: 6. PCEF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.1 + PCEF-->>SCEF: 6. PCEF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.1 + Note right of SCEF: 7. Status information + SCEF-->>SCS/AS: 7. Status information + +``` + +Sequence diagram illustrating the interaction between PCEF, PCRF, OCS, SCEF, and SCS/AS for setting up an AS session with required QoS. The sequence starts with an On-demand QoS request from SCS/AS to SCEF, followed by Authorization and Parameter mapping. Then, a PCRF initiated IP-CAN Session Modification is triggered. The SCEF sends an On-demand QoS response to SCS/AS. Finally, a PCEF initiated IP-CAN Session Modification is triggered, and the SCEF sends Status information to SCS/AS. + +**Figure 5.11-1: Setting up an AS session with required QoS** + +1. When setting up the connection between SCS/AS and the UE with required QoS for the service, the SCS/AS sends an On-demand QoS request message (UE IP address, SCS/AS Identifier, Description of the application flows or External Application Identifier, QoS reference) to the SCEF. Optionally, a period of time or a traffic volume for the requested QoS can be included in the SCS/AS request. The SCEF assigns a TLTRI to the On-demand QoS request. +2. The SCEF authorizes the SCS/AS request and may apply policies to control the overall amount of pre-defined QoS authorized for the SCS/AS. If the authorisation is not granted, steps 3 and 4 are skipped and the SCEF replies to the SCS/AS with a Result value indicating that the authorisation failed. +3. The SCEF maps the UE IP address, the SCS/AS Identifier, the Description of the application flows and the QoS reference to existing Rx parameters (including the optionally received period of time or traffic volume which is mapped to sponsored data connectivity information). The SCEF acts as an AF defined in TS 23.203 [27]. + +NOTE: Before the QoS reference is mapped to Rx parameters, the SCEF can perform a mapping from the name space of the 3rd party SCS/AS to the name space of the operator. + +4. The SCEF interacts with the PCRF via the Rx interface and triggers a PCRF initiated IP-CAN Session Modification as described in clause 7.4.2 of TS 23.203 [27]. The SCEF shall request to be notified about the transmission resource status. + +The PCRF derives the required QoS based on the information provided by the SCEF and determines whether this QoS is allowed (according to the PCRF configuration for this 3rd party SCS/AS), and notifies the result to the SCEF. + +The PCRF notifies the SCEF whether the transmission resources corresponding to the QoS request are established or not. + +5. The SCEF sends an On-demand QoS response message (TLTRI, Result) to the SCS/AS. Result indicates whether the QoS request is granted or not. +6. The PCRF may notify the SCEF about bearer level events for the Rx session (e.g. transmission resources are released/lost) with a PCEF initiated IP-CAN Session Modification as described in clause 7.4.1 of TS 23.203 [27]. +7. If the SCEF gets informed by the PCRF about bearer level events for the Rx session (e.g. transmission resources are released/lost) the SCEF sends a Status information message (SCS/AS Identifier, TLTRI, Status) to the SCS/AS. The status indicates the bearer level event received from the PCRF. + +## 5.12 Change the chargeable party at session set-up or during the session procedure + +### 5.12.1 Set the chargeable party at session set-up + +This clause describes the signalling flow for setting the chargeable party at AS session set-up. The SCS/AS may either request to sponsor the traffic from the beginning or may request to become the chargeable party at a later point in time. + +![Sequence diagram showing the signalling flow for setting the chargeable party at AS session set-up. The diagram involves five entities: PCEF, PCRF, OCS, SCEF, and SCS/AS. The flow is as follows: 1. SCS/AS sends a 'Set chargeable party request' to SCEF. 2. SCEF sends an 'Authorization' message to OCS. 3. A 'PCRF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.2' is shown as a horizontal bar across PCEF, PCRF, and OCS. 4. SCEF sends a 'Set chargeable party response' to SCS/AS.](691626a7032a642bb74793336c37e274_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant OCS + participant PCRF + participant PCEF + Note right of SCS/AS: 1. Set chargeable party request + SCS/AS->>SCEF: 1. Set chargeable party request + Note right of SCEF: 2. Authorization + SCEF->>OCS: 2. Authorization + Note over PCEF, PCRF, OCS: 3. PCRF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.2 + Note right of SCEF: 4. Set chargeable party response + SCEF->>SCS/AS: 4. Set chargeable party response + +``` + +Sequence diagram showing the signalling flow for setting the chargeable party at AS session set-up. The diagram involves five entities: PCEF, PCRF, OCS, SCEF, and SCS/AS. The flow is as follows: 1. SCS/AS sends a 'Set chargeable party request' to SCEF. 2. SCEF sends an 'Authorization' message to OCS. 3. A 'PCRF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.2' is shown as a horizontal bar across PCEF, PCRF, and OCS. 4. SCEF sends a 'Set chargeable party response' to SCS/AS. + +**Figure 5.12.1-1: Set the chargeable party at AS session set-up** + +1. When setting up the connection between the AS and UE, the SCS/AS may request to become the chargeable party for the session to be set up by sending a Set chargeable party request message (SCS/AS Identifier, Description of the application flows or External Application Identifier, sponsor information, Sponsoring Status, Reference ID) to the SCEF, including optionally a usage threshold. The Sponsoring Status indicates whether sponsoring is started or stopped, i.e. whether the 3rd party service provider is the chargeable party or not. The Reference ID parameter identifies a previously negotiated transfer policy for background data transfer as defined in clause 4.5.9. The SCEF assigns a TLTRI to the Set chargeable party request. +2. The SCEF authorizes the SCS/AS request to sponsor the application traffic and stores the sponsor information together with the SCS/AS Identifier and the TLTRI. If the authorisation is not granted, step 3 is skipped and the SCEF replies to the SCS/AS with a Result value indicating that the authorisation failed. + +NOTE 1: Based on operator configuration, the SCEF may skip this step. In this case the authorization is performed by the PCRF in step 3. + +3. The SCEF interacts with the PCRF by triggering a PCRF initiated IP-CAN Session Modification as described in clause 7.4.2 of TS 23.203 [27] and provides IP filter information, sponsored data connectivity information (as defined in TS 23.203 [27]), Reference ID (if received from the SCS/AS) and Sponsoring Status (if received from the SCS/AS) to the PCRF. + +NOTE 2: The SCEF maps the Sponsoring Status to existing Rx parameters. + +The PCRF determines whether the request is allowed and notifies the SCEF if the request is not authorized. If the request is not authorized, SCEF responds to the SCS/AS in step 4 with a Result value indicating that the authorization failed. + +As specified in TS 23.203 [27], the PCRF determines the PCC rule(s) for the specified session including charging control information. Charging control information shall be set according to the Sponsoring Status (if received over Rx), i.e. either indicating that the 3rd party service provider is the chargeable party or not. The PCC rule(s) for the specified session shall then be provided to the PCEF. In the case of online charging and depending on operator configuration, the PCEF may request credit when the first packet corresponding to the service is detected or at the time the PCC Rule was activated. + +The PCRF notifies the SCEF that the request is accepted. + +4. The SCEF sends a Set chargeable party response message (TLTRI, Result) to the SCS/AS. Result indicates whether the request is granted or not. + +## 5.12.2 Change the chargeable party during the session + +This clause describes the signalling flow for changing the chargeable party during an ongoing AS session, i.e. the SCS/AS starting or stopping to sponsor the application traffic. + +![Sequence diagram showing the change chargeable party during an AS session. The diagram involves five entities: PCEF, PCRF, OCS, SCEF, and SCS/AS. The sequence of messages is: 1. SCS/AS sends a 'Change chargeable party request' to SCEF. 2. SCEF sends an 'Authorization' message to PCRF. 3. PCRF initiates an 'IP-CAN Session Modification' (according to TS23.203 clause 7.4.2) which involves PCEF, PCRF, and OCS. 4. SCEF sends a 'Change chargeable party response' to SCS/AS.](7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant PCRF + participant OCS + participant PCEF + + Note right of SCEF: 2. Authorization + SCS/AS->>SCEF: 1. Change chargeable party request + SCEF->>PCRF: 2. Authorization + Note left of PCEF: 3. PCRF initiated IP-CAN Session Modification according to TS23.203 clause 7.4.2 + Note right of SCEF: 4. Change chargeable party response + SCEF->>SCS/AS: 4. Change chargeable party response + +``` + +Sequence diagram showing the change chargeable party during an AS session. The diagram involves five entities: PCEF, PCRF, OCS, SCEF, and SCS/AS. The sequence of messages is: 1. SCS/AS sends a 'Change chargeable party request' to SCEF. 2. SCEF sends an 'Authorization' message to PCRF. 3. PCRF initiates an 'IP-CAN Session Modification' (according to TS23.203 clause 7.4.2) which involves PCEF, PCRF, and OCS. 4. SCEF sends a 'Change chargeable party response' to SCS/AS. + +**Figure 5.12.2-1: Change chargeable party during an AS session** + +1. For the ongoing AS session, the SCS/AS may send a Change chargeable party request message (SCS/AS Identifier, TLTRI, Sponsoring Status, Reference ID) to the SCEF, including optionally a usage threshold. The Sponsoring Status indicates whether sponsoring is enabled or disabled, i.e. whether the 3rd party service provider is the chargeable party or not. The Reference ID parameter identifies a previously negotiated transfer policy for background data transfer as defined in clause 4.5.9. The TLTRI provided in the Change chargeable party request message is set to the TLTRI that was assigned, by the SCEF, to the Set chargeable party request. +2. The SCEF authorizes the SCS/AS request of changing the chargeable party. If the authorisation is not granted, step 3 is skipped and the SCEF replies to the SCS/AS with a Result value indicating that the authorisation failed. + +NOTE 1: Based on operator configuration, the SCEF may skip this step. In this case the authorization is performed by the PCRF in step 3. + +3. Based on the SCS/AS Identifier and the TLTRI the SCEF determines the relevant Rx session and interact with the PCRF by triggering a PCRF initiated IP-CAN Session Modification as described in clause 7.4.2 of TS 23.203 [27]. The SCEF provides sponsored data connectivity information (as defined in TS 23.203 [27]), Reference ID (if received from the SCS/AS), and the Sponsoring Status to the PCRF. + +NOTE 2: The SCEF maps the Sponsoring Status to existing Rx parameters. + +The PCRF determines whether the request is allowed and notifies the SCEF if the request is not authorized. If the request is not authorized, SCEF responds to the SCS/AS in step 4 with a Result value indicating that the authorization failed. + +The PCRF identifies the affected PCC rule(s) and reacts based on their current status. If the traffic is subject to subscriber charging in the PCEF and the PCRF receives a Sponsoring Status indicating that sponsoring is started, the PCC rule(s) for the specified session shall be modified so that the charging control information indicates that the 3rd party service provider is charged for the traffic. If the traffic is subject to 3rd party charging in the PCEF and the PCRF receives a Sponsoring Status indicating that sponsoring is stopped, the PCC rule(s) for the specified session shall be modified so that the charging control information indicates that the 3rd party service provider is no longer charged for the traffic. As specified in TS 23.203 [27], PCRF modifies the PCC rule(s) of the service data flow accordingly and provides them to the PCEF. In the case of online charging and depending on operator configuration, the PCEF may request credit when the first packet corresponding to the service is detected or at the time the PCC Rule was activated. + +The PCRF notifies the SCEF that the request is accepted. + +4. The SCEF sends a Change chargeable party response message (Result) to the SCS/AS. Result indicates whether the request is granted or not. + +## 5.13 Non-IP Data Delivery procedures + +### 5.13.1 T6a/T6b Connection Establishment + +#### 5.13.1.1 General + +When the UE performs the EPS attach procedure (see TS 23.401 [7]) with PDN type of "Non-IP", and the subscription information corresponding to either the default APN for PDN type of "Non-IP" or the UE requested APN includes the "Invoke SCEF Selection" indicator, then the MME initiates a T6a/T6b connection towards the SCEF corresponding to the "SCEF ID" indicator for that APN. + +#### 5.13.1.2 T6a/T6b Connection Establishment Procedure + +![Sequence diagram of the T6a/T6b Connection Establishment Procedure. The diagram shows four lifelines: UE, MME/SGSN, ROAMING (containing IWK-SCEF), and SCEF. Step 1: UE sends an Attach procedure or PDN Connectivity procedure or PDP Context Activation procedure to the MME/SGSN. Step 2: MME/SGSN sends a Create SCEF Connection Request to the SCEF, passing through the IWK-SCEF. Step 3: SCEF sends a Create SCEF Connection Response back to the MME/SGSN, passing through the IWK-SCEF.](41af98c5f15e6022f8ddde55567cf56e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME/SGSN + participant ROAMING as ROAMING + participant SCEF + Note over UE, MME/SGSN: 1. Attach procedure or PDN Connectivity procedure or PDP Context Activation procedure + MME/SGSN->>SCEF: 2. Create SCEF Connection Request + Note over ROAMING: IWK-SCEF + SCEF-->>MME/SGSN: 3. Create SCEF Connection Response + +``` + +Sequence diagram of the T6a/T6b Connection Establishment Procedure. The diagram shows four lifelines: UE, MME/SGSN, ROAMING (containing IWK-SCEF), and SCEF. Step 1: UE sends an Attach procedure or PDN Connectivity procedure or PDP Context Activation procedure to the MME/SGSN. Step 2: MME/SGSN sends a Create SCEF Connection Request to the SCEF, passing through the IWK-SCEF. Step 3: SCEF sends a Create SCEF Connection Response back to the MME/SGSN, passing through the IWK-SCEF. + +**Figure 5.13.1.2-1: T6a/T6b Connection Establishment Procedure** + +1. UE performs steps 1-11 of the E-UTRAN Initial Attach procedure or step 1 of the UE requested PDN Connectivity procedure (see TS 23.401 [7]) or PDP Context Activation Procedure (see TS 23.060 [6]). The MME/SGSN receives subscription information for a non-IP PDN connection to an APN that is associated with an "Invoke SCEF Selection" indicator, and SCEF ID. If the MSISDN is also associated with the user's subscription, then it is made available as User Identity to the MME/SGSN by the HSS. +2. If the subscription information corresponding to either the default APN for PDN type of "Non-IP" or the UE requested APN includes "Invoke SCEF Selection" indicator, then instead of step 12-16 of the E-UTRAN Initial Attach procedure (see clause 5.3.2.1 of TS 23.401 [7]) or instead of step 2-6 of the UE requested PDN connectivity procedure (see clause 5.10.2 of TS 23.401 [7]) or instead of step 4-8 of the PDP Context Activation procedure (see clause 9.2.2.1 of TS 23.060 [6]), the MME/SGSN shall create a PDN connection towards the SCEF and allocate an EPS Bearer Identity (EBI) (see TS 23.401 [7]) to that PDN connection. The MME/SGSN does so by sending a Create SCEF Connection Request (User Identity, EPS Bearer Identity, SCEF ID, APN, Serving PLMN Rate Control, PCO, Serving PLMN ID, IMEISV) message towards the SCEF (see clause 4.7.7 of TS 23.401 [7]). If the IWK-SCEF receives the Create SCEF Connection Request message from the MME/SGSN, it shall forward it toward the SCEF. + +NOTE 1: The combination of EPS Bearer Identity, APN, and User Identity allows the SCEF to uniquely identify the PDN connection to the SCEF for a given UE. + +NOTE 2: For further details of T6a/T6b interactions please refer to Stage 3 specifications. + +NOTE 3: The details of how the MME/SGSN and SCEF encode the PCO's information on T6a/T6b are left to stage 3. + +If an SCS/AS has performed the NIDD Configuration procedure (see clause 5.13.2) with the SCEF for User Identity received in step 2, then step 3 is executed. If no SCS/AS has performed the NIDD Configuration procedure (see clause 5.13.2) with the SCEF for the User Identity, then the SCEF may: + +- reject the T6a/T6b connection setup, or +- initiate a NIDD Configuration procedure with SCS/AS configured in the SCEF using implementation specific procedures. + +For E-UTRAN, if provided by the MME, the SCEF may take the APN Rate Control Status into account when encoding the APN Rate Control parameters in Protocol Configuration Options and when enforcing the APN Rate Control as described in clause 4.7.7.3 of TS 23.401 [7]. + +3. The SCEF creates an SCEF EPS Bearer Context (see clause 5.3.2) for the user identified via User Identity and EBI. The SCEF sends a Create SCEF Connection Response (User Identity, EPS Bearer Identity, SCEF ID, APN, PCO, NIDD Charging ID) message towards the MME/SGSN confirming establishment of the PDN connection to the SCEF for the UE. If the IWK-SCEF receives the Create SCEF Connection Response message from the SCEF, it shall forward it toward the MME/SGSN. + +NOTE 4: For further details of T6a/T6b interactions please refer to Stage 3 specifications. + +## 5.13.2 NIDD Configuration + +Figure 5.13.2-1 illustrates the procedure of configuring necessary information at the SCEF and HSS. A NIDD Configuration is associated with a single UE or a group of UEs. The procedure can also be used for replacing and deleting configuration information. + +NOTE 1: In order to avoid MO NIDD failure, the NIDD configuration procedure should be performed by the SCS/AS prior to the UE establishing a PDN Connection that is served by the SCEF. MT non-IP data from the SCS/AS can be contained in the NIDD Configuration Request message. + +![Sequence diagram for NIDD Configuration procedure. The diagram shows three participants: HSS, SCEF, and SCS/AS. The sequence of messages is: 1. NIDD Configuration Request from SCS/AS to SCEF; 2. SCEF handling (internal SCEF step); 3. NIDD Authorization Request from SCEF to HSS; 4. HSS handling (internal HSS step); 5. NIDD Authorization Response from HSS to SCEF; 6. NIDD Configuration Response from SCEF to SCS/AS.](8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + Note right of SCEF: 2. SCEF handling + Note right of HSS: 4. HSS handling + SCS/AS->>SCEF: 1. NIDD Configuration Request + SCEF->>HSS: 3. NIDD Authorization Request + HSS->>SCEF: 5. NIDD Authorization Response + SCEF->>SCS/AS: 6. NIDD Configuration Response + +``` + +Sequence diagram for NIDD Configuration procedure. The diagram shows three participants: HSS, SCEF, and SCS/AS. The sequence of messages is: 1. NIDD Configuration Request from SCS/AS to SCEF; 2. SCEF handling (internal SCEF step); 3. NIDD Authorization Request from SCEF to HSS; 4. HSS handling (internal HSS step); 5. NIDD Authorization Response from HSS to SCEF; 6. NIDD Configuration Response from SCEF to SCS/AS. + +Figure 5.13.2-1: Configuration for NIDD procedure + +1. The SCS/AS sends an NIDD Configuration Request (External Group Identifier or External Identifier or MSISDN, SCS/AS Identifier, NIDD Duration, T8 Destination Address, TLTRI, Requested Action, PDN Connection Establishment Option, Reliable Data Service Configuration, MTC Provider Information) message to the SCEF. PDN Connection Establishment Option an optional field that is used to indicate what the SCEF should do if the UE, or group member UEs, has not established the PDN connection and MT non-IP data needs to be sent (wait for the UE to establish the PDN connection, respond with an error cause, or send a device trigger; see step 2 of the MT NIDD Procedure in clause 5.13.3). When PDN Connection Establishment Option is included in the Configuration of NIDD procedure, the SCEF will use the value as the default preference from the SCS/AS when handling all MT non-IP packets associated with the NIDD connection. Reliable Data Service Configuration is an optional parameter that is used to configure the Reliable Data Service (as defined in clause 4.5.14.3) including port numbers for originator application(s) and receiver application(s) and the mobile + +terminated and mobile originated serialization format(s) that are supported by the SCS/AS for each port number. TLTRI is included in the request if the Requested Action is set to "Update" or "Cancel", otherwise TLTRI is not included in the request and the SCEF assigns a TLTRI to the NIDD Configuration. + +NOTE 2: If the SCS/AS does not indicate serialization formats, it is assumed that the UE application is provisioned to know what serialization format will be used for MT traffic or that the SCS/AS will use the same format that is used by the associated MO traffic. + +When MT non-IP data is included in the NIDD Configuration request message, the SCEF can send the MT non-IP data to the UE only after a PDN connection to the SCEF is established as defined in clause 5.13.1.2. In such cases, upon successful completion of step 6 of the NIDD Configuration procedure, steps 2-9 from clause 5.13.3 are executed. When MT non-IP data is included in the request, the SCS/AS should also provide the parameters in step 1 of clause 5.13.3 so that the SCEF can properly execute steps 2-9 from clause 5.13.3. MT non-IP data shall not be included in the NIDD Configuration Request when the procedure is performed on an External Group Identifier. + +NOTE 3: It is up to the SCS/AS to determine whether and if NIDD Duration can be set to never expire. + +NOTE 4: The SCS/AS is expected to be configured to use the same SCEF as the one selected by the MME/SGSN during the UE's attachment to the network. + +NOTE 5: A relative priority scheme for the treatment of multiple SCS/AS NIDD Configuration Requests, e.g. for deciding which requests to serve under overload condition, can be applied. This priority scheme is an implementation option that is used locally by the SCEF, i.e. it is neither used nor translated in procedures towards other functions. + +NOTE 6: When more than one SCS/AS is associated with a PDN connection, the parameters that are provided in step 1 can be provisioned in the SCEF based on operator policy or configuration. In which case, any parameters that are provided in step 1 that conflict with the provisioned values are ignored. + +2. If the Requested Action is set to "Cancel" it indicates the purpose of the request is to cancel the transaction identified by TLTRI and the flow proceeds to step 6. If the Requested Action is set to "Update", the purpose of the transaction is to update the parameters associated with the configuration (i.e. Reliable Data Service, PDN Connection Establishment Option). Otherwise, the request is for a new NIDD configuration and the SCEF stores the External Group Identifier, External Identifier or MSISDN, TLTRI, SCS/AS Identifier, T8 Destination Address, PDN Connection Establishment Option, and NIDD Duration. If either the SCS/AS is not authorized to perform this request (e.g. based on policies, if the SLA does not allow for it) or the NIDD Configuration Request is malformed, the SCEF performs step 6 and provides a Cause value appropriately indicating the error. Depending on the configuration, the SCEF may change the NIDD Duration. + +3. The SCEF sends an NIDD Authorization Request (External Group Identifier or External Identifier or MSISDN, APN, MTC Provider Information) message to the HSS to authorize the NIDD configuration request for the UEs that belongs to the External Group Identifier, received External Identifier or MSISDN, and to receive necessary information for NIDD, if required. + +NOTE 7: The SCEF uses the SCS/AS Identifier and External Group Identifier, External Identifier or MSISDN that was obtained in step 1 to determine what APN will be used to enable transfer of non-IP data between the UE and the SCS/AS. This determination is based on local policies. + +NOTE 8: The MTC Provider Information in step 1 is an optional parameter. The SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information, if not present in step 1, is left to implementation (e.g. based on the requesting SCS/AS). + +4. The HSS examines the NIDD Authorization Request message, e.g. with regards to the existence of External Group Identifier, External Identifier or MSISDN. If an External Identifier was included in the NIDD Authorization Request, the HSS maps the external identifier to IMSI and/or MSISDN and updates the SCEF ID field of the PDN subscription context for the provided APN with the requesting SCEF's ID. Otherwise, if an External Group Identifier was included in the NIDD Authorization Request, the HSS authorizes the NIDD configuration request for the received External Group Identifier, resolves the External Group Identifier to an IMSI-Group Identifier and an External Identifier and/or MSISDN for each of the IMSIs in the IMSI-Group. If this check fails, the HSS follows step 5 and provides a result indicating the reason for the failure condition to the SCEF. If the SCEF ID is different from the one in the PDN subscription contexts for the provided APN, the HSS + +updates the SCEF ID at the MME/SGSN for the provided APN. If this update fails, the HSS follows step 5 and provides a result indicating the reason for the failure condition to the SCEF. + +NOTE 9: How the HSS selects an External ID when multiple External IDs are associated with the same IMSI is left to implementation, e.g. based on the MTC Provider Information (if received) or the default External ID (if not received). + +5. The HSS sends an NIDD Authorization Response (with single value or list of (IMSI and MSISDN or External Identifier), Result) message to the SCEF to acknowledge acceptance of the NIDD Authorization Request. If the HSS determines that the list size exceeds the message capacity, the HSS shall segment the list and send it in multiple messages (for details on segmentation, see TS 29.336 [45]). The IMSI(s) and, if available, the MSISDN(s) (when NIDD Configuration Request contains an External Identifier) or if available, External Identifier(s) (when NIDD Configuration Request contains an MSISDN) are returned by the HSS in this message. This allows the SCEF to correlate the SCS/AS request received in step 1 of this procedure to the T6a/T6b Connection established (see clause 5.13.1.2) for each UE or each group member UE. +6. The SCEF sends an NIDD Configuration Response (TLTRI, Maximum Packet Size, Reliable Data Service Indication, and Cause) message to the SCS/AS to acknowledge acceptance of the NIDD Configuration Request and the deletion of the identified NIDD configuration, if it was requested. If the NIDD Configuration was accepted, the SCEF will create an association between the TLTRI, External Group Identifier or External Identifier or MSISDN, IMSI, and EBI of the non-IP PDN Connection. In the MT NIDD procedure, the SCEF will use TLTRI and External Group Identifier or External Identifier or MSISDN to determine the IMSI(s) and EBI(s) of the non-IP PDN Connection(s). In the MO NIDD procedure, the SCEF will use the IMSI(s) and EBI(s) to obtain the TLTRI, External Identifier or MSISDN. The Reliable Data Service Indication indicates if the Reliable Data Service is enabled in the APN configuration. The Maximum Packet Size is the maximum NIDD packet size that was transferred to the UE by the SCEF in the PCO, see clause 4.5.14.1. If no maximum packet size was provided to the UE by the SCEF, the SCEF sends a default configured max packet size to SCS/AS. + +### 5.13.3 Mobile Terminated NIDD procedure + +Figure 5.13.3-1 illustrates the procedure using which the SCS/AS sends non-IP data to a given user as identified via External Identifier or MSISDN. This procedure assumes that procedures in clause 5.13.1 is completed. + +![Sequence diagram for Mobile Terminated NIDD procedure. Lifelines: UE, MME/SGSN, HSS, ROAMING (IWK-SCEF), SCEF, SCS/AS. The sequence shows the SCS/AS sending an MT NIDD Submit Request to the SCEF, which then interacts with the HSS and MME/SGSN to deliver the data to the UE.](550eaffa2d1e03391ac33ccb5ad16cd3_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + participant MME/SGSN + participant UE + Note right of SCEF: ROAMING (IWK-SCEF) + + SCS/AS->>SCEF: 1. MT NIDD Submit Request + SCEF->>SCEF: 2a. Authorization and load control + SCEF-->>SCS/AS: 2b. MT NIDD Submit Response + SCEF->>HSS: 3. NIDD Submit Request + HSS-->>MME/SGSN: 4. NIDD Submit Response + Note right of SCEF: (IWK-SCEF) + SCEF-->>SCS/AS: 5. MT NIDD Submit Response + Note right of SCEF: (IWK-SCEF) + SCEF-->>HSS: 6. NIDD Submit Indication + Note right of SCEF: (IWK-SCEF) + HSS-->>MME/SGSN: 7. NIDD Submit Request + Note right of SCEF: (IWK-SCEF) + MME/SGSN->>UE: 8. NIDD Delivery + Note right of SCEF: (IWK-SCEF) + HSS-->>SCEF: 9. NIDD Submit Response + SCEF-->>SCS/AS: 10. MT NIDD Submit Response + +``` + +Sequence diagram for Mobile Terminated NIDD procedure. Lifelines: UE, MME/SGSN, HSS, ROAMING (IWK-SCEF), SCEF, SCS/AS. The sequence shows the SCS/AS sending an MT NIDD Submit Request to the SCEF, which then interacts with the HSS and MME/SGSN to deliver the data to the UE. + +Figure 5.13.3-1: Mobile Terminated NIDD procedure + +1. If SCS/AS has already activated the NIDD service for a given UE, and has downlink non-IP data to send to the UE, the SCS/AS sends a MT NIDD Submit Request (External Identifier or MSISDN, TLTRI, non-IP data, non- + +IP data sequence number, Reliable Data Service Configuration, Maximum Latency, Priority, PDN Connection Establishment Option) message to the SCEF. The Maximum Latency is an optional field that is used to indicate maximum delay acceptable for downlink data and may be used to configure the buffer duration; a Maximum Latency of 0 indicates that buffering is not allowed. If Maximum Latency is not provided, the SCEF determines the acceptable delay based on local policies. Priority is an optional field that is used to indicate the priority of the non-IP data packet relative to other non-IP data packets. If Priority is not provided, the SCEF determines the acceptable delay based on local policies. Reliable Data Service Configuration is an optional parameter that is used to configure the Reliable Data Service (as defined in clause 4.5.14.3); it may be used to indicate if a Reliable Data Service acknowledgment is requested and port numbers for originator application and receiver application. PDN Connection Establishment Option an optional field that is used to indicate what the SCEF should do if the UE has not established the PDN connection (wait for the UE to establish the PDN connection, respond with an error cause, or send a device trigger; see step 2). If PDN Connection Establishment Option is not provided with the non-IP packet, the SCEF uses the PDN Connection Establishment Option that was provided during NIDD Configuration to decide how to handle the absence of a PDN connection. Non-IP data sequence number is an optional field that refers to earlier MT NIDD requests, it is only included if the purpose of the MT NIDD Submit Request is to replace or purge data that is buffered in the SCEF. If an MT NIDD Submit Request is received with non-IP data and a non-IP data sequence that is equal to a request that is already buffered, then the buffered data is replaced. If an MT NIDD Submit Request is received with no non-IP data and a non-IP data sequence that is equal to a request that is already buffered, then the buffered data is purged. + +The Maximum Latency Parameter provided by the SCS/AS in this procedure is only used by the SCEF to determine the maximum acceptable delay for associated non-IP data and is not propagated further by the SCEF. + +2. The SCEF determines the EPS Bearer Context based on the APN associated with the NIDD configuration and the User Identity. If an SCEF EPS bearer context corresponding to the External Identifier or MSISDN included in step 1 is found, then the SCEF checks whether the SCS/AS is authorised to send NIDD requests and that the SCS/AS has not exceeded the quota (e.g. 200 bytes in 24hrs) or rate (e.g. 10 bytes / hour) of data submission to the SCEF EPS bearer. When determining the quota and the rate of data submissions, the SCEF considers the APN Rate Control pre-configured in the SCEF and the Serving PLMN Rate Control parameter that was received from MME during the T6a/b connection establishment. The SCEF considers already buffered data during the check of whether the quota or the rate was exceeded. If the SCEF receives additional NIDD request(s) while already buffering data, the SCEF considers the non-IP data priority when checking the quota and the rate and deciding whether to buffer the additional non-IP data. If this check is successful and SCEF buffers the additional non-IP data, the SCEF continues with step 5. If this check fails or if the non-IP packet size is larger than then the Maximum Packet Size that was provided to the SCS/AS during NIDD Configuration, the SCEF sends a MT NIDD Submit Response (Cause) with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise, the flow continues with step 3. + +If no SCEF EPS bearer context is found, then the SCEF, depending on PDN Connection Establishment Option, may either: + +- send a MT NIDD Submit Response (Cause) with appropriate error cause value. The flow stops at this step; or +- perform device triggering towards the UE to establish a PDN Connection of type Non-IP to the default APN by using T4 SMS device triggering to a pre-defined SMS Application Port ID (refer to clause 5.2.2). In this case, the SCEF sends a MT NIDD Submit Response (non-IP data sequence, Buffered Indication, Trigger Indication, cause) with an appropriate cause value. The Buffered Indication indicates if the SCEF buffered the non-IP data. The non-IP data sequence number is assigned by the SCEF and may be used by the SCS/AS to overwrite or purge the buffered data at a later time. The Trigger Indication is used to indicate that a trigger was sent in order to establish the PDN connection. If data is not buffered, the flow stops at this step, otherwise, it proceeds to step 6. The SCEF may use Priority to configure the priority of the device trigger and may use Maximum Latency to configure the validity period of the device trigger; or + +NOTE 1: It is left to stage 3 to reserve the SMS Application Port ID number that will be used to carry the trigger to the UE to indicate that the UE should establish a PDN Connection of type Non-IP to the default APN. + +- accept the MT NIDD Submit Request, and execute step 5 with an appropriate cause value, and wait for the UE to perform a procedure (see TS 23.401 [7]) causing the establishment of a PDN connection to the SCEF (see clause 5.13.1.2). If data is not buffered, the flow stops at step 5. + +NOTE 2: The duration for which the SCEF may wait for establishment of a PDN connection to the SCEF for the given UE is implementation dependent. + +3. If an SCEF EPS bearer context corresponding to the External Identifier or MSISDN included in step 1 is found, then the SCEF sends a NIDD Submit Request (User Identity, EPS Bearer ID, SCEF ID, non-IP data, SCEF Wait Time, Maximum Re-transmission time) message toward the MME/SGSN. SCEF Wait Time indicates how long the SCEF is prepared to wait for MME/SGSN response. Maximum Re-transmission indicates how long the SCEF is prepared to re-transmit the message. + +If the IWK-SCEF receives a NIDD Submit Request message from the SCEF, it relays the message to the MME/SGSN. + +4. If the MME/SGSN can immediately deliver the non-IP data to the UE e.g. when UE is already in ECM\_CONNECTED mode, or UE is in ECM\_IDLE and MME/SGSN is able to initiate paging procedure (see TS 23.401 [7]), the procedure proceeds at step 8. + +If the MME/SGSN is aware of the UE being temporarily unreachable, or if the MME/SGSN knows that the UE is not scheduled to be reachable within the SCEF Wait Time, while using power saving functions e.g. UE Power Saving Mode (see clause 4.5.4) or extended idle mode DRX (see clause 4.5.13), then the MME/SGSN may send a NIDD Submit Response (Cause, Requested Re-Transmission Time) message towards the SCEF. The Cause parameter indicates that Non-IP data was not delivered to the UE, as the UE is temporarily not reachable due to power saving but the MME/SGSN will notify the SCEF when the MME/SGSN determines the UE is reachable. The MME/SGSN sets the Not Reachable for NIDD flag in the EMM context for this UE and stores the corresponding SCEF address. If the Maximum Re-transmission Time was included in the Request, the MME may indicate in Requested Re-Transmission time IE the time when the SCEF is expected to re-transmit the DL data to the currently unreachable UE. + +5. The SCEF may send a MT NIDD Submit Response (Requested Re-Transmission time, non-IP data sequence number, Buffered Indication, Cause) to the SCS/AS informing of the received results from the MME/SGSN. If the SCEF receives from the MME/SGSN a Cause value indicating that UE is temporarily not reachable due to power saving, the SCEF can buffer the non-IP data requested at step 3 based on the configuration and proceed to step 6. The Buffered Indication indicates if the SCEF buffered the non-IP data. The non-IP data sequence number is assigned by the SCEF and may be used by the SCS/AS to overwrite or purge the buffered data at a later time. If, in step 2, the SCEF buffered the non-IP data and is waiting for the UE to establish a PDN connection, then the SCEF proceeds to step 7 after T6a Connection Establishment. The Requested Re-Transmission tells the SCS/AS when the SCEF is expected to re-transmit the DL data to the currently unreachable UE. + +6. When the MME/SGSN detects that the UE is reachable (e.g. when coming out of PSM mode by performing TAU/RAU, when initiating MO communication etc.), or when the UE is about to become reachable (e.g. extended idle mode DRX cycle expiring, MME/SGSN anticipating MO communication pattern for the UE etc.), and the MME/SGSN has the Not Reachable for NIDD flag set, then the MME/SGSN sends a NIDD Submit Indication (User Identity) message towards the SCEF. The MME/SGSN clears the Not Reachable for NIDD flag from its EMM context. + +If the MME included the Requested Re-transmission-Time in the NIDD Submit Response, the MME sends a NIDD Submit Indication (User Identity) message towards the SCEF only if the UE becomes reachable before the Requested Re-transmission Time. The MME shall clear the Not Reachable for NIDD flag when the Requested Re-transmission Time expires and the UE has not become reachable yet. + +If the MME/SGSN sends the NIDD Submit Request message towards the SCEF as described in clause 5.13.4 or an Update Serving Node Information Request message towards the SCEF as described in clause 5.13.6, then the MME/SGSN clears the Not Reachable for NIDD flag from its EMM context, but it need not send the NIDD Submit Indication message. If the SCEF receives the NIDD Submit Request message or an Update Serving Node Information Request from the MME/SGSN for this UE, the SCEF may consider it an implicit NIDD Submit Indication, and proceed with step 7. + +7. If the data has not been purged, the SCEF sends a NIDD Submit Request (User Identity, EPS Bearer ID, SCEF ID, non-IP data, SCEF Wait Time, Maximum Re-transmission time) message toward the MME/SGSN. +8. If required, the MME/SGSN pages the UE and delivers the non-IP data to the UE using data transfer via the MME procedure as described in clause 5.3.4B.3 of TS 23.401 [7] or the SGSN procedure as described in clauses 9.3 and 9.6 of TS 23.060 [6]. Depending on operator configuration, the MME/SGSN may generate the necessary accounting information required for charging. +9. If the MME/SGSN was able to initiate step 8, then the MME/SGSN sends a NIDD Submit Response (cause) message towards the SCEF acknowledging the NIDD Submit Request from SCEF received in step 3 or step 7. If + +the eNodeB supports acknowledgements of downlink NIDD delivery and if acknowledgements of downlink NAS data PDUs are enabled in the subscription information for the UE and the eNodeB has acknowledged successful delivery to the MME/SGSN (see clause 5.3.4B.3 of TS 23.401 [7]), the cause is set to 'Success Acknowledged Delivery' otherwise 'Success Unacknowledged Delivery'. If the delivery failed, the cause is 'Unsuccessful delivery'. + +If Reliable Data Service header indicates that acknowledgement is requested, then the UE shall respond with an acknowledgement to the DL data that was received in step 8 following the Mobile Originated NIDD Procedure in clause 5.13.4, steps 1 - 2 and 5. + +NOTE 3: The 'Success Acknowledged Delivery' implies reliable delivery to the UE using RLC acknowledged mode. The 'Success Unacknowledged Delivery' result does not imply the data is successfully received at the UE, but just the MME/SGSN has sent the non-IP data in NAS signalling to the UE. If the UE sends UL data in response to the received DL data in step 8, then it follows the Mobile Originated NIDD Procedure in clause 5.13.4. + +10. The SCEF sends an MT NIDD Submit Response (Reliable Data Service Acknowledgement Indication, Hop-by-Hop Acknowledgment Indication, non-IP data sequence number, Cause). The Reliable Data Service Acknowledgement Indication is used to indicate if an acknowledgement was received from the UE for the MT NIDD. If the Reliable Data Service was requested in step 1, then the MT NIDD Submit Response is sent to the SCS/AS after the acknowledgement is received from the UE or, if no acknowledgement is received, then the MT NIDD Submit Response is sent to the SCS/AS with a cause value indicating that no acknowledgement was received. When the Reliable Data Service was not requested in step 1, the Hop-by-Hop Acknowledgment Indication may be sent to the SCS/AS indicating the result of the Hop-by-Hop acknowledgment with a value of 'Success Acknowledged Delivery', 'Success Unacknowledged Delivery' or 'Unsuccessful delivery'. + +### 5.13.4 Mobile Originated NIDD procedure + +![Sequence diagram of the Mobile Originated NIDD procedure. The diagram shows five steps: 1. UE sends MO non-IP Data to MME/SGSN; 2. MME/SGSN sends NIDD Submit Request to SCEF (via IWK-SCEF in ROAMING); 3. SCEF sends MO NIDD Indication to SCS/AS; 4. SCS/AS sends MO NIDD Acknowledgement to SCEF; 5. SCEF sends NIDD Submit Response to MME/SGSN (via IWK-SCEF in ROAMING).](86e1f8551d4922ea8fa197f96fe4098b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME_SGSN as MME/SGSN + subgraph ROAMING + participant IWK_SCEF as IWK-SCEF + end + participant SCEF + participant SCS_AS as SCS/AS + + Note left of MME_SGSN: 1. MO non-IP Data + MME_SGSN->>SCEF: 2. NIDD Submit Request + Note right of SCEF: 3. MO NIDD Indication + SCEF->>SCS_AS: 3. MO NIDD Indication + Note right of SCS_AS: 4. MO NIDD Acknowledgement + SCS_AS->>SCEF: 4. MO NIDD Acknowledgement + Note left of SCEF: 5. NIDD Submit Response + SCEF->>MME_SGSN: 5. NIDD Submit Response + +``` + +Sequence diagram of the Mobile Originated NIDD procedure. The diagram shows five steps: 1. UE sends MO non-IP Data to MME/SGSN; 2. MME/SGSN sends NIDD Submit Request to SCEF (via IWK-SCEF in ROAMING); 3. SCEF sends MO NIDD Indication to SCS/AS; 4. SCS/AS sends MO NIDD Acknowledgement to SCEF; 5. SCEF sends NIDD Submit Response to MME/SGSN (via IWK-SCEF in ROAMING). + +Figure 5.13.4-1: Mobile Originated NIDD procedure + +1. The UE sends a NAS message with EPS bearer ID and non-IP data, the Reliable Data Service header is included if the Reliable data service is enabled, to the MME as per the procedure described in clause 5.3.4B.2 of TS 23.401 [7] (steps 0 - 2) or the UE sends data to the SGSN (see clause 9.3 and 9.6 of TS 23.060 [6]) on a PDP Context of PDN type Non-IP associated with a T6b interface. +2. The MME/SGSN sends NIDD Submit Request (User Identity, EBI, SCEF ID, non-IP data, MO Exception data counter) message to the SCEF. In the roaming case, the MME/SGSN sends the message to the IWK-SCEF which forwards the message to the SCEF over T7. The MME only includes the MO Exception data counter if the RRC establishment cause is set to "MO exception data" and the UE is accessing via the NB-IoT RAT. The MME maintains the MO Exception Data Counter and sends it to the SCEF as described in TS 29.128 [37]. +3. When the SCEF receives the non-IP data on the T6a/T6b (or T7) interface, and finds an SCEF EPS bearer context and the related T8 Destination Address, then it sends the non-IP data to the SCS/AS that is identified by the T8 Destination address in a MO NIDD Indication (External Identifier or MSISDN, non-IP data, TLTRI, Reliable Data Service Configuration). The Reliable Data Service Configuration is used to provide the SCS/AS with additional information when the Reliable Data Service (as defined in clause 4.5.14.3) is enabled (e.g. + +indicate if an acknowledgement was requested and port numbers for originator application and receiver application). If no T8 Destination address is associated with the UE's PDN connection, the data is discarded, MO NIDD Indication is not sent, and the flow continues at step 5. + +NOTE 1: It is left to stage 3 whether or not the SCEF aggregates MO NIDD Indication messages to the SCS/AS. + +4. The SCS/AS responds to the SCEF with a MO NIDD Acknowledgement (Cause). +5. The SCEF sends NIDD Submit Response to MME/SGSN. In the roaming case, the SCEF sends the message to the IWK-SCEF over T7 and the IWK-SCEF forwards the message to the MME/SGSN over T6a/T6b. If the SCEF cannot deliver the data, e.g. due to missing SCS/AS configuration, the SCEF sends an appropriate error code to the MME/SGSN. If the Reliable Data Service is enabled in the APN configuration and the non-IP packet indicates that an acknowledgment is requested, then the SCEF follows the Mobile Terminated NIDD Procedure in clause 5.13.3, steps 3-9. + +NOTE 2: If the SCS/AS has Downlink data to send (e.g. an application level acknowledgement for the NIDD delivery), it follows the Mobile Terminated NIDD Procedure in clause 5.13.3. + +## 5.13.5 T6a/T6b Connection Release + +### 5.13.5.1 General + +The MME releases the T6a connection(s) towards the SCEF(s) corresponding to the "SCEF ID" indicator for that APN in the following cases: + +- UE-initiated Detach procedure for E-UTRAN, or +- MME-initiated Detach procedure, or +- the HSS-initiated Detach procedure, or +- UE or MME requested PDN disconnection procedure. + +The SGSN releases the T6b connection(s) towards the SCEF(s) corresponding to the "SCEF ID" indicator for that APN in the following cases: + +- Detach Procedures (see clause 6.6 of TS 23.060 [6]), or +- MS and network initiated PDP Deactivation Procedures (see clause 9.2.4 of TS 23.060 [6]). + +The SCEF releases the T6a/b connection(s) towards the MME/SGSN corresponding to PDN connections in the following cases: + +- when an NIDD Authorization Update Request from the HSS indicates that the User is no longer authorized for NIDD, or +- failure of SCEF or failure of SCS/AS connection, or +- based on a request from the SCS/AS, or +- based on removal of the APN associated with the T6a/b connection from the SCEF. + +### 5.13.5.2 MME/SGSN Initiated T6a/T6b Connection Release procedure + +![Sequence diagram of the MME/SGSN Initiated T6a/T6b Connection Release procedure. The diagram shows five lifelines: UE, MME/SGSN, HSS, ROAMING (containing IWK-SCEF), and SCEF. Step 1: A box labeled '1. Detach procedure or PDN disconnection procedure or Deactivation Procedures' spans the UE, MME/SGSN, and HSS lifelines. Step 2: An arrow labeled '2. Delete SCEF Connection Request' goes from the MME/SGSN lifeline, through the IWK-SCEF box, to the SCEF lifeline. Step 3: An arrow labeled '3. Delete SCEF Connection Response' goes from the SCEF lifeline, through the IWK-SCEF box, back to the MME/SGSN lifeline.](a66383962afcd0f0458f0d45c101fabf_img.jpg) + +Sequence diagram of the MME/SGSN Initiated T6a/T6b Connection Release procedure. The diagram shows five lifelines: UE, MME/SGSN, HSS, ROAMING (containing IWK-SCEF), and SCEF. Step 1: A box labeled '1. Detach procedure or PDN disconnection procedure or Deactivation Procedures' spans the UE, MME/SGSN, and HSS lifelines. Step 2: An arrow labeled '2. Delete SCEF Connection Request' goes from the MME/SGSN lifeline, through the IWK-SCEF box, to the SCEF lifeline. Step 3: An arrow labeled '3. Delete SCEF Connection Response' goes from the SCEF lifeline, through the IWK-SCEF box, back to the MME/SGSN lifeline. + +**Figure 5.13.5.2-1: MME/SGSN Initiated T6a/T6b Connection Release procedure** + +1. The UE performs step 1 of the UE-initiated Detach procedure for E-UTRAN (see clause 5.3.8.2.1 TS 23.401 [7]), or the MME performs the MME-initiated Detach procedure (see clause 5.3.8.3 of TS 23.401 [7]), or the HSS performs step 1a of the HSS-initiated Detach procedure (see clause 5.3.8.4 of TS 23.401 [7]), or the UE/MME performs steps 1a-1b of the UE or MME requested PDN disconnection procedure (see clause 5.10.3 of TS 23.401 [7]), or a Detach Procedure specified in clause 6.6 of TS 23.060 [6] is performed, or an MS or network initiated Deactivation Procedure specified in clause 9.2.4 of TS 23.060 [6] is performed, for which the PDN/PDP connection to an SCEF exists. +2. If the MME/SGSN has an active EPS bearer context(s) or PDP Context(s) corresponding to the PDN/PDP connection to the SCEF(s), then for each active EPS bearer context/PDP Context, the MME/SGSN sends a Delete SCEF Connection Request (User Identity, EPS Bearer Identity, SCEF ID, APN) message towards the SCEF. The MME/SGSN deletes the EPS bearer context/PDP Context corresponding to the PDN connection. + +NOTE 1: For further details of T6a/T6b/T7 interactions please refer to Stage 3 specifications. + +NOTE 2: The SGSN uses the NSAPI of the PDP Context used for SCEF communication as an EPS Bearer ID when T6b is used. + +3. The SCEF sends a Delete SCEF Connection Response (User Identity, EPS Bearer Identity, SCEF ID, APN, PCO) message towards the MME/SGSN indicating acceptance of the removal of SCEF Connection information for the UE. The SCEF deletes the SCEF EPS bearer context corresponding to the PDN connection. + +NOTE 3: For further details of T6a/T6b/T7 interactions please refer to Stage 3 specifications. + +If the last PDN Connection of a given APN is being released, the SCEF may send to the MME the current APN Rate Control Status (see clause 4.7.7.3 of TS 23.401 [7]). The MME stores it in the MM context. + +### 5.13.5.3 SCEF Initiated T6a/T6b Connection Release procedure + +![Sequence diagram of the SCEF Initiated T6a/T6b Connection Release procedure. Lifelines: UE, MME/SGSN, HSS, ROAMING (containing IWK-SCEF), and SCEF. The procedure consists of four steps: 1. SCEF sends an HSS Authorization Update or SCS/AS Request or SCEF Congestion message to the HSS. 2. The HSS sends a Delete SCEF Connection Request to the MME/SGSN. 3. The MME/SGSN sends a Delete SCEF Connection Response to the SCEF. 4. The MME/SGSN initiates a Detach Procedure or PDN disconnection procedure or Deactivation Procedures for the UE.](142c0ec898fdb4803450dd39592136c5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME/SGSN + participant HSS + subgraph ROAMING + participant IWK-SCEF + end + participant SCEF + + Note right of SCEF: 1. HSS Authorization Update or SCS/AS Request or SCEF Congestion + SCEF->>HSS: + HSS->>MME/SGSN: 2. Delete SCEF Connection Request + MME/SGSN->>SCEF: 3. Delete SCEF Connection Response + Note left of UE: 4. MME Initiated Detach Procedure or PDN disconnection procedure or Deactivation Procedures + +``` + +Sequence diagram of the SCEF Initiated T6a/T6b Connection Release procedure. Lifelines: UE, MME/SGSN, HSS, ROAMING (containing IWK-SCEF), and SCEF. The procedure consists of four steps: 1. SCEF sends an HSS Authorization Update or SCS/AS Request or SCEF Congestion message to the HSS. 2. The HSS sends a Delete SCEF Connection Request to the MME/SGSN. 3. The MME/SGSN sends a Delete SCEF Connection Response to the SCEF. 4. The MME/SGSN initiates a Detach Procedure or PDN disconnection procedure or Deactivation Procedures for the UE. + +**Figure 5.13.5.3-1: SCEF Initiated T6a/T6b Connection Release procedure** + +1. An NIDD Authorization Update request from the HSS indicates that the User is no longer authorized for NIDD, the SCS/AS indicates that the User's NIDD PDN connection is no longer needed, or the SCEF determines that it is needs to release a T6a/b connection. +2. The SCEF sends a Delete SCEF Connection Request (User Identity, EPS Bearer Identity, SCEF ID) message towards the MME/SGSN. The SCEF deletes the SCEF EPS bearer context corresponding to the PDN connection. + +NOTE 1: For further details of T6a/T6b/T7 interactions please refer to Stage 3 specifications. + +If the last PDN Connection of a given APN is being released, the SCEF may send to the MME the APN Rate Control Status (see clause 4.7.7.3 of TS 23.401 [7]). The MME stores it in the MM context. + +3. The MME/SGSN sends a Delete SCEF Connection Response (User Identity, EPS Bearer Identity, SCEF ID, APN) message towards the SCEF acknowledging the removal of SCEF Connection information for the UE. The MME/SGSN deletes the EPS bearer context/PDP Context corresponding to the PDN connection. + +NOTE 2: For further details of T6a/T6b/T7 interactions please refer to Stage 3 specifications. + +NOTE 3: The SGSN uses the NSAPI of the PDP Context used for SCEF communication as an EPS Bearer ID when T6b is used. + +4. The MME may perform the MME-initiated Detach procedure (see clause 5.3.8.3 of TS 23.401 [7]), or step 1b of the UE or MME requested PDN disconnection procedure (see clause 5.10.3 of TS 23.401 [7]). An SGSN may perform SGSN-Initiated Detach Procedure specified in clause 6.6.2.1 of TS 23.060 [6], or a network initiated Deactivation Procedure specified in clause 9.2.4 of TS 23.060 [6], for which the PDN/PDP connection to an SCEF exists. + +## 5.13.6 Serving node relocation procedure over T6a/T6b + +### 5.13.6.1 General + +Mobility may happen with respect to a non-IP PDN connection via the SCEF as a result of a TAU/RAU procedure. The following procedures apply: + +- Successful TAU/RAU on a new MME/SGSN, + +- Failed TAU/RAU. + +### 5.13.6.2 Successful TAU/RAU procedure with T6a/T6b + +The procedure in Figure 5.13.6.2-1 applies when a T6a/T6b PDN/PDP connection exists for a UE that executes a successful TAU procedure to a new MME or a successful RAU procedure to a new SGSN. + +![Sequence diagram for Figure 5.13.6.2-1: T6a/T6b and successful TAU/RAU procedure. The diagram shows four lifelines: Old MME/SGSN, New MME/SGSN, ROAMING (containing IWK-SCEF), and SCEF. Step 1: Old MME/SGSN sends UE context to New MME/SGSN. Step 2: New MME/SGSN sends Update Serving Node Information Request to SCEF. Step 3: SCEF sends Update Serving Node Information Response to New MME/SGSN.](29997432244f81212ee1e6c94f308f1b_img.jpg) + +``` + +sequenceDiagram + participant OldMME as Old MME/SGSN + participant NewMME as New MME/SGSN + subgraph ROAMING + IWK-SCEF + end + participant SCEF + Note left of OldMME: 1. UE context is sent to the new MME/SGSN including non-IP PDN/PDP connection + OldMME->>NewMME: + NewMME->>SCEF: 2. Update Serving Node Information Request + SCEF-->>NewMME: 3. Update Serving Node Information Response + +``` + +Sequence diagram for Figure 5.13.6.2-1: T6a/T6b and successful TAU/RAU procedure. The diagram shows four lifelines: Old MME/SGSN, New MME/SGSN, ROAMING (containing IWK-SCEF), and SCEF. Step 1: Old MME/SGSN sends UE context to New MME/SGSN. Step 2: New MME/SGSN sends Update Serving Node Information Request to SCEF. Step 3: SCEF sends Update Serving Node Information Response to New MME/SGSN. + +Figure 5.13.6.2-1: T6a/T6b and successful TAU/RAU procedure + +- UE performs a successful TAU/RAU procedure (see TS 23.401 [7] and TS 23.060 [6]) and the new MME/SGSN receives subscription information for a non-IP PDN/PDP connection to an APN that is associated with an "Invoke SCEF Selection" indicator and an associated SCEF ID. +- If the subscription information corresponding to either the default APN for PDN type of "Non-IP" or the UE requested APN includes "Invoke SCEF Selection" indicator, then the new MME/SGSN shall create a PDN/PDP connection to the SCEF or to the IWK-SCEF, using the already allocated EBI. As for the "T6a/T6b Connection Establishment Procedure", clause 5.13.1.2, the new MME/SGSN does so by sending an Update Serving Node Information Request (User Identity, EPS Bearer Identity, SCEF ID, APN, Serving PLMN ID, IMEISV) message towards the SCEF. If the SCEF received the Reachable for NIDD flag for the UE from old MME/SGSN but has yet to receive the NIDD Submit Indication message from the old MME/SGSN, and the SCEF has buffered the Non-IP data, then the SCEF may execute the procedure in clause 5.13.3 starting at step 7. + +NOTE 1: For further details of T6a/T6b interactions please refer to Stage 3 specifications. + +If the IWK-SCEF receives the Update Serving Node Information Request message from the MME/SGSN, it shall forward it to the SCEF. + +- The SCEF creates an SCEF EPS Bearer Context (see clause 5.3.2) for the user identified via User Identity. The SCEF sends Update Serving Node Information Response (User Identity, EPS Bearer Identity, SCEF ID, Cause, NIDD Charging ID) message toward the MME/SGSN confirming establishment of the PDN connection to the SCEF for the UE. If the IWK-SCEF receives the Update Serving Node Information Response message from the SCEF, it shall forward it to the MME/SGSN. + +NOTE 2: For further details of T6a/T6b interactions please refer to Stage 3 specifications. + +### 5.13.7 Void + +### 5.13.8 NIDD Authorisation Update + +Figure 5.13.8-1 illustrates the procedure of updating or revoking an existing NIDD Authorisation. The HSS may initiate the NIDD Authorisation Update procedure with the SCEF to send updated Authorisation information to the SCEF. + +![Sequence diagram for NIDD Authorisation Update procedure. Lifelines: HSS, SCEF, SCS/AS. 1. HSS to SCEF: NIDD Authorisation Update Request. 2. SCEF to HSS: NIDD Authorisation Update Response. 3. SCEF to SCS/AS: NIDD Authorisation Notification Request. 4. SCS/AS to SCEF: NIDD Authorisation Notification Response.](6e9d059430baba0c363e33749f68b107_img.jpg) + +``` + +sequenceDiagram + participant HSS + participant SCEF + participant SCS/AS + Note left of HSS: + HSS->>SCEF: 1. NIDD Authorisation Update Request + SCEF-->>HSS: 2. NIDD Authorisation Update Response + Note right of SCEF: + SCEF->>SCS/AS: 3. NIDD Authorisation Notification Request + SCS/AS-->>SCEF: 4. NIDD Authorisation Notification Response + +``` + +Sequence diagram for NIDD Authorisation Update procedure. Lifelines: HSS, SCEF, SCS/AS. 1. HSS to SCEF: NIDD Authorisation Update Request. 2. SCEF to HSS: NIDD Authorisation Update Response. 3. SCEF to SCS/AS: NIDD Authorisation Notification Request. 4. SCS/AS to SCEF: NIDD Authorisation Notification Response. + +**Figure 5.13.8-1: NIDD Authorisation Update procedure** + +1. The HSS may send an NIDD Authorisation Update Request (IMSI and MSISDN or External Identifier, APN, Result) message to the SCEF to update a user's NIDD authorisation. The HSS shall include in the NIDD Authorisation Update Request the IMSI and either MSISDN or External Identifier or both. The SCEF initiates the SCEF Initiated T6a/T6b Connection Release Procedure. +2. The SCEF sends an NIDD Authorisation Update Response (cause) message to the HSS to acknowledge the authorisation update. If the authorisation is removed, the SCEF should release T6a/T6b connection as specified in clause 5.13.5.3. +3. The SCEF informs the SCS/AS that the User's authorisation status has changed by sending an NIDD Authorisation Notification Request (External Identifier or MSISDN, TLTRI, Result) message to the SCS/AS. +4. The SCS/AS responds to the SCEF with an NIDD Authorisation Notification Response. + +## 5.14 PFD management via SCEF + +### 5.14.1 Procedure for PFD management via SCEF + +This procedure is used by the 3rd Party SCS/AS to manage PFDs into the operator network via SCEF. Figure 5.14.1-1 illustrates the procedure. + +![Sequence diagram for PFD management via SCEF. Lifelines: PFDF, SCEF, SCS/AS. 1. SCS/AS to SCEF: PFD Management Request. 2. SCEF handling (internal). 3. SCEF to PFDF: PFD Management Request. 4. PFDF handling (internal). 5. PFDF to SCEF: PFD Management Response. 6. SCEF to SCS/AS: PFD Management Response.](41fa90d03d7195caa162c74d289817a4_img.jpg) + +``` + +sequenceDiagram + participant PFDF + participant SCEF + participant SCS/AS + Note right of SCS/AS: + SCS/AS->>SCEF: 1. PFD Management Request + Note right of SCEF: 2.SCEF handling + SCEF->>PFDF: 3. PFD Management Request + Note left of PFDF: 4. PFD Handling + PFDF->>SCEF: 5. PFD Management Response + Note right of SCEF: + SCEF->>SCS/AS: 6. PFD Management Response + +``` + +Sequence diagram for PFD management via SCEF. Lifelines: PFDF, SCEF, SCS/AS. 1. SCS/AS to SCEF: PFD Management Request. 2. SCEF handling (internal). 3. SCEF to PFDF: PFD Management Request. 4. PFDF handling (internal). 5. PFDF to SCEF: PFD Management Response. 6. SCEF to SCS/AS: PFD Management Response. + +**Figure 5.14.1-1: procedure for PFD management via SCEF** + +1. The 3rd party SCS/AS sends a PFD Management Request (SCS/AS Identifier, external Application Identifier(s) and one or more sets of PFDs and PFD operation for each Application Identifier, Allowed Delay) message to the SCEF. The external Application Identifier(s) should be provided by an 3rd party SCS/AS that is known at the + +SCEF, so that the 3rd party SCS/AS and the MNO has an SLA in place. PFD operation indicates that the PFD is to be created, updated or removed in the operator's network. The Allowed Delay is an optional parameter. If the Allowed Delay is included, it indicates that the list of PFDs in this request should be provisioned to all the PCEF/TDFs known in the PFDF within the time interval indicated by the Allowed Delay. + +2. Based on operator policies, if the 3rd party SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow it due to the Allowed Delay is too short or other reasons), the SCEF performs step 6 and provides a Cause value appropriately indicating the error. Otherwise, the SCEF translates each external Application Identifier to the corresponding Application Identifier known at the PFDF. +3. The SCEF sends a PFD Management Request message (Application Identifier(s), one or more sets of PFDs and PFD operation for each Application Identifier, Allowed Delay) to the PFDF. +4. The PFDF creates, updates or deletes the list of PFDs for each Application Identifier into the PFDF as requested by the respective PFD operation. +5. The PFDF sends a PFD Management Response (Application Identifier(s), Cause) message to the SCEF to provide the feedback of the handling result for the PFD Management Request. +6. The SCEF sends a PFD Management Response (Cause) message to the 3rd party SCS/AS to provide the feedback of the handling result for the PFD Management Request. + +## 5.14.2 PFD definition + +PFD (Packet Flow Description) is a set of information enabling the detection of application traffic including: + +- PFD id; and +- one or more of the following: + - 3-tuple(s) including protocol, server side IP address and port number; + - the significant parts of the URL to be matched, e.g. host name; + - a Domain name matching criteria and information about applicable protocol(s). + +NOTE 1: Based on the agreement between SCS/AS and mobile operator, the PFD can be designed to convey proprietary extension for proprietary application traffic detection mechanisms. + +NOTE 2: How the PFD(s) are used in service data flow detection is specified in TS 23.203 [27]. + +## 5.15 Procedure for MSISDN-less MO-SMS via T4 + +![Sequence diagram for MSISDN-less MO-SMS via T4 showing interactions between UE, MSC/MME/SGSN, HSS/HLR, SMS-SC/GMSC/IWMSC, MTC-IWF, and SCS.](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MSC as MSC/MME/SGSN + participant HSS as HSS/HLR + participant SMS as SMS-SC/GMSC/IWMSC + participant IWF as MTC-IWF + participant SCS + + UE->>MSC: 1. SMS Submit + MSC->>SMS: 2. MO Forward SM + SMS-->>UE: 3. SMS Submit Report + SMS->>IWF: 4. MO payload delivery Request + IWF->>HSS: 5. Subscriber Information Request + HSS-->>IWF: 6. Subscriber information Respose + IWF->>SCS: 7a. Forward MO payload + SCS-->>IWF: 7b. Ack + IWF-->>SMS: 8. MO payload delivery Response (Status) + SMS-->>UE: 9. SMS Status Report + +``` + +Sequence diagram for MSISDN-less MO-SMS via T4 showing interactions between UE, MSC/MME/SGSN, HSS/HLR, SMS-SC/GMSC/IWMSC, MTC-IWF, and SCS. + +**Figure 5.15-1: MSISDN-less MO-SMS via T4** + +1. UE uses Short Message Mobile Originated procedure as specified in TS 23.040 [12] to delivery small data to SCS/AS. The service centre address points to the SMS-SC which contain the function described in this procedure, the destination SME address is set to short/long code of the SCS/AS, and Application Port ID element of the TP-User-Data field is set to an appropriate value. +2. For MSISDN-less subscription, the MSC/VLR/MME/SGSN/IP-SM-GW uses the dummy MSISDN. This MSISDN and the IMSI of the UE are sent using existing SMS delivery procedure (e.g. MAP MO forward SM operation) to SMS-SC. +3. SMS-SC indicates to UE that it has successfully received the SMS message using existing SMS Submit Report defined in TS 23.040 [12]. +4. SMS-SC uses the destination SME address (long/short code of the SCS/AS) to identify the corresponding MTC-IWF based on a pre-configured mapping table. SMS-SC extracts the SMS payload, Application port ID, and IMSI of the UE and deliver them to MTC-IWF via T4 along with the destination SME address (long/short code of the SCS/AS). +- 5-6. Over S6m, MTC-IWF uses the IMSI of the UE and application port ID to query the HSS/HLR for external ID. +7. Over Tsp, a MTC-IWF forwards the SMS payload, external ID, and Application Port ID to the SCS/AS. The SCS/AS is identified with the destination SME address (long/short code of the SCS/AS) received from step 3. The payload is delivered directly to the SCS/AS, not processed by MTC-IWF. +8. Via T4, MTC-IWF returns a success or failure delivery indication to SMS-SC. + +- SMS-SC indicates success/failure of the delivery of the SMS to the target back to UE using existing SMS Status Report defined in TS 23.040 [12]. + +## 5.16 Procedure for Enhanced Coverage Restriction Control via SCEF + +Figure 5.16-1 shows the procedures for Enhanced Coverage Restriction Control via SCEF. + +![Sequence diagram for Enhanced Coverage Restriction Control via SCEF. The diagram shows interactions between MME/SGSN, HSS, SCEF, and SCS/AS. The process starts with an Enhanced Coverage Request from SCS/AS to SCEF. SCEF performs internal handling and then sends an Enhanced Coverage Request to HSS. HSS performs a set or get operation on the Enhanced Coverage Restriction Parameter. HSS then sends an Insert Subs Data Request to MME/SGSN. MME/SGSN performs the Set Enhanced Coverage Restriction Parameter in MM context. MME/SGSN sends an Insert Subs Data Answer to HSS. HSS sends an Enhanced Coverage Response to SCEF. Finally, SCEF sends an Enhanced Coverage Response (Success/Failure) to SCS/AS.](d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + participant MME/SGSN + + Note right of SCEF: 2. SCEF handling + Note left of HSS: 4. Depending on Request Type, either Set or Get the value of Enhanced Coverage Restriction Parameter + Note right of MME/SGSN: 6. Set Enhanced Coverage Restriction Parameter in MM context + + SCS/AS->>SCEF: 1. Enhanced Coverage Request (Type = Enable/Disable/Status) + SCEF->>HSS: 3. Enhanced Coverage Request + HSS->>MME/SGSN: 5. Insert Subs Data Request + MME/SGSN-->>HSS: 7. Insert Subs Data Answer + HSS->>SCEF: 8. Enhanced Coverage Response + SCEF->>SCS/AS: 9. Enhanced Coverage Response (Success/Failure) + +``` + +Sequence diagram for Enhanced Coverage Restriction Control via SCEF. The diagram shows interactions between MME/SGSN, HSS, SCEF, and SCS/AS. The process starts with an Enhanced Coverage Request from SCS/AS to SCEF. SCEF performs internal handling and then sends an Enhanced Coverage Request to HSS. HSS performs a set or get operation on the Enhanced Coverage Restriction Parameter. HSS then sends an Insert Subs Data Request to MME/SGSN. MME/SGSN performs the Set Enhanced Coverage Restriction Parameter in MM context. MME/SGSN sends an Insert Subs Data Answer to HSS. HSS sends an Enhanced Coverage Response to SCEF. Finally, SCEF sends an Enhanced Coverage Response (Success/Failure) to SCS/AS. + +**Figure 5.16-1: Procedure for Enhanced Coverage Restriction Control via SCEF** + +- The SCS/AS sends an Enhanced Coverage Request (External Identifier or MSISDN, SCS/AS Identifier, Request Type, Enhanced Coverage Restriction Data, MTC Provider Information) message to the SCEF. Request Type indicates if the request is to query the status of, or to enable, or to disable the enhanced coverage restriction. Enhanced Coverage Restriction Data provides data related to the Enhanced Coverage Restriction. Enhanced Coverage Restriction Data is only present if Request Type is to either enable or disable the enhanced coverage restriction. +- The SCEF stores the SCS/AS Identifier. The SCEF assigns an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Enhanced Coverage Request is malformed or the SCS/AS has exceeded its quota or rate of submitting Enhanced Coverage requests, the SCEF performs step 9 and provides a Cause value appropriately indicating the failure result. +- The SCEF sends an Enhanced Coverage Request (External Identifier or MSISDN, SCEF ID, SCEF Reference ID, Type, MTC Provider Information) message to the HSS. + +NOTE 1: The MTC Provider Information in step 1 is an optional parameter. The SCEF can validate the provided MTC Provider Information and override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information, if not present in step 1, is left to implementation (e.g. based on the requesting SCS/AS). + +4. The HSS examines the Enhanced Coverage Request message, e.g. with regard to the existence of External Identifier or MSISDN, whether any included parameters are in the range acceptable for the operator, whether the Enhanced Coverage restriction is supported by the serving MME/SGSN. If this check fails the HSS follows step 8 and provides a Cause value indicating the reason for the failure condition to the SCEF. + +If the Request Type is to get the current status of enhanced coverage HSS retrieves the value and procedure follows at Step 8. Else If the Type is to enable or to disable the enhanced coverage, HSS sets Enhanced Coverage Restricted parameter to the appropriate value and the procedure continues at step 5. + +5. If required by the specific Enhanced Coverage Request Type and when Enhanced Coverage is supported by the serving MME/SGSN, the HSS sends an Insert Subscriber Data Request (Type, SCEF ID, SCEF Reference ID) message to the MME/SGSN. +6. Based on operator policies, the MME/SGSN may reject the request (e.g. overload or HSS has exceeded its quota or rate of submitting enhanced coverage requests defined by an SLA). + +The MME/SGSN updates Enhanced Coverage Restricted parameters in the MME/SGSN context. + +The MME/SGSN will transfer the Enhanced Coverage Restricted parameters stored as part of its context information during MME/SGSN change. + +NOTE 2: UE is informed of the updated Enhanced Coverage Restricted parameters value at next TAU/RAU, or based on the local policy, network can detach the UE indicating re-attach is required. + +7. If the Enhanced Coverage restriction is updated successful, the MME/SGSN sends an Insert Subscriber Data Answer (Cause) message to the HSS. MME/SGSN may include the Enhanced Coverage Restricted parameter in the Insert Subscriber Data Answer message. +8. The HSS sends an Enhanced Coverage Response (SCEF Reference ID, Cause) message to the SCEF. HSS includes result = success/failure and in the case of success may include Enhanced Coverage Restriction Data. + +In the case of UE mobility, the HSS determines whether the new MME/SGSN supports Enhanced Coverage restriction. + +9. The SCEF sends an Enhanced Coverage Response (Cause, Enhanced Coverage Restriction Data) message to the SCS/AS. Cause indicates success or failure. If in step 1 the Enhanced Coverage Request message is sent to query the status of Enhanced Coverage Restricted, then Enhanced Coverage Restriction Data is included (in the case of success) in the Enhanced Coverage Response message. + +## 5.17 Procedures for accessing MTC-IWF Functionality via SCEF + +### 5.17.1 Device triggering procedure via T8 + +Figure 5.17.1-1 shows the procedure for Triggering via T8. + +![Sequence diagram of device triggering procedure via T8. Lifelines: SMS-SC/GMSC/IWMSC, HSS, MTC-IWF, SCEF, SCS/AS. The sequence starts with SCS/AS determining a trigger is needed, followed by a Trigger Submit Request to SCEF, a Trigger Submit to MTC-IWF, a Trigger Submit Confirmation from SCEF to SCS/AS, a Trigger Delivery to MTC-IWF, and finally a Trigger Delivery Report from SCEF to SCS/AS.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant MTC-IWF + participant HSS + participant SMS-SC/GMSC/IWMSC + + Note right of SCS/AS: 1. Determine Trigger Needed + SCS/AS->>SCEF: 2. Trigger Submit Request + Note over SMS-SC/GMSC/IWMSC, HSS, MTC-IWF: 3. Trigger Submit + SCEF->>SCS/AS: 4. Trigger Submit Confirmation + Note over SMS-SC/GMSC/IWMSC, HSS, MTC-IWF: 5. Trigger Delivery + SCEF->>SCS/AS: 6. Trigger Delivery Report + +``` + +Sequence diagram of device triggering procedure via T8. Lifelines: SMS-SC/GMSC/IWMSC, HSS, MTC-IWF, SCEF, SCS/AS. The sequence starts with SCS/AS determining a trigger is needed, followed by a Trigger Submit Request to SCEF, a Trigger Submit to MTC-IWF, a Trigger Submit Confirmation from SCEF to SCS/AS, a Trigger Delivery to MTC-IWF, and finally a Trigger Delivery Report from SCEF to SCS/AS. + +**Figure 5.17.1-1: Device triggering procedure via T8** + +1. The SCS/AS determines the need to trigger the device. If the SCS/AS has no contact details for the SCEF, it may determine the IP address(es)/port(s) of the SCEF by performing a DNS query using the External Identifier or using a locally configured SCEF identifier. +2. The SCS/AS sends the Trigger Submit Request (External Identifier or MSISDN, SCS Identifier, trigger reference number, validity period, priority, Application Port ID and trigger payload) message to the SCEF. The SCEF assigns a TLTRI to the Trigger Submit Request. +3. The SCEF/MTC-IWF executes steps 3-6 of the Device triggering over Tsp procedure of clause 5.2.1, followed by steps 1-2 of the Trigger Delivery using T4 procedure of clause 5.2.2. +4. The SCEF sends a Trigger Submit Confirmation (TLTRI, Cause) to the SCS/AS to confirm that the Device Trigger Request has been accepted for delivery to the UE. +5. Steps 4-9 of the Trigger Delivery using T4 procedure of clause 5.2.2 are executed. In step 9 of the Trigger Delivery using T4 procedure, the SCEF/MTC-IWF receives the Message Delivery Report from the SMS/SC. +6. The SCEF sends the Trigger Delivery Report (TLTRI, cause) message to the SCS/AS with a cause value indicating the trigger delivery outcome (e.g. succeeded, unknown or failed and the reason for the failure). + +## 5.17.2 Device triggering recall/replace procedures via T8 + +Figure 5.17.2-1 shows the procedures for recalling and replacing triggers over T8. + +![Sequence diagram for triggering recall/replace via T8. Lifelines: SMS-SC/GMSC/IWMSC, HSS, MTC-IWF, SCEF, SCS/AS. The sequence starts with a '1. Trigger Modify Request' from SCS/AS to SCEF. SCEF then sends a '2. Trigger Recall/Replace' message to MTC-IWF. Finally, SCEF sends a '3. Trigger Modify Response' back to SCS/AS.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant MTC-IWF + participant HSS + participant SMS-SC/GMSC/IWMSC + Note left of SCEF: 1. Trigger Modify Request + SCEF->>MTC-IWF: 2. Trigger Recall/Replace + Note right of SCEF: 3. Trigger Modify Response + SCEF->>SCS/AS: 3. Trigger Modify Response + +``` + +Sequence diagram for triggering recall/replace via T8. Lifelines: SMS-SC/GMSC/IWMSC, HSS, MTC-IWF, SCEF, SCS/AS. The sequence starts with a '1. Trigger Modify Request' from SCS/AS to SCEF. SCEF then sends a '2. Trigger Recall/Replace' message to MTC-IWF. Finally, SCEF sends a '3. Trigger Modify Response' back to SCS/AS. + +Figure 5.17.2-1: Procedure for triggering recall/replace via T8 + +1. The SCS/AS determines that it needs to recall/replace a trigger message that it has previously submitted. The SCS/AS sends Trigger Modify Request (SCS Identifier, TLTRI, action type, new trigger reference number, new validity period, new priority, new Application Port ID, and new trigger payload) message with action type set to "Trigger Recall Request" or "Trigger Replace Request". The SCS needs to include a new trigger reference number, new validity period, new priority, new Application Port ID and new trigger payload for trigger replace request only. The SCEF uses the TLTRI to determine the trigger reference number which was assigned to the previously submitted trigger message that the SCS/AS wants to cancel. +2. The SCEF/MTC-IWF executes steps 2-4 of the Device trigger recall/replace procedure over Tsp of clause 5.2.3.1. +3. The SCEF indicates trigger recall/replace success or failure in the Trigger Modify Response (result) message to the SCS/AS. + +### 5.17.3 Procedure for MSISDN-less MO-SMS via T8 + +Figure 5.17.3-1 shows the procedures for MSISDN-less MO-SMS via T8. + +![Sequence diagram for MSISDN-less MO-SMS via T8. Lifelines: UE, HSS, SMS-SC/GMSC/IWMSC, MTC-IWF, SCEF, SCS/AS. The sequence starts with '1. SMS Submit' from UE to SMS-SC/GMSC/IWMSC. SMS-SC/GMSC/IWMSC sends '2. Retrieve Subscriber Information' to HSS. HSS sends '3. MO SMS Submit Request' to SCEF. SCEF sends '4. MO SMS Submit Response' back to HSS. Finally, HSS sends '5. SMS Report' to SMS-SC/GMSC/IWMSC.](fae02fa1dac97fc5f19a7b85d20df290_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HSS + participant SMS-SC/GMSC/IWMSC + participant MTC-IWF + participant SCEF + participant SCS/AS + Note left of SMS-SC/GMSC/IWMSC: 1. SMS Submit + SMS-SC/GMSC/IWMSC->>HSS: 2. Retrieve Subscriber Information + HSS->>SCEF: 3. MO SMS Submit Request + SCEF->>HSS: 4. MO SMS Submit Response + Note right of HSS: 5. SMS Report + HSS->>SMS-SC/GMSC/IWMSC: 5. SMS Report + +``` + +Sequence diagram for MSISDN-less MO-SMS via T8. Lifelines: UE, HSS, SMS-SC/GMSC/IWMSC, MTC-IWF, SCEF, SCS/AS. The sequence starts with '1. SMS Submit' from UE to SMS-SC/GMSC/IWMSC. SMS-SC/GMSC/IWMSC sends '2. Retrieve Subscriber Information' to HSS. HSS sends '3. MO SMS Submit Request' to SCEF. SCEF sends '4. MO SMS Submit Response' back to HSS. Finally, HSS sends '5. SMS Report' to SMS-SC/GMSC/IWMSC. + +Figure 5.17.3-1: Procedure for MSISDN-less MO-SMS via T8 + +1. The UE sends an SMS to the SCS/AS. The UE, MSC/MME/SGSN, and SMS-SC execute steps 1 and 2 of the MSISDN-less MO-SMS via T4 procedure of clause 5.15. SMS-SC uses the destination SME address (long/short code of the SCS/AS) to identify the corresponding SCEF based on a pre-configured mapping table. SMS-SC extracts the SMS payload, Application port ID, and IMSI of the UE and deliver them to SCEF via T4 along with the destination SME address (long/short code of the SCS/AS). +2. The SCEF/MTC-IWF executes steps 4-5 of the MSISDN-less MO-SMS via T4 procedure of clause 5.15. +3. The SCEF sends a MO SMS Submit Request (SMS payload, external ID, and Application Port ID) to the SCS/AS. The SCS/AS is identified with the destination SME address (long/short code of the SCS/AS) received from step 1. The payload is delivered directly to the SCS/AS, it is not processed by SCEF. +4. The SCS/AS sends a MO SMS Submit Response to the SCEF. +5. The SCEF/MTC-IWF executes steps 7 of the MSISDN-less MO-SMS via T4 procedure of clause 5.15. The SMS Delivery or failure report is delivered to the UE as shown in step 8 of the MSISDN-less MO-SMS via T4 procedure of clause 5.15. + +## 5.18 Procedure for Network Parameter Configuration via SCEF + +![Sequence diagram for Network Parameter Configuration via SCEF. Lifelines: MME/SGSN, HSS, SCEF, SCS/AS. The process involves a request from SCS/AS to SCEF, then to HSS, followed by responses and handling steps back through the chain, ending with a monitoring indication and a sub-clause procedure.](23aceb0e7d3c1a644294899d9047df05_img.jpg) + +``` + +sequenceDiagram + participant SCS/AS + participant SCEF + participant HSS + participant MME/SGSN + + Note right of SCEF: 2. SCEF Handling + Note right of HSS: 4. HSS Handling + Note right of MME/SGSN: 8. MME/SGSN Handling + + SCS/AS->>SCEF: 1. T8 Set Suggested Network Configuration Request + SCEF->>HSS: 3. Set Suggested Network Configuration Request + HSS-->>SCEF: 5. Set Suggested Network Configuration Response + SCEF-->>SCS/AS: 6. T8 Set Suggested Network Configuration Response + HSS->>MME/SGSN: 7. Insert Subscriber Data Request + MME/SGSN-->>HSS: 9. Insert Subscriber Data Answer + HSS-->>SCEF: 10. Set Suggested Network Configuration Response + HSS-->>SCEF: 10a. Monitoring Indication + SCEF-->>SCS/AS: 11. T8 Set Suggested Network Configuration Response + Note right of SCEF: 12. Step 2-5 of Network-Initiated Explicit Monitoring Event Deletion Procedure (subclause 5.6.9) + +``` + +Sequence diagram for Network Parameter Configuration via SCEF. Lifelines: MME/SGSN, HSS, SCEF, SCS/AS. The process involves a request from SCS/AS to SCEF, then to HSS, followed by responses and handling steps back through the chain, ending with a monitoring indication and a sub-clause procedure. + +Figure 5.18-1: Procedure for Network Parameter Configuration via SCEF + +1. The SCS/AS sends a T8 Set Suggested Network Configuration Request (External Identifier or MSISDN or External Group Identifier, SCS/AS Identifier, Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets, Group Reporting Guard Time, TLTRI for Deletion, TLTRI for Update, the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added for an existing group event, operation indication (cancellation or addition), MTC Provider Information) message to the SCEF to request that the network consider setting Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets to the requested value(s); they are all optional fields. If a new monitoring event is being configured, the SCEF assigns a TLTRI to the T8 Set Suggested Network Configuration Request. If the SCS/AS wants to perform deletion of a previously configured network parameter(s), then it shall include TLTRI for Deletion. + +If the SCE/AS decides to cancel or add the monitoring event for certain UEs (i.e. one individual UE or a sub-set of UEs) in a group of UEs for which there is a configured Monitoring Event, the SCS/AS can send Monitoring Request message including the TLTRI for Update corresponding to the existing monitoring event configuration and the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added with the operation indication which is either cancellation or addition. + +2. The SCEF stores the TLTRI and assigns it to an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Set Suggested Network Configuration Request is malformed, the SCEF skips steps 3-10 and provides a Cause value appropriately indicating the error. The SCEF checks whether the parameters are within the range defined by operator policies. If one or more of the parameters are not within range, then, based on operator policies, the SCEF may either reject the request by skipping steps 3-10 and providing a cause value that indicates which parameters are out of range, discard the value(s) that are out of range and proceed with the flow, or select different value(s) that are in range and proceed with flow. If the SCEF decides on using values, for the parameters provided in step 1, different to the ones provided by the SCS/AS, then the SCS/AS is informed of it in step 11. If the SCEF received a TLTRI for Update, the SCEF looks up the SCEF context pointed to by the TLTRI for Update to derive the related SCEF Reference ID. If the SCEF received a TLTRI for Deletion, the SCEF looks up the SCEF context pointed to by the TLTRI for Deletion to derive the related SCEF Reference ID for Deletion. +3. The SCEF sends a Set Suggested Network Configuration Request (External Identifier or MSISDN or External Group Identifier, SCEF ID, SCEF Reference ID, Maximum Latency (if provided), Maximum Response Time (if provided), Suggested Number of Downlink Packets (if provided), Group Reporting Guard Time, SCEF Reference ID for Deletion, the External Identifier(s) or MSISDN(s) of the individual member UE(s) to be cancelled or added, operation indication (cancellation or addition), MTC Provider Information) message to the HSS to configure the parameters on the HSS and on the MME/SGSN. If the External Group Identifier is included, External Identifier or MSISDN shall be ignored. + +NOTE 1: The MTC Provider Information in step 1 is an optional parameter. The SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information, if not present in step 1, is left to implementation (e.g. based on the requesting SCS/AS). + +4. The HSS examines the Set Suggested Network Configuration Request message, e.g. with regard to the existence of External Identifier or MSISDN or External Group Identifier or whether the included parameters are in the range acceptable for the operator, if this check fails the HSS either skips steps 5-9 and provides a Cause value indicating the reason for the failure condition to the SCEF or selects different value(s) that are in range and proceeds with flow. If the HSS decides on using values, for the parameters provided in step 3, different to the ones provided by the SCEF, then the SCEF is informed of it in step 10. In addition, the HSS sets the subscribed periodic RAU/TAU timer using the value of Maximum Latency, if it is provided. + +If the Enhanced Multiple Event Monitoring feature is not supported and if the subscribed periodic RAU/TAU timer was previously set by a Monitoring Request then, depending on operator configuration, the flow skips steps 5-9 and the HSS rejects the Network Configuration Request with an appropriate Cause indicating the failure condition or accepts the request. In the case that the HSS accepts this request, the HSS cancels the previously accepted Monitoring Request. If SCEF Reference ID for Deletion was provided, the HSS deletes the network parameter configuration identified by the SCEF Reference ID for Deletion. If the previously accepted Monitoring Request is associated with a group of UEs and the HSS is not cancelling the previously accepted Monitoring Request for all UEs in the group, then the HSS provides the indicated UEs (External Identifier or MSISDN) to the SCEF in step 10. + +If the Enhanced Multiple Event Monitoring feature is supported, and if the subscribed periodic RAU/TAU Timer, or Active Time, or Suggested number of downlink packets, or any combination were previously set by a different Monitoring Request or Network Parameter Configuration for the same UE, as long as the Maximum Latency (if received), Maximum Response Time (if received) and Suggested number of downlink packets (if received) are within the range defined by operator policies, the HSS shall accept the request as follows: + +- If the newly received Maximum Latency is lower than the provided subscribed periodic RAU/TAU timer, the HSS shall set the subscribed periodic RAU/TAU timer using the newly received Maximum Latency. +- If the newly received Maximum Response Time is higher than the provided subscribed Active Time (i.e. previously provided Maximum Response Time), the HSS shall set the subscribed Active Time using the newly received Maximum Response Time. +- If Suggested number of downlink packets is newly received, the HSS shall add the newly received value to the currently used value of Suggested number of downlink packets if the aggregated value is within the operator defined range. If the aggregated value is not within the operator defined range, the HSS shall set the subscribed Suggested number of downlink packets according to operator defined range. + +The HSS may notify the SCEF (which then notifies the SCS/AS) of the actual value of Maximum Latency and Maximum Response Time that are being applied in the 3GPP network. + +5. For group based processing (if the HSS received the Set Suggested Network Configuration Response with an External Group Identifier), the HSS sends a Set Suggested Network Configuration Response (SCEF Reference ID, SCEF Reference ID for Deletion, Cause) message to the SCEF to acknowledge acceptance of the Set Suggested Network Configuration Request before beginning the processing of individual UEs indicating that Group processing is in progress. +6. For group based processing (if the SCEF received the T8 Set Suggested Network Configuration Response with an External Group Identifier), the SCEF sends a T8 Set Suggested Network Configuration Response (TLTRI, Cause) message to the SCS/AS. The Cause value indicates progress of Group processing request. +7. If the Enhanced Multiple Event Monitoring feature is not supported and the HSS accepts new monitoring event configuration and cancels the existing monitoring event configuration, the HSS sends an Insert Subscriber Data Request (newly received Maximum Response Time (if provided), subscribed periodic RAU/TAU timer (if modified), newly received Suggested Number of Downlink Packets (if provided)) message to the MME/SGSN for the individual UE or for each individual group member UE. When HSS accepts new monitoring event configuration for the indicated UEs in step 4 above, for each indicated UE, the HSS sends such Insert Subscriber Data Request message to the MME/SGSN. When HSS removes a previously configured Monitoring Event for the indicated UEs in step 4 above, the HSS also deletes the previously configured Monitoring Event in the MME/SGSN, if applicable. + +If the Enhanced Multiple Event Monitoring feature is supported, the HSS sends an Insert Subscriber Data Request (Maximum Response Time (if modified), subscribed periodic RAU/TAU timer (if modified), newly received Suggested Number of Downlink Packets (if the newly received Suggested number of downlink packets is higher than the provided Suggested number of downlink packets)) message to the MME/SGSN for the individual UE or for each individual group member UE. + +If the Set Suggested Network Configuration Request message is for a group of UEs, the HSS sends an Insert Subscriber Data Request message per UE to all the MME/SGSN(s) serving the members of the group. If the HSS received a SCEF Reference ID for Deletion in step 3, the HSS shall stop using the provisioned values and determine the parameters that it notifies to the MME/SGSN as in the case when no externally provisioned parameters apply. + +8. The MME/SGSN verifies the request, e.g. if the parameters are covered by a roaming agreement when the request is from another PLMN. If this check fails, the MME/SGSN follows step 9 and provides a Cause value indicating the reason for the failure condition to the HSS. Based on operator policies, the MME/SGSN may also reject the request due to other reasons (e.g. overload or HSS has exceeded its quota or rate of submitting requests defined by an SLA). + +If the subscribed periodic RAU/TAU timer was modified, at every subsequent TAU/RAU procedure, the MME/SGSN applies the subscribed periodic RAU/TAU timer. + +NOTE 2: The MME/SGSN will transfer the parameters stored as part of its context information during an MME/SGSN change. + +9. The MME/SGSN sends an Insert Subscriber Data Answer (Cause) message to the HSS. +10. For single UE processing (if the HSS received the Set Suggested Network Configuration Response without an External Group Identifier), the HSS sends Set Suggested Network Configuration Response (SCEF Reference ID, SCEF Reference ID for Deletion, Maximum Response Time (if modified), Maximum Latency (if modified), Suggested Number of Downlink Packets (if modified), Cancelled SCEF Reference ID, Cause) message to the SCEF to acknowledge acceptance or indicate the rejection of the Set Suggested Network Configuration Request. If the HSS modified any of the parameters that were provided in step 3, the modified values are provided to the SCEF. + +For group based processing, if the Group Reporting Guard Time was provided in the Request, the HSS accumulates multiple responses for the UEs of the group within the Group Reporting Guard Time. After the Group Reporting Guard Time expiration, the HSS sends a Set Suggested Network Configuration Response (SCEF Reference ID, SCEF Reference ID for Deletion, Cause, list of (External Identifier or MSISDN, Cancelled SCEF Reference ID, Cause)) with the accumulated responses. The HSS includes UE identity(ies) and a Cause value indicating the reason for the failure in the message if the monitoring configuration of the group member failed. + +If the HSS cancelled Monitoring Event(s) for UE(s) in step 4 and the cancelled Monitoring Event(s) is subscribed by the SCEF which is the same as the one sending the Set Suggested Network Configuration Request at step 1, the HSS includes the SCEF Reference ID of the cancelled Monitoring Event(s) and reason for cancellation event(s) in the Set Suggested Network Configuration response message, or Monitoring Indication message if step 5 is executed already. If the HSS, in step 4 above, decides to cancel Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS also includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +If the HSS, in step 4 above, decides to add Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +- 10a. If the HSS cancelled a Monitoring Event(s) for UE in step 4 and the cancelled Monitoring Event(s) is subscribed by the SCEF which is different from the SCEF sending the Set Suggested Network Configuration Request at step 1, the HSS sends the Monitoring Indication message towards the SCEF which subscribed the cancelled Monitoring Event(s) and includes SCEF Reference ID of a cancelled Monitoring Event(s) and reason of cancellation. If the HSS, in step 4 above, decides to cancel Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS also includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +If the HSS, in step 4 above, decides to add Monitoring Event for indicated UEs (i.e. one individual UE or a sub-set of UEs) in the group of UEs for which there was a previously configured Monitoring Event, the HSS includes the External Identifier or MSISDN of these indicated UEs towards the SCEF. + +11. For single UE processing (if the SCEF received the T8 Set Suggested Network Configuration Response without an External Group Identifier), the SCEF sends a T8 Set Suggested Network Configuration Response (TLTRI, Maximum Response Time (if modified), Maximum Latency (if modified), Suggested Number of Downlink Packets (if modified), Cause) message to the SCS/AS. If the SCEF or HSS modified any of the parameters that were provided in step 1, the modified values are provided to the SCS/AS. If the SCEF discarded any of the parameters that were provided in step 1, the cause value indicates which values were discarded. + +For group based processing, SCEF sends a T8 Set Suggested Network Configuration Response (TLTRI, Maximum Response Time (if modified), Maximum Latency (if modified), Suggested Number of Downlink Packets (if modified), Cause, list of (External Identifier or MSISDN, Cause)) with the accumulated responses received from the HSS in step 10. If the SCEF or HSS modified any of the parameters that were provided in step 1, the modified values are provided to the SCS/AS. If the SCEF discarded any of the parameters that were provided in step 1, the cause value indicates which values were discarded. + +12. If the SCEF received Cancelled SCEF Reference ID in step 10 or 10a, the steps 2-5 of Network-initiated Explicit Monitoring Event Deletion procedure defined in clause 5.6.9 are performed with the TLTRI corresponding to the Cancelled SCEF Reference ID. + +## 5.19 RACS information provisioning procedures + +### 5.19.1 General + +This clause specifies procedures for provisioning of UCMF with RACS related information from SCS/AS, either via SCEF or directly. Specification of these procedures does not preclude other methods of UCMF provisioning being used, e.g. O&M. + +### 5.19.2 RACS information provisioning procedures via SCEF + +This procedure is used by SCS/AS to add, update or delete UE radio access capability entries in the UCMF using the protocol specified in TS 29.122 [44] for the SCEF northbound API and the protocol defined in TS 29.675 [49] for the UCMF northbound API. Figure 5.19.2-1 illustrates the procedure. + +![Sequence diagram illustrating the RACS information provisioning procedure via SCEF. The diagram shows three participants: UCMF, SCEF, and SCS/AS. The sequence of messages is: 1. SCS/AS sends a Radio Capability Entry Request to SCEF; 2. SCEF handles the request; 3. SCEF sends a Radio Capability Entry Request to UCMF; 4. UCMF handles the request; 5. UCMF sends a Radio Capability Entry Response to SCEF; 6. SCEF sends a Radio Capability Entry Response to SCS/AS.](5c834b7b0f3ad30428fe3d02926b225b_img.jpg) + +``` +sequenceDiagram + participant SCS/AS + participant SCEF + participant UCMF + Note right of SCEF: 2. SCEF handling + Note right of UCMF: 4. UCMF handling + SCS/AS->>SCEF: 1. Radio Capability Entry Request + SCEF->>UCMF: 3. Radio Capability Entry Request + UCMF->>SCEF: 5. Radio Capability Entry Response + SCEF->>SCS/AS: 6. Radio Capability Entry Response +``` + +Sequence diagram illustrating the RACS information provisioning procedure via SCEF. The diagram shows three participants: UCMF, SCEF, and SCS/AS. The sequence of messages is: 1. SCS/AS sends a Radio Capability Entry Request to SCEF; 2. SCEF handles the request; 3. SCEF sends a Radio Capability Entry Request to UCMF; 4. UCMF handles the request; 5. UCMF sends a Radio Capability Entry Response to SCEF; 6. SCEF sends a Radio Capability Entry Response to SCS/AS. + +**Figure 5.19.2-1: RACS information provisioning procedure via SCEF** + +1. The SCS/AS sends a Radio Capability Entry Request ((list of) UE Radio Capability ID(s), UE radio access capability(s) set with its coding format(s) for each UE radio Capability ID, one (list of) IMEI/TAC values(s) for each UE Radio Capability ID, action) message to the SCEF. The action indicates add/modify/delete operation for the UE Radio Capability ID and UE radio access capability. + +NOTE: The UE radio access capability for each UE radio Capability ID can be in one coding format or both the coding formats as defined in TS 36.331 [50] or TS 38.331 [51]. + +2. The SCEF may check whether the UE Radio Capability ID is within the allowed list of manufacturers according to local policy. If the checking fails, step 6 is executed with error response. +3. The SCEF sends a Radio Capability Entry Request ((list of) UE Radio Capability ID(s), UE radio access capability(s) set with its coding format(s) for each UE radio Capability ID, one (list of) IMEI/TAC values(s) for each UE Radio Capability ID, action) message to the UCMF. +4. The UCMF creates, updates or deletes the UE radio access capability entry (or entries) for the indicated UE Radio Capability ID(s). The UCMF shall ensure that for the same UE Radio Capability ID, only one UE radio access capability entry in one or both the coding formats exists. +5. The UCMF sends a Radio Capability Entry Response (Cause) message to the SCEF. +6. The SCEF sends a Radio Capability Entry Response (Cause) message to the SCS/AS. + +### 5.19.3 RACS information provisioning procedures via T9a + +This procedure is used by SCS/AS to add, update or delete UE radio access capability entries in the UCMF using the protocol defined in TS 29.675 [49]. Figure 5.19.3-1 illustrates the procedure. + +![Sequence diagram illustrating the RACS information provisioning procedure via T9a. The diagram shows two lifelines: UCMF and SCS/AS. The sequence of messages is: 1. Radio Capability Entry Request (SCS/AS to UCMF), 2. UCMF handling (internal UCMF process), and 3. Radio Capability Entry Response (UCMF to SCS/AS).](868ee7df1ec851f132ccf8c390de76a8_img.jpg) + +``` +sequenceDiagram + participant SCS/AS + participant UCMF + Note right of UCMF: 2. UCMF handling + SCS/AS->>UCMF: 1. Radio Capability Entry Request + UCMF-->>SCS/AS: 3. Radio Capability Entry Response +``` + +Sequence diagram illustrating the RACS information provisioning procedure via T9a. The diagram shows two lifelines: UCMF and SCS/AS. The sequence of messages is: 1. Radio Capability Entry Request (SCS/AS to UCMF), 2. UCMF handling (internal UCMF process), and 3. Radio Capability Entry Response (UCMF to SCS/AS). + +**Figure 5.19.3-1: RACS information provisioning procedure via T9a** + +1. The SCS/AS sends a Radio Capability Entry Request ((list of) UE Radio Capability ID(s), UE radio access capability(s) set with its coding format(s) for each UE radio Capability ID, one (list of) IMEI/TAC values(s) for each UE Radio Capability ID, action) message to the UCMF. The action indicates add/modify/delete operation for the UE Radio Capability ID and UE radio access capability. +- NOTE: The UE radio access capability for each UE radio Capability ID can be in one coding format or both the coding formats as defined in TS 36.331 [50] or TS 38.331 [51]. +2. The UCMF creates, updates or deletes the UE radio access capability entry (or entries) for the indicated UE Radio Capability ID(s). The UCMF shall ensure that for the same UE Radio Capability ID, only one UE radio access capability entry in one or both the coding formats exists. + 3. The UCMF sends a Radio Capability Entry Response (Cause) message to the SCS/AS. + +## Annex A (informative): MTC Deployment Scenarios + +In the indirect and hybrid models, the deployment of a SCS may be inside or outside the operator domain as illustrated in figures A-1 and A-2. When the SCS is part of the operator domain (figure A-1 C and figure A-2), the SCS is considered a mobile operator internal network function, is operator controlled, and may provide operator value-added services. In this case, security and privacy protection for communication between the MTC-IWF and SCS is optional. When the SCS is deployed outside the operator domain (figure A-1 B and A-2), the SCS is MTC Service Provider controlled. In this case, security and privacy protection for communication between the MTC-IWF and SCS is needed. In the direct model (figure A-1 A), there may not be an external or internal SCS in the communication path. + +![Figure A-1: Deployment scenarios for direct and indirect model. The diagram shows three models: A. Direct Model, B. Indirect Model (MTC Service Provider Controlled), and C. Indirect Model (Mobile Network Operator Controlled). Each model shows the connection between an Application Server, a SCS (if applicable), an Operator Network, and a UE. A dashed red line indicates the Operator Boundary. A legend indicates that dashed lines represent the Control plane and solid lines represent the User plane.](dd8c4eb490876d1c18169c84d877ef32_img.jpg) + +The diagram illustrates three deployment scenarios for MTC: + +- A. Direct Model:** An Application Server is connected directly to an Operator Network, which is connected to a UE. The connection between the Application Server and the Operator Network is a solid line (User plane). The connection between the Operator Network and the UE is a solid line (User plane). +- B. Indirect Model (MTC Service Provider Controlled):** An Application Server is connected to an SCS, which is connected to an Operator Network, which is connected to a UE. The connection between the Application Server and the SCS is a dashed line (Control plane). The connection between the SCS and the Operator Network is a dashed line (Control plane). The connection between the Operator Network and the UE is a solid line (User plane). +- C. Indirect Model (Mobile Network Operator Controlled):** An Application Server is connected to an SCS, which is connected to an Operator Network, which is connected to a UE. The connection between the Application Server and the SCS is a dashed line (Control plane). The connection between the SCS and the Operator Network is a solid line (User plane). The connection between the Operator Network and the UE is a solid line (User plane). + +A dashed red line labeled "Operator Boundary" separates the Application Server and SCS (if present) from the Operator Network and UE. A legend indicates that dashed lines represent the Control plane and solid lines represent the User plane. + +Figure A-1: Deployment scenarios for direct and indirect model. The diagram shows three models: A. Direct Model, B. Indirect Model (MTC Service Provider Controlled), and C. Indirect Model (Mobile Network Operator Controlled). Each model shows the connection between an Application Server, a SCS (if applicable), an Operator Network, and a UE. A dashed red line indicates the Operator Boundary. A legend indicates that dashed lines represent the Control plane and solid lines represent the User plane. + +Figure A-1: Deployment scenarios for direct and indirect model + +![Diagram of the Hybrid Model deployment scenario for MTC.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +The diagram illustrates the Hybrid Model deployment scenario. At the top is an **Application Server**. Below it, an **SCS** (Service Capability Server) is shown. A dashed line (Control plane) connects the Application Server to this SCS. Below the SCS is a red dashed line labeled **Operator Boundary**. Below the boundary, another **SCS** is shown, which is part of the **Operator Network**. A dashed line (Control plane) connects the first SCS to the second SCS. A solid line (User plane) connects the Application Server to the second SCS. At the bottom, a **UE** (User Equipment) is shown, connected to the Operator Network by a dashed line (Control plane) and a solid line (User plane). A legend box at the bottom right indicates that dashed lines represent the Control plane and solid lines represent the User plane. + +Diagram of the Hybrid Model deployment scenario for MTC. + +**Figure A-2: Deployment scenarios for hybrid model** + +An operator may deploy the hybrid model with a combination of no internal and external SCS (as in the Direct Model) and internal and/or external SCS (as in the Indirect Model). As shown in Figure A-2, a UE may be in communications with multiple SCSs in an HPLMN which can be made up of a combination of operator controlled and MTC service provider controlled SCSs. In that scenario, the MTC Service provider controlled SCS, and the 3GPP operator controlled SCS may offer different capabilities to the MTC Applications. + +Though not illustrated, it is also possible that the deployment of an AS may be inside the operator domain and under operator control. + +--- + +Annex B (informative): +Void + +## Annex C (informative): Triggering with OMA Push + +### C.1 General + +The 3GPP Device Trigger function enables a transport of application defined triggers to be delivered from a Service Capability Server (SCS) towards the UE. One defined application trigger framework is OMA Push Architecture [20]. OMA Push defined messages can be carried as payload in the Device Trigger message. + +### C.2 Triggering flow using Service Loading + +![Sequence diagram showing the triggering flow using OMA Push. The diagram involves eight lifelines: UE, MSC MME SGSN, PGW GGSN, SMS-SC, HSS, MTC IWF, DNS, and SCS. The sequence of messages is: 1. Trigger requested (SCS to MTC IWF), 2. Trigger submitted over 3GPP access (MTC IWF to UE), 3. Forward to Application (UE to MSC MME SGSN), 4. PDP/PDN connection activation (MSC MME SGSN to HSS), 5. Retrieve content (UE to SCS), and 6. Additional Application Communication (SCS to UE).](6ee202d340236de98def8045f273fa38_img.jpg) + +``` +sequenceDiagram + participant UE + participant MSC as MSC MME SGSN + participant PGW as PGW GGSN + participant SMS as SMS-SC + participant HSS + participant MTC as MTC IWF + participant DNS + participant SCS + + Note right of SCS: 1. Trigger requested + SCS->>MTC: + Note right of MTC: 2. Trigger submitted over 3GPP access + MTC->>UE: + Note left of UE: 3. Forward to Application + UE->>MSC: + Note right of MSC: 4. PDP/PDN connection activation + MSC->>HSS: + Note left of UE: 5. Retrieve content + UE->>SCS: + Note left of UE: 6. Additional Application Communication + SCS-->>UE: +``` + +Sequence diagram showing the triggering flow using OMA Push. The diagram involves eight lifelines: UE, MSC MME SGSN, PGW GGSN, SMS-SC, HSS, MTC IWF, DNS, and SCS. The sequence of messages is: 1. Trigger requested (SCS to MTC IWF), 2. Trigger submitted over 3GPP access (MTC IWF to UE), 3. Forward to Application (UE to MSC MME SGSN), 4. PDP/PDN connection activation (MSC MME SGSN to HSS), 5. Retrieve content (UE to SCS), and 6. Additional Application Communication (SCS to UE). + +Figure C.2-1: Triggering flow using OMA Push + +1. The SCS generates content (e.g. an MTC application specific command) and a URI towards the content (or receives a URI towards content from another source) and then the SCS (performing OMA Push Proxy Gateway functionality) generates a Push Message [19] with the PDU set according to Service Loading [17], and sends a trigger request over Tsp according to clause 5.2.1. +2. The MTC-IWF receives the trigger request and sends it according to clause 5.2.1. +3. The UE SMS dispatcher receives the SMS and routes it to the OMA Push Client which has registered for the triggering routing identifier (e.g. SMS Application port). The OMA Push Client, optionally validates the source (using whitelist defined in OMA Push Management Object [18]) and then forwards the trigger using the Application-Id (e.g. to the M2M Service Capability Layer). +4. The UE activates a PDP/PDN connection. + +5. The content described as part of the URI is retrieved (retrieval of content is mandatory for content type Service Loading [17]). +6. Based on the content retrieved the addressed Application may perform additional actions (e.g. the M2M Service Capability Layer may convey the information to an M2M Application addressed as part of the "command" retrieved, within the same or in a different physical device), but this is outside scope of 3GPP standardisation. + +## Annex D (informative): Device triggering using direct model over user plane + +The following flow shows an example of device triggering using direct model over user plane. In this example, an application in the UE explicitly registers with a DT-AS/SCS (Device Trigger Application Server) in the home operator's network using an existing PDN connection (e.g. default PDN connection). The DT-AS uses the information from the application registration (such as IP address, port, protocol, etc.) to deliver the incoming device triggers, forwarded by another AS (e.g. third party AS) or itself, to the UE through the user plane. Once the UE receives the trigger, the UE either uses the existing PDN connection or the UE sets up a new PDN connection to the appropriate APN to contact the third-party Application Server. + +![Sequence diagram illustrating the triggering flow using direct model over user plane. The diagram shows four steps: 1. UE registers with DT-AS/SCS over user plane through first PDN; 2. DT-AS receives a trigger from a third-party AS; 3. DT-AS delivers the trigger to the UE over user plane; 4. UE uses existing or establishes a new PDN connection to contact the appropriate AS.](886af5e2ffd5d8f11079c547675cf882_img.jpg) + +``` +sequenceDiagram + participant UE + participant PGW/GGSN + participant DT-AS/SCS as DT-AS/SCS (operator n/w) + participant AS as AS (third party) + + Note right of DT-AS/SCS: 1. Application layer registration over user plane through first PDN + Note right of AS: 2. DT-AS receives a trigger from a third-party AS to contact the UE + Note right of DT-AS/SCS: 3. DT-AS delivers the trigger to the UE over user plane + Note right of UE: 4. UE either uses the existing PDN connection or establishes a new PDN connection to contact the appropriate AS +``` + +Sequence diagram illustrating the triggering flow using direct model over user plane. The diagram shows four steps: 1. UE registers with DT-AS/SCS over user plane through first PDN; 2. DT-AS receives a trigger from a third-party AS; 3. DT-AS delivers the trigger to the UE over user plane; 4. UE uses existing or establishes a new PDN connection to contact the appropriate AS. + +**Figure D-1: Triggering flow using direct model over user plane** + +1. The UE/MTC application registers with the DT-AS in an operator's network using an existing PDN connection (for e.g. default PDN). The registration information, for example, could include the IPv4/IPv6 address and the port number where the application is reachable. +2. The DT-AS receives a trigger from a third-party AS to reach the UE. +3. The DT-AS delivers the trigger to the UE over the user plane. +4. The UE either uses the existing PDN connection or sets up a new PDN connection using the appropriate APN to contact the third-party AS. + +--- + +## Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2012-02 | SP-55 | SP-120095 | - | - | - | MCC Update to version 1.0.0 for presentation to TSG SA for Information and Approval . | 1.0.0 | +| 2012-03 | SP-55 | - | - | - | - | MCC Update to version 11.0.0 after TSG SA Approval (Release 11) | 11.0.0 | +| 2012-06 | SP-56 | SP-120239 | 0001 | 2 | F | Deletion of the SMS-SC from the SCS related description | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0004 | 2 | F | Removal of unnecessary information in Table 5.3.1-1 | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0006 | 2 | F | Overall corrections | 11.1.0 | +| 2012-06 | SP-56 | SP-120240 | 0007 | 1 | F | Missing description of addressing in TS 23.682 | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0009 | 2 | F | Clarifications on Device Triggering | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0011 | 2 | F | Clarification for the reference point between HSS/HLR and MTC-IWF | 11.1.0 | +| 2012-06 | SP-56 | SP-120240 | 0018 | 2 | F | Identifier and addressing usage | 11.1.0 | +| 2012-06 | SP-56 | SP-120240 | 0021 | 1 | F | SIMTC with IP-SM-GW adaption for SMSMI work from Server to MSISDN-less IMS UE direction | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0023 | 2 | F | Corrections of trigger flows | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0025 | 2 | F | External Identifier Usage | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0027 | 2 | F | Corrections to T4 interface requirements | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0028 | 2 | F | Changes to clause 4.4 | 11.1.0 | +| 2012-06 | SP-56 | SP-120240 | 0030 | 1 | F | T4 triggering for PS-only IMS UE without MSISDN | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0031 | - | F | Giving the MTC AAA to HSS/HLR reference point a name | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0032 | 3 | F | Backward compatibility with legacy SMS networks | 11.1.0 | +| 2012-06 | SP-56 | SP-120239 | 0036 | 1 | F | Clarifications on Functionality of Network Elements | 11.1.0 | +| 2012-06 | SP-56 | SP-120337 | 0039 | 2 | F | Updates to TS 23.682 Scope | 11.1.0 | +| 2012-06 | SP-56 | SP-120337 | 0040 | 2 | C | External Interface Security | 11.1.0 | +| 2012-06 | SP-56 | SP-120337 | 0041 | - | B | Network based solution for filtering SMS-delivered device trigger messages | 11.1.0 | +| 2012-09 | SP-57 | SP-120482 | 0049 | 1 | F | Addition of MTC AAA into the architecture figure | 11.2.0 | +| 2012-09 | SP-57 | SP-120482 | 0054 | 2 | F | Adding missing information elements into Table 5.3.1-1 | 11.2.0 | +| 2012-09 | SP-57 | SP-120482 | 0058 | 2 | F | Clarification of Architecture Models and Deployment scenarios | 11.2.0 | +| 2012-09 | SP-57 | SP-120482 | 0060 | 1 | F | Message waiting for Device Triggering Function corrections | 11.2.0 | +| 2012-09 | SP-57 | SP-120601 | 0052 | 1 | F | Tsp interface security requirements | 11.2.0 | +| 2012-12 | SP-58 | SP-120717 | 0055 | 4 | F | Device Triggering corrections | 11.3.0 | +| 2012-12 | SP-58 | SP-120717 | 0065 | 1 | F | Add IP-SM-GW identifier to S6m and T4 messages | 11.3.0 | +| 2012-12 | SP-58 | SP-120717 | 0066 | 1 | F | Message Waiting for device trigger procedure correction | 11.3.0 | +| 2013-06 | SP-60 | SP-130305 | 0069 | 4 | F | Triggering indication added in the CDR | 11.4.0 | +| 2013-06 | SP-60 | SP-130305 | 0072 | 3 | F | Making Device Trigger outcome to SCS optional | 11.4.0 | +| 2013-06 | SP-60 | SP-130305 | 0073 | 1 | F | Missing condition of delivery of Message Delivery Report | 11.4.0 | +| 2013-06 | SP-60 | SP-130257 | 0074 | 2 | F | Device triggering indication in SM | 11.4.0 | +| 2013-09 | SP-61 | SP-130403 | 0075 | 1 | F | HSS/HLR filtering SMS-delivered device trigger messages | 11.5.0 | +| 2013-12 | SP-62 | SP-130530 | 0076 | 2 | B | Core Network assisted eNodeB parameters tuning | 12.0.0 | +| 2013-12 | SP-62 | SP-130529 | 0077 | 6 | B | Introducing UE Power Saving Mode | 12.0.0 | +| 2013-12 | SP-62 | SP-130530 | 0078 | 5 | B | Device trigger recall and replace | 12.0.0 | +| 2014-03 | SP-63 | SP-140104 | 0079 | 3 | F | Power Saving Mode applicability | 12.1.0 | +| 2014-03 | SP-63 | SP-140053 | 0083 | - | D | Deleting SA WG3 specific text | 12.1.0 | +| 2014-06 | SP-64 | SP-140263 | 0084 | - | F | Removal of HSS impacts on device trigger recall/replace | 12.2.0 | +| 2014-06 | SP-64 | SP-140263 | 0085 | 1 | F | Clarification on TAU/RAU procedure for Power Saving Mode | 12.2.0 | +| 2014-06 | SP-64 | SP-140263 | 0086 | 1 | F | Clarification on ISR for PSM UE | 12.2.0 | +| 2014-12 | SP-66 | SP-140691 | 0087 | 1 | B | Service Capability Exposure Architecture | 13.0.0 | +| 2014-12 | SP-66 | SP-140693 | 0089 | 3 | C | PSM Enhancement | 13.0.0 | +| 2015-03 | SP-67 | SP-150019 | 0092 | - | A | Correction to the scope | 13.1.0 | +| 2015-06 | SP-68 | SP-150228 | 0102 | 1 | A | Handling of PSM timer | 13.2.0 | +| 2015-06 | SP-68 | SP-150237 | 0095 | - | B | Architecture update for GROUPE | 13.2.0 | +| 2015-06 | SP-68 | SP-150237 | 0094 | 6 | B | Group message delivery function and procedure | 13.2.0 | +| 2015-06 | SP-68 | SP-150236 | 0100 | 4 | B | Monitoring Feature Description | 13.2.0 | +| 2015-06 | SP-68 | SP-150236 | 0104 | 2 | B | Introduction of Charging Principles for Monitoring Events feature | 13.2.0 | +| 2015-06 | SP-68 | SP-150236 | 0097 | 5 | B | Introduction of Monitoring Procedures | 13.2.0 | +| 2015-06 | SP-68 | SP-150236 | 0093 | 6 | B | Monitoring via PCRF | 13.2.0 | +| 2015-06 | SP-68 | SP-150339 | 0099 | 2 | B | Architectural updates for Monitoring feature | 13.2.0 | +| 2015-06 | SP-68 | SP-150236 | 0107 | 5 | B | Enhancing roaming architecture for Service Exposure | 13.2.0 | +| 2015-06 | SP-68 | SP-150238 | 0106 | 3 | B | Introducing functions for High latency communication | 13.2.0 | +| 2015-06 | SP-68 | SP-150238 | 0115 | 4 | B | HLcom solution Using Monitoring Event 'Availability after DDN Failure' | 13.2.0 | +| 2015-06 | SP-68 | SP-150238 | 0108 | 2 | B | HLcom solution reusing Monitoring Event 'UE Reachability' realization | 13.2.0 | +| 2015-06 | SP-68 | SP-150235 | 0109 | 1 | B | Architectural updates for AESE feature | 13.2.0 | +| 2015-06 | SP-68 | SP-150235 | 0116 | 2 | B | Detailed description for informing about potential network issues | 13.2.0 | +| 2015-06 | SP-68 | SP-150235 | 0114 | 2 | B | Addition of resource management for background data transfer feature | 13.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|---------------------------------------------------------------------------------------------------------------|---------------| +| 2015-06 | SP-68 | SP-150235 | 0113 | 3 | B | Implementing AESE Solution on providing predictable communication patterns of a UE to the MME | 13.2.0 | +| 2015-06 | SP-68 | SP-150235 | 0117 | 1 | B | Setting up an AS session with required QoS | 13.2.0 | +| 2015-06 | SP-68 | SP-150235 | 0118 | 3 | B | Change the chargeable party at the session set-up or during the session | 13.2.0 | +| 2015-06 | SP-68 | SP-150236 | 0096 | 2 | B | Update to PSM to support Monitoring events | 13.2.0 | +| 2015-06 | SP-68 | SP-150235 | 0119 | 4 | C | Clarification on the overall architecture related with SCEF | 13.2.0 | +| 2015-06 | SP-68 | SP-150338 | - | - | - | Structuring of AESE, MONTE, GROUPE, and HLcom related CRs to TS 23.682. GUIDE TO IMPLEMENTATION OF CRS | 13.2.0 | +| 2015-09 | SP-69 | SP-150499 | 0120 | 1 | C | Monitoring for roaming scenarios | 13.3.0 | +| 2015-09 | SP-69 | SP-150499 | 0121 | 1 | F | Location reporting clarifications for Monitoring | 13.3.0 | +| 2015-09 | SP-69 | SP-150502 | 0122 | 4 | B | Introducing eDRX for High latency communication | 13.3.0 | +| 2015-09 | SP-69 | SP-150498 | 0123 | 1 | F | Remove T4 and Tsm from Figure 4.2-2 | 13.3.0 | +| 2015-09 | SP-69 | SP-150502 | 0124 | - | F | Non-Applicability of HLCom Monitoring Events feature to Gn/Gp-SGSN | 13.3.0 | +| 2015-09 | SP-69 | SP-150498 | 0125 | - | F | Adding Nt reference point to architecture | 13.3.0 | +| 2015-09 | SP-69 | SP-150501 | 0126 | 2 | B | Introducing Extended Idle mode DRX | 13.3.0 | +| 2015-09 | SP-69 | SP-150502 | 0128 | 1 | F | Providing DL Data Buffer Expiration Time and the Suggested number of buffered downlink Packets | 13.3.0 | +| 2015-09 | SP-69 | SP-150498 | 0130 | 2 | F | Corrections of monitoring via PCRF and informing about potential network issues | 13.3.0 | +| 2015-09 | SP-69 | SP-150498 | 0132 | 2 | F | Correction on provision of CP parameters | 13.3.0 | +| 2015-12 | SP-70 | SP-150611 | 0133 | 10 | B | Introducing Extended Idle mode DRX | 13.4.0 | +| 2015-12 | SP-70 | SP-150609 | 0134 | - | F | Correction of location signalling | 13.4.0 | +| 2015-12 | SP-70 | SP-150609 | 0135 | 2 | F | Clarification of MONTE Reporting Procedure | 13.4.0 | +| 2015-12 | SP-70 | SP-150610 | 0136 | 2 | F | Usage of cell identities in the MBMS bearer activation for group message delivery | 13.4.0 | +| 2015-12 | SP-70 | SP-150611 | 0137 | 2 | F | Extended DRX support for multiple applications | 13.4.0 | +| 2015-12 | SP-70 | SP-150609 | 0139 | 2 | F | Correcting HSS handling of CP parameters | 13.4.0 | +| 2015-12 | SP-70 | SP-150612 | 0141 | 3 | C | Applying eDRX for HLcom notification procedure "UE reachability" | 13.4.0 | +| 2015-12 | SP-70 | SP-150608 | 0142 | 3 | F | Clarify validity time for CP Parameters, Add Delete Capability | 13.4.0 | +| 2015-12 | SP-70 | SP-150609 | 0143 | - | F | Correct step 3 text in 5.6.1.7 | 13.4.0 | +| 2015-12 | SP-70 | SP-150610 | 0149 | 2 | F | Content delivery via MBMS bearer | 13.4.0 | +| 2015-12 | SP-70 | SP-150609 | 0150 | 1 | F | Monitoring event figure clarification | 13.4.0 | +| 2015-12 | SP-70 | SP-150611 | 0151 | 1 | F | Support for MT services when UE configured for eDRX | 13.4.0 | +| 2015-12 | SP-70 | SP-150609 | 0152 | 2 | F | Event cancellation in case of non-support in new MME | 13.4.0 | +| 2016-03 | SP-71 | SP-160159 | 0156 | 2 | F | Determination of MB2/Ns interface connection agreement | 13.5.0 | +| 2016-03 | SP-71 | SP-160202 | 0159 | 5 | F | Handling of a 5.12s eDRX cycle | 13.5.0 | +| 2016-03 | SP-71 | SP-160161 | 0160 | 3 | B | Introduction of non-IP data delivery via the SCEF for cellular IoT | 13.5.0 | +| 2016-03 | SP-71 | SP-160161 | 0165 | 2 | B | Update HSS/HLR functionality to support non-IP data delivery via SCEF | 13.5.0 | +| 2016-03 | SP-71 | SP-160161 | 0166 | 1 | B | HLcom update for C IoT CP optimisation | 13.5.0 | +| 2016-06 | SP-72 | SP-160298 | 0162 | 5 | C | Remove T5 | 13.6.0 | +| 2016-06 | SP-72 | SP-160293 | 0167 | - | F | Clarification of Monitoring event configuration and deletion | 13.6.0 | +| 2016-06 | SP-72 | SP-160293 | 0168 | 1 | F | Clarification of informing the HSS about the result of a configuration when an IWK-SCEF is involved | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0169 | 1 | F | Removal of SCEF ID in T6a Authorization Request | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0171 | 5 | F | HLCOM and eDRX for NIDD via SCEF | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0172 | 3 | F | Specify Rate Control information for SCEF | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0173 | 1 | F | Corrections to 5.3.2 | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0174 | 6 | F | Correction on User Identity | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0175 | 1 | F | Delete the concept of valid/invalid T6a context | 13.6.0 | +| 2016-06 | SP-72 | SP-160289 | 0181 | - | F | Adding PTW length to S1 paging message in case of eDRX | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0182 | 2 | F | Keeping UE applications unaware of SCEF/PDN GW choice | 13.6.0 | +| 2016-06 | SP-72 | SP-160287 | 0183 | 2 | F | Corrections to T6a Connection Establishment Procedure | 13.6.0 | +| 2016-06 | SP-72 | SP-160295 | 0170 | 2 | B | Introducing support for Non-IP data for GPRS | 14.0.0 | +| 2016-09 | SP-73 | SP-160655 | 0189 | 5 | B | Provisioning PFD via SCEF | 14.1.0 | +| 2016-09 | SP-73 | SP-160640 | 0191 | - | A | Alignment of MONTE Event Suspend / Resume / Cancel procedure with stage 3 | 14.1.0 | +| 2016-09 | SP-73 | SP-160648 | 0192 | 1 | B | Cleanup and alignment of C IoT specs | 14.1.0 | +| 2016-09 | SP-73 | SP-160657 | 0193 | 2 | B | Monitoring event configuration for a group of UEs via PCRF | 14.1.0 | +| 2016-09 | SP-73 | SP-160655 | 0194 | 2 | B | Adding reference point description between SCEF and PFDF | 14.1.0 | +| 2016-09 | SP-73 | SP-160657 | 0195 | 1 | B | Group Communication Pattern Provisioning | 14.1.0 | +| 2016-09 | SP-73 | SP-160636 | 0198 | 1 | A | Corrections for Non-IP Data Delivery Procedures | 14.1.0 | +| 2016-09 | SP-73 | SP-160636 | 0200 | 3 | A | Updates of eDRX for NB-IoT | 14.1.0 | +| 2016-09 | SP-73 | SP-160637 | 0202 | - | A | Aligning PTW definition with RAN2 | 14.1.0 | +| 2016-09 | SP-73 | SP-160659 | 0205 | 1 | C | Operator management of eDRX parameters | 14.1.0 | +| 2016-09 | SP-73 | SP-160636 | 0208 | 1 | A | Alignment of NIDD procedures at T6a interface with TS 29.128 | 14.1.0 | +| 2016-09 | SP-73 | SP-160636 | 0209 | 3 | F | Removal of payload from NIDD Submit Response | 14.1.0 | +| 2016-09 | SP-73 | SP-160636 | 0210 | 1 | A | Addition of new parameters to T6a interface | 14.1.0 | +| 2016-09 | SP-73 | SP-160658 | 0211 | 2 | F | Clarifying the configuration of PSM Active Time | 14.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|------------------------------------------------------------------------------------------------------------|---------------| +| 2016-09 | SP-73 | SP-160637 | 0215 | 1 | A | Correction of loose Hyper SFN synchronization for eDRX | 14.1.0 | +| 2016-09 | SP-73 | SP-160632 | 0217 | 2 | A | Clarification of MTC-IWF and SCEF connection possibilities | 14.1.0 | +| 2016-09 | SP-73 | SP-160640 | 0219 | 2 | A | Reachability Report Corrections | 14.1.0 | +| 2016-09 | SP-73 | SP-160658 | 0220 | 2 | B | MO SMS over T4 | 14.1.0 | +| 2016-09 | SP-73 | SP-160636 | 0224 | 1 | A | Correction to reporting of MO exception data | 14.1.0 | +| 2016-09 | SP-73 | SP-160640 | 0226 | - | A | Correction of the update to PSM to support Monitoring events | 14.1.0 | +| 2016-09 | SP-73 | SP-160640 | 0229 | - | A | Reachability for SMS in GERAN and UTRAN | 14.1.0 | +| 2016-09 | SP-73 | SP-160657 | 0230 | 2 | C | Group Monitoring events configuration directly at MME/SGSN | 14.1.0 | +| 2016-09 | SP-73 | SP-160637 | 0233 | - | A | Clarification on homogenous support of extended idle mode DRX in a Tracking Area | 14.1.0 | +| 2016-12 | SP-74 | SP-160821 | 0227 | 10 | C | Group based MONTE Event Configuration via HSS | 14.2.0 | +| 2016-12 | SP-74 | SP-160823 | 0234 | 4 | C | Reliable UE delivery based on hop-by-hop acknowledgements (5c) | 14.2.0 | +| 2016-12 | SP-74 | SP-160823 | 0235 | 4 | B | Support of Enhanced Coverage Authorization Control via SCEF | 14.2.0 | +| 2016-12 | SP-74 | SP-160825 | 0237 | 1 | F | SCEF Behavior when MT NIDD Causes a Trigger | 14.2.0 | +| 2016-12 | SP-74 | SP-160823 | 0238 | 4 | B | CloT Data Delivery Service | 14.2.0 | +| 2016-12 | SP-74 | SP-160821 | 0239 | 3 | C | Enhancements to monitoring event configuration and reporting procedures for group of UEs | 14.2.0 | +| 2016-12 | SP-74 | SP-160808 | 0242 | 5 | A | Corrections for MT NIDD procedure to handle multiple non-IP data | 14.2.0 | +| 2016-12 | SP-74 | SP-160808 | 0244 | 1 | A | Correction of T6a Connection Establishment parameters | 14.2.0 | +| 2016-12 | SP-74 | SP-160809 | 0245 | 1 | A | Active time correction in UE Power Save Mode | 14.2.0 | +| 2016-12 | SP-74 | SP-160808 | 0248 | 2 | A | Streamlining NIDD Submit Indication | 14.2.0 | +| 2016-12 | SP-74 | SP-160808 | 0249 | 2 | A | Adding Rate Control parameters into SCEF context | 14.2.0 | +| 2016-12 | SP-74 | SP-160823 | 0251 | 2 | B | MBMS and Power Saving functions | 14.2.0 | +| 2016-12 | SP-74 | SP-160825 | 0252 | 3 | B | Procedure for the HSS to update NIDD Authorization | 14.2.0 | +| 2016-12 | SP-74 | SP-160823 | 0254 | 1 | B | Enhancements to Location Services for CloT | 14.2.0 | +| 2017-03 | SP-75 | SP-170053 | 0259 | 1 | B | SCEF Initiated T6 Release | 14.3.0 | +| 2017-03 | SP-75 | SP-170053 | 0262 | 2 | F | Background Data Transfer Policy Activation via the SCEF | 14.3.0 | +| 2017-03 | SP-75 | SP-170054 | 0260 | 3 | B | Group Message Delivery Procedure changes due to NAPS | 15.0.0 | +| 2017-03 | SP-75 | SP-170054 | 0261 | 3 | C | Northbound APIs for a co-located SCEF/MTC-IWF - Clause 4 enhancements to describe MTC-IWF deployment cases | 15.0.0 | +| 2017-03 | SP-75 | SP-170054 | 0263 | 2 | B | Background Data Transfer Policy Activation via the SCEF | 15.0.0 | +| 2017-03 | SP-75 | SP-170054 | 0271 | 1 | B | Northbound APIs for SCEF - SCS/AS Interworking - Clause 1-3 enhancements | 15.0.0 | +| 2017-03 | SP-75 | SP-170054 | 0272 | 3 | B | Northbound APIs for SCEF - SCS/AS Interworking - Clause 4 enhancements | 15.0.0 | +| 2017-06 | SP-76 | SP-170376 | 0274 | 2 | C | TMGI and Location changes for GMD | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0275 | 4 | B | Enable T8 for MONTE procedures | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0277 | 1 | B | Enabling the Routing of non-IP traffic between the UE and SCEF | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0278 | 3 | B | SCEF Behaviour in the NIDD Configuration and NIDD Authorisation Update Procedures | 15.1.0 | +| 2017-06 | SP-76 | SP-170464 | 0279 | 4 | B | SCEF Behaviour in the Mobile Terminated NIDD Procedure | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0280 | 1 | B | SCEF Behaviour in the Mobile Originated NIDD Procedure | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0281 | 1 | B | Accessing MTC-IWF functionality via T8 | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0283 | 3 | B | T8 to AS directly and SCEF Behaviour in the MONTE | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0286 | 1 | F | T8 updates for procedure for enhanced coverage restriction control via SCEF | 15.1.0 | +| 2017-06 | SP-76 | SP-170369 | 0288 | 1 | A | Reliability Data Service capability exchange between the UE and the SCEF | 15.1.0 | +| 2017-06 | SP-76 | SP-170372 | 0294 | 1 | A | Removal of Non-IP APN | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0302 | 1 | B | Enable T8 for CP procedures | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0303 | 1 | F | Transaction ID's in the Background Data Transfer Procedure | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0304 | 1 | C | Transaction ID's in the Change of Chargeable Party Procedures | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0305 | 1 | C | T8 Updates for Support of setting up an AS session with required QoS | 15.1.0 | +| 2017-06 | SP-76 | SP-170368 | 0308 | 1 | A | Corrections of parameters on SCEF-PFDF interface | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0311 | 2 | C | T8 Updates for Network Status Reports | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0312 | 1 | C | T8 Updates for PFD Management | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0313 | 4 | B | Setting Suggested Network Configuration Parameters via T8 | 15.1.0 | +| 2017-06 | SP-76 | SP-170369 | 0316 | 1 | A | Reliable Data Service Port Numbers | 15.1.0 | +| 2017-06 | SP-76 | SP-170362 | 0319 | - | A | Mismatch between table and call flow steps | 15.1.0 | +| 2017-06 | SP-76 | SP-170376 | 0320 | 1 | B | Charging management at SCEF and at T8 for MONTE procedures | 15.1.0 | +| 2017-09 | SP-77 | SP-170730 | 0306 | 2 | F | Completion of SCEF description (clause 4.4.8) | 15.2.0 | +| 2017-09 | SP-77 | SP-170723 | 0310 | 2 | A | IoT UE capabilities for MBMS user service | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0322 | 3 | B | Enable minimum time interval for Continuous Location Reporting | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0324 | - | D | Removing Reference to TATD | 15.2.0 | +| 2017-09 | SP-77 | SP-170716 | 0326 | 1 | A | Use of MBMS with MB2 for UEs with power saving functions | 15.2.0 | +| 2017-09 | SP-77 | SP-170723 | 0330 | - | A | Removal of "configuration" type monitoring request | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0333 | 4 | B | Group MT NIDD | 15.2.0 | +| 2017-09 | SP-77 | SP-170723 | 0339 | 2 | A | Event Reporting when the UE Belongs to Multiple Groups | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------|---------------| +| 2017-09 | SP-77 | SP-170730 | 0340 | 2 | C | MO NIDD RDS Header Configuration | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0341 | 2 | F | Triggering the UE in the MT NIDD Procedure | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0342 | 1 | C | Idle Status Indications for extended idle mode DRX and extended buffering | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0343 | 2 | C | HSS Influence of Network Parameters from the SCEF | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0344 | 1 | F | Group Reporting Guard timer clarification | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0345 | 1 | C | Avoiding Duplicate Monitoring Reports | 15.2.0 | +| 2017-09 | SP-77 | SP-170732 | 0346 | 1 | F | Removing unused parameter | 15.2.0 | +| 2017-09 | SP-77 | SP-170732 | 0347 | 2 | F | Handling of multiple CP parameter sets | 15.2.0 | +| 2017-09 | SP-77 | SP-170720 | 0352 | 1 | A | Corrections for managing multiple Application IDs | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0354 | - | C | Removing SCS/AS Identifier from Response | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0355 | 1 | C | TTRI and TLTRI Usage and Unnecessary Parameters | 15.2.0 | +| 2017-09 | SP-77 | SP-170730 | 0359 | 1 | C | Filtering the Report for Number of UEs in a Geographic Area | 15.2.0 | +| 2017-09 | SP-77 | SP-170732 | 0360 | 1 | F | Normative conditions to send RDS acknowledgement | 15.2.0 | +| 2017-09 | SP-77 | SP-170718 | 0361 | 2 | A | Clarifications on report location to SCS/AS for a group of UEs via PCRF | 15.2.0 | +| 2017-12 | SP-78 | SP-170918 | 0363 | 1 | A | Correction of TMGI allocation extension | 15.3.0 | +| 2017-12 | SP-78 | SP-170922 | 0364 | 1 | F | Notifying SCS/AS about loss of transmission resources | 15.3.0 | +| 2017-12 | SP-78 | SP-170922 | 0365 | 1 | F | Corrected monitoring procedures | 15.3.0 | +| 2017-12 | SP-78 | SP-170924 | 0366 | 2 | C | Reliable Data Service with PtP SGi Tunneling | 15.3.0 | +| 2017-12 | SP-78 | SP-170922 | 0367 | 2 | C | Reliable Data Service Configuration | 15.3.0 | +| 2017-12 | SP-78 | SP-170924 | 0368 | 1 | F | Updating SCEF ID in HSS during NIDD configuration procedure | 15.3.0 | +| 2017-12 | SP-78 | SP-170918 | 0370 | 1 | A | Correction of Rate Control in SCEF | 15.3.0 | +| 2017-12 | SP-78 | SP-170918 | 0372 | 2 | A | Reasons for the Loss of Connectivity Monitoring Event | 15.3.0 | +| 2017-12 | SP-78 | SP-170924 | 0373 | 2 | B | Reasons for the Loss of Connectivity Monitoring Event | 15.3.0 | +| 2017-12 | SP-78 | SP-170924 | 0374 | 2 | B | Introduction of Service Gap Control | 15.3.0 | +| 2017-12 | SP-78 | SP-170922 | 0375 | - | F | Corrected Group MT NIDD procedure | 15.3.0 | +| 2018-03 | SP-79 | SP-180109 | 0378 | 2 | F | Correction to cancelled monitoring Event in the network parameter configuration via SCEF | 15.4.0 | +| 2018-03 | SP-79 | SP-180084 | 0381 | 1 | A | SMS reachability monitoring correction | 15.4.0 | +| 2018-03 | SP-79 | SP-180109 | 0382 | 4 | F | Supporting Common API framework for SCEF | 15.4.0 | +| 2018-03 | SP-79 | SP-180109 | 0384 | 5 | F | Corrections of Group Message Delivery via NIDD | 15.4.0 | +| 2018-03 | SP-79 | SP-180109 | 0387 | 1 | F | Correction to the Usage of Monitoring Duration | 15.4.0 | +| 2018-06 | SP-80 | SP-180498 | 0376 | 3 | B | Additional parameters for NB-IoT UE Uu operation optimisation | 15.5.0 | +| 2018-06 | SP-80 | SP-180496 | 0386 | 4 | F | Correction of APN Rate Control for PDN connection release and re-establishment | 15.5.0 | +| 2018-06 | SP-80 | SP-180493 | 0390 | 1 | F | Making the T8 Destination Address Mandatory for APIs that Create a Subscription | 15.5.0 | +| 2018-06 | SP-80 | SP-180493 | 0392 | 4 | F | TLTRI and TTRI Usage | 15.5.0 | +| 2018-06 | SP-80 | SP-180493 | 0393 | 3 | F | Fixing Group NIDD | 15.5.0 | +| 2018-06 | SP-80 | SP-180472 | 0394 | 1 | A | Monitoring Event configuration removal for a group | 15.5.0 | +| 2018-06 | SP-80 | SP-180493 | 0395 | - | F | Correction to the group message delivery | 15.5.0 | +| 2018-06 | SP-80 | SP-180493 | 0396 | 2 | F | Deletion of Network Parameter Configuration | 15.5.0 | +| 2018-06 | SP-80 | SP-180496 | 0397 | 2 | F | Removal of leftover sentence regarding MTC-IWF architecture | 15.5.0 | +| 2018-06 | SP-80 | SP-180493 | 0399 | 1 | F | Indicating the Reachability Report Cause | 15.5.0 | +| 2018-09 | SP-81 | SP-180728 | 0402 | 5 | B | Traffic Profile for NB-IoT UE Uu operation optimisation | 15.6.0 | +| 2018-09 | SP-81 | SP-180727 | 0406 | 2 | F | Group NIDD fix | 15.6.0 | +| 2018-09 | SP-81 | SP-180729 | 0409 | 1 | F | Addition of the missing definition of WB-E-UTRAN | 15.6.0 | +| 2018-09 | SP-81 | SP-180730 | 0404 | 5 | B | Enhancement of network event reporting | 16.0.0 | +| 2018-12 | SP-82 | SP-181095 | 0411 | 2 | A | Monitoring event deletion for large UE groups | 16.1.0 | +| 2018-12 | SP-82 | SP-181094 | 0413 | 1 | A | Monitoring event report | 16.1.0 | +| 2018-12 | SP-82 | SP-181094 | 0415 | - | A | Correction of accuracy level | 16.1.0 | +| 2018-12 | SP-82 | SP-181082 | 0417 | 1 | A | Removal of incorrect architecture requirement in NIDD configuration | 16.1.0 | +| 2018-12 | SP-82 | SP-181095 | 0419 | 2 | A | Corrections to Service Gap Control | 16.1.0 | +| 2018-12 | SP-82 | SP-181095 | 0421 | 1 | A | Handling of multiple external IDs for the same UE | 16.1.0 | +| 2018-12 | SP-82 | SP-181096 | 0422 | 1 | F | IWK-SCEF correction | 16.1.0 | +| 2019-03 | SP-83 | SP-190175 | 0425 | 1 | F | Change xMB reference | 16.2.0 | +| 2019-03 | SP-83 | SP-190161 | 0428 | - | A | Protocol criteria for domain name matching | 16.2.0 | +| 2019-03 | SP-83 | SP-190175 | 0431 | 2 | F | Correction on Procedure for MSISDN-less MO-SMS via T4 | 16.2.0 | +| 2019-03 | SP-83 | SP-190175 | 0433 | 1 | A | Correction to the location reporting with minimum reporting interval | 16.2.0 | +| 2019-03 | SP-83 | SP-190175 | 0435 | - | F | Correction on enhancements to Location Services for CIoT | 16.2.0 | +| 2019-06 | SP-84 | SP-190405 | 0437 | 1 | A | Group message delivery | 16.3.0 | +| 2019-06 | SP-84 | SP-190406 | 0438 | 2 | F | PFD provisioning procedure | 16.3.0 | +| 2019-06 | SP-84 | SP-190405 | 0440 | 1 | A | Alignment with stage 3 on multiple values for a PFD attribute | 16.3.0 | +| 2019-06 | SP-84 | SP-190405 | 0443 | 3 | A | Availability after DDN notification for eDRX | 16.3.0 | +| 2019-06 | SP-84 | SP-190414 | 0444 | 2 | F | Adding Support for Dynamic Port Management in RDS | 16.3.0 | +| 2019-06 | SP-84 | SP-190414 | 0445 | 2 | F | Monitoring information for Reporting Event Change of IMSI-IMEI(SV) association | 16.3.0 | +| 2019-06 | SP-84 | SP-190417 | 0446 | 1 | C | Adding Support for Indicating Serialization Format in RDS | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------|---------------| +| 2019-06 | SP-84 | SP-190425 | 0447 | 1 | B | EPS exposure architecture supporting RACS | 16.3.0 | +| 2019-06 | SP-84 | SP-190414 | 0448 | 1 | B | Enhancement of Monitoring Event configuration and Network Parameter Configuration | 16.3.0 | +| 2019-06 | SP-84 | SP-190405 | 0451 | 1 | A | Group message delivery using MBMS via xMB | 16.3.0 | +| 2019-09 | SP-85 | SP-190622 | 0454 | 1 | F | Correction to Maximum Latency for Mobile Terminating NIDD procedure | 16.4.0 | +| 2019-09 | SP-85 | SP-190622 | 0455 | 1 | F | Session type Files in Group Message Delivery using MBMS via xMB | 16.4.0 | +| 2019-09 | SP-85 | SP-190617 | 0457 | 2 | B | UCMF provisioning procedures | 16.4.0 | +| 2019-09 | SP-85 | SP-190622 | 0459 | 3 | C | Enhanced Multiple Event Monitoring | 16.4.0 | +| 2019-12 | SP-86 | SP-191089 | 0461 | 1 | F | SMS transmission in Communication pattern parameters | 16.5.0 | +| 2019-12 | SP-86 | SP-191089 | 0462 | 2 | F | Fix initial reporting issue | 16.5.0 | +| 2019-12 | SP-86 | SP-191089 | 0463 | | F | Subscriber data download during Attach, TAU/RAU | 16.5.0 | +| 2019-12 | SP-86 | SP-191089 | 0464 | | F | UE reachability monitoring correction | 16.5.0 | +| 2019-12 | SP-86 | SP-191067 | 0466 | - | A | Alignment with SA4 for using Resource ID in xMB | 16.5.0 | +| 2020-03 | SP-87E | SP-200074 | 0467 | 2 | F | On the UCMF provisioning | 16.6.0 | +| 2020-03 | SP-87E | SP-200081 | 0468 | - | F | External Identifier correction | 16.6.0 | +| 2020-07 | SP-88E | SP-200436 | 0469 | - | F | Support of multiple coding formats | 16.7.0 | +| 2020-09 | SP-89E | SP-200686 | 0471 | - | F | MTC provider information for network parameter configuration | 16.8.0 | +| 2021-03 | SP-91E | SP-210082 | 0472 | 1 | F | Roaming status monitoring event clarification | 16.9.0 | +| 2021-03 | SP-91E | SP-210055 | 0474 | - | F | MTC Provider Information for EC restriction control | 16.9.0 | +| 2021-06 | SP-92E | SP-210341 | 0475 | 2 | C | Application Identifier for SCEF API ChargebleParty and AS Session with QoS | 17.0.0 | +| 2021-06 | SP-92E | SP-210363 | 0477 | 2 | B | Dynamic management of group based event monitoring | 17.0.0 | +| 2021-09 | SP-93E | SP-210903 | 0482 | 1 | A | 5GS Idle Status Indication correction | 17.1.0 | +| 2021-09 | SP-93E | SP-210937 | 0483 | - | F | Update Configuration for Group Monitoring Event with adding Users | 17.1.0 | +| 2021-12 | SP-94E | SP-211305 | 0484 | - | F | updates for service parameters regarding addition of UEs for group based event subscription | 17.2.0 | +| 2021-12 | SP-94E | SP-211284 | 0487 | 2 | B | Support IoT NTN in EPS | 17.2.0 | +| 2022-06 | SP-96 | SP-220411 | 0489 | 1 | F | EPS roaming status for dual registration | 17.3.0 | +| 2023-03 | SP-99 | SP-230080 | 0490 | 2 | F | Removing inappropriate use of the term device | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-25/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/raw/rel-18/23_series/23700-25/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3633499c5835594f0576947bde104b216ed37493 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:532d743118b2eefa0d6290000d780ff321684a64c2269c7a3dad275f08e41b0c +size 71218 diff --git a/raw/rel-18/23_series/23700-25/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg b/raw/rel-18/23_series/23700-25/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33492e0c948155a57a00bb4047beb9b40b4af593 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc8b6c4779276c9afc11bc1fb10178adcaeefc081bef1dee68640ff473215a9 +size 110122 diff --git a/raw/rel-18/23_series/23700-25/0f7871077bba48a2c97f7859a5edda0d_img.jpg b/raw/rel-18/23_series/23700-25/0f7871077bba48a2c97f7859a5edda0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b4e24f26c01a4bff637cae7fca051eef28c8dc4 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/0f7871077bba48a2c97f7859a5edda0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b28aa7a300d7b7265c7cfd3cb8810abca48ef8ba87ed4b43c10a2033fdebbdd5 +size 53148 diff --git a/raw/rel-18/23_series/23700-25/24a89bcaba787f2bc1721356480a4a01_img.jpg b/raw/rel-18/23_series/23700-25/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c24e273d32eff5ba5b6ce004ae7e5e927120bcf2 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:025912b763f5bdf69de066df589ba89605849d704f95c9977b0be9a9d21b40ed +size 55196 diff --git a/raw/rel-18/23_series/23700-25/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/raw/rel-18/23_series/23700-25/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4403131129355fa2063dd1f08ec1e59f322baeb6 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe6c9c6d1639dcfe76f6a5ece2d9ea9cd1f209bc16f6cd9fff410dae2376f54a +size 106028 diff --git a/raw/rel-18/23_series/23700-25/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/raw/rel-18/23_series/23700-25/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2f46a3a38407c02a13de666f5548de1eea041a0 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88beb32f80b237eeb0dd054f06440f7986f231aea5a0544e3e533eaa433e8d3b +size 110987 diff --git a/raw/rel-18/23_series/23700-25/41af98c5f15e6022f8ddde55567cf56e_img.jpg b/raw/rel-18/23_series/23700-25/41af98c5f15e6022f8ddde55567cf56e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7be790035b94bea402c805916c891d1a95f050ff --- /dev/null +++ b/raw/rel-18/23_series/23700-25/41af98c5f15e6022f8ddde55567cf56e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:146853b3e32229736b059ed01eb79eca1b2f114a0ba709e9b63c7b0a01ad4707 +size 40842 diff --git a/raw/rel-18/23_series/23700-25/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-25/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f72e11e448979857068716d511d3ca811635a498 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e947ccfcc7502075d566db891ce5990104b8a7df5ef139ed76f9fa390554c92c +size 7783 diff --git a/raw/rel-18/23_series/23700-25/605625ddfc3363a6205ab0d43b184eaf_img.jpg b/raw/rel-18/23_series/23700-25/605625ddfc3363a6205ab0d43b184eaf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45b2c7e36a405d9b863ba3dd7c837832ef0d1699 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/605625ddfc3363a6205ab0d43b184eaf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa66b05321ad857587889db361f8a2013bbb54a96ef06225f7325cb1cafc4371 +size 43075 diff --git a/raw/rel-18/23_series/23700-25/7156cf400ef0e19f9d06a5d0549834a3_img.jpg b/raw/rel-18/23_series/23700-25/7156cf400ef0e19f9d06a5d0549834a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efb4b8e0e2ef8b10c4964a706697c2d50621a32c --- /dev/null +++ b/raw/rel-18/23_series/23700-25/7156cf400ef0e19f9d06a5d0549834a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fa5a29e4e9a4f9a84ee1206bf5c1a6aaac4353e039ad18d05b2273ed7e01808 +size 68858 diff --git a/raw/rel-18/23_series/23700-25/8a94796989f4fcba2688c4faa7991538_img.jpg b/raw/rel-18/23_series/23700-25/8a94796989f4fcba2688c4faa7991538_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51f87318781213e8f4493daf7f3135e94f233f42 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/8a94796989f4fcba2688c4faa7991538_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b8e3a1089d63087746a7d613e8da67a8018e115ba82811bf88dd77ed83725a3 +size 86850 diff --git a/raw/rel-18/23_series/23700-25/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/raw/rel-18/23_series/23700-25/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..620d66430be8141d758c4cc7bea2985a0e63a611 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efe544a344362ea47b79ef17986349c5f7b713b935c74be630d871e7e1695033 +size 41942 diff --git a/raw/rel-18/23_series/23700-25/91c33f8e1713989e8192322ec2d1212b_img.jpg b/raw/rel-18/23_series/23700-25/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bd1a4330bfce46882c0908e2fcd5d363212f06c --- /dev/null +++ b/raw/rel-18/23_series/23700-25/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32d5342811bb02f872ab13274a1d7d3e9e272837b23c5129fc21245918f7fbbd +size 79649 diff --git a/raw/rel-18/23_series/23700-25/95c11a9c59e4ad4af81a0e635ceafe45_img.jpg b/raw/rel-18/23_series/23700-25/95c11a9c59e4ad4af81a0e635ceafe45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a85557195e0cb69f81b85c8278be617e54fc4ab2 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/95c11a9c59e4ad4af81a0e635ceafe45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:344494dbbb58fdc3694b77d34cd53e78c48cd2c66f6a147ce59e6ba269ac1b65 +size 47953 diff --git a/raw/rel-18/23_series/23700-25/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/raw/rel-18/23_series/23700-25/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ba0e0a9c212853fc0f5e8ad0ebbae3a104c0d86 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0165b5f4debd5cb9dc355edee8250eab4adc1539e9225ba959ccc987cd77c66 +size 79297 diff --git a/raw/rel-18/23_series/23700-25/a963ca41bde1669b18a4b783616f228b_img.jpg b/raw/rel-18/23_series/23700-25/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d81fa456ed2a20e61c98b59763e65902c7c592d5 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a1a1681876df398260d91e7fb175c7220c801f2fbb9e95fdb4d69dbbb99e99 +size 106583 diff --git a/raw/rel-18/23_series/23700-25/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/raw/rel-18/23_series/23700-25/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b660dbbe61e132bc391df7372ac5102faac343f5 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:219d4fb6bb27e2fdb49804785186231d1b581e7d11b4af7ee2652cc4f8011e04 +size 120067 diff --git a/raw/rel-18/23_series/23700-25/db5deafdae53dbc7d5972957f708c691_img.jpg b/raw/rel-18/23_series/23700-25/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b6e30edd4da9b5f490131bdfb0b84e10871a2ba --- /dev/null +++ b/raw/rel-18/23_series/23700-25/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:285713e60ea5322df64bbf484f9d476464bd20afbdcb561b5409c239f7f95201 +size 87033 diff --git a/raw/rel-18/23_series/23700-25/db730b8d3402ded94362bb3037b985ed_img.jpg b/raw/rel-18/23_series/23700-25/db730b8d3402ded94362bb3037b985ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99d77b2a68d207c81552c2ccd3c0db72da9553b3 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/db730b8d3402ded94362bb3037b985ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd67b41d483db9b71b8476c115a7406de9a293a728d6aaee88c0afee366a25c6 +size 26138 diff --git a/raw/rel-18/23_series/23700-25/ddfa5b18550d1a022a941e3c31843814_img.jpg b/raw/rel-18/23_series/23700-25/ddfa5b18550d1a022a941e3c31843814_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..273559075031303109c6cd4fa3f262daba4e027c --- /dev/null +++ b/raw/rel-18/23_series/23700-25/ddfa5b18550d1a022a941e3c31843814_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21c9e07b7a019ed7bddd0bf2b921b02d816dc3849f0e42c1e1838951ae5e6b12 +size 44788 diff --git a/raw/rel-18/23_series/23700-25/fcc757566216206ceddbd6c775e8db02_img.jpg b/raw/rel-18/23_series/23700-25/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52df0ec037d5cd745ff747e616f62a003d5269e5 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:955d3ca497e987ff4809a57d73af3e8990070ccb3d0d59d074809c330d5deb01 +size 100212 diff --git a/raw/rel-18/23_series/23700-25/raw.md b/raw/rel-18/23_series/23700-25/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e089bb004cf305b36af7a80f7770b10b1ab9f5a6 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/raw.md @@ -0,0 +1,3537 @@ + + +# 3GPP TR 23.700-25 V18.1.0 (2023-03) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on timing resiliency and TSC and URLLC enhancements (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 logo for 3GPP, featuring the letters '3GPP' in a stylized font with a red signal wave icon below the 'G'. + +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 ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms and abbreviations ..... | 10 | +| 3.1 Terms..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 Architectural Assumptions and Requirements..... | 10 | +| 4.1 Architectural Assumptions..... | 10 | +| 4.2 Architectural Requirements..... | 11 | +| 5 Key Issues ..... | 11 | +| 5.1 Key Issue #1: 5GS network timing synchronization status and reporting ..... | 11 | +| 5.1.1 Description ..... | 11 | +| 5.2 Key Issue #2: Time synchronization service enhancements..... | 11 | +| 5.2.1 Description ..... | 11 | +| 5.3 Key Issue #3: Support for controlling 5G time synchronization service based on subscription ..... | 12 | +| 5.3.1 Description ..... | 12 | +| 5.4 Key Issue #4: How to enable an AF to explicitly provide PER to NEF/PCF ..... | 12 | +| 5.4.1 Description ..... | 12 | +| 5.5 Key Issue #5: Interworking with TSN network deployed in the transport network ..... | 12 | +| 5.5.1 Description ..... | 12 | +| 5.6 Key Issue #6: Adapting downstream scheduling based on RAN feedback for low latency communication..... | 13 | +| 5.6.1 Description ..... | 13 | +| 6 Solutions..... | 13 | +| 6.0 Mapping of Solutions to Key Issues ..... | 13 | +| 6.1 Solution #1: Inform UE and AF about network timing synchronization status..... | 14 | +| 6.1.1 Introduction ..... | 14 | +| 6.1.2 Functional Description ..... | 14 | +| 6.1.3 Procedures ..... | 17 | +| 6.1.4 Impacts on services, entities and interfaces..... | 17 | +| 6.2 Solution #2: Burst arrival time adaptation ..... | 17 | +| 6.2.1 Introduction ..... | 17 | +| 6.2.2 Functional Description ..... | 17 | +| 6.2.3 Procedures ..... | 18 | +| 6.2.4 Impacts on services, entities and interfaces..... | 18 | +| 6.3 Solution #3: Timing synchronization resiliency and status reporting..... | 19 | +| 6.3.1 Introduction ..... | 19 | +| 6.3.2 Functional Description ..... | 19 | +| 6.3.3 Procedures ..... | 20 | +| 6.3.4 Impacts on services, entities and interfaces..... | 21 | +| 6.4 Solution #4: 5GC learning and reporting network timing synchronization status..... | 21 | +| 6.4.1 Introduction ..... | 21 | +| 6.4.2 Functional Description ..... | 22 | +| 6.4.2.1 Functional Description for 5GC learning network timing synchronization status ..... | 22 | +| 6.4.2.2 Functional Description for network timing synchronization status information ..... | 23 | +| 6.4.2.3 Functional Description for AF requested network timing synchronization status ..... | 23 | +| 6.4.2.4 Functional Description for network timing synchronization status reporting to UE(s) ..... | 25 | +| 6.4.3 Procedures ..... | 25 | +| 6.4.3.1 Procedure for AF requested network timing synchronization status ..... | 25 | +| 6.4.3.2 Procedure for UE provisioning network timing synchronization status..... | 28 | +| 6.4.4 Impacts on services, entities and interfaces..... | 30 | +| 6.5 Solution #5: Inform UE and AF about 5GS network timing synchronization status for PTP ..... | 31 | +| 6.5.1 Introduction ..... | 31 | + +| | | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.5.2 | Functional Description ..... | 31 | +| 6.5.3 | Procedures ..... | 31 | +| 6.5.4 | Impacts on services, entities and interfaces..... | 31 | +| 6.6 | Solution #6: Support for 5G Timing Exposure Enhancement. .... | 32 | +| 6.6.1 | Introduction ..... | 32 | +| 6.6.2 | General description..... | 32 | +| 6.6.3 | Procedures ..... | 32 | +| 6.6.4 | Impacts on services, entities and interfaces..... | 34 | +| 6.7 | Solution #7: RequestedCoverage area filters for time synchronization service..... | 34 | +| 6.7.1 | Introduction ..... | 34 | +| 6.7.2 | Functional Description ..... | 34 | +| 6.7.3 | Procedures ..... | 35 | +| 6.7.3.1 | Procedure for AF requested (g)PTP timing synchronization with Requested Coverage Area..... | 35 | +| 6.7.3.1a | Procedure for AF requested (g)PTP timing synchronization with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR ..... | 37 | +| 6.7.3.2 | Procedure for AF requested 5G access stratum timing synchronization with Requested Coverage Area..... | 39 | +| 6.7.3.2a | Procedure for AF requested 5G access stratum timing synchronization with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR..... | 40 | +| 6.7.4 | Impacts on services, entities and interfaces..... | 42 | +| 6.8 | Solution #8: AF Request of PER for QoS and Alt-QoS ..... | 42 | +| 6.8.1 | Introduction ..... | 42 | +| 6.8.2 | Functional Description ..... | 42 | +| 6.8.3 | Procedures ..... | 42 | +| 6.8.4 | Impacts on services, entities and interfaces..... | 43 | +| 6.9 | Solution #9: Interworking with TSN network deployed in the transport network..... | 43 | +| 6.9.1 | Introduction ..... | 43 | +| 6.9.2 | Functional Description ..... | 44 | +| 6.9.3 | Procedures ..... | 47 | +| 6.9.4 | Impacts on services, entities and interfaces..... | 47 | +| 6.10 | Solution #10: 5GC acting as a CUC for CNC in TN ..... | 48 | +| 6.10.1 | Introduction ..... | 48 | +| 6.10.2 | Functional Description ..... | 48 | +| 6.10.3 | Procedures ..... | 49 | +| 6.10.4 | Impacts on services, entities and interfaces..... | 51 | +| 6.11 | Solution #11: Interworking with TSN enabled N3 transport network for deterministic traffic delivery..... | 52 | +| 6.11.1 | Introduction ..... | 52 | +| 6.11.2 | Functional Description ..... | 52 | +| 6.11.3 | Procedures ..... | 54 | +| 6.11.4 | Impacts on services, entities and interfaces..... | 55 | +| 6.12 | Solution #12: Cross layer scheduling optimization based on RAN feedback..... | 55 | +| 6.12.1 | Introduction ..... | 55 | +| 6.12.2 | Functional Description ..... | 55 | +| 6.12.3 | Procedures ..... | 56 | +| 6.12.4 | Impacts on services, entities and interfaces..... | 57 | +| 6.13 | Solution #13: Pro-active RAN burst timing preference provision..... | 57 | +| 6.13.1 | Introduction ..... | 57 | +| 6.13.2 | Functional Description ..... | 57 | +| 6.13.3 | Procedures ..... | 58 | +| 6.13.4 | Impacts on existing services and interfaces..... | 59 | +| 6.14 | Solution #14: Assisted and Complement Timing Support..... | 60 | +| 6.14.1 | General ..... | 60 | +| 6.14.2 | Functional Description ..... | 60 | +| 6.14.3 | Procedures ..... | 61 | +| 6.14.3.1 | Procedures for (g)PTP time distribution ..... | 61 | +| 6.14.3.2 | Procedures for 5G access stratum time distribution ..... | 64 | +| 6.14.4 | Impacts on services, entities and interfaces..... | 67 | +| 6.15 | Solution #15: Burst arrival time adaptation ..... | 68 | +| 6.15.1 | Introduction ..... | 68 | +| 6.15.2 | Functional Description ..... | 68 | +| 6.15.3 | Procedures ..... | 68 | +| 6.15.4 | Impacts on services, entities and interfaces..... | 69 | + +| | | | +|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------| +| 6.16 | Solution #16: BAT adjustment during a QoS Flow setup or modification ..... | 69 | +| 6.16.1 | Introduction ..... | 69 | +| 6.16.2 | Functional Description ..... | 69 | +| 6.16.3 | Procedures ..... | 70 | +| 6.16.4 | Impacts on services, entities and interfaces ..... | 71 | +| 6.17 | Solution #17: DS-TT and NW-TT assisted 5GS synchronization error detection..... | 71 | +| 6.17.1 | Introduction ..... | 71 | +| 6.17.2 | Functional Description ..... | 72 | +| 6.17.3 | Procedures ..... | 72 | +| 6.17.4 | Impacts on services, entities and interfaces..... | 73 | +| 6.18 | Solution #18: Subscription based control of time synchronization service ..... | 73 | +| 6.18.1 | Introduction ..... | 73 | +| 6.18.2 | Functional Description ..... | 73 | +| 6.18.3 | Procedures ..... | 75 | +| 6.18.3.1 | Procedure for subscription based control of access stratum time synchronization service without AF request..... | 75 | +| 6.18.3.2 | Procedure for subscription based control of access stratum time synchronization service with AF request..... | 76 | +| 6.18.3.3 | Procedure for subscription based control of (g)PTP time synchronization service without AF request..... | 77 | +| 6.18.3.4 | Procedure for (g)PTP time synchronization service with AF request ..... | 78 | +| 6.18.4 | Impacts on services, entities and interfaces..... | 78 | +| 6.19 | Solution 19: Support for controlling 5G time synchronization service based on subscription..... | 79 | +| 6.19.1 | Introduction ..... | 79 | +| 6.19.2 | General description..... | 79 | +| 6.19.3 | Procedures ..... | 80 | +| 6.19.3.1 | AF requesting time synchronization service for targeted UE..... | 80 | +| 6.19.4 | Impacts on services, entities and interfaces..... | 81 | +| 6.20 | Solution #20: NG-RAN acting as CUC towards CNC of the N3 transport network..... | 81 | +| 6.20.1 | Introduction ..... | 81 | +| 6.20.2 | Functional Description ..... | 81 | +| 6.20.3 | Procedures ..... | 82 | +| 6.20.4 | Impacts on services, entities and interfaces..... | 82 | +| 6.21 | Solution #21: BAT adjustment by TSNCF to TSN in the transport network ..... | 82 | +| 6.21.1 | Introduction ..... | 82 | +| 6.21.2 | Functional Description ..... | 82 | +| 6.21.3 | Procedures ..... | 83 | +| 6.21.4 | Impacts on services, entities and interfaces..... | 84 | +| 6.22 | Solution #22: Transmission opportunities exposure ..... | 84 | +| 6.22.1 | Introduction ..... | 84 | +| 6.22.2 | Functional Description ..... | 84 | +| 6.22.3 | Procedures ..... | 85 | +| 6.22.4 | Impacts on services, entities and interfaces..... | 86 | +| 7 | Evaluation ..... | 86 | +| 7.1 | Key Issue #3: Support for controlling 5G time synchronization service based on subscription ..... | 86 | +| 7.2 | Key Issue #5: Interworking with TSN network deployed in the transport network ..... | 87 | +| 7.3 | Evaluation for KI #6: Adapting downstream scheduling based on RAN feedback for low latency communication ..... | 88 | +| 8 | Conclusions..... | 89 | +| 8.1 | Conclusion for KI #4: AF Request of PER for QoS and Alt-QoS..... | 89 | +| 8.2 | Key Issue #2: Time synchronization service enhancements..... | 89 | +| 8.3 | Conclusion for KI #5: Interworking with TSN network deployed in the transport network ..... | 90 | +| 8.4 | Key issue #6: Adapting downstream scheduling based on RAN feedback for low latency communication ..... | 91 | +| 8.5 | Conclusion for KI #1: 5GS network timing synchronization status and reporting..... | 92 | +| 8.6 | Conclusion for KI#3: Support for controlling 5G time synchronization service based on subscription ..... | 95 | +| Annex A: KI#1 related additional analysis ..... | | 98 | +| A.1 | Methods to notify RAN Time Synchronization Status towards the UE ..... | 98 | +| A.1.1 | Alternative 1: gNB provides a reference report ID within SIB..... | 98 | + +- A.1.2 Alternative 2:..... 100 +- A.1.3 Alternative 3: Broadcast the time change status in SIB ..... 101 + - A.1.3.1 Procedures ..... 101 + - A.1.3.1.1 Broadcast the time change status ..... 101 +- A.1.4 Alternative 4: Ciphered RAN Time Synchronization Status in SIB ..... 102 + - A.1.4.1 Procedures ..... 102 + - A.1.4.1.1 Broadcast of RAN Time Synchronization Status ..... 102 + - A.1.4.1.2 Delivery of ciphering keys to UEs for broadcast of RAN Time Synchronization Status ..... 103 + +**Annex B: Change history..... 105** + +# 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 objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for supporting 5G Timing Resiliency and TSC & URLLC enhancements for 5G System (5GS). The following aspects are covered: + +- Study how to report 5GS network timing synchronization status (such as divergence from UTC and 5GS network timing source degradation) to UEs and 3rd party applications (AFs): + - Study how RAN and 5GC learn about network 5GS network timing synchronization status to be able to inform UEs and AFs. + - Study if additional information needs to be provided to UEs and AFs to inform about 5GS network timing synchronization status. +- Study how to enable AFs to request time synchronization service in a specific coverage area and how to enforce the coverage area. +- Study how to control 5G time synchronization service based on subscription (i.e. introducing subscription parameter for time synchronization and enforcing it). +- Study how to enable an AF to explicitly provide PER to NEF/PCF. +- Study mechanisms for interworking with TSN transport networks. Study interworking mechanisms with TSN networks deployed in the transport network in order to support of E2E determinism and low latency communication and efficient N3 transmission. +- Study if there is a need for applications to adapt downstream scheduling in order for 5GS to meet really low latency (e.g. 2 msecs) requirement and if there is a need to have feedback from RAN (e.g. for application to consider DL packet transmission time slots to avoid buffering in the RAN) for this purpose. + +# --- 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 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [6] IEEE 802.1Qcc: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks -- Amendment 31: Stream Reservation Protocol (SRP) Enhancements and Performance Improvements". +- [7] IEEE Std 802.1AS: "IEEE Standard for Local and Metropolitan Area Networks-Timing and Synchronization for Time-Sensitive Applications". + +- [8] IEEE Std 1588: "Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". +- [9] 3GPP TR 22.878: "Feasibility Study on 5G Timing Resiliency System". +- [10] IEEE P802.1Qdj d0.2: "Configuration Enhancements for Time-Sensitive Networking". +- [11] 3GPP TS 38.321: "Medium Access Control (MAC) protocol specification". +- [12] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [13] 3GPP TS 38.300: "NR and NG-RAN Overall Description; Stage 2". +- [14] IEEE Std 802.1AB-2016: "IEEE Standard for Local and metropolitan area networks - Station and Media Access Control Connectivity Discovery". +- [15] ITU-T Recommendation G.8271.1: "Network limits for time synchronization in packet networks with full timing support from the network". +- [16] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [17] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)". + +# --- 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]. + +## 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]. + +# --- 4 Architectural Assumptions and Requirements + +## 4.1 Architectural Assumptions + +The following architectural assumptions apply: + +- The architecture defined in clause 4.4.8 of TS 23.501 [2] is as a baseline for the study. +- The TSN network deployed in the transport network supports the fully centralised model defined in IEEE 802.1Qcc [6]. + +NOTE: The transport network and 5GS may belong to the same operator or different operator. + +- Configuration and operation of the external synchronization network (i.e. timing synchronization provided by network external to 5GS network) and mitigation actions when time source fails or degrades are assumed to be outside the scope of 3GPP. +- This study is assumed to inherit the time synchronization architecture, methods, and exposure framework as defined in Rel-17 for 5G System in TS 23.501 [2]. This includes the support for time synchronization service based on 5G Access Stratum timing distribution, (g)PTP time sync based on IEEE Std 802.1AS [7] with 5GS acting as Grand-master or PTP time sync with 5GS acting as grand-master based on IEEE Std 1588 [8], along with support for DS-TT, NW-TT and TSCTSF in the time synchronization architecture. + +- How the 5GS network is time synchronized is assumed to be deployment specific thus outside the scope of this study (e.g. 5GS may use local GNSS server, may be time synchronized with an external clock using transport network synchronization protocols, etc.). +- The study assumes that sync network design complies with applicable performance requirements also during network rearrangements (for example, in the case of ITU-T Recommendation G.8271.1 [15], where budget is allocated to Sync network rearrangements). + +## 4.2 Architectural Requirements + +The following architectural requirements apply: + +- Solutions for timing resilience and time synchronization shall support the already defined time synchronization distribution methods as defined in clause 4.1. + +**Editor's note:** In the case of PTP-based time sync, for which IEEE Std 1588 [8] profile(s) to support timing resilience is FFS. + +- Solutions for main 5G time resiliency use cases shall at least support that the UEs are static to address financial and power grid scenarios, see TR 22.878 [9]), but may also support the scenarios where the UEs may not be static. + +# --- 5 Key Issues + +## 5.1 Key Issue #1: 5GS network timing synchronization status and reporting + +### 5.1.1 Description + +The objective of this Key Issue is to study the monitoring and reporting for timing synchronization status in 5GS. + +For this Key Issue the following areas should be studied: + +- Study how RAN and 5GC learn about 5GS network timing synchronization status to be able to inform UEs (e.g. application running in the UE), devices attached to the UE (i.e. that receive time information from 5GS) and AFs. +- Study how to report 5GS network timing synchronization status (such as divergence from UTC and 5GS network timing source degradation) to UEs (e.g. application running in the UE), devices attached to the UE (i.e. that receive time information from 5GS) and 3rd party applications (AFs). +- Study if additional information needs to be provided to UEs and AFs to inform about 5GS network timing synchronization status. + +## 5.2 Key Issue #2: Time synchronization service enhancements + +### 5.2.1 Description + +The objective of this Key Issue is to study enhancements for 5GS time synchronization considering the coverage area where the service is configured. + +For this Key Issue the following areas should be studied: + +- How to enable AFs to request time synchronization service in a specific coverage area and whether and how to enforce the coverage area. + +## 5.3 Key Issue #3: Support for controlling 5G time synchronization service based on subscription + +### 5.3.1 Description + +Control of time synchronization service based on UE subscription is important for the operator in managing time critical services such as smart grid or financial services. + +This key issue aims at studying how to control 5G time synchronization service based on subscription (i.e. introducing subscription parameter for time synchronization and enforcing it). + +The following technical issues will be studied: + +- How to authorize time synchronization service based on UE subscription. +- How to enforce time synchronization service on a per UE basis based on subscription. +- What parts of time synchronization service require a separate UE subscription (and authorization), if any. + +## 5.4 Key Issue #4: How to enable an AF to explicitly provide PER to NEF/PCF + +### 5.4.1 Description + +For this Key Issue the following areas should be studied: + +1. Enable an AF to explicitly provide the required PER to the NEF/PCF for QoS and Alt-QoS. + +## 5.5 Key Issue #5: Interworking with TSN network deployed in the transport network + +### 5.5.1 Description + +The objective of this Key Issue is to study interworking mechanisms with TSN networks deployed in the transport network in order to support of E2E determinism and low latency communication and efficient N3 transmission. + +This Key Issue applies only to 3GPP layer traffic flows that fall in the category of "periodic deterministic communication" as defined in clause 5.27.1a of TS 23.501 [2], i.e. for 3GPP layer traffic flows that can be associated with the TSCAI parameters - namely, burst arrival time, periodicity and flow direction. + +For this Key Issue the following areas should be studied: + +- a) The architecture enhancement to support the interworking between 5GS and TSN networks deployed in the transport network. +- b) What information are needed and how to collect these information from 5GS (e.g. NG-RAN, 5GC NF), so that the 5GS can interact with TSN network. Also, determine which 5GS entity is responsible to provide it to the TSN network deployed in the transport network. + +**NOTE:** In the context of interworking with a TSN-based transport network, 5GS is assumed to take the role of the CUC towards the CNC of the TSN transport network. It is assumed to rely on on-going work in IEEE for the interaction between CUC and CNC (P802.1Qdj), i.e. no new interface to the CNC will be specified as part of this work. + +## 5.6 Key Issue #6: Adapting downstream scheduling based on RAN feedback for low latency communication + +### 5.6.1 Description + +This key issue is targeting how for applications to adapt downstream scheduling in order for 5GS to meet really low latency (e.g. 2ms) requirement. + +For this key issue, the following areas should be studied: + +- Need for application transmission schedule adaptation and the ability to meet extremely low PDB for a QoS Flow from the 5GS perspective for periodic traffic streams (based on feedback from RAN WGs). +- How to enable the RAN to provide feedback to application for low latency communication (e.g. for application to consider DL packet transmission time slots to avoid buffering in the RAN) for this purpose. + +NOTE 1: The key issue needs to consider also the downlink scheduling in N3 transport network as studied under the Key Issue #x: Interworking with TSN network deployed in the transport network. + +NOTE 2: Although the focus is on downstream scheduling, any optimization on upstream scheduling should not be precluded if similar enhancement as for downstream scheduling applies. + +# --- 6 Solutions + +## 6.0 Mapping of Solutions to Key Issues + +**Table 6.0-1: Mapping of Solutions to Key Issues** + +| | Key Issue #1 | Key Issue #2 | Key Issue #3 | Key Issue #4 | Key Issue #5 | Key Issue #6 | +|-----------|--------------|--------------|--------------|--------------|--------------|--------------| +| Solutions | | | | | | | +| #1 | X | | | | | | +| #2 | | | | | | X | +| #3 | X | | | | | | +| #4 | X | | | | | | +| #5 | X | | | | | | +| #6 | | X | | | | | +| #7 | | X | | | | | +| #8 | | | | X | | | +| #9 | | | | | X | | +| #10 | | | | | X | | +| #11 | | | | | X | | +| #12 | | | | | | X | +| #13 | | | | | | X | +| #14 | X | | | | | | +| #15 | | | | | | X | +| #16 | | | | | | X | +| #17 | X | | | | | | +| #18 | | | X | | | | +| #19 | | | X | | | | +| #20 | | | | | X | | +| #21 | | | | | | X | +| #22 | | | | | | X | + +## 6.1 Solution #1: Inform UE and AF about network timing synchronization status + +### 6.1.1 Introduction + +This solution enables UE and AF to learn about network timing synchronization status, addressing KI #1. + +This solution makes the following assumptions: + +- NG-RAN is time synchronized with an external clock using transport network synchronization protocols or using a local GNSS receiver. +- NG-RAN can detect network timing synchronization degradation/improvement or timing synchronization failures locally, e.g. based on information provided by the transport network time synchronization protocols or based on information provided by the local GNSS receiver. The details of how NG-RAN detects timing synchronization degradation/improvement or timing synchronization failures are beyond the scope of 3GPP. +- If UPF/NW-TT is involved in providing timing information to UEs, UPF/NW-TT is time synchronized e.g. using transport network-based time synchronization protocols. +- UPF can detect network timing synchronization degradation/improvement or timing synchronization failures locally, e.g. based on information provided by the transport network time synchronization protocols. The details of how the UPF detects timing synchronization degradation/improvement or timing synchronization failures are beyond the scope of 3GPP. + +This solution addresses the following scenarios for 5G internal timing distribution: + +- 5GS distributes timing information to UEs using access stratum signalling. +- 5GS is acting as GM and distributes timing information to UEs using PTP or gPTP. + +### 6.1.2 Functional Description + +The solution is based on the following principles: + +- Informing 5GC and AFs about network timing synchronization status: +- Informing 5GC about RAN and UPF time synchronization status: + - TSCTSF subscribes for receiving RAN time synchronization status on a per RAN node level from NWDAF: + - NWDAF subscribes for RAN time synchronization status information from OAM. RAN time synchronization internal status information includes e.g. synchronization state, primary source information (e.g. type, quality, lock state), relevant PTP dataset members such as clock class (if PTP applies), the more general UTC traceability information, stability and clock accuracy. + - As an alternative option, TSCTSF subscribes for RAN time synchronization status information from OAM. RAN time synchronization status information includes e.g. synchronization state, primary source information (e.g. type, quality, lock state), relevant PTP dataset members such clock class (if PTP applies), the more general UTC traceability, stability and clock accuracy information. + - If UPF/NW-TT is involved in providing time information to DS-TT, TSCTSF subscribes for receiving time synchronization status from UPF (i.e. the status of the synchronization of the UPF with the transport network timing): + - Based on this, UPF reports transport network time synch status (e.g. relevant PTP dataset members such as clock class (if PTP applies), UTC traceability information and clock accuracy and stability) to TSCTSF. + +NOTE 1: UPF time synchronization status is only needed for the option when UPF/NW-TT is generating and timestamping messages for the DS-TT, which are forwarded from DS-TT adding residence time. + +- Determining UEs impacted by RAN time synchronization status degradation or improvement: + - TSCTSF subscribes to receive location information (RAN node granularity) from AMF for UEs that AF requested time synchronization for. + - TSCTSF requests UEs for which an AF requested time synchronization to perform a Registration Update if the UE is in CM-IDLE and detects a change in the RAN time synchronization status information (see below) for the current cell or when re-selecting to a different cell. This ensures that the CN is made aware of the location of a UE if the RAN time synchronization status changes while a UE that has been configured to receive time information is in CM-IDLE. +- Determining UEs impacted by UPF time synchronization status degradation or improvement (only for the case when UPF/NW-TT is involved in providing time information to DS-TT): + - If TSCTSF receives time synchronization status information for NG-RAN nodes from NWDAF (or from OAM directly) indicating time synchronization status degradation or improvement, then TSCTSF determines the UEs served by those NG-RAN nodes based on location information received from AMF. + - If TSCTSF receives time synchronization status information from UPF indicating time synchronization status degradation or improvement, then the TSCTSF determines the UEs for which the UPF/NW-TT or the DS-TT co-located with those UEs is configured to send (g)PTP messages. +- Inform AFs about network timing synchronization status degradation or improvement: + - If TSCTSF has determined UEs impacted by RAN or UPF time synchronization status degradation or improvement then TSCTSF informs the AF about the network timing synchronization status for those UEs as follows: + - For UEs impacted by RAN time synchronization status degradation or improvement for which the AF has requested 5G access stratum time distribution, TSCTSF determines if the Time synchronization error budget provided by the AF can be met given the change of clock accuracy for the RAN node serving the UE: + - If the sum of the clock accuracy of the RAN node serving a UE and the Uu time synchronization error budget previously calculated for the UE (see clause 5.27.1.9 of TS 23.501 [2]) exceeds the Time synchronization error budget provided by the AF, then the TSCTSF informs the AF that the time synchronization request cannot be fulfilled for the impacted UE. + - Otherwise, the TSCTSF informs the AF that the time synchronization request can be fulfilled again for the impacted UE. + - For UEs for which the AF has requested (g)PTP based time distribution and which are impacted by RAN and/or UPF time synchronization status degradation or improvement, TSCTSF determines if the Time synchronization error budget provided by the AF can be met given the change of clock accuracy for the RAN node serving the UE and/or the change of clock accuracy reported by the UPF: + - If the sum of: + - the clock accuracy of the RAN node serving a UE; + - the Uu time synchronization error budget previously calculated for the UE (see clause 5.27.1.9 of TS 23.501 [2]); and + - (if NW-TT is configured to act as Grandmaster on behalf of the UE/DS-TT) the clock accuracy reported by the UPF; + - exceeds the Time synchronization error budget provided by the AF, the TSCTSF informs the AF that the time synchronization request cannot be fulfilled for the impacted UE by indicating the PTP port state as Inactive for the related DS-TT PTP port. + - Otherwise, the TSCTSF informs the AF that the time synchronization request can be fulfilled again for the impacted UE by indicating the PTP port state as Active for the related DS-TT PTP port. + +**Editor's note:** Whether and how to provide network timing synchronization status for the case that an AF requested time synchronization service in a specific coverage area depends on the progress of the related key issue. + +- Informing UEs and devices attached to UE/DS-TT about network timing synchronization status: + - NG-RAN detects network timing synchronization degradation or failure based on implementation-specific means. + - NG-RAN informs UEs that receive 5G access stratum time about the time synchronization status by providing additional time synchronization status information (e.g. synchronization state, primary source description (e.g. type, quality, lock state), clock class and information about traceability to UTC, clock accuracy and stability) to UEs in SIB or using dedicated RRC. +- Reflecting RAN and UPF time synchronization status degradation and improvement in Announce messages sent by DS-TT and NW-TT: + - If TSCTSF has determined that UEs that are part of a PTP instance are impacted by RAN or UPF time synchronization status degradation or improvement for which the Time synchronization error budget provided by the AF can still be met (see above), then TSCTSF may update the clockQuality information sent in Announce messages (see IEEE 1588 [8] clause 7.6.2) for the PTP instance. For example, TSCTSF may change the clockQuality information to reflect that the clock has entered holdover state or to reflect a change in clock accuracy. + - If a DS-TT is configured to send Announce messages for the related PTP port, then TSCTSF changes the clockQuality information for the related PTP port using PMIC. + - If NW-TT is configured to send Announce messages on behalf of the DS-TT, then TSCTSF changes the clockQuality information for the related PTP port using UMIC. + - The handling of Announce messages follow existing procedures as described in TS 23.501 [2]. + +NOTE 2: ClockQuality information included in Announce message needs to be the same for all PTP ports of the same PTP instance. Therefore TSCTSF needs to configure the same clockQuality information for all UEs that are part of the same instance PTP instance even if only some UEs are impacted. For example, if one UE that is part of a PTP instance is served by a RAN node that lost synchronization to a primary reference time source (e.g. GNSS) and enters holdover mode, then the clockClass attribute needs to be changed for all UEs that are part of that PTP instance. Alternatively, disabling the impacted UE PTP port would preserve the other UEs' status. + +NOTE 3: Time synchronization status information provided to the UE using RRC is assumed to be used by the UE, e.g. for applications running on the UE or to provide time information to devices attached to the UE using implementation specific means. Time synchronization status information provided to UE/DS-TT by 5GC in (g)PTP (e.g. clock class, clock accuracy) is assumed to be consumed by devices attached to the UE to which UE/DS-TT forwards the (g)PTP frames/packets. + +- Deactivation and re-activation of (g)PTP based time synchronization due to RAN or UPF time synchronization status degradation and improvement: + - If TSCTSF has determined UEs impacted by RAN or UPF time synchronization status degradation (see above) for which the AF has requested (g)PTP based time distribution and for which the Time synchronization error budget provided by the AF cannot be met (see above) then TSCTSF temporarily removes the UE/DS-TT from the PTP instance: + - If the DS-TT is configured to send Sync, Follow\_Up and Announce messages for the related PTP instance, then TSCTSF deactivates the Grandmaster functionality in the DS-TT using PMIC (see also clause K.2.2.4 of TS 23.501 [2]) and removes the DS-TT from the PTP instance (see also clause K.2.2.1 of TS 23.501 [2]). + - If NW-TT is configured to send Sync, Follow\_Up and Announce messages on behalf of the DS-TT, then TSCTSF deactivates the Grandmaster functionality on behalf of the DS-TT in NW-TT using UMIC (see also clause K.2.2.4 of TS 23.501 [2]) and removes the DS-TT from the PTP instance (see also clause K.2.2.1 of TS 23.501 [2]). + - If TSCTSF has determined UEs impacted by RAN or UPF time synchronization status improvement for which the AF has requested (g)PTP based time distribution and for which the Time synchronization error budget provided by the AF can be met again (see above) then TSCTSF adds the DS-TT PTP port to the PTP instance again and also re-activates the Grandmaster functionality. + +### 6.1.3 Procedures + +### 6.1.4 Impacts on services, entities and interfaces + +#### NG-RAN: + +- Indicate RAN network timing synchronization status to UEs in RRC signalling or SIB9. + +#### UE: + +- Support receiving RAN network timing synchronization status information. +- Support performing a Registration request when RAN network timing synchronization status information changes while the UE is in CM-IDLE, if requested by TSCTSF. + +#### NWDAF: + +- Support subscribing for RAN time synchronization status information from OAM and providing RAN time synchronization status information to TSCTSF. + +#### TSCTSF: + +- Receive time synchronization status information from NWDAF (or OAM) and UPF. +- Subscribe for receiving location information from AMF. +- Support for requesting UEs to perform a Registration request if the UE detects a change in RAN network timing synchronization status information and the UE is in CM-IDLE. +- Inform AFs about time synchronization status (i.e. for which UEs time synchronization can be provided or not due to 5GS time synchronization status). +- Discover serving AMF for a UE. + +#### UPF: + +- Report transport network time synch status (e.g. primary source information and status, clock class UTC traceability and clock accuracy and stability) to TSCTSF if NW-TT is configured to generate (g)PTP messages (see case (a) in clause 5.27.1.7 of TS 23.501 [2]). + +## 6.2 Solution #2: Burst arrival time adaptation + +### 6.2.1 Introduction + +This solution enables the network to adjust the burst arrival time by signalling positive or negative offset values (e.g. +3 ms) to the AF so that the AF can adjust the burst sending time accordingly. + +Providing a burst arrival time offset value to an AF does not require 5GS and AF to be time synchronized. + +The solution builds on top of the QoS notification control mechanism (clause 5.7.2.4.1a (without Alternative QoS Profiles) or clause 5.7.2.4.1b (with Alternative QoS Profiles) of TS 23.501 [2]). In line with the assumptions for the existing QoS notification control mechanism, also this solution applies only if the application traffic is able to adapt to the change in QoS, i.e. if an application can tolerate that the PDB target is temporarily not met. + +### 6.2.2 Functional Description + +This solution is based on the following principles: + +- When requesting QoS for a flow as defined in clause 6.1.3.22 of TS 23.503 [4], AF may also indicate support of Burst arrival time adaptation to 5GS. AF also subscribes to receive notifications for successful resource allocation + +and when the QoS targets can no longer (or can again) be fulfilled as described in clause 6.1.3.18 of TS 23.503 [4]. + +- PCF forwards the support of Burst arrival time adaptation indication to SMF together with a PCC rule and other parameters (burst size, flow direction, burst periodicity), BAT (optional), if provided by the AF. PCF enables QoS Notification Control in the PCC rule. + +NOTE 1: If AF and 5GS are time synchronized, then the AF may additionally include BAT. + +- SMF creates TSCAI based on the received periodicity , flow direction and BAT (if provided by PCF). If PCF indicated support of Burst arrival adaptation, SMF includes support of Burst arrival time adaptation indication in TSCAI and signals TSCAI to NG-RAN as described in clause 4.3.3.2 of TS 23.501 [2]. As part of this, SMF also activates QoS notification control. +- At any time after the flow has started, if NG-RAN has received the indication of support of Burst arrival time adaptation in TSCAI for the given QoS Flow and NG-RAN determines that the PDB of the QoS profile cannot be fulfilled in DL direction, then NG-RAN sends a notification to SMF as defined in clause 5.7.2.4.1a of TS 23.501 [2] (if no Alternative QoS parameters have been provided) or as defined in clause 5.7.2.4.1b of TS 23.501 [2] (if Alternative QoS parameters have been provided). As part of the notification to SMF, NG-RAN may include a burst arrival time offset value. The burst arrival offset can take positive or negative values. + +NOTE 2: NG-RAN determines a relative burst arrival time offset value in reference to the current Burst Arrival Time experienced by RAN (i.e. in reference to when RAN currently receives bursts). Since it is a relative offset it can also be applied by the AF for adapting when it sends bursts, i.e. for the AF to adapt the burst sending time (see further below). + +NOTE 3: Since NG-RAN is aware of the radio resource situation NG-RAN can determine whether it would be possible to support the PDB of the QoS profile again if the burst was shifted in the time domain and calculate the required offset value. + +NOTE 4: The QoS notification procedure, which is reused by this solution already avoids too frequent signalling to the SMF (see NOTE 2 in clause 5.7.2.4.1b of TS 23.501 [2]). + +- The burst arrival time offset value is signalled from SMF to AF via PCF/TSCTSF/NEF using existing Notification control signalling. +- For downlink flows AF adapts the burst sending time based on the received offset. + +### 6.2.3 Procedures + +Existing procedures are reused (PDU session modification to signal support of Burst arrival time adaptation indication in TSCAI to NG-RAN; Notification control as defined in clause 5.7.2.4.1a or clause 5.7.2.4.1b of TS 23.501 [2], to signal burst arrival time offset value to PCF/TSCTSF/NEF/AF). + +### 6.2.4 Impacts on services, entities and interfaces + +AF: + +- Support of sending burst arrival time adaptation indication and receiving burst arrival time offset. + +NEF, PCF, TSCTSF, SMF: + +- Support of signalling burst arrival time adaptation indication and burst arrival time offset. + +NG-RAN: + +- Support of receiving burst time arrival adaptation indication, determining and signalling burst arrival time offset. + +## 6.3 Solution #3: Timing synchronization resiliency and status reporting + +### 6.3.1 Introduction + +This solution aims to address Key issue #1: 5GS network timing synchronization status and reporting. When 5GS provides timing resiliency service e.g. in the smart grid or financial sector, the timing synchronization status (such as divergence from UTC, timing source degradation) needs to be able to inform UEs (e.g. application running in the UE), devices attached to the UE (i.e. that receive time information from 5GS) and AFs. The AF can configure 5GS with the requirements about the timing resiliency service to meet when timing synchronization event happens. + +This solution makes the following assumptions: + +- UEs are consuming (g)PTP timing synchronization service from UPF/NW-TT that acts as Grand-master based on IEEE Std 802.1AS [7] or IEEE Std 1588 [8]; +- 5G GM may have different sources of time/frequency like GNSS signal, Synchronous Ethernet (SyncE), PTP transport network, PPS input, etc. It is assumed that UPF is synchronized with 5G GM by PTP compatible transport, etc. +- When UPF detects 5GS networking timing synchronization status for original 5G GM timing source, it sends the reporting to 5GC. Additionally, the UPF activates the timing synchronization configuration for PTP GM functionality as configured by TSCTSF in the case of degradation for original 5G GM timing source, so as to provide seamless time synchronization service for the UEs; or the UPF de-activates the timing synchronization configuration for PTP GM functionality as configured by TSCTSF in the case of recovery for original 5G GM timing source. + +NOTE: This solution assumes the time synchronization service is offered by (g)PTP based timing distribution, and can be used in combination with other solutions (e.g. sol#4 in clause 6.4) to address the case where the time synchronization service is offered based on 5G Access Stratum timing distribution. + +### 6.3.2 Functional Description + +This solution uses the following principles: + +- TSCTSF collects timing synchronization capability of UPF. The TSCTSF retrieves the timing synchronization capability via PMIC or UMIC, and then TSCTSF sends the collected information to AF if it subscribes: + - The timing synchronization capability can indicate holdover time or traceability capability information. For example, clock class, synchronization accuracy, holdover time parameters for the smart grid scenario, or UTC divergence scale and synchronization accuracy parameters for financial scenario. +- TSCTSF creates timing synchronization configuration on the UPF upon reception of AF request: + - TSCTSF receives timing synchronization requirement from AFs. The timing synchronization requirement consists of the time synchronization error budget. AF may also request to subscribe network timing synchronization status from TSCTSF (if it is a trusted AF, or via NEF). + - TSCTSF confirms that the 5GS can meet the requirement based on UPF reported timing synchronization capability. + - TSCTSF creates a timing synchronization configuration on UPF. + - With the timing synchronization configuration, the UPF detects and reports the networking timing synchronization status, and (de)activates the timing synchronization configuration for PTP GM functionality accordingly. +- UEs are consuming (g)PTP timing synchronization service from UPF/NW-TT that acts as grand-master based on IEEE Std 802.1AS [7] or IEEE Std 1588 [8]. +- When UPF detects networking timing synchronization status for original 5G GM timing source, it sends the status reporting to TSCTSF, and the TSCTSF forwards the reporting to AFs: + +- When UPF detects recovery for original 5G GM timing source, the UPF activates the timing synchronization configuration for PTP GM functionality as configured by TSCTSF, and the status reporting contains: 5GS timing synchronization enabled status, the timing source clock class, time validity. +- When UPF detects degradation or unavailable for original 5G GM timing source, the UPF de-activates the timing synchronization configuration for PTP GM functionality, and status reporting contains: 5GS timing synchronization disabled status, the timing source clock class, time validity. +- Inform the status to UE: + - When UPF detects networking timing synchronization status for original 5G GM timing source, the UPF/NW-TT may update (g)PTP attributes as configured by the TSCTSF via UMIC and sends the updated (g)PTP messages to the UE(s). + +### 6.3.3 Procedures + +Existing PDU Session establishment procedures are reused in timing synchronization capability configuration. Enhanced the procedure for exposure of capability of time sync service defined in clause 4.15.9.2 of TS 23.502 [3] to support exposure of timing synchronization capability. Existing timing distribution procedures are reused for UEs using (g)PTP messages. + +![Sequence diagram for Timing synchronization resiliency and status reporting. Lifelines: DS-TT/UE, RAN, UPF/NW-TT, SMF, PCF, TSCTSF, AF. The sequence shows: 0. PDU session establishment; 1. AF sends Timesync status request to TSCTSF; 2. TSCTSF determines UPF to provide time sync service; 3. TSCTSF creates time sync service configuration for UPF via PMIC/UMIC; 4. UPF/NW-TT detects time sync service degradation or recovery; 5. UPF/NW-TT sends Timesync status report to SMF, PCF, and TSCTSF; 6. TSCTSF updates time sync service configuration at UPF via PMIC/UMIC; 7. UPF/NW-TT sends Updated PTP messages to UE.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +``` + +sequenceDiagram + participant DS-TT/UE + participant RAN + participant UPF/NW-TT + participant SMF + participant PCF + participant TSCTSF + participant AF + + Note over DS-TT/UE, TSCTSF: 0.PDU session establishment + AF->>TSCTSF: 1.Timesync status request(with time resiliency requirement, target UE) + Note right of TSCTSF: 2.Determines the UPF to provide time sync service + TSCTSF->>UPF/NW-TT: 3.TSCTSF create time sync service configuration with time resiliency to UPF via PMIC/UMIC + Note left of SMF: 4. Detect the time sync service degradation or recovery + UPF/NW-TT->>SMF: 5.Timesync status report + Note right of UPF/NW-TT: 6.TSCTSF updates time sync service configuration at UPF via PMIC/UMIC + UPF/NW-TT->>DS-TT/UE: 7. Updated PTP messages to UE + +``` + +Sequence diagram for Timing synchronization resiliency and status reporting. Lifelines: DS-TT/UE, RAN, UPF/NW-TT, SMF, PCF, TSCTSF, AF. The sequence shows: 0. PDU session establishment; 1. AF sends Timesync status request to TSCTSF; 2. TSCTSF determines UPF to provide time sync service; 3. TSCTSF creates time sync service configuration for UPF via PMIC/UMIC; 4. UPF/NW-TT detects time sync service degradation or recovery; 5. UPF/NW-TT sends Timesync status report to SMF, PCF, and TSCTSF; 6. TSCTSF updates time sync service configuration at UPF via PMIC/UMIC; 7. UPF/NW-TT sends Updated PTP messages to UE. + +Figure 6.3.3-1: Timing synchronization resiliency and status reporting + +0. PDU session establishment procedure with UPF timing resiliency capability, UPF exchanges timing resiliency capability to TSCTSF via UMIC/PMIC. +1. AF requests for time synchronization service status, with time synchronization error budget for specific UE(s). +2. TSCTSF confirms that the 5GS can meet the requirement based on UPF reported timing synchronization capability, and determinates UPF to provide time sync service. +3. TSCTSF creates a timing synchronization configuration on UPF via PMIC/UMIC. + +Editor's note: It is FFS the information in timing synchronization configuration. + +4. The UPF detects and reports the networking timing synchronization status degradation or recovery, and (de)activates the timing synchronization configuration for PTP GM functionality accordingly. +5. When UPF detects degradation or recovery for original 5G GM timing source, the UPF sends the status reporting contains 5GS timing synchronization enabled or disable status, the timing source clock class, time validity to AF, via TSCTSF. +6. The TSCTSF may reconfigure (g)PTP operation at the UPF/NW-TT via PMIC/UMIC. +7. UEs are consuming (g)PTP timing synchronization service from UPF or RAN that acts as grand-master based on IEEE Std 802.1AS [7] or IEEE Std 1588 [8]. UPF/NW-TT sends updated PTP messages to the UE(s). + +### 6.3.4 Impacts on services, entities and interfaces + +UPF: + +- Support of signalling the timing synchronization capability to TSCTSF and AF. +- Support of reporting time synchronization status (e.g. holdover time or UTC divergence status) to TSCTSF. + +TSCTSF: + +- Support of receiving timing synchronization requirement from AFs. +- Support of timing synchronization with timing resiliency capability configuration. +- Support of timing synchronization status report to AFs. + +AF: + +- Support of providing timing synchronization requirement (time synchronization error budget) to TSCTSF, and receiving status reporting from TSCTSF. +- Support of subscribing timing synchronization capability. + +## 6.4 Solution #4: 5GC learning and reporting network timing synchronization status + +### 6.4.1 Introduction + +This solution is proposed to solve Key Issue #1: 5GS network timing synchronization status and reporting. + +In this key issue, the 5GS has a synchronization plane that synchronizes the 5G network functions (e.g. UPFs and RAN nodes) to a common time reference. The synchronization plane may have different sources of time/frequency like GNSS signal, Synchronous Ethernet (SyncE), PTP transport network, PPS input, etc. Thus, the following assumptions are considered for the synchronization plane: + +- NG-RAN is time synchronized with an external clock using transport network synchronization protocols or using a local GNSS receiver. +- NG-RAN is frequency synchronized (i.e. synchronization) with an external clock using transport network syntonization methods or using a local GNSS receiver. + +NOTE 1: The syntonization aspect is included in the assumptions because it may have an important role when the primary time reference source is lost but still the base station has a frequency reference (e.g. SyncE), then the holdover period can be longer. This is taking for example the long interruption failure scenarios considered in ITU-T Recommendation G.8271.1 [15], Appendix V. + +- NG-RAN can detect network timing synchronization degradation/improvement or timing synchronization failures locally, e.g. based on information provided by the transport network time or frequency synchronization methods or based on information provided by the local GNSS receiver. The details of how NG-RAN detects timing synchronization degradation/improvement or timing synchronization failures are beyond the scope of 3GPP. + +- UPF/NW-TT is time synchronized with an external clock using transport network-based time synchronization protocols if UPF/NW-TT is involved in providing time information to UEs/DS-TTs. +- UPF can detect network timing synchronization degradation/improvement or timing synchronization failures locally, e.g. based on information provided by the transport network time synchronization protocols. The details of how the UPF detects timing synchronization degradation/improvement or timing synchronization failures are beyond the scope of 3GPP. + +This solution addresses the following scenarios: + +- 5GS distributes time information to UEs using access stratum signalling. +- 5GS distributes time information to UEs using PTP or gPTP messages and the 5GS (i.e. UPF/NW-TT) is acting as the grand-master. + +NOTE 2: How the performance of the 5G clock distribution across the 5GS impact the external (g)PTP clock scenario is out of scope. + +From UE/DS-TT perspective, the 5GS time information received can be the primary time source the UE/DS-TT is consuming or can be a back-up time source alternative to a time source already present at the UE/DS-TT side. For both cases, this solution proposes enablers to allow the 5GC to retrieve 5GS network timing synchronization status from NG-RAN nodes and UPF/NW-TT (if needed) and report this information to subscribed UEs and AFs. + +### 6.4.2 Functional Description + +#### 6.4.2.1 Functional Description for 5GC learning network timing synchronization status + +The following principles are proposed to enable the 5GC to learn the network timing synchronization status at the NG-RAN and UPF/NW-TT: + +- The TSCTSF can retrieve and store timing synchronization status from NG-RAN and UPF/NW-TT. +- The NG-RAN timing synchronization status and the UPF/NW-TT timing synchronization status provide information for different time synchronization processes the UE/DS-TT(s) may have configured. The TSCTSF checks the time synchronization distribution method the target UE(s) have configured and determines the network functions to subscribe: + - The NG-RAN timing synchronization status informs the synchronization performance of the time distribution process the gNB and UE execute at Uu interface using access stratum signalling. + - On top of the access stratum time distribution method, if the UE/DS-TT receives 5G clock via (g)PTP with the UPF/NW-TT acting as a PTP grandmaster, the (g)PTP Announce messages already include GM quality attributes to determine UPF/NW-TT timing synchronization status at the UE/DS-TT. + +NOTE 3: If the UE/DS-TT is acting as a PTP grandmaster, it might not be required for the UE to receive gPTP or PTP messages over user plane (i.e. the UE and DS-TT use the 5G timing information and generate the necessary gPTP or PTP message for the end station as described in clause 5.27.1.1 of TS 23.501 [2]). In this case, there is no need for the UPF reporting time synch status to TSCTSF. + +- For TSCTSF subscription to NG-RAN timing synchronization status, three reporting alternatives via AMF are possible as follows: + - Alternative 1 for NG-RAN Time Sync Status reporting: The TSCTSF is responsible for determining the impacted UE(s) based on their location and the NG-RAN timing synchronization status reports received from AMF. + - Alternative 2 for NG-RAN Time Sync Status reporting: The AMF is responsible for determining the impacted UE(s) based on their location and the NG-RAN timing synchronization status reports received. Per impacted UE, the AMF forwards the notification to the TSCTSF subscribed to it. + - Alternative 3 for NG-RAN Time Sync Status reporting: The NG-RAN is responsible for determining the impacted UE(s) and sending the NG-RAN timing synchronization status reports to the AMF. Per impacted UE, the AMF forwards the notification to the TSCTSF subscribed to it. + +- For TSCTSF subscription to UPF/NW-TT timing synchronization status, three reporting alternatives are possible as follows: + - Alternative 1 for UPF/NW-TT Time Sync Status reporting: Using UPF event exposure service operation. The TSCTSF can be a new consumer of the service and node level signalling is used between UPF and TSCTSF. + - Alternative 2 for UPF/NW-TT Time Sync Status reporting: Using N4 Node Level procedures between the UPF and the SMF to report the update from the UPF. The TSCTSF subscribes to this information at the SMF on a per UE level or node level (between UPF and SMF or between SMF and TSCTSF). If UE level signalling is preferred, the SMF is responsible for determining the impacted UE(s) and notify the TSCTSF per UE level basis using PDU Session information available. + - Alternative 3 for UPF/NW-TT Time Sync Status reporting: Using UMIC to forward the status update from the UPF to the TSCTSF. Node level signalling is used between UPF and TSCTSF. +- The TSCTSF can determine time source degradation/failure/recovery events using the event flags and/or comparing numeric attributes included within the network timing synchronization status update received from NG-RAN and UPF/NW-TT. +- The TSCTSF can use the primary source quality attributes included within the NG-RAN and UPF/NW-TT timing synchronization status update to recalculate Uu time synchronization error budget for the time synchronization service offered to UE(s) to assist time synchronization enforcement (i.e. to notify the AF if the time synchronization error budget provided cannot be fulfilled, or to provide an updated Uu time synchronization error budget to the serving NG-RAN node). + +#### 6.4.2.2 Functional Description for network timing synchronization status information + +**Editor's note:** What type of information is needed and how it is used is FFS. + +#### 6.4.2.3 Functional Description for AF requested network timing synchronization status + +The following capabilities are proposed for AF requesting network timing synchronization status: + +- The AF requests network timing synchronization status monitoring from the NEF or TSCTSF (if it is a trusted AF). Existing Time synchronization APIs (i.e. Ntsctsf\_TimeSynchronization\_Config and Ntsctsf\_ASTI) are extended with Subscribe/Unsubscribe/Notify operations to enable the AF to perform this request for monitoring. The request may contain: + - Targets of the monitoring and filtering information (e.g. UE IDs, spatial validity, DNN/S-NSSAI, or time synchronization service identifier (i.e. PTP instance reference for the (g)PTP service scenario or time synchronization configuration ID for the ASTI service scenario)). + - The subscription events or information elements it wants to be notified. + - Request for UE side reporting (i.e. the UE(s) that are targets of the monitoring receive also the network timing synchronization status report) and reporting criterion (e.g. as soon as new information is available, when the UE is reachable). + - AF Identification. +- To determine the targets of the monitoring, AF request for network timing synchronization status provides the filter information. Four criteria to determine the targets of the network timing synchronization status exposure framework can be considered as summarized in Table 6.4.2.3 based on UE identities, known location, or connectivity. + +**Table 6.4.2.3: Criteria alternatives for network timing synchronization status exposure** + +| Criteria | Spatial validity | All UEs within the spatial validity | All UEs connected to the DNN/S-NSSAI | A UE or group of UEs | +|--------------------------------|----------------------------|-------------------------------------|--------------------------------------|-----------------------------------------------------| +| Target of Monitoring Reporting | an optional SUPI or any UE | any UE | any UE | one or more SUPI(s) or Internal Group Identifier(s) | +| Monitoring Filter information | spatial validity; | Spatial validity | DNN;
S-NSSAI; | | + +- If AF's request includes geographical area filter(s), the AF can provide them in spatial validity format (e.g. a civic address or shapes), or area(s) of interest. If the AF provides spatial validity, the NEF maps the spatial validity to validity area(s) (based on pre-configuration). Later, the TSCTSF or PCF determines the area(s) of interest based on validity area(s). The TSCTSF or AMF subscriptions use area of interest that may be the same as spatial validity condition or may be a subset of the spatial validity condition (e.g. a list of TAs or list of Cells) based on the latest known UE location. +- AMF or TSCTSF uses Location reports or UE presence in Area of Interest services at the AMF to identify the UE(s) to which the AF request with geographical area filter(s) applies, following the description of clause 6.4.2.1. +- If AF's request includes DNN/S-NSSAI filters, service events related to PDU Sessions (e.g. establishment or release) can be used at the SMF or TSCTSF to identify the UE(s) to which the request applies. +- Based on the network timing synchronization status reports the TSCTSF receives from NG-RAN and UPF/NW-TT (if applicable) nodes, the TSCTSF re-evaluates if the time synchronization service configured for the UE(s) impacted for which the AF has requested time synchronization service can be fulfilled: + - If TSCTSF determines that the service requirements (time synchronization error budget) cannot be met: + - For ASTI based time synchronization service, the TSCTSF updates access stratum time distribution indication to "disable" and forwards the attribute to the serving NG-RAN nodes for the impacted UEs via AMF (following Release-17 operation as described in clause 4.15.9.4 of TS 23.502 [3]). + - For (g)PTP based time synchronization service, the TSCTSF temporarily removes the UE/DS-TT from the PTP instance and reconfigures the UPF/NW-TT accordingly (following Release-17 operation described in clause K.2.2 of TS 23.501 [2]). The TSCTSF may update the clockQuality information (via PMIC if DS-TT or via UMIC if NW-TT is configured to send Announce messages) for the PTP instance (see IEEE 1588 [8] clause 7.6.2). + +NOTE 4: ClockQuality information included in Announce message needs to be the same for all PTP ports of the same PTP instance. Therefore, TSCTSF needs to configure the same clockQuality information for all UEs that are part of the same instance PTP instance even if only some UEs are impacted. For example, if one UE that is part of a PTP instance is served by a RAN node that lost synchronization to a primary reference time source (e.g. GNSS) and enters holdover mode, then the clockClass attribute needs to be changed for all UEs that are part of that PTP instance. Instead of changing the clockClass of all related UEs, an alternative way is to mark the impacted UE PTP port disabled and other UEs of the PTP instance unchanged. This is up to implementation. + +NOTE 5: When DS-TT is configured to generate Announce messages for one or more PTP ports, 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 as described in clause K.2.2.4 of TS 23.501 [2]). + +- If TSCTSF determines that the service requirements can be met: + - For ASTI based time synchronization service, the TSCTSF updates access stratum time distribution indication to "enable" and forwards the attribute to the serving NG-RAN nodes for the impacted UEs via AMF (following Release-17 operation as described in clause 4.15.9.4 of TS 23.502 [3]). + +- For (g)PTP based time synchronization service, the TSCTSF adds the UE/DS-TT to the PTP instance again (or changes the status of the impacted UE PTP port) and reconfigures the UPF/NW-TT accordingly (following Release-17 operation described in clause K.2.2 of TS 23.501 [2]). + +#### 6.4.2.4 Functional Description for network timing synchronization status reporting to UE(s) + +The following capabilities are proposed for UE(s) receiving network timing synchronization status: + +- Based on TSCTSF policies or the received AF's network timing synchronization status request as described in clause 6.4.2.3 and the time synchronization service the UE has configured, the TSCTSF is responsible for subscribing to network timing synchronization status as described in clause 6.4.2.1 (i.e. to the serving NG-RAN via AMF and if needed to the UPF/NW-TT via SMF or UPF directly). +- The trigger conditions of UE side reporting include, +- AF's request for UE side reporting + +**Editor's note:** Need for UE side reporting depends e.g. on how timing status information is reported to the UE and is FFS. + +- TSCTSF policies (e.g. whether there exists AF's request or not, TSCTSF reports status to UEs who have network timing synchronization services) +- UE's authorization (e.g. newly defining UE's subscription data stored in the UDM, which indicates whether the UE is authorized to receive the network timing synchronization status reports) + +**NOTE:** Whether and how to define UE's subscription data for the case that an UE authorize the network timing synchronization status reporting depends on the progress of the related key issue (i.e. KI#3). + +- When access stratum time distribution method is configured for the UE, the TSCTSF could configure the NG-RAN node (via AMF) to generate and send the NG-RAN timing synchronization status report to the UE(s) via SIB9/RRC signalling. The report shall be made available to DS-TT by the UE. +- When (g)PTP time distribution method is configured for the UE/DS-TT, the PTP attributes received via PTP announce messages are enough to describe the status of the UPF/NW-TT timing synchronization status. +- If the DS-TT is the last recipient of the network timing synchronization status reports (if only access stratum time distribution method is configured), it is up to the DS-TT implementation the determination of how the time source status update impacts the total degradation of the timing service the DS-TT is running. + +### 6.4.3 Procedures + +#### 6.4.3.1 Procedure for AF requested network timing synchronization status + +An overall procedure for AF requested network timing synchronization status is illustrated in Figure 6.4.3.1-1. Note this procedure is focusing on NG-RAN network timing synchronization status reporting and uses ASTI based time synchronization service as an example how the report can be exposed to the AF. For (g)PTP based time synchronization service, the exposure API should be Nxxx\_TimeSynchronization\_ConfigSubscribe/Notify in steps 1, 2, 9, 10, 16, and 17. + +![Sequence diagram illustrating the procedure for AF requested network timing synchronization status. The diagram shows interactions between NG-RAN, AMF, TSCTSF, NRF, NEF, and AF. The process starts with the AF sending a request to the NEF, which is then forwarded to the TSCTSF. The TSCTSF determines target UEs and network elements, then initiates reporting via the AMF and NG-RAN. The AMF subscribes to location reporting, and upon a primary source event, the AMF sends an N2 message to the NG-RAN. The NG-RAN then sends an N2 message to the AMF, which notifies the TSCTSF. The TSCTSF evaluates the time synchronization service and sends a response back to the NEF, which in turn sends a response to the AF.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant NRF + participant TSCTSF + participant AMF + participant NG-RAN + + Note right of AF: 1: Nnef_ASTISubscribe Request + AF->>NEF: 1: Nnef_ASTISubscribe Request + Note right of NEF: 2: Ntsctsf_ASTISubscribe Request + NEF->>TSCTSF: 2: Ntsctsf_ASTISubscribe Request + Note right of TSCTSF: 3: Determine the target UEs for AF's request (e.g., based on UE IDs, AoI, DNN/S-NSSAI) + TSCTSF->>NRF: 4: Nnrf_NFDiscovery_Request + Note right of TSCTSF: 4: TSCTSF determines the network elements (i.e., AMF or UPF/NW-TT) to contact + TSCTSF->>AMF: 5: Namf_NonUeN2MsgTransfer (AoI(s), NG-RAN TSS reporting request type) + AMF->>NG-RAN: 6: N2 message + Note right of AMF: 7: Namf_NonUeN2InfoSubscribe + AMF->>TSCTSF: 7: Namf_NonUeN2InfoSubscribe + Note right of TSCTSF: 8: If AoI filtering and NG-RAN node level subscription is preferred at the AMF, TSCTSF subscribes to AMF location services and AMF provides current known UE(s) location + TSCTSF->>NEF: 9: Ntsctsf_ASTISubscribe Response + NEF->>AF: 10: Nnef_ASTISubscribe Response + Note right of AMF: 11: AMF subscribes to UE location reporting + AMF->>AMF: 11: AMF subscribes to UE location reporting + Note right of NG-RAN: 12: Primary source event + NG-RAN->>AMF: 13: N2 message + AMF->>TSCTSF: 14: Namf_NonUeN2InfoNotify + Note right of TSCTSF: 15: TSCTSF reevaluates if the time synchronization service offered to the UE can be still satisfied (e.g., in terms of Uu time synchronization error budget) + TSCTSF->>NEF: 16: Ntsctsf_ASTINotify + NEF->>AF: 17: Nnef_ASTINotify + +``` + +Sequence diagram illustrating the procedure for AF requested network timing synchronization status. The diagram shows interactions between NG-RAN, AMF, TSCTSF, NRF, NEF, and AF. The process starts with the AF sending a request to the NEF, which is then forwarded to the TSCTSF. The TSCTSF determines target UEs and network elements, then initiates reporting via the AMF and NG-RAN. The AMF subscribes to location reporting, and upon a primary source event, the AMF sends an N2 message to the NG-RAN. The NG-RAN then sends an N2 message to the AMF, which notifies the TSCTSF. The TSCTSF evaluates the time synchronization service and sends a response back to the NEF, which in turn sends a response to the AF. + +**Figure 6.4.3.1-1: Procedure for AF requested network timing synchronization status** + +- 1-2. The AF sends network timing synchronization status request to the NEF or TSCTSF. The request may include targets of the monitoring and filtering information (as described in Table 6.4.2.3), the subscription events or information elements it wants to be notified, request for UE side reporting and reporting criterion, AF Identification. + +If the request is received at the NEF, it checks whether the AF is authorized to send the request and forwards the request to the TSCTSF. + +If spatial validity is included in AF's request, NEF maps the spatial validity to list of TA(s) or Cell(s). + +- Based on the filters the request contains, the TSCTSF determines the target(s) UE(s) for the request. +- The TSCTSF determines the AMF(s) and the UPF/NW-TT nodes (if applicable) that needs to initiate network timing synchronization status subscription considering the time synchronization service the target UE(s) have configured in the 5GS. + +To determine the serving AMF(s), the TSCTSF can use different methods such as: + +- Method 1: NRF services (Nnrf\_NFDiscovery, illustrated in Figure 6.4.3.1-1) or UDM UE Context Management services (Nudm\_UECM\_Get) to discover the AMF of the target TAI(s) or UE(s). This method enables the TSCTSF to directly interact with the AMF to retrieve NG-RAN Time Sync Status reports at UE or NG-RAN node level. +- Method 2: AM policy procedures via PCF. The TSCTSF can discover the PCF for the UE using the BSF and interact with the AMF via PCF AM Policy services. This method only enables the TSCTSF to retrieve NG-RAN Time Sync Status reports at UE level. + +To determine the serving UPF/NW-TT(s) the TSCTSF can use the PTP instance information already configured for the (g)PTP service provided to the UE(s). That is, the TSCTSF can reuse the time synchronization capability exchange via UMIC with the UPF/NW-TT (e.g. attribute List of UEs associated with the User-Plane Node ID in Table 5.2.6.25.8-1 of TS 23.502 [3]). + +- 5-7. The TSCTSF request NG-RAN timing synchronization status (TSS) subscription to the AMF. First the TSCTSF may send the configuration of the TSS reporting to the NG\_RAN via AMF using Namf\_NonUeN2MsgTransfer. The AMF interacts with the NG-RAN to configure the reporting. Finally, the TSCTSF initiates the subscription to TSS reporting at the AMF. Three alternatives are possible (as described in clause 6.4.2.1): + - Alternative 1 for NG-RAN Time Sync Status reporting (option illustrated in Figure 6.4.3.1-1): TSCTSF subscribes for receiving NG-RAN timing synchronization status at the AMF on a per RAN node level. The AMF forwards the received status report from the NG-RAN node to the TSCTSF. The TSCTSF is responsible for determining the impacted UE(s) based on their location. + - Alternative 2 for NG-RAN Time Sync Status reporting: TSCTSF subscribes for receiving NG-RAN timing synchronization status at the AMF on a per UE level. The AMF is responsible for determining the impacted UE(s) based on the NG-RAN node level report received and UE(s) location. Per impacted UE, the AMF forwards the NG-RAN time synchronization status report to the TSCTSF subscribed to it. + - Alternative 3 for NG-RAN Time Sync Status reporting: TSCTSF subscribes for receiving NG-RAN timing synchronization status at the AMF on a per UE level. The NG-RAN is responsible for determining the impacted UE(s) and sending the NG-RAN timing synchronization status reports to the AMF. Per impacted UE, the AMF forwards the notification to the TSCTSF subscribed to it. + +If (g)PTP time distribution is configured for a UE, the TSCTSF request UPF/NW-TT timing synchronization status subscription to the SMF (at UE level or node level) or directly at the UPF/NW-TT (node level), as described in clause 6.4.2.1. + +8. If AF's request contains a spatial validity filter and the TSCTSF subscribes to node level information at the AMF in step 4, the TSCTSF is responsible for determining if a serving NG-RAN timing synchronization status update received at node level signalling impacts the UE(s) matching AF's request condition. To support this, the TSCTSF subscribes to location services at the AMF (e.g. Namf\_EventExposure service for events like Location Report (TAI, Cell ID) or UE moving in or out of a subscribed "Area Of Interest"). + +If AF's request contains a spatial validity filter and (g)PTP time distribution is configured for a UE, the TSCTSF is responsible of determining the UE(s) matching AF's request condition based in their location and the serving UPF/NW-TT for the PTP instance. + +- 9-10. The TSCTSF responds the AF. + +11. The AMF subscribes to UE(s) location services reporting from NG-RAN node using Location reporting Request procedure. + +12. The NG-RAN node detects a primary source event (e.g. degradation, failure, recovery). + +13. The NG-RAN node notifies the AMF providing a NG-RAN timing synchronization status report. The report message may include, for example, the gNB node information, time status information, relevant UE information. The gNB node information indicates which 5G access stratum time distribution is impacted. The time status information might include the clock status in gNB node, and it can refer to the time service indication (disabled, enabled and holdover status). The relevant UE info represents those UE using the involved gNB access stratum time. + +**Editor's note:** The actual details of the parameters to be provided by NG-RAN and to AF are FFS. + +14. The AMF forwards the NG-RAN timing synchronization status report to the TSCTSF. If TSCTSF subscription is at NG-RAN node level (alternative 1 for NG-RAN Time Sync Status reporting, illustrated in Figure 6.4.3.1-1), the AMF can directly forward the report received from NG-RAN node. If TSCTSF subscription is at UE level (alternative 2 and 3 for NG-RAN Time Sync Status reporting), the AMF or RAN determines the UE(s) impacted by the status update received from NG-RAN before notifying the TSCTSF (e.g. based on UE locations or UE identities). +15. The TSCTSF reevaluates if the time synchronization service configured for the UE(s) impacted can still be fulfilled ( time synchronization error budget provided by AF). If the service requirements cannot be met, then the TSCTSF may temporarily deactivate time synchronization service for the impacted UE(s). + +For ASTI based time synchronization service, this implies the TSCTSF updates access stratum time distribution indication to "disable" and forwards the attribute to the serving NG-RAN nodes for the impacted UEs via AMF (following Release-17 operation as described in clause 4.15.9.4 of TS 23.502 [3]). + +For (g)PTP based time synchronization service (not illustrated in Figure 6.4.3.1-1), this implies the TSCTSF temporarily removes the UE/DS-TT from the PTP instance or marks the impacted DS-TT ports disabled and reconfigures the UPF/NW-TT accordingly (following Release-17 operation described in clause K.2.2 of TS 23.501 [2]). + +- 16-17. The TSCTSF stores the network timing synchronization status update received and notifies the subscribed AF via exposure framework. If the notification from gNB provides the time status information (e.g. disabled, enabled and holdover status, actual status information values is FFS), TSCTSF stores the time status information locally. If the notification from the gNB has triggered the (de)activation of time synchronization service for the impacted UE(s), the TSCTSF notifies the AF. + +Figure 6.4.3.1-1 illustrates the NG-RAN timing synchronization status subscription example, if the TSCTSF requires UPF/NW-TT timing synchronization status (determined in step 3), a similar signalling exchange between UPF/NW-TT, SMF, and TSCTSF is required to subscribe to UPF/NW-TT updates (directly or via the SMF), as described in clause 6.4.2.1. + +#### 6.4.3.2 Procedure for UE provisioning network timing synchronization status + +An overall procedure for UE provisioned network timing synchronization status is illustrated in Figure 6.4.3.2-1. + +![Sequence diagram illustrating the procedure for UE provisioning network timing synchronization status. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, TSCTSF, NEF, and AF. The process starts with an AF request for network timing synchronization status. The NG-RAN detects a primary source event and sends a TSS Report to the AMF. The AMF forwards this to the TSCTSF via Namf_NonUeN2InfoNotify. The TSCTSF decides to notify the UE. Depending on the UE's CM and RRC state, the TSCTSF may initiate a network triggered procedure. The AMF then sends a Namf_Communication_N1N2MessageTransfer to the NG-RAN. Two options are shown: 7a. The AMF configures the NG-RAN to send notifications directly via SIB9 or RRC signaling (N2 message to NG-RAN, RRC signaling to UE). 7b. The AMF uses NAS signaling to send notifications (N2 message to NG-RAN, DL NAS Transport to UE).](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant TSCTSF + participant AMF + participant NG-RAN + participant UE/DS-TT + + Note right of AF: 1: AF request for network timing synchronization status is already configured as shown in clause 6.4.3.1 + AF->>NEF: + Note left of NG-RAN: 2: Primary source event + NG-RAN->>AMF: 3: NGAP: TSS Report + AMF->>TSCTSF: 4: Namf_NonUeN2InfoNotify + Note right of TSCTSF: 5: TSCTSF decides to notify the UE the primary source event + Note left of AMF: Depending on UE's CM and RRC state, the TSCTSF may initiate a network triggered procedure to reach the UE and include a report or notification to forward to the UE + AMF->>NG-RAN: 6: Namf_Communication_N1N2MessageTransfer + Note left of NG-RAN: 7a. Option a) The AMF configures the NG-RAN to send notifications to the UE directly via SIB9 or RRC signaling + AMF->>NG-RAN: N2 message + NG-RAN->>UE/DS-TT: RRC signaling + Note left of NG-RAN: 7b. Option b) The AMF uses NAS signaling to send notifications to the UE + AMF->>NG-RAN: N2 message + NG-RAN->>UE/DS-TT: DL NAS Transport + +``` + +Sequence diagram illustrating the procedure for UE provisioning network timing synchronization status. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, TSCTSF, NEF, and AF. The process starts with an AF request for network timing synchronization status. The NG-RAN detects a primary source event and sends a TSS Report to the AMF. The AMF forwards this to the TSCTSF via Namf\_NonUeN2InfoNotify. The TSCTSF decides to notify the UE. Depending on the UE's CM and RRC state, the TSCTSF may initiate a network triggered procedure. The AMF then sends a Namf\_Communication\_N1N2MessageTransfer to the NG-RAN. Two options are shown: 7a. The AMF configures the NG-RAN to send notifications directly via SIB9 or RRC signaling (N2 message to NG-RAN, RRC signaling to UE). 7b. The AMF uses NAS signaling to send notifications (N2 message to NG-RAN, DL NAS Transport to UE). + +**Figure 6.4.3.2-1: Procedure for UE provisioning network timing synchronization status** + +1. The AF sends network timing synchronization status request to the NEF or TSCTSF. The subscription configuration of NG-RAN nodes and UPF/NW-TT (if applicable) is performed as described in clause 6.4.3.1. +2. The NG-RAN node detects a primary source event (e.g. degradation, failure, recovery). +3. The NG-RAN node notifies the AMF providing a NG-RAN timing synchronization status report. The TSCTSF may have already configured the NG-RAN node to provide updates to the UE directly via SIB9/RRC signalling, in that case, steps 5 7 can be skipped. +4. The AMF forwards the NG-RAN timing synchronization status report to the TSCTSF. If TSCTSF subscription is at NG-RAN node level (alternative 1 for NG-RAN Time Sync Status reporting, illustrated in Figure 6.4.3.2-1), the AMF can directly forward the report received from NG-RAN node. If TSCTSF subscription is at UE level (alternative 2 and 3 for NG-RAN Time Sync Status reporting), the AMF or RAN determines the UE(s) impacted by the status update received from NG-RAN before notifying the TSCTSF (e.g. based on UE locations or UE identities). +5. The TSCTSF determines the UE(s) to notify and the method to use to forward the network timing synchronization status notification. + +Similar to step 15 in clause 6.4.3.1, when the TSCTSF receives a status notification reevaluates if the time synchronization service configured for the UE(s) impacted can still be fulfilled (time synchronization error budget). If the service requirements cannot be met, then the TSCTSF may temporarily deactivate time synchronization service for the impacted UE(s) following Release-17 operation. + +6. The TSCTSF can initiate a network triggered procedure to forward the notification to the UE via AMF. When the AMF receives the notification, it will forward it to the NG-RAN node. Two alternatives are possible: send the report to the UE using RRC signalling or NAS signalling. +- 7a. If RRC signalling is preferred, the AMF sends a N2 message to forward the UE's report from AMF to the NG-RAN node. The serving NG-RAN node forwards the network timing synchronization status to the UE using RRC signalling. +- 7b. If NAS signalling is preferred, the AMF initiates DL NAS Transport procedure to forward the UE's report transparently via the NG-RAN node to the UE using NAS signalling. + +### 6.4.4 Impacts on services, entities and interfaces + +#### UE: + +- Support receiving RAN timing synchronization status information. +- Support performing a registration request when RAN network timing synchronization status information changes while the UE is in CM-IDLE, if requested by TSCTSF or AMF. + +#### DS-TT: + +- Support receiving network timing synchronization status information. + +#### NG-RAN: + +- Indicate NG-RAN network timing synchronization status to UEs via SIB9 or RRC signalling. +- Report NG-RAN network timing synchronization status to AMF. + +#### AMF: + +- Subscribe for network timing synchronization status reports from NG-RAN nodes. +- Report NG-RAN timing synchronization status to the TSCTSF (at UE level or NG-RAN node level). + +#### SMF: + +- If SMF is involved in UPF/NW-TT timing sync status reporting, subscribe for network timing synchronization status reports from UPF/NW-TT nodes. +- Report UPF/NW-TT timing synchronization status to the TSCTSF (at UE level or UPF node level). + +#### TSCTSF: + +- Receive network timing synchronization status information from NG-RAN (via AMF) and UPF/NW-TT (via SMF or directly). +- Discover serving AMF for a UE. +- Subscribe for receiving UE's location, UE's presence in Area of Interest, and reachability information from AMF. +- Subscribe for receiving UE's PDU Session events from SMF. +- Support for requesting UEs to perform a Registration request if the UE detects a change in RAN network timing synchronization status information and the UE is in CM-IDLE. +- Inform AFs about network timing synchronization status and time synchronization service status for the impacted UE(s). +- Initiate network-triggered procedures to reach the UE if is in CM-IDLE. +- Inform UE about RAN timing synchronization status using NAS signalling, or configuration of NG-RAN node to notify the UE via RRC/SIB. + +#### UPF: + +- Report transport network timing synchronization status to TSCTSF (directly or via SMF). + +#### AF: + +- Request for network timing synchronization status. +- Support receiving network timing synchronization status information. + +## 6.5 Solution #5: Inform UE and AF about 5GS network timing synchronization status for PTP + +### 6.5.1 Introduction + +The solution is proposed to solve Key Issue #1: 5GS network timing synchronization status and reporting. + +This solution addresses the following scenarios: + +- 5GS is acting as Bridge to distribute time information to UEs using PTP or gPTP, as defined in clause 5.27.1.7 of TS 23.501 [2]. + +This solution makes the following assumptions: + +- The UE/DS-TT, NG-RAN, UPF/NW-TT are synchronized with the 5G GM (i.e. the 5G internal system clock) as specified in TS 23.501 [2] and TS 38.331 [5]. +- The UE/DS-TT and UPF/NW-TT handle the (g)PTP message as TS 23.501 [2]. + +### 6.5.2 Functional Description + +This solution only get time synchronization status from UPF/NW-TT. To enable NG-RAN time synchronization status case, this solution can be used in combination with other KI#1 solutions (like solution #1 or solution #4). + +The solution is based on the following principles: + +- The AF/NEF subscribes the time synchronization status with TSCTSF. +- TSCTSF subscribes for receiving time synchronization status from UPF/NW-TT via PMIC/UMIC (i.e. the status of the synchronization of the UPF/NW-TT with the 5G GM and PTP GM): + - According to the status subscription, the UPF/NW-TT reports 5G GM and PTP GM (e.g. clock class and traceability) to TSCTSF/TSN AF via PMIC/UMIC. +- When TSCTSF receives the time synchronization status, it determines the impacted PTP ports and related UE (i.e. AF sessions): + - The TSCTSF notifies the AF with the time synchronization status. + +### 6.5.3 Procedures + +The exchange of PMIC/UMIC between TSCTSF and UE/DS-TT and between TSCTSF and UPF/NW-TT is specified in clause 5.28.3 of TS 23.501 [2]. + +### 6.5.4 Impacts on services, entities and interfaces + +TSCTSF: + +- Receive time synchronization status from UPF/NW-TT. +- Inform AFs about time synchronization status. + +UPF/NW-TT: + +- Report 5G GM or PTP GM time sync status (e.g. clock class and UTC traceability) to TSCTSF via PMIC/UMIC. + +## 6.6 Solution #6: Support for 5G Timing Exposure Enhancement. + +### 6.6.1 Introduction + +The solution enables AF to request time synchronization service in a specific coverage area. 5GS enforces the time synchronization service according to the requested coverage area. + +### 6.6.2 General description + +- The AF requested time synchronization service is for one UE or a group of UE. +- UEs get time synchronization service by receiving 5GS access stratum time or time-synchronized UPF/NW-TT. + +The general idea of the solution is structured as follows: + +- AF requests time synchronization service for targeted UE(s), and the coverage area info is included in the request. +- NEF authorizes the AF request and sends it to TSCTSF. +- TSCTSF determines the time source for the requested AF. +- AMF reports UE location information to PCF when the PCF initiates the AM policy association modification. +- If UE moves out of the coverage area, the requirements of time synchronization service in the AF request will not be met any more. When TSCTSF receives the notification from AMF about UE leave, TSCTSF will deactivate the time synchronization service and the RAN node will stop to provide 5G access stratum information to the UE. +- The coverage area information in the AF request can be per cell, per RAN nodes or a geographical area. If the requested coverage area information is presented in per cell or per RAN nodes, TSCTSF will update the access stratum time indication combined with coverage area information. If the requested area is a geographical area, it is assumed that the requested information can be interpreted by NEF to a 3GPP defined location information. It may be a pre-configured area mapping or depending on specific implement. + +### 6.6.3 Procedures + +Flow chart for the AF requested time synchronization service in a specific area is illustrated as following. + +![Sequence diagram showing the interaction between AMF, PCF, BSF, TSCTSF, NEF, and AF for requesting time synchronization service. The diagram includes 9 steps: 1. AM Policy Association Establishment; 2. Nnef_TimeSynchronization_ASTI Create/Update/Delete (coverage area info); 3. Ntsctsf_TimeSynchronization_ASTI Create/Update/Delete request; 4. Nbsf_Management_Subscribe/Notify; 5. Npcf_AMPolicyAuthorization_Create/Update request (UE location info needed); 6. AM Policy Association Modification initiated by the PCF (UE location information); 7. Npcf_AMPolicyAuthorization_Create/Update response; 8. Ntsctsf_TimeSynchronization_ASTI Create/Update/Delete Response; 9. Nnef_TimeSynchronization_ASTI Create/Update/Delete Response.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant PCF + participant BSF + participant TSCTSF + participant NEF + participant AF + + Note over AMF, BSF: 1. AM Policy Association Establishment + AF->>NEF: 2.Nnef_TimeSynchronization_ASTI Create/Update/Delete (coverage area info) + NEF->>TSCTSF: 3.Ntsctsf_TimeSynchronization_ASTI Create/Update/Delete request + TSCTSF->>BSF: 4.Nbsf_Management_Subscribe/Notify + BSF->>PCF: 5.Npcf_AMPolicyAuthorization_Create/Update request (UE location info needed) + Note over AMF, PCF: 6.AM Policy Association Modification initiated by the PCF (UE location information) + PCF->>TSCTSF: 7.Npcf_AMPolicyAuthorization_Create/Update response + TSCTSF->>NEF: 8.Ntsctsf_TimeSynchronization_ASTI Create/Update/Delete Response + NEF->>AF: 9.Nnef_TimeSynchronization_ASTI Create/Update/Delete Response + +``` + +Sequence diagram showing the interaction between AMF, PCF, BSF, TSCTSF, NEF, and AF for requesting time synchronization service. The diagram includes 9 steps: 1. AM Policy Association Establishment; 2. Nnef\_TimeSynchronization\_ASTI Create/Update/Delete (coverage area info); 3. Ntsctsf\_TimeSynchronization\_ASTI Create/Update/Delete request; 4. Nbsf\_Management\_Subscribe/Notify; 5. Npcf\_AMPolicyAuthorization\_Create/Update request (UE location info needed); 6. AM Policy Association Modification initiated by the PCF (UE location information); 7. Npcf\_AMPolicyAuthorization\_Create/Update response; 8. Ntsctsf\_TimeSynchronization\_ASTI Create/Update/Delete Response; 9. Nnef\_TimeSynchronization\_ASTI Create/Update/Delete Response. + +**Figure 6.6.3-1: AF requesting time synchronization service in a specific area** + +1. AM policy association establishment is finalized during UE registration procedure. +2. The procedure is triggered by the AF request to influence the 5G time distribution. The coverage area information is added in step 2 when the AF requests the service in a specific area. +3. The NEF authorizes the request and invokes the operation with the corresponding TSCTSF. TSCTSF calculates the Uu time synchronization error budget if the AF provides the error budget requirements. The coverage area information is considered together with the 5G access stratum time distribution indication by the TSCTSF. If 5G access stratum time distribution is enabled in the coverage area, it can meet the request. If another gNB not in the coverage area or time-synchronized UPF/NW-TT can meet the request requirements, it provides reference time to the targeted UE in the area to enforce AF request if possible. +4. If the 5G access stratum time distribution parameters in UDR are associated with a DNN/S-NSSAI for the PCF for the UE may discover the PCF for the PDU Session using SUPI and (DNN, S-NSSAI) as parameters. +5. TSCTSF selects for the PCF that handles the AM Policy Association of the targeted UE with SUPI (step 4) as an input parameter and informs the PCF to consider UE location information when determining AM policy. +6. If the TSCTSF sends multiple time synchronization error budgets for a given UE, the PCF would pick the most stringent budget. The PCF takes a policy decision and then it may initiate an AM Policy Association Modification procedure. In the step, the AMF is responsible for reporting UE location information to PCF. When PCF receives UE location information, it determines to provide which 5GS access stratum time information to UE based on time synchronization date sent by TSCTSF. As part of this, the 5G access stratum time distribution indication and the Uu time synchronization error budget are provided to NG-RAN. Based on this, NG-RAN provides the 5GS access stratum time to the UE according to the Uu time synchronization error budget as provided by the TSCTSF (if supported by UE and NG-RAN). +7. The PCF of the UE replies to the TSCTSF with the result of Npcf\_AMPolicyAuthorization operation. +8. The TSCTSF responds to the NEF request in step 3. +9. The NEF informs the AF about the result of the operation in step 2. + +### 6.6.4 Impacts on services, entities and interfaces + +AF: + +- Support to include the coverage area information in the time synchronization service request. + +TSCTSF: + +- Support to include the coverage area information in the time synchronization service request. +- Update the 5G access stratum time distribution indication based on coverage area information. +- Inform the PCF to consider UE location information. + +PCF: + +- Combine UE location information when AM policy decision. + +## 6.7 Solution #7: Requested Coverage area filters for time synchronization service + +### 6.7.1 Introduction + +This solution is proposed to solve Key Issue #2: Time synchronization service enhancements. In this Key Issue, the coverage area is taken into account for the configuration of the time synchronization service. Therefore, this solution addresses the time synchronization service scenarios already supported in 5G Release-17 based on access stratum or (g)PTP time distribution methods. + +This solution proposes to use a list of Tracking Areas (TAs) identified by Tracking Area Identities (TAI) or a list of Cells to describe a specific geographical area (a so-called Requested Coverage Area) where an AF requests to enable a time synchronization (TS) service. Furthermore, in order to enforce that the requested TS service is enabled for UEs (a specific UE or a group of UEs) only in that Requested Coverage Area, the proposed solution exploits the 5GS functionality (provided by the AMF) of tracking and reporting "UE mobility on Area of Interest" events (clause 5.3.4.4 of TS 23.501 [2]). An Area of Interest (AoI) for each AMF is represented by a list of TA(s) or by a list of Cells, wherein the Area of Interest is identical to the Requested Coverage Area or the Area of Interest is a TA or cell subset of the Requested Coverage Area. + +### 6.7.2 Functional Description + +The existing time synchronization exposure procedures (clause 4.15.9 of TS 23.502 [3]) are enhanced. + +The following principles are proposed to enable the use of coverage area for time synchronization service operation: + +- An AF may optionally include a Requested Coverage Area within the timing synchronization service request using a spatial validity condition. +- As a spatial validity condition, the AF may use a geographical area (e.g. a civic address or shapes) or a TA/Cell list (if it is an AF within the operator's domain, it will have TA(s) or Cell(s) configured): + - If the AF uses a geographical area as a spatial validity condition, the NEF transforms this information into 3GPP identifiers (e.g. TAI(s) or Cell(s)) based on pre-configuration. Later, the TSCTSF discovers the AMF(s) serving the TAs/Cells comprising Area(s) of Interest. The TSCTSF or AMF subscriptions use Area of Interest that may be the same as the Requested Coverage Area or may be a subset of TAs/Cells from the list of TAs/Cells describing the Requested Coverage Area. + - If the AF is within the operator's domain, it uses a list of TAs or a list of Cells directly (based on pre-configuration) to formulate the spatial validity condition for the Requested Coverage Area. +- TSCTSF uses Location or UE presence in Area of Interest services at the AMF Event Exposure service (Namf\_EventExposure operations) to identify the UE(s) to which the AF request with a Requested Coverage Area applies. The TSCTSF subscribes to this information at the AMF(s), stores it, and determines the UE(s) presence in the Requested Coverage Area using the notification(s) from one or multiple AMFs. + +- Requested Coverage Area will be used at the TSCTSF for triggering time synchronization service activation/modification/deactivation with the following differences: + - 1) the TSCTSF discovers the AMF(s) serving in the Tracking Areas (TAs) comprising the Requested Coverage Area; + - 2) the TSCTSF subscribes (using the Namf\_EventExposure\_Subscribe service operation specified in clause 5.2.2.3.2 of TS 23.502 [3]) to the UE mobility on Area of Interest event notification service from the AMF(s) to be notified the UE(s) presence in an Area of Interest for each AMF (e.g. UE location is IN or OUT an Area of Interest); + - 3) the TSCTSF determines (based on the notification from the AMF(s)) whether or not the targeted UE(s) are inside the Requested Coverage Area; and + - 4) the TSCTSF proceeds with the time synchronization service activation/deactivation only after the TSCTSF has determined which of the targeted UE(s) are in or out of the Requested Coverage Area. The subscription to reports of UE presence in the Area of Interest procedure is described in clause 5.3.4.4 of TS 23.501 [2]. +- For access stratum distribution activation/deactivation, the TSCTSF will enable/disable ReferenceTimeInformation delivery to the UE at the serving NG-RAN node reusing the procedure 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-TT and UMIC to the UPF/NW-TT, as described in clause K.2.2 of TS 23.501 [2]. +- Alternatively, the TSCTSF can trigger a deferred 5GC-MT-LR procedure to GMLC with the type of event assigned to Area, where the area information is set to the Requested Coverage Area for time synchronization services provided by TSN AF. GMLC receives the deferred 5GC-MT-LR procedure and responds with location event notification indicating the UE entering or moving out of the coverage area. + +### 6.7.3 Procedures + +#### 6.7.3.1 Procedure for AF requested (g)PTP timing synchronization with Requested Coverage Area + +An overall procedure for AF providing coverage area for (g)PTP based time synchronization service is illustrated in Figure 6.7.3.1-1. + +![Sequence diagram for (g)PTP time distribution configuration with Requested Coverage Area. Lifelines: UE/DS-TT, NG-RAN, AMF, UPF/NW-TT, NRF, TSCTSF, NEF, AF. The sequence shows the AF sending a request to the NEF, which then interacts with the TSCTSF, NRF, and AMF to configure the PTP instance and manage time distribution for UEs in a specific area. It also includes steps for UE movement and subsequent deactivation of the service.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant TSCTSF + participant NRF + participant AMF + participant NG-RAN + participant UE/DS-TT + + Note right of AF: 1: Nnef_TimeSynchronization_ConfigCreate Request (with spatial validity condition) + AF->>NEF: 1: Nnef_TimeSynchronization_ConfigCreate Request (with spatial validity condition) + Note right of NEF: 2: NEF determines TAs/Cells from the spatial validity condition + NEF->>TSCTSF: 3: Ntsctsf_TimeSynchronization_ConfigCreate Request (with TAs/Cells) + Note right of TSCTSF: 4: Nnrf_NFDiscovery_Request + TSCTSF->>NRF: 4: Nnrf_NFDiscovery_Request + Note right of NRF: 5: Namf_EventExposure_Subscribe Request (Event ID: UE's presence in the AoI) + NRF->>AMF: 5: Namf_EventExposure_Subscribe Request (Event ID: UE's presence in the AoI) + Note right of AMF: 6: NGAP: Location Reporting Control + AMF->>NG-RAN: 6: NGAP: Location Reporting Control + Note right of NG-RAN: 7: NGAP: Location Report + NG-RAN->>AMF: 7: NGAP: Location Report + Note right of AMF: 8: Namf_EventExposure_Subscribe Response + AMF->>TSCTSF: 8: Namf_EventExposure_Subscribe Response + Note right of TSCTSF: 9: TSCTSF determines whether to activate time synchronization service + TSCTSF->>NEF: 10: Ntsctsf_TimeSynchronization_ConfigCreate Response + NEF->>AF: 11: Nnef_TimeSynchronization_ConfigCreate Response + Note right of TSCTSF: 12: TSCTSF configures PTP instance as described in clause K.2.2 of TS 23.501 for the UEs matching the spatial validity condition + Note right of TSCTSF: 13: TSCTSF manages 5G access stratum time distribution for the UEs matching the spatial validity condition as described in clause 4.15.9.4 of TS 23.502 + Note right of UE/DS-TT: 14: UE moves in/out of the allowed area of interest + UE/DS-TT->>NG-RAN: 15: NGAP: Location Report + NG-RAN->>AMF: 15: NGAP: Location Report + Note right of AMF: 16: Namf_EventExposure_Notify + AMF->>TSCTSF: 16: Namf_EventExposure_Notify + Note right of TSCTSF: 17: TSCTSF (de)activates time synchronization service for the UE. (g)PTP (de)activation as described in clause K.2.2 of TS 23.501. Access stratum time distribution (de)activation as described in clause 4.15.9.4 of TS 23.502 + TSCTSF->>NEF: 18: Ntsctsf_TimeSynchronization_ConfigUpdateNotify + NEF->>AF: 19: Nnef_TimeSynchronization_ConfigUpdateNotify + +``` + +Sequence diagram for (g)PTP time distribution configuration with Requested Coverage Area. Lifelines: UE/DS-TT, NG-RAN, AMF, UPF/NW-TT, NRF, TSCTSF, NEF, AF. The sequence shows the AF sending a request to the NEF, which then interacts with the TSCTSF, NRF, and AMF to configure the PTP instance and manage time distribution for UEs in a specific area. It also includes steps for UE movement and subsequent deactivation of the service. + +Figure 6.7.3.1-1: (g)PTP time distribution configuration with Requested Coverage Area + +1. The AF creates a time synchronization service configuration for a PTP instance by invoking Nnef\_TimeSynchronization\_ConfigCreate service operation. The request includes the parameters as described in table 4.15.9.3.1 in TS 23.502 [3] and optionally a spatial validity condition (i.e. Requested Coverage Area) in the format of a geographical area (e.g. a civic address or shapes) a list of TA(s), or a list of Cells. +2. The NEF authorizes the request. If the AF uses a geographical area as a spatial validity condition, the NEF transforms this information into a list of TA(s) or a list of Cells based on pre-configuration. The list of TA(s) or the list of Cells describes the Requested Coverage Area. + +The AF within the operator's domain shall use a list of TA(s) or a list of Cells directly to formulate a spatial validity condition describing the Requested Coverage Area. + +3. After successful authorization, the NEF invokes the Ntsctsf\_TimeSynchronization\_ConfigCreate service operation with the corresponding TSCTSF, with the parameters as received from the AF. + +The AF that is part of operator's trust domain may invoke the services directly with TSCTSF. + +4. TSCTSF determines whether the TSCTSF has subscribed for the UE presence for an area that is indicated in the TAs or Cell IDs in the spatial validity condition. If not, the TSCTSF discovers the AMF(s), serving in the TAs or serving the Cells that either comprise the spatial validity condition, using the NRF discovery service (Nnrf\_NFDiscovery\_Request) with the list of TAs or the list of Cells, respectively. +5. The spatial validity condition for the UE(s) is resolved at the TSCTSF. In order to do that, the TSCTSF subscribes to the AMF(s) to receive notifications about the UE presence in an area of interest (or UE location) using Namf\_EventExposure operation. The subscribed area of interest may be the same as the Requested Coverage Area specified by the spatial validity condition or may be a subset of the Requested Coverage Area (e.g. a list of TAs, or cell list) based on the latest known UE location. + +- 6-7. The AMF(s) track the UE's location to determine the UE's presence in an Area of Interest as described in clause 4.15.4.2 of TS 23.502 [3]. Further, the AMF(s) notify the TSCTSF about the UE(s) presence (IN, OUT, or UNKNOWN) in the Area of Interest(s). +8. The AMF(s) accept TSCTSF's subscription and provide the first corresponding event report (if available). +9. According to the UE location of each UE that is targeted by the request and spatial validity condition in step 1, the TSCTSF determines whether to active time synchronization service for this UE: + - If the UE location is in an Area of Interest (and thus in the Requested Coverage Area), the TSCTSF determines to active time synchronization service and creates a PTP port in a DS-TT and assigns it into the PTP instance. + - If the UE location is out of Requested Coverage Area, the TSCTSF creates a PTP port in a DS-TT and assigns it into the PTP instance but temporarily removes the UE/DS-TT from the PTP instance and indicates the PTP port state as Inactive for the related DS-TT PTP port. +10. The TSCTSF responds with the Ntsctsf\_TimeSynchronization\_ConfigCreate response. +11. The NEF responds with the Nnef\_TimeSynchronization\_ConfigCreate response. +12. The TSCTSF uses the procedures described in clause K.2.2 of TS 23.501 [2] to configure and initialize the PTP instance in the DS-TT(s) and NW-TT. +13. The TSCTSF uses the procedure in clause 4.15.9.4 of TS 23.502 [3] to manage the 5G access stratum time distribution for the UEs that are part of the impacted PTP instance. +14. UE moves in/out of the determined area of interest (i.e. Requested Coverage Area). +15. NG-RAN determines the UE presence in the area of interest has changed and notifies the AMF. +16. The AMF detects the subscription change related event occurs and it sends the event report by means of Namf\_EventExposure\_Notify message to the TSCTSF. +17. If the TSCTSF receives the UE location change notification for AoI. The TSCTSF may update to activate or deactivate the time synchronization service for the given UE. + - If the UE moves out of the Requested Coverage Area, the TSCTSF temporarily removes the UE/DS-TT from the PTP instance and indicates the PTP port state as Inactive for the related DS-TT PTP port. + - If the UE moves into an Area of Interest, and according to Temporal Validity Condition (if this parameter is available, and current time is within validity time period), the TSCTSF determines to activate time synchronization service; the TSCTSF adds the DS-TT PTP port to the PTP instance again and indicates the PTP port state as Active for the related DS-TT PTP port. + - The TSCTSF keeps the requested TS service unchanged (i.e. active/inactive) when the UE presence in the Requested Coverage Area becomes UNKNOWN until the TSCTSF determines that the UE is inside/outside the Requested Coverage Area. +18. The TSCTSF updates the state of the time synchronization configuration and may notify the NEF (or AF) with the Ntsctsf\_TimeSynchronization\_ConfigUpdateNotify service operation. The notification indicates the identities of the UEs currently within the area of spatial validity. +19. The NEF notifies the AF with the Nnef\_TimeSynchronization\_ConfigUpdateNotify service operation. + +##### 6.7.3.1a Procedure for AF requested (g)PTP timing synchronization with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR + +An overall procedure for AF providing coverage area for (g)PTP based time synchronization service is illustrated in Figure 6.7.3.1a-1. + +![Sequence diagram for PTP time distribution configuration with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR. The diagram shows interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, TSCTSF, NEF, and AF. The process involves a request from AF to NEF, a config create request from NEF to TSCTSF, a location request from TSCTSF to H-GMLC, a deferred 5GC-MT-LR procedure, an event notify from H-GMLC to TSCTSF, a determination by TSCTSF, and a final procedure call.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant TSCTSF + participant H-GMLC + Note right of AF: 1. Nnef_TimeSynchronization_ConfigCreate Request (with spatial validity condition) + AF->>NEF: Nnef_TimeSynchronization_ConfigCreate Request (with spatial validity condition) + Note right of NEF: 2. NEF determines Tas/Cells from the spatial validity condition + Note right of NEF: 3. Ntsctsf_TimeSynchronization_ConfigCreate Request + NEF->>TSCTSF: Ntsctsf_TimeSynchronization_ConfigCreate Request + Note right of TSCTSF: 4. Ngmlc_Location_ProvideLocation Request + TSCTSF->>H-GMLC: Ngmlc_Location_ProvideLocation Request + Note right of H-GMLC: 5. Deferred 5GC-MT-LR procedure as defined from step 2 to 20 in Figure 6.7.3.1-1 of TS 23.273 v17.5.0 with the type of event assigned to Area + Note right of H-GMLC: 6. Ngmlc_Location_EventNotify + H-GMLC->>TSCTSF: Ngmlc_Location_EventNotify + Note right of TSCTSF: 7. TSCTSF determines whether to activate time synchronization service + Note right of TSCTSF: 8. the procedure as defined from step 10 to 19 in Figure 6.7.3.1-1 + +``` + +Sequence diagram for PTP time distribution configuration with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR. The diagram shows interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, TSCTSF, NEF, and AF. The process involves a request from AF to NEF, a config create request from NEF to TSCTSF, a location request from TSCTSF to H-GMLC, a deferred 5GC-MT-LR procedure, an event notify from H-GMLC to TSCTSF, a determination by TSCTSF, and a final procedure call. + +**Figure 6.7.3.1a-1: (g)PTP time distribution configuration with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR** + +1. The AF creates a time synchronization service configuration for a PTP instance by invoking Nnef\_TimeSynchronization\_ConfigCreate service operation. The request includes the parameters as described in table 4.15.9.3.1 in TS 23.502 [3] and optionally a spatial validity condition (i.e. Requested Coverage Area) in the format of a geographical area (e.g. a civic address or shapes) a list of TA(s), or a list of Cells. +2. The NEF authorizes the request. If the AF uses a geographical area as a spatial validity condition. +3. After successful authorization, the NEF invokes the Ntsctsf\_TimeSynchronization\_ConfigCreate service operation with the corresponding TSCTSF, with the parameters as received from the AF. + +The AF that is part of operator's trust domain may invoke the services directly with TSCTSF. + +4. TSCTSF triggers a deferred 5GC-MT-LR procedure to GMLC with the type of event assigned to Area, where the area information is set to the Requested Coverage Area for time synchronization services provided by TSN AF. +5. GMLC performs deferred 5GC-MT-LR procedure as defined from step 2 to 20 in Figure 6.7.3.1-1 of TS 23.273 [16] v17.5.0 with the type of event assigned to Area. +6. The GMLC notifies the TSCTSF about the UE(s) presence (IN, OUT, or UNKNOWN) in the Area of Interest(s). +7. TSCTSF determines whether to activate time synchronization service. According to the UE location of each UE that is targeted by the request and spatial validity condition in step 1, the TSCTSF determines whether to active time synchronization service for this UE: + - If the UE location is in an Area of Interest (and thus in the Requested Coverage Area), the TSCTSF determines to active time synchronization service and creates a PTP port in a DS-TT and assigns it into the PTP instance. + - If the UE location is out of Requested Coverage Area, the TSCTSF creates a PTP port in a DS-TT and assigns it into the PTP instance but temporarily removes the UE/DS-TT from the PTP instance and indicates the PTP port state as Inactive for the related DS-TT PTP port. + +8 The following procedure is described from step 10 to 19 in Figure 6.7.3.1-1. + +#### 6.7.3.2 Procedure for AF requested 5G access stratum timing synchronization with Requested Coverage Area + +An overall procedure for AF requesting a specific coverage area for 5G access stratum based time synchronization service (see TS 23.502 [3]) is illustrated in Figure 6.7.3.2-1. + +![Sequence diagram for Figure 6.7.3.2-1: 5G access stratum time distribution configuration with Requested Coverage Area. The diagram shows interactions between UE, NG-RAN, AMF, NRF, TSCTSF, NEF, and AF. The process starts with the AF sending a Nnef_ASTI_Create Request to the NEF. The NEF determines TAs/Cells and sends an Ntsctsf_ASTI_Create Request to the TSCTSF. The TSCTSF sends an Nnrf_NFDiscovery_Request to the NRF. The NRF sends an Namf_EventExposure_Subscribe Request to the AMF. The AMF sends an NGAP: Location Reporting Control to the NG-RAN. The NG-RAN sends an NGAP: Location Report to the AMF. The AMF sends an Namf_EventExposure_Subscribe Response to the TSCTSF. The TSCTSF determines whether to activate the time synchronization service and sends an Ntsctsf_ASTI_Create Response to the NEF. The NEF sends an Nnef_ASTI_Create Response to the AF. The TSCTSF manages the 5G access stratum time distribution for UEs matching the spatial validity condition. If a UE moves in/out of the allowed area of interest, the NG-RAN sends an NGAP: Location Report to the AMF, which sends an Namf_EventExposure_Notify to the TSCTSF. The TSCTSF deactivates the access stratum time distribution and sends an Ntsctsf_ASTI_UpdateNotify to the NEF, which sends an Nnef_ASTI_UpdateNotify to the AF.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant TSCTSF + participant NRF + participant AMF + participant NG-RAN + participant UE + + Note right of AF: 1: Nnef_ASTI_Create Request (with spatial validity condition) + AF->>NEF: 1: Nnef_ASTI_Create Request (with spatial validity condition) + Note right of NEF: 2: NEF determines TAs/Cells from the spatial validity condition + NEF->>TSCTSF: 3: Ntsctsf_ASTI_Create Request (with TAs/Cells) + TSCTSF->>NRF: 4: Nnrf_NFDiscovery_Request + NRF->>AMF: 5: Namf_EventExposure_Subscribe Request (Event ID: UE's presence in the AoI) + AMF->>NG-RAN: 6: NGAP: Location Reporting Control + NG-RAN->>AMF: 7: NGAP: Location Report + AMF->>TSCTSF: 8: Namf_EventExposure_Subscribe Response + Note right of TSCTSF: 9: TSCTSF determines whether to activate time synchronization service + TSCTSF->>NEF: 10: Ntsctsf_ASTI_Create Response + NEF->>AF: 11: Nnef_ASTI_Create Response + Note right of TSCTSF: 12: TSCTSF manages 5G access stratum time distribution for the UEs matching the spatial validity condition as described in clause 4.15.9.4 of TS 23.502 + Note right of UE: 13: UE moves in/out of the allowed area of interest + UE->>NG-RAN: 14: NGAP: Location Report + NG-RAN->>AMF: 15: Namf_EventExposure_Notify + Note right of TSCTSF: 16: TSCTSF deactivates access stratum time distribution as described in clause 4.15.9.4 of TS 23.502 + TSCTSF->>NEF: 17: Ntsctsf_ASTI_UpdateNotify + NEF->>AF: 18: Nnef_ASTI_UpdateNotify + +``` + +Sequence diagram for Figure 6.7.3.2-1: 5G access stratum time distribution configuration with Requested Coverage Area. The diagram shows interactions between UE, NG-RAN, AMF, NRF, TSCTSF, NEF, and AF. The process starts with the AF sending a Nnef\_ASTI\_Create Request to the NEF. The NEF determines TAs/Cells and sends an Ntsctsf\_ASTI\_Create Request to the TSCTSF. The TSCTSF sends an Nnrf\_NFDiscovery\_Request to the NRF. The NRF sends an Namf\_EventExposure\_Subscribe Request to the AMF. The AMF sends an NGAP: Location Reporting Control to the NG-RAN. The NG-RAN sends an NGAP: Location Report to the AMF. The AMF sends an Namf\_EventExposure\_Subscribe Response to the TSCTSF. The TSCTSF determines whether to activate the time synchronization service and sends an Ntsctsf\_ASTI\_Create Response to the NEF. The NEF sends an Nnef\_ASTI\_Create Response to the AF. The TSCTSF manages the 5G access stratum time distribution for UEs matching the spatial validity condition. If a UE moves in/out of the allowed area of interest, the NG-RAN sends an NGAP: Location Report to the AMF, which sends an Namf\_EventExposure\_Notify to the TSCTSF. The TSCTSF deactivates the access stratum time distribution and sends an Ntsctsf\_ASTI\_UpdateNotify to the NEF, which sends an Nnef\_ASTI\_UpdateNotify to the AF. + +Figure 6.7.3.2-1: 5G access stratum time distribution configuration with Requested Coverage Area + +1. The AF request to influence the 5G access stratum time distribution providing access stratum time distribution parameters to the NEF (together with the AF identifier and potentially further inputs as specified in table 4.15.9.4-1 of TS 23.502 [3]) and optionally a spatial validity condition (i.e. Requested Coverage Area) in the format of a geographical area (e.g. a civic address or shapes), a list of TA(s), or a list of Cells. +2. The NEF authorizes the request. If the AF uses a geographical area as a spatial validity condition, the NEF transforms this information into a list of TA(s) or a list of Cells based on pre-configuration. The list of TA(s) or the list of Cells describes the Requested Coverage Area. + +The AF within the operator's domain shall use a list of TA(s) or a list of Cells directly to formulate a spatial validity condition describing the Requested Coverage Area. + +3. After successful authorization, the NEF invokes the Ntsctsf\_ASTI\_Create service operation with the corresponding TSCTSF. +4. TSCTSF determines whether the TSCTSF has subscribed for the UE presence for an area that is indicated in the TAs or Cell IDs in the spatial validity condition. If not, the TSCTSF discovers the AMF(s), serving in the TAs or serving the Cell(s) that either comprise the spatial validity condition, using the NRF discovery service (Nnrf\_NFDiscovery\_Request) with the list of TAs or the list of Cells, respectively. + +5. The spatial validity condition is resolved at the TSCTSF. In order to do that, the TSCTSF subscribes to the AMF to receive notifications about change of UE location in an area of interest using Namf\_EventExposure operation. The subscribed area of interest may be the same as the Requested Coverage Area specified by the spatial validity condition or may be a subset of the Requested Coverage Area (e.g. a list of TAs, a list of Cells) based on the latest known UE location. +- 6-7. The AMF(s) track the UE's location to determine the UE's presence in an Area of Interest as described in clause 4.15.4.2 of TS 23.502 [3]. Further, the AMF(s) notify the TSCTSF about the UE(s) presence (IN, OUT, or UNKNOWN) in the Area of Interest(s). +8. The AMF(s) accept TSCTSF's subscription and provide the first corresponding event report (if available). +According to the UE location and spatial validity condition, the TSCTSF determines whether to activate time synchronization service: + - If the UE location is in an Area of Interest (and thus in the Requested Coverage Area), the TSCTSF determines to activate time synchronization service. + - If the UE location is out of Requested Coverage Area, the TSCTSF stores the UE identity and determines not to activate ASTI time synchronization service for the UE. +10. The TSCTSF responds the AF with the Ntsctsf\_ASTI\_Create service operation response. +11. The NEF informs the AF about the result of the Nnef\_ASTI\_Create service operation performed in step 1. +12. The TSCTSF uses the procedures described in clause 4.15.9.4 of TS 23.502 [3] to configure ReferenceTimeInformation delivery to the UE(s) at the serving NG-RAN nodes. +13. UE moves in/out of the configured Area(s) of Interest. +14. NG-RAN determines the change of the UE presence in the area of interest has changed and notifies the AMF. +15. The AMF detects the subscription change related event occurs and it sends the event report by means of Namf\_EventExposure\_Notify message to the TSCTSF. +16. If the TSCTSF receives the UE location change notification for AoI. The TSCTSF may update to activate or deactivate the time synchronization service. + - If the UE moves out of the Requested Coverage Area, the TSCTSF determines to temporarily deactivate ASTI time synchronization service as described in clause 4.15.9.4 of TS 23.502 [3]. + - If the UE moves into an Area of Interest, and according to Temporal Validity Condition (if this parameter is available, and current time is within validity time period), the TSCTSF determines to activate ASTI time synchronization service as described in clause 4.15.9.4 of TS 23.502 [3]. + - The TSCTSF keeps the requested TS service unchanged (i.e. active/inactive) when the UE presence in the Requested Coverage Area becomes UNKNOWN until the TSCTSF determines that the UE is inside/outside the Requested Coverage Area. +17. The TSCTSF updates the state of the time synchronization configuration and may notify the NEF (or AF) with the Ntsctsf\_ASTI\_UpdateNotify service operation for the UE identities that are inside or outside of the area in the spatial validity condition. +18. The NEF notifies the AF with the Nnef\_ASTI\_UpdateNotify service operation. + +##### 6.7.3.2a Procedure for AF requested 5G access stratum timing synchronization with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR + +An overall procedure for AF requesting a specific coverage area for 5G access stratum based time synchronization service (see TS 23.502 [3]) is illustrated in Figure 6.7.3.2-1. + +![Sequence diagram for 5G access stratum time distribution configuration with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR. The diagram shows interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, TSCTSF, NEF, and AF. The process involves a request from AF to NEF, determination of cells by NEF, a request from NEF to TSCTSF, a location request from TSCTSF to H-GMLC, a deferred 5GC-MT-LR procedure, a location event notification from H-GMLC to TSCTSF, a determination by TSCTSF, and finally a procedure defined in Figure 6.7.3.1-1.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant TSCTSF + participant H-GMLC + participant UDM + participant V-GMLC + participant LMF + participant AMF + participant NG-RAN + participant UE + + Note right of AF: Nnef_TimeSynchronization_ConfigCreate Request (with spatial validity condition) + AF->>NEF: Nnef_TimeSynchronization_ConfigCreate Request (with spatial validity condition) + Note right of NEF: 2. NEF determines Tas/Cells from the spatial validity condition + NEF->>TSCTSF: 3. Ntsctsf_TimeSynchronization_ConfigCreate Request + TSCTSF->>H-GMLC: 4. Ngmlc_Location_ProvideLocation Request + Note left of H-GMLC: 5. Deferred 5GC-MT-LR procedure as defined from step 2 to 20 in Figure 6.7.3.1-1 of TS 23.273 v17.5.0 with the type of event assigned to Area + H-GMLC->>TSCTSF: 6. Ngmlc_Location_EventNotify + Note right of TSCTSF: 7. TSCTSF determines whether to activate time synchronization service + Note left of UE: 8. the procedure as defined from step 10 to 18 in Figure 6.7.3.1-1 + +``` + +Sequence diagram for 5G access stratum time distribution configuration with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR. The diagram shows interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, TSCTSF, NEF, and AF. The process involves a request from AF to NEF, determination of cells by NEF, a request from NEF to TSCTSF, a location request from TSCTSF to H-GMLC, a deferred 5GC-MT-LR procedure, a location event notification from H-GMLC to TSCTSF, a determination by TSCTSF, and finally a procedure defined in Figure 6.7.3.1-1. + +**Figure 6.7.3.2a-1: 5G access stratum time distribution configuration with Requested Coverage Area where UE's presence is obtained via TSCTSF triggered deferred 5GC-MT-LR** + +1. The AF request to influence the 5G access stratum time distribution providing access stratum time distribution parameters to the NEF (together with the AF identifier and potentially further inputs as specified in table 4.15.9.4-1 in TS 23.502 [3]) and optionally a spatial validity condition (i.e. Requested Coverage Area) in the format of a geographical area (e.g. a civic address or shapes), a list of TA(s), or a list of Cells. +2. The NEF authorizes the request. If the AF uses a geographical area as a spatial validity condition. +3. After successful authorization, the NEF invokes the Ntsctsf\_TimeSynchronization\_ConfigCreate service operation with the corresponding TSCTSF, with the parameters as received from the AF. +The AF that is part of operator's trust domain may invoke the services directly with TSCTSF. +4. TSCTSF triggers a deferred 5GC-MT-LR procedure to GMLC with the type of event assigned to Area, where the area information is set to the Requested Coverage Area for time synchronization services provided by TSN AF. +5. GMLC performs deferred 5GC-MT-LR procedure as defined from step 2 to 20 in Figure 6.7.3.1-1 of TS 23.273 [16] v17.5.0 with the type of event assigned to Area. +6. The GMLC notifies the TSCTSF about the UE(s) presence (IN, OUT, or UNKNOWN) in the Area of Interest(s). +7. TSCTSF determines whether to activate time synchronization service. According to the UE location of each UE that is targeted by the request and spatial validity condition in step 1, the TSCTSF determines whether to active time synchronization service for this UE: + - If the UE location is in an Area of Interest (and thus in the Requested Coverage Area), the TSCTSF determines to active time synchronization service and creates a PTP port in a DS-TT and assigns it into the PTP instance. + - If the UE location is out of Requested Coverage Area, the TSCTSF creates a PTP port in a DS-TT and assigns it into the PTP instance but temporarily removes the UE/DS-TT from the PTP instance and indicates the PTP port state as Inactive for the related DS-TT PTP port. + +8 The following procedure is described from step 10 to 18 in Figure 6.7.3.2-1. + +### 6.7.4 Impacts on services, entities and interfaces + +TSCTSF: + +- Subscribe for receiving UE's presence in Area of Interest from AMF or from GLMC as a deferred 5GC-MT-LR with the type of event assigned to Area. +- Determination of area of interest based on list of TAs or Cells. +- Support for time synchronization service configuration conditioned to the AF-Requested Coverage Area using a spatial validity condition. +- Discovers the related AMF(s) using the NRF's service operation Nnrf\_NFDiscovery\_Request. +- Notifies the AF/NEF via a new Ntsctsf\_ASTI\_UpdateNotify service operation for the UE identities that are inside or outside of the area in the spatial validity condition. + +AMF: + +- Tracks a UE's location to determine the UE's presence in an Area of Interest using the existing event reporting type, i.e. UE mobility on Area of Interest. +- Notifies the subscribed TSCTSF about the change of UE's status (IN, OUT, or UNKNOWN) in the Area of Interest using the (existing) Namf\_EventExposure\_Notify service operation. + +AF: + +- Includes the Spatial Validity Condition in AF request for time synchronization service configuration. + +## 6.8 Solution #8: AF Request of PER for QoS and Alt-QoS + +### 6.8.1 Introduction + +This solution is proposed to solve Key Issue #4: Enable an AF to explicitly provide the required PER to the NEF/PCF for QoS and Alt-QoS. + +In Release 17, the "Setting up an AF session with required QoS" procedure (clause 4.15.6.6 of TS 23.502 [3]) and the "AF Session with required QoS update" procedure (clause 4.15.6.6a of TS 23.502 [3]) were revised so the AF can provide individual parameters for QoS and Alt-QoS. Inclusion of PER as an individual parameter requested by the AF was postponed to Release 18. PER is a QoS Characteristic as defined in clause 5.7.3.1 of TS 23.501 [2], similar to PDB which was included as an individual parameter. PER is also currently part of the Alternative QoS Profile, along with PDB and GFBR. PDB and GFBR as individual parameters for Alt-QoS were addressed in Release 17. + +This solution adds Requested PER to the AF request for QoS and Alternative QoS. + +### 6.8.2 Functional Description + +When there is a single PDU session anchor for the UE, an AF request for QoS specifying a Requested PER value can be sent to the PCF where it is mapped to a PCC rule with a 5QI that reflects the Requested PER. Similarly, a Requested PER value can be added to each Alternative-QoS Related parameter set (currently comprising Requested Delay and Requested GBR) in the Alternative QoS Requirements. Requested PER in the Alternative QoS requirements is mapped to the corresponding parameters in the Alternative QoS Profile (as defined in clause 5.7.1.2a of TS 23.501 [2]), in the same manner as was done for PDB and GFBR in Release 17. PCF selects the appropriate 5QI considering the requested PER and Requested 5GS Delay as in TS 23.503 [4]. + +### 6.8.3 Procedures + +Following are the steps needed for the AF requested PER to be considered either using single or redundant user plane paths: + +1. The AF provides Requested PER for QoS and Alternative QoS. If it is a trusted AF, it may provide it directly to the TSCTSF. If not, it provides it via the NEF which eventually forwards it to the TSCTSF. +2. The TSCTSF forwards the parameters to the PCF. +3. The PCF selects the appropriate 5QI considering the requested PER and the individual QoS Parameters as specified in clause 6.1.3.22 of TS 23.503 [4]. +4. The PCF determines a PCC rule using the Requested PERs received from the AF/NEF. +5. The response to the AF (Nnef\_AFsessionWithQoS\_Create/Update response) indicates whether the PER request was achieved. + +### 6.8.4 Impacts on services, entities and interfaces + +SMF: + +- Map Requested PER to QoS Profile for QoS and Alternative QoS. + +PCF: + +- Map Requested PER to PCC Rule for QoS and Alternative QoS. + +TSCTSF: + +- Support receiving Requested PER from NEF and sending to PCF. + +NEF: + +- Include Requested PER in Nnef\_AFSessionWithQoS service and send Requested PER to TSCTSF. + +AF: + +- Request PER for QoS and Alternative QoS. + +## 6.9 Solution #9: Interworking with TSN network deployed in the transport network + +### 6.9.1 Introduction + +This solution enables enhancement to support TSN transport network (TN) for N3 tunnels. + +NOTE: The same solution can be used also for N9 tunnels, if necessary. + +This solution addresses the following areas: + +- a) The architecture enhancement to support the interworking between 5GS and TSN networks deployed in the transport network. +- b) The information from 5GS to interact with TSN network. + +This solution makes the following assumptions: + +- The underlay transport network for N3 tunnels support TSN features and deploys a CNC. +- 5GC implements the UNI as defined in IEEE P802.1Qdj [10] towards the CNC in Transport Network. The related parameters are defined in IEEE Std 802.1Qcc [6]. +- The solution can be used with both Ethernet and IP type PDU Sessions. +- The solution can be used when 5GS is integrated with external IEEE TSN networks as specified in TS 23.501 [2]. In this case the CNC in external TSN network controls the 5GS as an IEEE 802.1Q bridge via TSN AF. + +- The solution can be used when integration with external IEEE TSN networks does not apply as specified in TS 23.501 [2]. In this case the AF uses the 3GPP QoS-service to indicate the QoS requirements and traffic characteristics to the TSCTSF. +- A dynamic value for the CN PDB of a Delay-critical GBR 5QI is determined by the SMF as described in clause 5.3.7.4 of TS 23.501 [2]. +- NG-RAN may include AN-TL function and UPF may include CN-TL function, to support acting as a TSN Talker/Listener. SMF/CUC communicates with the AN-TL via Transparent Container that conveys the IEEE Std 802.1Qcc [6] data sets in N2 interface. SMF/CUC communicates with the CN-TL via Transparent Container that conveys the IEEE Std 802.1Qcc [6] data sets in N4 interface. +- AN-TL and CN-TL enable the following functions: + - hold and buffer functionality in a case when the TSCAI contains a BAT in UL and/or DL direction. In this case the TimeAwareOffset is sent to the AN-TL and/or CN-TL in a Transparent Container, and the Talker in RAN/UPF must buffer the data burst until the time indicated in the TimeAwareOffset is reached. + - for support of stream transformation, in this case the InterfaceConfiguration is sent in a Transparent Container to AN-TL and/or CN-TL, and the Talker in RAN/UPF must use the indicated MAC address, VLAN ID or IP-tuples for the data stream. + - for SMF/CUC to retrieve the InterfaceCapabilities and/or EndStationInterfaces from the AN-TL or CN-TL via Transparent Container. Otherwise, this information must be preconfigured or determined by SMF/CUC. +- It is assumed that RAN, 5GC and Transport Network are time synchronized with each other in 5G internal system clock in this case. + +### 6.9.2 Functional Description + +5GC will act as CUC to interact with the TN CNC. RAN and UPF may act as Talker or Listener by implementing Access Network TSN Talker/Listener (AN-TL) and Core Network N3 interface TSN Talker/Listener (CN-TL) as network termination point for the N3 interface. AN-TL and CN-TL support the functionality of Talker and Listener (End Station). + +The architecture is as Figure 6.9.2-1: + +![Figure 6.9.2-1: Architecture on interworking with TSN transport network. The diagram shows a 5G system architecture. At the top, a '5GS Bridge / 5GS' block contains a '5GS Control Plane' and a 'CUC' (Core Network Control Plane). The 'CUC' is connected to a 'CNC / AF' (Application Function) on the right. Below the '5GS Bridge / 5GS' is a 'RAN' (Radio Access Network) block. The 'RAN' is connected to the '5GS Bridge / 5GS' via N1 and N2 interfaces. The 'RAN' contains an 'End Station (AN-TL)' which is connected to a 'UE (DS-TT)' via a Uu interface. The 'End Station (AN-TL)' is also connected to a 'TSN Bridges' cloud via an N3 interface. The 'TSN Bridges' cloud is connected to another 'End Station (CN-TL)' via an N3 interface. The 'End Station (CN-TL)' is connected to a 'UPF (NW-TT)' (User Plane Function) block. The 'UPF (NW-TT)' is connected to the '5GS Bridge / 5GS' via an N4 interface. A 'UNI' (User Network Interface) is shown between the 'CUC' and a 'TN CNC' (Transport Network Control Plane) block. The 'TN CNC' is connected to the 'TSN Bridges' cloud. The entire 5G system (RAN, UPF, 5GS Bridge/5GS) is enclosed in a dashed box, and the TSN transport network (TSN Bridges, End Stations, TN CNC) is enclosed in a yellow shaded area.](24a89bcaba787f2bc1721356480a4a01_img.jpg) + +Figure 6.9.2-1: Architecture on interworking with TSN transport network. The diagram shows a 5G system architecture. At the top, a '5GS Bridge / 5GS' block contains a '5GS Control Plane' and a 'CUC' (Core Network Control Plane). The 'CUC' is connected to a 'CNC / AF' (Application Function) on the right. Below the '5GS Bridge / 5GS' is a 'RAN' (Radio Access Network) block. The 'RAN' is connected to the '5GS Bridge / 5GS' via N1 and N2 interfaces. The 'RAN' contains an 'End Station (AN-TL)' which is connected to a 'UE (DS-TT)' via a Uu interface. The 'End Station (AN-TL)' is also connected to a 'TSN Bridges' cloud via an N3 interface. The 'TSN Bridges' cloud is connected to another 'End Station (CN-TL)' via an N3 interface. The 'End Station (CN-TL)' is connected to a 'UPF (NW-TT)' (User Plane Function) block. The 'UPF (NW-TT)' is connected to the '5GS Bridge / 5GS' via an N4 interface. A 'UNI' (User Network Interface) is shown between the 'CUC' and a 'TN CNC' (Transport Network Control Plane) block. The 'TN CNC' is connected to the 'TSN Bridges' cloud. The entire 5G system (RAN, UPF, 5GS Bridge/5GS) is enclosed in a dashed box, and the TSN transport network (TSN Bridges, End Stations, TN CNC) is enclosed in a yellow shaded area. + +**Figure 6.9.2-1: Architecture on interworking with TSN transport network** + +NOTE 1: The TN CNC in transport network (TN) is independent from the CNC in the DN. + +NOTE 2: DS-TT and NW-TT are required when 5GS is integrated with external IEEE TSN networks. + +It is proposed the SMF will act as the CUC or the CUC functionality is collocated with SMF. SMF/CUC provides merged stream requirements on QoS Flow basis (i.e. translated Talker group and Listener group information) as + +specified in clause 45.1.7 of IEEE P802.1Qdj [10] via the User/Network-Interface (UNI) to the TN CNC. TN CNC uses the merged stream requirements as input to select respective path(s) and calculate schedules in TN. Based on the results, the TN CNC provides merged end station communication-configuration back to the SMF/CUC. The SMF may further adjust the transmit time of the stream in UPF and RAN by including TimeAwareOffset in a Transparent Container in a QoS Flow modification request. + +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 that is determined on QoS Flow basis. The NG-RAN provides the dynamic value of 5G-AN PDB to the SMF in a response to the QoS Flow request. + +The details of providing End Station related information to generate the merged stream requirements for the QoS Flow by the SMF/CUC are as follows: + +For the Talker group: + +- Stream ID and Stream Rank can be generated by the SMF/CUC based on pre-configuration. +- EndStationInterfaces and Interface Capabilities (optional) are either pre-configured in the SMF/CUC or the SMF/CUC can collect them during PDU Session Establishment from AN-TL and CN-TL. The pre-configured information at the SMF/CUC leaves the InterfaceCapabilities empty. +- DataFrameSpecification (optional) is present if stream transformation is not performed in AN-TL and CN-TL. + +or if AN-TL and CN-TL functions are not supported. In this case, the TN CNC configures the edge bridge to perform the stream transformation based on the provided the DataFrameSpecification. The SMF/CUC populates the attribute with the N3 tunnel end point addresses/ports during the QoS Flow setup. + +If the TL-functions are not supported, two options can be considered for identifying the traffic on QoS Flow basis in the TN: + +- a) The SMF can instruct the UPF and NG-RAN to assign a separate CN tunnel end point address for each QFI of the N4 Session. This ensures the TN can distinguish the QoS Flows based on the N3 tunnel destination IP addresses. For example IPv6 can be used in the N3 tunnel end point addresses to provide sufficient address space. +- b) The interface between the SMF/CUC and TN CNC allows the SMF /CUC to indicate the TEID and QFI of the given QoS Flow to the TN CNC. For example, the SMF/CUC indicates a Stream Filter including the source/destination IP addresses/ports and QFI and/or TEID, and merged stream requirements that are associated with this Stream Filter. TN can distinguish the QoS Flows based on the TEID and QFI as carried in the GTP-U. This option impacts the IEEE P802.1Qdj [10]. + +NOTE 3: Option b) will be abandoned if it is not supported by IEEE P802.1Qdj [10]. + +- In TrafficSpecification elements, there are several parameters related to the TSC traffic within 5GS: +- MaxFrameSize, SMF/CUC could generate it from the Burst Size of the TSC traffic. PCF needs to transfer the Burst Size to the SMF. SMF also needs to consider the framing bits which is not used for transferring in 5GS, (e.g. CRC), the GTP-U tunnel overhead. +- MaxFramesPerInterval, SMF could set it as 1. +- Interval, SMF could generate it from the Periodicity of the traffic as indicated in the TSCAI. +- TSpecTimeAware group (optional, present only if the traffic is time-synchronized): + - EarliestTransmitOffset, the earliest offset within the Interval. + - For uplink, EarliestTransmitOffset should be set based on the BAT in UL in TSCAI, 5G-AN PDB, and Interval using the following formula: + +The sum of (UL BAT + 5G-AN PDB) (presented in TAI time and corrected for clock drifting as specified in TS 23.501 [2]) - M x Interval, where M is the largest integer for which the relation: + +$$\text{UL BAT} + \text{5G-AN PDB} > M \times \text{Interval duration.}$$ + +would be true. + +- For downlink, EarliestTransmitOffset should be set based on the BAT in DL in TSCAC, and UPF Residence Time and Interval using the following formula: + +The sum of (DL BAT + UPF Residence Time) (presented in TAI time and corrected for clock drifting as specified in TS 23.501 [2]) - CN PDB - M x Interval, where M is the largest integer for which the relation: + +$$\text{DL BAT} + \text{UPF Residence Time} > M \times \text{Interval duration.}$$ + +would be true. + +- LatestTransmitOffset, the last chance within an interval should leave enough time to transfer a packet with MaxFrameSize. Thus, the SMF could generate it from the EarliestTransmitOffset plus the interval subtracting subtracting the sum of jitter and the time to transfer a packet with MaxFrameSize. +- Jitter, SMF could generate it based on local configuration. +- UserToNetworkRequirements.MaxLatency: + - NumSeamlessTrees, SMF/CUC could set it as 0 if no redundancy is needed, otherwise it could use other values. + - MaxLatency, SMF/CUC could generate it based on CN PDB and UPF Residence Time, i.e. it should be CN PDB minus UPF Residence Time. + +The Listener group contains Stream ID, EndStationInterfaces, UserToNetworkRequirements, and Interface Capabilities. The SMF could generate the corresponding information in the same way as defined for the Talker group. + +NOTE 4: It is assumed that the merged stream requirements will contain at least the same information as defined for the User/network configuration information (i.e. Talker group and Listener group). + +The merged end station communication-configuration provided by TN CNC to the SMF/CUC includes: + +- Stream ID. +- StatusInfo. +- AccumulatedLatency. +- InterfaceConfiguration (optional): + - MAC Address (optional, present only if stream transformation is performed). + - VLAN Tag (optional, present only if stream transformation is performed). + - IPv4/IPv6 Tuples (optional, present only if stream transformation is performed). + - TimeAwareOffset (optional, present only if the traffic is time-synchronized). +- FailedInterfaces. + +The details of the above information are described in IEEE Std 802.1Qcc [6]. When the SMF/CUC receives the merged end station communication-configuration from TN CNC, the configuration may include InterfaceConfiguration, optionally with TimeAwareOffset element. + +If the InterfaceConfiguration is included from TN CNC to SMF/CUC, and if the NG-RAN and UPF include the AN-TL/CN-TL and support the Stream Transformation as described in IEEE 802.1Qdj [10], SMF can instruct the UPF and NG-RAN to assign for each TSC stream an individual TSN Transport address by providing the InterfaceConfiguration to the AN-TL/CN-TL. The Talker in AN-TL/CN-TL shall use the indicated InterfaceConfiguration, e.g. Multicast destination MAC address as assigned by the TN CNC. In this case the TN can identify the streams based on the Stream Transformation that is applied in the Talker in the AN-TL/CN-TL. This allows to use a single GTP-U tunnel as defined for non TSN Transport networks. The TSN transport address used for identification in TN can be a Destination MAC address, a Source MAC address and a VLAN ID (optional). + +If the TimeAwareOffset is included from TN CNC to SMF/CUC, the SMF/CUC should configure the AN-TL and CN-TL based on the TimeAwareOffset. The SMF/CUC adjusts the TimeAwareOffset to be relative from the start of the BAT before sending it to the AN-TL or CN-TL. The AN-TL and CN-TL should set the sending time of the traffic (e.g. AdminBaseTime and OperBaseTime in 802.1Qbv data sets) in the transport layer accordingly. + +NOTE 5: It is assumed that the merged end station communication-configuration will contain at least the same information as defined for the status. + +### 6.9.3 Procedures + +Figure 6.9.3-1 shows the procedure for this solution: + +![Sequence diagram showing the procedure for interworking with TSN transport network. The diagram involves six lifelines: UE, RAN/AN-TL, UPF/CN-TL, SMF/CUC, PCF, and TN CNC. The sequence of messages is: 1. PDU Session establishment procedure (UE to SMF/CUC); 2. PCC Rules with TSC Assistance Container (PCF to SMF/CUC); 2a. QoS Flow setup with RAN and UPF (SMF/CUC to RAN/AN-TL and UPF/CN-TL); 3. Parameter mapping (SMF/CUC to UPF/CN-TL); 4. Merged stream requirements (SMF/CUC to TN CNC); 5. Merged end station communication-configuration (TN CNC to SMF/CUC); 6a. End station configuration (SMF/CUC to RAN/AN-TL); 6b. End station configuration (SMF/CUC to UPF/CN-TL).](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +Sequence diagram showing the procedure for interworking with TSN transport network. The diagram involves six lifelines: UE, RAN/AN-TL, UPF/CN-TL, SMF/CUC, PCF, and TN CNC. The sequence of messages is: 1. PDU Session establishment procedure (UE to SMF/CUC); 2. PCC Rules with TSC Assistance Container (PCF to SMF/CUC); 2a. QoS Flow setup with RAN and UPF (SMF/CUC to RAN/AN-TL and UPF/CN-TL); 3. Parameter mapping (SMF/CUC to UPF/CN-TL); 4. Merged stream requirements (SMF/CUC to TN CNC); 5. Merged end station communication-configuration (TN CNC to SMF/CUC); 6a. End station configuration (SMF/CUC to RAN/AN-TL); 6b. End station configuration (SMF/CUC to UPF/CN-TL). + +**Figure 6.9.3-1: Procedure for interworking with TSN transport network** + +1. UE triggers the PDU Session Establishment procedure as described in clause 4.3.2 of TS 23.502 [3]. If the RAN/UPF support the TL-function, the RAN and UPF report InterfaceCapabilities to the SMF/CUC via a Transparent Container. +2. During QoS Flow setup, the SMF received PCC rules with TSC Assistance Container from the PCF. The PCF needs to send Burst Size of the TSC traffic as described in clause 6.9.2. +- 2a. SMF setups the QoS Flow with UPF and NG-RAN. +3. The SMF/CUC generates merged stream requirements as described in clause 6.9.2. +4. The SMF/CUC sends the merged stream requirements to the TN CNC. +5. The TN CNC returns the merged end station communication-configuration to the SMF/CUC. +6. The SMF/CUC configures the Talker and Listener based on the merged end station communication-configuration returned by the TN CNC. The SMF/CUC could send the TimeAwareOffset to the CN-TL and AN-TL in a Transparent Container. The CN-TL and AN-TL should adjust the sending time of the traffic (e.g. AdminBaseTime and OperBaseTime) accordingly. + +### 6.9.4 Impacts on services, entities and interfaces + +SMF: + +- Support the collocation with CUC, i.e.: + +- Provide input related to the Talker/Listener Group based on the above description. Passes the merged stream requirements to the TN CNC. Receives the merged end station communication-configuration from the TN CNC. +- Optionally transfer received merged end station communication-configuration from the TN CNC to the Talker/Listener accordingly. + +PCF: + +- sends the TSCAC including Burst Size of the TSC traffic to the SMF. + +RAN: + +- optionally support the functionality of Listener/Talker as described above. + +UPF: + +- optionally support the functionality of Talker/Listener as described above. + +## 6.10 Solution #10: 5GC acting as a CUC for CNC in TN + +### 6.10.1 Introduction + +This solution is merged into Solution #9. + +This solution enables the 5GC to act as a TSN CUC (Centralized User Configuration). + +This solution makes the following assumptions: + +- The underlay transport network for N3 and N9 tunnels support TSN features and deploys a CNC. +- 5GC implements the UNI as defined in IEEE P802.1Qdj [10] towards the CNC in Transport Network. +- The solution can be used with both Ethernet and IP type PDU Sessions. +- The solution can be used when 5GS is integrated with external IEEE TSN networks as specified in TS 23.501 [2]. In this case the CNC in external TSN network controls the 5GS as an IEEE 802.1Q bridge via TSN AF. +- The solution can be used when integration with external IEEE TSN networks does not apply as specified in TS 23.501 [2]. In this case the AF uses the 3GPP QoS-service to indicate the QoS requirements and traffic characteristics to the TSCTSF. +- A dynamic value for the CN PDB of a Delay-critical GBR 5QI is determined by the SMF as described in clause 5.3.7.4 of TS 23.501 [2]. + +### 6.10.2 Functional Description + +The solution is based on the architecture in Figure 6.10.2-1: + +![Figure 6.10.2-1: Architecture to support the control of TSN features in TN. The diagram shows a UE/DS-TT connected to a Talker/Listener, which is connected to an NG-RAN. The NG-RAN is connected to a UPF/NW-TT via an N3 tunnel and L3/L2. The UPF/NW-TT is connected to another Talker/Listener. A TN-CNC is connected to the UPF/NW-TT via a Transport Network. The TN-CNC is connected to a CNC/AF via a TSCAC. The CNC/AF is connected to a TSN AF/TSCTSF, which is connected to a PCF, which is connected to an SMF/CUC. The SMF/CUC is connected to the NG-RAN via a TSCAI. The SMF/CUC is also connected to the UPF/NW-TT via a UNI.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Figure 6.10.2-1: Architecture to support the control of TSN features in TN. The diagram shows a UE/DS-TT connected to a Talker/Listener, which is connected to an NG-RAN. The NG-RAN is connected to a UPF/NW-TT via an N3 tunnel and L3/L2. The UPF/NW-TT is connected to another Talker/Listener. A TN-CNC is connected to the UPF/NW-TT via a Transport Network. The TN-CNC is connected to a CNC/AF via a TSCAC. The CNC/AF is connected to a TSN AF/TSCTSF, which is connected to a PCF, which is connected to an SMF/CUC. The SMF/CUC is connected to the NG-RAN via a TSCAI. The SMF/CUC is also connected to the UPF/NW-TT via a UNI. + +**Figure 6.10.2-1: Architecture to support the control of TSN features in TN** + +- The solution supports deployments with and without external TSN network: + - a) When integration with IEEE TSN applies: CNC in external TSN network provides bridge configuration to the TSN AF. TSN AF uses the PSFP (IEEE 802.1Qci) information as provided by the CNC to derive the TSC Assistance Container (TSCAC). TSCAC is provided to the SMF (via PCF), and SMF determines the TSC Assistance Information (TSCAI) as specified in TS 23.501 [2]. + - b) When integration with IEEE TSN does not apply: The AF provides a Ntsctsfs\_QoSAndTSCAssistance service request to the TSCTSF (directly or via NEF). The request contains the flow description and may contain one or more of the Requested 5GS delay, Burst Size, Burst Arrival Time, Periodicity, and Time Domain as specified in clause 4.15.6.6 of TS 23.502 [3]. TSCTSF determines the TSCAC and provides it to the SMF (via PCF), and SMF determines the TSCAI. DS-TT and NW-TT are optional as in Release 17. +- TSN Transport Network (TN) deploys a CNC that communicates with a CUC residing in the 5GC. The SMF is collocated with the CUC and information is exchanged between SMF and CUC by implementation specific means (out of scope of 3GPP). Once the SMF has established a QoS Flow between UPF and NG-RAN, the SMF/CUC determines the merged stream requirements for the QoS Flow in the transport network and communicates them to the CNC in TN. +- The CUC implements the UNI as defined in IEEE P802.1Qdj [10] towards the CNC in Transport Network. +- CNC in TN configures the TN according to the merged stream requirements reflecting the required traffic characteristics of the QoS Flow. + +**Editor's note:** Stream Aggregation is FFS. + +### 6.10.3 Procedures + +Figure 6.10.3-1 describes the overall procedure how QoS Flows are established with the solution. + +![Sequence diagram illustrating the QoS Flow establishment process between NG-RAN, PCF, SMF, UPF, and TN CNC.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN + participant PCF + participant SMF + participant UPF + participant TN CNC + + Note right of PCF: 1. PCF determines the PCC Rules based on the policy authorization service from AF/NEF/TSCTSF. + Note right of SMF: 2. SMF receives the PCC Rules from PCF. SMF binds the PCC rule to a QoS Flow. + Note right of UPF: 3. SMF indicates N4 rules for the QoS Flow to the UPF. UPF assigns the CN tunnel endpoint address for the QoS Flow. + Note right of NG-RAN: 4. SMF provides the QoS profile for the QoS Flow to NG-RAN. NG-RAN assigns the AN tunnel endpoint address. + Note right of TN CNC: 5. SMF provides the traffic requirements for the QoS Flow to TN CNC via CUC + +``` + +The diagram shows a sequence of five steps for QoS Flow establishment. The participants are NG-RAN, PCF, SMF, UPF, and TN CNC. Step 1: PCF determines PCC Rules based on policy authorization from AF/NEF/TSCTSF. Step 2: SMF receives PCC Rules from PCF and binds them to a QoS Flow. Step 3: SMF indicates N4 rules for the QoS Flow to UPF, which assigns a CN tunnel endpoint address. Step 4: SMF provides the QoS profile to NG-RAN, which assigns an AN tunnel endpoint address. Step 5: SMF provides traffic requirements to TN CNC via CUC. + +Sequence diagram illustrating the QoS Flow establishment process between NG-RAN, PCF, SMF, UPF, and TN CNC. + +**Figure 6.10.3-1: Overview of the QoS Flow establishment** + +1. PCF receives the Policy Authorization service request from the AF/NEF/TSCTSF. The PCF composes the PCC Rules as specified in Release 17. PCF includes the TSCAC in the request when it invokes the SMF. +2. SMF receives the PCC Rules from the PCF. The SMF binds the PCC rule to a QoS Flow. +3. SMF indicates N4 rules for a QoS Flow to the UPF. The UPF assigns the CN tunnel endpoint address. The SMF determines a dynamic value for the CN PDB, based on the UPF and NG-RAN of the PDU Session. +4. The SMF provides the QoS profile for the QoS Flow to the NG-RAN. The SMF signals the dynamic value for the CN PDB for the QoS Flow to NG-RAN. NG-RAN assigns the AN tunnel endpoint address. + +SMF provides the TSCAI to the NG-RAN on QoS Flow basis. The TSCAI may contain Burst Arrival Time (BAT) at the UE egress for UL traffic, and BAT at the gNB ingress for DL traffic, as specified in Release 17. + +Upon receiving the TSCAI for a QoS Flow from the SMF, if the TSCAI includes a BAT in UL direction, the RAN determines the corresponding BAT offset in UL direction at the gNB egress. The NG-RAN provides the value to the SMF in a response. + +BAT offset is relative to the BAT value in UL direction NG-RAN has received from the SMF in TSCAI. BAT offset can take positive or negative values. The NG-RAN estimates the value of BAT offset at the time of QoS Flow establishment or modification. If necessary, the NG-RAN can update the BAT offset to the SMF e.g. if certain threshold is exceeded. + +If (g)PTP time synchronization is used and the TSCAC contains the Burst Arrival Time expressed in external GM time, the SMF adjusts the TSCAI to be expressed in 5GS time based on the clock drifting reports from the UPF as in Release 17. In this case the SMF may update the TSCAI of the QoS Flow to the NG-RAN. + +5. After the SMF has setup a QoS Flow between UPF and NG-RAN, the SMF deducts the received BAT offset from the current BAT in UL direction in the TSCAI for the given QoS Flow. + +The SMF provides the corresponding flow identification (AN tunnel end point address/port and CN tunnel endpoint address/port) along with the traffic requirements and characteristic for the QoS Flow (BAT at RAN egress in UL direction, BAT at UPF egress in DL direction, Periodicity, maximum latency, maximum jitter, max number of frames per interval, maximum frame size, etc.). While the collocated CUC translates this information to merged stream requirements. The CUC communicates the merged stream requirements to the CNC in the TN. The SMF sets the maximum latency to the value of the CN PDB. + +**Editor's note:** It is FFS if also the UPF residence time needs to be considered when calculating the maximum latency that is indicated in the stream requirements. + +The CUC and CNC in TN may use the data frame specification for IP to identify at UNI the TN stream on QoS Flow basis, in order to treat the data flow according to the traffic requirements assigned for the QoS Flow. The CNC in TN can then use the provided merged stream requirements to ensure that sufficient resources are reserved in the TN for the TN stream e.g. to select the path(s) and calculate schedules for the traffic that can guarantee the required maximum latency. + +NG-RAN and UPF may support the Stream Transformation as described in IEEE P802.1Qdj [10], e.g. Talker uses the Multicast MAC address as assigned by the TN-CNC and indicated to the NG-RAN and UPF from the SMF/CUC. Alternatively, if the NG-RAN and UPF do not support Stream Transformation, two options can be considered for identifying the traffic on QoS Flow basis in the TN: + +- a) The SMF can instruct the UPF and NG-RAN to assign a separate CN tunnel end point address for each QFI of the N4 Session. This ensures the TN can distinguish the QoS Flows based on the AN and CN tunnel destination IP addresses. It is assumed that IPv6 is used in the CN tunnel addresses to provide sufficient number of addresses. +- b) The interface between the CUC and CNC in the TN allows the SMF and CUC to indicate the TEID and QFI of the given QoS Flow to the CNC in the TN. For example, the CUC indicates a Stream Filter including the source/destination IP addresses/ports and QFI and/or TEID, and merged stream requirements that are associated with this Stream Filter. TN can distinguish the QoS Flows based on the TEID and QFI as carried in the GTP-U. This option impacts the IEEE P802.1Qdj [10]. + +### 6.10.4 Impacts on services, entities and interfaces + +#### SMF: + +- Allows information access with the collocated CUC to support UNI as described in IEEE P802.1Qdj [10]. +- Determines the traffic requirements for a QoS Flow and initiates that CUC translates them to merged stream requirements which are then passed to the CNC in Transport Network. + +#### NG-RAN: + +- Determines a BAT offset in UL direction at the gNB egress, based on the BAT in UL direction the NG-RAN receives from the SMF in TSCAI. The NG-RAN provides the BAT offset value to the SMF in a response to the QoS Flow establishment or modification request. If Option a) is used to identify the flows in TN, assigns a separate AN tunnel end point address for each QFI of the PDU Session. + +#### UPF: + +- If Option a) is used to identify the flows in TN, assigns a separate CN tunnel end point address for each QFI of the N4 Session. + +## 6.11 Solution #11: Interworking with TSN enabled N3 transport network for deterministic traffic delivery + +### 6.11.1 Introduction + +The solution is proposed to solve Key Issue #5: Interworking with TSN network deployed in the transport network. In the 3GPP Rel-16 and Rel-17, the 5GS has supported "periodic deterministic communication", so called TSC communication. + +The E2E delay for the service flow in the 5GS (called as PDB) includes AN-PDB between UE and NG-RAN, and CN-PDB between NG-RAN and UPF. The CN-PDB is guaranteed by N3 transport network. + +If the TSN is deployed in the N3 transport network, the 5GS can utilize the TSN capability in the N3 to provide the deterministic CN-PDB. + +### 6.11.2 Functional Description + +In the figure 6.11.2-1, it proposes an enhanced 5GS architecture to utilize the TSN capability in the N3 transport network. + +![Figure 6.11.2-1: The enhanced 5GS interworking with CNC in transport network. The diagram shows the 5GS architecture components (UE/DS-TT, NG-RAN/NG-TT, AMF, PCF, SMF, TSNCF/CUC, UPF/NW-TT/TNW-TT) connected to an N3 transport network. The N3 transport network contains TSN Bridges and a CNC (Centralized Network Controller). The UE/DS-TT is connected to the NG-RAN/NG-TT. The NG-RAN/NG-TT is connected to the AMF and the NG-TT. The AMF is connected to the PCF and the TSNCF/CUC. The PCF is connected to the SMF. The SMF is connected to the UPF/NW-TT. The UPF/NW-TT is connected to the N6/DN. The NG-TT is connected to the TSN Bridge. The TSN Bridge is connected to the CNC. The CNC is connected to the TSN Bridge. The TSN Bridge is connected to the UPF/NW-TT. The UPF/NW-TT is connected to the TNW-TT. The TNW-TT is connected to the N3 transport network.](ddfa5b18550d1a022a941e3c31843814_img.jpg) + +Figure 6.11.2-1: The enhanced 5GS interworking with CNC in transport network. The diagram shows the 5GS architecture components (UE/DS-TT, NG-RAN/NG-TT, AMF, PCF, SMF, TSNCF/CUC, UPF/NW-TT/TNW-TT) connected to an N3 transport network. The N3 transport network contains TSN Bridges and a CNC (Centralized Network Controller). The UE/DS-TT is connected to the NG-RAN/NG-TT. The NG-RAN/NG-TT is connected to the AMF and the NG-TT. The AMF is connected to the PCF and the TSNCF/CUC. The PCF is connected to the SMF. The SMF is connected to the UPF/NW-TT. The UPF/NW-TT is connected to the N6/DN. The NG-TT is connected to the TSN Bridge. The TSN Bridge is connected to the CNC. The CNC is connected to the TSN Bridge. The TSN Bridge is connected to the UPF/NW-TT. The UPF/NW-TT is connected to the TNW-TT. The TNW-TT is connected to the N3 transport network. + +**Figure 6.11.2-1: The enhanced 5GS interworking with CNC in transport network** + +The solution is based on the following principles: + +- It is assumed that RAN, 5GC and Transport Network are time synchronized with each other in 5G internal system clock in this case. +- There may be a logical functionality, NG-TT (NG-RAN TSN translator) in the NG-RAN, which act as the TSN end station in the N3 transport network. + - it may support LLDP to provide topology information to the TSN Transport Network. + - As TSN end station, it acts as Talker when it sends UL packets, and as Listener when it receives DL packets. + - it may support PMIC and UMIC to communicate with TSNCF. +- There may be a logical functionality, TNW-TT (Transport NW-TT) in the UPF, which acts as TSN end station in the N3 transport network. + - it may support LLDP to provide topology information to CNC the TSN Transport Network. + - As TSN end station, it acts as Talker when it sends to DL packets, and as Listener when it receives UL packets. + +- it may support PMIC and UMIC to communicate with TSNCF. +- When LLDP is supported, the u-plane is performing the LLDP functionality without the need for c-plane interaction with CNC of the transport network for the purpose of LLDP. This can be achieved with following measures: + - The TSN End Station (UPF, NG-RAN, or respective End Station TSN Translator) implements the Transmit Only operation mode as defined in clause 9.1 of IEEE Std 802.1AB-2016 [14]. + - 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-2016 [14]. + - The System Capabilities TLV may also be set to Station Only as defined in clause 8.5.8 of IEEE Std 802.1AB-2016 [14]. + +NOTE 1: It may reuse the PMIC/UMIC for the NW-TT. + +- There is TSN CUC Function (TSNCF) in the 5GC. It act as the CUC to communicate with CNC in the N3 transport network. + - The TSNCF may be in the TSN AF, or TSCTSF. + - During TSC communication establishment, it collect the Talker/Listener stream requirement as specified in IEEE Std 802.1Qcc [6] from NG-TT and TNW-TT. + - The TSNCF provides the Talker/Listener status to CNC and receives the status of stream configuration from CNC. + - The TSNCF provides the Talker/Listener configuration status to NG-TT and TNW-TT via PMIC/UMIC. + - The Talker/Listener stream requirement and Talker/Listener configuration status as specified in IEEE Std 802.1Qcc [6] are encoded as container in the PMIC which is transferred between TSNCF and UPF/TNW-TT. + - The Talker/Listener stream requirement and Talker/Listener configuration status as specified in IEEE Std 802.1Qcc [6] are encoded as container in N2 container which is transferred between TSNCF and NG-RAN. +- The NG-TT/TNW-TT provides the CN PDB to TSN CUC Function (TSNCF) in the 5GC. +- The NG-TT/TNW-TT provides the following Talker status to TSN CUC Function (TSNCF) in the 5GC. + - EndStationInterfaces. + - DataFrameSpecification. DataFrameSpecification is present if stream transformation IEEE Std 802.1Qcc [6] clause 46.1.4 is not performed in the End Station. This solution proposes the Talker (NG-TT/TNW-TT) always send this IE. + +There are two methods in DataFrameSpecification, which can be used by TSN to identify the TSN stream. + +Option A): For each Qos flow for the TSN, there is a distinct GTP tunnel, i.e. source IP address + source UDP port + destination IP address shall be unique. (Destination UDP port is well known, i.e. 2152). + +Option B): There is no impact to the usage of existing GTP-U. For each Qos flow for the TSN, it used the source MAC address + destination MAC address + VLAN ID identify the stream. Because the VLAN tag value is less than 4096, so the NG-TT/TNW-TT need to maintain a MAC address pool for each interface. + +- TrafficSpecification. +- InterfaceCapabilities. +- The NG-TT/TNW-TT provides the following Listener status to TSN CUC Function (TSNCF) in the 5GC. + - EndStationInterfaces. + - InterfaceCapabilities. + +- The TSN CUC Function (TSNCF) in the 5GC create the following IE for the talker and Listener. + - StreamID. + - StreamRank. + - UserToNetworkRequirements. + +NOTE 2: The value of Listener and Talker status refer to solution 9 except the DataFrameSpecification. + +### 6.11.3 Procedures + +The procedure in Figure 6.11.3-1 shows a signalling flow in which the 5GS reserve the resource in the TSN enabled N3 transport network. + +![Sequence diagram showing the procedure for reserve the resource in TSN transport network. The diagram involves nine participants: UE, NG RAN/NG-TT, AMF, SMF, UPF/TNW-TT, PCF, TSNCF/CUC, CNC, and NEF/AF. The sequence starts with a Service requirement from NEF/AF to TSNCF/CUC. TSNCF/CUC sends an AF session update to PCF. PCF sends an SM Policy Association modify to SMF. SMF sends an N4 Session Request / Response to UPF/TNW-TT. SMF sends an Nsmf_PDUSession_UpdateSMContext to AMF. AMF sends an N2 PDU Session Request to NG RAN/NG-TT. NG RAN/NG-TT sends an RRC resource setup to UE. NG RAN/NG-TT sends an N2 PDU Session Response to AMF. AMF sends an Nsmf_PDUSession_UpdateSMContext to SMF. SMF sends an N4 Session Request / Response to UPF/TNW-TT. SMF sends an SM Policy Association modify to PCF. PCF sends a Notify to TSNCF/CUC. TSNCF/CUC sends a Talker/Listener status to CNC. CNC sends an AF session update to TSNCF/CUC. TSNCF/CUC sends an SM Policy Association modify to SMF. SMF sends an N4 Session Request / Response to UPF/TNW-TT. SMF sends an Nsmf_Communication_N1N2 Message Transfer to AMF. AMF sends an N2 PDU Session Request to NG RAN/NG-TT.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +``` + +sequenceDiagram + participant NEF/AF + participant TSNCF/CUC + participant CNC + participant PCF + participant SMF + participant UPF/TNW-TT + participant AMF + participant NG RAN/NG-TT + participant UE + + NEF/AF->>TSNCF/CUC: 1. Service requirement + TSNCF/CUC->>PCF: 2. AF session update + PCF->>SMF: 3. SM Policy Association modify + SMF->>UPF/TNW-TT: 4. N4 Session Request / Response + SMF->>AMF: 5. Nsmf_Communication_N1N2 Message Transfer + AMF->>NG RAN/NG-TT: 6. N2 PDU Session Request + NG RAN/NG-TT->>UE: 7. RRC resource setup + NG RAN/NG-TT->>AMF: 8. N2 PDU Session Response + AMF->>SMF: 9. Nsmf_PDUSession_UpdateSMContext + SMF->>UPF/TNW-TT: 10. N4 Session Request / Response + SMF->>PCF: 11. SM Policy Association modify + PCF->>TSNCF/CUC: 12. Notify + TSNCF/CUC->>CNC: 13. Talker/Listener status + CNC->>TSNCF/CUC: 14. AF session update + TSNCF/CUC->>SMF: 15. SM Policy Association modify + SMF->>UPF/TNW-TT: 16. N4 Session Request / Response + SMF->>AMF: 17. Nsmf_Communication_N1N2 Message Transfer + AMF->>NG RAN/NG-TT: 18. N2 PDU Session Request + +``` + +Sequence diagram showing the procedure for reserve the resource in TSN transport network. The diagram involves nine participants: UE, NG RAN/NG-TT, AMF, SMF, UPF/TNW-TT, PCF, TSNCF/CUC, CNC, and NEF/AF. The sequence starts with a Service requirement from NEF/AF to TSNCF/CUC. TSNCF/CUC sends an AF session update to PCF. PCF sends an SM Policy Association modify to SMF. SMF sends an N4 Session Request / Response to UPF/TNW-TT. SMF sends an Nsmf\_PDUSession\_UpdateSMContext to AMF. AMF sends an N2 PDU Session Request to NG RAN/NG-TT. NG RAN/NG-TT sends an RRC resource setup to UE. NG RAN/NG-TT sends an N2 PDU Session Response to AMF. AMF sends an Nsmf\_PDUSession\_UpdateSMContext to SMF. SMF sends an N4 Session Request / Response to UPF/TNW-TT. SMF sends an SM Policy Association modify to PCF. PCF sends a Notify to TSNCF/CUC. TSNCF/CUC sends a Talker/Listener status to CNC. CNC sends an AF session update to TSNCF/CUC. TSNCF/CUC sends an SM Policy Association modify to SMF. SMF sends an N4 Session Request / Response to UPF/TNW-TT. SMF sends an Nsmf\_Communication\_N1N2 Message Transfer to AMF. AMF sends an N2 PDU Session Request to NG RAN/NG-TT. + +**Figure 6.11.3-1: Procedure for reserve the resource in TSN transport network** + +The signalling procedure is similar with the network requested PDU Session Modification specified in clause 4.3.3.2 of TS 23.502 [3]. The enhancement are: + +- The NG-RAN send the PMIC/UMIC in the N2 request, which carry the stream information needed for CUC. For the UL traffic, the stream information is for the Talker, and for the DL traffic, the stream information is for the Listener. The stream information detail see clauses 46.2.3 and 46.2.4 of IEEE Std 802.1Qcc [6]. +- The PMIC/UMIC from NG-TT is sent to SMF. +- The UPF/TNW-TT send the PMIC/UMIC in the N4 response, which carry the stream information needed for CUC. For the DL traffic, the stream information is for the Talker, and for the UL traffic, the stream information is for the Listener. The stream information detail see clauses 46.2.3 and 46.2.4 of IEEE Std 802.1Qcc [6]. +- The PMIC/UMIC from NG-TT and TNW-TT is sent to TSNCF via PCF. +- The TSNCF send the Talker/Listener status to CNC. The CNC response with stream configuration. +- The TSNCF send the stream configuration to NG-TT and TNW-TT in the PMIC/UMIC. + +### 6.11.4 Impacts on services, entities and interfaces + +- NG-RAN/NG-TT: it may support LLDP to report the topology to CNC. As the TSN end station, it is Talker when it send to UL packet, and is Listener when it receives the DL packet. It support container to communicate with TSNCF. +- UPF/TNW-TT: it may support LLDP to report the topology to CNC. As the TSN end station, it is Talker when it send to DL packet, and is Listener when it receives the UL packet. It support PMIC and UMIC to communicate with TSNCF. +- TSNCF: It collect the Talker/Listener stream requirement as specified in IEEE Std 802.1Qcc [6] from NG-TT and TNW-TT via PMIC/UMIC. It provides the Talker/Listener status to CNC and receives the status of stream configuration from CNC. It provides the Talker/Listener configuration status to NG-TT and TNW-TT via PMIC/UMIC. + +**Editor's note:** Additional impact is FFS. + +## 6.12 Solution #12: Cross layer scheduling optimization based on RAN feedback + +### 6.12.1 Introduction + +This solution enables the RAN to provide time offset feedback to AF for low latency communication, and the solution addresses the following scenarios: + +- adapting application transmission schedule in DL based on RAN feedback for low latency. +- The same solution can be used also in UL direction, if necessary +- The solution can be used together with the Solution 9 to configure the underlay network in the TN for the required traffic characteristics of the QoS Flow. + +### 6.12.2 Functional Description + +In the current specification, the AF/NEF provides the traffic characteristics information to the TSCTSF using the Ntsctsf\_QoSAndTSCAssistance service. The TSCTSF constructs a TSC Assistance Container (including flow direction, periodicity and Burst Arrival Time) for an application and provides it to the SMF via PCF. In this solution, instead of the BAT, the AF provides BAT window (as indicated by BAT-early and BAT-late) showing the acceptable earliest and latest arrival time of the traffic (as experienced by the 5GS). The TSCTSF provides the BAT windows in the TSC Assistance Container to the SMF via PCF if included in the Ntsctsf\_QoSAndTSCAssistance. + +**NOTE 1:** This solution assumes that 5GS and AF are time synchronized. + +The SMF determines the TSCAI for the QoS Flow based on the TSC Assistance Container of the PCC rule bound to the QoS Flow as described in clause 5.27.2.4 of TS 23.501 [2], i.e. the BAT-early and BAT-late in the TSCAI represent a range for the latest possible time when the first packet of the data burst arrives at the AN. + +When NG-RAN receives the TSCAI, NG-RAN determines a Semi-Persistent Scheduling scheme according to the TSCAI and the PDB. To maximize the time for transmission/re-transmission over the air interface and to minimize the scheduling time (within the PDB available for the QoS Flow), the NG-RAN may calculate the offset time between the earliest arrival time of the Burst Arrival Time and the determined scheduling time. + +**NOTE 2:** The timing of the arrival of the DL traffic can be made more accurate for the NG-RAN by using Solution 9 to configure the underlay network. + +For example, the adjusted packet for DL traffic based on the offset should arrive at a time slot before and closest to the determined scheduling time slot so that it could be transferred immediately. The NG-RAN may select the BAT offset that is relative to the BAT-early, and is less or equal to the subtract of the BAT-late and BAT-early. + +NG-RAN forwards the BAT offset in DL direction to the SMF. SMF will send it back to the AF via PCF/TSCTSF/NEF. + +AF receives the BAT offset and notifies the application to adapt the DL transmission schedule to it. + +In similar manner, NG-RAN may determine scheduling for configured grants in UL direction, and provide a BAT offset in UL direction to the SMF. The SMF sends it back to the AF via PCF/TSCTSF/NEF. + +If the AF wishes to change the accepted BAT offset, the AF can update the TSCTSF with the new BAT window by initiating a new QoS update procedure. The TSCTSF updates the TSCAC based on the AF update. + +NOTE 3: This solution could also be used for UL as BAT offset could be indicated separately for UL and DL directions. + +The SMF configures the UPF for clock drifting reports as specified in TS 23.502 [3]. In a case the SMF receives a clock drifting report from UPF, the SMF adjusts the BAT offset based on the existing procedures in TS 23.502 [3] and provides the updated BAT offset to the AF via PCF/TSCTSF/NEF. + +### 6.12.3 Procedures + +Figure 6.12.3-1 describe the procedure for this solution: + +![Sequence diagram illustrating the procedure for Cross layer scheduling optimization based on RAN feedback. The diagram shows interactions between UE, RAN, AMF, SMF, PCF, and AF/TSCTSF. The steps are: 1. AF/TSCTSF provides TSCAC (BAT window) to SMF via PCF. 2. SMF determines TSCAI. 3. SMF provides TSCAI (BAT window) to RAN via AMF. 4. RAN determines Expected BAT offset. 5. RAN provides BAT offset to SMF via AMF. 6. SMF performs optional communication with TN CNC as in Solution 9. 7. SMF provides BAT offset to AF/TSCTSF via PCF. 8. AF/TSCTSF adjusts the sending time accordingly.](7156cf400ef0e19f9d06a5d0549834a3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant PCF + participant AF/TSCTSF + + Note right of AF/TSCTSF: 1. TSCAC (BAT window) + AF/TSCTSF->>PCF: + PCF->>SMF: + Note right of SMF: 2. SMF determines TSCAI + SMF->>AMF: 3. TSCAI (BAT window) + AMF->>RAN: + Note right of RAN: 4. Expected BAT offset + RAN->>AMF: 5. BAT offset + AMF->>SMF: + Note right of SMF: 6. BAT offset [OPTIONAL] Communication with TN CNC as in Solution 9 + SMF->>PCF: 7. BAT offset + PCF->>AF/TSCTSF: + Note right of AF/TSCTSF: 8. Adjust the sending time accordingly + +``` + +Sequence diagram illustrating the procedure for Cross layer scheduling optimization based on RAN feedback. The diagram shows interactions between UE, RAN, AMF, SMF, PCF, and AF/TSCTSF. The steps are: 1. AF/TSCTSF provides TSCAC (BAT window) to SMF via PCF. 2. SMF determines TSCAI. 3. SMF provides TSCAI (BAT window) to RAN via AMF. 4. RAN determines Expected BAT offset. 5. RAN provides BAT offset to SMF via AMF. 6. SMF performs optional communication with TN CNC as in Solution 9. 7. SMF provides BAT offset to AF/TSCTSF via PCF. 8. AF/TSCTSF adjusts the sending time accordingly. + +**Figure 6.12.3-1: Procedure for Cross layer scheduling optimization based on RAN feedback** + +1. AF/TSCTSF provides TSCAC to the SMF as described in clause 5.27.2 of TS 23.501 [2]. Optionally, the TSCTSF provides a BAT window (BAT-early and BAT-late) in UL and/or DL direction in the TSC Assistance Container to the SMF via PCF based on the AF request. +2. The SMF determines the TSCAI for the QoS Flow based on the TSC Assistance Container of the PCC rule (including BAT windows) bound to the QoS Flow as described in clause 5.27.2.4 of TS 23.501 [2]. +3. The SMF transfer the TSCAI generated in step 2 to the RAN. +4. NG-RAN determines the BAT offset(s) as described in clause 6.12.2. +5. NG-RAN provides the BAT offset(s) to SMF. + +6. [OPTIONAL] If Solution 9 is used to interwork with TSN in the transport network, the SMF adds the received BAT offset in UL or DL direction to the BAT-early in UL or DL direction, respectively. The SMF uses the resulted new BAT value(s) as an input to the formula as described in Solution 9, when the SMF calculates the EarliestTransmitOffset(s) to the CNC in Transport Network. +7. SMF provides the BAT offset(s) to the TSCTSF/AF. +8. The AF receives the offset time or expected BAT and notifies the application to adapt the DL transmission schedule to it. + +If the AF wishes to change the accepted BAT offset, the AF can update the TSCTSF with the new BAT window by initiating a new QoS update procedure as in step 1. The TSCTSF updates the TSCAC based on the AF update. + +### 6.12.4 Impacts on services, entities and interfaces + +NG-RAN: + +- Supports of BAT offset calculating and reporting. + +AF: + +- Receiving BAT offset. +- Providing a BAT window. +- Notifying the applications to adapt the DL transmission schedule to it. + +SMF: + +- Mapping the BAT offset between external clock and the 5G clock. +- Support of signalling the BAT offset and BAT window. + +PCF/TSCTSF/NEF + +- Support of signalling the BAT offset BAT window. + +## 6.13 Solution #13: Pro-active RAN burst timing preference provision + +### 6.13.1 Introduction + +This solution enables AF to configure burst transmission scheduling (transmission time and/or periodicity) optimally considering the radio configuration. This is achieved by signalling RAN burst timing preferences pro-actively to AF at the time of QoS configuration phase. + +### 6.13.2 Functional Description + +This solution is based on the following principles: + +- The AF indicates its burst timing adaptation capabilities in QoS request together with the TSC stream characteristics to TSCTSF. The TSCTSF sends burst timing adaption capabilities in TSCAC to the PCF: + - The application may be capable of adapting burst sending time and/or burst periodicity proactively based on the feedback. +- The SMF receives the TSCAC including burst timing adaptation capability from the PCF and sends it to the RAN in TSCAI. +- For a given UE, the RAN node derives the preferred time window for burst arrival taking at least radio configuration and radio resource status into account and communicates the derived burst timing preferences to + +5GC. RAN burst timing preferences includes both the burst arrival window (BAW) in absolute time and burst periodicit(ies) separately for UL and DL in order to align periodic burst optimally to the radio configuration at the radio interface. Burst arrival window (BAW) refers to the time period that is provided by RAN, including the earliest possible absolute time and the latest possible absolute time (taking radio configuration and radio resources status into account). + +- RAN can provide one/multiple of periodicities as part of feedback to AF based on the periodicity values of the TDD cycle specified in TS 38.331 [5]. + +NOTE 1: If the application is unable to adapt the traffic according to burst timing preferences provided by the AF, there could be misalignment between incoming traffic and transmission opportunity in the RAN. + +- The SMF translates the (absolute time) burst arrival window from 5G clock to external clock (depending on AF time domain) and from RAN reference point to 5G ingress reference point considering the clock drift between the 5G clock and external clock, UE/DS-TT residence time and CN PDB. The SMF forwards the preferred 5G Ingress BAW and preferred periodicity for UL and DL along with UE/DS-TT residence time to the PCF. +- The TSCTSF receives burst timing preferences (BAW and periodicity) from the PCF. The TSCTSF may derive exact 5G ingress burst arrival times from the burst arrival window from the RAN node. +- The TSCTSF forwards burst timing preferences to the AF. + +NOTE 2: Achieving determinism for the transport network (i.e. to avoid inaccuracies with CN PDB) is out of scope for this solution. + +### 6.13.3 Procedures + +As shown in figure below, the solution utilizes existing procedures. Mainly following enhancements are proposed: + +1. The AF session with requested QoS procedure (clause 4.15.6.6 of TS 23.502 [3]) is used for burst timing adaptation capability signalling from AF to PCF. + - The TSCTSF includes the burst timing adaptation capabilities in TSCAC. +2. The burst timing adaptation capability is forwarded to RAN by reusing PDU session modification procedure. The PDU session modification procedure is also used for RAN timing preference signalling to the PCF. + - The SMF derives the TSCAI and includes the burst timing adaptation capabilities in TSCAI. + - The RAN derives RAN burst timing preferences (preferred RAN BAW and periodicity) based on the radio configuration and radio resource status, and performs admission control. RAN communicates the derived timing preferences to SMF (through AMF). + - The SMF translates RAN BAW to 5GS ingress BAW and signals RAN preferences to PCF. +3. The notification procedures are utilized for burst timing preference signalling from PCF to TSCTSF and from TSCTSF to AF. + - The TSCTSF derives exact BAT from the BAW and includes BAT to the NEF. + - The TSCTSF provides the updated BAT value as part of TSC Assistance container which is eventually forwarded to the SMF and provided as updated TSCAI to the RAN. + +![Sequence diagram illustrating the procedure for AF requested QoS with burst timing adaptation. The diagram shows interactions between UE, RAN, SMF, PCF, TSCTSF, NEF, and AF. It is divided into three main phases: 1. AF session with requested QoS, 2. PDU session modification, and 3. RAN preference notification. A horizontal line at the bottom indicates the TSC flow.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant SMF + participant PCF + participant TSCTSF + participant NEF + participant AF + + Note over UE, PCF: PDU session setup + + Note over PCF, AF: 1. AF session with requested QoS + AF->>NEF: Nef_AfsessionWithQoS_Update request [Adapt. Capability] + NEF->>TSCTSF: Ntsctsf_QoSandTSCAssistance_Create request: [Adapt. Capability] + TSCTSF->>PCF: Npcf_PolicyAuthorization_Update request TSCAC [Adapt. Capability] + + Note over SMF, RAN: 2. PDU session modification + PCF->>SMF: Npcf_SMPolicyControl_UpdateNotify request TSCAC [Adapt. Capability] + SMF->>RAN: PDU Session Request TSCAI [Adapt. capability] + Note over RAN: Admission control Preferred RAN BAW and periodicity derivation + RAN->>SMF: PDU Session Response [RAN BAW, periodicity] + Note over SMF: RAN BAW to ingress BAW translation. + SMF->>PCF: Npcf_SMPolicyControl_Update request [ingress BAW, periodicity] + + Note over PCF, AF: 3. RAN preference notification + PCF->>TSCTSF: Npcf_PolicyAuthorization_Notify [ingress BAW, periodicity] + Note over TSCTSF: BAT derivation from BAW + TSCTSF->>NEF: Ntsctsf_QoSandTSCAssistance_Update [ingress BAT, periodicity] + NEF->>AF: Nef_AfsessionWithQoS_Notify [ingress BAT, periodicity] + + Note over UE, AF: TSC flow + +``` + +Sequence diagram illustrating the procedure for AF requested QoS with burst timing adaptation. The diagram shows interactions between UE, RAN, SMF, PCF, TSCTSF, NEF, and AF. It is divided into three main phases: 1. AF session with requested QoS, 2. PDU session modification, and 3. RAN preference notification. A horizontal line at the bottom indicates the TSC flow. + +Figure 6.13.3.1-1: Procedure for AF requested QoS with burst timing adaptation + +### 6.13.4 Impacts on existing services and interfaces + +#### AF: + +- Indication of burst timing adaptation capabilities. +- Burst sending schedule adaptation according to the received timing preferences. + +#### TSCTSF: + +- Reception and forwarding of burst timing adaptation capabilities. +- Receptions of RAN timing preferences from the PCF. +- Derivation of the exact BAT from the wider BAW from the RAN and timing coordination between burst of different TSC streams and providing the BAT value as part of updated TSCAI to the RAN. + +#### RAN: + +- Reception of Adjustment Capability flag that triggers derivation of RAN Burst arrival window and periodicity. +- Derivation of RAN burst timing preferences based on the radio configurations and radio resource status. + +#### SMF: + +- Translation of RAN burst arrival window to 5GS ingress burst arrival window. + +#### NEF, PCF: + +- Support of signalling burst timing adaptation capabilities and RAN timing preferences. + +## 6.14 Solution #14: Assisted and Complement Timing Support + +### 6.14.1 General + +**Editor's note:** Whether this solution is in scope of the key issue is FFS. + +This solution is addressing the requirement for timing resiliency towards a client network (external network that requires a resilient timing service by the 5GS), as backup when the local primary time source fails, or as a complement to calibrate an inaccurate local primary timing source in the client network. + +In these cases, delivering a stable and accurate phase or frequency is sufficient (no need to deliver time information over the 5G network). + +This solution proposes to support Assisted Timing to provide backup timing service which if applied to 5GS implies a low impact since the only timing information to be provided is a stable phase or frequency only. As an alternative, the stable phase synchronization could be offered in order to complement (by calibrating) the external inaccurate primary local source, i.e. Complement Timing. In the case of Complement Timing where timing information is provided in terms of phase synchronization, NG-RAN is required to deliver phase synchronization (frequency synchronization is not sufficient). + +If the client network supports receiving some form of assisted/complement timing and requires Timing Resiliency from 5GS via the already supported Time Synchronization service activation, the 5GS will be able to provide assisted/complement timing, where the timing information may be phase or frequency. The AF request therefore may indicate during the Time Synchronization service activation, that Timing Resiliency is required, whether assisted or complement timing is required, the type to timing information (phase or frequency). Additional parameters need to be provided such as service availability (including holdover time), and frequency/phase accuracy compared to UTC frequency/phase, respectively. Like with per-Uu interface time error budget, the frequency/phase accuracy has to be calculated per UE (per Uu interface) by TSCTSF and provided to NG-RAN. The timing service can be provided over different types of external interfaces, e.g. (g)PTP as defined in TS 23.501 [2] or by an implementation specific interface. + +If Timing Resiliency is required, the client network should receive feedback (status report) whenever the service requirements (e.g. time error budget, UTC traceability, frequency/phase accuracy, etc.) are out of the agreed range. Moreover, status reports content just indicate that requirements were not achieved, instead of including the actual values of the parameters. How to provide the status report is out of the scope in this solution. + +### 6.14.2 Functional Description + +This solution is based on the following principles: + +- AF may include in its request for time synchronization service the following: + - Timing Resiliency requirement, including the following parameters: + - Assisted or complement timing requirement; + - Type of timing information required (phase or frequency); + - Frequency/phase accuracy requirement compared to UTC frequency/phase, respectively. + +**Editor's note:** It is FFS whether to include this list of specific parameters as part of the subscription data related to KI #3. + +**NOTE:** Other parameters such as service availability (including holdover time) and stability level of the timing information (time, phase or frequency) are relevant and can apply to this solution. + +- Status report is sent to UE application and to AF when one or more agreed requirements are out of range, indicating that service requirements are not achieved. + +### 6.14.3 Procedures + +Existing time synchronization activation procedures (see clause 4.15.9 of TS 23.502 [3]) are reused, where the AF request content is modified to include Timing Resiliency requirement, whether assisted/complement timing is required, the type of timing information (phase or frequency), frequency/phase accuracy. + +Extract of clauses from TS 23.502 [3] (using approved S2-2203232 from SA WG2 meeting #150E for clause 4.15.9.4) are presented showing the changes proposed to support this solution. + +NOTE: Except for clause 4.15.9.3.1, where time synchronization parameters are added, procedures in clause 4.15.9.3 remain unchanged. + +Clause 4.15.9.4 of TS 23.502 [3] is also modified to add parameters to the time synchronization table, to state that TSCTSF calculates the Uu frequency/phase accuracy, and to transfer time resiliency parameters (including assisted or complement timing requirement, timing information type, frequency/phase accuracy), likewise Uu time synchronization error budget, to NG-RAN. + +#### 6.14.3.1 Procedures for (g)PTP time distribution + +To procedures are presented as changes (underlined text) to clause 4.15.9.3.1 of TS 23.502 [3], as follows: + +This procedure can be used by the AF to activate, modify or deactivate the (g)PTP instances in 5GS. + +The AF may activate the time synchronization service using the Nnef\_TimeSynchronization\_ConfigCreate service operation. The service operation creates a time synchronization configuration based on the service parameters as indicated in the create request. The AF may update the time synchronization configuration using the Nnef\_TimeSynchronization\_ConfigUpdate service operation. The AF may deactivate the time synchronization service using the Nnef\_TimeSynchronization\_ConfigDelete service operation, which deletes the corresponding time synchronization service configuration. + +The Nnef\_TimeSynchronization\_ConfigCreate and Nnef\_TimeSynchronization\_ConfigUpdate request may contain the parameters as described in Table 6.14.3.1-1. + +**Table 6.14.3.1-1: Description of Time Synchronization service parameters** + +| Time Synchronization Parameter | Description | +|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PTP instance type | Identifies the requested PTP instance type as described in clause 5.27.1.4 of TS 23.501 [2]. | +| Transport protocol | Identifies the requested transport protocol for PTP instance as described in clause 5.27.1.4 of TS 23.501 [2]. This is applicable for IEEE Std 1588 [8] Boundary Clock and Transparent Clock operation. | +| PTP Profile | Identifies the PTP profile for the PTP instance as requested by AF. | +| Grandmaster enabled | Indicates whether the AF requests the PTP instance in 5GS to be able to act as a grandmaster for PTP or gPTP (depending on the requested PTP instance type). This is applicable for IEEE Std 1588 [8] Boundary Clock or IEEE Std 802.1AS [7] operation.
[optional] | +| Grandmaster priority | Indicates a priority used as defaultDS.priority1 when generating Announce message when 5GS acts as (g)PTP GM. Applicable only if the Grandmaster enabled = TRUE. If omitted, the default value as described in the PTP Profile is used.
[optional] | +| Time Domain | (g)PTP domain of the PTP instance as defined in IEEE Std 1588 [8]. | +| Temporal Validity Condition | Indicates start-time and stop-time attributes that describe the time period when the time synchronization service for a PTP instance is active.
[optional] | +| Time synchronization error budget | Indicates the time synchronization budget for the time synchronization service (as described in clause 5.27.1.9 of TS 23.501 [2]).
[optional] | +| Timing resiliency | Indicates whether the synchronization service will be used to provide timing resiliency. | +| >Assisted/Complement timing method | Indicates whether Assisted timing or Complement timing is used. | +| >Type of timing information | Indicates which type of timing information will be provided (time, frequency, phase). | +| >Required timing information accuracy | It provides the required phase or frequency (according to type of timing information specified) accuracy compared to the UTC phase or frequency (according to type of timing information specified). | +| For each PTP port in the PTP instance | | +| Either UE identity (for a DS-TT port), or "N6 interface" indication | Identifies the UE/DS-TT which the parameters below apply. "N6 interface" indicates that the parameters below apply to the N6 interface.
If the "PTP port" needs to be identified, this field refers to the UE identity (GPSI or SUPI).
If the N6 termination needs to be identified, then this field indicates "N6 interface" flag, instead of SUPI or GPSI. | +| PTP enabled | TRUE/FALSE. This is used to set the portDS.portEnable. If omitted, the default value as described in the PTP Profile is used.
[optional] | +| Log Sync Interval | Specifies the mean time interval between successive Sync messages. This is applicable for IEEE Std 1588 [8] Boundary Clock or IEEE Std 802.1AS [7] operation. If omitted, the default value as described in the PTP Profile is used.
[optional] | + +| | | +|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Use management settable Log Sync Interval | TRUE/FALSE. This is applicable if the PTP Profile is I IEEE Std 802.1AS [7].
When set to FALSE, the Log Sync Interval is used to set the initialLogSyncInterval as described in IEEE Std 802.1AS [7]. When set to TRUE, the Log Sync Interval is used to set the mgtSettableLogSyncInterval as described in IEEE Std 802.1AS [7].
If omitted, the default value as described in the IEEE Std 802.1AS [7] is used.
[optional] | +| Log Announce Interval | Specifies the mean time interval between successive Announce messages. This is applicable for IEEE Std 1588 [8] Boundary Clock or IEEE Std 802.1AS [7] operation. If omitted, the default value as described in the PTP Profile is used.
[optional] | +| Use management settable Log Announce Interval | TRUE/FALSE. This is applicable if the PTP Profile is IEEE Std 802.1AS [7].
When set to FALSE, the Log Announce Interval is used to set the initialLogAnnounceInterval as described in IEEE 802.1AS. When set to TRUE, the Log Announce Interval is used to set the mgtSettableLogAnnounceInterval as described in IEEE Std 802.1AS [7].
If omitted, the default value as described in the IEEE Std 802.1AS [7] is used.
[optional] | + +Editor's note: The purpose of the timing resiliency parameters for (g)PTP-based time synchronization is FFS. + +The AF may use Nnef\_TimeSynchronization\_CapsSubscribe service operation as described in clause 4.15.9.2 of TS 23.502 [3] to learn the UE capabilities for time synchronization service. The Nnef\_TimeSynchronization\_CapsNotify service operation indicates the list of UE identities, User-plane Node ID, and the Subscription Correlation ID. The AF can use the Subscription Correlation ID and the user-plane node ID received in the Nnef\_TimeSynchronization\_CapsNotify service operation as a target of the Nnef\_TimeSynchronization\_ConfigCreate request. The NEF uses the Subscription Correlation ID and user-plane node ID to determine the list of UEs and list of AF-sessions to which the Nnef\_TimeSynchronization\_ConfigCreate service operation is targeted to. + +#### 6.14.3.2 Procedures for 5G access stratum time distribution + +To procedures are presented as changes (underlined text) to clause 4.15.9.4 of TS 23.502 [3], (taken from approved S2-2203232) as follows: + +- The AF can use the procedure to activate, update or delete the 5G access stratum time distribution for one UE or a group of UEs. +- The AF may query the status of the 5G access stratum time distribution using Nnef\_ASTIGet service operation. The Nnef\_ASTICreate and Nnef\_ASTIUpdate request may contain the parameters as described in Table 6.14.3.2-1. + +**Table 6.14.3.2-1: Description of 5G access stratum time distribution parameters** + +| Parameter | Description | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5G access stratum time distribution indication (enable, disable) | Indicates that the access stratum time distribution via Uu reference point should be activated or deactivated for the associated UE identities. | +| Time synchronization error budget | Indicates the time synchronization error budget for the time synchronization service (as described in clause 5.27.1.9 of TS 23.501 [2]).
[optional] | +| Temporal Validity Condition | Indicates start-time and stop-time attributes that describe the time period when the time synchronization service is active.
[optional] | +| Timing resiliency | Indicates whether the synchronization service will be used to provide timing resiliency. | +| >Assisted/Complement timing method | Indicates whether Assisted timing or Complement timing is used. | +| >Type of timing information | Indicates which type of timing information will be provided (frequency, phase). | +| >Required timing information accuracy | It provides the required phase or frequency accuracy (according to type of timing information specified) compared to the UTC phase or frequency (according to type of timing information specified). | + +![Sequence diagram showing the management of 5G access stratum time information. Lifelines: AMF, PCF, BSF, UDM, TSCTSF, NEF, AF. The diagram illustrates the interaction between these entities for steps 1 through 12, including policy association establishment, AF requests to NEF, TSCTSF interactions, UDM/BSF management, and PCF authorization.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant PCF + participant BSF + participant UDM + participant TSCTSF + participant NEF + participant AF + + Note over AMF, PCF, BSF: 1. AM Policy Association Establishment + Note right of AF: 2. Nnef_ASTI_Create/Update/Delete/Get request + Note right of NEF: 3. Ntscstf_ASTI_Create/Update/Delete/Get request + Note right of TSCTSF: 4. Nudm_SDM_Get request + Note right of UDM: 5. Nudm_SDM_Get response + Note right of UDM: 6. Nbsf_Management_Subscribe + Note right of BSF: 7. Nbsf_Management_Notify + Note right of BSF: 8. Npcf_AMPolicyAuthorization_Create/Update request + Note left of AMF: 9. AM Policy Association Modification initiated by the PCF + Note right of PCF: 10. Npcf_AMPolicyAuthorization_Create/Update response + Note right of PCF: 11. Ntscstf_ASTI_Create/Update/Delete/Get response + Note right of TSCTSF: 12. Nnef_ASTI_Create/Update/Delete/Get response + +``` + +Sequence diagram showing the management of 5G access stratum time information. Lifelines: AMF, PCF, BSF, UDM, TSCTSF, NEF, AF. The diagram illustrates the interaction between these entities for steps 1 through 12, including policy association establishment, AF requests to NEF, TSCTSF interactions, UDM/BSF management, and PCF authorization. + +**Figure 6.14.3.2-1: Management of 5G access stratum time information** + +1. AM Policy Association establishment as described in clause 4.16.1 in TS 23.502 [3]. +2. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): + - To create a new request, the AF provides access stratum time distribution parameters to the NEF using the Nnef\_ASTI\_Create service operation (together with the AF identifier and potentially further inputs as specified in table 6.14.3.2-1), including a target (one UE identified by SUPI or GPSI, a group of UEs identified by an External Group Identifier. The NEF maps the External Group Identifier to an Internal Group Identifier and any GPSI to a SUPI). + - To update or remove an existing request, the AF invokes an Nnef\_ASTI\_Update or Nnef\_ASTI\_Delete service operation providing the corresponding time synchronization configuration id. + - To query the status of the access stratum time distribution, the AF invokes Nnef\_ASTI\_Get service operation providing the target (List of UE identities (SUPI or GPSI)). + +The AF that is part of operator's trust domain may invoke the services directly with the TSCTSF. + +NOTE 1: Steps 1 and 2 can occur in any order. + +3. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution): + +- The NEF authorizes the request. After successful authorization, the NEF invokes the Ntsctsf\_ASTI\_Create/Update/Delete/Get service operation with the TSCTSF discovered and selected as described in clause 6.3.24 of TS 23.501 [2]. +- The TSCTSF determines whether the targeted UE is part of a PTP instance in 5GS, if so the TSCTSF rejects the request (steps 4-10 are skipped). + +(When the procedure is triggered by PTP instance activation, modification, or deactivation in the TSCTSF): + +- If time synchronization error budget is provided by the AF, the TSCTSF may use the PTP port state of each DS-TT to determine an Uu time synchronization error budget for corresponding SUPIs that are part of the PTP instance. + - If time synchronization error budget is provided by the AF, the TSCTSF calculates the Uu time synchronization error budget as described in clause 5.27.1.9 of TS 23.501 [2]. + - If frequency or phase accuracy compared to UTC phase or frequency respectively, has been provided, the TSCTSF calculates the Uu accuracy value. +4. If the AF request targets a group of UEs, the TSCTSF uses the Nudm\_SDM\_Get request to retrieve the subscription information (SUPI list) from the UDM using the Internal Group ID. + 5. The UDM provides the Nudm\_SDM\_Get response containing a SUPI list that identifies UEs that belong to that group of UEs. + 6. The TSCTSF searches the PCF for the UE using Nbsf\_Management\_Subscribe with a SUPI as an input parameter, indicating that it is searching for the PCF that handles the AM Policy Association of the UE. + 7. The BSF provides to the TSCTSF the identity of the PCF for the UE for the requested SUPI via an Nbsf\_Management\_Notify operation. If matching entries already existed in the BSF when step 6 is performed, this shall be immediately reported to the TSCTSF. + 8. The TSCTSF sends to the PCF for the UE its request for the AM policy of the UE (identified by SUPI) using Npcf\_AMPolicyAuthorization request, containing the 5G access stratum time distribution indication (enable, disable) and optionally the calculated Uu time synchronization error budget, and the timing resiliency parameters (if provided), including the Uu frequency or phase accuracy. + 9. If the PCF receives multiple time synchronization error budgets or frequency/phase accuracy for a given UE, then the PCF picks the most stringent budget or frequency/phase accuracy. The PCF takes a policy decision and then the PCF may initiate an AM Policy Association Modification procedure for the UE as described in clause 4.16.2.2 of TS 23.502 [3] to provide AMF the 5G access stratum time distribution parameters. As part of this, the AMF shall, if supported, send the 5G access stratum time distribution indication (enable, disable) and the Uu time synchronization error budget and timing resiliency parameters, when they are available, to an NG-RAN node using NGAP procedures (e.g. UE Context Setup/Modification) specified of TS 38.413 [12]. The NG-RAN node shall, if supported, store the information in the UE Context. Based on this information, the NG-RAN node provides the 5GS access stratum timing to the UE according to the Uu time synchronization error budget and timing resiliency parameters as provided by the TSCTSF (if supported by UE and NG-RAN). + +NOTE 2: 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 [13]. + +10. The PCF of the UE replies to the TSCTSF with the result of Npcf\_AMPolicyAuthorization operation. +11. The TSCTSF responds the AF with the Ntsctsf\_ASTI\_Create/Update/Delete/Get service operation response. +12. The NEF informs the AF about the result of the Nnef\_ASTI\_Create/Update/Delete/Get service operation performed in step 2. + +### 6.14.4 Impacts on services, entities and interfaces + +AF: + +- Formulation of the AF request that may include parameters indicating requirements for Timing Resiliency, assisted timing/complement timing and type of timing information. These parameters are delivered to RAN. + +NOTE: There can be implications regarding the provided frequency/phase accuracy influencing the operation of (g)PTP (including correcting the content of (g)PTP messages) and certain parameters (such as clockClass) in the IEEE1588 data sets to be delivered to PMIC/BMIC. (g)PTP messages may not be used (e.g. in the case of a frequency synchronization service, or because they may not be needed when the level of accuracy is out of range), however (g)PTP messages may be received and there might be the need to process them at the DS-TT/NW-TT and update certain fields in the Announce messages. + +Editor's note: The reasons to update Announce messages at DS-TT/NW-TT and how to trigger this behaviour is FFS. + +NG-RAN: + +- Supporting delivery of frequency and phase synchronization. There is no expected impact to generate the frequency or phase synchronization, since these are subsets of the time synchronization, e.g. no SIB need to be sent. The phase/frequency can be extracted by client network (as defined in clause 6.14.1) using the SFNs of the regular radio signal, as long as this signal has guaranteed performance and UTC traceability. gNB may receive requirement parameters such as Timing Resiliency requirement, assisted/complement timing, the timing information type to be delivered, and frequency/phase accuracy compared to UTC frequency/phase respectively. This information enables NG-RAN to determine if and how to provide 5G reference timing information to the UE efficiently (i.e. RRC/SIB). How NG-RAN is using this information is up to RAN implementation. + +Editor's note: Details of RAN behaviour for phase/frequency sync, and related to that the need for additional information to be sent to RAN to trigger such behaviour is FFS. + +TSCTSF: + +- Calculates the frequency/phase accuracy for the UE (Uu interface) and transfers to NG-RAN via PCF, AMF. + +## 6.15 Solution #15: Burst arrival time adaptation + +### 6.15.1 Introduction + +This solution enables the network to adjust the burst arrival time by signalling positive or negative offset values (e.g. +3 ms) for UL scheduling and DL scheduling to the AF so that the AF can adjust the burst sending time accordingly. + +### 6.15.2 Functional Description + +This solution is based on the following principles: + +- For DL scheduling: refer to solution #2. +- For UL scheduling: Upon reception of UL packets at UE from the application on the UE or from the device connected to the UE, UE determines a relative burst arrival time offset value in reference to the current Burst Arrival Time experienced by UE (i.e. in reference to when UE currently receives bursts) and the scheduling UL time slot at UE (e.g. in Configured Grants, as defined in TS 38.321 [11]). UE sends the time offset to RAN via RRC message when the time offset value reaches the configured threshold, and NG-RAN sends the burst arrival time offset value to SMF in the same way as for DL scheduling. Alternatively, UE may send the preferred burst arrival time offset to SMF using NAS SM signalling (providing the preferred time offset from UE AS layer to NAS layer is UE implementation specific). +- For downlink or uplink flows AF adapts the burst sending time based on the received offset. When receiving the burst arrival time offset for uplink flows, the AF determines the burst sending time by sending the offset to the application on the UE or the devices connected to the UE for adaption via application signalling. + +### 6.15.3 Procedures + +In addition to clause 6.2.3 in solution #2, RRC message or NAS SM message to signal support of burst arrival time offset value from UE to RAN and/or UE to SMF respectively. + +### 6.15.4 Impacts on services, entities and interfaces + +Besides the impacts documented in clause 6.2.4 of solution #2: + +- UE: Support of determining and signalling burst arrival time offset to RAN via RRC message. + +## 6.16 Solution #16: BAT adjustment during a QoS Flow setup or modification + +This solution is merged into Solution 12. + +### 6.16.1 Introduction + +This solution enables the 5GC to adapt applications to the downstream scheduling, and to upstream scheduling if necessary, in Uu reference point to meet really low latency (e.g. 2 ms) requirement. + +This solution makes the following assumptions: + +- NG-RAN can indicate an adjustment to the Burst Arrival Time (BAT offset) in a response to QoS Flow establishment or modification request. +- The solution builds upon Solution 10: 5GC acting as a CUC for CNC in TN; Solution 10 is used to configure the underlay network in the TN for the required traffic characteristics of the QoS Flow. This ensures that jitter in the transport network in DL direction can be reduced and thus the accuracy of the Burst Arrival Time for DL packets at the ingress of NG-RAN is improved. +- The same assumptions as in Solution 10 apply. + +### 6.16.2 Functional Description + +The solution is based on the architecture in Figure 6.16.2-1: + +![Figure 6.16.2-1: Architecture to support adaptation to the upstream / downstream scheduling. The diagram shows the flow of data and control signals between various network entities. At the top, a 'Listener' and 'UE/DS-TT' are connected to 'NG-RAN' via 'DL data'. 'NG-RAN' is connected to 'UPF/NW-TT' via 'N3 tunnel' and 'IP transport'. 'UPF/NW-TT' is connected to a 'Talker' via 'DL data'. Below 'NG-RAN', a 'CNC' is connected via 'TSCAC/ BAT offset' and 'IEEE 802.1Qdj' to a 'Transport Network'. The 'Transport Network' is connected to a 'CUC'. Below the 'CNC', a 'TSN AF' is connected to a 'PCF' via 'TSCAC/ BAT offset'. The 'PCF' is connected to an 'SMF', which is connected to a 'CUC'. Below the 'SMF', an 'AF' is connected to a 'TSCTSF' via 'TSCAC/ BAT offset'. The 'TSCTSF' is connected to a 'CUC'.](95c11a9c59e4ad4af81a0e635ceafe45_img.jpg) + +Figure 6.16.2-1: Architecture to support adaptation to the upstream / downstream scheduling. The diagram shows the flow of data and control signals between various network entities. At the top, a 'Listener' and 'UE/DS-TT' are connected to 'NG-RAN' via 'DL data'. 'NG-RAN' is connected to 'UPF/NW-TT' via 'N3 tunnel' and 'IP transport'. 'UPF/NW-TT' is connected to a 'Talker' via 'DL data'. Below 'NG-RAN', a 'CNC' is connected via 'TSCAC/ BAT offset' and 'IEEE 802.1Qdj' to a 'Transport Network'. The 'Transport Network' is connected to a 'CUC'. Below the 'CNC', a 'TSN AF' is connected to a 'PCF' via 'TSCAC/ BAT offset'. The 'PCF' is connected to an 'SMF', which is connected to a 'CUC'. Below the 'SMF', an 'AF' is connected to a 'TSCTSF' via 'TSCAC/ BAT offset'. The 'TSCTSF' is connected to a 'CUC'. + +**Figure 6.16.2-1: Architecture to support adaptation to the upstream / downstream scheduling** + +- The solution supports deployments with and without external TSN network: + - When integration with IEEE TSN applies: In addition what is described in Solution 10, this solution provides Burst Arrival Time (BAT) offset for DL direction from NG-RAN via SMF and PCF to the TSN AF. TSN AF can act as a CUC towards the CUC in external TSN network and provide the BAT offset as feedback to the + +external TSN network. The CUC then controls the CNC in external TSN network and adjusts the TSN streams accordingly. + +- b) When integration with IEEE TSN does not apply: In addition to what is described in Solution 10, this solution provides Burst Arrival Time (BAT) offset for DL direction from NG-RAN via SMF and PCF to the AF. The AF can then adjust the data streams accordingly by means that are out of scope of 3GPP. +- As described in Solution 10, Transport Network deploys a CNC that can be controlled by a CUC residing in the 5GC via the procedures specified in IEEE P802.1Qdj [10]. In addition what is described in Solution 10, this solution can provide an adjusted BAT for both UL and DL directions to the Transport Network, based on the feedback received from the NG-RAN. + +### 6.16.3 Procedures + +The figure 6.16.3-1 describes the overall procedure how QoS Flows are established with the solution. + +![Sequence diagram showing the QoS Flow establishment procedure between NG-RAN, PCF, SMF, UPF, and TN CNC. The steps are: 1. PCF determines PCC Rules; 2. SMF receives PCC Rules from PCF; 3. SMF indicates N4 rules for the QoS Flow to the UPF; 4. SMF provides the QoS profile to NG-RAN, and NG-RAN provides BAT offset values; 5. SMF provides traffic requirements and BAT offset values to TN CNC via CUC.](0c88b98a59dd5d549fed7b13c0ca6536_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN + participant PCF + participant SMF + participant UPF + participant TN CNC + + Note right of PCF: 1. [As in Solution X]: +PCF determines the PCC Rules + Note right of SMF: 2. [As in Solution X]: +SMF receives the PCC Rules from PCF. + Note right of SMF: 3. [As in Solution X]: +SMF indicates N4 rules for the QoS Flow to the UPF. + Note right of SMF: 4. [As in Solution X]: +SMF provides the QoS profile for the QoS Flow to NG-RAN. +[Enhancement to Solution X]: +NG-RAN provides BAT offset values based on upstream/downstream scheduling + Note right of SMF: 5. [As in Solution X]: +SMF provides the traffic requirements for the QoS Flow to TN CNC via CUC. +[Enhancement to Solution X]: +SMF provides the BAT offset values to TSN AF / AF. + +``` + +Sequence diagram showing the QoS Flow establishment procedure between NG-RAN, PCF, SMF, UPF, and TN CNC. The steps are: 1. PCF determines PCC Rules; 2. SMF receives PCC Rules from PCF; 3. SMF indicates N4 rules for the QoS Flow to the UPF; 4. SMF provides the QoS profile to NG-RAN, and NG-RAN provides BAT offset values; 5. SMF provides traffic requirements and BAT offset values to TN CNC via CUC. + +Figure 6.16.3-1: Overview of the QoS Flow establishment + +1. [No changes to Solution 10]: PCF receives the Policy Authorization service request from the AF/NEF/TSCTSF. The PCF composes the PCC Rules as specified in Release 17. PCF includes the TSCAC in the request when it invokes the SMF. +2. [No changes to Solution 10]: SMF receives the PCC Rules from the PCF. The SMF binds the PCC rule to a QoS Flow. +3. [No changes to Solution 10]: SMF indicates N4 rules for a QoS Flow to the UPF. The UPF assigns the CN tunnel endpoint address. The SMF determines a dynamic value for the CN PDB, based on the UPF and NG-RAN of the PDU Session. + +4. As described in Solution 10, the SMF provides the QoS profile for the QoS Flow to the NG-RAN. The SMF signals the dynamic value for the CN PDB for the QoS Flow to NG-RAN. NG-RAN assigns the AN tunnel endpoint address. + +As described in Solution 10, upon receiving the TSCAI for a QoS Flow from the SMF, if the TSCAI includes a BAT in UL direction, the RAN determines the corresponding BAT offset in UL direction at the gNB egress. The NG-RAN provides the value to the SMF in a response. As an enhancement to Solution 10, when the NG-RAN provides the offset value to SMF, the NG-RAN may adjust the offset value based on the upstream scheduling in Uu reference point. + +As an enhancement to Solution 10, if the NG-RAN determines a need to adjust the Burst Arrival Time for DL direction to adapt the applications to the downstream scheduling in Uu reference point, NG-RAN includes a BAT offset for DL direction in the response to the SMF. + +BAT offset is relative to the BAT value in corresponding direction NG-RAN has received from the SMF in TSCAI. BAT offset can take positive or negative values. + +5. After the SMF has setup a QoS Flow between UPF and NG-RAN, if the NG-RAN indicated a BAT offset for UL or DL direction to the SMF, the SMF deducts the received BAT offset from the BAT in UL or DL direction, respectively, that the SMF has received in the TSCAI for the given QoS Flow, and indicates the resulted new BAT value(s) to the Transport Network using the procedure as described in Solution 10. + +The SMF provides the BAT offset values in UL and DL direction (if available) to NEF/AF or TSN AF via PCF. When integration with IEEE TSN applies, TSN AF can act as a CUC towards the CUC in external TSN network and provide the BAT offset as feedback to the external TSN network. The CUC then controls the CNC in external TSN network and adjusts the TSN streams accordingly. + +**Editor's note:** Typically for TSN flows there would be already an external CUC. Whether CNC can handle two CUCs for the same flows is FFS. Whether CNC can replan TSN flows after they have started is FFS. + +When integration with IEEE TSN does not apply, the BAT offset values are provided to the AF, and the AF can then adjust the data streams accordingly by means that are out of scope of 3GPP. + +### 6.16.4 Impacts on services, entities and interfaces + +The same impacts as in Solution 10: 5GC acting as a CUC for CNC in TN. In addition, the following impacts are caused by this solution: + +SMF: + +- If the NG-RAN indicates a BAT offset for UL or DL direction to the SMF in a response to the QoS Flow establishment or modification request, the SMF deducts the received BAT offset from the current BAT in UL or DL direction, respectively, in the TSCAI for the given QoS Flow, and indicates the resulted new BAT value(s) to the Transport Network using the procedure as described in Solution 10. + +NG-RAN: + +- Determines a BAT offset in UL direction, based on the BAT in UL direction the NG-RAN receives from the SMF in TSCAI and the upstream scheduling in Uu reference point. +- Determines a BAT offset in DL direction, based on the BAT in DL direction the NG-RAN receives from the SMF in TSCAI and the downstream scheduling in Uu reference point. +- Provides the BAT offset values to the SMF in a response to the QoS Flow establishment or modification request. + +## 6.17 Solution #17: DS-TT and NW-TT assisted 5GS synchronization error detection + +### 6.17.1 Introduction + +The solution is proposed to solve Key Issue #1 for the object: "Study how RAN and 5GC learn about 5GS network timing synchronization status" and can be used by the other solutions. + +This solution addresses the following scenarios: + +- 5GS is acting as Bridge to distribute time information to UEs using PTP or gPTP, as defined in clause 5.27.1.7 of TS 23.501 [2]. +- The NG-RAN node is not able to detect the 5GS timing synchronization error due to implementation limits. + +**Editor's note:** It is FFS whether scenarios exist where the NG-RAN node cannot detect the 5GS timing synchronization error by itself. + +This solution has the following assumptions: + +- The UE/DS-TT, NG-RAN, UPF/NW-TT are synchronized with the 5G GM (i.e. the 5G internal system clock) as specified in TS 23.501 [2] and TS 38.331 [5]. +- The UE/DS-TT and UPF/NW-TT handle the (g)PTP messages by making timestamping according to 5G GM as specified in clause 5.27.1.2.2 of TS 23.501 [2]. +- The DS-TT and NW-TT can detect (g)PTP timing synchronization error by comparing the (g)PTP clock and 5G GM clock. +- If 5G GM degradation occurs, there is timing error when calculating the residence time in 5GS according to 5G GM timestamping. Then DS-TT or NW-TT can detect the (g)PTP time sync error. + +**Editor's note:** How DS-TT or NW-TT can detect time synch error is FFS. + +### 6.17.2 Functional Description + +The solution is based on the following principles: + +- The AF/NEF subscribes the time synchronization status notification from TSCTSF. +- TSCTSF subscribes for time synchronization status information report from NW-TT and DS-TT via PMIC/UMIC (i.e. the status of the synchronization of the PTP GM in NW-TT and DS-TT): + - When receiving the (g)PTP time synchronization signals, the DS-TT/NW-TT can detect the (g)PTP time synchronization offset between the (g)PTP local clock (i.e. the clock maintained by the device locally) and the (g)PTP clock calculated according to the time synchronization signal. If the (g)PTP time synchronization offset exceeds the configured threshold and the jitter of the time synchronization offset between the (g)PTP local clock and 5GS internal local clock does not exceed jitter threshold, DS-TT/NW-TT can decide that there is a timing synchronization error (i.e. Timing Sync Signal is not correct). If the time synchronization offset and the jitter both exceed their thresholds, DS-TT/NW-TT can decide that the (g)PTP local clock should be adjusted according to the time synchronization signal as in this case it can be assumed there is an error in the (g)PTP local clock. + +**Editor's note:** How DS-TT and NW-TT can decide that there is a timing synchronization error only based on observing an offset between their local clock and the time reported in (g)PTP is FFS. + +- If TSCTSF has subscribed the status report, the NW-TT and DS-TT reports (g)PTP timing synchronization status information to TSCTSF via PMIC/UMIC. +- When TSCTSF receives the (g)PTP time synchronization status information, it determines whether the (g)PTP synchronization error occurs in the ingress port of the (g)PTP domain or 5G GM synchronization error occurs in the serving RAN: + - The TSCTSF can determine the affected UE according to the time domain (for (g)PTP synchronization error) or the UE's RAN information (for 5G GM synchronization error). + +### 6.17.3 Procedures + +The exchange of PMIC/UMIC between TSCTSF and DS-TT/NW-TT is specified in clause 5.28.3 of TS 23.501 [2]. The enhancement is that DS-TT and NW-TT should report the (g)PTP timing synchronization status to TSCTSF via PMIC/UMIC. + +TSCTSF can determine the time synchronization error according to the (g)PTP timing synchronization status information as following: + +- Case A: Both DS-TT (maybe multiple DS-TTs belonging to the same time domain) and NW-TT report the (g)PTP timing synchronization error. TSCTSF can determine that the (g)PTP synchronization error occurs in the ingress port of the (g)PTP domain. +- Case B: Only DS-TT(s) or NW-TT reports the (g)PTP timing synchronization error (normally the egress port reports the timing synchronization error, while the ingress port does not). TSCTSF can determine that the (g)PTP timing synchronization error is caused by 5G GM synchronization error in the RAN serving the DS-TT related UE. + +TSCTSF may subscribe to the AMF to get the serving RAN of the UE(s) to determine the affected UE(s). + +### 6.17.4 Impacts on services, entities and interfaces + +DS-TT: + +- Support reporting the (g)PTP timing synchronization status information to TSCTSF via PMIC + +TSCTSF: + +- Receive (g)PTP time synchronization status information report from DS-TT and NW-TT and decide time synchronization error as above. + +NW-TT: + +- Report (g)PTP GM timing synchronization status information to TSCTSF via PMIC/UMIC. + +## 6.18 Solution #18: Subscription based control of time synchronization service + +### 6.18.1 Introduction + +This solution is proposed to solve Key Issue #3: Support for controlling 5G time synchronization service based on subscription. In this Key Issue, the time synchronization service scenarios already supported in 5G Release-17 and Release-16 based on access stratum or (g)PTP time distribution methods are addressed. + +### 6.18.2 Functional Description + +The solution is based on the following principles: + +- UE subscription data types stored in the UDM are extended to include two new data structures related to time synchronization service: + - The "Access and Mobility Subscription data" is extended with the following field: + - Access Stratum Time Synchronization Service Authorization: + - Indication whether the UE is authorized to receive RTT reception via RRC dedicated signalling Note this field applies to the gNB using dedicated RRC signalling to disseminate access stratum time information to the UE. + - (Optionally) Uu time synchronization error budget + - (Optionally) Start and stop time defining active times of Access Stratum Time Synchronization Service for the UE. Start and stop times do not include the date information + - (Optionally) Coverage Area: defining a list of TAs where the ASTI-based time synchronization is available for the UE. + +- The AMF retrieves "Access Stratum Time Synchronization Service Authorization" in the UDM when the UE registers with the 5GS. If "Access Stratum Time Synchronization Service Authorization" is available, the AMF configures the access stratum time distribution information at the NG-RAN accordingly using Rel-17 NGAP signalling. +- The TSCTSF may retrieve "Access Stratum Time Synchronization Service Authorization" in the UDM for getting the UE's subscribed Uu time synchronization error budget. The TSCTSF should not configure the Uu time synchronization error budget to the NG-RAN exceeding the value in the UDM. +- A new subscription data "Time Synchronization Subscription data" with the following fields: + - 1) AF request Authorization: + - Indicates whether the UE is authorized for an AF-requested time synchronization services (either (g)PTP based or ASTI based). + - 2) The "Time Synchronization Service Authorization": + - One or more Subscribed time synchronization service ID(s): Provides reference to a PTP configuration pre-configured at the TSCTSF (i.e. DNN/S-NSSAI, PTP instance configuration within the 5GS, including e.g. PTP profile, PTP domain, etc.). + - 3) (Optionally) Start and stop times defining active times of Time Synchronization Service for the UE. Start and stop time do not include the date information. + - 4) (Optionally) Coverage Area: defining a list of TAs where the (g)PTP-based time synchronization is available for the UEs in the PTP instance. + - 5) Access Stratum Time Synchronization Service Authorization: + - Indication whether the UE is authorized to receive RTT reception via RRC dedicated signalling + +NOTE: This field applies to the gNB using dedicated RRC signalling to disseminate access stratum time information to the UE. + +- (Optionally) Uu time synchronization error budget +- For (g)PTP time distribution method, the TSCTSF accesses Time Synchronization Subscription data in the UDM and based on the subscription data, the TSCTSF may enable/disable time synchronization configuration for the UE with or without an AF request for the service. The trigger for the TSCTSF to retrieve this subscription data from the UDM is the notification from the PCF that a UE has established a PDU Session for a specific DNN/S-NSSAI (based on the PCF using Npcf\_PolicyAuthorization\_Notify service operation). +- For access stratum time distribution method with AF request, the TSCTSF retrieves Time Synchronization Subscription data available at the UDM and checks if the AF is allowed to request access stratum time synchronization as a service or not. +- The configuration of access stratum time distribution for a UE via Access Stratum Time Synchronization Service Authorization in the Access and Mobility Subscription data or AF request is assumed to mutually exclusive meaning that the AF is not allowed to modify the 5GS access stratum time distribution parameters if the UE is authorized to receive RTT according to the "Access and Mobility Subscription data". This is enforced by the AMF. +- The configuration of access stratum time distribution for a UE via Access Stratum Time Synchronization Service Authorization in the Time Synchronization Subscription data and Access and Mobility Subscription data simultaneously is considered as a configuration error. +- Access Stratum Time Synchronization Service Authorization and Time Synchronization Subscription Data is stored at the UDR. The UDM retrieves this subscription data from the UDR for other NFs to access it. +- For (g)PTP time distribution method, the TSCTSF may modify the PTP instance configuration by means of sending a PMIC to the impacted UE/DS-TT and UMIC to the UPF/NW-TT, as described in clause K.2.2 of TS 23.501 [2]. + +- For access stratum time distribution method, if AMF receives Access Stratum Time Synchronization Service Authorization from UDM, then AMF provides 5G access stratum time distribution indication and Uu time synchronization error budget (if part of the Access Stratum Time Synchronization Service Authorization received from the UDM) to NG-RAN. + +### 6.18.3 Procedures + +#### 6.18.3.1 Procedure for subscription based control of access stratum time synchronization service without AF request + +An overall procedure for subscription based control of access stratum time synchronization service without AF request for time synchronization is illustrated in Figure 6.18.3.1-1. + +![Sequence diagram illustrating the subscription based control of access stratum time synchronization service without AF request. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, and UDM. The steps are: 1. UE performs general registration procedure; 2. AMF sends Nudm_SDM_Get Request to UDM; 3. UDM responds with Nudm_SDM_Get Response (Enriched Access Stratum Time Synchronization Service Authorization); 4. AMF sends Nudm_SDM_Subscribe to UDM; 5. AMF sends N2 message (Access stratum time distribution configuration) to NG-RAN.](0f7871077bba48a2c97f7859a5edda0d_img.jpg) + +``` + +sequenceDiagram + participant UE/DS-TT + participant NG-RAN + participant AMF + participant UDM + Note right of UE/DS-TT: 1: UE performs general registration procedure (clause 4.2.2.2.2 in TS 23.502). + Note right of AMF: 2: Nudm_SDM_Get Request + AMF->>UDM: 2: Nudm_SDM_Get Request + Note right of UDM: 3: Nudm_SDM_Get Response (Enriched Access Stratum Time Synchronization Service Authorization) + UDM-->>AMF: 3: Nudm_SDM_Get Response + Note right of AMF: 4: Nudm_SDM_Subscribe + AMF->>UDM: 4: Nudm_SDM_Subscribe + Note right of AMF: 5: N2 message (Access stratum time distribution configuration) + AMF-->>NG-RAN: 5: N2 message + +``` + +Sequence diagram illustrating the subscription based control of access stratum time synchronization service without AF request. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, and UDM. The steps are: 1. UE performs general registration procedure; 2. AMF sends Nudm\_SDM\_Get Request to UDM; 3. UDM responds with Nudm\_SDM\_Get Response (Enriched Access Stratum Time Synchronization Service Authorization); 4. AMF sends Nudm\_SDM\_Subscribe to UDM; 5. AMF sends N2 message (Access stratum time distribution configuration) to NG-RAN. + +**Figure 6.18.3.1-1: Subscription based control of access stratum time synchronization service** + +1. The UE performs the registration procedure with the 5GS. +2. While the registration procedure is configured, the AMF retrieves the UE subscription data stored at the UDM as described in step 14b in clause 4.2.2.2. in TS 23.502 [3]. +3. If Access Stratum Time Synchronization Service Authorization is available at the UDM, the UDM provides it to the AMF. Optionally, if a valid start and stop time for time synchronization are included in the UE subscription data, the AMF should enable the ASTI time synchronization service only during this time period. +4. If the AMF receives Access Stratum Time Synchronization Service Authorization from the UDM in step 3, the AMF may subscribe to notifications for updates at the UDM. Optionally, if a valid geographical area for time synchronization is included in the UE subscription data, the AMF tracks the UE's location to determine the UE's presence (i.e. in or out of the subscribed "valid geographic area"). If the UE location is out of the "valid geographic area", the AMF determines not to activate ASTI time synchronization service for the UE. + +If the Access Stratum Time Synchronization Service Authorization contains a Coverage Area, the AMF subscribes for the UE mobility events locally. + +5. When the AMF is setting up or modifying the UE Context in the NG-RAN and AMF has received Access Stratum Time Synchronization Service Authorization from the UDM, then AMF provides access stratum attributes to NG-RAN via N2 message (5G access stratum time distribution indication and Uu time synchronization error budget). If Uu time synchronization error budget is not part of the Access Stratum Time Synchronization Service Authorization received from the UDM then AMF may send to NG-RAN a Uu time synchronization error budget based on a default pre-configured default value. + +The registration procedure continues as described in TS 23.502 [3]. + +If the Access Stratum Time Synchronization Service Authorization contains Start and stop times, 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 Access Stratum Time Synchronization Service Authorization contains Coverage Area, the AMF enables and disables the 5G access stratum time distribution indication to the NG-RAN when the UE moves inside or outside of the Coverage Area, respectively. + +#### 6.18.3.2 Procedure for subscription based control of access stratum time synchronization service with AF request + +An overall procedure for subscription based control of access stratum time synchronization service with asynchronous reception of an AF request for ASTI service is illustrated in Figure 6.18.3.2-1. + +![Sequence diagram illustrating the procedure for subscription based control of access stratum time synchronization service with AF request. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, PCF, UDM, TSCTSF, and AF.](b8efedb73292a798b3f2050f9335cae6_img.jpg) + +``` + +sequenceDiagram + participant AF + participant TSCTSF + participant UDM + participant PCF + participant AMF + participant NG-RAN + participant UE/DS-TT + + Note right of TSCTSF: 3: TSCTSF determines if AF is allowed to request ASTI based on UE's subscription + AF->>TSCTSF: 1: Ntscstf_ASTI_Create Request + TSCTSF->>UDM: 2: Nudm_SDM_Get (Time Synchronization Subscription Data) + TSCTSF->>PCF: 4: Npcf_AMPolicyAuthorization_Update Request + Note over PCF: 5: AM Policy Association Modification initiated by the PCF + PCF->>AMF: 6: N2 message (Access stratum time distribution configuration) + AMF->>NG-RAN: 6: N2 message (Access stratum time distribution configuration) + PCF->>TSCTSF: 7: Npcf_AMPolicyAuthorization_Update Response + TSCTSF->>AF: 8: Ntscstf_ASTI_Create Response + +``` + +Sequence diagram illustrating the procedure for subscription based control of access stratum time synchronization service with AF request. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, PCF, UDM, TSCTSF, and AF. + +**Figure 6.18.3.2-1: Subscription based control of access stratum time synchronization service with AF request** + +1. The AF request to influence the 5G access stratum time distribution. +2. The TSCTSF retrieves Time Synchronization Subscription Data available at the UDM: +3. The TSCTSF determines if the AF is allowed to request ASTI service. If authorized, the TSCTSF proceeds with ASTI service configuration. Otherwise, if the AF is not authorized, steps 4-7 are skipped. +4. The TSCTSF sends to the PCF for the UE its request to update the AM policy of the UE (identified by SUPI) containing the 5G access stratum time distribution indication (enable, disable) and optionally the calculated Uu time synchronization error budget (if available). +5. The PCF takes a policy decision and then the PCF may initiate an AM Policy Association Modification procedure for the UE as described in clause 4.16.2.2 of TS 23.502 [3] to provide AMF the 5G access stratum time distribution parameters. The PCF includes a Policy Control Request Trigger for the 5G access stratum time distribution into the request. +6. The AMF sends the 5G access stratum time distribution indication (enable, disable) and the Uu time synchronization error budget (if available) to the NG-RAN via N2 signalling. + +If the AMF has received Access Stratum Time Synchronization Service Authorization from the UDM as described in clause 6.18.3.1, the AMF ignores the 5G access stratum time distribution parameters received from + +the PCF. If the PCF included a Policy Control Request Trigger for the 5G access stratum time distribution into the request in step 5, the AMF initiates AM Policy Association Modification procedure for the UE as described in TS 23.502 [3] clause 4.16.2.1, indicating the 5G access stratum time distribution parameters as stored in the Access Stratum Time Synchronization Service Authorization. + +7. The PCF of the UE replies to the TSCTSF with the result of Npcf\_AMPolicyAuthorization operation. +8. The TSCTSF responds the AF with the Ntsctsf\_ASTI\_Create service operation response. + +#### 6.18.3.3 Procedure for subscription based control of (g)PTP time synchronization service without AF request + +An overall procedure for subscription based control of (g)PTP time synchronization service without AF request is illustrated in Figure 6.18.3.3-1. + +![Sequence diagram illustrating the subscription based control of (g)PTP time synchronization service without AF request. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, UPF/NW-TT, PCF, TSCTSF, and UDM. The steps are: 1. UE performs UE-requested PDU Session Establishment procedure (clause 4.3.2.2 in TS 23.502); 2. PCF invokes Npcf_PolicyAuthorization_Notify service operation to the TSCTSF; 3. TSCTSF uses the SUPI to retrieve the Time Synchronization Subscription Data available at the UDM; 4. TSCTSF determines (g)PTP time synchronization service configuration based on UE's subscription; 5. TSCTSF configures PTP instance as described in clause K.2.2 of TS 23.501.](91c33f8e1713989e8192322ec2d1212b_img.jpg) + +``` + +sequenceDiagram + participant UE/DS-TT + participant NG-RAN + participant AMF + participant UPF/NW-TT + participant PCF + participant TSCTSF + participant UDM + + Note over UE/DS-TT, UDM: 1: UE performs UE-requested PDU Session Establishment procedure (clause 4.3.2.2 in TS 23.502) + Note over PCF, TSCTSF: 2: Npcf_PolicyAuthorization_Notify + Note over TSCTSF, UDM: 3: Nudm_SDM_Get (Time Synchronization Subscription Data) + Note over TSCTSF: 4: TSCTSF determines (g)PTP time synchronization service configuration based on UE's subscription + Note over TSCTSF, UPF/NW-TT: 5: TSCTSF configures PTP instance as described in clause K.2.2 of TS 23.501 + +``` + +Sequence diagram illustrating the subscription based control of (g)PTP time synchronization service without AF request. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, UPF/NW-TT, PCF, TSCTSF, and UDM. The steps are: 1. UE performs UE-requested PDU Session Establishment procedure (clause 4.3.2.2 in TS 23.502); 2. PCF invokes Npcf\_PolicyAuthorization\_Notify service operation to the TSCTSF; 3. TSCTSF uses the SUPI to retrieve the Time Synchronization Subscription Data available at the UDM; 4. TSCTSF determines (g)PTP time synchronization service configuration based on UE's subscription; 5. TSCTSF configures PTP instance as described in clause K.2.2 of TS 23.501. + +**Figure 6.18.3.3-1: Subscription based control of (g)PTP time synchronization service without AF request** + +1. The UE performs the UE-requested PDU Session Establishment for data establishing connectivity. +2. The PCF determines if the PDU Session is potentially impacted by time synchronization service and invokes Npcf\_PolicyAuthorization\_Notify service operation to the TSCTSF discovered and selected for time synchronization to indicate there is a UE connected to a specific DNN/S-NSSAI configured for (g)PTP services. +3. The TSCTSF uses the SUPI to retrieve the Time Synchronization Subscription Data available at the UDM. +4. If the Time Synchronization Subscription Data contains: + - a) one or more Subscribed Time Synchronization Service ID(s) that can be mapped to PTP instance configuration(s), the TSCTSF determines if one or more of the PTP instance configurations match with the DNN/S-NSSAI of the given PDU Session. The TSCTSF assumes that the time-synchronization service cannot be controlled by an AF for the given SUPI. + - b) An indication that an AF-requested (g)PTP time synchronization service is allowed for the given UE and DNN/S-NSSAI, the TSCTSF adds the given SUPI to the list of SUPIs for which the time-synchronization service can be controlled by an AF. + - c) If TSCTSF receives neither a) nor b), the TSCTSF assumes that the time-synchronization service cannot be controlled by an AF for the given SUPI. The TSCTSF releases the AF-session with the PCF. +5. For each matching PTP instance configuration determined in step 4, 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 of TS 23.501 [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 of TS 23.501 [2]. + +If the Time Synchronization Subscription data for the UE in UDR contains start and stop times, the TSCTSF sets a timer for the expiration of start and stop time. Upon expiry of start time, the TSCTSF adds the PTP port in DS-TT to the corresponding PTP instance. Upon expiry of stop time, the TSCTSF temporarily removes the PTP port in DS-TT from the corresponding PTP instance. + +If the Time Synchronization Subscription data for the UE in UDR contains Coverage Area, the TSCTSF subscribes to UE's presence in Area of Interest at the discovered AMF(s) in similar manner as concluded for KI#2. When the TSCTSF determines that the UE has moved inside or outside of the Coverage Area, the TSCTSF adds or temporarily removes the PTP port in DS-TT from the corresponding PTP instance, in similar manner as concluded for KI#2. + +#### 6.18.3.4 Procedure for (g)PTP time synchronization service with AF request + +An overall procedure for (g)PTP time synchronization service with AF request. Steps 1 to 4 below are illustrated in figure 6.18.3.3-1. + +1. The UE performs the UE-requested PDU Session Establishment for data establishing connectivity. +2. Upon PDU Session establishment, the PCF determines if the PDU Session is potentially impacted by time synchronization service and invokes Npcf\_PolicyAuthorization\_Notify with the TSCTSF as configured in the PCF. The TSCTSF setups an AF-session with the PCF as described in clause 4.15.9.2 of TS 23.502 [3]. +3. The TSCTSF uses the SUPI to retrieve the Time Synchronization Subscription Data available at the UDM. +4. If the Time Synchronization Subscription Data contains: + - a) one or more Subscribed Time Synchronization Service ID(s) that can be mapped to PTP instance configuration(s), the TSCTSF determines if one or more of the PTP instance configurations match with the DNN/S-NSSAI of the given PDU Session. In this case, for each such PTP instance configuration, 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 of TS 23.501 [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 of TS 23.501 [2]. The TSCTSF assumes that the time-synchronization service cannot be controlled by an AF for the given SUPI. + - b) An indication that an AF-requested (g)PTP time synchronization service is allowed for the given UE and DNN/S-NSSAI, the TSCTSF adds the given SUPI to the list of SUPIs for which the time-synchronization service can be controlled by an AF. + - c) If TSCTSF receives neither a) nor b), the TSCTSF assumes that the time-synchronization service cannot be controlled by an AF for the given SUPI. The TSCTSF releases the AF-session with the PCF. +5. Based on received subscription data in step 4, the TSCTSF determines that the UE is authorized for the service, and the TSCTSF proceeds with rest of the procedure as described in clause 4.15.9.2 of TS 23.502 [3]. + +When the TSCTSF receives Ntsctsf\_TimeSynchronization\_CapsSubscribe service operation from the AF, the TSCTSF determines the matching AF-session(s) as described in clause 4.15.9.2 of TS 23.502 [3]. If the UE is not authorized for the service for the given DNN/S-NSSAI in the UDM, the TSCTSF does not consider the AF-session as matching. This implies that the time synchronization capability event notification does not list any of the SUPIs that cannot be controlled by an AF. + +### 6.18.4 Impacts on services, entities and interfaces + +#### UDR: + +- Storage and retrieval of Time Synchronization Subscription Data by the UDM. + +#### UDM: + +- Time Synchronization Subscription Data and Access Stratum Time Synchronization Service Authorization fields management. + +#### AMF: + +- Receive Access Stratum Time Synchronization Service Authorization from UDM. + +- Provide access stratum time distribution indication and Uu time synchronization error budget to RAN based on Access Stratum Time Synchronization Service Authorization received from UDM. +- Manage timers for start and stop times as indicated by the start and stop times in the Access Stratum Time Synchronization Service Authorization. +- Enables and disables the 5G access stratum time distribution for the UE based on the UE location and Coverage Area in the Access Stratum Time Synchronization Service Authorization. + +#### TSCTSF: + +- Time synchronization service configuration (i.e. ASTI and/or (g)PTP time distribution) based on UE's Time Synchronization Subscription Data. +- Manages the Coverage Area in the Time Synchronization Subscription Data in the same way as if it was received from the AF as concluded in KI#2. +- Subscription to Time Synchronization Subscription Data at the UDM. + +## 6.19 Solution 19: Support for controlling 5G time synchronization service based on subscription + +### 6.19.1 Introduction + +The solution enables the operator to control time synchronization service based on UE subscription for time critical services management. + +### 6.19.2 General description + +The following assumptions are made: + +- For specific UEs which the holdover capability is not supported or supported badly, the operator should provide them reference time information continuously. +- UE subscription should be taken into account when TSCTSF chooses a time information provider in 5GS. The subscription data may include time synchronization enable parameters or timing resiliency services parameters. According to the subscription data, TSCTSF can determinate whether and which timing source to provide timing synchronization service. +- UEs get time synchronization service by receiving 5GS access stratum time or time-synchronized UPF/NW-TT. 5G GM may have different sources of time/frequency like GNSS signal, Synchronous Ethernet (Sync E), PTP transport network, PPS input, etc. Besides, 5G GM may collocate with UPF or RAN, not limited with the deployment. + +Following are the principles for the solution: + +- In order to provide continuous time synchronization service for targeted UEs, 5GC should be informed if the time synchronization status of those UEs change. The time status changes can be resulted from some unexpected cases, e.g. time sources failure or UE mobility. +- The AF could send a request to TSCTSF (directly or via NEF) to control the (g)PTP time synchronization service and may target to a set of AF-sessions with a UE or multiple UE(s). In addition, the AF may request time synchronization distribution method, such as a Boundary Clock, peer-to-peer Transparent Clock, or end-to-end Transparent Clock or as a PTP relay instance. For all the AF-request, TSCTSF should check targeted UE(s) subscription data from the UDM first before it invokes time synchronization service. If necessary, the SMF would check the per UE subscription data again when PDU session establishment. +- The AF may request to use the 5G access stratum timing information for UE(s) or the attached DS-TT(s). When TSCTSF receives the request, it should get the targeted UE subscription data from the UDM to authorize the request. If needed, the AMF is responsible to check the per UE subscription data when it controls 5G-AN to provide 5G access stratum timing information. + +- A trusted AF can request a stringent/resilient time synchronization service for targeted UEs or DS-TTs if the UEs subscription supports. +- Time service parameters can be included in the UE subscription data: + - a) Authorized time synchronization method: access stratum, gPTP, or both; + - b) One or multiple authorized Uu error budget: e.g. 1us, 250ns, or other values. Multiple authorized Uu error budgets allows 5G network to select a certain Uu error budget, based on AF request. The enforced Uu error budget should not exceed the most stringent value. + +### 6.19.3 Procedures + +Below is the flow chart for AF requesting time synchronization service for targeted UE. + +#### 6.19.3.1 AF requesting time synchronization service for targeted UE + +Procedures of AF requesting time synchronization service for targeted UE are shown: + +![Sequence diagram showing the procedure for AF requesting time synchronization service for targeted UE. The diagram involves eight lifelines: DS-TT/UE, RAN, AMF, SMF, UPF/NW-TT, UDM, TSCTSF, and AF. The sequence starts with the AF sending a request to the TSCTSF. The TSCTSF then checks the UDM for subscription data. The UDM returns subscription data including time sync service or timing resiliency services parameters. The TSCTSF then determines a suitable time source. Finally, the TSCTSF provides the time sync service to the UEs using either PTP or gPTP based distribution (4a) or 5G access stratum distribution (4b).](71f0fd23b2f06b621ba89a65ee3c284c_img.jpg) + +``` + +sequenceDiagram + participant DS-TT/UE + participant RAN + participant AMF + participant SMF + participant UPF/NW-TT + participant UDM + participant TSCTSF + participant AF + + Note right of UDM: 0.subscription data including time sync service or timing resiliency services parameters. + + AF->>TSCTSF: 1b.AF request for timeSync Creat/Update service for UE + TSCTSF->>UDM: 2.Get subscription data from UDM + Note right of TSCTSF: 3.TSCTSF determines a suitable time source to provide time sync service based on UE subscription + TSCTSF->>UPF/NW-TT: 4a.Provide time sync service to UEs using PTP or gPTP based distribution + TSCTSF->>RAN: 4b.Provide time sync service to UEs using 5G access stratum distribution + +``` + +Sequence diagram showing the procedure for AF requesting time synchronization service for targeted UE. The diagram involves eight lifelines: DS-TT/UE, RAN, AMF, SMF, UPF/NW-TT, UDM, TSCTSF, and AF. The sequence starts with the AF sending a request to the TSCTSF. The TSCTSF then checks the UDM for subscription data. The UDM returns subscription data including time sync service or timing resiliency services parameters. The TSCTSF then determines a suitable time source. Finally, the TSCTSF provides the time sync service to the UEs using either PTP or gPTP based distribution (4a) or 5G access stratum distribution (4b). + +**Figure 6.19.3-1: AF requesting time synchronization service based on subscription** + +0. UDM subscription data may include a new subscription type for time synchronization service or timing resiliency service. The subscription data indicates whether or not the UE support time synchronization service or timing resiliency services. The subscription data may also include 5GS clock properties, e.g. clock class, accuracy, etc. to reflect the possible selection of clock source e.g. during GNSS unavailability. +1. AF request for time synchronization service for the UE. +2. When receiving the time synchronization request for the UE, the TSCTSF will check with UDM, whether and what information the UE has the subscription for time synchronization service. The time service parameter of UE subscription data refers to the above description. +3. TSCTSF determinates a suitable time source to provide time synchronization service for the UE if the subscription data is satisfied. +4. TSCTSF may sends the determinate information (with 5GS clock properties including e.g. clock class, accuracy information) to UPF for time synchronization service, UPF initiates PTP or gPTP based distribution to the UE to provide timing synchronization. Or TSCTSF may send the determinate information to RAN for time synchronization service, RAN initiates access stratum distribution to the UE to provide timing synchronization. + +### 6.19.4 Impacts on services, entities and interfaces + +TSCTSF: + +- Update the 5G time distribution indication based on UE subscription. +- Authorize time synchronization service request based on UE subscription. +- Providing time synchronization service based on UE subscription. +- Determining a suitable 5G timing source to provide time synchronization service for the UE. + +AMF: + +- Support to forward UE time synchronization service to targeted TSCTSF. + +UDM: + +- Support to perform the storage of UE Subscription data including time synchronization parameters or timing resiliency parameters. + +## 6.20 Solution #20: NG-RAN acting as CUC towards CNC of the N3 transport network + +### 6.20.1 Introduction + +Key idea of this solution is that NG-RAN acts as CUC towards the CNC of the N3 transport network. + +### 6.20.2 Functional Description + +The solution is based on the architecture in Figure 6.20.2-1: + +![Diagram of the architecture for NG-RAN acting as CUC towards CNC of the N3 transport network. The diagram shows an NG-RAN/CUC connected to a UPF via an N3 tunnel. Both are connected to a Transport network. The NG-RAN/CUC is also connected to a Transport Network CNC via a UNI. The Transport network is connected to the Transport Network CNC via a bidirectional arrow.](db730b8d3402ded94362bb3037b985ed_img.jpg) + +``` + +graph TD + NG_RAN_CUC[NG-RAN/CUC] --- N3_tunnel[N3 tunnel] + N3_tunnel --- UPF[UPF] + NG_RAN_CUC --- Transport_network[Transport network] + UPF --- Transport_network + NG_RAN_CUC --- UNI[UNI] + UNI --- Transport_Network_CNC[Transport Network CNC] + Transport_network <--> Transport_Network_CNC + +``` + +Diagram of the architecture for NG-RAN acting as CUC towards CNC of the N3 transport network. The diagram shows an NG-RAN/CUC connected to a UPF via an N3 tunnel. Both are connected to a Transport network. The NG-RAN/CUC is also connected to a Transport Network CNC via a UNI. The Transport network is connected to the Transport Network CNC via a bidirectional arrow. + +Figure 6.20.2-1: NG-RAN acting as CUC towards CNC of the N3 transport network + +**Editor's note:** The consequence of collocating CUC with a single gNB is FFS. + +The solution is based on the following principles: + +- If NG-RAN receives a QoS Flow description from the SMF, which includes a TSCAI: + - NG-RAN derives a stream identification description based on the NG-RAN and UPF tunnel end point addresses and ports and traffic requirements/characteristics based on the QoS profile, TSCAI information and the CN PDB. +- RAN (acting as a CUC), provides the stream identification/requirements to the transport network CNC. +- If the QoS flow description with TSCAI is removed by the SMF or if the UE context is removed in the RAN (e.g. when the UE enters Idle or when the UE relocates to a different RAN node), then RAN (acting as CUC) removes the previously provided stream identification/requirements from the transport network's CNC. + +NOTE 1: To enable the transport network to distinguish QoS flows, this solution assumes that separate tunnel end-point addresses are used for the N3 tunnels for QoS flows, which include a TSCAI (SMF can instruct RAN and UPF to do so). Use of IPv6 addresses can ensure that sufficient addresses are available. + +NOTE 2: This solution does not assume support of talker/listener functionality to be supported by RAN and UPF. + +NOTE 3: Whether the above needs to be standardized or can be left as an option for RAN implementation can be determined in coordination with RAN WG3. + +### 6.20.3 Procedures + +Existing procedures are reused. + +### 6.20.4 Impacts on services, entities and interfaces + +NG-RAN: + +- For QoS flows for which SMF provides TSCAI, derive a stream identification based on NG-RAN/UPF tunnel end point addresses and ports and traffic requirements/characteristics based on the QoS profile, TSCAI information and the CN PDB. +- Provide stream requirements to transport network CNC. +- Allocate separate tunnel end-point destination addresses per QoS Flow (for QoS flows with TSCAI) used for the N3 tunnels (existing functionality). + +UPF: + +- Allocate separate tunnel end-point destination addresses per QoS Flow (for QoS flows with TSCAI) used for the N3 tunnels (existing functionality). + +SMF: + +- Instruct the NG-RAN and UPF to allocate separate tunnel end-point destination addresses per QoS Flow (for QoS flows with TSCAI) used for the N3 tunnels using existing NGAP and existing N4 signalling. + +## 6.21 Solution #21: BAT adjustment by TSNCF to TSN in the transport network + +### 6.21.1 Introduction + +This solution enables the 5GS to adapt downstream scheduling in order for 5GS to meet really low latency (e.g. 2ms) requirement. This solution also can be used for the UL stream scheduling. + +This solution makes the following assumptions: + +- There is TSN deployed in the transport network. +- This solution builds on the top of solution 11. + +### 6.21.2 Functional Description + +The solution is based on the architecture in Figure 6.11.2-1 of solution 11. + +The solution is based on the following principles: + +- When the NG-RAN receives the TSCAI during QoS flow establishment/modification, it detects there is a need for adjustment to the Burst Arrival Time (i.e. offset to the BAT). +- The NG-RAN indicate the BAT offset to TSNCF/CUC in the response. + +- The TSNCF calculate the Talker/Listener status according to the BAT offset and stream information. The TSNCF uses the procedures described in Solution 11 to communicate with the NG-TT, TNW-TT and CNC. + +NOTE: Whether TSNCF can enforce a negative BAT offset depends on whether the TSN in the transport network can achieve the delay, i.e. CN-PDB – BAT offset + +- After the TSNCF/CUC receives the configuration from CNC, the TSNCF update the TSCAC and send it to SMF. +- The SMF update the TSCAI and send to NG-RAN/UPF. + +### 6.21.3 Procedures + +The procedure in Figure 6.11.3-1 is re-used with following enhancement: + +![Sequence diagram for Figure 6.21.3-1 (Figure 6.11.3-1) showing the interaction between UE, NG RAN/NG-TT, AMF, SMF, UPF/TNW-TT, PCF, TSNCF/CUC, CNC, and NEF/AF. The diagram illustrates the enhanced procedure for TSN configuration, including steps for service requirement, AF session update, SM policy association modify, N4 session request/response, N2 PDU session request/response, and TSNCF/CUC status calculation.](8a94796989f4fcba2688c4faa7991538_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG_RAN as NG RAN/NG-TT + participant AMF + participant SMF + participant UPF as UPF/TNW-TT + participant PCF + participant TSNCF as TSNCF/CUC + participant CNC + participant NEF as NEF/AF + + Note right of NEF: 1. Service requirement + NEF->>CNC: + CNC->>TSNCF: 2. AF session update + TSNCF->>PCF: 3. SM Policy Association modify + PCF->>SMF: 4. N4 Session Request / Response + SMF->>AMF: 5. Namf_Communication_N1N2 Message Transfer + AMF->>NG_RAN: 6. N2 PDU Session Request + NG_RAN->>UE: 7. RRC resource setup + UE->>NG_RAN: 8. N2 PDU Session Response + NG_RAN->>AMF: 9. Nsmf_PDUSession_UpdateSMContext + AMF->>SMF: 10. N4 Session Request / Response + SMF->>PCF: 11. SM Policy Association modify + PCF->>TSNCF: 12. Notify + TSNCF->>CNC: 13. Talker/Listener status + CNC->>TSNCF: 14. AF session update + TSNCF->>PCF: 15. SM Policy Association modify + PCF->>SMF: 16. N4 Session Request / Response + SMF->>AMF: 17. Namf_Communication_N1N2 Message Transfer + AMF->>NG_RAN: 18. N2 PDU Session Request + +``` + +Sequence diagram for Figure 6.21.3-1 (Figure 6.11.3-1) showing the interaction between UE, NG RAN/NG-TT, AMF, SMF, UPF/TNW-TT, PCF, TSNCF/CUC, CNC, and NEF/AF. The diagram illustrates the enhanced procedure for TSN configuration, including steps for service requirement, AF session update, SM policy association modify, N4 session request/response, N2 PDU session request/response, and TSNCF/CUC status calculation. + +Figure 6.21.3-1: (Figure 6.11.3-1) + +8. NG-RAN detect the offset to the BAT is needed. The NG-RAN send the offset and stream information to AMF. + +9-12. The BAT offset is sent to TSNCF. + +13. The TSNCF calculate the Talker/Listener status according to the BAT offset and stream information. + +14-15. TSNCF/CUC receives the configuration from CNC, the TSNCF sends the stream configuration to NG-TT and TNW-TT in the PMIC/UMIC as described in Solution 11 and updates the TSCAC and sends it to SMF with the configuration. + +NOTE: Update the TSCAC is to make TSCAI is align with the stream configuration from TSN CNC in the NG-RAN. + +Editor's note: It is FFS whether updating the TSCAC is necessary because the stream configuration that is sent to NG-TT via PMIC contains the same timing information. + +17-18. The SMF updates the TSCAI. And send the TSCAI and configuration to the NG-RAN. + +### 6.21.4 Impacts on services, entities and interfaces + +In addition to the impacts in sol#11, the following impacts are caused by this solution: + +#### NG-RAN: + +- Determines a BAT offset for UL/DL traffic according to TSCAI. +- Provides the BAT offset values to the TSNCF in a response to the QoS Flow establishment or modification request. + +#### TSNCF: + +- The TSNCF calculate the Talker/Listener status according to the BAT offset and stream information. +- After the TSNCF/CUC receives the configuration from CNC, the TSNCF update the TSCAC and send it to SMF. + +## 6.22 Solution #22: Transmission opportunities exposure + +### 6.22.1 Introduction + +This solution enables the RAN to provide to an AF some details on DL transmission opportunities, so that the AF can adapt its transmissions times to minimise end-to end delays. + +The solution addresses the following scenario: Adapting downstream scheduling based on RAN feedback for low latency communication. + +The solution addresses also the enhancement of transmissions delays in the uplink. + +In TDD transmissions, the frame structure has an impact on transmission delays. Indeed, a DL packet has to wait for a DL part of the frame before being actually transmitted, and similarly an UL packet will have to wait for an UL part in the frame. + +In NR, the TDD frame structure is very flexible, and can be composed of several UL and DL chunks. We call "transmission opportunity" one of this DL or UL chunk. + +The principle of this solution is to provide to an application function information about the transmission opportunities. It is then up to the application to adapt its sending times accordingly to minimise transmission delays. In the case of 5GS integration in a TSN network, this information can be used to minimise the independent delays provided to the CNC. + +### 6.22.2 Functional Description + +The application function is assumed to be able to adapt its sending times. In the case of UL streams, the application client is assumed to be able to adapt its transmission times. This is typically the case when the 5G system is acting as a TSN bridge in a TSN. + +The solution is based on the following principle: + +The AF indicates to the PCF that it is interested in getting transmission opportunities information, directly in the case of a TSN-AF or through NEF/TSCTSF otherwise. + +The transmission opportunities information request is forwarded to RAN by reusing PDU session modification procedure. + +The RAN builds the transmission opportunities information. This information may be composed of: + +- A start of frame reference time. +- A list of offsets for DL opportunities. +- A list of offsets for UL opportunities. + +- A periodicity. + +An example of the mapping between a RAN frame structure and the transmission opportunities information is provided in Figure 6.22.2-1. + +![Figure 6.22.2-1: Example of transmission opportunities information. This diagram shows a sequence of 20 frames, each containing Downlink (DL) and Uplink (UL) slots. The sequence is: DL, DL, DL, UL, UL, DL, DL, DL, DL, UL, DL, DL, DL, UL, UL, DL, DL, DL, DL, UL. The 'Start of Frame' is indicated at the beginning. 'DL Offset 1' is marked at the start of the first DL slot. 'UL Offset 1' is marked at the start of the first UL slot. 'DL Offset 2' is marked at the start of the second DL slot. 'UL Offset 2' is marked at the start of the second UL slot. A bracket labeled 'Periodicity' spans from the start of the first DL slot to the start of the second DL slot.](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +Figure 6.22.2-1: Example of transmission opportunities information. This diagram shows a sequence of 20 frames, each containing Downlink (DL) and Uplink (UL) slots. The sequence is: DL, DL, DL, UL, UL, DL, DL, DL, DL, UL, DL, DL, DL, UL, UL, DL, DL, DL, DL, UL. The 'Start of Frame' is indicated at the beginning. 'DL Offset 1' is marked at the start of the first DL slot. 'UL Offset 1' is marked at the start of the first UL slot. 'DL Offset 2' is marked at the start of the second DL slot. 'UL Offset 2' is marked at the start of the second UL slot. A bracket labeled 'Periodicity' spans from the start of the first DL slot to the start of the second DL slot. + +**Figure 6.22.2-1: Example of transmission opportunities information** + +The RAN forwards the transmission opportunities information to the SMF. + +The SMF translates the reference time from 5G clock to external clock, taking into account CN delay and clock drift. + +SMF sends the translated transmission opportunities information back to the AF via PCF/TSCTSF/NEF or directly via the PCF in the case of TSN-AF. + +**Editor's note:** Clock time difference management has to be clarified. + +### 6.22.3 Procedures + +Figure 6.22.3-1 describe the procedure for this solution. + +![Figure 6.22.3-1: Procedure for transmission opportunities exposure. This sequence diagram shows the interaction between UE, RAN, SMF, PCF, TSN-AF/TSCTSF, NEF, and AF. The procedure consists of three main steps: 1. AF session with requested QoS: The AF sends a Nef_AfSessionWithQoS_Update request [TxOps Info Request] to the NEF, which then sends an Ntsdsf_QoSandTSCAssistance_Create request [TxOps Info Request] to the TSN-AF/TSCTSF. The TSN-AF/TSCTSF sends an Npcf_PolicyAuthorization_Update [TxOps Info Request] to the PCF. 2. PDU session modification: The PCF sends an Npcf_SMPolicyControl_UpdateNotify request TSCAC [TxOps Info Request] to the SMF. The SMF sends a PDU Session Request TSCAI [TxOps Info Request] to the RAN. The RAN performs a 'Get frame format' operation and sends a PDU Session Response [Start, TxOpsDL, TxOpsUL, Periodicity] to the SMF. The SMF performs a '5G clock to external clock translation' and sends an Npcf_SMPolicyControl_Update request [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the PCF. 3. RAN response: The PCF sends an Npcf_PolicyAuthorization_Notify [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the TSN-AF/TSCTSF. The TSN-AF/TSCTSF sends an Ntsdsf_QoSandTSCAssistance_Update [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the NEF, which then sends a Nef_AfSessionWithQoS_Notify [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the AF.](96c8d8b0159c47a7478ada46d781060b_img.jpg) + +Figure 6.22.3-1: Procedure for transmission opportunities exposure. This sequence diagram shows the interaction between UE, RAN, SMF, PCF, TSN-AF/TSCTSF, NEF, and AF. The procedure consists of three main steps: 1. AF session with requested QoS: The AF sends a Nef\_AfSessionWithQoS\_Update request [TxOps Info Request] to the NEF, which then sends an Ntsdsf\_QoSandTSCAssistance\_Create request [TxOps Info Request] to the TSN-AF/TSCTSF. The TSN-AF/TSCTSF sends an Npcf\_PolicyAuthorization\_Update [TxOps Info Request] to the PCF. 2. PDU session modification: The PCF sends an Npcf\_SMPolicyControl\_UpdateNotify request TSCAC [TxOps Info Request] to the SMF. The SMF sends a PDU Session Request TSCAI [TxOps Info Request] to the RAN. The RAN performs a 'Get frame format' operation and sends a PDU Session Response [Start, TxOpsDL, TxOpsUL, Periodicity] to the SMF. The SMF performs a '5G clock to external clock translation' and sends an Npcf\_SMPolicyControl\_Update request [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the PCF. 3. RAN response: The PCF sends an Npcf\_PolicyAuthorization\_Notify [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the TSN-AF/TSCTSF. The TSN-AF/TSCTSF sends an Ntsdsf\_QoSandTSCAssistance\_Update [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the NEF, which then sends a Nef\_AfSessionWithQoS\_Notify [StartExt, TxOpsDL, TxOpsUL, Periodicity] to the AF. + +**Figure 6.22.3-1: Procedure for transmission opportunities exposure** + +1. AF indicates to the PCF a request for getting transmission opportunities information. Signalling AF session with requested QoS procedure (clause 4.15.6.6 in TS 23.502 [3]) is used. + +2. The transmission opportunities information is forwarded to RAN by reusing PDU session modification procedure: + - RAN gets frame format it uses for that PDU session and derives the transmission opportunities parameters. + - SMF translates the start of frame indication from 5G internal clock reference to external clock reference. +3. PCF provides the transmission opportunities information to the AF using the notification procedures. + +In the case of TSN-AF, the transmission opportunities information can be useful for computing the delays to be advertised to the CNC, i.e. the TSN-AF shall have the option of getting the transmission opportunity information before requesting any data flow. In this case, the TSN-AF triggers the transmission opportunities information request in Npcf\_PolicyAuthorization\_Update without including a stream request. + +**Editor's note:** To be checked whether the QoS request procedure is the right procedure to use if the AF does not include a stream request. + +After having received the transmission opportunities information, the AF may trigger another AF session with requested QoS procedure including flow BAT and periodicity that take into account transmission opportunities information. + +### 6.22.4 Impacts on services, entities and interfaces + +AF: + +- Transmission opportunities information request. +- Computing the delays to be advertised to the CNC taking into account transmission opportunities information (TSN-AF). +- Burst sending schedule adaptation according to the received transmission opportunities information. + +SMF: + +- Support of signalling transmission opportunities request / transmission opportunities information. +- Translates the start of frame indication from 5G clock to external clock. + +NG-RAN: + +- Reception of transmission opportunities information request. +- Provides transmission opportunities information. + +PCF/TSCTSF/NEF: + +- Support of signalling transmission opportunities request / transmission opportunities information. + +# --- 7 Evaluation + +## 7.1 Key Issue #3: Support for controlling 5G time synchronization service based on subscription + +There are 2 solutions (Sol#18, Sol#19) for KI#3. The following technical issues are studied: + +1. How to authorize time synchronization service based on UE subscription: + - TSCTSF performs time synchronization service configuration (i.e. ASTI and/or (g)PTP time distribution) based on UE's Time Synchronization Subscription Data. (Sol#18, Sol#19). + - AMF performs time synchronization service configuration for ASTI if the Access Stratum Time Synchronization Service Authorization is available at the UDM and the UE is authorized. (Sol#18). + +- Applicability of time sync subscription for time sync service activation with or without AF request. (Sol#18). + - TSCTSF authorizes time synchronization service request based on UE subscription. (Sol#19). +2. How to enforce time synchronization service on a per UE basis based on subscription: +- TSCTSF performs time synchronization service configuration (i.e. ASTI and/or (g)PTP time distribution) based on UE's Time Synchronization Subscription Data with or without AF request. (Sol#18). + - AMF performs time synchronization service configuration for ASTI if the Access Stratum Time Synchronization Service Authorization is available at the UDM and the UE is authorized. (Sol#18). + - TSCTSF updates the 5G time distribution indication based on UE subscription. (Sol#19). + - TSCTSF subscribes to Time Synchronization Subscription Data at the UDM. (Sol#18, Sol#19). + - TSCTSF determines a suitable 5G timing source to provide time synchronization service for the UE. (Sol#19). +3. What parts of time synchronization service require a separate UE subscription (and authorization), if any: +- UDM stores Time Synchronization Subscription Data and Access Stratum Time Synchronization Service Authorization fields management with or without AF request. (Sol#18). + - UDM stores Subscription data including time synchronization parameters or timing resiliency parameters. (Sol#19). + +## 7.2 Key Issue #5: Interworking with TSN network deployed in the transport network + +There are 4 solutions (Sol#9, Sol#10, Sol#11, Sol#20) for KI#5. The solution #10 has been merged into Solution #9, therefore it is not considered here. The following technical issues are studied: + +- a) The architecture enhancement to support the interworking between 5GS and TSN networks deployed in the transport network. + - NG-RAN/NG-TT and UPF/TNW-TT support LLDP to report the topology to CNC in TSN Transport Network. It supports the container to communicate with TSNCF. TSNCF collects the Talker/Listener stream requirement as specified in IEEE Std 802.1Qcc [6] from NG-TT and TNW-TT via PMIC/UMIC. It provides the Talker/Listener status to CNC and receives the status of stream configuration from CNC. It provides the Talker/Listener configuration status to NG-TT and TNW-TT via PMIC/UMIC. (Sol#11). + - SMF allows information access with the collocated TN CUC to support UNI as described in IEEE P802.1Qdj [10]. SMF determines the traffic requirements for a QoS Flow and initiates that CUC translates them to merged stream requirements which are then passed to the CNC in TSN Transport Network. (Sol#9). + - TSNCF (co-located with TSCCF/TSN AF) act as 5G CUC to support UNI as described in IEEE P802.1Qdj [10]. TSNCF determines the traffic requirements and translates them to merged stream requirements which are then passed to the CNC in TSN Transport Network. (Sol#11). + - NG-RAN and UPF may support Listener/Talker and Stream Transformation as described in IEEE P802.1Qdj [10]. (sol#9 and sol#11) If the Stream Transformation in NG-RAN and UPF is not supported, two options for identifying the traffic on QoS Flow basis in the TN: 1) SMF instructs UPF and RAN to assign a separate CN tunnel end point address for each QFI or 2) the interface between the CUC and CNC in the TN allows the SMF and CUC to indicate the TEID and QFI of the given QoS Flow to the CNC in the TN (Sol#9). + - SMF may transfer received merged end station communication-configuration from the TN CNC to the Talker/Listener accordingly. (Sol#9). + - TSNCF (co-located with TSCCF/TSN AF) may transfer received merged end station communication-configuration from the TN CNC to the Talker/Listener accordingly. (Sol#11). + - NG-RAN and UPF may support the functionality of Listener/Talker as described above. (Sol#9, sol#11). + +- NG-RAN provides stream requirements to transport network CNC, and allocates separate tunnel end-point destination addresses per QoS Flow (for QoS flows with TSCAI) used for the N3 tunnels (existing functionality). (Sol#20). + - SMF instructs the NG-RAN and UPF to allocate separate tunnel end-point destination addresses per QoS Flow (for QoS flows with TSCAI) used for the N3 tunnels using existing NGAP and existing N4 signalling. (Sol#20). + - NG-RAN provides stream identification to transport network CNC. (Sol#20). +- b) What information are needed and how to collect the information from 5GS (e.g. NG-RAN, 5GC NF), so that the 5GS can interact with TSN network. Also, determine which 5GS entity is responsible to provide it to the TSN network deployed in the transport network. +- TSNCF collects the Talker/Listener stream requirement as specified in IEEE Std 802.1Qcc [6] from NG-TT and TNW-TT via PMIC/UMIC. It provides the Talker/Listener status to CNC and receives the status of stream configuration from CNC. It provides the Talker/Listener configuration status to NG-TT and TNW-TT via PMIC/UMIC. (Sol#11). + - SMF allows information access with the collocated CUC to support UNI as described in IEEE P802.1Qdj [10]. SMF determines the traffic requirements for a QoS Flow and initiates that CUC translates them to merged stream requirements which are then passed to the CNC in Transport Network. (Sol#9). + - NG-RAN provides stream requirements to transport network CNC, and allocates separate tunnel end-point destination addresses per QoS Flow (for QoS flows with TSCAI) used for the N3 tunnels (existing functionality). (Sol#20). + - NG-RAN may determine a dynamic value of 5G-AN PDB in UL direction at the gNB egress. The NG-RAN provides the dynamic value of 5G-AN PDB value to the SMF in a response to the QoS Flow establishment or modification request. This is used as more accurate value for AN-PDB when the SMF determines the traffic requirements for a QoS Flow towards the TN CNC (Sol#9). + +## 7.3 Evaluation for KI #6: Adapting downstream scheduling based on RAN feedback for low latency communication + +There are currently 7 solutions in the TR for Key Issue#6: Solution#2, Solution#12, Solution#13, Solution#15, Solution#16, Solution#21 and Solution#22. Solution#16 has been merged with Solution#12, so it is not considered further. Rest of the solutions are summarized below. + +The solutions can be divided into two categories: + +- 1) NG-RAN determines the timing feedback based on the reception time of the packets in user plane (**Solutions 2 and 15**). + +The 5GS notifies the AF for the Burst Arrival Time offset; that is expressed in reference to the actual reception timing of the packets as experienced by the NG-RAN in User Plane; Burst Arrival Time offset can take positive or negative values. The solution#2 is applicable only for traffic in DL direction. Solution #15 is an enhancement of Solution#2 to make it applicable also for traffic in UL direction, but this impacts to the UE. The solutions do not require that the application is time-synchronized with the 5GS, i.e. BAT in TSCAI is optional. + +The solution can only adjust the sending time after the traffic has started. In practice it requires several packets until the application receives the feedback and required latency can be met. + +- 2) 5GS and AF negotiate the Burst Arrival Time in control plane (**Solutions 12, 13, 21, 22**). + +These solutions require that the application is time-synchronized with the 5GS, i.e. BAT in TSCAI is mandatory. + +In Solution#12 the AF provides a "BAT window" to 5GC and to NG-RAN; it consists of earliest and latest arrival time of the traffic. The NG-RAN responds with a "BAT offset" that is relative to the earliest arrival time in the BAT window and is less or equal to the subtract of the latest and earliest arrival times of the BAT window. The BAT offset can be provided separately for UL and DL directions. + +In Solution#21 the feedback from the NG-RAN is only used to indicate the timing of the burst to the Transport Network (via TN CNC), thus the solution requires that integration with TSN in the Transport Network is supported as described in Solution#11 for KI#5. In addition, since the feedback is not sent to the AF, the application cannot adjust the timing based on the feedback, thus the bridges in the Transport Network will buffer the bursts. + +In Solution#13 the NG-RAN provides a Burst Arrival Window (BAW) in absolute time and burst periodicity preference to 5GC (separately for UL and DL). The BAW and periodicity preference are then to be provided to the AF; the AF provides a BAT to the NG-RAN that is within the Burst Arrival Window. + +Solution#22 is similar to Solution#13, but instead of providing Burst Arrival Window and periodicity preference, the NG-RAN provides "transmission opportunities" to the AF, that consists of start of frame reference time, a list of offsets for DL opportunities, a list of offsets for UL opportunities, and periodicity. The AF is then supposed to update the QoS-request accordingly. The solution also contains a procedure for the AF to query the "transmission opportunities" from the NG-RAN, before the AF has invoked the actual QoS-request for a stream. + +# --- 8 Conclusions + +## 8.1 Conclusion for KI #4: AF Request of PER for QoS and Alt-QoS + +It is agreed to adopt Solution #8: "AF Request of PER for QoS and Alt-QoS" for normative work. + +## 8.2 Key Issue #2: Time synchronization service enhancements + +The following bullet points summarize the principles for the way forward: + +- To request a Requested Coverage Area for time synchronization services, AFs within the operator's domain formulates a spatial validity condition using a list of Tracking Area identities, but AFs outside the operator's domain use a geographical area (e.g. a civic address or shapes) instead, while NEF transforms this information into a list of Tracking Area identities. +- The AF provides the Requested Coverage Area for time synchronization services, UE list and time synchronization services (ASTI or (g)PTP based) to TSCTSF, optional via NEF. + +NOTE: The Requested Coverage Area is restricted to TA level granularity. + +- In order to track the UE moving in and out of Time Synchronization coverage area at a TA granularity, the Registration Area (RA) shall only include TAs either inside or outside of the Requested Coverage Area the AF requested for Time Synchronization. This ensures the UE performs Registration update with the network when the UE moves in and out of Requested Coverage Area. +- The TSCTSF need to query with UDM to check whether ASTI or (g)PTP based time synchronization is allowed to be requested by AF for the UE. +- The TSCTSF is responsible of activate/deactivate time synchronization services (ASTI or (g)PTP based) considering the spatial validity condition provided by the AF. +- The TSCTSF discovers the AMF(s) serving the list of TA(s) that comprise the spatial validity condition using the NRF. +- The TSCTSF subscribes to UE's location or UE's presence in Area of Interest at the discovered AMF(s). +- The TSCTSF may optionally provide the Location Reporting Type indication to the AMF when the TSCTSF subscribes to UE's location or presence in AoI. Otherwise, the AMF determines the Location Reporting Type indication. +- The determination of the Location Reporting Type indication and Location Report Level can be based on AoI requested, other location reporting processes the UE may have active with the AMF, and the UE's current RRC state (if known). Alternatively, the UE's presence in the AoI event type may be used unless specified otherwise. + +- The Location Report Level shall be set in accordance with the Requested Coverage Area. +- The TSCTSF determines (based on notifications from the discovered AMF(s)) whether the targeted UE(s) are inside or outside the AF Requested Coverage Area. +- The TSCTSF activates time synchronization services for UE(s) that are inside the Requested Coverage Area. If the AF has requested (g)PTP based time distribution, then TSCTSF creates the PTP port in DS-TT and adds it to the PTP instance as described in clause 4.15.9.3.2 in TS 23.502 [3]. +- TSCTSF notifies the AF with the indication of 5G access stratum time distribution (enabled, disabled) for the targeted UE(s) for which the AF has requested ASTI-based time distribution that are inside or move inside or outside of the Requested Coverage Area. +- If the TSCTSF has determined (e.g. notified) that the UE has moved outside the AF Requested Coverage Area for which the AF has requested (g)PTP based time distribution, then TSCTSF temporarily removes the UE/DS-TT from the PTP instance: + - If the DS-TT is configured to send Sync, Follow\_Up and Announce messages for the related PTP instance, then TSCTSF deactivates the Grandmaster functionality in the DS-TT using PMIC (see also clause K.2.2.4 of TS 23.501 [2]) and removes the DS-TT from the PTP instance (see also clause K.2.2.1 of TS 23.501 [2]). + - If NW-TT is configured to send Sync, Follow\_Up and Announce messages on behalf of the DS-TT, then TSCTSF deactivates the Grandmaster functionality on behalf of the DS-TT in NW-TT using UMIC (see also clause K.2.2.4 of TS 23.501 [2]) and removes the DS-TT from the PTP instance (see also clause K.2.2.1 of TS 23.501 [2]). + - The TSCTSF informs the AF for the impacted UE by indicating the PTP port state as Inactive for the related DS-TT PTP port. +- If TSCTSF has determined (e.g. notified) that the UE has moved inside the AF Requested Coverage Area for which the AF has requested (g)PTP based time distribution, then TSCTSF adds the DS-TT PTP port to the PTP instance and also (re-)activates the Grandmaster functionality. The TSCTSF informs the AF for the impacted UE by indicating the PTP port state as Active for the related DS-TT PTP port. +- If the TSCTSF has determined (e.g. notified) that the UE has moved outside the AF Requested Coverage Area for which the AF has requested ASTI based time distribution, then TSCTSF temporarily deactivate ASTI time synchronization service by disabling the indication of 5G access stratum time distribution for the targeted UE(s). +- If TSCTSF has determined (e.g. notified) that the UE has moved inside the AF Requested Coverage Area for which the AF has requested ASTI based time distribution, then TSCTSF enables the indication of 5G access stratum time distribution for the targeted UE(s) based on the AF-requested requirement of time synchronization service. + +## 8.3 Conclusion for KI #5: Interworking with TSN network deployed in the transport network + +The following bullet is the interim conclusion for KI#5: + +- There is 5G CUC to interact with TN CNC on exchanging Talker/Listener or Status Groups information. The 5G CUC is collocated with the SMF(s). +- The 5G CUC will map the QoS Flow related parameters into Talker/Listener Group in IEEE 802.1Qcc [6]. The detailed handling of the parameters in Talker/Listener or Status Groups information is described in clause 6.9.2. +- The RAN and UPF may support the functionality of Listener/Talker for the following: + - hold and buffer functionality in a case when the TSCAI contains a BAT in UL and/or DL direction. In this case the TimeAwareOffset is sent to the Talker in RAN/UPF in a Transparent Container, and the Talker in RAN/UPF must buffer the data burst until the time indicated in the TimeAwareOffset is reached. + - for support of stream transformation, the Talker/Listener does not provide the DataFrameSpecification. In this case the 5G CUC transfers the InterfaceConfiguration received from the TN CNC to Talker in a + +Transparent Container, and the Talker in RAN/UPF must use the indicated MAC address, VLAN ID or IP-tuples for the data stream. + +- for 5G CUC to retrieve the InterfaceCapabilities and/or EndStationInterfaces from the Talker/Listener via Transparent Container. Otherwise, this information must be preconfigured or determined by 5G CUC. +- NG-RAN and UPF may support u-plane LLDP functionality. When LLDP is supported, the u-plane is performing the LLDP functionality without the need for c-plane interaction with CNC of the transport network for the purpose of LLDP as specified in clause 6.11.2. +- It is assumed that RAN, 5GC and Transport Network are time synchronized with each other in 5G internal system clock. + +## 8.4 Key issue #6: Adapting downstream scheduling based on RAN feedback for low latency communication + +The following bullet points summarize the principles for the way forward: + +- Proactive feedback requires that 5GS and the AF receive time information from the same master clock. Since this assumption cannot hold in all deployments, both pro-active and reactive feedback mode shall be supported. The feedback is in order to align the burst arrive time and the next transmission opportunity on the respective direction (i.e. both UL and DL) of the traffic to reduce the potential buffering delay. +- When the AF gets the feedback for BAT (in both modes), the AF adjusts the burst sending time accordingly. +- When the AF gets the periodicity feedback (in proactive mode), the AF adjusts the periodicity accordingly. + +NOTE 1: For both UL and DL direction, the AF adjusts the burst sending time and periodicity by using application layer mechanism, e.g. to notify the application in device side. + +- The AF provides adaptation capability information of the application to 5GS as described below. + +Principles for Proactive feedback for BAT: + +- The AF may indicate its capability for BAT window along with the BAT as specified in Rel-17. If the PCF receives a policy authorization request from the AF/NEF/TSCTSF that indicates that capability or a BAT window: +- the PCF sets a trigger to be notified for the "BAT offset" event for the corresponding PCC Rule via the SM policy control service to the SMF. +- If the SMF receives an indication for a BAT adaptation capability or a BAT window, in a TSCAC, the SMF includes that indication or a BAT window into TSCAI along with the QoS Flow establishment request. This indicates to the NG-RAN that the NG-RAN may provide a BAT offset in an N2 SM information as a response to the SMF. +- As a response to the QoS Flow establishment request, the NG-RAN may provide a "BAT offset" that is within the BAT window, if available, value. The BAT offset is provided from NG-RAN to SMF, eventually forwarded via PCF/TSCTSF/NEF to AF. +- If the AF does not receive the BAT offset (e.g. NG-RAN did not provide it), the AF assumes that the 5GS does not support BAT adaptation and the initial BAT value is used as a Burst Arrival Time in 5GS. +- The SMF configures the UPF for clock drifting reports as specified in TS 23.502 [3]. In a case the SMF receives a clock drifting report from UPF, if the SMF has received a BAT offset from the RAN, the SMF adjusts the BAT offset based on the existing procedures in TS 23.502 [3] and provides the updated BAT offset to the AF via PCF/TSCTSF/NEF. + +Principles for Proactive feedback for Periodicity: + +- The AF may also indicate its capability for Periodicity Range in the AF Request along with the Periodicity as specified in Rel-17, together with the parameter for BAT adaptation mentioned above: + +- The RAN may provide a periodicity feedback together with a BAT offset mentioned above. The periodicity feedback shall be within the Periodicity Range (if available). +- If the RAN provides feedback with proposed periodicity value and a BAT offset, the BAT offset is accepted based on the proposed periodicity. +- If the RAN provides BAT offset and no proposed periodicity, the Periodicity as specified in Rel-17 is accepted and the BAT offset is processed as described for the proactive feedback for BAT. +- The AF may attempt to update the Periodicity and/or BAT using the same procedure as described for initial proactive feedback. +- If the interworking with TSN network deployed in the transport network is supported, the SMF/CUC uses the accepted periodicity and BAT offset to derive the Talker/Listener Group in IEEE 802.1Qcc [6] as described in clause 8.3. + +Principles for Reactive feedback: + +- The AF may request the 5GS to report the BAT offset; that is a time offset to the observed timing of the packet reception in the user plane in the NG-RAN. In this case the AF subscribes for the QoS notifications as described in the QoS notification control procedure in TS 23.501 [2] and includes an indication of "burst arrival time adaptation" in the QoS-request to the 5GC. +- If the PCF receives indication for "burst arrival time adaptation" along a subscription for QoS notifications in policy authorization request from AF/NEF/TSCTSF, the PCF sets the QoS notification control parameter as described in TS 23.501 [2] and in addition sets a trigger to be notified for the "BAT offset" event for the corresponding PCC Rule via the SM policy control service to the SMF. The SMF provides the notification control parameter to the NG-RAN as described in TS 23.501, and in addition includes the indication of "burst arrival time adaptation" to the QoS profile. +- If the Notification control is enabled and indication of "burst arrival time adaptation" is set in the TSCAI, and the NG-RAN determines that the PDB can no longer be guaranteed for a QoS Flow, the NG-RAN notifies the SMF as described in TS 23.501 [2] and in addition may include a BAT offset to the N2 SM information that is sent to SMF, eventually forwarded via PCF/TSCTSF/NEF to AF. +- If the NG-RAN receives the indication for "burst arrival time adaptation", the NG-RAN indicates the parameter to the UE via RRC signalling. The NG-RAN indicates a threshold for the BAT offset reports to the UE. +- If the UE receives the indication for "burst arrival time adaptation" from NG-RAN, the UE determines a relative BAT offset value in reference to the current Burst Arrival Time experienced by UE (i.e. in reference to when UE currently receives bursts) and the scheduling UL time slot at UE (e.g. in Configured Grants, as defined in TS 38.321 [11]). The UE sends the BAT offset to RAN when the time offset value reaches the configured threshold, and NG-RAN sends the BAT offset value to SMF. + +NOTE 2: Whether the UE provides the BAT offset to the RAN or RAN can determine the BAT offset based on other information provided by the UE will be determined by RAN WG2. Need for "burst arrival time adaptation" indication to the UE depends on the RAN WG2 conclusion. + +## 8.5 Conclusion for KI #1: 5GS network timing synchronization status and reporting + +The following bullet points summarize the principles for the way forward: + +- Detecting and reporting RAN and UPF timing synchronization status to TSCTSF. +- NG-RAN and UPF/NW-TT can detect timing synchronization degradation/failure/improvement locally. + +NOTE 1: The detection is performed based on information provided by time synchronization protocols used in the transport network for both RAN and UPF, or, in the case of NG-RAN, using information provided by a local GNSS receiver. However, in any case, the details on how exactly NG-RAN/UPF detects timing synchronization degradation/failure/improvement locally are beyond the scope of 3GPP. + +Two options are defined for the TSCTSF to detect the timing synchronization status information of RAN and UPF/NW-TT: + +- 1) TSCTSF may receive network timing synchronization status information of RAN and UPF/NW-TT directly from OAM. +- 2) Alternatively, TSCTSF may receive network timing synchronization status information of RAN and UPF/NW-TT using control plane signalling at node level: + - For UPF/NW-TT case the TSCTSF may use UMIC. + - For NG-RAN case the TSCTSF may obtain NG-RAN network timing synchronization status information via the AMF (i.e. AMF uses NGAP signalling to configure the NG-RAN reporting). + +The network timing synchronization status information from RAN or UPF/NW-TT can contain the following parameters: node's synchronization state, node's synchronization performance, primary source description, and primary source event. + +- UE determining that the RAN clock quality information changed using: + - SIB broadcast information to enable UEs in RRC\_IDLE and RRC\_INACTIVE and in the case of RRC\_CONNECTED UEs, dedicated RRC signalling, to enable UEs to determine that: + - the timing synchronization status of the cell that the UE is camping on has changed; + - the timing synchronization status of the new cell the UE is camping on after cell reselection is different compared to the timing synchronization status of the cell that the UE was previously camping on. + - If the UE has determined that the RAN clock quality information has changed and the UE has been requested by the TSCTSF to connect to the network in the case that the RAN clock quality information changes, the UE performs a registration (if the UE is in RRC\_IDLE) or the UE Triggered Connection Resume in RRC Inactive procedure (if the UE is in RRC\_INACTIVE). +- Informing UEs in RRC\_Inactive/Idle state about a change of the RAN clock quality information: + - The gNB includes in SIB9 a reference report ID as a notification for the UEs reading the SIB9 that there is new clock quality information available. The UE compares the reference report ID with locally stored reference report ID to determine if it had retrieved the last available clock quality information already. + - The reference report ID consists of the scope of the report ID and an Event ID (an integer). Scope may either identify a group of cells within a single gNB or a group of cells across gNBs. The latter would reduce the amount of signalling even further since then UEs that move to another gNB would not need to retrieve the clock quality details. + +NOTE 2: RAN WGs are expected to decide whether to support both scopes (group of cells per gNB or across gNBs). + +NOTE 3: It is not required that the UE always transitions to RRC\_CONNECTED immediately to retrieve the latest available clock quality information. In order to reduce RACH access from many UE(s) (to move back to RRC\_CONNECTED state) at the same time, the following option has been considered pending RAN WG2 feedback: + +- The RAN may require that the UE(s) randomize re-connecting back to the network, i.e. to spread the UEs' connection attempts in the time domain, e.g. over the course of one minute. It is up to RAN WG2 to determine how this is achieved. +- Providing RAN's latest clock quality information to the UE in RRC\_Connected state: + - If a UE is subscribed for Access Stratum Time Synchronization (ASTI) in the UDM (see clause 8.6), then the "Access and Mobility Subscription data" may additionally contain the following clock quality reporting control information: + - Clock quality detail level: 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; + - Clock quality acceptance criteria for the UE (if the clock quality level equals "acceptable/not acceptable indication": the clock quality acceptance criteria for the UE. Acceptance criteria can be defined based on + +the following attributes: time source, traceability to UTC or GNSS, synchronization state, clock accuracy, PTP clockClass, frequency stability. (e.g. acceptable clock accuracy, acceptable frequency stability, etc.). + +NOTE 4: Attributes that can be used for clock quality acceptance criteria depends on RAN capabilities to provide them and pending RAN WGs feedback. Whether PTP clockClass can be used will be determined during the normative phase. + +NOTE 5: Whether and which clock quality information to provide to the UE depends on the needs of the time service consumer (referred to as client network operator hereafter). Therefore, the clock quality detail level and clock quality acceptance criteria are based on the parameters and their values specified in the agreement between the 5G network operator and the client network operator. The clock quality acceptance criteria refer to the quality with which 5G access stratum time needs to be delivered to and received by the UE (i.e. also considering propagation delays). Additional inaccuracies in the UE, e.g. if the 5G access stratum time is delivered to devices attached to the UE, are not included in the clock quality acceptance criteria because they are assumed to be budgeted by the client network operator when agreeing the required clock accuracy with the 5G network operator. + +- If an AF requests Access Stratum Time Synchronization (ASTI) for a UE, then the AF may provide clock quality reporting control information and service acceptance criteria (defined based on the following attributes: time source, traceability to UTC or GNSS, synchronization state, clock accuracy, clockClass, frequency stability, see NOTE 4) to TSCTSF. TSCTSF provides the clock quality reporting control information to AMF. +- When AMF provides the 5G access stratum time distribution indication and the Uu time synchronization error budget to NG-RAN, AMF also includes the clock quality reporting control information. +- Based on the clock quality reporting control information received from AMF, RAN reports its timing synchronization status to the UE using unicast RRC: + - If clock quality detail level is set to "clock quality metrics", then the RAN provides clock quality metrics to the UE that reflect its current timing synchronization status. Clock quality metrics refers to the following information: clock accuracy, PTP clockClass, traceability to UTC, frequency stability, time source, synchronization state. + - If clock quality detail level is set to "acceptable/not acceptable indication", then the RAN provides an acceptable indication to the UE if the RAN's timing synchronization status matches the acceptance criteria received from AMF; otherwise RAN indicates "not acceptable" to the UE. + - When determining the clock quality metrics for a UE and when determining whether clock quality is acceptable or not acceptable for a UE, RAN considers whether propagation delay compensation is performed. + +NOTE 6: Clock quality metrics and the acceptable/not acceptable indication refer to the quality with which 5G access stratum time is delivered to and received by the UE (i.e. also considering propagation delays). In addition, the UE can, for example, update clock quality metrics to reflect internal inaccuracies in the UE before providing the clock quality metrics to devices connected to the UE. + +- Determining UEs impacted by RAN timing synchronization status degradation/improvement: + - TSCTSF subscribes to receive notifications for UE presence in Area of Interest information (Area of Interest is set to a list of RAN node IDs that have the same RAN timing synchronization status) from AMF for UEs that AF requested time synchronization for or which are configured for (g)PTP-based or ASTI-based time synchronization based on subscription. + - When activating time synchronization for a UE, TSCTSF requests the UE to connect to the network via AMF (i.e. to perform a registration if the UE is in RRC\_IDLE or the UE Triggered Connection Resume in RRC Inactive (if the UE is in RRC\_INACTIVE) in the case when the UE later detects that the RAN timing synchronization status has changed while the UE is in RRC\_IDLE or RRC\_INACTIVE). + - TSCTSF correlates information about impacted RAN nodes and the UE location information received from AMF to determine the UEs impacted by RAN timing status degradation/failure/improvement. + +NOTE 7: How to determine the impacted UE will continue to be discussed during the normative phase. + +- Determining UEs impacted by UPF timing synchronization status degradation or improvement (only for the case when UPF/NW-TT is involved in providing time information to DS-TT): + - TSCTSF determines the UEs for which an impacted UPF/NW-TT is configured to send (g)PTP messages. +- Informing AFs about network timing synchronization status degradation or improvement: + - If TSCTSF has determined UEs impacted by RAN or UPF timing synchronization status degradation or improvement or failure then TSCTSF informs the AF about the timing synchronization status for those UEs if the AF was the requester of the time synchronization service. + - The AF may subscribe to time synchronization service status for a UE (or group of UEs) for which the AF requests or has requested time synchronization service (for ASTI or (g)PTP services). + - For the subscribed AFs the TSCTSF provides time synchronization service status. +- The TSCTSF may perform the following: + - For AFs that requested ASTI service, the TSCTSF may indicate whether it can support the ASTI service or not as per the requested criteria. + - For AFs that requested PTP service, the TSCTSF may indicate whether it can support the PTP service or not as per the requested criteria. + - For AFs that subscribe for ASTI/PTP service status update (i.e. change in support status), the TSCTSF may provide notification towards the AF when there is a change in support status. +- Deactivating/reactivating/updating time synchronization services based on RAN/UPF timing synchronization status changes: + - PTP case: For UEs that are part of a PTP instance and which are impacted by RAN or UPF time synchronization status degradation or improvement: + - If TSCTSF determines that the Time synchronization error budget provided by AF can still be met, then TSCTSF may update the clockQuality 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 TS 23.501 [2]. + - If TSCTSF determines that the Time synchronization error budget provided by AF cannot be met (see above) then TSCTSF informs the AF about the intention to temporarily remove the UE/DS-TT from the PTP instance and performs the action using existing procedures in clause K.2.2.1 and clause K.2.2.4 of TS 23.501 [2]) after receiving the confirmation. If the AF declines the intention, the TSCTSF keeps the service active. + - If TSCTSF determines that the Time synchronization error budget provided by AF can be met again then TSCTSF adds the DS-TT PTP port to the PTP instance again and also re-activates the Grandmaster functionality. + - ASTI case: the TSCTSF determines if the acceptance criteria can be met or not and notifies the result to the AF. Based on the notification, the AF decides to modify the ASTI service if preferred (e.g. disable the service upon degradation or enable it again upon recovery). + +## 8.6 Conclusion for KI#3: Support for controlling 5G time synchronization service based on subscription + +The following principles summarize the solution baseline: + +- UE subscription data types stored in the UDM are extended to include two new data structures related to time synchronization service: + - 1) The "Access and Mobility Subscription data" is extended with the following fields: + - "Access Stratum Time Synchronization Service Authorization" which indicate whether the UE is provisioned to receive RTT reception. + +- (Optionally) the Uu time synchronization error budget. + - (Optionally) One or more periods of Start and stop times defining active times of Access Stratum Time Synchronization Service for the UE. + - (Optionally) Coverage Area: defining a list of TAs where the ASTI-based time synchronization is available for the UE. . +- 2) A new subscription data "Time Synchronization Subscription data": +- the "AF request Authorization", indicating whether the UE is authorized for an AF-requested time synchronization services: + - "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). + - optionally Coverage Area defining a list of TA(s) which restricts the area in which an AF may request time synchronization services (for ASTI or PTP services). + - 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, Coverage Area defining a list of TAs where the (g)PTP-based time synchronization is available for the UEs in the PTP instance. + - (Optionally) Uu time synchronization error budget. +- The AMF uses the "Access and Mobility Subscription data" in the following way: +- The AMF retrieves the "Access and Mobility Subscription data" stored at the UDM during the registration procedure. + - If the AMF receives Access Stratum Time Synchronization Service Authorization from UDM, it provides 5G access stratum time distribution indication and Uu time synchronization error budget (if part of the Access Stratum Time Synchronization Service Authorization received from the UDM) to NG-RAN. + - The AF is not allowed to modify the 5GS access stratum time distribution parameters if "Access Stratum Time Synchronization Service Authorization" indicates that the UE is provisioned to receive RTT reception. This may be enforced by the AMF. +- NOTE: If there is "Access Stratum Time Synchronization Service Authorization" in the "Access and Mobility Subscription data", the "AF request Authorization" for ASTI based in the "Time Synchronization Subscription data" should be set to "not allowed". +- If the Access Stratum Time Synchronization Service Authorization contains Start and stop times, 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. If the UE is in CM\_Idle when a Start time condition is met, 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 response to the paging. + - If the Access Stratum Time Synchronization Service Authorization contains Coverage Area, the AMF enables and disables the 5G access stratum time distribution indication to the NG-RAN when the UE moves inside or outside of the Coverage Area, respectively. +- The TSCTSF uses the Time Synchronization Subscription data in the following way: +- 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 Subscription data, the TSCTSF determines whether the UE is authorized for an + +AF-requested time synchronization service. If the UE is authorized, the TSCTSF proceeds as specified in TS 23.502 [3]. + +- The TSCTSF retrieves the Time Synchronization Subscription data from the UDM when the TSCTSF 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 of TS 23.501 [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 of TS 23.501 [2]. +- 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 Coverage Area, the TSCTSF subscribes to UE's presence in Area of Interest at the discovered AMF(s) in similar manner as concluded for KI#2. When the TSCTSF determines that the UE has moved inside or outside of the Coverage Area, the TSCTSF adds or temporarily removes the PTP port in DS-TT from the corresponding PTP instance, in similar manner as concluded for KI#2. + +# --- Annex A: KI#1 related additional analysis + +## A.1 Methods to notify RAN Time Synchronization Status towards the UE + +### A.1.1 Alternative 1: gNB provides a reference report ID within SIB + +In this alternative when there is a new RAN timing synchronization status report available at the gNB, the gNB includes in the SIB a status report ID as a notification for the UEs reading the SIB. The report ID can be an optional integer information element. This report ID enables the UE to know there is new information available at the NG-RAN that is not available locally at the UE. There are two options for the UE to determine RAN timing synchronization status information with the report ID: + +- a) The UE can actively retrieve the RAN timing synchronization status information from the network by entering RRC\_Connected. In order to determine if a report ID is associated to a new report, the UE uses status report ID and the SIB information to identify the serving gNB in the cell. For report ID composition, the report ID is constructed from a pre-agreed (known values at the UE and network side) set of values. The report ID is constructed from a cell group ID and event ID elements: + - Cell group ID is an integer allocated by the gNB that identifies a group of cells controlled by the same gNB. + - Event ID is an integer value. +- b) Report ID is an index that maps to a pre-defined and/or standardized time synchronization characteristics thus the UE can automatically determine this without having to move to RRC\_CONNECTED state. The report ID is composed by one integer which values are standardized or operator defined that are known at the UE and the NG-RAN node. + +To limit the possible permutations of report IDs, in addition to the report ID mapping to time synchronization characteristics, the UEs or AFs may receive additional time synchronization characteristics via SLA or dedicated signalling. The decision depends on the time synchronization characteristics that should be considered. For example, the following parameters can be considered: Lock state, Parent Time Source, Clock class, Clock stability, Clock identifier, Physical layer frequency availability, Holdover specification + +An overall procedure for SIB including a reference report ID is illustrated in Figure A.1.1-1. + +![Sequence diagram illustrating the procedure for gNB provisioning status report ID in SIB. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, and TSCTSF. It starts with a note that the UE has already access stratum time distribution configured and the RAN releases the UE. The sequence includes: 1. SIB9 (RTI) from NG-RAN to UE; 2. Primary source event at NG-RAN; 3. gNB generates RAN timing synchronization status report and report ID at NG-RAN; 4. SIB (RTI, status report ID) from NG-RAN to UE; 5. SIB (RTI, status report ID) from NG-RAN to UE; 6. UE reads status report ID; 7. UE enters RRC_CONNECTED state (For alternative a); 8. gNB realizes the UE is subscribed to RAN timing synchronization status at NG-RAN; 9. DLInformationTransfer (RTI, RAN timing synchronization status report, status report ID) from NG-RAN to UE; 10. For alternative b) the UE uses the report ID as an index to determine the RAN timing synchronization status information at UE.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant UE/DS-TT + participant NG-RAN + participant AMF + participant TSCTSF + + Note right of TSCTSF: UE has already access stratum time distribution configured. +The RAN releases the UE. + + NG-RAN->>UE/DS-TT: 1. SIB9 (RTI) + Note right of NG-RAN: 2. Primary source event + Note right of NG-RAN: 3. gNB generates RAN timing synchronization status report and report ID + NG-RAN->>UE/DS-TT: 4. SIB (RTI, status report ID) + NG-RAN->>UE/DS-TT: 5. SIB (RTI, status report ID) + Note left of UE/DS-TT: 6. UE reads status report ID + + alt For alternative a) + Note right of UE/DS-TT: 7. UE enters RRC_CONNECTED state + Note right of NG-RAN: 8. gNB realizes the UE is subscribed to RAN timing synchronization status + NG-RAN->>UE/DS-TT: 9. DLInformationTransfer (RTI, RAN timing synchronization status report, status report ID) + end + + Note left of UE/DS-TT: 10. For alternative b) the UE uses the report ID as an index to determine the RAN timing synchronization status information + +``` + +Sequence diagram illustrating the procedure for gNB provisioning status report ID in SIB. The diagram shows interactions between UE/DS-TT, NG-RAN, AMF, and TSCTSF. It starts with a note that the UE has already access stratum time distribution configured and the RAN releases the UE. The sequence includes: 1. SIB9 (RTI) from NG-RAN to UE; 2. Primary source event at NG-RAN; 3. gNB generates RAN timing synchronization status report and report ID at NG-RAN; 4. SIB (RTI, status report ID) from NG-RAN to UE; 5. SIB (RTI, status report ID) from NG-RAN to UE; 6. UE reads status report ID; 7. UE enters RRC\_CONNECTED state (For alternative a); 8. gNB realizes the UE is subscribed to RAN timing synchronization status at NG-RAN; 9. DLInformationTransfer (RTI, RAN timing synchronization status report, status report ID) from NG-RAN to UE; 10. For alternative b) the UE uses the report ID as an index to determine the RAN timing synchronization status information at UE. + +**Figure A.1.1-1: Procedure for gNB provisioning status report ID in SIB** + +1. The UE has received reference time information using unicast RRC or via SIB9. The RAN releases the UE to RRC Inactive or RRC Idle state. +2. The NG-RAN node detects a primary source event (e.g. degradation, failure, recovery). +3. The NG-RAN generates a RAN timing synchronization status report and an associated status report ID. +- 4-5. The NG-RAN node broadcasts a status report ID in the cell using SIB to notify the primary source event to the UEs camping in the cell. +6. The UE reads SIB and the status report ID and: + - Alternative a), if the UE does not have stored locally the RAN timing synchronization status report corresponding to the status report ID, the UE retrieves a new RAN timing synchronization status report corresponding to the status report ID the NG-RAN Otherwise, the UE uses the locally stored RAN timing synchronization status report and steps 7-9 are skipped; or + +- Alternative b), the UE uses the status report ID as an index to map to the pre-defined and/or standardized characteristics. Steps 7-9 are skipped. +- 7. In the case of alternative a), the UE enters RRC\_CONNECTED. +- 8. In the case of alternative a) after UE moves to RRC\_CONNECTED mode, the NG-RAN determines the UE is subscribed to RAN timing synchronization status (e.g. based on configuration provided by the TSCTSF via AMF). +- 9. In the case of alternative a) the NG-RAN node sends the last available RAN timing synchronization status report with its associated status report ID to the UE via dedicated RRC signalling. The UE may store the RAN timing synchronization status report with the corresponding status report ID locally for a configured time or until deregistration, and thus avoid the need to reconnect with the network. +- 10. In the case of alternative b) the UE uses the report ID as an index to map to the pre-defined and/or standardized characteristics that describe the RAN timing synchronization status. + +### A.1.2 Alternative 2: + +This alternative covers a case when a time synchronization status needs to be reported to UEs in RRC\_IDLE and RRC\_Inactive states where applications need such information. For this purpose, it is proposed to use a SIB9 message to transmit a flag and a timestamp so that UEs in RRC\_IDLE and RRC\_Inactive state get information/trigger about a new time synchronization status report available. Then, UEs, providing a specific time synchronization service, need now to move to RRC\_CONNECTED state so that the report could be delivered to them via dedicated RRC signalling. An overall procedure shall include at least the following steps: + +- 0. The UE has a time synchronization service configured. During the ongoing service, the UE moves to RRC\_IDLE or RRC\_Inactive state (which could happen due to different reasons). While the UEs in RRC\_IDLE or and RRC\_Inactive state, the NG-RAN detects an event related to a primary time source (e.g. degradation, improvement, failure, etc.). This event triggers a time synchronization status report, and now this report needs to be sent from the NG-RAN node to the UE. +- 1. A new field, acting as a flag, is included in SIB9 to indicate to UEs in RRC\_IDLE state that a time synchronization status report is available. Consequently, the UEs need to move to RRC\_CONNECTED state to receive the report, if it has an ongoing time synchronization service. + +In addition to a flag, another field (e.g. flagSetTimeUTC) is included in SIB9 to reflect a time (actual timeInfoUTC value) when the flag was set/changed, which is required so that UEs are aware which report the flag is referring to since every report can be linked to unique time. + +NOTE: UEs supporting the feature and when the time sync service is active (e.g. configured by upper layers) in the UE, such UE will be mandated to ensure that they always have a valid version of SIB9 stored, which is required for this reporting procedure to work. Otherwise, UEs are not mandated to re-acquire a SIB9 message unless a SI update notification is received, i.e. no new requirements on UEs with respect to SIB acquisition are pursued. + +The flag and flagSetTimeUTC fields (this two information may be reflected by one field) shall be updated by the NG-RAN node only when there is a change in a time synchronization status. + +- 2. If there is a new report, NG-RAN updates SIB9. The UEs re-acquires SIB9 and reads the flag and flagSetTimeUTC fields in the received SIB9 message. Based on the information in these fields, the UE determines whether there is a new time synchronization report available at the NG-RAN. +- 3. If the UE determines there is a new time synchronization status report available, the UE initiates the relevant legacy procedure to enter the RRC\_CONNECTED state. The procedure of RRC state transition is not affected. +- 4. After completing the transition to RRC\_CONNECTED state, the NG-RAN determines (based on the information provided by the AMF via the TSCTSF)) that the latest time synchronization status report needs to be sent to this UE. + +Steps at RRC\_CONNECTED state is common to all variants. + +5. The NG-RAN sends the latest time synchronization status report to the UE via dedicated RRC signalling. If a time synchronization status changes and a new report is available after the UE has gone to RRC\_IDLE or RRC\_Inactive state again, then the process with an update of the flag and the flagSetTimeUTC fields repeats. + +### A.1.3 Alternative 3: Broadcast the time change status in SIB + +This alternative is related to the conclusion for KI#1 on: + +- the NG-RAN informs UEs that receive 5G access stratum time about the time synchronization status by providing additional time synchronization status information (e.g. synchronization state, primary source description (e.g. type, quality, lock state), clock class and information about traceability to UTC, clock accuracy and stability) to UEs + +The idea of this alternative is to provide RAN Time Synchronization Status in SIB. According to the status information, the UE know the time status has be changed. In this alternative, there is no inter-RAN node cooperation. + +The ReferenceTimeinfo (RTI) is extended with: + +- Time quality (e.g. quality, clock class) +- Latest time status change time +- Time source + +NOTE: The detail of time quality will depend on the ITU-T feedback. + +#### A.1.3.1 Procedures + +##### A.1.3.1.1 Broadcast the time change status + +![Sequence diagram showing the procedure for broadcasting RAN Time Synchronization Status. The diagram involves three entities: UE, NG-RAN, and AMF/TSCTSF. The sequence of messages is: 1. The TSCTSF has requested the ASTI for the UE (from AMF/TSCTSF to NG-RAN); 2. RTI over SIB9/dedicated RRC (from NG-RAN to UE); 3. Primary time source Event (internal event in NG-RAN); 4. enhanced RTI over SIB9/dedicated RRC (from NG-RAN to UE).](605625ddfc3363a6205ab0d43b184eaf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF/TSCTSF + Note right of AMF/TSCTSF: 1. The TSCTSF has requested the ASTI for the UE + NG-RAN->>UE: 2. RTI over SIB9/dedicated RRC + Note right of NG-RAN: 3. Primary time source Event + NG-RAN->>UE: 4. enhanced RTI over SIB9/dedicated RRC + +``` + +Sequence diagram showing the procedure for broadcasting RAN Time Synchronization Status. The diagram involves three entities: UE, NG-RAN, and AMF/TSCTSF. The sequence of messages is: 1. The TSCTSF has requested the ASTI for the UE (from AMF/TSCTSF to NG-RAN); 2. RTI over SIB9/dedicated RRC (from NG-RAN to UE); 3. Primary time source Event (internal event in NG-RAN); 4. enhanced RTI over SIB9/dedicated RRC (from NG-RAN to UE). + +**Figure A.1.3.1.1-1: Broadcasting RAN Time Synchronization Status** + +1. The AF has requested 5G access stratum time distribution for the UE and NG-RAN know it need to notify the time status to UE if there is primary time source event (e.g. changed, degradation, etc.). + +NOTE 1: This step can be optional or depend on the existing solution in this TR. + +2. The NG-RAN provides the referencetimeinfo to UE via SIB9 or dedicated RRC: +3. There is a primary time source event that occurs (e.g. degradation, switch, failure, recovery). +4. The NG-RAN provides the enhanced referencetimeinfo to UE via SIB9 or dedicated RRC. According to the Latest time status change time in the RTI, the UE know whether this is primary time source event occurs. + +NOTE 2: The UE may store the RAN id and Latest time status change time to make the comparison. This is up to UE implementation. + +### A.1.4 Alternative 4: Ciphered RAN Time Synchronization Status in SIB + +Key idea of this alternative is to provide RAN Time Synchronization Status in SIB. RAN Time Synchronization Status may optionally be ciphered. Ciphering keys are only provided to UEs, which are subscribed for time synchronization or for which an AF has successfully requested time synchronization. + +Ciphering RAN Time Synchronization Status in SIB ensures that RAN Time Synchronization Status can only be read by UEs that are privy to this information. + +To enable ciphering of the RAN Time Synchronization Status, TSCTSF obtains the RAN Time Synchronization Status from NG-RAN nodes and provides the ciphered RAN Time Synchronization Status to NG-RAN nodes via AMF (see clause A.1.4.1 for details). + +NOTE: Details of how to obtain RAN Time Synchronization Status are discussed in the solutions documented in clause 6 of this TR. + +This means that the same ciphered RAN Time Synchronization Status information is provided to all UEs that have received the ciphering keys. + +This alternative is based on the existing solution for Broadcast of Assistance Data for location services (see clause 6.14 of TS 23.273 [16] and clause 7 of TS 37.355 [17] for details on Broadcast of Assistance Data). + +Editor's note: Feasibility of this solution depends on feedback from RAN WG2/WG3 and SA WG3. + +#### A.1.4.1 Procedures + +##### A.1.4.1.1 Broadcast of RAN Time Synchronization Status + +![Sequence diagram showing the broadcast of RAN Time Synchronization Status. The diagram involves four entities: UE, NG-RAN, AMF, and TSCTSF. The sequence of messages is: 1. TSCTSF obtains RAN time synchronization status from NG-RAN; 2. TSCTSF optionally ciphers the RAN time synchronization status (shown in a dashed box); 3. TSCTSF sends a Namf_Communication_NonUeN2MessageTransfer (RAN time synchronization status) to AMF; 4. AMF sends an N2 Transport (RAN time synchronization status) to NG-RAN; 5. NG-RAN broadcasts the message (RAN time synchronization status) to the UE.](7e6522034f6ba31b1243b189d2e65ca2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant TSCTSF + Note right of TSCTSF: 2. Optionally cipher RAN time synchronization status + TSCTSF->>NG-RAN: 1. TSCTSF obtains RAN time synchronization status + TSCTSF-->>AMF: 3. Namf_Communication_NonUeN2MessageTransfer (RAN time synchronization status) + AMF->>NG-RAN: 4. N2 Transport (RAN time synchronization status) + NG-RAN->>UE: 5. Broadcast message (RAN time synchronization status) + +``` + +Sequence diagram showing the broadcast of RAN Time Synchronization Status. The diagram involves four entities: UE, NG-RAN, AMF, and TSCTSF. The sequence of messages is: 1. TSCTSF obtains RAN time synchronization status from NG-RAN; 2. TSCTSF optionally ciphers the RAN time synchronization status (shown in a dashed box); 3. TSCTSF sends a Namf\_Communication\_NonUeN2MessageTransfer (RAN time synchronization status) to AMF; 4. AMF sends an N2 Transport (RAN time synchronization status) to NG-RAN; 5. NG-RAN broadcasts the message (RAN time synchronization status) to the UE. + +Figure A.1.4.1.1-1: Broadcasting RAN Time Synchronization Status + +1. TSCTSF obtains RAN Time Synchronization Status. + +NOTE 1: Details of how to obtain RAN Time Synchronization Status are discussed in the solutions documented in clause 6 of this TR. + +2. TSCTSF may optionally cipher RAN Time Synchronization Status using a common key for all RAN nodes across one or multiple tracking areas. +3. TSCTSF invokes the Namf\_Communication\_NonUeN2MessageTransfer service operation towards the AMF to request the transfer of RAN Time Synchronization Status to an NG-RAN node. TSCTSF includes the Network RAN Time Synchronization Status and the target NG-RAN node identity. +4. AMF provides RAN Time Synchronization Status to the NG-RAN node indicated by TSCTSF. +5. RAN broadcasts the RAN Time Synchronization Status. +- 6.- UEs receive the RAN Time Synchronization Status provided in SIB. If the reference time quality information is ciphered and the UE has been provided with the ciphering key (see clause A.1.4.1.2), the UE decipheres the reference time quality information. + +NOTE 2 Similar as for the existing broadcast of assistance data for location services, it is assumed that UEs, which support receiving RAN Time Synchronization Status will be mandated, e.g. configured by upper layers, to ensure having a valid version of the SIB that will contain RAN Time Synchronization Status in RRC\_IDLE and RRC\_INACTIVE. (See also clause 5.2.2.1 of TS 38.331 [5] for further details on SIB handling by the UE for broadcast of assistance data for location services). + +##### A.1.4.1.2 Delivery of ciphering keys to UEs for broadcast of RAN Time Synchronization Status + +This procedure is used by the TSCTSF and the AMF to distribute ciphering keys to UEs to enable UEs to decipher RAN Time Synchronization Status ciphered by TSCTSF. + +![Sequence diagram showing the delivery of ciphering keys to UEs for broadcast of RAN Time Synchronization Status. The diagram involves four entities: UE, RAN, AMF, and TSCTSF. The sequence of messages is: 1. TSCTSF sends '1. Ciphering keys' to AMF. 2. AMF performs '2. Store ciphering keys'. 3. UE sends '3. Registration Request' to AMF via RAN. 4. AMF sends '4. Registration Accept (ciphering keys)' to UE via RAN.](41af98c5f15e6022f8ddde55567cf56e_img.jpg) + +``` +sequenceDiagram + participant UE + participant RAN + participant AMF + participant TSCTSF + Note right of AMF: 2. Store ciphering keys + TSCTSF->>AMF: 1. Ciphering keys + UE->>AMF: 3. Registration Request + AMF-->>UE: 4. Registration Accept (ciphering keys) +``` + +Sequence diagram showing the delivery of ciphering keys to UEs for broadcast of RAN Time Synchronization Status. The diagram involves four entities: UE, RAN, AMF, and TSCTSF. The sequence of messages is: 1. TSCTSF sends '1. Ciphering keys' to AMF. 2. AMF performs '2. Store ciphering keys'. 3. UE sends '3. Registration Request' to AMF via RAN. 4. AMF sends '4. Registration Accept (ciphering keys)' to UE via RAN. + +**Figure A.1.4.1.2-1: Delivery of Ciphering Keys to UEs for broadcast of RAN Time Synchronization Status** + +1. TSCTSF provides AMF with one or more ciphering keys used to cipher RAN Time Synchronization Status information according to the procedure in clause A.1.4.1.1.1. For each ciphering key, TSCTSF includes a ciphering key value, a ciphering key identifier, a validity period, and a set of applicable tracking areas. +2. The AMF stores the ciphering keys including the validity periods and applicable tracking areas. +3. A UE sends a Registration Request. The Registration Request may be sent as part of normal mobility management, a Registration Request may also be sent specifically to request and obtain ciphering keys. The UE includes in the Registration Request an indication that ciphering keys are requested. + +4. The AMF returns a Registration Accept to the UE as defined in TS 23.502 [3]. If the Registration Request includes the indication that ciphering keys are requested and the UE is subscribed for time synchronization services or AMF has received a request from TSCTSF to activate access stratum time synchronization for the UE, then AMF includes in the Registration Accept one or more ciphering keys applicable to the UE's current tracking area. AMF also includes for each ciphering key the ciphering key value, the ciphering key identifier, the validity period and the set of applicable tracking areas. + +# Annex B: Change history + +| Change history | | | | | | | | | +|----------------|-----------|------------|----------|-----|-----|---------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2022-02 | SA2#149 E | S2-2201055 | - | - | - | Proposed skeleton agreed at S2#149E | | 0.0.0 | +| 2022-09 | SA#97-e | SP-220818 | - | - | - | MCC editorial update for presentation to TSG SA for information` | | 1.0.0 | +| 2022-11 | SA#98-e | SP-221101 | - | - | - | 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 | +| 2023-03 | SA#99 | SP-230066 | 000
2 | 1 | C | TR 23.700 KI#1 conclusion update | | 18.1.0 | +| 2023-03 | SA#99 | SP-230066 | 000
3 | 1 | C | TR 23.700 KI#6 conclusion update | | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-41/raw.md b/raw/rel-18/23_series/23700-41/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..29f87441a11f1aabfe8f1a16015909744994e399 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/raw.md @@ -0,0 +1,6264 @@ + + +# 3GPP TR 23.700-41 V18.0.0 (2022-12) + +Technical Report + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; 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 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 ..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions of terms and abbreviations ..... | 12 | +| 3.1 Terms..... | 12 | +| 3.2 Abbreviations ..... | 12 | +| 4 Architectural Assumptions and Requirements..... | 12 | +| 5 Key Issues ..... | 12 | +| 5.1 Key Issue #1: Support of Network Slice Service continuity..... | 12 | +| 5.1.1 Description ..... | 12 | +| 5.2 Key Issue #2: Support of providing VPLMN network slice information to a roaming UE ..... | 13 | +| 5.2.1 Description ..... | 13 | +| 5.3 Key Issue #3: Network Slice Area of Service for services not mapping to existing TAs boundaries and Temporary network slices ..... | 13 | +| 5.3.1 Description ..... | 13 | +| 5.4 Key Issue #4: Support of NSAC involving multi service Area ..... | 14 | +| 5.4.1 Description ..... | 14 | +| 5.5 Key Issue #5: Improved support of RAs including TAs supporting Rejected S-NSSAIs ..... | 14 | +| 5.5.1 General description..... | 14 | +| 5.6 Key Issue #6: Improved network control of the UE behaviour ..... | 15 | +| 5.6.1 Description ..... | 15 | +| 6 Solutions..... | 16 | +| 6.0 Mapping of Solutions to Key Issues ..... | 16 | +| 6.1 Solution #1: Additional S-NSSAI associated with the PDU session..... | 18 | +| 6.1.1 Introduction ..... | 18 | +| 6.1.2 Functional Description ..... | 18 | +| 6.1.3 Procedures ..... | 19 | +| 6.1.3.1 Additional S-NSSAI handling during Handover Procedure..... | 19 | +| 6.1.3.2 Additional S-NSSAI handling during PDU Session Establishment Procedure..... | 19 | +| 6.1.4 Impacts on existing entities and interfaces..... | 20 | +| 6.2 Solution #2: Slice Re-mapping Capabilities for Network Slice Service Continuity..... | 21 | +| 6.2.1 Introduction ..... | 21 | +| 6.2.2 Functional Description ..... | 21 | +| 6.2.3 Procedures ..... | 21 | +| 6.2.3.1 General..... | 21 | +| 6.2.3.2 Registration..... | 21 | +| 6.2.3.3 Change of S-NSSAI of a PDU Session ..... | 22 | +| 6.2.3.4 AMF-triggered PDU Session Modification to change of S-NSSAI of PDU Session ..... | 23 | +| 6.2.4 Impacts on services, entities and interfaces..... | 24 | +| 6.3 Solution #3: Support of Network Slice Service continuity using a SSC mode 3 type of Service continuity..... | 24 | +| 6.3.1 Introduction ..... | 24 | +| 6.3.2 Functional Description ..... | 24 | +| 6.3.3 Procedures ..... | 24 | +| 6.3.4 Impacts on services, entities and interfaces..... | 26 | +| 6.4 Solution #4: PDU Session on compatible network slice..... | 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: PDU session handover to a target CN with an alternative S-NSSAI support ..... | 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..... | 29 | +| 6.6 | Solution #6: Extended SoR VPLMN Slice Information transfer to UEs..... | 29 | +| 6.6.1 | Introduction ..... | 29 | +| 6.6.2 | Functional Description ..... | 29 | +| 6.6.3 | Procedures ..... | 30 | +| 6.6.3.1 | Extended SoR VPLMN Slice Information transfer to UE..... | 30 | +| 6.6.3.1.1 | UE Initiated capability indication ..... | 31 | +| 6.6.3.1.2 | Network Triggered capability indication ..... | 33 | +| 6.6.4 | Impacts on Existing Nodes and Functionality..... | 34 | +| 6.7 | Solution #7: Enabling awareness of Network Slice availability in VPLMNs ..... | 34 | +| 6.7.1 | Introduction ..... | 34 | +| 6.7.2 | Functional Description ..... | 34 | +| 6.7.3 | Procedures ..... | 35 | +| 6.7.3.1 | Option 1 - UE's USIM is NOT configured to receive a Slice-Aware SoR..... | 35 | +| 6.7.3.2 | Option 2 - UE's USIM is configured to receive a Slice-Aware SoR..... | 36 | +| 6.7.4 | Impacts on services, entities and interfaces..... | 36 | +| 6.8 | Solution #8: Gracefully network slice termination ..... | 37 | +| 6.8.1 | Introduction ..... | 37 | +| 6.8.2 | Functional Description ..... | 38 | +| 6.8.3 | Procedures ..... | 38 | +| 6.8.4 | Impacts on services, entities and interfaces..... | 40 | +| 6.9 | Solution #9: Support of a Network Slice with an AoS not matching existing TA boundaries..... | 41 | +| 6.9.1 | Introduction ..... | 41 | +| 6.9.2 | Description ..... | 41 | +| 6.9.3 | Procedures ..... | 42 | +| 6.9.4 | Impacts on services, entities and interfaces..... | 44 | +| 6.10 | Solution #10: Associating a validity timer with a temporary slice ..... | 45 | +| 6.10.1 | Introduction ..... | 45 | +| 6.10.2 | Procedures ..... | 46 | +| 6.10.3 | Impacts on services, entities and interfaces..... | 46 | +| 6.11 | Solution #11: Enabling UEs to Request S-NSSAIs not uniformly available..... | 47 | +| 6.11.1 | Introduction ..... | 47 | +| 6.11.2 | Functional Description ..... | 47 | +| 6.11.3 | Procedures ..... | 48 | +| 6.11.3.1 | Registration Procedure..... | 48 | +| 6.11.3.2 | UE Configuration Update Procedure..... | 49 | +| 6.11.3.3 | UE Requested PDU Session Establishment Procedure ..... | 49 | +| 6.11.3.4 | Service Request..... | 49 | +| 6.11.3.5 | PDU Session Release..... | 49 | +| 6.11.4 | Impacts on services, entities and interfaces..... | 49 | +| 6.12 | Solution #12: Solution for Centralized Counting for Multiple Service Areas and 5GS-EPS Interworking ..... | 50 | +| 6.12.1 | Description ..... | 50 | +| 6.12.2 | Procedures ..... | 51 | +| 6.12.2.1 | UE Registration Admission ..... | 51 | +| 6.12.2.1.1 | 5GS only slices..... | 51 | +| 6.12.2.1.2 | 5GS-EPS Interworking with EPS Counting Active ..... | 51 | +| 6.12.2.2 | Roaming..... | 52 | +| 6.12.2.3 | UE PDU Session Admission..... | 52 | +| 6.12.2.3.1 | 5GS only slices..... | 52 | +| 6.12.2.3.2 | 5GS-EPS Interworking with EPS Counting Active ..... | 53 | +| 6.12.2.4 | Discovery of Central NSACF..... | 53 | +| 6.12.3 | Impacts on services, entities and interfaces..... | 53 | +| 6.13 | Solution #13: Hierarchical NSACF Architecture for Maximum UE/PDU Session number control ..... | 54 | +| 6.13.1 | Introduction ..... | 54 | +| 6.13.2 | Functional Description ..... | 54 | +| 6.13.3 | Procedures ..... | 56 | +| 6.13.3.1 | Registration management Procedures..... | 56 | +| 6.13.3.2 | PDU Session management Procedures ..... | 58 | +| 6.13.3.3 | Redistribution of local maximum number ..... | 59 | +| 6.13.3.4 | Session continuity handling..... | 59 | +| 6.13.3.5 | HPLMN control and EPS counting support ..... | 60 | +| 6.13.4 | Impacts on services, entities and interfaces..... | 60 | + +| | | | +|----------|------------------------------------------------------------------------------------------------------------------------------|----| +| 6.14 | Solution #14: Maximum Number Distribution in multiple NSACFs ..... | 60 | +| 6.14.1 | Introduction ..... | 60 | +| 6.14.2 | Functional Description ..... | 61 | +| 6.14.3 | Procedure ..... | 61 | +| 6.14.4 | Impacts on services, entities and interfaces ..... | 61 | +| 6.15 | Solution #15: Service continuity in case of Network Slice instance overload..... | 62 | +| 6.15.1 | Introduction ..... | 62 | +| 6.15.2 | Functional Description ..... | 62 | +| 6.15.3 | Procedures ..... | 63 | +| 6.15.4 | Impacts on services, entities and interfaces ..... | 63 | +| 6.16 | Solution #16: UE assisted slice based VPLMN prioritization for Extended SoR ..... | 64 | +| 6.16.1 | Introduction ..... | 64 | +| 6.16.2 | High Level Description ..... | 64 | +| 6.16.3 | Procedures ..... | 64 | +| 6.16.4 | Impacts on services, entities and interfaces ..... | 66 | +| 6.17 | Solution #17: Slice based VPLMN Selection Policy ..... | 66 | +| 6.17.1 | Introduction ..... | 66 | +| 6.17.2 | Functional Description ..... | 66 | +| 6.17.3 | Procedures ..... | 67 | +| 6.17.4 | Impacts on services, entities and interfaces ..... | 68 | +| 6.18 | Solution #18: Sending rejected NSSAI to the UDM to assist the UDM to steer the UE to the PLMN supporting rejected NSSAI..... | 68 | +| 6.18.1 | Introduction ..... | 68 | +| 6.18.2 | Procedures ..... | 68 | +| 6.18.3 | Impacts on services, entities and interfaces..... | 69 | +| 6.19 | Solution #19: Configuring the UE with network slice aware preferred PLMNs lists..... | 70 | +| 6.19.1 | Introduction ..... | 70 | +| 6.19.2 | Functional Description ..... | 70 | +| 6.19.3 | Procedures ..... | 71 | +| 6.19.4 | Impacts on services, entities and interfaces ..... | 73 | +| 6.20 | Solution #20: PLMN Selection following existing SoR information ..... | 73 | +| 6.20.1 | Introduction ..... | 73 | +| 6.20.2 | Functional Description ..... | 73 | +| 6.20.3 | Procedures ..... | 74 | +| 6.20.4 | Impacts on services, entities and interfaces..... | 74 | +| 6.21 | Solution #21: Temporary slice based on URSP ..... | 75 | +| 6.21.1 | Introduction ..... | 75 | +| 6.21.2 | Functional Description ..... | 75 | +| 6.21.3 | Procedures ..... | 75 | +| 6.21.4 | Impacts on services, entities and interfaces ..... | 75 | +| 6.22 | Solution #22: Enabling graceful slice termination with support of UE policies..... | 76 | +| 6.22.1 | Introduction ..... | 76 | +| 6.22.2 | Functional Description ..... | 76 | +| 6.22.3 | Procedures ..... | 77 | +| 6.22.4 | Impacts on services, entities and interfaces ..... | 77 | +| 6.23 | Solution #23: UE registration for conditional network slices ..... | 77 | +| 6.23.1 | Introduction ..... | 77 | +| 6.23.2 | Functional description ..... | 77 | +| 6.23.3 | Procedures ..... | 78 | +| 6.23.4 | Impacts on services, entities and interfaces ..... | 79 | +| 6.24 | Solution #24: On the handling of temporary network slices..... | 79 | +| 6.24.1 | Introduction ..... | 79 | +| 6.24.2 | Functional Description ..... | 79 | +| 6.24.3 | Procedures ..... | 80 | +| 6.24.3.1 | RM aspects..... | 80 | +| 6.24.3.2 | Session Management aspect ..... | 81 | +| 6.24.4 | Impacts on services, entities and interfaces ..... | 84 | +| 6.25 | Solution #25: Handling Rejected S-NSSAIs in some TAs of RA ..... | 85 | +| 6.25.1 | Key Issue mapping ..... | 85 | +| 6.25.2 | Functional Description ..... | 85 | +| 6.25.3 | Procedures ..... | 86 | +| 6.25.4 | Impacts on services, entities and interfaces ..... | 87 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.26 | Solution #26: Multiple areas and resource partitioning ..... | 87 | +| 6.26.1 | Introduction ..... | 87 | +| 6.26.2 | Functional Description ..... | 88 | +| 6.26.2.1 | Support of multiple areas ..... | 88 | +| 6.26.2.2 | Reducing resources for cells outside service area ..... | 88 | +| 6.26.3 | Procedures ..... | 90 | +| 6.26.4 | Impacts on services, entities and interfaces ..... | 91 | +| 6.27 | Solution #27: Exception to the rejected NSSAI handling ..... | 91 | +| 6.27.1 | Introduction ..... | 91 | +| 6.27.2 | Functional Description ..... | 91 | +| 6.27.3 | Procedures ..... | 92 | +| 6.27.4 | Impacts on services, entities and interfaces ..... | 93 | +| 6.28 | Solution #28: Support of network slices with TA granularity within a RA ..... | 93 | +| 6.28.1 | Functional Description ..... | 93 | +| 6.28.2 | Procedures ..... | 94 | +| 6.28.3 | Impacts on Existing Nodes and Functionality ..... | 94 | +| 6.29 | Solution #29: On handling S-NSSAIs not supported in certain TAs of a RA during a registration ..... | 94 | +| 6.29.1 | Introduction ..... | 94 | +| 6.29.2 | Functional Description ..... | 95 | +| 6.29.3 | Procedures ..... | 96 | +| 6.29.3.1 | Indication to UE of TAs where the rejected S-NSSAI is supported (or is not supported) in the RA ..... | 96 | +| 6.29.3.2 | Indication to UE of Allowed NSSAI in RA and of Partially Allowed S-NSSAIs in RA with TAs of RA where the Partially Allowed S-NSSAIs is supported. .... | 97 | +| 6.29.3.2.1 | Registration ..... | 97 | +| 6.29.3.2.2 | MO Procedure from idle mode ..... | 98 | +| 6.29.3.2.3 | MT Procedure from idle mode ..... | 101 | +| 6.29.3.2.4 | Connected Mode system behaviour ..... | 103 | +| 6.29.3.2.5 | Session management ..... | 106 | +| 6.29.3.2.6 | AN Release ..... | 106 | +| 6.29.4 | Impacts on services, entities and interfaces ..... | 106 | +| 6.30 | Solution #30: Rejected S-NSSAI with new cause value ..... | 107 | +| 6.30.1 | Introduction ..... | 107 | +| 6.30.2 | Functional Description ..... | 107 | +| 6.30.3 | Procedure ..... | 107 | +| 6.30.4 | Impacts on services, entities and interfaces ..... | 108 | +| 6.31 | Solution #31: Enabling Flexible RAs with Slice Service Area ..... | 108 | +| 6.31.1 | Introduction ..... | 108 | +| 6.31.2 | Functional Description ..... | 108 | +| 6.31.3 | Procedures ..... | 108 | +| 6.31.3.1 | Option A - Reject Slices that are Not Available in the current TA ..... | 108 | +| 6.31.3.2 | Option B - Neither Reject nor Allow Slices that are Not Available in the current TA ..... | 109 | +| 6.31.4 | Impacts on services, entities and interfaces ..... | 109 | +| 6.32 | Solution #32: Solution for Network Control for UE Slice Use ..... | 110 | +| 6.32.1 | Description ..... | 110 | +| 6.32.2 | Procedures ..... | 111 | +| 6.32.2.1 | PDU session Transfer from Source Slice to Target Slice, UE Initiated approach ..... | 111 | +| 6.32.2.2 | PDU Session Transfer from Source Slice to Target Slice - Network Initiated Approach ..... | 112 | +| 6.32.2.2.1 | AMF Initiated Approach ..... | 112 | +| 6.32.2.2.2 | PCF Initiated Approach ..... | 113 | +| 6.32.2.3 | SSC Mode and PDU Session Transfer from Source Network Slice to Target Network Slice ..... | 114 | +| 6.32.3 | Impacts on Existing Nodes and Functionality ..... | 114 | +| 6.33 | Solution #33: Slice-specific implicit deactivation timers ..... | 114 | +| 6.33.1 | Functional Description ..... | 114 | +| 6.33.1.1 | Registration control ..... | 114 | +| 6.33.1.2 | PDU session control ..... | 115 | +| 6.33.2 | Procedures ..... | 115 | +| 6.33.3 | Impacts on Existing Nodes and Functionality ..... | 115 | +| 6.34 | Solution #34: On-demand slices ..... | 115 | +| 6.34.1 | Functional Description ..... | 115 | +| 6.34.2 | Procedures ..... | 116 | +| 6.34.3 | Impacts on Existing Nodes and Functionality ..... | 116 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.35 | Solution #35: Network Slice usage control by the network..... | 116 | +| 6.35.1 | Introduction ..... | 116 | +| 6.35.2 | Functional description ..... | 116 | +| 6.35.3 | Procedures ..... | 117 | +| 6.35.4 | Impacts on services, entities and interfaces..... | 118 | +| 6.36 | Solution #36: UE provided reason for registration to S-NSSAI ..... | 118 | +| 6.36.1 | Introduction ..... | 118 | +| 6.36.2 | Functional Description ..... | 118 | +| 6.36.3 | Procedures ..... | 119 | +| 6.36.4 | Impacts on services, entities and interfaces..... | 120 | +| 6.37 | Solution #37: Actual UE Activity-based Slice Admission Control ..... | 120 | +| 6.37.1 | Introduction ..... | 120 | +| 6.37.2 | Functional Description ..... | 121 | +| 6.37.3 | Procedures ..... | 121 | +| 6.37.4 | Impacts on services, entities and interfaces..... | 123 | +| 6.38 | Solution #38: On configuring the UE with UE behaviour policies..... | 123 | +| 6.38.1 | Introduction ..... | 123 | +| 6.38.2 | Functional Description ..... | 123 | +| 6.38.3 | Procedures ..... | 124 | +| 6.38.3.1 | USIM default configuration..... | 124 | +| 6.38.3.2 | Control plane procedures ..... | 125 | +| 6.38.3.2.1 | UDM Option ..... | 125 | +| 6.38.3.2.2 | NSSF/PCF Option 2 ..... | 127 | +| 6.38.3.3 | URSP possible impact ..... | 129 | +| 6.38.4 | Impacts on services, entities and interfaces..... | 129 | +| 6.39 | Solution #39: Serving PLMN steering UE to preferred slice for selection of PDU session..... | 130 | +| 6.39.1 | Description ..... | 130 | +| 6.39.2 | Procedures ..... | 131 | +| 6.39.3 | Impacts on Existing Nodes and Functionality..... | 131 | +| 6.40 | Solution #40: S-NSSAI change decided by PCF ..... | 131 | +| 6.40.1 | Introduction ..... | 131 | +| 6.40.2 | Functional Description ..... | 132 | +| 6.40.3 | Procedures ..... | 132 | +| 6.40.3.1 | The S-NSSAI change determination by PCF for an ongoing PDU session on non-roaming and local breakout roaming scenario ..... | 132 | +| 6.40.3.2 | The S-NSSAI change determination by PCF for an ongoing PDU session triggered by an SMF report on home-routed roaming cases..... | 134 | +| 6.40.4 | Impacts on services, entities and interfaces..... | 135 | +| 6.41 | Solution #41: Network Slice change without service interruption ..... | 136 | +| 6.41.1 | Introduction ..... | 136 | +| 6.41.2 | Functional Description ..... | 136 | +| 6.41.3 | Procedures ..... | 136 | +| 6.41.3.1 | General..... | 136 | +| 6.41.3.2 | Change of network slice ..... | 136 | +| 6.41.4 | Impacts on services, entities and interfaces..... | 137 | +| 6.42 | Solution #42: Network controlled change to an alternative S-NSSAI..... | 138 | +| 6.42.1 | Introduction ..... | 138 | +| 6.42.2 | Functional Description ..... | 138 | +| 6.42.3 | Procedures ..... | 139 | +| 6.42.4 | Impacts on services, entities and interfaces..... | 142 | +| 6.43 | Solution #43: Allowed NSSAI Determination in Initial Registration to Support Network Slice Service Continuity..... | 142 | +| 6.43.1 | Introduction ..... | 142 | +| 6.43.2 | Functional Description ..... | 142 | +| 6.43.3 | Procedures ..... | 143 | +| 6.43.3.1 | Secondary NSSAI Determination..... | 143 | +| 6.43.3.2 | PDU Session Transferred to a New Network Slice in No Mobility Scenario ..... | 144 | +| 6.43.3.3 | PDU session transferred to a new network slice in mobility scenario..... | 144 | +| 6.43.4 | Impacts on services, entities and interfaces..... | 145 | +| 6.44 | Solution #44: Controlling UE access to the network per Network Slice on a per cell level granularity ..... | 145 | +| 6.44.1 | Introduction ..... | 145 | +| 6.44.2 | Functional Description ..... | 145 | + +| | | | +|--------------------------------------|-------------------------------------------------------------------------------------|------------| +| 6.44.3 | Procedures ..... | 146 | +| 6.44.3.1 | General..... | 146 | +| 6.44.3.2 | Mobility procedures..... | 147 | +| 6.44.4 | Impacts on services, entities and interfaces..... | 147 | +| 6.45 | Solution #45: Constrained Service Area for the Network Slice..... | 147 | +| 6.45.1 | Introduction ..... | 147 | +| 6.45.2 | Functional Description ..... | 147 | +| 6.45.3 | Procedures ..... | 148 | +| 6.45.3.1 | Configuration of Constrained Service Area information..... | 148 | +| 6.45.3.2 | UE mobility..... | 148 | +| 6.45.4 | Impacts on services, entities and interfaces..... | 148 | +| 6.46 | Solution #46: Controlling network slice based on UE's inactive PDN connection ..... | 148 | +| 6.46.1 | Introduction ..... | 148 | +| 6.46.2 | Functional Description ..... | 148 | +| 6.46.3 | Procedures ..... | 149 | +| 6.46.4 | Impacts on services, entities and interfaces..... | 149 | +| 7 | Overall Evaluation ..... | 149 | +| 7.1 | Evaluation for KI#1..... | 149 | +| 7.2 | Evaluation for KI#2..... | 154 | +| 7.3 | Evaluation for KI#3..... | 154 | +| 7.4 | Evaluation for KI#4..... | 156 | +| 7.5 | Evaluation for KI#5..... | 156 | +| 7.6 | Evaluation for KI#6..... | 157 | +| 8 | Conclusions..... | 160 | +| 8.1 | Conclusions for KI#1 ..... | 160 | +| 8.2 | Conclusions for KI#2 ..... | 161 | +| 8.3 | Conclusions for KI#3 ..... | 162 | +| 8.4 | Conclusions for KI#4 ..... | 163 | +| 8.5 | Conclusions for KI #5 ..... | 165 | +| 8.6 | Conclusions for KI #6 ..... | 165 | +| Annex A: Change history ..... | | 167 | + +## 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 the gaps and performs evaluations of potential architecture enhancements to support Network Slicing with the following objectives: + +1. Study whether and how to address the following scenario in order to provide service continuity: if an existing network slice or network slice instance cannot serve the PDU session, or if the existing network slice instance cannot meet the performance requirements of the applications. The study should investigate whether deployment optimization is sufficient. Minimized system optimisations can be considered if valuable. +2. Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA. +3. Study whether and how to support the following stage one Rel-18 EASNS requirements related to roaming specified in TS 22.261 clause 6.1.2.1, i.e. Requirement on enhancement the information available to the UE in roaming scenarios regarding the availability of network slices in VPLMNs available in the roaming country, in order to allow the UE to select and obtain services from the VPLMN supporting the network slices which UE may wish to use. +4. Study whether and how to enhance the system to ensure network controlled behaviour of network slice usage including UE registration and PDU Session establishment (e.g. so that when performing NSAC the network slice can serve UEs/PDU Sessions with actual activity). +5. Study deployment considerations when a service provided has an area of service that does not overlap with the already deployed Tracking Areas and/or have a limited lifetime and how existing mechanisms including network slicing can help support such scenarios. If existing mechanisms are concluded to be not sufficient to achieve the scenarios, study whether and how additional mechanisms can resolve the analysed gap. +6. Study whether and how to enhance the support of NSAC when more than one NSACF is involved in enforcing a shared maximum allowed number of the UEs or PDU Sessions for a network slice in one PLMN or in roaming, in order to avoid fragmentation of the shared maximum allowed number. This item depends on the outcome of corresponding Rel-17 CRs. + +# 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)". +- [3] 3GPP TR 38.832: "Study on enhancement of Radio Access Network (RAN) slicing". +- [4] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1". +- [5] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [6] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [7] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [8] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". + +- [9] 3GPP TS 38.304: "User Equipment (UE) procedures in Idle mode and RRC Inactive state". +- [10] 3GPP TS 22.071: "Location Services (LCS); Service Description". +- [11] 3GPP TS 38.331: "Radio Resource Control (RRC) protocol specification". +- [12] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS)". +- [13] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM)". +- [14] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [15] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [16] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". + +--- + +## 3 Definitions of terms 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]. + +### 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]. + +--- + +## 4 Architectural Assumptions and Requirements + +The following architectural requirements apply: + +- Solutions may include reuse (in part or totally) of existing mechanisms. When reuse is deemed to be possible, whether new approaches shall also be adopted or added shall be subject of evaluation. (i.e. it shall be considered whether the reuse of existing system capabilities is sufficiently effective and efficient in addressing the problem space). + +--- + +## 5 Key Issues + +### 5.1 Key Issue #1: Support of Network Slice Service continuity + +#### 5.1.1 Description + +This Key issues is aiming to address WT#1. The following scenarios can happen: + +**1) No mobility scenario:** + +Scenario 1a): network slice is overloaded in NG-RAN. + +Scenario 1b): network slice or network slice instance is overloaded or undergoing planned maintenance in CN (e.g. network slice termination). + +Scenario 1c): network performance of the network slice cannot meet the SLA. + +**2) Inter RA Mobility scenario:** + +Scenario 2a): network slice is not supported in the target RAN node. + +Scenario 2b): network slice in target RAN node is overloaded. + +Scenario 2c): network slice is not supported in the target CN. + +Scenario 2d): network slice or network slice instance is overloaded in the target CN. + +This key issue is to study whether and how to provide service continuity for PDU sessions in network slices in the above scenarios 1b), 1c) and 2d). + +NOTE 1: PDU Session with different SSC modes will be considered during the study. + +NOTE 2: For scenario 1a) and 2b), TR 38.832 [3] already has conclusion. However it doesn't preclude that solutions defined for this key issue can also be used in these scenarios. + +NOTE 3: For scenario 2a) and 2c), it is a deployment issue and assumed not to be studied in SA WG2. + +**Editor's note:** It is FFS whether there is a need to study 2a) and 2c). + +NOTE 4: Coordination with RAN working groups may be needed to conclude the key issue. + +## 5.2 Key Issue #2: Support of providing VPLMN network slice information to a roaming UE + +### 5.2.1 Description + +As an outcome of SA WG1 EASNS (Enhanced Access to and Support of Network Slice) work, clause 6.1.2.1 of TS 22.261 [4] captures the following service requirement for a roaming UE. + +*For a roaming UE activating a service/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice.* + +This key issue aims at addressing the following aspects for a roaming UE requiring a network slice not offered by higher priority VPLMN(s) but available from other network(s): + +- Study how and when the HPLMN provides the UE with information about slice availability per VPLMN and prioritization information of the VPLMNs with which the UE may register for the network slice. The study includes the content of the information. +- Study how and when to use the information received by the UE from the HPLMN to influence automatic PLMN selection. + +NOTE 1: For details on PLMN selection aspects and impacts on PLMN selection of solutions of this key issue, coordination with CT1 is needed. + +NOTE 2: Impacts to manual selection is not in scope of the key issue. + +This key issue only considers the network selection procedure for the 3GPP access type. + +NOTE 3: Coordination with the Study Item FS\_5WWC\_Ph2 is required regarding the VPLMN selection procedure when non-3GPP access type is used. + +## 5.3 Key Issue #3: Network Slice Area of Service for services not mapping to existing TAs boundaries and Temporary network slices + +### 5.3.1 Description + +Network Slices are deployed for services over an Area of Service which may match the existing TAs or for which the Area of Service can be different. Currently, the network slice availability (i.e. where the network slices are defined to be supported) is designed to match deployed TA boundaries. In addition, the UEs and network configuration can be + +impacted when network slices are deployed and decommissioned over certain time interval (e.g. the Configured NSSAI can change when a network slice is no longer available or becomes available, this can affect the Allowed NSSAI and other parameters and in turn the RA may need to change, etc.). + +This Key Issue will study how to address the issues described above and whether system level improvements are needed to mitigate e.g. the deployment and control plane issues that arise due to the currently defined system behaviour: + +- The support of services over network slices when the services have Area of Service not matching the existing deployed TA boundaries. +- The support of network slices which have a limited lifetime (including how to gracefully terminate a network slice which can apply also to network slices which have a longer lifespan in order to avoid abrupt PDU Session release). + +NOTE: Coordination with SA WG5 can be needed for Network Slice Life Cycle Management aspects. + +## 5.4 Key Issue #4: Support of NSAC involving multi service Area + +### 5.4.1 Description + +For one S-NSSAI, there is only one configured global Maximum allowed number value for NSAC. It is possible more than one service area is associated with one S-NSSAI, e.g. to split a PLMN into multi-service areas. This impacts the use cases below as there will be more than one NSACF handling the UE: + +- Multi NSACF deployed within one PLMN: For NSACF deployment more than one service area are defined within one PLMN. For each service area one NSACF or NSACF set is selected for slice admission control. This include the control of the maximum allowed number of UE or PDU session. +- Roaming: when one user resides at the visit PLMN, the NSAC (Maximum PDU session) may be controlled by the NSACF in the VPLMN (e.g. for LBO PDU session), or the NSACF in the HPLMN (e.g. for HR PDU session). +- EPS interworking: when the user establishes a HR PDN connection at the EPS network and move to 5GS later, the NSACF(Maximum UE number) selected by the SMF+PGW-C and AMF may be different. + +This key issue addresses the above cases, to ensure consistent NSAC handling against the configured global Maximum allowed number. The following aspects will be covered by the key issue: + +- UE Registration. +- PDU Session establishment. +- Session continuity when UE move across the service area. + +## 5.5 Key Issue #5: Improved support of RAs including TAs supporting Rejected S-NSSAIs + +### 5.5.1 General description + +When the AMF creates a Registration Area (RA) with one or more Tracking Areas (TAs), all the S-NSSAIs of the S-NSSAIs in the Allowed NSSAI need to be available in all the TAs of the RA. If the UE requests an S-NSSAI that is not available in current TA, with current specifications this S-NSSAI is rejected with an indication that the S-NSSAI is not available in the RA. This cause code indicates to the UE that the UE is not allowed to try to register the S-NSSAI again in any of the TAs of the RA. This restriction is placed on the UE even if some of the TAs in the RA do support the S-NSSAI. This then creates the need to choose between optimal RA (considering the trade-off between paging load vs. the load generated due to Mobility Registration Update (MRU) requests) and the goal to allow the UE to register as soon as possible with the S-NSSAI that was not supported in the TA where the S-NSSAI was not available and therefore not allowed. + +This key issue will study whether and how to allow the UE to initiate a registration for an S-NSSAI which was rejected for the RA when the UE enters a TA that is part of the RA and the TA supports this S-NSSAI. + +NOTE: When an RA is created considering the trade-off between paging load vs the load generated due to Mobility Registration Update (MRU), without considering the need of the UE to register with an S-NSSAI in these TAs, the AMF can add to the RA TAs that support an S-NSSAI that was not available in the TA where the S-NSSAI was not allowed. + +## 5.6 Key Issue #6: Improved network control of the UE behaviour + +### 5.6.1 Description + +In the 5GS specifications up to rel-17, a UE Registers/Deregisters with a Network Slice and establishes/tears down PDU sessions based on own policy taking into account network provided information such as the URSPs. However, this does not allow an operator e.g. to enforce that the UE only registers with a S-NSSAI when it is actually needed to have connectivity in the related network slice. A UE may in fact choose to register with all the Configured NSSAIs and then use the URSP just to decide which DNNs to connect to at run time. Also, it is not clear whether a UE can be requested by the operator to establish connectivity with a DNN based on own logic and URSPs at any time e.g. based on the UE configuration alone. + +Operators currently do not have the ability to enforce when the UE can register with network slices based on e.g. only on actual need of connectivity in a network slice, or by configuration independent of detected need of connectivity, etc. depending on e.g. what is best for the domain of application (e.g. to save battery usage one may just register based on configuration despite the URSPs are provisioned, or, when NSAC is applied on the number of UEs, the operators may want the UE to deregister from the slice subject to NSAC and register with it based on actual usage.) Operators also cannot provide to the UE a policy for deregistration of a network slice or tear down of a PDU session (e.g. the operator cannot control the time when a PDU session is released after it is last needed by any application running in the UE, nor can the operator define the earliest time a UE is allowed to deregister from a network slice after there are no more PDU sessions established over it). + +There is also no way for the serving PLMN to steer a UE to a preferred slice of the serving PLMN (i.e. the HPLMN or VPLMN) even if the UE may have the related HPLMN slice included in the possible connectivity options (URSP) for one application. + +NOTE: for the purpose of this Key Issue, usage of a PDU session means there is at least one application actually uses the connectivity of the PDU session. + +This Key Issue will study how to enable network-controlled behaviour and ensure the proper utilization of Slices in the system (e.g. what the network can request to the UE and how and what additional policies the network can provide to the UE) taking into account the above aspects (e.g. actual slice usage, UE activity, etc.). + +--- + +## 6 Solutions + +### 6.0 Mapping of Solutions to Key Issues + +**Table 6.0-1: Mapping of Solutions to Key Issues** + +| Solutions | Key Issues | | | | | | +|-------------------------------------------------------------------------------------------------------------------------|------------|------|------|------|------|------| +| | KI#1 | KI#2 | KI#3 | KI#4 | KI#5 | KI#6 | +| Solution #1: Additional S-NSSAI associated with the PDU session | X | | | | | | +| Solution #2: Slice Re-mapping Capabilities for Network Slice Service Continuity | X | | | | | | +| Solution #3: Support of Network Slice Service continuity using SSC mode 3 | X | | | | | | +| Solution #4: PDU Session on compatible network slice | X | | | | | | +| Solution #5: PDU session handover to a target CN with an alternative S-NSSAI support | X | | | | | | +| Solution #6: Extended SoR VPLMN Slice Information transfer to UEs | | X | | | | | +| Solution #7: Enabling awareness of Network Slice availability in VPLMNs | | X | | | | | +| Solution #8: Gracefully network slice termination | | | X | | | | +| Solution #9: Support of a Network Slice with an AoS not matching existing TA boundaries | | | X | | | | +| Solution #10: Associating a validity timer with a temporary slice | | | X | | | | +| Solution #11: Enabling UEs to Request S-NSSAIs not uniformly available | | | X | | X | | +| Solution #12: Solution for Centralized Counting for Multiple Service Areas and 5GS-EPS Interworking | | | | X | | | +| Solution #13: Hierarchical NSACF Architecture for Maximum UE/PDU Session number control | | | | X | | | +| Solution #14: Maximum Number Distribution in multiple NSACFs | | | | X | | | +| Solution #15: Service continuity in case of Network Slice instance overload | X | | | | | | +| Solution #16: UE assisted slice based VPLMN prioritization for Extended SoR | | X | | | | | +| Solution #17: Slice based VPLMN Selection Policy | | X | | | | | +| Solution #18: Sending rejected NSSAI to the UDM to assist the UDM to steer the UE to the PLMN supporting rejected NSSAI | | X | | | | | +| Solution #19: configuring the UE with network slice aware preferred PLMNs lists | | X | | | | | +| Solution #20: VPLMN Selection following existing SoR information | | X | | | | | +| Solution #21: Temporary slice based on URSP | | | X | | | | +| Solution #22: Enabling graceful slice termination with support of UE policies | | | X | | | | +| Solution #23: UE registration for conditional network slices | | | X | | X | | +| Solution #24: On the handling temporary network slices | | | X | | | | +| Solution #25: Handling Rejected S-NSSAIs in some TAs of RA | | | | | X | | +| Solution #26: Multiple areas and resource partitioning | | | X | | X | | +| Solution #27: Exception to the rejected NSSAI handling | | | | | X | | +| Solution #28: Support of network slices with TA granularity within a RA | | | | | X | | +| Solution #29: On handling S-NSSAIs not supported in certain TAs of a RA during a registration | | | X | | X | | +| Solution #30: Rejected S-NSSAI with new cause value | | | | | X | | +| Solution #31: Enabling Flexible RAs with Slice Service Area | | | | | X | | +| Solution #32: Solution for Network Control for UE Slice Use | X | | | | | X | +| Solution #33: Slice-specific implicit deactivation timers | | | | | | X | +| Solution #34: On-demand slices | | | | | | X | +| Solution #35: Network Slice usage control by the network | | | | | | X | +| Solution #36: UE provided reason for registration to S-NSSAI | | | | | | X | +| Solution #37: Actual UE Activity-based Slice Admission Control | | | | | | X | +| Solution #38: On configuring the UE with UE behaviour policies | | | | | | X | +| Solution #39: Serving PLMN steering UE to preferred slice for selection of PDU session | | | | | | X | +| Solution #40: S-NSSAI change decided by PCF | X | | | | | | +| Solution #41: Network Slice change without service interruption | X | | | | | | +| Solution #42: Network controlled change to an alternative S-NSSAI | X | | | | | | +| Solution #43: Allowed NSSAI Determination in Initial Registration to Support Network Slice Service Continuity | X | | | | | | +| Solution #44: Controlling UE access to the network per Network Slice on a per cell level granularity | | | X | | | | +| Solution #45: Constrained Service Area for the Network Slice | | | X | | | | + +| | | | | | | | +|-------------------------------------------------------------------------------|--|--|--|--|--|---| +| Solution #46: Controlling network slice based on UE's inactive PDN connection | | | | | | X | +|-------------------------------------------------------------------------------|--|--|--|--|--|---| + +## 6.1 Solution #1: Additional S-NSSAI associated with the PDU session + +### 6.1.1 Introduction + +This solution aims to address the key issues#1: Support of Network Slice Service continuity, particularly it reuses the concept that the PDU session can be associate with two S-NSSAIs (based on values provided in mapping of Allowed NSSAI in case of e.g. roaming). The scenario covers the case where NFs (e.g. AMF, SMF, UPF...) in a network slice instance support multiple S-NSSAIs. How to split the resource depends on implementation. It is possible that the resource of one S-NSSAI is getting congested, while other S-NSSAI is not (e.g. there is a fixed allocation of resources to each S-NSSAI in the NF instances). This solution proposes that when one S-NSSAI is congested, the network can associate the PDU session with additional S-NSSAI in order to provide service continuity during mobility scenario (scenario 2d), so the resource allocated in SMF and/or UPF for one S-NSSAI can be shared by other S-NSSAI if other S-NSSAI is getting congested. This solution can also be used for PDU Session establishment procedure in scenario 1b. + +**Editor's note:** The validity of the scenario that this solution covers is to be further assessed. + +**NOTE:** This solution may be extended to cover no mobility scenarios 1b and 1c described in clause 5.1.1 + +**Editor's note:** It is FFS whether and how the PDU Session can be associated with more than one S-NSSAI within a PLMN + +### 6.1.2 Functional Description + +In this solution it is assumed that a network slice instance may be associated with multiple S-NSSAIs in the PLMN and each S-NSSAI may use different network resources. The AMF, SMF and UPF is configured with which S-NSSAIs are associated with the network slice instance. When the UE establishes PDU session it determines the requested S-NSSAI based on the URSP rules. The PDU Session is initially associated with this requested S-NSSAI. When this requested S-NSSAI become congested in the area of interest, the network may associate the PDU session with an additional S-NSSAI which can be associated with the network slice instance and is not congested in this area. The network then sends during the PDU Session establishment this additional S-NSSAI associated with the PDU session to the NG-RAN, instead of the original requested S-NSSAI. After the S-NSSAI congestion is mitigated, the network may remove the additional S-NSSAI of the PDU Session locally in the CN. + +The AMF may determine the S-NSSAI is congested in the area of interest and the impacted PDU sessions based on the load level information or service experience for a Network Slice or network slice instance provided by the NWDAF. + +When the AMF determines to associate the PDU session with an additional S-NSSAI and if there is an I-SMF, the AMF provides the additional S-NSSAI to the I-SMF and the I-SMF provides the additional S-NSSAI to the SMF. If there is no I-SMF, the AMF provides the additional S-NSSAI to SMF. The I-SMF/SMF uses this additional S-NSSAI in the N2 information and send it to NG-RAN. The I-SMF/SMF may also send the additional S-NSSAI to the UPF. + +This additional S-NSSAI is not provided to the UE, so from UE perspective the PDU session is still associated with the original requested S-NSSAI and therefore no impact on the UE side. Since the PDU session is still associated with the original requested S-NSSAI, the anchor SMF/UPF and the IP address is not changed so service continuity is ensured. + +**NOTE 1:** From RAN perspective, the PDU session is only associated with single S-NSSAI + +**Editor's note:** In this solution PDU session can be associated with different S-NSSAIs in UE and RAN node. The impact on the RAN is FFS. + +**NOTE 2:** It is not necessary that the additional S-NSSAI is part of Allowed NSSAI. + +For PDU Session with home routed scenario, the AMF may determine to associate this PDU session with additional S-NSSAI in the VPLMN. The AMF doesn't update the slice mapping between VPLMN and HPLMN in the UE. + +**NOTE 3:** When the AMF detects that the original requested S-NSSAI is not congested, the AMF may remove the additional S-NSSAI associated with the PDU session. + +During PDU Session establishment procedure, if the requested S-NSSAI is congested in this area, the AMF may also determine to associate both the requested S-NSSAI and the additional S-NSSAI with the PDU session. + +### 6.1.3 Procedures + +#### 6.1.3.1 Additional S-NSSAI handling during Handover Procedure + +The target AMF is configured that both S-NSSAI#1 and S-NSSAI#2 are associated with one network slice instance. + +![Sequence diagram illustrating the Additional S-NSSAI handling during Handover Procedure. The diagram shows interactions between UE, S-RAN, T-RAN, Source AMF, Target AMF, SMF, and UPF. The steps are: 1. PDU Session Establishment procedure with S-NSSAI#1; 2. Handover Required; 3. Create UE context; 4. Slice Remapping; 5. Nsmf_PDUSession_UpdateSMContext Request; 6. N4 Session Modification; 7. Nsmf_PDUSession_UpdateSMContext Response; 8. Handover Request; 9. Remaining steps in Inter NG-RAN node N2 based handover procedure.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-RAN + participant T-RAN + participant Source AMF + participant Target AMF + participant SMF + participant UPF + + Note over S-RAN, SMF: 1. PDU Session Establishment procedure with S-NSSAI#1 + S-RAN->>Source AMF: 2. Handover Required + Source AMF->>Target AMF: 3. Create UE context + Note over Target AMF: 4. Slice Remapping + Target AMF->>SMF: 5. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 6. N4 Session Modification + SMF->>Target AMF: 7. Nsmf_PDUSession_UpdateSMContext Response + Target AMF->>T-RAN: 8. Handover Request + Note over S-RAN, SMF: 9. Remaining steps in Inter NG-RAN node N2 based handover procedure + +``` + +Sequence diagram illustrating the Additional S-NSSAI handling during Handover Procedure. The diagram shows interactions between UE, S-RAN, T-RAN, Source AMF, Target AMF, SMF, and UPF. The steps are: 1. PDU Session Establishment procedure with S-NSSAI#1; 2. Handover Required; 3. Create UE context; 4. Slice Remapping; 5. Nsmf\_PDUSession\_UpdateSMContext Request; 6. N4 Session Modification; 7. Nsmf\_PDUSession\_UpdateSMContext Response; 8. Handover Request; 9. Remaining steps in Inter NG-RAN node N2 based handover procedure. + +Figure 6.1.3.1-1: Additional S-NSSAI handling during Handover Procedure + +1. The UE establishes a PDU session with the requested S-NSSAI#1 via S-RAN. +2. S-RAN performs a UE measurement and determines that a handover to the T-RAN is needed. The S-RAN sends a handover required message (T-RAN node information, a source to target transparent container, an SM N2 information list, PDU session ID(s)) to the AMF via the N2 interface. +3. The source AMF selects a target AMF based on the T-RAN node information and create UE context in the target AMF. +4. If the target AMF is notified that the S-NSSAI#1 is under congestion in the CN and the service continuity of the PDU session is required, the target AMF checks if the S-NSSAI#2 is supported in the T-RAN node. If it is supported the target AMF determines to associate the PDU session with additional S-NSSAI#2. +5. The target AMF sends an Nsmf\_PDUSession\_UpdateSMContext request message (the PDU session ID, the S-NSSAI#2, N2 SM Information) to the SMF. The SMF associates the S-NSSAI#2 with the PDU session. +6. The SMF may modify the N4 session to update the N4 session information in the UPF. +7. The SMF sends a Nsmf\_PDUSession\_UpdateSMContext response message (PDU session ID, N2 SM Information) to the target AMF. The N2 SM information includes the S-NSSAI#2 received from the AMF. +8. The rest steps in N2 based handover procedure are performed. + +#### 6.1.3.2 Additional S-NSSAI handling during PDU Session Establishment Procedure + +The target AMF is configured that both S-NSSAI#1 and S-NSSAI#2 are associated with one network slice instance. + +![Sequence diagram showing the additional S-NSSAI handling during PDU Session establishment procedure. The diagram involves five entities: UE, RAN, AMF, SMF, and UPF. The sequence of messages is: 1. PDU Session Establishment Request (UE to AMF); 2. Slice Remapping (AMF internal); 3. Nsmf_PDUSession_CreateSMContext Request (AMF to SMF); 4. N4 Session Establishment (SMF to UPF); 5. Nsmf_PDUSession_CreateSMContext Response (SMF to AMF); 6. Namf_Communication_N1N2MessageTransfer (SMF to AMF); 7. N2 Message (AMF to RAN); 8. Remaining steps in PDU Session Establishment procedure (RAN to AMF).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF + Note right of AMF: 2. Slice Remapping + UE->>AMF: 1. PDU Session Establishment Request + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request + SMF->>UPF: 4. N4 Session Establishment + SMF->>AMF: 5. Nsmf_PDUSession_CreateSMContext Response + SMF->>AMF: 6. Namf_Communication_N1N2MessageTransfer + AMF->>RAN: 7. N2 Message + RAN->>AMF: 8. Remaining steps in PDU Session Establishment procedure + +``` + +Sequence diagram showing the additional S-NSSAI handling during PDU Session establishment procedure. The diagram involves five entities: UE, RAN, AMF, SMF, and UPF. The sequence of messages is: 1. PDU Session Establishment Request (UE to AMF); 2. Slice Remapping (AMF internal); 3. Nsmf\_PDUSession\_CreateSMContext Request (AMF to SMF); 4. N4 Session Establishment (SMF to UPF); 5. Nsmf\_PDUSession\_CreateSMContext Response (SMF to AMF); 6. Namf\_Communication\_N1N2MessageTransfer (SMF to AMF); 7. N2 Message (AMF to RAN); 8. Remaining steps in PDU Session Establishment procedure (RAN to AMF). + +**Figure 6.1.3.2-1: Additional S-NSSAI handling during PDU Session establishment Procedure** + +1. The UE establishes a PDU session with the requested S-NSSAI#1 via RAN. +2. The AMF is notified that the S-NSSAI#1 is under congestion in the CN, the AMF checks if the S-NSSAI#2 is supported in the RAN node. If it is supported the AMF determines to associate the PDU session with additional S-NSSAI#2. +3. The AMF sends an Nsmf\_PDUSession\_CreateSMContext request message (the PDU session ID, requested S-NSSAI#1, S-NSSAI#2, SM NAS container) to the SMF. The SMF determines that the PDU session is associated with both S-NSSAI#1 and S-NSSAI#2. +4. The SMF creates the N4 session to update the N4 session information in the UPF. +5. The SMF sends a Nsmf\_PDUSession\_CreateSMContext response message to AMF. +6. The SMF sends Namf\_Communication\_N1N2MessageTransfer(PDU session ID, N2 SM Information) to the AMF. The N2 SM information includes the S-NSSAI#2 received from the AMF. +7. The AMF sends the N2 message to the RAN node, including the N2 SM information. +8. The rest steps in PDU Session establishment procedure are performed. + +## 6.1.4 Impacts on existing entities and interfaces + +AMF: + +- support two S-NSSAIs associated with one PDU session for non roaming case + +SMF/I-SMF: + +- support two S-NSSAIs associated with one PDU session for non roaming case + +UPF: + +- support two S-NSSAIs associated with one PDU session for non roaming case + +NG-RAN: (TBD) + +UE: None + +## 6.2 Solution #2: Slice Re-mapping Capabilities for Network Slice Service Continuity + +### 6.2.1 Introduction + +The solution addresses the Key Issue #1: Support of network slice service continuity. + +### 6.2.2 Functional Description + +The solution provides a mechanism to determine a re-mapped slice for a network slice that requires slice re-mapping due to an overload, planned maintenance, etc. and to move ongoing PDU sessions to the re-mapped slice. The solution can be applied to the scenario 1b) and 1c). + +### 6.2.3 Procedures + +#### 6.2.3.1 General + +During a registration procedure, AMF selects PCF that supports slice re-mapping and obtain an information for slice re-mapping. A call flow for slice re-mapping policy at registration procedure is shown in Figure 6.2.3.2-1. + +When a network slice that requires slice re-mapping occurs, AMF obtain a remapped S-NSSAI for each PDU session that is associated with a network slice that requires slice re-mapping either via PCF or via AMF itself. Once a re-mapped slice is selected for the network slice that requires slice re-mapping, for each old PDU session associated with the network slice that requires slice re-mapping, AMF may interact with SMF to change the S-NSSAI of the PDU session. A call flow for changing S-NSSAI of PDU session is shown in Figure 6.2.3.3-1. + +#### 6.2.3.2 Registration + +![Sequence diagram showing the slice re-mapping policy at registration procedure. The diagram involves five entities: UE, AMF, AUSF, PCF, and UDM. The sequence of messages is: 1. Registration Request from UE to AMF; 2. Interaction with AUSF and UDM (represented by a large block); 3. PCF selection (represented by a block within the interaction); 4. Npcf_AMPolicyControl_Create Request from AMF to PCF; 5. Npcf_AMPolicyControl_Create Response from PCF to AMF; 6. Rest of the UE registration procedure (represented by a large block).](c0e369274e53b2e5364666be6f786c7a_img.jpg) + +``` +sequenceDiagram + participant UE + participant AMF + participant AUSF + participant PCF + participant UDM + + Note right of AMF: 2. Interaction with AUSF and UDM + Note right of AMF: 3. PCF selection + + UE->>AMF: 1. Registration Request + AMF->>PCF: 4. Npcf_AMPolicyControl_Create Request + PCF-->>AMF: 5. Npcf_AMPolicyControl_Create Response + + Note right of AMF: 6. Rest of the UE registration procedure +``` + +Sequence diagram showing the slice re-mapping policy at registration procedure. The diagram involves five entities: UE, AMF, AUSF, PCF, and UDM. The sequence of messages is: 1. Registration Request from UE to AMF; 2. Interaction with AUSF and UDM (represented by a large block); 3. PCF selection (represented by a block within the interaction); 4. Npcf\_AMPolicyControl\_Create Request from AMF to PCF; 5. Npcf\_AMPolicyControl\_Create Response from PCF to AMF; 6. Rest of the UE registration procedure (represented by a large block). + +**Figure 6.2.3.2-1: Slice re-mapping policy at registration procedure** + +1. A UE triggers registration with the network. +2. The AMF may interact with AUSF and UDM according to clause 4.2.2.2.2 in TS 23.502 [5]. + +3. If the AMF decides to perform PCF discovery and selection and if the AMF supports slice re-mapping, the AMF may select PCF that supports slice re-mapping by utilizing NRF or local configuration. +4. The AMF may request PCF to obtain AM policy. +5. The PCF provides a policy including a PCR trigger of slice re-mapping required that instructs the AMF to interact with PCF when a network slice that requires slice re-mapping occurs to AMF. +6. In the UE policy association procedure, the PCF provides a PCR trigger of change of re-mapped slice that instructs the AMF to interact with PCF when a new network slice for a slice that requires slice re-mapping is selected. +7. A rest of the UE registration procedure according to clause 4.2.2.2.2 in TS 23.502 [5]. + +### 6.2.3.3 Change of S-NSSAI of a PDU Session + +PCF is configured with information that pairs of network slices can be used as an alternative for each other (both slices support the same services with the same DNNs and same DNAIs pointing to the same DNs, hosting the same services, etc.). + +![Sequence diagram illustrating the Change of S-NSSAI of a PDU Session. The diagram shows four lifelines: UE, AMF, SMF, and PCF. Step 1: AMF determines that a network slice that requires slice re-mapping occurs. Step 2: AMF sends Npcf_AMPolicyControl_Update Request to PCF. Step 3: PCF sends Npcf_AMPolicyControl_Update Response to AMF. Step 4: AMF triggers change of S-NSSAI of PDU session.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant PCF + Note right of AMF: 1. Determines that a network slice that requires slice re-mapping occurs + AMF->>PCF: 2. Npcf_AMPolicyControl_Update Request + PCF-->>AMF: 3. Npcf_AMPolicyControl_Update Response + Note right of AMF: 4. AMF-triggered change of S-NSSAI of PDU session + +``` + +Sequence diagram illustrating the Change of S-NSSAI of a PDU Session. The diagram shows four lifelines: UE, AMF, SMF, and PCF. Step 1: AMF determines that a network slice that requires slice re-mapping occurs. Step 2: AMF sends Npcf\_AMPolicyControl\_Update Request to PCF. Step 3: PCF sends Npcf\_AMPolicyControl\_Update Response to AMF. Step 4: AMF triggers change of S-NSSAI of PDU session. + +Figure 6.2.3.3-1: Change of S-NSSAI of a PDU Session + +1. The AMF determines that a network slice that requires slice re-mapping occurs. +2. From AMF to PCF: AM Policy Association ID, S-NSSAI that requires slice re-mapping. + +If the AMF has received a PCR trigger that instructs the AMF to interact with PCF when a network slice that requires slice re-mapping occurs and the AMF determined in step 1 that a network slice that requires slice re-mapping occurs, the AMF triggers AM Policy Association modification procedure to PCF. + +3. From PCF to AMF: AM Policy Association ID, selected S-NSSAI. + +The PCF selects re-mapped S-NSSAI and provides it to the AMF based on the S-NSSAI that requires slice re-mapping received from AMF in step 2. The re-mapped S-NSSAI is selected within Allowed NSSAI. The AMF considers the selected S-NSSAI as a new slice for the S-NSSAI that requires slice re-mapping. + +4. From AMF to PCF: UE Policy Association ID, S-NSSAI that requires slice re-mapping, selected S-NSSAI. + +If the AMF has received a PCR trigger of a change of re-mapped slice and the AMF determined a new selected S-NSSAI for the S-NSSAI that requires slice re-mapping, the AMF triggers UE Policy Association modification procedure to PCF. The AMF includes S-NSSAI that requires slice re-mapping and selected S-NSSAI for the S-NSSAI that requires slice re-mapping in the message towards PCF. + +The PCF may update URSP rules and triggers UE Configuration Update procedure based on the S-NSSAI that requires slice re-mapping and the selected re-mapped S-NSSAI. In roaming scenario, the AMF sends the + +message towards H-PCF via V-PCF and the message may include S-NSSAI mapped to HPLMN. On receiving the message from AMF, the H-PCF may update URSP rules and triggers UE Configuration Update procedure. + +5. The PCF sends the response message to the AMF. +6. For each old PDU session and associated with the network slice that requires slice re-mapping, AMF may trigger a change of the slice of the old PDU session to the selected re-mapped S-NSSAI received in step 3 according to the procedure shown in clause 6.2.3.4. + +### 6.2.3.4 AMF-triggered PDU Session Modification to change of S-NSSAI of PDU Session + +![Sequence diagram for AMF-triggered PDU session modification. Lifelines: UE, (R)AN, AMF, UPF1, UPF2, SMF1, SMF2. Step 1: AMF sends Nsmf_PDUSession_UpdateSMContext Request to SMF1. Step 1b: SMF1 sends Nsmf_PDUSession_UpdateSMContext Response to AMF. Step 2: A block labeled 'Steps 1 to 6 as in fig 4.3.5.2-1 in Clause 4.3.2.4, TS 23.502 [5]' spans across all lifelines.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF1 + participant UPF2 + participant SMF1 + participant SMF2 + + AMF->>SMF1: 1a. Nsmf_PDUSession_UpdateSMContext Request + SMF1-->>AMF: 1b. Nsmf_PDUSession_UpdateSMContext Response + Note over UE, SMF2: 2. Steps 1 to 6 as in fig 4.3.5.2-1 in Clause 4.3.2.4, TS 23.502 [5] + +``` + +Sequence diagram for AMF-triggered PDU session modification. Lifelines: UE, (R)AN, AMF, UPF1, UPF2, SMF1, SMF2. Step 1: AMF sends Nsmf\_PDUSession\_UpdateSMContext Request to SMF1. Step 1b: SMF1 sends Nsmf\_PDUSession\_UpdateSMContext Response to AMF. Step 2: A block labeled 'Steps 1 to 6 as in fig 4.3.5.2-1 in Clause 4.3.2.4, TS 23.502 [5]' spans across all lifelines. + +**Figure 6.2.3.4-1: AMF-triggered PDU session modification** + +1. From AMF to SMF: SM Context ID, selected S-NSSAI + +The AMF triggers AMF-initiated PDU session modification procedure to change the S-NSSAI of the PDU session with the selected S-NSSAI. In home-routed scenario, corresponding HPLMN S-NSSAI for the selected S-NSSAI is provided to H-SMF. + +2. From SMF to AMF: Result Indication + +For the SSC mode 1 PDU Session, the result indication may indicate failure if the SMF and the UPF for the PDU Session does not support the selected S-NSSAI. + +3. Steps 1 to 6 as in Figure 4.3.5.2-1 in clause 4.3.5.2 of TS 23.502 [5] are performed with the following differences: + - In step 1, if the SMF has received the Nsmf\_PDUSession\_SMContextUpdate request message (SM Context ID, selected S-NSSAI) from the AMF and the selected S-NSSAI is different from the S-NSSAI of the PDU session for the SM Context ID, the SMF decides to change the S-NSSAI of the PDU session to the selected S-NSSAI. + - In step 2, if the SMF invokes the Namf\_Communication\_N1N2MessageTransfer due to the change of the S-NSSAI. If the SMF determines to change the S-NSSAI without UPF relocation (e.g. for the PDU session of SSC mode 1), Cause indicates that a change of S-NSSAI of the PDU session is required without UPF relocation and the selected S-NSSAI received from the AMF is included in the PDU Session Modification Command. If the SMF determines to change the S-NSSAI with the UPF relocation, Cause indicates that a PDU Session re-establishment to the same DN is required and the selected S-NSSAI is included in the PDU Session Modification Command. + - In step 3d, if the SMF1 has set Cause to the change of S-NSSAI of the PDU session is required in step 2 in the PDU session Modification Command and the SMF received the acknowledgement from the UE in step 3c, the SMF1 includes the selected S-NSSAI in the N4 Session Modification request towards the UPF. The UPF changes the S-NSSAI of the N4 session to the selected S-NSSAI in the N4 Session Modification request and sends response message to SMF1. + +- In step 4, if the UE receives PDU Session Modification Command that includes the Cause indicating the change of S-NSSAI of the PDU session is required, the UE changes the S-NSSAI of the corresponding PDU session to the selected S-NSSAI in the PDU Session Modification Command. +- In step 4, if the UE receives PDU Session Modification Command that includes the Cause indicating the same DN and the S-NSSAI, the UE may decide to initiate the PDU Session Establishment procedure described in clause 4.3.2.2 of TS 23.502 [5], to the same DN with the new S-NSSAI the following differences: + - In step 1 of clause 4.3.2.2.1, the new PDU Session ID is included as PDU Session ID in the NAS request message and the Old PDU Session ID which indicates the existing PDU Session to be released is also provided to AMF in the NAS request message. + +## 6.2.4 Impacts on services, entities and interfaces + +AMF: + +- Support slice re-mapping. +- send a message to SMF to trigger a change of S-NSSAI. + +SMF: + +- trigger SSC mode operation with a S-NSSAI received from AMF as a new PDU session. + +NRF: + +- Support discovery of PCF that support slice re-mapping. + +PCF: + +- Support slice re-mapping. + +UE: + +- Handle the PDU session modification command message that includes S-NSSAI. + +## 6.3 Solution #3: Support of Network Slice Service continuity using a SSC mode 3 type of Service continuity + +### 6.3.1 Introduction + +This solution addresses KI#1 scenarios of mobility. + +### 6.3.2 Functional Description + +This solution, for generality (as this solution can apply also without any mobility in a totally AMF initiated approach), considers a UE which is in CM-CONNECTED mode and arrives at an area where it needs to be handed over to a cell outside the current RA where a PDU session in a certain slice cannot continue as the slice is no longer available for any of the reasons documented in the KI#1. Specifically, the RAN is based on local information detecting the target RAN node cannot serve the current slice and it is configured with a valid replacement so it can continue the sessions associated with the replaced slice temporality till they are replaced by session with the correct slice. This may be due to e.g. the AMFs in target RAN node region not supporting the S-NSSAI any more for e.g. maintenance or other causes so they provide an AMF configuration update to tell the RAN a S-NSSAI no longer is supported and a replacement is defined for it. + +This solution relies on using SSC mode 3 type of service continuity in a network-controlled manner across network slices (SSC3 only operates for same DNN and S-NSSAI today so strictly speaking this is not the existing SSC mode 3). The next clause provides the necessary details. + +### 6.3.3 Procedures + +The call flow below in figure 6.3.3-1 proposes using SSC mode 3 type of mobility across network slices to provide the service continuity solution. A single NG-RAN node may also be involved, two NG-RAN nodes are shown for + +generality and only the Xn Handover case is shown but this can apply also to NG Handover. Also, more than one AMF can be involved but for simplicity only one is considered (if more than one is involved there is an extra AMF reallocation step to be added where the context is transferred alongside the slice remapping information). + +![Sequence diagram illustrating service continuity upon slice change. Lifelines: UE, Source NG-RAN node 1, Target NG-RAN node 2, AMF, SMF 10, SMF 11. The sequence shows registration, ongoing session, handover request/complete, PSR, configuration updates, and session establishment/release.](e354b57563dae469c00b412b2abdf765_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN node 1 + participant Target NG-RAN node 2 + participant AMF + participant SMF 10 + participant SMF 11 + + Note over UE, SMF 10: 1) UE registers with slice 10 and indicates support of the new SSC 3- like mobility across slices + Note over UE, SMF 10: 2. UE has ongoing PDU session 1 of slice 10 and SMF indicated support of SSC3-like type of Mobility across Slices + + Source NG-RAN node 1->>Target NG-RAN node 2: 3. HO request (pdu session 1) + Target NG-RAN node 2-->>Source NG-RAN node 1: Handover command (PDU session 1 temporary accepted) + Source NG-RAN node 1->>UE: Handover complete + Target NG-RAN node 2->>AMF: 4. PSR (end slice 10 sessions, replace with new slice 11 sessions) + AMF->>UE: 5. UE configuration Update Command (Allowed NSSAI (slices 10, 11), Configured NSSAI ) + UE-->>AMF: 5. UE configuration Update Complete + AMF->>SMF 10: 6. update (end slice 10, replace with new slice 11) + Note right of SMF 10: SSC mode 3 type of mobility Timer expiry + AMF->>UE: 7. NAS PDU Session Modification Command (end slice 10, replace with new slice 11) + UE->>SMF 11: 8. Establish PDU session 2 on slice 11 + SMF 11-->>UE: + Target NG-RAN node 2->>SMF 10: 9. Release pdu session 1 of slice 10 + SMF 10-->>Target NG-RAN node 2: + AMF->>UE: 10. UE Configuration Update (new Allowed NSSAI= slice 11 only) + +``` + +Sequence diagram illustrating service continuity upon slice change. Lifelines: UE, Source NG-RAN node 1, Target NG-RAN node 2, AMF, SMF 10, SMF 11. The sequence shows registration, ongoing session, handover request/complete, PSR, configuration updates, and session establishment/release. + +**Figure 6.3.3-1: service continuity upon slice change** + +1. AMF has sent the UE Allowed NSSAI to the serving NG-RAN node as part of the registration and the UE per existing procedures. The UE had indicated to the AMF it supports this new feature in the registration request. +2. UE has ongoing PDU session 1 of slice 10 where the SMF has indicated to the AMF is support this SSC mode 3 like type of behaviour across slices. +3. Source NG-RAN triggers Handover to target NG-RAN. The target NG-RAN node 2 informs during the HO procedure the source NG-RAN node 1 that it accepts the PDU session 1 of slice 10 temporarily due to slice remapping action which it has been configured with for slice 10. It also indicates the new slice 11 for the PDU session. It is assumed that the AMF provided this information to impacted NG-RAN nodes by indication of the alternative slice is replacing the overloaded slice by a NG-AP AMF Configuration Update procedure. +4. At handover completion, the target NG-RAN indicates to AMF in Path Switch Request that PDU session 1 of slice 10 needs to be terminated and a new PDU session is to be setup with slice 11. + +5. The AMF provides a new Allowed NSSAI including both S-NSSAI 10 and S-NSSAI 11 in the UE Configuration Update command and may include S-NSSAI 11 in the Configured NSSAI as temporary S-NSSAI replacing S-NSSAI 10. Because the AMF has received (end slice 10) at step 4, the AMF still includes the slice 10 in the Allowed NSSAI towards the UE at this step (the slice is indeed still temporarily available until it receives from SMF notification of the final release of PDU session 1 of slice 10 at step 9). This is just a temporary allowed NSSAI that will be soon replaced and may include two S-NSSAIs in the serving PLMN supporting same HPLMN S-NSSAI exceptionally. The Allowed NSSAI information element is indicating that a S-NSSAI is Allowed to replace another S-NSSAI in the Allowed S-NSSAI. In roaming case, this additional allowed S-NSSAI maps to the same HPLMN slice(s) (temporarily). This should be possible as what slice maps to HPLMN slice(s) is a VPLMN decision (whether permanently or temporarily). The Configured NSSAI update may not be required if SA2 will specify this is not updated for this case and the UE shall ignore inconsistencies. The AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. +6. AMF sends an Update message to SMF indicating end of PDU session 1 of slice 10 and remapping to slice 11. The SMF triggers step 7 as the UE has indicated SSC mode 3. +7. In reaction to step 5, the SMF triggers towards the UE the NAS PDU Session Modification Command (Cause, PCO (PDU Session Address Lifetime value), end slice 10, new slice 11) to invoke SSC mode 3 type of behaviour. The (end slice 10, new 11) may be included towards the UE to prompt the UE to setup the new PDU session 2 with slice 11. By this feature the possibility that SSC mode 3 type of behaviour applies across slices is introduced even if the UE had not indicated the existing SSC mode 3 when the PDU session was established. +8. The UE triggers the establishment of PDU session 2 with slice 11 according to SSC mode 3 procedure as per existing procedures described in clause 4.3.2.2.1 of TS 23.502 [5]. The S-NSSAI requested is S-NSSAI 11, the DNN is the same as used for the existing PDU session. +9. At the expiry of SSC mode 3 timer, the SMF triggers the release of the PDU session 1 of slice 10 according to SSC mode 3 procedures (existing procedures described in clause 4.3.2.2.1 of TS 23.502 [5]). +10. Upon notification from the SMF that PDU session of no longer supported slice 10 has been released, the AMF sends a final the UCU (UE Configuration Update) message in order to update the Allowed NSSAI towards the NG-RAN and the UE. In this example, the new Allowed NSSAI is slice 11. When the slice 10 can be resumed the inverse procedure can take place by swapping slice 11 with slice 10 using the same method. + +### 6.3.4 Impacts on services, entities and interfaces + +The solution has the following impacts: + +NG-RAN node: + +- configuration to perform slice remapping for certain slices and related behaviour as per above procedure. + +AMF: + +- temporarily allow slices while SSC3 type of behaviour completes for the PDU session and do UE configuration update to provide the final allowed NSSAI when the new PDU session is up and running and old PDU session leg released. +- The AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. + +UE: + +- performs SSC mode 3 type of behaviour with the slice indicated to replace the ongoing slice when requested by step 7. + +## 6.4 Solution #4: PDU Session on compatible network slice + +### 6.4.1 Introduction + +This solution addresses the bellow requirements from Key Issue #1: Support of Network Slice Service continuity. + +- 1) No mobility scenario: + +Scenario 1b): network slice or network slice instance is overloaded. + +## 6.4.2 Functional description + +This solution allows for a PDU Session establishment on a compatible network slice if the network slice on which the PDU Session is initially required is not available or is overloaded. The assumption in this solution is that an Application in the UE may be allowed to get a service from more than one network slice as per the network slice selection criteria (NSSP) within the URSP rules in the UE. In such a case the UE may include a compatible S-NSSAI as an extra parameter in the PDU Session Establishment Request message along with the S-NSSAI on which the PDU Session is required and the PDU Session establishment procedure can continue on the compatible S-NSSAI in case the initially required S-NSSAI is not available or is overloaded. + +## 6.4.3 Procedures + +![Sequence diagram showing PDU Session establishment on a compatible network slice. The diagram involves three entities: UE, AMF, and SMF. The sequence of messages is: 1) UE sends a UL NAS TRANSPORT message (PDU Session Establishment Request) to AMF with (PDU Session ID, DNN, S-NSSAI, compatible S-NSSAI). 2) AMF checks if the requested S-NSSAI is overloaded or not available; if so, it continues with the PDU Session establishment on the compatible S-NSSAI. 3) AMF sends an Nsmf_PDUSession_CreateSMContext Request to SMF with (PDU Session ID, DNN, S-NSSAI=compatible S-NSSAI). 4) The process continues with PDU Session Establishment on the compatible S-NSSAI as per TS23.502, clause 4.3.2.2.1.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + Note right of AMF: 2). If the requested S-NSSAI is overloaded or not available, the AMF continues with the PDU Session establishment on the compatible S-NSSAI instead of the requested S-NSSAI. + UE->>AMF: 1). UL NAS TRANSPORT message (PDU Session Establishment Request (PDU Session ID, DNN, S-NSSAI, compatible S-NSSAI)) + AMF->>SMF: 3). Nsmf_PDUSession_CreateSMContext Request (PDU Session ID, DNN, S-NSSAI=compatible S-NSSAI) + Note left of UE: 4). Continue PDU Session Establishment on the compatible S-NSSAI as per TS23.502, clause 4.3.2.2.1 + +``` + +Sequence diagram showing PDU Session establishment on a compatible network slice. The diagram involves three entities: UE, AMF, and SMF. The sequence of messages is: 1) UE sends a UL NAS TRANSPORT message (PDU Session Establishment Request) to AMF with (PDU Session ID, DNN, S-NSSAI, compatible S-NSSAI). 2) AMF checks if the requested S-NSSAI is overloaded or not available; if so, it continues with the PDU Session establishment on the compatible S-NSSAI. 3) AMF sends an Nsmf\_PDUSession\_CreateSMContext Request to SMF with (PDU Session ID, DNN, S-NSSAI=compatible S-NSSAI). 4) The process continues with PDU Session Establishment on the compatible S-NSSAI as per TS23.502, clause 4.3.2.2.1. + +Figure 6.4.3-1: PDU Session on compatible network slice + +1. When an Application in the UE requires service, the UE triggers PDU Session Establishment Request to the AMF in which the UE includes the S-NSSAI and the DNN on which the service is available based on the S-NSSAI selection and DNN selection criteria within the URSP rules in the UE. Optionally, the UE may include in the PDU Session Establishment Request a compatible S-NSSAI, if available. The compatible S-NSSAI is an alternative S-NSSAI from the network slice selection criteria within the URSP if the network slice selection criteria within the URSP rules in the UE allows the Application requiring service to use more than one S-NSSAI. The UE includes a compatible S-NSSAI in the PDU Session Establishment Request if one is available in the network slice selection criteria within the URSP and it is in the Allowed NSSAI list for the UE. +2. If the S-NSSAI on which a PDU Session is required by the UE is overloaded or not available and the UE has included a compatible S-NSSAI in the PDU Session Establishment Request message, the AMF selects an SMF based on the compatible S-NSSAI and the AMF continues the PDU Sessions Establishment procedure on the compatible S-NSSAI instead of the initially requested S-NSSAI. +3. The AMF sends Nsmf\_PDUSession\_CreateSMContext Request message to the SMF in which the AMF includes the compatible S-NSSAI received by the UE. +4. Continue PDU Session Establishment on the compatible S-NSSAI according to clause 4.3.2.2.1 of TS 23.502 [5]. The SMF may notify the UE that the PDU Session is established on the compatible S-NSSAI and the AMF may indicate to the UE the reason for the network slice switch to a compatible S-NSSAI. In the PDU Session Establishment Accept, the SMF may provide back off timer for the original S-NSSAI so that the UE cannot request a PDU Session according to the existing URSP rule until the back off timer is expired. + +After PDU Session is established, the AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. + +## 6.4.4 Impacts on services, entities and interfaces + +UE: + +- new compatible S-NSSAI parameter in the PDU Session Establishment Request. + +AMF: + +- PDU Session switch to a compatible S-NSSAI. +- new cause to indicate the network slice switch to a compatible S-NSSAI. +- After PDU Session is established, the AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. + +## 6.5 Solution #5: PDU session handover to a target CN with an alternative S-NSSAI support + +### 6.5.1 Introduction + +This solution addresses the bellow requirements from Key Issue #1: Support of Network Slice Service continuity. + +#### 2) Inter RA Mobility scenario: + +Scenario 2d): network slice or network slice instance is overloaded in the target CN. + +### 6.5.2 Functional description + +This solution allows for a PDU Session handover to an alternative network slice when the current network slice is not supported by the target CN or it is overloaded in the target CN. At PDU Session establishment the UE may include in the PDU Session Establishment Request an alternative S-NSSAI, if available. The alternative S-NSSAI is another S-NSSAI from the network slice selection criteria within the URSP rules in the UE in case the URSP rules allow the Application requiring the service to use more than one S-NSSAI. Then this alternative S-NSSAI is included by the UE in the PDU Session Establishment Request and is stored in the UE context within the AMF and used for PDU Session handover to this alternative S-NSSAI if the current S-NSSAI is not supported in the target CN or the current S-NSSAI is overloaded in the target CN. + +### 6.5.3 Procedures + +![Sequence diagram illustrating the PDU session handover to a target CN with an alternative S-NSSAI support. The diagram shows interactions between UE, S-RAN, T-RAN, S-AMF, T-AMF, and SMF. The process involves NAS message exchange, S-AMF storing the alternative S-NSSAI, continuing PDU session establishment, triggering a handover request, N2 handover to T-RAN and T-AMF, UE registration with T-AMF, PDU session modification, and finally a PDU session modification command to the UE.](9a159e2112eac7be06bdb97e84a0c49a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-RAN + participant T-RAN + participant S-AMF + participant T-AMF + participant SMF + + Note right of S-AMF: 2. S-AMF stores the alternative S-NSSAI in the UE context + Note over UE, SMF: 3. Continue with the PDU Session Establishment on S-NSSAI as per TS23.502 + Note left of S-RAN: 4. S-RAN triggers Handover request. + Note over S-RAN, T-AMF: 5. N2 Handover to a T-RAN and T-AMF supporting the alternative S-NSSAI as the current S-NSSAI is not available or overloaded in the target CN. During the N2 handover the alternative S-NSSAI is passed to the T-AMF + Note over UE, SMF: 6. UE registration with the T-AMF as per TS23.502. The alternative S-NSSAI is an allowed S-NSSAI in T-AMF. + Note over T-RAN, SMF: 7. PDU session modification on the alternative S-NSSAI per TS23.502 + +``` + +Sequence diagram illustrating the PDU session handover to a target CN with an alternative S-NSSAI support. The diagram shows interactions between UE, S-RAN, T-RAN, S-AMF, T-AMF, and SMF. The process involves NAS message exchange, S-AMF storing the alternative S-NSSAI, continuing PDU session establishment, triggering a handover request, N2 handover to T-RAN and T-AMF, UE registration with T-AMF, PDU session modification, and finally a PDU session modification command to the UE. + +**Figure 6.5.3-1: PDU session handover to a target CN with an alternative S-NSSAI support** + +1. An Application in the UE requires service on S-NSSAI. The UE initiates PDU Session Establishment procedure on that S-NSSAI to the S-AMF. Optionally, the UE may include in the NAS message an alternative S-NSSAI, if + +available. The alternative S-NSSAI is another S-NSSAI from the network slice selection criteria within the URSP if the URSP rules allow the Application requiring the service to use more than one S-NSSAI. The UE includes an alternative S-NSSAI in the NAS message if one is available in the network slice selection criteria within the URSP. + +2. The S-AMF may perform some further checks for the eligibility of the alternative S-NSSAI(s) received from the UE before the S-AMF stores the alternative S-NSSAI in the UE context. +3. Continue and complete the PDU Session establishment procedure on S-NSSAI according to clause 4.3.2.2.1 of TS 23.502 [5]. +4. At some stage the S-RAN triggers handover request to the S-AMF. +5. The S-RAN selects a T-RAN supporting the current S-NSSAI and possibly supporting the alternative S-NSSAI if provided by the UE. The S-AMF proceeds with the N2 handover procedure to T-RAN and T-AMF supporting the current S-NSSAI and/or the alternative S-NSSAI. +6. UE registration with the T-AMF. The current and the alternative S-NSSAI received from the S-AMF during the N2 handover is supported and allowed in the T-AMF after the UE registration. +7. If at step 5 the UE did handover to a T-RAN supporting the current S-NSSAI and the alternative S-NSSAI however, the T-AMF is overloaded for the current S-NSSAI, then the PDU Session switches to the alternative S-NSSAI via PDU Session modification to the alternative S-NSSAI procedure as per clause 4.3.3.2.1 of TS 23.502 [5]. The T-AMF may select another SMF if the PDU Session switches to an alternative S-NSSAI. +8. The T-RAN forwards the PDU Session Modification Command received from the T-AMF to the UE with the alternative S-NSSAI included in case of PDU Session switch to an alternative S-NSSAI. + +After HO, the AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. + +#### 6.5.4 Impacts on services, entities and interfaces + +UE: + +- new alternative S-NSSAI parameter in the PDU Session Establishment Request message. + +AMF: + +- alternative S-NSSAI(s) handling. +- AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. + +### 6.6 Solution #6: Extended SoR VPLMN Slice Information transfer to UEs + +#### 6.6.1 Introduction + +This solution targets KI#2, namely the issues of: + +- "how and when the HPLMN provides the UE with information about slice availability per VPLMN"; and +- "study how and when to use the information received by the UE from the HPLMN to influence automatic PLMN selection". + +#### 6.6.2 Functional Description + +In this solution the SoR AF verifies if the Subscribed S-NSSAIs are available in the VPLMN where the UE is currently trying to register. If some of the Subscribed S-NSSAIs or all are not available, depending on operator policy, the SoR AF may provide additional information that can be sent to the UE regarding VPLMNs and/or other networks that do support the Subscribed S-NSSAIs or a subset of them (e.g. called slice-based SoR). + +The decision by the UDM to request the SoR AF to verify if slice-based SoR information is required depends on the UE capabilities to handle this additional information, the UE current location (e.g. the current serving network ID) and on the Subscribed S-NSSAIs. The slice-based SoR information contains a list of one or more VPLMNs which with available S-NSSAIs from the Subscribed S-NSSAIs or a subset of them, as per operator's policy. + +Two options are proposed for the UDM to obtain UE capabilities; a network based approach and a UE based approach. + +- In the UE based approach, the UE includes at 5GC Registration a transparent container intended for the UDM. The AMF in the VPLMN transparently sends this container to the UDM. The UDM in turn can forward the received information from the SoR AF to the UE in the Registration Response. +- In the network based approach, the UDM fetches the UE capabilities using an extended UE Parameter Update procedure. The UE includes its capabilities in the UPU acknowledgment sent to UDM via the AMF in an UL NAS TRANSPORT. + +The AMF sends the received information from the SoR AF via the UDM in a DL NAS TRANSPORT message to the UE. + +The following UE behaviour applies: + +- Initially when the UE roams to a different country, the UE selects PLMN (automatic or manual selection) according to the existing mechanism, e.g. by using "Operator controlled PLMN selector with Access Technology" list. +- If the UE wants to use an S-NSSAI which is not available in the current serving PLMN or in the current Registration Area (RA) and the UE is configured with slice-based SoR, the UE triggers network selection procedure by considering the slice-based network selection information. + +## 6.6.3 Procedures + +### 6.6.3.1 Extended SoR VPLMN Slice Information transfer to UE + +The procedure below is a high level solution to provide the slice-based SoR to the UE. + +![Sequence diagram illustrating the UE Initiated for Extended SoR Information procedure. The diagram shows interactions between the UE, AMF, UDM, and SoR AF across VPLMN and HPLMN domains.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + participant SoR AF + + Note over UE, AMF: VPLMN + Note over UDM, SoR AF: HPLMN + + Note right of AMF: 1. Trigger for UDM Interaction with SOR AF + Note right of UDM: 2. Nsoraf Get Request (VPLMN ID or SNPN ID, UE Location, Subscribed NSSAI, etc..) + Note right of SoR AF: 3. SoR AF creates the needed Information + Note right of SoR AF: 4. Nsoraf Get Response (Prioritized List of VPLMNs.) + Note right of AMF: 5. Extended SoR AF Information sent to the UE + Note left of UE: 9. UE scans the received Steering Info and adjust accordingly + +``` + +The sequence diagram illustrates the following steps: + +- The AMF in the VPLMN sends a trigger for UDM interaction with the SoR AF. +- The UDM in the HPLMN sends an Nsoraf Get Request (containing VPLMN ID or SNPN ID, UE Location, Subscribed NSSAI, etc..) to the SoR AF. +- The SoR AF creates the needed information. +- The SoR AF sends an Nsoraf Get Response (Prioritized List of VPLMNs) to the UDM. +- The AMF sends the Extended SoR AF Information to the UE. +- The UE scans the received Steering Info and adjusts accordingly. + +Sequence diagram illustrating the UE Initiated for Extended SoR Information procedure. The diagram shows interactions between the UE, AMF, UDM, and SoR AF across VPLMN and HPLMN domains. + +Figure 6.6.3.1-1: UE Initiated for Extended SoR Information + +The steps in the call flow are described briefly below: + +1. A trigger is detected in the UDM for a roaming UE to provide slice-based SoR information, e.g. the UDM is preconfigured (e.g. via the OAM or OSS based on Service Level Agreements with the roaming partners) that one or more of the UE's Subscribed S-NSSAIs are not available in specific visited country or networks (VPLMNs). The UDM may retrieve the UE capabilities to handle the slice-based SoR information. The slice-based SoR information may be either generated in the UDM or the UDM may request the SoR AF to create it. + +If the UDM can create the slice-based SoR information itself, the UDM proceeds further with step 5. + +After the UE's UPU/SoR capabilities are retrieved, they may be stored in the UDM on per IMEI basis. + +NOTE: The conclusion clause for this KI to explicitly mentions that the procedure includes the functions performed by UDM, SoR AF independently. + +2. The UDM initiates towards the SoR AF an Nsoraf\_SoR\_Get Request (VPLMN ID), SUPI of the UE, access type (see TS 29.571 [6], subscribed S-NSSAIs, UE location, UE capability to receive enhanced information). The UDM passes transparently information included in the container and relevant for the SoR AF to consider. +3. SoR AF creates slice-based SoR information taking into account the information provided by the UDM and availability of the Subscribed S-NSSAIs in the possible VPLMNs. To enable the SoR AF to create the slice-based SoR information, the SoR AF scans the possible list of VPLMNs and for each one determines the extent to which the Subscribed NSAAIs are supported. The SoR AF may then order the information as an example as shown below: + - VPLMNs supporting all the Subscribed NSSAIs in any order preferred by HPLMN. + - VPLMN supporting a subset of the Subscribed NSSAIs in any order preferred by HPLMN. + - List of additional networks supporting the Subscribed NSSAIs or Requested NSSAIs not preferred by HPLMN. + +Editor's note: Additional information to be included is FFS. + +4. SoR AF sends the slice-based SoR information to the UDM in a Nsoraf\_SoR\_Get Response. +5. UDM sends the slice-based "steering of roaming information" to the UE via the AMF. +6. UE uses the slice-based SoR info and if the Allowed NSSAI doesn't include all slices desired by the UE then the UE scans for VPLMN supporting the S-NSSAIs not in Allowed NSSAI and selects and registers accordingly. + +The two options for UDM detection of UE capabilities are described below. Both options incorporate the common aspects between them for completeness and clarity. Steps 2 to 4 and step 6 are common for both options. + +#### 6.6.3.1.1 UE Initiated capability indication + +The procedure below implements the UE initiated option to indicate the UPU/SoR capabilities. + +![Sequence diagram illustrating the UE Initiated for Extended SoR Information flow between VPLMN and HPLMN entities.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + participant SoAR_AF as SoAR AF + + Note left of UE: VPLMN + Note right of SoAR_AF: HPLMN + + UE->>AMF: 1. Registration Request (Requested NSSAI, Transparent Container,..) + AMF->>UDM: 2. Nudm_SDM_UECM_Reg (Container, ..) +Nudm_Get_SDM (SUPI, AMF Data,..) + Note right of UDM: 3. UDM interacts with SoR AF to fetch extended Information based on UE capabilities + UDM->>SoAR_AF: 4. Nsoraf Get Request (VPLMN ID, UE Location, Subscribed NSSAI, etc..) + Note right of SoAR_AF: 5. SoR AF creates the needed Information + SoAR_AF->>UDM: 6. Nsoraf Get Response (Prioritized List of VPLMNs) + UDM->>AMF: 7. Nudm_Get Responses (Extended SoR Information sent within AMF Mobility subscription Data,..) + AMF->>UE: 8. Registration Response (Extended SoR Info,..) + Note left of UE: 9. UE scans the received Steering Info and adjust accordingly + +``` + +Sequence diagram illustrating the UE Initiated for Extended SoR Information flow between VPLMN and HPLMN entities. + +**Figure 6.6.3.1.1-1: UE Initiated for Extended SoR Information** + +The steps in the call flow are described briefly below: + +1. While roaming, the UE includes a new transparent container in a 5GC Registration Request, when UE performs Initial Registration or when the UE wants HPLMN to be aware of UE changes e.g. UE capability changes or UE requests new network slices. This new container is an indication that the UE wants the UDM to provide the UE with information relevant to Subscribed/Requested NSSAIs in the current VPLMN as well as other VPLMNs where the UE is currently located. The container includes the requested information and includes UE information that is pertinent to the request. The UE may send a protected container (transparent for AMF i.e. container is protected with home network security information) that includes info relevant for UDM e.g. UE capabilities, UE location, Requested NSSAI, etc. + +NOTE: Security aspects on how to protect the UE capabilities provided by the UE are to be discussed in SA WG3. + +2. new info: AMF forwards the received container transparently from the UE in the Nudm\_UECM\_Reg Request towards the UDM. +3. UDM uses UE capabilities to check that UE supports ability to handle the additional information and if the UE does support the additional information, then UDM initiates a request to the SoR AF and indicates in such a request the UE capabilities. +4. This is identical to step 2 in clause 6.6.3.1. +5. This is identical to step 3 in clause 6.6.3.1. +6. This is identical to step 4 in clause 6.6.3.1. +7. HPLMN (or CH) sends SoR information within the Access and Mobility Subscription data i.e. AMF is transparent to the content of such data. +8. AMF forwards the "steering of roaming information" within the Registration Accept as per current specification. +9. This is identical to step 6 in clause 6.6.3.1. + +### 6.6.3.1.2 Network Triggered capability indication + +The procedure below implements the Network triggered option to retrieve the UPU/SoR capabilities. + +![Sequence diagram for Network Initiated for Extended SoR Information. The diagram shows interactions between UE, AMF, UDM, and SoR AF across VPLMN and HPLMN domains. The process involves registration, capability fetching, UPU request, and SoR information delivery.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + participant SoR_AF as SoR AF + + Note over UE, AMF: VPLMN + Note over UDM, SoR_AF: HPLMN + + Note right of AMF: 2. UDM based on e.g local configuration Fetches UE capabilities + + UE->>AMF: 1. UE performs Regular Registration based on exiting procedures + AMF->>UDM: 3. Nudm_SDM_Notify (Fetch UE Capabilities) + AMF->>UE: 4. DL NAS TRANSPORT (UDM Request VPLMN Extended List Capabilities) + UE->>AMF: 5. UL NAS TRANSPORT(Containing UPU ACK Container) + AMF->>UDM: 6. Nudm_SDM_Info (UE Capabilities) + UDM->>SoR_AF: 7. Nsoraf Get Request (VPLMN ID, UE Location, Subscribed NSSAI, etc..) + Note right of SoR_AF: 8. SoR AF creates the needed Information + SoR_AF->>UDM: 9. Nsoraf Get Response (Prioritized List of VPLMNs) + UDM->>AMF: 10. Nudm_SDM_Notify (SoR Info) + AMF->>UE: 11. DL NAS TRANSPORT (Extended SoR Info) + UE->>AMF: 12. UL NAS TRANSPORT(Containing UPU ACK Container) + AMF->>UDM: 13. Nudm_SDM_Info (SoR ACK) + Note left of UE: 14. UE scans the received Steering Info and adjust accordingly + +``` + +Sequence diagram for Network Initiated for Extended SoR Information. The diagram shows interactions between UE, AMF, UDM, and SoR AF across VPLMN and HPLMN domains. The process involves registration, capability fetching, UPU request, and SoR information delivery. + +**Figure 6.6.3.1.2-1: Network Initiated for Extended SoR Information** + +The steps in the call flow are briefly described below: + +1. The UE performs a regular Registration. During that procedure, the UDM may interact with the SoR AF to provide SoR info to the UE during initial registration (e.g. based on local configuration) + 2. UDM decides to fetch the UE capabilities to see if the UE supports slice-based SoR information. The UDM may determine to trigger this step based on e.g. local configuration, UE location in specific PLMN or a new indication provided by the SoR AF to the UDM in step 1. + 3. The UDM triggers an extended UPU procedure requesting the UE to send its UPU capabilities in the response. Hence, UDM sends to the AMF, an Nudm\_SDM Notification including a UPU transparent container to trigger the UE to return its UPU capabilities. +- NOTE: Security aspects of the protection of the UPU transparent container are to be discussed in SA WG3. +4. The AMF sends a DL NAS TRANSPORT message to the UE, where this DL NAS TRANSPORT message including the UPU transparent container where the UDM requests the UE capabilities of the UE to handle enhanced SoR information (e.g. a list of VPLMNs and optional supported network slices and/or applicability/validity info, as described herein). + 5. The UE returns its capabilities within an UPU ACK transparent container in an NAS UL TRANSPORT message to the AMF. + 6. The AMF sends, to the UDM, an Nudm\_SDM\_Info including the UPU ACK transparent container indicating that the UE has the capabilities to receive enhanced SoR information. + 7. This is identical to step 2 in clause 6.6.3.1. + 8. This is identical to step 3 in clause 6.6.3.1. + +9. This is identical to step 4 in clause 6.6.3.1. +10. The UDM sends, to the AMF, a Nudm\_Notify and includes the enhanced SoR information. +11. The AMF sends a DL NAS TRANSPORT message including the enhanced SoR information to the UE. Optionally, an ID of the enhanced SoR information may be included in the message. The UE stores the enhanced SoR information. +12. The UE returns UPU ACK in an NAS UL TRANSPORT message to the AMF. +13. The AMF sends to the UDM an Nudm\_SDM\_Info UPU to acknowledge UE reception of the enhanced SoR info including the VPLMN List. +14. This is identical to step 6 in clause 6.6.3.1. + +## 6.6.4 Impacts on Existing Nodes and Functionality + +### UE + +- supports the slice-based SoR information. + +### UDM + +- handles the new UE capabilities. Creates the slice-based SoR information based on incoming data from the UE only if co-located with SoR-AF, or transparently pass the UE needed information to the SoR AF. Transport the slice- based SoR information to the UE. + +### AMF + +- To convey the transparent container to UDM. + +### SoR AF + +- Creates the slice-based SoR information based on incoming data from the UE. + +## 6.7 Solution #7: Enabling awareness of Network Slice availability in VPLMNs + +### 6.7.1 Introduction + +This solution addresses KI#2 from TR 23.700-41, clause 5.2 and explains how the UE may use information about slice availability per VPLMN and prioritization information, received from the HPLMN to influence automatic PLMN selection. + +### 6.7.2 Functional Description + +During the Registration procedure, if the AMF does not have subscription data for the UE, the AMF invokes Nudm\_SDM\_Get service operation to HPLMN UDM to get Access and Mobility subscription Data for the UE. Upon receipt of a Nudm\_SDM\_Get message and as part of the Steering of Roaming procedure, the UDM includes in the list of preferred VPLMN/Access Technology combinations, a list of supported S-NSSAIs. + +The AMF relays the Steering of Roaming information, including the S-NSSAI information associated with the VPLMN/Access Technology combination. + +When the Steering of Roaming information, including the S-NSSAI information is received, the UE determines, based on the list of VPLMNs available in the area and the S-NSSAIs supported in these VPLMNs, whether the UE may attempt to obtain service on a higher priority VPLMN as specified in the received Steering of Roaming information. + +The solution considers two cases: + +- Option 1: The UE's USIM is not configured to receive a Slice-Aware SoR. If the UE is not configured to receive Slice-Aware SoR information and the current VPLMN has rejected S-NSSAIs the UE has requested, then the UE, as an implementation option, may determine to execute a Deregistration procedure. The UE may indicate in the Deregistration Request message, within the Deregistration Type, that the Deregistration procedure has been + +triggered due to lack of S-NSSAI support. When the Deregistration Type indicates, "Required S-NSSAI not supported/available", the AMF informs the UDM that the UE has Deregistered due to lack of S-NSSAI in this VPLMN. + +If during the Deregistration procedure the UDM received an indication that the UE has requested Deregistration due to lack of S-NSSAI support in a VPLMN, the UDM may keep a "Slice-Aware SoR pending" flag in the UE subscription information indicating that the UE may re-register in a different VPLMN to seek S-NSSAI support and that Slice-Aware SoR information shall be sent to the UE upon a subsequent Registration attempt. + +During a subsequent Registration, if the AMF does not have subscription data for the UE, the AMF invokes Nudm\_SDM\_Get service operation to HPLMN UDM to get Access and Mobility subscription Data for the UE. If the "Slice-Aware SoR pending" flag is set, upon receipt of a Nudm\_SDM\_Get message and as part of the Steering of Roaming procedure, the UDM may include in the list of preferred VPLMN/Access Technology combinations, a list of supported S-NSSAIs + +- Option 2: The UE is capable and configured to receive Slice-Aware SoR information. The UE indicates in the Registration Request that the UE shall receive Slice-aware SoR information, e.g. including VPLMN, location (e.g. geographical coordinates or specific TA) and S-NSSAI combination. + +During a registration procedure, if the AMF does not have subscription data for the UE, the AMF invokes Nudm\_SDM\_Get service operation to HPLMN UDM to get Access and Mobility subscription Data for the UE. Upon receipt of a Nudm\_SDM\_Get message and as part of the Steering of Roaming procedure, the UDM may include in the list of preferred VPLMN/Access Technology combinations, a list of supported S-NSSAIs. + +## 6.7.3 Procedures + +### 6.7.3.1 Option 1 - UE's USIM is NOT configured to receive a Slice-Aware SoR + +This option is characterized in that the HPLMN relies on the Slice-Aware SoR pending flag to provide the UE with Slice-Aware SoR information. + +A UE may request access Registration to a VPLMN from its current VPLMN/access technology list, while roaming in a visited network. Following existing procedures, the UE constructs the Requested NSSAI based on the NSSP and Configured NSSAI, which the UE uses to associate applications to specific S-NSSAIs. + +The visited network accepts the Registration request, via a Registration Accept message, but it may reject the UE's request for an S-NSSAI, the UE included in the Requested NSSAI. In this option, as the UE is not configured to expect to receive Slicer-Aware SoR, the HPLMN may not deliver the Slice-Aware SoR, i.e. the slice-based SoR in the UDM subscription is not set. + +If no Slice-Aware SoR information is provided, the UE may decide, in an implementation specific manner, that it does not want to remain in a VPLMN that does not provide the entire Requested S-NSSAI, or S-NSSAIs the UE requires for specific applications and the UE triggers a Deregistration procedure and it provides a new Deregistration Type: "S-NSSAI not available" and it provides which S-NSSAI(s) was/were not available. The including of the new Deregistration type indicates to the UDM that the UE is capable and configured to receive the "Slice-Aware SoR" information. + +The VPLMN AMF accepts the Deregistration Request and if the UE indicated Deregistration Type as "S-NSSAI not available", the AMF notifies the UDM the UE has Deregister and it provides the Deregistration Type as: "S-NSSAI not available". + +The UDM interprets the receipt of the new Registration type as an implicit indication that the UE is configured to receive the Slice-Aware SoR information and it may set the slice-based SoR Flag to indicate that the UE may attempt to re-register and that a slice-based SoR container may be sent to the UE to provide information about available S-NSSAI in VPLMNs the UE may access, in the area the UE is currently located. + +The UDM may request SoR information from the SOR-AF and it may indicate that the S-NSSAI associated to the VPLMN/access technology are required. + +The SOR-AF may use analytics and/or information from AMF VPLMN and possible NSSF at the VPLMN to derive S-NSSAI information in TA from relevant VPLMNs. The AMF gathers this information with the help of the NSSF and the AN, when the 5G-AN nodes establish or update the N2 connection with the AMF. The SOR-AF, may obtain analytics or per VPLMN S-NSSAI information, e.g. by subscribing to a new event through the V-NEF and derive the list of S-NSSAI available in the VPLMN in a particular area, using NEF operations (i.e. Nnef\_EventExposure\_Notify + +service operation). The SOR-AF may provide a Slice-Aware SoR container to the UDM and the UDM can include it during the next Registration for UE for which a "Slice-Aware SoR" flag is set, or if local configuration warrants it. + +Alternatively, the UDM may decide to include the Slice-Aware SoR container in the Deregistration service operation Output. If the UDM includes the Slice-Aware SoR container in the Deregistration service operation Output, the AMF relays it to the UE in the Deregistration accept message. + +If the UE does not get the Slice-Aware SoR container in the Deregistration accept message, the UE may decide to attempt a new Registration to attempt access to a specific S-NSSAI and it may decide to deprioritize this VPLMN. + +If this is an initial registration or if the UE indicates that is capable and configured to received Slice-Aware SoR information, the AMF triggers a SoR operation through a Nudm\_SDM\_Get request message, indicating that the S-NSSAI information is also required. The UDM may request SoR information from the SOR-AF, if not already requested. Note that such request could be executed either because of a Nudm\_SDM\_Get request message or as a result of a Nudm\_UECM\_DeregistrationNotification message. + +The UDM may use information from the SOR-AF to provides the list of VPLMN/access technologies and associated S-NSSAIs in the Nudm\_SDM\_Get\_response message. + +The AMF may provide to the UE in the Registration Accept message as part of the SOR container, the list of VPLMN/access technologies and associated S-NSSAIs. + +The UE may reselect to a higher priority VPLMN that may support S-NSSAI according to the information receive in the SoR container. + +### 6.7.3.2 Option 2 - UE's USIM is configured to receive a Slice-Aware SoR + +This option is characterized in that the HPLMN relies on the indication in the UDM that the UE is expected to receive the Slice-Aware SoR information. This is based on existing SoR principles as described in TS 23.122 [7] and does not rely on URSP rules. + +A UE request access Registration to a VPLMN in its current VPLMN/access technology list, while roaming in a visited network. The UE constructs the Requested NSSAI based on the NSSP. + +The visited network accepts the Registration request, via a Registration Accept message, but it may reject the UE's request for an S-NSSAI, the UE included in the Requested NSSAI. + +If this is an initial registration or if the UE indicates that is capable and configured to received Slice-Aware SoR information, the AMF triggers a SoR operation through a Nudm\_SDM\_Get request message, indicating that the S-NSSAI information is also required. The UDM may request SoR information from the SOR-AF, if not already requested. + +The UDM may use information from the SOR-AF to provides the list of VPLMN/access technologies and associated S-NSSAIs. + +In this option, since UE's USIM is configured to receive a Slice-Aware SoR, the Slice-Aware SoR information is provided to the UE in the Registration Accept message, therefore a list of VPLMN/access technologies and associated S-NSSAIs may be provided to the UE as part of the SOR container. If the UE did not receive Slice-Aware SoR information in the Registration Accept message, the UE may trigger reselection as per regular PLMN selection procedure, the UE may consider this PLMN as low priority. + +The UE may reselect to a higher priority VPLMN that may support S-NSSAI according to the information receive in the SoR container. + +## 6.7.4 Impacts on services, entities and interfaces + +UE: + +- The UE triggers a Deregistration procedure and it provides a new Deregistration Type: "S-NSSAI not available" and it may provide which S-NSSAI(s) was/were not available. +- The UE receives, in the Registration Accept message, Slice-Aware SoR information including a list of VPLMN/access technologies and associated S-NSSAIs provided to the UE as part of the SOR container. + +- The UE reselects to a higher priority VPLMN that may support S-NSSAI according to the information received in the SoR container. + +**AMF:** + +- The AMF provides information to the SOR-AF on available S-NSSAIs for certain VPLMN/access technology combination, if the SOR-AF is not in the operator's trusted domain, the AMF communicates with SOR-AF via NEF. The AMF gathers this information with the help of the NSSF and the AN, when the 5G-AN nodes establish or update the N2 connection with the AMF. +- During a Deregistration Request procedure, the AMF notifies the UDM that UE has Deregistered and it provides the Deregistration Type as: "S-NSSAI not available". + +**UDM:** + +- The UDM is notified in the Nudm\_UECM\_DeregistrationNotify, that the UE has Deregistered and the UDM gets the Deregistration Type as: "S-NSSAI not available". +- The UDM interprets the receipt of the new Registration type as an implicit indication that the UE is configured to receive the Slice-Aware SoR information and it may set a new Flag to indicate that the UE may attempt to re-register and that SoR may be used to provide information about available S-NSSAI in VPLMNs the UE may access in the area the UE is currently located. +- The UDM requests SoR information from the SOR-AF and it indicates that the S-NSSAI(s) associated to the VPLMN/access technology are required. +- The UDM uses information from the SOR-AF to provide the list of VPLMN/access technologies and associated S-NSSAIs in the Nudm\_SDM\_Get\_response message. + +**SOR-AF:** + +- The SOR-AF uses analytics and information from AMF VPLMN and possible NSSF at the VPLMN to derive S-NSSAI information in TA from relevant VPLMNs. +- The SOR-AF gets a request from the UDM, via a Nsoraf\_SoR\_request message, indicating that the S-NSSAI associated to the VPLMN/access technology are required. +- If the SOR-AF is not in the operator's trusted domain, the SOR-AF may communicate with the AMF and possibly NSSF at the VPLMN via NEF. The SOR-AF uses analytics and information from AMF VPLMN and possible NSSF at the VPLMN to derive S-NSSAI information in TA from relevant VPLMNs. + +## 6.8 Solution #8: Gracefully network slice termination + +### 6.8.1 Introduction + +The solution addresses the Key Issue#3 and in particular how to avoid service disruption due to an abrupt PDU Session release, when a network slice is terminated due to an undergoing planned maintenance in CN or due to the end of network slice's lifetime. + +The scenario, where the solution is addressing, is the following: + +- An operator would like to terminate a network slice (S-NSSAI) either for the whole PLMN or for a particular region in the PLMN for maintenance purpose or due to the end of network slice's lifetime, while there are still some UEs being registered to the network slice and some PDU Sessions including the PDU Session for Emergency, Critical and Priority services, which are established in the network slice. This leads to a removal of UEs and to release of existing PDU Sessions from the network slice and hence resulting to an abrupt service disruption and a degradation of service quality experience by a user. + +This solution makes the following assumptions: + +- OAM is configured with the information about when and which network slice is to be terminated. + +NOTE: Solution #8 can coexist with other solutions in the TR, which handle the issue of temporary network slice and have an impact on the UE. + +## 6.8.2 Functional Description + +The solution is based on the following principles: + +- To achieve a graceful network slice termination, prior to the time for terminating the S-NSSAI, based on operator's policy, it is proposed that the CN should consider the following criteria/condition for tearing down PDU Sessions associated with the network slice subject to be terminated. +- first is to check whether the PDU Session is active or inactive. CN releases all inactive PDU Session first; +- second is to check whether the active PDU Session are for emergency, critical and priority service; If active PDU Sessions are not for emergency, critical and priority service, the CN further releases these PDU Sessions even they are active PDU Sessions after a certain operator's pre-defined period of time. If active PDU Session are for emergency, critical and priority service, it is recommended to keep such PDU Session at least for another operator's pre-defined period of time. +- To trigger the CN NF (AMF) to start tearing down PDU sessions, OAM configures the UDM with the information that the network slice is to be terminated and when to be terminated. The UDM sends an update notification to the AMF on the subscription data related to the Access and Mobility. + +NOTE 1: It is possible that OAM configures directly the AMF(s) affected by the S-NSSAI to be terminated. In this case, UDM will not trigger the affected AMF(s) as depicted in Figure 6.8.3-1. However, once all PDU Sessions associated with the S-NSSAI to be terminated are released, OAM should inform the UDM to remove the S-NSSAI from the UE's subscription data. In case, an operator wants to terminate a S-NSSAI in a specific region and not for the whole PLMN, OAM can configure directly the AMF(s) in that region, where the S-NSSAI is to be terminated. + +- In roaming scenario, where a VPLMN plans to terminate a network slice in its network, it is assumed that OAM in VPLMN configures network functions (i.e. AMF) associated with the network slice to be terminated with the information about when and which network slice is to be terminated. This enables the affected AMF(s) to gradually release roaming UE's PDU Session(s) and to update the Allowed NSSAI to the UE. + +NOTE 2: For the roaming UE, the update of Allowed NSSAI could potentially consist of associating the mapping of subscribed S-NSSAI to another S-NSSAI in the serving network. + +## 6.8.3 Procedures + +Figure 6.8.3-1 describes an overview of the procedure how the network slice is terminated while minimizing abrupt service disruption as much as possible. + +![Sequence diagram showing the interaction between UE, AMF, and UDM for updating session management subscriber data. The process involves UDM configuration, notification to AMF, AMF response, PDU session release, and UDM data removal.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + Note right of UDM: 1. Configuration with the info. when and which S-NSSAI is to be terminated + UDM->>AMF: 2. Nudm_SDM_Notification Request + AMF->>UDM: 3. Nudm_SDM_Notification Response + Note left of AMF: 4. Gracefully releasing PDU Session associated with the S-NSSAI subject to be terminated + AMF->>UDM: 5. Nudm_SDM_Info + Note right of UDM: 6. UDM removes the S-NSSAI subject to be terminated from the UE's subscription data + +``` + +Sequence diagram showing the interaction between UE, AMF, and UDM for updating session management subscriber data. The process involves UDM configuration, notification to AMF, AMF response, PDU session release, and UDM data removal. + +**Figure 6.8.3-1: Updating session management subscriber data in AMF** + +1. The UDM is configured by the OAM with the information of which S-NSSAI is subject to be terminated and when the S-NSSAI will be terminated. This information is part of the Access and Mobility Subscription data. In addition, if the S-NSSAI termination is only applicable within a specific region within the PLMN, OAM configures UDM with the location information such as TAI list along with the S-NSSAI that is subject to be terminated. + +NOTE 1: The information about "when the S-NSSAI will be terminated" can be in different forms, e.g. "to be terminated in a due time, like in 1 hour", or "to be terminated at a specific date and time". + +2. Based on the implicit subscription during registration procedure, the UDM notifies the update of the Access and Mobility Subscription data to the affected AMF(s) by the means of invoking Nudm\_SDM\_Notification service operation. The Nudm\_SDM\_Notification Request message includes the S-NSSAI(s) subject to be terminated, and optionally, the time period indicating when the S-NSSAI is to be terminated. + +3. The AMF responds to the UDM with the Nudm\_SDM\_Notification Response message. + +4. The AMF modifies the Access and Mobility Subscription data in the UE context that is stored in the AMF. + +The AMF performs the following for a PDU Session associated with the S-NSSAI marked as "subject to be terminated": + +NOTE 2: This step 3 is performed for all UEs that are affected by the S-NSSAI marked as "subject to be terminated". + +- If a PDU Session is already established but inactive, the AMF triggers the respective SMF to release the PDU Session. Similar to step 1a in clause 4.3.4.2 of TS 23.502 [5]. +- If a PDU Session is already established and still active, the AMF does not trigger the respective SMF to release the PDU Session. When the PDU Session becomes inactive, the AMF triggers the SMF to release the PDU Session. + +PDU Session. Similar to step 1a in clause 4.3.4.2 of TS 23.502 [5]. Subject to operator's policy, the AMF may check if the PDU Session is used for Emergency, Critical and Priority services. + +NOTE 3: Based on step 4 in clause 4.2.3.2 of TS 23.502 [5], for NB-IoT RAT Type, it is possible that AMF is aware of active/inactive status of PDU Session. One possible way is that the AMF subscribes to an event report from SMF on when the PDU Session is activated or is deactivated via an existing Nsmf\_EventExposure\_Subscribe service operation. + +**Editor's note:** It is FFS whether and how the AMF is aware of PDU Session Status (active/inactive). + +- In case the PDU Session is not used for Emergency, Critical and Priority services, subject to operator's policy, the AMF triggers the SMF to release the active PDU Session after an operator's pre-defined period of time expires. Similar to step 1a in clause 4.3.4.2 of TS 23.502 [5]. + - In case the PDU Session is used for Emergency, Critical and Priority services, subject to operator's policy, the AMF may keep the PDU Session for an operator's pre-defined period of time. After that, the AMF triggers the SMF to release the active PDU Session for Emergency, Critical and Priority services. Similar to step 1a in clause 4.3.4.2 of TS 23.502 [5]. + - If the AMF receives a new PDU Session Establishment Request or any requests (e.g. Registration Request) for the S-NSSAI subject to be terminated, the AMF rejects the request or does not include the S-NSSAI subject to be terminated in the Allowed NSSAI. +5. When AMF has released all PDU Sessions associated with the S-NSSAI subject to be terminated, the AMF informs the UDM of the result accordingly. This can be done with Nudm\_SDM\_Info service operation or a new message, + 6. When UDM receives a response from all affected AMF(s) associated with the S-NSSAI subject to be terminated, the UDM deletes the S-NSSAI from the UE's subscription data, which triggers an update towards the AMF to remove the S-NSSAI from the Configured NSSAI and from the Allowed NSSAI. + +After this, the network operator can safely terminate the corresponding network slice at the point in time according to the schedule known by the OAM. + +NOTE 4: For any RAN, which are affected by terminating the network slice, the OAM removes the supported S-NSSAI from the RAN. For interoperability between the RAN and the AMF, the affected RAN uses RAN Configuration Update procedure as specified in clause 8.7.2 of TS 38.413 [8] to inform the AMF about updating S-NSSAI(s) supported by the RAN. In addition, the affected AMF also informs the RAN about updating S-NSSAI(s) supported by the AMF by using the AMF Configuration Update procedure in clause 8.7.3 of TS 38.413 [8]. + +## 6.8.4 Impacts on services, entities and interfaces + +UDM: + +- UDM is enhanced to support which S-NSSAI is subject to be terminated and when the S-NSSAI will be terminated and to inform SMF by invoking the Nudm\_SDM\_Notification service. + +AMF: + +- AMF is enhanced to gracefully release PDU Session(s) associated with the S-NSSAI subject to be terminated based on the operator's policy and optionally to inform the UDM about the results of terminating PDU Session(s). +- AMF is enhanced to know active/inactive status of all PDU Session(s), and not just for PDU Session established with the NB-IoT RAT Type. + +## 6.9 Solution #9: Support of a Network Slice with an AoS not matching existing TA boundaries. + +### 6.9.1 Introduction + +This solution aims to address the key issues#3 by proposing that the RAN is enhanced to support additional TAC broadcast (secondary TACs) that supporting UEs can use. This will require RAN2/3 and CT1 to update their specifications accordingly. + +### 6.9.2 Description + +As the use cases for network slicing become more and more advanced and permit addressing private networking and industrial IoT applications, the Area of Service (AoS) of network slice can become limited to small areas of a PLMN which may not map to already existing TA boundaries. In order to accommodate this, with the current set of specification the way to achieve this would be to redesign the TAs topology of the network. + +Indeed, if the goal of an operator is to support legacy UEs while using such slices, the only possible solution is to redesign the TA boundaries and potentially add new and smaller TAs. + +So, it can be concluded that to support legacy UEs, the only solution possible to address the problem space is to redesign the TAs to enable matching the needs to deploy limited AoS network slices not matching already deployed TAs topology. + +While this can be a solution, this implies that even users that do not have interest in the specific limited AoS slices may end up having to be allocated to such smaller tracking area and/or the TAI list can become rather complicated to form or even in some cases exceed the limit of 16 TAs in the TAI-list. It may in some situations cause also additional signalling traffic due to mobility management and needs of UE configuration update even if the UEs are not interested at all by the use of these specific slices. So, for rel-18 and beyond, improvements can be considered. + +If there are network slices that the operator knows the customer has full control on the UE population of and the specification of the supported UEs capabilities is part of the SLA, we can explore alternative option that is presented here. + +The solution is based on allowing the broadcast on SIB of additional TACs (we expect only a small number if not just one additional to be only needed to cover most cases, RAN2 to define how many can be configured) that supporting UEs can read. These additional/secondary TAC values are passed to the CN with the associated slices supported in NG-AP messages uses to maintain the supported slices and explicitly indicated as "Secondary TACs" in UE specific signalling when the TAC is included today to signal the UE location in the Initial UE message. The AMF then forms the RA by considering the support of slices as today, but it can only include in the Allowed NSSAI network slices requiring TAs that are broadcasted as secondary TAs in the RA for the supporting UEs (so e.g. Note well that the support of slices that are not fully supported in a TA is not signalled, as per today's specifications (so, e.g. TA4 only uniformly supports S-NSSAI 1 and S-NSSAI 4). See figure 6.9.2-1. These slices whose AoS also requires some secondary TAs, can be allowed in the in the secondary TAs indicated in the RA only for supporting UEs - so, if the RA includes secondary TAs, then only supporting UEs can received these slices S-NSSAIs in the Allowed NSSAI. Primary TAs may be included in the RA for these slices in addition to secondary TAs only if the S-NSSAIs is uniformly supported in the primary TA that are indicated in the RA. Of course these capable UEs are as capable as the legacy UEs to be allowed to use slices that fully match existing deployed TAs (so if the supporting UE requests S-NSSAI 1 only, it can be indicated a RA=(TAI1,TAI5). + +![Figure 6.9.2-1: Example TA topology including Primary and Secondary TAs. The diagram shows a large oval representing the network area, containing several smaller ovals representing Tracking Areas (TAs). A legend indicates that thick lines represent Primary TAs and thin lines represent Secondary TAs. The TAs are labeled as follows: TA1 S-NSSAI 1 (Primary), TA1, TA2 S-NSSAI 1,2 (Secondary), TA1, TA3 S-NSSAI 1,3 (Secondary), TA1, TA3, TA4 S-NSSAI 1,3,4 (Secondary), and TA5 S-NSSAI 1 (Primary). Below the diagram is a table listing the uniformly supported slices per TA.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +| Uniformly Supported Slices per TA | TA | S-NSSAI | Support Level | +|-----------------------------------|------|-------------|---------------| +| | TA1: | S-NSSAI 1 | primary | +| | TA2: | S-NSSAI 1,2 | secondary | +| | TA3: | S-NSSAI 1,3 | secondary | +| | TA4: | S-NSSAI 1,4 | secondary | +| | TA5: | S-NSSAI 1 | primary | + +Figure 6.9.2-1: Example TA topology including Primary and Secondary TAs. The diagram shows a large oval representing the network area, containing several smaller ovals representing Tracking Areas (TAs). A legend indicates that thick lines represent Primary TAs and thin lines represent Secondary TAs. The TAs are labeled as follows: TA1 S-NSSAI 1 (Primary), TA1, TA2 S-NSSAI 1,2 (Secondary), TA1, TA3 S-NSSAI 1,3 (Secondary), TA1, TA3, TA4 S-NSSAI 1,3,4 (Secondary), and TA5 S-NSSAI 1 (Primary). Below the diagram is a table listing the uniformly supported slices per TA. + +Figure 6.9.2-1: Example TA topology including Primary and Secondary TAs + +Based on the uniform support of network slices per TA in figure 6.9.2-1, if, the UE requests S-NSSAI 3 and S-NSSAI 1 only, then the RA includes TAI 3 but not TAI1. It is not permitted to add TA4 as cells broadcasting TA4 do not always support S-NSSAI 3 (see above in figure 6.9.2-1 that the cells broadcasting TA4 under primary TA5 do not support S-NSSAI 3). + +In other words, the uniform support of slices is assumed also at the secondary TAI level. + +Since a gNB only provides the supported slices under the TAC it administers, S-NSSAI(s) uniform support by a secondary TA shall be configured in each gNB even though for the cells under its scope support may be considered uniform (e.g. in figure 6.9.2-1 the TA5 and TA1 may be under different gNBs and so TA4 may be considered uniformly supporting S-NSSAI 3 from the gNB supporting TAI1 and not supporting S-NSSAI 3 in gNB supporting TAI5). The alternative is that the AMF or NSSF determine the uniform support based on the received information from the RAN by combining the support indication received by different NG-AP sources (i.e. if gNB 1 declares S-NSSAI3 is supported by TAI4 and gNB5 does not indicate support of S-NSSAI3 by TAI4, then TAI4 does not support S-NSSAI 3 uniformly and the NSSF/AMF can summarize this when they combine the indication by different gNBs). + +### 6.9.3 Procedures + +When the UE performs a MRU, it includes support secondary TAs in UE 5GMM capabilities. The Initial UE message or the UL NAS transport message where the Registration Request is carried, convey the User Location Information IE with the primary TAC and the secondary TACs of the Cell Id to determine the S-NSSAIs that are supported in the cell where the UE is. + +![Figure 6.9.3-1: enhanced ULI in INITIAL UE/ UL NAS TRANSPORT MESSAGES. The diagram shows a sequence of messages between an NG-RAN node and an AMF. The NG-RAN node sends an INITIAL UE / UL NAS TRANSPORT MESSAGE (incl. ULI with Secondary TACs of cell) to the AMF.](63a2519518616620ef0e53d98b923c05_img.jpg) + +Figure 6.9.3-1: enhanced ULI in INITIAL UE/ UL NAS TRANSPORT MESSAGES. The diagram shows a sequence of messages between an NG-RAN node and an AMF. The NG-RAN node sends an INITIAL UE / UL NAS TRANSPORT MESSAGE (incl. ULI with Secondary TACs of cell) to the AMF. + +Figure 6.9.3-1: enhanced ULI in INITIAL UE/ UL NAS TRANSPORT MESSAGES + +Indicatively, we propose to modify the "User Location Information IE" in clause 9.3.1.16 of TS 38.413 [8]: + +**From:** + +This IE is used to provide location information of the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|------------------------|---------------------------------------------------------------------|-------------|----------------------| +| CHOICE User Location Information | M | | | | - | | +| >E-UTRA user location information | | | | | | | +| >>E-UTRA CGI | M | | 9.3.1.9 | | - | | +| >>TAI | M | | 9.3.3.11 | | - | | +| >>Age of Location | O | | Time Stamp
9.3.1.75 | Indicates the UTC time when the location information was generated. | - | | +| >>PSCell Information | O | | NG-RAN CGI
9.3.1.73 | | YES | ignore | +| >NR user location information | | | | | | | +| >>NR CGI | M | | 9.3.1.7 | | - | | +| >>TAI | M | | 9.3.3.11 | | - | | +| >>Age of Location | O | | Time Stamp
9.3.1.75 | Indicates the UTC time when the location information was generated. | - | | +| >>PSCell Information | O | | NG-RAN CGI
9.3.1.73 | | YES | ignore | + +**To:** + +This IE is used to provide location information of the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|------------------------|---------------------------------------------------------------------|-------------|----------------------| +| CHOICE User Location Information | M | | | | - | | +| >E-UTRA user location information | | | | | | | +| >>E-UTRA CGI | M | | 9.3.1.9 | | - | | +| >>TAI LIST | M | | 9.3.3.11 | | - | | +| >>Age of Location | O | | Time Stamp
9.3.1.75 | Indicates the UTC time when the location information was generated. | - | | +| >>PSCell Information | O | | NG-RAN CGI
9.3.1.73 | | YES | ignore | +| >NR user location information | | | | | | | +| >>NR CGI | M | | 9.3.1.7 | | - | | +| >>TAI LIST | M | | 9.3.3.11 | | - | | +| >>Age of Location | O | | Time Stamp
9.3.1.75 | Indicates the UTC time when the location information was generated. | - | | +| >>PSCell Information | O | | NG-RAN CGI
9.3.1.73 | | YES | ignore | + +where the definition of TAI LIST can be like: + +## TAI LIST + +This IE indicates the list of TAIs broadcast by the NG RAN node and can be accessed by the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------|----------|----------------------------|--------------------------------------|-----------------------|-------------|----------------------| +| TAI Item | | 1.. | | | - | | +| >TAC | M | | 9.2.2.5 | Broadcast TAC | - | | +| >Broadcast PLMNs | | 1.. | | | - | | +| >>PLMN Identity | M | | 9.2.2.4 | Broadcast PLMN | - | | +| >>TAI Type | M | | ENUMERATED (primary, secondary, ...) | slice categorization | - | | + +The *TAI Type* information shall also be conveyed alongside the TAI in the NG-AP NG SETUP REQUEST, RAN CONFIGURATION UPDATE messages. similarly, the same applies on Xn-AP Xn SETUP REQUEST and NG-RAN CONFIGURATION UPDATE message and in the F1-AP F1 SETUP REQUEST and GNB-DU CONFIGURATION UPDATE messages. + +**In the registration Request message itself, the gNB also includes:** + +In the UE Registration Request step 1 of Figure 4.2.2.2.2-1: "Registration procedure" the registration request includes the "last visited TAI" information. + +[...] UE to (R)AN: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, **[last visited TAI (if available)]**). [...] + +**It is proposed that now it is augmented with the "Last visited secondary TAIs" by supporting UEs because these TAIs have to be detected in the AMF as additional to the primary TAI to have complete information.** + +[...] UE to (R)AN: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, **[last visited TAI (if available)], [last visited secondary TAIs (if available and supported by the UE)]**). [...] + +## 6.9.4 Impacts on services, entities and interfaces + +The solution has the following impacts: + +NG-RAN node: + +- Broadcast one or more additional TAIs via a new information element in SIB. +- Support new messages in the NG-AP and Xn-AP as well as F1AP procedures to share support of additional secondary TAI, or indicating the cell where the UE is support >1 TAC and what the TAC and which ones the primary/secondary values are. + +AMF: + +- Obtain information on the slice support for primary and secondary TAIs via NGAP procedures. +- Assign the registration area considering the primary and secondary TACs and whether the UE is a legacy UE or new UE. +- Page UEs considering the primary and secondary TAC if informed via NGAP procedures as well as the corresponding registration areas of the UEs. +- Obtain UE's primary TAC and secondary TACs via initial UE message. + +UE: + +- When multiple TACs are available for the selected PLMN, the UE selects (all things being equal) a primary or secondary TAC inside the RA. +- perform registration procedure by taking into account the secondary TAC broadcasted. + +## 6.10 Solution #10: Associating a validity timer with a temporary slice + +### 6.10.1 Introduction + +The solution addresses second part of the key issue #3 " Network Slice Area of Service for services not mapping to existing TAs boundaries and Temporary network slices " which states that there can be case where a network slice is deployed temporarily for a particular time period + +The network (e.g. AMF, SMF, NSSF or other NFs) associates a validity timer for each S-NSSAI which is deployed temporarily either by explicit signalling (e.g. the NFs gets validity timer from the UDM) or through O&M procedure. This validity timer for each temporary S-NSSAI is sent to the UE e.g. in the configured NSSAI list during the registration procedure. When the UE receives the S-NSSAI with a validity timer in the configured NSSAI, the UE runs a validity timer. The UE will register to the S-NSSAI when the validity timer is running. In CM-IDLE once the validity timer expires the UE locally removes the S-NSSAI from the allowed NSSAI list and the UE locally release the PDU session associated with the S-NSSAI. The network (e.g. AMF) also runs the validity timer for the S-NSSAI, once the validity timer expires the network removes the S-NSSAI from the allowed NSSAI list and locally release the PDU sessions associated with the S-NSSAI. In CM-CONNECTED state, on expiry of the validity timer, the AMF initiates PDU session release procedure. The network may also associate a S-NSSAI with validity timer if the S-NSSAI was not associated with any validity timer. The UE provides the capability to the AMF which provides to the UDM or other network function that it support configured NSSAI with validity timer. The UE not supporting the timer doesn't get the validity timer in the configured NSSAI. In addition of UDM other entities can also provide the validity timer. This covers both the case where the timer is set in the serving network (for the serving S-NSSAI) and from the subscription (UDM-based, for the subscribed S-NSSAI). + +**Editor's note:** whether O&M or UDM configures validity timer in the roaming case is FFS. + +## 6.10.2 Procedures + +![Sequence diagram illustrating the handling of a temporary network slice. The diagram shows interactions between UE, (R)AN, AMF, and UDM. The UE sends a Registration Request to the AMF. The AMF initiates an authentication procedure with the (R)AN. The (R)AN sends a Security Mode Command to the UE. The AMF registers the UE with the UDM (Nudm_UECM_Registration). The UDM provides the subscribed NSSAI to the AMF (Nudm_SDM_GET Response). The AMF sends a Registration Accept to the UE. The UE stores the configured NSSAI. The UE sends a Registration Complete to the AMF. The UE starts timer t1 and initiates registration to the S-NSSAI 1. The AMF also starts timer t1 and accepts registration to the S-NSSAI 1. Once the timer t1 expires, the UE removes the S-NSSAI 1 from the allowed list locally. The AMF removes the S-NSSAI 1 from the allowed list locally.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UDM + + Note left of UE: 8. UE stores the configured NSSAI + UE->>AMF: 1. Registration Request (User identity, Requested NSSAI) + AMF->>RAN: 2. Authentication procedure + RAN->>UE: 3. Security Mode Command procedure + AMF->>UDM: 4. Nudm_UECM_Registration + AMF->>UDM: 5. Nudm_SDM_GET Request + UDM-->>AMF: 6. Nudm_SDM_GET Response (Subscribed NSSAI= {(S-NSSAI 1, validity time= t1), .....}) + AMF->>UE: 7. Registration Accept(Configured NSSAI= {(S-NSSAI 1, validity time= t1), .....}) + Note right of AMF: 10. Timer t1 is started. The network accepts registration to the S-NSSAI 1 while the timer t1 is running. Once the t1 expires the UE removes the S-NSSAI 1 from the allowed list locally. + UE->>AMF: 9. Registration Complete + Note left of UE: 10. Timer t1 is started. The UE initiates registration to the S-NSSAI 1 while the timer t1 is running. Once the t1 expires the UE removes the S-NSSAI 1 from the allowed list locally. The UE removes the S-NSSAI 1 from the configured NSSAI list. + +``` + +Sequence diagram illustrating the handling of a temporary network slice. The diagram shows interactions between UE, (R)AN, AMF, and UDM. The UE sends a Registration Request to the AMF. The AMF initiates an authentication procedure with the (R)AN. The (R)AN sends a Security Mode Command to the UE. The AMF registers the UE with the UDM (Nudm\_UECM\_Registration). The UDM provides the subscribed NSSAI to the AMF (Nudm\_SDM\_GET Response). The AMF sends a Registration Accept to the UE. The UE stores the configured NSSAI. The UE sends a Registration Complete to the AMF. The UE starts timer t1 and initiates registration to the S-NSSAI 1. The AMF also starts timer t1 and accepts registration to the S-NSSAI 1. Once the timer t1 expires, the UE removes the S-NSSAI 1 from the allowed list locally. The AMF removes the S-NSSAI 1 from the allowed list locally. + +Figure 6.10.2-1: Handling of a temporary network slice + +The detailed procedure are as described below: + +0. The UE can be preconfigured with configured NSSAI with validity timer. Configured NSSAI can also come in UE Configuration Update message. + +NOTE 1: A S-NSSAI can be added or removed dynamically as per the current procedure. + +1. The UE initiates registration procedure and sends registration request message. + +- 2-3. The network may trigger authentication procedure and security mode command procedure. + +- 4-6. The AMF registers to the UDM for the UE. the UDM provides the subscribed NSSAI to the AMF. In the subscribed NSSAI the UDM associate a validity time for each temporary S-NSSAI. + +NOTE 2: The validity timer for a temporary S-NSSAI can also be provided by other NSSF. + +7. The AMF sends configured NSSAI = Subscribed NSSAI to the UE in the registration accept message. + +8. The UE stores the configured NSSAI. + +9. The sends registration complete message to the AMF. + +- 10a. The UE starts t1. The UE initiates registration to the S-NSSAI 1 while the timer t1 is running. Once the t1 expires the UE removes the S-NSSAI 1 from the allowed list locally. The UE removes the S-NSSAI 1 from the configured NSSAI list. + +- 10b. AMF starts t1 is. The AMF accepts registration to the S-NSSAI 1 while the timer t1 is running. Once the t1 expires the UE removes the S-NSSAI 1 from the allowed list locally. + +NOTE 3: The value of the timer can be hours, days or months and details can be captured in stage 3. + +## 6.10.3 Impacts on services, entities and interfaces + +UE + +- Handling of validity timer for a S-NSSAI. + +AMF, SMF, NSSF, PCF + +- Handling of validity timer for a S-NSSAI. + +UDM + +- UDM needs to provide the validity timer for a temporary S-NSSAI for a UE to the AMF. + +## 6.11 Solution #11: Enabling UEs to Request S-NSSAIs not uniformly available + +### 6.11.1 Introduction + +This solution applies to KI#5 and KI#3. This applies to S-NSSAIs that are: + +- either available only temporarily or at specific times, or +- valid in Area of Service that does not match the deployed TA boundaries, or +- valid only in some TAs of the current RA assigned to the UE. + +### 6.11.2 Functional Description + +The high-level points of the proposed solution are: + +- The AMF creates an RA for the UE as per current mechanisms ensuring the optimal size of the RA with respect to the S-NSSAIs that can be allowed. +- Temporary Slices for which the UE has a subscription are provided in the Configured NSSAI provided to the UE. +- The Allowed NSSAI contains only S-NSSAIs that the UE has requested and that are allowed in the whole RA (i.e. each TA of the RA) and, in case of temporary slices, are currently available. + - for temporary slices, the Allowed NSSAI may be augmented to contain a validity time for the S-NSSAI(s) corresponding to temporary slices. When receiving the Allowed NSSAI containing a validity time for the S-NSSAI(s) corresponding to temporary slices, the UE runs a timer and, when the validity timer expires, the UE locally removes the S-NSSAI from the allowed NSSAI list and the UE release the PDU session associated with the corresponding S-NSSAI. +- The AMF provides a set of conditions to the UE for the S-NSSAIs (here called Conditional S-NSSAI) that are valid only under specific conditions (e.g. only in specific TAs, or that have a validity time associated) and therefore cannot be placed in the Allowed NSSAI (here called Conditional S-NSSAI): + - the conditions may include a list of TAs (not included in the present RA) where the S-NSSAI is allowed. + - the conditions may include an Area of Service (as defined in KI#3) for the S-NSSAI. The Area of Service may be defined as a set of TAs or a set of cells. If the Area of Service of an S-NSSAI does not match exactly one or a set of TAs, the RA selected for the UE may not include the TAs that overlap with the area of service and the S-NSSAI corresponding to the Area of Service may be provided as a Conditional S-NSSAI to the UE with the Area of Service information. The Conditional S-NSSAI may be supported in one or more TAs of the RA but not in all of the TAs of the RA. + - it is assumed that the AMF is informed about a slice availability on a per-cell basis from the NG-RAN. + - it is assumed that the AMF is informed about a slice availability in terms of validity time based on OAM or subscription information. + - the conditions may include "time-related conditions" (e.g. specific times at which an S-NSSAI is available or the time period in which the S-NSSAI is available) to support the use cases associated with KI#3. + - multiple conditions may be associated to an S-NSSAI (e.g. list of TAs and "time-related conditions"). + +NOTE 1: An S-NSSAI that is allowed in the whole RA or part of the RA but only under specific time conditions would be placed in the Conditional S-NSSAI. + +- the conditions are provided by placing the S-NSSAI in a new Conditionally Allowed NSSAI IE which contains all the S-NSSAIs the UE requested and that cannot be placed in the Allowed NSSAI since they are not available in the whole RA, but that may be available under different conditions (other TAs, other times, etc.). The UE is allowed to request resources (e.g. establish a PDU session) for the S-NSSAI in the Conditionally Allowed NSSAI without requiring the UE to re-register. If the UE supports the Conditionally Allowed S-NSSAI feature, the UE shall indicate its support for it in the Registration Request message and the AMF shall provide the Conditionally Allowed NSSAI to the UE only if the UE indicated support for it. + +**Editor's note:** The exact impact of allowing the UE to request resources for S-NSSAIs in the Conditionally Allowed NSSAIs without allowing the UE to re-register is FFS. + +**Editor's note:** The impact of using the Conditionally Allowed NSSAI as described above on NSCAF mechanisms is FFS. + +NOTE 2: The decision with respect to which IE is used to convey the additional information should be taken in CT WG1. + +NOTE 3: S-NSSAIs that are placed in the Pending NSSAI may be considered Conditional NSSAIs once the NSSAA procedure is completed successfully. + +- The AMF provides the conditions to the UE anytime the AMF provides, or updates, the Allowed NSSAI and Rejected NSSAI to the UE (e.g. registration procedure, UCU procedure). + +**Editor's note:** How the AMF is provided such condition information, e.g. via OAM or other mechanisms, is FFS. + +- The UE shall not request resources for a Conditional S-NSSAI unless the associated conditions indicate the S-NSSAI is available (e.g. specific TA or time). +- When the UE determines that one or more Conditional S-NSSAI(s) are available and that the applications in the UE require connectivity with the Conditional S-NSSAI(s), the UE may request a PDU session for such S-NSSAI(s). + - when the UE is in a TA corresponding to the set of TAs where a Conditional S-NSSAI is available, the UE may request the establishment of a PDU session for the Conditional S-NSSAI. + - when the validity time associated with a Conditional S-NSSAI applies (i.e. the slice is currently available according to the validity time), then the UE may request the establishment of a PDU session for the Conditional S-NSSAI. + - when the UE is in the Serving Area where a Conditional S-NSSAI is available, the UE may request the establishment of a PDU session for the Conditional S-NSSAI. +- When the UE performs a Service Request for an S-NSSAI that is no longer available (e.g. the UE has moved outside the TA or Serving Area where the S-NSSAI is available or the time conditions have changed), the request for the resources associated to the S-NSSAI is rejected and an indication is provided to the UE as to why. If the S-NSSAI was in the Allowed NSSAI, the AMF may provide a new Allowed NSSAI and a Conditionally Allowed NSSAI to the UE. +- Not all AMFs in a network may support this extension, thus to enable compatibility a UE receiving the additional information regarding Conditional S-NSSAIs shall ignore it and no capability indication to the AMF is required. +- With this solution, non-supporting AMFs cannot support S-NSSAIs with Serving Area or time constraints. + +### 6.11.3 Procedures + +#### 6.11.3.1 Registration Procedure + +The Registration procedure in clause 4.2.2.2.2 of TS 23.502 [5] is enhanced as follows: + +- Step 21: the AMF may include information about Conditional S-NSSAI in the Conditionally Allowed NSSAI in the Registration Accept message. + +### 6.11.3.2 UE Configuration Update Procedure + +The UE Configuration Update procedure in clause 4.2.4.2 of TS 23.502 [5] is enhanced as follows: + +- Step 1: the AMF may include information about Conditional S-NSSAI in the Conditionally Allowed NSSAI in the UE Configuration Update Command message. + +When a temporary network slice is deployed, the AMF may update the Configured NSSAI of UE by adding the corresponding S-NSSAI and when the temporary network slice is decommissioned, the AMF updates the Configured NSSAI and optionally the Allowed NSSAI and the Conditionally Allowed NSSAI, to remove the corresponding S-NSSAI. + +### 6.11.3.3 UE Requested PDU Session Establishment Procedure + +The UE Requested PDU Session Establishment procedures in clause 4.3.2.2.1 (non-roaming and roaming with local breakout) and clause 4.3.2.2.2 (home-routed roaming) of TS 23.502 [5] are enhanced as follows: + +- Step 1: the UE can request PDU Session Establishment for a Conditional S-NSSAI only if the conditions associated to the Conditional S-NSSAI are valid. +- Step 2: the AMF verifies whether the conditions associated to the Conditional S-NSSAI are valid and, if not, the AMF rejects the request. + +### 6.11.3.4 Service Request + +The Service Request procedure in clause 4.2.3.2 of TS 23.502 [5] is enhanced as follows: + +- when the UE performs a Service Request for a Conditional S-NSSAI whose associated conditions are no longer valid and therefore is no longer available (e.g. the UE has moved outside the TA or Serving Area where the S-NSSAI is available or the time conditions have changed), the request for the resources associated to the S-NSSAI is rejected and an indication is provided to the UE as to why. If the S-NSSAI was in the Allowed NSSAI, the AMF may provide a new Allowed NSSAI and a Conditionally Allowed NSSAI to the UE. + +### 6.11.3.5 PDU Session Release + +The PDU Session Release procedures in clause 4.3.4.2 (non-roaming and roaming with local breakout) and clause 4.3.4.3 (home-routed roaming) of TS 23.502 [5] are modified as follows: + +- Step 1a in clauses 4.3.4.2 and 4.3.4.3: the UE initiates the PDU Session release when it detects that it moves out of the TA or Area of Service of the Conditional S-NSSAI associated with the PDU Session. +- Step 1c in clause 4.3.4.2: the AMF verifies whether the UE moves out of the TA(s) or Area of Service where a Conditional S-NSSAI associated with the PDU Session is available, e.g. based on the serving cell of the UE, the geographical UE location or the area type event report from LMF as described in clause 4.1a.5.1 of TS 23.273 [15] and the AMF requests the release of the PDU Session corresponding to the Conditional S-NSSAI. +- Step 1b in clause 4.3.4.3: the AMF verifies whether the UE moves out of the TA(s) or Area of Service where a Conditional S-NSSAI associated with the PDU Session is available, e.g. based on the serving cell of the UE, the geographical UE location or the area type event report from LMF as described in clause 4.1a.5.1 of TS 23.273 [15] and the AMF requests the release of the PDU Session corresponding to the Conditional S-NSSAI. + +## 6.11.4 Impacts on services, entities and interfaces + +The following impacts have been identified: + +- UE: + - interpreting and processing new information in Rejected NSSAI or new Conditional S-NSSAI IE. + - support for the Conditional S-NSSAI feature indication at registration. +- AMF: + +- providing new information in Rejected NSSAI or new Conditional S-NSSAI IE. +- providing rejection cause at Service Request. +- RAN: + +**Editor's note:** exact impacts on RAN and impacts on other NFs are to be identified. + +## 6.12 Solution #12: Solution for Centralized Counting for Multiple Service Areas and 5GS-EPS Interworking + +### 6.12.1 Description + +In this solution and in support of 5GS only slices, when multiple Service Areas are deployed, it is proposed that a single central NSACF NF performs the PLMN global counting and admission to ensure a consistent counting, e.g. such that during handover between different Service Areas no additional admission needs to be performed. The admission request includes all necessary information to enable the central NSACF NF to collect all pertinent information per Service Area. Interaction between the NF performing the admission, be it the SMF or the AMF, occurs with the designated central NSACF for that purpose. The central NSACF NF responsible for PLMN global count is discovered via NRF as per clause 6.12.2.4 or can be pre-configured. + +Two options are proposed to enable a Service Area to perform some local tasks; e.g. keeping local statistics in conjunction with centralized counting with a single central NSACF NF: + +#### **Option 1: Transparent Proxying to central NSACF NF Via an intermediate NF** + +Based on policy, an NF, e.g. SMF or AMF performing the admission with the central NSACF NF may additionally and optionally interact with a local NF associated with the Service Area, for any additional capabilities not supported by the central NSACF NF. Such additional capabilities are not specified. but can be e.g. to keep local statistics. + +The interaction with such a local NF is such, that the local NF in the Service Area proxies the original request, as is, to the central NSACF NF, after performing the tasks it desires upon receipt of the admission Request intended for the central NSACF NF. Hence, in this option1, the interaction with the central NSACF server is proxied via an intermediate NF to the central NF, as long as it is transparent to the central NSACF NF. Transparent means that the central NSACF NF cannot distinguish whether the Request is direct from the AMF/SMF or proxied via an intermediate NF. It also need ensure the response message from central NSACF go through the intermediate NF. The local NF can be configured in this option with the central NSACF, can discover the central NSACF as per clause 6.12.2.4, or can receive the information from the AMF/SMF. + +#### **Option 2: Dual Interaction with Local NF and central NSACF NF** + +Based on policy, an NF, e.g. SMF or AMF performing the admission with the central NSACF NF may additionally and optionally interact with a local NF associated with the Service Area, for any additional capabilities not supported by the central NSACF NF. Such additional capabilities are not specified. but can be e.g. to keep local statistics + +Hence the AMF/SMF performs dual interactions in parallel; once towards the central NSACF NF and an additional one towards a local NF in the Service Area. + +For both options 1 or 2, AMFs/SMFs are configured with a service area to be used for a local NF selection and a service area to be used for central NSACF selection. + +NOTE 1: These two-service areas are for two different NF discovery and selection. It can be different. + +As an additional option, the AMFs/SMFs can be configured with the local NFs to be used. The central NSACF to be used can be discovered by the appropriate NF or be configured in the appropriate NFs depending on the selected option by the PLMN. + +In support of roaming and to enable such a central NF to handle roaming UEs, as well as home bound UEs, the admission query to the central NF includes the PLMN-ID where the UE is roaming. + +To support EPS counting while interworking with 5GS when activated and where home routing is the only option for attachment to EPS, a central NSACF NF could be optionally dedicated for 5GS-EPS interworking shared count as per clause 6.12.2.4. In this case, such a dedicated NF is discovered. The PLMN can also reuse a single NSACF NF for all admissions. + +Similar to the 5GS case and based on policy, a NF performing admission with the central NSACF responsible for the shared 5GS-EPS count may additionally and optionally interact with a local NF associated with the Service Area, for any additional capabilities not supported by the central NSACF NF. Such additional capabilities are not specified. Hence, in this case as well, both options 1 and 2 above for 5GS only slices are supported for the 5GS-EPS interworking case. + +With central count regardless of any interactions with a local NF based on either option 1 or option 2, admission is solely based on the central NSACF, even if these local NFs are local NSACFs maintaining count. Given that the service area is included in the interaction with the central NSACF for all cases, see clause 6.12.2.1.1, as one example, the central NSACF is able to determine when a UE, who has a stored state in it as being registered in one service area, has moved to a new service area when a new admission request arrives from a new service area and as such the central NSACF does not perform an admission in this case. + +NOTE 2: As stated before functions performed in the local NF are out of scope. A Release 17 NSACF, as currently specified, is not expected to be used in this case as a local NF. This solution defines access to a central NSACF and any local NF must adapt to ensure compliance, depending on the adopted option. Indeed, implementations may choose not to support any local NF option for a centralized NSACF as all information is available there. However, a Release 17 NSACF is enhanced, as detailed in the procedures below, to become a centralized NSACF. + +## 6.12.2 Procedures + +### 6.12.2.1 UE Registration Admission + +#### 6.12.2.1.1 5GS only slices + +In this procedure, there is a single central NSACF NF performing the count for the entire PLMN. The AMF discovers the central NSACF NF performing the PLMN global counting. The NF profile for the NSACF is updated to indicate that the NSACF is the central NSACF for the S-NSSAI handling the PLMN global count for 5GS slices, i.e. discovery procedure in clause 5.2.7.2.2 of TS 23.502 [5] is updated and clause 6.3.22 of TS 23.501 [2] is updated and the central NSACF information can be encoded as part of the NSACF service capabilities as a specific capability or as part of the NSACF Serving Area information. + +The AMF performs admission as in clause 4.2.11.2 of TS 23.502 [5] with the following changes: + +- The AMF includes the Service Area and the PLMN ID in its request to the central NSACF NF. +- AMF performs either option 1 or option 2 below: + - In support of **option 1**, the AMF, based on policy, communicates directly with central NSACF NF or via an intermediate NF that proxies the original request unaltered to the central NSACF. The actions performed in the intermediate NF are out of scope. + - In support of **option 2**, the AMF, based on policy, sends the admission request to the central NSACF NF and sends the admission request as well to a local NF in the Service Area. The local NF performs tasks out of scope of standardization. +- The central NSACF NF does not change the number of registered UE for a UE that is moving between multiple Service Areas given that the UE has already been admitted and successfully registered in an old Service Area. In this case, the central NSACF NF performing the PLMN global counting only updates the UE stored information. + +The AMF, in case the policy is to communicate additionally with local NSACFs (option 2), updates the applicable local NSACF with the change i.e. UE leaving one Service Area and entering the new Service Area. + +With central count regardless of any interactions with a local NSACF based on either option 1 or option 2, admission is solely based on the central NSACF, even if these local NSACFs maintaining count. + +#### 6.12.2.1.2 5GS-EPS Interworking with EPS Counting Active + +In this solution, there is a shared count for maximum number of Registered UEs for interworking between 5GS and EPS. The count can be performed by a central NSACF NF dedicated for 5GS-EPC interworking, or the central NSACF NF used for 5GS slices can be used. The count can be separate or bundled with the 5GC only slices count. + +If a dedicated 5GS-EPS central NSACF NF is used, the AMF/SMF+PGW-C discovers the central NSACF NF handling the shared 5GS-EPS count for the number of Registered UEs. The NF profile for the NSACF is updated to indicate that + +the NSACF is the central NSACF for the for shared 5GS-EPS count for number of Registered UEs. i.e. clause 5.2.7.2.2 of TS 23.502 [5] is updated and clause 6.3.22 of TS 23.501 [2] is updated and the central NSACF information can be encoded as part of the NSACF service capabilities as a specific capability or as part of the shared 5GS-EPS count. + +The AMF/SMF+PGW-C performs admission as in clause 4.2.11.2 of TS 23.502 [5] with the following changes: + +- The AMF/ SMF+PGW-C includes the Service Area, the PLMN ID where the UE is currently in its request to the central NSACF responsible for shared 5GS-EPS count for number of Registered UEs +- AMF/SMF+PGW-C performs either option 1 or option 2 below: + - In support of **option 1**, the AMF/SMF+PGW-C, based on policy, communicates directly with central NSACF NF or via an intermediate NF that proxies the original request unaltered to the central NSACF. The actions performed in the intermediate NF are out of scope. + - In support of **option 2**, the AMF/SMF+PGW-C, based on policy, sends the admission request to the central NSACF NF and sends the admission request as well to a local NF in the Service Area. The local NF performs tasks out of scope of standardization. + +The NSACF NF responsible for the shared 5GS-EPS count or number of Registered UEs does not change the number of registered UE for a UE that is moving between multiple Service Areas given that the UE has already been admitted and registered in an old Service Area and counted for. The NSACF NF handling the shared 5GS-EPS count simply updates the UE stored information. + +The AMF/SMF+PGW-C, in case the policy is to communicate additionally with local NSACFs (option 2), updates the applicable local NSACF with the change i.e. UE leaving one access to another access. + +### 6.12.2.2 Roaming + +Roaming is covered by the above solution as the PLMN ID is included in an admission request, enabling the NSACF NF to identify roaming UEs. + +### 6.12.2.3 UE PDU Session Admission + +#### 6.12.2.3.1 5GS only slices + +In this procedure, the SMF discovers the central NSACF NF performing the PLMN global counting for number of PDU sessions for network slices subject to NSAC. The NF profile for the NSACF is updated to indicate that the NSACF is the central NSACF for the S-NSSAI handling the PLMN global count for the number of PDU sessions, i.e. clause 5.2.7.2.2 of TS 23.502 [5] is updated and clause 6.3.22 of TS 23.501 [2] is updated and the central NSACF information can be encoded as part of the NSACF service capabilities as a specific capability or as part of the NSACF Serving Area information. + +The SMF performs admission as in clause 4.2.11.4 of TS 23.502 [5] with the following changes: + +- The SMF includes the Service Area and the PLMN ID in its request to the central NSACF NF. +- SMF performs either option 1 or option 2 below: + - In support of **option 1**, the SMF, based on policy, communicates directly with central NSACF NF or via an intermediate NF that proxies the original request unaltered to the central NSACF. The actions performed in the intermediate NF are out of scope. + - In support of **option 2**, the SMF, based on policy, sends the admission request to the central NSACF NF and sends the admission request as well to a local NF in the Service Area. The local NF performs tasks out of scope of standardization. + +When a PDU session is handed over between two Service Areas, the central NSACF NF handling the number of PDU session does not change the number of PDU sessions if the session is successfully handed over. In case of a successful handover, the central NSACF NF performing the PLMN global counting simply updates the UE stored information. The SMF, in case the policy is to communicate additionally with local NSACFs (option 2), updates the applicable local NSACFs with the change i.e. UE leaving one Service Area and entering the new Service Area. + +With central count regardless of any interactions with a local based on either option 1 or option 2, admission is solely based on the central NSACF, even if these local NFs are local NSACFs maintaining count. + +### 6.12.2.3.2 5GS-EPS Interworking with EPS Counting Active + +In this solution, there is a shared count for maximum number of PDU sessions between 5GS and EPS performed by a central NSACF NF dedicated for that purpose, or the central NSACF NF used for 5GS slices can be used. + +If a dedicated 5GS-EPS central NSACF NF is used, the SMF/SMF+PGW-C discovers the central NSACF NF handling the shared 5GS-EPS count for the number of PDU sessions for a slice subject to NSACF. The NF profile for the NSACF is updated to indicate that the NSACF is the central NSACF for the for shared 5GS-EPS count for number of PDU sessions i.e. TS 23.502 [5] clause 5.2.7.2.2 is updated and clause 6.3.22 of TS 23.501 [2] is updated and the central NSACF information can be encoded as part of the NSACF service capabilities as a specific capability or as part of the shared 5GS-EPS count. + +The SMF/SMF+PGW-C performs admission as in clause 4.2.11.2 of TS 23.502 [5] with the following changes: + +- The SMF/ SMF+PGW-C includes the Service Area, the PLMN ID in its request to the central NSACF NF responsible for shared 5GS-EPS count for maximum number of PDU sessions. +- SMF/SMF+PGW-C performs either option 1 or option 2 below: + - In support of **option 1**, the SMF/SMF+PGW-C, based on policy, communicates directly with central NSACF NF or via an intermediate NF that proxies the original request unaltered to the central NSACF. The actions performed in the intermediate NF are out of scope. + - In support of **option 2**, the SMF/SMF+PGW-C, based on policy, sends the admission request to the central NSACF NF and sends the admission request as well to a local NF in the Service Area. The local NF performs tasks out of scope of standardization. + +When a PDU session is handed over between 5GS and EPS, the central NSACF NF handling the number of PDU session does not change the number of PDU sessions if the session is successfully handed over between 5GS and EPS. In case of a successful handover, the NSACF NF handling the shared 5GS-EPS count simply updates the UE stored information. + +The SMF/SMF+PGW-C, in case the policy is to communicate additionally with local NSACFs (option 2), updates the applicable local NSACF with the change i.e. UE leaving one access to another access. + +### 6.12.2.4 Discovery of Central NSACF + +Currently following factors may be considered by the NF consumer for NSACF selection: + +- S-NSSAI(s). +- NSACF Serving Area information. The NSACF service area is related to the location of the NF consumer. + +NOTE: Each Serving Area is unique and unambiguously identified. + +For central counting, a PLMN shall include a service area unambiguously identified for that purpose. This could be as an example, the PLMN ID. In roaming case the PLMN ID is the HPLMN ID. Stage 3 makes the final determination This enables an AMF/SMF utilizing centralized counting to be able to select the appropriate NSACF. + +If applicable an NSACF can be utilized exclusively for 5GC EPC interworking, when EPC and 5GC have a joint admission counting between them. In this case, there shall be an NSACF service area distinctly and unambiguously identified for that purpose. A PLMN can only have only one NSACF for that purpose used by both EPC and 5GC for admission purposes in this case. This NSACF is also utilized for home and outbound roamers in all VPLMNs. + +## 6.12.3 Impacts on services, entities and interfaces + +NSACF: Enhanced to support reception of service area in an incoming request, detecting a UE moving between service areas to avoid admission, as well as registering its capabilities in NRF. + +AMF: + +- To perform discovery and may support either option 1 or option 2. +- Include the service area and PLMN ID for admission control. + +SMF: + +- To perform discovery and may support either option or option 2. +- Include the service area and PLMN ID for admission control. + +Local NF: Optional NF. The functionality provided by this local NF is out of scope. However, it need be able to discover the central NSACF. If this NF is deployed in support of option1, it must ensure that it can proxy a received request from an AMF /SMF in the service area served by this local NF transparently to the central NSACF as well as the received responses back to the corresponding request in the initiating AMF/SMF. + +NOTE: The local statistics is to be executed at the local NF is out of scope. + +## 6.13 Solution #13: Hierarchical NSACF Architecture for Maximum UE/PDU Session number control + +### 6.13.1 Introduction + +This is a solution to Key Issue #4, "Support of NSAC involving multi service Area". + +As defined in Rel-17 an NSACF is deployed on a service area basis, which can be one NSACF instance or one NSACF Set. Each NSACF performs maximum number of registered UE or established PDU session number control independently. It is possible that UE registration or PDU session establishment is rejected by the network due to the maximum number of UE/PDU session is reached at the current serving NSACF even the maximum number may still be available at other NSACF. This also impacts the session continuity when the UE moves across the service area. + +Thus how to enhance the NSAC mechanism when multi NSACFs are deployed at the network needs to be considered. In addition, a particular case of Multiple NSACFs may be in a roaming use case and this should also be covered. + +### 6.13.2 Functional Description + +The hierarchical NSACF architecture for the control of the maximum number of registered UEs is shown as the Figure 6.13.2-1. For an S-NSSAI, one NSACF acting as Primary NSACF is introduced. Other NSACFs take the same role as the existing NSACF, i.e. serving one service area. The Primary NSACF and NSACF is the enhancement of the NSACF defined in Rel-17 to support centralized management of a single maximum number of UEs or PDU sessions. + +The slice SLA attribute (e.g. Maximum number of UEs), i.e. the global maximum number value valid across Service Areas, is only configured at the Primary NSACF. The global maximum number value is shared among different service area(s). The Primary NSACF registers its NF profile to the NRF, which can be discovered by other NF. The NF profile of the Primary NSACF includes the information that for the indicated S-NSSAI it manages for all service areas, i.e. the global service area. + +![Diagram of Hierarchical NSACF Architecture for UE number control (non-roaming case).](1230eaa9d75a09d7e7b8509931e9190e_img.jpg) + +The diagram illustrates a hierarchical NSACF architecture. At the top is the 'Primary NSACF'. Below it are two 'NSACF' boxes. The left 'NSACF' is connected to 'AMF1' and 'AMF2' via 'N80' interfaces. The right 'NSACF' is connected to 'AMF3' and 'AMF4' via 'N80' interfaces. The 'Primary NSACF' is connected to both 'NSACF' boxes via 'Nxx' interfaces. A dashed vertical line separates the left and right sides. Below the AMFs, 'Service Area-1' is labeled under AMF1 and AMF2, and 'Service Area-2' is labeled under AMF3 and AMF4. + +Diagram of Hierarchical NSACF Architecture for UE number control (non-roaming case). + +**Nxx:** Reference point between Primary NSACF and NSACF. + +**Figure 6.13.2-1: Hierarchical NSACF Architecture for UE number control(non-roaming case)** + +![Diagram of Hierarchical NSACF Architecture (Roaming case).](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates a hierarchical NSACF architecture. At the top, a box labeled 'Primary NSACF' is connected to two boxes labeled 'NSACF' via lines labeled 'Nyy'. A horizontal dashed line separates the 'Primary NSACF' from the 'NSACF' boxes. Below the left 'NSACF' box, two boxes labeled 'AMF 1' and 'AMF 2' are connected to it via lines labeled 'N80'. Below the right 'NSACF' box, two boxes labeled 'AMF 3' and 'AMF 4' are connected to it via lines labeled 'N80'. A vertical dashed line separates the left and right sides of the diagram. The label 'HPLMN' is at the top right. The label 'VPLMN 1' is at the bottom left, and 'VPLMN2' is at the bottom right. + +Diagram of Hierarchical NSACF Architecture (Roaming case). + +**Nyy:** Reference point between Primary NSACF and NSACF. + +**Figure 6.13.2-2: Hierarchical NSACF Architecture (Roaming case)** + +With the replacement of the AMF with SMF or SMF+PGW-c, the same architecture is used for the enforcement of a maximum number of PDU session. In roaming cases the NSACF interacting with primary NSACF, which is located at the HPLMN, for the mapped S-NSSAI of the VPLMN. + +To improve the signalling efficiency the Primary NSACF may allocate to each of the NSACF a partial amount of the global maximum number that is required to be enforced. When the AMF or SMF(+PGW-C) interact with a NSACF, if the local maximum number at the NSACF is reached, the NSACF interacts with the Primary NSACF to check whether there is more allowance for the specific S-NSSAI. + +For the NEF subscription on the value of the registered UE number or PDU session number or UEs with at least one PDU session number, same handling as the multi NSACF defined in TS 23.502 [5] is executed, i.e. the NRF return the primary NSACF and other NSACFs to the NEF and NEF subscribes and get notification from primary NSACF and other NSACFs as before. + +As an alternative mechanism, the subscription from NEF can be only point to the primary NSACF. In this case the NEF invoke the subscription with the primary NSACF and Primary NSACF collect the information from the NSACFs. Per the subscription event filter, the primary NSACF notify the NEF when the event if fulfilled. + +## 6.13.3 Procedures + +### 6.13.3.1 Registration management Procedures + +![Sequence diagram illustrating the NSAC check of the maximum number of UEs. The diagram shows interactions between AMF, NSACF, and Primary NSACF. The process starts with a trigger in the AMF, followed by a request to the NSACF. The NSACF performs a local check and then discovers/selections the Primary NSACF. It then sends a request to the Primary NSACF, which performs an update and check. The Primary NSACF returns a response to the NSACF, which then performs a final local check and update before returning a response to the AMF.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NSACF + participant Primary NSACF + + Note left of AMF: 1. A trigger to perform number of UEs per network slice availability check and update + AMF->>NSACF: 2.Nnsacf_NSAC_NumberOfUEsUpdate_Request + Note right of NSACF: 3. The number of UEs per network slice availability check and update + Note right of NSACF: 4. Primary NSACF Discovery/Selection + NSACF-->>Primary NSACF: 5.Nnsacf_NSAC_NumberOfUEsUpdate_Request + Note right of Primary NSACF: 6. NSAC for update and check against max. allowed UE of an S-NSSAI + Primary NSACF-->>NSACF: 7. Nnsacf_NSAC_NumberOfUEsUpdate_Response + Note right of NSACF: 8. The number of UEs per network slice availability check and update using the updated local maximum number of UE + NSACF-->>AMF: 9.Nnsacf_NSAC_NumberOfUEsUpdate_Response + +``` + +Sequence diagram illustrating the NSAC check of the maximum number of UEs. The diagram shows interactions between AMF, NSACF, and Primary NSACF. The process starts with a trigger in the AMF, followed by a request to the NSACF. The NSACF performs a local check and then discovers/selections the Primary NSACF. It then sends a request to the Primary NSACF, which performs an update and check. The Primary NSACF returns a response to the NSACF, which then performs a final local check and update before returning a response to the AMF. + +**Figure 6.13.3.1-1: NSAC check of the maximum number of UEs** + +If a S-NSSAI is subject to counting of registered UEs, it can be determined based on subscription. This simplifies the configuration in roaming and non-roaming cases. Also, this enables to indicate per VPLMN whether the feature is activated for a S-NSSAI to the VPLMN. + +For a S-NSSAI subject to counting of the number of registered UEs, the enforcement of maximum number of UEs registered for an S-NSSAI is performed as follow: + +1-2. Same as the steps 1-2 defined in clause 4.2.11.2 of TS 23.502 [5]. + +3. The NSACF performs NSAC for the indicated S-NSSAI. + +If the update flag parameter from the AMF indicates increase, + +- If the local maximum number of UEs is not yet reached, the NSACF execute same as step 3 defined in clause 4.2.11.2 of TS 23.502 [5]. Steps 4-8 are skipped. +- If the local maximum number of UEs is reached by admitting the UE and the Primary NSACF does not indicate to reject the further admission in an earlier interaction, the NSACF interact with the Primary NSACF. Step 4-8 are executed. + +If the update flag parameter from the AMF indicates decrease, + +- If the UE entry to be deleted is stored at the NSACF, i.e. the UE entry with the same UE ID, NF ID and Access type is stored at the NSACF, the NSACF execute same as step 3 defined in clause 4.2.11.2 of TS 23.502 [5]. Steps 4-8 are skipped. +- If the UE entry to be deleted is not stored at the NSACF, the NSACF interact with the Primary NSACF. Steps 4-8 are executed. + +4. If the Primary NSACF has not been discovered before, the NSACF discovers and selects the Primary NSACF, which manages the global service area. + +5. The NSACF invokes Nnsacf\_NSAC\_NumberOfUEsUpdate\_Request to the Primary NSACF. + +The NSACF forwards the update request to the Primary NSACF. If the update flag parameter from the AMF indicates increase, the NSACF also include the current local maximum number of UEs, which is the last received from the Primary NSACF, i.e. the configured one before. + +6. The Primary NSACF performs NSAC for the indicated S-NSSAI. + +If the update flag parameter from the NSACF indicates increase and the local maximum number is received by the Primary NSACF from the NSACF, per operator's policy, the Primary NSACF may delegate the subsequent NSAC update request to the NSACF. If the following NSAC update request is delegated to the NSACF, the Primary NSACF increases the local maximum number of UEs allocated to the NSACF and does not store the received UE ID information. + +If the update flag parameter from the NSACF indicates increase and the subsequent NSAC update request is expected to be handled at the Primary NSACF due to local maximum number is reached: + +- If the Primary NSACF has not allocated the complete range of the global maximum number, per the received UE ID information the UE entry stored at the Primary NSACF is updated for the related UE ID, including the NF ID and Access type. +- If the Primary NSACF has allocated the complete range of the global maximum number , then the UE cannot be granted admission if the UE does the initial registration. However SC can still be supported if the UE ID was managed by the primary NSACF when the UE first registered for admission in an old SA served by a local NSACF that forwarded the requested to the primary NSACF. + +NOTE 1: For the whole global maximum number, the maximum number managed by the primary NSACF is the last one to be reached. Before the maximum number managed by Primary NSACF is nearly to be consumed, the primary NSACF can decrease the local maximum number of registered UEs according to step 4 of clause 6.13.3.3 for those local NSACFs that are below a configured usage threshold. + +If the update flag parameter from the NSACF indicates decrease and the UE entry is managed by the primary NSACF, per the received UE ID information the UE entry stored at the Primary NSACF is updated for the related UE ID, including the NF ID and Access type. + +NOTE 2: The UE entry managed by the Primary NSACF is used to support the session continuity when the UE moves to the new service area and the local maximum number is reached at the target NSACF. + +If the update flag parameter from the NSACF indicates decrease, the Primary NSACF updates the UE entry for the related UE ID, NF ID and Access type. + +7. The Primary NSACF returns the Nnsacf\_NSAC\_NumberOfUEsUpdate\_Response. If the local maximum number of UEs is increased by the Primary NSACF, the updated local maximum number of UEs is also included, i.e. the updated configured value at the NSACF. + +8. The NSACF checks the response from primary NSACF and determines whether it need update the UE entry stored at the NSACF. + +If a new local maximum number of UEs is received from Primary NSACF, the NSACF replaces the local maximum number of UEs with the received updated value and update the UE entry for the related UE ID, NF ID and Access type. In other case the NSACF forwards the response to the AMF. + +9. Same as the step 4 defined in clause 4.2.11.2 of TS 23.502 [5]. + +### 6.13.3.2 PDU Session management Procedures + +![Sequence diagram illustrating the NSAC check of the maximum number of PDU Sessions. The diagram shows interactions between SMF, NSACF, and Primary NSACF. The SMF triggers a check (1), sends a request (2) to the NSACF. The NSACF performs a check (3) and discovers the Primary NSACF (4). The NSACF sends a request (5) to the Primary NSACF. The Primary NSACF updates and checks (6) and sends a response (7) to the NSACF. The NSACF performs another check (8) and sends a response (9) to the SMF.](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant NSACF + participant Primary NSACF + + Note left of SMF: 1. A trigger to perform number of PDUs per network slice availability check and update + SMF->>NSACF: 2.Nnsacf_NSAC_NumberOfPDUsUpdate_Request + Note right of NSACF: 3. The number of PDUs per network slice availability check and update + Note right of NSACF: 4. Primary NSACF Discovery/Selection + NSACF->>Primary NSACF: 5.Nnsacf_NSAC_NumberUpdate_Request + Note right of Primary NSACF: 6. Update and check against max. allowed PDU Sessions of an S-NSSAI + Primary NSACF-->>NSACF: 7.Nnsacf_NSAC_NumberUpdate_Response + Note right of NSACF: 8. The number of PDUs per network slice availability check and update using the updated local Maximum number + NSACF-->>SMF: 9.Nnsacf_NSAC_NumberOfPDUsUpdate_Response + +``` + +Sequence diagram illustrating the NSAC check of the maximum number of PDU Sessions. The diagram shows interactions between SMF, NSACF, and Primary NSACF. The SMF triggers a check (1), sends a request (2) to the NSACF. The NSACF performs a check (3) and discovers the Primary NSACF (4). The NSACF sends a request (5) to the Primary NSACF. The Primary NSACF updates and checks (6) and sends a response (7) to the NSACF. The NSACF performs another check (8) and sends a response (9) to the SMF. + +**Figure 6.13.3.2-1: NSAC check of the maximum number of PDU Sessions** + +If a S-NSSAI is subject to counting of PDU sessions, it can be determined based on subscription information. This simplifies the configuration in roaming and non-roaming cases. Also, this enables to indicate per VPLMN whether the feature is activated for a S-NSSAI to the VPLMN. + +For a S-NSSAI subject to counting of the number of PDU sessions, the enforcement of maximum number of PDU Session established for an S-NSSAI is performed as follow: + +1-2. Same as the steps 1-2 defined in clause 4.2.11.4 of TS 23.502 [5]. + +3. The NSACF performs NSAC for the indicated S-NSSAI. + +If the UE entry update at the NSACF is possible, e.g. Adding the associated PDU session ID for increase case or removing the associated PDU session ID for decrease case, same as step 3 defined in clause 4.2.11.4 of TS 23.502 [5] is executed. Steps 4-8 are skipped. + +If the UE entry update at the NSACF is impossible, i.e. the update flag parameter from the SMF(+PGW-C) indicates increase and by admitting the PDU session the local maximum PDU session number is reached, the NSACF interacts with the Primary NSACF unless the Primary NSACF indicated to reject further PDU sessions in earlier interaction with a cause code (e.g. maximum number of PDU sessions reached). Step 4-8 are executed. + +If the Primary NSACF indicates to reject the further admission before, the NSACF reject the admission of the new established PDU session. Step 4-8 are skipped. + +4. If the Primary NSACF has not been discovered before, the NSACF discovers and selects the Primary NSACF, which manages the global service area. + +5. The NSACF invokes Nnsacf\_NSAC\_NumberUpdate\_Request to the Primary NSACF. The message includes the S-NSSAI, requested local maximum PDU session number, i.e. increasing the local maximum PDU session number. + +6. The Primary NSACF checks the global maximum PDU session number and determine whether accept or reject the requested the local maximum PDU session number from NSACF, i.e. whether the update of the local maximum PDU session number of NSACF is accepted or not. If the Primary NSACF has no more available + +allowance for maximum number of PDU sessions, the Primary NSACF may indicate to NSACF to reject any new increase request. At any time, the Primary NSACF may notify NSACF to remove the indication of reject any new increase request if it has been notified to NSACF in earlier interaction. + +7. The Primary NSACF returns the Nnsacf\_NSAC\_NumberUpdate\_Response. The response may include a new allocated local maximum PDU session number, or it may return indication to reject any further new PDU sessions with a cause code. +8. If the primary NSACF provides a new allowance e.g. for the number of PDU sessions, the NSACF replaces the local maximum PDU session number with the received allocated local maximum PDU session number value. If the allocated local maximum PDU session number is increasing, the NSACF creates or adds the associated PDU session ID into the UE entry. Otherwise the NSACF rejects the permission to establish the PDU session as indicated. +9. Same as the step 4 defined in clause 4.2.11.4 of TS 23.502 [5]. + +### 6.13.3.3 Redistribution of local maximum number + +![Sequence diagram illustrating the redistribution of local maximum number between NSACF and Primary NSACF.](4842f073775fb1e84d101c02fd74e59e_img.jpg) + +``` + +sequenceDiagram + participant NSACF + participant Primary NSACF + Note right of Primary NSACF: 3. A trigger to update local Maximum value + NSACF->>Primary NSACF: 1.Nnsacf_SliceEventExposure_Subscribe + Primary NSACF-->>NSACF: 2.Nnsacf_SliceEventExposure_Notify + Primary NSACF->>NSACF: 4.Nnsacf_NSAC_NumberUpdate_Request + Note left of NSACF: 5. Local Maximum number value update + NSACF-->>Primary NSACF: 6.Nnsacf_NSAC_NumberUpdate_Response + +``` + +The sequence diagram shows the interaction between NSACF and Primary NSACF for redistributing the local maximum number. The steps are: + + +- NSACF sends a `1.Nnsacf_SliceEventExposure_Subscribe` message to Primary NSACF. +- Primary NSACF responds with `2.Nnsacf_SliceEventExposure_Notify`. +- A trigger to update the local Maximum value occurs at the Primary NSACF. +- Primary NSACF sends a `4.Nnsacf_NSAC_NumberUpdate_Request` message to NSACF. +- NSACF performs a `5. Local Maximum number value update`. +- NSACF returns a `6.Nnsacf_NSAC_NumberUpdate_Response` message to Primary NSACF. + +Sequence diagram illustrating the redistribution of local maximum number between NSACF and Primary NSACF. + +**Figure 6.13.3.3-1: Redistribution of local maximum number** + +At any time the Primary NSACF may update the allocated local Maximum number of UE or PDU session configured at the NSACF as follow: + +- 1-2. The Primary NSACF subscribes the slice event exposure service from the NSACF. This is to get the status of the current registered number of UE or established PDU session number. Per the subscription, the NSACF notifies the status of the current registered number of UE or established PDU session number based on the configured value to the Primary NSCAF periodically or when above or below the configured threshold per the event subscribed. +3. Per the received current registered UE/PDU session number at NSACFs and operator's policy, the Primary NSACF decides to update the local maximum UE/PDU session number values at the NSACF(s), i.e. the configured value. +4. The Primary NSACF invokes `Nnsacf_NSAC_NumberUpdate_Request` to the NSACF. The message includes the allocated new local maximum number. +5. The NSACF replaces the local maximum number with the received new local maximum number value. +6. The NSACF returns the `Nnsacf_NSAC_NumberUpdate_Response`. + +### 6.13.3.4 Session continuity handling + +For maximum number of PDU session control, there is no impact on PDU session handling in case of UE mobility across service area. + +For maximum number of UE control, the NSACF discovered by the AMF (or SMF+PGW-C) is deployed as the following: + +- Different service area within one PLMN: the NSACF is deployed in each service area. +- Roaming: the NSACF is located at the VPLMN. +- EPS interworking: when the UE camps at the EPS network, the SMF+PGW-C select the NSACF at the serving PLMN or the NSACF at the HPLMN depending on whether the PDU session is LBO PDU session or HR PDU session. When the UE camps at the 5GS network, the AMF selects the NSACF at the camping service area of the serving PLMN. + +In all above cases there is only one Primary NSACF instance or one NSACF Set, which is located at the HPLMN. + +When UE moves across different service area, different NSACF may be interacted to perform the maximum UE number control. If local Maximum number is not reached at the target NSACF, the NSACF accepts the UE registration at the new service area. If local Maximum number is reached, the target NSACF delegates the NSAC request to the Primary NSACF. The Primary NSACF updates the UE ID entry per the received UE ID information until the maximum number at the Primary NSACF is reached. Thus even if the local maximum number at one NSACF is reached, the session continuity is still supported. + +As the Primary NSACF can balance the maximum number among different NSACFs and also manage the UE ID directly, in general, the support of session continuity when UE move to a new service area should be no issue. + +### 6.13.3.5 HPLMN control and EPS counting support + +Per the S2-2202800, GSMA has sent the new NSAC requirement. It includes two parts: + +1. NSAC controlled by the HPLMN for UE/PDU session number control. + +This is supported with the Primary NSACF located at the HPLMN. + +### 6.13.4 Impacts on services, entities and interfaces + +The following impacts are foreseen by this solution: + +NSACF: + +- A new NSACF type, i.e. Primary NSACF, is introduced. Compare to the Rel-17 NSACF function, it manages the global Maximum number value and distribute global Maximum number to NSACF additionally. +- Support the update of the local Maximum number per the instruction from Primary NSACF. +- Determines whether the UE ID entry update is to be performed at the NSACF or Primary NSACF. +- Support the update of PDU session number. + +UDM/AMF/SMF: + +- New subscription data to support the NSAC control, EPS counting, EPS counting with at least one PDU session. + +NEF: + +- For the slice status subscription, only do the subscription with the Primary NSACF. + +## 6.14 Solution #14: Maximum Number Distribution in multiple NSACFs + +### 6.14.1 Introduction + +This solution aims to address the KI#4: Support of NSAC involving multi service Area. This solution can be applicable to both non roaming scenario and roaming scenario. + +NOTE: This solution doesn't resolve the service continuity issue. + +## 6.14.2 Functional Description + +In this solution, there is one centralized NSACF controlling the overall maximum number of UEs and maximum number of PDU Sessions of the S-NSSAI. The distributed NSACF requests the local maximum number from the centralized NSACF. The centralized NSACF may also update the local maximum number to the related NSACFs, + +In roaming case the NSACF in VPLMN interacts with the centralized NSACF in the HPLMN to retrieve the local maximum number and perform the NSAC locally. + +The central NSACF may invoke Nnsacf\_SliceEventExposure service to request the number of UE and number of PDU session in each distributed NSACF. + +*Editor's note: It is FFS whether the central NSACF is a new node and resolve it at next meeting.* + +## 6.14.3 Procedure + +![Sequence diagram showing the procedure for maximum number distribution between a Distributed NSACF and a Centralized NSACF.](8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg) + +``` +sequenceDiagram + participant Distributed NSACF + participant Centralized NSACF + Note right of Distributed NSACF: 1. Local Maximum Number Request + Distributed NSACF->>Centralized NSACF: 1. Local Maximum Number Request + Note left of Centralized NSACF: 2. Local Maximum Number Response + Centralized NSACF-->>Distributed NSACF: 2. Local Maximum Number Response + Note left of Centralized NSACF: 3. Local Maximum Number Update + Centralized NSACF-->>Distributed NSACF: 3. Local Maximum Number Update + Note right of Distributed NSACF: 4. Local Maximum Number Response + Distributed NSACF->>Centralized NSACF: 4. Local Maximum Number Response +``` + +Sequence diagram showing the procedure for maximum number distribution between a Distributed NSACF and a Centralized NSACF. + +**Figure 6.14.3-1: Procedure for Maximum Number Distribution in multiple NSACFs** + +1. When there is no local maximum number in NSACF, or the number of UE or number of PDU session of the S-NSSAI will reach the local maximum number in the NSACF , it sends Local Maximum Number Request to centralized NSACF to request a new local maximum number. +2. If the request is accepted, the central NSACF sends a new maximum number to the NSACF. The NSACF stores the new local maximum number of the S-NSSAI. +3. At any time the centralized NSACF may send Local Maximum Number update message to update the local maximum number in the NSACF which has requested the local maximum number. +4. The NSACF stores the new local maximum value and send response message to the centralized NSACF. + +## 6.14.4 Impacts on services, entities and interfaces + +### NSACF: + +- new interaction between NSACFs for maximum number distribution. + +## 6.15 Solution #15: Service continuity in case of Network Slice instance overload + +### 6.15.1 Introduction + +Based on the operator's operational or deployment needs, an S-NSSAI can be associated with one or more Network Slice instances. Based on the clause 5.15.2.1 of TS 23.501 [2], 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. + +The overall concept of Early Binding and Late Binding for Network Slice instance selection are as follows since Rel-15: + +- Early Binding (EB) - Associating the UE with the selected NSI(s) according to the UE's Allowed S-NSSAI(s) upon the successful UE registration. The identification of the selected target serving NSI corresponding to the Allowed S-NSSAI and the serving NRF for the target NSI are identified and responded to the serving AMF to support future PDU session establishment. +- Late Binding (LB) - Associating the UE with Allowed S-NSSAI upon the successful UE registration, however, the selection of the target NSI happens only when receiving the first PDU session establishment request for the specific Allowed S-NSSAI. Once the target NSI is selected, the serving NRF for the target NSI is also selected to progress the PDU session establishment procedure. + +As a consequence of only one Network Slice instance associated with a given S-NSSAI to serve UE, the AMF is constrained to discover SMF using the same Network Slice instance for a given S-NSSAI, once the Network Slice instance is selected by NSSF to serve UE that is allowed to use this S-NSSAI. Therefore, the case where this Network Slice instance is overloaded occurs. + +This is a solution to Key Issue#1, "Support of Network Slice Service continuity", which proposes Network Slice instance reselection for a given S-NSSAI, in order to alleviate current load status of selected Network Slice instance. + +This solution applies to both no mobility scenario and inter RA Mobility scenario. + +### 6.15.2 Functional Description + +This solution is applied as follows: + +- It is assumed that the SMFs within the Network Slice instance are aware whether the Network Slice instance is overloaded. When the existing PDU session is decided as to be migrated to another Network Slice instance, the SMF performs PDU Session re-establishment by using the mechanism of SSC mode#2 or SSC mode#3. +- If there are multiple existing PDU sessions associated with the Network Slice instance, the SMF decides which existing PDU sessions need to be migrated to another Network Slice instance based on, e.g. SSC mode and other local policy. In order to prevent resource overload within the new Network Slice instance, the SMF may select parts of existing PDU sessions to be migrated. +- The AMF is notified that the event that the Network Slice instance for a given S-NSSAI is overloaded, e.g. from OAM. The stored NSI ID that identifies the Network Slice instance that is overloaded is deleted by AMF from the UE context. Then AMF will query NSSF to select a suitable Network Slice instance for the new PDU session requested by UE. + +### 6.15.3 Procedures + +![Sequence diagram illustrating the procedure of PDU Session re-establishment due to Network Slice instance overload. The diagram shows interactions between UE, AMF, NSSF, SMF (old NSI), and SMF (new NSI).](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant NSSF + participant SMF_old as SMF (old NSI) + participant SMF_new as SMF (new NSI) + + Note right of AMF: 1a. Be aware of the event that the Network Slice instance is overloaded + Note right of SMF_old: 1b. Be aware of the event that the Network Slice instance is overloaded + Note right of AMF: 2a. Deleting the NSI ID that identifies the Network Slice instance that is overloaded + AMF->>UE: 2b-1. SSC mode 2: PDU Session Release Command message + AMF->>UE: 2b-2. SSC mode 3: PDU Session Modification Command + UE->>AMF: 3. PDU session establishment Request + Note right of SMF_old: 4. Existing procedure of Network Slice instance selection + Note right of SMF_new: 5. Other steps of the PDU session establishment procedure + +``` + +Sequence diagram illustrating the procedure of PDU Session re-establishment due to Network Slice instance overload. The diagram shows interactions between UE, AMF, NSSF, SMF (old NSI), and SMF (new NSI). + +**Figure 6.15.3-1: Procedure of PDU Session re-establishment due to Network Slice instance overload** + +1. The AMF and SMF are aware of the event that the Network Slice instance for a given S-NSSAI is overloaded, e.g. based on OAM. +2. If this overloaded Network Slice instance is previously selected for UE, the stored NS ID that identifies the Network Slice instance that is overloaded is deleted by AMF from the UE context. For existing PDU sessions associated with the Network Slice instance, the SMF performs PDU Session re-establishment by using the mechanism of SSC mode#2 or SSC mode#3 as defined in clause 4.3.5 of TS 23.502 [5]. If there are multiple existing PDU sessions associated with the Network Slice instance, the SMF decides which existing PDU sessions need to be migrated to the new Network Slice instance based on, e.g. SSC mode and other local policy. +3. The UE initiates PDU Session Establishment procedure as indicated by SMF, which requests to establish a new PDU session associated with same S-NSSAI as the existing PDU session. +4. Existing procedure as described in clause 4.3.2.2.3 of TS 23.502 [5] for SMF selection is performed, where new NSI ID is determined for the same S-NSSAI. +5. Other steps of the PDU Session Establishment procedure. A new SMF within the new Network Slice instance serves current PDU session. The old PDU Session is released as described in the TS 23.502 [5]. + +### 6.15.4 Impacts on services, entities and interfaces + +AMF: + +- Deleting the NSI ID that identifies the Network Slice instance that is overloaded. + +SMF: + +- A new condition to trigger PDU Session re-establishment by using the mechanism of SSC mode#2 or SSC mode#3. + +## 6.16 Solution #16: UE assisted slice based VPLMN prioritization for Extended SoR + +### 6.16.1 Introduction + +Solution # 6 proposes a solution to KI #2. The solution relies on the UE indicating its location to HPLMN and makes the following assumption: "A trigger is detected in the UDM for a roaming UE to provide slice-based SoR information, e.g. the UDM is preconfigured (e.g. via the OAM or OSS based on Service Level Agreements with the roaming partners) that one or more of the UE's Subscribed S-NSSAIs are not available in specific visited country or networks (VPLMNs)." + +However, there may be limitations with these assumptions: + +- a) Network Slice support may vary (statically or dynamically) at cell level within the same RAN belonging to a VPLMN. It is impractical to assume that all VPLMNs will provide up-to-date geographical network slice support information to HPLMN under the SLA. +- b) HPLMN may not be aware of the availability (visibility or suitability for camping) of all VPLMNs in the UE's current location. +- c) In some cases, the UE itself may be unable to report its detailed location. E.g. not all mMTC devices can be expected to have positioning capabilities (i.e. equipped with a GNSS or A-GNSS receiver) or privacy permissions as described in TS 22.071 [10]. + +To overcome these limitations, this solution adds a UE assisted enhancement to the VPLMN prioritization in solution #6. + +### 6.16.2 High Level Description + +A UE performs PLMN selection as described in TS 23.122 [7]. "PLMN Search" is a procedure to support the PLMN selection as detailed in clause 5.1.1 of TS 38.304 [9]. "PLMN Search" is triggered in several scenarios like the switch-on, recovery from lack of coverage or periodic attempt to obtain service on HPLMN (while roaming). + +From Release 17 of TS 38.331 [11], the supported slice info of the current cell and neighbour cells is optionally broadcast in SIB 16 (this was agreed in RP-220490 and then subsequently became part of V17.0.0). Under these conditions, during PLMN Search the UE can additionally read the supported slice information and provide it to the network for prioritizing the available VPLMNs for selection. + +The solution is based on the following high-level assumptions and principles: + +- The UE is configured with S-NSSAIs which are supported by some cells (strongest cell or neighbour cells) in the Registration area. +- The NG-RAN is broadcasting the supported slice info of the current cell and neighbour cells. +- If a roaming UE activates a service/application requiring a network slice not offered by the serving network, it may deregister and trigger a PLMN Search followed by re-registration. + +**Editor's note:** This solution is applicable only when there is a need for PLMN (re)selection. In mobility cases, a deregistration and PLMN Search is not needed if the UE can find another cell that supports the network slice within the serving PLMN, using cell reselection (TR 38.832 [3]) or solutions for KI #1. It is FFS whether any UE assistance is needed by HPLMN for updated slice info in such cases. + +### 6.16.3 Procedures + +Existing PLMN search and selection procedures are used with some changes shown in Figure 6.16.3-1. In this figure, three RANs belonging to three different PLMNs are represented for illustration purpose. + +![Sequence diagram illustrating UE assisted slice based VPLMN prioritization for Extended SoR. The diagram shows interactions between a UE, three VPLMNs (VPLMN1, VPLMN2, VPLMN3), and the HPLMN. The process starts with the UE having S-NSSAI configured, followed by an Extended PLMN Search (steps 1-4). The UE then builds a list of available VPLMN IDs and slice info. The HPLMN's SoR AF inquires about slice mapping info for some VPLMNs (steps 6a and 6b). Finally, the UE proceeds with registration steps 5-9, taking into account the available VPLMN + slice info list.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +The diagram illustrates the following sequence of events: + +- 1. UE has S-NSSAI configured**: Initial state of the UE. +- Extended PLMN Search**: A phase containing: + - 2. PLMN Search**: The UE searches for available PLMNs. + - 3a. System Info (with slice info)**: The UE reads system information from the strongest cell. + - 3b. System Info (with slice info)**: The UE reads system information from neighbour cells (if broadcast). +- 4. UE builds {VPLMN + slice Info} list**: The UE compiles a list of available VPLMNs and their associated slice information. +- 5. Figure 6.6.3.1.1-1 steps 1 ~ 4**: The UE begins the registration process, including the transmission of the {available VPLMN + slice info} list. +- 6a. Namf\_Communication\_Request/Response (slice mapping info)**: The SoR AF in the HPLMN inquires about slice mapping info for VPLMN1. +- 6b. Namf\_Communication\_Request/Response (slice mapping info)**: The SoR AF in the HPLMN inquires about slice mapping info for VPLMN2. +- 7. Figure 6.6.3.1.1-1 steps 5 ~ 9**: The UE completes the registration process, prioritizing VPLMNs based on the collected information. + +Sequence diagram illustrating UE assisted slice based VPLMN prioritization for Extended SoR. The diagram shows interactions between a UE, three VPLMNs (VPLMN1, VPLMN2, VPLMN3), and the HPLMN. The process starts with the UE having S-NSSAI configured, followed by an Extended PLMN Search (steps 1-4). The UE then builds a list of available VPLMN IDs and slice info. The HPLMN's SoR AF inquires about slice mapping info for some VPLMNs (steps 6a and 6b). Finally, the UE proceeds with registration steps 5-9, taking into account the available VPLMN + slice info list. + +**Figure 6.16.3-1: UE assisted slice based VPLMN prioritization for Extended SoR.** + +The various steps of Figure 6.16.3-1 are described below: + +- The UE has been configured with S-NSSAI and needs to do a PLMN Search due to e.g.: + - Switch on/recovery from lack of coverage; or + - Activation of a service/application requiring a network slice not offered by the serving network. + - The UE performs a PLMN Search as described in clause 5.1.1 of TS 38.304 [9]. + - a) and b). During PLMN Search, the UE reads system information of the strongest cell in particular band, in order to find out which PLMN(s) the cell belongs to and any associated CAG(s). Additionally, it reads system information (SIB16) for the supported slice info of the current cell and neighbour cells (if broadcast). +- NOTE 1: For illustration purposes, in Figure 6.16.3-1, two out of three VPLMNs are broadcasting the supported slice info. +- NOTE 2: In Figure 6.16.3-1, steps 2 and 3 are labelled as 'Extended PLMN Search'. +- The UE builds a list of available VPLMN ids and the corresponding slice info (if broadcast). + - The UE proceeds with registration as in clause 6.6.3.1.1 and includes the {available VPLMN + slice info} list in the transparent container (steps 1 ~ 4 of Figure 6.6.3.1.1-1). + - a) and/or b). Optionally, if the slice mapping info for some VPLMNs is not known, SoR AF in the HPLMN (Figure 6.6.3.1.1-1) may first inquire the AMF belonging to that VPLMN. + - The UE proceeds with steps 5 ~ 9 of Figure 6.6.3.1.1-1. In step 5, SoR AF takes into account the {available VPLMN + slice info} list before generating the prioritized list of VPLMNs. + +## 6.16.4 Impacts on services, entities and interfaces + +The impacts to the 5GS entities are the following: + +UE: + +- PLMN Search procedure in clause 5.1.1 of TS 38.304 [9] is modified to additionally read supported slice info of the serving and neighbour cells. The rest of PLMN selection, cell selection and registration procedures remain unchanged. + +NG-RAN: + +- Broadcast system information is modified to include supported slice info of the serving and neighbour cells, as recommended in TR 38.832 [3]. + +AMF: + +- AMF is modified to provide configured NSSAI, rejected NSSAI and any Direct AMF selection info to the NG-RAN, as recommended in TR 38.832 [3]. + +## 6.17 Solution #17: Slice based VPLMN Selection Policy + +### 6.17.1 Introduction + +This solution addresses key issue #2: Support of providing VPLMN network slice information to a roaming UE. This solution proposes a solution that can control in which condition the UE can trigger VPLMN selection by providing operator controlled policy. This solution is not a stand-alone solution and expected to be used together with other solutions such as solution #6. + +NOTE: This solution can be used together with any other solutions that provides available slice information to the UE. + +### 6.17.2 Functional Description + +A UE can determine to trigger VPLMN selection if the UE knows which network slices are supported in a VPLMN and the registered VPLMN does not support slice the UE want to use. The UE determines to use a network slice for an application by using URSP rules. + +However, current specification allows the network to provide multiple RSDs for a traffic descriptor, i.e. the network can use multiple slices for an application. Also network can provide "match all" traffic descriptor to the UE. In this case, the UE may use a slice in the RSD of "match all" traffic descriptor if the UE fails to establish a PDU Session using the slice with traffic descriptor for the specific application. From the UE perspective, all slices (e.g. slice in the RSD of matched traffic descriptor with higher priority, slice in the RSD of matched traffic descriptor with lower priority and slice in the RSD of "match all" traffic descriptor) are allowed for the application. So the UE can choose whether to trigger VPLMN selection when a slice in the higher priority URSP rule is in not available in the registered VPLMN. For example, some UEs may not triggers VPLMN selection at all since the slice in the "match all" traffic descriptor is expected to be supported in all VPLMNs. But operator may prefer to use a slice in the higher priority URSP rule if it is available by triggering VPLMN selection. + +In addition to above case, there are some cases that a slice the UE wants to use is supported in the VPLMN but temporally rejected by the network due to some reasons. For example, the network may not allow using the slice due to NSAC failure, congestion control, not allowed in the current registration area. In these cases, each operator may have different preference, e.g. as those conditions are temporal restriction some operators may want to keep the UE in the registered PLMN while some operators may want to trigger VPLMN selection. + +In order to control the UE behaviour in above cases, this solution proposes that the HPLMN may provide Slice based VPLMN Selection Policy (SVSP) to the UE. The policy indicates in which condition the UE is allowed to trigger VPLMN selection to find a network that supports slices the UE want to use. The operator may provide different policy depending on the UE. For example, the PCF or UDM (adding the policy to SoR Info) may consider subscription of the UE, location, etc. to generate SVSP. The SVSP contains following information for each S-NSSAI: + +- Whether the UE can trigger VPLMN selection when the S-NSSAI the UE wants to use is not available due to +- Not allowed in the current registration area + +- Whether the UE can trigger VPLMN selection before using a slice in the URSP rule with "match all" traffic descriptor. + +NOTE: It is expected that SA WG3 will define end-to-end security-mechanism to ensure that VPLMN does not modify UE policy if this policy is conveyed by PCF and not by SoR container. + +### 6.17.3 Procedures + +This procedure is used to deliver SVSP to the UE and supports both roaming and non-roaming scenarios. SoR information can be used as alternative mechanism to deliver this policy (see TS 23.122 [7]). + +![Sequence diagram illustrating the overall procedure for SVSP delivery. The diagram shows interactions between UE, AMF, V-PCF, and H-PCF. The steps are: 1. Registration request from UE to AMF; 2a. Npcf_UEPolicyControl_Create from AMF to H-PCF; 2b. Npcf_UEPolicyControl_Response from H-PCF to AMF; 3. Registration accept from AMF to UE; 4a. Npcf_UEPolicyControl_UpdateNotify request from H-PCF to V-PCF; 4b. Npcf_UEPolicyControl_UpdateNotify response from V-PCF to H-PCF; 4c. UE Configuration Update procedure (AMF to UE); 4d. Npcf_UEPolicyControl_Update request from AMF to H-PCF; 4e. Npcf_UEPolicyControl_Update response from H-PCF to AMF; 5. VPLMN selection (UE internal process).](3e20f0289a1945c7c3894f51383d8e37_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-PCF + participant H-PCF + + Note left of UE: 5. VPLMN selection + UE->>AMF: 1. Registration request + AMF->>H-PCF: 2a. Npcf_UEPolicyControl_Create + H-PCF-->>AMF: 2b. Npcf_UEPolicyControl_Response + AMF->>UE: 3. Registration accept + H-PCF->>V-PCF: 4a. Npcf_UEPolicyControl_UpdateNotify request + V-PCF-->>H-PCF: 4b. Npcf_UEPolicyControl_UpdateNotify response + Note right of AMF: 4c. UE Configuration Update procedure + AMF->>H-PCF: 4d. Npcf_UEPolicyControl_Update request + H-PCF-->>AMF: 4e. Npcf_UEPolicyControl_Update response + +``` + +Sequence diagram illustrating the overall procedure for SVSP delivery. The diagram shows interactions between UE, AMF, V-PCF, and H-PCF. The steps are: 1. Registration request from UE to AMF; 2a. Npcf\_UEPolicyControl\_Create from AMF to H-PCF; 2b. Npcf\_UEPolicyControl\_Response from H-PCF to AMF; 3. Registration accept from AMF to UE; 4a. Npcf\_UEPolicyControl\_UpdateNotify request from H-PCF to V-PCF; 4b. Npcf\_UEPolicyControl\_UpdateNotify response from V-PCF to H-PCF; 4c. UE Configuration Update procedure (AMF to UE); 4d. Npcf\_UEPolicyControl\_Update request from AMF to H-PCF; 4e. Npcf\_UEPolicyControl\_Update response from H-PCF to AMF; 5. VPLMN selection (UE internal process). + +Figure 6.17.3-1: Overall procedure + +In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF interacts with the V-PCF: + +1. The UE performs Registration procedure. The UE indicates that it supports SVSP in the Registration request. + +NOTE: During the Registration procedure, the UE also indicates whether it supports slice aware SoR. + +2. The AMF creates UE policy association with PCF. The AMF provides the UE's capability, i.e. support of SVSP to the PCF. +3. The AMF provides Registration accept to the UE. +4. The H-PCF may provide the UE policy container including SVSP. The policy is delivered to the UE by using the UE Configuration Update procedure for transparent UE Policy delivery as described in TS 23.502 [5]. +5. The UE wants to use a slice but the VPLMN does not allow the slice due to some reason. The UE checks the stored SVSP and determine that the SVSP allows triggering VPLMN selection. The UE triggers VPLMN selection by using SoR AF or UDM provided information e.g. as described in solution 6. + +## 6.17.4 Impacts on services, entities and interfaces + +UE: + +- The UE supports receiving SVSP from the PCF. +- The UE determines whether to trigger PLMN selection based on SVSP. +- The UE indicates SVSP capability during the registration. + +AMF: + +- The AMF provides UE's SVSP capability to the PCF during the UE Policy Association Establishment. + +PCF: + +- The PCF supports providing SVSP to the UE. + +## 6.18 Solution #18: Sending rejected NSSAI to the UDM to assist the UDM to steer the UE to the PLMN supporting rejected NSSAI + +### 6.18.1 Introduction + +The solution addresses KI#2 Support of providing VPLMN network slice information to a roaming UE. + +During the registration procedure in a VPLMN, if the AMF determines that a S-NSSAI is not allowed e.g. the S-NSSAI is not supported by the VPLMN or the S-NSSAI is not available e.g. the no. of UE reached for the S-NSSAI, the AMF sends the rejected NSSAI and requested NSSAI to the UDM. When the UDM receives the rejected NSSAI and the requested NSSAI, the UDM can determine which other VPLMN can support the rejected NSSAI. The UDM will prioritize the VPLMN supporting the rejected NSSAI and initiates SoR procedure with the VPLMN supporting the prioritized VPLMN as highest priority PLMN. + +When the UE receives the SoR, the UE may select the VPLMN which supports the rejected NSSAI as this VPLMN is highest priority PLMN. + +### 6.18.2 Procedures + +![Sequence diagram illustrating the procedure for steering of roaming to a VPLMN supporting the network slice which is not available in the current PLMN. The diagram shows interactions between UE, Cell (VPLMN 1), AMF (VPLMN 1), Cell (VPLMN 2), AMF (VPLMN 2), PCF (VPLMN 1), UDM, and SoR-AF.](b4415fea4ab6fd9f150a1347d4148525_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Cell1 as Cell (VPLMN 1) + participant AMF1 as AMF (VPLMN 1) + participant Cell2 as Cell (VPLMN 2) + participant AMF2 as AMF (VPLMN 2) + participant PCF1 as PCF (VPLMN 1) + participant UDM + participant SoR-AF + + Note right of AMF1: 2. Determination of allowed NSSAI. + + UE->>AMF1: 1. Registration Request (User identity, Requested NSSAI) + AMF1->>UE: 3. Registration Accept (allowed NSSAI, Rejected NSSAI) + UE->>AMF1: 4. Registration Complete (assistance information (e.g. Allowed NSSAI or Rejected NSSAI)) + AMF1->>UDM: 5. Nudm_UECM_Update (assistance information (e.g. Allowed NSSAI or Rejected NSSAI)) + UDM->>AMF1: 6. Nudm_UECM_Update Response + Note right of PCF1: 7. UDM determines to trigger SoR depending based on assistance information and operator policies.) + UDM->>SoR-AF: 8a. Nsoraf_SoR_Get request (VPLMN ID, allowed NSSAI, Rejected NSSAI) + SoR-AF->>UDM: 8b. Nsoraf_SoR_Get Response(Preferred PLMN list) + Note right of AMF1: 9. SoR Transmission mechanism + Note right of AMF1: 10. The UE may select VPLMN 2 and initiate registration procedure over VPLMN 2. + +``` + +Sequence diagram illustrating the procedure for steering of roaming to a VPLMN supporting the network slice which is not available in the current PLMN. The diagram shows interactions between UE, Cell (VPLMN 1), AMF (VPLMN 1), Cell (VPLMN 2), AMF (VPLMN 2), PCF (VPLMN 1), UDM, and SoR-AF. + +Figure 6.18.2-1: Steering of roaming to a VPLMN supporting the network slice which is not available in the current PLMN + +The detailed steps of the procedure are defined below: + +0. The UE selects a VPLMN as defined in the TS 23.122 [7]. The VPLMN sends configured NSSAI when it is registering to the VPLMN for the first time. +1. The UE initiates the registration procedure (e.g. Initial Registration, mobility registration) to VPLMN 1 for the S-NSSAIs present in the requested NSSAI. The UE sends a capability that it supports Slice based SoR procedure to the AMF. +2. The AMF determines that some S-NSSAI(s) are allowed and some S-NSSAI(s) are rejected (e.g. the S-NSSAI is not supported in the TA or the PLMN). The AMF sends Registration accept message containing the allowed NSSAI and rejected NSSAI. +- 3-4. Upon reception of the Registration accept message, the UE sends Registration complete message. The registration complete message contains secured assistance information e.g. rejected NSSAI and allowed NSSAI which is passed transparently to the UDM via AMF. The UE may also send secured assistance information in the UL NAS TRANSPORT message e.g. Registration complete message is not required to send. + +The UE sends the assistance information only when the UE receives rejected NSSAI from the AMF (i.e. rejected S-NSSAI due to no support in the RA or in the PLMN or other reject values). + +5. The AMF sends Nudm\_UECM\_Update containing assistance information e.g. allowed NSSAI and rejected NSSAI to the UDM. + 6. The UDM sends Nudm\_UECM\_Update response message. When the UDM receives assistance information it will follow step 7. + 7. UDM determines to trigger SoR procedure based on assistance information (e.g. the Rejected NSSAI and allowed NSSAI) as described below. + - 8a. The UDM sends Nsoraf\_SoR\_Get request (VPLMN ID, allowed NSSAI, Rejected NSSAI) to the SoR-AF. +- NOTE: When the UDM triggers SoR is totally based on operator policies. The allowed NSSAI and rejected NSSAI is provided as assistance information to the HPLMN. For example, if the rejected NSSAI indicates a S-NSSAI is rejected with cause "S-NSSAI not available in the current PLMN" then the UDM may steer the UE to another VPLMN. +- 8b. The SoR-AF calculate preferred PLMN list depending on the allowed NSSAI and rejected NSSAI and sends it in the Nsoraf\_SoR\_Get response message (Preferred PLMN list). The preferred PLMN list consists of PLMN IDs and the S-NSSAIs supported by the PLMN in the preferred PLMN list. + 9. The UDM send SoR as defined in TS 23.122 [7]. The content of SoR can be + 10. After the completion of the SoR procedure, the UE may select a VPLMN (e.g. VPLMN 2) according to the PLMN list received in step 9. + +### 6.18.3 Impacts on services, entities and interfaces + +UE: + +- sending secured assistance information (e.g. rejected and allowed NSSAI) to the UDM via AMF. + +AMF: + +- Sending of allowed NSSAI and rejected NSSAI to the UDM. + +UDM: + +- determines to trigger SoR based on rejected NSSAI and allowed NSSAI. + +SoR-AF: + +- SoR AF preparing the preferred PLMN list based on the rejected NSSAI and Allowed NSSAI. + +## 6.19 Solution #19: Configuring the UE with network slice aware preferred PLMNs lists + +### 6.19.1 Introduction + +This solution aims to address the key issues#2: Support of providing VPLMN network slice information to a roaming UE by enhancing SoR with slice aware preferred PLMN lists. + +This solution relies on (e.g. existing) SoR or UE configuration methods that enable delivery of SoR information to the UE. + +### 6.19.2 Functional Description + +It is normal practice for operators to configure the UE with a (set of) preferred PLMN(s) in a certain country while the UEs are roaming. In the 5GS this set of preferences may e.g. be configured or updated in the UE using the SoR (Steering of Roaming) procedure defined in TS 23.502 [5] and TS 33.501 [14]. + +TS 23.502 [5] reads: + +"During registration the Home Network can provide Steering of Roaming information to the UE via the AMF (i.e. a list of preferred PLMN/access technology combinations or HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed). The Home Network can include an indication for the UE to send an acknowledgement of the reception of this information. Details regarding the handling of Steering of Roaming information including how this information is managed between the AMF and the UE are defined in TS 23.122 [7]." + +The home operator may want the UE to remain with a list of preferred PLMNs (i.e. PLMNs in the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology"), unless the UE requires to use a network slice which these PLMNs do not support. Also, the home operator may have specific preferred PLMN list when specific network slices are used. This is not possible today with the current PLMN selection mechanisms as the UE will, in automatic PLMN selection, always remain with the preferred PLMNs (in respective priority order) if they are available. + +This solution proposes to configure the UE with additional network slice aware PLMN selection information, in the form of one or more lists of PLMNs that are preferred when the UE requires to use a respective S-NSSAI of the HPLMN. The S-NSSAI values in this information are the HPLMN S-NSSAIs (i.e. the mapped value of the S-NSSAIs in the V-PLMN are not considered and so there is no impact on this solution if the VPLMNs decide to change the value of S-NSSAI they use to identify the network slice locally). The UE therefore can be configured with the preferred PLMN list as today and additional Network-Slice-Aware PLMN lists per S-NSSAI which may take precedence as an exception over the preferred PLMN list. In other words, the UE may be configured with: + +- nothing (i.e. neither "Operator Controlled PLMN Selector with Access Technology" nor Network Slice Aware PLMN list); +- just a preferred PLMNs list (e.g. "Operator Controlled PLMN Selector with Access Technology"); +- a mix of preferred PLMN list and at least one Network-Slice-Aware PLMN list; or +- at least one Network-Slice-Aware PLMN list. + +The UE is configured with a Network-Slice-Aware PLMN list of alternate (potentially ordered by a priority value) PLMN IDs associated with the supported S-NSSAIs. Some of the S-NSSAIs may not be supported (or are preferred instead of) by the PLMNs in the "Operator Controlled PLMN Selector with Access Technology" list. + +When the Network-Slice-Aware PLMN list is provided for an S-NSSAI and this S-NSSAI is required but not yet allowed or rejected, this is a trigger for evaluation by the UE whether to consider the Network-Slice-Aware PLMN list to perform PLMN selection. + +The Network-Slice-Aware PLMN list may be associated with validity parameters (e.g. location in particular country or time period restriction). If so, the UE applies the configuration when the validity restriction is fulfilled. + +When attempting to use/register with a S-NSSAI associated with a Network-Slice-Aware PLMN list, the UE prefers and selects one of the PLMNs identified in the Network-Slice-Aware PLMN list if a PLMN ID is present in such list for + +this S-NSSAI that is of higher priority of the current PLMN, or if the PLMN ID of the current PLMN is not among the PLMN IDs in the Network-Slice-Aware PLMN list for the S-NSSAI. The UE may return to using the ordinary list of preferred PLMNs when it deregisters from all S-NSSAIs associated to any Network-Slice-Aware PLMN lists it is configured with, so in a sense the UE uses the Network Slice Aware PLMN list when an S-NSSAI is not available in currently registered PLMN or to find a PLMN which is preferable when some S-NSSAIs are associated to a Network Slice Aware PLMN list.. + +It is assumed that the UE at any time selects the PLMN ID which maximises the number of S-NSSAIs that the UE can use. If all S-NSSAIs can be used in a set of PLMNs, the UE selects the common PLMN ID across all the Network-Slice-Aware PLMN list which ranks higher on average. This average may also consider predefined weighted factors assigned to each Network Slice. In case a UE needs to use a network slice which is present in the Network-Slice-Aware PLMN list and another network slice which is not present in the Network Slice Aware PLMN list, then the UE shall give preference to the PLMNs in the order of the Network Slice Aware PLMN list. If there are no common PLMNs where both can be supported, then the UE will decide which slice to use based on local policy. An example of a UE configuration with set of Network-Slice-Aware PLMN list is in figure 6.19.2-1. Alternatively, if the HPLMN does not provide a weight factor per S-NSSAI with a Network-Slice-Aware PLMN list the UE can create internally a list of preferred S-NSSAIs, generate locally the weights accordingly and can select a PLMN ID (from the Network-Slice-Aware PLMN list) which serves the preferred S-NSSAIs. + +**Editor's note:** The use of weight factors or some other means is FFS. + +**NOTE** How the HPLMN generates these weight factors and in general the PLMN lists is outside the scope of 3GPP (as for existing SoR info). + +**Table 6.19.2-1: Example of a UE configuration with 3 Network-Slice-Aware PLMN lists** + +| Weight | S-NSSAI | PLMN ID list with priority | +|--------|--------------|----------------------------------------------| +| 0.5 | S-NSSAI 1 1 | PLMN1 prio 1
PLMN3 prio 2
PLMN4 prio 3 | +| 0.3 | S-NSSAI 2 2 | PLMN1 prio 1
PLMN2 prio 2
PLMN3 prio 3 | +| 0.2 | S-NSSAI 3 78 | PLMN2 prio 1
PLMN3 prio 2
PLMN1 prio 3 | + +Based on the configuration in Figure 6.19.2-1, let's suppose the UE needs to request S-NSSAI1, S-NSSAI2 and S-NSSAI3. If the UE needs to perform PLMN selection (as e.g. it may be on a PLMN which does not support all 3 S-NSSAIs), then the UE computes the average PLMN priority of the common PLMNs where all three S-NSSAIs can be supported this way: + +$$\text{PLMN1} = 0.5 * 1 + 0.3 * 1 + 0.2 * 3 = 0.5 + 0.3 + 0.6 = 1.4 \text{ weighted priority}$$ + +$$\text{PLMN3} = 0.5 * 2 + 0.3 * 3 + 0.2 * 2 = 1 + 0.9 + 0.4 = 2.3 \text{ weighted priority}$$ + +This example shows that PLMN1 is the PLMN to be used as it has the highest priority. + +In the event that there were no common PLMNs in the Network-Slice-Aware PLMN lists for two S-NSSAIs and the UE needs to request both, the UE would restrict the selection to the S-NSSAIs associated with the highest weight factor. If none of the two has highest weight factor, local policy applies. By extension, if there are S-NSSAIs that have common PLMNs in the Network-Slice-Aware PLMN lists but are incompatible with other S-NSSAIs Network-Slice-Aware PLMN lists, then the groups for S-NSSAIs with common PLMNs with the highest total weight factor are considered for PLMN selection. + +## 6.19.3 Procedures + +It is assumed that a UE is configured with both a preferred PLMN list and one or more Network-Slice-Aware PLMN lists. This is the starting point in step 0 (if this is not yet achieved, then e.g. SoR configuration procedure steps could be followed to obtain such configuration as per existing specification procedures) + +![Sequence diagram illustrating the usage of Network Slice Aware PLMN lists. The diagram shows interactions between UE, Preferred VPLMN(s), VPLMNs in Network slice aware PLMN list, and HPLMN. The process starts with UE configuration by HPLMN and proceeds through several steps of PLMN selection based on S-NSSAI availability.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PV as Preferred VPLMN(s) + participant NSAPL as VPLMNs in Network slice aware PLMN list + participant HPLMN + + Note right of HPLMN: 0. UE configured by HPLMN with the Preferred PLMN list and Network slice aware PLMN selection exception list of PLMN IDs per S-NSSAI + Note left of UE: 1. the UE is in a country where there are some S-NSSAI in the network slice aware PLMN list pointing to PLMN IDs not in the preferred PLMN ID list for the MCC + Note left of UE: 2. UE selects to use only S-NSSAIs not in the Network slice aware PLMN selection PLMN list of PLMNs + Note left of UE: 3. UE selects a VPLMN in the ordinary preferred PLMN list configured by HPLMN + Note left of UE: 4. the UE needs to use at least one S-NSSAI that is in the Network slice aware PLMN list + Note left of UE: 5. the UE Selects a VPLMN in the network slice aware PLMN list of PLMNs compatible with the needed S-NSSAIs as configured by HPLMN + Note left of UE: 6. the UE no longer needs to use any S-NSSAI that is in any Network slice aware PLMN list + Note left of UE: 7. UE selects a VPLMN in the ordinary preferred PLMN list configured by HPLMN + +``` + +Sequence diagram illustrating the usage of Network Slice Aware PLMN lists. The diagram shows interactions between UE, Preferred VPLMN(s), VPLMNs in Network slice aware PLMN list, and HPLMN. The process starts with UE configuration by HPLMN and proceeds through several steps of PLMN selection based on S-NSSAI availability. + +**Figure 6.19.3-1: example of usage of Network Slice Aware PLMN lists** + +In step 0, the UE has been already configured with the suitable ordinary preferred PLMN list (e.g. Operator Controlled PLMN Selector with Access Technology) and any Network-Slice-Aware PLMN lists by e.g. using the existing SoR interactions for UEs that indicate support of receiving the Network-Slice-Aware PLMN lists in SoR interactions. + +In step 1 the UE detects it is in a country for which it is configured with a preferred PLMNs configuration. + +In step 2/3 the UE detects that none of the S-NSSAI for which it has Network-Slice-Aware PLMN lists needs to be used, so, it behaves according to the ordinary preferred PLMN list behaviour. + +In step 4 the UE detects the need to register with one or more S-NSSAIs that have a Network-Slice-Aware PLMN list associated with them. How this "need" is detected is based on UE implementation (e.g. an application needs a specific slice based on the UE configuration including URSP information). + +In step 5 the UE detects that the current PLMN is not preferred based on the S-NSSAI(s) it needs to use so it proceeds to select the suitable PLMN according to the Network-Slice-Aware PLMN list. + +In step 6 the UE detects that none of the S-NSSAIs with a Network-Slice-Aware PLMN list is registered, so it returns to operate based on the ordinary preferred PLMN list. + +In step 7 the UE selects a PLMN, if that is needed, based on the ordinary preferred PLMN list. + +## 6.19.4 Impacts on services, entities and interfaces + +The solution has the following impacts: + +UE: + +- ability to be configured with Network-Slice-Aware PLMN lists and ability to perform PLMN selection taking this also into account the Network-Slice-Aware PLMN lists. Further, the UE is able to indicate the support of this feature to UDM. + +SOR-AF/UDR: + +- ability to provide Network-Slice-Aware PLMN lists for supporting UEs. + +UDM: + +- ability to send Network-Slice-Aware PLMN lists via a SOR transparent container to a supporting UE and to forward the indication of support of feature to SOR-AF. + +## 6.20 Solution #20: PLMN Selection following existing SoR information + +### 6.20.1 Introduction + +This solution will address KI#2: Support of providing VPLMN network slice information to a roaming UE. This solution lets the UE reuse the current Steering of Roaming information. Thus, it could be used for legacy UEs and bring little impact to the VPLMN. + +### 6.20.2 Functional Description + +Currently the UE will get SoR (Steering of Roaming) information as described in TS 23.122 [7]. But the current SoR does not consider the expected S-NSSAIs of the UE, so the PLMN which does not contain any S-NSSAIs the UE want to use may have a higher priority but the PLMN which contains many S-NSSAIs the UE want to use may have a lower priority. Then the UE will access to a non-optimized PLMN. + +It is proposed that the UDM should generate the SoR information based on the expected S-NSSAIs (i.e. the S-NSSAIs the UE expects to include in the Request NSSAI in the next Registration) if SoR-AF is collocated with the UDM. The expected S-NSSAIs are the S-NSSAIs in the Subscribed S-NSSAIs, thus UDM could understand the meaning of the expected S-NSSAIs. The UE can generate the expected S-NSSAIs in the same way as generating Requested NSSAI as described in TS 23.501 [2]. The S-NSSAIs use the HPLMN values, not the values of the visited network(s), and there is no restriction regarding their presence in the Configured NSSAI of the visited network(s) if any, or in default Configured NSSAI. The UE may send the expected S-NSSAIs in a container. The AMF should transfer the container to the UDM and shall not change the context of the container, i.e. the AMF shall transfer the expected S-NSSAIs transparently. The UDM will generate SoR based on the expected S-NSSAI. If there is no expected S-NSSAIs (e.g. for legacy UEs), the UDM could generate SoR based on the Subscribed S-NSSAI. In particular, the PLMNs supporting more Expected/Subscribed S-NSSAIs will have higher priority. The UDM should get the mapping between corresponding PLMNs and supporting S-NSSAIs based on configuration or from NSSF. + +If SoR-AF is not collocated with the UDM, UDM needs to send the expected S-NSSAIs in the container or Subscribed S-NSSAIs to the SoR-AF. The SoR-AF will generate SoR based on the expected S-NSSAI. If there is no expected S-NSSAIs (e.g. for legacy UEs), the SoR-AF could generate SoR based on the Subscribed S-NSSAI. In particular, the + +PLMNs supporting more Expected/Subscribed S-NSSAIs will have higher priority. The SoR-AF should get the mapping between corresponding PLMNs and supporting S-NSSAIs based on configuration or from NSSF. + +The UE will follow the current SoR handling as described in TS 23.122 [7]. + +### 6.20.3 Procedures + +Figure 6.20.3-1 describe the procedure for this solution: + +![Sequence diagram illustrating the procedure for PLMN Selection following existing SoR information. The diagram shows interactions between UE, VPLMN AMF, HPLMN UDM, and SOR-AF. The steps are: 1. REGISTRATION REQUEST from UE to VPLMN AMF; 2. Nudm_SDM_Get request from VPLMN AMF to HPLMN UDM; 3. Decision to send steering of roaming information (involving SOR-AF); 4. Nudm_SDM_Get response from HPLMN UDM to VPLMN AMF; 5. REGISTRATION ACCEPT from VPLMN AMF to UE; 6. Use Steering of roaming information (at UE).](708e4c9a044ef61f586126676eb2eeb8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant VPLMN AMF + participant HPLMN UDM + participant SOR-AF + Note right of SOR-AF: 3. Decision to send steering of roaming information, as described in TS 23.122 [x]. Further considering the Expected/Subscribed S-NSSAIs of the UE. + + UE->>VPLMN AMF: 1. REGISTRATION REQUEST + VPLMN AMF->>HPLMN UDM: 2. Nudm_SDM_Get request + HPLMN UDM-->>SOR-AF: + Note right of SOR-AF: 3. Decision to send steering of roaming information, as described in TS 23.122 [x]. Further considering the Expected/Subscribed S-NSSAIs of the UE. + HPLMN UDM-->>VPLMN AMF: 4. Nudm_SDM_Get response + VPLMN AMF->>UE: 5. REGISTRATION ACCEPT + Note left of UE: 6. Use Steering of roaming information + +``` + +Sequence diagram illustrating the procedure for PLMN Selection following existing SoR information. The diagram shows interactions between UE, VPLMN AMF, HPLMN UDM, and SOR-AF. The steps are: 1. REGISTRATION REQUEST from UE to VPLMN AMF; 2. Nudm\_SDM\_Get request from VPLMN AMF to HPLMN UDM; 3. Decision to send steering of roaming information (involving SOR-AF); 4. Nudm\_SDM\_Get response from HPLMN UDM to VPLMN AMF; 5. REGISTRATION ACCEPT from VPLMN AMF to UE; 6. Use Steering of roaming information (at UE). + +**Figure 6.20.3-1: procedure for PLMN Selection following existing SoR information** + +1. During registration in roaming case, when the UE finds out it needs a service provided by a slice that is not available in the current visited PLMN, the UE may send expected S-NSSAIs as a container. +2. The AMF forwards the container to the UDM by invoking Nudm\_SDM\_Get request. The AMF shall not change the content of the container. +3. If the UDM and SoR-AF are collocated, the UDM generates SoR information further based on expected S-NSSAIs of the UE and the supporting S-NSSAIs of the VPLMN other than the description in TS 23.122 [7]. If there is no expected S-NSSAIs, the UDM could generate SoR information further based on Subscribed S-NSSAIs of the UE. If SoR-AF is not collocated with the UDM,, UDM needs to send the expected S-NSSAIs in the container/Subscribed S-NSSAIs to the SoR-AF. The SoR-AF will generate the SoR information accordingly and send the SoR information to the UDM. + +NOTE: If the UDM or SoR-AF generates SoR information based on Subscribed S-NSSAIs of the UE, it could send the SoR information in both roaming and non-roaming scenario. The SoR information could also be sent after registration. + +- 4-6. The UDM sends the SoR information as described in TS 23.122 [7]. The UE will use the SoR based on the current description in TS 23.122 [7]. + +### 6.20.4 Impacts on services, entities and interfaces + +UE: + +- may send Expected S-NSSAI container to the HPLMN (i.e. UDM). + +NOTE: The Solution is also applicable to legacy UEs. + +AMF: + +- may transfer the Expected S-NSSAI container to the UDM transparently. VPLMN does not need to change any other logic. + +UDM/SoR-AF: + +- generates SoR information based on expected S-NSSAI of the UE and the supporting S-NSSAIs of the VPLMN. For legacy UEs, it can generate the SoR information based on Subscribed S-NSSAI. + +## 6.21 Solution #21: Temporary slice based on URSP + +### 6.21.1 Introduction + +This solution is for KI#3. It covers the following aspects by reusing the current URSP mechanism: + +- The support of services over network slices when the services have Area of Service not matching the existing deployed TA boundaries +- The support of network slices which have a limited lifetime (including how to gracefully terminate a network slice which can apply also to network slices which have a longer lifespan in order to avoid abrupt PDU Session release). + +### 6.21.2 Functional Description + +The PCF should get the information of the temporary slice, (i.e. serving time window of a slice or serving area of a slice) from the UDR. If there is only one PCF in the network or OAM can consistently update more than one PCF, the PCF could get the information based on OAM. The PCF should generate the Route Selection Validation Criteria in the URSP based on the information of the temporary slice. For example, the Time window or Location Criteria could be exactly the one received from the UDR or a little bit more limited than the one received from UDR. The UE will release the PDU Session gracefully based on URSP and its implementation as described in TS 23.503 [12]. + +On other aspects related to slicing, the current mechanism described in clause 5.15 of TS 23.501 [2] is not changed. The NSSF/AMF could remove the S-NSSAI in the Allowed NSSAI when it is not in the valid duration based on configuration. In particular, when the operator removes the S-NSSAI (i.e. the S-NSSAI is removed from Subscribed S-NSSAIs of a UE via OAM), the AMF should set the S-NSSAI as rejected S-NSSAI if it is in Allowed NSSAI for a UE via UCU procedure as described in clause 4.2.4.2 of TS 23.502 [5]. And the AMF trigger PDU Session Release as described in clause 4.3.4.2 of TS 23.502 [5] if the UE does not release the PDU Session in time. Besides, the AMF may also configure the serving area/time window of the S-NSSAI (or from NSSF) and subscribe the UE location. When UE is in Connected Mode and does not release the PDU Session in time if the UE is out of the serving area, the AMF should trigger the PDU Session Release as described in clause 4.3.4.2 of TS 23.502 [5] if the operator wants to control it strictly based on operator policy. If the operator wants to control is in a soft way based on operator policy, i.e. can wait for UE entering CM-IDLE state, there is no additional action needed. + +NOTE: As described in TS 23.503 [12], if the re-evaluation of RSD in the URSP leads to a change of the application to PDU Session association, the UE can enforce such changes in a timely manner based on implementation, e.g. immediately or when UE enters CM-IDLE state. + +**Editor's note:** with this approach, the time-based validity is totally taken away from the route selection and used to support the temporary slice. this means this solution needs to explain how the current use of thee time-based validity independent of the slice availability is supported. + +### 6.21.3 Procedures + +There is no impact on the current procedure. Only involve the information of the temporary slice as UE context policy control subscription information as defined in clause 6.2.1.3 of TS 23.503 [12]. + +### 6.21.4 Impacts on services, entities and interfaces + +PCF: + +- Needs to get the information of the temporary slice from UDR or based on configuration. + +UDR: + +- Store the information of the temporary slice + +AMF: + +- May need to get the serving area/time window of temporary slice from NSSF or based on configuration and check UE location. + +## 6.22 Solution #22: Enabling graceful slice termination with support of UE policies + +### 6.22.1 Introduction + +This solution applies to KI#3. + +This solution enables a graceful replacement and removal of network slices. + +NOTE: As temporary network slice instances are not part of the KI#3 the removal of a network slice means the removal of one or more S-NSSAIs. + +### 6.22.2 Functional Description + +The basic principles of this solution are the following for HPLMN S-NSSAIs: + +1. The "time" or area where a network slice is to be terminated is known in advance +2. If a network slice is to be replaced by a new network slice then: + - First a new network slice is created i.e. NFs and resources etc and then add the S-NSSAI to subscriptions and then use PCF to update the UE policies (URSP) + - Update UEs URSP rules such that the UEs use the new S-NSSAI for new access attempts; + - Update UEs URSP rules Route Selection Validation Criteria with appropriate Time Window and Location Criteria; + - The UE is assumed to try and use the Time Window and use higher priority rules when the Time Window is no longer valid. + - Update the UE URSP rules such that PCF can enforce/command the UE to re-apply the URSP rules i.e. triggers the UE to move the user data from S-NSSAI to be removed to the new S-NSSAI e.g. using SSC 3 etc immediately. +3. OAM knows when and which network slice is to be terminated and configures NFs + - 1.- UDR/UDM are updated such that Network Slices are added and UDM notifies AMFs about the added Subscribed S-NSSAIs. + 2. NFs of network slice to be replaced updates NF profile such that load is reduced e.g. no new entrants + - 3.- PCF updated as per bullet 2 + - 4.- At a suitable time, UDR/UDM are updated such that the to be removed Subscribed S-NSSAIs are removed and UDM notifies AMFs. + 5. After all subscriptions been updated, OAM removes any remaining usage of the S-NSSAI in the 5GC and 5G-AN. +4. AMFs follows current logic i.e. + - AMF updates NSSAI information towards the UE + - AMF enforces removal of S-NSSAIs e.g. initiates release of PDU Sessions within the network. + +The basic principles of this solution are the following for serving PLMN S-NSSAIs: + +1. The "time" or area where a network slice is to be terminated is known in advance +2. If a network slice is to be replaced by a new network slice then: + +- First a new network slice is created i.e. NFs and resources etc +3. OAM knows when and which network slice is to be terminated and configures NFs + 1. NFs of network slice to be replaced updates NF profile such that load is reduced e.g. no new entrants + 2. OAM removes any remaining usage of the S-NSSAI in the 5GC and 5G-AN. + 4. AMF follows current logic i.e. + - After AMF got updated by OAM at step 3, the AMF updates NSSAI information towards the UEs i.e. + - New UE requests uses the new S-NSSAI for the serving PLMN + - For UEs with registered S-NSSAIs without PDU Sessions, the AMF issues UE Configuration Updates changing the NSSAI information with the new S-NSSAI for the serving PLMN +- Editor's note:** It is FFS how to gracefully re-establish current established PDU Sessions with a new S-NSSAI for the serving PLMN +- Before the S-NSSAI is removed the AMF enforces removal of S-NSSAIs e.g. initiates release of PDU Sessions within the network. + +### 6.22.3 Procedures + +The existing procedures are used as is with minimal impacts to the content of the URSP rules. + +### 6.22.4 Impacts on services, entities and interfaces + +The following impacts have been identified: + +UE: + +- UE supports the new conditions in the URSP rules such that PCF can enforce/command the UE to re-apply the URSP rules as above. + +**NOTE:** The functionality works also without UE support, but there can then be a service interruption when changing network slice e.g. when UDM notifies AMF that a subscribed S-NSSAI been removed the AMF updates the UE and the AMF also de-registers the S-NSSAI + +PCF: + +- supports the new conditions in the URSP rules such that PCF can enforce/command the UE to re-apply the URSP rules for also existing usage. + +**Editor's note:** It is FFS whether the UEs are already required to re-evaluate the URSP rules for existing registered S-NSSAI and PDU Sessions when the UE is updated with new URSP rules or an existing rule used to register the S-NSSAI or for the PDU Session Establishment no longer is valid. If that is the case, then there is no need to update the URSP rules but the solution can be used to describe how to support the temporary network slices with existing 5GS functionality. + +## 6.23 Solution #23: UE registration for conditional network slices + +### 6.23.1 Introduction + +This solution addresses the use case where a network slice is not supported in the whole RA of the UE, i.e. the network slice is supported only in some of the TAs of the UE's RA. The solution is related to the requirements of KI#3 and KI#5. + +### 6.23.2 Functional description + +The solution allows for UE registration for a network slice which is not homogeneously supported in all of the TAs of the RA. Such a network slice is called conditional network slice as the UE can request a service on it only when this network slice is supported by the network in the UE's location. When a UE supporting registration to a conditional network slice feature initiates the registration procedure, the UE shall indicate its support for registration for a + +conditional network slices feature. Then the AMF may allocate to the UE a RA where not all of the requested by the UE network slices are homogeneously supported. The network slices that are supported homogeneously in the UE's RA (i.e. in all TAs of the RA) are included in the Allowed NSSAI for the UE while the network slices that are not supported in all the TAs of the RA are included in a new Conditional NSSAI parameter for the UE. The UE is allowed to initiate a service on a conditional S-NSSAI only when the UE is in a location where the conditional S-NSSAI is supported. During the UE registration the network provides for each conditional S-NSSAI a list of TAs where the conditional S-NSSAI is supported. + +If a UE initiates a service on conditional S-NSSAI that is not available in the TA of UE's location, the request is rejected and an indication is provided to the UE as to why. + +If a UE with active session(s) on conditional S-NSSAI moves to TA where the conditional S-NSSAI is not supported, session(s) on the conditional S-NSSAI are deactivated, however, the context may be preserved so that the sessions(s) are re-activated when the UE moves to TA which supports the conditional S-NSSAI. + +### 6.23.3 Procedures + +![Sequence diagram of UE registration for conditional network slices. The diagram shows interactions between UE, AMF, and UDM. Step 1: UE sends a Registration Request with requested NSSAI (S-NSSAI-1, S-NSSAI-2, S-NSSAI-3, and conditional S-NSSAI support). Step 2: AMF continues registration per TS 23.502. Step 3: AMF may provide conditional S-NSSAI(s) not supported in all TAs. Step 4: AMF sends Registration Accept with Allowed NSSAI and Conditional NSSAI (S-NSSAI-3 and TA list). Step 5: UE may request service on conditional S-NSSAI-3 only in supported TAs.](ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + Note right of AMF: 3) If the UE indicated support for conditional S-NSSAI, the AMF may provide to the UE S-NSSAI(s) that are not supported in all of the TAs of the RA for the UE (e.g. conditional S-NSSAI(s)) + Note left of UE: 5) The UE may request a service on the conditional S-NSSAI-3 only when the UE is in a TA where the conditional S-NSSAI-3 is supported. + UE->>AMF: 1) UE Registration Request (Requested NSSAI = S-NSSAI-1, S-NSSAI-2, S-NSSAI-3, conditional S-NSSAI support) + AMF->>UDM: 2) Continue with the registration procedure as per clause 4.2.2.2.2 in TS23.502 + AMF-->>UE: 4) UE Registration Accept (Allowed NSSAI=S-NSSAI-1, S-NSSAI-2, Conditional NSSAI=S-NSSAI-3, conditional S-NSSAI-3 TA list) + +``` + +Sequence diagram of UE registration for conditional network slices. The diagram shows interactions between UE, AMF, and UDM. Step 1: UE sends a Registration Request with requested NSSAI (S-NSSAI-1, S-NSSAI-2, S-NSSAI-3, and conditional S-NSSAI support). Step 2: AMF continues registration per TS 23.502. Step 3: AMF may provide conditional S-NSSAI(s) not supported in all TAs. Step 4: AMF sends Registration Accept with Allowed NSSAI and Conditional NSSAI (S-NSSAI-3 and TA list). Step 5: UE may request service on conditional S-NSSAI-3 only in supported TAs. + +**Figure 6.23.3-1: UE registration for conditional network slices** + +1. A UE requests registration for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. If the UE supports the registration for conditional network slice feature, the UE shall indicate in the Registration Request message its support for conditional network slices. +2. The UE registration procedure continues as in clause 4.2.2.2.2 of TS 23.502 [5]. +3. If the UE indicated support for conditional S-NSSAI, the AMF may assign the UE a RA where not all of the requested by the UE network slices are supported. For example, the AMF may register the UE for a RA where S-NSSAI-1 and S-NSSAI-2 are supported homogeneously in all TAs of the RA and S-NSSAI-3 is supported only in one or limited number of TAs of the RA. In this case the AMF includes the network slices S-NSSAI-1 and S-NSSAI-2 in the Allowed NSSAI for the UE and includes the S-NSSAI-3 in the Conditional NSSAI for the UE. Optionally, the AMF may provide to the UE a list of TAs where the conditional S-NSSAI is supported. +4. AMF confirms the UE registration with Registration Accept message in which the AMF includes the Allowed NSSAI parameter and if the UE indicated support for conditional S-NSSAI, the AMF also includes the new Conditional NSSAI parameter and optionally a list of TA(s) per each conditional S-NSSAI where the conditional S-NSSAI is supported. +5. If the UE was provided with conditional S-NSSAI(s) withing the Conditional NSSAI parameter, the UE is allowed to initiate service on a conditional S-NSSAI only when the conditional S-NSSAI is supported in the TA of the UE's current location. The UE knows about the conditional S-NSSAI availability in its current location from the list of TA(s) where the conditional S-NSSAI is supported and which is provided by the AMF during the registration. + +NOTE: This solution allows for conditional S-NSSAI support with TA(s) granularity. However, it can work also when the conditional S-NSSAI is supported with cell(s) granularity in which case the RAN has to report the S-NSSAI(s) support per cell level and the AMF provides to the UE the area, where the conditional S-NSSAI is supported, with TA(s) and cell(s) granularity. + +## 6.23.4 Impacts on services, entities and interfaces + +UE, AMF: + +- support for conditional S-NSSAI feature +- conditional S-NSSAI feature support indication in the Registration Request message. +- conditional S-NSSAI parameter in the Registration Accept message. + +RAN (only impacted if conditional S-NSSAI is supported with cell granularity): + +- If the solution is implemented with conditional S-NSSAI support per cell granularity, the RAN needs to report the S-NSSAI(s) support to the AMF per cell level. + +## 6.24 Solution #24: On the handling of temporary network slices + +### 6.24.1 Introduction + +This solution addresses KI#3. + +This solution addresses the case where it is necessary to deploy network slices which have a known limited lifetime or a periodic lifetime. It addresses from RM and SM standpoint the support of Temporary/Periodic Network Slices and, when necessary, of the Temporary/Periodic TAs supporting these Network Slices. + +### 6.24.2 Functional Description + +This proposal is optimizing the system behaviour when Temporary or Periodic Network Slices and any related temporary or periodic TAs are deployed, in a Serving PLMN. In addition, the HPLMN can provide for the S-NSSAI subscription information timing information which may or may not be the same as any absolute timing information for the corresponding slices in the VPLMN. The AMF in the serving PLMN combines any timing information received from UDM and in the Serving PLMN to derive the combined timing information. + +If a UE is capable of supporting optimizations for temporary/periodic Network Slice and TAs support, it signals in the UE MM capabilities that it can support the related RM and MM optimisation for temporary/periodic Network Slices. + +NOTE: whether temporary/periodic TAs support can be considered a standalone capability can be evaluated, but in principle one could deploy temporary TAs just to optimize the RM/Paging trade off at certain time of day, irrespective of the need to support temporary/periodic Network Slices with a AoS that does not match existing/permanent TA boundaries. + +For UEs that can support the temporary/periodic Network Slices optimizations, the UE can be provided with the timing information for the S-NSSAIs and any temporary/periodic TAs that are needed to support these slices. Otherwise, for non-supporting UEs, the network must provide at any time the information Configured NSSAI, Allowed NSSAI and TAI in the RA to UE that is consistent with the timing information. + +It is proposed that the timing information for Temporary/Periodic network slices and TAs is configured in the (R)AN and that the (R)AN can indicate it to the AMF alongside the related S-NSSAIs for the TAs where these temporary/periodic network slices are supported. + +The timing information can be passed to SMF also when PDU sessions are established to cause the local release of PDU sessions without additional signalling being needed. For periodic slices, the timing information allows the periodic deactivation and reactivation of PDU sessions without additional system wide signalling also. + +The timing information can be of the forms: + +- {Ts, Te} indicating an absolute time of start (Ts) and end (Te). + +- {Ts, [Tu, Td]}, indicating an absolute time of start Ts and an up time period (Tu) and a down time period (Td) with the first uptime starting at time Ts. + +## 6.24.3 Procedures + +### 6.24.3.1 RM aspects + +![Sequence diagram illustrating Registration Management aspects for network slices. The diagram shows interactions between UE, (R)AN, AMF, NSSF, and UDM. Step 0: OAM configures NG-RAN and AMF with supported network slices and timing information. UDM may also be provided with timing information. Step 1a: RAN and AMF update each other on network slice support per TA. RAN provides timing info to AMF, and AMF provides it to NSSF via NG setup and Nssf_Availability Update. Step 2a: Combined timing info from serving PLMN and UDM is used for allowed and configured NSSAI for non-supporting UEs. Step 2b: Combined timing info is provided to UEs for S-NSSAIs in the configured NSSAI. Step 3: UE locally adjusts RA, Allowed NSSAI, and configured NSSAI based on received info.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +The diagram illustrates the following sequence of events: + +- 0. OAM Configures NG-RAN, AMF with supported network slices. The RAN additionally has information on what NS is supported in which TA and for each temporary network slice and TA the related timing information** +- 0. the UDM may be provided with additional timing information per S-NSSAI (e.g. to cause decommissioning of a slice)** +- 1a. RAN and AMF update each other on the support of Network slices per TA. For Network slices and TAs available on a temporary basis, the relevant timing information is provided by the RAN to the AMF in the NG-Setup message (3GPP TS 38.413). The AMF provides the additional timing information for NSs and TAs to the NSSF.** +NG setup and Nssf\_Availability Update +- 2a. The combined timing information from serving PLMN and UDM is taken into account when providing the allowed NSSAI and configured NSSAI to non supporting UEs, as well as the RA if there are temporary TAs. This is impacting Registration messages and potentially UE configuration update messages are needed to update non supporting UEs of the changing Configured S-NSSAIs/allowed NSSAI when temporary/periodic slices are no longer available or become available.** +Registration and UCU +- 2b. For UEs supporting the temporary/periodic network slices optimizations, the combined timing information from UDM and serving PLMN is provided to the UE for S-NSSAIs in the configured NSSAI so the UE know when the configured NSSAI changes without need of additional signalling. In addition, any timing information for TAs in the RA is provided. The allowed NSSAI may include periodically available S-NSSAIs also when they are requested when the S-NSSAI is in the period when it is not available. This information is normally provided in the Registration Accept, but if update from UDM or RAN happens, the AMF can update the UE Configured NSSAI, and the RA TAs timing information by a UE configuration update** +Registration and UCU +- 3. For UEs supporting the temporary/periodic network slices optimizations, the UE locally adjusts the RA, Allowed NSSAI and configured NSSAI based on the received information** + +Sequence diagram illustrating Registration Management aspects for network slices. The diagram shows interactions between UE, (R)AN, AMF, NSSF, and UDM. Step 0: OAM configures NG-RAN and AMF with supported network slices and timing information. UDM may also be provided with timing information. Step 1a: RAN and AMF update each other on network slice support per TA. RAN provides timing info to AMF, and AMF provides it to NSSF via NG setup and Nssf\_Availability Update. Step 2a: Combined timing info from serving PLMN and UDM is used for allowed and configured NSSAI for non-supporting UEs. Step 2b: Combined timing info is provided to UEs for S-NSSAIs in the configured NSSAI. Step 3: UE locally adjusts RA, Allowed NSSAI, and configured NSSAI based on received info. + +Figure 6.24.3.1-1: Registration Management aspects + +Figure 6.24.3.1-1 above provides a synopsis of the RM impact for supporting and non-supporting UEs. Additionally, it shows which network entities are configured with the timing information and how the timing information is provided to the AMF and NSSF. The timing information in NSSF is the serving PLMN timing information for TAs and Network slices of the serving PLMN. In roaming case, the AMF provides to the NSSF the timing information for the mapped S-NSSAIs of HPLMN if any applies as received from the UDM. + +- The timing information for the S-NSSAIs in the serving PLMN is configured in the (R)AN, as well as any timing information for the TAs. The UDM can also be configured with timing information for S-NSSAIs in the UE subscriptions information. +- The (R)AN provides any per S-NSSAIs and any per TA timing information to the AMF using NG-Setup. The AMF also provides this information to the NSSF using the Nssf\_NSSAIAvailability\_Update service operation. +- The AMF and NSSF provide in a Registration Accept (and update, when necessary, by a UE Configuration Update Command) a **non-supporting UE** with the Configured NSSAI, allowed NSSAI and RA that are based on taking into account the combined timing information for the S-NSSAIs and the corresponding mapped S-NSSAIs of the HPLMN and also any timing information that is associated to the TAs received from the (R)AN at NG Setup. + +- 2b. The AMF and NSSF provide in a Registration Accept (and update, when necessary, by a UE Configuration Update Command) a **supporting UE** with the Configured NSSAI with the combined timing information for S-NSSAIs (based on serving PLMN and HPLMN information) and any timing information for the TAIs in the RA. The allowed NSSAI may include periodically available S-NSSAIs even when these are in the time period when these are not available. +3. A supporting UE which has received at step 2b timing information, can use it locally to adapt the Allowed NSSAI, Configured NSSAI and RA. For the S-NSSAI in the Configured NSSAI that are periodic, these can be used in the registration request in the Requested NSSAI even when the timing information indicates they are in the period when they are not available. The (R)AN and AMF/NSSF locally adapt without further signalling as the (R)AN is the source of the timing information and the AMF receives the information from the (R)AN at step 1a. + +### 6.24.3.2 Session Management aspect + +In order to ensure that there is a coherent end to end handling of the timing information, the UE may include this in the PDU Session Establishment Request (and update the timing information by PDU Session Modification request, if necessary). The UE can request explicitly that the PDU sessions are automatically released (e.g. if the respective network slices have an end of life timing information) or retained and restored (e.g. if the respective network slices have a periodic timing information). Alternatively, e.g. when the UE indicates no S-NSSAI when it establishes a PDU session, the UE indicated in the UE MM capabilities that it supports the SM timing information and the AMF can include this based on the combined S-NSSAIs timing information for the S-NSSAI (which may be also determined by the AMF) of the PDU session in the request towards the SMF that PDU sessions are automatically released (e.g. if the respective network slices have an end of lifecycle) or retained and restored (e.g. if the respective network slices are periodic). In all cases, the SMF that supports the feature then returns in the PDU session Establishment/Modification Accept and in the N1N2 the acceptance of the requested behaviour so that the UE and AMF and (R)AN can adapt locally the behaviour without any further signalling. In addition, the AMF provides the confirmed timing information for the PDU session to the (R)AN in N2 message transporting the PDU session Accept message to the (R)AN and triggering the DRBs configuration for the PDU session. The two behaviours are indicated in figures 6.24.3.2-1 and 6.24.3.2-2 respectively, where the new aspects of the procedure from TS 23.502 [5] are highlighted in boldface. The NAS message is a PDU session Request or a PDU session Accept as it can be understood from the context. + +![Sequence diagram of UE-requested PDU Session Establishment with timing indication from UE. The diagram shows interactions between UE, (R)AN, AMF, UPF, SMF, PCF, UDM, and DN. Key steps include PDU Session Establishment Request with automatic restoration/release timing indication, SMF selection, Nsmf_PDUSession_CreateSMContext Request, Subscription retrieval, PDU Session authentication/authorization, PCF selection, SM Policy Association Establishment, UPF selection, N4 Session Establishment/Modification Request, N2 PDU Session Request, AN-specific resource setup, and subsequent updates and notifications.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant DN + + Note right of AMF: 2. SMF selection + UE->>AMF: 1. PDU Session Establishment Request (automatic restoration/release timing indication, ) + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request (NASmsg (automatic restoration/release timing indication automatic restoration/release timing indication)) + SMF->>UDM: 4. Subscription retrieval/ Subscription for updates + UDM-->>SMF: + SMF->>AMF: 5. Nsmf_PDUSession_CreateSMContext Response () + Note over AMF, UPF: 6. PDU Session authentication/authorization + Note right of SMF: 7a. PCF selection + Note over SMF, PCF: 7b. SM Policy Association Establishment or SMF initiated SM Policy Association Modification + SMF->>PCF: + PCF-->>SMF: + Note right of SMF: 8. UPF selection + Note over SMF, UPF: 9. SMF initiated SM Policy Association Modification + SMF->>UPF: + UPF-->>SMF: + SMF->>AMF: 10a. N4 Session Establishment/Modification Request (automatic restoration/release timing indication) + AMF-->>SMF: 10b. N4 Session Establishment/Modification Response () + AMF->>SMF: 11. Namf_Communication_N1N2MessageTransfer NASmsg (automatic restoration/release timing indication), automatic restoration/release timing indication ) + AMF->>UE: 12. N2 PDU Session Request (NASmsg (automatic restoration/release timing indication), automatic restoration/release timing indication) + UE->>AMF: 13. AN-specific resource setup (PDU Session Establishment Accept (automatic restoration/release timing indication) ) + AMF->>UE: 14. N2 PDU Session Response + Note left of UE: First Uplink Data + UE-->>AMF: + AMF->>SMF: 15. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 16a. N4 Session Modification Request + UPF-->>SMF: 16b. N4 Session Modification Response + SMF->>UDM: 16c. Registration + UDM-->>SMF: + SMF->>AMF: 17. Nsmf_PDUSession_UpdateSMContext Response + AMF-->>SMF: 18. Nsmf_PDUSession_SMContextStatusNotify + SMF->>UPF: 19. IPv6 Address Configuration + Note over SMF, PCF: 20. SMF initiated SM Policy Association Modification + SMF->>PCF: + PCF-->>SMF: + Note right of SMF: 21. Unsubscription + SMF-->>UDM: + Note left of UE: First Downlink Data + UE-->>AMF: + +``` + +Sequence diagram of UE-requested PDU Session Establishment with timing indication from UE. The diagram shows interactions between UE, (R)AN, AMF, UPF, SMF, PCF, UDM, and DN. Key steps include PDU Session Establishment Request with automatic restoration/release timing indication, SMF selection, Nsmf\_PDUSession\_CreateSMContext Request, Subscription retrieval, PDU Session authentication/authorization, PCF selection, SM Policy Association Establishment, UPF selection, N4 Session Establishment/Modification Request, N2 PDU Session Request, AN-specific resource setup, and subsequent updates and notifications. + +Figure 6.24.3.2-1 UE-requested PDU Session Establishment with timing indication from UE + +![Sequence diagram for UE-requested PDU Session Establishment without timing indication from UE. The diagram shows interactions between UE, (R)AN, AMF, UPF, SMF, PCF, UDM, and DN. Key steps include PDU Session Establishment Request, SMF selection, Nsmf_PDUSession_CreateSMContext Request, subscription retrieval, PDU Session authentication/authorization, PCF selection, SM Policy Association Establishment, UPF selection, N4 Session Establishment/Modification, NASmsg transfer, N2 PDU Session Request, AN-specific resource setup, N2 PDU Session Response, First Uplink Data, Nsmf_PDUSession_UpdateSMContext Request, N4 Session Modification, Registration, Nsmf_PDUSession_UpdateSMContext Response, SMContextStatusNotify, IPv6 Address Configuration, SMF initiated SM Policy Association Modification, and Unsubscription.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant DN + + Note left of UE: 1. PDU Session Establishment Request () + UE->>AMF: 1. PDU Session Establishment Request () + Note right of AMF: 2. SMF selection + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request (automatic restoration/release timing indication) + SMF->>UDM: 4. Subscription retrieval/ Subscription for updates + UDM-->>SMF: + SMF->>AMF: 5. Nsmf_PDUSession_CreateSMContext Response () + Note right of AMF: 6. PDU Session authentication/authorization + AMF->>SMF: 6. PDU Session authentication/authorization + Note right of SMF: 7a. PCF selection + SMF->>PCF: 7b. SM Policy Association Establishment or SMF initiated SM Policy Association Modification + PCF-->>SMF: + Note right of SMF: 8. UPF selection + SMF->>UPF: 9. SMF initiated SM Policy Association Modification + UPF-->>SMF: + SMF->>AMF: 10a. N4 Session Establishment/Modification Request (automatic restoration/release timing indication) + AMF->>SMF: 10b. N4 Session Establishment/Modification Response () + SMF->>AMF: 11. Namf_Communication_N1N2MessageTransfer NASmsg (automatic restoration/release timing indication), automatic restoration/release timing indication ) + AMF->>RAN: 12. N2 PDU Session Request (NASmsg (automatic restoration/release timing indication), automatic restoration/release timing indication) + RAN->>UE: 13. AN-specific resource setup (PDU Session Establishment Accept (automatic restoration/release timing indication) ) + UE->>RAN: 14. N2 PDU Session Response + Note left of RAN: First Uplink Data + RAN->>UPF: First Uplink Data + AMF->>SMF: 15. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 16a. N4 Session Modification Request + UPF->>SMF: 16b. N4 Session Modification Response + SMF->>UDM: 16c. Registration + UDM-->>SMF: + SMF->>AMF: 17. Nsmf_PDUSession_UpdateSMContext Response + AMF->>SMF: 18. Nsmf_PDUSession_SMContextStatusNotify + SMF->>UPF: 19. IPv6 Address Configuration + Note right of SMF: 20. SMF initiated SM Policy Association Modification + SMF->>PCF: 20. SMF initiated SM Policy Association Modification + PCF-->>SMF: + Note right of SMF: 21. Unsubscription + SMF->>UDM: 21. Unsubscription + UDM-->>SMF: + +``` + +Sequence diagram for UE-requested PDU Session Establishment without timing indication from UE. The diagram shows interactions between UE, (R)AN, AMF, UPF, SMF, PCF, UDM, and DN. Key steps include PDU Session Establishment Request, SMF selection, Nsmf\_PDUSession\_CreateSMContext Request, subscription retrieval, PDU Session authentication/authorization, PCF selection, SM Policy Association Establishment, UPF selection, N4 Session Establishment/Modification, NASmsg transfer, N2 PDU Session Request, AN-specific resource setup, N2 PDU Session Response, First Uplink Data, Nsmf\_PDUSession\_UpdateSMContext Request, N4 Session Modification, Registration, Nsmf\_PDUSession\_UpdateSMContext Response, SMContextStatusNotify, IPv6 Address Configuration, SMF initiated SM Policy Association Modification, and Unsubscription. + +Figure 6.24.3.2-2: UE-requested PDU Session Establishment without timing indication from UE + +Figure 6.24.3.2-3 here below shows the procedure for PDU session modification. it should be noted that this figure shows the UE providing the updated timing information because it has received an updated timing information from the AMF for the related network slice S-NSSAI. However, it is also possible for the AMF to initiate this if the RAN is providing the updated PDU session related modification to the AMF for capable UEs (for which timing information was provided to the RAN for the PDU session). which approach to select can be further studied. + +![Sequence diagram for UE-requested PDU Session Modification with timing indication from UE. The diagram shows interactions between UE, RAN, AMF, SMF, UPF (I-UPFs), UDM, and PCF. The process involves a PDU Session Modification Request from the UE, followed by various internal signaling steps (Nsmf_PDUSession_UpdateSMContext, N4 Session Establishment/Modification, SM Policy Association Modification) and finally a PDU Session Modification Command Ack from the UE.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UPF as UPF (I-UPFs) + participant UDM + participant PCF + + Note right of AMF: automatic restoration/release timing indication + + UE->>RAN: 1a. PDU Session Modification Request + RAN->>AMF: 1a. Nsmf_PDUSession_UpdateSMContext + Note right of SMF: automatic restoration/release timing indication + SMF->>PCF: 1b. PCF initiated SM Policy Association Modification + SMF->>UDM: 1c. Nudm_SDM_Notification + Note right of SMF: 1d. QoS Update Trigger + RAN->>AMF: 1e. N2 message (PDU session ID, SM information) + AMF->>SMF: 1e. Nsmf_PDUSession_UpdateSMContext + AMF->>SMF: 1f. Nsmf_PDUSession_UpdateSMContext + AMF->>SMF: 1g. Nsmf_PDUSession_UpdateSMContext + SMF->>PCF: 2. SMF initiated SM Policy Association Modification + SMF->>UPF: 2a. N4 Session Establishment/Modification + UPF->>SMF: N4 Session Establishment/Modification Response + SMF->>AMF: 3a. Response of Nsmf_PDUSession_UpdateSMContext (NASmsg(automatic restoration/release timing indication), automatic restoration/release timing indication) + AMF->>SMF: 3b. Namf_Communication_N1N2MessageTransfer + SMF->>AMF: 3c. Nsmf_PDUSession_SMContextStatusNotify + SMF->>AMF: 3d. Nsmf_PDUSession_SMContextStatusNotify + AMF->>RAN: 4. N2 Message (NASmsg(automatic restoration/release timing indication), automatic restoration/release timing indication) + RAN->>UE: 5. AN-specific resource modification of transport (including PDU Session Modification Command (automatic restoration/release indication) / Ack) + RAN->>AMF: 6. N2 Message + AMF->>SMF: 7a. Nsmf_PDUSession_UpdateSMContext Request + SMF->>AMF: 7b. Nsmf_PDUSession_UpdateSMContext Response + SMF->>UPF: 8a. N4 Session Modification Request + UPF->>SMF: 8b. N4 Session Modification Response + UE->>RAN: 9. PDU Session Modification Command Ack + RAN->>AMF: 10. N2 NAS uplink transfer + AMF->>SMF: 11a. Nsmf_PDUSession_UpdateSMContext Request + SMF->>AMF: 11b. Nsmf_PDUSession_UpdateSMContext Response + SMF->>UPF: 12a. N4 Session Modification Request + UPF->>SMF: 12b. N4 Session Modification Response + SMF->>PCF: 13. SMF initiated SM Policy Association Modification + +``` + +Sequence diagram for UE-requested PDU Session Modification with timing indication from UE. The diagram shows interactions between UE, RAN, AMF, SMF, UPF (I-UPFs), UDM, and PCF. The process involves a PDU Session Modification Request from the UE, followed by various internal signaling steps (Nsmf\_PDUSession\_UpdateSMContext, N4 Session Establishment/Modification, SM Policy Association Modification) and finally a PDU Session Modification Command Ack from the UE. + +Figure 6.24.3.2-3: UE-requested PDU Session Modification with timing indication from UE + +## 6.24.4 Impacts on services, entities and interfaces + +The following impacts are foreseen by this solution: + +UE: + +- indication of support of the feature(s) in this proposal +- supports handling of timing information for S-NSSAIs and TAIs in RM and in SM +- locally adapt the behaviour based on timing information received. + +(R)AN: + +- supports configuration of temporarily/periodically available s-NSSAIs and TAIs. + +- Provides the indication per TAI of the Temporarily/Periodically available S-NSSAIs, including for TAIs which are temporarily available, to the aMF in NG setup. +- determines when certain DRBs are no longer active for certain sessions and release them (or deactivates, for periodic slices) them when UE when timing information is requesting that, upon receiving confirmation from the AMF that it can do so based on the capability of UE and the SMF capabilities (i.e when it receives the timing information for the PDU session). The (R)AN may also initiate modification of the PDU session when new timing information is provided to the (R)AN (TBD whether the UE or the (R)AN should initiate the modification) + +## AMF: + +- handle the timing information for S-NSSAIs coming from (R)AN and UDM and combine it into a timing information for the UE subscribed S-NSSAIs. +- handle any timing information for TAIs received from the (R)AN +- update NSSF with timing information for S-NSSAIs and TAI received from the (R)AN +- provide the non-supporting UEs with Configured NSSAI, Allowed NSSAIs and RA based on the combined timing information +- provide the supporting UEs with Configured NSSAI including combined timing information for some S-NSSAIs if any and RA including TAIs with timing information if any. +- locally adapt the Allowed NSSAI and RA for the UE based on the respective provided combined timing information + +## NSSF: + +- handle the timing information for S-NSSAIs coming from AMF. +- handle any timing information for TAIs received from the AMF +- receive update from AMF with timing information for S-NSSAIs and TAI received from the (R)AN +- provide the non-supporting UEs with Configured NSSAI, Allowed NSSAIs and RA based on the combined timing information +- provide the supporting UEs with Configured NSSAI including combined timing information for some S-NSSAIs if any and RA including TAIs with timing information if any. + +## SMF: + +- support of the timing information-based automatic release or retention and restoration of PDU sessions + +## UDM + +- Support the indication of timing information to AMFs for S-NSSAIs in the subscription information. + +## 6.25 Solution #25: Handling Rejected S-NSSAIs in some TAs of RA + +### 6.25.1 Key Issue mapping + +This solution is related to KI#5 regarding improved support of RAs including TAs supporting Rejected S-NSSAIs. + +### 6.25.2 Functional Description + +This solution proposes AMF to provide additional slice information in TA granularity to UE related to UE's current RA. The additional slice information is based on UE requested S-NSSAI which is only available in some TAs of UE's RA. The additional slice information comprises the mapping between an S-NSSAI within the rejected S-NSSAIs and TAIs that can support/or cannot support such S-NSSAI. e.g. the information can be either S-NSSAI 1 in the rejected S-NSSAI together with the TAI(s) supporting it, or indicating S-NSSAI 1 is rejected for TAI1, TAI2, TAI3. The current cause value "rejected S-NSSAI in the RA" can be changed to "rejected S-NSSAI in current TA". Thus, when UE moves + +out of the current TA, it can start registration update to get updated allowed NSSAI including also the rejected S-NSSAI in the previous TA and potentially also a new RA. AMF can also provide additional slice information to UE, so that UE can start registration update only when moves to a TA where the rejected S-NSSAI can be supported. + +In both options, UE can initiate the service request with new allowed NSSAI after the registration update in the new TA. The difference is just the number of rejected S-NSSAI and TAI pairs to be included in the signalling to the UE. + +NOTE: Such registration update is based on the application requirements, UE can also decide not to perform registration update when changes to a new TA. + +### 6.25.3 Procedures + +The provision of rejected S-NSSAI of a TA to UE uses the existing UE registration procedure or UE configuration update procedure. Each rejected S-NSSAI should also indicate the correspondent TAI. + +![Sequence diagram of UE registration and registration update procedure showing interactions between UE, AMF, and UDM/NSSF.](0d9b44054c70dcda35129f11b97a912f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM/NSSF + UE->>AMF: 1.Registration request + rect rgb(255, 255, 255) + Note over AMF,UDM/NSSF: 2. Slice authorization and selection + AMF->>UDM/NSSF: + UDM/NSSF-->>AMF: + end + AMF->>UE: 3. Registration response + rect rgb(255, 255, 255) + Note over UE: 4. Detection of new TA change + end + UE->>AMF: 5.Registration update + AMF->>UE: 6.Registration response + rect rgb(255, 255, 255) + Note over UE,AMF: 7.service request with previously rejected S-NSSAI + UE->>AMF: + end + +``` + +Sequence diagram of UE registration and registration update procedure showing interactions between UE, AMF, and UDM/NSSF. + +**Figure 6.25.3-1: UE registration and registration update procedure** + +1. UE sends registration request to AMF. The UE shall indicate the capability support of receiving additional slice information in the registration request. +2. AMF decides the Registration Area, Allowed NSSAI, additional slice information in TA granularity (e.g. rejected S-NSSAI with the rejected/supported TAI(s)) for this RA with the help of UDM/NSSF. For UEs with the capability indicated in step 1, AMF decides the Registration Area including the TA supporting Rejected S-NSSAI and sends the additional slice information to the UE. + +NOTE 1: The Allowed NSSAI is still homogeneously supported in the RA. + +NOTE 2: For UEs without the capability, AMF decides the Registration Area as specified in clause 5.3.4.3.3 of TS 23.501 [2] (i.e. the AMF shall set the RA so that the RA does not include TAs supporting the S-NSSAIs rejected for the RA). + +NOTE 3: The rejected S-NSSAI here is limited to the one with the rejection cause of slice not available in the current TA. + +3. AMF includes the Allowed NSSAI, additional slice information in TA granularity and Registration Area in Registration response to UE. +4. UE detects that it enters a new TA, where one of the previously rejected S-NSSAIs can be supported. +5. UE can send registration update with the previously rejected S-NSSAI in step 4 in the Requested NSSAI to AMF + +NOTE 4: UE can decide not to perform registration update when changes to a new TA based on the application requirements. + +6. AMF response to UE with updated allowed NSSAI, updated additional slice information in TA granularity as well as the updated Registration Area. The interaction with UDM and NSSF is not needed in this step since the rejected S-NSSAI is only due to the slice availability in the previous TA. +7. If the previously rejected S-NSSAI is included in the updated allowed NSSAI from the AMF, UE can request service of that S-NSSAI. + +![Sequence diagram of UE configuration update procedure. Lifelines: UE, AMF, UDM/NSSF. The process starts with the network identifying the need to update the UE on slice support info. This is followed by a UE configuration update from AMF to UE. The UE then detects a new TA change. The UE sends a registration update to the AMF, which responds with a registration response. Finally, the UE sends a service request with the previously rejected S-NSSAI to the AMF.](d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM_NSSF as UDM/NSSF + Note right of AMF: 1. Network identifies the needs to update UE on slice support info + AMF->>UE: 2. UE configuration update + Note left of UE: 3. Detection of new TA change + UE->>AMF: 4. Registration update + AMF-->>UE: 5. Registration response + UE->>AMF: 6. service request with previously rejected S-NSSAI + +``` + +Sequence diagram of UE configuration update procedure. Lifelines: UE, AMF, UDM/NSSF. The process starts with the network identifying the need to update the UE on slice support info. This is followed by a UE configuration update from AMF to UE. The UE then detects a new TA change. The UE sends a registration update to the AMF, which responds with a registration response. Finally, the UE sends a service request with the previously rejected S-NSSAI to the AMF. + +Figure 6.25.3-2: UE configuration update procedure + +1. Network may decide to update UE on the slice support information of a TA in UE's RA, e.g. due to the change of slice load in a certain TA. +2. In such cases, AMF provides UE with additional slice information in TA granularity in the UE configuration update procedure. +- 3-6. is the same as steps 4-7 in previous case. + +## 6.25.4 Impacts on services, entities and interfaces + +AMF: + +- Provide additional slice information in TA granularity to UE. + +UE: + +- Storage of additional slice information in TA granularity. +- Initiate registration update procedure based on additional slice information when needed. +- Indicate the capability support of receiving additional slice information in the registration request. + +## 6.26 Solution #26: Multiple areas and resource partitioning + +### 6.26.1 Introduction + +This solution applies to KI#5 and KI#3. + +## 6.26.2 Functional Description + +### 6.26.2.1 Support of multiple areas + +As TACs in 5GS uses 3 octets compared to 2 octets in EPS allows to define more and smaller TAs. In fact, KI#5 drives the need to define smaller TAs as to maintain a uniform support of network slice availability per TA. Defining smaller TAs and supporting moving UEs will likely challenge the current maximum of 16 TAs within an RA and supporting TAs with different capabilities and network slice availability will also drive the need for enabling the UE being registered with multiple network slices while some are only available in a subset of the TAs of the UE's RA. + +The following principles are proposed as to address the above aspects: + +- The total number of TAs of the RA is increased; +- S-NSSAIs can be available and registered for all of the TAs of the RA or for a subset of the RA; +- The AMF/NSSF can provide S-NSSAIs and TAs to the UE as follows: + - Allowed NSSAI includes S-NSSAIs that are registered in the whole RA; + - List of Secondary Allowed NSSAI and associated Secondary RA: + - A Secondary Allowed NSSAI includes S-NSSAIs that are registered and available in the associated Secondary RA; + +**Editor's note:** It is FFS whether the associated Secondary RA needs to be a set of TAs that are a subset of the RA, or if it is possible to include TAs that are not part of the RA. + +**Editor's note:** It is FFS whether information like network capabilities, IMS voice support indication etc are to be kept per RA or adding the possibility to indicate Secondary RA. + +**Editor's note:** It is FFS whether slicing functionality like NSSAA, NSAC and NSSRG are to be set for the RA or per Secondary RA. + +- The UE is not allowed to register an S-NSSAI in a TA where the S-NSSAI is not defined to be available; +- If an S-NSSAI is registered and the UE moves to a TA where the S-NSSAI is not defined to be available then: + - UP for any PDU Sessions for the S-NSSAI will be deactivated; + - The UE is not allowed to request to activate UP for a PDU Session for such S-NSSAI; +- If the UE is paged for an S-NSSAI and the UE is located in a TA where the S-NSSAI is not defined to be available, then the UE replies to the paging but the AMF/SMF ensures that the UP is not activated. + +### 6.26.2.2 Reducing resources for cells outside service area + +While maintaining the network slice availability uniform per TA it means that some cells can be located outside the service area i.e. there is no need for the operator to serve the customer services (e.g. meeting the KPIs) using the network slice in those cells. + +A TA with cells within a customer provided service area and cells outside the customer provided service area while is visualized in Figure 6.26.2.2-1. + +![Diagram illustrating the relationship between a customer-provided service area and network cells within a Tracking Area (TA-1).](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +The diagram shows a large grey oval representing 'TA-1'. Inside this oval, there are several colored circles representing cells: Cell-D (light blue), Cell-E (yellow), Cell-A (red), Cell-B (green), and Cell-C (purple). A smaller, semi-transparent purple oval labeled 'Customer provided area' is overlaid on the cells, covering Cell-A, Cell-B, and Cell-C. Cell-D and Cell-E are outside this customer-provided area but still within TA-1. Cell-F (orange) is located outside the TA-1 oval entirely. + +Diagram illustrating the relationship between a customer-provided service area and network cells within a Tracking Area (TA-1). + +**Figure 6.26.2.2-1: Example of customer provided service area relation to cells** + +The following principles are used for cells inside and outside the customer defined service area while maintaining uniform support of network slices within the TA: + +- Customer wants service in a specific area i.e. the customer provided area. +- Operator uses a network slice with S-NSSAI-1 for the customer +- When UE uses cell A-C the user will get service as specified in agreed KPI's. +- S-NSSAI-1 is defined to be available in TA-1 (i.e. available in cells A-E) +- When UE is in cell D,E, the S-NSSAI is available, but only shared resources are allocated to the S-NSSAI-1 i.e. cannot expect to get the KPI's as agreed to be available within the customer provided area. +- When user moves out of TA to Cell-F the S-NSSAI-1 is not available. + +For the cells outside the service area, but within the TA i.e. cells D and E, the operator defines that the network slice is available but defines the RRM policies such that the network slice uses shared resources, see figure 4.3.36-2 from TS 28.541 [13]. As the network slice only get shared resources outside the service area means that the network slice does not compete with other network slices requiring dedicated resources in that cell and also means that uniform support of network slices can be maintain by re-using existing OAM mechanisms. + +![Figure 6.26.2.2-2: Structure of RRM Policy Ratio. A vertical bar chart showing resource allocation from 0 to 100%. The bar is divided into three sections: 'Dedicated resources' at the bottom, 'Prioritized resources' in the middle, and 'Shared resources' at the top. Horizontal lines mark the boundaries: rRMPolicyDedicatedRatio between Dedicated and Prioritized, rRMPolicyMinRatio between Prioritized and Shared, and rRMPolicyMaxRatio between Shared and the top (100%).](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +Figure 6.26.2.2-2: Structure of RRM Policy Ratio. A vertical bar chart showing resource allocation from 0 to 100%. The bar is divided into three sections: 'Dedicated resources' at the bottom, 'Prioritized resources' in the middle, and 'Shared resources' at the top. Horizontal lines mark the boundaries: rRMPolicyDedicatedRatio between Dedicated and Prioritized, rRMPolicyMinRatio between Prioritized and Shared, and rRMPolicyMaxRatio between Shared and the top (100%). + +Figure 6.26.2.2-2: Structure of RRM Policy Ratio + +### 6.26.3 Procedures + +Figure 6.26.3-1 shows a high-level description of the proposed impacts to the registration procedure. + +![Figure 6.26.3-1: Registration procedure. A sequence diagram showing interactions between UE, AMF, and NSSF. 1. UE sends 'Registration request' to AMF. 2. AMF sends 'Nssf_NSSelection_Get' to NSSF. 3. AMF performs 'Create RA and register S-NSSAIs based on network slice availability'. 4. AMF sends 'Registration accept' to UE. 5. UE performs 'Change cell' (dashed box). 6. UE and AMF perform 'PDU Session Establishment' (dashed box).](832a0ce332e784fe80289e9f00f56574_img.jpg) + +Figure 6.26.3-1: Registration procedure. A sequence diagram showing interactions between UE, AMF, and NSSF. 1. UE sends 'Registration request' to AMF. 2. AMF sends 'Nssf\_NSSelection\_Get' to NSSF. 3. AMF performs 'Create RA and register S-NSSAIs based on network slice availability'. 4. AMF sends 'Registration accept' to UE. 5. UE performs 'Change cell' (dashed box). 6. UE and AMF perform 'PDU Session Establishment' (dashed box). + +Figure 6.26.3-1: Registration procedure + +The Registration procedure in TS 23.502 [5] is used with following modifications: + +1. The UE provides Requested NSSAI in Registration Request based on available information; +2. The AMF provides NSSAI information to NSSF as per existing procedures; +3. The AMF creates an RA and Allowed NSSAI as per existing procedures and the AMF can in addition create a list of Secondary Allowed NSSAI and associated Secondary RA. The S-NSSAIs in the Secondary Allowed NSSAI can be S-NSSAIs that NSSF rejected for the RA or S-NSSAIs that are available in the UE's current TA while not available in all TAs of the RA. +4. The AMF provides the Registration Accept with the additional list of Secondary Allowed NSSAI and associated Secondary RA. + +5. If the UE moves to a different cell in a different TA within the RA, the UE checks such that the S-NSSAI is available for the TA before trying to e.g. activate UP for a PDU Session using the S-NSSAI. +6. The UE is allowed to establish PDU Sessions for S-NSSAIs that are defined to be available in the UE's current TA. + +## 6.26.4 Impacts on services, entities and interfaces + +The following impacts have been identified: + +UE: + +- Support of Secondary Allowed NSSAI and associated Secondary RA and logic to avoid activating UP outside the TAs defined for the S-NSSAI. + +AMF: + +- Support of Secondary Allowed NSSAI and associated Secondary RA and logic to enforce such that UP cannot be activated outside the TAs defined for the S-NSSAI; +- Create RA including TAs where some requested S-NSSAIs are not available. + +## 6.27 Solution #27: Exception to the rejected NSSAI handling + +### 6.27.1 Introduction + +This solution applies to KI#5 i.e. how to allow the UE to initiate a registration for an S-NSSAI which was rejected for the RA when the UE enters a TA that is part of the RA and the TA supports this S-NSSAI. + +The issue scenario is that initially UE receives a rejected S-NSSAI for the current Registration Area. Then UE enters another TA that is part of the RA and the TA "may" support this S-NSSAI. + +### 6.27.2 Functional Description + +This solution outlines are as follows: + +The AMF + +- provides the rejected S-NSSAIs for the current RA per current mechanism i.e. no new cause value. +- associates an indication to rejected S-NSSAI(s) for an exceptional handling that UE can use the S-NSSAI even if UE stores the S-NSSAI in the rejected NSSAI storage for the current RA when the UE enters another TA in the current RA and provides the associated indication to the UE. +- may associate a list of TA (included in the current RA) where the rejected S-NSSAI is supported and provide it to the UE. + +The UE + +- stores the received rejected NSSAI per current mechanism. +- sends a 5GMM capability of support of new slice granularity i.e. per tracking area in Registration Request message. +- can use the S-NSSAI stored in rejected NSSAI storage if the received exception indication indicates that it is allowed to use the S-NSSAI when the UE enters another TA in the current RA. +- shall not use the S-NSSAI stored in rejected NSSAI storage if the received indication indicates that it is not allowed to use the S-NSSAI when the UE enters another TA in the current RA. + +### 6.27.3 Procedures + +![Sequence diagram illustrating the exceptional handling of Rejected NSSAI between a UE and an AMF. The diagram shows four steps: 1. Registration Request (support of new slice granularity) from UE to AMF; 2. Continue Registration procedure (a block); 3. Registration Accept (Rejected S-NSSAI with exception indication) from AMF to UE; 4. Continue Registration procedure (a block).](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + Note right of AMF: 2. Continue Registration procedure + UE->>AMF: 1. Registration Request (support of new slice granularity) + Note left of UE: 4. Continue Registration procedure + AMF-->>UE: 3. Registration Accept (Rejected S-NSSAI with exception indication) + +``` + +Sequence diagram illustrating the exceptional handling of Rejected NSSAI between a UE and an AMF. The diagram shows four steps: 1. Registration Request (support of new slice granularity) from UE to AMF; 2. Continue Registration procedure (a block); 3. Registration Accept (Rejected S-NSSAI with exception indication) from AMF to UE; 4. Continue Registration procedure (a block). + +**Figure 6.27.3-1: Exceptional handling of Rejected NSSAI** + +1. The UE initiates Registration procedure. The Registration Request message includes a 5GMM capability of support of new slice granularity i.e. per tracking area. +2. The AMF continues with Registration procedure. +3. The AMF sends Rejected S-NSSAI(s) with the cause value "S-NSSAI not available in the current registration area" and an associated exception indication. The exception indication indicates the exception to the Rejected S-NSSAI handling. If operator and implementation policy require, the AMF may also provide a list of TA (included in the current RA) where the rejected S-NSSAI(s) is supported and associated the list of TA to each rejected S-NSSAI. +4. The UE continues with Registration procedure. + +When the UE moves to another TA in current RA where the UE received the Rejected S-NSSAI and the cause value indicates "S-NSSAI not available in the current registration area", if the exception indication indicates that the Rejected S-NSSAI(s) is TA granularity so that it is allowed to use the Rejected S-NSSAI in another TA, the UE is allowed to use the Rejected S-NSSAI in the Registration procedure. If the previously Rejected S-NSSAI is included in the Allowed NSSAI, UE can request the service for the S-NSSAI. If the AMF provides a list of TA associated with the rejected S-NSSAI(s) to the UE, the UE will send Registration Request for the rejected S-NSSAI when the UE moves into a new TA that is in the list of TA. + +For example, the simple implementation of the exception indication can be realized by adding 1 bit indication in octet 3 bit 8 of TS 24.501 [16] Figure 9.11.3.75.2 Extended rejected NSSAI information element. + +**NOTE:** It is left to Stage-3 specifications to define the exact format of how the exception indication information would be provided to the UE. Here, for the purpose clarifying the aspect of "simple implementation", the example format is shown. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +|--------------------|--------------|---|---|--------------------|---|---|---|------------------------------------|--|--|--|--|--|--|--| +| NSI | Type of list | | | Number of elements | | | | octet 3 | | | | | | | | +| Rejected S-NSSAI 1 | | | | | | | | octet 4 | | | | | | | | +| Rejected S-NSSAI 2 | | | | | | | | octet j
octet j+1* | | | | | | | | +| ... | | | | | | | | octet k*
octet k+1 | | | | | | | | +| Rejected S-NSSAI n | | | | | | | | octet p*
octet p+1*
octet m* | | | | | | | | + +Network Slice per TA (octet 3, bit 8) + This bit indicates if it is allowed to use the associated S-NSSAIs when the UE enters a new TA in current registration area + 0 Network Slice per TA not allowed + 1 Network Slice per TA allowed + +## 6.27.4 Impacts on services, entities and interfaces + +The following impacts have been identified: + +UE: + +- sending a 5GMM capability of support of new slice granularity i.e. per tracking area in Registration Request message. +- performing the exceptional handling of Rejected S-NSSAI. + +AMF: + +- providing an exception indication indicates that the Rejected S-NSSAI(s) is TA granularity so that it is allowed to use the Rejected S-NSSAI in another TA. +- providing a list of TA associated to the rejected S-NSSAI. + +## 6.28 Solution #28: Support of network slices with TA granularity within a RA + +### 6.28.1 Functional Description + +If the Requested NSSAI contains S-NSSAI(s) that is (are) available only in some specific TA(s), the UE should be allowed to request the rejected S-NSSAI(s) again once it moves to a new TA within the RA. + +In order to achieve this, the AMF includes a new rejection cause value for the list of Rejected S-NSSAIs that are rejected due to not being available in the current TA. The new rejection cause value is defined as the following: + +"S-NSSAI not available in the current tracking area". + +If all the Requested NSSAI(s) are rejected in the current TA, the AMF includes a new cause code in Registration Reject message. This cause code will give a hint to the UE that Requested NSSAI(s) is (are) rejected only in the current tracking area. The new rejection cause code is defined as the following: + +"No S-NSSAI available in the current tracking area". + +When the UE moves to a different TA within the same RA and the UE has received at least one Rejected NSSAI with "S-NSSAI not available in the current tracking area" rejection cause value, then the UE can perform a Mobility + +Registration Update procedure and include any of the Rejected S-NSSAIs in the Requested NSSAI of the Registration Request that were rejected in the previous TA with "S-NSSAI not available in the current tracking area" rejection cause value. + +When the UE moves to a different TA within the same RA and the UE has received the "No S-NSSAI available in the current tracking area" rejection cause code in the Registration Reject message, then the UE can perform the initial Registration procedure and include any Requested NSSAI(s) in the Registration Request that were rejected in the previous TA. + +In order to decrease the number of Mobility Registration Update requests at every TA change, the AMF, optionally, should also generate a Supported TAI list for each Rejected NSSAI(s) including the TAs where the Requested NSSAI(s) is (are) supported within the RA and include such list together with the Rejected NSSAI(s) along with the new rejection cause value. + +Using the Supported TAI list, the UE only triggers the Mobility Registration Update procedure when it enters a TA that is part of the Supported TAI list. + +## 6.28.2 Procedures + +The solution relies on existing registration procedures defined in clause 4.2.2.2.2 of TS 23.502 [5] with the exception that Mobility Registration Update at step 1 can also be generated upon changing to a new TA inside the RA. Optionally, the trigger to generate Mobility Registration Update can be restricted to the case when the UE enters a TA that is part of the Supported TAI list. + +## 6.28.3 Impacts on Existing Nodes and Functionality + +UE: + +- Processes "S-NSSAI not available in the current tracking area" rejection cause value. +- Processes "No S-NSSAI available in the current tracking area" rejection cause code. +- Performs Mobility Registration Update procedure at every TA change within the RA until the Requested NSSAI is allowed. Optionally, the UE performs Mobility Registration Update procedure when the UE enters a TA that is part of the Supported TAI list. + +AMF: + +- Includes "S-NSSAI not available in the current tracking area" rejection cause value for the Rejected S-NSSAI in Registration Accept message if the Requested NSSAI is not available in the current TA. +- Includes "No S-NSSAI available in the current tracking area" rejection cause code in the Registration Reject message if none of the Requested NSSAI(s) is (are) available in the current TA. +- Includes a Supported TAI list for each Rejected NSSAI(s) including the TAs where the Requested NSSAI(s) is (are) supported within the RA. + +## 6.29 Solution #29: On handling S-NSSAIs not supported in certain TAs of a RA during a registration + +### 6.29.1 Introduction + +This solution addresses KI#5 and also benefits KI#3 solutions like solution in clause 6.9. + +Specifically: The Secondary TAs in the solution are conceivably supporting additional slices that are not supported in the whole primary TA. It can often happen that the primary TAs support commonly used slices like eMBB and the Secondary TAs are related to the Area of Service (AoS) of more specific slices like those associated with venues, enterprise slices with a smaller AoS that often would not map to any deployed TA perfectly. So, a UE supporting solution in 6.9 can be given an RA including both primary and Secondary TAs in the RA TAI list and the Secondary TAs are typically associated to e.g. Partially Allowed or Partially rejected S-NSSAIs in the RA. + +This Solution proposes optimizations of the RA formation while taking into account the S-NSSAIs of the requested NSSAI. + +## 6.29.2 Functional Description + +This solution covers the case a UE is registering with a S-NSSAI from a TA where at least one of the S-NSSAIs in the Requested NSSAIs is not supported. In rel-17 the only possible solution to let the UE attempt to register again with any such S-NSSAI would be to indicate a RA which only includes the TAI where allowed S-NSSAIs are supported, but then exclude from the RA any TAI where at least one of the rejected S-NSSAIs is supported. This however was limiting the RA formation optimality. In Rel-18 we propose to resolve this by proposing that two options can be supported by a network for supporting UEs: + +- 1) the UE is provided with a RA including TAI where the S-NSSAIs which are not supported in the current TA are also included, but for each rejected S-NSSAI the AMF provides a list of TAI in the RA where the rejected S-NSSAI is supported (or, alternately, a list of TAI in the RA where the rejected S-NSSAI is known to be not supported). This allows the UE, when it is camping in a cell of a TAI where the rejected S-NSSAI is known to be supported, to be able to trigger registration with such S-NSSAI if needed. The AMF provides for S-NSSAIs that are rejected in the whole RA the existing cause code ("Not supported in the RA") and for S-NSSAIs that are rejected in a subset of the RA TAI a new cause code " Partially Rejected/supported in the RA" or some similar cause code +- 2) the alternative is that the AMF provides an Allowed NSSAI that is known to be supported in the whole RA (if any) and then one or more "Partially Allowed S-NSSAI in the RA" including for each the Partial RA (subset of the RA) where these are supported. the advantage of this approach is that the UE can avoid further registrations as it moves in the RA among TAI where the support of the Slices changes. This solution option shows also how the MO/MT transaction in idle mode happen and how the connected mode mobility is supported. + +Both options can be supported in the same network as for instance the option 1) is optimal for the case where the AMF does not support both S-NSSAIs indicated in Requested NSSAI (so redirection to a AMF supporting both happens only if the UE lands at some point in a TA supporting both S-NSSAIs and the UE does still request both). Option 2) is more convenient when the AMF supports all the requested S-NSSAIs that it indicates in the Allowed NSSAI and in partially allowed S-NSSAIs. Also, it is possible to combine the two approaches in one procedure (e.g. let's suppose that there is a third S-NSSAI3 that is partially supported in the RA but not in the AMF in case 2), then this third S-NSSAI could be rejected with indication of where this S-NSSAI3 works). + +In addition. if a S-NSSAI is subject to NSSAA and the UE is not yet authorised (NSSAA has not already occurred earlier) but not supported in current TA, the AMF behaviour is to indicate it is "Partially rejected in the RA" so NSSAA is executed upon the UE registering in the TA where the S-NSSAI is supported (if the S-NSSAI was partially allowed this means the UE would not cause the triggering of NSSAA). + +For slices subject to simultaneous use constraints, the operator can only include in the same registration accept Allowed NSSAI and/or Partially allowed S-NSSAIs which can work together in the same TAI for all the TAI where the S-NSSAIs are allowed to be used together simultaneously. + +If a S-NSSAI is subject to NSAC, the operator indicates the S-NSSAI not supported in the current TA is "Partially rejected in the RA", so that the counting of Allowed S-NSSAIs is matching exactly what is allowed at any time. Whether it could be desirable to enable operators to also support the behaviour where the Partially allowed S-NSSAIs is counted (so that the additional registration is avoided upon mobility inside the RA) can be further discussed in normative phase. + +When there are overlapping TAs with TA(s) where a S-NSSAI which is partially rejected is supported, which however do not support the S-NSSAI, a further optimization is to indicate to the UE the TAs where the UE is allowed attempting to register with a Partially Rejected S-NSSAI, even if it is not in the list of TAs where the slice is actually supported. Similarly, for the case of Partially Allowed S-NSSAI, a further optimization is to indicate to the UE the TAs where the UE is allowed attempting to e.g perform a SR or establish a session within a Slice that was indicated as partially allowed, even if it is not in the list of TAs where the slice is actually supported. This type of optimization enables avoiding blind attempts to use the slice. + +This indication of TAs where the UE can initiate registration (or, respectively, service request and PDU session establishment/modification) can be done with an explicit indication of such TAs in the Registration accept/UE configuration update when the Partially rejected/Allowed S-NSSAI is provided. + +In the message flows in the following clauses, we do not show this particular optimization for overlapping TAs and rather show for the partially allowed TA the case without such optimization. + +## 6.29.3 Procedures + +### 6.29.3.1 Indication to UE of TAs where the rejected S-NSSAI is supported (or is not supported) in the RA + +![Sequence diagram illustrating the registration process with a rejected S-NSSAI. The diagram shows two registration attempts. In the first, the UE registers in TAI 1, requesting S-NSSAI 1 and 2. The AMF rejects S-NSSAI 2, indicating it is supported in TAI 2, and provides RA = (TAI1, TAI2). In the second, the UE registers in TAI 2, requesting S-NSSAI 1 and 2. The AMF accepts both and provides RA = (TAI2).](a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + Note left of UE: 0. UE is camping in a cell in TAI 1 and requests S-NSSAI 1 and S-NSSAI 2 + UE->>AMF: 1. Registration Request (Request NSSAI (S-NSSAI1, S-NSSAI2)) + Note right of AMF: 2. AMF determines the Requested NSSAI includes S-NSSAI 2 not supported in TAI 1 but it is supported in TAI 2. Includes TAI1, TAI 2 in RA, indicates S-NSSAI 2 is rejected with new cause code "partly rejected in RA" + AMF-->>UE: 3. Registration Accept (Allowed NSSAI (S-NSSAI1), Rejected S-NSSAI2(supported in TAI2), RA= (TAI1, TAI2) ) + Note left of UE: 4. UE is camping in a cell in TAI 2 and requests S-NSSAI 1 and S-NSSAI 2 + UE->>AMF: 5. Registration Request (Request NSSAI (S-NSSAI1, S-NSSAI2)) + AMF-->>UE: 3. Registration Accept (Allowed NSSAI (S-NSSAI1, S-NSSAI 2), RA= (TAI2) ) + +``` + +Sequence diagram illustrating the registration process with a rejected S-NSSAI. The diagram shows two registration attempts. In the first, the UE registers in TAI 1, requesting S-NSSAI 1 and 2. The AMF rejects S-NSSAI 2, indicating it is supported in TAI 2, and provides RA = (TAI1, TAI2). In the second, the UE registers in TAI 2, requesting S-NSSAI 1 and 2. The AMF accepts both and provides RA = (TAI2). + +**Figure 6.29.3.1-1: Registration with rejected S-NSSAI with indication of which TA in RA it is supported.** + +0. The UE is camping on a cell in TAI 1 where S-NSSAI1 is supported but not S-NSSAI2 +1. The UE request S-NSSAI1 and S-NSSAI2 while in TAI 1 +2. The AMF determines TAI1 does not support S-NSSAI 2 and forms the RA and detects S-NSSAI 2 is supported in TAI2 in the RA. +3. The AMF allows S-NSSAI1, rejects S-NSSAI 2 indicating it is supported in TAI2 (or, alternatively, another encoding option is indicating that it is not supported in TAI1) and a new cause code "Partially rejected in the RA" and provides RA= (TAI1, TAI2). +4. The UE now camps on TAI2 cell +5. From TAI2 cell the UE registers with S-NSSAI1 and S-NSSAI 2 +6. The AMF provides Allowed S-NSSAI = (S-NSSAI1, S-NSSAI2) and RA = TAI2 + +### 6.29.3.2 Indication to UE of Allowed NSSAI in RA and of Partially Allowed S-NSSAIs in RA with TAIs of RA where the Partially Allowed S-NSSAIs is supported. + +#### 6.29.3.2.1 Registration + +![Sequence diagram illustrating the registration process with partially allowed S-NSSAI between a UE and an AMF.](796d2e601722450d6456085e0a801e1e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + Note left of UE: 0. UE is camping in a cell in TAI 1 and requests S-NSSAI 1 and S-NSSAI 2 + UE->>AMF: 1. Registration Request (Request NSSAI (S-NSSAI1, S-NSSAI2)) + Note right of AMF: 2. AMF determines the Requested NSSAI includes S-NSSAI 2 not supported in TAI 1 but it is supported in TAI2. Includes TAI1, TAI2 in RA. + AMF->>UE: 3. Registration Acceptt (Allowed NSSAI (S-NSSAI1), [Partly Allowed S-NSSAI (S-NSSAI2), Partial RA =(TA2)] RA= (TAI1, TAI2) ) + Note left of UE: 4. UE is camping in a cell in TAI 1 and can use only S-NSSAI 1. + Note left of UE: 5. UE is camping in a cell in TAI 2 and can use S-NSSAI 1 and S-NSSAI 2. + +``` + +The diagram shows a sequence of interactions between a User Equipment (UE) and an Access and Management Function (AMF) during registration. + 1. The UE sends a Registration Request for S-NSSAI 1 and S-NSSAI 2 while in TAI 1. + 2. The AMF determines that S-NSSAI 2 is not supported in TAI 1 but is supported in TAI 2. It forms a Registration Area (RA) consisting of TAI 1 and TAI 2. + 3. The AMF sends a Registration Acceptance. S-NSSAI 1 is allowed. S-NSSAI 2 is marked as 'Partly Allowed' with a 'Partial RA' of TAI 2. The overall RA is (TAI1, TAI2). + 4. When the UE is in TAI 1, it can only use S-NSSAI 1. + 5. When the UE moves to TAI 2, it can use both S-NSSAI 1 and S-NSSAI 2. + +Sequence diagram illustrating the registration process with partially allowed S-NSSAI between a UE and an AMF. + +**Figure 6.29.3.2.1-1: Registration with partially allowed S-NSSAI** + +0. The UE is camping on a cell in TAI 1 where S-NSSAI1 is supported but not S-NSSAI2 +1. The UE request S-NSSAI1 and S-NSSAI1 while in TAI 1 +2. The AMF determines TAI1 does not support S-NSSAI 2 and forms the RA = (TAI1, TAI2) and detects S-NSSAI 2 is supported in TAI2 in the RA. +3. The AMF allows S-NSSAI1, Indicates that S-NSSAI 2 is partially allowed in RA indicating it is supported in TAI2 (or, alternatively, another encoding option is indicating that it is not supported in TAI1) and a new cause code and provides RA= (TAI1, TAI2). +4. The UE now camps on TAI1 cell and can only use S-NSSAI1 +5. The UE now camps on TAI2 cell and can use both S-NSSAI1 and S-NSSAI2. + +## 6.29.3.2.2 MO Procedure from idle mode + +![Sequence diagram of MO service request procedure from idle mode involving UE, gNB1 (TAI1), gNB2 (TAI2), AMF, and SMF/UPF.](da06747b80ea0d71593cbbd4c2ea89aa_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 (TAI1) + participant gNB2 as gNB2 (TAI2) + participant AMF + participant SMF/UPF + + Note left of UE: 0. UE is camping in a cell in TAI1 and is registered with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2 + UE->>gNB1: 1. RRC connection Establishment ((Service request for S-NSSAI2 session or for all S-NSSAIs)) + gNB1->>AMF: 2. Initial UE message(Service Request for S-NSSAI 2 or for all S-NSSAIs) + Note right of AMF: 3. AMF detect the Service request comes from TAI1 not supporting S-NSSAI2 or all S-NSSAIs so it requests RAN to immediately trigger HO to a cell supporting S-NSSAI2 or all S-NSSAIs + AMF->>gNB1: 4. Initial Context Setup Request (PDU sessions to be activated with (for PDU sessions for S-NSSAI 2) indication that these are not to be activated unless there is successful immediate HO to a TAI supporting S-NSSAI 2 also required, Allowed NSSAI = S-NSSAI1, Partially allowed S-NSSAI = S-NSSAI2 in TAI2) + gNB1->>UE: 5. RRC reconfiguration with DRB configured for S-NSSAI 2 considered not usable at UE for UL data as UE is camping in TAI1 cell + gNB1->>AMF: 6. Initial Context Setup Response(Handover for S-NSSAI 2 pending) + Note right of SMF/UPF: 7. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 1 and Delay contacting SMF for S-NSSAI2 + Note right of UE: 8. Data for S-NSSAI1 + Note left of gNB2: 9. Successful Handover to a cell in TAI2, UE now considers also the DRBs for S-NSSAI 2 usable + gNB2->>AMF: 10. Path Switch request ( HO for S-NSSAI 2 completed) + Note right of SMF/UPF: 11. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 + Note right of UE: 12. Data for PDU session for S-NSSAI 2 and if applicable continuation of data for S-NSSAI1 + +``` + +Sequence diagram of MO service request procedure from idle mode involving UE, gNB1 (TAI1), gNB2 (TAI2), AMF, and SMF/UPF. + +Figure 6.29.3.2.2-1: MO service request: success case with TAs supported by different gNBs + +Figure 6.29.3.2.2-1 s shows the service request with the UE which is registered in TAI, TAI2 with allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2. This MO SR may apply to just S-NSSAI2 PDU session(s) or all S-NSSAIs PDU Session(s). If it does apply to all S-NSSAIs, step 7 includes contacting the SMFs for s-NSSAI 1 to enable the applicable connectivity for S-NSSAI1. + +It should be noted that the AMF detects in step 3 that the S-NSSAI2 connectivity is only possible if a HO is executed to a cell supporting S-NSSAI2 so this is requested by the AMF to the RAN. if this is successful, like in this case, step 11 enables connectivity for S-NSSAI2 PDU session. + +![Sequence diagram for MO service request failure case with TAs supported by different gNBs. The diagram shows interactions between UE, gNB1 (TA1), gNB2 (TA2), AMF, and SMF/UPF. The UE sends an RRC connection establishment with a service request for S-NSSAI2. The gNB1 forwards this to the AMF. The AMF detects the request comes from TA1, which does not support S-NSSAI2, and requests a handover to a cell supporting S-NSSAI2. The gNB1 responds that a handover for S-NSSAI2 is not possible. The AMF then sends an Nsmf_PDUSession_UpdateSMContext Request/Response to the SMF/UPF for PDU sessions for S-NSSAI1 and S-NSSAI2, setting them as deactivated. Finally, data for S-NSSAI1 is sent from the SMF/UPF to the UE.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 (TA1) + participant gNB2 as gNB2 (TA2) + participant AMF + participant SMF/UPF + + Note left of UE: 0. UE is camping in a cell in TA1 and is registered with Allowed S-NSSAI1 in TA1, TA2, and partially allowed S-NSSAI2 in TA2, RA = TA1, TA2 + UE->>gNB1: 1. RRC connection Establishment ((Service request for S-NSSAI2 session or for all S-NSSAIs)) + gNB1->>AMF: 2. Initial UE message (Service Request for S-NSSAI 2 or for all S-NSSAIs) + Note right of AMF: 3. AMF detect the Service request comes from TA1 not supporting S-NSSAI2 or all S-NSSAIs so it requests RAN to immediately trigger HO to a cell supporting S-NSSAI2 or all S-NSSAIs + gNB1->>AMF: 4. Initial Context Setup Request (PDU sessions to be activated with (for PDU sessions for S-NSSAI 2) indication that these are not to be activated unless there is successful immediate HO to a TA supporting S-NSSAI 2 also required, Allowed NSSAI = S-NSSAI1, Partially allowed S-NSSAI = S-NSSAI2 in TA2) + Note left of UE: 5. RRC reconfiguration with DRB configured for S-NSSAI 2 considered not usable at UE for UL data as UE is camping in TA1 cell + gNB1->>AMF: 6. Initial Context Setup Response (Handover for S-NSSAI 2 Not possible) + Note right of SMF/UPF: 7. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI1 and S-NSSAI2, S-NSSAI2 PDU sessions set as deactivated + SMF/UPF-->>UE: 8. Data for S-NSSAI1 + +``` + +Sequence diagram for MO service request failure case with TAs supported by different gNBs. The diagram shows interactions between UE, gNB1 (TA1), gNB2 (TA2), AMF, and SMF/UPF. The UE sends an RRC connection establishment with a service request for S-NSSAI2. The gNB1 forwards this to the AMF. The AMF detects the request comes from TA1, which does not support S-NSSAI2, and requests a handover to a cell supporting S-NSSAI2. The gNB1 responds that a handover for S-NSSAI2 is not possible. The AMF then sends an Nsmf\_PDUSession\_UpdateSMContext Request/Response to the SMF/UPF for PDU sessions for S-NSSAI1 and S-NSSAI2, setting them as deactivated. Finally, data for S-NSSAI1 is sent from the SMF/UPF to the UE. + +Figure 6.29.3.2.2-2: MO service request: failure case with TAs supported by different gNBs + +Figure 6.29.3.2.2-2 shows the service request with the UE which is registered in TA1, TA2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TA2 S-NSSAI2. This may apply to just S-NSSAI2 PDU session(s) or all S-NSSAIs PDU Session(s). If it does apply to all S-NSSAIs, step 7 includes contacting the SMFs for S-NSSAI 1 to enable the applicable connectivity for S-NSSAI1 and since it was not possible to handover to a TA supporting S-NSSAI2, the PDU session for S-NSSAI2 are set as deactivated so DL data is not sent till the UE moves in connected mode to a cell supporting S-NSSAI2 (in TA2). + +![Sequence diagram for MO service request: success case with TAs supported by single gNB. The diagram shows interactions between UE, gNB (TAI1, TAI2), AMF, and SMF/UPF. The process involves RRC connection establishment, initial UE message, AMF detection and HO request, context setup, RRC reconfiguration, successful handover, context response, SMF update, and data transfer.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB as gNB (TAI1, TAI2) + participant AMF + participant SMF/UPF + + Note left of UE: 0. UE is camping in a cell in TAI1 and is registered with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2 + UE->>gNB: 1. RRC connection Establishment ((Service request for S-NSSAI2 session or for all S-NSSAIs)) + gNB->>AMF: 2. Initial UE message(Service Request for S-NSSAI 2) + Note right of AMF: 3. AMF detect the Service request comes from TAI1 not supporting S-NSSAI2 or all S-NSSAIs so it requests RAN to immediately trigger HO to a cell supporting S-NSSAI2 + gNB->>AMF: 4. Initial Context Setup Request (PDU sessions to be activated with (for PDU sessions for S-NSSAI 2) indication that these are not to be activated unless there is successful immediate HO to a TAI supporting S-NSSAI 2 also required, Allowed NSSAI = S-NSSAI1, Partially allowed S-NSSAI = S-NSSAI2 in TAI2) + Note left of gNB: 5. RRC reconfiguration with DRB configured for S-NSSAI 2 considered not usable at UE for UL data as UE is camping in TAI1 cell + Note left of gNB: 6. Successful Handover to a cell in TAI2, UE now considers also the DRBs for S-NSSAI 2 usable + gNB->>AMF: 7. Initial Context Setup Response (Mandatory Handover for S-NSSAI 2 completed) + Note right of SMF/UPF: 8. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 and S-NSSAI1 if applicable + AMF->>SMF/UPF: 9. Data for PDU session for S-NSSAI 2 and S-NSSAI1 if applicable + SMF/UPF->>UE: + +``` + +Sequence diagram for MO service request: success case with TAs supported by single gNB. The diagram shows interactions between UE, gNB (TAI1, TAI2), AMF, and SMF/UPF. The process involves RRC connection establishment, initial UE message, AMF detection and HO request, context setup, RRC reconfiguration, successful handover, context response, SMF update, and data transfer. + +**Figure 6.29.3.2.2-3: MO service request: success case with TAs supported by single gNB** + +Figure 6.29.3.2.2-3 shows the service request with the UE which is registered in TAI, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under the same gNB. This may apply to just S-NSSAI2 PDU session(s) or all s-NSSAIs PDU Session(s). If it does apply to all S-NSSAIs, step 8 includes contacting the SMFs for s-NSSAI 1 to enable the applicable connectivity for S-NSSAI1 and since it was possible to handover to TA2 supporting S-NSSAI2, SMFs for PDU sessions for S-NSSAI2 are also contacted to enable connectivity at step 8. + +## 6.29.3.2.3 MT Procedure from idle mode + +Two options are considered: + +**OPTION A:**![Sequence diagram for MT service request: success case with TAs supported by different gNBs. The diagram shows the interaction between UE, gNB1 (TAI1), gNB2 (TAI2), AMF, and SMF/UPF. The UE is initially camping in TAI1 and registered with S-NSSAI1. When MT data for S-NSSAI2 arrives at the AMF, it pages the UE via gNB1. The UE responds with an RRC connection establishment and an initial UE message (Service Request). The AMF detects the request from TAI1, which does not support S-NSSAI2, and triggers a handover to gNB2 (TAI2). The AMF sends an initial context setup request to gNB2, which includes a conditional activation of the S-NSSAI2 PDU session. The UE performs an RRC reconfiguration, and a successful handover to gNB2 occurs. The AMF then sends a path switch request to the SMF/UPF, which updates the SM context. Finally, data for S-NSSAI2 is transmitted to the UE.](691626a7032a642bb74793336c37e274_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 (TAI1) + participant gNB2 as gNB2 (TAI2) + participant AMF + participant SMF/UPF + + Note left of UE: 0. UE is camping in a cell in TAI1 and is registered with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2 + Note right of AMF: 1. MT data for S-NSSAI2 + AMF->>gNB1: 2. Paging + gNB1->>UE: 2. Paging + UE->>gNB1: 3. RRC connection Establishment () + gNB1->>AMF: 3. Initial UE message(Service Request) + Note right of AMF: 4. AMF detect the Service request comes from TAI1 not supporting S-NSSAI2 so it requests RAN to immediately trigger HO to a cell supporting S-NSSAI2 + AMF->>gNB2: 5. Initial Context Setup Request (PDU sessions to be activated with (for PDU sessions for S-NSSAI 2) indication that these are not to be activated unless there is successful immediate HO to a TAI supporting S-NSSAI 2 also required, Allowed NSSAI = S-NSSAI1, Partially allowed S-NSSAI = S-NSSAI2 in TAI2) + Note left of gNB2: 5. RRC reconfiguration with DRB configured for S-NSSAI 2 considered not usable at UE for UL data as UE is camping in TAI1 cell + gNB2->>AMF: 6. Initial Context Setup Response(Handover for S-NSSAI 2 pending) + Note right of AMF: 7. Delay contacting SMF for S-NSSAI2 + Note left of UE: 8. Successful Handover to a cell in TAI2, UE considers DRBs for S-NSSAI2 usable + gNB2->>AMF: 9. Path Switch request( HO for S-NSSAI 2 completed, Reactivate PDU sessions for S_NSSAI 2) + Note right of SMF/UPF: 10. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 + AMF->>SMF/UPF: 11. Data for S-NSSAI2 + SMF/UPF->>UE: 11. Data for S-NSSAI2 + +``` + +Sequence diagram for MT service request: success case with TAs supported by different gNBs. The diagram shows the interaction between UE, gNB1 (TAI1), gNB2 (TAI2), AMF, and SMF/UPF. The UE is initially camping in TAI1 and registered with S-NSSAI1. When MT data for S-NSSAI2 arrives at the AMF, it pages the UE via gNB1. The UE responds with an RRC connection establishment and an initial UE message (Service Request). The AMF detects the request from TAI1, which does not support S-NSSAI2, and triggers a handover to gNB2 (TAI2). The AMF sends an initial context setup request to gNB2, which includes a conditional activation of the S-NSSAI2 PDU session. The UE performs an RRC reconfiguration, and a successful handover to gNB2 occurs. The AMF then sends a path switch request to the SMF/UPF, which updates the SM context. Finally, data for S-NSSAI2 is transmitted to the UE. + +**Figure 6.29.3.2.3-1: MT service request: success case with TAs supported by different gNBs** + +Figure 6.29.3.2.3-1 shows the MT service request with the UE which is registered in RA= TAI1, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs. This DL paging applies to a PDU session for S-NSSAI2. the UE replies to paging and the AMF at step 4 detect the UE replied for TAI1 not supporting the Slice. This triggers a Initial UE context setup including indication the S-NSSAI2 PDU session is conditionally activated subject to successful Handover to a cell of a supporting TA (TA2 in this example). At step 7, the AMF delays contacting the SMFs for the PDU sessions as it has received indication that the S-NSSAI2 PDU session activation is pending handover completion. Since it was possible to handover to TA2 supporting S-NSSAI2, as detected at the AMF when it receives the confirmation at step 9, SMF for the PDU session for S-NSSAI2 is contacted to enable connectivity at step 10. The triggering data is received at step 11. Otherwise, if the gNB cannot handover to a TA supporting the S-NSSAI2, the gNB updated the AMF with a NG-AP message (not shown in the figure above as it is describing only the success case) indicating the requested HO is not possible and the AMF may trigger AN connection release. + +## OPTION B: + +![Sequence diagram for MT service request success case with TAs supported by different gNBs. Lifelines: UE, gNB1 (TAI1), gNB2 (TAI2), AMF, SMF/UPF. The sequence shows the UE reselecting from TAI1 to TAI2 to receive a paging for S-NSSAI2, then sending a service request which is successfully processed by the AMF in TAI2.](51167ecef86d85cdc6dde05a3afb74b8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 (TAI1) + participant gNB2 as gNB2 (TAI2) + participant AMF + participant SMF/UPF + + Note left of UE: 0. UE is camping in a cell in TAI1 and is registered with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2 + Note right of SMF/UPF: 1. MT data for S-NSSAI2 + AMF->>gNB1: 2. Paging(S-NSSAI2) + gNB1->>UE: 2. Paging(Band indication) + Note left of UE: 3. Attempt Cell Reselection within RA + Note left of UE: 4. RRC connection Establishment ( ) from TAI2 after reselection + UE->>AMF: 5. Initial UE message(Service Request) + Note right of AMF: 6. AMF detect the Service request comes from TAI2 supporting S-NSSAI2 + AMF->>gNB2: 7. Initial Context Setup Request ( ) + Note left of UE: 8. RRC reconfiguration with DRB configured for S-NSSAI2 + gNB2->>AMF: 9. Initial Context Setup Response ( ) + Note right of SMF/UPF: 10. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI2 + SMF/UPF->>UE: 11..Data for S-NSSAI2 + +``` + +Sequence diagram for MT service request success case with TAs supported by different gNBs. Lifelines: UE, gNB1 (TAI1), gNB2 (TAI2), AMF, SMF/UPF. The sequence shows the UE reselecting from TAI1 to TAI2 to receive a paging for S-NSSAI2, then sending a service request which is successfully processed by the AMF in TAI2. + +Figure 6.29.3.2.3-2: MT service request: success case with TAs supported by different gNBs + +Figure 6.29.3.2.3-2 shows the MT service request with the UE which is registered in RA= TAI1, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs. This DL paging applies to a PDU session for S-NSSAI2 and noticing the S-NSSAI 2 is partially allowed in the RA at step 2 the paging request includes the S-NSSAI 2. The RAN receives S-NSSAI 2 in the paging request and selects a preferred band from one of the TA2 cells bands (i.e. the preferred band for S-NSSAI2 is indicated). For paging messages sent to cells in TAI1, the gNB1 sends to the UE a paging message with the indication of the preferred band (how this is done needs to be decided by RAN2) and the UE shall trigger cell reselection to this preferred band only considering cells in the RA. Regardless of the outcome of cell reselection, the UE issues then a service request. If the cell reselection had positive outcome, like in the figure 6.29.3.2.3-2, the SR is received at the AMF and the AMF detects it is from TA2 where the S-NSSAI2 is supported. This then allows the SR to successfully complete. The triggering downlink data is received at step 11. Otherwise, if the SR is received from TAI1, the AMF may trigger AN connection release. + +## 6.29.3.2.4 Connected Mode system behaviour + +![Sequence diagram illustrating connected mode system behaviour for mobility with deactivation of S-NSSAI2 sessions upon entering TAI1.](e26bb66586e464339df27951d5c9355e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB2 as gNB2 (TAI2) + participant gNB1 as gNB1 (TAI1) + participant AMF + participant SMF as SMF(s)/UPF(s) + + Note left of UE: 0. UE is camping in a cell in TAI2 and is CM-Connected with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2. it has connected DRBs and PDU sessions for both S-NSSAIs + Note left of gNB1: 1. UE is handed over to Cell in TAI1, where S-NSSAI 2 is not supported. RRC reconfiguration places the DRBs for S-NSSAI 2 in deactivated state but the PDU session related context is kept in gNB 1 in TAI1 + gNB1->>AMF: 2 Path Switch request ( Deactivate PDU sessions for -NSSAI 2) + Note right of AMF: 3. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 indicating Deacvtivation + +``` + +The diagram shows a sequence of events during a handover from gNB2 (TAI2) to gNB1 (TAI1). + 0. The UE is initially connected in TAI2 with Allowed S-NSSAI1 and partially allowed S-NSSAI2. + 1. Upon handover to gNB1 in TAI1, where S-NSSAI2 is not supported, the RRC reconfiguration deactivates DRBs for S-NSSAI2 but keeps the PDU session context. + 2. gNB1 sends a Path Switch request to the AMF to deactivate PDU sessions for S-NSSAI2. + 3. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Request/Response to the SMF(s)/UPF(s) for S-NSSAI2, indicating deactivation. + +Sequence diagram illustrating connected mode system behaviour for mobility with deactivation of S-NSSAI2 sessions upon entering TAI1. + +**Figure 6.29.3.2.4-1: CONNECTED mobility with deactivation of S-NSSAI2 sessions upon entering TAI1 (different gNB)** + +Figure 6.29.3.2.4-1 shows mobility of UE which is CM-CONNECTED with RA= TAI, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs and where the UE has PDU sessions activated for both S-NSSAI1 and S-NSSAI2. Upon mobility to TAI1, the PDU session(s) for S-NSSAI2 are deactivated, meaning the context is preserved but the DL data is dropped and is not accounted for. the related DRBs are also reconfigured to be deactivated during the HO. The trigger for deactivation at AMF is the reception of a Path switch indicating S-NSSAI2 is now not supported (whether this is explicitly indicated, or the ULI allows the AMF to detect that, can be decided in normative phase). + +![Sequence diagram for Figure 6.29.3.2.4-2: CONNECTED mobility with reactivation of S-NSSAI2 sessions upon entering TAI2 (different gNB).](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +This sequence diagram illustrates the network interaction for connected mobility when the UE moves from TAI1 to TAI2, which are managed by different gNBs (gNB1 and gNB2 respectively). The participants are UE, gNB2 (TAI2), gNB1 (TAI1), AMF, and SMF(s)/UPF(s). The process starts with the UE camping in TAI1 and being connected with S-NSSAI1 active and S-NSSAI2 deactivated. Upon handover to gNB2 in TAI2, the RRC reconfiguration activates the DRBs for S-NSSAI2. The gNB2 then sends a Path Switch request to the AMF to reactivate the PDU sessions for S-NSSAI2. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Request/Response to the SMF(s)/UPF(s), indicating reactivation. Finally, data for the PDU session for S-NSSAI2 is forwarded from the SMF(s)/UPF(s) back to the UE. + +``` + +sequenceDiagram + participant UE + participant gNB2 as gNB2 (TAI2) + participant gNB1 as gNB1 (TAI1) + participant AMF + participant SMF as SMF(s)/UPF(s) + + Note left of UE: 0. UE is camping in a cell in TAI1 and is CM-Connected with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2. It has connected DRBs and PDU sessions for both S-NSSAIs. PDU sessions For S-NSSAI2 are deactivated + Note left of UE: 1. UE is handed over to Cell in TA2, where S-NSSAI 2 is supported. RRC reconfiguration places the DRBs for S-NSSAI 2 in activated state + gNB2->>AMF: 2. Path Switch request ( RE-activate PDUsessions for S-NSSAI 2) + AMF->>SMF: 3. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 indicating Reactivation + SMF->>UE: 4. Data for PDU session for S-NSSAI 2 + +``` + +Sequence diagram for Figure 6.29.3.2.4-2: CONNECTED mobility with reactivation of S-NSSAI2 sessions upon entering TAI2 (different gNB). + +**Figure 6.29.3.2.4-2: CONNECTED mobility with reactivation of S-NSSAI2 sessions upon entering TAI2 (different gNB)** + +Figure 6.29.3.2.4-2 shows mobility of UE which is CM-CONNECTED with RA= TAI, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs and where the UE has PDU sessions activated for S-NSSAI1 and deactivated for S-NSSAI2. Upon mobility to TAI2, the PDU session(s) for S-NSSAI2 are reactivated, meaning the context now set in SMF/UPF to enable data forwarding for the PDUs sessions for S-NSSAI2. The related DRBs are also reconfigured to be activated during the HO. The trigger for reactivation at AMF is the reception of a Path switch indicating S-NSSAI2 is now supported (whether this is explicitly indicated, or the ULI allows the AMF to detect that, can be decided in normative phase). + +![Sequence diagram for Figure 6.29.3.2.4-3: CONNECTED mobility with reactivation of S-NSSAI2 sessions upon entering TAI1 (same gNB).](6d67eee81b97a14e06a6fe57a95aff36_img.jpg) + +This sequence diagram illustrates the network interaction for connected mobility when the UE moves from TAI2 to TAI1, which are managed by the same gNB (gNB (TAI1, TAI2)). The participants are UE, gNB (TAI1, TAI2), AMF, and SMF(s)/UPF(s). The process starts with the UE camping in TAI1 and being connected with S-NSSAI1 active and S-NSSAI2 deactivated. Upon handover to the same gNB in TAI1, the RRC reconfiguration activates the DRBs for S-NSSAI2. The gNB then sends an NG-AP message to the AMF to reactivate the PDU sessions for S-NSSAI2. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Request/Response to the SMF(s)/UPF(s), indicating reactivation. Finally, data for the PDU session for S-NSSAI2 is forwarded from the SMF(s)/UPF(s) back to the UE. + +``` + +sequenceDiagram + participant UE + participant gNB as gNB (TAI1, TAI2) + participant AMF + participant SMF as SMF(s)/UPF(s) + + Note left of UE: 0. UE is camping in a cell in TAI1 and is CM-Connected with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2. It has connected DRBs and PDU sessions for both S-NSSAIs. PDU sessions For S-NSSAI2 are deactivated + Note left of UE: 1. UE is handed over to Cell in TA2, where S-NSSAI 2 is supported. RRC reconfiguration places the DRBs for S-NSSAI 2 in activated state + gNB->>AMF: 2. NG-AP message ( RE-activate PDUsessions for S-NSSAI 2) + AMF->>SMF: 3. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 indicating Reactivation + SMF->>UE: 4. Data for PDU session for S-NSSAI 2 + +``` + +Sequence diagram for Figure 6.29.3.2.4-3: CONNECTED mobility with reactivation of S-NSSAI2 sessions upon entering TAI1 (same gNB). + +**Figure 6.29.3.2.4-3: CONNECTED mobility with reactivation of S-NSSAI2 sessions upon entering TAI1 (same gNB)** + +Figure 6.29.3.2.4-3 shows mobility of UE which is CM-CONNECTED with RA= TAI1, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs and where the UE has PDU sessions activated for S-NSSAI1 and deactivated for S-NSSAI2. Upon mobility to TAI2, the PDU session(s) for S-NSSAI2 are reactivated, meaning the context now set in SMF/UPF to enable data forwarding for the PDUs sessions for S-NSSAI2. The related DRBs are also reconfigured to be activated during the HO. The trigger for reactivation at AMF is the reception of a NG-AP message indicating S-NSSAI2 is now supported (whether this is explicitly indicated, or the ULI allows the AMF to detect that, can be decided in normative phase). which NG-AP message is used is up to RAN3 to decide, but in this case a path Switch seems not sent based on current standards. + +![Sequence diagram for Figure 6.29.3.2.4-4 showing connected mobility with deactivation of S-NSSAI2 sessions upon entering TAI1 (different gNB) with no deactivation at SMF option. The diagram shows the interaction between UE, gNB2 (TAI2), gNB1 (TAI1), AMF, and SMF(s)/UPFs. The UE moves from gNB2 to gNB1. Upon entering gNB1, the PDU session for S-NSSAI2 is deactivated at the RAN, and data is dropped. The AMF is informed via a RAN Dropped data report. The SMF is not informed of the deactivation.](c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg) + +Sequence diagram illustrating the mobility process: + +- Initial State:** UE is camping in a cell in TAI2 and is CM-Connected with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2. It has connected DRBs and PDU sessions for both S-NSSAIs. +- Handover:** UE is handed over to Cell in TAI1, where S-NSSAI 2 is not supported. RRC reconfiguration places the DRBs for S-NSSAI 2 in deactivated state but the PDU session related context is kept in gNB 1 in TAI1. +- Path Switch:** gNB1 (TAI1) sends a Path Switch request to AMF. +- Data Forwarding:** AMF sends Data for PDU session for S-NSSAI 2 to gNB1 (TAI1). This step is marked with a red 'X'. +- Dropped Data:** gNB1 (TAI1) triggers reporting of dropped DL data. +- RAN Dropped Data Report:** gNB1 (TAI1) sends RAN Dropped data report (per PDU session) to AMF. +- SMF Notification:** AMF sends RAN Dropped data report (per PDU session) to SMF(s)/UPFs. + +Sequence diagram for Figure 6.29.3.2.4-4 showing connected mobility with deactivation of S-NSSAI2 sessions upon entering TAI1 (different gNB) with no deactivation at SMF option. The diagram shows the interaction between UE, gNB2 (TAI2), gNB1 (TAI1), AMF, and SMF(s)/UPFs. The UE moves from gNB2 to gNB1. Upon entering gNB1, the PDU session for S-NSSAI2 is deactivated at the RAN, and data is dropped. The AMF is informed via a RAN Dropped data report. The SMF is not informed of the deactivation. + +**Figure 6.29.3.2.4-4: CONNECTED mobility with deactivation of S-NSSAI2 sessions upon entering TAI1 (different gNB) with no deactivation at SMF option** + +Figure 6.29.3.2.4-4 shows mobility of UE which is CM-CONNECTED with RA= TAI1, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs and where the UE has PDU sessions activated for both S-NSSAI1 and S-NSSAI2. Upon mobility to TAI1, as an alternative to the approach followed in figure 6.29.3.2.4-1, the DL for the PDU session(s) for S-NSSAI2 data is dropped in the RAN. The related DRBs are also reconfigured to be deactivated during the HO. Since there is DL dropped data at the RAN, this data is accounted for so a report of the dropped data volume may need to be sent periodically and when the AN connection is released as per configuration in the RAN. this may be sent to HPLMN SMF based on roaming agreement. the advantage of this configuration is that the activation/deactivation of sessions is local event in the RAN based on the TA where the UE is. It may also be more beneficial when RRC inactive is enabled. whether this option of the one requiring end to end modification of the state of PDU sessions is pursued is subject to evaluation in this study. + +## 6.29.3.2.5 Session management + +![Sequence diagram showing PDU session establishment for S-NSSAI 2 from TAI1, where TAs are supported by different gNBs. The diagram involves UE, gNB1 (TAI1), gNB2 (TAI2), AMF, and SMF/UPF. The process starts with the UE camping in TAI1 and attempting to establish a PDU session for S-NSSAI 2. The AMF detects that TAI1 does not support S-NSSAI 2 and marks the session as deactivated. Upon mobility to TAI2, the session is reactivated.](af90aabfe3c8c65617da060d82bf99c5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 (TAI1) + participant gNB2 as gNB2 (TAI2) + participant AMF + participant SMF/UPF + + Note left of UE: 0. UE is camping in a cell in TAI1 and is registered with Allowed S-NSSAI1 in TAI1, TAI2, and partially allowed S-NSSAI2 in TAI2, RA = TAI1, TAI2 + UE->>gNB1: 1. RRC connection Establishment (NAS PDU session Establishment Request for S-NSSAI2 session ) + gNB1->>AMF: 2. Initial UE message(PDU Session Establishment Request for S-NSSAI 2 ) + Note right of AMF: 3. AMF detect the Request comes from TAI1 not supporting S-NSSAI2 do ity indicates to SMF the PDU session needs to be marked as deactivated + AMF->>SMF/UPF: 4. Nsmf_PDUSession_CreateSMContext Request/Response for PDU session for S-NSSAI 2 and indication PDU session is deactivated + AMF->>SMF/UPF: 5. Namf_Communication_N1N2MessageTransfer request/response for PDU session for S-NSSAI 2 + SMF/UPF->>gNB1: 6. PDU session resource Setup request (PDU s for S-NSSAI 2 ) + Note left of gNB1: 7. RRC reconfiguration with DRB configured for S-NSSAI 2 considered not usable at UE for UL data as UE is camping in TAI1 cell + Note right of gNB1: 8. UE upon conected mode mobility is in TA2, RAN indicates PDU session needs to be reactivated + AMF->>SMF/UPF: 8. Nsmf_PDUSession_UpdateSMContext Request/Response for PDU session for S-NSSAI 2 with indication to reactivate PDU sessions + SMF/UPF->>UE: 9. Data for S-NSSAI2 + +``` + +Sequence diagram showing PDU session establishment for S-NSSAI 2 from TAI1, where TAs are supported by different gNBs. The diagram involves UE, gNB1 (TAI1), gNB2 (TAI2), AMF, and SMF/UPF. The process starts with the UE camping in TAI1 and attempting to establish a PDU session for S-NSSAI 2. The AMF detects that TAI1 does not support S-NSSAI 2 and marks the session as deactivated. Upon mobility to TAI2, the session is reactivated. + +**Figure 6.29.3.2.5-1: PDU session Establishment for S-NSSAI 2 from TAI1, TAs supported by different gNBs** + +Figure 6.29.3.2.5-1 shows mobility of UE which is registered with RA= TAI, TAI2 with Allowed NSSAI S-NSSAI1 and Partially allowed S-NSSAI in TAI2 S-NSSAI2 where the TAI1 and TAI2 are supported by cells under different gNBs and where the UE attempts to establish a PDU session for S-NSSAI 2 while in a cell in TAI1 which does not support the S-NSSAI2. The PDU session is established but it is marked as deactivated. Upon connected mode mobility it is reactivated in step 8 when the UE moves to TAI2. + +## 6.29.3.2.6 AN Release + +During the AN release procedure, the Inactive PDU session are all marked as active so the data can be delivered to the RAN upon paging the UE. + +## 6.29.4 Impacts on services, entities and interfaces + +The following impacts are foreseen by this solution: + +UE: + +- supports registration for partially allowed S-NSSAIs in partial RAs subset of the RA. +- can determine which PDU sessions are activated or deactivated based on TAI where the UE is. +- can support partially rejected S-NSSAI + +RAN: + +- supports the intelligent activation/reactivation of PDU sessions and DRBs based on the TAI where the UE is in connected mode. +- Attempts to trigger HO to a supporting TAI when UE is using certain S-NSSAIs upon transition from Idle mode to connected mode upon SR. +- can determine which PDU sessions are activated or deactivated based on TAI where the UE is. +- depending on the chosen solution, when the AN connection is released (and periodically, if configured to do so), can issue DL dropped data volume reports per PDU session to the AMF so it can be discounted when a PDU session is deactivated +- depending on the chosen solution, can issue a NG-AP update information to AMF so the AMF detects when PDU session for a S-NSSAI are deactivated/reactivated and report this to SMF(s) + +AMF: + +- can handle the Partially allowed S-NSSAIs or the partially rejected S-NSSAIs in the RA as described above. + +SMF: + +- can handle the Activated/Deactivated sessions status, with the retention of the UE context while in deactivated status and the drop of DL data in deactivated status. Activated/Deactivated status is removed when the UE enters CM-IDLE. + +## 6.30 Solution #30: Rejected S-NSSAI with new cause value + +### 6.30.1 Introduction + +This solution aims to address the KI#5: Improved support of RAs including TAs supporting Rejected S-NSSAIs. In particular, this solution proposes new cause value for the Rejected NSSAI so the UE can differentiate the rejection cause and initiate a registration for an S-NSSAI when the UE enters a TA that is part of the RA and the TA supports this S-NSSAI. + +### 6.30.2 Functional Description + +During UE registration, the UE sends Requested NSSAI in RRC message to the RAN. The RAN selects the AMF based on the Requested NSSAI. The NSSF may further reselect a different AMF. The selected AMF may not support all S-NSSAIs in the Requested NSSAI. In previous releases, the AMF rejects the unsupported S-NSSAI with cause value "rejected for the RA" and the UE shall not request this S-NSSAI again before the UE moves outside of the RA. This solution introduces a new cause value "rejected due to AMF not support", so the UE can still request the rejected S-NSSAI in UE registration procedure without moving outside of the RA and the RAN may select a new AMF, which supports this S-NSSAI. UE may provide new UE capability indication for this feature to AMF + +- NOTE: If the AMF detects that the UE continuously triggers registration for the S-NSSAI and the AMF rejects it with cause value "rejected due to AMF not support", the AMF may use different cause value "rejected due to AMF not support" for the rejected S-NSSAI so the UE will not try again before it moves outside of the RA. + +### 6.30.3 Procedure + +During UE registration procedure, the AMF provides new cause values for the rejected S-NSSAI in the Registration Accept/Reject message to UE + +## 6.30.4 Impacts on services, entities and interfaces + +### AMF: + +- providing one new cause value "rejected due to AMF not support" for the rejected S-NSSAI + +### UE: + +- send new UE capability indication to AMF +- support handling of new cause value + +## 6.31 Solution #31: Enabling Flexible RAs with Slice Service Area + +### 6.31.1 Introduction + +This solution addresses key issue #5 as described in clause 5.5 and explains how the UE may initiate a registration for an S-NSSAI that was not allowed in a first TA of the RA but may be available in another TA of the RA. + +### 6.31.2 Functional Description + +A building block of the solution is that when the network does not allow a requested slice, the network can also provide the UE with a new information element, called Slice-Specific Service Area. The Slice-Specific Service Area information element is a list of TA(s) in the RA where the slice that was not allowed is available. The Slice-Specific Service Area information element can be provided for a requested slice that is not allowed and is not available in the current TA, but is available in some TA(s) of the RA. + +During Registration, the UE may indicate to the AMF, in the UE 5GMM Core Network Capability information element, that the UE is able to receive the Slice-Specific Service Area information element. The AMF can consider the UE's capability when forming the RA. For example, if the UE is capable of receiving the Slice-Specific Service Area information element, then the AMF may choose to include TA(s) in the RA where a slice that was not allowed is available. If the UE does not indicate that it is capable of receiving the Slice-Specific Service Area, the AMF may choose to avoid including TA(s) in the RA where a slice that was not allowed is available. + +This solution includes two options. + +- Option A reuses the existing slice rejection cause code value of "S-NSSAI not available in the current registration area". However, compared to a Rel-17 UE, the solution proposes that a UE will interpret this cause code differently if the Slice-Specific Service Area information element is provided for the rejected slice. The solution explains how the UE may request rejected S-NSSAI again only if it is in a TA of the RA where the slice is available i.e. based on Slice-Specific Service Area information. The UE can then be sent a new RA when it performs a new registration. +- Option B proposes to reuse the existing Rel-17 option to neither reject nor allow slices that are available in only some TAs of the RA. In Rel-17 it is already possible to neither allow nor reject a slice. However, in this scenario, the Rel-17 UE would not be prevented from attempting again to register to a slice that is not available in the TA. The solution proposes that if the Slice-Specific Service Area information element is provided to the UE for a slice that is not rejected or allowed, then the UE may request the not allowed S-NSSAI again only if it is in a TA of the RA where the slice is available i.e. based on Slice-Specific Service Area information. The UE can then be sent a new RA when it performs a new registration. + +### 6.31.3 Procedures + +#### 6.31.3.1 Option A - Reject Slices that are Not Available in the current TA + +In this option, the network will reject a requested slice that is not available in the UE's current TA. + +The UE sends a Registration Request and indicates in the UE 5GMM Core Network Capability information element that it supports receiving the Slice-Specific Service Area information element. + +The AMF sends a Registration Accept message to the UE. The Requested NSSAI includes slices that are not available in the current TA, thus the Registration Accept message includes Rejected S-NSSAI(s). The AMF includes TA(s) in the RA where one or more of the Rejected S-NSSAI(s) are available. The AMF also includes a Slice-Specific Service Area + +information element in the Registration Accept message for each Rejected S-NSSAI that is available in some TA(s) of the RA. + +The slice rejection cause is set to the existing cause code value of "S-NSSAI not available in the current registration area". A UE that receives this cause code and a Slice-Specific Service Area information element for the rejected S-NSSAI shall not attempt to use this S-NSSAI(s) in the current registration area unless UE's current TA is included in the Slice-Specific Service Area information element that is associated with the slice. If the UE's current TA is included in the Slice-Specific Service Area information element that is associated with the slice, then the UE may attempt to register for this S-NSSAI(s) again. + +In this option, if the AMF later wants to reject an allowed S-NSSAI, the AMF may send the UE Configuration Update command with an RA that includes TA(s) where the rejected slice is available and a Slice-Specific Service Area information element for the rejected slice. + +### 6.31.3.2 Option B - Neither Reject nor Allow Slices that are Not Available in the current TA + +In this option, the network may choose to neither allow nor reject a requested slice that is not available in the UE's current TA. + +The UE sends a Registration Request and indicates in the UE 5GMM Core Network Capability information element that it supports receiving the Slice-Specific Service Area information element. + +The AMF sends a Registration Accept message to the UE. The Requested NSSAI includes slices that are not available in the current TA, thus the Registration Accept message does not include these slices in the Allowed NSSAI. However, since the slice(s) are available in some TA(s) of the RA, the network chooses to also not include these slices in the Rejected S-NSSAIs and the AMF includes a Slice-Specific Service Area information element in the Registration Accept message for each of the slices that are only available in some TA(s) of the RA. + +When the UE receives a Slice-Specific Service Area information element, the UE shall not attempt to register for the associated S-NSSAI in the current registration area unless the UE's current TA is included in the Slice-Specific Service Area information element that is associated with the slice. The UE may then attempt to register for this S-NSSAI(s) again when it is in a TA where the slice is available (i.e. based on Slice-Specific Service Area information) and thus obtain a new RA. + +In this option, if the AMF later wants to remove a slice from the UE's Allowed NSSAI, but not reject the slice, the AMF may send the UE Configuration Update command with an RA that includes TA(s) where the slice that is no longer allowed is available and a Slice-Specific Service Area information element for that slice. + +## 6.31.4 Impacts on services, entities and interfaces + +UE: + +- Indicates support for Slice-Specific Service Area in the UE 5GMM Core Network Capability information element of the Registration Request. +- Receives the Slice-Specific Service Area information element in the Registration Accept and UE Configuration Update Command. +- Determines slice availability for registration in a TA of the RA based on the provided Slice-Specific Service Area information associated with the slice. +- Option A only: Interpretation of the "S-NSSAI not available in the current registration area" slice rejection cause is different if the UE receives the Slice-Specific Service Area information element (i.e. the UE is allowed to try to register again in a TA that is part of the slice's Slice-Specific Service Area). + +AMF: + +- Receives the Slice-Specific Service Area support indication in the UE 5GMM Core Network Capability information element of the Registration Request. +- May consider the UE's support for the feature when forming the RA. +- Sends the Slice-Specific Service Area information element in the Registration Accept and UE Configuration Update Command. + +- Option A only: Interpretation of the "S-NSSAI not available in the current registration area" slice rejection cause by the UE will be different if the UE receives the Slice-Specific Service Area information element (i.e. the UE is allowed to try to register again in a TA that is part of the slice's Slice-Specific Service Area). + +## 6.32 Solution #32: Solution for Network Control for UE Slice Use + +### 6.32.1 Description + +Operators would like to control the use of a network slice so as to optimize the performance of their network. In addition to that, there can be other reasons for a capability to enforce a certain usage of network slices, e.g. an operator may like to pull a network slice out of service for maintenance or other reasons and would like to let the UE use another network slice instead. + +Also, the operator may experience congestion in a network slice due to some unforeseen circumstance for example due to Network Slice Admission Control (NSAC) there may a need to off-load a network slice, or simply due to a large amount of other UEs using the network slice (e.g. to access higher prioritized services or the other UEs are considered to be of higher priority) and therefore the network would like to control the use of the slice so as to alleviate e.g. the congestion. + +Irrespective of the reasons, in this solution different actions are proposed depending on the level of control required by the operator. The following network initiated capabilities are proposed to be supported: + +**Action 1:** Deregistering network slices for UEs or deregistering the UEs that are registering in network slices without establishing any PDUs. + +**Action 2:** Deregistering network slices for UEs or deregistering the UEs that have PDU sessions that are not active. + +**Action 3:** Enabling PDU sessions to be transferred from one network slice to another network slice, the other network slice can be previously included in the Allowed NSSAI or will be added to the Allowed NSSAI. This action 3 applies to KI#1 as well + +The above capabilities can be applied in the context of deregistering the network slice for a limited number of UEs with progressively applying one or more of the above capabilities, as required, or applying all of the above capabilities in case of a network slice being taken out of service permanently or for a limited time (i.e. in such case the capabilities of case 3 is done first and then subsequently applying the deregistration). + +For case 1 and case 2, the AMF can deregister a UE (e.g. when the UE is only registered to one network slice) using existing procedure "network initiated deregistration" as specified in clause 4.2.2.3.3 of TS 23.502 [5] or deregistering a network slice for a UE by removing the S-NSSAI from the Allowed NSSAI using the UE Configuration Update procedure as specified in clause 4.2.4.2 of TS 23.502 [5]. The AMF monitors/acquires the needed information regarding the usage of the network slice, e.g. if no PDU Session is established for the slice according to the network policy and/or if not complying with the network policy the AMF deregisters the UE from the network slice. As stated before, the means of detecting non-compliance are out of scope as well as triggers can be initiated by other NFs such as PCF, NSACF. + +For case 3, there are several options: + +Option 1. The AMF initiates UE Configuration Update procedure towards the UE. The procedure is extended to support a PDU session transfer request from a source (network slice to be removed) network slice to a new target network slice if the AMF can locate another suitable network slice in the Allowed NSSAI or a new network slice is to be requested. If the target network slice is already in the Allowed NSSAI (before the UE Configuration Update procedure or is added to the Allowed NSSAI by the UE Configuration Update procedure, the UE then uses existing procedures to initiate a new PDU session using the target network slice for that purpose and tears down the PDU session on the source slice. If the target network slice is required to be registered by the UE, i.e. needs to be added to the Allowed NSSAI, the UE first requests the network slice by issuing a registration request and including the target network slice in the Requested NSSAI and then when the target NSSAI is in the Allowed NSSAI the UE establish PDU Session(s) using the target network slice. + +Option 2. The AMF initiates a request towards the SMF for a PDU session transfer, extending the existing service Nsmf\_PDUSession\_UpdateSM Context to support transfer of a PDU session from source slice to target slice. The SMF uses existing session management procedures extended with the necessary information to notify the UE to initiate a new PDU session towards the target slice and to tear down the old PDU sessions on the source slice. + +Option 3. The PCF initiates SM Policy Control Update Notify to SMF. The procedure is extended to include the target network slice. Then, as option 2, the SMF uses existing session management procedures with extensions to notify the UE to initiate a new PDU session towards the target slice and to tear down the old PDU sessions on the source slice. The PCF selection of UEs whose PDU sessions need to be transferred is use case dependent and relies on the existing mechanisms. In this option, the target network slice selection is per operator's policy. To ensure that selected target S-NSSAI is part of the subscribed NSSAI, the PCF selects a target NSSAI based on per NSSAI policy data received from UDR. When the target S-NSSAI is not in the cell the UE is camped on, the transfer will not take place. + +## 6.32.2 Procedures + +### 6.32.2.1 PDU session Transfer from Source Slice to Target Slice, UE Initiated approach + +In this UE Initiated approach, the UE Configuration Procedure is updated to remove in the Allowed Slice the source slice that needs to be removed. There will be a new control information element (IE) to describe the handling of PDU sessions established on a slice that is now removed from the Allowed Slices. The IE instructs the UE to transfer the PDU session from the removed network slice or to be removed network slice in Allowed NSSAI to a new target network slice in the Allowed NSSAI. The to be removed network slice can either be kept in the Allowed NSSAI for the duration of the UCU procedure and later removed, or directly removed by the UE Configuration Update command, but regarded as still allowed until the transfer to the target network slice has been completed. + +The call flow in Figure 6.32.2.1-1 illustrates the procedure depicted above. The following is a brief description of the steps in the call flow. + +The assumption in the call flow is a UE that has some PDU Sessions already established on a network slice and these PDU sessions have to be transferred to another network slice. + +- In step 1, the AMF initiates a UE Configuration Update Command, marking in (or in relation to) the Allowed NSSAI the network slice to be removed and including a new IE information to instruct the UE regarding the removed slice (or to be removed network slice) and the new target network slice that replaces it. As stated before, if the target network slice is not added by the UCU procedure to the Allowed NSSAI, the UE first requests the network slice to be registered by issuing a registration request and including the target network slice in the Requested NSSAI and then when the target NSSAI is included in the Allowed NSSAI the UE establishes PDU Session(s) using the target network slice. Note that the Figure below does not show the aspect of UE registering to request the target slice to be used. In the UE Configuration Update Command, the AMF may provide back off timer for the source S-NSSAI and/or includes the original slice in the Rejected NSSAI so that the UE cannot request a PDU Session according to the existing URSP rule until the back off timer is expired. + +**Editor's note:** It is FFS if additional information is to be included in the new IE to perform PDU Session Transfer. + +- In step 2 the UE acknowledges the reception of the Configuration Update Command. + +The remaining steps are based on existing procedures per clause 4.3.5.2 of TS 23.502 [5]. + +![Sequence diagram illustrating the UE Initiated Procedure for PDU Session Transfer. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, SMF1, and SMF2. The sequence includes: 1. UE Configuration Update Command (AMF to UE), 2. UE Configuration Update Complete (UE to AMF), 3. UE-initiated PDU Session establishment procedure (with Target S-NSSAI using UPF2) (UE to AMF), 4. UL/DL Data (AMF to UPF2), and 5. PDU Session release procedure (with Source S-NSSAI and UPF1) (AMF to SMF1).](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF1 + participant UPF2 + participant SMF1 + participant SMF2 + + Note over UE, UPF1: UL/DL Data + AMF->>UE: 1. UE Configuration Update Command + UE-->>AMF: 2. UE Configuration Update Complete + Note over UE, AMF: 3. UE-initiated PDU Session establishment procedure (with Target S-NSSAI using UPF2) + AMF->>UPF2: 4. UL/DL Data + Note over AMF, SMF1: 5. PDU Session release procedure (with Source S-NSSAI and UPF1) + +``` + +Sequence diagram illustrating the UE Initiated Procedure for PDU Session Transfer. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, SMF1, and SMF2. The sequence includes: 1. UE Configuration Update Command (AMF to UE), 2. UE Configuration Update Complete (UE to AMF), 3. UE-initiated PDU Session establishment procedure (with Target S-NSSAI using UPF2) (UE to AMF), 4. UL/DL Data (AMF to UPF2), and 5. PDU Session release procedure (with Source S-NSSAI and UPF1) (AMF to SMF1). + +Figure 6.32.2.1-1: PDU Session Transfer - UE Initiated Procedure + +## 6.32.2.2 PDU Session Transfer from Source Slice to Target Slice - Network Initiated Approach + +### 6.32.2.2.1 AMF Initiated Approach + +In this solution, the Slices in Allowed NSSAI are not changed but one of the slices for example is temporarily taken out of service and should not be used. The AMF, per operator's policy or by learning from other NFs that a slice shouldn't be used instructs the SMF used for the source network slice (i.e. network slice to not be used), to initiate a PDU Session Transfer from the source network slice to the target network slice (new network slice to be used). The Nsmf\_PDUSession\_UpdateSMContext service is extended to support such a capability e.g. the AMF indicates a Target network slice to the SMF. The SMF in turn sends a PDU Session Modification Request to the UE to initiate a PDU Session transfer. The PDU Modification Session Request can be extended to support this new capability (e.g. adding target slice and optionally source slice that otherwise could be derived from existing PDU Session, either in PCO together with existing "PDU Session Address Lifetime value" or in a new IE. The UE uses existing procedures to establish the PDU session using the new target slice and usually the same DNN and releases the old PDU sessions used with the source network slice. + +The call flow in Figure 6.32.2.2-1 illustrates the procedure depicted above. The following is a brief description of the steps in the call flow. + +The assumption in the call flow is that a UE has some PDU Sessions already established on a network slice and these PDU sessions have to be transferred to another network slice. + +- In step 1, the AMF initiates a Nsmf\_PDUSession\_UpdateSMContext Request to initiate a PDU session transfer from a source slice to a target slice. The Request is extended to support this new capability e.g. the Target network slice to the SMF and possible an indication that a transfer is to be initiated. The Request is now extended with the following optional information so that the SMF can inform the UE to perform a PDU Session transfer from source slice to a target slice: + - Source network Slice, + - Target network Slice, + - Action: Perform Session transfer for all PDU sessions immediately or at a scheduled tie time applicable to the UE location. +- In step 2, the SMF initiates action to notify the UE about a PDU session transfer from a source slice to a target slice as indicated above is extending the PDU Session Modification Request sent to the UE to include the needed information. + +- In step 3, SMF returns Nsmf\_PDUSession\_UpdateSMContext response to the AMF. +- In step 4, the SMF invokes the Namf\_Communication\_N1N2MessageTransfer to include an SM container towards the UE with a PDU Session Modification Command extended (e.g. with target S-NSSAI) to inform the UE of a PDU Session Transfer. +- In step 5 the AMF forwards the SM Container content to the UE. + +The AMF may include back off timer for the original slice and/or includes the original slice in the Rejected NSSAI to prevent the UE requesting the slice due to URSP rule re-evaluation. + +The remaining steps are based on existing procedures per clause 4.3.5.2 of TS 23.502 [5]. + +The call flow does not show the aspect of UE registering to request the target slice to be used if this step is required, when the target slice is not in the Allowed slices. + +![Sequence diagram for AMF initiated PDU Session Transfer - Session Management Procedure. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, SMF1, and SMF2. The procedure involves Nsmf_PDUSession_UpdateSMContext messages, Namf_Communication_N1N2MessageTransfer, and subsequent UE-initiated PDU Session establishment and release procedures.](034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF1 + participant UPF2 + participant SMF1 + participant SMF2 + + Note left of UE: UL/DL Data + AMF->>SMF1: 1. Nsmf_PDUSession_UpdateSMContext (Session transfer from source S-NSSAI to target S-NSSAI) + SMF1->>UPF2: 2. SMF To instruct the UE about a Session Transfer from the source slice to Target Slice + SMF1->>AMF: 3. Nsmf_PDUSession_UpdateSMContext Response + SMF1->>AMF: 4. Namf_Communication_N1N2MessageTransfer + AMF->>UE: 5a. PDU Session Modification Command (PDU Session Transfer) + UE->>AMF: 5b. PDU Session Modification Command ACK + AMF->>SMF1: 5c. Nsmf_PDUSession_UpdateSMContext Request + SMF1->>AMF: 5d. Nsmf_PDUSession_UpdateSMContext Response + Note right of SMF1: 6. UE-initiated PDU Session establishment procedure (with UPF2) + Note left of UE: UL/DL Data + Note right of SMF1: 7. PDU Session release procedure (with UPF1) + +``` + +Sequence diagram for AMF initiated PDU Session Transfer - Session Management Procedure. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, SMF1, and SMF2. The procedure involves Nsmf\_PDUSession\_UpdateSMContext messages, Namf\_Communication\_N1N2MessageTransfer, and subsequent UE-initiated PDU Session establishment and release procedures. + +**Figure 6.32.2.2.1-1: AMF initiated PDU Session Transfer - Session Management Procedure** + +*Editor's note: the impact of overriding of the SSC mode need be evaluated.* + +### 6.32.2.2.2 PCF Initiated Approach + +In this solution the PCF initiates the PDU session transfer. The flow is the same as the one described in clause 6.32.2.2.1 with the exception of Step 1. In this solution the PCF sends a Npcf\_SMPolicyControl\_UpdateNotify to initiate a PDU session transfer from a source slice to a target slice. The update notify is extended to indicate the SMF, the Target network slice and indication that a PDU transfer is to be initiated. The Update Notify message sent from the PCF is extended with the following information to enable the SMF to request the UE to perform a PDU Session transfer from source slice to a target slice: + +- Source network Slice; +- Target network Slice; +- Action: Perform Session transfer for all PDU sessions immediately or at a scheduled time applicable to the UE location. + +![Sequence diagram for PCF Initiated PDU Session Transfer - Session Management Procedure. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, SMF1, SMF2, and PCF. A dashed arrow labeled 'UL/DL Data' goes from (R)AN to UE. A solid red arrow labeled '1. Npcf_SMPolicyControl_UpdateNotify (Session transfer from source S-NSSAI to target S-NSSAI)' goes from PCF to SMF1. A horizontal bar labeled '2. Steps 2-7 of Figure 6.32.2.2.1' spans from AMF to SMF2.](6e9d059430baba0c363e33749f68b107_img.jpg) + +Sequence diagram for PCF Initiated PDU Session Transfer - Session Management Procedure. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, SMF1, SMF2, and PCF. A dashed arrow labeled 'UL/DL Data' goes from (R)AN to UE. A solid red arrow labeled '1. Npcf\_SMPolicyControl\_UpdateNotify (Session transfer from source S-NSSAI to target S-NSSAI)' goes from PCF to SMF1. A horizontal bar labeled '2. Steps 2-7 of Figure 6.32.2.2.1' spans from AMF to SMF2. + +Figure 6.32.2.2.2-1: PCF Initiated PDU Session Transfer - Session Management Procedure + +### 6.32.2.3 SSC Mode and PDU Session Transfer from Source Network Slice to Target Network Slice + +It is desirable that SSC mode 3 is employed for performing PDU session transfer from a source network slice to a target network slice. This is critically important for emergency PDU sessions and PDU sessions used for MC applications and which cannot be disconnected before completion or otherwise have to be handled with SSC mode 3. It is thus possible for either of the above solutions that the UE may receive the SSC mode 3 to be used during the PDU session transfer. This implies that the UE overrides the SSC mode currently used for the PDU session to be transferred. + +More specifically, in the UE initiated approach, the target NSSAI in the UE Configuration Update Command can indicate that the UE can apply SSC mode 3 logic for the PDU session transfer. + +For the network initiated approach, the PDU Modification Session Request can be extended to include the SSC mode 3 logic to be used for PDU session transfer. + +## 6.32.3 Impacts on Existing Nodes and Functionality + +AMF: + +- provide back off timer for the source slice so that the UE cannot request a PDU Session according to the existing URSP rule until the back off timer is expired. + +PCF: + +- Support S-NSSAI change determination. +- In case of separated PCFs (i.e. SM PCF and UE PCF), an extension of N43 to obtain UE information (e.g. allowed NSSAI). +- Support Npcf\_SMPolicyControl\_UpdateNotify extension. + +## 6.33 Solution #33: Slice-specific implicit deactivation timers + +### 6.33.1 Functional Description + +#### 6.33.1.1 Registration control + +During registration procedure, the UE indicates support for **slice-specific implicit registration deactivation timer** capability in 5GMM Core Network Capability. On receiving the Registration Request from the UE with this capability, AMF chooses a value for slice-specific implicit registration deactivation timer based on subscription and/or current load on the S-NSSAI and sets the Allowed NSSAI list along with slice specific implicit registration deactivation timer duration values for those slices that are high in demand or resource constrained. Based on subscription, different UEs may get assigned different values for the timer (e.g. premium subscribers can get assigned a longer value). + +Both the UE and AMF start the slice-specific implicit registration deactivation timer when there are no PDU sessions with active user plane resources on the slice that is associated with the implicit timer. + +When the UE establishes a PDU session with active user plane resources or activates a user plane connection for an established PDU Session, the slice-specific implicit registration deactivation timer is stopped. + +When the timer expires at UE and AMF, both UE and AMF perform Implicit Deregistration procedure locally for the slice without any explicit deregistration procedure. + +If necessary, AMF can adjust the slice-specific implicit registration deactivation timer duration using the UE Configuration Update procedure (clause 4.2.4 of TS 23.502 [5]) depending on the network resource usage/load balance. + +### 6.33.1.2 PDU session control + +During PDU session establishment procedure, the UE indicates support for **slice-specific implicit PDU session deactivation timer** capability in 5GSM Core Network Capability. On receiving the PDU Session Establishment Request from the UE with this capability, the SMF chooses a value for slice-specific implicit PDU session deactivation timer based on subscription and/or current load on the S-NSSAI and sets the slice specific implicit PDU session deactivation timer duration values for those slices that are high in demand or resource constrained. Based on subscription, different UEs may get assigned different values for the timer (e.g. premium subscribers can get assigned a longer value). + +Both the UE and SMF start the slice-specific implicit PDU session deactivation timer when the user plane connection is deactivated for the PDU session. + +When the UE activates a user plane connection for the PDU Session, the slice-specific implicit PDU session deactivation timer is stopped. + +When the timer expires at UE and SMF, both UE and SMF locally release the PDU session without any explicit PDU session release procedure. + +If necessary, SMF can adjust the slice-specific implicit PDU session deactivation timer duration via network requested PDU Session Modification procedure (clause 4.3.3.2 of TS 23.502 [5]) depending on the network resource usage/load balance. + +## 6.33.2 Procedures + +The solution relies on existing procedures defined in TS 23.502 [5]. + +## 6.33.3 Impacts on Existing Nodes and Functionality + +UE: + +- Supports slice-specific implicit registration deactivation timer. +- Supports slice-specific implicit PDU session deactivation timer. + +AMF: + +- Supports slice-specific implicit registration deactivation timer, sets value via Registration procedure, adjusts value via UE Configuration Update procedure. + +SMF: + +- Supports slice-specific implicit PDU session deactivation timer, sets value via PDU session establishment procedure, adjusts value via network requested PDU Session Modification procedure. + +# 6.34 Solution #34: On-demand slices + +## 6.34.1 Functional Description + +When the Serving PLMN configures the UE with Configured NSSAIs, the Serving PLMN may include an additional indication whether each S-NSSAI in the list of Configured NSSAI is an on-demand S-NSSAI. The Serving PLMN is aware whether a slice is resource-constrained and in that case, it configures the corresponding S-NSSAI in the UE as on-demand. + +The UE, upon receiving the list of Configured NSSAI for the Serving PLMN, will not attempt to register for any of the Configured NSSAI that are indicated as on-demand S-NSSAI. Rather, when the UE evaluates URSP rules and an on-demand S-NSSAI appears in the Route Selection Descriptor of a URSP rule, the UE will attempt to register the on-demand S-NSSAI with the AMF. If the S-NSSAI is returned among the Allowed NSSAI in the Registration Accept + +message, the UE will then further evaluate the Route Selection Descriptor of the URSP rule and establish a PDU session for the on-demand slice accordingly. This results in the UE only registering with a S-NSSAI when it needs to have connectivity to the related network slice. + +## 6.34.2 Procedures + +The solution relies on existing procedures defined in TS 23.502 [5]. + +## 6.34.3 Impacts on Existing Nodes and Functionality + +UE: + +- Registers with Configured NSSAI marked as on-demand NSSAI only when triggered by a corresponding URSP rule. + +AMF/NSSF: + +- Able to mark Configured NSSAI as on-demand NSSAI to ensure the proper utilization of slices in the system. + +# 6.35 Solution #35: Network Slice usage control by the network + +## 6.35.1 Introduction + +This solution addresses the bellow requirement from Key Issue #6: Improved network control of the UE behaviour: + +This Key Issue will study how to enable network-controlled behaviour and ensure the proper utilization of Slices in the system (e.g. what the network can request to the UE and how and what additional policies the network can provide to the UE) taking into account the above aspects (e.g. actual slice usage, UE activity, etc.). + +## 6.35.2 Functional description + +The solution allows for network slice usage control by the network. If a UE is registered for a network slice that is subject to a slice usage control and the network slice is not used by the UE for a specific time duration (e.g. no PDU Session is established on the network slice for a time duration defined by the operator via operator policy configuration), the network deregisters the UE from the network slice. The UE can still get a service on such network slice however, the UE shall register for it first as it has been removed from the Allowed NSSAI of the UE. The solution re-uses the existing NSAC service operations Nnsacf\_NumOfUEsUpdate\_Request by adding a new parameter 'slice usage control' which indicates to the NSACF that the network slice is subject to slice usage control. If a network slice is subject to slice usage control, the NSACF starts a slice usage control timer per each network slice subject to slice usage control and if the network slice is not utilised for the duration of the slice usage control timer (e.g. no PDU Session on the network slice by the UE), the UE is deregistered from the network slice. The slice usage control timers can be configured with values based on the operator policy. The slice usage control timers are re-started each time the network slice becomes not used by the UE, i.e. no established PDU session on the network slice. + +NOTE: Stage 3 may decide to define designated service operations for the network slice usage control instead re-using the existing NSAC service operation in step 2. + +### 6.35.3 Procedures + +![Sequence diagram illustrating Network Slice usage control by the network. The diagram shows interactions between UE, AMF, SMF, NSACF, and UDM. The process involves registration, slice usage control timer management, and deregistration when a slice is unused.](6348f4fc8b3848158fcfbe85e26a731d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant NSACF + participant UDM + + Note over UE, UDM: 1) UE registers for S-NSSAI-1 and S-NSSAI-2 as per the registration procedure in TS 23.502 + AMF->>NSACF: 2) Nnsacf_NSAC_NumOfUEsUpdate_Request (UE_Id, S-NSSAI-1, S-NSSAI-2, slice usage control) + Note right of NSACF: 3) If slice usage control parameter included, NSACF starts slice usage control timers for S-NSSAI-1 and S-NSSAI-2 for the UE + Note over UE, SMF: 4) PDU session establishment on S-NSSAI-1 + AMF->>NSACF: 5) Nnsacf_PDUSessionNotification (UE_Id, S-NSSAI-1, PDU_Session_Id, PDU_Session_Status) + Note right of NSACF: 6) NSACF stops the slice usage control timer for S-NSSAI-1 for the UE + Note right of NSACF: 7) The slice usage control timer for S-NSSAI-2 for the UE expires + NSACF->>AMF: 8) Nnsacf_DeregistrationNotification (UE_Id, S-NSSAI-2, cause=slice usage control timer expired) + Note over UE, AMF: 9) UCU message (S-NSSAI-2 removed from the Allowed NSSAI, cause=slice usage control timer expired). / Deregistration Request (S-NSSAI-2, cause=slice usage control timer expired) + +``` + +Sequence diagram illustrating Network Slice usage control by the network. The diagram shows interactions between UE, AMF, SMF, NSACF, and UDM. The process involves registration, slice usage control timer management, and deregistration when a slice is unused. + +**Figure 6.35.3-1: Network Slice usage control by the network** + +1. A UE registers for network slices S-NSSAI-1 and S-NSSAI-2 as per clause 4.2.2.2.2 of TS 23.502 [5]. +2. If the network slices S-NSSAI-1 and S-NSSAI-2 are subject to slice usage control, the AMF sends Nnsacf\_NSAC\_NumOfUEsUpdate\_Request message to the NSACF in which the AMF includes the network slices that are subject to slice usage control (e.g. S-NSSAI-1 and S-NSSAI-2) and a slice usage control parameter to indicate that the network slices are subject to slice usage control. +3. When the NSACF receives a request for network slice usage control from the AMF, the NSACF starts a slice usage control timer per each network slice requiring network slice usage control. The slice usage control timer value can be configured in the NSACF based on the operator policy. +4. At some stage the UE initiates a service (e.g. PDU Session) on network slice S-NSSAI-1, for example. +5. The AMF notifies the NSACF for the PDU Session establishment on S-NSSAI-1 via Nnsacf\_PDUSessionNotification where the PDU\_Session\_Status parameter indicates whether the PDU Session is established or released. +6. If network slice S-NSSAI-1 is subject to slice usage control and a slice usage control timer is running in the NSACF for the UE for S-NSSAI-1, the NSACF stops the slice usage control timer for S-NSSAI-1 as S-NSSAI-1 is being used by the UE, i.e. a PDU Session is established on the S-NSSAI-1 by the UE. The NSACF will restart the slice usage timer for S-NSSAI-1 as soon as the UE releases the PDU Session(s) on S-NSSAI-1, i.e. it becomes unused. +7. The slice usage control timer for S-NSSAI-2 for the UE expires as the UE has not used the S-NSSAI-2 for the duration of the slice usage control timer for S-NSSAI-2. +8. The NSACF sends Nnsacf\_NSAC\_DeregistrationNotification message to the AMF including UE\_Id, S-NSSAI-2 and optionally a cause which is set to slice usage control timer expired. The NSACF also updates the number of the UEs registered with the S-NSSAI-2 by decreasing the number of the registered UEs with S-NSSAI-2 by 1 and also the NSACF removes the UE identity from the list of the UEs registered with S-NSSAI-2. +9. Upon receiving the Nnsacf\_NSAC\_DeregistrationNotification message, the AMF deregisters the UE for S-NSSAI-2 via the UE Configuration Update procedure by removing the S-NSSAI-2 from the Allowed NSSAI list for the UE. Optionally, the AMF may include in the UCU message a cause parameter set to slice usage control timer expired. Alternatively, the AMF may use UE Deregistration procedure in order to remove the S-NSSAI-2 from the Allowed NSSAI for the UE. + +## 6.35.4 Impacts on services, entities and interfaces + +UE, AMF, NSACF: + +- A new slice usage control timer expired cause parameter (optional). + +AMF: + +- New slice usage control parameter in the Nnsacf\_NumOfUEsUpdate\_Request message in order to re-use it for slice usage control purpose. +- Notification towards the NSACF when a PDU Session is created and released. + +NSACF: + +- Running slice usage control timer per network slice subject to slice usage control. + +## 6.36 Solution #36: UE provided reason for registration to S-NSSAI + +### 6.36.1 Introduction + +This solution targets KI#6 on "Improved network control of the UE behaviour". Particularly the issue is that the network has to assure proper utilization of the network slices in the 5GS. + +It is assumed that the network is aware about the policies and conditions how a UE is allowed to register with the requested Network Slices. + +### 6.36.2 Functional Description + +It is proposed that during Registration procedure the UE provides assistance information associated with the S-NSSAIs of the Requested NSSAI. This solution can be used during the Registration procedure and work in addition to other solution which monitor the usage of a Network Slice after the Registration procedure. The assistance information is basically the reason for registration with the S-NSSAI. The reason for registration with the S-NSSAI can be one of the following: + +- a) The S-NSSAI is requested due to need for 'immediate use': an application in the UE requests connectivity and a matching URSP rule or UE Local Policy determined to use an S-NSSAI (e.g. as part of the URSP rule's RSD). In this sense, the UE needs the slice registration for (immediate) usage. In another example, if there are already established PDU Sessions (with active or inactive UP resources) in the S-NSSAI, the UE can use this reason for registration. +- b) The S-NSSAI is requested due to a match to 'default applications': based on local configuration, the UE is aware about the default applications and can determine the corresponding S-NSSAI (which can be identified as "always on" S-NSSAIs). For example, a voice-centric UE knows that IMS voice application is needed at any time, i.e. the IMS voice application is a default application. The corresponding S-NSSAI falls into this category. +- c) The S-NSSAI is requested due to a 'proactive registration': based on UE implementation, the UE may want to register to an S-NSSAI in order to be able to immediately establish a PDU Session in this network slice when needed at some point of time. + +The network (e.g. the AMF) may configure the UE whether to include the reason for registration with the S-NSSAI. + +When the network (e.g. AMF or NSSF) receives a reason for registration with S-NSSAI, the network determines, based on internal policies and the received reason for registration with each S-NSSAI of the Requested NSSAIs, which S-NSSAI of the Requested NSSAI are included in the Allowed NSSAI. + +The AMF can optionally include a requested S-NSSAI with reason for registration 'proactive registration' in the list of rejected S-NSSAIs with an appropriate reject cause (e.g. rejected due to 'proactive registration'). The UE may request the S-NSSAI at any time later if there is application which needs this S-NSSAI. + +Regarding the UE behaviour, if an application request data connectivity and the matching URSP rule includes an S-NSSAI which is not in the Allowed NSSAI (but also not rejected due unavailability in the PLMN, RA, or NSAC), the + +UE can first sends a request to register with the S-NSSAI before processing further RSDs or before the UE concludes that the RSD is invalid. + +### 6.36.3 Procedures + +The Figure 6.36.3-1 shows the procedure how the UE provides the reason for registration with S-NSSAI and how the AMF (or NSSF) determines the Allowed NSSAI by considering the information received from the UE and UE Subscription Data from the UDM. + +![Sequence diagram showing the procedure for UE registration with S-NSSAI. Lifelines: UE, 5G-AN, AMF/NSSF, UDM/UDR. The process involves determining the reason for registration, sending a Registration Request, executing the registration procedure, fetching subscription data, determining allowed NSSAI, and finally sending a Registration Accept/UCU.](a3f61f2e4a173b16257cd80e83d41d38_img.jpg) + +``` + +sequenceDiagram + participant UE + participant 5G-AN + participant AMF/NSSF + participant UDM/UDR + + Note left of UE: 0. NW may configure the UE whether to indicate the reason for registration with S-NSSAI + Note left of UE: 1. Determine the reason for registration with an S-NSSAI + UE->>AMF/NSSF: 2. Registration Request (..., Requested NSSAI, reason for S-NSSAI registration) + Note over UE, AMF/NSSF: 3. Registration procedure, e.g. steps 2-19 from 23.502 Figure 4.2.2.2.2-1 + AMF/NSSF-->>UDM/UDR: 4a-1. Nudm_SDM_Get Request (SUPI, ...) + UDM/UDR-->>AMF/NSSF: 4a-2. Nudm_SDM_Get Reply (SUPI, ..., Subscribed S-NSSAIs (indication „register when slice in use“)) + Note right of AMF/NSSF: 4b. AMF/NSSF determines the Allowed NSSAI by considering: +1) the reason for S-NSSAI registration from step 2; +2) S-NSSAI type as per step 4a; +3) current network situation (e.g. slice load, NSAC). + AMF/NSSF->>UE: 5. Registration Accept / UCU (..., Allowed NSSAI) + Note left of UE: 6. UE behaviour + +``` + +Sequence diagram showing the procedure for UE registration with S-NSSAI. Lifelines: UE, 5G-AN, AMF/NSSF, UDM/UDR. The process involves determining the reason for registration, sending a Registration Request, executing the registration procedure, fetching subscription data, determining allowed NSSAI, and finally sending a Registration Accept/UCU. + +**Figure 6.36.3-1: Procedure for UE registration with S-NSSAI having different reasons** + +The detailed description of the steps is provided as follows: + +0. The network (e.g. the AMF) may configure the UE whether to indicate the reason for registration with S-NSSAI. This step is shown as optional because indicating the reason for registration with S-NSSAI may be a default/mandatory behaviour and the configuration may be not needed. +1. The UE determines the reason for registration for each S-NSSAI which is to be included in the Requested NSSAI. + +The details for the reason for registration for each S-NSSAI are described in clause 6.36.2. + +2. The UE sends NAS Registration Request message. The Requested NSSAI includes information about the reason for registration for each S-NSSAI. +3. The network continues with the registration procedure, e.g. steps 2-19 from Figure 4.2.2.2.2-1 in TS 23.502 [5]. +- 4a. During the UE Subscription Data retrieval from the UDM, the AMF may receive a list of Subscribed S-NSSAIs indicating whether a UE is allowed to register with the S-NSSAI when the S-NSSAI is needed for use. +- 4b. The AMF (or the NSSF) determines the Allowed NSSAI by considering the following information: (1) the reason for S-NSSAI registration from step 1; (2) the S-NSSAI type as per step 4a; and (3) current network conditions for each S-NSSAI from the Requested NSSAI (e.g. slice load, whether the S-NSSAI is subject to NSAC for maximum number of UEs, etc.). + +For example, if due to configuration or load conditions the AMF determines to allow only S-NSSAI registrations when the S-NSSAI is to be used or already in use, the AMF includes in the Allowed NSSAI only S-NSSAIs having a reason for registration 'immediate use' or 'default applications'. When the AMF is not configured to limit the registrations for an S-NSSAI, the AMF can include the S-NSSAI in the Allowed NSSAI independent on the reason for registration sent from the UE. + +The AMF can optionally include an S-NSSAI with reason for registration 'proactive registration' in the list of rejected S-NSSAIs in order to avoid the UE to continue requesting this S-NSSAI. + +5. The AMF sends Registration Accept message to the UE including the Allowed NSSAI as determined in step 4b. +6. The UE processes the Registration Accept message as known (e.g. step 21 from Figure 4.2.2.2.2-1 in TS 23.502 [5]). + +Additionally, if an application request data connectivity and the corresponding S-NSSAI is not in the Allowed NSSAI, the UE first sends a request to register with the S-NSSAI before processing further RSDs or before the UE concludes that the RSD is invalid. + +## 6.36.4 Impacts on services, entities and interfaces + +Impacts to the UE: + +- ability to determine the reason for registration with an S-NSSAI. +- sending the reason for registration for each S-NSSAI part of the Requested NSSAI. +- receiving an S-NSSAI reject cause (e.g. rejected due to 'proactive registration'). +- triggering a registration with an S-NSSAI which is outside the Allowed NSSAI (and also not in the rejected S-NSSAIs different from rejected due to 'proactive registration') based on the URSP rules evaluation. + +Impacts to the AMF: + +- Configuring the UE whether to send the reason for registration with an S-NSSAI. +- Determining the Allowed NSSAI based on internal policies and the received reason for registration with each S-NSSAI of the Requested NSSAIs. +- Providing to the UE an S-NSSAI reject cause (e.g. rejected due to 'proactive registration'). + +## 6.37 Solution #37: Actual UE Activity-based Slice Admission Control + +### 6.37.1 Introduction + +This solution is to extend the *CN-initiated selective deactivation of UP connection of an existing PDU Session* as specified in clause 4.3.7 of TS 23.502 [5]. In case of an unreasonable inactivity, i.e. the configured timer, is detected, the SMF can release the PDU Session. Subsequently, the serving AMF can deregister a UE from a given S-NSSAI if the released PDU Session is the only PDU session that used a given S-NSSAI. + +Further optimization in terms of cutting down monitoring effort of a PDU Session inactivity or UE inactivity on a Serving SMF and Serving AMF respectively is possible if UE is supposed to be configured with policies letting a UE manage releasing inactive PDU Sessions and deregistering from an unused S-NSSAI after configured timers. Such a policy that helps a UE manage releasing an inactive PDU Session or deregistering from an unused S-NSSAI is termed "*UE behaviour control policies*". + +NOTE: It is assumed if the UE is configured with the UE behaviour control policy, when the PDU session need be released or S-NSSAI need be deregistered, the UE initiates the explicit PDU session release or registration update procedure as defined in TS 23.502 [5]. + +## 6.37.2 Functional Description + +Unless a serving AMF gets notified in terms of a UE's ability to support *UE behaviour control policies*, when UEs get successfully registered for a network slice, AMF should monitor for a configured time duration whether these UEs are making any PDU sessions using the same slice. If AMF finds that some of the UEs do not have any PDU sessions and the timer is expired, then it deregisters the slice by removing the slice from the Allowed NSSAI. If the same slice is present in the Allowed NSSAI of both 3GPP and N3GPP access and AMF finds no PDU session only for one of the access, then it deregisters the slice for the corresponding access. + +Unless a serving SMF gets notified in terms of a UE's ability to support *UE behaviour control policies*, for an already established PDU sessions, when an SMF receives an indication from UPF after a configured time duration that UE is not transferring any user plane packets and the established session is inactive then based on operator policy the SMF may release the session. SMF may give an indication to AMF while releasing the session, based on which AMF will trigger to deregister the UE from the related slice. If AMF finds out that the same UE is having active PDU sessions through other SMFs then it shall not proceed with deregistration of the slice. + +The duration where AMF monitors to define the slice inactivity and UPF monitors to define the PDU session inactivity can be configured from AF or can be configured by MNO and stored in UDM as well. These monitoring activities by a serving SMF or AMF can be restricted to the case if a UE does not support *UE behaviour control policies*. If, on the other hand, UE supports such a policy, a serving SMF or AMF having to monitor for inactivity, may not always be necessary. + +## 6.37.3 Procedures + +![Sequence diagram illustrating network controlled slice usage based on UE activity. The diagram shows interactions between UE, AMF, SMF, PSA-UPF, UDM, and AF. The sequence starts with AF providing external parameters to UDM, followed by UE registration, PDU session establishment, SMF determining session release, PDU session release, AMF determining slice deregistration, and finally UE configuration update.](2914642fbfe4ae35924bdf4beb189c1f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant PSA-UPF + participant UDM + participant AF + + Note right of AF: 1. External parameter Provision as defined in clause 4.15.6.3 + AF->>UDM: 1. External parameter Provision as defined in clause 4.15.6.3 + Note over UE, UDM: 2. UE registration as defined in clause 4.2.2.2.2 of TS23.502. + UE->>AMF: 2. UE registration as defined in clause 4.2.2.2.2 of TS23.502. + Note over UE, UDM: 3. PDU Session establishment as defined in clause 4.3.2.2 of TS23.502 + UE->>AMF: 3. PDU Session establishment as defined in clause 4.3.2.2 of TS23.502 + Note right of SMF: 4. SMF determines that the PDU session can be released. + SMF->>PSA-UPF: 4. SMF determines that the PDU session can be released. + Note over UE, SMF: 5. PDU Session Release as defined in clause 4.3.4 of TS23.502 + UE->>AMF: 5. PDU Session Release as defined in clause 4.3.4 of TS23.502 + Note right of AMF: 6. AMF determines that the Allowed S-NSSAI can be deregistered. + AMF->>SMF: 6. AMF determines that the Allowed S-NSSAI can be deregistered. + Note over UE, AMF: 7. UE configuration Update procedure as defined in clause 4.2.4.2 of TS23.502 + AMF->>UE: 7. UE configuration Update procedure as defined in clause 4.2.4.2 of TS23.502 + +``` + +Sequence diagram illustrating network controlled slice usage based on UE activity. The diagram shows interactions between UE, AMF, SMF, PSA-UPF, UDM, and AF. The sequence starts with AF providing external parameters to UDM, followed by UE registration, PDU session establishment, SMF determining session release, PDU session release, AMF determining slice deregistration, and finally UE configuration update. + +Figure 6.37.3-1: Network controlled slice usage based on UE activity + +Depending on operator policy with regard to UEs' support of for *UE behaviour control policies*, based on inactivity of the UE, the network can release the PDU session and/or remove the S-NSSAI from the Allowed NSSAI. The procedure is executed as following: + +1. The AF which uses the indicated slice provides the UE inactivity time parameter to the UDM as defined in the clause 4.15.6.2 of TS 23.502 [5]. The UE inactivity time includes two parts, i.e. the PDU session inactivity time and S-NSSAI inactivity time. + +The defined PDU session inactivity time is associated with a DNN and S-NSSAI combination pair and optional UE type (e.g. factory UE, Vehicular UE which can be identified as group of UE). It indicates exactly when a given PDU session can be released after an observed inactivity. + +The S-NSSAI inactivity time is associated with a S-NSSAI and optional UE type (e.g. factory UE, Vehicular UE which can be identified as group of UE). It defines exactly when the serving AMF can remove that S-NSSAI from the Allowed NSSAI after an observed inactivity of a UE that has registered to a given S-NSSAI but has not established any PDU session associated with that indicated S-NSSAI. + +It is also possible that the UE inactivity time is set by a mobile network operator and stored in the UDM even without any AF provisioning. + +2. A UE performs registration procedure as defined in clause 4.2.2.2.2 of TS 23.502 [5]. As part of that procedure, the serving AMF get the S-NSSAI inactivity time from the UDM. + +Once the UE has registered on a given S-NSSAI, the serving AMF gets notified whether a given UE supports *UE behaviour control policies*. + +- If the UE does not support that policy handling, the AMF will starts monitoring the S-NSSAI inactivity time. For each UE this S-NSSAI inactivity time is per each given S-NSSAI if the given S-NSSAI is in the Allowed NSSAI. +- If UE supports *UE behaviour control policies* and there is no additional configuration that requires an AMF to still keep network control in terms of dealing with UE inactivity, the serving AMF may not configure inactivity timers for those UEs and subsequently monitor those UEs for their inactiveness before deregistering them from an unused S-NSSAI. + +3. A UE performs PDU session establishment procedure as defined in clause 4.3.2.2 of TS 23.502 [5]. As part of that procedure, the serving SMF gets the PDU session inactivity time from the UDM and also whether UE supports *UE behaviour control policies*. + +If the UE does not support that policy handling, the SMF configures the indicated time value at the UPF. + +A Serving SMF will configure inactivity timer and monitor PDU Sessions belonging to those UEs in case the support for *UE behaviour control policies* is not available for those UEs. However, a serving SMF may still keep the control of having to release PDU Sessions after an inactivity has been monitored over a configured inactivity timer even for UEs that support *UE behaviour control policies*, e.g. monitoring of misbehaving UEs. + +4. When the UPF detects no traffic on the related PDU session at least over the configured PDU session inactivity time, it will report to the serving SMF. The serving SMF determines that the PDU session can be released unless this PDU session is related to MPS or Emergency service. + +5. The serving SMF triggers the PDU session release procedure as defined in clause 4.3.4 of TS 23.502 [5]. + +The serving SMF may give an indication to AMF while releasing the PDU session due to inactivity. + +6. If the serving AMF detects that no established PDU session associated with the indicated S-NSSAI over the related access type and the S-NSSAI inactivity timer (if configured at step 2) is expired, it determines that the UE's S-NSSAI can be deregistered from a given Allowed S-NSSAI for the given access type. + +For established PDU session the AMF may deregister the UE from indicated S-NSSAI if the AMF receives the PDU session release indication which is set by SMF at step 5 and the PDU session is the last PDU session associated with S-NSSAI. + +7. The serving AMF initiates the UE configuration update procedure as defined in clause 4.2.4.2 of TS 23.502 [5] to remove the indicated S-NSSAI from Allowed NSSAI of the UE. + +## 6.37.4 Impacts on services, entities and interfaces + +The following impacts are foreseen by this solution: + +### NEF: + +- A new UE inactivity time is to be provisioned to the network. + +### UDM: + +- A new UE inactivity time is to be stored and provisioned to the AMF/SMF. + +### SMF: + +- A new trigger for the PDU session release procedure is added, which can be per operator's policy and UE capability. +- Receiving the PDU session inactivity time and configuring it at the UPF. +- Providing one indication to AMF to deregister the associate slice because of inactive PDU Session. + +### AMF: + +- A new trigger for UE Configuration Update procedure is added, which can be per operator's policy and UE capability. +- For each UE monitor the S-NSSAI usage based on the received S-NSSAI inactivity time from an UDM for each given S-NSSAI, which is in the Allowed NSSAI. +- Deregistering the slice based on the Inactivity timer or indication from SMF for inactive PDU session. + +## 6.38 Solution #38: On configuring the UE with UE behaviour policies + +### 6.38.1 Introduction + +This solution addresses KI#6. + +It proposes that the UE can receive from the HPLMN and, if allowed, by the VPLMN, UE behaviour control policies which address the need to improve the degree of control the network operators can have of the UE behaviour in registering with network slices and establishing PDU sessions. + +### 6.38.2 Functional Description + +This solution requires the UE to support the handling of UE behaviour control policies received from the network. The UE can receive policies from both the VPLMN and the HPLMN. The policies are subject to HPLMN control, or, only if allowed by the HPLMN, to VPLMN control. Whether there are VPLMN-only policies or V-PLMN driven policies that require no HPLMN authorization can be studied (e.g. whether some policies can condition the UE behaviour only based on information available in the VPLMN or VPLMN decision is FFS). + +Each policy is associated to an indication of whether it is a VPLMN policy or a HPLMN policy. A Version number of the policy is also provided to the UE (a version number can apply to a VPLMN policies and one for HPLMN policy). When the UE is powered off it should be able to store the policies for the last N visited PLMNs with N based on UE implementation, if any serving VPLMN policy applies. The UE shall store the HPLMN policies in permanent memory when received and use these unless an overriding VPLMN policy is received. + +When the UE registers, it indicates to the network it supports this feature, the Version identifier of any VPLMN policies it stores and the version identifier of the HPLMN policies. Based on information the AMF receives from the UDM and based on local policy and based on checking whether the versions of the policies are up to date, the AMF decides whether and with which policies to update the UE. + +The policies that the UE can receive can indicate: + +- 1) Whether to register with all the Slices in the Configured NSSAI for the PLMN or whether to register when a PDU session needs to be established in the network slices or whether to register with a list/subset of slices from configured-NSSAI irrespective of whether a PDU session is established or not. +- 2) Whether to establish all the PDU sessions configured in the RSDs or to establish them based on the *need to use* these by applications or whether to establish PDU sessions to specific set of DNNs irrespective of whether an application needs it or not. Additional conditions for establishing a PDU session for a slice, may include time of the day or time interval of the day, and/or geographical location, and/or total duration in time for a PDU session regardless of activity. + +If the UE is configured to operate on a "need" basis, rather than on a "configuration" basis, then the UE can additionally be provided with this information: + +- 3) Time to release a PDU session after no application is detected in the UE to need to use the PDU session This time, for example, can be immediately after use is over, or the PDU session can remain Idle up to a maximum time. +- 4) Time to deregister from a network slice since the last PDU session is releases which was using the network slice. + +In addition: the URSP rules can be augmented with an indication of which RSD is mandatory to be established (which implies that the corresponding network slice must remain registered and the corresponding PDU session must remain established if possible and allowed in the serving PLMN. The URSP rule can also indicate whether an application matching a certain TD needs to be served always by the highest priority of an alternative set of RSDs which differ only for the S-NSSAI part, so as to implement the behaviour of always steering the UE to the highest priority slice among alternative slices whenever the higher priority slices are available, without compromising the connectivity to the same DNN of the same network. + +Additionally, Configured-NSSAI can be augmented with an indication which implies that the corresponding network slice must remain registered if possible and allowed in the serving PLMN. + +## 6.38.3 Procedures + +### 6.38.3.1 USIM default configuration. + +The UE behaviour policies may be preconfigured in the UE USIM and apply to all PLMNs, unless they are overridden by information configured in the control plane. The HPLMN policies apply across all PLMNs and may be updated by some VPLMN-specific policy, the HPLMN and VPLMN can configure the UE behaviour by the following procedures. + +### 6.38.3.2 Control plane procedures + +#### 6.38.3.2.1 UDM Option + +![Sequence diagram showing the registration process with UE behaviour control assistance information. The diagram involves three main entities: UE, AMF, and UDM. The process starts with the UE sending a Registration Request (step 1) to the AMF. The AMF then sends a Nudm_UECM Registration message (step 2) to the UDM. The UDM responds with Nudm_SDM_Get (step 3). The AMF then performs internal logic (step 4) to determine the configuration. The AMF sends a Registration Accept (step 5) to the UE, which includes UE behaviour control assistance information. The UE responds with a Registration Complete (ACK) (step 6). Finally, the AMF sends a Nudm_SDM_Info service (step 7) to the UDM.](ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + Note left of UE: 0. UE not yet configured or only configured in USIM + UE->>AMF: 1. Registration Request (Indication of support of "UE behaviour control" feature) + AMF->>UDM: 2. Nudm_UECM Registration (UE behaviour control support) + UDM->>AMF: 3. Nudm_SDM_Get (UE behaviour control information incl. version and whether VPLMN can update) + Note right of AMF: 4. AMF based on logic taking into account received subscription data determines the configuration to be provided to the UE + AMF->>UE: 5. Registration Accept (UE behaviour control assistance information) + UE->>AMF: 6. Registration Complete (ACK) + AMF-->>UDM: 7. Nudm_SDM_Info service + +``` + +Sequence diagram showing the registration process with UE behaviour control assistance information. The diagram involves three main entities: UE, AMF, and UDM. The process starts with the UE sending a Registration Request (step 1) to the AMF. The AMF then sends a Nudm\_UECM Registration message (step 2) to the UDM. The UDM responds with Nudm\_SDM\_Get (step 3). The AMF then performs internal logic (step 4) to determine the configuration. The AMF sends a Registration Accept (step 5) to the UE, which includes UE behaviour control assistance information. The UE responds with a Registration Complete (ACK) (step 6). Finally, the AMF sends a Nudm\_SDM\_Info service (step 7) to the UDM. + +**Figure 6.38.3.2.1-1: Registration with UE behaviour control assistance information (UE initially not yet configured)** + +In Figure 6.38.3.2.1-1 the UE is getting configured with UE behaviour control policies + +0. Starting from a state where the UE has no HPLMN nor VPLMN policies. +- 1-2. The HPLMN detects the UE can be provided with such policies based on the information it receives at step 2 during the registration of the UE. +3. If the HPLMN has any UE behaviour control policies, the HPLMN provides them to the VPLMN and also an indication that on whether the PLMN is allowed to update the policies with local policy. If the HPLMN has no policy, it may still indicate whether the VPLMN is allowed to set policies in the UE. +- 4-5. after the AMF receives the information it updates the UE in the registration accept including any applicable HPLMN and/or VPLMN policy in the registration accept alongside its version number. +- 6-7. The UE configuration with the policies is confirmed. At reception of step 6 message, the AMF stores the applicable HPLMN and the VPLMN version number of policy. Step 7 is required only if HPLMN policies were provided. + +![Sequence diagram showing the registration process with UE behaviour control assistance information. The diagram involves three main entities: UE, AMF, and UDM. The process starts with the UE already configured. The UE sends a Registration Request to the AMF. The AMF sends Nudm_UECM_Registration and Nudm_SDM_Get to the UDM. The UDM responds with UE behaviour control information. The AMF then determines the configuration based on subscription data. The AMF sends a Registration Accept to the UE. The UE responds with a Registration Complete (AC). Finally, the AMF sends a Nudm_SDM_Info service to the UDM.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + Note left of UE: 0. UE already configured + UE->>AMF: 1. Registration Request (Indication of support of "UE behaviour control" feature, Version of policy by HPLMN, version of Policy by VPLMN) + AMF->>UDM: 2. Nudm_UECM_Registration (UE behaviour control support and version of HPLMN policy) + AMF->>UDM: 3. Nudm_SDM_Get (UE behaviour control information incl. version and whether VPLMN can update) + Note right of AMF: 4. AMF based on logic taking into account received subscription data determines the configuration to be provided to the UE + AMF->>UE: 5. Registration Accept (UE behaviour control assistance information) + UE->>AMF: 6. Registration Complete (AC) + AMF-->>UDM: 7. Nudm_SDM_Info service + +``` + +Sequence diagram showing the registration process with UE behaviour control assistance information. The diagram involves three main entities: UE, AMF, and UDM. The process starts with the UE already configured. The UE sends a Registration Request to the AMF. The AMF sends Nudm\_UECM\_Registration and Nudm\_SDM\_Get to the UDM. The UDM responds with UE behaviour control information. The AMF then determines the configuration based on subscription data. The AMF sends a Registration Accept to the UE. The UE responds with a Registration Complete (AC). Finally, the AMF sends a Nudm\_SDM\_Info service to the UDM. + +**Figure 6.38.3.2.1-2: Registration with UE behaviour control assistance information (UE initially configured)** + +In Figure 6.38.3.2.1-2 the UE is getting configured with UE behaviour control policies: + +0. Starting from a state where the UE has already some HPLMN and/or VPLMN policies. +- 1-2. The HPLMN detects the UE can be provided with such policies based on the information it receives at step 2 during the registration of the UE and also the versions of the HPLMN policy the UE is configured with. +3. If the HPLMN has any new UE behaviour control policies (i.e. a new version of the policies for the UE), the HPLMN provides them to the VPLMN and also an indication that on whether the VPLMN is allowed to update the policies with local policy. If the HPLMN has no policy, it may still indicate whether the VPLMN is allowed to set policies in the UE. +- 4-5. After the AMF receives the information it updates the UE in the registration accept including any applicable HPLMN and/or VPLMN policy in the registration accept alongside its version number. +- 6-7. The UE configuration with the policies is confirmed. At reception of step 6 message, the AMF stores the applicable HPLMN and VPLMN version number of policy. Step 7 is required only if HPLMN policies were provided. + +![Sequence diagram showing the update of UE behaviour control assistance information. The diagram involves three entities: UE, AMF, and UDM. The sequence of messages is: 1. UDM provides updated policy as part of subscription data update (from UDM to AMF, dashed box); 2. AMF based on logic taking into account received subscription data determines the configuration to be provided to the UE supporting the feature (internal AMF logic); 3. UE configuration Update Command (UE behaviour control assistance information) (from AMF to UE); 4. UE Configuration Update Complete (ACK) (from UE to AMF); 5. Nudm_SDM_Info service (from AMF to UDM, dashed line).](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + Note right of AMF: 1. UDM provides updated policy as part of subscription data update + Note right of AMF: 2. AMF based on logic taking into account received subscription data determines the configuration to be provided to the UE supporting the feature + AMF->>UE: 3. UE configuration Update Command (UE behaviour control assistance information) + UE->>AMF: 4. UE Configuration Update Complete (ACK) + AMF-->>UDM: 5. Nudm_SDM_Info service + +``` + +Sequence diagram showing the update of UE behaviour control assistance information. The diagram involves three entities: UE, AMF, and UDM. The sequence of messages is: 1. UDM provides updated policy as part of subscription data update (from UDM to AMF, dashed box); 2. AMF based on logic taking into account received subscription data determines the configuration to be provided to the UE supporting the feature (internal AMF logic); 3. UE configuration Update Command (UE behaviour control assistance information) (from AMF to UE); 4. UE Configuration Update Complete (ACK) (from UE to AMF); 5. Nudm\_SDM\_Info service (from AMF to UDM, dashed line). + +**Figure 6.38.3.2.1-3: Update of UE behaviour control assistance information** + +In figure 6.38.3.2.1-3, the UE behaviour policy is updated if a new version of HPLMN or VPLMN policy is available for a capable UE that is already configured with some policy. + +1. If, the UDM detects a new version of policy is available for the UE, it updates the AMF with this updated subscription information. +- 2-3. After the AMF receives any updated UE behaviour control policies from the HPLMN in step 1, or, if it was allowed to do so by the HPLMN, it has new VPLMN policy for the UE, it updates the UE including any applicable HPLMN and/or VPLMN policy in the registration accept alongside its version number in a UE Configuration Update Command message. +- 4-5. The UE configuration with the policies is confirmed. At reception of step 4 message, the AMF stores the applicable HPLMN and VPLMN version number of UE behaviour control policy. Step 5 is required only if HPLMN policies were provided. + +#### 6.38.3.2.2 NSSF/PCF Option 2 + +In this solution UE policies applicable to Network Slice usage in a VPLMN/HPLMN are included as an additional element in the Registration Accept or UE Configuration Update Command. These policies include rules for using the network slices subject to applicable conditions to the rules. These rules are configured either in the NSSF or the PCF, and are provided to AMF for inclusion the Registration Accept or UPU procedure. Figure 6.38.3.2.2-1 depicts the procedure. + +NOTE 1 The NSSF based solution does not allow per UE policies. + +NOTE 2: In roaming case this means also querying the HPLMN NSSF /PCF to get the HPLMN policies and to check whether the VPLMN can set the policies. + +NOTE 3: This option proposes 2 sub-options but only one sub-option is expected to be selected if this sub option is selected. + +![Sequence diagram illustrating the NSSF/PCF Option for Update of UE behaviour Slice Usage policies. The diagram shows interactions between UE, vAMF, vNSSF, vPCF, and UDM. The process involves registration, policy retrieval from NSSF or PCF, validation, and enforcement of slice usage policies.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant vAMF + participant vNSSF + participant vPCF + participant UDM + + Note right of vAMF: 2. Registration Procedure steps 2-192C + Note right of vAMF: 3. Registration Procedure steps 19C- + + UE->>vAMF: 1. Registration Request (Indication of support of "UE behaviour control" feature, ) + vAMF->>vNSSF: 3. Nnssf_NNSelection_Get Request () + vNSSF-->>vAMF: 4. Nnssf_NNSelection_Get Response (Slice Usage policies) + Note left of vAMF: 5. AMF Validates UE capabilities. Policies are stored part of the UE context + vAMF-->>UE: 6. Registration Complete (Usage policies ) + Note left of UE: 7. UE applies policies + Note left of vAMF: 8. vAMF enforces policies + +``` + +Sequence diagram illustrating the NSSF/PCF Option for Update of UE behaviour Slice Usage policies. The diagram shows interactions between UE, vAMF, vNSSF, vPCF, and UDM. The process involves registration, policy retrieval from NSSF or PCF, validation, and enforcement of slice usage policies. + +**Figure 6.38.3.2.2-1: NSSF/PCF Option for Update of UE behaviour Slice Usage policies** + +The steps in the call flow are as shown below. + +1. In step 1, the UE registers in 5GS. The UE includes its capabilities to support handling and processing of network slice (and DNN/PDU Session) usage policies/rules. The UE MM Core Network Capability (i.e. in the UE 5GMM Core Network Capability) is extended to include this information. +2. In step 2 Registration procedure steps 2-19c are performed according to TS 23.502 [5] with the additional need to store the new UE capabilities. In case, the V-PCF sub-option is selected to provide the policies, the Access and mobility related policy information is extended such that AMF provides to V-PCF the Configured NSSAI and DNNs in the Npcf\_AMPolicyControl\_Create (see TS 23.502 [5] step 2 of figure 4.16.1.2-1) or the Npcf\_AMPolicyControl\_Update (see TS 23.502 [5] step 1 of figure 4.16.2.1.1-1) and the V-PCF derives the related policies and provides them in the response. V-PCF can later on update the policies in Npcf\_AMPolicyControl\_UpdateNotify (see TS 23.502 [5] step 3 of Figure 4.16.2.2-1). +3. In step 3 if the AMF is not configured for the policies for the Allowed slices (and V-PCF sub-option of step 2 is not used), the AMF sends a Nnssf\_NSSelection\_Get Request to the NSSF to either fetch Network Slice selection information and policies or just the policies applicable to usage of allowed slices (e.g. all S-NSSAIs of Configured NSSAI). The Nnssf\_NSSelection\_Get Request is extended to include the request of network slice usage policies for Allowed slices/Configured Slices. Alternatively, a new NSSF service operation is used to retrieve the policies in which case the AMF provides the applicable S-NSSAIs e.g. all S-NSSAIs of the Configured NSSAI, PLMN ID of the UE or complete UE ID (e.g. SUPI) and the related DNNs of the S-NSSAIs. +4. In step 4 the Nnssf\_NSSelection\_Get Response is extended to include this additional network slice usage policies/rules information, or a response of the new service operation. +5. In step 5, the AMF stores the received information, and checks if the UE supports the ability to store and process network slice usage policies/rules, unless that was done before in step 2 or before step 3. +6. In step 6 assuming UE supports the policies, the AMF includes this information in the Registration Accept response to the UE. +7. In step 7, the UE applies the received network slice rules/policies. +8. In step 8 the AMF enforces the policies. The AMF action in case of policy violation could be based on policy but is out of scope. + +If the network wants to update the policies, the AMF provides the updated policies to the UE using UE Configuration Update Command (see Figure 4.2.4.2-1 in TS 23.502 [5]). + +The above procedure is performed in the visited network. + +### 6.38.3.3 URSP possible impact + +Separately from the generic UE behaviour control provided by the UE behaviour control policies by HPLMN and VPLMN, it should be possible via the URSPs to control additional aspects of UE behaviour. The URSP can be augmented with information indicating whether certain RSD S-NSSAI registration is mandatory or whether certain RSD DNN+S-NSSAI PDU session establishment is mandatory. + +Also, if the RSDs matching a TD share the DNN but have different priority order due to respective S-NSSAIs, the related PDU connection can be used interchangeably to serve the application in priority order. If an indication is provided to the UE to do so in the URSP, meaning that the UE is indicated explicitly to always attempt use the highest priority S-NSSAI RSD even if one RSD related to a lower Priority S-NSSAI is already being used and the higher priority RSD slice is not yet allowed. + +### 6.38.4 Impacts on services, entities and interfaces + +The following impacts are foreseen by this solution: + +UE: + +- Supports the processing of the UE behaviour control policies. +- Can receive configuration from the AMF and store it for the VPLMN and HPLMN. +- Reports the version number of policies and indicates support of the feature. + +AMF UDM Option 1: + +- Can handle UE behaviour control policies and the indications of support from UE. can store the policy versions and confirm to HPLMN the configuration of policies received from HPLMN. + +PCF-UDM Option 1: + +- Can provide URSP including additional indications to control UE behaviour. + +AMF - NSSF/PCF Option 2: + +- Can handle UE behaviour control policies and the indications of support from UE. Can handle policies according to either PCF or NSSF option. Enforces received policies + +PCF - NSSF/PCF Option 2: + +- If the PCF sub-option of option 2 is supported then then PCF provides the UE usage policies to the AMF with impacts to Npcf\_AMPolicyControl\_Create, Npcf\_AMPolicyControl\_Update, and Npcf\_AMPolicyControl\_UpdateNotify. + +NSSF-NSSF/PCF Option 2: + +- If the NSSF sub-option of option 2 is supported then then NSSF provides the UE usage policies to the AMF with impacts to Nnssf\_NSSelection\_Get Request or a new Request. + +UDM - UDM Option 1: + +- Can detect support of the UE behaviour control policies support by the UE and if so provide related information to the AMF as indicated. if the AMF is belonging to a VPLMN it may indicated whether the AMF in VPLMN can generate local policies. + +Nudm\_UECM\_Registration - UDM Option: + +- Input to optionally include "UE behaviour control support" and "version of HPLMN UE behaviour control policy". + +Nudm\_SDM\_Get - UDM Option: + +- Output to optionally include UE behaviour control policy incl. version and whether VPLMN can update. + +## 6.39 Solution #39: Serving PLMN steering UE to preferred slice for selection of PDU session + +### 6.39.1 Description + +UE use preconfigured or network provided URSP to select any particular slice while initiating any PDU session with network. But the Rel17 NSAC feature increase the probability for the UE's PDU session to get rejected if the quota for the concurrent established PDU session for the given slice is about to exhaust. Hence there is a need for serving network to steer to some other preferred slice by updating the URSP and sending to those UEs. + +The following are the main principles of the solution: + +- PCF will subscribe using the Nnsacf\_SliceEventExposure\_Subscribe service operation with NSACF to the event 'the number of PDU Sessions established on a network slice' and the threshold can be set as per the configuration. PCF will NSACF discovery as in clause 6.3.22 of TS 23.501 [2]. +- NSACF will notify to the PCF. +- PCF will derive the list of UEs for which the slice is applicable. Then PCF will update the URSP by replacing that slice or lowering the precedence of that slice with some other preferred slice for the DNN/Application and send to UEs. In case of replacement, the PCF can select one available slice from at least one of Allowed NSSAI, subscribed S-NSSAI and/or Configured NSSAI and replace the exhausted slice with the selected slice. + +![Downward arrow indicating modification](1c051a3d61003bc7d513e03015245317_img.jpg) + +| URSP rules before PCF modification | | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rule Precedence =1
Traffic Descriptor: Application descriptor=App1 | Route Selection Descriptor Precedence=1
Network Slice Selection: S-NSSAI-a
SSC Mode Selection: SSC Mode 3
DNN Selection: internet
Access Type preference: 3GPP access | +| Rule Precedence =2
Traffic Descriptor: Application descriptor=App1 | Route Selection Descriptor Precedence=1
Network Slice Selection: S-NSSAI-b
DNN Selection: internet
Access Type preference: Non-3GPP access | + +| URSP rules after PCF modification | | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rule Precedence =1
Traffic Descriptor: Application descriptor=App1 | Route Selection Descriptor Precedence=1
Network Slice Selection: S-NSSAI-c
SSC Mode Selection: SSC Mode 3
DNN Selection: internet
Access Type preference: 3GPP access | +| Rule Precedence =2
Traffic Descriptor: Application descriptor=App1 | Route Selection Descriptor Precedence=1
Network Slice Selection: S-NSSAI-b
DNN Selection: internet
Access Type preference: Non-3GPP access | + +Downward arrow indicating modification + +Figure 6.39.1-1: Example of URSP rule modification + +## 6.39.2 Procedures + +![Sequence diagram illustrating the PCF steering to a preferred slice procedure. The diagram shows four lifelines: UE, AMF, PCF, and NSACF. The sequence of steps is: 1. UE is already registered as per clause 4.2.2.2.2 of TS 23.502; 2. UE has preconfigured URSP or been updated with network provided URSP; 3. PCF sends Nnsacf_SliceEventExposureSubscribe to NSACF; 4. NSACF sends Nnsacf_SliceEventExposure_Notify to PCF; 5. PCF updates URSP to UE as per clause 4.2.4.3 of TS 23.502.](649f424fd35ea31f622163506a6148ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF + participant NSACF + Note left of UE: 1. UE is already registered as per clause 4.2.2.2.2 of TS 23.502 + Note left of UE: 2. UE has preconfigured URSP or been updated with network provided URSP + PCF->>NSACF: 3. Nnsacf_SliceEventExposureSubscribe + NSACF-->>PCF: 4. Nnsacf_SliceEventExposure_Notify + Note left of UE: 5. PCF updates URSP to UE as per clause 4.2.4.3 of TS 23.502 + +``` + +Sequence diagram illustrating the PCF steering to a preferred slice procedure. The diagram shows four lifelines: UE, AMF, PCF, and NSACF. The sequence of steps is: 1. UE is already registered as per clause 4.2.2.2.2 of TS 23.502; 2. UE has preconfigured URSP or been updated with network provided URSP; 3. PCF sends Nnsacf\_SliceEventExposureSubscribe to NSACF; 4. NSACF sends Nnsacf\_SliceEventExposure\_Notify to PCF; 5. PCF updates URSP to UE as per clause 4.2.4.3 of TS 23.502. + +**Figure 6.39.2-1: PCF steering to a preferred slice** + +The detailed procedure is described in Figure 6.39.2-1. + +1. The UE registers to 5GC as in clause 4.2.2.2.2 of TS 23.502 [5]. +2. The UE has preconfigured URSP or been updated with network provided URSP. +3. PCF subscribe to the event "the number of PDU Sessions established on a network slice" by sending Nnsacf\_SliceEventExposureSubscribe to the NSACF as in clause 5.2.21.4.2 of TS 23.502 [5] and PCF will set the threshold as per the configuration. +4. NSACF will notify when the event is occurred using Nnsacf\_SliceEventExposure\_Notify service operation as in clause 5.2.21.4.4 of TS 23.502 [5] +5. PCF will update the URSP rules either by replacing the slice or lowering the precedence of the slice for which quota has been exceeded the threshold with a preferred slice and send to the UE as in clause 4.2.4.3 of TS 23.502 [5]. + +**Editor's note:** How the URSP will be updated in VPLMN is FFS. + +## 6.39.3 Impacts on Existing Nodes and Functionality + +This solution may have the following impacts to existing entities and interfaces: + +PCF: + +- PCF will use Slice Event exposure service offered by NSACF to steer to UE with a preferred slice by replacing the slice which has been exhausted the threshold. + +# 6.40 Solution #40: S-NSSAI change decided by PCF + +## 6.40.1 Introduction + +This solution aims to address the scenario 1b) and 1c) in the Key Issue #1: Support of network slice service continuity. + +Scenario 1b): network slice or network slice instance is overloaded or undergoing planned maintenance in CN (e.g. network slice termination). + +Scenario 1c): network performance of the network slice cannot meet the SLA. + +On scenario 1b), it could be a SMF or a NWDAF finds the related network slice or network slice instance is overloaded or receives a maintenance command about a network slice termination. + +## 6.40.2 Functional Description + +This solution proposes the PCF to determine whether the S-NSSAI associated to an ongoing PDU session needs to be changed and which one is the replacement, triggered by a SMF or NWDAF. After determination, the PCF provides the suggested new S-NSSAI to the SMF, and the SMF initiates the modification of the PDU session and notifies the AMF. + +The corresponding procedures are per PDU session granularity and related to session management. + +## 6.40.3 Procedures + +### 6.40.3.1 The S-NSSAI change determination by PCF for an ongoing PDU session on non-roaming and local breakout roaming scenario + +![Sequence diagram illustrating the S-NSSAI change determination process. Lifelines: UE, (R)AN, AMF, UPF1, UPF2, SMF1, SMF2, PCF, NEF, NWDAF, AF. The process starts with SMF1 sending an Npcf_SMPolicyControl_Update to PCF. PCF receives notifications from NWDAF (Nnwdaf_AnalyticsSubscription_Notify) and AF (Nnef_ParameterProvision_Update_Req) via NEF. PCF determines the S-NSSAI change and notifies SMF1. SMF1 determines if UPF/SMF relocation is needed. AMF sends Nsmf_PDUSession_SMContextStatus Notify Request to SMF1. SMF1 sends Namf_Communication_N1N2MessageTransfer to AMF. AMF sends PDU Session Modification Command to UE. Finally, a box indicates steps 1 to 6 are as per figure 4.3.5.2-1 in subclause 4.3.5.2, TS 23.502.](43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF1 + participant UPF2 + participant SMF1 + participant SMF2 + participant PCF + participant NEF + participant NWDAF + participant AF + + Note right of SMF1: 1a. Npcf_SMPolicyControl_Update + SMF1->>PCF: 1a. Npcf_SMPolicyControl_Update + Note right of NWDAF: 1b. Nnwdaf_AnalyticsSubscription_Notify + NWDAF-->>PCF: 1b. Nnwdaf_AnalyticsSubscription_Notify + Note right of AF: 1c. Nnef_ParameterProvision_Update_Req + AF->>NEF: 1c. Nnef_ParameterProvision_Update_Req + NEF->>PCF: 1c. Nnef_ParameterProvision_Update_Req + Note right of PCF: 2c. Npcf_PolicyAuthorization_Update_Req + PCF->>NEF: 2c. Npcf_PolicyAuthorization_Update_Req + Note right of NEF: 3. PCF determines S-NSSAI change + NEF-->>PCF: + Note right of PCF: 4. Npcf_SMPolicyControl_UpdateNotify request(new S-NSSAI) + PCF->>SMF1: 4. Npcf_SMPolicyControl_UpdateNotify request(new S-NSSAI) + Note right of SMF1: 5. Npcf_SMPolicyControl_UpdateNotify response + SMF1-->>PCF: 5. Npcf_SMPolicyControl_UpdateNotify response + Note right of SMF1: 6. SMF determines whether UPF/SMF Relocation needs to be performed. + SMF1->>AMF: 7a. Nsmf_PDUSession_SMContextStatus Notify Request(new S-NSSAI) + AMF->>SMF1: 8a. Namf_Communication_N1N2MessageTransfer + Note right of AMF: 9a. PDU Session Modification Command (new S-NSSAI) + AMF->>UE: 9a. PDU Session Modification Command (new S-NSSAI) + Note right of UE: 7b. Steps 1 to 6 as figure 4.3.5.2-1 in subclause 4.3.5.2, TS 23.502 + +``` + +Sequence diagram illustrating the S-NSSAI change determination process. Lifelines: UE, (R)AN, AMF, UPF1, UPF2, SMF1, SMF2, PCF, NEF, NWDAF, AF. The process starts with SMF1 sending an Npcf\_SMPolicyControl\_Update to PCF. PCF receives notifications from NWDAF (Nnwdaf\_AnalyticsSubscription\_Notify) and AF (Nnef\_ParameterProvision\_Update\_Req) via NEF. PCF determines the S-NSSAI change and notifies SMF1. SMF1 determines if UPF/SMF relocation is needed. AMF sends Nsmf\_PDUSession\_SMContextStatus Notify Request to SMF1. SMF1 sends Namf\_Communication\_N1N2MessageTransfer to AMF. AMF sends PDU Session Modification Command to UE. Finally, a box indicates steps 1 to 6 are as per figure 4.3.5.2-1 in subclause 4.3.5.2, TS 23.502. + +**Figure 6.40.3.1-1: The S-NSSAI change determination for a ongoing PDU session triggered by an SMF report** + +1a. From SMF1 to PCF: The SMF1 invokes Npcf\_SMPolicyControl\_Update service to send the information on the policy control request trigger condition that has been met. The policy control request trigger condition contains network slice or network slice instance overloaded or undergoing planned maintenance. Npcf\_SMPolicyControl\_Update request contains the information the S-NSSAI associated to the PDU session is overloaded or undergoing planned maintenance. + +1b. From NWDAF to PCF: The NDWAF invokes Nnwdaf\_AnalyticsSubscription\_Notify service operation to notify the PCF that the S-NSSAI associated to the PDU session is overloaded or undergoing planned maintenance. + +In local breakout roaming cases, all the NFs in this procedure are from visited network and the S-NSSAI included in the information from V-SMF1 to V-PCF is an S-NSSAI in VPLMN. + +1c. From AF to PCF: AF is notified that the QoS performance of the UE is changed, e.g. because the resource of the current S-NSSAI becomes congested. AF sends Nnef\_ParameterProvision\_Update request, including GPSI and QoE improvement indication, which reflects the requirement of application services, to the NEF. + +- 2c. From NEF to PCF: ENF sends Npcf\_PolicyAuthorization\_Update request, including GPSI and QoE improvement indication to the PCF. + +3. The PCF determines the new S-NSSAI of the PDU session within the allowed NSSAI. + +The PCF makes the determination based on the information related to the SM policy, the network slice SLA and the UE (e.g. UE policy and the allowed NSSAI of the UE.). The allowed NSSAI can be obtained from AMF according to TS 23.503 [12] clause 6.1.2.5. If the PCF for the PDU session and the PCF for the UE are deployed separately, the former gets the information related to the UE via the N43 reference point. + +In local breakout roaming case, the allowed NSSAI is the allowed NSSAI of VPLMN. + +If no new S-NSSAI can be selected within the allowed NSSAI for the PDU session, the PCF rejects the requests of changing the PDU session in step 1. + +4. From PCF to SMF: updated Policy information for the PDU Session and new S-NSSAI. + +The PCF performs a PCF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.2 to notify SMF about the modification. Npcf\_SMPolicyControl\_UpdateNotify request contains the new S-NSSAI. In local breakout roaming case, V-PCF provides V-SMF1 the new S-NSSAI of VPLMN. + +5. From SMF to PCF: The SMF acknowledges the PCF request with a Npcf\_SMPolicyControl\_UpdateNotify response. + +6. The SMF1 determines whether UPF/SMF Relocation needs to be performed. + +The SMF1 makes the determination upon the capabilities of itself and the associated UPF. If UPF/SMF Relocation needs not to be performed, step 6a/7a/8a applies; while if UPF/SMF Relocation needs to be performed, step 6b applies. + +- 7a. From the SMF1 to AMF: SMF1 notifies the AMF the network slice associated to the PDU session is changed to the new S-NSSAI. + +- 8a. From the SMF1 to AMF: SMF1 invokes Namf\_Communication\_N1N2MessageTransfer including N1/N2 SM message. + +- 9a. From the AMF to UE: AMF transports PDU Session Modification Command transparently to the UE. PDU Session Modification Command contains the new S-NSSAI. In home routed roaming case, the new HPLMN S-NSSAI is included. + +The UE replace the S-NSSAI associated to the PDU session. + +- 7b. Steps 1 to 6 as in Figure 4.3.5.2-1 in clause 4.3.5.2 of TS 23.502 [5] are performed. + +In step 1a, SMF1 notifies the AMF the network slice associated to the PDU session is changed to the new S-NSSAI. + +In step 3a, the new S-NSSAI is included in the PDU Session Modification Command. + +In step 4, the UE initiate the PDU Session Establishment procedure described in clause 4.3.2.2 of TS 23.502 [5], to the new S-NSSAI. + +### 6.40.3.2 The S-NSSAI change determination by PCF for an ongoing PDU session triggered by an SMF report on home-routed roaming cases + +![Sequence diagram illustrating the S-NSSAI change determination by PCF for an ongoing PDU session on home-routed roaming cases. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, V-SMF1, V-SMF2, H-SMF1, H-SMF2, H-PCF, and NWDAF. The process involves policy control updates, analytics subscription notifications, and determination of UPF/SMF relocation needs at both HPLMN and VPLMN.](37104233d1b6d7728427e833816594dc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF1 + participant UPF2 + participant VSMF1 as V-SMF1 + participant VSMF2 as V-SMF2 + participant HSMF1 as H-SMF1 + participant HSMF2 as H-SMF2 + participant HPCF as H-PCF + participant NWDAF + + Note right of HSMF1: 1a. Npcf_SMPolicyControl_Update + HSMF1->>HPCF: 1a. Npcf_SMPolicyControl_Update + Note right of VSMF1: 1b. Nsmf_PDUSession_StatusNotify + VSMF1->>HSMF1: 1b. Nsmf_PDUSession_StatusNotify + Note right of HSMF1: 1b. Npcf_SMPolicyControl_Update + HSMF1->>HPCF: 1b. Npcf_SMPolicyControl_Update + Note right of HPCF: 1c. Nnwdaf_AnalyticsSubscription_Notify + HPCF-->>NWDAF: 1c. Nnwdaf_AnalyticsSubscription_Notify + Note right of HPCF: 2. PCF determines S-NSSAI change + Note right of HPCF: 3. Npcf_SMPolicyControl_UpdateNotify request(new S-NSSAI) + HPCF->>HSMF1: 3. Npcf_SMPolicyControl_UpdateNotify request(new S-NSSAI) + Note right of HSMF1: 4. Npcf_SMPolicyControl_UpdateNotify response + HSMF1->>HPCF: 4. Npcf_SMPolicyControl_UpdateNotify response + Note right of HSMF1: 5. H-SMF Determines whether UPF/SMF Relocation needs to be performed at HPLMN + Note right of HSMF1: 6. Nsmf_PDUSession_Update (new S-NSSAI, SMF/UPF relocation indication) + HSMF1->>VSMF1: 6. Nsmf_PDUSession_Update (new S-NSSAI, SMF/UPF relocation indication) + Note right of VSMF1: 7. V-SMF Determines whether UPF/SMF Relocation needs to be performed at VPLMN + Note right of VSMF1: 8a. Steps 6a to 8a in subclause 6.40.3.1 with the mapped S-NSSAI of VPLMN + Note right of VSMF1: 8b. Steps 1 to 6 as figure 4.3.5.2-1 in subclause 4.3.5.2, TS 23.502 with the mapped S-NSSAI of VPLMN + +``` + +Sequence diagram illustrating the S-NSSAI change determination by PCF for an ongoing PDU session on home-routed roaming cases. The diagram shows interactions between UE, (R)AN, AMF, UPF1, UPF2, V-SMF1, V-SMF2, H-SMF1, H-SMF2, H-PCF, and NWDAF. The process involves policy control updates, analytics subscription notifications, and determination of UPF/SMF relocation needs at both HPLMN and VPLMN. + +**Figure 6.40.3.2-1: The S-NSSAI change determination by PCF for an ongoing PDU session on home-routed roaming cases** + +1a. This step is the same with step 1a in clause 6.40.3.1. + +1b. The V-SMF1 invokes *Nsmf\_PDUSession\_StatusNotify* service operation to notify H-SMF1 the policy control request trigger condition has been met. H-SMF subsequently invokes *Npcf\_SMPolicyControl\_Update* service to H-PCF for policy control. *Npcf\_SMPolicyControl\_Update* request contains the information the HPLMN S-NSSAI associated to the PDU session is overloaded or undergoing planned maintenance. + +1c. This step is the same with step 1b in clause 6.40.3.1. + +In home-routed roaming case, H-SMF1 reports the network slice instance overloaded or undergoing planned maintenance to H-PCF, and the S-NSSAI included in the information is an S-NSSAI in HPLMN. + +2. The H-PCF determines the new S-NSSAI of the PDU session within the allowed NSSAI. + +The H-PCF makes the determination based on the information related to the SM policy, the network slice SLA and the UE (e.g. UE policy and the allowed NSSAI of the UE). If the PCF for the PDU session and the PCF for the UE are deployed separately, the former gets the information related to the UE via the N43 reference point. + +In home-routed roaming case, the allowed NSSAI is queried from V-PCF by H-PCF via N24. If no new S-NSSAI can be selected within the allowed NSSAI for the PDU session, the PCF rejects the requests of changing the PDU session in step 1. + +3. From PCF to SMF: updated Policy information for the PDU Session and new S-NSSAI. + +The PCF performs a PCF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.2 to notify SMF about the modification. Npcf\_SMPolicyControl\_UpdateNotify request contains the new S-NSSAI. In home-routed roaming case, H-PCF provides H-SMF1 the new S-NSSAI of HPLMN. + +4. From SMF to PCF: The H-SMF acknowledges the PCF request with Npcf\_SMPolicyControl\_UpdateNotify response. + 5. The H-SMF1 determines whether UPF/SMF Relocation needs to be performed at HPLMN based on the capabilities of itself and the associated UPF. + 6. H-SMF1 invokes Nsmf\_PDUSession\_Update to indicate the S-NSSAI associated to the PDU session is changed and send the new S-NSSAI to V-SMF1. If UPF/SMF Relocation is needed in step 5, the indication of UPF/SMF Relocation is also included. + 7. The V-SMF1 determines whether UPF/SMF Relocation needs to be performed at VPLMN based on the capabilities of itself and the associated UPF. +- 8a. If the UPF/SMF Relocation is not needed, step 6a to 8a in clause 6.40.3.1 applies. +- 8b. If the UPF/SMF Relocation is needed, Steps 1 to 6 as in Figure 4.3.5.2-1 in clause 4.3.5.2 of TS 23.502 [5] are performed. + +## 6.40.4 Impacts on services, entities and interfaces + +### PCF: + +- Support S-NSSAI change determination based on AF request or SMF report. +- (optional) N43 extended to get information of the UE(e.g. UE policy, the allowed NSSAI). +- Support Npcf\_SMPolicyControl service extension. +- H-PCF supports query of Allowed NSSAI from V-PCF via N24. + +### SMF: + +- Support notifying the AMF and UE the S-NSSAI change. +- Support Nsmf\_PDUSession service and PDU Session Modification Command extension. +- Support Nsmf\_PDUSession\_Update extension to support indicating the S-NSSAI associated to the PDU session is changed, the new S-NSSAI and the indication of UPF/SMF Relocation. + +### AMF: + +- Support Nsmf\_PDUSession service extension. + +### UE: + +- Support PDU Session Modification Command extension. + +### N7/Npcf\_SMPolicyControl service: + +- Add a new policy control request trigger condition(i.e. network slice or network slice instance overloaded or undergoing planned maintenance). +- Add the new S-NSSAI in UpdateNotify service operation. + +### N11/Nsmf\_PDUSession service: + +- Add the new S-NSSAI in SMContextStatusNotify service operation. + +### N1/PDU Session Modification Command: + +- Add the new S-NSSAI. + +## 6.41 Solution #41: Network Slice change without service interruption + +### 6.41.1 Introduction + +The solution addresses the Key Issue #1: Support of network slice service continuity. + +### 6.41.2 Functional Description + +The solution provides a mechanism to determine the need to change a network slice, and to allow a change of network slice while maintaining the PDU Sessions. + +The AMF determines that a PDU Session allows a change of S-NSSAI by: + +- UE indicates the support for the capability. +- SMF indicates the additionally supported S-NSSAIs and the capability to change S-NSSAI. + +The scenarios supported by this solution are 1b, 1c, 2d. + +NOTE: whether there is a need for any new S-NSSAI when same SMF/UPF is used and address is preserved is unclear as repartitioning may also work like done in the RAN for similar issue. + +### 6.41.3 Procedures + +#### 6.41.3.1 General + +For 1b, 1c, 2d, the AMF determines that there is a need to change S-NSSAI. For scenario 1b and 2d this is determined by information from OAM, including the case that resource re-partitioning cannot be done as to enable the existing S-NSSAI to be maintained. For scenario 1c, this is determined by NWDAF. + +The AMF determines the new S-NSSAI to use e.g. by NSSF, by PCF (as in solution #2) or by OAM. + +The principles for the change of S-NSSAI for the above scenarios are as follows: + +- AMF determines that a S-NSSAI need to be changed as per above logic. +- AMF determines the S-NSSAI to use, and if SMF (PSA) supports the new S-NSSAI and the capability to change S-NSSAI, then AMF requests SMF to change to the new S-NSSAI, and initiate procedure towards the UE that the S-NSSAI has been changed. +- If the SMF (PSA) does not support the new S-NSSAI and/or the capability to change S-NSSAI then AMF invokes procedure to initiate PDU Session transfer using any SSC mode as described by other solutions. + +If it is not possible to change to a new S-NSSAI without changing SMF, then AMF invokes procedure to initiate PDU Session transfer using any SSC mode as described by other solutions. + +#### 6.41.3.2 Change of network slice + +**Network Slice change for scenarios 1b, 1c, 2d.** + +![Sequence diagram illustrating Network Slice change while maintaining the PDU Session. The diagram shows five entities: UE, RAN, AMF, SMF/UPF, and PCF. The sequence of messages is: 1. AMF determines S-NSSAI need to be changed and the new S-NSSAI; 2. AMF requests SMF to change to the new S-NSSAI; 3. AMF informs UE that S-NSSAI has been changed and/or that the UE needs to establish a new PDU Session for the new S-NSSAI; 4. UE performs PDU Session Establishments for PDU Sessions that could not be changed.](3334fcca5dac808f4fd3840aba35bc2e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF/UPF + participant PCF + Note right of AMF: 1. Determine S-NSSAI need to be changed and the new S-NSSAI + Note right of AMF: 2. Requests SMF to change to the new S-NSSAI + Note right of AMF: 3. Informing UE that S-NSSAI been changed and/or that the UE needs to establish a new PDU Session for the new S-NSSAI + Note right of UE: 4. UE performs PDU Session Establishments for PDU Sessions that could not be changed + +``` + +Sequence diagram illustrating Network Slice change while maintaining the PDU Session. The diagram shows five entities: UE, RAN, AMF, SMF/UPF, and PCF. The sequence of messages is: 1. AMF determines S-NSSAI need to be changed and the new S-NSSAI; 2. AMF requests SMF to change to the new S-NSSAI; 3. AMF informs UE that S-NSSAI has been changed and/or that the UE needs to establish a new PDU Session for the new S-NSSAI; 4. UE performs PDU Session Establishments for PDU Sessions that could not be changed. + +**Figure 6.41.3-1: Network Slice change while maintaining the PDU Session** + +1. AMF determines that a S-NSSAI need to be changed. For scenario 1b and 2d this is determined by information from OAM. For scenario 1c, this is determined by NWDAF. + +AMF then determines the new S-NSSAI to use e.g. by NSSF or by PCF (as in solution #2). + +The solution assume that UE's URSP include rules for the new HPLMN S-NSSAI if the HPLMN S-NSSAI is changed. + +2. If SMF (PSA) supports the new S-NSSAI and the capability to change S-NSSAI (this the SMF indicates to the AMF during PDU Session Establishment), then AMF requests SMF to change to the new S-NSSAI, and initiate procedure towards the UE that the S-NSSAI has been changed. + +If the SMF (PSA) does not support the new S-NSSAI and/or the capability to change S-NSSAI then AMF invokes procedure to initiate PDU Session transfer using any SSC mode as described by other solutions i.e. indicating to SMF to request the UE to change S-NSSAI by establishing a new PDU Session. + +3. The AMF informs the UE, e.g. using UCU, the new Allowed NSSAI (new S-NSSAI can either by set as an S-NSSAI for the Serving network/PLMN or the HPLMN S-NSSAI is changed). The AMF may need to separately indicate to the UE that PDU Sessions will be modified as to avoid the UE to locally release the PDU Sessions before they are changed. To avoid a new indication in UCU, the AMF can add the new S-NSSAI in Allowed NSSAI and then trigger a new UCU after step 4, under the assumption that the UE will not start to use the to be removed S-NSSAI e.g. establishing a new PDU Session, etc. + +For the PDU Sessions that can be changed without re-establishment, the SMF performs PDU Session Modification procedure towards the UE and the NG-RAN indicating the new S-NSSAI for the PDU Session. For the PDU Sessions that require the UE to re-establish them, the AMF/SMF indicates to the UE to perform the re-establishment according to other solutions. + +4. The UE performs PDU Session re-establishment for the PDU Sessions that could not be changed directly. + +#### 6.41.4 Impacts on services, entities and interfaces + +NG-RAN: + +- No impact. + +AMF: + +- Support slice re-mapping. +- send a message to SMF to trigger a change of S-NSSAI. + +SMF: + +- trigger change of S-NSSAI for the PDU Sessions based on AMF request. + +NRF: + +- Support discovery of PCF that support slice re-mapping. + +PCF: + +- Support slice re-mapping. + +UE: + +- Support change of S-NSSAI for serving network while maintaining the PDU Sessions. + +## 6.42 Solution #42: Network controlled change to an alternative S-NSSAI + +### 6.42.1 Introduction + +This solution addresses the bellow requirements from Key Issue #1 "Support of Network Slice Service continuity". + +1) No mobility scenario: + +Scenario 1b): network slice or network slice instance is overloaded or undergoing planned maintenance in CN (e.g. network slice termination). + +Scenario 1c): network performance of the network slice cannot meet the SLA. + +2) Inter RA Mobility scenario: + +Scenario 2d): network slice or network slice instance is overloaded in the target CN. + +In any of the scenarios above, it is assumed that a new S-NSSAI (called alternative S-NSSAI or S-NSSAI-2), which is meant to replace the old S-NSSAI, is identified to serve the traffic which is currently carried on the old network slice (e.g. S-NSSAI-1). + +**NOTE:** This solution targets the use case where change of S-NSSAI is required. The following use cases are not targeted: (a) the same S-NSSAI can be used and the change of NSI within the S-NSSAI is required or (b) the S-NSSAI change within a network internal network resource partitioning is required. + +If the user traffic from the S-NSSAI-1 can be served over the alternative network slice (e.g. S-NSSAI-2), then there are several cases how the alternative S-NSSAI-2 relates to the UE's Subscribed S-NSSAI(s) list: + +Case A: The S-NSSAI-2 is part of the Subscribed S-NSSAIs and already part of the Allowed NSSAI. + +Case B: The S-NSSAI-2 is part of the Subscribed S-NSSAIs, but not part of the allowed NSSAI. The S-NSSAI-2 can be added to the Allowed NSSAI, as the S-NSSAI-2 is supported in the current tracking area (TA). + +Case C: The S-NSSAI-2 is not part of the Subscribed S-NSSAIs (in non-roaming case) or not part of the Configured NSSAI (in roaming case). The UE cannot request and use S-NSSAI-2 unless the S-NSSAI-2 is not part of the UE's Configured NSSAI. + +- The Case C is also possible when an initial alternative S-NSSAI is part of the Subscribed S-NSSAIs, but the initial alternative S-NSSAI cannot be added to the Allowed NSSAI, as the initial alternative S-NSSAI-2 is not supported in the UE's current TA or rejected due to some reason (e.g. due to NSSAA failure). Then the AMF/NSSF determine another alternative S-NSSAI (e.g. S-NSSAI-2). + +This solution attempts to cover all use cases from above. + +### 6.42.2 Functional Description + +The solution proposes that the AMF (or together with the NSSF or OAM system) determines that an old S-NSSAI (e.g. S-NSSAI-1) is unavailable and the alternative S-NSSAI (e.g. S-NSSAI-2) is available in the current TA and should be used to replace the S-NSSAI-1. The AMF internally checks the UE network slice configuration (e.g. Subscribed S-NSSAIs, Allowed NSSAI, Rejected NSSAI) against the S-NSSAI-2 and the AMF applies one of the following procedures: + +- 1) When the S-NSSAI-2 is part of the UE's subscribed S-NSSAIs and S-NSSAI-2 is not part of the rejected NSSAI for the UE (e.g. in the Cases A and B from clause 6.42.1), it is assumed that the S-NSSAI-2 would be also configured in the UE's URSP rules. Specifically, the URSP rule which is used to establish the existing PDU Session on S-NSSAI-1 would also include further RSD including S-NSSAI-2. Therefore, the AMF deduces that the UE configuration with URSP rules (and Configured NSSAI) allows the UE to use S-NSSAI-2; or in other words the AMF determines that UE Network Slice reconfiguration is not needed, i.e. NAS SM procedure can be applied. When the AMF determines that the S-NSSAI-1 becomes unavailable, the AMF triggers SM procedure towards the SMF to indicate that the PDU Session on S-NSSAI-1 should be released and alternative S-NSSAI may be used. The SMF indicates to the UE in the NAS SM signalling for PDU Session release procedure that a new PDU Session can be established on an S-NSSAI different from S-NSSAI-1. The UE re-evaluates the URSP rule determines to use S-NSSAI-2 (as part of a further RSD) for the new PDU Session establishment. If the S-NSSAI-2 is not part of the Allowed NSSAI, the UE first performs Registration procedure to request the registration to S-NSSAI-2 and afterwards the PDU Session establishment procedure. + +NOTE: The assumption that the UE is configured with a URSP rule containing an RSD with S-NSSAI-1 and an RSD with S-NSSAI-2 is justified by the fact that the UE is subscribed with both S-NSSAI-1 and S-NSSAI-2: Furthermore, the network is configured/aware that both S-NSSAI-1 and S-NSSAI-2 can serve the same user traffic, but with different slice preferences, at the time of URSP creation in the PCF. + +- 2) When a first determined alternative S-NSSAI is part of the UE's subscribed S-NSSAIs, but part of the Rejected NSSAI (e.g. due to NSSAA failure), the AMF may determine another alternative S-NSSAI (e.g. S-NSSAI-2) which the UE can use in the current TA. Furthermore, the S-NSSAI-2 may not be part of the Subscribed S-NSSAIs of the UE, which means that the S-NSSAI-2 is not part of the Configured NSSAI. In other words, the UE cannot request, register with, and use the alternative S-NSSAI-2 which is according to the Case C from clause 6.42.1. When the AMF determines that the S-NSSAI-1 becomes unavailable, the AMF triggers UE network slice reconfiguration procedure (e.g. UCU procedure) in order to send a new Configured NSSAI with a corresponding Mapping of the Configured NSSAI information containing the mapping of S-NSSAI-2 to S-NSSAI-1. Such slice mapping information can be also applicable in the HPLMN. + +Please note that in case the S-NSSAI-1 becomes unavailable and there is already established PDU Session on S-NSSAI-1, the network anyhow needs to release the PDU Session independent of the SSC mode of the PDU Session. In case of PDU Session in SSC modes 1 or 2, the SMF initiates PDU Session release procedure and may indicate to the UE that an alternative S-NSSAI can be used. In case of PDU Session in SSC modes 3, the SMF initiates PDU Session modification procedure and indicates to the UE that an alternative S-NSSAI should be used. In any of the cases, the service continuity on the application layer is provided if the application using the PDU Session can manage IP address change. + +### 6.42.3 Procedures + +When the old S-NSSAI (e.g. S-NSSAI-1) is not any longer available and the alternative S-NSSAI (e.g. S-NSSAI-2) is to be used, the Figure 6.42.3-1 shows how the AMF (or together with NSSF) initiates one of the following procedures: + +- option 1) from the Functional Description which is based on SM procedure in Cases A and B from clause 6.42.1; +- option 2) from the Functional Description which is based on MM procedure in Case C from clause 6.42.1. + +![Sequence diagram showing the signalling flow for replacing S-NSSAI-1 with S-NSSAI-2 using SM or MM procedures. The diagram involves UE, AN, AMF, SMF1 (S-NSSAI-1), SMF2 (S-NSSAI-2), and NSSF. It details two options: Option 1 (SM procedure) and Option 2 (MM procedure).](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AN + participant AMF + participant SMF1 as SMF1 (S-NSSAI-1) + participant SMF2 as SMF2 (S-NSSAI-2) + participant NSSF + + Note left of UE: 0a. UE is registered in the network and uses S-NSSAI_1 + Note left of UE: 0b. UE establishes a PDU Session on S-NSSAI-1 to SMF1 + + Note right of AMF: 1. Determines that S-NSSAI-1 is not any longer available and alternative S-NSSAI-2 is to replace S-NSSAI-1. + + Note left of AMF: Option 1) Using SM procedure (and URSP rule with multiple RSD) + Note right of AMF: 2a. If S-NSSAI-2 is part of the Subscribed S-NSSAIs and there is PDU Session on S-NSSAI-1 + Note right of AMF: 2b. Nsmf_PDUSession_ReleaseSMContext request (S-NSSAI-1 unavailable, alternative S-NSSAI is available) + Note left of UE: 2c. PDU Session Release request (use alternative S-NSSAI) + Note right of SMF1: 2d. Nsmf_PDUSession_UpdateSMContext response + Note left of UE: 3a. If S-NSSAI-2 not in Allowed NSSAI, perform registration to S-NSSAI-2 + Note left of UE: 3b. NAS message (S-NSSAI-2, DNN1, N1 SM container (PDU Session Establishment Request)) + + Note right of NSSF: 4a. If S-NSSAI-2 is NOT part of UEs Subscribed/Configured S-NSSAIs, AMF determines to apply mapping of S-NSSAI-2 to S-NSSAI-1 + Note left of AMF: Option 2) Using MM procedure for UE network slice reconfiguration + Note right of AMF: 4b. UCU Command (new Configured NSSAI (S-NSSAI-2), Mapping of Configured NSSAI (S-NSSAI-2 to S-NSSAI-1), Allowed NSSAI, Mapping of Allowed NSSAI) + Note left of UE: 5a. If S-NSSAI-2 not in Allowed NSSAI, perform registration to S-NSSAI-2 + Note left of UE: 5b. NAS message (S-NSSAI-2, mapping to S-NSSAI-1, DNN1, N1 SM container (PDU Session Establishment Request)) + Note right of SMF2: 5c. Nsmf_PDUSession_CreateSMContext request (S-NSSAI-2, mapping to S-NSSAI-1, DNN1, N1 SM container) + +``` + +Sequence diagram showing the signalling flow for replacing S-NSSAI-1 with S-NSSAI-2 using SM or MM procedures. The diagram involves UE, AN, AMF, SMF1 (S-NSSAI-1), SMF2 (S-NSSAI-2), and NSSF. It details two options: Option 1 (SM procedure) and Option 2 (MM procedure). + +**Figure 6.42.3-1: Signalling flow for replacing the S-NSSAI-1 with S-NSSAI-2 by using either SM or MM procedures** + +The detailed description of the steps is provided as follows: + +0a. The UE requests registration with the network and with a network slice S-NSSAI-1. + +0b. The UE initiates the establishment of a PDU Session on S-NSSAI-1. The SMF1 is selected by the AMF to be the serving SMF for the PDU Session. + +1. The AMF determines at least one of: (a) S-NSSAI-1 becomes unavailable and (b) an alternative S-NSSAI (e.g. S-NSSAI-2) can be used to replace S-NSSAI-1. The reason why S-NSSAI-1 becomes unavailable can be one of: non-mobility event (e.g. OAM or NSSF/NF reconfiguration, S-NSSAI-1 will be down due to network maintenance); or UE mobility event (e.g. the T-AMF does not support S-NSSAI-1). + +The AMF proceeds either with Option 1) in step 2 or with Option 2) in step 4 as described below. + +Option 1) (using SM procedure and existing URSP rules): + +- 2a. If the AMF determines that the S-NSSAI-2 is part of the UE's subscribed S-NSSAIs or part of the Configured NSSAI, the AMF assumes that the UE has been provided with the URSP rules including the use of the S-NSSAI-2. If there is at least one established PDU Session on S-NSSAI-1, the AMF triggers Session Management procedure to sends a request to the SMF1 to release the PDU Session. +- 2b. The AMF sends to the SMF1 Nsmf\_PDUSession\_ReleaseSMContext request message including one or more indications that the S-NSSAI-1 is unavailable and alternative S-NSSAI may be used. +- 2c. The SMF1 initiates the PDU Session release procedure in case of SSC mode 1 and 2. In case of SSC mode 3, the SMF1 may trigger PDU Session modification procedure to trigger the UE to initiate the establishment of a new PDU Session. In any of the procedures (e.g. PDU Session release/modification procedure), the SMF includes an indication that the PDU Session may be re-established on an S-NSSAI different from S-NSSAI-1. +- 2d. The SMF1 acknowledges to the AMF the release of the PDU Session. +- 3a. If the S-NSSAI-2 is not part of the Allowed NSSAI (e.g. Case B from clause 6.42.1), the UE first performs Registration procedure to request the registration to S-NSSAI-2. +- 3b. The UE re-evaluates the URSP rule and determines a further RSD having an S-NSSAI different from S-NSSAI-1, i.e. S-NSSAI-2. In Case A from clause 6.42.1 or after step 3a, the UE triggers a new PDU Session(s) establishment according to the further RSD which contains S-NSSAI-2. The UE sends a NAS message to the AMF including S-NSSAI-2, and in case of SSC mode 3, the UE includes the old PDU Session ID. + +Option 2) (using MM procedure for UE network slice reconfiguration): + +- 4a. If the determined alternative S-NSSAI cannot be potentially included in the Allowed NSSAI for the UE (e.g. due to stored NSSAA failure result or available S-NSSAIs in the current UE's TA) as per Case C from clause 6.42.1, the AMF may determine yet another alternative S-NSSAI (e.g. S-NSSAI-2) not part of the UE's Subscribed S-NSSAIs; or the AMF simply determines an alternative S-NSSAI-2 which is not part of the UE's Subscribed S-NSSAIs. Then the AMF determines to configure the UE to use the S-NSSAI-2 in addition to S-NSSAI-1, i.e. by applying the network slice mapping mechanisms to configure the UE to use S-NSSAI-2 wherein the S-NSSAI-2 is mapped to the S-NSSAI-1. + +If the NSSF is responsible to determine the Configured NSSAI, Allowed NSSAI and/or Rejected NSSAI, the AMF sends a Nnssf\_NSSelection\_Get request service operation to the NSSF including an additional indication that an alternative S-NSSAI to S-NSSAI-1 is required. The NSSF may determine the S-NSSAI-2 to replace S-NSSAI-1, the NSSF may create the Configured NSSAI and Allowed NSSAI with the corresponding mapping information and send them to the AMF. + +- 4b. The AMF triggers the UE Configuration Update (UCU) Command procedure where the AMF may include a new Configured NSSAI containing S-NSSAI-2 and in addition mapping information of S-NSSAI-2- to S-NSSAI-1; and new Allowed NSSAI with corresponding mapping of Allowed NSSAI information. + +NOTE: The AMF can wait with step 4b until the established PDU Session on S-NSSAI-1 is not in active state (e.g. the user plane resources are not activated). This would allow the UE to establish new PDU Session(s) and terminate the existing PDU Session(s) while there is no user traffic to be sent over the PDU Session(s). + +- 5a. The UE internally determines to trigger the establishment of new PDU Session(s) for the user traffic which is currently routed to the S-NSSAI-1. If the S-NSSAI-2 is not part of the Allowed NSSAI, the UE first performs Registration procedure to request the registration to S-NSSAI-2. +- 5b. The UE applies the same URSP rule and same RSD, but the UE includes the S-NSSAI-2 and the mapping information of S-NSSAI-2 to S-NSSAI-1 in the NAS message to the AMF. The UE creates the PDU Session establishment request according the matching URSP and the UE includes it the N1 SM container in the NAS message to the AMF. +- 5c. The SMF2 uses the mapped S-NSSAI value (e.g. S-NSSAI-1) from the slice mapping information received from the UE to retrieve the UE subscription data from the UDM. + +After some time when the AMF may determines that S-NSSAI 1 can be used again, the AMF would perform the UCU procedure to configure the UE to use the S-NSSAI-1 again. + +## 6.42.4 Impacts on services, entities and interfaces + +Impacts to the AMF: + +- Determine whether to trigger (a) Session Management procedure (if the S-NSSAI-2 is configured in the UE), or (2) Mobility Management procedure (if the S-NSSAI-2 is not configured in the UE). +- The AMF is able to determine whether a potentially alternative S-NSSAI can be included in the Allowed NSSAI for the UE (e.g. by checking the stored results of NSSAA procedure). +- In case of option 1), i.e. SM procedure, the AMF indicates to the SMF that PDU Session re-establishment on S-NSSAI different from the S-NSSAI-1. + +Impacts to the NSSF: + +- In case of option 2), i.e. MM procedure, and NSSF is involved, the ability to create alternative S-NSSAI to an original S-NSSAI, e.g. creating a new mapped S-NSSAI information. + +Impacts to the SMF: + +- In case of option 1), i.e. SM procedure, the ability to indicate to the UE in the PDU Session release/modification procedure that the PDU Session can be re-established on S-NSSAI different from the S-NSSAI-1. + +Impacts to the UE: + +- In case of option 1), if another RSD of the same URSP rule is available containing an S-NSSAI different from S-NSSAI-1, the UE uses such RSD to re-establish the PDU Session. +- In case of option 2), there are impacts to the 5GC Network Functions but **no impacts** to the UE as the current UE specification supports the "Mapping Of Allowed NSSAI", "Mapping Of Configured NSSAI" and the change of them. + +## 6.43 Solution #43: Allowed NSSAI Determination in Initial Registration to Support Network Slice Service Continuity + +### 6.43.1 Introduction + +The solution aims to address Key Issue #1: Support of network slice service continuity. + +1) No mobility scenario: + +Scenario 1b): network slice or network slice instance is overloaded or undergoing planned maintenance in CN (e.g. network slice termination). + +Scenario 1c): network performance of the network slice cannot meet the SLA. + +2) Inter RA Mobility scenario: + +Scenario 2d): network slice or network slice instance is overloaded in the target CN. + +### 6.43.2 Functional Description + +This solution allows AMF to obtain a secondary NSSAI related to each S-NSSAI in Allowed S-NSSAI during registration procedure. The value of secondary NSSAI is decided by the AMF through querying NSSF. NSSF determines secondary NSSAI based on the slice load, UE subscription, etc. The AMF then stores the mapping between the secondary NSSAI and Allowed NSSAI that UE can access in current registration area, and UE will not need to re-visit the NSSF every time the value of secondary NSSAI needed unless the stored information in AMF cannot determine the secondary NSSAI in the current situation, e.g. the access type changes, the mapping information stored in the AMF is missing/expired, UE subscription changes or UE has moved out of current registration area, etc. The secondary NSSAI is also part of Allowed S-NSSAI, so the Allowed S-NSSAI consists two parts: S-NSSAIs of network slices which UE can access in current registration area and S-NSSAIs (i.e. secondary S-NSSAI) which network operator deploy to support slice continuity. USRP provided to UE contains only first part. + +In no mobility scenario, AMF will trigger network slice PDU session change to the new secondary NSSAI. + +In mobility scenario, the mapping information is provided from the source AMF to the target AMF during handover procedure, if the target AMF cannot support all the allowed NSSAI and secondary NSSAI, it will request to the NSSF in the registration procedure to ask for a new mapping information in current tracking area, make sure the new target AMF can also support the service continuity. + +### 6.43.3 Procedures + +#### 6.43.3.1 Secondary NSSAI Determination + +![Sequence diagram illustrating the Secondary NSSAI determination during the initial registration procedure. The diagram shows interactions between UE, Initial AMF, Target AMF, NSSF, and UDM. The process starts with the UE sending an Initial Registration Request to the Initial AMF. The Initial AMF then sends a Nudm_SDM_Get request to the UDM. The UDM responds with Nudm_SDM_Response. The Initial AMF then sends a Nnssf_NSSelection_Get request to the NSSF. The NSSF responds with Nnssf_NSSelection_Get_Response (Secondary S-NSSAI). The Initial AMF then sends a Namf_Communication N1MessageNotify to the Target AMF. A horizontal bar labeled '7. rest registration procedure' spans across the bottom. Finally, the Target AMF sends a Registration Accept (Allowed NSSAI) to the UE.](8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Initial AMF + participant Target AMF + participant NSSF + participant UDM + + Note left of UE: 1. Initial Registration Request + UE->>Initial AMF: 1. Initial Registration Request + Note right of Initial AMF: 2. Nudm_SDM_Get (Slice Selection Subscription data) + Initial AMF->>UDM: 2. Nudm_SDM_Get (Slice Selection Subscription data) + Note right of UDM: 3. Nudm_SDM_Response + UDM-->>Initial AMF: 3. Nudm_SDM_Response + Note right of Initial AMF: 4. Nnssf_NSSelection_Get + Initial AMF->>NSSF: 4. Nnssf_NSSelection_Get + Note right of NSSF: 5. Nnssf_NSSelection_Get_Response (Secondary S-NSSAI) + NSSF-->>Initial AMF: 5. Nnssf_NSSelection_Get_Response (Secondary S-NSSAI) + Note right of Initial AMF: 6. Namf_Communication N1MessageNotify + Initial AMF->>Target AMF: 6. Namf_Communication N1MessageNotify + Note right of Target AMF: 7. rest registration procedure + Target AMF-->>UE: 8. Registration Accept (Allowed NSSAI) + +``` + +Sequence diagram illustrating the Secondary NSSAI determination during the initial registration procedure. The diagram shows interactions between UE, Initial AMF, Target AMF, NSSF, and UDM. The process starts with the UE sending an Initial Registration Request to the Initial AMF. The Initial AMF then sends a Nudm\_SDM\_Get request to the UDM. The UDM responds with Nudm\_SDM\_Response. The Initial AMF then sends a Nnssf\_NSSelection\_Get request to the NSSF. The NSSF responds with Nnssf\_NSSelection\_Get\_Response (Secondary S-NSSAI). The Initial AMF then sends a Namf\_Communication N1MessageNotify to the Target AMF. A horizontal bar labeled '7. rest registration procedure' spans across the bottom. Finally, the Target AMF sends a Registration Accept (Allowed NSSAI) to the UE. + +**Figure 6.43.3.1-1: Secondary NSSAI information obtained during initial registration procedure** + +- 1: UE carries the Requested NSSAI to initiate the initial registration process. +- 2: If the current Initial AMF needs to obtain the UE subscription information to perform the redirection/reroute process, the AMF initiates a Nudm\_SDM\_Get request to obtain the UE subscription information. +- 3: UDM returns the subscription information of the UE. +- 4: Initial AMF carries the Requested NSSAI, Subscribed NSSAI, TAI and other information to initiate a Nnssf\_NSSelection\_Get request to obtain relevant network slice selection information. +- 5: NSSF returns Initial AMF related information, including: Allowed NSSAI, Secondary NSSAI mapping with Allowed NSSAI UE can access in current registration area, AMF Set or AMF address list, NSI-ID. NSSF can determine a secondary NSSAI for each Subscribed NSSAI by considering UE location, subscription and some other information. +- 6: Initial AMF performs AMF redirection, and transmits the network slice selection information to the target AMF, including: Allowed NSSAI, Secondary NSSAI mapping corresponding to Allowed NSSAI UE can access in current registration area, AMF Set or AMF address list, NSI-ID. In this step, Target AMF stores the mapping messages of Allowed NSSAI UE can access in current registration area and Secondary NSSAI returned by NSSF, avoiding query NSSF every time UE registered into the network. +- 7,8: The rest of the registration procedure. + +### 6.43.3.2 PDU Session Transferred to a New Network Slice in No Mobility Scenario + +![Sequence diagram for PDU Session Transferred to a New Network Slice in No Mobility Scenario. Lifelines: UE, RAN, AMF, S-SMF, T-SMF, S-UPF, T-UPF. The diagram shows the AMF deciding to trigger a PDU session handover to a secondary S-NSSAI. It then details two paths: SSC Mode 2, which involves a PDU session release with S-UPF followed by a new establishment with T-UPF; and SSC Mode 3, which involves a PDU session modification command and ACK, followed by a new establishment with T-UPF, and finally a release with S-UPF.](d3253d5db64378db6e72b66b41067a5b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant S-SMF + participant T-SMF + participant S-UPF + participant T-UPF + + Note right of AMF: 1. AMF decide to trigger PDU session handover to the secondary S-NSSAI + AMF->>S-SMF: 2.Nsmf_PDUSession_UpdateSMContext Request + S-SMF-->>AMF: 3.Nsmf_PDUSession_UpdateSMContext Response + AMF->>S-SMF: 4a.Nsmf_PDUSession_SMContextStatusNotify Request and Response + + Note left of AMF: SSC Mode 2 + AMF->>S-UPF: 5a.PDU session release with S-UPF + Note right of AMF: 6a.PDU session establishment with T-UPF + Note left of AMF: SSC Mode 3 + AMF->>S-SMF: 4b.Nsmf_PDUSession_SMContextStatusNotify Request and Response + AMF->>T-SMF: 5b.Nsmf_Communication_N1N2Message Transfer + UE->>AMF: 6b.PDU Session Modification Command and ACK + AMF->>T-SMF: 7b.Nsmf_PDUSession_UpdateSMContextS Request + T-SMF-->>AMF: 8b.Nsmf_PDUSession_UpdateSMContextS Response + Note right of AMF: 9b. PDU session establishment with T-UPF + Note right of AMF: 10b.PDU session release with S-UPF + +``` + +Sequence diagram for PDU Session Transferred to a New Network Slice in No Mobility Scenario. Lifelines: UE, RAN, AMF, S-SMF, T-SMF, S-UPF, T-UPF. The diagram shows the AMF deciding to trigger a PDU session handover to a secondary S-NSSAI. It then details two paths: SSC Mode 2, which involves a PDU session release with S-UPF followed by a new establishment with T-UPF; and SSC Mode 3, which involves a PDU session modification command and ACK, followed by a new establishment with T-UPF, and finally a release with S-UPF. + +Figure 6.43.3.2-1: PDU Session transferred to a new network slice in no mobility scenario + +- 1: AMF decides to trigger PDU session handover to secondary NSSAI when the SLA cannot meet or the CN in overloaded. The determination of Secondary NSSAI is according to the relationship stored inside AMF during registration procedure. +- 2: AMF triggers the PDU session Modification process, the AMF send secondary NSSAI to S-SMF in smf\_PDUSession\_UpdateSMContext request. +- 4-10. The rest of PDU session management procedures in different SSC mode in clause 4.3.5 of TS 23.502 [5]. + +### 6.43.3.3 PDU session transferred to a new network slice in mobility scenario + +![Sequence diagram for PDU session transferred to a new network slice in mobility scenario. Lifelines: UE, S-RAN, T-RAN, S-AMF, T-AMF, S-SMF, T-SMF, S-UPF, T-UPF. The diagram shows the S-RAN deciding to trigger a relocation via N2, sending a handover request to S-AMF, and then the T-AMF selection process. It then shows the AMF deciding to trigger a PDU session handover to the secondary S-NSSAI, followed by the rest of the PDU session transfer in different SSC mode.](d3a5878a2aeffba0c2c5e8b75ce5c37e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-RAN + participant T-RAN + participant S-AMF + participant T-AMF + participant S-SMF + participant T-SMF + participant S-UPF + participant T-UPF + + Note right of S-RAN: 1. S-RAN decide to trigger a relocation via N2 + S-RAN->>S-AMF: 2.Handover Request + Note right of T-AMF: 3.T-AMF selection (Secondary S-NSSAI) + Note right of AMF: 4.Rest of Handover Procedure + Note right of AMF: 5. AMF decide to trigger PDU session handover to the secondary S-NSSAI + Note right of AMF: 6.Rest of PDU session transfer in different SSC mode + +``` + +Sequence diagram for PDU session transferred to a new network slice in mobility scenario. Lifelines: UE, S-RAN, T-RAN, S-AMF, T-AMF, S-SMF, T-SMF, S-UPF, T-UPF. The diagram shows the S-RAN deciding to trigger a relocation via N2, sending a handover request to S-AMF, and then the T-AMF selection process. It then shows the AMF deciding to trigger a PDU session handover to the secondary S-NSSAI, followed by the rest of the PDU session transfer in different SSC mode. + +Figure 6.43.3.3-1: PDU Session transferred to a new network slice in no mobility scenario + +- 1: S-RAN determines to execute the N2 relocation process +- 2: S-RAN sends a handover request to S-AMF +- 3: During the T-AMF selection process, the corresponding relationship between the Secondary NSSAI and the Allowed NSSAI originally stored in the S-AMF is sent to the T-AMF. + +After the information is received by T-AMF, it compares with the corresponding relationship stored by itself. If it is consistent with the corresponding relationship stored in the current T-AMF, then continue the rest of + +handover procedure; if it is inconsistent with the corresponding relationship stored in the current T-AMF, there are following possibilities: + +Existed relationship inside T-AMF includes all the Allowed NSSAI in S-AMF but the value of Secondary NSSAI is different, the T-AMF will perform following service continuity process according to the existed relationship and delete the received information from S-AMF; + +Existed relationship in T-AMF does not include all the Allowed NSSAI in S-AMF, T-AMF will query NSSF in the following registration procedure after handover complete as described in clause 4.9.1.3.3 of TS 23.502 [5], even if AMF re-allocation is not needed any more, to obtain the latest Secondary NSSAI and Allowed NSSAI related information at UE's current location area. + +- 4: Rest of the RAN handover procedures. +- 5, 6: Similar to the No mobility scenario, AMF triggers the migration of network slices when it finds that the current SLA is not satisfied or the CN load is insufficient as described in clause 6.43.3.2. + +### 6.43.4 Impacts on services, entities and interfaces + +The following impacts have been identified: + +#### AMF: + +- Support storage of secondary NSSAI information obtained in initial registration procedure; +- Send original secondary NSSAI information from S-AMF to T-AMF during RAN handover and related processing. + +#### NSSF: + +- Decide value of secondary NSSAI during initial registration procedure. + +#### SMF: + +- Trigger PDU session modification when receiving secondary NSSAI from AMF. + +#### UE, NG-RAN: + +- Handling PDU session modification which related to the secondary NSSAI. + +## 6.44 Solution #44: Controlling UE access to the network per Network Slice on a per cell level granularity + +### 6.44.1 Introduction + +The solution addresses the "Network Slice Area of Service for services not mapping to existing TAs boundaries" of the Key Issue #3: Network Slice Area of Service for services not mapping to existing TAs boundaries and Temporary network slices. + +### 6.44.2 Functional Description + +The solution provides two mechanisms to select among for addressing the case when Network Slice Area of Service for services not mapping to existing TAs boundaries. + +The two mechanisms are summarized as follows: + +1. Extend Access and mobility related policy information such that Service Area Restrictions can be set per S-NSSAI on a per cell level granularity. UDM can set Service Area Restrictions per subscribed S-NSSAI and also indicate the geographical information (e.g. longitude/latitude, zip code, etc) or (for non-roaming) list of cells, As per current logic the PCF can adjust the Service Area Restrictions, and then AMF sends the Service Area Restrictions to the UE. The UE then applies the Service Area Restrictions possibly on a per network slice and cell granularity. + +## 6.44.3 Procedures + +### 6.44.3.1 General + +During initial registration the UE indicates that the UE is supporting the extended functionality i.e. URSP, Service Area Restrictions The AMF applies current logic and if the UE requests or subscribes to S-NSSAIs that are applicable for the extended location restriction and the UE does not support the extended functionality, the network decides whether to provide the applicable S-NSSAI in Allowed NSSAI and Configured NSSAI to the UE. The decision can be implemented as operator policy in AMF, or decided by another NF e.g. UDM, NSSF or PCF in which case the UE support needs to be forwarded to the NF. + +![Sequence diagram illustrating the Registration procedure for Service Area Restrictions. The diagram shows interactions between UE, RAN, AMF, PCF, and UDM. The process starts with NG SETUP and NG CONFIGURATION UPDATE, followed by Initial Registration from UE to AMF. The AMF then executes steps 2 to 14a from 23.502 clause 4.2.2.2.2. The AMF sends a Nudm_SDM_Get() request to the UDM, which responds with Nudm_SDM_Get Response. The AMF then performs AM Policy Establishment with the PCF. The AMF executes the rest of the Registration call flow (steps 14c-20) and sends a Registration Accept to the UE. Finally, the UE, AMF, and NG-RAN store and enforce the Location restriction, and the AMF executes the rest of the Registration call flow (steps 21b-25).](2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant PCF + participant UDM + + Note right of RAN: 0. NG SETUP and NG CONFIGURATION UPDATE + UE->>AMF: 1. Initial Registration + Note right of AMF: 2. Steps 2 to 14a in 23.502 clause 4.2.2.2.2 + AMF->>UDM: 3. Nudm_SDM_Get() + UDM-->>AMF: 4. Nudm_SDM_Get Response + Note right of AMF: 5. AM Policy Establishment + Note right of AMF: 6. Execute the rest of Registration call flow, steps 14c-20 + AMF-->>UE: 7. Registration Accept + Note left of AMF: 8. UE, AMF and NG-RAN stores and enforces the Location restriction + Note right of AMF: 9. Execute the rest of Registration call flow, steps 21b-25 + +``` + +Sequence diagram illustrating the Registration procedure for Service Area Restrictions. The diagram shows interactions between UE, RAN, AMF, PCF, and UDM. The process starts with NG SETUP and NG CONFIGURATION UPDATE, followed by Initial Registration from UE to AMF. The AMF then executes steps 2 to 14a from 23.502 clause 4.2.2.2.2. The AMF sends a Nudm\_SDM\_Get() request to the UDM, which responds with Nudm\_SDM\_Get Response. The AMF then performs AM Policy Establishment with the PCF. The AMF executes the rest of the Registration call flow (steps 14c-20) and sends a Registration Accept to the UE. Finally, the UE, AMF, and NG-RAN store and enforce the Location restriction, and the AMF executes the rest of the Registration call flow (steps 21b-25). + +**Figure 6.44.3.1-1. Registration procedure for Service Area Restrictions** + +The initial registration procedure is executed as in clause 4.2.2.2.2 of TS 23.502 [5] with the following differences. + +1. The UE indicates the UE's capability to support the extended location restriction functionality in the Registration message e.g. in the UE 5GMM Core Network Capability. +2. No changes to steps 2 to 14a in clause 4.2.2.2.2 of TS 23.502 [5]. +3. If UDM is to be able to decide whether to provide S-NSSAIs applicable for extended location restriction to the UE, then AMF indicates whether the UE and serving network supports the extended location restriction functionality. +4. The UDM can provide Service Area Restrictions with per S-NSSAI restrictions. The location information can be as currently, geographical information (e.g. longitude/latitude, zip code, etc) or list of cells. The UDM can adapt the content based on the knowledge whether the UE and serving network supports the extended location restrictions. +5. For the Service Area Restrictions option, the AMF provides the subscribed Service Area Restrictions to the PCF and the PCF can adapt the content. +6. No changes to steps 14c to 20 in clause 4.2.2.2.2 of TS 23.502 [5]. +7. AMF provides the extended Service Area Restrictions to the UE. + +8. The UE stores the extended location restrictions and enforces the information. + +For the extended Service Area Restrictions option, the UE applies the Allowed or Non-Allowed Area per S-NSSAI and the granularity per list of cells + +The NG-RAN enforces the extended location restrictions for Service Area Restrictions. The AMF enforces the extended location restrictions for the Service Area Restrictions option + +10. In step 22 the UE can additionally report that the extended location restrictions been stored. No additional changes to steps 21b to 25 in clause 4.2.2.2.2 of TS 23.502 [5]. + +### 6.44.3.2 Mobility procedures + +The NG-RAN gets the extensions as part of the Mobility Restriction List (that is extended with per S-NSSAI and per cell restrictions) and the Mobility Restrictions for CM-CONNECTED state when in RRC-Connected state are executed by the radio access network and the core network such that UP for the associated S-NSSAIs are not allowed to be activated (as per current procedures). + +## 6.44.4 Impacts on services, entities and interfaces + +NG-RAN: + +- Support extended location restrictions for the Service Area Restrictions option. + +AMF: + +- Support extended location restrictions. + +PCF: + +- Support extension with a per cell level granularity per network slice for Service Area Restrictions. + +UE: + +- Support extended location restrictions and indicate the UE's support for e.g. support Service Area Restrictions on a per S-NSSAI and cell level granularity. + +UDM: + +- Service Area Restrictions per subscribed S-NSSAI. + +## 6.45 Solution #45: Constrained Service Area for the Network Slice + +### 6.45.1 Introduction + +This solution addresses KI#3: Network Slice Area of Service for services not mapping to existing TAs boundaries, and temporary network slices. + +When the area of services over a network slice does not match the existing Tracking Area boundaries, the Constrained Service Area for Network Slice (CSANS) with cell granularity per S-NSSAI is proposed to improve the radio resources usage and avoid the complexity of TA reallocation for the network slice with a limited lifetime. Dedicated resources may not be allocated for the network slice in the cell(s) belonging to the CSANS in which the services related to the user plane are allowed without SLA guarantee, according to the operator's policy. + +### 6.45.2 Functional Description + +The Constrained Service Area information for the network slice is configured in NG-RAN by the OAM. The Constrained Service Area per S-NSSAI includes the Cell IDs of the cell(s), which belong to the CSANS. The uniform support of the network slice within a TA is not changed. For the cells both in the TA and the CSANS, the network slice is available, but without dedicated resources. For the cells within the TA but outside the CSANS, dedicated resources are allocated for the network slice to guarantee the SLA of the services. + +After the network slice with corresponding CSANS is deployed and subscribed by the UE, the UE includes the S-NSSAI in the Requested NSSAI and obtains an Allowed NSSAI including the S-NSSAI after registration procedure, when the UE is in a Tracking Area supporting the S-NSSAI, no matter the UE is currently in a cell belonging to the CSANS or not. To avoid protocol impact on the UE, the CSANS information is not to be sent to the UE. + +To avoid unnecessary service interruption or experience deterioration, the NG-RAN should prevent the UE with active PDU session related to the S-NSSAI from entering into the CSANS unnecessarily. + +### 6.45.3 Procedures + +#### 6.45.3.1 Configuration of Constrained Service Area information + +When the area of services over the network slice does not match the existing deployed TA boundaries, the Constrained Service Area information is configured in the NG-RAN. + +The uniform support of the network slice within a TA is not changed. If in the TA there is any cell not in the area of services over a specific network slice, the NG-RAN is configured with the Constrained Service Area information of the network slice. + +NOTE: There may be two ways to indicate the Constrained Service Area information: Either using Constrained Service Area per S-NSSAI as a list of cell(s) out of the area of services, or vice versa, using Service Area per S-NSSAI as a list of cell(s) in the area of services. + +#### 6.45.3.2 UE mobility + +When the UE is in a Tracking Area supporting the S-NSSAI, no matter whether the UE is currently in a cell belonging to the CSANS or not, the UE obtains Allowed NSSAI including the S-NSSAI after registration with the Requested NSSAI, which may include the S-NSSAI related to the CSANS. + +In order to avoid unnecessary service interruption or experience deterioration, the handover procedure should be optimized for the PDU session in the network slice related to the CSANS. If the radio quality of any cell out of the CSANS is acceptable, the NG-RAN removes the neighbour cell belonging to the CSANS from the target cell list for handover to prevent the UE with active PDU session related to the S-NSSAI from unnecessarily entering into a cell belonging to the CSANS. + +NOTE: The handover optimization procedure depends on the RAN WG. + +### 6.45.4 Impacts on services, entities and interfaces + +RAN: + +- Prevent the UE from entering into a cell belonging to the CSANS unnecessarily when any PDU session related to the S-NSSAI has an active user plane. +- Keep the configuration of the Constrained Service Area information. + +## 6.46 Solution #46: Controlling network slice based on UE's inactive PDN connection + +### 6.46.1 Introduction + +This solution is an additional enhancement to all the solutions where the network will release the existing PDN connection on the detection of PDN inactivity. + +### 6.46.2 Functional Description + +#### Implicit deactivation approach: + +In this approach all the existing solution suggests that PDU session inactivity timer will run at both UE & SMF. After expiry of this timer both UE & SMF implicitly release the existing PDU session upon detection of PDU inactivity. + +Now it is suggested that when UE is attached to EPC and having one established PDN connections then both UE and SMF+PGW-C release the existing PDN connection upon detection of PDN inactivity. + +#### Explicit deactivation approach: + +In this approach all the existing solution suggests that PDU session inactivity timer will run only at SMF. After expiry of this timer SMF will release the existing PDU session by explicitly informing to UE upon detection of PDU inactivity. + +Now it is suggested that when UE is attached to EPC and having one established PDN connections then SMF+PGW-C release the existing PDN connection upon detection of PDN inactivity by explicitly informing to UE. + +### 6.46.3 Procedures + +There is no new procedures for this solution. The existing solution procedures applicable with below difference: + +SMF -> SMF+PGW-C. + +UPF -> UPF+PGW-U. + +PDU Session -> PDN Connections. + +5GS -> EPS. + +### 6.46.4 Impacts on services, entities and interfaces + +SMF+PGW-C: + +- A new trigger for the PDN connection release procedure is added. +- Providing implicit PDN connection deactivation timer to UE during PDN connection establishment procedure in the case of implicit deactivation approach. +- Configuring the PDN connections inactivity timer at the UPF+PGW-U for the explicit deactivation approach. + +--- + +## 7 Overall Evaluation + +### 7.1 Evaluation for KI#1 + +Solutions #1, #2, #3, #4, #5, #15, #32, #40, #41, #42 and #43 are documented to address all or some of the scenarios 1b), 1c) and 2d) from the KI#1 description. + +The Table 7.1-1 shows the evaluation of the solutions. + +**Editor's note:** The evaluation in Table 7.1-1 is based on the TR 23.700-41 version V1.0.0. Updates to the solutions in future TR versions can result in update to the evaluation in the Table 7.1-1. + +**Table 7.1-1: Evaluation of solutions for Key Issue 1** + +| | | +|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Solution #1
Additional S-NSSAI associated with the PDU session

|

The main principle is that a PDU session can be associated with multiple S-NSSAIs in the network (i.e. NG-RAN, AMF, SMF, UPF). During PDU session establishment or HO procedure, the AMF notifies the new S-NSSAI to SMF. The SMF provides the new S-NSSAI to the NG-RAN. The network does not notify the change of S-NSSAI in the UE while NG-RAN, AMF, SMF and UPF update the S-NSSAI of the PDU Session.

The solution applies to certain deployments where the old S-NSSAI and the new S-NSSAI are associated with the same NSI (e.g. the new S-NSSAI uses shared resource of the NSI, whereas the old S-NSSAI uses dedicated resource of the NSI). One benefit is that the network can apply the procedure of PDU Session transfer to the new S-NSSAI for legacy UEs, as there are no UE impacts.

This solution requires that the new S-NSSAI is part of the Allowed NSSAI.

The solution assumes that all the S-NSSAIs supporting slice remapping establish end-to-end availability in the combination of OAM and signalling among network functions, i.e. the SMF and the UPF shall always support both original S-NSSAI and new S-NSSAI.

This solution uses different S-NSSAI towards the UE compared to S-NSSAI used in the network.

| +|

Solution #2
Slice Re-mapping Capabilities for Network Slice Service Continuity

|

The main principle is that the AMF derive a new/alternative S-NSSAI for a congested S-NSSAI optionally requesting the AM PCF (which specifically supports slice re-mapping), where the new/alternative S-NSSAI has to support the same DNN, DNAI and selected within Allowed NSSAI. Then, the AMF requests the current SMF to change the PDU Session to the new S-NSSAI. The SMF triggers the PDU session transfer to the new S-NSSAI without UPF relocation (i.e. Option 1, re-use the existing PDU session) and with UPF relocation (i.e., Option 2, new PDU session established similar to SSC mode 3) based on the SSC mode of the PDU session and sends to the UE a PDU Session Modification Request including the corresponding cause value and the new S-NSSAI.

The solution also proposes to update the URSP rules of the UE by means of UE Policy PCF trigger of slice re-mapping event. Further, in the solution, AM PCF based new S-NSSAI selection requires that the AM PCF has knowledge about the S-NSSAIs configuration.

It is not specified when the AMF triggers the slice remapping procedure.

Besides, the UE may not use updated URSP immediately. It is unclear how the service continuity is supported in this case.

| +|

Solution #3
Support of Network Slice Service continuity using a SSC mode 3 type of Service continuity

|

The main principle is that the AMF determines the need to exchange old/original S-NSSAI 1 with a new/alternative S-NSSAI 2 (and in case of mobility to T-RAN, the T-RAN temporarily accepts the PDU Session of S-NSSAI 1 and indicates in the Path Switch Request to the AMF an alternative S-NSSAI 2). The AMF triggers UCU procedure to the UE to include both S-NSSAI 1 and S-NSSAI 2 in the Allowed NSSAI, and afterwards the AMF notifies the SMF about the end of usage of S-NSSAI 1 and to use the new S-NSSAI 2.

The solution proposes to notify the UE of slice re-mapping by enhancing the Allowed NSSAI format and using the NAS MM signalling, and in addition, the solution proposes to also use SM signalling from the SMF (SSC mode 3 like procedure) to update the UE about the S-NSSAI change/remapping. The question is whether a single NAS signalling is not enough to reconfigure the UE about the S-NSSAI change, i.e. either using NAS MM or NAS SM signalling may be sufficient. As the network slice configuration is performed in the NAS MM-sublayer, it would aligned with the existing network slice configuration to use the NAS MM signalling from the AMF to the UE.

Additionally, it is not clear whether the impacts to the NG-RAN (notification about slice re-mapping) are required, since there is no NG-RAN specific behaviour to support slice re-mapping. The AMF itself can determine the alternative S-NSSAI 2 as in other solutions (e.g. solution #1, 32, 42, etc.).

How to do slice remapping for N2 based handover is FFS.

| + +| | | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #4
PDU Session on compatible network slice |

[Non-mobility use case] During new PDU Session Establishment, if there are further RSDs for the matching URSP rule, the UE includes in the NAS message to the AMF an alternative S-NSSAI (which is stored in the UE's context in the AMF). If the original S-NSSAI is congested, the AMF may use the alternative S-NSSAI to select an SMF and continue with the PDU Session establishment on the alternative S-NSSAI.

The solution covers the use case of a new PDU Session establishment. The following analysis is provided:

  • - If the alternative S-NSSAI (sent from the UE to the AMF) is part of the Rejected NSSAI or not available in the current TA, the AMF cannot use such UE-indicated alternative S-NSSAI. Therefore, the AMF itself is required to have the ability to determine an appropriate alternative S-NSSAI. As result, the indication of the alternative S-NSSAI from the UE to the AMF applies to limited scenarios and it is not necessarily needed.
  • - It is proposed that for a new PDU Session establishment on the old/current S-NSSAI, the AMF determines to apply the new/alternative S-NSSAI and select an SMF accordingly. It is not clear what is the UE behaviour when the UE receives the PDU Session Establishment Accept message with an S-NSSAI different from the requested S-NSSAI. Also, the UE may have applied cell selection using NSAG feature for the old S-NSSAI, however, the new S-NSSAI may be served preferably on another cell/frequency layer. Therefore, it may be more efficient if the AMF rejects the new PDU Session establishment request with an indication to the UE to use the new/alternative S-NSSAI replacing the old S-NSSAI; and then the UE would apply the new S-NSSAI for the PDU Session establishment appropriately.

This solution is not applicable when the matching URSP rule, which triggers the PDU Session establishment, is associated with a single S-NSSAI in the URSP rule.

| +| Solution #5
PDU session handover to a target CN with an alternative S-NSSAI support |

[Mobility use case, scenario 2d] This solution is similar to solution #4 with the addition that the T-AMF may select a different SMF based on the alternative S-NSSAI, if the PDU Session switches to an alternative S-NSSAI. The old SMF triggers PDU Session modification procedure.

It is unclear how (e.g. in step 7) the T-AMF selects a new SMF and in parallel the old SMF triggers PDU Session modification procedure, i.e. it seems there are concurrent SM signalling for the same PDU Session. Also, during the Registration procedure with the T-AMF, it is not clear whether and how the UE includes the alternative S-NSSAI in the Requested NSSAI.

This solution is not applicable when the matching URSP rule, which triggers the PDU Session establishment, is associated with a single S-NSSAI in the URSP rule.

| +| Solution #15
Service continuity in case of Network Slice instance overload |

It is assumed that multiple NSIs are deployed for the same S-NSSAI. The current NSI selection is done without being able to consider load balancing after the UE registration/PDU Session Establishment. The solution describes how the NSI can be changed. When the existing PDU session is decided as to be migrated to another Network Slice instance, the SMF performs PDU Session re-establishment by using the mechanism of SSC mode#2 or SSC mode#3. Then the PDU session establishment request arrives at the AMF, the AMF removes from the UE context the old NSI ID and the AMF can select another NSI.

This solution is not applicable for SSC mode#1. The service continuity is ensured at application layer.

| +| Solution #32
Solution for Network Control for UE Slice Use |

Three options are described in this solution:

  • - Option 1: the UE-initiated procedure, i.e. when the UE establishes a new PDU Session the UE is configured to use the new S-NSSAI. The new S-NSSAI is provided to the UE by the AMF during enhanced UCU procedure indicating that PDU session transfer is requested from an old S-NSSAI (i.e. to be removed) to the new S-NSSAI.
  • - Option 2: AMF-initiated procedure towards SMF, i.e. the AMF notifies the SMF to initiate SSC mode 3 like procedure so that the UE triggers PDU Session Establishment by using target slice. This option is similar to solutions # 2, 3, 4, 5.
  • - Option 3: PCF-initiated procedure, i.e. the PCF notifies the SMF that an alternative S-NSSAI is to be used. As in Option 2, the SMF uses enhanced NAS SM procedure to notify the UE to initiate a new PDU session towards the alternative S-NSSAI.

For the UE-initiated option, it is not clear how to apply the procedure for existing PDU Sessions. If Option 1 and Option 2 are combined, then the result would be similar to Solution #3. Please refer to the evaluation of solution #3.

Option 3 is similar to and solution #40. Therefore similar evaluation would apply as to solution #2 and solution #40.

The impact of overriding of the SSC mode is FFS.

| +| Solution #40
S-NSSAI change decided by PCF |

The main principle is that the PCF determines (e.g. triggered by a SMF or NWDAF) whether the S-NSSAI associated to an ongoing PDU session needs to be changed and which is the alternative/replacement S-NSSAI. Then, the PCF provides the suggested new S-NSSAI to the SMF, and the SMF initiates the modification of the PDU session and notifies the AMF.

The solution addresses scenarios 1b) and 1c).

The PCF for a Session may only serve the original S-NSSAI. It is not clear how the PCF can determine the new S-NSSAI in the roaming case and how the PCF can decide the mapped new S-NSSAI.

| + +| | | +|-----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #41
Network Slice change without service interruption |

The main principle is that the AMF determines the new/alternative S-NSSAI to be used to replace the congested S-NSSAI and:

  • - (option 1) if the current SMF (PSA) supports the new S-NSSAI and the capability to change S-NSSAI, then AMF requests SMF to change to the new S-NSSAI. The SMF initiates SM procedure towards the UE to notify the UE that the S-NSSAI has been changed. This case is similar to solution #2, but solution #41 informs the UE about the S-NSSAI change.
  • - (option 2) if the current SMF (PSA) does not support the new S-NSSAI and/or the capability to change S-NSSAI, the AMF invokes procedure to initiate PDU Session transfer using any SSC mode as described by other solutions (e.g. solutions 3, 4).

The solution addresses scenarios 1b, 1c, 2d.
In option 1, similar as Solution #2, it is not clear what is the behaviour of the UE after receiving the PDU Session Modification request from the SMF indicating change of the S-NSSAI.

| +| Solution #42
Network controlled change to an alternative S-NSSAI |

The main principle is that the AMF (or together with the NSSF or OAM system) determines an alternative S-NSSAI (e.g. S-NSSAI-2) which is available in the current TA and can be used by the UE (e.g. S-NSSAI is not part of the Rejected NSSAI, or NSSAA has failed, etc.). If the NSSF is used to determine the alternative S-NSSAI, the AMF may include a new indication to the NSSF that an alternative S-NSSAI to S-NSSAI-1 is required (this is similar to solution #43). Two options are proposed:

  • - (Option 1) If the S-NSSAI-2 is part of the UE's subscribed S-NSSAIs, it is assumed that the S-NSSAI-2 is part of further RSD the same URSP rule which is used for established PDU Session. The AMF triggers SM procedure towards the SMF to indicate that the PDU Session on S-NSSAI-1 should be released and alternative S-NSSAI may be used. The SMF releases the PDU Session with an indication to the UE to establish the PDU Session on an alternative S-NSSAI.
  • - (Option 2) If the S-NSSAI-2 is not part of the UE's Subscribed S-NSSAIs, the AMF triggers UE network slice reconfiguration procedure (e.g. UCU procedure) in order to send a new Configured NSSAI with a corresponding Mapping of the Configured NSSAI information containing the mapping of S-NSSAI-2 to S-NSSAI-1 (and Mapping Of the Allowed NSSAI). The AMF may wait with the UE reconfiguration when the PDU Session(s) on the old S-NSSAI are inactive.

In Option 1, it is not assured that the URSP rule includes an RSD with S-NSSAI-2 and also, the Option 1 works only when the RSD with S-NSSAI-2 in the URSP rule is configured to match the traffic to be moved in S-NSSAI-1. Therefore, it may be more deterministic if the option 2 is always performed, i.e. the UE should be updated to include in the Allowed NSSAI the S-NSSAI-2 and the mapping of S-NSSAI-2 to S-NSSAI-1. There can be another alternative that S-NSSAI-2 is part of Configured S-NSSAI then legacy behaviour can be used.

In Option 2, in addition to the MM reconfiguration in the UE, in case of existing PDU Session(s) on the old S-NSSAI-1, the AMF may indicate to the SMF that an explicit PDU Session release is required and the SMF releases the current PDU Session with re-establishment indication. This results in more deterministic behaviour that the UE triggers a new PDU Session establishment to the old S-NSSAI with a mapped new S-NSSAI value, i.e. not relying on the UE implicit trigger of PDU Session re-establishment after receiving the new Allowed NSSAI.

Option 2 describes that the S-NSSAI-2 is provided to the UE in the Mapping Of Configured/Allowed NSSAI" information when the S-NSSAI-2 is not within the Subscribed S-NSSAI to UE. However, if the S-NSSAI-2 is part of the Subscribed S-NSSAIs, the Mapping of the Allowed NSSAI information can be also provided to the UE, similar to solutions #3 and #32. The S-NSSAI-2 may not be part of the Subscribed S-NSSAIs in the scenarios where the UE has a single Subscribed S-NSSAI, namely S-NSSAI-1.

| +| Solution #43
Allowed NSSAI Determination in Initial Registration to Support Network Slice Service Continuity |

The AMF queries the NSSF to obtain alternative S-NSSAI for each S-NSSAI of the Allowed NSSAI. The Allowed NSSAI, which is sent to the UE, contains two parts: (1) S-NSSAIs of network slices which UE can access and (2) alternative S-NSSAIs to support slice continuity. The USRP provided to UE contains only the part (1).

It may be inefficient to always query the NSSF about the alternative S-NSSAI for each S-NSSAI from the Allowed NSSAI, since the cases to use the alternative S-NSSAI are rather rare, and therefore, it is considered more efficient to query the alternative S-NSSAI from the NSSF on demand.

This solution does not describe how the UE uses this secondary S-NSSAI in the allowed NSSAI, i.e. whether the existing "Mapping Of Allowed NSSAI" information is used.

| + +Regarding the Network Function, which determines the alternative S-NSSAI to replace the old S-NSSAI, the solutions can be categorized into 2 groups: + +- The AMF determines the alternative S-NSSAI (e.g. solutions #1, #2, #3, #4, #5, #32, #42, #43, etc.). The AMF may optionally use the NSSF services to determine the alternative S-NSSAI (e.g. solutions #42, #43). The AMF may optionally use the PCF services to determine the alternative S-NSSAI (e.g. solutions #2, #41). The AMF may be triggered by the RAN (solution #3) or by the NWDAF.-The PCF determines the alternative S-NSSAI + +(e.g. solution #40). As documented in the#40 in Table 7.X-1, it is unclear how the PCF knows whether the alternative S-NSSAI is supported in the current TA and the RAN node. + +Regarding the impacts to the UE, the solutions can be categorized into the following groups: + +- Solutions without impact to the UE: + - For scenarios where the same S-NSSAI is deployed on multiple NSIs and NSI change is performed (e.g. solution #15): the NSI change is performed seamlessly to the UE, although there is signalling to the UE, but it uses legacy signalling. + - For scenarios where the old and alternative S-NSSAIs are deployed on the same NSI (e.g. solution #1): the principle is that the change of the old S-NSSAI to alternative S-NSSAI is handled within the 5GC and NG-RAN and transparent to the UE. +- Solutions with impact to the UE (e.g. solutions #2, #3, #4, #5, #32, #41, #42, etc.): the UE is informed either by using NAS MM signalling from AMF and/or by using NAS SM signalling from the SMF that the old S-NSSAI is to be replaced by an alternative S-NSSAI. It is beneficial if only a single configuration is performed to the UE. Usually, the NAS SM signalling is meant to influence a single PDU. It appears beneficial to use both: + - NAS MM signalling to include the alternative S-NSSAI in the Allowed NSSAI, the alternative S-NSSAI replaces the old S-NSSAI. + - NAS SM signalling is used to release the PDU Session with an indication to use an alternative S-NSSAI (e.g. as per NAS MM configuration). + +In solutions #4, #5 and #32, it is described that the AMF may provide back off timer for the old S-NSSAI and/or includes the old S-NSSAI in the Rejected NSSAI to prevent the UE requesting the old S-NSSAI due to URSP rule re-evaluation. However, if the old S-NSSAI is included in the Rejected NSSAI or back-off timer is configured, and the URSP rules have only the old S-NSSAI in the RSDs, the UE will not be able to establish a new PDU Session for the matching URSP rule, as the RSDs will be determined as invalid. Such solution is only applicable if the URSP rule(s) or local configuration contains multiple RSDs including the old S-NSSAI and the alternative S-NSSAI. + +NOTE: Given the limitation of this solution (i.e. include the old S-NSSAI in the Rejected NSSAI or using of BOT), it would be beneficial if the old S-NSSAI is excluded from the Allowed NSSAI but included as replaced (or mapped) S-NSSAI value in the Mapping OF Allowed NSSAI (or a new IE), i.e. similar to the mapped S-NSSAI value sent in the existing mapping of Allowed NSSAI. + +## 7.2 Evaluation for KI#2 + +Solutions #6, #7, #16, #17, #18, #19, and #20 proposed for KI#2 can be classified as those based on SoR procedures (#6, #7, #19) and those that are not (#16, #18). Given that this KI is related to a roaming UE, where SoR is already invoked, it is recommended that reuse of existing SoR procedures should be an important evaluation criterion. + +Solution #19 proposes some new SoR information that is slice aware is provided to the UE proactively from the HPLMN in addition to the existing SoR info, to trigger the Slice aware behaviour for specific S-NSSAIs and enable indication of specific separate preferred PLMN lists per S-NSSAI and a way to weight the PLMN selection when multiple such S-NSSAI are impacted. Solutions #17, represent supplemental capabilities that rely on the slice-aware information being already available at the UE. Solution #20 assumes the same existing procedure can be reused. + +Solutions based on SoR procedure impact the UDM in various ways to trigger the UDM to fetch the slice-based SoR information from the SoR AF. These triggers are not compatible in some solutions with the currently specified behaviour of the UDM within the SoR procedure. UDM is currently triggering the interactions with the SoR AF during the UE registration procedure while some of the proposed solutions require the UDM to trigger SoR also after the registration procedure has been completed from UDM point of view based on further new indication from the AMF (#7 option 1). + +The SoR-AF may need to be aware of the subscribed slices. + +## 7.3 Evaluation for KI#3 + +**Solutions related to the improved support of limited AoS not matching deployed TAs:** + +Solution 9 proposes that the limited AoS slices may be based on the configuration of additional secondary TAs in addition to the existing Primary TAs. This requires RAN2/3 to agree defining this concept as outlined in the solution in detail. The companion solution 29 then helps with UEs that need also to be allowed slices associated with AoS matching the existing TAs, then with the partially rejected or partially Allowed S-NSSAIs approach there is good way to form a RA that is encompassing a mix of Primary and Secondary TAs and optimally support this use case. + +Solution 11 bases the limited-service area support on the awareness of slice support at cell level in the system. This requires RAN3 impact as NG-RAN informs slice availability on per-cell basis. The AMF provides Conditional S-NSSAI (i.e. S-NSSAI with TA info the S-NSSAI is available) to the UE. The UE can use the Conditional S-NSSAI without further Registration if location condition is fulfilled. + +Solution 21 uses the validity rules of URSP to indicate only some area can support the service. The AMF does not removes slices from the Allowed NSSAI when the UE is outside of the service area of the slices if the UE is remains current Registration area. + +Solution 23 proposes inclusion of conditional slices in Registration Area Accept response to the UE. This solution is similar to solution 11 when cell level granularity is assumed. + +Solution 26 proposes to use the existing per cell RRM Policy Ratio logic such that cells outside the wanted service area are given only shared/limited or no resources for the concerned network slice, while slice support is maintained on a per TA level. This enables the KPIs to be met while the UE is within the defined service area while when the UE is outside the defined service area still within the TA supporting the S-NSSAI the S-NSSAI is supported but with reduced capabilities and that also enables the possibility to steer the UE back to the defined service area as soon as possible with using existing mechanisms. The solution enables the users to get the requested services and KPIs as per defined SLA, and efficiently get back to service if the UE temporary needs to access a cell outside of the area. The solution does allow the UE to access cells also outside the defined service area if there are resources i.e. it does not prohibit a complete access to the cell. + +Solution 29 is mainly oriented to KI#5 but it potentially with clarifications/changes supports solutions like Solution 9 where additional smaller secondary TA are deployed as it can allow these to be more flexibly added to the RA. This solution proposes procedure enhancements when Partially Allowed / Rejected S-NSSAIs is supported in the network. + +Solution 44 proposes to apply per S-NSSAI Service Area Restrictions. The UDM, RAN and UE needs to support such Service Area Restrictions per S-NSSAI. + +Solution 45 assumes the RAN is configured fit cells in TAs outside the AoS of a S-NSSAI as belonging to a CSAN (constrained service area) where the SLA is not met in the TA. This then results in a differentiated handling of UEs inside and outside the CSAN in the TA. There is no awareness in the UE and CN about the CSAN so this can result in the UE and CN behaving as if the network slice is supported inside the whole TA. + +#### **Solutions related to the support of temporary network slices:** + +Solution 10 that indicates network slices timing information, but this does not remove the need to update sessions with explicit signalling despite the timing information was known in advance. Also, this is driven by UDM or NSSF but there is no signalling instructing the RAN or the RAN itself cannot be the root cause of a slice termination if some slice support is time based in the RAN. + +Solution 11 proposes new temporary slices to be supported conditionally based on timing conditions. The AMF provides Conditional S-NSSAI (i.e. S-NSSAI with timing info the S-NSSAI is available) to the UE. The UE can use the Conditional S-NSSAI if timing condition is fulfilled. + +Solution 21 uses the validity criteria of URSP to indicate when some connections of a slice are no longer available. The UE to re-evaluate these conditions based on existing mechanism. + +Solution 24 proposes to associate a "timing information" allowing per S-NSSAI and per any associated limited time TAs to indicate a start and end time and also a periodicity. It is then proposed that the slices that are associated with time info are released from allowed NSSAI with their PDU sessions at the indicated time silently (i.e. without additional signalling needed) in the system and the UE as applicable (in roaming case only the UE and the used SMF/UPF in HPLMN are impacted if the slices are not actually terminated in the VPLMN network). in addition, this also triggers PDU session level indication of timing, so the sessions are silently released in SMF/UPF without signalling. + +#### **Solutions related to the support of how to gracefully terminate sessions:** + +Solution 8 provides a mechanism to trigger AMF (either via OAM to UDM and then to AMF or via OAM to AMF directly) to terminate PDU Sessions associated with the S-NSSAI subject to be terminated. An order of termination of PDU sessions and specific timing to terminate PDU Sessions are subject to operator's policy. + +Solution 11 proposes new temporary slices to be supported conditionally based on timing conditions. The AMF provides Conditional S-NSSAI (i.e. S-NSSAI with timing info the S-NSSAI is available) to the UE. The UE can use the Conditional S-NSSAI if timing condition is fulfilled. + +Solution 22 is similar to solution 21 but applies to graceful termination. Slice termination time is provided to the UE via validity criteria of URSP. The UE re-evaluate these conditions based on re-evaluation indication provided with the URSP. + +## 7.4 Evaluation for KI#4 + +### Centralized vs. Hierarchical NSACF + +For solution #12, the counting and admission is always handled at ONE central NSACF although the admission requests from users come from different service areas. The central NSACF is able to determine the Number of registrations per service area through configuration of the different service areas in the central NSACF. This enables the central NSACF to distinguish new UE registrations vs UE registrations related to a UE already admitted in another service area. Optionally the information about service area is passed as additional attributes to the NSACF together with the PLMN where the UE is registering. + +For solution #13, the two-tier NSACF architecture enables counting and admission at the NSACF or Primary NSACF. + +### UE registration/ PDU Session establishment handling + +For solution #12 NSAC handling is always at the central NSACF regardless of which service area UE is attached to. + +For solution #13 NSAC handling can be at the local NSACF associated with a service area where UE is attached to. + +### UE Mobility + +For solution #12 as the NSAC is always handled at the central NSACF there is no UE mobility issue. + +For solution #13, two-layer NSACF supports UE mobility. In particular, for the PDU session handling in case of UE mobility, there is no additional request to or check since the PDU session is anchored at the same SMF as before hence no need to interact with NSACF. For the UE counting handling in case of UE mobility, the NSACF associated with a new service area performs the admission together with the primary NSACF to update UE's status if needed. Session continuity is supported. + +For the interaction between NSACF and Primary NSACF, there are two options on how to handle NSAC if the NSACF cannot admit the new UE registration request by itself: + +1. Option 1: Quota based control. The Primary NSACF updates the quota at the NSACF. +2. Option 2: Threshold based control. Threshold is used to control how much percentage of local quota can be used for admission of UEs for initial registration at the NSACF. The primary NSACF can adjust the threshold setting at the NSACF. + +It is proposed to include support for both options and operator can configure which option to use. + +- Solution #14 addresses KI#4 in a proprietary manner. The solution assumes the node handling the quota distribution will be able to distribute quota in a way to ensure that there is never an issue during mobility between multiple services areas. This proprietary solution is similar to what currently exists in Release 17 and for which specific key issue is created to resolve in a more predictable and standardized manner. + +## 7.5 Evaluation for KI#5 + +The related solutions are #11, #23, #25, #26, #27, #28, #29, #30, #31. + +Category 1 is based on allowed S-NSSAI that is indicated to be supported not fully within the RA (hence **Partially/ Conditionally allowed**), where AMF provides for the S-NSSAI a list of TAI(s) where the S-NSSAI is partially/conditional allowed to UE (solution #11, #23, #25, #26, #29). + +Category 2 is based on rejected S-NSSAI that however are supported in some TAs of the RA (hence **Partially/conditionally Rejected**), where AMF provides the (Partially/conditionally) rejected S-NSSAI with a list of TAs TA or new cause to UE (solution #25, #27, #28, #29, #30, #31) with TA(s) where it is supported (or not supported, whichever is applicable) in the RA to the UE (solution #25, #27, #28, #29, #30, #31). + +**Table 7.5-1: Evaluation of KI#5 related principles** + +| | Category 1: | Category 2: | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pros |
  1. Does not require UE to perform registration update for using a requested S-NSSAI not supported in the previous TA.
  2. PDU sessions need not be re-established and disconnected (see solution 29).
  3. provides the support, in MO case, the UE can avoid causing MO access attempts for the slices that are not supported in current TA or provide the TAs where the access attempt can be enabled even without support (assuming UE can be redirected in overlapping TAs).
|
  1. Reuse most of the current procedures. (only Registration procedure is impacted).
  2. Aligned with the current slice management features, where the network determines and updates UE on the Allowed NSSAI, rejected S-NSSAIs, target NSSAI and so on.
| +| Cons |
  1. Features related to slice management such as NSAC will be impacted. (e.g. Cannot be used together if perfect accuracy is required).
  2. Procedures related to PDU Session management will be impacted.
  3. Have impact on Homogenous slice support in RA. AMF will allow the UE to access an S-NSSAI which is only supported in part of the TAs unless additional information is provided where there is overlapping TA and the network can redirect upon a MO access attempt.
  4. The AMF in connected mode can detect when the connectivity of a slice is available or not, but in idle mode the MT services cannot assume where in the RA the UE is so the AMF would page anyhow. There can be RAN impact (e.g. as illustrated by Solution #29) to treat the PDU Sessions.
|
  1. Require UE to perform registration update for using a requested S-NSSAI not supported in the previous TA.
  2. Requires to release and re-establish sessions at mobility in an out the areas where the slice is supported.
  3. When entering the area of support of S-NSSAI, the RA size may need to be reduced to fit the addition of new S-NSSAIs in the Allowed NSSAI.
| + +## 7.6 Evaluation for KI#6 + +There are 9 solutions proposed for the KI#6. + +### 1. Solution #32 (The applicable part for KI#6): + +- Network to deregister network slices for UEs or deregistering the UEs that have PDU sessions that are not active. +- Network to deregister slices for UEs or deregister the UEs that are registering in network slices without establishing any PDUs. +- Enabling network controlled transfer of PDU session from one network slice to another network slice. + +**Comment:** In top two cases it is proposed that UE's slice need to be removed from the allowed list once slice inactivity is detected and the 3rd case enables network controlled transfer of PDU session from one network slice to another network slice addressing the "what" and "how" of the following KI#6 objective: "what the network can request from the UE and how". + +### 2. Solution #33: + +- UE indicates its implicit slice registration deactivation capability during registration and timer is set by network. UE and AMF start the slice-specific implicit registration deactivation timer when there are no PDU sessions with active user plane resources on the slice that is associated with the implicit timer. On the expiry of the timer both UE and AMF will remove the slice implicitly. + +- UE indicates its implicit PDU deactivation capability during registration and timer is set by network UE and SMF start the slice-specific implicit PDU session deactivation timer when the user plane connection is deactivated for the PDU session. On the expiry of the timer both UE and SMF will release the PDU session implicitly. + +**Comment:** Both UE and AMF can remove the slice from allowed list when inactivity is detected in case of no PDU session. But for PDU session with no data transfer only releasing PDU session is not sufficient. UE can remove the slice from allowed list here as well but SMF need to indicate AMF so that AMF will remove the slice as suggested in solution 37. + +### 3. Solution #34: on-demand S-NSSAI. + +- When the Serving PLMN configures the UE with Configured NSSAIs, the Serving PLMN may include an additional indication whether each S-NSSAI in the list of Configured NSSAI is an on-demand S-NSSAI. The UE, upon receiving the list of Configured NSSAI for the Serving PLMN, will not attempt to register for any of the Configured NSSAI that are indicated as on-demand S-NSSAI. Rather, when the UE evaluates URSP rules and an on-demand S-NSSAI appears in the Route Selection Descriptor of a URSP rule, the UE will attempt to register the on-demand S-NSSAI with the AMF. + +**Comment:** Only guiding the UE about when to register a particular slice won't help completely because the same PDU can be inactive. Hence to release the inactive session belong to on-demand slice also need implicit/explicit deactivation mechanism. Another comment is the network can not verify whether the slice registration request sent by the UE is really on demand. + +### 4. Solution #35: propose for the network to deregister the UE from the network slice if the network slice is not utilised for the duration of the slice usage control timer (e.g. no PDU Session on the network slice by the UE). + +- This timer is started at NSACF defined by the operator policy and updates AMF when to deregister the slice. + +**Comment:** This solution may not work completely as the same NSACF may not support both the UE count and PDU count. Also NSACF will not be able to identify the case when PDU session becomes inactive (no data transfer) and it will still treat as PDU established, hence will never indicate to release the slice. Also all the slices may not be subject to NSAC. + +### 5. Solution #36 provides assistance information (e.g. like the kind of registration) for each slice which means whether this slice will be used immediately (immediate registration) or after some duration (proactive registration) or because of default application. + +- The network may reject a S-NSSAIs due to 'proactive registration'. In such case, the UE will only request registration to this S-NSSAI when there is application traffic which needs this S-NSSAI, i.e. URSP rules evaluation process is modified: if an application request data connectivity and the matching URSP rule includes an S-NSSAI which is not in the Allowed NSSAI (but also not rejected due unavailability in the PLMN, RA, or NSAC), the UE can first sends a request to register with the S-NSSAI before processing further RSDs or before the UE concludes that the RSD is invalid. Once the UE is registered with a slice (e.g. due to immediate use), the release of slice and PDU session may be done as suggested in other solutions. + +**Comment:** This solution applies to scenarios where the network dynamically determines (e.g. based on current load or current number of slices/PDU Session close to the threshold when S-NSSAI is subject to NSAC) whether to apply network controlled UE behaviour for the registration to a particular S-NSSAI. This solution avoids the applicability of implicit/explicit deactivation solution when the UE requests e.g. proactive registration, especially when NSSAA or NSAC applies to an S-NSSAI and the inclusion of that S-NSSAI in the Allowed NSSAI would cause additional signalling. + +In scenarios where the network is statically configured that an S-NSSAI is to be used "on-demand", then solution #34 and solution #38 may be more efficient in term of avoiding the UE to request registration to S-NSSAI(s) for 'proactive registration'. + +Another comment is the information sent from the UE may not be trustable so the decision made based on this information may not accurate. "immediate registration" may get higher possibility to be accepted by the network so the UE may always set "immediate registration" and the network cannot verify it is real situation. + +### 6. Solution #37: This solution proposes to deregister the slice once slice inactive is detected by AMF (no PDU session is for certain duration). + +- Similarly to release the PDU session once slice inactive is detected by SMF (PDU inactive case) and then inform AMF so that same slice can be removed as well. This is network based approach where timer is running at AMF & SMF. +- Another approach is provided where timer may be only running at UE and it will indicate to network to remove the slice and release the PDU session once inactivity is detected at UE end. The UE PDU session status and Allowed NSSAI will be always synchronized with network later. + +**Comment:** Solution #37 which is an extension of CN-initiated selective deactivation of UP connection of an existing PDU Session as specified in clause 4.3.7 of TS 23.502 [5] has a unique feature of getting appropriate timers from an AF. With this, the 5GC can learn what a reasonable inactivity time of a given UE type or a UE group using a specific S-NSSAI. By doing this way abrupt releasing or deregistration can be minimized. Solution #37 also supports passing the control of having to deal with a UE inactivity on to a UE which has a required support (e.g., UE behaviour control policies). This way it relieves a serving AMF or SMF load. Further, network can still monitor the UE slice usage if needed, e.g. for malformed UE. + +#### 7. Solution #38: + +1. Whether to register with all the Slices in the Configured NSSAI for the PLMN or whether to register when a PDU session needs to be established in the network slices or whether to register with a list/subset of slices from configured-NSSAI irrespective of whether a PDU session is to be established or not. +2. Whether to establish all the PDU sessions configured in the RSDs or to establish them based on the need to use these by applications or whether to establish PDU sessions to specific set of DNNs irrespective of whether an application needs it or not. +3. Time to release a PDU session after no application is detected in the UE to need to use the PDU session This time, for example, can be immediately after use is over, or the PDU session can remain Idle up to a maximum time. +4. Time to deregister from a network slice since the last PDU session is released which was using the network slice. +5. Policy can be configured by HPLMN and VPLMN authorized by HPLMN. + +**Comment:** UE support is needed for this solution to work. This solution is not requiring an implicit deactivation timer based on traffic monitoring as the UE releases the session when no Application is detected to need a PDU sessions. how this is detected can be left to implementation of the UE (e.g. no application has a socket on the IP address of a PDU session or a logical association with the PDU sessions. the Modem layer is expected to be able to receive such indications from the OS layer). the release is explicit (i.e. with signalling). the advantage of this approach is that some applications may not be active for a long time if they are just expecting notifications. with an explicit timer approach the PDU session may be releases needlessly and with that the related slice if this was the last PDU session on the slice. + +#### 8. Solution #39 It proposes to steer the UE to another preferred slice by PCF updating the URSP rules once the originally intended slice is reaching quota limit. Based on the operator policy, the URSP will be updated only for the list of UEs configured at PCF. + +**Comment:** This solution works only for slices which are subject to NSAC. + +#### 9. Solution #40 It extends the PDU session inactivity mechanism in 5GS to PDN connection in EPS. + +- This solution works for both implicit deactivation/explicit deactivation based solution. + +**Comment:** This is not a standalone solution and complement any supported solution (be it implicit deactivation or explicit deactivation or both). + +There are broadly two categories of solutions which addresses the KI#6 of proper utilization of network slices by UE. + +**In the first category**, the usage of slices by UEs are considered and then based on whether slices are in use or not deactivation is triggered. + +1. **UE impacting with UE configuration:** In this case the UE indicates its capability of handling the configuration information or implicit deactivation to network and then network updates the corresponding configuration information or implicit timers to UE. the UE configuration runs at UE only and causes sessions to be released and slices to be deregistered explicitly based on the configuration information. the configuration information may also indicate which slices are to be kept registered at all times and which can be activated based on + +need/demand. The implicit registration slice deactivation timer runs at both UE & AMF and after the expiry of the timer both will remove the slice from the allowed list (no PDU session is established during this time period). Similarly implicit PDU session deactivation timer runs at both UE & SMF/SMF+PGW-C and after the expiry of the timer (PDU session is inactive) both will release the PDU session/PDN connections. + +2. **Network based on slice deactivation and explicit PDU session deactivation:** In this case the UE does not need any new capabilities. The explicit registration slice deactivation timer runs at AMF and after the expiry of the timer it will remove the slice from the allowed list (no PDU session is established during this time period). Similarly explicit PDU session deactivation timer runs at both UE & SMF/SMF+PGW-C and after the expiry of the timer (PDU session is inactive) it will release the PDU session/PDN connections. +3. **Timer setting,** the timer is used to monitor the PDU session/Allowed NSSAI usage as per point 2. To avoid abrupt PDU Session release or slice deregistration (i.e., removing an S-NSSAI from Allowed-NSSAI), the timer is set by the AF and stored at the UDM. + +**In the second category,** network will configure policy for some slices which will indicate whether the slice need to be registered and present all the time irrespective of the any corresponding PDU session is there or not. The following sub-categories may apply: + +1. Static configuration per some slices: the network may indicate to the UE whether to register whenever the UE wants or only when it wants make one PDU session using that slice. This indication can be provided by the network either in the configured NSSAI or in URSP. +2. Dynamic configuration per network slice: the network may determine based on current conditions whether to apply network controlled UE behaviour for the registration to a particular S-NSSAI. The UE indicates the type of registration to an S-NSSAI (e.g. immediate use, proactive or default). The network can reject network slices for 'proactive registration' and the UE will initiate registration to such slices only when there is matching application traffic. + +Solutions to address the aspect of KI#6 to enable network-controlled behaviour for the scenario where there is an existing PDU session, can be categorized as AMF initiated and PCF initiated mechanisms. In both approaches the network controls the transfer of PDU session from one network slice to another network slice and the difference is in the core network NF that triggers the transfer. + +--- + +## 8 Conclusions + +### 8.1 Conclusions for KI#1 + +The following principles are concluded for the normative work. + +NOTE 0: The IE names for the alternative S-NSSAI and other new information in the conclusion is to be determined during normative phase. + +- 0) The trigger in the AMF to replace a currently used S-NSSAI with an alternative S-NSSAI is either based on local configuration (e.g. based on trigger from OAM) or based on AM PCF/NSSF notification. The UE capability to support this feature is a prerequisite for the execution of the optimizations in this conclusions. + +NOTE 1: The SBI service used for AM-PCF notification will be determined in normative phase. + +- 1) The AMF determines the alternative S-NSSAI to be used to replace the old S-NSSAI. The AMF may interact with the AM PCF and/or with the NSSF to determine the alternative S-NSSAI. The alternative S-NSSAI may or may not be part of the Subscribed S-NSSAIs of the UE. The Subscribed S-NSSAIs of the UE are not updated for the purpose of KI#1. + +NOTE 2: The SBI service used for AM-PCF notification will be determined in normative phase. + +- 2) In case of a same S-NSSAI associated with multiple NSIs and a NSI can no longer be used, the NSI is no longer considered for binding S-NSSAI at the AMF and NSSF and when a PDU session establishment request from the UE arrives at the AMF, the AMF and NSSF performs NSI re-selection without considering the old NSI as candidate NSI and the AMF selects another NSI +- 3) In cases where the old S-NSSAI and the alternative S-NSSAI are associated with the same NSI, the mechanisms in bullet 4) is reused to transfer the PDU session to alternative S-NSSAI. + +- 4) In cases where the old S-NSSAI is replaced by an alternative S-NSSAI deployed on a different NSIs, the following principles apply: + - a) The AMF performs UE MM configuration update (e.g. UCU procedure) to include the alternative S-NSSAI in the Allowed NSSAI and/or in the Configured NSSAI, if not included yet. The AMF provides information that the alternative S-NSSAI is associated with a replaced/mapped value to the old S-NSSAI in both roaming or non-roaming case; and independent whether the alternative S-NSSAI is part or not part of the Subscribed S-NSSAIs. + +NOTE 3: Whether to use existing Mapping Of Allowed NSSAI or use an alternative IE is to be determined at normative phase. + +- b) For a new PDU Session establishment request from the UE only on the old S-NSSAI (for UEs without existing PDU session and not updated with alternative S-NSSAI in step 4a): + - The AMF proceeds with the PDU Session establishment to the SMF of the alternative S-NSSAI, and the AMF indicates the alternative S-NSSAI to the SMF and the SMF proceeds with the PDU Session establishment on the alternative S-NSSAI. The SMF sends the alternative S-NSSAI in the PDU Session Establishment Accept message so the UE knows the PDU session is associated with both the alternative S-NSSAI and old S-NSSAI. + - The AMF update the UE configuration according to 4a). +- c) For an existing PDU Session transfer from the old S-NSSAI to an alternative S-NSSAI, in order to ensure service continuity: + - The AMF update the UE configuration according to 4a). + - The AMF notifies the current SMF, e.g. by triggering Nsmf\_PDUSession\_UpdateSMContext service operation, that the PDU Session is to be relocated to an alternative S-NSSAI and indicates the alternative S-NSSAI. + - The SMF may determine that the PDU session needs to be retained and the slice resource cannot be repartitioned. In this case the SMF may send the alternative S-NSSAI to the UE in the PDU Session Modification Command, to the UPF in the N4 message and to the RAN in N2 message. + - The SMF may determine that the PDU session needs to be re-established, In this case, the SMF sends to the UE either PDU Session Modification Command (if the PDU Session is of SSC mode 3) or PDU Session Release/Modification Command (if the PDU Session is of SSC mode 1 or 2) and indicates the alternative S-NSSAI to the UE to trigger the re-establishment of the PDU Session the alternative S-NSSAI. + - The UE triggers a new PDU Session Establishment procedure to establish a PDU Session as follows: + - The PDU Session establishment request includes the alternative S-NSSAI together with the old S-NSSAI (similar as to use the mapped S-NSSAI value of the VPLMN when applying the RSD matched to the HPLMN S-NSSAI). + +## 8.2 Conclusions for KI#2 + +The following principles are concluded for KI#2. + +1. A slice based SoR mechanism to deliver enhanced slice-aware SoR information will reuse the current SoR mechanism defined in TS 23.122 [7] for SoR information delivery. The encoding of the enhanced slice-aware SoR information is in the CT1 remit. +2. The SoR container (which is used also to carry the enhanced slice-aware SoR information) from the UDM to the UE is security protected. + +NOTE 1: SA WG3 may further define any upgrade of security protection mechanism of the SoR mechanism, if it was needed. + +3. UDM requires knowing the support of the enhanced SoR information by the UE to deliver the enhanced slice-aware SoR information to the UE. + +NOTE 2: Whether the UE provides additional assistance information (refer TR 23700-41) and which kind of additional assistance information need to be discussed in CT1. Any UE assistance information is transparently forwarded by UDM to SoR-AF during the triggering procedure by UDM. The SoR-AF should not attempt to fetch any assistance information if not provided by the UE. UE assistance information can either implicitly or explicitly indicate that the UE supports slice based SoR feature. + +4. Only a UE supporting slice based SoR feature can receive the enhanced slice-aware SoR information via UDM, the enhanced slice aware information include preferred PLMNs for specific S-NSSAIs in the UE subscription (a preferred PLMN list may be also be a single PLMN that is known by HPLMN to support the S-NSSAI, or a list of PLMNs in preference order that differs from the order of the basic SoR information that is also provided). + +NOTE 3: It is left to CT1 to decide whether to apply weighted approach or alternative approach for the PLMN selection procedure, when more than one S-NSSAI has slice aware information and all these S-NSSAIs are needed by the UE + +5. The UE will perform the PLMN selection based on the received enhanced slice-aware SoR information. + +6. As for the current SoR information, It shall be possible for the HPLMN to update the enhanced slice-aware SoR information when it is required by HPLMN, e.g., change in the UE subscription or other HPLMN trigger. + +7. The SoR AF can take into account Subscribed S-NSSAIs of the UE. the SoR AF can get Subscribed S-NSSAIs using existing UDM services. This can also be used to generate enhanced slice-aware SoR information and legacy SoR information. + +## 8.3 Conclusions for KI#3 + +**For support of limited AoS slices not matching deployed TAs it is proposed that:** + +- Reconfiguration of TAs while keeping the uniform support of S-NSSAIs in cells within the TA unchanged, but if an operator do not want to change the TA borders, the operator configures the cells of a TA that are outside AoS to have no or limited resources using existing NG-RAN OAM configuration. + +- S-NSSAI availability policies with the validity set to location information (e.g. a set of cells, or combination of cells and TAs), that are sent to the UE. The UE uses the policies and when the availability are not valid, the UE considers the S-NSSAI to be 1) not registered or 2) registered while no UP are allowed to be activated based on information in the received policy. + +NOTE 1: Whether S-NSSAI validity policies is sent to the UE in the Configured NSSAI or separate is to be determined during normative phase. + +NOTE 2: How the handover can be optimized to prevent the UE from leaving the slice service area (or entering into the slice service area) will be considered during normative phase based on RAN WG feedback. + +NOTE 3: The AMF enforcement of the S-NSSAI availability policies e.g. when the UE does not support the policies will be described during normative phase based on AMF subscribing to AoI. + +**For improved support of temporary network slices:** + +**Option 4: AMF is configured with S-NSSAI availability policies that the AMF sends to the UE:** + +- AMF is configured with S-NSSAI availability policies that the AMF sends to the UE. Availability validity can be time and location. The UE uses the policies and when the availability are not valid, the UE considers the S-NSSAI to be 1) not registered or 2) registered while no UP are allowed to be activated based on information in the received policy. + +NOTE 4: Whether S-NSSAI validity policies is sent to the UE in the Configured NSSAI or separate is to be determined during normative phase. + +NOTE 5: The AMF enforcement of the S-NSSAI availability policies e.g. when the UE does not support the policies will be described during normative phase. + +NOTE 6: relationship with KI#5 will be determined during the normative phase. + +NOTE 7: Temporary network slices does not mean that the network slices are decommissions and created as per the timing information, but the network slices are not meant to be available for use by the UE. + +**For the graceful and gradual termination aspect:** + +- When a slice is to be decommissioned, and become no longer available for UEs in a network slice by a known time the operator determines, the PDU Sessions of the slice should be gracefully (for supporting UEs of the timing information) and gradually released (for no supporting UEs of the timing information): +- If the UE supports the handling of timing information indicating information on time of network slice availability, the network may provide the timing information to the UEs so the UE knows in advance when a network slice ceases to be supported. In this case, the UE can take the necessary actions to prepare for the slice not becoming available. + +NOTE 8: Normative phase will determine whether the timing information is sent as information to the UE or the UE is expected to apply explicit logic. + +- In addition, the AMF, for non-supporting UEs and for the case of UE not performing any actions despite of the timing information provided by the network, may be triggered by the OAM to start gradually terminating PDU Session(s) associated with S-NSSAI subject to be terminated. The AMF releases PDU Session(s), associated with the S-NSSAI subject to be terminated, based on operator's policy available at the AMF. + +NOTE 9: Coordination with SA5 is required during normative phase. + +NOTE 10: Whether graceful release can also be achieved for non supporting UEs is left for normative phase. + +## 8.4 Conclusions for KI#4 + +For operators implementing a single centralized solution, solution 12 is proposed. The central NSACF reuses the Release 17 NSACF extended with optional attributes for the AMF to convey the Service Area and PLMN during the Update operation. The Release 17 NRF discovery procedure is to be extended to allow the central NSACF to register multiple Service Areas to be supported by central NSACF + +For operators implementing hierarchical NSACF architecture as defined in solution 13, there are two types of NSACF, i.e. the Primary NSACF and NSACF. An NSCAF can be configured to support quota-based control (option 1), or UE admission threshold based control (options 2) as described below + +- Option 1: UE admission quota based control, admission of any UE is accepted up to the local maximum number. +- Option 2: UE admission threshold based control, admission of new UEs registering in for the first is accepted only below UE admission threshold. + +The following applies to both options: + +- 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). +- The Primary NSACF registers its NF profile to the NRF with the service area information as the global service Area. A consumer NF may utilise the NRF to discover the central NSACF by using the serving area information set to "global", and additional home PLMN ID information in roaming case. +- To enable Primary NSACF to update the local maximum number and established PDU session for NSCAF configured with option (1), NSACF subscribes to Primary NSCAF for that purpose. The primary NSACF updates the NSACF with the needed information via an explicit NOTIFY or in responses to requests initiated from the NSACF. +- To enable Primary NSACF to update the new UE admission threshold for NSCAF configured with option (2), NSACF subscribes to Primary NSCAF for that purpose. The primary NSACF updates the NSACF with the needed information via an explicit NOTIFY or in responses to requests initiated from the NSACF. +- The Primary NSACF subscribes from the NACF that it is in contact with to obtain the number of registered UEs or established PDU sessions admitted at the NSACF. + +### NSAC for the maximum number of UEs + +For NSACF supporting option 1, if the local maximum number has been reached, or the UE entry is managed by the Primary NSACF, the NSACF interacts with the Primary NSACF for the delegation of NSAC request for a UE. + +For NSACF supporting option 2, if UE admission is at or above the threshold level stored at the NSACF, NSACF immediately rejects UEs registering in for the first time. If the local maximum number has been reached but the registering UE already admitted in a previous service area, or the UE entry is managed by the Primary NSACF, the NSACF interacts with the Primary NSACF for the delegation of NSAC request for a UE. + +The Primary NSACF supports the following capabilities depending on the NSACF configuration it interacts with: + +- Returning a new updated local maximum number for the NSACF if the NSACF is configured to support that feature. Or +- Returning a new updated UE admission threshold if the NSACF is configured to support that feature. + +The Primary NSACF handles and stores entries only related to UEs that are already admitted in an existing service area but cannot be admitted in the new service area due to no remaining local maximum number. + +#### **NSAC for the maximum number of PDU session** + +The NSACF interacts with the Primary NSACF when the local maximum number is exceeded. + +The Primary NSACF supports the following capabilities: + +- Returning a new updated local maximum number for the NSACF. + +To enable Primary NSACF to update the local maximum number PDU session, NSACFs subscribes to Primary NSCAF for that purpose. At any time, in the response to a request from NSACF, or via a Notification, the Primary NSACF can update the local maximum number of PDU sessions per the current registered number of PDU session. + +#### **Support for NSAC with HPLMN while Roaming** + +VPLMNs shall support NSAC with HPLMN if the SLA requires that. A VPLMN can be configured or can fetch the applicable NSAC admission mode from HPLMN (UDM). + +If the NSAC admission mode is VPLMN, NSAC admission is determined by the VPLMN. Otherwise if the NSAC admission mode is HPLMN, NSAC admission is determined by the HPLMN. + +In this case every AMF in this VPLMN performs NSAC admission for the number of registered UEs with the HPLMN central or primary NSACF for all related inbound roamers from that HPLMN when they register in this VPLMN. The AMF discovers the HPLMN primary or central NSACF or optionally be configured with the needed information. + +Additionally, every SMF in this VPLMN performs NSAC admission for the number of LBO PDU sessions with the HPLMN central or primary NSACF for all related inbound roamers from that HPLMN when they initiate an LBO PDU session. The SMFs discovers the HPLMN primary or central NSACF or optionally be configured with the needed information. + +As mentioned before, AMFs and SMFs identifies the NSAC mode at UE registration and PDU session establishment from the UDM AMF and SMF data respectively. + +#### **Support for HPLMN Delegated NSAC Mode while Roaming** + +In this HPLMN delegated NSAC mode, HPLMN delegates NSAC to the VPLMN, both for number of registered UEs and the number of LBO sessions. + +NSAC NFs, i.e. NSACF, performing admission in the VPLMN need to acquire from the HPLMN central or primary NSACF the applicable quota for the number of registered UEs and/or the number of LBO sessions before or triggered by the NSAC admission request. In order to acquire the maximum number of registered UEs, and maximum number of LBO PDU sessions for admission for inbound roamers for an HPLMN, every NSAC in this VPLMN subscribes to the VPLMN primary NSACF for this information. Subsequently, the VPLMN primary or central NSACF subscribes to the HPLMN central or primary NSACF for this information. If re-distribution of quota is required in the VPLMN amongst multiple NSACs than this is handled by the primary NSACF in VPLMN with no involvement from the HPLMN. + +In this case every AMF in this VPLMN performs NSAC admission for the number of registered UEs with NSACF serving that service area in VPLMN for all related inbound roamers when they register in this VPLMN. + +Additionally, every SMF in this VPLMN performs NSAC admission for the number of LBO PDU session with NSACF serving that service area in VPLMN for all related inbound roamers when they initiate an LBO PDU session. + +If the NSAC admission mode is determined in the HPLMN, when the applicable quota to the VPLMN is exceeded, the primary or central NSACF in VPLMN interact with HPLMN Primary NSACF to determine whether the NSAC admission is accepted or rejected unless forbidden by the SLA. This applies the same principles as in the non-roaming case. + +As mentioned before, AMFs and SMFs identifies the NSAC mode at UE registration and PDU session establishment from the UDM AMF and SMF data respectively. This information is passed subsequently to the NSACF during NSAC admission. + +#### Support for NSAC in VPLMN while Roaming + +Release 18 enables NSACs in the VPLMN, in this mode, where the VPLMN performs admission, by fetching from the HPLMN primary or central NSACF the maximum number of registered UEs as well as the maximum number of PDU sessions to enforce. However, in this case, the VPLMN rejects any additional requests when the applicable quota is consumed. + +NOTE: NSACs in VPLMN can also be preconfigured with the maximum number of registered UEs as well as the maximum number of PDU sessions to enforce with no fetching required. + +## 8.5 Conclusions for KI #5 + +The following principle is proposed to be the conclusion for normative work: + +#### Partly rejected S-NSSAI: + +- AMF can provide information to the UE enabling the UE to be able to register an S-NSSAI that is rejected S-NSSAI for the RA, when the UE moves to a TA supporting the S-NSSAI. The AMF can provide additional IE to the UE e.g. Partially rejected S-NSSAI in the registration procedure and the UE configuration update procedure if the UE indicates that it supports this feature. The UE shall be able to request a rejected S-NSSAI, by initiating a registration update procedure, in a supported TA based on the supported/not supported TA information associated with this S-NSSAI. The current concept of Allowed NSSAI and uniform support of it in UE's RA is not impacted by this feature based on indication of where in the RA certain rejected S-NSSAIs are supported/not supported. In this approach, the Allowed NSSAI is still uniformly supported in the RA. + +NOTE 1: IE name to use is to be determined during normative phase. + +#### Partly allowed S-NSSAI: + +- If a requested S-NSSAI is not supported in the current TA but supported in other TAs part of the RA, or the requested S-NSSAI is supported in the current TA but not supported in all other TAs of the RA, the AMF (for supporting UEs) may indicate to the UE that some S-NSSAIs are allowed only in some TAs of the RA by indicating the TAs where these are supported and also registered. If so, the UE assumes it can use the connectivity for the slices in the TAs where it is indicated to be supported. In this approach, the Allowed NSSAI is still uniformly supported in the RA but the additional IE sent to the UE e.g. Partially Allowed S-NSSAI is not uniformly supported in the RA. The AMF sends the Partially/Conditionally Allowed S-NSSAI to NG-RAN in the same messages as the Allowed NSSAI is sent. + +NOTE 2: The RAN impacts will coordinated with RAN3 during the normative phase. + +NOTE 3: IE name to use is to be determined during normative phase. + +- Whether to apply one of the two options is a per S-NSSAI decision based on AMF policy, both options can be supported in a PLMN and can be applied simultaneously for one UE for different S-NSSAIs. + +NOTE 4: Whether to enable Partially/Conditionally Allowed S-NSSAI is based on network configuration and operator policies configured in the AMF and the AMF can also consider whether S-NSSAI is subject to e.g. NSAC. + +## 8.6 Conclusions for KI #6 + +The following conclusions are proposed for KI#6: + +For a supporting UE, the following principles are agreed for normative work: + +- The network can configure slice-specific policies; more specifically, it is proposed to use PCF or local AMF configuration/policy for handling network policies related to S-NSSAIs subject to network control during the registration procedure. These policies can include one or more of the following components: + - Whether the registration needs to be performed based on demand/usage or configuration. This indication can be configured by HPLMN and/or VPLMN (if authorized by HPLMN, based on e.g. UDM indication) and can be provided via existing UE configuration procedures e.g. together with the Configured NSSAI. + - Inactivity timer after a slice is implicitly deregistered if no PDU sessions are present. This applies only for slices that are established on-demand. The timer runs at both the UE and the AMF. The timer is provided by the HPLMN or the VPLMN (AMF policy) during the Registration procedure together with the Configured NSSAI. The timer can be per S-NSSAI. + +NOTE: In normative phase it will be checked whether problems of misalignment between UE and network can occur and if so whether explicit release should be used instead. + +- For EPS case, the PDN connections have similar handling to PDU sessions in 5GS. +- If the UE indicates it support this specific feature as defined in KI#1, it is proposed to enable the network to request the UE to transfer all PDU sessions from one S-NSSAI to another S-NSSAI. +- In normative phase any reuse of Rel-18 UE policy work outcomes will be explored. + +In addition to the above, the following is also agreed to proceed to normative work: + +- The AMF determines to deregister the network slice if no PDU session is using the slice for a determined network slice deregistration time which runs only at the AMF. +- The SMF determines to release the PDU session if no user data is sent over the PDU session for a determined PDU session inactivity timer which runs only at the UPF. The AMF may also removes the S-NSSAI from the Allowed NSSAI based on indication from the SMF after completion of the PDU Session Release procedure if it does not find any other PDU session for the same slice over related access type. +- PDU session inactivity timer, which cause the release of a PDU session if no data was transmitted or received for the duration of the inactivity timers, or Network slice Deregistration timer which cause the removal of a given S-NSSAI from an Allowed NSSAI after the last PDU session in the network slice was released, may be set by authorized AF (if PLMN allows and for slices solely dedicated for the AF and not shared with others) and stored in the network (e.g. UDM or PCF per S-NSSAI/DNN. The timer from network can be obtained by an AMF and SMF respectively at the time of UE registration and PDU session establishment. +- For EPS case, the PDN connections have similar handling to PDU sessions in 5GS. + +## Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------|------------|----|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149E | S2-2200563 | - | - | - | Skeleton | 0.0.0 | +| 2022-09 | SA#97-e | SP-220821 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.0.0 | +| 2022-11 | SA#98-e | SP-221109 | - | - | - | 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-46/raw.md b/raw/rel-18/23_series/23700-46/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a57710e79d95bb07a6a0776d3091996b49e69b78 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/raw.md @@ -0,0 +1,1362 @@ + + +# 3GPP TR 23.700-46 V18.0.0 (2023-03) + +*Technical Report* + +**3rd Generation Partnership Project; +Technical Specification Group Services and System Aspects; +Study on 5GS Deterministic Networking (DetNet) interworking +(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 ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms and abbreviations ..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architecture Assumptions..... | 8 | +| 5 Key Issues ..... | 9 | +| 5.1 Key Issue #1: 5GS DetNet node reporting..... | 9 | +| 5.1.1 Description ..... | 9 | +| 5.2 Key Issue #2: Provisioning DetNet configuration from the DetNet controller to 5GS ..... | 9 | +| 5.2.1 Description ..... | 9 | +| 6 Solutions..... | 9 | +| 6.1 Solution #1 for Key Issue #1: Node and neighbour information reporting to DetNet controller ..... | 9 | +| 6.1.1 Introduction ..... | 9 | +| 6.1.2 Functional Description ..... | 10 | +| 6.1.3 Procedures ..... | 11 | +| 6.1.4 Impacts on existing entities and interfaces..... | 12 | +| 6.2 Solution #2 for Key Issue #1: Network function enhancement to support 5GS DetNet node reporting ..... | 13 | +| 6.2.1 Introduction ..... | 13 | +| 6.2.2 Functional Description ..... | 13 | +| 6.2.3 Procedures ..... | 14 | +| 6.2.4 Impacts on existing entities and interfaces..... | 15 | +| 6.2.5 Solution evaluation..... | 15 | +| 6.3 Solution #3 for Key Issue #2: Mapping from DetNet YANG model to 3GPP configuration ..... | 15 | +| 6.3.1 Introduction ..... | 15 | +| 6.3.2 Functional Description ..... | 16 | +| 6.3.3 Procedures ..... | 18 | +| 6.3.4 Impacts on existing entities and interfaces..... | 19 | +| 6.4 Solution #4 for Key Issue #2: DetNet Flow Mapping ..... | 19 | +| 6.4.1 Introduction ..... | 19 | +| 6.4.2 Functional Description ..... | 19 | +| 6.4.3 Procedures ..... | 20 | +| 6.4.4 Impacts on existing entities and interfaces..... | 21 | +| 6.5 Solution #5 for Key Issue #2: Provisioning DetNet traffic to 5GS parameters ..... | 21 | +| 6.5.1 Introduction ..... | 21 | +| 6.5.2 Functional Description ..... | 21 | +| 6.5.3 Procedures ..... | 23 | +| 6.5.3.1 DetNet controller in a different domain from the 5GS ..... | 23 | +| 6.5.3.2 DetNet controller in the same trust domain as the 5GS..... | 24 | +| 6.5.4 Impacts on existing entities and interfaces..... | 24 | +| 6.6 Solution #6 for Key Issue #2: Solution for provisioning DetNet configuration from the DetNet controller to 5GS ..... | 25 | +| 6.6.1 Introduction ..... | 25 | +| 6.6.2 Functional Description ..... | 25 | +| 6.6.3 Procedures ..... | 26 | +| 6.6.4 Impacts on existing entities and interfaces..... | 27 | +| 6.6.5 Solution evaluation..... | 27 | +| 6.7 Solution #7 for Key Issue #2: Detnet configuration mapping to 5GS parameters..... | 28 | +| 6.7.1 Introduction ..... | 28 | +| 6.7.2 Functional Description ..... | 28 | +| 6.7.3 Procedures ..... | 29 | +| 6.7.4 Impacts on existing entities and interfaces..... | 30 | + +| | | | +|--------------------------------------|--------------------------------------------------------------------------------------------------|-----------| +| 6.8 | Solution #8 for Key Issues #1 and #2: 5GS DetNet Node IP Operation, Management and Exposure..... | 30 | +| 6.8.1 | Introduction ..... | 30 | +| 6.8.2 | Functional Description ..... | 31 | +| 6.8.3 | Procedures ..... | 33 | +| 6.8.4 | Impacts on services, entities and interfaces..... | 34 | +| 7 | Conclusions..... | 35 | +| 7.1 | General ..... | 35 | +| 7.2 | Key Issue #1: 5GS DetNet node reporting..... | 35 | +| 7.3 | Key Issue #2: Provisioning DetNet configuration from the DetNet controller to 5GS ..... | 36 | +| Annex A: Change history ..... | | 37 | + +# 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 objective of this Technical Report is to study whether and how to enable 3GPP support for DetNet such that a mapping is provided between the central DetNet controller entity (as defined in IETF) and the 5G system. Mapping involves translation of DetNet traffic profile and flow specification to 5GS QoS parameters and TSCAI. The study also considers which information needs to be exposed from the 5G system to the DetNet controller. + +The study scope assumes the following: + +- Only IP based DetNet is in the scope of the work; MPLS based DetNet is out of scope. +- DetNet over Ethernet TSN is not in the scope of the work as it can be supported based on existing 3GPP and IETF standards. +- It is out of scope to support for edge DetNet node functions in the 3GPP network. + +# --- 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] IETF RFC 8655: "Deterministic Networking Architecture". +- [3] IETF RFC 8939: "Deterministic Networking (DetNet) Data Plane: IP". +- [4] IETF RFC 9016: "Flow and Service Information Model for Deterministic Networking (DetNet)". +- [5] draft-ietf-detnet-yang: "Deterministic Networking (DetNet) YANG Model". +- [6] IETF RFC 8344: "A YANG Data Model for IP Management". +- [7] IETF RFC 8343: "A YANG Data Model for Interface Management". +- [8] IETF RFC 6241: "Network Configuration Protocol (NETCONF) ". +- [9] IETF RFC 8040: "RESTCONF Protocol". +- [10] IETF RFC 6021: "Common YANG Data Types". +- [11] IETF RFC 8349: "A YANG Data Model for Routing Management (NMDA Version)". +- [12] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2". +- [13] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [14] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [15] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3". + +# --- 3 Definitions of terms and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] apply. + +## 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]. + +| | | +|--------|--------------------------| +| DetNet | Deterministic Networking | +|--------|--------------------------| + +# --- 4 Architecture Assumptions + +The study has the following architecture assumptions: + +- DetNet may be used in combination with time synchronization mechanisms as defined in Rel-17 but does not require usage of these mechanisms. +- Since synchronization mechanisms that can be used are out of the scope in IETF DetNet specifications, the time synchronization framework in Release 17 is not modified for this study. +- Existing 3GPP routing mechanisms can be re-used for DetNet; no new routing function in the 3GPP system is to be defined. +- The existing filtering mechanisms can be re-used in the UE and in the UPF to identify the traffic for QoS differentiation. +- It is out of scope to extend 3GPP multicast mechanisms, but the existing multicast capabilities can be re-used for DetNet communications. +- IP based DetNet traffic is carried in PDU Sessions of IP type. +- The mapping functionality for DetNet is realized in the TSCTSF. +- The solutions should reuse the functionality of the TSC framework defined in Release 17 where applicable. +- The study considers 5GS acting as a DetNet node in the DetNet domain. Use cases where the 5GS acts as a sub-network (see RFC 8655 [2] clause 4.1.2) are also possible but do not require 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 already supported based on 3GPP Release 16-17. +- The study considers the DetNet forwarding sub-layer related functions that are applicable to the 5GS. For the IP case according to RFC 8939 [3] clause 1, no service sub-layer function needs to be defined. +- The granularity of the 5GS DetNet node is per UPF for each network instance. +- The solutions shall not have any 5G AN and UE impacts + +The 5G System is extended to support the following: + +- The UE is part of the 5GS logical DetNet Node, thus is not a DetNet Node or End System on its own + +The reference architecture is shown as below: + +**Editor's note:** It is FFS whether the NEF can be used between the DetNet controller and the TSCTSF. + +**Editor's note:** The protocol interactions between TSCTSF and the DetNet controller are FFS. + +# --- 5 Key Issues + +## 5.1 Key Issue #1: 5GS DetNet node reporting + +### 5.1.1 Description + +Clause 4.8 of IETF RFC 8655 [2] describes the Resources, Capabilities, and Adjacencies which may be reported by DetNet node to DetNet CPF (Controller Plane Function). + +For this Key Issue, the following areas should be studied: + +- which information the 5GS needs to report; +- how the 5GS collects the information to report. + +The solution should clarify whether the NEF could be deployed between the TSCTSF and the DetNet controller. + +## 5.2 Key Issue #2: Provisioning DetNet configuration from the DetNet controller to 5GS + +### 5.2.1 Description + +A DetNet controller may provide DetNet configuration as defined in ietf-detnet YANG module to the 5GS acting as a DetNet node. This key issue will study how to map the DetNet configuration. + +The DetNet controller communicates with the 5G system through TSCTSF. DetNet Flow-Related Parameters may be provided by the DetNet controller as defined in draft-ietf-detnet-yang [5]. The TSCTSF should map the parameters provided by the DetNet controller into 5G QoS parameters or other parameters e.g. TSCAI to configure 5GS flows for the DetNet traffic. + +This KI will address: + +- Which parameters provided by the DetNet controller should be mapped into which 5G parameters. +- How the 5GS finds the PDU Sessions corresponding to the given DetNet configuration. +- What mechanisms are used in 5GS to configure the system according to the configuration provided by the DetNet controller. + +The solution should clarify whether the NEF could be deployed between the TSCTSF and the DetNet controller. + +# --- 6 Solutions + +## 6.1 Solution #1 for Key Issue #1: Node and neighbour information reporting to DetNet controller + +### 6.1.1 Introduction + +The 5GS may report information about the node and its interfaces which correspond to the PDU Sessions (device side) and UPF interfaces (network side). The reporting from the TSCTSF to the DetNet controller also referred to as CPF, Controller Plane Function) is carried out using IETF protocols. + +The assumed architecture is shown in the figure below. On the device side, we typically have an end host as a DetNet system that makes use of the DetNet functionality. Note that the end host does not have to be DetNet aware. + +![Figure 6.1.1-1: Architecture for DetNet integration of 5GS. The diagram shows a 5GS logical DetNet Node (dashed box) containing UE, RAN, AMF, SMF, UPF, PCF, and TSCTSF. The UE is connected to a DetNet system. The RAN is connected to the AMF and UPF. The AMF is connected to the SMF. The SMF is connected to the UPF. The PCF is connected to the SMF and TSCTSF. The TSCTSF is connected to the CPF: DetNet controller. The CPF: DetNet controller is connected to a DetNet network cloud. The UPF is connected to the DetNet network cloud.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +graph LR + subgraph 5GS_logical_DetNet_Node [5GS logical DetNet Node] + UE[UE] --- RAN[RAN] + RAN --- AMF[AMF] + AMF --- SMF[SMF] + SMF --- UPF[UPF] + PCF[PCF] --- SMF + SMF --- TSCTSF[TSCTSF] + end + DetNet_system[DetNet system] --- UE + TSCTSF --- CPF[CPF: DetNet controller] + CPF --- DetNet_network((DetNet network)) + UPF --- DetNet_network + +``` + +Figure 6.1.1-1: Architecture for DetNet integration of 5GS. The diagram shows a 5GS logical DetNet Node (dashed box) containing UE, RAN, AMF, SMF, UPF, PCF, and TSCTSF. The UE is connected to a DetNet system. The RAN is connected to the AMF and UPF. The AMF is connected to the SMF. The SMF is connected to the UPF. The PCF is connected to the SMF and TSCTSF. The TSCTSF is connected to the CPF: DetNet controller. The CPF: DetNet controller is connected to a DetNet network cloud. The UPF is connected to the DetNet network cloud. + +Figure 6.1.1-1: Architecture for DetNet integration of 5GS + +### 6.1.2 Functional Description + +#### Information to report + +A DetNet node may report the following information. There can be multiple options regarding the detailed use of parameters, and the choice is up to the needs of the given implementation and deployment. + +- The interfaces of the 5GS acting as a DetNet node can be reported based on the YANG model in RFC 8344 [6]. That model is in turn based on RFC 8343 [7]. The model includes for each interface + - if-Index and name to identify the interface (see below for more details); + - type of the interface, which can identify whether it is a 3GPP interface on the device side or a fixed interface on the network side; + - IP address and subnet; + - when available in the case of network side interfaces, list of neighbour IP address and link layer address (which could be based on ARP or IPv6 neighbour discovery). In the case of device side interfaces the solution does not assume neighbours; only the hosts that are reachable with the assigned IP address(es) on the given PDU Session are reachable. +- In addition to the list of interfaces, the 5GS node itself also needs to be identified. There can be alternatives: + - The identification can be based on a YANG parameter of host type as defined in RFC 6021 [10] which can be either an IP address or a domain name. With this approach, the host is identified towards the DetNet controller, and the host identification is also provided together with the configuration. + - Alternatively, the DetNet node may also be identified by the IP address terminating the interface on the TSCTSF towards the DetNet controller, but in that case that IP address needs to be different for each logical DetNet node which is on a per UPF granularity. +- It is useful for the DetNet controller to be able to identify that the 5GS node is a 3GPP defined 5GS system, rather than a router with fixed interfaces only. This knowledge can be useful for the DetNet controller to consider for the QoS that can be provided for a flow. There can be several alternatives how this is determined in the DetNet controller. The alternatives below may be used depending on the needs of the deployment; the specification does not need to mandate a given mechanism. + - The interface type (as mentioned above) may indicate a 3GPP interface. A node having a 3GPP interface can be considered a 5GS system for a DetNet controller. + - If the 5GS DetNet node is identified by a domain name, that domain name may include a substring that identify the node as a 5GS node. + +- The DetNet controller may be pre-configured with a list or range of the node addresses or names that correspond to 5GS nodes. + +The reporting from the 5GS node to the DetNet controller is performed using YANG data models that can be carried using Netconf RFC 6241 [8] or Restconf RFC 8040 [9]. Given that DetNet is an IETF solution that can be used for a number of link layer technologies, IETF protocols are assumed at the DetNet controller. + +The solution does not require an NEF between the DetNet controller and the TSCTSF, since the DetNet controller is assumed to be trusted by the operator and can influence the QoS of the traffic flows. A NEF anyway cannot intercept the messages carried over Netconf or Restconf, which may be encrypted using TLS. + +#### Collection of the information + +The information about 5GS acting as a DetNet node is provided to the TSCTSF within the 3GPP system as follows. + +- For each PDU Session, the UPF generates a port number that is unique to the given UPF in the given network instance, similarly as in the Release 17 case. The port number is sent via the SMF and PCF to the TSCTSF. Similarly, a port number is generated for each interface on the UPF in the network side. The port number is used as the if-Index. Based on the if-Index, the name is generated, e.g. by using the if-Index as a string, possibly adding a substring prefix or postfix based on configuration. Note that 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. +- For each PDU Session, the allocated IP address is sent to the TSCTSF as in Release 17. Similarly, for each network interface of the UPF, the IP address and subnet is sent to the TSCTSF. + +In the case of interfaces that correspond to the PDU Sessions, the information about the port number as well as the IP address is delivered to the TSCTSF without requiring a PMIC container from the UE. It can be useful to be able to use DetNet even without having to require a PMIC, which makes the DetNet solution easier to deploy (but using a PMIC is not excluded, e.g. for time synch purposes). Based on configuration in the PCF for a given DNN, S-NSSAI, the TSCTSF is notified of the information. + +In the case of interfaces that correspond to the network side interfaces of the UPF, the information is carried in the PMIC, together with the port number and user plane node ID that is sent outside of the PMIC. The PMIC in this case includes the IP address, the subnet, and the neighbour information (list of neighbour IP addresses when available). + +The UPF also provides a user plane node ID. This can be constructed based on an IP address of the UPF, or also using the DNN, S-NSSAI or network instance known at the UPF, or it can be derived in other ways. The TSCTSF uses the user plane node ID provided by the UPF, and may optionally update it as needed (e.g. convert it to a domain name string, or map it to an IP address used for a network management protocol), to determine the host identification used for the given 5GS node. + +### 6.1.3 Procedures + +The charts below show a high level view of the procedures. Only the relevant steps are discussed, unaffected steps are not shown in the figures and not discussed in the explanations. + +For the device side ports of the 5GS node, the PDU Session Establishment procedure is used with the following extensions. (Similar extensions possible for the PDU Session Modification and PDU Session Release procedure.) The functionality is based on the Release 16-17 IoT functions. + +![Sequence diagram showing signalling at PDU Session Establishment between UPF, SMF, PCF, TSCTSF, and CPF.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +``` + +sequenceDiagram + participant UPF + participant SMF + participant PCF + participant TSCTSF + participant CPF + Note left of UPF: Request port and node info + UPF->>SMF: 1: Request port and node info + SMF-->>UPF: 2: Provide port and node info + SMF->>PCF: 3: Provide node and port info + PCF->>TSCTSF: 4: Provide node and port info + TSCTSF->>CPF: 5: Update state information + +``` + +Sequence diagram showing signalling at PDU Session Establishment between UPF, SMF, PCF, TSCTSF, and CPF. + + + +Figure 6.1.3-1: Signalling at PDU Session Establishment + +1. In the N4 Session Establishment Request, the SMF requests the UPF to provide port and node information. The SMF request may be based on configuration for the given DNN, S-NSSAI. +2. The UPF provides a port number that identifies the given port corresponding to the PDU Session in the logical 5GS node, and provides a user-plane node ID. +3. As part of the SMF initiated SM Policy Association Modification procedure, the SMF provides node and port information to the PCF, including the port number and the user plane node ID as well as the UE IP address. For this, based on configuration for the given DNN, S-NSSAI, the SMF is armed for reporting this information to the PCF. +4. As part of the SMF initiated SM Policy Association Modification procedure, the PCF reports the node and port information to the TSCTSF. +5. The TSCTSF provides information about the change in the 5GS node state, including information that is derived from the info received in the previous step. The detailed signalling for this step may depend on the actual IETF protocol used between the TSCTSF and the DetNet controller plane function (CPF). The update of the information may take place immediately based on a notification mechanism from the TSCTSF to the CPF, or it may take place when the CPF requests for the information. + +For the network side ports of the 5GS node, as in Releases 16-17, the N4 Session Level Reporting Procedure from the UPF to the SMF is used followed by the SMF initiated SM Policy Association Modification procedure. The signalling is extended with the relevant new parameters as illustrated below. + +![Sequence diagram showing signalling for updating node and port information between UPF, SMF, PCF, TSCTSF, and CPF. The sequence is: 1. UPF to SMF: Provide port and node info; 2. SMF to PCF: Provide node and port info; 3. PCF to TSCTSF: Provide node and port info; 4. TSCTSF to CPF: Update state information. A small URL 'http://msc-generator.sourceforge.net v7.2' is visible at the bottom right of the diagram.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant UPF + participant SMF + participant PCF + participant TSCTSF + participant CPF + Note right of CPF: http://msc-generator.sourceforge.net v7.2 + UPF->>SMF: 1: Provide port and node info + SMF->>PCF: 2: Provide node and port info + PCF->>TSCTSF: 3: Provide node and port info + TSCTSF->>CPF: 4: Update state information + +``` + +Sequence diagram showing signalling for updating node and port information between UPF, SMF, PCF, TSCTSF, and CPF. The sequence is: 1. UPF to SMF: Provide port and node info; 2. SMF to PCF: Provide node and port info; 3. PCF to TSCTSF: Provide node and port info; 4. TSCTSF to CPF: Update state information. A small URL 'http://msc-generator.sourceforge.net v7.2' is visible at the bottom right of the diagram. + +**Figure 6.1.3-2: Signalling for updating node and port information** + +1. As part of N4 reporting, the UPF provides a port and node information. This includes the port number that identifies the given port, and provides a user-plane node ID. The UPF also provides the IP address and subnet that is used on the given interface, the type of the interface, and if available, the IP addresses of the neighbours. This information can be included in the PMIC. +2. As part of the SMF initiated SM Policy Association Modification procedure, the SMF provides node and port information to the PCF, including the port number and the user plane node ID and other information provided by the UPF. For this, based on configuration for the given DNN, S-NSSAI, the SMF is armed for reporting this information to the PCF. +3. As part of the SMF initiated SM Policy Association Modification procedure, the PCF reports the node and port information to the TSCTSF. +4. The TSCTSF provides information about the change in the 5GS node state, including information that is derived from the info received in the previous step. The detailed signalling for this step may depend on the actual IETF protocol used between the TSCTSF and the DetNet controller plane function (CPF). The update of the information may take place immediately based on a notification mechanism from the TSCTSF to the CPF, or it may take place when the CPF requests for the information. + +### 6.1.4 Impacts on existing entities and interfaces + +UPF: + +- Provide node and interface information, optionally neighbour information. Generation of PMIC. + +SMF: + +- Configuration update to trigger signalling. + +TSCTSF: + +- Map collected information to IETF YANG models and provide to CPF. + +## 6.2 Solution #2 for Key Issue #1: Network function enhancement to support 5GS DetNet node reporting + +### 6.2.1 Introduction + +In 5G mobile network, in order to realize DetNet deterministic forwarding mechanism and ensure the certainty of wide area, the DetNet control plane requires the DetNet node to report relevant information to the DetNet control plane before issuing the strategy. + +IETF RFC 8655 [2] stipulates that DetNet nodes need to report corresponding information to DetNet control plane, including recognition of adjacent DetNet nodes. + +Therefore, as a DetNet node, 5GS system should also report corresponding information to the DetNet control plane to assist the DetNet control plane in making corresponding forwarding strategy. + +This report puts forward the method for the DetNet control plane to obtain the topology of adjacent 5GS DetNet node, and defines the mechanism of 5GS as a DetNet node to the DetNet control plane. An enhanced architecture supporting the reporting of mobile network information to DetNet control layer is designed. The architecture enhances the functions of NEF, SMF, and UPF respectively, so as to support the information collection, subscription and reporting of DetNet capability. + +### 6.2.2 Functional Description + +![Figure 6.2.2-1: Enhanced architecture and network function. The diagram shows a 5GS as DetNet node (dashed box) containing UE, RAN, AMF, UDM, PCF, SMF, and UPF. The SMF and UPF have 'DetNet information reporting' blocks. The AMF is connected to the RAN and UDM. The UDM is connected to the PCF. The PCF is connected to the SMF. The SMF is connected to the UPF. The UPF is connected to a cloud representing the DetNet node. The NEF (DetNet ability Exposure) is connected to the SMF and the DetNet controller. The TSCTSF is connected to the NEF. The DetNet controller is connected to the NEF and the cloud representing the DetNet node.](5dfc130b129ace4df375839020a5700d_img.jpg) + +Figure 6.2.2-1: Enhanced architecture and network function. The diagram shows a 5GS as DetNet node (dashed box) containing UE, RAN, AMF, UDM, PCF, SMF, and UPF. The SMF and UPF have 'DetNet information reporting' blocks. The AMF is connected to the RAN and UDM. The UDM is connected to the PCF. The PCF is connected to the SMF. The SMF is connected to the UPF. The UPF is connected to a cloud representing the DetNet node. The NEF (DetNet ability Exposure) is connected to the SMF and the DetNet controller. The TSCTSF is connected to the NEF. The DetNet controller is connected to the NEF and the cloud representing the DetNet node. + +**Figure 6.2.2-1: Enhanced architecture and network function** + +As shown in the figure 1, the 3GPP exposure architecture is enhanced to support DetNet node reporting. Extend NEF function to support the capability exposure of DetNet node, and extend SMF, and UPF to support DetNet information reporting function. The related network functions are enhanced to support following features: + +- Extend NEF function to support the exposure of DetNet capability: + - Receive the capability exposure subscription from DetNet control plane, and report related ability to it; + - Forward DetNet information reporting requirements to SMF based on DetNet controller subscription, including reporting contents, reporting frequency, indication of direct notification from UPF, etc.. + - Enhance the function of NEF to support the authentication of DetNet controller. + - The signalling protocol between NEF and DetNet control uses IETF Netconf [8] or Restconf [9]. + +- Expand SMF to support DetNet information reporting function. Based on the reporting requirements issued by NEF, SMF receives DetNet related information reported by UPF on N4 interface, and sends it to NEF as required. +- Expand UPF to support DetNet information reporting function, and report the following information through N4 interface, or via network exposure service: + - Identity and link with adjacent DetNet nodes: the identification of surrounding nodes can be obtained through routing broadcast messages on N6. + - When the PDU session is established, the UPF detects the DetNet node on the N6 interface, associates it with the PDU session, and sends the information to the SMF in the N4 PDU session update message, and the SMF forwards it to the NEF for external reporting. + +The collection and reporting methods of network information are as follows: + +- Reporting method of adjacent DetNet nodes for the UPF: + - UPF obtains identification of DetNet nodes around the N6 interface through BGP and other routing broadcast messages. + - UPF reports the identification and link of adjacent DetNet nodes to SMF through N4 interface, then opens the information to DetNet control plane. + - The UPF reports the identification and link of adjacent DetNet nodes information to the SMF on the N4 interface. And the SMF forwards the information to the NEF. There are no impacts on the PCF and TSCTSF. + +### 6.2.3 Procedures + +![Sequence diagram illustrating the subscription and reporting process of DetNet ability opening. The diagram shows four lifelines: DetNet controller, NEF(DetNet ability Exposure), SMF(DetNet capability reporting), and UPF(DetNet capability reporting). The process is divided into two phases: Subscription process and Reporting process. The Subscription process involves the DetNet controller subscribing to the NEF, the NEF forwarding the request to the SMF, and the SMF subscribing to the UPF. The Reporting process involves the UPF sending network side capability reporting to the SMF, the SMF performing capability integration and escalation, and the DetNet controller taking the whole 5GS as a DetNet node and opening up ability. Finally, the DetNet controller uses the report results to assist in the formation of DetNet forwarding decision.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` + +sequenceDiagram + participant DetNet controller + participant NEF as NEF(DetNet ability Exposure) + participant SMF as SMF(DetNet capability reporting) + participant UPF as UPF(DetNet capability reporting) + + Note left of DetNet controller: Subscription process + DetNet controller->>NEF: 1.Subscribe to ability opening messages, including reported message content and reported frequency / trigger conditions + NEF->>SMF: 2.Forward ability opening requirement DetNet requested + SMF->>UPF: 3.Subscribe to network side capability reporting + + Note left of DetNet controller: Reporting process + UPF->>SMF: 4.Network side capability reporting + SMF->>NEF: 5.Capability integration and escalation + NEF->>DetNet controller: 6.Take the whole 5GS as DetNet node, Opening up ability; + DetNet controller-->>NEF: 7.Based on the report results, assist in the formation of DetNet forwarding decision + +``` + +Sequence diagram illustrating the subscription and reporting process of DetNet ability opening. The diagram shows four lifelines: DetNet controller, NEF(DetNet ability Exposure), SMF(DetNet capability reporting), and UPF(DetNet capability reporting). The process is divided into two phases: Subscription process and Reporting process. The Subscription process involves the DetNet controller subscribing to the NEF, the NEF forwarding the request to the SMF, and the SMF subscribing to the UPF. The Reporting process involves the UPF sending network side capability reporting to the SMF, the SMF performing capability integration and escalation, and the DetNet controller taking the whole 5GS as a DetNet node and opening up ability. Finally, the DetNet controller uses the report results to assist in the formation of DetNet forwarding decision. + +**Figure 6.2.3-1: Subscription and reporting process of DetNet ability opening** + +1. Before issuing the forwarding strategy, or based on the need of periodic collection of the DetNet capability, the DetNet control plane subscribes the capability exposure to NEF, which includes the information to be reported ,reporting frequency and triggers. +2. NEF forwards the requested capability reporting requirements to SMF. +3. SMF subscribes the capability reporting of DetNet from UPF. + +4. According to the subscription request, UPF collects the relevant information of DetNet on the network side, including N6 interface topology; UPF may report the identification and link of adjacent DetNet nodes to NEF directly via network exposure service if received indication of direct notification from NEF. +5. SMF integrates the reporting messages received on the N4 interface to form the reporting data of 5GS as a DetNet node, such as adjacent nodes, which can be collected by NEF and be reported to the DetNet controller. +6. NEF reports corresponding information to DetNet control plane. +7. The DetNet control plane generates the DetNet forwarding strategy based on the received reports. + +In the above figure, steps 1-3 is the capability reporting subscription procedure, and steps 4-6 is the capability reporting procedure. + +### 6.2.4 Impacts on existing entities and interfaces + +The new requirements are mainly aimed at the functional enhancement of NEF, SMF and UPF modules. + +Extend NEF to achieve: + +- Receiving subscription information from DetNet control plane and reporting related capabilities to the outside, +- Based on subscription requirements, send DetNet information reporting requirements to SMF, including the information to be reported, reporting frequency, etc. + +Extend SMF to achieve: + +- Based on the reporting requirements issued by NEF, SMF receives DetNet related information reported by UPF on N4 interface. +- Comprehensively process relevant information and send it to NEF according to the required frequency or conditions. + +Extend UPF to achieve: + +- Report the identity and link with adjacent DetNet nodes through N4 interface. +- The UPF reports the identification and link of adjacent DetNet nodes information to the SMF on the N4 interface. And the SMF forwards the information to the NEF. There are no impacts on the PCF and TSCTSF. + +### 6.2.5 Solution evaluation + +- Adjust the strategy in time when the network capability changes. +- Better ensure the implementation of certainty on WAN. +- Without significantly changing the original framework, the information requirements of DetNet control plane can be met by expanding the existing network function. + +## 6.3 Solution #3 for Key Issue #2: Mapping from DetNet YANG model to 3GPP configuration + +### 6.3.1 Introduction + +The assumed architecture is shown in the figure below. On the device side, we typically have an end host as a DetNet system that makes use of the DetNet functionality. Note that the end host does not have to be DetNet aware. + +![Figure 6.3.1-1: DetNet logical reference architecture distribution in 5GC. The diagram shows a 'DetNet system' connected to a 'UE' (User Equipment). The 'UE' is connected to a 'RAN' (Radio Access Network), which is connected to an 'AMF' (Access and Management Function). The 'AMF' is connected to a 'SMF' (Session Management Function), which is connected to a 'UPF' (User Plane Function). The 'UPF' is connected to a 'DetNet network' (represented by a cloud). The 'DetNet network' is connected to a 'CPF: DetNet controller'. The 'CPF: DetNet controller' is connected to a 'TSCTSF' (Traffic Steering and Control Function), which is connected to a 'PCF' (Policy Control Function). The 'PCF' is connected to the 'SMF'. The 'UE', 'RAN', 'AMF', 'SMF', 'UPF', 'PCF', and 'TSCTSF' are all enclosed in a dashed box labeled '5GS logical DetNet Node'.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 6.3.1-1: DetNet logical reference architecture distribution in 5GC. The diagram shows a 'DetNet system' connected to a 'UE' (User Equipment). The 'UE' is connected to a 'RAN' (Radio Access Network), which is connected to an 'AMF' (Access and Management Function). The 'AMF' is connected to a 'SMF' (Session Management Function), which is connected to a 'UPF' (User Plane Function). The 'UPF' is connected to a 'DetNet network' (represented by a cloud). The 'DetNet network' is connected to a 'CPF: DetNet controller'. The 'CPF: DetNet controller' is connected to a 'TSCTSF' (Traffic Steering and Control Function), which is connected to a 'PCF' (Policy Control Function). The 'PCF' is connected to the 'SMF'. The 'UE', 'RAN', 'AMF', 'SMF', 'UPF', 'PCF', and 'TSCTSF' are all enclosed in a dashed box labeled '5GS logical DetNet Node'. + +**Figure 6.3.1-1: DetNet logical reference architecture distribution in 5GC** + +The main principles of the solution are as follows. + +- In the DetNet YANG model (draft-ietf-detnet-yang [5]), the forwarding sub-layer configuration and the traffic profile are for the mapping. +- The forwarding sub-layer configuration identifies the flow and the incoming, outgoing interfaces. Based on this information, the PDU Session and the flow direction (uplink, downlink or whether it is UE to UE) can be determined. +- The DetNet traffic requirements in the traffic profile include the max-latency, min-bandwidth and the max-loss, which can be converted to the 3GPP delay, GFBR and PER requirements. +- The YANG model as currently defined in IETF only includes the end to end traffic requirements. There are two options: the TSCTSF may either derive the per 5GS requirements from the end to end requirements, or the DetNet YANG model is extended for the 5GS to include also the requirements specific to the 5GS. +- The DetNet traffic specification is used to determine the periodicity and the bandwidth requirement of the flow. + +### 6.3.2 Functional Description + +#### Parameters to consider from the DetNet controller + +The YANG model in draft-ietf-detnet-yang [5] describes the parameters that are used by the DetNet nodes to set up the configuration for DetNet. As the 5GS realizes the forwarding sub-layer, it is the forwarding sub-layer configuration that needs to be considered in the YANG model. In addition, the YANG configuration can provide the Traffic Profile that includes the traffic requirements and the traffic specification that could be used by the 5GS system. + +The DetNet YANG model contains the following parameters in the traffic requirements referenced in the forwarding sub-layer which can be mapped to 3GPP parameters. + +- Max-latency, which relates to the required delay in the 5GS. +- Min-bandwidth, which relates to the guaranteed bitrate that is needed for the flow (GFBR). +- Max-loss, which relates to the PER that is being proposed to be added as a new parameter in the release 18 in the 5TRS\_URLLC study that can be provided to the 5GS. + +The DetNet YANG model also contains other parameters in the traffic profile that is referenced in the forwarding sub-layer which do not easily map to 3GPP parameters: max-latency-variation, max-consecutive-loss-tolerance, max-mis-ordering. There is no straightforward 3GPP mapping for these parameters as their definition differs from the current 3GPP parameters. Hence it is proposed not to standardize any mapping for these parameters in the current release. + +The traffic specification referenced in the forwarding sub-layer includes the following parameters that can be mapped. + +- Interval: this corresponds to the periodicity in the 3GPP system. + +- max-pkts-per-interval, max-payload-size: can be used to determine the maximum burst size; together with the interval parameter, the required bandwidth can be calculated, which corresponds to the MFBR. + +The traffic specification can also contain min-pkts-per-interval, min-payload-size, which do not map to any 3GPP parameters hence these are not proposed to be supported in the standardized mapping. + +The TSCTSF can use the Interval to generate the periodicity value in the TSCAI. + +Regarding the traffic requirements, it must be noted that the current DetNet YANG model includes only the end to end traffic requirements (e.g. in terms of maximal latency), and not the per node requirements that need to be realized by a given node. Even though it is the per node requirements that matter for the configuration of a given node, that information is currently not included in the IETF model as of today. + +Based on the current IETF YANG model as currently defined, two main options can be used by the 5GS acting as a DetNet node. + +- The TSCTSF derives the per node traffic requirements from the end to end traffic requirements using a pre-configured mapping in the TSCTSF, based on the knowledge of the given deployment. E.g. take a given fraction of the end to end requirements and/or subtract a constant that corresponds to the rest of the network. +- Extend the IETF YANG model with additional parameters that apply to the 5GS system on a per node basis. The YANG modelling language allows for extensibility. That can be achieved by a 3GPP defined YANG model that imports the IETF defined DetNet YANG model and adds the needed per node parameters. In that way, the model used by 5GS remains compatible with IETF DetNet, but allows for the DetNet controller to provide the traffic requirements on a per node basis when the DetNet controller is prepared for this and when it is aware that the DetNet node is a 5GS. (That knowledge can be available based on the exposure solution in Key Issue #1.) + +**Editor's note:** Whether and How to map the E2E traffic requirement is FFS. + +**Editor's note:** Whether and How to Extend the IETF YANG model is FFS. + +#### Identification of the PDU Sessions + +The TSCTSF receives the DetNet YANG forwarding configuration, which refers to the incoming and outgoing interfaces in 5GS. These are based on the interface identification that is provided in the reporting from the 5GS to the DetNet controller as part of Key Issue #1 solution. The interface is identified by its name, which is derived from the if-Index, which in turn is based on the port number that is set by the UPF. The TSCTSF stores the mapping between the port number (if-Index and the corresponding interface name) and the PDU Session, hence the PDU Session can be identified. The incoming and outgoing interfaces also identify whether the flow is uplink or downlink, hence flow direction is known, and also whether it is a UE to UE flow. + +The TSCTSF may also perform a verification whether the 3GPP system routes the given flow as defined in the DetNet forwarding sub-layer. Note that it is out of scope of the current study to update the 3GPP system's routing based on the DetNet configuration, but it can be possible to verify in the TSCTSF whether the incoming and outgoing interfaces in the DetNet configuration correspond to a valid routing in the 3GPP system. As an example, the TSCTSF may verify whether the destination IP address in a downlink flow towards a given interface corresponding to a PDU Session is the same IP address that is assigned for the same PDU Session. As another example, the TSCTSF may be preconfigured with the knowledge whether or not UE to UE routing is enabled or not. The TSCTSF may also verify other parameters of the configuration, and indicate that the configuration for the flow is not accepted if the configuration is outside of the supported range, based on TSCTSF preconfiguration. As a result of this optional verification, the TSCTSF may decide to accept or reject a given DetNet configuration. + +In the case of a UE to UE flow, if the system allows for such traffic, the TSCTSF generates separate requests on PDU Session basis towards the PCF(s) for the uplink and the downlink legs of the flow. + +#### 3GPP configuration for DetNet + +The PCF receives the relevant QoS requirements from the TSCTSF as well as the flow description as determined by the TSCTSF based on the DetNet configuration. The stage 3 definition of the flow description is extended according to the needs of DetNet, also including the DSCP value and optionally Ipv6 flow label and Ipsec SPI. The PCF determines the 3GPP QoS parameters based on the QoS requirements provided by the TSCTSF. The PCF may also consider the DSCP value in the flow description. The PCF may establish new QoS flows or modify existing QoS flows as needed. + +#### Deployment option: configuration of the implementation specific routing functionality on N6 + +Below we clarify a possible deployment option that does not require additional 3GPP specification. + +The UPF node may have routing functionality on the N6 interface side which is implementation specific. The 3GPP specifications are not responsible for setting the routing on the N6 interface side. In deployments where the implementation specific routing functionality on the N6 side also needs to be configured for DetNet, direct configuration can be used between the CPF and the routing functionality co-located with the UPF. This case can be modelled with a single interface between the UPF and the router; when the UPF and the router are co-located in the same physical node, then the interface between them can be modelled as a single virtual interface. This optional deployment is shown in the figure below. There is no need to use this option in deployments where there is no need for routing configuration by the CPF on the N6 side. + +![Figure 6.3.2-1: Optional deployment scenario with CPF control of N6 routing. The diagram shows a '5GS logical DetNet Node' containing AMF, SMF, UPF, and R. The AMF is connected to a UE, which is connected to a DetNet system. The R is connected to a DetNet network cloud. The SMF is connected to the UPF, which is connected to the R. The PCF is connected to the SMF, and the TSCTSF is connected to the PCF. The CPF: DetNet controller is connected to the TSCTSF and the DetNet network cloud.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Figure 6.3.2-1: Optional deployment scenario with CPF control of N6 routing. The diagram shows a '5GS logical DetNet Node' containing AMF, SMF, UPF, and R. The AMF is connected to a UE, which is connected to a DetNet system. The R is connected to a DetNet network cloud. The SMF is connected to the UPF, which is connected to the R. The PCF is connected to the SMF, and the TSCTSF is connected to the PCF. The CPF: DetNet controller is connected to the TSCTSF and the DetNet network cloud. + +Figure 6.3.2-1: Optional deployment scenario with CPF control of N6 routing + +#### Other considerations + +The solution does not require an NEF between the DetNet controller and the TSCTSF, since the DetNet controller is assumed to be trusted by the operator and can influence the QoS of the traffic flows. + +### 6.3.3 Procedures + +The figure illustrates the procedure for the mapping of the DetNet configuration. + +![Figure 6.3.3-1: Signalling for setting up YANG configuration for DetNet. The sequence diagram shows five steps: 1. CPF provides DetNet YANG configuration to TSCTSF; 2. TSCTSF provides mapped parameters to PCF; 3. PCF creates or updates QoS flows in SMF; 4. SMF responds to PCF; 5. PCF responds to TSCTSF.](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg) + +``` + +sequenceDiagram + participant CPF + participant TSCTSF + participant PCF + participant SMF + Note left of SMF: 3: Create or update QoS flows + CPF->>TSCTSF: 1: Provide DetNet YANG configuration + TSCTSF->>PCF: 2: Provide mapped parameters + PCF->>SMF: 3: Create or update QoS flows + SMF-->>PCF: 4: Response + PCF-->>TSCTSF: 5: Response + +``` + +Figure 6.3.3-1: Signalling for setting up YANG configuration for DetNet. The sequence diagram shows five steps: 1. CPF provides DetNet YANG configuration to TSCTSF; 2. TSCTSF provides mapped parameters to PCF; 3. PCF creates or updates QoS flows in SMF; 4. SMF responds to PCF; 5. PCF responds to TSCTSF. + +Figure 6.3.3-1: Signalling for setting up YANG configuration for DetNet + +1. The DetNet controller provides YANG configuration to the TSCTSF. The TSCTSF uses the identity of the incoming and outgoing interfaces to determine the affected PDU Session(s) and whether the flow is uplink or downlink. (For this, the information collected in the solution to Key Issue #1 is used.) The TSCTSF also determines if the flow is UE to UE in which case two PDU Sessions will be affected for the flow and can also verify whether the specified routing is applicable. The TSCTSF maps the configuration as described above and calculates the delay and PER requirements and the TSC Assistance Container for each flow description. +2. The TSCTSF provides the mapped parameters and the flow description to the PCF(s) on PDU Session basis. +3. The PCF(s) determines, based on the parameters received from the TSCTSF, whether the existing QoS flows need to be modified or a new QoS flow needs to be created. Additionally, the TSC Assistance Container is provided to the SMF. +4. The PCF responds to the TSCTSF, which includes information about the success of the configuration. + +5. The TSCTSF provides a response to the CPF regarding the success of the configuration setup. Optionally, it can be possible to provide 3GPP specific status codes to provide additional information if the requested configuration could not be set up. + +If the status of the flow changes later on for any reason, the TSCTSF notifies the CPF. Upon release of a PDU Session that is part of the existing DetNet configuration, the PCF notifies the TSCTSF for the PDU Session release, and TSCTSF notifies the CPF on status of the flow. + +### 6.3.4 Impacts on existing entities and interfaces + +TSCTSF: Maintains mapping between the port number in a UPF and the PDU Session and the associated interface in the DetNet configuration. Mapping of DetNet parameters and providing information to the DetNet controller whether the configuration is accepted. + +PCF: + +- Stage 3 definition of flow description parameter is extended. + +## 6.4 Solution #4 for Key Issue #2: DetNet Flow Mapping + +### 6.4.1 Introduction + +This contribution discusses about which parameters should be mapped into which 5G parameters to support the interworking between 5GS and DetNet controller. This contribution proposes an alternative mapping between DetNet flow and QoS flow. + +According to clause 5 of IETF RFC 9016 [4], the DetNet Flow-related parameters in the information model used in the DetNet controller can be classified into 3 categories: DetNet Flow identification parameters (including DnFlowID, DnFlowFormat and DnFlowSpecification etc.), DetNet Traffic Specification parameters (DnTrafficSpecification) and DetNet Flow requirements (e.g. DnFlowRequirements). DetNet Traffic Specification parameters parameters can be mapped into QFI and Packet Filter Sets to identify the DetNet Flow. The configuration that is sent to the 5GS is based on the Yang model in draft-ietf-detnet-yang [5]. Part of the DetNet Traffic Specification parameters and DetNet Flow requirements can be mapped into 5GS QoS related requirements (e.g. 5QI related QoS requirements and TSCAI related TSC requirements). + +The DetNet Flow requirements provided by the DetNet controller are all per DetNet Flow parameters for the whole DetNet network. Some of the parameters of the requirements (e.g. maximum latency of the DetNet Flow) cannot be mapped to 5GS QoS requirements directly and the status/capability information of the other nodes in the DetNet flow path is needed. + +### 6.4.2 Functional Description + +The TSC architecture defined in clause 4.4.8.3 of TS 23.501 [12] is reused for support of DetNet functions by the following function enhancement. + +- New DetNet AF is introduced to help TSCTSF support DetNet flow mapping. The DetNet controller sends the DetNet related parameters of the DetNet flow to DetNet AF and DetNet AF maps them to 5GS QoS requirements or TSC requirements and send the requirements to TSCTSF. Then TSCTSF interacts with PCF to configure the TSC QoS flow which is mapped to the DetNet flow. + +NOTE: This solution follows the Rel-17 architecture for AF requested support of Time Sensitive Communication and Time Synchronization defined in clause 4.4.8.3 of TS 23.501 [12]. Double mapping is used: DetNet controller interacts with DetNet AF using the IETF protocol defined in RFC 9016 [4] and draft-ietf-detnet-yang [5], and DetNet AF interacts with TSCTSF using the Rel-17 TSCTSF interfaces defined for TSC services. NEF may be deployed between the DetNet AF and TSCTSF according to the current architecture. + +PCF generates the QoS related policy and distributes the policy to SMF based on the current Policy control framework. TSCTSF generates the TSCAI according to the requirements sent by DetNet AF. + +Table 6.4.2-1 shows the mapping between DetNet related parameters and 5GS QoS parameters. + +Table 6.4.2-1: Mapping between DetNet related parameters and 5GS parameters + +| DetNet related parameters | 5GS requirement category | Whether the DetNet related parameters are node level info or Detnet flow level (NOTE 2) | +|-------------------------------------------|----------------------------------|-----------------------------------------------------------------------------------------| +| MaxPacketsPerInterval and Max PayloadSize | TBD | Y | +| MinBandwidth | QoS requirement | Y | +| MaxLatency | QoS requirement | N | +| MaxLoss | QoS requirement | N | +| MaxConsecutiveLossTolerance | TBD (NOTE 1) | N | +| Interval | TSC information | Y | +| Next hop information | TSC information (Flow direction) | Y | +| MinPayloadSize | TBD | Y | +| MinPacketsPerInterval | TBD | Y | +| MaxLatencyVariation | TBD | N | +| MaxMisordering | TBD | N | + +NOTE 1: TBD means no current 5GS parameters can be used for the mapping of DetNet related parameters. +NOTE 2: Indicates whether the DetNet related parameters can be used as node level parameters to configure the 5GS QoS.. Y=yes, N=No. + +Editor's note: Whether and how the DetNet related parameters marked as TBD in the table should be mapped to 5GS requirements is FFS. + +The DetNet Flow requirements provided by the DetNet controller are all per DetNet Flow parameters for the whole DetNet network. The parameters in table 6.4.2-1 with value 'N' in the third column can not be mapped to 5GS QoS parameters directly and the status/capability information of the other nodes in the DetNet flow path is needed. + +Editor's note: Whether and how to get the other DetNet nodes' information to support DetNet network is FFS. + +### 6.4.3 Procedures + +The existing policy control framework is reused. The only enhancement is that the DetNet AF can provide the mapped 5GS QoS requirements/ TSC requirements to TSCTSF for support of DetNet flow transmission. The detailed procedure is shown in Figure 6.4.3-1: + +![Sequence diagram for QoS flow configuration for DetNet. The diagram shows interactions between SMF, PCF, TSCTSF, DetNet AF, and CPF. The sequence is: 1. DetNet configuration from CPF to DetNet AF; 2. Mapped TSC requirements from DetNet AF to TSCTSF; 3. TSC QoS flow configuration from TSCTSF to PCF; 4. QoS Flow creation or update from SMF to PCF; 5. TSC QoS flow configuration response from PCF to TSCTSF; 6. Response from TSCTSF to DetNet AF; 7. DetNet configuration Response from DetNet AF to CPF.](552ca016af3d6240648ab5a2cad97f60_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant PCF + participant TSCTSF + participant DetNet AF + participant CPF + Note left of SMF: 4. QoS Flow creation or update + CPF->>DetNet AF: 1. DetNet configuration + DetNet AF->>TSCTSF: 2. Mapped TSC requirements + TSCTSF->>PCF: 3. TSC QoS flow configuration + SMF->>PCF: 4. QoS Flow creation or update + PCF->>TSCTSF: 5. TSC QoS flow configuration response + TSCTSF->>DetNet AF: 6. Response + DetNet AF->>CPF: 7. DetNet configuration Response + +``` + +Sequence diagram for QoS flow configuration for DetNet. The diagram shows interactions between SMF, PCF, TSCTSF, DetNet AF, and CPF. The sequence is: 1. DetNet configuration from CPF to DetNet AF; 2. Mapped TSC requirements from DetNet AF to TSCTSF; 3. TSC QoS flow configuration from TSCTSF to PCF; 4. QoS Flow creation or update from SMF to PCF; 5. TSC QoS flow configuration response from PCF to TSCTSF; 6. Response from TSCTSF to DetNet AF; 7. DetNet configuration Response from DetNet AF to CPF. + +Figure 6.4.3-1 QoS flow configuration for DetNet + +- The DetNet controller provides YANG configuration with the DetNet node ID (i.e. UPF node IP address) to the DetNet AF. The DetNet AF finds the mapped UE address according to the DetNet node ID, route interface information (DS-TT or NW-TT IP address as ingress/egress interface), Next hop information in YANG + +configuration (neighbouring DetNet node IP addresses). The DetNet AF maps the configuration as described above and calculates the TSC requirements for each DetNet flow. + +2. The DetNet AF provides the mapped TSC requirements to TSCTSF (optionally via NEF). +3. The TSCTSF calculates and provides the mapped QoS parameters, TSCAC and the flow description to the PCF(s) according to the TSC requirements. +4. The PCF(s) determines, based on the parameters received from the TSCTSF, whether the existing QoS flows need to be modified or a new QoS flow needs to be created. TSCAC is provided to the SMF. +5. The PCF responds to the TSCTSF with the result of the configuration. +6. The TSCTSF provides a response to the DetNet AF. + +NOTE: Step 2 to 6 refer to the clause 4.15.6.6 of TS 23.502 [13] for setting up TSC AF session with required QoS. + +7. DetNet AF responds to DetNet controller. + +### 6.4.4 Impacts on existing entities and interfaces + +DetNet AF: + +- Support of mapping DetNet flow related parameters to 5GS QoS requirements and TSC requirements and sending the parameters to TSCTSF (optionally via NEF). + +## 6.5 Solution #5 for Key Issue #2: Provisioning DetNet traffic to 5GS parameters + +### 6.5.1 Introduction + +This solution describes how 5GS maps DetNet configuration parameters given from the DetNet controller into 5GS parameters to handle DetNet traffic. There are assumptions for the solution: + +- DetNet Flow-Related Parameters as defined in draft-ietf-detnet-yang [5] is used as DetNet configuration parameters for DetNet traffic. +- DetNet controller is located in either a different domain from the 5GS or the same trust domain as the 5GS. + +### 6.5.2 Functional Description + +5GS does not support edge DetNet node functions and DetNet service sub-layer functions, according to the scope and architecture assumptions in this TR. That is, the 5GS supports the DetNet node functions and DetNet forwarding sub-layer related functions except for service sub-layer functions. As a result, this solution uses DetNet Flow-Related Parameters from the DetNet controller as DetNet configuration parameters for DetNet traffic (Table 6.5.2-1). + +Table 6.5.2-1: DetNet configuration parameters for DetNet traffic + +| Parameters | Descriptions | | 5GS Parameters | | +|-------------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| DetNet Flow attributes | | | | | +| DnFlowSpecification | SourceIpAddress | | IP Packet Filter Set

- Source IP address
- Destination IP address
- Flow label
- Type of Service / Traffic class
- Protocol ID
- Source port
- Destination port
- Security parameter index | | +| | DestinationIpAddress | | | | +| | Ipv6FlowLabel | | | | +| | Dscp | | | | +| | Protocol | | | | +| | SourcePort | | | | +| | DestinationPort | | | | +| | IPSecSpi | | | | +| DnTrafficSpecification | Interval | The period of time in which the traffic specification is specified | Periodicity | | +| | MaxPacketsPerInterval | The maximum number of packets that the Ingress will transmit in one Interval | Maximum data burst size (MDBV) | | +| | MaxPayloadSize | The maximum payload size that the Ingress will transmit | | | +| | MinPayloadSize | The minimum payload size that the Ingress will transmit | | | +| | MinPacketsPerInterval | The minimum number of packets that the Ingress will transmit in one Interval | | | +| DnFlowStatus | DnIngressStatus: None, Ready, Failed, OutOfService | | | | +| | DnEgressStatus: None, Ready, PartialFailed, Failed, OutOfService | | | | +| | FailureCode | | | | +| DetNet Flow Requirement attributes | | | | | +| DnFlowRequirements | MinBandwidth | | GFBR | | +| | MaxLatency | The maximum latency from Ingress to Egress(es) for a single packet of the DetNet flow | PDB | | +| | MaxLatencyVariation | The difference between the minimum and the maximum end-to-end, one-way latency | | | +| | MaxLoss | The maximum Packet Loss Rate (PLR) requirement for the DetNet flow between the Ingress and Egress(es) and the loss measurement interval | PER | | +| | MaxConsecutiveLossTolerance | The maximum number of consecutive packets whose loss can be tolerated | | | +| | MaxMisordering | The tolerable maximum number of packets that can be received out of order | | | + +The TSCTSF converts DetNet configuration parameters for DetNet traffic into 5GS QoS parameters and TSCAI, such as Interval into Periodicity and MaxPacketsPerInterval and MaxPayloadSize combined into MDBV. Due to the lack of any minimum values for payload size or packets in the 5GS specification, MinPayloadSize and MinPacketsPerInterval cannot currently be mapped into 5G parameters. + +In DnFlowRequirements, the MaxLatency, MaxLatencyVariation, MaxLoss, MaxConsecutiveLossTolerance, and MaxMisordering attributes specify requirements not in a single DetNet node but throughout the DetNet flow path. Therefore, if IETF DetNet specifications define explicit requirements on a DetNet node to enable DnFlowRequirements, how to provision them within the 5GS is dependent on the IETF DetNet specifications. At the moment, the 5GS may allow for the translation of MinBandwidth to GFBR, MaxLatency to PDB, and MaxLoss to PER. + +### 6.5.3 Procedures + +This solution considers both the case where the DetNet controller is in a different domain from the 5GS and the case where it is in the same trust domain as the 5GS. Depending on whether the DetNet controller is within the 5GS domain or not, the NEF may be employed. The NEF may optionally be used, according to the TR's conclusion. + +#### 6.5.3.1 DetNet controller in a different domain from the 5GS + +Using the Setting up an AF session with required QoS procedure as described in Figure 4.15.6.6-1 of TS 23.502 [13], the DetNet controller sends to the NEF DetNet configuration parameters defined in clause 6.5.2. The interface between the DetNet controller and the NEF in this situation is different from the procedure described in TS 23.502 [13]. + +![Sequence diagram illustrating the Required TSC QoS procedure for DetNet traffic. The diagram shows interactions between four entities: DetNet Controller, NEF, TSCTSF, and PCF. The sequence starts with the DetNet Controller sending a 'Send DetNet config' message to the NEF. The NEF then performs an 'Authorization' step. Next, the NEF sends an 'Npcf_PolicyAuthorization_Create request' to the PCF. The PCF sends a response back to the NEF. The NEF then sends an 'Ntsctsf_QoSandTSCAssistance_Create(DetNet config) request' to the TSCTSF. The TSCTSF performs a 'Requested PDB calculation' (indicated by a dashed box). The TSCTSF then sends an 'Npcf_PolicyAuthorization_Update request' to the PCF. The PCF sends a response back to the TSCTSF. The TSCTSF then sends an 'Npcf_PolicyAuthorization_Subscribe' message to the PCF. The PCF sends a response back to the TSCTSF. The TSCTSF then sends an 'Npcf_PolicyAuthorization_Notify' message to the PCF. The PCF sends a response back to the TSCTSF. The TSCTSF then sends an 'Ntsctsf_QoSandTSCAssistance_Notify' message to the NEF. The NEF sends a 'Response' back to the DetNet Controller.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +``` + +sequenceDiagram + participant DetNet Controller + participant NEF + participant TSCTSF + participant PCF + + DetNet Controller->>NEF: 1. Send DetNet config + NEF->>NEF: 2. Authorization + NEF-->>PCF: 3. Npcf_PolicyAuthorization_Create request + PCF-->>NEF: 4. Npcf_PolicyAuthorization_Create response + NEF-->>TSCTSF: 3a. Ntsctsf_QoSandTSCAssistance_Create(DetNet config) request + Note right of TSCTSF: Requested PDB calculation + TSCTSF-->>PCF: 3b. Npcf_PolicyAuthorization_Update request + PCF-->>TSCTSF: 4a. Npcf_PolicyAuthorization_Update response + TSCTSF-->>NEF: 4b. Ntsctsf_QoSandTSCAssistance_Create response + NEF-->>DetNet Controller: 5. Response + TSCTSF-->>PCF: 6. Npcf_PolicyAuthorization_Subscribe + PCF-->>TSCTSF: 6a. Npcf_PolicyAuthorization_Subscribe response + TSCTSF-->>PCF: 7. Npcf_PolicyAuthorization_Notify + PCF-->>TSCTSF: 7a. Npcf_PolicyAuthorization_Notify response + TSCTSF-->>NEF: 7b. Ntsctsf_QoSandTSCAssistance_Notify + NEF-->>DetNet Controller: 8. Response + +``` + +Sequence diagram illustrating the Required TSC QoS procedure for DetNet traffic. The diagram shows interactions between four entities: DetNet Controller, NEF, TSCTSF, and PCF. The sequence starts with the DetNet Controller sending a 'Send DetNet config' message to the NEF. The NEF then performs an 'Authorization' step. Next, the NEF sends an 'Npcf\_PolicyAuthorization\_Create request' to the PCF. The PCF sends a response back to the NEF. The NEF then sends an 'Ntsctsf\_QoSandTSCAssistance\_Create(DetNet config) request' to the TSCTSF. The TSCTSF performs a 'Requested PDB calculation' (indicated by a dashed box). The TSCTSF then sends an 'Npcf\_PolicyAuthorization\_Update request' to the PCF. The PCF sends a response back to the TSCTSF. The TSCTSF then sends an 'Npcf\_PolicyAuthorization\_Subscribe' message to the PCF. The PCF sends a response back to the TSCTSF. The TSCTSF then sends an 'Npcf\_PolicyAuthorization\_Notify' message to the PCF. The PCF sends a response back to the TSCTSF. The TSCTSF then sends an 'Ntsctsf\_QoSandTSCAssistance\_Notify' message to the NEF. The NEF sends a 'Response' back to the DetNet Controller. + +Figure 6.5.3.1-1: Required TSC QoS procedure for DetNet traffic + +The procedure of Setting up an AF session with required QoS in Figure 4.15.6.6-1 of TS 23.502 [13] is performed to handle DetNet traffic with the following modifications and clarifications: + +1. The DetNet controller sends DetNet configuration parameters to the NEF. + +- 3a. If the NEF receives DetNet configuration parameters from the DetNet controller, the NEF forwards these received parameters in the Ntsctsf\_QoSAndTSCAssistance\_Create request message with additional DetNet configuration parameters to the TSCTSF. + +NOTE: This procedure works if the DetNet controller provides YANG configuration via Restconf in accordance with IETF DetNet specifications. + +#### 6.5.3.2 DetNet controller in the same trust domain as the 5GS + +Without the NEF, the DetNet controller directly sends to the TSCTSF DetNet configuration parameters. + +![Sequence diagram showing the procedure of requesting TSC QoS for DetNet traffic. The diagram involves three lifelines: DetNet Controller, TSCTSF, and PCF. The sequence starts with the DetNet Controller sending a 'Send DetNet config' message to the TSCTSF. The TSCTSF then performs a 'Requested PDB calculation' (indicated by a dashed box). Next, the TSCTSF sends an 'Npcf_PolicyAuthorization_Update request' to the PCF. The PCF responds with an 'Npcf_PolicyAuthorization_Update response'. The TSCTSF then sends an 'Npcf_PolicyAuthorization_Subscribe' message to the PCF. The PCF responds with an 'Npcf_PolicyAuthorization_Notify' message. Finally, the TSCTSF sends a 'Response' message back to the DetNet Controller.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +``` +sequenceDiagram + participant DetNet Controller + participant TSCTSF + participant PCF + Note right of TSCTSF: Requested PDB calculation + DetNet Controller->>TSCTSF: 1. Send DetNet config + TSCTSF->>PCF: 2. Npcf_PolicyAuthorization_Update request + PCF-->>TSCTSF: 3. Npcf_PolicyAuthorization_Update response + TSCTSF-->>DetNet Controller: 4. Response + TSCTSF->>PCF: 5. Npcf_PolicyAuthorization_Subscribe + PCF-->>TSCTSF: 6. Npcf_PolicyAuthorization_Notify + TSCTSF-->>DetNet Controller: 7. Response +``` + +Sequence diagram showing the procedure of requesting TSC QoS for DetNet traffic. The diagram involves three lifelines: DetNet Controller, TSCTSF, and PCF. The sequence starts with the DetNet Controller sending a 'Send DetNet config' message to the TSCTSF. The TSCTSF then performs a 'Requested PDB calculation' (indicated by a dashed box). Next, the TSCTSF sends an 'Npcf\_PolicyAuthorization\_Update request' to the PCF. The PCF responds with an 'Npcf\_PolicyAuthorization\_Update response'. The TSCTSF then sends an 'Npcf\_PolicyAuthorization\_Subscribe' message to the PCF. The PCF responds with an 'Npcf\_PolicyAuthorization\_Notify' message. Finally, the TSCTSF sends a 'Response' message back to the DetNet Controller. + +**Figure 6.5.3.2-1: Procedure of requesting TSC QoS for DetNet traffic** + +1. If the DetNet controller is considered to be trusted by the operator, it sends DetNet configuration parameters to interact directly with TSCTSF. + +NOTE: This procedure works if the DetNet controller provides YANG configuration via Restconf in accordance with IETF DetNet specifications. + +### 6.5.4 Impacts on existing entities and interfaces + +#### TSCTSF: + +- Needs to support to accept YANG configuration via Restconf from the DetNet controller. +- Needs to support converting DetNet configuration parameters into 5GS QoS parameters. + +#### NEF: + +- (Optional) May support to accept YANG configuration via Restconf from the DetNet controller. + +## 6.6 Solution #6 for Key Issue #2: Solution for provisioning DetNet configuration from the DetNet controller to 5GS + +### 6.6.1 Introduction + +The goal of FS\_DetNet is to achieve deterministic packet forwarding in the wide area network. In order to support DetNet deterministic forwarding mechanism in 5G mobile network and realize wide area certainty, it is necessary to study how to map DetNet parameters to 5GS parameters. + +IETF RFC 9016 [4] defines the information model of the DetNet flow, draft-ietf-detnet-yang [5] defines the configuration, including DetNet flow description, and differentiate service requirements. Clause 5.7 of TS 23.501 [12] defines QoS models and parameters. + +This contribution proposes an enhanced architecture to support the interworking between 5GS and DetNet network. This architecture enhances the function of TSCTSF to support DetNet flow mapping. + +The architecture proposed by this contribution is based on 5GS QoS framework, and maps the DetNet flow to QoS flow. This contribution proposes a QoS parameter mapping method supporting wide area mobile deterministic networks. It also introduces an implementation procedure of DetNet business flow under 5GS QoS framework. + +### 6.6.2 Functional Description + +![Figure 6.6.2-1: Enhanced architecture diagram showing the 5GS as DetNet node architecture. The diagram illustrates the flow of DetNet configuration from the DetNet controller through the NEF and TSCTSF (with DetNet flow mapping) to the SMF and PCF, which then interact with the RAN and UE. The UPF is also shown as part of the data path.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +The diagram shows the following components and connections: + +- 5GS as DetNet node (dashed box):** Contains UE, RAN, AMF, SMF, UPF, PCF, and TSCTSF. + - UE is connected to RAN. + - RAN is connected to AMF and UPF. + - AMF is connected to UDM, SMF, and RAN. + - SMF is connected to UDM, AMF, PCF, and UPF. + - UPF is connected to SMF and RAN. + - PCF is connected to SMF and TSCTSF. + - TSCTSF is connected to SMF, PCF, and NEF. It contains a green box labeled "DetNet flow mapping". +- External components:** + - DetNet controller:** Connected to NEF. + - NEF:** Connected to TSCTSF and DetNet controller. + - DetNet node (cloud):** Connected to UPF. + +Figure 6.6.2-1: Enhanced architecture diagram showing the 5GS as DetNet node architecture. The diagram illustrates the flow of DetNet configuration from the DetNet controller through the NEF and TSCTSF (with DetNet flow mapping) to the SMF and PCF, which then interact with the RAN and UE. The UPF is also shown as part of the data path. + +**Figure 6.6.2-1: Enhanced architecture** + +As shown in Figure 1, the TSC architecture based on 3GPP Rel-17 supports DetNet function by the following function enhancement: + +- Enhance the function of TSCTSF to support DetNet flow mapping. +- Realize the information interaction between TSCTSF and DetNet control plane through NEF. +- Enhance the function of NEF to support the transmission of DetNet flow configuration. The DetNet controller sends the DetNet related parameters of the DetNet flow to NEF and NEF transports them to TSCTSF. +- Enhance the function of NEF to support the authentication of DetNet controller. +- Enhance the function of NEF to convert the IETF protocols Netconf [8] or Restconf [9] on the interface between DetNet controller and NEF to HTTP protocol on N85 interface. + +The DetNet controller transmits the forwarding requirements of the DetNet flow to TSCTSF. TSCTSF completes the QoS mapping from the service requirements of the DetNet flow to 5GS QoS flow. + +- Generate QoS policies for deterministic service forwarding and forward them to PCF. According to the framework of policy control, PCF sets up the QoS. Then it can realize the certainty of wide area. + +DetNet controller distributes the information model of the DetNet flow to NEF, using IETF protocols Netconf [8] or Restconf [9]. + +- NEF sends the information model of the DetNet flow to TSCTSF over N85. + +![Diagram illustrating the function and mapping method in the TSCTSF. A central green box labeled 'DetNet flow mapping module' is shown. To its left, under the heading '5GS Qos flow parameters', are 'Packet Filter Set', 'Qos profile', 'GFBR', '5QI-PDB', and '5QI-Error Rate'. To its right, under the heading 'DetNet flow parameters', are 'DetNet flow description (source/destination address, source/destination port, flow label, DSCP priority, protocol type, Spi value of IPSec)', 'DetNet flow service requirements', 'Minimum guaranteed bandwidth', 'Maximum Latency', and 'Maximum packet loss'. Arrows indicate the mapping from right to left: DetNet flow description to Packet Filter Set, DetNet flow service requirements to Qos profile, Minimum guaranteed bandwidth to GFBR, Maximum Latency to 5QI-PDB, and Maximum packet loss to 5QI-Error Rate.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Diagram illustrating the function and mapping method in the TSCTSF. A central green box labeled 'DetNet flow mapping module' is shown. To its left, under the heading '5GS Qos flow parameters', are 'Packet Filter Set', 'Qos profile', 'GFBR', '5QI-PDB', and '5QI-Error Rate'. To its right, under the heading 'DetNet flow parameters', are 'DetNet flow description (source/destination address, source/destination port, flow label, DSCP priority, protocol type, Spi value of IPSec)', 'DetNet flow service requirements', 'Minimum guaranteed bandwidth', 'Maximum Latency', and 'Maximum packet loss'. Arrows indicate the mapping from right to left: DetNet flow description to Packet Filter Set, DetNet flow service requirements to Qos profile, Minimum guaranteed bandwidth to GFBR, Maximum Latency to 5QI-PDB, and Maximum packet loss to 5QI-Error Rate. + +**Figure 6.6.2-2: Function and mapping method in the TSCTSF** + +Based on 5GS QoS management framework, the mapping relationship between DetNet flow and 5GS QoS flow is shown in Figure 2: + +- The DetNet IP flow description identifies the DetNet flow; it can be mapped to Packet filter Set under 5GS QoS framework. +- The traffic specification requirements of DetNet flow are specific service requirements for specific flows. It can be mapped to QoS profile under 5GS QoS framework. The specific mapping methods are as follows: + - The minimum guaranteed bandwidth is mapped to GFBR in QoS profile. + - The maximum delay is mapped to 5QI-PDB in QoS profile. + - The maximum packet loss is mapped to 5QI-Error Rate in QoS profile. + +The above mapping functions are executed by the DetNet flow mapping function extended in TSCTSF. + +DetNet controller determines the end-to-end path and ensures the end-to-end requirements of the DetNet flow. 5GS should strictly ensure the requirements. + +### 6.6.3 Procedures + +As shown in Figure 3, it introduces how the DetNet service flow is implemented on the enhanced architecture. + +![Sequence diagram illustrating the implementation process of DetNet flow forwarding under 5GS QoS framework. The diagram is divided into Control plane and User plane. Lifelines include UE, DetNet controller, NEF, TSCTSF (DetNet flow mapping function), PCF, SMF, AN/UPF, and DetNet Node. The process involves: 1. DetNet controller sends deterministic transmission requirements and parameters to 5GS (via NEF); 2. TSCTSF maps DetNet service requirements to 5GS QoS parameters; 3. TSCTSF sends the mapped QoS policy to PCF; 4. PCF sends QoS policy to SMF and AMF for execution; 5. SMF sends the QoS policy to the user plane for execution (via AN/UPF); 6. Packets transmission, fulfilled the DetNet flow forwarding requirements (from UE to DetNet Node).](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Sequence diagram illustrating the implementation process of DetNet flow forwarding under 5GS QoS framework. The diagram is divided into Control plane and User plane. Lifelines include UE, DetNet controller, NEF, TSCTSF (DetNet flow mapping function), PCF, SMF, AN/UPF, and DetNet Node. The process involves: 1. DetNet controller sends deterministic transmission requirements and parameters to 5GS (via NEF); 2. TSCTSF maps DetNet service requirements to 5GS QoS parameters; 3. TSCTSF sends the mapped QoS policy to PCF; 4. PCF sends QoS policy to SMF and AMF for execution; 5. SMF sends the QoS policy to the user plane for execution (via AN/UPF); 6. Packets transmission, fulfilled the DetNet flow forwarding requirements (from UE to DetNet Node). + +**Figure 6.6.3-1: Implementation process of DetNet flow forwarding under 5GS QoS framework** + +- DetNet controller sends deterministic transmission requirements and parameters to 5GS. +- The enhanced parameter mapping function on TSCTSF maps DetNet service requirements into 5GS QoS flow parameters. +- TSCTSF sends the mapped QoS policy(include flow description, and QoS requirements for the service flow as 3GPP Qos framework required) to PCF. +- PCF sends QoS policy to SMF. +- SMF send QoS policy to the user plane for execution. +- Transmit wide area deterministic service, fulfilled DetNet service requirements. + +### 6.6.4 Impacts on existing entities and interfaces + +The suggested solution mainly focuses on the TSCTSF function enhancement and 5GS QoS framework extension. + +Enhance the function of TSCTSF to support: + +- Maps DetNet flow requirements to 5GS requirements. + +Use DetNet controller to achieve: + +- Realize the information interaction between TSCTSF and DetNet control plane through NEF. +- NEF: the impacts are FFS. + +### 6.6.5 Solution evaluation + +- On the basis of the 5GS QoS framework, support DetNet service and DetNet deterministic wide area forwarding through function enhancement. +- Implement the mapping mechanism from DetNet parameters to mobile network parameters. +- Support the interworking between mobile network and DetNet network. +- Realize the L3 deterministic forwarding on mobile network. + +## 6.7 Solution #7 for Key Issue #2: Detnet configuration mapping to 5GS parameters + +### 6.7.1 Introduction + +This solution is for Key Issue #2, Provisioning DetNet configuration from the DetNet controller to 5GS. + +- Which parameters provided by the DetNet controller should be mapped into which 5G parameters. +- How the 5GS finds the PDU Sessions corresponding to the given DetNet configuration. +- What mechanisms are used in 5GS to configure the system according to the configuration provided by the DetNet controller. + +This solution follow the assumption in clause 4. + +- Existing 3GPP routing mechanisms can be re-used for DetNet; no new routing function in the 3GPP system is to be defined. +- The existing filtering mechanisms can be re-used in the UE and in the UPF to identify the traffic for QoS differentiation. +- IP based DetNet traffic is carried in PDU Sessions of IP type. +- The mapping functionality for DetNet is realized in the TSCTSF. +- The solutions should reuse the functionality of the TSC framework defined in Release 17 where applicable. +- The solutions shall not have any 5G AN and UE impacts + +### 6.7.2 Functional Description + +In this solution, the TSCTSF receives the configuration from Detnet controller and map it to service requirement and TSCAC. + +![Diagram showing the flow of configuration and service requirements between Detnet controller CPF, Detnet node (TSCTSF), and PCF.](68ea9310fb829dd6007635a6cd4ea2ad_img.jpg) + +``` +graph LR; A[Detnet controller CPF] -- "Configuration (RFC9016/detnet-yang)" --> B[Detnet node (TSCTSF)]; B -- "Service requirement, TSCAC" --> C[PCF]; +``` + +Diagram showing the flow of configuration and service requirements between Detnet controller CPF, Detnet node (TSCTSF), and PCF. + +**Figure 6.7.2-1: Parameters mapping** + +The Detnet flow-related parameters is defined in RFC 9016 [4], and expressed in draft-ietf-detnet-yang [5]. + +The service requirement needed for PCF is defined in clause 5.6.2.7 (MediaComponent) and clause 5.6.2.8 (MediaSubComponent) of TS 29.514 [15]. The TSCAC is defined in TS 23.501 [12]. + +The table 6.7.2-1 show the mapping relation between Detnet configuration defined in clause 5 of RFC 9016 [4] and 5G QoS parameters (service requirement and TSCAC). + +Table 6.7.2-1: Mapping between DetNet parameters and 5GS parameters + +| DetNet parameters | | 5G Qos parameters | | Note | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------|--------------------------------------------| +| DetNet flows attributes | | | | | +| clause 5.1 | DnFlowID | | N/A | | +| clause 5.2 | DnPayloadType | | N/A | IP | +| clause 5.3 | DnFlowFormat | | N/A | IP | +| clause 5.4 | DnFlowSpecification
a. SourceIpAddress
b. DestinationIpAddress
c. Ipv6FlowLabel
d. Dscp
e. Protocol
f. SourcePort
g. DestinationPort
h. IPSecSpi | TS 29.514 [15] | MediaSubComponent | Applied for both south and north interface | +| Clause 5.5 | Traffic Specification of the DetNet Flow | | | | +| | Interval | | Periodicity in TSCAC | | +| | MaxPacketsPerInterval | | Used for calculate the maxTscBurstSize | | +| | MaxPayloadSize | | Used for calculate the maxTscBurstSize | | +| | MinPayloadSize | | ? | | +| | MinPacketsPerInterval | | ? | | +| Clause 5.6 | DnFlowEndpoints | | ? | End to End? | +| Clause 5.7 | DnFlowRank | TS 29.514 [15] | tscPrioLevel | | +| Clause 5.8 | DnFlowStatus | TS 29.514 [15] | fStatus | | +| DetNet flows requirement attributes | | | | | +| Clause 5.9 | DnFlowRequirements | | | | +| | MinBandwidth | | GFBR | | +| | MaxLatency | | Use this parameters to determine the 5GS node latency
Note 3 | End to End? | +| | MaxLatencyVariation | | ? | | +| | MaxLoss | TS 29.514 [15] | maxPacketLossRateDI
maxPacketLossRateUI | | +| | MaxConsecutiveLossTolerance | TS 23.501 [12] | Survival time | | +| | MaxMisordering | | ? | | +| Clause 5.10 | DnFlowBiDir | | ? | | + +NOTE 1: "?" show how to map is unclear. + +NOTE 2: "End to End" means this value is not the parameters for Detnet node. + +NOTE 3: TSCTSF use MaxLatency and configuration to determine the 5GS detnet node latency. + +The TSCTSF uses the incoming and outgoing interfaces in the draft-ietf-detnet-yang [5] to determine the related PDU Session(s) and Flow direction. If the incoming and outgoing interface are related the UE side, the TSCTSF separate it to two PDU Sessions, one for UL and one for DL. + +NOTE: For the IP type traffic, the incoming interface is optional. If there is no incoming interface for UL traffic, the TSCTSF determine the PDU session according to configuration, topology information learned from KI#1 and source IP address in the DnFlowSpecification. + +Editor's note: How the map the end to end Detnet parameters to 5GS parameters is FFS. + +Editor's note: Which parameters in the table are carried in draft-ietf-detnet-yang [5] to Detnet node is FFS. + +### 6.7.3 Procedures + +The procedure in clauses 4.15.6 and 4.15.6.6a of TS 23.502 [13] are re-used with the following enhancement: + +- The Detnet controller send the Detnet configuration to TSCTSF. + +NOTE: In this solution, there is no NEF between TSCTSF and Detnet controller.. + +### 6.7.4 Impacts on existing entities and interfaces + +TSCTSF: + +- mapping DetNet flow configuration to 5GS QoS requirements and TSC parameters. + +Editor's note: Additional impacts are FFS. + +## 6.8 Solution #8 for Key Issues #1 and #2: 5GS DetNet Node IP Operation, Management and Exposure + +### 6.8.1 Introduction + +The 5G System supports IETF DetNet deterministic networking by abstracting the whole 5GS as a DetNet Node. The 5GS DetNet Node is comprised of a single UPF and a number of UEs connected to it with IP PDU Sessions. It supports DetNet IP data plane and forwarding sublayer operations, essentially acting as an IP router with specific QoS and management capabilities that are exposed to the DetNet controller. + +No UE impact is required even though the device including the UE may support also DS TT for the sake of taking benefit from Rel-17 TSC related Time synch work. While the UE is logically part of the 5GS DetNet Node, the device including the UE may also act as a separate DetNet capable IP router node as depicted in Figure 6.8.1-2. + +The architecture of the 5GS DetNet Node is shown in Figure 6.8.1-1. + +![Figure 6.8.1-1: 5GS DetNet Node architecture diagram. A dashed box labeled '5GS DetNet Node' contains the following components: PCF, TSCTSF, NEF (dashed box), DetNet controller (outside), AMF, SMF, UDM, RAN, UPF, NW-TT, DS-TT, and UE. Connections: DS-TT connects to an external DetNet Node (left) and UE; UE connects to RAN; RAN connects to AMF and UPF; AMF connects to SMF and PCF; SMF connects to UDM and UPF; PCF connects to TSCTSF; TSCTSF connects to NEF; NEF connects to DetNet controller (outside); UPF connects to NW-TT; NW-TT connects to an external DetNet Node (right). Circled numbers 1 and 2 are at the DS-TT and NW-TT respectively.](718be1eb075833deb7a3b80729a06264_img.jpg) + +Figure 6.8.1-1: 5GS DetNet Node architecture diagram. A dashed box labeled '5GS DetNet Node' contains the following components: PCF, TSCTSF, NEF (dashed box), DetNet controller (outside), AMF, SMF, UDM, RAN, UPF, NW-TT, DS-TT, and UE. Connections: DS-TT connects to an external DetNet Node (left) and UE; UE connects to RAN; RAN connects to AMF and UPF; AMF connects to SMF and PCF; SMF connects to UDM and UPF; PCF connects to TSCTSF; TSCTSF connects to NEF; NEF connects to DetNet controller (outside); UPF connects to NW-TT; NW-TT connects to an external DetNet Node (right). Circled numbers 1 and 2 are at the DS-TT and NW-TT respectively. + +Figure 6.8.1-1: 5GS DetNet Node + +![Diagram of 5GS DetNet Node and a separate 5G Mobile Device DetNet Node with a logical link between them. The diagram shows a '5G Mobile Device Logical DetNet Node' (left) and a '5GS Logical DetNet Node' (right). The mobile device contains a 'Router' with 'Ethernet interface(s)' and a 'Device 3GPP interface'. The 5GS node contains a 'UPF' with 'N6 IP interface(s)'. A 'Physical Device' box encloses the Router and a 'UE' (User Equipment). The UE has a '5GS 3GPP interface'. A 'Logical 3GPP link' connects the Device 3GPP interface to the 5GS 3GPP interface. A '5G Radio Link' connects the UE to the UPF.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Diagram of 5GS DetNet Node and a separate 5G Mobile Device DetNet Node with a logical link between them. The diagram shows a '5G Mobile Device Logical DetNet Node' (left) and a '5GS Logical DetNet Node' (right). The mobile device contains a 'Router' with 'Ethernet interface(s)' and a 'Device 3GPP interface'. The 5GS node contains a 'UPF' with 'N6 IP interface(s)'. A 'Physical Device' box encloses the Router and a 'UE' (User Equipment). The UE has a '5GS 3GPP interface'. A 'Logical 3GPP link' connects the Device 3GPP interface to the 5GS 3GPP interface. A '5G Radio Link' connects the UE to the UPF. + +**Figure 6.8.1-2: 5GS DetNet Node and a separate 5G Mobile Device DetNet Node with a logical link between them** + +The externally visible interfaces of the 5GS DetNet Node are located either at the UPF and supported by a NW-TT (2) or at the UEs and for UEs they may be supported by a DS-TT (1) when Rel-17 TSC features are required. Both UPF and UE side interfaces may be connected to other DetNet Nodes, which may be IP routers or hosts. Each interface has a distinct identity and is configured with IPv4 and/or IPv6 address information. + +The 5GS DetNet Node is able to forward IP packets between any of its interfaces according to DetNet IP data plane requirements. The TSCTSF maps the configuration between the DetNet controller and the 5GS DetNet Node, maintaining the overall configuration, capability and state information of the Node. It exposes the 5GS DetNet Node's interfaces and their associated IP address and IP forwarding information to the DetNet controller. It receives DetNet flow information including flow identification and QoS requirements from the DetNet controller and sets up the 5G user plane accordingly. + +The 5GS DetNet Node may support PTP time synchronization if the 5GS is configured to act as a PTP instance (operating as a boundary clock, peer-to-peer transparent clock or end-to-end transparent clock according to 3GPP Release 17 procedures applicable to IP PDU Sessions). The PTP time synchronization processes are orthogonal to DetNet IP QoS or IP routing (forwarding) procedure but both can be used together with the same TSCTSF, and NW-TT instances. Support of PTP time synchronization is not further detailed in the solution as it relies on Rel-17 features. + +The granularity of the 5GS DetNet Router is per UPF for each network instance or DNN/S-NSSAI. + +### 6.8.2 Functional Description + +5GS acts as a DetNet Node supporting IP Data Plane and forwarding sub-layer functionality. To support IP Data Plane, it acts as a Layer 3 IP Router. When integrated with IETF DetNet network, 5GS acts as one or more DetNet Nodes of the DetNet network (more than one DetNet node when there are more than one UPF). The 5GS DetNet Node is composed of one or more interfaces on a single UPF (i.e. PSA) side supported by NW-TT, the user plane tunnel between the UEs and the UPF (including 5G RAN and possibly intermediate UPF(s)), the interfaces on the UE side and possibly the DS-TT (s) when Rel-17 TSC time synchronization is needed. For each 5GS DetNet Node of a DetNet network, the interfaces on NW-TT support the connectivity to the DetNet network, and the interfaces on UE side are associated to the PDU Session providing connectivity to the DetNet network. + +The 5GS DetNet Node operation and management follow the procedures of 5GS Bridge and Support of integration with TSN as described in clause 5.28 of TS 23.501 [12] with the following differences and clarifications: + +- The logical networking entity is called 5GS DetNet Node and it has a unique Node ID. +- 5GS DetNet Node supports IP packet forwarding as an IP router and uses IP PDU Sessions. +- TSCTSF takes the role of the 5GS DetNet Node control and management entity and implements the control and management interface to the DetNet controller. +- Port numbers are used to create interface IDs that uniquely identify IP interfaces on UE and NW-TT. + +- The association between the UE/ IP address and (Ipv6) prefix, 5GS DetNet Node ID and port number based interface ID is maintained at TSCTSF and further used to assist to bind the DetNet flow IP traffic with the UE's IP PDU session. + +#### 5GS DetNet Node Interface IP addressing and IP Routing information management + +The User Plane Node and Port Management Information Container data models are extended with IP address and IP routing/forwarding information. + +For each UPF/NW-TT side interface the following information is provided: + +- Type of interface. +- MAC address. +- IP address (Ipv4 and/or Ipv6). +- IP Prefix (Ipv4 and/or Ipv6). +- Neighbour MAC and IP addresses. +- MTU size. +- IP forwarding table entries where this interface or one of its directly connected neighbours is the next hop. + +For each UE side interface the following information is provided: + +- Type of interface = "3GPP" (or any new type identifier allocated for this purpose): + - information specific to "3GPP" interface type i.e. Role = "Network". +- For Ipv4: UE Ipv4 address. +- For Ipv6: UE interface id and Ipv6 Prefix. +- MTU size. +- IP forwarding table entries where this interface is the next hop based on framed route and Ipv6 prefix delegation information. + +This allows the TSCTSF to learn for each DetNet Node interface the interface type, its IP address information and on UPF/NW-TT interfaces also neighbour information additionally useful for topology discovery. + +The DetNet controller needs to be aware of the data path taken by IP flows exchanged between Detnet hosts in order to be able to manage the QoS/resource reservation across the whole end-to-end path. For instance, the DetNet controller needs to know that if the 5GS DetNet Node receives an IP packet with a particular destination IP address from one of its UE interfaces, from which egress interface to which next hop DetNet Node it will forward it. + +For this purpose, for the UPF/NW-TT side interfaces, also the IP forwarding table entries are optionally provided including the following information: + +- IP address/prefix; +- address/prefix length; +- Destination IP interface or next hop IP address. + +NOTE 1: Additionally, other information about the routes can be included such as cost or delay, or the source of the routing information (static vs. dynamic). + +NOTE 2: All the above information can be included in Port Management Information Containers (PMIC) while it might be more efficient to use User Plane Node Management Information Containers (UMIC) to exchange the information for all NW-TT interfaces in a single container. + +While NW-TT is not necessary for IP routing/forwarding on N6, in the solution NW-TT is used for exposing the interface and interface specific routing/forwarding information to TSCTSF. + +On UE side interfaces, also the following is optionally exposed to the TSCTSF for each interface: + +- Framed routes associated with the interface. +- IPv6 prefixes delegated via the interface. + +#### TSCTSF exposing information to the DetNet controller + +After it has learned about the 5GS DetNet Node interfaces and their IP routing/forwarding information, the TSCTSF combines all the information into a single representation and makes it available for the DetNet controller. The information can be exposed to the DetNet controller using IETF RFC 8343, 8344 and 8345 YANG data models. RFC 8343 YANG may need to be extended with new interface type "3GPP" and any new information associated with it. + +Based on this information the DetNet controller learns 5GS DetNet Node interfaces, their IP addresses and IP prefixes, and the 5GS DetNet Node IP routing/forwarding- status. Using this information and similar information collected from the other DetNet IP data plane nodes, the DetNet controller is able to determine with DetNet traffic flows with given source and destination addresses are to be forwarded via the 5GS DetNet Node and which ingress and egress interfaces they will use. + +The way to exchange PMIC and UMIC between the TSCTSF and the NW-TT (via PCF, SMF, etc.) is as defined in Rel-17 for TSC. The difference is that the content of the PMIC/UMIC may differ as explained above. + +### 6.8.3 Procedures + +![Sequence diagram illustrating the procedures for 5GS DetNet Node interface and IP routing information learning and configuration. The diagram shows interactions between UE, SMF, UPF/NW-TT, UDM, PCF, and TSCTSF. The process involves four steps: 1. PDU session establishment procedure, UE IP interface port number allocation, and 5GS DetNet Node ID allocation as the first UE joins the 5GS DetNet node. 2. SMF provides the DetNet Node ID and UE info [UE residence time], port number, UE IP address. TSCTSF creates a new AF session associated with UE IP address and communicates with NW-TT. 3. NW-TT interface(s) IP address and IP routing information learning and configuration. 4. TSCTSF combines 5GS DetNet Node interface, IP address and IP routing information and makes it available for the DetNet controller.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant UPF/NW-TT + participant UDM + participant PCF + participant TSCTSF + + Note right of UPF/NW-TT: 1. PDU session establishment procedure +UE IP interface port number allocation. +5GS DetNet Node ID allocation as the first UE joins the 5GS DetNet node + Note right of SMF: 2. SMF provides the DetNet Node ID and UE info [UE residence time], port number, UE IP address. TSCTSF creates a new AF session associated with UE IP address and communicates with NW-TT. + Note right of UPF/NW-TT: 3. NW-TT interface(s) IP address and IP routing information learning and configuration. + Note right of TSCTSF: 4. TSCTSF combines 5GS DetNet Node interface, IP address and IP routing information and makes it available for the DetNet controller. + +``` + +Sequence diagram illustrating the procedures for 5GS DetNet Node interface and IP routing information learning and configuration. The diagram shows interactions between UE, SMF, UPF/NW-TT, UDM, PCF, and TSCTSF. The process involves four steps: 1. PDU session establishment procedure, UE IP interface port number allocation, and 5GS DetNet Node ID allocation as the first UE joins the 5GS DetNet node. 2. SMF provides the DetNet Node ID and UE info [UE residence time], port number, UE IP address. TSCTSF creates a new AF session associated with UE IP address and communicates with NW-TT. 3. NW-TT interface(s) IP address and IP routing information learning and configuration. 4. TSCTSF combines 5GS DetNet Node interface, IP address and IP routing information and makes it available for the DetNet controller. + +Figure 6.8.3-1 + +1. PDU Session Establishment as defined clause 4.3.2.2.1-1 of TS 23.502 [13] is used to establish a PDU Session serving for TSC. + +The SMF may determine the need to use dedicated resources (e.g. dedicated UPF(s)) for the 5GS DetNet Router based on local policies associated with the DNN and/or S-NSSAI. + +During this procedure, the SMF selects a UPF, which supports functions as defined in clause 5.28.1 of TS 23.501 [12], for the PDU Session. + +During this procedure, the SMF receives the allocated port number for UE IP interface and user-plane Node ID from the UPF: The UPF allocates the port number for UE, after receiving N4 Session Establishment Request message. The UPF retrieves also the user-plane Node ID (from the NW-TT) and provides its value to the SMF via N4 Session Level Reporting. + +During this procedure the SMF may also receive the UE-DS-TT residence time (if a DS TT is supported) + +2. The SMF sends the information received in step 1 to the TSCTSF via PCF (via Npcf\_SMPolicyControl service as defined in clause 4.16 of TS 23.502 [13]). The TSCTSF stores the binding relationship between 5GS user-plane Node ID, port number and UE IP address for future configuration. The TSCTSF requests creation (using the Npcf\_PolicyAuthorization service as defined in clause 4.16.5.1 of TS 23.502 [13]) of a new AF session associated with the UE IP address and may subscribe for TSC events over the newly created AF session. + +Using the 5GS user-plane Node ID the TSCTSF subscribes with the NW-TT for receiving user plane node management information changes for the 5GS DetNet Node indicated by the 5GS user-plane Node ID as described in clause 5.28.3.1 of TS 23.501 [12]. + +After receiving a User plane node Management Information Container (UMIC) containing the NW-TT port numbers, the TSCTSF subscribes with the NW-TT for receiving NW-TT port management information changes for the NW-TT port indicated by each of the NW-TT port numbers as described in clause 5.28.3.1 of TS 23.501 [12]. + +The TSCTSF can use any Npcf session (any PDU Session) to subscribe with the NW-TT for node or port management information notifications. Similarly, the UPF can use any N4 session (any PDU Session) to send node or port management information notifications. + +3. The TSCTSF learns the port management capabilities and interface information of each NW-TT interface. If NW-TT interfaces have locally available IP address or IP routing information, the TSCTSF learns it from the NW-TT. +4. The TSCTSF now has the up-to-date IP address and IP routing information of each UE and NW-TT interface. It combines it and makes it available for the DetNet controller. + +### 6.8.4 Impacts on services, entities and interfaces + +TSCTSF: + +- Learns IP addressing and IP routing information on NW-TT using extended Port Management Information Container data model. +- Maintains the 5GS DetNet Node interface, IP addressing and IP routing information base. +- Exposes the 5GS DetNet Node interface, IP addressing and IP routing information to the DetNet controller. + +SMF: + +- None. + +NW-TT: + +- Maintains IP address management and IP routing (forwarding) configuration for the NW-TT related IP interface(s). Provides information to TSCTSF using extended User Plane Node and Port Management Information Container data models. + +# 7 Conclusions + +## 7.1 General + +The following bullet points summarize the principles for the way forward: + +- YANG models over Netconf or Restconf are used between the TSCTSF and the DetNet controller. +- 3GPP does not standardize any signalling mechanism to include the NEF into the signalling path between the TSCTSF and the DetNet controller. If NEF functionality is desired, the relevant functions such as the authentication, authorization and potential throttling of signalling can be achieved by including such functionality in the TSCTSF depending on the needs of the given deployment. +- The TSCTSF terminates the interface towards the DetNet controller. The TSCTSF collects and provides exposure information to the DetNet controller. The TSCTSF collects the information from the UPF/NW-TT and the SMF with extensions to the 5GC data models or information elements as required. The entity reporting UPF N6 interface related information to the TSCTSF is NW-TT as in Rel-17 TSC. +- The TSCTSF may use the e2e traffic requirements in the YANG configuration, and based on a pre-configured mapping, derive 5GS requirements from them. +- It can be possible for the 5GS to verify in the TSCTSF whether the explicit routing information provided by the DetNet controller is in line with the 5GS mapping of IP addresses to PDU sessions. Apart from the verification, the 5GS routing is not modified by the DetNet controller in line with the agreed scope of the work. +- Based on existing specifications, 5GS DetNet Node can forward via its UE side interface IP packets destined not only to the UE's IP address or prefix but also to other IP prefixes according to 3GPP 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 and by TSCTSF to the DetNet controller. + +The following figure illustrates the DetNet architecture. + +![Figure 7.1-1: DetNet Architecture diagram showing the 5GS logical DetNet Node containing UE, RAN, AMF, SMF, NW-TT, and UPF, connected to a DetNet end system and a DetNet network via a CPF: DetNet controller and TSCTSF.](446100c084b94817a19c319fa776b412_img.jpg) + +The diagram illustrates the DetNet Architecture. A dashed box labeled "5GS logical DetNet Node" contains the following components: + + +- A **UE** (User Equipment) connected to a **RAN** (Radio Access Network). +- The **RAN** is connected to an **AMF** (Access and Management Function). +- The **AMF** is connected to an **SMF** (Session Management Function). +- The **SMF** is connected to a **NW-TT** (Network Termination) which is part of the **UPF** (User Plane Function). +- Both the **SMF** and the **UPF** are connected to a **TSCTSF** (Traffic Steering and Control Function). + + Outside the dashed box: + + +- The **UE** is connected to a **DetNet end system**. +- The **UPF** is connected to a cloud representing the **DetNet network**. +- The **TSCTSF** is connected to a **CPF: DetNet controller**. +- The **CPF: DetNet controller** is also connected to the **DetNet network**. + +Figure 7.1-1: DetNet Architecture diagram showing the 5GS logical DetNet Node containing UE, RAN, AMF, SMF, NW-TT, and UPF, connected to a DetNet end system and a DetNet network via a CPF: DetNet controller and TSCTSF. + +Figure 7.1-1: DetNet Architecture + +## 7.2 Key Issue #1: 5GS DetNet node reporting + +The 5GS is exposed by the TSCTSF to the DetNet controller as a router on a per UPF granularity. The node may be identified by a Node ID. The interfaces correspond to the PDU Sessions (and to the network side interfaces (i.e. including the interfaces of UPF and NW-TT). Each interface is identified by an interface identifier. + +The following information may be reported from TSCTSF to DetNet controller for each interface. + +- Type of interface. + +- IP address. +- subnet (prefix length). +- Neighbour address (in case of network side interfaces). +- MAC address (in case of network side interfaces). +- MTU size. + +The TSCTSF collects the information from the UPF/NW-TT and the SMF re-using the existing procedures in Rel-17 TSC, with the addition of new parameters as needed. + +## 7.3 Key Issue #2: Provisioning DetNet configuration from the DetNet controller to 5GS + +The parameters are mapped in the TSCTSF as follows. + +NOTE 1: See Clause 7.1 on mapping the end to end requirement to per node requirement. + +- Max-latency to Required delay. +- Min-bandwidth to GFBR. +- Max-loss to Required PER (new in Rel-18). +- Max-consecutive-loss-tolerance to Survival time - when such mapping is possible, such as when there is only a single packet per interval. Interval to Periodicity (in TSC info). +- max-pkts-per-interval \* (max-payload-size + protocol header size) to Max burst size. +- max-pkts-per-interval \* (max-payload-size + protocol header size)/ Interval to MFBR. +- DetNet flow specification to 3GPP flow description (also including the DSCP value and optionally IPv6 flow label and Ipsec SPI). + +The TSCTSF uses the identity of the incoming and outgoing interfaces to determine the affected PDU Session(s) and whether the flow is uplink or downlink. The TSCTSF also determines if the flow is UE to UE in which case two PDU Sessions will be affected for the flow; in that case the TSCTSF breaks up the requirements to individual requirements for the PDU Sessions. The TSCTSF provides the parameters to the PCF re-using the existing procedures in Rel-17 TSC, with the addition of PER. + +NOTE 2: For the IP type traffic, the incoming interface is optional. If there is no incoming interface for UL traffic, the TSCTSF may determine the PDU session according to configuration, topology information (e.g. Next Hop information and so on) learned from KI#1 and source IP address in the DetNet configuration. + +The TSCTSF provides a response to the DetNet controller regarding the success of the configuration setup. Optionally, if 3GPP may defines a new YANG module that extends the IETF DetNet YANG module, the 5GS may provide 3GPP specific status codes for additional information if the requested configuration could not be set up. + +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 for the PDU Session release, and TSCTSF notifies the DetNet controller on status of the flow. + +NOTE 3: 3GPP specifications do not support/ consider routing on the N6 interface, which can be explicitly set by the DetNet controller. The 3GPP specifications do not support the control of the N6 routing, since that has been considered out of scope of 3GPP. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|------------|------------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149E | S2-2200304 | - | - | - | TR skeleton (approved in S2-2200304) | 0.0.0 | +| 2022-02 | SA2#149E | - | - | - | - | Inclusions of documents agreed in SA2#149: S2-2201754, S2-2201755, S2-2201756, S2-2201757, S2-22017548 | 0.1.0 | +| 2022-05 | SA2#151E | - | - | - | - | Inclusions of documents agreed in SA2#151: S2-2204762, S2-2204763, S2-2204764, S2-2204765, S2-2204766, S2-2204767, S2-2204768, S2-2204769 | 0.2.0 | +| 2022-05 | SP#96 | - | - | - | - | Update for presentation to TSG SA#96 for Information | 1.0.0 | +| 2022-08 | SA2#152E | - | - | - | - | Inclusions of documents agreed in SA2#152: S2-2207430, S2-2207431, S2-2205722, S2-2205883, S2-2207433, S2-2207434 | 1.1.0 | +| 2023-01 | SA2#154AHE | - | - | - | - | Inclusions of documents agreed in SA2#154AHE: S2-2201627. | 1.2.0 | +| 2023-03 | SP#99 | - | - | - | - | Update for presentation to TSG SA#96 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-47/raw.md b/raw/rel-18/23_series/23700-47/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c9cee32ca8c8d9763c0e33f04aed77c29b6a5add --- /dev/null +++ b/raw/rel-18/23_series/23700-47/raw.md @@ -0,0 +1,5241 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services; Phase 2 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring the text "5G" in a bold, black font with a green signal wave icon above the "G", and the word "ADVANCED" in smaller, grey capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters "3GPP" in a stylized, bold, black font. The "P" has a red signal wave icon at its base. Below the logo, the text "A GLOBAL INITIATIVE" is written in small, black, capital letters. + +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 ..... | 8 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions of terms and abbreviations ..... | 11 | +| 3.1 Terms..... | 11 | +| 3.2 Abbreviations ..... | 11 | +| 4 Architectural Assumptions and Principles..... | 12 | +| 4.1 Common architectural requirements and principles..... | 12 | +| 4.2 Specific architectural requirements and principles for public safety service in a cell with large number of UEs..... | 12 | +| 5 Key Issues ..... | 13 | +| 5.1 Key Issue #1: Multicast MBS data reception in RRC Inactive state ..... | 13 | +| 5.1.1 Description ..... | 13 | +| 5.2 Key Issue #2: 5MBS MOCN Network Sharing ..... | 13 | +| 5.2.1 Description ..... | 13 | +| 5.3 Key Issue #3: On demand multicast MBS session..... | 13 | +| 5.3.1 Description ..... | 13 | +| 5.4 Key Issue #4: Group message delivery ..... | 14 | +| 5.4.1 Description ..... | 14 | +| 5.5 Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices ..... | 14 | +| 5.5.1 Description ..... | 14 | +| 5.6 Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs..... | 15 | +| 5.6.1 Description ..... | 15 | +| 6 Solutions..... | 15 | +| 6.0 Mapping of Solutions to Key Issues ..... | 15 | +| 6.1 Solution #1: Procedures for RRC Inactive MBS data reception..... | 16 | +| 6.1.1 Introduction ..... | 16 | +| 6.1.2 Functional description ..... | 16 | +| 6.1.3 Procedures ..... | 18 | +| 6.1.3.1 General..... | 18 | +| 6.1.3.2 MBS session creation, multicast session join and session establishment procedure ..... | 19 | +| 6.1.3.3 Moving a UE to RRC Inactive state ..... | 20 | +| 6.1.3.4 Moving a UE to RRC-CONNECTED from RRC Inactive state ..... | 21 | +| 6.1.4 Impacts on services, entities and interfaces..... | 21 | +| 6.2 Solution #2: Procedures for MOCN network sharing..... | 22 | +| 6.2.1 Introduction ..... | 22 | +| 6.2.2 Functional description ..... | 22 | +| 6.2.2.1 General..... | 22 | +| 6.2.2.2 Identifier of the broadcast MBS service ..... | 23 | +| 6.2.2.3 Reception of the broadcast data by the UE..... | 23 | +| 6.2.3 Procedures ..... | 24 | +| 6.2.3.1 General..... | 24 | +| 6.2.3.2 Broadcast Session Establishment..... | 24 | +| 6.2.3.3 Broadcast Session Release..... | 25 | +| 6.2.4 Impacts on services, entities and interfaces..... | 25 | +| 6.3 Solution #3: AF providing assistance information..... | 26 | +| 6.3.1 Introduction ..... | 26 | +| 6.3.2 Functional description ..... | 26 | +| 6.3.3 Procedures ..... | 26 | +| 6.3.4 Impacts on services, entities and interfaces..... | 27 | +| 6.4 Solution #4: MBS session management for RRC Inactive MBS data receiving UE ..... | 27 | +| 6.4.1 Introduction ..... | 27 | +| 6.4.2 Functional description ..... | 27 | + +| | | | +|----------|----------------------------------------------------------------------------------------------------------------|----| +| 6.4.3 | Procedures ..... | 28 | +| 6.4.4 | Impacts on services, entities, and interfaces..... | 29 | +| 6.5 | Solution #5: Mobility Procedures for UE supporting RRC Inactive MBS data reception ..... | 29 | +| 6.5.1 | Introduction ..... | 29 | +| 6.5.2 | Functional description ..... | 29 | +| 6.5.3 | Procedures ..... | 30 | +| 6.5.3.1 | RRc-inactive multicast group member moves within RNA ..... | 30 | +| 6.5.3.2 | RRc-inactive multicast group member UE move out of RNA and within RA..... | 30 | +| 6.5.3.3 | RRc-connected multicast group member UE move to RRc-inactive MBS reception supporting
NG-RAN ..... | 31 | +| 6.5.4 | Impacts on services, entities, and interfaces..... | 31 | +| 6.6 | Solution #6: Reusing the existing assistance info and Qos for RRc Inactive MBS data reception
decision..... | 32 | +| 6.6.1 | Introduction ..... | 32 | +| 6.6.2 | Functional description ..... | 32 | +| 6.6.3 | Procedures ..... | 33 | +| 6.6.4 | Impacts on services, entities and interfaces..... | 33 | +| 6.7 | Solution #7: MOCN RAN Sharing ..... | 33 | +| 6.7.1 | Introduction ..... | 33 | +| 6.7.2 | Functional description ..... | 33 | +| 6.7.3 | Procedures ..... | 33 | +| 6.7.3.1 | General..... | 33 | +| 6.7.3.2 | MBS Session Creation..... | 34 | +| 6.7.3.3 | MBS Session Start for Broadcast..... | 35 | +| 6.7.3.4 | MBS Session Release for Broadcast..... | 36 | +| 6.7.3.5 | Broadcast MBS Session Transport Request ..... | 36 | +| 6.7.4 | Impacts on services, entities and interfaces..... | 37 | +| 6.8 | Solution #8: Allocating and using MOCN TMGI..... | 38 | +| 6.8.1 | Introduction ..... | 38 | +| 6.8.2 | Functional description ..... | 38 | +| 6.8.3 | Procedures ..... | 39 | +| 6.8.3.1 | Procedure for Broadcast using MOCN TMGI..... | 39 | +| 6.8.4 | Impacts on services, entities and interfaces..... | 41 | +| 6.9 | Solution #9: Broadcast services considering MOCN RAN ..... | 41 | +| 6.9.1 | Introduction ..... | 41 | +| 6.9.2 | Functional description ..... | 41 | +| 6.9.3 | Procedures ..... | 41 | +| 6.9.3.1 | General..... | 41 | +| 6.9.3.2 | Broadcast Session Start procedure..... | 42 | +| 6.9.3.3 | Broadcast Session update and release procedure..... | 43 | +| 6.9.4 | Impacts on services, entities and interfaces..... | 44 | +| 6.10 | Solution #10: AF triggered MBS session management ..... | 44 | +| 6.10.1 | Introduction ..... | 44 | +| 6.10.2 | Functional description ..... | 44 | +| 6.10.3 | Procedures ..... | 45 | +| 6.10.3.1 | General..... | 45 | +| 6.10.3.2 | AF triggered MBS Session management procedures with PCC..... | 46 | +| 6.10.3.3 | AF triggered MBS Session management procedures without PCC ..... | 48 | +| 6.10.4 | Impacts on services, entities and interfaces..... | 49 | +| 6.11 | Solution #11: Solution on enabling the on-demand multicast MBS session management..... | 50 | +| 6.11.1 | Introduction ..... | 50 | +| 6.11.2 | Functional description ..... | 50 | +| 6.11.2.1 | Use cases..... | 50 | +| 6.11.3 | Procedures ..... | 51 | +| 6.11.3.1 | on-demand multicast MBS session management ..... | 51 | +| 6.11.4 | Impacts on services, entities and interfaces..... | 52 | +| 6.12 | Solution #12: Group Message Delivery ..... | 52 | +| 6.12.1 | Introduction ..... | 52 | +| 6.12.2 | Functional description ..... | 52 | +| 6.12.3 | Procedures ..... | 52 | +| 6.12.3.1 | General..... | 52 | +| 6.12.3.2 | Group Message Delivery via MBS Broadcast..... | 53 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------------------|----| +| 6.12.3.3 | Modification of previously submitted Group message..... | 55 | +| 6.12.4 | Impacts on services, entities and interfaces..... | 56 | +| 6.13 | Solution #13: Group message delivery for broadcast ..... | 57 | +| 6.13.1 | Introduction ..... | 57 | +| 6.13.2 | Functional description ..... | 57 | +| 6.13.3 | Procedures ..... | 57 | +| 6.13.3.1 | General..... | 57 | +| 6.13.3.2 | Broadcast Session Establishment..... | 58 | +| 6.13.3.3 | Modification of previously submitted group message..... | 59 | +| 6.13.4 | Impacts on services, entities and interfaces..... | 60 | +| 6.14 | Solution #14: MBS coexistence with power saving mechanisms of 5GS ..... | 60 | +| 6.14.1 | Introduction ..... | 60 | +| 6.14.2 | Functional description ..... | 60 | +| 6.14.3 | Procedures ..... | 61 | +| 6.14.4 | Impacts on services, entities and interfaces..... | 62 | +| 6.15 | Solution #15: Solution for coexistence of MBS delivery and power saving mechanisms ..... | 62 | +| 6.15.1 | Functional description ..... | 62 | +| 6.15.2 | Procedures ..... | 63 | +| 6.15.3 | Impacts Analysis ..... | 63 | +| 6.16 | Solution #16: Public Safety services offered over both Broadcast and Multicast transport ..... | 63 | +| 6.16.1 | Description ..... | 63 | +| 6.16.1.1 | General..... | 63 | +| 6.16.1.2 | Functional description..... | 64 | +| 6.16.2 | Procedures ..... | 65 | +| 6.16.2.1 | GCS AS configuration of both Broadcast and Multicast Services ..... | 65 | +| 6.16.2.2 | UE switching from Broadcast Reception to Multicast Reception ..... | 66 | +| 6.16.2.3 | UE switching from Multicast Reception to Broadcast Reception (UE based)..... | 66 | +| 6.16.2.3b | UE switching from Multicast Reception to Broadcast Reception (NG-RAN based)..... | 66 | +| 6.16.3 | Impacts on services, entities and interfaces..... | 67 | +| 6.17 | Solution #17: Performance Improvements for Public Safety..... | 68 | +| 6.17.1 | Introduction ..... | 68 | +| 6.17.2 | Functional description ..... | 68 | +| 6.17.3 | Procedures ..... | 69 | +| 6.17.3.1 | General..... | 69 | +| 6.17.3.2 | UE join multicast MBS session ..... | 70 | +| 6.17.3.3 | UE leave multicast MBS session ..... | 71 | +| 6.17.3.4 | Multicast session leave requested by the network or MBS session release..... | 72 | +| 6.17.3.5 | MBS Session Activation..... | 73 | +| 6.17.3.6 | N2 based Handover and IDLE Mobility..... | 74 | +| 6.17.4 | Impacts on services, entities and interfaces..... | 74 | +| 6.18 | Solution #18: MBS session management for RRC Inactive MBS data receiving UE..... | 75 | +| 6.18.1 | Introduction ..... | 75 | +| 6.18.2 | Functional description ..... | 75 | +| 6.18.3 | Procedures ..... | 76 | +| 6.18.4 | Impacts on services, entities, and interfaces..... | 77 | +| 6.19 | Solution #19: Procedures for Transmission mode for inactive data reception..... | 77 | +| 6.19.1 | Introduction ..... | 77 | +| 6.19.2 | Functional description ..... | 77 | +| 6.19.3 | Procedures ..... | 78 | +| 6.19.3.1 | Moving a UE to RRC Inactive state and providing assistance information to additional RAN nodes (Option A) ..... | 78 | +| 6.19.3.2 | MBS service activation..... | 79 | +| 6.19.3.3 | Triggering MBS service announcement by MB-SMF (Option B) ..... | 80 | +| 6.19.3.4 | MBS session release (Option A and B) ..... | 81 | +| 6.19.4 | Impacts on services, entities and interfaces..... | 81 | +| 6.20 | Solution #20: Registration procedure enhancements for multicast reception..... | 82 | +| 6.20.1 | Introduction ..... | 82 | +| 6.20.2 | Functional description ..... | 82 | +| 6.20.3 | Procedures ..... | 82 | +| 6.20.3.1 | Registration procedures ..... | 82 | +| 6.20.4 | Impacts on services, entities and interfaces..... | 83 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------------------------|-----| +| 6.21 | Solution #21: Mobility Procedures for UE supporting RRC Inactive MBS data reception with the MBS session container ..... | 84 | +| 6.21.1 | Introduction ..... | 84 | +| 6.21.2 | Functional description ..... | 84 | +| 6.21.3 | Procedures ..... | 84 | +| 6.21.3.1 | RRc-inactive multicast group member UE move out of RNA and within RA..... | 84 | +| 6.21.4 | Impacts on services, entities, and interfaces..... | 84 | +| 6.22 | Solution #22: Session management for RRC Inactive MBS data receiving UE..... | 85 | +| 6.22.1 | Introduction ..... | 85 | +| 6.22.2 | Functional description ..... | 85 | +| 6.22.3 | Procedures ..... | 85 | +| 6.22.3.1 | Modification to the MBS session de-activation procedure..... | 85 | +| 6.22.3.2 | Modification to the MBS session (re-)activation procedure..... | 86 | +| 6.22.4 | Impacts on services, entities, and interfaces..... | 86 | +| 6.23 | Solution #23: MBS session activation for RRC Inactive MBS data receiving UE..... | 86 | +| 6.23.1 | Introduction ..... | 86 | +| 6.23.2 | Functional description ..... | 87 | +| 6.23.3 | Procedures ..... | 88 | +| 6.23.4 | Impacts on services, entities, and interfaces..... | 89 | +| 6.24 | Solution #24: Solution based on configuration in RAN to support MOCN RAN Sharing ..... | 89 | +| 6.24.1 | Introduction ..... | 89 | +| 6.24.2 | Functional description ..... | 89 | +| 6.24.3 | Procedures ..... | 89 | +| 6.24.3.1 | General..... | 89 | +| 6.24.3.2 | MBS Session Creation..... | 89 | +| 6.24.3.3 | MBS Session Start for Broadcast..... | 90 | +| 6.24.3.4 | MBS Session Release for Broadcast..... | 91 | +| 6.24.4 | Impacts on services, entities and interfaces..... | 91 | +| 6.25 | Solution #25: Triggering capability limited devices to receive MBS data ..... | 92 | +| 6.25.1 | Introduction ..... | 92 | +| 6.25.2 | Description ..... | 92 | +| 6.25.3 | Procedures ..... | 93 | +| 6.25.3.1 | Periodic or one time transmission of MBS data to capability-limited devices..... | 93 | +| 6.25.3.2 | Deferred activation for aperiodic transmission of MBS data to capability-limited devices..... | 94 | +| 6.25.4 | Impacts on services, entities and interfaces..... | 94 | +| 6.26 | Solution #26: AF selects UEs to be kept in connected mode..... | 95 | +| 6.26.1 | Introduction ..... | 95 | +| 6.26.2 | Description ..... | 95 | +| 6.26.3 | Procedures ..... | 96 | +| 6.26.4 | Impacts on services, entities and interfaces..... | 96 | +| 6.27 | Solution #27: AF providing list of prioritized UEs when creating multicast MBS Session..... | 97 | +| 6.27.1 | Introduction ..... | 97 | +| 6.27.2 | Functional description ..... | 97 | +| 6.27.3 | Procedures ..... | 98 | +| 6.27.4 | Impacts on services, entities and interfaces..... | 99 | +| 6.28 | Solution #28: Session management and Mobility for RRC Inactive MBS data reception ..... | 100 | +| 6.28.1 | Introduction ..... | 100 | +| 6.28.2 | Functional description ..... | 100 | +| 6.28.3 | Procedures ..... | 101 | +| 6.28.3.1 | Moving the UE to RRC Inactive mode..... | 101 | +| 6.28.3.2 | Mobility within/out of RNA area..... | 101 | +| 6.28.4 | Impacts on services, entities, and interfaces..... | 103 | +| 6.29 | Solution #29: MOCN network sharing with a single TMGI..... | 103 | +| 6.29.1 | Introduction ..... | 103 | +| 6.29.2 | Description ..... | 104 | +| 6.29.3 | Procedures ..... | 104 | +| 6.29.4 | Impacts on services, entities and interfaces..... | 106 | +| 6.30 | Solution #30: On demand multicast MBS session set up by MB-SMF ..... | 107 | +| 6.30.1 | Introduction ..... | 107 | +| 6.30.2 | Description ..... | 108 | +| 6.30.3 | Procedures ..... | 110 | +| 6.30.4 | Impacts on services, entities and interfaces..... | 112 | + +| | | | +|-----------------|--------------------------------------------------------------------------------------------------------------|------------| +| 6.31 | Solution #31: Multicast access control for high number of public safety UEs..... | 113 | +| 6.31.1 | Introduction ..... | 113 | +| 6.31.2 | Functional description ..... | 113 | +| 6.31.3 | Procedures ..... | 113 | +| 6.31.4 | Impacts on services, entities, and interfaces..... | 114 | +| 7 | Evaluation ..... | 114 | +| 7.1 | Key Issue #1: MBS session reception in RRC Inactive ..... | 114 | +| 7.1.1 | Overview over available solutions ..... | 114 | +| 7.1.2 | Assistance Information ..... | 117 | +| 7.1.3 | Activation of MBS multicast session ..... | 119 | +| 7.1.4 | Mobility for RRC_Inactive UEs receiving MBS data..... | 120 | +| 7.2 | Key Issue #2: 5MBS MOCN RAN Sharing..... | 121 | +| 7.3 | Key Issue #3: On demand multicast MBS session..... | 125 | +| 7.4 | Key Issue #4: Group message delivery ..... | 126 | +| 7.5 | Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices ..... | 126 | +| 7.6 | Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs..... | 128 | +| 8 | Conclusions..... | 130 | +| 8.1 | Key Issue #1: MBS session reception in RRC Inactive ..... | 130 | +| 8.1.1 | Conclusions ..... | 130 | +| 8.2 | Key Issue #2: MOCN network sharing..... | 131 | +| 8.3 | Key Issue #3: On demand multicast MBS session..... | 132 | +| 8.4 | Key Issue #4: Group message delivery ..... | 132 | +| 8.5 | Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices ..... | 132 | +| 8.6 | Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs..... | 132 | +| Annex A: | Public Safety use cases of large number of UEs in a single cell..... | 134 | +| Annex B: | Change history..... | 135 | + +# 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 + +This Technical Report studies and evaluates further enhancements to the 5G Multicast/Broadcast Architecture in order to provide the following features. + +- Enabling UE's receiving Multicast MBS Session data in RRC Inactive state. +- Study feasible and efficient resource utilization for the same broadcast content to be provided to 5G MOCN network sharing scenarios (i.e. multiple CNs are connected to the same NG-RAN). +- Study whether and how to support on demand multicast MBS session triggered by AF, and efficient resource utilization via 5GC choosing multicast and/or unicast delivery for a certain service. +- Study whether and how to support group message delivery for capability-limited devices, including NEF enhancement, coexistence of existing power saving mechanisms and MBS. +- Study whether there are any identified performance issues for high number of public safety UEs, and if yes study necessary enhancements to 5MBS for that scenario. + +# 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.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [5] 3GPP TR 26.850: "MBMS for Internet of Things (IoT)". +- [6] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [7] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [8] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification". +- [9] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT); Stage 1". +- [10] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [11] 3GPP TS 26.502: "5G Multicast-Broadcast User Service Architecture". +- [12] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [13] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [14] 3GPP TS 33.501: "Security architecture and procedures for 5G system". + +- [15] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2". +- [16] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification". +- [17] 3GPP TS 29.532: "5G System; 5G Multicast-Broadcast Session Management Services; Stage 3". +- [18] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". + +# --- 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] and TS 23.247 [4]. + +## 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] and TS 23.247 [4]. + +# 4 Architectural Assumptions and Principles + +## 4.1 Common architectural requirements and principles + +**Editor's note:** This clause will document any architectural assumptions and principles for the study. + +- Solutions shall build on the 5G System architectural principles as in TS 23.501 [2], including flexibility and modularity for newly introduced functionalities. +- The system shall provide an efficient transport for a variety of multicast and broadcast services. +- Only NR of NG-RAN connected to 5GC is considered as RAT. +- Architecture reference models defined in clause 5.1 of TS 23.247 [4] are used as the baseline architecture for this study. Enhanced Architecture and Solutions in this study shall enable UEs with Rel-17 MBS capability to receive MBS data from Rel-18 architecture/solutions. + +**Editor's note:** The impact on RAN is to be analysed by and coordinated with the relevant RAN WGs. + +**Editor's note:** This study may also include the potential enhancements identified by other WGs or other SIDs (e.g. FS\_5GSAT\_ARCH\_Ph2) in their MBS work that need SA WG2 cooperation. + +## 4.2 Specific architectural requirements and principles for public safety service in a cell with large number of UEs + +Public Safety specific architectural requirements and principles: + +- Solutions shall enable simultaneous reception of MBS session data for a higher number of UEs in a cell than can be operating in RRC\_CONNECTED state, to participate in public safety group calls using MBS-based service. +- Solutions shall ensure that the pre-emption and admission control mechanisms result in public safety UEs being able to complete the setup of the MBS services and then operate according to regulation and operator policy, when a mix of UEs participating in one or more services and/or one or more sessions within each service is present in the cell. + +**NOTE 1:** This issue, which involves other Working Groups, deals with aspects like recognizing which UEs may be moved to RRC\_INACTIVE (service continues via MBS) vs. moved to RRC\_IDLE (service may fail), not impacting the UE while the UE is setting up connections or waiting for the floor (permission to talk), ability to override user settings in order to be able to pre-empt, if necessary, etc. + +- Solutions shall enable provision of assistance information to NG-RAN from the application function (AF) via 5GC, if required/needed. + +**Editor's note:** Solutions may require information to NG-RAN and application function (AF) to enable proper provisioning. This includes, e.g. the SA6 and RAN WGs deciding on, what information to be provided on, which members of a public safety group should stay in RRC\_CONNECTED and which one(s) are candidates for being transitioned to RRC\_INACTIVE. + +- If MBS sessions are temporarily deactivated and are subject to subsequent (re)activation, resulting in UEs in e.g. RRC\_INACTIVE state which need to be (re)-awakened to receive MBS service, solutions may enable simultaneously wake up (for MBS reception) for all the UEs associated with the session. + +**NOTE 2:** For active MBS Session, it is assumed that public safety applications (under the remit of SA6) will initiate minimum number and frequency of requests to transition to RRC\_CONNECTED state to perform uplink transmissions, while Public Safety UEs are in RRC\_INACTIVE state. + +- Whether there is a need for additional solutions to minimize packet loss during MBS reception, this should be addressed together with RAN WGs. + +# 5 Key Issues + +## 5.1 Key Issue #1: Multicast MBS data reception in RRC Inactive state + +### 5.1.1 Description + +In order to provide MBS service to more UEs in a cell, NG RAN could enable UEs within an MBS multicast session to receive MBS session data while in CM-CONNECTED with RRC Inactive state. + +The following aspect will be studied for multicast: + +- Whether, how and what MBS assistance information to provide from 5GC to RAN for an MBS session allowing UEs in CM-CONNECTED with RRC Inactive state to receive MBS content, including the aspect which 5GC NF(s) determine the MBS assistance information and how they do so; +- Whether and how to enhance the current procedures (including mobility related procedures) for MBS session with member UEs in RRC Inactive state. + +NOTE 1: During the study of this key issue, coordination with RAN WGs is needed before final conclusion. + +NOTE 2: RAN WG will determine how the switching for the UEs belonging to MBS session from CM-CONNECTED state to CM-CONNECTED with RRC Inactive state (and vice versa) is performed by the RAN node. + +## 5.2 Key Issue #2: 5MBS MOCN Network Sharing + +### 5.2.1 Description + +According to clause 5.18 of TS 23.501 [2], in a 5G Multi-Operator Core Network (5G MOCN), multiple CNs are connected to the same NG-RAN. + +When the same broadcast content is to be delivered to multiple CNs, the AF will set up multiple broadcast MBS sessions towards those CNs, each CN delivering the same content towards the same shared NG-RAN node. Therefore, for a broadcast MBS Session, the consumed radio resource will be (N-1) times more than needed, where N is the number of CNs involved. + +To investigate the feasibility of avoiding allocating more radio resource than needed, the following aspects need to be considered: + +- Whether and how to assist NG-RAN node to determine the same content is delivered by broadcast MBS Sessions from different 5G CNs? +- Whether and how to assist NG-RAN node to determine which PLMN is used to broadcast the MBS session data? +- Which entity (e.g. AF or other NFs) could provide the assistance parameters to the shared NG-RAN if needed? +- Whether and how to enable the UE to receive the broadcast content from the broadcast PLMN when the UE camps on cells of other PLMNs? + +NOTE 1: The feasibility of radio resource utilization optimization will be determined by RAN WGs. + +NOTE 2: Collaboration with SA3 is required regarding the security issue. + +## 5.3 Key Issue #3: On demand multicast MBS session + +### 5.3.1 Description + +For services shared by a group of users, e.g. background audio/video streams, status/warning update during the game, shared streaming of collaborative interactive application, enabling temporary multicast group for the service would be beneficial for operators to be more flexible to provide services with resource efficiency, i.e. dynamically creating multicast session when required by the service, and releasing them when not required. + +Based on the triggers provided by the AF, e.g. information or request provided by the AF which allows multicast transport for a specific service, and other factors, on demand multicast MBS session may be created by the 5GS for the service. A similar example in eMBMS is MBMS operation on Demand (MooD) defined by SA4. + +The following aspects are to be studied: + +- Use cases for on demand MBS multicast sessions and related requirements and potential gaps in Rel-17 MBS multicast procedures. +- Whether and how to enhance the Release-17 MBS procedures to enable the on-demand multicast MBS session management. If needed, what information can be exposed by the 5GC to the AF or be provided by the AF, to enable on demand multicast MBS session management by AF. + +NOTE: Coordination with SA4 is needed for study of this KI. + +## 5.4 Key Issue #4: Group message delivery + +### 5.4.1 Description + +In previous Releases, group-based enhancements were introduced to enable an optimised handling of groups of UEs/subscriptions. In clause 5.5 of TS 23.682 [6], the group message delivery is specified via MB2 and xMB interfaces over eMBMS. This key issue will study whether and how to support Group Message Delivery over MBS for feature parity. + +For this key issue, the following aspects will be studied: + +- Whether and how to enhance the MBS functionality to provide a similar group message delivery as available in eMBMS. +- Whether group message delivery applies to MBS broadcast, MBS multicast, or both. +- Whether and how to provide a unified group message delivery applicable to both 5GS using MBS and EPS using eMBMS. + +NOTE 1: Collaboration with SA4 is needed. + +NOTE 2: Control plane cell broadcast is not included. + +## 5.5 Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices + +### 5.5.1 Description + +Capability-limited devices may use power-saving mechanisms to extend their battery live. Existing power saving mechanisms include MICO (Mobile Initiated Connection Only) mode, DRX (Discontinuous Reception), eDRX (Extended Discontinuous Reception). + +MBS content should be transmitted to all devices at the same time to save transmission resources. However, the existing power saving mechanisms may prevent devices from receiving MBS content (for instance group messages). + +This KI will study the following issue: + +- Whether and how to support MBS content (for instance group message) delivery for capability-limited devices by considering coexistence of existing power saving mechanisms and MBS. + +NOTE: In SA WG4, co-existence between power saving mechanism and eMBMS has been studied in TR 26.850 [5]. The study result in TR 26.850 [5] could be taken into consideration during the solution study of this KI. + +## 5.6 Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs + +### 5.6.1 Description + +Public safety requirements are documented in TS 22.179 [9] and related procedures are documented in TS 23.280 [7] and TS 24.379 [8]. + +Specific 5MBS requirements for public safety are documented in clause 4.2. + +Based on the 5MBS requirements for public safety documented in clause 4.2, this Key issue will study whether there are any performance issues for high number of public safety UEs, and for identified performance issues related enhancements to 5MBS. + +NOTE: Coordination with RAN WGs and SA6 WG will be required. + +# --- 6 Solutions + +## 6.0 Mapping of Solutions to Key Issues + +*Editor's note: This clause describes the mapping between solutions and key issues.* + +Table 6.0-1: Mapping of Solutions to Key Issues + +| Solutions | Key Issues | | | | | | +|-----------|--------------------------------------------|---------------------------|--------------------------------------|-----------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------| +| | 1
MBS session reception in RRC Inactive | 2
MOCN network sharing | 3
On demand multicast MBS session | 4
Group Message Delivery | 5
Coexistence with existing power saving mechanisms for capability-limited devices | 6
Improvement on performance issues for public safety UEs | +| 1 | X | | | | | | +| 2 | | X | | | | | +| 3 | X | | | | | X | +| 4 | X | | | | | | +| 5 | X | | | | | | +| 6 | X | | | | | | +| 7 | | X | | | | | +| 8 | | X | | | | | +| 9 | | X | | | | | +| 10 | | | X | | | | +| 11 | | | X | | | | +| 12 | | | | X | | | +| 13 | | | | X | | | +| 14 | | | | | X | | +| 15 | | | | | X | | +| 16 | | | | | | X | +| 17 | | | | | | X | +| 18 | X | | | | | | +| 19 | X | | | | | | +| 20 | X | | | | | X | +| 21 | X | | | | | | +| 22 | X | | | | | | +| 23 | X | | | | | | +| 24 | | X | | | | | +| 25 | | | | | X | | +| 26 | X | | | | | X | +| 27 | X | | | | | | +| 28 | X | | | | | | +| 29 | | X | | | | | +| 30 | | | X | | | | +| 31 | | | | | | X | + +## 6.1 Solution #1: Procedures for RRC Inactive MBS data reception + +### 6.1.1 Introduction + +This solution addresses Key Issue #1. + +### 6.1.2 Functional description + +It is assumed to reuse the current architecture defined in Rel-17 MBS work (see TS 23.247 [4]). In other words, MB-SMF is used to handle MBS session-level management while SMF performs per-UE MBS session management, e.g. authorization, multicast session information provisioning, managing 5GC Individual MBS traffic delivery. + +An AF creating a multicast session should be able to influence the service quality (more UEs vs. higher reliability) taking into consideration the specific needs of the service it offers. Thus the AF can provide assistance information to help the PLMN to enable or disable the transmission to UEs in RRC-INACTIVE state. The AF may also, based on local configuration or triggered by e.g. event report from the NEF (e.g. "Number of UEs present in a geographical area" as specified in clause 4.15.3.1 of TS 23.502 [3]), subscribe to or requests network analytics information (e.g. Observed Service Experience analytics, NF load analytics, Network Performance analytics, User Data Congestion analytics) from + +the NWDAF as specified in TS 23.288 [10], and decide to enable or disable the transmission to UEs in RRC-INACTIVE state based on the analytics information. For example, if the User Data Congestion analytics information indicates that the congestion level of the network is (predicted to be) high, then the AF can enable the transmission to UEs in RRC-INACTIVE state (i.e. instructing the NG-RAN to switch the UE in RRC-CONNECTED state to RRC-INACTIVE state); and later on when the analytics information indicates that the congestion is relieved, the AF can disable the transmission to UEs in RRC-INACTIVE state (i.e. instructing the NG-RAN to switch the UE in RRC-INACTIVE state back to RRC-CONNECTED state). The AF provides the indication of enabling or disabling the transmission to UEs in RRC-INACTIVE state (i.e. an indication whether NG-RAN nodes may deliver the MBS session to UEs in the inactive state) as part of the assistance information to the NG-RAN. However, the decision whether to apply transmission to UEs in RRC-INACTIVE state remains in the RAN nodes if transmission to UE in RRC-INACTIVE state is enabled. + +NOTE: If the AF provides assistance information to disable reception in RRC-INACTIVE state, the number UEs in a cell that can receive the MBS session will be more limited but the transmission will be more reliable. + +**Editor's note:** Whether such behaviour is intended is FFS. + +Procedures in the following clauses focus on the following functionalities: + +- 5GC provisioning necessary parameters to NG-RAN node(s). +- Switching between RRC Connected and RRC Inactive modes. + +There are two levels of priority as a part of 5GC-provided parameters, namely: + +- MBS session priority: the MBS session priority denotes the priority level of an MBS session, and the priority level defines the relative importance of an MBS session. This allows the NG-RAN nodes deciding (the members of) which MBS session can be switched to RRC Inactive state, to free up resources of NG-RAN node upon e.g. congestion. NG-RAN node may also use it to decide (the members of) which MBS session can be switched to RRC Connected state, once the resources are regarded as sufficient. + +The details of how the 5GC provides MBS session priority to NG-RAN node are further described in clause 6.1.3.2. + +**Editor's note:** Whether the existing QoS parameters (e.g. ARP, 5QI) of the MBS QoS Flow(s) can be used for the MBS Session priority is FFS. + +- UE session priority: the UE session priority denotes the priority level of a certain UE within a certain MBS session, and the priority level defines the relative importance of a UE for an MBS session. This allows the NG-RAN nodes deciding if the UE of an MBS session can be switched to RRC Inactive state, to free up resources of NG-RAN node upon e.g. congestion. NG-RAN node may also use it to decide if the UE of an MBS session can be switched to RRC Connected state, once the resources are regarded as sufficient. + +The details of how the 5GC provides UE session priority to NG-RAN node are further described in clause 6.1.3.2. + +**Editor's note:** Whether and how the NG-RAN use the assistant information will be determined by RAN WGs. + +Whether the transmission mode for inactive reception is applied depends on multiple factors and determined by the NG-RAN node: + +- Backward compatibility with UEs supporting Rel-17 MBS but not capable of receiving 5MBS data while in RRC-inactive state. If such UEs that joined a MBS multicast session are in a cell, MBS data need to be transmitted using the Rel-17 transmission mode for RRC-connected reception. +- UE preferences: UEs could prefer to receive MBS data in RRC inactive state to reduce their battery consumption, or in RRC connected state to increase the service quality. + +NOTE: If the UE indicates reception in RRC-INACTIVE state is not preferred and if NG-RAN follows the UE preference, the number UEs in a cell that can receive the MBS session will be more limited but the transmission will be more reliable. + +**Editor's note:** Whether such behaviour is intended is FFS. + +- MBS session priority. + +**Editor's note:** How MBS Session priority could assist the NG-RAN in determining whether to apply transmission for inactive reception is FFS. + +- UE session priority. + +**Editor's note:** Detailed usage of combining UE priority and MBS session priority requires more study. + +- Whether the transmission for inactive reception is allowed for specific multicast MBS service(s). +- Ongoing session of the UEs (e.g. UE has other PDU session activated). + +**Editor's note:** Those assumptions need to be confirmed by RAN WGs. + +AF provides the following information, and MB-SMF stores this information as a part of Multicast MBS Session context, during MBS Session Creation procedures defined in clauses 7.1.1.2 or 7.1.1.3 of TS 23.247 [4] and clause 6.1.3.2: + +- MBS session priority. +- Whether the transmission for inactive reception is allowed for specific multicast MBS service(s). + +AF provides the following information, and UDM stores this information as a part of MBS subscription data, during External Parameter Provisioning procedures as defined in clause 6.4.2 of TS 23.247 [4]: + +- UE session priority. + +### 6.1.3 Procedures + +#### 6.1.3.1 General + +**NOTE:** The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. + +#### 6.1.3.2 MBS session creation, multicast session join and session establishment procedure + +![Sequence diagram illustrating the enhancement to current MBS procedures for session creation and join. The diagram shows interactions between UE, NG-RAN, AMF, SMF, MB-SMF, NEF/MBSF, and AF. It is divided into two main parts: 0. Registration (inactive reception capability and/or preference) and 3. Service announcement (inactive reception enabled).](10781f43062bf3e9601a1e086710556c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant MB-SMF + participant NEF/MBSF + participant AF + + Note left of UE: 0. Registration (inactive reception capability and/or preference) + UE->>AMF: 0. Registration (inactive reception capability and/or preference) + AMF->>MB-SMF: 2. Nmbsmf_MBSSession_Create Request (MBS Session ID, inactive reception enabled, MBS session priority) + + Note right of AMF: 3. Service announcement (inactive reception enabled) + AF->>NEF/MBSF: 1. Nnef_MBSSession_Create Request (MBS Session ID, service type, QoS request, inactive reception enabled, MBS session priority) + NEF/MBSF->>MB-SMF: 2. Nmbsmf_MBSSession_Create Request (MBS Session ID, inactive reception enabled, MBS session priority) + + UE->>AMF: 4. UL NAS message (N1 SM container (PDU Session Modification Request: join,)) + AMF->>SMF: 5. Nsmf_PDUSession_UpdateSMContext request + SMF->>MB-SMF: 6. Nmbsmf_MBSSession_ContextStatusSubscribe request/response (inactive reception Enabled) + SMF-->>MB-SMF: + SMF->>AMF: 7. Nsmf_PDUSession_UpdateSMContext response (inactive reception enabled, UE session priority) + AMF->>NG-RAN: 8. N2 message request (inactive reception enabled, UE session priority) + NG-RAN->>UE: 9. RRC message (inactive reception enabled) + + Note left of NG-RAN: 10. Decide to establish shared delivery for a multicast MBS session + NG-RAN->>AMF: 11. N2 MBS message () + AMF->>MB-SMF: 12. Nmbsmf_MBSSession_ContextUpdate Request + MB-SMF->>AMF: 13. Nmbsmf_MBSSession_ContextUpdate Response (inactive reception enabled, MBS session priority) + AMF->>NG-RAN: 14. N2 MBS message (inactive reception enabled, MBS session priority) + + Note left of NG-RAN: 15. Select Transmission mode for MBS session in cell + +``` + +Sequence diagram illustrating the enhancement to current MBS procedures for session creation and join. The diagram shows interactions between UE, NG-RAN, AMF, SMF, MB-SMF, NEF/MBSF, and AF. It is divided into two main parts: 0. Registration (inactive reception capability and/or preference) and 3. Service announcement (inactive reception enabled). + +Figure 6.1.3.2-1: Enhancement to current MBS procedures for session creation and join + +0. When UE registers, it indicates its capability to receive MBS multicast using the transmission mode for RRC inactive. It may also indicate a preference regarding the connectivity state in which it wishes to receive MBS session(s). If UE's preference changes (e.g. due to UE state change such as power level etc.), then the UE performs registration update. This information is propagated to NG-RAN via AMF. +- 1-2. When an AF requests the creation of a multicast MBS session, it indicates whether inactive reception of multicast shall be enabled for that session. AF also provides the MBS session priority to MB-SMF, optionally via NEF or MBSF. + +Editor's note: Whether the existing QoS parameters (e.g. ARP, 5QI) of the MBS QoS Flow(s) can be used for the MBS Session priority is FFS. + +3. The AF may also indicate in the service announcement towards the UE whether inactive/idle reception of multicast is enabled. +- 4.-14 The information whether the inactive transmission mode is enabled for an MBS session is propagated from MB-SMF towards NG-RAN, via PDU session and/or via shared delivery of a multicast session. + +SMF provides the UE session priority to NG-RAN node: In step 7, SMF includes UE session priority as a part of N2 SM information in Nsmf\_PDUSession\_UpdateSMContext response to AMF. In step 8, AMF sends the N2 SM information received from SMF to NG-RAN node during the shared tunnel establishment procedure. AF provides the UE session priority, and UDM stores this information as a part of MBS subscription data, during External Parameter Provisioning procedures as defined in clause 6.4.2 of TS 23.247 [4]. During PDU session establishment procedure, SMF fetches UE session priority from UDM. + +MB-SMF provides the MBS session priority to NG-RAN node: In step 13, since MB-SMF receives the MBS session priority in step 2, MB-SMF includes MBS session priority in the N2 SM information of Nmbsmf\_MBSSession\_ContextUpdate response message. And AMF sends N2 MBS Session response message to NG-RAN node in step 14. + +15. The NG-RAN decides the transmission mode to apply for the MBS multicast session in a cell. + +#### 6.1.3.3 Moving a UE to RRC Inactive state + +![Sequence diagram showing the process of moving a UE to RRC Inactive state. The diagram involves six entities: UE, NG-RAN, AMF, SMF, UPF, and MB-SMF. The sequence starts with a dashed box labeled '0. 5GC provides Assistance information to NG-RAN node'. Below this, the UE receives multicast MBS data in RRC-CONNECTED mode. Then, the NG-RAN determines to switch UEs in multicast MBS session to RRC Inactive state. This is followed by an 'RRC Connection Release' message from NG-RAN to UE. Finally, the UE receives multicast MBS data in RRC Inactive mode.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + + Note right of NG-RAN: 0. 5GC provides Assistance information to NG-RAN node + Note left of NG-RAN: 0. UE receives multicast MBS data in RRC-CONNECTED mode + Note left of NG-RAN: 1. RAN determines to switch UEs in multicast MBS session to RRC Inactive state. + NG-RAN->>UE: 2. RRC Connection Release + Note left of NG-RAN: 3. UE receives multicast MBS data in RRC Inactive mode + +``` + +Sequence diagram showing the process of moving a UE to RRC Inactive state. The diagram involves six entities: UE, NG-RAN, AMF, SMF, UPF, and MB-SMF. The sequence starts with a dashed box labeled '0. 5GC provides Assistance information to NG-RAN node'. Below this, the UE receives multicast MBS data in RRC-CONNECTED mode. Then, the NG-RAN determines to switch UEs in multicast MBS session to RRC Inactive state. This is followed by an 'RRC Connection Release' message from NG-RAN to UE. Finally, the UE receives multicast MBS data in RRC Inactive mode. + +**Figure 6.1.3.3-1: NG-RAN node moves a UE to CM-CONNECTED with RRC Inactive state** + +0. 5GC provides assistance information of RRC Inactive multicast MBS data reception to NG-RAN node, details see clause 6.1.3.2. UE receives multicast MBS data in CM-CONNECTED mode. + +**Editor's note:** Whether/what assistance information is needed is to be coordinated with RAN WGs. It is ffs if some UEs in the same cell can receive MBS data in RRC Inactive reception mode and other UEs can receive MBS data in Rel-17 reception mode. + +1. RAN determines to move UE in multicast MBS session to RRC Inactive state and the transmission mode to apply for the MBS multicast session in a cell taking the assistance information into consideration. + +**Editor's note:** Determination of switching to RRC Inactive will be confirmed by the RAN WGs. + +2. NG-RAN node releases the RRC connection and moves the UE to CM-CONNECTED with RRC Inactive state. + +**Editor's note:** How to release the UEs belongs to multicast MBS session will be determined by RAN WGs. + +3. UE receives multicast MBS data in CM-CONNECTED with RRC Inactive mode. + +**Editor's note:** RAN WGs will determine the configuration of UE receiving multicast MBS data in RRC Inactive. + +#### 6.1.3.4 Moving a UE to RRC-CONNECTED from RRC Inactive state + +![Sequence diagram showing the process of moving a UE from RRC Inactive state to RRC-CONNECTED state. The diagram involves six entities: UE, NG-RAN, AMF, SMF, UPF, and MB-SMF. The process starts with the 5GC providing assistance information to the NG-RAN node. The UE receives multicast MBS data in RRC Inactive mode. The RAN determines to switch UEs in the multicast MBS session to RRC CONNECTED state. The RAN informs related UEs to be switched to RRC-CONNECTED state. Finally, the UE receives multicast MBS data in RRC-CONNECTED mode.](a3472689858b068ef469213682965325_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + + Note right of NG-RAN: 0. 5GC provides Assistance information to NG-RAN node + Note left of UE: 0. UE receives multicast MBS data in RRC Inactive mode + Note right of NG-RAN: 1. RAN determines to switch UEs in multicast MBS session to RRC CONNECTED state. + Note right of NG-RAN: 2. RAN informs related UEs to be switched to RRC-CONNECTED state. + Note left of UE: 3. UE receives multicast MBS data in RRC-CONNECTED mode + +``` + +Sequence diagram showing the process of moving a UE from RRC Inactive state to RRC-CONNECTED state. The diagram involves six entities: UE, NG-RAN, AMF, SMF, UPF, and MB-SMF. The process starts with the 5GC providing assistance information to the NG-RAN node. The UE receives multicast MBS data in RRC Inactive mode. The RAN determines to switch UEs in the multicast MBS session to RRC CONNECTED state. The RAN informs related UEs to be switched to RRC-CONNECTED state. Finally, the UE receives multicast MBS data in RRC-CONNECTED mode. + +**Figure 6.1.3.4-1: NG-RAN node moves a UE to RRC-CONNECTED state** + +0. 5GC provides assistance information of RRC Inactive multicast MBS data reception to NG-RAN node, details see clause 6.1.3.2. UE receives multicast MBS data in CM-CONNECTED with RRC Inactive mode. + +**Editor's note:** Whether/what assistance information is needed is to be coordinated with RAN WGs. + +1. RAN determines to move UE in multicast MBS session to RRC-CONNECTED state based on the assistance information as described in clause 6.1.2. + +**Editor's note:** Determination of switching to RRC Inactive will be confirmed by the RAN WGs. + +2. NG-RAN node informs related UEs to RRC-CONNECTED state. + +**Editor's note:** How to inform the related UEs belonging to multicast MBS session will be determined by RAN WGs. + +3. UE receives multicast MBS data in RRC-CONNECTED mode. + +**Editor's note:** RAN WGs will determine the configuration of UE receiving multicast MBS data in RRC-CONNECTED mode. + +### 6.1.4 Impacts on services, entities and interfaces. + +**Editor's note:** This clause describes impacts to existing services, entities and interfaces. + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] is reused. + +AF: + +- The AF includes the MBS session priority and information whether the transmission for inactive reception is enabled in the message sent to MB-SMF. +- The AF includes the UE session priority during External Parameter Provisioning procedure. + +MB-SMF: + +- The MB-SMF stores MBS session priority and information whether the transmission mode for inactive reception is enabled as a part of multicast context, and provides MBS session priority and information whether the transmission mode for inactive reception is enabled to the NG-RAN node. + +SMF: + +- SMF fetches the UE MBS priority and provide to the NG-RAN node during PDU Session modification/establishment procedure. + +NG-RAN: + +- Determine the transmission mode for an MBS session in a cell and which UE can be switched RRC Inactive/Connected mode based on the UE MBS priority and MBS session priority from SMF/MB-SMF, respectively. + +UDM: + +- Storing the UE session priority of a certain MBS session. + +UE: + +- Indicate capability and preference for multicast reception in RRC inactive state. + +## 6.2 Solution #2: Procedures for MOCN network sharing + +### 6.2.1 Introduction + +This solution addresses Key Issue #2. + +### 6.2.2 Functional description + +#### 6.2.2.1 General + +It is assumed to reuse the current architecture and TMGI definition in Rel-17 MBS work (see TS 23.247 [4]). In other words, MB-SMF is used to handle MBS session-level management while SMF performs per-UE MBS session management, e.g. authorization, multicast session information provisioning, managing 5GC Individual MBS traffic delivery. + +In general the proposal is based on the additional identifier (i.e. identifier of the broadcast MBS service) provided by AF during MBS session Create procedure. The identifier of the broadcast MBS service is non-PLMN specific, which would be included and the same when AF sends requests for establishing the broadcast MBS session for the same broadcast MBS service to different PLMNs. The MB-SMF includes the received identifier in the N2 MB-SM container, and provided to NG-RAN node. Figure 6.2.2.1-1 demonstrates an example of the proposal. + +![Diagram of MOCN network sharing using additional identifier. The diagram shows two PLMNs, a and b, sharing an NG-RAN node. PLMN a consists of AF, MB-SMF a, AMF a, and UE of PLMN a. PLMN b consists of AF, MB-UPF b, AMF b, and UE of PLMN b. The NG-RAN node is shared by both PLMNs. Control messages for MBS sessions x and y are sent from the AMFs to the NG-RAN. The NG-RAN broadcasts the control messages to the UEs. A note indicates that only 1 copy of the broadcast service data is sent by the resources shared by MBS sessions x and y. Another note indicates that the NG-RAN drops the incoming N3mb data of PLMN b.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +| | PLMN a | PLMN b | +|-------------------|-------------------------|-------------------------| +| Broadcast service | Additional identifier w | Additional identifier w | +| Broadcast session | TMGI x | TMGI y | + +Diagram of MOCN network sharing using additional identifier. The diagram shows two PLMNs, a and b, sharing an NG-RAN node. PLMN a consists of AF, MB-SMF a, AMF a, and UE of PLMN a. PLMN b consists of AF, MB-UPF b, AMF b, and UE of PLMN b. The NG-RAN node is shared by both PLMNs. Control messages for MBS sessions x and y are sent from the AMFs to the NG-RAN. The NG-RAN broadcasts the control messages to the UEs. A note indicates that only 1 copy of the broadcast service data is sent by the resources shared by MBS sessions x and y. Another note indicates that the NG-RAN drops the incoming N3mb data of PLMN b. + +Figure 6.2.2.1-1: MOCN network sharing using additional identifier + +It is assumed that for the MBS sessions identified by the same "identifier of the broadcast MBS service", the NG-RAN node will use the same radio resources, but still broadcast the TMGIs for different PLMNs. In other words: + +- UE: UEs of different PLMNs behave the same as Rel-17, i.e. listen to the control channel of the TMGIs broadcasted by the NG-RAN node and receive the broadcast data. +- NG-RAN node: NG-RAN node behave the same as Rel-17, i.e. broadcasts the TMGIs of different PLMNs, but the NG-RAN node also use the same radio resources for transmitting the MBS data of different TMGIs but with the same "identifier of the broadcast MBS service". + +#### 6.2.2.2 Identifier of the broadcast MBS service + +The Identifier of the broadcast MBS service is used to denote the broadcast communication service. When creating the MBS session, the AF may additionally include the Identifier in the MBS session create request message. For the same broadcast communication service but transmitted in different PLMNs, the Identifier will be the same. + +The Identifier of the broadcast MBS service is non-PLMN specific, it is used for globally identify the broadcast service data at the NG-RAN node. The Identifier is in the form of IP addresses, which is the target IP address and optionally includes the source IP address. The source IP address is the source IP address of the data provider, e.g. the address of the AS, and the target IP address can be the destination IP address of the broadcast data, which might be the IP multicast address. + +**Editor's note:** It is ffs how a unique identifier can be provided if different AFs act as data source against different core networks. + +#### 6.2.2.3 Reception of the broadcast data by the UE + +It is proposed to not change the Uu interface for the MOCN scenario, i.e. MCCH/MTCH mechanisms defined by Rel-17 are reused. The sharing NG-RAN node uses the same radio resources for the data transmission, since the data service will be the same between/among different PLMNs. + +NOTE: The above-mentioned parts needs confirmation by the RAN WGs. + +### 6.2.3 Procedures + +#### 6.2.3.1 General + +NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. + +Editor's note: It will be confirmed by the RAN WG that whether the additional identifier is needed. + +Editor's note: Support of the encrypted content reception is FFS. + +#### 6.2.3.2 Broadcast Session Establishment + +![Sequence diagram for Broadcast Session Establishment for MOCN network sharing. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with TMGI allocation and MBS Session Create from AF to MB-SMF. MB-SMF sends Namf_MBSBroadcast_ContextCreate Request to AMF. AMF sends N2 message Request to NG-RAN. NG-RAN creates MBS Session context and sends IGMP/MLD join to MB-UPF. MB-UPF sends N2 message Response to AMF. AMF sends Namf_MBSBroadcast_ContextCreate Response to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. NG-RAN advertises TMGI to UE. NG-RAN sends N2 message Response to AMF. AMF sends Namf_MBSBroadcast_ContextStatusNotify Request to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. Finally, Media streams are established from AF to MB-UPF to NG-RAN to UE via PTM transmission.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +``` + +sequenceDiagram + participant AF + participant MB-SMF + participant AMF + participant NG-RAN + participant UE + participant MB-UPF + participant PCF + participant NEF/MBSF + + Note right of AF: 1. TMGI allocation and MBS Session Create: see clause 7.1.1.2 or 7.1.1.3 + AF->>MB-SMF: 2. Namf_MBSBroadcast_ContextCreate Request (TMGI, LL SSM, 5G Authorized QoS Profile, MBS service area, identifier of broadcast MBS service) + MB-SMF->>AMF: 3. N2 message Request (TMGI, LL SSM, QoS Profile, MBS service area, identifier of broadcast MBS service) + Note left of NG-RAN: 4. MBS Session context created + NG-RAN->>MB-UPF: 5. IGMP/MLD join + MB-UPF->>AMF: 6. N2 message Response (TMGI, N3mb DL Tunnel info) + AMF->>MB-SMF: 7. Namf_MBSBroadcast_ContextCreate Response () + MB-SMF->>MB-UPF: 8. N4mb Session Update (TMGI, N3mb DL Tunnel Info) + Note left of UE: 9. NG-RAN advertises TMGI + NG-RAN->>AMF: 10. N2 message Response (TMGI, N3mb DL Tunnel) + AMF->>MB-SMF: 11. Namf_MBSBroadcast_ContextStatusNotify Request () + MB-SMF->>MB-UPF: 12. N4mb Session Update (TMGI, N3mb DL Tunnel) + AF->>MB-UPF: 13. Media stream + MB-UPF->>NG-RAN: 14. Media stream + NG-RAN->>UE: 15. PTM transmission + +``` + +Sequence diagram for Broadcast Session Establishment for MOCN network sharing. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with TMGI allocation and MBS Session Create from AF to MB-SMF. MB-SMF sends Namf\_MBSBroadcast\_ContextCreate Request to AMF. AMF sends N2 message Request to NG-RAN. NG-RAN creates MBS Session context and sends IGMP/MLD join to MB-UPF. MB-UPF sends N2 message Response to AMF. AMF sends Namf\_MBSBroadcast\_ContextCreate Response to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. NG-RAN advertises TMGI to UE. NG-RAN sends N2 message Response to AMF. AMF sends Namf\_MBSBroadcast\_ContextStatusNotify Request to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. Finally, Media streams are established from AF to MB-UPF to NG-RAN to UE via PTM transmission. + +Figure 6.2.3.2-1: Broadcast Session Establishment for MOCN network sharing + +The following additions apply compared to clause 7.3.1 of TS 23.247 [4]: + +1. AF performs TMGI allocation and MBS session creation as specified in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4]. The AF further includes the identifier of the broadcast MBS service in MBS session creation request. +2. MB-SMF invokes Namf\_MBSBroadcast\_ContextCreate Request with further including identifier of the broadcast MBS service in the N2 SM container received in step 1. +4. NG-RAN node creates a Broadcast MBS Session Context, stores the TMGI, the QoS Profile and the identifier of the broadcast MBS service in the MBS Session Context, if the Broadcast MBS Session Context does not exist (i.e. the other PLMN network sharing the NG-RAN node has not requested for the same broadcast MBS service to be established at the NG-RAN node). + +If the NG-RAN node already exists, i.e. NG-RAN nodes stores the same "identifier of the broadcast MBS service" in the MBS Session Context of other MBS session, then the NG-RAN node reuses the previously allocated radio resources of the MBS session identified by the same "identifier of the broadcast MBS service", as the one for the newly requested MBS session. In other words, all MBS sessions having the same "identifier of the broadcast MBS service" shares the radio resources. When the NG-RAN node receives the DL MBS data of the requested MBS session afterwards, it will not send the received data in the air interface. + +9. NG-RAN broadcasts the TMGI representing the MBS service over radio interface. + +NOTE: This step is same as the session start procedure in TS 23.247 [4]; it is included here for the sake of clarity. + +Editor's note: Details will be confirmed by the RAN WGs. + +#### 6.2.3.3 Broadcast Session Release + +![Sequence diagram for Broadcast Session Release for MOCN network sharing. The diagram shows the interaction between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with a media stream from AF to UE via NEF/MBSF, PCF, MB-UPF, MB-SMF, and AMF. The AF then initiates an MBS Session Deletion. The MB-SMF sends a Namf_MBSSroadcast_ContextRelease Request (TMGI) to the AMF. The AMF sends an MB Session Resource Release Req (TMGI) to the NG-RAN. The NG-RAN then stops PTM delivery to the UE and sends an MLD/IGMP Leave (LL MC addr) to the PCF. The AMF sends an MB Session Resource Release Resp to the MB-SMF, which in turn sends a Namf_MBSSroadcast_ContextRelease Response to the AMF. Finally, a TMGI De-allocation procedure is initiated between the MB-SMF and the MB-UPF.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant PCF + participant NEF/MBSF + participant AF + + Note over AF, UE: 1. Media stream + AF->>NEF/MBSF: + NEF/MBSF->>PCF: + PCF->>MB-UPF: + MB-UPF->>MB-SMF: + MB-SMF->>AMF: + AMF->>NG-RAN: + NG-RAN->>UE: 1. PTM + Note over AF, MB-SMF: 2. MBS Session Deletion in Figure 7.1.1.3-1 + MB-SMF->>AMF: 3. Namf_MBSSroadcast_ContextRelease Request (TMGI) + AMF->>NG-RAN: 4. MB Session Resource Release Req (TMGI) + NG-RAN->>UE: 5. Stop PTM delivery + NG-RAN->>PCF: 6. MLD/IGMP Leave (LL MC addr) + AMF->>MB-SMF: 7. MB Session Resource Release Resp + MB-SMF->>AMF: 8. Namf_MBSSroadcast_ContextRelease Response + Note over MB-SMF, MB-UPF: 9. TMGI De-allocation in Figure 7.1.1.3-1 + +``` + +Sequence diagram for Broadcast Session Release for MOCN network sharing. The diagram shows the interaction between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with a media stream from AF to UE via NEF/MBSF, PCF, MB-UPF, MB-SMF, and AMF. The AF then initiates an MBS Session Deletion. The MB-SMF sends a Namf\_MBSSroadcast\_ContextRelease Request (TMGI) to the AMF. The AMF sends an MB Session Resource Release Req (TMGI) to the NG-RAN. The NG-RAN then stops PTM delivery to the UE and sends an MLD/IGMP Leave (LL MC addr) to the PCF. The AMF sends an MB Session Resource Release Resp to the MB-SMF, which in turn sends a Namf\_MBSSroadcast\_ContextRelease Response to the AMF. Finally, a TMGI De-allocation procedure is initiated between the MB-SMF and the MB-UPF. + +Figure 6.2.3.3-1: Broadcast Session Release for MOCN network sharing + +The following additions apply compared to clause 7.3.2 of TS 23.247 [4]: + +4. After NG-RAN node receives multiple N2 message to release the MBS Session for the TMGI (e.g. from several AMFs the NG-RAN is connected to), if there is no other PLMN requesting to the broadcast MBS service, the NG-RAN node performs step 5 and step 6. + +If the MBS session is about to be released, and 1) the NG-RAN nodes uses its MBS data as the one sending in the air interface, and 2) there are other MBS sessions identified by the same "identifier of the broadcast MBS service", then the NG-RAN node will select DL data of one other MBS session of the same "identifier of the broadcast MBS service" and send its data using the previous allocated radio resources. + +Editor's note: Details will be confirmed by the RAN WGs. + +### 6.2.4 Impacts on services, entities and interfaces + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] is reused exception for the following additions: + +AF, NEF: + +- Support to provide/process the identifier of the broadcast MBS service during broadcast session establishment procedure. + +MB-SMF: + +- Include the identifier of the broadcast MBS service to the N2 SM container sent to NG-RAN node. + +NG-RAN: + +- Support to identify the broadcast MBS service from 5GC and use the same resources for the same broadcast MBS service. +- Support to configure radio bearer of the MBS sessions with the same "identifier of the broadcast MBS service" with the same radio resources. +- Refrain from sending the data of the subsequently established MBS session with the same "identifier of the broadcast MBS service" to the UEs. + +## 6.3 Solution #3: AF providing assistance information + +### 6.3.1 Introduction + +This solution addresses the following bullet in Key Issue #1. + +- Whether, how and what MBS assistance information to provide from 5GC to RAN for an MBS session allowing UEs in CM-CONNECTED with RRC Inactive state to receive MBS content, including the aspect which 5GC NF(s) determine the MBS assistance information and how they do so. + +### 6.3.2 Functional description + +After the multicast MBS session is created, the AF may provide to the 5GC the group member information (e.g. whether a member belongs to a "privileged" category in a multicast group) so that the group members' UEs are not sent to RRC\_INACTIVE state and those members get the best possible service (e.g. voice quality, response time, assurance of not getting pre-empted, etc.). + +The 5GC then forward this information to NG-RAN to assist the RAN in the decision which UEs can be sent to RRC\_INACTIVE when needed. + +The group member information consists of the following: + +- MBS Session ID; +- group member category (e.g. privileged, non-privileged). + +### 6.3.3 Procedures + +The following existing procedures specified in TS 23.502 [3] are reused for the AF to provide assistant information, i.e. group member information (e.g. whether a member belongs to a "privileged" category in a multicast group): + +- 4.15.6.6 AF session with required QoS Create procedure. +- 4.15.6.6a AF session with required QoS update procedure. +- 4.16.5.2 PCF initiated SM Policy Association Modification. +- 4.3.3.2 UE or network requested PDU Session Modification (non-roaming and roaming with local breakout). + +Compared to clause 4.15.6.6 AF session with required QoS Create procedure of TS 23.502 [3], the additional group member information may be included in the following service operations: + +- Step 1: Nnef\_AFsessionWithQoS\_Create request. +- Step 3: Npcf\_PolicyAuthorization\_Create request. + +Compared to clause 4.15.6.6a AF session with required QoS Update procedure of TS 23.502 [3], the additional group member information may be included in the following service operations: + +- Step 1: Nnef\_AFsessionWithQoS\_Update request. +- Step 3: Npcf\_PolicyAuthorization\_Update request. + +Compared to clause 4.16.5.2 PCF initiated SM Policy Association Modification, there is following addition: + +- Step 4: In Npcf\_SMPolicyControl\_UpdateNotify service operation may include group member information. + +Compared to clause 4.3.3.2 UE or network requested PDU Session Modification (non-roaming and roaming with local breakout), there are following additions: + +- Step 3b: PCF initiated SM Policy Association Modification, same as step 4 of clause 4.16.5.2. +- If the UE has joined the MBS Session and the PDU Session UP activated, the SMF provides the group member information via PDU Session Modification towards the NG-RAN. + +If the UE has not joined the MBS Session or the UE has joined the MBS Session but does not have PDU Session UP activated, the SMF stores the group member information. The SMF sends the information to NG-RAN next time when PDU Session UP is activated for UE that has joined the MBS Session. + +### 6.3.4 Impacts on services, entities and interfaces. + +AF: + +- See clause 6.3.3. + +NEF + +- See clause 6.3.3. + +PCF: + +- See clause 6.3.3. + +SMF: + +- See clause 6.3.3. + +UPF: + +- No impact. The new parameter of MBS member priority is only used in NG-RAN. + +NG-RAN: + +- The NG-RAN receives the group member information in PDU Session setup or modification. + +**Editor's note:** How the group member information is used by NG-RAN requires collaboration with RAN WGs. + +## 6.4 Solution #4: MBS session management for RRC Inactive MBS data receiving UE + +### 6.4.1 Introduction + +This solution addresses Key Issue #1, especially on the enhancement of MBS session management for RRC Inactive MBS data receiving UE. + +### 6.4.2 Functional description + +This solution builds on top of solution 1. The multicast session management include following procedures: + +- MBS session activation, the group-based CN paging may be executed. If a UE in RRC-INACTIVE state is allowed to receive multicast data in that state, a paging reaction is not always needed due to it may not need to resume the RRC connection for receiving the MBS data. But paging reaction for other group member UE, which are in RRC-IDLE state or which need to receive the MBS data in the RRC connected state, is still needed. +- Multicast session deactivation/multicast session update, no impact to the existing procedure as defined in TS 23.247 [4]. If the UE is in the CM-IDLE state and need be notified, the paging is per UE paging. +- Multicast session release, the group-based paging may be executed. As defined in TS 23.247 [4] Paging reaction is needed for all UE as they all need go back to CM-CONNECTED with RRC-CONNECTED state. + +Per above consideration, it is suggested to focus on how to page UE due to the MBS session activation and MBS session release. The intention is to avoid RRC-INACTIVE group member UE, which supports receiving multicast service in RRC-inactive state, always resume the RRC connection blindly if the paging event is for activation and MBS session data can be received in RRC-INACTIVE state. + +**Editor's note:** Paging procedures are under remit of the RAN groups and any related enhancements need to be confirmed by RAN groups. + +### 6.4.3 Procedures + +![Sequence diagram illustrating the Multicast Session Activation/Release Procedure. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. The steps are: 1. UE join the multicast MBS session; 2. NG-RAN enable multicast group member receive multicast data in RRC-inactive state; 3. Multicast MBS session become deactivation; 4. MBS session activation or MBS session release; 5. Nmbsmf_MBSSession_ContextStatusNotify; 6. Namf_MT_EnableGroupReachability request; 7. Paging message; 8. Page UEs; 9. Step 6-15 of clause 7.2.5.2 of TS 23.247 Or Step 3-9 of clause 7.2.2.3 of TS 23.247.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-UPF + participant MB-SMF + + Note over UE, MB-SMF: 1. UE join the multicast MBS session, see clause 7.2.1.3 of TS 23.247 + Note over NG-RAN: 2. NG-RAN enable multicast group member receive multicast data in RRC-inactive state. + Note over UE, MB-SMF: 3. Multicast MBS session become deactivation, see clause 7.2.5.3 of TS 23.247 + Note over MB-SMF: 4. MBS session activation or MBS session release + Note over SMF: 5. Nmbsmf_MBSSession_ContextStatusNotify (TMGI, multicast session activated/multicast session release) + Note over SMF: 6. Namf_MT_EnableGroupReachability request([event information]) + Note over AMF: 7. Paging message([TMGI], [Paging Cause]) + Note over NG-RAN: 8. Page UEs + Note over UE, MB-SMF: 9. Step 6-15 of clause 7.2.5.2 of TS 23.247 +Or +Step 3-9 of clause 7.2.2.3 of TS 23.247 + +``` + +Sequence diagram illustrating the Multicast Session Activation/Release Procedure. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. The steps are: 1. UE join the multicast MBS session; 2. NG-RAN enable multicast group member receive multicast data in RRC-inactive state; 3. Multicast MBS session become deactivation; 4. MBS session activation or MBS session release; 5. Nmbsmf\_MBSSession\_ContextStatusNotify; 6. Namf\_MT\_EnableGroupReachability request; 7. Paging message; 8. Page UEs; 9. Step 6-15 of clause 7.2.5.2 of TS 23.247 Or Step 3-9 of clause 7.2.2.3 of TS 23.247. + +**Figure 6.4.3.1-1: Multicast Session Activation/Release Procedure.** + +1. UE joins the multicast MBS session via the procedure as defined in clause 7.2.1.3 of TS 23.247 [4]. +2. In some cases, e.g. due to radio resource congestion, NG-RAN could move one or multiple multicast group member UEs to RRC-INACTIVE state and those UEs are still able to received multicast MBS data. +3. The multicast MBS session becomes inactive via the procedure as defined in clause 7.2.5.3 of TS 23.247 [4]. The group member UE can be moved to CM-IDLE or CM-Connected with RRC Connected/Inactive state. +4. After some time, MB-SMF triggers the multicast session activation or multicast session release. +5. MB-SMF sends Nmbsmf\_MBSSession\_ContextStatusNotify to SMF(s), same as step 2 of clause 7.2.5.2 or step 1a of clause 7.2.2.3 of TS 23.247 [4], which also includes the MBS session status, i.e. activation or release, as event information. In addition the RRC-inactive reception assistance information, which assist NG-RAN to determine whether the MBS session is allowed to be received in RRC-inactive state, is also included. + +NOTE 1: Steps 1, 3-5 are same as the one defined in TS 23.247 [4]. + +6. The SMF includes the event information and RRC-inactive reception assistance information (if it is received) in Namf\_MT\_EnableGroupReachability Request to AMF. Other parameters in the Namf\_MT\_EnableGroupReachability Request to AMF are same as specified in TS 23.247 [4]. +7. If AMF determines that there are UEs in CM-IDLE state among the UEs provided by the SMF in step 6, based on the event information received from SMF, the AMF includes the MBS session ID and a paging cause in the paging message sent to NG-RAN, the paging case is used to indicate the paging is for the received MBS event, e.g. MBS session activation and RRC-inactive state reception assistance information. +8. The NG-RAN performs the group paging by sending the MBS session ID and paging cause. If paging is for MBS session activation and allowed to be received in RRC-inactive state, the NG-RAN node determines for each cell whether transmission for RRC INACTIVE UE is enabled and includes a paging cause if RRC INACTIVE UE do not need go back to the RRC-CONNECTED state. + +For RRC-inactive UE(s) that joined the MBS session and receive multicast service in RRC-INACTIVE state, if the UE(s) receives the group paging with the paging cause indicating that the paging is for MBS session activation for MBS session they are receiving and allowed to be received in RRC-inactive state, those UE(s) may remain in RRC-INACTIVE state and do not perform RRC connection resumption. Otherwise, e.g. group paging does not contain a paging cause, this UE sends RRC connection resumption message to NG-RAN. + +For the UE(s) joined the MBS session and need receive multicast service in RRC-Connected state, the UE initiates the Service Request as usual. + +9. For MBS session activation, steps 6-15 of clause 7.2.5.2 of TS 23.247 [4] is executed with the following difference: + +- For the UE(s) joined the MBS session and allowed to receive multicast service in RRC-INACTIVE state, step 6-10 are skipped. + +NOTE 2: It is to be decided by RAN WG on whether RAN initiated paging is needed or not. If the RAN initiated paging is needed, different paging cause can be included in the paging message for MBS session activation. + +For MBS session release, steps 3-9 of clause 7.2.2.3 of TS 23.247 [4] is executed. + +### 6.4.4 Impacts on services, entities, and interfaces + +UE: + +- Aware whether the group paging is for multicast session activation and allowed to be received in RRC-inactive state. + +AMF: + +- Support receive the event information from SMF and generate the corresponding paging cause. + +SMF: + +- Includes the event information and RRC-inactive reception assistance information parameter sent to AMF. + +MB-SMF + +- Notify the RRC-inactive reception assistance information to SMF. + +NG-RAN: + +- Support adding paging cause for group paging per receiving paging cause and whether the UE need go back to the RRC CONNECTED state. + +## 6.5 Solution #5: Mobility Procedures for UE supporting RRC Inactive MBS data reception + +### 6.5.1 Introduction + +This solution addresses Key Issue #1, especially on the mobility handling for UE supporting RRC Inactive state MBS data receiving. + +### 6.5.2 Functional description + +The procedures in clause 6.5.3.1 and 6.5.3.2 are used for the UE receiving the MBS data in RRC-inactive state, under the following mobility cases: + +- Moving within the RA. + +NOTE 1: It is assumed that the NG-RAN node(s) within the same RNA have the same MBS capability, i.e. all the NG-RAN nodes within the RNA are RRC-inactive MBS data reception supporting. + +- Moving out of RNA and within the RA. + +NOTE 2: The procedure includes a UE initiated service request handling, which can also be used for the case without mobility. + +- Moving out of the RA. + +NOTE 3: The target NG-RAN node could be either RRC-inactive MBS data reception supporting NG-RAN or non RRC-inactive MBS data reception supporting Node. + +The procedures in clause 6.5.3.3 is used for RRC-connected multicast group member UE moves to RRC-inactive MBS reception supporting NG-RAN. + +### 6.5.3 Procedures + +#### 6.5.3.1 RRC-inactive multicast group member moves within RNA + +Editor's note: The procedure of the mobility within RNA is under the responsibility of RAN WG. It need be confirmed and defined by RAN WGs. + +This clause describes the mobility procedure for the UE, which joined the MBS session and is allowed to receive the multicast service in RRC-inactive state, moves within RNA. + +NOTE 1: It is assumed all the NG-RAN nodes within the same RNA have same RRC-inactive MBS data reception supporting capability. + +Editor's note: If this assumption is realistic needs to be confirmed by RAN WGs + +Editor's note: It is ffs how to deal with situations where the transmission for inactive reception is nor applied everywhere, e.g. to support Rel-17 UEs in some cells + +![Sequence diagram illustrating the mobility procedure for multicast service received in RRC-inactive state. The diagram shows five entities: UE, source NG-RAN, target NG-RAN, MB-SMF, and MB-UPF. The procedure consists of three steps: 1. Interaction between UE and target NG-RAN; 2. Interaction between Source NG-RAN and Target NG-RAN; 3. Shared delivery establishment, see clause 7.2.1.4 of TS 23.247.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) + +``` + +sequenceDiagram + participant UE + participant source NG-RAN + participant target NG-RAN + participant MB-SMF + participant MB-UPF + Note right of UE: 1. Interaction between UE and target NG-RAN + Note right of source NG-RAN: 2. Interaction between Source NG-RAN and Target NG-RAN + Note right of target NG-RAN: 3. Shared delivery establishment, see clause 7.2.1.4 of TS 23.247 + +``` + +Sequence diagram illustrating the mobility procedure for multicast service received in RRC-inactive state. The diagram shows five entities: UE, source NG-RAN, target NG-RAN, MB-SMF, and MB-UPF. The procedure consists of three steps: 1. Interaction between UE and target NG-RAN; 2. Interaction between Source NG-RAN and Target NG-RAN; 3. Shared delivery establishment, see clause 7.2.1.4 of TS 23.247. + +Figure 6.5.3.1-1: Mobility procedure for multicast service received in RRC-inactive + +The UE(s) joined the multicast MBS session and is allowed to receive the multicast service in RRC-inactive state. + +1. If due to mobility the UE finds NG-RAN is changed and no multicast data received at the camping cell, the UE sends RRC message to target NG-RAN node. + +NOTE 2: The details of what is contained in the RRC message will be decided by RAN WG2. + +Editor's note: How the UE determines no multicast data at the camping cell is to be determined by RAN WGs. + +Editor's note: Whether the target RAN node needs to obtain any information about the MBS session and needs to broadcast any information about the multicast session to aid the UE with the determination is ffs. How to deal with transmission pauses is FFS. + +2. The target NG-RAN send Xn message to the source NG-RAN to get the related multicast MBS session information. The source NG-RAN provides the related MBS session information to target NG-RAN node. +3. Based on the message in step 2, if the target NG-RAN has not established the shared delivery for the indicated MBS session, the target NG-RAN trigger to establish the shared delivery to MB-UPF as defined in clause 7.2.1.4 of TS 23.247 [4]. + +Editor's note: How to stop the MBS data transmission at the cell if there are no RRC connected state UE and RRC inactive UE camp at that cell. + +#### 6.5.3.2 RRC-inactive multicast group member UE move out of RNA and within RA + +RNA update procedures for UE in RRC\_INACTIVE state are specified in TS 38.300 [13]. + +**Editor's note:** In this clause, the NG-RAN behaviour (e.g. interaction with UE) is to be determined by RAN WGs, e.g. for the UE joined the multicast MBS session and allowed receiving MBS data in RRC-inactive state, if the UE moves out its RNA and within RA, whether the RNA update procedure is performed in the same way as in Rel-17 is FFS. + +For the UE joined the multicast MBS session and allowed receiving MBS data in RRC-inactive state, if the UE moves out its RNA and within RA, it triggers the RNA update procedure as specified in TS 38.300 [13]. Based on that procedure, the UE may still in RRC Inactive state or enter RRC IDLE state per whether the UE context can be retrieved successfully or not. + +- If the UE is in the RRC Inactive state and the network indicate support RRC Inactive MBS data reception, the UE is aware that the multicast service can be received in RRC Inactive state and not need perform Service Request. + +**Editor's note:** How the RRC Inactive UE determines that network support RRC Inactive reception is to be determined by RAN WGs. + +- If the UE is in the RRC Inactive state and the network does not support RRC Inactive state MBS data reception, or in RRC Idle state, the UE invokes the Service Request to activate the user plane of the associated PDU session ID. During the user plane activation procedure, the SMF notifies the MBS session ID UE joined and the RRC inactive assistance information for MBS data receiving parameter in the N2SM Info to the NG-RAN. Per the received information, the individual or shared delivery path between the NG-RAN node and MB-UPF is established if needed. Later per NG-RAN configuration, the UE may be changed to RRC Inactive state to receive the MBS data. + +**Editor's note:** How the RRC Inactive UE determines that network does not support RRC Inactive reception is to be determined by RAN WGs. + +#### 6.5.3.3 RRC-connected multicast group member UE move to RRC-inactive MBS reception supporting NG-RAN + +For the UE joined the multicast MBS session and in RRC-connected state to receive the MBS data, if the UE moves to a RRC inactive MBS reception supporting NG-RAN, the following additions applies compared to clause 7.2.3 of TS 23.247 [4]: + +- For Xn handover, after the SMF receives the path switch request transfer information from target NG-RAN via AMF, the SMF includes the RRC inactive assistance information for MBS data receiving parameter in path switch request ACK (i.e. the N2SM Info) and sent to target NG-RAN. +- For N2 handover, after the SMF receives the Handover Required information from the source NG-RAN via the AMF, the SMF includes the RRC inactive assistance information for MBS data receiving parameter in the N2SM Info and sent to target NG-RAN within the Handover Request message via the AMF. +- After the handover procedure, based on the received RRC inactive assistance information for MBS data receiving parameter, the UE may be configured to RRC inactive state to receive the multicast MBS data same as defined in solution 1. + +### 6.5.4 Impacts on services, entities, and interfaces + +UE: + +- When the UE receives the MBS data in RRC Inactive state and move to a new cell but not receive the MBS data, the UE need activate the associated PDU session via the service request or registration procedure. + +SMF: + +- Include the RRC inactive assistance parameter in N2 SM Info and sent to target NG-RAN during handover procedure. + +**Editor's note:** Other impact will be determined by (and/or by collaboration with) RAN WGs. + +NG-RAN: + +**Editor's note:** The impact of NG-RAN is to support the mobility within RNA. It need be confirmed by RAN WGs. + +- Support trigger to establish the 5GC Shared MBS traffic delivery per the received MBS session information. + +Support provide the MBS session related information from source NG-RAN to target NG-RAN. + +## 6.6 Solution #6: Reusing the existing assistance info and Qos for RRC Inactive MBS data reception decision + +### 6.6.1 Introduction + +This solution is to address the Key Issue #1: Multicast MBS data reception in RRC Inactive state. + +### 6.6.2 Functional description + +Clause 5.3.3.2.5 of TS 23.501 [2] defines "RRC Inactive Assistance Information" sent by AMF to NG-RAN. It includes DRX, eDRX, RA, Periodic Registration Update timer, MICO mode, Information from the UE identifier, Paging Cause Indication for Voice, PEIPS Assistance Information. + +From the above Assistance information, there is no service related parameters except voice. In this solution, it keeps the same principle, i.e. there is no service related parameters added to the exist "RRC Inactive Assistance Information". + +NOTE 1: The transfer of a UE capability to receive the multicast MBS data in RRC\_INACTIVE state from UE to NG RAN is are assumed to be defined by RAN WGs. When the UE receives the multicast data in the RRC inactive, the major impact is the NG-RAN cannot receive the feedback, i.e. HARQ. It may cause the higher PER. And ARP of MBS QoS flow also be used by NG-RAN to determine whether or which MBS session can be put into RRC inactive, i.e. the member of multicast MBS session can be moved to RRC inactive state to receive the MBS data. + +**Editor's note:** Whether/how ARP of MBS Session QoS Flow can be used by NG-RAN in determining what UEs can be moved to RRC\_INACTIVE is to be determined by NG-RAN. + +So in addition to "RRC Inactive Assistance Information", the QoS parameters, e.g. PER and ARP in the 5QI of MBS QoS flow can be used by NG-RAN to determine whether the MBS session can be sent to RRC Inactive state to receives the multicast MBS session data. + +NOTE 2: The QoS parameters of MBS QoS flow is received by NG-RAN from MB-SMF during establishment of shared delivery. + +To support differentiate the UEs involving in one multicast MBS sessions, the same mechanism can be used. During or after the UE join the multicast MBS session, the AF may provide the PER to SMF which can be used for the associated Qos flow. After the SMF receives the PER for the associated Qos flow, it replaces the PER in the mapped Qos parameters of the associated Qos flow. The PER in the 5QI and ARP of associated QoS flow can be used by NG-RAN to determine whether the UE can be sent to RRC Inactive state to receives the multicast MBS session data. There are two possible method to provide the PER/ARP of associated QoS flow to SMF: + +- via PCF, in the R17, the associated QoS flow is not visible in PCF. But for this feature, the AF need to provides the flow description (e. g, SSM), PER to PCF, and PCF provides the rule to SMF. According to flow information (e.g. SSM), the SMF know this is related to the associated Qos flow. +- similar with UDM/UDR based solution, the AF provides the (PER/ARP and related UE list) for the MBS session to UDM/UDM. The SMF obtain these information. + +NOTE 3: In the R18 SID FS\_TRS\_URLLC, the KI#4 "How to enable an AF to explicitly provide PER to NEF/PCF" enable the AF provides the PER to PCF. + +NOTE 4: The UDM/UDR based solution can refer to solution 1. AF provides the PER, MBS session id, UE list, and UDM stores this information as a part of MBS subscription data, during External Parameter Provisioning procedures as defined in clause 6.4.2 of TS 23.247 [4]. + +NOTE 5: The NG-RAN can use the physical channel status load of the cell, or any other logic to determine whether the UE can be sent to RRC Inactive state meanwhile meeting the QoS requirement of the multicast service. Decision based on the channel status is out of SA WG2 scope. + +**Editor's note:** RAN WGs need to confirm the proposed NG RAN node behaviour. + +### 6.6.3 Procedures + +None. + +### 6.6.4 Impacts on services, entities and interfaces. + +AF: + +- Request PER for QoS. + +PCF: + +- Map Requested PER to PCC Rule with a 5QI that reflects the Requested PER. + +## 6.7 Solution #7: MOCN RAN Sharing + +### 6.7.1 Introduction + +This solution addresses Key Issue #2. + +### 6.7.2 Functional description + +This solution utilizes the associated session identifier (e.g. SSM used by AF) to be the identifier to associate broadcast MBS sessions from different CNs which transmitting the same content. + +The AF provides the associated session ID when creating broadcast MBS sessions with the same broadcast content. In all CNs, MB-SMF provides the associated session ID to the NG-RAN via the AMF. And then, the NG-RAN can utilize the associated session ID to associate those broadcast MBS sessions. + +NG-RAN establishes the user planes for the first broadcast MBS session it receives. The NG-RAN delivers the packets received from the established user plane over the air. For the other broadcast MBS sessions which are associated with the broadcast MBS session, the NG-RAN creates the broadcast MBS session contexts, advertises the TMGIs, but does not establish the user planes. + +In case there is a failure in the established user plane, the NG-RAN selects another associated broadcast MBS session to establish the user plane and continue to deliver the packets received from the newly established user plane over the air. + +Another option is to let AF select one allocated TMGI as the associated session identifier when creating MBS sessions towards all CNs. In this case, the NG-RAN includes only this selected TMGI in radio interface which points to the configuration, regardless of whether the NG-RAN is dedicated or MOCN shared. AF also includes only this selected TMGI in the service announcement, so that UE use it to receive the broadcast MBS session data. + +NOTE: The security mechanism for MBS traffic transmission specified in clause W.4 of TS 33.501 [14] is not applicable, while the content protection in AF can be applied for the content encryption and decryption. + +### 6.7.3 Procedures + +#### 6.7.3.1 General + +NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. + +#### 6.7.3.2 MBS Session Creation + +![Sequence diagram for MBS Session Creation for MOCN RAN sharing. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, MBSTF, AF. The diagram shows two main flows: TMGI allocation and MBS session creation, separated by service announcements.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` + +sequenceDiagram + participant AF + participant MBSTF + participant NEF/MBSF + participant NRF + participant MB-SMF + participant MB-UPF + + Note right of AF: 1. Nnef_TMGI_Allocate request + AF->>NEF/MBSF: 1. Nnef_TMGI_Allocate request + Note right of NEF/MBSF: 2. Authorization + NEF/MBSF->>NRF: 3. Nnrf_NFDiscovery (MB-SMF) + NRF-->>MB-SMF: 4. Nmbsmf_TMGI_Allocate Request + MB-SMF-->>NEF/MBSF: 5. Nmbsmf_TMGI_Allocate reponse(TMGI(s)) + NEF/MBSF-->>AF: 6. Nnef_TMGI_Allocate response(TMGI(s)) + + Note right of NEF/MBSF: 7. Service announcement + NEF/MBSF-->>AF: 8. Nnef_MBSSession_Create Request (MBS Session ID, service type, QoS request, associated session ID) + Note right of NEF/MBSF: 9. Authorization + NEF/MBSF->>NRF: 10. Nnrf_NFDiscovery (MB-SMF) + NRF-->>MB-SMF: 11. Nmbsmf_MBSSession_Create Request (MBS Session ID, service type, associated session ID) + MB-SMF-->>NRF: 12. Nnrf_NFManagement_NFUpdate (MBS session ID) + + Note right of MB-SMF: 13. Derive QoS parameters + MB-SMF->>MB-UPF: 14. Session Request + MB-UPF-->>MB-SMF: 15. Session Response (Ingress address) + + Note right of MB-SMF: 16. For broadcast, Procedures toward AMF and NG-RAN in clause 7.3.1 + MB-SMF-->>NEF/MBSF: 17. Nmbsmf_MBSSession_Create Response (Ingress Address) + + Note right of NEF/MBSF: 18. Session Request (Ingress address) + NEF/MBSF->>MBSTF: 18. Session Request (Ingress address) + Note right of MBSTF: 19. Session Response (Ingress address) + MBSTF-->>NEF/MBSF: 19. Session Response (Ingress address) + NEF/MBSF-->>AF: 20. Nnef_MBSSession_Create Response (Ingress Address) + + Note right of NEF/MBSF: 21. Service announcement + NEF/MBSF-->>AF: 21. Service announcement + + Note right of NEF/MBSF: 22. For multicast, UE join procedures in clause 7.2.1 + +``` + +Sequence diagram for MBS Session Creation for MOCN RAN sharing. Lifelines: MB-UPF, MB-SMF, NRF, NEF/MBSF, MBSTF, AF. The diagram shows two main flows: TMGI allocation and MBS session creation, separated by service announcements. + +Figure 6.7.3.2-1: MBS Session Creation for MOCN RAN sharing + +The following additions apply compared to clause 7.1.1.2 of TS 23.247 [4]: + +- The AF provides the associated session ID (e.g. SSM used by AF or one TMGI selected by AF) to the NEF/MBSF when invoking Nnef\_MBSSession\_Create Request. If AF determines to use TMGI as associated session ID, it needs to select one from those TMGIs which are to be used to create MBS sessions transmitting the same content. The AF also uses this TMGI in the service announcement. + +11. The NEF/MBSF provides the associated session ID to the MB-SMF when invoking Nmbsmf\_MBSsession\_Create Request. The MB-SMF stores the associated session ID as a part of the MBS session context to be further distributed to NG-RAN in clause 6.7.3.3. + +The same updates apply to clause 7.1.1.3 of TS 23.247 [4]. + +#### 6.7.3.3 MBS Session Start for Broadcast + +![Sequence diagram for MBS Session Start for Broadcast for MOCN RAN sharing. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with TMGI allocation and MBS Session Create (step 1). The AF sends a Namf_MBSSession_Create Request to the AMF (step 2). The AMF sends an N2 message Request to the NG-RAN (step 3). The NG-RAN creates an MBS Session context (step 4). The NG-RAN sends an IGMP/MLD join to the MB-UPF (step 5). The NG-RAN sends an N2 message Response to the AMF (step 6). The AMF sends a Namf_MBSSession_Create Response to the AF (step 7). The AMF sends an N4mb Session Update to the MB-UPF (step 8). The NG-RAN advertises the TMGI (step 9). The NG-RAN sends an N2 message Response to the AMF (step 10). The AMF sends a Namf_MBSSession_StatusNotify Request to the AF (step 11). The AMF sends an N4mb Session Update to the MB-UPF (step 12). The MB-UPF sends a Media stream to the NG-RAN (step 13). The NG-RAN sends a Media stream to the UE (step 14). The NG-RAN sends a PTM transmission to the UE (step 15).](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant PCF + participant NEF/MBSF + participant AF + + Note right of AF: 1. TMGI allocation and MBS Session Create: see clause 7.1.1.2 or 7.1.1.3 + AF->>AMF: 2. Namf_MBSSession_Create Request (TMGI, LL SSM, 5G Authorized QoS Profile, MBS service area, associated session ID) + AMF->>NG-RAN: 3. N2 message Request (TMGI, LL SSM, QoS Profile, MBS service area, associated session ID) + Note left of NG-RAN: 4. MBS Session context created + NG-RAN-->>MB-UPF: 5. IGMP/MLD join + NG-RAN->>AMF: 6. N2 message Response (TMGI, N3mb DL Tunnel info) + AMF->>AF: 7. Namf_MBSSession_Create Response () + AMF-->>MB-UPF: 8. N4mb Session Update (TMGI, N3mb DL Tunnel Info) + Note left of UE: 9. NG-RAN advertises TMGI + NG-RAN-->>AMF: 10. N2 message Response (TMGI, N3mb DL Tunnel) + AMF-->>AF: 11. Namf_MBSSession_StatusNotify Request () + AMF-->>MB-UPF: 12. N4mb Session Update (TMGI, N3mb DL Tunnel) + MB-UPF->>NG-RAN: 13. Media stream + NG-RAN->>UE: 14. Media stream + NG-RAN->>UE: 15. PTM transmission + +``` + +Sequence diagram for MBS Session Start for Broadcast for MOCN RAN sharing. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with TMGI allocation and MBS Session Create (step 1). The AF sends a Namf\_MBSSession\_Create Request to the AMF (step 2). The AMF sends an N2 message Request to the NG-RAN (step 3). The NG-RAN creates an MBS Session context (step 4). The NG-RAN sends an IGMP/MLD join to the MB-UPF (step 5). The NG-RAN sends an N2 message Response to the AMF (step 6). The AMF sends a Namf\_MBSSession\_Create Response to the AF (step 7). The AMF sends an N4mb Session Update to the MB-UPF (step 8). The NG-RAN advertises the TMGI (step 9). The NG-RAN sends an N2 message Response to the AMF (step 10). The AMF sends a Namf\_MBSSession\_StatusNotify Request to the AF (step 11). The AMF sends an N4mb Session Update to the MB-UPF (step 12). The MB-UPF sends a Media stream to the NG-RAN (step 13). The NG-RAN sends a Media stream to the UE (step 14). The NG-RAN sends a PTM transmission to the UE (step 15). + +Figure 6.7.3.3-1: MBS Session Start for Broadcast for MOCN RAN sharing + +The following additions apply compared to clause 7.3.1 of TS 23.247 [4]: + +- 2-3. The MB-SMF provides the associated session ID in the N2 SM container to the NG-RAN via AMF. +4. The NG-RAN creates the Broadcast MBS Session context including the associated session ID. If the NG-RAN determines there is already established user plane of another broadcast MBS session which is associated (identified by same associated session ID), the NG-RAN skips the user plane establishment of this broadcast MBS session. + +If multicast transport of N3mb applies, the NG-RAN skips step 5. + +If unicast transport of N3mb applies, the NG-RAN does not allocate N3mb DL Tunnel Info in step 6, and not include it in the N2 message towards MB-SMF in step 6-7 or step 10-11, so that step 8 or step 12 can also be skipped. + +9. If the NG-RAN determines the radio resource of another broadcast MBS Session is allocated which is associated (identified by the same associated session ID), and if the associated session ID is SSM, the NG-RAN advertises the TMGI of the broadcast MBS session and link the TMGI to the existing radio resources. + +If the associated session ID is TMGI, the NG-RAN uses the TMGI indicated in the associated session ID in radio interface, instead of the TMGI of broadcast MBS session. + +- 14-15. In case the user plane of the broadcast MBS session is not established, the NG-RAN will not receive the packets from the MB-UPF. + +**Editor's note:** Details will be confirmed by the RAN WGs. + +#### 6.7.3.4 MBS Session Release for Broadcast + +![Sequence diagram for MBS Session Release for Broadcast for MOON RAN sharing. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, AF. The diagram shows the release of an MBS session, starting with a media stream from AF to UE via NG-RAN. The AF then initiates an MBS Session Deletion. The MB-SMF sends a Namf_MBSSroadcast_ContextRelease Request to the AMF. The AMF sends an MB Session Resource Release Req to the NG-RAN. The NG-RAN sends an MLD/IGMP Leave to the PCF. The NG-RAN then sends an MB Session Resource Release Resp to the AMF. The AMF sends a Namf_MBSSroadcast_ContextRelease Response to the MB-SMF. Finally, a TMGI De-allocation is performed between the MB-SMF and the MB-UPF.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant PCF + participant NEF/MBSF + participant AF + + Note left of UE: 1. PTM + Note right of AF: 1. Media stream + Note right of MB-SMF: 2. MBS Session Deletion in Figure 7.1.1.3-1 + Note right of AMF: 3. Namf_MBSSroadcast_ContextRelease Request (TMGI) + Note right of NG-RAN: 4. MB Session Resource Release Req (TMGI) + Note left of UE: 5. Stop PTM delivery + Note right of PCF: 6. MLD/IGMP Leave (LL MC addr) + Note right of AMF: 7. MB Session Resource Release Resp + Note right of MB-SMF: 8. Namf_MBSSroadcast_ContextRelease Response + Note right of MB-UPF: 9. TMGI De-allocation in Figure 7.1.1.3-1 + +``` + +Sequence diagram for MBS Session Release for Broadcast for MOON RAN sharing. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, AF. The diagram shows the release of an MBS session, starting with a media stream from AF to UE via NG-RAN. The AF then initiates an MBS Session Deletion. The MB-SMF sends a Namf\_MBSSroadcast\_ContextRelease Request to the AMF. The AMF sends an MB Session Resource Release Req to the NG-RAN. The NG-RAN sends an MLD/IGMP Leave to the PCF. The NG-RAN then sends an MB Session Resource Release Resp to the AMF. The AMF sends a Namf\_MBSSroadcast\_ContextRelease Response to the MB-SMF. Finally, a TMGI De-allocation is performed between the MB-SMF and the MB-UPF. + +Figure 6.7.3.4-1: MBS Session Release for Broadcast for MOON RAN sharing + +The following additions apply compared to clause 7.3.2 of TS 23.247 [4]: + +- If the user plane of the broadcast MBS session has not been established, the NG-RAN simply stops the advertisement of the TMGI without releasing the user plane which hasn't been established. That is, step 6 is skipped for multicast transport of N3mb, and for unicast transport of N3mb DL Tunnel Info is not provided in steps 7-8. + +If the user plane of the broadcast MBS session has been established, the NG-RAN checks whether there are other associated broadcast MBS sessions. If there are, the NG-RAN may trigger Broadcast MBS Session Transport Request as specified in clause 6.7.3.5. + +**Editor's note:** Details will be confirmed by the RAN WGs. + +#### 6.7.3.5 Broadcast MBS Session Transport Request + +When NG-RAN detects there is a failure in the user plane which causes the NG-RAN cannot deliver the contents, the NG-RAN select another CN to trigger Broadcast MBS Session Transport Request procedure to establish the user plane. The selecting of CN can be up to NG-RAN implementation. + +It may apply to the scenario when the broadcast MBS session is released in that CN, whose user plane is used to content transmission, while there are some other broadcast MBS sessions not released. + +![Sequence diagram for Broadcast MBS Session Transport Request. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF. The diagram shows the NG-RAN selecting a CN to establish the user plane. The NG-RAN then sends an IGMP/MLD Join to the MB-UPF. The NG-RAN sends a Broadcast Session Transport Request (MBS Session ID, N3mb DL Tunnel Info) to the AMF. The AMF sends a Namf_MBSSroadcast_ContextsStatusNotify Request (MBS Session ID, N3mb DL Tunnel Info) to the MB-SMF. The MB-SMF sends an N4mb Session Update to the MB-UPF. The MB-SMF sends a Namf_MBSSroadcast_ContextsStatusNotify Response (MBS Session ID) to the AMF. The AMF sends a Broadcast Session Transport Response (MBS Session ID) to the NG-RAN. Finally, the NG-RAN performs PTP/PTM transmission to the UE.](dec689324b075952626a86da862b9549_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + + Note right of NG-RAN: 1. Select a CN to establish user plane + Note right of NG-RAN: 2. IGMP/MLD Join + Note right of NG-RAN: 3. Broadcast Session Transport Request (MBS Session ID, N3mb DL Tunnel Info) + Note right of AMF: 4. Namf_MBSSroadcast_ContextsStatusNotify Request (MBS Session ID, N3mb DL Tunnel Info) + Note right of MB-SMF: 5. N4mb Session Update + Note right of AMF: 6. Namf_MBSSroadcast_ContextsStatusNotify Response (MBS Session ID) + Note right of NG-RAN: 7. Broadcast Session Transport Response (MBS Session ID) + Note right of MB-UPF: 8. Media Streams + Note left of UE: 9. PTP/PTM transmission + +``` + +Sequence diagram for Broadcast MBS Session Transport Request. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF. The diagram shows the NG-RAN selecting a CN to establish the user plane. The NG-RAN then sends an IGMP/MLD Join to the MB-UPF. The NG-RAN sends a Broadcast Session Transport Request (MBS Session ID, N3mb DL Tunnel Info) to the AMF. The AMF sends a Namf\_MBSSroadcast\_ContextsStatusNotify Request (MBS Session ID, N3mb DL Tunnel Info) to the MB-SMF. The MB-SMF sends an N4mb Session Update to the MB-UPF. The MB-SMF sends a Namf\_MBSSroadcast\_ContextsStatusNotify Response (MBS Session ID) to the AMF. The AMF sends a Broadcast Session Transport Response (MBS Session ID) to the NG-RAN. Finally, the NG-RAN performs PTP/PTM transmission to the UE. + +Figure 6.7.3.5-1: Broadcast MBS Session Transport Request + +1. NG-RAN select a CN to establish user plane, utilizing the broadcast MBS session context stored in the NG-RAN. +2. If multicast transport of N3mb applies, the NG-RAN performs join the multicast group towards the LL SSM provided by the CN, and skip step 2 to step 5. +3. If unicast transport of N3mb applies, the NG-RAN allocates N3mb DL Tunnel Info, and sends N2 message (e.g. BROADCAST SESSION TRANSPORT REQUEST) to AMF, including the MBS Session ID and the N3mb DL Tunnel Info. +4. The AMF transfers the Namf\_MBSBroadcast\_ContextStatusNotify request to the MB-SMF, which contains the N2 message. +5. If unicast transport of N3mb applies, the MB-SMF sends an N4mb Session Modification Request to the MB-UPF to allocate the N3mb point-to-point transport tunnel for a replicated MBS stream for the MBS Session. The MB-UPF sends N4mb Session Modification Response to the MB-SMF. +6. The MB-SMF sends Namf\_MBSBroadcast\_ContextStatusNotify response to the AMF, which contains the N2 information. +7. The AMF forwards the received N2 information in N2 message (e.g. BROADCAST SESSION TRANSPORT RESPONSE) to the NG-RAN +8. The MB-UPF transmits the media stream to NG-RAN via N3mb multicast transport or unicast transport. +9. The NG-RAN brings the packets received over the air, reusing the existing radio resource. + +### 6.7.4 Impacts on services, entities and interfaces + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] are reused exception for the following additions: + +#### AF: + +- Provide the associated session ID (e.g. SSM used by AF or one TMGI selected by AF) to 5GC when creating MBS session. If AF determines to use TMGI as associated session ID, it needs to use this TMGI in the service announcement. + +#### NEF: + +- Provides the associated session ID to the MB-SMF if received in MBS Session Creation. + +#### MB-SMF: + +- Provides the associated session ID to the NG-RAN if received in MBS Session Start for Broadcast. + +#### NG-RAN: + +- Support the associated session ID and understand the association among those broadcast MBS sessions which delivers the same content. If the associated session ID is TMGI, the NG-RAN uses the TMGI indicated in associated session ID in radio interface, instead of the TMGI of broadcast MBS session. +- When broadcast MBS session start, if there is already established user plane of associated broadcast MBS session, the NG-RAN skips the user plane establishment of the broadcast MBS session. +- When broadcast MBS session release, if the user plane hasn't been established, the NG-RAN skips the user plane release of the broadcast MBS session. If the user plane has been established and there are some other associated broadcast MBS sessions, the NG-RAN may trigger Broadcast MBS Session Release Require procedure for each associated broadcast MBS session or trigger Broadcast MBS Session Transport Request procedure. +- When NG-RAN detects there is a failure in the CN which causes the NG-RAN cannot deliver the contents, the NG-RAN select another CN to trigger Broadcast MBS Session Transport Request procedure to establish the user plane. + +## 6.8 Solution #8: Allocating and using MOCN TMGI + +### 6.8.1 Introduction + +This solution addresses key issue #2 "5MBS MOCN Network Sharing". + +### 6.8.2 Functional description + +The proposed solution introduces a MOCN TMGI used for MBS session when the related MBS service needs to be provided over PLMNs sharing NG-RANs. The MOCN TMGI is identified by a shared PLMN ID it includes. A MOCN TMGI is allocated by one of the PLMNs and the MBS session identified by the MOCN TMGI is established only with the PLMN that has allocated the MOCN TMGI. The AF transmits the DL media stream to the PLMN that the MBS session was established. Therefore, the NG-RAN shared by the multiple PLMNs receives the DL media stream only from the 5GC of the PLMN that the MBS session was established and transmits the media stream by using the MOCN TMGI. + +For the MOCN TMGI, a Shared PLMN ID needs to be created and used by the PLMNs sharing NG-RANs. All the MB-SMFs in the PLMNs sharing NG-RANs are configured with the Shared PLMN ID so that the MB-SMFs can allocate the MOCN TMGIs. The MB-SMF understands whether a TAI is for shared NG-RAN or not by local configuration. + +Figure 6.8.2-1 shows an MBS example scenario including MOCN network sharing, specifically: + +- The AF wants to provide MBS service over PLMN-A, PLMN-B, PLMN-C and PLMN-D, i.e. to the UEs that are served by these PLMNs. +- UE-A, UE-B, UE-C and UE-D are served by PLMN-A, PLMN-B, PLMN-C and PLMN-D, respectively. +- NG-RAN#1 is shared by PLMN-A, PLMN-B and PLMN-C while NG-RAN#2 belongs only to PLMN-D. +- NG-RAN#1 and NG-RAN#2 covers the MBS service area for the MBS service provided by the AF. +- The AF is configured about which PLMNs share the NG-RAN, i.e. PLMN-A, PLMN-B and PLMN-C based on service level agreements with the PLMNs. + +![Diagram of MBS example scenario including MOCN network sharing. At the top, an AF (Application Function) is connected to four 5GC (5G Core) blocks: 5GC PLMN-A, 5GC PLMN-B, 5GC PLMN-C, and 5GC PLMN-D. Below the 5GCs, a dashed line labeled N2/N3 separates them from the NG-RANs. NG-RAN#1 is connected to 5GC PLMN-A, 5GC PLMN-B, and 5GC PLMN-C. NG-RAN#2 is connected to 5GC PLMN-D. Below the NG-RANs, a dashed line labeled 'Same MBS service' separates them from the UEs. UE-A, UE-B, and UE-C are connected to NG-RAN#1 and are grouped by a blue dotted oval labeled 'TMGI#1 (MOCN TMGI)'. UE-D is connected to NG-RAN#2 and is grouped by a pink dotted oval labeled 'TMGI#2'.](187bba66c887c745c512add37a577c5e_img.jpg) + +Diagram of MBS example scenario including MOCN network sharing. At the top, an AF (Application Function) is connected to four 5GC (5G Core) blocks: 5GC PLMN-A, 5GC PLMN-B, 5GC PLMN-C, and 5GC PLMN-D. Below the 5GCs, a dashed line labeled N2/N3 separates them from the NG-RANs. NG-RAN#1 is connected to 5GC PLMN-A, 5GC PLMN-B, and 5GC PLMN-C. NG-RAN#2 is connected to 5GC PLMN-D. Below the NG-RANs, a dashed line labeled 'Same MBS service' separates them from the UEs. UE-A, UE-B, and UE-C are connected to NG-RAN#1 and are grouped by a blue dotted oval labeled 'TMGI#1 (MOCN TMGI)'. UE-D is connected to NG-RAN#2 and is grouped by a pink dotted oval labeled 'TMGI#2'. + +Figure 6.8.2-1: MBS example scenario including MOCN network sharing + +The outline of the proposed solution for allocating and using MOCN TMGI is as below: + +- The AF performs TMGI allocation with only one PLMN among PLMNs sharing the NG-RANs to obtain a TMGI to identify new MBS session by indicating that MOCN TMGI allocation is requested (e.g. with PLMN-A in Figure 6.8.2-1). +- The MB-SMF allocates a MOCN TMGI and returns it to the AF. +- The AF performs MBS session establishment with the PLMN that has allocated the MOCN TMGI. +- The AF transmits the DL media stream to the PLMN that the MBS session was established. + +### 6.8.3 Procedures + +#### 6.8.3.1 Procedure for Broadcast using MOCN TMGI + +Figure 6.8.3.1-1 shows the procedure for Broadcast using MOCN TMGI. This procedure is based on the MBS example scenario depicted in Figure 6.8.2-1. + +![Sequence diagram illustrating the procedure for Broadcast using MOCN TMGI. The diagram shows interactions between User Equipment (UE-A, UE-B, UE-C, UE-D), NG-RANs (NG-RAN#1, NG-RAN#2), AMF, MB-UPF, MB-SMF, NEF/MBSSF, and the AF across two PLMNs (PLMN-A and PLMN-D).](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +The sequence diagram illustrates the following steps: + +- 1. TMGI allocation:** The AF sends a request to the NEF/MBSSF (PLMN-A), which is forwarded to the MB-SMF (PLMN-A). +- 2. Service announcement:** The MB-SMF (PLMN-A) sends service announcements to the AMF (PLMN-A), MB-UPF (PLMN-A), and NG-RAN#1. These are then passed on to the NEF/MBSSF (PLMN-A) and finally to the AF. +- 3. TMGI allocation:** The AF sends a request to the NEF/MBSSF (PLMN-D), which is forwarded to the MB-SMF (PLMN-D). +- 4. Service announcement:** The MB-SMF (PLMN-D) sends service announcements to the AMF (PLMN-D), MB-UPF (PLMN-D), and NG-RAN#2. These are then passed on to the NEF/MBSSF (PLMN-D) and finally to the AF. +- 5. Nnef\_MBSSession\_Create Request:** The AF sends a request to the NEF/MBSSF (PLMN-A). +- 6. MBS Session Establishment in PLMN-A 5GC and NG-RAN#1:** The NEF/MBSSF (PLMN-A) initiates session establishment with the AMF (PLMN-A) and NG-RAN#1. +- 7. Nnef\_MBSSession\_Create Response:** The NEF/MBSSF (PLMN-A) sends a response to the AF. +- 8. Nnef\_MBSSession\_Create Request:** The AF sends a request to the NEF/MBSSF (PLMN-D). +- 9. MBS Session Establishment in PLMN-D 5GC and NG-RAN#2:** The NEF/MBSSF (PLMN-D) initiates session establishment with the AMF (PLMN-D) and NG-RAN#2. +- 10. Nnef\_MBSSession\_Create Response:** The NEF/MBSSF (PLMN-D) sends a response to the AF. +- 11. Media stream:** The AF sends a media stream to the NEF/MBSSF (PLMN-A). +- 12. Media stream:** The NEF/MBSSF (PLMN-A) forwards the media stream to the AMF (PLMN-A). +- 13. PTM transmission:** The AMF (PLMN-A) performs PTM transmission to UE-A, UE-B, and UE-C via NG-RAN#1. +- 14. Media stream:** The AF sends a media stream to the NEF/MBSSF (PLMN-D). +- 15. Media stream:** The NEF/MBSSF (PLMN-D) forwards the media stream to the AMF (PLMN-D). +- 16. PTM transmission:** The AMF (PLMN-D) performs PTM transmission to UE-D via NG-RAN#2. + +Sequence diagram illustrating the procedure for Broadcast using MOCN TMGI. The diagram shows interactions between User Equipment (UE-A, UE-B, UE-C, UE-D), NG-RANs (NG-RAN#1, NG-RAN#2), AMF, MB-UPF, MB-SMF, NEF/MBSSF, and the AF across two PLMNs (PLMN-A and PLMN-D). + +**Figure 6.8.3.1-1: Procedure for Broadcast using MOCN TMGI** + +1. The AF requests TMGI allocation with one of PLMNs that it wants to provide broadcast service over. In this figure, the AF performs TMGI allocation with PLMN-A to obtain a TMGI to identify new MBS session. + +Steps 1 to 6 in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4] are performed with the following differences: + +- In step 1, the following information is provided by the AF when requesting TMGI allocation. + - a) A list of PLMNs that the AF wants to provide MBS service (i.e. PLMN-A, PLMN-B, PLMN-C in this figure). + - b) Indication that MOCN TMGI allocation is requested. + +NOTE 1: In Rel-17, the MBS service area is provided by the AF to indicate the possible service area for those TMGI(s) to be allocated, which may be needed for local MBS. In this solution, the MBS service area from the AF can be used for the MB-SMF to check whether all the MBS service area's NG-RANs are shared by the PLMNs that the AF wants to provide MBS service. + +- In step 5, the MB-SMF allocates a MOCN TMGI based on the information provided by the AF and local configuration related to MOCN network sharing. In this figure, the local configuration related to MOCN network sharing is that PLMN-A, PLMN-B and PLMN-C share NG-RANs. If some of the NG-RANs in the MBS service area provided by the AF are not shared by all the PLMNs that the AF wants to provide MBS service (i.e. some of the NG-RANs in the MBS service area provided by the AF are dedicated to specific PLMN), the MB-SMF allocates a MOCN TMGI only for the MBS service area served by the NG-RANs that are shared by those PLMNs. +- In step 5, the following information is provided by the MB-SMF when returning the TMGI. + - i) Indication that MOCN TMGI is allocated. + - ii) MBS service area that the allocated MOCN TMGI applies, if the MOCN TMGI does not apply to all the MBS service area that the AF provided when requesting TMGI allocation. + +If the MOCN TMGI allocated by the MB-SMF does not apply to all the MBS service area that the AF wants to provide MBS service, the AF performs TMGI allocation and MBS session creation with each PLMN for the MBS service area that the MOCN TMGI does not apply. The AF also may perform a Service Announcement including the TMGI dedicated to the PLMN to the UE in the PLMN. + +2. The AF may perform a Service Announcement including the MOCN TMGI towards UE-A, UE-B and UE-C. + +NOTE 2: When the UE receives Service Announcement including MOCN TMGI for shared NG-RAN(s) and Service Announcement including non-MOCN TMGI for dedicated NG-RAN(s) (i.e. TMGI dedicated to the PLMN) for same service from the AF, the service layer (e.g. 5MBS client, MC service client) or the application layer of the UE needs to understand these two TMGIs are for same service based on the information in the Service Announcements, e.g. SDP info with IP multicast address and port#, Service ID. + +3. The AF performs TMGI allocation with PLMN-D to obtain a TMGI to identify new MBS session as specified in steps 1 to 6 in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4]. + +The MBS session identified by the MOCN TMGI allocated in step 1 and the MBS session identified by the TMGI allocated in this step are for the same broadcast service. + +Step 1 and step 3 can be performed in parallel. + +4. The AF may perform a Service Announcement towards UE-D. + +5. The AF performs MBS session creation with PLMN-A by providing description for the MBS session for a previously allocated MOCN TMGI in step 1, as specified in step 8 in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4]. + +6-7. The MBS session is established in PLMN-A as specified in steps 9 to 20 in clause 7.1.1.2 or steps 9 to 33 in clause 7.1.1.3 of TS 23.247 [4]. + +The AF may also perform a Service Announcement towards UE-A, UE-B and UE-C at this stage. + +8. The AF performs MBS session creation with PLMN-D by providing description for the MBS session for a previously allocated TMGI in step 3, as specified in step 8 in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4]. + +9-10. The MBS session is established in PLMN-D as specified in steps 9 to 20 in clause 7.1.1.2 or steps 9 to 33 in clause 7.1.1.3 of TS 23.247 [4]. + +The AF may also perform a Service Announcement towards UE-D at this stage. + +11. The AF starts transmitting the DL media stream to PLMN-A as specified in step 13 in clause 7.3.1 of TS 23.247 [4]. + +12. The MB-UPF of PLMN-A transmits the media stream to NG-RAN via N3mb multicast transport or point-to-point transport. + +13. NG-RAN#1 shared by PLMN-A, PLMN-B and PLMN-C transmits the received DL media stream using DL PTM resources. + +UE-A, UE-B and UE-C can receive the media stream. + +14. The AF starts transmitting the DL media stream to PLMN-D as specified in step 13 in clause 7.3.1 of TS 23.247 [4]. The DL media stream is same to that in step 11 which means the AF transmits the same DL media stream to PLMN-A and PLMN-D. + +Step 11 and step 14 can be performed in parallel. + +15. The MB-UPF of PLMN-D transmits the media stream to NG-RAN via N3mb multicast transport or point-to-point transport. + +16. NG-RAN#2 of PLMN-D transmits the received DL media stream using DL PTM resources. + +UE-D can receive the media stream. + +### 6.8.4 Impacts on services, entities and interfaces + +AF: + +- supports MOCN TMGI allocation request. + +MB-SMF: + +- supports MOCN TMGI allocation. + +NEF: + +- Nnef\_MBSTMGI\_Allocate service operation supports additional parameters related to MOCN TMGI allocation. + +UE: + +- supports MOCN TMGI. + +NG-RAN: + +- supports MOCN TMGI. + +## 6.9 Solution #9: Broadcast services considering MOCN RAN + +### 6.9.1 Introduction + +This solution addresses Key Issue #2. + +### 6.9.2 Functional description + +It is assumed to reuse the current architecture in Rel-17 MBS specification (see TS 23.247 [4]). + +A TMGI is assigned and used for a broadcast service in an operator's network. However, if an NG-RAN is shared among operators, a primary TMGI may be selected and used instead of the TMGI in the shared NG-RAN if MOCN operators share a same broadcast service. + +### 6.9.3 Procedures + +#### 6.9.3.1 General + +When a broadcast service is shared among operator's networks, the contents provider may recognize the using TMGI for each operator. So that if the operators share some NG-RAN(s) (call MOCN NG-RAN), AF/ contents provider may provide the TMGI list for the broadcast service to 5GS. + +Then, the MOCN NG-RAN decides to use a primary TMGI out of the TMGI list, and the primary TMGI and its usage area (i.e. NG-RAN location or Cell IDs) is notified to AF so that such information can be announced to the UEs. + +NOTE: Security (i.e. en/decryption of content) is assumed to be not supported in 5GS, but possible by application layer. + +#### 6.9.3.2 Broadcast Session Start procedure + +![Sequence diagram for Broadcast Session Start procedure for MOCN NG-RAN. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, and AF/Contents provider. The process starts with TMGI allocation and AF recognizing broadcast services. The MB-SMF creates an MBS session context, and the NG-RAN advertises the primary TMGI to the UE. The media stream is then transmitted to the NG-RAN for broadcast to the UE.](e05122559f56af5699789b7118d8fe87_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant NEF/MBSF + participant AF/Contents provider + + Note right of AF/Contents provider: 1. AF recognizes the same broadcast services for multiple TMGIs. + AF/Contents provider->>NEF/MBSF: 2. Nnef_MBSSession_Create request (TMGI, additional TMGI list) + NEF/MBSF->>MB-SMF: 3. Nmbsmf_MBSSession_Create request (TMGI, additional TMGI list) + MB-SMF->>MB-UPF: 4. N4mb Session request/response + MB-SMF->>AMF: 5. Namf_MBSSBroadcast_ContextCreate Request(TMGI, MBS service area, additional TMGI list) + AMF->>NG-RAN: 6. N2 Message request() + Note left of NG-RAN: 7. MBS session Context created. Select a Primary TMGI if it is a shared RAN + NG-RAN->>AMF: 8. N2 Message response(TMGI, N3mb DL tunnel info, Primary TMGI, NG-RAN location) + AMF->>MB-SMF: 9. Namf_MBSSBroadcast_ContextCreate Response() + Note right of MB-SMF: 0. TMGI allocation + MB-SMF->>MB-UPF: 10. N4mb Session update(TMGI, N3mb DL tunnel info) + MB-SMF->>NEF/MBSF: 11. Nmbsmf_MBSSession_Create rsp( TMGI, Primary TMGI, NG-RAN location) + NEF/MBSF->>AF/Contents provider: 12. Nnef_MBSSession_Create rsp + NG-RAN->>UE: 13. NG-RAN advertise the primary TMGI + NG-RAN->>AMF: 14. MBS service announcement(TMGI, {Primary TMGI, NG-RAN location, MBS Frequency Selection Area ID}) + Note right of MB-UPF: 15. Media stream + MB-UPF->>NG-RAN: 15. Media stream + Note left of NG-RAN: 16. NG-RAN transmit the broadcast traffic over the primary TMGI only + Note left of UE: 17. UE may get the broadcast service via the Primary TMGI if it is in the shared RAN + +``` + +Sequence diagram for Broadcast Session Start procedure for MOCN NG-RAN. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, and AF/Contents provider. The process starts with TMGI allocation and AF recognizing broadcast services. The MB-SMF creates an MBS session context, and the NG-RAN advertises the primary TMGI to the UE. The media stream is then transmitted to the NG-RAN for broadcast to the UE. + +Figure 6.9.3.2-1: Broadcast Session start for MOCN NG-RAN + +The following additions apply compared to clause 7.3.1 of TS 23.247 [4]: + +0-3. AF performs TMGI allocation and MBS session creation as specified in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4]. The AF provides additionally the TMGI list for the broadcast service which each operator uses in MBS session creation request. + +5-6. MB-SMF invokes Namf\_MBSSBroadcast\_ContextCreate Request including AF may provide the TMGI list for the broadcast service which each operator uses in the N2 SM container. + +7. NG-RAN node creates a Broadcast MBS Session Context. If the NG-RAN is MOCN NG-RAN, it selects a primary TMGI out of the TMGI list. + +NOTE 1: How to select a primary TMGI follows local policy or NG-RAN implementation. + +8-12. NG-RAN responds additionally the primary TMGI and its location(e.g. Cell ID(s)) if the NG-RAN is MOCN NG-RAN, where such information is delivered to AF. At step 10 MB-SMF lets MB-UPF block and not deliver Broadcast service media stream to the NG-RAN if TMGI is different from the primary TMGI. + +13. MOCN NG-RAN advertises the primary TMGI for the broadcast service instead of using the TMGI for operator's network. + +**Editor's note:** Details will be confirmed by the RAN WGs. + +14. Service announcement to UEs includes the primary TMGI and its usage area (i.e. NG-RAN location or Cell IDs) as well as the TMGI for operator's network. + +**Editor's note:** Whether it is possible to prevent that each NG-RAN node selects a different primary TMGI and a number of TMGIs with potentially complicated location areas thus needs to be included in the service announcement is FFS. + +15. Broadcast service media stream is delivered to MOCN NG-RAN. + +NOTE 2: Broadcast service media stream is not delivered to MOCN NG-RAN via each operator's TMGI which is different from the primary TMGI. + +16. MOCN NG-RAN uses the primary TMGI only instead of TMGI for the same broadcast service. + +17. UE receives the broadcast service via the primary TMGI when it is in the MOCN NG-RAN. + +#### 6.9.3.3 Broadcast Session update and release procedure + +The clause 7.3.3 of TS 23.247 [4] is used when the broadcast MBS session is updated, which is triggered from AF or contents provider. + +However, when the primary TMGI can not be used longer in the NG-RAN e.g. due to the TMGI's PLMN becomes not to share the NG-RAN, NG-RAN should select another valid TMGI as a primary TMGI and update the broadcast MBS session with the new primary TMGI for the other PLMNs than the old primary TMGIs as in the following figure. + +![Sequence diagram of NG-RAN triggered primary TMGI update procedure. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, AF/Contents provider. The process involves detecting the old primary TMGI is invalid, selecting a new one, updating context in AMF/MB-SMF, notifying AF, and advertising the new TMGI to UEs.](bc9d0c0b02cbe628b1b6548cc1107734_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + participant MB-UPF + participant NEF/MBSF + participant AF/Contents provider + + Note right of NG-RAN: 0. Media stream (via the primary TMGI) + NG-RAN->>UE: 1. NG-RAN transmits the broadcast traffic over the primary TMGI + Note right of NG-RAN: 2. NG-RAN detects that the primary TMGI is not valid any more. And select a new TMGI + Note right of NG-RAN: 3. NG-RAN performs broadcast release require for the old primary TMGI + Note left of AMF: For other TMGIs than the old primary TMGI + NG-RAN->>AMF: 4. MBSBroadcastContextUpdate request(TMGI, N3mb DL tunnel info, Primary TMGI, NG-RAN location) + AMF->>MB-SMF: 5. Nmbsmf_MBSBroadcast_Contextupdate request() + MB-SMF->>MB-UPF: 6. N4mb_Session_update(TMGI, N3mb DL tunnel info) + MB-UPF->>AMF: 7. + AMF->>NG-RAN: 8. + NG-RAN->>UE: 9. NG-RAN advertise the new primary TMGI + MB-SMF->>NEF/MBSF: 10. Nmbsmf_MBSSession_StatusNotify(TMGI, Primary TMGI, NG-RAN location) + NEF/MBSF->>AF/Contents provider: 11. Nnef_MBSSession_StatusNotify + Note right of AF/Contents provider: 12. AF replaces the primary TMGI + AF/Contents provider->>NG-RAN: 13. MBS service announcement(TMGI, {new Primary TMGI, NG-RAN location, MBS Frequency Selection Area ID}) + Note right of NG-RAN: 14. Media stream (via the new primary TMGI) + NG-RAN->>UE: 15. NG-RAN transmits the broadcast traffic over the new primary TMGI + +``` + +Sequence diagram of NG-RAN triggered primary TMGI update procedure. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, NEF/MBSF, AF/Contents provider. The process involves detecting the old primary TMGI is invalid, selecting a new one, updating context in AMF/MB-SMF, notifying AF, and advertising the new TMGI to UEs. + +Figure 6.9.3.3-1: NG-RAN triggered primary TMGI update procedure + +0. Broadcast service media stream is delivered to MOCN NG-RAN via the primary TMGI. + +1-2. When the primary TMGI is not valid any more, it selects a new primary TMGI. + +3. For the old primary TMGI, NG-RAN performs the broadcast release require(the clause 7.3.6 of TS 23.247 [4]) for the old primary TMGI. + +For the other TMGIs than the old primary TMGI, steps 4~13 are applied. + +4-5. The new primary TMGI is updated in the MBS Broadcast context in AMF and MB-SMF. + +6. In case that the new primary TMGI only is used for broadcast traffic delivery among the shared PLMNs, MB-SMF may update the forwarding rules in the MB-UPF(e.g. for other PLMN than the primary TMGI, MB-UPF is allowed to block the broadcast traffics to NG-RAN, which are duplicated with the primary TMGI) + +9. MOCN NG-RAN advertises the new primary TMGI for the broadcast service instead of using the old primary TMGI. + +10-11. Information on the primary TMGI update is notified to AF. + +12-13. AF updates the primary TMGI and announces the UEs. + +**Editor's note:** It is FFS whether there can be service interruptions until the UEs receive the updated service announcement. + +14-15. via the new primary TMGI the broadcast service is performed in the MONC NG-RAN. + +The following additions apply compared to clause 7.3.2 of TS 23.247 [4] when the broadcast MBS session is released: + +- If the broadcast MBS session is used as the primary TMGI in the NG-RAN, NG-RAN should select another valid TMGI as a primary TMGI, and for the other PLMNs than the old primary TMGIs the broadcast MBS session should be updated as above procedure. + +### 6.9.4 Impacts on services, entities and interfaces + +**Editor's note:** This clause describes impacts to existing services, entities and interfaces. + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] is reused exception for the following additions: + +AF, NEF: + +- Support to provide the TMGI list for the broadcast service which each operator uses in MBS session creation request only when there exists a MOCN NG-RAN among operators. +- Obtain a primary TMGI which will be used in the MOCN NG-RAN and announce to UEs the primary TMGI and its usage area. + +MB-SMF: + +- Send TMGI list of other networks for a same broadcast service to NG-RAN node. +- Let MB-UPF block and not deliver Broadcast service media stream to the NG-RAN node if TMGI is different from the primary TMGI. + +NG-RAN: + +- In the case of MOCN NG-RAN, decide the primary TMGI for a same broadcast service, which will be used for the broadcast service in the MOCN NG-RAN. +- NG-RAN does not receive broadcast service media stream for the TMGI of MBS session establishment if TMGI is different from the primary TMGI. + +UE: + +- Receive the broadcast service via the primary TMGI in the MOCN NG-RAN. + +**Editor's note:** other additional impacts are FFS. + +## 6.10 Solution #10: AF triggered MBS session management + +### 6.10.1 Introduction + +This solution addresses Key Issue #3. + +This solution addresses the case that AF dynamically demands 5GC to use multicast transport for the content delivery, e.g. due to publisher dynamically provides the service and APP in UE interacts with AF for content fetching of the service, and according to the response from 5GC to select unicast mode for content delivery, e.g. UE does not support multicast transport (out of the scope of this study). The service may contain multiple media streams but only part of the media streams is demanded to use multicast transport. + +### 6.10.2 Functional description + +It is most popular today that content provider provides video to users via APP in UE, but in unicast transport style. Live stream dramatically grows today, which also uses unicast transport. The video services provided by AF can not only be published by the content provider, but also can be published by users of the content provider dynamically. The consumer will not only be a receiver in today's video stream services, but also a participant to interact with the services, such as sending message to interact with the live stream salesperson, sending message when watching a video to share with all the viewers. + +In most cases, the users visit the portal for requesting the content, and the AF holds most business logic for providing the services, e.g. the location related operations, the user authentication and authorization per the AF instead of the + +service, etc. And the service, in most cases, will contain multiple media streams that only part of the streams is demanded to be delivered via multicast transport. This business model is consistent for services provided by AF. + +In order to use multicast transport for multicast streams of those services, the 5GC needs to identify the multicast data and uses multicast transport for the delivery and do not impact the AF service logic. And in order to not limiting the consumers based on the UE capability, the 5GC and AF needs to prepare unicast mode in case the UE does not support receiving data with multicast transport (this is out of the scope of this study). + +**Editor's note:** Further explanation is required why the use cases in this clause cannot be addressed with Rel-17 MBS procedures. + +The Rel-17 MBS AF may first request TMGIs (optional), creates the MBS session, and may provision the authorization information for allowing UEs to join (optional). + +This solution provides a way for AF to deliver the traffic and knows who really joins the session for starting the interactive data exchange. + +**Editor's note:** Multicast traffic delivery is typically not started each time a user joins a session. The AF could also know that a user requested to join a session via the same application level interactions if the UE subsequently sends the join request as in Rel-17. + +This solution is based on the unicast business model that UE requests service from AF and AF requests resources from 5GC both for unicast and multicast transport for different flows. + +**Editor's note:** For unicast delivery no AF interactions are required unless sponsored connectivity or special QoS is envisioned. + +**Editor's note:** Compared to the Rel-17 interactions, sending separate join request for all UEs may lead to far more signalling interactions between AF and network. + +### 6.10.3 Procedures + +#### 6.10.3.1 General + +Following figure 6.10.3.1-1 shows the general concept of the solution: + +![Diagram of multicast session distribution from AF to UEs via 5GC and NG-RAN.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates the general concept of multicast session delivery. An Application Function (AF) sends data for Multicast Sessions 1, 2, and 3 through a Tunnel to the 5G Core (5GC). The 5GC then distributes these sessions to different NG-RAN nodes: Multicast Session 1 goes to one NG-RAN serving two UEs; Multicast Session 2 goes to another; and Multicast Session 3 goes to a third. Boxes on the right and bottom detail flow descriptions for three services. + +**Example of flow descriptions per UE** + +**Service 1:** + >For UEa: + >>Flow1: Src: unicast IP0/PORT01, TCP + >>Flow2 (multicast alternatively): Src: unicast IP0/PORT02, Dst: unicast IPa/PORTa, **multicast IP1**, UDP + >.................................................................. + >For UEx: + >>Flow1: Src: unicast IP0/PORT01, TCP + >>Flow2 (multicast alternatively): Src: unicast IP0/PORT02, Dst: unicast IPx/PORTx, **multicast IP1**, UDP + +**Service 2:** + >For UEb: + >>Flow1 (multicast alternatively): Src: unicast IP0/port03, Dst: unicast IPb/PORTb, **multicast IP2**, UDP + >.................................................................. + >For UEy: + >>Flow1 (multicast alternatively): Src: unicast IP0/port03, Dst: unicast IPy/PORTy, **multicast IP2**, UDP + +**Service 3:** + >For UEc: + >>Flow1: Src: unicast IP0/port04, TCP + >>Flow2 (multicast alternatively): Src: unicast IP0/port05, Dst: unicast IPc/PORTc, **multicast IP3**, UDP + >.................................................................. + >For UEz: + >>Flow1: Src: unicast IP0/port04, TCP + >>Flow2 (multicast alternatively): Src: unicast IP0/port05, Dst: unicast IPz/PORTz, **multicast IP3**, UDP + +Diagram of multicast session distribution from AF to UEs via 5GC and NG-RAN. + +Figure 6.10.3.1-1: General concept + +The AF delivers the multicast data of different multicast sessions to the 5GC, which may be in a tunnel between the AF and the 5GC if the transport network between the AF and 5GC does not support multicast. The AF can send multiple MBS Session data in one tunnel, the 5GC distinguishes the multicast session based on the mapping between the packet filters and the MBS Session ID. The content delivery is requested by the UEs over application layer, and the AF handles the service logic. + +Besides service announcement, the content provider may use a portal, which is out of 3GPP scope, to publish the services, which may be dynamically published, e.g. a live stream arranged by a live streamer, a live interview for breaking news, etc. The user may visit the portal via an APP in the UE and request the content of an MBS service, which may be interactive MBS service, i.e. contains multicast service data and unicast service data. Although service announcement for MBS Session is supported, but currently most content providers still want to use web portal, which is consistent as unicast service announcement. + +Editor's note: Rel-17 allows for application dependent service announcements. + +Similar as unicast business model, the AF of the content provider sends the flow descriptions per UE, which includes different multicast services, to the 5GC for asking transport for the services, but the flow descriptions includes multicast information, which could be seen as AF proxies the UE join to 5GC. + +Editor's note: For unicast delivery no AF interactions are typically required. + +**Editor's note:** For multicast, flow description will not depend on the UE and it may be preferable to provide it only a single time for an MBS session to avoid duplicated signalling. + +#### 6.10.3.2 AF triggered MBS Session management procedures with PCC + +This procedure is for AF triggered MBS Session Join or Leave when dynamic PCC is deployed. If the transport network between the AF and the 5GC does not support multicast transport, pre-configured tunnel is used for delivering multicast data from the AF to the 5GC. + +![Sequence diagram showing AF triggered MBS Session management procedures with PCC. The diagram illustrates the interaction between various network functions (UE, NG-RAN, AMF, SMF/UPF, PCF, UDM, MB-UPF, MB-SMF, MB-PCF, NRF, NEF, AF) to establish and manage an MBS session. The process starts with an APP Layer service request from the AF, followed by MBS On-demand Session Create/Update requests, authorization checks, policy authorization, and finally MBS data delivery.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF/UPF + participant PCF + participant UDM + participant MB-UPF + participant MB-SMF + participant MB-PCF + participant NRF + participant NEF + participant AF + + Note over UE, AF: 1. APP Layer: Service request with UE address (e.g. HTTP Get) + AF->>NEF: 2a. MBS On-demand Session Create/Update Req. + Note right of NEF: 2b. Authorization + Note right of NEF: 2c. Procedures in clause 7.1.1.2/3 of TS 23.247 + NEF->>PCF: 3. Policy Authorization Create/Update req./resp. + PCF->>NEF: 4. MBS On-demand Session Create/Update Resp. + NEF->>PCF: 5. Policy Authorization Subscribe + PCF->>SMF: 6. PCF Initiate Policy Update Notify (SSM, multicast flows info, unicast QoS info) + Note over UE, SMF: 7. PDU Session Modification Procedure for unicast + Note over SMF, MB-SMF: 8. Steps 2-4 in clause 7.2.1.3 of TS 23.247, or steps 3-6 in clause 7.2.3.4 + SMF->>UE: 9a. PDU Session Mod. Procedure for unicast and multicast + Note over SMF, MB-SMF: 9b. Shared delivery establishment/release (TMGI) + SMF->>PCF: 10. SM Initiate Policy Update + PCF->>NEF: 11. Policy Authorization Notify + NEF->>AF: 12. MBS On-demand Session Notify + Note over SMF, MB-SMF: MBS data delivery + AF->>MB-SMF: MBS data + +``` + +Sequence diagram showing AF triggered MBS Session management procedures with PCC. The diagram illustrates the interaction between various network functions (UE, NG-RAN, AMF, SMF/UPF, PCF, UDM, MB-UPF, MB-SMF, MB-PCF, NRF, NEF, AF) to establish and manage an MBS session. The process starts with an APP Layer service request from the AF, followed by MBS On-demand Session Create/Update requests, authorization checks, policy authorization, and finally MBS data delivery. + +**Figure 6.10.3.2-1: AF triggered MBS Session management procedures with PCC** + +- The UE established a PDU Session as described in clause 7.2.1.2 of TS 23.247 [4], during the PDU Session Establishment procedure, the UE indicates the MBS capability to SMF. The content provider may use a portal to publish the services, which may be dynamically published, e.g. a live stream arranged by a live streamer, a live interview for breaking news, etc. The user may visit the portal via an APP in the UE and request the content of an MBS service or stops the content of an MBS service, which may be interactive MBS service, i.e. contains multicast service data and unicast service data. The APP sends UE address and the UDP port for receiving the multicast data to the AF. + +NOTE: In case the UE has multiple PDU Sessions, the URSP in the UE needs to make sure that the APP uses the associated PDU Session for unicast traffic delivery. + +- The steps are same as described in clauses 4.15.6.6 and 4.15.6.6a of TS 23.502 [3], with following differences: + +- The name of service operations exposed by NEF is different, and the flow description(s), if included, includes some packet filters that additionally contains IP multicast address to indicate that the data of the unicast flow can be alternatively sent via multicast (in case unicast transport is used, the network can know that it is for a multicast service), c.f. figure 6.10.3.1-1. +- The flow description(s) sent to PCF includes some packet filters that additionally contains IP multicast address. +- If the MBS Session has not been created, the steps 10-17 in clause 7.1.1.2 or steps 10-26 in clause 7.1.1.3 of TS 23.247 [4] are performed to create the MBS Session. + +If the AF is in trust domain, the AF can perform steps 3, 5, and 11 directly. + +- The PCF invokes Policy Update Notify towards the SMF, which includes unicast QoS information and flow description(s) that additionally contains IP multicast address (i.e. multicast flow descriptions). + +7. The SMF may initiate PDU Session Modification procedure for updating unicast QoS flows. +8. **MBS Session Join:** For multicast flow creation, the steps 2-4 in clause 7.2.1.3 of TS 23.247 [4] are performed with following differences: + - If the authorization fails (feature level authorization is used for this procedure, i.e. whether the UE is allowed to use 5MBS or not based on subscription), go to step 10 and SMF indicates cause value to the PCF. The AF can use unicast transport for the multicast data delivery. + +**MBS Session Leave:** For multicast flow releasing, the steps 3-6 in clause 7.2.1.4 of TS 23.247 [4] are performed with following differences: + + - If the MB-SMF does not serve the MBS Session any more (i.e. all SMFs unsubscribed the MBS Session Context Status), steps 6-8 in clause 7.1.1.4 or 7-11 in clause 7.1.1.5 of TS 23.247 [4] are performed to delete the MBS Session. +9. **MBS Session Join:** For multicast QoS information creation, steps 5-12 described in clause 7.2.1.3 of TS 23.247 [4] are performed with following differences: + - The step 5 is Namf\_Communication\_N1N2MessageTransfer. If the MBS capability of UE is received and multicast streams are demanded, the SMF includes QoS rules for DL only in the N1 Message Container in step 5, which will include MBS Session ID as a parameter in the QoS rules for DL only. The QoS rules for DL only can be used by the UE to perform NATP, i.e. transfer the IP multicast address in the received multicast packets to the UE IP address, and to transfer the destination UDP port in the received multicast packets to the UDP port that the APP in the UE used to receive the data. + - If the MBS capability of UE is not received, the SMF does not include MBS Session related information in the N2 SM info send to NG-RAN (i.e. individual delivery is selected), as well as instructs the UPF to perform NATP as described in above bullet for the incoming multicast data of the MBS Session towards the UE (i.e. unicast mode is selected). + - If unicast QoS parameters are received in step 6, the SMF also update the unicast QoS flows during the PDU Session Modification procedure. + - If the UE denies the join, it can send a cause value to the SMF via PDU Session Modification Ack, and MBS session leave for the UE is triggered by the SMF then. + +**MBS Session Leave:** For multicast QoS information removal, steps 3-11 and 13 described in clause 7.2.2.2 of TS 23.247 [4] are performed with following differences: + + - The step 7 is Namf\_Communication\_N1N2MessageTransfer, and the SMF also update the unicast QoS flows during the PDU Session Modification procedure if unicast QoS flows need to be updated. +10. The SMF notifies the PCF. +11. The PCF Notifies the NEF with cause value related to MBS. +12. The NEF notifies the AF with the cause value. If the PCF does not support MBS (i.e. no corresponding cause value indicated), the corresponding unicast QoS flow will be established, the AF can use unicast transport for the multicast data delivery. + +#### 6.10.3.3 AF triggered MBS Session management procedures without PCC + +This procedure is for AF triggered MBS Session Join or Leave when dynamic PCC is not deployed. If the transport network between the AF and the 5GC does not support multicast transport, pre-configured tunnel is used for delivering multicast data from the AF to the 5GC. + +![Sequence diagram illustrating AF triggered MBS Session management procedures without PCC. The diagram shows interactions between UE, NG-RAN, AMF, SMF/UPF, MB-UPF, MB-SMF, NRF, NEF, and AF. The sequence starts with 0a. PDU Session Establishment, followed by 0b. SMF-NEF connection create (UE address). Then, 1. Step 1-2 of clause 6.10.3.2, 2. MBS On-demand Session Create/Update Req. (SSM), 3. Step 7-8 of clause 6.10.3.2, 4. MBS On-demand Session Create/Update Resp. (), 5. MBS On-demand Session Create/Update Resp., 6. Step 9 of clause 6.10.3.2, 7. MBS On-demand Session Notify, 8. MBS On-demand Session Notify, and finally MBS data delivery.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF/UPF + participant MB-UPF + participant MB-SMF + participant NRF + participant NEF + participant AF + + Note over UE, SMF/UPF: 0a. PDU Session Establishment + SMF/UPF->>NEF: 0b. SMF-NEF connection create (UE address) + Note over SMF/UPF, MB-UPF: 1. Step 1-2 of clause 6.10.3.2 + NEF->>SMF/UPF: 2. MBS On-demand Session Create/Update Req. (SSM) + Note over SMF/UPF, MB-UPF: 3. Step 7-8 of clause 6.10.3.2 + SMF/UPF->>NEF: 4. MBS On-demand Session Create/Update Resp. () + NEF->>AF: 5. MBS On-demand Session Create/Update Resp. + Note over SMF/UPF, MB-UPF: 6. Step 9 of clause 6.10.3.2 + SMF/UPF->>NEF: 7. MBS On-demand Session Notify + NEF->>AF: 8. MBS On-demand Session Notify + Note over NEF, AF: MBS data + AF->>MB-UPF: MBS data delivery + +``` + +Sequence diagram illustrating AF triggered MBS Session management procedures without PCC. The diagram shows interactions between UE, NG-RAN, AMF, SMF/UPF, MB-UPF, MB-SMF, NRF, NEF, and AF. The sequence starts with 0a. PDU Session Establishment, followed by 0b. SMF-NEF connection create (UE address). Then, 1. Step 1-2 of clause 6.10.3.2, 2. MBS On-demand Session Create/Update Req. (SSM), 3. Step 7-8 of clause 6.10.3.2, 4. MBS On-demand Session Create/Update Resp. (), 5. MBS On-demand Session Create/Update Resp., 6. Step 9 of clause 6.10.3.2, 7. MBS On-demand Session Notify, 8. MBS On-demand Session Notify, and finally MBS data delivery. + +**Figure 6.10.3.3-1: AF triggered MBS Session management procedures without PCC** + +0. After the PDU Session Establishment procedure, the SMF creates the SMF-NEF connection with the NEF similar as described in clauses 4.25.2 and 5.2.6.15 of TS 23.502 [3], during which the SMF sends the UE address, i.e. IP address, to the NEF. The difference is that the subscription of the UE includes the NEF ID for MBS, the NIDD information in the request to the NEF is changed to MBS information with same content, i.e. GPSI, AF ID, and additional UE address is included. +1. Same as steps 1-2 in clause 6.10.3.2. +2. The NEF invokes the MBS On-demand Session Create/Update with SSM towards the SMF. +3. Same as steps 7-8 in clause 6.10.3.2. +- 4-5. The SMF responds to the NEF. The NEF responds to the AF. +6. Same as step 9 in clause 6.10.3.2. +- 7-8. The SMF notifies to the NEF. The NEF notifies to the AF. + +### 6.10.4 Impacts on services, entities and interfaces. + +#### UE: + +- May support indicating MBS capability to SMF during PDU Session Establishment. +- May support NATP performance for incoming multicast data. + +#### NEF/MBSF: + +- Support handling on-demand MBS Session service to AF (similar as AF Session with QoS service). +- May support additionally handling UE address during SMF-NEF connection establishment procedure as described in TS 23.502 [3] clause 4.25.2, which is used to find out the serving SMF. + +#### SMF: + +- Support determining delivery method and instructs UPF to perform NATP for multicast data based on UE MBS capability. +- May support sending UE address during the SMF-NEF connection establishment procedure to NEF after associated PDU Session Establishment. + +#### **PCF:** + +- Support handling flow description(s) with SSM. +- Support sending cause value for handling multicast flows to NEF/AF. + +## 6.11 Solution #11: Solution on enabling the on-demand multicast MBS session management + +### 6.11.1 Introduction + +This solution addresses Key Issue #3: On demand multicast MBS session. + +### 6.11.2 Functional description + +#### 6.11.2.1 Use cases + +The use case for on demand MBS multicast session can be described as follows. + +One typical use case for KI #3 is the content provider delivering its content. Before a content provider (CP) delivers content, its subscriber needs to firstly request the content by sending application level request (e.g. clicking the "view" link). Such framework doesn't take into consideration of the scale of the amount of subscribers. + +As analysed by S2-2006311: + +*if the requested content is real-time, popular, and high data rate (e.g. World Cup Soccer matches, American Football games or Chinese Spring Festival Gala), a huge number of viewers simultaneously watching will put a huge burden on the network service providers (SPs).* + +*As more and more people watch content on their UEs, this will also impact MNOs because many duplicate copies of the same content will be delivered by the MNOs.* + +One way to resolve the large scale delivery of real-time high data rate content is to enable on-demand multicast MBS session management triggered by the AF. + +The trigger by the AF for enabling the on-demand multicast MBS session management, can be further based on network analysis result. To this end, the AF or CP subscribes to or requests the network analytics information from the NWDAF as specified in TS 23.288 [10]. Based on the analytics information, e.g. Observed Service Experience analytics defined in clause 6.4 of TS 23.288 [10], the AF decides to set/update the multicast related service parameters. + +For one AF session, the AF uses "AF session with required QoS update" procedure" defined in clause 4.15.6.6a to provide multicast related service parameters, including a multicast indication which indicates that the service data flows of the AF session can be transmitted over a multicast MBS session identified by an MBS session ID, to the PCF via the NEF. Based on multicast related service parameters, the PCF provides the multicast service related policy in PCC rules to the SMF. Then the SMF decides to initiate a multicast MBS session join/establishment procedure based on the multicast service related policy. + +The following procedures is on top of the procedures specified in clause 7.2.1.3 in TS 23.247 [4]. + +### 6.11.3 Procedures + +#### 6.11.3.1 on-demand multicast MBS session management + +![Sequence diagram for On-demand multicast MBS session establishment. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UDR, NRF, PCF, MB-SMF, MB-UPF, and AF. The process is divided into four main steps: 1. MBS Session Creation (spanning from UE to AF), 2. AF decides multicast related service parameters and provides to the PCF (AF to PCF), 3. PCF initiated SM policy association modification for multicast (PCF to SMF), and 4. Steps 2-19 in clause 7.2.1.3 of TS 23.247 (spanning from SMF to MB-UPF).](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +Sequence diagram for On-demand multicast MBS session establishment. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UDR, NRF, PCF, MB-SMF, MB-UPF, and AF. The process is divided into four main steps: 1. MBS Session Creation (spanning from UE to AF), 2. AF decides multicast related service parameters and provides to the PCF (AF to PCF), 3. PCF initiated SM policy association modification for multicast (PCF to SMF), and 4. Steps 2-19 in clause 7.2.1.3 of TS 23.247 (spanning from SMF to MB-UPF). + +**Figure 6.11.3.1-1: On-demand multicast MBS session establishment** + +The key steps of the procedure for this solution are as follows: + +1. MBS Session Creation with PCC procedure is performed as specified in clause 7.1.1.3 of TS 23.247 [4], where the AF may perform a Service Announcement towards the UEs. +2. The AF decides to set or update multicast related service parameters, including the multicast indication, for specific services/applications. The AF may, based on local configuration or triggered by e.g. event report from the NEF, subscribe to or requests network analytics information (e.g. Observed Service Experience analytics) from the NWDAF as specified in TS 23.288 [10], and decide to update the multicast related service parameters based on the analytics information. + +The AF provides updated service parameters, which include the multicast indication and a MBS Session ID for the multicast MBS session to be established, to the PCF via the NEF by using Nnef\_AFsessionWithQoS\_Update request (as defined in clause 4.15.6.6a of TS 23.502 [3]). The "AF session with required QoS update" procedure continues as defined in TS 23.502 [3] and the PCF receives the updated service parameters. + +NOTE 1: Those procedures are meant for individual UE joining the MBS session, and are not meant for an MBS session. If AF may send multiple requests in case multiple UEs are involved. Legacy procedures including PCF selection will be reused. + +NOTE 2: It is assumed AF can have the private IP address by e.g. application level interaction, public safety AF and so on. + +- 3a. The PCF initiates SM Policy Association Modification procedure as defined in clause 4.16.5.2 of TS 23.502 [3] to notify the SMF, with the multicast MBS session ID. +- 4a. Steps 2-19 specified in clause 7.2.1.3 of TS 23.247 [4] are reused to complete on-demand multicast MBS session establishment, for the UEs subscribed to the multicast MBS Session and with an associated PDU Session established for the multicast MBS Session, and Namf\_Communication\_N1N2MessageTransfer is used in step 5 instead of Nsmf\_PDUSession\_UpdateSMContext response message. The UE is informed of successfully joining the multicast MBS session upon receiving the PDU Session Modification Command which contains the MBS Session ID. + +### 6.11.4 Impacts on services, entities and interfaces. + +AF: + +- The AF needs to support triggering the on-demand multicast MBS Session establishment, based on e.g. the network analytics information provided by the NWDAF. + +PCF: + +- The PCF is enhanced to provide to the SMF(s) the multicast service related policy, i.e. MBS session ID that the AF request UE to join, for triggering the SMF(s) to complete the on-demand multicast MBS session establishment. + +## 6.12 Solution #12: Group Message Delivery + +### 6.12.1 Introduction + +This solution addresses the following aspect in Key Issue #4: Whether and how to enhance the MBS functionality to provide a similar group message delivery as available in eMBMS. + +### 6.12.2 Functional description + +This solution describes a NEF-based group message delivery via MBS method, which is comparable to the SCEF-based group message delivery via MBMS. + +This solution utilizes the Object Delivery Method in MBSTF specified in TS 26.502 [11] for the group message delivery via MBS. The Object Delivery Method in MBSTF is equivalent to the File Delivery Method in eMBMS. The Object Delivery Method can benefit from Application Layer Forward Error Correction (AL-FEC) to achieve the reliable delivery, which is essential for group message delivery. + +The NEF is responsible to handle Group Message Delivery request from the AF. It transforms the group message into a file and determine the meta data information of the file. In control plane, it performs Application Service Provisioning including MBS User Service creation and MBS User Data Ingest Session creation, which triggers the MBS session creation and MBS session start for broadcast towards 5GC and NR. In user plane, it is responsible for ingesting the file to the MBSTF, so that MBSTF can deliver the file to UE via 5GC shared traffic delivery and NR broadcast. + +### 6.12.3 Procedures + +#### 6.12.3.1 General + +NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. + +### 6.12.3.2 Group Message Delivery via MBS Broadcast + +![Sequence diagram for Group Message Delivery via MBS Broadcast. Lifelines: UE, RAN, 5GC, MBSF, MBSTF, NEF, AF. The process involves a request from AF to NEF, authorization, transformation of payload, service provisioning, session creation, session start, user service announcement, response to AF, data ingestion, FEC encoding, broadcast delivery to UE, file retrieval by UE, and final delivery to AF.](bccc028d0e75bc30c41528056f581545_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant MBSTF + participant MBSF + participant 5GC + participant RAN + participant UE + + Note right of NEF: 1. Group Message Req + AF->>NEF: 1. Group Message Req + Note right of NEF: 2. Authorization + NEF->>AF: 2. Authorization + Note right of NEF: 3. Transforms the group message payload into a file, and determine the user service information + Note right of NEF: 4. Application Service Provisioning + NEF-->>MBSTF: 4. Application Service Provisioning + Note right of MBSTF: 5. MBS Session Creation + MBSTF-->>5GC: 5. MBS Session Creation + Note right of 5GC: 6. Distribution Session Provisioning + 5GC-->>MBSTF: 6. Distribution Session Provisioning + Note right of MBSTF: 7. MBS Session Start for broadcast + MBSTF-->>5GC: 7. MBS Session Start for broadcast + Note right of 5GC: 8. MBS User Service Announcement + 5GC-->>RAN: 8. MBS User Service Announcement + RAN-->>UE: 8. MBS User Service Announcement + Note right of NEF: 9. Group Message Resp + NEF->>AF: 9. Group Message Resp + Note right of NEF: 10. Application Service Announcement + NEF-->>5GC: 10. Application Service Announcement + 5GC-->>RAN: 10. Application Service Announcement + RAN-->>UE: 10. Application Service Announcement + Note right of NEF: 11. User Data Ingestion + NEF->>MBSTF: 11. User Data Ingestion + Note right of MBSTF: 12. FEC Encoding and packetization + MBSTF->>5GC: 12. FEC Encoding and packetization + Note right of 5GC: 13. packet delivery over MBS broadcast + 5GC-->>RAN: 13. packet delivery over MBS broadcast + RAN-->>UE: 13. packet delivery over MBS broadcast + Note right of UE: 14. Get group message from file + UE->>5GC: 14. Get group message from file + Note right of NEF: 15. Group Message Delivery + NEF->>AF: 15. Group Message Delivery + +``` + +Sequence diagram for Group Message Delivery via MBS Broadcast. Lifelines: UE, RAN, 5GC, MBSF, MBSTF, NEF, AF. The process involves a request from AF to NEF, authorization, transformation of payload, service provisioning, session creation, session start, user service announcement, response to AF, data ingestion, FEC encoding, broadcast delivery to UE, file retrieval by UE, and final delivery to AF. + +**Figure 6.12.3.2-1: Group Message Delivery via MBS Broadcast.** + +NOTE 1: In the procedures referred to the TS 26.502 [11], the NEF is the MBS Application Provider. + +1. The AF sends Group Message Request to the NEF, containing the Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time, External Group Identifier. +2. The NEF checks authorization of AF. If geographical area information or civic address information was provided by the AF as MBS service area, the NEF translates the MBS service area to Cell ID list or TAI list. + +NOTE 2: The NEF is mandated for group message delivery. + +3. The NEF transforms the group message payload into a file, and determines the meta data information of the file (e.g. File URL, etc.). The NEF assigns a TLTRI that identifies this Group Message Request. + +If Application Service Provisioning hasn't been performed, step 4 to step 8 needs to be executed. Otherwise, they can be skipped. + +4. The NEF performs Application Service Provisioning towards the MBSF as specified in step 1 in clause 5.2 of TS 26.502 [11], which including invoking Nmbsf\_MBSUserService\_Create and Nmbsf\_MBSUserDataIngestSession\_Create on the MBSF. + +- The Target service area is set to MBS Service Area. +- The Distribution method is set to Object Distribution Method which is used for file delivery. + +- The Distribution Operating Mode is set to File or Carousel depends on the decision of the NEF. + - The Object acquisition method is set to Push or Pull depends on the decision of the NEF. +5. The MBSF performs MBS Session Creation as specified in clause 7.1.1.2 or clause 7.1.1.3 of TS 23.247 [4]. + 6. The MBSF performs Distribution Session Provisioning as specified in step 2 in clause 5.2 of TS 26.502 [11]. The MBSF invokes Nmbstf\_MBSDistributionSession\_Create on the MBSTF, passing the parameters of the MBS Distribution Session received in step 4 to the MBSTF. + 7. The MB-SMF initiates the MBS Session Start for Broadcast procedure as specified in step 2 to step 9 in clause 7.3.1 of TS 23.247 [4]. + 8. If the MBSF performs the service announcement, it initiates the MBS User Service Announcement as specified in step 3 in clause 5.2 of TS 26.502 [11]. The application may receive the appropriate information through the MBS-6 API from the MBS Client (see TS 26.502 [11]). The NEF may receive the service announcement information via Nmbstf\_MBSUserDataIngestSession\_StatusNotify callback service operation (see TS 26.502 [11]). + 9. The NEF sends Group Message Response to the AF, containing TLTRI, Acceptance Status, Cause. The Acceptance Status indicates whether the group message request is accepted or not. If not, the Cause indicates the appropriate failure reason. If the AF performs the service announcement, the service announcement information containing the file meta data can be optionally included in the Group Message Response. + 10. If the AF needs to perform the Service Announcement, the AF sends the application service announcement to the UE as specified in step 4 in clause 5.2 of TS 26.502 [11]. + 11. The NEF performs the User Data Ingestion towards the MBSTF as specified in step 5 in clause 5.2 of TS 26.502 [11]. The NEF may push the file to the MBSTF or let MBSTF pull the file from the NEF. + 12. The MBSTF performs packetization and optionally FEC encoding as specified in clause 4.3.3.2 of TS 26.502 [11]. + 13. The MBSTF delivers the packets to the MB-UPF to NG-RAN, and NG-RAN broadcast to the UE as specified in step 13 to step 15 in clause 7.3.1 of TS 23.247 [4]. + 14. Based on the service announcement information received in step 8 or step 10, the UE receives the packets, is required performs FEC decoding to restore the file, and gets the group message from the file, using the MBS Client as specified in clause 4.3.5 of TS 26.502 [11]. The MBS Client can expose the file towards the application in the UE using the MBS-7 API (see TS 26.502 [11]). + 15. The NEF sends a Group Message Delivery to the AF, containing TLTRI, Delivery Status. The Delivery Status indicates whether delivery of Group Message Payload corresponding is successful or not. The delivery status information is received by the NEF via Nmbstf\_MBSUserDataIngestSession\_StatusNotify callback service operation (see TS 26.502 [11]). + +### 6.12.3.3 Modification of previously submitted Group message + +![Sequence diagram for Modify or Cancel Group Message Delivery via MBS Broadcast. Lifelines: UE, RAN, 5GC, MBSF, MBSTF, NEF, AF. The diagram shows three request actions: 'Modify' with payload update, 'Modify' with service area update, and 'Cancel'. The 'Modify' with payload update path involves file transformation and ingestion. The 'Modify' with service area update path involves an MBS session update procedure. The 'Cancel' path involves session destruction and an MBS session deletion procedure.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant MBSTF + participant MBSF + participant 5GC + participant RAN + participant UE + + Note left of UE: Request Action = "Modify", Group Message Payload update + AF->>NEF: 1. Modify Group Message Req + NEF->>NEF: 2. Authorization + Note right of NEF: Request Action = "Modify", MBS Service Area update + Note right of NEF: Request Action = "Cancel" + Note right of NEF: 3. Transforms the group message payload into a file + NEF->>MBSF: 4. Update MBSUserDataIngestSession (update file) + MBSF->>MBSTF: 5. Update MBSDistributionSession (update file) + Note right of MBSTF: 6. User Data Ingestion + Note right of MBSTF: 7. Update MBSUserService (update service area) + Note right of 5GC: 8. MBS Session Update procedure (updated MBS service area) + Note right of MBSTF: 9. Update MBSUserDataIngestSession (cancel file) + Note right of MBSTF: 10. Update MBSDistributionSession (cancel file) + Note right of MBSTF: 11. HTTP DELETE + Note right of MBSTF: 12. Destroy MBSUserDataIngestSession + Note right of MBSTF: 13. Destroy MBSDistributionSession + Note right of 5GC: 14. MBS Session Deletion procedure + NEF->>AF: 15. Modify Group Message Resp + +``` + +Sequence diagram for Modify or Cancel Group Message Delivery via MBS Broadcast. Lifelines: UE, RAN, 5GC, MBSF, MBSTF, NEF, AF. The diagram shows three request actions: 'Modify' with payload update, 'Modify' with service area update, and 'Cancel'. The 'Modify' with payload update path involves file transformation and ingestion. The 'Modify' with service area update path involves an MBS session update procedure. The 'Cancel' path involves session destruction and an MBS session deletion procedure. + +**Figure 6.12.3.3-1: Modify or Cancel Group Message Delivery via MBS Broadcast** + +NOTE: In the procedures referred to the TS 26.502 [11], the NEF is the MBS Application Provider. + +- The AF sends Modify Group Message Request to the NEF, containing the TLTRI, Request Action, Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time, External Group Identifier. The NEF identifies the associated MBS Service using the external Group Identifier. Requested Action is either set to "Modify", or "Cancel". "Modify" indicates the request is to modify the group message delivery transaction. "Cancel" indicates the request is to cancel the group message delivery transaction. The TLTRI indicates the transaction to be modified or cancelled. +- The NEF checks authorization of AF. If geographical area information or civic address information was provided by the AF as MBS service area, the NEF translates the MBS service area to Cell ID list or TAI list. + +If Requested Action is "Modify" and Group Message Payload is updated, step 3 to step 6 are executed: + +- The NEF transforms the group message payload into a file, and use the determined file meta data (e.g. File URL, etc.) in clause 6.12.3.2. +- If Object acquisition method is set to Push, step 4 to step 5 can be skipped. If Object acquisition method is set to Pull, the NEF updates MBS User Data Ingest Session on the MBSF as specified in clause 7.2 of TS 26.502 [11]. The update service operation needs to indicate an update of the file containing the updated group message. +- The MBSF updates MBS Distribution Session on the MBSTF as specified in clause 7.3 of TS 26.502 [11]. The update service operation needs to indicate an update of the file containing the updated group message. + +6. If Object acquisition method is set to Push, the NEF pushes the update file to the MBSTF. If Object acquisition method is set to Pull, the MBSTF pull the updated file from the NEF. And the MBSTF delivers the updated file towards the MB-UPF in 5GC as specified in clause 4.3.3.2 of TS 26.502 [11]. + +If Requested Action is "Modify" and MBS service area is updated, step 7 to step 8 are executed: + +7. The NEF updates MBS User Service on the MBSF as specified in clause 7.2 of TS 26.502 [11]. The update service operation indicates MBS service area update. +8. The MBSF performs MBS Session Update as specified in clause 7.1.1.6 or clause 7.1.1.7 of TS 23.247 [4] to update MBS service area, which triggers MBS Session Update for Broadcast as specified in clause 7.3.3 of TS 23.247 [4]. + +If Requested Action is "Cancel", step 9 to step 14 are executed: step 9 to step 11 are needed when the group message delivery has started and MBSF needs to inform the MBS Client about the cancel of the file delivery. Otherwise, they can be skipped. + +9. The NEF updates MBS User Data Ingest Session on the MBSF as specified in clause 7.2 of TS 26.502 [11]. The update service operation needs to indicate the cancel of the file delivery. The MBSF informs the MBS Client about the cancel of the file delivery if needed. +10. If Object acquisition method is set to Pull, the MBSF updates MBS Distribution Session on the MBSTF as specified in clause 7.3 of TS 26.502 [11]. The update service operation indicates the cancel of the file delivery. The MBSTF stops the file delivery. +11. If Object acquisition method is set to Push, the NEF may send HTTP DELETE to the MBSTF to cancel the file delivery. The MBSTF stops the file delivery. +12. The NEF destroys MBS User Data Ingest Session on the MBSF as specified in clause 7.2 of TS 26.502 [11]. +13. The MBSF destroys MBS Distribution Session on the MBSTF as specified in clause 7.3 of TS 26.502 [11]. +14. The MBSF performs MBS Session Deletion as specified in clause 7.1.1.4 or clause 7.1.1.5 of TS 23.247 [4], which triggers MBS Session Release for Broadcast as specified in clause 7.3.2 of TS 23.247 [4]. +15. The NEF sends Modify Group Message Response to the AF, containing Acceptance Status, Cause. The Acceptance Status indicates whether the group message request is accepted or not. If not, the Cause indicates the appropriate failure reason. + +After the modified group message is delivered, the NEF sends a Group Message Delivery to the AF as described in step 15 in clause 6.12.3.2. + +## 6.12.4 Impacts on services, entities and interfaces + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] and clause 6.2 of TS 23.501 [2] are reused exception for the following additions: + +NEF: + +- Support group message delivery and modify group message interfaces towards AF, and optionally include the service announcement information in the group message delivery response to the AF. +- Transform the group message into a file and determine the meta data information of the file. +- Create MBS User Service and MBS User Data Ingest Session to the MBSF in group message delivery. +- Update MBS User Service to the MBSF for MBS service area update. Update MBS User Data Ingest Session to the MBSF when the group message is updated. +- Optionally update MBS User Data Ingest Session to the MBSF to cancel the file or DELETE the file to the MBSTF, when the group message delivery has started and MBSF needs to inform the MBS Client about the cancel of the file delivery. Destroy MBS User Data Ingest Session to the MBSF. +- Ingest file to the MBSTF. + +## 6.13 Solution #13: Group message delivery for broadcast + +### 6.13.1 Introduction + +This solution addresses Key Issue #4. + +### 6.13.2 Functional description + +It is assumed to reuse the current architecture and TMGI definition in Rel-17 MBS work (see TS 23.247 [4]). In other words, MB-SMF is used to handle MBS session-level management while SMF performs per-UE MBS session management, e.g. authorization, multicast session information provisioning, managing 5GC Individual MBS traffic delivery. + +For group message delivery, it mainly targeted for the Machine type communication services. The group message delivery has limited applicability and does not support all the scenarios, e.g. UEs not supporting MBS, UEs located in areas where MBS is not deployed. + +In TS 23.682 [6], features of group message delivery are highlighted as follows: + +- *"The specific procedure handling for group message delivery using MBMS is described in clause 5.5.1. The group message delivery using MBMS has limited applicability and does not support all the scenarios, e.g. UEs not supporting MBMS, UEs located in areas where MBMS is not deployed. The SCS/AS may recall or replace a previously submitted MBMS message; this is described in clause 5.5.2."* + +This solution proposes how to use MBS for group message delivery for the case when the UEs locate in the area where MBS is not deployed. This architecture can be re-used for general group message delivery purposes (not limited to MTC devices). + +Compared with Rel-17 defined mechanism, the case that UEs located in areas where MBS is not deployed needs to be considered for broadcast. + +NOTE: This solution assumes that the AF is aware of the exact location of UEs. + +### 6.13.3 Procedures + +#### 6.13.3.1 General + +NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. + +## 6.13.3.2 Broadcast Session Establishment + +![Sequence diagram for Broadcast Session Establishment for Group message delivery. Lifelines: UE, NG-RAN, MB-UPF, MBSTF, MB-SMF, MBSF, NEF, AF. The diagram shows two modes: Transport Only Mode and Service Mode. It includes steps for TMGI allocation, service announcement, group message delivery request, authorization, and session creation.](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant MB-UPF + participant MBSTF + participant MB-SMF + participant MBSF + participant NEF + participant AF + + Note right of AF: 0a. TMGI allocation procedure (see step 1-6 of TS 23.247 [4]) + AF-->>UE: 0b. Service announcement + Note right of AF: 1. Group message delivery request (TMGI, requested area) + AF->>NEF: 1. Group message delivery request (TMGI, requested area) + Note right of NEF: 2. Authorization + NEF->>NEF: 2. Authorization + Note right of NEF: 3. NEF figures out the area does not support MBS + NEF->>AF: 3. NEF figures out the area does not support MBS + + Note left of MB-SMF: Transport Only Mode + Note right of MB-SMF: 4. Nmbsmf_MBSSession_Create Request (TMGI, supported area) + MB-SMF->>NEF: 4. Nmbsmf_MBSSession_Create Request (TMGI, supported area) + Note left of NG-RAN: 5. Step 13-17 of Clause 7.1.1.2 in TS 23.247 [4] when PCC is not used, or Step 10-19, 21-30 of Clause 7.1.1.3 of TS 23.247 [4] when PCC is used. + NEF->>MB-SMF: 6. Nmbsmf_MBSSession_Create Response () + Note left of MB-SMF: Service Mode + Note right of MBSF: 7a. Nmbsmf_TMGI allocation + Note right of MBSF: 7b. Nmbsmf_MBSUserDataIngestSession_Create Request () + Note right of MBSF: 7a. Nmbsmf_MBSUserService_Create Request ([TMGI], supported area) + MBSF->>MBSTF: 7a. Nmbsmf_TMGI allocation + MBSF->>MB-SMF: 7b. Nmbsmf_MBSUserDataIngestSession_Create Request () + MBSF->>AF: 7a. Nmbsmf_MBSUserService_Create Request ([TMGI], supported area) + Note left of NG-RAN: 8. Same as step 5 + MB-SMF->>MBSF: 8. Nmbsmf_MBSSession_Create Request ([TMGI], supported area) + Note left of NG-RAN: 9. Same as step 5 + MB-SMF->>NEF: 10. Nmbsmf_MBSSession_Create Response () + Note right of MBSTF: 11. Nmbstf_MBSDistributionSession_Create + MBSTF->>MBSF: 11. Nmbstf_MBSDistributionSession_Create + Note right of MBSF: 12a. Nmbsmf_MBSUserService_Create Response + Note right of MBSF: 12b. Nmbsmf_MBSUserDataIngestSession_Create Response + MBSF->>AF: 12a. Nmbsmf_MBSUserService_Create Response + MBSF->>AF: 12b. Nmbsmf_MBSUserDataIngestSession_Create Response + Note right of AF: 13. Group message delivery response (TMGI, area not supporting MBS) + AF-->>UE: 13. Group message delivery response (TMGI, area not supporting MBS) + Note left of UE: 14. Service announcement + AF-->>UE: 14. Service announcement + Note left of UE: 15. AF uses unicast for the UEs not appear in the supported area. + Note left of UE: 16. Group message delivery + AF->>MB-UPF: 16. Group message delivery + MB-UPF->>NG-RAN: 16. Group message delivery + NG-RAN->>UE: 16. Group message delivery + +``` + +Sequence diagram for Broadcast Session Establishment for Group message delivery. Lifelines: UE, NG-RAN, MB-UPF, MBSTF, MB-SMF, MBSF, NEF, AF. The diagram shows two modes: Transport Only Mode and Service Mode. It includes steps for TMGI allocation, service announcement, group message delivery request, authorization, and session creation. + +Figure 6.13.3.2-1: Broadcast Session Establishment for Group message delivery + +The procedure is based on clauses 7.3.1 and 7.1.1.1/7.1.1.2 of TS 23.247 [4], and clause 5 of TS 26.502 [11], the delta parts is highlighted at following: + +0. AF optionally requests the 5GC to allocate the TMGI, details see steps 1-6 of TS 23.247 [4]. AF may send service announcement to the UEs. +1. The AF later further request to establish the MBS session, with including the requested MBS service area in Group message delivery request sent to NEF. If the TMGI is available (step 0 is executed), AF also includes the TMGI in the message. When included, Group Message Payload indicates the payload the AF intends to deliver. +2. NEF authorizes the request sent by AF, and the NEF may map the MBS service area to TA list or a list of cell ID. +3. NEF figures out the area which does not support MBS. + +If Service Mode is used, or MBSF is not involved, step 4-6 are skipped: + +4. NEF invokes Nmbsmf\_MBSSession\_Create Request, and uses the area supporting MBS as the MBS service area in the message. +5. MB-SMF continues the MBS Session Creation procedure as defined in TS 23.247 [4]. +6. MB-SMF sends the response message to NEF. If MBSF is involved, the message will go through MBSF. + +NOTE: For Transport Only Mode, it is assumed 5GC will not processing the ingested data therefore the AF is assumed to provide the functionalities e.g. reliability if needed. + +If Transport Only Mode is used, step 7-12 are skipped: + +7. If the Group Message Payload is included, and if Object Distribution Method is used, the NEF transforms the group message payload into a file. + +NEF invokes Nmbsf\_MBSUserService\_Create Request, and uses the area supporting MBS as the MBS service area in the message. NEF also sends Nmbsf\_MBSUserDataIngestSession\_Create Request message to the MBSF in which the MBS service area is the area supporting MBS. If Object Distribution Method is used, the "PUSH" mode may be used if the NEF is not assumed to support buffering the DL data. + +8. MBSF invokes Nmbsmf\_MBSSession\_Create Request. +9. Same as step 5. +10. MB-SMF sends Nmbsmf\_MBSSession\_Create Response message to MBSF. +11. MBS Distribution Session is created as defined in TS 26.502 [11]. +12. MBSF responses the messages from NEF in step 7. +13. NEF responses AF with Group message delivery response. NEF includes the areas in the requested MBS service area that do not support MBS. NEF may also send the address to the AF. +14. AF may send service announcement. +15. For the UEs locating out of the supported area, AF uses unicast for sending the data to the UE. +16. If Group Message Payload was included in step 1, then the NEF delivers to MBSTF/MB-UPF the Group Message Payload(s). If Group Message Payload was not included in step 1, the AF transfers the content to be delivered to the group to the NEF using the address received at step 13. + +If Object Distribution Method is used, the NEF transforms the subsequent message into a file and sends the file to MBSTF. If Object Distribution Method is not used, the NEF will not process the message and directly delivers the group message payload to MB-UPF. As mentioned in the NOTE of step 6, AF is assumed to provide the reliability if needed. + +### 6.13.3.3 Modification of previously submitted group message + +0. The pre-condition for this flow is the successful completion of step 13 from clause 6.13.3.2. +1. AF may send service announcement to the UEs, to enable UE to retrieve the related service information, e.g. TMGI, start time, etc. +2. The AF requests to modify the previously accepted Group Message Delivery Request. The AF sends the Modify Group Message Request to the NEF. MBS service area might be included in the message. When included, Group Message Payload indicates the payload the AF intends to deliver. The Requested Action is either set to "Modify", or "Cancel". "Modify" indicates the request is to modify the transaction. "Cancel" indicates the request is to cancel the transaction. +3. NEF authorizes the request sent by AF. The NEF may map the MBS service area to TA list or a list of cell ID. + +If Requested Action was set to "Cancel": + +- 4a. If Transport Only Mode is used: NEF invokes the MBS session deletion procedures defined in clause 7.1.1.4 or 7.1.1.5 of TS 23.247 [4]. + +- 4b. If Service Mode is used: NEF invokes Nmbstf\_MBSUserDataIngestSession\_Destroy, and Nmbstf\_MBSUserService\_Destroy service operation to destroy the data ingest session and User service, respectively. MBSF invokes Nmbstf\_MBSDistributionSession\_Destroy service operation to destroy the distribution session. + +If Requested Action was set to "Modify": + +- 5a. If Transport Only Mode is used: NEF invokes the MBS session update procedures defined in clause 7.1.1.6 or 7.1.1.7 of TS 23.247 [4]. +- 5b. If Service Mode is used: NEF invokes Nmbstf\_MBSUserService\_Update service operation to update the user service, if the AF requests to update the MBS service area, or QoS. If the Group Message Payload is included, and if Object Distribution Method is used, the NEF transforms the group message payload into a file. NEF may invoke Nmbstf\_MBSDistributionSession\_Update service operation, if the AF requests to update the QoS or file. + +The NEF may further invoke MBS session update procedures defined in clause 7.1.1.6 or 7.1.1.7 of TS 23.247 [4]. + +6. NEF responses AF with Group message delivery response. + +### 6.13.4 Impacts on services, entities and interfaces + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] is reused exception for the following additions: + +#### NEF: + +- Support differentiating the area with supporting MBS and non-supporting MBS. +- Support responding AF with the information that not supporting MBS. +- User plane handling of the group communication message. + +## 6.14 Solution #14: MBS coexistence with power saving mechanisms of 5GS + +### 6.14.1 Introduction + +This is a solution for Key Issue #5. + +Clause 4.5.18 of TS 23.682 [6] defines the mechanisms for co-existence between eMBMS and the power saving mechanisms that exist in EPS. The basic premise is that the time intervals the UE stays awake to receive MBMS user service or to discover if there is any MBMS user service scheduled for delivery, should not necessarily be the same as the reachable intervals negotiated for extended idle mode DRX or PSM. + +### 6.14.2 Functional description + +Same as in EPS, for 5GS also this solution proposes that the time intervals the UE needs to be awake for MBS service may not coincide with the wake up time windows mandated by eDRX (PTW) and/or MICO with active time (periodic Registration Update + active time) configuration. + +For those intervals the UE needs to be awake for MBS user service, the following cases can be identified: + +#### Scenario 1: + +When the UE needs to be awake due to MBS coinciding with the UE already being in connected mode due to other reasons, the UE follows normal connected mode procedures. + +#### Scenario 2: + +When the UE needs to be awake due to MBS coinciding with the UE already being in idle mode and reachable (e.g. in active time for MICO or PTW for eDRX) the UE follows normal idle mode procedures. + +#### Scenario 3: + +When the UE needs to be awake due to MBS coinciding with the UE being in idle mode and in deep sleep, i.e. unreachable for paging to the network, the UE leaves the deep sleep for MBS service only: + +- If the MBS service does not require the UE to transition to connected mode, i.e. the UE can receive the specific MBS service in idle mode using MBS broadcast, then the UE does not update the AMF to become reachable for paging. In other words, the UE would still be considered unreachable for paging in the core network. This minimizes the signalling between the UE and the network. +- If the MBS service requires the UE to transition to connected mode (e.g. MBS service that requires MBS multicast mode) then the UE performs regular procedures for CM connected mode. This would therefore make the UE become reachable. + +#### Scenario 4: + +When the UE is in the middle of an MBS data transfer, and the UE is scheduled to move to deep sleep due to power saving, e.g. end of PTW for eDRX, expiration of active time for MICO or the UE transitioning from CM-CONNECTED to CM-IDLE in the case of MICO with no active time, then the UE does not go to deep sleep during the remainder of the MBS data transfer: + +- If at the end of MBS data transfer, the UE knows there is another MBS data transfer scheduled soon, in that case depending of the time between MBS data transfers, the UE may not go to sleep between MBS data transfers. +- The UE may in fact not go to deep sleep while in an MBS broadcast session. + +### 6.14.3 Procedures + +With extrapolation of the procedures defined in TS 23.682 [6] to 5GS power saving mechanisms and MBS the following is defined: + +1. When the UE needs to be awake due to MBS coinciding with the UE already being in connected mode due to other reasons, the UE follows normal connected mode procedures. +2. When the UE needs to be awake due to MBS coinciding with the UE already being in idle mode and reachable (e.g. in active time in MICO or PTW for eDRX) the UE follows normal idle mode procedure. +3. When the UE needs to be awake due to MBS coinciding with the UE being in idle mode and in deep sleep, i.e. unreachable for paging to the network, the UE leaves the deep sleep state only to perform procedures related to MBS service. + - If the MBS service does not require the UE to transition to connected mode, i.e. the UE receives MBS service in broadcast mode and therefore can be in idle mode, then the UE does not update the AMF to become reachable for paging. The UE would therefore still be considered unreachable for paging in the AMF. This minimizes the signalling between the UE and the network. + - If the MBS service requires the UE to transition to connected mode (e.g. reception in MBS multicast mode) then the UE performs regular procedures for MBS multicast mode defined in TS 23.247 [4]. This would therefore make the UE become reachable in the network for other unicast services. +4. When the UE is in the middle of an MBS data transfer, and the UE is scheduled to move to deep sleep due to power saving, e.g. end of PTW for extended idle mode DRX, expiration of active time for MICO or the UE transitioning from CM-CONNECTED to CM-IDLE in the case of MICO with no active time, then the UE does not go to deep sleep during the remainder of the current MBS data transfer. + +NOTE 1: If the NG-RAN node knows the UE is within a certain MBS session, the NG-RAN node will not configure the eDRX $\geq 10.24\text{s}$ for the UE upon transiting the UE into CM-CONNECTED with RRC-Inactive state. The UE shall disable the MICO mode, after it successfully joins the MBS session. + +NOTE 2: If at the end of the current MBMS data transfer, the UE knows there is another MBMS data transfer scheduled soon, in that case depending of the time between MBS data transfers, the UE can decide to go to sleep between MBS data transfers. + +There are two possible ways the UE can be notified of an upcoming MBS broadcast session start: + +1. If MBS User Services defined in TS 26.502 [11] is used, the UE needs to receive MBS service announcement while awake (i.e. while in connected mode, or while idle mode during PTW for extended idle mode DRX, or active time for MICO). The UE wakes up if not already awake for MBS service reception based on the schedule received in the service announcement. For this option, the MBS service announcement may be provided via MBS broadcast service announcement or via any of the possible unicast service announcement delivery mechanisms. In case the MBS service announcement is provided in application layer, similar mechanisms need to be provided. + +NOTE 3: In order to allow all UEs using power saving function to receive the service announcement in time to be able to receive the MBS broadcast data delivery, the application server needs to be aware of the maximum unreachable period of the UEs. + +2. The UE may be configured by the application server with specific times to perform MBS procedures, and wakes up from deep-sleep if needed at those times. The UE may also receive MBS service announcements and/or MBMS broadcast delivery at those times (if needed). + +NOTE 4: The configuration (e.g. TMGI, start time) is out of scope of 3GPP and assumed to be performed between application server and UE at application layer. The application server needs to initiate MBS bearer service procedures during those time intervals. + +## 6.14.4 Impacts on services, entities and interfaces. + +In UE: + +- Handle potential wake up out of deep sleep due to power saving (e.g. eDRX, MICO with active time) for MBMS user service session/data transfer when it knows a scheduled broadcast it is interested in receiving. +- Remain awake during reception of MBMS data transfer, even when power saving function would trigger moving to deep sleep (e.g. end of PTW in eDRX, end of active time in MICO). +- (The UE can already be configured by application server with maximum allowed delay tolerance, in this case it would be for MBMS service, which can translate to UE requesting specific eDRX cycle or periodic TAU). +- Configuration for periodic wake ups for MBMS and UE behaviour when waking up only for MBMS service. + +In NW: + +- No standards impacts. +- Service announcement needs to be started at least an eDRX cycle or periodic Registration Update length earlier than the actual data broadcast. +- If UE belongs to some certain MBS sessions, RAN will not configure the long eDRX parameter for the UE upon transiting the UE into CM-CONNECTED with RRC-Inactive state. + +In AS: + +- The application server needs to trigger start for service announcement at least an eDRX cycle or periodic Registration Update length earlier than the actual data broadcast. + +## 6.15 Solution #15: Solution for coexistence of MBS delivery and power saving mechanisms + +### 6.15.1 Functional description + +This solution addresses Key Issue #5 (Coexistence with existing power saving mechanisms for capability-limited devices). + +Capability-limited devices may use power-saving mechanisms to extend their battery live. Existing power saving mechanisms include MICO (Mobile Initiated Connection Only) mode, DRX (Discontinuous Reception), eDRX (Extended Discontinuous Reception). + +When an MBS Session data delivery is required (e.g. for software/firmware update) is required, service announcement is needed. The service announcement using MBS Session data delivery may not be efficient from the network + +perspective since the capability-limited devices are not expected to be awake throughout the day, but only infrequently. Furthermore, the capability-limited devices do not wake-up at the same time and they are not reachable while being in power saving mode. + +This solution proposes to inform the capability-limited devices about a newly scheduled MBS Session data delivery during their wake-up periods when the devices are reachable. When MBS Session data delivery is required, the MBS Session data delivery time can be scheduled as follows: + +- When a new MBS delivery schedule for capability-limited devices become available, the network will send a service announcement to inform the UEs about the new schedule when they are reachable. +- The time interval from when MBS Session data delivery schedule is announced to when the first MBS Session data delivery as announced by that schedule will start can be shorter than the minimum power saving period of all capability-limited devices. +- The network may schedule multiple MBS deliveries. If at the end of the current MBS Session data delivery, the UE knows there is another MBS Session data delivery scheduled soon, in that case depending on the time between MBS Session data deliveries, the UE can decide to go to power saving between MBS Session data deliveries. + +**Editor's note:** Regarding the coexistence of multicast MBS Session data delivery with capability-limited devices, the dependency with KI#1 is FFS. + +## 6.15.2 Procedures + +Existing procedure for 5MBS is used. + +**Editor's note:** SA WG4 collaboration is required. + +## 6.15.3 Impacts Analysis + +UE: The UE needs to wake up according to the time scheduled for MBS delivery received in service announcement. + +# 6.16 Solution #16: Public Safety services offered over both Broadcast and Multicast transport + +## 6.16.1 Description + +### 6.16.1.1 General + +This is a solution for Key Issue #6. + +5G Broadcast and 5G Multicast services cater and are optimal in different scenarios: + +- The more sparse the UEs receiving a same content are, the larger the service area, the more attractive using 5G Multicast is. +- The more concentrated in an area the UEs receiving a same content are, the more attractive using 5G Broadcast may become. + +This solution consists on identifying areas of concentrated number of UEs for which 5G Broadcast services would be the optimal transport, areas of sparse UEs receiving the same public safety service for which multicast transport would be useful. Configuring Broadcast service and Multicast service for the same public safety service, and allow the UE to decide whether to receive the public safety MBS content via broadcast service if available, or multicast session. + +The solution relies on GCS AS (MCX AS) activates MBS broadcast session in broadcast service areas where MBS capable UEs are or are expected to be located. For that, the GCS AS (MCX AS) shall use the MBS SAI(s) and/or cell id(s) information to construct the MBS broadcast area parameter. LMS will configure the LMC as defined in TS 23.280 [7] for the parameters to report and determine the "granularity" and "frequency" of location reports. + +NOTE This solution requires that UEs provide accurate location reports to the GCS AS to enable the GCS AS to determine where UEs are concentrated. Those location reports require that UEs are in connected state and may lead to capacity bottlenecks. It is a trade-off between accuracy and frequency of the location reports and how fast switching between broadcast and multicast can be achieved. + +### 6.16.1.2 Functional description + +NOTE 1: The use of GCS AS in reference to this solution refers to stage-2 procedures defined in TS 23.468 [12] and are used for public safety IMS procedures defined in SA6 specifications for GC-1/MCPTT-1 interface. The interface between GCS AS and 5GC is not restricted to be MB2 only. Possible enhancements to other interfaces e.g. xMB, Nmb8 and Nmb10 are possible. + +NOTE 2: The term GCS AS is currently used in EPS only and not same in the context of this solution, the name to be used in 5GS only architecture is FFS. + +The functional description of the solution is as follows: + +1. GCS AS requests to establish a Broadcast service in a "Broadcast" Service Area to 5GC via MBS Session Start for Broadcast procedure (see TS 23.247 [4] clause 7.3.1), where the Broadcast Service Area is an identified area where of concentrated large number of UEs. +2. GCS AS also requests to establish a Multicast Service in a "Multicast" Service Area to 5GC via MBS Session Creation Procedure (see TS 23.247 [4] clause 7.1.1.2 or 7.1.1.3), where the Multicast Service Area is an identified area for Public Safety service that is larger than the Broadcast Service Area. Multicast and Broadcast service areas may overlap. +3. GCS AS configures the UE with both the Multicast service information (with its respective MBS session ID/TMGI) and the Broadcast service information (with its respective MBS Session ID/TMGI) and indicates to the UE that they correspond to the same public safety service. This can for example be done by allowing to include 2 TMGIs instead of one in service description that is sent to the UE in SIP. MESSAGE using the parameter. The exact formatting and changes required to the XML format defined in TS 24.379 [8] will be decided in stage-3. +4. Both Broadcast Service Area (as in Service announcement) and Multicast Service Area (as part of Service announcement or NAS signalling) may be known to UE. +5. The UE may join the Multicast session based on the received information from the GCS AS. +6. If UE based approach for the switching is used, when UE is in Broadcast Service Area, and the UE detects the Broadcast Service is available, the UE enables reception of Broadcast MBS session ID, and if already joined ignores reception of Multicast MBS session ID internally. +If NG-RAN based approach for the switching is used, the procedure in clause 6.16.2.3b is followed. +7. When the UE is outside Broadcast Service Area, and in Multicast Service area the UE receives MBS service in multicast mode. If not already joined, the UE initiates UE join procedure for the Multicast Session. + +## 6.16.2 Procedures + +### 6.16.2.1 GCS AS configuration of both Broadcast and Multicast Services + +![Sequence diagram showing the GCS AS configuration of both Broadcast and Multicast Services. The diagram illustrates the interaction between UE, NG-RAN, 5GC CP, MB-UPF, NEF/MBSF, MBSFT, and GCS AS. The sequence of steps is: 1. GCS AS triggered MBS Session Creation without PCC (TS 23.247 7.1.1.2) or with PCC (TS 23.247 7.1.1.3); 2. UE and GCS AS interaction, UE obtains Multicast information; 3. UE Join and Session establishment (TS 23.247 7.2.1); 4. MBS Session Activation (TS 23.247 7.2.5.2); 5. GCS AS decision to establish Broadcast Session e.g. based on UE report (see clause 6.X.2.4); 6. GCS AS triggered MBS Session Start for Broadcast (TS 23.247 clause 7.3.1); 7. UE and GCS AS interaction, UE obtains Multicast information; 8a. UE receives Broadcast data; 8b. UE triggered Service Request for Multicast reception (Steps 6-10 of MBS session activation procedure TS 23.247 clause 7.2.5). The final part of the diagram shows 'Multicast data' and 'Broadcast data' being transmitted from the NG-RAN to the UE.](742a5484e7dd016256ab99921bbd635d_img.jpg) + +Sequence diagram showing the GCS AS configuration of both Broadcast and Multicast Services. The diagram illustrates the interaction between UE, NG-RAN, 5GC CP, MB-UPF, NEF/MBSF, MBSFT, and GCS AS. The sequence of steps is: 1. GCS AS triggered MBS Session Creation without PCC (TS 23.247 7.1.1.2) or with PCC (TS 23.247 7.1.1.3); 2. UE and GCS AS interaction, UE obtains Multicast information; 3. UE Join and Session establishment (TS 23.247 7.2.1); 4. MBS Session Activation (TS 23.247 7.2.5.2); 5. GCS AS decision to establish Broadcast Session e.g. based on UE report (see clause 6.X.2.4); 6. GCS AS triggered MBS Session Start for Broadcast (TS 23.247 clause 7.3.1); 7. UE and GCS AS interaction, UE obtains Multicast information; 8a. UE receives Broadcast data; 8b. UE triggered Service Request for Multicast reception (Steps 6-10 of MBS session activation procedure TS 23.247 clause 7.2.5). The final part of the diagram shows 'Multicast data' and 'Broadcast data' being transmitted from the NG-RAN to the UE. + +**Figure 6.16.2.1-1: GCS AS configuration of both Broadcast and Multicast Services** + +Figure 6.16.2.1-1 shows the order of procedure execution for a GCS AS to provide a same public safety service via broadcast session in a specific service area and via Multicast session in a larger service area. + +NOTE: In Figure 6.16.2.1-1 the 5GC CP (control plane) denotes for simplicity all transport 5GC NFs relevant to MBS procedures, e.g. MB-SMF, MB-PCF, SMF, AMF, NRF, etc. + +1. In order to establish a Multicast session, the GCS AS initiates MBS Session Creation as defined in either clause 7.1.1.2 of TS 23.247 [4] (for case without PCC) or clause 7.1.1.3 of TS 23.247 [4] (for case with PCC). The GCS AS receives Multicast Session information. +2. The GCS AS may provide to UE(s) the Multicast session information necessary for the UE to join the Multicast session (i.e. TMGI for Multicast session). +3. UE may trigger UE join and Session establishment procedure (see clause 7.2.1 of TS 23.247 [4]) using the TMGI for Multicast provided by GCS AS. +4. When there is MBS data the GCS AS initiates MBS Session Activation for the Multicast TMGI (see clause 7.2.5.2 of TS 23.247 [4]). Step 4 may occur in parallel with steps 5 to 7. +5. The GCS AS may decide to establish a Broadcast session in a specific service area, e.g. based on UE reports in GC1/MCPTT-1 interface and detection of large number of UE receiving the same public safety service in a same area. +6. Based on the decision of step 5, the GCS AS initiates MBS session start for broadcast procedure as defined in TS 23.247 [4] for a Broadcast TMGI. +7. The GCS AS provides to UEs the information for broadcast reception, including the TMGI allocated for the Broadcast session. + +8. A UE that has received both the Broadcast session information (including TMGI for Broadcast session) and Multicast session information (including TMGI for Multicast session) for the same service, determines whether to receive the public safety data via broadcast session or multicast session. + - 8.a. If the UE detects that the Broadcast session is available, UE enables reception of Broadcast for the TMGI allocated for the broadcast session, and if already joined ignores reception of Multicast internally. The UE may ignore a paging with the TMGI allocated for the Multicast session. + - 8.b. If the UE does not detect that Broadcast session is available, and the UE joined the multicast MBS session in step 3, when it receives paging during MBS session activation for the TMGI allocated for Multicast, the UE follows the behaviour defined in clause 7.2.5 of TS 23.247 [4]. + +### 6.16.2.2 UE switching from Broadcast Reception to Multicast Reception + +When a UE that is receiving public safety data via Broadcast session detects that it has moved to a cell that is not providing the broadcast session i.e. the UE detects it has stepped out of the Broadcast service area or if NG-RAN based suspension and resumption is used the related multicast radio bearer is "resumed", the UE proceeds as follows: + +1. If the UE had not joined yet the corresponding Multicast session, the UE triggers MBS join and Session establishment procedure (see clause 7.2.1.3 of TS 23.247 [4]) using the TMGI allocated for Multicast session. +2. If the UE had already joined the corresponding Multicast session, the UE follows the procedures defined in TS 23.247 [4]. + +### 6.16.2.3 UE switching from Multicast Reception to Broadcast Reception (UE based) + +When a UE that is receiving public safety data via Multicast session detects that it has moved to a cell that is providing the broadcast session, i.e. the UE detects it has stepped inside of the Broadcast service area, the UE proceeds as follows: + +1. While the UE is in CM-CONNECTED receiving the Multicast data, the UE should maintain this Multicast reception if still available. This avoids ping pongs when the UE steps in and out of the Broadcast service area. +2. Following a CM-CONNECTED to CM-IDLE transition, the UE may decide to receive public safety data via Broadcast session, e.g. at next Broadcast Session Start. + +### 6.16.2.3b UE switching from Multicast Reception to Broadcast Reception (NG-RAN based) + +The UE based option for switching from multicast reception to broadcast reception assumes that the same content is provided in the same cell using both multicast and broadcast delivery modes. + +In the case of congestion in multicast session, the related Multicast Radio Bearer (MRB) may also be 'suspended' by NG-RAN and the UE becomes aware using AS signalling. + +For example, the UE may receive an explicit indication broadcast from the NG-RAN (similar to what is defined for E-UTRAN in MBMS Scheduling Information in TS 36.300 [15] and TS 36.321 [16]), where it is informed that transmission for the multicast MBS bearer is going to be, or has been, suspended or using other mechanisms decided by RAN. + +**Editor's note:** The details of the AS procedures e.g. whether these are the only possible procedures or other procedures can be considered will be decided in RAN WGs. + +The procedure used by the UE in these scenarios is depicted in figure 6.16.2.3b-1. + +![Sequence diagram showing the interaction between UE, NG-RAN, 5GC CP, MB-UPF, NEF/MBSF, MBSFT, and GCS AS for switching MBS delivery to broadcast following bearer suspension by NG-RAN.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant 5GC CP + participant MB-UPF + participant NEF/MBSF + participant MBSFT + participant GCS AS + + Note over UE, GCS AS: 1. UE and GCS AS interaction, UE obtains Multicast information + Note over NG-RAN, GCS AS: 2. GCS AS triggered MBS Session Start for Broadcast (TS 23.247 clause 7.3.1) + Note over NG-RAN: 3. Suspension Decision + NG-RAN->>UE: 4. Suspension Indication + Note over UE: 5. UE receives Broadcast data + +``` + +Sequence diagram showing the interaction between UE, NG-RAN, 5GC CP, MB-UPF, NEF/MBSF, MBSFT, and GCS AS for switching MBS delivery to broadcast following bearer suspension by NG-RAN. + +**Figure 6.16.2.3b-1: Switching MBS Delivery to Broadcast following bearer suspension by NG-RAN** + +1. The UE has an ongoing group communication using MBS multicast mode. +2. The GCS AS decides to set up the Broadcast Delivery path for the downlink data for this service following the procedure in clause 7.3.1 of TS 23.247 [4]. +3. NG-RAN (e.g. after detecting MBS congestion) decides to suspend one or more MBS bearer(s) (based on e.g. the ARP and/or on the counting results for the corresponding MBS service(s)), and trigger the migration of impacted UEs to receive DL data MBS broadcast mode, by some AS signalling. + +For example, explicitly informing those UEs that the MBS bearer has been, or is going to be, suspended by broadcasting an indication similar to what is defined for E-UTRAN in MBMS Scheduling Information in TS 36.300 [15] and TS 36.321 [16], or using other mechanism decided by RAN. + +NOTE 1: The decision of suspend in NG-RAN is independent with the broadcast session start from GCS AS, if NG-RAN suspends the MRB based on RAN congestion situation, while the broadcast MBS session hasn't been started by AF based on AF counting, it will cause service interruption for those joined UEs. + +4. The UE detects the suspension of the corresponding MBS bearer service, but continues to monitor for MBS Multicast mode delivery. +5. The UE receives DL data by broadcast delivery and continues to monitor for resumption of the MBS bearer. RAN removes the radio resources for the "suspended" MBS bearer(s). + +NOTE 2: UE receiving "suspend" signalling for the MBS bearer does not affect the UEs RRC state. For example, if the UE is RRC\_CONNECTED for other unicast services, continues to be in RRC\_CONNECTED and switches to RRC\_INACTIVE or RRC\_IDLE based on existing RAN triggers. + +NOTE 3: The data associated with the suspended MBS bearer continues to be delivered by the GCS AS on the corresponding multicast transport infrastructure towards NG-RAN (e.g. because it is still delivered via MBS in non-congested cells). This also allows a quicker resumption of the MBMS service when congestion is over. + +### 6.16.3 Impacts on services, entities and interfaces. + +On GCS AS: + +- Decision of delivery method, between multicast, broadcast and unicast with potentially different service areas: +- Use of on UE reports in GCI/MCPTT-1 interface for decision. + +- Configuration of UE of both Broadcast and Multicast session for same service. + +On UE: + +- Receive configuration from GCS AS of both Broadcast session with a TMGI and Multicast session with another TMGI for the same public safety service. +- Decide between reception of public safety data over Broadcast session or over Multicast session. +- Trigger switch from broadcast reception of public safety data and multicast reception of public safety data. +- Trigger switch from multicast reception of public safety data and broadcast reception of public safety data. + +On 5GC and NG-RAN: + +- No impacts for the UE based switching option. +- New procedure and signalling in NG-RAN to perform "suspend" and "resume" of Multicast Radio Bearers for the NG-RAN based option as defined in clause 6.16.2.3b. + +## 6.17 Solution #17: Performance Improvements for Public Safety + +### 6.17.1 Introduction + +This solution addresses leverages the improvements in KI#1 and further improves the call setup time for high number of public safety UEs for Key Issue #6. + +### 6.17.2 Functional description + +This solution enables AMF to get UE join/leave information of a multicast MBS session, so that AMF can maintain the complete group paging information (i.e. list of UEs and the paging area) for the joined CM-IDLE UEs when multicast MBS session is inactive. This solution focuses on the optimization on group paging, which may help group call setup time. + +When the MBS session activation request is received, AMF understands the multicast MBS session is activated. The AMF sends group paging request to MBS supporting NG-RAN nodes and individual paging request for non-MBS supporting NG-RAN nodes for those joined CM-IDLE UEs in the AMF. Usually, the MBS session activation request will reach the AMF prior to the enable group reachability request. In case the enable group reachability request reaches the AMF before the MBS session activation request, AMF can also trigger the group paging and individual paging. The AMF triggers paging once for one multicast MBS session activation procedure. The enable group reachability request or MBS session activation request received afterwards will not trigger the paging again. + +NOTE 1: RRC\_Inactive UEs will be paged using the typically quicker MBS session activation request. They will also not need to send a service request and will thus not benefit from this solution in most cases. + +NG-RAN triggers RAN paging based on MBS session activation request, which is supported in Rel-17. + +**Editor's note:** It is up to RAN WG to determine whether RAN paging can be performed upon receiving group paging request, if the MBS session activation request has not been received. + +In this way, CM-IDLE UEs and CM-CONNECTED UEs with RRC\_INACTIVE state can be notified for the multicast MBS session activation as early as possible. + +When multicast MBS session is activated, NG-RAN is expected to provide a method for those CM-CONNECTED UEs with RRC\_INACTIVE state to enable them to receive multicast MBS session data without being RRC-CONNECTED. + +**Editor's note:** It is up to RAN WG to determine how the method can provided (e.g. NG-RAN updates SIBx/MCCH) when the multicast MBS session is activated. + +When CM-CONNECTED UEs with RRC\_INACTIVE state are notified by the RAN paging, they can utilize the method provided by NG-RAN or locally stored RRC configuration which was configured by NG-RAN before, to receive the multicast MBS session data, in parallel with sending RRC RESUME to the network. + +**Editor's note:** It is up to RAN WG to determine whether RRC RESUME is needed for RRC\_INACTIVE UE to receive the MBS data. + +As AMF maintains CM-IDLE UEs which join the multicast MBS session, it may constantly prepare the group paging information to avoid the processing of UE list included in enable group reachability request, before sending the group paging request. Besides benefits of earlier notification, this solution further minimizes the number of the group paging signals between the AMF and the NG-RANs. Regardless the number of involved SMFs, the AMF only needs to send at most one group paging request to each NG-RAN node for one multicast MBS session. However, compared to the subsequent per-UE service request, the number of saved messages is not significant. + +NOTE 2: It requires that SMFs provide UE join/leave information outside N2SM information. + +NOTE 3: The constant preparation of group paging information requires the additional processing for UE CM state changes, when multicast MBS session is inactive. + +NOTE 4: The AMF needs to maintain backward compatibility with Rel-17 SMFs that will not provide information about the MBS session for the AMF. And for those Rel-17 SMFs, the AMF has to rely on the provided UE list from them for group paging. + +NOTE 5: In mixed deployments with Rel-17 AMFs and/ or SMFs, the benefit of signalling reductions is not much. + +### 6.17.3 Procedures + +#### 6.17.3.1 General + +NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase. + +## 6.17.3.2 UE join multicast MBS session + +![Sequence diagram for UE join multicast MBS session. The diagram shows the interaction between UE, NG-RAN, AMF, SMF, UPF, NRF, PCF, MB-SMF, MB-UPF, and AF. The process involves several steps: 1a. UL NAS message (N1 SM container (PDU Session Modification Request)) from UE to AMF; 1b. Nsmf_PDUSession_UpdateSMContext request from AMF to SMF; 2. Nnrf_NFDiscovery request/response from SMF to NRF; 3. Nmbsmf_MBSSession_ContextStatusSubscribe request/response from SMF to MB-SMF; 4. Authorization check (see clause 6.4.1) within SMF; 5. Nsmf_PDUSession_UpdateSMContext response with UE join info outside N2 SM container from SMF to AMF; 6. N2 message request from AMF to NG-RAN; 7. Establishment of shared delivery towards RAN node if NG-RAN supports 5G MBS (c.f. 7.2.1.4) from NG-RAN to AMF; 8. RRC message (PDU Session Modification command) from NG-RAN to UE; 9. N2 message response from NG-RAN to AMF; 10. Nsmf_PDUSession_UpdateSMContext request from AMF to SMF; 11. Establishment of 5GC Individual MBS traffic delivery if NG-RAN does not support 5G MBS, including 11a. N4 Session Modification, 11b. Nmbsmf_MBSSession_ContextUpdate request, 11c. N4mb Session Modification/Create, 11d. Nmbsmf_MBSSession_ContextUpdate response, and 11e. N4 Session Modification; 12. Nsmf_PDUSession_UpdateSMContext response from SMF to AMF; 13. Multicast data from AF to MB-UPF; 14. Multicast data from MB-UPF to NG-RAN (Transmission via 5GC Shared MBS traffic delivery); 15. Bear selection within NG-RAN; 16. Multicast data via PTP or PTM from NG-RAN to UE; 17. Multicast data from MB-UPF to UPF (Transmission via 5GC Individual MBS traffic delivery); 18. Multicast data via PDU Session from UPF to NG-RAN; 19. Multicast data via PDU Session from NG-RAN to UE.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +Sequence diagram for UE join multicast MBS session. The diagram shows the interaction between UE, NG-RAN, AMF, SMF, UPF, NRF, PCF, MB-SMF, MB-UPF, and AF. The process involves several steps: 1a. UL NAS message (N1 SM container (PDU Session Modification Request)) from UE to AMF; 1b. Nsmf\_PDUSession\_UpdateSMContext request from AMF to SMF; 2. Nnrf\_NFDiscovery request/response from SMF to NRF; 3. Nmbsmf\_MBSSession\_ContextStatusSubscribe request/response from SMF to MB-SMF; 4. Authorization check (see clause 6.4.1) within SMF; 5. Nsmf\_PDUSession\_UpdateSMContext response with UE join info outside N2 SM container from SMF to AMF; 6. N2 message request from AMF to NG-RAN; 7. Establishment of shared delivery towards RAN node if NG-RAN supports 5G MBS (c.f. 7.2.1.4) from NG-RAN to AMF; 8. RRC message (PDU Session Modification command) from NG-RAN to UE; 9. N2 message response from NG-RAN to AMF; 10. Nsmf\_PDUSession\_UpdateSMContext request from AMF to SMF; 11. Establishment of 5GC Individual MBS traffic delivery if NG-RAN does not support 5G MBS, including 11a. N4 Session Modification, 11b. Nmbsmf\_MBSSession\_ContextUpdate request, 11c. N4mb Session Modification/Create, 11d. Nmbsmf\_MBSSession\_ContextUpdate response, and 11e. N4 Session Modification; 12. Nsmf\_PDUSession\_UpdateSMContext response from SMF to AMF; 13. Multicast data from AF to MB-UPF; 14. Multicast data from MB-UPF to NG-RAN (Transmission via 5GC Shared MBS traffic delivery); 15. Bear selection within NG-RAN; 16. Multicast data via PTP or PTM from NG-RAN to UE; 17. Multicast data from MB-UPF to UPF (Transmission via 5GC Individual MBS traffic delivery); 18. Multicast data via PDU Session from UPF to NG-RAN; 19. Multicast data via PDU Session from NG-RAN to UE. + +Figure 6.17.3.2-1: UE join multicast MBS session + +The following additions apply compared to clause 7.2.1.3 of TS 23.247 [4]: + +5. In Nsmf\_PDUSession\_UpdateSMContext response, the SMF includes UE join information including the associated PDU Session ID and MBS Session ID outside the N2 SM information. The AMF stores the information and maintains the joined UE list of the MBS session with its associated PDU Session ID. + +NOTE: Different AMFs may interact with the same RAN nodes for different PDU sessions. It is assumed that each such AMF only stores MBS session IDs and UE join information for the UEs it serves. Different AMFs also store information about the MBS session (MBS session ID and involved RAN nodes) when the shared delivery is established. Thus different information about the same multicast session may reside on multiple AMFs. It is assumed that no synchronisation is performed. + +## 6.17.3.3 UE leave multicast MBS session + +![Sequence diagram for UE leave multicast MBS session. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF. The sequence shows the UE sending a PDU Session Modification Request to the AMF, which then triggers updates through the SMF, UPF, and MB-SMF/UPF. The SMF includes UE leave information in its response to the AMF. The AMF then sends an N2 Message to the NG-RAN, which initiates the release of shared delivery. A dashed box labeled 'For unicast transport' contains steps 4, 5, and 6.](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + participant MB-UPF + + Note right of MB-UPF: For unicast transport + UE->>AMF: 1. PDU Session Modification Request + AMF->>SMF: 2. Nsmf_PDUSession_UpdateSMContext Request + SMF->>UPF: 3a. N4 Session Modification Request + UPF-->>SMF: 3b. N4 Session Modification Response + SMF->>MB-SMF: 4. Nmbsmf_MBSSession_ContextUpdate request + MB-SMF->>MB-UPF: 5. N4mb Session Modification + MB-UPF-->>SMF: 6. Nmbsmf_MBSSession_ContextUpdate response + SMF->>AMF: 7. Nsmf_PDUSession_UpdateSMContext Response with UE leave info outside N2 SM container + AMF->>NG-RAN: 8. N2 Message + UE->>NG-RAN: 9. AN-specific resource modification + NG-RAN->>AMF: 10. N2 Message + AMF->>SMF: 11. Nsmf_PDUSession_UpdateSMContext Request/Response + AMF->>MB-SMF: 12. Nmbsmf_MBSSession_ContextStatusUnsubscribe Request/Response + Note right of NG-RAN: 13. NG-RAN initiates the release of shared delivery (c.f. 7.2.2.4) + +``` + +Sequence diagram for UE leave multicast MBS session. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-SMF, MB-UPF. The sequence shows the UE sending a PDU Session Modification Request to the AMF, which then triggers updates through the SMF, UPF, and MB-SMF/UPF. The SMF includes UE leave information in its response to the AMF. The AMF then sends an N2 Message to the NG-RAN, which initiates the release of shared delivery. A dashed box labeled 'For unicast transport' contains steps 4, 5, and 6. + +Figure 6.17.3.3-1: UE leave multicast MBS session + +The following additions apply compared to clause 7.2.2.2 of TS 23.247 [4]: + +7. In Nsmf\_PDUSession\_UpdateSMContext response, the SMF includes UE leave information outside the N2 SM information. The AMF remove the UE from the joined UE list of the MBS session. + +### 6.17.3.4 Multicast session leave requested by the network or MBS session release + +![Sequence diagram for multicast session leave requested by the network or MBS session release. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-SMF, and MB-UPF. The process starts with MB-SMF sending a context notify to SMF, followed by a reference to another sequence (steps 3-7 of figure 7.2.5.2-1). Then, SMF sends a communication message to AMF with UE leave info, followed by an N2 request to NG-RAN. NG-RAN sends a PDU session modification command to UE, which results in an AN-specific resource modification. Next, NG-RAN initiates a DL tunnel release with MB-SMF/MB-UPF. Finally, NG-RAN sends an N2 response to AMF, and AMF sends a PDUSession_UpdateSMContext request/response to SMF.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-SMF + participant MB-UPF + + Note right of MB-SMF: 1. Nmbsmf_MBSSession_ContextNotify (Release, MBS Session ID) + MB-SMF->>SMF: 1. Nmbsmf_MBSSession_ContextNotify (Release, MBS Session ID) + Note right of SMF: 2. step 3-7 of figure 7.2.5.2-1 + Note right of SMF: 3. Namf_Communication_N1N2MessageTransfer with UE leave info outside N2 SM Container + SMF->>AMF: 4. N2 Request + AMF->>NG-RAN: 5. PDU Session Modification Cmd/Ack + Note right of NG-RAN: 6. AN-specific resource modification + Note right of NG-RAN: 7. NG-RAN initiate the DL Tunnel release with the MB-SMF/MB-UPF (clause 7.2.2.4) + NG-RAN->>AMF: 8. N2 Response + AMF->>SMF: 9. Nsmf_PDUSession_UpdateSMContext request/response + +``` + +Sequence diagram for multicast session leave requested by the network or MBS session release. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-SMF, and MB-UPF. The process starts with MB-SMF sending a context notify to SMF, followed by a reference to another sequence (steps 3-7 of figure 7.2.5.2-1). Then, SMF sends a communication message to AMF with UE leave info, followed by an N2 request to NG-RAN. NG-RAN sends a PDU session modification command to UE, which results in an AN-specific resource modification. Next, NG-RAN initiates a DL tunnel release with MB-SMF/MB-UPF. Finally, NG-RAN sends an N2 response to AMF, and AMF sends a PDUSession\_UpdateSMContext request/response to SMF. + +**Figure 6.17.3.4-1: Multicast session leave requested by the network or MBS session release** + +The following additions apply compared to clause 7.2.2.3 of TS 23.247 [4]: + +3. In Namf\_Communication\_N1N2MessageTransfer request, the SMF includes UE leave information outside the N2 SM information. The AMF remove the UE from the joined UE list of the MBS session. + +## 6.17.3.5 MBS Session Activation + +![Sequence diagram for MBS Session Activation showing interactions between UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF.](b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-UPF + participant MB-SMF + + Note right of MB-SMF: 1. MB-SMF triggers session activation + MB-SMF->>SMF: 2. Nmbsmf_MBSSession_ContextStatusNotify + SMF->>AMF: 3. Namf_MT_EnableGroupReachability request + AMF-->>SMF: 4a. Namf_MT_EnableGroupReachability response + SMF->>AMF: 4b. Namf_Communication_N1N2MessageTransfer + Note left of AMF: 5. AMF pages idle mode UEs + UE->>AMF: 6. Service Request + AMF->>SMF: 7a. Nsmf_PDUSession_UpdateSMContext request + SMF-->>AMF: 7b. Nsmf_PDUSession_UpdateSMContext response + AMF->>SMF: 8a. Namf_MT_UEReachabilityInfo_Notify + SMF->>AMF: 8b. Namf_Communication_N1N2MessageTransfer + AMF->>NG-RAN: 9. N2 request + Note right of NG-RAN: 10a. Establishment of 5GC Shared MBS traffic delivery in clause 7.2.1.4 + Note right of NG-RAN: 10b. Steps 8-12 as described in clause 7.2.1.3 + AMF->>MB-SMF: 11. Namf_MBSCommunication_N2MessageTransfer request (TMGI) + AMF->>NG-RAN: 12. NGAP activation request (TMGI) + NG-RAN-->>AMF: 13. NGAP activation response + AMF-->>MB-SMF: 14. Namf_MBSCommunication_N2MessageTransfer response + MB-SMF->>UPF: 15. N4mb Session Modification + +``` + +Sequence diagram for MBS Session Activation showing interactions between UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. + +Figure 6.17.3.5-1: MBS Session Activation + +The following additions apply compared to clause 7.2.5.2 of TS 23.247 [4]: + +**Paging:** + +- At step 5 (enable group reachability request is received) or after step 11 (MBS session activation request is received), AMF performs group paging and individual paging based on joined UE list in the AMF, , when receiving an enable group reachability request from an SMF or MBS session activation request from the MB-SMF (if the AMF is used for shared delivery establishment), if the paging for the multicast MBS session hasn't been performed. The paging will be requested from each involved AMF once per MBS session activation procedure. A RAN node can receive paging request from multiple AMFs. A possible enable group reachability request or MBS session activation request received afterwards at the AMF from a different SMF will not trigger the paging again. + +NOTE 1: Considering the service request handling contribute most of the latency for those CM-IDLE UEs, the early notification does not bring significant improvement on the group call setup time. However, the improved paging mechanism can reduce the signalling load between the AMF and the NG-RANs effectively depending on how much SMF serving this MBS session. + +In step 11, to utilize MBS session activation request to trigger paging in the AMF, the MB-SMF needs to provide the MBS activation information to the AMF outside the N2 container. + +NOTE 2: Steps 11 to 14 are required to reach those RAN nodes handling CM-CONNECTED UEs (including both RRC\_CONNECTED and RRC\_INACTIVE states). + +**Editor's note:** It is up to RAN WG to determine whether RAN paging can be performed upon receiving group paging request in step 5, if the MBS session activation request has not been received. + +**NG-RAN provide a method to allow UEs to receive multicast MBS session data without being RRC-CONNECTED:** + +- After step 12, NG-RAN needs to provide a method for those CM-CONNECTED UEs with RRC\_INACTIVE state to enable them to receive multicast MBS session data without being RRC-CONNECTED. + +**Editor's note:** It is up to RAN WG to determine whether and how the method can provided (e.g. NG-RAN updates SIBx/MCCH) when the multicast MBS session is activated. + +**UE receives multicast MBS Session data without being RRC-CONNECTED** + +- The CM-CONNECTED UE with RRC\_INACTIVE state is notified by CN-Paging in step 5 (if share the same Paging Occasion) or RAN-Paging in step 12. It utilizes the method provided by NG-RAN or utilizes the locally stored RRC configuration if it has such information and receives multicast MBS session data, in parallel with sending RRC RESUME to NG-RAN. + +### 6.17.3.6 N2 based Handover and IDLE Mobility + +For N2 based handover, the following additions apply compared to clause 7.2.3.3 of TS 23.247 [4]: + +3. In Nsmf\_PDUSession\_updateSMContext response, the SMF includes the UE join information to the T-AMF. The AMF stores/updates the information and maintains the joined UE list of the MBS session with its associated PDU Session ID. + +For IDLE mobility, the following additions apply compared to the clause 4.2.2.2 of TS 23.502 [3]: + +17. In Nsmf\_PDUSession\_updateSMContext response, the SMF includes the UE join information to the new AMF. The AMF stores/updates the information and maintains the joined UE list of the MBS session with its associated PDU Session ID. + +### 6.17.4 Impacts on services, entities and interfaces. + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] are reused exception for the following additions: + +**SMF:** + +- Provide UE join information to the AMF when UE join the multicast MBS session. +- Provide UE leave information to the AMF when UE leave the multicast MBS session or when multicast session leave requested by the network or MBS session release. +- Provide UE join information to the T-AMF in N2 based handover and to the New AMF in IDLE mobility. + +**AMF:** + +- Receive UE join/leave information from the SMF in signalling related to the associated PDU session. +- Receive information about the MBS sessions a UE is participating in during N2 handover and IDLE mode mobility in signalling related to the associated PDU session. +- Maintain for each MBS session the joined UE list and the group paging information of the multicast MBS session. +- Trigger group paging and individual paging, when multicast MBS session activation request or enable group reachability request is received, if the paging for the MBS session activation hasn't been performed. + +**MB-SMF:** + +- Provide MBS activation information to the AMF when sending multicast MBS activation request. + +**NG-RAN:** + +- NG-RAN provides a method to configure those CM-CONNECTED UEs with RRC\_INACTIVE state to enable UEs to receive multicast MBS session data without being RRC-CONNECTED. + +**Editor's note:** It is up to RAN WG to determine how the method can provided (e.g. NG-RAN updates SIBx/MCCH) when the multicast MBS session is activated. + +**Editor's note:** It is up to RAN WG to determine whether RAN paging should be performed upon receiving group paging request, if the MBS session activation request has not been received. + +UE: + +- For CM-CONNECTED UEs with RRC\_INACTIVE state, when they are notified upon MBS session activation, they should utilize the method provided by NG-RAN or utilize the locally stored RRC configuration to receive multicast MBS session data, in parallel with sending RRC RESUME to NG-RAN. + +## 6.18 Solution #18: MBS session management for RRC Inactive MBS data receiving UE + +### 6.18.1 Introduction + +This solution addresses Key Issue #1, especially on the enhancement of MBS session management for RRC Inactive MBS data receiving UE. + +### 6.18.2 Functional description + +This solution builds on top of solution 1. The multicast session management include following procedures: + +- MBS session activation, for UEs in RRC-IDLE state, group paging may be performed to bring the UE to RRC\_CONNECTED as specified in TS 23.247 [4] for Rel-17. + +**Editor's note:** For UEs in RRC-INACTIVE state, the handling of MBS Session Activation in NG-RAN is to be determined by RAN WGs. + +- Multicast session deactivation/multicast session update, the existing procedure as defined in TS 23.247 [4] apply. +- Multicast session release, the handling for UEs in CM-IDLE or CM-CONNECTED with RRC-CONNECTED state follows clause 7.2.2.3 of TS 23.247 [4]. For UEs without activated UP, the following SMF behaviour in step 2 is assumed to avoid paging the IDLE UEs: + +*Alternatively, for UEs without activated UP, the SMF does not trigger message to the AMF, instead the SMF marks that the UE is to be informed of the MBS Session release. In this case, the SMF initiates PDU Session Modification to inform the UE of the MBS Session release at next UP activation of the associated PDU Session, if needed.* + +**Editor's note:** Paging procedures are under remit of the RAN groups and any related enhancements need to be confirmed by RAN groups. + +## 6.18.3 Procedures + +![Sequence diagram illustrating the Multicast Session Activation/Release Procedure. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. The steps are: 1. UE join the multicast MBS session; 2. NG-RAN enable multicast group member receive multicast data in RRC-inactive state; 3. Multicast MBS session become deactivation; 4. MB-SMF triggers MBS session activation or release; 5. MB-SMF sends Nmbsmf_MBSSession_ContextStatusNotify to SMF; 6. SMF sends Namf_MT_EnableGroupReachability request to AMF; 7. AMF sends Paging message to NG-RAN; 8. NG-RAN pages UEs; 9. Final step from clause 7.2.5.2 of TS 23.247.](7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-UPF + participant MB-SMF + + Note right of MB-SMF: 1. UE join the multicast MBS session, see clause 7.2.1.3 of TS 23.247 + Note left of SMF: 2. NG-RAN enable multicast group member receive multicast data in RRC-inactive state. + Note right of MB-SMF: 3. Multicast MBS session become deactivation, see clause 7.2.5.3 of TS 23.247 + Note right of MB-SMF: 4. MBS session activation or MBS session release + Note right of MB-SMF: 5. Nmbsmf_MBSSession_ContextStatusNotify (TMGI, multicast session activated/multicast session release) + Note left of AMF: 6. Namf_MT_EnableGroupReachability request + Note left of NG-RAN: 7. Paging message (TMGI) + Note left of UE: 8. Page UEs + Note right of MB-SMF: 9. Step 6-15 of clause 7.2.5.2 of TS 23.247 + +``` + +Sequence diagram illustrating the Multicast Session Activation/Release Procedure. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. The steps are: 1. UE join the multicast MBS session; 2. NG-RAN enable multicast group member receive multicast data in RRC-inactive state; 3. Multicast MBS session become deactivation; 4. MB-SMF triggers MBS session activation or release; 5. MB-SMF sends Nmbsmf\_MBSSession\_ContextStatusNotify to SMF; 6. SMF sends Namf\_MT\_EnableGroupReachability request to AMF; 7. AMF sends Paging message to NG-RAN; 8. NG-RAN pages UEs; 9. Final step from clause 7.2.5.2 of TS 23.247. + +**Figure 6.18.3.1-1: Multicast Session Activation/Release Procedure.** + +1. UE joins the multicast MBS session via the procedure as defined in clause 7.2.1.3 of TS 23.247 [4]. +2. In some cases, e.g. due to radio resource shortage, NG-RAN could move one or multiple multicast group member UEs to RRC-INACTIVE state and those UEs are still able to received multicast MBS data. +3. The multicast MBS session becomes inactive via the procedure as defined in clause 7.2.5.3 of TS 23.247 [4]. The group member UE can be moved to any state (i.e. CM-IDLE or CM-Connected with RRC Connected/Inactive state). +4. After some time, MB-SMF triggers the multicast session activation or multicast session release. +5. MB-SMF sends Nmbsmf\_MBSSession\_ContextStatusNotify to SMF(s), same as step 2 of clause 7.2.5.2 or step 1a of clause 7.2.2.3 of TS 23.247 [4], which also includes the MBS session status, i.e. activation or release. + +NOTE: Steps 1, 3-5 are same as the one defined in TS 23.247 [4]. + +6. Based on the event information, the SMF determines whether the event is for MBS session activation or MBS session release. The SMF invokes Namf\_MT\_EnableGroupReachability Request to AMF as specified in TS 23.247 [4]. + +**Editor's note:** Whether SMF needs to know that the function that RRC-INACTIVE UE can receive the MBS data is supported or not is FFS. + +7. The AMF determines that there are UEs in CM-IDLE state among the UEs provided by the SMF in step 6, and triggers group paging as specified in TS 23.247 [4]. + +**Editor's note:** When group paging for CM-IDLE UE is performed, whether/how the RRC\_INACTIVE UE(s) sharing the same PO will respond and whether related signalling extensions are required is to be decided by RAN WGs. + +8. The NG-RAN performs the group paging by sending the MBS session ID. + +**Editor's note:** How to handle RRC-inactive UE(s) that joined the MBS session and is able to receive multicast service in RRC-INACTIVE state is to be determined by RAN WGs. + +**Editor's note:** It needs to be confirmed that RRC-INACTIVE UEs also listen to the paging for RRC IDLE UEs, and not only to RAN paging. + +**Editor's note:** It is FFS whether and how UEs, NG-RAN nodes, or AMF also need to consider the transmission mode used in the cell where the UEs are camping to decide whether they can remain in RRC-INACTIVE state. + +For the UE(s) joined the MBS session and need receive multicast service in RRC-Connected state, the handling specified in TS 23.247 [4] will apply. + +9. For MBS session activation, steps 6-15 of clause 7.2.5.2 of TS 23.247 [4] applies. + +**Editor's note:** After receive step 12 in clause 7.2.5.2 of TS 23.247 [4], it is to be determined by RAN WGs whether the NG-RAN need page the UE if the UE is in RRC Inactive state. + +**Editor's note:** After receive step 12 in clause 7.2.5.2 of TS 23.247 [4], it needs clarify the behaviour of RRC-inactive UE after it receives the group paging of the related MBS session ID, e.g. whether it is allowed the UE to be aware it can receive the MBS data in RRC inactive state. + +For MBS session release, steps 3-9 of clause 7.2.2.3 of TS 23.247 [4] is not executed as for UEs without activated UP, the SMF does not trigger message to the AMF, instead the SMF marks that the UE is to be informed of the MBS Session release. In this case, the SMF initiates PDU Session Modification to inform the UE of the MBS Session release at next UP activation of the associated PDU Session, if needed. + +## 6.18.4 Impacts on services, entities, and interfaces + +UE: + +- For RRC\_INACTIVE UEs, multicast session activation is to be determined by RAN WGs. + +**Editor's note:** Detailed impact will be determined by (and/or in collaboration with) RAN WGs. + +## 6.19 Solution #19: Procedures for Transmission mode for inactive data reception + +### 6.19.1 Introduction + +This solution addresses Key Issue #1. + +### 6.19.2 Functional description + +This solution builds on top of solution 1. + +UEs that transition to RRC inactive mode can move freely in their RAN notification area without notifying the RAN nodes. Their location is thus not known at cell level. At the moment only the RAN node serving a UE is aware that it is participating in an MBS multicast session. Additional RAN nodes not handling RRC connected UEs within the multicast session but within RAN notification areas of those UEs may need to be made aware of the multicast session and perform procedures for the multicast session, such as deciding whether to deliver data for the MBS session and choosing the delivery mode, transmitting data of the multicast session and managing the related the shared delivery path. + +**Editor's note:** Related procedures need to be defined by RAN WGs. It also needs to be studied by RAN WGs whether it is possible to determine the presence of inactive UEs that desire to receive a multicast session in a cell. and whether and how a RAN can decide whether to deliver multicast data in cells without RRC connected UEs. Whether additional RAN nodes not handling RRC connected UEs within the multicast session need to be made aware of the multicast session and perform procedures for the multicast session needs to be decided by RAN WGs. + +RAN nodes not serving any connected UEs in the MBS sessions may thus need to be aware of the MBS session. This solution describes two option to accomplish that with CN impacts: + +**Option A:** RAN nodes inform their peers serving parts of RAN notification areas of UEs in an MBS session about the MBS session. The peer RAN nodes request assistance information from the CN via shared delivery establishment. + +**Option B:** The MB-SMF informs all RAN nodes in a service area of an MBS session via the AMF about the MBS session + +**Editor's note:** The RAN-centric option A is in scope of RAN WGs to a large extent. Whether this option is selected thus depends on RAN WGs. + +Editor's note: How the NG-RAN node determines transmission at one cell is not needed due to no UE camped at that cell need be solved by RAN WG. As service areas are optional for multicast MBS sessions, all RAN nodes in a PLMN are possible affected by Option B. + +NOTE 1: It may be preferable to only inform RAN nodes within RAN paging areas. + +RRc\_inactive UEs can move to cells where the transmission mode for RRc connected state is applied and then need to transition to the RRc connected state to receive MBS data. + +The current MBS session activation procedures use paging for the MBS session and trigger RRc-inactive UEs to transition to RRc-connected state. For the delivery mode for RRc\_inactive reception, RRc-inactive UEs should be made aware that the MBS multicast session is activated but remain in RRc-inactive state for multicast data reception. + +NOTE 2: It is not assumed all the RAN node within the same RNA area have the same capability and choose the same delivery mode. + +**Editor's note:** This assumption needs to be confirmed by RAN WGs. Procedures to support UEs that move between cells with different delivery mode need to be agreed by RAN WGs. + +## 6.19.3 Procedures + +### 6.19.3.1 Moving a UE to RRc Inactive state and providing assistance information to additional RAN nodes (Option A) + +![Sequence diagram showing the procedure for moving a UE to RRC Inactive state and providing assistance information to additional RAN nodes (Option A).](fa3258abeaa067802e97eb4d1901572f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN 1 + participant NG-RAN 2 + participant MB-SMF + + Note left of NG-RAN 1: 0. UE received MBS data and is in RRc connected state + Note left of NG-RAN 1: 1. NG-RAN 1 decides to apply transmission mode for RRc inactive reception and to move one or several UEs to RRc inactive state + Note left of NG-RAN 1: 2. RAN internal procedures + Note left of NG-RAN 2: 3. NG-RAN 1 request NG-RAN 2 in RAN paging area of UE(s) to handle MBS multicast session in area + Note left of MB-SMF: 4. Shared Delivery establishment (assistance information) + Note left of NG-RAN 2: 5. RAN internal procedures + +``` + +The sequence diagram illustrates the interaction between a UE, NG-RAN 1, NG-RAN 2, and MB-SMF. The process starts with the UE receiving MBS data in an RRc connected state. NG-RAN 1 then decides to apply a transmission mode for RRc inactive reception and moves the UE to an RRc inactive state. This is followed by RAN internal procedures. NG-RAN 1 then requests NG-RAN 2 to handle the MBS multicast session in its paging area. The MB-SMF performs a shared delivery establishment, providing assistance information. Finally, NG-RAN 2 performs its own RAN internal procedures. + +Sequence diagram showing the procedure for moving a UE to RRC Inactive state and providing assistance information to additional RAN nodes (Option A). + +**Figure 6.19.3.1-1: NG-RAN node moves a UE in 5MBS session to RRc Inactive state** + +0. UE joined an MBS session and receives MBS data while in RRc connected state + +1. NG-RAN 1 uses assistance information to decide whether to apply the delivery mode for RRC-inactive reception for an MBS session, and whether to move one or several UEs in MBS session to RRC inactive state. + 2. RAN internal procedures. + 3. NG-RAN 1 determines that part of the RAN notification areas of the UEs is served by NG-RAN 2. It informs NG-RAN 2 that handling of the MBS session for inactive UEs is required in that area, +- Editor's note:** Depending on RAN decision, assistance information for MBS might be transferred in that step. +4. The NG-RAN 2 establishes shared delivery with MB-SMF. The MB-SMF transmits assistance information as defined in solution 1 for inactive reception in the shared delivery response. + 5. RAN internal procedures at NG-RAN 2 to handle MBS session. + +NOTE: Transfer of assistance information and shared delivery to additional RAN nodes has system impacts in SA WG2 scope. + +### 6.19.3.2 MBS service activation + +![Sequence diagram for MBS service activation showing interactions between UE, NG RAN 1, NG RAN 2, AMF, and MB-SMF.](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG_RAN_1 as NG RAN 1 + participant NG_RAN_2 as NG RAN 2 + participant AMF + participant MB_SMF as MB-SMF + + Note right of NG_RAN_1: 2. RAN procedures + Note right of NG_RAN_2: 3. NG RAN 1 request NG_RAN 2 in RAN paging area of UE(s) to perform RAN paging + Note right of MB_SMF: 4. Shared Delivery establishment (assistance information) + Note right of NG_RAN_2: 5. RAN internal procedures + + AMF->>NG_RAN_1: 1. NGAP activation request (TMGI) + NG_RAN_1->>NG_RAN_2: 3. NG RAN 1 request NG_RAN 2 in RAN paging area of UE(s) to perform RAN paging + NG_RAN_2->>MB_SMF: 4. Shared Delivery establishment (assistance information) + +``` + +The diagram illustrates the sequence of interactions for MBS service activation. It starts with the AMF sending an NGAP activation request (TMGI) to NG RAN 1. NG RAN 1 then performs internal RAN procedures. Next, NG RAN 1 sends a request to NG RAN 2 to perform RAN paging in the area of the UE(s). NG RAN 2 then establishes a shared delivery with the MB-SMF, which provides assistance information. Finally, NG RAN 2 performs its own internal RAN procedures. The UE is shown as a participant but does not have any active interactions in this sequence. + +Sequence diagram for MBS service activation showing interactions between UE, NG RAN 1, NG RAN 2, AMF, and MB-SMF. + +Figure 6.19.3.2-1: MBS service activation + +1. When triggered according to step 11 of Figure 7.2.5.2-1 of TS 23.247 [4], AMF sends NGAP activation request message to NG-RAN nodes. +2. Related RAN procedures. RAN nodes decides whether to deliver in mode for RRC inactive reception, and otherwise will perform RAN paging. For the delivery mode for RRC\_inactive reception, RRC-inactive UEs should be made aware that the MBS multicast session is activated but remain in RRC-inactive state for multicast data reception. +3. NG-RAN 1 determines that part of the RAN notification areas of UEs in MBS session is served by NG-RAN 2. It requests NG-RAN 2 to perform RAN paging for MBS session, + +NOTE: Depending on RAN decision, assistance information for MBS might be transferred in that step. + +4. If not yet done, the NG-RAN 2 establishes shared delivery with MB-SMF. The MB-SMF transmits assistance information (as defined in solution 1) for inactive reception in the shared delivery response. + +5. RAN internal procedures at NG-RAN 2 similar to step 2. + +### 6.19.3.3 Triggering MBS service announcement by MB-SMF (Option B) + +NOTE 1: Unlike the broadcast session start, the present procedure is only used to make the RAN nodes aware that an MBS multicast session enabling delivery for inactive reception is ongoing. RAN nodes can then apply appropriate procedures to handle the MBS session, e.g. decide whether to transmit data and whether to allow RRC\_INACTIVE UE receiving MBS data. + +NOTE 2: UEs still need to join the MBS multicast session as outlined in clause 7.2.1.3 of TS 23.247 [4]. + +**Editor's note:** How the NG-RAN node determines the MBS session data can be transmitted due to UE is in RRC-inactive state need be solved by RAN WGs. + +![Sequence diagram illustrating the triggering of MBS service announcement by MB-SMF (Option B). The diagram shows interactions between UE, NG-RAN, AMF, and MB-SMF. The process starts with MB-SMF creating a new MBS multicast session and determining AMFs in the service area. It then sends a multicast announcement request to the AMF, which determines the NG-RAN in the service area and sends a multicast announcement request to the NG-RAN. The NG-RAN decides whether to apply delivery mode for inactive reception and transmits data. Finally, a shared delivery establishment is performed, followed by RAN procedures.](71f0fd23b2f06b621ba89a65ee3c284c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + + Note right of MB-SMF: 1. Creation of new MBS multicast session where transmission mode for inactive reception is enabled + Note right of MB-SMF: 2. Determine AMFs in service area + MB-SMF->>AMF: 3. Multicast announcement request (service area, MBS session ID, assistance information) + Note right of AMF: 4. Determine NG-RAN in service area + AMF->>NG-RAN: 5. Multicast announcement request (service area, MBS session ID, assistance information) + Note right of NG-RAN: 6. Decide whether to apply delivery mode for inactive reception and transmit data + Note right of NG-RAN: 7. Shared delivery establishment + Note right of UE: 8. RAN procedures + +``` + +Sequence diagram illustrating the triggering of MBS service announcement by MB-SMF (Option B). The diagram shows interactions between UE, NG-RAN, AMF, and MB-SMF. The process starts with MB-SMF creating a new MBS multicast session and determining AMFs in the service area. It then sends a multicast announcement request to the AMF, which determines the NG-RAN in the service area and sends a multicast announcement request to the NG-RAN. The NG-RAN decides whether to apply delivery mode for inactive reception and transmits data. Finally, a shared delivery establishment is performed, followed by RAN procedures. + +**Figure 6.19.3.3-1: Triggering MBS service announcement by MB-SMF (Option B)** + +- Multicast MBS session suitable for delivery mode for inactive reception is created at MB-SMF. The MB-SMF determines whether an MBS session is suitable for inactive reception either based on an indication whether the delivery mode for inactive reception is enabled received from the AF (see solution 1) or based on the QoS of the MBS session. +5. MB-SMF informs RAN nodes in service area of multicast session via AMFs of multicast session and asks them to announce multicast session. The MB-SMF may defer step 2 until a Nmbsmf\_MBSSession\_ContextStatusSubscribe request is received from an SMF. In step 4, AMFs only select NG-RAN nodes in service area supporting delivery mode for RRC\_inactive reception. +6. RAN nodes decide delivery mode for MBS session in a cell and whether to deliver data. + +7. RAN nodes may establish shared delivery as outlined in clause 7.2.1.4 of TS 23.247 [4]. +8. RAN related procedures, e.g. indication of delivery mode or delivery of data. + +**Editor's note:** The steps 6 and 8 are to be decided by RAN WGs. + +### 6.19.3.4 MBS session release (Option A and B) + +![Sequence diagram for MBS session release (Option A and B) involving UE, NG-RAN, AMF, and MB-SMF. The sequence starts with a procedure from Figure 7.2.2.3-1 of TS 23.247. Then, the MB-SMF sends a Namf_MBSSCommunication_N2MessageTransfer request (MBS session release(TMGI)) to the AMF. Finally, the AMF sends an N2 message (MBS session release(TMGI)) to the NG-RAN.](4847c98185bc52e8786b78738bc52b45_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant MB-SMF + Note over UE, MB-SMF: 1. Figure 7.2.2.3-1 of TS 23.247 + MB-SMF->>AMF: 2. Namf_MBSSCommunication_N2MessageTransfer request (MBS session release(TMGI)) + AMF->>NG-RAN: 3. N2 message (MBS session release(TMGI)) + +``` + +Sequence diagram for MBS session release (Option A and B) involving UE, NG-RAN, AMF, and MB-SMF. The sequence starts with a procedure from Figure 7.2.2.3-1 of TS 23.247. Then, the MB-SMF sends a Namf\_MBSSCommunication\_N2MessageTransfer request (MBS session release(TMGI)) to the AMF. Finally, the AMF sends an N2 message (MBS session release(TMGI)) to the NG-RAN. + +**Figure 6.19.3.3-1: MBS session release** + +1. The procedures in Figure 7.2.2.2-1 of TS 23.247 [4] are executed. +2. After a grace period, the MB-SMF checks if shared delivery is still established towards RAN nodes. If so, it sends a request to each related AMF to release the MBS session. + +**Editor's note:** It is to be clarified what is the criteria for MB-SMF to start the guard timer. + +3. The AMF determines stored RAN nodes for the MBS session and forwards the request to those RAN nodes. + +### 6.19.4 Impacts on services, entities and interfaces. + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] are reused. + +In addition to impacts for solution 1: + +#### NG-RAN: + +- Decide transmission mode for a multicast session in a cell. +- Receive assistance information either as part of request for service announcement or within shared delivery Establishment. + +#### UE: + +- Receive MBS data in indicated transmission mode while MBS data is active. + +#### MB-SMF: + +- inform RAN nodes in service area of multicast session (Option B). +- provide assistance information as part of shared delivery establishment. +- inform RAN nodes of MBS session release. + +## 6.20 Solution #20: Registration procedure enhancements for multicast reception + +### 6.20.1 Introduction + +This solution addresses Key Issue #1 and #6. + +**Editor's note:** Further evaluation whether this solution relates to those key issues is required. + +### 6.20.2 Functional description + +When the UE moves to a new Tracking Area (TA) outside the UE's Registration Area in CM-CONNECTED (including CM-CONNECTED with RRC Inactive state) or CM-IDLE state, the UE needs to initiate an Mobility Registration Update procedure towards the 5GS. + +If the UE is in CM-CONNECTED with RRC Inactive state and receiving multicast MBS session(s) before initiating the Mobility Registration Update procedure, in order to avoid interruption in data reception of the multicast MBS session(s), the UE should indicate to the network that the PDU Session(s) associated with the multicast MBS session(s) remain established. + +**NOTE 1:** As described in clause 7.2.2.2 of TS 23.247 [4], if the associated PDU Session is released, the UE leaves MBS Session(s) associated with that PDU session implicitly. To resume the reception of the related MBS service(s), the UE needs to initiate the procedures as defined in clause 7.2.1 of TS 23.247 [4] to re-join the MBS Session(s). + +In addition, since there can be more than one multicast MBS session associated with one PDU Session, it would be beneficial for the UE to also provide the (status) information of multicast MBS session(s) associated with the PDU Session, i.e. whether the UE wants to join or leave (e.g. due to triggers from the application layer) or remain joined an multicast MBS session, so that: + +**NOTE 2:** The network already has information about the MBS sessions a UE joined before. A UE might want to join a multicast if the boundary of the new TA coincides with the boundary of the service area of the multicast session, but the likelihood of that scenario is low. + +- the network will not trigger multicast MBS session establishment towards the NG-RAN if the UE indicates leaving the multicast MBS session. +- the multicast MBS session join/leave procedures is continued in the network and multicast MBS session resources can be reserved or released (if not reserved/released yet) during the registration procedure. + +Compared to Rel-17 MBS specification in TS 23.247 [4] where the UE needs to initiate PDU Session establishment or modification procedures to join/leave the multicast MBS session after the registration, it would improve the signalling efficiency and reduce the time for the UE to join/leave the multicast MBS session(s) to allow the UE to initiate MBS session join/leave or indicate join status in Registration procedures. + +### 6.20.3 Procedures + +#### 6.20.3.1 Registration procedures + +The following enhancements are applied to registration procedure with the following conditions: + +- the registration type is Mobility Registration Update, e.g. upon the UE changing to a new Tracking Area (TA) outside the UE's Registration Area in CM-CONNECTED (including CM-CONNECTED with RRC Inactive state) or CM-IDLE state. +- the UE has established the PDU Session(s) that is or can be associated with the multicast MBS session(s) before the registration procedure. + +The general registration procedure as defined in clause 4.2.2.2.2 of TS 23.502 [3] are used with the following enhancements: + +- In step 1, the UE includes/indicates also the following information in the Registration Request: + +- the PDU Session status of the associated PDU session(s) is set as established, if the UE remains joined or wants to join one or more multicast MBS Session(s) associated with the PDU session(s). +- MBS session information container, which contains the multicast MBS session information associated with the PDU Session ID identifying the associated PDU Session, as follows: + - MBS Session ID(s) and an indication of "join" for the multicast MBS session(s) that it wants to join, if any; + - MBS Session ID(s) and an indication of "leave" for the multicast MBS session(s) that it has joined and wants to leave, if any. +- In step 17, the AMF invokes the Nsmf\_PDUSession\_UpdateSMContext towards the SMF(s) serving the associated PDU Session(s). The Nsmf\_PDUSession\_UpdateSMContext contains the MBS session information container for the associated PDU Session. Then, based on the multicast MBS session information in the MBS session information container: + - if the multicast MBS session information contains the MBS Session ID(s) and indication of "join" for the multicast MBS session(s) that the UE wants to join, steps from step 2 onwards described in clause 7.2.1.3 of TS 23.247 [4] are executed to complete the multicast MBS session join procedure for the UE to join the multicast MBS session(s) identified by the MBS Session ID(s). + - if the multicast MBS session information contains the MBS Session ID(s) and an indication of "leave" for the multicast MBS session(s) that the UE wants to leave, steps from step 3a onwards described in clause 7.2.2.2 of TS 23.247 [4] are executed to remove the UE from the multicast MBS session(s) identified by the MBS Session ID(s). + - if, according to the MBS session context in the SMF, there is/are multicast MBS session(s) that the UE has joined but with MBS Session ID(s) not included the MBS session information container, the SMF considers that the UE remains joined in the multicast MBS session(s). If the network allows the UE to remain in the multicast MBS session, steps from step 5 onwards described in clause 7.2.1.3 of TS 23.247 [4] are executed to complete the multicast MBS session resource establishment procedure for the multicast MBS session(s); otherwise, steps from step 3 onwards described in clause 7.2.2.3 of TS 23.247 [4] are executed to remove the UE from the multicast MBS session(s). + +## 6.20.4 Impacts on services, entities and interfaces + +UE: + +- sets the PDU Session status of the associated PDU session(s) as established, if the UE remains joined or wants to join one or more multicast MBS Session(s) associated with the PDU session(s). +- provides the information of multicast MBS session(s) associated with the PDU Session, i.e. whether the UE wants to join or leave multicast MBS session(s), in the MBS session information container in the Registration Request to the AMF. + +AMF: + +- sends the MBS session information container received in the Registration Request towards the SMF(s) serving the associated PDU Session(s) in Registration procedures. + +SMF: + +- performs the corresponding multicast MBS session procedures based on the information in the MBS session information container. + +**Editor's note:** It is FFS whether there are RAN impacts due to a new SM container in registration request. The NG-RAN behaviour is to be determined by RAN WGs. + +## 6.21 Solution #21: Mobility Procedures for UE supporting RRC Inactive MBS data reception with the MBS session container + +### 6.21.1 Introduction + +This solution addresses Key Issue #1. + +### 6.21.2 Functional description + +For the UE joined the multicast MBS session(s) and allowed receiving MBS data in RRC-inactive state, if it moves out its RNA and within RA, the UE triggers the RNA update procedure. If the resumption of the RRC connection fails, the UE may initiate the Mobility Registration Update procedure with the MBS session information (i.e. whether the UE wants to join or leave a multicast MBS session) in the MBS session information container together with the associated PDU Session ID(s), to trigger the network to complete multicast MBS session join and/or leave procedures. + +NOTE: The UE may decide to join or leave a multicast session during the Mobility Registration Update procedure when the resumption of the RRC connection fails, e.g. due to pending application request. + +Later on, if the network supports multicast MBS session transmission to the UE in RRC Inactive state, the UE may be changed to RRC Inactive state to receive the MBS data. + +### 6.21.3 Procedures + +#### 6.21.3.1 RRC-inactive multicast group member UE move out of RNA and within RA + +For the UE joined the multicast MBS session(s) and allowed receiving MBS data in RRC-inactive state, if the UE moves out its RNA and within RA, it triggers the RNA update procedure as usual. Based on that procedure, the network may: + +- keep the UE in the RRC Inactive state for MBS data reception, if the network supports multicast MBS session transmission to the UE in RRC Inactive state; or +- move the UE to RRC Idle state if the UE context cannot be retrieved successfully by the NG-RAN. In this case: + - the UE may invoke the Mobility Registration Update procedure by sending a Registration Request which contains the associated PDU session ID(s) and the MBS session information container. The MBS session information container contains the multicast MBS session information associated with the PDU Session ID identifying the associated PDU Session, as follows: + - MBS Session ID(s) and an indication of "join" for the multicast MBS session(s) that it wants to join, if any; + - MBS Session ID(s) and an indication of "leave" for the multicast MBS session(s) that it has joined and wants to leave, if any. + +The AMF forwards the MBS session information container towards the SMF serving the associated PDU Session by invoking the Nsmf\_PDUSession\_UpdateSMContext service operation. Then, based on the multicast MBS session information in the MBS session information container, the SMF continues to perform multicast MBS session join and/or leave procedures as specified in TS 23.247 [4]. Later on, if the network supports multicast MBS session transmission to the UE in RRC Inactive state, the UE may be changed to RRC Inactive state to receive the MBS data. + +### 6.21.4 Impacts on services, entities, and interfaces + +UE: + +- When the UE receives the MBS data in RRC Inactive state and moves to a new cell but the resumption of the RRC connection fails, the UE provides the MBS session information (i.e. whether the UE wants to join or leave multicast MBS session(s)) in the MBS session information container together with the associated PDU Session ID(s), in the Mobility Registration Update procedure. + +SMF: + +- Performs the corresponding multicast MBS session procedures based on the information in the MBS session information container. + +AMF: + +- Sends the MBS session information container received in the Registration Request towards the SMF(s) serving the associated PDU Session(s). + +**Editor's note:** It is FFS whether there are RAN impacts due to a new SM container in registration request. The NG-RAN behaviour is to be determined by RAN WGs. + +## 6.22 Solution #22: Session management for RRC Inactive MBS data receiving UE + +### 6.22.1 Introduction + +This solution addresses Key Issue #1, for the SM procedure handling for handling UEs in CM-CONNECTED/RRC\_INACTIVE state. + +### 6.22.2 Functional description + +This solution is alternative to solution #4 that is currently documented in the TR. The multicast session management include following procedures: + +- When MBS session is de-activated as defined in clause 7.2.5.3 of TS 23.247 [4], the NG-RAN node keeps the multicast MBS session context and N3mb shared tunnel for the multicast MBS session as long as the NG-RAN has UE context for UEs in the MBS session context which may be in either RRC-CONNECTED or RRC\_INACTIVE state. In other words, the NG-RAN does not trigger release of the shared delivery as described in clause 7.2.2.4 of TS 23.247 [4] if it maintains context for RRC\_INACTIVE UEs. +- During MBS session (re-)activation, the group-based paging is executed only for UEs in CM-IDLE state as currently defined. A UE in RRC-INACTIVE state is in CM-CONNECTED state in CN and therefore group paging is not needed for this UE. + +**Editor's note:** RAN paging procedures are under remit of the RAN groups. + +### 6.22.3 Procedures + +#### 6.22.3.1 Modification to the MBS session de-activation procedure + +![Sequence diagram for MBS session de-activation procedure. Lifelines: UE, NG-RAN, AMF, UPF, SMF, MB-UPF, MB-SMF. Step 1: MB-UPF to MB-SMF (Steps 1-4 from TS 23.247 clause 7.2.5.3). Step 2: MB-SMF to AMF (Namf_MBSSCommunication_N2MessageTransfer request (TMGI)). Step 3: AMF to MB-SMF (Namf_MBSSCommunication_N2MessageTransfer response). Arrows from AMF, UPF, and SMF to MB-UPF are crossed out with an 'X'.](21c8a1f65b4718372aadf6a1cc10204d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UPF + participant SMF + participant MB-UPF + participant MB-SMF + + Note right of MB-UPF: 1. Steps 1-4 from TS 23.247 clause 7.2.5.3 + MB-UPF->>MB-SMF: + Note left of MB-SMF: + MB-SMF->>AMF: 2. Namf_MBSSCommunication_N2MessageTransfer request (TMGI) + Note left of AMF: + AMF->>MB-SMF: 3. Namf_MBSSCommunication_N2MessageTransfer response + Note left of MB-SMF: + AMF-xMB-UPF: + UPF-xMB-UPF: + SMF-xMB-UPF: + +``` + +Sequence diagram for MBS session de-activation procedure. Lifelines: UE, NG-RAN, AMF, UPF, SMF, MB-UPF, MB-SMF. Step 1: MB-UPF to MB-SMF (Steps 1-4 from TS 23.247 clause 7.2.5.3). Step 2: MB-SMF to AMF (Namf\_MBSSCommunication\_N2MessageTransfer request (TMGI)). Step 3: AMF to MB-SMF (Namf\_MBSSCommunication\_N2MessageTransfer response). Arrows from AMF, UPF, and SMF to MB-UPF are crossed out with an 'X'. + +**Figure 6.22.3.1-1: MBS session de-activation procedure to allow keeping the UEs in CM-CONNECTED/RRC\_INACTIVE state** + +1. No changes to steps 1-4 compared to TS 23.247 [4] clause 7.2.5.3. + +2-3. Steps 2 and 3 are shown in the figure for comparison with existing procedure since MB-SMF does not request de-activation of the MBS session and the AMF does not send NGAP deactivation request message (N2 SM information ()) to the NG-RAN nodes since the UEs are kept in CM-CONNECTED state. The NG-RAN node keeps the multicast MBS session context and N3mb shared tunnel for the multicast MBS session. NG-RAN can decide locally to change the RRC state of some UEs to RRC\_INACTIVE. + +NOTE 1: Based on this procedure UEs are kept in CM-CONNECTED state while the MBS session is deactivated, and they do not transit to CM-IDLE state (as in Rel-17). + +The MBS session context will never indicate that there are no UEs for the multicast MBS session, and therefore the NG-RAN will never trigger release of the shared delivery as described in clause 7.2.2.4. + +NOTE 2: NG-RAN does not trigger release of the shared delivery if there are UEs in CM-CONNECTED and RRC-Inactive. + +### 6.22.3.2 Modification to the MBS session (re-)activation procedure + +![Sequence diagram showing the MBS session re-activation procedure. The diagram includes seven entities: UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. The procedure is divided into two main steps. Step 1, labeled 'Steps 1-4a from TS 23.247 clause 7.2.5.2', involves a request from MB-SMF to MB-UPF. Step 2, labeled 'Steps 11-15 from TS 23.247 clause 7.2.5.2', involves a request from MB-UPF to AMF, which then interacts with NG-RAN, SMF, and UPF. The UE is shown as a vertical line on the left, indicating its presence but not its direct involvement in the signaling steps shown.](0d9b44054c70dcda35129f11b97a912f_img.jpg) + +Sequence diagram showing the MBS session re-activation procedure. The diagram includes seven entities: UE, NG-RAN, AMF, SMF, UPF, MB-UPF, and MB-SMF. The procedure is divided into two main steps. Step 1, labeled 'Steps 1-4a from TS 23.247 clause 7.2.5.2', involves a request from MB-SMF to MB-UPF. Step 2, labeled 'Steps 11-15 from TS 23.247 clause 7.2.5.2', involves a request from MB-UPF to AMF, which then interacts with NG-RAN, SMF, and UPF. The UE is shown as a vertical line on the left, indicating its presence but not its direct involvement in the signaling steps shown. + +**Figure 6.22.3.2-1: MBS session re-activation procedure to allow keeping the UEs CM-CONNECTED/RRC\_INACTIVE state** + +1. No changes to steps 1-4a compared to clause 7.2.5.2 of TS 23.247 [4]. After receiving the request, for each UE in the list, the AMF determines CM state of the UE and determines that specific UEs are CM-CONNECTED (since they are in RRC\_INACTIVE state in NG-RAN). The AMF indicates those UEs to the SMF, using Namf\_MT\_EnableGroupReachability Response (UE list). +2. No changes to steps 11-15 compared to clause 7.2.5.2 of TS 23.247 [4]. The shared tunnel has been established before, and therefore there is no need for it to be established. When the service is re-activated and there are UEs in RRC\_INACTIVE state, the NG-RAN needs to notify the UEs of this activation. + +NOTE: How the UEs are notified in this case is up to RAN2 to decide. + +## 6.22.4 Impacts on services, entities, and interfaces + +NG-RAN: + +- Keeps the MBS session context when it wants to allow reception in RRC\_INACTIVE. + +MB-SMF: + +- Does not de-activate the shared tunnel. + +## 6.23 Solution #23: MBS session activation for RRC Inactive MBS data receiving UE + +### 6.23.1 Introduction + +This solution addresses Key Issue #1, especially on the MBS session activation for RRC Inactive MBS data receiving UE. + +This solution builds on top of solution 6, i.e. reuse the Qos information to determine whether MBS session can be put into RRC inactive. + +## 6.23.2 Functional description + +This solution builds on top of solution 6. The solution is based on the following principles: + +- For the MBS session deactivation procedure, there is no impact. After MBS session deactivation, the NG-RAN can determine how to handle the RRC inactive UE. +- The AMF know the 5GS support receiving multicast data in RRC inactive state. The AMF is aware of NG-RAN capability for supporting reception of MBS data in RRC Inactive state. +- When the AMF receives the Namf\_MT\_EnableGroupReachability from SMF, the AMF figures out the paging area covering all the registration areas of those UE(s), which need to be paged. This paging area includes the all the registration areas of those UE in CM-IDLE mode, and NG-RAN node where the CM-Connected mode UE(s) is camping on. For example, even all the UEs involved in the MBS session are in CM-Connected mode, the AMF need to figure out the NG-RAN node the UEs camp on, so the AMF need to inform these NG-RAN nodes to handle the potential RRC inactive UE. + +**Editor's note:** There is a need for further explanation of this procedure. RAN paging will also be triggered by the MB-SMF, and this request is typically faster as it does not need to be forwarded by SMFs. + +- When the NG-RAN receives the paging request from AMF with TMGI, it perform the paging for the UE (e.g. UE in idle mode and RRC Inactive mode). + +**NOTE:** How the NG-RAN handle the UE in the RRC inactive when receives the paging request is in RAN scope. + +**Editor's note:** When receiving the group paging, the behaviour of UE supporting RRC inactive reception will be further defined by RAN WGs. + +**Editor's note:** Whether the radio resource (MRB) for multicast MBS can be established for the UE in RRC Inactive state depends on RAN WG decision. + +### 6.23.3 Procedures + +![Sequence diagram of the Multicast Session Activation Procedure. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-UPF, MB-SMF. The procedure starts with MB-SMF triggering session activation, followed by context status notifications and reachability requests. It includes AMF paging of idle mode UEs, service requests, and session context updates. A dashed box indicates steps 10a and 10b, which refer to other clauses. The final steps involve NGAP activation requests and responses, and an N4mb session modification.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant MB-UPF + participant MB-SMF + + Note right of MB-SMF: 1. MB-SMF triggers session activation + MB-SMF->>SMF: 2. Nmbsmf_MBSSession_ContextStatusNotify + SMF->>AMF: 3. Namf_MT_EnableGroupReachability request + AMF-->>SMF: 4a. Namf_MT_EnableGroupReachability response + AMF->>SMF: 4b. Namf_Communication_N1N2MessageTransfer + Note left of AMF: 5. AMF pages idle mode UEs + UE->>AMF: 6. Service Request + AMF-->>SMF: 7a. Nsmf_PDUSession_UpdateSMContext request + SMF-->>AMF: 7b. Nsmf_PDUSession_UpdateSMContext response + AMF-->>SMF: 8a. Namf_MT_UEReachabilityInfo_Notify + AMF->>SMF: 8b. Namf_Communication_N1N2MessageTransfer + SMF->>NG-RAN: 9. N2 request + Note right of NG-RAN: 10a. Establishment of 5GC Shared MBS traffic delivery in clause 7.2.1.4 + Note right of NG-RAN: 10b. Steps 8-12 as described in clause 7.2.1.3 + AMF->>MB-SMF: 11. Namf_MBSCommunication_N2MessageTransfer request (TMGI) + AMF->>NG-RAN: 12. NGAP activation request (TMGI) + NG-RAN-->>AMF: 13. NGAP activation response + AMF-->>MB-SMF: 14. Namf_MBSCommunication_N2MessageTransfer response + MB-SMF->>UPF: 15. N4mb Session Modification + +``` + +Sequence diagram of the Multicast Session Activation Procedure. Lifelines: UE, NG-RAN, AMF, SMF, UPF, MB-UPF, MB-SMF. The procedure starts with MB-SMF triggering session activation, followed by context status notifications and reachability requests. It includes AMF paging of idle mode UEs, service requests, and session context updates. A dashed box indicates steps 10a and 10b, which refer to other clauses. The final steps involve NGAP activation requests and responses, and an N4mb session modification. + +**Figure 6.23.3.1-1: Multicast Session Activation Procedure** + +The procedure is on top of TS 23.247 [4] Figure 7.2.5.2-1, with following enhancement. + +Before step 1, the NG-RAN may move some UE into CM-Connected with RRC Connected/Inactive state. + +5. The AMF figures out the paging area covering all the registration areas of those UE(s), which need to be paged. This paging area includes the all the registration areas of those UE in CM-IDLE mode, and NG-RAN node where the CM-Connected mode UE(s) is camping on. The AMF sends a paging request message to the NG-RAN node(s) belonging to this Paging Area with the TMGI as the identifier to be paged if the related NG-RAN node(s) support MBS. If the NG-RAN node(s) do not support MBS, the AMF sends initiate the normal CN paging. + +6. For the RRC inactive mode UE, the NG-RAN initiates the RAN paging. + +For the UE(s) joined the MBS session and need receive multicast service in RRC-Connected state, the UE initiates the Service Request as usual. + +NOTE 1: How the NG-RAN handle the UE in the RRC inactive when receives the RAN paging request is in RAN scope. + +12. If step received before step 5, for the RRC inactive mode UE, the NG-RAN initiates the RAN paging. Which is similar with step 6. + +NOTE 2: In most cases, the step 12 is before step 5. + +Editor's note: The UE behaviour when received the group paging is to be defined by RAN WG. + +### 6.23.4 Impacts on services, entities, and interfaces + +AMF: + +- The AMF figures out the paging area covering all the registration areas of those UE(s), which need to be paged. This paging area includes the all the registration areas of those UE in CM-IDLE mode, and NG-RAN node where the CM-Connected mode UE(s) is camping on. + +Editor's note: The NG-RAN behaviour is RAN scope. + +## 6.24 Solution #24: Solution based on configuration in RAN to support MOCN RAN Sharing + +### 6.24.1 Introduction + +This solution addresses Key Issue #2. + +### 6.24.2 Functional description + +This solution relies on RAN configuration does not need any new parameter as proposed in existing solutions but the service-id part of the TMGI of the RAN sharing partners that corresponds to the same content is configured in RAN. + +For example, if PLMNs with MCC=234, MNC=15 (operator A) and MCC=234, MNC=10 (operator B) are doing MBS RAN sharing, the corresponding RAN nodes are already configured with the PLMN-ids of each of the sharing partner and can be configured with the specific respective service-id (6 digits numbers) of the TMGIs of two PLMNs that correspond to the same content or even range of service-ids. For instance, service-id=123456 (for operator A) and service-id=001234 (for operator B) corresponds to content from "TV channel X". This means that the corresponding MB-SMF in each PLMN will allocate the service ids for the TMGI based on the specific range expected for the same content. Then the RAN node can populate accordingly the MCCH with the respective TMGI of the RAN sharing partners. Based on rel.17 RRC encoding, it is possible to have common MTCH configuration and same G-RNTI mapped to different TMGIs. Based on RAN OAM configuration, it is possible to identify which TMGIs (belonging to different PLMNs in this case) providing same broadcast service. + +In the service announcement for the broadcast MBS sessions delivering the same content, the respective MBSFs of each PLMN can indicate the PLMN specific TMGI to the UEs. + +Editor's note: Support of the encrypted content reception is FFS. + +### 6.24.3 Procedures + +#### 6.24.3.1 General + +#### 6.24.3.2 MBS Session Creation + +As in clauses 7.1.1.2 and 7.1.1.3 of TS 23.247 [4] for each PLMN. + +## 6.24.3.3 MBS Session Start for Broadcast + +![Sequence diagram for MBS Session Start for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, AF. The sequence starts with a common step '1. TMGI allocation, MBS Session Create and service Announcement: see clause 7.1.1.2 or 7.1.1.3'. Then, AMF sends '2. Namf_MBSBroadcast_ContextCreate Request' to MB-SMF. AMF also sends '3. N2 message Request' to NG-RAN. NG-RAN creates '4. MBS Session context created'. NG-RAN sends '5. IGMP/MLD join' to MB-UPF. NG-RAN sends '6. N2 message Response' to AMF. AMF sends '7. Namf_MBSBroadcast_ContextCreate Response' to MB-SMF. MB-SMF sends '8. N4mb Session Update' to MB-UPF. NG-RAN sends '9. NG-RAN advertises TMGI' to UE. NG-RAN sends '10. N2 message Response' to AMF. AMF sends '11. Namf_MBSBroadcast_ContextStatusNotify Request' to MB-SMF. MB-SMF sends '12. N4mb Session Update' to MB-UPF. Finally, media streams are shown: '13. Media stream' from AF to MB-UPF, '14. Media stream' from MB-UPF to AMF, and '15. PTM transmission' from AMF to UE.](145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg) + +Sequence diagram for MBS Session Start for Broadcast. Lifelines: UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, AF. The sequence starts with a common step '1. TMGI allocation, MBS Session Create and service Announcement: see clause 7.1.1.2 or 7.1.1.3'. Then, AMF sends '2. Namf\_MBSBroadcast\_ContextCreate Request' to MB-SMF. AMF also sends '3. N2 message Request' to NG-RAN. NG-RAN creates '4. MBS Session context created'. NG-RAN sends '5. IGMP/MLD join' to MB-UPF. NG-RAN sends '6. N2 message Response' to AMF. AMF sends '7. Namf\_MBSBroadcast\_ContextCreate Response' to MB-SMF. MB-SMF sends '8. N4mb Session Update' to MB-UPF. NG-RAN sends '9. NG-RAN advertises TMGI' to UE. NG-RAN sends '10. N2 message Response' to AMF. AMF sends '11. Namf\_MBSBroadcast\_ContextStatusNotify Request' to MB-SMF. MB-SMF sends '12. N4mb Session Update' to MB-UPF. Finally, media streams are shown: '13. Media stream' from AF to MB-UPF, '14. Media stream' from MB-UPF to AMF, and '15. PTM transmission' from AMF to UE. + +**Figure 6.24.3.3-1: Existing MBS Session Start for Broadcast for MOCN RAN sharing (as in clause 7.3.1 of TS 23.247 [4])** + +The following modifications apply compared to clause 7.3.1 of TS 23.247 [4] when MBS Session Start for the second and later broadcast MBS sessions: + +1. Each PLMN needs to allocate the TMGIs based on the specific service-ids or ranges of service-ids. For example, MB-SMF of operator A allocates service-id=123456 and MB-SMF of operator B service-id=001234. This can happen in different ways: + - a) NEF/MBSF will need to pass the afID defined in Nnef\_TMGI\_Allocate to MB-SMF using Nmbsmf\_TMGI\_Allocate (i.e. afID needs to be added in TS 29.532 [17]) and therefore allow MB-SMF to have a "policy" in TMGI allocation based on identification of AF. The afID is currently encoded in "string" format according to TS 29.522 [18], and it needs to provide enough information (e.g. indicating specific content) to NEF/MBSF in order to allocate the TMGI according to the required "policy". + - b) MB-SMF can delegate a TMGI range to NEF to allocate for that purpose and keep the afID so it can assign based on some policy + - c) (if MBSF is used) MB-SMF can delegate a TMGI range to MBSF to allocate for that purpose and it can assign the TMGI based on some "policy" depending on the identification of AF + +**Editor's note:** Whether the afID will be provided to MB-SMF will be coordinate with CT WG4. + +No changes required in steps 2-8. + +9. Since NG-RAN is configured with the list of the associated specific service-ids or ranges of service-ids of the TMGIs of each RAN sharing partner whose content has been delivered over the air, the NG-RAN propagates the TMGI for the new PLMN for which the second or later broadcast session is established. + +For example, if the service-id=123456 (for operator A) and service-id=001234 (for operator B) corresponds to content from "TV channel X" and MCCH already advertised TMGI= 123456 234 15, it also adds in MCCH TMGI= 001234 234 10. + +NG-RAN configures the same MTCH for both TMGIs. + +The UE from operator B, having received the service announcement is able to read the TMGI (001234 234 10) and receive the content. + +15. Since NG-RAN understands the broadcast MBS Session is associated with another Broadcast MBS Session identified by the corresponding TMGI whose content has been delivered over the air, the NG-RAN can silently drop packets received in this broadcast MBS session, and do not deliver them again. + +Editor's note: Details will be confirmed by the RAN WGs. + +Editor's note: It is FFS whether NG-RAN should avoid establishing UP resources for the second and later broadcast MBS sessions for more saving. + +#### 6.24.3.4 MBS Session Release for Broadcast + +![Sequence diagram for MBS Session Release for Broadcast for MOCN RAN sharing. The diagram shows the interaction between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process involves: 1. Media stream delivery from AF to UE via NEF/MBSF, PCF, MB-UPF, MB-SMF, AMF, and NG-RAN. 2. MBS Session Deletion (referenced to Figure 7.1.1.3-1) initiated by AF. 3. Namf_MBSBroadcast_ContextRelease Request (TMGI) from AMF to NG-RAN. 4. MB Session Resource Release Req (TMGI) from NG-RAN to AMF. 5. Remove TMGI from MCCH from NG-RAN to UE. 6. MLD/IGMP Leave (LL MC addr) from UE to PCF. 7. MB Session Resource Release Resp from AMF to NG-RAN. 8. Namf_MBSBroadcast_ContextRelease Response from AMF to MB-SMF. 9. TMGI De-allocation (referenced to Figure 7.1.1.3-1) involving MB-SMF, MB-UPF, and PCF.](bbddeb46a8bee133d49003273fcfc8dd_img.jpg) + +Sequence diagram for MBS Session Release for Broadcast for MOCN RAN sharing. The diagram shows the interaction between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process involves: 1. Media stream delivery from AF to UE via NEF/MBSF, PCF, MB-UPF, MB-SMF, AMF, and NG-RAN. 2. MBS Session Deletion (referenced to Figure 7.1.1.3-1) initiated by AF. 3. Namf\_MBSBroadcast\_ContextRelease Request (TMGI) from AMF to NG-RAN. 4. MB Session Resource Release Req (TMGI) from NG-RAN to AMF. 5. Remove TMGI from MCCH from NG-RAN to UE. 6. MLD/IGMP Leave (LL MC addr) from UE to PCF. 7. MB Session Resource Release Resp from AMF to NG-RAN. 8. Namf\_MBSBroadcast\_ContextRelease Response from AMF to MB-SMF. 9. TMGI De-allocation (referenced to Figure 7.1.1.3-1) involving MB-SMF, MB-UPF, and PCF. + +Figure 6.24.3.4-1: MBS Session Release for Broadcast for MOCN RAN sharing + +The following modifications apply compared to clause 7.3.2 of TS 23.247 [4] when MBS Session Release for the broadcast MBS session which is created firstly: + +5. If the NG-RAN intends to perform MBS Session Release for operator A but determines there are other corresponding broadcast MBS sessions for other PLMNs available, it removes only the TMGI for operator A from the MCCH while keeping the rest of the TMGIs. NG-RAN should switch to another MBS session to receive data (e.g. MBS session for operator B). + +Editor's note: Details will be confirmed by the RAN WGs. + +#### 6.24.4 Impacts on services, entities and interfaces. + +Functional entities defined in clause 5.3.2 of TS 23.247 [4] are reused exception for the following additions: + +NG-RAN: + +- RAN is configured with specific service-ids or service-id ranges corresponding to the same content for each of their RAN sharing partners. +- During MBS Session starts for each of the MOCN PLMNs NG-RAN adds to the MCCH the corresponding TMGI. +- During MBS Sessions releases for each of the MOCN PLMNs NG-RAN removes from the MCCH the corresponding TMGI. +- RAN configures the same MTCH for each of the TMGI corresponding the same content as allowed by existing Rel-17 RRC. + +Depending on which option is used for TMGI allocation by the PLMN (a, b, or c) different impacts apply: + +In the case of a): + +MB-SMF: + +- MB-SMF of each PLMN is configured with specific service-ids or service-id ranges corresponding to the same content based on AF ID provide from NEF. + +NEF: + +- NEF to provides AF Id to MB-SMF. + +In the case of b): + +NEF: + +- NEF to allocate TMGI and keep the afID so it can assign TMGI based on some policy that applies per specific content from AF. + +In the case of c): + +MBSF: + +- MBSF to allocate TMGI and keep the afID so it can assign TMGI based on some policy that applies per specific content from AF. + +No other impacts in AF, and UE. + +## 6.25 Solution #25: Triggering capability limited devices to receive MBS data + +### 6.25.1 Introduction + +This solution addresses Key Issue #5. + +### 6.25.2 Description + +To enable capability limited devices using power-saving mechanisms (MICO (Mobile Initiated Connection Only) mode, DRX (Discontinuous Reception), eDRX (Extended Discontinuous Reception) to extend their battery live, those devices need to wake up at coordinated times when the MBS data are being transmitted. For MBS multicast reception, the UEs send service requests at those times when being in idle state beforehand. While no MBS data are being transmitted, the devices follow the power saving procedures and may thus not be reachable + +If periodic transmissions are scheduled in an MBS session or the MBS session is set up for a one-time delivery, the devices may be informed in advance via service announcement or when it joins the MBS session about the time(s) when MBS data transmission will take place. The AF provides information about the time(s) when MBS data transmission will take place via NEF/MBSF to MB-SMF when configuring the multicast session. MB-SMF activates/deactivates multicast session based on configured times. The UEs start to receive MBS data at the configured times. + +If an MBS session is used to transmit data at irregular intervals, the devices need to be informed about the data transmission while the MBS session is ongoing. The AF sends a delayed activation request indicating the desired activation time for an MBS session to the MB-SMF, and the MB-SMF request the SMFs to perform a delayed activation. The SMFs in turn request the AMFs to perform deferred paging. If UEs negotiated an eDRX cycle and joined the multicast session, the AMF pages the UE in the Paging Hyperframes (PH) / time intervals calculated according to eDRX procedures before the transmission start and indicates the transmission start time. + +**NOTE:** For a periodic transmission or a one-time transmission it is sufficient to let the AF activate or deactivate the MBS Session based configured time. For transmission at irregular intervals not known at service announcement time, UEs need to be informed before the transmission can start and the delayed activation request is required. + +**Editor's note:** whether both scenarios will be supported will be assessed in the evaluation phase. + +## 6.25.3 Procedures + +### 6.25.3.1 Periodic or one time transmission of MBS data to capability-limited devices + +![Sequence diagram illustrating the procedure for periodic or one time transmission of MBS data to capability-limited devices. The diagram shows interactions between UE, RAN, AMF, SMF, MB-SMF, and AF. The process starts with AF sending an MBS session creation message to MB-SMF. MB-SMF stores the session configuration and sends a Service Announcement to the UE. The UE sends a PDU session modify (Join MBS) request to the SMF. The SMF sends an Nmbsmf_MBSSession_ContextStatusSubscribe to the MB-SMF. The MB-SMF sends a PDU Session Modify Response (Join Ack) to the SMF. The SMF sends an Activate/Paging message to the AMF. The AMF sends a Multicast data message to the RAN. The RAN sends a Multicast data message to the UE. Two dashed boxes indicate that at the configured wake-up times, the UE starts reception and the MB-SMF triggers activation.](d9638e837004a4e09dbbc50b8aecbd5f_img.jpg) + +``` + +sequenceDiagram + participant AF + participant MB-SMF + participant SMF + participant AMF + participant RAN + participant UE + + Note right of MB-SMF: session configuration stored (wake up times) + + AF->>MB-SMF: MBS session creation (MBS session ID, Wake Up Times) + MB-SMF-->>UE: Service Announcement (MBS session ID, wake-up times) + Note left of UE: At Wake up times UE starts reception + UE->>SMF: PDU session modify (Join MBS) + SMF->>MB-SMF: Nmbsmf_MBSSession_ContextStatusSubscribe (wake-up-time) + MB-SMF-->>SMF: PDU Session Modify Response (Join Ack (Wake Up Times)) + Note right of MB-SMF: At Wake up times MB SMF triggers activation + SMF->>AMF: Activate/Paging + AMF->>RAN: Multicast data + RAN->>UE: Multicast data + +``` + +Sequence diagram illustrating the procedure for periodic or one time transmission of MBS data to capability-limited devices. The diagram shows interactions between UE, RAN, AMF, SMF, MB-SMF, and AF. The process starts with AF sending an MBS session creation message to MB-SMF. MB-SMF stores the session configuration and sends a Service Announcement to the UE. The UE sends a PDU session modify (Join MBS) request to the SMF. The SMF sends an Nmbsmf\_MBSSession\_ContextStatusSubscribe to the MB-SMF. The MB-SMF sends a PDU Session Modify Response (Join Ack) to the SMF. The SMF sends an Activate/Paging message to the AMF. The AMF sends a Multicast data message to the RAN. The RAN sends a Multicast data message to the UE. Two dashed boxes indicate that at the configured wake-up times, the UE starts reception and the MB-SMF triggers activation. + +**Figure 6.25.3.1-1: Periodic or one time transmission of MBS data to capability-limited devices** + +If periodic transmissions are scheduled in an MBS session or the MBS session is set up for a one-time delivery, the devices may be informed in advance via service announcement or when it joins the MBS session about the time(s) when MBS data transmission will take place. The AF provides information about the time(s) when MBS data transmission will take place via NEF/MBSF to MB-SMF when configuring the multicast session. MB-SMF activates/deactivates multicast session based on configured times. The UEs start to receive MBS data at the configured times. + +### 6.25.3.2 Deferred activation for aperiodic transmission of MBS data to capability-limited devices + +![Sequence diagram illustrating the deferred activation for aperiodic transmission of MBS data to capability-limited devices. The diagram shows interactions between UE, RAN, AMF, SMF, MB-SMF, and AF. The process starts with MBS session creation and UE join. The AF sends a delayed activation request to the MB-SMF, which then sends a delayed activation request to the SMF. The SMF sends a delayed activation request to the AMF. The AMF performs paging at the eDRX paging time window for each idle UE. The UE sends a Service Request to the AMF, which responds with a NAS transfer (Activation time). The UE then sends a Release message. At the activation time, the UE starts reception of multicast data from the SMF.](c7e27041e661260fd0c8e89c763bb32e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant MB-SMF + participant AF + + Note left of UE: MBS session creation and UE join + AF->>MB-SMF: Delayed activation request(MBS session ID, Activation Time) + MB-SMF->>SMF: Delayed activation request(MBS session ID, Activation Time + list of idle UEs) + SMF->>AMF: Delayed activation request + Note left of UE: At eDRX paging time window for each idle UE + AMF->>UE: Paging + UE->>AMF: Service Request + AMF->>UE: NAS transfer (Activation time) + UE->>AMF: Release + Note left of UE: At activation time UE starts reception + SMF->>UE: Multicast data + +``` + +Sequence diagram illustrating the deferred activation for aperiodic transmission of MBS data to capability-limited devices. The diagram shows interactions between UE, RAN, AMF, SMF, MB-SMF, and AF. The process starts with MBS session creation and UE join. The AF sends a delayed activation request to the MB-SMF, which then sends a delayed activation request to the SMF. The SMF sends a delayed activation request to the AMF. The AMF performs paging at the eDRX paging time window for each idle UE. The UE sends a Service Request to the AMF, which responds with a NAS transfer (Activation time). The UE then sends a Release message. At the activation time, the UE starts reception of multicast data from the SMF. + +**Figure 6.25.3.2-1: Deferred activation for aperiodic transmission of MBS data to capability-limited devices** + +If an MBS session is used to transmit data at irregular intervals, the devices need to be informed about the data transmission while the MBS session is ongoing. The AF sends a delayed activation request indicating the desired activation time for an MBS session to the MB-SMF, and the MB-SMF request the SMFs to perform a delayed activation. The SMFs in turn request the AMFs to perform deferred paging. If UEs negotiated an eDRX cycle and joined the multicast session, the AMF pages the UE in the Paging Hyperframes (PH) / time intervals calculated according to eDRX procedures before the transmission start and indicates the transmission start time. + +### 6.25.4 Impacts on services, entities and interfaces. + +**Editor's note:** This clause describes impacts to existing services, entities and interfaces. + +#### AF: + +- Inform NEF about start times. +- Send delayed activation request indicating start time. +- Send MBS data at indicated times only. + +#### UE: + +- Receive and store start times via service announcement, join, or NAS transfer. +- wake up at indicated times. + +#### AMF: + +- For deferred activation, page UEs according to eDRX procedures and inform them about wakeup time. + +SMF: + +- Activate MBS session at indicated times. +- Forward request for deferred activation. + +## 6.26 Solution #26: AF selects UEs to be kept in connected mode + +### 6.26.1 Introduction + +This solution addresses Key Issues #1 and #6. + +### 6.26.2 Description + +This solution applies to active MBS sessions, and inactive MBS sessions. + +**Editor's note:** It is to be clarified whether and how this solution will be prevented to be applied to the UEs without joined MBS Sessions, due to no MBS related call flows involved in this solution. + +As outlined in clause 4.2, solutions shall enable simultaneous reception of MBS session data for a higher number of UEs in a cell than can be operating in RRC\_CONNECTED state, to participate in public safety group calls using MBS-based service. This requires that many such UEs transition to RRC-inactive state. On the other hand there are requirements for short reaction times for floor control requests and some participants in an MBS session may be so frequent talkers that a very frequent transition between RRC-Connected state and RRC\_INACTIVE state would burden the network, and it is thus desirable to keep such UEs in RRC\_CONNECTED state. + +For UEs in one or several MBS sessions, AF identifies UEs that should be kept in connected state, e.g. UEs of likely talkers in an MBS session such as dispatchers for public safety, and provides this information to CN as assistance information. The AF does this via Nnef\_ParameterProvision\_Create/Update service operations (see clause 4.15.6.2 of TS 23.502 [3]). The NEF only accepts related requests from authorized trusted AFs, e.g. related to public safety. + +**Editor's note:** It is FFS whether AF can identify UEs to be kept in RRC\_CONNECTED state or AF should provide priority information (which may cooperate with solutions for KI#1) for NG-RAN to determine RRC states. + +AF may use configuration or frequency of floor requests received from UE as criterion to select UEs and should only keep a small fractions of the UEs participating in an MBS session with many participants in connected state. + +**Editor's note:** Details how the AF selects a small fraction of UEs will need to be studied by SA6. + +**NOTE 1:** If the AF selects an excessive number of UEs for the connected state, this will limit the number of UEs that can receive an MBS multicast session and will also negatively impact the overall admission control of a RAN node. AF should remove information that UEs shall always be connected when related MBS session(s) end. The AF may also remove MBS UEs while the session is inactive for longer periods. + +**Editor's note:** Specifications under the SA6 remit might require updates to ensure that AF to remove information when related MBS session(s) ends. This requires collaboration with SA6 + +NEF stores in UDM users that preferably shall be kept connected. The NEF may restrict the number of UEs that an AF is allowed to suggest for connected state by rejecting requests with the number of UEs exceeding a preconfigured limit. + +**Editor's note:** It is to be clarified how the preconfigured limit can be determined in NEF. + +For each indicated UE, the UDM stores as part of the UE subscription data that user shall preferably be kept connected + +SMFs are notified about changes in UE subscription data based on previous subscription or inquire UE subscription data when PDU session is being established. This includes information that user shall preferably be kept connected. + +SMF provides the information that UE shall preferably be kept connected as part of the SM management information via AMF to NG RAN node handling the user. + +NG RAN nodes should keep UE for which such information was received and that are participating in at least one active multicast MBS session in RRC and CM connected state and may select to move other UEs to RRC Inactive or CM idle states if experiencing higher load, as long as this is feasible in its admission control. + +NOTE 2: The RAN does not need check whether the UE is participating in any MBS sessions, as the AF is expected to only select UEs in MBS sessions. + +Editor's note: How the RRC state is handled is to be determined by RAN WGs. + +As an additional improvement, UEs do not send "listener reports" while in MBS service area and in RRC inactive mode. Listener reports can become a problem in particular for UEs close to cell border moving frequently between cells. + +Editor's note: Coordination with SA6 is required on the implication that UEs do not send "listener reports" while in MBS service area and in RRC inactive mode. + +### 6.26.3 Procedures + +![Sequence diagram showing the procedure for AF selecting UEs to be kept in connected mode. The diagram involves six lifelines: NG RAN, AMF, SMF, UDM, NEF, and AF. The sequence starts with the AF identifying always connected users (1). The AF then sends an Nnef_ParameterProvision_Create/Update message to the NEF (2). The NEF sends an Nnef_ParameterProvision_Create/Update message to the UDM (3). The UDM sends a Nudm_SDM_Notify message to the SMF (4). The SMF sends an Nsmf_PDUSession_CreateSMContext Response or Nsmf_PDUSession_UpdateSMContext Response or Nsmf_PDUSession_SMContextStatusNotify message to the AMF (5). The AMF sends an N2 message to the NG RAN (6). The NG RAN keeps the UE in RRC connected state (7).](dde1a42ca58cd189901556a0cbfe7d57_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDM + participant SMF + participant AMF + participant NG_RAN as NG RAN + + Note right of AF: 1. Identify always connected users + AF->>NEF: 2. Nnef_ParameterProvision_Create/Update (always connected users) + NEF->>UDM: 3. Nnef_ParameterProvision_Create/Update (always connected users) + UDM->>SMF: 4. Nudm_SDM_Notify (userID, Keep connected) + SMF->>AMF: 5. Nsmf_PDUSession_CreateSMContext Response or Nsmf_PDUSession_UpdateSMContext Response or Nsmf_PDUSession_SMContextStatusNotify (N2 container( Keep connected)) + AMF->>NG_RAN: 6. N2 message (N2 container( Keep connected)) + Note left of NG_RAN: 7. Keep UE in RRC connected state + +``` + +Sequence diagram showing the procedure for AF selecting UEs to be kept in connected mode. The diagram involves six lifelines: NG RAN, AMF, SMF, UDM, NEF, and AF. The sequence starts with the AF identifying always connected users (1). The AF then sends an Nnef\_ParameterProvision\_Create/Update message to the NEF (2). The NEF sends an Nnef\_ParameterProvision\_Create/Update message to the UDM (3). The UDM sends a Nudm\_SDM\_Notify message to the SMF (4). The SMF sends an Nsmf\_PDUSession\_CreateSMContext Response or Nsmf\_PDUSession\_UpdateSMContext Response or Nsmf\_PDUSession\_SMContextStatusNotify message to the AMF (5). The AMF sends an N2 message to the NG RAN (6). The NG RAN keeps the UE in RRC connected state (7). + +Figure 6.26.3.2-1: AF selects UEs to be kept in connected mode + +1. AF identifies UEs to be kept in RRC connected state. +2. AF uses parameter provisioning procedure to provide UEs to be kept in connected state to NEF. +3. NEF stores in UDM users that preferably shall be kept connected. For each indicated UE, the UDM stores as part of the UE subscription data that user shall preferably be kept connected. +4. SMFs are notified about changes in UE subscription data based on previous subscription or inquire UE subscription data when PDU session is being established. This includes information that user shall preferably be kept connected. +- 5-6. SMF provides the information that UE shall preferably be kept connected as part of the SM management information via AMF to NG RAN node handling the user. +7. NG RAN nodes preferably keep UE for which such information was received in RRC and CM connected state. + +### 6.26.4 Impacts on services, entities and interfaces. + +#### AF: + +- Select UEs to be kept in connected mode and provide those UEs to CN via parameter provisioning procedure + +#### NEF/UDM/SMF + +- Updates to parameter provisioning procedure to transfer UEs to be kept in connected mode + +**SMF:** + +- Inform NG-RAN that UE shall be kept in connected state via PDU session modification + +**NG-RAN:** + +- Keep indicated UE in connected state + +**UE:** + +- Do not send listener reports while in MBS service area and inactive state + +## 6.27 Solution #27: AF providing list of prioritized UEs when creating multicast MBS Session + +### 6.27.1 Introduction + +This solution addresses the following bullet in Key Issue #1. + +- Whether, how and what MBS assistance information to provide from 5GC to RAN for an MBS session allowing UEs in CM-CONNECTED with RRC Inactive state to receive MBS content, including the aspect which 5GC NF(s) determine the MBS assistance information and how they do so. + +### 6.27.2 Functional description + +When the AF creates multicast MBS session, the AF may provide to the 5GC list of UEs (represented by GPSI) whether they're privileged or not within the multicast group. + +- NOTE 1: Compared to Solution#3 in clause 6.3.2, this solution carries the UE list of privileged users in the existing MBS Session creation message, while Solution#3 provide the privileged user information using PDU Session signalling triggered by PCC. +- NOTE 2: How to handle situations where different UEs are prioritized in different multicast groups is to be determined by RAN WGs. +- NOTE 3: The merits of providing a prioritized UE list related to a multicast session need to be discussed in the evaluation phase. +- NOTE 4: A UE involved in different multicast groups may be prioritized/privileged in one multicast group, but not prioritized/privileged in another group. +- NOTE 5: When the MBS session is handed over to non-MBS supporting RAN node, if the 5GC Individual Traffic delivery is applied, the MBS data will be transferred via PDU Session which requires the UE to be in RRC\_CONNECTED, therefore the UE differentiation proposed in this solution does not apply to non-supporting NG-RAN. + +The number of UEs to differentiate provided by AF is expected to be small. Exact number can be based on configuration, and in case the number exceeds the limit, the MB-SMF can do a throttling and include the list of dropped UEs in the response to the AF. + +- NOTE 6: The merits of selecting UEs to be dropped at the MB-SMF instead of the AF needs to be discussed in the evaluation phase. +- NOTE 7: For multicast MBS Session, in SMF, the list of UEs that have joined the MBS Session is included in MBS Session context which is shared by all UEs. In this solution, the SMF retrieves the list of prioritized UEs as part of MBS Session context information. It is possible that some prioritized UEs in the list are not handled by an SMF (if those UEs have not joined yet, or joined in other SMF(s)). Due to that, later if the list of UE is updated, the unrelated SMF also need be notified. + +When the 5GC provides the UE join information to the NG-RAN at UE join or MBS Session Activation, if the SMF has got information from MB-SMF that the UE is prioritized within the multicast group, the SMF provides such information to the NG-RAN to assist NG-RAN in its decision what UEs can be sent to RRC\_INACTIVE and continue receiving MBS data. + +### 6.27.3 Procedures + +In the existing procedure in clause 7.1.1.2 of TS 23.247 [4], step 8 & step 11 is enhanced as follows (**enhancement text in bold**): + +8. *AF of content provider may provide description for an MBS session (possibly providing information for a previously allocated TMGI to NEF via a Nnef\_MBSSession\_Create request ([MBS Session ID], service type, MBS information, [TMGI allocation indication]). If step 1-6 has not been executed before, the AF may provide a SSM or it may request that the network allocates an identifier for the MBS session (i.e. TMGI). The AF provides the service type (i.e. either multicast service or broadcast service). MBS session information may further include QoS requirements and Any UE indication (indicating whether a multicast MBS session is "open to any UEs"), MBS service area, start and end time of the MBS session and MBS session state (Active/Inactive). In addition, MBS information may also indicate whether the allocation of an ingress transport address is requested.* + +*If geographical area information or civic address information was provided by the AF as MBS service area, NEF/MBSF translates the MBS service area to Cell ID list or TAI list.* + +*For broadcast communication, the AF may determine MBS FSA ID(s) for the Broadcast MBS session based on business agreements and include them in the description of the MBS session* + +**For multicast MBS Session, the AF may provide a list of UEs that are to be differentiated (or prioritized) and those UEs are represented by GPSI.** + +... + +11. *NEF/MBSF sends Nmbsmf\_MBSSession\_Create Request (MBS Session ID, service type, TMGI allocation indication, MBS service area information, ingress transport address request indication) to MB-SMF, to request MB-SMF to reserve ingress resources for a MBS distribution session, The NEF/MBSF provides MBS Session ID or request allocation of a TMGI, and indicate the requested service type (either multicast service or broadcast service) and MBS session state (Active/Inactive). It also indicates that the allocation of an ingress transport address is requested if this was requested in step 8, or if the MBSF decides to insert an MBSTF into the user plane for the MBS session. The request also includes the Any UE indication if provided in step 8.* + +*The MBS service area is provided by NEF/MBSF to the MB-SMF if provided by the AF in step 8.* + +*MBS FSA ID(s) are provided by NEF/MBSF to the MB-SMF if provided by the AF in step 8.* + +*If requested to do so, or if a source specific multicast is provided as MBS Session ID in step 11, the MB-SMF allocates a TMGI.* + +*For broadcast communication, if no MBS FSA ID(s) have been received, the MB-SMF selects MBS FSA ID(s) for the Broadcast MBS session based on local configuration.* + +**For multicast MBS Session, the NEF/MBSF forward to the MB-SMF the list of UEs that are to be differentiated (or prioritized) if provided by the AF.** + +In the existing procedure in clause 7.2.1.3 of TS 23.247 [4], there is following enhancement (**enhancement text in bold**): + +3. *[Conditional] For each MBS session in step 1, if the SMF has not subscribed to the MBS Session Context, it invokes Nmbsmf\_MBSSession\_ContextStatusSubscribe request (MBS Session ID) towards the MB-SMF to subscribe to events notifications related to the multicast MBS session and to request information about the MBS Session Context. The MB-SMF responds with the information about the indicated multicast MBS session in Nmbsmf\_MBSSession\_ContextStatusSubscribe response (multicast QoS flow information (e.g. QoS profile(s) for the multicast MBS session), [start time], [session state (Active/Inactive)], [Any UE indication], [multicast DL tunnel info], **[List of prioritized UEs]**).* + +*If it is the first time for the MB-SMF to receive Nmbsmf\_MBSSession\_ContextStatusSubscribe request of the indicated MBS Session from any SMF, the MB-SMF learns it is the first UE joining the multicast MBS session. For multicast transport between MB-UPF and content provider, if it is the first UE joining the multicast MBS session, and MB-UPF has not joined the multicast tree in the MBS session creation procedure, described in clause 7.1.1, the MB-SMF requests the MB-UPF to join the multicast tree towards the AF/MBSF, otherwise MB-SMF will not send the request to the MB-UPF.* + +NOTE 2: The MB-SMF can answer the Nmbsmf\_MBSSession\_ContextStatusSubscribe request either based on information received in the MBS session creation procedures in clause 7.1.1 or based on preconfigured information. The pre-configuration also includes information about the MBS session stored in the NRF. If the MB-SMF uses preconfigured information, the pre-configuration also includes MB-UPF configuration. + +4. The SMF determines whether the user is authorized to join the Multicast MBS session taking into account the MBS subscription data received from the UDM and the Any UE indication if received from the MB-SMF. The SMF considers the UE as authorized to the Multicast MBS session if the UE is authorized to use multicast MBS services, and if the MBS Session ID(s) in the PDU Session Modification Request is included in the MBS subscription data or Any UE indication is received. If authorization check fails, the SMF rejects the join request with a cause value. If a UE joins prior to the start time of the multicast MBS session, the SMF may accept the join request and indicate to the UE the start time, or it may reject the join request with an appropriate error cause and optionally a back-off timer. If a UE joins while the multicast MBS session is inactive, the SMF accepts the join request. +5. If the join request is accepted, the SMF responds to the AMF through Nsmf\_PDUSession\_UpdateSMContext response (N2 SM information (PDU Session ID, MBS Session ID, [updated PDU Session information], [mapping information between unicast QoS flow(s) and multicast QoS flow(s)], [**assistant information of UE differentiation/prioritization**]), N1 SM container (PDU Session Modification Command)) to: + - create an MBS Session Context for the indicated MBS session in the RAN, if it does not exist in the RAN already; and + - inform the NG-RAN about the relation between the Multicast MBS Session Context and the UE's PDU Session context by including the MBS Session ID and the mapping between the multicast QoS flow(s) and associated QoS flow(s). + - **Inform NG-RAN the assistant information of UE differentiation (or prioritization).** + +Based on operator policy, the SMF may prepare for 5GC Individual MBS traffic delivery fall-back. The SMF maps the received QoS information of the multicast QoS Flow into PDU Session's unicast QoS Flow information, and includes the information of the QoS Flows and the mapping information about the QoS Flows (termed "associated QoS flow information") in the SM information sent to RAN. The SMF compares the QFIs of the multicast QoS Flows received from the MB-SMF with QFIs in use for the PDU Session and assigns unused QFIs to the PDU Session's unicast QoS Flows corresponding to multicast QoS Flows. + +... + +6. The N2 message, which includes the MBS Session ID(s) the UE has joined and, if applicable, associated QoS Flow, is sent to the NG-RAN. **The N2 message may also include information whether the UE is differentiated/prioritized to assist the NG-RAN when deciding what UEs can be sent to RRC\_INACTIVE and continue receiving MBS data.** + +If the MBS is supported by NG-RAN, 5GC Shared MBS traffic delivery is adopted. If the MBS is not supported by NG-RAN, 5GC Individual MBS traffic delivery is used if the PDU Session's unicast QoS Flow include QoS Flows for the multicast session. + +If the NG-RAN supports MBS, the NG-RAN uses the MBS Session ID to determine that the PDU Session identified by the PDU Session ID is associated with the indicated multicast MBS session. + +If the NG-RAN supports MBS, the associated unicast QoS flow information, if provided, is not used to allocate the radio resource and CN resource for corresponding QoS flows. + +NOTE 6: UE join request via PDU Session signalling will fail if NG-RAN rejects the PDU Session Resource setup request (e.g. due to the number of UEs reaching a limit). + +## 6.27.4 Impacts on services, entities and interfaces. + +AF: + +- Include new parameter with list of prioritized UEs (represented by GPSIs) that may assist the NG-RAN when determining to move the UEs when receiving MBS data to RRC\_INACTIVE. + +NEF (if deployed) + +- Forward the parameter of list of prioritized UEs to MB-SMF. + +MB-SMF: + +- Store the list of prioritized UEs (represented by GPSI) and provide the list to SMF when UE joins the multicast MBS Session. + +SMF: + +- If the UE differentiation information is provided by MB-SMF, the SMF provides the information to NG-RAN. + +NG-RAN: + +- The NG-RAN receives the UE differentiation information and may consider it when the NG-RAN determines whether to move the UE receiving MBS to RRC\_INACTIVE in PDU Session setup or modification. + +NOTE: How the group member information is used by NG-RAN is to be determined by RAN WGs. + +## 6.28 Solution #28: Session management and Mobility for RRC Inactive MBS data reception + +### 6.28.1 Introduction + +This solution addresses Key Issue #1, especially on the session management and mobility handling for RRC Inactive state UE MBS data reception. + +There are several assumptions for this solution: + +- In the RAN Notification Area for the UE, all the RAN nodes are homogeneously supporting the UE receiving the MBS data in RRC-inactive state +- The RAN Notification Area may span multiple RAN nodes. +- For the case, some RAN nodes within the RNA choose the delivery mode for connected mode reception and other RAN nodes choose the delivery mode for inactive mode reception for the MBS session: + - If the UE move from source node which deliver data in connected mode to target node which deliver the data in RRC Inactive mode, the target NG-RAN determine whether move the UE to RRC inactive reception. +- If the UE move from source node which deliver data in RRC inactive mode to target node which deliver the data in connected mode, how to move the UE to connected mode depend on the RAN WG decision. + +**Editor's note:** The assumption need to be confirmed by RAN WGs. + +### 6.28.2 Functional description + +The session management for the RRC inactive state UE receiving the multicast MBS session data, includes the following procedures/principle: + +- When the serving RAN node determines to move the UE into RRC Inactive state, it keeps the UE context and interacts with other RAN nodes in the RAN notification area. The serving RAN node forward the data received from shared delivery tunnel to other RAN nodes in the RAN notification area. The other RAN nodes need to send the multicast MBS session data in Uu. + +NOTE 1: Whether and how to prevent that multicast data are also transmitted in cells where no UE in the multicast session is located depend on RAN WG decision. + +NOTE 2: Whether and how the MBS RRC inactive assistant information is sent to RAN depends on other solution. + +- If both RAN nodes in the same RAN notification area have established the shared delivery tunnel for the multicast MBS session, they do not forward the MBS session data to each other according to the interaction. +- If RAN nodes in the same RNA area which does not establish the shared delivery tunnel, may receive the MBS data from one RAN node or multiple RAN nodes which have established the shared delivery tunnel . + +NOTE 3: how to prevent that such a RAN node receives multiple copies of the MBS data depend on RAN WG decision. + +- When the UE move to RRC connected mode, the procedure is specified in the TS 23.247 [4]. + +**Editor's note:** RAN node procedures and The Xn interaction will be determined by RAN WG. + +The mobility for the RRC inactive state UE receiving the multicast MBS session data, includes the following procedures/principle: + +- Moving within the RNA. The UE does not need to move into RRC connected mode. +- Moving out of RNA and within the RA. The UE perform the RNA update procedure as specified in the R17. +- Moving out of the RA. The UE perform mobility registration. The SMF provides the MBS session information to the RAN to establish the shared delivery tunnel or individual delivery tunnel. + +**Editor's note:** The functionality of this solution needs to be discussed and agreed in RAN WGs. + +## 6.28.3 Procedures + +### 6.28.3.1 Moving the UE to RRC Inactive mode + +**Editor's note:** The detailed solution will be defined by RAN WGs. + +This clause describes the NG-RAN moves the UE to RRC Inactive state. + +![Sequence diagram showing the procedure for moving a UE to RRC Inactive state. The diagram involves four main entities: UE, NG-RAN, NG-RANs in RNA, and MB-SMF/MB-UPF. The sequence of steps is: 1. UE receives multicast MBS data in RRC connected mode; 2. NG-RAN determines to move the UE to RRC Inactive mode; 3. NG-RAN informs other RAN nodes in the RNA to handle the MBS session for inactive UEs; 4. UE receives the multicast MBS session data in RRC Inactive state in the RNA area. A dashed arrow labeled 'Multicast MBS session data' points from the MB-SMF/MB-UPF to the NG-RANs in RNA.](605625ddfc3363a6205ab0d43b184eaf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant NG-RANs in RNA + participant MB-SMF/MB-UPF + + Note right of UE: 1. UE receives the multicast MBS data in RRC connected mode + Note right of NG-RAN: 2. NG-RAN determines to move the UE to RRC Inactive mode + Note right of NG-RANs in RNA: 3. NG-RAN informs other RAN nodes in the RNA to handle the MBS session for inactive UEs + Note right of UE: 4. UE receives the multicast MBS session data in RRC Inactive state in the RNA area + + MB-SMF/MB-UPF-->>NG-RANs in RNA: Multicast MBS session data + +``` + +Sequence diagram showing the procedure for moving a UE to RRC Inactive state. The diagram involves four main entities: UE, NG-RAN, NG-RANs in RNA, and MB-SMF/MB-UPF. The sequence of steps is: 1. UE receives multicast MBS data in RRC connected mode; 2. NG-RAN determines to move the UE to RRC Inactive mode; 3. NG-RAN informs other RAN nodes in the RNA to handle the MBS session for inactive UEs; 4. UE receives the multicast MBS session data in RRC Inactive state in the RNA area. A dashed arrow labeled 'Multicast MBS session data' points from the MB-SMF/MB-UPF to the NG-RANs in RNA. + +**Figure 6.28.3.1-1: NG-RAN node moves a UE to RRC Inactive state** + +1. The UE has joined the multicast MBS session and is receiving the MBS data in CM-CONNECTED with RRC connected mode. +2. NG-RAN determines to move the UE to RRC Inactive mode. + +NOTE: Whether and how the MBS RRC inactive assistant information is sent to RAN depends on other solution. + +3. The NG-RAN interact with other RAN nodes in the RNA area to handle the multicast MBS session for inactive UEs in the RNA area. + +When the NG-RAN receives the multicast MBS data, it forward to other RAN nodes in the RNA area. + +4. All the NG-RAN nodes in the RNA area provide the Multicast MBS data in the RNA. + +### 6.28.3.2 Mobility within/out of RNA area. + +**Editor's note:** The detailed solution will be defined by RAN WGs. + +When the UE moves within the RNA area, it does not need to access to the new RAN node to receive the MBS data if the UE has joined the multicast MBS session. + +The UE may access to the new RAN node in several scenario: + +- Within RNA. +- Out of RNA. + +If the new RAN node retrieves the UE context successfully, it may established the shared delivery tunnel and initiates the path switch to SMF. + +If the new RAN node fails to retrieve the UE context, the new NG-RAN establish the RRC connection with UE. The UE initiate the mobility registration or service request. The SMF send the MBS session information to NG-RAN via N2 to establish the shared delivery tunnel and radio resource. + +![Sequence diagram illustrating the successful retrieval of UE context during an RNA update.](468be155058fd5d2862919eb8ec35496_img.jpg) + +``` +sequenceDiagram + participant UE + participant Target RAN + participant Source RAN + participant AMF + participant SMF/UPF + participant MB-SMF/MB-UPF + + Note right of Target RAN: 2. retrieve the UE context from source RAN + Note right of SMF/UPF: 3. shared delivery tunnel establishment + + UE->>Target RAN: 1. RNA update + Target RAN->>Source RAN: 2. retrieve the UE context from source RAN + Note right of Target RAN: 3. shared delivery tunnel establishment + Target RAN->>AMF: 4. Path switch + AMF->>SMF/UPF: 5. PDU session update + SMF/UPF->>Target RAN: 6. Path switch ACK +``` + +The diagram shows a sequence of interactions between a UE, Target RAN, Source RAN, AMF, SMF/UPF, and MB-SMF/MB-UPF. The process starts with the UE sending an 'RNA update' to the Target RAN. The Target RAN then sends a request to the Source RAN to 'retrieve the UE context from source RAN'. A dashed box labeled '3. shared delivery tunnel establishment' encompasses the subsequent steps. The Target RAN sends a 'Path switch' message to the AMF. The AMF sends a 'PDU session update' to the SMF/UPF. Finally, the SMF/UPF sends a 'Path switch ACK' back to the Target RAN. + +Sequence diagram illustrating the successful retrieval of UE context during an RNA update. + +**Figure 6.28.3.2-1: retrieve the UE context successfully** + +The UE(s) joined the multicast MBS session and is receiving the multicast service in RRC-inactive state. + +1. If UE need to access to the new RAN node, it initiate the RNA update to target RAN. +2. The target NG-RAN retrieve the UE context from source RAN including MBS session information. +3. The target NG-RAN may initiate the shared delivery method establishment procedure as specified in TS 23.247 [4]. + +Steps 4~6. The path switch procedure is triggered. The SMF provides the MBS information to NG-RAN as specified in TS 23.247 [4]. + +NOTE: Whether and how the MBS RRC inactive assistant information is sent to RAN depends on other solution. + +![Sequence diagram illustrating the failure to retrieve the UE context during a multicast service session. The diagram shows interactions between UE, Target RAN, Source RAN, AMF, SMF/UPF, and MB-SMF/MB-UPF. The sequence starts with an RNA update from UE to Target RAN. The Target RAN fails to retrieve the UE context from the Source RAN. The UE then sends an RRCSetup message to the Target RAN. The Target RAN sends a Registration/Service Request to the AMF. The AMF sends a PDU session update to the SMF/UPF. The SMF/UPF sends an N2 Request to the Target RAN. Finally, a shared delivery tunnel establishment is shown as a dashed box involving the Target RAN, Source RAN, AMF, SMF/UPF, and MB-SMF/MB-UPF.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target RAN + participant Source RAN + participant AMF + participant SMF/UPF + participant MB-SMF/MB-UPF + + Note right of Target RAN: 2. fail to retrieve the UE context from source RAN + + UE->>Target RAN: 1. RNA update + Target RAN-->>UE: 3. RRCSetup + UE->>AMF: 4. Registration/Service Request + AMF->>SMF/UPF: 5. PDU session update + SMF/UPF->>Target RAN: 6. N2 Request + Note right of SMF/UPF: 7. shared delivery tunnel establishment + +``` + +Sequence diagram illustrating the failure to retrieve the UE context during a multicast service session. The diagram shows interactions between UE, Target RAN, Source RAN, AMF, SMF/UPF, and MB-SMF/MB-UPF. The sequence starts with an RNA update from UE to Target RAN. The Target RAN fails to retrieve the UE context from the Source RAN. The UE then sends an RRCSetup message to the Target RAN. The Target RAN sends a Registration/Service Request to the AMF. The AMF sends a PDU session update to the SMF/UPF. The SMF/UPF sends an N2 Request to the Target RAN. Finally, a shared delivery tunnel establishment is shown as a dashed box involving the Target RAN, Source RAN, AMF, SMF/UPF, and MB-SMF/MB-UPF. + +**Figure 6.28.3.2-2: fail to retrieve the UE context** + +The UE(s) joined the multicast MBS session and is receiving the multicast service in RRC-inactive state. + +1. If UE need to access to the new RAN node, it initiate the RNA update to target RAN. +2. The target NG-RAN fail to retrieve the UE context from source RAN. +3. RRC connection is established. +4. The UE initiate the Registration or Service Request procedure with PDU session status IE to activate the associated PDU session. +- 5-6. The SMF provides the MBS information to NG-RAN as specified in TS 23.247 [4]. + +NOTE: Whether and how the MBS RRC inactive assistant information is sent to RAN depends on other solution. + +## 6.28.4 Impacts on services, entities, and interfaces + +UE: + +- When the UE receives the MBS data in RRC Inactive state and need to access to a new RAN node, the UE need activate the associated PDU session via the service request or registration procedure if RRC connection need to be established. + +NG-RAN: + +- The serving RAN interact with other RAN nodes in the RNA area to handle the multicast MBS session for inactive UEs in the RNA area. +- As the user plane anchoring point to forward the MBS data to other RAN node in the RNA area. + +**Editor's note:** The impact of NG-RAN need to be confirmed by RAN WGs. + +## 6.29 Solution #29: MOCN network sharing with a single TMGI + +### 6.29.1 Introduction + +This solution addresses Key Issues #2. + +The present solution aims to use a single TMGI to minimize the required updates and to avoid that multiple TMGIs for the same multicast data are broadcasted over the radio to save bandwidth. + +TMGIs contain a mobile country code (MCC) and mobile network code (MNC). For MOCN network sharing, if a single TMGI is used, core networks will need to accept TMGIs with a MNC of a different CN. While existing stage 2 + +procedures do not rule out such behaviour, many existing deployments will likely reject MBS session creation requests with such TMGIs and it is suggested to use an MOCN signalling flag to request a different behaviour. + +### 6.29.2 Description + +One TMGI is reserved for the MBS broadcast data for which MOCN network sharing applies. It is selected by the involved AF(s) and made known to all AFs performing service announcements for the MBS data and is used as part of those service announcements. For instance, one AF can be tasked by configuration to request the primary TMGI and share it with the other involved AFs. + +If an AF contacts a NEF to create an MBS broadcast session for which MOCN network sharing applies, it provides the TMGI and an indication that MOCN network sharing applies. If the NEF/MBSF receives an MBS session create request with an MOCN network sharing indicator and an TMGI including a MNC (Mobile network code) that is not identical to the MNC of the network including the NEF/MBSF, the NEF/MBSF checks configured data whether there is a network sharing agreement with the network indicated by the MNC, and if so accepts the request to create the MBS session, but selects the MB-SMF not based on the TMGI but based on the service area. + +The TMGI and the indication that MOCN network sharing applies are included in messages to establish the broadcast session from MB-SMF via AMF towards the NG-RAN node. Based on the indication that MOCN network sharing applies, the NG RAN node checks whether there are additional MBS sessions with the same TMGI and identifies the correlated MBS sessions via the same TMGI. For the identified correlated sessions, the NG RAN broadcast related data only once over the radio. the NG RAN nodes checks if it already receives data for the broadcast session for any of the correlated sessions and if so does not provide a downlink tunnel endpoint and does send a lower layer join request. + +**Editor's note:** It is to be confirmed by RAN WGs whether different MBS broadcast sessions from different CNs should share the same TMGI, which was used to identify one MBS broadcast session in Rel-17, except for location dependent MBS, area session ID needs be considered together. + +If an MBS RAN node receives a request to release an MBS session for broadcast, it checks whether there are still correlated MBS sessions. If so, the RAN node continues to broadcast data for the MBS session over the radio. The NG RAN checks if it requested to receive MBS data from the core for the MBS session that is to be released. If so, the NG RAN node sends a request for another of the correlated MBS sessions to receive the MBS data from the related core network. + +### 6.29.3 Procedures + +![Sequence diagram for MBS session creation for MOCN network sharing. Lifelines: UE, MB-SMF, NEF/MBSF, AF. The sequence starts with AF determining a TMGI for MBS session with MOCN network sharing. Then AF sends a service announcement with TMGI to NEF/MBSF. NEF/MBSF sends an Nnnef_MBSSession_Create request (TMGI, MOCN network sharing, MBS service area) to MB-SMF. MB-SMF checks if TMGI contains external MNC and if network sharing is authorized. If so, it does not select MB-SMF based on TMGI. Finally, MB-SMF sends an Nmbsmf_MBSSession_Create Request (TMGI, MOCN network sharing) to UE. The diagram also shows a step 1: TMGI allocation: In one CN MB SMF assigns TMGIs to AF and step 7: Interactions in subsequent flow.](8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant MB-SMF + participant UE + + Note right of AF: 2. Determine TMGI for MBS session with MOCN network sharing + AF->>NEF/MBSF: 3. Service announcement, TMGI + Note right of NEF/MBSF: 4. Nnnef_MBSSession_Create Request (TMGI, MOCN network sharing, MBS service area) + Note right of NEF/MBSF: 5. If TMGI contains external MNC: Check if network sharing with MNC is authorized. Do not select MB-SMF based on TMGI + NEF/MBSF->>MB-SMF: 6. Nmbsmf_MBSSession_Create Request (TMGI, MOCN network sharing) + Note left of MB-SMF: 7. Interactions in subsequent flow + +``` + +Sequence diagram for MBS session creation for MOCN network sharing. Lifelines: UE, MB-SMF, NEF/MBSF, AF. The sequence starts with AF determining a TMGI for MBS session with MOCN network sharing. Then AF sends a service announcement with TMGI to NEF/MBSF. NEF/MBSF sends an Nnnef\_MBSSession\_Create request (TMGI, MOCN network sharing, MBS service area) to MB-SMF. MB-SMF checks if TMGI contains external MNC and if network sharing is authorized. If so, it does not select MB-SMF based on TMGI. Finally, MB-SMF sends an Nmbsmf\_MBSSession\_Create Request (TMGI, MOCN network sharing) to UE. The diagram also shows a step 1: TMGI allocation: In one CN MB SMF assigns TMGIs to AF and step 7: Interactions in subsequent flow. + +Figure 6.29.3-1: MBS session creation for MOCN network sharing + +- 1. AF may request TMGI(s) + +2. The same TMGI is used for all related MBS broadcast sessions where MOCN network sharing applies. If multiple AFs are involved and provide data for an MBS broadcast session with MOCN network sharing, the AFs coordinate to use the same TMGI. For instance, one AF may be tasked by configuration to request the TMGI, and to share it with the other involved AFs. The TMGI may also be provided as configuration to all involved AFs. +3. The TMGI is provided as part of the service announcement for the MBS session by all AFs performing service announcements for the MBS session. + +The following steps are executed for each CN involved in the network sharing: + +4. AF sends a request to create an MBS session, which includes TMGI, MOCN network sharing indicator, and a service area to NEF/MBSF and an identifier of the broadcast MBS service. +5. Due to the MOCN network sharing indicator, if the NEF/MBSF receives an TMGI including a MNC (Mobile network code) that is not identical to the MNC of the network including the NEF/MBSF, the NEF/MBSF checks configured data whether there is a network sharing agreement with the network indicated by the MNC, and if so accepts the request to create the MBS session. In addition, the NEF/MBSF selects the MB-SMF not based on the TMGI but based on the service area. +6. The NEF/MBSF forwards the request to create an MBS session to the MB-SMF. MB-SMF accepts TMGIs with external MNC based on network sharing indicator. +7. Interactions as described in Figure 6.29.3-2. + +![Sequence diagram for Broadcast Session start for MOCN NG-RAN. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with TMGI allocation and MBS Session Create (see previous flow) from AF to MB-SMF. Then, Namf_MBSBroadcast_ContextCreate Request is sent from MB-SMF to AMF. AMF sends an N2 message Request to NG-RAN. NG-RAN creates MBS Session context and identifies related contexts. NG-RAN sends IGMP/MLD join to MB-UPF. MB-UPF sends N2 message Response to AMF. AMF sends Namf_MBSBroadcast_ContextCreate Response to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. NG-RAN advertises TMGI and sends MBS data only one time. AMF sends N2 message Response to NG-RAN. AMF sends Namf_MBSBroadcast_ContextsStatusNotify Request to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. Media stream is sent from AF to MB-UPF to MB-SMF to NG-RAN to UE via PTM transmission.](e20792fef9de6560b2d6c5441da7614a_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF/MBSF + participant MB-SMF + participant PCF + participant MB-UPF + participant AMF + participant NG-RAN + participant UE + + Note right of AF: 1. TMGI allocation and MBS Session Create: see previous flow + AF->>MB-SMF: 2. Namf_MBSBroadcast_ContextCreate Request (TMGI, MOCN Network sharing, LL SSMA, 5G Authorized QoS Profile, MBS service area) + MB-SMF->>AMF: 3. N2 message Request (TMGI, MOCN Network sharing, LL SSMA, QoS Profile, MBS service area,) + AMF->>NG-RAN: 4. MBS Session context created Identify related contexts based on same TMGI. + NG-RAN->>MB-UPF: 5. IGMP/MLD join + MB-UPF->>AMF: 6. N2 message Response (TMGI, N3mb DL Tunnel info) + AMF->>MB-SMF: 7. Namf_MBSBroadcast_ContextCreate Response () + MB-SMF->>MB-UPF: 8. N4mb Session Update (TMGI, N3mb DL Tunnel Info) + NG-RAN->>UE: 9. NG-RAN advertises TMGI and sends MBS data only one time. + AMF->>NG-RAN: 10. N2 message Response (TMGI, N3mb DL Tunnel) + AMF->>MB-SMF: 11. Namf_MBSBroadcast_ContextsStatusNotify Request () + MB-SMF->>MB-UPF: 12. N4mb Session Update (TMGI, N3mb DL Tunnel) + AF->>MB-UPF: 13. Media stream + MB-UPF->>MB-SMF: 14. Media stream + MB-SMF->>NG-RAN: 15. PTM transmission + NG-RAN->>UE: 15. PTM transmission + +``` + +Sequence diagram for Broadcast Session start for MOCN NG-RAN. The diagram shows interactions between UE, NG-RAN, AMF, MB-SMF, MB-UPF, PCF, NEF/MBSF, and AF. The process starts with TMGI allocation and MBS Session Create (see previous flow) from AF to MB-SMF. Then, Namf\_MBSBroadcast\_ContextCreate Request is sent from MB-SMF to AMF. AMF sends an N2 message Request to NG-RAN. NG-RAN creates MBS Session context and identifies related contexts. NG-RAN sends IGMP/MLD join to MB-UPF. MB-UPF sends N2 message Response to AMF. AMF sends Namf\_MBSBroadcast\_ContextCreate Response to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. NG-RAN advertises TMGI and sends MBS data only one time. AMF sends N2 message Response to NG-RAN. AMF sends Namf\_MBSBroadcast\_ContextsStatusNotify Request to MB-SMF. MB-SMF sends N4mb Session Update to MB-UPF. Media stream is sent from AF to MB-UPF to MB-SMF to NG-RAN to UE via PTM transmission. + +Figure 6.29.3.2-2: Broadcast Session start for MOCN NG-RAN + +1. See Figure 6.29.3-1. +2. Same as in Figure 7.3.1-1 of TS 23.247 [4]. A MOCN network sharing indicator is included. AMF accepts TMGIs with external MNC based on network sharing indicator. +3. Same as in Figure 7.3.1-1 of TS 23.247 [4]. A MOCN network sharing indicator is included. +4. Based on the MOCN network sharing indicator, the NG RAN node checks whether there are additional MBS sessions with the same TMGI and identifies the correlated MBS sessions via the same TMGI. + +5. If the NG RAN node does not yet receive data for the broadcast session, and if the NG-RAN node is configured to use multicast transport, NG-RAN node sends an IGMP/MLD join request for the LL SSMA received in step 2. +6. As in Figure 7.3.1-1 of TS 23.247 [4]. If the NG RAN node does not yet receive data for the broadcast session, and if the NG-RAN node is configured to use unicast transport, NG-RAN node provides a N3mb DL Tunnel endpoint in the N2 message response. + +**Editor's note:** Details will be confirmed by the RAN WGs. + +7. As in Figure 7.3.1-1 of TS 23.247 [4]. +8. As in Figure 7.3.1-1 of TS 23.247 [4]. +9. For the identified correlated sessions, the NG RAN broadcast related data and the related TMGI only once over the radio. +- 10-15. As in Figure 7.3.1-1 of TS 23.247 [4]. + +![Sequence diagram titled 'Broadcast Session release for MOCN NG-RAN'. The diagram shows the interaction between a UE, NG-RAN, and two Core Networks (CN 1 and CN 2). CN 1 contains AMF 1, MB-SMF 1+ MB-UPF 1, NEF 1, and AF 1. CN 2 contains AMF 2, MB-SMF 2+ MB-UPF 2, NEF 2, and AF 2. The sequence starts with the UE sending data for correlated MBS broadcast sessions to the NG-RAN. The NG-RAN sends a 'Nsmf_MBSSBroadcast_ContextRelease Request (TMGI)' to AMF 1. AMF 1 sends a 'Delete Broadcast session' message to NEF 1. NEF 1 sends 'MBS data' to AF 1. AMF 1 then sends an 'N2 message(TMGI, N2Container(N3mb DL Tunnel))' to the NG-RAN. The NG-RAN checks for other correlated MBS sessions. If none, it sends 'Send data for correlated MBS broadcast sessions only one time' to the UE. If there are other sessions, it continues broadcasting. The NG-RAN also sends 'MBS data' to AMF 2. AMF 2 sends 'Nsmf_MBSSBroadcast_ContextStatusNotify (TMGI, N2Container)' to NEF 2. NEF 2 sends 'Configure MB-UPF2 to send MBS data to N3mb DL Tunnel' to AMF 2. AMF 2 then sends 'MBS data' to AF 2. Finally, the NG-RAN sends 'Send data for correlated MBS broadcast sessions only one time' to the UE again.](d9d09655eb4282168769ac97178db50c_img.jpg) + +Sequence diagram titled 'Broadcast Session release for MOCN NG-RAN'. The diagram shows the interaction between a UE, NG-RAN, and two Core Networks (CN 1 and CN 2). CN 1 contains AMF 1, MB-SMF 1+ MB-UPF 1, NEF 1, and AF 1. CN 2 contains AMF 2, MB-SMF 2+ MB-UPF 2, NEF 2, and AF 2. The sequence starts with the UE sending data for correlated MBS broadcast sessions to the NG-RAN. The NG-RAN sends a 'Nsmf\_MBSSBroadcast\_ContextRelease Request (TMGI)' to AMF 1. AMF 1 sends a 'Delete Broadcast session' message to NEF 1. NEF 1 sends 'MBS data' to AF 1. AMF 1 then sends an 'N2 message(TMGI, N2Container(N3mb DL Tunnel))' to the NG-RAN. The NG-RAN checks for other correlated MBS sessions. If none, it sends 'Send data for correlated MBS broadcast sessions only one time' to the UE. If there are other sessions, it continues broadcasting. The NG-RAN also sends 'MBS data' to AMF 2. AMF 2 sends 'Nsmf\_MBSSBroadcast\_ContextStatusNotify (TMGI, N2Container)' to NEF 2. NEF 2 sends 'Configure MB-UPF2 to send MBS data to N3mb DL Tunnel' to AMF 2. AMF 2 then sends 'MBS data' to AF 2. Finally, the NG-RAN sends 'Send data for correlated MBS broadcast sessions only one time' to the UE again. + +**Figure 6.29.3.2-3: Broadcast Session release for MOCN NG-RAN** + +If NG-RAN receives a request to release an MBS session for broadcast, NG-RAN checks if there are other correlated MBS sessions. If there are correlated MBS sessions, NG-RAN continues to broadcast data for the MBS session over the radio. NG-RAN checks if it requested to receive MBS data from the core via the MBS session that is to be released. If so, NG-RAN sends a request via another of the correlated MBS sessions to receive the MBS data to the related core network. If the NG-RAN is configured to use unicast transport, it sends an N2 message indicating the TMGI and N3mb downlink (DL) tunnel information. If the NG-RAN 430 is configured to use multicast transport, it may transmit an IGMP/MLD join request for the IP SSMA received in a previous request of the other correlated MBS session. + +**Editor's note:** Details will be confirmed by the RAN WGs. + +## 6.29.4 Impacts on services, entities and interfaces + +### AF: + +- Use same TMGI for all correlated MBS broadcast sessions with MOCN network sharing; +- Indicate network sharing in request to create MBS session. + +### NEF/MBSF: + +- Authorize create request for MOCN network sharing with TMGI with external MNC; +- Select MB-SMF based on service area instead of TMGI. + +#### MB-SMF and AMF: + +- Accept TMGI with external MNC. + +#### NG RAN: + +- identify correlated MBS sessions; +- Broadcast TMGI and data for correlated MBS session only once; +- Select one correlated session to request data for MBS session. + +## 6.30 Solution #30: On demand multicast MBS session set up by MB-SMF + +### 6.30.1 Introduction + +This solution addresses Key Issues #3. + +TS 23.247 [4] already provides some support for on-demand multicast sessions in Rel-17: + +- An AF can create a multicast session at any time, e.g. when noticing demand. +- A multicast session may be established without prior creation by an AF when a UE tries to join it: If no MB-SMF is assigned for the MBS session ID (i.e. the NRF provides empty MB-SMF profile), the SMF may select an MB-SMF and request it to configure the multicast MBS session. However, details are left to SMF implementation. + +The present solution avoids the need for an AF to establish the multicast session and fills related gaps that are left to implementation in Rel-17. It allows to have preconfigured policies for such on-demand multicast sessions. It allows to determine whether to establish a multicast session towards the radio based on the number/frequency/location of join requests. + +The present solution enables that an MBS session for an external IP multicast session is established: + +- (a) either when the first UE within the PLMN request to join that IP multicast session; or +- (b) when multiple UE within the same PLMN have requested to join that IP multicast session + +NOTE 1: Whether Option (b) is required and its merits will be further discussed as part of the evaluation. + +The present solution also enables UEs to receive data from an IP multicast session even if the network does not establish the multicast session towards the radio: + +Operators may want to enable UEs to join an external IP multicast session via a normal PDU session while not setting up an MBS session in their network. An application on the UE would likely send IGMP join requests to join such external IP multicast sessions. As discussed in Rel-17, this IGMP join request in the user plane will likely be converted to CP join request by the UE protocol stack. If that join request is rejected, the UE is not able to join a multicast session at all. To enable a UE to join, a user plane join request would need to be generated by the UPF, and the UPF also needs to be configured to forward received related multicast packets to the UE. (Even if a UPF receives a UP IP join request and forwards the request, the UE would not receive related multicast packets without special UPF procedures or configuration to forward them.) + +One could also consider a decentral solution to enable UEs to join an external IP multicast session where each SMF configures the related UPF separately. However, this complicates a subsequent full establishment of an MBS session for the multicast IP session and also makes it hard for an operator to observe that there are many UEs joining the same external IP multicast session. The immediate assignment of an MB-SMF and MB-UPF is meant to enable a subsequent conversion to a full IP multicast session and also provides means to monitor whether many UEs join an external multicast session. + +**Editor's note:** More clarification and evaluation is required on the benefits of applying individual delivery versus immediately establishing the MBS session towards the radio as in the Rel-17 existing mechanisms, especially in the scenario of the second bullet above. + +This solution focuses on IP multicast sessions (using the IGMP protocol for joining and source specific multicast addresses as identifiers) provided by an application server in the internet that does not directly interact with the 5GS. It enables the 5GS to dynamically detects that many UEs join the same IP multicast sessions and based on that set up a related MBS multicast session to save transmission resources. + +The following related issues need to be resolved: + +- How to enable UEs to join multicast IP sessions if no related MBS session exists in the network. +- How to detect that multiple UEs join the same multicast IP session (possibly at high rate or in proximity to each other). +- How to establish a related on-demand MBS session based on the detection. +- How to inform the UEs to join the on-demand MBS session established in step 3. + +NOTE 2: This solutions is only applicable if a source specific IP multicast address is used as MBS session ID. + +NOTE 3: This solutions allows that QoS for a multicast session is preconfigured by the operator, e.g. based on a SLA with a service provider. If there is no such preconfigured information, only a default QoS will be provided for the 5MBS session. + +NOTE 4: Only CP join requests are supported. IP applications on the UE can either use that join method, or the protocol stack in the UE can convert IGMP join requests to CP join requests. + +## 6.30.2 Description + +If the SMF receives a join request for a source specific IP multicast address with no MB-SMF assigned, the SMF assigns an MB-SMF and informs it that a join request for the source specific multicast address was received and about the location of the UE that issued a join request. The MB-SMF decides based on operator policy and possibly based on PCF interactions to inquire predefined information about policies for the source specific IP multicast address in the UDR whether the join request shall be accepted and whether to establish the MBS session towards the radio, and informs the SMF about those decisions. Based on operator policy, the MB-SMF may immediately establish the MBS session towards the radio when the first UE joins or wait until more UEs join the join request for a source specific IP multicast address. + +If the MB-SMF decides to accept the join request, the MB-SMF registers itself at the NRF as handling the source specific multicast address, and configures the MB-UPF to send an IGMP join request for the source specific IP multicast address towards the external network and to receive related data, irrespective of whether it decides whether to establish the MBS session towards the radio. + +If the MB-SMF decides not to accept the join request, the SMF rejects the join request. + +If the MB-SMF decides to establish the MBS session towards the radio, normal MBS multicast procedures apply from that point onwards. + +If the MB-SMF decides not to establish the MBS session towards the radio, the SMF also informs the MB-SMF about subsequent join request for the same IP multicast request until the MB-SMF decides to establish the multicast session towards the radio. + +If the MBS session is not to be established towards the radio, the SMF does not add MBS session information to the PDU session but still accepts the join request. Individual delivery is then used towards that UE. + +If the MB-SMF does not establish the MBS session towards the radio, it will then be informed by SMFs about subsequent join attempts for this source specific multicast address, and can then decide to establish the MBS session towards the radio. The MB-SMF may count the number or log the join requests to determine their frequency and/or whether the attempts are concentrated in a specific area in order to decide whether to establish the MBS session, and in order to determine a service area for the MBS session. It can interact with the PCF to check whether the multicast session can be authorized. The PCF can consider the area and the load in the area for a related decision. The PCF can contact the UDR to check whether there is preconfigured policy for a multicast session with the specific source specific multicast address. + +The MB-SMF stores the SMFs that subscribed to info about the MBS session. It notifies those SMFs when it decides to establish the MBS session towards the radio. The SMFs then update the PDU sessions of related UEs with the MBS session information. + +**Editor's note:** It is to be clarified the benefit of applying individual delivery, instead of shared delivery when the first (a few) UEs join the MBS session. + +To enable a UE to receive an IP multicast sessions within a PDU session if no related MBS session towards the radio is established, an IGMP join requests needs to be send towards the IP network. In Rel-17 it was assumed that a UE would only send join request in the control plane signalling. It was anticipated that the protocol stack in the UE could recognise IGMP join requests in the user plane and convert them to control plane join requests. An MB-SMF that it is informed about a join attempt for an IP SSMA with no related MBS session and decides not to establish the MBS session configures the MB-UPF to send an IGMP join request. + +## 6.30.3 Procedures + +![Sequence diagram showing the procedure for a UE to join an IP SSMA when the related MBS session is not yet created. The diagram involves 10 lifelines: UE, NG-RAN, AMF, SMF, UPF, NRF, MB-UPF, MB-SMF, PCF, and UDR. The process starts with a UL NAS message from the UE to the AMF, followed by a series of requests and responses between the AMF, SMF, NRF, MB-SMF, PCF, and UDR. The SMF then initiates the establishment of 5GC Individual MBS traffic delivery, which involves multiple steps between the SMF, UPF, and MB-SMF. Finally, multicast data is transmitted from the UPF to the UE via the PDU Session.](b30e390cb591b39482fe7ecd4c4cd84b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant NRF + participant MB-UPF + participant MB-SMF + participant PCF + participant UDR + + Note left of UE: 1a. UL NAS message (N1 SM container) (PDU Session Modification Request: join IP SSMA) + UE->>AMF: 1a. UL NAS message (N1 SM container) (PDU Session Modification Request: join IP SSMA) + AMF->>SMF: 1b. Nsmf_PDUSession_UpdateSMContext request (UE location, NI container) + SMF->>NRF: 2. Nnrf_NFDiscovery request/response + SMF->>MB-SMF: 3. Nmbsmf_MBSSession_ContextStatusSubscribe request(IP SSMA, UE Location) + MB-SMF->>PCF: 4. Npcf_MBSPolicyControl request (IP SSMA, location) + PCF-->>MB-SMF: 5. Inquire possible predefined policies for SSMA + MB-SMF-->>PCF: 6. Npcf_MBSPolicyControl response (QoS) + Note right of MB-SMF: 7. For IP SSMA: Decide whether to create MBS radio session, Log join request + MB-SMF->>UPF: 8. Create N4 Session For IP SSMA + UPF->>UDR: 9. IGMP join (IP SSMA) + UPF->>NRF: 10. Update profile (IP SSMA) + MB-SMF-->>SMF: 11. Nmbsmf_MBSSession_ContextStatusSubscribe response (No MBS radio session establishment, QoS Info) + SMF->>AMF: 12. Nsmf_PDUSession_UpdateSMContext response (no MBS session info, QoS Flow) + AMF->>NG-RAN: 13. N2 message request + NG-RAN->>UE: 14. RRC message (PDU Session Modification command) + + Note right of SMF: Establishment of 5GC Individual MBS traffic delivery + SMF-->>UPF: 15A N4 Session Modification + Note right of SMF: Setup unicast transport or request multicast DL tunnel info for multicast transport + SMF->>MB-SMF: 15b. Nmbsmf_MBSSession_ContextUpdate request + MB-SMF-->>SMF: 15c. N4mb Session Modification/Create + SMF-->>UPF: 15d. Nmbsmf_MBSSession_ContextUpdate response + SMF-->>UPF: 15e. N4 Session Modification + + Note right of UPF: Transmission via 5GC Individual MBS traffic delivery + UPF->>UE: 16. Multicast data + UPF->>NG-RAN: 17. Multicast data + NG-RAN->>UE: 18. Multicast data via PDU Session + UE->>NG-RAN: 19. Multicast data via PDU Session + +``` + +Sequence diagram showing the procedure for a UE to join an IP SSMA when the related MBS session is not yet created. The diagram involves 10 lifelines: UE, NG-RAN, AMF, SMF, UPF, NRF, MB-UPF, MB-SMF, PCF, and UDR. The process starts with a UL NAS message from the UE to the AMF, followed by a series of requests and responses between the AMF, SMF, NRF, MB-SMF, PCF, and UDR. The SMF then initiates the establishment of 5GC Individual MBS traffic delivery, which involves multiple steps between the SMF, UPF, and MB-SMF. Finally, multicast data is transmitted from the UPF to the UE via the PDU Session. + +Figure 6.30.3-1: UE join request when related MBS session is not yet created + +1. UE sends a join request for an IP SSMA. +2. The SMF checks whether the UE is authorized to join 5MBS multicast sessions. The SMF inquires MB-SMF handling the IP SSMA at the NRF and detects that none is assigned. It inquires MB-SMF at NRF based on other criteria, e.g. UE location and selects MB-SMF to handle IP SSMA. +3. SMF requests MB-SMF to provide info about the MBS session for the IP SSMA and provides UE location. +4. MB-SMF may interact with PCF to check whether policies allow creation of MBS session. It indicates that MBS session is not yet established and possibly location(s) of UE(s) desiring to join or a service area selected by the MB-SMF based on those locations. + +5. PCF may check at UDR whether there are preconfigured policies for IP SSMA. +6. PCF decides whether an MBS radio session is permissible at the indicated location(s) or a service area and selects QoS for the MBS session (e.g. based on policies in the UDR) and indicates that to the MB-SMF. +7. The MB-SMF decides whether to accept the join request and whether to establish the MBS session towards the radio. The MB-SMF may count the number or log the join requests to determine their frequency and/or whether the attempts are concentrated in a specific area in order to decide whether to establish the MBS session towards the radio and in order to determine a possible service area for the MBS session. + +The MB-SMF also stores SMFs that subscribed in step 3. + +8. The MB-SMF request the MB-UPF to create an N4 session of the MBS session with IP SSMA and to send an IGMP join request for the IP SSMA. +9. MB UPF sends IGMP join request for the IP SSMA. +10. If the MB-SMF does not establish the MBS session towards the radio, it still registers itself at the NRF as handling the source specific multicast address, and will then be informed by SMFs about subsequent join attempts for this source specific multicast address, and can then decide to establish the MBS session towards the radio. +11. The MB-SMF informs SMF whether the MBS session towards radio is to be established and informs about QoS flow(s) for the MBS session. It may instead request that the join request is rejected. +- 12.-14. SMF updates the PDU session with additional QoS flow unless that flow can be transported via default QoS flow. The SMF provides no other information about MBS session in N2 container if MB-SMF decided not to establish the MBS session towards the radio. It indicates towards the UE that the join request is accepted. +15. Same as step 11 in Figure 7.2.1.3-1 of TS 23.247 [4]. +16. Same as step 13 in Figure 7.2.1.3-1 of TS 23.247 [4]. +- 17-19. Same as in Figure 7.2.1.3-1 of TS 23.247 [4]. + +![Sequence diagram showing the PDU Session modification when MB-SMF decides to establish MBS session towards radio. The diagram involves five entities: UE, NG-RAN, AMF, SMF, and MB-SMF. The process starts with the MB-SMF deciding to establish an MBS session towards the radio. It then enters a loop 'For each Subscribed SMF' to notify them via 'Nmbsmf_MBSSession_ContextStatusNotify (Establish MBS session)'. Next, it enters a loop 'For each affected UE' to initiate a 'PDU Session Modification procedure to add info about MBS session'. Finally, it enters a loop 'For each affected NG-RAN node' to perform 'Shared delivery establishment for MBS session'.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant MB-SMF + + Note right of MB-SMF: 1. Decide to establish MBS session towards radio + Note over SMF: For each Subscribed SMF + Note right of MB-SMF: 2. Nmbsmf_MBSSession_ContextStatusNotify (Establish MBS session) + Note over SMF: For each affected UE + Note right of SMF: 3. PDU Session Modification procedure to add info about MBS session + Note over NG-RAN: For each affected NG-RAN node + Note right of NG-RAN: 4. Shared delivery establishment for MBS session + +``` + +Sequence diagram showing the PDU Session modification when MB-SMF decides to establish MBS session towards radio. The diagram involves five entities: UE, NG-RAN, AMF, SMF, and MB-SMF. The process starts with the MB-SMF deciding to establish an MBS session towards the radio. It then enters a loop 'For each Subscribed SMF' to notify them via 'Nmbsmf\_MBSSession\_ContextStatusNotify (Establish MBS session)'. Next, it enters a loop 'For each affected UE' to initiate a 'PDU Session Modification procedure to add info about MBS session'. Finally, it enters a loop 'For each affected NG-RAN node' to perform 'Shared delivery establishment for MBS session'. + +**Figure 6.30.3-2: PDU Session modification when MB-SMF decides to establish MBS session towards radio** + +1. The MB-SMF decides to establish the MBS session towards the radio. The MB-SMF may count the number or log the join requests to determine their frequency and/or whether the attempts are concentrated in a specific area in order to decide whether to establish the MBS session towards the radio. +2. The MB-SMF notifies SMFs that subscribed to info about an MBS session when the MB-SMF decides to establish the MBS session towards the radio. +3. The SMFs then update the PDU sessions of related UEs with the MBS session information. +4. NG RAN nodes serving UEs within the MBS session request the MB-SMF to deliver MBS data towards them and start multicasting those MBS data over the radio. + +## 6.30.4 Impacts on services, entities and interfaces. + +### MB-SMF + +- Decide whether to establish MBS session toward radio. +- Inform SMFs when deciding to do so. + +### SMF + +- Select MB-SMF when UE request to join IP SSMA and no MB-SMF is assigned. +- If MB-SMF decides not to establish MBS session toward radio, apply individual delivery and do not provide MBS session information within PDU session. +- If MB-SMF subsequently decides not establish MBS session toward radio, update PDU session with MBS session information. + +### UDR + +- Store preconfigured information about MBS policies for an IP SSMA. + +## 6.31 Solution #31: Multicast access control for high number of public safety UEs + +### 6.31.1 Introduction + +This solution addresses Key Issue #6. Considering the case that multiple departments from the same mission critical organization served by different AS may utilize the same PLMN network, as described in bullet 2 in clause 4.2, it is important to support the multicast resource is fairly used by the different departments. + +### 6.31.2 Functional description + +During the UE join or the MBS session activation procedure, when the NG-RAN is going to allocate resource for the join requesting UE, the NG-RAN needs to check the resource availability for this UE who is mapped to a certain slice. Different departments' users may be mapped into different slices. If there are available resource in the dedicated/shared multicast resource for that slice, then the join/MBS session activation will success and continue, else the NG-RAN reject the PDU Session Resource setup and informs the UE, which may further reports the resource failure towards the AF to make further decision, e.g. release some low priority group communications which is using the MBS. + +### 6.31.3 Procedures + +This solution is on top of the procedure in 7.2.1.3 of TS 23.247 [4]. The enhancement are as follows: + +In step 7, The NG-RAN checks the radio resource usage corresponding to the S-NSSAI. + +In step 8, if the NG-RAN determined that there is no available dedicated and shared multicast resource for the slice. As part of the AN specific signalling exchange with the UE, no radio resources for the UE to receive the multicast MBS session is provided to the UE. + +In step 9, a radio resource failure is included in N2 SM container and provided to the SMF. After the SMF receive the failure, it may trigger the network triggered multicast session leave as described in clause 7.2.2.3, and step 11-19 will not performed. + +**Editor's note:** It is FFS whether network triggered multicast session leave can be triggered at this step. + +After step 8, the UE(s) can report the failure events to the AF. + +**Editor's note:** For public safety, related application level signalling is defined by SA6 and coordination is required. + +**Editor's note:** It is to be evaluated the benefits of this solution compared with existing join failure event report from MCX Client to MCX Server. + +**NOTE 1:** This UE signalling can cause extra overload and requires the UE to be in RRC\_Connected state. + +Based on the reports from UE(s), the AF may release the multicast MBS session and may instead use an existing MBS broadcast session or establish a new MBS broadcast session for the group call, or the AF may release some low priority group communications which is using the MBS if there is not enough radio resource. + +**Editor's note:** For public safety, related AF procedures are defined by SA6 and coordination is required. + +**Editor's note:** More investigation whether a broadcast MBS session can avoid overload in a better manner than a multicast MBS session with transmission mode for inactive reception is required. + +**Editor's note:** It is FFS why the broadcast MBS session can be established but radio resource allocation fails for multicast MBS session. + +**NOTE 2:** In order to avoid the uplink overload, the application layer can provide mechanism to alleviate the overload, e.g. announcing to the UEs that no report is needed any more, or dynamic specifying some UE to report this event based on location. Or the application client can make the decision when to report considering the load conditions. + +The MBS session activation procedure defined in clause 7.2.5.2 of TS 23.247 [4] is also impacted. As the radio resource allocation interactions in step 10b is referred from the step 8-12 in clause 7.2.1.3 MBS session join procedure. So the changes in above procedure is also applied to the MBS session activation procedure. + +Editor's note: It is FFS about the resource allocation failure when multicast MBS session is activated in step 12 in clause 7.2.5.2 of TS 23.247 [4]. + +### 6.31.4 Impacts on services, entities, and interfaces + +NG-RAN: + +- Send failure events related with MBS session join or MBS session activation to the UE. + +UE: + +- Receive failure events related with MBS session join or MBS session activation from NG-RAN and report it to the AF. + +Editor's note: Detailed impact will be determined by (and/or in collaboration with) RAN WGs. + +--- + +## 7 Evaluation + +Editor's note: This clause will provide evaluation of different solutions. + +### 7.1 Key Issue #1: MBS session reception in RRC Inactive + +#### 7.1.1 Overview over available solutions + +For Key Issue #1 "Multicast MBS data reception in RRC Inactive state", there are 14 solutions in the TR: + +- #1,#3,#4,#5,#6, #18, #19, #20, #21, #22, #23, #26, #27, #28. + +A comparison of solutions covering RRC\_Inactive MBS Multicast reception is shown in Table 7.1.1-1. + +Table 7.1.1-1: Comparison of multicast solutions for KI#1 RRC\_Inactive mode reception + +| Sol | CN Assistance/Recommend for Inactive Reception | Assistance Parameters | Mobility Handling | MBS session activation/release/deactivation | RAN selects UEs delivery mode | Remarks | +|-----|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|------------------------------------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Y. AF provides assistance to NG-RAN | Y. MBS priority, UE session priority, RRC_Inactive enable | | | Y. RAN can decide when to switch UE mode for MBS | Per session allow/disallow RRC_Inactive reception In place of MBS priority ARP, 5QI can be used. Discussion whether UE priority needs to be per MBS session is below Per user priority may be difficult to handle, per session allow/disallow sufficient | +| 3 | Y. AF provides assistance to NG-RAN | Y. MBS session ID, privilege/non-privilege users in MBS session. If privilege transition to RRC_Inactive should be avoided | | | | How paging is handled for privileged UEs in case of activation of MBS session is FFS | +| 4 | | | | Y. Group CN paging with paging cause | | Paging cause indicates the reason for paging to enable RRC_Inactive UEs to remain inactive when MBS session is activated and enable UE to receive the MBS session data in RRC Inactive state. | +| 5 | | Y. MBS context shared among RAN nodes in RNA | Y. Depends on UE moves within RNA, outside RNA | Y. Depends on whether target cell has MBS session support or not | | Assumes all the NG-RAN nodes are homogeneous in terms of RRC_Inactive reception capability. RNA update procedure may be used. Mostly RAN centric | +| 6 | N. Existing QoS parameters for MBS QoS flows sufficient | Existing. PER, 5QI, ARP etc. will help RAN to decide enabling RRC_Inactive reception | | | Y. RAN can decide when to switch delivery mode for MBS | 5QI, PER, ARP, etc. may be used to indicate a MBS level priority to NG-RAN but may not implicitly to decide to allow/disallow INACTIVE MBS reception. They also propose to use existing "RRC Inactive Assistance Information" sent by AMF to NG-RAN. But this information may not have any co-relation with MBS session and can only be used as additional UE specific information to be used by NG-RAN to decide the RRC_Inactive state for a UE | +| 18 | | | | Y. Group paging without paging cause | | Requires RAN input: Whether/how RRC Inactive UE responds when the CN initiated group paging is performed, it go back to the RRC Connected state. | +| 19 | Y. When requested by target NG-RAN, MB-SMF provides assistance information | Y. MBS context related info | Y. UE moves to NG-RAN where current MBS is not served | Y. RAN then decides delivery mode | Y. RAN can decide when to switch delivery mode for MBS | To enable RRC_Inactive UE to continue reception when moving within RNA, either source RAN node informs serving/target RAN node about MBS, or MB-SMF informs all RAN nodes in a service area | +| 20 | | | Y. Move to new NG-RAN in a new TA. Initiate mobility procedure | | | UE can join or leave multicast session during a re-registration for TA updated. | + +| | | | | | | | +|----|--------------------------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 21 | | | Y. UE moves out of RNA but within RA | | | Assumes that when UE in RRC Inactive state moves out of the Registration Area or fails to perform the RRC Resume procedure (e.g. when moving out of the RNA), UE invokes the mobility registration update procedure. | +| 22 | | | | Y. Page only CM-Idle UEs. Group paging not needed for RRC_Connected, RRC_Inactive | | NG-RAN keeps context of MBS and shared tunnel live even if session is inactive. Resource consumption is not optimal RAN-centric decision | +| 23 | | | | Y. Individual paging to RRC_Inactive and RRC_Idle UEs | | AMF observes and takes the decision (to page UEs) without the information about SMF on MBS context. | +| 26 | Y. CN sends (to RAN) list of UEs recommended to be kept in RRC_Connected | Y. List of UEs recommended to be kept in | | | Y. CN list is only recommendation | Discussion whether list of recommended UEs/ UE priority needs to be per MBS session is below | +| 27 | Y. AF provides list of privileged UEs during MBS-creation. | Y. GPSI of list of privileged UEs | | | Y. List of shared UEs needs to be in RRC_Connected mode | This solution requires that the AF be aware of the UEs' GPSI. This solution does not depend on PCC deployment and does not require per UE/PDU Session signalling as in case of Sol#3
Discussion whether list of recommended UEs/ UE priority needs to be per MBS session is below. | +| 28 | | Y. MBS context and data shared among RAN nodes in RNA | Y. different handling if UE moves within RNA, outside RNA, outside RA | Y. Depends on whether target cell has MBS UP already established or not | | RNA update procedure is used if UE moves outside RNA and mobility procedure is used if UE moves outside RA
Prevention of multiple data between source and target gNB has to be ensured
Assumes all the NG-RAN nodes are homogeneous in terms of RRC_Inactive reception capability | + +## 7.1.2 Assistance Information + +**Sol#1:** proposes to have assistance from AF: + +- Indication of whether multicast reception by UEs in RRC\_Inactive state is allowed for specific multicast MBS service(s)/session(s). +- MBS session Priority. +- UE priority within MBS session. +- UE capabilities and preferences. + +**Solution#3:** (Solution covers both KI#1 and KI#6) AF provides assistance information with "privileged" UEs of an MBS session, which are preferably to be kept in RRC\_Connected state. In Sol#3, the use case is targeted to public + +safety only and assuming that the private IP address of the UE is available (as in IMS case). The assistant information is provided via PCF. + +**Solution#6:** Proposes that existing "RRC Inactive Assistance Information", and the existing QoS parameters, e.g. PER in the 5QI and ARP of MBS QoS flow can be used by NG-RAN to determine whether the receiving of the multicast MBS session data in RRC inactive state can be enabled and whether UEs can be sent to RRC Inactive state to receive the multicast MBS session data. + +**Solution#26:** (Solution covers both KI#1 and KI#6) AF indicates for some UEs recommended (that may be part of one or multiple MBS sessions) should to be kept in RRC\_Connected state. The indication is independent of an MBS session. + +**Solution#27:** (Solution covers both KI#1 and KI#6) This solution proposes that AF sends a list of privileged UEs in MBS Session creation. This solution requires that the AF be aware of the UEs' GPSI. This solution does not depend on PCC deployment. + +#### Comparison of the solutions with assistance information: + +##### *Per MBS session assistance information* + +Solution #1 proposes to have explicit assistance information (MBS priority and/or recommendation whether to enable inactive MBS reception to be used to decide which MBS sessions can be allowed RRC\_Inactive reception). Solution #6 proposes that the existing QoS parameters, e.g. PER and ARP in the 5QI of MBS QoS flow can be used to support the NG-RAN to decide which MBS can be allowed RRC\_Inactive reception. Whereas solution #6 advocates that that the existing QoS parameters, e.g. PER and ARP in the 5QI of MBS QoS flow is sufficient and can be used to support the NG-RAN to decide which MBS can be allowed RRC\_Inactive reception. + +##### *Per UE assistance information.* + +Solution #1 proposes a UE session priority as assistance information to enable RAN to decide which UEs in the MBS session can be switched to RRC\_Inactive state. Solution #3 and solution #27 also suggest that some UEs within an MBS session can be marked as privileged to assist NG RAN to decide which UEs should be kept in RRC\_Connected state. Solution#26 proposes that a recommendation can be provided for some UEs that they should be kept in RRC\_Connected state; this recommendation is not linked to an MBS session. In all those solutions, it is assumed that an AF provides the related information. Most of the solutions also address key issue 6 as a typical use case could be that a public safety AF has knowledge of privileged or frequently talking users. For such users frequent state transitions between RRC\_Connected and RRC\_Inactive state can in this manner be avoided. + +Only solution 1 suggest multiple priority levels. + +Solutions 26 has the advantage that it is well suited for users in multiple MBS sessions (as dispatcher for public safety) and that it avoids possible conflicting state recommendations obtained for the same user via different MBS sessions. If the UE is different role in different MBS session, the AF need coordinate the UE role in different MBS session and depending on which MBS session is in activate state, the AF may need give different information to 5GC. + +The signalling procedure for the AF to provide the information also differ: Solutions 27 extends the MBS session create procedure. Solution 3 extends AF session with required QoS Create procedure and assumes that the information is propagated via the PCF to the SMF. Solution 26 extends the parameter provisioning procedure. + +For UE level assistance information, one proposal (solution 6) is to reflect the UE level assistance information via the QoS information of associated QoS flow. This solution assumes that whether the UE can be moved into RRC Inactive state depend on the UE QoS requirement, i.e. RRC Inactive UE has lower QoS requirement because there is no HARQ. + +##### *Parameter provision procedure* + +For the MBS session level assistance information, it seems the only way to transmit from AF to 5GC is via the MBS session creation procedure. + +Sol#1/#26 propose the AF provides the parameter (list of UE) (same as solution 1 as part of the MBS subscription data) to the UDM. When the UE joins the MBS session, the SMF fetches the data from UDM, which include the related UE + +level assistance information. The difference between two solutions is on whether this UE level assistance information is per MBS session or per UE granularity. As mentioned in Sol#26 if the UE level assistance information is per UE level, AF needs to consider whether the related MBS session is in active or inactive state and update the UDM accordingly. However, if this information is per MBS session level, this additional update per MBS session state is not needed. If the UE joins multi MBS session, at the NG-RAN side it may receive different UE level assistance information from different MBS session. NG-RAN nodes need to reconcile the information, e.g. it can take the highest request, e.g. whether the UE level assistance information in one of the MBS session prefer to be in CONNECTED state, as input parameter to decide whether it need keep in Connected state. + +Sol#1 and Sol#26 (if Sol#26 is updated to be associated with MBS Session), requires the AF to perform Nnwf\_ParameterProvision\_Create/Update procedure after the MBS Session in created. + +Sol#3/#6 propose the AF provides the parameter as part of the QoS information to the PCF and SMF gets the related information during the SM policy association establishment/update procedure. By doing this, the deployment of PCF is mandatory. The AF cannot inject the related information before the UE activates the associated PDU session. Also this update need be done per UE granularity, i.e. for a list of UE, the AF needs to update one by one per UE. + +Sol#27 proposes the AF provides the parameter (list of UE) as one parameter during the MBS session creation procedure. The MB-SMF store the received list of UE information. The MB-SMF provides full list of the UE information to all contacted SMF(s). It is possible that some prioritized UEs in the list are not handled by an SMF (if those UEs have not joined yet, or joined in other SMF(s)), and in case the list of UEs is changed, the MB-SMF needs to notify all SMF(s) involved in this MBS session. + +For the MBS session level assistance information, it is better to be conveyed as other MBS session information parameter, e.g. QoS information. Then it is proposed to be delivered to NG-RAN node as part of the shared delivery tunnel establishment procedure. + +For the UE level assistance information, all solution proposes to use the PDU session level signaling to deliver the parameter to the NG-RAN node. + +### 7.1.3 Activation of MBS multicast session + +**Solution#4:** Proposes to use group based CN paging as the trigger for activation and release of MBS session. If paging is for MBS session activation, the NG-RAN node determines for each cell whether transmission for RRC INACTIVE UE is enabled and includes a paging cause if RRC INACTIVE UE do not need go back to the RRC-CONNECTED state. + +**Solution#18:** Unlike Solution#4 (where paging cause is used), solution#18 proposes that no paging cause is required for MBS Session activation. It follows existing Rel 17 paging procedures. It also proposes that, for releasing of MBS session, RRC IDLE UEs (without active UP) get notified by SMF only when they reconnect using PDU Session Modification procedure. In case RRC\_INACTIVE UE happens to share the same PO with any of the IDLE UEs and responds to paging, the RRC\_INACTIVE UE will be brought back to RRC\_CONNECTED. + +**Editor's note** Whether the RRC\_INACTIVE UE need be aware the group paging is CN initiated or RAN initiated is FFS. + +**Solution#19:** Existing MBS session activation procedures are used from CN towards RAN nodes. RAN nodes in RNA inform each other about MBS session activation. RRC-Inactive UE in cell shall remain RRC-inactive during MBS session activation when related delivery mode is used in that cell. RAN groups will determine related signalling. + +**Solution#22:** NG-RAN node keeps the multicast MBS session context and N3mb shared tunnel for the multicast MBS session as long as the NG-RAN has UE context for UEs in the MBS session context which may be in either RRC-CONNECTED or RRC\_INACTIVE state. (this seems existing REL-17 behaviour) Because of this, when the MBS session is (re-)activated, it should page only RRC\_Idle UEs and need not page RRC\_Inactive UEs (group paging is not needed). + +**Solution#23:** Suggests using CN paging also for RRC\_Inactive UEs. The paging area includes all the registration areas of those UE in CM-IDLE mode, and NG-RAN node where the CM-Connected mode UE(s) is camping. Unclear what the benefits compared to RAN paging would be are quite debatable. + +### Comparison of the solutions focusing on Activation/Release: + +#### *On how to efficiently page RRC\_Inactive UEs during activation MBS session* + +All the four solutions (#4, #18, #22, #23), propose group CN paging for RRC\_Idle UEs. However, they differ in the way they handle the RRC\_Inactive UEs. The overall view by all the solutions are, + +- For activation, only RRC\_Idle UEs should go to RRC\_Connected state (after paging) and RRC\_Inactive UEs should not switch to RRC\_Connected state. +- While Sol#4 proposes to include paging cause to not let RRC\_Inactive UEs to switch to RRC\_Connected state, sol#18 does not use paging cause. Not including the paging cause may allow RRC\_Inactive UEs to switch to Connected state. +- Solution #22 proposes that only RRC\_Idle UEs should be group CN paged. And for RRC\_Inactive UEs, the NG-RAN node keeps the multicast MBS session context and N3mb shared tunnel for the multicast MBS session and when the service is re-activated and there are UEs in RRC\_INACTIVE state, the NG-RAN needs to notify the UEs of this activation. But they fail to explain that without using RAN paging how NG-RAN node can notify UEs. +- Solution 23 proposes that AMF will page all the NG-RAN where there are CM\_Idle UEs. For RRC\_Inactive UEs, NG-RAN will use RAN paging. However, it is unclear that how RRC\_Inactive UEs will react to CN paging. + +#### *On how to efficiently page RRC\_Inactive UEs during release of MBS session* + +Only solutions #4 and #18 talk about paging for release of MBS session. In Sol #18, the Rel-17 solution is assumed how RRC\_Inactive UEs can be notified about the release of the MBS session, solution #4 states that RRC\_Inactive UEs to be paged to go to RRC\_Connected state for release of the MBS session. + +NOTE: Whether/how RRC\_INACTIVE UEs behave when group paging for CM-IDLE UE(s) is performed is to be determined by RAN WG(s). + +#### *On whether the solution can be able to differentiate between RRC\_Inactive MBS UEs than RRC\_Idle MBS UEs?* + +Only solution #4 is proposing to have differentiated paging (with paging cause included) for RRC\_Inactive UEs. Because, in case RRC\_INACTIVE UE happens to share the same paging occasions with any of the IDLE UEs and responds to paging, the RRC\_INACTIVE UE will be brought back to RRC\_CONNECTED, which should be avoided. + +### 7.1.4 Mobility for RRC\_Inactive UEs receiving MBS data + +**Solution#5:** Proposes MBS session service continuity procedures in case of RNA change, but most aspects of the solution will need to be decided by RAN. If RRC\_inactive UE moves within RNA and if the target NG-RAN node does not deliver multicast data at target cell using delivery mode for RRC\_inactive reception, the UE sends RRC message to transition to RRC\_connected state to target NG-RAN node. If target RAN node does not have UE context, it may fetch it from source RAN. If the UE moves out its RNA and within RA, it triggers the RNA update procedure as specified in TS 38.300 [13]. The evaluation will require RAN feedback. + +**Solution#19:** It focuses on how to inform RAN nodes not serving any connected UEs in the MBS sessions? about the MBS session. This solution describes two options to accomplish: + +- i) source RAN informs serving/target RAN about MBS; +- ii) MB-SMF informs all RAN nodes in a service area. + +RRC\_inactive UEs can move to cells where the transmission mode for RRC connected state is applied and then need to transition to the RRC connected state to receive MBS data. The evaluation will require RAN feedback. Existing MBS session activation procedures are used from CN towards RAN nodes. RRC-Inactive UE in cell shall remain RRC-inactive during MBS session activation when related delivery mode is used in that cell. + +**Solution#20 and #21:** The two solutions propose to allow a UE to request MBS session join/leave during mobility registration update procedure by using a multicast session information container in the Registration Request message, + +when the UE in Idle state or receiving multicast data in RRC Inactive state moves out of the Registration Area or fails to perform the RRC Resume procedure (e.g. when moving out of the RNA). + +**Solution#28:** When the UE is moved into RRC Inactive state, the serving RAN node acts the anchoring point, to inform the other RAN nodes in the RNA to provide the Multicast MBS data. The UE performs the RNA update procedure as specified in the R17, if it moves outside RNA. If UE moves out of RA, the UE initiates mobility registration after the RNA update procedure fails. This solution proposes that RAN nodes in the same RNA area may receive the MBS data from one RAN node or multiple RAN nodes which have established the shared delivery tunnel. + +#### Comparison of the solutions focusing on Mobility: + +*On how to manage RRC\_Inactive UEs continuation of MBS data Outside RNA.* + +Most of the solutions propose to use RNA update procedure by the UE when it moves outside RNA. Solutions #20 and #28 propose to use mobility registration procedure when UE moves outside RA. Solution #21 also advocates that if UE in Idle state or receiving multicast data in RRC Inactive state moves out of the Registration Area or fails to perform the RRC Resume procedure (e.g. when moving out of the RNA). + +## 7.2 Key Issue #2: 5MBS MOCN RAN Sharing + +Soln #2, #7, #8, #9, #24 and #29 are proposed to address Key Issue #2: 5MBS MOCN Network Sharing. + +Soln#2 proposes a solution of providing an additional identifier by the AF towards the MB-SMF when creating MBS sessions. The MB-SMF passes it to the NG-RANs. Based on the additional identifier, the shared NG-RAN can understand multiple Broadcast MBS sessions are transferring the same content and deliver packets from one session over the air. + +Soln#7 proposes to use associated session ID to be passed from the AF to NG-RANs via 5GCs, to enable shared NG-RAN to associate multiple Broadcast MBS sessions. The shared NG-RAN associate multiple Broadcast MBS sessions and deliver packets from one session over the air. The associated session ID can be SSM or TMGI as two options. To further saving CN resources and NG-RAN processing efficiency, Soln#7 proposes to establish one user plane within those broadcast MBS sessions. In case there is a failure in the on-going user plane, shared NG-RAN will initiate the establishment of another user plane towards another 5GC. + +Soln#8 proposes to use MOCN TMGI to create one broadcast MBS session towards one 5GC for those shared NG-RANs, and if all NG-RANs under MBS service area are not shared, also create one broadcast MBS session towards each 5GC for each PLMN for those dedicated NG-RANs. + +Soln#9 proposes pass all the associated TMGIs from the AF towards the MB-SMF when creating MBS sessions. The MB-SMF pass the TMGI list to the NG-RANs. The NG-RAN selects the primary TMGI and return the primary TMGI and its usage area to the AF via the MB-SMF, so that AF can update service announcement to let UEs to understand the TMGIs and their corresponding usage area. To further saving CN resources and NG-RAN processing efficiency, Soln#9 also proposes not to establish the user plane in case the TMGI of the broadcast MBS session is not the primary TMGI. + +Soln#24 proposes to configure the associated TMGIs in NG-RANs, so that shared NG-RAN can associate multiple broadcast MBS sessions and delivery the content of one broadcast MBS session over the air. + +Soln#29 proposes to use the same TMGI to create broadcast MBS sessions towards each 5GC together with a MOCN signalling flag to differentiate from normal broadcast MBS sessions. Soln#29 also proposes to establish one user plane within those broadcast MBS sessions. In case there is a failure, shared NG-RAN will initiate the establishment of another user plane towards another 5GC. + +The evaluation can be performed from the following aspects: + +#### Whether the solution can enable shared NG-RAN to optimize radio resource utilization for MOCN network sharing deployment? + +These criteria can be used to evaluate whether the solution can address KI#2. + +Soln#2 and Soln#7 introduce additional identifier and associated session ID to be provided by the AF. The AF provide it to the MB-SMF in MBS session creation. The MB-SMF passes it to the NG-RANs, so that shared NG-RAN can bring data from one broadcast MBS session over the air. + +Soln#8 proposes to create only one broadcast MBS session towards shared NG-RAN, so the shared NG-RAN will only deliver the data from this broadcast MBS session over the air. + +Soln#9 passes all the relevant TMGIs to the NG-RAN, so that shared NG-RAN will select the primary TMGI and deliver the data from the broadcast MBS session identified by the primary TMGI. + +Soln#24 configures the associated TMGIs in NG-RANs, so that shared NG-RAN can bring data from one broadcast MBS session over the air. + +Soln#29 proposes to create broadcast MBS sessions with the same TMGI and additional MOCN signalling flag, so that the shared NG-RAN can determine and bring one broadcast MBS session over the air. + +All those solutions can address KI#2. + +#### **Whether the solution can be applied to any deployments?** + +In MOCN network sharing deployment, it is possible that not all NG-RAN nodes are shared. There may be some NG-RAN nodes dedicated to specific PLMN which connected to the corresponding 5GC. The assumption that all NG-RAN nodes are shared in MOCN network sharing deployment cannot be made. + +In Soln#2, Soln#7, Soln#9, Soln#24 and Soln#29, AF creates each broadcast MBS session separately, so that the shared NG-RAN will receive multiple broadcast session setup requests and offer the service, while the dedicated NG-RAN will receive only the corresponding broadcast session setup request to offer the service. + +In Soln#8, AF creates one broadcast MBS session towards one 5GC for those shared NG-RAN nodes, and if all NG-RAN nodes under MBS service area are not shared, creates one broadcast MBS session towards each 5GC for those dedicated NG-RAN nodes. + +#### **Whether extra efforts are needed when introducing a new MBS service?** + +To introduce a new MBS service (e.g. a TV channel), it is important to evaluate whether extra efforts are needed. + +In Soln#2, Soln#7, Soln#8 and Soln#29, AF can perform TMGI allocation and broadcast MBS session creation as in Rel-17. Soln#9 requires all relevant TMGIs to be allocated prior to the broadcast MBS session creation, which are minor implications on the AF. For those solutions, the new MBS service can be introduced by the invoking Nmbsmf or Nmbsf APIs, without additional efforts. + +Soln#24 requires the coordination of the O&M configuration in NG-RANs (provision relevant TMGIs) and service operation (TMGI allocation and broadcast MBS session creation). The O&M configuration is done prior to TMGI allocation, since the TMGI belongs on a pre-agreed service-id range amongst the participating PLMNs. For example, if PLMNs with MCC=234, MNC=15 (operator A) and MCC=234, MNC=10 (operator B) are doing MBS RAN sharing, the corresponding RAN nodes are already configured with the PLMN-ids of each of the sharing partner and can be configured with the specific respective service-id (6 digits numbers) of the TMGIs of two PLMNs that correspond to the same content or even range of service-ids. For instance, service-id=123456 (for operator A) and service-id=001234 (for operator B) corresponds to content from "TV channel X". + +For all solutions, prior to introducing new MBS services, the configuration in all shared NG-RANs need to be done beforehand. + +#### **How many TMGIs are advertised by a shared NG-RAN?** + +The number of TMGIs advertised will cause some impacts on the radio resource efficiency. + +Soln#2, Soln#7 SSM option and Soln#24 propose to have all the relevant TMGIs advertised, and those TMGIs point to the same radio resource for broadcast data delivery. Soln#7 TMGI option only has one TMGI advertised. + +Soln#8 only has one MOCN TMGI advertised. + +Soln#9 only has the selected primary TMGI advertised. + +Soln#29 only has one common TMGI advertised. + +#### **Is it backward compatible (service announcement impacted)?** + +The backward compatibility is an important aspect in the evaluation. If the solution is backward compatible, it can benefit Rel-17 UEs to work in the optimized way. All the solutions are backward compatible in radio interface, but some are not in the service announcement. + +In Soln#2, Soln#7 SSM option and Soln#24, there are no impacts on service announcement. Each UE will get the service announcement with its own TMGI with the PLMN ID it belongs to. In Soln#29 and Soln#7 TMGI option, each UE will get the service announcement with a common TMGI, which may have different PLMN ID from its network. + +In Soln#8, there are no impacts on service announcement as well. Each UE may get the one service announcement with MOCN TMGI and another one with its own TMGI (i.e. TMGI dedicated to PLMN) if all NG-RAN nodes under MBS service area are not shared. + +In Soln#9, AF needs to consolidate the information it receives from all shared NG-RANs and include TMGIs with their usage area in service announcement. + +#### How UE receives broadcast MBS session data? + +The complexity of the UE logic is not negligible. + +In Soln#2, Soln#7 SSM option and Soln#24, a UE can receive the broadcast MBS session data with its own TMGI, as indicated in the service announcement. In Soln#29 and Soln#7 TMGI option, a UE receives the broadcast MBS session data with a common TMGI in the service announcement. + +In Soln#8, each UE may use the MOCN TMGI or its own TMGI to receive the broadcast MBS session data, depends on whether it is served by a shared NG-RAN or dedicated NG-RAN. + +**NOTE:** When the UE receives Service Announcement including MOCN TMGI and Service Announcement including its own TMGI (i.e. TMGI dedicated to the PLMN) for same service from the AF, the service layer (e.g. 5MBS client, MC service client) or the application layer of the UE needs to be able to understand the MOCN TMGI and its own TMGI are for same service based on the information in the service announcements, e.g. SDP info with IP multicast address and port#, Service ID, and UE needs to be able to switch the listening TMGI when moving to the new cell without broadcasting the currently used TMGI. However, the lower layer does not have to be aware that these two TMGIs are for same service. + +In Soln#9, a UE needs to determine its location and find the appropriate TMGI to be used. And then, it can use the selected TMGI to receive broadcast MBS session data. + +#### Is the solution resource efficient in CN and NG-RAN processing? + +For those multiple broadcast MBS sessions, only the packets delivered over one broadcast MBS session will be used. The packets over other broadcast MBS sessions will be dropped, which wastes not only 5GC transportation resource, but also NG-RAN processing resource. + +Soln#2 and Soln#24 propose to establish all user planes which improves the service reliability, but less resource efficient. + +Soln#7, Soln#9 and Soln#29 propose to establish one user plane across those broadcast MBS sessions. In case the on-going one fails, NG-RAN initiates the establishment of another user plane, to improve the service reliability. In this approach, there will be some additional service interruption time for the user plane re-establishment (from MB-UPF to NG-RAN). However, compared with the error detection period, the additional user plane establishment period is small. + +In Soln#8, each NG-RAN has only one broadcast MBS session. Note that there is a trade-off between "*resource efficient in CN and NG-RAN processing*" and "*the efforts to re-establish the shared tunnel when currently used N3mb tunnel is released*". Having multiple shared tunnels could be beneficial for that case. + +#### Are there signalling impact in 5GC and NG-RAN? + +All solutions require service operation update provided by MB-SMF, as it is a new feature to be introduced. Some solutions avoid signalling impact in 5GC and NG-RAN, while some require. + +Soln#2 and Soln#7 require an additional identifier (associate session ID) to be passed from the AF to NG-RAN via 5GC. Soln#9 requires the complete TMGI list to be passed. Soln#29 requires a MOCN signalling flag to be passed and the TMGI in use may have different PLMN ID. + +**Editor's note:** It is to be confirmed by RAN WGs whether a shared NG-RAN can use a TMGI with a different PLMN ID which is not shared PLMN ID. + +Soln#8 requires MB-SMF return shared MBS service area to AF, but there is no signalling impact in 5GC and NG-RAN. + +Soln#24 avoids the signalling impact by the configuration in NG-RAN. However, depends on the alternatives to be chosen, it may require TMGI allocation to be delegated to NEF or MBSF. + +Table 7.2-1 illustrate the comparison of the solutions for KI#2 5MBS MOCN Network Sharing. + +**Table 7.2-1: Comparison of solutions for KI#2 5MBS MOCN Network Sharing** + +| Evaluation Aspects | Solution | | | | | | +|----------------------------------------------------------------|----------|--------------------|-----------------|-----|-----|-----| +| | 2 | 7
(NOTE 3) | 8 | 9 | 24 | 29 | +| Enable shared NG-RAN to optimize radio resource utilization | Yes | Yes | Yes | Yes | Yes | Yes | +| Applicable to any MOCN network sharing deployment | Yes | Yes | Yes | Yes | Yes | Yes | +| Additional efforts required when introducing a new MBS service | No | No | No | No | Yes | Yes | +| Number of TMGIs advertised | All | All/One | One | One | All | One | +| Backward compatible (regarding no Service announcement impact) | Yes | Yes | Yes | No | Yes | Yes | +| Additional logic in UE when receiving data | No | No/No?
(NOTE 1) | No?
(NOTE 1) | Yes | No | No | +| Resource Efficiency in 5GC and NG-RAN | No | Yes | Yes | Yes | No | Yes | +| Additional effort for recovering data transmission (NOTE 2) | No | Yes | NA | Yes | No | Yes | +| Signalling impacts in 5GC and NG-RAN | Yes | Yes | No | Yes | No | Yes | + +NOTE 1: The service layer or application layer of the UE may be impacted as described in the NOTE under "*How UE receives broadcast MBS session data?*" It applies to Soln#8. It does not apply to Soln#7 SSM Option. It applies to Soln#7 TMGI option only when there are pre Rel-18 NG-RANs. + +NOTE 2: The answer "No" means NG-RAN needs to detect the failure and switch the user plane locally, the "Yes" means NG-RAN needs to establish user plane towards another CN additionally, and the "NA" means it is the same as the MBS session for non-MOCN scenario. + +NOTE 3: The first value refers to SSM option and the second value refers to TMGI option, when there are two values in the cell. + +Besides those criteria mentioned above, some other issues shall also need to be taken into consideration: + +#### Whether AF can release MBS sessions flexibly? + +It is possible for the AF to request to trigger the MBS session deletion procedure for one or several PLMNs after a while. + +Soln#2 and Soln#7 SSM option use extra ID to identify the service, therefore the release of one PLMN will not affect other PLMNs. Soln#24 assumes the relationship is pre-configured therefore releasing will not affect others as well. + +Soln#8, Soln#29, and Soln#7 TMGI option propose to use MOCN TMGI (or same TMGI). However, a TMGI can be allocated and released separately from an MBS session, and thus the MOCN TMGI (or same TMGI) must be kept not deallocated when the MBS session towards this PLMN is stopped, if it is still in use by other PLMNs. + +Soln#9 proposes to pass all the associated TMGIs from the AF towards the MB-SMF when creating MBS sessions. When releasing the broadcast MBS session for one PLMN, the MBS session context of the PLMNs needs to be updated as well, which requires further clarification. Or the AF must keep holding the associated TMGIs till all relevant MBS sessions are released. + +#### Whether the solution can be compatible with pre Rel-18 NG-RANs? + +With the compatibility of pre Rel-18 NG-RANs, operators can deploy the MBS service freely. Otherwise, the optimization developed for KI#2 cannot be applied, until all the NG-RAN nodes are upgraded. + +In Soln#2, Soln#7 SSM Option and Soln#9, the additional information (associated session ID, TMGI list) is sent to NG-RAN as an optional parameter. Pre Rel-18 NG-RANs will ignore the parameter and continue to establish the broadcast MBS sessions in legacy way. The optimization will not be applied to pre Rel-18 NG-RANs, i.e. the same MBS content will be broadcasted several times over the air interface. However, the Soln#9 brings additional requirements on AF to construct the mapping of the primary TMGI and the usage area manually. + +In Soln#24, no additional information needs to be passed to NG-RAN, and thus pre Rel-18 NG-RANs could work naturally. + +In Soln#8 uses MOCN TMGI and native TMGI to separately target different NG-RAN nodes. There are no issues for dedicated pre Rel-18 NG-RANs, but for those shared pre Rel-18 NG-RANs, the MOCN TMGI may not be supported. + +Soln#29 assumes the TMGI from one certain PLMN as the common TMGI and uses it as the TMGI together with the MOCN signalling to create broadcast MBS sessions in all of the PLMNs requested by the AF. The MCC/MNC (i.e. PLMN ID) field of the common TMGI can be different from the current PLMN about to establish the broadcast MBS session, and there is no standardized requirement to check those fields or not. A dedicated pre Rel-18 NG-RAN nodes could not support the TMGI if it checks the MCC/MNC. There are different views on whether Rel-17 will be affected and whether the proprietary behavior can be ruled out. Depending on implementation, a shared pre Rel-18 NG-RAN node may only accept the first broadcast MBS session, while reject the later ones with the same TMGI. A shared pre Rel-18 NG-RAN node may accept all broadcast session setup requests with the same TMGI and only store the MBS session context of the latest one. However, the UEs from all PLMNs will be able to receive the MBS session using that TMGI and the MBS data will only be transmitted a single time. + +Soln#7 TMGI option also uses a common TMGI to be associated session ID. Pre Rel-18 NG-RANs will ignore it and continue to establish the broadcast MBS sessions using the native TMGI (the TMGI in MBS session ID). The broadcast MBS session establishment and content delivery work in the legacy way. However, it also requires AF to use native TMGI in service announcement, which leads to the similar service announcement issue as Soln#8 (multiple TMGIs are provided to the UE for the same MBS service). + +## 7.3 Key Issue #3: On demand multicast MBS session + +There are three solutions proposed with the intention to address the objective to regarding the on demand multicast MBS session: Solutions #10, #11 and #30. + +- Solution #10 proposes to reuse 4.15.6.6 and/or 4.15.6.6a, and includes flow description(s) with unicast and IP multicast address (i.e. MBS Session ID) to inform the PCF the MBS session that a certain UE wants to join. After the PCF informs SMF (with including the MBS session ID), the residual parts are similar as current defined procedure in TS 23.247 [4] with the following additions: 1) inform the MBS session to the UE via NAS and UE may further perform NATP for the received multicast data, and 2) associate the unicast flow and multicast data to further perform NATP by UPF for pre Rel-18 UE. +- Solution #11 proposes to reuse 4.15.6.6a, and includes MBS session ID to inform the PCF the MBS session that a certain UE wants to join. After the PCF informs SMF (with including the MBS session ID), the residual parts are similar as current defined procedure in TS 23.247 [4]. This solution alternative mandates deployment of dynamic PCC and assumes that UE's private IP address is available over N33. Solution#11, Alt#2 has impact on AF, PCF, SMF and UE. Besides, clause 4.15.6.6a of TS 23.502 [3] is intended for dynamic QoS update but the AF request join is not related to QoS control. +- Solution #30 proposes procedures for creation of an MBS multicast sessions towards the NG-RAN when UEs request to join an ongoing multicast session in an external IP network without the need of AF interactions. Based on operator policy, the MB-SMF may immediately establish the MBS session towards the radio when the first UE joins or wait until more UEs join. If the former, then this is Rel-17 solution, and if the latter, it is still to be clarified that is the benefit of applying individual delivery, instead of shared delivery when the first UE(s) join the MBS session. + +Solutions #10 and #11 have a substantial number of unresolved issues. + +**Editor's note:** The advantages of enabling an AF to request the core network to add users to an MBS session compared to the Rel-17 procedures where the AF invites UEs via service announcement and then the UEs request to join the session are FSS. + +From the perspective of impact to 5GC, Solution #10 has the same part as solution #11 with the addition that the 5GC configures the NATP in UE, and optionally SMF uses individual delivery for pre Rel-18 UEs, and UPF performs NATP for them. Solution #11 requires AF provide the MBS session ID, and PCF initiate SM Policy Association Modification procedure with including MBS session ID. + +Both Solution #10 and Solution #11 enhance the "AF session with required QoS update procedure. + +Compared to solutions #10 and #11, solution #30 addresses a different use case and thus also proposes entirely different procedures, mainly enhancements to the Nmbsmf\_MBSSession\_ContextStatusSubscribe and Nmbsmf\_MBSSession\_ContextStatusNotify procedures between MB-SMF and SMF. + +## 7.4 Key Issue #4: Group message delivery + +Solutions #12 and #13 are proposed to address Key Issue #4. + +Soln#12 proposes a solution on the NEF, which utilizing the Full-Service Mode offered by the MBSF/MBSTF (Object Delivery method). + +Soln#13 proposes a solution on the NEF, which utilizing both the Full-Service Mode offered by the MBSF/MBSTF as well as the Transport-Only Mode offered by the MB-SMF/MB-UPF directly. + +Both solutions keep the backward compatibilities with the group message delivery solution in eMBMS. + +For the Full-Service Mode, Soln#12 and Soln#13 are aligned. The solutions described in Soln#12 and Soln#13 contain the delivery of the group message, as well as the cancel and the modification of the group message, which are required from group message handling perspective. There are no contradictions between those two solutions. + +For the Transport-Only Mode, Soln#13 expects the reliability of the group message delivery to be implemented in the AF, and 5GC provides a transparent delivery bearer. In Transport-Only Mode, AF can interact with the MB-SMF/MB-UPF directly without the involvement of the NEF, which is supported in Rel-17. There are no additional benefits needs to include the NEF besides the existing exposure functionality (i.e. utilize the service operations defined for group message). Furthermore, the reliability delivery handling in AF does not fully take the advantage of the MBS. It increases the complexity of the AF implementation and requires each AF to implement the logic of reliable delivery, while such reliable delivery logic has already been offered by 5GC. + +It is an alternative option to let the NEF packetize the received group message and deliver packets to the MB-UPF. However, without service layer protection, the UEs are not able to deal with any errors during the transmission (e.g. packet loss, packet disorder, etc.). And it is not appropriate to introduce service layer protection to the NEF. + +Soln#13 points out the solution shall be re-used for general group message delivery purposes (not limited to MTC devices), which align with the proposal in group message delivery solution in eMBMS. + +Soln#13 further include the area which does not support MBS in the response message towards the AF. Even though this function is not tightly coupled with group message solution, it could benefit the AF and hide the deployment complexity towards the AF. The solution proposes that the AF can then deliver data to UEs outside the area via unicast, but the AF will in some cases not be aware of the UE location + +## 7.5 Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices + +For Key Issue #5, there are following solutions: + +- Sol#14 is intended for both multicast and broadcast MBS Session. +- Sol#15 covers only broadcast MBS Session. +- Sol#25 is intended for multicast MBS Session. + +For interaction between broadcast MBS and power saving mechanism, Sol#14 and Sol#15 are aligned. + +The table below is to provide an overview of the solutions of KI#5. + +**Table 7.5-1: Comparison of multicast solutions for KI#5** + +| | Solution #14 | Solution #15 | Solution #25
(periodic or one time transmission) | Solution #25
(Deferred activation) | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Inform UE the scheduled time | service announcement | Service Announcement. | Service Announcement or PDU session modification command. | NAS message (built by AMF) | +| Method to control the "awake" timing | DRX level - counted in milliseconds. | SDP level (NTP time values) - counted in seconds. | SDP level (NTP time values) - counted in seconds. | SDP level (NTP time values) - counted in seconds. | +| 5GC enhancement | N/A. | N/A | MB-SMF activates MBS session at start time | MB-SMF: provides wake-up time to SMF(s) in delayed activation request.
SMF: provides wake-up time in delayed activation request with UE list.
AMF: finds the UE in power saving mode and paging them individually, and provide the wake-up time in NAS message. | +| UE behaviour | DRX for MBS takes precedence over the existing Power saving mechanism. E.g. MICO, PSM, or eDRX. | Provided time takes precedence over the existing Power saving mechanism. | Provided time takes precedence over the existing Power saving mechanism. | Provided time takes precedence over the existing Power saving mechanism. | +| Use cases | MBS service
Suitable data transmission at times known in advance, e.g. for periodically repeated data transmissions | MBS service
Suitable data transmission at times known in advance, e.g. for periodically repeated data transmissions | MBS service.
Suitable data transmission at times known in advance, e.g. for periodically repeated data transmissions | Multicast MBS service.

Suitable for data transmission at not previously known times | + +NOTE: Note that the above-mentioned table may not exhaustively list the proposal of the solutions. For example, Solution#14 also suggest to keep UE connected for a while in the middle of an MBS data transfer. + +In fact the main idea of DRX level control and SDP level control are not against each other, they are, on the other hand, the complementary solutions and therefore can be adopted at the same time. In addition, Solution #25, option 1 also proposes to make use of service announcement to convey the knowledge of session start/end time of the MBS session. Solution #25 option 2 proposes to provide such information via NAS message to UEs in the MBS session and is therefore suited for multicast MBS service. + +Solution 25 Option 2 enables data transmission at times which are not known when the service announcement is performed. + +For solution #25: + +- The idea of "periodic or one time transmission" is to use the start time , which is already part of MBS session context, and provide the start time to the UE either via PDU Session Modification or service announcement, and 5GC triggers the session activation based on the start time. + +This solution has impact on AF, MB-SMF, SMF and UE. The activation and deactivation of an MBS session is a prerequisite for Rel-17 UEs to enter IDLE state when no data transmission is ongoing. + +- The idea of "Deferred activation" is another alternative to provide the time information, i.e. AF provides the wake-up time to 5GC whenever needed, and such information will be provided to UE via individual paging. The proposal uses session activation and provides the MBS information to UE by the AMF. The UEs start to receive MBS data at the configured times. From system impact perspective, the AMF is not supposed to be involved in + +the UE's handling of MBS Session whenever possible (due to the SMF-centric multicast solution chosen in Rel-17), however the new procedure of NAS Transfer in Figure 6.25.3.2-1 is not aligned with that principle. + +## 7.6 Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs + +**Editor's note:** It may need to be revised, depending on the conclusion of the updated solution and new solutions. + +Solution #3, #16, #17, #20, #26 and #31 are proposed to address Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs. + +Below is a short summary of the solutions: + +**Solution #3** proposes a solution to enable the AF to provide the group member information to NG-RANs via 5GC, which could be utilized by NG-RAN as assistance information when deciding which UEs can be sent to RRC\_INACTIVE when needed. The assistance information is provided via PCF. + +**Solution #16** proposes a solution to enable AF to offer public safety service via broadcast and/or multicast sessions, which allows the UE to decide whether to receive the public safety MBS content via broadcast MBS Session if available, and/or multicast session. + +**Solution #17** proposes a solution to enable AMF to become aware of the list of UEs that has joined a MBS sessions and get the UE list ready for group paging. When requested, the AMF trigger group paging without having to going through the UE list. + +**Solution #20** proposes to allow the UE to request multicast MBS session join/leave during mobility registration update procedure, by including the associated PDU session status and the multicast session information container in the Registration Request message. The UE can be in CM-IDLE state or in CM-CONNECTED with RRC Inactive state. + +**Solution #26** proposes a solution to let AF provide information to 5GC (via parameter provisioning interface) and then to NG-RAN that a UEs should stay in RRC\_CONNECTED. It also contains proposals to reduce the cell load for public safety UEs by reducing the amount of Listener Reports. However, it is to be clarified how the Listener Reports are to be reduced. + +**Solution #31** proposes that the NG-RAN indicates the resource allocation failure (which can be per slice to the UE and then the UE reports the failure towards the AF which may take further action, e.g. releasing low priority group communications which is using the MBS, switching the group call to broadcast MBS session. + +Following is a detailed evaluation of the solutions: + +### Solution #3: + +This solution enables an AF to provide group member information (e.g. privileged or not) as part of the MBS session to assist NG-RAN when deciding which UEs can be sent to RRC\_INACTIVE. As there are similar proposals only submitted for KI#1, this solution will be further evaluated in KI#1. + +### Solution #26: + +This solution also enables an AF to provide information about UEs recommended to be kept in RRC\_Connected state. The information is provisioned independent of the MBS session and thus applied for privileged users participating in multiple MBS sessions. As there are similar proposals only submitted for KI#1, this aspect of the solution will be further evaluated in KI#1. + +The solution also contains proposals to reduce the cell load for public safety UEs by reducing the amount of Listener Reports to avoid that UEs frequently need to transition to RRC-Connected state to send such reports. This needs to be clarified and evaluated together with SA6. + +**NOTE:** It is up to SA6 to determine if the amount of Listener Reports should be reduced and how it can be achieved, which is independent from SA2.**Solution #20,** + +The solutions enables that the UE requests multicast MBS session join/leave during mobility registration update procedure. In addition to the associated PDU Session status, the multicast session information container is also included in the Registration Request message to indicate whether the UE wants to join or leave (e.g. due to triggers from the application layer) or remain joined in one or more multicast MBS sessions associated with the PDU Session, so that: + +- the multicast MBS session join/leave can be performed during the registration procedure. +- the network will not trigger multicast MBS session establishment towards the NG-RAN if the UE indicates leaving the multicast MBS session. + +Considering UE(s) in RRC Idle or RRC Inactive state can join the multicast MBS session using mobility registration procedure, and then receive multicast data in RRC Inactive state, it will bring the benefits of less signalling interactions, time and radio resource consumption. + +Utilizing the mobility registration to indicate “join” or “leave”, it requires the conditions for mobility registration update are met when UE requests session join or leave (e.g. due to pending application layer request). Even if such possibility for one UE may be low, it would be beneficial considering the large number of UEs. + +#### Solution #16, + +The intention is that AF starts a broadcast MBS session in some dense area and the UEs in that area receives MBS data via broadcast, and when moving out of broadcast coverage, UEs receives data via multicast. + +The decision to suspend the MRB of multicast MBS session in NG-RAN is based on congestion situation in NG-RAN, and the decision of start broadcast session logic in GCS AS is based on the counting of UEs in a specific area. A possible misconfiguration is that in some areas, AF does not start the broadcast session, but NG-RAN suspends the MRB of the multicast session, which may require those joined UEs to fall back to unicast. It is also possible that in some areas, AF started the broadcast and NG-RAN keeps the MRB of the multicast session, which will cause double resource consumption. + +Furthermore, to start broadcast MBS session effectively, accurate and frequent location reports are required, which may also lead to capacity bottlenecks. There is a trade-off between accuracy and frequency of the location reports and how fast switching between broadcast and multicast can be achieved. + +#### Solution #17, + +The intention is to shorten the group call setup time by letting the AMF be aware of UE join and get the list of UEs for group paging ready and constantly calculating the group paging area, which can avoid processing of the UE list when receiving enable group reachability requests. Whenever the multicast MBS session is activated, the AMF can trigger the group paging when receiving the first request (enable group reachability request or multicast session activation request). Furthermore, the AMF triggers a group paging for all the joined CM-IDLE UEs in the AMF, instead of triggering group paging per enable group reachability request. This solution is not intended to address the bottleneck in air interface. + +As service request handling constitute most of the delay for a CM-IDLE UE in MBS session activation, Solution #17 can reduce the group call setup time but not significantly. The solution requires AMF constantly updates the group paging area for UE CM state change when MBS session is inactive. This requires the involved SMFs to include the joining/leaving message outside the N2SM information. + +Another aspect, it may minimize the number of group paging requests from the AMF to the NG-RANs, which reduce the number of interactions between the AMF and the NG-RANs. If the frequency of multicast MBS session activation is low, the performance improvement will not be significant as well. Also, this depends on how many SMFs are involved in the MBS session, e.g. if there is only one SMF, the differences are not that much. + +#### Solution #31, + +This solution enables the AF to take actions (e.g. releasing low priority group communications which is using the MBS, switching the group call to broadcast MBS session, by the NG-RAN informs the UEs of the resource allocation failure and then the UEs further informs the AF. + +It is not clear how the solution works in MBS session activation procedure. It requires further explanation on whether such application-level feedback works when the cell is overloaded. And it is to be evaluated the benefits compared with the solution using the join failure event report from the UE to the AF which exist already. + +## 8 Conclusions + +*Editor's note: This clause will list conclusions that have been agreed during the course of the study item activities.* + +### 8.1 Key Issue #1: MBS session reception in RRC Inactive + +#### 8.1.1 Conclusions + +The following conclusions is proposed for KI#1: + +- It is possible to keep some UEs within the same MBS session in RRC\_CONNECTED and some in RRC\_INACTIVE state. NG-RAN nodes take the responsibility to determine (e.g. during congestion) which UE(s) within an MBS multicast session will be moved from CM-CONNECTED with RRC CONNECTED to CM-CONNECTED with RRC Inactive state and still receive MBS session data. +- The 5GC provides information about the MBS session as specified for Rel-17 and may provide additional assistance information to help NG-RAN to determine whether to apply delivery enabling reception by UEs in RRC\_Inactive state for an MBS session and which UE(s) to be moved to RRC Inactive state. +- The assistance information may include recommendations whether to enable delivery for reception in RRC\_Inactive state for an MBS session and information about UEs that should preferably be kept in RRC\_Connected state, i.e. the MBS session level and UE level MBS assistance information, and may be provided by the AF to 5GC and then to NG-RAN. +- For MBS session level assistance information: + - The existing MBS session QoS parameters (e.g. ARP, 5QI) can be used as the MBS session level assistance information by NG-RAN to differentiate different MBS sessions. +- For UE level MBS assistance information: + - The UE level MBS assistance information is an optional new parameter and set per MBS session. It is indicated by the AF to inform the network whether from the expected traffic pattern of the UE the indicated UE is preferred to be kept in the RRC Connected state even if it is able according to its radio capabilities to receive the MBS session data in RRC\_INACTIVE state, e.g. a frequent talker. + +NOTE 1: The protocol detail and how the assistance information is formatted (e.g. as a flag, multiple choices (high/low/medium) or multiple integer values of the assistance information for the expected traffic pattern) is to be defined in normative phase and requires RAN WG feedback. + +- The AF provides the UE level MBS assistance information as part of MBS subscription data during External Parameter Provisioning procedures as defined in clause 6.4.2 of TS 23.247 [4]. +- The SMF provides the received UE level MBS assistance information to NG-RAN node as part of the PDU session information in N2 SM Info and sent to NG-RAN via AMF. +- NG-RAN use the MBS session level and UE level MBS assistance information as help for the decisions on whether to enable delivery for reception in RRC\_INACTIVE state for an MBS session and/or on which UEs to keep in RRC\_CONNECTED or RRC\_INACTIVE state. How NG-RAN performs those decisions is up to NG-RAN implementation. + +NOTE 2: How the NG-RAN handles the situation without assistance information for RRC Inactive multicast MBS data reception is to be determined by RAN WGs. + +NOTE 3: What is defined in clause 5.3.3.2.5 of TS 23.501 [2] for "RRC Inactive Assistance Information" is sent by AMF to NG-RAN and may be used by NG-RAN together with any other MBS session level assistance information and UE level MBS assistance information for deciding whether to send a UE to RRC Inactive state. + +- When the MBS session is activated, the UEs in RRC Inactive state in cells, where the MBS session is delivered allowing RRC-inactive reception, should be able to remain in RRC Inactive state for receiving the MBS session data. + +- For group paging, the network notifies which MBS session is to be activated. For the UE in RRC\_INACTIVE state how the group paging is handled will be decided by RAN WGs. +- How NG-RAN notifies the UE that the MBS session is re-activated and whether the MBS session is allowed to be received in RRC-inactive state will be decided by RAN WGs. +- When an RRC\_INACTIVE UE is in the process of receiving ongoing MBS session data and moves to a new cell within the RNA, the UE shall be able to receive MBS session data. +- When the UE moves outside the RNA, the UE performs UE Triggered Connection Resume in RRC Inactive procedure to the target RAN node as per existing procedures in TS 23.502 [3]. +- When the UE receives the MBS data in RRC Inactive state and move out of the RNA area but Connection resume fails, it follows existing procedures and transition to CM-IDLE. When the UE transition to CM-IDLE since is not able to receive the MBS multicast data at the new cell, the UE initiates the mobility registration update or Service Request procedure and activates the associated PDU session, so that the shared tunnel (if not already established) or the individual delivery can be established towards the NG-RAN node for multicast data delivery to the UE. +- When the UE moves outside the RA, the UE performs mobility registration procedure and as per the existing procedure in clause 5.3.3.2.5 of TS 23.501 [2] for "Mobile initiated NAS signalling procedure" for UEs in CM-CONNECTED with RRC Inactive state, the UE will resume the RRC Connection. +- During the handover procedure, the SMF includes the "MBS assistance information for RRC Inactive" if any in N2 SM Info and sent to NG-RAN via AMF. + +The following requirements, which need be supported by RAN WGs, are concluded: + +- Backward compatibility with Rel-17 UEs not supporting the RRC\_Inactive reception of MBS multicast data needs to be ensured. +- RAN WG2 define UE radio capability for MBS reception in RRC\_INACTIVE state. +- NG-RAN nodes decide for which MBS sessions to apply delivery enabling reception in RRC\_Inactive state. The NG RAN nodes handling RRC-Connected UE in an MBS multicast session also decides whether the UEs can transition to RRC\_Inactive state and may consider assistance information from the 5G core network for that decision. How NG-RAN performs those decisions is up to NG-RAN implementation. +- When the MBS session is activated, the UE in RRC Inactive state in cells where the MBS session is delivered in the delivery mode for RRC-inactive reception should be able to remain in RRC Inactive state for receiving the MBS session data. +- When the UE is in RRC Inactive state and moves within the RNA, it shall be able to continue receiving DL multicast MBS data unless it leaves the MBS service area. + +## 8.2 Key Issue #2: MOCN network sharing + +For conclusions, the following aspects will be considered: + +- For solutions where the broadcast MBS sessions for different PLMNs are established towards a NG-RAN node, the NG-RAN node shall be able to identify the same MBS service and avoid multiple deliveries over radio. +- A solution compatible with Rel-17 UEs is preferred. +- A solution compatible with Rel-17 NG-RAN is preferred. +- The AF may provide associated session identifier (SSM used by AF) additionally to the NG-RAN nodes via 5GC so that the shared NG-RAN nodes can determine that the multiple broadcast MBS sessions are transmitting same content for the same MBS service (i.e. Soln#2 and Soln#7 SSM option), or +- The association of MBS session identifiers may be configured in NG-RAN, where there is no requirement on AF to provide associated session identifier.- It should be possible not to establish all the shared delivery tunnels to the same NG RAN from different PLMNs for the same MBS service. + +- The solution should support the scenario where all NG-RAN nodes are shared by PLMNs and the scenario where only part of the NG-RAN nodes are shared by PLMNs. + +## 8.3 Key Issue #3: On demand multicast MBS session + +The use case in KI#3 is already possible in Rel-17 and no further normative work is needed in Rel-18. + +## 8.4 Key Issue #4: Group message delivery + +For group message delivery, the following principles have been agreed: + +- It shall support reliable delivery of group messages via MBS. Full-Service Mode solution, which utilize the Object Delivery Method offered by the MBSF/MBSTF, is adopted. + +NOTE: The AF can invoke the Nmbsmf service operations offered by the MB-SMF (optionally via the NEF) for Transport Only Mode, as supported in Rel-17. + +- It shall support group message delivery request from AF. The group message is included in the group message delivery request. +- It shall support the cancellation of a previously accepted group message delivery request. +- It shall support the modification of a previously accepted group message delivery request. +- It shall be applied for general group message delivery purposes (not limited to MTC devices). +- The AF may be informed about the areas where MBS is not supported. The support of this feature is optional. + +## 8.5 Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices + +The following principles are applied for normative work to allow UEs to receive multicast/broadcast MBS data when they are using power saving mechanisms (e.g. eDRX, MICO with active time etc): + +- Solution #14 is used as the basis for normative work with the following further clarifications: + - The UE is configured by the AF via the service announcement about a session start time and a possible sequence of scheduled activation times when the AF may activate the MBS session and transmit MBS data. + - At the session start time and the possible scheduled activation times, the UEs apply the procedures of Solution #14 to receive MBS data. This means that for an MBS multicast session, if the UE has already joined the MBS session as defined in clause 7.2.1.3 of TS 23.247 [4], at the possible scheduled activation times, IDLE UEs need to listen for paging requests and if paged by the network with group paging follow the existing procedures in clause 7.2.5.2 of TS 23.247 [4]. In this case, how long the UE need to listen to paging is left up to UE implementation. + - If the UE has not previously joined the MBS multicast session, at the possible scheduled activation time it performs MBS join procedure as currently defined in clause 7.2.1.3 of TS 23.247 [4]. Whether the UE performs MBS join procedure in advance and stays "joined" or every time at activation time is left up to UE implementation. + - How to support NR capability-limited (RedCap) UEs in MBS will be decided in normative phase considering possible related decisions of RAN WGs + +## 8.6 Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs + +No normative work on this key issue will be performed by SA WG2 in Rel-18. + +NOTE 1: Solutions addressing both key issue #6 and other key issues can be selected in conclusions for other key issues. + +NOTE 2: It is assumed that: + +- An AF e.g. MCX AS is able to create additional broadcast session for the same service as per UE feedback; +- An AF e.g. MCX server can create broadcast and multicast session for the same service; and +- Public Safety UE procedures can be enhanced to reduce uplink signalling (e.g. location reports) without any further impacts in SA2 specifications. It is up to SA6 to decide upon such procedures. + +NOTE 3: For public safety services, based on existing QoS mechanisms, the NG-RAN ensures that public safety UEs are able to complete the setup of the MBS services and then operate according to regulation and operator policy, e.g. pre-emption mechanisms can be activated for PDU sessions unrelated to MBS sessions, resulting in some UEs already in RRC\_CONNECTED state being transitioned to RRC\_IDLE or RRC\_INACTIVE to "make room" for some of the newly arrived mission critical enabled UEs to get to the RRC\_CONNECTED state necessary to start/complete their association with the public safety group of interest. Normative work is not required. + +## Annex A: Public Safety use cases of large number of UEs in a single cell + +This Annex covers the case when the mission critical enabled UEs are concentrated in a single cell. + +A general public safety use case, for example, can assume that: + +- a cell with UEs receiving a mix of public safety and non public safety services: some UEs receive only non public safety services, other UEs receive only public safety services, being engaged in one or more mission critical one-to-one call or on single or multiple simultaneous group calls (e.g. PTT and video), and yet other UEs receive both public safety and non-public safety services at the same time; +- the number of UEs in RRC\_CONNECTED state in the cell is at, or very near to, the limit of the number of UEs in RRC\_CONNECTED state that can be accepted in that cell due to various limiting factors; +- at that moment, a number of mission critical enabled UEs (e.g. the occupants of a fire truck) interested in participating in group calls associated with a specific public safety group arrive roughly simultaneously in the cell with their UEs in various RRC states (or possibly, powered off) and attempt to perform the necessary connection steps to the RAN, CN and AF, to be able to connect and associate themselves to the public safety group of interest; +- this situation results in a larger number of UEs being or attempting to get in RRC\_CONNECTED state than can be admitted in the cell in that state. The admission control to the cell and/or pre-emption mechanisms will be activated, resulting in some UEs already in RRC\_CONNECTED state being transitioned to RRC\_IDLE or RRC\_INACTIVE to "make room" for some of the newly arrived mission critical enabled UEs to get to the RRC\_CONNECTED state necessary to start/complete their association with the public safety group of interest; +- some (or all) of the mission critical enabled UEs associated with public safety group(s) of interest which use or intend to use MBS for downlink communication may have to be transitioned to RRC\_INACTIVE or RRC\_IDLE state to ensure that the total number of UEs in the cell in RRC\_CONNECTED state does not exceed the limit for that cell; + +NOTE 1: The transition from RRC\_CONNECTED state should not happen for just arrived public safety UEs before their association with the public safety group of interest is complete, which is needs to be ensured by public safety applications. Some application-function (AF) provided information about specific public safety participants in group calls (e.g. privilege status, priority) may be used to identify which UEs should be kept in RRC\_CONNECTED state and which UEs are candidates for being transitioned to RRC\_INACTIVE or RRC\_IDLE state. + +- whether an MBS Session for public safety is active or inactive, a UE in RRC\_INACTIVE or RRC\_IDLE state, may request transition to RRC\_CONNECTED state to perform unicast uplink transmissions (e.g. to request the floor, send user data, send location reports, etc.). Since the number of UEs already in RRC\_CONNECTED state in the cell may be at or near the cell admissibility limit, one or more UEs already in RRC\_CONNECTED state may need to first be moved to RRC\_INACTIVE or RRC\_IDLE state, in order to "make room" for the UE wanting to transmit; +- while in RRC\_INACTIVE state receiving user data via MBS under a session, a mission critical enabled UE may request (see bullet above), and be able to additionally start receiving public safety service via MBS, in parallel, under another session. + +NOTE 2: Treatment of failure by public safety UEs in RRC\_INACTIVE state to receive MBS downlink transmissions when expected to do so, is left to implementation. + +## Annex B: Change history + +| Change history | | | | | | | | +|----------------|----------|------------|----|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149E | S2-2201354 | - | - | - | TR skeleton (approved in S2-2201354) | 0.0.0 | +| 2022-09 | SA#97-e | SP-220822 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.0.0 | +| 2022-11 | SA#98-e | SP-221111 | - | - | - | 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-48/raw.md b/raw/rel-18/23_series/23700-48/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4174ca5147b99c46f2e3772f572cfd1d792ff9fb --- /dev/null +++ b/raw/rel-18/23_series/23700-48/raw.md @@ -0,0 +1,7770 @@ + + +# 3GPP TR 23.700-48 V18.0.0 (2022-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G System Enhancements for Edge Computing; 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, 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. + +© 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 ..... | 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 ..... | 14 | +| 4 Architectural assumptions and principles ..... | 14 | +| 4.1 Architectural Assumptions..... | 14 | +| 4.2 Architectural Requirements..... | 14 | +| 5 Key issues ..... | 14 | +| 5.1 KI#1: Accessing EHE in a VPLMN when roaming ..... | 14 | +| 5.1.1 Description ..... | 14 | +| 5.1.2 Scenarios..... | 15 | +| 5.1.3 Assumptions ..... | 15 | +| 5.2 KI#2: Fast and efficient network exposure improvements ..... | 15 | +| 5.2.1 Description ..... | 15 | +| 5.2.2 Use cases and scenarios..... | 16 | +| 5.3 KI#3: Policies for finer granular sets of UEs ..... | 16 | +| 5.3.1 Description ..... | 16 | +| 5.3.2 Scenarios..... | 16 | +| 5.3.3 Assumptions ..... | 17 | +| 5.4 KI#4: Influencing UPF and EAS (re)location for collections of UEs..... | 17 | +| 5.4.1 Description ..... | 17 | +| 5.4.2 Scenarios..... | 18 | +| 5.4.3 Assumptions ..... | 18 | +| 5.5 KI#5: GSMA OPG impacts and improvements for EHE operated by separate party ..... | 18 | +| 5.5.1 Description ..... | 18 | +| 5.5.2 Scenarios..... | 18 | +| 5.5.3 Assumptions ..... | 19 | +| 5.6 KI#6: Avoiding UE to switch away from EC PDU Session ..... | 19 | +| 5.6.1 Description ..... | 19 | +| 5.6.2 Scenarios..... | 19 | +| 5.6.3 Assumptions ..... | 20 | +| 5.7 KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI..... | 20 | +| 5.7.1 Description ..... | 20 | +| 5.7.2 Scenarios..... | 20 | +| 5.7.3 Assumptions ..... | 20 | +| 6 Solutions..... | 20 | +| 6.0 Solution-Key issue matrix..... | 20 | +| 6.1 Solution 01 (KI#1): EAS discovery in Home Routed roaming scenario ..... | 22 | +| 6.1.1 Description ..... | 22 | +| 6.1.2 Procedures ..... | 23 | +| 6.1.2.1 EAS discovery when HPLMN has the knowledge of EAS deployment information in VPLMN ..... | 23 | +| 6.1.2.2 EAS discovery when HPLMN does not have the knowledge of EAS deployment information in VPLMN ..... | 24 | +| 6.1.3 Impacts on services, entities and interfaces..... | 25 | +| 6.2 Solution 02 (KI#1): Session Breakout in Visited PLMN..... | 26 | +| 6.2.1 Description ..... | 26 | +| 6.2.2 Procedure ..... | 27 | +| 6.2.3 Impacts on services, entities and interfaces..... | 28 | +| 6.3 Solution 03 (KI#1): EAS (re)discovery procedure in roaming scenario..... | 29 | +| 6.3.1 Description ..... | 29 | + +| | | | +|----------|-------------------------------------------------------------------------------------|----| +| 6.3.2 | Procedures ..... | 29 | +| 6.3.2.1 | EAS discovery procedure in roaming scenario..... | 29 | +| 6.3.2.2 | EAS rediscovery procedure in roaming scenario ..... | 32 | +| 6.3.3 | Impacts on existing entities and interfaces..... | 32 | +| 6.4 | Solution 04 (KI#1): Support EAS (re-)discovery in VPLMN via HR PDU Session..... | 33 | +| 6.4.1 | Description ..... | 33 | +| 6.4.2 | Procedures ..... | 33 | +| 6.4.2.1 | EAS discovery ..... | 33 | +| 6.4.2.2 | EAS re-discovery..... | 36 | +| 6.4.3 | Impacts on services, entities and interfaces..... | 37 | +| 6.5 | Solution 05 (KI#1): Accessing V-EHE via HR PDU Session ..... | 39 | +| 6.5.1 | Description ..... | 39 | +| 6.5.2 | Procedures ..... | 40 | +| 6.5.2.1 | EAS discovery ..... | 40 | +| 6.5.2.2 | EAS re-discovery..... | 41 | +| 6.5.3 | Impacts on services, entities and interfaces..... | 41 | +| 6.6 | Solution 06 (KI#1): URSP solution to support roamers access to EHE in a VPLMN ..... | 42 | +| 6.6.1 | Description ..... | 42 | +| 6.6.2 | Procedures ..... | 43 | +| 6.6.3 | Impacts on Existing Nodes and Functionality..... | 43 | +| 6.7 | Solution 07 (KI#1): Using URSP Rules to Establish an LBO PDU Session..... | 43 | +| 6.7.1 | Description ..... | 43 | +| 6.7.1.1 | General..... | 43 | +| 6.7.1.2 | Procedure ..... | 44 | +| 6.7.2 | Impacts on services, entities and interfaces..... | 44 | +| 6.8 | Solution 08 (KI#1): V-ECS Discovery during Steering of Roaming..... | 45 | +| 6.8.1 | Description ..... | 45 | +| 6.8.1.1 | General..... | 45 | +| 6.8.1.2 | Procedure ..... | 45 | +| 6.8.2 | Impacts on services, entities and interfaces..... | 47 | +| 6.9 | Solution 09 (KI#1): PDU Session configuration from EASDF ..... | 47 | +| 6.9.1 | Description ..... | 47 | +| 6.9.2 | Procedures ..... | 47 | +| 6.9.2.1 | PDU Session configuration from EASDF ..... | 47 | +| 6.9.2.2 | DNS structure ..... | 48 | +| 6.9.3 | Impacts on services, entities and interfaces..... | 49 | +| 6.10 | Solution 10 (KI#1): LBO PDU Session establishment using PLMN criteria in RSD ..... | 49 | +| 6.10.1 | Description ..... | 49 | +| 6.10.2 | Procedure ..... | 50 | +| 6.10.3 | Impacts on services, entities and interfaces..... | 50 | +| 6.11 | Solution 11 (KI#2): Exposure of Network Congestion..... | 51 | +| 6.11.0 | General ..... | 51 | +| 6.11.1 | Procedure..... | 51 | +| 6.11.2 | Impacts on services, entities and interfaces..... | 53 | +| 6.12 | Solution 12 (KI#2): Efficient exposure of RAN information ..... | 54 | +| 6.12.1 | Key Issue mapping ..... | 54 | +| 6.12.2 | Description ..... | 54 | +| 6.12.3 | Procedures ..... | 55 | +| 6.12.3.1 | Subscribing information ..... | 55 | +| 6.12.3.2 | Information report..... | 57 | +| 6.12.4 | Impacts on services, entities and interfaces..... | 57 | +| 6.13 | Solution 13 (KI#2): Fast and efficient network exposure improvements ..... | 58 | +| 6.13.1 | Introduction ..... | 58 | +| 6.13.2 | Functional Description ..... | 58 | +| 6.13.3 | Procedures ..... | 58 | +| 6.13.4 | Impacts on services, entities and interfaces..... | 60 | +| 6.14 | Solution 14 (KI#4): Group Management ..... | 60 | +| 6.14.1 | Introduction ..... | 60 | +| 6.14.2 | Functional Description ..... | 60 | +| 6.14.3 | Procedures ..... | 62 | +| 6.14.4 | Impacts on services, entities and interfaces..... | 64 | +| 6.15 | Solution 15 (KI#4): Selection of common DNAI ..... | 64 | + +| | | | +|----------|---------------------------------------------------------------------------------------|----| +| 6.15.1 | Introduction ..... | 64 | +| 6.15.2 | Functional Description ..... | 65 | +| 6.15.3 | Procedures ..... | 65 | +| 6.15.3.1 | General..... | 65 | +| 6.15.3.2 | Selection of the common DNAI ..... | 67 | +| 6.15.3.3 | EAS selection and re-selection using ECS option, preconfigured..... | 68 | +| 6.15.3.4 | EAS selection and re-selection using ECS option, dynamic invoke of SCMF ..... | 69 | +| 6.15.3.5 | EAS selection and re-selection via application layer..... | 71 | +| 6.15.4 | Impacts on services, entities and interfaces..... | 72 | +| 6.16 | Solution 16 (KI#4): Selecting the same EAS/DNAI for collection of UEs ..... | 72 | +| 6.16.1 | Description ..... | 72 | +| 6.16.2 | Procedures ..... | 73 | +| 6.16.2.1 | EAS discovery procedure ..... | 73 | +| 6.16.2.2 | Synchronization procedure for EAS IP/DNAI ..... | 74 | +| 6.16.3 | Impacts on services, entities and interfaces..... | 75 | +| 6.17 | Solution 17 (KI#4): Application layer EAS selection for collections of UEs ..... | 75 | +| 6.17.1 | Introduction ..... | 75 | +| 6.17.2 | Functional Description ..... | 75 | +| 6.17.3 | Procedures ..... | 76 | +| 6.17.3.1 | EAS selection for multiple UE based application layer ..... | 76 | +| 6.17.4 | Impacts on services, entities and interfaces..... | 77 | +| 6.18 | Solution 18 (KI#4): Discovery of the same EAS for collections of UEs..... | 77 | +| 6.18.1 | Description ..... | 77 | +| 6.18.2 | Procedures ..... | 78 | +| 6.18.2.1 | EASDF-related procedure..... | 78 | +| 6.18.2.2 | Direct DNS response to UE..... | 80 | +| 6.18.2.3 | EAS Discovery Procedure with Local DNS Server/Resolver ..... | 81 | +| 6.18.3 | Impacts on services, entities and interfaces..... | 81 | +| 6.19 | Solution 19 (KI#4): Influencing UPF and EAS (re)location for collections of UEs ..... | 82 | +| 6.19.1 | Introduction ..... | 82 | +| 6.19.2 | Functional Description ..... | 82 | +| 6.19.3 | Procedure ..... | 82 | +| 6.19.3.1 | AF provisioning ad-hoc group information ..... | 82 | +| 6.19.3.2 | Group members served by same SMF ..... | 83 | +| 6.19.4 | Impacts on services, entities and interfaces..... | 84 | +| 6.20 | Solution 20 (KI#5): Global EASDF ..... | 84 | +| 6.20.1 | Description ..... | 84 | +| 6.20.2 | Procedures ..... | 85 | +| 6.20.2.1 | Global EASDF ..... | 85 | +| 6.20.3 | Impacts on services, entities and interfaces..... | 86 | +| 6.21 | Solution 21 (KI#5): EAS Deployment information differentiated by PLMN ID ..... | 86 | +| 6.21.1 | Introduction ..... | 86 | +| 6.21.2 | Functional Description ..... | 86 | +| 6.21.3 | Procedures ..... | 86 | +| 6.21.4 | Impacts on services, entities and interfaces..... | 86 | +| 6.22 | Solution 22 (KI#5): EAS discovery for Edge Node Sharing ..... | 87 | +| 6.22.1 | Introduction ..... | 87 | +| 6.22.2 | Functional description ..... | 87 | +| 6.22.2.0 | Option 0: SMF configuration..... | 87 | +| 6.22.2.1 | Option 1: Shared EASDF ..... | 87 | +| 6.22.2.2 | Option 2: Per-PLMN EASDFs ..... | 88 | +| 6.22.3 | Procedures ..... | 90 | +| 6.22.3.0 | Option 0: SMF configuration..... | 90 | +| 6.22.3.1 | Option 1: Shared EASDF ..... | 90 | +| 6.22.3.2 | Option 2: Per-PLMN EASDFs ..... | 92 | +| 6.22.4 | Impact on existing entities and interfaces..... | 94 | +| 6.22.4.0 | Option 0: SMF configuration..... | 94 | +| 6.22.4.1 | Option 2: Shared EASDF ..... | 94 | +| 6.22.4.2 | Option 3: Per-PLMN EASDFs ..... | 94 | +| 6.23 | Solution 23 (KI#5): Improvements for EHE operated by separate party..... | 94 | +| 6.23.1 | Introduction ..... | 94 | +| 6.23.2 | Functional Description ..... | 95 | + +| | | | +|----------|-------------------------------------------------------------------------------------------------------|-----| +| 6.23.3 | Solution Details ..... | 95 | +| 6.24 | Solution 24 (KI#1): Reuse Option D after UL-CL Insertion ..... | 96 | +| 6.24.1 | Description ..... | 96 | +| 6.24.2 | Procedure ..... | 97 | +| 6.24.3 | Impacts on services, entities, and interfaces ..... | 97 | +| 6.25 | Solution 25 (KI#1): EAS discovery in VPLMN via V-EASDF for a HR PDU Session ..... | 98 | +| 6.25.1 | High level description ..... | 98 | +| 6.25.2 | Procedures ..... | 99 | +| 6.25.2.1 | PDU Session establishment and EAS discovery ..... | 99 | +| 6.25.2.2 | EAS rediscovery due to UE or application mobility ..... | 101 | +| 6.25.3 | Impacts on services, entities and interfaces ..... | 102 | +| 6.26 | Solution 26 (KI#1): SM Policy for HR Session Breakout in VPLMN ..... | 103 | +| 6.26.1 | Description ..... | 103 | +| 6.26.2 | Procedures ..... | 104 | +| 6.26.2.1 | Option 1: Indirect interaction between V-PCF and H-PCF ..... | 104 | +| 6.26.2.2 | Option 2 — Direct interaction between V-PCF and H-PCF ..... | 105 | +| 6.26.3 | Impacts on existing entities and interfaces ..... | 106 | +| 6.27 | Solution 27 (KI#1): EAS discovery with dynamic setup of a LBO PDU Session ..... | 107 | +| 6.27.1 | High level description ..... | 107 | +| 6.27.2 | Procedures ..... | 108 | +| 6.27.3 | Impacts on services, entities and interfaces ..... | 109 | +| 6.28 | Solution 28 (KI#1): Support edge computing in Roaming ..... | 109 | +| 6.28.1 | Description ..... | 109 | +| 6.28.1.1 | General ..... | 109 | +| 6.28.1.2 | ECS configuration information Configuration Information configuration in UE ..... | 110 | +| 6.28.2 | Procedures ..... | 110 | +| 6.28.2.1 | UE registers in VPLMN and URSP rules updated timely ..... | 110 | +| 6.28.2.2 | UE registers in VPLMN and URSP rules are not updated timely ..... | 111 | +| 6.28.2.3 | HR session to support Edge computing ..... | 111 | +| 6.28.2.4 | When UE moving into VPLMN and the original EC-session are impacted ..... | 113 | +| 6.28.3 | Impacts on services, entities and interfaces ..... | 113 | +| 6.29 | Solution 29 (KI#3): Use of Internal Group ID and constraints in EDI ..... | 114 | +| 6.29.1 | High level description ..... | 114 | +| 6.29.2 | Impacts on services, entities and interfaces ..... | 115 | +| 6.30 | Solution 30 (KI#3): Policies referring to "Allowed services" and/or "Subscriber categories" ..... | 115 | +| 6.30.1 | Description ..... | 115 | +| 6.30.2 | Procedures ..... | 116 | +| 6.30.3 | Impacts on Existing Nodes and Functionality ..... | 117 | +| 6.31 | Solution 31 (KI#3): Providing traffic offload policy for a set of UEs with service information ..... | 118 | +| 6.31.1 | Description ..... | 118 | +| 6.31.2 | Procedures ..... | 118 | +| 6.31.3 | Impacts on services, entities and interfaces ..... | 120 | +| 6.32 | Solution 32 (KI#3): Offload policy for finer granular set of UEs ..... | 121 | +| 6.32.1 | Description ..... | 121 | +| 6.32.2 | Procedures ..... | 121 | +| 6.32.3 | Impacts on services, entities and interfaces ..... | 122 | +| 6.33 | Solution 33 (KI#3): AF requests offload policy for sets of UEs ..... | 122 | +| 6.33.1 | Description ..... | 122 | +| 6.33.2 | Procedures ..... | 123 | +| 6.33.3 | Impacts on services, entities and interfaces ..... | 123 | +| 6.34 | Solution 34 (KI#4): Selecting the same EAS/DNAI for collection of UEs ..... | 123 | +| 6.34.1 | Description ..... | 123 | +| 6.34.2 | Procedure ..... | 125 | +| 6.34.3 | Impacts on services, entities and interfaces ..... | 126 | +| 6.35 | Solution 35 (KI#4): Providing dedicated (re)location information as traffic routing information ..... | 126 | +| 6.35.1 | Description ..... | 126 | +| 6.35.2 | Procedures ..... | 127 | +| 6.35.3 | Impacts on services, entities and interfaces ..... | 130 | +| 6.36 | Solution 36 (KI#4): Providing dedicated (re)location information as EAS Deployment information ..... | 130 | +| 6.36.1 | Description ..... | 130 | +| 6.36.2 | Procedures ..... | 131 | +| 6.36.3 | Impacts on services, entities and interfaces ..... | 133 | + +| | | | +|----------|------------------------------------------------------------------------------------------|-----| +| 6.37 | Solution 37 (KI#4): (Re)location of same EAS and coordination across UEs ..... | 134 | +| 6.37.1 | Introduction ..... | 134 | +| 6.37.2 | Functional Description ..... | 134 | +| 6.37.3 | Solution Details ..... | 134 | +| 6.37.3.1 | EAS (re)location to the ad hoc group member UEs ..... | 134 | +| 6.37.3.2 | Updating EAS ID in the Group Info ..... | 135 | +| 6.37.3.3 | Collection of UEs based on 5GC criteria..... | 136 | +| 6.37.4 | Impacts on services, entities and interfaces..... | 136 | +| 6.38 | Solution 38 (KI#5): EAS Discovery for EHE shared with other PLMN ..... | 136 | +| 6.38.1 | Description ..... | 136 | +| 6.38.2 | Procedures ..... | 137 | +| 6.38.2.1 | Option1 - NEF-based EDI provision to serving Operator ..... | 137 | +| 6.38.2.2 | Option2 - EWBI/AF-based EDI provision to serving Operator ..... | 138 | +| 6.38.3 | Impacts on services, entities and interfaces..... | 139 | +| 6.39 | Solution 39 (KI#1, KI#5): Support EAS relocation of inter-PLMN..... | 139 | +| 6.39.1 | Description ..... | 139 | +| 6.39.2 | Procedures ..... | 141 | +| 6.39.2.1 | EAS relocation from VPLMN to HPLMN (KI#1) ..... | 141 | +| 6.39.2.2 | EAS relocation from HPLMN to VPLMN (KI#1) ..... | 142 | +| 6.39.2.3 | EAS relocation between operators via N6 (KI #5) ..... | 143 | +| 6.39.3 | Impacts on services, entities and interfaces..... | 144 | +| 6.39.3.1 | EAS relocation between VPLMN and HPLMN (clause 6.39.2.1 and 6.39.2.2) ..... | 144 | +| 6.39.3.2 | EAS relocation between operators via N6 (clause 6.39.2.3) ..... | 145 | +| 6.40 | Solution 40 (KI#5): EAS discovery for shared EHE ..... | 145 | +| 6.40.1 | Introduction ..... | 145 | +| 6.40.2 | Functional description ..... | 145 | +| 6.40.3 | Procedures ..... | 147 | +| 6.40.4 | Impacts on existing entities and interfaces..... | 148 | +| 6.41 | Solution 41 (KI#6): Controlling non-3GPP access of EC traffic via URSP and ATSSS ..... | 148 | +| 6.41.1 | High level description..... | 148 | +| 6.41.2 | Procedures ..... | 149 | +| 6.41.3 | Impacts on services, entities and interfaces..... | 150 | +| 6.42 | Solution 42 (KI#6): Network-guided EC traffic switching..... | 151 | +| 6.42.1 | General ..... | 151 | +| 6.42.1.1 | Introduction..... | 151 | +| 6.42.1.2 | Description..... | 151 | +| 6.42.1.3 | WLAN offload guided by the network ..... | 151 | +| 6.42.2 | Procedures ..... | 152 | +| 6.42.3 | Impacts to existing nodes ..... | 153 | +| 6.43 | Solution 43 (KI#6): Network-based solution for keeping EC traffic on 3GPP Access ..... | 153 | +| 6.43.1 | Description ..... | 153 | +| 6.43.2 | Procedures ..... | 154 | +| 6.43.2.1 | Network sides rejects EC-PDU Sessions handover from 3GPP Access to non-3GPP Access ..... | 154 | +| 6.43.2.2 | UE decides PDU Session handover according to NWDAF analytics ..... | 154 | +| 6.43.4 | Impacts on services, entities and interfaces..... | 156 | +| 6.44 | Solution 44 (KI#6): EAS traffic switching avoidance ..... | 156 | +| 6.44.1 | Description ..... | 156 | +| 6.44.2 | Procedures ..... | 157 | +| 6.44.3 | Impacts on existing entities and interfaces..... | 158 | +| 6.45 | Solution 45 (KI#1, KI#6): Application selected PDU Session ..... | 158 | +| 6.45.1 | Description ..... | 158 | +| 6.45.2 | Procedures ..... | 159 | +| 6.45.2.1 | Procedures for Application selected PDU Session ..... | 159 | +| 6.45.3 | Impacts on services, entities and interfaces..... | 159 | +| 6.46 | Solution 46 (KI#6): Avoid UE switching on-going EC traffic away from 3GPP access ..... | 159 | +| 6.46.1 | Description ..... | 159 | +| 6.46.2 | Procedure ..... | 159 | +| 6.46.3 | Impacts on services, entities and interfaces..... | 160 | +| 6.47 | Solution 47 (KI#6): Avoiding Switch Away Based on an SMF Indication..... | 161 | +| 6.47.1 | Description ..... | 161 | +| 6.47.1.1 | General ..... | 161 | +| 6.47.1.2 | Procedure ..... | 161 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------|-----| +| 6.47.2 | Impacts on services, entities and interfaces..... | 162 | +| 6.48 | Solution 48 (KI#6): Avoiding Switch Away Based on an Indication in the URSP..... | 163 | +| 6.48.1 | Description ..... | 163 | +| 6.48.1.1 | General..... | 163 | +| 6.48.1.2 | Procedure ..... | 163 | +| 6.48.2 | Impacts on services, entities and interfaces..... | 163 | +| 6.49 | Solution 49 (KI#6): URSP based solution to avoid UE to switch away from Edge PDU Session..... | 163 | +| 6.49.1 | Introduction ..... | 163 | +| 6.49.2 | Functional Description ..... | 164 | +| 6.49.3 | Procedure..... | 164 | +| 6.49.4 | Impacts on services, entities and interfaces..... | 165 | +| 6.50 | Solution 50 (KI#7): Obtain and maintain mapping table between IP address/IP range with DNAI ..... | 165 | +| 6.50.1 | Key Issue mapping ..... | 165 | +| 6.50.2 | Description ..... | 165 | +| 6.50.3 | Procedures ..... | 166 | +| 6.50.4 | Impacts on existing entities and interfaces..... | 166 | +| 6.51 | Solution 51 (KI#7): EDI holding the IP address to DNAI mapping..... | 166 | +| 6.51.1 | High level description..... | 166 | +| 6.51.2 | High level procedures..... | 167 | +| 6.51.2.1 | Provisioning ..... | 167 | +| 6.51.2.2 | Providing IP address to DNAI mapping ..... | 167 | +| 6.51.3 | Impacts on services, entities and interfaces..... | 168 | +| 6.52 | Solution 52 (KI#7): AF obtaining target DNAI provided by NEF ..... | 168 | +| 6.52.1 | Description ..... | 168 | +| 6.52.2 | Procedure..... | 169 | +| 6.52.3 | Impacts on services, entities and interfaces..... | 169 | +| 6.53 | Solution 53 (KI#1): EDC-based EAS discovery for HR PDU Session with Session Breakout ..... | 170 | +| 6.53.1 | High level description..... | 170 | +| 6.53.2 | Procedures ..... | 170 | +| 6.53.3 | Impacts on services, entities and interfaces..... | 172 | +| 6.54 | Solution 54 (KI#4): PCF controlling common DNAI..... | 173 | +| 6.54.1 | Description ..... | 173 | +| 6.54.2 | Procedure..... | 173 | +| 6.54.3 | Impacts on Existing Nodes and Functionality..... | 173 | +| 6.55 | Solution 55 (KI#5): Access the shared EAS via N9 tunnel ..... | 173 | +| 6.55.1 | Description ..... | 173 | +| 6.55.2 | Procedure..... | 174 | +| 6.55.2.1 | Determine target DNAI in PLMN A according to EAS IP address ..... | 174 | +| 6.55.2.2 | SMF recovers or obtain the mapping table to determine the target DNAI..... | 174 | +| 6.55.2.3 | EAS discovery procedure and access the shared EAS via N9 tunnel..... | 175 | +| 6.55.3 | Impacts on services, entities and interfaces..... | 177 | +| 7 | Evaluation ..... | 177 | +| 7.1 | Evaluation for KI#1: Accessing EHE in a VPLMN when roaming ..... | 177 | +| 7.1.1 | Evaluation for scenario 1 (via LBO PDU Session)..... | 177 | +| 7.1.2 | Evaluation for scenario 2 (via HR PDU Session) ..... | 179 | +| 7.1.3 | Evaluation for ECS address delivery aspects ..... | 181 | +| 7.2 | Evaluation for KI#2: Fast and efficient network exposure improvements ..... | 183 | +| 7.3 | Evaluation for KI#3: Policies for finer granular sets of UEs ..... | 183 | +| 7.4 | Evaluation for KI#4: Influencing UPF and EAS (re)location for collections of UEs..... | 184 | +| 7.5 | Evaluation for KI#5: GSMA OPG impacts and improvements for EHE operated by separate party ..... | 186 | +| 7.6 | Evaluation for KI#6: Avoiding UE to switch away from EC PDU Session..... | 187 | +| 7.7 | Evaluation for KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI..... | 189 | +| 8 | Conclusions..... | 190 | +| 8.1 | Conclusion for KI#1: Accessing EHE in a VPLMN when roaming..... | 190 | +| 8.1.1 | Conclusion for scenario 1 (via LBO PDU Session)..... | 190 | +| 8.1.2 | Conclusion for scenario 2 (via HR PDU Session)..... | 190 | +| 8.1.3 | Conclusion for ECS Address Configuration Information delivery ..... | 191 | +| 8.2 | Conclusion for KI#2: Fast and efficient network exposure improvements ..... | 192 | +| 8.3 | Conclusion for KI#3: Policies for finer granular sets of UEs ..... | 192 | +| 8.4 | Conclusion for KI#4: Influencing UPF and EAS (re)location for collections of UEs..... | 193 | + +8.5 Conclusion for KI#5: GSMA OPG impacts and improvements for EHE operated by separate party ..... 194 +8.6 Conclusion for KI#6: Avoiding UE to switch away from EC PDU Session..... 195 +8.7 Conclusion for KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI..... 195 +**Annex A: Change history ..... 196** + +## 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 describes key issues and solutions for the phase 2 of the system enhancements for Edge Computing in 5GS. + +Edge Computing is supported in 5GS since Rel-15. During Rel-17 FS\_enh\_EC study described in TR 23.748 [4], further enhancements for supporting Edge Computing have been studied, including discovery and re-discovery of EAS, edge relocation etc. 4 key issues from FS\_enh\_EC study have been concluded and progressed in TS 23.548 [3]. Some other issues were raised during the Rel-17 study but not studied due to the time limitation in Rel-17. + +This technical report will document the study of potential system enhancements for enhanced edge computing support, including: + +- improvements to roaming, to support access to EHE in a VPLMN (WT#1); +- defining use cases that may benefit from exposure of additional data via the Local UPF/NEF including describing (on a high level) the characteristics of the data and data delivery to fulfil the use cases; investigating the solutions and their feasibility and suitability for improved network exposure of UE traffic related information to common Edge Application Server via Local UPF/NEF, such as network congestion status (WT#3); + +NOTE 1: XR/media and AI/ML services specific QoS information exposure are to be studied in corresponding study items with considering the same exposure framework as defined by this study. + +NOTE 2: This objective will look at the use cases and the data to be exposed but not at the actual UPF exposure mechanism or UPF-originated data, if/when already covered by FS\_UPEAS. + +- investigating the potential need and solutions for supporting offload policies to match more granular sets of UE(s) without exposing operator-internal configurations to 3rd party AFs (WT#5); +- investigating the potential need and solutions to influence of PSA-UPF and EAS (re)location for collection of UEs, e.g. in scenarios when UE(s) should use the same EAS and are not members of a pre-defined group (WT#6); +- investigating potential impacts related to the GSMA Operator Platform Group work, and potential improvements related with 5GC and EHE being operated by different organizations (WT#7); +- investigating the potential need and solutions to avoid the UE to switch the EC traffic away from the EC PDU Session and 5GS altogether, due to conflicting connectivity preferences in the device (e.g. via means outside of 3GPP connectivity, e.g. non-integrated Wifi) (WT#8); +- investigating the potential solutions for the AF to be able to obtain/determine the DNAI that is associated to a certain selected EAS, for subsequent use with already defined services provided to the AF (WT#9). + +# 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)". +- [3] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". + +- [4] 3GPP TR 23.748: "Study on enhancement of support for Edge Computing in 5G Core network (5GC)". +- [5] GSMA OPG.02: "Operator Platform Telco Edge Requirements", . +- [6] SP-210583: "Reply LS to GSMA Operator Platform Group on edge computing definition and integration", SA#92e. +- [7] IETF RFC 5681: "TCP Congestion Control". +- [8] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [9] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". +- [10] 3GPP TR 23.700-85: "Study on enhancement of 5G User Equipment (UE) policy". +- [11] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [12] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [13] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS)". +- [14] 3GPP TS 38.415: "NG-RAN; PDU session user plane protocol". +- [15] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [16] 3GPP TS 23.003: "Numbering, addressing and identification". +- [17] 3GPP TS 29.519: "Usage of the Unified Data Repository Service for Policy Data, Application Data and Structured Data for Exposure". +- [18] 3GPP TS 29.503: "Unified Data Management Services". +- [19] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [20] S2-2203633: "LS on UPF selection based on DNAI", SA2#151e. +- [21] 3GPP TR 23.700-60: "Study on XR (Extended Reality) and media services". + +--- + +## 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], TS 23.548 [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]. + +### 3.2 Void + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2], TS 23.548 [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]. + +| | | +|------|---------------------------------------| +| EACI | ECS Address Configuration Information | +| EDI | Edge Deployment Information | + +--- + +## 4 Architectural assumptions and principles + +### 4.1 Architectural Assumptions + +Existing solutions defined in Rel-15, Rel-16 and Rel-17 will be considered as baseline in this study. + +The architecture for support of Edge Computing in 5GC shall be based on the following architecture assumptions: + +- the architecture for Edge computing specified in Release 17 is used as basis for further potential enhancement; +- the Edge Hosting Environment (EHE) can be under the control of the serving network operator or a 3rd party; +- interconnectivity between EHEs of different operators cannot be assumed to be available for all deployments. + +### 4.2 Architectural Requirements + +- The solutions should minimize the impact on the application layer. + +--- + +## 5 Key issues + +### 5.1 KI#1: Accessing EHE in a VPLMN when roaming + +#### 5.1.1 Description + +The purpose of this key issue is to define 5GS improvements to support the UE access to an EHE in a VPLMN. + +Two scenarios (i.e. UE accessing EHE in VPLMN via an LBO PDU Session and UE accessing EHE in VPLMN via a PDU Session established as HR) are described in clause 5.1.2. + +For the scenario using LBO PDU Session, potential solutions should address the following: + +- how to establish the LBO PDU Session towards the correct S-NSSAI/DNN pair in order to access an EHE in the VPLMN; +- how to support Rel-17 edge computing related procedures, such as EAS (re-)discovery, as specified in clause 6 of TS 23.548 [3]. + +For the scenario using a PDU Session with a PSA in the HPLMN, potential solutions should address the following: + +- how to authorize the PDU Session to support local traffic routing to access an EHE in the VPLMN; +- whether and how to support charging for the local traffic of a PDU Session that supports local traffic routing to access an EHE in the VPLMN; +- how to support Rel-17 edge computing related procedures, such as EAS (re-)discovery, as specified in clause 6 of TS 23.548 [3]; + +- how to ensure proper policy control and QoS enforcement; +- potential impact on Policy and QoS control; +- how to configure the VPLMN ECS address to UE in roaming scenarios; +- how to support the edge relocation in roaming scenarios. + +NOTE 1: Interaction with SA5 is expected regarding charging aspects where needed. + +NOTE 2: Latency needs to be considered and addressed for all scenarios. + +NOTE 3: In Rel-17, the ECS address is provided by UDM, which requires further consideration in scenarios with ECS in a VPLMN. This may need some coordination with SA WG6. + +## 5.1.2 Scenarios + +For a roaming UE, accessing to EHE in VPLMN might be needed to fulfil use cases requiring edge computing. Two main scenarios should be considered: + +- 1) UE accessing V-EHE via a Local Breakout (LBO) PDU Session: + +The scenario supports all connectivity models and assumes that an LBO PDU Session is used to access an EHE in VPLMN for EC applications. + +With a LBO PDU Session, the UE can access an EHE in VPLMN. + +NOTE 1: Two different PDU Sessions are required to access an EHE in VPLMN and Home DN in HPLMN simultaneously. + +- 2) UE accessing V-EHE via a Home Routed (HR) PDU Session (i.e. with PSA in HPLMN): + +This scenario assumes the session breakout for the HR PDU Session is used to access EHE in VPLMN for EC application. + +With a single PDU Session, UE can access an EHE in VPLMN and also the DN in HPLMN. + +NOTE 2: With a single PDU Session and (DNN+S-NSSAI), it can support both EC and non-EC applications in either roaming or non-roaming case. + +To support such PDU Session, it needs to be studied how the UE can access the V-EHE via a HR PDU Session. Two sub-scenarios may be considered: + +- 2.1) HPLMN has the knowledge of EAS deployment information in VPLMN for specific services. The HPLMN triggers EAS discovery and local traffic routing in VPLMN. +- 2.2) HPLMN does not have the knowledge of EAS deployment information in VPLMN. The VPLMN triggers EAS discovery and local traffic routing in VPLMN. + +## 5.1.3 Assumptions + +The solutions do not have to restrict any deployment option or solution options allowed in the previous releases for both for VPLMN and HPLMN. In other words, all deployment options or solution options that are allowed in the previous releases can be assumed. Also, VPLMN and HPLMN may have different deployment options, for example, various EAS (re-)discovery options specified in clause 6 of TS 23.548 [3] or whether to deploy the dynamic PCC. + +# 5.2 KI#2: Fast and efficient network exposure improvements + +## 5.2.1 Description + +This key issue addresses improvements to fast and efficient network exposure of UE traffic related information to Edge Application Server via Local UPF/NEF to support additional information, such as network congestion status. + +This key issue defines use cases that may benefit from exposure of additional data via the Local UPF/NEF including describing (on a high level) the characteristics of the data and data delivery to fulfil the use cases. + +Based on the use cases, this key issue investigates solutions and their feasibility and suitability for improved network exposure of UE traffic related information to common Edge Application Server via Local UPF/NEF, such as network congestion status. In this case, the following issues should be studied: + +- which information and at which level (e.g. per QoS Flow, per cell) needs to be provided to AF via local UPF/NEF? +- how the above information is obtained? + +NOTE 1: XR/media and AI/ML services specific QoS information exposure are to be studied in corresponding study items with considering the same exposure framework as defined by this study. + +NOTE 2: This key issue will look at the use cases and the data to be exposed but not at the actual UPF exposure mechanism or UPF-originated data, if/when already covered by the FS\_ UPEAS. UPF exposure mechanism to be discussed in FS\_ UPEAS is possibly reused. + +NOTE 3: The aim is to, whenever possible, re-use information already defined in existing 3GPP specifications. + +## 5.2.2 Use cases and scenarios + +Observation of the link characteristics is widely used to adjust the transmission behaviour in different scenarios. For example: + +- For some transport layer protocols, e.g. TCP, QUIC, congestion control algorithms can be used to control packets transmission via 5GS based on e.g. observing packet loss and take it as indication of network congestion. For example, TCP congestion control algorithm defined in RFC 5681 [7] uses different ways to adjust congestion window, perform slow start, congestion avoidance, fast retransmit, and fast recovery, which leads to classic "sawtooth" congestion window. +- Media based services can benefit by low and consistent latency. This can be achieved by rate adaptation by the endpoints. + +For Edge computing scenarios, most applications, e.g. autonomous automotive vehicles, real-time mobile gaming, cloud gaming, robotic applications, interactive video, are sensitive to the change of network latency and throughput. When network congestion happens, if the application can be notified in a fast and efficient way (e.g. within a RTT of user packet transmission), these services can react to the change of network congestion status more agilely. + +NOTE: The solution in the following clause 6 will use the use case(s) in this clause as guidance to judge the feasibility and suitability. + +## 5.3 KI#3: Policies for finer granular sets of UEs + +### 5.3.1 Description + +This key issue investigates the potential need and solutions for supporting offload policies for more granular sets of UE(s). + +This key issue will study the following aspects: + +- how to identify set of UEs at a finer granularity that are associated with a dedicated offload policy, and how to express the set of UE in the offload policy; +- impacts to 5GS needed to support providing traffic offload policy for such a set of UEs. + +### 5.3.2 Scenarios + +Considering limited or expensive EC resources, the application service provider or the operator may consider to provide EC services for certain users only under certain conditions, e.g. within a specific geographical area, or at specific time, + +etc. The AFs can provide the request to support some offload policies only for certain set of UE(s) following a set of specific criteria. + +There are cases that traffic offload policy aims at a finer sets of UE(s), for instance, UEs satisfying a combination of criteria: + +- Case a: UEs within a specific geographical area and have been associated with specific service provided by operator or application service provider; +- Case b: UEs that have been associated with a combination of services provided by operator or application service provider; +- Case c: UEs within a specific geographical area and have been associated with a combination of services provided by operator or application service provider; +- Case d: at specific time, UEs that have been associated with specific service or a combination of services provided by operator or application service provider; +- Case e: UEs belongs to both group-A and group-B, or UEs belongs to group-A and associated with specific service. It is possible that these users belong to pre-defined groups or do not belong to any pre-defined groups. + +### 5.3.3 Assumptions + +Operator-internal configurations shall not be exposed to 3rd party AFs. + +The application can be deployed in both central location(s) and edge cloud(s). + +The application service provider is expected to be able to interact with the operator regarding setting the offload policies. + +Solutions for this KI will identify their support for the following: + +- AF under operator control; +- AF under 3rd party control. + +## 5.4 KI#4: Influencing UPF and EAS (re)location for collections of UEs + +### 5.4.1 Description + +Investigate the potential need and solutions to influence of PSA-UPF and EAS (re)location for collection of UEs, e.g. in scenarios when UE(s) should use the same EAS and are not members of a pre-defined group. + +In particular, the key issue will study the following aspects: + +- whether and how to define a collection of UEs forming a dynamic ad-hoc group that should use the same EAS and/or same local part of DN and/or same DNAI and how the collection is identified; +- whether and how to influence UPF and EAS (re)location for a collection of UEs that should use the same EAS and/or same local part of DN and/or same DNAI; +- how to decide on a common local part of DN for the collection of UEs; +- for a given collection of UEs defined in the above, whether and how to determine if any UE in this collection have no access to EAS or local part of DN, and whether and how to define any specific treatments for such UE if any; +- how to handle coordination of the UPF(s) and EAS (re)location for collections of UEs; +- whether and how existing mechanisms suffice; + +- whether and what improvements are required for EAS discovery and re-discovery for UEs belonging to a collection of UEs. + +## 5.4.2 Scenarios + +There are use cases that UEs belonging to a non-predefined dynamic group should be treated the same way, and members of the dynamic group is likely to change dynamically, e.g. UE could join/leave the group randomly. For example: + +- Multi-user low latency Gaming: In such use cases, the Application client running on the UE are served by a particular application server which is the corresponding game hosting server i.e. Edge Application Server (EAS). This EAS provides gaming services and maintains individual UEs gaming profile, user level registration details, etc. These members could change dynamically over period of time. Also, due to maintenance purposes or due to overload situation EAS would require to be relocated to another one, thus moving all registered users to the new EAS. +- Platooning: In case of platooning use case, all the member UEs involved have similar attributes and requirements, for example, all UEs in a particular platoon have similar mobility characteristics i.e. moving in the same direction and with similar speed, located in proximity to each other, and so on. +- XR application which consists of a group of application components on multiple UEs: In the use case, the XR application consists of multiple application components running on different UEs for different purposes e.g. recognizing, modelling, rendering of a group of objects. The application components processing for the group of UEs should be run on a single EAS instance. + +## 5.4.3 Assumptions + +For the dynamic group management, coordination between FS\_EDGE\_Ph2 and FS\_GMEC might be needed. + +# 5.5 KI#5: GSMA OPG impacts and improvements for EHE operated by separate party + +## 5.5.1 Description + +As indicated in the LS out to GSMA Operator Platform Group (OPG) in SP-210583 [6], the ongoing GSMA OPG work may have impacts on 5G architecture. + +GSMA OPG introduced the concept of Federation of Operator Platforms introduced in GSMA OPG.02 [5], to allow Application Providers to reach a wider geographical area and user base. The following aspects shall be studied: + +- investigate potential impacts related to the GSMA Operator Platform Group work, and potential improvements related with 5GC network and EHE being operated by different organizations; +- investigate potential impacts related to the GSMA Operator Platform Group work on EAS discovery; +- how the 5GS facilitates edge relocation between an EAS deployed by a source EHE provider to another EHE deployed by a target EHE provider, even in scenarios when EHEs are operated by different service providers. + +## 5.5.2 Scenarios + +Clause 3.3.5 of the GSMA OPG.02 [5] requirement document introduces the Edge Node Sharing scenario in which EAS A (hosted by one partner, e.g. 3rd party or another Operator) is to be accessed by the other partners, e.g. Operator B's network (see figure 2 in clause 3.3.5 of GSMA OPG.02 [5]). The same modelling and solutions of a 3rd party provider hosting the EHE are considered. Under such circumstances, mechanisms should be available to allow a PLMN to use EHE resources shared by another MNO appropriately, i.e. allow a UE in PLMN B to access efficiently the EAS in PLMN A located in close proximity and to route the UE traffic to the identified EAS. + +The following terms defined in the GSMA OPG.02 [5] requirement document are used: + +| | | +|-------|--------------------------| +| E/WBI | East/Westbound Interface | +|-------|--------------------------| + +| | | +|--------|------------------------------------------| +| OP | Operator Platform | +| SBI-CR | Southbound Interface – Cloud Resources | +| SBI-NR | Southbound Interface – Network Resources | +| UNI | User to Network Interface | + +## 5.5.3 Assumptions + +Edge Node Sharing is a deployment option based on agreements between two or more parties (the operator providing the connectivity and one or more 3rd parties or other operators providing the Edge Cloud Compute Resources). + +To support the Edge Node Sharing scenario in which EAS's are hosted by one or more partners (3rd party or another Operator), the East/Westbound interface (defined by GSMA OPG) can be used to provide the serving operator with application instance access information. This approach allows the serving Operator to performing service discovery and delivery as when the application was delivered from an EHE in the serving Operator's own network. + +The Edge Node sharing allows the Home and Visited PLMN to incorporate EASs that are hosted on Edge Node sharing partners Edge compute resources without impact on the roaming solutions. + +# 5.6 KI#6: Avoiding UE to switch away from EC PDU Session + +## 5.6.1 Description + +This key issue investigates the potential need and solutions to avoid the UE to switch the EC traffic away from the EC PDU Session and 5GS altogether, due to conflicting connectivity preferences in the device (e.g. via means outside of 3GPP connectivity, e.g. non-integrated Wi-Fi). + +In particular, this key issue will address: + +- how to determine what traffic is using the 5G System to access edge computing resources, and specifically in what granularity the traffic can be identified (e.g. Flow and/or PDU Session); +- what actions might be taken when some application traffic is currently using the 5G System to access edge computing resources and connectivity outside of 5GS becomes available. + +## 5.6.2 Scenarios + +5GS may provide a number of enablers for Edge Computing, those for 3GPP Rel-17 being specified in TS 23.548 [3]. For example: + +- EAS (Re-)discovery for Distributed Anchor and Multiple PDU Sessions Connectivity Model; +- EAS (Re-)discovery over Session Breakout Connectivity Model; +- Edge Relocation Involving AF Change. + +In some scenarios, these Edge Computing enablers cannot be used if the UE switches to an access for all UP traffic that is not integrated with 5GS or does not provide the expected characteristics. Problematic cases include: + +- non-integrated access, where re-connecting to the 5GS is not possible, e.g. because lack of UE support or an N3IWF could not be discovered or connected to and these Edge Computing enablers can only be reached via the 5GS; +- re-connecting to the 5GS is possible but results in long UP paths because of e.g. a centralized N3IWF; +- session breakout scenarios where an UL-CL and L-PSA is used to obtain EC connectivity and switching to an access that is not integrated with 5GS would therefore break the EC connectivity. + +A UE may use a PDU Session to access Edge Computing Services. When non-integrated connectivity becomes available for the UE, the UE's connectivity preferences may dictate that the UE use the non-integrated connectivity for traffic that is currently accessing Edge Computing Services via the 5G System. + +### 5.6.3 Assumptions + +This key issue should consider all of the connectivity models that are described in clause 4.3 of TS 23.548 [3] (i.e. Distributed Anchor Point, Session Breakout, and Multiple PDU Session). + +## 5.7 KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI + +### 5.7.1 Description + +For edge computing scenarios, it is important for AF to obtain target DNAI in order to determine the target new EAS for edge relocation. Up to Rel-17, it has been assumed that the AF has been provisioned with the proper DNAI information if it is required to use it during its interactions with the 5GC. This key issue will investigate the potential solutions for the AF to be able to obtain/determine the DNAI that is associated to a certain selected EAS, for subsequent use with already defined services provided to the AF. + +The following aspects shall be studied: + +- what information the AF should provide to 5GC (e.g. IP address or range thereof (i.e. IPv4 subnetwork and IPv6 prefixes), FQDN) and how it should provide it to help determine proper DNAI if the AF does not have knowledge of the DNAI information; +- whether and how the 5GC can provide a DNAI to AF to help the subsequent AF influence/request. + +### 5.7.2 Scenarios + +What we have met in the real network is that the AF does not understand the DNAI information. All the DNAIs are created by operators and transmitted to AF based on offline configuration. The DNAI information has been supported since Rel-15 by TS 23.501 [2] AF influence procedure. + +However, there still existing the scenario that the AF has not been provided beforehand with DNAI information and needs to know the DNAI(s) associated with the EAS(s) in the EHE under its responsibility. + +### 5.7.3 Assumptions + +The existing service operations used by the AF and making use of DNAI shall not be impacted by this new functionality. + +--- + +## 6 Solutions + +### 6.0 Solution-Key issue matrix + +The solutions in clause 6 can apply to one or more key issues described in clause 5 of this report. Table 6.0-1 describes the relationship between solutions and key issues. + +Table 6.0-1: Solution-Key issue matrix + +| Solution | | Key issues | | | | | | | +|---------------------------------------------------------------------------------|------|------------|------|------|------|------|------|--| +| Title | KI#1 | KI#2 | KI#3 | KI#4 | KI#5 | KI#6 | KI#7 | | +| 01: EAS discovery in Home Routed roaming scenario | X | | | | | | | | +| 02: Session Breakout in Visited PLMN | X | | | | | | | | +| 03: EAS (re)discovery procedure in roaming scenario | X | | | | | | | | +| 04: Support EAS (re-)discovery in VPLMN via HR PDU Session | X | | | | | | | | +| 05: Accessing V-EHE via HR PDU Session | X | | | | | | | | +| 06: URSP solution to support roamers access to EHE in a VPLMN | X | | | | | | | | +| 07: Using URSP Rules to Establish an LBO PDU Session | X | | | | | | | | +| 08: V-ECS Discovery during Steering of Roaming | X | | | | | | | | +| 09: PDU Session configuration from EASDF | X | | | | | | | | +| 10: LBO PDU Session establishment using PLMN criteria in RSD | X | | | | | | | | +| 11: Exposure of Network Congestion | | X | | | | | | | +| 12: Efficient exposure of RAN information | | X | | | | | | | +| 13: Fast and efficient network exposure improvements | | X | | | | | | | +| 14: Group Management | | | | X | | | | | +| 15: Selection of common DNAI | | | | X | | | | | +| 16: Selecting the same EAS/DNAI for collection of UEs | | | | X | | | | | +| 17: Application layer EAS selection for collections of UEs | | | | X | | | | | +| 18: Discovery of the same EAS for collections of UEs | | | | X | | | | | +| 19: Influencing UPF and EAS (re)location for collections of UEs | | | | X | | | | | +| 20: Global EASDF | | | | | X | | | | +| 21: EAS Deployment information differentiated by PLMN ID | | | | | X | | | | +| 22: EAS discovery Edge Node Sharing | | | | | X | | | | +| 23: Improvements for EHE operated by separate party | | | | | X | | | | +| 24: Reuse Option D after UL-CL insertion | X | | | | | | | | +| 25: EAS discovery in VPLMN via V-EASDF for a HR PDU Session | X | | | | | | | | +| 26: SM Policy for HR Session Breakout in VPLMN | X | | | | | | | | +| 27: EAS discovery with dynamic setup of a LBO PDU Session | X | | | | | | | | +| 28: Support edge computing in Roaming | X | | | | | | | | +| 29: Use of Internal Group ID and constraints in EDI | | | X | | | | | | +| 30: Policies referring to "Allowed services" and/or "Subscriber categories" | | | X | | | | | | +| 31: Providing traffic offload policy for a set of UEs with service information | | | X | | | | | | +| 32: Offload policy for finer granular set of UEs | | | X | | | | | | +| 33: AF requests offload policy for sets of UEs | | | X | | | | | | +| 34: Selecting the same EAS/DNAI for collection of UEs | | | | X | | | | | +| 35: Providing dedicated (re)location information as traffic routing information | | | | X | | | | | +| 36: Providing dedicated (re)location information as EAS Deployment information | | | | X | | | | | +| 37: (Re)location of same EAS and coordination across UEs | | | | X | | | | | +| 38: EAS Discovery for EHE shared with other PLMN | | | | | X | | | | +| 39: Support EAS relocation of inter-PLMN | X | | | | X | | | | +| 40: EAS discovery for shared EHE | | | | | X | | | | +| 41: Controlling non-3GPP access of EC traffic via URSP and ATSSS | | | | | | X | | | +| 42: Network-guided EC traffic switching | | | | | | X | | | +| 43: Network-based solution for keeping EC traffic on 3GPP Access | | | | | | X | | | +| 44: EAS traffic switching avoidance | | | | | | X | | | +| 45: Application selected PDU Session | X | | | | | X | | | +| 46: Avoid UE switching on-going EC traffic away from 3GPP access | | | | | | X | | | +| 47: Avoiding Switch Away Based on an SMF Indication | | | | | | X | | | +| 48: Avoiding Switch Away Based on an Indication in the URSP | | | | | | X | | | + +| Solution | | Key issues | | | | | | | +|-----------------------------------------------------------------------------|------|------------|------|------|------|------|------|--| +| Title | KI#1 | KI#2 | KI#3 | KI#4 | KI#5 | KI#6 | KI#7 | | +| 49: URSP based solution to avoid UE to switch away from Edge PDU Session | | | | | | X | | | +| 50: Obtain and maintain mapping table between IP address/IP range with DNAI | | | | | | | X | | +| 51: EDI holding the IP address to DNAI mapping | | | | | | | X | | +| 52: AF obtaining target DNAI provided by NEF | | | | | | | X | | +| 53: EDC-based EAS discovery for HR PDU Session with Session Breakout | X | | | | | | | | +| 54: PCF controlling common DNAI | | | | X | | | | | +| 55: Access the shared EAS via N9 tunnel | | | | | X | | | | + +## 6.1 Solution 01 (KI#1): EAS discovery in Home Routed roaming scenario + +### 6.1.1 Description + +This solution is for Key Issue #1, which addresses 5GS improvements to support the UE access to an EHE in a VPLMN using a PDU Session with a PSA in the HPLMN including aspects related to: + +- How to authorize the PDU Session to support local traffic routing to access an EHE in the VPLMN; +- How to support Rel-17 edge computing related procedures, such as EAS (re-)discovery, as specified in clause 6 of TS 23.548 [3]. + +The current standards only depict 5GS architecture for non-roaming and LBO roaming scenario supporting with UL-CL/BP. For Home Routed roaming scenario, the data flow of the UE needs to pass through the UPF of the VPLMN to the UPF of the HPLMN, the routing is controlled by SMF of the HPLMN, therefore the local traffic routing in the VPLMN cannot be achieved. + +This solution proposes several ways to support UE access to VPLMN EHE in HR roaming scenarios according to different scenarios. + +When H-AF has the knowledge of V-AF request, it creates a new request with carrying V-AF application requirement, and the H-AF configures it to the H-SMF according to the AF requests to influence traffic routing procedure defined in clause 4.3.6.2 of TS 23.502 [9]. H-SMF will send the PCC rule related with the AF request about the HR PDU Session to V-SMF, H-SMF also sends the VPLMN ECS address and local traffic routing indication to V-SMF, and V-SMF will perform the EAS discovery and local traffic routing in VPLMN as described in clause 6.2.3.2.3 of TS 23.548 [3]. + +When HPLMN does not have the knowledge of EAS deployment information in VPLMN, after the H-SMF authorizes the V-SMF to perform local traffic routing, V-SMF retrieves the EAS deployment information of the VPLMN from the V-NEF and performs EAS discovery according to the EAS discovery procedure described in TS 23.548 [3]. + +In addition, the V-AF can also configure the V-SMF according to the AF influence on traffic routing procedure. In this case, during the HR PDU Session establishment, the V-SMF needs to select a PCF in the VPLMN to establish the SM Policy Association. V-PCF may send the VPLMN ECS address obtained from V-AF to V-SMF. + +The charging at VPLMN can be applied by V-UPF reporting usage information to V-SMF to V-CHF, and the usage information also needs to be reported by V-UPF to H-SMF via V-SMF, and H-SMF reports the usage to H-CHF for charging at HPLMN. + +## 6.1.2 Procedures + +### 6.1.2.1 EAS discovery when HPLMN has the knowledge of EAS deployment information in VPLMN + +![Sequence diagram illustrating HPLMN triggered EAS discovery in HR roaming scenario. The diagram shows interactions between UE, V-UPF, V-SMF, H-SMF, H-PCF, H-UDR, H-NEF, and H-AF. Step 1: H-AF sends an AF request to influence traffic routing to H-PCF. Step 2: Home Routed PDU Session establishment occurs between UE and H-SMF. Step 3: V-SMF performs steps 1-6 described in TS 23.548 clause 6.2.3.2.3, involving V-UPF ULCL, V-UPF PSA, and DNS Server in VPLMN.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-UPF + participant V-SMF + participant H-SMF + participant H-PCF + participant H-UDR + participant H-NEF + participant H-AF + + Note right of H-AF: 1. AF request to influence traffic routing as described in TS 23.502 clause 4.3.6.2 step 1-4 + H-AF->>H-PCF: AF request + Note right of H-PCF: 2. Home Routed PDU Session establishment + UE->>H-SMF: PDU Session Request + H-SMF->>V-SMF: Nsmf_PDUSession_Create response + Note right of V-SMF: 3. Step 1-6 described in TS 23.548 clause 6.2.3.2.3 + V-SMF->>V-UPF: ULCL/PSA configuration + V-SMF->>DNS: DNS Server configuration + V-SMF->>UE: DNS Server IP address + +``` + +Sequence diagram illustrating HPLMN triggered EAS discovery in HR roaming scenario. The diagram shows interactions between UE, V-UPF, V-SMF, H-SMF, H-PCF, H-UDR, H-NEF, and H-AF. Step 1: H-AF sends an AF request to influence traffic routing to H-PCF. Step 2: Home Routed PDU Session establishment occurs between UE and H-SMF. Step 3: V-SMF performs steps 1-6 described in TS 23.548 clause 6.2.3.2.3, involving V-UPF ULCL, V-UPF PSA, and DNS Server in VPLMN. + +**Figure 6.1.2.1-1: HPLMN triggered EAS discovery in HR roaming scenario** + +1. H-AF creates a new request with carrying V-AF application requirement and invokes a Nnef\_TrafficInfluence\_Create service operation and influences the traffic as described in steps 1-4 in clause 4.3.6.2 of TS 23.502 [9]. It is assumed that EAS deployment information of VPLMN is not contained in AF request. + +NOTE 1: How V-AF sends application related information to H-AF is in SA6 scope. As an alternative, the V-AF may, depending on operator agreement, act as a non-trusted AF of the HPLMN (using NEF). + +2. 5GS establishes a Home Routed PDU Session. During PDU Session establishment, H-SMF retrieves the PCC rules for which PDU Session may be impacted by the H-AF request for VPLMN from H-PCF using Rel-17 Npcf mechanisms, and sends Nsmf\_PDUSession\_Create response to V-SMF, which also includes an indication to authorize V-SMF to perform local traffic routing in VPLMN and VPLMN ECS address. The indication and VPLMN ECS address are obtained by H-SMF from H-UDM. + +NOTE 2: The PCC rules are sent from H-SMF to V-SMF over N16. + +3. Steps 1-6 in clause 6.2.3.2.3 of TS 23.548 [3] are performed. In step 1 of clause 6.2.3.2.3, UL-CL will be inserted by V-SMF. + +NOTE 3: The local DNS server IP address will be configured to UE by V-SMF as described in Option C in clause 6.2.3.2.3 of TS 23.548 [3] based on the information provided in the AF request in step 1. + +### 6.1.2.2 EAS discovery when HPLMN does not have the knowledge of EAS deployment information in VPLMN + +![Sequence diagram illustrating VPLMN triggered EAS discovery in HR roaming scenario. The diagram shows interactions between UE, V-UPF, V-SMF, V-PCF, V-UDR, V-NEF, V-AF, H-UPF, and H-SMF.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-UPF + participant V-SMF + participant V-PCF + participant V-UDR + participant V-NEF + participant V-AF + participant H-UPF + participant H-SMF + + Note right of V-NEF: 1. EAS Deployment Information Provision from AF via NEF as described in TS 23.548 clause 6.2.3.4.2 + V-NEF->>V-SMF: 2. Nnef_EASDeployment_Notify request + V-SMF-->>V-NEF: 3. Nnef_EASDeployment_Notify response + Note right of V-AF: 4. AF request to influence traffic routing as described in TS 23.502 clause 4.3.6.2 step 1-4 + V-AF->>V-NEF: + Note over UE, H-SMF: 5. Home Routed PDU Session establishment + Note left of V-UPF: [V-EASDF, V-UPF ULCL, V-UPF PSA, DNS Server in VPLMN] + UE->>V-UPF: 6. DNS query + V-UPF->>V-SMF: 7. V-UPF forwards the request to V-SMF + Note right of V-SMF: 8. EASDF selection + V-SMF->>H-SMF: 9. V-SMF sends Nsmf_PDUSession_Update request + H-SMF-->>V-SMF: 10. Nsmf_PDUSession_Update response + V-SMF->>V-PCF: 11. Npcf_SMPolicyControl_Create request + V-PCF-->>V-SMF: 12. Npcf_SMPolicyControl_Create response + V-SMF->>V-UPF: 13. Neasdf_DNSContext_Create Request + V-UPF-->>V-SMF: 14. Neasdf_DNSContext_Create Response + Note right of V-SMF: 15a. V-SMF indicates UE to resend the DNS Query Message + Note left of UE: 16a. Step 7-19 described in TS 23.548 clause 6.2.3.2.2 + Note right of V-SMF: 15b. V-SMF indicates UE to resend the DNS Query Message + Note left of UE: 16b. Step 1-6 described in TS 23.548 clause 6.2.3.2.3 + +``` + +Sequence diagram illustrating VPLMN triggered EAS discovery in HR roaming scenario. The diagram shows interactions between UE, V-UPF, V-SMF, V-PCF, V-UDR, V-NEF, V-AF, H-UPF, and H-SMF. + +**Figure 6.1.2.2-1: VPLMN triggered EAS discovery in HR roaming scenario** + +1. EAS deployment Information provisioned from AF via NEF as described in clause 6.2.3.4.2 of TS 23.548 [3]. +- 2-3. It is assumed that V-SMF has subscribed to EAS Deployment Information Change Notification from the V-NEF. The V-NEF invokes Nnef\_EASDeployment\_Notify to the SMF to provide the EAS Deployment Information. +4. If V-AF related information changes, V-AF creates a new request and invokes a Nnef\_TrafficInfluence\_Create service operation and influences the traffic as described in steps 1-4 in clause 4.3.6.2 of TS 23.502 [9]. +5. UE establishes Home Routed PDU Session. During the HR PDU Session establishment, UE uses a DNN which supports local traffic routing in VPLMN for Home Routed PDU Sessions. When V-SMF recognises the DNN, it will select a PCF in VPLMN and establish a SM Policy Association with it. The PCC instructions sent by V-PCF to V-SMF and PCC instructions sent by H-PCF to H-SMF will be translated into QoS rules respectively and both stored in V-SMF until being updated by new policy such as when step 10 happens. +6. UE sends DNS Query message to V-UPF. +7. V-UPF will detect the DNS query based on the V-SMF configured data forwarding rule to the V-UPF for the traffic to be offloaded and notify V-SMF. +8. V-SMF requests to do the local traffic routing in VPLMN and V-SMF selects V-EASDF before the authorization, in order to support including V-EASDF/Local DNS address information in PCO generated from HPLMN. +9. V-SMF sends the request of local traffic routing in VPLMN to H-SMF via Nsmf\_PDUSession\_Update request, with including V-EASDF/Local DNS address information, and also sends the capability of supporting EASDF indication to H-SMF. According to the feature and principle of Home Routed PDU Session, H-SMF should have the control of PDU Session, so V-SMF should request local traffic routing from H-SMF first and then request the policy from V-PCF as described in step 10. This requires operators in VPLMN to enhance the control of V-SMF and optimize the protocol with operator in HPLMN. +10. H-SMF sends the indication to authorize V-SMF to perform local traffic routing in VPLMN and the H-DNS for the traffic to be routed to HPLMN via or Nsmf\_PDUSession\_Update response. The indication is obtained by H-SMF from H-UDM. H-SMF also includes V-EASDF/Local DNS address information in PCO via Nsmf\_PDUSession\_Update response. +- 11-12. V-SMF sends Npcf\_SMPolicyControl\_Create request to V-PCF to retrieve the new policy impacted by the AF request. After this step, V-SMF gets two kinds of policies, one is from V-PCF and one is from H-PCF. + +13. The V-SMF invokes Neasdf\_DNSContext\_Create Request to the selected V-EASDF. The DNS messages for the EC service to be offloaded to the VPLMN are configured to be handled as step 15a-16a. For other DNS messages, they are configured to be forwarded to the DNS server related to the HPLMN. +14. The EASDF invokes the service operation Neasdf\_DNSContext\_Create Response. +- 15a. If V-SMF has received the EAS deployment information in steps 2-3, V-SMF sends the PCO generated by H-SMF to UE and indicates UE to resend the DNS Query message to V-EASDF. +- 16a. Steps 7-19 in clause 6.2.3.2.2 of TS 23.548 [3] are performed. +- 15b. If V-SMF did not receive the EAS deployment information in steps 2-3, and V-SMF received the application related information (e.g. DNAI, local DNS server address), V-SMF sends the PCO generated by H-SMF to UE and indicates UE to resend the DNS Query message to local DNS server. +- 16b. Steps 1-6 in clause 6.2.3.2.3 of TS 23.548 [3] are performed. + +After the whole above procedure, if the UE sends out a DNS query which intends for Home PLMN DNS processing, while using the V-EASDF or Local DNS server address as the target IP address (since in step 15a and 15b the UE PCO is updated with V-EASDF or Local DNS server address), the V-UL-CL and V-UPF should identify the FQDN and decide whether the DNS query should be sent to Home PLMN network. If yes, V-UPF should send the DNS query to H-UPF, and H-UPF should change the target IP address in the DNS query into Home PLMN DNS address, based on the N4 rule from H-SMF. + +### 6.1.3 Impacts on services, entities and interfaces + +#### For 6.1.2.1 + +##### H-SMF: + +- obtains the indication to authorize V-SMF to perform local traffic routing in VPLMN and VPLMN ECS address from UDM; +- Sends the indication and VPLMN ECS address to V-SMF + +##### H-UDM: + +- In the UE subscription data, the indication and VPLMN ECS address are configured. + +##### V-SMF: + +- obtains the indication to perform local traffic routing in VPLMN from H-SMF; +- obtains VPLMN ECS address from H-SMF; +- supports to insert UL-CL and local PSA UPF for local traffic routing in VPLMN. + +#### For 6.1.2.2 + +##### V-SMF: + +- When V-SMF recognises the DNN, it will select a PCF in VPLMN and establish a SM Policy Association with the V-PCF; +- V-SMF sends the V-PCF related PCC rules to V-UPF through N4; +- interacts with V-EASDF by reusing the interface between SMF and EASDF defined in TS 23.548 [3]; +- requests local traffic routing from H-SMF; +- sends the V-EASDF address/local DNS address to H-SMF. + +##### V-PCF: + +- involved with the HR PDU Session and provides PCC instructions to V-SMF. + +##### V-UPF: + +- detects the DNS query and notifies the V-SMF. + +H-SMF: + +- sends the indication to authorize V-SMF to perform local traffic routing in VPLMN; +- H-SMF gets this indication from H-UDM. +- creates the PCO including V-EASDF/Local DNS address; +- configures the H-UPF with changing the target IP address of the DNS query into Home PLMN DNS address. + +H-UPF: + +- changes the target IP address of the DNS query into Home PLMN DNS address. + +## 6.2 Solution 02 (KI#1): Session Breakout in Visited PLMN + +### 6.2.1 Description + +This solution corresponds to KI#1 and addresses the scenario 2.2, that is, UE accessing V-EHE via a Home Routed (HR) PDU Session (i.e. with PSA in HPLMN) where HPLMN does not have the knowledge of EAS deployment information in VPLMN as described in clause 5.1.2. + +This solution corresponds to KI#1 and addresses the following aspects for the scenario using a PDU Session with a PSA in the HPLMN: + +- how to authorize the PDU Session to support local traffic routing to access an EHE in the VPLMN; +- how to support Rel-17 edge computing related procedures, such as EAS (re-)discovery, as specified in clause 6 of TS 23.548 [3]. + +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 session breakout for the home routed session. + +- 1) During the establishment of Home Routed PDU Session, Home PLMN allows the roaming UE to access the local part of DN identified by DNN based on its HPLMN subscription. +- 2) V-SMF in V-PLMN executes the session breakout procedure for the UE to access the local part of DN where the EAS in EHE is located in VPLMN. This can be triggered by the EAS discovery procedure using V-EASDF. +- 3) Through a Home Routed Session, the UE can access EAS deployed in EHE in VPLMN while the UE can also access the Home DN in the Home PLMN. + +NOTE: The companion solution #26 in clause 6.26 explains the policy and charging aspect of this solution. + +![Figure 6.2.1-1: Architecture for Home Routing Session Breakout in Visited PLMN. This diagram shows the network architecture split into VPLMN (Visited PLMN) and HPLMN (Home PLMN). In the VPLMN, the UE connects to an AN, which connects to an AMF. The AMF connects to a V-SMF via N2 and N4 interfaces. The V-SMF connects to a UPF (ULCL/BP) via N3 and N4 interfaces. This UPF connects to another UPF (L-PSA) via N6, which is part of the Local part of DN (EAS). The V-SMF also connects to a NEF and a V-EASDF. The AMF connects to an NRF via Nnrf, a V-PCF via Npcf, and an AF via Naf. In the HPLMN, the V-UPF connects to an H-UPF (C-PSA) via N9. The H-UPF connects to a Central DN via N6. The H-UPF connects to an H-SMF via N4. The H-SMF connects to a UDM via Nudm and an H-PCF via Npcf. The H-SMF also connects to the V-SMF via Nsmf.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 6.2.1-1: Architecture for Home Routing Session Breakout in Visited PLMN. This diagram shows the network architecture split into VPLMN (Visited PLMN) and HPLMN (Home PLMN). In the VPLMN, the UE connects to an AN, which connects to an AMF. The AMF connects to a V-SMF via N2 and N4 interfaces. The V-SMF connects to a UPF (ULCL/BP) via N3 and N4 interfaces. This UPF connects to another UPF (L-PSA) via N6, which is part of the Local part of DN (EAS). The V-SMF also connects to a NEF and a V-EASDF. The AMF connects to an NRF via Nnrf, a V-PCF via Npcf, and an AF via Naf. In the HPLMN, the V-UPF connects to an H-UPF (C-PSA) via N9. The H-UPF connects to a Central DN via N6. The H-UPF connects to an H-SMF via N4. The H-SMF connects to a UDM via Nudm and an H-PCF via Npcf. The H-SMF also connects to the V-SMF via Nsmf. + +Figure 6.2.1-1: Architecture for Home Routing Session Breakout in Visited PLMN + +## 6.2.2 Procedure + +![Figure 6.2.2-1: PDU Session Establishment Procedure for HR Session Breakout in VPLMN. This sequence diagram shows the interaction between various network functions: UE, RAN, AMF, L-UPF, V-UPF (w/ ULCL), V-SMF, V-EASDF, Visited DNS Server, H-UPF, H-SMF, UDM, and Home DNS Server. The procedure starts with a Registration Request from the UE to the AMF. The AMF sends a Get SDM Information request to the H-SMF, which responds with SDM information indicating HR-VSBO is allowed. The AMF then sends a Registration Response to the UE. Next, the UE sends a PDU Session Establishment Request to the AMF. The AMF sends a CreateSMContext Request to the V-SMF, which responds with a CreateSMContext Response. The V-SMF then sends an N4 Establishment with V-UPF request to the V-UPF. The V-UPF sends a PDU Session Create Request to the V-EASDF, which responds with a PDU Session Create Response. The V-EASDF then sends a DNSContextCreate to the Visited DNS Server. The Visited DNS Server sends a DNS Query to the Home DNS Server, which responds with a DNS Response. The Visited DNS Server then sends a DNS Notify to the V-EASDF. The V-EASDF sends a DNS Query to the H-UPF, which responds with a DNS Response. The H-UPF then sends an N4 Establishment with H-UPF request to the H-SMF, which responds with an N4 Establishment with H-UPF response. The H-SMF sends a PDU Session Create Request to the H-UPF, which responds with a PDU Session Create Response. The H-UPF then sends an N4 Update with V-UPF request to the V-UPF. The V-UPF sends a Local UPF insertion request to the L-UPF, which responds with a Local UPF insertion response. The L-UPF then sends an N4 Update with V-UPF request to the V-UPF. The V-UPF sends a PDU Session Establishment Accept/Reject to the AMF, which then sends a PDU Session Establishment Accept/Reject to the UE. Finally, the UE sends a DNS Query to the V-EASDF, which responds with a DNS Response.](088921fa3f5a44c8551815122517eefd_img.jpg) + +Figure 6.2.2-1: PDU Session Establishment Procedure for HR Session Breakout in VPLMN. This sequence diagram shows the interaction between various network functions: UE, RAN, AMF, L-UPF, V-UPF (w/ ULCL), V-SMF, V-EASDF, Visited DNS Server, H-UPF, H-SMF, UDM, and Home DNS Server. The procedure starts with a Registration Request from the UE to the AMF. The AMF sends a Get SDM Information request to the H-SMF, which responds with SDM information indicating HR-VSBO is allowed. The AMF then sends a Registration Response to the UE. Next, the UE sends a PDU Session Establishment Request to the AMF. The AMF sends a CreateSMContext Request to the V-SMF, which responds with a CreateSMContext Response. The V-SMF then sends an N4 Establishment with V-UPF request to the V-UPF. The V-UPF sends a PDU Session Create Request to the V-EASDF, which responds with a PDU Session Create Response. The V-EASDF then sends a DNSContextCreate to the Visited DNS Server. The Visited DNS Server sends a DNS Query to the Home DNS Server, which responds with a DNS Response. The Visited DNS Server then sends a DNS Notify to the V-EASDF. The V-EASDF sends a DNS Query to the H-UPF, which responds with a DNS Response. The H-UPF then sends an N4 Establishment with H-UPF request to the H-SMF, which responds with an N4 Establishment with H-UPF response. The H-SMF sends a PDU Session Create Request to the H-UPF, which responds with a PDU Session Create Response. The H-UPF then sends an N4 Update with V-UPF request to the V-UPF. The V-UPF sends a Local UPF insertion request to the L-UPF, which responds with a Local UPF insertion response. The L-UPF then sends an N4 Update with V-UPF request to the V-UPF. The V-UPF sends a PDU Session Establishment Accept/Reject to the AMF, which then sends a PDU Session Establishment Accept/Reject to the UE. Finally, the UE sends a DNS Query to the V-EASDF, which responds with a DNS Response. + +Figure 6.2.2-1: PDU Session Establishment Procedure for HR Session Breakout in VPLMN + +1-4. During the registration procedure, the UDM sends the Home Routed Visited SBO (HR-VSBO) allowed indication to the AMF. + +5-8. During the PDU Session establishment procedure, if the AMF receives the HR-VSBO allowed indication and AMF selects V-SMF supporting UL-CL with V-EASDF interaction, the AMF sends the HR VSBO allowed indication to the V-SMF. + +9. If the V-SMF decides to create HR VSBO session, V-SMF sends the VSBO request and V-EASDF/DNS server address of VPLMN to the H-SMF. The HPLMN allowed local DN configuration is configured with the V-SMF per DNN/S-NSSAI. + +10-11. The H-SMF checks whether the HR-VSBO is allowed based on its local configuration or subscription. + +12. The H-SMF establishes N4 session with H-UPF. + +13. H-SMF checks whether the HR VSBO is allowed for the UE. If allowed, the H-SMF sends the VSBO grant indication with DNS server address set to the V-EASDF in PCO and Home DNS Server address to the V-SMF. The H-SMF may send the HPLMN allowed V-SBO information to the V-SMF. The HPLMN allowed V-SBO information includes the IP address ranges and DNS domain name range within which the V-SMF is allowed to route traffic. + +NOTE 1: If the H-SMF grants the HR-VSBO request, the V-SMF is allowed to offload for accessing the EHE in VPLMN without further control from HPLMN. + +14-15. The V-SMF may perform the Local UPF insertion (or UL-CL insertion) procedure. The V-SMF determines the UL-CL filters based on the V-SBO information provided by the H-SMF in step 13. Steps 14 and 15 show how local UPF insertion can be performed in the middle of the PDU Session Establishment. + +16. After the V-SMF performs Local UPF insertion for the local part of DN, the V-SMF performs the DNSContext creation procedure to send the DNS Message Handling Rules and Home DNS Server Address to the V-EASDF. + +NOTE 2: With configured DNS Message Handling Rules configured to V-EASDF, all the DNS Queries using this PDU Session go to the V-EASDF, and DNS resolution for the local routed traffic is handled based on the Rel-17 mechanism for EAS discovery using EASDF. DNS Queries that do not match the rule configured by V-SMF go to the Home DNS Server. + +NOTE 3: Step 12 can be performed when the Local UPF insertion procedure after the PDU Session Establishment. + +NOTE 4: V-SMF can use the EAS Deployment Information provisioned from the AF using the existing procedures described in the clauses 6.2.3.4.2, 6.2.3.4.3 of TS 23.548 [3] to determine DNS Message Handling Rules. V-SMF also uses the V-SBO information provided by H-SMF for DNS Message Handling Rules. + +17-18. The AMF forwards the PDU Session Establishment Accept/Reject to the UE. + +19-21. The EAS (re)-discovery over Session Breakout Connectivity Model as specified in clause 6.2.3 of TS 23.548 [3] can be performed among the UE, V-SMF and V-EASDF based on the UE DNS Query so the UE can access EHE in VPLMN. With the same PDU Session, the UE can still access DN in HPLMN at the same time. Receiving the DNS Query from the UE, the V-EASDF checks whether FQDN can be locally served. If FQDN is for visited network, the V-EASDF exchanges DNS Query and Response with Visited DNS server. Otherwise, the V-EASDF exchanges DNS Query and DNS Response with Home DNS server. + +## 6.2.3 Impacts on services, entities and interfaces + +AMF: + +- The AMF is required to select the V-SMF supporting Visited Session Breakout for Home Routed Session and forward the Home Routed Session Breakout indication to the V-SMF. + +V-SMF: + +- The V-SMF is required to request the Visited Session Breakout with the V-EASDF/DNS server address of VPLMN to the H-SMF. +- The V-SMF is required to interact with V-EASDF by reusing the interface between SMF and EASDF defined in TS 23.548 [3], including creating DNS message handling Rules using the received DNS server address using the DNS server address of HPLMN provided by the H-SMF. + +H-SMF: + +- The H-SMF is required to authorize the V-SMF request for Visited Session Breakout. +- The H-SMF is required to send the V-SMF provided V-EASDF/DNS server address to the UE via V-SMF. +- The H-SMF is required to provide the DNS Server address of HPLMN to the V-SMF. +- The H-SMF is required to provide HPLMN allowed Visited Session Breakout information including the range of IP addresses and FQDN during the establishment of the Home Routed Session to the V-SMF. + +UDM: + +- The subscription information of UDM is required to support the indication for Home Routed Session Breakout. + +V-EASDF: + +- The V-EASDF is required to support the DNS message rule including the default DNS server address indicating all DNS Queries that do not match other rules should be forwarded. + +NOTE: It is assumed that the functionalities of SMF and EASDF in Rel-17 to support edge computing in home network for non-roaming scenario are also required to be supported by V-SMF and V-SMF in VPLMN for roaming scenario. + +## 6.3 Solution 03 (KI#1): EAS (re)discovery procedure in roaming scenario + +### 6.3.1 Description + +KI#1 proposes the scenario: Accessing EHE in a VPLMN when roaming. This solution addresses one of these specific scenarios, i.e. UE accessing V-EHE for a PDU Session with a PSA in HPLMN and assumes that HPLMN does not have the knowledge of EAS deployment information in VPLMN. + +This solution proposes EAS (re)discovery procedure in V-EHE by transmitting a newly defined EC enabling indicator between V-SMF and H-SMF and using the V-EASDF. The UL-CL functionality is used to combine the features of HR and LBO roaming and steer local traffic to the local V-PSA. To minimize the impact of UE, UE is not aware of DNS server changing in HR roaming scenario. + +NOTE 1: According to the roaming agreement between HPLMN and VPLMN, DNS security issue (i.e. using EASDF IP replacement mechanism) can be resolved based on mutual trust between operators. + +NOTE 2: This EC enabling indicator means that VPLMN can apply the traffic offload related to EC service (e.g. UL-CL insertion for EC traffic) without any further HPLMN control. + +### 6.3.2 Procedures + +#### 6.3.2.1 EAS discovery procedure in roaming scenario + +When a UE that has established an HR PDU Session expects to use edge computing service, the UE may send a DNS query to the DNS server, the corresponding EAS discovery procedure is shown in figure 6.3.2.1-1: + +![Sequence diagram of EAS discovery procedure accessing V-EHE in roaming scenario. Lifelines: UE, V-SMF, V-UPF, V-ULCL/V-PSA, V-EASDF, V-DNS server, H-PSA, H-DNS server, H-SMF. The sequence starts with 1. HR PDU session establishment procedure. UE sends 2. DNS query to V-UPF. V-UPF sends 3a. DNS query transmission to H-PSA and 3b. DNS query transmission to V-EASDF. V-EASDF sends 4. Neasdf_DNSContext_Notify request to V-SMF. V-SMF sends 5. Neasdf_DNSContext_Notify response to V-EASDF. V-EASDF sends 6. Neasdf_DNSContext_Update request to V-SMF. V-SMF sends 7. Neasdf_DNSContext_Update response to V-EASDF. V-EASDF sends 8. DNS resolution to V-DNS server. V-EASDF sends 9. Neasdf_DNSContext_Notify request to V-SMF. V-SMF sends 10. Neasdf_DNSContext_Notify response to V-EASDF. A block 11. V-ULCL/V-PSA selection and insertion occurs. V-SMF sends 12. Neasdf_DNSContext_Update request to V-EASDF. V-EASDF sends 13. Neasdf_DNSContext_Update response to V-SMF. A block 14. DNS response handling and transmission occurs. A block 15. EC traffic charging occurs.](dd5771673aececa53d42ece89218299d_img.jpg) + +Sequence diagram of EAS discovery procedure accessing V-EHE in roaming scenario. Lifelines: UE, V-SMF, V-UPF, V-ULCL/V-PSA, V-EASDF, V-DNS server, H-PSA, H-DNS server, H-SMF. The sequence starts with 1. HR PDU session establishment procedure. UE sends 2. DNS query to V-UPF. V-UPF sends 3a. DNS query transmission to H-PSA and 3b. DNS query transmission to V-EASDF. V-EASDF sends 4. Neasdf\_DNSContext\_Notify request to V-SMF. V-SMF sends 5. Neasdf\_DNSContext\_Notify response to V-EASDF. V-EASDF sends 6. Neasdf\_DNSContext\_Update request to V-SMF. V-SMF sends 7. Neasdf\_DNSContext\_Update response to V-EASDF. V-EASDF sends 8. DNS resolution to V-DNS server. V-EASDF sends 9. Neasdf\_DNSContext\_Notify request to V-SMF. V-SMF sends 10. Neasdf\_DNSContext\_Notify response to V-EASDF. A block 11. V-ULCL/V-PSA selection and insertion occurs. V-SMF sends 12. Neasdf\_DNSContext\_Update request to V-EASDF. V-EASDF sends 13. Neasdf\_DNSContext\_Update response to V-SMF. A block 14. DNS response handling and transmission occurs. A block 15. EC traffic charging occurs. + +**Figure 6.3.2.1-1: EAS discovery procedure accessing V-EHE in roaming scenario** + +1. UE requests PDU Session establishment for HR roaming as described in clause 4.3.2.2.2 of TS 23.502 [9]. During the PDU Session Establishment procedure, the H-SMF may consider the UE subscription information to select a H-DNS server for the PDU Session. H-SMF sends H-DNS server IP address included in PCO to UE via V-SMF. + +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 V-SMF does not store the EC enabling indicator per PDU Session level, V-SMF sends an EC enabling indicator request to H-SMF. + +H-SMF respond with a positive EC enabling indicator to V-SMF to indicate that the HPLMN authorizes VPLMN to manage the EC service according to the roaming agreement between these two operators and UE is unaware of potential DNS server changing. H-SMF also sends the IP address of H-DNS server to V-SMF. + +According to the roaming agreement, a FQDN list for EC service in VPLMN is preconfigured on the V-SMF. And V-SMF selects V-EASDF based on the local configuration. V-SMF drives related DNS message handling rule based on EAS deployment information provided by V-PLMN AF and/or local configuration and sends this DNS message handling rule to V-EASDF via Neasdf\_DNSContext\_Create request. + +**NOTE 1:** V-EASDF selection is triggered in HR PDU Session establishment procedure based on the roaming agreement and the positive EC enabling indicator. + +V-SMF uses the FQDN list to derive a traffic routing rule. This traffic routing rule is provided to V-UPF (with UL-CL functionality), e.g. V-UPF routes DNS Queries for an FQDN (range) query to V-EASDF, and routes other traffic to H-PSA. + +V-SMF configures V-UPF with EASDF IP replacement information (i.e. H-DNS server IP address and port number, V-EASDF IP address and port number). In uplink direction, V-UPF replaces the destination address of + +the DNS query with corresponding FQDN from H-DNS server to V-EASDF; in downlink direction, V-UPF replaces the source address of the DNS response with corresponding FQDN from V-EASDF to H-DNS server so that the UE is not aware of the change of DNS server. + +NOTE 2: This configuration refers to the option D of session breakout connectivity model in TS 23.548 [3] and assumes that V-UPF (with UL-CL functionality) steering is based on L4 information (i.e. DNS port number) and that V-UPF (with UL-CL functionality) has visibility of the DNS traffic (i.e. FQDN in the DNS Query message). + +2. UE sends DNS query to H-DNS server. +- 3a. If the DNS query does not match the FQDN list, V-UPF delivers the DNS query to H-PSA via N9 tunnel and H-PSA delivers the DNS query to H-DNS server. +- 3b. If the DNS query matches the FQDN list, V-UPF delivers the DNS query to V-EASDF using EASDF IP replacement. The following EAS discovery procedure is based on step 3b. +4. If the DNS Query message matches a DNS message detection template of DNS message handling rule for reporting, the V-EASDF sends the DNS message report to V-SMF by invoking Neasdf\_DNSContext\_Notify Request. +5. V-SMF responds with Neasdf\_DNSContext\_Notify Response. +6. V-SMF updates DNS message handling rule if needed. V-SMF sends this DNS message handling rule to V-EASDF via Neasdf\_DNSContext\_Update request. +7. V-EASDF responds with Neasdf\_DNSContext\_Update response. +8. V-EASDF handles the DNS query according to the DNS message handling rule and sends the DNS query to the DNS server in VPLMN, the V-DNS server returns the DNS response including EAS IP address and FQDN to V-EASDF. +9. V-EASDF sends the DNS response to the V-SMF by invoking Neasdf\_DNSContext\_Notify request including EAS information if the EAS IP address or the FQDN in the DNS response matches the DNS message detection template provided by the V-SMF as described in clause 6.2.3.2.2 of TS 23.548 [3], and V-EASDF buffers this DNS response. +10. V-SMF responds with Neasdf\_DNSContext\_Notify Response. +11. Based on EAS information received from the V-EASDF in Neasdf\_DNSContext\_Notify and other UPF selection criteria, V-SMF may determine the DNAI and determine the associated N6 traffic routing information for the DNAI based on local configuration. V-SMF may perform V-UL-CL and V-PSA selection and insertion as described in TS 23.502 [9]. + +V-SMF configures the V-UL-CL with CN tunnel info provided by V-UPF and V-PSA and with AN tunnel info provided by serving AN. The traffic routing rules are provided to V-UL-CL based on EAS information, e.g. V-UL-CL routes the traffic to V-PSA if the IP packet has a destination address of V-EAS and routes other traffic to V-UPF. + +V-SMF configures the Usage Report Rule on V-PSA for traffic charging. V-PSA collects and reports the charging information between UE and V-EAS based on the corresponding URR. + +12. V-SMF invokes Neasdf\_DNSContext\_Update Request (DNS message handling rule). The DNS message handling rule with the Control Action "Send the buffered DNS response(s) message to UE" indicates the V-EASDF to send the DNS response buffered in step 9 to UE via V-UPF. +13. V-EASDF responds with Neasdf\_DNSContext\_Update response. +14. If it is indicated to send the buffered DNS response to UE in step 12, the V-EASDF sends the DNS response to the V-UPF. V-UPF replaces the source address from V-EASDF to H-DNS server in the DNS response based on the V-SMF instructions and sends this DNS response to the UE via V-UL-CL. +15. For traffic charging between UE and V-EAS, V-PSA collects and reports the charging information based on the corresponding URR. + +### 6.3.2.2 EAS rediscovery procedure in roaming scenario + +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 as described in clause 6.2.3.3 of TS 23.548 [3]. The corresponding EAS rediscovery procedure is shown in figure 6.3.2.2-1: + +![Sequence diagram of EAS rediscovery procedure in roaming scenario. The diagram shows interactions between UE, V-SMF, V-ULCL/V-PSA, V-EASDF, V-UPF, New V-EASDF, and H-SMF. The steps are: 0. EAS discovery procedure (as described in clause 6.3.2.1); 1. Serving network triggered EAS rediscovery; 2. V-SMF sends EAS rediscovery indication and UE refreshes DNS record; 3. EAS rediscovery procedure in VPLMN.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant V-ULCL/V-PSA + participant V-EASDF + participant V-UPF + participant New V-EASDF + participant H-SMF + + Note over all participants: 0. EAS discovery procedure(as described in clause 6.3.2.1) + Note over UE, V-SMF, V-ULCL/V-PSA, V-EASDF: 1. Serving network triggered EAS rediscovery + Note over UE, V-SMF, V-ULCL/V-PSA, V-EASDF, V-UPF, New V-EASDF: 2. V-SMF sends EAS rediscovery indication and UE refreshes DNS record + Note over UE, V-SMF, V-ULCL/V-PSA, V-EASDF, V-UPF, New V-EASDF: 3. EAS rediscovery procedure in VPLMN + +``` + +Sequence diagram of EAS rediscovery procedure in roaming scenario. The diagram shows interactions between UE, V-SMF, V-ULCL/V-PSA, V-EASDF, V-UPF, New V-EASDF, and H-SMF. The steps are: 0. EAS discovery procedure (as described in clause 6.3.2.1); 1. Serving network triggered EAS rediscovery; 2. V-SMF sends EAS rediscovery indication and UE refreshes DNS record; 3. EAS rediscovery procedure in VPLMN. + +**Figure 6.3.2.2-1: EAS rediscovery procedure accessing V-EHE in roaming scenario** + +- The procedure in clause 6.3.2.1 executes with following difference to apply to EAS rediscovery: + +In step 1, the UE may indicate its support for refreshing stale EAS information stored locally corresponding to the impact field per the EAS rediscovery indication from network to the V-SMF during the HR PDU Session Establishment procedure. + +NOTE 1: If the UE indicates such support, V-SMF may store this indication in the PDU Session context. + +- Due to the UE mobility the V-SMF triggers V-PSA insertion, change or removal for the PDU Session. The insertion, change or removal of V-PSA triggers EAS rediscovery. + +NOTE 2: This solution does not cover EAS rediscovery scenario triggered by AF. + +- V-SMF sends PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE as described in step 2 of clause 6.2.3.3 of TS 23.548 [3], with the following differences: + +V-SMF sends the impact field with the EAS rediscovery indication if the UE supports this indication. + +If V-SMF chooses new V-EASDF for the PDU Session, it does not provide the V-EASDF IP address to UE. V-SMF may configure V-UPF with the updated traffic routing rule (e.g. V-UPF routes DNS Queries for an FQDN (range) query to the new V-EASDF) and with corresponding EASDF IP replacement information (i.e. H-DNS server IP address and port number, new V-EASDF IP address and port number) as described in step 1 of clause 6.3.2.1. + +UE refreshes DNS record according to EAS rediscovery indication received from V-SMF. + +- UE may trigger EAS discovery procedure to get new EAS information. This DNS query is sent to corresponding DNS server using IP address replacement in VPLMN. + +### 6.3.3 Impacts on existing entities and interfaces + +H-SMF: + +- sends H-DNS server IP address and an EC enabling indicator to V-SMF in the HR PDU Session establishment procedure. + +V-SMF: + +- identifies the EC enabling indicator and manages the EC service for UE in VPLMN; +- selects and inserts the V-UL-CL and V-PSA based on local policy and does not need to interact with H-SMF; +- stores the indication which indicates that UE supports to refresh stale EAS information stored locally corresponding to the impact field per the EAS rediscovery indication from network in the PDU Session context; +- sends the EAS rediscovery indication including the impact field to UE. + +## 6.4 Solution 04 (KI#1): Support EAS (re-)discovery in VPLMN via HR PDU Session + +### 6.4.1 Description + +This solution corresponds to KI#1. The scenarios 2.1 and 2.2 are described in clause 5.1.2. + +As described in clause 5.1.2, a roaming UE may access V-EHE via an established HR PDU Session. To support such scenario, session breakout to access EHE in VPLMN is used. The following aspects are included: + +- The H-PCF provides authorization policy which indicates local traffic routing in VPLMN is authorized for the UE accessing the VPLMN. +- UL-CL/BP and local PSA insertion. + +The V-SMF performs selection and insertion of UL-CL/BP and local PSA based on UE location when receiving the authorization policy from H-SMF without considering EAS deployment information in VPLMN. In this case, UL-CL/BP is selected based on UE location. + +For scenario 2.1, the V-SMF may select and insert UL-CL/BP and local PSA based on UE location and target DNAI after PDU Session is established. The V-SMF selects target DNAI based on DNAIs received from H-SMF. The DNAIs are determined by H-SMF based on EAS IP report from H-EASDF. In this case, UL-CL/BP is selected based on UE location and selected EAS IP address. + +- EAS discovery using H-EASDF. + +For scenario 2.1, the H-SMF obtains ECS option/local DNS server from V-SMF during DNS based EAS discovery procedure and send it to H-EASDF. The H-EASDF handles DNS queries including FQDNs deployed in VPLMN based on the ECS option/local DNS server as defined in TS 23.548 [3]. In this case, different FQDNs may use different ECS option/local DNS Server. + +For scenario 2.2, the H-SMF obtains ECS option/local DNS server from V-SMF during PDU Session Establishment and send it to H-EASDF. The H-EASDF handles all DNS queries of the UE based on this ECS option/local DNS server. In this case, all DNS queries requested by the UE will share same ECS option/local DNS server. + +### 6.4.2 Procedures + +#### 6.4.2.1 EAS discovery + +Figure 6.4.2.1-1 shows the procedure of EAS discovery in VPLMN via HR PDU Session. + +![Sequence diagram illustrating EAS discovery in VPLMN via HR PDU Session. The diagram shows interactions between UE, V-SMF, UL CL/BP, H-SMF, H-PCF, H-EASDF, and DNS server. The process involves PDU Session Establishment, Nsmf_PDUSession_Create Request/Response, Npcf_SMPolicyControl_Create Request, Neasdf_DNSContext_Create Request/Response, Insert UL CL/BP and local PSA, DNS Query, Neasdf_DNSContext_Notify Request, Nsmf_PDUSession_Update Request/Response, Neasdf_DNSContext_Update Request, and DNS Response.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant UL CL/BP + participant H-SMF + participant H-PCF + participant H-EASDF + participant DNS server + + Note right of UL CL/BP: 6. Insert UL CL/BP and local PSA + Note right of UL CL/BP: 15b. Insert UL CL/BP and local PSA + + UE->>V-SMF: 1. PDU Session Establishment request + V-SMF->>H-SMF: 2. Nsmf_PDUSession_Create Request + H-SMF->>H-PCF: 3. Npcf_SMPolicyControl_Create Request + H-SMF->>H-EASDF: 4. Neasdf_DNSContext_Create Request/Response + H-SMF->>V-SMF: 5. Nsmf_PDUSession_Create Response + V-SMF->>UE: 7. PDU Session Establishment Accept + Note right of UE: 8. DNS Query + Note right of H-EASDF: 9. Neasdf_DNSContext_Notify Request + Note right of V-SMF: 10. Nsmf_PDUSession_Update Request + Note right of H-SMF: 11. Nsmf_PDUSession_Update Response + Note right of H-EASDF: 12. Neasdf_DNSContext_Update Request + Note right of DNS server: 13. DNS Query / Response + Note right of H-EASDF: 14. Neasdf_DNSContext_Notify Request + Note right of V-SMF: 15a. (H-SMF initiated) Nsmf_PDUSession_Update Request + Note right of V-SMF: 15c. Nsmf_PDUSession_Update Response + Note right of H-EASDF: 16. Neasdf_DNSContext_Update Request + Note right of UE: 17. DNS Response + +``` + +Sequence diagram illustrating EAS discovery in VPLMN via HR PDU Session. The diagram shows interactions between UE, V-SMF, UL CL/BP, H-SMF, H-PCF, H-EASDF, and DNS server. The process involves PDU Session Establishment, Nsmf\_PDUSession\_Create Request/Response, Npcf\_SMPolicyControl\_Create Request, Neasdf\_DNSContext\_Create Request/Response, Insert UL CL/BP and local PSA, DNS Query, Neasdf\_DNSContext\_Notify Request, Nsmf\_PDUSession\_Update Request/Response, Neasdf\_DNSContext\_Update Request, and DNS Response. + +**Figure 6.4.2.1-1: EAS discovery in VPLMN via HR PDU Session** + +1. UE sends PDU Session establishment request to V-SMF. +2. The V-SMF sends Nsmf\_PDUSession\_Create Request to H-SMF. + +For scenario 2.2 where HPLMN does not have the knowledge of EAS deployment in VPLMN, the V-SMF may, based on UE location, send information to build ECS option/local DNS server for the VPLMN from V-SMF to H-SMF. + +3. The H-SMF receives authorization policy which indicates whether local traffic routing in the VPLMN is authorized from H-PCF. + +The content of authorization policy includes the following information: + +- Local Traffic Routing Authorization Indication. The indication is used to indicate whether local traffic routing in VPLMN is authorized. +- Traffic description information, e.g. FQDN(s), EAS IP(s). The traffic description information is used to indicate the corresponding specific traffic is authorized to perform local traffic routing in VPLMN. + +4. H-SMF invokes Neasdf\_DNSContext\_Create Request including DNS handling rule to H-EASDF. + +For scenario 2.2, the H-SMF may send the information to build ECS option/local DNS server as described in step 2 to the H-EASDF. + +5. The H-SMF sends Nsmf\_PDUSession\_Create Response including authorization policy to the V-SMF. + +The H-SMF sends H-EASDF address to the V-SMF. + +6. [Conditional] The V-SMF performs UL-CL/BP and local PSA selection and insertion if the authorization policy indicates local traffic routing in the VPLMN is authorized for the traffic indicated by Traffic description information in the authorization policy. In this case, the V-SMF selects DNAI for the UL-CL/BP insertion based on UE location. + +The V-SMF also interacts with H-SMF to establish N9 tunnel between the UL-CL/BP and PSA controlled by H-SMF. Details can be found in steps 4-5 in clause 4.23.9.1 of TS 23.502 [9] by replacing I-SMF with V-SMF and SMF with H-SMF. + +To support charging in both PLMNs, the V-SMF provides Usage Reporting Rules to the UL-CL/BP and local PSA to collect Usage Report for charging in VPLMN. + +NOTE 1: The interactions between H/V-SMF and H/V-CHF are not in the scope of SA2. + +The V-SMF forwards the Usage Report to the H-SMF. The H-SMF aggregates and constructs usage reports towards H-CHF. + +7. The V-SMF sends PDU Session Establishment accept message including the H-EASDF address to UE. +8. UE sends DNS query which includes FQDN deployed in the VPLMN to the H-EASDF. + +For scenario 2.1, H-SMF may obtain ECS option/local DNS server from V-SMF by performing steps 9-12: + +9. The H-EASDF reports the FQDN to H-SMF by invoking Neasdf\_DNSContext\_Notify Request. + +H-SMF determines candidate DNAIs of VPLMN corresponding the FQDN based on the EAS deployment information in the VPLMN. H-SMF may consider UE location to select the candidate DNAIs of VPLMN in this step. (steps 10-12) + +10. The H-SMF initiates Nsmf\_PDUSession\_Update Request service including FQDN to the V-SMF. +11. V-SMF determines the target DNAI based on UE location and provides information to build ECS option or local DNS server to H-SMF based on the target DNAI. +12. H-SMF invokes Neasdf\_DNSContext\_Update Request to H-EASDF including updated DNS handling rule, e.g. information to build ECS option or local DNS server. +13. The H-EASDF adds ECS option into the DNS query and sends it to C-DNS server, or sends the DNS query to the local DNS server if the DNS query matches the DNS handling rule as described in clause 6.2.3 of TS 23.548 [3]. + +H-EASDF receives the DNS Response including EAS IP address which is determined by the DNS system. + +For scenario 2.1, H-SMF may trigger V-SMF selecting and inserting UL-CL/BP and local PSA by performing steps 14-16: + +14. The H-EASDF invokes Neasdf\_DNSContext\_Notify Request including EAS IP to the H-SMF based on DNS handling rule. +15. The H-SMF triggers the V-SMF to perform UL-CL/BP and local PSA selection and insertion as described in step 6 of clause 4.23.9.1 in TS 23.502 [9] by replacing I-SMF as V-SMF and SMF as H-SMF. + +H-SMF determines target DNAI of VPLMN corresponding the EAS IP based on the EAS deployment information in the VPLMN. + +The H-SMF initiates Nsmf\_PDUSession\_Update Request service including target DNAI of VPLMN to the V-SMF. + +The V-SMF selects and inserts UL-CL/BP and local PSA based on the target DNAI. + +The V-SMF also interacts with H-SMF to establish N9 tunnel between the UL-CL/BP and PSA controlled by H-SMF. Details can be found in steps 4-5 in clause 4.23.9.1 of TS 23.502 [9] by replacing I-SMF with V-SMF and SMF with H-SMF. + +The V-SMF sends Nsmf\_PDUSession\_Update Response to H-SMF. + +16. The H-SMF invokes Neasdf\_DNSContext\_Update Request to trigger the H-EASDF sending DNS response to UE. + +17. The H-EASDF sends the DNS response including the EAS IP to UE. + +#### 6.4.2.2 EAS re-discovery + +Figure 6.4.2.2-1 shows the procedure of EAS rediscovery in VPLMN via HR PDU Session. + +![Sequence diagram for EAS rediscovery in VPLMN via HR PDU Session. The diagram shows interactions between UE, Target V-SMF, Source V-SMF, ULCL/BP/L-PSA, H-SMF, and H-EASDF. It is divided into two main phases: Handover procedure and VPLMN L-PSA insert/change/remove procedure. The Handover procedure includes steps 1a1/1b (V-SMF insertion) and 1a2/1b (V-SMF change) where the Target V-SMF requests context from the H-SMF or Source V-SMF. A sub-step 1.C indicates the Target V-SMF selects a Target V-UPF. The VPLMN L-PSA procedure includes steps 2 through 6, involving Nsmf_PDUSession_Update requests and PDU Session Modification commands between the V-SMF, H-SMF, and UE, with a Neasdf_DNSContext_Update interaction between the H-SMF and H-EASDF.](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +Sequence diagram for EAS rediscovery in VPLMN via HR PDU Session. The diagram shows interactions between UE, Target V-SMF, Source V-SMF, ULCL/BP/L-PSA, H-SMF, and H-EASDF. It is divided into two main phases: Handover procedure and VPLMN L-PSA insert/change/remove procedure. The Handover procedure includes steps 1a1/1b (V-SMF insertion) and 1a2/1b (V-SMF change) where the Target V-SMF requests context from the H-SMF or Source V-SMF. A sub-step 1.C indicates the Target V-SMF selects a Target V-UPF. The VPLMN L-PSA procedure includes steps 2 through 6, involving Nsmf\_PDUSession\_Update requests and PDU Session Modification commands between the V-SMF, H-SMF, and UE, with a Neasdf\_DNSContext\_Update interaction between the H-SMF and H-EASDF. + +**Figure 6.4.2.2-1: EAS rediscovery in VPLMN via HR PDU Session** + +When UE moves with V-SMF insertion/change/remove, the procedure is performed from step 1. When UE moves without V-SMF change, the procedure is performed from step 2. + +1. The procedure described in clause 4.23.7 (N2 based handover) or 4.23.11 (Xn based handover) of TS 23.502 [9] is performed by replacing I-SMF with V-SMF and SMF with H-SMF. + - 1a1. (V-SMF insertion) The (target) V-SMF retrieves SM context requests SM context from H-SMF. + - 1a2. (V-SMF change) The target V-SMF retrieves SM context from the source V-SMF. +- 1b. SMF (H-SMF / source V-SMF) to target V-SMF: Nsmf\_PDUSession\_Context Response including the N9 FTEID/IP address of the H-UPF. The SMF responds with the requested SM context which includes authorization policy from H-SMF. The SM context also includes impact field corresponding to the old target DNAI if it has been inserted by H-SMF. Additionally, in case the PLMN ID received from the V-SMF in + +Nsmf\_PDUSession\_Context Request is different from H-SMF's own PLMN ID, the H-SMF provides the N9 FTEID/IP address of the H-UPF to the Target V-SMF. + +- 1c. The target V-SMF selects a target V-UPF: based on the received SM context, e.g. S-NSSAI and UE location information, and the N9 FTEID/IP address of the H-UPF, the target V-SMF selects a target V-UPF complying with the QoS/delay requirements. + +For the V-SMF remove case, step 2 and steps 4-5 are skipped, only steps 3 and 6 are performed. + +After the handover procedure, the (target) V-SMF performs UL-CL/BP and local PSA insertion/change/removal as described in clause 4.23.9 of TS 23.502 [9] by replacing I-SMF with V-SMF and SMF and H-SMF. Differences are shown as steps 2 to 5: + +2. The (target) V-SMF invokes Nsmf\_PDUSession\_Update Request (new target DNAI if available and corresponding information to build ECS option) to SMF. + +For the case of local PSA removal, the request message is sent to SMF without including any DNAI. + +3. The H-SMF determines DNAI is changed and updates DNS handling rules towards the H-EASDF by invoking Neasdf\_DNSContext\_Update service. +4. The H-SMF initiates Nsmf\_PDUSession\_Update Request towards the (target) V-SMF. +5. The V-SMF initiates PDU Session Modification command (EAS rediscovery indication and impact field) to UE. + +The impact field corresponds to the new target DNAI and old target DNAI. + +For the case of local PSA insertion/change, the (target) V-SMF determines the impact field based on the new target DNAI. Based on the received impact field in step 1 corresponding to old target DNAI, the target V-SMF determines the final impact field corresponding to the new target DNAI and old target DNAI. + +For the case of local PSA removal, as there is no new target DNAI, there is no impact field corresponding to the new target DNAI. + +6. (V-SMF removal case) The H-SMF initiates PDU Session Modification command to UE. + +For scenario 2.1, as the H-SMF has the knowledge of EAS deployment information in VPLMN, the H-SMF determines the impact field corresponding to old target DNAI inserted by the removed V-SMF. Then the H-SMF sends EAS rediscovery indication and the impact field to the UE. + +For scenario 2.2, as the H-SMF does not have the knowledge of EAS deployment information in VPLMN, the H-SMF only sends EAS rediscovery indication to the UE. + +For EAS rediscovery triggered by AF, if the AF can interact with the HPLMN via H-NEF, the EAS re-discovery procedure is performed from step 4. + +NOTE: For the AF that cannot interact with HPLMN via H-NEF, the EAS rediscovery triggered by AF is not supported in this Release. + +### 6.4.3 Impacts on services, entities and interfaces + +#### EAS discovery: + +##### H-PCF: + +- retrieves and sends authorization policy to H-SMF which indicates local traffic routing in VPLMN is authorized. + +##### H-SMF: + +- sends H-EASDF address to V-SMF; +- sends authorization to V-SMF; +- receives information to build ECS option/local DNS server from V-SMF; +- receives Usage Report corresponds to local routed traffic in VPLMN from V-SMF; + +- in case the PLMN ID sent by V-SMF is different from H-SMF's own PLMN ID, the H-SMF provides in Nsmf\_PDUSession\_Context Response the N9 FTEID/IP address of the H-UPF to the target V-SMF; +- for scenario 2.1: + - sends FQDN to V-SMF. +- for scenario 2.2: + - configured with information to build ECS option/local DNS server. + +**V-SMF:** + +- receives H-EASDF address from H-SMF; +- receives authorization policy from H-SMF; +- sends Usage Report corresponds to local routed traffic in VPLMN; +- the target V-SMF selects a target V-UPF based on the received SM context, e.g. S-NSSAI and UE location information, and the N9 FTEID/IP address of the H-UPF; +- for scenario 2.1: + - receives FQDN from H-SMF; + - determines information to build ECS option/local DNS server based on candidate DNAIs and UE location; + - sends information to build ECS option/local DNS server to H-SMF; + - receives target DNAI from H-SMF and perform UL-CL/BP insertion. +- for scenario 2.2: + - sends ECS Option/local DNS server of the VPLMN to H-SMF; + - determines DNAI and perform UL-CL/BP insertion based on the UE location and authorization policy. + +**V-NRF:** + +- additionally receives the N9 IP address of the H-UPF in NRF discovery request from target V-SMF; +- provides candidate list of V-UPFs to target V-SMF based on S-NSSAI and UE location information, and the N9 IP address of the H-UPF. + +**EAS rediscovery:****V-SMF:** + +- (V-SMF insertion/change) receives SM context including authorization policy and impact field corresponding to old target DNAI from source V-SMF/H-SMF; +- (V-SMF insertion/change) determines impact field based on new target DNAI and impact field received from V-SMF/H-SMF. + +**H-SMF:** + +- (V-SMF insertion) sends SM context including authorization policy and impact field corresponding to old target DNAI to V-SMF; +- (V-SMF removal) initiates PDU Session modification procedure for EAS rediscovery. + +## 6.5 Solution 05 (KI#1): Accessing V-EHE via HR PDU Session + +### 6.5.1 Description + +The following solution corresponds to the key issue #1 on Accessing EHE in a VPLMN when roaming as specified in clause 5.1. + +The UE establishes a Home Routed PDU Session using session breakout to access the EHE in VPLMN. The V-SMF determines the HR PDU Session for V-EHE should be activated based on the EAS information and roaming offload policy received from H-PCF via H-SMF, and configures the traffic routing rule and Usage Report Rule to assist traffic offload to V-EAS and usage information report from UL-CL V-UPF or BP V-UPF to H-SMF via V-SMF for offline and online charging. + +![Diagram illustrating UP traffic and CP signalling for scenario of accessing V-EHE via a HR PDU Session. The diagram shows the flow of traffic and signaling between the UE, V-SMF, V-UPF (UL CL/BP), V-UPF (L-PSA), EAS (Local part of DN), H-SMF, H-UPF, and Central DN across VPLMN and HPLMN boundaries.](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +The diagram illustrates the network architecture and data flow for accessing V-EHE via a Home Routed (HR) PDU Session. It is divided into two main domains by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. + +- UE (User Equipment):** Located in the VPLMN. It sends **UP traffic** (indicated by a blue dashed line) to the **V-UPF (UL CL/BP)**. +- V-UPF (UL CL/BP):** A User Plane Function in the VPLMN that handles uplink traffic. It is connected to the **V-SMF** (Session Management Function) via a green dashed line representing **CP (usage information)** signaling. +- V-UPF (L-PSA):** A second User Plane Function in the VPLMN, acting as a Local PDN Session Anchor. It receives traffic from the V-UPF (UL CL/BP) and is connected to the **EAS (Local part of DN)**. +- EAS (Local part of DN):** The Edge Application Server located in the VPLMN. +- V-SMF:** The Session Management Function in the VPLMN. It is connected to the **H-SMF** in the HPLMN via a green dashed line for **CP (usage information)** signaling. +- H-SMF:** The Session Management Function in the HPLMN. It is connected to the **H-UPF**. +- H-UPF:** The User Plane Function in the HPLMN. It receives traffic from the **V-UPF (UL CL/BP)** and forwards it to the **Central DN**. +- Central DN:** The Core Network in the HPLMN. + +Diagram illustrating UP traffic and CP signalling for scenario of accessing V-EHE via a HR PDU Session. The diagram shows the flow of traffic and signaling between the UE, V-SMF, V-UPF (UL CL/BP), V-UPF (L-PSA), EAS (Local part of DN), H-SMF, H-UPF, and Central DN across VPLMN and HPLMN boundaries. + +Figure 6.5.1-1: UP traffic and CP signalling for scenario of accessing V-EHE via a HR PDU Session + +## 6.5.2 Procedures + +### 6.5.2.1 EAS discovery + +![Sequence diagram illustrating the EAS discovery procedure for accessing V-EHE via a HR PDU Session. The diagram shows interactions between UE, V-SMF, V-UPF (UL CL/BP), V-UPF (PSA), H-SMF, and H-PCF across VPLMN and HPLMN domains.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant V-UPF_UL as V-UPF (UL CL/BP) + participant V-UPF_PSA as V-UPF (PSA) + participant H-SMF + participant H-PCF + + Note left of UE: VPLMN + Note right of H-PCF: HPLMN + + UE->>V-SMF: 1. PDU Session Establishment Request + V-SMF->>H-SMF: 2. Nsmf_PDUSession_Create Request + H-PCF->>V-SMF: 3. H-PCF may provide the authorized roaming offload policy to V-SMF via H-SMF + Note left of V-SMF: 4. V-EASDF selection + Note right of V-UPF_PSA: 5. UE sends DNS query to V-EASDF, and EAS information is retrieved + V-SMF->>V-UPF_UL: 6. Configure traffic routing rule and URR to the UL CL/BP V-UPF + Note right of V-UPF_PSA: 7. UL/DL traffic is routed between UE and V-EAS via UL CL/BP UPF + V-UPF_PSA->>H-SMF: 8. Send usage information (and charging information) to H-SMF + +``` + +Sequence diagram illustrating the EAS discovery procedure for accessing V-EHE via a HR PDU Session. The diagram shows interactions between UE, V-SMF, V-UPF (UL CL/BP), V-UPF (PSA), H-SMF, and H-PCF across VPLMN and HPLMN domains. + +**Figure 6.5.2.1-1: Accessing V-EHE via a HR PDU Session** + +1. The UE initiates a Home Routed PDU Session establishment procedure with V-SMF. +2. The V-SMF sends Nsmf\_PDUSession\_Create Request to H-SMF. +3. The H-PCF may provide the authorized roaming offload policy to V-SMF via H-SMF. The roaming offload policy includes the specific Application Identifier(s) or FQDN set or IP range, and indicates if the Application Identifier or FQDN or EAS IP is satisfied, the HR PDU Session for V-EHE is activated (e.g. inserts a V-UPF accessing EAS). The H-SMF may also send the IP address of Home DNS server to V-SMF. +4. The V-SMF selects a V-EASDF, and the EAS Deployment Information in VPLMN is provisioned as specified in clause 6.2.3 of TS 23.548 [3]. The V-SMF includes the IP address of the V-EASDF as DNS server/resolver for the UE in the PDU Session Establishment Accept message. According to the roaming offload policy and the EAS Deployment Information, the V-SMF configures DNS message handling rules to V-EASDF. The V-EASDF handles all DNS queries based on the DNS message handling rules. If the requested FQDN matches the DNS message handling rule for VPLMN traffic routing, the V-EASDF decides to send the DNS Query to Local DNS server or C-DNS server (adding EDNS Client Subnet option). If the requested FQDN matches the DNS message handling rule for HPLMN traffic routing, the V-EASDF may send it to Home DNS server. The Home DNS server could be locally configured at V-SMF or received from H-SMF in step 3. +5. The UE sends a DNS Query message to the V-EASDF, and the V-EASDF performs EAS discovery as specified in clause 6.2.3 of TS 23.548 [3]. The discovered EAS information is reported to V-SMF. +6. Based on the received EAS information (e.g. EAS IP address) and the roaming offload policy, the V-SMF decides to insert or relocate UL-CL/BP V-UPF and PSA V-UPF for traffic offload to the V-EAS. +7. The V-SMF configures traffic routing rule and Usage Report Rule on the UL-CL V-UPF or the BP V-UPF. The traffic routing rule includes EAS IP (for UL-CL) or IP prefix @local PSA (for BP) to route traffic towards the V- + +EAS. The Usage Report Rule is to request the report of the relevant usage information via monitoring traffic from UE to V-EAS, which is used for offline and online charging. + +8. UL and DL traffic routed between UE and V-EAS via UL-CL V-UPF or BP V-UPF. The UL-CL V-UPF or V-UPF collects and reports the usage information to V-SMF. +9. The V-SMF sends usage information received from V-UPF to the H-SMF, and the H-SMF generates charging information. Alternatively, the V-SMF may generate the charging information, and sends both usage information and charging information to H-SMF. + +### 6.5.2.2 EAS re-discovery + +Figure 6.5.2.2-1 shows the procedure of EAS rediscovery in VPLMN via HR PDU Session. + +![Sequence diagram for EAS rediscovery in VPLMN via HR PDU Session. The diagram shows interactions between UE, Target V-SMF, Source V-SMF, V-UL CL/V-PSA, V-EASDF, H-SMF, and AF. Step 1: Due to UE mobility or AF triggered EAS relocation, the target V-SMF is selected and informed the roaming offload policy and the information for EAS relocation. Step 2: EAS re-discovery procedure is performed. Step 3: PDU Session Modification Command is sent from the Target V-SMF to the UE.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target V-SMF + participant Source V-SMF + participant V-UL CL/V-PSA + participant V-EASDF + participant H-SMF + participant AF + + Note over UE, AF: 1. Due to UE mobility or AF triggered EAS relocation, the target V-SMF is selected and informed the roaming offload policy and the information for EAS relocation + Note over Target V-SMF, V-EASDF: 2. EAS re-discovery procedure is performed + Note over UE, Target V-SMF: 3. PDU Session Modification Command + +``` + +Sequence diagram for EAS rediscovery in VPLMN via HR PDU Session. The diagram shows interactions between UE, Target V-SMF, Source V-SMF, V-UL CL/V-PSA, V-EASDF, H-SMF, and AF. Step 1: Due to UE mobility or AF triggered EAS relocation, the target V-SMF is selected and informed the roaming offload policy and the information for EAS relocation. Step 2: EAS re-discovery procedure is performed. Step 3: PDU Session Modification Command is sent from the Target V-SMF to the UE. + +**Figure 6.5.2.2-1: EAS rediscovery in VPLMN via HR PDU Session** + +- 1a. Due to the UE mobility, the V-SMF insertion/change/remove is triggered, the procedure is performed as described in step 1 of clause 6.4.2.2 (solution #04). +- 1b. If the AF triggers EAS relocation, the H-AF provides the EAS deployment information and IP address of target EAS to network. + +The H-SMF determines the target DNAI based on the EAS deployment information and IP address of target EAS. The H-SMF sends the target DNAI to the H-AMF by invoking Nsmf\_PDUSession\_SMContextStatusNotify service operation. The H-AMF selects V-SMF based on the target DNAI as described in clause 4.23.5.4 of TS 23.502 [9]. + +In the case of V-SMF insertion, the target V-SMF retrieves SM context which includes roaming offload policy and the information for EAS relocation from H-SMF. In case of V-SMF change, the target V-SMF retrieves SM context which includes roaming offload policy and the information for EAS relocation from the source V-SMF. + +2. The procedure is performed as described in step 2 of clause 6.2.3.3 of TS 23.548 [3], with the following differences: + - In the case of V-PSA insertion/change, the (target) V-SMF determines the impact field based on the new target DNAI. + +According to the roaming offload policy and new target DNAI, the V-SMF may select a new V-EASDF and configures DNS message handling rules to (new) V-EASDF. The (new) V-EASDF handles all DNS queries based on the DNS message handling rules as described in clause 6.5.2.1. + +3. The V-SMF sends PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE. + +### 6.5.3 Impacts on services, entities and interfaces + +V-SMF: + +- receives the roaming offload policy included in PCC rule from H-PCF via H-SMF; + +- generates the DNS message handling rules according to the roaming offload policy and the EAS Deployment Information; +- generates traffic routing rule and Usage Report Rule according to EAS information and roaming offload policy; +- sends usage information (and charging information, if it is generated by V-SMF) to H-SMF; +- interacts with V-EASDF using the interface defined between SMF and EASDF in TS 23.548 [3], including configuring DNS message handling rules to EASDF according to the roaming offload policy; +- receives the information for EAS relocation from source V-SMF/H-SMF. + +V-PCF: + +- creates PCC rule that includes roaming offload policy. + +H-SMF: + +- sends the roaming offload policy to V-SMF; +- sends the information for EAS relocation to V-SMF; +- receives usage information (and charging information, if it is generated by V-SMF) from V-SMF. + +## 6.6 Solution 06 (KI#1): URSP solution to support roamers access to EHE in a VPLMN + +### 6.6.1 Description + +UE not served by their home network should where possible (when allowed by their home network) benefit from traffic offload and Edge Computing capabilities deployed by their serving network. + +A solution is to leverage clause 6.6 of TS 23.548 [3] "Support of AF Guidance to PCF Determination of Proper URSP Rules" and clause 4.15.6.10 of TS 23.502 [9] "Application guidance for URSP rules determination mechanisms" as defined for Rel-17. This is to guide UE for traffic to be offloaded in the VPLMN to use a specific DNN and slice deployed in LBO mode while the rest of the traffic can use HR PDU Session(s). + +An AF belonging to the VPLMN reaching the NEF of the HPLMN (a roaming partner) indicates the (VPLMN) DNN and slices related with traffic offload / EC that it supports (according to clause 6.6 of TS 23.548 [3] and clause 4.15.6.10 of TS 23.502 [9]) this indication can be leveraged by the PCF of the HPLMN to (if authorized by HPLMN policies) provide dedicated URSP rules applicable to relevant users of the HPLMN when they are roaming in that VPLMN. These URSP may have a validity condition corresponding to the VPLMN location but should refer to S-NSSAI(s) defined by the HPLMN. + +NOTE 1: The interaction from AF in VPLMN to the NEF in HPLMN does not involve the SEPP. + +This interaction between the AF belonging to the VPLMN and the HPLMN NEF is not related to a specific UE, but is meant to cover all UEs matching the VPLMN related location criteria. + +The AF belonging to the VPLMN provides HPLMN S-NSSAI(s) (that are determined from the VPLMN S-NSSAI(s)). + +NOTE 2: As the VPLMN has the translation between HPLMN S-NSSAI(s) and the VPLMN S-NSSAI(s), translation is needed in the VPLMN to serve the HPLMN users. + +The H-PCF may, based on local policies, determine whether to always send the URSP rules immediately to the UE or to send these rules only when the UE is served by the corresponding serving PLMN, e.g. waiting to be triggered from a V-PCF of that PLMN in step 3 of clause 4.6.11 of TS 23.502 [9]. + +The PCF of the HPLMN when it sends such URSP update to a UE, needs, as for Rel-17, to ensure that the DNN, S-NSSAI provided in the URSP rules sent to the UE is allowed in LBO mode in the user subscription (in UDM/UDR) even when the UE is roaming in that VPLMN. + +NOTE 3: This solution can also apply for UEPO (see TR 23.700-85 [10]). + +The VPLMN may provide Geographical or VPLMN location (e.g. VPLMN TAI or cells) related validity conditions for the URSP to apply. When the AF belonging to the VPLMN provides the HPLMN with VPLMN validity conditions, the VPLMN location information (e.g. VPLMN TAI or cells) contains a VPLMN ID that may be used by the H-PCF to understand that this information is specific for a VPLMN. + +Depending on H-PCF policies (on when to deliver URSP(s) valid in remote PLMN(s)) and on the situation (e.g. UE arriving rapidly in a new PLMN when for example the user arrives by plane in a remote country), it may take some time before URSP rules take effect in UE: it may happen that the UE gets URSP(s) applicable to the VPLMN while HR PDU Sessions have already been established. As defined in TS 23.503 [13], "For every newly detected application the UE evaluates the URSP rules in the order of Rule Precedence and determines if the application is matching the Traffic descriptor of any URSP rule." Thus, it may happen that some traffic has started using HR PDU Sessions, but as soon as new application interactions start, corresponding traffic will gradually be moved to LBO PDU Sessions in the serving PLMN while already started IP flows may go on using the H-UPF. + +It can happen that traffic that used to be served by a unique PDU Session while the UE was served by its HPLMN becomes served by 2 PDU Sessions when the UE roams in a VPLMN for which URSP guides it to use a LBO PDU Session for an application while it should use the initial PDU Session in HR mode for the rest of the traffic. + +NOTE 4: This can happen regardless of Edge Computing. + +NOTE 5: Before concluding this solution for normative work, alignment check with FS\_eUEPO shall be done in order to avoid any conflict with the conclusion of KI#1 in TR 23.700-85 [10]. Final decision on generic URSP enhancement for supporting LBO roaming case should be made within FS\_eUEPO study. + +## 6.6.2 Procedures + +The solution reuses existing procedures. + +## 6.6.3 Impacts on Existing Nodes and Functionality + +- The VPLMN and the HPLMN as part of the roaming agreement need to ensure that an AF belonging to the VPLMN can contact the NEF of the HPLMN to use the API defined in clause 4.15.6.10 of TS 23.502 [9]. +- Potential UDM impact to ensure that the DNN, S-NSSAI provided in the URSP rules sent to the UE is allowed in LBO mode in the user subscription (in UDM/UDR) even when the UE is roaming in that VPLMN. + +# 6.7 Solution 07 (KI#1): Using URSP Rules to Establish an LBO PDU Session + +## 6.7.1 Description + +### 6.7.1.1 General + +This solution addresses that part of Key Issue #1 that considers how to establish the LBO PDU Session towards the correct S-NSSAI/DNN pair in order to access an EHE in the VPLMN. + +The principles of this solution are: + +- In Rel-17, a URSP rule can already be configured with Location Criteria that indicates to the UE that the route (i.e. PDU Session) should only be established, or used, when the UE served by certain cell(s), RAN node(s), or TAIs. This feature can be used to cause the UE to select a DNN/S-NSSAI combination that is appropriate for the PLMN where the UE is registered (e.g. an LBO Session). Location criteria is defined in TS 24.526 [11] and may be a list of cell(s), RAN node(s), or TAI(s). This solution proposes that Location Criteria can also include PLMN ID(s). + +NOTE: Whether a PLMN ID can be encoded as part of Location Criteria or encoded as a new validation criteria information element is left to stage 3. + +- When a route includes Location Criteria, a "Revaluation Suggested" indication can be added to the RSD. A "Revaluation Suggested" indication in the RSD indicates to the UE that the UE should re-evaluate URSP rules + +for traffic that uses the PDU Session if the Location Criteria becomes invalid and release the PDU Session no traffic is using the PDU Session after re-evaluation. In other words, the PDU Session may be released when the UE leaves the PLMN, cell(s), RAN node(s), or TAI(s) where the location criteria is valid and all traffic is moved to a different PDU Session (e.g. an LBO PDU Session). + +- Triggering re-evaluation will cause the UE to select a new route. The new route may include location criteria for the UE's new location and a PDU Session will be established with a DNN/S-NSSAI combination that is better suited for the UE's new location (e.g. for the PLMN where the UE is now registered). + +NOTE: It is a UE implementation decision when to re-evaluate URSP rules. The indication is used to by the UE to help determine if it should re-evaluate. + +### 6.7.1.2 Procedure + +The UE receives URSP rules. Some URSP rules may have Traffic Descriptors that are associated with edge services. The RSDs of these URSP rules may include Location Criteria. By including Location Criteria, the URSP rule can be configured such that the UE will select a DNN/S-NSSAI combination for PDU Session Establishment based on the UE's cell, RAN Node, TAI or PLMN ID. Thus, the UE will use a DNN/S-NSSAI combination based on the PLMN that the UE is registered with. For example, the route will only be considered valid if the PLMN ID in the Location Criteria matches the PLMN ID of the PLMN where the UE is currently registered or if the PLMN ID in the Location Criteria is an equivalent PLMN of the PLMN where the UE is currently registered. + +Existing Rel-17 behaviour is that when the UE leaves the cell, RAN Node, or tracking area, the UE will continue to use the PDU Session until URSP Rules are re-evaluated. However, the UE is not required to re-evaluate URSP rules for the traffic. + +This solution proposes that the RSD(s) also include a "Revaluation Suggested" indication. When a change of cell, RAN node, TAI, or PLMN occurs, the existing PDU Session will be released if no longer needed and the UE will re-evaluate URSP rules. URSP re-evaluation will cause the UE to choose a new RSD for the traffic. The location criteria in the new RSD will cause the UE to select a DNN/S-NSSAI that is associated with the PLMN where the UE is currently registered. + +NOTE: Before concluding this solution for normative work, alignment check with FS\_eUEPO shall be done in order to avoid any conflict with the conclusion of KI#1 in TR 23.700-85 [10]. Final decision on generic URSP enhancement for supporting LBO roaming case should be made within FS\_eUEPO study. + +## 6.7.2 Impacts on services, entities and interfaces + +PCF: + +- can include the "Revaluation Suggested" indication in RSDs or URSPs; +- can include PLMN ID(s) in location criteria. + +UE: + +- can receive the "Revaluation Suggested" indication in RSDs or URSPs; +- can use the "Revaluation Suggested" indication to decide when to trigger URSP re-evaluation; +- can receive PLMN ID(s) in location criteria. + +## 6.8 Solution 08 (KI#1): V-ECS Discovery during Steering of Roaming + +### 6.8.1 Description + +#### 6.8.1.1 General + +This solution addresses that part of Key Issue #1 that considers how to configure the VPLMN ECS address to UE in roaming scenarios. + +The principle of this solution is that the Steering of Roaming framework that is specified in TS 23.122 [12] can be extended to provide information to the UE so that the EEC can communicate with an ECS in VPLMN (i.e. a V-ECS). This solution explains how the SoR transparent container can be used to provide information to the UE that can be used to establish an LBO PDU Session that is used to reach a V-ECS. + +NOTE: CT1 has stage 2 and stage 3 responsibility for the Steering of Roaming feature. If this solution is selected for normative work, coordination with CT1 would be required. + +#### 6.8.1.2 Procedure + +As one option, the SoR transparent container can be used to provide an FQDN or an IP Address of a V-ECS to the UE. 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 ECS (e.g. an LBO Session). + +As a second option, the SoR transparent container can be used to 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 in the VPLMN 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 TS 23.548 [3]. The EEC may then use the ECS FQDN or IP Address from the ECS Address Configuration Information. + +Figure 6.8.1.2-1 procedure illustrates a procedure for this solution. + +![Sequence diagram showing V-ECS Discovery during Steering of Roaming. The diagram involves three entities: UE, 3GPP Core Network, and V-ECS. The sequence of messages is: 1. Receive SoR Transparent Container (UE to 3GPP Core Network), 2. PLMN Selection (UE internal), 3. Registration (UE to 3GPP Core Network), 4. PDU Session Establishment (UE to 3GPP Core Network), 5. Service Provisioning Request (3GPP Core Network to V-ECS), and 6. Service Provisioning Response (V-ECS to 3GPP Core Network).](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` +sequenceDiagram + participant UE + participant 3GPP Core Network + participant V-ECS + Note left of UE: 1. Receive SoR Transparent Container + Note left of UE: 2. PLMN Selection + Note left of UE: 3. Registration + Note left of UE: 4. PDU Session Establishment + 3GPP Core Network->>V-ECS: 5. Service Provisioning Request + V-ECS-->>3GPP Core Network: 6. Service Provisioning Response +``` + +Sequence diagram showing V-ECS Discovery during Steering of Roaming. The diagram involves three entities: UE, 3GPP Core Network, and V-ECS. The sequence of messages is: 1. Receive SoR Transparent Container (UE to 3GPP Core Network), 2. PLMN Selection (UE internal), 3. Registration (UE to 3GPP Core Network), 4. PDU Session Establishment (UE to 3GPP Core Network), 5. Service Provisioning Request (3GPP Core Network to V-ECS), and 6. Service Provisioning Response (V-ECS to 3GPP Core Network). + +**Figure 6.8.1.2-1: V-ECS Discovery during Steering of Roaming** + +1. The UE receives the SoR Transparent Container. The SoR Transparent Container may include a new information element called ECS Discovery Information. The ECS Discovery Information may include ECS Contact Information (O), ECS Provider ID (O), DNN (O), and S-NSSAI (O). The network may have been pre-provisioned with the ECS Discovery information (e.g. via OAM) and what ECS Discovery information is sent to the UE may be based on roaming agreement (e.g. the roaming agreement may allow the HPLMN to point the UE to an ECS in the EHE of the VPLMN). +2. As described in TS 23.122 [12], the reception of the SoR Transparent Container triggers the UE to perform PLMN Selection. +3. The UE registers with a PLMN that was provided in the SoR Transparent Container. +4. The UE establishes an LBO PDU Session that will be used to communicate with the V-ECS and/or to obtain ECS Contact Information from the VPLMN. + +Option A: The ECS Discovery Information from step 1 may have included only ECS Contact Information (i.e. an FQDN of an ECS in the VPLMN). 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). + +Option B: The ECS Discovery Information from step 1 may have included only 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 TS 23.548 [3]. +5. The EEC sends a Service Provisioning Request to an ECS in the visited network. The ECS address was obtained in step 1 or step 4. + +6. The EEC receives a Service Provisioning Response. + +## 6.8.2 Impacts on services, entities and interfaces + +SoR-AF: + +- can provide ECS Discovery Information. + +UE: + +- can receive the ECS Discovery Information in the SoR Transparent Container. + +## 6.9 Solution 09 (KI#1): PDU Session configuration from EASDF + +### 6.9.1 Description + +This solution addresses KI#1: Accessing EHE in a VPLMN when roaming. + +In this solution, the UE uses a predefined FQDN to the EASDF that is shared between operators. For example, GSMA could host the root entry for this Global EASDF. This solution is based on that the Global EASDF supports either configuration for a local EASDF or configuration for the UE to set up a new PDU Session. + +For a specific VPLMN, if the HPLMN requires the UE to use a new (LBO) PDU Session to access the V-PLMN's EHE, then the HPLMN will configure the Global EASDF with configuration for the UE to use to set up a new PDU Session. When the UE initiates the new PDU Session, then the UE will receive all needed configuration from the V-SMF for EAS discovery in the V-PLMN's network. If the HPLMN instead uses HR PDU Session, then it will configure the Global EASDF with the IP address of the EASDF in the V-PLMN's network. The UE will then use that one to discover EAS(s) in the V-PLMN. This allows the V-PLMN to utilize local traffic routing to the V-PLMN's EHE according to the agreement between them. + +The Global EASDF acts as a DNS server to provide the UE with either the IP address of the EASDF that the UE should use in the V-PLMN or the S-NSSAI/DNN combination that the UE will use to set up a PDU Session. + +This solution does not utilize URSP rules for the UE to retrieve and set up new PDU Session. + +### 6.9.2 Procedures + +#### 6.9.2.1 PDU Session configuration from EASDF + +![Sequence diagram illustrating the PDU Session configuration from EASDF. The diagram shows interactions between a UE, V-PLMN (EAS, Local EASDF, SMF), H-PLMN (SMF), and GSMA (Global EASDF).](16d7062de0d42e048d1bb46d792d37b0_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph V-PLMN + EAS + LocalEASDF[Local EASDF] + SMF_V[SMF] + end + subgraph H-PLMN + SMF_H[SMF] + end + subgraph GSMA + GlobalEASDF[Global EASDF] + end + + Note over UE, SMF_V: 0 PDU session establishment + UE->>GlobalEASDF: 1 EASDF Discovery & PDU Session Configuration Request (DNS Request) + GlobalEASDF-->>UE: 2 DNS Response + Note over UE, SMF_V: 3 PDU session establishment + UE->>LocalEASDF: 4 Local EAS Discovery (DNS Request) + LocalEASDF-->>UE: 5 DNS Response + Note over UE, EAS: 6 Application session to the EAS + +``` + +Sequence diagram illustrating the PDU Session configuration from EASDF. The diagram shows interactions between a UE, V-PLMN (EAS, Local EASDF, SMF), H-PLMN (SMF), and GSMA (Global EASDF). + +Figure 6.9.2-1: PDU Session configuration from EASDF + +0. Pre-requisites: The UE has a Home Routed PDU Session and the HPLMN has configured the Global EASDF with appropriate configuration for supported Visitors EHE(s). +1. The UE performs a DNS query to the Global EASDF. Since this is a public FQDN to the Global EASDF, the UE may use any locally configured DNS Server that in turn will use next DNS server in the DNS hierarchy until it goes to the Global EASDF. +2. The Global EASDF responds with either the configuration the UE needs to set up a PDU Session in the V-PLMN or the IP address of the local EASDF. + +If the V-PLMN uses existing PDU Session (HR PDU Session with local traffic routing) then the Global EASDF is configured with the V-PLMN's EASDF. If the operators require a new LBO PDU Session, then the Global EASDF is only configured with the configuration the UE needs to set up the new PDU Session. + +NOTE: When the HR PDU Session with local traffic routing is used, the V-EASDF sent to the UE via DNS response applies to the DNS query being handled. The subsequent DNS queries are sent to the Global EASDF for further handling, which may repeat step 2. + +3. If PDU Session configuration was received, then the UE initiates a PDU Session Establishment procedure with the configuration received in previous step. The V-SMF initiates and configures the EASDF selection and related DNS handling rules when the UE initiates the PDU Session Establishment procedure to the V-PLMN. The SMF may indicate to the UE the EASDF that the UE shall use for this PDU Session according to steps 1 and 2 in clause 6.2.3.2.2 of TS 23.548 [3]. +4. The UE performs EAS Discovery, same as step 7 in clause 6.2.3.2.2 of TS 23.548 [3]. If the UE received an EASDF address during step 2 above, then the UE uses that address instead of the one provided by the PDU Session establishment. +5. EASDF sends the DNS Response(s) to the UE, same as step 19 in clause 6.2.3.2.2 of TS 23.548 [3]. +6. The UE application starts to utilize the provided EAS. + +## 6.9.2.2 DNS structure + +The DNS structure uses the following format: + +easdf.cmnc.cmcc.mnc.mcc. + +The is replaced by the UE with the Mobile Network Code from the subscription. + +The is replaced by the UE with the Mobile Country Code from the subscription. + +The is replaced by the UE with the (Current) Mobile Network Code the UE is roaming into. + +The is replaced by the UE with the (Current) Mobile Country Code the UE is roaming into. + +The MNC/MCC pair represents the H-PLMN + +The CMNC/CMCC pair represents the V-PLMN + +With this structure, each H-PLMN decides and manages what configuration should be included for each roaming partner since all configuration for each V-PLMN is encoded as sub-domain for the H-PLMN. + +The following DNS record types is used: + +CNAME OR A Record: + +This type is used by the operator to configure which local EASDF the UE should use when the H-PLMN utilises HR PDU Session with local traffic routing in that specific V-PLMN. + +SRV Record: + +This type should be used by the operator to configure the UE with the PDU Session configuration to set up a local PDU Session that terminates in V-PLMN. The following syntax is used for the SRV record: + +"\_dnn.\_tcp.." + +The is replaced with any domain name that the operator owns. The SRV Record target syntax is .. The SD (Slice Differentiator) should always be included and according to clause 28.4.2 of TS 23.003 [16] a reserved value is defined ("FFFFFF") when no SD is defined. The SST shall be set as port number. + +### 6.9.3 Impacts on services, entities and interfaces + +UE: + +- configured with the FQDN of the Global EASDF; +- needs to receive PDU Session configuration in an SRV record and use information from the record to establish a PDU Session; +- when existing PDU Session should be used, then the UE uses the IP Address from the Global EASDF instead of the one provided in the ePCO from the PDU Session establishment procedure for the EASDF. + +Global EASDF: + +- acts as a DNS Server and responds to the DNS Queries from the UE. The DNS is configured with standard DNS SRV records that contains PDU Session configuration. + +## 6.10 Solution 10 (KI#1): LBO PDU Session establishment using PLMN criteria in RSD + +### 6.10.1 Description + +This solution corresponds to KI#1, and addresses the scenario which UE accessing EHE in VPLMN using LBO PDU Session. + +For better illustration, it is assumed that Service 1 is deployed in both HPLMN and EHE in VPLMN, and Service 2 is deployed only in HPLMN (or deployed in EHE in VPLMN, but the UE is not allowed to access to EHE in VPLMN for Service 2). + +When UE accesses to VPLMN, UE may access to EHE in VPLMN via a LBO PDU Session, and access to HPLMN via a HR PDU Session. That means URSP rules with different RSDs shall be used for Service 1 accessing to EHE in VPLMN and Service 2 accessing to HPLMN. + +When UE access to HPLMN, it is unnecessary to access to Service 1 and Service 2 via different PDU Sessions. That means URSP rules with same RSD shall be used for Service 1 and Service 2. + +Adding Route Selection Validation Criteria related to PLMN(s) is a way to meet both requirements on S-NSSAI/DNN pair mentioned above. Table 6.10.1-1 illustrates the enhanced RSD, and Table 6.10.1-2 gives an example of the enhanced RSD for Service 1. + +Table 6.10.1-1: Route Selection Descriptor with PLMN criteria + +| Information name | Description | Category | PCF permitted to modify in URSP | Scope | +|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------|-------------------| +| Route Selection Descriptor Precedence | Determines the order in which the Route Selection Descriptors are to be applied. | Mandatory (NOTE 1) | Yes | UE context | +| Route selection components | This part defines the route selection components | Mandatory (NOTE 2) | | | +| Network Slice Selection | Either a single value or a list of values of S-NSSAI(s). | Optional (NOTE 3) | Yes | UE context | +| DNN Selection | Either a single value or a list of values of DNN(s). | Optional | Yes | UE context | +| Route Selection Validation Criteria (NOTE 6) | This part defines the Route Validation Criteria components | Optional | | | +| Time Window | The time window when the matching traffic is allowed. The RSD is not considered to be valid if the current time is not in the time window. | Optional | Yes | UE context | +| Location Criteria | The UE location where the matching traffic is allowed. The RSD rule is not considered to be valid if the UE location does not match the location criteria. | Optional | Yes | UE context | +| PLMN Criteria (new) | The PLMN(s) where the matching traffic is allowed. The RSD is not considered to be valid if the serving PLMN does not match the PLMN criteria. | Optional (NOTE 1) | Yes | UE context | + +NOTE 1: If PLMN Criteria is not included in a RSD, the RSD shall be considered as valid in all PLMNs. + +Table 6.10.1-2: An example of RSDs with PLMN criteria + +| | Information name | Content | +|-----------|-------------------------|-------------------------------| +| | Traffic Descriptor | Service 1 | +| | Network Slice Selection | S-NSSAI 1 | +| URSP rule | RSD 1 | DNN Selection | +| | PLMN Criteria | HPLMN | +| | Network Slice Selection | S-NSSAI 1 | +| | RSD 2 | DNN Selection | +| | PLMN Criteria | VPLMN 1, VPLMN 2, etc. | + +NOTE: Before concluding this solution for normative work, alignment check with FS\_eUEPO shall be done in order to avoid any conflict with the conclusion of KI#1 in TR 23.700-85 [10]. Final decision on generic URSP enhancement for supporting LBO roaming case should be made within FS\_eUEPO study. + +## 6.10.2 Procedure + +The provision of the enhanced URSP with PLMN criteria re-uses the procedure in current specification TS 23.502 [9], or UE may be pre-configured the URSP. In order to determine PLMN criteria, H-PCF shall get the information related to PLMN(s) which the service deployed. The information can be either pre-configured in H-PCF or provisioned by AF. When UE triggers PDU Session selection or PDU Session establishment based on URSP, the UE takes the serving PLMN into consideration. + +## 6.10.3 Impacts on services, entities and interfaces + +PCF: + +- controls the UE to use different DNN+S-NSSAI in different PLMN by including PLMN Criteria in URSP RSDs. + +UE: + +- shall consider the serving PLMN when it determines whether to re-use or establish PDU Session, if PLMN Criteria is included in the selected Route Selection Descriptor. + +## 6.11 Solution 11 (KI#2): Exposure of Network Congestion + +### 6.11.0 General + +This solution corresponds to KI#2 on Fast and efficient network exposure improvements. + +Based on the use cases and scenarios in clause 5.2.2, the following network congestion information needs to be exposed to AF via local UPF/NEF: + +- QoS Notification Control. For GBR QoS Flow, RAN exposes "GBR can no longer be guaranteed" (or "GBR can be guaranteed"), as well as the reference to the matching Alternative QoS Profile to AF via local UPF/NEF. +- Network Congestion indication. For non-GBR QoS Flow, RAN exposes network congestion indication that indicates network congestion occurrence or recovery to AF via local UPF/NEF. +- Network Congestion Level. This indicates the degree of RAN congestion. RAN exposes network congestion level to AF via local UPF/NEF. + +NOTE 1: How to determine the network congestion level of a RAN node is up to RAN implementation. + +NOTE 2: This solution targets services with user plane packet transmission. + +### 6.11.1 Procedure + +Figure 6.11.1-1 shows the call flow for exposing network congestion information to AF via local UPF/NEF. + +![Sequence diagram illustrating Network Congestion Information Exposure to AF via local UPF/NEF. The diagram shows five steps: 0. PDU Session Establishment, 1. AF session with required QoS, 2. PCF initiates PDU session modification, 3. RAN determines Network Congestion Information, 4. UL packet including network congestion information, and 5. Local UPF exposes network congestion information to AF.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant L-PSA UPF + participant SMF + participant PCF + participant Local NEF/NEF + participant AF + + Note over UE, Local NEF/NEF: 0. PDU Session Establishment + Note over PCF, AF: 1. AF session with required QoS + Note over RAN, Local NEF/NEF: 2. PCF initiates PDU session modification + Note over RAN: 3. RAN determines Network Congestion Information + Note over RAN, L-PSA UPF: 4. UL packet including network congestion information + Note over L-PSA UPF, AF: 5. Local UPF exposes network congestion information to AF as described in step 4 of Figure 6.4.2.1-1 of TS 23.548 + +``` + +Sequence diagram illustrating Network Congestion Information Exposure to AF via local UPF/NEF. The diagram shows five steps: 0. PDU Session Establishment, 1. AF session with required QoS, 2. PCF initiates PDU session modification, 3. RAN determines Network Congestion Information, 4. UL packet including network congestion information, and 5. Local UPF exposes network congestion information to AF. + +**Figure 6.11.1-1: Network Congestion Information Exposure to AF via local UPF/NEF** + +The procedure is based on the Network exposure to Edge Application Server procedure in clause 6.4.2.1 of TS 23.548 [3]. + +0. The UE establishes a PDU Session as defined in clause 4.3.2.2.1 of TS 23.502 [9]. A local PSA UPF is selected for this PDU Session. +1. AF initiates setting up an AF session with required QoS procedure as defined in clause 6.4.2.1 of TS 23.548 [3]. + +The AF may subscribe to direct notification of network congestion for the service data flow to PCF. + +The AF may also send a report updating threshold to the PCF. When the difference between latest and previous reported network congestion information exceeds the report updating threshold, the local PSA exposes the latest network congestion information to the AF. + +If QoS notification control trigger is provisioned and the Alternative QoS parameter set(s) are authorized within the PCC rule, the PCF shall include the reference to the Alternative QoS requirement within each corresponding Alternative QoS parameter set. + +NOTE 1: The need for this optional Report updating threshold to the PSA UPF is to be decided during conclusion phase. + +2. The PCF makes policy information based on the AF request and/or local configuration and initiates PDU Session Modification procedure as described in clause 4.3.3.2 of TS 23.502 [9], steps 1b, 3b, 4-8b. The PCF sends policy information to SMF. The policy information may include a report updating threshold which is received from AF or determined by the PCF. + +If the SMF receives the indication of direct notification of network congestion, the SMF invokes Namf\_Communication\_N1N2MessageTransfer service of AMF, and AMF sends N2 PDU Session Request to + +RAN to indicate the RAN to expose network congestion information via local UPF. Based on local configuration, the SMF can further determine whether to enable direct notification of network congestion for this QoS Flow to NG-RAN. The SMF provisions the target local NEF or local AF address to the local PSA included in the PCC rule. + +If QoS notification control trigger is provisioned and the Alternative QoS parameter set(s) are authorized within the PCC rule, the SMF shall also provision the mapping between the reference to the Alternative QoS Profile and the reference to the Alternative QoS requirement to the local PSA. + +NOTE 2: With this enhancement, the PCF can be configured to only enable the Notification control over User Plane for the QoS Flow subject to edge computing. + +The SMF sends network congestion detection indication to UPF to enable network congestion notification detection. A report updating threshold may be informed to the UPF. + +The N2 SM information also includes measure frequency, report threshold. + +If there is no corresponding UL service data flow template for the service data flow, e.g. the service data flow has different QoS requirements for uplink and downlink, the SMF also indicates a different QoS Flow with corresponding UL service data flow template to the RAN for the reporting. The RAN exposes network congestion information via UL packets corresponding to the indicated QoS Flow. + +3. Based on local configuration and step 2, the RAN determines network congestion information when network congestion occurs. The network congestion information can be any information listed in clause 6.11.0. +4. In case the reporting condition is met, the RAN sends the network congestion information to the local PSA via the GTP-U header of corresponding UL packet. + +If the RAN is requested to report the network congestion information via a different QoS flow, the RAN sends the network congestion information via UL packets corresponding to the QoS Flow indicated by the SMF. + +If no UL packet can be used when report is needed, RAN generates a dummy UL packet for the report. + +As described in clause 6.11.0, the network congestion information includes QoS Notification Control information (for GBR QoS Flow) and network congestion level/indication (for non-GBR QoS Flow). + +NOTE 3: In order to avoid a too frequent report to the Local PSA, it is assumed that NG-RAN implementation can apply hysteresis (e.g. via a configurable update condition) before notifying a changed network congestion information to the local PSA. + +NOTE 4: RAN can repeat the network congestion information to the local PSA multiple times to avoid loss of the report. + +5. The local PSA exposes/updates the network congestion information to AF as described in step 4 of Figure 6.4.2.1-1 of TS 23.548 [3]. + +If a report updating threshold is informed by the SMF in step 2, local PSA updates the latest network congestion information to the AF when the difference between latest and previous reported network congestion information exceeds the report updating threshold. + +The local PSA sends the notification to the target local NEF or local AF address corresponding to the QoS flow. If the reference to the Alternative QoS Profile is also received within the notification, the local PSA shall also include the reference to the Alternative QoS requirement corresponding to the reference in the notification sent to the target local NEF or local AF address. + +NOTE 5: The AF logic after receiving the network congestion information is not in the scope of this study. + +## 6.11.2 Impacts on services, entities and interfaces + +AF: + +- subscribes direct notification of network congestion information from 5GC. + +PCF: + +- includes the reference to the Alternative QoS requirement within each corresponding Alternative QoS parameter set. + +SMF: + +- indicates RAN to expose network congestion information via local UPF; +- indicates a UL QoS Flow for RAN to be used to expose network congestion information when there is no UL QoS Flow of the service data flow; +- provisions the associated target local NEF or local AF address for this network congestion information reporting; +- provisions the mapping between the reference to the Alternative QoS Profile and the reference to the Alternative QoS requirement to the local UPF. + +UPF: + +- receives the mapping between the reference to the Alternative QoS Profile and the reference to the Alternative QoS requirement; +- exposes the reference to the Alternative QoS requirement to local NEF/AF. + +RAN: + +- supports exposing network congestion information via local UPF. + +## 6.12 Solution 12 (KI#2): Efficient exposure of RAN information + +### 6.12.1 Key Issue mapping + +The solution applies to KI#2: Fast and efficient network exposure improvements. + +### 6.12.2 Description + +In general, the application server support monitoring the data rate of the link between the client and server. The application server uses the monitored result to adjust service data throughput and the handling within the server. There are many factors impacting on the data rate of the link, e.g. the congestion of the transport network. The 5GS link is partial segment of the link between the client and server. Reporting network resource congestion of the 5GS can help the application server to estimate the bottle neck is in 5GS or other part between the server and the client, when the link data rate decreases outstandingly. + +Hence, it is proposed to expose the network congestion of the 5GS to the application server. + +In general, the bottleneck of the network congestion is the RAN congestion since the time-frequency resource is limited. However, the RAN does not support service-based interface and it is not efficient to expose RAN's congestion from RAN to AF via AMF-SMF-PCF-NEF. + +In order to support efficient exposure of RAN's congestion, it is proposed to considered to expose RAN's congestion via user plane, as shown in figure 6.12.2-1. + +![Diagram illustrating the exposure of RAN's congestion via the user plane. The diagram shows three stacked boxes: Consumer (AF,NEF) at the top, UPF in the middle, and RAN at the bottom. A double-headed arrow labeled 'QoS flow' connects the RAN and the UPF. A single-headed arrow labeled 'Nupf_EventExposure_notify' points from the UPF to the Consumer (AF,NEF).](133d09b09892b9fa5e84cfaa627e11a2_img.jpg) + +Diagram illustrating the exposure of RAN's congestion via the user plane. The diagram shows three stacked boxes: Consumer (AF,NEF) at the top, UPF in the middle, and RAN at the bottom. A double-headed arrow labeled 'QoS flow' connects the RAN and the UPF. A single-headed arrow labeled 'Nupf\_EventExposure\_notify' points from the UPF to the Consumer (AF,NEF). + +Figure 6.12.2-1: exposure RAN's congestion + +The solution is based on the existing Network Exposure functionality with the following enhancement: + +- The AF subscribes the network congestion with a UE address. +- The PCF generates a PCC rule for RAN to report RAN's congestion. +- The SMF generates a QoS flow's QoS profile for RAN report. +- The RAN reports RAN Congestion Start, RAN Congestion End, RAN's congestion level from the UL data in the QoS flow for RAN report. +- The UPF detects the RAN Congestion Start, RAN Congestion End, RAN's congestion level from the UL data in the QoS flow for RAN report. + +## 6.12.3 Procedures + +### 6.12.3.1 Subscribing information + +![Sequence diagram for Subscribing information procedure. Lifelines: UE, RAN, AMF, SMF, UPF, PCF, NEF, AF. The process involves AF sending a request to NEF, NEF authorizing and sending a request to PCF, PCF making a policy decision, and then a series of messages between SMF, AMF, RAN, and UE to set up resources and notifications.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant PCF + participant UPF + participant SMF + participant AMF + participant RAN + participant UE + + Note right of NEF: 2. Authorization + Note right of UPF: 4. Policy decision +PDU Set Mapping + + AF->>NEF: 1. Nnef_AFsessionWithQoS_Create request + NEF-->>NEF: 2. Authorization + NEF->>PCF: 3. Npcf_Policy Authorization_ Create request + PCF->>UPF: 4. Policy decision +PDU Set Mapping + PCF->>NEF: 5. Npcf_Policy Authorization_ Create response + NEF->>AF: 6. Nnef_AFsessionWithQoS_ Create response + PCF->>SMF: 7. Npcf_SMPolicyControl_ UpdateNotify request + SMF->>PCF: 8. Npcf_SMPolicyControl_ UpdateNotify response + SMF->>UPF: 9. N4 Session Modification Request + UPF->>SMF: 10. N4 Session Modification Response + AMF->>SMF: 11. Namf_Communication_N1N2MessageTransfer + AMF->>RAN: 12. N2 message + UE->>RAN: 13. resource setup + RAN->>AMF: 14. N2 message + AMF->>SMF: 15. Nsmf_PDUSession_ UpdateSMContext Request + SMF->>AMF: 16. Nsmf_PDUSession_ UpdateSMContext Response + SMF->>UPF: 17. N4 Session Modification Request + UPF->>SMF: 18. N4 Session Modification Response + +``` + +Sequence diagram for Subscribing information procedure. Lifelines: UE, RAN, AMF, SMF, UPF, PCF, NEF, AF. The process involves AF sending a request to NEF, NEF authorizing and sending a request to PCF, PCF making a policy decision, and then a series of messages between SMF, AMF, RAN, and UE to set up resources and notifications. + +Figure 6.12.3.1-1: Subscribing Normal Data Transmission Interruption event and Date Rate + +1. The AF subscribes the Network Congestion (e.g. RAN congestion) by sending Nnef\_EventExposure\_Subscribe request (UE address, event ID(s)). +2. The NEF authorizes the AF request. +3. The NEF interacts with the PCF by triggering a Npcf\_PolicyAuthorization\_Subscribe request to the Network Congestion (e.g. RAN congestion). +4. Upon reception of the subscribe request of Network Congestion for a UE address, the PCF generates a QoS rule for RAN to report RAN's congestion. The PCC rule includes an indication that the PCC rule is used for RAN report information. + +The PCF also generates a QoS monitoring policy for network congestion measurement. + +5. The PCF responds to the NEF a Npcf\_Policy Authorization\_Create response. +6. The NEF sends a Nnef\_AFsessionWithQoS\_Create response message to the AF. +7. The PCF initiates SM Policy Association Modification Request (PCC rule) to the SMF. + +The SMF maps a QoS flow for the PCC rule from the PCF. The QoS flow's QoS profile includes the indication that the QoS flow is used for RAN report information. + +The SMF generates the QoS Monitoring configuration for UPF: RAN congestion detection indication. + +The SMF generates the QoS Monitoring configuration for RAN: RAN congestion measurement indication, measure frequency, report threshold. + +8. The SMF replies SM Policy Association Modification Response to the PCF. +9. The SMF initiates N4 Session Modification Request (QoS Monitoring configuration, QoS rule) to the UPF. + +Upon reception of QoS Monitoring configuration, the UPF enables the RAN's congestion detection and report. + +10. The UPF(s) respond to the SMF. + +11. For SMF requested modification, the SMF invokes Namf\_Communication\_N1N2MessageTransfer ([N2 SM information] (PDU Session ID, QFI(s), QoS Profile(s), QoS Monitoring configuration), N1 SM container)). + +12. The AMF may send N2 ([N2 SM information received from SMF], NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command))) Message to the (R)AN. + +Upon reception of QoS flow's QoS profile and the indication that the QoS flow is used for RAN report information, the RAN skips to map DRB for the QoS flow and makes the QoS flow terminated between the RAN and the UPF. + +Upon reception of QoS Monitoring configuration, the RAN enables the RAN congestion measurement and report. + +14. The (R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU Session Ack Message to the AMF. + +- 15-16. The AMF forwards the N2 SM information and the User location Information received from the AN to the SMF via Nsmf\_PDUSession\_UpdateSMContext service operation. The SMF replies with a Nsmf\_PDUSession\_UpdateSMContext Response. + +- 17-18. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF. + +### 6.12.3.2 Information report + +![Sequence diagram illustrating the Normal Data Transmission Interruption event and measured Data Rate. The diagram shows interactions between RAN, AMF, UPF, PCF, NEF, and AF. The sequence starts with '1. Congestion Starts' in the RAN, followed by '2. UL Data(Congestion Start, Congestion level)' from RAN to UPF. The UPF then sends '3. Nupf_EventExposure_Notify' to the NEF, which in turn sends '4. Nnef_Nnef_EventExposure_Notify' to the AF. Later, '5. Congestion Ends' is indicated in the RAN, followed by '6. UL Data(Congestion End)' from RAN to UPF. The UPF sends '7. Nupf_EventExposure_Notify' to the NEF, which sends '8. Nnef_Nnef_EventExposure_Notify' to the AF.](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +``` + +sequenceDiagram + participant RAN + participant AMF + participant UPF + participant PCF + participant NEF + participant AF + + Note left of RAN: 1. Congestion Starts + RAN->>UPF: 2. UL Data(Congestion Start, Congestion level) + UPF->>NEF: 3. Nupf_EventExposure_Notify + NEF->>AF: 4. Nnef_Nnef_EventExposure_Notify + Note left of RAN: 5. Congestion Ends + RAN->>UPF: 6. UL Data(Congestion End) + UPF->>NEF: 7. Nupf_EventExposure_Notify + NEF->>AF: 8. Nnef_Nnef_EventExposure_Notify + +``` + +Sequence diagram illustrating the Normal Data Transmission Interruption event and measured Data Rate. The diagram shows interactions between RAN, AMF, UPF, PCF, NEF, and AF. The sequence starts with '1. Congestion Starts' in the RAN, followed by '2. UL Data(Congestion Start, Congestion level)' from RAN to UPF. The UPF then sends '3. Nupf\_EventExposure\_Notify' to the NEF, which in turn sends '4. Nnef\_Nnef\_EventExposure\_Notify' to the AF. Later, '5. Congestion Ends' is indicated in the RAN, followed by '6. UL Data(Congestion End)' from RAN to UPF. The UPF sends '7. Nupf\_EventExposure\_Notify' to the NEF, which sends '8. Nnef\_Nnef\_EventExposure\_Notify' to the AF. + +**Figure 6.12.3.2-1: Normal Data Transmission Interruption event and measured Data Rate** + +- 1&2. When the RAN congestion starts or congestion level reaches the report threshold, the NG-RAN indicates the RAN Congestion Start and RAN congestion level in the GTP-U header of the UL data. +3. Upon detection of the RAN Congestion Start and RAN congestion level from the UL data, the UPF triggers the Nupf\_EventExposure\_Notify message to report the RAN Congestion Start and RAN congestion level. +4. The NEF sends a Nnef\_Nnef\_EventExposure\_Notify (RAN Congestion Start and RAN congestion level) message to the AF. +- 5&6. When the RAN congestion ends, the NG-RAN indicates the RAN Congestion End in the GTP-U header of the UL data. +7. Upon detection of the RAN Congestion End from the UL data, the UPF triggers the Nupf\_EventExposure\_Notify message to report the RAN Congestion End. +8. The NEF sends a Nnef\_Nnef\_EventExposure\_Notify (RAN Congestion End) to the AF. + +### 6.12.4 Impacts on services, entities and interfaces + +#### AF: + +- subscribes network congestion information from 5GC. + +#### PCF: + +- generates a PCC rule for RAN to report RAN's congestion. The PCC rule includes an indication that the QoS rule is used for RAN report information; +- generates a QoS monitoring policy for RAN congestion information measurement. + +#### SMF: + +- indicates RAN to expose RAN congestion information via UPF; +- sets up a QoS flow between the RAN and UPF for RAN to report RAN congestion information. + +#### RAN: + +- sets up a QoS flow between the RAN and UPF for RAN to report RAN congestion information; +- detects and reports RAN congestion information to UPF. + +#### UPF: + +- detects and exposes RAN congestion information to AF/NEF. + +## 6.13 Solution 13 (KI#2): Fast and efficient network exposure improvements + +### 6.13.1 Introduction + +This solution addresses the KI#2: Fast and efficient network exposure improvements. This solution reuses mechanism defined to establish QoS Monitoring as specified in clause 5.33.3 of TS 23.501 [2], clause 4.3.3 of TS 23.502 [9] and support of network exposure with low latency to local AF as specified in clause 6.4.2 of TS 23.548 [3]. + +The solution is based on following principles: + +- The local AF subscribes the low latency exposure of cell ID, etc. from the PCF via a local NEF. +- NG-RAN provides information such as cell ID(s) as requested by the SMF. +- UPF exposes received information as defined in clause 5.2.26 of TS 23.502 [9] and further enhanced in FS\_UPEAS to local NEF/AF. +- The local AF may use received information about the cell(s) currently serving a UE to retrieve current and predicted UE and cell radio conditions from RAN. Such information may be used by local AF and applications, for instance, to trigger video codec rate adaption and prevent user experience degradation. + +### 6.13.2 Functional Description + +This solution addresses KI#2 and the following principles are used: + +1. The local AF subscribes using Nnef\_AFSessionWithQoS / Npcf\_PolicyAuthorization\_Subscribe service the low latency exposure of cell ID(s), etc. from the PCF via a local NEF as defined in clause 6.4.2.1 of TS 23.548 [3]. The local AF may also subscribe direct event notification from the UPF to the local AF as defined in clause 6.4.2.1 of TS 23.548 [3]. +2. PCF sends this subscription to SMF as defined in clause 6.4.2.1 of TS 23.548 [3], together with requested information. +3. The SMF configures NG-RAN via AMF, and the UPF over N4 for the UPF, with the requested to notify AF. +4. NG-RAN node sends the requested information e.g. cell ID(s) in NG-RAN UL (Uplink) over GTP-u to UPF. Requested information may be sent, e.g. using UL PDU Session Information as defined in TS 38.415 [14] for QoS Monitoring information. + +NOTE: AF may use e.g. Cell ID to obtain additional information e.g. using APIs defined by ETSI MEC, etc. but these are outside the scope of this solution. + +5. This SMF provided configuration is transferred to the new/target NG-RAN node when the UE has been handed over to a the new/target NG-RAN node. +6. If the serving cell Id(s) has changed (and upon receiving the SMF request), the NG-RAN provides the latest/new serving cell Id(s). +7. The UPF exposes received information to local NEF/AF as defined in clause 5.2.26 of TS 23.502 [9] and further enhanced in FS\_UPEAS. + +### 6.13.3 Procedures + +This procedure is based on clause 6.4.2.1 of TS 23.548 [3] for Network Exposure to Edge Application Server and further enhanced in FS\_UPEAS as follows: + +![Sequence diagram showing reporting information by the NG-RAN to local AF. The diagram involves UE, RAN, AMF, L-PSA UPF, SMF, PCF, Local NEF/NEF, AF, and a dashed box for 'new AF'. The sequence starts with '0. PDU Session establishment' across UE, RAN, AMF, L-PSA UPF, and SMF. Then, '1a. AF Session (cell ID(s), other info indication)' is sent from AF to PCF. '1b. Npcf_PolicyAuthorization_Subscribe' is sent from PCF to AF. '2a. PCC rules in Npcf_SMSPolicyControl_Create / Npcf_SMSPolicyControl_UpdateNotify' is sent from PCF to SMF. '2b. N4 Session Modification' is sent from SMF to L-PSA UPF. '2c. PDU Session Resource Setup / Modify' is sent from SMF to RAN. '3. UL GTP-u packet(s) including requested information' is sent from RAN to L-PSA UPF. '4a. Nupf_EventExposure_Notify' is sent from L-PSA UPF to Local NEF/NEF. '4b. Nnef_EventExposure_Notify' is sent from Local NEF/NEF to AF. The 'new AF' box is shown as a dashed box on the right, indicating a potential future entity.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Sequence diagram showing reporting information by the NG-RAN to local AF. The diagram involves UE, RAN, AMF, L-PSA UPF, SMF, PCF, Local NEF/NEF, AF, and a dashed box for 'new AF'. The sequence starts with '0. PDU Session establishment' across UE, RAN, AMF, L-PSA UPF, and SMF. Then, '1a. AF Session (cell ID(s), other info indication)' is sent from AF to PCF. '1b. Npcf\_PolicyAuthorization\_Subscribe' is sent from PCF to AF. '2a. PCC rules in Npcf\_SMSPolicyControl\_Create / Npcf\_SMSPolicyControl\_UpdateNotify' is sent from PCF to SMF. '2b. N4 Session Modification' is sent from SMF to L-PSA UPF. '2c. PDU Session Resource Setup / Modify' is sent from SMF to RAN. '3. UL GTP-u packet(s) including requested information' is sent from RAN to L-PSA UPF. '4a. Nupf\_EventExposure\_Notify' is sent from L-PSA UPF to Local NEF/NEF. '4b. Nnef\_EventExposure\_Notify' is sent from Local NEF/NEF to AF. The 'new AF' box is shown as a dashed box on the right, indicating a potential future entity. + +**Figure 6.13.3-1: Reporting information by the NG-RAN to local AF.** + +0. The UE establishes a PDU Session as defined in clause 4.3.2.2.1 of TS 23.502 [9]. 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 [9]. + +In the request, the AF may subscribe to direct notification of requested information such as Cell ID(s), for the service data flow to PCF possibly via Local NEF or NEF. + +The AF may also first initiate an AF Session with PCF and later subscribe to direct notification of requested information to PCF by invoking Npcf\_PolicyAuthorization\_Subscribe service operation. + +The local AF or NEF may discover a local NEF as specified in step 1 in clause 6.4.2.1 of TS 23.548 [3]. + +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 [9], steps 1b, 3b, 4-8b. + +If the direct notification is subscribed, 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. + +If the SMF receives (2a) the indication of direct event notification from the PCF and the SMF determines that the L-PSA UPF supports such reporting, the SMF sends (2b) requested information indication and associates the indication with the target local NEF or local AF address to the L-PSA UPF via N4 rules. + +The SMF sends (2c) via N2 to NG-RAN within a PDU Session resource Create/Modify (defined in TS 38.413 [15]) a request to send to the UPF requested information that contains e.g. the cell(s) currently serving a PDU Session, etc. + +3. The L-PSA UPF obtains requested information sent in GTP-u by NG-RAN. + +If the SMF had beforehand requested that the NG-RAN sends an indication and the PDU Session resources have been released in the NG-RAN, the NG-RAN needs to send to the UPF an indication that the cell(s) currently serving the PDU Session and /or the UE identity as handled by the NG-RAN are no longer valid. + +If there is no UL traffic, the NG-RAN may send a GTP-u packet with no user plane traffic (dummy UL packet). + +The NG-RAN may send updated serving cell Id(s) and/or UE identity as handled by the NG-RAN in multiple UL packet sent over 5GS N3 interface (in order to not lose the information if some UL traffic was discarded between the NG-RAN and the UPF responsible of the reporting to the EC AF). + +4. The L-PSA UPF sends the notification related requested information over Nupf\_EventExposure\_Notify service operation as specified in step 4 (a, b) in clause 6.4.2.1 of TS 23.548 [3]. + +5-8. may follow as specified in clause 6.4.2.1 of TS 23.548 [3]. + +## 6.13.4 Impacts on services, entities and interfaces + +Proposed information exposure impacts the same entities and interfaces as QoS monitoring defined in Rel-16. + +NG-RAN: + +- should support exposing of requested information such as Cell ID(s) in GTP-u packets. + +UPF: + +- should support exposing of requested information such as Cell ID(s) in GTP-u packets; +- should support exposing requested information which includes cell ID(s) in Nupf\_Event\_Exposure\_Notify. + +NEF, PCF, SMF: + +- should support indication of RAN assistance information in Nnef\_AFSessionWithQoS / Npcf\_PolicyAuthorization\_Subscribe. + +SMF and UPF: + +- N4 should support indication of requested information. + +## 6.14 Solution 14 (KI#4): Group Management + +### 6.14.1 Introduction + +This solution addresses the Key Issue #4, and in particular how to define a collection of UEs forming a dynamic ad-hoc group. This dynamic ad-hoc group may be then used to identify the users that should use the same EAS and/or same local part of DN and/or same DNAI. + +This solution makes the following assumptions: + +- AF determines the identities of the UEs that should be part of the collection and creates an ad-hoc group for this collection to the 5GC. The AF includes an External Group ID in the group creation request. The AF can add or remove users in the group in dynamic manner. 5GC stores the group members with associated Internal and External Group IDs. +- The AF uses the Traffic Influence and EAS Deployment services to submit edge service related data for the given ad-hoc group as identified by the External Group ID. No impact to Rel-17 is foreseen. +- The 5GC is responsible to determine and select a common local part of the DN for the group members. This step is not in the scope of this solution proposal. + +### 6.14.2 Functional Description + +The solution is based on the following principles: + +- In this solution, the AF is responsible to create and maintain the ad-hoc group data in 5GC. NEF provides a generic Group Management service for the AF to create, modify and delete ad-hoc groups in 5GC. Generic here means that the group data does not contain any service specific data, but instead any service data can be associated with the corresponding group identifier. This solution proposal describes how the traffic influence + +service data and EAS Deployment Information data can be associated with the group data, but the same principle could be used with any other service data. + +- Upon receiving a request to include a user into a group (i.e. when the group is created or a new user is added to the group), the UDM ensures that the group data and individual subscription data are aligned; i.e. the UDM updates the individual user subscription data for the group member to contain the Internal Group ID of the group. In similar manner, when the AF requests a user to be removed from a group, the UDM removes the corresponding Internal Group ID from the individual user subscription data. A user may belong to more than one group. +- Nnef\_TrafficInfluence service as specified in Rel-17 is used to store the DNN/S-NSSAI and the Internal Group ID. The service data may contain an "Indication of traffic correlation" parameter as defined in clause 5.6.7 in TS 23.501 [2] to indicate that a common local part of DN should be selected. The service data is applicable for all members of the given group using the given DNN/S-NSSAI. +- Nnef\_EASDeployment service as specified in clause 6.2.3.4 in TS 23.548 [3] is used to store the EAS Deployment Information in the NEF and UDR. The SMF retrieves the EAS Deployment Information from the NEF and configures the DNS handling rules to EASDF correspondingly. EAS Deployment Information can contain an Internal Group ID as described in Table 6.2.3.4-1 in TS 23.548 [3]. The service data is applicable for all members of the given group using the given DNN/S-NSSAI. +- A single DNN/S-NSSAI may be used by multiple ad-hoc groups. In this case the groups may be controlled by the same or different AFs, each submitting a different traffic influence service data containing the same DNN/S-NSSAI. + +NOTE: The solution assumes that the principle in Rel-17 holds, where multiple AFs that manage different services can submit traffic influence data for the same user with the same DNN/S-NSSAI. + +The figure 6.14.2-1 illustrates the overall structure of the Group management data, Traffic Influence data, and EAS Deployment Information data. + +![Diagram illustrating the overall structure of the Group management data and Traffic Influence data. The NEF provides three services (Group management service, Traffic Influence service, and EAS Deployment service) to the UDM and UDR. The UDM ensures consistency between the data stored in the UDR and the data provided by the NEF. The data is categorized into four types: Group data, User subs data, Traffic Influence data, and EAS Deployment Information data.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +The diagram shows the flow of data from the NEF to the UDM and UDR. The NEF provides three services: Group management service, Traffic Influence service, and EAS Deployment service. The UDM and UDR are connected to the NEF. The UDM ensures consistency between the data stored in the UDR and the data provided by the NEF. The data is categorized into four types: + +- Group data:** + - ext-group-id + - int-group-id + - list of SUPIs +- User subs data:** + - SUPI + - GPSI(s) + - int-group-id(s) +- Traffic Influence data:** + - int-group-id + - DNN/S-NSSAI + - service data +- EAS Deployment Information data:** + - int-group-id + - DNN/S-NSSAI + - service data + +UDM ensures consistency + +Diagram illustrating the overall structure of the Group management data and Traffic Influence data. The NEF provides three services (Group management service, Traffic Influence service, and EAS Deployment service) to the UDM and UDR. The UDM ensures consistency between the data stored in the UDR and the data provided by the NEF. The data is categorized into four types: Group data, User subs data, Traffic Influence data, and EAS Deployment Information data. + +**Figure 6.14.2-1: Overall structure of the Group management data and Traffic Influence data** + +The NEF provides three distinct services: 1) generic Group Management service, 2) Traffic Influence service, and 3) EAS Deployment service. + +For the Group Management service, either a new service needs to be specified, or the existing Nnef\_ParameterProvision service is used as specified in clause 5.29.2 in TS 23.501 [2]. In the latter case, the Nnef\_ParameterProvision service shall be generalized so that it can be used also for groups that are not specific for 5G VN group communication service. This means that the group data should not be required to contain any service specific data, as the group data can be referenced from any service. + +As specified in clause 5.29.2 in TS 23.501 [2], the UDM ensures that the group data and user subscription data are aligned, i.e. the user who is listed as a member in the group data should have the same group identity in the user subscription data. + +For the Traffic Influence and EAS deployment services, the existing procedures are used to store the traffic influence data and EAS Deployment Information data into UDR. The traffic influence data and EAS Deployment Information data can contain a DNN/S-NSSAI and Internal Group ID that the service data is applicable for. + +The figure 6.14.2-2 illustrates how the UDMs can align the group data and individual subscription data in a case where the group data and individual user subscription data are served by different UDMs. + +![Sequence diagram illustrating the interaction between UDM-1, UDR-1, UDR-2, and UDM-2 to align group and user subscription data.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` + +sequenceDiagram + participant AF + participant UDM1 as UDM-1 + participant UDR1 as UDR-1 + participant UDR2 as UDR-2 + participant UDM2 as UDM-2 + Note right of UDR1: Group data: +- ext-group-id +- int-group-id +- list of SUPIs + Note right of UDR2: User subs data: +- SUPI +- GPSI(s) +- int-group-id(s) + + AF->>UDM1: Group create/update request + UDM1->>UDR1: Nudr_DM_Create/Update request + UDM1->>UDR2: Nudr_DM_Create/Update request + UDM2->>UDR2: Subscription data via OAM + UDM2->>UDR2: Nudr_DM_Create/Update request + UDR2->>UDM1: Nudr_DM_Notify request + +``` + +The diagram shows the following sequence of events: + +- An external request (Group create/update request) is received by UDM-1. +- UDM-1 sends a `Nudr_DM_Create/Update request` to UDR-1 to store group data. +- UDM-1 also sends a `Nudr_DM_Create/Update request` to UDR-2 to update user subscription data. +- UDM-2 receives `Subscription data via OAM` and sends a `Nudr_DM_Create/Update request` to UDR-2. +- UDR-2 sends a `Nudr_DM_Notify request` back to UDM-1 to indicate a data change. + +Below UDR-1, a box labeled **Group data:** contains: + + +- ext-group-id +- int-group-id +- list of SUPIs + +Below UDR-2, a box labeled **User subs data:** contains: + + +- SUPI +- GPSI(s) +- int-group-id(s) + +Sequence diagram illustrating the interaction between UDM-1, UDR-1, UDR-2, and UDM-2 to align group and user subscription data. + +**Figure 6.14.2-2: Different UDMs serving the user(s) and group** + +AF invokes a group creation or update request to the NEF (not shown in the figure). The NEF discovers the UDM-1 based on the External Group ID. The UDM-1 receives the group creation request from the NEF. UDM-1 discovers the UDR based on External Group ID and stores the group data into UDR-1. UDM-1 uses the SUPI to discover the UDR for each member (UDR-2). UDM-1 updates the user subscription data for the member's SUPI and adds the Internal Group ID of the group to the user subscription data. If the user subscription data is updated via OAM, the UDM-2 updates the user subscription data in UDR-2 and UDR-2 notifies the UDM-1 for the data change. + +### 6.14.3 Procedures + +Figure 6.14.3-1 describes an overview of the procedure to create an ad-hoc group that is used to determine the collection of users that should have a common local part of DN. + +![Sequence diagram showing the creation of a group and using it for selecting the local part of DN. The diagram involves six network functions: AF, NEF, UDM, UDR, PCF, and SMF. It is divided into four numbered sections: 1. Group Management, 2. Edge service management, 3. PDU Session establishment, and 4. Selecting the common local part of DN. Section 1 details the AF using NEF to create an ad-hoc group, NEF using UDM to create the group, and UDM storing data in UDR. Section 2 details NEF using Nnef_TrafficInfluence and Nnef_EASDeployment services to submit traffic influence and EAS Deployment Information data to the UDR. Section 3 details SMF retrieving user subscription data from UDM, informing PCF, receiving traffic influence data from UDR, and receiving EAS Deployment Information data from NEF. Section 4 details 5GC determining and selecting a common local part of the DN for the users of the group.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +AF NEF UDM UDR PCF SMF + +**1. Group Management:** + +AF uses a generic group management service provided by NEF to create an ad-hoc group. NEF uses an UDM service to create the group in UDM. UDM may store the group data (External Group ID, Internal Group ID and list of SUPIs) into UDR. UDM ensures that the individual subscription data of the member UEs are updated with the Internal Group ID of the group. + +**2. Edge service management:** + +NEF uses the Nnef\_TrafficInfluence and Nnef\_EASDeployment services to submit traffic influence service and EAS Deployment Information data to the NEF. NEF stores the service data to the UDR. The service data contains a DNN/S-NSSAI and the Internal Group ID. PCF(s) that have subscribed for the UDR data change for traffic influence data are notified. (No impact to Release 17 procedures) + +**3. PDU Session establishment:** + +SMF retrieves the user subscription data from the UDM and determines the Internal Group ID(s) of the user. SMF informs the PCF with the Internal Group ID(s) of the user. PCF receives the traffic influence data from the UDR for the given DNN/S-NSSAI and Internal Group ID(s). SMF receives the EAS Deployment Information data from NEF for the given DNN/S-NSSAI and Internal Group ID(s). (Out of scope of this solution) + +**4. Selecting the common local part of DN:** + +5GC determines and selects a common local part of the DN for the users of the group accessing the given DNN/S-NSSAI. (Out of scope of this solution) + +Sequence diagram showing the creation of a group and using it for selecting the local part of DN. The diagram involves six network functions: AF, NEF, UDM, UDR, PCF, and SMF. It is divided into four numbered sections: 1. Group Management, 2. Edge service management, 3. PDU Session establishment, and 4. Selecting the common local part of DN. Section 1 details the AF using NEF to create an ad-hoc group, NEF using UDM to create the group, and UDM storing data in UDR. Section 2 details NEF using Nnef\_TrafficInfluence and Nnef\_EASDeployment services to submit traffic influence and EAS Deployment Information data to the UDR. Section 3 details SMF retrieving user subscription data from UDM, informing PCF, receiving traffic influence data from UDR, and receiving EAS Deployment Information data from NEF. Section 4 details 5GC determining and selecting a common local part of the DN for the users of the group. + +**Figure 6.14.3-1: Creation of a group and using it for selecting the local part of DN** + +**1. Group Management:** + +The AF invokes a group creation request to the NEF. The group creation request contains an External Group ID and list of GPSIs that are members in the group. NEF uses an UDM service to create the group. The group data contains the members (SUPIs) and External Group ID. The UDM discovers an UDR based on the External Group ID and stores the group data into UDR. The UDR assigns an Internal Group ID for the group and stores it to the group data. + +Upon receiving a request to include a user into a group, the UDM updates the individual user subscription data for the group members in the corresponding UDR(s) to contain the Internal Group ID of the group. + +**NOTE:** A single UDR should serve the group data for a particular External Group ID. How the UDR ensures that the Internal Group ID is unique is left up to implementation, as long as the format defined in clause 19.9 in TS 23.003 [16] is followed. + +**2. Edge service management (no impact):** + +AF uses the Nnef\_TrafficInfluence service as specified in clause 4.3.6.2 in TS 23.502 [9] to influence SMF routing decisions for User Plane traffic of PDU Sessions. AF uses the Nnef\_EASDeployment service as specified in clause 6.2.3.4 in TS 23.548 [3]. The AF may include an External Group ID to the service + +requests. If the AF requires that the same local part of DN is used for the group members when they access the given DNN/S-NSSAI, the AF includes the "Indication of traffic correlation" parameter to the Nnef\_TrafficInfluence service request. + +The NEF uses the Nudm\_SDM\_Get (Group Identifier Translation, External Group ID) service to resolve the External Group ID to Internal Group ID, as specified in Rel-17. The NEF stores the TrafficInfluence service information and EAS Deployment Information in the UDR. The service data contains the DNN/S-NSSAI and Internal Group ID as specified in Rel-17. The PCF(s) that have subscribed for the Traffic Influence data for the matching DNN/S-NSSAI and Internal Group ID receive a notification from the UDR. + +3. PDU Session establishment (not in the scope of this solution): + +Upon PDU Session establishment, the SMF retrieves the user subscription data from the UDM. The user subscription data may contain one or more Internal Group IDs. The SMF passes the DNN/S-NSSAI and Internal Group ID(s) to the PCF as specified in clause 4.16.4 in TS 23.502 [9]. If the PCF does not have the traffic influence service data for the given DNN/S-NSSAI and Internal Group ID, the PCF retrieves it from the UDR. + +The SMF retrieves the EAS Deployment Information for the given DNN/S-NSSAI and Internal Group ID(s) from the NEF as described in clause 6.2.3.4 in TS 23.548 [3]. + +4. Selecting the common local part of DN (not in the scope of this solution): + +If the traffic influence service data contains the "Indication of traffic correlation" parameter, 5GC determines and selects a common local part of the DN for all PDU Sessions that use the given DNN/S-NSSAI where the user is a member in the given group. + +## 6.14.4 Impacts on services, entities and interfaces + +Assuming that the existing Nnef\_ParameterProvision service is used as specified in clause 5.29.2 in TS 23.501 [2] to provide a generic Group Management service, the impacts are limited to the generalization of the Nnef\_ParameterProvision service as described below. + +NEF: + +- Nnef\_ParameterProvision service is enhanced to remove a requirement to provide any service specific data in group creation. At least DNN and S-NSSAI are currently mandatory parameters in the Nnef\_ParameterProvision\_Create service operation when a 5G VN group is created. + +UDM: + +- Nudm\_ParameterProvision service is enhanced to remove a requirement to provide any service specific data in group creation. At least DNN and S-NSSAI are currently mandatory parameters in the Nudm\_ParameterProvision\_Create service operation when a 5G VN group is created. + +UDR: + +- Nudr\_DataManagement service is used to manage the group data in the UDR. The service is enhanced to remove a requirement to provide any service specific data when the group data is stored in UDR. At least DNN and S-NSSAI are currently mandatory parameters in the Group Data Subset in subscription dataset for a 5G VN group. The UDR stores the Internal/External Group IDs and the member list (list of SUPIs). + +## 6.15 Solution 15 (KI#4): Selection of common DNAI + +### 6.15.1 Introduction + +This solution aims to address the KI#4 created for WT#6 related to the influence on UPF and EAS (re)location for a collection of UEs in scenarios when the UEs should use the same EAS and are not members of a pre-defined group. + +As addressed under the key issue description, the UPF selection and relocation, and deciding on a common local part of DN are the focus of this solution. In practice, an optimal common local part of DN would be needed to make the service experience best for all UEs in the group. + +How to define a collection of UEs forming a dynamic ad-hoc group is not in the scope of this solution proposal. + +## 6.15.2 Functional Description + +The solution is based on the following principles: + +- Session Collection Management Function (SCMF) entity is introduced to determine the location of the common local part of DN (L-DN) and used for common DNAI selection. +- Individual SMFs one by one add more sessions to the collection of PDU Sessions that is managed by the SCMF, and SCMF selects the common DNAI for this collection of PDU Sessions. SCMF can re-consider the common DNAI whenever a new PDU Session "joins" to an existing collection of PDU Sessions. +- The interface between SMF and SCMF can be based on subscribe/notify model, so even if the SCMF fails to select the common DNAI in some error case, the individual SMFs can proceed as with regular UPF/DNAI selection as a fallback. +- SCMF can make the decision on the common DNAI based on the information it receives from individual SMFs. Then, each SMF selects the location of the UPF based on the common DNAI and relocates the UPF on PDU Session basis. +- For selecting the common DNAI, SCMF may further use Analytics services from NWDAF for determining service experience between the gNB and candidate UPFs. +- Nnef\_TrafficInfluence service as specified in TS 23.501 [2] is used to store the DNN/S-NSSAI, Internal Group ID, and a list of DNAIs. The traffic influence data may contain an "Indication of traffic correlation" parameter as defined in clause 5.6.7 in TS 23.501 [2] to indicate that a common DNAI should be selected. PCF retrieves the traffic influence data from UDR and constructs the PCC Rules accordingly. No impact to Nnef\_TrafficInfluence service is foreseen. +- Nnef\_EASDeployment service as specified in clause 6.2.3.4 in TS 23.548 [3] is used to store the EAS Deployment Information in the NEF and UDR. The SMF retrieves the EAS Deployment Information from the NEF and configures the DNS handling rules to EASDF correspondingly. EAS Deployment Information can contain an Internal Group ID as described in Table 6.2.3.4-1 in TS 23.548 [3]. No impact to Nnef\_EASDeployment service is foreseen. +- The solution proposes to enhance the PCC Rules by adding a new identifier "influence-id", which is associated with the list of DNAIs in the PCC Rules. UDR assigns the "influence-id" for each entry in the traffic influence data in the UDR when the entry is created as specified in Rel-17. In this solution, the PCF retrieves the "influence-id" from the UDR as part of the traffic influence data and includes it to the PCC Rules. This is necessary when the same DNN/S-NSSAI is used by multiple ad-hoc groups (Internal Group IDs), where each group has different traffic influence service data (e.g. list of DNAIs) containing the same DNN/S-NSSAI. In this case the PCC Rules will contain multiple lists of DNAIs and the "influence-id" is used to determine the lists of DNAIs in different PDU Sessions that are related to each other. + +## 6.15.3 Procedures + +### 6.15.3.1 General + +The overall procedure is described in figure 6.15.3.1-1. + +![Figure 6.15.3.1-1: Overall procedure diagram showing the interaction between AF, NEF, UDM, UDR, PCF, and SMF. The diagram is divided into three main steps: 1. Group Management and Edge service management (out of scope), 2. PDU Session establishment, and 3. Selecting the common local part of DN. Step 2 details that SMF retrieves user subscription data from UDM, informs PCF of Internal Group ID(s), PCF receives traffic influence data from UDR, and SMF receives EAS Deployment Information from NEF. Step 3 details that 5GC determines and selects a common local part of the DN for the users of the group accessing the given DNN/S-NSSAI.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +The diagram illustrates the overall procedure for selecting the common local part of the DN. It shows the following components and steps: + +- Components:** AF, NEF, UDM, UDR, PCF, SMF. +- Step 1: Group Management and Edge service management (out of scope of this solution)** +- Step 2: PDU Session establishment:** + - SMF retrieves the user subscription data from the UDM and determines the Internal Group ID(s) of the user. + - SMF informs the PCF with the Internal Group ID(s) of the user. + - PCF receives the traffic influence data from the UDR for the given DNN/S-NSSAI and Internal Group ID(s). + - SMF receives the EAS Deployment Information data from NEF for the given DNN/S-NSSAI and Internal Group ID(s). +- Step 3: Selecting the common local part of DN:** + - 5GC determines and selects a common local part of the DN for the users of the group accessing the given DNN/S-NSSAI. + +Figure 6.15.3.1-1: Overall procedure diagram showing the interaction between AF, NEF, UDM, UDR, PCF, and SMF. The diagram is divided into three main steps: 1. Group Management and Edge service management (out of scope), 2. PDU Session establishment, and 3. Selecting the common local part of DN. Step 2 details that SMF retrieves user subscription data from UDM, informs PCF of Internal Group ID(s), PCF receives traffic influence data from UDR, and SMF receives EAS Deployment Information from NEF. Step 3 details that 5GC determines and selects a common local part of the DN for the users of the group accessing the given DNN/S-NSSAI. + +**Figure 6.15.3.1-1: Overall procedure** + +1. Prerequisite: AF has created an ad-hoc group in 5GC. AF submits the traffic influence data and EAS Deployment Information data for the group to 5GC. This step is out of scope of this solution. +2. Upon PDU Session establishment, the SMF retrieves the user subscription data from the UDM. The user subscription data may contain one or more Internal Group IDs. The SMF passes the DNN/S-NSSAI and Internal Group ID(s) to the PCF as specified in clause 4.16.4 in TS 23.502 [9]. If the PCF does not have the traffic influence service data for the given DNN/S-NSSAI and Internal Group ID(s), the PCF retrieves the data from the UDR. The PCF creates or updates the PCC Rules to the SMF. + +The PCC Rules contain a list of DNAIs associated with the "Indication of traffic correlation" and with "influence-id". The PCF retrieves the "influence-id" from the UDR, thus the value of "influence-id" remains the same across all PDU Sessions that use the same traffic influence data. + +NOTE: SMF indicates the Internal Group ID(s) and DNN/S-NSSAI to PCF, and PCF uses these to retrieve the corresponding traffic influence data from UDR, as specified in Rel-17, clause 6.4.2.2 of TS 29.519 [17]. + +[Optional] If the DNS queries are to be used to influence to the EAS address selection as described in clauses 6.15.3.2 and 6.15.3.3, the SMF retrieves the EAS Deployment Information as described in TS 23.548 [3]. + +3. SMF(s) invoke the SCMF for selection of the common DNAI. This is described in clause 6.15.3.2. + +Depending on the variation of the procedure, the SMF(s) may invoke the SCMF either based on the user subscription and service data as received in steps 1 and 2, or alternatively the SMF(s) invoke SCMF in dynamic manner based on DNS Query from the UE. + +Rest of the clauses describes the following procedures: + +- Clause 6.15.3.2 "Selection of the common DNAI" describes the core procedure in the solution how SCMF selects the common DNAI. This procedure is part of all solution variants. +- Clause 6.15.3.3 "EAS selection and re-selection using ECS option, preconfigured" describes a solution variant where SMF(s) invoke the SCMF based on the preconfigured user subscription and service data before any DNS Query from the UE. ECS option in DNS request is used to indicate the common DNAI to the DNS server. +- Clause 6.15.3.4 "EAS selection and re-selection using ECS option, dynamic invoke of SCMF" describes a solution variant where SMF(s) invoke the SCMF based on a DNS Query from the UE. ECS option in DNS request is used to indicate the common DNAI to the DNS server. +- Clause 6.15.3.5 "EAS selection and re-selection via application layer" describes a solution variant where SMF(s) invoke the SCMF based on the user subscription and service data. Early/late UP path change notifications are used to indicate the common DNAI to the application layer. + +### 6.15.3.2 Selection of the common DNAI + +Figure 6.15.3.2-1 describes a procedure for selection of common DNAI for the collection of UEs that should use a common local part of DN and common EAS. + +![Sequence diagram illustrating the selection of the common DNAI. The diagram shows interactions between BSF/NRF, SMF, UPF, SCMF, AMF, and NWDAF. The steps are: 1. SMF discovers the SCMF; 2. SMF invokes the SCMF; 3. SCMF uses Analytics from NWDAF and subscribes for UE mobility events from AMF; 4. SCMF notifies the SMF(s) for the common DNAI; 5. SMF(s) select the UPF based on the common DNAI; 6. SCMF may re-select the common DNAI based on UE mobility events from AMF.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +``` + +sequenceDiagram + participant BSF/NRF + participant SMF + participant UPF + participant SCMF + participant AMF + participant NWDAF + + Note right of SMF: 1. SMF discovers the SCMF. + Note right of SMF: 2. SMF invokes the SCMF. + Note right of SCMF: 3. SCMF can use the Analytics from NWDAF for service experience between gNB and candidate UPFs. NWDAF subscribes for UE mobility events from AMF. + Note right of SCMF: 4. SCMF notifies the SMF(s) for the common DNAI. + Note right of SMF: 5. SMF(s) select the UPF based on the common DNAI. + Note right of SCMF: 6. SCMF may re-select the common DNAI, e.g. If the SCMF receives a UE mobility event from the AMF. SCMF notifies the SMF(s) for the new common DNAI, and SMF(s) re-select the UPF. + +``` + +Sequence diagram illustrating the selection of the common DNAI. The diagram shows interactions between BSF/NRF, SMF, UPF, SCMF, AMF, and NWDAF. The steps are: 1. SMF discovers the SCMF; 2. SMF invokes the SCMF; 3. SCMF uses Analytics from NWDAF and subscribes for UE mobility events from AMF; 4. SCMF notifies the SMF(s) for the common DNAI; 5. SMF(s) select the UPF based on the common DNAI; 6. SCMF may re-select the common DNAI based on UE mobility events from AMF. + +**Figure 6.15.3.2-1: Selection of the common DNAI** + +1. SMF receives the user subscription data and PCC Rules as described in step 2 in clause 6.15.3.1. Based on the "Indication of traffic correlation" and "influence-id" associated with a list of DNAIs in the PCC Rules, SMF knows that it needs to discover a SCMF for a selection of a common DNAI. SMF discovers the SCMF from NRF. SMF discovers one SCMF for each "influence-id" associated with a list of DNAIs in the PCC Rules. + +BSF can be used to ensure that the same SCMF is selected for all PDU Sessions with the same "influence-id"; SMF uses the "influence-id" to retrieve the SCMF identity from the BSF. If the registration in BSF for the given "instance-id" does not exist, the SMF discovers the SCMF from NRF, using e.g. the DNN/S-NSSAI as a discovery factor. SCMF registers the "influence-id" to BSF after SCMF has been selected for the first PDU Session for an "influence-id". + +2. The SMF invokes the SCMF and indicates the "influence-id", SUPI, DNN/S-NSSAI, and a list of DNAIs for the given "influence-id" as received in the PCC Rules to the SCMF. The SMF invokes the SCMF for each "influence-id" associated with a list of DNAIs in the PCC Rules. +3. For the selection of the common DNAI for a collection of PDU Sessions associated with the same "influence-id", the SCMF may consider the UE locations, network topology, or the current Analytics from NWDAF for service experience between the gNB and candidate UPFs. SCMF can subscribe for UE location info (UE mobility events) for the SUPI from the AMF. Based on the current Rel-17 procedures, there are two options for the SCMF to subscribe the mobility event for a UE: + - the SCMF uses Nudm\_EventExposure\_Subscribe service operation from UDM for a SUPI, and UDM continues the rest, i.e. knows the AMF for the SUPI; + - the SCMF manages a certain area and subscribes mobility events for any UE from all AMFs serving this area. + +If the SCMF uses Analytics services from NWDAF, the SCMF invokes the NWDAF on PDU Session and "influence-id" basis. + +4. SCMF determines the common DNAI per each "influence-id" and notifies the SMF(s) of the corresponding "influence-id" for the result. Based on the notification from the NWDAF, or any internal trigger, SCMF can reselect a new common DNAI, and notify the SMF(s) for the change of the common DNAI accordingly. +5. The SMF(s) select and relocate the UPF based on the notifications from SCMF. The SMF configures the UPF to route the UL traffic towards the EAS in the L-DN. The details depend on how the EAS is discovered and is described in clause 6.15.3.2. +6. Whenever a new UE that belongs to the same Internal Group ID initiates a PDU Session with the given DNN/S-NSSAI, the steps 2-5 are performed for the new PDU Session. + +If the SCMF determines a new common DNAI for the group, the SMF(s) of the existing PDU Sessions are notified by the SCMF for a new common DNAI. This may be done e.g. due to a new PDU Session joining to the group, or one of the existing PDU Sessions are released, or one or more of the UEs in the group are moving and the SCMF finds a more optimal DNAI. + +### 6.15.3.3 EAS selection and re-selection using ECS option, preconfigured + +Figure 6.15.3.3-1 describes a procedure for EAS selection and re-selection for a group of UEs when DNS queries from the UE influence to the EAS selection. EDNS Client Subnet option in the DNS Query is used to indicate the common DNAI to the DNS server. The SMF subscription for the common DNAI from SCMF is done based on the pre-configured edge service data that is applicable for the PDU Session, i.e. traffic influence data and EAS Deployment Information as described in TS 23.548 [3]. + +The flow is applicable for all connectivity models described in TS 23.548 [3]. UPF in the figure corresponds to PSA UPF in the local site (L-PSA UPF). In case of Session Breakout connectivity model, the UL-CL or BP is used although not shown in the figure. In case of Distributed Anchor connectivity model, instead of EASDF a DNS resolver that is preconfigured with the ECS Option may be used. + +![Sequence diagram for EAS (re-)selection using ECS option, preconfigured. The diagram shows interactions between UE, SMF, EASDF, UPF, DNS server, and EAS. Step 1: SMF configures the EASDF. Step 2: UE sends a DNS query, EASDF notifies SMF and inserts ECS option, DNS server returns EAS IP address(es). Step 3: UP data flow. Step 4: SCMF may notify SMF for change of common DNAI, SMF re-selects UPF.](10bf8762a8e8d9385609cc6fb11061fe_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant EASDF + participant UPF + participant DNS server + participant EAS + + Note right of SMF: 1. SMF configures the EASDF. + Note right of UE: 2. UE sends a DNS query. EASDF notifies the SMF. EASDF inserts an ECS option to the DNS request corresponding to the common DNAI. DNS server returns the EAS IP address(es). + Note right of UPF: 3. UP data flow + Note right of SCMF: 4. SCMF may notify the SMF(s) for the change of common DNAI. SMF re-selects the UPF. + +``` + +Sequence diagram for EAS (re-)selection using ECS option, preconfigured. The diagram shows interactions between UE, SMF, EASDF, UPF, DNS server, and EAS. Step 1: SMF configures the EASDF. Step 2: UE sends a DNS query, EASDF notifies SMF and inserts ECS option, DNS server returns EAS IP address(es). Step 3: UP data flow. Step 4: SCMF may notify SMF for change of common DNAI, SMF re-selects UPF. + +**Figure 6.15.3.3-1: EAS (re-)selection using ECS option, preconfigured** + +Pre-requisite: SMF receives the user subscription data and PCC Rules as described in step 2 in clause 6.15.3.1. SMF has invoked the SCMF as described in clause 6.15.3.2. SCMF notifies the SMF for the common DNAI. + +1. The SMF uses the common DNAI to select the UPF. The SMF configures the EASDF for the DNS message handling rules using the EAS Deployment Information as described in TS 23.548 [3]. The SMF may notify the AF for UP path change events via early and/or late notifications as described in clause 4.3.6.3 in TS 23.502 [9], based on subscriptions in the PCC Rules. The notifications indicate the common DNAI as a target DNAI. +2. When the UE initiates a DNS Query, the EASDF matches it against the rules it has received from the SMF. Based on the DNS message handling rules from SMF, the EASDF inserts an EDNS Client Subnet option to the + +DNS Query. The EDNS Client Subnet option refers to a location that is topologically close to the common DNAI. The DNS server may resolve the EAS IP address considering the EDNS Client Subnet option and sends the DNS Response via the EASDF and UPF1 to the UE. + +3. Application client and EAS transmit data via the user plane via UPF. +4. If the SCMF determines a new common DNAI as described in step 6 in clause 6.15.3.2, the SCMF notifies all SMF(s) that have subscribed for the given "instance-id". The SMF(s) reselect the UPF accordingly. SMF(s) notify the AF as in step 2. + +The SMF(s) trigger an EAS rediscovery procedure with the UE(s). In case of Distributed Anchor Point connectivity model as described in TS 23.548 [3], when the SMF relocates the UPF, the UE detects that the PDU Session is released or new IP prefix is allocated within the PDU Session, and the UE removes the old DNS cache related to old/removed IP address/prefix as described in clause 6.2.2. in TS 23.548 [3]. + +In case of Session Breakout connectivity model as described in TS 23.548 [3], the SMF sends PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE as described in in clause 6.2.3.3 in TS 23.548 [3]. The EAS rediscovery indication indicates to refresh the cached EAS information. The UE behaves as described in TS 23.548 [3]. + +The UE(s) resolve the new EAS address as in step 2. Application client and the new EAS transmit data via the user plane via new UPF. + +If the PCC Rules indicate multiple "influence-ids" with Session Breakout connectivity model, the SMF(s) may assign a separate local PSA for each common DNAI, if necessary. In Distributed Anchor connectivity model, the SMF(s) can assign a local PSA that is most optimal for any of the common DNAIs. + +#### 6.15.3.4 EAS selection and re-selection using ECS option, dynamic invoke of SCMF + +Figure 6.15.3.4-1 describes a procedure for EAS selection and re-selection for a group of UEs when DNS queries from the UE influence the EAS selection. EDNS Client Subnet option in the DNS Query is used to indicate the common DNAI to the DNS server. The invoke of the SCMF is done in dynamic manner based on the DNS Queries from the UE, in addition to edge service data that is applicable for the PDU Session, i.e. traffic influence data and EAS Deployment Information as described in TS 23.548 [3]. + +The flow is applicable for all connectivity models described in TS 23.548 [3]. In case of Session Breakout connectivity model the UL-CL or BP is used although not shown in the figure. + +![Sequence diagram illustrating EAS (re-)selection using ECS option, dynamic model. The diagram shows interactions between UE, SMF, EASDF, C-UPF, DNS server, L-UPF, and EAS. The process involves SMF configuring EASDF, UE sending a DNS query, discovery of SCMF, re-sending of DNS query with ECS option, and potential reselection of UPF.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant EASDF + participant C-UPF + participant DNS server + participant L-UPF + participant EAS + + Note right of SMF: 1. SMF configures the EASDF. + SMF->>C-UPF: 2. UP data flow + Note left of C-UPF: 3. UE sends a DNS query. EASDF notifies the SMF. + Note right of SMF: 4. Discovery of the SCMF. SCMF notifies the SMF for the common DNAI. +SMF selects the L-UPF. +[Distributed anchor] SMF triggers the UE to perform a reselection of EAS. + Note left of C-UPF: 5. [Distributed anchor] UE re-sends the DNS query. +EASDF inserts the ECS option to the DNS request corresponding to the common DNAI. +DNS server returns the EAS IP address(es). + Note right of SMF: 6. UP data flow + Note left of C-UPF: 7. SCMF may notify the SMF(s) for the change of common DNAI. SMF re-selects the UPF. +[Distributed anchor] The SMF triggers the UE to perform a reselection of EAS. + +``` + +Sequence diagram illustrating EAS (re-)selection using ECS option, dynamic model. The diagram shows interactions between UE, SMF, EASDF, C-UPF, DNS server, L-UPF, and EAS. The process involves SMF configuring EASDF, UE sending a DNS query, discovery of SCMF, re-sending of DNS query with ECS option, and potential reselection of UPF. + +**Figure 6.15.3.4-1: EAS (re-)selection using ECS option, dynamic model** + +Pre-requisite: SMF receives the user subscription data and PCC Rules as described in step 2 in clause 6.15.3.1. + +1. The SMF configures the EASDF for the DNS message handling rules using the EAS Deployment Information as described in TS 23.548 [3]. +2. The SMF assigns a central UPF (C-UPF) for the PDU Session. +3. When the UE initiates a DNS Query, the EASDF matches it against the rules it has received from the SMF. +4. Based on the DNS message handling rules from SMF, the EASDF reports the FQDN to the SMF. The SMF uses the user subscription data and edge service data as described in clause 6.15.3.1 step 3 to determine that the FQDN is related to a group service where a SCMF needs to be invoked. + +The SMF invokes the SCMF as described in clause 6.15.3.2. The SMF selects the UPF based on the common DNAI as described in clause 6.15.3.2. + +In case of Session Breakout connectivity model, the SMF configures the EASDF to insert an EDNS Client Subnet option to the DNS Query, as described in step 2 in clause 6.15.3.3. + +In case of Distributed Anchor connectivity model, the SMF triggers an EAS rediscovery procedure with the UE as described in step 4 in clause 6.15.3.3. + +5. In case of Distributed Anchor connectivity model, the UE re-initiates a DNS Query as in step 4 in clause 6.15.3.3. The EASDF matches it against the rules it has received from the SMF. + +Based on the DNS message handling rules from SMF, the EASDF inserts an EDNS Client Subnet option to the DNS Query. The DNS server returns the EAS address to the UE. + +6. Application client and EAS transmit data via the user plane via L-UPF. + +7. If the SCMF determines a new common DNAI as described in step 6 in clause 6.15.3.2, the SCMF notifies all SMF(s) that have subscribed for the given "instance-id". The SMF(s) reselect the UPF accordingly. UE(s) perform an EAS reselection as described in step 4 in clause 6.15.3.2. + +NOTE: Signalling storm can be avoided especially at race conditions by implementing a threshold so that common DNAI does not change back and forth frequently among a group of DNAIs. + +If the PCC Rules indicate multiple "influence-ids" with Session Breakout connectivity model, the SMF(s) may assign a separate local PSA for each common DNAI, if necessary. In Distributed Anchor connectivity model, the SMF(s) can assign a local PSA that is most optimal for any of the common DNAIs. + +### 6.15.3.5 EAS selection and re-selection via application layer + +Figure 6.15.3.5-1 describes a procedure for EAS selection and re-selection for a group of UEs when application layer protocols are used to redirect the application client in the UE to an EAS serving the group. In this case, DNS queries from the UE do not influence to the EAS selection. The flow is applicable for all connectivity models described in TS 23.548 [3]. In case of Session Breakout model, the UPFs in the figure correspond to PSA UPF in the local site (L-PSA UPF). + +In this procedure, the EASDF is not involved and the Nnef\_EASDeployment service is not used. + +![Sequence diagram for EAS (re-)selection via application layer. The diagram shows five entities: UE, AF, SMF, UPF, and EAS. The sequence of events is: 1. SMF notifies the AF for the UP path change event. 2. Application layer informs the App client in the UE for the FQDN or IP address of the EAS. 3. UP data flow (indicated by a dashed double-headed arrow between UE and EAS via UPF). 4. SCMF may notify the SMF(s) for the change of common DNAI. SMF re-selects the UPF. Steps 1-2 are repeated.](879d68959f0c0ba370ef82447298ba17_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AF + participant SMF + participant UPF + participant EAS + + Note right of SMF: 1. SMF notifies the AF for the UP path change event. + Note left of UE: 2. Application layer informs the App client in the UE for the FQDN or IP address of the EAS. + Note right of SMF: 3. UP data flow + Note left of UE: 4. SCMF may notify the SMF(s) for the change of common DNAI. SMF re-selects the UPF. Steps 1-2 are repeated. + +``` + +Sequence diagram for EAS (re-)selection via application layer. The diagram shows five entities: UE, AF, SMF, UPF, and EAS. The sequence of events is: 1. SMF notifies the AF for the UP path change event. 2. Application layer informs the App client in the UE for the FQDN or IP address of the EAS. 3. UP data flow (indicated by a dashed double-headed arrow between UE and EAS via UPF). 4. SCMF may notify the SMF(s) for the change of common DNAI. SMF re-selects the UPF. Steps 1-2 are repeated. + +**Figure 6.15.3.5-1: EAS (re-)selection via application layer** + +Pre-requisite: SMF receives the user subscription data and PCC Rules as described in step 2 in clause 6.15.3.1. SMF has invoked the SCMF as described in clause 6.15.3.2. SCMF notifies the SMF for the common DNAI. + +1. The SMF uses the common DNAI to select the UPF. The SMF notifies the AF for UP path change events via early and/or late notifications as described in clause 4.3.6.3 in TS 23.502 [9]. The notifications indicate the common DNAI as a target DNAI. +2. The application layer informs the UE for the group FQDN that corresponds to the current common DNAI. The UE resolves the EAS address via DNS Query. Alternatively, the application layer can inform the EAS IP address(es) directly via application layer. This step is out of scope of 3GPP. +3. Application client and EAS transmit data via the user plane via UPF. +4. If the SCMF determines a new common DNAI, the SCMF notifies all SMF(s) that have subscribed for the given "instance-id". The SMF(s) reselect the UPF accordingly. SMF(s) notify the AF as in step 1. The UE(s) resolve the new EAS address as in step 2. Application client and new EAS transmit data via the user plane via new UPF. + +If the PCC Rules indicate multiple "influence-ids" with Session Breakout connectivity model, the SMF(s) may assign a separate local PSA for each common DNAI, if necessary. In Distributed Anchor connectivity model, the SMF(s) can assign a local PSA that is most optimal for any of the common DNAIs. + +## 6.15.4 Impacts on services, entities and interfaces + +### SCMF: + +- a new function; +- determines the common DNAI for a collection of UEs; +- notifies the SMF(s) that have subscribed for the common DNAI; +- has similar information about the network topology and DNAIs as the SMF has; +- registers to the BSF using the Nbsf\_Management\_Register service operation; +- implements a threshold so that the common DNAI does not change back and forth between the same DNAIs; +- delays the individual notifications it generates to the SMFs if the group is big. + +### BSF: + +- Nbsf\_Management\_Register is enhanced for the SCMF to be able to register the SCMF ID and the influence-id to the BSF; +- Nbsf\_Management\_Discovery service operations is enhanced to be able to discover the SCMF ID based on the influence-id. + +### SMF: + +- discovers and invokes the SCMF; +- discovers the SCMF from BSF using the Nbsf\_Management\_Discovery service operation; +- selects the UPF based on the common DNAI as notified by the SCMF. + +### PCF: + +- receives the "influence-id" from UDR and includes it into PCC Rules as part of traffic influence data. + +### UDR: + +- indicates the "influence-id" to the PCF in Nudm\_DataManagement service response for each entry in the traffic influence data in the UDR. + +## 6.16 Solution 16 (KI#4): Selecting the same EAS/DNAI for collection of UEs + +### 6.16.1 Description + +This solution corresponds to KI#4: + +- whether and how to define a collection of UEs forming a dynamic ad-hoc group that should use the same EAS and/or same local part of DN and/or same DNAI and how the collection is identified; +- whether and what improvements are required for EAS discovery and re-discovery for UEs belonging to a collection of UEs. + +## 6.16.2 Procedures + +### 6.16.2.1 EAS discovery procedure + +The following is the procedure for selecting the same EAS for collection of UEs accessing the same application. The procedures defined in figure 4.3.6.2-1 in TS 23.502 [9] and figure 6.2.3.2.2-1 in TS 23.548 [3] are reused. + +There could be only one SMF for serving the collection of UEs that connecting to the same EAS/DNAI for accessing the same application, or there could be multiple SMFs for different UEs in the collection. AF could provide the common EAS/DNAI in AF request, in which case, SMF(s) select the common EAS/DNAI provided by AF. If AF does not provide the common EAS/DNAI, then SMF selects the common EAS/DNAI and stores it in the corresponding AF traffic influence request information in UDR. + +![Sequence diagram illustrating the discovery procedure for selecting the same EAS/DNAI for collection of UEs. The diagram shows interactions between UE, EASDF, DNS Server, SMF, PCF, UDR, NEF, and AF. The steps are: 1. AF Request to influence traffic routing procedure (SMF to AF); 2. EAS discovery procedure with EASDF (SMF to EASDF); 3. Determine UE accessing the application belongs to the collection (SMF internal); 4. Synchronization Procedure for EAS IP or DNAI (SMF to PCF); 5. EAS discovery procedure with EASDF (SMF to EASDF); 6. Synchronization Procedure for EAS IP or DNAI (SMF to PCF).](1399c76ef88f22b70d05ed3f781d3c48_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 + SMF->>AF: + Note left of SMF: 2. Step 1~9 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF, TS23.548 + SMF->>EASDF: + Note right of SMF: 3. determine UE Accessing the application belongs to The collection of UEs should use the same EAS or DNAI for the application + SMF->>PCF: 4. Synchronization Procedure for EAS IP or DNAI + Note left of SMF: 5. Step 10~19 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF, TS23.548 + SMF->>EASDF: + SMF->>PCF: 6. Synchronization Procedure for EAS IP or DNAI + +``` + +Sequence diagram illustrating the discovery procedure for selecting the same EAS/DNAI for collection of UEs. The diagram shows interactions between UE, EASDF, DNS Server, SMF, PCF, UDR, NEF, and AF. The steps are: 1. AF Request to influence traffic routing procedure (SMF to AF); 2. EAS discovery procedure with EASDF (SMF to EASDF); 3. Determine UE accessing the application belongs to the collection (SMF internal); 4. Synchronization Procedure for EAS IP or DNAI (SMF to PCF); 5. EAS discovery procedure with EASDF (SMF to EASDF); 6. Synchronization Procedure for EAS IP or DNAI (SMF to PCF). + +**Figure 6.16.2.1-1: Discovery procedure for selecting the same EAS/DNAI for collection of UEs** + +1. The AF request in step 1 of figure 4.3.6.2-1 in TS 23.502 [9] is used to request selecting the same EAS or same DNAI for UEs accessing the application as identified in the AF Request. + +An eas\_correlation indication or dnai\_correlation indication is provided for indicating selecting the same EAS or the same DNAI (i.e. selecting EAS corresponding to the same DNAI) for collection of UEs accessing the same application (e.g. FQDN). Spatial Validity Condition could be provided for limiting the location of the UEs, and also "any UE" or an UE list or group ID will be provided for defining UE collection accessing the same EAS or the same DNAI. + +- In the case of selecting the same DNAI, the DNAI could be determined and provided by AF to PCF and then to SMF. +- In the case of selection the same EAS, the EAS could be determined and provided by AF to PCF and then to SMF. + +A Correlation ID is included in AF Request for identifying the UE collection. + +In step 5 of figure 4.3.6.2-1 of TS 23.502 [9], PCF determines the UEs influenced by the AF Request, and based on AF request, PCF creates PCC rule with FQDN, Correlation ID, and eas\_correlation indication or dnai\_correlation indication to SMF. + +2. The same as steps 1~9 in figure 6.2.3.2.2-1 of TS 23.548 [3]. +3. If FQDN in Neasdf\_DNSContext\_Notify Request is for the application (e.g. FQDN) indicated in AF request, and if eas\_correlation indication is set, SMF determines the UE belongs to collection of UEs accessing the application and determines the UE needs to select the same EAS as UEs in the UE collection; or if + +dnai\_correlation indication is set, SMF determines the UE belongs to collection of UEs accessing the application and determines the UE needs to select EAS corresponding to the same DNAI as UEs in the UE collection. + +4. If EAS IP/DNAI has not been determined, or SMF could not make sure the selected EAS IP/DNAI is the one that is stored in UDR, then SMF synchronizes with UDR and receives EAS IP or DNAI for the UE collection, as defined in clause 6.16.2.2. UDR maintains EAS IP or DNAI for the UE collection. +5. Based on steps 10~19 in figure 6.2.3.2.2-1 of TS 23.548 [3]: + +For selecting the same EAS case: if the same EAS for the UE collection has not been determined yet, steps 10~15 are used for discovering an EAS, and between step 14 and step 16, SMF could send the selected EAS IP to UDR; When the same EAS for the UE collection has been determined, in step 17, SMF sends DNS message handling rule with IP address for the EAS instructing EASDF to return the IP address for the EAS to UE in step 19, steps 10~15 are skipped; + +For selecting EAS corresponding to the same DNAI case: if no DNAI for the UE collection has been determined, in step 10 SMF determines DNAI for the UE collection and selects information to build ECS option or Local DNS server based on the DNAI. When DNAI for the UE collection has been determined, in step 10 SMF determines information to build ECS option or local DNS server related to the DNAI, and sends DNS message handling rule with the information to build ECS option or local DNS server. + +6. If EAS IP/DNAI has not been determined, or SMF could not make sure the selected EAS IP/DNAI is the one that stored in UDR, then SMF synchronizes EAS IP/DNAI with UDR via NEF, as defined in clause 6.16.2.2. + +## 6.16.2.2 Synchronization procedure for EAS IP/DNAI + +![Sequence diagram showing the synchronization procedure for EAS IP/DNAI between SMF, PCF, and UDR. The diagram consists of two main parts. The first part shows SMF sending an Npcf_SMPolicyControl_Update Request to PCF, which then sends a Nudr_DM_Update Request to UDR. UDR responds with a Nudr_DM_Update Response to PCF, which in turn sends an Npcf_SMPolicyControl_Update Response to SMF. The second part shows PCF sending a Nudr_DM_Subscribe to UDR, which responds with a Nudr_DM_Notify to PCF, which then sends an Npcf_SMPolicyControl_UpdateNotify to SMF.](ddcdc1712375261ba1d89165fdf12aa6_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant PCF + participant UDR + + Note left of SMF: Part 1: Update + SMF->>PCF: 1.Npcf_SMPolicyControl_Update Request + PCF->>UDR: 2.Nudr_DM_Update Request + UDR-->>PCF: 3.Nudr_DM_Update Response + PCF-->>SMF: 4.Npcf_SMPolicyControl_Update Response + + Note left of SMF: Part 2: Subscribe/Notify + PCF->>UDR: 5.Nudr_DM_Subscribe + UDR-->>PCF: 6.Nudr_DM_Notify + PCF-->>SMF: 7.Npcf_SMPolicyControl_UpdateNotify + +``` + +Sequence diagram showing the synchronization procedure for EAS IP/DNAI between SMF, PCF, and UDR. The diagram consists of two main parts. The first part shows SMF sending an Npcf\_SMPolicyControl\_Update Request to PCF, which then sends a Nudr\_DM\_Update Request to UDR. UDR responds with a Nudr\_DM\_Update Response to PCF, which in turn sends an Npcf\_SMPolicyControl\_Update Response to SMF. The second part shows PCF sending a Nudr\_DM\_Subscribe to UDR, which responds with a Nudr\_DM\_Notify to PCF, which then sends an Npcf\_SMPolicyControl\_UpdateNotify to SMF. + +Figure 6.16.2.2-1: Synchronization Procedure for EAS IP/DNAI + +- 1-4. In case a new EAS/DNAI has been determined, SMF sends the EAS/DNAI, Resource URI to PCF by invoking Npcf\_SMPolicyControl\_Update Request, triggering the PCF to update the corresponding AF traffic influence request information with common EAS/DNAI in UDR and UDR will lock the data to prevent the data to be modified to other EAS/DNAI by other PCF providing different EAS/DNAI for the same UE collection. PCF updates PCC rule to SMF including the common EAS/DNAI of AF traffic influence request information in UDR. + +In case SMF decides to trigger EAS rediscovery for UE collection, SMF removes the common EAS/DNAI from AF traffic influence request information, UDR notifies PCF, and then PCF updates SMF with updated PCC rule removing the common EAS/DNAI, and triggers other SMF for EAS rediscovery. + +NOTE 1: Npcf\_SMPolicyControl\_Update is proposed to be used for updating EAS/DNAI in UDR, but a new service or operation, instead of reusing Npcf\_SMPolicyControl\_Update could also be a candidate. + +NOTE 2: The common EAS/DNAI for collection of UEs could be deleted in case the AF traffic influence request information is removed by AF. + +- 5-7. In case the common EAS/DNAI for collection of UEs is created/deleted, UDR notifies PCFs and then PCF will update PCC rules. + +## 6.16.3 Impacts on services, entities and interfaces + +### AF: + +- to be updated with eas\_correlation indication/ dnai\_correlation indication for indicating selecting the same EAS/DNAI for collection of UEs accessing the application; +- providing UE ID list, Correlation ID in AF Request. + +### NEF: + +- Nnef\_TrafficInfluence service is impacted to include "eas\_correlation indication" or "dnai\_correlation indication", list of FQDNs and list of UE identities. + +### SMF: + +- to be updated for storing and retrieving the EAS/DNAI from UDR; +- using the retrieved EAS/DNAI when selecting the same EAS/DNAI for collection of UEs; +- when deciding to trigger EAS rediscovery, SMF requests to remove the common EAS/DNAI from AF traffic influence request information; +- initializes EAS rediscovery when receiving updated PCC rule removing the common EAS/DNAI. + +### UDR: + +- to be updated for maintaining common EAS/DNAI for the collection of UEs in AF traffic influence request information for the application. + +### EASDF: + +- to be updated for create and send DNS response to UE. + +### PCF: + +- Npcf\_SMPolicyControl\_UpdateNotify service is to be updated to transmit PCC rule with eas\_correlation indication/ dnai\_correlation indication, Correlation ID, common EAS/common DNAI, Resource URI and FQDN(s); +- receiving EAS/DNAI from SMF. + +## 6.17 Solution 17 (KI#4): Application layer EAS selection for collections of UEs + +### 6.17.1 Introduction + +This solution corresponds to KI #4. This solution assumes that the AF is responsible for generating the collection of the UEs and select the same EAS for the collection of the UEs. The SMF(s) selects the candidate DNAI(s) for the UE(s) and exposes them to the AF. The AF determines the common DNAI considering the candidate DNAI(s) from different SMFs, then the AF can select the proper EAS with the common DNAI for the collection of the UEs. + +### 6.17.2 Functional Description + +This solution is based on the following principles: + +- The AF can determine the user list and sends the UE list and available DNAI list to 5GC to query the candidate DNAI(s) for the UEs. + +- SMF decides the candidate DNAI(s) for the UE(s) in the UE list served by the SMF according to the location of the UE(s) and the DNAI topology. + +NOTE: The UEs of the group may be served by multiple SMFs. + +- The AF can determine the common DNAI based on candidate DNAIs from SMF(s) and then discover an EAS and notify the UEs about the selected EAS via the application layer. + +## 6.17.3 Procedures + +### 6.17.3.1 EAS selection for multiple UE based application layer + +This solution focuses on the EAS selection for multiple UE based application layer. + +![Sequence diagram illustrating the application layer implementation for EAS selection. The diagram shows interactions between UE, SMF, PCF, UPF, ULCL/Local PSA, BSF, AF, and EAS. The process involves AF sending discovery requests to BSF, AF retrieve requests to PCF, DNAI retrieve requests to SMF, DNAI selection by SMF, AF retrieve responses to AF, EAS selection by AF, AF influence traffic routing for UEs, Service Server IP notification to UPF, and Service Data flow between UPF and EAS.](149826281804ec51b5cca5603c88b23b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant PCF + participant UPF + participant ULCL/Local PSA + participant BSF + participant AF + participant EAS + + Note left of UE: Multiple UEs + Note left of SMF: Multiple SMFs + Note left of PCF: Multiple PCFs + + AF->>BSF: 1. Nbsf_management_Discovery request + AF->>PCF: 2. AF retrieve request + PCF->>SMF: 3. DNAI retrieve request + Note right of SMF: 4. DNAI selection + SMF->>AF: 5. AF retrieve response + Note right of AF: 6. EAS selection + Note right of ULCL/Local PSA: 7. AF influence traffic routing for the UEs + AF-->>UPF: 8. Service Server IP notification + UPF-->>EAS: 9. Service Data + EAS-->>UPF: 9. Service Data + UPF-->>UE: 9. Service Data + +``` + +Sequence diagram illustrating the application layer implementation for EAS selection. The diagram shows interactions between UE, SMF, PCF, UPF, ULCL/Local PSA, BSF, AF, and EAS. The process involves AF sending discovery requests to BSF, AF retrieve requests to PCF, DNAI retrieve requests to SMF, DNAI selection by SMF, AF retrieve responses to AF, EAS selection by AF, AF influence traffic routing for UEs, Service Server IP notification to UPF, and Service Data flow between UPF and EAS. + +**Figure 6.17.3.1-1: Application layer implementation for EAS selection** + +1. The AF groups the UEs and generates the UE list (UE addresses) of the collection of UEs according to its application logic. The AF sends Nbsf\_management\_Discovery request(s) to the BSF to retrieve the PCF(s) for each UE in the UE list. +- 2 For each UE, AF sends AF retrieve request to the PCF to query the candidate DNAI(s). The AF request may include the available DNAI list where EAS instances are deployed. The AF request may also include the UE list. The AF may send the AF request to PCF directly, or via the NEF. +3. PCF sends the DNAI retrieve request to SMF. +4. SMF selects the candidate DNAI(s). The SMF may consider the UE location and available DNAI list provided by AF to select the closest available DNAI(s) as candidate DNAI(s). The SMF may also provide the DNAI(s) in a prioritized order. +5. SMF notifies the AF (optionally via NEF) about the candidate DNAI(s) of the UE. +6. After receiving the candidate DNAI(s) of each UE in the list, the AF selects a proper EAS and a common DNAI according to the DNAI(s). +7. AF initiates AF influence on traffic routing procedure as defined in clause 4.3.6.4 of TS 23.502 [9] for each UE in the UE list to route the application traffic to the common DNAI. +8. The AF notifies the UEs about the selected EAS via application layer. +9. The users connect to the same EAS via the common DNAI and start the service. + +## 6.17.4 Impacts on services, entities and interfaces + +AF/NEF: + +- supports sending new AF retrieve request to query the candidate DNAI(s) of a list of UEs. + +PCF: + +- supports handling the AF retrieve request and sending corresponding DNAI retrieve request to SMF. + +SMF: + +- supports selecting the candidate DNAI(s) for the UE according to the location of the UE(s) and the DNAI topology; +- supports notifying the AF about the candidate DNAI(s) of the UE. + +## 6.18 Solution 18 (KI#4): Discovery of the same EAS for collections of UEs + +### 6.18.1 Description + +In order to realize the discovering the same EAS to collections of UEs, the following conditions should be satisfied: + +- The same FQDN in DNS query or a group of FQDNs that can be resolved to a certain EAS IP address by DNS server. The same EAS can be mapped to one FQDNs or a group of FQDNs. Only the collections of the UEs request the same DNS query with these FQDNs, that the DNS server can provide the same EAS IP address. +- The collections of the UEs have the similar UE location. For example, in a stadium, some of the players can access the 5GC by the same gNB or a group of gNBs, UEs are located in a specific location area. According to the UE location information, the 5GC can identify that these UEs should be served by the same EAS. +- The collections of the UEs are identified by UE Identifiers, e.g. UEs belong to an Ad-hoc group. + +An AF request may be created to include indication of EAS correlation and pre-conditions as defined in step 1 of figure 4.3.6.2-1 of TS 23.502 [9], which is used to request selecting the same EAS for a collection of UEs. The pre-conditions indicate the conditions whether a UE belongs to a collection of UEs. The pre-conditions may reuse the information elements as defined in clause 5.6.7 of TS 23.501 [2], which includes Spatial Validity Condition (e.g. Area of Interest(s)), FQDN(s)/Application Identifier(s), Target UE Identifier(s). The PCF creates the PCC rule based on information provided in AF request, and sends the PCC rule to SMF. + +The pre-conditions may also be a local policy preconfigured on SMF. The SMF determines whether the pre-conditions are satisfied, and which UE collection the UE belongs to, according to the pre-conditions and received information (e.g. UE location is in the Area of Interest, requested FQDN in DNS query). + +If the Spatial Validity Condition is provided in AF request as the pre-condition, the PCF subscribes to the SMF to receive notifications about change of UE location in an area of interest. The SMF is aware the UE location is in or out of the subscribed area of interest and sends notifications to the PCF, as specified in clause 5.6.7.1 of TS 23.501 [2]. If the FQDN(s)/Application Identifier(s) is provided in AF request as the pre-condition, it is carried in the PCC rule as Service data flow template. If the indication of EAS correlation is included in the PCC rule, then SMF determines which UE collection the UE belongs to, accordingly. + +NOTE 1: Target UE Identifier(s) can be group identifier and stored in UDR as current mechanism. + +NOTE 2: For multiple SMFs situation, the updated information (e.g. common EAS/DNS server) are stored in UDR and synchronize the data to other SMFs. + +When the pre-conditions above are guaranteed, that for the 5GC side, the following procedures can be used to realize to discover the same EAS for these UEs: + +- Use the same DNS server to resolve the FQDN. It needs the 5GC to deliver the same DNS server IP address to these UEs, for example, the EASDF or local DNS server. + +- If the same local DNS server is selected, that whether the EAS will be resolved depends on the DNS server's mechanism that is out of scope. +- If the same EASDF is selected, that all these DNS query should be treated with the same way, that applied to the same DNS message handling rules. Whether and how the C-DNS or L-DNS to resolve the same EAS depends on the DNS server's mechanism that is out of scope. +- Directly responds to the DNS query to UE. This way only applies to the EASDF. That if the EASDF identifies that the UE's DNS query should be replied with the same EAS that other UEs use, the EASDF can directly respond with the DNS query without having the DNS related procedure to DNS server. The SMF may determine a timer to update the IP address of EAS in DNS message handling rule using the Neasdf\_DNSContext\_Update Service. How the SMF determines the timer is by implementation. + +**Table 6.18.1-1: Example of pre-conditions of configured the same EAS** + +| Pre-condition | Actions to configured the same EAS to the UEs which satisfies the pre-condition | +|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| UE location:
- Cell ID: from XXX1 to XXX9
- DNAI: from XXA to XXE
- TAI
Area(s) of Interest
FQDN:
FQDN = ABC.com
UE Identifiers | Action 1: DNS message handling rules
- Local DNS server = 10.1.1.1
- ECS option = X.X.X.X
Action 2: EAS IP address
- 192.168.1.1 | + +## 6.18.2 Procedures + +### 6.18.2.1 EASDF-related procedure + +![Sequence diagram illustrating the EASDF related procedure to discover the same EAS. The diagram shows interactions between UE 1 - UE n, RAN, AMF, SMF, EASDF, UDM, and DNS server. The process starts with the SMF determining pre-conditions and selecting an EASDF. The SMF then subscribes to UE location events from the AMF. When a DNS query arrives from a UE, the SMF checks if pre-conditions are met. If so, it updates the EASDF context, sends a DNS query to the DNS server, receives a response, updates the EASDF context again, and finally sends the DNS response back to the UE. A dashed box indicates the 'UL CL insertion' step.](dfe74512a9c9fb620f72c9dbc22874aa_img.jpg) + +``` + +sequenceDiagram + participant UE as UE 1 - UE n + participant RAN + participant AMF + participant SMF + participant EASDF + participant UDM + participant DNS as DNS server + + Note over SMF: 0. Determines the pre-conditions of UEs should be configured the same EAS + Note over SMF: 0. Selection of the same EASDF to collections of UEs + UE->>SMF: 1. DNS Query + SMF->>EASDF: 2. Neasdf_DNSContext_Notify Request + EASDF-->>SMF: 3. Neasdf_DNSContext_Notify Response + SMF->>AMF: 4. Namf_EventExposure_Subscribe (UE location) + AMF-->>SMF: 5. Namf_EventExposure_Subscribe response + AMF->>SMF: 6. Namf_EventExposure_Notify + Note right of SMF: 7. SMF determines whether the pre-conditions are satisfied + SMF->>EASDF: 8. Neasdf_DNSContext_Update + EASDF-->>SMF: 9. Neasdf_DNSContext_Update Response + SMF->>DNS: 10. DNS query + DNS-->>SMF: 11. DNS response + SMF->>EASDF: 12. Neasdf_DNSContext_Notify Request + EASDF-->>SMF: 13. Neasdf_DNSContext_Notify Response + Note right of SMF: 14. UL CL insertion + SMF->>UE: 15. DNS response + +``` + +Sequence diagram illustrating the EASDF related procedure to discover the same EAS. The diagram shows interactions between UE 1 - UE n, RAN, AMF, SMF, EASDF, UDM, and DNS server. The process starts with the SMF determining pre-conditions and selecting an EASDF. The SMF then subscribes to UE location events from the AMF. When a DNS query arrives from a UE, the SMF checks if pre-conditions are met. If so, it updates the EASDF context, sends a DNS query to the DNS server, receives a response, updates the EASDF context again, and finally sends the DNS response back to the UE. A dashed box indicates the 'UL CL insertion' step. + +**Figure 6.18.2.1-1: EASDF related procedure to discover the same EAS** + +0. The AF may request the indication of EAS correlation and pre-conditions and the PCF creates the PCC rule correspondingly as described in clause 6.18.1. + +0. The SMF determines the pre-conditions of the UEs that should be configured with the same EAS. The pre-conditions may be a local policy or derived based on PCC rule received from PCF. The pre-conditions are defined below: + - The same FQDN in DNS query or range of FQDNs that can be resolved to a certain EAS IP address by DNS server. The same EAS can be mapped to one FQDNs or a group of FQDNs. Only the collections of the UEs request the same DNS query with these FQDNs, that the DNS server can provide the same EAS IP address(es). + - The collections of the UEs have the similar UE location, for example, the same UE location or the UE location in the Area of Interest. According to the UE location information or UE is IN/OUT of Area(s) of Interest, the 5GC can identify that these UEs should be served by the same EAS. The UE location includes: Cell ID, range of Cell ID, TAI lists, DNAI, range of DNAI, gNB ID, range of gNB ID, DNN, S-NSSAI. + +NOTE 1: If the pre-conditions are provided by AF and include location information, then the SMF is aware the UE location is in or out of the subscribed area of interest and sends notifications to the PCF, and the SMF determines which UE collection the UE belongs to, as described in clause 6.18.1. + +0. The 5GC can deliver the same DNS server IP address to these UEs that satisfy the pre-conditions, for example, the EASDF. +1. The UE sends a DNS Query message to the EASDF. +2. The same procedure as step 8 defined in figure 6.2.3.2.2-1 of TS 23.548 [3]. The EASDF provides the FQDN in DNS query to SMF. +3. The same procedure as step 9 defined in figure 6.2.3.2.2-1 of TS 23.548 [3]. +4. [Conditional] The SMF determines the Area(s) of Interest and subscribes to UE mobility event notification from the AMF (e.g. location reporting, UE moving into or out of Area of Interest), or the UE location from AMF by Namf\_EventExposure\_Subscribe (event ID = UE moving in or out of Area of Interest, UE location). The UE location information and UE presence IN or OUT of Area of Interest can be used by SMF to identify whether this UE should be configured with the same EAS. +5. [Conditional] The AMF responds to SMF. +6. [Conditional] The AMF notifies the SMF of UE(s) presence (IN, OUT, or UNKNOWN) in the Area(s) of Interest or the UE location information, including: TAI, Cell ID and etc. +7. SMF determines whether the UE is satisfied with the pre-conditions, according to UE location information and/or FQDN(s). If the UE location information is in the scope of UE location that defined in pre-conditions, and the FQDN is also in the scope of pre-defined scope, the SMF determines: + - use the same DNS server to resolve the FQDN. The DNS query should be treated with the same way, that applied to the same DNS message handling rules, e.g. the same DNS server address or information of EDNS Client Subnet option is indicated in the Forwarding Action. + - directly responds to the DNS query to UE. This way only applies to the EASDF. That if the SMF identifies that the UE's DNS query should be replied with the same EAS that other UEs use, the SMF can set the DNS message handling rules to EASDF to directly respond with the DNS query without having the DNS related procedure to DNS server, e.g. add a new action for Forwarding Action: forward the DNS response with specific EAS IP address to UE. The SMF should update the IP address of EAS in DNS message handling rule using the Neasdf\_DNSContext\_Update Service based on the timer retrieved by implementation. +- NOTE 2: For the load balance of service, the DNS server can reply different IP address of EAS. But, these IP addresses still stay in the same IP range or in the similar IP range. +8. The SMF updates the DNS message handling rule to guarantee the same EAS discovery for this UE. The SMF invokes Neasdf\_DNSContext\_Update Request (DNS message handling rules) to EASDF, and the DNS message handling rules are the same as pre-defined of other UEs. + +For Option A, the DNS handling rule includes the same corresponding IP address to be used to build the EDNS Client Subnet option. For Option B, the DNS handling rule includes corresponding Local DNS Server IP address which is also the same as other UEs. + +9-15. The same procedure from step 11 to step 19 as defined in figure 6.2.3.2.2-1 of TS 23.548 [3]. + +According to the enhancement from SMF, this UE can receive the same EAS IP address as other UEs which satisfies the pre-condition. + +## 6.18.2.2 Direct DNS response to UE + +![Sequence diagram for Direct DNS response to UE. Lifelines: UE 1 - UE n, RAN, AMF, SMF, EASDF, UDM, DNS server. The process involves determining pre-conditions, selecting an EASDF, sending a DNS query, subscribing to UE location, notifying the AMF, determining if pre-conditions are satisfied, updating the EASDF context, and finally sending the DNS response to the UE.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +``` + +sequenceDiagram + participant UE as UE 1 - UE n + participant RAN + participant AMF + participant SMF + participant EASDF + participant UDM + participant DNS as DNS server + + Note over UE, EASDF: 0. Determines the pre-conditions of UEs should be configured the same EAS + Note over UE, EASDF: 0. Selection of the same EASDF to collections of UEs + UE->>SMF: 1. DNS Query + SMF->>EASDF: 2. Neasdf_DNSContext_No tify Request + EASDF->>SMF: 3. Neasdf_DNSContext_No tify Response + SMF->>AMF: 4. Namf_EventExposure_S ubscribe (UE location) + AMF->>SMF: 5. Namf_EventExposure_S ubscribe response + SMF->>AMF: 6. Namf_EventExposure_N otify + Note right of SMF: 7. SMF determines whether the pre-conditions are satisfied + SMF->>EASDF: 8. Neasdf_DNSContext_Update + EASDF->>SMF: 9. Neasdf_DNSContext_Update Response + SMF->>UE: 10. DNS response + +``` + +Sequence diagram for Direct DNS response to UE. Lifelines: UE 1 - UE n, RAN, AMF, SMF, EASDF, UDM, DNS server. The process involves determining pre-conditions, selecting an EASDF, sending a DNS query, subscribing to UE location, notifying the AMF, determining if pre-conditions are satisfied, updating the EASDF context, and finally sending the DNS response to the UE. + +Figure 6.18.2.2-1: Direct DNS response to UE + +0-6. The same procedure as indicated in Figure 6.18.2.1-1 from step 0 to step 6. + +7. SMF determines whether the UE is satisfied with the pre-conditions, according to UE location information and/or FQDN. The SMF can also recover the DNAI, PSA ID, DNN, S-NSSAI of the UE or the UE's PDU Sessions. If the UE location information in the scope of pre-defined UE location, and the FQDN is also in the scope of pre-defined scope, the SMF determines to discover the same EAS to this UE as other UEs in group. SMF decides to have a direct DNS response to the UE. + +8-9. The same procedure as indicated in Figure 6.18.2.1-1 from step 8 to step 9. But SMF invokes Neasdf\_DNSContext\_Update Request (DNS message handling rules) to EASDF to directly respond to the UE DNS query with the same EAS IP address that other UEs are served. The SMF should update the IP address of EAS in DNS message handling rule using the Neasdf\_DNSContext\_Update Service based on the timer retrieved by implementation. + +10. The EASDF sends the DNS Response(s) to the UE with the same EAS IP address that other UEs are served. + +### 6.18.2.3 EAS Discovery Procedure with Local DNS Server/Resolver + +![Sequence diagram of the EAS Discovery Procedure with Local DNS Server/Resolver. The diagram shows five steps: 1. UE sends a PDU Session Establishment Request to SMF. 2. SMF determines DNAI and selects PSA UPF, and determines DNS server(s). 3. SMF selects and inserts UL CL/BP (optional). 4. SMF sends a PDU Session Establishment Accept to UE. 5. SMF retrieves EAS IP address from the DNS Server and sends it to the UE.](b87818c8505328b198d035761bbc3f2d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant UPF_UL as UPF (UL CL/BP) + participant UPF_PSA as UPF (PSA) + participant DNS as DNS Server + + Note right of SMF: 2. SMF determines DNAI and selects PSA UPF, and determines DNS server(s) + Note right of SMF: 3. SMF selects and inserts UL CL/BP + + UE->>SMF: 1. PDU Session Establishment Request + SMF-->>UPF_PSA: + SMF-->>UPF_UL: + SMF-->>UE: 4. PDU Session Establishment Accept + Note right of SMF: 5. Retrieve EAS IP address and send it UE + SMF->>DNS: + DNS-->>SMF: + SMF-->>UE: + +``` + +Sequence diagram of the EAS Discovery Procedure with Local DNS Server/Resolver. The diagram shows five steps: 1. UE sends a PDU Session Establishment Request to SMF. 2. SMF determines DNAI and selects PSA UPF, and determines DNS server(s). 3. SMF selects and inserts UL CL/BP (optional). 4. SMF sends a PDU Session Establishment Accept to UE. 5. SMF retrieves EAS IP address from the DNS Server and sends it to the UE. + +**Figure 6.18.2.3-1: EAS Discovery Procedure with Local DNS Server/Resolver** + +1. The UE sends a PDU Session establishment request to SMF. +2. SMF determines whether the UE is satisfied with the pre-conditions, according to UE location information and FQDN. The SMF can also recover the DNAI, PSA ID, DNN, S-NSSAI of the UE or the UE's PDU Sessions. If the UE location information in the scope of pre-defined UE location, and the FQDN is also in the scope of pre-defined scope, the SMF determines to discover the same EAS to this UE as other UEs in group. The SMF determines the DNAI and selects corresponding PSA UPF serves the DNAI, and determines DNS server(s) to ensure a dynamic group uses the same EAS and/or same DNAI. +3. Optionally, the SMF selects and inserts UL-CL/BP. The SMF configures the UL-CL/BP for DNS Query handling. +4. The SMF includes the IP address of Local DNS Server in PDU Session Establishment Accept message. +5. The EAS information (e.g. EAS IP address) is resolved by Local DNS Server and sent the UE. + +### 6.18.3 Impacts on services, entities and interfaces + +#### SMF: + +- determines the pre-conditions of whether the collections of the UE should be configured with the same EAS. +- determines whether the UE is satisfied with the pre-conditions, according to UE location information and FQDN. +- decides to have a direct DNS response to the UE or configure the same DNS message handling rule to this UE DNS query, according to the configurations in the pre-conditions; +- updates the IP address of EAS in DNS message handling rule using the Neasdf\_DNSContext\_Update Service based on the timer retrieved by implementation. + +#### EASDF: + +- directly responds to the UE DNS query with the EAS IP address that other UEs are served. + +#### AF: + +- sends the indication of EAS correlation. + +#### PCF: + +- creates PCC rule based on information provided in AF request. + +## 6.19 Solution 19 (KI#4): Influencing UPF and EAS (re)location for collections of UEs + +### 6.19.1 Introduction + +This solution aims to address the technical requirements related to key issue #4. In particular, it proposes for certain Edge Application use case e.g. all users playing a certain online game and registered to a particular EAS, or all UEs in a platoon, how these UEs collectively form an ad hoc and dynamic group, how to identify such group, how to handle coordination of the UPF(s) and EAS (re)location for the UEs belonging to the same group. + +### 6.19.2 Functional Description + +The following are the main principles of the solution: + +- Application Function creates an ad hoc group of collection of UEs specific to specific use cases and based on its respective criteria, for example: all Users served by the same EAS that hosts an online gaming application, and ad hoc group of UEs of a Platoon.. +- Application Function creates an ad hoc group of collection of UEs, and provides to 5GC, either directly or via NEF, the necessary group specific information, together with (external) group ID. +- NEF performs AF request authorization and provides necessary mappings, and configures UDM with the ad hoc group information. + +### 6.19.3 Procedure + +#### 6.19.3.1 AF provisioning ad-hoc group information + +The figure 6.19.3.1-1 below provides a detailed call flow on ad hoc group and group specific attributes provisioning by AF. + +![Sequence diagram showing AF provisioning ad-hoc group information. The diagram involves five lifelines: AF, NEF, UDM, UDR, and SMF/AMF. The sequence starts with the AF sending a Nnef_ParameterProvision_Create/Update/Delete request to the NEF. The NEF then performs an authorization and mapping to internal IDs. Next, the NEF sends a Nudm_ParameterProvision_Create/Update/Delete request to the UDM. The UDM sends a Nudr_DM_Query to the UDR, which responds with a Nudr_DM_Update. The UDM then sends a Nudm_ParameterProvision_Create/Update/Delete response to the NEF. Finally, the NEF sends a Nnef_ParameterProvision_Create/Update/Delete response to the AF. A dashed line indicates a Nudm_SDM_Notification Notify from the UDM to the SMF/AMF.](99781d878388c3e0f359b1d6ce14119c_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDM + participant UDR + participant SMF/AMF + + Note right of NEF: 2a. Authorization, mapping to Internal IDs + AF->>NEF: 1. Nnef_ParameterProvision_Create/Update/Delete request (External Group ID, Group Type, Group members) + NEF->>UDM: 2b. Nudm_ParameterProvision_Create/Update/Delete request (Group ID, Group Type, Group members) + UDM->>UDR: 3. Nudr_DM_Query + UDR-->>UDM: 4. Nudr_DM_Update + UDM->>NEF: 5. Nudm_ParameterProvision_Create/Update/Delete response + NEF->>AF: 6. Nnef_ParameterProvision_Create/Update/Delete response + UDM-->>SMF/AMF: 7. Nudm_SDM_Notification Notify + +``` + +Sequence diagram showing AF provisioning ad-hoc group information. The diagram involves five lifelines: AF, NEF, UDM, UDR, and SMF/AMF. The sequence starts with the AF sending a Nnef\_ParameterProvision\_Create/Update/Delete request to the NEF. The NEF then performs an authorization and mapping to internal IDs. Next, the NEF sends a Nudm\_ParameterProvision\_Create/Update/Delete request to the UDM. The UDM sends a Nudr\_DM\_Query to the UDR, which responds with a Nudr\_DM\_Update. The UDM then sends a Nudm\_ParameterProvision\_Create/Update/Delete response to the NEF. Finally, the NEF sends a Nnef\_ParameterProvision\_Create/Update/Delete response to the AF. A dashed line indicates a Nudm\_SDM\_Notification Notify from the UDM to the SMF/AMF. + +Figure 6.19.3.1-1: AF Provisioning Ad-hoc Group Information + +1. Application Function configures an ad hoc dynamic group of a collection of UEs. These collection of UEs are based on common use case or application. e.g. all users registered on a particular gaming server (EAS) or all UEs in a platoon. AF assigns an (external) Group ID to this collection of UEs. AF provisions this group information to 5GC either directly or via NEF and provides required details including: (external) group ID, Group Type (this is to differentiate with static groups based on user subscriptions), collection of UEs IDs forming the group, i.e. list of group members, and group property or attributes such as all users to be served by the same EAS. + +Alternatively, AF may use new API e.g. Nnef\_GroupParameterProvision\_Create/update/delete to provision these information. + +Group Type indicates specific ad hoc groups e.g. an ad hoc group specific to platooning or an ad hoc group of UEs playing online game and registered to a particular gaming server/EAS. Group Type may be used by NEF to translate group specific 5GC internal requirements and store in the UDM/UDR as group attribute information, for example: + +- all group members to be served by same SMF. This may be based on indication from AF such as Specific Application e.g. platooning and/or based on preconfigured logic of the NEF; + - same PSA-UPF and DNAI for all UEs in the group. This may be based on indication from AF such as same EAS, or Specific Application e.g. online gaming or based on preconfigured logic on NEF. +2. NEF after authorizing the AF request, creates or updates these information in UDM. It translates AF provided information into corresponding 5GC internal information such as external Group ID into an internal group ID. The Group Attributes are group specific information such as indication to use same EAS for all group members, or same PSA UPF. + +NEF stores (or updates) these in UDM. + +As specified in clause 4.15.6.2 of TS 23.502 [9], and clause 6.5.6.2.6 of TS 29.503 [18], UDM/UDR assigns/allocates a unique Internal Group ID. + +- 3-4. UDM uses Nudr\_DM\_Query/Update to UDR. UDR stores the data as part of the Group subscription data and responds with Nudr\_DM\_Create/Update/Delete Response message. + +**Table 6.19.3-1: Ad hoc group data** + +| Parameters | Description | +|------------------|------------------------------------------------------------------------------------------------------------------------------------| +| S-NSSAI | (Optional) S-NSSAI for the ad hoc group | +| DNN | (Optional) DNN for the ad hoc group | +| Group Type | Indicates specific ad hoc group e.g. platooning, online gaming, etc. | +| EAS ID | (Optional) Edge Application Server ID e.g. application server instance where users of the online gaming application are registered | +| Group Attributes | Group type specific properties | + +**Table 6.19.3-2: Ad hoc group membership management parameters** + +| Parameters | Description | +|-------------------|-----------------------------------------------------------------| +| External Group ID | An identifier of the ad hoc group | +| List of GPSI | List of ad hoc group members, each member is identified by GPSI | + +5. UDM responds with Nudm\_ParameterProvision\_Create/Update/Delete Response. +6. NEF responds to AF with Nnef\_ParameterProvision\_Create/Update/Delete Response. +7. UDM notifies to the subscribed Network Function e.g. AMF and SMF, of the Group subscription data via Nudm\_SDM\_Notification Notify message. The SMF stores the received parameters and associates them with a PDU Session based on the DNN and S-NSSAI included in the message from UDM. + +The group information is used e.g. by SMF to ensure collective and common behaviour and treatment to the member UEs of the ad hoc group. For example, all the UEs of a particular ad hoc group are (re-)located in the same EAS instance as in solution 6.37. + +### 6.19.3.2 Group members served by same SMF + +For certain group applications e.g. platooning, network can improve and optimize services and possibly reduce management/signalling overhead by ensuring same SMF (or SMF instances belonging to the same SMF set) serves all the group member UEs. This SMF then provides common and coordinated treatment of the group member UEs. + +Below figure 6.19.3.2-1 provides details to allow the serving SMF to register itself in the UDM/UDR updating the particular group information. + +![Sequence diagram showing the serving SMF registering to the UDM/UDR. The diagram involves six entities: UE, RAN, AMF, SMF, UDM, and UDR. The sequence starts with a PDU Session establishment Request from UE to AMF. A dashed box indicates the PDU Session establishment procedure as per TS 23.502. Following this, the SMF sends a Group Info update (Group ID, Serving SMF ID (Or SMF Set ID)) to the UDM. The UDM then performs a Nudr_DM_Query to the UDR, followed by a Nudr_DM_Update from the UDR back to the UDM. A box labeled '3a. Stores/Updates together with Group Attributes: Serving SMF Identity or SMF Set ID' is shown within the UDM's processing.](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant UDM + participant UDR + + Note right of SMF: 3a. Stores/Updates together with Group Attributes: Serving SMF Identity or SMF Set ID + + UE->>AMF: 1. PDU Session establishment Request + Note over AMF, UDM: 2. PDU Session establishment procedure as per TS 23.502 + SMF->>UDM: 3. Group Info update (Group ID, Serving SMF ID (Or SMF Set ID)) + UDM->>UDR: 4. Nudr_DM_Query + UDR-->>UDM: 5. Nudr_DM_Update + +``` + +Sequence diagram showing the serving SMF registering to the UDM/UDR. The diagram involves six entities: UE, RAN, AMF, SMF, UDM, and UDR. The sequence starts with a PDU Session establishment Request from UE to AMF. A dashed box indicates the PDU Session establishment procedure as per TS 23.502. Following this, the SMF sends a Group Info update (Group ID, Serving SMF ID (Or SMF Set ID)) to the UDM. The UDM then performs a Nudr\_DM\_Query to the UDR, followed by a Nudr\_DM\_Update from the UDR back to the UDM. A box labeled '3a. Stores/Updates together with Group Attributes: Serving SMF Identity or SMF Set ID' is shown within the UDM's processing. + +Figure 6.19.3.2-1: Serving SMF registers to the UDM/UDR + +- 1-2. Same as in TS 23.502 [9]. +3. SMF registers SMF ID and/or SMF Set ID (serving the group), to UDM/UDR and/or to NEF. + - SMF uses Nudm\_UECM\_Registration API or a new message/API to register SMF ID and/or SMF set ID to the particular ad hoc group ID. + - Alternatively, SMF may update its SMF ID and/or SMF set ID for the particular ad hoc group to UDR via NEF. +- 4-5. UDM may further store this information in UDR by Nudr\_DM\_Update, thus updating ad hoc group attributes to indicate the serving SMF for the particular Group. + +## 6.19.4 Impacts on services, entities and interfaces + +AF: + +- provisions ad hoc group information to the 5GC. + +NEF: + +- authorizes, translates and stores ad hoc group information to UDM/UDR. + +SMF: + +- subscribes to the ad hoc group subscription data, and also updates its ID in the group information stored in the UDM/UDR. + +## 6.20 Solution 20 (KI#5): Global EASDF + +### 6.20.1 Description + +This solution addresses KI#5: GSMA OPG impacts and improvements for EHE operated by separate party. + +In this solution, the UE uses a predefined EASDF that is global between operators. For example, GSMA could host this with the URL: + +.mcc.pub.3gppnetwork.org> + +Each operator that wants to support separate party's EHE into their network will then add these EHEs entry points into the DNS entry owned by themselves in the Global EASDF. There are two alternatives to do this, either they add the + +EAS entry point directly into the Global EASDF. The other alternative is to add the entry point to another EASDF into the Global EASDF. With the second alternative then the UE shall now use that received IP address as EASDF to discover the appropriate EAS according to existing procedures. Since the Global EASDF is based on standard DNS infrastructure that allows an operator to specify which order the UE shall select EAS/EASDF in the different separate party's operated EHEs. If we allow both alternatives, then it is up to each operator to decide which method they want to use as long as we specify that the UE shall support both methods. The second alternative with discovering another EASDF allows more static configuration in the Global EASDF. + +## 6.20.2 Procedures + +### 6.20.2.1 Global EASDF + +![Sequence diagram for Global EASDF procedures. The diagram shows interactions between a UE, HPLMN Domain (PSA UPF, SMF), Separate Party (3rd party EASDF, 3rd party EAS), and GSMA (Global EASDF). It details two options for EASDF discovery after a PDU session establishment.](86bd357c573c9696393f5bde4d4cce4f_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph HPLMN_Domain [HPLMN Domain] + PSA_UPF[PSA UPF] + SMF[SMF] + end + subgraph Separate_Party [Separate Party] + 3rd_party_EASDF[3rd party EASDF] + 3rd_party_EAS[3rd party EAS] + end + subgraph GSMA [GSMA] + Global_EASDF[Global EASDF] + end + + Note left of UE: 1 PDU session establishment + Note right of UE: Option A + UE->>Global_EASDF: 2 EASDF Discovery (DNS Request) + Global_EASDF-->>UE: 3 DNS Response + UE->>3rd_party_EASDF: 4 Local EAS Discovery (DNS Request) + 3rd_party_EASDF-->>UE: 5 DNS Response + Note right of UE: Option B + UE->>Global_EASDF: 6 EAS Discovery (DNS Request) + Global_EASDF-->>UE: 7 DNS Response + Note left of UE: 8 Application session to the EAS + +``` + +Sequence diagram for Global EASDF procedures. The diagram shows interactions between a UE, HPLMN Domain (PSA UPF, SMF), Separate Party (3rd party EASDF, 3rd party EAS), and GSMA (Global EASDF). It details two options for EASDF discovery after a PDU session establishment. + +Figure 6.20.2-1: Global EASDF + +0. Pre-requisites: HPLMN has configured the Global EASDF with appropriate entries for all separate party's EASDF and/or their EAS they want to enable in their network. +1. Existing PDU Session establishment procedure according to step 1 in clause 6.2.3.2.2 of TS 23.548 [3]. +2. For Option A, the UE performs a DNS query to the Global EASDF. Since this is a public FQDN to the Global EASDF, the UE may use any locally configured DNS Server that in turn will use next DNS server in the DNS hierarchy until it goes to the Global EASDF. + +NOTE 1: The unique identifier to use for querying another EASDF will be specified during the normative phase. + +NOTE 2: The structure of the DNS Query is the same as defined in solution#09 in clause 6.9. + +3. The Global EASDF responds with the IP address of the EASDF that the UE should use in next step. +4. The UE performs EAS Discovery, as specified in step 7 in clause 6.2.3.2.2 of TS 23.548 [3] except that it uses the IP address received in step 3 as DNS server for the DNS query instead of the one received during PDU Session establishment procedure. +5. EASDF sends the DNS Response to the UE, as specified in step 19 in clause 6.2.3.2.2 of TS 23.548 [3]. +6. For Option B, The UE performs EAS Discovery, as specified in step 7 in clause 6.2.3.2.2 of TS 23.548 [3] and uses the IP address of the Global EASDF instead of the one received during PDU Session establishment procedure. +7. EASDF sends the DNS Response to the UE, as specified in step 19 in clause 6.2.3.2.2 of TS 23.548 [3]. +8. The UE application starts to utilize the provided EAS. + +## 6.20.3 Impacts on services, entities and interfaces + +UE: + +- configured with the FQDN for the Global EASDF. The UE allows to perform a EASDF Discovery from the EASDF address that the UE received from the Global EASDF. + +Global EASDF: + +- acts as a DNS Server and responds to the DNS Queries from the UE. + +## 6.21 Solution 21 (KI#5): EAS Deployment information differentiated by PLMN ID + +### 6.21.1 Introduction + +This solution proposes an EAS discovery method for the scenario described in clause 2.1.5 of GSMA OPG.02 [5] that an OP deploys applications provided by Application Providers on another OP. This solution focuses on the scenario that the OPs are different PLMNs. In this case, the problem is to ensure the EAS deployed by HPLMN in VPLMN's EHE should only be discovered and accessed by the UE of the HPLMN roaming to the VPLMN and using LBO PDU Session. This solution introduces how to handle the DNS requests to ensure an EAS deployed by a PLMN can only be accessed by the UE of same PLMN. + +This solution corresponds to KI#5. + +### 6.21.2 Functional Description + +This solution is based on the following principles: + +- The EAS Deployment information provided by AF contains the EAS provider's ID (i.e. PLMN ID) to differentiate the EAS deployment information of different PLMNs. Different EAS providers (PLMNs) may use different DNS servers (e.g. C-DNS server or Local DNS server) to discover the EAS deployed by the PLMNs. +- During the PDU Session Establishment procedure, the SMF selects the proper PLMN's EAS Deployment Information based on UE's HPLMN ID and then generates corresponding DNS message handling rule to handle DNS messages related to the roaming UE. + +### 6.21.3 Procedures + +The EAS Deployment Information Provision procedure reuses the procedure defined in clause 6.2.3.4.2 of TS 23.548 [3]. The enhancement is that the EAS Deployment information provided by AF in step 1 includes PLMN ID to differentiate EAS deployment information of different PLMNs. EAS deployment information of different PLMNs may contain different DNS servers (e.g. C-DNS server or Local DNS server) or different ECS options. + +The EAS Deployment Information Management in the SMF reuses the procedure defined in clause 6.2.3.4.3 of TS 23.548 [3]. + +The EAS discovery procedure with EASDF defined in clause 6.2.3.2.2 of TS 23.548 [3] is reused to discover the EAS(s) deployed by different providers. The enhancement is that the during the PDU Session Establishment procedure, the SMF selects the proper provider based on HPLMN ID. The SMF queries the UDR via NEF with the HPLMN ID to get the EAS Deployment information and configures the EASDF with DNS message handling rules to handle DNS messages related to the UE. Then the following steps in clause 6.2.3.2.2 of TS 23.548 [3] are reused for DNS queries and UL-CL/BP insertion. + +### 6.21.4 Impacts on services, entities and interfaces + +AF: + +- supports sending EAS Deployment information with PLMN ID to differentiate the EAS deployment information of different providers. + +SMF: + +- supports selecting proper provider based on roaming UE's HPLMN ID and configures the EASDF according to the EAS Deployment information of the HPLMN. + +## 6.22 Solution 22 (KI#5): EAS discovery for Edge Node Sharing + +### 6.22.1 Introduction + +This solution addresses Key Issue #5 and allows the discovery of an Edge Application Server (EAS) in case of Edge Node Sharing. In this solution, it is assumed that the EAS is hosted by a different PLMN than the PLMN that is serving the UE. + +NOTE: It is assumed that the EAS is hosted by a different PLMN than the PLMN serving the UE, and that the two PLMNs have IP connection at the edge area. + +### 6.22.2 Functional description + +#### 6.22.2.0 Option 0: SMF configuration + +This solution is based on the Rel-17 EAS based discovery procedures with the assumption that the SMFs of each PLMN Sharing Edge Node need to be configured with the DNAI values associated to the EAS' hosted by the other Operators. More in details: + +- the SMF needs to know the EAS deployment information of the EAS running on other PLMN's edge infrastructure e.g. IP address range(s)/FQDN(s). + +For example, if the EAS is running in MNO 2's PLMN#2, when the EAS discovery is triggered the EASDF in MNO 1's PLMN#1 will receive the DNS response from the DNS server knowing the EAS' address and will forward the EAS' address to the SMF in PLMN#1. + +- At this point, after the SMF gets the IP address of EAS running in PLMN#2, in order to know that the EAS is instantiated in PLMN#2's edge infrastructure, it is required that the SMF knows the mapping between the PLMN ID of the PLMN hosting the EAS and the corresponding IP address received as a result of the DNS query so that the SMF can steer the user plane path towards the PLMN#2's domain. This may require an update of the SMF each time an EAS is added or removed. + +#### 6.22.2.1 Option 1: Shared EASDF + +This option is based on the concept of shared EAS Discovery Function (shared EASDF), which is a new network entity shared among multiple operators and used to support the discovery of EAS for shared Edge Nodes. + +![Figure 6.22.2.1-1: Architecture with deployed Shared EASDF. The diagram shows two network slices separated by a dashed line. The top slice (MNO2's PLMN, Anchor PLMN) includes an EDN with EAS, a Shared EASDF (yellow box), and standard 5G core elements (AMF, SMF, PCF, AF, UPF, DN). The bottom slice (MNO1's PLMN) includes a UE, (R)AN, UPF, DN, AMF, sSMF, PCF, AF, and sEASDF. Red lines indicate connections between the sEASDF and the Shared EASDF via the sSMF, and between the Shared EASDF and the EDN via the SMF of the anchor PLMN.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +Figure 6.22.2.1-1: Architecture with deployed Shared EASDF. The diagram shows two network slices separated by a dashed line. The top slice (MNO2's PLMN, Anchor PLMN) includes an EDN with EAS, a Shared EASDF (yellow box), and standard 5G core elements (AMF, SMF, PCF, AF, UPF, DN). The bottom slice (MNO1's PLMN) includes a UE, (R)AN, UPF, DN, AMF, sSMF, PCF, AF, and sEASDF. Red lines indicate connections between the sEASDF and the Shared EASDF via the sSMF, and between the Shared EASDF and the EDN via the SMF of the anchor PLMN. + +**Figure 6.22.2.1-1: Architecture with deployed Shared EASDF** + +The Shared EASDF is a new network entity deployed in the core network and shared among the PLMNs of the MNOs that support Edge Node Sharing. The shared EASDF is hosted by one PLMN. The PLMN hosting the shared EASDF is the anchor PLMN. The communication between other PLMNs and the shared EASDF takes place via the serving EASDF (sEASDF) and the serving SMF (sSMF), that is via the EASDF and the SMF of the PLMN serving the UE. The sSMF handles the DNS context on the shared EASDF in a similar way as for the sEASDF, i.e. via the Neasdf\_DNSContext\_Create service. + +The shared EASDF stores EAS deployment information such as EAS address hosted by other PLMNs. An operator needs to update its EAS information in the shared EASDF any time a change is applied (e.g. an EAS is added/modified/removed, or an MNO joins or leaves sharing of Edge Node). + +## 6.22.2.2 Option 2: Per-PLMN EASDFs + +This solution option is based on the communication between the EASDFs of the different PLMNs of the MNOs that support sharing of Edge Nodes. The EASDF of a PLMN manages information for EAS' that are hosted by the Edge Data Network of that PLMN, and the EASDF of a PLMN can interact with other PLMNs' EASDFs to support Edge Node Sharing. + +### Architecture + +![Figure 6.22.2.2-1: Architecture with per-PLMN EASDF. The diagram shows two PLMNs, MNO1's PLMN and MNO2's PLMN, separated by a dashed line. In MNO1's PLMN (bottom), a UE connects to an (R)AN, which connects to an AMF via N1 and N2 interfaces. The AMF connects to a UPF via N3 and N9 interfaces. The UPF connects to a DN via N6 and N9 interfaces. The AMF also connects to an sSMF via N11 and N14 interfaces. The sSMF connects to a PCF via N7 and N15 interfaces. The PCF connects to an AF via N5 interface. The sSMF also connects to an sEASDF via N4 interface. In MNO2's PLMN (top), an (R)AN connects to an AMF via N2 interface. The AMF connects to a UPF via N3 and N9 interfaces. The UPF connects to a DN via N6 and N9 interfaces. The AMF also connects to an SMF via N11 and N14 interfaces. The SMF connects to a PCF via N7 and N15 interfaces. The PCF connects to an AF via N5 interface. The SMF also connects to a pEASDF via N4 interface. Red lines indicate connections between the sEASDF and pEASDF, and between the sEASDF and the DN in MNO2's PLMN. The DN in MNO2's PLMN contains an EAS (Edge Application Server).](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +Figure 6.22.2.2-1: Architecture with per-PLMN EASDF. The diagram shows two PLMNs, MNO1's PLMN and MNO2's PLMN, separated by a dashed line. In MNO1's PLMN (bottom), a UE connects to an (R)AN, which connects to an AMF via N1 and N2 interfaces. The AMF connects to a UPF via N3 and N9 interfaces. The UPF connects to a DN via N6 and N9 interfaces. The AMF also connects to an sSMF via N11 and N14 interfaces. The sSMF connects to a PCF via N7 and N15 interfaces. The PCF connects to an AF via N5 interface. The sSMF also connects to an sEASDF via N4 interface. In MNO2's PLMN (top), an (R)AN connects to an AMF via N2 interface. The AMF connects to a UPF via N3 and N9 interfaces. The UPF connects to a DN via N6 and N9 interfaces. The AMF also connects to an SMF via N11 and N14 interfaces. The SMF connects to a PCF via N7 and N15 interfaces. The PCF connects to an AF via N5 interface. The SMF also connects to a pEASDF via N4 interface. Red lines indicate connections between the sEASDF and pEASDF, and between the sEASDF and the DN in MNO2's PLMN. The DN in MNO2's PLMN contains an EAS (Edge Application Server). + +**Figure 6.22.2.2-1: Architecture with per-PLMN EASDF** + +In the figure above: + +- serving EASDF (sEASDF) and the serving SMF (sSMF) are, respectively, the EASDF and the SMF of the PLMN that is currently serving the UE; +- partner EASDF (pEASDF) is the EASDF of the partner PLMN which hosts the Edge Application Server whose service is desired. + +#### EAS Deployment Information extension + +By using the Nnef\_EASDeployment APIs, the AF provides to the CN the EAS Deployment Information (see table 6.2.3.4-1 of TS 23.548 [3]). Such information needs to be associated to the additional PLMN ID(s) and FQDN filter/DNS server address filter(s) to help the SMF identify, during EAS discovery, where the EAS is located. Table 6.22.2.2-1 shows the filtering information used to select the proper EAS and table 6.22.2.2-2 shows some examples of FQDN/DNS server address filter(s). + +**Table 6.22.2.2-1: NEW: Filtering table for EAS Deployment Information** + +| Parameters | Description | +|------------------|--------------------------------------------------------------| +| PLMN ID(s) – NEW | Used to identify in which PLMN the EAS is located [optional] | +| Filter(s) – NEW | Used to identify where the EAS is located [optional] | + +**Table 6.22.2.2-2: NEW: Examples of Filters for EAS Deployment Information** + +| DNS query content or DNS resolution | DNS server address or FQDN filter | Result | +|-------------------------------------|-----------------------------------|-----------------------------------------------------------------------------------------| +| MNO1.xrgaming.edge | MNO1.* | Matched, select EASDF of MNO1 | +| Battle.gamingX.edge.com | *.gamingX.edge.* | Matched, serving MNO knows in which MNO 'gamingX' is running, so select the MNO's EASDF | +| 11.123.45.22 | 11.123.* | Matched, selected the EASDF of MNO1, which is corresponding to 11.123.* | + +## EAS Discovery + +The EAS discovery is based on the existing EAS discovery procedures described in TS 23.548 [3], with the following changes: + +- provisioning of EAS deployment information to 5GS: + - For each of its EASs, the application service provider (via the AF) provides each PLMN Sharing Edge Nodes with the EAS deployment information with PLMN ID, DNAI, and (list of) FQDNs necessary to discover the EAS. Such information is stored in the UDR following the EAS Deployment Information Provision from AF via NEF procedure (clause 6.2.3.4.2 of TS 23.548 [3]). + - The SMF retrieves the EAS deployment information from the UDR (clause 6.2.3.4.3 of TS 23.548 [3]) and provides the following pieces of information to the EASDF (clause 6.2.3.4.4 of TS 23.548 [3]): + - a) FQDN filter: the list of filters regarding FQDN in the DNS query from the UE; + - b) DNS server address filter: the list of filters regarding DNS server address in the DNS query from the UE; + - c) PLMN ID associated with the FQDN filter or DNS server address; + - d) Action: DNS query forwarding to the target pEASDF, reporting to the SMF. +- EAS discovery: + - At EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]), the sEASDF determines the target pEASDF associated with the PLMN ID, if the received DNS query (from the UE) meets the following conditions: + - the FQDN in the DNS query matches with the configured FQDN filter associated with the DNAI/PLMN ID; + - the DNS server address in the query matches with the configured DNS address filter with the DNAI/PLMN ID. + - Based on the indication by the sSMF, the sEASDF forwards the query to target pEASDF. + - Target pEASDF replies with the specific DNAI/PLMN ID result. + - The result is reported to the sSMF. + +## 6.22.3 Procedures + +### 6.22.3.0 Option 0: SMF configuration + +This option re-uses the EAS discovery procedure defined in clause 6.2.3.2.2 of TS 23.548 [3]. + +### 6.22.3.1 Option 1: Shared EASDF + +Figure 6.22.3.1-1 describes a modified EAS discovery procedure based on the Rel-17 procedure described in TS 23.548 [3]. + +![Sequence diagram for Modified EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]) for Option 1. The diagram shows interactions between UE, sSMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, sEASDF, Shared EASDF, and DNS Server. It is divided into DNSContext Creation Procedure and DNSContext Update Procedure. The DNSContext Creation Procedure includes steps 1-4. The DNSContext Update Procedure includes steps 5-9. A new step 9a (Selects Shared EASDF) is added. Steps 9b/c (Neasdf_DNSContext_Create Request/Request) are highlighted in red. Steps 10-11 (Neasdf_DNSContext_Update Request/Response) are also highlighted in red. Steps 12-13 (DNS query/Response) are highlighted in red. Steps 14-15 (Neasdf_DNSContext_Notify Request/Response) are highlighted in red. Step 16 (ULCL/BP insertion) is highlighted in red. Steps 17-18 (Neasdf_DNSContext_Update Request/Response) are highlighted in red. Step 19 (DNS response) is highlighted in red.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant sSMF + participant UPF_ULCL_BP as UPF ULCL/BP + participant UPF_L_PSA as UPF L-PSA + participant UPF_PSA as UPF PSA + participant sEASDF + participant Shared_EASDF as Shared EASDF + participant DNS_Server as DNS Server + + Note left of UE: DNSContext Creation Procedure + Note left of UE: 1. PDU Session Establishment Procedure + Note left of sSMF: 2. Select EASDF + sSMF->>sEASDF: 3. Neasdf_DNSContext_Create Request + sEASDF-->>sSMF: 4. Neasdf_DNSContext_Create Response + + Note left of UE: DNSContext Update Procedure + sSMF->>sEASDF: 5. Neasdf_DNSContext_Update Request + sEASDF-->>sSMF: 6. Neasdf_DNSContext_Update Response + + Note left of sSMF: 7. DNS Query + sSMF->>sEASDF: 8. Neasdf_DNSContext_Notify Request + sEASDF-->>sSMF: 9. Neasdf_DNSContext_Notify Response + + Note left of sSMF: 9a. Selects Shared EASDF + sSMF->>Shared_EASDF: 9b/c. Neasdf_DNSContext_Create Request/Request + Shared_EASDF-->>sSMF: 10. Neasdf_DNSContext_Update Request + sSMF-->>Shared_EASDF: 11. Neasdf_DNSContext_Update Response + + Note left of Shared_EASDF: 11a. DNS query + Shared_EASDF->>DNS_Server: 12. DNS query + DNS_Server-->>Shared_EASDF: 13. DNS Response + Note left of Shared_EASDF: 13a. DNS Response + Shared_EASDF-->>sSMF: 14. Neasdf_DNSContext_Notify Request + sSMF-->>Shared_EASDF: 15. Neasdf_DNSContext_Notify Response + + Note left of sSMF: 16. ULCL/BP insertion + sSMF->>sEASDF: 17. Neasdf_DNSContext_Update Request + sEASDF-->>sSMF: 18. Neasdf_DNSContext_Update Response + sSMF-->>UE: 19. DNS response + +``` + +Sequence diagram for Modified EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]) for Option 1. The diagram shows interactions between UE, sSMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, sEASDF, Shared EASDF, and DNS Server. It is divided into DNSContext Creation Procedure and DNSContext Update Procedure. The DNSContext Creation Procedure includes steps 1-4. The DNSContext Update Procedure includes steps 5-9. A new step 9a (Selects Shared EASDF) is added. Steps 9b/c (Neasdf\_DNSContext\_Create Request/Request) are highlighted in red. Steps 10-11 (Neasdf\_DNSContext\_Update Request/Response) are also highlighted in red. Steps 12-13 (DNS query/Response) are highlighted in red. Steps 14-15 (Neasdf\_DNSContext\_Notify Request/Response) are highlighted in red. Step 16 (ULCL/BP insertion) is highlighted in red. Steps 17-18 (Neasdf\_DNSContext\_Update Request/Response) are highlighted in red. Step 19 (DNS response) is highlighted in red. + +Figure 6.22.3.1-1: Modified EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]) for Option 1 + +The procedure is based on the EAS discovery procedure defined in clause 6.2.3.2.2 of TS 23.548 [3], with the following changes: + +- new step 9a: based on the DNS message report sent by the sEASDF in steps 8/9, the SMF selects the shared EASDF. +- new step 9b/c: the sSMF creates the DNS context in the shared EASDF. + +NOTE 1: In case of IPv4, it is assumed that the SMF knows the UE's public IP address. This can be done based on interaction with the NAT server and/or on implementation specific ways. + +- steps 10/11: the sSMF instructs the sEASDF to forward the DNS query to the shared EASDF. The sSMF provides to the serving EASDF the FQDN filter (e.g. FQDN ranges) to be reported. The FQDN filter indicates that the shared EASDF needs to be contacted to resolve the DNS query. + +- new step 11a: the sEASDF forwards the DNS query to the shared EASDF. + +NOTE 2: While the sEASDF matches the DNS query with the DNS context for the UE (as per Rel-17), the Shared EASDF does not need to do that because it uses the DNS ECS option to select the most appropriate EAS. In that sense the Shared EASDF behaves as a regular DNS server. The need to have a DNS UE context in the Shared EASDF for UE accessing from partner PLMNs can be discussed in the normative phase. + +- new step 13a: the shared EASDF resolves the DNS query and sends the DNS reply to the sEASDF. + +NOTE 2: Alternatively to steps 11a/13a, the DNS query can be forwarded by the sEASDF to the shared EASDF via the SMF. + +### 6.22.3.2 Option 2: Per-PLMN EASDFs + +Figure 6.22.3.2-1 describes the modified EAS discovery procedure based on the Rel-17 procedure described in TS 23.548 [3]. + +![Sequence diagram for Modified EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]) for Option 2. The diagram shows interactions between UE, sSMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, sEASDF, pEASDF, and DNS Server. It is divided into DNSContext Creation Procedure and DNSContext Update Procedure. The DNSContext Update Procedure includes steps 7-19, with step 9a (Selects pEASDF) being a new step. Red arrows indicate new or modified messages: 10. Neasdf_DNSContext_Update Request, 11. Neasdf_DNSContext_Update Response, 11a. DNS query, 12. DNS query, 13. DNS Response, and 13a. DNS Response.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant UE + participant sSMF + participant UPF_ULCL_BP as UPF ULCL/BP + participant UPF_L_PSA as UPF L-PSA + participant UPF_PSA as UPF PSA + participant sEASDF + participant pEASDF + participant DNS_Server as DNS Server + + Note left of UE: DNSContext Creation Procedure + Note left of UE: 1. PDU Session Establishment Procedure + Note left of sSMF: 2. Select EASDF + sSMF->>sEASDF: 3. Neasdf_DNSContext_Create Request + sEASDF-->>sSMF: 4. Neasdf_DNSContext_Create Response + + Note left of UE: DNSContext Update Procedure + sSMF->>sEASDF: 5. Neasdf_DNSContext_Update Request + sEASDF-->>sSMF: 6. Neasdf_DNSContext_Update Response + sSMF->>sEASDF: 7. DNS Query + sSMF->>sEASDF: 8. Neasdf_DNSContext_Notify Request + sEASDF-->>sSMF: 9. Neasdf_DNSContext_Notify Response + Note left of sSMF: 9a. Selects pEASDF + sSMF->>sEASDF: 10. Neasdf_DNSContext_Update Request + sEASDF-->>sSMF: 11. Neasdf_DNSContext_Update Response + sEASDF->>pEASDF: 11a. DNS query + pEASDF->>DNS_Server: 12. DNS query + DNS_Server-->>pEASDF: 13. DNS Response + pEASDF-->>sEASDF: 13a. DNS Response + sSMF->>sEASDF: 14. Neasdf_DNSContext_Notify Request + sEASDF-->>sSMF: 15. Neasdf_DNSContext_Notify Response + Note left of UPF_ULCL_BP: 16. ULCL/BP insertion + sSMF->>sEASDF: 17. Neasdf_DNSContext_Update Request + sEASDF-->>sSMF: 18. Neasdf_DNSContext_Update Response + sSMF->>UE: 19. DNS response + +``` + +Sequence diagram for Modified EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]) for Option 2. The diagram shows interactions between UE, sSMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, sEASDF, pEASDF, and DNS Server. It is divided into DNSContext Creation Procedure and DNSContext Update Procedure. The DNSContext Update Procedure includes steps 7-19, with step 9a (Selects pEASDF) being a new step. Red arrows indicate new or modified messages: 10. Neasdf\_DNSContext\_Update Request, 11. Neasdf\_DNSContext\_Update Response, 11a. DNS query, 12. DNS query, 13. DNS Response, and 13a. DNS Response. + +Figure 6.22.3.2-1: Modified EAS discovery (clause 6.2.3.2.2 of TS 23.548 [3]) for Option 2 + +The procedure is based on the EAS discovery procedure defined in clause 6.2.3.2.2 of TS 23.548 [3], with the following changes: + +- in step 3: the sSMF may provide to the serving EASDF the Filters for EAS Deployment Information (e.g. FQDN ranges) to be reported. +- new step 9a: based on the DNS message report sent by the sEASDF in steps 8/9 and on mapping criteria (see e.g. clause 6.40) or local configuration (i.e. a list of preconfigured, per partner PLMN DNS servers), the SMF selects the pEASDF or the preconfigured DNS server, respectively. +- steps 10/11: the sSMF instructs the sEASDF to forward the DNS query to the selected partner EASDF or to at least one preconfigured DNS server in the partner PLMNs. +- new step 11a: the sEASDF forwards the DNS query to the pEASDF or to at least one preconfigured DNS server in the partner PLMNs. + +NOTE: While the sEASDF matches the DNS query with the DNS context for the UE (as per Rel-17), the partner EASDF does not need to do that because it uses the DNS ECS option to select the most appropriate EAS. In that sense, the pEASDF behaves as a regular DNS server. The need to have a DNS UE context in the pEASDF for UE accessing from partner PLMNs can be discussed in the normative phase. + +- new step 13a: the pEASDF resolves the DNS query and sends the DNS reply to the sEASDF. In case of multiple replies to the sEASDF, the sEASDF selects (based on internal logic) which pEASDF (and, consequently, which partner PLMN) is to be used for the EAS selection. + +## 6.22.4 Impact on existing entities and interfaces + +### 6.22.4.0 Option 0: SMF configuration + +SMF: + +- needs to know EAS deployment information (IP address range(s)/FQDN(s)) of each EAS running in the PLMNs of the operators supporting Edge Node Sharing; +- needs to be configured with mapping between EAS deployment information and PLMN ID. If EAS' are added or removed, the configuration information needs to be updated. + +### 6.22.4.1 Option 2: Shared EASDF + +EASDF: + +- requires capability to communicate with shared-EASDF forward DNS query to and receive DNS response. + +Shared-EASDF: + +- needs to be configured with IP range/FQDN of list of all EAS' running in PLMNs of operators participating in the Edge Node Sharing. + +SMF: + +- needs to be configured with shared-EASDF address. + +### 6.22.4.2 Option 3: Per-PLMN EASDFs + +EASDF: + +- requires capability to communicate with EASDFs of another PLMN to forward DNS query to and receive DNS response. + +SMF: + +- needs to be configured per-PLMN EASDF addresses. + +AF: + +- provides CN with EAS Deployment Information with PLMN ID(s) and/or Filters. + +## 6.23 Solution 23 (KI#5): Improvements for EHE operated by separate party + +### 6.23.1 Introduction + +This solution aims to address the technical requirements related to key issue #5. In particular, it provides solutions to, among others, how the 5GS facilitates edge relocation between an EAS deployed by a source EHE provider to another EHE deployed by a target EHE provider, even in scenarios when EHEs are operated by different service providers. This solution has following architecture assumptions: + +- the architecture for Edge computing specified in Rel-17 is used as basis; +- the Edge Hosting Environment (EHE) can be under the control of the serving network operator or a 3rd party; +- the target and source AFs communicate with the SMF/NEF of a single PLMN; +- interconnectivity between EHEs of different operators is available, thus those deployments that does not support this would need further enhancements. + +## 6.23.2 Functional Description + +The following are the main principles of the solution: + +- In case of multiple and/or different EHE providers, it is possible that there is no cooperation and agreements among different Edge domains, thus implying that source EHE is unaware of other/target EHE specific deployment details. In such cases, specific to Edge relocation scenarios, source AF is unaware of suitable target AF and/or target EAS. Thus, source AF is not always able to assist suitable AF and EAS relocation as per clause 4.3 of TS 23.548 [3]. +- EHE providers likely have some kind of agreements with the 5GS, thus enabling 5GS to know respective EHE domain deployment details and corresponding AF, service area, TAI, application supported, etc. + +## 6.23.3 Solution Details + +- The selection of the target EHE, and corresponding AF/EAS is triggered due to multiple reasons, for example UE mobility, EAS overload, etc. +- SMF is able to know AF in the target EHE. This may be possible with either NRF or NEF maintaining AF list indicating for each AF one or more of these parameters: EHE domain it supports, service area, application supported, etc. This list could be based on e.g. pre-configuration and SLA with the EHE domain. Accordingly, SMF selects suitable target AF based on e.g. UE current location. + +The figure 6.23.3-1 below provides call flow where AF and EAS relocations are performed during early and late notifications. + +![Sequence diagram illustrating the procedure to support EAS and/or AF relocation between EHE from different provider. The diagram shows interactions between SMF, NEF, Source AF, and Target AF. The process starts with SMF triggering the selection of a target AF. It then proceeds through early notification, relocation request, relocation reply, traffic influence, PDU session reconfiguration, late notification, and finally relocation complete. Key elements include Nsmf_EventExposure_Notify, Nef_TrafficInfluence_Notify, UL Buffering activated/deactivated, and AF context exchanged.](2e8dcf3d807269a64340a9c292ea7f5d_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant NEF + participant Source AF + participant Target AF + + Note left of SMF: Trigger to select Target AF + SMF->>NEF: 1. Early Notification (... target AF ID, src AF Trans ID) + Note right of NEF: (Nsmf_EventExposure_Notify) (Nef_TrafficInfluence_Notify) + NEF->>Source AF: 2. Relocation Request (... source EAS ID, Service ID) + Source AF->>Target AF: 3. Relocation Reply (... target EAS ID, Service ID) + Note right of Target AF: AF context exchanged + Target AF->>Source AF: 4. EAS Relocation (e.g. context exchanged) + Source AF->>NEF: 5. Traffic Influence (... src AF Trans ID, ACK) + Note right of NEF: (UL Buffering activated) + NEF->>SMF: (Nsmf_EventExposure_AppRelocationInfo) + SMF->>NEF: 6. PDU Session Reconfiguration w/ possibly UPF PSA relocation + SMF->>NEF: 7. Late Notification + Note right of NEF: (Nsmf_EventExposure_Notify) + NEF->>Source AF: 8. Traffic Influence (GPSI, traffic description, source EAS @IP, target EAS @IP) + Note right of Source AF: (UL Buffering deactivated) + Source AF->>SMF: 9. Relocation Complete (... Service ID) + Note right of SMF: (Nsmf_EventExposure_AppRelocationInfo) + +``` + +Sequence diagram illustrating the procedure to support EAS and/or AF relocation between EHE from different provider. The diagram shows interactions between SMF, NEF, Source AF, and Target AF. The process starts with SMF triggering the selection of a target AF. It then proceeds through early notification, relocation request, relocation reply, traffic influence, PDU session reconfiguration, late notification, and finally relocation complete. Key elements include Nsmf\_EventExposure\_Notify, Nef\_TrafficInfluence\_Notify, UL Buffering activated/deactivated, and AF context exchanged. + +Figure 6.23.3-1: Procedure to support EAS and/or AF relocation between EHE from different provider + +- 0. SMF decides to relocate AF and/or EAS based on different criteria such as UE new location, Anchor UPF relocation and so on. + +1. As part of early notification, SMF provides target AF ID i.e. ID of the AF responsible for the new/target EC Domain corresponding to UE new location. SMF also provides source AF transaction ID. These are provided in the Nsmf\_eventExposure\_Notify and/or Nnef\_TrafficInfluence\_Notify. +2. Source AF on receipt of message in step 1 above, initiates AF context exchange and provides to target AF these information: source EAS ID, Service ID, etc. +3. Target AF responds by sending Relocation Reply with target EAS ID and Service ID. +4. EAS is relocated and if required application layer context are also exchanged. + +NOTE: This may require some application layer exchange between source and target EAS/AFs. How these information are exchanged are outside the scope of SA2. + +5. Source AF Acknowledges to SMF by sending Nnef\_EventExposure\_AppRelocationInfo and Nsmf\_EventExposure\_AppRelocation\_Info messages. +6. After confirmation from AF and considering information provided by AF, SMF may re-configure user plane path, etc. as required. +7. SMF sends Late notification to target AF in Nsmf\_eventExposure\_Notify and/or Nnef\_TrafficInfluence\_Notify. +8. Target AF sends acknowledgement to received late notification from SMF. New traffic descriptors are provided to replace the old ones which were provided earlier by the source AF. +9. Target AF sends Relocation Complete to the source AF so that the later deletes (relocated) EAS contexts. + +## 6.24 Solution 24 (KI#1): Reuse Option D after UL-CL Insertion + +### 6.24.1 Description + +This solution addresses the following aspect in KI#1: + +- how to support Rel-17 edge computing related procedures, such as EAS (re-)discovery, as specified in clause 6 of TS 23.548 [3]. + +Option D is specified in clause 6.2.3.2.3 of TS 23.548 [3] to support EAS Discovery procedure with Local DNS Server/Resolver. + +This solution addresses the scenario 2.2 of clause 5.1.2, that is, UE accessing V-EHE via a Home Routed (HR) PDU Session (i.e. with PSA in HPLMN) where HPLMN does not have the knowledge of EAS deployment information in VPLMN. + +This solution assumes that the V-SMF in the VPLMN is authorized by HPLMN to insert the UL-CL and Local PSA during or after PDU Session Establishment based on the VPLMN operator's configuration, which can be based on the conclusion on other solutions for this key issue. With this assumption, Option D can work for both LBO and HR roaming cases. + +## 6.24.2 Procedure + +![Sequence diagram for EAS discovery with Local DNS server/resolver. The diagram shows interactions between UE, V-SMF, UL CL, L-PSA, PSA, Local DNS Resolver, Local DNS Server, and C-DNS. The steps are: 1. UL CL insertion (V-SMF to UL CL), 2. DNS Query (UE to L-PSA), 3. DNS message forwarding and handling (L-PSA to C-DNS), and 4. DNS Response (C-DNS to UE).](7dfe05137c554aca6bed20d67e52d739_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant UL CL + participant L-PSA + participant PSA + participant Local DNS Resolver + participant Local DNS Server + participant C-DNS + + Note right of V-SMF: 1. UL CL insertion + UE->>L-PSA: 2. DNS Query + Note right of L-PSA: 3. DNS message forwarding and handling + C-DNS-->>UE: 4. DNS Response + +``` + +Sequence diagram for EAS discovery with Local DNS server/resolver. The diagram shows interactions between UE, V-SMF, UL CL, L-PSA, PSA, Local DNS Resolver, Local DNS Server, and C-DNS. The steps are: 1. UL CL insertion (V-SMF to UL CL), 2. DNS Query (UE to L-PSA), 3. DNS message forwarding and handling (L-PSA to C-DNS), and 4. DNS Response (C-DNS to UE). + +**Figure 6.24.2-1: EAS discovery with Local DNS server/resolver** + +1. UL-CL and Local PSA are inserted by V-SMF. This procedure can happen during PDU Session establishment or can be triggered by DNS messages as defined in clause 6.2.3.2.2 of TS 23.548 [3]. During this procedure, the V-SMF instructs the UL-CL the traffic routing rule to route the DNS Query for an FQDN (range) to a local DNS Server/Local DNS Resolver. + +NOTE 1: Option D assumes that UL-CL steering is based on L4 information (i.e. DNS port number) and that UL-CL 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. + +2. The DNS Query message is sent by UE. The UL-CL locally routes the DNS Query message to Local PSA. + +3. 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 2: 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. + +4. 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 3: If IP address replacement has been enforced at step 3, the Local PSA replaces the source IP address to EASDF IP according to SMF instruction. + +## 6.24.3 Impacts on services, entities, and interfaces + +### V-SMF: + +- supports UL-CL/Local PSA insertion, traffic routing rule configuration on UL-CL to route the DNS Query for an FQDN (range) to a local DNS Server/Resolver. + +## 6.25 Solution 25 (KI#1): EAS discovery in VPLMN via V-EASDF for a HR PDU Session + +### 6.25.1 High level description + +The solution addresses a scenario where the UE accesses EHE in VPLMN via a HR PDU Session for the two sub-scenarios 2.1 and 2.2, in clause 5.1.2. In addition, the solution includes an option that allows the HPLMN to monitor, assist and validate VPLMN decisions for accessing EHE when that has been triggered by HPLMN (scenario 2.1). + +The authorization for the traffic offload for a HR PDU Session with given S-NSSAI and DNN is received by the AMF from the UDM, based on a "HR-LBO allowed" indication in the UE subscription data. + +In scenario 2.1, HPLMN has the knowledge of EAS Deployment information (EDI) in VPLMN for specific areas. In this solution, EDI Information structure in TS 23.548 [3] table 6.2.3.4-1 does not require VPLMN DNAIs, which simplifies the information exchanged between all parties (VPLMN DNAIs in EDI to HPLMN require that Home MNO understands the VPLMN DNAIs, that HPLMN shares them then with the Service providers (SPs) it has agreements with, and that SPs provide EDI related to VPLMN DNAIs and modify it if VPLMN DNAIs change). In this solution, EDI information is structured and grouped based on common steering needs, e.g. same SP EHE. As part of SLA between the HPLMN and VPLMN, HPLMN provides the list of EC FQDNs and/or traffic descriptors (e.g. destination IP ranges) for the traffic that would require access to EHE in VPLMN to trigger EAS Discovery and local traffic routing in VPLMN. This information is used to set the UL-CL filters and also to provision V-EASDF in the case of dynamic PSA insertion by DNS-based EAS discovery. Alternatively, this information can be conveyed to V-SMF by H-SMF during PDU Session establishment or update. AF can use clause 6.2.3.4 in TS 23.548 [3] EAS Deployment Information Management mechanisms to create/update/delete HPLMN knowledge of EAS Deployment information of specific services relevant for HPLMN roamers in VPLMN. A common steering identifier can be used instead of DNAI. + +For scenario 2.1, when HPLMN wishes to monitor, assist and validate VPLMN decisions when HPLMN has triggered accessing EHE in VPLMN, the common steering identifier refers to Geo Location Area in VPLMN. This alternative requires that HPLMN knows how VPLMN ECSs map to the VPLMN Geo Location Areas. + +For scenario 2.2, VPLMN has the knowledge of EAS Deployment information in VPLMN for specific areas. Clause 6.2.3.4 in TS 23.548 [3] EAS Deployment Information Management mechanisms can be used by AF to provide and keep updated EDI in VPLMN via V-NEF, and by V-SMF to retrieve that data and use in EAS Discovery procedures. Information can also be locally configured. + +At HR PDU Session establishment, the HPLMN (H-SMF) receives V-EASDF address from V-SMF. For V-EASDF to be the DNS resolver for the EC FQDNs, there are two options: + +- A. H-SMF configures V-EASDF in the UE as DNS server for the PDU Session. V-SMF may insert a UL-CL/BP and local PSA to reach the V-EASDF, to eliminate DNS traffic tromboning. V-SMF gets the HPLMN DNS Resolver. +- B. V-SMF receives the EC FQDNs (either by OAM or from H-SMF at PDU Session establishment), and it configures a local UL-CL for replacement of the destination IP address of DNS queries with EC FQDN to V-EASDF IP. + +NOTE 1: The above solution is known as option D described in clause 6.2.3.2.3 in TS 23.548 [3]. Option D assumes that UL-CL steering is based on L4 information (i.e. DNS port number) and that UL-CL has visibility of the DNS traffic (i.e. FQDN in the DNS Query message). The UPF can be instructed by the SMF to apply different forwarding of unencrypted 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. + +V-SMF selects and inserts UL-CL/L-PSA for the DNS traffic at PDU Session establishment and for the EC application traffic either statically at PDU Session establishment, or dynamically, based on interaction with V-EASDF. + +For scenario 2.2 in clause 5.1.2, dynamic EAS discovery and insertion of UL-CL and local PSA happens in the V-PLMN based on V-EASDF as defined in TS 23.548 [3]. HPLMN does not need to know the EC deployment in VPLMN, VPLMN has the knowledge of EAS Deployment information in VPLMN, and the selection is made by V-SMF considering this information. + +For scenario 2.1 in clause 5.1.2, the VPLMN does not know the EC deployment in VPLMN (it is known by HPLMN), and V-SMF selects the L-PSA based on UE location only. V-SMF selects the UL-CL and L-PSA based on V-EASDF notification as defined in TS 23.548 [3], but without considering the EAS deployment information. V-SMF uses information provided by HPLMN to set the UL-CL filters and to provision V-EASDF. + +For scenario 2.1, if Home MNO monitors, assists and validates the decisions related to applications for which it has triggered user access to EHE in VPLMN, H-SMF selects an H-EASDF that monitors the DNS resolution for those applications and that validates the selected L-PSA. The address of the H-EASDF for the PDU Session is sent to V-SMF as a next HPLMN DNS Resolver after V-EASDF, which triggers validation in the following way: + +- V-EASDF appends to the UE DNS queries for EC FQDNs (agreed in the SLA, or provided at session establishment) an ECS option based on current UE location and sends it to H-EASDF. +- H-EASDF notifies H-SMF of the query, also sending the ECS option received, based on which H-SMF identifies the UE Geo Location Area and may select a local DNS server for the query and provide it to H-EASDF. +- Based on the information received from the H-SMF, the H-EASDF forwards the query according to instruction, setting the next DNS server to the local DNS server if one received +- The DNS response is then received by H-EASDF, which notifies H-SMF. If an EAS has been selected, H-SMF may instruct H-EASDF to include ECS back in the response (the one provided by VPLMN in the DNS Query or one corresponding to the EAS IP selection) and to forward the DNS Response to V-EASDF. +- If the ECS is inserted in the response, this means that it has been used in EAS selection. V-SMF then selects and inserts UL-CL and local PSA based on notification received from V-EASDF considering the ECS received if any. + +The solution is based on the Session breakout connectivity model in VPLMN. + +In scenario 2.1, as part of SLA between the HPLMN and VPLMN, HPLMN may also provide QoS policies for specific Applications to VPLMN. V-SMF may be configured with limitations for roamers (and DNN/S-NSSAI) it enforces on HPLMN provided policies. Alternatively, QoS rules can be conveyed to V-SMF by H-SMF during PDU Session establishment or update as specific information or as an indication to V-SMF to store the information sent to the UE in the NAS message and the QoS profile sent to gNB. + +In scenario 2.2, V-PCF may provide PCCs to V-SMF during PDU Session Establishment. + +To support charging in both PLMNs, the V-SMF provides Usage Reporting Rules to the UL-CL/BP and local PSA to collect Usage Reports for charging in VPLMN that it conveys to H-SMF. + +## 6.25.2 Procedures + +### 6.25.2.1 PDU Session establishment and EAS discovery + +The solution is shown in figure 6.25.2.1-1 below. + +![Sequence diagram for EAS discovery in VPLMN via HR PDU Session. Lifelines: UE, V-SMF, UL CL/BP, V-EASDF, H-SMF, H-PCF, UDM, H-EASDF, DNS server. The sequence starts with UE registration (0) and PDU session establishment (1). V-SMF sends Nsmf_PDUSession_Create Request (2) to H-SMF. H-SMF retrieves subscription and policies (3) and sends Neasdf_DNSContext_Create Request/Response (4) to H-EASDF. V-SMF receives Nsmf_PDUSession_Create Response (5) and inserts UL CL/BP and local PSA (6). V-SMF sends Neasdf_DNSContext_Create Request/Response (7) to V-EASDF. UE receives PDU Session Establishment Accept (8) and sends DNS Query (9). A dashed box (10) indicates steps 8-19 from TS 23.548, clause 6.2.3.2.2, involving V-SMF and V-EASDF and insertion of UL CL and L-PSA. Another dashed box (11) indicates steps 8-11 from TS 23.548, clause 6.2.3.2.2, involving V-SMF and V-EASDF. V-EASDF sends DNS Query (12) to H-EASDF. A dashed box (13) indicates steps 8-15 and 17-18 from TS 23.548, clause 6.2.3.2.2, involving H-SMF and H-EASDF. H-EASDF sends DNS Response (14) to V-EASDF. A dashed box (15) indicates steps 14-18 from TS 23.548, clause 6.2.3.2.2, involving V-SMF and V-EASDF and insertion of UL CL and L-PSA. UE receives DNS Response (16).](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +Sequence diagram for EAS discovery in VPLMN via HR PDU Session. Lifelines: UE, V-SMF, UL CL/BP, V-EASDF, H-SMF, H-PCF, UDM, H-EASDF, DNS server. The sequence starts with UE registration (0) and PDU session establishment (1). V-SMF sends Nsmf\_PDUSession\_Create Request (2) to H-SMF. H-SMF retrieves subscription and policies (3) and sends Neasdf\_DNSContext\_Create Request/Response (4) to H-EASDF. V-SMF receives Nsmf\_PDUSession\_Create Response (5) and inserts UL CL/BP and local PSA (6). V-SMF sends Neasdf\_DNSContext\_Create Request/Response (7) to V-EASDF. UE receives PDU Session Establishment Accept (8) and sends DNS Query (9). A dashed box (10) indicates steps 8-19 from TS 23.548, clause 6.2.3.2.2, involving V-SMF and V-EASDF and insertion of UL CL and L-PSA. Another dashed box (11) indicates steps 8-11 from TS 23.548, clause 6.2.3.2.2, involving V-SMF and V-EASDF. V-EASDF sends DNS Query (12) to H-EASDF. A dashed box (13) indicates steps 8-15 and 17-18 from TS 23.548, clause 6.2.3.2.2, involving H-SMF and H-EASDF. H-EASDF sends DNS Response (14) to V-EASDF. A dashed box (15) indicates steps 14-18 from TS 23.548, clause 6.2.3.2.2, involving V-SMF and V-EASDF and insertion of UL CL and L-PSA. UE receives DNS Response (16). + +**Figure 6.25.2.1-1: EAS discovery in VPLMN via HR PDU Session** + +0. At UE registration procedure, the AMF receives a "HR-LBO allowed" indication from the UDM for a given S-NSSAI and DNN. This is used by the AMF to select a V-SMF with the required capability during the PDU Session establishment procedure. +1. UE sends PDU Session establishment request to V-SMF selected by the AMF. AMF appends HR-LBO authorization indication to V-SMF. +2. V-SMF takes into account the HR-LBO indication and may create an association with V-PCF for local traffic offload policies. For scenario 2.2, it may contact V-NEF to retrieve EAS Deployment Information. V-SMF selects UPF and V-EASDF in VPLMN (that could be based on the policies fetched from V-PCF) and sends Nsmf\_PDUSession\_Create Request to H-SMF, in which it indicates support for EC, and also provides the V-EASDF address to H-SMF and recommended indication for EDC usage for the PDU Session. +3. H-SMF retrieves subscription information and policies for this UE and PDU Session, and selects and configures UPF in HPLMN as in steps 7-12 in clause 4.3.2.2.2 of TS 23.502 [9], but the subscription information and policies include the information related to the EC traffic that could be directed to EHE in VPLMN. For scenario 2.1, H-SMF may contact H-NEF to retrieve EAS Deployment Information. + +4. [Conditional] For scenario 2.1 in clause 5.1.2 if HPLMN monitoring, assisting and validation, the H-SMF selects an H-EASDF and configures the DNS handling rules in H-EASDF, via Neasdf\_DNSContext\_Create. +5. The H-SMF sends Nsmf\_PDUSession\_Create Response to the V-SMF. H-SMF provides V-SMF with the H-DNS server as resolver for non-EC FQDNs (in case of Option A from clause 6.25.1). For scenario 2.1, the H-SMF response may include QoS rules for this PDU Session. According to UE support, the H-SMF response may also include in e PCO the vECS (Edge Configuration Server) information and indication for EDC usage for the PDU Session for the UE. The DNS server information in the PCO includes one of: + - a. V-EASDF IP address (in case of Option A from clause 6.25.1); or + - b. a H-DNS server (in case of Option B from clause 6.25.1). + +For scenario 2.1, H-SMF may provide V-SMF with information of applications for which to trigger routing to EHE in VPLMN (IP ranges and DNS domain name ranges). + +[Conditional] For scenario 2.1 if HPLMN monitoring, assisting and validation, H-SMF also provides the address of the selected H-EASDF. + +6. The V-SMF performs UL-CL/BP and local PSA selection and insertion. The V-SMF also provisions V-EASDF and UL-CL/BP to steer DNS traffic (only certain FQDNs if Option B) towards V-EASDF IP address and local PSA. +7. V-SMF configures the DNS handling rules in V-EASDF, via Neasdf\_DNSContext\_Create. +8. V-SMF sends PDU Session Establishment accept message including the PCO received from H-SMF to the UE. +9. UE sends a DNS query which includes FQDN for an EHE deployed in the VPLMN. The query reaches V-EASDF via the local UL-CL and PSA (in case of both Options A and B from clause 6.25.1). +10. [Conditional] For scenario 2.2 and 2.1 in clause 5.1.2 without HPLMN monitoring, assisting and validation, the EAS discovery and UL-CL/BP and local PSA selection is performed as described in steps 8–19 from clause 6.2.3.2.2 in TS 23.548 [3], though information available in each scenario varies. For scenario 2.1, V-SMF does not have EDI, and decision is mainly based on UE location. + +Steps 11-16. [Conditional] For scenario 2.1 in clause 5.1.2 with HPLMN monitoring, assisting and validation: + +11. The DNS query triggers notification from V-EASDF to V-SMF, which provides message handling rules to V-EASDF as described in steps 8-11 from clause 6.2.3.2.2 of TS 23.548 [3]. The rules include an ECS to append to the DNS query corresponding to the candidate local PSA and H-EASDF as next DNS server to send the query to. V-SMF does not have EDI, and decision is mainly based on UE location. +12. The DNS query is forwarded from V-EASDF to H-EASDF using the ECS received from V-SMF in step 11. +13. The procedure in steps 8-15 from clause 6.2.3.2.2 of TS 23.548 [3] is repeated, where the DNS query triggers notification from H-EASDF to H-SMF, and H-EASDF sends the DNS query to H-SMF together with the ECS received. This triggers a validation process in H-SMF for UE Geo Location Area corresponding to the received ECS. The SMF may instruct H-EASDF to send the query to a Local DNS in the DNS handling rule. H-EASDF then handles the DNS resolution and notifies the response to the H-SMF that may also validate the response. Note that H-SMF does not deploy any UL-CL/BP and local PSA. H-SMF may instruct H-EASDF to include ECS back in the response (the one provided by VPLMN in the DNS Query or one corresponding to the EAS IP selection) and to forward the DNS Response to V-EASDF. +14. The DNS response is sent back the V-EASDF. +15. V-EASDF notifies V-SMF that takes into account ECS and may modify the UP path to steer application traffic to another L-PSA as in steps 14-18 from clause 6.2.3.2.2 of TS 23.548 [3]. +16. If indicated so, the DNS response is sent back to the UE. + +## 6.25.2.2 EAS rediscovery due to UE or application mobility + +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 as described in clause 6.2.3.3 of TS 23.548 [3]. The corresponding EAS rediscovery procedure is shown in figure 6.25.2.2-1: + +![Sequence diagram illustrating the EAS rediscovery procedure due to UE mobility. The diagram shows interactions between UE, V-SMF, ULCL/BP L-PSA, V-EASDF, New V-EASDF, and H-SMF. The steps are: 0. PDU Session establishment (UE indicates support for refreshing stale EAS information) and EAS discovery; 1. UE mobility or AF influence triggers UL CL/BP and L-PSA reselection in VPLMN; 2. Nsmf_PDUSession_Update Request (EAS rediscovery needed, impact, new V-EASDF) from V-SMF to H-SMF; 3. H-SMF sends EAS rediscovery indication and UE refreshes DNS record; 4. Nsmf_PDUSession_Update Response from H-SMF to V-SMF; 5. EAS rediscovery procedure in VPLMN.](c0ca823603794512478906b302176bca_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant ULCL/BP L-PSA + participant V-EASDF + participant New V-EASDF + participant H-SMF + + Note over UE, H-SMF: 0. PDU Session establishment (UE indicates support for refreshing stale EAS information) and EAS discovery + Note over UE, H-SMF: 1. UE mobility or AF influence triggers UL CL/BP and L-PSA reselection in VPLMN + V-SMF->>H-SMF: 2. Nsmf_PDUSession_Update Request (EAS rediscovery needed, impact, new V-EASDF) + Note over UE, H-SMF: 3. H-SMF sends EAS rediscovery indication and UE refreshes DNS record + H-SMF-->>V-SMF: 4. Nsmf_PDUSession_Update Response + Note over UE, H-SMF: 5. EAS rediscovery procedure in VPLMN + +``` + +Sequence diagram illustrating the EAS rediscovery procedure due to UE mobility. The diagram shows interactions between UE, V-SMF, ULCL/BP L-PSA, V-EASDF, New V-EASDF, and H-SMF. The steps are: 0. PDU Session establishment (UE indicates support for refreshing stale EAS information) and EAS discovery; 1. UE mobility or AF influence triggers UL CL/BP and L-PSA reselection in VPLMN; 2. Nsmf\_PDUSession\_Update Request (EAS rediscovery needed, impact, new V-EASDF) from V-SMF to H-SMF; 3. H-SMF sends EAS rediscovery indication and UE refreshes DNS record; 4. Nsmf\_PDUSession\_Update Response from H-SMF to V-SMF; 5. EAS rediscovery procedure in VPLMN. + +**Figure 6.25.2.2-1: EAS rediscovery procedure due to UE mobility** + +0. The procedure in clause 6.25.2.1 is executed with the following differences required for EAS rediscovery: + +In step 1, the UE may indicate its support for refreshing stale EAS information stored locally corresponding to the impact field per the EAS rediscovery indication from network. + +If the UE indicates such support, then in step 5, H-SMF conveys this indication to V-SMF and V-SMF stores this indication. + +1. Due to the UE mobility or AF influence on traffic routing to VPLMN (which happens through V-NEF and V-PCF for scenario 2.2), the V-SMF triggers L-PSA insertion, change or removal for the PDU Session. +2. V-SMF sends PDU Session Nsmf\_PDUSession\_Update Request to H-SMF, including: + - an EAS rediscovery needed indication; + - information about the impacted EAS(s); + - [conditionally] if V-EASDF relocation is also needed, the new V-EASDF IP address. +3. H-SMF sends PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE as described in step 2 of clause 6.2.3.3 of TS 23.548 [3]. The EAS rediscovery indication indicates to refresh the cached EAS information. The impact field is used to identify which EAS(s) information needs to be refreshed. +4. H-SMF sends PDU Session Nsmf\_PDUSession\_Update Response to V-SMF. +5. UE may trigger EAS discovery procedure to get new EAS information. + +NOTE: For scenario 2.1, AF request to influence traffic routing towards the HPLMN (H-SMF) is not possible if the EDI does not include DNAIs. The Application mobility will in general not imply UL-CL/BP and L-PSA relocation for scenario 2.1, as the L-PSA is selected based on UE location. + +### 6.25.3 Impacts on services, entities and interfaces + +#### UDM: + +- UE subscription information enhanced for authorizing the "HR-LBO". + +#### AMF + +- handles "HR-LBO" in UE Subscription and takes it into account for V-SMF selection. + +#### V-SMF: + +- indicating support for EC and providing V-EASDF IP address and recommended EDC usage indication to H-SMF; +- supporting V-EASDF selection and interaction with V-EASDF using Neasdf interface as in TS 23.548 [3]; +- supporting interaction with NEF in VPLMN to retrieve EDI as in TS 23.548 [3] (only scenario 2.2); + +- supporting UL-CL/BP and L-PSA selection and provisioning for session breakout in HR PDU Session based for example on local configuration, and user session information from policy association with VPCF, from HPLMN H-SMF, and/or from V-EASDF; +- sending EAS rediscovery needed indication and impacted EAS(s) information; +- supporting V-EASDF interaction including instructions for tunnelling DNS messages towards a next H-EASDF (only scenario 2.1 with HPLMN monitoring, assisting and validation). + +**H-SMF:** + +- provisions UE using (e)PCO via V-SMF with V-EASDF for the EC related DNS queries (using option A from clause 6.25.2.1), EDC usage indication (considering V-SMF recommendation) and vECS information for the VPLMN; +- sends to V-SMF information related to local traffic routing such as the IP address ranges and DNS domain name ranges for EC applications for which to trigger steering to EHE in VPLMN. Information is based on HPLMN knowledge of EDI (only scenario 2.1). It also sends the H-DNS; +- sends H-EASDF IP address to V-SMF (including any tunnelling information) and with H-EASDF it inspects/replaces/restores ECS information in received DNS messages from VPLMN to monitor, assist and validate selected L-PSA vs the selected EAS location (only for scenario 2.1 with HPLMN monitoring and validation). + +**V-PCF:** + +- provides local policies to V-SMF for HR-PDU Sessions. + +**EASDF:** + +- sends DNS query/response over a tunnel (between V-EASDF and H-EASDF). EASDF instructions include tunnelling information (only for scenario 2.1 with HPLMN monitoring and validation). + +## 6.26 Solution 26 (KI#1): SM Policy for HR Session Breakout in VPLMN + +### 6.26.1 Description + +This solution addresses the following aspects in KI#1 for the scenario where Home Routed PDU Session is used with a PSA in the HPLMN: + +- how to authorize the PDU Session to support local traffic routing to access an EHE in the VPLMN; +- how to ensure proper policy control and QoS enforcement; +- potential impact on Policy and QoS control. + +This solution proposes how to obtain and apply Session Management policy when a roaming UE establishes a Home Routed PDU Session supporting session breakout in VPLMN to access EHE in VPLMN, assuming that HPLMN and VPLMN have an agreement on supporting HR session breakout. + +In this scenario, Session Management policy is created and applied for the HR Session supporting session breakout as follows: + +- 1) During the establishment of Home Routed PDU Session, if the roaming UE is allowed to access the local part of DN, V-SMF selects a V-PCF that is capable of providing SM policy for HR session breakout and requests, to the selected V-PCF, SM policy for HR session breakout via SM policy association procedure. +- 2) The V-PCF provides SM Policy to the V-SMF based on the VPLMN operator policy (option 1) or interaction with H-PCF (option 2). +- 3) The V-SMF executes the session breakout procedure and configures V-UPF acting as UL-CL/BP, V-PSA (connected to local part of DN), and V-UPF (connected with H-UPF for home routed session), respectively + +based on the SM Policy. For example, usage monitoring control and QoS information can be applied differently for the session toward the H-UPF and the local session to the local part of DN (i.e. HR breakout session). Thus, different usage monitoring control related information and QoS information such as Session-AMBR are provisioned to the V-UPF connected with the H-UPF and the V-PSA providing access to local part of DN, respectively. + +## 6.26.2 Procedures + +### 6.26.2.1 Option 1: Indirect interaction between V-PCF and H-PCF + +![Sequence diagram illustrating the SM Policy Association Procedure for HR Session Breakout in VPLMN. The diagram shows interactions between V-SMF, V-PCF, H-PCF, and H-SMF. The steps are: 1. V-SMF receives SM Context Create request; 2. V-SMF sends SM Policy Association Establishment request (with HR session breakout indication) to V-PCF; 3. V-PCF sends SM Policy Association Estb. response to V-SMF; 4. V-SMF sends PDU Session Create Request (with HR session breakout indication and V-PCF policy info) to H-SMF; 5. H-SMF performs Subscription data retrieval; 6. H-SMF sends SM Policy Association Establishment request to H-PCF; 7. H-SMF sends PDU Session Create Response to V-SMF; 8. V-SMF sends SM Policy Association Modification to V-PCF.](6d67eee81b97a14e06a6fe57a95aff36_img.jpg) + +``` + +sequenceDiagram + participant V-SMF + participant V-PCF + participant H-PCF + participant H-SMF + + Note left of V-SMF: 1. Receive SM Context Create request + V-SMF->>V-PCF: 2. SM Policy Association Establishment request +(Indication for HR session breakout related policy request) + V-PCF-->>V-SMF: 3. SM Policy Association Estb. response + V-SMF->>H-SMF: 4. PDU Session Create Request +(HR session breakout indication, V-PCF provided policy information) + Note right of H-SMF: 5. Subscription data retrieval + H-SMF->>H-PCF: 6. SM Policy Association Establishment + H-SMF-->>V-SMF: 7. PDU Session Create Response + V-SMF->>V-PCF: 8. SM Policy Association Modification + +``` + +Sequence diagram illustrating the SM Policy Association Procedure for HR Session Breakout in VPLMN. The diagram shows interactions between V-SMF, V-PCF, H-PCF, and H-SMF. The steps are: 1. V-SMF receives SM Context Create request; 2. V-SMF sends SM Policy Association Establishment request (with HR session breakout indication) to V-PCF; 3. V-PCF sends SM Policy Association Estb. response to V-SMF; 4. V-SMF sends PDU Session Create Request (with HR session breakout indication and V-PCF policy info) to H-SMF; 5. H-SMF performs Subscription data retrieval; 6. H-SMF sends SM Policy Association Establishment request to H-PCF; 7. H-SMF sends PDU Session Create Response to V-SMF; 8. V-SMF sends SM Policy Association Modification to V-PCF. + +**Figure 6.26.2.1-1: Option 1: SM Policy Association Procedure for HR Session Breakout in VPLMN** + +1. During the PDU Session establishment procedure, the AMF indicates to the SMF that the HR session breakout is allowed. +2. If the V-SMF is indicated by the AMF that the HR session breakout is allowed, the V-SMF sends Session Management Policy Association Establishment request to the V-PCF. The V-SMF provides the V-PCF with the indication to request HR session breakout related policy. +3. The V-PCF makes the authorization and the policy decision for HR session breakout, and sends SM Policy Association Establishment response to the V-SMF. The V-PCF provides policy information that may include QoS constraints (e.g. including HR breakout session AMBR constraint) or usage monitoring control related information (e.g. AMBR and volume threshold for the session toward the local part of the DN) for the HR breakout session. +4. The V-SMF sends PDU Session Create Request to H-SMF. The V-SMF provides the H-SMF with the VPLMN-provided policy information for the HR breakout session. +5. The H-SMF retrieves Session Management subscription data related to the HR breakout session (e.g. Subscribed HR breakout session AMBR from UDM) for the VPLMN. The Session Management subscription data related to the HR breakout session may be associated with PLMN ID (i.e. VPLMN ID). + +6. The H-SMF performs SM Policy Association Establishment with the H-PCF. The H-SMF provides the H-PCF with the received VPLMN-provided policy information for the HR breakout session and Subscribed HR breakout session AMBR retrieved from UDM. The H-PCF executes the authorization and the policy decision for HR roaming session with taking VPLMN-provided policy information and Subscribed HR breakout session AMBR retrieved from UDM into account. The H-PCF provides the authorized SM policy information to the H-SMF as the response to the SM Policy Association Establishment request. +7. The H-SMF sends PDU Session Create Response to V-SMF. The H-SMF provides HPLMN-authorized policy information. +8. The V-SMF performs SM Policy Association Modification with V-PCF based on the policy information from the H-SMF. The V-SMF performs the insertion of V-UPF acting as UL-CL with configuring the authorized SM policy (e.g. HR breakout session AMBR) into it. + +#### 6.26.2.2 Option 2 — Direct interaction between V-PCF and H-PCF + +![Sequence diagram for Option 2: SM Policy Association Procedure for HR Session Breakout in VPLMN. The diagram shows interactions between V-SMF, V-PCF, H-PCF, and H-SMF. Steps include: 1. V-SMF receives SM Context Create request; 2. V-SMF sends SM Policy Association Establishment request to V-PCF (with HR session breakout indication); 3. V-PCF sends SM Policy Association Establishment request to H-PCF; 4. H-PCF sends SM Policy Association Establishment response to V-PCF; 5. V-PCF sends SM Policy Association Estb. response to V-SMF; 6. V-SMF sends PDU Session Create Request to H-SMF (with HR session breakout indication, policy information, H-PCF ID/address); 7. H-SMF performs Subscription data retrieval; 8. H-SMF sends SM Policy Association Establishment to H-PCF; 9. H-SMF sends PDU Session Create Response to V-SMF.](34d7353cac3d344f71ad82bd1eda40d1_img.jpg) + +``` + +sequenceDiagram + participant V-SMF + participant V-PCF + participant H-PCF + participant H-SMF + + Note left of V-SMF: 1. Receive SM Context Create request + V-SMF->>V-PCF: 2. SM Policy Association Establishment request +(Indication for HR session breakout related policy request) + V-PCF->>H-PCF: 3. SM Policy Association Establishment request + H-PCF-->>V-PCF: 4. SM Policy Association Establishment response + V-PCF-->>V-SMF: 5. SM Policy Association Estb. response + V-SMF->>H-SMF: 6. PDU Session Create Request +(HR session breakout indication, policy information, H-PCF ID/address) + Note right of H-SMF: 7. Subscription data retrieval + H-SMF->>H-PCF: 8. SM Policy Association Establishment + H-SMF-->>V-SMF: 9. PDU Session Create Response + +``` + +Sequence diagram for Option 2: SM Policy Association Procedure for HR Session Breakout in VPLMN. The diagram shows interactions between V-SMF, V-PCF, H-PCF, and H-SMF. Steps include: 1. V-SMF receives SM Context Create request; 2. V-SMF sends SM Policy Association Establishment request to V-PCF (with HR session breakout indication); 3. V-PCF sends SM Policy Association Establishment request to H-PCF; 4. H-PCF sends SM Policy Association Establishment response to V-PCF; 5. V-PCF sends SM Policy Association Estb. response to V-SMF; 6. V-SMF sends PDU Session Create Request to H-SMF (with HR session breakout indication, policy information, H-PCF ID/address); 7. H-SMF performs Subscription data retrieval; 8. H-SMF sends SM Policy Association Establishment to H-PCF; 9. H-SMF sends PDU Session Create Response to V-SMF. + +**Figure 6.26.2.2-1: Option 2: SM Policy Association Procedure for HR Session Breakout in VPLMN** + +0. During the Registration procedure, the AMF is indicated by the UDM that the HR session breakout is allowed. This indication can be per DNN/S-NSSAI. The AMF performs discovery and selection of the H-PCF that is capable of providing SM Policy for HR session breakout if the AMF receives the HR session breakout allowed indication from the UDM. +1. During the PDU Session establishment procedure, the AMF sends Session Management Context Create Request including the selected H-PCF information and the indication to the SMF that the HR session breakout is allowed. +2. If the V-SMF is indicated by the AMF that the HR session breakout is allowed, the V-SMF sends Session Management Policy Association Establishment request to the V-PCF. The V-SMF provides the V-PCF with the indication to request HR session breakout related policy and the H-PCF information. +3. The V-PCF determines to interact with the H-PCF identified by the AMF-provided H-PCF information and sends SM Policy Establishment request. The V-PCF provides the H-PCF with the VPLMN-supported policy + +information that may include QoS constraints or usage monitoring control related information (e.g. AMBR and volume threshold for the session toward the local part of the DN) for the HR breakout session in VPLMN. + +4. The H-PCF executes the authorization and the policy decision for HR roaming session with taking the received policy information into account. The H-PCF provides the authorized SM policy information to the V-PCF as the response to the SM Policy Association Establishment request. +5. The V-PCF forwards the received SM policy information to the V-SMF. +6. The V-SMF sends PDU Session Create Request to H-SMF after UPF selection and configuration in VPLMN based on the received SM policy information. The V-SMF provides the H-SMF with the applied SM policy information in VPLMN and information of the H-PCF that establishes SM Policy Association with the V-PCF. +7. The H-SMF retrieves Session Management subscription data related to the HR breakout session (e.g. Subscribed HR breakout session AMBR from UDM) for the VPLMN. The Session Management subscription data related to the HR breakout session may be associated with PLMN ID (i.e. VPLMN ID). +8. The H-SMF performs SM Policy Association Establishment with the H-PCF of which information is provided by the V-SMF. The H-PCF executes the authorization and the policy decision for HR roaming session with taking the VPLMN-provided policy information into account. The H-PCF provides the authorized SM policy information to the H-SMF as the response to the SM Policy Association Establishment request. +9. The H-SMF sends PDU Session Create Response to V-SMF. The V-SMF performs the insertion of V-UPF acting as UL-CL with configuring the authorized SM policy (e.g. HR breakout session AMBR) into it. + +### 6.26.3 Impacts on existing entities and interfaces + +#### V-SMF: + +- supports SM Policy Association with the V-PCF for the HR PDU Session; +- supports to provide VPLMN-provided policy information to the H-SMF; +- supports to insert the V-UPF acting as UL-CL for the HR PDU Session and provide enforcement rule information (e.g. HR breakout session AMBR). + +#### V-PCF: + +- supports SM Policy Association with the V-SMF, authorization and policy decision for the HR Session breakout in VPLMN; +- supports SM Policy Association with the H-PCF (for option 2). + +#### H-SMF/H-PCF: + +- supports SM Policy Association with taking VPLMN-provided SM Policy information into account; +- (H-SMF) supports to retrieve the subscription information related to HR session breakout. + +#### AMF: + +- supports to indicate V-SMF that HR session breakout is allowed; +- supports discovery and selection of SM PCF in HPLMN (for option 2). + +#### UDM: + +- supports to store the subscription information for whether HR session breakout is allowed and indicate AMF that HR session breakout is allowed based on the stored information; +- supports to store the subscription information for QoS constraints on HR breakout session such as Subscribed HR breakout session AMBR. + +## 6.27 Solution 27 (KI#1): EAS discovery with dynamic setup of a LBO PDU Session + +### 6.27.1 High level description + +The solution addresses a scenario where the UE accesses EHE in VPLMN via a LBO PDU Session. + +UE initially connects to the HPLMN. The transition from a HR PDU Session to a LBO PDU Session takes place based on a trigger to the H-SMF, which may be e.g. a DNS query from the UE towards an EC FQDN or an AF influence of traffic routing for the UE. The latter may be issued by an AF of the VPLMN too. H-SMF determines that a LBO PDU Session to the VPLMN is needed, based on: + +- Information provided by VPLMN at PDU Session Establishment, like indication of support for Dynamic set up of LBO for the PDU Session and information related to supported edge computing applications, i.e. Application IDs, or FQDN ranges; +- the FQDN in the UE DNS query and EDI available in HPLMN for the given FQDN, where the DNAI is relevant for a certain PLMN in the EDI, i.e. there is an associated information in the EDI stating which PLMN is relevant for the DNAI; +- the DNAI in the N6 routing information in the AF influence of traffic routing, where the DNAI has associated PLMN information; +- policy information available in the H-SMF (that could be provided by H-PCF) regarding the requested FQDN or DNAI. + +Then, H-SMF sends a LBO session authorization indication to the AMF via V-SMF – optionally including a DNAI e.g. if previously received from the AF in the N6 routing information – and then it requests the PDU Session release with indication that PDU Session re-establishment to the same DN is required. + +NOTE 1: The LBO session authorization indication overrides the subscription data. + +NOTE 2: The HPLMN ensures that there are no URSP rules in the UE conflicting with the LBO authorization for this PDU Session, e.g. no other traffic that requires HR PDU Session should be mapped to the same DNN and S-NSSAI that could be authorized for LBO. If the information related to supported Edge Computing applications sent by the VPLMN is in collision with the current URSP rules in HPLMN for some application, then the HPLMN can just omit this information and not authorize the PDU Session for LBO for the given application. + +NOTE 3: Terminating the HR PDU Session before establishing the LBO PDU Session as in SSC#2 impacts the ongoing traffic on that PDU Session, e.g. TCP connections break and QUIC connections are interrupted until the connectivity is re-established on the new LBO PDU Session. + +The AMF decides to set up a LBO PDU Session for the next UE PDU Session establishment request from the UE for the same DNN and S-NSSAI, based on the authorization indication received from the H-SMF. Then it selects V-SMF based on internal configuration or target DNAI received and it also conveys a target DNAI to V-SMF corresponding to the DNAI received from H-SMF. The V-SMF selects a PSA based on the DNAI information received from AMF (if available) or based on policy information and may also configure a V-EASDF if dynamic EAS discovery is to be used. + +NOTE 4: An LBO PDU Session can be established for this DNN, and it is assumed that configuration in VPLMN for this DNN has been set accordingly. + +The solution requires a H-EASDF is selected for this HR PDU Session in HPLMN for the case of LBO PDU Session dynamically triggered by DNS EAS discovery and EAS discovery can be applied for all connectivity models in V-PLMN, in the following way: + +- in case of Distributed anchor and Multiple PDU Sessions connectivity models, the V-SMF selects a local anchor to the UE's current location based on policies for this DNN. EAS (re-)discovery happens as described in clause 6.2.2 of TS 23.548 [3]; +- in case of Session Breakout, the V-SMF selects an UL-CL/BP and local anchor based on: + +- the DNAI received from the AF in the AF influence of traffic routing if a DNAI for an N6 routing is specified; or +- the FQDN of a subsequent UE DNS query, as described in clause 6.2.3.2.2 in TS 23.548 [3]. + +V-SMF may initiate termination of the LBO PDU Session if traffic ceases towards the EHE. + +## 6.27.2 Procedures + +The solution is shown in figure 6.27.2-1 below. + +![Sequence diagram illustrating EAS discovery in VPLMN with dynamic setup of a LBO PDU Session. The diagram shows interactions between UE, UPF2, UPF1, AMF, V-SMF, H-SMF, H-EASDF, H-PCF, and AF. The process involves HR PDU session establishment, DNS EAS discovery, AF request on traffic routing, H-SMF determination of LBO, and PDU Session Change from HR to LBO.](b49477e8f148b5ef044a2fd5a43528f6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UPF2 + participant UPF1 + participant AMF + participant V-SMF + participant H-SMF + participant H-EASDF + participant H-PCF + participant AF + + Note over UE, H-EASDF: 1. HR PDU session establishment to H-SMF and UPF1 (Clause 4.3.2.2.2 of TS 23.502) and H-EASDF context creation and update (Clause 6.2.3.2.2 of TS 23.548, Step 1 - 6) + Note over UE, H-SMF: 2a. DNS EAS discovery triggers notification to H-SMF (Clause 6.2.3.2.2 of TS 23.548, Step7 - 11) + Note over H-PCF, H-SMF: 2b. AF request on traffic routing (Clause 4.3.6.2 or 4.3.6.4 of TS 23.502) with policy update to SMF (Clause 4.16.5 of TS 23.502) + Note over H-SMF: 3. H-SMF determines that a LBO to VPLMN is needed + Note over H-SMF, V-SMF: 4. Nsmf_PDUSession_StatusNotify + Note over V-SMF, AMF: 5. Nsmf_PDUSession_SMContextStatusNotify + Note over UE, UPF2: 6. PDU Session Change from HR (UPF1) to LBO (with UPF2) + +``` + +Sequence diagram illustrating EAS discovery in VPLMN with dynamic setup of a LBO PDU Session. The diagram shows interactions between UE, UPF2, UPF1, AMF, V-SMF, H-SMF, H-EASDF, H-PCF, and AF. The process involves HR PDU session establishment, DNS EAS discovery, AF request on traffic routing, H-SMF determination of LBO, and PDU Session Change from HR to LBO. + +**Figure 6.27.2-1: EAS discovery in VPLMN with dynamic setup of a LBO PDU Session** + +1. HR PDU Session Establishment to H-SMF and UPF1, according to the procedure described in clause 4.3.2.2.2 of TS 23.502 [9] with the difference that AMF or V-SMF, based on configuration, sends indication to support Dynamic set up of LBO for this PDU Session. Optionally, based on configuration, V-SMF also sends information related to supported edge computing applications, i.e. Application IDs, or FQDN ranges. In case of dynamic setup of a LBO PDU Session by DNS, allocation of an H-EASDF and sending rules to the EASDF also happens according to steps 1-6 in the clause 6.2.3.2.2 for EAS Discovery Procedure with EASDF for Session Breakout connectivity model in TS 23.548 [3]. +- 2a. [Conditional] The UE sends a DNS Query message for an FQDN to the EASDF via Central PSA. Steps 7-11 in the procedure in clause 6.2.3.2.2 in TS 23.548 [3] for EAS Discovery Procedure with EASDF for Session breakout Connectivity are applied. That is, the H-EASDF checks the DNS Query against the DNS Handling Rules in the DNS Context and reports to H-SMF. +- 2b. [Conditional] The AF sends a request on traffic routing for the UE as specified in clauses 4.3.6.2 or 4.3.6.4 of TS 23.502 [9], impacting the existing PDU Session. Therefore, H-PCF updates the H-SMF with corresponding new policy information about the PDU Session by invoking Npcf\_SMPolicyControl\_UpdateNotify service operation as described in steps 5 and 6 in clause 4.16.5 of TS 23.502 [9]. +3. Based on either 2a or 2b, H-SMF determines that an LBO PDU Session to the VPLMN is needed, as described in clause 6.27.1 above. If 2a, H-SMF removes the Session Context in H-EASDF and the DNS Query is discarded. +4. H-SMF invokes Nsmf\_PDUSession\_StatusNotify service operation to the V-SMF, sending an indication that LBO is authorized for the next PDU Session establishment for this UE, DNN and S-NSSAI, and optionally also sending a target DNAI to the AMF for the local PSA to be selected for the next PDU Session request from the UE for the same DNN and S-NSSAI. H-SMF sends an "AMF acknowledgment requested" indication within this message and a validity indication that shows for how long the AMF should keep the information received and apply it for the next PDU Session. +5. V-SMF invokes Nsmf\_PDUSession\_SMContextStatusNotify service operation to the AMF including the received indication that LBO is authorized and target DNAI. V-SMF acknowledges the notification from step 4 after receiving the AMF acknowledgment to this notification. +6. H-SMF triggers a PDU Session change from HR (UPF1) to LBO (UPF2), using one of the procedures below: + +- SSC#2: H-SMF triggers a HR PDU Session release, as described in clause 4.3.4.3 of TS 23.502 [9]. Indication that PDU Session re-establishment to the same DN is required is included. + +At the next UE request for PDU Session establishment for the same DNN and S-NSSAI, based on the LBO authorization indication and target DNAI received in step 5, AMF decides on a LBO PDU Session establishment towards a proper V-SMF and UPF 2, as specified in clause 4.3.2.2 of TS 23.502 [9]. EAS discovery then happens as described in clause 6.27.1 above. + +- SSC#3: H-SMF triggers a HR PDU Session modification, as described in clause 4.3.3.3 of TS 23.502 [9], where PDU Session ID indicates the existing PDU Session to be relocated and Cause indicates that a PDU Session re-establishment to the same DN is required. A PDU Session Address Lifetime value may also be provided. + +The UE may decide to initiate the PDU Session Establishment request to the same DNN and S-NSSAI described in clause 4.3.2.2 of TS 23.502 [9], with the differences described in clause 4.3.5.2 of TS 23.502 [9]. Based on the LBO authorization indication and target DNAI received in step 5, AMF decides on a LBO PDU Session establishment towards a proper V-SMF and UPF 2, as specified in clause 4.3.2.2 of TS 23.502 [9]. + +The old PDU Session may be released as described in clause 4.3.4.3 either by the UE before the timer provided in step 3 expires (e.g. once the UE has consolidated all traffic on new PDU Session or if the session is no more needed) or by the H-SMF upon expiry of this timer. + +## 6.27.3 Impacts on services, entities and interfaces + +### H-SMF: + +- determines that a LBO PDU Session to the VPLMN is needed for a given UE and PDU Session; +- sends an indication to AMF that LBO is authorized for the next PDU Session establishment and a validity indication. + +### AMF: + +- logic to switch to LBO PDU Session for a PDU Session establishment request based on the LBO authorization and validity indications previously received from the H-SMF via V-SMF. + +### AMF or V-SMF: + +- indication to support dynamic set up of LBO for this PDU Session. + +### V-SMF: + +- sends information related to supported edge computing applications, i.e. Application IDs, or FQDN ranges. + +## 6.28 Solution 28 (KI#1): Support edge computing in Roaming + +### 6.28.1 Description + +#### 6.28.1.1 General + +When the UE powers on in visited PLMN and does not have initial registration, the following procedures are performed: + +- When the UE registers in the visited PLMN, the updated URSP rules is provided by H-PCF via V-PCF. In the updated URSP rules, the EAS IP address which located in the visited PLMN is included, and the URSP rules can trigger to establish an LBO session or apply the application traffic which connects to EAS in visited PLMN by LBO PDU Session. +- If the URSP rules in visited PLMN are not updated timely, or the URSP rules related to EAS in visited PLMN do not exist, the UE should establish the PDU Session either LBO PDU Session or HR PDU Session. The UE should be configured with the DNS server in visited PLMN scenarios and triggers the DNS query of FQDN. + +In the LBO PDU Session, the V-SMF delivers the DNS server IP address to UE via NAS messages. For the HR session, the H-SMF is responsible for configuring the DNS server IP address to UE via NAS messages. + +In the LBO PDU Session, the UE can connect to EAS in visited PLMN via visited local PSA. But for the HR session, after DNS server responds with the DNS response, the home PLMN should trigger a UL-CL insertion for the local breakout session to offload the UE traffic to visited EAS. + +### 6.28.1.2 ECS configuration information Configuration Information configuration in UE + +To support EDGEAPP in SA6, the UE in visited PLMN should receive the ECS configuration information Configuration Information. + +When UE in LBO session, the V-SMF retrieves the UE subscription data in UDM and delivers the ECS configuration information to UE in ePCO. + +When UE in HR session, the H-SMF checks the UE subscription in UDM and retrieves the ECS configuration information. After that, the H-SMF delivers the ECS configuration information to V-SMF, and the V-SMF delivers the ECS configuration information to UE in ePCO. + +All of the ECS configuration information above should be retrieved per VPLMN ID. + +Also, in order to support to establish the LBO PDU Session to ECS, the 5GC can also support to distribute the updated URSP rules to UE. When UE has the traffic towards ECS in visited PLMN, the URSP rules with ECS configuration information can trigger an LBO PDU Session establishment or apply the traffic to LBO PDU Session. + +## 6.28.2 Procedures + +### 6.28.2.1 UE registers in VPLMN and URSP rules updated timely + +![Sequence diagram illustrating the procedure for UE registration and URSP rule updates in VPLMN. The diagram shows interactions between UE, RAN, AMF, V-PCF, H-PCF, V-SMF, V-EASDF, L-PSA, EAS 1, and EAS 2. The process starts with UE power on in visiting PLMN, followed by registration and URSP rule delivery. When traffic is sent to EAS 1, a new LBO PDU session is established. The V-SMF selects V-EASDF, and a NAS procedure delivers the DNS server IP address. The UE applies application traffic from EAS 1 to the LBO PDU session. A DNS query for EAS 2 FQDN is sent, and the V-EASDF handles it. The DNS response (EAS 2 IP address) is returned, and application traffic to EAS 2 is established.](a04f61f63e7b6e8e7fbbe222f0534ce6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant V-PCF + participant H-PCF + participant V-SMF + participant V-EASDF + participant L-PSA + participant EAS 1 + participant EAS 2 + + Note left of UE: 1. UE power on in visiting PLMN + UE->>RAN: + Note over RAN, AMF, V-PCF, H-PCF: 2. UE triggers register procedure; 5GC delivers the URSP rules to UE timely + Note left of UE: 3. UE has traffic to be sent to EAS 1 and the URSP rules related to EAS 1 is existing in UE; No LBO session + UE->>RAN: + Note over RAN, AMF, V-PCF, H-PCF, V-SMF, V-EASDF, L-PSA: 4. PDU session establishment procedure (LBO session) + Note right of V-SMF: 5. V-SMF select V-EASDF + V-SMF->>UE: 6. NAS Procedure to deliver DNS server IP address to UE in roaming + UE->>L-PSA: 7. UE applies application traffic which from EAS 1 to LBO PDU session + L-PSA->>EAS 1: + Note left of UE: 8. DNS Query (EAS 2 FQDN) + UE->>V-EASDF: + Note right of V-EASDF: 9. Same procedure as in R17 for DNS handling rules + V-EASDF->>UE: 10. DNS response (EAS 2 IP address) + UE->>L-PSA: 11. Application traffic to EAS 2 + L-PSA->>EAS 2: + +``` + +Sequence diagram illustrating the procedure for UE registration and URSP rule updates in VPLMN. The diagram shows interactions between UE, RAN, AMF, V-PCF, H-PCF, V-SMF, V-EASDF, L-PSA, EAS 1, and EAS 2. The process starts with UE power on in visiting PLMN, followed by registration and URSP rule delivery. When traffic is sent to EAS 1, a new LBO PDU session is established. The V-SMF selects V-EASDF, and a NAS procedure delivers the DNS server IP address. The UE applies application traffic from EAS 1 to the LBO PDU session. A DNS query for EAS 2 FQDN is sent, and the V-EASDF handles it. The DNS response (EAS 2 IP address) is returned, and application traffic to EAS 2 is established. + +Figure 6.28.2.1-1: UE registers in VPLMN and URSP rules updated timely + +1. UE powers on in roaming PLMN initially. +2. The UE registers into the visiting PLMN, and the URSP rules are delivered from 5GC to UE timely. Some of the URSP rules which related to the EAS located in VPLMN and ECS are provided by 5GC. +3. The application on UE has the traffic to be sent to EAS 1, and the UE uses the URSP rules to trigger a new LBO PDU Session establishment. +4. UE triggers to establish an LBO PDU Session with the parameters that provided by the RSD in URSP rules which the URSP rules is related to EAS 1 located in VPLMN. + +5. During the LBO PDU Session establishment procedure, the V-SMF is responsible for selecting local DNS server (e.g. V-EASDF) for UE in VPLMN. Also, the V-SMF should retrieve the UE subscription data from UDM to obtain the ECS configuration information. Each ECS configuration information is associated with the visiting PLMN ID. The related UPF should be configured with the routing rules to route the UE DNS query to local DNS server. Also, the V-SMF should authorize in UDM that whether the UE can consume the EASDF to discover the EAS in VPLMN. +6. The V-SMF delivers the local DNS server IP address and ECS configuration information to UE in ePCO via DL NAS messages. +7. The IP connection between UE and EAS 1 is established. +8. For EAS 2 deployed in VPLMN, if there is no such URSP rules related to EAS 2 in UE, the UE can only receive the FQDN related to EAS 2 to trigger DNS query towards the local DNS server received from V-SMF via ePCO in step 7. +9. The DNS query is routed to local DNS server via local PSA in VPLMN. If the V-EASDF is selected for the UE in VPLMN, the V-EASDF should use the Rel-17 mechanism to apply the DNS message handling rules to DNS query. +10. The UE receives the DNS response from local DNS server. +11. The IP connection between UE and EAS 2 is established. + +#### 6.28.2.2 UE registers in VPLMN and URSP rules are not updated timely + +If the UE registers to 5GS and the URSP rules which related to the EAS deployed in VPLMN not timely, and the UE has the DNN, S-NSSAI in VPLMN, the UE can only establish an LBO PDU Session with the DNN, S-NSSAI in VPLMN. + +During the LBO PDU Session establishment, the V-SMF delivers the local DNS server IP address and ECS configuration information to UE in ePCO via DL NAS messages. UE triggers the DNS query to local DNS server with the FQDN, and the local DNS server responds with the EAS IP address. + +The overall procedures are similar to the procedure in clause 6.28.2.1 from step 4 to 11 without step 7. + +#### 6.28.2.3 HR session to support Edge computing + +If the UE registers to 5GS and the URSP rules which related to the EAS are deployed in VPLMN not timely, and the UE does not have the DNN, S-NSSAI in VPLMN, the UE can only establish an HR PDU Session with the DNN, S-NSSAI in HPLMN. During the HR session, the edge computing features can be guaranteed. + +In this procedure, it is supposed that the HPLMN can obtain the EDI from VPLMN. + +![Sequence diagram for HR session to support Edge computing. The diagram shows interactions between UE, RAN, AMF, V-UDR, V-UPF, V-SMF, V-NEF, V-PSA, V-NRF, H-UPF, H-SMF, H-NRF, UDM, and H-EASDF. The process includes UE power on, registration, PDU session establishment, SMF selection, UPF selection, PDU session authentication/authorization, H-EASDF selection, Nnrf_NFDiscovery, Nnef_EASDeployment, Nudr_DM, Nsmf_PDUSession, N2 PDU session, RRC reconfiguration, and data flow.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant V-UDR + participant V-UPF + participant V-SMF + participant V-NEF + participant V-PSA + participant V-NRF + participant H-UPF + participant H-SMF + participant H-NRF + participant UDM + participant H-EASDF + + Note left of UE: 1. UE power on + Note left of AMF: 2. UE registers + Note left of UE: 3. UE has DNN, S-NSSAI from HPLMN + Note left of AMF: 4. PDU session establishment request (HR session) + Note left of AMF: 5. SMF selection + Note left of AMF: 6. Nsmf_PDUSession_CreateSMContext Request + Note left of V-SMF: 7. Nsmf_PDUSession_CreateSMContext Response + Note left of V-SMF: 8. UPF selection + Note left of V-SMF: 9. N4 request + Note left of V-UPF: 10. N4 response + Note left of V-SMF: 11. Nsmf_PDUSession_Create Request + Note left of H-SMF: 12. Subscription recovery (ECS address, whether in VPLMN the EC feature is supported) + Note left of H-SMF: 13. PDU session Authentication/Authorization + Note left of H-SMF: 14. H-EASDF selection + Note left of H-SMF: 15. Nnrf_NFDiscovery_Request + Note left of H-NRF: 16. Nnrf_NFDiscovery_Request + Note left of H-NRF: 17. Nnrf_NFDiscovery_Response + Note left of H-SMF: 18. Nnrf_NFDiscovery_Response + Note left of V-NEF: 19. Nnef_EASDeployment_Subscribe Request/Nnef_EASDeployment_Get Request + Note left of V-NEF: 20. Nnef_EASDeployment_Subscribe Response/Nnef_EASDeployment_Get Response + Note left of V-UDR: 21. Nudr_DM_Subscribe (EAS Deployment information) + Note left of V-NEF: 22. Nudr_DM_Notify (EAS Deployment information) + Note left of H-SMF: 23. Nnef_EASDeployment_Notify + Note left of H-SMF: 24. Neasf_BaselineDNSPattern_Create Request + Note left of H-EASDF: 25. Neasf_BaselineDNSPattern_Create Response + Note left of H-SMF: 26. PCF selection + Note left of H-SMF: 27. SM policy association establishment or modification + Note left of H-SMF: 28. UPF selection + Note left of H-SMF: 29. N4 request + Note left of V-UPF: 30. N4 response + Note left of V-SMF: 31. Nsmf_PDUSession_Create Response (ECS address, H-EASDF IP address) + Note left of V-SMF: 32. N4 request + Note left of V-UPF: 33. N4 response + Note left of AMF: 34. Nsmf_Communication_N1N2MessageTransfer + Note left of RAN: 35. N2 PDU session request + Note left of UE: 36. RRC reconfiguration + Note left of RAN: 37. ACK + Note left of AMF: 38. Nsmf_PDUSession_UpdateSMContext Request + Note left of V-SMF: 39. N4 request + Note left of V-UPF: 40. N4 response + Note left of AMF: 41. Nsmf_PDUSession_UpdateSMContext Response + Note left of UE: Uplink data + Note left of H-UPF: Downlink data + Note left of H-EASDF: Uplink data + Note left of H-UPF: Downlink data + +``` + +Sequence diagram for HR session to support Edge computing. The diagram shows interactions between UE, RAN, AMF, V-UDR, V-UPF, V-SMF, V-NEF, V-PSA, V-NRF, H-UPF, H-SMF, H-NRF, UDM, and H-EASDF. The process includes UE power on, registration, PDU session establishment, SMF selection, UPF selection, PDU session authentication/authorization, H-EASDF selection, Nnrf\_NFDiscovery, Nnef\_EASDeployment, Nudr\_DM, Nsmf\_PDUSession, N2 PDU session, RRC reconfiguration, and data flow. + +Figure 6.28.2.3-1: HR session to support Edge computing + +The overall procedure in figure 6.28.2.3-1 are similar as the procedure in figure 4.3.2.2.2-1 of TS 23.502 [9], but with the following changes and differences: + +12. The H-SMF retrieves the subscription data in UDM. The subscription data includes two parts. The first one is, whether the UE is authorized for the edge computing service in VPLMN. Some of the traffic should be offloaded in VPLMN, not re-routed to the HPLMN. The second one is, the H-SMF retrieves the ECS configuration information from UDM, per VPLMN. + +14. H-SMF selects the H-EASDF for the UE. + +15-18. Due to the H-SMF should configure the baseline DNS pattern in the H-EASDF or the DNS handling rules, the EDI is required. But the EDI related to VPLMN is stored in V-UDR and the H-SMF should retrieve the EDI in VPLMN. + +The H-SMF triggers the V-NEF discovery to H-NRF using the Nnrf\_NFDiscovery\_Request, and the H-NRF invokes the Nnrf\_NFDiscovery\_Request service to vNRF. The association between H-NRF and V-NRF are referred to the procedure in figure 4.3.2.2.3.3-1 of TS 23.502 [9]. The V-NRF responds with the IP address of V-NEF to H-NRF, to H-SMF. + +19-23. After the V-NEF is discovered, the H-SMF subscribes or gets the EDI from V-UDR via V-NEF. These procedures are similar to the procedure in TS 23.548 [3]. + +24-25. After the retrieving the EDI from VPLMN, the H-SMF configures the baseline DNS pattern towards H-EASDF. + +29. The H-SMF configures the routing rules in H-UPF to route the UE DNS query towards H-EASDF. + +31. The H-SMF responds to V-SMF with Nsmf\_PDUSession\_Create response. In the response, the ECS configuration information and H-EASDF IP address are included. + +### 6.28.2.4 When UE moving into VPLMN and the original EC-session are impacted + +For the situation when the UE moves into the VPLMN and the original EC session will be influenced. The UE should re-discover another EAS from the DNS procedure. + +In order to not stop the traffic and business, the UE should discover a new EAS and performs the EAS relocation procedure. + +The details of the procedure are listed below: + +![Sequence diagram illustrating EAS relocation from EAS in HPLMN to VPLMN. The diagram shows the interaction between UE, RAN, AMF, V-PCF, V-UPF, V-SMF, V-EASDF, V-PSA, EAS 1, H-UPF, H-SMF, H-EASDF, UDM, and EAS 2. The process involves UE roaming to VPLMN, HR session establishment, NAS indication to refresh DNS cache, DNS cache clearing, DNS query and response, and finally EAS relocation.](034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant V-PCF + participant V-UPF + participant V-SMF + participant V-EASDF + participant V-PSA + participant EAS 1 + participant H-UPF + participant H-SMF + participant H-EASDF + participant UDM + participant EAS 2 + + Note left of UE: 1. UE roaming to VPLMN + UE->>RAN: + Note right of RAN: 2. HR session + RAN->>AMF: Uplink data + AMF->>V-UPF: Uplink data + V-UPF->>V-SMF: Uplink data + V-SMF->>V-EASDF: + V-EASDF->>V-PSA: Uplink data + V-PSA->>EAS 1: Uplink data + EAS 1->>H-UPF: + H-UPF->>H-SMF: Uplink data + H-SMF->>H-EASDF: Uplink data (via local PSA) + H-EASDF->>UDM: + Note left of UE: 3a. NAS indication to refresh the DNS cache and DNS rediscvery + V-SMF->>AMF: + AMF->>RAN: + RAN->>UE: + Note left of UE: 3b. The IP of session is changed + Note left of UE: 4. DNS cache is clear + Note left of UE: 5. DNS Query and response + UE->>H-EASDF: + Note right of H-EASDF: 6. EAS relocation + H-EASDF->>UDM: + UDM->>H-EASDF: + H-EASDF->>H-SMF: + H-SMF->>H-UPF: + H-UPF->>EAS 2: + EAS 2->>V-PSA: Uplink data + V-PSA->>V-EASDF: Downlink data + V-EASDF->>V-SMF: + V-SMF->>V-UPF: Downlink data + V-UPF->>AMF: + AMF->>RAN: + RAN->>UE: + +``` + +Sequence diagram illustrating EAS relocation from EAS in HPLMN to VPLMN. The diagram shows the interaction between UE, RAN, AMF, V-PCF, V-UPF, V-SMF, V-EASDF, V-PSA, EAS 1, H-UPF, H-SMF, H-EASDF, UDM, and EAS 2. The process involves UE roaming to VPLMN, HR session establishment, NAS indication to refresh DNS cache, DNS cache clearing, DNS query and response, and finally EAS relocation. + +Figure 6.28.2.4-1: EAS relocation from EAS in HPLMN to VPLMN + +1. The UE is the status of roaming in VPLMN, and the original PDU Session to EAS in HPLMN are influenced, for example, the EAS in HPLMN becomes suboptimum for UE to connect. +2. The HR session is established to continue the old PDU Session to EAS in HPLMN. +- 3a. The 5GC triggers an indication to UE to refresh the DNS cache that the old cache still reflects the mapping table between FQDN and EAS IP address located in HPLMN. +- 3b. If the HR session changes the IP address of PDU Session, for example, due to the relocation of PSA in HPLMN and the IP address of PDU Session is changed, the UE refreshes the DNS cache stored in HPLMN. +4. The DNS cache is cleared or refreshed. +5. The UE triggers a new DNS query with the FQDN towards the local DNS server or H-EASDF. +6. The old EAS deployed in HPLMN relocates to the new EAS located in VPLMN. + +### 6.28.3 Impacts on services, entities and interfaces + +H-SMF: + +- retrieves the EDI from V-UDR via V-NEF; +- retrieves the indication of whether the EC feature is supported in VPLMN and ECS address from UDM. + +V-UDR: + +- supports to provide the EDI in VPLMN to HPLMN. + +V-SMF: + +- supports to retrieve the ECS address from UDM; +- delivers the DNS server IP address to UE via NAS messages. + +UDM: + +- stores the ECS configuration information by PLMN basis. + +## 6.29 Solution 29 (KI#3): Use of Internal Group ID and constraints in EDI + +### 6.29.1 High level description + +To identify a finer granularity of UEs, Internal Group ID is to be used. There is no practical limit for how many Internal group IDs that can be assigned in a 5GS. The structure of an Internal Group ID is as follows: + +![Figure 6.29.1-1: Internal Group ID structure diagram. The diagram shows a horizontal bar labeled 'Internal Group Identifier' at the top. Below it, four boxes represent the components of the ID: '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). Arrows indicate the length of each component.](99a0eddf16e836f411661acee6facd17_img.jpg) + +Figure 6.29.1-1: Internal Group ID structure diagram. The diagram shows a horizontal bar labeled 'Internal Group Identifier' at the top. Below it, four boxes represent the components of the ID: '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). Arrows indicate the length of each component. + +Figure 6.29.1-1: Internal Group ID structure + +A UE can be associated with a number of Internal Group IDs as per TS 23.501 [2]. Stage 3 has not specified any limit for how many internal groups a UE can be associated with. + +To support different constraints related to EC, the solution uses EDI, which is enhanced with a constraints field that tells under which constraints the EDI record applies. The EDI can be provisioned by an operator through OAM to UDR (or via NEF) or the EDI can be provided by an AF. + +Example of the updated EDI from table 6.2.3.4-1 in TS 23.548 [3]: + +Table 6.29.1-1: EDI parameters + +| Parameters | Description | +|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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]
NOTE: 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. | +| Application ID | Identifies the application for which the EAS Deployment Information corresponds to.
[optional] | +| Constraints | When and where this EDI applies
Example:
Time: 08:00-17:00
Place: TAI-list | +| FQDN(s) | Supported FQDN(s) for application(s) deployed in the Local part of the DN. | +| 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(s) of the EASs in the local DN for each DNAI.
[optional] | + +NOTE: External/Internal Group IDs in this solution are all provisioned via OAM procedures to UDM. + +## 6.29.2 Impacts on services, entities and interfaces + +### SMF: + +- needs to take the constraints into account when constructing DNS handling rules to EASDF, and action taken when EASDF notifies SMF due to a DNS handling rule. + +### UDR: + +- new data in EDI. + +### NEF: + +- Nnef\_EASDeployment service: new data in EDI. + +### AF: + +- new data in EDI. + +## 6.30 Solution 30 (KI#3): Policies referring to "Allowed services" and/or "Subscriber categories" + +### 6.30.1 Description + +The solution aims at supporting AF request for specific traffic routing (as defined for Nnef\_TrafficInfluence\_Create / Update in clause 5.6.7 of TS 23.501 [2]) targeting a category of users or users having subscribed to specific services (basically for users having subscribed to specific tariff plans). + +NOTE 1: Very local traffic offload can be expensive (the more locally CPU is deployed, e.g. to support EAS, the more expensive this CPU is) and it may be useful to apply very local offload only for users with specific tariff plans (e.g. users having subscribed to a "game boost" offer). The goal is also to avoid the burden to define dedicated DNN and/or slices for these cases. + +AF guidance is needed as it is the AF that knows the relative cost of deploying very local EAS capabilities. + +The solution adds a new kind of targets (beyond a UE, a group of UE, Any UE) for AF requests for traffic routing Nnef\_TrafficInfluence\_Create/Update where this new kind of targets may correspond to one of "Allowed services" and/or "Subscriber categories" as defined in TS 23.503 [13] table 6.2-2: PDU Session policy control subscription information. + +The AF requests is provided to the PCF as defined in clause 4.3.6.2 of TS 23.502 [9]. When the SMF invokes an SM Policy Association Establishment as defined in clause 4.16.4 of TS 23.502 [9], the PCF looks up the UDR to check whether the corresponding user subscription maps to one of "Allowed services" and/or "Subscriber categories" of the AF policies received by the PCF (from the UDR as defined in clause 4.3.6.2 of TS 23.502 [9]). + +Allowed services and Subscriber categories as defined in table 6.2-2 of TS 23.503 [13] cannot be sent on roaming interfaces as they refer to subscription plans of a given operator; this is not an issue as Nnef\_TrafficInfluence\_Create/Update and NWDAF services are not defined on roaming interfaces. + +An external AF (an AF from a third party with no specific agreement with the 5GC operator) cannot use "Allowed services" and/or "Subscriber categories" targets whose set of values are not defined by 3GPP and left for deployment definition (values defined by the 5GC operator). The NEF may have local policies allowing it to map the information included in an AF request from an external AF to identify the more granular sets of UE(s) into operator defined "Allowed services" and/or "Subscriber categories" values. The information included in an AF request to identify the more granular sets of UE(s) can include AF identifier and/or MTC Provider Information (identifying the MTC/non-MTC Service Provider and/or MTC/non-MTC Application). + +NOTE 2: NOTE 5 in clause 4.15.6.10 of TS 23.502 [9] states "The MTC Provider Information can be used by any type of Service Providers (MTC or non-MTC) or Corporate or External Parties for, e.g. to distinguish their different customers". So, the MTC Provider Information can also be used to carry information for non-MTC service. + +NOTE 3: Different values of the allowed services parameter (in PCF subscription data stored in UDR) can based on local operator configuration to distinguish between subscription allowing to benefit from edge computing or even from deep edge computing (using more expensive compute resources at the RAN site) from subscription not allowing not to benefit from edge computing for some services. For example, the operator may associate some "game boost" tariff plan with values of the allowed services parameter in PCF subscription data (stored in UDR) allowing the users to have a better gaming experience as the gaming application they would use would be very local. + +## 6.30.2 Procedures + +Clause 4.3.6.2 of TS 23.502 [9] "Processing AF requests to influence traffic routing for Sessions not identified by an UE address" is modified as described below: + +![Sequence diagram showing the processing of AF requests to influence traffic routing for sessions not identified by an UE address. The diagram involves seven lifelines: AMF, UPF/EASDF, SMF, PCF(s), UDR, NEF, and AF. The sequence starts with the AF creating a request, which is sent to the NEF via Nnef_TrafficInfluence_Create/Update/Delete. The NEF then sends a response to the AF via Nnef_TrafficInfluence_Create/Update/Delete Response. The NEF also sends a message to the UDR via Nudr_DM_Notify. The UDR then sends a message to the PCF(s) via Npcf_SMPolicyControl_UpdateNotify. The PCF(s) then sends a message to the SMF via Nsmf_PDUSession_SMContextStatusNotify. The SMF then sends a message to the UPF/EASDF via Traffic Routing Reconfiguration. Finally, the SMF sends a message to the AMF via Nsmf_PDUSession_SMContextStatusNotify.](427095219f3706148e8c03f1013eaec8_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDR + participant PCF(s) + participant SMF + participant UPF/EASDF + participant AMF + + Note right of AF: 1. Creation of the AF request + AF->>NEF: 2 Nnef_TrafficInfluence_Create / Update / Delete + Note right of NEF: 3a. Storing/Updating/Removing the information + NEF->>AF: 3b. Nnef_TrafficInfluence_Create / Update / Delete Response + NEF->>UDR: 4. Nudr_DM_Notify + UDR->>PCF(s): 5. Npcf_SMPolicyControl_UpdateNotify + Note right of SMF: 6. Traffic Routing Reconfiguration + SMF->>AMF: 7. Nsmf_PDUSession_SMContextStatusNotify + +``` + +Sequence diagram showing the processing of AF requests to influence traffic routing for sessions not identified by an UE address. The diagram involves seven lifelines: AMF, UPF/EASDF, SMF, PCF(s), UDR, NEF, and AF. The sequence starts with the AF creating a request, which is sent to the NEF via Nnef\_TrafficInfluence\_Create/Update/Delete. The NEF then sends a response to the AF via Nnef\_TrafficInfluence\_Create/Update/Delete Response. The NEF also sends a message to the UDR via Nudr\_DM\_Notify. The UDR then sends a message to the PCF(s) via Npcf\_SMPolicyControl\_UpdateNotify. The PCF(s) then sends a message to the SMF via Nsmf\_PDUSession\_SMContextStatusNotify. The SMF then sends a message to the UPF/EASDF via Traffic Routing Reconfiguration. Finally, the SMF sends a message to the AMF via Nsmf\_PDUSession\_SMContextStatusNotify. + +**Figure 6.30.2-1: Processing AF requests to influence traffic routing for Sessions not identified by an UE address** + +- In step 1, the target of the AF request may refer a set of UEs as described in clause 6.30.1. +- In step 3 and 4, the data stored in UDR and the information sent to the PCF may refer to one of "Allowed services" and/or "Subscriber categories" as defined in TS 23.503 [13] table 6.2-2. + +Clause 4.3.6.2 of TS 23.502 [9] "SM Policy Association Establishment" is modified as follows: + +![Sequence diagram for SM Policy Association Establishment. Lifelines: SMF, PCF, UDR, CHF. The sequence starts with SMF sending '1. Npcf_SMPolicyControl_Create' to PCF. PCF then sends '2. Nudr_DM_Query & Nudr_DM_Subscribe' to UDR. UDR responds with a dashed return arrow. PCF then sends '3. Initial Spending Limit Report Retrieval' to CHF. CHF returns '4. Policy decision' to PCF. Finally, PCF sends '5. Npcf_SMPolicyControl_Create Response' back to SMF.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant PCF + participant UDR + participant CHF + Note right of PCF: 3. Initial Spending Limit Report Retrieval + Note right of PCF: 4. Policy decision + SMF->>PCF: 1. Npcf_SMPolicyControl_Create + PCF->>UDR: 2. Nudr_DM_Query & Nudr_DM_Subscribe + UDR-->>PCF: + PCF->>CHF: 3. Initial Spending Limit Report Retrieval + CHF-->>PCF: 4. Policy decision + PCF->>SMF: 5. Npcf_SMPolicyControl_Create Response + +``` + +Sequence diagram for SM Policy Association Establishment. Lifelines: SMF, PCF, UDR, CHF. The sequence starts with SMF sending '1. Npcf\_SMPolicyControl\_Create' to PCF. PCF then sends '2. Nudr\_DM\_Query & Nudr\_DM\_Subscribe' to UDR. UDR responds with a dashed return arrow. PCF then sends '3. Initial Spending Limit Report Retrieval' to CHF. CHF returns '4. Policy decision' to PCF. Finally, PCF sends '5. Npcf\_SMPolicyControl\_Create Response' back to SMF. + +**Figure 6.30.2-2: SM Policy Association Establishment** + +- In step 2, the PCF looks up the UDR PDU Session policy control subscription information as defined in table 6.2-2 of TS 23.503 [13] to check whether the corresponding user subscription maps to one of "Allowed services" and/or "Subscriber categories" of the AF policies received by the PCF as defined in clause 4.3.6.2 of TS 23.502 [9]. If there is a match, the PCF uses this information of the AF policies for its policy rules determination. + +### 6.30.3 Impacts on Existing Nodes and Functionality + +AF and NEF: + +- support the new target ("Allowed services" and/or "Subscriber categories") in Nnef\_TrafficInfluence\_Create / Update in clause 5.6.7 of TS 23.501 [2]. + +UDR: + +- storage of the new target type of "Allowed services" and/or "Subscriber categories" in data set "Application data" and Data Subset "AF traffic influence request information". + +PCF: + +- looks up the UDR PDU Session policy control subscription information defined in table 6.2-2 of TS 23.503 [13] to check whether the user subscription corresponding to a SM Policy Association maps to one of "Allowed services" and/or "Subscriber categories" received from the "AF traffic influence request information" policies in UDR. + +## 6.31 Solution 31 (KI#3): Providing traffic offload policy for a set of UEs with service information + +### 6.31.1 Description + +To provide the traffic routing policy for a set of UEs at a finer granularity, the set of UEs at a finer granularity can be identified using a pre-defined group of UEs or a dynamic group of UEs. The set of UEs can be decided by the network administrator or by the application. For example, the set of UEs can be a pre-defined group which is configured by the operator. The set of UEs can be decided by the application side. For example, only certain users under certain conditions can access the application with edge computing service due to limited or expensive EC resource, considering the service agreement among the EC provider(s), application provider, network provider and the users. The set of UEs can be decided dynamically when the related conditions are met, e.g. the application client with specific service level can use edge computing service under certain conditions. + +For providing the traffic routing policy for a set of UEs within a pre-defined group, or a dynamic group reusing 5G VN group management mechanism as defined in clause 6.14, it can be implemented using Application Function influence on traffic routing procedure targeting a group of UEs. + +For providing the traffic routing policy for a set of UEs with associated with the same service information, e.g. the same application client category, it can be implemented reusing the existing Application Function influence on traffic routing mechanism with additionally including the following: + +- The traffic routing policy information is provisioned associated a set of UEs with the same service information. +- The UE accessing the application with the matched Service information can apply the traffic routing policy information provisioned associated a set of UEs with the service information. + +NOTE: The service information, for example, can be Target Category information that is an abstract value associated with 1) Allowed services for accessing applications with additional conditions e.g. allowed applications to be accessed, allowed application to be accessed using edge computing; or 2) Subscriber categories of the UE defined by the operator or of application users defined by the application provider, or 3) other service information acting as condition to group the set of UEs, e.g. the application decided service information such as application level client category for the application clients. + +### 6.31.2 Procedures + +The following figure shows the solution providing the traffic routing policy for a set of UE with associated with the same service information. + +![Sequence diagram illustrating traffic routing policy provisioning for a set of UE with associated service information. The diagram shows interactions between UE, L-UPF, C-UPF, SMF, PCF(s)/NEF, UDM/UDR, EAS, and AF/AS. It details two scenarios: one where service information is matched and another where it is not, leading to different traffic routing decisions.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant L-UPF + participant C-UPF + participant SMF + participant PCF as PCF(s)/NEF + participant UDR as UDM/UDR + participant EAS + participant AF as AF/AS + + Note left of UE: 0.Session Establishment with C-UPF + UE->>SMF: + Note right of SMF: 2. SMPolicyControl (No service information matched, the related TRI is not sent to the SMF for the PDU session) + Note right of PCF: 1.AF requests to influence traffic routing, targeting UE(s) with service information + Note left of UE: 3. Application Client with service information requests the IP address of app server and logs in, the User-plane communication takes place between the Application Client in UE and Application Server via the C-UPF. + Note right of PCF: 4. Service specific parameter provisioning( AppID, UE IP, service information ) + Note right of SMF: 5. service information matched, the related TRI is sent to the SMF for the PDU session + Note right of SMF: 6. SMPolicyControl (service information matched, the related TRI is sent to the SMF for the PDU session) + Note left of UE: 7. UE enters the EDN Service Area + Note right of SMF: 8.SMf establishes ULCL and L-UPF for local access + Note right of PCF: 9a. Nsmf_EventExposure_Notify (DNAI change) + Note right of PCF: 9b. smf_EventExposure_AppRelocationInfo + Note right of SMF: 10.Updates C-UPF + Note left of UE: 11. User-plane communication takes place between the Application Client in UE and Edge Application Server via the local UPF. + Note left of UE: 12. The AC with service information logs out of the application or the IP flows Of the application are terminated. + Note right of PCF: 13. Service specific parameter deleting ( AppID, UE IP, service information ) + Note right of SMF: 14. service information matched, the related TRI is removed to the SMF for the PDU session + Note right of SMF: 15. SMPolicyControl (service information is removed, the related TRI is not sent to the SMF for the PDU session) + Note left of UE: 16. Application Client without service information requests the IP address of app server and logs in, the User-plane communication takes place between the Application Client in UE and Application Server via the C-UPF. + Note right of SMF: 17. SMPolicyControl (No service information matched, the related TRI is not sent to the SMF for the PDU session) + Note left of UE: 18. For Application Client without service information, the User-plane communication takes place between the Application Client in UE and Application Server via the C-UPF, no traffic routing to the local EAS is performed. + +``` + +Sequence diagram illustrating traffic routing policy provisioning for a set of UE with associated service information. The diagram shows interactions between UE, L-UPF, C-UPF, SMF, PCF(s)/NEF, UDM/UDR, EAS, and AF/AS. It details two scenarios: one where service information is matched and another where it is not, leading to different traffic routing decisions. + +**Figure 6.31.2-1 Traffic routing policy provisioning for a set of UE with associated service information** + +0. The UE initiates the PDU Session establishment procedure. +1. AF request with traffic routing information is sent to the PCF targeting UE(s) with service information. For the Target UE Identifier(s), the service information, acting as the criteria to identify the UE(s) that the request is targeting, so the traffic routing information can only be applied to the PDUs which are allowed to access the application with service information. The related information is sent via NEF and stored in the UDR, and delivered to the PCF following the existing Application Function influence on traffic routing procedure. Data Key = AF Transaction Internal ID, S-NSSAI and DNN and the service information for the application. For + +management of the targeting UE(s) with specific service information for the application(s), the specific internal group ID may be allocated by the UDM corresponding to the targeting UEs with specific service information as which is done for the 5G VN group management. + +2. The SMF retrieves the SM policy using SM Policy Association Establishment procedure during the PDU Session establishment procedure. The traffic routing information for the specific application in step 1 is not sent to the SMF for the PDU Session because no service information matched. +3. Application Client with service information requests the IP address of app server and logs in, the user-plane communication takes place between the Application Client in UE and Application Server via the C-UPF. In this step, the application layer can decide that the service information the application client associated with based on the configuration or application subscription information. +4. Optionally, the AF gets the service information for the accessing application client reusing the procedure of Service specific parameter provisioning defined in clause 4.15.6.7 of TS 23.502 [9] one of the following procedures with service information. If the internal group ID is associated with UE for the accessing application client, the internal group ID is stored as information of the subscription data of the UE. + +NOTE: The service information in this solution is notified to the SM-PCF to influence the PCC Rules instead of AM-PCF delivered to the UE as defined in clause 4.15.6.7 of TS 23.502 [9]. + +- 5-6. The PCF makes the decision to modify the SM policy for the application within the PDU Session based on the traffic routing information targeting the set of UEs received in step 1, and the related information for the PDU Session including "Allowed services" and/or "Subscriber categories" as defined in "PDU Session policy control subscription information" in TS 23.503 [13] table 6.2-2 and/or the service information for the PDU Session received in step 4, and the routing policy related to the traffic routing information is sent to the SMF. +7. The UE enters the service area of the edge DN. +- 8-10. The SMF decides to establish a new PDU Session Anchor e.g. due to UE mobility as described in step 7, and based on the latest traffic routing policy received in step 6. +11. User-plane communication takes place between the Application Client in UE and Edge Application Server via the local UPF. +- 12-13. The AF decides to delete the service specific parameter, e.g. when the AC with service information logs out of the application or the IP flows of the application are terminated. The delete procedure is similar to the create procedure described in step 4, the only difference is that it is to delete the related information. +- 14-15. The PCF makes the decision to modify the SM policy for the application within the PDU Session, and the related traffic routing policy is deleted in the SMF. +- 16-18. If another Application Client without service information requests the IP address of app server and logs in in the PDU Session of the UE, the User-plane communication takes place between the Application Client in UE and Application Server via the C-UPF. As there is no related traffic routing information matched for this application client, no traffic routing policy is applied to the application for this UE in this case. + +### 6.31.3 Impacts on services, entities and interfaces + +The following impacts are involved to support providing the traffic routing policy for a set of UE associated with the same service information: + +#### AF/NEF/UDR: + +- service information is supported while providing traffic routing policy information in the procedure of AF influence traffic routing, wherein the service information can be the Target Category information associated with "Allowed services" and/or "Subscriber categories" and/or the application decided service information such as application level client category; +- service information of the UE accessing the application is optionally provided using the procedure of Service specific parameter provisioning. + +#### PCF: + +- the traffic routing policy for a set of UE associated with service information is received; + +- service information of the UE accessing the application is notified; +- associates the UE accessing the application with the set of UEs using Service information, and sends the PCC rule to the SMF for the PDU Session of the UE with the traffic routing policy information provisioned associated a set of UEs with the service information. + +## 6.32 Solution 32 (KI#3): Offload policy for finer granular set of UEs + +### 6.32.1 Description + +This solution corresponds to KI#3, which addresses offload policy for finer granular set of UEs related to: + +- how to identify set of UEs at a finer granularity that are associated with a dedicated offload policy, and how to express the set of UE in the offload policy; +- impacts to 5GS needed to support providing traffic offload policy for such a set of UEs. + +Based on the existing traffic influence procedure, this solution introduces "subscribed services", which is used for expressing a set of UEs at a finer granularity, and the Spatial Validity Condition and Temporal Validity Condition in AF request is reused for expressing location and time period for definition of set of UEs. + +The "subscribed services" includes logical combination of criteria, for instance: + +- Allowed Service#1 AND Allowed Service#2; +- Group#1 AND Group#2; +- Allowed Service#1 AND Group#1; +- Group#1 AND (NOT Group#2); +- Subscriber category#1 AND Group#1; +- PLMN ID (the offload policy is to UEs subscribed to PLMN identified by PLMN ID); +- etc. + +The criterion (e.g. Allowed Service, Subscriber category, Group ID etc) is maintained in UE subscription, and when the "subscribed services" is included in traffic influence, then the traffic influence applies to UE(s) whose subscription information matching with the "subscribed services" logically, for example, the "subscribed services" is "Allowed Service#1 AND Group ID#1" then traffic influence is for UEs whose subscription including both Allowed Service#1 and Group ID#1; the "subscribed services" is "Allowed Service#1 AND (NOT Group ID#1)", then traffic influence is for UEs whose subscription including Allowed Service#1 but not Group ID#1. + +NOTE 1: If one criterion belongs to MNO's internal information, then it could only be used by an AF belonging to the MNO. + +### 6.32.2 Procedures + +The following is the procedure for providing traffic offload policy to UEs matching with "subscribed service". + +The procedure of "Processing AF requests to influence traffic routing for Sessions not identified by an UE address" as defined in clause 4.3.6.2 of TS 23.502 [9] is reused with the following updates: + +- in step 2: AF includes "subscribed services" in the AF request. The "subscribed services" can be indicated, for example, by including one or more of the following information or by other means: + - Allowed Service; + - Subscriber category; + - Group ID; + +- PLMN ID. +- in step 5: Based on received AF request, PCF creates PCC rule for UEs whose subscription information matching with the "subscribed services", for example, the "subscribed services" is "Allowed Service#1 AND Group ID#1", then PCC rule is created for UEs whose subscription including both Allowed Service#1 and Group ID#1; the "subscribed services" is "Allowed Service#1 AND (NOT Group ID#1)", then PCC rule is created for UEs whose subscription including Allowed Service#1 but not Group ID#1. + +### 6.32.3 Impacts on services, entities and interfaces + +AF, NEF, PCF and UDR is to be updated for supporting "subscribed services". + +Nnef\_TrafficInfluence Service is extended with new parameter "subscribed services". + +## 6.33 Solution 33 (KI#3): AF requests offload policy for sets of UEs + +### 6.33.1 Description + +The following solution corresponds to the key issue #3 on Policies for finer granular sets of UEs as specified in clause 5.3. + +It is using the AF influence traffic mechanism to route the traffic for a collection of UEs. The AF provides the Category information in AF request to indicate which information elements (e.g. Spatial Validity Condition, Application Identifier, FQDN range, Temporal Validity Condition, Target UE Identifier) are used to determine the collection of UEs for traffic offload. + +The information elements defined in clause 5.6.7 in TS 23.501 [2] can be reused, the categories include: + +- Category 1: Spatial Validity Condition (Area of Interest, geographical area etc.), e.g. the traffic routing mechanism is applied to the UEs located in the same Area of Interest. +- Category 2: Application Identifier/FQDN range, e.g. the traffic routing mechanism is applied to the UEs that are using the same application. +- Category 3: Temporal Validity Condition, e.g. the traffic routing mechanism is applied to the UEs that use the same application during the specific time interval. +- Category 4: Target UE Identifier(s), e.g. the traffic routing mechanism is applied to the UEs that are associated with a specific External Group Identifier. + +Other categories: combinations of category 1-4, it may include: + +- Category 5: Spatial Validity Condition AND Application Identifier/FQDN range, e.g. the traffic routing mechanism is applied to the UEs located in the same Area of Interest and using the same application. +- Category 6: Combination of different groups, e.g. UEs that are associated with both External Group Identifier A and External Group Identifier B. +- etc. + +Based on the Category information in AF request, the PCF generates PCC rule(s) and sends it to the SMF. The SMF determines that the UE belongs to the collection of UEs for traffic offload, and reconfigures the UP per PCC rule(s). + +## 6.33.2 Procedures + +![Sequence diagram showing the processing of AF requests to influence traffic routing for sessions associated with a collection of UEs. The diagram involves seven network functions: AMF, UPF/EASDF, SMF, PCF(s), UDR, NEF, and AF. The sequence starts with the AF sending a '1. Creation of the AF request' to the NEF. The NEF then sends a '2 Nnef_TrafficInfluence_Create / Update / Delete' to the UDR. The UDR performs '3a. Storing/Updating/Removing the information' and sends a '3b. Nnef_TrafficInfluence_Create / Update / Delete Response' back to the NEF. The NEF then sends a '4. Nudr_DM_Notify' to the PCF(s). The PCF(s) sends a '5. Npcf_SMPolicyControl_UpdateNotify' to the SMF. The SMF performs '6. Traffic Routing Reconfiguration' and sends a '7. Nsmf_PDUSession_SMContextStatusNotify' to the AMF.](f1ba1e68228ebd4c3109371574a723e6_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UPF/EASDF + participant SMF + participant PCF(s) + participant UDR + participant NEF + participant AF + + Note right of AF: 1. Creation of the AF request + AF->>NEF: 2 Nnef_TrafficInfluence_Create / Update / Delete + Note right of UDR: 3a. Storing/Updating/Removing the information + NEF->>AF: 3b. Nnef_TrafficInfluence_Create / Update / Delete Response + UDR->>PCF(s): 4. Nudr_DM_Notify + PCF(s)->>SMF: 5. Npcf_SMPolicyControl_UpdateNotify + Note right of SMF: 6. Traffic Routing Reconfiguration + SMF->>AMF: 7. Nsmf_PDUSession_SMContextStatusNotify + +``` + +Sequence diagram showing the processing of AF requests to influence traffic routing for sessions associated with a collection of UEs. The diagram involves seven network functions: AMF, UPF/EASDF, SMF, PCF(s), UDR, NEF, and AF. The sequence starts with the AF sending a '1. Creation of the AF request' to the NEF. The NEF then sends a '2 Nnef\_TrafficInfluence\_Create / Update / Delete' to the UDR. The UDR performs '3a. Storing/Updating/Removing the information' and sends a '3b. Nnef\_TrafficInfluence\_Create / Update / Delete Response' back to the NEF. The NEF then sends a '4. Nudr\_DM\_Notify' to the PCF(s). The PCF(s) sends a '5. Npcf\_SMPolicyControl\_UpdateNotify' to the SMF. The SMF performs '6. Traffic Routing Reconfiguration' and sends a '7. Nsmf\_PDUSession\_SMContextStatusNotify' to the AMF. + +**Figure 6.33.2-1: Processing AF requests to influence traffic routing for Sessions associates with a collection of UEs (reuse the figure 4.3.6.2-1 of TS 23.502 [9])** + +The solution reuses the procedure of AF requests to influence traffic routing as described in clause 4.3.6.2 of TS 23.502 [9], with the following enhancements: + +- In step 1, the AF requests the offload policy with Category information that indicates the collection of UEs for traffic offload, and the content of offload policy is as described in clause 6.33.1. +- In step 2, the offload policy is included in the AF request message. +- In step 5, the PCF determines which UE belongs to the collection of UEs for traffic offload and generates PCC rule(s) for PDU Session of UEs in the UE collection based on the Category information in AF request. +- In step 6, based on the received PCC rule(s) from PCF, the SMF reconfigures the User plane of the PDU Session correspondingly. + +## 6.33.3 Impacts on services, entities and interfaces + +AF: + +- provides the Category information in AF request. + +PCF: + +- creates PCC rule based on the Category information. + +## 6.34 Solution 34 (KI#4): Selecting the same EAS/DNAI for collection of UEs + +### 6.34.1 Description + +This solution is based on solution 16, described in clause 6.16. + +This solution uses EDI to make sure a collection defined by an AF uses the same DNAI and/or EAS. By this EDI is updated with EAS address field per DNAI and an indicator if the DNAI is selected for a group. The data in EDI is also updated with a Dynamic External Group Id that can be per DNAI or per application ID. The AF can use the Dynamic External Group ID and external application id to influence routing for a collection of UEs. The dynamic external group id is an identifier that is generated by the AF, i.e. it is not to be confused with the external group id configured in UDM. The AF associates a list of UEs with the dynamic external group id when requesting in AF influence on routing that the list of UEs should be using the same EAS and/or DNAI. + +Example of EDI record before any group has been requested through traffic influence: + +DNN-1/S-NSSAI-1: + +ApplicationID-1 + +FQDN + +DynExtGrID-1 + +DynExtGrID-2 + +DNAI-1 + +DynExtGrID-4 + +DynExtGrID-5 + +DNAI-2 + +DynExtGrID-5 + +etc. + +Example of EDI record before after *some* groups have been requested through traffic influence: + +DNN-1/S-NSSAI-1: + +ApplicationID-1 + +FQDN + +DynExtGrID-1 + +DNAI-55 + +EASaddr-1 + +DynExtGrID-2 + +DNAI-1 + +DynExtGrID-4 + +DNAI selection indicator + +EASaddr-3 + +DynExtGrID-5 + +DNAI-2 + +DynExtGrID-5 + +EASaddr-2 + +## 6.34.2 Procedure + +The following is the procedure for selecting the same EAS for collection of UEs accessing the same application. The procedures defined in figure 4.3.6.2-1 in TS 23.502 [9] and figure 6.2.3.2.2-1 in TS 23.548 [3] are reused. + +![Sequence diagram illustrating the discovery procedure for selecting the same EAS/DNAI for collection of UEs. The diagram shows interactions between UE, EASDF, DNS server, SMF, PCF, UDR, NEF, and AF. The steps are: 1. Provisioning of EDI (AF to UDR); 2. AF request to influence routing (AF to SMF); 3. Steps 1-2 in 6.2.3.3 in TS 23.548 (dashed box, SMF to EASDF/DNS server); 4. Steps 1-9 in 6.2.3.2.2 in TS 23.548 (SMF to EASDF/DNS server); 5. Determine if UE should be part of dynamic group (SMF to PCF); 6. update EAS/DNAI data (dashed box, PCF to UDR/NEF); 7. Steps 10-19 in 6.2.3.2.2 in TS 23.548 (SMF to EASDF/DNS server).](ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EASDF + participant DNS server + participant SMF + participant PCF + participant UDR + participant NEF + participant AF + + Note right of AF: 1. Provisioning of EDI + AF->>UDR: + Note right of AF: 2. Steps 1-5 in AF request to influence routing + AF->>SMF: + Note right of SMF: 3. Steps 1-2 in 6.2.3.3 in TS 23.548 + SMF-->>EASDF: + SMF-->>DNS server: + Note right of SMF: 4. Steps 1-9 in 6.2.3.2.2 in TS 23.548 + SMF-->>EASDF: + SMF-->>DNS server: + Note right of SMF: 5. Determine if UE should be part of dynamic group + SMF->>PCF: + Note right of PCF: 6. update EAS/DNAI data + PCF-->>UDR: + PCF-->>NEF: + Note right of SMF: 7. Steps 10-19 in 6.2.3.2.2 in TS 23.548 + SMF-->>EASDF: + SMF-->>DNS server: + +``` + +Sequence diagram illustrating the discovery procedure for selecting the same EAS/DNAI for collection of UEs. The diagram shows interactions between UE, EASDF, DNS server, SMF, PCF, UDR, NEF, and AF. The steps are: 1. Provisioning of EDI (AF to UDR); 2. AF request to influence routing (AF to SMF); 3. Steps 1-2 in 6.2.3.3 in TS 23.548 (dashed box, SMF to EASDF/DNS server); 4. Steps 1-9 in 6.2.3.2.2 in TS 23.548 (SMF to EASDF/DNS server); 5. Determine if UE should be part of dynamic group (SMF to PCF); 6. update EAS/DNAI data (dashed box, PCF to UDR/NEF); 7. Steps 10-19 in 6.2.3.2.2 in TS 23.548 (SMF to EASDF/DNS server). + +**Figure 6.34.2-1: Discovery procedure for selecting the same EAS/DNAI for collection of UEs** + +1. AF provides EDI and SMF may get the EDI according to TS 23.548 [3]. AF includes a Dynamic External Group ID per DNAI or per External Application ID, if on External application ID, then it is relevant for all DNAIs. There may be a list of Dynamic External Group IDs on both levels. See example in clause 6.16.2.1. +2. The AF request in step 1 of figure 4.3.6.2-1 in TS 23.502 [9] is used to request selecting the same EAS and/or same DNAI for a collection of UEs accessing the application as identified by external application ID in the AF Request. The AF provides a DNAI correlation indication and/or EAS correlation indication. The correlation indications are used as a means to request a common DNAI and/or a common EAS for the UEs. Spatial Validity Condition could be provided for limiting the location of the UEs, and also "any UE" or an UE list or group ID will be provided for defining UE collection accessing the same EAS or the same DNAI. + +NEF maps external application ID to application ID. + +AF will also indicate if re-discovery is needed to NEF, this can only be used if a list of UEs is provided. This is to ensure that a common EAS will be used by the concerned UEs. + +In step 5 of figure 4.3.6.2-1 of TS 23.502 [9], PCF determines the UEs influenced by the AF Request, and based on AF request, PCF creates PCC rule with application ID and the Dynamic External Group ID and DNAI correlation indication and/or EAS correlation indication. + +If not already subscribed to receive updates events of the EDI for the concerned DNN and S-NSSAI, SMF does that as per TS 23.548 [3] to retrieve the EDI. + +3. If re-discovery is requested, SMF does a PDU Session modification to trigger EAS re-discovery as per clause 6.2.3.3 in TS 23.548 [3]. +4. The same as steps 1-9 in figure 6.2.3.2.2-1 in TS 23.548 [3]. + +5. If the notified FQDN from EASDF to SMF is related to the Application ID that is associated with a Dynamic External Group ID, and that DNAI and/or EAS correlation information was received in step 2, the SMF determines that the UE should be part of a dynamic group with same DNAI and/or same EAS (depending on what the AF originally requested). Using the data received in step 2, SMF determines if any of the DNAI has been selected for the group by checking the EDI. If so, the SMF uses this DNAI in step 7. and if EAS correlation indication was received from PCF, and if there is an EAS address associated with the Dynamic External Group ID SMF uses this in step 7. +6. The following cases can occur: + - If no DNAI could be used in step 5, SMF selects a DNAI and if a common DNAI should be selected indicated via the DNAI correlation indicator in step 2, SMF updates the EDI with the selected DNAI, either with an indicator or the actual DNAI depending on which level the dynamic external group id was provided on (SMFs subscribing to update events to the EDI change will be notified). + - If EAS correlation indication was set in step 2 and SMF did not have any EAS address available in step 5, SMF provides the EAS address that was received from EASDF. If multiple EAS addresses were received, SMF selects one. SMF updates EDI with the EAS address. SMF uses this in step 7. +7. Based on steps 10-19 in figure 6.2.3.2.2-1 in TS 23.548 [3], i.e. updates of the DNS handling rules with the EAS address, and breaking out the session at selected DNAI. + +### 6.34.3 Impacts on services, entities and interfaces + +AF: + +- to be updated with Dynamic External Group ID, EAS correlation indicator, and DNAI correlation indicator. + +NEF: + +- Nnef\_TrafficInfluence service (or new) as per AF new information; +- new data in EDI. + +SMF: + +- using PCC rule to associate UEs to a dynamic group of UEs, based on the original AF provided information given by PCF. Using and updating data in EDI. + +UDR: + +- new data in EDI. + +EASDF: + +- may need to be updated for create and send DNS response to UE. + +PCF: + +- services related to AF influence on routing to be updated with Dynamic External Group ID, EAS correlation ID, DNAI correlation ID. + +## 6.35 Solution 35 (KI#4): Providing dedicated (re)location information as traffic routing information + +### 6.35.1 Description + +To provide the dedicated (re)location information for a collection of UEs, the collection of UEs can be a pre-defined group of UEs or a dynamic group of UEs, the dedicated (re)location information can be the target DNAI or the target EAS which is shared by the collection of UEs. The collection of UEs can be decided by the network administrator or by the application. The collection of UEs can be a pre-configured group which is be configured by the operator, which is already supported and out of scope of KI#4. The collection of UEs can also be decided by the application. + +The target DNAI or target EAS can be decided by the AF based on the edge relocation triggered by AF or can be received by the AF via the User Plane Management events notification to the AF from the CN, or can be received by the AF via application layer. AF Providing the dedicated (re)location information for the identified collection of UEs, the existing Application Function influence on traffic routing mechanism is reused with additionally including the following: + +- The target DNAI/EAS is provisioned for a collection of UEs, not only targeting an individual UE. +- The collection of UEs can be identified by dynamic group ID managed with 5G VN group management mechanism as defined in clause 6.14, or the UEs shares the same service information. + +## 6.35.2 Procedures + +The following figure shows the solution providing the dedicated (re)location information for a collection of UE within the same dynamic group or associated with the same service information. + +![Sequence diagram illustrating Server Discovery with dedicated (re)location information. The diagram shows interactions between UE1, UE2, L-UPF, C-UPF, SMF, EASDF, PCF(s)/NEF, UDM/UDR, EAS/L-DNS, and AF/AS. The process involves session establishment, service discovery, traffic routing influence, and subsequent deactivation.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +The sequence diagram illustrates the interaction for server discovery with dedicated (re)location information. The lifelines are: UE2 (with Lower layers), UE1 (with Lower layers), L-UPF, C-UPF, SMF, EASDF, PCF(s)/NEF, UDM/UDR, EAS/L-DNS, and AF/AS. + +- UE1 establishes a session with C-UPF to access the DN, and UE1 communicates with the AS for the application. +- UE1 enters the EDN Service Area and initiates one game and target EAS is discovered for the game. +- AF requests to influence traffic routing (AppID, targeting UE(s) with specific service information/Group ID, Traffic correlation information, target DNAI/EAS). +- Service specific parameter provisioning (AppID, UE ID(GPSI/SUPI), Specific service information). +- SMF establishes BP and L-UPF for local access. +- Updates C-UPF. +- User-plane communication takes place between the Application Client in UE1 and Edge Application Server the local UPF after the application relocation to the EAS, the new UE IP address is used. +- UE2 Session Establishment with C-UPF to access the DN, and EASDF is configured with DNS handling rules. +- UE2 sends a DNS Query. +- Service specific parameter provisioning (AppID, UE ID(GPSI/SUPI), Specific service information). +- Condition triggered, the related policy with traffic correlation and the target DNAI/EAS is generated. This occurs if: + - Specific service information matched + - UE2 belongs to the same group with UE1 who has target DNAI/EAS information. +- SMF manages the PDU Session considering the target DNAI/EAS. +- ULCL/BP insertion. +- Neasdf\_DNSContext\_Notify Request/Response. +- Neasdf\_DNSContext\_Update Request/Response (rule with target DNAI/EAS). +- DNS query/Response. +- DNS response. +- User-plane communication takes place between the Application Client in UE2 and Edge Application Server via the local UPF after the application relocation to the EAS. +- The game is over and the application are terminated. +- AF requests to influence traffic routing deleting (for the targeting UE(s) with specific service information). +- Service specific parameter deleting (AppID, UE1/UE2 ID, Specific service information). +- Specific service information matched, the related traffic routing policy with target DNAI/EAS is removed for the related PDU session with UE1/UE2, the SM management and DNS context is updated accordingly. A note indicates: "When the condition changes, it should be supported that the Association of the collections of UEs can be Updated or disassociated for EAS (re)location". + +Sequence diagram illustrating Server Discovery with dedicated (re)location information. The diagram shows interactions between UE1, UE2, L-UPF, C-UPF, SMF, EASDF, PCF(s)/NEF, UDM/UDR, EAS/L-DNS, and AF/AS. The process involves session establishment, service discovery, traffic routing influence, and subsequent deactivation. + +Figure 6.35.2-1: Server Discovery with dedicated (re)location information + +- The UE1 establishes the PDU Session with C-UPF. +- UE1 enters the EDN Service Area and initiates one application e.g. starts one game and target EAS is discovered for the game. +- The dedicated relocation information is included in step 3, which targets the collection of UEs. The traffic correlation can be explicitly indicated by the traffic correlation indication, or implicitly indicated by the dedicated relocation information for the collection of UEs. AF request with traffic routing information is used to provide the dedicated relocation information, and is sent to the Core network for the specific application with the application ID, targeting a collection of UE(s). The collection of UEs can be identified by the group ID (the group can be dynamically managed with the existing mechanism), or by the target UEs with service information (e.g. the application instance identifier identifying the application instance a collection of UEs are accessing, which means all the UEs accessing the identified application instance). If it targets a group of UEs with the + +service specific information, it means the UE with the service specific information in the group can apply the receive traffic routing information received. The dedicated relocation information should be stored as associated data for the collection of UEs. + +- 3a. Step 3a is used for sending the information of a specific UE to associate the UE with the collection of UEs, if the group ID is used to identify the collection of UEs and the UEs belong to the group are preconfigured in 5GC, step 3a is skipped. Otherwise, if the collection of UEs is identified with the service information provided in step 3, the procedure of Service specific parameter provisioning defined in clause 4.15.6.7 of TS 23.502 [9] can be used to send the service specific information of the UE, for example indicating the UE is accessing the application with service specific information (e.g. joining the game). + +If the collection of UEs is identified by the group ID within 5GC, the group ID can be sent to the SMF while retrieving the SM subscription data, and the SMF retrieves the PCC rule with the group ID from the PCF for each UE, and the UE accesses the application will be matched whether it belongs to the group, if so, the traffic of the UE for the application should be correlated with the group of UEs accessing the application in the PCF. + +NOTE: The service information in this solution is notified to the SM-PCF to influence the PCC Rules instead of AM-PCF delivered to the UE as defined in clause 4.15.6.7 of TS 23.502 [9]. + +4. Based on the information received in step 3 and/or step 3a, the related policy with traffic correlation and the dedicated relocation information is sent to the SMF. The traffic correlation information is optional, if it is included, all the PDU Sessions with the same traffic correlation information can be correlated together to relocate the related traffic to the target DNAI/EAS. The SMF manages the PDU Session considering the target DNAI/EAS, which includes the routing decisions for traffic of PDU Session and the DNS handling rule decision. +- 5-7. The SMF controls the traffic routing based on the received traffic routing with dedicated relocation information accordingly. BP and L-UPF are inserted based on the edge relocation information e.g. the target DNAI/EAS received in step 4 if available. User-plane communication takes place between the Application Client in UE1 and Edge Application Server the local UPF after the application relocation to the EAS, the new UE IP address is used if multi-homing is used. +8. UE2 Session Establishment with C-UPF to access the DN, and EASDF is configured with DNS handling rules. +9. UE2 sends DNS query for the application. +- 10a-10b. Condition triggered, the related policy with traffic correlation and the target DNAI/EAS is generated. The condition triggered includes one of the following: + - Specific service information matched, in this case, the specific service information of UE2 accessing the application is sent to the PCF in step 10a which is similar to step 3a. + - UE2 belongs to the same group as UE1, the target DNAI/EAS information is associated with the group as described in step 3-4. +- 11-12. The related policy with traffic correlation and the target DNAI/EAS is sent to the SMF. The traffic correlation information is optional, if it is included, all the PDU Sessions with the same traffic correlation information will be correlated together to relocate the related traffic to the target DNAI/EAS. The SMF manages the PDU Session considering the target DNAI/EAS, which includes the routing decisions for traffic of PDU Session and the DNS handling rule decision. +13. UL-CL/BP insertion based on the target DNAI/EAS received in step 11. +14. Receiving the DNS query message for UE2 for the application as described in step 9, 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. +15. The SMF decides the DNS handling rule based on the target DNAI/EAS received in step 11: + - If the dedicated relocation information is target DNAI, the SMF selects the EDNS Client Subnet option or the local DNS server based on the target DNAI, and sends the DNS handling rule accordingly. + - If the dedicated relocation information is target EAS, the SMF indicates the EASDF to response the DNS query with the target EAS, by adding one more action of responding with indicated EAS in the DNS handling rule. + +16. Optionally, the EASDF handles the DNS Query message. +17. The EASDF sends the DNS response to the UE with the EAS within the target DNAI or with the target EAS directly. +18. User-plane communication takes place between the Application Client in UE2 and Edge Application Server via the local UPF after the application relocation to the EAS. +- 19-22. When the condition changes, it should be supported that the Association of the collections of UEs can be updated or disassociated for EAS (re)location, for example the collection of UEs can be updated, the dedicated relocation information can be updated, the association of the collection of UEs can be disassociated. + +Step 19-22 gives the example that the association of the collection of UEs can be disassociated when the game is over. The game is over. The delete procedure is similar to the create procedure described in step 4, the only difference is that it is to delete the related information and the PCF makes the decision to modify the SM policy for the application within the PDU Session accordingly. + +If the association of the collections of UEs are updated, the AF update is executed and the PCF updates the related SM policy accordingly. + +### 6.35.3 Impacts on services, entities and interfaces + +The following impacts are involved to support providing the traffic routing policy for a set of UE with associated with the same service information: + +#### AF/NEF/UDR: + +- dedicated (re)location information is provided as traffic routing information; +- service information is optionally supported to associate a specific UE with a collection of UEs; +- traffic correlation information to differentiate different collections of UEs may be supported. + +#### PCF: + +- the dedicated (re)location information for a set of UEs is received; +- service information is optionally supported to associate a specific UE with a set of UEs; +- associates the UE accessing the application with the set of UEs, and sends the PCC rule to the SMF for the PDU Session of the UE with the traffic routing policy information with the dedicated (re)location information; +- traffic correlation information to differentiate different set of UEs may be supported. + +#### SMF: + +- manages the PDU Session considering the received dedicated (re)location information, which includes the routing decisions for traffic of PDU Session and the DNS handling rule decision; +- all the PDU Sessions with the same traffic correlation information will be correlated together to use the same traffic correlation information. + +#### EASDF: + +- sends the DNS response to the UE with the EAS indicated by the SMF. + +## 6.36 Solution 36 (KI#4): Providing dedicated (re)location information as EAS Deployment information + +### 6.36.1 Description + +To provide the dedicated (re)location information for a collection of UEs for server discovery, the collection of UEs can be a pre-defined group of UEs or a dynamic group of UEs, the dedicated (re)location information can be the target + +DNAI or the target EAS which is shared by the collection of UEs. The collection of UEs can be decided by the network administrator or by the application. The collection of UEs can be a pre-configured group which is configured by the operator, which is already supported and out of scope of KI#4. The collection of UEs can also be decided by the application. + +The target DNAI or target EAS can be decided by the AF based on the edge relocation triggered by AF or can be received by the AF via the User Plane Management events notification to the AF from the CN, or can be received by the AF via application layer. AF Providing the dedicated (re)location information for the identified collection of UEs, the EAS Deployment Information Management mechanism is reused with additionally including the following: + +- The target DNAI/EAS is provisioned for a collection of UEs. +- The collection of UEs can be identified by pre-configured group ID, dynamic group ID managed with 5G VN group management mechanism as defined in clause 6.14, or the UEs shares the same service information. + +## 6.36.2 Procedures + +The following figure shows the solution providing the dedicated (re)location information for a collection of UE within the same dynamic group or associated with the same service information. + +![Sequence diagram for Server Discovery with dedicated (re)location information as EAS Deployment Information. The diagram shows interactions between UE1, UE2, L-UPF, C-UPF, SMF, EASDF, PCF(s)/NEF, UDM/UDR, EAS/L-DNS, and AF/AS. The process involves session establishment, service discovery, and DNS handling for application relocation.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +``` + +sequenceDiagram + participant UE2 + participant UE1 + participant L-UPF + participant C-UPF + participant SMF + participant EASDF + participant PCF(s)/NEF + participant UDM/UDR + participant EAS/L-DNS + participant AF/AS + + Note over UE2: Lower layers + Note over UE1: Lower layers + + Note over UE1, AF/AS: 1. Session Establishment with C-UPF to access, and UE1 communicates with the AS for the application + + Note right of UE1: 2. UE1 enters the EDN Service Area +and initiates one game +and target EAS is discovered +for the game. + + AF/AS->>PCF(s)/NEF: 3. AF requests to Provide EAS Deployment information ( AppID, targeting UE(s) with specific +service information/Group ID, target DNAI/EAS) + + PCF(s)/NEF->>SMF: 4. Service specific parameter provisioning( AppID, UE ID(GPSI/SUPI), Specific service information ) + + SMF->>L-UPF: 5. SMF establishes ULCL/BP and L-UPF for local access + + SMF->>C-UPF: 6. Updates C-UPF + + Note over UE1, EAS/L-DNS: 7. User-plane communication takes place between the Application Client in UE1 and Edge Application Server the local UPF after the application +relocation to the EAS, the new UE IP address is used. + + Note over UE2, EASDF: 8. UE2 Session Establishment with C-UPF to access the DN, and EASDF is configured with DNS handling rules + + PCF(s)/NEF->>SMF: 10a. Service specific parameter provisioning( AppID, UE ID(GPSI/SUPI), Specific service +information ) + + UE2->>EASDF: 9. DNS Query + + Note right of SMF: 10. Condition triggered, +The SMF manages the the +PDU Session considering +the correlated target +DNAI/EAS + + Note right of EASDF: 1. Specific service information matched +2. UE2 belongs to the same group with UE1 +who has target DNAI/EAS information. + + SMF->>L-UPF: 11. ULCL/BP insertion + + SMF->>EASDF: 12. Neasdf_DNSContext_Notify Request/Response + + SMF->>EASDF: 13. Neasdf_DNSContext_Update Request/Response (rule with target DNAI/EAS) + + EASDF->>EAS/L-DNS: 14. DNS query/Response + + EASDF->>UE2: 15. DNS response + + Note over UE2, EAS/L-DNS: 16. User-plane communication takes place between the Application Client in UE2 and Edge Application Server via the local UPF after the application relocation to the EAS. + +``` + +Sequence diagram for Server Discovery with dedicated (re)location information as EAS Deployment Information. The diagram shows interactions between UE1, UE2, L-UPF, C-UPF, SMF, EASDF, PCF(s)/NEF, UDM/UDR, EAS/L-DNS, and AF/AS. The process involves session establishment, service discovery, and DNS handling for application relocation. + +**Figure 6.36.1: Server Discovery with dedicated (re)location information as EAS Deployment Information** + +1. The UE1 establishes the PDU Session with C-UPF. +2. UE1 enters the EDN Service Area and initiates one application e.g. starts one game and target EAS is discovered for the game. +3. The dedicated relocation information is sent to the SMF to improve the PSA/application relocation. All the UEs within the game are required to access the application according to the dedicated relocation information, which is the same DNAI/EAS. The SMF manages the PDU Sessions considering the target DNAI, which includes the routing decisions for traffic of PDU Session and the DNS handling rule decision. + +AF request to Provide EAS Deployment information with dedicated relocation information is sent to the Core network for the specific application(s) with the application ID(s), targeting a collection of UE(s) using the EAS Deployment Information Management procedure defined in clause 6.2.3.4 of TS 23.548 [3]. The collection of UEs can be identified by the group ID (the group can be dynamically managed similar with the 5GVN group management mechanism), or by the target UEs with service information (e.g. the application instance identifier identifying the application instance a collection of UEs are accessing, which means all the UEs accessing the identified application instance). If it targets a group of UEs with the service specific information, it means the UE with the service specific information in the group can apply the dedicated relocation information received. + +4. If the group ID is used to identify the collection of UEs and the UEs belong to the group are preconfigured in 5GC, step 3a for sending the information of a specific UE to associate the UE with the collection of UEs is skipped. If the collection of UEs is identified with the service information provided in step 3, the procedure of Service specific parameter provisioning defined in clause 4.15.6.7 of TS 23.502 [9] can be used to send the service specific information of the UE, for example indicating the UE is accessing the application with service specific information (e.g. joining the game). + +NOTE: The service information in this solution is notified to the SM-PCF to influence the PCC Rules instead of AM-PCF delivered to the UE as defined in clause 4.15.6.7 of TS 23.502 [9]. + +If the collection of UEs is identified by the group ID within 5GC, the group ID can be sent to the SMF while retrieving the SM subscription data, and the SMF retrieves the PCC rule with the group ID from the PCF for each UE, and the UE accesses the application will be matched whether it belongs to the group, if so, the traffic of the UE for the application should be correlated with the group of UEs accessing the application. + +- 5-7. The SMF controls the traffic routing based on the received information of dedicated relocation information (the target DNAI) accordingly. BP and L-UPF are inserted based on the dedicated relocation information e.g. the target DNAI. User-plane communication takes place between the Application Client in UE1 and Edge Application Server the local UPF after the application relocation to the EAS, the new UE IP address is used if multi-homing is used. +8. UE2 Session Establishment with C-UPF to access the DN, and EASDF is configured with DNS handling rules. +9. UE2 sends DNS query for the application. +- 10a-10. Condition triggered, the related information of the target DNAI/EAS are received by the SMF. The condition triggered includes one of the following: + - specific service information matched; in this case, the specific service information of UE2 accessing the application is sent to the SMF in step 10a which is similar as step 4; + - UE2 belongs to the same group with UE1, the target DNAI/EAS information is associated with the group as described in step 3-4. +11. BP insertion based on the target DNAI for the PDU Session received in step 10a-10 if needed. +12. Receiving the DNS query message for UE2 for the application as described in step 9, 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. +13. The SMF decides the DNS handling rule based on the target DNAI/EAS as described in step 10a-10, including: + - if the dedicated relocation information is target DNAI, the SMF selects the EDNS Client Subnet option or the local DNS server based on the target DNAI, and sends the DNS handling rule accordingly to the EASDF; + - if the dedicated relocation information is target EAS, the SMF indicates the EASDF to response the DNS query with the target EAS, by adding one more action of responding with indicated EAS in the DNS handling rule. +14. The EASDF handles the DNS Query message. Optionally, the EASDF forwards the DNS query message. +15. The EASDF sends the DNS response to the UE with the EAS within the target DNAI or with the target EAS directly. + +### 6.36.3 Impacts on services, entities and interfaces + +The following impacts are involved to support providing the traffic routing policy for a set of UE with associated with the same service information: + +AF/NEF/UDR: + +- dedicated (re)location information is provided as EAS Deployment information; +- service information is optionally supported to associate a specific UE with a collection of UEs. + +SMF: + +- the EAS Deployment information with dedicated (re)location information for a set of UEs is received; +- service information is optionally supported to associate a specific UE with a set of UEs; +- associates the UE accessing the application with the set of UEs using service information if received; +- makes the DNS handling rule decision for the PDU Session associated with the set of UEs considering the received dedicated (re)location information. + +EASDF: + +- sends the DNS response to the UE with the EAS indicated by the SMF. + +## 6.37 Solution 37 (KI#4): (Re)location of same EAS and coordination across UEs + +### 6.37.1 Introduction + +This solution aims to address the technical requirements related to key issue #4. In particular, it provides solutions to, among others, how the 5GS facilitates EAS (re)location of EAS for the collection of UEs. The procedure defined in figure 6.2.3.2.2-1 in TS 23.548 [3] is reused. Also, procedure for ad hoc group provisioning and group information management/storing in the UDM/UDR are assumed, for example solution 19 in clause 6.19. + +There could be one SMF serving the collection of UEs that connects the same EAS/DNAI for accessing the same application, or there could be multiple SMFs for different UEs in the collection. For the latter case, UDM is used for coordination between SMFs to make sure selecting the same EAS/DNAI for UEs in the ad hoc group, i.e. SMF updates the selected EAS IP/DNAI to UDM or SMFs gets the EAS IP/DNAI information from UDM. + +### 6.37.2 Functional Description + +The following are the main principles of the solution: + +- Procedure for ad hoc group provisioning and group information management/storing in the UDM/UDR are re-used for example based on solution 19 in clause 6.19. +- EAS ID is determined based on the procedure in clause 6.2.3.2.2-1 in TS 23.548 [3]. +- SMF updates the ad hoc group information in the UDM/UDR with the EAS ID. +- SMFs subscribes to the UDM to get notification on any changes to the ad hoc group data. +- For the subsequent ad hoc group member UEs DNS request, SMF(s) instructs the EASDF to provide the already determined EAS IP address in the DNS response for DNS queries. + +### 6.37.3 Solution Details + +#### 6.37.3.1 EAS (re)location to the ad hoc group member UEs + +The figure 6.37.3.1-1 below provides a detailed call flow on the (re)location of the same EAS to the all the UEs of the ad hoc group. + +Although the figure below does not explicitly indicate the same DNAI, but the same is applicable in case of common/same DNAI requirement. For example, initial/first SMF selects a DNAI and updates to the group information in the UDM/UDR. UDM/UDR then notifies to other SMFs (if subscribed). This DNAI may change e.g. using existing procedures due to UE mobility and/or AF influence and so on. If so, respective SMF updates to the group information in the UDM/UDR newly selected DNAI using Nudm\_ParameterProvision. This ensures that the same DNAI is applied to all the group members, and also allows DNAI change. + +![Sequence diagram for EAS (re)location to the ad hoc group member UEs. Lifelines: UE, EASDF, DNS Server, SMF, PCF, UDM, NEF, AF. The diagram shows 7 steps involving group provisioning, discovery procedures, and notifications.](9958beca8f65818eb0ff893647af94de_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EASDF + participant DNS Server + participant SMF + participant PCF + participant UDM + participant NEF + participant AF + + Note over UDM, AF: 1. Ad hoc group provisioning and group information management/storing in the UDM/UDR + Note over UE, SMF: 2. Step 1-15 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF, TS23.548 + Note over SMF: 3. SMF determines UE belongs to group of UEs To use the same EAS for the application + SMF->>UDM: 4. Nudm_ParameterProvision (Group ID, EAS ID, FQDN) + Note over UE, SMF: 5. Step 16-19 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF, TS23.548 + UDM-->>SMFx: 6. Nudm_SDM_Notification (Group ID, EAS ID, FQDN) + Note over EASDFx, SMFx: 7. steps 1~9 and steps 16~19 in figure 6.2.3.2.2-1 in TS 23.548 + +``` + +Sequence diagram for EAS (re)location to the ad hoc group member UEs. Lifelines: UE, EASDF, DNS Server, SMF, PCF, UDM, NEF, AF. The diagram shows 7 steps involving group provisioning, discovery procedures, and notifications. + +**Figure 6.37.3.1-1: EAS (re)location to the ad hoc group member UEs** + +1. Ad hoc group provisioning and group information management/storing in the UDM/UDR, for example: + - as in solution 19 in clause 6.19 or based on details in clause 6.37.3.3. Nnef\_ParameterProvision\_Create request is used to provision group attributes like group ID, member UEs, FQDN, etc. SMF subscribed to the Group subscription data via Nudm\_SDM\_Notification Notify message. +2. The same as steps 1~15 in figure 6.2.3.2.2-1 in TS 23.548 [3]. +3. This step may possibly/also occur before step 2, where SMF learns via Nudm\_SDM\_Notification Notify that UE belongs to the ad hoc group provisioned by the AF for certain application that requires same application server/EAS. +4. SMF uses Nudm\_ParameterProvision to update ad hoc group subscription data in the UDM/UDR to include EAS ID. +5. Based on steps 16~19 in figure 6.2.3.2.2-1 in TS 23.548 [3]: + + +In step 17, SMF sends DNS message handling rule with IP address for the EAS instructing EASDF to return the IP address for the EAS to UE in step 19. +6. All the SMFs subscribed to the notification of the Group subscription data are notified of the changes using Nudm\_SDM\_Notification Notify, and thus learn EAS ID applicable to the ad hoc group member UEs. +7. For the Group of UEs, if another UE of Group of UEs sends DNS request, based on steps 1~9 in figure 6.2.3.2.2-1 in TS 23.548 [3]: + + +Steps 10 to 15 are skipped and in step 16 the UL-CL UPF is selected by SMFx for EAS ID notified by UDM and at step 17, SMFx sends DNS message handling rule with IP address for the EAS instructing its EASDFx to return the IP address for the EAS to UE in step 19. + +### 6.37.3.2 Updating EAS ID in the Group Info + +In cases such as where multiple UEs of the same group send DNS queries almost simultaneously, and subsequently resolved to different EAS ID, it is possible that respective SMF may try to update the EAS ID of the ad hoc group. For this kind of race condition, the procedures below are proposed: + +- SMF creates/modifies the correlation of an EAS ID with a Group ID and FQDN in the UDM/UDR as explained in clause 6.37.3.1. The binding information may include an FQDN for which the binding exists and/or SMF ID and/or SMF set ID; +- SMF subscribes to the UDM/UDR for notification of change of creation/deletion/modification of the correlation of EAS ID with Group ID; + +- Based on the binding information that includes an FQDNs for which the binding exists and/or SMF ID and/or SMF set ID, UDM/UDR evaluates new creation/deletion/modification of the correlation of EAS ID with Group ID in order to avoid overwriting the initially stored EAS ID and accordingly UDM/UDR rejects creation/deletion/modification of the correlation of EAS ID with Group ID by sending the stored EAS ID to the subsequent SMF, i.e. SMF2; +- SMF2 accepts the response to the creation/update of the correlation of EAS ID with Group ID from UDM/UDR with an EAS ID (i.e. if already stored in the group data) different from the EAS ID provided by the SMF2 to the database; +- SMF evaluates the EAS ID received in the response from the UDM/UDR and re-selects and re-configures DNAI / UL-CL UPF and PSA UPF (before instructing the EASDF to reply with DNS response towards the UE). + +### 6.37.3.3 Collection of UEs based on 5GC criteria + +This clause relates to 5GC initiated ad hoc group creation/update/deletion, i.e. SMF may form a dynamic ad hoc group of a collection of UEs that could be subject to collective and common treatment. This collection of UEs may be based on specific criteria, for example all the UEs in this group use the same EAS and/or same DNAI and/or same PSA UPF and/or UEs in a specific geographical area. + +In case of ad hoc group consisting of UEs using the same EAS, SMF may interact with EASDF to form this group. Thus, SMF determines the collection of UEs based on the DNS response messages provided by EASDF to SMF. + +As per existing specification, SMF instructs EASDF to report DNS responses matching one or more specific FQDNs and/or EAS IP addresses. EASDF notifies SMF per UE's PDU Session when such DNS response is received. Once SMF receives the notification from EASDF for each PDU Session, then SMF can group them based on the grouping criteria. Alternatively, the SMF may instruct the EASDF to report DNS responses matching one or more specific FQDNs and/or EAS IP addresses for any PDU Session of ANY UE possibly matching certain criteria (e.g. a specific S-NSSAI and DNN). Once SMF receives notification from the EASDF, SMF assigns an ad hoc group ID for the same and may store group information in the UDM/UDR, together with Group ID and list of UEs, etc. SMF may also report this group ID/info to AF based on AF notification criteria, thus allowing AF to make an offloading decision subsequently. + +### 6.37.4 Impacts on services, entities and interfaces + +SMF: + +- subscribes to the ad hoc group subscription data; +- updates UDM/UDR with EAS ID/DNAI information in the ad hoc group subscription data; +- interactions between SMF and EASDF related to clause 6.37.3.3. + +## 6.38 Solution 38 (KI#5): EAS Discovery for EHE shared with other PLMN + +### 6.38.1 Description + +In Key Issue#5, the following aspects shall be studied: + +- investigate potential impacts related to the GSMA Operator Platform Group work on EAS discovery. + +Edge Node Sharing scenario is one use case defined in clause 3.3.5 of GSMA OPG.02 [5], in which case EAS A (hosted by Operator A) is to be accessed by Operator B's network. This solution aims to solve the EAS discovery for the Edge Node Sharing scenario. From Operator B's point of view, the EAS deployed in Operator A's network is equivalent to the case that 3rd party provider hosting the EHE. Application provider (AF) creates EDI (EAS Deployment Information) corresponding to Operator A's network, and Operator A forward EDI to Operator B instead of the application provider. + +There are two candidate options to provision EDI to serving Operator: + +- 1) based on interaction between NEFs from different PLMNs; + +- 2) based on EWBI interface defined by GSMA OPG.02 [5]. + +Option1 - NEF-based EDI provision to serving Operator: + +Operator A needs to translate the EDI provided by AF to an EDI corresponding to Operator B's network, and also N6 traffic routing requirements could be included in EDI for instructing how to route traffic from Operator B's network to the Operator A's EHE. It is assumed that AF only has agreement with Operator A. NEF is in charge of translation between EDIs, it translates DNAI corresponding to Operator A's network to DNAI corresponding to Operator B's network. + +NOTE 1: The translation of DNAI could be based on configured relationship between DNAIs from different operators, or NEF could retrieve Operator B's DNAI dynamically, e.g. based on solutions from KI#7 described in clause 5.7. The N6 traffic routing requirements could be determined based on SLA between Operators (similar to the way how AF configures N6 traffic routing requirements currently). + +Option2 - EWBI-based EDI provision to serving Operator: + +EWBI defined by GSMA OPG.02 [5] is used for exchange EDI information between PLMNs, and it assumes EWBI support the capability for exchanging application instance access information between PLMNs. The OPG platform could interact with NEF of serving PLMN via SBI-NR interface for provision of EDI. + +NOTE 2: Per SLA agreement between operator one dedicated IP connection can be established between Operators, which will be in charge of satisfy the end-to-end QoS requirement when the traffic routing from Operator B's UPF to Operator A's DN, and UPF could mark the packets with appropriate pre-configured DSCP value for traffic routing Qos fulfilment between PLMNs. + +## 6.38.2 Procedures + +### 6.38.2.1 Option1 - NEF-based EDI provision to serving Operator + +The EAS discovery procedure for Edge Node Sharing scenario is defined below. + +![Sequence diagram of the EAS discovery procedure for Edge Node Sharing scenario. The diagram shows interactions between various network functions (UE, UPF, DNS Server, EASDF, SMF, UDR, NEF#B, NEF#A, AF) across two operators, Operator B and Operator A. The sequence starts with AF in Operator A sending a Nnef_EASDeployment_Create Request to NEF#A. NEF#A handles this and sends a response to AF. NEF#A then sends a Nnef_EASDeployment_Create Request to NEF#B in Operator B. NEF#B sends a Nudr_DM_Create Request to UDR. UDR responds with Nudr_DM_Create Response. NEF#B then sends a Nnef_EASDeployment_Create Response to NEF#A. NEF#A sends a response to AF. SMF in Operator B receives EDI from NEF#B. Finally, EAS Discovery is performed according to step 3~19 in Figure 6.2.3.2.2-1 TS23.548[3].](c973a830a03be42682a331ad3215d6c6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UPF + participant DNS Server + participant EASDF + participant SMF + participant UDR + participant NEF#B as NEF#B (Operator B) + participant NEF#A as NEF#A (Operator A) + participant AF + + Note right of NEF#A: Operator A + Note left of NEF#B: Operator B + + AF->>NEF#A: 1.Nnef_EASDeployment_Create Request + NEF#A->>AF: 2.NEF handling + NEF#A->>AF: 3.Nnef_EASDeployment_Create Response + NEF#A->>NEF#B: 4.Nnef_EASDeployment_Create Request + NEF#B->>UDR: 5.Nudr_DM_Create Request + UDR->>NEF#B: 6.Nudr_DM_Create Response + NEF#B->>NEF#A: 7.Nnef_EASDeployment_Create Response + Note right of SMF: 8.SMf receives EDI as defined in clause 6.2.3.4.3 TS23.548[3] + Note left of SMF: 9.EAS Discovery according to step 3~19 in Figure 6.2.3.2.2-1 TS23.548[3] + +``` + +Sequence diagram of the EAS discovery procedure for Edge Node Sharing scenario. The diagram shows interactions between various network functions (UE, UPF, DNS Server, EASDF, SMF, UDR, NEF#B, NEF#A, AF) across two operators, Operator B and Operator A. The sequence starts with AF in Operator A sending a Nnef\_EASDeployment\_Create Request to NEF#A. NEF#A handles this and sends a response to AF. NEF#A then sends a Nnef\_EASDeployment\_Create Request to NEF#B in Operator B. NEF#B sends a Nudr\_DM\_Create Request to UDR. UDR responds with Nudr\_DM\_Create Response. NEF#B then sends a Nnef\_EASDeployment\_Create Response to NEF#A. NEF#A sends a response to AF. SMF in Operator B receives EDI from NEF#B. Finally, EAS Discovery is performed according to step 3~19 in Figure 6.2.3.2.2-1 TS23.548[3]. + +Figure 6.38.2.1-1: EAS discovery procedure + +1. AF invokes the Nnef\_EASDeployment\_Create operation with EDI1 corresponding to Operator A. +2. NEF of Operator A translates the received EDI1 from AF to a new EDI2 corresponding to Operator B: + - NEF translates DNAI in the received EDI1 to the DNAI of Operator B, and includes the DNAI of Operator B in the new EDI2. + - (optional) NEF adds N6 traffic routing information in the new EDI2. + +NOTE 1: The translation of DNAI could be based on configured relationship between DNAIs from different operators, or NEF could retrieve Operator B's DNAI dynamically, e.g. based on solution from KI#7, described in clause 5.7. The N6 traffic routing requirements could be determined based on SLA between operators. + +3. The NEF of Operator A sends Nnef\_EASDeployment\_Create Response to the AF. +- 4~7. The same as steps in EAS Deployment Information management in the AF procedure as defined in figure 6.2.3.4.2-1 in TS 23.548 [3]. In step 3, EDI2 corresponding to Operator B is included in the Nnef\_EASDeployment\_Create operation. In step 4, NEF#B could do authorization on the request from NEF#A. +8. The same as EAS Deployment Information management in the SMF procedure as defined in figure 6.2.3.4.3-1 in TS 23.548 [3]. +9. Step 3~19 of EAS Discovery procedure in figure 6.2.3.2.2-1 in TS 23.548 [3] is reused, with the following difference: + +In step 16, after determining the DNAI, SMF could determine the N6 traffic routing information for the DNAI based on the N6 routing Information in EDI. + +### 6.38.2.2 Option2 - EWBI/AF-based EDI provision to serving Operator + +![Sequence diagram for EAS discovery procedure based on EWBI. Lifelines: UE, UPF, DNS Server, EASDF, SMF, UDR, NEF, AF(OP of serving PLMN). The sequence starts with the AF sending a Nnef_EASDeployment_Create Request to the NEF. The NEF performs internal handling and sends a response back to the AF. Simultaneously, the NEF sends a Nudr_DM_Create Request to the UDR, which responds with Nudr_DM_Create Response. The SMF then receives the EDI from the UDR. Finally, the EAS Discovery procedure (steps 3~19) is initiated between the UE and the EASDF.](273610b2edda13f5c3de995f4e845396_img.jpg) + +``` + +sequenceDiagram + participant AF as AF(OP of serving PLMN) + participant NEF + participant UDR + participant SMF + participant EASDF + participant DNS Server + participant UPF + participant UE + + Note right of AF: 1.Nnef_EASDeployment_Create Request + AF->>NEF: 1.Nnef_EASDeployment_Create Request + Note right of NEF: 2.NEF handling + Note right of NEF: 3.Nnef_EASDeployment_Create Response + NEF-->>AF: 3.Nnef_EASDeployment_Create Response + Note right of NEF: 4.Nudr_DM_Create Request + NEF->>UDR: 4.Nudr_DM_Create Request + Note right of UDR: 5.Nudr_DM_Create Response + UDR-->>NEF: 5.Nudr_DM_Create Response + Note right of SMF: 6.SMf receives EDI as defined in clause 6.2.3.4.3 TS23.548[3] + UDR-->>SMF: 6.SMf receives EDI as defined in clause 6.2.3.4.3 TS23.548[3] + Note right of EASDF: 7.EAS Discovery according to step 3~19 in Figure 6.2.3.2.2-1 TS23.548[3] + EASDF-->>UE: 7.EAS Discovery according to step 3~19 in Figure 6.2.3.2.2-1 TS23.548[3] + +``` + +Sequence diagram for EAS discovery procedure based on EWBI. Lifelines: UE, UPF, DNS Server, EASDF, SMF, UDR, NEF, AF(OP of serving PLMN). The sequence starts with the AF sending a Nnef\_EASDeployment\_Create Request to the NEF. The NEF performs internal handling and sends a response back to the AF. Simultaneously, the NEF sends a Nudr\_DM\_Create Request to the UDR, which responds with Nudr\_DM\_Create Response. The SMF then receives the EDI from the UDR. Finally, the EAS Discovery procedure (steps 3~19) is initiated between the UE and the EASDF. + +Figure 6.38.2.2-1: EAS discovery procedure based on EWBI + +NOTE 1: The serving PLMN gets EDI of PLMN, which shares the EHE, via EWBI interface, and GSMA OP platform could act the role of AF. It assumes EWBI supports the capability for exchanging application instance access information between PLMNs. + +1. AF invokes the Nnef\_EASDeployment\_Create operation with EDI1 corresponding to PLMN hosting EHE. The EDI1 contains DNAI(s) corresponding to PLMN hosting EHE. +2. NEF translates the received EDI1 from AF to a new EDI2 corresponding to UE's serving PLMN: + - NEF translates DNAI in the received EDI1 to the DNAI of serving PLMN, and includes the DNAI of serving PLMN in the new EDI2; + - (optional) NEF adds N6 traffic routing information in the new EDI2. + +NOTE 2: The translation of DNAI could be based on configured relationship between DNAIs from different PLMNs, or NEF could retrieve serving PLMN's DNAI dynamically, e.g. based on solution from KI#7, described in clause 5.7. The N6 traffic routing requirements could be determined based on SLA between operators. + +3. The NEF of Operator A sends Nnef\_EASDeployment\_Create Response to the AF. + +- 4-5. NEF stores the received EDI into UDR. +- 6. The same as EAS Deployment Information management in the SMF procedure as defined in figure 6.2.3.4.3-1 in TS 23.548 [3]. +- 7. Steps 3-19 of EAS Discovery procedure in figure 6.2.3.2.2-1 in TS 23.548 [3] is reused, with the following difference: + - In step 16, after determining the DNAI, SMF could determine the N6 traffic routing information for the DNAI based on the N6 routing Information in EDI. + +### 6.38.3 Impacts on services, entities and interfaces + +EAS Deployment Information (EDI) is extended with N6 traffic routing Information for DNAI. + +NEF: + +- supports EDI translation. + +AF: + +- supports the new EDI. + +SMF: + +- supports N6 traffic routing Information in EDI.NEF. + +## 6.39 Solution 39 (KI#1, KI#5): Support EAS relocation of inter-PLMN + +### 6.39.1 Description + +The following solution corresponds to the key issue #1 on Accessing EHE in a VPLMN when roaming as specified in clause 5.1 "how to support the edge relocation in roaming scenarios" and key issue #5 on GSMA OPG impacts and improvements for EHE operated by separate party as specified in clause 5.5 "how the 5GS facilitates edge relocation between an EAS deployed by a source EHE provider to another EHE deployed by a target EHE provider, even in scenarios when EHEs are operated by different service providers". + +This solution makes the following assumptions: + +- the EAS relocation is triggered by AF (e.g. due to the load balance between EAS instances in the EHE); +- an OP to deploy EAS on another OP, and these OPs are different PLMNs; +- the EAS is relocated from VPLMN/HPLMN to HPLMN/VPLMN. + +The solution is to address EAS relocation of different PLMNs, and it is illustrated as the scenario of figure 6.39.2.1-1. The EHE1 is operated by OP1 in PLMN1. In the EHE1, there is a EAS1 deployed by OP1 and a EAS4 deployed by OP2. The EHE2 is operated by OP2 in PLMN2. In the EHE2, there is a EAS2 deployed by OP1 and a EAS3 deployed by OP2. + +![Figure 6.39.1-1: Scenario of EAS relocation from VPLMN to HPLMN. The diagram shows network functions and their interfaces across two PLMNs. In PLMN1 (HPLMN), H-SMF connects to H-UPF via N4. H-UPF connects to EHE1 of OP1 (containing EAS1-OP1 and EAS4-OP2) via N6. In PLMN2 (VPLMN), UL CL/BP UPF connects to H-UPF via N9. UE connects to (R)AN via N1. (R)AN connects to UL CL/BP UPF via N3 and to AMF via N2. UL CL/BP UPF connects to V-UPF via N9. AMF connects to V-SMF via N11 and to V-PCF via N15. V-SMF connects to V-PCF via N7 and to V-UPF via N4. V-PCF connects to AF via N5. V-UPF connects to EHE2 of OP2 (containing EAS2-OP1 and EAS3-OP2) via N6.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +The diagram illustrates the network architecture for EAS relocation from VPLMN to HPLMN. At the top, the H-SMF is connected to the H-UPF via the N4 interface. The H-UPF is connected to the EHE1 of OP1 (containing EAS1-OP1 and EAS4-OP2) via the N6 interface. Below a dashed line representing the boundary between PLMN1 (HPLMN) and PLMN2 (VPLMN), the H-UPF is connected to the UL CL/BP UPF via the N9 interface. The UE is connected to the (R)AN via the N1 interface. The (R)AN is connected to the UL CL/BP UPF via the N3 interface and to the AMF via the N2 interface. The UL CL/BP UPF is connected to the V-UPF via the N9 interface. The AMF is connected to the V-SMF via the N11 interface and to the V-PCF via the N15 interface. The V-SMF is connected to the V-PCF via the N7 interface and to the V-UPF via the N4 interface. The V-PCF is connected to the AF via the N5 interface. The V-UPF is connected to the EHE2 of OP2 (containing EAS2-OP1 and EAS3-OP2) via the N6 interface. + +Figure 6.39.1-1: Scenario of EAS relocation from VPLMN to HPLMN. The diagram shows network functions and their interfaces across two PLMNs. In PLMN1 (HPLMN), H-SMF connects to H-UPF via N4. H-UPF connects to EHE1 of OP1 (containing EAS1-OP1 and EAS4-OP2) via N6. In PLMN2 (VPLMN), UL CL/BP UPF connects to H-UPF via N9. UE connects to (R)AN via N1. (R)AN connects to UL CL/BP UPF via N3 and to AMF via N2. UL CL/BP UPF connects to V-UPF via N9. AMF connects to V-SMF via N11 and to V-PCF via N15. V-SMF connects to V-PCF via N7 and to V-UPF via N4. V-PCF connects to AF via N5. V-UPF connects to EHE2 of OP2 (containing EAS2-OP1 and EAS3-OP2) via N6. + +Figure 6.39.1-1: Scenario of EAS relocation from VPLMN to HPLMN + +![Figure 6.39.1-2: Scenario of EAS relocation from HPLMN to VPLMN. In PLMN1 (HPLMN), AMF connects to H-SMF via N11 and to H-PCF via N15. H-SMF connects to H-PCF via N7 and to H-UPF via N4. H-PCF connects to AF via N5. H-UPF connects to EHE1 of OP1 (containing EAS1-OP1 and EAS4-OP2) via N6. UE connects to (R)AN via N1. (R)AN connects to AMF via N2 and to UL CL/BP UPF via N3. UL CL/BP UPF connects to H-UPF via N9. In PLMN2 (VPLMN), UL CL/BP UPF connects to V-UPF via N9. V-UPF connects to EHE2 of OP2 (containing EAS2-OP1 and EAS3-OP2) via N6 and to V-SMF via N4.](d1be394c67ec994c0c8529d29ea3e9cc_img.jpg) + +The diagram illustrates the network architecture for EAS relocation from HPLMN to VPLMN. At the top in PLMN1 (HPLMN), the AMF is connected to the H-SMF via the N11 interface and to the H-PCF via the N15 interface. The H-SMF is connected to the H-PCF via the N7 interface and to the H-UPF via the N4 interface. The H-PCF is connected to the AF via the N5 interface. The H-UPF is connected to the EHE1 of OP1 (containing EAS1-OP1 and EAS4-OP2) via the N6 interface. The 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 UL CL/BP UPF via the N3 interface. The UL CL/BP UPF is connected to the H-UPF via the N9 interface. Below a dashed line in PLMN2 (VPLMN), the UL CL/BP UPF is connected to the V-UPF via the N9 interface. The V-UPF is connected to the EHE2 of OP2 (containing EAS2-OP1 and EAS3-OP2) via the N6 interface and to the V-SMF via the N4 interface. + +Figure 6.39.1-2: Scenario of EAS relocation from HPLMN to VPLMN. In PLMN1 (HPLMN), AMF connects to H-SMF via N11 and to H-PCF via N15. H-SMF connects to H-PCF via N7 and to H-UPF via N4. H-PCF connects to AF via N5. H-UPF connects to EHE1 of OP1 (containing EAS1-OP1 and EAS4-OP2) via N6. UE connects to (R)AN via N1. (R)AN connects to AMF via N2 and to UL CL/BP UPF via N3. UL CL/BP UPF connects to H-UPF via N9. In PLMN2 (VPLMN), UL CL/BP UPF connects to V-UPF via N9. V-UPF connects to EHE2 of OP2 (containing EAS2-OP1 and EAS3-OP2) via N6 and to V-SMF via N4. + +Figure 6.39.1-2: Scenario of EAS relocation from HPLMN to VPLMN + +![Figure 6.39.1-3: Scenario of EAS relocation between operators via N6. The diagram shows a UE connected to an (R)AN, which is connected to an AMF1. AMF1 is connected to an SMF1 via N11. SMF1 is connected to a PCF1 via N7. PCF1 is connected to an AF via N5. AMF1 is also connected to an UPF1 via N3. UPF1 is connected to an EAS1-OP1 (EHE1 of OP1) via N6. A dashed line separates PLMN1 (containing UE, (R)AN, AMF1, SMF1, PCF1, AF, UPF1, EAS1-OP1) and PLMN2 (containing EAS2-OP1, EHE2 of OP2). A blue line indicates the path of the EAS relocation from EAS2-OP1 in PLMN2 to EAS1-OP1 in PLMN1 via the N6 interface.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +Figure 6.39.1-3: Scenario of EAS relocation between operators via N6. The diagram shows a UE connected to an (R)AN, which is connected to an AMF1. AMF1 is connected to an SMF1 via N11. SMF1 is connected to a PCF1 via N7. PCF1 is connected to an AF via N5. AMF1 is also connected to an UPF1 via N3. UPF1 is connected to an EAS1-OP1 (EHE1 of OP1) via N6. A dashed line separates PLMN1 (containing UE, (R)AN, AMF1, SMF1, PCF1, AF, UPF1, EAS1-OP1) and PLMN2 (containing EAS2-OP1, EHE2 of OP2). A blue line indicates the path of the EAS relocation from EAS2-OP1 in PLMN2 to EAS1-OP1 in PLMN1 via the N6 interface. + +Figure 6.39.1-3: Scenario of EAS relocation between operators via N6 + +## 6.39.2 Procedures + +### 6.39.2.1 EAS relocation from VPLMN to HPLMN (KI#1) + +![Figure 6.39.2.1-1: EAS relocation from VPLMN to HPLMN. The diagram shows the interaction between HPLMN (Home PLMN) and VPLMN (Visited PLMN). HPLMN contains H-PSA UPF and H-SMF. VPLMN contains V-PSA UPF, UL CL/BP V-UPF, V-SMF, NEF/PCF, and AF. The sequence of messages is: 0. LBO PDU session is established in VPLMN; 1. AF invokes Nnef_TrafficInfluence_Create/Update or Npcf_PolicyAuthorization_Create/Update to NEF/PCF; 2. NEF/PCF invokes Npcf_SMSPolicyControl_UpdateNotify to V-SMF; 3. V-SMF selects H-SMF; 4. V-SMF selects UL CL/BP V-UPF, and sends the inter-PLMN relocation indicator and EAS replacement information/EAS information to H-SMF; 5. H-SMF selects H-PSA UPF, configure routing rule; 6. H-SMF sends Nsmf_PDUSession_Create Response to V-SMF; 7. V-SMF configures routing rule.](bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg) + +Figure 6.39.2.1-1: EAS relocation from VPLMN to HPLMN. The diagram shows the interaction between HPLMN (Home PLMN) and VPLMN (Visited PLMN). HPLMN contains H-PSA UPF and H-SMF. VPLMN contains V-PSA UPF, UL CL/BP V-UPF, V-SMF, NEF/PCF, and AF. The sequence of messages is: 0. LBO PDU session is established in VPLMN; 1. AF invokes Nnef\_TrafficInfluence\_Create/Update or Npcf\_PolicyAuthorization\_Create/Update to NEF/PCF; 2. NEF/PCF invokes Npcf\_SMSPolicyControl\_UpdateNotify to V-SMF; 3. V-SMF selects H-SMF; 4. V-SMF selects UL CL/BP V-UPF, and sends the inter-PLMN relocation indicator and EAS replacement information/EAS information to H-SMF; 5. H-SMF selects H-PSA UPF, configure routing rule; 6. H-SMF sends Nsmf\_PDUSession\_Create Response to V-SMF; 7. V-SMF configures routing rule. + +Figure 6.39.2.1-1: EAS relocation from VPLMN to HPLMN + +0. When UE is roaming to VPLMN, it establishes a LBO PDU Session to access the source EAS (EAS2), which is deployed by OP1 in VPLMN (EHE of OP2), e.g. OP1 and OP2 have a federation agreement. +1. When the EAS relocation is triggered, AF determines the source EAS should be relocated to the target EAS (e.g. EAS 1) deployed by OP1 in HPLMN (e.g. based on a federation agreement). The AF invokes Nnef\_TrafficInfluence\_Create or Nnef\_TrafficInfluence\_Update service operation to send the request message to NEF, or invokes Npcf\_PolicyAuthorization\_Create or Npcf\_PolicyAuthorization\_Update to send the request message to the PCF directly. The request message includes the PLMN ID, which indicates the EAS should be relocated to the target PLMN (identified by PLMN ID). + +If 5GC supports EAS IP replacement mechanism, 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 V-SMF as specified in clause 6.3.3 of TS 23.548 [3]. Alternatively, the AF sends the EAS information (e.g. EAS IP address) to network and to UE via application layer. + +2. The PCF creates and sends the PCC rule to the V-SMF by invoking Npcf\_SMPolicyControl\_UpdateNotify service operation. The PCC rule includes the PLMN ID. +3. V-SMF discovers the H-SMF. + +If the V-SMF has knowledge of EAS deployment information in HPLMN, the V-SMF determines the target DNAI based on the EAS deployment information and IP address of target EAS. V-SMF sends the target DNAI to the V-AMF by invoking Nsmf\_PDUSession\_SMContextStatusNotify service operation. Then, V-AMF selects H-SMF based on the target DNAI. Then, H-SMF sends Nsmf\_PDUSession\_Context Request to V-SMF. + +Alternatively, the V-SMF sends discovery request to vNRF by invoking Nnrf\_NFDiscovery\_Request (serving PLMN ID, home PLMN ID), and discovers the H-SMF as specified in clause 4.17.5 in TS 23.502 [9]. + +4. The V-SMF inserts or changes the UL-CL/BP V-UPF. The V-SMF sends an inter-PLMN relocation indicator to H-SMF by Nsmf\_PDUSession\_Update Request. The inter-PLMN relocation is to indicate the EAS is relocated from VPLMN to HPLMN. +5. The H-SMF selects the H-PSA UPF based on the EAS IP replacement information/EAS information. H-SMF configures the H-PSA UPF for traffic routing towards target EAS. If the EAS IP replacement information is received, the H-SMF configures H-PSA UPF with EAS IP replacement information. +6. The H-SMF sends the acknowledgement message to the V-SMF, which includes the tunnel information towards H-PSA UPF. +7. When V-SMF receives the acknowledgement, V-SMF configures the UL-CL/BP V-UPF for traffic routing towards H-PSA UPF if the destination address is the IP address of source EAS or target EAS. + +### 6.39.2.2 EAS relocation from HPLMN to VPLMN (KI#1) + +![Sequence diagram for EAS relocation from HPLMN to VPLMN (KI#1). The diagram shows interactions between VPLMN (V-PSA UPF, V-SMF) and HPLMN (H-PSA UPF, UL CL/BP H-UPF, H-SMF, NEF/PCF, AF).](6c03366230af7163bc0866430f8b20c2_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph VPLMN + V-PSA UPF + V-SMF + end + subgraph HPLMN + H-PSA UPF + UL CL/BP H-UPF + H-SMF + NEF/PCF + AF + end + Note right of H-PSA UPF: 0. PDU session is established in HPLMN + Note right of AF: 1. Nnef_TrafficInfluence_Create/Update or Npcf_PolicyAuthorization_Create/Update + Note right of NEF/PCF: 2. Npcf_SMPolicyControl_UpdateNotify + Note right of H-SMF: 3. H-SMF selects V-SMF + Note right of H-SMF: 4. Select UL CL/BP V-UPF, and sends the inter-PLMN relocation indicator and EAS replacement information/EAS information to H-SMF + Note right of V-SMF: 5. Select V-PSA UPF, configure routing rule + Note right of V-SMF: 6. Nsmf_PDUSession_Create Response + Note right of H-PSA UPF: 7. Configure routing rule + +``` + +Sequence diagram for EAS relocation from HPLMN to VPLMN (KI#1). The diagram shows interactions between VPLMN (V-PSA UPF, V-SMF) and HPLMN (H-PSA UPF, UL CL/BP H-UPF, H-SMF, NEF/PCF, AF). + +Figure 6.39.2.2-1: EAS relocation from HPLMN to VPLMN + +0. The UE establishes PDU Session to access the source EAS (EAS1). +1. When the EAS relocation is triggered, AF determines the source EAS should be relocated to the target EAS (e.g. EAS 2) deployed by OP1 in VPLMN (e.g. based on a federation agreement). The AF invokes Nnef\_TrafficInfluence\_Create or Nnef\_TrafficInfluence\_Update service operation to send the request message to NEF, or invokes Npcf\_PolicyAuthorization\_Create or Npcf\_PolicyAuthorization\_Update to send the request + +message to the PCF directly. The request message includes the PLMN ID, which indicates the EAS should be relocated to the target PLMN (identified by PLMN ID). + +If 5GC supports EAS IP replacement mechanism, 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 V-SMF as specified in clause 6.3.3 of TS 23.548 [3]. Alternatively, the AF sends the EAS information (e.g. EAS IP address) to network and to UE via application layer. + +2. If the PCF authorizes the traffic routing in the VPLMN is allowed, the PCF creates and sends the PCC rule to the V-SMF by invoking Npcf\_SMPolicyControl\_UpdateNotify service operation. The PCC rule includes the PLMN ID. +3. H-SMF discovers the V-SMF. + +If the H-SMF has knowledge of EAS deployment information in VPLMN, the H-SMF determines the target DNAI based on the EAS deployment information and IP address of target EAS. H-SMF sends the target DNAI to the H-AMF by invoking Nsmf\_PDUSession\_SMContextStatusNotify service operation. Then, H-AMF selects V-SMF based on the target DNAI. Then, V-SMF sends Nsmf\_PDUSession\_Context Request to H-SMF. + +Alternatively, the H-SMF sends discovery request to hNRF by invoking Nnrf\_NFDiscovery\_Request (home PLMN ID, serving PLMN ID), and discovers the V-SMF as specified in clause 4.17.5 in TS 23.502 [9]. + +4. The H-SMF inserts or changes the UL-CL/BP H-UPF. The H-SMF sends an inter-PLMN relocation indicator to V-SMF by Nsmf\_PDUSession\_Update Request. The inter-PLMN relocation indicator is to indicate the EAS is relocated from HPLMN to VPLMN. Optionally, the H-SMF may check with H-UDM whether UE is authorized to access VPLMN. +5. The V-SMF selects the V-PSA UPF based on the EAS IP replacement information/EAS information. V-SMF configures the V-PSA UPF for traffic routing towards target EAS. If the EAS IP replacement information is received, the V-SMF configures V-PSA UPF with EAS IP replacement information. +6. The V-SMF sends the acknowledgement message to the H-SMF, which includes the tunnel information towards V-PSA UPF. +7. When H-SMF receives the acknowledgement, H-SMF configures the UL-CL/BP H-UPF for traffic routing towards V-PSA UPF if the destination address is the IP address of source EAS or target EAS. + +### 6.39.2.3 EAS relocation between operators via N6 (KI #5) + +![Sequence diagram illustrating EAS relocation between operators via N6 (KI #5). The diagram shows interactions between PLMN2 (EAS) and PLMN1 (UE, PSA UPF, SMF, NEF/PCF, AF).](d5f4af137f0f2f002c86899367868c81_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PSA_UPF as PSA UPF + participant SMF + participant NEF_PCF as NEF/PCF + participant AF + participant EAS as EAS (PLMN2) + + Note right of UE: 0. PDU session is established in PLMN1 + Note right of AF: 1. Nnef_TrafficInfluence_Create/Update or Npcf_PolicyAuthorization_Create/Update + Note right of NEF_PCF: 2. Npcf_SMPolicyControl_UpdateNotify + Note right of SMF: 3. SMF inserts or changes PSA UPF and configures traffic routing rule, and EAS IP replacement information. + Note right of UE: 4. UE accesses the EAS deployed in PLMN2 via PSA UPF using controlled IP network. + +``` + +Sequence diagram illustrating EAS relocation between operators via N6 (KI #5). The diagram shows interactions between PLMN2 (EAS) and PLMN1 (UE, PSA UPF, SMF, NEF/PCF, AF). + +Figure 6.39.2.3-1: EAS relocation between operators via N6 + +0. The UE establishes PDU Session to access the source EAS (EAS1) in PLMN1. + +1. When the EAS relocation is triggered, AF determines the source EAS should be relocated to the target EAS (e.g. EAS 2 as shown in figure 6.39.1-3) deployed by OP2 in target PLMN2 (e.g. based on a federation agreement). The AF invokes Nnef\_TrafficInfluence\_Create or Nnef\_TrafficInfluence\_Update service operation to send the request message to NEF, or invokes Npcf\_PolicyAuthorization\_Create or Npcf\_PolicyAuthorization\_Update to send the request message to the PCF directly. The request message includes the PLMN ID, which can be used as an inter-PLMN relocation indicator and indicates the EAS should be relocated to the target PLMN (identified by PLMN ID). + +If 5GC supports EAS IP replacement mechanism, 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 V-SMF as specified in clause 6.3.3 of TS 23.548 [3]. Alternatively, the AF sends the EAS information (e.g. EAS IP address) to network and to UE via application layer. +2. If the PCF authorizes the traffic routing in the PLMN1 (serving PLMN) is allowed, the PCF creates and sends the PCC rule to the SMF by invoking Npcf\_SMPolicyControl\_UpdateNotify service operation. The PCC rule includes the PLMN ID. +3. Based on the received PLMN ID, the SMF can differentiate the EAS deployment information of different PLMNs (the PLMN ID is included in the EAS deployment information) and determine the target DNAI corresponding to PLMN1, and then SMF inserts or changes the PSA UPF that supports target DNAI to access target EAS via controlled IP network. The SMF configures the PSA UPF for traffic routing towards target EAS. If the EAS IP replacement information is received, the SMF configures UPF with EAS IP replacement information. +4. UE accesses the EAS deployed in PLMN2 using PSA UPF via N6. + +### 6.39.3 Impacts on services, entities and interfaces + +#### 6.39.3.1 EAS relocation between VPLMN and HPLMN (clause 6.39.2.1 and 6.39.2.2) + +##### AF: + +- determines the target EAS and sends corresponding PLMN ID. + +##### V-SMF: + +- determines target DNAI based on EAS information and EAS deployment information; +- sends an inter-PLMN relocation indicator to H-SMF; +- configures the UL-CL/BP V-UPF for traffic routing towards H-PSA UPF if the destination address is the IP address of source EAS or target EAS. + +##### H-SMF: + +- determines target DNAI based on EAS information and EAS deployment information; +- sends an inter-PLMN relocation indicator to V-SMF; +- configures the UL-CL/BP H-UPF for traffic routing towards V-PSA UPF if the destination address is the IP address of source EAS or target EAS. + +##### PCF: + +- authorizes the traffic routing in the target PLMN is allowed; +- creates the PCC rule, which includes the PLMN ID. + +##### H-AMF: + +- selects V-SMF based on the target DNAI received from H-SMF. + +##### EAS Deployment information: + +- adding PLMN ID. + +### 6.39.3.2 EAS relocation between operators via N6 (clause 6.39.2.3) + +AF: + +- determines the target EAS and sends corresponding PLMN ID. + +PCF: + +- authorizes the traffic routing in the target PLMN is allowed; +- creates the PCC rule, which includes the PLMN ID. + +EAS Deployment information: + +- adding PLMN ID. + +## 6.40 Solution 40 (KI#5): EAS discovery for shared EHE + +### 6.40.1 Introduction + +This solution addresses Key Issue #5 and allows the discovery of an Edge Application Server (EAS) within a set of Operators sharing the EHE. It is assumed that the EAS is hosted by a different PLMN than the PLMN that is serving the UE, and the two PLMNs have IP connection at edge area. + +### 6.40.2 Functional description + +In this solution description, it is assumed that the EAS is deployed in MNO2's PLMN2 and that the UE is connected to MNO1's PLMN1 (see figure 6.40.2-1). The solution is based on the following two steps: + +#### Step 1: Configuration phase + +The MNO2 AF provides the DNS query filtering information for PLMN2 EHE as well as the EASDF Deployment information for PLMN2 described in table 6.40.2-1 to EASDF1 in PLMN1 before the PDU Session establishment. + +#### Step 2: After PDU Session establishment + +When a DNS query from UE is intended for a specific application at edge, but EASDF1 in PLMN1 finds that the application cannot be found in current PLMN1's edge platform but can be found in PLMN2's DNS query filtering information, the EASDF1 will send (UE IP address, DNS handling rule) created by SMF1 to the selected EASDF2 through SEPP through control plane. Then, EASDF1 forwards the DNS Query message to EASDF2 through user plane. EASDF2 then sends the DNS query to DNS server in PLMN2 for EAS discovery. + +DNS query filtering information includes the PLMN2's supported EAS FQDN(s). + +The EASDF2 is selected by EASDF1 based on UE location, EASDF2 serving area, EDI information for PLMN2 EHE, and the N6 Transmission requirement. + +EASDF1 sends DNS query to EASDF2 through user plane. The DNS query is transmitted in the path of EASDF1→UPF1→UPF2→EASDF2. The UPF1 and UPF2 are locally configured to support the DNS message transmission between two PLMNs. + +The indication of supporting shared EAS discovery will be included in UE SM subscription data. SMF1 gets this information from UDM1 during the PDU Session establishment. SMF1 may select the proper UPF(s) to support the DNS message transmission via two PLMNs. The UPF(s) in PLMN1 which support access to PLMN2 domain, may support to add DSCP value in IP layer to guarantee the transmission between two PLMNs. + +MNO2 AF may create an External Group ID to show that these UE(s) support the interaction between different PLMNs. + +![Figure 6.40.2-1: Architecture with Operator Platform. The diagram shows two PLMNs, MNO1's PLMN1 and MNO2's PLMN2, separated by a dashed line. In PLMN1, a UE connects to an (R)AN, which connects to an AMF. The AMF connects to an SMF via N11 and to an EASDF via N14. The SMF connects to a UPF via N4. The UPF connects to a DN via N6 and to an EASDF via N9. The DN connects to an EDN (EAS) in PLMN2. In PLMN2, an AMF connects to an SMF via N11 and to an EASDF via N14. The SMF connects to a UPF via N4. The UPF connects to a DN via N6 and to an EASDF via N9. The DN connects to an EDN (EAS) in PLMN2. A red line indicates a connection between the EASDF in PLMN1 and the EASDF in PLMN2.](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) + +Figure 6.40.2-1: Architecture with Operator Platform. The diagram shows two PLMNs, MNO1's PLMN1 and MNO2's PLMN2, separated by a dashed line. In PLMN1, a UE connects to an (R)AN, which connects to an AMF. The AMF connects to an SMF via N11 and to an EASDF via N14. The SMF connects to a UPF via N4. The UPF connects to a DN via N6 and to an EASDF via N9. The DN connects to an EDN (EAS) in PLMN2. In PLMN2, an AMF connects to an SMF via N11 and to an EASDF via N14. The SMF connects to a UPF via N4. The UPF connects to a DN via N6 and to an EASDF via N9. The DN connects to an EDN (EAS) in PLMN2. A red line indicates a connection between the EASDF in PLMN1 and the EASDF in PLMN2. + +Figure 6.40.2-1: Architecture with Operator Platform + +## EASDF Deployment Information + +EASDF1 finds EASDF2 based on EASDF Deployment Information (EDI) information including UE location, serving area of EASDF2 in PLMN2, N6 transmission requirement of PLMN2. + +Table 6.40.2-1: EASDF Deployment Information + +| Parameters | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN ID(s) | Used to identify in which PLMN the EAS is located | +| EASDF FQDN(s) | FQDN(s) of EASDF in other PLMN | +| Serving area(s) | Serving area where the EASDF can provide service | +| External Group Identifier/Internal Group Identifier | Group ID for the EAS Deployment information. [optional] (NOTE 1) | +| N6 Transmission requirement (e.g. DSCP) | Transmission requirements when packet transmit between two PLMNs. This parameter will be added by UPF of PLMN1 in the IP-layer when packet is sent out from PLMN1 to PLMN2. [optional] | +| NOTE 1: 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. The PLMN2 provides external group identifier to PLMN1 thus PLMN1 can identify that the UE is allowed to access the EAS in PLMN2. | | + +### 6.40.3 Procedures + +![Sequence diagram for EAS discovery in shared EAS scenario. The diagram shows interactions between UE, SMF, UPF PSA, UPF UL CL/BP, UPF L-PSA, EASDF1, UPF1, UPF2, EASDF2, and DNS server. The process involves DNS queries, Neasdf_DNSContext notifications, and context creation between EASDF1 and EASDF2.](48090d8f1db2e826aaa740035aa12ecb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant UPF_PSA as UPF PSA + participant UPF_UL as UPF UL CL/BP + participant UPF_L as UPF L-PSA + participant EASDF1 + participant UPF1 + participant UPF2 + participant EASDF2 + participant DNS as DNS server + + Note left of UE: 1. step 1-6 described in TS 23.548 clause 6.2.3.2.2 + UE->>EASDF1: 2.DNS query + EASDF1->>SMF: 3.Neasdf_DNSContext_Notify Request + SMF->>EASDF1: 4.Neasdf_DNSContext_Notify Response + EASDF1->>EASDF2: 5.Neasdf_DNSContext_Create Request + EASDF2->>EASDF1: 6.Neasdf_DNSContext_Create Response + EASDF1->>UPF2: 7.DNS query + UPF2->>DNS: 8.DNS query + DNS->>UPF2: 9.DNS response + UPF2->>EASDF1: 10.DNS response + EASDF1->>SMF: 11.Neasdf_DNSContext_Notify Request + SMF->>EASDF1: 12.Neasdf_DNSContext_Notify Response + Note right of SMF: 13.UL CL/BP insertion, PSA relocation + SMF->>EASDF1: 14.Neasdf_DNSContext_Update Request + EASDF1->>SMF: 15.Neasdf_DNSContext_Update Response + SMF->>UE: 16.DNS response + +``` + +Sequence diagram for EAS discovery in shared EAS scenario. The diagram shows interactions between UE, SMF, UPF PSA, UPF UL CL/BP, UPF L-PSA, EASDF1, UPF1, UPF2, EASDF2, and DNS server. The process involves DNS queries, Neasdf\_DNSContext notifications, and context creation between EASDF1 and EASDF2. + +**Figure 6.40.3-1: EAS discovery in shared EAS scenario** + +1. Steps 1-6 are the same as EAS discovery procedure in clause 6.2.3.2.2 of TS 23.548 [3]. + 2. UE sends DNS query to EASDF1. + 3. If EASDF1 finds the DNS Query message cannot be resolved by PLMN1's DNS server, but matches a PLMN2's FQDN(s) information, EASDF1 sends the DNS Query Message to SMF with providing indication that EASDF2 in PLMN2 should be selected. +- NOTE: When EASDF receives multiple DNS Query messages from one UE, if EASDF detects that these DNS Query messages are the same, EASDF will only send the Neasdf\_DNSContext\_Notify Request once to SMF for these DNS Query messages. +4. The SMF responds with Neasdf\_DNSContext\_Notify Response. + 5. EASDF1 invokes Neasdf\_DNSContext\_Create Request (UE IP address, PLMN1 ID, notification endpoint, (DNS message handling rules)) to the selected EASDF2 in PLMN2. + +The EASDF2 creates a DNS context for the PDU Session and stores the UE IP address, PLMN1 ID, notification endpoint, (DNS message handling rules) into the context. + +The DNS handling rule is created by SMF and redirected to EASDF1 and EASDF1 sends this to EASDF2. In this handling rule, option A is used to forward the DNS message with the EDNS Client Subnet option that is updated to UE location information. Option B is not supported since the EASDF1 does not have DNS address in PLMN2. + +6. The EASDF2 invokes the service operation Neasdf\_DNSContext\_Create Response. +7. EASDF1 sends DNS query to EASDF2 through user plane. The DNS query may pass through UPF1 which is able to access UPF2 in PLMN2. The DSCP value can be added by UPF1 in DNS query IP layer to satisfy transmission requirement with low latency between two PLMNs. +- 8-9. The same as steps 12-13 in clause 6.2.3.2.2 in TS 23.548 [3]. +10. EASDF2 returns DNS response (EAS IP address or FQDN) to EASDF1. +- 11-12. The same as steps 14-15 in clause 6.2.3.2.2 in TS 23.548 [3]. +13. The SMF may perform UL-CL/BP and Local PSA selection and insert UL-CL/BP and Local PSA. +- 14-16. The same as steps 17-19 in clause 6.2.3.2.2 in TS 23.548 [3]. + +During PDU Session Release procedure, the SMF triggers the removal of the DNS context by invoking Neasdf\_DNSContext\_Delete service from EASDF1 to EASDF2. + +#### 6.40.4 Impacts on existing entities and interfaces + +##### EASDF: + +- enhanced to support to communicate with EASDFs in other PLMN to transform DNS handling rule and related information; +- needs to be configured with EASDF Deployment information to discover other PLMN's EASDF. + +##### UDM: + +- UE authorization for EAS discovery via other PLMN's EASDF. + +##### UPF: + +- enhanced to support the addition of N6 Transmission requirement (e.g. DSCP) into IP-layer to ensure low latency. + +##### AF: + +- can configure other PLMN's DNS query filtering information and EASDF deployment information in serving PLMN. + +### 6.41 Solution 41 (KI#6): Controlling non-3GPP access of EC traffic via URSP and ATSSS + +#### 6.41.1 High level description + +If a network is to apply EC-related functionality such as providing connectivity to the edge for all or part of the traffic for a given PDU Session, and the EC-related functionality requires specific consideration of traffic steering to the non-3GPP access, then the network re-configures the URSP rules in the UE for the RDS corresponding to the EC traffic. Examples of useful URSP rules: + +- setting the Access Type Preference to "3GPP" for the given EC traffic descriptors, DNN and S-NSSAI. This will result in setting up the PDU Session carrying the EC traffic on the 3GPP access. +- setting the Access Type Preference to "Multi-access" for the given traffic descriptors, DNN and S-NSSAI. + +The latter is used when a refined control of traffic steering over the 3GPP and non-3GPP accesses is needed, based on appropriate ATSSS rules for the PDU Session provided by the network (SMF). Examples of useful ATSSS rules to control steering EC traffic to non-3GPP access (see clause 5.32.8 of TS 23.501 [2]): + +- Steering Mode=Active-Standby, Active=3GPP & no Standby (octet f+4=00000001): it results in steering the related traffic within the PDU Session (described by the traffic descriptors) always to the 3GPP access; +- Steering Mode=Load Balancing allows for using the non-3GPP access based on latency and loss thresholds. + +NOTE 1: SMF may change the access network over which the traffic of a GBR QoS flow is transmitted, and in this way it can both select the access for this QoS flow and provide bandwidth guarantees. + +The solution may be applied for all connectivity models. + +NOTE 2: How the URSP settings interact with built-in UE policies or user preferences to influence the UE's decision to use connectivity outside of 5GC is out of scope. + +## 6.41.2 Procedures + +For Multiple Sessions and Distributed Anchor connectivity models, the existing procedures are applicable, where the following options may be used: + +- the URSP rules and ATSSS rules are configured in the UE before or during the setup of the PDU Session, if the corresponding non-3GPP access related policies are already available; +- if the URSP rules are dynamically updated (based on Application guidance for URSP determination clause 4.15.6.10 in TS 23.502 [9]) while some EC traffic is ongoing on a PDU Session, the updated rules might not be enforced by the UE immediately for this traffic, but they will be applied for any application traffic that will start later. Updating the URSP rules requires SMF notification towards the UE PCF. + +For the Session Breakout scenario, only the 3GPP access should be allowed for the EC traffic, because the UL-CL is reachable only through that access, since there are no ATSSS procedures that would ensure that an UL-CL can be on path when the UE connects through a non-3GPP access. Based on the received EC related policy and deployment information the SMF may, however, select an UL-CL based on existing procedures if the UE connects through a 3GPP access. One simple solution to keep the EC traffic to 3GPP access is to set the Access Type Preference to "3GPP" in the corresponding URSP rule for this PDU Session. To avoid other, non-EC traffic be constrained to the 3GPP access, WIFI offload can be setup for that traffic using the "Non-Seamless Offload indication" as route selection in the corresponding URSP rule. An example URSP rule set is given in table 6.41.2-1. Note that the traffic descriptors in the URSP rules may need to be updated, e.g. based on AF Application guidance for URSP determination, resulting that the updated URSP rules might not be immediately enforced for some ongoing traffic. + +**Table 6.41.2-1: Example URSP rules to restrict EC traffic to 3GPP access in the Session Breakout model** + +| URSP rules | | Comments | +|---------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rule Precedence =1

Traffic Descriptor:
Application descriptor=App1
IP descriptor = Destination_prefix1 | Route Selection Descriptor
Precedence = 1
DNN Selection: internet
Access Type preference: 3GPP access | This URSP rule associates the traffic of application "App1" and the traffic to "Destination_prefix1" 3GPP access and the "internet" DNN.

It enforces the following routing policy:
The traffic of App1 as well as the traffic to "Destination_prefix1" should be transferred on a PDU Session supporting DNN=internet over 3GPP access. If this PDU Session is not established, the UE shall attempt to establish a PDU Session with the "internet" DNN over 3GPP access. | +| Rule Precedence =default

Traffic Descriptor: * | Route Selection Descriptor
Precedence = 1
Non-seamless Offload indication: Permitted | This URSP rule enables all the traffic that is not covered by the previous rule of higher preference be directly offloaded to WLAN, if the UE is connected to a WLAN | + +A specific case in the Session Breakout model is when the EC traffic shares the PDU Session with other traffic that requires traffic steering based on ATSSS. In that case the Access Type Preference in the URSP rule for this traffic is set to "Multi-access", based on which the UE sets up a MA PDU Session for this DNN and S-NSSAI on all available accesses. The MA PDU Session is set up to a C-PSA, where the ATSSS functionality is applied for the non-EC traffic. + +The SMF configures ATSSS rules for the EC traffic (identified by Application ID or IP ranges in route descriptors) that steer the traffic always to the 3GPP access (using Steering Mode=Active-Standby, see clause 6.41.1). Other traffic may be allowed to be offloaded to WIFI by URSP rules as described above. + +For Dynamic PSA distribution using EASDF, URSP rules could be set similarly as for the Session Breakout Scenario, see table 6.41.2-1, assuming that the PCF knows the traffic descriptors of the EC applications. Further flexibility for the EC applications may be achieved by using the ATSSS rules. An example solution based on ATSSS rules is depicted in the generic figure below: + +![Sequence diagram illustrating the ATSSS solution for controlling non-3GPP usage for Dynamic PSA distribution. The diagram shows interactions between APP, UE, 3GPP access, non-3GPP access, N3IWF/TNGF, L-PSA, C-PSA, SMF, PCF, and EAS. The sequence includes: 1. PDU session establishment (C-PSA) and EASDF context creation and update; 2. DNS EAS discovery triggering dynamic PSA change from C-PSA to L-PSA; 3. PDU Session Modification (SSC Mode 3) or Release (SSC Mode 2); 4. MA PDU session establishment (L-PSA); 5. Configure ATSSS rules; 6. Apply ATSSS rules. Below the sequence, two UP paths for EC traffic are shown: one through 3GPP access and another through non-3GPP access, both leading to the EAS via the L-PSA.](9d47fe89bc71acebde670ea760ee6ffb_img.jpg) + + + +Sequence diagram illustrating the ATSSS solution for controlling non-3GPP usage for Dynamic PSA distribution. The diagram shows interactions between APP, UE, 3GPP access, non-3GPP access, N3IWF/TNGF, L-PSA, C-PSA, SMF, PCF, and EAS. The sequence includes: 1. PDU session establishment (C-PSA) and EASDF context creation and update; 2. DNS EAS discovery triggering dynamic PSA change from C-PSA to L-PSA; 3. PDU Session Modification (SSC Mode 3) or Release (SSC Mode 2); 4. MA PDU session establishment (L-PSA); 5. Configure ATSSS rules; 6. Apply ATSSS rules. Below the sequence, two UP paths for EC traffic are shown: one through 3GPP access and another through non-3GPP access, both leading to the EAS via the L-PSA. + +**Figure 6.41.2-1: ATSSS solution for controlling non-3GPP usage for Dynamic PSA distribution** + +1. UE sets up a PDU Session. The session is initially set up to a C-PSA and the URSP rules in the UE need not contain any constraints related to non-3GPP usage. The UE may indicate in the session establishment message its ATSSS capability and that "MA-PDU Network upgrade allowed" for this PDU Session, which can help selecting an ATSSS capable SMF for this PDU Session. SMF creates/updates the EASDF context for this PDU Session. +2. A DNS query for the EAS discovery from the UE APP triggers dynamic PSA change in the SMF. +3. SMF initiates a PDU Session modification or PDU Session release depending on the SSC Mode selected. +4. The UE initiates a PDU Session establishment, where the UE indicates in the session establishment message its ATSSS capability and that "MA-PDU Network upgrade allowed" for this PDU Session. The SMF (that may be a new SMF that receives indication to provide connectivity to the edge from the AMF in the form of a DNAI) selects an edge UPF (L-PSA), and it provisions the DNS settings in the UE, as described in clause 6.2.2.4 of TS 23.548 [3]. The SMF also upgrades the session to a MA PDU Session, based on related policy rules that may be received from the PCF. If UE is registered to non-3GPP access, then the UE initiates a MA PDU Session establishment also on this leg. Otherwise, it initiates another MA PDU Session establishment when it connects to the non-3GPP. +5. SMF configures ATSSS rules for this MA PDU Session that will define how the different accesses may be used by the EC application. +6. UE starts applying the ATSSS rules for this PDU Session. The EC application traffic will be routed to the EAS through the L-PSA from either allowed access. + +### 6.41.3 Impacts on services, entities and interfaces + +UE: + +- URSP support, and (conditionally, if ATSSS rules apply) ATSSS support. + +NOTE 1: It is expected that the UE supports the URSP rules for non-seamless offload as specified in clause 6.1.2.2.1 of TS 23.503 [13]. + +SMF: + +- (conditionally, if dynamic update to URSP rules apply) notification towards the UE PCF about the EC traffic handling that may be mediated by SM PCF. + +NOTE 2: It is expected that the SMF supports the procedure for EAS discovery in the Session Breakout model as described in TS 23.548 [3] also for the MA PDU Sessions with 3GPP access. + +## 6.42 Solution 42 (KI#6): Network-guided EC traffic switching + +### 6.42.1 General + +#### 6.42.1.1 Introduction + +The KI#6 deals with the scenario where Edge computing enablers cannot be served to the UE when the UE has taken a decision to switch application traffic to a route that is not integrated with MNO. In a typical scenario, UE considers multiple inputs before choosing the best of the available routes for application traffic. The range of inputs include user and application preferences, power consumption status of the UE, delay status in both routes, server loading status, etc. + +When the 5G connectivity offers additional benefits for edge computing traffic, this information will be critical to the UE before making the decision to switch away traffic that is benefiting from MNO's edge deployments. + +This solution assumes that the EAS is also reachable via Internet, and that the UE application is aware of this and that the UE would not switch the traffic away from 3GPP access if it is not the case. + +#### 6.42.1.2 Description + +The current edge enablers in 5G network are often not visible to the UE. For example, a UE does not know if the application traffic is being carried over a PDU Session that has access to edge data centre. Similarly, whether a PDU Session has a UL-CL and L-PSA inserted for local routing of certain application traffic is not known to the UE. This information is foreseen as an important parameter that UE should consider before deciding on which access to use for certain application traffic, when all other things are equal. + +#### 6.42.1.3 WLAN offload guided by the network + +In the URSP rules today, there is only a possibility to indicate if a given traffic can be offloaded to WLAN. The presence of the route selection component "Non-Seamless Offload indication" in a Route Selection Descriptor and the priority of the Route selection descriptor for a URSP rule informs UE when the corresponding traffic can be offloaded to a non-integrated non-3gpp access. + +However, this method is a static guidance on whether traffic can be routed over non-integrated path corresponding to the priority of the RSD. + +For edge computing traffic, whether the network is currently offering any of the edge optimized routing in the network is an aspect that varies dynamically. To enable the UE to make an informed decision, additional evaluations may be required according to the current nature of traffic routing. + +The URSP information can provide a static guidance to the UE, so that it evaluates the use of edge enablers at the time when traffic switching is decided. A new route selection component in the Route Selection Descriptor is introduced for this purpose. + +**Table 6.42.1.3-1: Addition to table 6.6.2.1-3 of TS 23.503 [13]: Route Selection Descriptor** + +| Information name | Description | Category | PCF permitted to modify in URSP | Scope | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------------|------------| +| WLAN Offload Guidance | The presence of this component indicates that decision on offloading edge computing traffic matching the Traffic Descriptor for this URSP rule is conditional to the evaluation of conditions informed by the network | Optional | Yes | UE context | + +The conditions for switching the traffic are dynamic indications that the network provides to the UE. + +Dynamic conditions are indicated to the UE using the following information. + +First one is an indication that network is using any of the edge enablers for the SDF corresponding to the edge application. This could be for example, the use of L-PSA providing access to an EAS in a local Edge Hosting Environment or a UL-CL with traffic offload in a session break-out model. + +The second component of dynamic condition is a configuration to measure latency experienced by the Edge application. For an application, one of the most important benefits of connecting to an Application Server in edge hosting environment is latency. When the UE has alternate paths to reach an application server, it would be an important parameter to measure the round-trip time for these alternate paths. During the PDU Session establishment/modification, the network configures the UE with necessary measurement configuration to do an RTT measurement (similar to the performance measurement for ATSSS) to the EAS in Edge Hosting environment. The UE triggers measurement on the cellular path and evaluates RTT on alternate paths before deciding which one should be selected to meet applications' requirement. + +## 6.42.2 Procedures + +The following call flow illustrates the procedure for traffic offload guidance. + +![Sequence diagram illustrating Network guided EC traffic switching. The diagram shows interactions between UE, NG-RAN, UPF, SMF, and PCF. The process starts with an App PDU arriving at the UE. The UE evaluates URSP rules and triggers a PDU Session Establishment/Modification Request to the SMF. The SMF requests the UPF to perform RTT measurements to the Application Server (AS) and provides RTT measurement rules to the UE. The UE detects Non-3GPP connectivity options and sends EchoRequests to the UPF. The UPF responds with EchoResponses. The UE computes RTT for the 3GPP link, performs RTT measurements for non-3GPP links, and decides on traffic offload if necessary.](9b069184e680aac7a22df55de63370fa_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant UPF + participant SMF + participant PCF + + Note left of UE: App PDU + UE->>SMF: 2. PDU Session Establishment /Modification Request + SMF->>UPF: 3. At the time of adding an SDF to a QoS Flow or when a new ULCL/BP is inserted, SMF requests UPF to perform RTT measurement to the AS. This value is also informed to the UE through the PDU Session Establishment Accept/Modification. + SMF->>UE: 4. PDU Session Establishment Accept/Modification Command + Note right of UE: As part of PDU Session Establishment Accept/Modification Command UE is provided with ( EC indication (SDF), RTT measurement rules (per SDF), RTT between UPF-AS, Traffic Offload Rule ) + UE->>UPF: 6a. EchoRequest + UPF->>UE: 6b. EchoResponse + Note left of UE: 7. UE computes RTT for 3GPP link + Note left of UE: 8. UE performs RTT measurements for non-3GPP link + Note left of UE: 9. UE decides on traffic offload if necessary + +``` + +Sequence diagram illustrating Network guided EC traffic switching. The diagram shows interactions between UE, NG-RAN, UPF, SMF, and PCF. The process starts with an App PDU arriving at the UE. The UE evaluates URSP rules and triggers a PDU Session Establishment/Modification Request to the SMF. The SMF requests the UPF to perform RTT measurements to the Application Server (AS) and provides RTT measurement rules to the UE. The UE detects Non-3GPP connectivity options and sends EchoRequests to the UPF. The UPF responds with EchoResponses. The UE computes RTT for the 3GPP link, performs RTT measurements for non-3GPP links, and decides on traffic offload if necessary. + +Figure 6.42.2 1: Network guided EC traffic switching + +1. The UE evaluates URSP rules on receiving an application PDU. +2. The UE triggers a PDU Session Establishment/Modification request to carry the application traffic. +3. The SMF fetches appropriate SM Policies for adding this SDF to a QoS Flow. This may also need insertion of UL-CL/BP for the UE. SMF requests UPF to perform RTT measurements to Application Server. The Application Server information for RTT measurement is provided by the AF as part of TrafficInfluence rules. +4. SMF sends PDU Session Establishment Accept or Modification Command to the UE. If UE is configured with edge enablers (e.g. L-PSA or UL-CL/BP) for any traffic carried in this PDU Session, SMF includes an "EC indication" marked per SDF. In this message, SMF also includes performance measurement rules applicable for this SDF, measured RTT value between UPF and Edge Application Server, Traffic offload rule. The traffic offload rule can be either an absolute threshold or factor by which non-3GPP RTT shall be better than 3GPP RTT before UE offloads traffic. + +5. UE detects availability of an alternate non-3GPP path that is suitable for this application traffic. +6. UE performs RTT measurement in the UE-UPF path over 3GPP link. +7. UE computes the aggregate RTT on the 3GPP path as the sum of measured RTT on UE-UPF link and the UPF-AS RTT indicated by the SMF. + +NOTE: The RTT between UPF and an application server in Edge Hosting Environment is considered as a static component of the overall RTT. + +8. UE performs RTT computation between UE and the Application Server over the non-3GPP link. +9. UE applies the network provided traffic offload rule provided by the network to the decision matrix for traffic offload. + +### 6.42.3 Impacts to existing nodes + +SMF: + +- provides an EC indication per SDF if any edge enablers are configured for the traffic; +- provides RTT measurement rules to the UE, instructs UPF for RTT measurement to the AS. + +PCF: + +- provides "WLAN Offload guidance" as part of RSD in URSP rules for a traffic descriptor that may be subject to dynamic evaluation of edge performance prior to traffic offload; +- provides SM Policy rules with information for UPF-AS RTT measurement to the SMF. + +UPF: + +- performs UPF-AS RTT measurements; +- enables UE-UPF performance measurements. + +UE: + +- understands the URSP rules with traffic offload guidance; +- performs performance measurement and applies the results according to the configured traffic offload rules. + +## 6.43 Solution 43 (KI#6): Network-based solution for keeping EC traffic on 3GPP Access + +### 6.43.1 Description + +When UE has several available access types in the UE location, the UE may switch from 3GPP access to non-3GPP access; for example, at home, the non-3GPP usually has better performance or non-3GPP has higher priority than 3GPP access. + +But for the EC traffic on UE, if the traffic is switched from 3GPP access to non-3GPP access, the EC features might not be maintained, for example, the N3IWF is located in the central, and the traffic should be routed to central PSA and routed back to EAS in the local area. + +One of the solutions is, when UE triggers PDU Session establishment using the PDU Session ID of EC traffic towards 5GC in non-3GPP access, the 5GC can judge this PDU Session is an EC PDU Session, and rejects the PDU Session establishment request. So, the UE can keep the EC PDU Session to not switched to non-3GPP access, and still use this EC PDU Session to communicate with EAS via 3GPP access. + +NOTE: This solution applies to the situation of 5GC controlled non-3GPP access procedure, also called integrated non-3GPP. + +## 6.43.2 Procedures + +### 6.43.2.1 Network sides rejects EC-PDU Sessions handover from 3GPP Access to non-3GPP Access + +![Sequence diagram illustrating the network-based solution for keeping EC traffic on 3GPP Access. The diagram shows interactions between UE, Non-3GPP Access, N3IWF/TN GF, RAN, AMF, SMF, UPF, and PCF. Step 1: Registration via non-3GPP access (dashed line). Step 2: PDU session establishment procedure (solid line). Step 3: SMF identifies the EC PDU sessions (solid line). Step 4: SMF rejects the PDU session establishment (solid line with arrow to UE).](de18140c2e0030a43004b58338467655_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Non-3GPP Access + participant N3IWF/TN GF + participant RAN + participant AMF + participant SMF + participant UPF + participant PCF + + Note left of AMF: 1. Registration via non-3GPP access + UE->>AMF: + Note right of AMF: 2. PDU session establishment procedure: step 1 to step 2a in clause 4.12.5 of TS 23.502[x], or in clause 4.12a.5 of TS 23.502[x] + AMF->>SMF: + Note right of SMF: 3. SMF identifies the EC PDU sessions + SMF->>AMF: + AMF->>UE: 4. SMF rejects the PDU session establishment + +``` + +Sequence diagram illustrating the network-based solution for keeping EC traffic on 3GPP Access. The diagram shows interactions between UE, Non-3GPP Access, N3IWF/TN GF, RAN, AMF, SMF, UPF, and PCF. Step 1: Registration via non-3GPP access (dashed line). Step 2: PDU session establishment procedure (solid line). Step 3: SMF identifies the EC PDU sessions (solid line). Step 4: SMF rejects the PDU session establishment (solid line with arrow to UE). + +**Figure 6.43.2.1-1: Network-based solution for keeping EC traffic on 3GPP Access** + +1. If the UE is not registered via non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2 (untrusted non-3GPP access) of TS 23.502 [9] or as defined in clause 4.12a.2.2 of TS 23.502 [9]. +2. The UE performs PDU Session Establishment procedure in non-3GPP Access with the PDU Session ID of the PDU Session to be moved as specified from step 1 to step 2a in clause 4.12.5 of TS 23.502 [9] or in clause 4.12a.5 of TS 23.502 [9]. At this stage, the PDU Session ID includes both the EC PDU Session to EAS and non-EC PDU Session to non-EAS. + +The UE can have an indication of the preference of whether the some of the PDU Sessions should be switched to non-3GPP access or not, to 5GC, essentially the PDU Session ID of EC PDU Session towards EAS. There exists the situation that user's preference is to access non-3GPP, and not to keep the EC PDU Session at 5GS. + +3. The SMF receives the PDU Session establishment request from UE, that includes multiple PDU Session IDs. The SMF can identify the PDU Session is EC or non-EC, according to PDU Session ID. Also, SMF can identify the PDU Session is EC or non-EC PDU, according to the PDU Session parameters that PDU Session ID refers to, that helps SMF to identify whether it is EC PDU Session or not: + +- S-NSSAI: The SMF identifies the whether the S-NSSAI the PDU Session access is local or not. +- DNN: The SMF identifies the whether the DNN the PDU Session selects is local or not. +- PSA IP address: The SMF checks the PSA IP address that serves the UE, and decides whether the PSA IP address is located in the IP range of local area or local data network. + +4. According to the PDU Session ID, the PDU Session parameters that PDU Session ID and user's preference, the SMF may reject the PDU Session establishment request, if: + +- PDU Session ID represents an EC PDU Session; +- there is no user preference of whether the EC PDU Session switch from 3GPP access to non-3GPP access towards the EC PDU Session. + +The SMF sends the rejection of the PDU Session ID that EC PDU Session refers to, to UE via NAS message. The reason of rejection in NAS message is: the PDU Session over non-3GPP Access is not allowed. + +After UE receives the rejection, the UE can keep the EC PDU Session on 3GPP access which the rejection of PDU Session ID refers to in the NAS message. + +### 6.43.2.2 UE decides PDU Session handover according to NWDAF analytics + +In study of Rel-18 FS\_AIMLsys, the UE obtaining the NWDAF analytics is discussed and the UE can acquire the analytics from NWDAF via DCAF or NAS messages. + +In Rel-17, the NWDAF can provide the analytics of service experience in both 3GPP Access and non-3GPP Access according to the table 6.4.3-1 of TS 23.288 [19]. + +**Table 6.43.2.2-1: Service Experience statistics (Referred to table 6.4.3-1 of TS 23.288 [19])** + +| Information | Description | +|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Application service experiences (0..max) | List of observed service experience information for each Application. | +| > S-NSSAI | Identifies the Network Slice used to access the Application. | +| > Application ID | Identification of the Application. | +| > Service Experience Type | Type of Service Experience analytics, e.g. on voice, video, other. | +| > UE location | Indicating the UE location information (e.g. TAI list, gNB ID, etc) when the UE service is delivered. | +| > UPF Info | Indicating UPF serving the UE. | +| > DNN | DNN for the PDU Session which contains the QoS flow. | +| > Application Server Instance Address | Identifies the Application Server Instance (IP address of the Application Server) or FQDN of Application Server. | +| > Service Experience | Service Experience over the Analytics target period (average, variance). | +| > SUPI list (0..SUPImax) | List of SUPI(s) with the same application service experience. | +| > Ratio | Estimated percentage of UEs with similar service experience (in the group, or among all UEs). | +| > Spatial validity | Area where the Application service experience analytics applies. | +| > Validity period | Validity period for the Application service experience analytics as defined in clause 6.1.3 of TS 23.288 [19]. | +| > RAT Type | Indicating the list of RAT type(s) for which the application service experience analytics applies. | +| > Frequency | Indicating the list of carrier frequency value(s) of UE's serving cell(s) where the application service experience analytics applies. | + +Also, the NWDAF can provide WLAN performance in certain area or under certain SSID as indicated in table 6.11.3-1 of TS 23.288 [19]. + +The performance of different Access mode includes: QoS flow Bit Rate, QoS flow Packet Delay, Packet retransmission, UL/DL data rate, etc. + +When UE obtains the analytics above from NWDAF in certain UE location and time range, the UE can decide whether to handover the EC-PDU Session from 5GC to non-3GPP access according to the performance. For example, if in the certain UE location and time, the EC-PDU Session in 3GPP Access has better performance than the non-3GPP Access, for example, the lower packet loss and higher UL/DL data rate, the UE can decide to not handover the EC-PDU Session to non-3GPP Access, and vice versa. + +![Sequence diagram illustrating NWDAF based solutions for keeping EC traffic not handover to non-3GPP Access. The diagram shows interactions between UE, Non-3GPP Access, N3IWF/TN GF, RAN, AMF, SMF, UPF, and NWDAF. The process involves registration via non-3GPP access, obtaining analytics from NWDAF, comparing performance, deciding not to handover, and then establishing a PDU session.](a0bd5927fc9594395881eedffd55129a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Non-3GPP Access + participant N3IWF/TN GF + participant RAN + participant AMF + participant SMF + participant UPF + participant NWDAF + + Note left of UE: 1. Registration via non-3GPP access + UE->>Non-3GPP Access: + Non-3GPP Access->>N3IWF/TN GF: + N3IWF/TN GF->>RAN: + RAN->>AMF: + AMF->>SMF: + SMF->>UPF: + AMF->>NWDAF: + Note right of NWDAF: 2. UE obtains the analytic from NWDAF about 3GPP Access and non-3GPP Access in certain location and time range + NWDAF->>AMF: + AMF->>RAN: + RAN->>N3IWF/TN GF: + N3IWF/TN GF->>Non-3GPP Access: + Note left of UE: 3. UE compares the performance between 3GPP Access and non-3GPP Access + UE->>UE: + Note left of UE: 4. UE decides the EC-PDU session ID that not handover to non-3GPP Access + UE->>UE: + Note right of UE: 5. PDU session establishment procedure: step 1 to step 2a in clause 4.12.5 of TS 23.502[x], or in clause 4.12a.5 of TS 23.502[x] + UE->>Non-3GPP Access: + +``` + +Sequence diagram illustrating NWDAF based solutions for keeping EC traffic not handover to non-3GPP Access. The diagram shows interactions between UE, Non-3GPP Access, N3IWF/TN GF, RAN, AMF, SMF, UPF, and NWDAF. The process involves registration via non-3GPP access, obtaining analytics from NWDAF, comparing performance, deciding not to handover, and then establishing a PDU session. + +**Figure 6.43.2.2-1: NWDAF based solutions for keeping EC traffic not handover to non-3GPP Access** + +1. If the UE is not registered via non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2 (untrusted non-3GPP access) of TS 23.502 [9] or as defined in clause 4.12a.2.2 of TS 23.502 [9]. + +2. UE obtains the analytics from NWDAF. The Analytic ID includes Service Experience, WLAN Performance. After UE obtains the analytics from NWDAF, the UE can receive both of the performance under 3GPP Access and non-3GPP Access in certain UE location and time range, for example, the QoS flow Bit Rate, QoS flow Packet Delay, Packet retransmission, UL/DL data rate, etc. +3. UE compares the performance between 3GPP Access and non-3GPP Access of a certain EC PDU Session. +4. If the UE decides that an EC PDU Session established in 3GPP Access has better performance than non-3GPP Access, the UE decides to not handover this PDU Session from 3GPP Access (for example, 5GS) to non-3GPP Access. If the PDU Session established in 3GPP Access has worse performance than non-3GPP Access, the PDU Session ID which the PDU Session referred to should be selected out, and to be used in step 5, to handover to non-3GPP Access to acquire better performance. +5. The UE performs PDU Session Establishment procedure in non-3GPP Access with the PDU Session ID selected by UE in step 4 of the PDU Session to be moved as specified from step 1 to step 2a in clause 4.12.5 of TS 23.502 [9] or in clause 4.12a.5 of TS 23.502 [9]. + +At this stage, the PDU Session which has worse performance in non-3GPP Access should not be included in the PDU Session Establishment procedure. + +#### 6.43.4 Impacts on services, entities and interfaces + +UE: + +- provides the user's preference in NAS messages which access type are preferred or whether the PDU Session is expected to switched to non-3GPP or not. + +SMF: + +- according to the user's preference and the PDU Session ID, the SMF identifies the EC PDU Session and rejects the PDU Session establishment request from UE. + +### 6.44 Solution 44 (KI#6): EAS traffic switching avoidance + +#### 6.44.1 Description + +This solution addresses Key Issue #6: Avoiding UE to Switch away from EC PDU Session. + +This solution considers a scenario where a UE discovers an EAS with assistance of 5GC and uses a PDU Session for the data traffic exchange between application in the UE and the discovered EAS. When non-integrated connectivity becomes available for the UE, the UE connectivity setting (e.g. WiFi is on) may induce that the data traffic for the EAS is switched from the PDU Session to other session associated to the connectivity which is outside of 5GS. Then, local access via UL-CL/BP and local PSA to the EAS cannot be supported for the UE. To prevent this, 5GC may indicate to the UE that the traffic for EAS discovered via 5GC assistance (e.g. with EASDF) shall not be switched away from the PDU Session to other session associated to the access (e.g. non-integrated Wi-Fi) that is not integrated with 5GS even if the non-integrated connectivity becomes available for the UE. Such indication is based on the UE subscription information and delivered by the SMF during the establishment procedure for the PDU Session to which the EAS traffic is mapped. Additionally, the UE needs to support a capability to prevent switching away the EAS traffic according to the indication from the SMF. + +In this regard, this solution proposes a procedure to address the following aspects: (i) how to determine what EAS traffic is targeted for avoidance of switching away from the 5GS for edge computing service and (ii) how to indicate to UE such determination and the related information for the targeted application traffic in order to prevent from switching away from the PDU Session used for edge computing when connectivity outside 5GS (e.g. non-integrated Wi-Fi) becomes available. + +## 6.44.2 Procedures + +![Sequence diagram illustrating EAS traffic switching information provisioning during PDU Session Establishment. The diagram shows interactions between UE, AMF, SMF, and UDM.](c5d9ee57705b6598bd43f9c075fec3c7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UDM + + UE->>AMF: 1. PDU Session Establishment request + AMF->>SMF: 2. Nsmf_PDUSession_CreateSMContextRequest + SMF->>UDM: 3. Nudm_SDM_Get request + UDM-->>SMF: 4. Nudm_SDM_Get response + Note over SMF,UDM: EAS traffic switching information + Note over SMF: 5. EASDF selection and DNS context creation + SMF->>AMF: 6. Namf_Communication_N1N2messageTransfer + Note over AMF,SMF: EAS traffic switching information + AMF->>UE: 7. PDU Session Establishment response + Note over UE,AMF: EAS traffic switching information + Note over UE: 8. Information delivery to upper layer + +``` + +Sequence diagram illustrating EAS traffic switching information provisioning during PDU Session Establishment. The diagram shows interactions between UE, AMF, SMF, and UDM. + +**Figure 6.44.2-1: EAS traffic switching information provisioning during PDU Session Establishment** + +- 1-2. During the PDU Session Establishment procedure, UE may indicate to the SMF its capability to support the EDC functionality and to control application traffic switching via PCO. +3. The SMF invokes Nudm\_SDM\_Get to retrieve the UE subscription information from the UDM. +4. The UDM provides the SMF with the UE subscription information that may include an indication on UE authorization for EAS discovery via EASDF and EAS traffic switching information. The EAS traffic switching information indicates that the traffic for EAS discovered via 5GC assistance (e.g. with EASDF) shall be delivered over 5GS access without being switched away from the PDU Session to other session associated to the access that is not integrated with 5GS (e.g. non-integrated Wi-Fi) even if the non-integrated connectivity becomes available for the UE. +5. The SMF selects an EASDF and perform DNS context creation at the selected EASDF. +- 6-7. The SMF may decide to indicate to the UE either that the use of the EDC functionality is allowed for this PDU Session or that the use of the EDC functionality is required for this PDU Session. If the UE subscription information retrieved in step 4 includes EAS traffic switching information, the SMF indicates to UE that EAS traffic switching control is required via AMF (by invoking Namf\_Communication\_N1N2MessageTransfer service) as follows: + - If the SMF decides to indicate that EDC functionality is allowed, the SMF indicates that EAS traffic switching control is required for the traffic of the application(s) that is mapped onto the PDU Session and explicitly requests the use of the EDC functionality. + - If the SMF decides the use of EDC functionality is required for the PDU Session, the SMF indicates to UE that EAS traffic switching control is required for all the traffic of the application mapped onto the PDU Session. + - If the UE does not indicate its capability to support EDC functionality (i.e. does not support EDC functionality), the SMF indicates to UE that EAS traffic switching control is required for all the traffic of applications that are mapped onto the PDU Session and whose DNS resolution is performed via EASDF. +8. After the successful PDU Session Establishment, the UE informs upper layer with the EAS traffic switching information indicated by the SMF in step 6-7. + +The UE performs EAS traffic switching avoidance for the application traffic associated to the PDU Session and indicated by the SMF as follows: + +- When the connectivity that is not integrated with 5GS becomes available, the UE keeps the 5GS connectivity for the established PDU Session and does not perform the switching the traffic away from the PDU Session for the following application(s): + - application(s) that explicitly requests the use of the EDC functionality if the SMF indicates that EDC functionality is allowed and that EAS traffic switching control is required for the traffic of the application(s) that is mapped onto the PDU Session; + - all the applications that are mapped onto the PDU Session and of which traffic is transmitted over the PDU Session if the SMF indicates the use of EDC functionality is required for the PDU Session; + - application(s) that are mapped onto the PDU Session and of which DNS resolution is performed via EASDF if the UE does not support EDC functionality and if the SMF indicates that EAS traffic switching control is required. + +### 6.44.3 Impacts on existing entities and interfaces + +UE: + +- indicates to the SMF its capability to control application traffic switching via PCO; +- performs EAS traffic switching avoidance for the application traffic based on the information provided by SMF. + +UDM: + +- provides SMF with an indication on UE authorization for EAS traffic switching information. + +SMF: + +- determines to indicate UE that EAS traffic switching control. + +## 6.45 Solution 45 (KI#1, KI#6): Application selected PDU Session + +### 6.45.1 Description + +This solution addresses KI#6: Avoiding UE to switch away from EC PDU Session. This solution also addresses some parts of KI#1: Accessing EHE in a VPLMN when roaming. + +This solution is based on the existing functionalities in smartphones which allows a UE application to ignore the UE OS preference on preferred connectivity (3GPP vs non-integrated Wi-Fi). The UE Application will instead decide which connectivity (PDU Session) to be used regardless if for example Wi-Fi will become available or not. In current smartphones, the UE application can either use UE OS Preference for data connectivity and then the UE OS will automatically select the "best" connectivity when they become available. Alternatively, the UE Application selects a specific network interface, which corresponds to a specific PDU Session. In this case, the UE Application will always use that network interface regardless of other applications or if the UE OS connectivity preference is changing. When the UE Application has selected a specific network interface (PDU Session) then the smartphone supports the exposure of the operator provided DNS Server for that network interface. In this solution, the UE Application should discover EAS from the EASDF according to existing procedure and in addition, use the same PDU Session for all edge related connectivity, not only for the DNS Query as specified in clause 5.2 of TS 23.548 [3]§. + +NOTE: This solution is applicable when the UE Application is aware that the UE Application uses an EC service. + +## 6.45.2 Procedures + +### 6.45.2.1 Procedures for Application selected PDU Session + +![Sequence diagram illustrating the procedure for Application selected PDU Session. The diagram shows interactions between UE, EAS, (Local) DNS, PSA UPF, and SMF. Step 1: PDU session establishment & provisioning of (local) DNS Server to the UE. Step 2: UE Application select specific network interface. Step 3a: EAS Discovery (DNS Request) from UE to (Local) DNS. Step 3b: DNS Response from (Local) DNS to UE. Step 4: Application session to the EAS.](cdcbafff3cef7d54a001e3d0a4d9841e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EAS + participant DNS as (Local) DNS + participant UPF as PSA UPF + participant SMF + + Note over UE, SMF: 1 PDU session establishment & provisioning of (local) DNS Server to the UE + Note over UE, SMF: 2 UE Application select specific network interface + Note over UE, DNS: 3a EAS Discovery (DNS Request) + Note over DNS, UE: 3b DNS Response + Note over UE, EAS: 4 Application session to the EAS + +``` + +Sequence diagram illustrating the procedure for Application selected PDU Session. The diagram shows interactions between UE, EAS, (Local) DNS, PSA UPF, and SMF. Step 1: PDU session establishment & provisioning of (local) DNS Server to the UE. Step 2: UE Application select specific network interface. Step 3a: EAS Discovery (DNS Request) from UE to (Local) DNS. Step 3b: DNS Response from (Local) DNS to UE. Step 4: Application session to the EAS. + +**Figure 6.45.2-1: Procedure for Application selected PDU Session** + +1. Existing PDU Session establishment procedure according to step 1 in clause 6.2.3.2.2 of TS 23.548 [3] where the SMF indicates to the UE that this PDU Session is to be used for the EDC functionality. +2. The UE Application selects the appropriate network interface for all edge related communication to be used as long as it is available. +3. The UE Application uses the selected network interface for the EAS Discovery and Re-discovery as specified in clause 6.2.4 of TS 23.548 [3]. +4. The UE application uses the selected network interface for all communication to the EAS. + +## 6.45.3 Impacts on services, entities and interfaces + +UE: + +- The UE Application is expected to select a specific network interface for all edge related communications. + +## 6.46 Solution 46 (KI#6): Avoid UE switching on-going EC traffic away from 3GPP access + +### 6.46.1 Description + +As described in clause 5.6.2, the existing edge computing enablers cannot be used if the UE switches to an access that is not integrated with 5GS or does not provide the expected characteristics. The on-going EC traffic in a PDU Session may suffer an interruption or a bad user experience due to long UP path. This solution avoids UE switching the on-going EC traffic away from 3GPP access. + +NOTE: This solution applies to options A and B as described in TS 23.548 [3]. + +### 6.46.2 Procedure + +Figure 6.46.2-1 shows the call flow of avoiding UE switching on-going EC traffic away from 3GPP access. + +![Sequence diagram illustrating the procedure to avoid UE switching EC traffic away. The diagram shows five lifelines: UE, RAN, AMF, SMF, and EASDF. The sequence starts with a '1. PDU Session Establishment procedure' spanning all entities. Then, a dashed arrow labeled '2. DNS Query (FQDN)' goes from the UE to the EASDF. A solid arrow labeled '3. Neasdf_DNSContext_Notify Request' goes from the EASDF to the SMF. A box labeled '4. SMF determines the FQDN is for EC service, the SMF initiates PDU Session Modification procedure' is shown. Finally, a solid arrow labeled '5. PDU Session Modification Command (indicator: indicates UE avoiding switching the on-going EC traffic away from 3GPP access)' goes from the SMF to the UE.](649426750a89fa0e5d7c1736d5cf72c6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant SMF + participant EASDF + Note over UE, RAN, AMF, SMF, EASDF: 1. PDU Session Establishment procedure + UE-->>EASDF: 2. DNS Query (FQDN) + EASDF->>SMF: 3. Neasdf_DNSContext_Notify Request + Note right of SMF: 4. SMF determines the FQDN is for EC service, the SMF initiates PDU Session Modification procedure + SMF->>UE: 5. PDU Session Modification Command (indicator: indicates UE avoiding switching the on-going EC traffic away from 3GPP access) + +``` + +Sequence diagram illustrating the procedure to avoid UE switching EC traffic away. The diagram shows five lifelines: UE, RAN, AMF, SMF, and EASDF. The sequence starts with a '1. PDU Session Establishment procedure' spanning all entities. Then, a dashed arrow labeled '2. DNS Query (FQDN)' goes from the UE to the EASDF. A solid arrow labeled '3. Neasdf\_DNSContext\_Notify Request' goes from the EASDF to the SMF. A box labeled '4. SMF determines the FQDN is for EC service, the SMF initiates PDU Session Modification procedure' is shown. Finally, a solid arrow labeled '5. PDU Session Modification Command (indicator: indicates UE avoiding switching the on-going EC traffic away from 3GPP access)' goes from the SMF to the UE. + +**Figure 6.46.2-1: Avoid UE switching EC traffic away** + +1. UE establishes a PDU Session as defined in clause 4.3.2.2.1 of TS 23.502 [9]. +2. UE sends DNS query including FQDN to EASDF. +3. EASDF reports the FQDN to the SMF. +4. The SMF determines the FQDN corresponds to EC service based on EAS deployment information as described in clause 6.2.3.4 of TS 23.548 [3]. The SMF initiates PDU Session Modification procedure. +5. The SMF sends PDU Session Modification Command including an indicator that it requests the UE to avoid switching traffic corresponding to the FQDN away from the 3GPP access. + +Based on the received indicator, the UE shall avoid switching away the on-going traffic corresponding to the FQDN away from the 3GPP access even though non-3GPP access is available and has a higher priority than 3GPP access. + +### 6.46.3 Impacts on services, entities and interfaces + +SMF: + +- sends an indicator to UE by initiating PDU Session Modification procedure. + +UE: + +- avoids switching on-going EC traffic corresponding to the FQDN in DNS query away from the 3GPP access. + +## 6.47 Solution 47 (KI#6): Avoiding Switch Away Based on an SMF Indication + +### 6.47.1 Description + +#### 6.47.1.1 General + +This solution addresses Key Issue #6 for the cases where the Distributed Anchor Point, Session Breakout, and Multiple PDU Session connectivity models are used. + +The premise of the solution is that the SMF is aware of whether the PDU Session uses a PSA UPF in local site and the SMF can send an "edge-anchored" indication to the UE that indicates that the PDU Session uses a PSA UPF that is in a local site and also a "5GC-preference" indication that indicates that the network prefers to keep the traffic in the 5GC, or a "3GPP-access-preference" indication that indicates that the network prefers to keep the traffic on the 3GPP access. The indications may be coupled with descriptors of the impacted traffic. The UE can use the "edge-anchored" indication to notify any subscribed consumer (e.g. an application) mapped into the PDU Session about the local PSA. Also, when non-integrated connectivity becomes available for the UE, the UE can use the "5GC-preference" indication from the SMF to help determine whether to use the non-integrated connectivity for the traffic that is currently associated with a PSA UPF in a local site. + +NOTE: The user preferences that are associated with the UE should be taken into account and how this is done is not specified. For example, the user preferences may indicate that all traffic should use non-integrated connectivity when it is available. In such a scenario, this indications from the SMF would be ignored. + +#### 6.47.1.2 Procedure + +In the case when the network provides connectivity to the edge for all or part of the traffic for a given PDU Session, the SMF may include an "edge-anchored" and "5GC-preference" or "3GPP-access-preference" indications in the ePCO of the PDU Session Establishment Accept message or PDU Session Modification Command. The "edge-anchored" indication indicates to the UE that the that the PDU Session has a local PSA UPF. The "5GC-preference" indication indicates that the 5GC prefers that the traffic stays within the 5GC (e.g. because the services are only available via the 5GC). The "3GPP-access-preference" indication indicates that the network prefers to keep the traffic on the 3GPP access. + +The trigger for the SMF providing connectivity to the edge and sending the "edge-anchored" and/or "5GC-preference" indication or "3GPP-access-preference" indication in the ePCO may be: + +- A PDU Session Establishment request arriving from the UE through the AMF in a Nsmf\_PDUSession\_CreateSMContext request message, where the SMF decides to provide connectivity to the edge for all or part of this PDU Session. The indications in the ePCO are sent by the SMF in the PDU Session Establishment Accept message. +- An EAS discovery message from the UE that is triggering in the SMF (via from EASDF) a selection of a local PSA. The indications in the ePCO are sent by the SMF in a PDU Session Modification Command message. +- An AF traffic influence request via the NEF and PCF that is targeting connectivity to the edge for some traffic within an existing PDU Session (conveyed via a Npcf\_SMPolicyControl\_UpdateNotify message from the PCF). The indications in the ePCO message are sent by the SMF in a PDU Session Modification Command. + +Once the PDU Session is established, if the SMF (re)selects a PSA UPF for the PDU Session and there is no longer any local PSA UPF for the PDU Session, then the SMF may send a PDU Session Modification Command to indicate in the ePCO that the PDU Session should no longer be considered "edge-anchored". + +Once the PDU Session is established, if none of the PSA UPF(s) are deployed in a local site and the SMF (re)selects a PSA UPF for the PDU Session and the new PSA UPF is deployed in a local site, then the SMF may send a PDU Session Modification Command to the UE and indicate in the ePCO that the PDU Session should now be considered "edge-anchored". The SMF may also send the "5GC-preference" indication if there is a preference to keep the traffic within the 5GC. Alternatively, the SMF may also send "3GPP-access-preference" indication if there is a preference to keep the traffic on the 3GPP access. + +The UE may use the "edge-anchored" indication to notify any subscribed consumer (e.g. an application) mapped into the PDU Session about the local PSA. The consumer (application) could use this information to perform actions to maintain proper connectivity to edge computing resources, such as keeping the 3GPP access active, monitoring non-3GPP access performance and taking traffic routing decisions. + +When the SMF has information about the impacted traffic or applications, e.g. it has configured a branching point UPF or an uplink classifier UPF for the PDU Session such that only some traffic is routed towards a PSA UPF in a local site, then the "edge-anchored" and "5GC-preference" or "3GPP-access-preference" indications may be sent to the UE in the ePCO with the Flow Descriptor(s) (e.g. Packet Filters derived from the PDR(s) that were sent to the branching point UPF or uplink classifier UPF to be used to detect which traffic should be forwarded to the local site. The UE may use the Flow Descriptor(s) to determine which traffic from the PDU Session is associated with a PSA that is in a local site and may use this to notify the specific applications. + +In some cases, AF may become aware of the alternate connectivity options for a UE and determines that a connectivity through 5GS is optimal. AF may request 5GS to provide the traffic guidance to the UE through a policy control update procedure. The SMF may decide to send the "edge-anchored" and "5GC-preference" or "3GPP-access-preference" indication once the traffic corresponding to the SDF is detected based on this policy setting requested by the AF. If the AF determines that an alternate connectivity is better, it may request 5GS to stop providing traffic switching guidance to the UE. + +When connectivity outside of 5GC becomes available for the UE, the UE may use the "5GC-preference" or "3GPP-access-preference" indication and any associated Flow Descriptor(s) to decide if the traffic that is currently associated with a PDU Session should be transferred to connectivity outside of 5GC. + +NOTE 1: How the "edge anchored" and "5GC-preference" or "3GPP-access-preference" indications interact with user preferences to influence the UE's decision to use connectivity outside of 5GC is out of scope. + +NOTE 2: The SMF does not send an "edge-anchored" indication every time there is branching point UPF or an uplink classifier UPF for the PDU Session; the SMF only sends the "edge-anchored" indication when the branching point UPF or uplink classifier UPF is being used to access edge computing services. The SMF knows based on configuration (e.g. per DNAI) whether a branching point UPF or an uplink classifier UPF is being used to access edge computing services. + +## 6.47.2 Impacts on services, entities and interfaces + +SMF: + +- sends the "edge-anchored" and "5GC-preference" or "3GPP-access-preference" indications and associated Flow Descriptor(s) in the ePCO of the PDU Session Establishment Accept and PDU Session Modification Command messages. + +UE: + +- receives the "edge-anchored" and "5GC-preference" or "3GPP-access-preference" indications and associated Flow Descriptor(s) in the ePCO of the PDU Session Establishment Accept and PDU Session Modification Command messages and provides functionality to notify relevant applications to consider avoiding connectivity to non-integrated access. + +PCF: + +- evaluates and provides to SMF the policy configured by the AF to generate traffic switching guidance indications. + +NEF: + +- provides interface to an AF to update the policy for edge traffic switching. + +## 6.48 Solution 48 (KI#6): Avoiding Switch Away Based on an Indication in the URSP + +### 6.48.1 Description + +#### 6.48.1.1 General + +This solution addresses Key Issue #6 for the cases where URSP Rules are used, and it is known that certain DNN/S-NSSAI combinations will use PSA UPFs that are in a local site. + +The premise of the solution is that an indication may be added to the URSP Rules to indicate that any PDU Session that is associated with an RSD may be using a PSA UPF that is in a local site. When non-integrated connectivity becomes available for the UE, the UE may use the indication to help determine whether to use the non-integrated connectivity for the traffic that is currently associated with the PDU Session. + +NOTE: The user preferences that are associated with the UE should be taken into account and how this is done is not specified. For example, the user preferences may indicate that all traffic should use non-integrated connectivity when it is available. In such a scenario, this indication in the RSD would be ignored. + +#### 6.48.1.2 Procedure + +The Route Selection Descriptor of a URSP Rule may include an "edge-anchored" indication. The UE may consider any PDU Session that is established with the RSD to be "edge-anchored". Whether the PCF includes the "edge-anchored" indication in an RSD, may be based on configuration (e.g. OAM). For example, the PCF may be configured to know that certain DNN / S-NSSAI combinations should be considered to be "edge-anchored". + +NOTE 1: This solution assumes that the inclusion of the "edge-anchored" indication in the RSD indicates that the DNN / S-NSSAI combination should always be considered to be "edge-anchored". + +When connectivity outside of 5GS becomes available for the UE, the UE may use "edge-anchored" indication to decide if the traffic that is currently associated with a PDU Session should be transferred to connectivity outside of 5GS. + +NOTE 2: How the "edge-anchored" indication influences the UE's decision to use connectivity outside of 5GS is out of scope. + +### 6.48.2 Impacts on services, entities and interfaces + +PCF: + +- may include the "edge-anchored" indication in RSD(s) of URSP Rules. + +UE: + +- receives the "edge-anchored" indication in RSD(s) of URSP Rules. + +## 6.49 Solution 49 (KI#6): URSP based solution to avoid UE to switch away from Edge PDU Session + +### 6.49.1 Introduction + +This solution enables UE to avoid switching the EC traffic away from the EC PDU Session and 5GS altogether, for example due to connectivity to non-integrated Wi-Fi). In particular it addresses below identified problems: + +- how to determine what traffic is using the 5G System to access edge computing resources, and specifically in what granularity the traffic can be identified (e.g. Flow and/or PDU Session); +- what actions might be taken when some application traffic is currently using the 5G System to access edge computing resources and connectivity outside of 5GS becomes available. + +## 6.49.2 Functional Description + +The following are the main principles of the solution: + +- Providing URSP rules to the UE with extended Route Selection Descriptor to indicate EC traffic to the local part of the DN i.e. RSD is extended with an EC tag indicating Edge computing offload to local DN. +- The PCF for a UE triggers an update of the URSP rules to the UE when it is notified of an EC traffic to a local Data Network. This could be due to: + - AF, as part of Application Guidance for URSP determination as described in clause 4.15.6.10 of TS 23.502 [9], request URSP with EC tag e.g. if AF is aware of requirement due to ongoing EC traffic; + - PCF for the PDU Session subscribes to the SMF and is notified about EC traffic to the local part of the DN e.g. DNAI change or Local PSA UPF selection. Also, the PCF for a UE (i.e. the PCF that is responsible for provisioning the URSP rules to a UE) subscribes to the PCF for a PDU Session for such events. When a PCF for a UE is notified of EC traffic to a local Data Network, it may determine and trigger an update of the URSP rules to the UE. + - If the PCF for the UE and the PCF for the PDU Session are different PCFs, the PCF for the UE is informed when a SM Policy Association is established or released by subscription to the BSF. PCF for the UE may subscribe to the BSF to be notified when a PCF for the PDU Session is registered in the BSF as defined for AM policy use cases in TS 23.502 [9] clause 4.16.14. The (DNN, S-NSSAI) combinations may be configured in the PCF for the UE or retrieved from the UDR as part of the Application Data Set. If the PCF for the UE subscribed to the BSF, the BSF notifies that a PCF for the PDU Session is registered in the BSF. +- With received indication in the URSP, and considering its user preferences, the UE may accordingly decide to continue using the ongoing PDU Session for EC traffic. + +## 6.49.3 Procedure + +Figure 6.49.3-1 below shows the detailed procedure to allow PCF of the UE to be informed of EC traffic thus PCF triggering an update to URSP rule with extended Route Selection Descriptor indicating EC traffic to the local part of the DN is being performed. + +![Sequence diagram showing the procedure for PCF for a UE to subscribe to events indicating edge computing session and trigger UE Policy modification. The diagram involves four main entities: PCF for a UE, UPF, SMF, and PCF for a PDU Session. The sequence of messages is: 1. PCF for a UE sends Npcf_EventExposure_Subscribe to PCF for a PDU Session. 2. PCF for a PDU Session sends Nsmf_EventExposure_Subscribe to SMF. 3. SMF sends Nsmf_EventExposure_Notify to PCF for a PDU Session. 4. PCF for a PDU Session sends Npcf_EventExposure_Notify to PCF for a UE. 5. PCF for a UE determines to update URSP and triggers UE Policy Association Modification.](05b0f658f02a1301691b547d089c485a_img.jpg) + +``` + +sequenceDiagram + participant PCF_UE as PCF for a UE + participant UPF + participant SMF + participant PCF_PDU as PCF for a PDU Session + + Note right of SMF: Notification trigger met e.g. +established a local or Edge PDU +session + + PCF_UE->>PCF_PDU: 1. Npcf_EventExposure_Subscribe (Events indicating traffic offload) + PCF_PDU->>SMF: 2. Nsmf_EventExposure_Subscribe (Events indicating traffic offload) + SMF->>PCF_PDU: 3. Nsmf_EventExposure_Notify (Events indicating traffic offload) + PCF_PDU->>PCF_UE: 4. Npcf_EventExposure_Notify (Events indicating traffic offload) + Note left of PCF_UE: 5. Determine to update +URSP to include ongoing +traffic offload to the local +part of the DN and +provision it by triggering +UE Policy Association +Modification initiated by +the PCF as described in +23.502 clause 4.16.12.2 + +``` + +Sequence diagram showing the procedure for PCF for a UE to subscribe to events indicating edge computing session and trigger UE Policy modification. The diagram involves four main entities: PCF for a UE, UPF, SMF, and PCF for a PDU Session. The sequence of messages is: 1. PCF for a UE sends Npcf\_EventExposure\_Subscribe to PCF for a PDU Session. 2. PCF for a PDU Session sends Nsmf\_EventExposure\_Subscribe to SMF. 3. SMF sends Nsmf\_EventExposure\_Notify to PCF for a PDU Session. 4. PCF for a PDU Session sends Npcf\_EventExposure\_Notify to PCF for a UE. 5. PCF for a UE determines to update URSP and triggers UE Policy Association Modification. + +**Figure 6.49.3-1: PCF for a UE subscribes to Events that indicate edge computing session and triggers UE Policy modification** + +The Events indicating EC traffic that can be subscribed in the above figure 6.49.3-1 may be implemented as an extension of the User Plane Management Events specified in TS 23.502 [9], extended to include events that indicate that the SMF has established a local or Edge PDU Session (e.g. via selection of the PSA UPF and/or UL-CL UPF for + +EC traffic) or any of the Edge Computing connectivity models described in clause 4.3 of TS 23.548 [3], i.e. Distributed Anchor Point, Session Breakout, Multiple PDU Sessions. + +## 6.49.4 Impacts on services, entities and interfaces + +PCF: + +- subscribes to receive indication on EC traffic to local part of the DN, and accordingly updates URSP rule. + +SMF: + +- new event type in the User Plane Management event exposure. + +UE: + +- receives URSP with RSP indicating EC traffic. With received indication in the URSP, and considering its user preferences, the UE may accordingly decide to continue using the ongoing PDU Session for EC traffic. + +## 6.50 Solution 50 (KI#7): Obtain and maintain mapping table between IP address/IP range with DNAI + +### 6.50.1 Key Issue mapping + +This solution addresses Key Issue #7 with following aspects: + +- what information the AF should provide to 5GC (e.g. IP address or range thereof (i.e. IPv4 subnetwork and IPv6 prefixes), FQDN) and how it should provide it to help determine proper DNAI if the AF does not have knowledge of the DNAI information; +- whether and how the 5GC can provide a DNAI to AF to help the subsequent AF influence/request. + +### 6.50.2 Description + +When AF does not have DNAI information, based on the AF request, the 5GS should help determine proper DNAI(s) and notify the information to AF. DNAI information implies the proper UPF which should be selected for the UE's PDU Session, and the proper UPF should be located in the same or nearby area to the target EAS. Therefore, it is possible that the AF will provide AF/EAS IP address or AF/EAS IP address range to help 5GS determine the DNAI. + +When NEF gets the AF request for determine DNAI information with the AF/EAS IP address or AF/EAS IP address range, optionally with the target geographic area, DNN, S-NSSAI. The NEF can map the geographic area into TA list. The NEF may find the target SMF(s) through NRF, with using the TA list, DNN, S-NSSAI. Then, the NEF requests the SMF with the AF/EAS IP address range, optionally TA list, DNN, S-NSSAI, in order to find the suitable DNAI(s). + +The NEF may store the mapping relationship between the DNAI(s) and the AF/EAS IP address/IP address range, in order to help the subsequent AF request for DNAI determination. + +SMF is locally configured with the mapping information between the DNAI(s) and the AF/EAS IP address/IP address range, no matter whether the AF/EAS IP address/IP address range is public or private IP address. + +AF may subscribe the mapping information modification with NEF/SMF. When the configuration information (relationship between DNAI and EAS IP address/IP address range) is changed, the SMF can notify the new mapping information to NEF, and NEF forwards this notification to AF. + +### 6.50.3 Procedures + +![Sequence diagram showing the procedure for 5GS to determine the DNAI based on an AF request. The diagram involves three entities: AF, NEF, and SMF. The sequence of messages is: 1. AF sends an Nnef_EventExposure_Subscribe request to NEF; 2. NEF sends an Nsmf_EventExposure_Subscribe request to SMF; 3. SMF sends an Nsmf_EventExposure_Notify response to NEF; 4. NEF sends an Nnef_EventExposure response to AF.](0d9149a10167a487a93c349f5d848b7d_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant SMF + Note left of AF: 1. Nnef_EventExposure_Subscribe request + AF->>NEF: 1. Nnef_EventExposure_Subscribe request + Note right of NEF: 2. Nsmf_EventExposure_Subscribe request + NEF->>SMF: 2. Nsmf_EventExposure_Subscribe request + Note right of SMF: 3. Nsmf_EventExposure_Notify response + SMF->>NEF: 3. Nsmf_EventExposure_Notify response + Note left of NEF: 4. Nnef_EventExposure response + NEF->>AF: 4. Nnef_EventExposure response + +``` + +Sequence diagram showing the procedure for 5GS to determine the DNAI based on an AF request. The diagram involves three entities: AF, NEF, and SMF. The sequence of messages is: 1. AF sends an Nnef\_EventExposure\_Subscribe request to NEF; 2. NEF sends an Nsmf\_EventExposure\_Subscribe request to SMF; 3. SMF sends an Nsmf\_EventExposure\_Notify response to NEF; 4. NEF sends an Nnef\_EventExposure response to AF. + +**Figure 6.50.3-1: 5GS determines the DNAI based on AF request** + +1. AF invokes Nnef\_EventExposure service to subscribe for DNAI determination. The request includes EAS IP address or IP address range, may include geographic area. AF may also subscribe the DNAI information modification in NEF. +2. NEF finds the corresponding SMF based on the S-NSSAI, DNN, TA. Then, NEF invokes the Nsmf\_EventExposure service to get the suitable DNAI(s) based on the EAS IP address or IP address range, TA list, S-NSSAI or DNN. NEF can also subscribe the DNAI information modification in SMF. +- 3-4. SMF notifies the DNAI(s) information/the changed DNAI information (optionally with the EAS IP address or IP address range) to AF/NEF. + +### 6.50.4 Impacts on existing entities and interfaces + +NEF: + +- information exposure enhancement to support the DNAI exposure; +- capability enhancement to store the relationship between DNAI and IP address mapping. + +SMF: + +- finds the corresponding DNAI based on the EAS IP address/IP address range; +- notifies the new DNAI information, optionally with the EAS IP address or IP address range, once the mapping relationship between DNAI and the EAS IP address/IP address range changed. + +## 6.51 Solution 51 (KI#7): EDI holding the IP address to DNAI mapping + +### 6.51.1 High level description + +OAM provisions EDI either to UDR or to NEF where NEF may store it in UDR. For this purpose, EDI shall at least contain DNN and S-NSSAI and IP address range(s) per DNAI, but other EDI information may also be present. + +Furthermore, SMF can also interrogate NEF for EDI to get use this EDI information for option A when assigning a ECS options IP address. + +## 6.51.2 High level procedures + +### 6.51.2.1 Provisioning + +The provisioned EDI for this purpose contains at least DNN and S-NSSAI, and IP address range(s) (IPv4 subnetwork(s) and/or IPv6 prefix(es)). + +![Sequence diagram for provisioning of DNAI from NEF. Lifelines: UDR, NEF. 1a. EDI create/update/delete via OAM (UDR). 1b. EDI create/update/delete via OAM (NEF). 2b. Nudr_DM_Create/Update/Delete Request (NEF to UDR). 3b. Nudr_DM_Create/Update/Delete Response (UDR to NEF).](c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg) + +``` + +sequenceDiagram + participant UDR + participant NEF + Note left of UDR: 1a. EDI create/update/delete via OAM + Note right of NEF: 1b. EDI create/update/delete via OAM + NEF->>UDR: 2b. Nudr_DM_Create/Update/Delete Request + UDR-->>NEF: 3b. Nudr_DM_Create/Update/Delete Response + +``` + +Sequence diagram for provisioning of DNAI from NEF. Lifelines: UDR, NEF. 1a. EDI create/update/delete via OAM (UDR). 1b. EDI create/update/delete via OAM (NEF). 2b. Nudr\_DM\_Create/Update/Delete Request (NEF to UDR). 3b. Nudr\_DM\_Create/Update/Delete Response (UDR to NEF). + +Figure 6.51.2.1-1: Provisioning of DNAI from NEF + +- 1a EDI creating/updating/deleting through OAM procedure to UDR. +- 1b EDI creating/updating/deleting through OAM procedures to NEF. +- 2b. The NEF invokes the Nudr\_DM\_Create/Update/Delete to the UDR if it is authorized. +- 3b. The UDR stores/updates/removes the corresponding information (and responds a Nudr\_DM\_Create/Update/Delete Response to the NEF). + +### 6.51.2.2 Providing IP address to DNAI mapping + +![Sequence diagram for getting DNAI information. Lifelines: UDR, NEF, AF. 1. Nnef_IPtoDNAI_Get Request (AF to NEF). 2. NEF Handling (NEF). 3. Nudr_DM_Get Request (NEF to UDR). 4. Nudr_DM_Get Response (UDR to NEF). 5. NEF Handling (NEF). 6. Nnef_IPtoDNAI_Get Response (NEF to AF).](bc92832923e394e43c69264e7c66d919_img.jpg) + +``` + +sequenceDiagram + participant UDR + participant NEF + participant AF + AF->>NEF: 1. Nnef_IPtoDNAI_Get Request + Note right of NEF: 2. NEF Handling + NEF->>UDR: 3. Nudr_DM_Get Request + UDR-->>NEF: 4. Nudr_DM_Get Response + Note right of NEF: 5. NEF Handling + NEF->>AF: 6. Nnef_IPtoDNAI_Get Response + +``` + +Sequence diagram for getting DNAI information. Lifelines: UDR, NEF, AF. 1. Nnef\_IPtoDNAI\_Get Request (AF to NEF). 2. NEF Handling (NEF). 3. Nudr\_DM\_Get Request (NEF to UDR). 4. Nudr\_DM\_Get Response (UDR to NEF). 5. NEF Handling (NEF). 6. Nnef\_IPtoDNAI\_Get Response (NEF to AF). + +Figure 6.51.2.2-1: Getting DNAI information + +- 1 AF queries NEF for translation of IP address to DNAI using Nnef\_IPtoDNAI\_Get Request (IP address(es)). +- 2 NEF checks whether the AF is authorized to perform the request. The NEF derives DNN and S-NSSAI from the AF-Service-Identifier if not received explicitly. +- 3 NEF queries UDR for records related to the received IP address(es) using Nudr\_DM\_Get Request (DNN, S-NSSAI, IP address(es)). + +- 4 UDR responds with related records holding IP address per DNAI information Nudr\_DM\_Get Response (EDI records). +- 5 NEF formats result to an IP address(es) to DNAI mapping table. +- 6 NEF sends the result to AF Nnef\_IPtoDNAI\_Get Request (IP address(es) per DNAI). + +NOTE: NEF can cache any received result from UDR to reduce signalling load towards UDR. + +### 6.51.3 Impacts on services, entities and interfaces + +NEF: + +- new service. + +EDI: + +- FQDN not required. + +## 6.52 Solution 52 (KI#7): AF obtaining target DNAI provided by NEF + +### 6.52.1 Description + +This solution corresponds to KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI. + +The AF may provide one or more the following information set to 5GC, in order to request for target DNAI(s): + +- EHE information, including one or more of the following: + - EAS IP address/IP range: the IP address or IP range of the requested EAS; + - FQDN(s): the FQDN (list) of the requested EAS; + - (Local) DNS server information: the (L-)DNS server address for each DNAI. +- DNN(s): the DNN(s) related to the requested EAS; +- S-NSSAI(s) (optional): the S-NSSAI(s) related to the requested EAS. + +After receiving the information above, the 5GC determines and sends the DNAI to the AF by the following way: + +- NEF may determine target DNAI based on NF local configuration; +- NEF may obtain target DNAI from UDR. + +## 6.52.2 Procedure + +![Sequence diagram illustrating the procedure of AF obtaining target DNAI. The diagram shows three lifelines: UDR, NEF, and AF. The sequence of messages is: 1. AF sends 'Create of the AF request' to NEF; 2. NEF sends 'Nnef_EASDeployment_Query Request' to UDR; 3. UDR sends 'Nudr_DM_Query Request' to NEF; 4. NEF sends 'Nudr_DM_Query Response' to UDR; 5. NEF sends 'Nnef_EASDeployment_Query Response' to AF.](15b94d74577004248532b2f4fd64f535_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDR + Note right of AF: 1. Create of the AF request + AF->>NEF: 2. Nnef_EASDeployment_Query Request + NEF->>UDR: 3. Nudr_DM_Query Request + UDR-->>NEF: 4. Nudr_DM_Query Response + NEF->>AF: 5. Nnef_EASDeployment_Query Response + +``` + +Sequence diagram illustrating the procedure of AF obtaining target DNAI. The diagram shows three lifelines: UDR, NEF, and AF. The sequence of messages is: 1. AF sends 'Create of the AF request' to NEF; 2. NEF sends 'Nnef\_EASDeployment\_Query Request' to UDR; 3. UDR sends 'Nudr\_DM\_Query Request' to NEF; 4. NEF sends 'Nudr\_DM\_Query Response' to UDR; 5. NEF sends 'Nnef\_EASDeployment\_Query Response' to AF. + +**Figure 6.52.2-1: Procedure of AF obtaining target DNAI** + +- The AF has the requirement to obtain target DNAI, and creates an AF request, which may include the following information to 5GC, in order to request for target DNAI: + - EHE information, including one or more of the following: + - EAS IP address/IP range: the IP address or IP range of the requested EAS; + - FQDN(s): the FQDN (list) of the requested EAS; + - (Local) DNS server information: the (L-)DNS server address for each DNAI. + - DNN(s): the DNN(s) related to the requested EAS; + - S-NSSAI(s) (optional): the S-NSSAI(s) related to the requested EAS. +- The AF invokes Nnef\_EASDeployment\_Query Request service to send its request to the NEF. The NEF authorizes the AF request. + +The NEF may determine the target DNAI by local configuration, or obtain the DNAI from UDR, as described in steps 3-4. + +- The NEF invokes Nudr\_DM\_Query Request service to request for target DNAI, including information received in the AF request. +- The UDR sends Nudr\_DM\_Query Response to the NEF, including the target DNAI. +- The NEF sends Nnef\_EASDeployment\_Query Response to the AF, including the target DNAI. + +## 6.52.3 Impacts on services, entities and interfaces + +AF: + +- provides EHE information (described in clause 6.52.2), DNN(s), S-NSSAI(s) via invoking Nnef\_EASDeployment\_Query service. + +NEF: + +- provides target DNAI in Nnef\_EASDeployment\_Query Response; +- requests DNAI information (described in clause 6.52.2) via invoking Nudr\_DM\_Query service. + +UDR: + +- provides target DNAI in Nudr\_DM\_Query Response. + +## 6.53 Solution 53 (KI#1): EDC-based EAS discovery for HR PDU Session with Session Breakout + +### 6.53.1 High level description + +This solution is based on Solution 25 (see clause 6.25) and enables the UE to select which DNS resolver (between H-EASDF/H-DNS resolver and V-EASDF) to be used for a certain application. The solution works as follows: + +1. During the PDU Session Establishment/Modification, the H-SMF provides via ePCO the UE with both the H-EASDF/H-DNS resolver's IP address (as per Rel-17) and the V-EASDF's IP address. In addition, the H-SMF may include a preference indication indicating which one of the two DNS resolvers the HPLMN would like the UE to use. If no preference indication is included, it means that the HPLMN does not have a preference. + +NOTE 1: For backward compatibility, if the H-SMF includes only one IP address in the ePCO (i.e. the one of the H-EASDF/-HDNS resolver), then the UE behaves as per Rel-17 (see EDC functionality in TS 23.548 [3] clauses 5.2.1 and 6.2.4). In that case the H-SMF will not include in the preference indication in the ePCO. + +NOTE 2: As described in Solution 25 in clause 6.25, this assumes that the V-SMF provides the H-SMF with the IP address of the V-EASDF. The H-SMF can provide the V-SMF with the IP address of the H-EASDF/H-DNS resolver so that, if needed, it can be configured to forward potential unresolvable DNS queries. + +2. The EDC functionality in the UE, once received the two addresses, takes the optional preference indication from the HPLMN into account and, based on local logic (e.g. whether a certain application can use Edge Computing services in the VPLMN, user preferences, etc.), selects to use either the H-EASDF/H-DNS resolver (as per Rel-17) or the V-EASDF to resolve a specific DNS query. +3. Depending on the selected DNS resolver, the DNS query is sent to the HPLMN or to the VPLMN. + +### 6.53.2 Procedures + +Figure 6.53.2-1 represents a simplified signalling flow for discovering the EAS in case of HR PDU Session with Session Breakout in the VPLMN. + +![Sequence diagram illustrating EAS discovery in case of HR PDU Session with Session Breakout in the VPLMN. The diagram shows interactions between UE/EDC, V-SMF, UL CL/BP, V-EASDF, H-SMF, H-PCF, UDM, and H-EASDF/H-DNS resolver. It is divided into two main parts: A. EDC selects V-EASDF and B. EDC selects H-EASDF/H-DNS resolver.](c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg) + +The sequence diagram illustrates the EAS discovery process for an HR PDU Session with Session Breakout in the VPLMN. The participants are UE/EDC, V-SMF, UL CL/BP, V-EASDF, H-SMF, H-PCF, UDM, and H-EASDF/H-DNS resolver. + +**Sequence of Events:** + +- 0. UE Registration:** The UE registers to the network and the AMF in the V-PLMN receives an "HR-SBO allowed" indication. +- 1. PDU Session Establishment request:** The UE sends a PDU Session Establishment request to the V-SMF. +- 2. Nsmf\_PDUSession\_Create Request:** The V-SMF sends a request to the H-SMF, including the V-EASDF's IP address. +- 3. Retrieve subscription and policies:** The H-SMF retrieves subscription and policies from the UDM and configures the UPF. +- 4. Neasdf\_DNSContext\_Create Request/Response:** The H-SMF sends a request to the H-EASDF/H-DNS resolver, which responds. +- 5. Nsmf\_PDUSession\_Create Response:** The H-SMF sends a response to the V-SMF, including the ePCO with the H-EASDF/H-DNS resolver's address and the V-EASDF's address and preference. +- 6. Insert UL CL/BP and local PSA:** The V-SMF sends a request to the UL CL/BP to insert the UL CL/BP and local PSA. +- 7. Neasdf\_DNSContext\_Create Request/Response:** The V-SMF sends a request to the V-EASDF, which responds. +- 8. PDU Session Establishment Accept:** The V-SMF sends an accept message to the UE, including the ePCO with the H-EASDF/H-DNS resolver's address and the V-EASDF's address and preference. +- 9A. EDC selects V-EASDF:** Based on HPLMN's preference and local logic, the EDC selects the V-EASDF. +- 10A. DNS Query:** The EDC sends a DNS query to the V-EASDF. +- 11A. Steps 8-18 from TS 23.548, clause 6.2.3.2.2:** The V-EASDF performs optional insertion of UL CL and L-PSA. +- 12A. DNS Response:** The V-EASDF sends a DNS response to the EDC. +- 9B. EDC selects H-EASDF/H-DNS resolver:** Based on HPLMN's preference and local logic, the EDC selects the H-EASDF/H-DNS resolver. +- 10B. DNS Query:** The EDC sends a DNS query to the H-EASDF/H-DNS resolver. +- 11B. Steps 8-18 from TS 23.548, clause 6.2.3.2.2:** The H-EASDF/H-DNS resolver performs steps 8-18 from TS 23.548, clause 6.2.3.2.2, with no UL-CL/L-PSA insertion needed. +- 12B. DNS Response:** The H-EASDF/H-DNS resolver sends a DNS response to the EDC. + +Sequence diagram illustrating EAS discovery in case of HR PDU Session with Session Breakout in the VPLMN. The diagram shows interactions between UE/EDC, V-SMF, UL CL/BP, V-EASDF, H-SMF, H-PCF, UDM, and H-EASDF/H-DNS resolver. It is divided into two main parts: A. EDC selects V-EASDF and B. EDC selects H-EASDF/H-DNS resolver. + +**Figure 6.53.2-1: EAS discovery in in case of HR PDU Session with Session Breakout in the VPLMN** + +0. The UE registers to the network and the AMF in the V-PLMN receives an "HR-SBO allowed" indication. + +1-2. At PDU Session establishment request, the V-PLMN CN decides to establish a Session Breakout for the HR PDU Session. This is possible because the H-PLMN previously sent the "HR-SBO allowed" indication. The V-SMF sends to the H-SMF the address of the V-EASDF. + +NOTE 1: If the V-SMF does not include the V-EASDF's IP address in step 2, it means that the V-PLMN does not want to establish a Session Breakout for the HR PDU session and the following steps do not apply. + +3-4. The H-SMF retrieves the subscription/policy information from the UDM and create the DNS context in the H-EASDF. + +5. The H-SMF sends Nsmf\_PDUSession\_Create Response to the V-SMF. H-SMF provides H-EASDF reachability/IP address to VPLMN. The DNS server information in the ePCO includes both the: + +- H-EASDF/H-DNS resolver's IP address; and +- V-EASDF's IP address. + +The H-SMF may include in the ePCO an indication of which DNS resolver the HPLMN prefers the UE to use for resolving the DNS query. If no preference indication is included in the ePCO, it means that the HPLMN has no preference. The preference indication may be: + +- preference to use the H-EASDF/H-DNS resolver, +- preference to use the V-EASDF. + +NOTE 2: For backward compatibility, if the H-SMF includes only one IP address in the ePCO (i.e. the one of the H-EASDF/-HDNS resolver), then the UE behaves as per Rel-17 (see EDC functionality in TS 23.548 [3] clauses 5.2.1 and 6.2.4). In that case the H-SMF will not include in the preference indication in the ePCO. + +6-8. The V-SMF inserts the UL-CL/BP and local PSA, creates the DNS context in the V-EASDF and forwards the PDU Session Establishment Accept message to the UE including the addresses of both V- and H-EASDF and the preference indication from the H-PLMN. + +#### Option A + +9A. The EDC functionality in the UE takes the optional preference indication from the H-SMF into account and, based on local logic, it selects to use the V-EASDF as resolver for the DNS queries. + +10A. The UE sends the DNS query to the V-EASDF. + +11.A The DNS query triggers steps 8-18 of TS 23.548 [3] clause 6.2.3.2.2 executed in the in V-PLMN. If UL-CL/local PSA have been inserted in step 6, then it is not executed now. + +12.A The V-EASDF resolves the DNS query and sends the DNS response to the UE. + +#### Option B + +9B. The EDC functionality in the UE takes the optional preference indication from the H-SMF into account and, based on local logic, it selects to use the H-EASDF/H-DNS resolver (i.e. the address indicated as per Rel-17) as resolver for the DNS queries. + +10B. The UE sends the DNS query to the H-EASDF/H-DNS resolver. + +11B. The DNS query triggers steps 8-18 of TS 23.548 [3] clause 6.2.3.2.2 executed in the in H-PLMN. + +12B. The H-EASDF/H-DNS resolver resolves the DNS query and sends the DNS response to the UE. + +### 6.53.3 Impacts on services, entities and interfaces + +#### H-SMF: + +- sends authorization for "HR-LBO" to V-EASDF; +- sends H-EASDF/H-DNS resolver's IP address to V-SMF to configure the V-EASDF, if needed; +- provides to the UE address of H-EASDF/H-DNS Resolver and of V-EASDF (via ePCO); +- optionally provides to the UE preference on which address to use for DNS resolution (via ePCO). + +#### V-SMF: + +- indicates support for EC and providing V-EASDF IP address to H-SMF; +- supports interaction with V-EASDF using Neasdf interface. + +#### UE: + +- indicates capability to CN; +- receives in ePCO two IP addresses and preference indication; +- considers precedence indication when selecting IP address for DNS resolution. + +## 6.54 Solution 54 (KI#4): PCF controlling common DNAI + +### 6.54.1 Description + +This solution addresses KI#4. The solution addresses how 5GC can select a common DNAI for a set of UEs. + +It is assumed that the AF/EASs solves the issue with a common EAS for the set of UEs. + +The set of UEs is identified by the AF by the external group ID. It is assumed that the AF creates the UE set (group) by e.g. as per solution 14, in clause 6.14. + +### 6.54.2 Procedure + +The AF will request a common DNAI from 5GC in AF influence on routing by indicating correlation of traffic for a group of UEs. The group is identified by the External Group ID, which is translated by 5GC (UDM via NEF) to an Internal Group ID. + +The request for influencing traffic ends up in PCF, via UDR, see TS 23.502 [9] clause 4.3.6.2. Once PCF has received the request for the group of UEs, it will need to send PCC rules to the concerned PDU sessions. PCF starts with sending the PCC rule via Npcf\_SMPolicyControl\_UpdateNotify including indication of traffic correlation and the related Internal Group ID to the SMF having most of the PDU Sessions that should be correlated. SMF determines the common DNAI for the Internal Group and responds with the selected DNAI to the PCF. PCF then sends Npcf\_SMPolicyControl\_UpdateNotify with indication of traffic correlation, the related Internal Group and selected DNAI to the rest of the PDU Sessions for the UEs identified by the Internal Group ID. + +### 6.54.3 Impacts on Existing Nodes and Functionality + +SMF: + +- selects common DNAI, gives it to PCF, uses selected DNAI when ordered from PCF. + +PCF: + +- selects the SMF with most PDU Sessions for the concerned group of UEs, receives and sends selected DNAI. + +## 6.55 Solution 55 (KI#5): Access the shared EAS via N9 tunnel + +### 6.55.1 Description + +As indicated in LS S2-2203633 [20], the 5GAA has requirements to allow a PLMN to use EHE resources shared by another MNO appropriately, i.e. allow a UE in PLMN B to access efficiently the EAS in PLMN A located in close proximity and route the UE traffic to the identified EAS. + +As some of the MNOs do not have local edge resources, in order to consume the edge service from other PLMN, the issues below should be resolved: + +- how can the UE in PLMN B discover the EAS deployed in PLMN A by a 3GPP-defined mechanism; +- after having determined the EAS IP address deployed in PLMN A, how to determine the target DNAI. The EAS deployed in PLMN A may refer to the target DNAI defined in PLMN A, and the SMF in PLMN B cannot directly determine the target DNAI; +- how to select the UPF in PLMN A. In order to access the EAS deployed in PLMN A, the PLMN B where the UE is located should trigger the UPF selection in PLMN A and configure the N4 rules and N9 tunnel information to UPF in PLMN A. This procedure refers to the interoperability across PLMNs. + +## 6.55.2 Procedure + +### 6.55.2.1 Determine target DNAI in PLMN A according to EAS IP address + +As the EAS shared by PLMN A can be accessed via N9 tunnel by UE in PLMN B, the target DNAI related to EAS IP address should be determined. The DNAI is used or defined per PLMN, and as the EAS is deployed in another PLMN, the SMF in PLMN B cannot directly determine the target DNAI in PLMN A. + +Some information should be provided by PLMN A to assist SMF in PLMN B to determine the target DNAI in PLMN A. The AF in PLMN A can provide such information to AF in PLMN B, which is the application layer procedure. The AF in PLMN B reuses the EDI procedure. + +There exists a relationship between the EAS IP address(range)/FQDN and target DNAI in PLMN A. The information used to determine target DNAI in PLMN A are listed in table 6.55.2.1-1. + +**Table 6.55.2.1-1 Mapping table between target DNAI and IP range provided by AF** + +| Parameters | Description | +|------------------|-------------------------------------------------------------------| +| IP range/address | Indicates the IP range/address to be converted to the target DNAI | +| DNAI | The target DNAI is equivalent to the IP address/range | +| PLMN ID | Indicates the target DNAI supported in this PLMN | + +The procedure where AF provides the mapping table to 5GC is in Figure 6.55.2.1-1. + +![Sequence diagram showing the mapping table procedure between UDR, NEF, and AF. The steps are: 1. AF provides the mapping table between IP address/range and target DNAI in different PLMN to NEF; 2. NEF handling; 3. NEF sends Nudr_DM_Create/Update to UDR; 4. UDR sends Nudr_DM_Create/Update response to NEF; 5. NEF sends response to AF.](022d578ec5fd05303811e9e57975ab2e_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDR + Note right of AF: 1. AF provides the mapping table between IP address/range and target DNAI in different PLMN + AF->>NEF: + Note right of NEF: 2. NEF handling + NEF->>UDR: 3. Nudr_DM_Create/Update + UDR->>NEF: 4. Nudr_DM_Create/Update response + NEF->>AF: 5. response + +``` + +Sequence diagram showing the mapping table procedure between UDR, NEF, and AF. The steps are: 1. AF provides the mapping table between IP address/range and target DNAI in different PLMN to NEF; 2. NEF handling; 3. NEF sends Nudr\_DM\_Create/Update to UDR; 4. UDR sends Nudr\_DM\_Create/Update response to NEF; 5. NEF sends response to AF. + +**Figure 6.55.2.1-1: Mapping table between target DNAI in other PLMN and IP range in the AF procedure** + +1. The AF invokes the service operation to provide the mapping table between target DNAI in other PLMN and EAS IP range/address. +2. NEF checks whether the AF is authorized to perform the request, and authorised to provision the mapping table to UDR based on the operator policies. +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.55.2.2 SMF recovers or obtain the mapping table to determine the target DNAI + +After receiving the EAS IP address from EASDF, the SMF cannot determine the target DNAI, because this DNAI is referred to the other PLMN ID. So, the SMF should check the mapping table in UDR and convert the received EAS IP address to target DNAI in other PLMN, and trigger the UPF selection in other PLMN. + +![Sequence diagram showing SMF, NEF, and UDR interactions for mapping table recovery.](dbe8bef1723acb3e03e8616be4faf939_img.jpg) + +``` +sequenceDiagram + participant SMF + participant NEF + participant UDR + Note over SMF, NEF, UDR: 0. AF has already provided the mapping table between target DNAI and IP range/address + Note left of SMF: 1. SMF receives the EAS IP address from EASDF but can not determine the target DNAI + SMF->>NEF: 2. SMF subscribes the mapping table + NEF-->>SMF: 3. Response + NEF->>UDR: 4. Nudr_DM_Query/Subscribe + UDR-->>NEF: 5. Nudr_DM_Notify + NEF-->>SMF: 6. Notify the mapping table to SMF +``` + +The diagram illustrates a sequence of interactions between three network functions: SMF, NEF, and UDR. At the top, a note indicates that the AF has already provided the mapping table between target DNAI and IP range/address. The sequence begins with the SMF receiving an EAS IP address from EASDF but being unable to determine the target DNAI. The SMF then subscribes to the mapping table from the NEF. The NEF responds with a 'Response'. Next, the NEF invokes a 'Nudr\_DM\_Query/Subscribe' to the UDR. The UDR returns a 'Nudr\_DM\_Notify' to the NEF. Finally, the NEF sends a 'Notify the mapping table to SMF' message to the SMF. + +Sequence diagram showing SMF, NEF, and UDR interactions for mapping table recovery. + +**Figure 6.55.2.2-1: SMF recovers or obtain the mapping table** + +1. The SMF receives the EAS IP address from EASDF, but the SMF cannot decide the target DNAI according to EAS IP address, because this IP address corresponds to the target DNAI which is supported by another PLMN. +- 2-3. The SMF subscribes to the mapping table Change Notification from the NEF or obtains the mapping table from NEF. +- 4-5. The NEF invokes the Nudr\_DM\_Query/Subscribe to the UDR for the mapping table. +6. The NEF sends notification or Response to the SMF for the mapping table between EAS IP address/range and target DNAI. + +### 6.55.2.3 EAS discovery procedure and access the shared EAS via N9 tunnel + +The EAS deployed in PLMN A can be shared to UE in PLMN B to provide the edge services. PLMN A has already provided the mapping table between IP address/range and target DNAI in PLMN A as indicated in clause 6.55.2.1. + +![Sequence diagram of EAS discovery procedure and access the shared EAS via N9 tunnel. The diagram shows interactions between UE, SMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, EASDF, and DNS Server. It is divided into DNSContext Creation and DNSContext Update procedures.](b0f7b7a99fad9dffaf1b3dc5e4d01c86_img.jpg) + +MNO A + +``` + +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 + 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 + + Note right of SMF: 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 + + Note right of SMF: 14. Neasdf_DNSContext_Notify Request + SMF->>EASDF: 14. Neasdf_DNSContext_Notify Request + EASDF-->>SMF: 15. Neasdf_DNSContext_Notify Response + + Note left of SMF: 16. IP address and target DNAI acquired. + SMF->>UPF_ULCL_BP: 17. UL CL/BP insertion + SMF->>EASDF: 18. Neasdf_DNSContext_Update Request + EASDF-->>SMF: 19. Neasdf_DNSContext_Update Response + SMF->>UPF_ULCL_BP: 20. DNS response + UPF_ULCL_BP-->>UE: + +``` + +Sequence diagram of EAS discovery procedure and access the shared EAS via N9 tunnel. The diagram shows interactions between UE, SMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, EASDF, and DNS Server. It is divided into DNSContext Creation and DNSContext Update procedures. + +**Figure 6.55.2.3-1: EAS discovery procedure and access the shared EAS via N9 tunnel** + +0. For some of the FQDNs that can only be resolved in the PLMN B. So, the PLMN B can provide the EDI related to such FQDNs to PLMN A. +- 1-11. These procedures are the same as the procedures listed steps 1 to 13 in figure 6.2.3.2.2-1 of TS 23.548 [3] with the exception below: + - 5-6. After receiving the EDI from PLMN B, the SMF retrieves the EDI from UDR via NEF, and configures the DNS message handling rules to EASDF, to handle some of the FQDNs related to PLMN B. + - 8-11. If EASDF receives the DNS query which contains an FQDN deployed in PLMN B or PLMN B can resolve, the EASDF reports the FQDN to SMF, the SMF recovers the EDI from UDR provided by PLMN B, and SMF configures the DNS message handling rules. +12. According to the DNS handling rules, the EASDF delivers the DNS query to DNS server. This DNS message handling rules are generated by the PLMN B EDI. +13. The DNS server delivers the DNS response to EASDF in PLMN A. + +- 14-15. 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. SMF cannot decide the target DNAI according to the EAS IP address or the FQDN in the DNS response. +16. The SMF recovers or obtains the mapping table from UDR via NEF, which can be used to determine the target DNAI. The SMF uses the mapping table to decide that the EAS IP address corresponds to the target DNAI in PLMN A. +17. The SMF may perform UL-CL/BP and Local PSA selection according to the target DNAI. +- 23-25. These procedures are the same as the procedures listed in steps 17-19 in figure 6.2.3.2.2-1 of TS 23.548 [3]. + +### 6.55.3 Impacts on services, entities and interfaces + +#### SMF: + +- receives the mapping table from UDR via NEF, and transfers the EAS IP address to target DNAI; +- generates the DNS handling rules according to the EDI from PLMN B, and configures the EASDF with DNS message handling rules. + +#### UDR: + +- stores the mapping table between EAS IP address/range and target DNAI. + +#### AF: + +- provides the mapping table between EAS IP address/range and target DNAI to 5GC; +- provides the EDI from other PLMN. + +--- + +## 7 Evaluation + +### 7.1 Evaluation for KI#1: Accessing EHE in a VPLMN when roaming + +#### 7.1.1 Evaluation for scenario 1 (via LBO PDU Session) + +Solutions #6, #7, #8, #9, #10, #27, #28, and #39 all cover the scenario where the EHE is accessed via an LBO PDU Session. + +For how to establish the LBO PDU Session towards the correct S-NSSAI/DNN pair, updating the URSP rules in the UE is regarded as the general solution to establish the LBO PDU Session with proper DNN, S-NSSAI for the traffic that needs EC treatment. The generation of URSP rules that apply in the VPLMN and their provisioning to the roaming UE is part of scope of FS\_eUEPO KI#1. TR 23.700-85 [10] includes several solutions in this area, and the solutions in FS\_EDGE\_Ph2 for this topic do basically overlap with solutions in FS\_eUEPO report. + +The proposal is to leave to FS\_eUEPO Study Item the definition of the solution that guarantees that it is possible to provision the UE with URSPs that allow that for a given EC application, UE selects the correct S-NSSAI/DNN that can trigger vPLMN to establish and use a LBO PDU Session to access the VPLMN EHE. That includes scenarios where vAF sends guidance for determination of proper URSP in VPLMN. + +Solutions #6, #7, and #10 share some common points and all relate to URSP enhancements. Solution #7 extends Location Criteria, while solution #10 defines PLMN Criteria as new validity criteria. Considering PLMN is not kind of location, e.g. multiple PLMNs can cover same location, PLMN ID is recommended as a new criterion besides Location Criteria in RSD. + +In solution #6, an AF of the VPLMN contacts the NEF of the HPLMN to use the API defined in clause 4.15.6.10 of TS 23.502 [9], "Application guidance for URSP rules determination mechanisms". This allows the VPLMN to influence + +the URSP Rules to guide UE for traffic to be offloaded in the VPLMN to use a specific DNN and slice deployed in LBO mode while the rest of the traffic can use HR PDU Session(s). The H-PCF may, based on local policies, determine whether to always send the URSP rules immediately to the UE or to send these rules only when the UE is served by the corresponding serving PLMN, e.g. waiting to be triggered from a V-PCF of that PLMN in step 3 of TS 23.502 [9], clause 4.6.1. If the URSP rules are sent immediately (i.e. before the UE is being served by the VPLMN), then the new rules may trigger the UE to re-evaluate URSP rules and select DNN/S-NSSAI combinations that are not optimal. If the URSP rules are sent by the H-PCF when triggered by the V-PCF, then there will be some delay between when the UE is roaming and actually receiving policies that can be used to access the EHE. + +Instead of introducing a new "Revaluation Suggested" indication, updating to condition for UE to re-evaluate URSP rules in clause 6.6.2.3 of TS 23.503 [13] can achieve the purpose. + +Solution #7 proposes 2 changes to URSP Rules: + +- Solution #7 proposes that PLMN ID(s) can be part of Location Criteria in the Validation Criteria. This will allow the UE to be sent URSP rules that will work in the VPLMN before the UE is served by the VPLMN and prevent the UE from establishing a PDU Session with the RSD unless the UE is actually served by the VPLMN. +- Solution #7 also proposes that the RSD(s) can also optionally include a "Revaluation Suggested" indication. This indication may be included to indicate to the UE that URSP Re-evaluation should take place if the Validation Criteria is no longer met. This is needed because Rel-17 behaviour, as described in TS 23.503 [13] is that "*The Time Window and Location Criteria are not required to be checked again during the lifetime of the PDU Session.*" + +Solution #6 and Solution #7 can be paired in the sense that Solution #6 can be used to allow an AF in the VPLMN to provide the H-PCF with information that can be used to build URSP rules that include PLMN ID(s) in the Location Criteria and use the "Revaluation Suggested" indication to ensure that URSP rules are re-evaluated when appropriate. Thus, the network can send the URSP rules when they are immediately available and the UE will not attempt to establish PDU Sessions with the VPLMN DNN/S-NSSAI combinations until the UE is served by the VPLMN. + +Solution #10 is similar to Solution #7 because it also proposes that PLMN ID(s) can be part of the Validation Criteria. Since the UE only uses the Route Selection Validation Criteria to determine whether a PDU Session should be established and the Time Window and Location Criteria are not required to be checked again during the lifetime of the PDU Session, this solution would benefit from additionally including the "Revaluation Suggested" indication that is included in Solution #7. The "Revaluation Suggested" indication can be used to ensure that URSP rules are re-evaluated when the serving PLMN changes. + +Solution #8 deals specifically with V-ECS discovery when roaming. Solution #8 proposes that the SoR Transparent Container can include either: + +- an FQDN or an IP Address of a V-ECS to the UE. 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 ECS (e.g. an LBO Session); or +- a DNN/S-NSSAI combination. In this case, the DNN/S-NSSAI combination may be used to send a PDU Session Establishment Request in the VPLMN 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 TS 23.548 [3]. The EEC may then use the ECS FQDN or IP Address from the ECS Address Configuration Information. + +Solution #9 relies on the UE using a predefined FQDN to the EASDF that is shared between operators. The Global EASDF acts as a DNS server to provide the UE with either the IP address of the EASDF that the UE should use in the VPLMN or the S-NSSAI/DNN combination that the UE will use to set up a PDU Session. It is not clear how the Global EASDF obtains the information to determine that a new LBO PDU Session is needed, and extending DNS Response message for such an indication is not specified in our specification. It is unclear why URSPs do not suffice and why an alternative mechanism is needed, neither which mechanism in UE will determine which applications shall use this DNN/S-NSSAI. + +In Solution #27, the H-SMF detects that a HR PDU Session would be better served by an LBO PDU Session. This detection is based on DNS query from the UE towards an EC FQDN or an AF influence of traffic routing for the UE. When the H-SMF detects that the UE should switch to an LBO PDU Session, the H-SMF will terminate the HR PDU Session and inform the AMF that the DNN/S-NSSAI combination should trigger an LBO PDU Session when the UE attempts to re-establish the PDU Session. According to current Rel-17 specification, whether to establish a LBO PDU Session is determined by UE subscription based on DNN+S-NSSAI. Other applications using same DNN+S-NSSAI as per URSP will be forced to use the same LBO PDU Session even if they may need a HR Session to access services. + +Terminating the HR PDU Session impacts the ongoing traffic on that PDU Session, e.g. TCP connections break and QUIC connections are interrupted until the connectivity is re-established on the new LBO PDU Session. Solution #27 requires that the HPLMN ensures that there are no URSP rules in the UE conflicting with the LBO authorization for this PDU Session, e.g. no other traffic that requires HR PDU Session should be mapped to the same DNN and S-NSSAI that could be authorized for LBO. Solution #27 also allows the V-SMF to send information related to supported edge computing applications, i.e. Application IDs or FQDN ranges. + +In Solution #28, in order to support to establish the LBO PDU Session to ECS, the 5GC can support to distribute the updated URSP rules to UE. When UE has the traffic towards ECS in visited PLMN, the URSP rules with ECS configuration information can trigger an LBO PDU Session establishment or apply the traffic to LBO PDU Session. During LBO PDU Session establishment procedure, SMF selects EASDF, and sends EASDF address to UE via NAS message, and/or delivers ECS configuration information to UE in ePCO. Then UE may perform EAS discovery with the EASDF. The LBO procedure of solution #28 re-uses Rel-17 non-roaming EAS discovery procedure. + +Solution #39 deals with the case where the EAS is relocated between the VPLMN and HPLMN. When moving from the VPLMN to the HPLMN, the V-SMF determines target DNAI based on EAS information and EAS deployment information, sends an inter-PLMN relocation indicator to H-SMF, and configures the UL-CL/BP V-UPF for traffic routing towards H-PSA UPF if the destination address is the IP address of source EAS or target EAS. The same approach is taken when moving from the HPLMN to the VPLMN. + +## 7.1.2 Evaluation for scenario 2 (via HR PDU Session) + +In this clause, we evaluate the solutions addressing KI#1 scenario 2: #1, #2, #3, #4, #5, #24, #25, #26, #28 HR part and #53. + +1. Regarding the technical aspect on how to authorize the PDU Session to support local traffic routing to access an EHE in the VPLMN, there are three categories of solutions as follows: + - 1) With #2, #25 and #53, the authorization information is stored in UDM. During the UE registration procedure, the UDM sends the allowed indication to the AMF in VPLMN. + - 2) With #1 and #3, the authorization information is stored in UDM or is configured in H-SMF locally according to roaming agreement. During the PDU Session Establishment procedure, the H-SMF sends the indication to allow local traffic routing to the V-SMF. + - 3) With #4 and #5, H-PCF provides the policy to V-SMF via H-SMF. + +UDM-based approaches can be used where no dynamic PCC is deployed. The allowed indication sent to the AMF can be used to assist the AMF to select the V-SMF. + +2. Regarding the technical aspect on whether and how to support charging for the local traffic of a PDU Session that supports local traffic routing to access an EHE in the VPLMN, there are six solutions (#1, #2, #3, #4, #5 and #25) addressing VPLMN charging. + - With #1, V-UPF reports the usage and charging records to the V-SMF. V-SMF sends the charging information to V-CHF and also sends the usage records to the H-SMF. + - With #2 and #3, V-PSA collects and reports it. + - With #4 and #5, V-SMF configures the traffic routing rule and Usage Report Rule to assist traffic offload to V-EAS and usage information report from UL-CL V-UPF or BP V-UPF to H-SMF via V-SMF for offline and online charging. + - Solution #25 proposes that the V-SMF provides Usage Reporting Rules to the UL-CL/BP and local PSA to collect Usage Reports for charging in VPLMN that it conveys to H-SMF. + +Both VPLMN and HPLMN need to store charging records, it is reasonable that V-SMF sends the records to H-SMF. + +3. Regarding the technical aspect on how to support Rel-17 edge computing related procedures, such as EAS (re-) discovery, as specified in clause 6 of TS 23.548 [3], there are seven solutions (#1, #2, #3, #4, #5, #24, and #25). + - 1) Scenario 2.1: #1, #4, #5, and #25 + - #1. H-AF requests influence traffic routing and H-SMF sends local routing indication to the V-SMF. + +- #4. H-EASDF is used. The V-SMF performs selection and insertion of UL-CL/BP and local PSA based on DNAs received from H-SMF. The DNAs are determined by H-SMF based on EAS IP report from H-EASDF, which implies interaction between H-SMF and V-SMF in every DNS resolution to trigger V-SMF actions related to local UL-CL/PSA selection and configuration and unnecessary involvement of HPLMN for scenario 2.2. +- #5. The V-SMF determines the HR PDU Session for V-EHE should be activated based on the EAS information and roaming offload policy received from H-PCF via H-SMF, and configures the traffic routing rule to assist traffic offload to V-EAS. +- #25. H-SMF and Home DNS/H-EASDF may monitor, assist and validate the L-PSA selected by the V-SMF, based on H-EASDF trigger. + +#4 supports the dynamic EAS (re-)discovery by H-SMF based on interaction with EASDF. + +In #1, #5 and #25, HPLMN sends an offload policy/configuration to the V-SMF, and V-SMF performs the UL-CL and local PSA selection at EAS (re-)discovery. + +2) Scenario 2.2: #1, #2, #3, #4, #5, #24, #25, #28 HR part + +- #1. V-SMF retrieves the EAS deployment information of the VPLMN from the V-NEF and performs EAS discovery according to the EAS discovery procedure. +- #2. Based on V-EASDF trigger, the V-SMF decides the Session Breakout using EAS Deployment Information provisioned from the AF and V-SBO information provided by the H-SMF. +- #3. V-SMF uses a pre-configured list of FQDNs subject to EC services to derive a traffic routing rule and configures it to the V-UPF so that the V-UPF can route DNS queries (corresponding to FQDNs) to V-EASDF reusing IP replacement mechanism of Option D. After the V-UPF routes DNS queries (corresponding to FQDNs) to V-EASDF, the EAS discovery procedure with V-EASDF which implements the functions of EASDF refers to TS 23.548 [3]. 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. Based on EAS information received from the V-EASDF and UE location, V-SMF may perform V-ULCL and V-PSA selection and insertion. +- #4. V-SMF performs V-UL-CL/V-BP and V-local PSA selection and insertion based on UE location. The H-SMF obtains ECS option/local DNS server from V-SMF during PDU Session Establishment and send it to H-EASDF. The H-EASDF handles all DNS queries of the UE based on this ECS option/local DNS server. +- #5. Based on the received EAS information (e.g. EAS IP address) and the roaming offload policy, the V-SMF decides to insert or relocate UL-CL/BP V-UPF and PSA V-UPF for traffic offload to the V-EAS. According to the roaming offload policy and the EAS Deployment Information, the V-SMF configures DNS message handling rules to V-EASDF. +- #24. During the PDU Session establishment procedure, the V-SMF instructs the UL-CL the traffic routing rule to route the DNS Query for an FQDN (range) to a local DNS Server/Local DNS Resolver (Re-use Option D). +- #25. Dynamic EAS discovery and insertion of UL-CL and local PSA happens in the V-PLMN based on available EC application information and related policies and trigger from V-EASDF. +- #28 HR part. The HPLMN obtains EDI from VPLMN via interaction between H-NEF and V-NEF. + +V-SMF decides UL-CL and local UPF insertion based on V-EASDF notification (#1, #2, #3, #5, #25) while in #4, H-SMF determines the DNAI of VPLMN. + +V-SMF configures V-EASDF based on roaming offload policy from H-SMF and EAS deployment Information (#1, #2, #3, #5, #25). + +Solutions address how to forward DNS query: + +- use V-EASDF handling rule by the V-SMF (#2, #5, #25 opt A); +- use Option C (#1); + +- V-UPF to forward the DNS queries to local DNS server/V-EASDF or home DNS server/H-EASDF (i.e. Option D) (#3, #24, #25 Opt B); +- always use H-EASDF (#4, #28 HR part). + +In solution 53, the solution describes that the network sides provide multiple DNS server IP address to UE with the precedence. One is the DNS server in VPLMN and the other is in HPLMN. Together with the DNS server from network, the precedence of each DNS server is also provided to UE. When UE triggers the DNS query, according to the precedence, the UE selects one of the DNS servers to trigger the DNS query. + +However, this design has some problematic and unclear issue: + +- First, if the MNO has the precedence of DNS server, why does the MNO not directly indicate the DNS server to UE and instead let the UE select? + - Second, to indicate which DNS server to select is only by the preference. However, the UE still does not know the logic why the DNS server A has higher priority than DNS server B. Also, which DNS server to select is the role of MNO, not of the UE. So, it is not needed for UE to make the choice via a complex design. + - Finally, which DNS server is better to use depends on whether this FQDN in the DNS query can be resolved as an EAS IP address. This is fully internal 5GC strategy, which the UE does not understand. So, as the precedence does not have a relationship with the FQDN, and the precedence alone cannot reflect which DNS server is better to resolve the FQDN, this design does not bring much enhancement. +4. Regarding the technical aspect on how to ensure proper policy control and QoS enforcement, there are four solutions (#1, #4, #5 and #26) + +With #1, #4 and #5, regarding HPLMN policy, V-SMF receives the roaming offload policy/rules from H-PCF via H-SMF, while regarding VPLMN policy, with #26, V-SMF receives its VPLMN policy from V-PCF. + +Solution #25 proposes that in scenario 2.1, HPLMN may provide QoS policies for specific applications in the SLA, and then this will be configured in V-SMF with limitation to roamers. Alternatively, QoS rules can be conveyed to V-SMF by H-SMF during PDU Session establishment or update as specific information or as an indication to V-SMF to store the information sent to the UE in the NAS message and the QoS profile sent to gNB. In scenario 2.2, V-PCF provides local policies for V-SMF. + +It is reasonable to support both HPLMN and VPLMN policy respectively and both can co-exist. + +5. Regarding the technical aspect on potential impact on Policy and QoS control: + +The technical aspects 2 and 4 address this aspect. + +6. Regarding the technical aspect on how to configure the VPLMN ECS address to UE in roaming scenarios, one solution (#1) addresses this issue. + +With #1, H-SMF sends VPLMN ECS address stored in UDM to UE via V-SMF. + +7. Regarding the technical aspect on how to support the edge relocation in roaming scenarios, #39 (clauses 6.39.2.1 and 6.39.2.2) addresses this issue. + +It supports the AF triggered EAS relocation between different PLMNs. The AF sends PLMN ID corresponding to target EAS to the network, which assists to select SMF and UPF, and indicates SMF to configure traffic rule on UPF to access target PLMN. It is reasonable to support this scenario. + +### 7.1.3 Evaluation for ECS address delivery aspects + +For the ECS address delivery in roaming situation (including both HR and LBO), according to and following the conclusion in Rel-17, some of the issues should be discussed: + +1. When home routed, how the AF in visited network provides the ECS address to 5GC in HPLMN, and how the AF in visited network provides the ECS address to 5GC in visited PLMN when local breakout. +2. For both HR and LBO, how to recover the UE subscription data from UDM and get the ECS address. +3. How to send ECS address to UE in both HR and LBO. + +4. How to identify the ECS address to be used for UEs in different VPLMN. + +For each of the bullets, there are two categories, including home-routed situation and LBO situation. + +For bullet #1, the ECS address can be provided by 3rd party AF via parameter provisioning procedure, which is the Rel-17 conclusion. In Rel-18, the conclusion can still be followed: + +- 1a. For LBO situation, the AF in the visited PLMN provides the ECS address by parameter provisioning procedure to UDM. This principle follows the design in Rel-17. +- 1b. For HR situation, as the home PLMN should configure the ECS address to UE in roaming, the HPLMN should obtain the ECS address provided by VPLMN in advance. There are two categories: HPLMN has the knowledge of ECS address in VPLMN and HPLMN does not have the knowledge of ECS address in VPLMN: + - Category A: In this category, HPLMN has the knowledge of ECS address in VPLMN including Sol#1 and Sol#28. Sol#1 and Sol#28: The V-AF sends application related information to H-AF, which includes the ECS address. This procedure is in scope of SA6. + - Category B: In this category, HPLMN does not have the knowledge of ECS address in VPLMN including Sol#1. Sol#1: The V-AF configures the V-SMF according to the AF influence on traffic routing procedure. In this case, during the HR PDU Session establishment, the V-SMF needs to select a PCF in the VPLMN to establish the SM Policy Association. V-PCF may send the VPLMN ECS address obtained from V-AF to V-SMF. The V-SMF sends the ECS address to H-SMF during PDU Session establishment procedure. + +For bullet #2, as the ECS address is one of the UE subscription data stored in UDM, how to recover this information can follow the Rel-17 principle: + +- 2a. For LBO situation, Sol#28: When UE in LBO session, the V-SMF retrieves the UE subscription data from UDM. +- 2b. There are two categories: HPLMN has the knowledge of ECS address in VPLMN and HPLMN does not have the knowledge of ECS address in VPLMN: + - Category A: In this category, HPLMN has the knowledge of ECS address in VPLMN including Sol#1 and Sol#28. Sol#1 and Sol#28: The H-SMF retrieves the UE subscription data including ECS address from UDM. + - Category B: In this category, HPLMN does not have the knowledge of ECS address in VPLMN including Sol#1. Sol#1: The V-SMF sends the ECS address to H-SMF during PDU Session establishment procedure. The H-SMF does not recover the UE subscription data from UDM. + +For bullet #3, after receiving or obtaining the ECS address, the ECS address should be delivered to UE. For both the LBO and HR situations, there are two categories for UE receiving the ECS address: + +- 3a. In Sol#28, it follows the Rel-17 principle that the V-SMF or H-SMF sends the ECS address in ePCO to UE via DL NAS message. +- 3b. In Sol#8, the SoR transparent container can be used to provide an FQDN or an IP Address of a V-ECS. This is a new feature to be introduced in Rel-18. + +As the SoR has the specific function, the information in SoR transparent container is used for PLMN selection when UE in roaming. Certainly, the SoR is not designed or enhanced to support any general application layer connection. Also, the SoR is used for HPLMN to deliver the information that is unknown to VPLMN or that the HPLMN does not want the VPLMN to know. Certainly, the ECS address does not belong to the unknown information or the information that the HPLMN does not want VPLMN to know. At last, there is no defect of delivering ECS address in ePCO to UE to solve the situation in UE roaming. + +Based on the evaluation above, there is no need to enhance the SoR. The Rel-17 principle of delivering ECS address in ePCO via DL NAS message to UE should be reused. + +For bullet #4, as the UE can roam to different PLMNs, the ECS address should also be coordinated with the different PLMNs. For both the LBO and HR situations: + +- In Sol#28: All of the ECS configuration information above should be retrieved per VPLMN ID. The AF should also provide the ECS address that is paired to the PLMN ID to UDM, and the SMF can decide to retrieve the different ECS address when UE roaming in different PLMN. + +## 7.2 Evaluation for KI#2: Fast and efficient network exposure improvements + +Key Issue #2 is for fast and efficient network exposure improvements. Solutions #11, #12 and #13 are proposed to solve this KI. + +### Exposure information + +In solutions #11 and #12, network congestion indication/level is exposed to AF by extending GTP-U header and UPF/L-NEF exposure services, same as the exposure path used in clause 6.4 of TS 23.548 [3]. Furthermore, solution #11 proposes to expose QNC for GBR QoS Flow via this path. + +Report updating threshold as proposed in Solution#11 is provided to RAN, and optionally it may be provided to the PSA UPF, but the need and benefits are not clear for the second case, as pointed out in Note 1 in clause 6.11.1. + +In solution #12, a specific QoS flow is used to expose the above information. + +In solution #13, cell ID is exposed to AF via user plane. The current specification defined exposure of cell ID to AF as part of UE location as specified in clause 4.15.3.1 of TS 23.502 [9] is not the most optimal and efficient. + +### Subscribe service + +In solutions #11 and #13, AF uses Nnef\_AFSessionWithQoS to subscribe the above information exposed by 5GC, same as local exposure mechanism defined in TS 23.548 [3]. While in solution#12, AF uses Nnef\_EventExposure\_Subscribe to subscribe information exposed by 5GC. + +## 7.3 Evaluation for KI#3: Policies for finer granular sets of UEs + +The following solutions address Key Issue 3: + +- #29: Use of Internal Group ID and constraints in EDI; +- #30: Policies referring to "Allowed services" and/or "Subscriber categories"; +- #31: Providing traffic offload policy for a set of UEs with service information; +- #32: Offload policy for finer granular set of UEs; +- #33: AF requests offload policy for sets of UEs. + +Rules to control which PDU Sessions of which users are subject to Edge computing are carried via Nnef\_TrafficInfluence service and target the PCF. + +- Solution 30 uses "allowed services" and "subscribed services" as a means for addressing a finer granularity of UEs; +- Solution 31 adds a "service information" as a means for selecting a finer granularity of UEs; +- Solution 32 introduces "subscribed services" which is a logical combination of criteria, e.g. group1 AND group2; +- Solution 33 introduces category information to indicate which information elements (e.g. spatial validity condition, application id...) determine the collection of UEs. Logical combinations are also possible. + +Solution 31 and part of solution 30 and/or use of External/Internal group IDs should sufficiently support the Key Issue, which means that an AF can identify a finer granularity set of UEs by means of: + +- External Group ID or a list of External Group IDs; +- external representation if needed of "Subscriber categories" (e.g. gold / silver / bronze users); +- service information like application client category, or application-decided service level. This can be matched against allowed services by PCF. + +## 7.4 Evaluation for KI#4: Influencing UPF and EAS (re)location for collections of UEs + +For KI#4, the key points to address the issues include: + +1. How to define and identify a collection of UEs forming a dynamic ad-hoc group that should use the same EAS and/or same local part of DN and/or same DNAI. The dynamic ad-hoc group, agreed between the 5GC and the AF (e.g. as part of a SLA) can be managed only by AF or be synchronized by both AF and 5GC using agreed targeting information. +2. How to inform the SMF the information of the same EAS and/or same local part of DN and/or same DNAI to be used. The information of the same EAS and/or same local part of DN and/or same DNAI to be used can be determined by the AF and sent to the 5GC for maintaining and using (corresponding to AF selection of common EAS/DNAI), or can be determined by the 5GC and maintained within 5GC (corresponding to 5GC selection of common EAS/DNAI). For the AF-determined DNAI/EAS, it can be sent to the UE via application layer which is out of scope of 3GPP SA2, it can also be sent to the 5GC for the routing decisions for traffic of PDU Session and the DNS handling rule decision. + +In TS 23.548 [3], the mechanism to support "Edge Relocation Triggered by AF" is defined. The AF may invoke the AF request targeting an individual UE address procedure as described in TS 23.502 [9] clause 4.3.6.4 (the AF influence on traffic routing procedure), due to EAS relocation. + +In TS 23.548 [3] and TS 23.502 [9], the solution for "EAS (re-)discovery over Session Breakout Connectivity Model" is described. The SMF interacts with EASDF and provides the ECS option or the Local DNS server address, related to candidate DNAI(s) for that FQDN for the UE location, as part of the rules to handle DNS queries from the UE to the EASDF, the EASDF sends DNS message to the local DNS server or sends DNS message to the centralized DNS server with ECS option. The rules to handle DNS queries from the UE can be updated based on the notified DNS Query with certain FQDN, UE mobility or PSA relocation. 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 TS 23.503 [13] clause 6.4 or be preconfigured into the SMF. The EAS Deployment Information used to construct the rule can be set per group. + +Solutions of KI#4 address one or more of the following aspects: UE collection definition, 5GC selection of common EAS/DNAI, AF selection of common EAS/DNAI. + +**Table 7.4-1: Solutions addressing KI#4** + +| Solution | UE collection definition | 5GC selects common EAS/DNAI | AF selects common EAS/DNAI | +|----------------------------------------------------------------------------------|--------------------------|-----------------------------|----------------------------| +| #14: Group management | X | | | +| #15: Selection of common DNAI | | X | X | +| #16: Selecting the same EAS/DNAI for collection of UEs | X | X | X | +| #17: Application layer EAS selection for collections of UEs | | | X | +| #18: Discovery of the same EAS for collections of UEs | X | X | | +| #19: Influencing UPF and EAS (re)location for collections of UEs | X | | X | +| #34: Selecting the same EAS/DNAI for collection of UEs | X | X | | +| #35: Providing dedicated (re)location information as traffic routing information | X | | X | +| #36: Providing dedicated (re)location information as EAS Deployment information | X | | X | +| #37: (Re)location of same EAS and coordination across UEs | X | X | | + +Thus, based on the issues for KI#4 and to reuse the existing mechanism as much as possible and solve the issue for KI#4, the solutions are analysed with focus on the above three aspects. + +### Aspect 1: UE collection definition + +Solution #14 performs UE collection definition by group management. It utilizes Nnef\_ParameterProvision (or new defined) service for AF to send GPSI list and external group ID. UDM aligns the group data and UE subscription data. UDR generates internal group ID, and stores SUPI list, internal group ID and external group ID. + +If Nnef\_ParameterProvision service is used, it shall be enhanced to support dynamic UE group management, which only supports 5G VN group or MBS group management in current specification. + +Solution #19 performs UE collection definition by group management. AF uses Nnef\_ParameterProvision (or new defined) service to send group management information, including group member management parameters and group data: + +- Group member management parameters: GPSI list, external group ID; +- Group data: DNN/S-NSSAI, Group Type (i.e. ad-hoc group for gaming/platooning/etc.), EAS ID, Group Attributes (e.g. same EAS/same PSA is needed/etc.). + +NEF translates external group ID into internal group ID, and stores this information in UDM. + +Solution #16, #18 and #34 use UE list, group ID or any UE, and Spatial Validity Condition to define the UE collection of specific application, which is identified by FQDN or Application ID. + +Solution #35 and #36, the collection of UEs can be identified using explicit group management extending the 5GVN group management which is similar as that described for Solution #14 and #19. The collection of UEs can also be identified with target UEs with service information. The PCF or SMF associates the UE with the collection based on the group ID or the service information via traffic routing information or EDI, and the specific service information for each PDU session received via the procedure of Service specific parameter provisioning. + +#### **Aspect 2: 5GC selection of common EAS/DNAI** + +Solution #16 proposes that the SMF determines that UE belongs to the dynamic UE group when steps 1-9 of clause 6.2.3.2.2 of TS 23.548 [3] are performed, and the SMF obtains common EAS/DNAI of the UE collection, locally or retrieving from UDR. If the common EAS/DNAI has not been determined for UE collection, the SMF determines the common EAS/DNAI via the Rel-17 EAS discovery procedure, and synchronizes to UDR with the common EAS/DNAI. + +Solution #34 EDI is used for maintaining the common EAS/DNAI. SMF synchronizes common EAS/DNAI by updating EDI to NEF/UDR. + +Solution #37 UDM/UDR is used for maintaining the common DNAI/EAS as part of group information. The difference is, when common EAS/DNAI is synchronized, the UDM/UDR shall send notification to the SMF(s) that subscribed the group data (see solution #19, clause 6.19), including the common EAS/DNAI. + +Solution #15 introduces a new network function SCMF to manage the common DNAI. SMF may obtain the common DNAI either when PDU Session is established (pre-invoke of SCMF) or when reported DNS Query by EASDF (dynamic invoke of SCMF). The SMF sends EASDF information to build ECS option or L-DNS server address according to the common DNAI. Then rest of procedure in clause 6.2.3.2.2 of TS 23.548 [3] are performed. Solution #15 only deals with common DNAI case. + +Solution #18 assumes that the UE group is served by a single SMF. When reported DNS Query, the SMF responds to the EASDF with either the common EAS, or the same information to build ECS option or L-DNS server address as other member(s) of the dynamic UE group. + +#### **Aspect 3: AF selection of common EAS/DNAI** + +Solution #15 proposes both 5GC and AF selection ways, and only AF selection procedure is evaluated in this aspect. + +SMF selects UPF according to common DNAI obtained from SCMF, and notifies the common DNAI to AF as target DNAI via UP path change event. Then AF sends "group FQDN" corresponding to the common DNAI to UE via application layer. UE solves common EAS via DNS. If common DNAI is updated, SMF gets notified by SCMF, and the above is repeated. + +Solution #17 proposes that AF determines members of the dynamic UE group. For each group member UE, AF sends request to the SMF for candidate DNAI(s) via PCF. SMF notifies AF the candidate DNAI(s). AF selects common DNAI and common EAS according to the candidate DNAI(s) from all the SMF(s). Then AF sends the common DNAI to each SMF via AF influence traffic procedure, and sends the address of the common EAS to each UE via application layer. + +Solution #35 and #36 propose a solution to support the case that AF determines common EAS/DNAI for certain application for dynamic UE group. The common EAS/DNAI is sent to the SMF via PCC rule or EAS Deployment Information, and the SMF uses the common DNAI/EAS for the routing decisions for traffic of PDU Session and the DNS handling rule decision. In Solution #35, the common EAS/DNAI for the collection of UEs is received via traffic routing information. The PCF associates the UE accessing the application with the collection of UEs using the same DNAI/EAS, and the PCF sends the PCC rule with the common EAS/DNAI to the SMF. In Solution #36, the common EAS/DNAI for the collection of UEs is received via EAS Deployment Information, and the SMF associates the UE accessing the application with the collection of UEs using the same DNAI/EAS. + +## 7.5 Evaluation for KI#5: GSMA OPG impacts and improvements for EHE operated by separate party + +The solutions addressing Key Issue #5 can be split into two categories: + +1. solutions that enable the discovery of an EAS deployed in another PLMN than the one serving the UE, and +2. solutions that facilitate the edge relocation between PLMNs. + +### **Solutions to enable the discovery of an EAS deployed in another PLMN than the one serving the UE.** + +This category of solutions encompasses Solution #20, Solution #21, Solution #22, Solution #38 and Solution #40. All solutions assume that the involved PLMNs are part of an GSMA OP federation and/or that there is a controlled inter-PLMN IP connectivity between the PLMN serving the UE and the PLMN hosting the EAS. + +Solution #20 is based on the usage of the newly defined Global EASDF which can directly resolve the DNS query sent by the UE to discover the shared EAS (which can be deployed in any PLMN) or can first resolve the DNS query sent by the UE to discover the EASDF able to provide the IP address of the shared EAS. Both options require the UE to be configured with the Global EASDF's URL and to resolve it to obtain the Global EASDF's IP address. Because of that these two options are inconsistent with the Rel-17 EAS discovery procedure described in TS 23.548 [3] clause 6.2.3.2.2 (which, on the contrary, assumes that the EASDF's IP address is provided by the SMF via ePCO during PDU Session establishment/modification). In addition, the second option is incompatible with the Rel-17 EAS discovery because it requires the UE to obtain the EASDF's IP address by sending a DNS query to the Global EASDF, while the Rel-17 EASDF in the PLMN has no role to play. + +Solution #22 describes three alternative options: Option 0 (based on the SMF configuration to know the EAS deployment information of the EAS running on other PLMN's edge infrastructure, e.g. IP address range(s)/FQDN(s)), Option 1 (based on the usage of the Shared EASDF which stores the EDI of each EAS running in each PLMN sharing Edge Nodes) and Option 2 (which relies on inter-PLMN inter-EASDF communication to resolve the DNS Query for an EAS hosted by another PLMN). Option 2 requires storing in the NEF/UDR/SMF/EASDF an additional filtering information (PLMN ID and DNS server address/FQDN filter) for the EAS' deployed in another PLMN – such information is essential to locate the EAS during the EAS discovery procedure. Solution #22 has no impact on the UE, but, depending on the option, it affects the CN entities to different degrees. + +Solution #38 relies on the AF to provide extended EAS Deployment Information (EDI) which includes N6 traffic routing information to the PLMN hosting the EHE. After having been translated by the NEF of the original PLMN and sent to the PLMN serving the UE, the extended EDI is stored in the UDR of the PLMN serving the UE. The SMF of the serving PLMN can then use such EDI to find the EAS hosted in the other PLMN. Similar to Solution #22, this solution has no UE impacts. + +Solution #40 has a similar concept to Option 2 of Solution #22, in that it forwards the DNS query from the EASDF of the PLMN serving the UE to the EASDF of the PLMN hosting the EHE, if the former cannot find it. Differently from Solution #22 though, the inter-EASDF communication takes place via SMF and NEF. In addition, Solution #40 proposes the use of additional information (S-NSSAI, DNN, UE location and External Group ID) to allow the SMF in the PLMN hosting the EHE to find the proper EASDF. + +Solution #21 ensures that an EAS deployed by a certain operator in a VPLMN's EHE can only be discovered and accessed by the UE of that operator while roaming in local breakout to the VPLMN. To do this, the solution the AF to provide, together with the EAS Deployment Information, the PLMN ID of the EAS owner so that the SMF can match it with the UE's HPLMN ID when the EAS discovery is triggered. This solution, however, does not seem to address the ENS (Edge Node Sharing) deployment which allows OP B to deploy Edge Computing applications in the Operator A's EHE, without restricting the access to it to only OP B's UEs. + +### Solutions to enable the EAS relocation for shared EHE + +Solution #23 proposes to support the scenario of EAS relocation between EHE deployed by a source EHE provider to another EHE deployed by a target EHE provider, even in scenarios when EHEs are operated by different service providers. It needs the NRF or NEF maintains parameters for each AF, e.g. EHE domain it supports, service area, etc. Then SMF selects suitable target AF. The impact is introduced on 5GC and no impact on UE. + +Solution #39 proposes to support the scenario EAS relocation between EHEs deployed in different PLMNs. The AF sends corresponding PLMN ID to network to indicate the EAS should be relocated to the target PLMN, and based on retrieval of PLMN ID, SMF selects UPF to access target EAS via controlled IP network. The impact is introduced on 5GC and no impact on UE. + +## 7.6 Evaluation for KI#6: Avoiding UE to switch away from EC PDU Session + +There are nine solutions provided for this key issue, Solutions #41 to #49. + +Clause 5.6.2 lists some problematic scenarios that should be covered: + +- non-integrated access, where re-connecting to the 5GS is not possible, e.g. because lack of UE support or an N3IWF could not be discovered or connected to and these Edge Computing enablers can only be reached via the 5GS; +- re-connecting to the 5GS is possible but results in long UP paths because of e.g. a centralized N3IWF; +- session breakout scenarios where an UL-CL and L-PSA is used to obtain EC connectivity and switching to an access that is not integrated with 5GS would therefore break the EC connectivity. + +In the first case, connecting to non-integrated WIFI access should be avoided if the 5GS applies Edge Computing enablers. This could be achieved, as different solutions propose, e.g. by an indication from the 5GC to the UE to avoid switching away to non-integrated WIFI access. + +Whether the application still gets access to application server via non-integrated access can depend also on factors outside of 5GC control, such as the IP latency from the WIFI POP to the EHE, the EHE connectivity configuration or transport protocol used between the UE applications and local application server (e.g. QUIC can provide service continuity during access change, but TCP cannot). It may depend on application functionality (e.g. RTT measurements over the different accesses) whether the application could leverage on using non-integrated WIFI. The application may, however, benefit from an indication whether the 5GC currently applies EC treatment: this may trigger the application logic to control its traffic over different accesses, e.g. based on latency monitoring as proposed in Solution #42. + +In the second and third cases above, even (re-)connecting to 5GC via non-3GPP access should be avoided. In these cases, the 5GC has the information to decide whether this is needed or not so the 5GS may again send an indication to the UE to avoid switching to non-3GPP access. + +There are different alternatives proposed to send an indication from 5GS to avoid switching away to non-integrated WIFI access: + +1. via existing URSP rules: Solution #41 proposes to apply the existing URSP rules to control non-seamless WIFI offload. As stated in clause 6.1.2.2.1 of TS 23.503 [13]: *"If the UE has an URSP rule (except the URSP rule with the "match all" Traffic descriptor) that matches the application as defined in clause 6.6.2.3, the UE shall perform the association of the application to the corresponding PDU Session or to Non-Seamless Offload or ProSe Layer-3 UE-to-Network Relay Offload according to this rule"*. That is, if 5GC defines policy rules for non-seamless offload for some traffic in the RSD, then the UE should apply these rules for that traffic in the corresponding PDU Session. For session breakout, if an update of traffic descriptors in URSP rules is required, the resulting rule will possibly not be acted upon by the UE immediately. The ATSSS rules can be configured for more refined control of traffic steering if the conflicting non-3GPP access is integrated. The solution can achieve this outcome without any impacts to the specifications. However, in this solution, the UE is not made aware whether any of the edge enablers are configured for the 3GPP access. +2. via a new attribute in URSP rules: Solution #48 proposes an "edge-anchored" indication in URSP RSD(s). The principle of Solution #48 is that an indication may be added to the URSP Rules to indicate that any PDU Session that is associated with the RSD is possibly using a PSA UPF that is in a local site. Solution #48 only applies to the scenario where it is known that a PDU Session that is associated with certain Traffic Descriptors or DNN/S- + +NSSAI combinations will always access edge computing resources that cannot be accessed if the UE switches to an access that is not integrated with the 5GS. The solution makes no reference whether the URSP can be updated based on the AF guidance at run time. Solution #49 proposes to dynamically indicate "ongoing traffic offload" in the RSD. This is based on AF provisioning as part of Application Guidance for URSP determination as described in clause 4.15.6.10 of TS 23.502 [9], and/or based on PCF decision due to an offloading of EC traffic to a local Data Network. With received indication in the URSP, and considering its user preferences, the UE may accordingly decide to continue using the ongoing PDU Session for EC traffic. + +3. as a new indication via PCO: the principle of Solution #47 is that the SMF is aware of whether the PDU Session uses a PSA UPF in local site and the SMF can send an "edge-anchored" indication to the UE that indicates that the PDU Session uses a PSA UPF that is in a local site and also a "5GC-preference" indication that indicates that the network prefers to keep the traffic in the 5GC. The indications can be per Flow Descriptor(s). +4. as a new indication coupled to EDC attributes: Solution #44 proposes that the ability for network to control UE's traffic offloading decision is dependent on UE capability and UE's subscription. The UE may indicate to the SMF its capability to support the EDC functionality and to control application traffic switching via ePCO. If the UE subscription information includes EAS traffic switching information, the SMF indicates to UE that EAS traffic switching control is required. The solution proposes this capability to be linked to the EDC functionality, but EDC which is handling DNS queries from the UE will possibly not have visibility of the actual application traffic and cannot enforce traffic routing rules. + +NOTE 1: Solution #44 is similar to Solution #47. Solution#46 also proposes indication to the UE that the PDU Session is using edge computing functionality of the network, but it is not explicitly stated how this indication is conveyed. The UE decision of traffic switching cannot be enforced as stated in the solution since it may happen in upper layers. + +There are two potential alternatives to send the indication to UE whether the 5GC currently applies EC treatment for some traffic: + +1. as a new indication via PCO. Solution#47 proposes an "Edge-anchored" indication; +2. via a new attribute in URSP rules. See point 2 above. + +Providing an indication to the UE to avoid switching to non-3GPP access has been proposed in two solutions: + +- Solution#41 proposes to apply the existing URSP rules for this, i.e. setting the Access Type Preference to "3GPP" for the given EC traffic. Besides, for MA PDU sessions, it proposes to use the ATSSS rules to avoid going to non-3GPP access. +- Solution #47 proposes that this type of indication could be also sent via PCO. This could be needed in the cases when a dynamic update needed for an existing PDU session where URSP rules would be difficult to update. + +Other solutions include: + +- Solution#42 proposes a new "WLAN Offload Guidance" indication in the Route Selection Descriptor to indicate to the UE that offloading edge computing traffic matching the Traffic Descriptor for this URSP rule to integrated non-3GPP access is conditional to the evaluation of conditions informed by the network. The UE may then perform RTT measurements on the non-3GPP path and use the measurements to help decide if integrated non-3GPP access should be used. It is not clear what the benefit of this approach is compared to when the application measures RTT directly to EAS over the different accesses. This solution requires that Application Server also supports the best path selection in the UE by configuring performance measurement parameters to compute RTT over 3GPP and non-3GPP paths. +- Solution#43 provides two approaches: + 1. SMF rejects the PDU Session establishment from non-3GPP access if it is handling EC traffic. This reuses the handover procedure defined in clause 4.9.2 of TS 23.502 [9]. If the UE uses the PDU Session ID of 3GPP access to trigger the PDU Session establishment in non-3GPP, the SMF rejects this establishment and the EC-session is still kept in 3GPP access. This requires UE support, i.e. keeping the old PDU Session on the 3GPP access while attempting to establish a PDU Session on the non-3GPP access, which likely requires multi PDU Session capable UEs. The SMF can know whether this session is EC or not according to the former notification from EASDF about the FQDN and EAS IP address. The SMF which decides the rejection and the SMF involved in session creation during the DNS related procedure are the same. This requires a new logic in the SMF. + +2. The UE decides to perform a PDU Session handover according to NWDAF analytics. This does not require the UE registration to non-3GPP, only if there is another device available that the analytics can rely on. The analytics can either the historic/real-time analytics or the prediction but the real-time analytics is what could provide sufficient reliability. The analytics can indicate to the UE or 5GC which kind of access is better for the EAS. This will avoid that the EC-traffic is directly kept unconditionally on 5GS, as the 5GS might have low coverage or poor signal. Performance comparison between the non-3GPP access and 5GS is necessary. +- Solution#45 proposes an application-based solution to select/bind to a proper network interface for communication. This solution does not require SA2 standardization. Note that it assumes that the application is aware that it uses an EC service, which also calls for an indication to the UE (conveyed by the UE to the Application) that the 5GC currently applies EC treatment. It should also be noted that for operator deployed services, application clients can be designed to use this mechanism. + +## 7.7 Evaluation for KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI + +There are 3 solutions (solutions #50, #51 and #52) addressing KI#7: "Obtain and maintain mapping table between IP address/IP ranges with DNAI". + +The main differences among these solutions are two aspects: + +1. which NF determines DNAI, +2. what parameter(s) AF provides to NEF. + +For aspect 1: + +- Solution #50 proposes that SMF is configured with mapping information between EAS IP address(es)/IP range(s) and DNAI(s), and determine DNAI. NEF can cache the mapping information. +- Solution #51 proposes that UDR/NEF stores EDI. NEF determine target DNAI based on EAS IP address in AF queries. +- Solution #52 proposes that NEF determines target DNAI based on NF local configuration. NEF may obtain target DNAI from UDR. + +For aspect 2: + +- Solution #50: (mandatory) EAS IP address/IP range, (optional) DNN, S-NSSAI, geographical area. +- Solution #51: (mandatory) EAS IP address/IP range, (optional) DNN, S-NSSAI. +- Solution #52: (mandatory) EHE information (i.e. at least one of EAS IP address/IP range, FQDN(s), (local) DNS server address), (optional) DNN, S-NSSAI. + +### Evaluation of the solutions + +For aspect 1, on which NF determines DNAI: + +- Since mapping relationship between IP address/FQDN and DNAI is kind of network deployment information and independent from session management, SMF is not the proper NF for the determination of DNAI. AF can request such a map without any PDU Session established beforehand. Therefore, NEF is more suitable for such a mapping service. + +For aspect 2, on what parameter(s) AF provide to NEF: + +- According to the description of the key issue, IP address/IP range or FQDN may be provided by AF to obtain DNAI. DNN, S-NSSAI, and geographical area can be used optionally to obtain corresponding DNAI. + +## 8 Conclusions + +### 8.1 Conclusion for KI#1: Accessing EHE in a VPLMN when roaming + +#### 8.1.1 Conclusion for scenario 1 (via LBO PDU Session) + +To support the establishment of an LBO PDU Session towards the correct DNN/S-NSSAI to access an EHE in the VPLMN, URSP based solution is preferred. Key Issue 1 of TR 23.700-85 [10] is studying URSP rule provisioning and updating procedures in roaming scenarios. Therefore, the conclusions of Key Issue 1 of TR 23.700-85 [10] will take in account the conclusions of this clause. + +In order to support scenarios where the EHE is accessed via an LBO PDU Session, it is concluded that URSP related procedures should be enhanced as follows: + +- PLMN ID(s) should be sent with URSP rules. How the PLMN ID(s) are included is defined in the conclusion of Key Issue #1 of TR 23.700-85 [10]. +- Whether the UE can be sent URSP rules that is applicable in the VPLMN before the UE is served by the VPLMN will be defined in the conclusion of Key Issue #1 of TR 23.700-85 [10]. + +NOTE 1: Normative work for the bullets above will take place within the scope of a WID that is based on the conclusions of FS\_eUEPO Key Issue #1. It will be decided in FS\_eUEPO Key Issue #1 whether a new trigger for URSP re-evaluation is needed. + +NOTE 2: The agreement that the normative work for this KI#1/LBO will take place within the WID for FS\_eUEPO depends on whether the conclusion for KI#1 FS\_eUEPO fulfils the conclusion listed in this clause. If this is not the case, the normative work to fulfil this conclusion will have to take place within the WID for EDGE\_Ph2. + +#### 8.1.2 Conclusion for scenario 2 (via HR PDU Session) + +Regarding KI#1 scenario 2, it is concluded with the following principles: + +##### 1. Authorization: + +AMF can get SMF Selection Subscription data with indication for HR-local traffic routing allowed during registration procedure, in order to help AMF select the proper SMF. V-SMF sends the HR PDU session establishment request to H-SMF, H-SMF authorizes the local traffic routing request for this PDU Session based on subscription data and provides HR-local traffic offloading authorization information (e.g. allowed FQDN ranges) to V-SMF. The V-SMF configures V-EASDF taking into account this authorization information. + +After authorizing the local traffic routing in VPLMN, the H-SMF sends VPLMN-specific roaming offload policy including traffic description information, e.g. FQDN range, EAS IP range and the session-related policy to the V-SMF if configured in HPLMN based on the service level agreement between VPLMN and HPLMN. + +##### 2. Charging: + +NOTE 1: It will be described how V-SMF supports charging for the local traffic of a PDU Session that supports local traffic routing to access an EHE in the VPLMN and whether it reports to V-CHF as well as to H-SMF in coordination with SA5 during normative phase. + +##### 3. EAS discovery: + +V-SMF decides UL-CL/BP and local UPF insertion based on V-EASDF notification and UE location. The V-SMF interacts with the H-SMF for UL CL/BP and local UPF insertion as described in clause 4.23.9.1 of TS 23.502 [9] by replacing I-SMF with V-SMF and SMF with H-SMF. + +For Options A and B as specified in clause 6.2.3.2.2 of TS 23.548 [3], with the following differences: + +V-SMF configures V-EASDF based on roaming offload policy from H-SMF and EAS Deployment Information from AF deployed in VPLMN via V-NEF and/or local configuration in V-SMF and the DNS server address of HPLMN received from HPLMN. + +The V-SMF sends the V-EASDF address to the H-SMF for the H-SMF to create PCO for the UE during PDU Session Establishment/Modification procedure. + +Options C and D specified in clause 6.2.3.2.3 of TS 23.548 [3] can be used to route some unencrypted DNS messages after the UL-CL is inserted for the PDU Session for HR roaming scenarios, with the following differences: + +- For Option C, the V-SMF sends the local DNS server address to the H-SMF for the H-SMF to create PCO for the UE during PDU Session Establishment/Modification procedure. +- For Option D, the H-SMF sends H-DNS server address 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 reusing IP replacement mechanism. In case of routing to V-EASDF, V-UPF replaces the destination IP address of DNS query (corresponding to FQDNs) to V-EASDF and routes this DNS query to V-EASDF, the EAS discovery procedure with V-EASDF which implements the functions of EASDF refers to TS 23.548 [3]. 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. The procedure and restriction of Option D defined in clause 6.2.3.2.3 of TS 23.548 [3] still apply in the HR roaming case. + +#### 4. EAS (Re-)discovery: + +For UE mobility triggered EAS Re-discovery for both inter-PLMN and intra-PLMN: + +The V-SMF uses the existing procedure defined in clause 4.23.9 of TS 23.502 [9] by replacing I-SMF with V-SMF and SMF with H-SMF to send target DNAI (if available), with the difference that V-SMF may optionally send also the impact field and optionally target V-EASDF to the H-SMF. + +The H-SMF triggers the PDU Session Modification procedure as described in TS 23.502 [9] and TS 23.548 [3] to send EAS rediscovery indication, optionally impact field and optionally V-EASDF to UE. + +For AF triggered EAS Re-discovery for an AF interacting with HPLMN: + +The AF deployed in VPLMN acting as 3rd party AF interacts with H-SMF via H-NEF and provides the target DNAI to the H-SMF. + +The H-SMF sends target DNAI information including the target DNAI to the V-SMF that relays this information to the AMF, and the AMF uses the target DNAI to select a target V-SMF as described in clause 4.23.5.4 of TS 23.502 [9] by replacing I-SMF with V-SMF, SMF with H-SMF. + +The target V-SMF selects target V-EASDF based on the target DNAI as described in clause 6.3.23 of TS 23.501 [2] and initiates PDU Session Modification procedure to trigger EAS re-discovery. + +NOTE 2: The baseline procedure for AF triggered EAS Re-discovery for an AF interacting with VPLMN will be determined in normative phase. + +5. For edge relocation in roaming scenarios, the AF sends PLMN ID corresponding to target EAS to the network, and an inter-PLMN relocation indicator is transferred between V-SMF and H-SMF to indicate that the EAS relocation is between HPLMN and VPLMN. + +### 8.1.3 Conclusion for ECS Address Configuration Information delivery + +#### 1. ECS Address Configuration Information (EACI) provision by the AF to 5GC: + +- For the LBO case, the AF in the visited PLMN provides the EACI by using the parameter provisioning procedure to UDM. This principle follows the design in Rel-17. +- For the HR case when access to EHE in VPLMN is allowed, there are two categories: + 1. the HPLMN has the knowledge of EACI in the VPLMN. + +In this case, it is assumed that an AF deployed in the HPLMN provides the EACI to the HPLMN (i.e. UDM) as per Rel-17. + +NOTE: SA WG2 is not going to define how an AF deployed in the HPLMN can know the EACI that applies in a given VPLMN. + +**In the UDM and UDR, the subscription data of EACI is stored per PLMN ID.** + +2. HPLMN does not have the knowledge of EACI in VPLMN. + +In this case, the AF deployed in the VPLMN provides the EACI in the VPLMN to the V-SMF via the V-NEF. During the HR PDU Session establishment, the V-SMF sends the VPLMN EACI obtained from V-AF to the H-SMF. + +2. Provision of the EACI to the UE: + +- The V-SMF (for the LBO case) or the H-SMF via the V-SMF (for the HR case) provides the UE with the EACI as indicated in step 11 in figure 4.3.2.2.1-1 of TS 23.502 [9]. +- For the HR case, the V-SMF does not modify, but just delivers the EACI provided by the H-SMF. + +## 8.2 Conclusion for KI#2: Fast and efficient network exposure improvements + +To support fast and efficient network exposure the conclusion for Key Issue #3 of TR 23.700-60 [21] (5GS information exposure for XR/media Enhancements) is endorsed. + +NOTE 1: Normative work will take place within the scope of a WID that is based on the conclusions of FS\_XRM Key Issue #3. + +## 8.3 Conclusion for KI#3: Policies for finer granular sets of UEs + +Normative specifications related to KI#3 will be based on following principles: + +- 1) the 5GC and the AF may (as part of a SLA) agree on a Target Category information that is an abstract value (whose values are not specified by 3GPP) and that may represent a combination of a list of External group Identifiers or any UE, and ("Subscriber categories" and/or service information). + +Whether 5GC actually exposes the internal representation of "subscriber categories" or some external representation is to be used, will be decided in normative phase. + +The combination may e.g. refer to users members of Group Id = X and Y and also having a certain "Subscriber category" for example "Gold", or any UE having subscriber category set to e.g. "Silver". + +- 2) The NEF may, based on local policies, determine a combination of a list of group Identifiers or any UE, and ("Subscriber categories" and/or service information), that is to be associated with the Target Category in an incoming Nnef\_TrafficInfluence service request. + +Only the NEF needs to be aware of Target Category and SLA with the application. + +NOTE: The NEF is the 5GC NF where policies per AF are configured. + +- 3) AF may provide a list of group IDs in AF request for providing policy for UEs belong to all the groups in the list. +- 4) The data stored by NEF in UDR (as part of step 3a of figure 4.3.6.2-1 of TS 23.502 [9]) and the information sent by UDR to the PCF (as part of step 4 of figure 4.3.6.2-1 of TS 23.502 [9]) may refer to a combination of Group IDs or any UE, and (service information and/or "Subscriber categories"). +- 5) The PCF is impacted by the work on this key issue as the policies it gets from UDR may refer to a combination of a list of Group IDs or any UE and (service information and/or "Subscriber categories"). +- 6) The SMF, EASDF and UPF are not impacted by normative work on this KI. + +## 8.4 Conclusion for KI#4: Influencing UPF and EAS (re)location for collections of UEs + +KI#4 shall be concluded by the three aspects: UE collection definition, 5GC selection of common EAS/DNAI, AF selection of common EAS/DNAI. + +### UE collection definition + +The selection of a common DNAI/EAS map apply to a collection of PDU Sessions that are accessing the same application and are using the same DNN, and are established by UEs in the UE collection. + +The UEs in the UE collection are identified by a UE list, group ID or any UE may be used. Optionally, Spatial Validity Condition, may be used to limit the UEs in the UE collection to a specific area. + +The dynamic group management may be used to manage the UEs in the UE collection, and Nnef\_ParameterProvision service for 5G VN group management is extended to support the dynamic group management other than that specific for 5G VN group. + +NOTE 1: The details to differentiate 5GVN group and general dynamic group, e.g. using Group Type indication, can be decided in the normative phase. + +Indication for traffic correlation, and optionally with Correlation ID, for using common DNAI/EAS as part of the Traffic influence information is provided to indicating the UE collection using common DNAI/EAS. + +The SMF determines that the UE belongs to a collection of UEs accessing the application based on the following: + +- the indication for traffic correlation in the PCC Rule with eas\_correlation indication/dnai\_correlation indication, Correlation ID, and: + - 1) the FQDN in the DNS Query reported to the SMF matched with FQDN(s) as indicated in the EAS Deployment Information and the Service data flow template of the PCC Rule with the indication for traffic correlation; or + - 2) the traffic to be routed matched with the Service data flow template of the PCC Rule with the indication for traffic correlation. + +NOTE 2: Whether correlation ID as a generic value, or Internal Group ID will be used to correlate a collection of UEs will be decided in normative phase. + +### 5GC selection and enforcement of common EAS/DNAI + +For solutions using 5GC NFs to manage the common EAS/DNAI, it is concluded that: + +- 5GC selection of the common DNAI for UE collection shall be supported; +- 5GC selection of a common EAS for a collection of UEs shall be supported; +- UDM/UDR is used for storing the common EAS/DNAI. + +For the common EAS/DNAI selection, it is concluded that: + +- SMF selects the common EAS/DNAI considering both multiple SMFs and single SMF cases. + +NOTE 3: The detailed procedure to be used to consider multiple SMFs for common DNAI/EAS selection in 5GC is decided in normative phase. + +For the common EAS/DNAI maintenance within 5GC, it is concluded that: + +- UDM/UDR is used for storing the common EAS/DNAI; +- 5GC enforcement of common EAS/DNAI is applicable to single as well as multiple SMFs cases. + +For the using of common DNAI/EAS, it is concluded that: + +- for using common DNAI for Traffic routing handling: + +- in case of Distributed Anchor connectivity model, the SMF may change the PSA of the PDU Session to a PSA that provides connectivity to the common DNAI; +- in case of Session Breakout connectivity model, the SMF triggers UL-CL/BP and L-PSA insertion as specified in clause 6.2.3.2.2 in TS 23.548 [3]. +- for using common DNAI/EAS for EAS (re)discovery: + - for EAS (Re-)discovery over Session Breakout Connectivity Model using EASDF, the common DNAI can be used as input for DNS handling rule construction: + - for Option A, the SMF configures the EASDF to insert an EDNS Client Subnet option to the DNS Query. The EDNS Client Subnet option refers to a location that is topologically close to the common DNAI; + - for Option B, the SMF configures the EASDF to forward the DNS Query to a common Local DNS server or a Local DNS related to the common DNAI; + - for Option C, the SMF provides the address of Local DNS server corresponds to common DNAI to UE; + - if a common EAS IP address is applicable to the collection of UEs and if the IP address of the common EAS is determined e.g. using EAS discovery procedure, the SMF configures the EASDF with DNS handling rules for the collection of UEs to directly respond with the IP address of the common EAS in response to the DNS Query; + - for common EAS, the SMF may initiate EAS re-discovery to the UE. + +NOTE 4: The control of the validity of the common EAS stored in 5GC can be discussed and decided in normative phase. + +#### AF selection of common EAS/DNAI + +As an option, AF could determine the common EAS/DNAI for the UE collection and provide the common EAS/DNAI to 5GS. For this aspect, it is proposed that: + +- AF selection of the common EAS/DNAI for UE collection shall be supported by 5GC; +- AF can determine the common EAS/DNAI, e.g. based on candidate DNAI(s) obtained from SMF(s); + +NOTE 5: The information used by the AF to determine common DNAI/EAS to be standardised is to be decided in normative phase. + +- AF may provide common DNAI/EAS for the UE collection as part of AF traffic influence data, or AF provides common EAS ID applicable to the group as part of group provisioning procedure. + +## 8.5 Conclusion for KI#5: GSMA OPG impacts and improvements for EHE operated by separate party + +To enable the discovery of an EAS deployed by the serving Operator's OP on cloud resources provided by another PLMN or partner (i.e. the Edge Node Sharing Scenario as described in GSMA OPG.02 [5], the following is recommended as baseline for normative work. + +### EAS Deployment Provision + +The serving PLMN is provided with the information needed to support UEs to discover and connect to the shared EHE deployed in the hosting network. In particular, the serving SMF may either store: + +- the FQDN(s), DNS Server Information, and/or DNAI(s) of the EAS Deployment Information (EDI, see TS 23.548 [3] clause 6.2.3.4-1). Depending on GSMA OPG feedback, a Partner ID (e.g. PLMN ID) to identify to which partner that EDI corresponds to may also be included. Such EDI information can be preconfigured in the serving SMF or provided by the AF. + +The serving SMF configures EASDF according to EDI based on Rel-17 methods (see TS 23.548 [3]). + +The DNS server can be selected by SMF by considering the UE location as described in Rel-17 TS 23.548 [3]. + +### EAS Discovery Procedure + +The EAS discovery procedure defined in TS 23.548 [3] will be reused. + +### Traffic transmission between two PLMNs + +When the traffic transmitted between two PLMNs, the UPF in serving PLMN should support mechanisms to facilitate low latency transmission. N6 routing information (as defined in TS 23.501 [2] clause 5.6.7) could be included in EDI for routing specific edge. + +NOTE: How to support charging in EHE sharing scenario will be specified by considering GSMA OPG's feedback. Some cooperation with SA5 may be needed. + +### Edge Relocation + +For edge relocation in GSMA OPG scenario, the EAS reselection methods should be the same as the initial selection. + +Edge relocation within the same hosting PLMN's EHE is supported, with the principles below: + +- 1) SMF initiates AF/EAS relocation and selection of the target EHE e.g. due to UE mobility; +- 2) SMF determines AF in the target EHE domain corresponding to the UE target location based on service area or EHE domain supported by AF; +- 3) notification of User plane management event procedure is enhanced to support AF/EAS change (Sol #23, see clause 6.23). + +EAS relocation between different PLMNs' EHE depends on GSMA feedback. Depending on the feedback, for different PLMNs case: + +- 1) the AF initiates EAS relocation (e.g. due to AF internal triggers) and sends PLMN ID corresponding to target EAS to the network for indicating the EAS should be relocated to the target PLMN (identified by PLMN ID); +- 2) the PCF creates the PCC rule including PLMN ID (if PCF authorizes that the traffic routing in the target PLMN is allowed); +- 3) the SMF determines the target DNAI for accessing target PLMN. + +## 8.6 Conclusion for KI#6: Avoiding UE to switch away from EC PDU Session + +It has been concluded not to pursue KI#6 for the normative phase. + +## 8.7 Conclusion for KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI + +The following are recommended as baseline for normative work: + +- NEF/UDR is configured by OAM with the mapping information between EAS IP/IP range and DNAI. +- AF requests to NEF to obtain DNAI by providing EAS IP/IP range and/or FQDN and optionally DNN, S-NSSAI, and geographical area. NEF checks the authorization of AF and obtains DNAI locally or from UDR. NEF responses DNAI to AF. +- Once the mapping information between DNAI(s) and EAS IP /IP range is changed or removed, AF can get the notification from NEF. + +## Annex A: Change history + +| Change history | | | | | | | | | +|----------------|----------|------------|----|-----|-----|---------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2022-02 | SA2#149e | S2-2201771 | - | - | - | TR23.700-48 skeleton | | 0.0.0 | +| 2022-09 | SA#97-e | SP-220823 | - | - | - | MCC editorial update for presentation to TSG SA for information | | 1.0.0 | +| 2022-11 | SA#98-e | SP-221114 | - | - | - | MCC editorial update for presentation to TSG SA for information | | 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-71/raw.md b/raw/rel-18/23_series/23700-71/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..73d3b87e9ee2e8482b453850e94134ab5754c41c --- /dev/null +++ b/raw/rel-18/23_series/23700-71/raw.md @@ -0,0 +1,6350 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement to the 5GC LoCation Services (LCS); 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 red signal wave icon. Underneath 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. + +© 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 ..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions of terms, symbols and abbreviations..... | 12 | +| 3.1 Terms..... | 12 | +| 3.2 Abbreviations ..... | 13 | +| 4 Architectural Assumptions and Requirements..... | 13 | +| 4.1 Architecture assumptions..... | 13 | +| 4.2 Architecture requirements ..... | 13 | +| 5 Key Issues ..... | 13 | +| 5.1 Key Issue #1: Architectural Enhancement to support User Plane positioning ..... | 13 | +| 5.1.1 Introduction ..... | 13 | +| 5.2 Key Issue #2: enhanced positioning architecture for NPN deployment ..... | 14 | +| 5.2.1 Description ..... | 14 | +| 5.3 Key Issue #3: Local Area Restriction for an LMF and GMLC ..... | 14 | +| 5.3.1 Description ..... | 14 | +| 5.4 Key Issue #4: Interaction between Location Service and NWDAF..... | 15 | +| 5.4.1 Description ..... | 15 | +| 5.5 Key Issue #5: Assistance data provisioning for low power high accuracy GNSS positioning..... | 15 | +| 5.5.1 Description ..... | 15 | +| 5.6 Key Issue #6: UE Positioning without UE/User Awareness..... | 16 | +| 5.6.1 Description ..... | 16 | +| 5.7 Key Issue #7: support of Positioning Reference Units and Reference UEs..... | 16 | +| 5.7.1 Description ..... | 16 | +| 5.8 Key Issue #8: support of location service continuity in case of UE mobility..... | 17 | +| 5.8.1 Description ..... | 17 | +| 5.9 Key Issue #9: Support of Positioning Requirements Related to Satellite Access..... | 17 | +| 5.9.1 Description ..... | 17 | +| 5.10 Key Issue #10: Support of Reduced Latency..... | 18 | +| 5.10.1 Description ..... | 18 | +| 5.11 Key Issue #11: Enhance the Triggered Location for UE power saving purpose ..... | 18 | +| 5.11.1 Description ..... | 18 | +| 5.12 Key Issue #12: support of low power and/or high accuracy positioning ..... | 19 | +| 5.12.1 Description ..... | 19 | +| 6 Solutions..... | 20 | +| 6.0 Mapping Solutions to Key Issues..... | 20 | +| 6.1 Solution #1: Positioning protocol transport over User Plane..... | 20 | +| 6.1.1 Introduction ..... | 20 | +| 6.1.2 Functional Description ..... | 20 | +| 6.1.3 Procedures ..... | 21 | +| 6.1.3.1 Establish LCS-UP connection between UE and LMF..... | 21 | +| 6.1.3.2 Modify LCS-UP connection between UE and LMF ..... | 22 | +| 6.1.3.3 UE Assisted and UE Based Positioning Procedure over LCS-UP ..... | 23 | +| 6.1.4 Impacts on services, entities, and interfaces..... | 23 | +| 6.2 Solution #2: Discovery of User Plane service Cooperated with 3GPP LCS Features..... | 24 | +| 6.2.1 Introduction ..... | 24 | +| 6.2.2 Functional Description ..... | 24 | +| 6.2.3 Procedures ..... | 27 | +| 6.2.3.1 LMF Offload traffic to Cooperated LCUP ..... | 27 | +| 6.2.3.2 LMF Activates UE with UP Connection to LCUP..... | 29 | +| 6.2.4 Impacts on services, entities, and interfaces..... | 30 | +| 6.3 Solution #3: User plane location capability transfer and positioning via user plane ..... | 30 | +| 6.3.1 Introduction ..... | 30 | + +| | | | +|----------|----------------------------------------------------------------------------|----| +| 6.3.2 | Functional Description ..... | 31 | +| 6.3.3 | Procedures ..... | 31 | +| 6.3.3.1 | User plane location capability transfer ..... | 31 | +| 6.3.3.2 | 5GC-MT-LR Procedure via user plane..... | 32 | +| 6.3.3.2a | Deferred 5GC-MT-LR Procedure via user plane ..... | 34 | +| 6.3.3.2b | Cancellation of Event Reporting..... | 35 | +| 6.3.3.3 | 5GC-MO-LR Procedure via user plane ..... | 35 | +| 6.3.3.4 | LPP transfer via user plane ..... | 36 | +| 6.3.3.5 | LMF Change Procedure with user plane positioning ..... | 37 | +| 6.3.4 | Impacts on services, entities, and interfaces..... | 38 | +| 6.4 | Solution #4: Direct communication between LMF and RAN node..... | 38 | +| 6.4.1 | Introduction ..... | 38 | +| 6.4.2 | Functional Description ..... | 38 | +| 6.4.3 | Procedures ..... | 40 | +| 6.4.3.1 | Network Assisted Positioning Procedure ..... | 40 | +| 6.4.3.2 | Obtaining Non-UE Associated Network Assistance Data..... | 41 | +| 6.4.4 | Impacts on services, entities, and interfaces..... | 41 | +| 6.5 | Solution #5: LCS architecture with "any AMF" ..... | 42 | +| 6.5.1 | Introduction ..... | 42 | +| 6.5.2 | Functional Description ..... | 42 | +| 6.5.3 | Procedures ..... | 43 | +| 6.5.3.1 | Network Assisted Positioning Procedure ..... | 43 | +| 6.5.3.2 | Obtaining Non-UE Associated Network Assistance Data..... | 43 | +| 6.5.4 | Impacts on services, entities, and interfaces..... | 44 | +| 6.6 | Solution #6: LMF selection based on LMF ID ..... | 44 | +| 6.6.1 | Introduction ..... | 44 | +| 6.6.2 | Functional Description ..... | 44 | +| 6.6.3 | Procedures ..... | 45 | +| 6.6.4 | Impacts on existing entities and interfaces..... | 45 | +| 6.7 | Solution #7: LMF selection based on client or AF identifier..... | 46 | +| 6.7.1 | Introduction ..... | 46 | +| 6.7.2 | Functional Description ..... | 46 | +| 6.7.3 | Procedures ..... | 46 | +| 6.7.4 | Impacts on services, entities, and interfaces..... | 46 | +| 6.8 | Solution #8: LMF Selection based on GMLC service area ..... | 46 | +| 6.8.1 | Introduction ..... | 46 | +| 6.8.2 | Functional Description ..... | 46 | +| 6.8.3 | Procedures ..... | 47 | +| 6.8.4 | Impacts on services, entities, and interfaces..... | 47 | +| 6.9 | Solution #9: local LMF and GMLC selection..... | 47 | +| 6.9.1 | Introduction ..... | 47 | +| 6.9.2 | Functional Description ..... | 47 | +| 6.9.3 | Procedures ..... | 47 | +| 6.9.3.1 | 5GC-MT-LR Procedure for the commercial location service ..... | 47 | +| 6.9.3.2 | integration with user plane positioning..... | 48 | +| 6.9.4 | Impacts on services, entities, and interfaces..... | 49 | +| 6.10 | Solution #10: Support interaction between location service and NWDAF ..... | 49 | +| 6.10.1 | Introduction ..... | 49 | +| 6.10.2 | Functional Description ..... | 49 | +| 6.10.3 | Procedures ..... | 50 | +| 6.10.3.1 | NWDAF accesses location service ..... | 50 | +| 6.10.3.2 | LMF obtains data analytics from NWDAF ..... | 50 | +| 6.10.4 | Impacts on services, entities, and interfaces..... | 50 | +| 6.11 | Solution #11: Interaction Enhancement between LCS and NWDAF ..... | 51 | +| 6.11.1 | Introduction ..... | 51 | +| 6.11.2 | Functional Description ..... | 51 | +| 6.11.3 | Procedure ..... | 51 | +| 6.11.4 | Impacts on services, entities, and interfaces..... | 52 | +| 6.12 | Solution #12: Supporting analytics for location accuracy ..... | 52 | +| 6.12.1 | Description ..... | 52 | +| 6.12.2 | Procedures ..... | 53 | +| 6.12.3 | Impacts on services, entities and interfaces..... | 57 | + +| | | | +|------------|--------------------------------------------------------------------------------------------|----| +| 6.13 | Solution #13: Architecture enhancement for the interaction between LCS and NWDAF ..... | 57 | +| 6.13.1 | Introduction ..... | 57 | +| 6.13.2 | Architecture ..... | 58 | +| 6.13.3 | Procedures ..... | 58 | +| 6.13.3.1 | One-time Collection Procedure ..... | 58 | +| 6.13.3.2 | Continuous Collection Procedure ..... | 59 | +| 6.13.4 | Impacts on existing entities and interfaces ..... | 61 | +| 6.13.4.1 | Impacts on AMF ..... | 61 | +| 6.13.4.2 | Impacts on NWDAF ..... | 61 | +| 6.14 | Solution #14: Unawareness positioning ..... | 61 | +| 6.14.1 | Introduction ..... | 61 | +| 6.14.2 | Functional Description ..... | 61 | +| 6.14.3 | Procedures ..... | 62 | +| 6.14.3.1 | UE unaware positioning ..... | 62 | +| 6.14.3.2 | User unaware positioning ..... | 63 | +| 6.14.4 | Impacts on services, entities, and interfaces ..... | 63 | +| 6.15 | Solution #15: PRU assisted LCS architecture and procedure ..... | 64 | +| 6.15.1 | Introduction ..... | 64 | +| 6.15.2 | Functional Description ..... | 64 | +| 6.15.2.1 | PRU Information ..... | 64 | +| 6.15.2.2 | PRU Information Acquisition ..... | 64 | +| 6.15.2.3 | PRU (de)/Activation ..... | 65 | +| 6.15.2.4 | CM-IDLE/RRC-Inactive PRU(s) Utilization ..... | 65 | +| 6.15.3 | Procedures ..... | 65 | +| 6.15.3.0 | Architecture Assumption ..... | 65 | +| 6.15.3.1 | PRU Management ..... | 66 | +| 6.15.3.2 | PRU Activation/Deactivation ..... | 68 | +| 6.15.3.3 | Location service procedure by using PRU(s) ..... | 68 | +| 6.15.3.3.1 | AMF-centric MT-LR ..... | 68 | +| 6.15.3.3.2 | AMF-centric MO-LR ..... | 70 | +| 6.15.3.3.3 | LMF-centric MT-LR ..... | 71 | +| 6.15.3.3.4 | LMF-centric MO-LR ..... | 72 | +| 6.15.4 | Impacts on services, entities, and interfaces ..... | 73 | +| 6.16 | Solution #16: Support of Positioning Reference Units ..... | 74 | +| 6.16.1 | Introduction ..... | 74 | +| 6.16.2 | Functional Description ..... | 74 | +| 6.16.3 | Procedures ..... | 75 | +| 6.16.3.1 | PRU Registration ..... | 75 | +| 6.16.3.2 | PRU Utilization ..... | 76 | +| 6.16.4 | Impacts on services, entities, and interfaces ..... | 77 | +| 6.17 | Solution #17: Support for 5GS Localization via Reference UE ..... | 77 | +| 6.17.1 | Introduction ..... | 77 | +| 6.17.2 | Functional Description ..... | 77 | +| 6.17.3 | Procedures ..... | 78 | +| 6.17.4 | Impacts on services, entities and interfaces ..... | 79 | +| 6.18 | Solution #18: Location Verification for Satellite Access assisted by NWDAF Analytics ..... | 79 | +| 6.18.1 | Introduction ..... | 79 | +| 6.18.2 | Functional description ..... | 79 | +| 6.18.3 | Procedures ..... | 80 | +| 6.18.4 | Impacts on services, entities and interfaces ..... | 81 | +| 6.19 | Solution #19: Support of Low Latency via User Plane ..... | 82 | +| 6.19.1 | Introduction ..... | 82 | +| 6.19.2 | Functional Description ..... | 82 | +| 6.19.2.1 | Architecture ..... | 82 | +| 6.19.2.2 | Protocol Layering ..... | 82 | +| 6.19.3 | Procedures ..... | 83 | +| 6.19.3.1 | Event Reporting from a UE directly to an LCS Client or AF ..... | 83 | +| 6.19.3.2 | Event Reporting from a UE to an LCS Client or AF via an H-GMLC ..... | 84 | +| 6.19.3.3 | Event Reporting from a UE to an LCS Client or AF via an LMF ..... | 86 | +| 6.19.3.4 | Cancellation of Event Reporting ..... | 88 | +| 6.19.4 | Impacts on services, entities, and interfaces ..... | 88 | +| 6.20 | Solutions 20: NWDAF based Indoor or Outdoor in Location Services ..... | 89 | + +| | | | +|-----------|--------------------------------------------------------------------------------------|-----| +| 6.20.1 | Introduction ..... | 89 | +| 6.20.2 | Solution Description ..... | 89 | +| 6.20.3 | Procedures ..... | 90 | +| 6.20.4 | Impacts on services, entities, and interfaces ..... | 91 | +| 6.21 | Solution #21: Collection of nearby GNSS assistance data ..... | 91 | +| 6.21.1 | Introduction ..... | 91 | +| 6.21.2 | Functional Description ..... | 91 | +| 6.21.3 | Procedures ..... | 92 | +| 6.21.3.1a | GNSS assistance data collection from untrusted AF ..... | 92 | +| 6.21.3.1b | GNSS assistance data collection from trusted AF ..... | 92 | +| 6.21.4 | Impacts on services, entities, and interfaces ..... | 93 | +| 6.22 | Solution #22: Support of LCS mobility when UE moves between NG-RAN nodes ..... | 93 | +| 6.22.1 | Introduction ..... | 93 | +| 6.22.2 | Functional Description ..... | 94 | +| 6.22.3 | Procedure ..... | 94 | +| 6.22.4 | Impacts on services, entities, and interfaces ..... | 96 | +| 6.23 | Solution #23: Location Verification for Satellite Access assisted by TN access ..... | 96 | +| 6.23.1 | Introduction ..... | 96 | +| 6.23.2 | Functional Description ..... | 97 | +| 6.23.3 | Procedures ..... | 97 | +| 6.23.4 | Impacts on services, entities, and interfaces ..... | 98 | +| 6.24 | Solution #24: UE Location Verification based on Obtained Information ..... | 98 | +| 6.24.1 | Introduction ..... | 98 | +| 6.24.2 | Functional Description ..... | 99 | +| 6.24.3 | Procedures ..... | 99 | +| 6.24.3.1 | UE Provided Location Verification based on Obtained Information ..... | 99 | +| 6.24.4 | Impacts on services, entities, and interfaces ..... | 100 | +| 6.25 | Solution #25: Event Report in an Allowed Area ..... | 100 | +| 6.25.1 | Introduction ..... | 100 | +| 6.25.2 | Functional Description ..... | 100 | +| 6.25.3 | Procedures ..... | 101 | +| 6.25.3.1 | Event Report Allowed Area provided by UE ..... | 101 | +| 6.25.3.2 | Event Report in an Allowed Area ..... | 101 | +| 6.25.3.3 | Add a new trigger for Cancellation of Reporting of Location Events by a UE ..... | 101 | +| 6.25.4 | Impacts on services, entities, and interfaces ..... | 101 | +| 6.26 | Solution #26: LPHAP requirement awareness by LMF ..... | 102 | +| 6.26.1 | Introduction ..... | 102 | +| 6.26.2 | Functional Description ..... | 102 | +| 6.26.3 | Procedures ..... | 103 | +| 6.26.4 | Impacts on services, entities, and interfaces ..... | 103 | +| 6.27 | Solution #27: Use Group Information to Correlate GMLC and LMF ..... | 104 | +| 6.27.1 | Introduction ..... | 104 | +| 6.27.2 | Functional Description ..... | 104 | +| 6.27.3 | Procedures ..... | 106 | +| 6.27.4 | Impacts on services, entities, and interfaces ..... | 106 | +| 6.28 | Solution #28: Support of PRUs ..... | 107 | +| 6.28.1 | Introduction ..... | 107 | +| 6.28.2 | Functional Description ..... | 107 | +| 6.28.2.1 | Architecture ..... | 107 | +| 6.28.2.2 | Protocol Layering ..... | 108 | +| 6.28.2.3 | Multiple LMF Association ..... | 108 | +| 6.28.3 | Procedures ..... | 109 | +| 6.28.3.1 | Registration Procedure ..... | 109 | +| 6.28.3.2 | Registration Modification Procedure ..... | 111 | +| 6.28.3.3 | Positioning Procedure for a PRU ..... | 112 | +| 6.28.4 | Impacts on services, entities, and interfaces ..... | 112 | +| 6.29 | Solution #29: Use PRU in 5G LCS Procedures ..... | 112 | +| 6.29.1 | Introduction ..... | 112 | +| 6.29.2 | Functional Description ..... | 113 | +| 6.29.3 | Procedures ..... | 114 | +| 6.29.3.1 | PRU Information Update ..... | 114 | +| 6.29.3.2 | Positioning Procedures with PRU ..... | 115 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.29.4 | Impacts on services, entities, and interfaces..... | 115 | +| 6.30 | Solution #30: location service continuity for UE moves between NG-RAN nodes ..... | 116 | +| 6.30.1 | Introduction ..... | 116 | +| 6.30.2 | Functional description ..... | 116 | +| 6.30.3 | Procedures ..... | 117 | +| 6.30.3.1 | Location Service Continuity for UE moves in RRC-inactive..... | 117 | +| 6.30.3.2 | Location Service Continuity for UE moves in CM-connected with RRC-connected ..... | 119 | +| 6.30.3.2.1 | Xn handover ..... | 119 | +| 6.30.3.2.2 | N2 handover ..... | 120 | +| 6.30.3.3 | Location Service Continuity for UE moves in CM-IDLE ..... | 121 | +| 6.30.4 | Impacts on services, entities, and interfaces..... | 121 | +| 6.31 | Solution #31: location service continuity between EPS and 5GS (bi-direction) ..... | 122 | +| 6.31.1 | Introduction ..... | 122 | +| 6.31.2 | Functional description ..... | 122 | +| 6.31.3 | Architecture Assumption..... | 122 | +| 6.31.4 | Procedures ..... | 124 | +| 6.31.4.1 | Location Service Continuity from 5GS to EPS ..... | 124 | +| 6.31.4.2 | Location Service Continuity from EPS to 5GS ..... | 126 | +| 6.31.5 | Impacts on services, entities, and interfaces..... | 126 | +| 6.32 | Solution #32: LCS continuity Support for N26 based Handover..... | 127 | +| 6.32.1 | Introduction ..... | 127 | +| 6.32.2 | Functional Description ..... | 127 | +| 6.32.3 | Procedures ..... | 127 | +| 6.32.3.1 | LCS support during Handover from 5GS to EPS ..... | 127 | +| 6.32.3.2 | LCS support during Handover from EPS to 5GS ..... | 129 | +| 6.32.4 | Impacts on services, entities, and interfaces..... | 131 | +| 6.33 | Solution #33: Support of LCS mobility when UE moves between 5GS and EPS..... | 131 | +| 6.33.1 | Introduction ..... | 131 | +| 6.33.2 | Functional Description ..... | 132 | +| 6.33.3 | Procedure ..... | 132 | +| 6.33.4 | Impacts on services, entities, and interfaces..... | 135 | +| 6.34 | Solution #34: UE location determination for Mobility Restriction enforcement..... | 135 | +| 6.34.1 | Introduction ..... | 135 | +| 6.34.2 | Functional Description ..... | 135 | +| 6.34.3 | Procedure ..... | 136 | +| 6.34.4 | Impacts on services, entities, and interfaces..... | 136 | +| 6.35 | Solution #35: Support reporting the UE location only when the UE locates the target area defined with the finer granularity ..... | 137 | +| 6.35.1 | Introduction ..... | 137 | +| 6.35.2 | Functional Description ..... | 137 | +| 6.35.3 | Procedures ..... | 137 | +| 6.35.3.1 | NWDAF interacts with GMLC..... | 137 | +| 6.35.3.1 | NWDAF interacts with AMF ..... | 139 | +| 6.35.4 | Impacts on services, entities, and interfaces..... | 141 | +| 7 | Evaluation ..... | 141 | +| 7.1 | Key Issue #1: Architectural Enhancement to support User Plane positioning ..... | 141 | +| 7.2 | Key Issue #2: enhanced positioning architecture for NPN deployment ..... | 144 | +| 7.3 | Key Issue #3: Local Area Restriction for an LMF and GMLC ..... | 144 | +| 7.4 | Key Issue #4: Interaction between Location Service and NWDAF..... | 145 | +| 7.5 | Key Issue #5: Assistance data provisioning for low power high accuracy GNSS positioning..... | 146 | +| 7.6 | Key Issue #6: UE Positioning without UE/User Awareness..... | 146 | +| 7.7 | Key Issue #7: Support of Positioning Reference Units and Reference UEs..... | 147 | +| 7.7.1 | Evaluation of solutions for PRU..... | 147 | +| 7.7.2 | Evaluation of solutions for Reference UE..... | 149 | +| 7.8 | Key Issue #8: support of location service continuity in case of UE mobility ..... | 150 | +| 7.9 | Key Issue #9: Support of Positioning Requirements Related to Satellite Access..... | 151 | +| 7.10 | Key Issue #10: Support of Reduced Latency..... | 153 | +| 7.11 | Key Issue #11: Enhance the Triggered Location for UE power saving purpose ..... | 153 | +| 8 | Conclusions..... | 154 | +| 8.1 | Key Issue #1: Architectural Enhancement to support User Plane positioning ..... | 154 | + +| | | | +|--------------------------------------|----------------------------------------------------------------------------------------------|------------| +| 8.2 | Key Issue #2: enhanced positioning architecture for NPN deployment ..... | 155 | +| 8.3 | Key Issue #3: Local Area Restriction for an LMF and GMLC ..... | 155 | +| 8.4 | Key Issue #4: Interaction between Location Service and NWDAF..... | 156 | +| 8.5 | Key Issue #5: Assistance data provisioning for low power high accuracy GNSS positioning..... | 157 | +| 8.6 | Key Issue #6: UE Positioning without UE/User Awareness..... | 157 | +| 8.7 | Key Issue #7: Support of Positioning Reference Units and Reference UEs..... | 157 | +| 8.8 | Key Issue #8: Support of location service continuity in case of UE mobility ..... | 158 | +| 8.9 | Key Issue #9: Support of Positioning Requirements Related to Satellite Access..... | 159 | +| 8.10 | Key Issue #10: Support of Reduced Latency..... | 159 | +| 8.11 | Key Issue #11: Enhance the Triggered Location for UE power saving purpose ..... | 159 | +| 8.12 | Key Issue #12: support of low power and/or high accuracy positioning ..... | 160 | +| Annex A: Change history ..... | | 161 | + +# 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 to the to the 5GC LoCation Services including the following aspects: + +- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. support Positioning Signalling via user plane. +- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. reduction of location service latency, signalling overhead and location estimate exposure. +- Study how the location services can benefit from NWDAF reporting and how the NWDAF use cases can benefit from location services, e.g. enhanced accuracy in certain UE location or population flow statistics data that require UE locations smaller than TA/cell +- Study enhancements to support low power positioning (e.g. for RedCap) including the requirements related to low power high accuracy positioning described in TS 22.104 [7]. +- Study necessary enhancement to support regulatory requirement i.e. the network should not notify the UE by any means during the LCS session. +- Study enhancement to support the Flexible and Efficient Periodic and Triggered Location for UE power saving purpose. +- In collaboration with RAN, study specific network functionality related to use of Positioning Reference Units (PRUs) as defined by RAN WGs and study how 5GS to support a specific UE (i.e. Reference UE) to improve the accuracy of positioning, and reduce the signalling; +- Study enhancements to support the location service continuity for UE mobility, i.e. between EPS and 5GS; +- For 5G with satellite access, in collaboration with RAN, study LCS architectural enhancement to support network verified UE location, and to meet location services related requirements defined in TS 22.261 [8]. + +# 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.271: "Functional stage 2 description of Location Services (LCS)". +- [5] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); 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". + +- [8] 3GPP TS 22.261: "Service requirements for the 5G system". +- [9] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [10] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [11] S3i210282: "LS OUT on UE location aspects in NTN" +[https://www.3gpp.org/ftp/TSG\\_SA/WG3\\_Security/TSGS3\\_LI/2021\\_81e-a/Docs/s3i210282.zip](https://www.3gpp.org/ftp/TSG_SA/WG3_Security/TSGS3_LI/2021_81e-a/Docs/s3i210282.zip). +- [12] RP-213690: "New WI: NR NTN (Non-Terrestrial Networks) enhancements". +- [13] OMA-AD-SUPL-V2\_0: "Secure User Plane Location Architecture Approved Version 2.0". +- [14] OMA-TS-ULP-V2\_0\_6: "User Plane Location Protocol Approved Version 2.0.6". +- [15] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)". +- [16] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [17] 3GPP TR 23.700-81: "Study on Enablers for Network Automation for 5G; Phase 3". +- [18] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1". +- [19] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [20] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2". +- [21] 3GPP TS 24.080: "Supplementary services specification; Formats and coding". +- [22] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2". +- [23] 3GPP TR 23.700-86: "Study on Architecture Enhancement to support Ranging based services and sidelink positioning". +- [24] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". +- [25] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". +- [26] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". + +# --- 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]. + +**Positioning Reference Unit (PRU):** As defined in TS 38.305 [6]. + +**Reference UE:** A UE with a location assumed known to the network that can obtain location related information of one or more target UE(s), which may assist the network to improve the positioning performance of target UE(s). In this technical report, the Reference UE is the PRU and the location related information is the measurements provided by PRU. + +**NOTE:** Within the FS\_eLCS\_ph3 study and this TR, the Reference UE has no relationship with other Studies, e.g. FS\_Ranging\_SL, unless clearly mentioned. If a terminology alignment between studies is required, it will be done before starting normative work. + +## 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]. + +| | | +|-------|--------------------------------------------| +| EASDF | Edge Application Server Discovery Function | +| EDC | Edge DNS Client | +| FQDN | Fully Qualified Domain Name | +| LCS | LoCation Service | +| LCUP | LCs User Plane | +| LMF | Location Management Function | +| LPP | LTE Positioning Protocol | +| LPPe | LPP extension | +| NPN | Non-Public Network | +| NWDAF | Network Data Analytics Function | +| PRU | Positioning Reference Unit | +| TAI | Tracking Area Identity | +| ULI | User Location Information | +| URSP | UE Route Selection Policy | + +# --- 4 Architectural Assumptions and Requirements + +## 4.1 Architecture assumptions + +The existing 5G LCS architecture is the bases for further enhancement work, with following add on assumption: + +- Positioning methods may be Access Network specific, although commonalties should be encouraged between Access Networks. + +## 4.2 Architecture requirements + +The following requirements are applicable to further enhance the existing 5GC LCS architecture defined in TS 23.273 [5]: + +- The further enhancement to the 5GC LCS architecture should incorporate flexible modular components with open interfaces that facilitate equipment interoperability and the architectural requirements based on evolution of service providing capabilities. +- The further enhancement to the 5GC LCS architecture should be future proof. + +### --- 5 Key Issues + +### 5.1 Key Issue #1: Architectural Enhancement to support User Plane positioning + +#### 5.1.1 Introduction + +The key target of this KI is to identify the LCS features and enhancements required to support user plane positioning. + +Positioning Signalling via user plane has several benefits, such as: + +- It has a more efficient communication overload with a direct connection from LCS server to UE. + +- It may not require gNodeB, AMF, LMF signalling processing of RRC, NG-AP and HTTP/2 protocol stacks. A single session may handle all the transactions. +- It can have multiple choices depending on UE support. For example, both 3GPP LPP and OMA LPPe can be possible in positioning methods' choices. + +To deploy user plane positioning, it involves the following considerations: + +- Different use cases like emergency/non-emergency, other regulatory cases like lawful interception and MO-LR cases, etc. +- Different deployment options including centrally deployed or local deployment ,i.e, deployed the edge data network. +- Whether the solution is end to end or restricted to only certain entities (e.g. UE and LMF, LMF and LCS Client). + +For user plane positioning deployment, two options are identified, although other options are also possible: + +Option 1: User plane positioning functionality (e.g. LMF) in the central network. + +Option 2: The user plane positioning functionality can be deployed "in scenarios like edge computing" of the edge data network to provide positioning in the edge and fits into the architecture in TS 23.548 [10]. + +This KI is to address architectural changes allowing user plane positioning deployment, including central deployment or deployment at the edge e.g.: + +- Discovery of user plane capability and configuration and selection of PDU Sessions (if needed) to be used for the communication between UE and user plane positioning. +- Whether and how to enhance existing 5GS LCS architecture or related procedures to support MO-LR, MT-LR, Deferred MT-LR and regulatory-related positioning procedures when user plane positioning is involved. +- Interaction with legacy LCS call flows and security aspect. +- Requirements on transport protocol e.g. if reliable transport and in sequence delivery is required. +- Interaction (if any) between user plane and existing control plane solution. +- User plane as a possible enhancement to control plane. + +## 5.2 Key Issue #2: enhanced positioning architecture for NPN deployment + +### 5.2.1 Description + +For NPN network deployments, the following technical issues will be studied: + +- How to realize low latency positioning procedure under NPN deployment. +- How to realize low complexity positioning procedure under NPN deployment. +- How to achieve reliable and secure location result delivery and exposure, e.g. UE location not exposed to the public network. + +## 5.3 Key Issue #3: Local Area Restriction for an LMF and GMLC + +### 5.3.1 Description + +In some scenarios, an GMLC and an LMF might be restricted to supporting location services in a local area, i.e. the LMF needs to be selected within the same local area of the GMLC. The objective of this KI is to investigate how to support the local area restriction for GMLC and LMF. + +NOTE: This KI is not applicable to an NPN. + +## 5.4 Key Issue #4: Interaction between Location Service and NWDAF + +### 5.4.1 Description + +NWDAF can generate different analytics data, e.g. UE mobility analytics, WLAN performance analytics. 5GC NF (e.g. AMF, PCF) can request analytics data from NWDAF for decision making. But whether and how location service can benefit from NWDAF is not studied yet. For example, whether the existing analytics generated by NWDAF (e.g. WLAN performance analytics) can be used to improve the location service performance, e.g. to assist the LMF to select the positioning method or decide more accurate assistance data? + +Furthermore, based on Table 6.7.2.2.1 and Table 6.7.2.3.1 of TS 23.288 [9], the UE location collected and included in the analytics data by the NWDAF is TA or cell. But in some use cases, analytics in granularity of TA or cell level is not sufficient. Considering location service can provide more accurate UE location information, it is needed to study how does the location service provides such information to NWDAF. + +To support the aspects above, this key issue will study: + +- How to provide the NWDAF with location information with finer granularity than TA/cell level, e.g. which NF in the location architecture supports the interface to the NWDAF, whether existing location procedures can be re-used or not; +- Whether the privacy check can be skipped or not when the NWDAF requests location information via LCS services, if not, how to perform the privacy check in LCS; +- Whether existing data analytics generated by the NWDAF can be used to improve location service performance and how, e.g. assist the LMF to select the positioning method, decide more accurate assistance data, reduce signalling cost and delay etc.; +- Identify use cases where new or existing data analytics from the NWDAF can be used for improving location service performance. Regulatory requirements (e.g. different location accuracy requirements from FCC in different cases) will be taken into account. + +NOTE: Coordinated activities between the study FS\_eNA\_Ph3 and this study are needed. Any new data analytics agreed as part of this Key Issue that need to be provided by NWDAF need to be studied and agreed in FS\_eNA\_Ph3. + +## 5.5 Key Issue #5: Assistance data provisioning for low power high accuracy GNSS positioning + +### 5.5.1 Description + +The GNSS assistance data could help reduce UE GNSS receivers' power consumption and increase the position accuracy. Nowadays, UE usually gets the assistance data from internet through user-plane. However, using a user plane based way means that UE must active a PDU Session, which leads to higher power consumption. Moreover, it may not apply to Redcap UEs, as some of them may not support to establish a PDU Session. + +The distance between the UE GNSS receivers and GNSS reference receiver should be sufficiently short to make sure the GNSS assist data provided by the reference receiver are valid and accurate. However, GNSS reference receivers are not widely implemented in some countries, which makes it hard to provide high accuracy GNSS positioning service for UE GNSS receivers in some areas. + +This key issue aims at studying the possible method to get nearby GNSS assistance data inside 3GPP, to mitigate a lack of implementation of GNSS reference receivers. + +The following aspects will be studied: + +- How could the core network (i.e. LMF) get the GNSS assistance data of a GNSS reference receiver, either inside 3GPP domain or external to 3GPP domain to select a GNSS reference receiver close to the estimated location of the UE, help reduce power consumption and increase the positioning accuracy? +- Whether and how existing procedures, protocols or interfaces can be re-used or enhanced to make UE get the nearby GNSS assistance data? + +## 5.6 Key Issue #6: UE Positioning without UE/User Awareness + +### 5.6.1 Description + +There are regulatory cases (e.g. helping with police enquires), in that UE should not be notified by any means during the LCS session. But how to support the requirement has not been considered. + +For some IoT or RedCap devices, when power saving is more important than fulfilling the LCS request, how to obtain UE location without notifying the UE especially when UE is in CM-IDLE or RRC\_INACTIVE state is also not considered. + +To support the requirements above, this key issue will study: + +- Which NF and how to decide not to notify UE/User during the LCS session, e.g. what information is considered to make the decision; +- Functionality and procedure enhancements to guarantee not to notify UE/User during the LCS session when UE is in CM\_CONNECTED, CM\_IDLE or RRC\_INACTIVE state; +- What UE location information is provided to LCS Client/ AF to fulfil the LCS QoS when the UE is in CM\_IDLE or RRC\_INACTIVE state and if the UE is not notified during the LCS procedure. + +## 5.7 Key Issue #7: support of Positioning Reference Units and Reference UEs + +### 5.7.1 Description + +Based on RAN WG conclusion in Rel-17, positioning reference units (PRUs) with known locations can enhance the positioning performance. PRUs may be used to assist positioning of UEs by e.g. providing measurement information related to RAN nodes. This key issue aims to study the system level impact to support PRUs. + +The accuracy of positioning heavily relies on the number of Line of Sight (LoS) paths, so positioning in the indoor environment is complex, as there are many factors that reduce the possibility of LoS path. It is resource consuming and complicated to deploy sufficient RAN nodes (e.g. pRRUs or gNBs) to provide enough LoS path, considering the complex environment with possible changes. Consequently, a simplified node, referred to as a Reference UE, is required to provide more potential LoS paths for positioning. + +The following aspects will be studied for PRUs: + +- What information of the PRUs needs to be obtained by 5GC and how can the 5GC become aware which PRU(s) are available. +- How can 5GC determine and enable particular (e.g. candidate) PRU(s) from the available PRU(s). +- How are the location service procedures performed to improve positioning accuracy using PRU(s). This can include using PRUs to assist positioning of one UE or using PRUs to assist positioning of many or all UEs. + +The following aspects will be studied for Reference UEs: + +- Whether and how the 5GS can assist with the selection of Reference UE supporting the 5G location services provided to a different UE. +- The specific entities and mechanisms in the 5GC whose functionality need to be updated to account for the Reference UE operation as part of the location service. + +NOTE 1: Coordination with RAN WG may be required. + +NOTE 2: Whether PRU and Reference UE can be the same entity should be determined during normative phase. + +NOTE 3: Within the FS\_eLCS\_ph3 study and this TR, the Reference UE has no relationship with other Studies, e.g. FS\_Ranging\_SL, unless clearly mentioned. If a terminology alignment between studies is required, it will be done before starting normative work. + +## 5.8 Key Issue #8: support of location service continuity in case of UE mobility + +### 5.8.1 Description + +For commercial location service, in particular the use case on vehicle(V2X) UE, it is very likely that UE moves between EPS and 5GS, and continuous UE positioning (periodical location service/LDR) is required. + +Following UE mobility scenarios are considered under this key issue: + +- UE mobility between EPS and 5GS (bi-direction). +- UE mobility between NG-RAN node. + +The following "Types of Location Request" should be considered in the scope of WT#6: + +- Mobile Terminated Location Request, and in detail covers: + - Immediate Location Request (Response Time "no delay" and "low delay" are excluded). + - Deferred Location Request (both periodic location service, and event based location request). +- Mobile Originated Location Request. + +The following issues will be studied: + +- How to handle the UE location service context in case of UE mobility (e.g. context in the AMF, MME, LMF, E-SMLC). +- Configuration update of the positioning information/configuration on the source and target RAN nodes in case of UE mobility. +- How to enhance the cancellation of the existing positioning procedure in case of UE mobility. + +## 5.9 Key Issue #9: Support of Positioning Requirements Related to Satellite Access + +### 5.9.1 Description + +In Rel-17, the 5GS system has been enhanced to support the service requirements of 5GC with satellite access (in the WID: Architecture aspects for using satellite access in 5G). + +In Rel-17, when a UE is using NR satellite access, in order to ensure to meet the regulatory requirements, the network will verify whether the PLMN selected by the UE is allowed to operate in the country of the UE location based on the UE location information. + +Besides, the broadcast TAI(s) and the TAI where the UE is geographically located, if known, will be provided as part of ULI by NG-RAN to the AMF. Using UE-generated location information (e.g. GNSS/A-GNSS) to determine the TAI where the UE is geographically located can be accurate but may be unreliable as has been evaluated by SA WG3. + +When UE access 5G via satellite access, some services with regulatory requirements, e.g. emergency calls service and lawful interception, require a trusted/reliable methods to determine with sufficient accuracy the UE location. Any method which relies solely on UE-generated location information may not be reliable unless the information provided + +by the UE can be verified by the network. But how does the network verify the UE location has not been considered, so this key issue will study: + +- What kind of location information can represent the UE location that meets required accuracy in NR satellite access (e.g. doing verification based on the location information to meet regulatory requirements)? +- In collaboration with RAN, for the reliability of the location verification by the network for regulated services (LI, emergency) and given SA WG3-LI requirements defined in S3i210282 [11], further study how the 5GC LCS can ensure that network verification of UE location is performed with reliable method, that does not rely solely on UE-generated location information, and the result of such network verification of UE location meets aforementioned requirements; +- In collaboration with RAN on their work on network verified UE location, study whether existing core network verification mechanisms needs enhancement and conditions (which NF, when, how, etc.); +- How to further enhance the LCS to verify location services related requirements defined in TS 22.261 [8]; + +NOTE: The work of this key issue needs collaboration with RAN. Considering SA WG2 Rel-18 work begins earlier than RAN and RAN will make decision related to the work by RAN#98 as indicated in NR\_NTN\_enh WID in RP-213690 [12], thus SA WG2 can start discussing solutions first and make conclusion in collaboration with RAN. + +## 5.10 Key Issue #10: Support of Reduced Latency + +### 5.10.1 Description + +Reduction of latency is useful for many user cases and needs to be end-to-end. For example, very low latency for positioning that may be supported by procedures defined by RAN1 and RAN2 would be nullified by extra time in establishing a positioning session with a target UE or in returning a location estimate to an LCS Client or AF. + +The following aspects will be studied: + +- Reducing end to end latency for an immediate location request (5GC-MT-LR, 5GC-MO-LR). +- Reducing end to end latency for a deferred location request (periodic or triggered 5GC-MT-LR). + +NOTE: Reducing latency should focus on aspects related to signalling and procedures involving the 5GCN and not on aspects completely within NG-RAN which are under RAN control. + +## 5.11 Key Issue #11: Enhance the Triggered Location for UE power saving purpose + +### 5.11.1 Description + +Some use cases only need the UE location to be tracked when the UE is within a set of pre-defined areas, e.g. when UE is within one big city or a campus. For power saving purpose, it is beneficial to only allow UE location tracking when the UE enters one such area. + +This Key Issue will study: + +- How to provide location service only when the UE is within a pre-defined area, including border district and central district in this area; +- How to define and identify the pre-defined areas; and: +- Which entity provide such pre-defined areas to the LCS system and how? + +## 5.12 Key Issue #12: support of low power and/or high accuracy positioning + +### 5.12.1 Description + +SA WG1 considers low power high accuracy positioning is an integral part of a considerable number of industrial applications. The total energy needed for a specific operation time for such a low power high accuracy positioning optimized IoT-device is a combination of energy for positioning (varies depending on the used positioning method), energy for communication/synchronization and a difficult to predict factor to take additional losses through e.g. security, power management, microcontroller, and self-discharge of batteries into account. + +Low power and/or high accuracy positioning may need specific handling in the system level, depending on the localization requirements of an LCS Client or AF. + +Reduction of power consumption can be useful for IIoT and CIoT UEs and is generally preferable for any UE to improve battery lifetime. Reduction of power consumption may or may not be associated with high accuracy. + +Following issues are proposed for study: + +- How to identify localization QoS for low power and/or high accuracy positioning; +- Whether new information is needed in subscription data for low power and/or high accuracy positioning; +- Whether LCS QoS should be enhanced to support LPHAP; +- How to handle UE connection management/mobility management, for power saving purpose, when supporting low power and/or high accuracy positioning; +- Positioning procedure optimization: + - Reducing UE power consumption for an immediate location request (5GC-MT-LR, 5GC-MO-LR); + - Reducing UE power consumption for a deferred location request (periodic or triggered 5GC-MT-LR); + - Reducing UE power consumption in association with high accuracy positioning. + +## 6 Solutions + +### 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 | 7 | 8 | 9 | 10 | 11 | 12 | +| 1 | X | | | | | | | | | X | | | +| 2 | X | | | | | | | | | | | | +| 3 | X | | | | | | | | | X | | | +| 4 | | X | | | | | | | | | | | +| 5 | | X | | | | | | | | | | | +| 6 | | | X | | | | | | | | | | +| 7 | | | X | | | | | | | | | | +| 8 | | | X | | | | | | | | | | +| 9 | | | X | | | | | | | | | | +| 10 | | | | X | | | | | | | | | +| 11 | | | | X | | | | | | | | | +| 12 | | | | X | | | | | | | | | +| 13 | | | | X | | | | | | | | | +| 14 | | | | | | X | | | | | | | +| 15 | | | | | | | X | | | | | | +| 16 | | | | | | | X | | | | | | +| 17 | | | | | | | X | | | | | | +| 18 | | | | X | | | | | X | | | | +| 19 | X | | | | | | | | | X | | | +| 20 | | | | X | | | | | | | | | +| 21 | | | | | X | | | | | | | | +| 22 | | | | | | | | X | | | | | +| 23 | | | | | | | | | X | | | | +| 24 | | | | | | | | | X | | | | +| 25 | | | | | | | | | | | X | | +| 26 | | | | | | | | | | | | X | +| 27 | | | X | | | | | | | | | | +| 28 | | | | | | | X | | | | | | +| 29 | | | | | | | X | | | | | | +| 30 | | | | | | | | X | | | | | +| 31 | | | | | | | | X | | | | | +| 32 | | | | | | | | X | | | | | +| 33 | | | | | | | | X | | | | | +| 34 | | | | | | | | | X | | | | +| 35 | | | | X | | | | | | | X | | + +### 6.1 Solution #1: Positioning protocol transport over User Plane + +#### 6.1.1 Introduction + +This solution addresses Key Issue #1 on Architectural Enhancement to support User Plane positioning and also provides option to reduce latency for Key Issue #10. + +#### 6.1.2 Functional Description + +The AMF, UE and LMF are enhanced to initiate setup of a User Plane connection between a selected LMF and UE and to provide LMF and UE with needed information to establish a secure connection. The information includes e.g. IP address of LMF to be used for the connection, temporary UE identifier (not the same as used N2 or other reference points), and security credentials. The AMF, UE and LMF are enhanced to transport LPP over a UP protocol. Once the + +LCS-UP connection is established the LMF selects either to use the LCS-UP procedure according to clause 6.1.3.3 or to use CP procedure according to clause 6.11.1 of TS 23.273 [5]. Within one LPP session the same transport shall be used. + +Since LCS-UP connection is maintained during the lifetime of the PDU session, the procedure also reduces the latency if LMF selects LCS-UP over CP for certain positioning requests. + +Current solution considers UE has only one LCS-UP connection with the selected LMF. + +Multiple LCS-UP connection establishment could be also considered from a single or multiple LMF to separate different traffic type (emergency, LI or commercial). + +NOTE: If and what security mechanism is used and subject to SA WG3 conclusion. + +It is proposed to define a protocol stack that includes a lightweight LPP transfer protocol that is limited services aligned to what CP transport provides (e.g. identification of UE and positioning session). A potential stack is shown in Figure 6.1.2-1 (TCP is shown as example of a transport layer and security details are omitted). Details of protocol stack will be determined in the normative work. + +![Figure 6.1.2-1: Protocol Layering for User Plane Transfer of LPP. The diagram shows the protocol stacks for UE, 5G-AN, UPF, and LMF. UE stack: LPP, LPP Transfer Protocol, TCP, IP, 5G-AN Protocol Layers. 5G-AN stack: 5G-AN Protocol Layers, Relay, 5GC Protocol Layers. UPF stack: IP, 5GC Protocol Layers. LMF stack: LPP, LPP Transfer Protocol, TCP, IP, Lower Protocol Layers. Interfaces N3 and N6 are indicated between 5G-AN and UPF, and UPF and LMF respectively.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +Figure 6.1.2-1: Protocol Layering for User Plane Transfer of LPP. The diagram shows the protocol stacks for UE, 5G-AN, UPF, and LMF. UE stack: LPP, LPP Transfer Protocol, TCP, IP, 5G-AN Protocol Layers. 5G-AN stack: 5G-AN Protocol Layers, Relay, 5GC Protocol Layers. UPF stack: IP, 5GC Protocol Layers. LMF stack: LPP, LPP Transfer Protocol, TCP, IP, Lower Protocol Layers. Interfaces N3 and N6 are indicated between 5G-AN and UPF, and UPF and LMF respectively. + +Figure 6.1.2-1: Protocol Layering for User Plane Transfer of LPP + +## 6.1.3 Procedures + +### 6.1.3.1 Establish LCS-UP connection between UE and LMF + +The flow below shows how a secure LCS-UP connection between UE and LMF is established. + +![Figure 6.1.3.1-1: Connection establishment between UE and LMF. This sequence diagram shows the interaction between UE, AMF, NG-RAN, UPF, and LMF. 1. AMF triggers LMF selection and LCS-UP setup. 2. AMF sends Nlmf_Location_UPConfig (UP Info) Request to LMF. 3. LMF sends Nsmf_Communication_N1N2MessageTransfer (UP Info) to AMF. 4. AMF sends DL NAS TRANSPORT (UP Info) to UE via NG-RAN. 5. A secure connection is established between UPF and LMF. 6. LMF sends Nlmf_Location_UPConfig Response to AMF. 7. AMF stores the LCS-UP connection context.](2876be3592c7b4878400b85f209b2b6a_img.jpg) + +Figure 6.1.3.1-1: Connection establishment between UE and LMF. This sequence diagram shows the interaction between UE, AMF, NG-RAN, UPF, and LMF. 1. AMF triggers LMF selection and LCS-UP setup. 2. AMF sends Nlmf\_Location\_UPConfig (UP Info) Request to LMF. 3. LMF sends Nsmf\_Communication\_N1N2MessageTransfer (UP Info) to AMF. 4. AMF sends DL NAS TRANSPORT (UP Info) to UE via NG-RAN. 5. A secure connection is established between UPF and LMF. 6. LMF sends Nlmf\_Location\_UPConfig Response to AMF. 7. AMF stores the LCS-UP connection context. + +Figure 6.1.3.1-1: Connection establishment between UE and LMF + +1. At applicable Registration events or when an LCS procedure is initiated, AMF may decide to select an LMF and request the UE and the selected LMF to establish an LCS-UP connection to be used for transfer of LPP signalling. The decision may be based on e.g. UE capabilities, UE location, subscription information, LMF load + +and LMF capabilities. It can be an operator decision whether LCS-UP connection is established at Registration events or when an LCS procedure is initiated. + +Latency sensitive use-cases would require LCS-UP connection established at Registration events. Emergency traffic might not require pre-established LCS-UP connection. + +- 1.b. When a new LCS procedure is initiated for the UE which already has LCS-UP connection, the AMF may detect a need to reselect LMF used for LCS-UP signalling. The detection may be based on e.g. UE capabilities, UE location, subscription information, LMF load and LMF capabilities. Further at AMF relocation, the target AMF needs to inform the LMF using LCS-UP signalling about the AMF change. +2. The AMF sends a Nlmf\_Location\_UPConfig Request towards the LMF to request set up of a LCS-UP connection. The message may include e.g. a temporary UE identifier. +3. The LMF sends a LCS UP Info message to the UE via the serving AMF by invoking the Namf\_Communication\_N1N2MessageTransfer service operation. The LCS UP Info message may include e.g. IP or FQDN address of LMF, temporary UE identifier and security credentials. +4. The AMF forwards the LCS UP Info in a DL NAS TRANSPORT message. +5. The UE and LMF establish a secure connection. +6. The LMF sends Nlmf\_Location\_UPConfig Response message to AMF to inform of outcome of connection setup. +7. The AMF stores the LCS-UP connection context as part of UE context. + +After establishing the connection, UE and LMF may maintain the connection for later message transfer via user plane. + +### 6.1.3.2 Modify LCS-UP connection between UE and LMF + +The flow below shows how a secure LCS-UP connection between UE and LMF is modified. Flow describes change of LMF but applies also when source and target LMF is the same. The procedure can also be used to terminate LCS-UP connection to Source LMF by AMF not selecting any Target LMF. + +![Sequence diagram illustrating the connection modification between UE and LMFs. The diagram shows four lifelines: UE, AMF, Source LMF, and Target LMF. The sequence of messages is: 1a. Nlmf_Location_UPNotify (UP Info) from Source LMF to AMF; 1b. Trigger LMF reselection (conditional) within AMF; 2. Move connection to Target LMF (conditional) from AMF to Source LMF; 3. Nlmf_Location_UPConfig (UP Info) Request from AMF to Source LMF; 4. Terminate connection with UE (conditional) from Source LMF to AMF; 5. Nlmf_Location_UPConfig Response from Source LMF to AMF.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant Source LMF + participant Target LMF + Note right of Source LMF: 1a. Nlmf_Location_UPNotify (UP Info) + Source LMF->>AMF: 1a. Nlmf_Location_UPNotify (UP Info) + Note right of AMF: 1b. Trigger LMF reselection + AMF-->>Source LMF: 2. Move connection to Target LMF + Note right of AMF: 3. Nlmf_Location_UPConfig (UP Info) Request + AMF->>Source LMF: 3. Nlmf_Location_UPConfig (UP Info) Request + Note right of Source LMF: 4. Terminate connection with UE + Source LMF-->>AMF: 4. Terminate connection with UE + Note right of Source LMF: 5. Nlmf_Location_UPConfig Response + Source LMF->>AMF: 5. Nlmf_Location_UPConfig Response + +``` + +Sequence diagram illustrating the connection modification between UE and LMFs. The diagram shows four lifelines: UE, AMF, Source LMF, and Target LMF. The sequence of messages is: 1a. Nlmf\_Location\_UPNotify (UP Info) from Source LMF to AMF; 1b. Trigger LMF reselection (conditional) within AMF; 2. Move connection to Target LMF (conditional) from AMF to Source LMF; 3. Nlmf\_Location\_UPConfig (UP Info) Request from AMF to Source LMF; 4. Terminate connection with UE (conditional) from Source LMF to AMF; 5. Nlmf\_Location\_UPConfig Response from Source LMF to AMF. + +**Figure 6.1.3.2-1: Connection modification between UE and LMFs** + +- 1a. [Conditional] The LMF discovers a need to change LMF or re-establish LCS-UP connection. The LMF sends an Nlmf\_Location\_UPNotify message that includes UP Info that indicates the reason for modification. The address of the AMF was provided to LMF as a "Notification Target Address" in latest Nlmf\_Location\_UPConfig message. +- 1b. [Conditional] At applicable Registration events and when an LCS procedure is initiated, AMF may detect a need to reselect LMF used for LCS-UP signalling. The detection may be based on e.g. UE capabilities, UE location, subscription information and LMF capabilities. Further at AMF relocation the target AMF needs to inform the LMF using LCS-UP signalling of the AMF change. + +2. [Conditional] If AMF reallocation has occurred this step is skipped. Otherwise, steps 2 to 7 of clause 6.1.3.1 are performed between AMF, UE, and Target LMF with addition that UE also terminate connection to Source LMF. +3. The AMF sends a Nlmf\_Location\_UPConfig Request towards the source LMF. The message may include a request for the Source LMF to terminate a specific LCS-UP connection to the UE if connection is still active. Alternatively, it may include information about AMF reallocation. +4. [Conditional] If the LCS-UP connection to source LMF is still active source LMF terminates the connection to the UE. +5. The LMF sends Nlmf\_Location\_UPConfig Response message to AMF to confirm connection termination or acknowledge change of AMF. + +### 6.1.3.3 UE Assisted and UE Based Positioning Procedure over LCS-UP + +The flow below shows a positioning procedure used by an LMF to support UE based positioning, UE assisted positioning and delivery of assistance data. The procedure is based on use of the LPP protocol defined in TS 37.355 [15] between the LMF and UE. + +![Sequence diagram of UE Assisted and UE Based Positioning Procedure over LCS-UP. The diagram shows four entities: UE, NG-RAN, UPF, and LMF. The sequence of messages is: 1. DL UP TRANSFER (LPP Message) from LMF to UE via UPF and NG-RAN. 2. Positioning Measurements and/or Computation performed by the UE. 3. UL UP TRANSFER (LPP Message) from UE via NG-RAN and UPF to LMF.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant UPF + participant LMF + Note left of UE: 2. Positioning Measurements and/or Computation + LMF->>UPF: 1. DL UP TRANSFER (LPP Message) + UPF->>NG-RAN: + NG-RAN->>UE: + UE->>NG-RAN: 3. UL UP TRANSFER (LPP Message) + NG-RAN->>UPF: + UPF->>LMF: + +``` + +Sequence diagram of UE Assisted and UE Based Positioning Procedure over LCS-UP. The diagram shows four entities: UE, NG-RAN, UPF, and LMF. The sequence of messages is: 1. DL UP TRANSFER (LPP Message) from LMF to UE via UPF and NG-RAN. 2. Positioning Measurements and/or Computation performed by the UE. 3. UL UP TRANSFER (LPP Message) from UE via NG-RAN and UPF to LMF. + +**Figure 6.1.3.3-1: UE Assisted and UE Based Positioning Procedure over LCS-UP** + +1. The LMF use the LCS-UP connection to transfer of a Downlink (DL) UP TRANSFER message to the UE. The message includes a LPP message. The LPP message may request location information from the UE, provide assistance data to the UE or query for the UE capabilities. +2. The UE stores any assistance data provided in the Downlink Positioning message and performs any positioning measurements and/or location computation requested by the Downlink Positioning message. +3. [Conditional] The UE use the LCS-UP connection to transfer of a Uplink (UL) UP TRANSFER message carrying includes a LPP message to the LMF to return any location information or returns any capabilities. + +### 6.1.4 Impacts on services, entities, and interfaces + +The solution impacts the following network functions: + +- AMF that need to support triggering of LCS-UP connection setup, modification & termination. Additionally, AMF also needs to consider at LMF selection that the requested UE has an existing LCS-UP connection with one of the LMFs. +- LMF that need to support procedure to setup, modification & termination of LCS-UP connection. Transfer of LPP messages over LCS-UP. +- UE that need to support: Procedure to setup, modification & termination of LCS-UP connection. Transfer of LPP messages over LCS-UP. +- UDM that need to add info in Subscriber info if LCS-UP transport is supported. +- NRF that need to add info in NF profile LMF support LCS-UP transport. + +## 6.2 Solution #2: Discovery of User Plane service Cooperated with 3GPP LCS Features + +### 6.2.1 Introduction + +This solution addresses the KI "Key Issue #1: Architectural Enhancement to support User Plane positioning". + +The solution contains mainly two parts: + +1. User Plane feature support with compatibility with OMA standards [13][14] +2. User Plane service (re-)discovery compatible to TS 23.548 [10]. + +### 6.2.2 Functional Description + +As described in clause 5, User Plane positioning gives benefits including a simpler protocol stack, less overload, better performance, extra LPPE support, etc. When there is overloaded LCS signalling over N1 and/or NL1 interfaces, like massive emergency cases, LMF can offload the traffic to the user plane to enhance capacity. + +LMF can perform legacy 3GPP LCS features independently. User Plane features can also be used independently or cooperated with LMF using OMA User Plane specifications as specified in TS 23.271 [4] and TS 38.305 [6]. + +With many features defined by OMA, since UE can't take uplink measurements, to fulfil positioning methods like RTT, the User Plane has to cooperate with Control Plane LMF to collect both uplink and downlink measurements. + +User Plane cooperated with the 3GPP LCS control plane can be named 'LCUP' (LCs User Plane). + +![Figure 6.2.2-1: Network architecture diagram showing the interaction between various network functions (NRF, Other NF, UDM, EASDF) and the User Plane (UPF) for positioning. The diagram illustrates two LMF configurations: an Independent LMF and a Cooperated LMF and LCS User Plane (LCUP).](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +The diagram illustrates a 5G network architecture for positioning. At the top, four Network Functions (NFs) are connected to a Service Based Interface (SBI): NRF, Other NF, UDM, and EASDF. Below the SBI, four more NFs are connected: Independent LMF (via Nlmf), AMF (via Nanf), SMF (via Nsmf), and LMF (via Nlmf). The AMF is connected to the UE via N1 and to the (R)AN via N2. The (R)AN is connected to the UPF via N3. The UPF is connected to the DN via N6 and has a downward interface N9. The DN is connected to an Independent UP via Lup. A dashed box labeled 'Cooperated LMF and LCS User Plane' contains the LMF and LCUP. The LCUP is connected to the DN via Lup and to the UPF via N4. The LMF is connected to the UPF via N4. The UE is connected to the (R)AN via N1. + +Figure 6.2.2-1: Network architecture diagram showing the interaction between various network functions (NRF, Other NF, UDM, EASDF) and the User Plane (UPF) for positioning. The diagram illustrates two LMF configurations: an Independent LMF and a Cooperated LMF and LCS User Plane (LCUP). + +**Figure 6.2.2-1: LMF and LCUP can be deployed independently and can cooperate with each other** + +Independent/legacy LMF handles control plane requests as per legacy 3GPP LCS specifications. + +For independent User Plane entity, it could perform end to end location service (possibly following legacy OMA specifications) without 5GC impact: + +![Diagram showing the independent user plane architecture. A UE (User Equipment) is connected via a double-headed arrow to an Independent UP (User Plane), which is in turn connected via a double-headed arrow to an LCS Client.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +graph LR + UE[UE] <--> Independent_UP[Independent UP] + Independent_UP <--> LCS_Client[LCS Client] + +``` + +Diagram showing the independent user plane architecture. A UE (User Equipment) is connected via a double-headed arrow to an Independent UP (User Plane), which is in turn connected via a double-headed arrow to an LCS Client. + +**Figure 6.2.2-2: Independent user plane** + +Details of independent user plane function is out of this solution scope. + +In this solution, only user plane invoked by LMF to enhance the 3GPP 5G LCS procedures is referred as 'LCUP'. This solution makes it compatible that LCUP could also act as independent user plane while cooperating with LMF. For LCUP cooperated with LMF, it can achieve the following benefits: + +1. Both uplink and downlink measurements can be collected. +2. User Plane and Control Plane can have feature reusability, e.g. sharing the same algorithm calculation. + +NOTE 1: As per clause 5.1 of TS 38.305 [6], detailed cooperation interface between LMF and LCUP is out of the solution scope and could be implementation specific. + +To keep legacy LCS procedures' compatibility, for the cooperated LMF and LCUP instances, LMF should still perform the entry point and response route for 5GS LCS procedures, including MO-LR, MT-LR, Deferred MT-LR and regulatory-related positioning when user plane positioning is involved. + +Since there could be multiple LMF and LCUP instances, when LCUP cooperated with LMF, UE needs to discover the correct instance of LCUP. With 3GPP LCS MT-LR/NI-LR/MO-LR procedures, when AMF has selected an LMF instance - LMFi to serve an LCS request about a UE, when the UE establishes user plane interaction with an LCUP, the UE should perform user plane session with an LCUPi cooperated with LMFi. This means UE should discover the LCUP instance working with the serving LMF instance. + +For the cooperated case, LMF can perform the offload operation to switch the LPP traffic to User Plane. + +LMF can provide information to UE, and allows the UE to establish a secure UP connection to a proper LCUP over existing or new PDU session through the following options: + +1. LMF can send SUPL INIT to UE through OMA-defined push mechanisms and activate the UP session with its cooperated LCUP. +2. For LPP offload in Rel.18, it is straightforward that the LCUP related information be delivered over LPP itself. LMF can treat cooperated LCUP information and contents in SUPL INIT as part of assistance data in LPP provide assistance message. + - a. The provide assistance data message can be unsolicited or in response to a request assistance message from UE. + - b. The LPP offload instruction in the LCUP assistance can be imperative or instructive. Imperative means UE can choose to offload the traffic or receive failure; instructive means UE would better to offload the traffic but may still be served by LMF over control plane. +3. LMF can also provide LCUP information to AMF using Namf\_Communication\_N1N2MessageTransfer and AMF forward it to UE with DL NAS TRANSPORT. + +Besides the contents in SUPL INIT, LCUP assistance data can also include: + +1. The pre-provisioned or unique FQDN of the LCUP cooperating with serving LMF. +2. Security attributes of LCUP for TLS connection establishment. + +NOTE 2: The PDU session (or related DNN) may be used only for LCS UP connection. + +NOTE 3: If any security work with PDU session and/or User Plane connection needed, it should be handled by SA WG3. + +Meanwhile, LCUP service should only be provided to capable UEs. UE capability of User Plane can be exposed in a similar way as its legacy 3GPP LCS capability: + +1. The capabilities of a target UE to support user plane may be signalled by the UE to a serving PLMN or to an SNPN at the AS, NAS during registration of the UE. +2. Some of these positioning capabilities may be transferred subsequently to an LMF with enhanced LPP signalling. + +Such capability information could be transferred to LMF from: + +1. AMF in the DetermineLocation Request enhancement when UE provides the UP capability during registration. +2. LPP message to LMF in capabilities exchange. + +As per [13][14], UE could use pre-configured FQDN and/or runtime parameter(s) received in SUPL INIT as OMA compliant approach or LPP/NAS assistance as R18 enhancements to discover the LCUP. + +Since UE uses FQDN to discover the User Plane server, URSP, EASDF rules and different FQDN resolution can be used to locate the LCUP: + +1. As one of the Rel-18 enhanced options, each LCUP instance cooperated with the LMF can be assigned to a unique FQDN. LMF can provide the corresponding FQDN as part of the assistance data to the UE. UE can also retry the user plane in case of an overloaded error reply of the control plane request. +2. As OMA SUPL compliant option, for UEs which can only use provisioned (H-SLP) FQDN and related trusted certificate settings, before the traffic offload, the serving LMF can act as a (backend) DNS server and respond to the DNS query to reply the cooperated LCUP. + - a. If LCUP is bounded to certain area like in localized LCS, LMF can use the same serving cell identity to choose the LCUP as its cooperated instance. + - b. For the more specific cases that LMF is pre-configured with LCUP instance, after LMF offload instruction to UE. UE performs the LCUP DNS query. EASDF rules can attach UE IP in the ECS (EDNS Client Subnet) and forward the provisioned FQDN's DNS query to all related LMF instances. LMF could decide the DNS response by combining UP IP with information query from BSF or message contents from IMS. Only when UE IP in ECS exists in the serving UE IP list, the LMF would reply with its cooperated LCUP IP. Then UE can use the LCUP assistance delivered from serving LMF to establish User Plane session with the cooperated LCUP instance. + +In conclusion, the solution to the cooperation of LMF and LCUP can be summarized as follows: + +1. LMF performs the entry point and response route of LCS procedures +2. OAM provisions LMF with the assistance information (including FQDN, etc.) of its cooperated LCUP instance(s). +3. LMF provides LCUP assistance to UE either through OMA defined push mechanism or LPP/NAS assistance delivery +4. With knowledge of LCUP service, URSP configured in the UE may indicate which existing or new PDU session is used to establish the connection with LCUP. +5. With Edge DNS Client (EDC) functionality in the UE, EASDF rules has the flexibility to match the DNS query to correct LCUP provisioned to the cooperated LMF instance. + - a. When each cooperated LCUP can have its unique FQDN so that UE can have direct access, it could be pre-configured in LMF for all its LCUP assistance delivery. + - b. When applying DNS query feature to LMF, when triggered by MT/MO/NI procedures, after offload instruction, serving LMF can reply the DNS query with its cooperated LCUP assistance information based on either serving area or UE IP/identity. + +When LCUP is used with 3GPP LCS MT/NI/MO procedures, LMF can offload the LPP traffic to LCUP by the following options to activate UP connection from UE : + +1. LMF can use LPP assistance delivery containing LCUP information. +2. LMF can use OMA defined push mechanisms. This is compatible with legacy SUPL capability of UE. + +3. LMF can also use Namf\_Communication\_N1N2MessageTransfer to AMF which forwards LCUP info to UE with DL NAS TRANSPORT. + +After UE gets the cooperated LCUP assistance data of its serving LMF: + +1. UE starts LCUP DNS query either with pre-provisioned, or from OMA defined push mechanism or LPP assistance delivery: + - a. If the FQDN of LCUP could uniquely identify an LCUP instance, such instance would be the serving LCUP cooperated with the currently serving LMF. OAM can perform pre-provision. + - b. With localized LCS cases where LCUP and/or LMF are bounded to the serving area, LMF can use UE's serving cell ID to match its serving area and respond to DNS queries with its cooperated LCUP assistance information. + - c. LMF can also maintain serving UE IP list from BSF query or SIP IP header of SIP INVITE with co-location with LRF/RDF in emergency IMS call. LMF can use UE IP to match ECS in LCUP DNS query to know whether it is the serving LMF so that its cooperated LCUP assistance can be replied for the DNS query. +2. UE connects to the LCUP over the user plane through the N6 interface. +3. UE establishes TLS connection possibly with LCUP assistance data or pre-configured trusted certificates. +4. UE can start OMA specified SUPL positioning procedures besides the control plane MT/MO/NI procedures. + +## 6.2.3 Procedures + +### 6.2.3.1 LMF Offload traffic to Cooperated LCUP + +![Sequence diagram for LMF Offload traffic to Cooperated LCUP. The diagram shows interactions between UE, NG-RAN, AMF, LMF, LCUP, GMLC, UDM, and External Client. The LMF and LCUP are grouped together in a dashed box. The sequence starts with the External Client sending an LCS Service Request to the GMLC, which then sends a Nudm_UECM_Get Request to the UDM. The UDM responds with a Nudm_UECM_Get Response. The GMLC then sends a Namf_Location_ProvidePositioningInfo(UE UP Capable) to the AMF. The AMF triggers a Network Triggered Service Request to the UE. The UE responds with an LMF Selection Positioning. The AMF then sends an Nlmf_Location_DetermineLocation Request to the LMF. The LMF sends an LPP LCUP assistance for UE to offload to LCUP to the UE. The UE responds with 8a. UL position methods over NRPPa and 8b. DL position methods over LPP. The LMF then sends an Nlmf_Location_DetermineLocation Response to the AMF. The AMF sends a Namf_Location_ProvidePositioningInfo Response to the GMLC. Finally, the GMLC sends an LCS Service Response to the External Client.](356eb99ab9489bbd647223390a913903_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant LCUP + participant GMLC + participant UDM + participant External Client + + Note right of LMF: (LMF and LCUP are grouped) + + External Client->>GMLC: 1. LCS Service Request + GMLC->>UDM: 2. Nudm_UECM_Get Request + UDM-->>GMLC: 3. Nudm_UECM_Get Response + GMLC->>AMF: 4. Namf_Location_ProvidePositioningInfo(UE UP Capable) + Note left of AMF: 5. Network Triggered Service Request + AMF->>UE: 5. Network Triggered Service Request + UE-->>AMF: 6. LMF Selection Positioning + AMF->>LMF: 7. Nlmf_Location_DetermineLocation Request + LMF->>UE: 8. LPP LCUP assistance for UE to offload to LCUP + Note left of UE: 8a. UL position methods over NRPPa + UE-->>LMF: 8a. UL position methods over NRPPa + Note left of UE: 8b. DL position methods over LPP + UE-->>LMF: 8b. DL position methods over LPP + LMF->>AMF: 9. Nlmf_Location_DetermineLocation Response + AMF->>GMLC: 10. Namf_Location_ProvidePositioningInfo Response + GMLC->>External Client: 11. LCS Service Response + +``` + +Sequence diagram for LMF Offload traffic to Cooperated LCUP. The diagram shows interactions between UE, NG-RAN, AMF, LMF, LCUP, GMLC, UDM, and External Client. The LMF and LCUP are grouped together in a dashed box. The sequence starts with the External Client sending an LCS Service Request to the GMLC, which then sends a Nudm\_UECM\_Get Request to the UDM. The UDM responds with a Nudm\_UECM\_Get Response. The GMLC then sends a Namf\_Location\_ProvidePositioningInfo(UE UP Capable) to the AMF. The AMF triggers a Network Triggered Service Request to the UE. The UE responds with an LMF Selection Positioning. The AMF then sends an Nlmf\_Location\_DetermineLocation Request to the LMF. The LMF sends an LPP LCUP assistance for UE to offload to LCUP to the UE. The UE responds with 8a. UL position methods over NRPPa and 8b. DL position methods over LPP. The LMF then sends an Nlmf\_Location\_DetermineLocation Response to the AMF. The AMF sends a Namf\_Location\_ProvidePositioningInfo Response to the GMLC. Finally, the GMLC sends an LCS Service Response to the External Client. + +Figure 6.2.3.1-1: LMF offload traffic to cooperated LCUP + +1. The external location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or an SUPI. + +2. The GMLC invokes a Nudm\_UECM\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of this UE. +3. The UDM returns the network addresses of the current serving AMF. +4. The GMLC invokes the Namf\_Location\_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS, Supported GAD shapes and UE UP capability. +5. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [3] to establish a signaling connection with the UE. +6. The AMF selects an LMF based on the available information as defined in clause 5.1 or based on AMF local configuration. The LMF selection takes the 5G-AN currently serving the UE into account. The selection may use an NRF query. +7. The AMF invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE. +8. LMF offloads the LPP traffic to its cooperated LCUP by one of the methods in clause 6.2.2. + - 8.a The cooperated LMF can perform one or more of the positioning procedures with RAN defined by 3GPP. + - 8.b The cooperated LCUP can perform one or more of the positioning procedures with UE defined by OMA. + +NOTE: LPPe can be executed in step 8.b. + +9. The LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF with the combined result from cooperated LMF and LCUP. +10. The AMF returns the Namf\_Location\_ProvidePositioningInfo Response towards the GMLC/LRF. +11. The GMLC sends the location service response to the external location services client. + +### 6.2.3.2 LMF Activates UE with UP Connection to LCUP + +![Sequence diagram showing the interaction between UE, NG-RAN, LCUP, LMF, AMF, GMC, SMF, EASDF, PCF, and AF for LMF activation of UE with UP connection to LCUP.](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant LCUP + participant LMF + participant AMF + participant GMC + participant SMF + participant EASDF + participant PCF + participant AF + + Note right of LMF: 1. URSP as 4th rule in Table A-1 in TS 23.503 + PCF->>UE: 2. PCF Sends URSP rules to the UE per 23.502 § 4.16.11 / 4.16.12 and per 23.503 + Note right of LMF: 3. 5G LCS MT-LR/MO-LR/NI-LR as per TS 23.273 + LMF->>AMF: 4. Nlmf_Location_DetermineLocation with UE id + Note right of LMF: 4.a LMF may get UE ip from BSF query or from SIP header of GMLC/LRF in eme IMS call + AMF->>UE: 5.a.1 LPP Request Capability & Provide LCUP assistance + UE->>AMF: 5.a.2. LPP Provide Capability with UP capability + AMF->>LCUP: 5.b.1 Namf_Communication_N1N2MessageTransfer request capability & provides LCUP assistance + AMF->>UE: 5.b.2 DL_NAS_TRANSPORT for capability & LCUP assistance + UE->>AMF: 5.b.3 Provide Capability thru AMF + UE->>LCUP: 5.c.1 SUPL INIT + AMF->>SMF: 6. PDU Session reuse or establishment request to dnn+s-nssai corresponding to the URSP rule + Note right of SMF: 6.a selection, addition and control of EASDF per 23.548 + SMF->>UE: 7. PDU Session establishment completes + UE->>EASDF: 8. DNS request to get the LUCUP IP address & use EASDF rules as per TS 23.548 + Note right of LMF: 9.a.1 if FQDN is not unique, add UE IP in ECS and query all LMF with LCUP + LMF->>EASDF: 9.a.2 serving LMF matches UE ip and reply with its LCUP address + EASDF->>UE: 10. LCUP address either from config in DNS or LMF reply + UE->>LCUP: 11. UE contacts the LCUP and establishes a secured connection with the LCUP + UE->>LCUP: 5.c.2. SUPL POS INIT + +``` + +Sequence diagram showing the interaction between UE, NG-RAN, LCUP, LMF, AMF, GMC, SMF, EASDF, PCF, and AF for LMF activation of UE with UP connection to LCUP. + +Figure 6.2.3.2-1 + +1. URSP rules can be provisioned as an example in TS 23.503 [16]: + +| | | | +|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rule Precedence =4 | Route Selection Descriptor
Precedence =1
Network Slice Selection: S-NSSAI-a
DNN Selection: DNN_1
Access Type preference: Non-3GPP access | This URSP rule associates the application "App1" and the Connection Capabilities "internet" and "supl" with DNN_1, S-NSSAI-a over Non-3GPP access.

It enforces the following routing policy:
When the "App1" requests a network connection with Connection Capability "internet" or "supl", the UE establishes (if not already established) a PDU Session with DNN_1 and S-NSSAI-a over Non-3GPP access. After that, the UE routes the traffic of "App1" over this PDU Session. | +| Traffic Descriptor:
Application descriptor=App1

Connection Capabilities="internet", "supl" | | | + +2. URSP rules are applied to UE. +3. The start of 3GPP LCS procedures contained in TS 23.273 [5]. +4. Request comes to LMF with UE identity in inputData of Nlmf\_Location\_DetermineLocation request. When UE provides the user plane capability in registration, the request could take such capability in its parameters. + +- a. LMF can use UE id to query BSF for UE IP; in emergency IMS call, E-CSCF forwards SIP INVITE to GMLC/LRF. Through GMLC/LRF, LMF can also get the UE IP from SIP header of the SIP INVITE. + +NOTE 1: If authentication work needed, it should be handled by SA WG3. + +5. LMF gets UE user plane capability and provides LCUP information through either LPP or NAS. LMF can also reuse legacy 2G/3G/4G SUPL mechanisms by sending SUPL INIT to UE with attempts to activate user plane connection. + - a. LPP capability exchange is used to fetch UE user plane capability if Nlmf\_Location\_DetermineLocation doesn't show such capability; LMF can also use solicited or unsolicited assistance data delivery to transfer LCUP information to UE. + - b. In (rare) cases that UE doesn't support LPP but supports user plane, DL\_NAS\_TRANSPORT can be used to query UE user plane capability and delivery the LCUP assistance information. + - c. To be compatible with legacy SUPL implementation in UE, especially when LMF has knowledge of UE user plane capability by OAM provision or other means, LMF can use OMA defined push mechanisms and send SUPL INIT message to activate the user plane session. +- 6, 7, 8. PDU session and EASDF rule execution as per TS 23.548 [10]. +9. If FQDN in DNS query is uniquely mapped to one LCUP instance, the LCUP address is replied. This applies to cases when such FQDN is transferred from LMF to UE at step 5. But this may not apply to pre-provisioned H-SLP/E-SLP in UE. Such pre-configuration follows OMA SUPL specifications whose FQDN and trusted certificates override the runtime parameter transferred through step 5 or other means. + - a. If FQDN could be mapped to multiple LCUP instances (for example, different LCUP instances in different campus areas), EASDF attached UE address in ECS field and forward the DNS query to related LMF/LCUP instances. Since each LCUP and cooperated LMF can be configured with (e.g. local data network) address ranges, the serving LMF/LCUP instance could match UE address among its serving UE requests and reply its LCUP address. This address is the cooperated LCUP instance that UE should establish or resume user plane session. +10. DNS result is replied to UE. If the UE has previous TLS context with same FQDN, the TLS handshake workload can be minimized as per clause 6.1.1.4 in OMA-TS-ULP [14]. +11. UE continues to establish or resume secure user plane session. After secure connection established, user plane messages can be transferred, e.g. SUPL POS INIT for option c in step 5. + +NOTE 2: The discovery process in above activation procedures follows the EAS discovery and relocation defined in TS 23.548 [10]. It covers both the initial discovery of User Plane service for the UE and also the rediscovery process when UE needs to switch different User Plane services. + +## 6.2.4 Impacts on services, entities, and interfaces + +LMF: provides NAS, LPP assistance and acts as backend DNS server for LCS UP server instance. + +For UE compliant with user plane specified in TS 23.271 [4], TS 38.305 [6]: there is no mandatory changes needed. + +For UE with Rel-18 enhancement: there can be update to support DL\_NAS\_TRANSPORT and/or LPP assistance for User Plane assistance. + +## 6.3 Solution #3: User plane location capability transfer and positioning via user plane + +### 6.3.1 Introduction + +This solution addresses Key Issue #1 on Positioning via user plane transmission. + +In this solution, UE 'user plane location capability' can be regarded as a part of 5GMM capability or as a LPP sub-capability. If network determines to use user plane for positioning, the network should send the information (e.g. + +address information) of the LMF supporting user plane positioning functionality to UE to enable the user plane connection. + +## 6.3.2 Functional Description + +In this solution, we assume LMF is integrated with a user plane location function , to which UE needs to establish a user plane connection if user plane positioning is to be used. + +Before a UE establishes the user plane connection, it is required to send user plane location capability to the network so that the network knows that the UE supports positioning via user plane then can determine to use user plane for positioning. Thus, for the 'user plane location capability' awareness, UE can include its 'user plane location capability' as part of the '5GMM Capability' in the Registration Request message (Option 1) or the existing LPP capability transfer should cover the 'user plane location capability' indication (Option 2). + +During the MO or MT positioning procedure, after the network determines to use user plane positioning, the network should indicate the UE to use user plane for positioning with the address information of LMF. With the address information, UE can establish a secure connection with the LMF, and via this secure connection, position messages can be transferred between UE and the LMF. The established user plane connection may be reused for subsequent user plane position messages transmission triggered by UE or LMF, e.g. if UE does not move to a new place, does not have new QoS requirements and uses the same positioning method via the user plane. + +## 6.3.3 Procedures + +### 6.3.3.1 User plane location capability transfer + +During the MO-LR or MT-LR procedures, LMF may request the UE to provide the user plane location capability. Figure 6.3.3.1-1 presents the capability transfer procedure, the *ProvideCapabilities* message message described in TS 37.355 [15] should support to carry 'user plane location capability' indication. + +![Sequence diagram for Figure 6.3.3.1-1: Capability transfer. The diagram shows the interaction between UE, NG-RAN, AMF, SMF, UPF, LMF, GMLC, UDM, and LCS Client. The sequence of messages is: 1. Nlmf_Location_DetermineLocation Request from AMF to LMF; 2. Namf_Communication_N1N2MessageTransfer (DL Positioning Message: capability request) from LMF to AMF; 3. DL NAS TRANSPORT (DL Positioning Message: capability request) from AMF to UE; 4. UL NAS TRANSPORT (UL Positioning Message: capability response) from UE to AMF; 5. Namf_Communication_N1InfoNotify (UL Positioning Message: capability response) from AMF to LMF.](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant LMF + participant UE + Note left of AMF: 1. Nlmf_Location_DetermineLocation Request + AMF->>LMF: 1. Nlmf_Location_DetermineLocation Request + Note right of LMF: 2. Namf_Communication_N1N2MessageTransfer (DL Positioning Message: capability request) + LMF->>AMF: 2. Namf_Communication_N1N2MessageTransfer (DL Positioning Message: capability request) + Note left of AMF: 3. DL NAS TRANSPORT (DL Positioning Message: capability request) + AMF->>UE: 3. DL NAS TRANSPORT (DL Positioning Message: capability request) + Note right of UE: 4. UL NAS TRANSPORT (UL Positioning Message: capability response) + UE->>AMF: 4. UL NAS TRANSPORT (UL Positioning Message: capability response) + Note left of AMF: 5. Namf_Communication_N1InfoNotify (UL Positioning Message: capability response) + AMF->>LMF: 5. Namf_Communication_N1InfoNotify (UL Positioning Message: capability response) + +``` + +Sequence diagram for Figure 6.3.3.1-1: Capability transfer. The diagram shows the interaction between UE, NG-RAN, AMF, SMF, UPF, LMF, GMLC, UDM, and LCS Client. The sequence of messages is: 1. Nlmf\_Location\_DetermineLocation Request from AMF to LMF; 2. Namf\_Communication\_N1N2MessageTransfer (DL Positioning Message: capability request) from LMF to AMF; 3. DL NAS TRANSPORT (DL Positioning Message: capability request) from AMF to UE; 4. UL NAS TRANSPORT (UL Positioning Message: capability response) from UE to AMF; 5. Namf\_Communication\_N1InfoNotify (UL Positioning Message: capability response) from AMF to LMF. + +Figure 6.3.3.1-1: Capability transfer + +1. AMF sends Nlmf\_Location\_DetermineLocation Request to the LMF. +- 2-3. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF to request the transfer of a Downlink (DL) Positioning message to the UE. The Downlink Positioning message queries for the UE capabilities if the UE Positioning Capability is not received from AMF. The AMF forwards the Downlink Positioning message to the UE in a DL NAS TRANSPORT message. +- 4-5. UE provide its 'user plane location capability' indication in an Uplink Positioning message included in a NAS TRANSPORT message, if it supports user plane positioning method. + +### 6.3.3.2 5GC-MT-LR Procedure via user plane + +![Sequence diagram of 5GC-MT-LR Procedure via user plane showing interactions between UE, NG-RAN, AMF, SMF, UPF, LMF, GMLC, UDM, and LCS Client.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant LMF + participant GMLC + participant UDM + participant LCS Client + + Note over UE, UDM: 0a. UE Registration procedure in figure 4.2.2.2-1 of TS 23.502 [3] + AMF-->>UE: 0b. PDU session establishment trigger + Note over UE, UPF: 0c. PDU establishment Procedure + Note over UE, LCS Client: 23273. 6.1.2 step1~step10 + AMF->>LMF: 11. Nlmf_Location_DetermineLocation Request + LMF-->>UE: 12. capability request + UE-->>LMF: 13. capability provide(user plane location capability) + Note right of LMF: 14. Decides to utilize user plane + LMF->>AMF: 15. Namf_Communication_N1N2Transfer(User Plane positioning information) + AMF->>UE: 16. User Plane positioning information + Note over UE, UPF: 17. PDU establishment Procedure + UE->>AMF: 18. User Plane location Acknowledge + AMF->>LMF: 19. Namf_N1MessageNotify(User Plane location Acknowledge) + Note over UE, LMF: 20a. UE establishing secure user plane connection + Note over UE, LMF: 20b. UE Positioning via user Plane + LMF->>AMF: 21. Nlmf_Location_DetermineLocation Response + AMF->>GMLC: 22. Namf_Location_ProvidePositioningInfo Response + GMLC->>LCS Client: 23. LCS Service Response + AMF->>LMF: 24. Nlmf_Location_EventNotify + +``` + +Sequence diagram of 5GC-MT-LR Procedure via user plane showing interactions between UE, NG-RAN, AMF, SMF, UPF, LMF, GMLC, UDM, and LCS Client. + +**Figure 6.3.3.2-1: 5GC-MT-LR Procedure via user plane** + +- 0a. UE registration procedure in figure 4.2.2.2-1 of TS 23.502 [3]. If Option 1 for UE capability awareness is selected, UE include its 'user plane location capability' indication as part of the '5GMM Capability' in the Registration Request. +- 0b. [Conditional] AMF may trigger UE to establish a PDU session for later usage based on the capability of UE, UE location, and subscription information if 'user plane location capability' indication is received in step 0a. +- 0c. [Conditional] UE establishes a PDU session for positioning if receiving the trigger in step 0b. +- 1~10. Steps 1-10 of figure 6.1.2-1 in TS 23.273 [5]. For the step 10, if UE include its 'user plane location capability' indication as part of the '5GMM Capability' in the Registration Request (Option 1 for UE user plane location capability awareness), AMF selects a LMF supporting user plane location based on the capability information. +11. The AMF invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE, which carries the 'user plane location capability' information of UE if AMF received it in step 10. AMF also sends its notification URL to LMF in this message for subscription of secure user plane connection status. +- 12-13. [Conditional] Steps 2-5 of clause 6.3.3.1 for capability transfer, if Option 2 for UE user plane location capability awareness is used and LMF has not obtained the capability of UE. +14. Based on the 'user plane location capability' indication of the UE received in step 11 or step 12-13, the Positioning methods and modes the UE supports, the load of the control plane, service type, Client Type, deferred location type, required location QoS received in step 11, LMF decides whether to continue the position procedure via user plane. Steps 15-20a is skipped if there is already user plane connection context of the target UE in LMF. +15. [Conditional] If LMF decides to utilize user plane and there is no established secure user plane positioning for the UE, LMF sends a user plane positioning information to AMF to indicate UE to use user plane positioning. The user plane positioning information includes the FQDN or IP address of the LMF, the S-NSSAI and DNN for the PDU session used for user plane positioning, a temporary UE identifier and security related information. LMF may send a dedicated DNN for user plane connection. Also, the LMF may require the UE to report the IP + +address of the PDU session used for user plane positioning. If UE supports more than one positioning methods, LMF may also indicate UE which type of positioning methods should use the user plane connection, while others may still use the control plane (e.g. user plane for sensor method and control plane for NR-based positioning method). The user plane positioning information transfer can be based on NAS signalling or enhanced LPP. + +NOTE: LMF can select different positioning methods (e.g. motion sensor-based method) for the user plane and it is based on implementation and local configuration to determine which positioning method to use on user plane. + +Editor's note: The security mechanism and security information provided by LMF to UE is subject to SA WG3's work. + +16. [Conditional] When AMF receives the user plane information from LMF in step 15, AMF sends it to UE via a DL NAS TRANSPORT message. +17. [Conditional] The UE starts to establish a secure connection with LMF. If UE finds there is no suitable existing PDU session for user plane positioning, UE should establish a PDU session with the S-NSSAI and DNN received from the positioning information. SMF should select a UPF connecting with the LMF based on S-NSSAI, DNN (maybe a dedicated DNN), and UE location information, etc. +18. [Conditional] If the suitable PDU session exists, UE sends an acknowledgement to LMF through AMF via a UL NAS TRANSPORT message, to confirm that user plane position is chosen, and the IP address of the PDU session may also be included in the acknowledgement. If there is no suitable existing PDU session and the PDU session establishment failed in step 17, a failure indication should be included in the acknowledgement message. +19. [Conditional] AMF sends the acknowledgement received in step 18 to the LMF via Namf\_N1messageNotify service. +- 20a. UE establishes a secure user plane connection with LMF. +- 20b. LPP message can be transferred between UE and LMF for UE based positioning, UE assisted positioning and delivery of assistance data. If the user plane secure connection has been established, LMF directly sends LPP messages to UE. The message flow of step 20a and 20b is described in clause 6.3.3.4. +- 21~23. Steps 9~11 of figure 6.1.1-1 in TS 23.273 [5]. In step 21, LMF indicates AMF in the Nlmf\_Location\_DetermineLocation Response message that a user plane positioning method is used. AMF should store the indication information and LMF ID, which presents that there is a user plane connection between the UE and LMF. +24. UE and LMF may maintain the secure user plane connection for later message transfer via user plane. If UE or LMF release the connection, LMF should send an Nlmf\_Location\_EventNotify message to indicate AMF to release related resources. This step can occur at any time after step 21. + +## 6.3.3.2a Deferred 5GC-MT-LR Procedure via user plane + +![Sequence diagram for Deferred 5GC-MT-LR Procedure via user plane. The diagram shows interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, LCS Client, NEF, and AF. The procedure is divided into several steps: 0. Step 0a-0c in clause 6.3.3.2; 1. Step 1-13 of Deferred MT-LR Procedure in TS 23.273 Clause 6.3.1; 2. Nlmf_Location_DetermineLocation Request; 3. Capability Transfer; 3b. Decides to use user plane; 4. Namf_Communication_N1N2Transfert(User Plane positioning information); 5. User Plane positioning Information; 6. PDU Session Establishment Procedure; 7. User Plane Location ACK; 8. Namf_N1MessageNotify (Ack); 9a. Establishing secure user plane; 9b. UE Positioning via user plane; 10a. LCS Periodic-Triggered Invoke Request; 10b. LCS Periodic-Triggered Invoke Return Result; 10c. Nlmf_Location_DetermineLocation Response; 10d. Step 19-21 of Deferred MT-LR Procedure in TS 23.273 Clause 6.3.1; 11. Event Detected; 12. Location Measurements; 13. Event Report; 14. Event Report Acknowledgment; 15. UE Positioning via user plane; 16. Step 28-31 of Deferred MT-LR Procedure in TS 23.273 Clause 6.3.1.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Sequence diagram for Deferred 5GC-MT-LR Procedure via user plane. The diagram shows interactions between UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, LCS Client, NEF, and AF. The procedure is divided into several steps: 0. Step 0a-0c in clause 6.3.3.2; 1. Step 1-13 of Deferred MT-LR Procedure in TS 23.273 Clause 6.3.1; 2. Nlmf\_Location\_DetermineLocation Request; 3. Capability Transfer; 3b. Decides to use user plane; 4. Namf\_Communication\_N1N2Transfert(User Plane positioning information); 5. User Plane positioning Information; 6. PDU Session Establishment Procedure; 7. User Plane Location ACK; 8. Namf\_N1MessageNotify (Ack); 9a. Establishing secure user plane; 9b. UE Positioning via user plane; 10a. LCS Periodic-Triggered Invoke Request; 10b. LCS Periodic-Triggered Invoke Return Result; 10c. Nlmf\_Location\_DetermineLocation Response; 10d. Step 19-21 of Deferred MT-LR Procedure in TS 23.273 Clause 6.3.1; 11. Event Detected; 12. Location Measurements; 13. Event Report; 14. Event Report Acknowledgment; 15. UE Positioning via user plane; 16. Step 28-31 of Deferred MT-LR Procedure in TS 23.273 Clause 6.3.1. + +Figure 6.3.3.2a-1: Deferred 5GC-MT-LR via user plane + +0. Same with step 0a-0c in figure 6.3.3.2-1 of clause 6.3.3.2. +1. Steps 1-13 of Deferred MT-LR Procedure in clause 6.3.1 of TS 23.273 [5]. In step 13, AMF selects a LMF supporting user plane positioning based on UE capability if received 'user plane location' indication in step 0. +- 2-9. Same with steps 11-20 in clause 6.3.3.2. +- 10a-10c. Step 16-18 of Deferred MT-LR Procedure in clause 6.3.1 of TS 23.273 [5] with following differences: + - In step 18 (step 10c in this figure), LMF indicates AMF in the Nlmf\_Location\_DetermineLocation Response message that a user plane positioning method is used. AMF should store the indication information, which presents that there is a user plane connection between the UE and LMF. + - For UE available location event, after step 18, LMF may still maintain the user plane connection for later usage. + +- 10d. Steps 19-21 of Deferred MT-LR Procedure in clause 6.3.1 of TS 23.273 [5] with following difference: +- After step 19, besides storing UE user plane positioning context for periodic and triggered event report, AMF should maintain the secure user plane connection status of UE if LMF does not indicate AMF to release it. +- 11-15. Steps 16-21 of Deferred MT-LR Procedure in clause 6.3.1 of TS 23.273 [5] with following differences: +- The Event report of step 13-14 and step 15 for UE positioning are performed via user plane. + - To reduce the event report latency, LMF and UE may maintain the user plane connection thus UE will not be in CM-IDLE state. +- 16-17. Steps 28-31 of Deferred MT-LR Procedure in clause 6.3.1 of TS 23.273 [5]. + +### 6.3.3.2b Cancellation of Event Reporting + +Cancellation of event reporting can be initiated by the UE, H-GMLC or LCS Client or AF, using the control plane procedures defined in clauses 6.3.2 and 6.3.3 in TS 23.273 [5] with following differences: + +- LMF and UE may still maintain the secure user plane for later positioning session usage after Cancellation of Event Reporting for current positioning session. If LMF decides to release the secure user plane connection, or UE has released the secure user plane connection, LMF sends the Nlmf\_Location\_EventNotify message to AMF to release the stored information. + +### 6.3.3.3 5GC-MO-LR Procedure via user plane + +For MO-LR procedure, the user plane location capability may be included in the MO-LR request message, in this case there is no need for LMF to require UE to report its user plane capability if Option 2 for capability awareness is selected. After receiving the Nlmf\_Location\_DetermineLocation message, LMF determines whether to utilize user plane for UE positioning. + +Figure 6.3.3.2-2 presents the 5GC-MO-LR procedure via user plane, of which the principle is similar with 5GC-MT-LR Procedure via user plane. The difference is, in step 4, the user plane location capability can be carried by the Nlmf\_Location\_DetermineLocation message no matter whether Option 1 or Option 2 for UE capability awareness is selected. + +If the UE has received DNNs/S-NSSAIs used for user plane positioning and established corresponding PDU sessions from previous location procedure, it may directly interact with LMF via the user plane connection for MO-LR, if the requested location service type is either location estimate of the UE or location assistance data. If the MO-LR requesting location transfer to an LCS client or AF, the UE still should send the MO-LR request through AMF, but step 5~9 in figure 6.3.3.2-2 can be skipped after LMF determined to utilize user plane. + +![Sequence diagram for 5GC-MO-LR Procedure via user plane if there is no established user plane secure connection between UE and LMF. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, LMF, GMLC, UDM, and LCS Client. Steps include UE Triggered Service Request, UL NAS TRANSPORT (MO-LR Request), LMF Selection, Nlmf_Location_DetermineLocation Request, Determine to utilize user plane, Namf_Communication_N1N2Transfer, User Plane positioning information, PDU session establishment Procedure, User Plane location Acknowledge, Namf_Communication_N1Notify(Ack), Establishing Secure user Plane connection, UE Positioning via user Plane, Nlmf_Location_DetermineLocation Response, Namf_Location_ProvidePositioningInfo Response, and LCS service Response.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant LMF + participant GMLC + participant UDM + participant LCS Client + + Note left of UE: 1. UE Triggered Service Request + UE->>NG-RAN: 2. UL NAS TRANSPORT (MO-LR Request) + NG-RAN->>AMF: 3. LMF Selection + AMF->>LMF: 4. Nlmf_Location_DetermineLocation Request(Lpp message: user plane location capability) + Note right of LMF: 4b. Determine to utilize user plane + LMF->>AMF: 5. Namf_Communication_N1N2Transfer (User Plane positioning information) + AMF->>UE: 6. User Plane positioning information + Note left of UE: 7. PDU session establishment Procedure + UE->>AMF: 8. User Plane location Acknowledge + AMF->>LMF: 9. Namf_Communication_N1Notify(Ack) + Note over UE, LMF: 10a. Establishing Secure user Plane connection + Note over UE, LMF: 10b. UE Positioning via user Plane + LMF->>AMF: 11. Nlmf_Location_DetermineLocation Response + AMF->>GMLC: 12. Namf_Location_ProvidePositioningInfo Response + GMLC->>LCS Client: 13. LCS service Response + LMF->>AMF: 14. Nlmf_Location_EventNotify + +``` + +Sequence diagram for 5GC-MO-LR Procedure via user plane if there is no established user plane secure connection between UE and LMF. The diagram shows interactions between UE, NG-RAN, AMF, SMF, UPF, LMF, GMLC, UDM, and LCS Client. Steps include UE Triggered Service Request, UL NAS TRANSPORT (MO-LR Request), LMF Selection, Nlmf\_Location\_DetermineLocation Request, Determine to utilize user plane, Namf\_Communication\_N1N2Transfer, User Plane positioning information, PDU session establishment Procedure, User Plane location Acknowledge, Namf\_Communication\_N1Notify(Ack), Establishing Secure user Plane connection, UE Positioning via user Plane, Nlmf\_Location\_DetermineLocation Response, Namf\_Location\_ProvidePositioningInfo Response, and LCS service Response. + +**Figure 6.3.3.3-1: 5GC-MO-LR Procedure via user plane if there is no established user plane secure connection between UE and LMF** + +1-4. Similar with steps 1-4 in figure 6.2-1 of clause 6.2 of TS 23.273 [5]. The difference is that the 'user plane location capability' indication can be carried by the Nlmf\_Location\_DetermineLocation message in step 4 no matter whether Option 1 or Option 2 for UE capability awareness is selected. + +4b-14. Same with steps 15-24 in clause 6.3.3.2. + +### 6.3.3.4 LPP transfer via user plane + +This procedure presents the LPP Message transfer between UE and LMF via user plane. The LMF interacts with the UE in order to exchange location information applicable to UE assisted and UE based position methods. + +![Sequence diagram for UE assisted and UE based positioning via user plane. The diagram shows interactions between UE, NG-RAN, UPF, and LMF. Steps include Establishing secure connection, DL UP LPP TRANSFER (LPP Message), Positioning Measurements and/or Calculation, and UL UP LPP TRANSFER (LPP Message).](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant UPF + participant LMF + + Note over UE, LMF: 1. Establishing secure connection + LMF->>UPF: 2. DL UP LPP TRANSFER (LPP Message) + Note left of UE: 3. Positioning Measurements and/or Calculation + UE->>UPF: 4. UL UP LPP TRANSFER (LPP Message) + UPF->>LMF: + +``` + +Sequence diagram for UE assisted and UE based positioning via user plane. The diagram shows interactions between UE, NG-RAN, UPF, and LMF. Steps include Establishing secure connection, DL UP LPP TRANSFER (LPP Message), Positioning Measurements and/or Calculation, and UL UP LPP TRANSFER (LPP Message). + +**Figure 6.3.3.4-4: UE assisted and UE based positioning via user plane** + +1. Before the LPP message transfer, UE and LMF should have established a secure connection. +2. LMF send LPP Message to UE via DL UP LPP TRANSFER, which may request location information from the UE, provide assistance data to the UE or query for the UE capabilities. + +3. After receiving the downlink LPP message, the UE may store assistance data provided by LMF and/or performs positioning measurements and/or location computation. +4. UE may return location information or returns capabilities to LMF via uplink LPP message. + +**Editor's note:** The user plane transport protocol and security aspects for LPP re-use solution#1 and the conclusion of SA WG3. + +### 6.3.3.5 LMF Change Procedure with user plane positioning + +The LMF Change procedure supports change of a serving LMF during a deferred 5GC-MT-LR procedure for periodic, or triggered location events via user plane as described in clause 6.3.2.2.a. + +When there is no ongoing positioning sessions, AMF may also trigger the LMF re-selection to transfer the maintained secure user-plane connection to a new LMF. + +![Sequence diagram of LMF Change Procedure with user plane positioning. Lifelines: UE, (R)AN, AMF, LMF1, LMF2. The procedure involves determining a new LMF2, transferring user plane positioning information, establishing a secure connection with LMF2, and deleting the connection with LMF1.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant LMF1 + participant LMF2 + + Note right of AMF: 1. Determine new LMF2 + AMF->>LMF1: 2. Nlmf_Location_LMFRelocation(New LMF2) + Note right of LMF1: 3. Determine new LMF2 + LMF1->>AMF: 4. Namf_Communication_N1N2MessageTransfer (user plane positioning information) + AMF->>UE: 5. user plane positioning information + Note right of UE: 6. Establishing the secure connection with LMF2 and UE Positioning Procedure via user plane + UE->>AMF: 7. user plane location ACK + AMF->>LMF1: 8. Namf_Communication_N1MessageNotify (ACK) + LMF1->>LMF2: 9. Nlmf_Location_LocationContextTransfer Request + LMF2->>LMF1: 10. Nlmf_Location_LocationContextTransfer Response + LMF2->>AMF: 11. Namf_Communication_N1N2MessageTransfer (user plane positioning information) + AMF->>UE: 12. user plane positioning information + Note right of UE: 13. Deleting the secure connection with LMF1 and UE Positioning Procedure via user plane + +``` + +Sequence diagram of LMF Change Procedure with user plane positioning. Lifelines: UE, (R)AN, AMF, LMF1, LMF2. The procedure involves determining a new LMF2, transferring user plane positioning information, establishing a secure connection with LMF2, and deleting the connection with LMF1. + +**Figure 6.3.3.5-1: LMF Change Procedure with user plane positioning** + +1. [Conditional] At applicable Registration events, AMF may decide to reselect a new LMF as there is a MT-LR positioning session for periodic or triggered events report via user plane of UE or there is a secure user plane connection between UE and LMF. +2. [Conditional] AMF sends the Nlmf\_Location\_LMFRelocation request to LMF1, carrying the information of the selected new LMF2. +3. [Conditional] The old LMF1 may decide to use a new LMF2 for user plane positioning. + +- 4-5. If the old LMF1 decides to change LMF with user plane positioning, the old LMF1 sends a user plane positioning information message to AMF to include the information of new LMF2. +6. UE decides whether or not the old PDU Session associated with old LMF1 for user plane positioning can be reused for the new LMF2. If not, the UE establishes the new PDU session associated with the information of new LMF2. +- 7-8. UE sends a user plane positioning information message to AMF to acknowledge the update of new LMF2 information. +- 9-10. The old LMF1 performs context transfer and send the request to the new LMF2 selected in step 1 or step 3 as specified in steps 6-7 of clause 6.4 of TS 23.273 [5]. +- 11-12. After finishing the Location context switch, the new LMF2 sends a user plane positioning information message to AMF to indicate the accomplishment of LMF change with user plane positioning. AMF updates the routing information of serving LMF for the UE. +13. The UE utilizes the new LMF2 and PDU Session if possible for the transmission of Event report message and deletes the old PDU Session associated with the old LMF1 if possible. + +### 6.3.4 Impacts on services, entities, and interfaces + +The solution impact the following network functions: + +- UE supports to send user plane location capability to LMF, receives user plane positioning information from LMF, support setup and release of UP connection and supports to perform positioning via user plane location connection; +- LMF supports user plane location service and supports to transfer the user plane positioning information to UE. +- AMF supports to trigger UE to establish a PDU session for user plane positioning based on UE capability and store the secure user plane connection status of UE. + +## 6.4 Solution #4: Direct communication between LMF and RAN node + +### 6.4.1 Introduction + +This solution aims to address the key issues#2: enhanced positioning architecture for NPN deployment. Particularly this solution address the following questions: + +- How to realize low latency positioning procedure under NPN deployment. +- How to achieve reliable and secure location result delivery and exposure, e.g. UE location not exposed to the public network. + +### 6.4.2 Functional Description + +The following is the architecture figure in this solution. + +![Figure 6.4.2: Reference architecture for Location Services. The diagram shows the following components and interfaces: UE connected to AMF via N1; RAN node connected to UE and AMF via N2; AMF connected to UDM via N8, to LMF via NL1, and to GMLC via NL2; Local AMF connected to RAN node via N2 and to LMF via NL1; LMF connected to GMLC; GMLC connected to LCS Client via Le. The Local AMF is shown as an intermediate node between the RAN node and the LMF.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +graph TD + UE[UE] -- N1 --> AMF[AMF] + RAN[RAN node] -- N2 --> UE + RAN -- N2 --> AMF + AMF -- N8 --> UDM[UDM] + AMF -- NL1 --> LMF[LMF] + AMF -- NL2 --> GMLC[GMLC] + UDM -- NL6 --> GMLC + RAN -- N2 --> LocalAMF[Local AMF] + LocalAMF -- NL1 --> LMF + LMF --> GMLC + GMLC -- Le --> LCS((LCS Client)) + +``` + +Figure 6.4.2: Reference architecture for Location Services. The diagram shows the following components and interfaces: UE connected to AMF via N1; RAN node connected to UE and AMF via N2; AMF connected to UDM via N8, to LMF via NL1, and to GMLC via NL2; Local AMF connected to RAN node via N2 and to LMF via NL1; LMF connected to GMLC; GMLC connected to LCS Client via Le. The Local AMF is shown as an intermediate node between the RAN node and the LMF. + +**Figure 6.4.2: Reference architecture for Location Services** + +In this solution, the LMF communicates with the RAN node via a local AMF. The LMF exchanges Network Positioning Message with RAN for Non-UE Associated Network Assistance Data procedure, without going through the AMF. The LMF directly communicates with the GMLC to expose the UE location to GMLC directly without going through the AMF. For network assisted or network based positioning procedure, the LMF sends the Network Positioning Message(request) toward the RAN via the serving AMF. The RAN sends the Network Positioning Message(response or notification) towards LMF via the Local AMF. + +The interface between local AMF and LMF is NL1, as defined in TS 23.273 [5]. The local AMF needs not retain state information for Network Assisted Positioning procedure and Non-UE Associated Network Assistance Data procedure, e.g. can treat any response from NG-RAN as a separate non-associated transfer. + +The Local AMF supports the management of N2 interface, i.e. the TNL association between the RAN node and Local AMF. The TNL association between the RAN node and the local AMF is pre-established via configuration. The weight factor of TNL association with the Local AMF shall be set to zero so the RAN node shall not select the Local AMF for initial N2. + +Other functionalities supported by the serving AMF defined in TS 23.501 [2] may not be needed in local AMF. + +The GMLC notification address is provided from AMF to LMF. The LMF notifies the UE location estimation towards the GMLC directly. + +NOTE 1: This solution assumes that the LMF/Local AMF and the RAN node are in the same trusted domain. + +NOTE 2: In order to reduce the latency the local AMF and LMF can be deployed together. The local AMF address is local configured in the LMF. + +NOTE 3: The user plane based solution in KI#1 can be used for UE Assisted and UE Based Positioning. + +## 6.4.3 Procedures + +### 6.4.3.1 Network Assisted Positioning Procedure + +![Sequence diagram for Mobile Terminated Network Assisted Positioning Procedure. Lifelines: UE, RAN node, AMF, Local AMF, LMF, GMLC. The sequence shows 11 steps: 1. TNL association establishment (RAN node to Local AMF), 2. Namf_Location_ProvidePositioningInfo Request (GMLC to AMF), 3. Network initiated Service Request (AMF to UE), 4. Nlmf_Location_DetermineLocation Request (AMF to LMF), 5. Nlmf_Location_DetermineLocation Response (LMF to AMF), 6. Namf_Location_ProvidePositioningInfo Response (AMF to GMLC), 7. Namf_Communication_N1N2MessageTransfer (LMF to AMF), 8. DOWNLINK UE ASSOCIATED NRPPA TRANSPORT (AMF to RAN node), 9. UPLINK UE ASSOCIATED NRPPA TRANSPORT (RAN node to Local AMF), 10. Namf_Communication_N2InfoNotify (Local AMF to LMF), 11. Nlmf_Location_EventNotify (LMF to GMLC).](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN node + participant AMF + participant Local AMF + participant LMF + participant GMLC + + Note left of UE: 3. Network initiated Service Request + RAN node->>Local AMF: 1. TNL association establishment + GMLC->>AMF: 2. Namf_Location_ProvidePositioningInfo Request + AMF->>UE: 3. Network initiated Service Request + AMF->>LMF: 4. Nlmf_Location_DetermineLocation Request + LMF->>AMF: 5. Nlmf_Location_DetermineLocation Response + AMF->>GMLC: 6. Namf_Location_ProvidePositioningInfo Response + LMF->>AMF: 7. Namf_Communication_N1N2MessageTransfer + AMF->>RAN node: 8. DOWNLINK UE ASSOCIATED NRPPA TRANSPORT + RAN node->>Local AMF: 9. UPLINK UE ASSOCIATED NRPPA TRANSPORT + Local AMF->>LMF: 10. Namf_Communication_N2InfoNotify + LMF->>GMLC: 11. Nlmf_Location_EventNotify + +``` + +Sequence diagram for Mobile Terminated Network Assisted Positioning Procedure. Lifelines: UE, RAN node, AMF, Local AMF, LMF, GMLC. The sequence shows 11 steps: 1. TNL association establishment (RAN node to Local AMF), 2. Namf\_Location\_ProvidePositioningInfo Request (GMLC to AMF), 3. Network initiated Service Request (AMF to UE), 4. Nlmf\_Location\_DetermineLocation Request (AMF to LMF), 5. Nlmf\_Location\_DetermineLocation Response (LMF to AMF), 6. Namf\_Location\_ProvidePositioningInfo Response (AMF to GMLC), 7. Namf\_Communication\_N1N2MessageTransfer (LMF to AMF), 8. DOWNLINK UE ASSOCIATED NRPPA TRANSPORT (AMF to RAN node), 9. UPLINK UE ASSOCIATED NRPPA TRANSPORT (RAN node to Local AMF), 10. Namf\_Communication\_N2InfoNotify (Local AMF to LMF), 11. Nlmf\_Location\_EventNotify (LMF to GMLC). + +**Figure 6.4.3-1: Mobile Terminated Network Assisted Positioning Procedure** + +1. Based on configuration the TNL association may be pre-established between the RAN node and the Local AMF. +2. The GMLC invokes the *Namf\_Location\_ProvidePositioningInfo* service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS and Supported GAD shapes. +3. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [3] to establish a signalling connection with the UE. +4. The AMF selects the LMF and invokes the *Nlmf\_Location\_DetermineLocation* service operation towards the LMF to request the current location of the UE. This service operation may also include the GMLC notification address to receive the UE location. +5. The LMF response *Nlmf\_Location\_DetermineLocation* response. +6. The AMF response *Namf\_Location\_ProvidePositioningInfo* response with success indication. +7. The LMF sends a *Namf\_Communication\_N1N2MessageTransfer*(Network Positioning message) to the serving AMF. +8. The serving AMF sends *DOWNLINK UE ASSOCIATED NRPPA TRANSPORT* via the TNL association to the RAN node to request position related information from the RAN node. The N2 Transport message includes the Routing ID of the LMF. +9. The target RAN node determines the Local AMF based on the configuration or Routing ID of the LMF, and returns any position related information to the Local AMF in a Network Positioning message included in an *UPLINK UE ASSOCIATED NRPPA TRANSPORT* message. The N2 Transport message includes the Routing ID of the LMF received from the serving AMF. The AMF NGAP UE ID is set to one received from the serving AMF. +10. The Local AMF sends *Namf\_Communication\_N2InfoNotify*(Network Positioning message) to the LMF identified by the Routing ID. + +11. The LMF invokes the Nlmf\_Location\_EventNotify service operation towards the GMLC notification address received from AMF in step 4. + +### 6.4.3.2 Obtaining Non-UE Associated Network Assistance Data + +![Sequence diagram for Non-UE Associated Network Assistance Data procedure. The diagram shows three participants: RAN node, Local AMF, and LMF. The sequence of messages is: 1. TNL association establishment (dashed line between RAN node and Local AMF); 2. Namf_Communication_NonUeN2MessageTransfer (solid line from LMF to Local AMF); 3. DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT (solid line from Local AMF to RAN node); 4. UPLINK NON UE ASSOCIATED NRPPA TRANSPORT (solid line from RAN node to Local AMF); 5. Namf_Communication_N2InfoNotify (solid line from Local AMF to LMF).](34b047489058d6400b412cd0ae2334ba_img.jpg) + +``` + +sequenceDiagram + participant RAN node + participant Local AMF + participant LMF + Note left of RAN node: 1. TNL association establishment + RAN node-->>Local AMF: 1. TNL association establishment + Note right of LMF: 2. Namf_Communication_NonUeN2MessageTransfer + LMF->>Local AMF: 2. Namf_Communication_NonUeN2MessageTransfer + Note right of Local AMF: 3. DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT + Local AMF->>RAN node: 3. DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT + Note left of RAN node: 4. UPLINK NON UE ASSOCIATED NRPPA TRANSPORT + RAN node->>Local AMF: 4. UPLINK NON UE ASSOCIATED NRPPA TRANSPORT + Note right of Local AMF: 5. Namf_Communication_N2InfoNotify + Local AMF->>LMF: 5. Namf_Communication_N2InfoNotify + +``` + +Sequence diagram for Non-UE Associated Network Assistance Data procedure. The diagram shows three participants: RAN node, Local AMF, and LMF. The sequence of messages is: 1. TNL association establishment (dashed line between RAN node and Local AMF); 2. Namf\_Communication\_NonUeN2MessageTransfer (solid line from LMF to Local AMF); 3. DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT (solid line from Local AMF to RAN node); 4. UPLINK NON UE ASSOCIATED NRPPA TRANSPORT (solid line from RAN node to Local AMF); 5. Namf\_Communication\_N2InfoNotify (solid line from Local AMF to LMF). + +Figure 6.4.3.2: Non-UE Associated Network Assistance Data procedure + +1. Based on configuration the TNL association may be pre-established between the RAN node and the LMF/Local AMF. +2. The LMF decides the Local AMF and invokes Namf\_Communication\_NonUeN2MessageTransfer service operation in the Local AMF. 3. The Local AMF sends a Network Positioning message in the DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT message via the TNL association to the RAN node to request position related information from the RAN node. +4. The target RAN node returns any position related information to the LMF in a Network Positioning message included in an UPLINK NON UE ASSOCIATED NRPPA TRANSPORT message. +5. The Local AMF invokes the Namf\_Communication\_N2InfoNotify service operation to the LMF. + +### 6.4.4 Impacts on services, entities, and interfaces + +#### LMF: + +- Exchange the Non-UE associated Network Positioning message with RAN node via the Local AMF. +- Send the UE location directly to the GMLC. + +#### Local AMF: + +- Receives UE or non-UE associated Network Positioning message from the RAN node. +- Forward the UE or non-UE associated Network Positioning message towards the LMF identified by the Routing ID. + +#### RAN node: + +- Sends UE or non-UE associated Network Positioning message towards the Local AMF. + +## 6.5 Solution #5: LCS architecture with "any AMF" + +### 6.5.1 Introduction + +This solution is applicable to LCS procedure including MO-LR, MT-LR, and LDR. When network based positioning method is selected by LMF, the signalling between LMF and NG-RAN, LMF and GMLC, are not transmitted to the AMF in the public network. + +### 6.5.2 Functional Description + +Architecture for this solution is illustrated as below. + +![Figure 6.5.2-1: Architecture for NPN. The diagram shows a 'public network' containing an AMF connected to a UDM via an N8 interface. Below it, a 'campus network' contains a UE connected to NG-RAN 1 via a Uu interface. NG-RAN 1 is connected to the AMF via an N2 interface and to the LMF via an NL1 interface. NG-RAN 2 and NG-RAN 3 are also connected to the AMF via N2 interfaces and to the 'any AMF' via N2 interfaces. The 'any AMF' is connected to the LMF via an NL1 interface. The LMF is connected to the GMLC via an NLx interface. The GMLC is connected to an LCS client via an Le interface. There are also NL2 and NL6 interfaces between the AMF and the LMF/GMLC respectively.](50214d232017279410e9c9db8eb75119_img.jpg) + +Figure 6.5.2-1: Architecture for NPN. The diagram shows a 'public network' containing an AMF connected to a UDM via an N8 interface. Below it, a 'campus network' contains a UE connected to NG-RAN 1 via a Uu interface. NG-RAN 1 is connected to the AMF via an N2 interface and to the LMF via an NL1 interface. NG-RAN 2 and NG-RAN 3 are also connected to the AMF via N2 interfaces and to the 'any AMF' via N2 interfaces. The 'any AMF' is connected to the LMF via an NL1 interface. The LMF is connected to the GMLC via an NLx interface. The GMLC is connected to an LCS client via an Le interface. There are also NL2 and NL6 interfaces between the AMF and the LMF/GMLC respectively. + +**Figure 6.5.2-1: Architecture for NPN** + +When UE registers to the network, NG-RAN 1 is the serving RAN node for the UE. NG-RAN 1 shall select an AMF in the public network'. It is assumed, by means of configuration, that "any AMF" cannot be selected as the serving AMF of the UE. + +Multiple RAN nodes are deployed in the campus network. At a given time, only a certain RAN (e.g. RAN 1 in the figure) is the serving RAN of the UE. Other RAN nodes may be selected by the LMF to measure the UE positioning signal. + +It is assumed all RAN nodes in the campus network have TNL association and NG-AP connection with the "any AMF". + +Current LCS design assumes NG-RAN report UE measurement to AMF (NRPPa message) and then to LMF. Because the NG-AP message may not be cyphered, it is likely the information will be sniffed by other entity in the transport network, which leads to exposure concern. + +**It is proposed to update the NRPPa signalling as follows:** + +During the location request procedure, if network based positioning method is selected by LMF, for UE associated NRPPa signalling, it is transmitted via the serving AMF. For non UE associated NRPPa signalling, it is transmitted using "any AMF" deployed in the campus network. + +The description of using "any AMF" is specified in TS 38.305 [6]: + +*An LMF can interact with any gNB reachable from any of the AMFs with signalling access to the LMF in order to obtain location related information to support the NR RAT-Dependent positioning methods. The information can include timing information for the TRP in relation to either absolute GNSS time or timing of other TRPs and information about the supported cells and TRPs including PRS schedule.* + +*Signalling access between the LMF and gNB may be via any AMF with signalling access to both the LMF and gNB.* + +"any AMF" is an AMF defined in TS 23.501, and needs to support the following functionality in this solution. + +- handling of Namf\_nonUEN2message transfer service from LMF; +- NG-AP message encapsulation and decapsulation for UL and DL non UE associated NRPPa message. + +Other functionalities supported by the AMF may not be needed in "any AMF". + +NOTE 1: Based on configuration by the campus network, the NG-RAN(s) are configured with the "any AMF" address, and establish NG-AP association with the any AMF. + +Topology of NG-RAN, "any AMF" and LMF are configured by the operator. LMF is configured with "any AMF" address. NG-RAN nodes in the campus network establishes TNL association with "any AMF" in the campus network. + +NOTE 2: this solution is for the positioning procedure using UL positioning method. Regarding the positioning procedure using DL positioning method, solution#3 can be a candidate. + +## 6.5.3 Procedures + +### 6.5.3.1 Network Assisted Positioning Procedure + +Same as clause 6.11.2 of TS 23.273 [5]. + +The AMF illustrated in this call flow is the serving AMF of the UE. + +![Sequence diagram of the Network Assisted Positioning Procedure. The diagram shows four participants: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. Namf_Communication_N1N2MessageTransfer (Network Positioning Message) from LMF to AMF; 2. Network Triggered Service Request (dashed box) from AMF to NG-RAN; 3. N2 Transport (Network Positioning Message) from AMF to NG-RAN; 4. Obtain Measurements (solid box) from NG-RAN to AMF; 5. N2 Transport (Network Positioning Message) from AMF to NG-RAN; 6. Namf_Communication_N2InfoNotify (Network Positioning Message) from AMF to LMF.](9e5d66cdb5112ad5cab89552b126e4b9_img.jpg) + +``` +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note right of AMF: 2. Network Triggered Service Request + LMF->>AMF: 1. Namf_Communication_N1N2MessageTransfer (Network Positioning Message) + AMF->>NG-RAN: 2. Network Triggered Service Request + AMF->>NG-RAN: 3. N2 Transport (Network Positioning Message) + NG-RAN->>AMF: 4. Obtain Measurements + AMF->>NG-RAN: 5. N2 Transport (Network Positioning Message) + AMF->>LMF: 6. Namf_Communication_N2InfoNotify (Network Positioning Message) +``` + +Sequence diagram of the Network Assisted Positioning Procedure. The diagram shows four participants: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. Namf\_Communication\_N1N2MessageTransfer (Network Positioning Message) from LMF to AMF; 2. Network Triggered Service Request (dashed box) from AMF to NG-RAN; 3. N2 Transport (Network Positioning Message) from AMF to NG-RAN; 4. Obtain Measurements (solid box) from NG-RAN to AMF; 5. N2 Transport (Network Positioning Message) from AMF to NG-RAN; 6. Namf\_Communication\_N2InfoNotify (Network Positioning Message) from AMF to LMF. + +Figure 6.5.3.1-1: Network assisted positioning procedure + +### 6.5.3.2 Obtaining Non-UE Associated Network Assistance Data + +Same as clause 6.11.3 of TS 23.273 [5]. + +The AMF illustrated in this call flow is "any AMF" deployed in the campus network. LMF is configured with "any AMF" address. NG-RAN nodes in the campus network establishes TNL association with "any AMF" in the campus network. + +![Sequence diagram illustrating the process of obtaining non-UE associated network assistance data. The diagram shows four entities: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. Namf_Communication_NonUeN2MessageTransfer (Network Positioning Message) from AMF to NG-RAN; 2. N2 Transport (Network Positioning Message) from NG-RAN to AMF; 3. Obtain Measurements (a process box); 4. N2 Transport (Network Positioning Message) from AMF to NG-RAN; 5. Namf_Communication_NonUeN2InfoNotify (Network Positioning Message) from NG-RAN to LMF.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + Note right of NG-RAN: 3. Obtain Measurements + AMF->>NG-RAN: 1. Namf_Communication_NonUeN2MessageTransfer (Network Positioning Message) + NG-RAN->>AMF: 2. N2 Transport (Network Positioning Message) + AMF->>NG-RAN: 4. N2 Transport (Network Positioning Message) + NG-RAN->>LMF: 5. Namf_Communication_NonUeN2InfoNotify (Network Positioning Message) + +``` + +Sequence diagram illustrating the process of obtaining non-UE associated network assistance data. The diagram shows four entities: UE, NG-RAN, AMF, and LMF. The sequence of messages is: 1. Namf\_Communication\_NonUeN2MessageTransfer (Network Positioning Message) from AMF to NG-RAN; 2. N2 Transport (Network Positioning Message) from NG-RAN to AMF; 3. Obtain Measurements (a process box); 4. N2 Transport (Network Positioning Message) from AMF to NG-RAN; 5. Namf\_Communication\_NonUeN2InfoNotify (Network Positioning Message) from NG-RAN to LMF. + +Figure 6.5.3.2-1: Obtaining Non-UE associated network assistance data + +## 6.5.4 Impacts on services, entities, and interfaces + +LMF: + +- configured with "any AMF" address. +- if network based positioning method is selected by LMF, for UE associated NRPPa signalling, it is transmitted via the serving AMF. For non UE associated NRPPa signalling, it is transmitted using "any AMF" deployed in the campus network. + +NG-RAN: + +- establishes TNL association with "any AMF". + +## 6.6 Solution #6: LMF selection based on LMF ID + +### 6.6.1 Introduction + +This solution aims to address the key issues#3: Local Area Restriction for an LMF and GMLC. In this solution the LMF discovery and selection mechanism is enhanced to use LMF ID as input parameter. + +### 6.6.2 Functional Description + +In this solution, the GMLC is configured with an LMF ID of the LMF located within the same local area of the GMLC. The LMF may register itself in the NRF. The GMLC provides the LMF ID to AMF in Namf\_Location\_ProvidePositioningInfo service operation. The AMF uses the LMF ID to discover the LMF via NRF query or local configuration and invokes the Nlmf\_Location\_DetermineLocation service operation to request the current location of the UE. + +### 6.6.3 Procedures + +![Sequence diagram of the 5GC-MT-LR procedure. Lifelines: UE, NG-RAN, AMF, LMF, GMLC, UDM, External Client. The sequence starts with the External Client sending an LCS Service Request to the GMLC. The GMLC sends a Nudm_UECM_Get Request to the UDM, which returns a response. The GMLC then sends a Namf_Location_ProvidePositioningInfo Request to the AMF. The AMF initiates a Network Triggered Service Request to the UE (indicated by a dashed box). The AMF performs LMF Selection and sends an Nlmf_Location_DetermineLocation Request to the LMF. The LMF performs UE Positioning and returns a response to the AMF. The AMF sends a response to the GMLC, which finally sends an LCS Service Response to the External Client.](f142b022cfc716cd967297f027efe647_img.jpg) + +``` + +sequenceDiagram + participant External Client + participant GMLC + participant UDM + participant AMF + participant LMF + participant NG-RAN + participant UE + + Note right of External Client: 1. LCS Service Request + External Client->>GMLC: 1. LCS Service Request + Note right of GMLC: 2. Nudm_UECM_Get Request + GMLC->>UDM: 2. Nudm_UECM_Get Request + Note right of UDM: 3. Nudm_UECM_Get Response + UDM-->>GMLC: 3. Nudm_UECM_Get Response + Note right of GMLC: 4. Namf_Location_ProvidePositioningInfo Request + GMLC->>AMF: 4. Namf_Location_ProvidePositioningInfo Request + Note right of AMF: 5. Network Triggered Service Request + AMF-->>NG-RAN: 5. Network Triggered Service Request + Note right of NG-RAN: 6. LMF Selection + AMF->>LMF: 7. Nlmf_Location_DetermineLocation Request + Note right of LMF: 8. UE Positioning + LMF-->>AMF: 9. Nlmf_Location_DetermineLocation Response + Note right of AMF: 10. Namf_Location_ProvidePositioningInfo Response + AMF->>GMLC: 10. Namf_Location_ProvidePositioningInfo Response + Note right of GMLC: 11. LCS Service Response + GMLC-->>External Client: 11. LCS Service Response + +``` + +Sequence diagram of the 5GC-MT-LR procedure. Lifelines: UE, NG-RAN, AMF, LMF, GMLC, UDM, External Client. The sequence starts with the External Client sending an LCS Service Request to the GMLC. The GMLC sends a Nudm\_UECM\_Get Request to the UDM, which returns a response. The GMLC then sends a Namf\_Location\_ProvidePositioningInfo Request to the AMF. The AMF initiates a Network Triggered Service Request to the UE (indicated by a dashed box). The AMF performs LMF Selection and sends an Nlmf\_Location\_DetermineLocation Request to the LMF. The LMF performs UE Positioning and returns a response to the AMF. The AMF sends a response to the GMLC, which finally sends an LCS Service Response to the External Client. + +**Figure 6.6.3-1: 5GC-MT-LR procedure** + +1. The external location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or an SUPI. +2. The GMLC invokes a Nudm\_UECM\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of this UE. +3. The UDM returns the network addresses of the current serving AMF. +4. The GMLC invokes the Namf\_Location\_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS and Supported GAD shapes. The service operation may also include the LMF ID if it is configured in the GMLC. +5. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [3] to establish a signalling connection with the UE. +6. The AMF selects the LMF based on the LMF ID received from GMLC. The selection may use a NRF query or local configuration. +- 7-11. Same steps 7-11 in clause 6.1.1 of TS 23.273 [5]. + +### 6.6.4 Impacts on existing entities and interfaces + +GMLC: + +- Configured with LMF ID in the same location area. +- Send the LMF ID to AMF in Namf\_Location\_ProvidePositioningInfo service operation. + +AMF: + +- Select the LMF according to the LMF ID received from the GMLC. + +## 6.7 Solution #7: LMF selection based on client or AF identifier + +### 6.7.1 Introduction + +This solution is to address KI#3: Local Area Restriction for an LMF and GMLC. + +LMF selection functionality is used by the AMF to determine an LMF for location estimation of the target UE. In some local cases, operators may deploy specific LMF and GMLC for enterprises for some customized or privacy requirements. But the UEs of different enterprises may share the same AMF or AMF pool. In order to select the right LMF for specific enterprise, AMF could use new identifiers which can map between enterprise and specific LMF. + +### 6.7.2 Functional Description + +Based on the scenarios mentioned above, AMF may use client identifiers or AF identifiers as one of the additional factors during the LMF selection, as specified in clause 5.1 in TS 23.273 [5]. The client and AF request the location information of the target UE, whose identifiers are assigned by the operator. The selection policy can be configured locally at AMF, or by querying NRF. + +If the LMF selection is performed at the AMF by querying NRF, LMF shall register with the client or AF identifier(s) that the LMF can serve. + +### 6.7.3 Procedures + +N/A. + +### 6.7.4 Impacts on services, entities, and interfaces + +AMF: + +- Take AF or client identifier(s) into account during the LMF selection. + +AF: + +- Provide the AF identifier(s) in location service procedures. + +UE: + +- Provide the client or AF identifier(s) to AMF in location service procedures. + +LMF: + +- Register in NRF with serving AF or client identifier(s). + +## 6.8 Solution #8: LMF Selection based on GMLC service area + +### 6.8.1 Introduction + +This solution addresses KI#3: Local Area Restriction for an LMF and GMLC. + +### 6.8.2 Functional Description + +The existing LMF selection mechanism is re-used with the following enhancements: + +- When AMF selects LMF: a new factor considered for LMF selection is added, i.e. GMLC service area consisting of one or more TA(s) which is locally configured in AMF. + +- When AMF selects target LMF: if the GMLC is restricted to supporting local services in a local area, it selects target LMF able to support location in the same local area. + +### 6.8.3 Procedures + +The existing LMF Change Procedure in clause 6.4 in TS 23.273 [5] is re-used. + +### 6.8.4 Impacts on services, entities, and interfaces + +AMF: + +- Consider GMLCS service area when selecting LMF. + +LMF: + +- If the LMF is restricted to supporting local services in a local area, it selects target LMF in the same local area. + +## 6.9 Solution #9: local LMF and GMLC selection + +### 6.9.1 Introduction + +This solution enables dedicated LMF and GMLC selection for the UE positioning in the local network. The solution addresses key issue 1 and key issue 3. + +### 6.9.2 Functional Description + +Three options are proposed for the AMF to select a local LMF and local GMLC: + +- Based on operator's configuration. An example could be a mapping table of UE identity e.g. GPSI and LMF/GMLC address is stored at AMF. +- Fetch from UDM, UE LCS subscription storing its serving local LMF and local GMLC address. +- UE LCS subscription data indicate a set of parameters including the dedicated DNN, UPF, and LMF/GMLC. When retrieved by AMF, User Plane positioning is determined for UE positioning. AMF triggers the PDU session establishment by indicating SMF with the UPF, and LMF/GMLC identifier. For example, in solution#3 step 0c, when AMF receives the PDU session request from UE, AMF includes the UPF, and LMF/GMLC identifier to the SMF, when invoking a Nsmf\_session create service operation. + +### 6.9.3 Procedures + +#### 6.9.3.1 5GC-MT-LR Procedure for the commercial location service + +Is clause 6.1.2 of TS 23.273 [5]. + +![Sequence diagram showing the Local LMF selection during 5GC-MT-LR procedure for the commercial location service. The diagram involves ten lifelines: UE, NG-RAN, AMF, LMF, VGMLC, HGMLC, UDM, LCS Client, NEF, and AF. The procedure starts with the LCS Client sending an LCS Service Request to the HGMLC. The HGMLC then interacts with the UDM (Nudm_SDM_Get, Nudm_UECM_Get) and the NEF (Nnef_EventExposure_Subscribe). The HGMLC sends a Location_ProvideLocation Request to the VGMLC, which in turn sends a Namf_Location_ProvidePositioningInfo Request to the AMF. The AMF then triggers a Network Triggered Service Request to the UE via the NG-RAN. The UE responds with a NAS Location Notification. The AMF then performs LMF Selection (step 10) and sends an Nlmf_Location_DetermineLocation Request to the LMF. The LMF performs UE Positioning (step 12) and returns a response to the AMF. The AMF then sends a response to the VGMLC, which sends a response to the HGMLC. The HGMLC performs a Privacy Check (step 16) and sends a Location_ProvideLocation Request to the AMF. The AMF triggers another Network Triggered Service Request to the UE. The UE responds with a NAS Location Notification. The AMF then sends a response to the VGMLC, which sends a response to the HGMLC. The HGMLC sends an LCS Service Response to the LCS Client. Finally, the HGMLC sends a response to the NEF, which sends a notification to the AF.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant HGMLC + participant UDM + participant NEF + participant VGMLC + participant AMF + participant LMF + participant NG-RAN + participant UE + participant AF + + Note right of LCS Client: 1a. LCS Service Request + LCS Client->>HGMLC: 1a. LCS Service Request + Note right of HGMLC: 1b-1. Nnef_EventExposure_Subscribe + HGMLC->>NEF: 1b-1. Nnef_EventExposure_Subscribe + Note right of HGMLC: 1b-2. Ngmlc_Location_ProvideLocation Request + HGMLC->>VGMLC: 1b-2. Ngmlc_Location_ProvideLocation Request + Note right of HGMLC: 2. Nudm_SDM_Get + HGMLC->>UDM: 2. Nudm_SDM_Get + Note right of HGMLC: 3. Nudm_UECM_Get + HGMLC->>UDM: 3. Nudm_UECM_Get + Note right of HGMLC: 4. Ngmlc_Location_ProvideLocation Request + HGMLC->>VGMLC: 4. Ngmlc_Location_ProvideLocation Request + Note right of VGMLC: 5. Namf_Location_ProvidePositioningInfo Request + VGMLC->>AMF: 5. Namf_Location_ProvidePositioningInfo Request + Note right of AMF: 6. Network Triggered Service Request + AMF->>NG-RAN: 6. Network Triggered Service Request + Note right of NG-RAN: 7. NAS Location Notification Invoke Request + NG-RAN->>UE: 7. NAS Location Notification Invoke Request + Note right of UE: 8. NAS Location Notification Return Result + UE->>NG-RAN: 8. NAS Location Notification Return Result + Note right of NG-RAN: 9. Nudm_ParameterProvision_Update + NG-RAN->>AMF: 9. Nudm_ParameterProvision_Update + Note right of AMF: 10. LMF Selection + AMF->>LMF: 11. Nlmf_Location_DetermineLocation Request + Note right of LMF: 12. UE Positioning + LMF->>AMF: 13. Nlmf_Location_DetermineLocation Response + Note right of AMF: 14. Namf_Location_ProvidePositioningInfo Response + AMF->>VGMLC: 14. Namf_Location_ProvidePositioningInfo Response + Note right of VGMLC: 15. Ngmlc_Location_ProvideLocation Response + VGMLC->>HGMLC: 15. Ngmlc_Location_ProvideLocation Response + Note right of HGMLC: 16. Privacy Check + HGMLC->>AMF: 17. Ngmlc_Location_ProvideLocation Request + Note right of AMF: 18. Namf_Location_ProvidePositioningInfo Request + AMF->>NG-RAN: 18. Namf_Location_ProvidePositioningInfo Request + Note right of AMF: 19. Network Triggered Service Request + AMF->>NG-RAN: 19. Network Triggered Service Request + Note right of NG-RAN: 20. NAS Location Notification Invoke Request + NG-RAN->>UE: 20. NAS Location Notification Invoke Request + Note right of UE: 21. NAS Location Notification Return Result + UE->>NG-RAN: 21. NAS Location Notification Return Result + Note right of NG-RAN: 22. Namf_Location_ProvidePositioning Response + NG-RAN->>AMF: 22. Namf_Location_ProvidePositioning Response + Note right of AMF: 23. Ngmlc_Location_ProvideLocation Response + AMF->>VGMLC: 23. Ngmlc_Location_ProvideLocation Response + Note right of VGMLC: 24a. LCS Service Response + VGMLC->>HGMLC: 24a. LCS Service Response + Note right of HGMLC: 24b-1. Ngmlc_Location_ProvideLocation Response + HGMLC->>NEF: 24b-1. Ngmlc_Location_ProvideLocation Response + Note right of HGMLC: 24b-2. Nnef_EventExposure_Notify + HGMLC->>AF: 24b-2. Nnef_EventExposure_Notify + +``` + +Sequence diagram showing the Local LMF selection during 5GC-MT-LR procedure for the commercial location service. The diagram involves ten lifelines: UE, NG-RAN, AMF, LMF, VGMLC, HGMLC, UDM, LCS Client, NEF, and AF. The procedure starts with the LCS Client sending an LCS Service Request to the HGMLC. The HGMLC then interacts with the UDM (Nudm\_SDM\_Get, Nudm\_UECM\_Get) and the NEF (Nnef\_EventExposure\_Subscribe). The HGMLC sends a Location\_ProvideLocation Request to the VGMLC, which in turn sends a Namf\_Location\_ProvidePositioningInfo Request to the AMF. The AMF then triggers a Network Triggered Service Request to the UE via the NG-RAN. The UE responds with a NAS Location Notification. The AMF then performs LMF Selection (step 10) and sends an Nlmf\_Location\_DetermineLocation Request to the LMF. The LMF performs UE Positioning (step 12) and returns a response to the AMF. The AMF then sends a response to the VGMLC, which sends a response to the HGMLC. The HGMLC performs a Privacy Check (step 16) and sends a Location\_ProvideLocation Request to the AMF. The AMF triggers another Network Triggered Service Request to the UE. The UE responds with a NAS Location Notification. The AMF then sends a response to the VGMLC, which sends a response to the HGMLC. The HGMLC sends an LCS Service Response to the LCS Client. Finally, the HGMLC sends a response to the NEF, which sends a notification to the AF. + +**Figure 6.9.3.1-1: Local LMF selection during 5GC-MT-LR procedure for the commercial location service** + +Other steps are same as in TS 23.273 [5], except step 10: + +10. AMF, based on local configuration, e.g. mapping table mapping table of UE identity e.g. MSISDN and LMF address, or the UE LCS subscription data where includes a dedicated LMF ID, selects an LMF. + +### 6.9.3.2 integration with user plane positioning + +During the UE initial registration procedure, AMF retrieves the UE LCS subscriber data from UDM. If the subscriber data includes the DNN, UPF, and LMF/GMLC, AMF determines to trigger the PDU session establishment for user plane positioning using these parameters. Procedures are described in solution#3. + +## 6.9.4 Impacts on services, entities, and interfaces + +### AMF: + +- configured locally, a mapping table of UE identity e.g. MSISDN and LMF/GMLC address is stored at AMF. +- Fetch from UDM, UE LCS subscription storing its serving local LMF and local GMLC address. +- Determine the LMF for the location request. + +### UDM: + +- Stores UE LCS subscriber data including: + - serving local LMF and local GMLC address; + - a set of parameters including the dedicated DNN, UPF, and LMF/GMLC. + +## 6.10 Solution #10: Support interaction between location service and NWDAF + +### 6.10.1 Introduction + +This solution addresses KI#4: Interaction between Location Service and NWDAF. + +### 6.10.2 Functional Description + +This solution reuses the existing architecture and interfaces to support interaction between location service and NWDAF: + +- Based on description in clause 4.3.2 of TS 23.273 [5], the LCS service supports NFs to access LCS services from a GMLC. So the Ngmlc interface is re-used when NWDAF obtains UE location by invoking LCS services. +- Based on description in clause 4.2.0 of TS 23.288 [9], any 5GC NF can request network analytics information from NWDAF. So the Nnwdaf interface is re-used when LMF obtains data analytics from the NWDAF. In this solution, the LMF selects positioning method based on WLAN performance analytics from the NWDAF. +- The existing privacy check mechanism is re-used with enhancements of introducing the following new LCS Client Type and Service Type which are used by NWDAF to request UE location: + - new LCS Client Types for PLMN Operator Class: + - NWDAF client in the HPLMN (when the UE is currently being served by the HPLMN); + - NWDAF client in the VPLMN ; + - exempted NWDAF client in the HPLMN (when the UE is currently being served by the HPLMN); + - exempted NWDAF client in the VPLMN. + +NOTE: For the exempted NWDAF client in the HPLMN and the exempted NWDAF client in the VPLMN, which may indicate the privacy check is performed on the NWDAF side, then the privacy check procedure in LCS will be skipped in some scenarios with the signalling reduction purpose. Performing the privacy check on the NWDAF side needs coordination work with eNA\_Ph3. + +- new standardized Service Type for Tracking Services: + - Analytics; + - Model training. +- The NWDAF may invoke LCS services for a SUPI, a list of SUPI or an internal group identifier. The NWDAF determines the identifier as described in TS 23.288 [9]. + +## 6.10.3 Procedures + +### 6.10.3.1 NWDAF accesses location service + +![Sequence diagram showing the interaction between UE, NG-RAN, LMF, AMF, GMLC, and NWDAF. The NWDAF sends a request to the GMLC, which then performs a location procedure (steps 2-23 or 2-29) involving the AMF, LMF, and NG-RAN, and finally returns a response to the NWDAF.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant LMF + participant AMF + participant GMLC + participant NWDAF + + Note right of GMLC: 1. Ngmlc_Location_ProvideLocation Request + Note left of GMLC: 2. Steps 2-23 in clause 6.1.2 or steps 2-29 in clause 6.3.1 or the procedure in clause 6.8 in TS 23.273 + Note right of GMLC: 3. Ngmlc_Location_ProvideLocation Response + +``` + +Sequence diagram showing the interaction between UE, NG-RAN, LMF, AMF, GMLC, and NWDAF. The NWDAF sends a request to the GMLC, which then performs a location procedure (steps 2-23 or 2-29) involving the AMF, LMF, and NG-RAN, and finally returns a response to the NWDAF. + +**Figure 6.10.3.1-1: NWDAF accesses location service based on existing mechanism** + +1. NWDAF invokes Ngmlc\_Location\_ProvideLocation Request to GMLC. + +The NWDAF includes the LCS Client Type, Service Type, LCS QoS and UE identifier in the Request. + +The LCS Client Type is NWDAF client in the HPLMN (when the UE is currently being served by the HPLMN) or NWDAF client in the VPLMN. The Service Type is analytics or model training. The UE identifier is SUPI, SUPI list or an internal group identifier. + +If the NWDAF requests location of any UE within an Area of Interest, it provides the Area of Interest instead of UE identifier. + +2. The GMLC performs steps 2-23 in clause 6.1.2, or steps 2-29 in clause 6.3.1, or triggers the procedure in clause 6.8 of TS 23.273 [5]. + +If the UE identifier is SUPI, the GMLC performs steps 2-23 in clause 6.1.2, or steps 2-29 in clause 6.3.1 of TS 23.273 [5]. If the UE identifier is SUPI list, the GMLC performs the procedure above for each SUPI in the list. If the UE identifier is an internal group identifier, the GMLC performs the procedure in clause 6.8 of TS 23.273 [5]. + +If the NWDAF provides an Area of Interest in step 1, the GMLC obtains from AMF a list of UEs located within the Area of Interest and then performs step 2. + +3. The GMLC sends Ngmlc\_Location\_ProvideLocation Response to NWDAF. + +### 6.10.3.2 LMF obtains data analytics from NWDAF + +The procedure in clause 6.11.4 of TS 23.288 [9] can be re-used. + +## 6.10.4 Impacts on services, entities, and interfaces + +### LMF: + +- Selects positioning method based on data analytics from NWDAF. + +### GMLC: + +- If the UE identifier is SUPI list in the Ngmlc\_Location\_ProvideLocation Request, the GMLC triggers the existing positioning procedure for each SUPI in the list. + +## 6.11 Solution #11: Interaction Enhancement between LCS and NWDAF + +### 6.11.1 Introduction + +This solution addresses the KI "Key Issue #4: Interaction between Location Service and NWDAF". + +### 6.11.2 Functional Description + +TS 23.273 [5] defines LCS QoS to have the following attributes: + +- Location Accuracy. +- Response time. +- QoS Class. + +Among these, the QoS Class attribute gives the requirement on the other attributes like accuracy or response time. It could take values Best Effort, Multiple QoS Class or Assured. While the Best Effort class is the least stringent one, the other two require the LMF to determine how accurate its location estimate is. + +For example: + +- In the case of "Multiple QoS Class", if the accuracy is less than what is required, the LMF shall rerun the estimate with more measurements etc. to achieve the accuracy required. +- In the case of "Assured" QoS Class, the procedure fails if the accuracy required is not met. + +This is a data analytics-based solution that shall run in the NWDAF where a Machine Learning model is trained using data like positioning estimate, positioning method used, assistance data, UE ID, time of the day etc. and corresponding accuracy. This model is then subsequently used by the LMF to determine if its location estimate meets the accuracy required and take appropriate action. To enable this, the LMF makes use of a Service Based API that is exposed by the NWDAF. + +### 6.11.3 Procedure + +![Sequence diagram titled 'ML Based Positioning Accuracy' showing interactions between UE, NG_RAN, NWDAF, LMF, and LCS_Client. The diagram illustrates a process where the LMF uses the NWDAF's ML model to ensure location accuracy. Steps include: 1. LMF subscribes to Analytics ID for Location Accuracy. 2. NWDAF performs offline training of supervised ML model using labeled data (e.g., MDT data from OAM). 3. LCS_Client requests UE location with specific QoS (Multiple QoS Class or Assured). 4. LMF initiates LCS session with NG-RAN and UE to estimate location. 5. LMF invokes NWDAF API for Analytics Info, which uses the trained ML model to infer location accuracy. 6. LMF compares returned accuracy with required accuracy. 7. If accuracy is not met, LMF may re-run the LCS session with changed assistance data. 8. LMF returns the location estimate with desired accuracy.](4b8c5ecb492fd759c766fe8950fafe67_img.jpg) + +**ML Based Positioning Accuracy** + +``` + +sequenceDiagram + participant UE + participant NG_RAN + participant NWDAF + participant LMF + participant LCS_Client + + Note right of LMF: Step 0.1: LMF invokes NWDAF API to subscribe to the Analytics ID corresponding to Location Accuracy for a given target area + Note left of NWDAF: Step 0.2: The NWDAF performs the offline training of supervised ML model using labeled data collected from eg. MDT data from OAM + + Note right of LCS_Client: Step 1: Client requests for UE location with QoS->QoS_Class="Multiple QoS Class" or "Assured" + Note right of LMF: Step 2: LMF initiates LCS session with the NG-RAN and UE and estimates the UE location + Note right of LMF: Step 3: LMF invokes NWDAF API for Analytics Info - it gives the subscribed Analytics ID, location estimate and other parameters like UE ID, time of the day to NWDAF. NWDAF uses the trained ML model to infer location accuracy and returns the the same to LMF + Note right of LMF: Step 4: LMF compares the returned accuracy with the required accuracy in the Location QoS + Note right of LMF: Step 5: If the accuracy is not met, LMF may re-run the LCS Session with changed assistance data (higher periodicity, different set of TRPs to measure etc.) + Note right of LMF: Step 6: LMF returns the location estimate with the desired accuracy + +``` + +Sequence diagram titled 'ML Based Positioning Accuracy' showing interactions between UE, NG\_RAN, NWDAF, LMF, and LCS\_Client. The diagram illustrates a process where the LMF uses the NWDAF's ML model to ensure location accuracy. Steps include: 1. LMF subscribes to Analytics ID for Location Accuracy. 2. NWDAF performs offline training of supervised ML model using labeled data (e.g., MDT data from OAM). 3. LCS\_Client requests UE location with specific QoS (Multiple QoS Class or Assured). 4. LMF initiates LCS session with NG-RAN and UE to estimate location. 5. LMF invokes NWDAF API for Analytics Info, which uses the trained ML model to infer location accuracy. 6. LMF compares returned accuracy with required accuracy. 7. If accuracy is not met, LMF may re-run the LCS session with changed assistance data. 8. LMF returns the location estimate with desired accuracy. + +**Figure 6.11.3-1: ML based positioning accuracy** + +Step 0.1: The LMF invokes NWDAF API to subscribe to the Analytics ID corresponding to Location Accuracy for a given target area, this acts as a trigger for the NWDAF to do the offline training of the corresponding ML model. + +**Editor's note:** Whether to use new Analytics ID or reuse existing one is FFS and may need to be decided in coordination with eNA\_ph3. + +Step 0.2: The NWDAF performs the offline training of the model using supervised data. It may also access labelled data collected from eg.MDT for its training purposes. The training is complete waiting for analytics request from the LMF for that Analytics ID. + +Step 1: LCS Client requests UE location with QoS Class as either "Multiple QoS Class" or "Assured" along with the location accuracy required. The expected behaviour from the LMF is as given in clause 6.11.2. + +Step 2: The LMF initiates the LCS session as given in TS 23.273 [5] and derives the UE location estimate + +Step 3: The LMF then queries the NWDAF for the location estimate accuracy giving as inputs the subscribed Analytics ID, location estimate and other parameters like UE ID, assistance data, time of the day etc. The NWDAF uses the corresponding model trained in Step: 0.2 and provides the location accuracy as the output to the LMF. + +NOTE 1: The training done in step 0.2 gives the ML model the ability to predict the location accuracy without the need for a reference location estimate. This is made possible by the extensive training done using various accuracy/reference values, which result in the computing of weights in the ML model. Such a trained model can then be used for an inference/prediction of the location accuracy in this step. An internal PoC has shown very encouraging results using such an ML model + +NOTE 2: The NWDAF and related aspects of this solution to be further discussed in FS\_eNA\_Ph3, as part of Key Issue #9: Enhancement of NWDAF with finer granularity of location information given in TR 23.700-81 [23]. + +Step 4: LMF compares the location accuracy got in step 3 with the required location accuracy got in step 1 from the LCS Client. + +Step 5: If the required location accuracy is not met, the LMF may take subsequent actions like re-executing the LCS procedure with more stringent parameters (for example: higher periodicity measurements). + +Step 6: The LMF returns the location estimate with the required accuracy. + +## 6.11.4 Impacts on services, entities, and interfaces + +LMF: + +- To request and receive analytics corresponding to Location Accuracy for a given target area from NWDAF. +- To decide whether the required location accuracy is met or not based on the analytics provided by NWDAF. + +NWDAF: + +- To support Analytics ID corresponding to Location Accuracy for a give target area. +- To provide the Location Accuracy analytics to LMF. + +# 6.12 Solution #12: Supporting analytics for location accuracy + +## 6.12.1 Description + +As part of the location services requirements defined in TS 22.071 [18], one of the main requirements for the LCS service is the support of Location Accuracy. + +The location accuracy is provided in terms of horizontal, vertical accuracy and response time. In general the accuracy of the location depends on the positioning technology used, the varying radio environments (e.g. considering multipath propagation), the type of environment where the location is measured (dense urban area or rural area). + +The location accuracy required by each service varies and can vary from location accuracy up to 200km for weather services to location accuracy of up to 50m for Asset Location, route guidance, navigation. Further information is provided in Table 4.1 of TS 22.071 [18]. + +When a location client requires a location accuracy the location client may include in the request to the GMLC: + +- A response time (no delay, low delay, delay tolerant). +- Horizontal and/or vertical accuracy requirements (in meters). +- LCS QoS Class (best effort, assured or multiple QoS corresponding to a priority of QoS accuracy). + +When the LMF determines the location the LMF also determines the accuracy of the location and also whether the location requirements are met which are sent to the GMLC. The GMLC responds to the client the accuracy of the location measurement can be met. + +Analytics from the NWDAF can be enhanced to allow a location client to be aware if a location accuracy can be met. Example consumers of such analytics is as follows: + +- LMF uses the analytics to identify the best positioning method to use to determine a location in a specific area, taking into account UE capabilities, QoS requirements and operator policies. +- The location client can determine to upgrade/downgrade the requested LCS QoS taking into account the analytics of location accuracy. +- The location client can adapt the application service accordingly. For example, a navigation service can take into account areas where location accuracy cannot be met when providing route guidance. + +## 6.12.2 Procedures + +A consumer (e.g. a location client) requests from the NWDAF analytics for "Location Accuracy Sustainability". The request may also include the following as Analytic Filters: + +- A target area. +- A target UE (not applicable for option 1), group of UEs (not applicable for option 1) or any UE. +- Time of Day. +- An LCS QoS Class or Horizontal/Vertical Accuracy requirement (denotes the requested LCS QoS or Horizontal/Vertical accuracy requirement). +- Optionally a positioning method used. +- A location accuracy threshold, i.e. report accuracy analytics only if the location accuracy exceed an horizontal or a vertical accuracy threshold (in meters). + +The analytics consumer may also include as Analytic Filters within the location request the following: + +- An indication to report the ratio of UEs using LOS/NLOS measurements in a target area. + +Two options are available from the NWDAF to collect input data for Location Measurement Accuracy: + +- Option 1: Data Producer is the LMF (applicable when an analytics consumer requests Location Accuracy Analytics for any UE for a specific Target Area). +- Option 2: Data Producer is the GMLC. + +### Data collection for Option 1: + +The NWDAF finds the LMF that serves a target area. The NWDAF then invokes a new SBI (e.g. Nlmf\_Event\_Exposure) and requests data from the LMF identified by a new Event ID, e.g. "Location Measurement Accuracy request". The LMF based on the Event ID requested provides information on accuracy of a measurement of a location when a location measurement is made by the LMF. + +The LMF provides measurements reports to the NWDAF as follows: + +- The LMF provides measurements report for any location request received by the LMF by a location client (the request is received via the GMLC). + +- If the request includes a requested LCS QoS class or horizontal/vertical accuracy the LMF provides a measurements report when the LMF receives a location request from a location client with the requested accuracy. +- If the request includes a positioning method, the LMF provides measurements report when the LMF determines the location using the position method used. +- If the request includes an LOS/NLOS ratio the LMF triggers the UEs to report whether a measurement was made according to LOS or NLOS measurements. + +The procedure is shown below: + +![Sequence diagram illustrating the procedure to derive analytics for location accuracy sustainability (Option 1). The diagram shows interactions between Consumer, NWDAF, LMF, RAN, and UE.](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +``` +sequenceDiagram + participant Consumer + participant NWDAF + participant LMF + participant RAN + participant UE + + Consumer->>NWDAF: 1. Request Analytics (Analytic ID: LocationAccuracySustainability) + NWDAF->>LMF: 2. Find LMF + NWDAF->>LMF: 3. Request Data (New Event ID: LocationAccuracyData) + LMF->>RAN: 4a. Location Request + Note right of LMF: 4b. Retrieves location and calculate accuracy of location measurement + Note right of LMF: 5. Determines location measurements needs to be reported to the NWDAF + LMF->>NWDAF: 6. Data Response + Note right of NWDAF: 7. Derive Analytics + NWDAF->>Consumer: 8. Analytics Response +``` + +Sequence diagram illustrating the procedure to derive analytics for location accuracy sustainability (Option 1). The diagram shows interactions between Consumer, NWDAF, LMF, RAN, and UE. + +**Figure 6.12.2-1: Procedure to derive analytics for location accuracy sustainability(Option 1)** + +1. A Consumer requests analytics for location accuracy sustainability from the NWDAF. The request may include a target area, a time of day, a target UE (or group of UEs or any UE). The request may also include, to report analytics for a specific LCS QoS requirement or horizontal/vertical accuracy. +2. The NWDAF finds the LMF serving the UE target area (Option 1) by querying the NRF. +3. The NWDAF sends a request to the LMF to provide location measurement accuracy data (the request may be a subscription or a one-time request). The NWDAF includes in the request to the LMF information to satisfy the requirements of the consumer in step 1. +- 4a-4c. The LMF is triggered to provide a location from a location client as per procedure in TS 23.273 [5]. The LMF derives the location of the UE. +5. The LMF determines that the location measured is in an area where the NWDAF has subscribed to report location measurements. The LMF reports the location accuracy to the NWDAF. +6. The data are provided to the NWDAF. + +7. The NWDAF derives analytics for location accuracy. +8. The NWDAF provides analytics to the consumer. + +**Data collection for Option 2:** + +The NWDAF subscribes from GMLC to obtain location data for a UE or any UE. The NWDAF discovers GMLC from NRF and invokes (via a new SBI) to retrieve data about the location measurement accuracy (optionally per positioning method). + +The GMLC provides measurements report to the NWDAF as follows: + +- If the request target any UE the GMLC provides measurements report for any location request received by a location client +- If the request target a specific UE, the GMLC provides measurements report when the GMLC receives a location request from a location client that targets the specific UE. +- If the request includes a requested LCS QoS class or horizontal/vertical accuracy the GMLC provides measurements report when the GMLC receives a location request from a location client with the requested accuracy +- If the request includes a positioning method, the GMLC provides measurements report when the GMLC receives information (from the AMF) on the positioning method used by the LMF to determine the location of the UE. + +The procedure is shown below: + +![Sequence diagram illustrating the procedure to derive analytics for location accuracy sustainability (Option 2).](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +``` +sequenceDiagram + participant Consumer + participant NWDAF + participant GMLC + participant 5GC as 5GC (LMF, AMF, RAN) + participant UE + + Consumer->>NWDAF: 1. Request Analytics (Analytic ID: LocationAccuracySustainability) + NWDAF->>NWDAF: 2. Find GMLC + NWDAF->>GMLC: 3. Request Data (New Event ID: LocationAccuracyData) + GMLC->>5GC: 4a. Location Request + Note right of 5GC: 4b. Receives location information + Note right of GMLC: 5. Determines location measurements needs to be reported to the NWDAF + GMLC->>NWDAF: 6. Data Response + NWDAF->>NWDAF: 7. Derive Analytics + NWDAF->>Consumer: 8. Analytics Response +``` + +The sequence diagram shows the interaction between five entities: Consumer, NWDAF, GMLC, 5GC (LMF, AMF, RAN), and UE. The process starts with the Consumer sending a 'Request Analytics' message to the NWDAF. The NWDAF then performs an internal 'Find GMLC' step. It sends a 'Request Data' message to the GMLC. The GMLC sends a 'Location Request' to the 5GC. The 5GC returns 'location information' to the GMLC. The GMLC then determines the necessary measurements and sends a 'Data Response' to the NWDAF. Finally, the NWDAF performs 'Derive Analytics' and sends an 'Analytics Response' back to the Consumer. + +Sequence diagram illustrating the procedure to derive analytics for location accuracy sustainability (Option 2). + +**Figure 6.12.2-2: Procedure to derive analytics for location accuracy sustainability (Option 2)** + +1. A Consumer requests analytics for location accuracy sustainability from the NWDAF. The request may include a target area, a time of day, a target UE (or group of UEs or any UE). The request may also include, to report analytics for a specific LCS QoS requirement or horizontal/vertical accuracy. + +2. The NWDAF finds the GMLC from the NRF +3. The NWDAF sends a request to the GMLC to provide location measurement accuracy data (the request may be a subscription or a one-time request). The NWDAF includes in the request to the GMLC information to satisfy the requirements of the consumer in step 1. +- 4a-4b. The GMLC is triggered to provide a location from a location client as per procedure in TS 23.273 [5]. The GMLC invokes a location request to the AMF/LMF according to TS 23.273 [5]. The GMLC receives location information from the AMF/LMF including information indicating if the location accuracy requested has been met and the positioning method used. +5. The GMLC determines to report the location information to the NWDAF. +6. The data are provided to the NWDAF +7. The NWDAF derives analytics for location accuracy . +8. The NWDAF provides analytics to the consumer. + +The following input data are required by the NWDAF to measure location measure accuracy. + +**Table 6.12.2-1: Location measurement accuracy data collected by NWDAF** + +| Information | Source | Description | +|------------------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location Measurement accuracy data | LMF or GMLC | Includes information on the Position Method used, the requested LCS QoS or horizontal/accuracy and whether the location accuracy request was satisfied | +| Timestamp | LMF or GMLC | The time where the location was measured by the LMF | +| LOS or NLOS measurements | LMF | Indication whether the UE measurements was based on LOS/NLOS measurements | +| UE Location | AMF | The location area of the UE when the location measurement was made | + +The analytics output to the consumer may include one of the following: + +**Table 6.12.2-2: "Location Accuracy Sustainability" statistics** + +| Information | Description | +|---------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| List of Accuracy Analytics (1..max) | | +| >Applicable Area | A list of TAIIs or Cell IDs within the Location information that the analytics applies to. | +| >Applicable Time Period | The time period within the Analytics target period that the analytics applies to. | +| >The requested LCS QoS | The analytics provide a delta against the request measurement accuracy level from a consumer. | +| > List of SUPIs | A list of SUPIs experiencing the same analytics accuracy. | +| > Positioning Method | The positioning method used to measure location. | +| > Ratio of NLOS/LOS measurements in target area | Provides a ratio of LOS to NLOS measurements reported by the UE in the target area. | +| > Percentage of analytics accuracy above/below requested thresholds | A percentage indicating if the requested analytics accuracy is met. | + +**Table 6.12.2-3: "Location Accuracy Sustainability" predictions** + +| Information | Description | +|---------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| List of Accuracy sustainability Analytics (1..max) | | +| >Applicable Area | A list of TAIIs or Cell IDs within the Location information that the analytics applies to. | +| >Applicable Time Period | The time period within the Analytics target period that the analytics applies to. | +| > The requested LCS QoS | The analytics provide a delta against the request measurement accuracy level from a consumer. | +| > List of SUPIs | A list of SUPIs experiencing the same analytics accuracy. | +| > Positioning Method | The positioning method used to measure location. | +| > Ratio of NLOS/LOS measurements in target area | Provides predicted ratio of LOS to NLOS measurements of UEs in target area. | +| > Percentage of analytics accuracy above/below requested thresholds | A percentage prediction indicating if the requested analytics accuracy is met. | +| >Confidence | Confidence of the prediction. | + +### 6.12.3 Impacts on services, entities and interfaces + +- Applicable to Option 1: New Nlmf event notification service to allow the NWDAF to retrieve location measurement reports from the LMF. +- Applicable to Option 2: NWDAF support Ngmlc service based interfaces to retrieve location information for a UE. + +## 6.13 Solution #13: Architecture enhancement for the interaction between LCS and NWDAF + +### 6.13.1 Introduction + +The solution is intended to address and resolve Key Issue 4: Interaction between Location Service and NWDAF. + +Here are three schemes that can be a potential basis to support the finer granularity location information interaction between LCS and NWDAF, i.e. AMF interacts with NWDAF, GMLC interacts with NWDAF, and LMF interacts with NWDAF. This solution aims to enhance the interfaces between AMF and NWDAF with the consideration of the reduction of the time latency and the signalling flows. + +The interaction between AMF and NWDAF is enhanced to support the delivery of the finer granularity location information, including the finer geographical location, velocity, accuracy, and other necessary information. When the location information request is received in AMF from NWDAF, the AMF has a responsibility to distinct the requested granularity to determine whether it is necessary to initiate a request to LMF. If the granularity is TA/cell level, the AMF returns the TA/cell level location to the NWDAF as specified in TS 23.288 [9]. If the granularity is finer than the TA/cell level and other requirements are received in the requested message, the AMF initiates a location request to LMF. + +To solve the aforementioned issue, this solution proposes a scheme to support location information delivery between LCS architecture and NWDAF. + +## 6.13.2 Architecture + +![Figure 6.13.2-1: Interaction between LCS and NWDAF architecture. The diagram shows a UE connected to a RAN, which is connected to an AMF via N2. The UE is also connected to the AMF via N1. The AMF is connected to a UDM via Nudm, an LMF via Nlmf, and an NWDAF via Nnwdaf. The NWDAF is connected to a GMMLC via Ngmlc, which is connected to an LCS client via Le.](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +graph TD + UE[UE] -- N1 --> AMF[AMF] + RAN[RAN] -- N2 --> AMF + AMF -- Nudm --> UDM[UDM] + AMF -- Nlmf --> LMF[LMF] + AMF -- Nnwdaf --> NWDAF[NWDAF] + NWDAF -- Ngmlc --> GMMLC[GMMLC] + GMMLC -- Le --> LCS_client((LCS client)) + +``` + +Figure 6.13.2-1: Interaction between LCS and NWDAF architecture. The diagram shows a UE connected to a RAN, which is connected to an AMF via N2. The UE is also connected to the AMF via N1. The AMF is connected to a UDM via Nudm, an LMF via Nlmf, and an NWDAF via Nnwdaf. The NWDAF is connected to a GMMLC via Ngmlc, which is connected to an LCS client via Le. + +**Figure 6.13.2-1: Interaction between LCS and NWDAF architecture** + +Figure 6.13.2-1 is similar to Figure 4.2.1-1 in TS 23.273 [5] and additionally supports the enhancement of the service-based interface between AMF and NWDAF. + +Enhanced Service Based Interfaces proposed in this solution comprise: + +**Nnwdaf:** Service-based interface exhibited by NWDAF. + +**Namf:** Service-based interface exhibited by AMF. + +In addition, this solution utilizes the existing service operations defined in TS 23.502 [3] and TS 23.273 [5] for the Nlmf and Nudm service based interfaces. + +As for privacy check for location service, this solution supports performing privacy check on the NWDAF side in some scenarios with the signalling reduction purpose. The NWDAF sends location requests for the SUPI with an indication to exempt the privacy check in LCS only when the user consent and the privacy check of this SUPI are all passed on the NWDAF side. The LCS architecture skips the privacy check accordingly. Otherwise, the NWDAF will not initiate the location request for the SUPI. + +NOTE: Performing the privacy check on the NWDAF side needs coordination work with eNA\_Ph3. + +In detail, if the result of the privacy check for call/session unrelated class is "Location allowed without notification" then the NWDAF acquires the UE location as normal without notifying the UE. If the indicator of privacy check indicates the UE must either be notified or notified with privacy verification, then the NWDAF request to the AMF with an indication of a privacy related action and the AMF sends a notification invoke message to the target UE. + +## 6.13.3 Procedures + +### 6.13.3.1 One-time Collection Procedure + +Figure 6.13.3.1-1 illustrates the one-time data collection from NWDAF to LCS architecture. In this scenario, it is assumed that the target UE(s) is identified using a SUPI or GPSI. This procedure is applicable to a request from NWDAF for immediately location collection. + +![Sequence diagram showing the AMF providing UE location information to NWDAF (One-time Collection). The diagram involves six lifelines: UE, RAN, AMF, LMF, UDM, and NWDAF. The sequence of messages is: 1. Nudm_UECM_Get Request from NWDAF to UDM; 2. Nudm_UECM_Get Response from UDM to NWDAF; 3. Location information Request from NWDAF to AMF; 4. LMf Selection (internal AMF process); 5. Nlmf_Location_DetermineLocation Request from AMF to LMF; 6. UE Positioning (internal LMF process); 7. Nlmf_Location_DetermineLocation Response from LMF to AMF; 8. Location information Response from AMF to NWDAF.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant LMF + participant UDM + participant NWDAF + + Note right of NWDAF: 1. Nudm_UECM_Get Request + NWDAF->>UDM: 1. Nudm_UECM_Get Request + Note right of UDM: 2. Nudm_UECM_Get Response + UDM-->>NWDAF: 2. Nudm_UECM_Get Response + Note right of NWDAF: 3. Location information Request + NWDAF->>AMF: 3. Location information Request + Note right of AMF: 4. LMf Selection + AMF->>LMF: 5. Nlmf_Location_DetermineLocation Request + Note right of LMF: 6. UE Positioning + LMF-->>AMF: 7. Nlmf_Location_DetermineLocation Response + Note right of AMF: 8. Location information Response + AMF-->>NWDAF: 8. Location information Response + +``` + +Sequence diagram showing the AMF providing UE location information to NWDAF (One-time Collection). The diagram involves six lifelines: UE, RAN, AMF, LMF, UDM, and NWDAF. The sequence of messages is: 1. Nudm\_UECM\_Get Request from NWDAF to UDM; 2. Nudm\_UECM\_Get Response from UDM to NWDAF; 3. Location information Request from NWDAF to AMF; 4. LMf Selection (internal AMF process); 5. Nlmf\_Location\_DetermineLocation Request from AMF to LMF; 6. UE Positioning (internal LMF process); 7. Nlmf\_Location\_DetermineLocation Response from LMF to AMF; 8. Location information Response from AMF to NWDAF. + +**Figure 6.13.3.1-1: AMF provides UE location information to NWDAF (One-time Collection)** + +1. The NWDAF invokes a Nudm\_UECM\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of the UE. If the NWDAF needs to have a trajectory or the location of the target UE and the user consent has been checked to allow the NWDAF to collect and use the location information, then the NWDAF process this procedure. +2. The UDM returns the address of the current serving AMF for the target UE. +3. The NWDAF invokes the location information request towards the AMF to request the location of the UE. The service operation includes the SUPI, the required location granularity, and may include the collection type, an indication of velocity information and the required QoS, which includes accuracy, latency, and QoS class. +4. The AMF determines whether the required location granularity can be provided by AMF itself. If the finer granularity location is required, the AMF selects an LMF based on NRF query or configuration in AMF. +5. The AMF invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the location information of the UE. The service operation includes an LCS Correlation identifier, the access type and may include the required QoS, which includes accuracy, latency, and QoS class. +6. The LMF initiates the positioning procedure toward UE. +7. The LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF to return the location information of the UE. The service operation includes the location estimate and may include velocity estimate, the age of location information, the timestamp, achieved QoS, which includes accuracy, latency and QoS class. +8. The AMF returns the Namf\_Location\_ProvideLocation Response towards the NWDAF to return the location information of the UE. + +### 6.13.3.2 Continuous Collection Procedure + +Figure 6.13.3.2-1 illustrates the continuous data collection from NWDAF to LCS architecture using event reporting. In this architecture, it is assumed that the target UE(s) is identified using a SUPI or GPSI. This procedure is applicable for the request from NWDAF for the deferred location reporting. + +![Sequence diagram showing the interaction between UE, RAN, AMF, LMF, UDM, and NWDAF for continuous UE location information collection. The process starts with NWDAF sending a Nudm_UECM_Get Request to UDM, which returns a response. NWDAF then sends a Location information Request to AMF. AMF performs LMF Selection and sends an Nlmf_Location_DetermineLocation Request to LMF. A UE Positioning phase occurs between RAN and LMF. AMF sends an LCS Periodic-Triggered Invoke request to UE via RAN, and UE returns a response. AMF sends an Nlmf_Location_DetermineLocation response to LMF, which in turn sends a Location information response to NWDAF. An Event Detection phase occurs between UE and RAN, with an Event report sent from RAN to LMF and an Ack returned to RAN. A second UE Positioning phase occurs between RAN and LMF. Finally, AMF sends an Nlmf_Location_DetermineLocation response to LMF, which sends a Location information response to NWDAF.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant LMF + participant UDM + participant NWDAF + + Note right of NWDAF: 1. Nudm_UECM_Get Request + NWDAF->>UDM: 1. Nudm_UECM_Get Request + Note right of UDM: 2. Nudm_UECM_Get Response + UDM-->>NWDAF: 2. Nudm_UECM_Get Response + Note right of NWDAF: 3. Location information Request + NWDAF->>AMF: 3. Location information Request + Note right of AMF: 4. LMF Selection + AMF->>LMF: 5. Nlmf_Location_DetermineLocation Request + Note over RAN, LMF: 6. UE Positioning + Note right of AMF: 7. LCS Periodic-Triggered Invoke request + AMF->>RAN: 7. LCS Periodic-Triggered Invoke request + RAN->>UE: 7. LCS Periodic-Triggered Invoke request + Note right of UE: 8. LCS Periodic-Triggered Invoke return result + UE-->>RAN: 8. LCS Periodic-Triggered Invoke return result + RAN-->>AMF: 8. LCS Periodic-Triggered Invoke return result + Note right of AMF: 9. Nlmf_Location_DetermineLocation response + AMF->>LMF: 9. Nlmf_Location_DetermineLocation response + Note right of AMF: 10. Location information response + AMF->>NWDAF: 10. Location information response + Note right of UE: 11. Event Detection + Note right of RAN: 12. Event report + RAN->>LMF: 12. Event report + Note right of LMF: 13. Event report Ack + LMF-->>RAN: 13. Event report Ack + Note over RAN, LMF: 14. UE Positioning + Note right of AMF: 15. Nlmf_Location_DetermineLocation response + AMF->>LMF: 15. Nlmf_Location_DetermineLocation response + Note right of AMF: 16. Location information response + AMF->>NWDAF: 16. Location information response + +``` + +Sequence diagram showing the interaction between UE, RAN, AMF, LMF, UDM, and NWDAF for continuous UE location information collection. The process starts with NWDAF sending a Nudm\_UECM\_Get Request to UDM, which returns a response. NWDAF then sends a Location information Request to AMF. AMF performs LMF Selection and sends an Nlmf\_Location\_DetermineLocation Request to LMF. A UE Positioning phase occurs between RAN and LMF. AMF sends an LCS Periodic-Triggered Invoke request to UE via RAN, and UE returns a response. AMF sends an Nlmf\_Location\_DetermineLocation response to LMF, which in turn sends a Location information response to NWDAF. An Event Detection phase occurs between UE and RAN, with an Event report sent from RAN to LMF and an Ack returned to RAN. A second UE Positioning phase occurs between RAN and LMF. Finally, AMF sends an Nlmf\_Location\_DetermineLocation response to LMF, which sends a Location information response to NWDAF. + +**Figure 6.13.3.2-1: AMF provides UE location information to NWDAF (Continuous Collection)** + +1. The NWDAF invokes a Nudm\_UECM\_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of the UE. If the NWDAF needs to collect the trajectory or the location of the target UE and the user consent has been checked to allow the NWDAF to collect and use the location information, then the NWDAF process this procedure. +2. The UDM returns the address of the current serving AMF of the target UE. +3. The NWDAF invokes the location information request towards the AMF to request the location of the UE. The service operation includes the SUPI, the required location granularity and may include the collection type, the event type, an indication of velocity information and the required QoS, which includes accuracy, latency, and QoS class. + +The NWDAF includes trigger or periodic event types in the location information request message. The AMF delivers event types to LMF and then LMF sends to the UE are specified as the current deferred MT-LR procedure. + +4. The AMF determines whether the required location granularity can be provided by AMF itself. If the finer granularity location is required the AMF selects an LMF based on NRF query or configuration in AMF. +5. The AMF invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the location information of the UE. The service operation includes an LCS Correlation identifier, the access type and may include the event type, the required QoS, which includes accuracy, latency, and QoS class. + +6. The LMF initiates the positioning procedure towards UE. +- 7-8. The AMF includes in the notification to the UE the type of deferred location request in the case of periodic or triggered location. The UE returns a result to the LMF. +- 9-10. The LMF may report the current location information, including the age of location information, the timestamp, event type, location estimate, velocity estimate, achieved QoS accuracy and QoS class, to the AMF and then to the NWDAF according to the periodic location reporting rule. +11. The UE monitors for the occurrence of the trigger or periodic event requested in step 7. When a trigger or periodic event is detected, the UE needs to connect to LMF and report its location information. +- 12-13. The UE sends an event reporting to the LMF. This event report may include the event type, location estimate, velocity estimate. +14. One or more UE positioning may be needed in this scenario. +- 15-16. The LMF reports the current location information, which may include the age of location information, the timestamp, event type, location estimate, velocity estimate, achieved QoS accuracy and QoS class. + +## 6.13.4 Impacts on existing entities and interfaces + +### 6.13.4.1 Impacts on AMF + +- Provides to NWDAF with finer granularity location data than TA/cell level and other information, e.g. location estimate, velocity estimate, timestamp, achieved QoS information. + +### 6.13.4.2 Impacts on NWDAF + +- Enhanced interface with AMF to request finer granularity location data than TA/cell level. +- Enable NWDAF to perform user consent and privacy check when requiring the finer granularity location data than TA/cell level. + +## 6.14 Solution #14: Unawareness positioning + +### 6.14.1 Introduction + +This solution addresses KI#6: UE Positioning without UE/User Awareness. + +### 6.14.2 Functional Description + +The principles of the solution are as follows: + +- UE unaware positioning: + - If the UE is in CM\_IDLE or RRC\_INACTIVE state, the UE cannot be paged during the positioning procedure. In this case, the 5GC provides the latest stored UE location information to the LCS Client/AF if the requested accuracy is achieved. + - If the UE is in CM\_CONNECTED state, the LMF selects uplink positioning method (e.g. Uplink E-CID, Uplink NR-E-CID, UL-TDOA, UL-AoA) which requires the NG-RAN configures the UE to report the measurement information, e.g. E-UTRA RSRP, E-UTRA RSRQ measurements in UL E-CID. From UE point of view, it has no idea that the measurement is related to positioning, so UE unawareness can be achieved. Furthermore, the privacy check which requires interaction with UE is also skipped. + - The UE unaware positioning can be applied to the 5GC-MT-LR and NI-LR procedures. +- User unaware positioning: + - If the UE is in CM\_IDLE or RRC\_INACTIVE state, the UE can be paged during the positioning procedure. + +- The User unaware positioning can be applied to any existing positioning procedure with the exception that the privacy check which requires interaction with user is skipped. + +## 6.14.3 Procedures + +### 6.14.3.1 UE unaware positioning + +To support UE unaware positioning, enhancements to the existing 5GC-MT-LR procedure and NI-LR procedure are described in this clause. + +Enhancements to 5GC-MT-LR procedure for the regulatory location service in clause 6.1.1 of TS 23.273 [5] are as follows: + +- Step 1: the LCS Service Request includes the UE unaware indication. +- Step 4: the Namf\_Location\_ProvidePositioningInfo Request includes the UE unaware indication. +- If the UE is in CM\_IDLE or RRC\_INACTIVE state (if known by AMF by requesting the NG-RAN to report RRC state information), the enhancements to steps 5-11 are as follows: + - Steps 5-9 are skipped. + - Step 10: the AMF rejects the location request with appropriate rejection cause or returns the Namf\_Location\_ProvidePositioningInfo Response which includes the latest UE location information. + - Step 11: the GMLC rejects the LCS Service Request if there is no UE location can fulfil the QoS. Otherwise, the GMLC returns the LCS Service Response with latest UE location. +- If the UE is in CM\_CONNECTED state, the enhancements to steps 5-11 are as follows: + - Step 7: the Nlmf\_Location\_DetermineLocation Request includes the UE unaware indication. The LMF selects positioning method based on the UE unaware indication. +- If the UE is in RRC\_INACTIVE state (from AMF point of view, UE is CM-CONNECTED), the enhancements to steps 5-11 are as follows: + - Step 7: the Nlmf\_Location\_DetermineLocation Request includes the UE unaware indication. The LMF selects positioning method based on the UE unaware indication. + - Step 8: The LMF sends NRPPa message including UE unaware indication to RAN. Because UE cannot be paged, RAN rejects the NRPPa message. + - Step 9: The LMF rejects the Nlmf\_Location\_DetermineLocation Reject with appropriate rejection cause. + - Step 10: the AMF rejects the location request with appropriate rejection cause or returns the Namf\_Location\_ProvidePositioningInfo Response which includes the latest UE location information. + - Step 11: the GMLC rejects the LCS Service Request if there is no UE location can fulfil the QoS. Otherwise, the GMLC returns the LCS Service Response with latest UE location. + +Enhancements to 5GC-MT-LR procedure for the commercial location service in clause 6.1.2 of TS 23.273 [5] are as follows: + +- Steps 1a, 1b-1, 1b-2, 4, 5: the corresponding message includes the UE unaware indication. +- If the UE is in CM\_IDLE or RRC\_INACTIVE state (if known by AMF by requesting the NG-RAN to report RRC state information), the enhancements to steps 6-24 are as follows: + - Steps 5-21 are skipped. + - Step 22: the AMF rejects the location request with appropriate rejection cause or returns the Namf\_Location\_ProvidePositioningInfo Response which includes the latest UE location information. + - Step 23-24: the GMLC rejects the LCS Service Request if there is no UE location can fulfil the QoS. Otherwise, the latest UE location is returned to LCS Client or AF. + +- If the UE is in CM\_CONNECTED state, the enhancements to steps 6-24 are as follows: + - Steps 7-9 are skipped. + - Step 11: the Nlmf\_Location\_DetermineLocation Request includes the UE unaware indication. The LMF selects positioning method based on the UE unaware indication. + - Steps 20-21 are skipped. +- If the UE is in RRC\_INACTIVE state (from AMF point of view, UE is CM-CONNECTED), the enhancements to steps 6-24 are as follows: + - Step 11: the Nlmf\_Location\_DetermineLocation Request includes the UE unaware indication. The LMF selects positioning method based on the UE unaware indication. + - Step 12: The LMF sends NRPPa message including UE unaware indication to RAN. Because UE cannot be paged, RAN rejects the NRPPa message. + - Step 13: The LMF rejects the Nlmf\_Location\_DetermineLocation Reject with appropriate rejection cause. + - Step 14: the AMF rejects the location request with appropriate rejection cause or returns the Namf\_Location\_ProvidePositioningInfo Response which includes the latest UE location information. + - Step 16-23 are skipped. + - Step 24: the GMLC rejects the LCS Service Request if there is no UE location can fulfill the QoS. Otherwise, the GMLC returns the LCS Service Response with latest UE location. + +Enhancements to 5GC-NI-LR procedure in clause 6.10.1 of TS 23.273 [5] are as follows: + +- Step 1: the AMF decides that the positioning is UE unaware based on configuration. +- Step 2: the Nlmf\_Location\_DetermineLocation Request includes the UE unaware indication. The LMF selects positioning method based on the UE unaware indication. + +### 6.14.3.2 User unaware positioning + +To support user unaware positioning, enhancements to the existing procedures are described in this clause. + +Enhancements to 5GC-MT-LR procedure for the commercial location service in clause 6.1.2 of TS 23.273 [5] are as follows: + +- Steps 1a, 1b-1, 1b-2, 4, 5: the corresponding message includes the user unaware indication. +- Steps 7-9, 20-21 are skipped. + +Enhancements to Deferred 5GC-MT-LR procedure for Periodic, Triggered and UE Available Location Events in clause 6.3 of TS 23.273 [5] are as follows: + +- Steps 1a, 1b-1, 1b-2, 4, 5: the corresponding message includes the user unaware indication. +- Steps 11-12 are skipped. + +### 6.14.4 Impacts on services, entities, and interfaces + +GMLC: + +- To support UE unaware positioning: receive UE unaware positioning indication from LCS Client and send the indication to AMF. +- To support user unaware positioning: receive user unaware positioning indication from LCS Client and send the indication to AMF. + +AMF: + +- To support UE unaware positioning: + +- If UE is in CM\_IDLE or RRC\_INACTIVE state (if known by AMF), the AMF does not page UE. The AMF rejects the request or returns the latest UE location to GMLC. +- If UE is in CM\_CONNECTED state, the AMF sends the UE unaware indication to LMF. +- To support user unaware positioning: the AMF does not send the NAS Location Notification Invoke Request to UE. + +LMF: + +- To support UE unaware positioning: + - Receives the UE unaware indication from AMF and selects positioning method based on the indication. +- Sends the UE unaware indication included in the NRPPa message to NG-RAN.NG-RAN: + - To support UE unaware positioning: receives the UE unaware indication from LMF and rejects the NRPPa request if UE is in RRC\_INACTIVE state. + +LCS Client/AF: + +- To support UE unaware positioning: send UE unaware positioning indication to GMLC. +- To support user unaware positioning: send user unaware positioning indication to GMLC. + +## 6.15 Solution #15: PRU assisted LCS architecture and procedure + +### 6.15.1 Introduction + +This solution addresses Key Issue #7, especially on the enable of the PRU management in 5GC and utilize the PRU to enhance the LCS procedure. + +### 6.15.2 Functional Description + +The procedures in clause 6.15.3.1 is used for 5GC to obtain the available PRU(s) information. The procedures in clauses 6.15.3.2 and 6.15.3.3 are used for the 5GC to choose the candidate PRU(s) and to use the candidate PRU(s) to enhance the location service procedure. + +#### 6.15.2.1 PRU Information + +The PRU information consists the following aspects: + +- Capability: indicate the capability a PRU supports positioning signal transmission capability and positioning measurement capability on Uu and PC5, based on that information, PRUs could be selected as candidate PRUs to assist the positioning of other UE. + +NOTE 1: The positioning signal transmission capability and signal measurement capability on PC5 relates to the study in RAN WG. + +- Location information, e.g. whether absolute location coordinates are available and to which degree of accuracy. This is required if a PRU to be utilized for timing calibration or to be utilized to complete the insufficient LoS path. The location information may include other parameters, such as velocity information, time stamps or duration of valid location information etc. +- Mobility state, whether a PRU is fixed or mobile. +- State indication, e.g. ON/OFF: this indicates whether a PRU is enabled to assist positioning of the other UEs. + +#### 6.15.2.2 PRU Information Acquisition + +PRU information could be obtained by 5GC via three different ways: + +i. Registration to AMF: + +A UE can be registered as a PRU. When a PRU registers to the network, the PRU information may be included in the UE context data and obtained by the AMF. After receive the PRU registration, the AMF sends message to NRF to indicate PRU existence in certain area (e.g. the TAI of the PRU location). + +ii. Registration to LMF: + +A UE can be configure as a PRU by a NF, e.g. LMF. LMF obtains PRU information via AMF. This information may be provided by the UE via LPP procedure. After receive the PRU registration, LMF sends message to NRF to indicate PRU existence in certain area (e.g. the TAI of the PRU location). + +iii. Subscription to UDM: + +A UE may be pre-configured as a PRU. Then, the PRU information may be included in the UE subscription data as a new parameter set and stored in UDM/UDR. + +### 6.15.2.3 PRU (de)/Activation + +To save power, the PRU may not always be activated. 5GC may activate or deactivate the PRU(s) based on the location service requirements. This can be enabled by updating the state indication in the PRU information. For instance, LMF may determine to de/activate PRUs via AMF. + +### 6.15.2.4 CM-IDLE/RRC-Inactive PRU(s) Utilization + +To fully utilize the PRU(s) in the same camping cell of target UE, target UE AMF can send the PRU wake up indication to the target UE NG-RAN, then target UE NG-RAN broadcast this information in target UE camping cell, then all candidate PRU(s) could listen this information and go back to connected state. + +NOTE 1: RAN WG coordination is needed. + +NOTE 2: This clause does not support the function to fully utilize the PRUs in the neighbour cells of target UE and in CM-IDLE/RRC-inactive state. + +## 6.15.3 Procedures + +### 6.15.3.0 Architecture Assumption + +It is assumed to reuse the existing architecture defined in Rel-17 LCS work (see TS 23.273 [5]). + +![Architecture Assumption diagram showing various network functions and their connections.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +The diagram illustrates a network architecture assumption. At the center is the AMF (Access and Management Function). To its left, a UE (User Equipment), PRU (PRU), and (R)AN (Radio Access Network) are connected via N1 and N2 interfaces. Above the AMF, the LMF (Location Management Function) is connected via NL1, and the UDM (Unified Data Management) is connected via N8. Below the AMF, the NEF (Network Exposure Function) is connected via N51. To the right of the AMF, the GMLC (Gateway Mobile Location Centre) and LRF (Location Retrieval Function) are connected via NL2 and NL5. The GMLC is connected to an LCS Client (Location Server Client) via Le interfaces. The UDM is also connected to the GMLC via NL6 and to the NEF via N52. The LMF is connected to the UDM via NL7. The NEF is connected to an AF (Application Function) via N33. + +Architecture Assumption diagram showing various network functions and their connections. + +Figure 6.15.3.1-0: Architecture Assumption + +### 6.15.3.1 PRU Management + +The PRU management procedure is used by 5GC to obtain the PRU information and to become aware which PRU(s) are available in the network. + +To manage PRU, three options could be considered: + +- Option A: PRU registration to AMF. +- Option B.1: PRU registration to LMF. +- Option B.2: LMF obtains available PRU information via LPP procedures. +- Option C: PRU information are pre-configured in the UDM. + +![Sequence diagram for PRU Management showing four options (A, B.1, B.2, C) involving PRU, NG-RAN, PRU AMF, LMF, NRF, and UDM. Option A shows PRU registering directly with PRU AMF. Option B.1 shows PRU registering with NG-RAN, which then registers with PRU AMF, which then registers with LMF. Option B.2 shows PRU registering with LMF via LPP. Option C shows PRU information being pre-configured in UDM.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant PRU + participant NG-RAN + participant PRU_AMF as PRU AMF + participant LMF + participant NRF + participant UDM + + Note left of PRU: Option#A + PRU->>NG-RAN: 1a. Registration Request (PRU Info) + NG-RAN->>PRU_AMF: 2a. Registration Request (PRU Info) + PRU_AMF->>NRF: 3a. Nnrf_NFManagement_NFUpdate Request (PRU location, PRU existence indication) + + Note left of PRU: Option#B.1 + PRU->>NG-RAN: 1b. UL NAS Transport (PRU Registration Request (PRU Info)) + NG-RAN->>PRU_AMF: 2b. Namf_Communication_N1MessageNotify (PRU Registration Request (PRU Info)) + PRU_AMF->>LMF: 3b. Nnrf_NFManagement_NFUpdate Request (PRU location, PRU existence indication) + + Note left of PRU: Option#B.2 + PRU->>LMF: 1b. LPP Capability Transfer (PRU Registration Request (PRU Info)) + LMF->>NRF: 2b. Nnrf_NFManagement_NFUpdate Request (PRU location, PRU existence indication) + + Note left of PRU: Option#C + Note right of UDM: PRU Info +Pre-configured + +``` + +Sequence diagram for PRU Management showing four options (A, B.1, B.2, C) involving PRU, NG-RAN, PRU AMF, LMF, NRF, and UDM. Option A shows PRU registering directly with PRU AMF. Option B.1 shows PRU registering with NG-RAN, which then registers with PRU AMF, which then registers with LMF. Option B.2 shows PRU registering with LMF via LPP. Option C shows PRU information being pre-configured in UDM. + +Figure 6.15.3.1-1: PRU Management + +**Option A: PRU registration to AMF** + +- 1a~2a. PRU initiate the registration procedure to the AMF, including the PRU capability as well as the User Location Information (i.e. CGI and TAI). The PRU may also include the mobility state (e.g. mobile or static) in its registration, so AMF can maintain all the available PRU with related information dynamically. +- 3a. After receive the PRU information, the AMF invokes the Nnrf\_NFManagement\_NFUpdate Request (PRU location, PRU existence indication) to NRF to indicate the PRU existence in certain areas (e.g. in one or multiple TAI(s)). + +**Option B.1: PRU registration to LMF** + +- 1b~2b. The UE provides an indication to the serving AMF whether it can function as a PRU. The serving AMF then registers the PRU to an LMF. +- 3b. After receive the PRU information, the LMF invokes the Nnrf\_NFManagement\_NFUpdate Request (PRU location, PRU existence indication) to NRF to indicate the PRU existence in certain areas (e.g. in one or multiple TAI(s)). + +**Option B.2: PRU registration to LMF** + +- 1b. LMF obtains available PRU information via LPP procedures. +- 2b. This step is same as step 3b in Option B.1. + +**Option C: PRUs information are maintained at the UDM.** + +A UE may be pre-configured as a PRU with the PRU information included in the UE subscription data as a new parameter set and stored in UDM. + +### 6.15.3.2 PRU Activation/Deactivation + +PRU activation/deactivation procedure is used by 5GC to enable/disable the candidate PRU(s) for assisting location service. + +![Sequence diagram for PRU activation/deactivation procedure. The diagram shows interactions between PRU(s), NG-RAN, LMF, PRU AMF(s), and UDM. The process starts with a trigger in the LMF (LCS QoS triggered or location procedure triggered). The LMF sends a Namf_PRUActivation Request to the PRU AMF(s). The PRU AMF(s) sends a Nudm_SDM_Get to the UDM. The UDM returns a response. The PRU AMF(s) performs a privacy check. The PRU AMF(s) sends a Nudm_UECM_update Request (PRU ID, State=ON) to the UDM. The UDM returns a response. The PRU AMF(s) activates the candidate PRU. Finally, the PRU AMF(s) sends a Namf_PRUActivation Response to the LMF.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +``` + +sequenceDiagram + participant PRU(s) + participant NG-RAN + participant LMF + participant PRU AMF(s) + participant UDM + + Note right of LMF: 1. LCS QoS triggered or location procedure triggered + LMF->>PRU AMF(s): 2. Namf_PRUActivation Request (target UE location, number of PRU(s), trigger condition) + PRU AMF(s)->>UDM: 3. Nudm_SDM_Get + Note over PRU(s), NG-RAN, LMF, PRU AMF(s): 4. Privacy check + PRU AMF(s)->>UDM: 5. Nudm_UECM_update Request (PRU ID, State=ON) + UDM-->>PRU AMF(s): 6. Nudm_UECM_update Response + Note over PRU(s), NG-RAN, LMF, PRU AMF(s): 7. PRU activation + PRU AMF(s)->>LMF: 8. Namf_PRUActivation Response + +``` + +Sequence diagram for PRU activation/deactivation procedure. The diagram shows interactions between PRU(s), NG-RAN, LMF, PRU AMF(s), and UDM. The process starts with a trigger in the LMF (LCS QoS triggered or location procedure triggered). The LMF sends a Namf\_PRUActivation Request to the PRU AMF(s). The PRU AMF(s) sends a Nudm\_SDM\_Get to the UDM. The UDM returns a response. The PRU AMF(s) performs a privacy check. The PRU AMF(s) sends a Nudm\_UECM\_update Request (PRU ID, State=ON) to the UDM. The UDM returns a response. The PRU AMF(s) activates the candidate PRU. Finally, the PRU AMF(s) sends a Namf\_PRUActivation Response to the LMF. + +Figure 6.15.3.2-1: PRU activated or deactivated + +1. Activation/deactivation of PRU(s) is triggered by LMF, such as based on LCS requirements, e.g. LCS QoS of target UEs cannot be met, or based on the location service procedure in clause 6.15.3.3. +2. LMF invokes the PRU activation request towards the PRU AMF. The operation request may include target UE location, PRU(s) information and triggering conditions. +3. AMF invokes a Nudm\_SDM\_Get service operation towards the UDM to obtain the privacy settings of the PRU(s). The UDM returns the PRU(s) privacy setting. AMF checks the PRU(s) Privacy profile. +4. AMF performs privacy check if the privacy profile indicates that the PRU(s) must be either notified or verified. +5. AMF invokes the context management update operation request to UDM to update the PRU state information. +6. AMF receives the response from UDM. +7. The AMF activates the candidate PRU. +8. AMF returns PRU activation response towards LMF. + +### 6.15.3.3 Location service procedure by using PRU(s) + +This clause describes the location service procedure with the assistance of PRU. Clauses 6.15.3.3.1 and 6.15.3.3.2 are based on the prerequisite that PRU(s) are managed by AMF, i.e. the AMF-centric. Clauses 6.15.3.3.3 and 6.15.3.3.4 are based on the prerequisite that PRU(s) are managed by LMF, i.e. the LMF-centric. + +#### 6.15.3.3.1 AMF-centric MT-LR + +The AMF-centric MT-LR requests PRU AMF to provide one or multiple candidates PRU(s) in the vicinity of target UE, e.g. the same cell or the neighbour cell, to improve positioning accuracy. + +## 6.15.3.3.1.1 MT-LR procedure based on Option A in clause 6.15.3.1 + +![Sequence diagram of the MT-LR procedure using PRU (AMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, PRU AMF(s), LMF, GMLC, UDM, NRF, and LCS client. The process involves service requests, location determination, PRU discovery, and final positioning.](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +``` + +sequenceDiagram + participant LCS client + participant GMLC + participant UDM + participant NRF + participant LMF + participant PRU AMF(s) + participant Target UE AMF + participant NG-RAN + participant PRU(s) + participant Target UE + + Note right of LCS client: Network Triggered Service Request + LCS client->>GMLC: 1. LCS Service Request(GPSI/SUPI, required QoS, supported GAD shapes) + GMLC->>UDM: 2. Nudm_UECM_Get Request/Response (UE ID, NF Type=AMF) + GMLC->>Target UE AMF: 3a. Namf_Location_ProvidePositioningInfo Request (target UE's GPSI/SUPI, LCS client type, LCS location type) + Target UE AMF-->>NG-RAN: 3b. PRU wake up indication + Target UE AMF->>LMF: 4. Nlmf_Location_DetermineLocation Request (LCS correlation ID, target UE location) + LMF->>NRF: 5. Nnrf_NFDiscovery_Request Request (target UE location, indication to discover the PRU AMF) + NRF-->>LMF: 6. Nnrf_NFDiscovery_Request Response (PRU AMF(s)) + LMF->>PRU AMF(s): 7. NXXX_PRUDiscovery Request (target UE location and/or vicinal location) + Note right of PRU AMF(s): choose one or multiple candidate PRU(s) + PRU AMF(s)-->>LMF: 8. NXXX_PRUDiscovery Response (candidate PRU(s) information) + LMF->>PRU(s): 9. PRU Activation (i.e., clause 6.15.3.2) and Positioning + LMF->>Target UE: 10. Target UE Positioning + +``` + +Sequence diagram of the MT-LR procedure using PRU (AMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, PRU AMF(s), LMF, GMLC, UDM, NRF, and LCS client. The process involves service requests, location determination, PRU discovery, and final positioning. + +Figure 6.15.3.3-1: MT-LR procedure using PRU (AMF-centric) + +The following additions apply to step 1~4 compared to steps 1-5 defined in clause 6.1.1 of TS 23.273 [5]. + +- 3b. After target UE AMF receive step 3a, if the target UE support positioning by PRU, e.g. based on the target UE subscription information or the information in target UE context, or based on the target UE positioning capability, e.g. whether target UE support NR positioning, the AMF send an indication to NG-RAN to trigger NG-RAN broadcast the PRU wake up information in target UE camping cell, e.g. the per PLMN indication in posSIB. For those PRU(s) in CM-IDLE/RRC-inactive state, after receive this information, those PRU(s) trigger the service request/RRC-resume to go back to CM-CONNECTED as described in clause 4.2.3.2 of TS 23.502 [3] or clause 9.2.2.4 of TS 38.300 [22]. +5. The LMF invokes the Nnrf\_NFDiscovery\_Request Request towards NRF to request the PRU AMF. The service operation includes the target UE location information (e.g. the TAI of target UE), the indication to find the PRU AMF which could serve in the area around the target UE. +6. Based on the PRU AMF discovery indication and the target UE location information, the NRF return one or multiple PRU AMF(s) via Nnrf\_NFDiscovery\_Request Response. +7. LMF sends the PRU discovery request to PRU AMF to request the candidate PRU. The message includes the target UE location information and the target UE vicinal location (e.g. the neighbour cell of target UE). +8. Based on the message in step 7, the PRU AMF choose one or multiple candidate PRU(s) based on the target UE location, the target UE vicinal location, and the mobile state of PRU. The PRU AMF invokes PRU discovery response to LMF, includes one or multiple candidate PRU(s). +9. The LMF performs the activation procedure as defined in clause 6.15.3.2 to activate the desired PRU(s). LMF also performs one or more of the positioning procedures towards PRU as described in clauses 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 [5]. +10. The LMF performs one or more of the positioning procedures towards target UE as described in clauses 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 [5]. + +## 6.15.3.3.1.2 MT-LR procedure based on Option C in clause 6.15.3.1 + +![Sequence diagram of the MT-LR procedure using PRU (AMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, GMLC, UDM, and LCS client. The process starts with an LCS Service Request from the LCS client to the GMLC, followed by a Nudm_UECM_Get Request/Response from the GMLC to the LMF. The LMF then sends a Namf_Location_ProvidePositioningInfo Request to the Target UE AMF. A Network Triggered Service Request is sent from the Target UE AMF to the Target UE. The Target UE AMF sends a PRU wake up indication to the NG-RAN. The NG-RAN sends a Nudm_SDM_Get request to the UDM, which responds with a Nudm_SDM_Get response. The Target UE AMF then chooses one or multiple candidate PRU(s). The Target UE AMF sends an Nlmf_Location_DetermineLocation Request to the LMF. The LMF performs PRU Activation and Positioning. Finally, the Target UE is positioned.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +``` + +sequenceDiagram + participant LCS client + participant GMLC + participant LMF + participant Target UE AMF + participant UDM + participant NG-RAN + participant PRU(s) + participant Target UE + + Note left of Target UE: Network Triggered Service Request + LCS client->>GMLC: 1. LCS Service Request(GPSI/SUPI, required QoS, supported GAD shapes) + GMLC->>LMF: 2. Nudm_UECM_Get Request/Response (UE ID, NF Type=AMF) + LMF->>Target UE AMF: 3a. Namf_Location_ProvidePositioningInfo Request (target UE GPSI/SUPI, LCS client type, LCS location type) + Target UE AMF-->>Target UE: Network Triggered Service Request + Target UE AMF->>NG-RAN: 3b. PRU wake up indication + Target UE AMF->>UDM: 4. Nudm_SDM_Get request (subscription info of the UEs in the Vicinity of the target UE) + UDM-->>Target UE AMF: 5. Nudm_SDM_Get response (subscription info of the UEs in Vicinity of the target UE) + Note right of Target UE AMF: choose one or multiple candidate PRU(s) + Target UE AMF->>LMF: 6. Nlmf_Location_DetermineLocation Request (one or multiple PRU(s) information) + LMF->>PRU(s): 7. PRU Activation (i.e., clause 6.15.3.2) and Positioning + LMF->>Target UE: 8. Target UE Positioning + +``` + +Sequence diagram of the MT-LR procedure using PRU (AMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, GMLC, UDM, and LCS client. The process starts with an LCS Service Request from the LCS client to the GMLC, followed by a Nudm\_UECM\_Get Request/Response from the GMLC to the LMF. The LMF then sends a Namf\_Location\_ProvidePositioningInfo Request to the Target UE AMF. A Network Triggered Service Request is sent from the Target UE AMF to the Target UE. The Target UE AMF sends a PRU wake up indication to the NG-RAN. The NG-RAN sends a Nudm\_SDM\_Get request to the UDM, which responds with a Nudm\_SDM\_Get response. The Target UE AMF then chooses one or multiple candidate PRU(s). The Target UE AMF sends an Nlmf\_Location\_DetermineLocation Request to the LMF. The LMF performs PRU Activation and Positioning. Finally, the Target UE is positioned. + +Figure 6.15.3.3-2: MT-LR procedure using PRU (AMF-centric) + +The following additions apply to steps 1~3 compared to steps 1~4 defined in clause 6.1.1 of TS 23.273 [5]. + +- 3b. After target UE AMF receive step 3a, if the target UE support positioning by PRU, e.g. based on the target UE subscription information or the information in target UE context, or based on the target UE positioning capability, e.g. whether target UE support NR positioning, the AMF send an indication to NG-RAN to trigger NG-RAN broadcast the PRU wake up information in target UE camping cell, e.g. the per PLMN indication in posSIB. For those PRU(s) in CM-IDLE/RRC-inactive state, after receive this information, those PRU(s) trigger the service request/RRC-resume to go back to CM-CONNECTED as described in clause 4.2.3.2 of TS 23.502 [3] or clause 9.2.2.4 of TS 38.300 [22]. +4. The AMF invokes Nudm\_SDM\_Get request to UDM to request PRU information of the UE(s) in the same or vicinal location with the target UE, e.g. within the target UE TAI(s). +5. UDM sends the Nudm\_SDM\_Get response to AMF, includes PRU information in the subscription information of the UE(s) in the same or vicinal location with the target UE. The AMF choose one or multiple candidate PRU(s) from those UE(s) in step 5, such as, based on the target UE location, PRU capability, location information and mobility state. +6. The target UE AMF invokes Nlmf\_Location\_DetermineLocation Request towards LMF, includes one or multiple candidate PRU information. +7. The LMF performs the activation procedure as defined in clause 6.15.3.2 to activate the desired PRU(s). LMF also performs one or more of the positioning procedures towards PRU(s) as described in clauses 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 [5]. +8. The LMF performs one or more of the positioning procedures towards target UE as described in clauses 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 [5]. + +## 6.15.3.3.2 AMF-centric MO-LR + +The AMF-centric MO-LR requests PRU AMF to provide one or multiple candidates PRU(s) in the vicinity of target UE to improve positioning accuracy. + +## 6.15.3.3.2.1 MO-LR procedure based on Option A in clause 6.15.3.1 + +![Sequence diagram for MO-LR procedure using PRU/ (AMF-centric) based on Option A. Lifelines: Target UE, PRU(s), NG-RAN, Target UE AMF, PRU AMF(s), LMF, NRF. The sequence starts with a Target UE Triggered Service Request (1) from Target UE to Target UE AMF. The Target UE AMF sends a MO-LR (2a) to PRU(s). PRU(s) sends a wake up indication (2b) to Target UE AMF. The Target UE AMF performs LMF Selection (3). The Target UE AMF sends an Nlmf_Location_DetermineLocation Request (4) to LMF. The LMF sends an Nnrf_NFDiscovery_Request (5) to NRF. The NRF returns an Nnrf_NFDiscovery_Request Response (6) to LMF. The LMF sends an NXXX_PRUDiscovery Request (7) to PRU AMF(s). PRU AMF(s) choose one or multiple candidate PRU UE(s) (8). The LMF sends a PRU Activation (i.e., clause 6.15.3.2) and Positioning (9) to Target UE AMF. Finally, the Target UE AMF performs Target UE Positioning (10).](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +Sequence diagram for MO-LR procedure using PRU/ (AMF-centric) based on Option A. Lifelines: Target UE, PRU(s), NG-RAN, Target UE AMF, PRU AMF(s), LMF, NRF. The sequence starts with a Target UE Triggered Service Request (1) from Target UE to Target UE AMF. The Target UE AMF sends a MO-LR (2a) to PRU(s). PRU(s) sends a wake up indication (2b) to Target UE AMF. The Target UE AMF performs LMF Selection (3). The Target UE AMF sends an Nlmf\_Location\_DetermineLocation Request (4) to LMF. The LMF sends an Nnrf\_NFDiscovery\_Request (5) to NRF. The NRF returns an Nnrf\_NFDiscovery\_Request Response (6) to LMF. The LMF sends an NXXX\_PRUDiscovery Request (7) to PRU AMF(s). PRU AMF(s) choose one or multiple candidate PRU UE(s) (8). The LMF sends a PRU Activation (i.e., clause 6.15.3.2) and Positioning (9) to Target UE AMF. Finally, the Target UE AMF performs Target UE Positioning (10). + +Figure 6.15.3.3-3: MO-LR procedure using PRU/ (AMF-centric) + +Steps 1~4 are same as steps 1~4 defined in clause 6.2 of TS 23.273 [5]. + +Steps 5~10 are same as steps 5~10 in clause 6.15.3.3.1.1. + +## 6.15.3.3.2.2 MO-LR procedure based on Option C in clause 6.15.3.1 + +![Sequence diagram for MO-LR procedure using PRU (AMF-centric) based on Option C. Lifelines: Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, UDM. The sequence starts with a Target UE Triggered Service Request (1) from Target UE to Target UE AMF. The Target UE AMF sends a MO-LR (2a) to PRU(s). PRU(s) sends a wake up indication (2b) to Target UE AMF. The Target UE AMF sends a Nudm_SDM_Get request (3) to UDM. The UDM returns a Nudm_SDM_Get response (4) to Target UE AMF. The Target UE AMF performs LMF Selection (5). The Target UE AMF chooses one or multiple candidate PRU(s) (6). The Target UE AMF sends an Nlmf_Location_DetermineLocation Request (7) to LMF. The LMF sends a PRU Activation (i.e., clause 6.15.3.2) and Positioning (8) to Target UE AMF. Finally, the Target UE AMF performs Target UE Positioning (9).](879d68959f0c0ba370ef82447298ba17_img.jpg) + +Sequence diagram for MO-LR procedure using PRU (AMF-centric) based on Option C. Lifelines: Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, UDM. The sequence starts with a Target UE Triggered Service Request (1) from Target UE to Target UE AMF. The Target UE AMF sends a MO-LR (2a) to PRU(s). PRU(s) sends a wake up indication (2b) to Target UE AMF. The Target UE AMF sends a Nudm\_SDM\_Get request (3) to UDM. The UDM returns a Nudm\_SDM\_Get response (4) to Target UE AMF. The Target UE AMF performs LMF Selection (5). The Target UE AMF chooses one or multiple candidate PRU(s) (6). The Target UE AMF sends an Nlmf\_Location\_DetermineLocation Request (7) to LMF. The LMF sends a PRU Activation (i.e., clause 6.15.3.2) and Positioning (8) to Target UE AMF. Finally, the Target UE AMF performs Target UE Positioning (9). + +Figure 6.15.3.3-4: MO-LR procedure using PRU (AMF-centric) + +Steps 1~2 are same as the steps 1~2 defined in clause 6.2 of TS 23.273 [5]. + +Steps 3~7 are same as steps 4~8 in clause 6.15.3.3.1.2. + +## 6.15.3.3.3 LMF-centric MT-LR + +The LMF-centric MT-LR requests PRU LMF to provide one or multiple candidates PRU(s) in the vicinity of target UE to improve positioning accuracy. This procedure based on option B in clause 6.15.3.1. + +![Sequence diagram for MT-LR procedure using PRU (LMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, PRU LMF(s), GMLC, UDM, NRF, and LCS client. The process involves service requests, location determination, PRU discovery, and positioning activation.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant Target UE + participant PRU(s) + participant NG-RAN + participant Target UE AMF + participant LMF + participant PRU LMF(s) + participant GMLC + participant UDM + participant NRF + participant LCS client + + LCS client->>GMLC: 1. LCS Service Request(GPSI/SUPI, required QoS, supported GAD shapes) + GMLC->>UDM: 2. Nudm_UECM_Get Request/Response (UE ID, NF Type=AMF) + GMLC->>Target UE AMF: 3a. Namf_Location_ProvidePositioningInfo Request (target UE GPSI/SUPI, LCS client type, LCS location type) + rect rgb(255, 255, 255) + Note over Target UE, Target UE AMF: Network Triggered Service Request + end + Target UE AMF->>NG-RAN: 3b. PRU wake up indication + Target UE AMF->>LMF: 4. Nlmf_Location_DetermineLocation Request (LCS correlation ID, target UE location) + LMF->>NRF: 5. Nnrf_NFDiscovery_Request Request (target UE location, indication to discovery the PRU LMF) + NRF-->>LMF: 6. Nnrf_NFDiscovery_Request Response (PRU LMF(s)) + LMF->>PRU LMF(s): 7. NXXX_PRUDiscovery Request (target UE location and/or vicinal location) + rect rgb(255, 255, 255) + Note over PRU LMF(s): choose one or multiple +candidate PRU(s) + end + PRU LMF(s)-->>LMF: 8. NXXX_PRUDiscovery Response (one or multiple PRU(s) information) + rect rgb(255, 255, 255) + Note over PRU(s), LMF: 9. PRU Activation (i.e, clause 6.15.3.2) and Positioning + end + rect rgb(255, 255, 255) + Note over Target UE, LMF: 10. Target UE Positioning + end + +``` + +Sequence diagram for MT-LR procedure using PRU (LMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, PRU LMF(s), GMLC, UDM, NRF, and LCS client. The process involves service requests, location determination, PRU discovery, and positioning activation. + +**Figure 6.15.3.3-5: MT-LR procedure using PRU (LMF-centric)** + +The following additions apply to steps 1~4 compared to steps 1~5 defined in clause 6.1.1 of TS 23.273 [5]. + +- 3b. After AMF receive step 3a, if the target UE support positioning by PRU, e.g. based on the target UE subscription information or the information in target UE context, or based on the target UE positioning capability, e.g. whether target UE support NR positioning, the AMF send an indication to NG-RAN to trigger NG-RAN broadcast the PRU wake up information in target UE camping cell, e.g. the per PLMN indication in posSIB. For those PRU(s) in CM-IDLE/RRC-inactive state, after receive this information, those PRU(s) trigger the service request/RRC-resume to go back to CM-CONNECTED as described in clause 4.2.3.2 of TS 23.502 [3] or clause 9.2.2.4 of TS 38.300 [22]. +- 5. The LMF invokes the Nnrf\_NFDiscovery\_Request Request towards NRF to request the PRU LMF. The service operation includes the target UE location information (e.g. the TAI(s) of target UE), the indication to find the PRU LMF which could serve the target UE positioning. +- 6. Based on the PRU LMF discovery indication and the target UE location information, the NRF return one or multiple PRU UE LMF(s) via Nnrf\_NFDiscovery\_Request Response. +- 7. LMF sends PRU discovery request to PRU LMF to request the PRU information. The message includes the target UE location information and the target UE vicinal location (e.g. the neighbour cell of target UE). +- 8. The PRU LMF choose one or multiple candidate PRU(s) based on the target UE location, PRU capability, location information and mobility state. The PRU LMF invokes PRU discovery response to LMF, includes one or multiple candidate PRU(s). +- 9. The LMF performs the activation procedure as defined in clause 6.15.3.2 to activate the desired PRU(s). LMF also performs one or more of the positioning procedures towards PRU(s) as described in clauses 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 [5]. +- 10. The LMF performs one or more of the positioning procedures towards target UE as described in clauses 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 [5]. + +#### 6.15.3.3.4 LMF-centric MO-LR + +The LMF-centric MO-LR request PRU LMF to provide one or multiple candidates PRU(s) in the vicinity of target UE to improve the positioning accuracy. + +![Sequence diagram for MO-LR procedure using PRU (LMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, PRU LMF(s), and NRF. The process starts with a Service Request from the Target UE, followed by MO-LR and PRU wake-up indications. The LMF then performs location determination and PRU LMF discovery via the NRF. Finally, PRU activation and target UE positioning occur.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant Target UE + participant PRU(s) + participant NG-RAN + participant Target UE AMF + participant LMF + participant PRU LMF(s) + participant NRF + + Note left of Target UE: 1. Target UE Triggered Service Request + Target UE->>Target UE AMF: + Target UE AMF->>PRU(s): 2a. MO-LR + PRU(s)-->>NG-RAN: 2b. PRU wake up indication + Note right of NG-RAN: 3. LMF Selection + Target UE AMF->>LMF: 4. Nlmf_Location_DetermineLocation Request (LCS correlation ID, target UE location) + LMF->>NRF: 5. Nnrf_NFDiscovery_Request Request (target UE location, indication to discovery the PRU LMF) + NRF-->>LMF: 6. Nnrf_NFDiscovery_Request Response (PRU LMF(s)) + LMF->>PRU LMF(s): 7. NXXX_PRUDiscovery Request (target UE location and/or vicinal location) + Note right of PRU LMF(s): choose one or multiple candidate PRU(s) + PRU LMF(s)-->>LMF: 8. NXXX_PRUDiscovery Response (one or multiple PRU(s) information) + Note left of LMF: 9. PRU Activation (i.e., clause 6.15.3.2) and Positioning + Note left of Target UE: 10. Target UE Positioning + +``` + +Sequence diagram for MO-LR procedure using PRU (LMF-centric). The diagram shows interactions between Target UE, PRU(s), NG-RAN, Target UE AMF, LMF, PRU LMF(s), and NRF. The process starts with a Service Request from the Target UE, followed by MO-LR and PRU wake-up indications. The LMF then performs location determination and PRU LMF discovery via the NRF. Finally, PRU activation and target UE positioning occur. + +Figure 6.15.3.3-6: MO-LR procedure using PRU (LMF-centric) + +Steps 1~4 are same as the steps 1~4 defined in clause 6.2 of TS 23.273 [5]. + +Steps 5~10 are same as in clause 6.15.3.3.3. + +## 6.15.4 Impacts on services, entities, and interfaces + +UE: + +- Support operate as PRU and send PRU information to 5GC. + +AMF: + +- store PRU information in the UE context. +- when receive the PRU registration, sends message to NRF to indicate PRU existence in certain area. +- aware of the PRU information if there are UE(s) can be operated as PRU(s). +- choose one or multiple candidate PRU(s) and response to LMF. +- After target UE positioning is triggered, the target UE AMF send an PRU wake up indication to NG-RAN to trigger NG-RAN broadcast this information in target UE camping cell. + +LMF: + +- store PRU information. +- when receive the PRU registration, send message to NRF to indicate PRU existence in certain area. +- aware of the PRU information if there are UE(s) can be operated as PRU(s). +- choose one or multiple candidate PRU(s). + +NRF: + +- Support NF profile update once receive the PRU existence indication. +- Support selection of AMF(s)/LMF(s) that have registered with PRU. + +UDM: + +- store PRU(s) information. + +NG-RAN: + +- Support broadcast the PRU wake up information in target UE camping cell. + +UE: + +- After receive the PRU wake up indication, trigger to perform the service request/RRC resume procedure. + +## 6.16 Solution #16: Support of Positioning Reference Units + +### 6.16.1 Introduction + +This solution addresses the questions related to Positioning Reference Units (PRU) in KI#7: support of Positioning Reference Units and Reference UEs. + +### 6.16.2 Functional Description + +PRU Capability Verification: + +- During Registration procedure, the UE includes PRU capability in the Registration Request. The AMF verifies the capability based on the subscription data received from UDM. + +PRU Information Storage: + +- The PRU information is stored in the LMF: after successful Registration procedure of PRU, the AMF initiates the 5GC-NI-LR procedure (only steps 2 - 4 of the procedure are performed) to store PRU information in the LMF. +- The PRU information is stored in the NRF: in order to support that the PRU assists positioning of all UEs, but not the UEs in the service area of the LMF storing the PRU information, the LMF may further store PRU information in the LMF profile in the NRF. +- The PRU information includes LCS correlation ID, serving cell ID, serving AMF ID, PRU measurements and PRU location. + +PRU Utilization: + +- The LMF decides to use the PRU to assist UE positioning based on the required QoS. +- The LMF obtain PRU measurements by initiating PRU positioning or request the information from the serving LMF of the PRU. The LMF obtains the serving LMF of the PRU from NRF. +- To fully utilize the PRU(s) in the same camping cell of target UE, target UE AMF can send the PRU wake up indication to the target UE NG-RAN, then target UE NG-RAN broadcast this information in target UE camping cell, then all candidate PRU(s) could listen this information and go back to connected state. + +**Editor's note:** RAN WG coordination is needed. + +## 6.16.3 Procedures + +### 6.16.3.1 PRU Registration + +![Sequence diagram of the PRU Registration procedure. Lifelines: UE (PRU), AMF, LMF, UDM, NRF. The sequence starts with the UE (PRU) sending a Registration Request (PRU capability) to the AMF. The AMF sends a Nudm_SDM_Get to the UDM. The UDM returns a Registration Accept to the AMF. The AMF sends a Nlmf_Location_DetermineLocation Request (PRU indication, LCS correlation ID) to the LMF. The LMF performs UE positioning. The LMF sends a Nlmf_Location_DetermineLocation Response to the AMF. The LMF sends a Nnrf_NFManagement_NFUpdate Request (NF type=LMF, registered PRU information) to the NRF. The NRF returns a Nnrf_NFManagement_NFUpdate Response to the LMF.](60a40901e77feeb97ab6cf9c6d9418c3_img.jpg) + +``` + +sequenceDiagram + participant UE as UE (PRU) + participant AMF + participant LMF + participant UDM + participant NRF + + Note left of UE: 1. Registration Request (PRU capability) + UE->>AMF: 1. Registration Request (PRU capability) + Note right of AMF: 2. Nudm_SDM_Get + AMF->>UDM: 2. Nudm_SDM_Get + Note right of UDM: 3. Registration Accept + UDM->>AMF: 3. Registration Accept + Note right of AMF: 4. Nlmf_Location_DetermineLocation Request (PRU indication, LCS correlation ID) + AMF->>LMF: 4. Nlmf_Location_DetermineLocation Request (PRU indication, LCS correlation ID) + Note right of LMF: 5. UE positioning + LMF->>LMF: 5. UE positioning + Note right of LMF: 6. Nlmf_Location_DetermineLocation Response + LMF->>AMF: 6. Nlmf_Location_DetermineLocation Response + Note right of LMF: 7. Nnrf_NFManagement_NFUpdate Request (NF type=LMF, registered PRU information) + LMF->>NRF: 7. Nnrf_NFManagement_NFUpdate Request (NF type=LMF, registered PRU information) + Note right of NRF: 8. Nnrf_NFManagement_NFUpdate Response + NRF-->>LMF: 8. Nnrf_NFManagement_NFUpdate Response + +``` + +Sequence diagram of the PRU Registration procedure. Lifelines: UE (PRU), AMF, LMF, UDM, NRF. The sequence starts with the UE (PRU) sending a Registration Request (PRU capability) to the AMF. The AMF sends a Nudm\_SDM\_Get to the UDM. The UDM returns a Registration Accept to the AMF. The AMF sends a Nlmf\_Location\_DetermineLocation Request (PRU indication, LCS correlation ID) to the LMF. The LMF performs UE positioning. The LMF sends a Nlmf\_Location\_DetermineLocation Response to the AMF. The LMF sends a Nnrf\_NFManagement\_NFUpdate Request (NF type=LMF, registered PRU information) to the NRF. The NRF returns a Nnrf\_NFManagement\_NFUpdate Response to the LMF. + +**Figure 6.16.3.1-1: PRU Registration procedure** + +1. PRU sends Registration Request to AMF. The message includes PRU capability. +2. The AMF invokes a Nudm\_SDM\_Get service operation towards the UDM to obtain subscription data of the UE to verify whether the subscription data includes the PRU subscription. If not, the AMF rejects the Registration Request. +3. The AMF returns Registration Accept to PRU. +4. After the successful registration of PRU, the AMF invokes a Nlmf\_Location\_DetermineLocation Request to LMF. The request includes PRU indication and LCS correlation ID. +5. The LMF triggers UE positioning procedure to obtain measurements and location of PRU. The LMF stores the PRU information locally, e.g. PRU serving cell ID, serving AMF ID, LCS correlation ID, PRU measurements, PRU location. +6. The LMF invokes a Nlmf\_Location\_DetermineLocation Response to AMF. +7. [Conditional] If the LMF decides to store PRU information in the NRF, e.g. the serving cell of the PRU is near the boundary of the service area of the LMF, the PRU measurements can also be used by other LMF to assist UE positioning, the LMF invokes a Nnrf\_NFManagement\_NFUpdate Request to NRF. The service operation includes NF type=LMF, supported PRU information, e.g. PRU serving cell ID, PRU location, LCS correlation ID, serving AMF ID. +8. [Conditional] If step 7 is performed, the NRF returns a Nnrf\_NFManagement\_NFUpdate Response to LMF. + +## 6.16.3.2 PRU Utilization + +![Sequence diagram of PRU Utilization Registration procedure. Lifelines: PRU, NG-RAN, AMF, LMF, NRF, Serving LMF of PRU. The sequence starts with 0a. triggers for target UE Positioning (AMF to LMF), followed by 0b. PRU wake up indication (AMF to NG-RAN). Step 1: Nlmf_Location_DetermineLocation Request (AMF to LMF). Step 2: PRU Positioning (AMF to PRU). Step 3: Nnrf_NFDiscovery Request (LMF to NRF). Step 4: Nnrf_NFDiscovery Response (NRF to LMF). Step 5: Nlmf_Location_DetermineLocation Request (LMF to Serving LMF of PRU). Step 6: PRU Positioning (Serving LMF of PRU to PRU). Step 7: Nlmf_Location_DetermineLocation Response (Serving LMF of PRU to LMF). Step 8: Nlmf_Location_DetermineLocation Response (LMF to AMF).](7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg) + +``` + +sequenceDiagram + participant PRU + participant NG-RAN + participant AMF + participant LMF + participant NRF + participant SLMF as Serving LMF of PRU + + Note right of AMF: 0a. triggers for target UE Positioning + AMF->>NG-RAN: 0b. PRU wake up indication + AMF->>LMF: 1. Nlmf_Location_DetermineLocation Request (serving cell ID of target UE) + Note over AMF, PRU: 2. PRU Positioning + LMF->>NRF: 3. Nnrf_NFDiscovery Request (NF type=LMF, serving cell ID of target UE) + NRF-->>LMF: 4. Nnrf_NFDiscovery Response (LMF ID, PRU information) + LMF->>SLMF: 5. Nlmf_Location_DetermineLocation Request (serving cell ID of PRU, LCS correlation ID) + Note over SLMF, PRU: 6. PRU Positioning + SLMF-->>LMF: 7. Nlmf_Location_DetermineLocation Response + LMF-->>AMF: 8. Nlmf_Location_DetermineLocation Response (UE location) + +``` + +Sequence diagram of PRU Utilization Registration procedure. Lifelines: PRU, NG-RAN, AMF, LMF, NRF, Serving LMF of PRU. The sequence starts with 0a. triggers for target UE Positioning (AMF to LMF), followed by 0b. PRU wake up indication (AMF to NG-RAN). Step 1: Nlmf\_Location\_DetermineLocation Request (AMF to LMF). Step 2: PRU Positioning (AMF to PRU). Step 3: Nnrf\_NFDiscovery Request (LMF to NRF). Step 4: Nnrf\_NFDiscovery Response (NRF to LMF). Step 5: Nlmf\_Location\_DetermineLocation Request (LMF to Serving LMF of PRU). Step 6: PRU Positioning (Serving LMF of PRU to PRU). Step 7: Nlmf\_Location\_DetermineLocation Response (Serving LMF of PRU to LMF). Step 8: Nlmf\_Location\_DetermineLocation Response (LMF to AMF). + +Figure 6.16.3.2-1: PRU Utilization Registration procedure + +- 0a. The trigger for target UE positioning happens, e.g. the AMF receives Nnamf\_Location\_ProvidePositioningInfo Request service operation from GMLC or receives MO-LR Request from UE. +- 0b. If the target UE support positioning by PRU, e.g. based on the target UE subscription information or the information in target UE context, or based on the target UE positioning capability, e.g. whether target UE support NR positioning, the AMF send an indication to NG-RAN to trigger NG-RAN broadcast the PRU wake up information in target UE camping cell, e.g. the per PLMN indication in posSIB. For those PRU(s) in CM-IDLE/RRC-inactive state, after receive this information, those PRU(s) trigger the service request/RRC-resume to go back to CM-CONNECTED as described in clause 4.2.3.2 of TS 23.502 [3] or clause 9.2.2.4 of TS 38.300 [22]. +1. The AMF invokes a Nlmf\_Location\_DetermineLocation Request to LMF. + 2. The LMF triggers UE positioning procedure to obtain measurements from PRU. + 3. [Conditional] If the LMF decides to obtain PRU information from NRF, e.g. the PRU(s) stored in the LMF is not available to assist UE positioning, the LMF invokes a Nnrf\_NFDiscovery Request to NRF. The request includes NF type=LMF, cell ID or cell list, PRU indication. + 4. [Conditional] The NRF returns a Nnrf\_NFDiscovery Response to LMF. The response includes LMF ID and PRU information. + 5. [Conditional] If LMF receives PRU information and the serving LMF of the PRU from NRF, the LMF sends the Nlmf\_Location\_DetermineLocation Request to the serving LMF of the PRU. + 6. [Conditional] If step 5 is performed, the serving LMF of PRU triggers UE positioning procedure to obtain measurements from PRU. + 7. [Conditional] If step 6 is performed, the serving LMF of PRU sends the Nlmf\_Location\_DetermineLocation Response to the serving LMF. + 8. The LMF calculates UE location based on the measurements obtained from PRU in step 4 and step 7 and invokes a Nlmf\_Location\_DetermineLocation Response to AMF. + +## 6.16.4 Impacts on services, entities, and interfaces + +### AMF: + +- During Registration procedure, receive PRU capability from PRU and verify the capability using the subscription data. +- After PRU successful registration, AMF initiates the 5GC-NI-LR procedure (only steps 2 - 4 are performed) to store PRU information in LMF. The AMF includes PRU indication in step 2 of the 5GC-NI-LR procedure. +- After target UE positioning is triggered, the target UE AMF send an PRU wake up indication to NG-RAN to trigger NG-RAN broadcast this information in target UE camping cell. + +### LMF: + +- During the 5GC-NI-LR procedure, if PRU indication is received from AMF, the LMF stores PRU information locally or stores PRU information in NRF. +- Decide to use PRU to assist UE positioning based on the required QoS, obtain available PRU based on the locally stored information or from NRF. +- To obtain PRU measurements to assist UE positioning, initiate positioning procedure for PRU or request PRU measurements from serving LMF of the PRU based on the received information from NRF. + +### PRU: + +- Send Registration Request including PRU capability to AMF. + +### NRF: + +- Store information of the PRU which is in the service area of LMF in LMF profile. +- Provides PRU information to LMF. + +### NG-RAN: + +- Support broadcast the PRU wake up information in target UE camping cell. + +### UE: + +- After receive the PRU wake up indication, trigger to perform the service request/RRC resume procedure. + +## 6.17 Solution #17: Support for 5GS Localization via Reference UE + +### 6.17.1 Introduction + +This solution to KI#7 as described in clause 5.7 proposes a mechanism for the 5GS to assist determining the location of a set of UEs via another UE known as reference UE. The solution addresses use cases mentioned in clause 5.7 such as the set of UEs not having LoS path with the RAN node(s), or the opportunity to reduce the signalling involved in providing location services including positioning and tracking to a set of UEs. Multiple reference UEs may also be utilized to assist with the location of the target UE. + +### 6.17.2 Functional Description + +At a high level, the functional description of this solution is as follows: + +- The LCS architecture is leveraged to provide location services to a target UE assisted by one or multiple reference UE(s). + +The solution requires LMF to support location requests via reference UE and processing of the location estimation results. + +- A reference UE in this solution could be co-located with a PRU since both entities behave like UEs assisting with the positioning performance of a target UE. + +NOTE: In this solution it is assumed that reference UEs have known location obtained via Uu positioning. + +### 6.17.3 Procedures + +![Sequence diagram illustrating the support for 5GS Localization via Reference UE. The diagram shows interactions between UE_T, UE_1, UE_N, AMF, LMF, ProSe AS/PCF, GMLC, UDM, and External client. The steps are: 0) Registration (reference and target UEs); 1) Location request for target UE from External client to GMLC; 2) Setup of location information as per 5GC-MT-LR procedure; 3) Reference UE(s) identification by LMF; 4) ProSe configuration for location reporting including ProSe AS/PCF; 5) Positioning Request from LMF to UE_1; 6) Reference UE based positioning; 7) Multiple UE location data from UE_1 to LMF; 8) Processing of Location data by LMF; 9) Nlmf_Location_DetermineLocation Response from LMF to GMLC; 10) Nlmf_Location_EventNotify from LMF to GMLC; 11) LCS service response from GMLC to External client.](bc6f20871b4f01c61470306c304fc9fe_img.jpg) + +Sequence diagram illustrating the support for 5GS Localization via Reference UE. The diagram shows interactions between UE\_T, UE\_1, UE\_N, AMF, LMF, ProSe AS/PCF, GMLC, UDM, and External client. The steps are: 0) Registration (reference and target UEs); 1) Location request for target UE from External client to GMLC; 2) Setup of location information as per 5GC-MT-LR procedure; 3) Reference UE(s) identification by LMF; 4) ProSe configuration for location reporting including ProSe AS/PCF; 5) Positioning Request from LMF to UE\_1; 6) Reference UE based positioning; 7) Multiple UE location data from UE\_1 to LMF; 8) Processing of Location data by LMF; 9) Nlmf\_Location\_DetermineLocation Response from LMF to GMLC; 10) Nlmf\_Location\_EventNotify from LMF to GMLC; 11) LCS service response from GMLC to External client. + +**Figure 6.17.3-1: Support for 5GS Localization via Reference UE** + +0. The reference and target UEs register to the network. An indication identifying reference UE(s) may be provided to LMF by AMF. +1. The LCS client request location services for a target UE to the 5GS. +2. After receiving the location request from the LCS client, the LMF starts the localization procedures as in a default scenario as shown in clause 6.1.2 of TS 23.273 [5]. +3. The LMF may identify one or a set of reference UEs suitable to provide location information and/or assistance location data related to the target UE +4. Optionally, ProSe capabilities (e.g. for ranging or sidelink positioning) may be used by the reference UEs to collect location information or location assistance data from the target UE. + +NOTE 1: The functionality in step 4 is out of scope of this study but details can be found in TR 23.700-86 [17]. + +5. The LMF sends location request for a target UE to one or multiple reference UEs using LPP. + +NOTE 2: AS level procedures required between NG-RAN and the reference UE are determined by RAN WGs. + +6. The reference UE(s) will initiate the positioning of the target UE. This can include providing target UE related location measurements or assistance data. The target UE will provide the location assistance data (or measurements) to the one or multiple reference UEs. + +NOTE 3: This solution is agnostic as to what type of positioning mechanism is employed between reference UEs and target UE, e.g. Uu based positioning, sidelink positioning, etc. + +7. The reference UE(s) will relay location reporting data back to the LMF via LPP. +8. The LMF will process the data to combine and/or downselect multiple inputs from multiple Reference UE to generate the best possible estimate of the target UE location. +- 9-11. Location information is passed onto the LCS client through the AMF and GMLC. These steps are not changed from the default location responses in clause 6.1.2 of TS 23.273 [5]. + +## 6.17.4 Impacts on services, entities and interfaces + +### AMF + +- To support registration of reference UEs. + +### LMF + +- To support location request via multiple reference UEs. +- To support processing of multiple location estimations of same target UE via multiple reference UEs. + +### UE + +- As a reference UE to be able to provide location related measurements or any assistance data w.r.t. a target UE to 5GC. + +## 6.18 Solution #18: Location Verification for Satellite Access assisted by NWDAF Analytics + +### 6.18.1 Introduction + +This solution proposes a mechanism for location verification of the UE location provided via satellite access by leveraging NWDAF analytics in the 5GC. The solution addresses KI#9 as it enables the AMF to receive statistics and predictions on the UE location, hence making it easier to determine whether the potentially inaccurate location information provided by the UE is reliable and trustable or not. + +### 6.18.2 Functional description + +At a high level, the functional description of this solution is as follows: + +- The UE provides an initial location to NG-RAN/AMF via satellite access, and the location verification process at the 5GC is triggered. +- The AMF discovers an NWDAF instance capable of providing UE related analytics on the UE that provided its location via satellite access. If available, the selected NWDAF instance should have analytics aggregation analytics to retrieve UE related analytics from other NWDAF instances. +- If the selected NWDAF instance has aggregator capabilities, it discovers and collects UE related analytics from other NWDAF instance(s) following the procedures specified in TS 23.288 [9]. +- The NWDAF instance with potential aggregator capabilities aggregates analytics (if collected), derives its own analytics, and delivers them to the AMF. +- The AMF uses the received analytics as part of its decision on whether the UE location should be accepted or rejected as provided by the UE. + +### 6.18.3 Procedures + +![Sequence diagram illustrating the procedure for location verification for satellite access assisted by NWDAF analytics. The diagram shows interactions between UE, NG-RAN, AMF A, UDM, NWDAF A (aggregator), NRF, NF(s), and NWDAF(s).](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF_A as AMF A + participant UDM + participant NWDAF_A as NWDAF A (aggregator) + participant NRF + participant NF_s as NF(s) + participant NWDAF_s as NWDAF(s) + + Note right of NG-RAN: 2. AMF selection + UE->>NG-RAN: 1. UE location + NG-RAN->>AMF_A: 3. UE location reporting + AMF_A->>UDM: 4. UE subscriber profile retrieval + AMF_A->>NRF: 5. NWDAF discovery (aggregator) + AMF_A->>NWDAF_A: 6. Subscribe to receive analytics on UE behavior/ mobility pattern/other + NWDAF_A->>UDM: 7. UDM registration + Note right of AMF_A: 8. NWDAF(s) discovery + AMF_A->>NWDAF_s: 9. Request UE related analytics from other NWDAF instances + NWDAF_s->>NF_s: 10. Input data collection + Note right of NWDAF_s: 11. Derive analytics + NWDAF_s->>NWDAF_A: 12. provide UE related analytics to aggregator NWDAF + Note right of NWDAF_A: 13. Derive/Aggregate analytics + NWDAF_A->>AMF_A: 14. Response on requested analytics on UE behavior/ mobility pattern/other + Note right of AMF_A: 15. AMF decision + AMF_A->>UE: 16. AMF may reject or accept UE location depending on the outcome of analytics on UE location + +``` + +Sequence diagram illustrating the procedure for location verification for satellite access assisted by NWDAF analytics. The diagram shows interactions between UE, NG-RAN, AMF A, UDM, NWDAF A (aggregator), NRF, NF(s), and NWDAF(s). + +**Figure 6.18.2-1: Procedure for location verification for satellite access assisted by NWDAF analytics** + +1. UE reports location to the NG-RAN via satellite access. +2. NG-RAN selects a suitable AMF based on reported UE location (e.g. AMF A, serving Country A). +3. NG-RAN indicates to the AMF the need to verify/confirm the UE location provided via satellite access. +4. AMF retrieves the subscriber profile of the UE from the UDM. +5. If not done previously, AMF discovers NWDAF according to clause 5.2 of TS 23.288 [9] and clause 6.3.13 of TS 23.501 [2], if available supporting analytics aggregation as described in clause 6.1A.2 of TS 23.288 [9]. In addition, AMF uses NWDAF Serving Area information, and NWDAF location information to select the appropriate NWDAF instance. +6. AMF requests or subscribes to UE related analytics (e.g. expected UE behaviour, abnormal behaviour, UE mobility) for one or more Analytic IDs in a given Area of Interest from a NWDAF that covers the country where the UE reported its location. When the AMF requests or subscribes to analytics containing UE location information, it may use the Analytics ID "UE Mobility" supported in Release 17 with location information granularity of TA or cell. In addition, to increase the accuracy and reliability, the AMF may use other Analytics IDs supported in Release 18 with finer location information granularity than TA or cell. + +NOTE 1: The available granularity of UE location information will be decided when FS\_eNA\_ph3 reaches conclusions, and which fine granularity Analytics ID can be consumed by AMF for location verification purposes in satellite access depend on such conclusion and will be finalized during normative work. + +7. [OPTIONAL] The selected NWDAF instance may register with the UDM for the UE that it is collecting data for and for the related Analytic ID(s). + +8. [OPTIONAL] If needed and the selected NWDAF instance has analytics aggregation capability, the NWDAF for which the AMF requested analytics discovers other NWDAF instances that may provide relevant UE related analytics on the UE ID that provided its location in step 1. +9. [OPTIONAL] The aggregator NWDAF requests UE related analytics from other NWDAF(s) on the UE which initially provided its location information to NG-RAN. +10. [OPTIONAL] If needed, other NWDAFs contacted by the aggregator NWDAF may collect data from other NFs (AMFs, SMFs, etc.) related to this UE (e.g. previous locations in other countries, any reported UE abnormal behaviour, etc.). +11. [OPTIONAL] The NWDAF(s) contacted by the aggregator NWDAF derive(s) UE related analytics for the UE in the area it is responsible for, e.g. (part of) a country. +12. [OPTIONAL] The NWDAF(s) contacted by the aggregator NWDAF report(s) their analytics (UE mobility, UE abnormal behaviour, etc.) to the aggregator NWDAF. +13. The aggregator NWDAF performs aggregation of the reported analytics and derives analytics. +14. The aggregator NWDAF provides (potentially aggregated) analytics to the AMF. +15. AMF decides whether the UE should or should not be allowed access given the currently reported location. +16. AMF interacts with NG-RAN and/or the UE to convey the decision. For example, based on the reported UE analytics (e.g. UE behaviour, UE location), the AMF and/ or NG-RAN may behave as follows: + - a) In case of UE in initial access, the AMF may accept or reject UE Registration Request to the UE reported location. In case of rejection, the AMF may provide a cause value to the UE and/or NG-RAN (e.g. "inaccurate/wrong Location", "Location is not supported", or any other naming). + - b) AMF may forward the full, part or a modified version of the analytics (e.g. UE behaviour, UE location) to NG-RAN which may act upon it. For example, NG-RAN may release the UE in case of an "unexpected UE location". + - c) AMF may decide to initiate UE release procedure with the NG-RAN, and indicates the cause of UE context release as UE (e.g. "inaccurate/wrong/unexpected UE Location", "UE Location is not supported", or any other naming). + +NOTE 2: The AMF may use additional information other than analytics to increase the reliability of location verification for satellite access. It is up to RAN WGs to decide if additional information to AMF is provided by NG-RAN. + +NOTE 3: To which extent NWDAF analytics can enhance the reliability of the location verification is for RAN WGs to verify. + +#### 6.18.4 Impacts on services, entities and interfaces + +##### AMF: + +- To trigger UE related analytics request/subscription after NG-RAN requests AMF UE location verification for satellite access. +- To discover an NWDAF instance with aggregator capabilities for UE related analytics. +- To verify UE location provided via satellite access based on NWDAF analytics, report to NG-RAN and/or UE, and initiate any necessary action. + +##### NWDAF: + +- To support aggregation of UE related analytics for location verification purposes. + +## 6.19 Solution #19: Support of Low Latency via User Plane + +### 6.19.1 Introduction + +This solution addresses KI#1 (Architectural Enhancement to support User Plane positioning and KI#10 (Support of Reduced Latency). + +The main principles of this solution are as follows: + +1. The solution applies to event reporting for a periodic or triggered deferred 5GC-MT-LR. +2. The target UE uses a user plane connection to report events to the LCS Client or AF, either directly or via the LMF or H-GMLC. +3. When reporting directly to the LCS Client or AF or reporting via an H-GMLC, the UE sends a supplementary services event report (e.g. as defined in TS 24.080 [21]) over the user plane connection with a location estimate included. This could significantly reduce end-to-end latency because the event report no longer needs to be transferred via control plane through the NG-RAN, AMF, LMF, GMLC and possibly NEF. Signalling efficiency is likewise increased. +4. When reporting via the LMF, the UE sends a supplementary services event report over the user plane connection to the LMF with one or more LPP messages included in the event report. The LMF then verifies or determines a location estimate and sends the event report with the location estimate to the LCS Client or AF over a second user plane connection. This can still reduce latency and increase signalling efficiency. +5. The control plane associations between the UE and LMF, LMF and V-GMLC/H-GMLC and H-GMLC and LCS Client or NEF and AF are retained to allow the status of event reporting to be conveyed to the H-GMLC (and NEF if used) and to support cancellation of event reporting using the existing control plane procedures in clauses 6.3.2 and 6.3.3. in TS 23.273 [5]. + +### 6.19.2 Functional Description + +#### 6.19.2.1 Architecture + +There are no changes to 5GS architecture as defined in TS 23.501 [2] and TS 23.273 [5]. + +#### 6.19.2.2 Protocol Layering + +Location event reports are transferred from a UE to an LCS Client or AF using data transport through a UPF. Transfer can be direct or can be via an LMF or H-GMLC. Transfer via an LMF allows the LMF to determine or verify a location estimate and, if needed, exchange LPP messages with the target UE via user plane to perform positioning of the target UE. Transfer via an H-GMLC enables the H-GMLC to monitor event reporting by the target UE and to avoid direct UE to LCS Client or AF data interaction which might be a security risk to either entity. + +The associated protocol layering is shown in Figure 6.19.2.2-1. A version of TLS (e.g. TLS 1.2 defined in RFC 5246 [20]) is used to enable secure data connection. The LMF or H-GMLC shown in Figure 6.19.2.2-1 is only present when event reports are transferred through the LMF or H-GMLC and not directly to the LCS Client or AF. + +NOTE: Security aspects of reporting location to an AF or LCS Client via a user plane will need to be verified or defined by SA WG3. + +![Figure 6.19.2.2-1: Protocol Layering for User Plane Transfer of Event Reports. This diagram shows the protocol stack for data transfer between a UE and an LCS Client or AF via a RAN Node, UPF, and LMF or H-GMLC. The stack layers from top to bottom are: Supp Svcs (or LPP), TLS, TCP, IP, and RAN Protocols (on the UE side) or Lower Layer Protocols (on the other side). The RAN Node contains a 'Relay' component that switches between RAN Protocols and 5GC Protocols. The UPF contains IP and 5GC Protocols. The LMF or H-GMLC contains a dashed box with Supp Svcs (or LPP), TLS, TCP, and IP, with Lower Layer Protocols below it. Vertical dashed lines labeled N3 and N6 indicate the interfaces between the RAN Node and UPF, and between the UPF and LMF or H-GMLC respectively.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +Figure 6.19.2.2-1: Protocol Layering for User Plane Transfer of Event Reports. This diagram shows the protocol stack for data transfer between a UE and an LCS Client or AF via a RAN Node, UPF, and LMF or H-GMLC. The stack layers from top to bottom are: Supp Svcs (or LPP), TLS, TCP, IP, and RAN Protocols (on the UE side) or Lower Layer Protocols (on the other side). The RAN Node contains a 'Relay' component that switches between RAN Protocols and 5GC Protocols. The UPF contains IP and 5GC Protocols. The LMF or H-GMLC contains a dashed box with Supp Svcs (or LPP), TLS, TCP, and IP, with Lower Layer Protocols below it. Vertical dashed lines labeled N3 and N6 indicate the interfaces between the RAN Node and UPF, and between the UPF and LMF or H-GMLC respectively. + +Figure 6.19.2.2-1: Protocol Layering for User Plane Transfer of Event Reports + +## 6.19.3 Procedures + +### 6.19.3.1 Event Reporting from a UE directly to an LCS Client or AF + +Figure 6.19.3.1-1 shows a procedure for event reporting from a UE directly to an LCS Client or AF when a User Plane connection is established directly from the UE to the LCS Client or AF with no intermediate LMF or H-GMLC. This procedure is applicable when UE based position methods or standalone position methods are used by the UE. + +![Figure 6.19.3.1-1: Event Reporting from a UE directly to an LCS Client or AF. This sequence diagram shows the interaction between UE, NG-RAN, AMF, UPF, LMF, H-GMLC, LCS Client, NEF, and AF. The sequence of steps is: 1. Deferred 5GC-MT-LR Procedure for Periodic or Triggered Location Events in TS 23.273 Clause 6.3.1 Steps 1-21; 2. Establish secure TCP/IP Connection from UE to LCS Client or AF; 3. Request Assistance Data from LMF via Control Plane (dashed box); 4. Event Detected (at UE); 5. Location Determination (at UE); 6. Event Report (location estimate) from UE to LCS Client and AF; 7. Event Report Acknowledgment from LCS Client to UE; 8. Event Detected (at UE); 9. Transfer Cumulative Event Report to LCS Client or AF via Control Plane as in steps 25-30 of TS 23.273 Clause 6.3.1.](8a94796989f4fcba2688c4faa7991538_img.jpg) + +Figure 6.19.3.1-1: Event Reporting from a UE directly to an LCS Client or AF. This sequence diagram shows the interaction between UE, NG-RAN, AMF, UPF, LMF, H-GMLC, LCS Client, NEF, and AF. The sequence of steps is: 1. Deferred 5GC-MT-LR Procedure for Periodic or Triggered Location Events in TS 23.273 Clause 6.3.1 Steps 1-21; 2. Establish secure TCP/IP Connection from UE to LCS Client or AF; 3. Request Assistance Data from LMF via Control Plane (dashed box); 4. Event Detected (at UE); 5. Location Determination (at UE); 6. Event Report (location estimate) from UE to LCS Client and AF; 7. Event Report Acknowledgment from LCS Client to UE; 8. Event Detected (at UE); 9. Transfer Cumulative Event Report to LCS Client or AF via Control Plane as in steps 25-30 of TS 23.273 Clause 6.3.1. + +Figure 6.19.3.1-1: Event Reporting from a UE directly to an LCS Client or AF + +1. Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 of TS 23.273 [5] are performed with the following differences. + - At step 1, the LCS Client or AF includes a request for user plane reporting in the Location Request and includes an IP address or FQDN for the user plane connection and security information to enable a secure connection. + +- At steps 4, 5, 14 and 16, the request for user plane reporting and the IP address or FQDN and the security information are forwarded in sequence to the V-GMLC (if used), AMF, LMF and target UE. The type of user plane connection (direct to the LCS Client or AF) and criteria for sending cumulative event reports at step 9 are also conveyed to the target UE from the H-GMLC. The criteria can include a periodic time interval or the sending of a certain number of event reports via user plane at step 6. + - At steps 17-21, the target UE indicates to the LMF, H-GMLC and LCS Client or AF whether event reporting via user plane can be supported by the target UE. If event reporting via user plane cannot be supported, the target UE uses the procedure in clause 6.3.1 of TS 23.273 [5] to send events reports via Control Plane. +2. The UE establishes a secure TCP/IP connection to the LCS Client or AF using the IP address or FQDN and security information received at step 1. + 3. If the UE needs assistance data to help determine a location later at step 5, the UE may send a positioning LPP request to the LMF via Control Plane using the deferred Routing ID received in step 16 of the procedure in clause 6.3.1 in TS 23.273 [5] to identify and route the request to the correct LMF. The LMF then provides the requested assistance data to the UE by returning an LPP positioning message via Control Plane. Preferably, the UE requests assistance data some time before location determination is needed to avoid increasing latency. The LMF may use the LMF change procedure in clause 6.4 in TS 23.273 [5] to forward the request for assistance data to a better LMF if the current LMF cannot provide assistance data for the current UE location (e.g. the current UE TAI or CGI). In this case, the new LMF can return the assistance data to the UE via the original LMF to avoid changing the LMF association in the UE and H-GMLC or V-GMLC. + 4. The UE monitors for and detects the occurrence of a trigger or periodic event as described for step 22 of the procedure in clause 6.3.1 of TS 23.273 [5]. + 5. The UE obtains location measurements and determines a current location, possibly using assistance data obtained at step 3. +- NOTE: Obtaining a location at step 5 limits the UE to using UE based or standalone position methods. If UE assisted position methods need to be used, the LMF can use the procedure described in clause 6.19.3.3 instead of the procedure in this clause. +6. The UE sends a supplementary services Event Report to the LCS Client or AF over the secure TCP/IP Connection established at step 2. The event report indicates the type of event being reported and includes the location determined at step 5. + 7. The LCS Client or AF returns a supplementary services Event Report Acknowledgment to the UE over the secure TCP/IP Connection established at step 2. + 8. The UE continues to monitor for and detect further trigger or periodic events as at step 4 and repeats steps 5-7 for each detected trigger or periodic event. + 9. Based on the criteria received by the UE for sending of cumulative event reports (e.g. the expiration of a periodic timer or the sending of certain number of event reports at step 6), the UE sends a cumulative event report to the LMF, H-GMLC and LCS Client or AF over the control plane portion of the periodic or triggered deferred 5GC-MT-LR using steps 25-30 of the procedure in clause 6.3.1 of TS 23.273 [5]. The cumulative event report indicates to the LMF, H-GMLC and External LCS Client or AF that the control plane portion of the periodic or triggered deferred 5GC-MT-LR is still operational, that the UE is still reporting events (e.g. is still powered on and in network coverage) and may include statistics on the events reported since the last cumulative event report was sent (e.g. the number of event reports). + +### 6.19.3.2 Event Reporting from a UE to an LCS Client or AF via an H-GMLC + +Figure 6.19.3.2-1 shows a procedure for event reporting from a UE to an LCS Client or AF when a User Plane connection is established to the LCS Client or AF via the H-GMLC. This procedure is applicable when UE based position methods or standalone position methods are used by the UE. + +![Sequence diagram showing Event Reporting from a UE to an LCS Client or AF via the H-GMLC. The diagram illustrates the interaction between the UE, NG-RAN, AMF, UPF, LMF, H-GMLC, LCS Client, NEF, and AF. The process starts with a deferred 5GC-MT-LR procedure, followed by secure TCP/IP connections being established between the UE and H-GMLC, and between the H-GMLC and the LCS Client or AF. The UE then requests assistance data from the LMF, detects an event, determines its location, and sends an event report to the H-GMLC, which in turn reports it to the LCS Client or AF. Acknowledgments are returned at each step.](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UPF + participant LMF + participant H-GMLC + participant LCS Client + participant NEF + participant AF + + Note over UE, AF: 1. Deferred 5GC-MT-LR Procedure for Periodic or Triggered Location Events in TS 23.273 Clause 6.3.1 Steps 1-21 + Note over UE, H-GMLC: 2. Establish secure TCP/IP Connection from UE to H-GMLC + Note over H-GMLC, LCS Client: 3. Establish secure TCP/IP Connection from H-GMLC to LCS Client or AF + Note over UE, LMF: 4. Request Assistance Data from LMF via Control Plane + Note over UE: 5. Event Detected + Note over UE: 6. Location Determination + UE->>H-GMLC: 7. Event Report (location estimate) + H-GMLC->>LCS Client: 8. Event Report (location estimate) + LCS Client->>H-GMLC: 9. Event Report Acknowledgment + H-GMLC->>UE: 10. Event Report Acknowledgment + Note over UE: 11. Event Detected + +``` + +Sequence diagram showing Event Reporting from a UE to an LCS Client or AF via the H-GMLC. The diagram illustrates the interaction between the UE, NG-RAN, AMF, UPF, LMF, H-GMLC, LCS Client, NEF, and AF. The process starts with a deferred 5GC-MT-LR procedure, followed by secure TCP/IP connections being established between the UE and H-GMLC, and between the H-GMLC and the LCS Client or AF. The UE then requests assistance data from the LMF, detects an event, determines its location, and sends an event report to the H-GMLC, which in turn reports it to the LCS Client or AF. Acknowledgments are returned at each step. + +**Figure 6.19.3.2-1: Event Reporting from a UE to an LCS Client or AF via the H-GMLC** + +- Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 of TS 23.273 [5] are performed with the following differences. + - At step 1, the LCS Client or AF includes a request for user plane reporting in the Location Request and includes an IP address or FQDN for the user plane connection and security information to enable a secure connection. + - At steps 4, 5, 14 and 16, the request for user plane reporting and an IP address or FQDN and security information for the H-GMLC are forwarded in sequence to the VGMLC (if used), AMF, LMF and target UE. The H-GMLC also retains the IP address or FQDN and security information for the LCS Client or AF that was received at step 1. The type of user plane connection (via the H-GMLC) is also conveyed to the LMF and target UE from the H-GMLC. The H-GMLC can decide to use this procedure (rather than either of the other procedures) prior to step 4 or step 5 of the procedure in clause 6.3.1 of TS 23.273 [5]. + - At step 17-21, the target UE indicates to the LMF, H-GMLC and LCS Client or AF whether event reporting via user plane can be supported by the target UE. If event reporting via user plane cannot be supported, the target UE uses the procedure in clause 6.3.1 of TS 23.273 [5] to send events reports via Control Plane. +- The UE establishes a secure TCP/IP connection to the H-GMLC using the IP address or FQDN and security information received by the UE at step 1. +- The H-GMLC establishes a secure TCP/IP connection to the LCS Client or AF H-GMLC using the IP address or FQDN and security information received by the H-GMLC at step 1. +- If the UE needs assistance data to help determine a location later at step 6, the UE performs step 3 in clause 6.19.3.1 to obtain assistance data from the LMF using control plane. +- The UE monitors for and detects the occurrence of a trigger or periodic event as described for step 22 of the procedure in clause 6.3.1 of TS 23.273 [5]. +- The UE obtains location measurements and determines a current location, possibly using assistance data obtained at step 3. + +NOTE 1: Obtaining a location at step 6 limits the UE to using UE based or standalone position methods. If UE assisted position methods need to be used, the LMF can use the procedure described in clause 6.19.3.3 instead of the procedure in this clause. + +7. The UE sends a supplementary services Event Report to the H-GMLC over the secure TCP/IP Connection established at step 2. The event report indicates the type of event being reported and includes the location determined at step 6. +8. The H-GMLC forwards the supplementary services Event Report to LCS Client or AF over the secure TCP/IP Connection established at step 3. +9. The LCS Client or AF returns a supplementary services Event Report Acknowledgment to the H-GMLC over the secure TCP/IP Connection established at step 3. +10. The H-GMLC returns the supplementary services Event Report Acknowledgment to the UE over the secure TCP/IP Connection established at step 2. +11. The UE continues to monitor for and detect further trigger or periodic events as at step 5 and repeats steps 6-10 for each detected trigger or periodic event. + +NOTE 2: A cumulative event report from the UE, as at step 9 in the procedure in clause 6.19.3.1, should not be needed when event reports are sent via the H-GMLC, as the H-GMLC is already aware of the status of event reporting and would know if the UE had ceased reporting events. + +### 6.19.3.3 Event Reporting from a UE to an LCS Client or AF via an LMF + +Figure 6.19.3.3-1 shows a procedure for event reporting from a UE to an LCS Client or AF when a User Plane connection is established to the LCS Client or AF via the LMF. This procedure is applicable when UE assisted position methods are used by the UE. + +NOTE: This procedure does not support transfer of event reporting to a new LMF. While such support could be added, it could substantially increase latency as well as add more impacts for the target UE, LMF and LCS Client or AF. Environments where very low latency is needed can include factories, warehouses and industrial plants where a single LMF might support the entire UE coverage area, thereby making LMF change unnecessary. In other environments, where an LMF change could be needed, the procedure in clauses 6.19.3.1 or 6.19.3.2 could be used instead. + +![Sequence diagram showing Event Reporting from a UE to an LCS Client or AF via the LMF. The diagram illustrates the interaction between UE, NG-RAN, AMF, UPF, LMF, H-GMLC, LCS Client, NEF, and AF. The process involves deferred 5GC-MT-LR procedure, secure TCP/IP connections, assistance data requests, event detection, location measurements, event reports, and location determination.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UPF + participant LMF + participant H-GMLC + participant LCS Client + participant NEF + participant AF + + Note over UE, AF: 1. Deferred 5GC-MT-LR Procedure for Periodic or Triggered Location Events in TS 23.273 Clause 6.3.1 Steps 1-21 + Note over UE, LMF: 2. Establish secure TCP/IP Connection from UE to LMF + Note over LMF, LCS Client: 3. Establish secure TCP/IP Connection from LMF to LCS Client or AF + Note over UE, LMF: 4. Request Assistance Data from LMF via Control Plane + Note over UE: 5. Event Detected + Note over UE: 6. Location Measurements + UE->>LMF: 7. Event Report (LPP Messages(s)) + LMF-->>UE: 8. Event Report Acknowledgment + Note over UE, LMF: 9. LPP Positioning Messages + Note over LMF: 10. Location Determination + LMF->>AF: 11. Event Report (location estimate) + AF-->>LMF: 12. Event Report Acknowledgment + Note over UE: 13. Event Detected + Note over LMF, AF: 14. Transfer Cumulative Event Report to LCS Client or AF via Control Plane as in steps 28-30 of TS 23.273 Clause 6.3.1 + +``` + +Sequence diagram showing Event Reporting from a UE to an LCS Client or AF via the LMF. The diagram illustrates the interaction between UE, NG-RAN, AMF, UPF, LMF, H-GMLC, LCS Client, NEF, and AF. The process involves deferred 5GC-MT-LR procedure, secure TCP/IP connections, assistance data requests, event detection, location measurements, event reports, and location determination. + +**Figure 6.19.3.3-1: Event Reporting from a UE to an LCS Client or AF via the LMF** + +- Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 of TS 23.273 [5] are performed with the following differences: + - At step 1, the LCS Client or AF includes a request for user plane reporting in the Location Request and includes an IP address or FQDN for the user plane connection and security information to enable a secure connection. + - At steps 4, 5 and 14, the request for user plane reporting and the IP address or FQDN and the security information are forwarded in sequence to the V-GMLC (if used), AMF and LMF. The criteria for sending cumulative event reports at step 14 are also conveyed to the LMF. The criteria can include a periodic time interval or the sending of a certain number of event reports via user plane at steps 7 and 11. + - At step 16, the request for user plane reporting and an IP address or FQDN and security information for the LMF are sent to target UE. The LMF also retains the IP address or FQDN and security information for the LCS Client or AF that was received at step 14. The type of user plane connection (via the LMF) is also conveyed to the target UE at step 16. The LMF can decide to use this procedure (rather than either of the other procedures) prior to step 16 of the procedure in clause 6.3.1 of TS 23.273 [5] and only if the H-GMLC had decided not to use event reporting via the H-GMLC. + - At step 17-21, the target UE indicates to the LMF, H-GMLC and LCS Client or AF whether event reporting via user plane can be supported by the target UE. If event reporting via user plane cannot be supported, the target UE uses the procedure in clause 6.3.1 of TS 23.273 [5] to send events reports via Control Plane. +- The UE establishes a secure TCP/IP connection to the LMF using the IP address or FQDN and security information received by the UE at step 1. +- The LMF establishes a secure TCP/IP connection to the LCS Client or AF using the IP address or FQDN and security information received by the LMF at step 1. + +4. If the UE needs assistance data to help obtain location measurements later at step 6, the UE performs step 3 in clause 6.19.3.1 to obtain assistance data from the LMF using control plane. +5. The UE monitors for and detects the occurrence of a trigger or periodic event as described for step 22 of the procedure in clause 6.3.1 of TS 23.273 [5]. +6. The UE obtains location measurements and possibly determines a location, and possibly using assistance data obtained at step 4. +7. The UE sends a supplementary services Event Report to the LMF over the secure TCP/IP Connection established at step 2. The event report indicates the type of event being reported and includes an embedded LPP message with the location measurements or location estimate obtained at step 6. +8. The LMF returns a supplementary services Event Report Acknowledgment to the UE over the secure TCP/IP Connection established at step 2. +9. If the LMF needs additional location measurements or a location estimate from the UE, the LMF exchanges LPP messages with the UE over the secure TCP/IP Connection established at step 2 to request and receive the additional location measurements or location estimate from the UE. +10. Based on the location measurements or location estimate received from the UE at step 7 and/or step 9, the LMF determines or verifies a location estimate for the UE. +11. The LMF sends a supplementary services Event Report to the LCS Client or AF over the secure TCP/IP Connection established at step 3 and includes the type of event report and the location estimate determined or verified at step 10. +12. The LCS Client or AF returns a supplementary services Event Report Acknowledgment to the LMF over the secure TCP/IP Connection established at step 3. +13. The UE continues to monitor for and detect further trigger or periodic events as at step 5 and repeats steps 6-12 for each detected trigger or periodic event. +14. Based on the criteria received by the LMF for sending of cumulative event reports (e.g. the expiration of a periodic timer or the sending of certain number of event reports), the LMF sends a cumulative event report to the H-GMLC and LCS Client or AF over the control plane portion of the periodic or triggered deferred 5GC-MT-LR using steps 28-30 of the procedure in clause 6.3.1 of TS 23.273 [5]. The cumulative event report indicates to the H-GMLC and External LCS Client or AF that the control plane portion of the periodic or triggered deferred 5GC-MT-LR is still operational, that the UE is still reporting events (e.g. is still powered on and in network coverage) and may include statistics on the events reported since the last cumulative event report was sent (e.g. the number of event reports). + +#### 6.19.3.4 Cancellation of Event Reporting + +Cancellation of event reporting can be initiated by the UE, H-GMLC or LCS Client or AF using the control plane procedures defined in clauses 6.3.2 and 6.3.3 in TS 23.273 [5]. The only change to these procedures is that the user plane connection(s) established for the procedures in clauses 6.19.3.1, 6.19.3.2 and 6.19.3.3 are also released. The user plane connection(s) may be released by either end once cancellation at the control plane level has occurred. + +#### 6.19.4 Impacts on services, entities, and interfaces + +UE: + +- Support control plane signalling transfer of information related to user plane transfer (e.g. IP address, FQDN, security information). +- Support user plane connection establishment and release to an LMF, H-GMLC or LCS Client or AF. +- Support sending event reports via the user plane connection. +- Support cumulative event reporting to an LMF via control plane. + +LMF: + +- support control plane signalling transfer of information related to user plane transfer (e.g. IP address, FQDN, security information). +- Support user plane connection establishment and release to a UE and an LCS Client or AF (this is optional). +- Support receiving and sending event reports via the user plane connections (this is optional). +- Support receiving and sending cumulative event reports via control plane. + +#### H-GMLC: + +- support control plane signalling transfer of information related to user plane transfer (e.g. IP address, FQDN, security information). +- Support user plane connection establishment and release to a UE and an LCS Client or AF (this is optional). +- Support receiving and sending event reports via the user plane connections (this is optional). +- Support receiving and sending cumulative event reports via control plane. + +#### LCS Client or AF: + +- support control plane signalling transfer of information related to user plane transfer (e.g. IP address, FQDN, security information). +- Support user plane connection establishment and release to a UE, H-GMLC or LMF. +- Support receiving event reports via the user plane connection. +- Support receiving cumulative event reports via control plane. + +## 6.20 Solutions 20: NWDAF based Indoor or Outdoor in Location Services + +### 6.20.1 Introduction + +The FS\_eLCS\_Ph3 of this TR includes the following agreed aspect to study as part of key Issue #4: Interaction between Location Service and NWDAF: + +- Identify use cases where new or existing data analytics from the NWDAF can be used for improving location service performance. Regulatory requirements (e.g. different location accuracy requirements from FCC in different cases) will be taken into account. + +NOTE: Coordinated activities between the study FS\_eNA\_Ph3 and this study are needed. + +### 6.20.2 Solution Description + +As part of the Regulatory requirements, for example FCC "Wireless E911 Location Accuracy Requirements" which requires $\pm 3$ meters accuracy for indoor cases. However, currently, LMF output does not contain indoor/outdoor level indication. For example, police or lawful agency wants to know if user/victim is inside the building or outside the building, according, they approach the user. Additionally, knowledge of such UE status helps LMF to use most optimal positioning method and optimization to calculate UE's indoor and/or outdoor position. (e.g. different location accuracy requirements from FCC in different cases), it is required to determine if a particular user is located indoor or outdoor. Such information of user can then be used by rescue team to take appropriate action. This clause provides high level solution, and detail procedures are for further studies. + +This solution allows an regulatory AF/LCS client to request UE's indoor or outdoor location in the "LCS Service Request". + +Such request triggers LMF to request/subscribe to analytics data from NWDAF. This is to request analytics information from NWDAF to assist LMF in determining whether UE is indoor or not. + +Since indoor/outdoor information is regulatory requirements about accuracy and could assist in better accuracy of final result, to support this, NWDAF can use the same interface of regulatory AF/LCS Client to fetch both accurate result and indoor/outdoor information. NWDAF can also implement new analytics determination logic in order to determine indoor-outdoor prediction of the UE. This fits the KI#9 in eNA study. + +As proposed by other solutions of KI#4, using GMLC/NEF interface, NWDAF can get the better accurate information for machine learning of both accurate position and indoor/outdoor indication. + +"LMF can optionally decide the indoor/outdoor information by following methods: + +1. UE can detect the indoor-only signal including serving cell ID (NCGI) which serves only indoor cases, or indoor WLAN and/or Bluetooth positioning information defined in TS 37.355 [15]. +2. LMF can generate the altitude information and identify the UE is below the height of the roof (in SRTM DB, etc). +3. Other implementation specific methods. + +LMF provides all the measurements from RAN node/UE and optional indoor/outdoor indication to NWDAF: + +- When indoor/outdoor indication is provided to NWDAF, NWDAF can perform the learning process to correlate the positioning measurements with indoor/outdoor result. +- When indoor/outdoor indication is absent, LMF can use the measurements to query NWDAF for the indoor/outdoor decision result. + +NWDAF generates analytics data and with certain confidence level, provides as output to LMF indicating whether UE is indoor or outdoor. + +LMF based on its own decision or the received analytics result includes whether UE is indoor or outdoor, LMF can reply the information to AF/LCS Client to meet the regulatory requirements through AMF/GMLC/NEF; LMF can also determines most suitable positioning method e.g. optimized to indoor positioning or outdoor positioning. + +### 6.20.3 Procedures + +![Sequence diagram illustrating the procedures for in/out-door analytics provided by NWDAF. The diagram shows interactions between UE, NG-RAN, NWDAF, AMF, LMF, GMLC/LRF, and NWDAF/LI/Eme. The process starts with an NH-LR or MT-LR procedure (1). The LMF sends a request to the AMF (2). The AMF initiates UE positioning with the target UE (3). The LMF makes an in/out-door decision (3.1). The LMF feeds measurements and the decision to the NWDAF (3.2.a) or queries the NWDAF for measurements (3.2.b). The LMF then performs further UE positioning based on the in/out-door indication (3.3). The LMF sends a request to the AMF (4). The AMF sends an event notification to the GMLC/LRF (5). The GMLC/LRF sends an in/out-door indication with the legacy location result to the NWDAF/LI/Eme (6).](91aa06b0972f24b4889588fa0e3a331a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant NWDAF + participant AMF + participant LMF + participant GMLC/LRF + participant NWDAF_LI_Eme as NWDAF/LI/Eme + + Note over UE, NWDAF: 1. NH-LR or MT-LR procedure + LMF->>AMF: 2. Nlmf_Location_DetermineLocation requires in/out-door + Note over UE, LMF: 3 UE Positioning with target UE + Note over LMF, NWDAF: 3.1 in/out-door decision + LMF->>NWDAF: 3.2.a Feed measurements and in/out-door decision to NWDAF + LMF->>NWDAF: 3.2.b Use measurements to query in/out-door from NWDAF + Note over UE, LMF: 3.3 Further UE Positioning with target UE based on in/out-door + LMF->>AMF: 4. Nlmf_Location_DetermineLocation with in/out-door indication + AMF->>GMLC/LRF: 5. Namf_Location_EventNotify + GMLC/LRF->>NWDAF_LI_Eme: 6. in/out-door indication with legacy location result + +``` + +Sequence diagram illustrating the procedures for in/out-door analytics provided by NWDAF. The diagram shows interactions between UE, NG-RAN, NWDAF, AMF, LMF, GMLC/LRF, and NWDAF/LI/Eme. The process starts with an NH-LR or MT-LR procedure (1). The LMF sends a request to the AMF (2). The AMF initiates UE positioning with the target UE (3). The LMF makes an in/out-door decision (3.1). The LMF feeds measurements and the decision to the NWDAF (3.2.a) or queries the NWDAF for measurements (3.2.b). The LMF then performs further UE positioning based on the in/out-door indication (3.3). The LMF sends a request to the AMF (4). The AMF sends an event notification to the GMLC/LRF (5). The GMLC/LRF sends an in/out-door indication with the legacy location result to the NWDAF/LI/Eme (6). + +**Figure 6.20.3-1: In/out-door analytics provided by NWDAF** + +- Step 1: Regulatory (LI or Emergency) NI-LR or MT-LR procedure as defined in TS 23.273 [5]. NWDAF can also use GMLC to fetch finer granularity information with indoor/outdoor indication in response. +- Step 2: LMF receives the request which requires indoor and outdoor indication. + +- Step 3: LMF performs positioning procedures (using LPP with UE or NRPPa with RAN nodes). +- Step 3.1: LMF may decide indoor and outdoor decision by its own positioning procedures/measurements. This could also be carried out in non-regulatory procedures to enrich the NWDAF dataset. +- Step 3.2.a: When LMF decides the indoor/outdoor indication, it can feed the measurements and result to NWDAF for learning process. +- Step 3.2.b: When LMF can't decide the indoor/outdoor indication, it can use its measurements to query NWDAF. +- Step 3.3: No matter indoor/outdoor decision is made by LMF or NWDAF, LMF can use the information to optimize its positioning methods or procedures. +- Step 4~5: indoor and outdoor information can be forwarded back to various client to meet the regulatory requirements. +- Step 6: The indoor/outdoor information can be included in the response if needed. NWDAF can get the indoor/outdoor indication when better accurate information than TA/CI is needed. + +## 6.20.4 Impacts on services, entities, and interfaces + +LCS Client: support indication of indoor/outdoor in the LCS Service Request. + +LMF: support determination of UE's indoor or outdoor location. + +NWDAF: support new analytics of indoor and outdoor decision. + +## 6.21 Solution #21: Collection of nearby GNSS assistance data + +### 6.21.1 Introduction + +This solution addresses KI#5 about how LMF to obtain nearby GNSS assistance data. + +### 6.21.2 Functional Description + +Normally, a serving area of a GNSS reference station can cover one TA or multiple TAs (i.e. its GNSS assistance data applies to one TA or multiple TAs). When LMF collects GNSS assistance data, it requests corresponding data which can serve its serving area. The collection may be performed on a periodic basis. + +With different GNSS reference deployment scenarios, how LMF obtain GNSS assistance data can be different. In this solution, following cases are considered: + +- GNSS reference stations are third party functions co-located with gNBs and LMF collects data from AFs. + +LMF gets GNSS assistance data through AF event exposure service as described in clause 5.2.19.2 of TS 23.502 [3], LMF may also get the precise global coordinates of GNSS reference stations. In this case, LMF is enhanced to support utilize the Naf\_EventExposure service. LMFs collected GNSS assistance data may update its NF profile in NRF by indicating the TAs of which corresponding GNSS assistance data exists, which can be discovered and used by other LMFs not having corresponding GNSS assistance data. + +- For a trusted AF, AF registers at the NRF with its serving area (e.g. TAs or geographical location). LMF discovers trusted AFs which can cover its serving area through NRF and subscribes to GNSS assistance data exposure from discovered trusted AFs. +- For a third-party AF, AF registers at the NEF with its serving area (e.g. geographical location) and NEF registers itself with the serving area information (mapped into TAs) to NRF. LMF discovers corresponding NEFs which can cover its serving area through NRF then subscribes GNSS assistance data through the discovered NEFs. + +## 6.21.3 Procedures + +### 6.21.3.1a GNSS assistance data collection from untrusted AF + +The procedure in Figure 6.21.3.1a-1 is used by LMF to collect GNSS assistance information from AFs via the NEF, which is similar with NWDAF collecting data from untrusted AF described in clause 6.2.2.3 of TS 23.288 [9]. + +![Sequence diagram for GNSS assistance data collection from untrusted AF. Lifelines: NRF, LMF, NEF, AF. The process involves registration, discovery, and subscription/notification steps.](4540c7355b250cb891be0b54b0ba25c7_img.jpg) + +``` + +sequenceDiagram + participant NRF + participant LMF + participant NEF + participant AF + + Note right of AF: Registration of AF available GNSS Assistance data + AF->>NEF: 1a. Nnrf_NFManagement_NFUpdate_request + Note left of NEF: 1b. Store NF profile + NEF->>NRF: 1c. Nnrf_NFManagement_NFUpdate_response + + Note right of AF: Discovery of AF available GNSS Assistance data + LMF->>NRF: 1d. Nnrf_NFDiscovery_Request_request + NRF->>LMF: 1e. Nnrf_NFDiscovery_Request_response + + LMF->>NEF: 2. Nnef_EventExposure_Subscribe/ +Nnef_EventExposure_Unsubscribe + NEF->>AF: 3. Naf_EventExposure_Subscribe/ +Naf_EventExposure_Unsubscribe + AF-->>NEF: 4. Naf_EventExposure_Notify + NEF-->>LMF: 5. Nnef_EventExposure_Notify + +``` + +Sequence diagram for GNSS assistance data collection from untrusted AF. Lifelines: NRF, LMF, NEF, AF. The process involves registration, discovery, and subscription/notification steps. + +Figure 6.21.3.1a-1: GNSS assistance data collection + +1a-1c. Similar with steps 1a-1c in figure 6.2.2.3-1 of TS 23.288 [9]. The difference is that AF should also provide its serving area to NEF. NEF should map the serving area into TA(s) if it is presented as geographical location and update the NEF profile in NRF including the serving area information. + +1d-1e. Similar with steps 1d-1e in figure 6.2.2.3-1 of TS 23.288 [9]. The difference is that LMF may additionally provide TAs to discover specific NEFs. + +2-5. Similar with steps 2-5 in figure 6.2.2.3-1 of TS 23.288 [9]. The difference is that besides available GNSS assistance data, AF further provide associated serving area of the GNSS assistance data and optional precise global coordinates of the source of the GNSS assistance data. NEF may map the serving area into a TA or TA list. + +### 6.21.3.1b GNSS assistance data collection from trusted AF + +For trusted AFs, LMF should collect GNSS assistance data through AFs directly. LMF discovers trusted AFs covering LMF serving area through NRF and subscribes to GNSS assistance data exposure from discovered trusted AFs. + +![Sequence diagram showing GNSS measurements transfer between NRF, LMF, and AF. The diagram is divided into two dashed boxes. The first box contains steps 1a, 1b, and 1c: AF sends Nnrf_NFManagement_NFUpdate_request to NRF; NRF stores the NF profile; NRF sends Nnrf_NFManagement_NFUpdate_response to AF. The second box contains steps 1d, 1e, 2, and 3: LMF sends Nnrf_NFDiscovery_Request_request to NRF; NRF sends Nnrf_NFDiscovery_Request_response to LMF; LMF sends Naf_EventExposure_Subscribe/Naf_EventExposure_Unsubscribe to AF; AF sends Naf_EventExposure_Notify to LMF.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant AF + participant LMF + participant NRF + + Note left of NRF: 1a. Nnrf_NFManagement_NFUpdate_request + AF->>NRF: 1a. Nnrf_NFManagement_NFUpdate_request + Note right of NRF: 1b. Store NF profile + NRF-->>AF: 1c. Nnrf_NFManagement_NFUpdate_response + + Note left of LMF: 1d. Nnrf_NFDiscovery_Request_request + LMF->>NRF: 1d. Nnrf_NFDiscovery_Request_request + NRF-->>LMF: 1e. Nnrf_NFDiscovery_Request_response + + Note left of LMF: 2. Naf_EventExposure_Subscribe/Naf_EventExposure_Unsubscribe + LMF->>AF: 2. Naf_EventExposure_Subscribe/Naf_EventExposure_Unsubscribe + Note left of AF: 3. Naf_EventExposure_Notify + AF-->>LMF: 3. Naf_EventExposure_Notify + +``` + +Sequence diagram showing GNSS measurements transfer between NRF, LMF, and AF. The diagram is divided into two dashed boxes. The first box contains steps 1a, 1b, and 1c: AF sends Nnrf\_NFManagement\_NFUpdate\_request to NRF; NRF stores the NF profile; NRF sends Nnrf\_NFManagement\_NFUpdate\_response to AF. The second box contains steps 1d, 1e, 2, and 3: LMF sends Nnrf\_NFDiscovery\_Request\_request to NRF; NRF sends Nnrf\_NFDiscovery\_Request\_response to LMF; LMF sends Naf\_EventExposure\_Subscribe/Naf\_EventExposure\_Unsubscribe to AF; AF sends Naf\_EventExposure\_Notify to LMF. + +**Figure 6.21.3.1b-1: GNSS measurements transfer 1a-1c. AF registers at the NRF with its serving area (e.g. TAs)** + +1d-1e. LMF provide TAs to discover AFs. + +2-3. LMF subscribes AF for GNSS assistance collection. Besides available GNSS assistance data, AF further provides associated serving area of the GNSS assistance data and optional precise global coordinates of the source of the GNSS assistance data. + +## 6.21.4 Impacts on services, entities, and interfaces + +LMF: + +- Support to collect and store GNSS assistance data from AF, RAN or UE. +- When receive GNSS assistance data, send message to NRF to indicate GNSS assistance data existence in certain area. + +AF: + +- Support exposure of GNSS assistance data associated with geographical location. + +NEF: + +- Support exposure of GNSS assistance data associated with geographical location from AF. + +## 6.22 Solution #22: Support of LCS mobility when UE moves between NG-RAN nodes + +### 6.22.1 Introduction + +This solution addresses the KI "Key Issue #8: support of location service continuity in case of UE mobility". + +Continuity of certain basic services like a PDU session during mobility is defined currently. However, the handling of an LCS session during mobility procedures is not specified currently. In particular, there is no specification on whether an ongoing LCS session shall be terminated or continued with after the mobility and if continued, how the continuity shall work. There can be many effects due to this missing part: + +- LCS sessions may be terminated at mobility with the LCS Client having to re-initiate the session after the procedure. + +- The LMF may not be aware of the mobility at all, leading to inaccurate positioning estimates. +- Since there are no clear specifications, inter-vendor tests could fail. +- LCS sessions could be enabled as part of other critical services (like emergency calls) - those services could be impacted due to the current specifications - leading to regulatory issues. + +All of the above issues could be prevented if there is a clear specification on how LCS sessions are to be handled in different mobility procedures and in particular, if continuity can be guaranteed by the network. + +We describe the additional handling required at LMF change for LCS Continuity in both the scenarios - Xn based HO and NG based HO. + +It is noted that clause 6.4 of TS 23.273 [5] describes LMF change handling already. But this is for the case where the AMF detects the need for LMF change (possibly due to UE mobility) before the LCS session is started. In the scenario that solution 22 addresses, the HO happens after the LCS session is started. So, the existing solution will not address this scenario. + +## 6.22.2 Functional Description + +This proposal provides a solution for the intra-5GS mobility across NG-RAN nodes. + +## 6.22.3 Procedure + +![Sequence diagram titled 'MSC:Xn Based HO Success - LCS Continuity' showing the interaction between UE, SgNB, TgNB, AMF, LMF, and GMLC. The diagram illustrates the steps for maintaining LCS continuity during an Xn-based handover. Key steps include: 1. AMF sends a Namf_Location_providePositioningInfo Request to LMF; 2. AMF sends a Network Triggered Service Request to SgNB; 3. AMF performs LMF Selection; 4. AMF sends an Nlmf_Location DetermineLocation Request to LMF; 5. LCS Session Ongoing; 6. HO decision; 7. HO Req (Old NGAP AMF UE ID) from SgNB to TgNB; 8. HO Ack from TgNB to SgNB; 9. SN Status Transfer from SgNB to TgNB; 10. HO Success from TgNB to SgNB; 11. SN Status Transfer from TgNB to SgNB; HO Execution; 12. Path Switch Request (Old NGAP AMF UE ID) from TgNB to AMF; 13. AMF Compares LCS UE Correlation ID and Old NGAP AMF UE ID; 14. Notification (Mobility Completion) from AMF to LMF; 15. Path Switch Ack from AMF to TgNB; 16. LMF initiates assistance info and measurement request over TgNB. Annotations include: 'AMF knows the UE correlation ID for the LCS Session' at step 3, 'Indicate HO Completion to LMF if the IDs belong to the same UE' at step 12, and 'LCS Session continues after HO' at step 15.](4ee2de50739c96fd7bd5a38150ec9c78_img.jpg) + +**MSC:Xn Based HO Success - LCS Continuity** + +Sequence diagram titled 'MSC:Xn Based HO Success - LCS Continuity' showing the interaction between UE, SgNB, TgNB, AMF, LMF, and GMLC. The diagram illustrates the steps for maintaining LCS continuity during an Xn-based handover. Key steps include: 1. AMF sends a Namf\_Location\_providePositioningInfo Request to LMF; 2. AMF sends a Network Triggered Service Request to SgNB; 3. AMF performs LMF Selection; 4. AMF sends an Nlmf\_Location DetermineLocation Request to LMF; 5. LCS Session Ongoing; 6. HO decision; 7. HO Req (Old NGAP AMF UE ID) from SgNB to TgNB; 8. HO Ack from TgNB to SgNB; 9. SN Status Transfer from SgNB to TgNB; 10. HO Success from TgNB to SgNB; 11. SN Status Transfer from TgNB to SgNB; HO Execution; 12. Path Switch Request (Old NGAP AMF UE ID) from TgNB to AMF; 13. AMF Compares LCS UE Correlation ID and Old NGAP AMF UE ID; 14. Notification (Mobility Completion) from AMF to LMF; 15. Path Switch Ack from AMF to TgNB; 16. LMF initiates assistance info and measurement request over TgNB. Annotations include: 'AMF knows the UE correlation ID for the LCS Session' at step 3, 'Indicate HO Completion to LMF if the IDs belong to the same UE' at step 12, and 'LCS Session continues after HO' at step 15. + +**Figure 6.22.3-1: Xn Based Handover – LCS Continuity** + +Description: + +Steps 1-12 describe the normal LCS session and Xn based HO procedures. + +Some of the key steps are described below. + +Step 4: AMF knows the LCS Correlation ID of the UE for which the LCS session is being initiated - it stores the same. + +Step 12: AMF comes to know of the completion of the Xn based HO. The Target gNB also sends the old NGAP : AMF UE ID assigned by the AMF in the message (Target gNB gets it from Source gNB in step 7). + +Step 13: The AMF checks if this UE ID has an associated LCS session that is active (by checking for the corresponding LCS Correlation ID). + +Step 14: If such an LCS session exists, then the AMF shall invoke a notification towards the LMF indicating the completion of the ongoing mobility procedure. This could be an existing API enhanced or a new API. + +AMF determines that the existing LMF cannot serve the LCS session anymore due to UE mobility (this could be based on an internal configuration); it then selects a new LMF and provides this LMF address in the mobility completion notification to the old LMF. + +The old LMF then invokes the Nlmf\_Location\_LocationContextTransfer procedure to the new LMF and transfers the LCS Session context. + +Step 16: When the LMF receives the notification for mobility completion, it will keep all the active LCS sessions on, but requests for updated information to make the measurements accurate. The LMF may communicate with the Target gNB through the AMF for this purpose. + +The new LMF then initiates the LCS session (using the target NG-RAN). + +This could be the modified list of TRPs, assistance information etc. and then subsequently, a fresh request for measurements based on the updated information. + +As can be observed, the entire procedure is done in a way where GMLC and/or LCS Client is not aware of the mobility handling and the LCS session continuity is ensured. + +![Sequence diagram titled 'MSC:NG Based HO Success - LCS Continuity' showing the interaction between UE, SgNB, TgNB, SAMF, TAMF, LMF, and GMLC. The diagram illustrates the steps for a successful handover while maintaining LCS session continuity. Key steps include: 1. Nlmf_Location_providePositioningInfo Request from LMF to SAMF; 2. Network Triggered Service Request from SAMF to UE; 3. LMF Selection; 4. Nlmf_Location_DetermineLocation Request from SAMF to LMF; 5. LCS Session Ongoing; 6. HO decision; 7. NGAP : HO Required from SgNB to SAMF; 8. TAMF Selection; 9. Nlmf_CreateUEContext_Request from SAMF to TAMF (including Positioning Session Info, old NGAP AMF UE ID); 10. NGAP : HO Request from SAMF to TgNB; 11. NGAP : HO Request Ack from TgNB to SAMF; 12. Nlmf_CreateUEContext_Response from TAMF to SAMF; 13. NGAP : HO Command from SAMF to SgNB; 14. RRC : HO Command from SgNB to UE; 15. RRC : HO Confirm from UE to SgNB; 16. NGAP : HO Notify from SgNB to SAMF (new NGAP AMF UE ID); 17. T_AMF checks if the new NGAP AMF UE ID had an equivalent LCS UE Correlation ID; 18. Notification(HO Completion) from TAMF to LMF; 19. LMF initiates assistance info and measurement request over TgNB. Annotations highlight that the LCS session continues after HO, and that HO completion is indicated to the LMF if the IDs belong to the same UE. A note indicates that the TAMF gets the LCS session info and assigns a new NGAP AMF UE ID.](0726a03ffb4e106eb90cd4f9283a6347_img.jpg) + +**MSC:NG Based HO Success - LCS Continuity** + +Sequence diagram titled 'MSC:NG Based HO Success - LCS Continuity' showing the interaction between UE, SgNB, TgNB, SAMF, TAMF, LMF, and GMLC. The diagram illustrates the steps for a successful handover while maintaining LCS session continuity. Key steps include: 1. Nlmf\_Location\_providePositioningInfo Request from LMF to SAMF; 2. Network Triggered Service Request from SAMF to UE; 3. LMF Selection; 4. Nlmf\_Location\_DetermineLocation Request from SAMF to LMF; 5. LCS Session Ongoing; 6. HO decision; 7. NGAP : HO Required from SgNB to SAMF; 8. TAMF Selection; 9. Nlmf\_CreateUEContext\_Request from SAMF to TAMF (including Positioning Session Info, old NGAP AMF UE ID); 10. NGAP : HO Request from SAMF to TgNB; 11. NGAP : HO Request Ack from TgNB to SAMF; 12. Nlmf\_CreateUEContext\_Response from TAMF to SAMF; 13. NGAP : HO Command from SAMF to SgNB; 14. RRC : HO Command from SgNB to UE; 15. RRC : HO Confirm from UE to SgNB; 16. NGAP : HO Notify from SgNB to SAMF (new NGAP AMF UE ID); 17. T\_AMF checks if the new NGAP AMF UE ID had an equivalent LCS UE Correlation ID; 18. Notification(HO Completion) from TAMF to LMF; 19. LMF initiates assistance info and measurement request over TgNB. Annotations highlight that the LCS session continues after HO, and that HO completion is indicated to the LMF if the IDs belong to the same UE. A note indicates that the TAMF gets the LCS session info and assigns a new NGAP AMF UE ID. + +**Figure 6.22.3-2: NG Based Handover - LCS Continuity** + +Description: + +Steps 1-16 describe the normal LCS session and NG based HO procedures. Some key steps are highlighted below. + +Step 4: Source AMF knows the LCS Correlation ID of the UE for which the LCS session is being initiated - it stores the same. + +Step 9: The Source AMF adds the LCS Session information corresponding to all the active LCS sessions to the Target AMF along with the assigned old NGAP AMF UE ID. + +S-AMF already sends the Target RAN ID to the T-AMF as part Namf\_CreateUEContextRequest. It could add the S-LMF Address in the same. The T-AMF then determines if the same LMF can continue to serve the UE post HO (possibly based on internal configuration). + +Step 10: The Target AMF assigns a new NGAP AMF UE ID for the UE as per HO signalling. + +Step 12: T-AMF may then select a different LMF(T-LMF) and indicates this to the S-AMF in Namf\_CreateUEContextResponse. If a new LMF is indicated, then the S-AMF requests the S-LMF to initiate LMF context transfer using the Nlmf\_Location\_CancelLocation. This triggers the S-LMF to start Nlmf\_Location\_LocationContextTransfer procedure to the T-LMF and transfers the LCS Session context. + +Step 16: The HO completes and Target AMF gets the notification with the new NGAP AMF UE ID. + +Step 17: It then checks if that UE had an existing LCS Session on the Source AMF (using the data it got in step 9). + +Step 18: If such an LCS session exists, then the AMF shall invoke a notification towards the LMF indicating the completion of the ongoing mobility procedure. This could be an existing API enhanced or a new API. + +The LMF may then choose to do the same actions as described for the Xn based HO to keep the LCS session active, but with updated, more accurate parameters and measurements. The LMF may communicate with the Target gNB through the Target AMF for this purpose. This completes the LCS session continuity for NG based HO. + +The T-LMF shall then wait HO completion notification and then re-initiates the LCS session with the T-gNB. + +NOTE 1: The above solutions are applicable to: + +- UL or DL or UL+DL positioning methods. +- MTLR/MOLR/NILR LCS sessions. + +NOTE 2: In both the solutions, the LMF is assumed to remain the same. Handling of LCS session during LMF change is already specified in TS 23.273 [5]. + +## 6.22.4 Impacts on services, entities, and interfaces + +AMF: Check if the UE has an existing LCS Session after HO. If yes, invoke a notification towards the LMF indicating the completion of the ongoing mobility procedure. + +LMF: Receive notification indicating the completion of the ongoing mobility procedure and initiate the LCS session using the target NG-RAN. + +# 6.23 Solution #23: Location Verification for Satellite Access assisted by TN access + +## 6.23.1 Introduction + +This solution addresses Key Issue #9 on support of positioning requirements related to satellite access. + +When a UE using NR satellite access, the UE should first determine a most suitable PLMN based on its own physical location determination. As there may be border cases where the UE cannot determine sufficiently accurate or sufficiently precise in which country it is, in order to meet the regulatory requirements, the network needs to verify whether the PLMN selected by the UE is allowed to operate in the country of the UE location based on the UE location information. But the UE location information may not reliable since it was determined by gNB based on UE-generated location information (e.g. GNSS/A-GNSS ). + +Such verification becomes essential in the country borders, especially in terrestrial border. There is usually terrestrial cellular network coverage in such areas. This solution provides a method to do NTN location verification for UE using satellite access based on the UE location provided by TN access (e.g. NR) and based on the following assumptions: + +- The UE has the capability to support both TN access and NTN access. +- The area of the UE present location has both TN and NTN network coverage. + +## 6.23.2 Functional Description + +The high level functional description of this solution is as follows: + +- During the registration procedure through NR satellite access, the UE indicates the capability of supporting TN access (e.g. NR). +- If the network intends to do NTN location verification for UE using satellite access, it requests UE to initiate registration via TN access. +- The UE initiates Registration through TN access. The TN access (e.g. gNB) provides UE location information to the network through NGAP message. After receiving the UE location, the network responds Registration Reject to the UE. +- The AMF verifies the PLMN selected by the UE is whether allowed to operate in the country of the UE present location based on the UE location receiving from TN access. + +NOTE 1: Solution works in areas covered by both TN access and NTN access and the UE has the capability of supporting both TN access and NTN access. + +NOTE 2: How to support emergency service is out of scope in this solution. + +## 6.23.3 Procedures + +![Sequence diagram illustrating the procedure for location verification for satellite access assisted by TN access. The diagram shows interactions between UE, NTN RAN, TN RAN, AMF1, AMF2, and UDM.](6bbd36c86c0876e31b1bc2c4e63b029d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NTN_RAN as NTN RAN + participant TN_RAN as TN RAN + participant AMF1 + participant AMF2 + participant UDM + + Note left of UE: 8. NTN Location verification based on UE TN location + + UE->>AMF1: 1. Registration Request (supporting TN access) + AMF1->>UDM: 2. Nudm_UECM_Registration + AMF1->>UE: 3. Registration Accept (TN access request for NTN Location verification) + UE->>TN_RAN: 4. Registration Request (UE TN Location) + TN_RAN->>AMF2: 5. Nudm_UECM_Registration (NTN Location verification, UE TN Location) + AMF2->>UE: 6. Registration Reject + AMF2->>UDM: 7. Nudm_SDM_Notification (UE TN Location) + +``` + +Sequence diagram illustrating the procedure for location verification for satellite access assisted by TN access. The diagram shows interactions between UE, NTN RAN, TN RAN, AMF1, AMF2, and UDM. + +Figure 6.23.3-1: Procedure for location verification for satellite access assisted by TN access + +1. For a UE accessing to 5GC using NR satellite access, the UE sends a registration request message to AMF1. As per existing procedure, parameters such as registration type, SUCI or 5G-GUTI, etc, are contained in the message. Besides that, if the UE supports 3GPP TN access (e.g. NR), the capability is also included in the message. +2. The AMF1 registers to the UDM using Nudm\_UECM\_Registration message as described in clause 4.2.2.2.2 of TS 23.502 [3]. +3. The AMF1 determines NTN location verification for NR satellite access is needed, it returns the Registration Accept message to the UE with an indication to request the UE to access via TN access. +4. The UE sends registration request via TN access to AMF2 which includes "NTN location verification" to indicate the registration procedure is used to provide UE location for NTN location verification. The TN RAN (e.g. gNB) sends the UE location information in NGAP to the AMF2. The AMF1 and the AMF2 selected by the UE via NTN and TN access may belong to different PLMNs. +5. The AMF2 registers with the UDM using Nudm\_UECM\_Registration. The UDM stores the UE location information received from TN access. + +If the TN access and NTN access selected by the UE belong to different PLMNs, it can be seen as the PLMN selected by UE via NTN access is home PLMN while the PLMN selected by UE via TN access is Serving PLMN. The AMF2 in the serving PLMN will select UDM in the Home PLMN based on the UDM selection as specified in clause 6.3.8 in TS 23.501 [2] during initial registration. Then the AMF2 provides the UE location information in TN access to the UDM for preserve. + +6. The AMF2 sends registration reject message to UE with a suitable cause value indicating NTN location verification. +7. The UDM sends Nudm\_SDM\_Notification to provide the UE location receiving from TN access to the registered AMF1. +8. Based on the UE location receiving from TN access, the AMF1 can verify whether the UE is allowed to operate in the country/area of the UE present location. + +## 6.23.4 Impacts on services, entities, and interfaces + +### UE: + +- Capability to support both TN access and NTN access, inform this capability to the network. + +### AMF: + +- Based on the UE capability, requests UE to initiate registration through TN access. +- Requests UE location information from UDM. +- Based on the UE location information receiving from TN access, verifies the PLMN selected by UE is whether allowed to operate in the country of the UE location. + +### UDM: + +- Receives and Stores UE location information through registration procedure via TN access. +- Provides the UE location information to the AMF. + +## 6.24 Solution #24: UE Location Verification based on Obtained Information + +### 6.24.1 Introduction + +This solution addresses KI#9: Support of Positioning Requirements Related to Satellite Access. + +## 6.24.2 Functional Description + +In Rel-17, as described in clause 5.4.11.4 in TS 23.501 [2], if the AMF is not able to determine the UE's location with sufficient accuracy based on the ULI, 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 [5], 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 current UE location. + +In this solution, it is proposed to optimize the mechanism for UE location verification, as follows: + +- If NG-RAN can verify UE location, the NG-RAN provides assistance information including the verification result to AMF. +- When the assistance information indicates that UE location is reliable, the AMF skips the UE location verification mechanism in Rel-17. +- When the assistance information indicates that UE location is not reliable, the following scenario may happen: + - If the country of the UE reported location is the same as the country of the network verified UE location, the AMF triggers LCS procedure to obtain UE location and notify the UE location to NFs which have subscribed the related event. + - If the country of the UE reported location is different from the country of the network verified UE location, the AMF initiates deregistration procedure with a suitable cause value. + +NOTE: Whether and what assistance information can be provided by NG-RAN depends on the conclusion of the network verified UE location objective in Rel-18 NR\_NTN\_enh WID in RAN WG. + +- Otherwise, the existing UE location verification mechanism in Rel-17 is re-used. + +## 6.24.3 Procedures + +### 6.24.3.1 UE Provided Location Verification based on Obtained Information + +![Sequence diagram for UE Provided Location Verification based on Obtained Information. The diagram shows interactions between UE, NG-RAN, AMF, LMF, and NF. Step 1: UE sends UE location information to NG-RAN. Step 2: NG-RAN verifies UE location (conditional). Step 3: NG-RAN sends N2 message (assistance information) to AMF. Step 4: AMF triggers 5GC-NI-LR procedure (clause 6.10.1 in TS 23.273). Step 5: AMF sends Namf_EventExposure_Notify(UE location) to NF. Step 6: AMF sends Deregistration Request to UE.](cdd0f1dd36631f2c4b17d7ca0f174d80_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant NF + Note right of NG-RAN: 2. verify UE location + Note right of AMF: 4. 5GC-NI-LR procedure in clause 6.10.1 in TS 23.273 + UE->>NG-RAN: 1. UE location information + NG-RAN-->>AMF: 3. N2 message (assistance information) + AMF->>LMF: 4. 5GC-NI-LR procedure in clause 6.10.1 in TS 23.273 + AMF-->>NF: 5. Namf_EventExposure_Notify(UE location) + AMF-->>UE: 6. Deregistration Request + +``` + +Sequence diagram for UE Provided Location Verification based on Obtained Information. The diagram shows interactions between UE, NG-RAN, AMF, LMF, and NF. Step 1: UE sends UE location information to NG-RAN. Step 2: NG-RAN verifies UE location (conditional). Step 3: NG-RAN sends N2 message (assistance information) to AMF. Step 4: AMF triggers 5GC-NI-LR procedure (clause 6.10.1 in TS 23.273). Step 5: AMF sends Namf\_EventExposure\_Notify(UE location) to NF. Step 6: AMF sends Deregistration Request to UE. + +**Figure 6.24.3.1-1: UE Provided Location Verification based on Obtained Information** + +1. The UE sends UE location information (i.e. GNSS info) to NG-RAN over NR-Uu via satellite access. +2. [Conditional] If the NG-RAN can verify UE location, it verifies the reported UE location. + +NOTE: Whether NG-RAN can verify UE location and how to verify the UE location depends on the conclusion of the network verified UE location objective in Rel-18 NR\_NTN\_enh WID in RAN WG. + +3. [Conditional] If the step 2 is performed, the NG-RAN sends N2 message including the assistance information. + +4. [Conditional] If assistance information provided by NG-RAN indicates that UE location is not-reliable, and the country of the UE reported location is the same as the country of the network verified UE location, and there is NF(s) has subscribed UE location event report, the AMF triggers the 5GC-NI-LR procedure in clause 6.10.1 of TS 23.273 [5] to obtain UE location. +5. [Conditional] If the step 4 is performed , the AMF notifies the UE location to the NF(s).. +6. [Conditional] If assistance information provided by NG-RAN indicates that UE location is not-reliable and the country of the UE reported location is different from the country of the network verified UE location, the AMF deregisters the UE. + +## 6.24.4 Impacts on services, entities, and interfaces + +AMF: receive assistance information from NG-RAN and behaves accordingly. + +NG-RAN: verifies the UE location reported by the UE and provides assistance information to AMF. + +NOTE: Whether and what assistance information can be provided by NG-RAN depends on the conclusion of the network verified UE location objective in Rel-18 NR\_NTN\_enh WID in RAN WG. + +## 6.25 Solution #25: Event Report in an Allowed Area + +### 6.25.1 Introduction + +This solution addresses KI#11: Enhance the Triggered Location for UE power saving purpose. + +### 6.25.2 Functional Description + +To support tracking UE location in a pre-defined area, an event report allowed area is introduced in this solution. Only when a UE is in the area, it is allowed to send the event report. + +The event report allowed area can be provided by UE or LCS Client/AF: + +- The UE provided area is stored in UDM; and/or +- The LCS Client/AF can provide the event report allowed area in the LCS Service Request. + +If GMLC receives both areas above, the overlap of the areas is the event report allowed area. If there is no overlap, the GMLC rejects the LCS Service Request. The GMLC is responsible to determine a TA/cell list based on the event report allowed area. + +NOTE: To support power saving, the UE can set the event report allowed area to a small geographical area. + +The event report allowed area determined by GMLC is sent to UE via the LCS Periodic-Triggered Invoke Request message. When the UE detects the trigger or periodic event happens, if the UE is in the event report allowed area, then it obtains location measurements, calculates the location estimate and sends the event report. Otherwise, the UE behaviours above are not performed to save power. If the time period to the last time that the UE sent the event report or to the time that the UE receives the LCS Periodic-Triggered Invoke Request message reaches a certain threshold (e.g. the maximum reporting time for area or motion event type, implementation dependent threshold for UE available or periodic event type), the UE initiates the cancellation procedure. + +## 6.25.3 Procedures + +### 6.25.3.1 Event Report Allowed Area provided by UE + +![Sequence diagram for Figure 6.25.3.1-1: UE Provided Location Verification based on Obtained Information. The diagram shows four participants: UE, NG-RAN, AMF, and UDM. The sequence of messages is: 1. NAS: UE Location Privacy Setting Request (event report allowed area) from UE to AMF; 2. Nudm_ParameterProvision_Update from AMF to UDM; 3. NAS: UE Location Privacy Setting Response from AMF to UE.](ff87509cc2b267501d910a2d9f9054ac_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UDM + Note left of UE: + UE->>AMF: 1. NAS: UE Location Privacy Setting Request (event report allowed area) + AMF->>UDM: 2. Nudm_ParameterProvision_Update + AMF->>UE: 3. NAS: UE Location Privacy Setting Response + +``` + +Sequence diagram for Figure 6.25.3.1-1: UE Provided Location Verification based on Obtained Information. The diagram shows four participants: UE, NG-RAN, AMF, and UDM. The sequence of messages is: 1. NAS: UE Location Privacy Setting Request (event report allowed area) from UE to AMF; 2. Nudm\_ParameterProvision\_Update from AMF to UDM; 3. NAS: UE Location Privacy Setting Response from AMF to UE. + +**Figure 6.25.3.1-1: UE Provided Location Verification based on Obtained Information** + +1. If the UE has generated or updated the event report allowed area, the UE sends the event report allowed area to the AMF via UE Location Privacy Setting Request. +2. The AMF invokes a Nudm\_ParameterProvision\_Update service operation towards the UDM and the service operation carries the event report allowed area. The UDM stores or updates the event report allowed area in the UDR by invoking a Nudr\_DM\_Update (SUPI, Subscription Data) service operation accordingly. +3. The AMF responses to the UE via UE Location Privacy Setting Response. + +### 6.25.3.2 Event Report in an Allowed Area + +To support the event report allowed area, the enhancements to the existing Initiation and Reporting of Location Events in clause 6.3.1 of TS 23.273 [5] are as follows: + +- Step 1a: LCS Client includes the event report allowed area in the LCS Service Request. +- Step 1b: the event report allowed area is included in the Nnef\_EventExposure\_Subscribe Request and Ngmlc\_Location\_ProvideLocation Request. +- Step 2: the event report allowed area is included in Nudm\_SDM\_Get Response. + +If the event report allowed areas received in step 1 and step 2 are not overlapped, the GMLC rejects the location request, the left steps are skipped. Otherwise the event report allowed area is the overlapped area and enhancements to the left steps are as follows: + +- Steps 4, 5, 14 and 16 are enhanced to include the event report allowed area parameter. In step 4, the GMLC is responsible to determine the cell/TA list based on the overlapped area and include the cell/TA list in the event report allowed area. +- Step 22: When UE detects the event happens, it further checks whether it is in the event report allowed area. If yes, the steps 23 to 30b-2 are performed. Otherwise, the steps 23 to 30b-2 are skipped. + +### 6.25.3.3 Add a new trigger for Cancellation of Reporting of Location Events by a UE + +A new trigger is added for UE to cancel Reporting of Location Events procedure in clause 6.3.2 in TS 23.273 [5]: + +- If the time period to the last time that the UE sent the event report or to the time that the UE receives the LCS Periodic-Triggered Invoke Request message reaches a certain threshold (e.g. the maximum reporting time for area or motion event type, implementation dependent threshold for UE available or periodic event type), the UE initiates the cancellation procedure. + +## 6.25.4 Impacts on services, entities, and interfaces + +GMLC: + +- Receive the event report allowed area from LCS Client/AF and/or UDM and decide the final event report allowed area based on the received area(s). +- Send the event report allowed area to AMF. + +UDM: + +- Receive the event report allowed area from UE and store the parameter. +- Provide the event report allowed area to GMLC. + +AMF: Receives the event report allowed area from GMLC and send the parameter to LMF. + +LMF: send the event report allowed area to UE. + +UE: Receive the event report allowed area from LMF and enforce the parameter. + +## 6.26 Solution #26: LPHAP requirement awareness by LMF + +### 6.26.1 Introduction + +The solution addresses key issue #12, support of low power and/or high accuracy positioning. In particular, the issue "whether new information is needed in subscription data for low power and/or high accuracy positioning" is clarified its necessity. + +When RAN discussed low power and high accuracy positioning (LPHAP) in the workshop (RWS-210573), people believe the UE requiring low power and high accuracy positioning can be a new UE type, or based on Redcap UE or eMBB UE. It means low power and high accuracy positioning is not a "label" to differentiate UE, but actually a location service requirement for both UE impact and service performance. + +With the introduction of LPHAP, location procedure in rel-18 needs to be enhanced to satisfy the requirement. In terms of "HA(high accuracy)", currently it is identified by LCS QoS, and optionally provided by the LCS client/AF. If the LCS QoS is not provided, the LMF will treat the location request with a default accuracy. + +On the other hand, LPHAP also reflects the expected UE impact when being positioned, i.e. low power consumption. LMF is responsible for positioning method selection. Usually UE-based positioning will consume more power than NW-based one. Therefore LMF should take into account the LPHAP requirement when determine the positioning method. + +### 6.26.2 Functional Description + +In UE LCS subscription data, it may include "LPHAP indication". During UE registration, AMF fetches the UE LCS subscription data to the LMF. + +- AMF includes the LPHAP indication to LMF when forwards the location request message. +- AMF provisions RAN with LPHAP indication during UE registration procedure and/or LMF provides RAN with LPHAP indication during positioning procedure. This is used by RAN to determine positioning measurement method to the UE. + +### 6.26.3 Procedures + +![Sequence diagram illustrating the LPHAP requirement awareness by LMF procedure. The diagram shows interactions between UE, RAN, AMF, LMF, GMLC, LCS client, and UDM. It is divided into a 'registration phase' and a 'location procedure'. In the registration phase, the UE sends a registration request to the AMF, which then requests subscriber data from the UDM. In the location procedure, the LCS client sends a location request to the GMLC, which is forwarded to the AMF. The AMF then sends a location request to the LMF, including an LPHAP indication. The LMF determines a suitable positioning method based on this indication. The final step is labeled '10 rest of location procedure'.](e26bb66586e464339df27951d5c9355e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant LMF + participant GMLC + participant LCS client + participant UDM + + Note left of UE: registration phase + UE->>AMF: 1. registration request + AMF->>UDM: 2. request subscriber data + UDM-->>AMF: 3. subscriber data (including LPHAP indication) + AMF->>RAN: 4. UE context modification (LPHAP indication) + + Note right of UE: location procedure + LCS client->>GMLC: 5. location request + GMLC->>AMF: 6. Namf_location_request + AMF->>LMF: 7. Nlmf_location_request (LPHAP indication) + Note right of LMF: 8. determine suitable positioning method + Note right of UE: 10 rest of location procedure + +``` + +Sequence diagram illustrating the LPHAP requirement awareness by LMF procedure. The diagram shows interactions between UE, RAN, AMF, LMF, GMLC, LCS client, and UDM. It is divided into a 'registration phase' and a 'location procedure'. In the registration phase, the UE sends a registration request to the AMF, which then requests subscriber data from the UDM. In the location procedure, the LCS client sends a location request to the GMLC, which is forwarded to the AMF. The AMF then sends a location request to the LMF, including an LPHAP indication. The LMF determines a suitable positioning method based on this indication. The final step is labeled '10 rest of location procedure'. + +**Figure 6.26.3-1: LPHAP requirement awareness by LMF** + +1. (registration phase) UE sends requisition request message to AMF. +2. AMF request UDM for UE subscriber data. +3. UDM returns UE subscriber data including LCS relevant parameter, i.e. LPHAP indication. +4. AMF sends the LPHAP indication to RAN in the UE context modification message. +5. (Location procedure) LCS client sends location request to GMLC. +6. GMLC forwards the location request to AMF. +7. AMF sends location request to LMF including LPHAP indication. +8. LMF determines suitable positioning method, by taking into account the LPHAP requirement. +9. If NW based is determined in step8, LMF sends the LPHAP indication to RAN, in the NRPPa message. +10. (rest of the positioning procedure). + +### 6.26.4 Impacts on services, entities, and interfaces + +#### UDM: + +- LPHAP indication in the UE LCS subscription data. + +#### AMF: + +- Retrieve from UDM LPHAP indication in the UE LCS subscription data. +- Provides to LMF LPHAP indication, in the location request. + +- Provisions RAN with LPHAP indication. + +LMF: + +- Receive from AMF LPHAP indication in the location request. +- Determine positioning method, by taking into account the LPHAP requirement. +- sends LPHAP indication to RAN. + +RAN: + +- Receive from AMF LPHAP indication in the UE registration procedure and based on it to determine the handling of NRPPa request from LMF. + +## 6.27 Solution #27: Use Group Information to Correlate GMLC and LMF + +### 6.27.1 Introduction + +This solution addresses the key issue #3: Local Area Restriction for an LMF and GMLC. In this solution, the LMF discovery and selection mechanism by AMF is enhanced to use Group Information as a way to select a "local LMF" for local requests whose LMF should be "local". + +For example, it may be desirable to handle location requests targeting a UE belonging to a factory by using a "local" LMF associated with the factory i.e. possibly hosted on the factory premises, allowing to keep information related with location of the factory users within entities controlled by the factory. Conversely, the location of UE, not members of the factory (users passing by near or within the factory but not members of the factory staff), should not be handled by LMF resources of the factory. + +Another example is the ProSe [19]/Ranging services within the local area, after discovery process, the group information can be exposed to AS/AF through PC1/SR1 interface. Based on the information exposed, AS/AF can update the group and its member information by group management through NEF according to TS 23.501 [2]. When the group information has been aligned, AS/AF can use the group parameter in LCS request to the paired GMLC and LMF in the local area. + +The group information may be transferred directly from AF/LCS Client or derived from the LCS request by AMF. With the group information, which shows the location service requires a local LMF, AMF select a local LMF. + +GMLC/NEF may derive group information from the attributes in the request; when the slice information is correlated to the group communication, AMF may derive the group information from the slice information of the UE. + +Such information can also be used by LMF to select GMLC of the same area to perform event/periodic reporting. + +### 6.27.2 Functional Description + +#### AF/LCS Client Provides Group Parameter + +AF/LCS Client issues LCS request through NEF or GMLC. It may provide an external group ID in the location request as a parameter for LMF selection by AMF. + +NOTE: Detailed definition and/or parameters of group information can be decided during normative phase and/or stage 3 process. + +#### GMLC/NEF Forwards or Derives Group Information + +GMLC and NEF can forward the group information from LCS Client/AF to AMF. + +GMLC and NEF can also derive the group information from following parameters in the LCS request: + +- Group id (ExternalGroupId from AF/LCS Client) may be transferred to AMF through GMLC/NEF (using e.g. Ngmlc\_Location\_ProvideLocation service operation defined in clause 8.4.2 of TS 23.273 [5]), as a complementary information to the UE ID. + +- The ServiceIdentity/Serviceid/svcId in the request from AF/LCS Client. When it is the local service in the local area, NEF or GMLC can derive the group information from the AF/LCS Client information from the request (e.g. LCS Client Identification or ServiceIdentity/Serviceid in Ngmlc\_Location\_ProvideLocation service operation defined in clause 8.4.2 of TS 23.273 [5] or "svcId" in MonitoringEventSubscription of TS 29.522 [24]) and forward the derived target group information to AMF. +- A local (corporate or local service related) GMLC instance may be configured to always add a Group attribute in the LCs requests sent to the AMF +- In some cases (like NI-LR), NEF or GMLC may know the serving TAI/NCGI when receiving the LCS request, and can derive the area information where the GMLC/LMF correlation should be performed. The local group information can be derived independently or can also be queried from UDM. +- Through AF/AS(LCS Client) profile which can be derived by client connection, GMLC/NEF may be aware all the requests from such clients should be restricted to the area. The group information of the area can be attached before the request forwarded to AMF. + +Through above information, GMLC/NEF can instruct AMF to perform the LMF selection logic of the same area. + +#### **AMF Selection Logic with Group and/or Slice Information** + +The AMF may use group information received in a location request to select the LMF. + +Since slicing information is already defined as NF related NRF registration and discovery information, when dedicated slices allocated to the service area and LMF profile in NRF has configured same area (which could be used to drive such GMLC/LMF correlation), AMF could also lookup the LMF instance through the slice information to ensure the LMF of the specific area/service is chosen. + +For the serving TAI/NCGI in the area where the GMLC/LMF correlation should be performed. The local group information can be derived or can be queried from UDM. + +#### **LMF Registration to NRF** + +- The Group ID is added to LMF related NRF registration and discovery Information. +- Based on multiple trigger criteria, the AMF determines whether a group is to be related with a LCS request, and uses this information to select the proper LMF. + +#### **LMF Selection of GMLC in Event/Periodic Reporting** + +When selected, LMF receives the group information from the AMF LCS request. The group information is used in GMLC selection in case of event/periodic report in deferred location process: + +- LMF may be configured with local GMLC address when area correlation is used in the location request. +- LMF may use the group service area to derive the GMLC address for event/periodic reporting, and/or verify the GMLC address in the request and decides accordingly with implementation logic. + +### 6.27.3 Procedures + +![Sequence diagram illustrating the LMF selection based on group information. The diagram shows interactions between UE, NG-RAN, UDM, AMF, Local LMF, Local GMLC, and AF/LCS Client. The process starts with an MT-LR procedure from the AF/LCS Client. The Local GMLC derives group info. The AMF receives the request and may use slice info to select an LMF. The AMF then sends a location determination request to the Local LMF, which requires verification. The Local LMF performs UE positioning with the target UE. Finally, the AMF sends a location determination with verification result to the Local LMF, which then sends an event notification to the Local GMLC and the AF/LCS Client.](af90aabfe3c8c65617da060d82bf99c5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant UDM + participant AMF + participant Local LMF + participant Local GMLC + participant AF/LCS Client + + Note over all: 1. MT-LR procedure from AF/LCS Client + Note right of Local GMLC: 2. Derive Group Info + Note right of AMF: 3. Namf_Location_ProvidePositioningInfo + Note right of AMF: 3.1. slice Info to select LMF + Note right of AMF: 4. Nlmf_Location_DetermineLocation requires verification + Note over all: 5 UE Positioning with target UE + Note right of AMF: 6. Nlmf_Location_DetermineLocation with verification result + Note right of AMF: 7. Nlmf_Location_EventNotify + +``` + +Sequence diagram illustrating the LMF selection based on group information. The diagram shows interactions between UE, NG-RAN, UDM, AMF, Local LMF, Local GMLC, and AF/LCS Client. The process starts with an MT-LR procedure from the AF/LCS Client. The Local GMLC derives group info. The AMF receives the request and may use slice info to select an LMF. The AMF then sends a location determination request to the Local LMF, which requires verification. The Local LMF performs UE positioning with the target UE. Finally, the AMF sends a location determination with verification result to the Local LMF, which then sends an event notification to the Local GMLC and the AF/LCS Client. + +**Figure 6.27.3-1: LMF selection based on group information** + +- Step 1: MT-LR procedure started as defined in TS 23.273 [5]. The service uses local GMLC (or through NEF). AF/LCS Client may take group information in the request parameters. +- Step 2: Local GMLC may use the group information in the request or derive the group information from the context or parameters of the request. +- Step 3: AMF receives the request. +- Step 3.1: For local/edge service, AMF could also use the slice information to select/lookup LMF instance (from NRF). +- Steps 4~6: LMF performs the LCS session. +- Step 7: LMF select the paired GMLC for reporting. When multiple criteria exist, the GMLC selection logic is implementation specific. + +### 6.27.4 Impacts on services, entities, and interfaces + +AS/AF/LCS Client: + +- may provide group information in an LCS request. + +GMLC/NEF: + +- May propagate group information received from AS/AF/LCS Client or may determine group information based on the received location request. + +AMF: + +- Select the LMF according to the group information received from the GMLC. + +## 6.28 Solution #28: Support of PRUs + +### 6.28.1 Introduction + +This solution addresses KI#7 - support of Positioning Reference Units (PRUs) according to the definition in TS 38.305 [6] which is as follows: + +#### **5.4.5 Positioning Reference Unit (PRU)** + +A Positioning Reference Unit (PRU) at a known location can perform positioning measurements (e.g. RSTD, RSRP, UE Rx-Tx Time Difference measurements, etc.) and report these measurements to a location server. In addition, the PRU can transmit SRS to enable TRPs to measure and report UL positioning measurements (e.g. RTOA, UL-AoA, gNB Rx-Tx Time Difference, etc.) from PRU at a known location. The PRU measurements can be compared by a location server with the measurements expected at the known PRU location to determine correction terms for other nearby target devices. The DL- and/or UL location measurements for other target devices can then be corrected based on the previously determined correction terms. + +From a location server perspective, the PRU functionality is realized by a UE with known location. + +The definition shows that a PRU can be a supported as a UE since positioning measurements and SRS transmission can correspond to what is defined for a UE. + +The main principles of this solution are as follows: + +1. Treat PRUs the same as normal UEs from an architectural perspective. +2. Avoid impacting an AMF, NG RAN node, UDM or any existing non-eLCS interface or reference point. +3. Make use of a Supplementary Service protocol (e.g. the protocol defined in TS 24.080 [21]) to enable interaction between a PRU and an LMF that is transparent to other entities. + +NOTE: It is assumed that a PRU can only operate when in coverage of the PLMN to which it belongs or with which it is associated. + +### 6.28.2 Functional Description + +#### 6.28.2.1 Architecture + +The non-roaming reference architecture shown in Figure 4.2.1-1 in TS 23.273 [5] is modified as shown in Figure 6.28.2.1-1 to support a PRU. + +![Non-roaming reference architecture for a PRU. The diagram shows a PRU connected to an AMF via N1. The AMF is connected to an LMF via NL1, to a UDM via N8, to a GMLC via NL2, to an NEF via N51, and to an (R)AN via N2. The GMLC is connected to an LCS Client via Le. The NEF is connected to an AF via N33. The LMF is connected to the UDM via NL6. The UDM is connected to the GMLC via NL5. The PRU is also connected to the (R)AN via N1.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +Non-roaming reference architecture for a PRU. The diagram shows a PRU connected to an AMF via N1. The AMF is connected to an LMF via NL1, to a UDM via N8, to a GMLC via NL2, to an NEF via N51, and to an (R)AN via N2. The GMLC is connected to an LCS Client via Le. The NEF is connected to an AF via N33. The LMF is connected to the UDM via NL6. The UDM is connected to the GMLC via NL5. The PRU is also connected to the (R)AN via N1. + +Figure 6.28.2.1-1: Non-roaming reference architecture for a PRU + +### 6.28.2.2 Protocol Layering + +A PRU interacts with an LMF using the protocol layering shown in Figure 6.28.2.2-1. This is the same protocol layering defined in clause 6.4.1 of TS 38.305 [6] for LMF to UE interaction except for allowing a supplementary services protocol and other positioning protocols besides LPP to be used between an LMF and a PRU at the top level. + +![Protocol Layering for LMF to PRU Signalling. This diagram shows the protocol stacks for the PRU, NG RAN, AMF, and LMF. The PRU stack includes Supp. Svcs or Pos Protocol, NAS, RRC, PDCP, RLC, MAC, and L1. The NG RAN stack includes a Relay section with RRC and NGAP, PDCP and SCTP, RLC and IP, MAC and L2, and L1 and L1. The AMF stack includes a Relay section with NAS and HTTP/2, NGAP, SCTP with TLS and TCP, IP and IP, L2 and L2, and L1 and L1. The LMF stack includes Supp. Svcs or Pos Protocol, HTTP/2, TLS, TCP, IP, L2, and L1. Interfaces are labeled: PRU (NR-Uu, LTE-Uu), NG RAN (NG-C), AMF (NL1), and LMF.](b49477e8f148b5ef044a2fd5a43528f6_img.jpg) + +Protocol Layering for LMF to PRU Signalling. This diagram shows the protocol stacks for the PRU, NG RAN, AMF, and LMF. The PRU stack includes Supp. Svcs or Pos Protocol, NAS, RRC, PDCP, RLC, MAC, and L1. The NG RAN stack includes a Relay section with RRC and NGAP, PDCP and SCTP, RLC and IP, MAC and L2, and L1 and L1. The AMF stack includes a Relay section with NAS and HTTP/2, NGAP, SCTP with TLS and TCP, IP and IP, L2 and L2, and L1 and L1. The LMF stack includes Supp. Svcs or Pos Protocol, HTTP/2, TLS, TCP, IP, L2, and L1. Interfaces are labeled: PRU (NR-Uu, LTE-Uu), NG RAN (NG-C), AMF (NL1), and LMF. + +Figure 6.28.2.2-1: Protocol Layering for LMF to PRU Signalling + +The top protocol layer between the PRU and the LMF is a supplementary services protocol (e.g. as defined in TS 24.080 [21]) or a positioning protocol (e.g. LPP). + +### 6.28.2.3 Multiple LMF Association + +A PRU can be registered with more than one LMF to enable multiple LMFs to obtain location related information from or for the PRU. This is no different to a normal target UE being positioned by different LMFs (e.g. at the same time or at different times). A PRU may be configured with a limit on the number of LMFs that it is allowed to register with. When a PRU receives a conflicting location related request from an LMF (e.g. a request to obtain measurements at the same time as obtaining measurements for another LMF), the PRU can reject the request. The sharing of a PRU by several LMFs might occur in a border area between areas supported by the different LMFs. + +PRU registration in more than one LMF can be avoided or reduced if PRUs are deployed to support only one LMF or if multiple LMF registration is restricted to just a small fraction of PRUs located in border areas shared by two or more LMFs. + +## 6.28.3 Procedures + +### 6.28.3.1 Registration Procedure + +Figure 6.28.3.1-1 shows a registration procedure used by a PRU to register with an LMF. The procedure is used for initial registration when a PRU first starts to access its associated PLMN - e.g. following an initial deployment and initial power on. The procedure can also be used subsequently to perform a registration update to inform the LMF of the continued availability of the PRU or to inform the LMF of some change to the PRU such as a change of location (e.g. a change of tracking area or change of serving AMF) or change of the PRU positioning capabilities. + +![Sequence diagram of the Registration Procedure for a PRU. The diagram shows interactions between PRU, NG-RAN Node, AMF, and LMF. The steps are: 1. UE-Triggered Service Request (PRU to NG-RAN Node); 2. UL NAS TRANSPORT (Routing ID, Registration Request) (NG-RAN Node to AMF); 3. Registration Request (AMF to LMF); 4. Authenticate PRU (LMF to AMF); 5a. Registration Response, Correlation ID (LMF to AMF); 6a. DL NAS TRANSPORT (Registration Response, Routing ID) (AMF to PRU); 5b. Registration Reject (Routing ID) (LMF to AMF); 6b. DL NAS TRANSPORT (Registration Reject (Routing ID)) (AMF to PRU); 7. Positioning Procedure as in Figure 6.x.3.3-1 (dashed box covering steps 5a, 6a, 5b, and 6b).](aa22da43c463563d3d0035722bd79449_img.jpg) + +``` + +sequenceDiagram + participant PRU + participant NG-RAN Node + participant AMF + participant LMF + Note right of PRU: 1. UE-Triggered Service Request + PRU->>NG-RAN Node: + NG-RAN Node->>AMF: 2. UL NAS TRANSPORT (Routing ID, Registration Request) + AMF->>LMF: 3. Registration Request + LMF->>AMF: 4. Authenticate PRU + LMF->>AMF: 5a. Registration Response, Correlation ID + AMF->>PRU: 6a. DL NAS TRANSPORT (Registration Response, Routing ID) + LMF->>AMF: 5b. Registration Reject (Routing ID) + AMF->>PRU: 6b. DL NAS TRANSPORT (Registration Reject (Routing ID)) + Note right of PRU: 7. Positioning Procedure as in Figure 6.x.3.3-1 + +``` + +Sequence diagram of the Registration Procedure for a PRU. The diagram shows interactions between PRU, NG-RAN Node, AMF, and LMF. The steps are: 1. UE-Triggered Service Request (PRU to NG-RAN Node); 2. UL NAS TRANSPORT (Routing ID, Registration Request) (NG-RAN Node to AMF); 3. Registration Request (AMF to LMF); 4. Authenticate PRU (LMF to AMF); 5a. Registration Response, Correlation ID (LMF to AMF); 6a. DL NAS TRANSPORT (Registration Response, Routing ID) (AMF to PRU); 5b. Registration Reject (Routing ID) (LMF to AMF); 6b. DL NAS TRANSPORT (Registration Reject (Routing ID)) (AMF to PRU); 7. Positioning Procedure as in Figure 6.x.3.3-1 (dashed box covering steps 5a, 6a, 5b, and 6b). + +Figure 6.28.3.1-1: Registration Procedure for a PRU + +#### Precondition: + +For initial Registration, a Routing Identifier has been configured in the PRU indicating an LMF. For subsequent Registration, a Routing ID indicating an LMF has been returned to the PRU at step 6a or 6b of a previous Registration. + +NOTE 1: A Correlation ID and a Routing ID are different terms for the same identifier. The term "Correlation ID" is used for an identifier in NL1 service operations between an AMF and LMF while the term "Routing ID" is used for an identifier in a NAS message sent over the N1 reference point between a PRU and AMF. + +1. The PRU performs a UE Triggered Service Request if in CM IDLE state. +2. The PRU sends a supplementary services Registration Request to the serving AMF in an UL NAS TRANSPORT message and includes the preconfigured Routing ID for an initial Registration or the Routing ID received at step 6a or step 6b for the previous Registration. The Registration Request is included in the UL NAS TRANSPORT message as a "Location services message container" at the NAS level which means that an AMF can transfer the message to the LMF at step 3 without a new AMF impact. The Registration Request may include an identity for the PRU (e.g. a SUPI, a PEI or a serial number), a reason for the Registration (e.g. initial Registration, a Registration update, a manually invoked Registration), a location of the PRU if available, optional authentication information, a type of PRU (e.g. whether the PRU is fixed or mobile) and capabilities of the PRU. The capabilities can include capabilities to perform positioning activities associated with a UE. + +Capabilities to perform positioning activities associated with a UE may be indicated by including one or more embedded LPP messages as defined in TS 37.355 [15] in the Registration Request. + +3. The AMF selects an LMF based on the Routing ID and transfers the Registration Request to the LMF. The LMF may be selected based on the Routing ID and the current TAI and/or CGI for the PRU. + +NOTE 2: The AMF sees the PRU as just a normal UE. However, an operator can assign reserved Routing IDs to a PRU different to Routing IDs used for other UEs. For example, all PRUs might be configured with a Routing ID A. The operator can then configure this Routing ID in an AMF such that the AMF selects a preferred LMF for Routing ID A. This may not require any new functionality in an AMF. + +4. The LMF authenticates the PRU and verifies that it is a legitimate for this PLMN. This may use one of the following methods. + +#### **Method A:** + +The AMF includes the SUPI of the PRU at step 3 and the LMF verifies that the SUPI matches a SUPI of a legitimate PRU configured in the LMF. + +#### **Method B:** + +The PRU includes an identification and authentication information at step 2 which the LMF verifies against expected authentication information configured in the LMF for a PRU with this identification. The authentication information might include a ciphering of the PRU identity and/or a current date and time (e.g. UTC) based on a private key stored in secure memory of the PRU. + +#### **Method C:** + +The LMF sends an authentication challenge to the PRU via the AMF as a DL supplementary services message and receives an authentication response from the PRU sent as an UL supplementary services message, where the authentication response is based on a private ciphering key held in secure memory in the PRU. If the LMF is able to store/update PRU information in other LMFs, the serving LMF need not provide Routing IDs for additional LMFs to the UE. + +- 5a. If the LMF is able to authenticate the PRU at step 4 and can accept the Registration, the LMF returns a Registration Response to the serving AMF as a location services supplementary services message and includes a Correlation ID. The Correlation ID is assigned by the LMF to identify the LMF and the PRU. The Registration Response may indicate conditions for performing another Registration with the LMF (e.g. a periodic Registration timer or Registration based on a change of location, change of TAI or change of serving AMF for the PRU). The Registration Response may also provide Routing IDs for additional LMFs with each of which the PRU shall perform a separate Registration. + +NOTE 3: A PRU may be fixed, with re-Registration of the PRU only needed at long periodic intervals. A PRU could instead be mobile (e.g. attached to a vehicle), with re-Registration then minimally needed whenever the serving AMF changes to enable the LMF to reach the PRU for the procedures in clause 6.28.3.2 and 6.28.3.3. If the LMF selected by the new AMF then changes, the previous LMF would discover this from an error response from the previous AMF when instigating the procedure in clause 6.28.3.2 or clause 6.28.3.3. + +NOTE 4: Provision of additional LMFs at step 5a can be implementation and operator dependent. As one example, if a PRU is located in an area supported by both the LMF and one or more other LMFs, the LMF may provide indications of the other LMFs to the PRU. + +- 6a. The serving AMF forwards the Registration Response and a Routing ID equal to the Correlation ID to the PRU. The PRU stores the Routing ID which is used for any repeated Registration with this LMF. If Routing IDs for other LMFs are included in the Registration Response, the PRU performs a Registration with each of these LMFs. + +- 5b. If the LMF is unable to authenticate the PRU at step 4 or cannot accept the Registration for some other reason (e.g. the LMF is the wrong LMF), the LMF sends a Registration Reject to the serving AMF and may include the Routing ID of another LMF with which the PRU shall perform a Registration. + +- 6b. The serving AMF forwards the Registration Reject to the PRU. If a Routing ID is included, the PRU performs a Registration with the LMF associated with this Routing ID. + +NOTE 5: The PRU may be configured with a limit on the number or duration of Registration attempts performed unsuccessfully. When this limit is reached, the PRU may send an indication to some entity in the PLMN. The indication might be a text message or an HTTPS message, for example. + +7. If Registration is performed successfully as in steps 5a and 6a, the LMF may optionally instigate positioning procedures for the PRU as described in clause 6.28.3.3. For example, the positioning procedures may be used to obtain or verify a location of the PRU or obtain the positioning capabilities of the PRU. The LMF also stores information for the PRU including the PRU identity, the Correlation ID assigned at step 5a and the serving AMF instance. + +NOTE 6: Positioning at step 7 may be performed prior to step 5 as an option - e.g. if PRU location needs to be verified before accepting the Registration. + +### 6.28.3.2 Registration Modification Procedure + +Figure 6.28.3.2-1 shows a Registration Modification procedure used by an LMF to change the Registration status of a PRU. The change in status can include deregistering the PRU, changing the conditions for sending Registration updates by the PRU or requesting the PRU to register with additional LMFs. + +![Sequence diagram of the Registration Modification Procedure for a PRU. The diagram shows four entities: PRU, NG-RAN Node, AMF, and LMF. The sequence of messages is: 1. LMF sends 'Registration Modification, Correlation ID' to AMF. 2. AMF sends 'Network Triggered Service Request' to NG-RAN Node (indicated by a dashed box). 3. NG-RAN Node sends 'DL NAS TRANSPORT (Registration Modification, Routing ID)' to PRU. 4. PRU sends 'UL NAS TRANSPORT (Registration Modification Response, Routing ID)' to AMF. 5. AMF sends 'Registration Modification Response, Correlation ID' to LMF.](6322885569221ec51d70560d7dba1339_img.jpg) + +``` + +sequenceDiagram + participant PRU + participant NG-RAN Node + participant AMF + participant LMF + Note right of AMF: 1. Registration Modification, Correlation ID + AMF->>NG-RAN Node: 2. Network Triggered Service Request + Note left of PRU: 3. DL NAS TRANSPORT (Registration Modification, Routing ID) + PRU->>AMF: 4. UL NAS TRANSPORT (Registration Modification Response, Routing ID) + AMF->>LMF: 5. Registration Modification Response, Correlation ID + +``` + +Sequence diagram of the Registration Modification Procedure for a PRU. The diagram shows four entities: PRU, NG-RAN Node, AMF, and LMF. The sequence of messages is: 1. LMF sends 'Registration Modification, Correlation ID' to AMF. 2. AMF sends 'Network Triggered Service Request' to NG-RAN Node (indicated by a dashed box). 3. NG-RAN Node sends 'DL NAS TRANSPORT (Registration Modification, Routing ID)' to PRU. 4. PRU sends 'UL NAS TRANSPORT (Registration Modification Response, Routing ID)' to AMF. 5. AMF sends 'Registration Modification Response, Correlation ID' to LMF. + +Figure 6.28.3.2-1: Registration Modification Procedure for a PRU + +#### Precondition: + +The PRU has previously successfully registered with the LMF using the procedure in clause 6.28.3.1. + +1. The LMF sends a Registration Modification to the serving AMF as a location services supplementary services message and includes the identity of the PRU (e.g. the SUPI) and a Correlation ID identifying the LMF and the PRU. The Registration Modification may indicate to the PRU new conditions for performing Registration updates with the LMF (e.g. a periodic Registration timer or Registration based on a change of location for the PRU). The Registration Modification may also provide Routing IDs for other LMFs with each of which the PRU shall perform a separate Registration. The Registration Modification may further indicate a deregistration of the PRU with the LMF. +2. If the PRU is in CM IDLE state, the serving AMF performs a Network Triggered service request to place the PRU in CM CONNECTED state. +3. The serving AMF forwards the Registration Modification and a Routing ID equal to the Correlation ID to the PRU. +4. The PRU returns a supplementary services Registration Modification response to the serving AMF in an UL NAS TRANSPORT message and includes the Routing ID received in step 3. The Registration Modification response confirms receipt of the information in the Registration Modification at step 3. +5. The serving AMF forwards the Registration Modification response to the LMF indicated by the Routing ID received at step 4 and includes a Correlation ID equal to the Routing ID. + +### 6.28.3.3 Positioning Procedure for a PRU + +Figure 6.28.3.3-1 shows a positioning procedure used by an LMF to obtain location related information from or for a PRU. + +![Sequence diagram showing the positioning procedure for a PRU. The diagram illustrates three steps: 1. UE Assisted and UE Based Positioning Procedure in TS 23.273 Clause 6.11.1 using LPP; 2. Network Assisted Positioning Procedure in TS 23.273 Clause 6.11.2; 3. Non-UE Associated Positioning Procedure in TS 23.273 Clause 6.11.3. The entities involved are PRU, NG-RAN, AMF, and LMF.](64bec4cd45e47e1976245711f702aca2_img.jpg) + +``` + +sequenceDiagram + participant PRU + participant NG-RAN + participant AMF + participant LMF + Note right of LMF: 1. UE Assisted and UE Based Positioning Procedure in TS 23.273 Clause 6.11.1 using LPP + Note right of LMF: 2. Network Assisted Positioning Procedure in TS 23.273 Clause 6.11.2 + Note right of LMF: 3. Non-UE Associated Positioning Procedure in TS 23.273 Clause 6.11.3 + +``` + +Sequence diagram showing the positioning procedure for a PRU. The diagram illustrates three steps: 1. UE Assisted and UE Based Positioning Procedure in TS 23.273 Clause 6.11.1 using LPP; 2. Network Assisted Positioning Procedure in TS 23.273 Clause 6.11.2; 3. Non-UE Associated Positioning Procedure in TS 23.273 Clause 6.11.3. The entities involved are PRU, NG-RAN, AMF, and LMF. + +**Figure 6.28.3.3-1: Positioning Procedure for a PRU** + +#### Precondition: + +The PRU has successfully registered with the LMF using the procedure in clause 6.28.3.1. + +1. The LMF may use the UE Assisted and UE Based Positioning Procedure defined in clause 6.11.1 of TS 23.273 [5] to request positioning capabilities from, provide assistance data to or request location measurements from a PRU when functioning as a target UE. The LMF can access the PRU through the serving AMF identified during Registration. +2. The LMF may use the Network Assisted Positioning Procedure defined in clause 6.11.2 of TS 23.273 [5] to send or request location information related to the PRU to or from the serving NG-RAN node for the PRU. The LMF can access the NG-RAN through the serving AMF identified during Registration. +3. The LMF may use the Obtaining Non-UE Associated Network Assistance Data procedure defined in clause 6.11.3 of TS 23.273 [5] to send or request location information related to the PRU to or from one or more NG-RAN nodes. The LMF can access the NG-RAN nodes through the serving AMF identified during Registration. + +## 6.28.4 Impacts on services, entities, and interfaces + +### PRU: + +- Support Registration and Registration Modification Procedures. + +### LMF: + +- Support Registration and Registration Modification Procedures for a PRU. + +### AMF: + +- no impact. + +## 6.29 Solution #29: Use PRU in 5G LCS Procedures + +### 6.29.1 Introduction + +This solution addresses KI#7, support of Positioning Reference Units and Reference UEs. + +## 6.29.2 Functional Description + +PRU can claim its location or capabilities' attributes during registration process, whether it is static or mobile; these attributes can also be provisioned by OAM so that 5GC components can fetch the information using its identity. + +- The location and capabilities of static PRU can either be claimed by itself in the registration phase or provisioned by OAM. +- The initial location and capabilities of mobile PRU can be identified in same way as static PRU in registration attributes or from OAM; it can also be identified in LPP by triggering an NI-LR process during the registration phase. + +LMF may perform the positioning procedures to PRU during the positioning process of target UE. But LMF may not always use PRU. It depends on the positioning request (QoS requirements, etc), environment profile or UE positioning capabilities and measurements. LMF takes the decision to use PRU and perform the query/discovery process of available/useful PRU instances. + +And there is no conclusion that LCS providers want to use full PRU capabilities to all LCS requests of all UEs. So, PRU usage is decided and its information is needed during the request procedures. They are on the request level instead of subscription level. + +For request level information, GMLC is the legacy portal for all LCS related queries. For future flexibility, GMLC performs the storage and query/discovery procedures of PRUs. + +GMLC can provide different PRU features to different client profiles and/or request attributes. PRU capabilities can be discovered differently according to different deployment or LCS provider policies. + +PRU information includes the following attributes stored in GMLC to be discovered/queried: + +1. PRU location information and its mobility and static attributes. +2. PRU capability and optionally, some measurements which don't change for different target UE transactions, like TA value of static PRU against static TRP. +3. Serving AMF and LMF instance of the PRU. + +Due to different LMF selection criteria in clause 5.1 of TS 23.273 [5] and solution to KI#3. When positioning procedures include both target UE and PRU, the serving LMF for UE and PRU may not be the same LMF instance. This solution provides inter-LMF communications. + +## 6.29.3 Procedures + +### 6.29.3.1 PRU Information Update + +![Sequence diagram of the PRU information update procedure. Lifelines: UE, PRU, NG-RAN, AMF, LMF for PRU, GMLC. The sequence starts with PRU registration (1) from PRU to AMF. Then LMF Selection (2) from AMF to LMF for PRU. Next, Nlmf_Location_DetermineLocation (3) from AMF to LMF for PRU. A block '3.1 UE Positioning with PRU' is shown. Then, 4.a Nlmf_Location_EventNotify (PRU info) from LMF for PRU to GMLC. 4.b Nlmf_Location_DetermineLocation(PRU info) from LMF for PRU to AMF. Finally, 5.b Namf_Location_EventNotify(PRU info) from AMF to GMLC.](57134800ac3a97b6212b27b93aa196ac_img.jpg) + +``` + +sequenceDiagram + participant PRU + participant AMF + participant NG-RAN + participant UE + participant LMF as LMF for PRU + participant GMLC + + Note right of PRU: 1. PRU registration + PRU->>AMF: + Note right of AMF: 2. LMF Selection + AMF->>LMF: + Note right of AMF: 3. Nlmf_Location_DetermineLocation + AMF->>LMF: + Note right of LMF: 3.1 UE Positioning with PRU + Note right of LMF: 4.a Nlmf_Location_EventNotify (PRU info) + LMF->>GMLC: + Note right of LMF: 4.b Nlmf_Location_DetermineLocation(PRU info) + LMF->>AMF: + Note right of AMF: 5.b Namf_Location_EventNotify(PRU info) + AMF->>GMLC: + +``` + +Sequence diagram of the PRU information update procedure. Lifelines: UE, PRU, NG-RAN, AMF, LMF for PRU, GMLC. The sequence starts with PRU registration (1) from PRU to AMF. Then LMF Selection (2) from AMF to LMF for PRU. Next, Nlmf\_Location\_DetermineLocation (3) from AMF to LMF for PRU. A block '3.1 UE Positioning with PRU' is shown. Then, 4.a Nlmf\_Location\_EventNotify (PRU info) from LMF for PRU to GMLC. 4.b Nlmf\_Location\_DetermineLocation(PRU info) from LMF for PRU to AMF. Finally, 5.b Namf\_Location\_EventNotify(PRU info) from AMF to GMLC. + +Figure 6.29.3.1-1: PRU information update procedure + +- Step 1: PRU performs registration. The registration may contain PRU attributes (including location estimate, capabilities). +- Step 2: AMF select LMF instance based on PRU attributes or other criteria. If PRU attributes are available, they are forwarded to LMF. +- Step 3: When necessary PRU attributes are missing, LMF perform LCS procedures to PRU to fetch these attributes. +- Step 4: LMF may notify GMLC directly with PRU information or indirectly through AMF. +- Option a: If PRU takes GMLC address in registration, LMF gets the information from AMF or LMF can derive GMLC address, the GMLC address can be used directly to send Nlmf\_Location\_EventNotify with PRU information to GMLC. +- Option b: LMF may use AMF to forward the PRU information to GMLC. AMF may derive the GMLC address. +- NOTE 1: Nlmf\_Location\_DetermineLocation response takes not only location result, but also additional information of PRU. +- NOTE 2: AMF selection of LMF, LMF/AMF selection of GMLC could be implementation specific. + +### 6.29.3.2 Positioning Procedures with PRU + +![Sequence diagram illustrating the positioning procedure with PRU. The diagram shows interactions between UE, PRU, AMF for PRU, AMF for UE, LMF of UE, GMLC/LRF, and LMF of PRU. The process starts with a general positioning procedure (1. NI-LR MO-LR or MT-LR), followed by a location determination request (2. Nlmf_Location_DetermineLocation). The main part involves UE positioning with a target UE (3.1), where the LMF decides to use PRU (3.2), discovers it (3.3), provides info to AMF (3.4), determines location (3.5), initiates a PRU session (3.6), receives results (3.7), and continues the target UE session (3.8).](54159e6d8f5ecc73ad262758e3a60677_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PRU + participant AMF_PRU as AMF for PRU + participant AMF_UE as AMF for UE + participant LMF_UE as LMF of UE + participant GMLC_LRF as GMLC/LRF + participant LMF_PRU as LMF of PRU + + Note over all: 1. NI-LR MO-LR or MT-LR procedure + Note over AMF_UE, LMF_UE: 2. Nlmf_Location_DetermineLocation + Note over all: 3.1 UE Positioning with target UE + Note over LMF_UE: 3.2 LMF decides to use PRU + Note over LMF_UE, GMLC_LRF: 3.3 Ngmlc_Location_PRUDiscovery + Note over LMF_UE, AMF_PRU: 3.4 Namf_Location_ProvidePositioningInfo + Note over LMF_UE, LMF_PRU: 3.5. Nlmf_Location_DetermineLocation + Note over all: 3.6 Necessary PRU Positioning Session + Note over AMF_PRU, LMF_UE: 3.7. Response with needed result from PRU session + Note over all: 3.8 Continue target UE session with PRU result + +``` + +Sequence diagram illustrating the positioning procedure with PRU. The diagram shows interactions between UE, PRU, AMF for PRU, AMF for UE, LMF of UE, GMLC/LRF, and LMF of PRU. The process starts with a general positioning procedure (1. NI-LR MO-LR or MT-LR), followed by a location determination request (2. Nlmf\_Location\_DetermineLocation). The main part involves UE positioning with a target UE (3.1), where the LMF decides to use PRU (3.2), discovers it (3.3), provides info to AMF (3.4), determines location (3.5), initiates a PRU session (3.6), receives results (3.7), and continues the target UE session (3.8). + +**Figure 6.29.3.2-1: Positioning procedure with PRU** + +Step 1: LCS NI-LR, MO-LR or MT-LR as defined in TS 23.273 [5]. + +Step 2: Request arrives to serving LMF of UE. + +Steps 3.1~3.2: LMF may decide to use PRU before/during/after positioning procedure of target UE. + +Step 3.3: LMF queries the GMLC for PRU discovery. It may use the target UE information or serving TAI/NCGI information as discovery parameters. LMF may get the GMLC information of the PRU by following ways. + +- LMF could query NRF using serving TAI/NCGI of target UE. +- LMF could get the serving GMLC if they are correlated as per solutions of KI#3 of certain local area. +- LMF may use implementation specific methods to get GMLC instance. + +Step 3.4: Based on PRU capabilities, with AMF information of PRU attributes, LMF for target UE sends request to serving AMF of PRU with requested positioning information of PRU. + +NOTE 1: With implementation specific policy, the serving LMF of PRU during its registration phase can be used. In this case, LMF for target UE should still send the request through AMF in case PRU is in CM-IDLE/RRC-INACTIVE state. + +Steps 3.5~3.7: Serving LMF of PRU performs the requested procedures and replies the necessary information back to the serving LMF of target UE. + +NOTE 2: Different PRU may use different LMF instances. The LMF instance decided by serving AMF may not be same as serving LMF during the registration phase. + +Step 3.8: LMF for target UE may use the result from PRU session to optimize its positioning procedures. + +### 6.29.4 Impacts on services, entities, and interfaces + +AMF: Notify PRU info to GMLC. + +GMLC: + +- Receive PRU info from AMF or LMF. + +- Provide PRU info to LMF based on request from LMF. + +LMF: + +- Notify PRU info to GMLC. +- Request PRU info from GMLC. + +## 6.30 Solution #30: location service continuity for UE moves between NG-RAN nodes + +### 6.30.1 Introduction + +This solution addresses Key Issue #8, mainly focus on the deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events procedure and the location service continuity for UE moves between NG-RAN nodes. + +### 6.30.2 Functional description + +The procedures in clause 6.30.3.1~6.30.3.3 are used for the location service continuity for UE moves between NG-RAN nodes, under the following mobility cases: + +- Moving in RRC-inactive for UL and DL positioning: with anchor NG-RAN relocation, target NG-RAN acquire the positioning related information via the retrieve UE context message, target NG-RAN update the positioning related configuration and sends the latest configuration to LMF. AMF or old LMF determines whether need trigger the LMF change procedure and enable the latest configuration reach to the correct LMF. After handover complete, AMF notify LMF the target cell ID and/or the target NG-RAN ID, based on that information, LMF configures the selected neighbour NG-RANs with the latest configuration. +- Moving in CM-connected with RRC-connected for UL and DL positioning: during the handover preparation phase, source NG-RAN sends the positioning related information to target NG-RAN via the handover message, target NG-RAN updates the positioning related configuration and sends the latest configuration to LMF. AMF or old LMF determine whether need trigger the LMF change procedure and enable the latest configuration reach to the correct LMF. AMF notify LMF the target cell ID and/or the target NG-RAN ID, based on that information, LMF configures the selected neighbour NG-RANs with the latest configuration. + +NOTE: RAN WG coordination is needed. + +- Moving in CM-IDLE: during the registration procedure, after new AMF receive the UE context information from old AMF, if AMF finds UE has positioning related information, AMF sends the new AMF instance ID to LMF via the next periodical N1messageNotify. + +## 6.30.3 Procedures + +### 6.30.3.1 Location Service Continuity for UE moves in RRC-inactive + +![Sequence diagram for Location Service Continuity for UE moves in RRC-inactive. Lifelines: UE, Source NG-RAN, Target NG-RAN, AMF, Old LMF, New LMF, Selected neighbour NG-RANs. The diagram shows two main paths: one where the AMF determines the new LMF (steps 7-15) and another where the Old LMF determines the new LMF (steps 16-23).](ceb9a4217df4b6e301712b3b88b09c69_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant AMF + participant Old LMF + participant New LMF + participant Selected neighbour NG-RANs + + Note over UE, Selected neighbour NG-RANs: 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in TS 23.273, clause 6.3.1, steps 1~21. + UE->>Source NG-RAN: 2. RRC_INACTIVE + UE->>Source NG-RAN: 3. Event Detected + UE->>Source NG-RAN: 4. RRC Resume + Source NG-RAN->>Target NG-RAN: 5. with anchor NG-RAN relocation, based on RAN R17 conclusion, target NG-RAN will acquire the old LMF ID and the positioning related information, target NG-RAN update the positioning configuration based on the positioning related information. + Target NG-RAN->>AMF: 6. N2 Path Switch Request + Note right of AMF: if AMF determine new LMF + AMF->>Old LMF: 7. Based on TS 23.273, if AMF determine the LMF change, as defined in clause 6.4 of TS 23.273, step 4~8. + Old LMF->>AMF: 8. N2 Path Switch Request ACK + AMF->>Target NG-RAN: 9. Uplink UE associated NRPPa transport(Positioning Information Update (Positioning configuration), Routing ID(i.e., source LMF ID)) + Note right of AMF: 10. if AMF finds UE has positioning related information and if the LMF change is on-going, after the LMF change complete, the AMF map the source LMF ID to the new LMF ID, then sends the NRPPa PDU to the new LMF. + AMF->>New LMF: 11. Namf_Communication_N2InfoNotify([Positioning Information Update],[Global RAN node ID], [cell ID],[handover complete notification]) + New LMF->>AMF: 12. Namf_Communication_N1N2MessageTransfer([NRPPa PDU (NRPPa Transaction ID)], [lcs correlation ID]) + AMF->>Target NG-RAN: 13. Downlink UE associated NRPPa transport (NRPPa PDU, new LMF ID, [indicate the LMF has been changed]) + Target NG-RAN->>Selected neighbour NG-RANs: 14. latest positioning configuration + Note right of Target NG-RAN: 15. update the LMF ID + + Note right of AMF: if AMF does not determine new LMF, old LMF determine new LMF + Old LMF->>AMF: 16. N2 Path Switch Request ACK + AMF->>Target NG-RAN: 17. Uplink UE associated NRPPa transport(Positioning Information Update (Positioning configuration), Routing ID(i.e., source LMF ID)) + AMF->>Old LMF: 18. Namf_Communication_N2InfoNotify(Positioning Information Update (NRPPa Transaction ID), [RAN node ID], [cell ID],[handover complete notification]) + Note right of Old LMF: 19. based on TS 23.273, if old LMF determine the LMF change, as defined in clause 6.4 of TS 23.273, step 5~7. + Old LMF->>New LMF: 20. Namf_Communication_N1N2MessageTransfer([NRPPa PDU (NRPPa Transaction ID)], [new LMF ID],[indicate the LMF has been changed]) + New LMF->>AMF: 21. Downlink UE associated NRPPa transport (NRPPa PDU, new LMF ID, [indicate the LMF has been changed]) + AMF->>Target NG-RAN: 22. latest positioning configuration + Target NG-RAN->>Selected neighbour NG-RANs: 23. update the LMF ID + +``` + +Sequence diagram for Location Service Continuity for UE moves in RRC-inactive. Lifelines: UE, Source NG-RAN, Target NG-RAN, AMF, Old LMF, New LMF, Selected neighbour NG-RANs. The diagram shows two main paths: one where the AMF determines the new LMF (steps 7-15) and another where the Old LMF determines the new LMF (steps 16-23). + +Figure 6.30.3.1-1: Location Service Continuity for UE moves in RRC-inactive + +1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in steps 1~21 in clause 6.3.1 of TS 23.273 [5]. +- 2~4. UE in RRC-inactive state and finds event is triggered, UE sends the RRC Resume to target NG-RAN. +5. With anchor NG-RAN relocation, target NG-RAN acquire the old LMF ID and the positioning related information (based on the RAN 17 conclusion, see clause 9.2.1.13 and clause 9.2.3.168 of TS 38.423 [25]), target NG-RAN update the positioning configuration (e.g. SRS configuration) based on the positioning related information (e.g. the requested SRS Transmission Characteristics). +6. Target NG-RAN sends the N2 Path Switch Request to AMF, based on the UE location information (i.e. the ULI in path switch request), either AMF or old LMF can determine whether LMF need change (i.e. clause 6.4 of TS 23.273 [5]), if AMF determine LMF change, steps 7~15 are performed and steps 16~23 are skipped, after LMF change complete, the AMF need store the mapping relationship between the source LMF ID and the new LMF ID. Otherwise, if old LMF determine LMF change, steps 7~15 are skipped and steps 16~23 are performed. + +If AMF determine the LMF change (i.e. as described in TS 23.273, clause 6.4, step 4~7), the following steps 7~15 are performed and steps 16~23 are skipped. + +NOTE 1: No sequence restrict for step 7 and step 8, step 7 and step 8 may perform in parallel. + +8~9. Target NG-RAN invokes the Uplink UE associated NRPPa transport message to AMF, includes the routing ID (i.e. the old LMF ID), the NRPPa PDU (i.e. the Positioning Information Update (includes the positioning configuration)). + +10. If AMF finds the LMF is changed, the AMF determine the source LMF ID corresponding new LMF ID, then sends the NRPPa PDU to the new LMF. + +11. AMF invokes Namf\_Communication\_N2InfoNotify to new LMF, includes the NRPPa PDU (e.g. the update positioning configuration), the NG-RAN node ID and/or the target cell ID, the handover complete notification. + +12. The new LMF invokes the Namf\_Communication\_N1N2MessageTransfer to AMF, includes the NRPPa PDU (e.g. the Positioning Information Activation), the LCS correlation ID. + +13. After receive the Namf\_Communication\_N1N2MessageTransfer from new LMF, the AMF invokes Downlink UE associated NRPPa transport message to target NG-RAN, includes the new LMF ID, the indication to indicates a change of LMF. + +14. Based on the handover complete notification and the target cell ID and/or the target NG-RAN node ID, the new LMF configure the selected neighbour NG-RAN nodes with the latest positioning configuration. + +NOTE 2: No sequence restrict for steps 12~15 and step 14, steps 12~15 and step 14 may perform in parallel. + +15. The target NG-RAN update the LMF ID. + +If old LMF determines the LMF change (i.e. as described in step 4~7 in clause 6.4 of TS 23.273 [5]), the following steps 16~23 are performed and steps 7~15 are skipped. + +17. Target NG-RAN invokes the Uplink UE associated NRPPa transport message to AMF, includes the routing ID (i.e. the old LMF ID), the NRPPa PDU (i.e. the Positioning Information Update (includes the positioning configuration)). + +18. The AMF invokes Namf\_Communication\_N2InfoNotify to new LMF, includes the NRPPa PDU (e.g. the update positioning configuration), the NG-RAN node ID and/or the target cell ID, the handover complete notification. + +20. The new LMF invokes the Namf\_Communication\_N1N2MessageTransfer from new LMF, includes the new LMF ID, the indication to indicate a change of LMF. + +21. The AMF invokes Downlink UE associated NRPPa transport message to target NG-RAN, includes the new LMF ID, the indication to indicates a change of LMF.22. Based on the handover complete notification and the target cell ID and/or the target NG-RAN node ID, the new LMF configure the selected neighbour NG-RAN nodes with the latest positioning configuration. + +23. The target NG-RAN update the LMF ID. + +NOTE 3: No sequence restrict for step 22 and steps 20~23, step 22 and steps 2~23 may perform in parallel. + +### 6.30.3.2 Location Service Continuity for UE moves in CM-connected with RRC-connected + +#### 6.30.3.2.1 Xn handover + +![Sequence diagram for Location Service Continuity for UE moves in CM-connected with RRC-connected Xn handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, Old LMF, New LMF, and Selected neighbour NG-RANs. It details the process of acquiring positioning information, determining if an LMF change is needed, and updating the UE's positioning configuration.](67a1dd734d3de6e31754caf85d6fe77f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant AMF + participant Old LMF + participant New LMF + participant Selected neighbour NG-RANs + + Note over all: 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in TS 23.273, clause 6.3.1, steps 1~21. + UE->>Source NG-RAN: 2. Measurement Report + Note over Source NG-RAN, Target NG-RAN: 3. target NG-RAN acquire the old LMF ID and the positioning related information, target NG-RAN update the positioning configuration based on the positioning related information. + Source NG-RAN->>Target NG-RAN: 4. Handover Confirm + Target NG-RAN->>AMF: 5. N2 Path Switch Request + + alt if AMF determine new LMF + Note over AMF: 6. based on TS 23.273, if AMF determine the LMF change, as defined in clause 6.4 of TS 23.273, step 4~8. + AMF->>Target NG-RAN: 7. N2 Path Switch Request ACK + Target NG-RAN->>AMF: 8. Uplink UE associated NRPPa transport(Positioning Information Update (Positioning configuration), Routing ID(i.e., source LMF ID)) + Note over AMF: 9. if AMF finds UE has positioning related information and if the LMF change is on-going, after the LMF change complete, the AMF map the source LMF ID to the new LMF ID, then sends the NRPPa PDU to the new LMF. + AMF->>New LMF: 10. Namf_Communication_N2InfoNotify([Positioning Information Update],[Global RAN node ID],[cell ID],[handover complete notification]) + New LMF->>AMF: 11. Namf_Communication_N1N2MessageTransfer([NRPPa PDU (NRPPa Transaction ID)] [lcs correlation ID]) + AMF->>Target NG-RAN: 12. Downlink UE associated NRPPa transport (NRPPa PDU, new LMF ID, [indicate the LMF has been changed]) + Target NG-RAN->>Selected neighbour NG-RANs: 13. latest positioning configuration + Note over Target NG-RAN: 14. update the LMF ID + else if AMF does not determine new LMF, old LMF determine new LMF + Note over Old LMF: 18. based on TS 23.273, if old LMF determine the LMF change, as defined in clause 6.4 of TS 23.273, step 5~7. + AMF->>Target NG-RAN: 15. N2 Path Switch Request ACK + Target NG-RAN->>AMF: 16. Uplink UE associated NRPPa transport(Positioning Information Update (Positioning configuration), Routing ID(i.e., source LMF ID)) + AMF->>Old LMF: 17. Namf_Communication_N2InfoNotify(Positioning Information Update (NRPPa Transaction ID), [Global RAN node ID], [cell ID], [handover complete notification]) + Note over Old LMF, New LMF: 19. same as steps 20~23 as mentioned in clause 6.X.3.1. + end + +``` + +Sequence diagram for Location Service Continuity for UE moves in CM-connected with RRC-connected Xn handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, Old LMF, New LMF, and Selected neighbour NG-RANs. It details the process of acquiring positioning information, determining if an LMF change is needed, and updating the UE's positioning configuration. + +Figure 6.30.3.2.1-1: Location Service Continuity for UE moves in CM-connected with RRC-connected Xn handover + +1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in steps 1~21 in clause 6.3.1 of TS 23.273 [5]. +- 2~4. Target NG-RAN acquire the old LMF ID and the positioning related information (e.g. via the handover request message), target NG-RAN update the positioning configuration based on the positioning related information and sends the update positioning configuration to UE. 5. Target NG-RAN sends the N2 Path Switch Request to AMF, based on clause 6.4 of TS 23.273 [5], either AMF or old LMF can determine whether LMF need change, if AMF determine LMF change, steps 6~14 are performed and steps 15~19 are skipped, if old LMF determine LMF change, steps 6~14 are skipped and steps 15~19 are performed. +- 6~14. Same as steps 7~19 as described in clause 6.30.3.1. +- 15~19. Same as steps 16~23 as described in clause 6.30.3.1. + +## 6.30.3.2.2 N2 handover + +![Sequence diagram for Location Service Continuity for UE moves in CM-connected with RRC connected-N2 handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, Old LMF, New LMF, and Selected neighbor NG-RANs. It details the flow of positioning information and LMF determination during a handover.](b9d5785720b6edd0917019f211469dde_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant AMF + participant Old LMF + participant New LMF + participant Selected neighbor NG-RANs + + Note over UE, Selected neighbor NG-RANs: 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in TS 23.273, clause 6.3.1, steps 1~21. + UE->>Source NG-RAN: 2. Measurement Report + Source NG-RAN->>Target NG-RAN: 3. target NG-RAN acquire the old LMF ID and the positioning related information, target NG-RAN update the positioning configuration based on the positioning related information + Source NG-RAN->>Target NG-RAN: 4. Handover Confirm + Target NG-RAN->>AMF: 5. Handover Notify + + Note right of AMF: if AMF determine new LMF + AMF->>Old LMF: 6. based on TS 23.273, if AMF determine the LMF change, as defined in clause 6.4 of TS 23.273, step 4~8. + AMF->>New LMF: 7. Uplink UE associated NRPPa transport(Positioning Information Update (Positioning configuration), Routing ID(i.e., source LMF ID)) + Note right of AMF: 8. if AMF finds UE has positioning related information and if the LMF change is on-going, after the LMF change complete, the AMF map the source LMF ID to the new LMF ID, then sends the NRPPa PDU to the new LMF. + AMF->>Old LMF: 9. Namf_Communication_N2InfoNotify([Positioning Information Update],[Global RAN node ID], [cell ID],[handover complete notification]) + AMF->>New LMF: 10. Namf_Communication_N1N2MessageTransfer([NRPPa PDU (NRPPa Transaction ID)], [lcs correlation ID]) + AMF->>Target NG-RAN: 11. Downlink UE associated NRPPa transport (NRPPa PDU, new LMF ID, [indicate the LMF has been changed]) + Target NG-RAN->>Selected neighbor NG-RANs: 12. latest positioning configuration + Note right of Target NG-RAN: 13. update the LMF ID + + Note right of AMF: if AMF does not determine new LMF, old LMF determine new LMF + AMF->>Old LMF: 14. Uplink UE associated NRPPa transport(Positioning Information Update (Positioning configuration), Routing ID(i.e., source LMF ID)) + AMF->>Old LMF: 15. Namf_Communication_N2InfoNotify(Positioning Information Update (NRPPa Transaction ID), [Global RAN node ID], [cell ID],[handover complete notification]) + Note right of Old LMF: 16. based on TS 23.273, if old LMF determine the LMF change, as defined in clause 6.4 of TS 23.273, step 5~7. + Old LMF->>New LMF: 17. same as steps 20~23 as described in clause 6.X.3.1. + +``` + +Sequence diagram for Location Service Continuity for UE moves in CM-connected with RRC connected-N2 handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, Old LMF, New LMF, and Selected neighbor NG-RANs. It details the flow of positioning information and LMF determination during a handover. + +**Figure 6.30.3.2.2-2: Location Service Continuity for UE moves in CM-connected with RRC connected-N2 handover** + +1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in steps 1~21 in clause 6.3.1 of TS 23.273 [5]. +- 2~4. Target NG-RAN acquire the old LMF ID and the positioning related information (e.g. via the handover required and handover request message), target NG-RAN update the positioning configuration based on the positioning related information and sends the update positioning configuration to UE. 5. Target NG-RAN sends the Handover Notify to AMF, based on clause 6.4 of TS 23.273 [5], either AMF or old LMF can determine whether LMF need change, if AMF determine LMF change, steps 6~14 are performed and steps 15~19 are skipped, if old LMF determine LMF change, steps 6~14 are skipped and steps 15~19 are performed. + +NOTE The AMF in figure 6.30.3.2.2-2 can be referred to the T-AMF, i.e. T-AMF determines whether the LMF need change based on the ULI (i.e. the target cell ID) included in handover notify message. + +- 6~13. Same as steps 7~15 as described in clause 6.30.3.1. +- 14~17. Same as steps 16~23 as described in clause 6.30.3.1. + +### 6.30.3.3 Location Service Continuity for UE moves in CM-IDLE + +![Sequence diagram illustrating Location Service Continuity for UE moves in CM-IDLE. The diagram shows interactions between UE, NG-RAN, New AMF, Old AMF, LMF, GMLC, and LCS client. The process starts with deferred 5GC-MT-LR procedures (steps 1-3). When the UE moves, a Registration Request is sent to the New AMF (step 4). The New AMF retrieves UE context from the Old AMF (steps 6-8). If positioning information is found, the New AMF sends the new AMF instance ID to the LMF via N1messageNotify (step 9). The UE then detects an event (step 10) and sends an Event Report to the New AMF (step 11). The New AMF sends Namf_N1MessageNotify to the LMF (step 12). Finally, the deferred 5GC-MT-LR procedure continues (step 13).](1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant New AMF + participant Old AMF + participant LMF + participant GMLC + participant LCS client + + Note over UE, LCS client: 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in TS 23.273, clause 6.3.1, steps 1~21. + Note over UE, LCS client: 2. periodical event triggered, UE sends the event report to 5GC, as defined in TS 23.273, clause 6.3.1 steps 22~30. + Note over UE, LCS client: 3. wait for the next periodical event trigger, UE may become CM-IDLE state. + + UE->>NG-RAN: 4. Registration Request + Note over NG-RAN: 5. AMF selection + NG-RAN->>New AMF: 6. Registration Request + New AMF->>Old AMF: 7. Namf_CommunicationUEContextTransfer + Old AMF-->>New AMF: 8. Namf_CommunicationUEContextTransfer Response + Note over New AMF: 9. After retrieve the UE context information, if AMF finds UE has positioning related information, AMF sends the new AMF instance ID to LMF, e.g., via the next periodical N1messageNotify. + Note over New AMF: ..... + Note over UE: 10. Event Detected + UE->>New AMF: 11. Event Report + New AMF->>LMF: 12. Namf_N1MessageNotify(new AMF instance ID), [lesCorrelationId] + Note over UE, LCS client: 13. continue the deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure as defined in TS 23.273, clause 6.3.1 + +``` + +Sequence diagram illustrating Location Service Continuity for UE moves in CM-IDLE. The diagram shows interactions between UE, NG-RAN, New AMF, Old AMF, LMF, GMLC, and LCS client. The process starts with deferred 5GC-MT-LR procedures (steps 1-3). When the UE moves, a Registration Request is sent to the New AMF (step 4). The New AMF retrieves UE context from the Old AMF (steps 6-8). If positioning information is found, the New AMF sends the new AMF instance ID to the LMF via N1messageNotify (step 9). The UE then detects an event (step 10) and sends an Event Report to the New AMF (step 11). The New AMF sends Namf\_N1MessageNotify to the LMF (step 12). Finally, the deferred 5GC-MT-LR procedure continues (step 13). + +**Figure 6.30.3.3-1: Location Service Continuity for UE moves in CM-IDLE** + +1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure, as defined in steps 1~21 in clause 6.3.1 of TS 23.273 [5]. +2. Periodic event triggered, UE sends the event report to 5GC, as described in steps 22~30 in clause 6.3.1 of TS 23.273 [5]. +3. Before next time periodic event triggered, UE may go to CM-IDLE state. +- 4~8. As UE moving, registration procedure may performed, as defined in steps 1~5 in clause 4.2.2.2.2 of TS 23.502 [3]. +9. After retrieve the UE context information, if AMF finds UE has positioning related information (i.e. if AMF has stored the periodic/deferred location service context), AMF sends the new AMF instance ID to LMF, e.g. via the next periodical N1messageNotify in step 12. +- 10~11. Same as steps 22~25 as defined in clause 6.3.1 of TS 23.273 [5]. +12. AMF sends the Namf\_N1MessageNotify to LMF, includes the new AMF instance ID, based on the received message, the LMF update the location context, i.e. substitute the old AMF instance ID to the new AMF instance ID. +13. Same as steps 26~30 in clause 6.3.1 of TS 23.273 [5]. + +### 6.30.4 Impacts on services, entities, and interfaces + +#### NG-RAN: + +- exchange the positioning related information and positioning related configuration during the handover preparation phase. +- After positioning configuration update, trigger to sends the latest positioning configuration to LMF. + +#### LMF: + +- After receive the positioning configuration and the target cell ID/target NG-RAN node ID, select and configure the candidate neighbour NG-RAN with the latest positioning configuration. + +- If LMF determine the LMF change, the new LMF invokes the Namf\_Communication\_N1N2MessageTransfer to AMF, includes the new LMF ID, the indication to indicate a change of LMF. + +AMF: + +- After receive the Uplink UE associated NRPPa transport, if UE has positioning related information and if AMF is changed, indicates the new AMF instance ID to LMF.- After retrieve the UE context information, if UE has positioning related information and if LMF is changed, map the source LMF ID to the new LMF ID and sends the NRPPa PDU to the new LMF. +- After handover complete, notify LMF the target cell ID and/or the target NG-RAN node ID. +- After receive downlink UE associated NRPPa transport, notify the new LMF ID and the LMF change indication to NG-RAN. + +## 6.31 Solution #31: location service continuity between EPS and 5GS (bi-direction) + +### 6.31.1 Introduction + +This solution addresses Key Issue #8, mainly focus on the location service continuity between EPS and 5GS (bi-direction). + +### 6.31.2 Functional description + +This solution include following procedures: + +- Location service continuity from 5GS to EPS: + +During periodic location service triggered, if AMF/LMF finds the UE reporting type includes "EUTRAN" and if the required "LCS QoS class" is "multiple QoS class", the AMF/LMF determines the corresponding location QoS can be applicable to EPS, e.g. AMF or LMF map the QoS class to "Best Effort" and choose the most stringent value from the "LocationQoS" as the QoS requirement, LMF sends these parameters to UE and AMF if AMF does not determine the location QoS applicable to EPS. + +After receive the handover required, if AMF finds UE can support interworking between 5GS and EPS, AMF sends the 5GS location QoS corresponding EPS location QoS to GMLC. + +After handover complete, if UE finds periodical event is triggered and if UE finds it has moved to EPS, the UE sends LCS MO-LR Invoke message, carry the location QoS can be applicable to EPS. + +- Location service continuity from EPS to 5GS: + +After receive the handover required message, if MME finds UE has positioning related information, MME trigger to send the handover to 5GC notification to GMLC. + +After handover complete, if UE finds periodical event is triggered and if UE finds it has moved to 5GS, UE sends event report message to 5GS. + +NOTE 1: If UE finds handover is not complete but the event is triggered, UE need wait handover complete to sends the event report message in 5GS or sends the LCS MO-LR Invoke message in EPS. + +NOTE 2: The procedures can be applied to all types of Location service. For deferred/periodic MT-LR, the core network also need coordinate with UE to enable UE sends the suitable signalling message and carry the suitable location QoS after the location event is triggered. + +### 6.31.3 Architecture Assumption + +It is assumed to use the co-located GMLC. + +![Architecture Assumption diagram showing connections between SCEF+NEF, HSS+UDM, MME, GMLC, AMF, E-UTRAN, 5G AN, and various clients.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +The diagram illustrates a network architecture assumption. At the top, a box labeled 'SCEF+NEF' is connected to 'HSS+UDM' via a vertical line labeled 'NL5'. 'SCEF+NEF' also has a horizontal line labeled 'T6a' extending to the left to an 'MME' box, and a horizontal line labeled 'N51' extending to the right to an 'AMF' box. The 'MME' box is connected to 'HSS+UDM' via a diagonal line labeled 'S6a', to 'GMLC' via a horizontal line labeled 'SLg', to 'E-UTRAN' via a vertical line labeled 'S1-MME', and to 'E-SMLC' via a diagonal line labeled 'SLs'. The 'E-UTRAN' box is connected to a 'UE' box via a vertical line labeled 'LTE-uu'. The 'GMLC' box is connected to 'HSS+UDM' via a vertical line, to 'NEF' via a vertical line, to 'LMF' via a horizontal line labeled 'NL2', and to 'AMF' via a horizontal line labeled 'NL2'. The 'NEF' box is connected to 'LCS client' via a vertical line. The 'LMF' box is connected to 'AMF' via a diagonal line labeled 'NL1'. The 'AMF' box is connected to 'HSS+UDM' via a diagonal line labeled 'N8', to '5G AN' via a vertical line labeled 'N2', and to 'UE' via a vertical line labeled 'NR-uu'. + +Architecture Assumption diagram showing connections between SCEF+NEF, HSS+UDM, MME, GMLC, AMF, E-UTRAN, 5G AN, and various clients. + +Figure 6.31.3-1: Architecture Assumption + +## 6.31.4 Procedures + +### 6.31.4.1 Location Service Continuity from 5GS to EPS + +![Sequence diagram illustrating Location Service Continuity from 5GS to EPS. The diagram shows interactions between UE, NG-RAN, E-UTRAN, MME, AMF, LMF, E-SMLC, GMLC, and LCS client. It is divided into several steps: 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure (steps 1-15); 2. Handover Required (step 7); 3. 5GS to EPS handover (steps 2-10); 4. MobilityFromNRCommand (steps 11-12); 5. Handover Complete (step 13); 6. 5GS to EPS handover (steps 12-21); 7. UE-initiated LCS MO-LR Invoke (steps 15-16); 8. Deferred EPC-MT-LR procedure (steps 15-24).](5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg) + +The sequence diagram illustrates the interaction for Location Service Continuity from 5GS to EPS. The participants are UE, NG-RAN, E-UTRAN, MME, AMF, LMF, E-SMLC, GMLC, and LCS client. The process is divided into several phases: + +- 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure as defined in clause 6.3.1 of TS 23.273, step 1-15.** + - The AMF sends a message to the LMF (step 2). + - The LMF sends an **LCS Periodic-Triggered Invoke Request** to the UE (step 3). + - The UE sends an **LCS Periodic-Triggered Invoke Return Result** to the AMF (step 4). + - The AMF sends an **Nlmf\_Location\_DetermineLocation Response** to the LMF (step 5). +- 6. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure as defined in clause 6.3.1 of TS 23.273, step 19-30.** + - The AMF sends a **Handover Required** message to the MME (step 7). + - The AMF sends a message to the GMLC (step 8). + - The AMF sends an **Namf\_LocationEventNotify** message to the MME (step 9). + - The MME sends a message to the GMLC (step 10). +- 10. 5GS to EPS handover as defined in clause 4.11.1.2.1 of TS 23.502, step 2-10.** + - The AMF sends a **MobilityFromNRCommand** (targetRAT=eutran; RRCReconfig) to the UE (step 11). + - The UE sends a **MobilityFromNRCommand** (targetRAT=eutran; RRCReconfig) to the NG-RAN (step 12). + - The NG-RAN sends a **Handover Complete** message to the UE (step 13). +- 14. 5GS to EPS handover as defined in clause 4.11.1.2.1 of TS 23.502, step 12-21.** + - If the UE finds event is triggered and if the UE find move to EPS, the UE sends **LCS MO-LR Invoke** message, carry the location QoS applicable to EPS (step 15). + - The UE sends an **LCS MO-LR Invoke** message to the AMF (step 16). +- 17. Deferred EPC-MT-LR procedure for Periodic and Triggered Location procedure as defined in clause 9.1.19 of TS 23.271, step 15-24.** + +Sequence diagram illustrating Location Service Continuity from 5GS to EPS. The diagram shows interactions between UE, NG-RAN, E-UTRAN, MME, AMF, LMF, E-SMLC, GMLC, and LCS client. It is divided into several steps: 1. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure (steps 1-15); 2. Handover Required (step 7); 3. 5GS to EPS handover (steps 2-10); 4. MobilityFromNRCommand (steps 11-12); 5. Handover Complete (step 13); 6. 5GS to EPS handover (steps 12-21); 7. UE-initiated LCS MO-LR Invoke (steps 15-16); 8. Deferred EPC-MT-LR procedure (steps 15-24). + +**Figure 6.31.4.1-1: Location Service Continuity from 5GS to EPS** + +- Steps 1-15 defined in clause 6.3.1 of TS 23.273 [5] with the following additions: after receive **Namf\_Location\_ProvidePositioningInfo Request**, if AMF determine the access type supported by UE for event reporting includes "EUTRAN" and if the required LCS QoS class in location QoS is "multiple QoS class", the AMF determines its corresponding location QoS can be applicable to EPS, i.e. determine two set of location QoS, one used for 5GS and its corresponding used for EPS (i.e. the location QoS applicable to EPS). If AMF determines the 5GS corresponding location QoS applicable to EPS, AMF notifies that information to LMF via **Nlmf\_Location\_DetermineLocation Request** message. Otherwise, if AMF does not do that processing, the LMF could perform that processing as described in step 2. +- After receive **Nlmf\_Location\_DetermineLocation Request**, if LMF determines the access type supported by UE for event reporting includes "EUTRAN" , e.g. the reporting type includes "EUTRAN" and if the required LCS QoS class in location QoS is "multiple QoS class", the LMF determines its corresponding location QoS can be applicable to EPS, i.e. determine two set of location QoS, one used for 5GS and its corresponding used for EPS (i.e. the location QoS applicable to EPS). For example, choose the most stringent values from the "LocationQoS" and set the "LcsQoSClass" in "LocationQoS" as the "Best Effort" (since the "LCS QoS class" is defined as an enumerate data type and MME only understand the enumerated value {"assured" and "best effort"}, it does not understand the enumerated value "multiple qos"). + +NOTE 1: Either AMF or LMF could determine the location QoS applicable to EPS if the UE reporting type includes "EUTRAN" and if the required "LCS QoS class" is "multiple QoS class". + +- 3-4. LMF sends the LCS Periodical-Triggered Invoke Request, includes the location QoS used for 5GS and the its corresponding location QoS used for EPS. UE response to LMF with the LCS Periodical-Triggered Invoke Return Result +5. LMF sends the Nlmf\_Location\_DermineLocation Response to AMF, if AMF does not determine the 5GS location QoS corresponding location QoS applicable to EPS, i.e. AMF does not perform the processing as illustrated in step 1, the LMF includes the location QoS used for 5GS and the its corresponding location QoS used for EPS to AMF. After receive that information, the AMF should keep the positioning related information and do not release. +- 6~9. After AMF receives the handover required message, if AMF finds UE can support interworking between 5GS and EPS, e.g. AMF can determine whether UE can be interworking between 5GS and EPS based on whether receive the location QoS used for 5GS and the its corresponding location QoS used for EPS from LMF or based on the UE subscription information or based on whether the UE reporting type includes "EUTRAN", AMF sends the Namf\_LocationEventNotify to GMLC, includes the MME ID/address, the handover to EPS notification, location QoS used in 5GS and its corresponding location QoS applicable to EPS. Alternatively, AMF can perform step 8 and step 9 after receive Relocation response message (i.e. step 9 in clause 4.11.1.2.1 of TS 23.502 [3]) or Relocation Complete Notification message (i.e. step 12c in clause 4.11.1.2.1 of TS 23.502 [3]) from MME. + +NOTE 2: No step sequence restrict between step 9 and steps 10~14, step 9 and steps 10~14 can be performed in parallel. + +10-14: 5GS to EPS handover. + +15. If UE finds periodical event triggered and if the UE has moved to EPS, the UE sends LCS MO-LR Invoke message, carry the location QoS can be applicable to EPS. The UE can determine whether it has moved to EPS based on the message received from target access network during handover, e.g. based on the "target RAT=eutran" included in message"MobilityFromNRCommand" or can based on the RRC message type, e.g. for NR-NR handover, UE will receive the RRCReconfiguration from target NG-RAN, for EUTRAN-EUTRAN handover, UE will receive the RRConnectionreconfiguration from target EUTRAN, for NG-RAN to EUTRAN handover, UE will receive the MobilityFromNRCommand from target EUTRAN. + +NOTE 3: If UE finds handover is not complete but the event is triggered, i.e. step 16 happens before step 13, the UE need wait handover complete to send the triggered LCS MO-LR Invoke message. + +Then, as UE moving, UE may moves from EPS back to 5GS, in that case, if UE finds periodical event triggered and if the UE has moved to 5GS, the UE sends Event Report message, carry the location QoS can be applicable to 5GS. Also, the MME need notify GMLC the handover to 5GS notification. + +### 6.31.4.2 Location Service Continuity from EPS to 5GS + +![Sequence diagram illustrating Location Service Continuity from EPS to 5GS. The diagram shows interactions between UE, NG-RAN, E-UTRAN, MME, AMF, LMF, E-SMLC, GMLC, and LCS client. It is divided into three main phases: 1. Deferred EPC-MT-LR procedure (steps 1-24), 2. EPS to 5GS handover (steps 3-16), and 3. EPS to 5GS handover (steps 4-13). Key messages include Handover Required, Subscriber Location Report, Handover Command, Handover from E-UTRAN Command, Handover to 5G-RAN Confirm, Event Report, and Deferred 5GC-MT-LR.](f5698523df298c80a0c6b5d4ca657993_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant E-UTRAN + participant MME + participant AMF + participant LMF + participant E-SMLC + participant GMLC + participant LCS_client as LCS client + + Note over UE, LCS_client: 1. Deferred EPC-MT-LR procedure for Periodic and Triggered Location procedure as defined in clause 9.1.19 of TS 23.271, step 1~24. + Note right of E-UTRAN: 2. Handover Required + Note right of MME: 3. If MME finds UE has positioning related information, MME trigger to send step 3 to GMLC. + Note right of MME: 4. Subscriber Location Report([AMF ID/address], [LDR Reference number], [handover to 5GS notification]) + Note over UE, LCS_client: 5. EPS to 5GS handover as defined in clause 4.11.1.2.2 of TS 23.502, step 3~16. + Note right of MME: 6. Handover Command + Note right of E-UTRAN: 7. Handover from E-UTRAN Command + Note right of NG-RAN: 8. Handover to 5G-RAN Confirm + Note over UE, LCS_client: 9. EPS to 5GS handover as defined in clause 4.11.1.2.2.3 of TS 23.502, step 4~13. + Note left of UE: 10. If UE finds periodical event is triggered and if the UE find move to 5GS, the UE sends event report message to 5GS. + Note right of UE: 11. Event Report + Note over UE, LCS_client: 12. Deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure as defined in clause 6.3.1 of TS 23.273, step 26~30. + +``` + +Sequence diagram illustrating Location Service Continuity from EPS to 5GS. The diagram shows interactions between UE, NG-RAN, E-UTRAN, MME, AMF, LMF, E-SMLC, GMLC, and LCS client. It is divided into three main phases: 1. Deferred EPC-MT-LR procedure (steps 1-24), 2. EPS to 5GS handover (steps 3-16), and 3. EPS to 5GS handover (steps 4-13). Key messages include Handover Required, Subscriber Location Report, Handover Command, Handover from E-UTRAN Command, Handover to 5G-RAN Confirm, Event Report, and Deferred 5GC-MT-LR. + +**Figure 6.31.4.2-1: Location Service Continuity from EPS to 5GS** + +Since all the "LCS QoS class" in "location QoS" supported by EPS can also supported by 5GS, there is no need do the location QoS class mapping processing as described in clause 6.31.4.1. + +3-4. After MME receives the handover required message, if MME finds UE has positioning related information, MME trigger to send Subscriber Location Report to GMLC, includes the AMF ID/address, the LDR Reference number, the handover to 5GS notification. Alternatively, MME can perform step 3 and step 4 after receive Forward Relocation Response message (i.e. step 14 in clause 4.11.1.2.2.2 of TS 23.502 [3]) or Forward Relocation Complete Notification (i.e. step 5 in clause 4.11.1.2.2.3 of TS 23.502 [3]) message from AMF. + +10. If UE finds periodical event triggered and if the UE has moved to 5GS, the UE sends event report message to 5GS. The UE can determine whether it has moved to 5GS based on the message receive from target access network during handover, e.g. based on the RRC message type, e.g. for NR-NR handover, UE will receive the RRCReconfiguration from target NG-RAN, for EUTRAN-EUTRAN handover, UE will receive the RRConnectionreconfiguration from target EUTRAN, for NG-RAN to EUTRAN handover, UE will receive the MobilityFromNRCommand from target EUTRAN. + +NOTE 1: IF UE finds handover is not complete but the event is triggered, i.e. step 10 happens before step 8, the UE need wait handover complete to send the triggered Event Report message. + +NOTE 2: No step sequence restrict between step 4 and steps 5~9, step 4 and steps 5~9 can be performed in parallel. + +Then, as UE moving, UE may moves from 5GS back to EPS, in that case, if UE finds periodical event triggered and if the UE has moved to EPS, the UE sends the LCS MO-LR Invoke message, carry the location QoS can be applicable to EPS. Also, the AMF need notify GMLC the handover to EPS notification. + +### 6.31.5 Impacts on services, entities, and interfaces + +UE: + +- After periodic event triggered, support differentiate whether move to EPS or 5GS and determine the suitable messages and location QoS sends to 5GS/EPS. + +LMF: + +- Support aware whether UE can support the interworking between 5GS and EPS. + +- Support determine the 5GS location QoS corresponding location QoS can be applicable to EPS, and send this information to UE and AMF. + +AMF: + +- Support determine the 5GS location QoS corresponding location QoS can be applicable to EPS, and send this information to LMF. +- After receive handover required, instigate Namf\_LocationEventNotify to GMLC to notify the handover and the 5GS location QoS corresponding location QoS can be applicable to EPS if UE can support interworking between 5GS and EPS. + +MME: + +- After receive handover required, instigate the Subscriber Location Report to GMLC to notify the handover if UE can support interworking between EPS and 5GS. + +## 6.32 Solution #32: LCS continuity Support for N26 based Handover + +### 6.32.1 Introduction + +This solution addresses KI#8: support of location service continuity in case of UE mobility. + +### 6.32.2 Functional Description + +The interworking between 5GS and EPS with N26 interface is specified in clause 5.17.2.2 of TS 23.501 [2], and the handover procedure via is specified in clause 4.11.1.2 of TS 23.502 [3]. During that handover procedure, location request from LCS Client may arrive at 5GC or EPS core network entities, e.g. AMF or MME. Or after core network entities received Location Request from GMLC and before actual positioning procedure finish, the handover required message maybe received from RAN. + +Since those handover procedure is on-going, continue performing positioning procedure within the source RAN may have problems, e.g. such positioning procedure may not able be finished due to UE moved to target side; the positioning result from the source side may not be accurate due to UE mobility. In such handover and location service simultaneously on-going scenarios, forwarding arrived location request to target side and trigger actual positioning procedure at target side has benefits over simply reject the location request. The benefits including that network can provide UE location timely and accurately. + +### 6.32.3 Procedures + +#### 6.32.3.1 LCS support during Handover from 5GS to EPS + +Within below figure 6.32.3.1-1, the MT-LR location request arrives at AMF (e.g. Step 4 of clause 6.1.1 of TS 23.273 [5], Namf\_Location\_Provide Request from V-GMLC), and this would trigger the positioning procedure. When such MT-LR procedure is still on-going, the NG-RAN may decides that a Handover is required. + +![Sequence diagram showing LCS support during handover from 5GS to EPS. The diagram illustrates the interaction between UE, E-UTRAN, NG RAN, AMF, LMF, MME, E-SMLC, V-GMLC, H-GMLC, and LCS Client. It details steps A-1 through J, covering positioning requests, handover procedures, and location responses.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant E-UTRAN + participant NG RAN + participant AMF + participant LMF + participant MME + participant E-SMLC + participant V-GMLC + participant H-GMLC + participant LCS Client + + Note right of AMF: A-1 +Within procedure in 6.1.1 of TS23.273: +Step4. AMF received Namf_Location_ProvidePositioningInfo Request from V-GMLC + AMF->>LMF: + Note left of AMF: A-2 +UE base positioning Procedure in 6.11 of TS23.273: +Step1. AMF received +Namf_communication_N1N2MessageTransfer() + AMF->>LMF: + Note left of AMF: B +Within procedure in 4.11.1.2.1 of TS23.502: +Step 1. Handover Required + AMF->>NG RAN: + Note right of AMF: C-1 +Within procedure in 6.1.1 of TS23.273: +Step10. AMF return Namf_Location_ProvidePositioningInfo +Response to V-GMLC + AMF->>V-GMLC: + Note right of AMF: C-2 +Within in 6.11 of TS23.273 +Step7. AMF response LMF with +Namf_communication_N1N2MessageNotify() + AMF->>LMF: + Note right of AMF: D +Forwarding Location/Positioning Request +Within procedure in 4.11.1.2.1 of TS23.502: +Step 3. Relocation Required + AMF->>MME: + Note right of MME: E-1 +Within procedure in 9.1.15 of TS23.271: +Step 6. MME send Location +Request to E-SMLC + MME->>E-SMLC: + Note left of AMF: F-1 +Within procedure in 9.1.15 of TS23.271: +Step 7. E-SMLC perform Positioning procedure + E-SMLC->>MME: + Note right of MME: G-1 +Within procedure in 9.1.15 of TS23.271: +Step 8. MME received Location +Reponse from E-SMLC + MME->>E-SMLC: + Note left of AMF: H: Forwarding Location Result +Define New Message or Re-USE context +Req/Response procedure + AMF->>LMF: + Note right of AMF: J +Within procedure in 6.1.1 of TS23.273: +Step 10. AMF response Namf_Location_ProvideLocation Response to V-GMLC + AMF->>V-GMLC: + +``` + +Sequence diagram showing LCS support during handover from 5GS to EPS. The diagram illustrates the interaction between UE, E-UTRAN, NG RAN, AMF, LMF, MME, E-SMLC, V-GMLC, H-GMLC, and LCS Client. It details steps A-1 through J, covering positioning requests, handover procedures, and location responses. + +**Figure 6.32.3.1-1: LCS support during handover from 5GS to EPS** + +Step A-1: During the 5GC-MT-LR procedure, e.g. in clause 6.1.1 of TS 23.273 [5], step 4, the AMF received Namf\_Location\_ProvidePositioningInfo request from V-GMLC, which includes the SUPI, and client type and may include the required QoS parameters. The LMF is then contacted to perform one or more of the positioning procedures described in clause 6.11.1 and 6.11.2 of TS 23.273 [5]. + +Step A-2. Take the clause 6.1.1 of TS 23.273 [5] as an example, the step 1 of this procedure is triggered. The LMF invokes the Namf\_Communication\_N1N2MessageTransfer service operation towards the AMF. + +Step B: Before the complete of procedure triggered in Step A-2, or before Step A-2 but after Step A-1, the NG-RAN may decide to initiate the Handover. The AMF receives the Handover Required from NG-RAN as defined in clause 4.11.1.2.1 of TS 23.502 [3], step 1. + +Step C-1: Replace the step 10 in 6.1.1 of TS 23.273 [5], the AMF returns the Namf\_Location\_ProvidePositioningInfo Response towards the V-GMLC, to indicate that there is a Handover. + +Step C-2: The AMF invokes the Namf\_Communication\_N1MessageNotify service operation towards the LMF, to indicate that there is a Handover, and the abort of positioning procedure. + +Step D: The AMF needs to indicate the MME to preform Location Procedure in EPS and return the result, via N26 interface. The AMF may map the Namf\_Location\_ProvidePositioningInfo request message received to the message Provide Subscriber Location message, and send this message to MME by piggybacking in the Relocation Required, which is step 3 of procedure in 4.11.1.2.1 of TS 23.502 [3]. The MME assumes such Provide Subscriber Location is come from a GMLC, and triggers the Step F-1. At the same time, the handover procedure continues, as defined in 4.11.1.2.1 of TS 23.502 [3]. + +Step E-1: The MME send Location request to E-SMLC, as defined in clause 9.1.15 of TS 23.271 [4]. + +Step F-1: The E-SMLC performs the step 7 of clause 9.1.15 of TS 23.271 [4]. + +Step G-1: The E-SMLC performs the step 8 of clause 9.1.15 of TS 23.271 [4]. In this step, the MME receives the Location Response message from E-SMLC. That means the positioning result is from the target side. + +Step H: The positioning result is return to AMF via N26 interface. The context request/response pair message could to re-use with some modification, or defines new messages for this purpose. + +Step J: Like the step 10 in clause 6.1.1 of TS 23.273 [5], the AMF returns the Namf\_Location\_ProvideLocation Response towards the V-GMLC, to return the UE location to V-GMLC. + +### 6.32.3.2 LCS support during Handover from EPS to 5GS + +Within below figure 6.22.3.2-1, the MT-LR location request (e.g. Provide Subscriber Location Request sent by VGMLC in step 2 of clause 9.1.15 of TS 23.271 [4]) arrives at MME, and this would trigger the positioning procedure. When such MT-LR procedure is still on-going, the NG-RAN decides that a Handover is required. + +![Sequence diagram illustrating LCS support during handover from EPS to 5GS. The diagram shows interactions between UE, E-UTRAN, NG RAN, AMF, LMF, MME, E-SMLC, V-GMLC, H-GMLC, and LCS Client. The sequence is divided into several steps: A (MME receives Provide Subscriber Location from V-GMLC), B (Handover Required), C (MME sends Location Abort to E-SMLC and Subscriber Location Report to V-GMLC), D (Forwarding Location Request), E (AMF sends Nlmf_Location_DetermineLocation_Request), F-1 (UE base positioning Procedure), F-2 (LMF sent Nlmf_Location_DetermineLocation_Response), G (Forwarding Location Result), and H (MME sends Subscriber Location Report to V-GMLC).](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +``` + +sequenceDiagram + participant UE + participant E-UTRAN + participant NG RAN + participant AMF + participant LMF + participant MME + participant E-SMLC + participant V-GMLC + participant H-GMLC + participant LCS Client + + Note right of AMF: A +Within procedure in 9.1.15 of TS23.271: +Step 2. MME received Provide Subscriber Location from V-GMLC + V-GMLC->>MME: Step 6. Location Request + Note left of MME: B +Within procedure in 4.11.1.2.2.2 of TS23.502: +Step 2. Handover Required + MME->>E-UTRAN: + Note right of MME: C +Step C-1. MME send Location Abort to E-SMLC + MME->>E-SMLC: + Note right of MME: Step C-2. MME send Subscriber Location Report to V-GMLC + MME->>V-GMLC: + Note right of AMF: D. Forwarding Location Request +Within procedure in 4.11.1.2.2.2 of TS23.502: +Step 3. Forward Relocation Request + AMF->>MME: + Note right of AMF: E +Within 6.1.1 of TS23.273: +Step 6. AMF send +Nlmf_Location_DetermineLocation_Request + AMF->>LMF: + Note left of AMF: F-1 +UE base positioning Procedure in 6.11.1 of TS23.273: +Step1. AMF received +Namf_communication_N1N2MessageTransfer() + AMF->>MME: + Note right of AMF: F-2 +Within 6.1.1 of TS23.273: +Step 8. LMF sent +Nlmf_Location_DetermineLocation_Response + LMF->>AMF: + Note right of AMF: G: Forwarding Location Result +Define New Message or Re-USE context +Req/Response procedure + AMF->>MME: + Note right of AMF: H +Within procedure in 9.1.15 of TS23.271: +Step 9a. MME send Subscriber Location Report to V-GMLC + MME->>V-GMLC: + +``` + +Sequence diagram illustrating LCS support during handover from EPS to 5GS. The diagram shows interactions between UE, E-UTRAN, NG RAN, AMF, LMF, MME, E-SMLC, V-GMLC, H-GMLC, and LCS Client. The sequence is divided into several steps: A (MME receives Provide Subscriber Location from V-GMLC), B (Handover Required), C (MME sends Location Abort to E-SMLC and Subscriber Location Report to V-GMLC), D (Forwarding Location Request), E (AMF sends Nlmf\_Location\_DetermineLocation\_Request), F-1 (UE base positioning Procedure), F-2 (LMF sent Nlmf\_Location\_DetermineLocation\_Response), G (Forwarding Location Result), and H (MME sends Subscriber Location Report to V-GMLC). + +**Figure 6.32.3.2-1: LCS support during handover from EPS to 5GS** + +Step A: During the EPS-MT-LR procedure, e.g. procedure in 9.1.15 of TS 23.271 [4], step 2, GMLC sends a Provide Subscriber Location message to the MME. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber's IMSI, LCS QoS information (e.g. accuracy, response time) and an indication of whether the LCS client has the override capability. The procedure may continue and step 6 of 9.1.15 of TS 23.271 [4] happens. + +Step B: Before the complete of procedure triggered in Step A, the E-UTRAN may decide to initiate the Handover. The MME receives the Handover Required from NG-RAN as defined in clause 4.11.1.2.2.2 of TS 23.502 [3], step 2. + +Step C-1: In such case, since the Handover is going to happen, continuing positioning at EPS side become useless, so the MME may send Location Abort to E-SMLC. + +Step C-2: The MME may also send Subscriber Location Report to V-GMLC, to indicate that there is a Handover imminent. + +Step D: The MME needs to indicate the AMF to perform Location Procedure in 5GS and return the result, via N26 interface. The MME sends the Provide Subscriber Location message to AMF, by piggybacking it in the Forward Relocation Request message, which is step 3 of procedure in 4.11.1.2.2.2 of TS 23.502 [3]. + +After receiving this message, the AMF needs to map the Provide Subscriber Location message to Namf\_Location\_ProvideLocation request message, and the MME assumes such Namf\_Location\_ProvideLocation is coming from a V-GMLC, and triggers the Step E. At the same time, the handover procedure continues, as defined in 4.11.1.2.2 of TS 23.502 [3]. + +Step E: As step 6 in clause 6.1.1 of TS 23.273 [5], the AMF selects an LMF based on NRF query or configuration in AMF and invokes the Nlmf\_Location\_DetermineLocation service operation towards the LMF to request the current location of the UE. + +Step F-1: As step 8 in clause 6.1.1 of TS 23.273 [5], the LMF performs one or more of the positioning procedures described in clause 6.11.1, 6.11.2 of TS 23.273 [5]. This step F-1 shows that clause 6.1.1 as an example. + +Step F-2: As step 9 in clause 6.1.1 of TS 23.273 [5], the LMF returns the Nlmf\_Location\_DetermineLocation Response towards the AMF to return the current location of the UE. + +Step G: The positioning result is returned to MME via N26 interface. The context request/response pair message could be re-used with some modification, or defines new messages for this purpose. + +Step H: Like the step 9a in 9.1.15 of TS 23.271 [4], the MME sends a Subscriber Location Report to the V-GMLC. + +## 6.32.4 Impacts on services, entities, and interfaces + +Impacted entities: + +- AMF: forward LCS related message to MME, and receive such message from MME, to trigger positioning procedure; to forward positioning result to MME; mapping the Provide Subscriber Location message to and from the Namf\_Location\_ProvideLocation request message. +- MME: forward LCS related message to AMF, and receive such message from AMF, to trigger positioning procedure; to forward positioning result to AMF. + +Impacted interfaces: + +- N26, forwarding LCS related messages between AMF and MME. + +## 6.33 Solution #33: Support of LCS mobility when UE moves between 5GS and EPS + +### 6.33.1 Introduction + +This solution addresses the KI "Key Issue #8: support of location service continuity in case of UE mobility". + +Continuity of certain basic services like a PDU session during mobility is defined currently. However, the handling of an LCS session during mobility procedures is not specified. In particular, there is no specification on whether an ongoing LCS session shall be terminated or continued with after the mobility and if continued, how the continuity shall work. There can be many effects due to this missing part: + +- LCS sessions may be terminated at mobility with the LCS Client having to re-initiate the session after the procedure. +- The LMF may not be aware of the mobility at all, leading to inaccurate positioning estimates. +- Since there are no clear specifications, inter-vendor tests could fail. +- LCS sessions could be enabled as part of other critical services (like emergency calls) - those services could be impacted due to the current specifications - leading to regulatory issues. + +All of the above issues could be prevented if there is a clear specification on how LCS sessions are to be handled in different mobility procedures and in particular, if continuity can be guaranteed by the network. + +The main considerations in the solution are: + +- Keep the changes minimal in EPC so that legacy functionality requires only a small incremental change +- Not needing a standardized interface between the EPC-GMLC and 5GC-GMLC. According to clause 4.2a of TS 23.273 [5], this interface, denoted as Lr' is not standardized and in case EPC-GMLC and 5GC-GMLC are co-located, Lr' is not needed altogether. This solution doesn't require the standardization of this interface. +- provide a common procedure for all types of Location Request (MO-LR/MT-LR with/without deferred location). +- provide a simple solution that works regardless of the current status of the on-going location procedure when the mobility event occurs. + +## 6.33.2 Functional Description + +This proposal provides solutions for mobility between 5GS and EPS. + +## 6.33.3 Procedure + +![Sequence diagram titled '5GS->EPS HO - LCS Continuity' showing the interaction between various network elements during a handover. The elements are UE, E_UTRAN, NG_RAN, MME, AMF, E_SMLC, LMF, EPC_GMLC, 5GC_GMLC, and LCS_Client. The diagram is divided into three main phases: 4. LCS Session on 5GS, 16 LCS Session Cancelled, and 22. LCS Session over EPC. The sequence starts with a Proprietary Lr' message from 5GC_GMLC to EPC_GMLC, followed by an LCS Service Request from LCS_Client to 5GC_GMLC. The AMF initiates the handover (5.HO Initiation) to the NG_RAN, which then sends a Relocation Request to the MME. The MME performs MME Selection and sends a Relocation Response to the AMF. The AMF sends an HO Command to the NG_RAN, which sends an HO Complete to the UE. The UE sends an HO Notify to the MME. The AMF sends a Nlmf_Location_CancelLocation Request to the LMF. The LMF sends a Nlmf_Location_ProvidePositioningInfo Resp to the 5GC_GMLC. The 5GC_GMLC sends a Location Transfer Request to the EPC_GMLC. The EPC_GMLC sends a Provide Subscriber Location to the AMF. The AMF performs E_SMLC Selection and sends a Location Request to the E_SMLC. The E_SMLC sends a Location Response to the AMF. The AMF sends a Subscriber Location Report to the EPC_GMLC. The EPC_GMLC sends a Subscriber Location Report to the 5GC_GMLC. The 5GC_GMLC sends an LCS Service Response to the LCS_Client.](7c4726a694799239785f7869a6947472_img.jpg) + +**5GS->EPS HO - LCS Continuity** + +``` + +sequenceDiagram + participant UE + participant E_UTRAN + participant NG_RAN + participant MME + participant AMF + participant E_SMLC + participant LMF + participant EPC_GMLC + participant 5GC_GMLC + participant LCS_Client + + Note right of 5GC_GMLC: Proprietary Lr' + LCS_Client->>5GC_GMLC: 1. LCS Service Request (UE ID, LCS QoS) + 5GC_GMLC->>AMF: 2. Nlmf_Location_ProvidePositioningInfo Req (UE ID, LCS QoS) + AMF->>LMF: 3. Nlmf_Location_DetermineLocation (UE ID, LCS Correlation ID, LCS QoS) + Note over NG_RAN, MME: 4. LCS Session on 5GS + NG_RAN->>AMF: 5.HO Initiation + AMF->>NG_RAN: 6.HO_Required + Note over MME: MME Selection + AMF->>MME: 7. Relocation_Request + MME->>NG_RAN: 8.HO_Request + NG_RAN->>MME: 9.HO_Request_Ack + MME->>AMF: 10. Relocation_Response + AMF->>NG_RAN: 11. HO_Command + NG_RAN->>UE: 12 HO_Command + UE->>NG_RAN: 13 HO_Complete + NG_RAN->>MME: 14 HO_Notify + AMF->>LMF: 15 Nlmf_Location_CancelLocation Request + Note over NG_RAN, MME: 16 LCS Session Cancelled + LMF->>5GC_GMLC: 17 Nlmf_Location_ProvidePositioningInfo Resp (UE ID, LCS Session Failure, HO to EPC, Target MME ID) + 5GC_GMLC->>EPC_GMLC: 18 Location Transfer Request (UE ID, LCS QoS, Target MME ID) + EPC_GMLC->>AMF: 19 Provide Subscriber Location (UE ID, LCS QoS) + Note over MME: 20 E_SMLC Selection + AMF->>E_SMLC: 21. Location Request (UE ID, LCS QoS) + Note over NG_RAN, MME: 22. LCS Session over EPC + E_SMLC->>AMF: 23. Location Response (UE ID, UE Location Estimate) + AMF->>EPC_GMLC: 24. Subscriber Location Report (UE ID, UE Location Estimate) + EPC_GMLC->>5GC_GMLC: 25. Subscriber Location Report (UE ID, UE Location Estimate) + 5GC_GMLC->>LCS_Client: 26. LCS Service Response (UE ID, UE Location Estimate) + +``` + +Sequence diagram titled '5GS->EPS HO - LCS Continuity' showing the interaction between various network elements during a handover. The elements are UE, E\_UTRAN, NG\_RAN, MME, AMF, E\_SMLC, LMF, EPC\_GMLC, 5GC\_GMLC, and LCS\_Client. The diagram is divided into three main phases: 4. LCS Session on 5GS, 16 LCS Session Cancelled, and 22. LCS Session over EPC. The sequence starts with a Proprietary Lr' message from 5GC\_GMLC to EPC\_GMLC, followed by an LCS Service Request from LCS\_Client to 5GC\_GMLC. The AMF initiates the handover (5.HO Initiation) to the NG\_RAN, which then sends a Relocation Request to the MME. The MME performs MME Selection and sends a Relocation Response to the AMF. The AMF sends an HO Command to the NG\_RAN, which sends an HO Complete to the UE. The UE sends an HO Notify to the MME. The AMF sends a Nlmf\_Location\_CancelLocation Request to the LMF. The LMF sends a Nlmf\_Location\_ProvidePositioningInfo Resp to the 5GC\_GMLC. The 5GC\_GMLC sends a Location Transfer Request to the EPC\_GMLC. The EPC\_GMLC sends a Provide Subscriber Location to the AMF. The AMF performs E\_SMLC Selection and sends a Location Request to the E\_SMLC. The E\_SMLC sends a Location Response to the AMF. The AMF sends a Subscriber Location Report to the EPC\_GMLC. The EPC\_GMLC sends a Subscriber Location Report to the 5GC\_GMLC. The 5GC\_GMLC sends an LCS Service Response to the LCS\_Client. + +**Figure 6.33.3-1 : LCS Continuity Solution for 5GS to EPS Mobility** + +Description: + +Steps 1-4 describe the normal MT-LR LCS session on 5GS (similar to steps 1.a. to 12 in Figure 6.1.2-1 in TS 23.273 [5]). + +Steps 5-14 describe the normal 5GS to EPS HO procedure (similar to steps 1 to 12.b in Figure 4.11.1.2.1-1 in TS 23.502 [3]). + +The AMF could initiate steps 15 and 17 in parallel to step 11 when it receives the Relocation Response (step 10). + +NOTE 1: Steps 15/16 is meant to be completed before the UE is handed over to LTE. If it is determined to be too close to the HO procedure, then the normative phase could choose to trigger step 15 in parallel with step 7. + +Steps 15-16: The LCS Session on 5GS is cancelled. + +Step 17: The AMF indicates failure to the 5GC-GMLC with reason "HO to EPC" and including the target MME ID. + +Step 18: The 5GC-GMLC forwards the location request to the EPC-GMLC including all the parameters of the LCS Request and the target MME ID. + +Steps 19-24: The LCS Session is started on EPS (similar to steps 1-10 in Figure 9.18 in TS 23.271 [4]). + +Steps 25-26: The UE location estimate is returned by the EPC-GMLC to the 5GC-GMLC which then forwards the same to the LCS Client. + +NOTE 2: As can be observed, the entire procedure is done in a way where the LCS Client is not aware of the mobility handling and the LCS session continuity is ensured. + +NOTE 3: There could be a mapping of LCS QoS (from the values defined for 5GS to values defined in 4GS) - this could be done by the GMLC. + +- For QoS attributes that are common between 5GS and EPS, the original LCS QoS defined values can be used as is in EPS. +- For QoS attributes that are specific to 5GS -> the QoS mapping could be done to the most stringent QoS value with best effort handling in QoS Class. If an LCS session was active over user plane in 5GS when the HO is triggered, the AMF/LMF share assistance data to the UE that minimizes the TLS handshake workload according to clause 6.1.1.4 of OMA-TS-ULP-V2\_0\_6 [14] specification, once the UE moves to EPS. + +![Sequence diagram for EPS->5GS HO - LCS Continuity. The diagram shows the interaction between UE, E_UTRAN, NG_RAN, AMF, E_SMLC, LMF, NRF, MME, 5GC_GMLC, EPC_GMLC, and LCS_Client. It details the steps for maintaining LCS continuity during an EPS to 5GS handover, including location requests, HO initiation, session cancellation on EPS, and session establishment on 5GS.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +**EPS->5GS HO - LCS Continuity** + +``` + +sequenceDiagram + participant UE + participant E_UTRAN + participant NG_RAN + participant AMF + participant E_SMLC + participant LMF + participant NRF + participant MME + participant 5GC_GMLC + participant EPC_GMLC + participant LCS_Client + + Note right of EPC_GMLC: Proprietary Lr + LCS_Client->>EPC_GMLC: 1. Location Request (UE ID, LCS QoS) + EPC_GMLC->>5GC_GMLC: 2. Provide Subscriber Location (UE ID, LCS QoS) + 5GC_GMLC->>MME: 3. Location Request (UE ID, LCS QoS) + Note left of E_SMLC: 4. LCS Session on LTE/EPC + E_UTRAN->>NG_RAN: 5. HO Initiation + NG_RAN->>AMF: 6. HO_Required + Note right of MME: AMF Selection + AMF->>MME: 7. Forward_Relocation_Required + MME->>AMF: 8. HO_Request + AMF->>NG_RAN: 9. HO_Request_Ack + MME->>AMF: 10. Forward_Relocation_Response + AMF->>MME: 11. HO_Command + MME->>E_UTRAN: 12. HO_From_EUTRAN_Command + E_UTRAN->>NG_RAN: 13. HO_To_5G_RAN_Confirm + NG_RAN->>AMF: 14. NGAP : HO_Notify + MME->>E_SMLC: 15. Location Cancel + Note left of E_SMLC: 16. LCS Session Cancelled + MME->>EPC_GMLC: 17. Location Response (Failure, UE ID, Event : HO to 5GC, AMF Address) + EPC_GMLC->>5GC_GMLC: 18. Location Transfer Request (UE ID, LCS QoS, Target AMF ID) + 5GC_GMLC->>LMF: 19. Request AMF Service URI (AMF address) + LMF->>5GC_GMLC: 20. AMF service URI for Namf_Location service + 5GC_GMLC->>AMF: 21. Namf_Location_ProvidePositioningInfo Req (UE ID, LCS QoS) + Note left of AMF: 22. LMF Selection + AMF->>LMF: 23. Nlmf_Location_DetermineLocation Request (UE ID, LCS Correlation ID, LCS QoS) + Note left of E_SMLC: 24. LCS Session on 5GC/NG_RAN + LMF->>AMF: 25. Nlmf_Location_DetermineLocation Response (UE ID, LCS Correlation ID, LCS Estimate) + AMF->>5GC_GMLC: 26. Namf_Location_ProvidePositioningInfo Resp (UE ID, Location Estimate) + 5GC_GMLC->>EPC_GMLC: 27. Location Response (UE ID, Location Estimate) + EPC_GMLC->>LCS_Client: 28. Location Response (UE ID, Location Estimate) + +``` + +Sequence diagram for EPS->5GS HO - LCS Continuity. The diagram shows the interaction between UE, E\_UTRAN, NG\_RAN, AMF, E\_SMLC, LMF, NRF, MME, 5GC\_GMLC, EPC\_GMLC, and LCS\_Client. It details the steps for maintaining LCS continuity during an EPS to 5GS handover, including location requests, HO initiation, session cancellation on EPS, and session establishment on 5GS. + +**Figure 6.33.3-2: LCS Continuity Solution for EPS to 5GS Mobility** + +**Description:** + +Steps 1-4 describe the normal MT-LR LCS session on EPS (similar to steps 1 to 3 in Figure 6.1.2-1 in TS 23.271 [4]). + +Steps 5-14 describe the normal EPS to 5GS HO procedure (similar to steps 1 to 16 in Figure 4.11.1.2.2.2-1 and steps 1-4 in Figure 4.11.1.2.2.3-1 in TS 23.502 [3]). + +The MME could initiate steps 15 and 17 in parallel to step 11 when it receives the Forward Relocation Response (step 10). + +Steps 15-16: The LCS Session on EPS is cancelled. + +Step 17: The MME indicates failure to the EPC-GMLC with reason "HO to EPC" and including the target AMF ID. + +Step 18: The EPC-GMLC forwards the location request to the 5GC-GMLC including all the parameters of the LCS Request and the target AMF ID. + +Steps 19-24: The LCS Session is started on 5GS (similar to steps 1-23 in Figure 6.1.2-1 in TS 23.273 [5]). + +Steps 25-26: The UE location estimate is returned by the 5GC-GMLC to the EPC-GMLC which then forwards the same to the LCS Client. + +NOTE 1: As can be observed, both the procedures are defined in a way to keep the LCS Client unaware of the mobility signalling and the LCS session continuity is ensured. + +NOTE 2: There could be a mapping of LCS QoS (from the values defined for 5GS to values defined in 4GS or vice versa) - this could be done by the GMLC. + +- For QoS attributes that are common between 5GS and EPS, the original LCS QoS defined values can be used as is in 5GS. +- For QoS attributes that are specific to EPS -> the QoS mapping could be done to the most stringent QoS value with best effort handling in QoS Class. +- If the LMF is configured to use LCS over user plane in 5GS, then LMF will choose to initiate the LCS session over user plane at step 24. + +### 6.33.4 Impacts on services, entities, and interfaces + +**Table 6.33.4-1: Impacts on services, entities and interfaces** + +| | GMLC | AMF | MME | LMF/eSMLC/
RAN/UE | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|----------------------| +| 5GS -> EPS Mobility | Transfer of LCS context from 5GS to EPS
Mapping of LCS QoS from 5GS to EPS
Initiating LCS session on EPS on target MME given by AMF | Provide the target MME ID to GMLC as part of Namf_Location_Response
Trigger the sending of LCS UP server assistance data to the UE as part of the HO procedure | | None | +| EPS -> 5GS Mobility | Transfer of LCS context from EPS to 5GS
Mapping of LCS QoS from EPS to 5GS | | Provide the target AMF ID to GMLC as part of Location_Response | None | + +## 6.34 Solution #34: UE location determination for Mobility Restriction enforcement + +### 6.34.1 Introduction + +Using UE-generated location information (e.g. GNSS/A-GNSS) to determine the TAI where the UE is geographically located can be accurate but may be unreliable as has been evaluated by SA WG3. + +To perform precise Mobility Restriction enforcement, this solution propose to use NI-LR procedure to determine the TAI where the UE is geographically located, when NG-RAN reports multiple TAIs to AMF and any but not all of them are Forbidden Area or Non-allowed area. + +### 6.34.2 Functional Description + +This solution proposes to utilize NI-LR procedure to determine the TAI where the UE (with satellite access) is geographically located, NG-RAN reports multiple TAIs to AMF (not indicating the TAI in which the UE is located) and any but not all of the reported TAIs are Forbidden Area or Non-allowed area. + +### 6.34.3 Procedure + +![Sequence diagram for NI-LR based UE location determination for Mobility Restriction enforcement. The diagram shows interactions between UE, RAN, AMF, UDM, and LMF. Step 1: RAN sends User Location Information (Multiple TAIs) to AMF. Step 2: AMF determines to initiate NI-LR if any but not all of TAIs of received is Forbidden or not allowed. Step 3: AMF sends NLmf_location_DetermineLocation Request (UE TAI determination indication) to LMF. Step 4: UE positioning (a horizontal bar spanning all lifelines). Step 5: LMF sends NLmf_location_DetermineLocation Response (UE location) to AMF. Step 6: Mobility Restriction enforcement (a horizontal bar spanning RAN, AMF, and UDM lifelines).](8942c590307508b28df9c207bad75740_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM + participant LMF + + Note right of AMF: 2. AMF determines to initiate NI-LR if any but not all of TAIs of received is Forbidden or not allowed + + RAN->>AMF: 1. User Location Information (Multiple TAIs) + AMF->>LMF: 3.NLmf_location_DetermineLocation Request (UE TAI determination indication) + Note over UE,RAN,AMF,UDM,LMF: 4. UE positioning + LMF->>AMF: 5.NLmf_location_DetermineLocation Response (UE location) + Note over RAN,AMF,UDM: 6. Mobility Restriction enforcement + +``` + +Sequence diagram for NI-LR based UE location determination for Mobility Restriction enforcement. The diagram shows interactions between UE, RAN, AMF, UDM, and LMF. Step 1: RAN sends User Location Information (Multiple TAIs) to AMF. Step 2: AMF determines to initiate NI-LR if any but not all of TAIs of received is Forbidden or not allowed. Step 3: AMF sends NLmf\_location\_DetermineLocation Request (UE TAI determination indication) to LMF. Step 4: UE positioning (a horizontal bar spanning all lifelines). Step 5: LMF sends NLmf\_location\_DetermineLocation Response (UE location) to AMF. Step 6: Mobility Restriction enforcement (a horizontal bar spanning RAN, AMF, and UDM lifelines). + +**Figure 6.34.2-1: NI-LR based UE location determination for Mobility Restriction enforcement** + +1. AMF receives a NGAP message containing User Location Information for a UE using NR satellite access during a Mobility Management or Session Management procedure. The ULI information contains multiple TAIs. + +NOTE 1: In step 1, NG-RAN does not indicate the TAI in which the UE is located as part of the ULI. + +2. AMF determines to initiate NI-LR procedure if any but not all of the received TAIs in step 1 is Forbidden or Not-Allowed. + +3. AMF sends Nlmf\_location\_DetermineLocation request to LMF including a UE TAI determination indication. + +4. Based on the indication of step 3, LMF may do not select UE standalone or UE-based positioning mode for UE positioning, or also may restrict the usage of UE-assisted method, which can ensure that network verification of UE location is performed with a reliable method. + +NOTE 2: The positioning method mode selection needs coordination with RAN TSG WG and depends on RAN supported methods. + +5. LMF sends the UE location estimate to AMF via Nlmf\_location\_DetermineLocation response. + +6. AMF maps the UE location into TAI and performs mobility restriction based on clause 5.3.4.1 of TS 23.501 [2]. + +NOTE 3: AMF is configured with TAI geographic information. + +### 6.34.4 Impacts on services, entities, and interfaces + +AMF: + +- Triggers NI-LR procedure when NG-RAN reports multiple TAIs (not indicating the TAI in which the UE is located) and any but not all of the reported TAIs are Forbidden Area or Non-allowed area) and any but not all of them are Forbidden Area or Non-allowed area. +- Indicates to LMF in the NI-LR request that the request is for UE TAI determination. + +- AMF is configured with TAI geographic information. + +LMF: + +- May select a reliable positioning method supported by RAN based on the UE TAI determination indication. +- RAN:NTN-based NG-RAN needs to support reliable positioning methods. + +## 6.35 Solution #35: Support reporting the UE location only when the UE locates the target area defined with the finer granularity + +### 6.35.1 Introduction + +This solution addresses KI#4: Interaction between Location Service and NWDAF, and KI#11: Enhance the Triggered Location for UE power saving purposes. + +With the requirements from the NWDAF or some power saving requirements, the LCS architecture is required to report the UE location only when the UE locates in the exact target area to accomplish the power-saving purpose or signalling reduction purpose. + +This solution addresses the following two points on the LCS side: + +- 1) delivers the detailed target area information from LCS service demander including NWDAF to the UE; +- 2) enables the UE to trigger the area event reporting only when the UE locates in the exact target area or enables the LMF to judge whether the UE location is in the target area or not, which is defined with the finer granularity. + +### 6.35.2 Functional Description + +This solution proposes that the LCS architecture delivers the detail of the target geographical area to the UE including the shape of the target area, the coordinates of latitude and longitude, area accuracy and other information. The area accuracy is used to allow the LCS architecture to report the UE location within the tolerant granularity. Besides, two approaches (i.e. decided by UE and decided by NF) are proposed to address how to report the UE location only when the UE locates the target area defined with the finer granularity: + +- **Approach A: Decided by UE.** The UE knows the exact target area with finer granularity and triggers area event reporting when the UE can calculate its location (e.g. RAT-independent positioning) and the UE locates in the exact target area; +- **Approach B: Decided by NF.** The NF (e.g. LMF) determines whether the UE location is in the exact target area or not when the UE can not calculate its exact location (e.g. UL positioning) or the NF (e.g. LMF) receives the request from the UE side to help to make a judgment. Then the NF (e.g. LMF) makes the judgment based on the UE location and the target area The judgment means the NF (e.g. LMF) only counts and reports the valid UE location data to the NWDAF or other LCS clients. + +Besides, if the LCS service demander including NWDAF indicates explicitly in the request that there is no need to implement the exact area event reporting, the UE would handle the area event reporting as cell and TA granularity although the target area is defined with the finer granularity. + +### 6.35.3 Procedures + +#### 6.35.3.1 NWDAF interacts with GMLC + +Figure 6.3.1-1 in clause 6.3.1 of TS 23.273 [5] is reused with the following enhancements: + +![Sequence diagram showing deferred 5GC-MT-LR for periodic, triggered and UE available location events. Lifelines: UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, LCS Client, NEF, AF. The diagram illustrates the interaction between these entities for various location reporting scenarios, including network-triggered, UE-triggered, and periodic events.](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant LMF + participant V-GMLC + participant H-GMLC + participant UDM + participant LCS Client + participant NEF + participant AF + + Note right of LCS Client: 1a. LCS Service Request + Note right of LCS Client: 1b-1. Nnef_EventExposure_Subscribe Request + Note right of H-GMLC: 1b-2. Ngmlc_Location_ProvideLocation Request + Note right of UDM: 2. Nudm_SDM_Get + Note right of UDM: 3. Nudm_UECM_Get + Note right of H-GMLC: 4. Ngmlc_Location_ProvideLocation Request + Note right of V-GMLC: 5. Namf_Location_ProvidePositioningInfo Request + Note right of AMF: 6. Namf_Location_ProvidePositioningInfo Response + Note right of H-GMLC: 7. Ngmlc_Location_ProvideLocation Response + Note right of LCS Client: 8a. LCS Service Response + Note right of H-GMLC: 8b-1. Ngmlc_Location_ProvideLocation Response + Note right of NEF: 8b-2. Nnef_EventExposure_Subscribe Response + Note right of AMF: 9. Wait for UE to become reachable + Note right of AMF: 10. Network Triggered Service Request + Note right of NG-RAN: 11. NAS Location Notification Invoke Request + Note right of AMF: 12. NAS Location Notification Return Result + Note right of AMF: 13. LMF Selection + Note right of AMF: 14. Nlmf_Location_DetermineLocation Request + Note right of LMF: 15. UE Positioning + Note right of NG-RAN: 16. LCS Periodic-Triggered Invoke Request + Note right of LMF: 17. LCS Periodic-Triggered Invoke Return Result + Note right of AMF: 18. Nlmf_Location_DetermineLocation Response + Note right of V-GMLC: 19. Namf_Location_EventNotify + Note right of H-GMLC: 20. Ngmlc_Location_EventNotify + Note right of LCS Client: 21a. LCS Service Response + Note right of H-GMLC: 21b-1. Ngmlc_Location_EventNotify + Note right of NEF: 21b-2. Nnef_EventExposure_Notify + Note right of UE: 22. Event Detected + Note right of UE: 23. Location Measurements + Note right of AMF: 24. UE Triggered Service Request + Note right of LMF: 25. Event Report + Note right of UE: 26. Event Report Acknowledgment + Note right of LMF: 27. UE Positioning + Note right of V-GMLC: 28. Nlmf_Location_EventNotify + Note right of H-GMLC: 29. Ngmlc_Location_EventNotify + Note right of LCS Client: 30a. LCS Service Response + Note right of H-GMLC: 30b-1. Ngmlc_Location_EventNotify + Note right of NEF: 30b-2. Nnef_EventExposure_Notify + Note right of UE: 31. Event Detected + +``` + +Sequence diagram showing deferred 5GC-MT-LR for periodic, triggered and UE available location events. Lifelines: UE, NG-RAN, AMF, LMF, V-GMLC, H-GMLC, UDM, LCS Client, NEF, AF. The diagram illustrates the interaction between these entities for various location reporting scenarios, including network-triggered, UE-triggered, and periodic events. + +**Figure 6.35.3.1-1 (Figure 6.3.1-1): Deferred 5GC-MT-LR for periodic, triggered and UE available location events** + +1. For area event reporting, the LCS client (e.g. NWDAF) provides to the GMLC the details of the target area and may include the requirement of area reporting (e.g. reporting based on the cell or TA level as the Rel-17 does, reporting only when the UE locates in the exact target area, multiple scheme reporting). In this step, if the target area is defined with finer granularity, the area accuracy may be included to allow the LCS architecture to report the UE location within the tolerant granularity. + +- 4&5. The GMLC delivers the target area information received in step 1 to the AMF. If the requirement of area report is indicated with reporting only when the UE locates in the exact target area, the GMLC may not convert the target area into the cell or TA lists and just notifies the target area to the UE. +- 14&16. The AMF delivers the target area information received in step 1 to the LMF and then the LMF notifies the UE in the LCS trigger invoke request message. +- 22. The UE detects the target area. If the UE obtains its exact location, the UE compares the location with the target area. The UE triggers area event reporting only when the UE locates in the exact target area. If the UE cannot calculate its exact location, the UE may request the NF (e.g. LMF) to assist in confirming and comparing the location with the target area. +- 25. The UE triggers area event reporting. Optionally, the UE may send temporary area event reporting to the LMF with an indication to request the LMF to confirm and compare location when the UE cannot calculate its exact location. +- 28. The LMF sends the area event reporting. If the temporary area event reporting is received in step 25, the LMF compares the location with the target area. This procedure will be terminated and the reporting status will not be updated if the UE doesn't locate in the exact target area. + +#### 6.35.3.1 NWDAF interacts with AMF + +The procedure mentioned (i.e. Figure 6.13.3.2-1) in sol#13 is reused with the following step enhancements: + +![Sequence diagram showing the interaction between UE, RAN, AMF, LMF, UDM, and NWDAF for continuous location collection. The sequence starts with NWDAF sending a Nudm_UECM_Get Request to UDM, followed by a Location information Request from NWDAF to AMF. The AMF then performs LMF Selection and sends an Nlmf_Location_DetermineLocation Request to the LMF. The LMF initiates UE Positioning, which involves an LCS Periodic-Triggered Invoke request to the UE. The UE responds with an LCS Periodic-Triggered Invoke return result. The LMF then sends an Nlmf_Location_DetermineLocation response to the AMF, which in turn sends a Location information response to the NWDAF. The UE also performs Event Detection and sends an Event report to the LMF, which responds with an Event report Ack. Finally, the LMF sends another Nlmf_Location_DetermineLocation response to the AMF, which sends a Location information response to the NWDAF.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant LMF + participant UDM + participant NWDAF + + Note right of NWDAF: 1. Nudm_UECM_Get Request + NWDAF->>UDM: 1. Nudm_UECM_Get Request + Note right of UDM: 2. Nudm_UECM_Get Response + UDM-->>NWDAF: 2. Nudm_UECM_Get Response + Note right of NWDAF: 3. Location information Request + NWDAF->>AMF: 3. Location information Request + Note right of AMF: 4. LMF Selection + AMF->>LMF: 5. Nlmf_Location_DetermineLocation Request + Note right of LMF: 6. UE Positioning + Note right of AMF: 7. LCS Periodic-Triggered Invoke request + AMF->>UE: 7. LCS Periodic-Triggered Invoke request + Note right of UE: 8. LCS Periodic-Triggered Invoke return result + UE-->>AMF: 8. LCS Periodic-Triggered Invoke return result + Note right of LMF: 9. Nlmf_Location_DetermineLocation response + LMF-->>AMF: 9. Nlmf_Location_DetermineLocation response + Note right of AMF: 10. Location information response + AMF->>NWDAF: 10. Location information response + Note right of UE: 11. Event Detection + Note right of UE: 12. Event report + UE->>LMF: 12. Event report + Note right of LMF: 13. Event report Ack + LMF-->>UE: 13. Event report Ack + Note right of LMF: 14. UE Positioning + Note right of LMF: 15. Nlmf_Location_DetermineLocation response + LMF-->>AMF: 15. Nlmf_Location_DetermineLocation response + Note right of AMF: 16. Location information response + AMF->>NWDAF: 16. Location information response + +``` + +Sequence diagram showing the interaction between UE, RAN, AMF, LMF, UDM, and NWDAF for continuous location collection. The sequence starts with NWDAF sending a Nudm\_UECM\_Get Request to UDM, followed by a Location information Request from NWDAF to AMF. The AMF then performs LMF Selection and sends an Nlmf\_Location\_DetermineLocation Request to the LMF. The LMF initiates UE Positioning, which involves an LCS Periodic-Triggered Invoke request to the UE. The UE responds with an LCS Periodic-Triggered Invoke return result. The LMF then sends an Nlmf\_Location\_DetermineLocation response to the AMF, which in turn sends a Location information response to the NWDAF. The UE also performs Event Detection and sends an Event report to the LMF, which responds with an Event report Ack. Finally, the LMF sends another Nlmf\_Location\_DetermineLocation response to the AMF, which sends a Location information response to the NWDAF. + +**Figure 6.35.3.1-1 (Figure 6.13.3.2-1): AMF provides UE location information to NWDAF (Continuous Collection)** + +3. The NWDAF provides to the AMF the details of the target area and may include the requirement of area reporting (e.g. reporting based on the cell or TA level as the Rel-17 does, reporting only when the UE locates in the exact target area, multiple scheme reporting). In this step, if the target area is defined with finer granularity, the area accuracy may be included to allow the LCS architecture to report the UE location within the tolerant granularity. +- 5&7. The AMF delivers the target area information received in step 3 to the LMF and then the LMF notifies the UE in the LCS trigger invoke request message. +11. The UE detects the target area. If the UE obtains its location, the UE compares the location with the target area. The UE triggers area event reporting only when the UE locates in the exact target area. If the UE cannot calculate its exact location, the UE may request the NF (e.g. LMF) to assist in confirming and comparing the location with the target area. +12. The UE triggers area event reporting. Optionally, the UE may send temporary area event reporting to the LMF with an indication to request the LMF confirm and compare location when the UE cannot calculate its exact location. +15. The LMF sends the area event reporting. If the temporary area event reporting is received in step 12, the LMF compares the location with the target area. This procedure will be terminated and the reporting status will not be updated if the UE doesn't locate in the exact target area. + +## 6.35.4 Impacts on services, entities, and interfaces + +GMLC/AMF/LMF: + +- Supports delivering the detailed target area information defined with finer granularity to the UE. + +LMF: + +- Determines whether the UE location is in the exact target area or not when the UE can not calculate its exact location or receives the request from the UE side to help to make a judgment. +- Update the reporting status only when the UE location is in the exact target area. + +UE: + +- Supports triggering area event reporting only when the UE can calculate its exact location and the UE locates in the exact target area defined with finer granularity + +--- + +## 7 Evaluation + +### 7.1 Key Issue #1: Architectural Enhancement to support User Plane positioning + +The following solutions address KI#1. + +- Solution #1: Positioning protocol transport over User Plane. +- Solution #2: Discovery of User Plane service Cooperated with 3GPP LCS Features. +- Solution #3: User plane location capability transfer and positioning via user plane. +- Solution #19: Support of Low Latency via User Plane. + +KI#1 identifies the following benefit of user plane positioning: + +- It has a more efficient communication overload with a direct connection from LCS server to UE. + - It may not require gNodeB, AMF, LMF signalling processing of RRC, NG-AP and HTTP/2 protocol stacks. A single session may handle all the transactions. + +An additional benefits can be reduced latency which is covered by KI#10, applicability in local service covered in KI#2, mobility support covered in KI#8, power saving covered by KI#11 and KI#12. + +Solutions need to be evaluated against these benefits. + +#### UE Impact + +As a "*direct connection from LCS server to UE*", UE impact is of first priority. In R16 and R17, UE compliant with TS 38.305 [6] and related specifications has already specified user plane support. + +As the considerations in KI#1 "*emergency/non-emergency, other regulatory cases like lawful interception*", whether legacy Rel-16/Rel-17 compatible UE can directly use the user plane service in this study is important for emergency and/or regulatory use cases. + +Solution#1 introduced a new protocol which requires UE with a new communication method. Solution#2 takes SUPL compliance with same reference as TS 38.305 [6]. Solution#3 supports 'secure user plane' and it depends on NAS to activate the user plane connection from UE; The detailed protocol between UE and LMF in solution#19 and solution#3 is unknown whether it is a new protocol to be defined from scratch or reusing SUPL. + +In summary: + +**Table 7.1-1: Comparison of solutions on UE Impact** + +| R16/R17 UE Impact | Solution#1 | Solution#2 | Solution#3 | Solution#19 | +|----------------------|------------|------------|------------|-------------| +| Mandatory Change | Yes | No | TBD | TBD | +| Optional Enhancement | Yes | Yes | Yes | TBD | + +NOTE 1: The main optional enhancement update to UE includes the DL\_NAS\_TRANSPORT or extension to LPP. These enhancements are needed in solution#1 and solution#3, optional to solution#2. + +### Delay Analysis + +The protocol of solution#1 doesn't have details for analysis. There are no enough details for comparison between 'lightweight' protocol in solution#1, OMA ULP in solution#2, 'secure user plane' in solution#3 and "User Plane Transfer of Event Reports" in solution#19. Although solution#19 improves legacy supplementary service, but it has two segments of secure connection. So, latency analysis doesn't have comparable result. + +### Mobility Support + +"mobility support covered in KI#8" has both EPS to 5GS mobility and inter-RAN node mobility. + +Since data channel should not have impact when UE moves from one RAN node to another, the analysis focuses on EPS and 5GS mobility. + +In EPS, user plane is specified in TS 23.271 [4] as same SUPL reference to TS 38.305 [6]. The mobility switches over with different cases as following summary: + +Since solution#19 doesn't cover handover or mobility contents, the EPS/5GS mobility in this solution is TBD. + +**Table 7.1-2: Comparison of solutions on how to support EPS and 5GS mobility** + +| EPS and 5GS mobility | Solution#1 | Solution#2 | Solution#3 | Solution#19 | +|--------------------------|------------------------------|------------|------------|-------------| +| UE moves from EPS to 5GS | SUPL->'lightweight protocol' | SUPL->SUPL | SUPL->TBD | SUPL->TBD | +| UE moves from 5GS to EPS | 'lightweight protocol'->SUPL | SUPL->SUPL | TBD->SUPL | TBD->SUPL | + +### Local/Edge LCS Support + +"Applicability in local service covered in KI#2" is taken as dependencies in solution# 4 and solution#5. + +It is also described in KI statements "deployed the edge data network.... and fits into the architecture in TS 23.548 [10]". TS 23.548 [10] mainly contains discovery and relocation features which maps to user plane function discovery and UE mobility to Edge Hosting Environment. + +Since solution#19 doesn't cover handover or mobility contents, the discovery and DN mobility in this solution is TBD. + +**Table 7.1-3: Comparison of solutions on Edge/Local LCS Support** + +| Edge/Local LCS Support | Solution#1 | Solution#2 | Solution#3 | Solution#19 | +|--------------------------------------------|---------------------------------------|-------------------------------|---------------------------------------|-------------| +| User Plan Discovery | Through enhancement of NAS | Compliant with TS 23.548 [10] | Through enhancement of NAS | TBD | +| Mobility between different data networks * | Through enhancement of LMF switchover | Compliant with TS 23.548 [10] | Through enhancement of LMF switchover | TBD | + +NOTE 2: The UE mobility can cover the following cases: + +1. UE may move between central data network (C-DN) and local data network (L-DN)). +2. UE may move between different local data networks (L-DN). + +## Other Aspects + +Among all solutions of KI#1, power saving is not addressed. + +With Solution #1, a LCS-UP connection over a PDU session is established between the UE and an LMF. During the registration procedure or the initiation of an LCS procedure, AMF decides to select an LMF and request the UE and the selected LMF to establish an LCS-UP connection. LMF sends its user plane location address to UE via existing procedures, and a lightweight LPP transfer protocol is to be introduced. User Plane connection establishment is initiated by the UE and can be transferred to another LMF by the AMF. An LMF can also transfer a user plane connection it has to a UE to a different LMF. User plane establishment and transfer requires extra signalling but should reduce signalling when used to transfer positioning messages between the UE and LMF. However, it is not clear how an AMF can determine which UEs will benefit from a user plane connection. If applied to all UEs, there could be more signalling overall and not less signalling. If applied to UEs which perform the most positioning, there might be less signalling overall. But there is no analysis of this. In this solution, it is LMF to decide whether or not utilize the user plane positioning method after receiving a request from AMF. The user plane connection would not be used if LMF decides to use control plane for UE positioning. + +With Solution #2, an LMF can transfer control plane positioning of a UE to a separate SUPL user plane connection between the UE and a separate but associated LCUP server. In this solution, it is LMF to decide whether or not utilize the user plane positioning method after receiving a request from AMF. SUPL based push mechanism or LPP itself is used to trigger the establishment of UP connection if there is no available one. There would be extra signalling to setup the SUPL user plane connection but, once setup, transfer of SUPL positioning messages could use less signalling. The user plane server (LCUP) might possibly be part of an LMF. The solution also requires some clarification of how the SUPL user plane connection would be used. For example, a SUPL user plane connection is normally released after a UE location is obtained, as its emphasized OMA SUPL compliance, it should use minimized handshake feature defined in clause 6.1.1.4 of OMA ULP specification if the SUPL user plane connection ends then can be resumed for a later positioning of the UE. URSP including user plane positioning related DNN/S-NSSAI is used for PDU session establishment. + +With Solution #3, an LMF can trigger a UE to establish a user plane secure connection with the LMF and then exchange LPP messages with the UE over the user plane secure connection. An LMF can also use an already established user plane secure connection with a UE to transfer LPP messages. The protocols to securely support the user plane connection and conditions for releasing the user plane connection re-uses the solution#1. Establishing a user plane will add extra signalling, thus AMF may trigger UE to establish the PDU session when UE registers, considering UE capability, location and subscription information, etc. to reduce signalling. + +With Solution #19, user plane positioning is used only for a periodic or triggered MT-LR to return location event reports to an LCS Client or AF. The user plane connection is between the UE and LCS Client or AF and comprises either a single direct connection or two concatenated user plane connections through an intermediate entity that is either the LMF or the H-GMLC. For UE assisted position methods, positioning (e.g. LPP) messages can be exchanged between the UE and LMF over one user plane connection, with an event report later sent by the LMF to the LCS Client or AF over a second user plane connection. For UE based position methods, no signalling between the UE and LMF is needed and a single direct user plane connection or two concatenated user plane connections through an H-GMLC can be used. Although there is extra signalling to establish and later release the user plane connection(s), signalling would be reduced for reporting of location events which would reduce overall signalling as long as event reports are sent. The 'second user plane connection' in this solution does not use the SBA pattern and exposes the address information of LMF directly to AF and LCS Client. In this solution, UE assisted and UE-based/UE standalone positioning methods utilize different procedures, which does not involve LMF to make the decision to select the positioning method and mode. The solution impacts the UE, AMF, LMF, GMLC, LCS client, AF. + +In general, use plane based solutions can reduce the communication overload and signalling cost of control plane, i.e. AMF not involved for LPP message transfer. In all solutions, there are no limitations on deployment scenario, i.e. the LMF or LCUP can be deployed at centre or edge. + +In summary, the comparison of solutions for KI#1 is listed in the Table 7.1-4. + +Table 7.1-4: Comparison of solutions of Key Issue #1 + +| Solutions | NF to trigger to establish the UP connection | How to trigger UP establishment if there is no available one | NF/entity the UE establish UP connection to | NF to selects the UP method | Transport mechanism for LPP or Supp Svc messages | Whether cover LMF change | Impacts on NFs | +|---------------|----------------------------------------------|--------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------|---------------------------------------------------------|--------------------------|------------------------------| +| Sol#1 | AMF | UP Info of LMF | LMF | LMF | A lightweight protocol to be defined by stage 3 in 3GPP | Yes | UE, AMF, LMF, UDM, NRF | +| Sol#2 | LMF | LCUP information or OMA SUPL based push mechanism | LCUP (separated but cooperated with LMF) | LMF or UE (SUPL) | OMA SUPL | NO | UE, LMF and LCUP at least | +| Sol#3 | LMF | UP Info of LMF | LMF | LMF or UE (for MO-LR after UP connection established) | Re-use Sol#1 | Yes | UE, LMF and AMF | +| Sol#19 | LCS client/ AF/GMLC/L MF | UP Info of LCS client/ AF/GMLC/LMF | LCS client or AF/GMLC/LM F | LMF not involved | TLS | NO | UE, LMF, GMLC, LCS client/AF | + +## 7.2 Key Issue #2: enhanced positioning architecture for NPN deployment + +The clause evaluates the solutions for KI#2 as following. + +Solution#4 and #5 addresses key issue#2: enhanced positioning architecture for NPN deployment. Both solutions propose the following principles: + +- AMF (in the public network) for general service operation, local AMF/any AMF for LCS operation. +- UE location result is transmitted from LMF to GMLC, not via AMF (in the public network). +- Non-UE NRPPa messages are transmitted between LMF and local AMF/any AMF. +- UE associated NRPPa Requested message are transmitted via AMF in public network. + +Open issue of this key issue is the method for UE associated NRPPa Response message transmission. Two options are for discussion: + +- Solution#4: via local AMF. The latency is reduced than legacy network, The impacts are on Local AMF, and RAN. +- Solution#5: via AMF in the public network. The latency is same as legacy network. No new impact. + +## 7.3 Key Issue #3: Local Area Restriction for an LMF and GMLC + +The clause evaluates the solutions for KI#3 as following. + +Solution#6, #7, #8, #9 are all addressing key issue#3: Local Area Restriction for an LMF and GMLC. Three aspects "parameter configuration", "parameter exchange", and "LMF selection logic" are used to summarize the solutions: + +**Table 7.3-1: Comparison of solutions of Key Issue #3** + +| | | | | | +|--------------------------------|----------------------------------|------------------------------------------------|-----------------------------------------------------------|------------------------------------------------| +| Parameter configuration | GMLC: configured with LMF ID | AMF/NRF: Mapping of AF/client ID and LMF ID | AMF: GMLC service area | AMF/UDM: Mapping of UE ID and LMF/GMLC address | +| Parameter exchange | GMLC to AMF: Configured LMF ID | If mapping is on NRF, AMF retrieves the LMF ID | none | If mapping is on UDM, AMF fetches it. | +| LMF selection | AMF, based on provisioned LMF ID | By AMF | AMF, make sure LMF can serve the service area of the GMLC | By AMF | + +## 7.4 Key Issue #4: Interaction between Location Service and NWDAF + +Key issue#4 details the questions to be studied for WT#2 in FS\_eLCS\_Ph3 SID which includes the following aspects: + +- Aspect#1: how the location services can benefit from NWDAF; +- Aspect#2: how the NWDAF use cases can benefit from location service; and +- Aspect#3: how to provide location information to NWDAF. + +Accordingly, the solutions for the key issue#4 can also be classified based on the three aspects above, as shown in the Table 7.4-1. + +**Table 7.4-1: Solution Classification for KI#4** + +| Aspect in WT#2 | Solutions for the aspect | Whether coordination with the FS_eNA_Ph3 study is needed | +|---------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------| +| Aspect#1: how the location services can benefit from NWDAF | solution#11, solution#20 | Yes | +| Aspect#2: how the NWDAF use cases can benefit from location service | solution#12, solution#20, | Yes | +| Aspect#3: how to provide location information to NWDAF | solution#10, solution#13, solution#35 | No | + +The evaluation of solutions (i.e. solution#11, solution#12 and solution#20) related to aspect#1 is as follows: + +- LMF subscribes from NWDAF to obtain Location Accuracy analytics. NWDAF obtains data from OAM (MDT data) or historical LMF output. LMF improves the location accuracy by leveraging the location estimation from the NWDAF (Solution#11). +- NWDAF can optionally provide indoor/outdoor information based on available measurements to assist LMF in above process (Solution#20). + +The evaluation of solutions (i.e. solution#12, solution#20) related to aspect#2 is as follows: + +- Analytics consumer requests Location Accuracy analytics. NWDAF obtains data from GMLC/LMF to identify location accuracy (e.g. vertical/horizontal accuracy) for a positioning method (Solution 12). + +NOTE 1: Solution#59 in eNA\_Ph3 study TR 23.700-81 [17] provides corresponding solution on NWDAF. + +- information fed to NWDAF from GMLC/LMF could contain the indoor/outdoor information so that NWDAF can provide such feature in aspect#1. + +The evaluation of solutions (i.e. solution#10, solution#35 and solution#13) related to aspect#3 is as follows: + +- In solution#10 and Solution#35, NWDAF requests UE location from GMLC, i.e. the NWDAF acts as an AF which can request UE location using the existing location service. In Solution#10, the only enhancement to existing location service is to introduce new LCS Client Type and Service Type for NWDAF. In Solution#35, + +the NWDAF requests (or collects) the location information of a UE within a target geographical area from LCS system via GMLC. The enhancement to existing location service is to provide a target geographical area, which can be any shape comparing to current cell or TA concept, and a new location event reporting condition(i.e. reporting only when the UE locates in the exact target geographical area) from NWDAF to LMF. + +NOTE 2: The requirement why the NWDAF requests the finer granularity location information from LCS system originates from FS\_eNA\_Ph3 KI#9. How to provide location information to NWDAF in a target geographical area finer than TA/cell should be determined in this FS\_eLCS\_Ph3. + +- In solution#13, NWDAF requests UE location from AMF, so GMLC is not involved. The solution can reduce location service latency because not involving GMLC leads to reducing signalling flows especially in the roaming scenarios. Some enhancements to NWDAF and AMF to help complete the privacy check. It is an optional choice to realize data collection between NWDAF and LCS. + +## 7.5 Key Issue #5: Assistance data provisioning for low power high accuracy GNSS positioning + +This clause provides evaluation of Candidate Solutions for Key Issue #5. + +A unique Candidate Solution has been proposed: + +- Candidate Solution #21- Collection of nearby GNSS assistance data. The following concepts are proposed within the solution. + - LMF collects GNSS assistance data and coordinates of GNSS reference stations from AF(s) through AF event exposure service as described in clause 5.2.19.2 of TS 23.502 [3]. + - LMFs collected GNSS assistance data may update its NF profile in NRF by indicating the TAs of which corresponding GNSS assistance data exists, which can be discovered and used by other LMFs not having corresponding GNSS assistance data. + +Solution #21 reuses the AF event exposure service to collect GNSS assistance data, this solution only has some small impacts on LMF, NRF and AF functionality. + +## 7.6 Key Issue #6: UE Positioning without UE/User Awareness + +There is one solution in the present TR, i.e. sol#14, related to key issue#6 which aims to support UE not notified by any means during the LCS session, especially when UE is in CM\_IDLE or RRC\_INACTIVE state. + +To support key issue#6, two indications (i.e. UE unaware indication and user unaware indication) are introduced in sol#14. When UE unaware indication is provided by LCS Client/ AF, if target UE is in CM\_IDLE or RRC\_INACTIVE state, the target UE is not paged. When user unaware indication is provided by LCS Client/ AF, the only exception with the existing positioning procedure is that interaction between network and user, i.e. privacy check requiring such interaction, is skipped. Thus the function of the two indications is different. The impacts to NFs of the two indications are further analyzed in Table 7.6-1. + +**Table 7.6-1: Impacts to NFs of Different Indications in Solution#14** + +| Impacts | UE unaware | User unaware | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| GMLC impacts | Receive UE unaware indication from LCS Client/NEF and send the indication to AMF. | Receive user unaware indication from LCS Client/NEF and send the indication to AMF. | +| NEF impacts | Receive UE unaware indication from AF and send the indication to GMLC. | Receive user unaware indication from AF and send the indication to GMLC. | +| AMF impacts | Receive UE unaware indication from GMLC and behave differently based on UE state:
UE in CM_CONNECTED: send the UE unaware indication to LMF.
UE in CM_IDLE: not to page UE and rejects the location request from GMLC or returns the latest UE location. | Receive user unaware indication from GMLC and skip the privacy check which requires interaction with user is skipped. | +| LMF impacts | Receive UE unaware indication from AMF, select uplink positioning method (e.g. UL E-CID) based on the indication and send the network positioning message including UE unaware indication to RAN node. | No | +| RAN impacts | Receive UE unaware indication from LMF and behave differently based on UE state:
UE in RRC_CONNECTED: RAN behaviour is not impacted.
UE in RRC_INACTIVE: not to page UE and reject the network positioning message. | No | + +Based on the analyses in Table 7.6-1, user unaware indication requires the network to page UE when UE is in CM\_IDLE or RRC\_INACTIVE state during the positioning procedure which is not required by UE unaware indication. Thus the user unaware indication can only support user unawareness, the UE unaware indication can support both UE and user unawareness. + +## 7.7 Key Issue #7: Support of Positioning Reference Units and Reference UEs + +### 7.7.1 Evaluation of solutions for PRU + +There are four solutions related to Positioning Reference Units (PRU) of KI#7, i.e. solution#15, #16, #28, #29 . Solution#15 includes three options from PRU Information Acquisition perspective, which are referred as solution#15-AMF, solution#15-LMF and solution#15-UDM. + +The comparison of solutions is shown in Table 7.7.1-1. + +Table 7.7.1-1: Comparison of solutions to PRU of KI#7 + +| | Sol#15-AMF | Sol#15-LMF | Sol#15-UDM | Sol#16 | Sol#28 | Sol#29 | +|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| PRU Registration | UE sends Registration Request including PRU information to AMF | Including two options:
Option#B.1: UE sends PRU Registration Request including PRU information to LMF via AMF. The message is a supplementary service operation.
Option#B.2: UE sends PRU Registration Request including PRU information to LMF via LPP procedure. | PRU information included in the UE subscription data is pre-configured in UDM | When AMF receives PRU indication in Registration Request, it triggers positioning procedure after the Registration procedure. LMF obtains PRU location after the positioning procedure and stores the information locally. | Similar to sol#15-LMF, option#B.1.

PRU may register to multiple LMFs. | UE sends Registration request with PRU info to AMF. PRU Info may include AMF ID, LMF ID or URI, mobile/static PRU, Position info. | +| | AMF invokes Nnrf_NFManagement_NFUpdate Request including PRU location and PRU existence indication to NRF. | LMF invokes Nnrf_NFManagement_NFUpdate Request including PRU location and PRU existence indication to NRF. | | LMF invokes Nnrf_NFManagement_NFUpdate Request including PRU information to NRF | | LMF notifies the GMLC the PRU information | +| How to obtain PRU information used to assist target UE positioning | Target UE LMF obtains PRU AMF from NRF. Target UE LMF obtains PRU information from PRU AMF. | Target UE LMF obtains PRU LMF from NRF. Target UE LMF obtains PRU information from PRU LMF. | Target UE AMF obtains PRU information from UDM and provides PRU information to Target UE LMF. | Same as sol#15-LMF | Target UE LMF stores information about available PRUs | Target UE LMF obtains PRU from GMLC. | +| Impacted 5GC NF | AMF, LMF, NRF | AMF, LMF, NRF | AMF, UDM, LMF | AMF, LMF, NRF | LMF | AMF, LMF, GMLC | +| Impacts to RAN/ RAN WG | PRU wake up: RAN receives PRU wake up indication from AMF and sends broadcast message in the serving cell of target UE. | PRU wake up: same as sol#15-AMF.
In Option#B.2, PRU registration procedure is a new LPP procedure which is in RAN2 scope. | PRU wake up: same as sol#15-AMF | PRU wake up: same as sol#15-AMF | No | No | + +Solution #15 supports multiple alternatives and impacts multiple entities besides PRUs (AMF, LMF, NRF, UDM). There are also separate procedures defined for supporting an MT-LR and MO-LR and for activating and deactivating PRUs which add more impact. Option A (PRU registration to AMF) impacts the AMF which needs to indicate a PRU to the NRF after which an LMF would need to discover PRUs from the NRF. However, PRUs are not NFs but more part of the NG-RAN making NRF support possibly unnecessary. Option B (PRU registration to LMF) is more direct and impacts the PRU, LMF and possibly NRF. Option C (PRUs information are maintained at the UDM) requires an AMF to query the UDM for available PRUs and then indicate these to an LMF. It is not clear how a UDM would know about + +PRU availability since a PRU could be powered off, out of coverage or undergoing maintenance. Of these options, option B looks simplest. + +Solution #16 uses the NAS Registration procedure to indicate a PRU to an AMF which then indicates the PRU to an LMF via an Nlmf location request. There is no direct confirmation back to the PRU that the AMF was able to indicate the PRU to an LMF, so if the LMF rejects the Nlmf location request or if the AMF cannot find a suitable LMF, the PRU would not know. However such failure case is in scope of stage 3, e.g. AMF could send the UCU to PRU to notify the PRU registration failure. LMF utilization of a PRU to support location of a target UE (in clause 6.16.3.2) includes UE positioning in steps 2 and 6 for Figure 6.16.3.2-1. However, no details are provided concerning how the PRU would help position the target UE. Positioning of a target UE by a PRU is not so far defined by RAN, so it is unclear whether these steps are feasible and what might be the impacts to the LMF, target UE and PRU. The use of an NRF to discover other PRUs managed by another LMF to assist with the location of a target UE would add additional impacts to an LMF and NRF. + +Solution #28 avoids any impact to an AMF or NRF. A PRU registers with one or more LMFs using a supplementary services protocol. The PRU can be used by an LMF to obtain measurements of RAN nodes in the same way as from a normal UE using LPP. These measurements and a location of the PRU can be used to determine correction terms (e.g. timings and internal delays) of RAN nodes, as defined in TS 38.305 [6]. Extension of the solution to support Reference UEs could be possible later. The PRU updates the registration in LMF based on conditions received from LMF, e.g. periodically or triggered by location change. When the PRU registers with more LMFs, each LMF stores the same PRU information which leads to duplicated storage of the same information in the LMFs. In this case, the PRU has to update the registration when needed to all LMFs storing the PRU information, so more signalling cost is introduced. Furthermore, the PRU authentication would need to be performed in each LMF separately. This duplication of storage and authentication among multiple LMFs should not be significant if PRUs are few in number compared to UEs or if duplicate PRU storage and authentication only occurs for PRUs in border areas between LMF serving areas. + +Solution #29 stores the PRU information in GMLC. When LMF decides to perform the positioning procedures to PRU during the positioning process of target UE, the LMF always obtains PRU information from the GMLC. Considering that the PRU is introduced to improve positioning accuracy which is the responsibility of LMF and is transparent to GMLC, in order to avoid dispersing the same function in different network functions, it is better to store PRU information in LMF or the LMF profile stored in NRF. + +## 7.7.2 Evaluation of solutions for Reference UE + +There is one solution related to Reference UE of KI#7, i.e. solution#17. + +Solution #17 is based on use of sidelink positioning and ProSe. There seems to be no Uu (UL/DL) level positioning. This means the solution should be part of sidelink positioning and ranging in Release 18 and cannot be evaluated separately, e.g. in case it duplicates or conflicts with other sidelink positioning and ranging solutions for Release 18. + +## 7.8 Key Issue #8: support of location service continuity in case of UE mobility + +**Table 7.8-1: Comparison of solutions to 5GS<>EPS Mobility** + +| Solution | Solution Summary | Solution Evaluation | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 31 |

During periodic location service triggered, if AMF/LMF finds the UE reporting type includes "EUTRAN" and if the required "LCS QoS class" is "multiple QoS class", the AMF/LMF determines the corresponding location QoS can be applicable to EPS, e.g. AMF or LMF map the QoS class to "Best Effort" and choose the most stringent value from the "LocationQoS" as the QoS requirement, LMF sends these parameters to UE and AMF if AMF does not determine the location QoS applicable to EPS.

After receive the handover required, if AMF finds UE can support interworking between 5GS and EPS, AMF sends the 5GS location QoS corresponding EPS location QoS to GMLC.

After handover complete, if UE finds periodical event is triggered and if UE finds it has moved to EPS, the UE sends LCS MO-LR Invoke message, carry the location QoS can be applicable to EPS.

Similar solution for EPS->5GS mobility.

|

Solution is the deferred MTLR case and it is converted into an MO-LR session in the target case.

Not clear how LCS session is handled when mobility happens during the LCS signalling itself (i.e. before the measurements are got).

| +| 32 |

The source RAT AMF/MME acts as the anchor, forwarding the Positioning context data to the target RAT MME/AMF, which forwards the same the eSMLC/LMF. The LCS session is continued with in the target RAT and result sent back to the source AMF/MME, which responds back to the GMLC to return the location estimate to the LCS Client.

|

There is an assumption that the UE context stays in the source AMF/MME till the LCS session completes in the target RAT. This is an unrealistic assumption since the LCS session could have a long life (particularly in cases of event triggered/periodic cases) during which time the UE context cannot be stored on the source side.

| +| 33 |

Source AMF/MME play central role, cancelling LCS session, responding to GMLC with a new cause for HO and target MME ID.

GMLC then initiates location request to target MME/AMF with the location session data - location estimated and returned to GMLC which returns the estimate to LCS Client.

|

It is a common solution for all types of LCS procedures and positioning methods while keeping impacts to EPC to minimum. No need for any UE context retention on the source RAT side after HO is complete. The procedure can be easily enhanced to support LCS session over.

| + +**Table 7.8-2: Comparison of solutions to NG-RAN node mobility** + +| ID | Solution Summary | Solution Evaluation | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 22 |

S-AMF shares LCS session details to T-AMF as part of HO preparation.

T-AMF notifies to LMF after HO completion.

LMF continues with the LCS Session with new configuration.

LMF responds with UE location.

|

The solution is applicable to UL/DL methods + MOLR/MTLR/NILR procedures + Xn/NG Based HO - it is generic in nature.

Sharing of LCS information was analysed at RAN/AMF/LMF/GMLC.

RAN - not possible for DL methods.

LMF - LMF/eSMLC have no direct interface.

GMLC - this is possible, but may take time compared to AMF.

AMF - was found to be the most optimal in terms of time taken + generality of the solution - was chosen for the solution

The solution ensures that the LCS Client need not be aware of the mobility.

For mobility in RRC-INACTIVE and RRC-IDLE the explicit solution is not proposed. For mobility in RRC-INACTIVE, we believe that the current solution defined in R17 (23.273, sec. 6.7.3/6.7.4/6.7.5) could be reused/enhanced.

For mobility in RRC-IDLE, the current proposed solution (where location transfer happens from the old AMF to new AMF) could be reused.

| +| 30 |

As part of the HO procedure, the source RAN sends Positioning related information to Target RAN over Xn or NGAP (depending on the type of HO).

Target RAN then sends the positioning information to LMF.

AMF/Old LMF then determine if LMF should be reselected and forward the positioning configuration to chosen LMF.

AMF notifies the LMF the target cell ID/NG-RAN - based on that, the LMF configures the neighbouring RAN with the latest configuration.

In RRC-Idle mobility, as part of registration procedure, the new AMF checks if positioning information is present in the UE context data - if so, then sends the new AMF ID to LMF via the next periodic N1messageNotify.

|

The solution for connected mobility proposes the sharing of Positioning information between RANs directly (through Xn or NG). The following issues are noted.

For DL methods, the source RAN will not know that an LCS session is on or not due to the following reasons.

LCS signalling happens over LPP (invisible to RAN).

there is no UE associated NRPPa signalling for DL methods.

The IE Positioning Information defined in R17:XnAP provides only SRS-Config info - for UL methods. Evidently this solution cannot be applied to DL methods.

For UL methods, the sharing information over Xn is not likely to speed up the procedure, since that information can be taken into use by the target RAN only when the LMF sets up the LCS session with the target RAN.

In summary, we believe that this solution will not work for DL methods based LCS session and offers not much advantage for UL methods. Any solution defined should be common for UL, DL or UL+DL methods.

| + +## 7.9 Key Issue #9: Support of Positioning Requirements Related to Satellite Access + +The clause evaluates the solutions for KI#9 as following. + +There are 4 candidate solutions proposed to address positioning requirements related to satellite access. + +Solution overview: + +- Solution #18: Location Verification for Satellite Access assisted by NWDAF Analytics. + +NWDAF is involved to provide analytics with statistics and predictions of the UE location which can assist with the network verification task that is required when a UE provides its location to the network via satellite access. + +- Solution #23: Location Verification for Satellite Access assisted by TN access. + +Location verification for UE using satellite access is enforced based on the UE location provided through TN access. If the AMF decides to do such verification, it indicates UE to do registration via TN access. The UE location in TN access can be delivered to the AMF through registration procedure. + +- Solution #24: UE Location Verification based on Obtained Information. + +This solution depends on the NG-RAN providing assistance information to do location verification. The reliability of verification can be enhanced by means of the assistance information, but whether and what assistance information can be provided by NG-RAN should depend on RAN WGs conclusion. + +- Solution #34: UE location determination for Mobility Restriction enforcement + +This solution proposes AMF to invoke NI-LR procedure to determine the UE located TAI in the case of not all of the NG-RAN reporting TAIs are in Forbidden Area or Non-allowed area. AMF can perform precise Mobility Restriction based on the TAI determined through NI-LR procedure. The positioning method mode selection needs coordination with RAN WGs and depends on RAN supported methods. + +All the solutions can be evaluated based on the following factors: + +- Solution assumptions or restrictions. +- The reliability of UE location verification. +- RAN dependency for proposed solution. +- Functionality(entity, interface) impact. + +Based on the solution whether to resolve reliability issue, whether the solution has RAN dependency and functionality impacts, solutions can be evaluated as follows: + +**Table 7.9-1: Candidate Solutions evaluation** + +| Solution | Assumptions | verification reliability | RAN Independency | Functionality impact | +|-----------------------------------------------------------------------------|-------------|--------------------------------|------------------|----------------------| +| #18: Location Verification for Satellite Access assisted by NWDAF Analytics | N | Analytics confidence dependent | Y | AMF, NWDAF | +| #23: Location Verification for Satellite Access assisted by TN access | Y | Y | Y | UE, AMF, UDM | +| #24: UE Location Verification based on Obtained Information | N | RAN assistance dependent | N | NG-RAN, AMF, LMF | +| #34: UE location determination for Mobility Restriction enforcement | N | RAN positioning dependent | N | NG-RAN, AMF, LMF | +| NOTE: N = No, Y = Yes | | | | | + +#### 1) Solution assumptions and restrictions + +There is no assumption or restriction on solution #18, #24 and #34. + +Solution #23 works under the conditions that 1) the area that the UE located is covered by both TN access (e.g. LTE, NR) and NR satellite access and 2) UE has the capability of supporting both TN access and NR satellite access. Considering the user location verification under satellite access often needs to be performed in national cross borders, and some of the boundary areas have TN and NR satellite coverage, this solution is feasible in some cases. + +#### 2) The reliability of UE location verification. + +Solution #18 relies on NWDAF providing location statistics and analytics to the AMF to assist with location verification. While location verification relying only on analytics may not always be fully reliable (e.g. predictions on UE location may not be accurate), they will certainly enhance the reliability of the location verification process when combined with additional assistance information and/or procedures. Hence, in most cases, this can enhance the reliability of verification. + +Solution #23 relies on UE location in TN access to do verification. Since the UE location (e.g. the cell the UE is camping on) is reported by RAN rather than generated by the UE, besides, the UE location in TN access represents a smaller range of location area than that in NR satellite access, based on above, it can be seen as reliable when used for verification. + +The premise of solution #24 relies on RAN providing reliable assistance information. + +Solution #34 relies on NR Satellite-based RAN position method to obtain reliable UE location. + +3) RAN dependency for proposed solution. + +Getting reliable UE location through RAN position will increase the time latency. Especially the latency of satellite communication is more serious, RAN position will aggravate the time delay. Besides, satellite resource may be scarce, RAN position will increase resource consumption. + +Solution #18 and solution #23 has no RAN dependency. + +Solution #24 and solution #34 relies on RAN providing reliable location information. The feasibility of the solutions depends on RAN conclusion. + +4) Functionality(entity, interface) impact. + +Solution #18 requires NWDAF to do UE location analytic with the request from AMF and provide it to the AMF. No other enhancement is needed. + +Solution #23 requires AMF to indicate UE to register on TN access when location verification is determined to perform by AMF. UE location in TN access is reported to UDM via registration procedure and is further delivered to AMF. UE, AMF and UDM are involved to convey such location information, existing procedure can be reused. + +Solution #24 requires RAN to provide location assistant information to the AMF. N2 interface need to be enhanced, existing procedure can be reused. + +Solution #34 requires AMF to indicate to the LMF that reliable position method is required. Existing procedure can be reused with no more enhancement. + +## 7.10 Key Issue #10: Support of Reduced Latency + +By supporting user plane-based positioning, Sol#1, Sol#2, Sol#3 and Sol#19 can reduce the latency of LPP or Supplementary service transfer between UE and LMF, in particular when UPF and LMF are located at edge while serving AMF are located at centre (i.e. the LPP message or Supplementary service not to be relayed by centre AMF through control plane). + +- Compared with control plane based mode, the user plane mode may introduce extra signalling latency, e.g. there will be a PDU session/UP connection establishment procedure if there is no available proper PDU session/UP connection, when a LCS request is received by LMF. Sol#1 and Sol#3 considers to trigger LCS-UP connection/PDU session establishment at application registration events, which aims to establish LCS-UP connection/PDU session in advance to reduce latency. Sol#1 and Sol#3 also proposed to maintain the established user plane connection for the sake of low latency of subsequent LCS request. +- Sol#19 proposed a 'second user plane' between LMF/GMLC and AF or LCS client, which aims to bypass GMLC to reduce latency when reporting UE location to LCS client. However, exposure of LMF address information directly to LCS client and AF may cause security risks. By co-deployment of GMLC and LMF at edge, the latency between GMLC and LMF may be reduced. +- Sol#19 proposed a user plane connection between the UE and AF or LCS client for a periodic or triggered MT-LR which can minimize end to end latency when the target UE (rather than LMF) determines location estimates. + +## 7.11 Key Issue #11: Enhance the Triggered Location for UE power saving purpose + +This clause provides the evaluation of Candidate Solution (i.e. solution#25 and solution#35) for Key Issue #11. + +Power saving purpose is achieved by allowing the UE to report location only when the UE is in the pre-defined area. The location event report has dependency on the pre-defined area. Both Solution#25 and Solution#35 proposed that the pre-defined area can be requested by an LCS Client/AF and sent to the UE via LCS Periodic-Triggered Invoke Request message. + +In Solution #25: + +- the pre-defined area will be translated by GMLC to a geographical area as defined in TS 23.032 [26] and converted to a TA/cell list. The UE received pre-defined area named "event report allowed area" is a TA/cell list. The UE periodically monitors cell ID and/or TAI as broadcasted by RAN, by simply comparing with the received "event report allowed area", UE can decide it is in the area or not. +- Only when the UE is in the area, the UE needs to detect whether the event happens. So the event report allowed area is used to reduce UE power consumption by reducing the number of event report and the number of UE positioning procedures which may be triggered by the event report. +- The event report allowed area can be applied to all event types, and the UE can adjust the area based on the power status, e.g. if the power status of UE is low, the UE can set the area to a small area. +- Solution #25 also contains two ambiguous aspects concerning whether a UE should occasionally send event reports when outside an allowed area to show an HGMMLC and LCS Client that event reporting is still active in the UE and on whether an allowed area can be used in an opposite sense where a UE only reports when outside a certain area (e.g. where a UE spends most time in the area but UE location is only needed when the UE is outside the area). + +In Solution #35: + +- the pre-defined area can be any shape as requested by LCS client/AF, or the translated geographical area as defined in TS 23.032 [26]. The UE received pre-defined area named "exact target area" is with finer granularity than TA/cell list and can be any shape. +- The "exact target area" is an enhancement to area type event report, that the UE location is only reported when the UE is exactly in the "exact target area" +- To achieve this, either UE or LMF needs to compare the UE location and the "exact target area" with the UE location measurement. Only when the UE is in the "exact target area", UE/LMF reports the event. +- Power saving can be achieved only with Solution #25, i.e. after UE detects it is in the TA/cell list ("event report allowed area") and obtains the Location Measurement as specified in step 23) in clause 6.3.1 TS 23.273 [5]. By further comparing the location with the "exact target area", UE/LMF can decide that the UE is in the area or not, i.e. Case II mentioned area as shown in Figure 7.11-1, the area identified by cell/TA, but not in the pre-defined area. + +![Figure 7.11-1: Illustration of pre-defined area, event report allowed area, and finer granularity area. The diagram shows three stages: 1. A blue triangle labeled 'Pre-defined area'. 2. An arrow pointing to a cluster of blue hexagons labeled 'Event report allowed area'. 3. A larger diagram showing a cluster of blue hexagons with a red triangle overlaid. The red triangle is labeled 'Pre-defined area'. Within the red triangle, a smaller red hexagon is labeled 'Case I: Area identified by cell/TA, and in pre-defined area'. Outside the red triangle but inside the blue hexagon cluster, a red hexagon is labeled 'Case II: Area identified by cell/TA, but not in pre-defined area'.](5432eacbc055292cc3b3da108863b835_img.jpg) + +Figure 7.11-1: Illustration of pre-defined area, event report allowed area, and finer granularity area. The diagram shows three stages: 1. A blue triangle labeled 'Pre-defined area'. 2. An arrow pointing to a cluster of blue hexagons labeled 'Event report allowed area'. 3. A larger diagram showing a cluster of blue hexagons with a red triangle overlaid. The red triangle is labeled 'Pre-defined area'. Within the red triangle, a smaller red hexagon is labeled 'Case I: Area identified by cell/TA, and in pre-defined area'. Outside the red triangle but inside the blue hexagon cluster, a red hexagon is labeled 'Case II: Area identified by cell/TA, but not in pre-defined area'. + +Figure 7.11-1: Illustration of pre-defined area, event report allowed area, and finer granularity area + +## 8 Conclusions + +### 8.1 Key Issue #1: Architectural Enhancement to support User Plane positioning + +- A user plane connection may be used between a UE and LMF with the following properties. + - The UE uses the URSP which includes user plane positioning related PDU session parameters (e.g. DNN and S-NSSAI) to establish the PDU session for user plane positioning. + +- It is LMF to decide whether to use user plane or control plane positioning mode when receiving positioning requests from AMF. +- If LMF decides to utilize user plane positioning, the LMF sends its UP positioning address and security related information to UE to trigger the UP connection if it is not available. +- LMF and UE may maintain the established user plane connection between UE and LMF for subsequent LCS session. Protocol to be used for User Plan connection may be decided by SA WG3 and by Stage 3 based on considering the proposed alternatives: + - The user plane connections can be supported using other transport decided by CT WG1 and common security procedures and protocol to be determined by SA WG3. + - As per both TS 38.305 [6] from RAN and TS 23.271 [4] for GERAN/UTRAN/E-UTRAN, the User Plane work aligned with both RAN and 2G/3G/4G may use solution#2. + - The UP connection between UE and LMF supports LPP message transfer and Supplementary service. +- A user plane connection may be used between a UE and AF or LCS Client as defined in Solution #19 for a periodic or triggered MT-LR for the case where UE based location is used and where the UE determines location estimates. The AF or LCS Client address and security related information is then provided to the UE in the MT-LR request. The UE establishes the user plane connection to the AF or LCS Client and uses it to send event reports to the AF or LCS Client. + +## 8.2 Key Issue #2: enhanced positioning architecture for NPN deployment + +The Local AMF/Any AMF in NPN deployment is used to transfer the Non-UE Associated Network Assistance Data between the RAN and LMF, as described in solution 4 and solution 5. + +For UE Associated Network Positioning procedure, the LMF sends the UE Associated Network Positioning message towards the RAN via the serving AMF. RAN responds UE Associated Network Positioning message to LMF via the serving AMF. + +The LMF notifies the UE location to GMLC directly, i.e. without going through the serving AMF. + +## 8.3 Key Issue #3: Local Area Restriction for an LMF and GMLC + +The following aspects are concluded for normative work: + +### Aspect 1: Provisioning of LMF ID: + +1. LCS Data in the GMLC for an LCS Client/AF, maybe enhanced by adding the following parameters: + +- LMF ID; +- Group ID and its correlating LMF ID. + +When the GMLC receives a MT location request from LCS client/AF, GMLC determines the LMF ID based on the LCS Data context per LCS client/AF. + +If that group ID can be provided or derived from the LCS request, GMLC determines the LMF ID based on the provisioned Group ID. + +2. GMLC may be configured with an LMF ID, and irrelevant to any LCS client/AF. When the GMLC receives a MT location request from LCS client/AF, GMLC determines the LMF ID for all LCS client/AF. +3. UDM may be enhanced in the UE LCS subscriber data by adding a correlating LMF ID, and GMLC fetches it when interacting with UDM. +4. AMF maybe configured locally, a mapping table of UE identity e.g. MSISDN and LMF/GMLC address, When receiving a MO-LR, AMF determines LMF and GMLC based on local configuration. + +**Aspect 2: LMF selection:** + +- The GMLC provides LMF ID to AMF or AMF determines the LMF ID based on aspect 1. The AMF uses the LMF ID to select the LMF. + +## 8.4 Key Issue #4: Interaction between Location Service and NWDAF + +Key issue#4 details the questions to be studied for WT#2 in FS\_eLCS\_Ph3 SID which includes the following three aspects: + +- Aspect#1: how the location services can benefit from NWDAF; +- Aspect#2: how the NWDAF use cases can benefit from location service; and +- Aspect#3: how to provide location information to NWDAF. + +The interim conclusion for aspect#1 is as follows: + +NOTE 1: In this aspect, as the beneficiary is LCS system, LCS will do the conclusion and inform FS\_eNA\_Ph3 about the requirements to NWDAF (eNA\_Ph3 Key Issue#9) for the enhancement of LCS system. + +- NWDAF provides new analytics for Location Estimation Accuracy. The location accuracy analytics include horizontal or vertical accuracy, indoor/outdoor indication. + - Solutions 11 and 20 will be used as a basis to derive location estimation accuracy analytics. Further details on input data for the new location accuracy analytics will be determined during the normative phase in coordination with eNA\_Ph3. +- LMF as a NWDAF consumer of such analytics uses Location Estimation Accuracy analytics to determine Position Method in the area where a UE is located. +- Location client as a consumer of such analytics uses Location Estimation Accuracy to determine a requested LCS QoS class or adjust application specific parameters (out of scope of 3GPP). + +The interim conclusion for aspect#2 is as follows: + +NOTE 2: In this aspect, as the beneficiary is NWDAF, NWDAF (FS\_eNA\_Ph3 Key Issue#9) is expected to be informed with the possibilities and benefits from LCS. + +NOTE 3: FS\_eNA\_Ph3 Key Issue#9 required enhancements to LCS system will be evaluated, coordinated in this aspect based on coordination decision. + +- The NWDAF can retrieve indoor/outdoor indication if it can be decided by LMF. +- The NWDAF can provide as part of Location Estimation Accuracy a ratio of NLOS/LOS measurements, if LMF receives the NLOS/LOS measurement indicator from the UE in the measurement report. + +The interim conclusion for aspect#3 is as follows: + +- The NWDAF retrieves location data from the GMLC using the Ngmlc services. +- To support privacy check, new LCS Client Type and Service Type is introduced and is used by NWDAF to request UE location: + - new LCS Client Types for PLMN Operator Class: + - NWDAF client in the HPLMN (when the UE is currently being served by the HPLMN); + - NWDAF client in the VPLMN. + - new standardized Service Type for Tracking Services: + - Analytics; + +- Model training. +- To support reporting of finer granularity UE location information in a target geographical area in form of any shape comparing with TA/cell to the NWDAF, the enhancements for LCS system include: + - The NWDAF provides to LCS system a target geographical area and a new location event reporting condition, i.e. reporting only when the UE locates in the exact target geographical area; + - By comparing UE location information with the target geographical area, the LCS system reports the UE location information to the NWDAF once UE locates in the target geographical area. + +## 8.5 Key Issue #5: Assistance data provisioning for low power high accuracy GNSS positioning + +LMF reuses the AF event exposure service to collect nearby GNSS assistance data. + +## 8.6 Key Issue #6: UE Positioning without UE/User Awareness + +For key issue #6, it is concluded that solution#14 (UE unaware indication) is used as the baseline for normative work. + +## 8.7 Key Issue #7: Support of Positioning Reference Units and Reference UEs + +To support PRU, the conclusions are as follows: + +- For PRU Registration, the conclusions include: + - UE sends UL NAS Transport including PRU Registration Request to AMF. + - The PRU Registration is an LCS supplementary service message and has no new AMF impact. + - AMF sends the PRU Registration Request to LMF and may include a UE verification indication indicating whether this UE can serve as a PRU. + - PRU Registration Request includes PRU information. + - PRU information may include PRU's positioning capability, location information (if known), type and state of the PRU (e.g. mobile/static type, on/off state) + - The PRU may register with multiple LMFs. e.g. for the case a PRU is in multiple LMF overlapped serving areas. + - LMF may indicate to NRF the PRU information or may store PRU information locally based on operator policy. + - LMF stores PRU information and may indicate to NRF the PRU existence in its NF profile. + - When the PRU information is provided to the NRF: + - The serving LMF invokes the Nnrf\_NFManagement\_NFUpdate service operation to store the PRU information in the LMF profile already stored in the NRF. + - When other LMF needs to obtain the PRU information for a certain area, the LMF just invokes the Nnrf\_NFDiscovery including NF type which is set to LMF and indicates the area. NRF will return the profile including PRU information of the LMFs covering the area. + - The target UE serving LMF may obtain PRU information locally, or may obtain PRU information and a PRU serving LMF from an NRF. + - A mobile PRU may lead to the update of registration at serving LMF and/or registration at a new LMF. + +- A serving LMF of PRU obtains PRU location measurements as described in clause 5.4.5 of TS 38.305 [6] by triggering the existing procedures defined in clause 6.11 of TS 23.273 [5]: +- To improve target UE positioning, the serving LMF of the target UE may obtain PRU location measurements from a serving LMF of PRU. + +To support Reference UE, the interim conclusion is as follows: + +- In this study, the Reference UE is the PRU. + +NOTE: The above Reference UE conclusion applies only to FS\_eLCS\_Ph3. Other uses of Reference UE as defined in other R18 studies do not require Reference UE to be a PRU. + +## 8.8 Key Issue #8: Support of location service continuity in case of UE mobility + +Normative work will take place according to principles described in this clause: + +### For 5GS -> EPS mobility: + +- (During Hand-over) The source AMF shall cancel the LCS session (e.g. to LMF), responding to GMLC with a new cause for HO and with the target MME ID. +- GMLC then initiates a new location request to the target MME identified in AMF message cancelling the LCS session over 5GS possibly translating location parameters such as QoS, user Id (no privacy check is needed). +- The location procedure takes place in EPS ; location estimation is returned to GMLC which returns the estimate to LCS Client. + +NOTE: This ensures a common procedure for all types of location and positioning methods (and regardless of where the hand-over takes place in the on-going location procedure) with no impacts to EPS. + +### For EPS -> 5GS mobility: + +- (During Hand-over) The source MME shall cancel the LCS session over EPS as currently specified, and responds to GMLC with a new cause for HO and with the target AMF ID. +- GMLC then initiates location request to target AMF identified in MME cancel message possibly translating location parameters such as QoS, user Id (no privacy check is needed). +- The location procedure takes place in 5GS ; location estimation is returned to GMLC which returns the estimate to LCS Client. + +For both direction of mobility between 5GS and EPS, the GMLC used over 5GS (respectively EPS) can issue location request over EPS (respectively 5GS). + +Based on operator policy, the following alternative solution could be considered. + +- For periodic/deferred location service continuity from 5GS to EPS: + - The LMF should determine whether UE can move between 5GS and EPS and notify UE the corresponding location QoS can be applied to EPS. + - After the location event is triggered, the UE should determine and send the suitable event triggered message and carry the suitable location QoS which can be applicable to EPS. +- For periodic/deferred location service continuity from EPS to 5GS: + - After the location event is triggered, the UE should determine and send the suitable event triggered message which can be applicable to 5GS. +- For both non-periodic/deferred location service continuity and periodic/deferred location service continuity: + - The LMF should determine the location information including the location QoS can be applicable to EPS, GMLC notify this information to E-SMLC to trigger the location procedure start in EPS. + +- After handover complete, the AMF/MME should notify GMLC. + +**For mobility between NG-RAN nodes in connected mode:** + +- S-AMF shares LCS session details to T-AMF as part of HO preparation. +- T-AMF notifies to LMF after HO completion. +- LMF continues with the LCS Session with new configuration. +- LMF responds with UE location to the T-AMF which responds to the LCS Client via the GMLC(s). + +**For mobility between NG-RAN node while the UE was RRC-INACTIVE:** + +- The current solution defined in R17 (clauses 6.7.3, 6.7.4, 6.7.5 of TS 23.273 [5]) is reused. + +**For mobility in RRC-IDLE:** + +- Reuse of the solution 22 (where location transfer happens from the old AMF to new AMF), as defined for connected mode in Solution #22, is used. + +## 8.9 Key Issue #9: Support of Positioning Requirements Related to Satellite Access + +Based on the KI#9 evaluation documented in clause 7.9, the following aspects are concluded as basis for normative work: + +- Verification of UE location provided via satellite access should be performed leveraging the LCS framework at the 5GC. +- The AMF is the entity in charge of providing the location verification decision, in line with Rel-17 mechanism of UE location verification: + - The AMF may trigger location service procedures as defined in TS 23.273 [5] to determine the UE location verification decision and optional TAI determination. Location information received at AMF is provided by LMF via the NI-LR procedure. The LMF may decide specific positioning methods to be used for verification based on RAN WG decisions. +- The AMF may receive assistance information from NWDAF (i.e. analytics containing UE location information) to perform the location verification decision. + +## 8.10 Key Issue #10: Support of Reduced Latency + +It is proposed to concluded as follows for KI#10: + +- When UPF and LMF are located at edge while AMF at centre, user plane based positioning can reduce the LPP message transfer latency between UE and LMF. +- By co-deployment of GMLC and LMF at edge, the latency of periodic or deferred location report from LMF to AF/LCS client through GMLC can be reduced. +- By using a user plane connection between a UE and an AF or LCS Client, end to end latency for a periodic or triggered MT-LR can be minimized if a target UE is able to determine the location estimates. + +## 8.11 Key Issue #11: Enhance the Triggered Location for UE power saving purpose + +For key issue #11, it is concluded that solution#25 (Event Report in an Allowed Area) is used as the baseline for normative work with the two ambiguous aspects identified in clause 7.11 also being resolved in the normative phase. + +## 8.12 Key Issue #12: support of low power and/or high accuracy positioning + +The following aspects are concluded for normative work: + +- UDM is enhanced to include LPHAP indication in the UE LCS subscription data. +- During the positioning procedure, AMF provides the LPHAP indication to the LMF, either obtaining from the GMLC, or in the UE LCS context which received during UE registration procedure. +- LMF is enhanced to receive from AMF of the LPHAP indication in the location request, and determine positioning method, by taking into account the LPHAP requirement. LMF also sends LPHAP indication to RAN in the NRPPa message. + +NOTE: RAN impact needs to coordinate with RAN WG, e.g. whether LPHAP indication needs to be sent to RAN at an earlier time, before positioning procedure is triggered. + +## Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------|------------|----|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149e | S2-2201583 | - | - | - | Proposed skeleton agreed at SA2#149e | 0.0.0 | +| 2022-09 | SA#97-e | SP-220828 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.0.0 | +| 2022-11 | SA#98-e | SP-221108 | - | - | - | 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-76/raw.md b/raw/rel-18/23_series/23700-76/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..020247b0dd733de0f0a844ba17940b7f3744d862 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/raw.md @@ -0,0 +1,1406 @@ + + +# 3GPP TR 23.700-76 V18.0.0 (2022-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on ad hoc group communication support for mission critical services; (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 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, and below the entire logo is the text 'A GLOBAL INITIATIVE' 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. + +© 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 ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations ..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4 Key issues ..... | 7 | +| 4.1 Key issue 1 – Ad hoc group communication ..... | 7 | +| 4.2 Key issue 2 – Network topology hiding from MC service client while establishing Ad hoc group communication..... | 7 | +| 4.3 Key issue 3 – Configuration parameters for Ad hoc group communication..... | 8 | +| 4.4 Key issue 4 – Modifying participants list of on-going ad hoc group communication..... | 8 | +| 4.5 Key issue 5 – Ad hoc group emergency alert..... | 8 | +| 5 Architectural requirements..... | 8 | +| 6 Architectural enhancements ..... | 9 | +| 7 Solutions..... | 9 | +| 7.1 Solution 1: Ad hoc group communication set up for MCX service..... | 9 | +| 7.1.1 General ..... | 9 | +| 7.1.2 Information flows ..... | 9 | +| 7.1.2.1 Ad hoc group communication request (MC service client – MC service server)..... | 9 | +| 7.1.2.2 Ad hoc group communication request return (MC service server – MC service client)..... | 12 | +| 7.1.2.3 AHGC share security material command (MC service client – MC service server)..... | 12 | +| 7.1.2.4 Ad hoc group communication request (MC service server – MC service client)..... | 13 | +| 7.1.2.5 Ad hoc group communication response (MC service server – MC service client)..... | 14 | +| 7.1.2.6 Ad hoc group communication response (MC service client – MC service server)..... | 14 | +| 7.1.2.7 Ad hoc group communication release request (MC service server – MC service client) ..... | 14 | +| 7.1.2.8 Ad hoc group communication release response (MC service client – MC service server)..... | 15 | +| 7.1.2.9 Ad hoc group communication get userlist (MC service server – MC service server)..... | 15 | +| 7.1.2.10 Ad hoc group communication get userlist response (MC service server – MC service server)..... | 15 | +| 7.1.2.11 Group Call Notify (MC service server – MC service client)..... | 15 | +| 7.1.3 Procedure ..... | 16 | +| 7.1.3.1 Ad hoc group communication within one MC system ..... | 16 | +| 7.1.3.1.1 Ad hoc group communication setup..... | 16 | +| 7.1.3.1.2 Release ad hoc group communication..... | 19 | +| 7.1.3.1.3 MC service server determining the participants list for the Ad hoc group communication setup ..... | 20 | +| 7.1.3.2 Ad hoc group communication involving multiple MC system..... | 23 | +| 7.1.3.2.1 Ad hoc group communication setup – Participants list provided by the initiator ..... | 23 | +| 7.1.3.2.2 Ad hoc group communication setup – Participants list determined by the MC service server..... | 24 | +| 7.1.4 Solution Evaluation ..... | 26 | +| 7.2 Solution 2: Ad hoc group call involving multiple MC systems..... | 26 | +| 7.2.1 General ..... | 26 | +| 7.2.2 Solution description..... | 26 | +| 7.2.2.1 Procedures..... | 26 | +| 7.2.2.1.1 Procedure for ad hoc group call setup..... | 26 | +| 7.2.2.1.2 Procedure for ad hoc group call release ..... | 28 | +| 7.3.2.1 Information Flows..... | 30 | +| 7.3.2.1.1 Group call request (MC service client – MC service server)..... | 30 | +| 7.3.2.1.2 Group call request (MC service server – MC service server)..... | 30 | +| 7.3.2.1.3 Group call request (MC service server – MC service client)..... | 31 | + +| | | | +|---------------------------------------------------|---------------------------------------------------------------------------------------------|-----------| +| 7.3.2.1.4 | Group call response (MC service server – MC service client) ..... | 32 | +| 7.3.2.1.5 | Group call response (MC service server – MC service server)..... | 32 | +| 7.3.2.1.6 | Group call response (MC service client – MC service server) ..... | 32 | +| 7.3.3 | Solution Evaluation ..... | 33 | +| 7.3 | Solution 3: Configuration parameters required for Ad hoc group communication ..... | 33 | +| 7.3.1 | General ..... | 33 | +| 7.3.2 | MC service configuration data ..... | 33 | +| 7.3.3 | MC service user profile configuration data ..... | 33 | +| 7.3.4 | Solution Evaluation ..... | 34 | +| 7.4 | Solution 4: Modifying participants list of on-going ad hoc group communication..... | 34 | +| 7.4.1 | General ..... | 34 | +| 7.4.2 | Information flows ..... | 34 | +| 7.4.2.1 | Modify ad hoc Group call participants request (MC service client – MC service server) ..... | 34 | +| 7.4.2.2 | Modify ad hoc group call participants response (MC service server – MC service client)..... | 35 | +| 7.4.2.3 | Ad hoc group call leave request (MC service server – MC service client) ..... | 35 | +| 7.4.2.4 | Ad hoc group call leave response (MC service client – MC service server)..... | 35 | +| 7.4.3 | Procedure ..... | 36 | +| 7.4.3.1 | Modification of ad hoc group communication participants by the initiator ..... | 36 | +| 7.4.3.2 | Modification of ad hoc group communication participants by the MC service server..... | 38 | +| 7.4.4 | Solution evaluation ..... | 40 | +| 8 | Overall evaluation ..... | 40 | +| 8.1 | Key issue and solution evaluation..... | 40 | +| 8.1.1 | Introduction ..... | 40 | +| 8.1.2 | Results ..... | 40 | +| 8.1.3 | Overall evaluation of key issue #1 ..... | 40 | +| 8.1.4 | Overall evaluation of key issue #2 ..... | 41 | +| 8.1.5 | Overall evaluation of key issue #3 ..... | 41 | +| 8.1.6 | Overall evaluation of key issue #4 ..... | 42 | +| 9 | Conclusions..... | 43 | +| Annex A (informative): Change history..... | | 44 | + +# --- 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 ad hoc group call allows authorised users to combine a set of MCX users based on implementation-specific criteria into a group call. The main characteristics of this ad hoc group call are: + +- a) The ad hoc group does not exist until it is spontaneously created during the call. +- b) The ad hoc group ceases to exist when the call terminates. +- c) The ad hoc group does not support 'persistent state' communication, e.g. emergency state. + +MCX users that are combined in an ad hoc group call can be served by the same or different MCX systems. The ad hoc group call uses a common security level, priority level, floor control method, and set of operational characteristics for the participants during the call. As with any group call, the priority level can change dynamically. + +The ad hoc group is used for a single call and it does not persist when the call is terminated. Authorized users can recreate the ad hoc group for subsequent calls, or request creation of a permanent MCX group from the participants in the ad hoc group call. + +This technical report identifies the key issues and corresponding solutions with recommendations for the normative work. + +# --- 1 Scope + +The present document studies solutions to satisfy the requirements identified to support Ad hoc group communication for MCX services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support Ad hoc group communications. Requirements for this study are taken from 3GPP TS 22.280 [3]. + +# --- 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.179: "Mission Critical Push to Talk (MCPTT); Stage 1". +- [3] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)". + +# --- 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]. + +**Ad hoc Group Communication:** The combining of a multiplicity of MCX Users into a group for the duration of a communication and when the communication is terminated the group no longer exists. + +For the purposes of the present document, the following terms given in 3GPP TS 22.280 [3] apply + +**MCX UE** +**MCX User** +**Mission Critical** +**Mission Critical Service** +**Functional alias** + +## 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 Key issues + +## 4.1 Key issue 1 – Ad hoc group communication + +The requirements for MCX service Ad hoc group communication are captured in 3GPP TS 22.280 [3] clause 6.15.5. + +Ad hoc group communication enables authorized MCX users to combine a random set of MCX Users into a group communication. The ad hoc group does not exist until it is spontaneously created during the communication and it ceases to exist once the communication is terminated. The participants of the ad hoc group communication may be served by the same or different MC systems. + +Hence it is required to study the following: + +- Procedures for establishing and release of the ad hoc group communication. +- Procedures for establishing the ad hoc group communication with end-to-end encryption support. +- Identify whether new information flows are required or existing information flows can be enhanced to support the ad hoc group communication set up. +- How to support different mechanisms for determining the participants list for the ad hoc group communication. It could be supplied by the initiator of the ad hoc group call or determined by the MCX system based on some pre-defined criteria. +- How to support a mechanism for the initiator of an MCX Service ad hoc group communication to request that the list of participants be determined and updated by the MCX Service system using a specific pre-defined criteria. +- Identify whether any changes are required to the existing MCX functional architecture for supporting the ad hoc group communication. + +## 4.2 Key issue 2 – Network topology hiding from MC service client while establishing Ad hoc group communication + +Ad hoc group communication enables authorized MCX users to combine a random set of MCX Users into a group communication. To best utilize the network resources, achieve best network performance and provide service resilience, a network operator normally deploys more than one MC service servers to serve its customers. This is applicable for all types of group communication and especially true in ad hoc group communications when it enables authorized users to combine a random set of MCX users into a group communication. This kind of deployment topology cannot be exposed and learned by the third party and only be controlled by the network operator. Ad hoc group is created spontaneously by the initiating client during the communication set up and therefore it leaves no choice for the network operators to decide on where to host the communication beforehand. + +Hence it is required to study the following: + +- How the group ID used for the ad hoc group communication can be created by MC service client and managed when establishing the ad hoc group communication. +- Whether and how to support the ad hoc group communication without exposing the network topology. + +- Whether and how to support the ad hoc group communication with dynamically allocated network resources (such as the MC service server that will host the communication). + +NOTE: This key issue also applies to existing specification of temporary groups creation by MC service client (e.g user regroup) + +## 4.3 Key issue 3 – Configuration parameters for Ad hoc group communication + +3GPP TS 22.280[3] has defined several requirements related to configuration of parameters required for ad hoc group communication by the administrator and initiator of the ad hoc group communication. Hence it is required to study the following : + +- Identify the required system or service level configuration parameters and document them. +- Identify the user level configuration parameters and document them. +- Identify the default parameters to be configured which will be applied when these parameters are not supplied as part of the ad hoc group communication request by the initiator. +- How the MCX server shall be able to determine whether the user is authorized to initiate ad hoc group communication. + +## 4.4 Key issue 4 – Modifying participants list of on-going ad hoc group communication + +During the course of an on-going ad hoc group communication, the initiator of the ad hoc group communication can be able to add or remove participants from the communication or the MCX system can add or remove participants based on some pre-defined criteria. This key issue is to identify the information flows and procedures required between the MCX client and MCX server to add/remove participants to/from an on-going ad hoc group communication. + +## 4.5 Key issue 5 – Ad hoc group emergency alert + +Ad hoc group emergency alert enables MC service users to send an MC service emergency alert also to an ad hoc group. The participants of the ad hoc emergency alert group may be served by multiple MC systems. + +It is required to study the following: + +- How the solution for the ad hoc group communication can be reused for the ad hoc group emergency alert. +- Procedures for initiating and cancelling an ad hoc group emergency alert. +- Support of a functional alias as target for sending an alert notification. +- Whether any new information flows are required or whether existing ad hoc group information flows can be enhanced to support ad hoc group emergency alerts. +- Whether the participants list for the ad hoc group emergency alert needs any modification compared to an ad hoc group communication. +- Whether any changes are required to the existing MC functional model to support the ad hoc group emergency alert. +- Clarify whether and which additional information along with the alert indication is useful. + +# --- 5 Architectural requirements + +NOTE: No architectural requirements were identified. + +# --- 6 Architectural enhancements + +NOTE: No architectural enhancements were identified. + +# --- 7 Solutions + +## 7.1 Solution 1: Ad hoc group communication set up for MCX service + +### 7.1.1 General + +This solution addresses the key issue 1 described in the clause 4.1 to support ad hoc group communication set up for MCX service. Information flows and procedures that are required to address the key issue 1 are addressed in this section. + +### 7.1.2 Information flows + +#### 7.1.2.1 Ad hoc group communication request (MC service client – MC service server) + +Table 7.1.2.1-1 describes the information flow ad hoc group communication request from the MC service client to the MC service server. + +**Table 7.1.2.1-1 Ad hoc Group communication request information elements** + +| Information Element | Status | Description | +|--------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service ad hoc group ID (see NOTE 1) | O | The MC service group ID which is generated by the MC service user to be associated with the ad hoc group communication | +| Encryption supported (see NOTE 2) | O | Indicates whether this ad hoc group communication supports end-to-end encryption | +| MC service ID list (see NOTE 3, NOTE 6) | O | MC service IDs of the participants being invited for the ad hoc group communication | +| SDP offer | M | Media parameters of MC service clients | +| Implicit floor request (see NOTE 4) | O | When originating client requests the floor, this element shall be included | +| Broadcast indicator | O | Indicates that the group communication request is for a broadcast group communication | +| Imminent peril indicator (see NOTE 5) | O | Indicates that the ad hoc group communication request is an MC service imminent peril communication | +| Emergency Indicator (see NOTE 5) | O | Indicates that the ad hoc group communication request is an MC service emergency communication | +| MC service ID list (see NOTE 3) | O | List of participants required to acknowledge the ad hoc group communication before start of the audio transmission | +| Block sharing participants list indicator (see NOTE 8) | O | Indicates that the participants shall be able to determine list of other participants or not | +| Location information | O | Location of the calling party. | +| Criteria for determining the participants (see NOTE 6) | O | Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MC service server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area | +| Preconfigured ad hoc group identity (see NOTE 7) | O | Group identity whose configuration is to be applied for this ad hoc group call. | +| Requested priority | O | Application priority level requested for this group communication | + +- NOTE 1: If this information element is not included the MC service server shall assign one to be used for the ad hoc group communication and shall return it to the calling party to use in the ad hoc group communication. +- NOTE 2: This information element shall be present and set to true only if this ad hoc group communication is encrypted. When the ad hoc group communication is initiated with participants provided by the initiator this acts as an indicator that subsequent requests shall follow targeting the individual participants and carrying the relevant key material. If this information element is set to false or not present, then this ad hoc group communication is unencrypted. +- NOTE 3: This element shall be included only when the originating client sends the list of participants. +- NOTE 4: This element shall be included only when the originating client requests the floor. +- NOTE 5: If used, only one of these information elements shall be present. +- NOTE 6: Only one of these information elements shall be present. +- NOTE 7: This information element shall be included if the criteria for inviting the participants information element is present and end-to-end encryption is supported. +- NOTE 8: This information element shall not be included if the criteria for inviting the participants information element is present. + +#### 7.1.2.2 Ad hoc group communication request return (MC service server – MC service client) + +Table 7.1.2.2-1 describes the information flow ad hoc group communication request return from the MC service server to the MC service client. + +**Table 7.1.2.2-1 Ad hoc group communication request return information elements** + +| Information Element | Status | Description | +|----------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| MC service ad hoc group ID | M | The MC service group ID to be associated with the ad hoc group communication which could be same as generated by the MC service client or assigned by the MC service server | +| Authorization result | M | Indicate if authorization is success or failure | + +#### 7.1.2.3 AHGC share security material command (MC service client – MC service server) + +Table 7.1.2.3-1 describes the information flow AHGC share security material command from the MC service client to MC service server. + +**Table 7.1.2.3-1 AHGC share security material command information elements** + +| Information Element | Status | Description | +|----------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service ad hoc group ID | M | The MC service group ID which is generated by the MC service user to be associated with the ad hoc group communication | +| MC service ID | M | The MC service ID of the user being invited for the ad hoc group communication | +| Security key material | M | Key material to be shared with the target participant for use with the ad hoc group communication if end-to-end encryption supported | + +#### 7.1.2.4 Ad hoc group communication request (MC service server – MC service client) + +Table 7.1.2.4-1 describes the information flow ad hoc group communication request from the MC service server to the MC service client. + +**Table 7.1.2.4-1 Ad hoc group communication request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service ad hoc group ID | M | The MC service group ID to be associated with the ad hoc group communication | +| SDP offer | M | Media parameters of MC service server | +| Security key material (see NOTE 1) | O | Key material for use with the ad hoc group communication if end-to-end encryption supported | +| Broadcast indicator | O | Indicates that the ad hoc group communication request is for a broadcast ad hoc group communication | +| Imminent peril indicator (see NOTE 2) | O | Indicates that the ad hoc group communication request is an MC service imminent peril communication | +| Emergency Indicator (see NOTE 2) | O | Indicates that the ad hoc group communication request is an MC service emergency communication | +| Preconfigured ad hoc group identity | O | Group identity whose configuration is to be applied for this ad hoc group call. | +| NOTE 1: This information element shall be present if the participants list is provided by the initiator and if end-to-end encryption is supported. | | | +| NOTE 2: If used, only one of these information elements shall be present. | | | + +#### 7.1.2.5 Ad hoc group communication response (MC service server – MC service client) + +Table 7.1.2.5-1 describes the information flow ad hoc group communication response from the MC service server to the MC service client. + +**Table 7.1.2.5-1 Ad hoc group communication response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service group ID | M | The MC service group ID to be associated with the ad hoc group communication | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group communication request (success or failure) | + +#### 7.1.2.6 Ad hoc group communication response (MC service client – MC service server) + +Table 7.1.2.6-1 describes the information flow ad hoc group communication response from the MC service client to the MC service server. + +**Table 7.1.2.6-1 Ad hoc group communication response information elements** + +| Information Element | Status | Description | +|----------------------------|--------|------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the target MC service user | +| Functional alias | O | The functional alias of the target MC service user | +| MC service ad hoc group ID | M | The MC service group ID to be associated with the ad hoc group communication | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the ad hoc group communication request (success or failure) | + +#### 7.1.2.7 Ad hoc group communication release request (MC service server – MC service client) + +Table 7.1.2.7-1 describes the information flow ad hoc group communication release request from the MC service server to the MC service client. + +**Table 7.1.2.7-1 Ad hoc group communication release request information elements** + +| Information Element | Status | Description | +|----------------------------|--------|----------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the ad hoc group communication participant | +| Functional alias | O | The functional alias of the ad hoc group communication participant | +| MC service ad hoc group ID | M | The MC service group ID of the ad hoc group communication on which communication is released | + +#### 7.1.2.8 Ad hoc group communication release response (MC service client – MC service server) + +Table 7.1.2.8-1 describes the information flow ad hoc group communication release response from the MC service server to the MC service client. + +**Table 7.1.2.8-1 Ad hoc group communication release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the ad hoc group communication participant | +| Functional alias | O | The functional alias of the ad hoc group communication participant | +| MC service group ID | M | The MC service group ID of the ad hoc group communication on which communication is released | + +#### 7.1.2.9 Ad hoc group communication get userlist (MC service server – MC service server) + +Table 7.1.2.9-1 describes the information flow ad hoc group communication get userlist from one MC service server to another MC service server. + +**Table 7.1.2.9-1: Ad hoc group communication get userlist** + +| Information element | Status | Description | +|-------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criteria for determining the participants | M | Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MC service server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area | + +#### 7.1.2.10 Ad hoc group communication get userlist response (MC service server – MC service server) + +Table 7.1.2.10-1 describes the information flow ad hoc group communication get userlist response from one MC service server to another MC service server. + +**Table 7.1.2.10-1: Ad hoc group communication get userlist response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------| +| MC service ID list | M | List of MC service IDs meeting the criteria specified in the ad hoc group communication get userlist | + +#### 7.1.2.11 Group Call Notify (MC service server – MC service client) + +Table 7.1.2.11-1 describes the information flow group call notify from MC service server to MC service client. + +**Table 7.1.2.11-1: Group Call Notify** + +| Information element | Status | Description | +|----------------------------------------------------|--------|------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service ad hoc group ID | M | The MC service group ID associated with the ad hoc group communication | +| MC service ID list (see NOTE) | O | The list of the invited MC service users who did not acknowledge the ad hoc group call request | +| NOTE: Only applicable to acknowledged group calls. | | | + +### 7.1.3 Procedure + +#### 7.1.3.1 Ad hoc group communication within one MC system + +##### 7.1.3.1.1 Ad hoc group communication setup + +Figure 7.1.3.1.1-1 below illustrates the ad hoc group communication setup procedure initiated by an authorized user. + +Pre-conditions: + +1. The authorized user at MC service client 1 wants to invite MC service users at MC service client 2, MC service client 3 and MC service client 4 for the ad hoc group communication. +2. Number of participants being invited for the communication is within the limit for non pre-configured approach. +3. End-to-End encryption is supported for this ad hoc group communication. +4. MC service client 1 is aware of the MC service IDs of the participants and has all the security related information required to communicate with the participants of the ad hoc group communication. + +NOTE: Selection of MC service IDs of the participants can be manual or from the user profile configuration data or by any other means. This is left for the implementation. + +![Sequence diagram for Ad hoc group communication setup. Lifelines: MC service client 1, MC service server, MC service client 2, MC service client 3, MC service client 4. The sequence starts with client 1 sending a request to the server, which authorizes and returns. Client 1 then sends security material commands to the server. The server then sends requests to clients 2, 3, and 4. Clients 2, 3, and 4 notify the server. The server then sends responses to clients 2, 3, and 4. Finally, the server sends a response and a group notify to client 1, and a media plane and floor control establishment message is sent to all participants.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server + participant MC service client 2 + participant MC service client 3 + participant MC service client 4 + + Note right of MC service server: 2. Authorise + + MC service client 1->>MC service server: 1. Ad hoc group communication request + MC service server-->>MC service client 1: 3. Ad hoc group communication request return + Note right of MC service server: 2. Authorise + MC service client 1->>MC service server: 4a. AHGC share security material command + MC service client 1-->>MC service server: 4b. AHGC share security material command + MC service client 1-->>MC service server: 4c. AHGC share security material command + MC service server->>MC service client 2: 5a. Ad hoc group communication request + MC service client 2->>MC service server: 5b. Ad hoc group communication request + MC service server->>MC service client 3: 5c. Ad hoc group communication request + MC service client 3->>MC service server: 6a.Notify ad hoc group communication + MC service server->>MC service client 4: 5c. Ad hoc group communication request + MC service client 4->>MC service server: 6c.Notify ad hoc group communication + MC service server->>MC service client 2: 7a. Ad hoc group communication response + MC service client 2->>MC service server: 7b. Ad hoc group communication response + MC service server->>MC service client 3: 7c. Ad hoc group communication response + MC service client 3->>MC service server: 7c. Ad hoc group communication response + MC service server->>MC service client 1: 8. Ad hoc group communication response + MC service client 1-->>MC service server: 9. Group Notify + Note right of MC service client 4: 10. Media plane and floor control establishment + +``` + +Sequence diagram for Ad hoc group communication setup. Lifelines: MC service client 1, MC service server, MC service client 2, MC service client 3, MC service client 4. The sequence starts with client 1 sending a request to the server, which authorizes and returns. Client 1 then sends security material commands to the server. The server then sends requests to clients 2, 3, and 4. Clients 2, 3, and 4 notify the server. The server then sends responses to clients 2, 3, and 4. Finally, the server sends a response and a group notify to client 1, and a media plane and floor control establishment message is sent to all participants. + +**Figure 7.1.3.1.1-1: Ad hoc group communication setup** + +1. User at MC service client 1 would like to initiate an ad hoc group communication. MC service client 1 initiates the ad hoc group communication by sending the ad hoc group communication request containing the list of participants to the MC service server. Encryption supported information element shall be set to true since end-to-end encryption is supported. The ad hoc group communication request may also contain block sharing participants list indicator information element set to true if the originating user want to suppress sharing of the participants list to other users. The ad hoc group communication request may include the MC service group ID that is created by the MC service client 1 or not include the MC service group ID that allow the MC service server to assign one for use. An SDP offer containing the MC service client media parameters is included. If there is a floor request to transmit, then the ad hoc group communication request contains an indication of an implicit floor request. If the MC service user of MC service client 1 has selected a functional alias, then the ad hoc group communication request contains that functional alias. If the ad hoc group communication request contains an implicit floor request it may also include location information. + +If the MC service user at MC service client 1 initiates an MC service emergency ad hoc group communication or the MC service emergency state is already set for the MC service client 1 (due to a previously triggered MC service emergency alert): + +- i. the MC service ad hoc group communication request shall contain an emergency indicator; +- ii. if the MC service emergency state is not set already, MC service client 1 sets its MC service emergency state. The MC service emergency state of MC service client 1 is retained until explicitly cancelled by the user of MC service client 1. + +2. The MC service server accepts the ad hoc group communication request if the ad hoc group communication is supported and authorized. Otherwise reject the ad hoc group communication request and do not continue with the rest of the steps. If authorised, it validates whether the number of invited participants is within the configured limit before proceeding with the communication setup. + +If functional alias is present, the MC service server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +If location information was included in the ad hoc group communication request, the MC service server checks the privacy policy of the MC service user to decide if the location information of MC service client 1 can be provided to other users on the communication (refer to Annex A.3 "Authorisation to provide location information to other MC service users on a communication when talking"). + +If an emergency indicator is present in the received MC service ad hoc group communication request, the MC service ad hoc group is considered to be in the in-progress emergency state until this ad hoc group communication is terminated; and + +If an imminent peril indicator is present in the received MC service ad hoc group communication request, the MC service ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group communication is terminated. + +The MC service server considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group. + +3. The MC service server shall send the ad hoc group communication request return message to MC service client 1 containing the below: + +- i. The MC service ad hoc group ID (e.g. either provided by MC service client 1 which is acceptable to the MC service server or generated by the MC service server in the case where the MC service ad hoc group ID created by the MC service client 1 is not acceptable or the case where the MC service ad hoc group ID was not provided by MC service client 1); and +- ii. Result of whether the ad hoc group communication is authorized or not + +If the ad hoc group communication request is not authorized, MC service client 1 shall not proceed with the rest of the steps. + +- 4a-4c. MC service client 1 sends AHGC share security material command targeting each of the participants containing the security material to be shared with the participants for use in this ad hoc group communication. + +NOTE 1: If end-to-end encryption is not supported, then the ad hoc group communication security material requests are not sent. + +- 5a-5c. The MC service server sends the ad hoc group communication requests towards the MC service clients of the invited users based on step 1. While sending the ad hoc group communication requests, the MC service server shall remove the information elements that are not required to be conveyed to the target MC service clients (e.g. Block sharing participants list indicator, MC service ID list of the users who are required to acknowledge) + +- 6a-6c. The receiving MC service clients are notified about the incoming ad hoc group communication. + +- 7a-7c. The receiving MC service clients accept the ad hoc group communication requests and send ad hoc group communication responses to the MC service server. The response may also contain a functional alias of the responding MC service user, which is verified (valid and activated for the user) by the MC service server. + +8. The MC service server sends the ad hoc group communication response to MC service client 1 through the signalling path to inform about successful communication establishment. + +NOTE 2: Steps 5 to step 7 can start to occur before all of step 4 is completed since the MC service server do not require to wait for the previous ad hoc group communication request to complete before sending the ad hoc group request to another participant. + +9. If the initiating MC service user requires the acknowledgement from the invited MC service users, and the required MC service users do not acknowledge the communication setup within a configured time (the "acknowledged communication setup timeout"), then the MC service server may proceed with or abandon the communication and then notify the initiating MC service user that the acknowledgements did not include all + +required members according to ad hoc group communication policy from the user profile configuration. The MC service server may notify the initiating MC service user of all MC service users who did not acknowledge the ad hoc group communication request within the configured time. This notification may be sent to the initiating MC service user by the MC service server more than once during the communication when MC service users join or leave the MC service ad hoc group communication. + +10. MC service client 1, MC service client 2, MC service client 3 and MC service client 4 establish media plane and floor control resources. + +NOTE 3: Step 10 can occur any time following step 8 if the conditions to proceed with the communication are met. + +##### 7.1.3.1.2 Release ad hoc group communication + +The procedure focuses on the case where the MC service server releases an ongoing MC service ad hoc group communication for all the participants of that ad hoc group communication, since at least one of the release conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving. + +Figure 7.1.3.1.2-1 below illustrates the signalling control plane procedure for the MC service server initiating termination an ongoing ad hoc group communication. + +![Sequence diagram titled 'Release ad hoc group communication' showing the interaction between MC service clients and the MC service server. The diagram starts with an ongoing ad hoc group call between clients 1, 2, and 3. The server initiates the release process by sending release requests to each client, notifying them, receiving responses, and finally releasing resources.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MC service client 1 + participant Server as MC service server + participant Client2 as MC service client 2 + participant Client3 as MC service client 3 + Note over Client1, Client3: 1. Ad hoc Group call ongoing between MC service client 1, client 2 and client 3 + Note over Server: 2. Release Ad hoc group call + Note over Server: 3. Determine Ad hoc group call participants and generate Ad hoc group call release + Server->>Client1: 4a. Ad hoc Group call release request + Note over Client1: 5a. Notify user + Client1->>Server: 6a. Ad hoc Group call release response + Server->>Client2: 4b. Ad hoc Group call release request + Note over Client2: 5b. Notify user + Client2->>Server: 6b. Ad hoc Group call release response + Server->>Client3: 4c. Ad hoc Group call release request + Note over Client3: 5c. Notify user + Client3->>Server: 6c. Ad hoc Group call release response + Note over Client1, Client3: 7. Releasing floor control and media plane resources associated with the Ad hoc group call + +``` + +Sequence diagram titled 'Release ad hoc group communication' showing the interaction between MC service clients and the MC service server. The diagram starts with an ongoing ad hoc group call between clients 1, 2, and 3. The server initiates the release process by sending release requests to each client, notifying them, receiving responses, and finally releasing resources. + +Figure 7.1.3.1.2-1: Release ad hoc group communication + +1. It is assumed that MC service users on MC service client 1, client 2 and client 3 are already part of the ongoing ad hoc group communication. + +2. MC service server would like to release the MC service ad hoc group communication which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving. +3. MC service server identifies the participants of the ongoing ad hoc group communication and generates ad hoc group communication release request to release ongoing session. The MC service server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group communication is an emergency or imminent peril communication respectively. +4. MC service server sends ad hoc group communication release request via SIP core towards each participant of the ongoing ad hoc group communication. +5. MC service users are notified about the release of the ad hoc group communication. +6. MC service client(s) receiving ad hoc group communication release request, acknowledge towards the MC service server by sending an ad hoc group communication release response. + +NOTE: If the participants list is not suppressed by the initiator of the ad hoc group communication, the MC service client(s) may choose to store the list of participants for easy re-initiation of another ad hoc group communication with the same participants. + +7. MC service client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the ad hoc group communication that is terminated and the ad hoc group ceases to exist (i.e., further communication is not possible over the same ad hoc group). + +##### 7.1.3.1.3 MC service server determining the participants list for the Ad hoc group communication setup + +Figure 7.1.3.1.3-1 below illustrates the ad hoc group communication setup procedure initiated by the MC service user and MC service client 1 wherein the list of participants is determined by the MC service server based on the criteria received from the MC service client. + +Pre-conditions: + +1. The MC service user at MC service client 1 is authorized to initiate ad hoc group communication. +2. The MC service user at MC service client 1 wants to invite MC service users who are satisfying certain criteria for the ad hoc group communication. + +![Sequence diagram illustrating the ad hoc group communication participant determination process. Lifelines: MC service Client 1, MC service server, MC service client 2, and MC service client 3. The process involves a request from Client 1, server authorization and participant determination, subsequent requests to other clients, their notifications and responses, and finally a group call notify and media plane establishment.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant Client 1 as MC service Client 1 + participant Server as MC service server + participant Client 2 as MC service client 2 + participant Client 3 as MC service client 3 + + Note right of Server: 4. Determine the list of participants to be invited for the call based on the rule-set specified in step 1 + + Client 1->>Server: 1. Ad hoc group communication request + Server-->>Server: 2. Authorize the request + Server-->>Client 1: 3. Ad hoc group communication request return + Server->>Client 2: 5a. Ad hoc Group communication request + Note right of Client 2: 6a. Notify adhoc group communication + Server->>Client 3: 5b. Ad hoc Group communication request + Note right of Client 3: 6b. Notify adhoc group communication + Client 2-->>Server: 7a. Ad hoc Group communication response + Client 3-->>Server: 7b. Ad hoc Group communication response + Server-->>Client 1: 8. Ad hoc Group communication response + Client 1-->>Client 1: 9. Group call notify + Note over Client 1, Server, Client 2, Client 3: 10. Media Plane and floor control establishment + +``` + +Sequence diagram illustrating the ad hoc group communication participant determination process. Lifelines: MC service Client 1, MC service server, MC service client 2, and MC service client 3. The process involves a request from Client 1, server authorization and participant determination, subsequent requests to other clients, their notifications and responses, and finally a group call notify and media plane establishment. + +**Figure 7.1.3.1.3-1: Ad hoc group communication participants determined by MC service server** + +- User at MC service client 1 would like to initiate an ad hoc group communication in-order to invite the participants satisfying specific criteria. MC service client 1 initiates the ad hoc group communication by sending the ad hoc group communication request containing the details of the criteria to be applied by the MC service server for determining the participants list. If end-to-end encryption is supported Encryption supported information element shall be set to true and pre-configured ad hoc group identity whose configuration is to be applied is included. The ad hoc group communication request may include the MC service group ID that is created by the MC service client 1 or not include the MC service group ID that allow the MC service server to assign one for use. An SDP offer containing the MC service client media parameters is included. If there is a floor request to transmit, then the ad hoc group communication request contains an indication of an implicit floor request. If the MC service user of MC service client 1 has selected a functional alias, then the ad hoc group communication request contains that functional alias. If the ad hoc group communication request contains an implicit floor request it may also include location information. + +If the MC service user at MC service client 1 initiates an MC service emergency ad hoc group communication or the MC service emergency state is already set for the MC service client 1 (due to a previously triggered MC service emergency alert): + +- the MC service ad hoc group communication request shall contain an emergency indicator; + +- ii. if the MC service emergency state is not set already, MC service client 1 sets its MC service emergency state. The MC service emergency state of MC service client 1 is retained until explicitly cancelled by the user of MC service client 1. +2. The MC service server accepts the ad hoc group communication request if the ad hoc group communication is supported and authorized. Otherwise reject the ad hoc group communication request and do not continue with the rest of the steps. + +If functional alias is present, the MC service server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +If location information was included in the ad hoc group communication request, the MC service server checks the privacy policy of the MC service user to decide if the location information of MC service client 1 can be provided to other users on the communication (refer to Annex A.3 "Authorisation to provide location information to other MC service users on a communication when talking"). + +If an emergency indicator is present in the received MC service ad hoc group communication request, the MC service ad hoc group is considered to be in the in-progress emergency state until this ad hoc group communication is terminated; and + +If an imminent peril indicator is present in the received MC service ad hoc group communication request, the MC service ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group communication is terminated. + +3. The MC service server shall send the ad hoc group communication request return message to MC service client 1 containing the below: + - i. The MC service ad hoc group ID (e.g. either provided by MC service client 1 which is acceptable to the MC service server or generated by the MC service server in the case where the MC service ad hoc group ID created by the MC service client 1 is not acceptable or the case where the MC service ad hoc group ID was not provided by MC service client 1); and + - ii. Result of whether the ad hoc group communication is authorized or not + +If the ad hoc group communication request is not authorized, MC service server and client 1 shall not proceed with the rest of the steps. + +4. The MC service server determines the list of participants to be invited for the ad hoc group communication based on the information present in the information element Criteria for determining the participants. This information element could carry either criteria or indicator identifying the criteria or combination of both. +5. The MC service server sends the ad hoc group communication requests towards the MC service clients 2 and 3. While sending the ad hoc group communication requests, the MC service server shall remove the information elements that are not required to be conveyed to the target MC service clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group communication if end-to-end encryption is requested. The MC service server considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group. +6. The receiving MC service clients are notified about the incoming ad hoc group communication. +7. The receiving MC service clients accept the ad hoc group communication requests and send ad hoc group communication responses to the MC service server. The response may also contain a functional alias of the responding MC service user, which is verified (valid and activated for the user) by the MC service server. +8. The MC service server sends the ad hoc group communication response to MC service client 1 through the signalling path to inform about successful communication establishment. +9. The MC service server may notify the initiating MC service user of all MC service users who acknowledged the ad hoc group communication request and joined the ad hoc group communication. This notification may be sent to the initiating MC service user by the MC service server more than once during the communication when MC service users join or leave the MC service ad hoc group communication. +10. MC service client 1, MC service client 2 and MC service client 3 establish media plane and floor control resources. + +#### 7.1.3.2 Ad hoc group communication involving multiple MC system + +##### 7.1.3.2.1 Ad hoc group communication setup – Participants list provided by the initiator + +Figure 7.1.3.2.1-1 below illustrates the ad hoc group communication setup procedure initiated by an authorized user involving the MC service users from multiple MC system. + +Pre-conditions: + +1. The authorized user at MC service client 1 wants to invite MC service users at MC service client 2, MC service client 3 and MC service client 4 for the ad hoc group communication. +2. MC service client 1 and MC service client 2 are registered to the MC service provider 1. MC service client 3 and MC service client 4 are registered to MC service provider 2. +3. Number of participants being invited for the communication is within the limit. +4. End-to-End encryption is supported for this ad hoc group communication. +5. MC service client 1 has all the security related information required to communicate with the participants of the ad hoc group communication. + +![Sequence diagram illustrating the ad hoc group communication setup involving multiple MC systems. The diagram shows interactions between MC service clients (1, 2, 3, 4) and MC service servers (1 primary, 2 partner) across two MC service providers. The process involves a request from client 1, authorization, security material sharing, and subsequent requests to other clients via their respective servers, leading to notifications and responses, and finally media plane establishment.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server 1 (primary) + participant MC service client 2 + participant MC service server 2 (partner) + participant MC service client 3 + participant MC service client 4 + + Note over MC service client 1, MC service client 4: MC service provider 1 | MC service provider 2 + + MC service client 1->>MC service server 1: 1. Ad hoc group communication request + MC service server 1-->>MC service client 1: 2. Authorise + MC service server 1-->>MC service client 1: 3. Ad hoc group communication request return + MC service client 1->>MC service server 1: 4a. AHGC share security material command + MC service client 1->>MC service server 1: 4b. AHGC share security material command + MC service client 1->>MC service server 1: 4c. AHGC share security material command + MC service server 1->>MC service client 2: 5a. Ad hoc group communication request + MC service server 1->>MC service server 2: 5b. Ad hoc group communication request + MC service server 1->>MC service server 2: 5c. Ad hoc group communication request + MC service server 2->>MC service client 3: 6a. Ad hoc group communication request + MC service server 2->>MC service client 4: 6b. Ad hoc group communication request + MC service client 2->>MC service server 1: 7a. Notify ad hoc group communication + MC service server 2->>MC service client 3: 7b. Notify ad hoc group communication + MC service server 2->>MC service client 4: 7c. Notify ad hoc group communication + MC service client 2->>MC service server 1: 8. Ad hoc group communication response + MC service server 2->>MC service client 3: 9a. Ad hoc group communication response + MC service server 2->>MC service client 4: 9b. Ad hoc group communication response + MC service server 1->>MC service client 3: 10a. Ad hoc group communication response + MC service server 1->>MC service client 4: 10b. Ad hoc group communication response + MC service client 1->>MC service server 1: 11. Ad hoc group communication response + MC service server 1-->>MC service client 1: 12. Group Call Notify + Note over MC service client 1, MC service client 4: 13. Media plane and floor control establishment + +``` + +Sequence diagram illustrating the ad hoc group communication setup involving multiple MC systems. The diagram shows interactions between MC service clients (1, 2, 3, 4) and MC service servers (1 primary, 2 partner) across two MC service providers. The process involves a request from client 1, authorization, security material sharing, and subsequent requests to other clients via their respective servers, leading to notifications and responses, and finally media plane establishment. + +**Figure 7.1.3.2.1-1: Ad hoc group communication setup involving multiple MC systems** + +1-5a. Same as described in sub-clause 7.1.3.1.1. + +5b-5c. The MC service server sends the ad hoc group communication requests for MC service client 3 and MC service client 4 to the MC service server 2. While sending the ad hoc group communication requests, the MC service server shall remove the information elements that are not required to be conveyed to the target MC service clients (e.g. Block sharing participants list indicator, MC service ID list of the users who are required to acknowledge) and shall include the security key material as received in steps 4b and 4c. + +- 6a-6b. The MC service server 2 forwards the ad hoc group communication requests to the MC service client 3 and MC service client 4. +- 7a-7c. The receiving MC service clients are notified about the incoming ad hoc group communication. +- 8. The MC service client 2 accept the ad hoc group communication request and send ad hoc group communication response to the MC service server 1. +- 9a-9b. The MC service client 3 and MC service client 4 accepts the ad hoc group communication request and sends ad hoc group communication responses to the MC service server 2. +- 10a-10b. The MC service server 2 forwards the responses to the MC service server 1. +- 11. The MC service server sends the ad hoc group communication response to MC service client 1 through the signalling path to inform about successful communication establishment. +- 12. The MC service server may notify the initiating MC service user of all MC service users who acknowledged the ad hoc group communication request and joined the ad hoc group communication. This notification may be sent to the initiating MC service user by the MC service server more than once during the communication when MC service users join or leave the MC service ad hoc group communication. +- 13. MC service client 1, MC service client 2, MC service client 3 and MC service client 4 establish media plane and floor control resources. + +NOTE: How to handle the end-to-end encryption when the MC service client 1 does not have the required security related information to communicate with the participants of the ad hoc group communication is in the scope of SA3. + +##### 7.1.3.2.2 Ad hoc group communication setup – Participants list determined by the MC service server + +Figure 7.1.3.2.2-1 below illustrates the ad hoc group communication setup procedure initiated by an authorized user wherein the list of participants is determined by the MC service server based on the criteria received from the MC service client and determined MC service users are from multiple MC systems. + +Pre-conditions: + +- 1. The MC service user at MC service client 1 is authorized to initiate ad hoc group communication. +- 2. End-to-End encryption is supported for this ad hoc group communication. + +![Sequence diagram showing ad hoc group communication setup involving multiple MC systems. The diagram illustrates the interaction between MC service clients (1, 2, 3, 4) and MC service servers (1 primary, 2 partner) across two MC service providers. The process involves a request from client 1 to server 1, authorization, participant list determination, user list requests between servers, and subsequent communication requests and responses to the clients, culminating in media plane establishment.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server 1 (primary) + participant MC service client 2 + participant MC service server 2 (partner) + participant MC service client 3 + participant MC service client 4 + + Note over MC service provider 1: MC service provider 1 + Note over MC service provider 2: MC service provider 2 + + MC service client 1->>MC service server 1: 1. Ad hoc group communication request + MC service server 1->>MC service client 1: 2. Authorise + MC service server 1->>MC service client 1: 3. Ad hoc group communication request return + Note right of MC service server 1: 4. Determine the list of participants to be invited for the call based on the rule-set specified in step 1 + MC service server 1->>MC service server 2: 5. Ad hoc group communication get userlist + MC service server 2->>MC service server 1: 6. Ad hoc group communication get userlist response + MC service server 1->>MC service server 2: 7. Ad hoc group communication request + MC service server 2->>MC service client 3: 8a. Ad hoc group communication request + MC service server 2->>MC service client 4: 8b. Ad hoc group communication request + Note right of MC service server 1: 10a. Notify ad hoc group communication + Note right of MC service server 2: 10b. Notify ad hoc group communication + Note right of MC service client 4: 10c. Notify ad hoc group communication + MC service client 2->>MC service server 1: 11. Ad hoc group communication response + MC service server 2->>MC service client 3: 12a. Ad hoc group communication response + MC service server 2->>MC service client 4: 12b. Ad hoc group communication response + MC service server 1->>MC service client 2: 13a. Ad hoc group communication response + MC service server 1->>MC service client 2: 13b. Ad hoc group communication response + MC service server 1->>MC service client 1: 14. Ad hoc group communication response + MC service client 1-->>MC service server 1: 15. Group Call Notify + Note over all participants: 16. Media plane and floor control establishment + +``` + +Sequence diagram showing ad hoc group communication setup involving multiple MC systems. The diagram illustrates the interaction between MC service clients (1, 2, 3, 4) and MC service servers (1 primary, 2 partner) across two MC service providers. The process involves a request from client 1 to server 1, authorization, participant list determination, user list requests between servers, and subsequent communication requests and responses to the clients, culminating in media plane establishment. + +**Figure 7.1.3.2.2-1: Ad hoc group communication setup involving multiple MC systems** + +- 1-4. Same as described in sub-clause 7.1.3.1.3. +5. MC service server 1 if it needs to involve the partner system based on the agreement and based on the criteria for determining the participants list, sends the ad hoc group communication get userlist request to the MC service server 2. This request carries the criteria specified in the step 1 . +6. MC service server 2 evaluates the criteria and determines the participants satisfying the criteria and sends the response containing the list of MC service users satisfying the criteria +7. The MC service server 1 sends the ad hoc group communication request towards the MC service server 2. This request carries the list of MC service users who needs to be invited for this ad hoc group communication and are registered with MC service server 2. It also carries the pre-configured group ID whose configuration is to be applied for this ad hoc group communication if end-to-end encryption is requested. +- 8a-8b. The MC service server 2 sends the ad hoc group communication request towards the MC service client 3 and MC service client 4. +9. The MC service server 1 sends the ad hoc group communication requests towards the MC service client 2. While sending the ad hoc group communication request, the MC service server shall remove the information elements that are not required to be conveyed to the target MC service clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group communication if end-to-end encryption is requested. The MC service server considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group. + +- 10a-10c. The receiving MC service clients are notified about the incoming ad hoc group communication. +- 11. The MC service client 2 accept the ad hoc group communication request and send ad hoc group communication response to the MC service server 1. +- 12a-12b. The MC service client 3 and MC service client 4 accepts the ad hoc group communication request and sends ad hoc group communication responses to the MC service server 2. +- 13a-13b. The MC service server 2 forwards the responses to the MC service server 1. +- 14. The MC service server 1 sends the ad hoc group communication response to MC service client 1 through the signalling path to inform about successful communication establishment. +- 15. The MC service server 1 may notify the initiating MC service user of all MC service users who acknowledged the ad hoc group communication request and joined the ad hoc group communication. This notification may be sent to the initiating MC service user by the MC service server 1 more than once during the communication when MC service users join or leave the MC service ad hoc group communication. +- 16. MC service client 1, MC service client 2, MC service client 3 and MC service client 4 establish media plane and floor control resources. + +### 7.1.4 Solution Evaluation + +The procedures proposed as part of this solution handles the ad hoc group communication setup and release as per the key issue 1. It also achieves the end-to-end security as per the stage-1 requirements. This solution introduces a new set of information flows required for ad hoc group communication. It also proposes a mechanism for the ad hoc group communication setup wherein the participants of the communication is determined by the MC service server based on the criteria which is either pre-defined or supplied by the initiator of the communication. + +Further the proposed solutions provide flexibility for the deployments to use the ad hoc group ID provided by the MC service client or the MC service server can generate and share the same to the initiator of the ad hoc group communication. This solution may require additional deployment considerations e.g. to configure the maximum number of participants allowed to participate in an ad hoc group communication, to meet the Stage 1 group call KPIs. + +The procedures proposed as part of this solution implicitly handles the Key issue #2 related to network topology hiding from MC service client while establishing Ad hoc group communication by having the ad hoc group ID generated by the MC service server. + +## 7.2 Solution 2: Ad hoc group call involving multiple MC systems + +### 7.2.1 General + +This solution pertains to key issue#1. The key characteristics of ad hoc group call are the following: + +- The ad hoc group does not exist until it is spontaneously created during the ad hoc group call setup. +- The ad hoc group ceases to exist when the communication terminates with the ad hoc group call release. + +### 7.2.2 Solution description + +#### 7.2.2.1 Procedures + +##### 7.2.2.1.1 Procedure for ad hoc group call setup + +Figure 7.2.2.1.1-1 illustrates the procedure for ad hoc group call setup procedure. + +Pre-conditions: + +- 1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MC system does not share their users' information to the primary MC system. + +2. The authorized MC service user/dispatcher belongs to the primary MC system. +3. The MC service server of the primary MC system is where the authorized MC service user/dispatcher creates the ad hoc group. +4. Some users of the ad hoc group may belong to partner MC systems. +5. The ad hoc group identity and ad hoc group configuration for an ad hoc group have been preconfigured in MC service client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication. +6. The call initiating MC service client is aware of a suitable preconfigured ad hoc group whose configuration has been preconfigured in the MC service UEs who are the participants of the ad hoc group. + +![Sequence diagram illustrating the ad hoc group call setup process. The diagram shows interactions between an MC service client (Authorized MC service user), MC service server (Primary), MC service client 1..N (Primary), MC service server (Partner), and MC service client 1..N (Partner). The steps are: 1. Group call request from Authorized user to Primary server; 2. Authorization check and ad hoc group formation (internal to Primary server); 3. Group call request from Primary server to Primary clients; 4. Group call response from Primary clients to Primary server; 5. Group call request from Primary server to Partner server; 6. Group call request from Partner server to Partner clients; 7. Group call response from Partner clients to Partner server; 8. Group call response from Partner server to Primary server; 9. Group call response from Primary server to Authorized user; 10. Media plane and floor control establishment (across all participants).](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MC service client (Authorized MC service user) + participant Server1 as MC service server (Primary) + participant ClientN1 as MC service client 1..N + participant Server2 as MC service server (Partner) + participant ClientN2 as MC service client 1..N + + Note right of Server1: 2. Authorization check and ad hoc group formation + + Client1->>Server1: 1. Group call request + Server1->>Server1: 2. Authorization check and ad hoc group formation + Server1->>ClientN1: 3. Group call request + ClientN1->>Server1: 4. Group call response + Server1->>Server2: 5. Group call request + Server2->>ClientN2: 6. Group call request + ClientN2->>Server2: 7. Group call response + Server2->>Server1: 8. Group call response + Server1->>Client1: 9. Group call response + Note over Client1, Server1, ClientN1, Server2, ClientN2: 10. Media plane and floor control establishment + +``` + +Sequence diagram illustrating the ad hoc group call setup process. The diagram shows interactions between an MC service client (Authorized MC service user), MC service server (Primary), MC service client 1..N (Primary), MC service server (Partner), and MC service client 1..N (Partner). The steps are: 1. Group call request from Authorized user to Primary server; 2. Authorization check and ad hoc group formation (internal to Primary server); 3. Group call request from Primary server to Primary clients; 4. Group call response from Primary clients to Primary server; 5. Group call request from Primary server to Partner server; 6. Group call request from Partner server to Partner clients; 7. Group call response from Partner clients to Partner server; 8. Group call response from Partner server to Primary server; 9. Group call response from Primary server to Authorized user; 10. Media plane and floor control establishment (across all participants). + +**Figure 7.2.2.1.1-1: Ad hoc group call setup** + +1. The MC service client of authorized user initiates a group call with multiple users from primary and partner MC systems. A group call request message with the information of the MC service IDs and the pre-configured ad hoc group is routed to the MC service server of the primary MC system. +2. The MC service server of the primary MC system forms the ad hoc group by using MC service users' information and the configuration of the preconfigured ad hoc group received in step 1 and assigns a MC service group ID for the newly formed ad hoc group. It identifies the appropriate MC service server responsible for the MC service users of the ad hoc group. The MC service users are automatically affiliated to the ad hoc group. + +NOTE 1: The newly formed ad hoc group information including the MC service group ID and the list of users is held in dynamic data in the MC service server. + +3. The MC service server of the primary MC system sends the group call request to the affiliated group members of the ad hoc group belonging to the primary MC system. +4. The MC service clients receive in the group call request the information of the MC service group ID for the ad hoc group and further notify their corresponding MC service user. The affiliated group members of the ad hoc group of the primary MC system may accept or reject the call and respond with the group call response. +5. The primary MC service server further initiates a group call request message to the MC service server of the partner MC system for the ad hoc group's MC service users' belonging to partner MC system. +6. Upon receiving the group call request message from the MC service server of the primary MC system, the MC service server of the partner MC system initiates a call invitation to its MC service users and sends the group call request to the MC service users of the partner MC system. + +7. The MC service clients receive in the group call request the information of the MC service group ID for the ad hoc group and further notify their corresponding MC service user. The MC service users upon receipt of the invitation may accept or reject the call, and respond with the group call response. +8. The MC service server of the partner MC system provides a group call response message to the MC service server of the primary MC system with success or failure result and/or detailed reason information in case of failure. +9. The MC service server of the primary MC system provides a group call response message to the MC service client of the authorized MC service user upon receiving response to the corresponding group call request with the MC service server of the partner MC system. The group call response will consist of the success or failure result and/or detailed reason information in case of failure. The MC service client 1 receives the MC service group ID assigned for the ad hoc group via this step. + +NOTE 2: The group call response message is triggered depending on the conditions to proceed with the call. + +10. Upon successful group call setup, a group call is established amongst the multiple group members from primary and partner MC systems. The media plane and floor control resources are established. + +##### 7.2.2.1.2 Procedure for ad hoc group call release + +This procedure focuses on the case where an MC service server initiates the termination of an ongoing MC service ad hoc group call for all the participants of that group call, since at least one of the termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MC service group members are not present. + +Procedures in figure 7.2.2.2-1 are the signalling control plane procedures for the MC service server initiating termination of an ongoing MC service ad hoc group call. + +![Sequence diagram for Ad hoc group call release. Lifelines: MC service client 1, MC service server (Primary), MC service client 2, MC service server (Partner), MC service client 3. The process starts with an ongoing ad hoc group call. The Primary server initiates release, determines participants, and sends release requests. Clients are notified and send responses. Finally, resources are released and information is removed.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant C1 as MC service client 1 + participant S1 as MC service server (Primary) + participant C2 as MC service client 2 + participant S2 as MC service server (Partner) + participant C3 as MC service client 3 + + Note over C1, C3: 1. Ad hoc group call ongoing between MCPTT client 1, client 2 and client 3 + S1->>S1: 2. Release group call + S1->>S1: 3. Determine group call participants and generate group call release + S1->>C1: 4. Group call release request + S1->>C2: 4. Group call release request + S1->>S2: 4. Group call release request + S2->>C3: 4. Group call release request + C1->>S1: 5. Notify user + C2->>S1: 5. Notify user + C3->>S2: 5. Notify user + C1->>S1: 6. Group call release response + C2->>S1: 6. Group call release response + C3->>S2: 6. Group call release response + Note over C1, C3: 7. Releasing floor control and media plane resources associated with the group call and remove the related ad hoc group information + +``` + +Sequence diagram for Ad hoc group call release. Lifelines: MC service client 1, MC service server (Primary), MC service client 2, MC service server (Partner), MC service client 3. The process starts with an ongoing ad hoc group call. The Primary server initiates release, determines participants, and sends release requests. Clients are notified and send responses. Finally, resources are released and information is removed. + +**Figure 7.2.2.2-1: Ad hoc group call release** + +1. It is assumed that MC service users on MC service client 1, client 2 belonging to primary MC system and client 3 belonging to partner MC system are already part of the ongoing ad hoc group call (e.g. as a result of ad hoc group call setup as specified in clause 7.2.2.1.1). +2. The MC service server would like to release the MC service group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MC service group members are not present. +3. The MC service server identifies the participants of the ongoing ad hoc group call and generates group call release request to release ongoing session. +4. The MC service server sends a group call release request via SIP core towards each participant of the ongoing group call. If the participants belong to partner MC system, then group call release request is sent to the partner MC service server, which further sends the group call release request to the MC service clients. +5. The MC service users are notified about the release of the ad hoc group call. +6. The MC service client(s) receiving group call release request, send acknowledgement towards the MC service server by sending a group call release response. +7. The MC service client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the group call that is terminated. The MC service servers remove the ad hoc group information from the dynamic data held in the MC service servers and thus the ad hoc group ceases to exist. + +#### 7.3.2.1 Information Flows + +##### 7.3.2.1.1 Group call request (MC service client – MC service server) + +Table 7.3.2.1.1-1 describes the information flow group call request from the MC service client to the MC service server. The group call request information flow specified in MC service specifications is to be updated accordingly as shown in **bold**. + +**Table 7.3.2.1.1-1 Group call request information elements** + +| Information Element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service group ID
(see NOTE 1) | O | The MC service group ID of the group on which the call is requested | +| MC service ID list
(see NOTE 2) | O | The list of MC service IDs on which the group call is requested. | +| Preconfigured ad hoc group identity
(see NOTE 2) | O | Ad hoc group identity whose configuration is to be applied on the group call. | +| SDP offer | M | Media parameters of MC PTT clients | +| Implicit floor request | O | When originating client requests the floor, this element shall be included | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Location information | O | Location of the calling party. | +| Requested priority | O | Application priority level requested for this call | +| NOTE 1: This IE may be included when the group call is an ad hoc group call. This IE is always included for other group calls | | | +| NOTE 2: These IEs are included when the group call is an ad hoc group call. | | | + +##### 7.3.2.1.2 Group call request (MC service server – MC service server) + +Table 7.3.2.1.2-1 describes the information flow group call request between the MC service servers. The group call request information flow specified in MC service specifications is to be updated accordingly as shown in **bold**. + +**Table 7.3.2.1.2-1 Group call request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service group ID
(see NOTE 3) | M | The MC service group ID of the group on which the call is initiated | +| MC service ID list
(see NOTE 2) | O | The list of MC service IDs of ad hoc group's MC service users' belonging to partner MC system on which the group call is requested. | +| Preconfigured ad hoc group identity
(see NOTE 2) | O | Ad hoc group identity whose configuration is to be applied on the group call. | +| SDP offer | M | Media parameters of MC service server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Implicit floor request
(see NOTE 1) | O | Indicates that the originating client requests the floor. | +| Requested priority | O | Priority level requested for the call. | +| Location information | O | Location of the calling party | +| NOTE 1: This element shall be included only when the originating client requests the floor. | | | +| NOTE 2: These IEs are included when the group call request is for ad hoc group call. | | | +| NOTE 3: If Preconfigured ad hoc group identity IE or MC service ID list is included then MC service group ID IE indicates the MC service group ID of the ad hoc group. | | | + +##### 7.3.2.1.3 Group call request (MC service server – MC service client) + +Table 7.3.2.1.3-1 describes the information flow group call request from the MC service server to the MC service client. The group call request information flow specified in MC service specifications is to be updated accordingly as shown in **bold**. + +**Table 7.3.2.1.3-1 Group call request information elements** + +| Information Element | Status | Description | +|------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service group ID | M | The MC service group ID of the group on which the call is initiated. | +| Preconfigured ad hoc group identity
(see NOTE 1) | O | Ad hoc group identity whose configuration is to be applied on the group call. | +| SDP offer | M | Media parameters of MC service server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| NOTE 1: This IE is included when the group call request is for ad hoc group call. | | | + +##### 7.3.2.1.4 Group call response (MC service server – MC service client) + +Table 7.3.2.1.4-1 describes the information flow group call response from the MC service server to the MC service client. No change is expected to the group call response information flow specified in MC service specifications. + +**Table 7.3.2.1.4-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service group ID | M | The MC service group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +##### 7.3.2.1.5 Group call response (MC service server – MC service server) + +Table 7.3.2.1.5-1 describes the information flow group call response between the MC service servers. No change is expected to the group call response information flow specified in MC service specifications. + +**Table 7.3.2.1.5-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the target MC service group member | +| Functional alias | O | The functional alias of the target MC service group member | +| MC service group ID | M | The MC service group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +##### 7.3.2.1.6 Group call response (MC service client – MC service server) + +Table 7.3.2.1.6-1 describes the information flow group call response from the MC service client to the MC service server. No change is expected to the group call response information flow specified in MC service specifications. + +**Table 7.3.2.1.6-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the target MC service group member | +| Functional alias | O | The functional alias of the target MC service group member | +| MC service group ID | M | The MC service group ID of the group on which the call is initiated | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +### 7.3.3 Solution Evaluation + +This is a viable solution to setup and release an ad hoc group call where the ad hoc group is created during the group call setup and the ad hoc group is removed when the group call is released thus the ad hoc group ceases to exist. This procedure achieves the required performance and security as per the stage 1 requirements for a group call. The group call security is achieved via the use of a preconfigured ad hoc group information and its group security information is applied on the ad hoc group call. + +## 7.3 Solution 3: Configuration parameters required for Ad hoc group communication + +### 7.3.1 General + +This solution addresses the key issue 3 described in clause 4.3 on configuration parameters required for supporting ad hoc group communication. This clause identifies the list of configuration parameters and which category of the configuration data they belong to. + +### 7.3.2 MC service configuration data + +Table 7.3.2-1 describes MCPTT service configuration data required for the ad hoc group communication. + +**Table 7.3.2-1: MCPTT service configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT server | Configuration management server | +|-----------------------------------------|----------------------------------------------------------------------------------------|----------|--------------|---------------------------------| +| [R-6.15.5.3-005] of 3GPP TS 22.280 [17] | Support of ad hoc group call | Y | Y | Y | +| [R-6.15.5.3-002] of 3GPP TS 22.280 [17] | Maximum number of participants allowed to participate in an ad hoc group communication | Y | Y | Y | +| [R-6.15.5.3-004] of 3GPP TS 22.280 [17] | Hang timer for ad hoc group communication | N | Y | Y | +| | Maximum duration for ad hoc group communication | Y | Y | Y | +| | List of preferred voice codecs for ad hoc group call | Y | Y | Y | + +### 7.3.3 MC service user profile configuration data + +Table 7.3.3-1 describes MCPTT user profile configuration data required for the ad hoc group communication. + +**Table 7.3.3-1: MCPTT user profile configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT server | Configuration management server | MCPTT user database | +|-----------------------------------------|-----------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| | Permissions related to ad hoc group communication | | | | | +| [R-6.15.5.3-001] of 3GPP TS 22.280 [17] | > Authorised to initiate ad hoc group call | Y | Y | Y | Y | +| R-6.15.5.3-003] of 3GPP TS 22.280 [17] | > Authorised to participate in ad hoc group call | Y | Y | Y | Y | +| | > Authorised to initiate emergency ad hoc group call | Y | Y | Y | Y | +| | > Authorised to initiate imminent peril ad hoc group call | Y | Y | Y | Y | + +### 7.3.4 Solution Evaluation + +This solution provides additional configuration parameters that are required to support MCX ad hoc group communication procedures. Parameters proposed as part of this solution are based on the requirements specified in 3GPP TS 22.280 [3]. + +## 7.4 Solution 4: Modifying participants list of on-going ad hoc group communication + +### 7.4.1 General + +This solution addresses the key issue 4 described in clause 4.4 on Modifying participants list of on-going ad hoc group communication. Information flows and procedures that are required to address the key issue 4 are addressed in this section. + +### 7.4.2 Information flows + +#### 7.4.2.1 Modify ad hoc Group call participants request (MC service client – MC service server) + +Table 7.4.2.1-1 describes the information flow Modify ad hoc Group call participants request from the MC service client to the MC service server. + +**Table 7.4.2.1-1 Modify ad hoc group call participants request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service ad hoc group ID | M | The MC service group ID of ad hoc group call whose participants list needs to be modified | +| MC service ID list (see NOTE 1) | O | List of additional MC service users to be added to the on-going ad hoc group call | +| MC service ID list (see NOTE 1) | O | List of MC service users to be removed from the on-going ad hoc group call | +| NOTE 1 : Either one or both of these elements shall be present | | | + +#### 7.4.2.2 Modify ad hoc group call participants response (MC service server – MC service client) + +Table 7.4.2.2-1 describes the information flow Modify ad hoc group call participants response from the MC service server to the MC service client. + +**Table 7.4.2.2-1 Modify Ad hoc group call participants response information elements** + +| Information Element | Status | Description | +|----------------------------|--------|--------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MC service ad hoc group ID | M | The MC service group ID of ad hoc group call whose participants list needs to be modified | +| Result | M | Result of the modify ad hoc group call participants request (success or failure) | +| MC service ID list | O | List of MC service users who are not allowed to be added to the on-going ad hoc group call | + +#### 7.4.2.3 Ad hoc group call leave request (MC service server – MC service client) + +Table 7.4.2.3-1 describes the information flow ad hoc group call leave request from the MC service server to the MC service client. + +**Table 7.4.2.3-1 Ad hoc group call leave request information elements** + +| Information Element | Status | Description | +|----------------------------|--------|-------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the ad hoc group call participant leaving the call | +| MC service ad hoc group ID | M | The MC service group ID of ad hoc group call on which call is on-going | +| Reason to leave | O | Carries the reason of why the MC service client is being asked to leave the ongoing ad hoc group call | + +#### 7.4.2.4 Ad hoc group call leave response (MC service client – MC service server) + +Table 7.4.2.4-1 describes the information flow Ad hoc group call leave response from the MC service client to the MC service server. + +**Table 7.4.2.4-1 Ad hoc group call leave response information elements** + +| Information Element | Status | Description | +|----------------------------|--------|-------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the ad hoc group call participant leaving the call | +| MC service ad hoc group ID | M | The MC service group ID of ad hoc group call on which call is on-going | + +### 7.4.3 Procedure + +#### 7.4.3.1 Modification of ad hoc group communication participants by the initiator + +Figure 7.4.3.1-1 below illustrates the modification of ad hoc group communication participants procedure by the initiator of the ad hoc group communication. + +Pre-conditions: + +1. The MC service client 1 is the initiator of the ad hoc group communication. +2. The MC service users on MC service client 1, MC service client 3 to MC service client n are on an ongoing ad hoc group communication. +3. The MC service user 1 requests to remove the user of MC service client 3 from the ad hoc group communication and add user of MC service client 2 into the on-going ad hoc group communication. + +![Sequence diagram illustrating the modification of ad hoc group communication participants by the initiator. The diagram shows interactions between MC service client 1, MC service server, MC service client 3, MC service client n, and MC service client 2. The process involves a modify request, authorization, a leave request for client 3, user notification, a leave response, removal of client 3, a security material command, a new group request for client 2, another user notification, a group call notify, and a final participant notification.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server + participant MC service client 3 + participant MC service client n + participant MC service client 2 + + Note over all participants: Ad hoc group communication is established and on-going + + MC service client 1->>MC service server: 1. Modify Ad hoc Group communication participants request + MC service server-->>MC service client 1: 2. Authorize the request + MC service server-->>MC service client 1: 3. Modify Ad hoc Group communication participants response + MC service server->>MC service client 3: 4. Ad hoc Group communication leave request + Note right of MC service client 3: 5. Notify user + MC service client 3-->>MC service server: 6. Ad hoc Group Call leave response + Note right of MC service server: 7. MC service client 3 is removed from the ongoing ad hoc group call + MC service client 1-->>MC service server: 8.AHGC share security material command + MC service server->>MC service client 2: 9. Ad hoc Group communication request + Note right of MC service client 2: 10. Notify ad hoc group ccommunication + MC service server-->>MC service client 1: 11. Ad hoc Group communication response + MC service client 1-->>MC service server: 12. Group Call Notify + Note over all participants: 13. Notify participants of the on-going ad hoc group communication regarding the change in the participants + +``` + +Sequence diagram illustrating the modification of ad hoc group communication participants by the initiator. The diagram shows interactions between MC service client 1, MC service server, MC service client 3, MC service client n, and MC service client 2. The process involves a modify request, authorization, a leave request for client 3, user notification, a leave response, removal of client 3, a security material command, a new group request for client 2, another user notification, a group call notify, and a final participant notification. + +**Figure 7.4.3.1-1: Modification of ad hoc group communication participants by the initiator** + +1. The MC service client 1 sends the modify ad hoc group call participants request to the MC service server in order to remove MC service client 3 from the ongoing ad hoc group communication and add MC service client 2 into it. +2. The MC service server verifies whether the MC service client 1 is authorized to add or remove(modify) the participants of the on-going ad hoc group communication. +3. The MC service server sends the modify ad hoc group communication participants response to the MC service client 1. +4. The MC service server sends the ad hoc group call leave request to the MC service client 3 in order to remove it from the on-going ad hoc group communication. +5. The MC service client 3 notifies the user of the ad hoc group call leave request. +6. The MC service client 3 sends the ad hoc group call leave response to the MC service server. +7. The MC service server removes the MC service client 3 from the ongoing ad hoc group communication. + +8. MC service client 1 sends AHGC share security material command to the MC service targeting MC service client 2 containing the security material to be shared with the MC service client 2 for use in this ad hoc group communication. + +NOTE: Steps 8 to 11 can occur at any time following step 3. + +9. The MC service server sends the ad hoc group communication request towards MC service client 2. +10. The receiving MC service client 2 notifies the user about the incoming ad hoc group communication. +11. The MC service client 2 accepts the ad hoc group communication request and send ad hoc group communication responses to the MC service server. The response may also contain a functional alias of the responding MC service user, which is verified (valid and activated for the user) by the MC service server. +12. The MC service server may notify the initiating MC service user of all the users who are added to the on-going ad hoc group communication. This notification may be sent to the initiating MC service user by the MC service server more than once during the call when MC service users join or leave the ad hoc group communication. +13. The MC service server may notify the participants about the change in the participants list of on-going ad hoc group communication. + +#### 7.4.3.2 Modification of ad hoc group communication participants by the MC service server + +Figure 7.4.3.2-1 below illustrates the modification of ad hoc group communication participants procedure by the MC service server. + +Pre-conditions: + +1. The MC service client 1 is the initiator of the ad hoc group communication. +2. MC service server determined the participants for the ad hoc group communication based on the criteria specified by the MC service client 1 while initiating the ad hoc group communication. +3. MC service server continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group communication. +4. The MC service server detects that the MC service client 5 satisfies the criteria and MC service client 4 stops to meet the criteria specified by the MC service client 1. + +![Sequence diagram illustrating the modification of ad hoc group communication participants by the MC service server. The diagram shows interactions between MC service client 1, MC service server, MC service client 2, MC service client 3, MC service client 4, and MC service client 5. The process involves establishing communication, detecting a new participant (client 5), adding them, detecting an old participant (client 4) no longer meeting criteria, removing them, and updating the group.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server + participant MC service client 2 + participant MC service client 3 + participant MC service client 4 + participant MC service client 5 + + Note right of MC service client 1: 1. Ad hoc group communication established based on the criteria specified by MC service client 1 + Note right of MC service server: 2. MC service server detects that MC service client 5 now meets criteria + MC service server->>MC service client 5: 3. Ad hoc group communication request + Note right of MC service client 5: 4. Notify User + MC service client 5->>MC service server: 5. Ad hoc group communication response + Note right of MC service client 1: 6. Ad hoc group communication changed by adding client 5 based on the criteria specified by MC service client 1 + Note right of MC service server: 7. MC service server detects that MC service client 4 does not meet criteria any more + MC service server->>MC service client 4: 8. Ad hoc group call leave request + Note right of MC service client 4: 9. Notify User + MC service client 4->>MC service server: 10. Ad hoc group call leave response + Note right of MC service client 1: 11. Ad hoc group communication changed by removing client 4 based on the criteria specified by MCPTT client 1 + +``` + +Sequence diagram illustrating the modification of ad hoc group communication participants by the MC service server. The diagram shows interactions between MC service client 1, MC service server, MC service client 2, MC service client 3, MC service client 4, and MC service client 5. The process involves establishing communication, detecting a new participant (client 5), adding them, detecting an old participant (client 4) no longer meeting criteria, removing them, and updating the group. + +**Figure 7.4.3.2-1: Modification of ad hoc group communication participants by the MC service server** + +1. The ad hoc group communication is established and on-going with the participants MC service client 1, MC service client 2, MC service client 3 and MC service client 4. The participants list is determined by the MC service server based on the criteria specified by the MC service client 1 while initiating the communication +2. The MC service server detects that the MC service client 5 satisfies the criteria specified by the MC service client. +3. The MC service server sends the ad hoc group communication request to the MC service client 5. +4. The MC service client 5 notifies the user about the incoming ad hoc group communication. +5. The MC service client 5 accepts the ad hoc group communication request and sends the ad hoc group communication response to the MC service server. +6. The on-going ad hoc group communication is updated by adding MC service client 5 which satisfies the criteria specified by the MC service client 1. +7. The MC service server detects that the MC service client 4 is no more satisfying the criteria to be the participant of the ad hoc group communication. +8. The MC service server sends the ad hoc group communication leave request to the MC service client 4 and removes it from the on-going ad hoc group communication. +9. The MC service client 4 notifies the user of the ad hoc group call leave request. +10. The MC service client 4 sends the ad hoc group communication leave response to the MC service server. +11. The on-going ad hoc group communication is updated by removing MC service client 4 which no more satisfies the criteria specified by the MC service client 1. + +### 7.4.4 Solution evaluation + +The procedures proposed as part of this solution handle the modification of participants list of the on-going ad hoc group communication. Participants can either be added to or removed from the on-going ad hoc group communication. This solution provides a mechanism for the initiator of the ad hoc group communication to modify the participants list if the list of participants is provided by the initiator and for the MC service server if the list of participants for the on-going ad hoc group communication is determined by the MC service server. + +# 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 4) 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 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 – Ad hoc group communication | Solution #1: Ad hoc group communication set up for MCX service | Clause 7.1.4 | SA3 | +| | Solution #2: Ad hoc group call involving multiple MC systems | Clause 7.2.3 | SA3 | +| Key issue #2 – Network topology hiding from MC service client while establishing Ad hoc group communication | Solution #1: Ad hoc group communication set up for MCX service | Clause 7.1.4 | None | +| Key issue #3 – Configuration parameters for Ad hoc group communication | Solution #3: Configuration parameters required for Ad hoc group communication | Clause 7.3.4 | None | +| Key issue #4 – Modifying participants list of on-going ad hoc group communication | Solution #4: Modifying participants list of on-going ad hoc group communication | Clause 7.4.4 | None | + +### 8.1.3 Overall evaluation of key issue #1 + +Key issue #1 is about the Ad hoc group communication, which enables authorized MCX users to combine a random set of MCX Users into a group communication. Following open issues are considered during the study : + +1. Procedures for establishing and release of the ad hoc group communication. +2. Procedures for establishing the ad hoc group communication with end-to-end encryption support. + +3. Identify whether new information flows are required or existing information flows can be enhanced to support the ad hoc group communication set up. +4. How to support different mechanisms for determining the participants list for the ad hoc group communication. It could be supplied by the initiator of the ad hoc group call or determined by the MCX system based on some pre-defined criteria. +5. How to support a mechanism for the initiator of an MCX Service ad hoc group communication to request that the list of participants are updated by the MCX Service system using a specific pre-defined criteria. +6. Identify whether any changes are required to the existing MCX functional architecture for supporting the ad hoc group communication. + +Both solution#1 and solution#2 addresses the open issues described above. Based on solution#1 and solution#2, a harmonized procedure is required to address the key issue#1. End-to-end encryption support is mandatory for the AHGC and usage of pre-configured group to achieve end-to-end encryption as specified in solution #2 will be adapted. New information flows except the AHGC share security material command described as part of solution #1 will be used. No architectural updates as specified in open issue 7 are required to support AHGC. + +### 8.1.4 Overall evaluation of key issue #2 + +Key issue #2 is about the network topology hiding while establishing the ad hoc group communication. Following open issues are considered : + +- How the group ID used for the ad hoc group communication can be created by MC service client and managed when establishing the ad hoc group communication. +- Whether and how to support the ad hoc group communication without exposing the network topology. +- Whether and how to support the ad hoc group communication with dynamically allocated network resources (such as the MC service server that will host the communication). + +Solution #1 with the option that the network creates the ad hoc group ID for the AHGC addresses the open issues listed above. This solution provides a procedure for the MC service server to create the ad hoc group ID and share it to the MC service clients that needs to be used for the ad hoc group communication. MC service client is not allowed to create AHGC group ID in solution #1. This way the MC service client is totally transparent of the network topology of the MC system domain and no need to create the ad hoc group ID by itself. As the network is the one selecting which MC service server to host the AHGC, network resources (the MC service server that hosts this group communication) can be dynamically allocated based on real-time information of network resources such as availability and traffic load balance that can be further specified in the normative work. The mechanism provided in Solution #1 can serve as basis for the normative work when topology hiding is required. + +### 8.1.5 Overall evaluation of key issue #3 + +Key issue #3 is about the configuration parameters that are required to be applied while establishing the ad hoc group communication. Following open issues are considered : + +- Identify the required system or service level configuration parameters and document them. +- Identify the user level configuration parameters and document them. +- Identify the default parameters to be configured which will be applied when these parameters are not supplied as part of the ad hoc group communication request by the initiator. +- How the MCX server shall be able to determine whether the user is authorized to initiate ad hoc group communication. + +Solution #3 identifies the configuration parameters that are required to address the open issues listed above and it can serve as basis for the normative work. There were no default parameters identified which needs to be configured. These configuration parameters are applied by MC service server handling AHGC as described in the below table: + +| Parameter description | Details | +|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Support of ad hoc group call | Value of this parameter determines whether ad hoc group communication is supported or not. MC service server rejects the ad hoc group communication if the value of this parameter is set to false. | +| Maximum number of participants allowed to participate in an ad hoc group communication | MC service server rejects the ad hoc group communication request if the number of participants invited for the call is exceeding the value of this parameter. | +| Hang timer for ad hoc group communication | MC service server terminates the ad hoc group call if there is no traffic for the time duration specified by this parameter. | +| Maximum duration for ad hoc group communication | This parameter value determines maximum allowed time duration for the ad hoc group communication to remain active after which the MC service server will terminate it. | +| List of preferred voice codecs for ad hoc group call | List of codecs, which can be used by the MC service client in the SDP offer. | +| Authorised to initiate ad hoc group call | MC service server uses this parameter to check whether the MC service user is authorized to initiate the ad hoc group call | +| Authorised to participate in ad hoc group call | MC service server uses this parameter to check whether the MC service user is authorized to participate the ad hoc group call | +| Authorised to initiate emergency ad hoc group call | MC service server uses this parameter to check whether the MC service user is authorized to initiate the emergency ad hoc group call | +| Authorised to initiate imminent peril ad hoc group call | MC service server uses this parameter to check whether the MC service user is authorized to initiate the imminent peril ad hoc group call | + +Editor's note: Any additional parameters related to MCVideo and MCData services applicable for AHGC is FFS. + +### 8.1.6 Overall evaluation of key issue #4 + +Key issue #4 is related to modification of participants list of on going ad hoc group communication. Following open issues are considered : + +- Modifying the participants list by the initiator of the ad hoc group communication when the participants list is provided by the initiator while establishing the ad hoc group communication. +- Modifying the participants list by the MC service server when the participants list is determined by the MC service server. + +Solution #4 identifies the information flows and procedures required to address the open issues listed above and it can service as basis for the normative work. + +# 9 Conclusions + +This technical report fulfils the objectives of the study on supporting ad hoc group communication for MC services. 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. Individual solutions addressing the key issues (clause 7); and +4. Overall evaluations of all the solutions (clause 11). + +No architectural requirements and enhancements were identified as part of the study. Also no dependencies on other working groups within 3GPP were identified. + +The study concludes with following considerations for the normative work: + +1. Definition of terms and abbreviations captured in clause 3 will be reused; +2. Following individual solutions, corresponding to the key issues, will be considered as candidate solutions: + - a. for Key issue #1 (Ad hoc group communication): + - i. Information flows specified in Solution #1 (Ad hoc group communication set up for MCX service) + - ii. Information flow AHGC share security material command is not required + - iii. Pre-configured group as specified in Solution #2 to be used for achieving the end-to-end security for both the cases where the participants list is supplied by the initiator of the AHGC and participants list is determined by the MC Service server. + - iv. Pre-configured group to be used for the AHGC is determined by the MC Service server and not by the initiating client. + - b. for Key issue #2 (Network topology hiding): + - i. Mechanism provided in Solution #1 (Ad hoc group communication set up for MCX service) where the MC service group ID is created by the MC Service server and shared to the participating clients to be adapted. + - c. for Key issue #3 (Configuration parameters): + - i. Solution #3 (Configuration parameters) + - d. for Key issue #4 (Modifying participants list): + - i. Solution #4 (Modifying participants list) + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA6#47-e | | | | | TR skeleton | 0.0.0 | +| 2022-02 | SA6#47-e | | | | | S6-220050, S6-220051, S6-220052, S6-220443, S6-220405, S6-220054, S6-220055, S6-220444, S6-220406 | 0.1.0 | +| 2022-04 | SA6#48-e | | | | | S6-220777, S6-220802, S6-220807 | 0.2.0 | +| 2022-05 | SA6#49-e | | | | | S6-221441, S6-221362, S6-221090, S6-221092 | 0.3.0 | +| 2022-06 | SA#96 | | | | | Presentation for information at SA#96 | 1.0.0 | +| 2022-07 | SA6#49-bis-e | | | | | S6-221565, S6-221566 | 1.1.0 | +| 2022-09 | SA6#50-e | | | | | S6-221523(SA6#49-bis-e), S6-222444, S6-222571, S6-222572, S6-222596, S6-222573, S6-222224 | 1.2.0 | +| 2022-10 | SA6#51-e | | | | | S6-222751, S6-222917, S6-222763 | 1.3.0 | +| 2022-12 | SA#98-e | SP-221223 | | | | Submitted for Approval at SA#98-e | 2.0.0 | +| 2022-12 | SA#98-e | SP-221223 | | | | 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-78/raw.md b/raw/rel-18/23_series/23700-78/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..50c640f06a7dbb00c609e3892c0e4c5ed0ca1544 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/raw.md @@ -0,0 +1,3766 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Application layer support for Personal IoT Network; (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 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 + +# **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 | +| Introduction ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms, symbols and abbreviations ..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 Key issues ..... | 10 | +| 4.1 Key issue #1: PIN Management..... | 10 | +| 4.2 Key issue #2: PINAPP accesses 5G network by application mechanism..... | 11 | +| 4.3 Key issue #3: Service switch in PIN ..... | 11 | +| 4.4 Key issue #4: PIN Application Server Discovery..... | 11 | +| 4.5 Key issue #5: Service continuity..... | 12 | +| 4.6 Key issue #6: PEMC/PEGC replacement in PIN..... | 12 | +| 5 Architecture requirements..... | 13 | +| 5.1 General ..... | 13 | +| 5.2 Requirements..... | 13 | +| 5.2.1 General requirements..... | 13 | +| 5.2.1.1 General..... | 13 | +| 5.2.1.2 Requirements ..... | 13 | +| 5.2.2 PIN Management..... | 13 | +| 5.2.2.1 General..... | 13 | +| 5.2.2.2 Requirements ..... | 13 | +| 5.2.3 PIN enable 5GS communication ..... | 14 | +| 5.2.3.1 General..... | 14 | +| 5.2.3.2 Requirements ..... | 14 | +| 5.2.4 Service Switch ..... | 14 | +| 5.2.4.1 General..... | 14 | +| 5.2.4.2 Requirements ..... | 14 | +| 5.2.5 Application server discovery..... | 14 | +| 5.2.5.1 General..... | 14 | +| 5.2.5.2 Requirements ..... | 14 | +| 5.2.6 Service continuity..... | 14 | +| 5.2.6.1 General..... | 14 | +| 5.2.6.2 Requirements ..... | 15 | +| 6 Architecture..... | 15 | +| 6.1 General ..... | 15 | +| 7 Solutions..... | 16 | +| 7.1 Mapping of solutions to key issues ..... | 16 | +| 7.2 Solution #1: PINAPP architecture..... | 16 | +| 7.2.1 Architecture assumption..... | 16 | +| 7.2.1.1 User accessing services provided by PIN Element from outside the PIN ..... | 17 | +| 7.2.2 Functional elements..... | 18 | +| 7.2.2.1 PIN element with Management Capabilities (PEMC)..... | 18 | +| 7.2.2.2 PIN Server..... | 18 | +| 7.2.2.3 PIN element with Gateway Capabilities (PEGC) ..... | 19 | +| 7.2.2.4 PIN client ..... | 19 | +| 7.2.2.5 Application client..... | 19 | +| 7.2.3 Reference Points..... | 19 | +| 7.2.4 Functional Entity Cardinality ..... | 20 | +| 7.2.4.1 PEMC..... | 20 | + +| | | | +|-----------|--------------------------------------------------------------------------|----| +| 7.2.4.2 | PEGC ..... | 20 | +| 7.2.4.3 | PIN server ..... | 20 | +| 7.2.4.4 | PIN client ..... | 21 | +| 7.2.4.5 | Application client..... | 21 | +| 7.2.5 | Identities ..... | 21 | +| 7.2.5.1 | PIN ID..... | 21 | +| 7.2.5.2 | UE identifier ..... | 21 | +| 7.2.5.3 | PIN client ID ..... | 21 | +| 7.2.5.4 | Application Client ID..... | 21 | +| 7.2.5.5 | PIN server ID ..... | 21 | +| 7.3 | Solution #2: PIN management ..... | 21 | +| 7.3.1 | Architecture enhancements..... | 21 | +| 7.3.2 | Solution description..... | 21 | +| 7.3.2.1 | General..... | 21 | +| 7.3.2.2 | Procedures of Creation of PIN..... | 22 | +| 7.3.2.3 | Procedures of Modification of PIN..... | 24 | +| 7.3.2.3.1 | PIN modification triggered by PEMC..... | 24 | +| 7.3.2.3.2 | PIN modification triggered by event of PEGC ..... | 26 | +| 7.3.2.3.3 | PEMC replacement triggered by PIN server..... | 26 | +| 7.3.2.3.4 | PEMC replacement triggered internally within the PIN ..... | 27 | +| 7.3.2.3.5 | PEGC replacement triggered by PEMC..... | 28 | +| 7.3.2.3.6 | PIN modification triggered by PEGC ..... | 29 | +| 7.3.2.3.7 | PIN modification triggered after local PEMC failure ..... | 31 | +| 7.3.2.3.8 | PIN management with multiple PEGCs..... | 31 | +| 7.3.2.3.9 | PIN management with multiple PEMCs ..... | 32 | +| 7.3.2.4 | Procedures of PIN Profile retrieval..... | 33 | +| 7.3.3 | Solution evaluation ..... | 34 | +| 7.4 | Solution #3: Insertion and remove of PIN elements in a PIN ..... | 34 | +| 7.4.1 | Architecture enhancements..... | 34 | +| 7.4.2 | Solution description..... | 34 | +| 7.4.2.1 | General..... | 34 | +| 7.4.2.2 | Procedures..... | 35 | +| 7.4.2.2.1 | PIN client requests to join into a PIN..... | 35 | +| 7.4.2.2.2 | The PEMC removes the PIN elements from a PIN..... | 36 | +| 7.4.2.2.3 | The PIN elements decides to leave the PIN ..... | 37 | +| 7.5 | Solution #4: PIN delete ..... | 38 | +| 7.5.1 | Architecture enhancements..... | 38 | +| 7.5.2 | Solution description..... | 38 | +| 7.5.2.1 | General..... | 38 | +| 7.5.2.2 | Procedures of Delete of PIN ..... | 38 | +| 7.5.2.2.1 | PIN delete triggered by PEMC..... | 38 | +| 7.5.2.2.2 | PIN delete triggered by PIN server ..... | 39 | +| 7.5.2.2.3 | PIN delete locally by PEMC ..... | 40 | +| 7.6 | Solution #5: PIN discovery ..... | 41 | +| 7.6.1 | Architecture enhancements..... | 41 | +| 7.6.2 | Solution description..... | 41 | +| 7.6.2.1 | General..... | 41 | +| 7.6.2.2 | Procedures of PIN discovery ..... | 42 | +| 7.6.2.2.1 | Procedures of PIN discovery based on PEMC..... | 42 | +| 7.6.2.2.2 | Procedures of PIN discovery with assistance of PIN server via PEGC ..... | 43 | +| 7.7 | Solution #6: PIN Profile ..... | 44 | +| 7.7.1 | Architecture enhancements..... | 44 | +| 7.7.2 | Solution description..... | 44 | +| 7.7.2.1 | General..... | 44 | +| 7.7.2.2 | PIN Profile in a PIN ..... | 45 | +| 7.7.2.3 | Dynamic profile information of a PIN..... | 45 | +| 7.7.2.4 | PIN client profile ..... | 47 | +| 7.7.3 | Solution evaluation ..... | 47 | +| 7.8 | Solution #7: PIN server discovery ..... | 48 | +| 7.8.1 | Architecture enhancements..... | 48 | +| 7.8.2 | Solution description..... | 48 | +| 7.8.2.1 | General..... | 48 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------|----| +| 7.8.2.2 | Procedures of PIN server discovery..... | 48 | +| 7.8.2.2.1 | Procedures of PIN server discovery based on receiving PIN server endpoint information ..... | 48 | +| 7.8.2.2.2 | Procedures of PIN server discovery via PEGC ..... | 48 | +| 7.8.2.2.3 | Procedures of PIN server discovery from PEMC ..... | 49 | +| 7.9 | Solution #8: Service switch in a PIN ..... | 50 | +| 7.9.1 | Architecture enhancements..... | 50 | +| 7.9.2 | Solution description..... | 50 | +| 7.9.2.1 | General ..... | 50 | +| 7.9.2.2 | Procedure ..... | 50 | +| 7.9.2.2.1 | Functional entities ..... | 50 | +| 7.9.2.2.2 | Procedures of PIN Service Switch ..... | 50 | +| 7.9.3 | Solution evaluation ..... | 52 | +| 7.10 | Solution #9: PINAPP role change..... | 53 | +| 7.10.1 | Architecture enhancements..... | 53 | +| 7.10.2 | Solution description..... | 53 | +| 7.10.2.1 | General ..... | 53 | +| 7.10.2.2 | Procedure ..... | 53 | +| 7.10.3 | Solution evaluation ..... | 54 | +| 7.11 | Solution #10: Service switch internal PIN ..... | 54 | +| 7.11.1 | Architecture assumptions ..... | 54 | +| 7.11.2 | Solution description..... | 54 | +| 7.11.2.1 | General ..... | 54 | +| 7.11.2.2 | Procedure of service switch internal PIN ..... | 55 | +| 7.11.3 | Solution evaluation ..... | 56 | +| 7.12 | Solution #11: Application Server Discovery in a PIN ..... | 56 | +| 7.12.1 | Architecture enhancements..... | 56 | +| 7.12.2 | Solution description..... | 56 | +| 7.12.2.1 | General ..... | 56 | +| 7.12.2.2 | Procedure ..... | 56 | +| 7.12.2.2.1 | Functional entities ..... | 57 | +| 7.12.2.2.2 | Procedures of PIN Application Server Discovery..... | 57 | +| 7.12.3 | Solution evaluation ..... | 58 | +| 7.13 | Solution #12: PEMC registration to PIN server ..... | 58 | +| 7.13.1 | Architecture enhancements..... | 58 | +| 7.13.2 | Solution description..... | 58 | +| 7.13.2.1 | General ..... | 58 | +| 7.13.2.2 | Procedures of PEMC registration ..... | 59 | +| 7.13.2.3 | Procedures of PINE/PEGC registration..... | 59 | +| 7.14 | Solution #13: SEAL enabled PINAPP architecture and PIN management ..... | 60 | +| 7.14.1 | Architecture assumption..... | 60 | +| 7.14.2 | PIN creation..... | 61 | +| 7.14.3 | PIN update ..... | 61 | +| 7.14.4 | PIN deletion..... | 61 | +| 7.14.5 | PIN discovery and PIN element discovery..... | 61 | +| 7.15 | Solution #14: PIN communication via 5GS..... | 61 | +| 7.15.1 | Architecture enhancements..... | 61 | +| 7.15.2 | Solution description..... | 61 | +| 7.15.2.1 | General ..... | 61 | +| 7.15.2.2 | Procedures of PIN communication via 5GS ..... | 62 | +| 7.15.2.3 | Procedures of credential provisioning to PINE via 5GS ..... | 63 | +| 7.16 | Solution #15: Service continuity ..... | 65 | +| 7.16.1 | Architecture enhancements..... | 65 | +| 7.16.2 | Solution description..... | 65 | +| 7.16.2.1 | General ..... | 65 | +| 7.16.2.2 | Procedures to support service continuity ..... | 66 | +| 7.16.2.2.1 | PEGC relocation..... | 66 | +| 7.16.2.2.2 | Change application layer communication to communication via 5GS, with the support of PIN server ..... | 67 | +| 8 | Deployment scenarios ..... | 76 | +| 8.1 | General ..... | 76 | +| 8.x | Deployment scenario #x: ..... | 76 | + +| | | | +|----------------------------------------------------|---------------------------------------------------------------------------------------|-----------| +| 9 | Overall evaluation ..... | 76 | +| 9.1 | Architecture enhancements ..... | 76 | +| 9.2 | Key issue evaluations ..... | 76 | +| 9.2.1 | General ..... | 76 | +| 9.2.2 | Evaluation of key issue #1: PIN Management ..... | 78 | +| 9.2.3 | Evaluation of key issue #2: PINAPP accesses 5G network by application mechanism ..... | 81 | +| 9.2.4 | Evaluation of key issue #3: Service switch in PIN ..... | 81 | +| 9.2.5 | Evaluation of key issue #4: PIN Application Server Discovery ..... | 83 | +| 9.2.6 | Evaluation of key issue #5: Service continuity ..... | 83 | +| 9.2.7 | Evaluation of key issue #6: PEMC/PEGC replacement in PIN ..... | 84 | +| 9.2.8 | Evaluation of PINAPP architecture ..... | 85 | +| 10 | Conclusions ..... | 85 | +| 10.1 | Conclusion of PIN management of KI#1 ..... | 85 | +| 10.2 | Conclusion of KI#2 ..... | 87 | +| 10.3 | Conclusion of Service Switch of KI#3 ..... | 88 | +| <b>Annex A (informative): Change history .....</b> | | <b>90</b> | + +# 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 + +Personal IoT Networks (PIN) is based on the greatly increasing number of consumers IoT devices. These devices can either be wearable devices or can be IoT devices in the home. Users create Personal IoT Networks out of all these Personal IoT devices mainly in their homes or around their body. This technical report identifies the key issues and corresponding application architecture and related solutions with recommendations for the normative work based on 3GPP TS 22.261 [2] and 3GPP TR 22.859 [3]. 3GPP TS 22.261 [2] also refer to requirements in 3GPP TS 22.101 [5] clause 26a that apply to Personal IoT Networks. + +# --- 1 Scope + +The present document is a technical report capturing the study on application layer support for Personal IoT networks (PIN). The aspects of the study include analyzing application layer architecture requirements of PIN, identifying key issues and supporting PIN application layer functional model. The study also includes information and support from 3GPP network to PIN, service or applications discovery within a PIN or by the UE outside of a PIN via 3GPP network. + +The study takes into consideration the work done for PIN in 3GPP TS 23.700-88 [4] and other related work in 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 22.261: "Service requirements for the 5G system". +- [3] 3GPP TR 22.859: "Study on Personal Internet of Things (PIoT) networks". +- [4] 3GPP TR 23.700-88: "Study on architecture enhancements for Personal IoT Network (PIN)". +- [5] 3GPP TS 22.101: "Service Principles". + +# --- 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]. + +**Access Control Information:** A set of information that assists the authorized PINE in a PIN to access 5GS network via PEGC, for example, the username or password. + +**PIN enabler:** Refers to the overall functionality provided by the entities such as PIN Client, PIN Gateway Client, PIN Management Client, and PIN server in support of applications as per the architecture defined in solution 7.2. + +**PIN management:** Refers to the set of operations related to creation, modification, maintenance and removal of PIN. + +**PIN Profile:** A set of data and information about the PIN and PIN elements resides in the PIN. **Service Switch:** A mechanism to switch the service traffic flow between Application server and PINE to application server and other PINE. + +NOTE: 3GPP TS 22.101 [5] clause 26a lists information that can be included in a PINE profile. + +For the purposes of the present document, the following terms given in 3GPP TS 22.261 [2] apply: + +**Personal IoT Network** + +**PIN direct connection** + +**PIN Element** + +**PIN Element with Gateway Capability** + +**PIN Element with Management Capability** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| <symbol> | <Explanation> | +|----------|---------------| + +## 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]. + +| | | +|--------|----------------------------------------| +| PIN | Personal IoT Network | +| PINAPP | Personal IoT Network Application | +| PEMC | PIN Element with Management Capability | +| PEGC | PIN Element Gateway Capability | +| PINE | PIN Element | + +# --- 4 Key issues + +## 4.1 Key issue #1: PIN Management + +As indicated in clause 6.38 of TS 22.261[2], the following requirements will be studied in this TR phase and reflect in this key issues: + +- The 5G system shall support mechanisms to identify a PIN, a PIN Element. +- The 5G system shall be able to support PINs with PIN Elements subscribed to more than one network operator (e.g., a PIN Element that is a MUSIM UE and subscribes to different operators respectively, one PIN Element subscribed to network operator A and another PIN Element subscribed to network operator B). + +In order to avail PIN management, for example, PIN creating/modifying/deleting UE or PINAPP should be able to trigger PIN management request to MNO. What is critical is whether and how the UE or PINAPP triggers PIN management request. + +After creating a PIN, in order to avail PIN service to other PIN elements (e.g.: IoT device), the PIN elements should be able to newly added into a PIN. So for the management of PIN, add or remove the PIN elements into a PIN is necessary. Also, one of the most important features of PIN is PEGC that enables PIN elements to communicate with 5G network and some of the PIN elements interact directly to other PIN elements within PIN. How to manage the specific permissions, for example, communicate with UE outside of PIN or connect to 5G network are important. + +It is required to study the following: + +- Who can manage (create/modify/delete) a PIN? +- Whether and how to trigger a PIN network management request, for example, PIN creation/modification/deletion. What parameters are required in PIN network management request? + +- How to add/remove PIN elements into a PIN after PIN establishment? What parameters or information are needed during adding/removing PIN elements into a PIN? How to configure newly added PIN element? +- Determine the certain PIN services in PIN. +- What information about the PIN and PIN elements needs to be maintained at the PIN server, PEMC and PEGC for the management of PIN and its elements and whether and how they are notified about the changes to this information. +- What set of events occurring in the PIN (e.g., PIN element added, PIN element removed etc.,) need to trigger the updates to the information maintained at the PIN server, PEMC and PEGC. +- What information can be created or modified or deleted by the authorized user. + +NOTE: PIN management services defined by SA2 will be reused and under consideration in PINAPP. + +## 4.2 Key issue #2: PINAPP accesses 5G network by application mechanism + +As indicated in clause 6.38 of TS 22.261[2], the following requirements will be studied in this TR phase and reflect in this key issues: + +- The 5G system shall enable the network operator to provide any 5G services to any UE via a PEGC. +- The 5G system shall support applications on an Application Server connected to a PIN. + +As a feature, PINAPP within a PIN can communicate with other devices, services and applications within the same PIN. Furthermore, PINAPP can connect with the 5G Network via a PEGC. Also, as a feature, some of the PINAPP in PIN has the permissions that they can communicate with other UE or application outside of PIN with the help of 5GC. + +From the aspects of PINAPP accesses 5G network by application mechanism, it is required to study the following: + +- How to realize that PINAPP access 5G network by application mechanism? + +NOTE: How to derive the route control information for PINAPP to access 5GS is in the scope of SA2, and not discussed in SA6. + +## 4.3 Key issue #3: Service switch in PIN + +As indicated in clause 6.38 of TS 22.261[2], the following requirements will be studied in this TR phase and reflect in this key issues: + +- The 5G system shall support mechanisms to aggregate, switch or split the service between non-3GPP RAT and PIN direct connections using licensed spectrum. +- The 5G system shall support applications on an Application Server connected to a CPN or PIN. + +When UE is located outside of PIN, the UE has the direct connection to application server via 5GS. When UE moves into the coverage of PIN, some of the PIN application in PIN has the capability, for example, to terminate the application traffic from application server. These PIN applications have better experience than the UE, in screen or sound. + +It is required to study the following: + +- How to support application mechanism for service switching in a PIN between different PIN applications for achieving better service experience? + +NOTE: The coordination with SA2 about the support for switching application traffic between RATs is needed. + +## 4.4 Key issue #4: PIN Application Server Discovery + +As indicated in 3GPP TS 22.261 [2], clause 6.38.2.1, the following requirement will be studied in this TR: + +- The 5G system shall support applications on an Application Server connected to a PIN. + +Supporting Application Servers connected to a PIN can involve service or applications discovery by PIN Elements or by a UE outside of a PIN via 3GPP network. + +Application clients can be running on PIN elements in a PIN and may want to discover and connect to an Application Server connected to the PIN. At the same time UEs running Application Clients outside of a PIN may try to discover and connect to an Application Server connected to the PIN. + +It is required to study the following: + +- How to enable discovery of Application Server, connected to a PIN, by Application Clients running in the same PIN? +- How to enable discovery of Application Server, connected to a PIN, by Application Clients running in a different PIN? +- How to enable discovery of Application Server, connected to a PIN, by Application Clients running in a UE outside of the PIN over 3gpp network? +- How to manage Application Server discovery by MNOs or third-party application service providers? +- Evaluate the applicability of Edge Enabler Layer and CAPIF for PIN application service discovery. + +## 4.5 Key issue #5: Service continuity + +As indicated in clause 6.38 of TS 22.261[2], the following requirements that describes the service continuity will be studied in this TR phase and reflect in this key issues: + +- The 5G system shall be able to minimize service disruption when a PIN Element changes the communication path from one PIN Element (e.g. PIN Element with Gateway Capability) to another PIN Element or operator provided mobile access. The communication path between PIN Elements may include licensed and unlicensed spectrum as well as 3GPP and non-3GPP access. + +The PIN application is the application deployed on PIN elements (for example, the UE) in PIN. One of the PIN application features is, the PIN application in UE can have a direct communication with other PIN application into a PIN, without have any routing from 5GS. + +But, there are the situations that may have a service disruption or relocation: + +- When UE moves out of a PIN or the terminal PIN application is in the status of moving, the original direct communication between two PIN applications may be influenced and changed (for example, the direct communication between two PIN applications may be routed via PEGC); +- Usually if a PIN application on a UE is consuming service from an application server and due to UE mobility, the PIN application on the UE should continue to receive services from the application server. + +It is required to study the following: + +- How to the support the service continuity when the UE hosting PIN application is in the status of moving? +- How to the support the service continuity when UE moves out of a PIN and keep the communication towards the PIN application? + +NOTE: Some of the service continuity work has relationship to SA2 work and depends on the SA2's feedback later. + +## 4.6 Key issue #6: PEMC/PEGC replacement in PIN + +For the management of PIN and to enable PIN elements communicate with 5GC, each active PIN will have atleast one PEMC and PEGC PIN elements successfully configured and registered. The PEMC or PEGC PIN elements may cease to perform their role because of any of the following reasons : + +1. Power drain of PIN elements acting as PEMC or PEGC + +2. Their validity duration allowed to perform the role of PEMC or PEGC is expiring +3. PEMC or PEGC PIN elements moving out of coverage of cellular network + +Hence there is a need for other existing PIN elements to take the role of PEMC or PEGC in order to successfully manage the PIN and to avoid service disruption. + +It is required to study the following: + +- Whether and how the need for PEMC or PEGC role change is determined? +- How another active PIN element take over the role or is assigned the role of PEMC or PEGC? +- Whether and how the existing active PIN elements is notified about the role change? +- Whether and how the required dynamic or context information of PIN is made available to the new element taking the role of PEMC or PEGC + +# --- 5 Architecture requirements + +## 5.1 General + +## 5.2 Requirements + +### 5.2.1 General requirements + +#### 5.2.1.1 General + +This clause specifies general requirements for the architecture. + +#### 5.2.1.2 Requirements + +[AR-5.2.1.2-a] The application layer architecture shall support deployment of personal IoT network. + +[AR-5.2.1.2-b] The application layer architecture shall support different deployment models in conjunction with an operator's 3GPP network. + +[AR-5.2.1.2-c] The application layer architecture shall be compatible with the 3GPP network system. + +### 5.2.2 PIN Management + +#### 5.2.2.1 General + +This clause specifies PIN management requirements for the architecture. + +#### 5.2.2.2 Requirements + +[AR-5.2.2.2-a] The application layer architecture shall provide mechanisms to create PIN for UE or PIN elements. + +[AR-5.2.2.2-b] The application layer architecture shall provide mechanisms to delete PIN, either triggered by PINEs or by PIN server. + +[AR-5.2.2.2-c] The application layer architecture shall support the mechanisms of PIN modification procedure, for example, PEMC/PEGC relocation. + +- [AR-5.2.2.2-d] The application layer architecture shall support the deployment and mechanism of multiple PEMCs/PEGCs. +- [AR-5.2.2.2-e] The application layer architecture shall support mechanisms to obtain PIN server endpoint address. +- [AR-5.2.2.2-f] The application layer architecture shall support the mechanisms to perform PIN discovery, and enable the PINs to join/leave the PIN. +- [AR-5.2.2.2-g] The application layer architecture shall support the mechanisms of PINE registration to PIN server. +- [AR-5.2.2.2-h] The application layer architecture shall support mechanisms to maintain, configure, update the PIN profile/PIN client profile. + +### 5.2.3 PIN enable 5GS communication + +#### 5.2.3.1 General + +This clause specifies PIN communication requirements for the architecture. + +#### 5.2.3.2 Requirements + +- [AR-5.2.3.2-a] The application layer architecture shall provide mechanisms to configure routing information in PEGC to enable the PINE to access the network provided by PEGC. +- [AR-5.2.3.2-b] The application layer architecture shall provide mechanisms to support the PIN and the PINs in PIN to consume the 5GS communication. +- [AR-5.2.3.2-c] The application layer architecture shall provide mechanisms to support the PEMC/PEGC to request the 5GS resource for PIN. + +### 5.2.4 Service Switch + +#### 5.2.4.1 General + +This clause specifies service switch requirements for the architecture. + +#### 5.2.4.2 Requirements + +- [AR-5.2.4.2-a] The application layer architecture shall provide mechanisms to support the service switching in a PIN between different PINE for achieving better service experience. + +### 5.2.5 Application server discovery + +#### 5.2.5.1 General + +This clause specifies application server discovery requirements for the architecture. + +#### 5.2.5.2 Requirements + +- [AR-5.2.5.2-a] The application layer architecture shall provide mechanisms to support the application server discovery for PIN. + +### 5.2.6 Service continuity + +#### 5.2.6.1 General + +This clause specifies service continuity requirements for the architecture. + +#### 5.2.6.2 Requirements + +[AR-5.2.6.2-a] The application layer architecture shall provide mechanisms to support the PEGC relocation procedure to enable service continuity. + +[AR-5.2.6.2-b] The application layer architecture shall provide mechanisms to change the communication from via PEGC to via 5GS, and enable the service continuity. + +# --- 6 Architecture + +## 6.1 General + +*This clause provides a general description of the architecture of PINAPP.* + +# 7 Solutions + +## 7.1 Mapping of solutions to key issues + +Table 7.2-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 | | | | | X | +| Sol #3 | X | | | | | | +| Sol #4 | X | | | | | | +| Sol #5 | X | | | | | | +| Sol #6 | X | | | | | | +| Sol #7 | X | | | | | | +| Sol #8 | | | X | | | | +| Sol #9 | | | | | | X | +| Sol #10 | | | X | | | | +| Sol #11 | | | | X | | | +| Sol #12 | X | | | | | | +| Sol #13 | X | | | | | | +| Sol #14 | | X | | | | | +| Sol #15 | | X | | | X | | +| Sol #16 | X | | | | | | +| Sol #17 | | | | | X | | + +## 7.2 Solution #1: PINAPP architecture + +### 7.2.1 Architecture assumption + +The Figure 7.2.1-1 shows the application architecture for enabling PINAPP. + +![Figure 7.2.1-1: PINAPP architecture diagram showing a Personal IoT network connected to a 3GPP Core network and a Data network. The Personal IoT network contains multiple Application clients, PIN client (enablers), PIN elements (PEGC, PEMC), and PIN elements (Relay). The 3GPP Core network contains a PIN server (enabler). The Data network contains an Application server. Interfaces are labeled PIN-1 through PIN-10.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates the PINAPP architecture. A dashed box labeled 'Personal IoT network' contains several components: + + +- Three 'Application client' blocks, each connected to a 'PIN client (enabler)' block. +- The first 'PIN client (enabler)' is associated with 'PIN elements C (3GPP/non-3GPP device)'. +- The second 'PIN client (enabler)' is associated with 'PIN elements B (3GPP/non-3GPP device)'. +- The third 'PIN client (enabler)' is associated with 'PIN elements A (Relay) (3GPP/non-3GPP device)'. +- There is also a 'PIN Gateway Client' block containing 'PIN elements (PEGC)'. +- A 'PIN Management client' block containing 'PIN elements (PEMC)'. + + Interfaces within the network are labeled: + + +- PIN-1, PIN-2, PIN-3, PIN-4, PIN-5, PIN-6, PIN-7, PIN-8, PIN-9, PIN-10. +- There are also labels 'Uu' and 'PIN - 3'. + + External connections: + + +- The 'Personal IoT network' connects to a '3GPP Core network' block. +- The '3GPP Core network' contains a 'PIN server (enabler)' block. +- The 'PIN server (enabler)' connects to a 'Data network' block. +- The 'Data network' contains an 'Application server' block. +- Interfaces PIN-7, PIN-8, and PIN-9 are shown between the 3GPP Core network and the Data network. + + Dashed arrows indicate 'Application data traffic not via PEGC' and 'APP Direct communication via PEGC'. + +Figure 7.2.1-1: PINAPP architecture diagram showing a Personal IoT network connected to a 3GPP Core network and a Data network. The Personal IoT network contains multiple Application clients, PIN client (enablers), PIN elements (PEGC, PEMC), and PIN elements (Relay). The 3GPP Core network contains a PIN server (enabler). The Data network contains an Application server. Interfaces are labeled PIN-1 through PIN-10. + +Figure 7.2.1-1: PINAPP architecture + +The UE or PIN elements have PIN client. The UE or PIN Element with gateway capability (PEGC) performs the role of an entity supporting gateway capability for PIN. The PEGC provides gateway functionality for the PIN elements. The UE or PIN Element with management capability (PEMC) performs the role of an entity supporting management capability for PIN. The PEMC provides management functionality for the PIN elements. + +The interactions between PEMC and PIN client are supported over PIN-3. The interactions between PEMC and PEGC are supported over PIN-4. The interactions between PEGC and PIN client are supported over PIN-2. The interactions between PIN clients from different UEs or PIN elements are supported over PIN-5. + +NOTE 1: It is possible that an application client on PIN elements can communicate with application server directly via 5GS or indirectly via PEGC. + +NOTE 2: It is possible that an application client can communicate with other application client in the same PIN directly or via PEGC. + +NOTE 3: It is possible that an application client can communicate with other application client in another PIN via PEGC. + +#### 7.2.1.1 User accessing services provided by PIN Element from outside the PIN + +The Figure 7.2.1.1-1 shows the application architecture updates to enable authorized user to access services provided by PIN element behind the PEGC. For simplicity, not all functional elements of Figure 7.2.1-1 are shown in below Figure 7.2.1.1-1. + +![Figure 7.2.1.1-1: PINAPP architecture diagram showing an authorized user accessing services from outside the PIN. The Personal IoT network contains an Application client, PIN client (enabler), PIN elements (Relay), PIN Gateway Client (PEGC), and PIN Management client (PEMC). The 3GPP Core network contains a PIN server (enabler). The Authorized User (PIN elements) connects to the PIN server. Interfaces are labeled PIN-1 through PIN-12.](9b62a616c7a1097c5da57f001ab6dd64_img.jpg) + +This diagram shows an update to the PINAPP architecture. A dashed box labeled 'Personal IoT network' contains: + + +- An 'Application client' block connected to a 'PIN client (enabler)' block. +- The 'PIN client (enabler)' is associated with 'PIN elements A (Relay) (3GPP/non-3GPP device)'. +- There is also a 'PIN Gateway Client' block containing 'PIN elements (PEGC)'. +- A 'PIN Management client' block containing 'PIN elements (PEMC)'. + + Interfaces within the network are labeled: + + +- PIN-1, PIN-2, PIN-3, PIN-4. + + External connections: + + +- The 'PIN client (enabler)' connects to a '3GPP Core network' block via PIN-3. +- The '3GPP Core network' contains a 'PIN server (enabler)' block. +- The 'PIN server (enabler)' connects to an 'Authorized User (PIN elements)' block via PIN-12. +- The 'Authorized User (PIN elements)' contains an 'Application client' block connected to a 'PIN client (enabler)' block. +- Interfaces PIN-11 and PIN-12 are shown between the 3GPP Core network and the Authorized User. + +Figure 7.2.1.1-1: PINAPP architecture diagram showing an authorized user accessing services from outside the PIN. The Personal IoT network contains an Application client, PIN client (enabler), PIN elements (Relay), PIN Gateway Client (PEGC), and PIN Management client (PEMC). The 3GPP Core network contains a PIN server (enabler). The Authorized User (PIN elements) connects to the PIN server. Interfaces are labeled PIN-1 through PIN-12. + +Figure 7.2.1.1-1: PINAPP architecture + +The interactions between PEGC and PIN client of the authorized user are supported over interface PIN-11. The interactions between PEMC and PIN client of the authorized user are supported over interface PIN-12. The authorized user uses PIN-12 to configure the policies in a PIN. + +NOTE: The authorized user is allowed to manage a PIN due to authorized user has PIN-12 interface to communicate with PEMC.7.2.1.2 **PIN Localization** + +Personal IoT Networks enable the communication needs of IoT devices within the constraints of a localized, private network. IoT devices using 3GPP or non-3GPP access may be members of a PIN. The PIN may consist of wearable IoT devices or IoT devices used in home automation. A PIN client that is authorized to access the PIN may access the PIN locally within the coverage area of the PIN or remotely over the 5G network. PIN localization refers to the main coverage area of the PIN and may be mobile if the PIN consists of wearable IoT devices and is being used by a user of the PIN who is mobile. + +### 7.2.2 Functional elements + +The functional entities of the application architecture for enabling PINAPP are described in this clause. + +#### 7.2.2.1 PIN element with Management Capabilities (PEMC) + +PEMC: A PIN Element with Management Capability is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN. + +It provides following functionalities: + +- For a network operator or authorized user to configure the policies of the PIN; +- Provide life span information of the PIN to the authorized user or the PIN elements; +- Maintain the UEs or PIN elements who joined the PIN. It includes maintaining available services, capability to act as a relay to other UEs or PIN elements; and +- Maintain the PIN profile for each PIN and PINE in PIN; +- To configure and manage a PIN; including: + - authorizing the UEs or PIN elements requesting to join the PIN; + - authorizing the PEGC and configure the parameters in PEGC to support PINE communication (via 5GS or direct communication); + - configuring UEs or PIN elements to enable service discovery of other UEs or PIN Elements; + - add new UEs or PIN elements to the PIN; + - configure UEs and PIN elements to enable direct communications; and + - configure UEs and PIN elements to communicate with each other when gateway device is unavailable. + - support the PIN server endpoint address delivery to UEs or PIN elements; + - support the credentials delivery to UEs or PIN elements; + +NOTE: When gateway device is unavailable, the configurations are required to enable direct communication. + +#### 7.2.2.2 PIN Server + +PIN server: Deployed by operator in network, and provisioning of configuration information to UE (PINAPP). Authorization of the Creation request of PIN, and arranges the PEGC information about access control to PIN. + +- Maintain the PIN profile for each PIN and PINE in PIN; +- Authorized the PIN create/PIN modification/PIN delete +- Determine the access control information of PEGC/PINE in PIN +- Authorized the PINE to be added/removed into/from the PIN +- Support PIN discovery and application server discovery + +#### 7.2.2.3 PIN element with Gateway Capabilities (PEGC) + +PEGC: A PIN Element with Gateway Capability is a PIN Element that provide any 5G services to any UE or PINAPP. + +- Maintain the PIN profile for each PIN and PINE in PIN; +- Maintain the access control information for each PIN and each PINE in PIN, and authorized whether the PINE can access the network provided by PIN; +- Support to trigger the PDU session modification towards 5GS to request the resource for PIN; +- Enable the 5GS communication or direct communication; +- Support to PIN server address delivery; +- Support to deliver the credentials to PINE; +- Support PIN discovery function + +#### 7.2.2.4 PIN client + +PIN client: The PIN enabler layer deployed in PIN elements to enable the management procedure to PEMC and routing control procedure to PEGC. + +It provides the following functionalities for the application clients in the UE or PIN element: + +- Registering the available service and capabilities; +- Perform service discovery of other UEs or PIN elements; +- Communicate with PIN clients of other UEs or PIN elements; +- Act as a relay for other UEs or PIN elements; +- Selects relay for direct communication; and +- Indicate whether the UE or PIN element, in which the PIN client resides, is discoverable or not. +- Maintain the PIN profile; +- Support to do application server discovery; +- Perform to join/leave a PIN; +- Support to discover the available PIN. +- Support to receive the information to access the network provided by PEGC; + +#### 7.2.2.5 Application client + +Application client: AC is the application resident in the PIN elements performing the client function. + +### 7.2.3 Reference Points + +PIN - 1: The interactions related to enabling PINAPP, between the Application client and the PIN client. + +PIN - 2: This reference point exists between PIN client and PEGC which connects PIN client of UE to PEGC. The PIN client uses this interface to communicate with other PIN clients within PIN or to access 3GPP network.. + +PIN - 3: This reference point exists between the PIN client and PEMC and following functionalities are supported over this reference point: + +- Authorizing PIN clients to access PIN; + +- Service discovery of other UEs or PIN elements; +- Discovery and selection of relay UEs or PIN elements; +- Notifying the PIN information modification details (e.g. PEMC change, PEGC change, PIN capabilities change). + +PIN - 4: This reference point exists between the PEGC and PEMC and following functionalities are supported over this reference point: + +- Authorizing PEGC for PIN access; +- Notification of PIN elements joining or leaving the PIN by PEMC to PEGC; +- Delivery of PIN dynamic profile information by PEMC to PEGC whenever it changes; + +PIN - 5: This reference point exists between the one PIN client and another PIN client and it supports direct connection over 3GPP or non-3GPP RAT. It also connects to PIN client of a UE or PIN element to the PIN client of another UE or PIN element acting as a relay. + +PIN - 6: This reference point exists between the PEMC and PIN server and supports the following functionalities: + +- Authorization of PEMC; +- Notifying PIN server whenever a PIN element joins or leaves the PIN, whenever a PIN client updates its capabilities; +- Notifying PIN server of PEGC replacement; +- Delivery of PIN dynamic profile information; + +PIN - 7: The interactions related to enabling PINAPP, between the one PEGC and PIN server. + +PIN - 8: The interactions related to enabling PINAPP, between the one PIN server and 3GPP core network. + +PIN - 9: The interactions related to enabling PINAPP, between the application server and PIN server. + +PIN - 10: The interactions related to enabling PINAPP, between the PIN client in PIN element and PIN server. + +PIN - 11: The interactions related to enabling PINAPP, between the PEGC and PIN client from outside the PIN to access the services provided by PIN elements within the PIN. + +PIN - 12: The interactions related to enabling PINAPP, between the PEMC and PIN client for configuring and managing the PIN from outside the PIN. + +### 7.2.4 Functional Entity Cardinality + +#### 7.2.4.1 PEMC + +The following cardinality rules apply for PEMC: + +- a) one or more PEMCs per PIN. + +#### 7.2.4.2 PEGC + +The following cardinality rules apply for PEGC: + +- a) one or more PEGCs per PIN. + +#### 7.2.4.3 PIN server + +The following cardinality rules apply for PIN server: + +- a) one PIN server per PIN. +- b) Multiple PINs per PIN server. + +NOTE: There might be multiple PIN servers deployed in a PLMN. + +#### 7.2.4.4 PIN client + +The following cardinality rules apply for PIN client: + +- a) one or more PIN clients per PIN. +- b) one PIN client per PIN element. + +#### 7.2.4.5 Application client + +The following cardinality rules apply for application client: + +- a) one or more application clients per PIN client. + +### 7.2.5 Identities + +#### 7.2.5.1 PIN ID + +The PIN ID is a unique value in PLMN that identifies the PIN. + +#### 7.2.5.2 UE identifier + +The UE ID uniquely identifies a particular UE within a PLMN domain. Following identities are examples that can be used: + +- a) GPSI, as defined in 3GPP TS 23.501 [02]. + +NOTE: To protect privacy of the user, MSISDN can be used as GPSI only after obtaining user's consent. + +#### 7.2.5.3 PIN client ID + +The PIN client ID is a globally unique value that identifies the PIN client. + +#### 7.2.5.4 Application Client ID + +The ACID identifies the client side of a particular application, for e.g. SA6Video viewer, SA6MsgClient etc. For example, all SA6MsgClient clients will share the same ACID. + +In case that the UE is running mobile OS, the ACID is a pair of OSId and OSAppId. + +#### 7.2.5.5 PIN server ID + +The PIN server ID is a unique value in PLMN domain that identifies the PIN server. + +## 7.3 Solution #2: PIN management + +### 7.3.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.3.2 Solution description + +#### 7.3.2.1 General + +This solution addresses aspects of Key Issue #1. + +After the UE or PINAPP acquires the role of PEMC, the PINAPP can trigger a creation of PIN towards PIN server. + +When the PINAPP as a PEMC to trigger the creation of PIN, there may be the two situations below: + +- There is only one element in PIN, and the PEMC manages itself; +- There are already several PIN elements or PEMC. The other PIN elements or PEGC have communication links with PEMC via non-3GPP access and the PEMC can trigger creation of PIN with these PIN elements in group. + +After the creation of PIN is accepted by network, the PIN server response with the PIN ID, the PEGC information about access control configured in PEGC. + +At the network side, a PIN server should be deployed. The PIN server (represent the operator) is responsible for the authorization of the Creation request of PIN, and arranges the PEGC information about access control to PIN. + +How the PIN server receives or derives PEGC information about access control is in the scope of SA2. + +For an established PIN, the PIN can be modified in the following situation: + +- Changes of PEMC. For example, the current PEMC may no longer be provide management of PIN and the role of PEMC will be changed to another PIN elements. +- Changes of PEGC. For example, if the current PEGC has broken down or is switched off, or the PEGC moves out of the direct communication proximity of the PINE client(s). The current PEGC is no longer suitable and enforcing another PIN element as PEGC is needed. +- Update of PIN service. If the service that a PINE (in a PIN) or PIN can provide is updated, the PEMC should trigger the modification of PIN towards PIN server to update the PIN service. +- Update of PIN service remotely by authorised administrator after local PEMC failure. An authorised administrator is the owner of the PIN and needs to reconfigure the PIN after a communication failure with the local PEMC. The authorised administrator can access the PIN and the PIN server only through the 5G network. + +**Editor's note:** The access control information should be coordinated with SA2 and wait for further update. + +#### 7.3.2.2 Procedures of Creation of PIN + +This procedure presents a high-level overview of Solution #X. + +Figure 7.3.2.2.2.-1 illustrates PIN creation procedure based on request/response model. + +Pre-conditions: + +1. The UE (PINAPP) has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The UE Identifier or PIN client Identifier is available; +3. The PINAPP has been authorized to communicate with the PIN server; +4. The PINE-1 has already received the role of PEMC from PIN server; + +![Sequence diagram for PIN creation. Lifelines: PIN Server, PINE-1 (PEMC), PINE-2 (PEGC), PINE-3, PINE-4. The sequence starts with PINE-1 sending a '1. Request of creation of PIN' to the PIN Server. The server responds with '2. Process request' and '3. Response of creation of PIN'. PINE-1 then sends notification requests (4a, 4b, 4c) to PINE-2, PINE-3, and PINE-4 respectively. Each receives a corresponding notification response (5a, 5b, 5c).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant PIN Server + participant PINE-1 (PEMC) + participant PINE-2 (PEGC) + participant PINE-3 + participant PINE-4 + + Note left of PIN Server: 2. Process request + PINE-1->>PIN Server: 1. Request of creation of PIN + PIN Server-->>PINE-1: 3. Response of creation of PIN + PINE-1->>PINE-2: 4a. PIN created notification request + PINE-2-->>PINE-1: 5a. PIN created notification response + PINE-1->>PINE-3: 4b. PIN created notification request + PINE-3-->>PINE-1: 5b. PIN created notification response + PINE-1->>PINE-4: 4c. PIN created notification request + PINE-4-->>PINE-1: 5c. PIN created notification response + +``` + +Sequence diagram for PIN creation. Lifelines: PIN Server, PINE-1 (PEMC), PINE-2 (PEGC), PINE-3, PINE-4. The sequence starts with PINE-1 sending a '1. Request of creation of PIN' to the PIN Server. The server responds with '2. Process request' and '3. Response of creation of PIN'. PINE-1 then sends notification requests (4a, 4b, 4c) to PINE-2, PINE-3, and PINE-4 respectively. Each receives a corresponding notification response (5a, 5b, 5c). + +Figure 7.3.2.2.2-1: Creation of PIN + +1. The PEMC sends a PIN creation request to the PIN server in-order to create a PIN. The PIN creation request includes the security credentials of the UE or PINAPP received during PINAPP authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PINAPP profile(s) information. The PEMC can also indicate the PIN service that the PIN can provide to PIN server. + +The PEMC can request to create a PIN including the details of other PIN elements that has already communicated with it. The details of the PIN elements could be for example, UE identifier such as GPSI, PIN client ID, UE location and PINAPP profile(s) information. + +If there are no other PIN elements in the request, the PEMC requests to create a PIN including itself. + +NOTE 1: In order to save the procedure of several PEMCs to be involved into the certain PIN as individual PEMC, the PEMC can have the additional PEMC GPSIs in the PIN create request, to indicate additional PEMCs that are allowed to manage the PIN. This procedure doesn't have conflict with that other PEMC requests to join the certain PIN and becomes PEMC separately. + +NOTE 2: For a certain PIN, only one PEMC at a time can be assigned with primary role and other PEMCs if any are assigned with secondary role.. + +2. Upon receiving the request, the PIN server performs an authorization check to verify whether the PINE-1 (PEMC) has authorization to perform the operation. + +**Editor's Note: Whether and how the 5GC involved in the PIN creation is FFS.** + +3. The PIN server sends a successful response to PINE-1PEMC, which includes a newly assigned PIN ID to indicate the PIN. It also includes the list of PIN elements and their identifier which are authorized and made as member of the newly created PIN if the PIN creation request contains the list of PIN elements to be included in the PIN. If the PIN creation request fails, the PIN server should give the failure response indicating the cause of PIN creation request failure. + +If there are no other PIN elements in the PIN creation request and the PIN creation is successful, the PEMC indicates the PINAPP (PEMC) to be the PEGC. The PINAPP who has already had the role of PEMC can also have the role of PEGC. + +If the PEGC is indicated, the PIN server sends PIN client ID (that represents the PEGC), assigned IP address or port number in successful response to PEMC. And, the PIN Server also sends the PEGC information about access control in the response, including: + +- Access control information includes: user name, account, SSID, BSSID. All the information is used by PIN elements in PIN to access 5G or access other application outside of PIN; + +The PIN server or PEMC can decide the access control information in certain PEGC. + +- If the access control information decided by PIN server, the PIN server sends the access control information to PEMC. And the PEMC delivers the access control information to PEGC. +- If the access control information decided by PEMC, the PEMC delivers the access control information to PEGC. + +4a-4c. [Optional] If the response of creation of PIN contains the list of PIN elements, the PINE-1 (PEMC) generates the PIN created notification request to individual PIN elements based on the list received in step 3. This notification request includes the PIN ID of the newly created PIN and also contains an indication that the PIN element is made the member of the newly created PIN. + +5a-5c. [Optional] The individual PIN elements sends the PIN created notification response to acknowledge the receipt of the notification. The PIN elements receiving the PIN creation notification request with joined indication shall not join the PIN by issuing the PIN join request since they are already made as the member of the PIN. + +After the procedure above, the PINAPP (PEMC) creates a PIN with PINAPP(PEGC) and other accepted PIN elements in PIN. + +The following procedure defines how to provide PEGC information (for example, the access control information) to PINE over direct connection which enables the PINE to connect to PEGC. + +![Sequence diagram showing the interaction between PINE and PEMC. Step 1: PEMC sends a 'Create Connection Request' with '[Connection Info]' and '[Auth Info]' to PINE. Step 2: PINE sends a 'Response' back to PEMC.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +``` + +sequenceDiagram + participant PINE + participant PEMC + Note right of PEMC: 1. Create Connection Request +([Connection Info], [Auth Info]) + PEMC->>PINE: 1. Create Connection Request + Note left of PINE: 2. Response + PINE->>PEMC: 2. Response + +``` + +Sequence diagram showing the interaction between PINE and PEMC. Step 1: PEMC sends a 'Create Connection Request' with '[Connection Info]' and '[Auth Info]' to PINE. Step 2: PINE sends a 'Response' back to PEMC. + +**Figure 7.3.2.2.2-2: Deliver access related information to PINE for connecting to PEGC** + +1. The PEMC sends request ([Connection Info], [Authorization Info]) to the PINE. The Connection Info contains the access control information. The Auth Info may be included for authenticating/authorizing PINE connecting to PEGC. +2. The PINE responds to the PEMC. + +After receiving the access control information, the PINE can access into the network that PEGC provide and after the authorization/authentication with PEMC, the PINE can finally use the gateway service to communication. + +**NOTE:** The access control information is per-PINE/per-PIN information. Each PINE uses this information to access the network provided by PEGC for a PIN. And the PEGC uses this access control information to authorize that whether the PINE can consume the network provided by PEGC in a PIN. + +#### 7.3.2.3 Procedures of Modification of PIN + +##### 7.3.2.3.1 PIN modification triggered by PEMC + +If the management of PIN should be changed to other PIN elements in UE, the original PEMC of a PIN should trigger the PIN modification procedure to PIN server. + +Figure 7.3.2.3.1-1 illustrates PIN modification procedure based on request/response model. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; +4. A PIN client has already received the role of PEMC from PIN server; + +![Sequence diagram showing the modification of PIN triggered by PEMC. The diagram involves three lifelines: PEMC (new), PEMC (old), and PIN server (AF). The sequence of messages is: 1. Request of modification of PIN from PEMC (old) to PIN server (AF); 2. Process request from PIN server (AF) to itself; 3. Response of modification of PIN from PIN server (AF) to PEMC (old); 4. Delivery of PIN management information from PIN server (AF) to PEMC (new).](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +``` + +sequenceDiagram + participant PEMC_new as PEMC (new) + participant PEMC_old as PEMC (old) + participant PIN_server as PIN server (AF) + Note right of PIN_server: 2. Process request + PEMC_old->>PIN_server: 1. Request of modification of PIN + PIN_server->>PIN_server: 2. Process request + PIN_server->>PEMC_old: 3. Response of modification of PIN + PIN_server->>PEMC_new: 4. Delivery of PIN management information + +``` + +Sequence diagram showing the modification of PIN triggered by PEMC. The diagram involves three lifelines: PEMC (new), PEMC (old), and PIN server (AF). The sequence of messages is: 1. Request of modification of PIN from PEMC (old) to PIN server (AF); 2. Process request from PIN server (AF) to itself; 3. Response of modification of PIN from PIN server (AF) to PEMC (old); 4. Delivery of PIN management information from PIN server (AF) to PEMC (new). + +**Figure 7.3.2.3.2-1: Modification of PIN triggered by PEMC** + +1. The PEMC sends a PIN modification request to the PIN server to request to change the role of PIN management. The PIN modification request includes the security credentials of the PIN client received during PIN client authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PIN client profile(s) information and PIN ID. The PIN ID indicates the management of this PIN will be changed. + +The PEMC can also include the potential PEMC in this PIN that represented by GPSI, PIN client ID. But this propose by PEMC is only for recommendation towards PIN server. If there are more than one potential PEMCs are included in PIN modification request, the original PEMC can label the priority of these potential PEMCs. + +Also, if the PIN service in PIN has updated, for example, the service in PINE (in this PIN) is newly added or the service in PINE (in this PIN) is deactivated or disabled, the PEMC should trigger PIN modification request includes the updated PIN services. + +2. Upon receiving the request, the PIN server performs an authorization check to verify whether the PEMC has authorization to perform the operation. The PIN server also updates and stores the PIN service of this PIN as PIN profile. +3. The PIN server sends a successful response to original PEMC, which includes a stop of administrator permissions of PIN and the PIN client ID of the new PEMC. If the PIN modification request fails, the PIN server should give the failure response to indicates that indicates the cause of PIN modification request failure. + +The PIN server can decide the new PEMC from the PIN elements in the PIN, and can also consider the potential PEMC that indicated by old PEMC. + +After the new PEMC is selected, the new PEMC can either be configured with the PIN Profile information by PIN server, or the PIN Profile information can be configured by the old PEMC. The PIN Profile information includes the PIN elements in PIN (for example, IP address or ID), access control information of each PIN elements. + +4. After receiving the successful of PIN modification response, the old PEMC stops the administrator permissions of a PIN which is represented by PIN ID. And the PIN server delivers the PIN Profile information to the new PEMC according to new PEMC IP address or ID indicated in successful PIN modification request. + +##### 7.3.2.3.2 PIN modification triggered by event of PEGC + +If the current PEGC is broken down or switched off, or the PEGC moves out of the direct communication proximity of the PINE clients(s). It is not properly to keep this PEGC, and enforces another PIN element as PEGC is needed. + +Figure 7.3.2.3.2-1 illustrates PIN modification procedure triggered by event of PEGC. + +Pre-conditions: + +1. The PEGC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEGC has been authorized to communicate with the PIN server; + +![Sequence diagram illustrating the PIN modification procedure triggered by PEGC. The diagram shows three lifelines: PEGC (new), PEGC (old), and PIN server/PEMC. The sequence of messages is: 0. PEGC (old) sends a 'Subscribe to the event of PEGC' message to PIN server/PEMC. 1. PEGC (old) sends a 'PEGC event notification' message to PIN server/PEMC. 2. PIN server/PEMC sends a 'Decides the PIN modification' message to PEGC (old). 3. PIN server/PEMC sends a 'Response of modification of PIN' message to PEGC (old). 4. PIN server/PEMC sends a 'Delivery of PIN management information' message to PEGC (new).](9b686adccf125267a013fa25721231a3_img.jpg) + +``` + +sequenceDiagram + participant PEGC_old as PEGC (old) + participant PIN_server_PEMC as PIN server/PEMC + participant PEGC_new as PEGC (new) + Note right of PIN_server_PEMC: 2. Decides the PIN modification + PEGC_old->>PIN_server_PEMC: 0. Subscribe to the event of PEGC + PEGC_old->>PIN_server_PEMC: 1. PEGC event notification + PIN_server_PEMC->>PEGC_old: 3. Response of modification of PIN + PIN_server_PEMC->>PEGC_new: 4. Delivery of PIN management information + +``` + +Sequence diagram illustrating the PIN modification procedure triggered by PEGC. The diagram shows three lifelines: PEGC (new), PEGC (old), and PIN server/PEMC. The sequence of messages is: 0. PEGC (old) sends a 'Subscribe to the event of PEGC' message to PIN server/PEMC. 1. PEGC (old) sends a 'PEGC event notification' message to PIN server/PEMC. 2. PIN server/PEMC sends a 'Decides the PIN modification' message to PEGC (old). 3. PIN server/PEMC sends a 'Response of modification of PIN' message to PEGC (old). 4. PIN server/PEMC sends a 'Delivery of PIN management information' message to PEGC (new). + +Figure 7.3.2.3.2-1: Modification of PIN triggered by PEGC + +0. The PIN server or PEMC can subscribe the mobility of PEGC that when the PEGC moves out of the area of interests (for example, leave home or office). Or the PIN server and PEMC can subscribe the status of PEGC that when the PEGC switches off and the PIN server can be notified by the PEGC. After receiving the event notification, the PIN server can trigger the modification of PEGC. +1. The PIN server or PEMC is notified by PEGC of event notification. +2. The PIN server or PEMC decides to modify the PIN with changing PEGC. +3. The PIN server or PEMC sends a successful response to original PEGC, which includes a stop of access control information in PEGC. If the PIN modification request fails, the PIN server should give the failure response to indicates that indicates the cause of PIN modification request failure. + +The PIN server or PEMC can decide the new PEGC from the PIN elements in the PIN. + +4. After receiving the successful of PIN modification response, the old PEGC stops the routing control of a PIN which is represented by PIN ID. And the PIN server delivers the access control information to the new PEGC. + +##### 7.3.2.3.3 PEMC replacement triggered by PIN server + +The following solution corresponds to the key issue #6 on PEMC/PEGC replacement in PIN as specified in clause 4.6. + +In some scenarios, like hardware failure, crash or power drain, the current PEMC may not be in a position to indicate to the PIN server or request the PIN server to assign the role of PEMC to another PIN element. In these cases, the PIN server on detecting the unavailability of the PIN element acting as PEMC, need to assign the role to another PINE and transfer the PIN dynamic profile information to the new PEMC. + +Figure 7.3.2.3.3-1 illustrates PEMC replacement procedure triggered by PIN server on detecting current PEMC is unavailable. + +Pre-conditions: + +1. PEMC-2 PIN element has already indicated that it can act as PEMC during the registration process. +2. Dynamic profile information about the PIN is available at the PIN server + +![Sequence diagram illustrating PEMC replacement triggered by PIN server. Lifelines: PIN Server, PEMC-1, PEMC-2, PEGC, PINE-1, PINE-2. The process starts with a note that PEMC-1 is the current PEMC. Then, the PIN server detects PEMC-1's unavailability, requests PEMC-2 to take over, receives a success response, and delivers dynamic information. Finally, PEMC-2 sends change notifications to PEGC, PINE-1, and PINE-2.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` + +sequenceDiagram + participant PIN Server + participant PEMC-1 + participant PEMC-2 + participant PEGC + participant PINE-1 + participant PINE-2 + + Note right of PEMC-1: 1. PEMC-1, PEMC-2, PEGC, PINE-1 and PINE-2 are part of the PIN. PEMC-1 is currently the PEMC of the PIN. + Note left of PIN Server: 2. PIN server detects unavailability of PEMC-1 + PIN Server->>PEMC-2: 3. Request to take the role of PEMC + PEMC-2-->>PIN Server: 4. Success response to take the role of PEMC + PIN Server->>PEMC-2: 5. Delivery of PIN dynamic information + PEMC-2->>PEGC: 6a. PEMC change notification + PEMC-2->>PINE-1: 6b. PEMC change notification + PEMC-2->>PINE-2: 6c. PEMC change notification + +``` + +Sequence diagram illustrating PEMC replacement triggered by PIN server. Lifelines: PIN Server, PEMC-1, PEMC-2, PEGC, PINE-1, PINE-2. The process starts with a note that PEMC-1 is the current PEMC. Then, the PIN server detects PEMC-1's unavailability, requests PEMC-2 to take over, receives a success response, and delivers dynamic information. Finally, PEMC-2 sends change notifications to PEGC, PINE-1, and PINE-2. + +**Figure 7.3.2.3.3-1: PEMC replacement triggered by PIN server** + +1. PEMC-1, PEMC-2, PEGC, PINE-1 and PINE-2 are part of same PIN. PEMC-1 is currently the PEMC of the PIN. +2. The PIN server identifies that PEMC-1 is down or crash or its duration to act as PEMC is ending. How PIN server identifies that the current PINE acting as PEMC is crashed or down is not in the scope of this specification. +3. The PIN server looks into the PIN profile and PIN dynamic profile information to identify the new PINE which can take up the role of PEMC (here PEMC-2 PIN element) and requests PEMC-2 to take the role of PEMC. +4. If the PEMC-2 PINE decides to take up the role of PEMC it sends the success response to the PIN server. +5. The PIN server delivers the PIN dynamic profile information to the PEMC-2. +- 6a,6b,6c. Once the PEMC replacement process is success, the PEMC-2 signals all the PINEs in the PIN including the PEGC about the change in the PIN element acting as PEMC and its reachability information. + +##### 7.3.2.3.4 PEMC replacement triggered internally within the PIN + +The following solution corresponds to the key issue #6 on PEMC/PEGC replacement in PIN as specified in clause 4.6. + +A PIN element could have been authorized to act as PEMC for a certain duration after which it is either removed from the PIN or de-authorized to act as PEMC. Another PIN element in the PIN takes over the role of PEMC. + +When the duration of its role as PEMC is expiring or for some other reasons (which could be implementation specific) the current PEMC requests another PINE to take the role of PEMC. Once the role assignment succeeds, the PIN server and other PIN elements including PEGC are notified of this role change. + +Figure 7.3.2.3.X-1 illustrates PEMC replacement procedure triggered internally within the PIN by current PEMC. + +Pre-conditions: + +1. PEMC-2 PIN element has already indicated that it can act as PEMC during the registration process. +2. Dynamic profile information about the PIN is available at the current PEMC and PIN server + +![Sequence diagram illustrating PEMC replacement triggered internally within the PIN. The diagram shows interactions between PIN Server, PEMC-1, PEMC-2, PEGC, PINE-1, and PINE-2. The process starts with a note that all elements are part of the PIN and PEMC-1 is the current PEMC. PEMC-1 then decides to handover the role, requests it from PEMC-2, receives a success response, and delivers dynamic information. Finally, PEMC-1 sends change notifications to the PIN Server, PEGC, PINE-1, and PINE-2.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` + +sequenceDiagram + participant PIN Server + participant PEMC-1 + participant PEMC-2 + participant PEGC + participant PINE-1 + participant PINE-2 + + Note right of PEMC-1: 1. PEMC-1, PEMC-2, PEGC, PINE-1 and PINE-2 are part of the PIN. PEMC-1 is currently the PEMC of the PIN. + Note left of PEMC-1: 2. PEMC-1 decides to handover the PEMC role to another PIN element + PEMC-1->>PEMC-2: 3. Request to take the role of PEMC + PEMC-2-->>PEMC-1: 4. Success response to take the role of PEMC + PEMC-1->>PEMC-2: 5. Delivery of PIN dynamic information + PEMC-1->>PIN Server: 6a. PEMC change notification + PEMC-1->>PEGC: 6b. PEMC change notification + PEMC-1->>PINE-1: 6c. PEMC change notification + PEMC-1->>PINE-2: 6d. PEMC change notification + +``` + +Sequence diagram illustrating PEMC replacement triggered internally within the PIN. The diagram shows interactions between PIN Server, PEMC-1, PEMC-2, PEGC, PINE-1, and PINE-2. The process starts with a note that all elements are part of the PIN and PEMC-1 is the current PEMC. PEMC-1 then decides to handover the role, requests it from PEMC-2, receives a success response, and delivers dynamic information. Finally, PEMC-1 sends change notifications to the PIN Server, PEGC, PINE-1, and PINE-2. + +**Figure 7.3.2.3.4-1: PEMC replacement triggered internally within the PIN** + +1. PEMC-1, PEMC-2, PEGC, PINE-1 and PINE-2 are part of same PIN. PEMC-1 is currently the PEMC of the PIN. +2. PEMC-1 decides to relinquish its PEMC role and handover to another PIN element. It may decide if it detects that its UE power is draining or its role as PEMC is nearing expiry. +3. The PEMC-1 looks into the PIN dynamic profile information to identify the new PINE which can take up the role of PEMC (here PEMC-2 PIN element) and requests PEMC-2 to take the role of PEMC. +4. If the PEMC-2 PINE decides to take up the role of PEMC it sends the success response to the PEMC-1. +5. The PEMC-1 updates the PIN dynamic profile information with this role change details and delivers the PIN dynamic profile information to the PEMC-2. +6. The PEMC-1 signals all the PINEs in the PIN including the PEGC and PIN server about the change in the PIN element acting as PEMC and its reachability information. On receiving this notification PIN server and PEGC updates the PIN dynamic profile information with the details of PEMC-2. + +##### 7.3.2.3.5 PEGC replacement triggered by PEMC + +The following solution corresponds to the key issue #6 on PEMC/PEGC replacement in PIN as specified in clause 4.6. + +In some scenarios, like hardware failure, crash or power drain, the current PEGC may not be in a position to indicate to the PIN server or request the PIN server to assign the role of PEGC to another PIN element. In these cases, the PEMC on detecting the unavailability of the PIN element acting as PEGC, need to assign the role to another PINE and transfer the PIN information to the new PEGC. + +Figure 7.3.2.3.5-1 illustrates PEGC replacement procedure triggered by PEMC on detecting current PEGC is unavailable or PEGC role change is required. + +Pre-conditions: + +1. PEGC-2 PIN element has already indicated that it can act as PEGC during the registration process. +2. Dynamic information about the PIN is available at the PEMC + +![Sequence diagram illustrating PEGC replacement triggered by PEMC. Lifelines: PIN Server, PEMC, PEGC-1, PEGC-2, PINE-1, PINE-2. The process involves PEMC detecting PEGC-1 unavailability, requesting PEGC-2 to take over, receiving a success response, notifying the PIN server, updating dynamic information, and then notifying all PINEs about the change.](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant PIN Server + participant PEMC + participant PEGC-1 + participant PEGC-2 + participant PINE-1 + participant PINE-2 + + Note right of PEMC: 1. PEMC, PEGC-1, PEGC-2, PINE-1 and PINE-2 are part of the PIN. PEGC-1 is currently the PEGC of the PIN. + Note left of PEMC: 2. PEMC detects unavailability of PEGC-1 + PEMC->>PEGC-2: 3. Request to take the role of PEGC + PEGC-2-->>PEMC: 4. Success response to take the role of PEGC + PEMC->>PIN Server: 5. PEGC change notification + Note left of PIN Server: 6. PEMC and PIN server updates the PIN dynamic information with the details of PEGC-2 + PEMC->>PEGC-2: 7. Delivery of PIN dynamic information + PEMC->>PINE-1: 8a. PEGC change notification + PEMC->>PINE-2: 8b. PEGC change notification + +``` + +Sequence diagram illustrating PEGC replacement triggered by PEMC. Lifelines: PIN Server, PEMC, PEGC-1, PEGC-2, PINE-1, PINE-2. The process involves PEMC detecting PEGC-1 unavailability, requesting PEGC-2 to take over, receiving a success response, notifying the PIN server, updating dynamic information, and then notifying all PINEs about the change. + +**Figure 7.3.2.3.5-1: PEGC replacement triggered by PEMC** + +1. PEMC, PEGC-1, PEGC-2, PINE-1 and PINE-2 are part of same PIN. PEGC-1 is currently the PEGC of the PIN. +2. The PEMC identifies that PEMC-1 is down or crash or its duration to act as PEGC is ending. How PEMC identifies that the current PINE acting as PEGC is crashed or down is not in the scope of this specification. +3. The PEMC looks into the PIN profile and PIN dynamic information to identify the new PINE which can take up the role of PEGC (here PEGC-2 PIN element) and requests PEGC-2 to take the role of PEGC. +4. If the PEGC-2 PINE decides to take up the role of PEGC it sends the success response to the PEMC. +5. The PEMC notifies the PIN server that PEGC-2 is the new PEGC of the PIN and it is releasing PEGC-1 from its role as PEGC +6. The PEMC and PIN server updates the PIN dynamic information with the relevant details of PEGC-2. +7. The PEMC delivers the PIN dynamic information to the PEGC-2. +- 8a,8b. The PEMC notifies all the PINEs in the PIN about the change in the PIN element acting as PEGC and its reachability information. + +NOTE: The PINEs are considered to be implicitly subscribed for notifying about the changes in the PIN. + +##### 7.3.2.3.6 PIN modification triggered by PEGC + +The current PEGC decides to relinquish the role of PEGC and requests the PIN server to assign the role to other PINE. The PIN server chooses a PINE and assigns the PEGC role to it. + +Figure 7.3.2.3.6-1 illustrates PIN modification procedure triggered by PIN server based on request from the current PEGC. + +Pre-conditions: + +1. The PEGC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEGC has been authorized to communicate with the PIN server; + +![Sequence diagram illustrating the modification of PIN triggered by PEGC. The diagram shows interactions between PIN Server, PEGC(old), PEGC(new), PEMC, and PIN Elements.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant PIN Server + participant PEGC(old) + participant PEGC(new) + participant PEMC + participant PIN Elements + + Note left of PIN Server: 2. Process request + PEGC(old)->>PIN Server: 1. Request to Modify PIN + PIN Server-->>PIN Server: 2. Process request + PIN Server->>PEGC(old): 3. Response to Modify PIN + PIN Server->>PEGC(new): 4. Request to take the role of PEGC + PEGC(new)-->>PIN Server: 5. Success response to take the role of PEGC + PIN Server->>PEGC(new): 6. Delivery of PIN dynamic information + PIN Server->>PEMC: 7a. PEGC change notification + PIN Server->>PIN Elements: 7b. PEGC change notification + Note left of PIN Server: 8a. Update PIN dynamic information + Note right of PEMC: 8b. Update PIN dynamic information + +``` + +Sequence diagram illustrating the modification of PIN triggered by PEGC. The diagram shows interactions between PIN Server, PEGC(old), PEGC(new), PEMC, and PIN Elements. + +**Figure 7.3.2.3.6-1: Modification of PIN triggered by PEGC** + +1. The PEGC (old) sends a PIN modification request to the PIN server to request to change the role of PEGC. The PIN modification request includes the security credentials of the PIN client received during PIN client authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PIN ID. +2. Upon receiving the request, the PIN server performs an authorization check to verify whether the PEGC has authorization to perform the operation. +3. The PIN server sends a successful response to original PEGC, which includes a stop of access control information in PEGC. If the PIN modification request fails, the PIN server should give the failure response to indicates that indicates the cause of PIN modification request failure. After receiving the successful of PIN modification response, the old PEGC stops the routing control of a PIN, which is represented by PIN ID. +4. The PIN server can identify the new PEGC by looking into the capabilities of the PIN elements from PIN dynamic profile information. PIN server requests the PEGC (new) to take the role of PEGC. +5. PEGC (new) if it can take the role of PEGC, sends the success response to the PIN server. +6. PIN server delivers the PIN dynamic profile information to the PEGC (new). +7. PIN server notifies the PEMC and other PIN elements about the change in the PEGC role and its reachability information. +8. PIN server and PEMC updates the PIN dynamic profile information with the details of PEGC (new). + +##### 7.3.2.3.7 PIN modification triggered after local PEMC failure + +An authorised administrator is the owner of a PIN and accesses PIN configuration using an application on a UE, which is one of the PEMC for the PIN. The authorised administrator leaves the local area of the PIN (e.g. in a home) and is able to access the PIN remotely through the 5G network. The authorised administrator is able to manage the PIN through the 5G network. + +Pre-conditions: + +1. The PIN server has authorised the creation of the PIN. +2. The authorised administrator is the owner of the PIN and has created the PIN. +3. The authorised administrator configures PEMC2 to provide PIN management for the PIN. PEMC2 becomes the active PEMC and UE/PEMC1 is an inactive PEMC. +4. PEMC2, PEGC, PINE-1, PINE-2, and the UE/PEMC1 are members of the PIN. PINE-1 has PEMC capability. + +![Sequence diagram for PIN modification after local PEMC failure. Lifelines: UE/PEMC1, 5GC, PIN Server, PEGC, PEMC2, PINE-1, PINE-2. The sequence shows: 1. PEGC notifies PIN Server of PEMC2 failure; 2. UE/PEMC1 sends PIN modification request to PIN Server via 5GC; 3. PIN Server processes request; 4. PIN Server assigns new PEMC (PINE-1); 5. PINE-1 responds; 6. PIN Server notifies other members; 7. PIN Server sends response to UE/PEMC1; 8. PIN communications resume with PINE-1.](fc0735d325f0ebd9214171975c68a888_img.jpg) + +``` + +sequenceDiagram + participant UE/PEMC1 + participant 5GC + participant PIN Server + participant PEGC + participant PEMC2 + participant PINE-1 + participant PINE-2 + + Note right of PEGC: 1. Notify PEMC2 failure + PEGC->>PIN Server: + Note left of UE/PEMC1: 2. PIN modification request + UE/PEMC1->>5GC: + 5GC->>PIN Server: + Note right of PIN Server: 3. Process request + Note right of PIN Server: 4. Assign new PEMC + PIN Server->>PINE-1: + Note right of PINE-1: 5. PEMC assignment response + PINE-1->>PIN Server: + Note right of PIN Server: 6. Management change notification + PIN Server->>5GC: + 5GC->>UE/PEMC1: + Note right of PINE-1: 8. PIN communications + PINE-1->>PINE-2: + +``` + +Sequence diagram for PIN modification after local PEMC failure. Lifelines: UE/PEMC1, 5GC, PIN Server, PEGC, PEMC2, PINE-1, PINE-2. The sequence shows: 1. PEGC notifies PIN Server of PEMC2 failure; 2. UE/PEMC1 sends PIN modification request to PIN Server via 5GC; 3. PIN Server processes request; 4. PIN Server assigns new PEMC (PINE-1); 5. PINE-1 responds; 6. PIN Server notifies other members; 7. PIN Server sends response to UE/PEMC1; 8. PIN communications resume with PINE-1. + +Figure 7.3.2.3.7-1: PIN Modification after local PEMC failure + +1. UE/PEMC1 receives a notification from PEGC that there is a communication failure with PEMC2. +2. An authorised administrator on UE/PEMC1 sends a PIN modification request to the PIN server through the 5G network. The modification request includes the security credentials of the authorised administrator, the UE ID, the PIN ID, PIN member ID, and a request that PINE-1 be assigned the new PEMC. +3. The PIN server processes the modification request and checks if the authorised administrator is allowed to modify the PIN. +4. If the authorised administrator is allowed to perform PIN modification, the PIN server sends a request to PINE-1 to assign PINE-1 as the new PEMC and provides PIN profile and dynamic profile information to PINE-1. +5. PINE-1 returns an accept response to the PIN server. +6. The PIN server notifies the other members of the PIN that PINE-1 will be the new PEMC for the PIN. +7. The PIN server sends a response to the PIN modification request with updated information for the PIN profile and the dynamic profile information. +8. PIN communications resume with PINE-1 serving as the new PEMC. + +##### 7.3.2.3.8 PIN management with multiple PEGCs + +This solution targets KI#1 on PIN management and KI#6 on PEMC/PEGC replacement in PIN, and applies for PIN deployment with a large number of PIN members. In these cases, multiple PIN Elements may be assigned with Gateway Capability to distribute relaying PIN communications among the different PEGCs. The multiple PEGCs in a PIN also provide redundancy for PIN communication should one of the PEGC fails. + +Precondition: + +1. A homeowner creates a PIN and assigns multiple PEGCs for relaying PIN communications. + +![Sequence diagram illustrating Multiple PEGC configuration for a PIN. Lifelines: PINE-2, PINE-1, PEGC-B, PEGC-A, PEMC, PIN Server. The sequence shows PIN creation, establishment, join requests, notifications, and policy updates.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` + +sequenceDiagram + participant PINE-2 + participant PINE-1 + participant PEGC-B + participant PEGC-A + participant PEMC + participant PIN Server + + Note right of PEMC: 1. PIN creation request + PEMC->>PIN Server: 1. PIN creation request + Note over PEGC-B, PEGC-A, PEMC: 2. PIN establishment (PEMC, PEGC-A, PEGC-B) + PEGC-B->>PEMC: 2. PIN establishment (PEMC, PEGC-A, PEGC-B) + PEGC-A->>PEMC: 2. PIN establishment (PEMC, PEGC-A, PEGC-B) + PINE-1->>PEMC: 3. PIN Join request + Note right of PEGC-A: 4a. PEGC Notification + PEGC-A->>PEMC: 4a. PEGC Notification + Note right of PEGC-B: 4b. PEGC Notification + PEGC-B->>PEMC: 4b. PEGC Notification + Note over PINE-1, PEGC-A, PEGC-B: 5. PIN Join response (PEGC-A default PEGC, PEGC-B backup) + PEGC-A->>PINE-1: 5. PIN Join response (PEGC-A default PEGC, PEGC-B backup) + Note over PINE-2, PEGC-B, PEGC-A: 6. PIN Join (PEGC-B default PEGC, PEGC-A backup) + PINE-2->>PEMC: 6. PIN Join (PEGC-B default PEGC, PEGC-A backup) + Note right of PEMC: 7. PIN policy update + PEMC->>PIN Server: 7. PIN policy update + +``` + +Sequence diagram illustrating Multiple PEGC configuration for a PIN. Lifelines: PINE-2, PINE-1, PEGC-B, PEGC-A, PEMC, PIN Server. The sequence shows PIN creation, establishment, join requests, notifications, and policy updates. + +**Figure 7.3.2.3.8-1: Multiple PEGC configuration for a PIN** + +1. A PIN Element with Management Capability, PEMC, requests and is authorized by the PIN server to create a PIN. +2. PEMC creates the PIN and configures PEGC-A and PEGC-B as PIN Element with Gateway Capability. The PIN owner plans to add a large number of devices to the PIN and wants to distribute PIN communications between PEGC-A and PEGC-B to avoid overloading one PEGC. In addition, PEGC-A and PEGC-B can offer redundancy in case either PEGC-A or PEGC-B fails. PEMC sends a PIN profile update to the PIN server of the configuration of PEGC-A and PEGC-B as PEGCs. +3. PINE-1 sends a PIN join request to the PEMC. PIN Client Profile information (required KPIs, location and schedule) is included in the request which PEMC uses to determine the optimal default and backup PEGCs for PINE-1. PEMC assigns PEGC-A as the default PEGC for PINE-1 and PEGC-B as the backup PEGC for PINE-1. PINE-1 will use PEGC-A as the primary PEGC to relay PIN communications and will use PEGC-B to relay PIN communications only if PEGC-A is not available. +4. The PEMC notifies PEGC-A and PEGC-B of their PEGC roles: PEGC-A will serve as the default PEGC and PEGC-B will serve as the backup PEGC for PINE-1. +5. PEMC returns a response to the join request and includes the PEGC configuration that PEGC-A will serve as the default PEGC and PEGC-B will serve as the backup PEGC. +6. Steps 3 to 5 are repeated for PINE-2. PEMC configures that PEGC-B will serve as the default PEGC and PEGC-A will serve as the backup PEGC for PINE-2. +7. PEMC sends a PIN profile update to the PIN server informing the PIN server of the PEGC configurations for PINE-1 and PINE-2. + +##### 7.3.2.3.9 PIN management with multiple PEMCs + +This solution targets KI#1 on PIN management and applicable for PIN with a large number of PIN elements and including multiple PIN elements with management capabilities. In these cases, multiple PIN Elements may be assigned with PEMC role for ease and effective management by the PIN owner or PIN admin. + +Precondition: + +1. A homeowner creates a PIN and configured multiple PEMCs. +2. PEMC-S is assigned with the role of secondary PEMC and PEMC-P is assigned with the role of primary PEMC. +2. PEMC-S has direct connection or PIN direct connection with the PEMC-P. + +![Sequence diagram illustrating PIN management with multiple PEMCs. The diagram shows the interaction between PEMC-S (secondary) and PEMC-P (primary). The steps are: 1. Application layer connection from PEMC-S to PEMC-P; 2. PEMC-S receives a request related to PIN management; 3. PIN Management request from PEMC-S to PEMC-P; 4. PEMC-P checks if the PIN element is authorized to perform the operation; 5. PEMC-P performs the requested operation; 6. PIN Management response from PEMC-P to PEMC-S.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant PEMC-S as PEMC-S (secondary) + participant PEMC-P as PEMC-P (primary) + Note left of PEMC-S: 2. Receives the request related to PIN management + PEMC-S->>PEMC-P: 1. Application layer connection + PEMC-S->>PEMC-P: 3. PIN Management request + Note right of PEMC-P: 4. Checks if the PIN element is authorized to perform the operation + Note right of PEMC-P: 5. Perform the requested operation + PEMC-P->>PEMC-S: 6. PIN Management response + +``` + +Sequence diagram illustrating PIN management with multiple PEMCs. The diagram shows the interaction between PEMC-S (secondary) and PEMC-P (primary). The steps are: 1. Application layer connection from PEMC-S to PEMC-P; 2. PEMC-S receives a request related to PIN management; 3. PIN Management request from PEMC-S to PEMC-P; 4. PEMC-P checks if the PIN element is authorized to perform the operation; 5. PEMC-P performs the requested operation; 6. PIN Management response from PEMC-P to PEMC-S. + +**Figure 7.3.2.3.9-1: PIN management with multiple PEMCs** + +1. The PEMC-S may already have an application layer connection established with PEMC-P. +2. PEMC-S receives a request from PIN owner/PIN admin to perform any of the PIN management operations. These operations could be PIN element removal, PIN element addition, PIN deletion, PIN configuration update etc. +3. PEMC-S prepares the corresponding request including the required details for the requested operation and sends it to PEMC-P. These requests shall carry the PIN client ID of the PEMC-S mandatorily. +4. PEMC-P on receiving the request checks whether the PEMC-S is authorized as secondary PEMC in-order to perform the operation. +5. If the authorization succeeds, PEMC-P proceeds with the requested operation. +6. PEMC-P sends the response to PEMC-S containing the status/result of the requested operation. + +**NOTE:** Only the operations that are required to be performed by the PIN owner/PIN admin can be performed through secondary PEMC and all other operations like PIN discovery, PIN service discovery, authorizing PIN elements to join PIN etc., cannot be handled by the secondary PEMC. + +#### 7.3.2.4 Procedures of PIN Profile retrieval + +The procedure describes how a PEMC queries the PIN server to obtain the information of a PIN that pre-configured or dynamically created by the PEMC. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; + +4. A PIN client has already received the role of PEMC from PIN server; + +![Sequence diagram showing the interaction between a PEMC and a PIN Server. The PEMC sends a '1. PIN profile query request' to the PIN Server, and the PIN Server responds with a '2. Response'.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` + +sequenceDiagram + participant PEMC + participant PIN Server + Note left of PEMC: 1. PIN profile query request + PEMC->>PIN Server: 1. PIN profile query request + Note right of PIN Server: 2. Response + PIN Server-->>PEMC: 2. Response + +``` + +Sequence diagram showing the interaction between a PEMC and a PIN Server. The PEMC sends a '1. PIN profile query request' to the PIN Server, and the PIN Server responds with a '2. Response'. + +**Figure 7.3.2.4-1: Query PIN information** + +1. The PEMC sends PIN Profile Query requests (PEMC ID, PIN ID) to the PIN server. If the PEMC is behind a PEGC, the message is encapsulated in the user plane packet. +2. [Optional] The PIN server determines whether the PEMC is one of the managers of the PIN. The PIN server can have the verification procedure with 5GS. +3. The PIN server responds to the PEMC with the PIN Profile, which includes for example, the PIN name, PIN description, List of Device Info (PINE), PIN duration, PEGC information or others. The device information is the information of PINE that in the PIN. + +### 7.3.3 Solution evaluation + +This solution addresses KI#1 about "Whether and how to triggers a PIN network management request, for example, PIN creating/modifying/deleting? What parameters are required in PIN network management request? ". + +This solution firstly solves the problem that only the PEMC can trigger a PIN network management request. Before the creation of PIN, the PINAPP or UE should be a PEMC first. And, when the PEMC triggers the PIN creating towards PIN server, some of the parameters are needed in the request. + +## 7.4 Solution #3: Insertion and remove of PIN elements in a PIN + +### 7.4.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.4.2 Solution description + +#### 7.4.2.1 General + +This solution addresses aspects of Key Issue #1. + +After the PIN is created by the PEMC, the other PIN elements can be added into the PIN. For the PIN elements that have already added into the PIN, they can be removed from a certain PIN by the PEMC. + +When a PIN element is added into a PIN, the PEMC should configure with the PIN elements with the necessary permission, for example, to be able to access to 5GS via the PEGC. + +Before the PIN element to be added into a PIN, the PEMC should discover the PIN element first, or the PIN element receives the lists of PIN Profile first (for example, the list of PIN ID, PIN description information). + +When a PIN element is added into a PIN, the PINE can indicate the service it can provide. The service includes both the service that PIN client in PINE can provide and the service that application client on PINE can provide. + +#### 7.4.2.2 Procedures + +##### 7.4.2.2.1 PIN client requests to join into a PIN + +Pre-conditions: + +1. The UE (PIN client) has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC; +2. The UE Identifier or PIN client Identifier is available; +3. The PIN client has been authorized to communicate with the PEMC; +4. The PIN client has already received the list of PIN ID, corresponding PEMC IP address; + +For a certain PIN element, it can receive the PIN profile from PEMC. The configuration includes PIN ID, PIN description (Human-readable description of the PIN, for example, the company name, location or the type of service) and the PEMC IP address. + +After receiving the PIN profile from PEMC, the PIN client can decide to join the PIN. + +![Sequence diagram showing the interaction between a PIN client, PEMC, PEGC / PIN elements (Relay), and PIN Server. The PIN client sends an application layer connection and a request to join the PIN to the PEMC. The PEMC performs an authorization check and sends a response. The PEMC then notifies the PIN Server and the PEGC / PIN elements. Finally, the PIN client, PEMC, PEGC / PIN elements, and PIN Server all update their PIN profiles.](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) + +``` + +sequenceDiagram + participant PIN client + participant PEMC + participant PEGC / PIN elements (Relay) + participant PIN Server + + Note left of PIN client: 1. Application Layer connection + PIN client->>PEMC: 2. Request to join the PIN + Note right of PEMC: 3. Authorization + PEMC->>PIN client: 4. Response + Note right of PEMC: 5. Notify + PEMC->>PIN Server: 5. Notify + Note right of PEMC: 6. Notify + PEMC->>PEGC / PIN elements (Relay): 6. Notify + Note right of PIN client: 7. Update the PIN profile + PIN client->>PIN client: 7. Update the PIN profile + Note right of PEGC / PIN elements (Relay): 8. Update the PIN profile + PEGC / PIN elements (Relay)->>PEGC / PIN elements (Relay): 8. Update the PIN profile + Note right of PIN Server: 9. Update the PIN profile + PIN Server->>PIN Server: 9. Update the PIN profile + +``` + +Sequence diagram showing the interaction between a PIN client, PEMC, PEGC / PIN elements (Relay), and PIN Server. The PIN client sends an application layer connection and a request to join the PIN to the PEMC. The PEMC performs an authorization check and sends a response. The PEMC then notifies the PIN Server and the PEGC / PIN elements. Finally, the PIN client, PEMC, PEGC / PIN elements, and PIN Server all update their PIN profiles. + +**Figure 7.4.2.2.1-1: PIN element requests to join a PIN towards PEMC** + +1. The PIN element already has an application layer connection with a PEMC which manages the PIN. + +**NOTE:** If the PIN client communicates with PEMC via WiFi or Bluetooth provided by PEMC, the PEMC can identify the PIN elements by the account number and password that PEMC distributed and the PIN client ID, UE GPSI if available. + +And the PEMC has already send the PIN profile to PIN elements. The configuration includes PIN ID, PIN description (Human-readable description of the PIN, for example, the company name, location or the type of service) and the PEMC IP address. + +2. The PIN client sends the request to PEMC to join the PIN. The request includes the security credentials of the PIN client received during PINAPP authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location, PIN ID and PIN client profile(s) information as shown in Table 7.7.2.2.1-1. The request also includes service that PINE can provide. In the request, both the service that PIN client in PINE can provide and the service that application client on PINE can provide. + +**Editor's note:** The authorization procedure between PIN client and PEMC should be captured in SA3 scope. + +3. Upon receiving the request, the PEMC performs an authorization check to verify whether the PIN client has authorization to join the PIN. + +4. The PEMC sends a successful response to PIN client. Also, the access control information for the PIN client is also included, for example, user name, account, SSID, BSSID. All the information is used by PIN elements (PINAPP) in PIN to access 5G or access other application outside of PIN. The PEMC also provides lifetime of the PIN, identity, address of PEGC and may also provide unique PIN client ID to identify the PIN element within a PIN. + +**Editor's note:** The access control information should be coordinated with SA2 for further study. + +5. The PEMC notifies the PIN server containing the details of the new PIN client that joined the PIN +6. The PEMC notifies the PEGC and other PIN elements containing the details of the new PIN client that joined the PIN. And the PEGC decides to enables the PINE to access 5GS. +7. The PEMC updates PIN profile with the details of the new PIN client that joined the PIN and the service that the PINE can provide. +8. The PEGC updates the PIN profile with the details of the new PIN client that joined the PIN and the service that the PINE can provide. +9. The PIN server updates the PIN profile with the details of the new PIN client that joined the PIN and the service that the PINE can provide. + +##### 7.4.2.2.2 The PEMC removes the PIN elements from a PIN + +Pre-conditions: + +1. The PIN client has already been added into a PIN; +2. The UE Identifier or PIN client Identifier is available; +3. The PIN client has been authorized to communicate with the PEMC; + +The PEMC can decide to remove a PIN client from a PIN, for example, the PIN client may not belong to the group. + +![Sequence diagram showing the removal of a PIN element from a PIN by PEMC. The diagram involves four lifelines: PIN client, PEMC, PEGC, and PIN server. The sequence of messages is: 1. Application Layer connection from PIN client to PEMC; 2. PEMC removes the PIN client from the PIN (internal message); 3. Notification from PEMC to PIN client; 4. Notification from PEMC to PEGC; 5. Notification from PEMC to PIN server; 6. Update the PIN profile (internal message for PEMC); 7. Update the PIN profile (internal message for PEGC); 8. Update the PIN profile (internal message for PIN server).](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +``` + +sequenceDiagram + participant PIN client + participant PEMC + participant PEGC + participant PIN server + Note left of PIN client: 1. Application Layer connection + PIN client->>PEMC: + Note right of PEMC: 2. PEMC removes the PIN client from the PIN + PEMC->>PIN client: 3. Notification + PEMC->>PEGC: 4. Notification + PEMC->>PIN server: 5. Notification + Note right of PEMC: 6. Update the PIN profile + Note right of PEGC: 7. Update the PIN profile + Note right of PIN server: 8. Update the PIN profile + +``` + +Sequence diagram showing the removal of a PIN element from a PIN by PEMC. The diagram involves four lifelines: PIN client, PEMC, PEGC, and PIN server. The sequence of messages is: 1. Application Layer connection from PIN client to PEMC; 2. PEMC removes the PIN client from the PIN (internal message); 3. Notification from PEMC to PIN client; 4. Notification from PEMC to PEGC; 5. Notification from PEMC to PIN server; 6. Update the PIN profile (internal message for PEMC); 7. Update the PIN profile (internal message for PEGC); 8. Update the PIN profile (internal message for PIN server). + +**Figure 7.4.2.2.2-1: Remove a PIN element from a PIN by PEMC** + +1. The PIN element already has an application layer connection with a PEMC which manages the PIN. +2. The PEMC decides to remove a PIN client from a PIN which indicated by PIN client ID or UE GPSI. +3. The PEMC sends the notification to PIN client to notify that the PIN client is included in the PIN any more. +4. The PEMC notifies the PEGC containing the details of the PIN client that has been removed from the PIN. +5. The PEMC notifies the PIN server containing the details of the PIN client that has been removed from the PIN. + +6. The PEMC updates the PIN profile to remove the details of the PIN client that has been removed from the PIN. +7. The PEGC updates the PIN profile to remove the details of the PIN client that has been removed from the PIN. The PEGC disable this PIN client to access 5GS. +8. The PIN server updates the PIN profile to remove the details of the PIN client that has been removed from the PIN. + +##### 7.4.2.2.3 The PIN elements decides to leave the PIN + +Pre-conditions: + +1. The PIN client has already been added into a PIN; +2. The UE Identifier or PIN client Identifier is available; +3. The PIN client has been authorized to communicate with the PEMC; + +The PIN client can decide to leave a PIN, for example, the PIN client has long route to the PIN and is not received service from PIN. + +![Sequence diagram showing the PIN client deciding to leave a PIN. The diagram involves four lifelines: PIN client, PEMC, PEGC, and PIN Server. The sequence of messages is: 1. Application Layer connection (PIN client to PEMC), 2. PIN client requests to leave the PIN (PIN client to PEMC), 3. PEMC authorization (PEMC internal), 4. Response (PEMC to PIN client), 5. Notification (PEMC to PEGC), 6. Notification (PEMC to PIN Server), 7. Update the PIN profile (PEMC internal), 8. Update the PIN profile (PEGC internal), 9. Update the PIN profile (PIN Server internal).](1ad662a678c4f002de911d403f00de8e_img.jpg) + +``` + +sequenceDiagram + participant PIN client + participant PEMC + participant PEGC + participant PIN Server + Note left of PIN client: 1. Application Layer connection + PIN client->>PEMC: 2. PIN client requests to leave the PIN + Note right of PEMC: 3. PEMC authorization + PEMC->>PIN client: 4. Response + Note right of PEMC: 5. Notification + PEMC->>PEGC: 5. Notification + Note right of PEMC: 6. Notification + PEMC->>PIN Server: 6. Notification + Note right of PEMC: 7. Update the PIN profile + Note right of PEGC: 8. Update the PIN profile + Note right of PIN Server: 9. Update the PIN profile + +``` + +Sequence diagram showing the PIN client deciding to leave a PIN. The diagram involves four lifelines: PIN client, PEMC, PEGC, and PIN Server. The sequence of messages is: 1. Application Layer connection (PIN client to PEMC), 2. PIN client requests to leave the PIN (PIN client to PEMC), 3. PEMC authorization (PEMC internal), 4. Response (PEMC to PIN client), 5. Notification (PEMC to PEGC), 6. Notification (PEMC to PIN Server), 7. Update the PIN profile (PEMC internal), 8. Update the PIN profile (PEGC internal), 9. Update the PIN profile (PIN Server internal). + +Figure 7.4.2.2.3-1: PIN client decides to leave a PIN + +1. The PIN element already has an application layer connection with a PEMC which manages the PIN. +2. The PIN client decides to leave a PIN, and sends the request to PEMC to leave the PIN. The request includes the security credentials of the UE or PIN client received during PINAPP authorization procedure and may include the UE identifier such as GPSI, PIN client ID, UE location and PIN ID. + +**Editor's note:** The authorization procedure between PIN client and PEMC should be captured in SA3 scope. + +3. The PEMC authorizes the request, and decides to remove a PIN client from a PIN which indicated by PIN client ID or UE GPSI. +4. The PEMC sends the response to PIN client to notify that the PIN client may not be included in the PIN anymore.5. The PEMC notifies the PEGC containing the details of the PIN client that requested to leave the PIN. +5. The PEMC notifies the PIN server containing the details of the PIN client that requested to leave the PIN. +6. The PEMC updates the PIN profile and remove the details of the PIN client that requested to leave the PIN. +7. The PEGC updates the PIN profile to remove the details of the PIN client that requested to leave the PIN. The PEGC disable this PIN client to access 5GS. +8. The PIN server updates the PIN profile to remove the details of the PIN client that requested to leave the PIN. + +## 7.5 Solution #4: PIN delete + +### 7.5.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.5.2 Solution description + +#### 7.5.2.1 General + +This solution addresses aspects of Key Issue #1. + +For an established PIN, the PIN can be deleted by the following situation: + +- Decided by PEMC. The PEMC of a PIN decides to delete the PIN and sends request to PIN server. The PIN server accepts the requests and deletes the PIN. The PIN elements in this PIN can't access to 5GS via PEGC anymore. +- Decided by PIN server. For each PIN, it has the life cycle that the PIN can exists. If the PIN has been in existence for longer than the life cycle, the PIN server can decide to delete the PIN and release the resource. + +After the delete of PIN, the PIN elements in PIN can't access to other PIN elements or application server via PEGC by 5GS. + +Due to the PEMC can store the lifecycle of a PIN locally, and when the lifecycle of PIN comes to the end, the PEMC can directly delete the PIN locally and without authorized by PIN server. After the PIN is deleted by PEMC, the PEMC can update the status of PIN to PIN server. + +#### 7.5.2.2 Procedures of Delete of PIN + +##### 7.5.2.2.1 PIN delete triggered by PEMC + +The PEMC can trigger the PIN delete to PIN server that the PIN doesn't need any more. + +Figure 7.5.2.2.1-1 illustrates PIN delete procedure based on request/response model. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; +4. A PIN client has already received the role of PEMC from PIN server; + +![Sequence diagram for Figure 7.5.2.2.1-1: Delete of PIN triggered by PEMC. The diagram shows four lifelines: PIN elements, PEGC, PEMC, and PIN server (AF). The sequence of messages is: 1. PEMC sends a 'Request of delete of PIN' to the PIN server (AF). 2. The PIN server (AF) performs an internal 'Process request'. 3. The PIN server (AF) sends a 'Response of delete of PIN' back to the PEMC. 4. The PEMC sends a 'PIN delete notification' to the PEGC. 5. The PEGC sends a 'PIN delete notification' to the PIN elements.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant PIN elements + participant PEGC + participant PEMC + participant PIN server (AF) + Note right of PIN server (AF): 2. Process request + PEMC->>PIN server (AF): 1. Request of delete of PIN + PIN server (AF)-->>PEMC: 3. Response of delete of PIN + PEMC->>PEGC: 4. PIN delete notification + PEGC->>PIN elements: 5. PIN delete notification + +``` + +Sequence diagram for Figure 7.5.2.2.1-1: Delete of PIN triggered by PEMC. The diagram shows four lifelines: PIN elements, PEGC, PEMC, and PIN server (AF). The sequence of messages is: 1. PEMC sends a 'Request of delete of PIN' to the PIN server (AF). 2. The PIN server (AF) performs an internal 'Process request'. 3. The PIN server (AF) sends a 'Response of delete of PIN' back to the PEMC. 4. The PEMC sends a 'PIN delete notification' to the PEGC. 5. The PEGC sends a 'PIN delete notification' to the PIN elements. + +**Figure 7.5.2.2.1-1: Delete of PIN triggered by PEMC** + +1. The PEMC sends a PIN delete request to the PIN server to request to delete the PIN. The PIN delete request includes the security credentials of the PIN client received during PIN client authorization procedure and PIN ID. The PIN ID indicates this PIN will be deleted. + +**Editor's note:** The security credentials design and the authorization procedure is in the scope of SA3. + +2. Upon receiving the request, the PIN server validates the PIN delete request and verifies the security credentials. +3. Upon successful authorization, the PIN server sends a successful delete response. + +After the PIN is deleted which is indicated by PIN ID, the access control information in PEGC is also disabled and the PIN elements in this PIN can't access to 5GS via PEGC anymore when the PIN is deleted. The PEGC may not be the gateway and for PIN element to access to 5GS for this PIN. + +4. Before the PIN deleted, the PEMC notifies the PEGC of PIN delete that identified by PIN ID, and PEGC disables the 5GS connection permission and access control information for the PIN elements in this PIN. +5. Before the PIN deleted, the PEMC notifies the PIN elements in this PIN of PIN delete that identified by PIN ID. The PIN elements in this PIN can delete the information about this PIN, for example, the PIN profile. + +##### 7.5.2.2.2 PIN delete triggered by PIN server + +The PIN server can trigger the PIN delete procedure, for example, when the life cycle of PIN is end or the PIN server decides to stop the PIN service in this PIN. + +Figure 7.5.2.2.2-1 illustrates PIN delete procedure based on request/response model. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; +4. A PIN client has already received the role of PEMC from PIN server; +5. It is assumed that PIN server manages the PIN life cycle; + +![Sequence diagram illustrating the delete of PIN triggered by PIN server. The diagram shows four lifelines: PIN elements, PEGC, PEMC, and PIN server (AF). The sequence of messages is: 1. PIN server (AF) decides to delete the PIN; 2. PIN server (AF) sends a PIN delete notification to PEMC; 3. PEMC sends a PIN delete notification to PEGC; 4. PEMC sends a PIN delete notification to PIN elements.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant PIN elements + participant PEGC + participant PEMC + participant PIN server (AF) + Note right of PIN server (AF): 1. PIN server decides to delete the PIN + PIN server (AF)->>PEMC: 2. PIN delete notification + PEMC->>PEGC: 3. PIN delete notification + PEMC->>PIN elements: 4. PIN delete notification + +``` + +Sequence diagram illustrating the delete of PIN triggered by PIN server. The diagram shows four lifelines: PIN elements, PEGC, PEMC, and PIN server (AF). The sequence of messages is: 1. PIN server (AF) decides to delete the PIN; 2. PIN server (AF) sends a PIN delete notification to PEMC; 3. PEMC sends a PIN delete notification to PEGC; 4. PEMC sends a PIN delete notification to PIN elements. + +**Figure 7.5.2.2.2-1: Delete of PIN triggered by PIN server** + +1. An event occurs at the PIN server that satisfies trigger conditions for notifying a subscribed PEMC of a PIN. If the life cycle of a PIN is end or the PIN server decides to not provide any PIN service in this PIN, the PIN server should trigger a PIN delete procedure to the PEMC which manages the PIN. +2. The PIN server sends PIN delete notification to the PEMC. The PIN server includes the PIN ID, security credentials in the notification. + +After the PIN is deleted which is indicated by PIN ID, the access control information in PEGC is also disabled and the PIN elements in this PIN can't access to 5GS via PEGC anymore when the PIN is deleted. The PEGC may not be the gateway and for PIN element to access to 5GS for this PIN. + +**Editor's note: The access control information in PEGC should be coordinated with SA2.** + +3. Before the PIN deleted, the PEMC notifies the PEGC of PIN delete that identified by PIN ID, and PEGC disables the 5GS connection permission and access control information for the PIN elements in this PIN. +4. Before the PIN deleted, the PEMC notifies the PIN elements in this PIN of PIN delete that identified by PIN ID. The PIN elements in this PIN can delete the information about this PIN, for example, the PIN profile. + +##### 7.5.2.2.3 PIN delete locally by PEMC + +The PEMC can directly trigger the PIN delete procedure, for example, when the life cycle of PIN is end, without authorization from PIN server. After the PIN is deleted successfully, the PEMC updates the PIN status to PIN server. + +Figure 7.5.2.2.3-1 illustrates PIN delete procedure based on request/response model. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; +4. A PIN client has already received the role of PEMC from PIN server; +5. It is assumed that PEMC manages or stores the PIN life cycle; + +![Sequence diagram for 'Delete of PIN locally by PEMC'. Lifelines: PIN elements, PEGC, PEMC, PIN server (AF). The sequence starts with a self-call on PEMC (0. The lifecycle of PIN comes to the end), followed by another self-call (1. PEMC deletes the PIN locally and the related PIN profile of this PIN). Then, PEMC sends a message to PEGC (2. Deactivate the access control information of this PIN), which responds (3. Response). PEMC then sends a message to PIN elements (4. Trigger to update the PIN profile in PINE). Next, PEMC sends a message to PIN server (AF) (5. Update the status of PIN), which responds (6. Response). Finally, a self-call on PIN server (AF) occurs (7. PIN profile update).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant PIN elements + participant PEGC + participant PEMC + participant PIN server (AF) + + Note right of PEMC: 0. The lifecycle of PIN comes to the end + Note right of PEMC: 1. PEMC deletes the PIN locally and the related PIN profile of this PIN + PEMC->>PEGC: 2. Deactivate the access control information of this PIN + PEGC-->>PEMC: 3. Response + PEMC->>PIN elements: 4. Trigger to update the PIN profile in PINE + PEMC->>PIN server (AF): 5. Update the status of PIN + PIN server (AF)-->>PEMC: 6. Response + Note right of PIN server (AF): 7. PIN profile update + +``` + +Sequence diagram for 'Delete of PIN locally by PEMC'. Lifelines: PIN elements, PEGC, PEMC, PIN server (AF). The sequence starts with a self-call on PEMC (0. The lifecycle of PIN comes to the end), followed by another self-call (1. PEMC deletes the PIN locally and the related PIN profile of this PIN). Then, PEMC sends a message to PEGC (2. Deactivate the access control information of this PIN), which responds (3. Response). PEMC then sends a message to PIN elements (4. Trigger to update the PIN profile in PINE). Next, PEMC sends a message to PIN server (AF) (5. Update the status of PIN), which responds (6. Response). Finally, a self-call on PIN server (AF) occurs (7. PIN profile update). + +**Figure 7.5.2.2.3-1: Delete of PIN locally by PEMC** + +0. The PEMC stores the lifecycle of PIN locally, and the lifecycle of PIN which indicated by PIN ID comes to the end. +1. The PEMC deletes the PIN which indicated by PIN ID locally, and the information in PIN profile related to this PIN is deleted too. +2. The PEMC indicates the PEGC to deactivate the access control information of this PIN. After the deactivation, the PINE in this PIN can't access the 5GS any more. +3. The PEGC sends response to PEMC that the access control information has been deactivated successfully. +4. The PEMC sends requests to PINE in this PIN to delete the PIN profile related to this PIN that represented by PIN ID. +5. The PEMC sends a PIN status update notification to the PIN server to indicate the PIN has been deleted. In this notification, the PIN ID is included. +6. The PIN server responses to the notification. +7. The PIN server updates the PIN profile to remove the details of the PIN which represented by PIN ID. + +## 7.6 Solution #5: PIN discovery + +### 7.6.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.6.2 Solution description + +#### 7.6.2.1 General + +This solution addresses aspects of Key Issue #1. + +For a certain PIN element, the PIN should be discovered and the PIN element can decide whether to join in the PIN. There are three situations that the PIN elements can discover the PIN as following: + +- If the PIN elements can have an application layer communication with the PEMC which manages a PIN, the PIN elements can receive the PIN ID, PIN description and the PIN service that a PIN can provide, and decides whether to join the PIN; +- The PEGC can be set as open access and the PIN element can communicate with PIN server to receive the PIN ID, PIN description and the PIN service that a PIN can provide from PIN server via the PEGC. + +#### 7.6.2.2 Procedures of PIN discovery + +##### 7.6.2.2.1 Procedures of PIN discovery based on PEMC + +Pre-conditions: + +1. The UE Identifier or PIN client Identifier is available; +2. The PIN client has been authorized to communicate with the PEMC; +3. The UE or PIN client has already received the role of PEMC from PIN server; + +If the PIN element has already had a communication connection with the PEMC, which manages a PIN, the PIN element can receive the PIN ID, PIN description information and IP address of PEMC and decides whether to join the PIN. + +![Sequence diagram showing the procedures of PIN discovery based on PEMC. The diagram involves two main lifelines: PIN client and PEMC. The sequence of messages is: 1. Application layer connection (from PIN client to PEMC), 2. PIN discovery request (from PIN client to PEMC), 3. Authorization (from PEMC to PIN client), and 4. PIN discovery response (from PEMC to PIN client).](63a2519518616620ef0e53d98b923c05_img.jpg) + +``` +sequenceDiagram + participant PIN client + participant PEMC + Note right of PEMC: 3. Authorization + PIN client->>PEMC: 1. Application layer connection + PIN client->>PEMC: 2. PIN discovery request + PEMC->>PIN client: 4. PIN discovery response +``` + +Sequence diagram showing the procedures of PIN discovery based on PEMC. The diagram involves two main lifelines: PIN client and PEMC. The sequence of messages is: 1. Application layer connection (from PIN client to PEMC), 2. PIN discovery request (from PIN client to PEMC), 3. Authorization (from PEMC to PIN client), and 4. PIN discovery response (from PEMC to PIN client). + +Figure 7.6.2.2.2-1: Procedures of PIN discovery based on PEMC + +1. The PIN element has already had an application layer connection with a PEMC which manages a PIN. + +If the PIN client communicates with PEMC via WiFi provided by PEMC, the PEMC can identify the PIN elements by the account number and password that PEMC distributed and the PIN client ID, UE GPSI if available. + +If the PIN client communicates with PEMC via Bluetooth provided by PEMC, the PEMC can identify the PIN elements by the PIN client ID, UE GPSI if available. + +NOTE: The RAT (e.g. wifi) between the PIN client and the PEGC/PEMC is out of scope of SA6 + +2. The PIN client sends the PIN discovery request to PEMC. The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI if available, PIN client ID, UE location, the service that PINE wants to consume and PIN client profile(s) information + +3. The PEMC performs an authorization check to verify whether PINE is allowed to perform the operation. + +**Editor's note:** The authorization and authentication procedure should be defined in SA3 and wait for SA3 to reply. + +4. The PEMC sends the PIN discovery response to PIN element including the configuration information of the PIN(s), which are offering the services requested by the PINE in the PIN discovery request. The configuration information includes PIN ID, PIN description (Human-readable description of the PIN, for example, the company name, location or the type of service) , services that each PIN can provide and the PEMC IP address. + +The PIN client receives the configuration information and decides whether to join in the PIN. + +##### 7.6.2.2.2 Procedures of PIN discovery with assistance of PIN server via PEGC + +Due to for some of the PIN elements can have the application interaction towards the PEGC, for example, via WiFi or Bluetooth pairing, and the PIN element can have the communication with PIN server to receive the lists of PIN ID and corresponding PIN description information. And the PIN elements can decide whether to join in the PIN. + +Figure 7.6.2.2.2-1 illustrates PIN server discovery via PEGC based on request/response model. + +Pre-conditions: + +1. The PIN elements or PIN client has application layer connection with PEGC; +2. The UE Identifier or PIN client Identifier is available; +3. The PEGC has been authorized to communicate with the PIN server; + +![Sequence diagram illustrating PIN discovery via PEGC. The diagram shows three lifelines: PIN client, PEGC, and PIN server. The sequence of messages is: 1. application layer connection (from PIN client to PEGC), 2. PIN discovery request (from PIN client to PIN server via PEGC), 3. PIN server authorization (internal to PIN server), and 4. PIN discovery response (from PIN server to PIN client via PEGC).](ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg) + +``` + +sequenceDiagram + participant PIN client + participant PEGC + participant PIN server + Note right of PIN server: 3. PIN server authorization + PIN client->>PEGC: 1. application layer connection + PIN client->>PIN server: 2. PIN discovery request + PIN server-->>PIN client: 4. PIN discovery response + +``` + +Sequence diagram illustrating PIN discovery via PEGC. The diagram shows three lifelines: PIN client, PEGC, and PIN server. The sequence of messages is: 1. application layer connection (from PIN client to PEGC), 2. PIN discovery request (from PIN client to PIN server via PEGC), 3. PIN server authorization (internal to PIN server), and 4. PIN discovery response (from PIN server to PIN client via PEGC). + +**Figure 7.6.2.2.2-1: PIN discovery via PEGC** + +1. (optional) The PIN element or PIN clients has already had the application layer connection towards PEGC. For example, the PIN elements can communicate with PEGC via WiFi or Bluetooth. + +The PIN client can communicate with the PIN server via PEGC. + +If the PIN client communicates with PEGC via WiFi provided by PEGC, the PEGC can identify the PIN elements by the account number and password that PEGC distributed and the PIN client ID, UE GPSI if available. + +If the PIN client communicates with PEGC via Bluetooth provided by PEGC, the PEGC can identify the PIN elements by the PIN client ID, UE GPSI if available. + +NOTE 1: The RAT (e.g. wifi) between the PIN client and the PEGC/PEMC is out of scope of SA6 + +NOTE 2: The PEGC can serve the PIN client which triggers the PIN discovery via relay PEGC. + +2. The PIN client sends the PIN discovery request to PIN server. The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI, PIN client ID, UE location, the service that PINE wants to consume and PIN client profile(s) information. + +The PIN client can have the filter information in the PIN discovery request for example, the interesting area, the interesting type of PIN and etc. + +3. Upon receiving the request, the PIN server performs an authorization check to verify whether the PIN client has authorization to perform the operation. +4. The PIN server sends a successful response to PIN client, which includes the configuration information to PIN elements. The configuration includes PIN ID, PIN description (Human-readable description of the PIN, for example, the company name, location or the type of service) , services that each PIN can provide and the corresponding PEMC IP address. + +## 7.7 Solution #6: PIN Profile + +### 7.7.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.7.2 Solution description + +#### 7.7.2.1 General + +This solution addresses aspects of Key Issue #1. + +For an established PIN, the PIN should have the profile or configuration information in PIN server, PEMC and PEGC. + +Also the PIN server, PEMC and PEGC shall maintain the dynamic profile information related to the PIN which needs to be updated based on the events (e.g. PIN element joining or leaving, PIN element capability is changed) occurring in the PIN. + +#### 7.7.2.2 PIN Profile in a PIN + +**Table 7.7.2.2.1-1: PIN Profile in PIN server, PEMC, PEGC and PINE** + +| Parameter Name | Parameter Description | PIN Server | PEMC | PEGC | PINE | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------|------|------| +| PIN ID | The identifier of the PIN | Y | Y | Y | Y | +| PIN Description | Human-readable description of the PIN, for example, the company name, location or the type of service. | Y | Y | Y | Y | +| Duration | Specifies the time period of how long the PIN can be active | Y | Y | Y | Y | +| Maximum number of PIN elements | Maximum number of PIN elements allowed to join the PIN | Y | Y | N | N | +| PIN service | List of service that a PIN can provide, including the PINE service or the service that can provided by application client on PINE:<br>> PIN service Provider Identifier<br>> PIN service type<br>> PIN service Feature | Y | Y | N | Y | +| PEMC list | The list of identifiers of the PIN elements which can be allowed to take the role as PEMC (e.g.: PIN client ID, UE GPSI etc.,) and also it contains whether the role is primary or secondary | Y | Y | Y | Y | +| PEGC ID list | The list of identifiers of the PIN elements which can be allowed to take the role as PEGC (e.g.: PIN client ID, UE GPSI etc.,) | Y | Y | Y | Y | +| PIN Server ID | The identifier of the PIN server that serves the PIN | N | Y | Y | Y | +| PIN server Endpoint | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the PIN server. | N | Y | Y | Y | +| PIN Elements List | List of PIN elements which can be allowed to join the PIN<br>> PIN element ID | Y | Y | Y | N | + +#### 7.7.2.3 Dynamic profile information of a PIN + +Table 7.7.2.3-1 describes the list of parameters that are classified as dynamic profile information and which are maintained at the PIN server, PEMC and PEGC. Dynamic profile information maintained at these entities are updated based on the following events occurring in the PIN: + +- PINE joins or leaves the PIN; +- Role of PEMC or PEGC changes; +- When the services offered by the PIN changes; +- When a PINE updates the services it offers; +- When a PINE joins or leaves the PIN; + +Table 7.7.2.3-1: Dynamic profile information of a PIN + +| Parameter Name | Parameter Description | PIN Server | PEMC | PEGC | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------|------| +| PIN ID | The identifier of the PIN | Y | Y | Y | +| PIN Description | Human-readable description of the PIN, for example, the company name, location or the type of service. | Y | Y | Y | +| Services offered | List of services offered by the PIN | Y | Y | N | +| Duration | Time period specifying how long the PIN can be active | | | | +| PEMC list | The list of identifiers of the PIN elements which are currently serving as PEMC (e.g.: PIN client ID, UE GPSI etc.,) and whether the PEMC is authorized as primary PEMC or secondary PEMC | Y | Y | Y | +| > PEMC Endpoint | Endpoint information of each PEMC (e.g. URI, FQDN, IP address) used to communicate with the PEMC. | | | | +| > Duration | Time period of being PEMC | | | | +| PEGC list | The list of identifiers of the PIN elements which are currently serving as PEGC (e.g.: PIN client ID, UE GPSI etc.,) | Y | Y | Y | +| > PEGC Endpoint | Endpoint information of each PEGC (e.g. URI, FQDN, IP address) used to communicate with the PEGC. | | | | +| > Duration | Time period of being PEGC | | | | +| > PEGC Supported KPIs | KPIs supported by this PEGC (e.g., maximum number of assigned PIN elements) | Y | Y | Y | +| > PEGC Schedule | Scheduled times when this PEGC is available to service PIN elements (e.g., time window). | Y | Y | Y | +| > PIN Elements details | List of PIN elements being served by PEGC and their connectivity information | | | | +| PIN Server ID | The identifier of the PIN server that serves the PIN | N | Y | Y | +| PIN server Endpoint | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the PIN server. | N | Y | Y | +| PIN Elements List | List of PIN elements currently registered/joined the PIN | Y | Y | N | +| > PIN Element ID | Identity of the PIN element | | | | +| > Services offered | Services offered by the the PIN element | | | | +| > Reachability information | Reachability information of the PIN element | | | | +| > Application List | List of application clients for this PIN element including:<br><br>> Minimum KPIs required by each application client to operate effectively within the PIN (e.g., PIN bandwidth, PIN request rate, PIN response time)<br><br>> Operational schedules of each application client (e.g., time windows) | Y | Y | Y | +| > Default PEGC | Identifier of the default PEGC authorized to service this PIN element. The PIN element will use this PEGC as the primary PEGC to relay PIN communications. Location and/or schedule information for the default PEGC may also be included such that the default PEGC may be selected by the PIN element based on its current location and proximity to the default PEGC and/or the availability schedule of the default PEGC. | Y | Y | Y | +| > Backup PEGCs List | Identifiers of backup PEGCs authorized to service this PIN element. The list is in prioritized order (the first PEGC listed will serve as the first backup PEGC). If the default PEGC is not available, the PIN element will use this prioritized list of PEGCs to relay PIN communications.-Location and/or schedule information for each of the backup PEGCs may also be included such that a backup PEGC may be selected by the PIN element based on its current location and proximity to a backup PEGC and/or the availability schedule of the PEGC. | Y | Y | Y | + +#### 7.7.2.4 PIN client profile + +Table 7.7.2.4-1 describes the list of PIN element maintained by a PIN client. These parameters are exchanged between the PIN client and PEMC (e.g., when the PIN client is joining or registering to the PIN). Depending on the parameter, the PIN client or the PEMC may configure the value of the parameter during the PIN client and PEMC exchange. + +**Table 7.7.2.4-1: PIN Client Profile** + +| Parameter Name | Status | Parameter Description | +|----------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PIN ID | M | The identifier of the PIN where the PIN client is joined | +| UE identifier | O | PIN Element or UE identifier | +| PIN client ID | M | The unique identity of the PIN client within PIN | +| Name of the device | O | Human-readable name of the device (i.e. door sensor, watch, smart TV, etc) along with manufacturer details | +| Access control information | O | Used for PINE to access the network provided by PEGC. Used for PEGC to control the PINE to access 5GS. Each PIN may be associated with different access control information.<br>> user name, account, SSID, BSSID | +| Application List | O | List of application identities | +| > Application Identity | O | Identity of the application | +| > Application schedule | O | Operational schedules of each application (e.g., time windows) which the | +| > Application KPIs | O | Minimum KPIs required by each application to operate effectively within the PIN (e.g., PIN bandwidth, PIN request rate, PIN response time) | +| capabilities | M | capabilities of the PIN client like supports relay capability for other PIN elements | +| Visibility | M | Determines whether this PIN element is discoverable by other PIN elements within PIN, discoverable by other UEs outside the PIN etc., | +| access type | M | Access type supported for the communication | +| Layer-2 details | O | Layer-2 address of the PIN element | +| Required services | O | Identifies the list of services the PINE wants to consume | +| Supported services | O | Identifies the list of services the PINE is providing and allowed to be accessed | +| Default PEGC | MO | Identifier of the default PEGC assigned by the PEMC to the PIN element. The PIN element will use this PEGC as the primary PEGC to relay PIN communications. Location and/or schedule information for the default PEGC may also be included such that the default PEGC may be selected by the PIN element based on its current location and proximity to the default PEGC and/or the availability schedule of the default PEGC. | +| Backup PEGCs list | O | Identifiers of backup PEGCs assigned by the PEMC to the PIN element. The list is in prioritized order (the first PEGC listed will serve as the first backup PEGC). If the default PEGC is not available, the PEGC will use this prioritized list of PEGCs to relay PIN communications. Location and/or schedule information for each of the backup PEGCs may also be included such that a backup PEGC may be selected by the PIN element based on its current location and proximity to a backup PEGC and/or the availability schedule of the PEGC. | + +### 7.7.3 Solution evaluation + +This solution captures the details of the information that needs to be maintained at the each entities that are part of the PIN. PIN profile and PIN dynamic profile information are maintained at the PIN server, PEMC and PEGC. PIN profile information is maintained till the life time of the PIN i.e., until it is deleted. PIN dynamic profile information is maintained till the PIN is in active state and it is updated based on the events occurring in the PIN. PIN elements sends the PIN client profile while joining or registering to the PIN. + +## 7.8 Solution #7: PIN server discovery + +### 7.8.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.8.2 Solution description + +#### 7.8.2.1 General + +This solution addresses aspects of Key Issue #1. + +Before the PEMC triggers the PIN establishment, or the PEMC triggers PIN modification or PIN delete, a certain PIN server should be discovered. The PIN server is responsible to perform the request of PIN create, PIN modification and PIN delete from PEMC of a PIN. + +Due to the PIN server in a PLMN can be multiple, so it is important to PIN elements to discover the appropriate PIN server to connect. + +#### 7.8.2.2 Procedures of PIN server discovery + +##### 7.8.2.2.1 Procedures of PIN server discovery based on receiving PIN server endpoint information + +The aim of PIN server discovery procedure is to receive one or more endpoint information (e.g. URI(s), FQDN(s), IP address(es)) of PIN server. And the PEMC, PEGC, PIN elements are all able to receive the PIN server endpoint information. + +The PIN server can be discovered by the following method: + +- pre-configured in the PIN elements or PIN clients; +- configured by the user; +- provisioned by MNO through 5GC procedure; or +- derived from HPLMN identifier for non-roaming scenario or from VPLMN identifier for roaming scenario. + +It may be possible to provide the PIN server endpoint information to the PIN client or PIN elements from the 5GC. If the PIN server endpoint information is provided by 5GC and available at the PEMC, the PEMC shall use the information for the PIN management procedure (e.g.: PIN creation/modification/delete). + +Otherwise, the PEMC shall use pre-configured PIN server endpoint information for PIN management procedure if pre-configured PIN server endpoint information is available in PEMC. + +##### 7.8.2.2.2 Procedures of PIN server discovery via PEGC + +Due to for some of the PIN elements can have the application interaction towards the PEGC, for example, via WiFi or Bluetooth pairing, so the PEGC can provide the PIN server end point information to PIN elements. + +For some of the PEGC, it has the open access capability to accept the application layer connection from the PIN elements. + +Figure 7.8.2.2.2.-1 illustrates PIN server discovery via PEGC based on request/response model. + +Pre-conditions: + +1. The PIN elements or PIN client has application layer connection with PEGC; +2. The UE Identifier or PIN client Identifier is available; + +![Sequence diagram for PIN server discovery via PEGC. Lifelines: PINE, PEGC, PEMC. The sequence starts with an application layer connection between PINE and PEGC. PINE sends a PIN server discovery request to PEGC. PEGC can respond directly or route the request to PEMC. PEMC returns a response to PEGC, which then forwards it to PINE.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant PINE + participant PEGC + participant PEMC + Note left of PINE: 1. application layer connection + PINE->>PEGC: 2. PIN server discovery request + PEGC-->>PINE: 3. Response directly from PEGC + PEGC->>PEMC: 4. PIN server discovery request + PEMC-->>PEGC: 5. PIN server discovery response + PEGC-->>PINE: 6. PIN server discovery response + +``` + +Sequence diagram for PIN server discovery via PEGC. Lifelines: PINE, PEGC, PEMC. The sequence starts with an application layer connection between PINE and PEGC. PINE sends a PIN server discovery request to PEGC. PEGC can respond directly or route the request to PEMC. PEMC returns a response to PEGC, which then forwards it to PINE. + +**Figure 7.8.2.2.2-1: PIN server discovery via PEGC** + +1. The PIN element or PIN clients has already had the application layer connection towards PEGC. For example, the PIN elements can communicate with PEGC via WiFi or Bluetooth. The PINE can also have the open access to PEGC that with no user name or password. For this situation, the PINE can't consume the communication service that provided by PEGC, but can have communication with the PEMC behind the PEGC. +2. The PINE sends PIN server discovery request to PEGC. The requests include the GPSI, MAC address, if has, UE location. +3. The PEGC can directly deliver the PIN server end point information to PIN elements or PIN client. The end point information of PIN server includes URI(s), FQDN(s), IP address(es)) of PIN server. +4. If the PINE has open access to PEGC, that the PEGC should route the request to PEMC that behind the PEGC. +- 5-6. The PEMC delivers the PIN server end point information to PIN elements or PIN client via PEGC. The end point information of PIN server includes URI(s), FQDN(s), IP address(es)) of PIN server. + +##### 7.8.2.2.3 Procedures of PIN server discovery from PEMC + +Due to for some of the PIN elements can have the application interaction towards the PEMC, for example, via WiFi or Bluetooth pairing, so the PEMC can provide the PIN server end point information to PIN elements. + +Figure 7.8.2.2.3-1 illustrates PIN server discovery from PEMC based on request/response model. + +Pre-conditions: + +1. The PIN elements or PIN client has application layer connection with PEMC; +2. The UE Identifier or PIN client Identifier is available; + +![Sequence diagram for PIN server discovery from PEMC. Lifelines: PINE, PEMC. The sequence starts with an application layer connection between PINE and PEMC. PINE sends a PIN server discovery request to PEMC. PEMC returns a response to PINE.](0b452c5334567cbdc22ee9817e1246f5_img.jpg) + +``` + +sequenceDiagram + participant PINE + participant PEMC + Note left of PINE: 1. Application layer connection + PINE->>PEMC: 2. PIN server discovery request + PEMC-->>PINE: 3. PIN server discovery response + +``` + +Sequence diagram for PIN server discovery from PEMC. Lifelines: PINE, PEMC. The sequence starts with an application layer connection between PINE and PEMC. PINE sends a PIN server discovery request to PEMC. PEMC returns a response to PINE. + +**Figure 7.8.2.2.3-1: PIN server discovery via PEMC** + +1. The PIN element or PIN clients has already had the application layer connection towards PEMC. For example, the PIN elements can communicate with PEMC via WiFi or Bluetooth. +2. The PINE sends PIN server discovery request to PEMC. The requests include the GPSI, MAC address, UE location. +3. The PEMC delivers the PIN server end point information to PIN elements or PIN client. The end point information of PIN server includes URI(s), FQDN(s), IP address(es) of PIN server. 7.9 Solution #8: Service switch in a PIN + +## 7.9 Solution #8: Service switch in a PIN + +### 7.9.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.9.2 Solution description + +#### 7.9.2.1 General + +This solution addresses Key Issue #3. The principles of this solution are: + +- The PIN Application Client in UE can discover or get notified about available PINs where an application service can be switched to. +- Once the PIN Application Client selects the PIN, it can request that the PIN Server trigger service switch procedure and obtain the necessary information for performing the service switch from the PIN Server. +- The PIN server can identify the PIN Applications in PINE, where the service can be split and terminated. +- The PIN Server instructs PIN Management Client to execute service switch procedure. +- The PIN Management client configures PIN Gateway client and PINEs for service switch. +- The PIN Gateway client uses the configuration information from the PIN Management Client to configure the PEGC which implements service switch function. + +#### 7.9.2.2 Procedure + +This procedure presents a high-level overview of Solution #1. + +##### 7.9.2.2.1 Functional entities + +**PIN Application Client:** A PINAPP function in UE, PINE, which initiates discovery, service switch, configuration. + +**PIN Management Client:** A PINAPP in PEMC, configures PEGC and PINE for service switch. + +**PIN Gateway Client:** A PINAPP in PEGC, obtains configuration from PEMC and executes service switch. + +**PIN Server:** Supports PIN Application Client by providing PIN information and executes service switch procedure when requested by PIN Application Client. + +##### 7.9.2.2.2 Procedures of PIN Service Switch + +Figure 7.9.2.2.2.-1 illustrates a discovery and service switch procedure based on request/response model. + +![Sequence diagram for PIN Service Switch. Lifelines: Application Client (PINE), Application Client (UE), PIN Client (UE), PIN Client (PINE), PIN Gateway Client, PIN Management Client, PIN Server, AS. The sequence starts with an ongoing streaming session from AS to UE. 1. Discover PIN: UE sends to PINE, PINE sends to PIN Server. 2. OK: PIN Server responds to PINE, PINE responds to UE. 3. Service switch request: UE sends to PINE, PINE sends to PIN Server. 4. OK: PIN Server responds to PINE, PINE responds to UE. 4. Switch Application Session: PIN Server sends to PIN Management Client. 5. Configure Service Switch: PIN Management Client sends to PIN Gateway Client. 6. OK: PIN Gateway Client responds to PIN Management Client. 6. Configure Service Switch: PIN Management Client sends to PINE, PINE sends to UE. 7. OK: PINE responds to PIN Management Client. 8. Service Switch: PIN Management Client sends to AS. 9. OK: AS responds to PIN Management Client. 9. Handshake with AS: PIN Management Client sends to PIN Server. 10. Session setup, modify, update: PIN Server sends to AS. 11. Split to one or more Application Clients: AS sends to PINE, PINE sends to UE.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Sequence diagram for PIN Service Switch. Lifelines: Application Client (PINE), Application Client (UE), PIN Client (UE), PIN Client (PINE), PIN Gateway Client, PIN Management Client, PIN Server, AS. The sequence starts with an ongoing streaming session from AS to UE. 1. Discover PIN: UE sends to PINE, PINE sends to PIN Server. 2. OK: PIN Server responds to PINE, PINE responds to UE. 3. Service switch request: UE sends to PINE, PINE sends to PIN Server. 4. OK: PIN Server responds to PINE, PINE responds to UE. 4. Switch Application Session: PIN Server sends to PIN Management Client. 5. Configure Service Switch: PIN Management Client sends to PIN Gateway Client. 6. OK: PIN Gateway Client responds to PIN Management Client. 6. Configure Service Switch: PIN Management Client sends to PINE, PINE sends to UE. 7. OK: PINE responds to PIN Management Client. 8. Service Switch: PIN Management Client sends to AS. 9. OK: AS responds to PIN Management Client. 9. Handshake with AS: PIN Management Client sends to PIN Server. 10. Session setup, modify, update: PIN Server sends to AS. 11. Split to one or more Application Clients: AS sends to PINE, PINE sends to UE. + +Figure 7.9.2.2.2-1: PIN Service Switch + +Pre-conditions: + +- The PIN Client in UE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; + - The PIN Client in UE has been authorized to communicate with the PIN server; + - The PIN Management Client supports functionality to execute the service switch procedure; + - The PIN Gateway Client supports functionality to execute the service switch procedure; + - The PIN Server has capability to communicate with Application server to identify application session and provide information about any changes to the end points of the session; + - There is an ongoing application session from AS to UE. +1. A PIN Client in a UE, triggered by an Application Client, sends a discovery request to a PIN Server. The purpose of the discovery request is to discover a PIN that can support a certain application in a certain location. The discovery request includes Location information, Application requirements such as Display characteristics, Audio characteristics, etc. The PIN Client can also subscribe to be notified when a PIN is available in a location and can support the application requirements. + 2. The PIN Server based on Location and application service requirement can send a notification to the PIN Client with the following information: discovered PIN ID, details of PINAPP capabilities and corresponding PE IDs, such as Device ID, IP address and Port number. PIN Client forwards the information to Application Client in UE. + 3. The Application Client in UE initiates service switch with the PIN Client, which sends a "Service switch request" to the PIN Server with information about the service to be switched. The information about the service to be switched includes Application session ID, Destination PIN ID, and an IP 4 Tuple that describes the session. The IP 4 tuple may include the IP Address of the UE, the IP Address of the Server that provides the service, and the UE port numbers that are associated with the service, and the port numbers on the server that are associated with the service. The PIN Server accepts the request and informs the Application Client. + 4. PIN Server sends the "Switch Application Session" request to the PIN Management Client. The request includes information such as + - The Application Session Id, + +- The, Destination PINE: PE IDs (1..N), can include IP address, Port number, URL etc. +- If the Application session needs to be split among multiple PINEs (i.e. split into sub-flows), it is indicated by setting the flag SPLIT == FALSE or TRUE. SPLIT can be set to TRUE only if the request includes multiple PINEs. +- The IP 4 Tuple +- Security related information elements required to successfully transfer the session context. + +NOTE: Security related information elements are in the scope of SA WG3 + +5. The PIN Management Client starts configuring PEGC by sending "Configure Service Switch" to PIN Gateway Client, which includes: + - The Session ID + - Destination PINE information, which is a list of PEID, IP address, Port number or URL, where the sub-flows will be terminated. + - The flag SPLIT is set to TRUE or FALSE, if the session needs to be split to multiple PINEs and more than one PINE information is included in the TerminatingPineList. It can also include information about PINE to sub-flow mapping. +6. The PIN Management Client also configures PINE to prepare for terminating application session. The configuration information is sent to the PIN Client and Application Client in PINE. +7. The PIN Management Client responds to PIN server to indicate that configuration of PEGC and PINE has happened successfully, with information such as + - The Terminating PEGC ID and + - The Terminating PEGC reachability information, such as IP address, port number, URL etc. + - The Terminating Destination PINE reachability information, such as IP address, port number, URL etc. +8. PIN Server informs Application Server to switch the application session to a new destination IP address. PIN Server provides information such as: + - Application Session ID: identifies the application session to be switched to new end point + - Term IP Address: IP address of the PEGC where the application session will be terminated. +9. PIN Gateway Client interacts with the AS, to get authorized by the AS for the service switch, by sending the information from Step 4. This authorization operation is in the scope of SA WG3. Once authorized, the TCP session up continues between the PEGC and the AS. +10. The PEGC may trigger a PDU Session Modification procedure in order to obtain QoS Rules for the new flow. PEGC can setup paths with one or more PINEs to split the main session flow into sub-flows. PEGC can also interact with PIN Server to maintain synchronization among the sub-flows. +11. Once the path from PINE Application Client to AS is available, Application Client can use application level mechanism to pull video stream, play and again pull. + +### 7.9.3 Solution evaluation + +This solution addresses KI#3 about "How to support application mechanism for service switching in a PIN between different PIN applications for achieving better service experience". + +The application-level mechanism described here allows the Application server, PEGC and PINEs to become aware of the new endpoints to execute service switch. Based on these information, PINE, PEGC, 5GS and Application Server executes session setup, modify procedures. + +## 7.10 Solution #9: PINAPP role change + +### 7.10.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.10.2 Solution description + +#### 7.10.2.1 General + +This solution addresses Key Issue #6. + +A UE that is serving the role of a PEGC for a PIN leaves the coverage area of the PIN. The PEMC detects that the UE has left the coverage area of the PIN and makes a request to the PIN server to select a new PEGC. + +#### 7.10.2.2 Procedure + +Pre-conditions: + +1. The PIN server has authorized the PEMC to create PINs. +2. The PEMC creates a local PIN with members: PEMC, UE serving as PEGC, PINE1, and PINE2. +3. The PEMC maintains a PIN profile with information of capabilities for each PIN member. +4. PINE2 is a PIN member that also has gateway capability. + +![Sequence diagram for PINAPP Role Change. The diagram shows the interaction between PINE 1, PINE 2, PEMC, PEGC (all within a 'Local PIN' dashed box) and the PIN Server. The sequence of messages is: 1. UE leave local PIN area (from PEGC to PIN Server), 2. PEMC detect absence of UE (internal to PEMC), 3. PIN role change request (from PEMC to PIN Server), 4. PIN role change response (from PIN Server to PEMC), 5. Deliver management information (from PIN Server to PEMC), and 6. PIN role change notification (from PEMC to PINE 1 and PINE 2).](1ca688982d625c3b8a8e382b675de466_img.jpg) + +``` + +sequenceDiagram + participant PINE1 as PINE 1 + participant PINE2 as PINE 2 + participant PEMC as PEMC + participant PEGC as PEGC + participant PS as PIN Server + + Note right of PEGC: 1. UE leave local PIN area + PEGC->>PS: + Note right of PEMC: 2. PEMC detect absence of UE + PEMC->>PS: 3. PIN role change request + PS-->>PEMC: 4. PIN role change response + PS-->>PEMC: 5. Deliver management information + PEMC->>PINE1: 6. PIN role change notification + PEMC->>PINE2: + +``` + +Sequence diagram for PINAPP Role Change. The diagram shows the interaction between PINE 1, PINE 2, PEMC, PEGC (all within a 'Local PIN' dashed box) and the PIN Server. The sequence of messages is: 1. UE leave local PIN area (from PEGC to PIN Server), 2. PEMC detect absence of UE (internal to PEMC), 3. PIN role change request (from PEMC to PIN Server), 4. PIN role change response (from PIN Server to PEMC), 5. Deliver management information (from PIN Server to PEMC), and 6. PIN role change notification (from PEMC to PINE 1 and PINE 2). + +Figure 7.10.2.2-1: PINAPP Role Change + +1. The UE leaves the local coverage area of the PIN. +2. The PEMC detects that the UE is no longer providing the PEGC service. For example, the PEMC may not be getting responses from the UE or either PINE1 or PINE2 has informed the PEMC that PIN routing via the UE is not available. + +NOTE: A corresponding event subscription/ notification is to be specified in the normative phase to enable this detection. + +3. The PEMC sends a PIN role change request to the PIN server to select a new PEGC. The request includes the PIN ID, the PEMC ID, the UE ID or the PEGC ID for the UE, the ID of a PIN member that can serve as the new PEGC (e.g. PINE2), and a timestamp. + +4. The PIN server considers which member of the PIN can serve as the new PEGC, including the PIN member the PEMC provided, and selects a PIN member to serve as the new PEGC. The PIN server sends a response to the PEMC with the status of the request, the ID of the new PEGC, and PIN traffic routing rules for the role change. The PIN server may also inform the PEMC to notify other PIN members of the PEGC role change. +5. The PIN server delivers management information to PINE2 to inform PINE2 to serve as the new PEGC. The management information includes PIN traffic routing rules that PINE2 would need to make routing decisions. +6. The PEMC notifies other members of the PIN that PINE2 will serve as the new PEGC. The PEMC includes the contact information of PINE2 and traffic routing rules that may be applicable to each member. + +### 7.10.3 Solution evaluation + +This solution addresses KI #6 on PEMC/PEGC replacement in PIN. The PEGC of the PIN leaves the coverage area of the PIN and PEMC detects that PIN gateway functionality is not available. The PEMC makes a request to the PIN server to assign a new PEGC for the PIN. The PIN server assigns PINE 2 as the new PEGC and provides PINE 2 with management information to route traffic for the PIN. PEMC notifies the other members of the PIN that PINE 2 is the new PEGC. + +The solution provides a procedure for role change of PEGC to ensure PIN routing is available for the PIN if the PEGC is not available. + +## 7.11 Solution #10: Service switch internal PIN + +### 7.11.1 Architecture assumptions + +The architecture assumptions of Solution #1 are also assumed in this solution. + +### 7.11.2 Solution description + +#### 7.11.2.1 General + +![Diagram illustrating the PIN Service Switch internal PIN scenario. A server is connected to a 5GS cloud, which is connected to a PIN. The PIN contains PINE B, PINE A, a Service switch, and a PEMC. PINE A sends a Service request to the PEMC. The Service switch is connected to PINE A and the PEMC. The 5GS cloud is connected to the PIN via a dashed green line.](86692d82da6655813b5acf58a767a38c_img.jpg) + +The diagram shows a 'server' at the top connected to a '5GS' cloud. Below the 5GS is a large oval representing the PIN. Inside the PIN, there is a 'PINE B' (represented by a filmstrip icon), a 'Service switch' (represented by a colorful square icon), 'PINE A' (represented by a smartphone icon), and a 'PEMC' (represented by a smartphone icon). A dashed green line connects the 5GS to the PIN. A solid black arrow labeled 'Service request' points from PINE A to the PEMC. A dashed green line also connects the Service switch to PINE A. + +Diagram illustrating the PIN Service Switch internal PIN scenario. A server is connected to a 5GS cloud, which is connected to a PIN. The PIN contains PINE B, PINE A, a Service switch, and a PEMC. PINE A sends a Service request to the PEMC. The Service switch is connected to PINE A and the PEMC. The 5GS cloud is connected to the PIN via a dashed green line. + +Figure 7.11.2.1-1: PIN Service Switch internal PIN + +In Figure 7.11.2.1-1, it describes the service switch scenario. + +The PINE A has the application communication with application server. And when the PINE A decides to select other alternative PINE B to apply the traffic flow, the PINE A firstly should discover a PIN and join in. And then, in the PIN, + +there should exist the PINE that can be hosted with the same service type as PINE A, for example, the video flow, music flow or game flow. + +The PINE A can send the request to PEMC to determine the PINE B to host the application traffic. After the determination, the PEMC sends the endpoint information to PINE A and the PINE A can offload the traffic either directly to PINE B or via PEGC. + +#### 7.11.2.2 Procedure of service switch internal PIN + +Pre-conditions: + +1. The UE Identifier or PIN client Identifier of PINE A or PINE B is available; +2. The PIN client in PINE A or PINE B has been authorized to communicate with the PEMC; +3. The PIN client in PINE B can provide the same PIN service as PINE A's traffic flow. + +![Sequence diagram illustrating the Service switch procedure internal PIN. The diagram shows interactions between PINE A, PINE B, PEGC, PEMC, and AS. The steps are: 0. PINE A decides to do service switch; 1. PINE A sends PIN service discovery request to PEMC; 2. PEMC processes request; 3. PEMC responds to PINE A with PIN service and related PINE endpoint information; 4. PINE A determines the PINE B for service switch; 5a. Service traffic is transferred to PINE B; 5b. PINE A transfers application context to PINE B and triggers application traffic relocation. Application traffic is shown being redirected from PINE A to PINE B via PEGC and AS.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +``` + +sequenceDiagram + participant PINE A + participant PINE B + participant PEGC + participant PEMC + participant AS + + Note left of PINE A: 0. Decide to do service switch + PINE A->>PEMC: 1. PIN service discovery request to PEMC + Note right of PEMC: 2. Process request + PEMC->>PINE A: 3. Response to PINE A with the PIN service and related PINE endpoint information + Note left of PINE A: 4. Determines the PINE B for service switch + Note left of PINE A: 5a. The service traffic can be transferred to PINE B + PINE A-->>AS: Application traffic + AS-->>PINE B: Application traffic + Note left of PINE A: 5b. The PINE A transfers the application context to PINE B and triggers the application traffic relocation + PINE A-->>AS: Application traffic + AS-->>PINE B: Application traffic + +``` + +Sequence diagram illustrating the Service switch procedure internal PIN. The diagram shows interactions between PINE A, PINE B, PEGC, PEMC, and AS. The steps are: 0. PINE A decides to do service switch; 1. PINE A sends PIN service discovery request to PEMC; 2. PEMC processes request; 3. PEMC responds to PINE A with PIN service and related PINE endpoint information; 4. PINE A determines the PINE B for service switch; 5a. Service traffic is transferred to PINE B; 5b. PINE A transfers application context to PINE B and triggers application traffic relocation. Application traffic is shown being redirected from PINE A to PINE B via PEGC and AS. + +Figure 7.11.2.2-1: Service switch procedure internal PIN + +0. The PINE A has application layer communication with application server. And the PINE A decides to do the service switch to other PINEs. And the PINE A has already been in a PIN. +1. The PINE A trigger the PIN service discovery procedure towards PEMC. This request carries the list of services the PINE wants to consume. +2. Upon receiving the request, the PEMC performs an authorization check to verify whether the PINE A has authorization to perform the operation. + +Editor's note: The authorization check needs SA3 for feedback. + +3. The PEMC provides the list of PINE endpoint(s), application client endpoint(s) information that are offering the requested services to PINE A. The PIN service can be represented by service type that PINE provides or the application client on PINE. If the request fails, the PEMC should give the failure response to indicates the cause of request failure. +4. The PINE A determines the PINE B for service switch as follow: + +Option A: The PINE A maintains the service towards AS and the service corresponds to a service type, for example, music or streaming media. The PINE A determines the potential PINE B for service switch according to whether this PINE has the capability to carry the service. + +Option B: The PINE A maintains the service towards AS by application client which represented by Application Client ID. The PINE A determines the potential PINE B for service switch according to whether this PINE has deployed the same application client as PINE A. + +5. (Use PINE B as example) The PINE A has two options to switch the service traffic to PINE B: + +Option A: Step 5a, the PINE A switches the traffic flow directly to PINE B via direct communication or via PEGC, just like the projection. + +Option B: Step 5b, the PINE A relocates the application context from application client in PINE A to application client in PINE B. After the context relocation, the application client in PINE A triggers the application relocation to PINE B. If the PIN client in PINE A or PIN client in PINE B can directly communicate with AS, the application client behaviour in step 5b is replaced by PINE A/B. + +### 7.11.3 Solution evaluation + +This solution addresses KI#3 about " How to support application mechanism for service switching in a PIN between different PIN applications for achieving better service experience ". + +This solution relies on the PEMC to select the potential PINE for service switch according to the service type. + +## 7.12 Solution #11: Application Server Discovery in a PIN + +### 7.12.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. Additionally, this solution introduces a PIN-11 reference point. + +PIN – 11: The interactions related to enabling PINAPP, between an AS and PIN Management Client. + +As shown in solution 1 in clause 7, the solution assumes a PIN-9 interface between the AS and PIN Server and a PIN-6 interface between the PIN Management Client and the PIN Server. The PIN-11 interface may be an extension so these interfaces (i.e. may re-use certain operations). + +### 7.12.2 Solution description + +#### 7.12.2.1 General + +This solution addresses aspects of Key Issue #4. + +One or more PINAPP(s) (e.g. in a PEMC or in a PIN server) can maintain a registry to manage information about AS(s) that are available to the PIN. The AS(s) register their availability with the PINAPP. + +The PINAPP(s) can update the PIN Server with information about the registry. The information about the registry can include the PIN ID, the PIN Location and an address (e.g. URL) of the PINAPP registry. + +The PINAPPs provide information from the registry to other PINAPPs about available AS(s). + +Application clients in a PINE can be provisioned with contact information for the PINAPP registry. Alternatively, Application clients can obtain contact information for the PINAPP registry by querying a PIN Server. + +Application clients can query the PINAPP registry for information about an AS. If the query cannot be resolved, it can be forwarded to another PINAPP. + +#### 7.12.2.2 Procedure + +This procedure presents a high-level overview of Solution #11. + +##### 7.12.2.2.1 Functional entities + +PINAPP: A PIN function, which can maintain information about AS(s) available to a PIN. The AS information can include Location and address (e.g. URL). + +PIN Server: The PIN Server can maintain information about PINAPPs including PINAPPs, which maintain AS registry functionality. + +PIN Application Client: Application clients running in PINE. + +##### 7.12.2.2.2 Procedures of PIN Application Server Discovery + +Figure 7.12.2.2.2-1 illustrates an initial provisioning and AS discovery procedure based on request/response model. + +Pre-conditions: + +- The PINAPP with an AS registry has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN Server. +- The PINAPP with an AS registry has been authorized to communicate with the PIN server. +- The PINAPP with an AS registry supports functionality to maintain a registry of AS(s). The PINAPP with an AS registry can be deployed in PEMC. When the AS Registry is in the PEMC, and AS interacts with the PIN Management Client via the PIN-11 reference point. +- The PIN Server also supports functionality to maintain a registry of AS(s). +- The PIN Server supports functionality to maintain information about PINAPPs which support an AS Registry (i.e. the PIN Server knows which PINAPPs support AS Registry Functionality). + +![Sequence diagram for PIN AS Discovery showing interactions between PIN Enabler Client, Application Server (AS), PINAPP (e.g. AS registry function), and PINAPP (PIN Server).](a78db21022e0687c18d97ed547dd7ecb_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server (AS) + participant PINAPP_E as PINAPP (e.g. AS registry function) + participant PINAPP_S as PINAPP (PIN Server) + participant PEC as PIN Enabler Client (PINE Application Client) + + Note over AS, PINAPP_E: 1. While PIN creation or when AS is deployed, update PINAPP with AS information + AS->>PINAPP_E: PINAPP AS Registration Request + PINAPP_E->>PINAPP_S: 2. UpdatePINAPPinfo + PINAPP_S->>PINAPP_E: 3. UpdateASinfo + PINAPP_E->>PINAPP_S: 4. PINAPP Discovery Request + PINAPP_S->>PEC: 5. OK (PINAPP information) + PEC->>PINAPP_E: 6. DiscoverAS + alt ALT 1: Direct Response + PINAPP_E->>PEC: 7. ok + else ALT 2: Forward Query + PINAPP_E->>PINAPP_S: 8. Forward DiscoverAsQuery + PINAPP_S->>PEC: 9. OK + end + +``` + +Sequence diagram for PIN AS Discovery showing interactions between PIN Enabler Client, Application Server (AS), PINAPP (e.g. AS registry function), and PINAPP (PIN Server). + +Figure 7.12.2.2.2-1: PIN AS Discovery + +1. A PIN has been successfully created. An AS registers with the PINAPP by sending information such as: AS name, InstanceID, and address (e.g. URL). The AS can be deployed anytime and can update its registration information in the PINAPP by sending a new Registration message. The PINAPP stores the AS information in its registry. + +2. The PINAPP updates the PIN Server by sending the PIN Server information from its registry. +3. If the PIN Server's registry has information from AS(s) that are not in the PINAPP's registry, then the PIN Server can also update the PINAPP with information about AS(s) that are stored in the registry of the PIN Server. Furthermore, the PIN Server can configure the PINAPP with Usage Policies for the AS(s) that are in the PINAPP's registry. The Usage Policy can indicate what types of Application Clients may discover the AS, the identity of Application Client(s) that may discover the AS, and times of day when the AS is available. +4. An Application Client, which wants to discover an AS, requests information from the PIN Server about how to reach the registry functions. +5. The PIN Server sends the Application Client information about the registry function PINAPP (e.g. a URL). +6. The Application client sends a Query for the PINAPP in order to obtain contact information for an AS. The query includes the name of the AS that the application client wants to contact. +7. If the query can be resolved, PINAPP responds with an address of the AS (e.g. URL). +8. If the query cannot be resolved, PINAPP forwards the query to PIN Server. +9. PIN server responds to Application Client with the details of the AS (e.g. URL). + +After the procedure above, Application Client in a PINE can start interacting with the AS. + +### 7.12.3 Solution evaluation + +This solution addresses KI#4 about "How to enable discovery of Application Server, connected to a PIN, by Application Clients running in the same PIN?". + +A PINAPP, which maintains AS information, helps Application Clients discover AS(s). The PINAPP can be discovered by PIN Application clients. In certain situations, if an AS is not found in the PINAPP, information can be fetched from other PINAPP(s) (e.g. a PIN Server). + +This solution allows flexibility in deploying AS(s) because new AS instances can store their information in registries so that they can be discovered. + +## 7.13 Solution #12: PEMC registration to PIN server + +### 7.13.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.13.2 Solution description + +#### 7.13.2.1 General + +This solution addresses aspects of Key Issue #1. + +Before the PEMC triggering the creation of PIN to network, the PEMC (for example, the UE) should receive the role of PEMC first from network. Only the PEMC can trigger creation of PIN. + +PEMC (PIN Element Management Control) is a PIN Element with Management Capability. A PIN Element with Management Capability is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN. Only after the PINE becoming the PEMC, the PINE can trigger the PIN create request to network. + +At the network side, a PIN server should be deployed. The PIN server is responsible for the authorization of the request of the role of PEMC from PINE. The PIN server has this verification procedure with 5GC, which the procedure is defined in SA2 specification. + +And the PINE/PEGC should also have the registration procedure to PIN server. For the PINE and PEGC registration, in order to reduce the signal interaction, it can be accomplished by the PEMC. The registration of PINE/PEGC includes the Device Metadata includes MAC address, vendor name, device description, PINE/PEGC Address. + +#### 7.13.2.2 Procedures of PEMC registration + +Pre-conditions: + +1. The PEMC has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The UE Identifier or PIN client Identifier is available; +3. The PEMC has been authorized to communicate with the PIN server; + +Figure 7.13.2.2.2-1 illustrates service provisioning procedure based on request/response model. + +![Sequence diagram showing PEMC registration on PIN server. The diagram involves three participants: PEMC, PIN Server, and 5GS. Step 1: PEMC sends a registration request to the PIN Server. Step 2: The PIN Server checks with the 5GS to see if it has a subscription for the PEMC. Step 3: The PIN Server sends a response (Successful or failure) back to the PEMC.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) + +``` + +sequenceDiagram + participant PEMC + participant PIN Server + participant 5GS + Note left of PEMC: 1. PEMC registers to PIN server + PEMC->>PIN Server: Request + Note right of PIN Server: 2. PIN server checks with 5GS of whether it has subscribes as the PEMC + PIN Server->>5GS: Check + 5GS-->>PIN Server: Response + Note left of PEMC: 3. Response (Successful or failure) + PIN Server-->>PEMC: Response + +``` + +Sequence diagram showing PEMC registration on PIN server. The diagram involves three participants: PEMC, PIN Server, and 5GS. Step 1: PEMC sends a registration request to the PIN Server. Step 2: The PIN Server checks with the 5GS to see if it has a subscription for the PEMC. Step 3: The PIN Server sends a response (Successful or failure) back to the PEMC. + +**Figure 7.13.2.2.2-1: PEMC requests to register on PIN server** + +1. The PEMC sends Registration Request (GPSI) to the PIN server. The service provisioning request includes the security credentials of the PEMC received during authorization procedure and may include the GPSI. The registration request carries the PIN ID of the PIN for which it is intending to register as PEMC and the PIN element may indicate whether it is to be assigned with primary or secondary PEMC role. +2. The PIN server interacts with the 5GS to check whether the UE identified by the GPSI has subscribed to be a PEMC. If subscribed, it checks the PIN profile whether the requesting PIN element can be assigned with primary or secondary role and authorize the PIN element accordingly. In case if the PIN has already been created, the requesting PIN element is assigned with the secondary PEMC role irrespective of the role requested by the PIN element. + +**Editor's note: whether and how to 5GS check the UE identified by the GPSI has subscribed to be a PEMC is in SA2 scope.** + +3. The PIN server responds to the PEMC with allocated PEMC ID in successful response. If the registration procedure fails, the PIN server should give the failure response to indicates that indicates the cause of registration request failure. + +#### 7.13.2.3 Procedures of PINE/PEGC registration + +Pre-conditions: + +1. The PEMC has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The UE Identifier or PIN client Identifier is available; +3. The PEMC has been authorized to communicate with the PIN server; +4. The PINE/PEGC has already received the IP address of PEMC. + +![Sequence diagram showing the registration process of PINE/PEGC on PIN server via PEMC.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant PINE/PEGC + participant PEMC + participant PIN server + Note over PINE/PEGC, PEMC: 1. PINE/PEGC sends the registration request to PEMC + PINE/PEGC->>PEMC: + Note over PEMC, PIN server: 2. PEMC sends registration request to PIN server + PEMC->>PIN server: + Note over PIN server, PEMC: 3. Response (Successful or failure) + PIN server-->>PEMC: + Note over PEMC, PINE/PEGC: 4. Response (Successful or failure) + PEMC-->>PINE/PEGC: + +``` + +Sequence diagram showing the registration process of PINE/PEGC on PIN server via PEMC. + +**Figure 7.13.2.3-1: PINE/PEGC register on PIN server** + +1. The PINE/PEGC sends Registration Request (Device Metadata) to the PEMC. The Device Metadata includes the information that related to PINE/PEGC, including MAC address, vendor name, device description, PINE/PEGC Address. +2. The PEMC sends Registration Request (PEMC ID, Device Metadata) to the PIN server. +3. The PIN server responds to the PEMC with the allocated PINE/PEGC ID in successful response. +4. The PEMC sends Registration Response (PINE ID) to the PINE/PEGC. + +## 7.14 Solution #13: SEAL enabled PINAPP architecture and PIN management + +### 7.14.1 Architecture assumption + +The Figure 7.14.1-1 shows the SEAL based application architecture for enabling PINAPP. + +![Diagram of SEAL based PINAPP architecture showing components in Personal IoT network, 3GPP Core network, and Data network.](b5987d63203a5fa601921039922ac520_img.jpg) + +The diagram illustrates the SEAL based PINAPP architecture across three network domains: + +- Personal IoT network:** Contains multiple Application clients. Each client stack includes an Application client, a PIN client (enabler), and a SEAL group mgmt client. Reference points PIN-1, PIN-2, PIN-3, PIN-5, and PIN-10 connect these internal components. GM-X and GM-Y reference points connect the SEAL group mgmt clients. +- 3GPP Core network:** Contains a PIN Gateway Client, a SEAL group mgmt client (PEGC), a PIN Management client, and a SEAL group mgmt client (PEMC). Reference points include GM-UU and GM-PCS. +- Data network:** Contains an Application server, a PIN server (enabler), and a SEAL group mgmt server. Reference points PIN-6, PIN-7, PIN-8, PIN-9, and GM-S connect these to the other networks. + +Diagram of SEAL based PINAPP architecture showing components in Personal IoT network, 3GPP Core network, and Data network. + +**Figure 7.14.1-1: SEAL based PINAPP architecture** + +The following difference is applied compared with Sol#1. + +- The UE also has a SEAL group management client, and the PIN client interact with the SEAL group management client via the GM-C to achieve PIN management; +- The PIN server interacts with the SEAL group management server via the GM-S reference point to accomplish PIN management; +- The SEAL group management client in the PEGC and PEMC interacts with the SEAL group management server via GM-UU; + +- The SEAL group management client in the PIN element interacts with the SEAL group management client in the PEMC via the GM-X/GM-Y which is over the non-3GPP RAT. +- The PIN is the VAL group, and the PIN elements is the group member. + +**Editor's Note:** The relationship between GM-X/GM-Y and PC5 is FFS. + +### 7.14.2 PIN creation + +The SEAL group management client at the PEMC, or the PIN server triggers the PIN creation (e.g., add PIN elements to the PIN or remove PIN elements from the PIN) as described in clause 10.3.3 of 3GPP TS 23.434. The SEAL group management client at the PEMC + +### 7.14.3 PIN update + +The SEAL group management client at the PEMC, or the PIN server triggers the PIN update as described in clause 10.3.5.2 of 3GPP TS 23.434. + +The PIN elements initiates to join the PIN as described in the clause 10.3.8 of 3GPP TS 23.434. + +The PIN elements initiates to leave the PIN as described in the clause 10.3.9 of 3GPP TS 23.434. + +### 7.14.4 PIN deletion + +The SEAL group management client at the PEMC, or the PIN server triggers the PIN deletion as described in clause 10.3.13 of 3GPP TS 23.434. + +### 7.14.5 PIN discovery and PIN element discovery + +The SEAL group management client at the PIN element discovers the PIN from the server as described in clause 10.3.8 (i.e., the group announcement in step 5) and clause 10.3.11 of 3GPP TS 23.434. + +The SEAL group management client at the PIN element discovers the PIN element from the server as described in clause 10.3.4 of 3GPP TS 23.434. + +## 7.15 Solution #14: PIN communication via 5GS + +### 7.15.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.15.2 Solution description + +#### 7.15.2.1 General + +This solution addresses aspects of Key Issue #2. + +For a certain PINE, it has the subscription whether the PINE has the permission to use 5GS to communicate. + +As a feature indicated in SA1 and KI#2, the PIN client within a PIN can communicate with other devices, services and applications within the same PIN. Furthermore, PIN client can connect the 5G Network via a PEGC. Also, as a feature, some of the PIN client in PIN has the permissions that they can communicate with other UE or application outside of PIN with the help of 5GC. + +In this solution, the PINE establishes direct connection with PEGC first. The PINE connects to PEGC via the password or username which is used for PINE to initial connect. + +And then, the PINE sends the relay request to PEMC or PIN server, to relay the traffic to other PINE via PEGC by 5GS. If the request is related to internet services, the DN-specific ID may be included. + +The PEMC requests to activate the relay request to PIN server and the PIN server can request the 5GS to establish the PDU session which is the procedure defined in SA2. The PIN server sends the parameters in relay request to 5GS to request to establish the PDU session. + +And according to the SA1 requirement of PIN, the TS 22.101 specifies that 5GS supports secure provisioning of credentials to a non-3GPP device via a gateway UE, whose User Identifier has been linked with the 3GPP subscription of the gateway UE, to enable the non-3GPP device to access the network and its services according to the linked 3GPP subscription when connected via non-3GPP access. So, the PIN server also supports to deliver the security credentials to PINE via application layer procedure with the support of 5GS network. + +Another way to configure PIN of 5GS communication is, the PEMC commands a PEGC to configure the allowed/disallowed traffic flow and corresponding requested QoS if allowed. And the PEGC triggers the PDU session establishment or modification towards 5GS, which is the conclusion reflected in TR 23.700-88[4]. The information of PEMC commands PEGC is the same as the PIN server trigger QoS establishment procedure. + +#### 7.15.2.2 Procedures of PIN communication via 5GS + +This procedure presents a high-level overview of Solution 1. + +Figure 7.15.2.2-1 illustrates PIN communication via 5GS procedure based on request/response model. + +Pre-conditions: + +1. The PINE is able to connected into PEGC via password and username; +2. The UE Identifier or PIN client Identifier is available for PINE; +3. The PIN client has been authorized to communicate with the PIN server and PEMC; +4. The PINE has the subscription that it can communicate via 5GS; +5. The PINE has already received the IP address of other PINE. + +NOTE: How to PINE receive the other PINE IP address are related to the procedure in section 7.3.2.3. + +![Sequence diagram illustrating PIN communication via 5GS. The diagram shows the interaction between PINE, PEGC, PEMC, PIN server, and 5GS. The sequence starts with '0. Direct connection setup' between PINE and PEGC. PINE sends a '1. PINE 5GS connection request' to PEGC. PEGC sends '2a. PINE 5GS connection request' to PEMC and '2b. Notification to PEMC' to PIN server. PEMC sends '3. PINE 5GS connection request' to PIN server. PIN server sends '4. PIN server interacts with 5GS to establish PDU session' to 5GS. A dashed box labeled '5. (optional) PEMC/PEGC replacement notification' is shown between PEGC and PEMC. PIN server sends '6. Response' to PEMC. PEMC sends '7. Response' to PEGC. PEGC sends '7. Response' to PINE.](9cd7ec4a653f07d02def283cb6f2309e_img.jpg) + +``` + +sequenceDiagram + participant PINE + participant PEGC + participant PEMC + participant PIN_server as PIN server + participant 5GS + + Note over PINE, PEGC: 0. Direct connection setup + PINE->>PEGC: 1. PINE 5GS connection request + PEGC->>PEMC: 2a. PINE 5GS connection request + PEGC->>PIN_server: 2b. Notification to PEMC + PEMC->>PIN_server: 3. PINE 5GS connection request + PIN_server->>5GS: 4. PIN server interacts with 5GS to establish PDU session + Note over PEGC, PEMC: 5. (optional) PEMC/PEGC replacement notification + PIN_server->>PEMC: 6. Response + PEMC->>PEGC: 7. Response + PEGC->>PINE: 7. Response + +``` + +Sequence diagram illustrating PIN communication via 5GS. The diagram shows the interaction between PINE, PEGC, PEMC, PIN server, and 5GS. The sequence starts with '0. Direct connection setup' between PINE and PEGC. PINE sends a '1. PINE 5GS connection request' to PEGC. PEGC sends '2a. PINE 5GS connection request' to PEMC and '2b. Notification to PEMC' to PIN server. PEMC sends '3. PINE 5GS connection request' to PIN server. PIN server sends '4. PIN server interacts with 5GS to establish PDU session' to 5GS. A dashed box labeled '5. (optional) PEMC/PEGC replacement notification' is shown between PEGC and PEMC. PIN server sends '6. Response' to PEMC. PEMC sends '7. Response' to PEGC. PEGC sends '7. Response' to PINE. + +Figure 7.15.2.2-1: PIN communication via 5GS + +0. The PINE establishes direct connection with PEGC. The PINE connects to the PEGC by means of the password and username, as indicated in section 7.3.2.2 of solution 2. +1. The PINE sends PINE 5GS connection request (PIN ID, PINE ID, Packet filters, [DN-specific ID]) to the PEGC. If the request is related to internet services, the DN-specific ID may be included. The packet filters include the target PINEs IP address or FQDN that wants to communicate. The PINE should discover the other PINE's IP address first. +2. If step 2 is performed, the PEGC sends the PINE 5GS connection request to the PEMC directly, or sends PEMC Notification (PEGC ID, PINE 5GS connection request) to PIN server and PIN server sends PEMC Event Notification (PEGC ID, PINE 5GS connection request) to the PEMC. +3. The PEMC sends PINE 5GS connection request (PIN ID, PEMC ID, PEGC ID, PINE ID, Packet filters) to the PIN server. The request will be sent to other PINE via 5GS. +4. The PIN server will check with the 5GS that whether this PINE has the subscription to communicate with other PINE via 5GS. And if the PINE has the subscription, the PIN server will interact with 5GS to create/update the QoS flow of PEGC for the PINE. + +**Editor's note: How to the PIN server interacts with 5GS to establish PDU session for PINE is in SA2 scope.** + +5. (Optional) If the IP address of the PEMC/PEGC is changed, the PEMC/PEGC sends Event Notification (PEMC/PEGC ID, old IP address, new IP address) to the PIN server. +6. The PIN server sends response to PEMC for successfully establish the PDU session. +7. The PEMC sends response to PINE. + +#### 7.15.2.3 Procedures of credential provisioning to PINE via 5GS + +Pre-conditions: + +1. The PINE is able to connected into PEGC via password and username; +2. The UE Identifier or PIN client Identifier is available for PINE; +3. The PIN client has been authorized to communicate with the PIN server and PEMC; +4. The PINE has the subscription that it can communicate via 5GS; + +![Sequence diagram for Credential Provisioning by 5GS. Lifelines: PINE, PEGC, PEMC, PIN server, 5GS. The process starts with a direct connection setup between PINE and PEGC. Then, PINE sends a credential provisioning request to PEGC. PEGC forwards this as 2a. credential provisioning request to PEMC. Simultaneously, PEGC sends a notification to the PIN server (2b. Notification to PEMC). The PIN server sends a credential provisioning request to PEMC (3. credential provisioning request). The PIN server then interacts with 5GS (4. PIN server interacts with 5GS to receive the credential request). Finally, responses are returned from the PIN server to PEMC (5. Response) and from PEMC to PEGC (5. Response), which then reaches PINE.](ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg) + +``` + +sequenceDiagram + participant PINE + participant PEGC + participant PEMC + participant PIN_server as PIN server + participant 5GS + + Note over PINE, PEGC: 0. Direct connection setup + PINE->>PEGC: 1. credential provisioning request + PEGC->>PEMC: 2a. credential provisioning request + PEGC->>PIN_server: 2b. Notification to PEMC + PEMC->>PIN_server: 3. credential provisioning request + Note over PIN_server, 5GS: 4. PIN server interacts with 5GS to receive the credential request + PIN_server->>PEMC: 5. Response + PEMC->>PEGC: 5. Response + PEGC->>PINE: 5. Response + +``` + +Sequence diagram for Credential Provisioning by 5GS. Lifelines: PINE, PEGC, PEMC, PIN server, 5GS. The process starts with a direct connection setup between PINE and PEGC. Then, PINE sends a credential provisioning request to PEGC. PEGC forwards this as 2a. credential provisioning request to PEMC. Simultaneously, PEGC sends a notification to the PIN server (2b. Notification to PEMC). The PIN server sends a credential provisioning request to PEMC (3. credential provisioning request). The PIN server then interacts with 5GS (4. PIN server interacts with 5GS to receive the credential request). Finally, responses are returned from the PIN server to PEMC (5. Response) and from PEMC to PEGC (5. Response), which then reaches PINE. + +Figure 7.15.2.3-1: Credential Provisioning by 5GS + +0. The PINE establishes direct connection with PEGC. The PINE connects to the PEGC by means of the password and username, as indicated in section 7.3.2.2 of solution 2. +1. The PINE sends Credential Provisioning Request (PIN ID, PINE ID, Duration) to the PEGC. The Duration indicates the lifetime of the path for the remote provisioning. +2. The PEGC sends the Credential Provisioning Request to the PEMC directly, or sends PEMC Notification (PEGC ID, Credential Provisioning Request) to PIN server and PIN server sends PEMC Event Notification (PEGC ID, Credential Provisioning Request) to the PEMC. +3. The PEMC sends Credential Provisioning Request (PIN ID, PEMC ID, PEGC ID, PINE ID, Duration) to the PIN server. +4. The PIN server interacts with 5GS and receives the credential from 5GS. + +**Editor's note: How to the PIN server interacts with 5GS to receive credentials is in SA2 scope. And the definition and architecture of credentials for PINE is in SA3 scope.** + +5. The PIN server responds to the PEMC with the credentials, and the PEMC responses to PINE with credentials. + +#### 7.15.2.4 Procedures of PIN communication via 5GS triggered by PEGC + +This procedure presents a high-level overview of Solution 1. + +Figure 7.15.2.4-1 illustrates PIN communication via 5GS procedure based on request/response model. + +Pre-conditions: + +1. The PINE is able to connected into PEGC via password and username; +2. The UE Identifier or PIN client Identifier is available for PINE; +3. The PIN client has been authorized to communicate with PEMC; +4. The PINE has the subscription that it can communicate via 5GS; +5. The PINE has already received the IP address of other PINE. +6. The communication between PEMC and PEGC is available. + +NOTE: How to PINE receive the other PINE IP address are related to the procedure in section 7.3.2.3. + +![Sequence diagram illustrating PIN communication configuration. Lifelines: PINE, PEMC, PEGC, 5GS. The sequence starts with PINE sending '1a. Traffic' to PEGC. PEGC then sends '1b. PIN Communication Request (PIN ID, MAC address/IP address, Traffic descriptors)' to PEMC. PEMC sends '2. Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS)' to PEGC. PEGC sends '3. PDU Session Modification' to 5GS. Finally, PEGC sends '4. Create/Update/Remove Communication Response' to PEMC.](8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg) + +``` + +sequenceDiagram + participant PINE + participant PEMC + participant PEGC + participant 5GS + Note left of PINE: 1a. Traffic + PINE-->>PEGC: 1a. Traffic + Note right of PEGC: 1b. PIN Communication Request (PIN ID, MAC address/IP address, Traffic descriptors) + PEGC-->>PEMC: 1b. PIN Communication Request (PIN ID, MAC address/IP address, Traffic descriptors) + Note right of PEMC: 2. Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) + PEMC->>PEGC: 2. Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) + Note right of PEGC: 3. PDU Session Modification + PEGC-->>5GS: 3. PDU Session Modification + Note right of 5GS: 4. Create/Update/Remove Communication Response + 5GS-->>PEGC: 4. Create/Update/Remove Communication Response + PEGC-->>PEMC: 4. Create/Update/Remove Communication Response + +``` + +Sequence diagram illustrating PIN communication configuration. Lifelines: PINE, PEMC, PEGC, 5GS. The sequence starts with PINE sending '1a. Traffic' to PEGC. PEGC then sends '1b. PIN Communication Request (PIN ID, MAC address/IP address, Traffic descriptors)' to PEMC. PEMC sends '2. Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS)' to PEGC. PEGC sends '3. PDU Session Modification' to 5GS. Finally, PEGC sends '4. Create/Update/Remove Communication Response' to PEMC. + +**Figure 7.15.2.4-1: PIN communication configuration** + +1. [Optional] The PINE may send traffic to PEGC, triggered by the traffic, the PEGC sends PIN Communication Request (PIN ID, MAC address/IP address, Traffic descriptors) to the PEMC. + +2. The PEMC sends Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) to the PEGC. The PEGC configures the local rule accordingly. +3. [Optional] According to the Packet filters, the PEGC may initiate PDU Session Modification with the Packet filters and requested QoS towards 5G system in order to make 5GC configure the N4 rules for UPF(s). + +If the PEGC has already got the information to trigger the PDU session, the interaction between PEMC and PEGC will be saved. If the PEGC doesn't have the related information (PIN ID, Packet filters, requested QoS), the procedure needs the PEMC to send related information to PEGC. + +NOTE: How to the PEGC interacts with 5GS to initiate PDU Session Modification is in SA2 scope. + +## 7.16 Solution #15: Service continuity + +### 7.16.1 Architecture enhancements + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.16.2 Solution description + +#### 7.16.2.1 General + +This solution addresses aspects of Key Issue #5 and some of Key Issue #2. + +As indicated in clause 6.38 of TS 22.261[2], the following requirements that describes the service continuity will be studied in this TR phase and reflect in this key issues 2: + +- The 5G system shall be able to minimize service disruption when a PIN Element changes the communication path from one PIN Element (e.g. PIN Element with Gateway Capability) to another PIN Element or operator provided mobile access. The communication path between PIN Elements may include licensed and unlicensed spectrum as well as 3GPP and non-3GPP access. + +In PIN architecture, there are four potential communication type for PINE/PEMC or other elements: + +- the PINE has direct communication with other PINE via Bluetooth or Wi-Fi +- the PINE has communication with other PINE via PEGC (scenario 1) +- the PINE has communication with other PINE via PEGC and by means of the 5GS (scenario 2) +- the PINE has communication with other PINE via PEGC and by means of the PIN server (scenario 3) + +![Figure 7.16.2.1-1: Communication type for PINE. The diagram illustrates three scenarios for communication between a PIN Element (PINE) and a PIN Element with Gateway Capability (PEMC) via a Packet Gateway (PEGC).](d5d5c87be8e612be9d06d406bc894fd5_img.jpg) + +The diagram shows three communication scenarios for PINE: + +- Scenario 1: via Gateway** +A PINE device (Inner IP: 192.168.1.101) is connected to a PEGC. The PEGC is connected to a PEMC device (Inner IP: 192.168.1.100). +- Scenario 2: via 5G-LAN (same as traffic between PEMC and PINE)** +A PINE device (Inner IP: 192.168.2.100) is connected to a PEGC2. PEGC2 is connected to a UPF (User Plane Function). The UPF is connected to a PEGC1, which is connected to a PEMC device (Inner IP: 192.168.1.100). +- Scenario 3: via PIN server** +A PINE device (Inner IP: 192.168.2.100) is connected to a PEGC2. PEGC2 is connected to a PIN server. The PIN server is connected to a PEGC1, which is connected to a PEMC device (Inner IP: 192.168.1.100). NAT IP: 180.1.1.101 is shown for PEGC2 and NAT IP: 180.1.1.100 is shown for the PIN server. + +Figure 7.16.2.1-1: Communication type for PINE. The diagram illustrates three scenarios for communication between a PIN Element (PINE) and a PIN Element with Gateway Capability (PEMC) via a Packet Gateway (PEGC). + +Figure 7.16.2.1-1: Communication type for PINE + +For scenario 1, the PEMC communicates with the PINE via PEGC. And the PEMC and PEGC has the same private IP range and the PEGC can easily route the information to PINE under the same PEGC. + +For scenario 2, the PEMC communicates with the PINE via two PEGCs. The PINE and PEMC are not under the same PEGC, and the PEMC should communicate with the PINE with the help of 5GS as indicated in the KI#2. The two PEGCs act as the 5G-LAN communication. + +For scenario 3, as the default communication, the PEMC communicates with the PINE via PIN server. The PIN server supports both the user plane and control plane interactions. + +But in order to coordinated with the SA1 requirements, it describes the changing of access of PINE. So, only two situation of continuity should be studied in TR: + +Firstly, the PEGC relocation. The PINE changes the gateway to communicate with other PINEs in PIN. + +Secondly, change the communication from via PEGC to via 5GS. The PINE when move out of PEGC coverage, the PINE can change the communicate via 5GS. + +#### 7.16.2.2 Procedures to support service continuity + +##### 7.16.2.2.1 PEGC relocation + +This procedure solves the situation, that PINE A has application layer communication with PINE B via PEGC 1. And for some reasons, the PEGC 1 should relocate to PEGC 2. And the PINE1 should continue to communicate with PINE 2 via PEGC 2. + +Figure 7.16.2.2.1-1 illustrates the service continuity to change the application layer communication to communication via different PEGC based on request/response model. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; +4. The PINE A and PINE B are both in the same PIN, and can communicate with PEGC 1; +5. The PEGC 2 is another PEGC that in this PIN; + +![Sequence diagram illustrating PEGC relocation in PIN. Lifelines: PINE 1, PINE 2, PEGC 1, PEGC 2, PEMC, PIN server. The sequence shows PEGC 1 detecting relocation, discovering PEGC 2, informing PEMC, and finally PINE 1 communicating with PINE 2 via PEGC 2.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant PINE 1 + participant PINE 2 + participant PEGC 1 + participant PEGC 2 + participant PEMC + participant PIN server + + rect rgb(255, 255, 255) + Note over PINE 1, PEGC 1: 1. PINE 1 communicates with PINE 2 via PEGC 1 + end + Note over PEGC 1: 2. Detect PEGC 1 relocation is +needed + Note over PEGC 1: 3a. PEGC 1 discovers PEGC 2 + rect rgb(255, 255, 255) + Note over PEGC 1, PEMC: 3b. PEGC 1 indicates PEMC to discover PEGC 2 + end + PEGC 1->>PEMC: 4a. PEGC 1 indicates PEMC of new PEGC 2 + Note over PEMC: 5. PEMC determines the +PEGC 2 + PEMC->>PEGC 2: 6. PEMC delivers the +access control information +to PEGC + rect rgb(255, 255, 255) + Note over PEGC 1, PEGC 2: 7. PIN profile relocation between two +PEGCs + end + PEMC->>PINE 1: 8. PEMC delivers the username and password to PINE if needed + rect rgb(255, 255, 255) + Note over PINE 1, PEGC 2: 9. PINE 1 communicates with PINE 2 via PEGC 2 + end + +``` + +Sequence diagram illustrating PEGC relocation in PIN. Lifelines: PINE 1, PINE 2, PEGC 1, PEGC 2, PEMC, PIN server. The sequence shows PEGC 1 detecting relocation, discovering PEGC 2, informing PEMC, and finally PINE 1 communicating with PINE 2 via PEGC 2. + +**Figure 7.16.2.2.1-1: PEGC relocation in PIN** + +- 1. The PINE A has application layer communication with PINE B via PEGC 1 in the PIN. +- 2. The PEGC 1 detects that PEGC 1 needs relocation, for example, the PEGC 1 will power down or will breakdown. +- 3a. The PEGC 1 discovers the PEGC 2 internal PIN. The PEGC 2 should be the PINE in the same PIN and should have the capability of gateway. +- 3b. If the PEGC 1 doesn't discover another potential gateway in PIN, the PEGC 1 can send the request to PEMC to request to discover a new PEGC in PIN. +- 4a. If in step 3a, the PEGC 1 determines the PEGC 2 itself, the PEGC 1 indicates the address information about PEGC 2 to PEMC. This PEGC address information including gateway ID or IP address will be taken into consideration when PEMC determines the new gateway. +- 5. The PEMC determines the new gateway. For example, the PEGC 2 to replace the PEGC 1. +- 6. The PEMC configures the new access control information to PEGC 2, for example, the user name, account, SSID, BSSID. This information is used to control the PINE to access the network. +- 7. The PEMC also responses to PEGC 1 that the new PEGC 2 has been determined. And before the PEGC 1 offline, the PEGC 1 triggers the PIN profile relocation to new PEGC 2, because the profile and the route information that configured in PEGC 1 can still be used by the PEGC 2. +- 8. The PEMC also sends the updated access control information and authorization information to PINE A. The Auth Info may be included for authenticating/authorizing PINE connecting to PEGC 2. +- 9. The PINE A can connect into the PEGC 2 and communicate with PINE B. + +##### 7.16.2.2.2 Change application layer communication to communication via 5GS, with the support of PIN server + +This procedure solves the situation, that PINE A has application layer communication with PINE B via PEGC. But when the communication via PEGC is not viable, for example, the PINB moves out of the coverage of PEGC 1, only newly establish the 5GS communication to connect PINE B is the potential way. + +Figure 7.16.2.2.2-1 illustrates the service continuity to change application layer communication to communication via PEGC + 5GS based on request/response model. + +Pre-conditions: + +1. The PEMC in a PIN has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PIN has already been created and a PIN ID is distributed by PIN server; +3. The PEMC has been authorized to communicate with the PIN server; +4. The PINE A has the subscription that can communicate with PINE B via 5GS; + +![Sequence diagram illustrating the service continuity to change application layer communication to communication via PEGC + 5GS. The diagram shows interactions between PINE 1, PINE 2, PEGC 1, PEMC, and PIN server. Step 1: PINE 1 communicates with PINE 2 via PEGC 1. Step 2: PINE 2 detects it will leave the location and cannot communicate via PEGC 1. Step 3: PEGC 1 requests to establish the QoS flow to PINE 2 to PIN server (also, can request PEMC to deliver) with information: QoS information, PINE 2 destination IP address. Step 4: AF triggers QoS procedure to 5GC. Step 5: PIN server decides the route information in PEGC 1. Step 6: PINE 1 communicates with PINE 2 via PEGC 1.](6031b46d356ee24f96bfe37ee2cb7616_img.jpg) + +``` + +sequenceDiagram + participant PINE 1 + participant PINE 2 + participant PEGC 1 + participant PEMC + participant PIN server + + Note right of PINE 1: 1. PINE 1 communicates with PINE 2 via PEGC 1 + Note right of PINE 2: 2. Detect PINE 2 will leave the location and cannot be communicate via PEGC 1 + Note right of PEGC 1: 3. PEGC 1 requests to establish the QoS flow to PINE2 to PIN server (also, can request PEMC to deliver) +Information: QoS information, PINE 2 destination IP address + Note right of PIN server: 4. AF triggers QoS procedure to 5GC + Note right of PIN server: 5. PIN server decides the route information in PEGC 1 + Note right of PINE 1: 6. PINE 1 communicates with PINE 2 via PEGC 1 + +``` + +Sequence diagram illustrating the service continuity to change application layer communication to communication via PEGC + 5GS. The diagram shows interactions between PINE 1, PINE 2, PEGC 1, PEMC, and PIN server. Step 1: PINE 1 communicates with PINE 2 via PEGC 1. Step 2: PINE 2 detects it will leave the location and cannot communicate via PEGC 1. Step 3: PEGC 1 requests to establish the QoS flow to PINE 2 to PIN server (also, can request PEMC to deliver) with information: QoS information, PINE 2 destination IP address. Step 4: AF triggers QoS procedure to 5GC. Step 5: PIN server decides the route information in PEGC 1. Step 6: PINE 1 communicates with PINE 2 via PEGC 1. + +**Figure 7.16.2.2.2-1: Change application layer communication to communication via PEGC + 5GS** + +1. The PINE A has application layer communication with PINE B via PEGC 1. +2. The PEGC 1 decides to use the 5GS communication to substitute the direct routing via PEGC 1. For example, if the PINE B move out of the coverage of PEGC 1 and can not communicate with PINE 1 via PEGC 1 directly anymore. +3. The PEGC 1 requests to establish the QoS towards PINE 2, reusing the procedure defined in solution 14. The PEGC 1 sends PINE 5GS connection request (PIN ID, PINE ID, Packet filters, [DN-specific ID]) to the PEMC. The PEMC sends PINE 5GS connection request (PIN ID, PEMC ID, PEGC ID, PINE ID, Packet filters) to the PIN server. +4. The PIN server will check with the 5GS that whether this PINE has the subscription to communicate with other PINE via 5GS. And if the PINE has the subscription, the PIN server will interact with 5GS to create/update the QoS flow of PEGC for the PINE. +5. According to the QoS flow establishment, the PIN server updates the route information and QoS information towards PINE 1 in PEGC 1 or the PIN server requests the PEMC to update. +6. The PINE A communicates with PINE 2 via 5GS. + +## 7.17 Solution #16: PINE registration via the PEGC + +### 7.17.1 Architecture assumptions + +The architecture of PIN is referred to the solution 1 in clause 7. + +### 7.17.2 Solution description + +#### 7.17.2.1 General + +This solution addresses aspects of Key Issue #1. + +A PINE may need to perform the PIN registration towards the PIN server to get essential authorizations for the following PIN operations like PIN join. + +The PINE is provisioned the PIN server address during the communication with PEMC. + +#### 7.17.2.2 Procedures of PINE registration via the PEGC + +Pre-conditions: + +1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PINE already establishes the connection with PEGC; + +Figure 7.17.2.2-1 illustrates the PIN registration via the PEGC procedure based on request/response model. + +![Sequence diagram of PINE registration to PIN server via PEGC](1e56c223f51992d193febf7a161af7be_img.jpg) + +``` +sequenceDiagram + participant PINE + participant PEGC + participant PIN_server as PIN server + + Note right of PEGC: 2. determine to forward to the PIN server + Note right of PIN_server: 4. Perform service authorization + + PINE->>PEGC: 1. PIN registration request + PEGC->>PIN_server: 3. PIN registration request + PIN_server-->>PEGC: 5. PIN registration response + PEGC-->>PINE: 6. PIN registration response +``` + +The diagram illustrates a sequence of interactions between three entities: PINE, PEGC, and PIN server. The sequence starts with the PINE sending a '1. PIN registration request' to the PEGC. The PEGC then performs an internal step '2. determine to forward to the PIN server' and sends a '3. PIN registration request' to the PIN server. The PIN server performs an internal step '4. Perform service authorization' and returns a '5. PIN registration response' to the PEGC. Finally, the PEGC forwards the '6. PIN registration response' to the PINE. + +Sequence diagram of PINE registration to PIN server via PEGC + +Figure 7.17.2.2-1: PINE registration to PIN server via PEGC + +1. The PINE sends PIN registration request to the PIN server. The PIN registration request is routed to the PEGC. The PINE device identity, device credentials and other necessary formation which is also needed for PIN service authorization are included. +2. The PEGC identifies the received message is the PIN registration request which is allowed to be forwarded regardless the PINE is authorized or not. +3. The PEGC forwards the PIN registration request towards the PIN server. +4. The PIN server performs service authorization and verifies the PINE device with the information in the registration request. If authorized, the PIN server allocates the PIN client ID, authorization and security credentials for the PINE. +5. The PINE server returns the PIN registration response to the PEGC. +6. The PEGC forwards the PIN registration response to the PINE. + +#### 7.17.2.3 Procedures of PINE registration during the PIN join via the PEGC + +Pre-conditions: + +1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server; +2. The PINE already establishes the connection with PEGC; +3. The PINE may get the PIN information from the PEMC, PEGC via PIN announcement after connecting to PEMC or PEGC. + +Figure 7.17.2.3.-1 illustrates the PINE registration during the PIN join via the PEGC procedure based on request/response model. + +![Sequence diagram illustrating PINE registration to PIN server via PEGC. The diagram shows four lifelines: PINE, PEGC, PEMC, and PIN server. The sequence of messages is: 1. PINE sends a PIN join/discovery request to PEGC. 2. PEGC determines that the PINE is not registered and authorized. 3. PEGC sends a Reject message to PINE. 4. PINE initiates the registration towards the PIN server (this step is shown in a separate box). 5. PINE sends a PIN join/discovery request to PEGC, which then forwards it to PEMC and then to the PIN server. The PIN server sends a response back to PEGC, which then forwards it to PINE.](0c88b98a59dd5d549fed7b13c0ca6536_img.jpg) + +``` +sequenceDiagram + participant PINE + participant PEGC + participant PEMC + participant PIN_server as PIN server + + Note right of PEGC: 2. determine the PINE is not reistered and authorized + + PINE->>PEGC: 1.PIN join/discovery request + PEGC-->>PINE: 3. Reject + Note over PINE, PEGC, PEMC, PIN_server: 4. PINE initiates the registration towards the PIN server + PINE->>PEGC: 5. PIN join/discovery request + PEGC->>PEMC: 5. PIN join/discovery request + PEMC->>PIN_server: 5. PIN join/discovery request + PIN_server-->>PEGC: 5. PIN join/discovery response + PEGC-->>PINE: 5. PIN join/discovery response +``` + +Sequence diagram illustrating PINE registration to PIN server via PEGC. The diagram shows four lifelines: PINE, PEGC, PEMC, and PIN server. The sequence of messages is: 1. PINE sends a PIN join/discovery request to PEGC. 2. PEGC determines that the PINE is not registered and authorized. 3. PEGC sends a Reject message to PINE. 4. PINE initiates the registration towards the PIN server (this step is shown in a separate box). 5. PINE sends a PIN join/discovery request to PEGC, which then forwards it to PEMC and then to the PIN server. The PIN server sends a response back to PEGC, which then forwards it to PINE. + +**Figure 7.17.2.3-1: PINE registration to PIN server via PEGC** + +1. The PINE sends PIN join/discovery request to the PEGC. The PINE device identity is included. + - For the PIN join request, the PIN ID is included. + - For the PIN discovery request, the discovery criteria are included. +2. The PEGC identifies the received message is the PIN join/discovery request, and the PINE is not registered and authorized due to no PIN client ID and credentials in the message. +3. The PEGC returns the PIN join/discovery reject message to the PINE. The registration and authorization indication are also included to instruct the PINE to perform registration. +4. The PINE if not registered, initiates the PIN registration towards the PIN server via the PEGC as described in clause 7.17.2.2. +5. After the registration, the PINE will use the PIN client ID and credentials to initiate the PIN join/discovery again. + +## 7.18 Solution #17: Service Continuity in a PIN + +### 7.18.1 Architecture enhancements + +None. + +### 7.18.2 Solution description + +#### 7.18.2.1 General + +This solution addresses aspects of Key Issue #5. The solution focuses on how a PIN application on a UE can continue to receive services from an application server after it moved out of reach of PIN element like PEGC or another PINE due to mobility. PIN service continuity in this context is maintaining reachability due to UE mobility. This solution is based on the following principles. + +- The PINE can subscribe for service continuity for one or more ongoing services involving application clients. Third party service provider and application developers, based on response to the subscription request, can make sure that the feature is available and supported for the application. The service continuity feature can be chosen for a specific application and ignored for others. E.g. service continuity can be enabled for gaming and not for TV application inside the house. +- The subscription can be authorized by PIN server and provide a service continuity policy to the PINE. PIN server is assumed to be the main trusted entity to authorize the subscription request coming from PINE. +- The PIN server informs the PEMC about allowed UE and applications which can be supported with service continuity feature. +- The PEMC configures PEGC about the PINE, which has subscribed for service continuity of a specific service. The PEGC can report back to PEMC when the UE is not reachable. The PEMC can decide at that time if it wants to trigger service continuity procedure. +- The PINE can also report about lost service to PEMC and about the available PEGCs in the PINE's proximity. The PINE reports those PEGCs, which it can reach. +- The PEMC configures a PEGC for service continuity and informs the PIN Server about the new PEGC. +- The PIN Server can expose standard APIs, to expose service continuity information to the AS. The application layer can have mechanisms to deal with service disruptions independent of any communication path changes (e.g. TCP operations), but the exposed APIs can assist the application layer to implement its own mechanism. + +NOTE: This solution is a feature that is provided by the PINAPP layer. An application can also support service continuity via procedures that are outside of 3GPP's scope and, in such a scenario, would not support this service continuity procedure. Further, an application can decide to not support this service continuity procedure if the application e.g. has particular requirements for authentication. + +#### 7.18.2.2 Procedure + +This section provides details of Solution #17. + +##### 7.18.2.2.1 Functional entities + +**PIN Client:** A PINAPP function in UE, PINE, which subscribes for service continuity and informs when service is lost. + +**PIN Management Client (PEMC Client):** A PINAPP in PEMC, configures the PEGC and PINE for service continuity. Informs PIN server about updates related to service continuity. + +**PIN Gateway Client (PEGC Client):** A PINAPP in PEGC, obtains configuration from PEMC and executes service continuity procedure. + +**PIN Server:** Supports PIN Client, PIN Management Client by providing service continuity related information when requested by PIN Management Client. It can expose service continuity information to external entities through APIs. + +##### 7.18.2.2.2 Procedures of PIN Service Continuity while the PINE is connected to a PEGC + +Figure 7.18.2.2.2-1 illustrates a service continuity procedure for scenario 1, based on request/response model. + +![Sequence diagram illustrating PIN Service Continuity procedures while the PINE is connected to a PEGC. The diagram shows interactions between PINE1 (PIN Client), PEMC (PEMC Client), PEGC (PEGC Client), PIN Server, and AS. The process involves subscription, configuration, connectivity loss detection, activation, and eventual service resumption after a PEGC change.](38a51baf4d5b8857d162e5d9a0645269_img.jpg) + +``` + +sequenceDiagram + participant PINE1 as PINE1 (PIN Client) + participant PEMC as PEMC (PEMC Client) + participant PEGC as PEGC (PEGC Client) + participant PIN Server as PIN Server + participant AS as AS + + Note left of PINE1: 1 + PINE1->>PEMC: Subscribe for Service Continuity + PEGC->>PIN Server: Authorize subscription for service continuity (ServiceID, AS information) + PIN Server->>PEMC: Configure for Service Continuity (PEID, Service ID) + PEMC->>PINE1: OK + Note left of PINE1: 2 + Note right of PINE1: If PINE was communicating through PEGC, connectivity loss event can trigger Service continuity procedure in PEGC + Note left of PINE1: Alternatively PINE sends, Activate service continuity (PEID, SERVICE ID) + PINE1->>PEMC: Activate service continuity (PEID, SERVICE ID) + Note right of PEGC: 3 + PEMC->>PEMC: PEMC decides to initiate service continuity procedure + Note left of PINE1: 4 + PEMC->>PIN Server: Update service continuity information (PEID, Service ID, SC_Status) + Note right of PIN Server: 5 + PIN Server->>AS: Update Service continuity information (PEID, Service ID, IP address of PINE) + Note left of PINE1: 6 + Note right of PINE1: PINE finds a new PEGC and connects to it. PEMC becomes aware of the new PEGC that the PINE is connected to, or new PEGC can inform PEMC + Note right of PEGC: New PEGC becomes part of the Service continuity procedure + Note left of PINE1: 7 + PEMC->>PEGC: Configure new PEGC for Service continuity (PEID, ServiceID, AS information) + PEGC->>PEMC: Ok (PEGC IP address, port#) + Note left of PINE1: 8 + PEMC->>PIN Server: Update PIN Server about Service continuity through new PEGC (PEGCID, IP Address, Port#, SERVICE ID) + Note right of PEGC: 9 + PEGC->>PIN Server: Update terminating PEGC information + Note left of PINE1: 10 + PIN Server->>AS: Update Service continuity information (PEGC ID, PIN ID, Service ID, PEGC IP address) + Note right of PINE1: Service resumes + +``` + +Sequence diagram illustrating PIN Service Continuity procedures while the PINE is connected to a PEGC. The diagram shows interactions between PINE1 (PIN Client), PEMC (PEMC Client), PEGC (PEGC Client), PIN Server, and AS. The process involves subscription, configuration, connectivity loss detection, activation, and eventual service resumption after a PEGC change. + +Figure 7.18.2.2.2-1: PIN Service Continuity when the PINE is connected via PEGC + +Pre-conditions: + +- More than one PEGC is serving the PIN. +- PEMC connectivity is not lost by a PINE. +- The PIN Client in UE has been either pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC Client, PIN server. +- The PEMC Client supports functionality to execute the service continuity procedure. +- The PEGC Client supports functionality to execute the service continuity procedure. +- The PIN Server has capability to expose service continuity information to external entities such as identification of a service and any changes to the end points of the service. + +1. A PIN Client in a UE subscribes for service continuity with the PEMC and PIN server. The purpose of the subscription request is to inform the PEMC and PIN Server that the PINE would like to continue an ongoing service if it loses connectivity with PEGC. The subscription request includes application level IDs such as, PEID, one or more Service identifiers which need service continuity, Application session ID, Destination PIN ID, and an IPv4 Tuple that describes the session. The IPv4 tuple can include the IP Address of the UE, the IP Address of the Server that provides the service, the UE port numbers that are associated with the service, and the port numbers on the server that are associated with the service. + +The PIN Server authorizes the subscription request, and provides PEMC Client with policy information about service continuity for the PINE. + +The PEMC configures PEGC for service continuity procedure by providing PEID, Service ID. + +The PEMC client informs the PINE if service continuity for the requested services is allowed or not. + +2. The PINE moves and loses contact with the PEGC. The loss of connectivity with the PINE can trigger service continuity procedure in the PEGC based on PEID and Service ID. +3. The PEGC Client informs the PEMC Client about the service discontinuity of the PINE by sending an “Activate service continuity” message, which includes PEID, Service ID. As an alternative PINE can also inform PEMC to activate the service continuity procedure. +4. The PEMC client decides if it is required to initiate service continuity procedure, and of so informs the PIN Server to update about the service continuity procedure, initiated by PEGC or PINE. The PEMC client sends an “Update Service Continuity information” to the PIN server with information such as the PEID, Service ID, Service continuity status like Started, Executing, Completed. This allows the PIN server to immediately update service continuity information and share with AS, rather than waiting for PINE to discover a new PEGC and update service continuity status. +5. The PIN server updates information about the service continuity such as identification of the service, involved PINEs and service continuity status to an external AS. +6. It is assumed that the PINE has the information about other available PEGCs in the PIN (possibly provided by PEMC during start-up procedure). The PINE is able to find and connect to another PEGC in the PIN. It is also assumed that PEMC Client becomes aware of the PINE connecting to the new PEGC. +7. The PEMC client determines, based on PEID, Service continuity policy, that the new PEGC can be configured to handle service continuity for the PINE. The PEMC Client sends a “Configure new PEGC” message to configure the PEGC with: + +- a) Session ID; +- b) destination PINE information, which is a list of PEID, IP address, Port number or URL; and +- c) Application Server information, which will resume service with the PEGC. Information includes Application Server ID, Application Server port-number, so that the new PEGC can configure to receive information from the Application Server. + +PEMC also collects the PEGC IP address and PEGC port-number, in the response message. + +8. The PIN Management Client sends an “Update Service continuity information” to the PIN server, to indicate that configuration of PEGC and PINE has happened successfully, and the service can be resumed, with information such as: + - a) Service ID: Service to be resumed; + - b) Application Server ID: Identifies the Application Server, which was providing service; + - c) Terminating PEGC ID; + - d) Terminating PEGC reachability information, such as IP address, port number, URL etc.; and + - e) Terminating Destination PINE reachability information, such as IP address, port number, URL etc. +9. PIN Gateway Client informs PIN Server that it is ready to resume the service with identification information from step 7. PIN Server updates this information and makes available for external entities. + +10. The IP address of PINE and PEGC can change or at application-level IP preserving technique can be applied. PIN Server updates all information for service continuity, which can be used to resume the service to a new destination IP address. PIN Server updates an external AS with the new service continuity information such as: + +- a) Application Session ID: identifies the application session to be switched to new endpoint; and +- b) Terminating IP Address: + - IP address of PINE, port-number where the service will be terminated; and + - IP address of the PEGC, which will forward the service to PINE. + +##### 7.18.2.2.3 Procedures of PIN Service Continuity while the PINEs are connected directly + +Figure 7.18.2.2.3-1 illustrates a service continuity procedure for scenario 2, based on request/response model. + +This procedure involves finding a new PEGC for a PINE's indirect communication by the PEMC. Selection of the new PEGC is dependent upon having connectivity between the PEMC and the PINEs (e.g. PINE1 and PINE2) involved. When the direct connection between PINEs is lost, the PEMC cannot determine correctly a PEGC which has connections to both PINEs. The PEMC requests that the PINEs to PEGCs which it can connect to. Then PEMC can select a PEGC, which has connectivity to both PINEs. These steps differentiate the service continuity procedure from PEGC reselection procedure. + +![Sequence diagram illustrating the PIN Service Continuity procedure when PINEs are connected directly. The diagram shows four lifelines: PINE (1..N) (PIN Client), PEMC (PEMC Client), PEGC (1..N) (PEGC Client), and PIN Server. The sequence of messages is: 1. PINE (1..N) sends a 'Subscribe for Service Continuity' to PEMC, which then sends an 'Authorize subscription for service continuity' to PIN Server. PIN Server responds with 'OK' to PEMC. 2. PINE (1..N) sends an 'Inform SC lost (PEIDs, Service ID)' to PEMC. 3. PEMC sends a 'Trigger PEGC discovery and report back (PEGC credentials)' to PINE (1..N), which responds with 'OK (PEGC LIST)'. 4. PEMC sends a 'Configure new PEGC for Service continuity (PEID, ServiceID, AS information)' to PEGC (1..N). 5. PEMC sends a 'Configure PINE (PEGC information)' to PINE (1..N). 6. A rounded rectangle labeled 'Service resumes' indicates the final state.](45578bd3ed11d45af63ce00e28bab2f8_img.jpg) + +``` + +sequenceDiagram + participant PINE as PINE (1..N) +(PIN Client) + participant PEMC as PEMC +(PEMC Client) + participant PEGC as PEGC (1..N) +(PEGC Client) + participant PIN as PIN Server + + Note left of PINE: 1 + PINE->>PEMC: Subscribe for Service Continuity + PEMC->>PIN: Authorize subscription for service continuity + PIN-->>PEMC: OK + Note left of PINE: 2 + PINE->>PEMC: Inform SC lost (PEIDs, Service ID) + Note left of PINE: 3 + PEMC->>PINE: Trigger PEGC discovery and report back (PEGC credentials) + PINE-->>PEMC: OK (PEGC LIST) + Note right of PEGC: 4 + PEMC->>PEGC: Configure new PEGC for Service continuity (PEID, ServiceID, AS information) + Note left of PINE: 5 + PEMC->>PINE: Configure PINE (PEGC information) + Note right of PEGC: 6 + Note right of PEGC: Service resumes + +``` + +Sequence diagram illustrating the PIN Service Continuity procedure when PINEs are connected directly. The diagram shows four lifelines: PINE (1..N) (PIN Client), PEMC (PEMC Client), PEGC (1..N) (PEGC Client), and PIN Server. The sequence of messages is: 1. PINE (1..N) sends a 'Subscribe for Service Continuity' to PEMC, which then sends an 'Authorize subscription for service continuity' to PIN Server. PIN Server responds with 'OK' to PEMC. 2. PINE (1..N) sends an 'Inform SC lost (PEIDs, Service ID)' to PEMC. 3. PEMC sends a 'Trigger PEGC discovery and report back (PEGC credentials)' to PINE (1..N), which responds with 'OK (PEGC LIST)'. 4. PEMC sends a 'Configure new PEGC for Service continuity (PEID, ServiceID, AS information)' to PEGC (1..N). 5. PEMC sends a 'Configure PINE (PEGC information)' to PINE (1..N). 6. A rounded rectangle labeled 'Service resumes' indicates the final state. + +Figure 7.18.2.2.3-1: PIN Service Continuity when PINEs are connected directly + +Pre-conditions: + +- One or more PEGC is serving the PIN. + - PEMC connectivity is not lost by a PINE. + - The PIN Client in UE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PEMC Client. + - PIN client is capable of triggering PEGC discovery procedure by PINE and provide report about the discovered PEGCs. + - The PEMC Client supports functionality to execute the service continuity procedure. + - The PEGC Client supports functionality to execute the service continuity procedure. + - The PIN Server has capability to communicate with Application Server to identify a direct service and provide policy and authorization information. +1. A PIN Client in a UE, subscribes for service continuity with PEMC or PIN server. The purpose of the subscription request is to inform that PINE would like to continue an ongoing service with another PINE, connected directly. The subscription request includes PEID, one or more Service identifiers which need service continuity, Destination PIN ID, and an IPv4 Tuple that describes the session. The IPv4 tuple can include the IP Address of the first UE, the IP Address of the second UE and the UE port numbers that are associated with the service. + - a) The PIN Server authorizes the subscription request and provides PEMC Client with policy information about service continuity for the PINEs. + - b) PEMC client informs the PINE if service continuity for the requested services is allowed or not and policy information related to service continuity. + 2. The PINE moves and loses contact with other PINE. The loss of connectivity results in service discontinuity between the PINEs. PIN Client informs PEMC Client about the service discontinuity by sending an “Inform SC lost” message, which includes PEIDs, Service ID. + 3. Triggering PEGC discovery by PINE, allows PEMC to be sure that the PINE can connect to the selected PEGC. If PEMC selects a PEGC using its own knowledge, there is a possibility that the PINE cannot connect to it. All the involved PINEs start PEGC discovery and reports back to PEMC, a list of discovered PEGCs with the OK message. + 4. PEMC client goes through one or more lists sent by one or more PINEs and selects one or more optimal PEGCs for service continuity. The PEMC Client sends a “Configure new PEGC” message to PEGC Client to configure PEGC with the following information, so that PEGC can setup forwarding path between the two PINEs. + - a) Service ID: The service that needs to be handled by PEGC. + - b) Destination PINE information, which is a list of PEID, IP address, Port number or URL. + 5. PEMC client configures PINE with the new PEGC information such as IP address, port-number, URL, and triggers connection setup. + 6. Once the connection between PINE and PEGC is successful, the service resumes. + +### 7.18.3 Solution evaluation + +The solution addresses the problem when PIN application on a UE is consuming service from an application server and due to UE mobility, how the PIN application on the UE can continue to receive services from the application server. Due to mobility the UE can go out of reach of the PEGC which was delivering service. + +The solution describes how the service continuity procedure is initiated. Serving PEGC detects that the UE is out of reach and informs PEMC client. PEMC client updates PIN server about the Service Continuity procedure status. + +To continue the service, UE can connect to a new PEGC, and inform PEMC client. To complete service continuity, PEMC configures the new PEGC to support service continuity and updates PIN server about the status of the procedure and new end point information. Once configuration is complete, service resumes towards the UE through the new PEGC. + +The detailed role of PEGC involvement for service continuity procedures requires further evaluation considering different PINE status and application scenarios. + +# 8 Deployment scenarios + +## 8.1 General + +*This clause provides a general description of the deployment scenarios.* + +## 8.x Deployment scenario #x: <Title> + +*Provide an illustrative description of the deployment scenario.* + +# 9 Overall evaluation + +*This clause provides a summary of architecture enhancements and solution evaluations.* + +## 9.1 Architecture enhancements + +## 9.2 Key issue evaluations + +### 9.2.1 General + +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. + +**Table 9.2.1-1 Key issue and solutions** + +| Key issues<br>(evaluation clause reference) | Solution | Architectural<br>enhancement<br><br>(clause<br>reference) | Enhancements<br>required | Dependency on<br>other working<br>groups | +|----------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------|--------------------------------|------------------------------------------| +| <i>KI#1: PIN Management</i> | <i>Solution #x:<br/><title></i> | <i>6.x</i> | <i>Architecture /<br/>None</i> | <i><WG></i> | +| | <i>Solution #y:<br/><title></i> | <i>6.y</i> | <i>Architecture /<br/>None</i> | <i><WG></i> | +| <i>KI#2: PINAPP accesses 5G network by<br/>application mechanism</i> | <i>Solution #x:<br/><title></i> | <i>6.x</i> | <i>Architecture /<br/>None</i> | <i><WG></i> | +| <i>KI#3: Service switch in PIN</i> | | | | | +| <i>KI#4: PIN Application Server Discovery</i> | <i>Solution #11:<br/>Application Server<br/>Discovery in a PIN</i> | | | | +| <i>KI#5: Service continuity</i> | | | | | +| <i>KI#6: PEMC/PEGC replacement in PIN</i> | | | | | + +For KI#1 and KI#6, they describe the management (control plane interaction) of PIN. + +**Phase 1: Prepare phase, before PIN create.** + +Before the PIN create, two procedures should be done. + +Firstly, as solution 12 describes, the PEMC, PEGC, PINE should register into the PIN server first. This procedure has two purpose. The fist is some of the PINE can receive the role of PEMC from PIN server. The second purpose is the device metadata of PINE, for example, the MAC address, GPSI, PIN client ID and etc can be obtained by PIN server. + +Secondly, as solution 7 describes, the PIN server discovery. Some of the PIN management procedures needs the PIN server to help. So, the PINE should receive the PIN server endpoint address first and then trigger the phase 2 procedure. + +#### Phase 2: PIN management procedure. + +In phase 2, it is the real PIN management procedure. And during the PIN management procedure, it can be divided as the following parts: + +1. PIN lifecycle: PIN create/delete. +2. PIN management procedure internal PIN (PIN modification): Including the PEMC/PEGC changes and PIN Profile recover. +3. Member management: Including add PINE into a PIN or delete a PINE from PIN. +4. PIN configuration: PIN Profile. + +For the PIN lifecycle, it includes the PIN create/modification/delete. The PIN create (solution 2) can only be triggered by PEMC, and approved by PIN server. For the PIN delete (solution 10), the PEMC can trigger the delete either internally or with the help of PIN server's authorization that a PIN is not needed. Also, the PIN server can trigger the PIN release for example, the life cycle of PIN comes to the end. + +For the PIN management procedure internal PIN (PIN modification), it includes the role changes of PEMC/PEGC. For the PEMC changes, it includes the PEMC changes itself (Solution 2), PIN server triggers PEMC changing (Solution 2), PEMC failure triggers the relocation (Solution 9). For PEGC relocation, it includes (Solution 2) the PEGC relocation itself, PEMC triggers the PEGC relocation, PIN server triggers the PEGC relocation. During the PEMC/PEGC relocation procedure, the PIN profile also need to recover. (Solution 2) A PIN profile recover procedure that recover the profile from PIN server is defined. + +For the member management, it includes the add PINE into a PIN or delete a PINE from PIN. For adding the PINE into a PIN, only the PINE takes the initiative to join the PIN is defined. (Solution 5) The PINE discovers the PIN from PEMC/PIN server first, and the PINE joins the PIN (Solution 3). For removing a PINE from PIN, one possible way is (Solution 3) the PINE leaves a PIN and this PINE is removed. Another possible way is (Solution 3) the PEMC/PIN server removes the PINE in a PIN. + +For the PIN configuration, it is related to the definition of PIN profile. (Solution 6) PIN profile and dynamic PIN Profile are defined to describe the related information about PINE, PEMC and PEGC. For example, the ID, endpoint address and etc. This information is important for a PIN, and can be seen as the control plane management information for the PIN. + +#### Phase 3: Enhancement function of PIN + +After the PIN management procedure, some of the enhancement functions are defined in the PIN, including: + +1. PINE communication via 5GS: the most important and fundamental features that PIN provide +2. Service Switch: offload the application traffic to internal PIN or changes the traffic termination +3. Application Server Discovery in a PIN: enhance the PIN to support application server procedure +4. PIN Continuity: A variety of PIN device interaction and changes the communication path, for example, via Gateway or via 5GS. + +For PINE communication via 5GS, (solution 14) PIN server triggers the QoS establishment or the PEGC triggers the PDU session establishment/modification (to coordinate with SA2). + +For Service Switch, two possible solutions are defined: (Solution 8) PIN server assisted service switch and (Solution 10) Service switch internal PIN. + +For Application Server Discovery in a PIN, (Solution 11) one or more PINAPP(s) (e.g. in a PEMC or in a PIN server) can maintain a registry to manage information about AS(s) that are available to the PIN. The AS(s) register their availability with the PINAPP. And the AS can be discovered at PIN server. + +**Editor's note:** PIN Continuity parts need to update later. + +#### Phase 4: Architectures of PIN + +(Solution 1) PIN enabler architecture needs a new design of PIN enabler layer that both supports AC and the 3GPP communication layer. + +(Solution 13) Another SEAL enhancement architecture is the UE also has a SEAL group management client, and the PIN client interact with the SEAL group management client via the GM-C to achieve PIN management. + +### 9.2.2 Evaluation of key issue #1: PIN Management + +For PIN create that addressed in KI#1, solution 2 gives the solution of the PIN create procedure with the following principle: + +- The PIN creation can only be triggered by the PEMC. The PINE receives the role of PEMC during the registration procedure towards PIN server as indicated in solution 12. And the PEMC receives the PIN server endpoint address before triggering the creation. +- The PEMC sends the PIN create request to PIN server with the GPSI, PIN client ID, UE location, security credential and PIN profile. The PIN profile includes some of the information that PEMC can request defined in solution 6, for example, the description of PIN, duration of PIN and etc. +- The PIN server sends a successful response to PEMC, which includes a newly assigned PIN ID to indicate the PIN. Also, the PIN lifetime or duration can be indicated to PEMC. If the PIN creation request fails, the PIN server should give the failure response to indicates that indicates the cause of PIN creation request failure. +- After the PIN create successfully, the PIN server or PEMC can allocate the access control information to PEGC if the gateway is selected for the PIN and delivers the access control information to PINEs. The access control information includes: user name, account, SSID, BSSID and etc. All the information is used by PINE in PIN to access the PEGC or benefited by 5GS communication. + +For PIN delete that addressed in KI#1, solution 4 gives the solution of the PIN delete procedure with the following principle: + +- The PIN delete can be triggered either by PEMC or PIN server. All these two situations are valuable. + - The PEMC decides to delete the PIN due to the PIN is not needed or the lifecycle of PIN comes to the end. The PEMC can delete the PIN locally or request PIN server to delete the PIN + - The PIN server can trigger the PIN delete procedure, for example, when the life cycle of PIN is end or the PIN server decides to stop the PIN service in this PIN and release the PIN resource. +- For PEMC triggers PIN delete and sends request to PIN server: the PEMC sends a PIN delete request to the PIN server to request to delete the PIN. The PIN delete request includes the security credentials of the PIN client received during PIN client authorization procedure and PIN ID. The PIN ID indicates this PIN will be deleted. +- If the PEMC detects that the lifecycle of PIN comes to the end, the PEMC can decide to delete the PIN locally. And the PEMC shall indicate the deletion of PIN to PIN server which includes the PIN ID. +- For PIN server deletes the PIN: An event occurs at the PIN server that satisfies trigger conditions for notifying a subscribed PEMC of a PIN. If the life cycle of a PIN is end or the PIN server decides to not provide any PIN resource in this PIN, the PIN server should trigger a PIN delete procedure to the PEMC. + +If a PIN is deleted, the PIN resource will be released and the PIN service will be stopped. Some of the procedure related to the deleted PIN defined in solution 4 addresses the principle below: + +- After PIN delete, the PEMC sends the notification to PEGC and PINE that in this PIN to delete the PIN profile related to the deleted PIN, which indicated by PIN ID. This is a notification procedure. +- The access control information in PEGC that related to this PIN and PINE in this PIN should be deactivated. + +- After PIN delete, if PIN is deleted by PEMC locally, the PEMC sends a PIN status update notification to the PIN server to indicate the PIN has been deleted. In this notification, the PIN ID is included. The PIN server updates the PIN profile to remove the details of this PIN which represented by PIN ID. +- After PIN delete, if the PIN is deleted by the PIN server, the PIN server sends the PIN status update notification to the PEMC to indicate the PIN has been deleted. In this notification, the PIN ID is included. The PEMC updates the PIN profile to remove the details of this PIN which represented by PIN ID and triggers other notification towards the PINE/PEGC in this PIN. + +Solution 7 addresses Key Issue 1 and describes the aspects of PIN server discovery. All of the PINE, including PEMC, PINE and PEGC should discover the PIN server first, and then have the interaction towards PIN server. The PIN server discovery procedure should be done before the PIN management. + +- Solution #7 addresses the procedure of PIN server discovery. The PIN server can be discovered by the following method as indicated in Solution #7: + - pre-configured in the PIN elements or PIN clients; + - configured by the user; + - provisioned by MNO through 5GC procedure; or + - derived from HPLMN identifier for non-roaming scenario or from VPLMN identifier for roaming scenario. + +For the provisioned by MNO through 5GC procedure, this has several drawbacks. Firstly, this has the impact to 5GC NAS procedure. Secondly, in order to deliver the PIN server endpoint address to the PIN enabler layer, the UE OS should have an enhancement. At last, if the PIN procedure are all happen in the application layer scope, that the 5GS is not aware of PIN, and this needs the 5GC impact that AF provides the PIN server endpoint address to 5GC. But whether SA2 support this is FFS. So, the PIN server endpoint address that provisioned by MNO through 5GC procedure is not appropriate to be included in the method of PIN server discovery. + +Solution 7 also addresses the method that due to PINE receives the PIN server endpoint address from the PEGC and PEMC. + +For example, if PINE has application layer connection with PEGC, for example, via WiFi or Bluetooth pairing, so there are two ways for PINE discovering PIN server: + +- If the PINE connects to PEGC with user name and password, the PINE sends PIN server discovery request to PEGC. The requests include the GPSI, PIN client ID if has, UE location. PEGC can response with PIN server end point address directly. +- If the PINE has the open access to PEGC that with no user name or password. For this situation, the PINE can't consume the communication service that provided by PEGC, but can have communication with the PEMC behind the PEGC. The PINE sends PIN server discovery request to PEGC and the PEGC routes the requests to PEMC. The request includes the GPSI, PIN client ID if has, UE location. PEMC can response with PIN server end point address to PINE via PEGC. + +Due to for some of the PIN elements can have the application interaction towards the PEMC, for example, via WiFi or Bluetooth pairing, so the PEMC can provide the PIN server end point information to PIN elements. The PINE sends PIN server discovery request to PEMC. The requests include the GPSI, PIN client ID if has, UE location. The PEMC delivers the PIN server end point information to PIN elements or PIN client. The end point information of PIN server includes URI(s), FQDN(s), IP address(es) of PIN server. + +For PIN discovery of PINE that addressed in KI#1, solution 5 gives the solution of the PINE discovers the PIN with the following principle: + +- The PINE can discover the available PIN from two methods: + - The PINE can send PIN discovery request to PEMC of a PIN. + - The PINE can send PIN discovery request to PIN server. +- If the PINE has already had an application layer connection with a PEMC which manages a PIN, the PINE sends the PIN discovery request to PEMC. The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI if available, PIN client ID, UE location, the service that PINE wants to consume and PIN client profile(s) information. + +- If the PINE has already had the application layer connection towards PEGC, and the PINE has already received the PIN server endpoint address, the PINE sends the PIN discovery request to PIN server. The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI, PIN client ID, UE location, the service that PINE wants to consume and PIN client profile(s) information. +- In the PIN discovery request to both PEMC or PIN server, the PINE can have the filter information in the PIN discovery request for example, the interesting area, the interesting type of PIN and etc. The filter information can be used for providing certain PIN information. + +Solution 12 and solution #16 addresses Key Issue 1 and describes the aspects of PINE/PEMC/PEGC registration procedure that ahead of PIN creation. + +- Solution #12 addresses the procedure that happens before PIN create. + - For the PEMC, the PEMC sends Registration Request (GPSI) to the PIN server. After successful registration in PIN server, the PIN server allocates the PIN client ID to this PEMC and the PEMC receives the role of PEMC. +- For the PINE and PEGC, the PINE/PEGC registers itself into PEMC with the device metadata (MAC address, vendor name, device description, PINE/PEGC Address). And the PEMC substitutes the PINE/PEGC to register on PIN server. After successful registration in PIN server, the PIN server allocates the PIN client ID to PINE/PEGC. +- Solution #16 addresses the procedure that happens before PINE joining any PIN. + - The PINE initiates the PIN registration towards the PIN server via the PEGC with the device information. And the PEGC is designed to identify the PIN registration message and forwards such message regardless of the PINE is authorized or not. The PINE gets the PIN clients ID, necessary authorization and security credentials from the PIN server via this PIN registration. + - If the PINE initiates the PIN join/discovery request without the registration and authorization, the PEGC rejects such PIN messages, and trigger the PINE to initiate the PIN registration towards the PIN server. + +Solution 6 addresses the aspects of Key Issue 1 related to what information needs to be maintained at the PIN server, PEMC, PEGC and PIN elements. Information maintained at these entities are classified into 2 types – PIN profile and dynamic profile information. Solution 6 captures the information that needs to be maintained at each of the PIN entities in detail. + +Solution 3 addresses Key Issue 1 and describes the aspects of PINE join into a PIN and remove the PINE from a certain PIN. Solution #3 addresses the procedure that happens after PINE accomplish PIN discovery, and the PINE has the application layer connection with PEMC + +For PINE joins into a PIN: + +- The PINE sends the request to PEMC to join the PIN. The request includes the security credentials of the PIN client, UE identifier such as GPSI, UE location, PIN ID and PIN client profile(s). After PEMC authorizes the request and accept the PINE to join the PIN, the PEMC notifies to PEGC/PIN server in PIN. The PEMC/PEGC/PIN server updates the PIN profile. The access control information in PEGC for this PINE is delivered by PEMC during the notification. +- During PIN create procedure, the PEMC can request to create a PIN including the potential PIN elements to be added into a PIN. +- The PINE sends PIN join/discovery request to the PEGC. The PEGC identifies the received message is the PIN join/discovery request, and the if the PINE is not registered and authorized due to no PIN client ID and credentials in the message, the PINE registration procedure will be also included. + +For removing PINE from a PIN, two potential ways: + +- The PEMC removes a PINE from PIN, and notify the result to PEGC/PIN server. The PEMC/PEGC/PIN server updates the PIN profile. The access control information in PEGC for this PINE is disabled after receiving the notification from PEMC. +- If the PINE decides to leave the PIN, the PINE sends the request to PEMC to leave the PIN. The request includes the security credentials of the PIN client, UE identifier such as GPSI, UE location, PIN ID and PIN client + +profile(s). After PEMC authorizes the request and accept the PINE to leave the PIN, the PEMC notifies to PEGC/PIN server in PIN. The PEMC/PEGC/PIN server updates the PIN profile. The access control information in PEGC for this PINE is disabled after receiving the notification from PEMC. + +Optionally, the PIN server can also be involved in the procedure of PINE added/removed into/from PIN. The PIN server can decide the PINE added/removed into/from PIN or the PIN server can be notified by the result of PINE added/removed into/from PIN. + +Solution 14 addresses Key Issue 1 and describes the aspects of credentials provisioning procedure. + +- Solution #14 addresses the procedure below: + - The PINE sends Credential Provisioning Request (PIN ID, PINE ID, Duration) to the PEGC. + - The PEGC sends the Credential Provisioning Request to the PEMC directly, or sends PEMC Notification (PEGC ID, Credential Provisioning Request) to PIN server and PIN server sends PEMC Event Notification (PEGC ID, Credential Provisioning Request) to the PEMC. + - The PEMC/PEGC sends Credentials Provisioning Response to PINE. + +NOTE: Which entity that the PEMC/PEGC obtains the Credentials, for example, the PIN server, 5GS or other NFs, is in the scope of SA3. + +### 9.2.3 Evaluation of key issue #2: PINAPP accesses 5G network by application mechanism + +Solution 14 addresses Key Issue 2 and describes how to enable the PIN with 5GS communication. For the PIN that support 5GS communication, the PIN can trigger to establish the PDU session or QoS for PINE. + +- Solution #14 addresses two procedures that enable the PIN with 5GS communication: + - Establish QoS for PINE with PIN server support. + - PEGC triggers PDU session establishment/modification for PINE when no PIN server deployed. + +For the PIN server requests 5GS to establish QoS for PINE, this reuses the procedure defined in SA2 that AF triggers the QoS establishment procedure. No impact to SA2 procedure. After receiving the destination IP address of other UEs or application clients, the PINE sends PINE 5GS connection request (PIN ID, PINE ID, Packet filters, [DN-specific ID]) to the PEMC, via PEGC. And the PEMC sends PINE 5GS connection request (PIN ID, PEMC ID, PEGC ID, PINE ID, Packet filters) to the PIN server. The PIN server should receive the Packet filters, DN-specific ID from PEMC that these parameters are used for AF to trigger the QoS. If the IP address of the PEMC/PEGC is changed, the PEMC/PEGC sends Event Notification (PEMC/PEGC ID, old IP address, new IP address) to the PIN server. + +Another alternative procedure is PEGC triggering PDU session establishment/modification for PINE without PIN server. This procedure is applied to adapt to SA2 PIN. The PINE may send traffic to PEGC, triggered by the traffic, the PEGC sends PIN Communication Request (PIN ID, MAC address/IP address, Traffic descriptors) to the PEMC. The PEMC sends Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) to the PEGC. The PEGC configures the local rule accordingly. According to the Packet filters, the PEGC may initiate PDU Session Modification with the Packet filters and requested QoS towards 5G system in order to make 5GC configure the N4 rules for UPF(s). + +### 9.2.4 Evaluation of key issue #3: Service switch in PIN + +This clause provides an overall evaluation for Key Issue #3, "Service switch in PIN". + +Solution #8 and #10 address aspects of Key Issue #3. + +Key Issue #3 studies how to support an application mechanism for service switching in a PIN between different PIN applications. + +- a) To execute a service switch, a PIN, which can handle the service must be discovered. + +Solution #8: + +- Describes application-level discovery of available PIN, where a PIN Client in a UE sends a discovery request to a PIN Server. +- Discovery request includes Location information, Application requirements such as Display characteristics, Audio characteristics. +- PIN Server based on Location and application service requirement can provide the PIN Client with information about, one or more available PIN IDs, details of PINAPP capabilities and corresponding PE IDs, such as Device ID, IP address and Port number for each PIN. + +Solution #10: + +- PINE is part of the PIN and initiates service discovery with PEMC. +- PEMC provides the details of the PIN Service (e.g. service type) and the PINE end point and application end point information. + +b) Among available PINs, the Application client can select a PIN and initiate service switch procedure. + +Solution #8: + +- PIN Application Client selects a PIN and requests that the PIN Server trigger a service switch procedure. +- PIN Application Client sends information such as Application session ID, Destination PIN ID, and an IP 4 Tuple that describes the session. +- PIN Server accepts the request and sends acknowledgement to PIN Client. + +Solution #10: + +- PIN Application client and the corresponding PINE is part of the PIN, selects the suitable PINE where the service can be switched. +- Selection is based on the following principles: firstly, whether this potential PINE has deployed the same application client as PINE and, secondly, whether this potential PINE can maintain the same service type as PINE + +c) The service switch procedure is handled differently in the two solutions. + +Solution #8: + +- PIN server can select the PIN Applications in PINE and instruct the PIN Management Client to execute service switch procedure. +- Information sent to PEMC Client includes Application Session ID, Destination PINE information, which includes PE ID, IP Address, Port number, URL. +- PEMC configures PEGC and PINE and sends end point information to PIN server. A flag is used to indicate PEGC, if the session needs to be split among more than one PINEs. + +NOTE: The target PINE and PEMC are assumed to have already performed an authentication and authorization procedure. + +- Thus, the solution relies on the PEMC to configure the target PINE and direct interaction between the original PINE and target PINE can be avoided. +- PIN server stores updated service switch related end point information and can make available to external AS through APIs, if it wants to use for its own service switch method. + +Solution #10: + +- Service switch being handled via direct interaction between the PINEs. +- Switch traffic flow directly from one PINE to another via direct communication method or via the PEGC. The destination IP address is always the original PINE and the original PINE forwards the traffic to the new PINE. + +- Application context is relocated along with application context to another PINE and the service resumes. After the context relocation, the application client in PINE triggers the application relocation to potential PINE. Note that this procedure changes the destination IP address +- In order to maintain the integrity of the application process, the application traffic from application server should be terminated at the PINE first. The PINE transfers the application traffic to the potential PINE directly or via the PEGC. + +### 9.2.5 Evaluation of key issue #4: PIN Application Server Discovery + +This clause provides an overall evaluation for Key Issue #4, "PIN Application Server Discovery". + +Solution #11 is the only solution that addresses Key Issue #4. + +- Solution #11 maintains a registry of PIN AS in the PINAPP, which is used to discover PIN AS by Application clients. + - The registry function can be part of the PEMC Client and PIN Server. + - This registry function information can be provisioned or configured in the UE or PIN Client. + - Registry function information can be an address, endpoint, or service API information. + - PIN Clients use the registry function information to query about PIN AS. + - Application clients in the PIN can register with the Registry function, through PIN client using the registry information. + - The PINAPP registry functions in a PIN can communicate and update information about PIN AS that are stored in the registry. Furthermore, the PIN Server can configure the PINAPP with Usage Policies + - PINAPP registry function in PIN server can communicate with the registry function in other PIN servers, which belong to different PIN. + +### 9.2.6 Evaluation of key issue #5: Service continuity + +Solution #17 and #15 address aspects of Key Issue #5. + +To execute a service continuity, first it needs to be detected that the mobile PINE is out of reach of the serving PEGC or another PINE in case of direct communication. After detection, the service continuity procedure can be triggered. + +- Solution #17 describes application-level detection by the serving PEGC, which was delivering service, that the PINE is out of reach. The PEGC informs PEMC about the condition that the service to the PINE may be disrupted. In the case of direct communication, the PINE informs PEMC about the loss of direct communication. +- Solution #15, addresses the situation where PINEs are interacting via PEGC and a PINE moves out of reach of the PEGC. The PEGC detects the PINEs are out of reach and initiates service continuity procedure. The PEGC discovers another PEGC or requests that PEMC discover another PEGC for the service. + +The service continuity procedure is executed similarly in the two solutions + +- Solution #17 describes that the PEMC selects the new PEGC and configures the new PEGC to support service continuity by providing information about the PINE and Service details. The PEMC also updates PIN server about the status of the service continuity procedure including the PINE and PEGC information. +- Solution #15 describes that the PEMC discovers a PEGC and configures it for service continuity. The configuration step includes providing access control information and exchanging profile information among PEGC. The PEMC also configures PINE if required. +- Solution #15 also covers the scenario where the PINE moves out of range of the PIN and the service will need to be provided via the 5GS. In this scenario, the PEGC notifies the PEMC and the PEMC notifies the PIN Server about the need for service continuity. The PIN Server is then able to configure QoS for the flows that are associated with the service. The PIN Server will then provide the updated route information to the PEGC. + +The solutions propose role assignments for PINE, PEGC, PEMC and PIN server for service continuity procedures considering certain impact to the application layer itself. These roles may require further modification or enhancement considering PINE status and application scenarios. + +### 9.2.7 Evaluation of key issue #6: PEMC/PEGC replacement in PIN + +This clause provides an overall evaluation for Key Issue #6, "PEMC/PEGC replacement in PIN". + +Various procedures documented as part of Solution #2 in the clause 7.3.2.3 addresses the aspects of Key Issue #6. + +Key Issue #6 studies the following open issues: + +- a) Whether and how the need for PEMC or PEGC role change is determined? + - b) How another active PIN element take over the role or is assigned the role of PEMC or PEGC? + - c) Whether and how the existing active PIN elements is notified about the role change? + - d) Whether and how the required dynamic or context information of PIN is made available to the new element taking the role of PEMC or PEGC +- Procedures documented as part of the clause 7.3.2.3 considers the PIN modification as means to assign the role of PEMC and PEGC to another PINE. The need of the role change could be because of the current PIN element assigned with the role of PEGC or PEMC is no more available or the duration associated with the role is expired. + - Role change is achieved based on the following principles: + - a) The current PEMC or PEGC triggering the role change to another PINE by requesting PIN server – Clause 7.3.2.3.1 describes the procedure for PEMC role change which is triggered by the current PEMC requesting the PIN server to assign the PEMC role to another PINE. As part of the request PEMC may include the list of potential candidate(s). Clause 7.3.2.3.6 describes the procedure for PEGC role change which is triggered by the current PEGC to assign the PEGC role to another PINE. Solution 9 describes the procedure for PEGC role change which is triggered by the PEMC on detecting the unavailability of PEGC. On detecting the unavailability of PEGC, PEMC requests the PIN server to assign the PEGC role to another PIN element which has the gateway capability. + - b) Role change triggered by the PIN server – Clause 7.3.2.3.2 describes the PEGC role change procedure by the PIN server on detecting the unavailability of the PIN element which is currently the PEGC. Clause 7.3.2.3.3 describes the PEMC role change procedure by the PIN server on detecting the unavailability of the PIN element which is currently the PEMC. + - c) Role change triggered internally within the PIN without involving PIN server - Clause 7.3.2.3.4 describes the procedure of how the current PEMC requesting another PIN element to take the role of PEMC. Once the role assignment succeeds, the PIN server, PEGC and other PIN elements are notified of the role change. Clause 7.3.2.3.5 describes the procedure of how the PEMC requesting another PIN element to take the role of PEGC. In this case the decision of role change is determined and executed by the PEMC and PIN server and other PIN elements are notified of the role change. Clause 7.3.2.3.8 describes the procedure where multiple PEGCs serve two groups of PINEs in a PIN and upon the failure of one of the PEGCs, a backup PEGC assumes the role of the new PEGC. + - d) PEMC Role change triggered by authorized administrator residing outside the PIN – Clause 7.3.2.3.7 describes the procedure of how the authorized administrator on a UE requests the PIN server through the 5G network to modify the role of PEMC to another PIN element. The authorized administrator on a UE receives the notification from PEGC about the failure/unavailability of current PEMC. + - e) Role change notification to the PIN entities – In all the procedures related to the role change in the PIN, the corresponding PIN entities (PIN server, PEMC, PEGC and PIN elements) are notified about the role change and the PIN dynamic profile information maintained at these entities are updated accordingly. + +### 9.2.8 Evaluation of PINAPP architecture + +The solutions 1 addresses the key issue related to PINAPP architecture, to support the PIN management and the PIN communication. Also, in the PINAPP architecture supports the service switch, application server discovery and service continuity. + +# --- 10 Conclusions + +*This clause provides conclusions of the study.* + +## 10.1 Conclusion of PIN management of KI#1 + +The following principle is considered normative for PIN create: + +- The PIN creation can only be triggered by the PEMC. The PINE receives the role of PEMC first during the registration procedure towards PIN server. +- The PEMC sends the PIN create request to PIN server with the GPSI, PIN client ID, UE location, security credential and PIN profile. In order to save the procedure of several PEMCs to be involved into the certain PIN as individual PEMC, the PEMC can have the additional PEMC GPSIs/PIN client ID in the PIN create request, to indicate additional PEMCs that are allowed to manage the PIN. In order to save the procedure of several PINEs to be involved into the certain PIN, the PEMC can have the lists of PINEs GPSIs/PIN client ID in the PIN create request, to indicate additional PINEs that are allowed to join the PIN. +- The PIN server sends a successful response to PEMC, which includes a newly assigned PIN ID to indicate the PIN. Also, the PIN lifetime or duration can be indicated to PEMC. If the PIN creation request fails, the PIN server should give the failure response to indicates that indicates the cause of PIN creation request failure. +- After the PIN create successfully, the PIN server or PEMC can allocate the access control information to PEGC if the gateway is selected for the PIN and delivers the access control information to PINEs. The access control information includes: user name, account, SSID, BSSID and etc. All the information is used by PINE in PIN to access the PEGC or benefited by 5GS communication. + +**Editor's note: Whether Access control information is determined by 5GC or PIN server itself depends on SA2 feedback and needs further update.** + +The following principles are considered normative for PIN delete: + +- The PIN delete procedure can be triggered either by PEMC or PIN server. +- The PEMC sends a PIN delete request to the PIN server to request to delete the PIN. +- The PEMC can decide to delete the PIN locally. After PIN deleted locally, the PEMC indicates the deletion of PIN to PIN server which includes the PIN ID. +- The PIN server deletes the PIN when events occur and satisfies trigger conditions for PIN delete. For example, the event includes the life cycle of a PIN is end or the PIN server decides to not provide any PIN resource in this PIN. + +The PIN delete request includes the security credentials of the PIN client received during PIN client authorization procedure and PIN ID. The PIN ID indicates this PIN will be deleted. + +The PEMC can delete the PIN locally based on some pre-configuration information on PEMC, for example, the according to the life time configured on PEMC. + +If a PIN is deleted, the PIN resource will be released and the PIN service will be stopped. Some of the procedure related to the deleted PIN should be normative: + +- After PIN delete, the PEMC sends the notification to PEGC and PINE to delete the PIN profile related to the deleted PIN. +- The access control information in PEGC that related to this PIN and PINE in this PIN should be deactivated. + +- If PIN is deleted by PEMC locally, the PEMC sends a PIN status update notification to the PIN server to indicate the PIN has been deleted. In this notification, the PIN ID is included. The PIN server updates the PIN profile to remove the details of this PIN which represented by PIN ID. +- If the PIN is deleted by the PIN server, the PIN server sends the PIN status update notification to the PEMC to indicate the PIN has been deleted. In this notification, the PIN ID is included. The PEMC updates the PIN profile to remove the details of this PIN which represented by PIN ID and triggers other notification towards the PINE/PEGC in this PIN. + +NOTE: The interaction between PINE and PEMC may be directly interaction or interaction via PEGC. + +The following principle is considered normative for PIN server discovery: + +The general static configuration of PIN server in PIN can be consumed as the following methods: + +- pre-configured in the PIN elements or PIN clients; +- configured by the user; +- derived from HPLMN identifier for non-roaming scenario or from VPLMN identifier for roaming scenario. + +The dynamic discovery of PIN server in PIN can be consumed as the following methods. If the PINE has the application layer connection to PEGC or PEMC: + +- If the PINE connects to PEGC with user name and password, the PINE sends PIN server discovery request to PEGC. The PEGC can response with PIN server end point address directly. +- If the PINE has the open access to PEGC, the PINE sends PIN server discovery request to PEGC and the PEGC routes the requests to PEMC. The PEMC can response with PIN server end point address to PINE via PEGC. Authorization information and procedure is needed between PEMC and PINE. +- If the PINE has the application interaction towards the PEMC, the PINE sends PIN server discovery request to PEMC. The PEMC delivers the PIN server end point information to PIN elements or PIN client. + +In the PIN server discovery request, the following parameters are included: GPSI, PIN client ID if has, UE location. And in the PIN server discovery response, the endpoint address information of PIN server is included, for example, the IP address, FQDN, or URI. + +NOTE: The PEGC is responsible for response the PIN server address to PINE directly or route the PIN server request to PEMC. If the PEGC is associated with multiple PIN and PEMC, the PEGC route the PIN server request to multiple PEMC separately. + +The following principle is considered normative for PIN discovery: + +- The PINE can discover the available PIN from two methods: + - The PINE can send PIN discovery request to PEMC of a PIN. + - The PINE can send PIN discovery request to PIN server. +- If the PINE has already had an application layer connection with a PEMC which manages a PIN, the PINE sends the PIN discovery request to PEMC. +- If the PINE has already had the application layer connection towards PEGC, and the PINE has already received the PIN server endpoint address, the PINE sends the PIN discovery request to PIN server. + +The PIN discovery request includes the security credentials of the UE or PIN client and may include the UE identifier such as GPSI if available, UE location, the service that PINE wants to consume and PIN client profile(s) information. + +In the PIN discovery request to both PEMC or PIN server, the PINE can have the filter information in the PIN discovery request for example, the interesting area, the interesting type of PIN and etc. The filter information can be used for providing certain PIN information. + +The following principle is considered normative for PINE/PEMC/PEGC registration: + +- For the PEMC, the PEMC sends Registration Request (GPSI) to the PIN server. After successful registration in PIN server, the PIN server allocates the PIN client ID to this PEMC and the PEMC receives the role of PEMC. + +- For the PINE and PEGC, the PEMC substitutes the PINE/PEGC to register on PIN server with the device metadata from PINE/PEGC (MAC address, vendor name, device description, PINE/PEGC Address). After successful registration in PIN server, the PIN server allocates the PIN client ID to PINE/PEGC. +- The PINE can also directly register to the PIN server via the PEGC, if the PEMC/PIN server has already provided the PIN server address to the PINE. And if the PINE is accessing the PEGC without any registration and authorization, the PEGC may reject the message from the PINE and request the PINE to perform the registration. + +For managing the PIN, it is required to maintain the information related to the PIN and PIN elements. Information captured as part of Solution 6 can serve as basis for the normative work and further information if any required can be decided during the normative work. + +The following principle is considered normative for adding/removing PINE into/from a PIN: + +For PINE joins into a PIN: + +- The PINE sends the request to PEMC to join the PIN. The request includes the security credentials of the PIN client, UE identifier such as GPSI, UE location, PIN ID and some of PIN client profile(s). After PEMC authorizes the request and accept the PINE to join the PIN, the PEMC notifies to PEGC/PIN server in PIN. The PEMC/PEGC/PIN server updates the PIN profile. The access control information in PEGC for this PINE is delivered by PEMC during the notification. +- During PIN create procedure, the PEMC can request to create a PIN including the potential PIN elements to be added into a PIN. +- The PINE sends PIN join/discovery request to the PEGC. The PEGC identifies the received message is the PIN join/discovery request, and the if the PINE is not registered and authorized due to no PIN client ID and credentials in the message, the PINE registration procedure will be also included. + +For removing PINE from a PIN, two potential ways: + +- The PEMC removes a PINE from PIN, and notify the result to PEGC/PIN server. The PEMC/PEGC/PIN server updates the PIN profile. The access control information in PEGC for this PINE is disabled after receiving the notification from PEMC. +- If the PINE decides to leave the PIN, the PINE sends the request to PEMC to leave the PIN. The request includes the security credentials of the PIN client, UE identifier such as GPSI, UE location, PIN ID and PIN client profile(s). After PEMC authorizes the request and accept the PINE to leave the PIN, the PEMC notifies to PEGC/PIN server in PIN. The PEMC/PEGC/PIN server updates the PIN profile. The access control information in PEGC for this PINE is disabled after receiving the notification from PEMC. + +Optionally, the PIN server can also be involved in the procedure of PINE added/removed into/from PIN. The PIN server can decide the PINE added/removed into/from PIN or the PIN server can be notified by the result of PINE added/removed into/from PIN. + +The following principle is considered normative for credential provisioning: + +- The PINE sends Credential Provisioning Request (PIN ID, PINE ID, Duration) to the PEGC. +- The PEGC sends the Credential Provisioning Request to the PEMC directly, or sends PEMC Notification (PEGC ID, Credential Provisioning Request) to PIN server and PIN server sends PEMC Event Notification (PEGC ID, Credential Provisioning Request) to the PEMC. +- The PEMC/PEGC sends Credentials Provisioning Response (Credentials) to PINE. + +## 10.2 Conclusion of KI#2 + +The following principle is considered normative for KI#2: + +- There are two methods to enable the PIN with 5GS communication: + +- Establish QoS for PINE with AF support. +- PEGC triggers PDU session establishment/modification for PINE when no PIN server deployed. + +For the AF related procedure, the AF trigger the QoS create/modification procedure with parameters of Packet filters, DN specific ID, to request the 5GS to arrange resource for PIN. + +For PEGC related procedure, the PEGC sends PIN Communication Request to the PEMC. The PEMC sends Create/Update/Remove Communication Request (PIN ID, Packet filters, requested QoS) to the PEGC. The PEGC configures the local rule accordingly, or according to the Packet filters, the PEGC may initiate PDU Session Modification with the Packet filters and requested QoS towards 5G system in order to make 5GC configure the N4 rules for UPF(s). + +The PIN Communication Request includes the following parameters: PIN ID, MAC address/IP address, Traffic descriptors. The Create/Update/Remove Communication Request includes PIN ID, Packet filters, requested QoS. + +During the QoS or PDU session establishment procedure, if the IP address of the PEMC/PEGC is changed, the PEMC/PEGC sends Event Notification (PEMC/PEGC ID, old IP address, new IP address) to the PIN server. + +## 10.3 Conclusion of Service Switch of KI#3 + +There are two solutions that solution 8 and solution 10 for service switch should be normative with the following principle: + +The Solution 10 is service switch accomplished internal PIN. The following principle is considered normative for Solution 10: + +- The PINE joins into a PIN and discovers the candidate PINE internal PIN to do the service switch. The candidates PINE should deploy the same application client or can maintains the service towards AS and the service corresponds to the same service type. +- After the traffic terminated at the PINE, the PINE offloads the traffic to candidate PINE directly or via PEGC if direct communication is not viable. + +The Solution 8 is service switch with support from PIN server. The following principle is considered normative for Solution 8: + +- The PINE discovers a PIN and decide a potential candidate PINE to be the target of service switch with the help of PIN server. +- And the PIN server requests the PEMC to configure PEGC, PINE, as well as informs AS to trigger another new application layer traffic to candidate PINE/AS. +- And after the new application layer is established, that some of the application client context relocation may needed between two clients. + +## 10.4 Conclusion of KI#4 + +Solution 11 reflects the KI#4. The following principle is considered normative for KI#4: + +- The application server registers into AS registry function (can be deployed in PEMC, PIN server) with the endpoint information. The AS registry function can store the information about AS for PINE to discover the appropriate AS. +- The PINE triggers the application server discovery request to the AS registry function in PEMC, which can be forwarded to the registry function in PIN server, and receives the endpoint address of AS +- Application clients in the PIN can register with the Registry function, through PIN client using the registry information, obtained by the PIN client from PIN server. + +## 10.5 Conclusion of KI#5: Service continuity + +In order to support the service continuity scenarios of Key Issue #5, the principles of Solution #15 and Solution #17 will be followed where the PEMC detects that a service continuity procedure is needed, selects a new PEGC to handle the service, configures the PEGC to handle the service, and can notify the PIN Server about the service continuity procedure. The PEMC detects that a service continuity procedure is needed based on a notification from a PEGC or, in the case of a service that is using direct PINE-to-PINE communication, a notification from a PINE. + +The principles of Solution #15 will be followed to cover the scenario where the PINE moves out of range of the PIN and the service will need to be provided via the 5GS. The PEGC notifies the PEMC and the PEMC notifies the PIN Server about the need for service continuity. The PIN Server is then able to configure QoS for the flows that are associated with the service. The PIN Server will then provide the updated route information to the PEGC. + +The service continuity role assignments for PINE, PEGC, PEMC and PIN server can be further modified or enhanced in the normative work considering different PINE status and applications scenarios. + +## 10.6 Conclusion of KI#6 + +The Key Issue #6, "PEMC/PEGC replacement in PIN" studied the open issues related to the PIN modification which is about the re-assignment of PEMC and PEGC role to another PIN element. Various procedures documented as part of Solution #2 in the clause 7.3.2.3 addresses the aspects of Key Issue #6. + +Following methods are considered for the normative work related to PEMC role change: + +1. Current PEMC requesting the PIN server to assign the PEMC role to another PIN element (clause 7.3.2.3.1). +2. PIN server assigning the PEMC role to another PIN element on detecting the unavailability of current PEMC (clause 7.3.2.3.3). +3. Current PEMC requesting another PIN element to take the role of PEMC (clause 7.3.2.3.4). +4. Authorized user from outside PIN requesting PIN server to assign to PEMC role another PIN element (clause 7.3.2.3.7) + +All the above methods require the consent from the new PIN element to be assigned with the role of PEMC. All other PIN elements including PEGC are to be notified about the change in the PEMC role and the PIN dynamic profile information is updated accordingly. + +Following methods are considered for the normative work related to PEGC role change: + +1. PIN server assigning the PEGC role to another PIN element on detecting the unavailability of current PEGC (clause 7.3.2.3.2). +2. PEMC assigning the PEGC role to another PIN element on detecting the unavailability of current PEGC (clause 7.3.2.3.5). +3. Current PEGC requesting the PIN server to assign the role to another PIN element (clause 7.3.2.3.6, clause 7.3.2.3.8) + +All the above methods require the consent from the new PIN element to be assigned with the role of PEGC. All other PIN elements including PEMC are to be notified about the change in the PEGC role and the PIN dynamic profile information is updated accordingly. + +## 10.7 Conclusion of PINAPP architecture + +It is supposed to use Solution 1 as baseline for normative PINAPP architecture. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA6#47-e | | | | | TS skeleton (version 0.0.0) approved in S6-220374<br>Implementation of the following pCRs approved by SA6:<br>S6-220375, S6-220376, S6-220475, S6-220476 | 0.1.0 | +| 2022-04 | SA6#48-e | | | | | Implementation of the following pCRs approved by SA6:<br>S6-220805, S6-220851, S6-220973, S6-220974 | 0.2.0 | +| 2022-05 | SA6#49-e | | | | | Implementation of the following pCRs approved by SA6:<br>S6-221475, S6-221476, S6-221477, S6-221478, S6-221336, S6-221479, S6-221480, S6-221163, S6-221361, S6-221481. | 0.3.0 | +| 2022-07 | SA6#49-bis-e | | | | | Implementation of the following pCRs approved by SA6:<br>S6-221549, S6-221571, S6-221615, S6-221788, S6-221804, S6-221806, S6-221807, S6-221808, S6-221826, S6-221828, S6-221831, S6-221834, S6-221867, S6-221895, S6-221900, S6-221993, S6-221994. | 0.4.0 | +| 2022-08 | SA6#50-e | | | | | Implementation of the following pCRs approved by SA6:<br>S6-222172, S6-222389, S6-222402, S6-222409, S6-222410, S6-222411, S6-222418, S6-222536, S6-222566, S6-222567, S6-222568, S6-222569, S6-222570. | 0.5.0 | +| 2022-10 | SA6#51-e | | | | | Implementation of the following pCRs approved by SA6:<br>S6-222651, S6-222746, S6-222747, S6-222858, S6-222904, S6-222905, S6-222906, S6-222907, S6-222910, S6-222911, S6-222912, S6-222914, S6-222916, S6-222959, S6-222972, S6-222973, S6-223047, S6-223048, S6-223049 | 0.6.0 | +| 2022-11 | SA6#51-e | | | | | Reimplementation of S6-222912 and editorial corrections | 0.6.1 | +| 2022-11 | SA6#52 | | | | | Implementation of the following pCRs approved by SA6:<br>S6-222651, S6-223170, S6-223172, S6-223186, S6-223191, S6-223265, S6-223362, S6-223370, S6-223384, S6-223385, S6-223524, S6-223525, S6-223526, S6-223527, S6-223528, S6-223529, S6-223530, S6-223533, S6-223535, S6-223550, S6-223577, S6-223578, S6-223593, S6-223594. | 0.7.0 | +| 2022-11 | SA6#52 | | | | | Correction of the implementation of pCR S6-223577 | 0.7.1 | +| 2022-12 | SA#98-e | SP-221219 | | | | Submitted for Approval at SA#98-e | 1.0.0 | +| 2022-12 | SA#98-e | SP-221219 | | | | MCC Editorial update for publication after TSG SA approval (SA#98-e) | 18.0.0 | +| 2023-03 | SA#99 | SP-230280 | 0001 | | B | Conclusion update for additional PEMCs and PINEs in PIN creation | 18.1.0 | +| 2023-03 | SA#99 | SP-230280 | 0002 | | B | Requirement update for PIN | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-79/raw.md b/raw/rel-18/23_series/23700-79/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4f5a21e737b21587b2fc662634e32d104a9e02b5 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/raw.md @@ -0,0 +1,1395 @@ + + +# **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Study of Gateway User Equipment (UE) function for Mission Critical (MC) communications; (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" 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 top. Below the "P" is a red signal wave icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, 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 +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. + +© 2021, 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 ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations ..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Scenarios..... | 7 | +| 4.1 MC gateway UE services and the relationship to MC service users/clients ..... | 7 | +| 4.1.1 General ..... | 7 | +| 5 Key issues ..... | 8 | +| 5.1 Key issue 1 – Functional Architecture for an MC gateway UE..... | 8 | +| 5.2 Key issue 2 – Authorisation for connection of non-3GPP devices with an MC gateway UE ..... | 8 | +| 5.3 Key issue 3 – Identification of MC service users behind an MC gateway UE residing on non-3GPP devices..... | 8 | +| 5.4 Key issue 4 – MBMS support ..... | 9 | +| 5.5 Key issue 5 – User traffic handling..... | 9 | +| 5.6 Key issue 6 – Use of multiple MC gateway UEs..... | 10 | +| 6 Architectural requirements..... | 10 | +| 7 Solutions..... | 10 | +| 7.1 Functional architecture..... | 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 ..... | 12 | +| 7.1.2.3 Media plane..... | 13 | +| 7.1.3 Solution evaluation ..... | 14 | +| 7.2 Connection authorisation with the MC gateway UE..... | 14 | +| 7.2.1 General ..... | 14 | +| 7.2.2 Information flows ..... | 14 | +| 7.2.2.1 Connection authorization request ..... | 14 | +| 7.2.2.2 Connection authorization response..... | 15 | +| 7.2.3 MC service UE configuration data ..... | 15 | +| 7.2.4 Initial MC gateway UE configuration data ..... | 15 | +| 7.2.5 Procedure..... | 16 | +| 7.2.6 Solution evaluation ..... | 17 | +| 7.3 Connection authorisation with an MC server via an MC gateway UE ..... | 17 | +| 7.3.1 General ..... | 17 | +| 7.3.2 Information flows ..... | 17 | +| 7.3.2.1 Connection authorization request ..... | 17 | +| 7.3.2.2 Connection authorization response..... | 18 | +| 7.3.3 MC server configuration data ..... | 18 | +| 7.3.4 Initial MC gateway UE configuration data ..... | 18 | +| 7.3.5 Procedure..... | 19 | +| 7.3.6 Solution evaluation..... | 20 | +| 7.4 Using IMS identities behind the MC gateway UE..... | 20 | +| 7.4.1 General ..... | 20 | +| 7.4.2 Solution description..... | 20 | +| 7.4.3 Solution evaluation ..... | 22 | +| 7.5 Connection authorisation for non-3GPP devices that do not host an MC client..... | 22 | +| 7.5.1 General ..... | 22 | + +| | | | +|------------------------|-------------------------------------------------------------------|----| +| 7.5.2 | Information flows ..... | 23 | +| 7.5.2.1 | Connection authorization request ..... | 23 | +| 7.5.2.2 | Connection authorization response ..... | 23 | +| 7.5.3 | MC server configuration data ..... | 23 | +| 7.5.4 | Initial MC gateway UE configuration data ..... | 23 | +| 7.5.6 | Solution evaluation ..... | 25 | +| 7.6 | 3GPP access network related location information management ..... | 25 | +| 7.6.1 | General ..... | 25 | +| 7.6.2 | Information flows ..... | 25 | +| 7.6.2.1 | MC GW Location reporting configuration ..... | 25 | +| 7.6.2.2 | MC GW Location information report ..... | 25 | +| 7.6.2.3 | MC GW Location information request ..... | 26 | +| 7.6.3 | Procedure ..... | 26 | +| 7.6.3.1 | Event-triggered location reporting procedure ..... | 26 | +| 7.6.4.2 | On-demand location reporting procedure ..... | 27 | +| 7.6.5.3 | Location reporting cancel procedure ..... | 28 | +| 7.6.4 | Solution evaluation ..... | 29 | +| 7.7 | Routing of data and signalling by the MC gateway UE ..... | 29 | +| 7.7.1 | General ..... | 29 | +| 7.7.2 | MC client uses the IP address from the MC gateway UE ..... | 29 | +| 7.7.3 | MC client uses an own IP address ..... | 30 | +| 7.7.4 | Solution evaluation ..... | 30 | +| 7.8 | MBMS Support for MC clients residing on non-3GPP devices ..... | 31 | +| 7.8.1 | General ..... | 31 | +| 7.8.2 | Information flows ..... | 31 | +| 7.8.2.1 | MC GW MBMS bearer announcement ..... | 31 | +| 7.8.2.2 | MC GW MBMS listening status report ..... | 31 | +| 7.8.2.3 | MC GW MapGroupToBearer request ..... | 32 | +| 7.8.2.4 | MC GW MapGroupToBearer response ..... | 32 | +| 7.8.2.5 | MC GW MBMS bearer quality report ..... | 32 | +| 7.8.2.6 | MC GW MBMS bearer suspension indication ..... | 33 | +| 7.8.3 | Procedure ..... | 33 | +| 7.8.3.1 | MBMS bearer announcement handling procedure ..... | 33 | +| 7.8.3.2 | Procedure for handling MapGroupToBearer message ..... | 34 | +| 7.8.3.3 | Procedure for MBMS bearer suspension notification ..... | 36 | +| 7.8.3.4 | Procedure for reporting MBMS bearer quality ..... | 36 | +| 7.8.4 | Solution Evaluation ..... | 37 | +| 8 | Overall evaluation ..... | 37 | +| 8.1 | Key issue and solution evaluation ..... | 37 | +| 8.1.1 | Introduction ..... | 37 | +| 8.1.2 | Results ..... | 38 | +| 9 | Conclusions ..... | 38 | +| Annex A (informative): | Gateway UE requirements ..... | 40 | +| A.1 | Shareable McPTT UEs and gateway UEs ..... | 40 | +| A.2 | Gateway requirements ..... | 40 | +| Annex B (informative): | Change history ..... | 41 | + +# --- Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> 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 + +An MC gateway UE has the functionality of providing service access with the MC service system for multiple MC service clients. The MC gateway UE enables MC service access for those MC service clients operating on devices that have no MC service capabilities (incl. 3GPP transport). This technical report identifies the key issues and corresponding solutions with recommendations for the normative work. + +# --- 1 Scope + +The present document studies solutions to satisfy the requirements for a Gateway UE function. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical communications. Requirements for this study are taken from stage 1 requirements, including 3GPP TS 22.179 [2] and 3GPP TS 22.280 [3]. + +# --- 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.179: "Mission Critical Push to Talk (MCPTT); Stage 1". +- [3] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)". +- [4] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [5] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [6] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [7] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". +- [8] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [9] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [10] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". +- [11] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes". + +# --- 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]. + +**MC gateway UE:** A UE that can be simultaneously shared between multiple MC service clients using the same or different MC services. + +**MC client:** A client that represents a set of clients (i.e. Group management client, Configuration management client, Identity management client, Key management client, Location management client and MC service client). + +**MC server:** A server that represents a set of servers (i.e. MC service server and servers of the Common services core). + +**Non-3GPP device:** A device that enables local connectivity towards an MC gateway UE using an access method not specified by 3GPP. A subset of these devices can host an MC client specified by 3GPP. + +**CSC client:** A client that represents a set of clients for group management, configuration management, identity management, key management, and location management. + +**CSC server:** A server that represents a set of servers for group management, configuration management, identity management, key management, and location management. + +**MC gateway client:** A client on a non-3GPP device that requests connection authorisation with an MC gateway UE server. + +**MC gateway UE server:** A server on an MC gateway UE that controls connection authorisation received from an MC gateway client. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +<symbol>      <Explanation> + +## 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]. + +<ABBREVIATION>      <Expansion> + +# --- 4 Scenarios + +## 4.1 MC gateway UE services and the relationship to MC service users/clients + +### 4.1.1 General + +The MC gateway UE service may provide the following necessary functions: + +- Allowing an MC service client to connect to a MC gateway UE. +- Allowing an MC service client to choose between multiple MC GW UEs for the required MC service capability. +- Support of MC service continuation while the MC service client changes the MC gateway UE association. +- Ensure that the content of communications between the MC system and MC service client connected to an MC gateway UE is unaltered. +- Ensure that the communication traffic attributes, e.g. priority and QoS, of an MC service client connected to an MC gateway UE remains independent from other MC service clients concurrently connected to the same MC gateway UE. +- Independent MC service client identification, authorisation and service profile association using the gateway MC UE functionality. +- Sharing of an MC gateway UE transport resources with multiple connected MC service clients. + +- Indication of potential MC gateway UE anomalies sent towards the connected MC service clients. +- MC service client is serving an MC service user on a device which is connected to the MC gateway UE via non-3GPP transport. + +# --- 5 Key issues + +## 5.1 Key issue 1 – Functional Architecture for an MC gateway UE + +The MC gateway UE may provide several sub-functions like an MC gateway UE user device connecting function, an MC gateway UE network function, an MC gateway UE user QoS handling function, an MC gateway UE exposure function, an MC gateway UE MBMS support function and other functions. + +A functional architecture for the MC gateway UE may help to develop proper mechanisms and procedures. + +List of key issues: + +- Clarify the need to define a functional architecture for the MC gateway UE. +- Describe the overall functional architecture and the details of the single elements from that architecture. + +## 5.2 Key issue 2 – Authorisation for connection of non-3GPP devices with an MC gateway UE + +A control mechanism for connecting non-3GPP devices with an MC gateway UE is needed as not all devices should be connected with all MC gateway UEs. An authorized usage of an MC gateway UE by clients and users is needed as well as a control mechanism on how many MC gateway UEs can be used by the same MC service user/client. If a connection related temporary identifier and an explicit login procedure is required (e.g. for traffic routing) needs to be clarified. + +List of key issues: + +- Clarify how to authorize the use of non-3GPP devices by the MC gateway UE. +- Clarify how to control MC service user/client use of multiple MC gateway UEs and to control the related traffic aggregation. +- Clarify whether there is a need for an explicit login procedure and assignment of a connection related temporary non-3GPP device ID. + +## 5.3 Key issue 3 – Identification of MC service users behind an MC gateway UE residing on non-3GPP devices + +The mission critical user identity (or MC ID) is the identity that an MC service user presents to the identity management server during a user authentication transaction (not necessarily tied to a single mission critical service). + +The MC service user identity (or MC service ID) is used as a globally unique identifier within the MC service that identifies an MC service user. + +The MC ID and the MC service ID may be the same. + +The SIP signalling control plane uses a private user identity to authenticate the signalling user agent and one or more public user identities for routing of signalling messages in the SIP core. + +There are several relationships between the MC service ID(s) and the public user identity(ies). + +List of key issues: + +- Clarify whether the MC ID can be used on non-3GPP devices connected to the MC system via an MC gateway UE. Identify impacts to existing authentication procedures. +- Clarify whether the MC service ID can be used on non-3GPP devices connected to the MC system via an MC gateway UE. Identify impacts or limitations on existing procedures in the application plane. +- Elaborate how and if SIP signalling plane identities can be used by non-3GPP devices connected to the MC system via an MC gateway UE. +- Elaborate the impacts regarding the current relationships between SIP signalling plane identities and application plane identities. +- Investigate whether there is a need for additional application plane identities to support non-3GPP devices connected to network via an MC gateway UE. + +## 5.4 Key issue 4 – MBMS support + +If non-3GPP devices are connected to the MC system via an MC gateway UE, then MBMS support should be supported. MBMS support is required for both, MC service clients residing on a UE acting as MC gateway UE and for MC service clients residing on a non-3GPP device. + +List of key issues: + +- Clarify how MBMS transmissions can be supported for MC service clients operating on non-3GPP devices via an MC gateway UE. +- Clarify whether there are any implications on switching between unicast and multicast. +- Clarify how the MC gateway UE forwards the MBMS downlink traffic to the corresponding MC service clients behind the MC gateway UE. +- Clarify whether the MBMS support for MC service client residing on a non-3GPP devices should be transparent for network, i.e. the network need not consider whether the MC service client residing on a non- 3GPP device is connected via an MC gateway UE or not while using MBMS bearers, to minimize the impact on the existing MC system. + +## 5.5 Key issue 5 – User traffic handling + +User data traffic and signalling information needs to be routed to/from user/clients residing on non-3GPP devices. The MC gateway UE needs to deal with multiple non-3GPP devices on one side and with multiple bearers (LTE) and 5G QFIs on the network side. The communication content should be unchanged, E2E encryption should be supported. + +List of key issues: + +- Clarify how the MC gateway UE routes and maps the traffic data and signalling information between non-3GPP devices and the network. +- Clarify whether there are any limitations in the MC gateway UE network connectivity aspects like max. number of PDU sessions, max. QFIs per PDU session etc. +- Elaborate how independent QoS and priority treatment of each communication per MC service client is enabled for a MC service user behind an MC gateway UE. +- Clarify how the content of a MC service user/client communication beyond an MC gateway UE remains unchanged. +- Clarify how end-to-end encryption (E2EE) is enabled for MC service users/clients residing on non-3GPP devices. + +## 5.6 Key issue 6 – Use of multiple MC gateway UEs + +An MC service client can use multiple MC gateway UEs that are bound to the same MC system while using the associated MC service per gateway. Potential impacts to the functional architecture and/or the MC service client capabilities are to be studied to develop proper mechanisms and procedures. + +List of key issues: + +- Clarify the potential impact to the MC service client capabilities when using multiple MC gateway UEs. +- Clarify the potential impact to the MC gateway UE capabilities in a multi MC gateway UE environment. +- Describe the functional architecture supporting more than one MC gateway UE, as extension of the single MC gateway UE functional architecture. + +## 5.7 Key issue 7 – 3GPP access network related location management by MC Clients + +Location management server may not be aware whether the MC service clients are residing on 3GPP devices or non 3GPP-devices when providing the location reporting configuration and when requesting the location information from the location management client. The MC clients residing on the non-3GPP devices may get the Location reporting configuration containing the trigger criteria related to 3GPP access network related location parameters. There may be some issues if the MC clients detects that it cannot handle the location reporting trigger criteria related to the 3GPP access network information or if it cannot provide the requested location information related to the 3GPP access network. + +List of key issues: + +- Whether and how the 3GPP access network related location trigger criteria are handled +- Clarify how the 3GPP access network related location information of MC service clients residing on non-3GPP devices is known to the MC system when required. + +# --- 6 Architectural requirements + +NOTE: No architectural requirements were identified. + +# --- 7 Solutions + +## 7.1 Functional architecture + +### 7.1.1 General + +This solution addresses the key issue 1 described in clause 5.1 on defining a functional architecture when using an MC gateway UE. + +### 7.1.2 Solution description + +#### 7.1.2.1 Functional architecture + +The MC gateway UE offers access to the MC server for several MC clients (see Figure 7.1.2-1). The MC clients can be either located in the MC gateway UE or in non-3GPP devices connected to the MC gateway UE via non-3GPP access. + +For non-3GPP devices which can host an MC client, the MC gateway UE enables connectivity to the MC server. For non-3GPP devices which cannot host the MC client, the MC gateway UE hosts the instantiation of the MC client for the non-3GPP device. + +![Figure 7.1.2.1-1: Functional architecture diagram showing three types of non-3GPP devices connected to an MC gateway UE, which is then connected to an MC server via 3GPP access.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates the functional architecture for MC services. On the left, three types of non-3GPP devices are shown: + + +- A device that can host MC clients, containing one MC client. +- A device that can host MC clients, containing two MC clients. +- A device that cannot host MC clients. + + All three devices connect to a central 'non-3GPP access' block. This block connects to an 'MC gateway UE (using MC service capabilities)'. Inside this gateway UE, for the device that cannot host MC clients, an MC client is instantiated. The MC gateway UE then connects to a '3GPP access' block, which finally connects to an 'MC server' on the far right. + +Figure 7.1.2.1-1: Functional architecture diagram showing three types of non-3GPP devices connected to an MC gateway UE, which is then connected to an MC server via 3GPP access. + +**Figure 7.1.2.1-1: Functional architecture** + +The MC gateway UE provides MC service capabilities and 3GPP access capabilities using 3GPP network credentials for authorized access with an MC server. + +For non-3GPP devices which cannot host MC clients, the MC gateway UE shall control the access and manage the communication between the non-3GPP devices and the MC server. Upon reception of connection authorisation request from a non-3GPP device, the MC gateway UE instantiates an MC client, acting on behalf of the non-3GPP device, to provide the requested services (e.g. emergency call, group calls, short data messages services, etc.). The communication interworking and the definition of associated procedures between the MC client (initiated at the MC gateway UE) and the non-3GPP devices is out of scope of this document. + +NOTE 1: MC clients residing on a non-3GPP device cannot use UICC credentials to perform authorisation with the 3GPP transport system. + +For MC clients getting MC service access via the MC gateway UE, the MC gateway UE forwards (unmodified) signalling and media from the individual MC clients to the MC server and vice versa. + +If the MC service user on the non-3GPP device utilizes multiple MC services simultaneously, the MC service access may also be provided by one or multiple MC gateway UEs (see figure 7.1.2.1-2) while restricting each MC service to one MC gateway UE (e.g. MCPTT via MC gateway UE1, MCData via MC gateway UE2). + +![Diagram showing simultaneous multiple MC gateway UE use by a single non-3GPP device.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the network architecture for simultaneous multiple MC gateway UE use by a single non-3GPP device. It is divided into three vertical sections by dashed lines: 'non-3GPP device (can host MC clients)' on the left, 'non-3GPP access' in the middle, and '3GPP access' on the right. On the left, a box contains two circles representing MC clients: 'MC client (e.g. MCPTT client)' and 'MC client (e.g. MCData client)'. Horizontal lines connect each client to a corresponding 'MC gateway UE' in the middle section. The top gateway is 'MC gateway UE1 (using MC service capabilities)' and the bottom is 'MC gateway UE2 (using MC service capabilities)'. From each gateway, a horizontal line extends through the '3GPP access' section to an 'MC server' on the far right. The top server is 'MC server (e.g. MCPTT server)' and the bottom is 'MC server (e.g. MCData server)'. + +Diagram showing simultaneous multiple MC gateway UE use by a single non-3GPP device. + +**Figure 7.1.2.1-2: Simultaneous multiple MC gateway UE use by a single non-3GPP device** + +NOTE 2: Even not shown in the above figure, the same principle of simultaneous use of multiple MC gateway UEs is applied for non-3GPP devices which cannot host an MC client. + +#### 7.1.2.2 Reference points + +For application level signaling between the MC client on the non-3GPP device and the MC gateway UE a new reference point called CSC-GW is introduced. The MC gateway UE uses existing reference points (CSC-n) toward the MC server. + +![Figure 7.1.2.2-1: Reference points. A diagram showing various MC clients on the left connected to an MC gateway UE in the center, which is then connected to various servers on the right. The clients include MC service client(s), MC gateway client, CSC client, Signalling user agent, and HTTP client. The servers include MC service servers, Common Service Core (containing CSC server), SIP Core, and HTTP proxy. Reference points are labeled on the connections: MCX-n, CSC-GW, CSC-n, SIP-1, and HTTP-1.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the reference points for various MC clients connecting to an MC gateway UE and subsequently to network servers. On the left, a box labeled 'MC client hosted by a non-3GPP device' contains several client types: 'MC service client(s)', 'MC gateway client', 'CSC client', 'Signalling user agent', and 'HTTP client'. These clients connect to a central box labeled 'MC gateway UE', which contains corresponding server-side components: 'MC service client(s)', 'MC gateway UE server', 'CSC client', 'Signalling user agent', and 'HTTP client'. The connections are labeled with reference points: 'MCX-n' for MC service clients, 'CSC-GW' for the MC gateway client, 'CSC-n' for CSC clients, 'SIP-1' for Signalling user agents, and 'HTTP-1' for HTTP clients. The MC gateway UE components then connect to external servers on the right: 'MC service servers' (via MCX-n), 'Common Service Core' (containing a 'CSC server', via CSC-n), 'SIP Core' (via SIP-1), and 'HTTP proxy' (via HTTP-1). + +Figure 7.1.2.2-1: Reference points. A diagram showing various MC clients on the left connected to an MC gateway UE in the center, which is then connected to various servers on the right. The clients include MC service client(s), MC gateway client, CSC client, Signalling user agent, and HTTP client. The servers include MC service servers, Common Service Core (containing CSC server), SIP Core, and HTTP proxy. Reference points are labeled on the connections: MCX-n, CSC-GW, CSC-n, SIP-1, and HTTP-1. + +**Figure 7.1.2.2-1: Reference points** + +The reference points CSC-n belonging to the application plane and the reference points SIP-1 and HTTP-1 belonging to the signaling control plane are used by the MC client on the non-3GPP device towards the MC gateway UE and the MC gateway UE relays the application and control plane signaling further to the MC server. + +CSC-n, SIP-1 and HTTP-1 reference points are specified in 3GPP TS 23.280 [5]. + +The corresponding MCX-n reference points are specified in 3GPP TS 23.379 [6], 3GPP TS 23.281 [7] and 3GPP TS 23.282 [8]. + +The CSC-GW reference point, which exists between the MC gateway client and the MC gateway UE client residing on the non-3GPP device and the MC gateway UE server residing on the MC gateway UE, is used for connection authorisation of non-3GPP devices with an MC gateway UE. For connection authorisation, the connection authorisation request will be forwarded by the MC gateway UE server via the corresponding MC service client residing on the MC gateway UE (see clause 7.3.4). CSC-GW is also used to request the forwarding of the media from the MC gateway UE by the MC client (see figure 7.1.2.3-1) using corresponding identifiers, e.g. TMGI, applicable for multicast/broadcast-based communication. + +For signalling, the MC clients utilize the allocated resources (default bearer for EPS or QoS flow in 5GS) between MC gateway UE and MC server. The MC gateway UE maps the signaling traffic between MC clients and MC server. + +#### 7.1.2.3 Media plane + +On the media plane a communication between the MC client on the non-3GPP device and is distributed both via non-3GPP access and via 3GPP access. Traffic from multiple MC clients may be transferred on the 3GPP access branch, depending on how many MC clients are served by the MC gateway UE. For that, the MC gateway UE has a media + +distribution function to relay the traffic on the non-3GPP access and the 3GPP access branch for unicast and multicast communications and multiple MC clients properly. + +![Figure 7.1.2.3-1: Media plane diagram showing the flow of unicast and multicast traffic from an MC client on a non-3GPP device through a CSC-GW and an MC gateway UE to an MC Server via 3GPP access.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates the media plane architecture. On the left, a box labeled 'MC client hosted by a non-3GPP device' contains two sub-components: 'MC gateway client' and 'Service dependent media function'. The 'MC gateway client' connects to a 'CSC-GW'. The 'Service dependent media function' connects to the 'CSC-GW' via a line labeled 'Unicast/Multicast'. The 'CSC-GW' is located at the boundary of 'non-3GPP access' (indicated by a vertical dashed line). To the right of the 'non-3GPP access' boundary is the 'MC gateway UE' box, which contains 'MC gateway UE server' and 'MC gateway UE media distribution function'. The 'CSC-GW' connects to the 'MC gateway UE server'. The 'MC gateway UE media distribution function' connects to the 'MC gateway UE server'. From the 'MC gateway UE media distribution function', two lines extend to the right, labeled 'Unicast (ref. points)' and 'Multicast (ref. points)'. These lines cross the '3GPP access' boundary (another vertical dashed line) and connect to the 'Service dependent media distribution function' box inside the 'MC Server' box on the far right. + +Figure 7.1.2.3-1: Media plane diagram showing the flow of unicast and multicast traffic from an MC client on a non-3GPP device through a CSC-GW and an MC gateway UE to an MC Server via 3GPP access. + +Figure 7.1.2.3-1: Media plane + +### 7.1.3 Solution evaluation + +The functional architecture describes how non-3GPP devices, which are connected via non-3GPP access to an MC gateway UE, are connected to the MC system. One type of non-3GPP devices can host MC clients, where a second type cannot host MC clients and so the MC gateway UE hosts them for the non-3GPP device. The use of multiple MC gateway UEs simultaneously by an MC client is described. + +The reference points for the signalling control plane and the media plane, including MBMS, are described. + +## 7.2 Connection authorisation with the MC gateway UE + +### 7.2.1 General + +This solution addresses the key issue 2 described in clause 5.2 on authorisation for connection of non-3GPP devices with an MC gateway UE. The solution only applies to non-3GPP devices which can host an MC client. + +With this procedure the MC gateway UE performs authorization for the use of the MC gateway UE by the MC client, i.e. the binding between the MC gateway UE and the MC client is authorized and controlled by the MC gateway UE. The solution implies that authorisation functionality is provided by the MC gateway UE. + +### 7.2.2 Information flows + +#### 7.2.2.1 Connection authorization request + +Table 7.2.2.1-1 describes the information flow connection authorization request sent from the MC client, which resides on a non-3GPP device, to the MC gateway UE. + +**Table 7.2.2.1-1: Connection authorization request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------|--------|---------------------------------------------------------| +| GW MC service ID (see NOTE) | M | The GW MC service ID of the requesting MC service user. | +| NOTE: The GW MC service ID indicates for which MC service the connection is to be authorised. | | | + +NOTE: The MC service ID used for MC service authorisation and the GW MC service ID used for connection authorization may have different values. Both identities are configured by the Mission Critical Organisation. + +#### 7.2.2.2 Connection authorization response + +Table 7.2.2.2-1 describes the information flow connection authorization response sent from the MC gateway UE to the MC client. + +**Table 7.2.2.2-1: Connection authorization response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user. | +| Response | M | Result of the connection authorization request, service feasibility, and connection evaluation. | + +### 7.2.3 MC service UE configuration data + +Table 7.2.3-1 describes the MC service UE configuration data which must be known by an MC service UE after MC service authorization. + +**Table 7.2.3-1: UE configuration data (on network)** + +| Reference | Parameter description | +|--------------------------------------|------------------------------------| +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service ID | +| | > GW MC service ID | + +### 7.2.4 Initial MC gateway UE configuration data + +The initial MC gateway UE configuration data is essential to the MC gateway UE to successfully connect MC clients to the MC system. The initial MC gateway UE configuration data can be the same or different across MC gateway UEs. + +Data in table 7.2.4-1 is provided to the MC gateway UE during the bootstrap process and can be configured on the MC gateway UE offline using the CSC-11 reference point or via other means. + +**Table 7.2.4-1: Initial MC gateway UE configuration data (on-network)** + +| Reference | Parameter description | +|--------------------------------------|-------------------------------------------------| +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service IDs for MCPTT | +| | > GW MC service ID | +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service IDs for MCVideo | +| | > GW MC service ID | +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service IDs for MCData | +| | > GW MC service ID | + +NOTE: Configured MC service IDs indicate the support of an MC service. + +### 7.2.5 Procedure + +The procedure for connection authorisation with an MC gateway UE is shown in figure 7.2.5-1. + +#### Pre-conditions + +- The MC service user wishes to have access to MC services by using a non-3GPP device. +- The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE. +- The MC client has been provided with an appropriate GW MC service ID. +- The MC gateway UE has performed service authorization for one or more MC services with the MC system. +- The MC service user has selected an MC gateway UE or alternatively, the MC client has performed a selection by internal criteria. + +NOTE 1: The internal criteria are outside the scope of the present document. + +![Sequence diagram showing the connection authorization procedure between an MC client and an MC gateway UE. The MC client sends a '1. Connection authorization request' to the MC gateway UE. The MC gateway UE performs a '2. Authorization and service check' (indicated by a self-call box). Finally, the MC gateway UE sends a '3. Connection authorization response' back to the MC client.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +``` + +sequenceDiagram + participant MC client + participant MC gateway UE + Note right of MC gateway UE: 2. Authorization and service check + MC client->>MC gateway UE: 1. Connection authorization request + MC gateway UE->>MC gateway UE: 2. Authorization and service check + MC gateway UE->>MC client: 3. Connection authorization response + +``` + +Sequence diagram showing the connection authorization procedure between an MC client and an MC gateway UE. The MC client sends a '1. Connection authorization request' to the MC gateway UE. The MC gateway UE performs a '2. Authorization and service check' (indicated by a self-call box). Finally, the MC gateway UE sends a '3. Connection authorization response' back to the MC client. + +**Figure 7.2.5-1: Connection authorisation with the MC gateway UE** + +1. The MC client requests connection authorization with the MC gateway UE. The MC client of the MC service user provides the GW MC service ID. +2. The MC gateway UE performs an authorization check by using the provided GW MC service ID to verify that the MC service user is permitted to use the MC gateway UE to access an MC server. + +In addition, the MC gateway UE checks whether: + +- the requested MC service, as indicated by the GW MC service ID, is supported by the MC gateway UE; + +- a network status information is available, the MC gateway UE should check if the resources and network coverage are sufficient for the requested service at the current location for the specific MC client sending the connection authorization request; +- a roaming scenario has been identified (e.g. switch between EPC and 5GC), then depending on operator policy, roaming agreements, and on national/regional regulatory requirements further check on the received request should be performed (e.g. a decision on how to handle the IP connectivity, the QoS Flows, etc.); +- the number of UEs present in a geographical area indicates that the maximum capacity is reached or a congestion status is occurred (i.e. in such situation pre-defined access control, access identities & access category rules will be used to handle the communication priority); +- the requested QoS can be provided under the current network operating conditions; +- a release mismatch is identified between the MC gateway UE and MC client or has been identified between the MC gateway UE and the MC server. + +NOTE 2: The authorization check mechanism is outside the scope of the present document. Further checks, for example, could be based on a pre-configured list of users who are expected to request connection authorization with the MC gateway UE. + +3. The MC gateway UE sends the connection authorization response to the MC client. + +After successful connection with the MC gateway UE, the MC client has now access to an MC server and may continue with user authentication and service authorization. + +If the MC service user wishes to have access to another MC service, the above procedure is repeated. The MC service user may select a different MC gateway UE for the new MC service, if multiple MC gateway UEs are available. + +### 7.2.6 Solution evaluation + +The authorization check performed by the MC gateway UE requires up to date information which must be pre-configured. + +The MC gateway UE acts as an MC application connection node which enables and handles user signalling traffic and media plane traffic individually, i.e. on a per MC service user basis, between the MC client and the corresponding MC server. + +## 7.3 Connection authorisation with an MC server via an MC gateway UE + +### 7.3.1 General + +This solution addresses the key issue 2 described in clause 5.2 on authorisation for connection of non-3GPP devices with an MC gateway UE. The solution only applies to non-3GPP devices which can host an MC client. + +With this procedure the MC server performs authorization for the use of the MC gateway UE by the MC client, i.e. the binding between the MC gateway UE and the MC client is authorized and controlled by the MC server. The MC gateway UE is not acting as the authorisation instance which authenticates MC clients. + +### 7.3.2 Information flows + +#### 7.3.2.1 Connection authorization request + +Table 7.3.2.1-1 describes the information flow connection authorization request sent from the MC client, which resides on a non-3GPP device, to the MC gateway UE, and from the MC gateway UE to the MC server. + +**Table 7.3.2.1-1: Connection authorization request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------|--------|---------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user. | +| NOTE: The GW MC service ID indicates for which MC service the connection is to be authorised. | | | + +NOTE: The MC service ID used for MC service authorisation and the GW MC service ID used for connection authorization may have different values. Both identities are configured by the Mission Critical Organisation. + +#### 7.3.2.2 Connection authorization response + +Table 7.3.2.2-1 describes the information flow connection authorization response sent from the MC server to the MC gateway UE, and from the MC gateway UE to the MC client residing on a non-3GPP device. + +**Table 7.3.2.2-1: Connection authorization response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user. | +| Response | M | Result of the connection authorization request, service feasibility, and connection evaluation. | + +### 7.3.3 MC server configuration data + +Table 7.3.3-1 describes configuration data to be stored in the MC server to perform an authorization check to verify that access via the MC gateway UE is permitted. + +**Table 7.3.3-1: MC service configuration data (on-network)** + +| Reference | Parameter description | MC client | MC server | Configuration management server | +|--------------------------------------|---------------------------------------|-----------|-----------|---------------------------------| +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service ID(s) | N | Y | Y | +| | > GW MC service ID | N | Y | Y | + +### 7.3.4 Initial MC gateway UE configuration data + +The initial MC gateway UE configuration data is essential to the MC gateway UE to successfully connect MC clients to the MC system. The initial MC gateway UE configuration data can be the same or different across MC gateway UEs. + +Data in table 7.3.4-1 is provided to the MC gateway UE during the bootstrap process and can be configured on the MC gateway UE offline using the CSC-11 reference point or via other means. + +**Table 7.3.4-1: Initial MC gateway UE configuration data (on-network)** + +| Reference | Parameter description | +|--------------------------------------|-------------------------------------------------| +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service IDs for MCPTT | +| | > GW MC service ID | +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service IDs for MCVideo | +| | > GW MC service ID | +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service IDs for MCData | +| | > GW MC service ID | + +NOTE: Configured MC service IDs indicate the support of an MC service. + +### 7.3.5 Procedure + +The procedure for connection authorisation via an MC gateway UE towards an MC server is shown in figure 7.3.5-1. + +#### Pre-conditions + +- The MC service user wishes to have access to MC services using a non-3GPP device. +- The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE. +- The MC client has been provided with an appropriate GW MC service ID. +- The MC gateway UE has performed service authorization for one or more MC services with the MC system. +- The MC service user has selected an MC gateway UE or alternatively, the MC client has performed a selection by internal criteria. + +NOTE: The internal criteria are outside the scope of the present document. + +![Sequence diagram showing the connection authorization procedure between an MC client, MC gateway UE, and MC server.](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +``` + +sequenceDiagram + participant MC client + participant MC gateway UE + participant MC server + Note right of MC gateway UE: 2. Service check + Note right of MC server: 4. Authorization check + Note right of MC gateway UE: 6. Mark MC client as authorized + + MC client->>MC gateway UE: 1. Connection authorization request + MC gateway UE->>MC server: 3. Connection authorization request + MC server-->>MC gateway UE: 5. Connection authorization response + MC gateway UE-->>MC client: 7. Connection authorization response + +``` + +Sequence diagram showing the connection authorization procedure between an MC client, MC gateway UE, and MC server. + +**Figure 7.3.5-1: Connection authorisation with an MC server via an MC gateway UE** + +1. The MC client requests connection authorization via the MC gateway UE with an MC server. The client of the MC service user provides the GW MC service ID. + +2. The MC gateway UE checks whether: + +- the requested MC service, as indicated by the GW MC service ID, is supported by the MC service gateway – + - a network status information is available; the MC gateway UE should check if the resources and network coverage are sufficient for the requested service at the current location for the specific MC client sending the connection authorization request; + - a roaming scenario has been identified (e.g. switch between EPC and 5GC), then depending on operator policy, roaming agreements, and on national/regional regulatory requirements further check on the received request should be performed (e.g. a decision on how to handle the IP connectivity, the QoS Flows, etc.); + - the number of UEs present in a geographical area indicates that the maximum capacity is reached or a congestion status is occurred (i.e. in such situation pre-defined access control, access identities & access category rules will be used to handle the communication priority); + - the requested QoS can be provided under the current network operating conditions; + - a release mismatch is identified between the MC gateway UE and MC client or has been identified between the MC gateway UE and the MC server. + +If the MC service is supported, the procedure continues with step 3, otherwise the procedure proceeds with step 7. + +3. The MC gateway UE sends the connection authorization request to the MC server. + +4. The MC server performs an authorization check, to verify that access via the MC gateway UE is permitted. + +5. The MC server sends the connection authorization response to the MC gateway UE. + +6. The MC gateway UE marks the MC client as authorized to have MC service access via the MC gateway UE. + +7. The MC gateway UE sends the connection authorization response to the MC client. + +After successful connection with the MC gateway UE, the MC client has now access to the MC server and may continue with user authentication and service authorization. + +If the MC service user wishes to have access to another MC service, the above procedure is repeated. The MC service user may select a different MC gateway UE for the new MC service, if multiple MC gateway UEs are available. + +### 7.3.6 Solution evaluation + +The MC gateway UE is not required to check whether the MC service user can have MC service access via the MC gateway UE. + +The MC gateway UE acts as an MC application connection node which enables and handles user signalling traffic and media plane traffic individually, i.e. on per MC service user basis, between the MC client and the corresponding MC server. + +## 7.4 Using IMS identities behind the MC gateway UE + +### 7.4.1 General + +This solution addresses the key issue 3 described in clause 5.3 on identification of MC service users behind an MC gateway UE residing on non-3GPP devices. + +### 7.4.2 Solution description + +The MC gateway UE offers access to the MC system for several MC service clients. The MC service clients can be either located in the MC gateway UE or in non-3GPP devices connected to the MC gateway UE via non-3GPP access. Simultaneous sharing of an MC gateway UE by various MC service clients requires a relationship between the MC + +service identities used by the MC service clients with media streams passing the MC gateway UE towards the MC system to share the network transport resources of the MC gateway UE. + +It is assumed that the MC service user behind the MC gateway UE has no 3GPP transport access credentials (i.e. no UICC), whereas the MC system relies on IMS identities (i.e. IMPUs/IMPIs) needed for authorisation with the IMS. In addition, in MC systems there exist a one-to-one correspondence of MC service IDs with IMPUs for enabling routing of signalling traffic between the MC service server and the MC service client. + +Taking the above into account two options are considered. + +Option 1 (see figure 7.4.2-1) relies on MC service IDs provided by the MC gateway UE. The MC service clients behind the MC gateway UE share the credentials from the IMS subscription of the MC gateway UE. The number of MC service clients behind the MC gateway UE is determined by the number of subscribed MC service IDs that are associated with the IMS subscription of the MC gateway UE. + +![Diagram illustrating the sharing of the MC gateway UE's IMS subscription. On the right, a large box labeled 'MC gateway UE (using MC service capabilities)' contains a dashed box labeled 'IMS subscription'. Inside the IMS subscription box is a circle labeled 'MC service client'. On the left, three boxes represent 'non-3GPP device'. The top two are labeled 'non-3GPP device' and each contains a dashed box with a circle labeled 'MC service client'. The bottom box is labeled 'non-3GPP device (cannot host MC service clients)' and is empty. Dashed lines connect the 'IMS subscription' box to the 'MC service client' circles in the top two non-3GPP devices, and another dashed line connects the 'IMS subscription' box to the empty bottom non-3GPP device box.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +Diagram illustrating the sharing of the MC gateway UE's IMS subscription. On the right, a large box labeled 'MC gateway UE (using MC service capabilities)' contains a dashed box labeled 'IMS subscription'. Inside the IMS subscription box is a circle labeled 'MC service client'. On the left, three boxes represent 'non-3GPP device'. The top two are labeled 'non-3GPP device' and each contains a dashed box with a circle labeled 'MC service client'. The bottom box is labeled 'non-3GPP device (cannot host MC service clients)' and is empty. Dashed lines connect the 'IMS subscription' box to the 'MC service client' circles in the top two non-3GPP devices, and another dashed line connects the 'IMS subscription' box to the empty bottom non-3GPP device box. + +**Figure 7.4.2-1: Sharing the MC gateway UE's IMS subscription** + +Option 2 (see figure 7.4.2-2) relies on the use of the IMS Credentials (IMC) application specified in 3GPP TS 23.228 [4]. The MC service clients behind the MC gateway UE use their own IMS subscription and do not rely on the IMS subscription from the MC gateway UE. The number of MC service clients behind the MC gateway UE is independent from the number of subscribed MC service IDs that are associated with the IMS subscription of the MC gateway UE. + +![Diagram illustrating two options for using independent IMS subscriptions. Option 1 shows a non-3GPP device with one MC service client and one IMS subscription. Option 2 shows a non-3GPP device with two MC service clients and one IMS subscription. The MC gateway UE (using MC service capabilities) is shown on the right, containing one IMS subscription and two MC service clients.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates two configurations for MC service clients and IMS subscriptions. On the left, two boxes represent 'non-3GPP device' options. The top box contains a dashed rectangle labeled 'IMS subscription' with a circle inside labeled 'MC service client'. The bottom box contains a dashed rectangle labeled 'IMS subscription' with two circles inside, each labeled 'MC service client'. On the right, a box labeled 'MC gateway UE (using MC service capabilities)' contains a dashed rectangle labeled 'IMS subscription' with two circles inside, each labeled 'MC service client'. + +Diagram illustrating two options for using independent IMS subscriptions. Option 1 shows a non-3GPP device with one MC service client and one IMS subscription. Option 2 shows a non-3GPP device with two MC service clients and one IMS subscription. The MC gateway UE (using MC service capabilities) is shown on the right, containing one IMS subscription and two MC service clients. + +**Figure 7.4.2-2: Using independent IMS subscriptions** + +Both options support an unambiguous identification of MC service clients behind the MC gateway UE. Option 2 also has the degree of freedom that the user profiles associated with the devices behind the MC gateway UE are independent of the MC gateway user profile. + +### 7.4.3 Solution evaluation + +Both options support an unambiguous identification of MC service clients behind the MC gateway UE and multiple simultaneous MC gateway UE use. Option 2 offers the degree of freedom that the user profiles used on the non -3GPP devices behind the MC gateway UE are independent from those of the MC gateway user profile. Whereas the pre-configuration of IMPUs for option 1 is not very flexible and sharing of IMPUs between different MC clients might have additional implications (e.g. managing of available IMPUs between MC clients). Option 2 seems not to have any significant drawbacks, has less implications regarding pre-configuration and is more future proof (e.g. parallel use of multiple MC gateway UEs). + +Option 2 is selected as way forward, i.e. on MC clients capable to host MC service clients separate IMS subscriptions are used, while for non-3GPP devices which cannot host MC client(s) the use IMS subscription(s) provided by the serving MC gateway UE(s) is applied. + +## 7.5 Connection authorisation for non-3GPP devices that do not host an MC client + +### 7.5.1 General + +This solution addresses the key issue 2 described in clause 5.2 on authorisation for connection of non-3GPP devices with an MC gateway UE. The solution is applied to non-3GPP devices which cannot host an MC client. + +With this procedure the MC server performs authorization for the use of the MC gateway UE by the MC client, i.e. the binding between the MC gateway UE and the MC client is authorized and controlled by the MC server. + +**NOTE:** The interworking between the MC client hosted at the MC gateway UE and an MC service user is out of scope of the present document, nevertheless, the connection authorisation performed by the MC gateway UE shall enable the non-3GPP devices to get the access to MC services requested by the service user. + +### 7.5.2 Information flows + +#### 7.5.2.1 Connection authorization request + +Table 7.5.2.1-1 describes the information flow connection authorization request sent from the MC client, which resides on a MC gateway UE, to the MC server. + +**Table 7.5.2.1-1: Connection authorization request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------|--------|---------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user. | +| NOTE: The GW MC service ID indicates for which MC service the connection is to be authorised. | | | + +NOTE: The MC service ID used for MC service authorisation and the GW MC service ID used for connection authorization may have different values. Both identities are configured by the Mission Critical Organisation. + +#### 7.5.2.2 Connection authorization response + +Table 7.5.2.2-1 describes the information flow connection authorization response sent from the MC server to the MC client residing on the MC gateway UE. + +**Table 7.5.2.2-1: Connection authorization response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user. | +| Result | M | Success or failure of the connection authorization request (authorization successful/failed; service not supported). | + +### 7.5.3 MC server configuration data + +Table 7.5.3-1 describes configuration data to be stored in the MC server to perform an authorization check to verify that access via the MC gateway UE is permitted. + +**Table 7.5.3-1: MC service configuration data (on-network)** + +| Reference | Parameter description | MC client | MC server | Configuration management server | +|--------------------------------------|---------------------------------------|-----------|-----------|---------------------------------| +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of permitted GW MC service ID(s) | N | Y | Y | +| | > GW MC service ID | N | Y | Y | + +### 7.5.4 Initial MC gateway UE configuration data + +The initial MC gateway UE configuration data is essential to the MC gateway UE to successfully connect MC clients to the MC system. The initial MC gateway UE configuration data can be the same or different across MC gateway UEs. + +Data in Table 7.5.4-1 is provided to the MC gateway UE during the bootstrap process and can be configured on the MC gateway UE offline using the CSC-11 reference point or via other means. + +**Table 7.5.4-1: Initial MC gateway UE configuration data (on-network)** + +| Reference | Parameter description | +|--------------------------------------|---------------------------------------| +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of GW MC service IDs for MCPTT | +| | > GW MC service ID | +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of GW MC service IDs for MCVideo | +| | > GW MC service ID | +| Subclause 5.15 of 3GPP TS 22.280 [3] | List of GW MC service IDs for MCData | +| | > GW MC service ID | + +NOTE: Configured MC service IDs indicate the support of an MC service. + +### 7.5.5 Procedure + +The procedure for connection authorisation of an MC client hosted by the MC gateway UE towards an MC server is shown in figure 7.5.5-1. + +#### Pre-conditions + +- The MC service user wishes to have access to MC services using a non-3GPP device, where the MC client is hosted by the MC gateway UE. +- The MC service user has selected an MC gateway UE or alternatively, the non-3GPP has performed a selection by internal criteria. + +NOTE: The internal criteria are outside the scope of the present document. + +- The MC client, which is hosted by the MC gateway UE, has been configured with the necessary parameters needed for connectivity with the MC gateway UE. +- The MC gateway UE has performed service authorization for one or more MC services with the MC system. + +![Sequence diagram showing the connection authorization process between an MC client hosted by an MC gateway UE and an MC server. The process consists of three steps: 1. Connection authorization request from the MC client to the MC server; 2. Authorization check performed by the MC server; 3. Connection authorization response from the MC server back to the MC client.](14515d82ffeec9475b9add3036ff26ab_img.jpg) + +``` + +sequenceDiagram + participant MC client hosted by MC gateway UE + participant MC server + Note right of MC server: 2. Authorization check + MC client hosted by MC gateway UE->>MC server: 1. Connection authorization request + MC server-->>MC client hosted by MC gateway UE: 3. Connection authorization response + +``` + +Sequence diagram showing the connection authorization process between an MC client hosted by an MC gateway UE and an MC server. The process consists of three steps: 1. Connection authorization request from the MC client to the MC server; 2. Authorization check performed by the MC server; 3. Connection authorization response from the MC server back to the MC client. + +**Figure 7.5.5-1: Connection authorisation of an MC client hosted by an MC gateway UE** + +1. The MC client, hosted by the MC gateway UE, requests connection authorization with an MC server by providing the GW MC service ID. The MC gateway UE sends the connection authorization request to the MC server. +2. The MC server performs an authorization check, to verify that access using the MC gateway UE is permitted. +3. The MC server sends the connection authorization response to the MC client residing on the MC gateway UE. + +The MC client has now access to the MC server and may continue with user authentication and service authorization. + +If the MC service user wishes to have access to another MC service, the above procedure is repeated. The MC service user may select a different MC gateway UE for the new MC service, if multiple MC gateway UEs are available. + +### 7.5.6 Solution evaluation + +The non-3GPP device is not required to host an MC client, instead the MC gateway UE hosts the MC client for the non-3GPP device. + +The MC gateway UE acts as an MC application connection node which enables and handles user signalling traffic and media plane traffic individually, i.e. on per MC service user basis, between the non-3GPP device and the corresponding MC server. + +## 7.6 3GPP access network related location information management + +### 7.6.1 General + +This solution addresses the key issue 7 described in the clause 5.7 on 3GPP access network related location management by MC clients. The solution only applies to non-3GPP devices which can host an MC client, and which cannot handle the location reporting configuration related to the 3GPP access network by itself. + +With this procedure the MC client requests the MC gateway UE to handle the location reporting configuration related to the 3GPP access network. Also, MC clients can fetch the 3GPP access network related location information if it requires to report the same to the MC system. + +### 7.6.2 Information flows + +#### 7.6.2.1 MC GW Location reporting configuration + +Table 7.6.2.1-1 describes the information flow from the MC client, which resides on a non-3GPP device, to the MC gateway UE for the location reporting configuration. + +**Table 7.6.2.1-1: MC GW Location reporting configuration** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user | +| Requested location information | O<br>(see NOTE 1) | Identifies what location information is requested | +| Triggering criteria | O<br>(see NOTE 1) | Identifies when the location management client will send the location report (see NOTE 2) | +| Minimum time between consecutive reports | O<br>(see NOTE 1) | Defaults to 0 if absent | +| NOTE 1: If none of the information elements is present, this represents a cancellation for location reporting, if configured. | | | +| NOTE 2: The triggering criteria contains only the events related to the 3GPP access network. | | | + +#### 7.6.2.2 MC GW Location information report + +Table 7.6.2.2-1 describes the information flow from the MC gateway UE to the MC client residing on a non-3GPP device for the location information reporting. + +**Table 7.6.2.2-1: MC GW Location information report** + +| Information element | Status | Description | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user | +| Triggering event | O | Identity of the event that triggered the sending of the report | +| Location information (see NOTE) | O | Location information of the MC gateway UE | +| NOTE: | The following location information elements which are related to 3GPP access network shall be present (configurable): Serving and neighbouring ECGI, MBMS SAsIs, MBMSfnArea, PLMN ID. | | + +#### 7.6.2.3 MC GW Location information request + +Table 7.6.2.3-1 describes the information flow from the MC client residing on a non-3GPP device to the MC gateway UE for requesting an immediate location information report. + +**Table 7.6.2.3-1: MC GW Location information request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------| +| GW MC service ID | M | The GW MC service ID of the requesting MC service user | + +### 7.6.3 Procedure + +#### 7.6.3.1 Event-triggered location reporting procedure + +The procedure for how the MC clients residing on non-3GPP devices handling the location reporting configuration containing the trigger criteria related to the 3GPP access network related location information is shown in the figure 7.6.3.1-1. + +##### Pre-conditions + +- The MC service user wishes to have access to MC services by using a non-3GPP device. +- The MC client successfully completed service authorization via MC gateway UE. + +![Sequence diagram of the event-triggered location reporting procedure. Lifelines: MC Client, MC Gateway UE, and Location Management Server. The sequence starts with the LMS sending a configuration to the MC Client, which then passes it to the MC Gateway UE. The UE triggers an event and sends a report back to the client, which then updates its local info and sends a final report to the LMS via the UE.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MC Client + participant MC Gateway UE + participant Location Management Server + + Note right of Location Management Server: 1. MC client received location reporting configuration from LMS which contains the triggering criteria of 3GPP access network related location information changes + MC Client->>MC Gateway UE: 2. MC GW Location reporting configuration + Note right of MC Gateway UE: 3. Configured location reporting event triggers + MC Gateway UE->>MC Client: 4. MC GW Location information report + Note left of MC Client: 5. Create the location information report + Note right of MC Client: 6. MC Client sends the Location information report the LMS via MC Gateway UE + +``` + +Sequence diagram of the event-triggered location reporting procedure. Lifelines: MC Client, MC Gateway UE, and Location Management Server. The sequence starts with the LMS sending a configuration to the MC Client, which then passes it to the MC Gateway UE. The UE triggers an event and sends a report back to the client, which then updates its local info and sends a final report to the LMS via the UE. + +**Figure 7.6.3.1-1: Event-triggered location reporting procedure** + +1. MC client receives the location reporting configuration request from LMS which contains the triggering criteria of 3GPP access network related location information changes. +2. MC client sends the MC GW Location reporting configuration to the MC gateway UE containing the 3GPP access network related location information triggers and the requested location information. MC Gateway UE stores the location reporting configuration and starts monitoring for the triggers as received in the MC GW location reporting configuration. +3. A location reporting event occurs, triggering step 4. +4. MC gateway UE sends the MC GW Location information report containing the location information requested by the MC client. +5. MC client updates the locally available location information with the location information received from the MC gateway UE. +6. The MC client sends a location information report to the location management server, containing location information identified by the location management server and available to the MC client. + +#### 7.6.4.2 On-demand location reporting procedure + +The MC client may need to immediately send the location report to the location management sometimes and the requested location information may be related to the 3GPP access network. Under these circumstances the MC client can request the MC gateway UE to report its location information as described in the figure 7.6.4.2-1. + +##### Pre-conditions + +- The MC service user wishes to have access to MC services by using a non-3GPP device. +- The MC client successfully completed service authorization via MC Gateway UE. + +![Sequence diagram illustrating the On-demand location reporting procedure. The diagram shows three lifelines: MC Client, MC Gateway UE, and Location Management Server. The sequence of messages is: 1. MC client received location information request to send the location information immediately (from LMS to MC Client); 2. Notify user and ask for permission to share location (internal to MC Client); 3. MC GW Location information request (from MC Client to MC Gateway UE); 4. MC GW Location information report (from MC Gateway UE to MC Client); 5. Update the available location information with the location information received from MC Gateway UE (internal to MC Client); 6. MC client sends the Location information report to the LMS via MC Gateway UE (from MC Client to LMS via MC Gateway UE).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant MC Client + participant MC Gateway UE + participant Location Management Server + + Note right of MC Client: 1. MC client received location information request to send the location information immediately + Note left of MC Client: 2. Notify user and ask for permission to share location + MC Client->>MC Gateway UE: 3. MC GW Location information request + MC Gateway UE-->>MC Client: 4. MC GW Location information report + Note left of MC Client: 5. Update the available location information with the location information received from MC Gateway UE + Note right of MC Client: 6. MC client sends the Location information report to the LMS via MC Gateway UE + MC Client->>MC Gateway UE: + MC Gateway UE->>Location Management Server: + +``` + +Sequence diagram illustrating the On-demand location reporting procedure. The diagram shows three lifelines: MC Client, MC Gateway UE, and Location Management Server. The sequence of messages is: 1. MC client received location information request to send the location information immediately (from LMS to MC Client); 2. Notify user and ask for permission to share location (internal to MC Client); 3. MC GW Location information request (from MC Client to MC Gateway UE); 4. MC GW Location information report (from MC Gateway UE to MC Client); 5. Update the available location information with the location information received from MC Gateway UE (internal to MC Client); 6. MC client sends the Location information report to the LMS via MC Gateway UE (from MC Client to LMS via MC Gateway UE). + +**Figure 7.6.4.2-1: On-demand location reporting procedure** + +1. MC client receives the location information request from LMS to send the location information immediately or any other events where it has to send the location report to the location management server immediately like initial login, group call etc. Requested location information includes the location information related to 3GPP access network. +2. MC service user is notified and asked for permission to share location information. MC service user can accept or deny the request. +3. MC client sends the MC GW Location information request to the MC Gateway requesting for the location information related to the 3GPP access network of the MC Gateway UE. +4. MC gateway UE sends the MC GW Location information report containing the location information requested by the MC client. +5. MC client updates the locally available location information with the location information received from the MC gateway UE. +6. The MC client sends a location information report to the location management server, containing location information identified by the location management server and available to the MC client. + +#### 7.6.5.3 Location reporting cancel procedure + +The location reporting cancel procedure reuses the information flow of location reporting configuration. + +Pre-conditions + +- The MC service user wishes to have access to MC services by using a non-3GPP device. +- The MC client successfully completed service authorization via MC gateway UE. +- The MC client no longer needs the location information report from MC gateway UE. + +![Sequence diagram illustrating the on-demand location reporting procedure. The diagram shows two lifelines: MC Client and MC Gateway UE. The MC Client sends a message labeled '1. MC GW Location reporting configuration' to the MC Gateway UE. The MC Gateway UE then sends a message labeled '2. Stop location report' back to the MC Client.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` +sequenceDiagram + participant MC Client + participant MC Gateway UE + Note right of MC Gateway UE: 2. Stop location report + MC Client->>MC Gateway UE: 1. MC GW Location reporting configuration +``` + +Sequence diagram illustrating the on-demand location reporting procedure. The diagram shows two lifelines: MC Client and MC Gateway UE. The MC Client sends a message labeled '1. MC GW Location reporting configuration' to the MC Gateway UE. The MC Gateway UE then sends a message labeled '2. Stop location report' back to the MC Client. + +**Figure 7.6.5.3-1: On-demand location reporting procedure** + +1. The location management client sends MC GW location reporting configuration without any information element to the MC gateway UE to stop location reporting from the MC gateway UE. +2. The MC gateway UE stops sending location information reports to the MC client. + +### 7.6.4 Solution evaluation + +This solution provides an additional information flows which are exchanged between the MC gateway UE and the MC clients residing on non-3GPP devices to ensure that the MC clients can handle the location reporting configuration containing the triggering criteria related to the 3GPP access network information and also provide the location information related to the 3GPP access network when requested. + +## 7.7 Routing of data and signalling by the MC gateway UE + +### 7.7.1 General + +This solution addresses the key issue 5 described in clause 5.5 on clarifying how the MC gateway UE routes and maps the traffic data and signalling information between non-3GPP devices and the network. + +Two different options are envisaged. + +### 7.7.2 MC client uses the IP address from the MC gateway UE + +The connection authorization process takes place centrally with the inclusion of the MC service server (see clause 7.3). The MC gateway UE stores the correlation between the GW MC service ID and the IP address used by the MC client once it receives the connection authorisation request. The assigned IP address of the MC gateway UE (used for 3GPP transport) is used to forward the connection authorization request from the MC client to the MC server, since the MC client IP address is unknown to the MC system. The connection authorization response is sent back accordingly from the MC server towards the MC gateway UE, which then forwards it to the corresponding MC client. Subsequent procedures initiated by the MC client, i.e. SIP registration, user authentication and service authorisation, would also use the MC gateway UE's IP address. The MC gateway UE's IP address would then also be used in the case of local connection authorization (see clause 7.2). + +The drawback of the approach is when the IP address of the MC gateway UE changes, all active MC clients would be affected with their communication with the MC server. + +![Figure 7.7.2-1: MC client uses MC gateway UE's IP address. This diagram shows three main components: an MC client hosted by a non-3GPP device, an MC gateway UE, and MC servers. The MC client contains 'MC Client(s)' and connects to the MC gateway UE via interfaces labeled MCX-n, CSC-n, and SIP-n. The MC gateway UE contains 'MC service Client(s)' and connects to the MC servers via the same interfaces. Above the components, a 'local IP' label spans from the MC client to the MC gateway UE, and an 'MC gateway UE IP' label spans from the MC gateway UE to the MC servers.](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 7.7.2-1: MC client uses MC gateway UE's IP address. This diagram shows three main components: an MC client hosted by a non-3GPP device, an MC gateway UE, and MC servers. The MC client contains 'MC Client(s)' and connects to the MC gateway UE via interfaces labeled MCX-n, CSC-n, and SIP-n. The MC gateway UE contains 'MC service Client(s)' and connects to the MC servers via the same interfaces. Above the components, a 'local IP' label spans from the MC client to the MC gateway UE, and an 'MC gateway UE IP' label spans from the MC gateway UE to the MC servers. + +Figure 7.7.2-1: MC client uses MC gateway UE's IP address + +### 7.7.3 MC client uses an own IP address + +For communications between the MC client and the MC server via an MC gateway UE, the MC client's IP address is also used for communications between the MC gateway UE and the MC server. For this, the IP address range must be known by the MC service environment beforehand to enable the MC client's host (non-3GPP device) routing. In addition, it requires a correlation between the MC client's IP address and the MC gateway UE's IP address as the next hop. The advantage would be the independence between an MC gateway UE IP address and the MC client IP address. + +![Figure 7.7.3-1: MC client uses local IP address. This diagram shows the same three components as Figure 7.7.2-1. The MC client connects to the MC gateway UE via MCX-n, CSC-n, and SIP-n interfaces. The MC gateway UE connects to the MC servers via the same interfaces. Above the components, a 'local IP' label spans from the MC client to the MC servers, and an 'MC gateway UE IP' label is shown below it, also spanning from the MC gateway UE to the MC servers.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +Figure 7.7.3-1: MC client uses local IP address. This diagram shows the same three components as Figure 7.7.2-1. The MC client connects to the MC gateway UE via MCX-n, CSC-n, and SIP-n interfaces. The MC gateway UE connects to the MC servers via the same interfaces. Above the components, a 'local IP' label spans from the MC client to the MC servers, and an 'MC gateway UE IP' label is shown below it, also spanning from the MC gateway UE to the MC servers. + +Figure 7.7.3-1: MC client uses local IP address + +The approach below is referred to as routing behind the UE on an APN/DNN basis enables the routing of packets to IP addresses that do not belong to the PDN session or PDU session, but exist behind it. The routing behind (framed routing) the UE functionality enables the routing of packets to IP addresses that do not belong to the PDN/PDU session of the UE. The IP address of the MC client associated with the non-3GPP device can be different than the MC GW UE address. + +The approach of framed routing (3GPP TS 23.501 [10], clause 5.6.14) in which the prefix, i.e. IPv6 prefix, of the route to the corresponding host IP address is marked behind the UE. The corresponding UPF may indicate support of framed routing by setting the FRRT flag in accordance to 3GPP TS 29.244 [11]. + +### 7.7.4 Solution evaluation + +The options described in clause 7.7.2. and clause 7.7.3 take different approaches. In the first approach, only the IP address of the MC gateway UE is used for CP and UP traffic of the MC clients in relation to the SIP core and the MC service servers. The MC gateway UE must provide additional functions for routing and address mapping. Another disadvantage is that when the MC gateway UE changes its IP address, all MC clients behind the MC gateway UE are always affected. The use of the MC gateway UE IP address also requires the detection of characteristics unique to a MC client, e.g. port mapping, in order to be able to differentiate between the MC clients. + +The second approach, using framed routing, enables the MC clients to act independently of the MC gateway UE IP address. This also eliminates the necessary IP address mapping function in the MC gateway UE and any type of traffic, CP and UP, is uniquely associated with the MC client's IP address. This option has been available since Rel-15 and is available for the use of PDN session and PDU session. + +## 7.8 MBMS Support for MC clients residing on non-3GPP devices + +### 7.8.1 General + +This solution addresses the key issue #4 described in the clause 5.4 on MBMS support. This solution in particular addresses the MBMS support for the MC clients residing on the non-3GPP devices. The MC gateway UE learns the MBMS bearer details from the MC clients and starts listening on them. MC gateway UE forwards the data received over MBMS bearer to the MC clients residing on non-3GPP access and have requested MC gateway UE to listen on the MBMS bearer. + +With this procedure MBMS bearer can be supported for the MC clients residing on non-3GPP devices without requiring any changes at the MC system side. Changes required are confined to the interface between MC gateway UE and the MC clients residing on non-3GPP devices. MC service server may rely on the location information received from the MC clients as defined in clause 7.6 while deciding to establish MBMS bearer. + +### 7.8.2 Information flows + +#### 7.8.2.1 MC GW MBMS bearer announcement + +Table 7.8.2.1-1 describes the information flow from the MC client which resides on a non-3GPP device to the MC gateway UE for sharing the details of MBMS bearer announcement received by the MC Client from the MC Service server. + +**Table 7.8.2.1-1: MC GW MBMS bearer announcement** + +| Information element | Status | Description | +|---------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| MC GW service ID | M | The GW MC service ID of the requesting MC service user. | +| TMGI | M | TMGI information | +| List of service area identifier | M | A list of service area identifier for the applicable MBMS broadcast area. | +| Frequency | O | Identification of frequency if multi carrier support is provided | +| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information) | +| Monitoring state | O | The monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not. | +| ROHC information | O | Indicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder. | + +#### 7.8.2.2 MC GW MBMS listening status report + +Table 7.8.2.2-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MBMS listening status report. + +**Table 7.8.2.2-1: MC GW MBMS listening status report** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMGI(s) | M | TMGI(s) information. | +| MBMS listening status(s) | M | The MBMS listening status per TMGI. | +| MBMS reception quality level | O | The reception quality level per TMGI | +| Non 3GPP transport channel establishment parameters (See NOTE) | O | This element contains the details of the non-3GPP channel establishment parameters (IP address, Port etc.) which is used by the MC gateway UE to forward the MC service communication data received over 3GPP MBMS bearer to the MC client | +| NOTE: These parameters are implementation specific and are dependent on the non 3GPP transport mechanism used between the MC client and MC gateway UE. This parameter shall be present mandatorily if the MBMS bearer listening status is success. | | | + +#### 7.8.2.3 MC GW MapGroupToBearer request + +Table 7.8.2.3-1 describes the information flow from the MC client which resides on a non-3GPP device to the MC gateway UE for sharing the details of MapGroupToBearer message received from the MC service server. + +**Table 7.8.2.3-1: MC GW MapGroupToBearer request** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------------------------| +| MC GW service ID | M | The GW MC service ID of the MC service user. | +| MCPTT group ID | M | This element identifies the MCPTT group, in which the call is started. | +| Media stream identifier | M | This element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel). | +| TMGI | M | The MBMS bearer identifier. | + +#### 7.8.2.4 MC GW MapGroupToBearer response + +Table 7.8.2.4-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MapGroupToBearer response. + +**Table 7.8.2.4-1: MC GW MapGroupToBearer response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MapGroupToBearer Status | M | Success or failure response | +| Non 3GPP transport channel establishment parameters (See NOTE) | M | This elements contains the details of the non 3GPP channel establishment parameters(IP address, Port etc.,) which is used by the MC gateway UE to forward the MC service Group communication data received over 3GPP MBMS bearer to the MC client | +| NOTE: These parameters are implementation specific and are dependent on the non 3GPP transport mechanism used between the MC client and MC gateway UE | | | + +#### 7.8.2.5 MC GW MBMS bearer quality report + +Table 7.8.2.5-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MBMS bearer quality report. + +**Table 7.8.2.5-1: MC GW MapGroupToBearer response** + +| Information element | Status | Description | +|------------------------------|--------|--------------------------------------| +| TMGI(s) | M | TMGI(s) information. | +| MBMS listening status(s) | M | The MBMS listening status per TMGI. | +| MBMS reception quality level | O | The reception quality level per TMGI | + +#### 7.8.2.6 MC GW MBMS bearer suspension indication + +Table 7.8.2.6-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MBMS bearer suspension indication. + +**Table 7.8.2.6-1: MC GW MBMS bearer suspension indication** + +| Information element | Status | Description | +|---------------------------|--------|--------------------------------------| +| TMGI(s) | M | TMGI(s) information. | +| MBMS suspension status(s) | M | The MBMS suspension status per TMGI. | + +### 7.8.3 Procedure + +#### 7.8.3.1 MBMS bearer announcement handling procedure + +Whenever the MC clients residing on non-3GPP devices receives the MBMS bearer announcements from the MC system, the MC clients shares the details of the MBMS bearer received in MBMS bearer announcement to the MC gateway UE. This enables the MC gateway UE to start monitoring the MBMS bearer. + +Figure 7.8.3.1-1 illustrates the procedure for handling the MBMS bearer announcement by the MC client and the MC gateway UE. + +Pre-conditions: + +1. The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE. +2. The MC client successfully completed service authorization via MC gateway UE. + +![Sequence diagram illustrating the handling of MBMS bearer announcement. The diagram shows interactions between MC Client (residing on non 3GPP device), MC Gateway UE, and MC service Server. The sequence starts with the MC service Server establishing MBMS bearers. Then, a procedure for MBMS bearer announcement occurs between the MC Gateway UE and the MC Client. The MC Gateway UE sends an announcement to the MC Client, who stores the information and starts monitoring. The MC Gateway UE then sends a listening status report to the MC Client. Finally, a procedure for establishing the communication channel for forwarding data occurs, followed by the MC Client sending a listening status report to the MC Gateway UE, which then forwards it to the MC service Server.](e4a14961bdc9882e296b25f7ae5f9760_img.jpg) + +``` + +sequenceDiagram + participant MC Client (residing on non 3GPP device) + participant MC Gateway UE + participant MC service Server + + Note right of MC service Server: 1. Establish MBMS bearers + Note over MC Gateway UE, MC Client: 2. Procedure for MBMS bearer announcement + MC Gateway UE->>MC Client: 3. MC GW MBMS bearer announcement + Note right of MC Gateway UE: 4. MC GW UE stores TMGI(s), service area and other info about the MBMS bearer(s), the MC GW UE starts to monitor the TMGI(s). + MC Gateway UE->>MC Client: 5. MC GW MBMS Listening status Report + Note over MC Gateway UE, MC Client: 6. Procedure for establishing the communication channel for forwarding the data received over MBMS + MC Client->>MC Gateway UE: 7a. MBMS bearer Listening status report + MC Gateway UE->>MC service Server: 7b. MBMS bearer Listening status Report + +``` + +Sequence diagram illustrating the handling of MBMS bearer announcement. The diagram shows interactions between MC Client (residing on non 3GPP device), MC Gateway UE, and MC service Server. The sequence starts with the MC service Server establishing MBMS bearers. Then, a procedure for MBMS bearer announcement occurs between the MC Gateway UE and the MC Client. The MC Gateway UE sends an announcement to the MC Client, who stores the information and starts monitoring. The MC Gateway UE then sends a listening status report to the MC Client. Finally, a procedure for establishing the communication channel for forwarding data occurs, followed by the MC Client sending a listening status report to the MC Gateway UE, which then forwards it to the MC service Server. + +**Figure 7.8.3.1-1: Handling of MBMS bearer announcement** + +1. The MC service server establishes the MBMS bearer(s) according to the procedures defined in 3GPP TS 23.468 [9]. Service description associated with the MBMS bearer(s) is returned from the BM-SC. +2. The MC service server provides service description information associated with the MBMS bearer to the MC client residing on non-3GPP devices via MC gateway UE. +3. The MC client sends the MC GW MBMS bearer announcement to the MC Gateway UE containing the MBMS bearer related information. +4. The MC Gateway UE stores the information associated with the TMGI(s). The MC Gateway UE uses the TMGI and other MBMS bearer related information to activate the monitoring of the MBMS bearer. +5. The MC Gateway UE that enters or is in the service area of at least one announced TMGI notifies to the MC client that it can receive data over MBMS by sending the MC GW MBMS listening status report. The MC GW MBMS listening status report also contains the details of the non-3GPP transport communication related parameters. The MC Gateway UE may choose to send the details of existing communication channel information as part of Non 3GPP transport channel establishment parameters IE if existing communication channel can be reused. +6. The MC client establishes the communication channel with the MC gateway UE based on the parameters received in step 5 to receive the MC service data from the MC gateway UE, if these parameters are not referring to any of the already established communication channel. The MC Gateway UE forwards the MC service data it received over the MBMS bearer from the MC service server to the MC client over this communication channel. +7. The MC Client sends the MBMS Listening Status Report to the MC Server indicating that it is able to receive the media over MBMS. + +#### 7.8.3.2 Procedure for handling MapGroupToBearer message + +Whenever the MC client detects that the data received from MC service server is MapGroupToBearer message and if the MC client participates in the group session or communication identified by the MapGroupToBearer message then it should inform the details contained in the MapGroupToBearer message to MC gateway UE. When the association of group call, MBMS bearer and the MC GW service ID of the MC client is known to the MC gateway UE, it can forward the data received over MBMS bearer accordingly. + +Figure 7.8.3.2-1 illustrates the procedure for handling the MapGroupToBearer message by the MC client and the MC gateway UE. + +Pre-conditions: + +1. The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE. +2. The MC client successfully completed service authorization via MC gateway UE. + +![Sequence diagram illustrating the handling of MapGroupToBearer message between MC Client, MC Gateway UE, and MC service Server.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MC Client (residing on non 3GPP device) + participant MC Gateway UE + participant MC service Server + + Note right of MC service Server: 1. MC service server sends MapGroupToBearer message over the MBMS Channel + MC service Server->>MC Gateway UE: 2. MC GW MBMS MapGroupToBearer Request + Note right of MC Gateway UE: 3. Maintains the association of GW MC Service ID and MBMS subchannel + MC Gateway UE->>MC Client: 4. MC GW MBMS MapGroupToBearer Response + Note left of MC Gateway UE: 5. Communication channel establishment to receive MC service group communication traffic + Note right of MC service Server: 6. DL media over MBMS for MC group communication + Note right of MC Gateway UE: 7. Checks the list of GW MC Service IDs associated with the MBMS subchannel for MC group communication + MC Gateway UE->>MC Client: 8. Forward the received media + +``` + +The sequence diagram shows the interaction between three entities: MC Client (residing on non 3GPP device), MC Gateway UE, and MC service Server. The process starts with the MC service Server sending a MapGroupToBearer message over the MBMS Channel to the MC Gateway UE. The MC Gateway UE then sends an MC GW MBMS MapGroupToBearer Request to the MC Client. The MC Gateway UE maintains the association of GW MC Service ID and MBMS subchannel. The MC Gateway UE sends an MC GW MBMS MapGroupToBearer Response to the MC Client. The MC Client establishes a communication channel to receive MC service group communication traffic. The MC service Server sends DL media over MBMS for MC group communication. The MC Gateway UE checks the list of GW MC Service IDs associated with the MBMS subchannel for MC group communication. Finally, the MC Gateway UE forwards the received media to the MC Client. + +Sequence diagram illustrating the handling of MapGroupToBearer message between MC Client, MC Gateway UE, and MC service Server. + +**Figure 7.8.3.2-1: Handling of MapGroupToBearer message** + +1. The MC service server sends a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MC service group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call. +2. If the MC client is participating in the MC group communication identified by the MapGroupToBearer message, it sends the details contained in the MapGroupToBearer message to the MC gateway UE through MC GW MapGroupToBearer request message. +3. The MC gateway UE on receiving the MC GW MapGroupToBearer Request message from the MC client it maintains the association between the GW MC Service ID and the corresponding MBMS sub channel. +4. The MC gateway UE sends the MC GW MapGroupToBearer response message to the MC client which contains the details of the non-3GPP transport communication related parameters. +5. The MC client establishes the communication channel with the MC gateway UE based on the parameters received in step 4 to receive the MC service group communication data from the MC gateway UE. +6. The MC service server sends the downlink media for the group communication session over the MBMS bearer. +7. The MC gateway UE checks which MC clients should receive the media of the MC group communication based on Step 3. +8. The MC gateway UE forwards the downlink media to the intended MC clients over the communication channel established as in step 5. + +#### 7.8.3.3 Procedure for MBMS bearer suspension notification + +The MC service server can choose to instruct some MC clients to send the MBMS bearer suspension report when notified by RAN. When the MC clients are residing on non-3GPP devices, MC gateway UE would be the one listening on the MBMS bearers. When RAN decides to suspend the MBMS bearer it indicates the MC gateway UE. MC gateway UE to notify the MC clients it is serving so that MC clients can report the same to the MC service server. This procedure is applicable only if the MC client is instructed to report the MBMS bearer suspension. Irrespective of whether the MC clients need to send the MBMS bearer suspension report to the MC service server, MC gateway can choose to notify the MC clients it is serving whenever RAN suspends the MBMS bearer. MC clients can then decide to send the MBMS bearer suspension report to the MC service server only if they are instructed by the MC service server. + +Figure 7.8.3.3-1 illustrates the procedure for MC clients residing on non-3GPP devices reporting the MC service server about the MBMS bearer suspension. + +![Sequence diagram for MBMS bearer suspension notification. Lifelines: MC client (residing on non 3GPP device), MC Gateway UE, Radio access network, MC service server. The sequence shows: 1. MC client received MBMS suspension reporting instruction from MC Service server; 2. RAN suspend MBMS; 3. MBMS suspension indication from RAN to MC Gateway UE; 4. MC GW MBMS bearer suspension indication from MC Gateway UE to MC client; 5. MBMS suspension report from MC client to MC service server.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +``` + +sequenceDiagram + participant MC client (residing on non 3GPP device) + participant MC Gateway UE + participant Radio access network + participant MC service server + + Note over MC client, MC service server: 1. MC client received MBMS suspension reporting instruction from MC Service server + Note over Radio access network: 2. RAN suspend MBMS + Radio access network->>MC Gateway UE: 3. MBMS suspension indication + MC Gateway UE->>MC client: 4. MC GW MBMS bearer suspension indication + MC client->>MC service server: 5. MBMS suspension report + +``` + +Sequence diagram for MBMS bearer suspension notification. Lifelines: MC client (residing on non 3GPP device), MC Gateway UE, Radio access network, MC service server. The sequence shows: 1. MC client received MBMS suspension reporting instruction from MC Service server; 2. RAN suspend MBMS; 3. MBMS suspension indication from RAN to MC Gateway UE; 4. MC GW MBMS bearer suspension indication from MC Gateway UE to MC client; 5. MBMS suspension report from MC client to MC service server. + +Figure 7.8.3.3-1: MBMS bearer suspension notification + +#### 7.8.3.4 Procedure for reporting MBMS bearer quality + +The MC Gateway UE listening on the MBMS bearer has to report the MBMS bearer quality to the MC clients so that MC clients can report the same to the MC service server. MC Gateway UE monitors an MBMS bearer to receive MC service media. Based on the received quality (e.g. radio level quality) the MC Gateway UE needs to inform the MC Clients which requested the MC Gateway UE to listen on MBMS bearer, whether it is able to receive the MC service media on the MBMS bearer with sufficient quality or not the MC Clients can inform the MC service server accordingly. + +Figure 7.8.3.4-1 illustrates the procedure for MC clients residing on non-3GPP devices reporting the MC service server about the MBMS bearer quality. + +Pre-conditions: + +1. There is an MBMS bearer activated and the MBMS bearer information is announced to the MC gateway UE. +2. The MC gateway UE is located in the MBMS broadcasting area +3. The MC gateway UE monitors SIB-13 (or SIB-20) and (SC-)MCCH to receive the modulation and coding scheme. +4. The MC gateway UE monitors the cell specific reference signal and when MBSFN transmission is used, the MBSFN specific reference signals. + +![Sequence diagram illustrating the reporting of MBMS bearer quality. The diagram shows four steps: 1. MBMS bearer quality determination (between MC Gateway UE and MC service Server), 2. MC GW MBMS Bearer Quality Report (from MC Gateway UE to MC Client), 3. MC Client sends the MBMS Listening Status Report to the MC service Server through MC Gateway UE, and 4. MC service server sends additional proposal.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant MC Client (residing on non 3GPP device) + participant MC Gateway UE + participant MC service Server + Note right of MC Gateway UE: 1. MBMS bearer quality determination + MC Gateway UE->>MC Client: 2. MC GW MBMS Bearer Quality Report + Note right of MC Client: 3. MC Client sends the MBMS Listening Status Report to the MC service Server through MC Gateway UE + Note right of MC service Server: 4. MC service server sends additional proposal + +``` + +Sequence diagram illustrating the reporting of MBMS bearer quality. The diagram shows four steps: 1. MBMS bearer quality determination (between MC Gateway UE and MC service Server), 2. MC GW MBMS Bearer Quality Report (from MC Gateway UE to MC Client), 3. MC Client sends the MBMS Listening Status Report to the MC service Server through MC Gateway UE, and 4. MC service server sends additional proposal. + +**Figure 7.8.3.4-1: Reporting MBMS bearer quality** + +1. The MC gateway UE follows the Step 1 of the procedure as described in 3GPP TS 23.280 [5] clause 10.7.3.6.2 for the MC service UE. Instead of reporting the bearer quality to the MC service server it has to inform all the MC clients which has asked the MC gateway UE to listen on the particular MBMS bearer. +2. If the MBMS bearer quality reaches a certain threshold, the MC gateway UE sends an MC GW MBMS Bearer Quality report to the MC Client. The threshold is used to define the MBMS listening status, which indicates if the MBMS bearer quality has been acceptable or not to receive a specific MC service media. If the MBMS bearer quality is mapped to a different MBMS reception quality level, the MC gateway UE may send an MBMS Bearer Quality report including the MBMS reception quality level to the MC Client. +3. The MC Client sends the MBMS listening status report to the MC Service server via MC Gateway UE containing the information received in the MC GW MBMS Bearer Quality report. +4. The MC service server may send additional proposal for measurements e.g. information about neighbouring MBMS bearers. This message may be an MBMS bearer announcement message. + +### 7.8.4 Solution Evaluation + +This solution provides additional information flows and procedures required to support MBMS transmissions for the MC service clients operating on non-3GPP devices and accessing the MC system through MC gateway UE. Changes required to support MBMS transmissions are confined to the interface between the MC service clients and the MC gateway UE. Existing information flows and procedures which are defined for supporting the MBMS transmissions for the MC service clients operating on a 3GPP devices remains unaltered and same is re-used for MC service clients operating on a non-3GPP devices. + +# 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: Functional Architecture for an MC gateway UE | Solution #1: Functional architecture | Clause 7.1.3 | None | +| Key issue #2: Authorisation for connection of non-3GPP devices with an MC gateway UE | Solution #2: Connection authorisation with the MC gateway UE | Clause 7.2.6 | None | +| | Solution #3: Connection authorisation with an MC server via an MC gateway UE | Clause 7.3.6 | None | +| | Solution #5: Connection authorisation for non-3GPP devices that do not host an MC client | Clause 7.5.6 | None | +| Key issue #3: Identification of MC service users behind an MC gateway UE residing on non-3GPP devices | Solution #4: Using IMS identities behind the MC gateway UE | Clause 7.4.3 | None | +| Key issue #4: MBMS support | Solution #1: Functional architecture | Clause 7.1.3 | None | +| | Solution #8: MBMS Support for MC clients residing on non 3GPP devices | Clause 7.8.4 | None | +| Key issue #5: User traffic handling | Solution #2: Connection authorisation with the MC gateway UE | Clause 7.2.6 | None | +| | Solution #3: Connection authorisation with an MC server via an MC gateway UE | Clause 7.3.6 | None | +| | Solution #7: Routing of data and signalling by the MC gateway UE | Clause 7.7.4 | None | +| Key issue #6: Use of multiple MC gateway UEs | Covered by solutions #1, #2, #3, #4 and #5 | Covered by the solution specific evaluation clauses | As stated by the specific solution | +| Key issue #7: 3GPP access network related location management by MC Clients | Solution #6: 3GPP access network related location information management | Clause 7.6.4 | None | + +# 9 Conclusions + +This technical report fulfills the objective to study solutions to satisfy the stage 1 requirements for a MC gateway UE function. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical communications. + +The results from the study will be considered for follow-up normative work in Rel-18 as follows: + +- 1) The functional architecture (clause 7.1) is used as starting point to develop a proper functional model to support the MC Gateway UE functionality. + +- 2) The solution connection authorisation with an MC server via an MC gateway UE (clause 7.3) will be used to define the authorisation procedure for an MC client hosted by a non-3GPP device. +- 3) The solution connection authorisation for non-3GPP devices that do not host an MC client (clause 7.5) will be used to define the authorisation procedure for an MC client which cannot be hosted by a non-3GPP device. +- 4) Option 2 of solution on using IMS identities behind the MC gateway UE (clause 7.4) will be used, where MC clients capable to host MC service clients use dedicated IMS subscriptions, and non-3GPP devices which cannot host an MC client make use of the IMS subscription provided by the serving MC gateway UE. +- 5) The solution 3GPP access network related location information management (clause 7.6) will be used to define the 3GPP access network related location management procedures for MC clients hosted by non-3GPP devices. +- 6) The solution MC client uses an own IP address which relies on framed routing (clause 7.7.3) will be used to describe the mechanism for routing of data and signalling by the MC gateway UE. +- 7) The solution MBMS Support for MC clients residing on non-3GPP devices (clause 7.8) will be used to support MBMS bearers for MC clients residing on non-3GPP devices without requiring any changes at the MC system side. + +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): Gateway UE requirements + +The gateway requirements are captured in 3GPP TS 22.179 [2] clause 4.5.4 (see clause A.1) and 3GPP TS 22.280 [3] clause 5.15 (see clause A.2). + +## A.1 Shareable McPTT UEs and gateway UEs + +The conceptual model for shareable McPTT UEs is that of a pool of UEs, each UE being interchangeable with any other, and users randomly choosing one or more UEs from the pool, each user for his temporary exclusive use. A shareable McPTT UE can be used by user who can gain access to the McPTT client application stored on it and can become an authenticated McPTT User. A shareable McPTT UE can serve only one McPTT User at a time. An McPTT User who signs into a shareable McPTT UE that is already in-use causes the sign-off of the previous McPTT User. + +An McPTT User can simultaneously have several active McPTT UEs, which, from an McPTT Service point of view, are addressable individually and/or collectively within the context of their association to the McPTT User. + +The conceptual model for a gateway UE is that of a UE capable of providing service to an McPTT User employing a non-3GPP device. A gateway UE is usable simultaneously by multiple McPTT Users. Unlike a shareable McPTT UE, if a new person enters his valid credentials towards signing in the McPTT Service, his successful signing in and becoming an McPTT User does not affect the initial McPTT Users already served by the gateway UE. + +A gateway UE is typically installed in a vehicle (e.g., a police car, fire truck) and has wired and/or wireless connections to various devices in use by the McPTT Users. + +A gateway UE differs functionally from a ProSe relay node. In the ProSe paradigm, the relay node and the devices served by it are all (ProSe enabled) 3GPP UEs and are "visible" to the 3GPP system as UEs. In the gateway UE paradigm, only the gateway UE is an 3GPP device and only it is "visible" at the 3GPP network layer. + +Figure A.1-1 shows schematically some of the relationships between McPTT Users and McPTT UEs. + +![Figure A.1-1: Relationships between McPTT Users and McPTT UEs. The diagram is split into two halves by a vertical dashed line. The left half, labeled 'Application Function', contains a box 'McPTT Application' on the far left. Arrows point from this box to four boxes: 'UserA', 'UserB', 'UserC', and 'UserD'. Above 'UserA' is the text 'User with multiple UEs' in blue. The right half, labeled 'LTE Transport', contains five boxes: 'UE0', 'UE1', 'UE2', 'UE3' (labeled 'Gateway UE' in green), and 'UE4'. Arrows point from 'UserA' to 'UE0', 'UE1', and 'UE2'. Arrows point from 'UserB' to 'UE2'. Arrows point from 'UserC' to 'UE3'. Arrows point from 'UserD' to 'UE4'. All five UE boxes have arrows pointing to a single box on the far right labeled 'LTE EPS'.](3621e1493d508bd789fec58ba8be9a40_img.jpg) + +Figure A.1-1: Relationships between McPTT Users and McPTT UEs. The diagram is split into two halves by a vertical dashed line. The left half, labeled 'Application Function', contains a box 'McPTT Application' on the far left. Arrows point from this box to four boxes: 'UserA', 'UserB', 'UserC', and 'UserD'. Above 'UserA' is the text 'User with multiple UEs' in blue. The right half, labeled 'LTE Transport', contains five boxes: 'UE0', 'UE1', 'UE2', 'UE3' (labeled 'Gateway UE' in green), and 'UE4'. Arrows point from 'UserA' to 'UE0', 'UE1', and 'UE2'. Arrows point from 'UserB' to 'UE2'. Arrows point from 'UserC' to 'UE3'. Arrows point from 'UserD' to 'UE4'. All five UE boxes have arrows pointing to a single box on the far right labeled 'LTE EPS'. + +Figure A.1-1: Relationships between McPTT Users and McPTT UEs + +## A.2 Gateway requirements + +[R-5.15-001] The MCX Service system shall be accessible via gateway MCX UEs by MCX Users. + +[R-5.15-001a] The MCX Service system shall provide a mechanism to uniquely identify a gateway MCX UE. + +[R-5.15-002] Gateway MCX UEs shall ensure that the content of communications between the MCX Service System and an MCX User attached to the gateway MCX UEs is unaltered. + +[R-5.15-003] Gateway MCX UEs shall handle the communication traffic attributes, e.g. priority and QoS, of an MCX User attached to a gateway MCX UE independently of other MCX Users concurrently attached to the same gateway MCX UE. + +[R-5.15-004] Multiple Gateway MCX UEs shall be able to operate within the same area (e.g., site of an incident or accident, overlapping coverage, adjacent cells, etc.). + +[R-5.15-005] MCX Users shall be able to select gateway MCX UEs, in case multiple, accessible gateway MCX UEs are available. + +[R-5.15-006] An MCX User shall be able to access multiple gateway MCX UEs simultaneously from a single device while restricting a MCX Service to one gateway (e.g., MCPTT on gateway UE 1, MCData and MCVideo on gateway UE 2). + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | New version | +| 2020-05 | SA6#37-e | | | | | TR skeleton | 0.0.0 | +| 2020-06 | SA6#37-e | | | | | S6-200655, S6-200656, S6-200657 | 0.0.1 | +| 2020-08 | SA6#38-e | | | | | S6-201195, S6-201196, S6-201257, S6-201198, S6-201199, S6-201200 | 0.1.0 | +| 2020-10 | SA6#39-BIS-e | | | | | S6-201738, S6-201888, S6-201889, S6-201890, S6-202022 | 0.2.0 | +| 2020-11 | SA6#40-e | | | | | S6-202138, S6-202236; S6-202237, S6-202238, S6-202239 | 0.3.0 | +| 2021-03 | SA6#42-e | | | | | S6-210401, S6-210410, S6-210411, S6-210413, S6-210415, S6-210416, S6-210582, S6-210583, S6-210584, S6-210585 | 0.4.0 | +| 2021-06 | SA6#43-e | | | | | S6-211184, S6-211185, S6-211186, S6-211187, S6-211188, S6-211189, S6-211190, S6-211191, S6-211222, S6-211394, S6-211413, S6-211414 | 0.5.0 | +| 2021-06 | SA#92-e | SP-210475 | | | | Presentation for information at SA#92-e | 1.0.0 | +| 2021-07 | SA6#44-e | | | | | S6-211596, S6-211598, S6-211621, S6-211624, S6-211733, S6-211748, S6-211773, S6-211790 | 1.1.0 | +| 2021-09 | SA6#45-e | | | | | S6-211892, S6-211893, S6-211919, S6-211921, S6-212059, S6-212106, S6-212143 | 1.2.0 | +| 2021-09 | SA#93-e | SP-210949 | | | | Presentation for approval at SA#93-e | 2.0.0 | +| 2021-09 | SA#93-e | SP-210949 | | | | MCC Editorial update for publication after TSG SA approval (SA#93) | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-85/raw.md b/raw/rel-18/23_series/23700-85/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8aee18b791c95a5f33895f9a847cb2bcbdacc58b --- /dev/null +++ b/raw/rel-18/23_series/23700-85/raw.md @@ -0,0 +1,5414 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of 5G User Equipment (UE) policy (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 + +## **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 + +--- + +<http://www.3gpp.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. + +© 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 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions of terms and abbreviations ..... | 11 | +| 3.1 Terms..... | 11 | +| 3.2 Abbreviations ..... | 11 | +| 4 Architectural Assumptions and Principles..... | 11 | +| 5 Key Issues ..... | 11 | +| 5.1 Key Issue #1: URSP in VPLMN..... | 11 | +| 5.1.1 Description ..... | 11 | +| 5.2 Key Issue #2: 5GC awareness of URSP enforcement..... | 12 | +| 5.2.1 Description ..... | 12 | +| 5.3 Key Issue #3: Provision consistent URSP to UE across 5GS and EPS ..... | 12 | +| 5.3.1 Description ..... | 12 | +| 5.4 Key Issue #4: Support standardized and operator-specific traffic categories in URSP ..... | 12 | +| 5.4.1 Description ..... | 12 | +| 5.X Key Issue #X: <Key Issue Title> ..... | 13 | +| 5.X.1 Description ..... | 13 | +| 6 Solutions..... | 14 | +| 6.0 Mapping of Solutions to Key Issues ..... | 14 | +| 6.1 Solution #1: Usage of application guidance for URSP rules determination mechanisms ..... | 14 | +| 6.1.1 Description ..... | 14 | +| 6.1.2 Procedures ..... | 15 | +| 6.1.3 Impacts on Existing Nodes and Functionality..... | 15 | +| 6.2 Solution #2: VPLMN influencing URSP rules in an HPLMN ..... | 15 | +| 6.2.1 Description ..... | 15 | +| 6.2.2 Procedures ..... | 16 | +| 6.2.2.1 VPLMN AF guidance for URSP rule creation at an HPLMN ..... | 16 | +| 6.2.2.2 UE behaviour on applying a URSP rule with a PLMN validity condition in route selection descriptor ..... | 18 | +| 6.2.3 Impacts on services, entities and interfaces..... | 18 | +| 6.3 Solution #3: URSP provisioning and updating in roaming..... | 18 | +| 6.3.1 Description ..... | 18 | +| 6.3.2 UE Policy Association Establishment with VPLMN assistant information ..... | 19 | +| 6.3.3 UE Policy Association modification with VPLMN assistant information..... | 20 | +| 6.3.4 Support routing of the same application traffic with different URSP rules in different PLMNs..... | 20 | +| 6.3.4.1 URSP enhancement with including the PLMN ID in TD (Option#1)..... | 20 | +| 6.3.4.2 URSP dedicated to VPLMN (Option#2) ..... | 21 | +| 6.3.5 Impacts on Existing Nodes and Functionality..... | 21 | +| 6.4 Solution #4: URSP decision with V-PCF involvement ..... | 21 | +| 6.4.1 Description ..... | 21 | +| 6.4.2 Procedure..... | 22 | +| 6.4.3 Impacts on services, entities and interfaces..... | 22 | +| 6.5 Solution #5: URSP determination based on service parameter obtained from VPLMN ..... | 23 | +| 6.5.1 Description ..... | 23 | +| 6.5.2 Procedures ..... | 24 | +| 6.5.2.1 Procedure for URSP determination based on service parameter obtained from VPLMN ..... | 24 | +| 6.5.3 Impacts on services, entities and interfaces..... | 25 | +| 6.6 Solution #6: Solution for URSP in VPLMN with PLMN domain indication..... | 26 | +| 6.6.1 General ..... | 26 | +| 6.6.2 Functional descriptions..... | 26 | +| 6.6.3 Procedures ..... | 27 | +| 6.6.4 Impacts on services, entities, and interfaces..... | 27 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------|----| +| 6.7 | Solution #7: URSP Compliance Verification..... | 27 | +| 6.7.1 | Description ..... | 27 | +| 6.7.2 | Procedures ..... | 31 | +| 6.7.2.1 | Provisioning of URSP Compliance Verification in Registration procedure ..... | 31 | +| 6.7.2.2 | URSP Compliance Verification in PDU Session Establishment procedure..... | 32 | +| 6.7.3 | Impacts on services, entities and interfaces..... | 34 | +| 6.8 | Solution #8: URSP Rule Precedence reporting for awareness of URSP enforcement ..... | 35 | +| 6.8.1 | Description ..... | 35 | +| 6.8.2 | Procedures ..... | 35 | +| 6.8.3 | Impacts on services, entities and interfaces..... | 36 | +| 6.9 | Solution #9: Per-PDU session awareness of URSP enforcement ..... | 37 | +| 6.9.1 | Description ..... | 37 | +| 6.9.2 | Procedures ..... | 37 | +| 6.9.3 | Impacts on services, entities and interfaces..... | 39 | +| 6.10 | Solution #10: Network based URSP rules enforcement feedback..... | 39 | +| 6.10.1 | Description ..... | 39 | +| 6.10.1.1 | Network based URSP rules enforcement verification without UE assistance..... | 39 | +| 6.10.1.2 | Network based URSP rules enforcement verification with UE assistance..... | 40 | +| 6.10.2 | Procedure ..... | 40 | +| 6.10.2.1 | Network based URSP rules enforcement verification without UE assistance..... | 40 | +| 6.10.2.2 | Network based URSP rules enforcement verification with UE assistance..... | 42 | +| 6.10.3 | Impacts on services, entities and interfaces..... | 44 | +| 6.11 | Solution #11: 5GC awareness of URSP recognition by UE ..... | 44 | +| 6.11.1 | Description ..... | 44 | +| 6.11.2 | Procedures ..... | 45 | +| 6.11.3 | Impacts on services, entities and interfaces..... | 45 | +| 6.12 | Solution #12: URSP rule enforcement validation via gating control..... | 46 | +| 6.12.1 | Description ..... | 46 | +| 6.12.2 | Procedure ..... | 46 | +| 6.12.3 | Impacts on existing Functions..... | 48 | +| 6.13 | Solution #13: URSP enforcement via PDU Session authorization/authentication when UE associating with application..... | 48 | +| 6.13.1 | Description ..... | 48 | +| 6.13.2 | Procedures ..... | 50 | +| 6.13.3 | Impacts on services, entities and interfaces..... | 51 | +| 6.14 | Solution #14: 5GC awareness of URSP rule evaluation and verification of network slice usage ..... | 51 | +| 6.14.1 | Description ..... | 51 | +| 6.14.2 | Procedures ..... | 52 | +| 6.14.2.1 | Overall procedure ..... | 52 | +| 6.14.2.2 | Application registration ..... | 53 | +| 6.14.3 | Impacts on services, entities and interfaces..... | 53 | +| 6.15 | Solution #15: UE URSP enforcement validation by the network ..... | 54 | +| 6.15.1 | Description ..... | 54 | +| 6.15.2 | Procedures ..... | 54 | +| 6.15.3 | Impacts on services, entities and interfaces..... | 55 | +| 6.16 | Solution #16: URSPs into PCO for EPC..... | 55 | +| 6.16.1 | Description ..... | 55 | +| 6.16.1.1 | Use cases and scenarios ..... | 55 | +| 6.16.1.2 | Background: URSP provisioning to a UE in 5GS ..... | 56 | +| 6.16.1.3 | How to provision URSP to a UE in EPC..... | 57 | +| 6.16.1.4 | Deployments where the PCF for the PDU session and the PCF for the UE are different PCFs ..... | 57 | +| 6.16.2 | Procedures ..... | 59 | +| 6.16.2.1 | Initial Attach procedure in EPC..... | 59 | +| 6.16.2.2 | URSP update initiated by PCF..... | 60 | +| 6.16.2.3 | Procedures for deployments where the PCF for the PDU session and the PCF for the UE are different PCFs ..... | 61 | +| 6.16.2.3.1 | Initial Attach Procedure in EPC ..... | 61 | +| 6.16.2.3.2 | URSP update initiated by PCF ..... | 62 | +| 6.16.2.3.3 | Handover from 5GS to EPC..... | 62 | +| 6.16.3 | Impacts ..... | 64 | +| 6.17 | Solution #17: Indication of applicability of URSP to UE in EPS..... | 65 | +| 6.17.1 | Description ..... | 65 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------|----| +| 6.17.2 | Procedures ..... | 66 | +| 6.17.2.1 | URSP provisioning with EPS applicability indication ..... | 66 | +| 6.17.2.2 | Evaluation of URSP rules with EPS applicability indication ..... | 67 | +| 6.17.3 | Impacts on services, entities and interfaces..... | 67 | +| 6.18 | Solution #18: Provisioning consistent URSP to UE across 5GS and EPS for Collocated PCF | | +| | Deployment ..... | 67 | +| 6.18.1 | Description ..... | 67 | +| 6.18.2 | Procedures ..... | 68 | +| 6.18.2.1 | UE triggered UE Policy provisioning procedure in EPS ..... | 68 | +| 6.18.2.2 | PCF triggered UE Policy provisioning procedure in EPS ..... | 68 | +| 6.18.3 | Impacts on services, entities and interfaces..... | 69 | +| 6.19 | Solution #19: Provision of URSP to UE when the UE attaches in the EPS ..... | 69 | +| 6.19.1 | Introduction ..... | 69 | +| 6.19.2 | Procedures ..... | 70 | +| 6.20 | Solution #20: URSP delivery for the UE in EPS ..... | 71 | +| 6.20.1 | Description ..... | 71 | +| 6.20.2 | Procedures ..... | 73 | +| 6.20.2.1 | UE Policy delivery procedure initiated by the UE in EPS ..... | 73 | +| 6.20.2.2 | UE Policy delivery procedure initiated by the PCF..... | 74 | +| 6.20.2.3 | URSP delivery over EPS Indication in 5GS ..... | 74 | +| 6.20.2.4 | 5GS to EPS Handover using N26 interface ..... | 75 | +| 6.20.2.5 | 5GS to EPS Idle mode mobility using N26 interface ..... | 76 | +| 6.20.2.6 | Relocate an established UE Policy Association to SM-PCF ..... | 76 | +| 6.20.3 | Impacts on services, entities and interfaces..... | 77 | +| 6.21 | Solution #21: Traffic Category with existing mechanism ..... | 78 | +| 6.21.1 | Description ..... | 78 | +| 6.21.2 | Procedures ..... | 79 | +| 6.21.3 | Impacts on services, entities and interfaces..... | 79 | +| 6.22 | Solution #22: UE provisioned/configured with a mapping of application traffic to traffic categories ..... | 79 | +| 6.22.1 | Description ..... | 79 | +| 6.22.2 | Procedures ..... | 80 | +| 6.22.2.1 | Association of application traffic to a Traffic Category ..... | 80 | +| 6.22.2.2 | Enhancing URSP rule with a Traffic Category Traffic Descriptor..... | 81 | +| 6.22.3 | Impacts on services, entities and interfaces..... | 82 | +| 6.23 | Solution #23: Support standardized and operator-specific traffic categories in URSP ..... | 83 | +| 6.23.1 | Description ..... | 83 | +| 6.23.2 | Procedures ..... | 84 | +| 6.23.3 | Impacts on services, entities and interfaces..... | 84 | +| 6.24 | Solution #24: Introduction of Traffic Category into URSP rules ..... | 84 | +| 6.24.1 | Description ..... | 84 | +| 6.24.2 | Procedure ..... | 85 | +| 6.24.3 | Impacts on services, entities and interfaces..... | 86 | +| 6.25 | Solution #25: Support standardized and operator-specific traffic categories in URSP ..... | 86 | +| 6.25.1 | Description ..... | 86 | +| 6.25.2 | Procedures ..... | 86 | +| 6.25.3 | Impacts on Existing Nodes and Functionality..... | 87 | +| 6.26 | Solution #26: Traffic categories based on 5G QoS characteristics ..... | 87 | +| 6.26.1 | Description ..... | 87 | +| 6.26.1.1 | Traffic categories based on service type..... | 87 | +| 6.26.1.2 | Traffic categories based on Traffic characteristics ..... | 88 | +| 6.26.2 | Procedures ..... | 88 | +| 6.26.3 | Impacts on services, entities and interfaces..... | 88 | +| 6.27 | Solution #27: URSP provisioning and updating in roaming ..... | 89 | +| 6.27.1 | Description ..... | 89 | +| 6.27.1.1 | Characteristics of the solution..... | 90 | +| 6.27.2 | Procedure for UE Policy Association Establishment with VPLMN provided URSP Rules ..... | 91 | +| 6.27.3 | PDU Session establishment for LBO ..... | 92 | +| 6.27.4 | AF guidance for URSP determination..... | 92 | +| 6.27.5 | Impacts on Existing Nodes and Functionality..... | 93 | +| 6.28 | Solution #28: Provisioning VPLMN URSP ..... | 93 | +| 6.28.1 | Description ..... | 93 | +| 6.28.2 | Procedures ..... | 94 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.28.2.1 | Provisioning VPLMN URSP rules for roaming scenario ..... | 94 | +| 6.28.2.2 | Application Guidance of URSP determination in VPLMN..... | 98 | +| 6.28.3 | Impacts on services, entities and interfaces..... | 100 | +| 6.29 | Solution #29: Using Location Criteria to Control Routing of Application Traffic..... | 100 | +| 6.29.1 | Description ..... | 100 | +| 6.29.2 | Procedures ..... | 101 | +| 6.29.3 | Impacts on services, entities and interfaces..... | 101 | +| 6.30 | Solution #30: Leveraging NWDAF to determine UEs that enforce URSP rules incorrectly. .... | 101 | +| 6.30.1 | Description ..... | 101 | +| 6.30.2 | Input Data ..... | 103 | +| 6.30.3 | Output Analytics..... | 103 | +| 6.30.4 | Procedures ..... | 103 | +| 6.30.5 | Impacts on services, entities and interfaces..... | 105 | +| 6.31 | Solution #31: New URSP Notification Component..... | 105 | +| 6.31.1 | Description ..... | 105 | +| 6.31.2 | Procedures ..... | 107 | +| 6.31.2.1 | URSP Notification procedure flow ..... | 107 | +| 6.31.2.2 | Detail of UE policy delivery and user consent ..... | 108 | +| 6.31.2.3 | URSP Rule rejection for pre-configured URSP rules or already-accepted URSP rules (e.g. change in privacy/security settings)..... | 109 | +| 6.31.2.4 | Example of PCF actions on receiving URSP Notifications..... | 110 | +| 6.31.2.4.1 | Example action: Storage of received notification on the UDR linked to the triggered UE ..... | 111 | +| 6.31.2.4.2 | Example action: Notification via Event exposure to other NFs..... | 113 | +| 6.31.2.4.3 | Example action: Notification of Application owner via NEF ..... | 114 | +| 6.31.3 | Impacts on Existing Nodes and Functionality..... | 115 | +| 6.32 | Solution #32: Application Detection using Domain Descriptor ..... | 116 | +| 6.32.1 | Description ..... | 116 | +| 6.32.2 | Procedures ..... | 117 | +| 6.32.2.1 | Procedure of application detection for domain (e.g. FQDN) traffic descriptor..... | 117 | +| 6.32.3 | Impacts on services, entities and interfaces..... | 118 | +| 6.33 | Solution #33: Consistent URSP Provisioning across 5GS and EPS ..... | 119 | +| 6.33.1 | Description ..... | 119 | +| 6.33.1.1 | Use Cases and Scenarios..... | 119 | +| 6.33.1.2 | Provision URSP to a UE in EPC ..... | 120 | +| 6.33.1.3 | Handle the UE Policy Association during mobility from 5GS to EPS with N26 ..... | 120 | +| 6.33.2 | Procedures ..... | 121 | +| 6.33.2.1 | UE Policy provisioning procedure with explicit URSP Support Indication in EPS ..... | 121 | +| 6.33.2.2 | PCF triggered UE Policy provisioning procedure ..... | 123 | +| 6.33.2.3 | 5GS to EPS Handover using N26 interface ..... | 124 | +| 6.33.2.4 | 5GS to EPS Idle mode mobility using N26 interface ..... | 125 | +| 6.33.2.5 | SM Policy and UE Policy Association Update after 5GS to EPS mobility using N26 interface ..... | 126 | +| 6.33.2.6 | UE Policy Association handling after EPS to 5GS mobility ..... | 126 | +| 6.33.3 | Impacts on services, entities and interfaces..... | 126 | +| 6.34 | Solution #34: Provisioning UE policy in EPS via N3IWF ..... | 127 | +| 6.34.1 | Description ..... | 127 | +| 6.34.2 | Procedures ..... | 128 | +| 6.34.3 | Impacts on services, entities and interfaces..... | 129 | +| 6.35 | Solution #35: Support standardized and operator-specific traffic categories using existing URSP traffic descriptors ..... | 129 | +| 6.35.1 | Description ..... | 129 | +| 6.35.2 | Procedures ..... | 130 | +| 6.35.3 | Impacts on services, entities and interfaces..... | 131 | +| 6.X | Solution #X: <Solution Title>..... | 131 | +| 6.X.1 | Description ..... | 131 | +| 6.X.2 | Procedures ..... | 131 | +| 6.X.3 | Impacts on services, entities and interfaces..... | 131 | +| 7 | Overall Evaluation ..... | 131 | +| 7.1 | Evaluation of solutions to KI#1 ..... | 131 | +| 7.1.1 | How to identify PLMN specific URSP Rules ..... | 132 | +| 7.1.2 | Which PLMN determines the VPLMN specific URSP Rules ..... | 135 | +| 7.2 | Evaluation on Solutions for KI#2..... | 139 | + +| | | | +|--------------------------------------|-------------------------------------------------------------------------|------------| +| 7.3 | Evaluation on Solutions for KI#3..... | 140 | +| 7.4 | Evaluation on Solutions for KI#4..... | 142 | +| 8 | Conclusions..... | 145 | +| 8.1 | Conclusions on KI#1..... | 146 | +| 8.1.1 | General ..... | 146 | +| 8.1.2 | Conclusions on the how to identify PLMN specific URSP Rules ..... | 146 | +| 8.1.3 | Conclusions on which PLMN determines the VPLMN specific URSP Rules..... | 146 | +| 8.1.4 | Conclusions on Re-evaluation Triggers ..... | 147 | +| 8.2 | Conclusion on KI#2 ..... | 147 | +| 8.3 | Conclusion on KI#3: ..... | 148 | +| 8.4 | Conclusion on KI#4 ..... | 148 | +| <b>Annex A: Change history .....</b> | | <b>150</b> | + +# 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 + +This study focuses on key issue description, solution and conclusion on the enhancement of 5G UE Policy aspect by covering following objectives: + +- URSP rule provisioning and updating procedures for home-routed and LBO roaming scenario, while keeping the existing framework of policy control based on HPLMN. +- Investigate whether and how the network can be made aware when the UE enforces URSP rule and investigate whether and what actions the 5G network can perform. +- Investigate if enhancements are needed for provisioning UE with consistent URSP across 5GC and EPC, and study the mechanism if needed. +- Investigate how to support standardized and operator-specific traffic categories in the traffic descriptor of URSP. + +# --- 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 (5GS); Stage 2". +- [4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [5] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [6] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [7] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [9] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3". +- [10] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [11] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [12] 3GPP TS 23.304: "Proximity based Service (ProSe) in the 5G System (5GS); Stage 2". +- [13] 3GPP TS 32.421: "Telecommunication Management; Subscriber and equipment trace; Trace concepts and requirements". +- [14] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane nodes". +- [15] 3GPP TS 29.519: "5G System; Usage of the Unified Data Repository Service for Policy Data, Application Data and Structured Data for Exposure; Stage 3". + +# --- 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]. + +## 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]. + +# --- 4 Architectural Assumptions and Principles + +**Editor's note:** This clause will document any architectural assumptions and principles. + +Rel-15, Rel-16 and Rel-17 specified UE Policy mechanism in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] will be used as baseline for this study. + +No new interface in EPC will be defined to solve the issue of consistent URSP provisioning. + +For the objective to investigate if enhancements are needed for provisioning UE with consistent URSP across 5GC and EPC, and study the mechanism if needed, the following applies: + +- Solutions using the ePCO to transfer URSP Rules via EPC assumes that the UE is registered in an MME supporting 5GS interworking, and as such transferring of ePCO in the PDN Connection signalling is supported by the MME and SGW. It is also assumed that the SMF+PGW-C selected for a PDN Connection established to a specific APN supports UE policy delivery service (i.e. SMF+PGW-C supports sending and receiving of a UE Policy Container to/from the UE). + +# --- 5 Key Issues + +## 5.1 Key Issue #1: URSP in VPLMN + +### 5.1.1 Description + +This Key Issue will study URSP rule provisioning and updating procedures in roaming scenario, while keeping backward compatibility with the existing framework of policy control based on HPLMN. In particular: + +- Whether the HPLMN needs any information from the VPLMN to generate URSP Rules in roaming. If so, which information and how to provide it. +- How to provide URSP Rules in roaming to the UE. In particular, how the HPLMN and VPLMN are involved in such procedure. +- Whether and how to support URSP enhancements to support routing of the application traffic with different URSP rules in different PLMNs. + +## 5.2 Key Issue #2: 5GC awareness of URSP enforcement + +### 5.2.1 Description + +This key issue address WT#4: whether and how the network can be made aware when the UE enforces URSP rule for a traffic and investigate whether and what actions the 5G network can perform. + +The following aspects will be studied: + +- Whether and how the 5GC can be made aware whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on the URSP rule provisioned by 5GC. +- Whether there are any actions the 5GS can take after 5GC is aware whether the UE enforces a URSP rule for specific application traffic or not. If any, what action 5GC should take? + +NOTE: User privacy needs to be considered when defining solution (e.g. 5GC will know if a user started/stopped "any" application). + +## 5.3 Key Issue #3: Provision consistent URSP to UE across 5GS and EPS + +### 5.3.1 Description + +The UE may use the route selection component (e.g. DNN) in a URSP rule in EPS, but when the URSP rule is updated at network side, there is no way to provision the URSP rule to UE in EPS based on current design. The different scenarios of provisioning the UE with URSP in EPS will be defined, according to the existing Rel-17 TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] TSs and considered in order to configure the UE with consistent URSP across EPS and 5GS. This key issue is to study how to support provisioning of URSP to a UE that is consistent across 5GC and EPC, including: + +- Identify the use cases and scenarios where the UE may need URSP that is consistent across 5GC and EPC. +- Study whether there are any issues and gaps in the existing URSP mapping mechanism described in clause 5.17.1.2 of TS 23.501 [2], if so, identify them and propose solutions. +- Whether, when and how to provision the URSP to UE when served by the EPC and ANDSF is not deployed in the network. For the Rel-15 UEs not supporting the URSP mapping in EPS, whether the URSP updating/provisioning to such UEs in EPS should be supported. + +NOTE: No new interface will be defined in EPC to solve this key issue. + +## 5.4 Key Issue #4: Support standardized and operator-specific traffic categories in URSP + +### 5.4.1 Description + +Based on GSMA requirement (LS in S2-2105356), SA WG2 will investigate how to support traffic categories in the traffic descriptor of URSP. Following aspects will be considered: + +- Definition of Traffic Category use cases and how to support both standardized traffic categories and MNO-specific traffic categories. If standardized values for traffic categories are defined, what are the various traffic categories that need to be standardized. +- Whether the existing URSP design can be used to support the traffic category. If not, how to support traffic category in the traffic descriptor of a URSP rule. + +NOTE 1: Traffic categories should support mechanisms that enable the UE to uniquely identify and categorize the traffic generated by any active application in a consistent manner across UE implementations. + +NOTE 2: 3GPP will coordinate with GSMA for the definition of traffic category, its use cases and the traffic categories GSMA may want to standardize. + +It is assumed to have following standardised traffic categories considering the requirement from GSMA: + +- IMS traffic category; voice, video and SMS over IMS, as well as RCS, are included in this traffic category. +- Internet traffic category. +- IoT and machine to machine type of traffic. +- On demand downlink streaming. +- On demand uplink streaming. +- Vehicular communications, including vehicle-to-infrastructure, vehicle-to-network, vehicle-to-vehicle, vehicle-to-pedestrian, vehicle-to-device and vehicle-to-grid. +- Real time interactive traffic. +- Unified communications traffic; instant messaging, VoIP and video collaboration are included in this category. +- Background traffic; comprising processes for e.g. firmware/software updates over the air. +- Location-based traffic. +- Critical Communications. + +## 5.X Key Issue #X: <Key Issue Title> + +### 5.X.1 Description + +**Editor's note:** This clause provides a description of the key issue. + +# 6 Solutions + +## 6.0 Mapping of Solutions to Key Issues + +Table 6.0-1: Mapping of Solutions to Key Issues + +| Solutions | Key Issues | | | | +|-----------|------------|---|---|---| +| | 1 | 2 | 3 | 4 | +| 1 | X | | | | +| 2 | X | | | | +| 3 | X | | | | +| 4 | X | | | | +| 5 | X | | | | +| 6 | X | | | | +| 7 | | X | | | +| 8 | | X | | | +| 9 | | X | | | +| 10 | | X | | | +| 11 | | X | | | +| 12 | | X | | | +| 13 | | X | | | +| 14 | | X | | | +| 15 | | X | | | +| 16 | | | X | | +| 17 | | | X | | +| 18 | | | X | | +| 19 | | | X | | +| 20 | | | X | | +| 21 | | | | X | +| 22 | | | | X | +| 23 | | | | X | +| 24 | | | | X | +| 25 | | | | X | +| 26 | | | | X | +| 27 | X | | | | +| 28 | X | | | | +| 29 | X | | | | +| 30 | | X | | | +| 31 | | X | | | +| 32 | | X | | | +| 33 | | | X | | +| 34 | | | X | | +| 35 | | | | X | + +## 6.1 Solution #1: Usage of application guidance for URSP rules determination mechanisms + +### 6.1.1 Description + +Currently when a UE is served by a network other than its home operator (i.e. VPLMN) the serving network cannot influence the determination of URSP. It would be useful for the serving network to be able to influence the determination of URSP for example in LBO case where the VPLMN may support dedicated DNN(s) for Edge applications. + +A solution is to leverage, clause 6.6 of TS 23.548 [5] "Support of AF Guidance to PCF Determination of Proper URSP Rules" and clause 4.15.6.10 of TS 23.502 [3] "Application guidance for URSP rules determination mechanisms" as defined for Rel-17. + +An AF from the VPLMN provides the VPLMN specific URSP information (e.g. DNN and S-NSSAI to be used for an application traffic etc.) (according to clause 6.6 of TS 23.548 [5] and clause 4.15.6.10 of TS 23.502 [3]); this indication can be leveraged by the PCF of the HPLMN to (if authorized by HPLMN) provide dedicated URSP rules applicable to relevant users of the HPLMN when they are roaming in that VPLMN. These URSP may have a validity condition (e.g. Time Window and/or Location Criteria) corresponding to the VPLMN. The location validity condition may be provided by the AF from VPLMN that contains the list of TA(s) or Cell Id(s) of the VPLMN. + +NOTE 1: The PLMN ID in the Policy Section identified by the Policy Section Identifier (PSI) is used to determine which PLMN owns the policy section. A PCF can provide UE policies for policy sections that are associated with the PLMN that the PCF belongs to i.e. a PCF from HPLMN cannot provide UE policies for a Policy Section list that belongs to a VPLMN. + +The H-PCF may, based on local policies, determine whether to always send the URSP rules immediately to the UE or to send these rules only when the UE is served by the corresponding serving PLMN, e.g. waiting to be triggered from a V-PCF of that PLMN in step 3 of clause 4.6.11 of TS 23.502 [3]. + +The PCF of the HPLMN when it sends such URSP update to a UE, needs, as for Rel-17, to ensure that the DNN, S-NSSAI provided in the URSP rules sent to the UE is allowed in UDM subscription even when the UE is roaming in that VPLMN. + +NOTE 2: This solution could also apply in FS\_EDGE\_Ph2. + +NOTE 3: This solution is applicable only when HPLMN supports dynamic PCC and application guidance for URSP rules determination mechanisms. + +### 6.1.2 Procedures + +The solution reuses existing procedures. + +### 6.1.3 Impacts on Existing Nodes and Functionality + +- The VPLMN and the HPLMN as part of the roaming agreement need to ensure that the VPLMN AF can reach the NEF of the HPLMN to use the API defined in clause 4.15.6.10 of TS 23.502 [3] "Application guidance for URSP rules determination mechanisms" +- UDM to include the DNN, S-NSSAI of the VPLMN in the list of Subscribed S-NSSAIs and to allow the DNN, S-NSSAI to work in LBO mode in the user subscription. + +## 6.2 Solution #2: VPLMN influencing URSP rules in an HPLMN + +### 6.2.1 Description + +**Editor's note:** This clause will describe the solution principles and architecture assumptions for corresponding key issue(s) which should be explicitly stated. (Sub) clause(s) may be added to capture details. + +To support the objectives of KI#1 it is proposed to re-use the procedure defined in Release-17 on application guidance for URSP rule creation with the additional enhancement on allowing an Application Function in a VPLMN to influence URSP rules creation at an HPLMN. The AF in the visited PLMN provides the service information re-using the service specific information provisioning procedure described in TS 23.502 [3] with the following addition: + +- The AF includes an indication to apply this rule only when UEs register to a specific PLMN. + +The trigger for the AF request could be due to: + +- AF service provider of a VPLMN wishes to use specific DNN/S-NSSAI handling for roaming UEs +- A trigger by the Network Slices Capability Enablement Server defined in TS 23.434 [6]. The NSCE server may be located in an AF. The NSCE server may receive from an NSCE client (located in a UE) a network/slice notification remapping for an application based on configuration provided by the NSCE server to the NSCE client in the UE. + +The NEF stores the AF request information in the UDR in the "Application Data" field within the Service Specific Information Data Subset together with the assigned Transaction Reference ID (provided by the AF). + +When the PCF receives the updated subscription information from the UDR the PCF derives updated URSP rules for a UE (or any UE) including in the URSP rule information indicating to the UEs to apply this URSP rules only when routing traffic via a specific PLMN. This is supported by enhancing the Route Selection Descriptor of the URSP rule including a PLMN identity. There are several options on how the RSD component can be enhanced: + +- **Option 1:** New validation criteria in RSD. +- **Option 2:** Use existing validation criteria i.e. the location criteria, where the location could be set to e.g. 3GPP location"={PLMN,location}. +- **Option 3:** Include a new RSD parameter (i.e. not validation criteria) to identify the PLMN. + +If the UE determines an applicable URSP rule for detected application traffic then the UE considers the Route Selection Descriptor valid if the PLMN identity of the validity condition matches the PLMN identity of the registered PLMN. The new RSD component that include PLMN identity are set by the PCF as higher priority so that the UE evaluates the first. + +Alternatively, the PCF filters the Service Specific Information Data Subset provided by UDR, e.g. using the PLMN as Data Subkey, then includes only URSP Rules applicable for the Serving PLMN. The PCF removes the URSP Rules applicable for the Serving PLMN when the UE Policy association with the V-PCF in the Serving PLMN is terminated or when the UE moves to a different Serving PLMN and a change of PLMN PCRT is reported via V-PCF. The H-PCF provides a list of PSIs identified by the HPLMN ID, the location validity conditions in the URSP Rule contains a list of TAI(s) or Cell ID(s), if included. + +An example of provisioning URSP rules that contains RSDs for a VPLMN is as follows. In order to let UE give preference to evaluate the VPLMN specific URSP rules, the UE receives the provisioning as follows: + +- VPLMN specific URSP rules only contains the RSDs for VPLMN; +- HPLMN specific URSP rules can be used for both VPLMN and HPLMN; +- VPLMN specific rules has higher priority than HPLMN specific URSP rules, so that UE can firstly evaluate VPLMN specific URSP rules/RSDs in roaming case. + +### 6.2.2 Procedures + +#### 6.2.2.1 VPLMN AF guidance for URSP rule creation at an HPLMN + +A call flow of the procedure is shown below. + +![Sequence diagram illustrating the procedure to influence URSP rules for a different PLMN. The diagram shows interactions between UE, V-PCF, HPLMN (PCF, UDM, UDR, NEF), and (VPLMN owned) AF. The process involves AF triggering a request, NEF authorizing with UDM, NEF updating UDR, UDR notifying PCF, PCF creating URSP rules, and PCF notifying UE via V-PCF.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-PCF + participant HPLMN as HPLMN + participant AF as (VPLMN owned) AF + Note right of AF: Apply these service parameters when a UE is located in VPLMN-ID + + Note over HPLMN: Application guidance on URSP determination + + AF->>NEF: 1. Trigger of AF request + NEF->>UDM: 2. Nnef_ServiceParameter_Create Request (App-1, DNN, S-NSSAI, Location = VPLMN-ID, Any UE (or specific UE ids), Event = Successful UE Policy Delivery) + UDM->>NEF: 2b. Authorize the AF request + NEF->>UDR: 3a. Nudr_DM_Create or Update (Data Set Identifier: Application Data, Data subset: Service specific information) + UDR->>NEF: 3b. ACK + NEF->>AF: 3c. Nnef_ServiceParameter_Create Response + UDR->>PCF: 4a. Nudr_DM_Notify + V-PCF->>PCF: 4b. UE policy create request (PSIs) + PCF->>UDR: 4c. Retrieve Application Data + Note right of PCF: 5. Create new URSP rule for App-1 that is valid in location = VPLMN-ID + PCF->>V-PCF: 6a. UE Configuration Update for transparent UE policy delivery + V-PCF->>UE: 6b. Success Ack + PCF->>UDM: 7. Notify + UDM->>NEF: 8a. Nudm_ServiceSpecific_NotifyUpdate Request + NEF->>UDM: 8b. Nudm_ServiceSpecific_NotifyUpdate Response + NEF->>AF: 9a. Nnef_ServiceParameter_Notify Request (Event = Successful UE Policy Delivery related to the invocation of AF provisioned Service Parameters) + AF->>NEF: 9b. Nnef_ServiceParameter_Notify Response + +``` + +Sequence diagram illustrating the procedure to influence URSP rules for a different PLMN. The diagram shows interactions between UE, V-PCF, HPLMN (PCF, UDM, UDR, NEF), and (VPLMN owned) AF. The process involves AF triggering a request, NEF authorizing with UDM, NEF updating UDR, UDR notifying PCF, PCF creating URSP rules, and PCF notifying UE via V-PCF. + +**Figure 6.2.2.1-1: Procedure to influence URSP rules for a different PLMN** + +Steps are as follows: + +1. AF in VPLMN is triggered to request to the home PLMN of a UE a specific handling of routing traffic to the VPLMN. +2. The AF invokes a service operation with the NEF including in the request updated service information as described in clause 4.15.6.10 of TS 23.502 [3]. The updated information includes a validity conditions to apply a URSP rule in a specific PLMN (or a list of PLMN). The request is applicable for any UE or the AF may include external identifiers of the UE. +- 2a-2c The NEF may authorize the request with the UDM according to TS 23.502 [3]. +- 3a When the authorization is successful the NEF updates the data in the UDR including within Application Data the updated service information. The NEF invokes an Nudr\_DM\_Create (or Update) service request requested the UDR to store the service information in the "Application Data" Data Set within the Service Specific Information Data Subset identifier. The NEF may also include a Data Key the target UEs or Group of UEs. +- 3b. The UDR acknowledges the NEF request. +- 3c. The NEF acknowledges the AF request. +- 4a. If the PCF has subscribed to Service Specific Information the UDR notifies the PCF of the updated service information. +- 4b. When a UE registers to the H-PLMN (or VPLMN) the UE includes a list of PSIs. The AMF (in HPLMN) or V-PCF (in VPLMN) initiates a UE Policy Association Create request with the PCF including in the request the list of PSIs associated to the HPLMN. +- 4c. The PCF may retrieve Application Data subscription information from the UDR. +5. The PCF creates updated URSP rules including URSP rules with validity conditions on per PLMN basis according to the information stored in the UDR. + +6. The PCF provides updated URSP rules to the UE by initiating a UE Configuration Update for transparent policy delivery (via the V-PCF if the UE is roaming) to deliver updated URSP rule to a UE. +- 6b. The UE acknowledges successful installation of rules. +7. If the AF has subscribed to notification of successful policy delivery the PCF notifies the UDR. +- 8a-8b The UDR informs the NEF of successful policy delivery. +- 9a-9b. The NEF informs the AF of successful policy delivery. + +#### 6.2.2.2 UE behaviour on applying a URSP rule with a PLMN validity condition in route selection descriptor + +The UE upon reception of URSP rules including a PLMN validity conditions within Route Selection Descriptors enforces the URSP rules as follows: + +- When the UE finds that application traffic matches traffic descriptor of a URSP rules the UE checks the list of Route Selection Descriptors of the matched URSP rule. +- If an RSD in the list of RSDs contains PLMN validity conditions the UE checks if the PLMN identity within the validity conditions matches the PLMN identity of the registered PLMN or an equivalent PLMN of the registered PLMN. +- If there is match the UE considers the RSD valid and routes the application traffic according to the contents of the route selection descriptor. +- If there is no match the UE considers the RSD as invalid and continues to process a second RSD in the list of RSD of the matched URSP rules if available. + +### 6.2.3 Impacts on services, entities and interfaces + +**Editor's note:** This clause captures impacts on existing 3GPP nodes and functional elements. + +URSP rule is enhanced with a PLMN identity validity condition within Route Selection Descriptors. The UE checks if the PLMN identity within the validity conditions matches the PLMN identity of the registered PLMN or an equivalent PLMN of the registered PLMN. + +## 6.3 Solution #3: URSP provisioning and updating in roaming + +### 6.3.1 Description + +This is a solution related to the Key Issue #1 URSP in VPLMN. + +Flexible scenarios deployed in VPLMN, e.g. flexible LADN deployment or MEC deployment, requires the URSP generation and updating to have the consideration of the policy information (including LADN DNN or AF located in VPLMN) in VPLMN dynamically. Furthermore, as it needs to keep the backward compatibility with the existing framework of policy control based on HPLMN, the aforementioned policy information in VPLMN needs to be provided to the HPLMN by VPLMN for UPSP generation and updating in roaming case. In this solution, it is proposed that the V-PCF provides the UE policy assistant information of VPLMN to the H-PCF and take the UE Policy Association Establishment/modification procedure as specified in clause 4.16.11 of TS 23.502 [3] as basis for URSP provisioning and updating. + +### 6.3.2 UE Policy Association Establishment with VPLMN assistant information + +![Sequence diagram showing the UE Policy Association Establishment with VPLMN assistant information. The diagram involves four main entities: AMF, V-PCF, V-UDR, and H-PCF. The process starts with the AMF making a decision to establish the association. The AMF sends a Npcf_UEPolicyControl create Request to the V-PCF. The V-PCF then sends a Nudr_DM_Query Request to the V-UDR to obtain VPLMN assistant UE policy information. The V-UDR responds with the information. The V-PCF then sends a Npcf_UEPolicyControl create Request (VPLMN assistant UE policy information) to the H-PCF. The H-PCF responds with a Npcf_UEPolicyControl create Response. The V-PCF then sends a Npcf_UEPolicyControl create Response to the AMF. The H-PCF then sends a Npcf_UEPolicyControl UpdateNotify request to the V-PCF. The V-PCF responds with a Npcf_UEPolicyControl UpdateNotify Response. The AMF then initiates a UE configuration update procedure. The H-PCF sends a Npcf_UEPolicyControl Update request to the V-PCF. The V-PCF responds with a Npcf_UEPolicyControl Update Response.](10781f43062bf3e9601a1e086710556c_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant V-PCF + participant V-UDR + participant H-PCF + + Note left of AMF: 1. Decision to establish UE policy Association + AMF->>V-PCF: 2. Npcf_UEPolicyControl create Request + V-PCF-->>V-UDR: 3. Nudr_DM_Query Request (for obtaining VPLMN assistant UE policy information) + V-UDR-->>V-PCF: 4. Npcf_UEPolicyControl create Request(VPLMN assistant UE policy information) + V-PCF-->>H-PCF: 5. Npcf_UEPolicyControl create Response + V-PCF-->>AMF: 6. Npcf_UEPolicyControl create Response + Note left of AMF: 9. UE configuration update procedure + H-PCF-->>V-PCF: 7. Npcf_UEPolicyControl UpdateNotify request + V-PCF-->>H-PCF: 8. Npcf_UEPolicyControl UpdateNotify Response + H-PCF-->>V-PCF: 10. Npcf_UEPolicyControl Update request + V-PCF-->>H-PCF: 11. Npcf_UEPolicyControl Update Response + +``` + +Sequence diagram showing the UE Policy Association Establishment with VPLMN assistant information. The diagram involves four main entities: AMF, V-PCF, V-UDR, and H-PCF. The process starts with the AMF making a decision to establish the association. The AMF sends a Npcf\_UEPolicyControl create Request to the V-PCF. The V-PCF then sends a Nudr\_DM\_Query Request to the V-UDR to obtain VPLMN assistant UE policy information. The V-UDR responds with the information. The V-PCF then sends a Npcf\_UEPolicyControl create Request (VPLMN assistant UE policy information) to the H-PCF. The H-PCF responds with a Npcf\_UEPolicyControl create Response. The V-PCF then sends a Npcf\_UEPolicyControl create Response to the AMF. The H-PCF then sends a Npcf\_UEPolicyControl UpdateNotify request to the V-PCF. The V-PCF responds with a Npcf\_UEPolicyControl UpdateNotify Response. The AMF then initiates a UE configuration update procedure. The H-PCF sends a Npcf\_UEPolicyControl Update request to the V-PCF. The V-PCF responds with a Npcf\_UEPolicyControl Update Response. + +**Figure 6.3.2-1: UE Policy Association Establishment with VPLMN assistant information** + +This procedure takes the UE Policy Association Establishment procedure in roaming case as specified in clause 4.16.11 of TS 23.502 [3] as basis. + +1. The AMF establishes UE Policy Association with the V-PCF same as step 1 in clause 4.16.11 of TS 23.502 [3]. +2. The AMF sends a Npcf\_UEPolicyControl Create Request to V-PCF same as step 2 in clause 4.16.11 of TS 23.502 [3]. +3. After receiving the Npcf\_UEPolicyControl Create Request from the AMF, the V-PCF gets the VPLMN assistant UE policy information based on local policy or get it from the V-UDR by using the Nudr\_DM\_Query service. The VPLMN assistant UE policy information is used for HPLMN to generate the UE policy taking the VPLMN requirement into account. +4. The V-PCF forwards the information received from AMF in step 2 and the VPLMN assistant UE policy information got in step 3 to the H-PCF. The VPLMN assistant UE policy information may include the following information: + - The mapping from traffic descriptor to DNN, NSSAI, SSC mode, PLMN ID, etc. in VPLMN. +- 5-6. Steps 5~6 same as steps 4~5 are performed. +7. Similar to step 6 in clause 4.16.11 of TS 23.502 [3], the H-PCF gets policy subscription related information and the latest list of PSIs from the UDR using Nudr\_DM\_Query service operation. The H-PCF creates the UE policy based on the policy information from UDR and the VPLMN assistant UE policy information if any in step 4, then provides the UE policy container in the Npcf\_UEPolicyControl UpdateNotify Request to V-PCF. +- 8~11. The steps 8~11 are same as the steps 7~10. + +### 6.3.3 UE Policy Association modification with VPLMN assistant information + +![Sequence diagram for UE Policy Association modification with VPLMN assistant information. The diagram shows interactions between AMF, V-PCF, V-UDR, and H-PCF. Step 1: V-UDR sends Nudr_DM_Notify to V-PCF. Step 2: V-PCF sends Npcf_UEPolicyControl_Update Request (VPLMN assistant UE policy information) to H-PCF. Step 3: H-PCF sends Npcf_UEPolicyControl_Update response to V-PCF. Step 4: V-PCF sends Npcf_UEPolicyControl_UpdateNotify Request to H-PCF. Step 5: H-PCF sends Npcf_UEPolicyControl_UpdateNotify response to V-PCF. Step 6: A block labeled 'Step 5~9 in figure 4.16.12.2-1 of TS 23.502' spans across the bottom of the diagram.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant V-PCF + participant V-UDR + participant H-PCF + Note right of V-PCF: 1. Nudr_DM_Notify + V-UDR->>V-PCF: 1. Nudr_DM_Notify + Note left of H-PCF: 2. Npcf_UEPolicyControl_Update Request(VPLMN assistant UE policy information) + V-PCF->>H-PCF: 2. Npcf_UEPolicyControl_Update Request(VPLMN assistant UE policy information) + Note right of H-PCF: 3. Npcf_UEPolicyControl_Update response + H-PCF->>V-PCF: 3. Npcf_UEPolicyControl_Update response + Note left of H-PCF: 4. Npcf_UEPolicyControl_UpdateNotify Request + V-PCF->>H-PCF: 4. Npcf_UEPolicyControl_UpdateNotify Request + Note right of H-PCF: 5. Npcf_UEPolicyControl_UpdateNotify response + H-PCF->>V-PCF: 5. Npcf_UEPolicyControl_UpdateNotify response + Note bottom: 6. Step 5~9 in figure 4.16.12.2-1 of TS 23.502 + +``` + +Sequence diagram for UE Policy Association modification with VPLMN assistant information. The diagram shows interactions between AMF, V-PCF, V-UDR, and H-PCF. Step 1: V-UDR sends Nudr\_DM\_Notify to V-PCF. Step 2: V-PCF sends Npcf\_UEPolicyControl\_Update Request (VPLMN assistant UE policy information) to H-PCF. Step 3: H-PCF sends Npcf\_UEPolicyControl\_Update response to V-PCF. Step 4: V-PCF sends Npcf\_UEPolicyControl\_UpdateNotify Request to H-PCF. Step 5: H-PCF sends Npcf\_UEPolicyControl\_UpdateNotify response to V-PCF. Step 6: A block labeled 'Step 5~9 in figure 4.16.12.2-1 of TS 23.502' spans across the bottom of the diagram. + +**Figure 6.3.3-1: UE Policy Association modification with VPLMN assistant information** + +This procedure takes the UE Policy Association Modification initiated by the PCF procedure in roaming case as specified in clause 4.16.12.2 of TS 23.502 [3] as a basis. + +1. If (V-)PCF subscribed to notification of VPLMN assistant information change and a change is detected, the V-UDR notifies V-PCF of that the VPLMN assistant information has been changed. Before performing this step, the V-PCF needs to subscribe the notification of VPLMN assistant information change from the V-UDR. +2. If the VPLMN assistant information changed according the step 1 or based on local policy in V-PCF, the V-PCF forwards the VPLMN assistant information to the H-PCF via the Npcf\_UEPolicyControl\_Update request. +3. H-PCF responds to V-PCF. +4. The H-PCF may update the UE policy based on the VPLMN assistant UE policy information from V-PCF in step 4, and send it to the V-PCF via the Npcf\_UEPolicyControl\_UpdateNotify request similar to the step 3 of figure 4.16.12.2-1 of TS 23.502 [3]. +5. The V-PCF sends a response to H-PCF using Npcf\_UEPolicyControl\_UpdateNotify Response. +6. The step 6 is same to the steps 5-9 of figure 4.16.12.2-1 of TS 23.502 [3]. + +### 6.3.4 Support routing of the same application traffic with different URSP rules in different PLMNs + +#### 6.3.4.1 URSP enhancement with including the PLMN ID in TD (Option#1) + +For support routing of the same application traffic with different URSP rules in different PLMNs, a potential way is to enhance the existing structure of URSP as specified in clause 6.6.2 of TS 23.503 [4]. The Traffic descriptor in URSP can be enhanced to include: + +- a new component "PLMN ID". + +When to perform the URSP evaluation, for every newly detected application, the UE additionally enter a PLMN ID with the application data. This means that PLMN ID is also involved in URSP evaluation. The PLMN ID is the PLMN ID of its serving PLMN. + +#### 6.3.4.2 URSP dedicated to VPLMN (Option#2) + +For support routing of the same application traffic with different URSP rules in different PLMNs, if there is the VPLMN assistant UE policy information received from the V-PCF as specified in step 4 of clause 6.3.2 or step 2 of clause 6.3.3, the H-PCF provides the URSP only applied to this VPLMN to the UE. When the UE moves to a different VPLMN, the H-PCF will generate or update the URSP Rule to the UE for this different and to be served VPLMN. + +### 6.3.5 Impacts on Existing Nodes and Functionality + +The solution has impacts on the following entities: + +#### V-PCF: + +- Is able to request the VPLMN assistant UE policy information from the V-UDR. +- Supports the subscription of VPLMN assistant UE policy information change notification from the V-UDR. + +#### UDR: + +- Supports the notification of VPLMN assistant UE policy information change. +- Support to provide the VPLMN assistant UE policy information to V-PCF. + +#### H-PCF: + +- Support to create/update the UE policy combined with the VPLMN assistant UE policy information from the V-PCF. +- Provides the URSP only dedicated to the VPLMN to the UE if VPLMN assistant UE policy information is received. + +#### UE: + +- Evaluates the URSP with the consideration of matching PLMN ID in TD with current serving PLMN ID. + +## 6.4 Solution #4: URSP decision with V-PCF involvement + +### 6.4.1 Description + +The Solution addresses Key Issue #1 on URSP in VPLMN. This solution assumes the following: + +- It is assumed that there are some applications which may be deployed in both VPLMN and HPLMN, or VPLMN only. In either scenario, the VPLMN may request to transport the corresponding application traffic with some specific DNN(s) and/or S-NSSAI(s). +- During the lifetime of UE Policy Association, the V-PCF is capable of generating URSP rules from VPLMN perspective, based on operator configuration or input from the AF. For example, the AF (e.g. gyms, museums) in VPLMN may request to distribute URSP rules to the UEs within a specific area, including the roaming UEs, thus the application traffic can be routed with corresponding DNN and/or S-NSSAI in the URSP rules. +- To avoid breaking the current framework of URSP decision by HPLMN, the V-PCF provides the generated URSP rules to the H-PCF for final decision, which contains the Route Selection Descriptor and Validation Criteria which indicates that the RSD is only applicable in the current VPLMN and its equivalent PLMN(s). + +The enhancement is to add a new criteria as Applicable PLMN to the **Route Selection Validation Criteria** in the Route Selection Descriptor, as defined in the Table 6.6.2.1-3 of the TS 23.503 [4]. + +| | | | | | +|-----------------|----------------------------------------------------------------------------------------|----------|-----|------------| +| Applicable PLMN | Indicates the applicable PLMN(s) in which the RSD can be adopted for URSP association. | Optional | Yes | UE context | +|-----------------|----------------------------------------------------------------------------------------|----------|-----|------------| + +### 6.4.2 Procedure + +![Sequence diagram illustrating the URSP decision procedure with V-PCF involvement. The diagram shows five entities: UE, AMF, V-PCF, AF, and H-PCF. The sequence of messages is: 0. UE Registers to the 5GS via VPLMN; 1. URSP decision in VPLMN (V-PCF to AF); 2. Npcf_UEPolicyControl_Update request (V-PCF to H-PCF); 3. URSP decision in HPLMN (H-PCF to V-PCF); 4. Npcf_UEPolicyControl_Update response (H-PCF to V-PCF); 5. UE Configuration Update procedure (V-PCF to UE).](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-PCF + participant AF + participant H-PCF + Note over UE, AMF, V-PCF, AF, H-PCF: 0. UE Registers to the 5GS via VPLMN + Note over V-PCF, AF: 1. URSP decision in VPLMN + V-PCF->>H-PCF: 2. Npcf_UEPolicyControl_Update request + Note over H-PCF: 3. URSP decision in HPLMN + H-PCF->>V-PCF: 4. Npcf_UEPolicyControl_Update response + Note over V-PCF, UE: 5. UE Configuration Update procedure + +``` + +Sequence diagram illustrating the URSP decision procedure with V-PCF involvement. The diagram shows five entities: UE, AMF, V-PCF, AF, and H-PCF. The sequence of messages is: 0. UE Registers to the 5GS via VPLMN; 1. URSP decision in VPLMN (V-PCF to AF); 2. Npcf\_UEPolicyControl\_Update request (V-PCF to H-PCF); 3. URSP decision in HPLMN (H-PCF to V-PCF); 4. Npcf\_UEPolicyControl\_Update response (H-PCF to V-PCF); 5. UE Configuration Update procedure (V-PCF to UE). + +**Figure 6.4.2-1: URSP decision with V-PCF involvement** + +0. UE registers to the 5GC via the VPLMN. + 1. The V-PCF determines to generate URSP rules applicable to the UE based on local policies and/or AF/V-UDR interaction, to allow the UE access to the application using the values indicated by specific DNN, and/or S-NSSAI. Besides, the Route Selection Validation Criteria of the RSD contains the PLMN(s) in which the RSD is applicable, e.g. the VPLMN, the PLMN(s) equivalent to the VPLMN. +- NOTE 1: The S-NSSAI within the NSSP provided by the V-PCF is for the HPLMN, which is determined by the V-PCF based on local configuration or based on the mapping of VPLMN S-NSSAIs to HPLMN S-NSSAIs received from the AMF. +- NOTE 2: The equivalent PLMN(s) of the VPLMN can be configured in the V-PCF or received from the AMF. +2. The V-PCF provides the generated URSP rule(s) to the H-PCF for final decision via Npcf\_UEPolicyControl\_Update request message. + 3. Based on the subscription data and/or local policies, the H-PCF checks whether the received URSP rule(s) can be authorized for the UE, e.g. whether the S-NSSAI in the NSSP is allowed by the subscription NSSAI. +- NOTE 3: It is up to the H-PCF implementation to determine the precedence of the URSP rules originated by the V-PCF. +4. The H-PCF provides the authorized URSP rules to the V-PCF via Npcf\_UEPolicyControl\_Update response message. + 5. The V-PCF triggers the UE policy delivery via UE configuration Update procedure. + +After this procedure, the UE can associate the corresponding application to appropriate PDU Session based on the received URSP rules. + +### 6.4.3 Impacts on services, entities and interfaces + +The solution has impacts in the following entities: + +UE: + +- Needs to support the validation of Applicable PLMN list in RSD Validation Criteria. + +V-PCF: + +- Needs to support the generation of URSP rules applicable to VPLMN only and further provide the generated URSP rules to H-PCF for final decision. + +H-PCF: + +- Needs to perform final decision taking the generated URSP rules from V-PCF into account. + +## 6.5 Solution #5: URSP determination based on service parameter obtained from VPLMN + +### 6.5.1 Description + +This is a solution for key issue #1 "URSP in VPLMN". + +Currently, URSP is only controlled and determined by HPLMN. Therefore, to give influence on URSP determination, e.g. application guidance for URSP determination specified in clause 4.15.6.10 of TS 23.502 [3], the AF needs to provide inputs to HPLMN. The application guidance for URSP determination may be for Edge services or for location-based services which means there may be the case that the URSP rules determined based on the application guidance can be applied and valid only when the UEs are in any specific VPLMN in roaming case. Anyhow, in this case, the AF may need to provide application guidance for URSP determination to all PLMNs whose subscribers will be probably roaming into the VPLMN, and the AF has service level agreements with. In addition, if the AF includes a geographical area as spatial validity condition in the application guidance for URSP determination, the NEF may need to transform this information into 3GPP identifiers (e.g. TAI(s)). For this, the NEF needs to have knowledge on VPLMN's 3GPP identifiers (e.g. TAI(s)). + +In this solution, the AF provides application guidance for URSP determination to the PLMN (i.e. to UDR via NEF of this PLMN) where the related services are provided or the related traffic is routed. H-PCF of the roaming UE obtains the application guidance for URSP determination from VPLMN by requesting V-PCF to subscribe to V-UDR to be notified about the data creation/modification for the UE. V-PCF subscribes to V-UDR on behalf of H-PCF, by adding a new PCRT that request notification when Service Parameters are available for a UE Policy Association. If the AF provides inputs to V-UDR via V-NEF, V-PCF provides the data notified by V-UDR to H-PCF. + +The AF can include the PLMN ID(s) when provisioning application guidance for URSP determination for all HPLMNs whose subscribers may roam into the VPLMN, in order to indicate that the provisioned information is for roamers from that PLMN ID(s). The Application data in UDR is extended to provide PLMN ID as Data Key. Table 6.5.1-1 shows "PLMN ID" as an additional Data Key and NOTE 5 describing the "PLMN ID" on top of data keys for Application data specified in Table 5.2.12.2.1-1: Data keys in TS 23.502 [3]. + +**Table 6.5.1-1: Data keys** + +| Data Set | Data Subset | Data Key | Data Sub Key | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------|--------------| +| Application data | Service specific information (See clause 4.15.6.7) | S-NSSAI and DNN or Internal Group Identifier or SUPI or "PLMN ID" or "any UE" indication (NOTE 4) (NOTE 5) | - | +| NOTE 4: When the Data Key targets "any UE", then the request to UDR applies on Application data that applies on all subscribers of the PLMN. For encoding, see TS 29.519 [15]. | | | | +| NOTE 5: When the Data Key targets "PLMN ID", then the request to UDR applies on Application data that applies on all subscribers of that PLMN ID. The AF provides a PLMN ID if the request applies for all subscribers of that PLMN that can be roaming to the VPLMN the AF provides the request to. | | | | + +This solution reuses the existing Npcf\_UEPolicyControl Service for the H-PCF to subscribe to reception of new/updated Service Parameters for the UE, using a new PCRT and for the V-PCF to notify to the H-PCF and provide the Service Parameters for the UE to the H-PCF. + +The H-PCF generates a new URSP Rule or updates an existing URSP Rule with the same traffic descriptor as provided in the Service Parameters, if the S-NSSAI subscription information indicates that this DNN, S-NSSAI is subscribed, and LBO roaming is allowed. + +The H-PCF sends the URSP Rule to the UE using existing procedures. In addition, the H-PCF subscribes to "change of PLMN", then when the UE moves to a different PLMN, the H-PCF removes or updates the URSP Rule sent to the UE to remove the RSD that routed the traffic through the VPLMN where the UE was registered. The H-PCF also removes or updates the URSP Rule sent to remove the RSD that routed the traffic through the VPLMN when the V-PCF requests to terminate the UE Policy Association. + +### 6.5.2 Procedures + +###### 6.5.2.1 Procedure for URSP determination based on service parameter obtained from VPLMN + +Figure 6.5.2.1-1 shows the procedure for URSP determination based on service parameter obtained from VPLMN. + +![Sequence diagram illustrating the procedure for URSP determination based on service parameter obtained from VPLMN. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, V-NEF, AF, H-PCF, V-SMF, V-UPF, and Application Server. The process starts with UE Registration, followed by UE Policy Association, Nudr_DM_Subscribe, Creation of the AF request, Nnef_ServiceParameter_Create Request, Storing the request information, Nnef_ServiceParameter_Create Response, Nudr_DM_Notify, Npcf_UEPolicyControl_Update (Service Parameters), Determining URSP rules, UE Policy delivery/update, URSP rule matching, PDU Session Establishment, and finally UL/DL Data.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-PCF + participant V-UDR + participant V-NEF + participant AF + participant H-PCF + participant V-SMF + participant V-UPF + participant AS as Application Server + + Note left of AMF: UE Registration + AMF->>H-PCF: 1. UE Policy Association + V-PCF->>V-UDR: 2. Nudr_DM_Subscribe + AF->>V-NEF: 3. Creation of the AF request + V-NEF->>AF: 4. Nnef_ServiceParameter_Create Request + AF->>V-UDR: 5. Storing the request information + V-UDR->>V-NEF: 6. Nnef_ServiceParameter_Create Response + V-NEF->>V-PCF: 7. Nudr_DM_Notify + V-PCF->>H-PCF: 8. Npcf_UEPolicyControl_Update (Service Parameters) + H-PCF->>H-PCF: 9. Determining URSP rules + H-PCF->>AMF: 10. UE Policy delivery/update + AMF->>UE: 11. URSP rule matching + UE->>V-SMF: 12. PDU Session Establishment + V-SMF->>V-UPF: 13. UL/DL Data + V-UPF-->>AS: 13. UL/DL Data + +``` + +Sequence diagram illustrating the procedure for URSP determination based on service parameter obtained from VPLMN. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, V-NEF, AF, H-PCF, V-SMF, V-UPF, and Application Server. The process starts with UE Registration, followed by UE Policy Association, Nudr\_DM\_Subscribe, Creation of the AF request, Nnef\_ServiceParameter\_Create Request, Storing the request information, Nnef\_ServiceParameter\_Create Response, Nudr\_DM\_Notify, Npcf\_UEPolicyControl\_Update (Service Parameters), Determining URSP rules, UE Policy delivery/update, URSP rule matching, PDU Session Establishment, and finally UL/DL Data. + +**Figure 6.5.2.1-1: Procedure for URSP determination based on service parameter obtained from VPLMN** + +1. The UE is registered to 5GC and the UE Policy Association is performed between the AMF and the H-PCF via V-PCF. In addition, the H-PCF may subscribe using a new PCRT "Service Parameters received" to the V-PCF. The V-PCF provides the Service Parameters if available. +2. Based on the reception of a new PCRT from the H-PCF, the V-PCF may subscribe to the reception of Service Parameters from the AF for the determination of URSP Rules for any UE of that HPLMN registered in this VPLMN, if not subscribes to V-UDR when the UE Policy Association is created for subscribers of that HPLMN. + +The V-PCF includes VPLMN DNN and S-NSSAI in the subscription request to the UDR given that the AF provides Application guidance for URSP determination to the VPLMN. + +3. To provide Application guidance for URSP determination as specified in clause 4.15.6.10 of TS 23.502 [3], the AF creates a new request. +- 4-6. As specified in steps 2 to 4 in clause 4.15.6.7 of TS 23.502 [3], the AF sends its request to the NEF, and the NEF stores the AF request information in the UDR and responds to the AF. In this figure, the NEF is V-NEF and the UDR is V-UDR. + +The AF request is targeting any UE (all UEs) of a HPLMN that are registered in this VPLMN. Therefore, the V-NEF authorizes the request based on local policy based on service level agreements between the AF and the VPLMN (e.g. based on AF Id) without requesting for any service specific authorization from UDM as specified in clause 4.15.6.10 of TS 23.502 [3]. + +NOTE: The AF request targeting a specific UE or a group of UE(s) does not apply to this solution because Service Specific Authorization for an individual UE or group of UEs by NEF to UDM has to be performed for the AF request as specified in clause 4.15.6.10 of TS 23.502 [3]. + +7. The V-PCF receives a Nudr\_DM\_Notify notification of data change from the V-UDR. +8. The V-PCF sends the notification of data change from the V-UDR invoking Npcf\_UEPolicyControl\_Update including the Service Parameters that have been received from the UDR to the H-PCF. The V-PCF also provides the mapping of the VPLMN S-NSSAI to HPLMN S-NSSAI and the mapping of the VPLMN DNN to HPLMN DNN to the H-PCF. +9. The H-PCF determines the URSP rules that is to be sent to the UE based on the Service Parameters received from the V-PCF and the S-NSSAI subscription information for this SUPI, DNN, S-NSSAI retrieved from the UE context policy control subscription information from the UDR. The H-PCF generates a new URSP Rule or update an existing URSP Rule that was sent to the UE for the same traffic descriptor to include a new RSD with the DNN, S-NSSAI provided by the V-PCF then sets the RSD precedence and validity conditions taking the information provided by the V-PCF into account. + +That is, the H-PCF replaces any URSP rules related to Route Selection Descriptor(s) including the DNN and S-NSSAI. + +10. The H-PCF provisions the URSP rules to the UE via the V-PCF by using the UE Configuration Update procedure for transparent UE Policy delivery as specified in clause 4.2.4.3 of TS 23.502 [3]. The H-PCF provides S-NSSAI and DNN values of the VPLMN to the UE in the RSD component of the URSP rule. +11. The UE needs to send traffic, e.g. destined to an Edge service. Therefore, the UE determines a URSP rule applicable for the traffic. For URSP Rules applicable in the VPLMN the UE considers a RSD valid if the S-NSSAI value is in the Allowed NSSAI instead of the Mapping Of Allowed NSSAI. +12. If there is no PDU Session that matches all components in the selected RSD within the URSP rule, the UE establishes a PDU Session. The UE provides both the S-NSSAI of the VPLMN, i.e., the S-NSSAI in the URSP Rule, and the S-NSSAI of the HPLMN obtained from the mapping of the Allowed NSSAI to HPLMN S-NSSAI as described in clause 5.15.5.3 of TS 23.501 [2]. The UE includes the DNN of the VPLMN, i.e., the DNN in the URSP Rule if provided as UE Requested DNN, as described in clause 6.6.2.1 of TS 23.503 [4]. If the UE Requested DNN is supported but not subscribed, then the AMF checks if there is a mapping to the HPLMN DNN configured, then uses it for subscription check. The AMF uses the UE Requested DNN as Selected DNN, then performs SMF selections. The AMF sends both the Selected DNN (i.e. UE Requested DNN) and the DNN value of the HPLMN to SMF. The SMF uses the DNN value of the HPLMN and the S-NSSAI value of the HPLMN for subscription check as described in clause 4.3.2.2.1 of TS 23.502 [3]. +13. The UE communicates with the Application Server, e.g. Edge Application Server. + +### 6.5.3 Impacts on services, entities and interfaces + +H-PCF: + +- Subscribes to a new PCRT "Service Parameters received". +- Reception of Service Parameters for a UE Policy Control Association established with the V-PCF. + +- Determines URSP rules based on the data provided by AF and received via V-UDR and V-PCF, taking S-NSSAI subscription information into account. +- S-NSSAI subscription information extended to include if LBO is allowed. + +## V-PCF: + +- Subscribes to V-UDR to be notified about the Service Parameters creation/modification for roaming UEs if the H-PCF provided a PCRT. +- Provides the Service Parameters notified by V-UDR to H-PCF. + +## H-UDR: + +- S-NSSAI Subscription information needs to include an indication of whether LBO roaming is allowed for a DNN, S-NSSAI. + +## UE: + +- For URSP Rules applicable in the VPLMN the UE considers the RSD valid if the S-NSSAI value is in the Allowed NSSAI instead of the Mapping Of Allowed NSSAI. + +## AMF: + +- At PDU Session Establishment uses the UE requested DNN as Selected DNN, for subscription check the AMF maps the UE Requested DNN to HPLMN DNN. + +## 6.6 Solution #6: Solution for URSP in VPLMN with PLMN domain indication + +### 6.6.1 General + +As specified in TS 23.503 [4], the URSP is only to be provided by the HPLMN. However, there are cases where different VPLMNs have different preference on the PDU session parameters for the same application. To support such differentiated URSP handling in different PLMNs, following enhancements are required: + +- Enhance the URSP provision so that the URSP rules are provided with PLMN ID(s) associated. +- Allowing the UE to utilize the URSP rules associated with the serving PLMN first, and if no match is found, utilize the URSP of the HPLMN. + +### 6.6.2 Functional descriptions + +The VPLMN provides the URSP applicable to the UE to HPLMN. This may be triggered by the UE's registration in the VPLMN or happen before UE roam into the VPLMN. AF in VPLMN may use the service specific parameter procedure to influence HPLMN generating the URSP for VPLMN. + +For how the UE identify VPLMN's URSP rules, there are two options as below. + +Option-1: The HPLMN constructs the URSP for the UE, with different list of PSIs associated with the different VPLMN IDs which are outside of PSI, then sends the mapping table to UE together with UE Policy Sections containing the URSP. Some examples are shown in below: + +<VPLMN #1 ID, list of PSIs>; + +<VPLMN #2 ID, list of PSIs>; + +... + +<VPLMN #n ID, list of PSIs>. + +The HPLMN ensures that the URSP rules associated with the VPLMN IDs only apply to the PDU session that supports LBO. This solution maintains the Rel-17 principle that the HPLMN ID is always part of the PSI when the policy section + +carries a URSP rule, thus there will continue to be no conflict between VPLMN allocated PSI's (which do not carry URSP rules) and HPLMN allocated PSIs. + +The UE is provisioned with the URSP rules following the existing procedure as defined in TS 24.501 [7]. The UE stores the list of PSIs associated with PLMN IDs. + +When UE registered in the VPLMN, it locates the list of PSIs associated with the VPLMN-ID and the list of PSIs associated with HPLMN-ID. + +UE applies the URSP rules associated with the VPLMN ID first, if any. If there is a match, the UE follows the URSP rule to establish the PDU session. + +If the UE does not find a match using the URSP rules associated with the VPLMN ID, it uses the URSP rules associated with the equivalent VPLMN ID, if any. If there is no URSP rules associated with the equivalent VPLMN ID, the UE uses the URSP rules associated with the HPLMN ID. + +The UE does not use other URSP rules than those associated with the VPLMN ID, equivalent VPLMN ID or HPLMN IDs. + +Option-2: alternatively, if the new mapping table is not used, the (H-)PCF provides URSP Rules that are identified by the HPLMN ID as defined in TS 23.503 [4]. The PCF removes the URSP Rules applicable for the Serving PLMN when the UE Policy association with the V-PCF in the Serving PLMN is terminated or when the UE moves to a different Serving PLMN and a change of PLMN PCRT is reported via V-PCF. The H-PCF provides a list of PSIs identified by the HPLMN ID, the location validity conditions in the URSP Rule may contain a list of TAI(s) or Cell ID(s). The URSP policy can be used to the registered VPLMN and its equivalent VPLMN, however cannot be used for other PLMNs. In order to avoid using a wrong URSP rules, the UE may remove all URSP rules when it moves to a different PLMN except the equivalent PLMN. This option-2 reduces the number of URSP Rules that are sent to the UE and the number of URSP Rules that needs to be evaluated by the UE. + +### 6.6.3 Procedures + +The existing procedures as defined in TS 24.501 [7] for UE Policy provisioning can be reused, besides the above enhancements. + +### 6.6.4 Impacts on services, entities, and interfaces + +For Option-1 (provisioning mapping table along with URSP rules), the impacts on existing entities: + +- UE needs to utilize URSP rules associated with the VPLMN or Equivalent PLMN if no VPLMN URSP rules, before applying URSP rules associated with HPLMN. +- A mapping between VPLMN ID and PSI sets need to be provisioned to UE along with the Policy Sections containing URSP rules. + +For Option-2 (provisioning new URSP rules when PLMN changes), the impact on existing entities: + +- The UE may remove all URSP rules when it moves to a different PLMN except an equivalent VPLMN. + +## 6.7 Solution #7: URSP Compliance Verification + +### 6.7.1 Description + +This solution addresses the following technical issues of the KI#2: + +- Whether and how the 5GC can be made aware whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on the URSP rule provisioned by 5GC. +- Whether there are any actions the 5GS can take after 5GC is aware whether the UE enforces a URSP rule for specific application traffic or not. If any, what action 5GC should take? + +In the current 5GC, there is no way to check whether the application traffic from the UE is compliant with the URSP. + +The URSP is composed of Traffic Descriptor and Route Selection Component. The UE can associate application with the existing PDU Session or request a new PDU Session if no PDU Session matches the URSP rules when the application is detected. In this solution, we focus on the case when the UE requests a new PDU Session and discuss how the 5GC can know whether the requested PDU Session is compliant with the URSP. + +In order to check whether the PDU Session Establishment request is compliant with URSP rule, the 5GC needs to identify the request is caused by which URSP rule. The PDU Session Establishment request can include RSC of the URSP rules, however, there is no information which URSP rule (i.e. Traffic Descriptor) matches. + +Therefore, we introduce an identifier for the URSP Rule so that the PCF can identify which URSP rule causes the request of the PDU Session. If the UE includes the matched URSP Rule Identifier in the PDU Session Establishment request, the 5GC can be aware of the association between the URSP rules and the PDU Session so that 5GC can verify whether the UE is compliant with the URSP rules. + +1. When constructing a URSP rule, URSP Rule Identifier (URID) is added to identify the URSP rule. +2. UE reports the URSP Rule Identifier associated with URSP rules causing a new PDU Session Establishment request by including the URID in the same request based on the PCF demand. + +When the SMF is reported for the associated URID, it should be reported to the PCF responsible for the URSP (i.e. UE-PCF). Since the multiple SM-PCFs can be used for one UE, we assume UE-PCF and SM-PCF may not be the same and the UE-PCF is responsible for URSP compliance verification. + +Since SMF may not have a direct interface to the UE-PCF, we use the reporting path from the SMF to the UE-PCF via SM-PCF in order for the SMF to report the URID and its received PDU Session Parameters (PSP). + +If the 5GC identifies that the UE is not compliant to the URSP rule, the 5GC does not allow the UE to establish a new PDU Session based on its policy. + +The abstract of this solution is depicted in the Figure 6.7.1-1. + +![Sequence diagram illustrating the authorization of a URSP verified PDU Session. The diagram shows interactions between UE, AMF, SMF, UE-PCF, and SM-PCF. The sequence is: 1. UE Policy Association (UARI) from UE to AMF; 2. URSP (URID, UCR) from AMF to UE; 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) from UE to AMF; 4. SMContextCreate (UARI, PDU-Session Est. Req) from AMF to SMF; 5. SM Policy Association (UARI, R-PSPs) from SMF to SM-PCF; 6. URSP Authorization Request (Requested PSPs, URID) from SM-PCF to UE-PCF; 7. URSP Authorization Response (URSP Authorization Result) from UE-PCF to SM-PCF; 8. SM Policy Association (Authorization Result) from SM-PCF to SMF.](68ea9310fb829dd6007635a6cd4ea2ad_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UE-PCF + participant SM-PCF + + Note right of UE: 1. UE Policy Association (UARI) + UE->>AMF: 1. UE Policy Association (UARI) + Note left of AMF: 2. URSP (URID, UCR) + AMF->>UE: 2. URSP (URID, UCR) + Note right of UE: 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) + UE->>AMF: 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) + Note left of AMF: 4. SMContextCreate (UARI, PDU-Session Est. Req) + AMF->>SMF: 4. SMContextCreate (UARI, PDU-Session Est. Req) + Note right of SMF: 5. SM Policy Association (UARI, R-PSPs) + SMF->>SM-PCF: 5. SM Policy Association (UARI, R-PSPs) + Note left of SM-PCF: 6. URSP Authorization Request (Requested PSPs, URID) + SM-PCF->>UE-PCF: 6. URSP Authorization Request (Requested PSPs, URID) + Note right of UE-PCF: 7. URSP Authorization Response (URSP Authorization Result) + UE-PCF->>SM-PCF: 7. URSP Authorization Response (URSP Authorization Result) + Note left of SM-PCF: 8. SM Policy Association (Authorization Result) + SM-PCF->>SMF: 8. SM Policy Association (Authorization Result) + +``` + +Sequence diagram illustrating the authorization of a URSP verified PDU Session. The diagram shows interactions between UE, AMF, SMF, UE-PCF, and SM-PCF. The sequence is: 1. UE Policy Association (UARI) from UE to AMF; 2. URSP (URID, UCR) from AMF to UE; 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) from UE to AMF; 4. SMContextCreate (UARI, PDU-Session Est. Req) from AMF to SMF; 5. SM Policy Association (UARI, R-PSPs) from SMF to SM-PCF; 6. URSP Authorization Request (Requested PSPs, URID) from SM-PCF to UE-PCF; 7. URSP Authorization Response (URSP Authorization Result) from UE-PCF to SM-PCF; 8. SM Policy Association (Authorization Result) from SM-PCF to SMF. + +**Figure 6.7.1-1: Authorization of URSP verified PDU Session with the UE reported URSP rule identifier** + +The UE-PCF is responsible for URSP compliance verification. The UE-PCF sends URSP Authorization Request Indication (UARI) to the AMF when the UE Policy Association is established or notified with the update. + +If AMF receives UARI and PCF binding info, it stores the information and sends them to the SMF during the PDU Session Establishment procedure. + +**NOTE:** This solution uses the existing feature that the AMF stores the PCF ID so that the SM-PCF can use it to contact the UE-PCF. + +When the SMF establishes the SM Policy Association, the SMF forwards the UARI and Received PDU Session Parameters (R-PSPs) to the SM-PCF. If the SM-PCF receives the UARI request, it performs the URSP Authorization procedure with UE-PCF with the R-PSPs received from the SMF through SM-PCF and URID received from the UE. + +The UE-PCF can request the UE to assist the URSP compliance by sending URSP Compliance Request (UCR) together with URSP rules with the UE Policy Container. The UCR indicates the UE to report the URSP Rule Identifier (URID) associated URSP rule that causes the establishment of the PDU Session. If the UE receives the UCR, the UE includes the URID in the PDU Session Establishment request when initiating a PDU Session caused by the URSP rule. + +When the SMF is requested for UARI and receives the PDU Session Establishment Request, the SMF requests the authorization of the PDU Session from the UE-PCF through SM-PCF. The UE-PCF checks the R-PSP requested by the UE and the URID to verify whether the PDU Session Establishment request is compliant with the URSP rule. + +The UE-PCF can take other actions later instead of immediate authorization of the PDU Session. In this scenario, the UE-PCF can receive the reporting of the established PDU Session from the SM-PCF. The UE-PCF requests the PDU Session Parameters Reporting (PSPR) instead of UARI. The abstract procedure of this alternative is described in the Figure 6.7.1-2. When the PSPR is requested from the UE-PCF, the SM-PCF notifies the PDU Session Parameters to the UE-PCF. + +![Figure 6.7.1-2: Sequence diagram showing PDU Session Parameter Reporting with the UE reported URSP rule identifier. The diagram involves four entities: UE, AMF, SMF, and UE-PCF. The sequence of messages is: 1. UE Policy Association (PSPR) from UE-PCF to AMF; 2. URSP (URID, UCR) from AMF to UE; 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) from UE to AMF; 4. SMContextCreate (PSPR, PDU-Session Est. Req) from AMF to SMF; 5. SM Policy Association (PSPR, Requested PSPs, Accepted PSPs) from SMF to SM-PCF; 6. SM Policy Authorization Notify (Requested PSPs, Accepted PSPs) from SM-PCF to UE-PCF; 9. URSP (URID, UCR) from UE-PCF to AMF.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant SM-PCF + participant UE-PCF + + UE-PCF->>AMF: 1. UE Policy Association (PSPR) + AMF->>UE: 2. URSP (URID, UCR) + UE->>AMF: 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) + AMF->>SMF: 4. SMContextCreate (PSPR, PDU-Session Est. Req) + SMF->>SM-PCF: 5. SM Policy Association (PSPR, Requested PSPs, Accepted PSPs) + SM-PCF->>UE-PCF: 6. SM Policy Authorization Notify (Requested PSPs, Accepted PSPs) + UE-PCF->>AMF: 9. URSP (URID, UCR) + +``` + +Figure 6.7.1-2: Sequence diagram showing PDU Session Parameter Reporting with the UE reported URSP rule identifier. The diagram involves four entities: UE, AMF, SMF, and UE-PCF. The sequence of messages is: 1. UE Policy Association (PSPR) from UE-PCF to AMF; 2. URSP (URID, UCR) from AMF to UE; 3. PDU Session Est. (URID, S-NSSAI, DNN, PDU Session ID, etc) from UE to AMF; 4. SMContextCreate (PSPR, PDU-Session Est. Req) from AMF to SMF; 5. SM Policy Association (PSPR, Requested PSPs, Accepted PSPs) from SMF to SM-PCF; 6. SM Policy Authorization Notify (Requested PSPs, Accepted PSPs) from SM-PCF to UE-PCF; 9. URSP (URID, UCR) from UE-PCF to AMF. + +**Figure 6.7.1-2: PDU Session Parameter Reporting with the UE reported URSP rule identifier** + +Due to various reasons, the UE-PCF does use the URSP rule identifier reporting. The UE-PCF performs the authorization of the URSP verified PDU Session without UE reporting as depicted in the Figure 6.7.1-3. In this scenario, the procedure is similar to the Figure 6.7.1-1 except the following differences: + +- The UE-PCF provides the URSP rules without URSP rule identifier and does not command URSP Compliance Request to the UE. +- The UE does not report the URSP rule identifier when establishing the PDU Session. + +![Figure 6.7.1-3: Sequence diagram showing Authorization of URSP verified PDU Session without UE reporting. The diagram involves four entities: UE, AMF, SMF, and UE-PCF. The sequence of messages is: 1. UE Policy Association (UARI) from UE-PCF to AMF; 2. PDU Session Est. from UE to AMF; 3. SMContextCreate (UARI) from AMF to SMF; 4. SM Policy Association (UARI, R-PSPs) from SMF to SM-PCF; 5. URSP Authorization Request (Requested PSPs) from SM-PCF to UE-PCF; 6. SM Policy Authorization Response (URSP Authorization Result) from UE-PCF to SM-PCF; 7. SM Policy Association (Authorization Result) from SM-PCF to SMF.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant SM-PCF + participant UE-PCF + + UE-PCF->>AMF: 1. UE Policy Association (UARI) + UE->>AMF: 2. PDU Session Est. + AMF->>SMF: 3. SMContextCreate (UARI) + SMF->>SM-PCF: 4. SM Policy Association (UARI, R-PSPs) + SM-PCF->>UE-PCF: 5. URSP Authorization Request (Requested PSPs) + UE-PCF->>SM-PCF: 6. SM Policy Authorization Response (URSP Authorization Result) + SM-PCF->>SMF: 7. SM Policy Association (Authorization Result) + +``` + +Figure 6.7.1-3: Sequence diagram showing Authorization of URSP verified PDU Session without UE reporting. The diagram involves four entities: UE, AMF, SMF, and UE-PCF. The sequence of messages is: 1. UE Policy Association (UARI) from UE-PCF to AMF; 2. PDU Session Est. from UE to AMF; 3. SMContextCreate (UARI) from AMF to SMF; 4. SM Policy Association (UARI, R-PSPs) from SMF to SM-PCF; 5. URSP Authorization Request (Requested PSPs) from SM-PCF to UE-PCF; 6. SM Policy Authorization Response (URSP Authorization Result) from UE-PCF to SM-PCF; 7. SM Policy Association (Authorization Result) from SM-PCF to SMF. + +**Figure 6.7.1-3: Authorization of URSP verified PDU Session without UE reporting** + +Similarly, the UE-PCF does use the URSP rule identifier reporting. The UE-PCF requests the PDU Session Parameter Reporting. The abstract procedure is described in Figure 6.7.1-4. + +![Sequence diagram showing the authorization of a URSP verified PDU Session without UE reporting. The diagram involves four entities: UE, AMF, SMF, and two PCFs (UE-PCF and SM-PCF). The sequence of messages is: 1. UE-PCF to AMF: UE Policy Association (PSPR); 2. UE to AMF: PDU Session Est.; 3. AMF to SMF: SMContextCreate (PSPR); 4. SMF to SM-PCF: SM Policy Association (PSPR, Requested PSPs, Accepted PSPs); 5. SM-PCF to UE-PCF: SM Policy Authorization Notify (Requested PSPs, Accepted PSPs).](dd5771673aececa53d42ece89218299d_img.jpg) + +``` +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UE-PCF + participant SM-PCF + Note right of UE-PCF: 1. UE Policy Association (PSPR) + UE->>AMF: 2. PDU Session Est. + AMF->>SMF: 3. SMContextCreate (PSPR) + SMF->>SM-PCF: 4. SM Policy Association (PSPR, Requested PSPs, Accepted PSPs) + SM-PCF->>UE-PCF: 5. SM Policy Authorization Notify (Requested PSPs, Accepted PSPs) +``` + +Sequence diagram showing the authorization of a URSP verified PDU Session without UE reporting. The diagram involves four entities: UE, AMF, SMF, and two PCFs (UE-PCF and SM-PCF). The sequence of messages is: 1. UE-PCF to AMF: UE Policy Association (PSPR); 2. UE to AMF: PDU Session Est.; 3. AMF to SMF: SMContextCreate (PSPR); 4. SMF to SM-PCF: SM Policy Association (PSPR, Requested PSPs, Accepted PSPs); 5. SM-PCF to UE-PCF: SM Policy Authorization Notify (Requested PSPs, Accepted PSPs). + +**Figure 6.7.1-4: Authorization of URSP verified PDU Session without UE reporting** + +#### Consideration on Requested PDU Session Parameters + +For the PCF for the UE to verify the appropriate RSD provided by the UE in the PDU Session Establishment request, the SMF should be able to deliver the RSD parameters that it receives from the UE to the SM-PCF. + +Among the Route selection components in URSP rules, the PDU Session Parameters such as DNN, S-NSSAI, PDU Session Type, Access Type that the UE sent to the SMF can be delivered to the PCF. + +However, the SSC Mode, PDU Session Pair ID, RSN are required to be sent to the PCF so that the PCF can validate parameters. + +NOTE: Non-seamless Offline indication and ProSe Layer-3 UE-to-Network Relay Offload indication is not subject to be verified in the serving network. + +**Table 6.7.1.1: Comparison between URSP RCS and the parameters in SMPolicyControl service operation** + +## 6.7.2 Procedures + +### 6.7.2.1 Provisioning of URSP Compliance Verification in Registration procedure + +| Route selection components | Description of RSC in Table 6.6.2.1-3 of TS 23.503 [4] | Npcf_SMPolicyControl_Create request (clause 5.2.5.4.2 of TS 23.502 [3]) | Required to be reported (New) | +|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|-------------------------------| +| <i>SSC Mode Selection</i> | <i>One single value of SSC mode.</i> | | YES | +| Network Slice Selection | Either a single value or a list of values of S-NSSAI(s). | S-NSSAI | Already exist | +| DNN Selection | Either a single value or a list of values of DNN(s). | DNN | Already exist | +| PDU Session Type Selection | One single value of PDU Session Type. | PDU Session Type | Already exist | +| Non-Seamless Offload indication | Indicates if the traffic of the matching application is to be offloaded to non-3GPP access outside of a PDU Session. | | Not required | +| ProSe Layer-3 UE-to-Network Relay Offload indication | Indicates if the traffic of the matching application is to be sent via a ProSe Layer-3 UE-to-Network Relay outside of a PDU session. | | Not required | +| Access Type preference | Indicates the preferred Access Type (3GPP or non-3GPP or Multi-Access) when the UE establishes a PDU Session for the matching application. | Access Type | Already exist | +| <i>PDU Session Pair ID</i> | <i>An indication shared by redundant PDU Sessions as described in clause 5.33.2.1 of TS 23.501 [2].</i> | | YES | +| <i>RSN</i> | <i>The RSN as described in clause 5.33.2.1 of TS 23.501 [2].</i> | | YES | + +This procedure describes the provisioning of URSP Compliance Verification procedure during the UE registration procedure. With this procedure, the UE-PCF performs the following: + +- 1) UE-PCF indicates the UE to report the URSP Rule Identifier associated with URSP rules causing a new PDU Session Establishment request by including the URID in the same request. +- 2) UE-PCF provides PDU Session Parameter Reporting (PSPR) or URSP Authorization Request Indication (UARI) with PCF binding information to the AMF so that the AMF sends them to the SMF during the PDU Session Establishment procedure. + +![Sequence diagram showing the provisioning of URSP Compliance Verification during Registration procedure. The diagram involves three entities: UE, AMF, and UE-PCF. The sequence of messages is as follows: 1. UE sends a Registration Request (UEP Container with UCCI) to AMF. 2. AMF sends a UE Policy Association Create Request (SUPI, PEI, UEPC(UCCI)) to UE-PCF. 3. UE-PCF sends a UE Policy Association Create Response (SM Policy Association Est. Notification, PCF binding info(PCF ID), PDU Session Parameter Reporting Request; PSPR, URSP Authorization Required Indication; UARI) to AMF. 4. AMF sends an N1N2messageTransfer (UEPC(URSP rules with URSP Rule ID(URID), URSP Compliance Reporting (UCR))) to UE. 5. UE sends a UE Configuration Update (UEPC (URID, UCR)) to AMF. 6. AMF sends a UE Configuration Update (Result of UE Policy delivery, UCR Ack, [compiled URID list]) to UE. 7. AMF sends an N1messageNotify (UEPC(Result of UE policy delivery, UCR Ack, [compiled URID list])) to UE-PCF. 8. UE-PCF sends an N1N2messageTransfer ack to AMF.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UE-PCF + Note left of UE: 1. Registration Request (UEP Container (URSP Compliance Capability Indication; UCCI)) + UE->>AMF: 1. Registration Request + Note right of AMF: 2. UE Policy Association Create Request (SUPI, PEI, UEPC(UCCI)) + AMF->>UE-PCF: 2. UE Policy Association Create Request + Note right of UE-PCF: 3. UE Policy Association Create Response (SM Policy Association Est. Notification, PCF binding info(PCF ID), PDU Session Parameter Reporting Request; PSPR, URSP Authorization Required Indication; UARI) + UE-PCF->>AMF: 3. UE Policy Association Create Response + Note right of AMF: 4. N1N2messageTransfer (UEPC(URSP rules with URSP Rule ID(URID), URSP Compliance Reporting (UCR))) + AMF->>UE: 4. N1N2messageTransfer + Note left of UE: 5. UE Configuration Update (UEPC (URID, UCR)) + UE->>AMF: 5. UE Configuration Update + Note right of AMF: 6. UE Configuration Update (Result of UE Policy delivery, UCR Ack, [compiled URID list]) + AMF->>UE: 6. UE Configuration Update + Note right of AMF: 7. N1messageNotify (UEPC(Result of UE policy delivery, UCR Ack, [compiled URID list])) + AMF->>UE-PCF: 7. N1messageNotify + Note right of UE-PCF: 8. N1N2messageTransfer ack + UE-PCF->>AMF: 8. N1N2messageTransfer ack + +``` + +Sequence diagram showing the provisioning of URSP Compliance Verification during Registration procedure. The diagram involves three entities: UE, AMF, and UE-PCF. The sequence of messages is as follows: 1. UE sends a Registration Request (UEP Container with UCCI) to AMF. 2. AMF sends a UE Policy Association Create Request (SUPI, PEI, UEPC(UCCI)) to UE-PCF. 3. UE-PCF sends a UE Policy Association Create Response (SM Policy Association Est. Notification, PCF binding info(PCF ID), PDU Session Parameter Reporting Request; PSPR, URSP Authorization Required Indication; UARI) to AMF. 4. AMF sends an N1N2messageTransfer (UEPC(URSP rules with URSP Rule ID(URID), URSP Compliance Reporting (UCR))) to UE. 5. UE sends a UE Configuration Update (UEPC (URID, UCR)) to AMF. 6. AMF sends a UE Configuration Update (Result of UE Policy delivery, UCR Ack, [compiled URID list]) to UE. 7. AMF sends an N1messageNotify (UEPC(Result of UE policy delivery, UCR Ack, [compiled URID list])) to UE-PCF. 8. UE-PCF sends an N1N2messageTransfer ack to AMF. + +**Figure 6.7.2.1-1: Provisioning of URSP Compliance Verification during Registration procedure** + +1. The UE, that is compliant with URSP and supports the reporting URSP identifier, sends URSP Compliance Capability Indicator (UCCI) within the UE Policy Container during the registration procedure. +2. The UE-PCF determines whether to perform the URSP compliance verification procedure (e.g. URSP compliant PDU Session Authorization or PDU Session Parameter Reporting). +3. The UE-PCF sends PSPR (PDU Session Parameter Reporting Request) or URSP Authorization Required Indication (UARI) to the AMF. The AMF records the PCF binding info (PCF ID) +- 4-5. The UE-PCF provides the URSP Compliance Reporting (UCR) and the URSP rules in UE Policy Container. When the UE-PCF constructing a URSP rule, URSP Rule Identifier (URID) is added to identify the URSP rule. The UE-PCF provides the URSP rules within which each URSP rule is identified by the URSP identifier. +5. When the UE receives the UE Policy Container, the UE stores the URSP rules with URID and UCR. +6. The UE sends the acknowledgement of UCR with the URID that the UE is compliant with them. +7. The UE-PCF receives the UCR acknowledgement. + +## 6.7.2.2 URSP Compliance Verification in PDU Session Establishment procedure + +This procedure describes the URSP Compliance Verification during the PDU Session Establishment procedure: + +- 1) Authorization of URSP compliant PDU Session Establishment with (or without) UE reporting URSP rule identifier. (UARI). +- 2) Reporting of PDU Session Parameters with (or without UE) UE reporting URSP rule identifier (PSPR). + +![Sequence diagram showing URSP Compliance Verification during PDU Session Establishment. The diagram involves five entities: UE, AMF, SMF, SM-PCF, and UE-PCF. The sequence of messages is as follows: 1. UE to AMF: PDU Session Establishment (PDU Session ID, URSP Rule ID; URID). 2. AMF to SMF: CreateSMContext (PCF ID, SM Policy Association Notification, PCF binding info, PSPR, UARI, SM-NAS (PDU Session ID, URID)). 3. SMF to SM-PCF: SM Policy Association Create (PCF ID, PSPR, UARI, Requested PDU Session Parameters (PDU Session ID, URID, DNN, S-NSSAI, SSC Mode, PDU Session Type, UARI, etc)). 4. SM-PCF to UE-PCF: URSP Compliance Authorization Request (R-PSP (PDU Session ID, URID, etc)). 5. UE-PCF to SM-PCF: URSP Compliance Authorization Response (Compliance Result). 6. SM-PCF to SMF: SM Policy Association Create Response (Result of Authorization, Authorized Policy Info). 7. SMF to AMF: N1N2messageTransfer (PDU Session Establishment Accept/Reject). 8. AMF to UE: PDU Session Establishment Accept/Reject. 9. AMF to SMF: UpdateSMContext. 10. SMF to SM-PCF: SM Policy Association Update (PCF ID, URID, R-PSP, Accepted-PSP). 11. SM-PCF to UE-PCF: SM Policy Authorization Notify (PDU Session Status, PDU Session ID, URID, R-PSP, A-PSP).](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Sequence diagram showing URSP Compliance Verification during PDU Session Establishment. The diagram involves five entities: UE, AMF, SMF, SM-PCF, and UE-PCF. The sequence of messages is as follows: 1. UE to AMF: PDU Session Establishment (PDU Session ID, URSP Rule ID; URID). 2. AMF to SMF: CreateSMContext (PCF ID, SM Policy Association Notification, PCF binding info, PSPR, UARI, SM-NAS (PDU Session ID, URID)). 3. SMF to SM-PCF: SM Policy Association Create (PCF ID, PSPR, UARI, Requested PDU Session Parameters (PDU Session ID, URID, DNN, S-NSSAI, SSC Mode, PDU Session Type, UARI, etc)). 4. SM-PCF to UE-PCF: URSP Compliance Authorization Request (R-PSP (PDU Session ID, URID, etc)). 5. UE-PCF to SM-PCF: URSP Compliance Authorization Response (Compliance Result). 6. SM-PCF to SMF: SM Policy Association Create Response (Result of Authorization, Authorized Policy Info). 7. SMF to AMF: N1N2messageTransfer (PDU Session Establishment Accept/Reject). 8. AMF to UE: PDU Session Establishment Accept/Reject. 9. AMF to SMF: UpdateSMContext. 10. SMF to SM-PCF: SM Policy Association Update (PCF ID, URID, R-PSP, Accepted-PSP). 11. SM-PCF to UE-PCF: SM Policy Authorization Notify (PDU Session Status, PDU Session ID, URID, R-PSP, A-PSP). + +**Figure 6.7.2.2-1: URSP Compliance Verification during PDU Session Establishment** + +1. After the UE evaluates URSP rules, the UE detects an application that matches the URSP rule and determines to establish a new PDU Session based on the URSP. If the UE receives the URSP Compliance Request (UCR) in the provisioning of URSP compliance verification during registration procedure (see the step 5 of Figure 6.7.2.1-1), the UE sends the PDU Session Establishment request including the URSP Rule Identifier (URID) associated with URSP rule causing the establishment of this PDU session. + +NOTE 1: No new privacy issue is caused by this solution. + +2. The AMF forwards the PDU Session Establishment to the SMF. If the PSPR or UARI is requested from the UE-PCF, the AMF forwards the request to the SMF together with PCF binding info. +3. UARI mode: The SMF sends Requested PDU Session Parameters (R-PSPs). The R-PSPs include the DNN, S-NSSAI, PDU Session Type, Access Type, which already appear in Npcf\_SMPolicyControl\_Create request. In addition, the R-PSPs include the SSC Mode, PDU Session Pair ID, RSN if the UE sent in the PDU Session Establishment request so that the PCF can validate the parameters. +4. If the UE-PCF has requested UARI (as in the step 3 of Figure 6.7.2.1-1), the SM-PCF sends the URSP Compliance Authorization Request to the UE-PCF. +5. The UE-PCF verify whether the UE is compliant with the URSP rules by checking the requested PDU Session parameters with the URSP rules (RSDs) and authorises the UE requested PDU Session. The UE-PCF is able to reject the PDU Session if the UE-PCF determines that the request is not compliant with URSP rules. + +Once the UE-PCF authorises the URSP compliance, the UE-PCF sends URSP Compliance Authorization Response including the URSP compliance result. + +NOTE 2: When UE-PCF and SM-PCF is deployed in the same entity, the step 4~5 and 11 are not exposed. + +6. If URSP compliance result is successful, the SM-PCF sends the authorized policy information to the SMF. The SMF forwards the URSP compliance result. +7. If the SMF is requested with UARI and the URSP Compliance Authorization Result is not successful, the SMF reject the PDU Session Establishment. +8. The AMF forwards the PDU Session Establishment Accept/Reject to the UE. +9. The AMF updates the SM context. +10. After the successful establishment of the PDU Session, if the SMF is indicated with the PSPR, the SMF reports the A-PSPs to the SM-PCF. + +NOTE 3: The UE-PCF can stores the established PDU Session Parameters and later it can use them to verify whether the UE is compliant with selecting the PDU Session for the corresponding application or application traffic by using application detection feature. + +11. If the SM-PCF is requested with PSPR to the UE-PCF, the SM-PCF notifies the UE-PCF of the PDU Session Status, PDU Session ID and URID, A-PSP. The UE-PCF records A-PSP, PDU Session ID associated with the URSP Rule Identifier for verification of the URSP compliance. + +### 6.7.3 Impacts on services, entities and interfaces + +#### UE: + +- The UE should understand the URSP Rule Identifier referring URSP Rules and be able to identify the URSP rule when initiating a PDU Session. +- The UE should be able to report the URSP Rule Identifier in the PDU Session Establishment Request. +- The UE should be able to report the complied URSP Rule Identifiers back to the UE-PCF. + +NOTE: Due to UE design philosophy, some of UE implementation may not support some of Traffic Descriptors in the URSP Rule. For those URSP rules, the UE may reply to the UE-PCF with sending the compiled URSP Rule Identifiers with UE policy delivery result. + +#### AMF: + +- The AMF should be able to receive the request (i.e. either URSP Compliance Authorization or PDU Session Parameter Reporting) and its related parameters from the UE-PCF during UE Policy Association procedure. +- When receiving PDU Session Establishment request from the UE, the AMF should forward the request from the UE-PCF to the SMF. + +#### SMF: + +- For URSP Compliance Authorization, the SMF should authorize the UE requested PDU Session based on the response from the SM-PCF after the UE-PCF authorizes the request via SM-PCF. +- For PDU Session Parameter Reporting, the SMF should report the requested and accepted PDU Session Parameters to the SM-PCF so that SM-PCF can report those to the UE-PCF. + +#### SM-PCF: + +- For USSP Compliance Authorization, during the SM Policy Association procedure caused by the PDU Session Establishment, the SM-PCF performs the URSP compliance authorization with UE-PCF. +- For PDU Session Parameter Reporting, after the PDU Session Establishment procedure, the SM-PCF reports the UE requested and accepted PDU Session Parameters to the UE-PCF. + +#### UE-PCF: + +- The UE-PCF is responsible for URSP compliance verification. The UE-PCF should be able to support 1) URSP Compliance Reporting 2) URSP Compliance Authorization 3) PDU Session Parameter Reporting. +- For URSP Compliance Reporting (UCR request) to the UE, the UE-PCF generates the URSP rules with URSP Rule Identifier and request the UE to report the URSP Rule Identifier. +- For URSP Compliance Authorization (UARI), the UE-PCF should be able to authorize the UE-requested PDU Session by checking whether the PDU Session Parameters of the request is compliant to the RSD's of URSP rules. +- For PDU Session Parameter Reporting (PSPR), the UE-PCF should be able to request the SMF to report the PDU Session Parameters of the request. + +## 6.8 Solution #8: URSP Rule Precedence reporting for awareness of URSP enforcement + +### 6.8.1 Description + +This solution aims to address the Key Issue#2: 5GC awareness of URSP enforcement. + +It is proposed to use the parameter of URSP Rule Precedence to identify a specific URSP rule. + +The UE can indicate to the network the URSP rule it is trying to enforce by reporting the URSP Rule Precedence. When an existing PDU session matches the RSD of selected URSP, or when the UE tries to establish a new PDU Session using the values specified by the selected RSD, the URSP enforcement reporting process can be done during a session management procedures such as PDU Session Establishment procedure or PDU Session Modification procedure. + +To protect user privacy, the URSP enforcement reporting process shall be subject to user consent. The user consent is obtained by the ASP and provided to the MNO. The information of user consent for URSP enforcement reporting is included per URSP rules and provisioned to the UE. The UE reports the URSP Rule Precedence of the URSP rule it is trying to enforce only when the user consent part of the URSP rule is "YES". + +NOTE: The procedures to obtain user consent need to be studied by SA3. + +### 6.8.2 Procedures + +As described in TS 23.503 [4], for every newly detected application the UE evaluates the URSP rules in the order of Rule Precedence and determines if the application is matching the Traffic descriptor of any URSP rule. When a valid Route Selection Descriptor is found, the UE determines if there is an existing PDU Session that matches all components in the selected Route Selection Descriptor. + +If one or more matching PDU Session(s) exist(s), the UE associates the application to one existing PDU Session and initiates PDU Session Modification procedure for URSP enforcement reporting as described in clause 4.3.3.2 of TS 23.502 [3]. Following impacts are applicable: + +- Step 1a: The UE includes UE Policy Container (URSP Rule Precedence corresponding to the URSP rule enforced by the UE, and the operating system identifier) in PDU Session Modification Request message. The AMF transfers the message transparently to the SMF via Nsmf\_PDUSession\_UpdateSMContext message. +- Step 2: After receiving UE Policy Container in the PDU Session Modification Request message, the SMF forwards the PCF the UE Policy Container reported by the UE using Npcf\_SMPolicyControl\_Update service operation. The PCF returns the URSP rule indicated by the URSP Rule Precedence to the SMF. + +The SMF compares the RSD of the URSP rule received from the PCF with the PDU session attributes (e.g. DNN, S-NSSAI, etc) of the PDU session the UE trying to associate to. If it is not matched, the SMF rejects the PDU Session Modification request with a proper cause value. + +- Step 2a/2b: The SMF generates N4 rules (PDR, URR) based on the Traffic Descriptor of the URSP rule received from the PCF and provisions the rules to the UPF using N4 Session Modification procedure. The SMF indicates the UPF to report the event when incorrect application traffic is detected for the QoS Flow indicated in the PDR. + +When incorrect application traffic is detected, the UPF should send a report to the SMF. The SMF should further inform to the PCF that the URSP rule is wrongly enforced by the UE. The PCF can decide whether to update the URSP rules to the UE based on local configuration and operator policies (e.g. update the URSP via UCU procedure by excluding the wrongly enforced URSP rule). + +NOTE 1: It is assumed that same PCF is selected by the SMF and the AMF. + +NOTE 2: The PDR sent from the SMF to the UPF indicates the QFI and a Packet Filter Set, any traffic in the QoS Flow identified by the QFI does not match the Packet Filter Set deemed as incorrect application traffic. + +If none of the existing PDU Sessions matches the selected Route Selection Descriptor, the UE tries to establish a new PDU Session as described in clause 4.3.2.2.1 TS 23.502 [3] using the values specified by the selected RSD. Following impacts are applicable for URSP enforcement reporting: + +- Step 1: The UE includes UE Policy Container (URSP Rule Precedence corresponding to the URSP enforced by the UE, and the operating system identifier) in PDU Session Establishment Request message. +- Step 3: The AMF transfers the PDU Session Establishment Request (UE Policy Container (URSP Rule Precedence corresponding to the URSP rule enforced by the UE, and the operating system identifier)) to the SMF by Nsmf\_PDUSession\_CreateSMContext Request message. +- Step 7b: After receiving UE Policy Container in the PDU Session Establishment Request message, the SMF forwards to the PCF the UE Policy Container reported by the UE using Npcf\_SMPolicyControl\_Create service operation. The PCF returns the URSP rule indicated by the URSP Rule Precedence to the SMF. + +The SMF compares the RSD of the URSP rule received from the PCF with the PDU session attributes (e.g. DNN, S-NSSAI, etc) of the PDU session the UE trying to establish. If it is not matched, the SMF rejects the PDU Session Establishment request with a proper cause value. + +- Step 10a/10b: The SMF generates N4 rules (PDR, URR) based on the Traffic Descriptor of the URSP rule received from the PCF and provisions the rules to the UPF using N4 Session Establishment procedure. The SMF indicates the UPF to report the event when incorrect application traffic is detected for the QoS Flow indicated in the PDR. + +When incorrect application traffic is detected, the UPF should send a report to the SMF. The SMF should further inform to the PCF that the URSP rule is wrongly enforced by the UE. The PCF can decide whether to update the URSP rules to the UE based on local configuration and operator policies (e.g. update the URSP via UCU procedure by excluding the wrongly enforced URSP rule). + +### 6.8.3 Impacts on services, entities and interfaces + +#### UE: + +- Initiates PDU Session Modification procedure when matching PDU Session is found for a URSP rule, and includes UE Policy Container (URSP Rule Precedence corresponding to the URSP enforced by the UE, and the operating system identifier) in PDU Session Modification Request message. +- During the new PDU Session Establishment procedure when none of the existing PDU Sessions matches the selected Route Selection Descriptor, includes UE Policy Container (URSP Rule Precedence corresponding to the URSP enforced by the UE, and the operating system identifier) in PDU Session Establishment Request message. + +#### SMF: + +- Forwards the UE Policy Container reported by the UE to the PCF. +- Compares the RSD of the URSP rule received from the PCF with the attributes of the PDU session the UE trying to establish or associate to. +- Generates N4 rules (PDR, URR) based on the Traffic Descriptor of the URSP rule received from the PCF. +- Indicates the UPF to report the event when incorrect application traffic is detected for the QoS Flow indicated in the PDR. +- Forwards the incorrect application traffic detection report received from UPF to the PCF. + +#### PCF: + +- Based on the UE Policy Container received from the SMF, provides corresponding URSP rule to the SMF. +- Decides whether to update the URSP to the UE by the UCU procedure when incorrect application traffic detection report is received from the SMF. + +#### UPF: + +- Detects application traffic and reports to the SMF when incorrect application traffic is detected. + +## 6.9 Solution #9: Per-PDU session awareness of URSP enforcement + +### 6.9.1 Description + +**Editor's note:** This clause will describe the solution principles and architecture assumptions for corresponding key issue(s) which should be explicitly stated. Clause(s) may be added to capture details. + +The main use case of this solution is to support a network operator to determine if a UE routes application traffic to an established PDU session of a specific DNN/S-NSSAI according to a URSP rule. For example, when the UE establishes a PDU session to an S-NSSAI/DNN that is used for enterprise services, based on a specific URSP rule, the network operator verifies that the UE does not route application traffic that is not intended for enterprise services. + +The solution relies on the PCF to identify if a UE routes traffic correctly when the UE establishes a PDU session for an S-NSSAI/DNN/RAT type that matches a Route Selection Descriptor of a URSP rule that was provisioned to the UE. + +The PCF determines to identify if the UE routes traffic correctly to the UE requested PDU session based on local configuration or based on information provided by the UDR. In such scenario, the PCF determines the applicable URSP rule that triggered the UE to request establishment of a PDU session to a specific S-NSSAI/DNN by obtaining the list of PSIs containing the provisioned URSP rules to the UE from the UDR. The PCF then identifies the traffic allowed to the requested S-NSSAI/DNN by identifying URSP rule(s) that have within a Route Selection Descriptor, components that matches the requested S-NSSAI/DNN and then evaluating the Traffic Descriptor of such URSP rule(s). For example, if the Traffic Descriptor includes a Destination Address IP 3 tuple then the PCF considers allowed traffic any traffic sent to or received via the Destination Address. + +When the PCF is triggered to identify if the UE routes traffic to an S-NSSAI/DNN according to a provisioned URSP rule the PCF provides rules to the SMF to report traffic that is not intended to be routed via the PDU session. Further details are provided below. + +### 6.9.2 Procedures + +**Editor's note:** This clause describes high-level procedures and information flows for the solution. + +The procedure is shown below: + +![Sequence diagram showing the interaction between UE, PCF, UDR, SMF, and UPF for URSP rule enforcement. The diagram illustrates the flow from application traffic detection in the UE to the final configuration of the UE with updated URSP rules via the PCF.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCF + participant UDR + participant SMF + participant UPF + + Note left of UE: 0. Application in UE Sends traffic + Note left of UE: 1. Decides to establish a PDU session (e.g. due to a matched URSP rule) + UE->>SMF: 2. Requests establishment of PDU session (S-NSSAI, DNN, SSC mode) + SMF->>PCF: 3. Npcf_SMPolicyControl_Create (SUPI PDU session ID, DNN, S-NSSAI, RAT type) + Note right of PCF: 4. PCF determines that for this PDU session URSP rule enforcement must be checked +One option is configuration from UDR + Note right of PCF: 5. Determines URSP rule that triggered PDU session establishment + PCF->>UDR: 5a. Nudr_DM_Query (SUPI, Policy Data, UE context policy control data, Policy Set Entry) + UDR->>PCF: 5b. Nudr_DM_Query response (Policy Sections with URSP rules) + Note right of PCF: 6. Policy Decision + PCF->>SMF: 7. Npcf_SMPolicyControl_Response (PDU session related information rules and PCC rules, Rule(s) to report non-matching traffic routed via this PDU session (Allowed Traffic)) + Note right of UPF: 8. Create N4 rules (N4 session ID, Rule(s) to report non-matching traffic routed via this PDU session (Allowed Traffic), UE ID, DNN/S-NSSAI) + Note right of UPF: 9. Reports Traffic (reports SDF traffic, data used) + Note right of SMF: 10. Reports Traffic (reports SDF traffic, data used) + Note right of UE: 11. Determines if the traffic detected should be routed via a different S-NSSAI/DNN (i.e. a different URSP rule) + Note right of UE: 12. Configures UE with updated URSP rules via UE Configuration Update procedure for transparent UE policy delivery + +``` + +Sequence diagram showing the interaction between UE, PCF, UDR, SMF, and UPF for URSP rule enforcement. The diagram illustrates the flow from application traffic detection in the UE to the final configuration of the UE with updated URSP rules via the PCF. + +**Figure 6.9.2-1: PCF requests to identify from UPF if UE enforces URSP rules correctly** + +The procedure is as follows: + +0. An application in the UE sends traffic or request a network connection. +1. The UE detects new application traffic and determines that application traffic needs to be routed via a PDU session of a specific DNN, S-NSSAI, RAT type. The determination may be based due to a configured URSP rule, local configuration or application request. +2. The UE requests establishment of a PDU session using specific S-NSSAI, DNN, SSC mode. Optionally, provided that there is user consent, if the determination in step 1 was made due to a URSP rule the UE may include a URSP indication in the PDU session establishment request provided that there is user consent. The indication may include an identifier of the URSP rule that triggered the UE to request establishment of a PDU session or may include the Policy Section Identifier of the policy section that contained the URSP rule that triggered the PDU session establishment. +3. The SMF selects a PCF and requests policies by establishing an SM Policy Association. The SMF sends an Npcf\_SM\_PolicyControl\_Create including the SUPI, PDU session ID, DNN, S-NSSAI requested and RAT type of the access that the UE requested establishment of a PDU session. +4. The PCF determines to check for the UE requested PDU session if the UE routes traffic according to a provisioned URSP rule. + +The PCF may be pre-configured or configured from the UDR with the allowed traffic when a UE establishes a PDU session to a specific S-NSSAI/DNN. Alternatively steps 5 takes place. +5. The PCF determines the potential URSP rule and the corresponding Traffic Descriptor of the URSP rule that triggered the UE to request establishment of a PDU session to a specific S-NSSAI/DNN. + +- 5a. The PCF obtains the URSP rule by interfacing with the UDR to obtain the policy sections of URSP rules provisioned to the UE. The PCF may include the PSI identifier or URSP rule id if included by the UE in step 2. +- 5b. The UDR provides the policy sections of the URSP rule. +6. The PCF makes policy decisions according to UE subscription. +7. The PCF provides PDU session related information rules and PCC rules in an Npcf\_SMPolicyCreate\_Response. The PCF also includes rules to the SMF to report non-matching traffic (i.e. traffic different to the allowed traffic) via the S-NSSAI, DNN. The PCF includes the Allowed Traffic that can be routed via the PDU session. + +NOTE: The PCF may provide rule at a later stage by invoking an Npcf\_SMPolicyModification request. + +8. SMF based on the PCC rules installs N4 rules at the UPF. SMF includes rules to the UPF to report non-matching traffic via the S-NSSAI, DNN and includes also the allowed traffic. +9. When the UPF detects non-matching traffic the UPF reports the traffic to the SMF. The UPF includes the service data flow information of the non-matching traffic detected. +10. The SMF reports the detected information to the PCF. +11. The PCF determines if the traffic reported should be sent via a different S-NSSAI or whether traffic should be blocked. The PCF may install rules to the SMF to block such traffic or determine new URSP rules to route traffic via a different S-NSSAI. +12. The PCF provides updated URSP rules to the UE using the UE Configuration Update for transparent policy delivery. + +### 6.9.3 Impacts on services, entities and interfaces + +**Editor's note:** This clause captures impacts on existing 3GPP nodes and functional elements. + +- UPF report SDFs that do not match to allowed traffic. + +## 6.10 Solution #10: Network based URSP rules enforcement feedback + +### 6.10.1 Description + +#### 6.10.1.1 Network based URSP rules enforcement verification without UE assistance + +The UE uses URSP rules to apply the application traffic to PDU sessions in UE. But, for some of the situation, the 5GC wants to aware of the enforcement of URSP rules in UE. + +One of the solutions is, according to the URSP rules, the UPF sets the PDR in specific UE's PDU session. If the specific application packets are detected by PDR, it means the application traffic is applied to this PDU session, and the parameters of this PDU session can be used to reverse to determine the RSD. Which RSDs contains the PDU session parameters, is the real URSP rules that used in UE for this application traffic. + +If PCF wants to monitor some of the enforcement of the RSD in specific Traffic Descriptor, the PCF provides the Traffic Descriptor which describes the traffic feature to SMF to construct the PDR. + +In PDR, the packet filter set is the main parameters for UPF to detect. And in the Traffic Descriptor in URSP rules, the IP descriptor can be directly used for the construction of PDR, that the IP descriptor describes the destination IP address. But for other kinds of Traffic Descriptor, for example, the Application Descriptor, DNN, Domain Descriptor or Connection Capabilities, that these parameters can't be directly used for construction of PDR. + +Although some of the Traffic Descriptor in URSP rules doesn't provide the 5-IP-tuple, but finally, the application traffic should be routed to a specific application server which is represented as IP address and port number. So, it means the Traffic Descriptor in UE only has the function of applying application traffic to specific PDU session, but there still has a mapping table between Traffic Descriptor and destination IP address. + +So, after applying the application traffic to a PDU session, the SMF should set the destination IP address of this application traffic in UPF. The SMF should maintain a mapping table between non-IP related Traffic Descriptor and 3-IP-tuple. + +For example: + +- If the application traffic is applied to a PDU session by Traffic Descriptor = ABC.com (FQDN), the SMF should have a mapping table between ABC.com and the destination IP address of this application traffic, for example, ABC.com (FQDN) is equal to 100.1.1.1; +- If the application traffic is applied to a PDU session by Traffic Descriptor = APP1 (Application Descriptor), the SMF should have a mapping table between APP1 and the destination IP address of this application traffic, for example, APP1 is equal to 192.168.1.1 + +### 6.10.1.2 Network based URSP rules enforcement verification with UE assistance + +Without UE's assistance, the network sides should have the packet detection in every of the UE's PDU session. In order to reduce the burden of network, some of the information should be reported by UE. For example, when UE enforces the URSP rules to apply the application traffic to a PDU session, the UE can report the PDU session ID that the application traffic applied to, and report the URSP rules the UE uses. With the help of UE, there are three level of URSP rules verification: + +- The stage 1 verification: When UE uses the URSP rules (one of the Traffic descriptor and RSD) to apply the application traffic to a PDU session (both existing PDU session or trigger to establish a new PDU session), the UE notifies the AM-PCF via NAS messages which URSP rules is used and which PDU session the application traffic applied to (indicated by PDU session ID). The AM-PCF can check the URSP rules that UE notifies. The URSP rule reported by the UE is inconsistent with the rule delivered by the network, the AM-PCF determines that the UE doesn't use the URSP rules correctly. +- The stage 2 verification: Although the UE notifies the URSP rules it used and the PDU session that the application traffic applied to, the AM-PCF should trigger the SMF to check whether the parameters of the PDU session (for example, the SSC mode, PDU session type and etc) are the same as in RSD. If in the PDU session ID which PDU session refers to and the application traffic applied to, the PDU session parameters are not the same as the parameter indicated in RSD, the AM-PCF can decide that the UE doesn't use the URSP rules correctly. Because the real PDU session parameters are not the same as the parameters in RSD that UE notifies. +- The stage 3 verification: Based on the previous two level of verification, the AM-PCF can decide that UE reports the same URSP rules as network distributed and the PDU session parameters are the same as in RSD that UE reports. But, whether the application traffic exists in the PDU session is unknown. So, the last stage of verification is, the 5GC should use the traffic detection mechanism in the PDU session, to detect whether the application traffic exists. The SMF develops the PDR according to the traffic descriptor and applies the PDR to PDU sessions. If no packet is detected, the SMF notifies the AM-PCF the results and the AM-PCF decides the UE doesn't use the URSP rules correctly. + +## 6.10.2 Procedure + +### 6.10.2.1 Network based URSP rules enforcement verification without UE assistance + +The details of the procedure of network based URSP rules enforcement feedback is in Figure 6.10.2-1. + +![Sequence diagram illustrating Network based URSP rules enforcement feedback. The diagram shows interactions between UE, AMF, PCF, SMF, PSA, UDR, and UDM. The process involves PDU session establishment, PCF deciding on URSP rules, SMF generating PDR, and subsequent traffic detection and reporting.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF + participant SMF + participant PSA + participant UDR + participant UDM + + Note left of PCF: 1. PCF decides which URSP rules in which UE to monitor + PCF->>UDM: 2. Nudm_UECM_Get Request + UDM-->>PSA: 3. Nudm_UECM_Get Response (SMF ID) + PCF->>SMF: 4. Nsmf_EventExposure Subscribe (Packet detection and URSP rules enforcement feedback) + Note left of SMF: 5. SMF generates PDR according to URSP rules + SMF->>PSA: 6. SMF applies PDR to UPF for traffic detection + Note left of UE: 7. URSP rules mapping application traffic to PDU session + Note right of PSA: 8. PSA detects the traffic + PSA->>SMF: 9. N4 reports + SMF->>PCF: 10. Nsmf_EventExposure_Notify + Note left of PCF: 11. PCF re-evaluates the URSP rules + PCF->>UE: 12. URSP rules delivery to UE + +``` + +Sequence diagram illustrating Network based URSP rules enforcement feedback. The diagram shows interactions between UE, AMF, PCF, SMF, PSA, UDR, and UDM. The process involves PDU session establishment, PCF deciding on URSP rules, SMF generating PDR, and subsequent traffic detection and reporting. + +**Figure 6.10.2-1: Network based URSP rules enforcement feedback** + +1. The PCF determines to monitor the URSP rules enforcement in UE. +2. The PCF finds the SMF serving the UE for this SUPI using Nudm\_UECM\_Get\_Request including SUPI, type of requested information set to SMF Registration Info and the S-NSSAI and DNN, as defined in clause 5.3.2.5.7 of TS 29.503 [11]. +3. The UDM provides the SMF id and the corresponding PDU Session id, S-NSSAI, DNN using +4. The PCF subscribes the service in SMF for packet detection. The PCF provides the monitored Traffic Descriptor to SMF via Nsmf\_EventExposure\_Subscribe. The PCF will be notified with the PDU session parameters that the application traffic applied to. + +NOTE: The PCF is AM-PCF, and the subscription procedure can be routed to SMF via SM-PCF. The details are described in the Figure 6.10.2-2. + +5. The SMF receives the parameters of Traffic Descriptor from PCF and generate the PDR. And the SMF should derive the IP descriptor which the Traffic Descriptor corresponds to. + +And in the Traffic Descriptor, the IP descriptor can be directly used for the construction of PDR, that the IP descriptor describes the destination IP address. If for other kinds of Traffic Descriptor, for example, the Application Descriptor, DNN, Domain Descriptor or Connection Capabilities, the SMF derives the 3-IP-tuple which the Application Descriptor, DNN, Domain Descriptor or Connection Capabilities corresponds to by the maintained mapping table between non-IP related Traffic Descriptor and 3-IP-tuple. + +6. The SMF applies the PDR to the UPF that serves the UE via N4 session procedure. +7. In UE, an application traffic is mapped to a PDU session by the monitored URSP rules. +8. The UPF detects the application traffic by PDR in a PDU session. +9. The UPF reports the PDU session information, which the application traffic applied to, to SMF, including the PDU session information, including PDU session id, SSC mode, DNN, access type, S-NSSAI and etc, by N4 reporting procedure. The PDU session information is used to verify the which RSDs are enforced in the Traffic Descriptor in URSP rules. +10. The SMF reports the PDU session information, which the application traffic applied to, to PCF, including the PDU session id, SSC mode, DNN, access type, S-NSSAI and etc by Nsmf\_EventExposure\_Notify. + +11. The PCF verify which RSDs are enforced in the Traffic Descriptor in URSP rules according to PDU session information. And PCF determines the enforcement of UE's URSP rules at this step. If no RSDs are matched to the PDU session information, it means the UE doesn't use the URSP rules correctly. + +The PCF should re-evaluate the URSP rules to this UE and update the URSP rules in UE, if the URSP rules are not enforced correctly. For example, adjust the precedence of Traffic Descriptor or RSD, update the RSDs in Traffic Descriptor, add or remove the Traffic Descriptor and RSDs, etc. + +12. The PCF updates the re-evaluated URSP rules to UE, according to the step from step 5 to step 9 described in clause 4.16.12.2 of TS 23.502 [3]. + +## 6.10.2.2 Network based URSP rules enforcement verification with UE assistance + +![Sequence diagram for Network based URSP rules enforcement verification with UE assistance. Lifelines: UE, AMF, SMF, UPF, AM-PCF, SM-PCF, UDM. The process involves UE applying traffic, AMF sending an update request to AM-PCF, AM-PCF performing stage 1 verification with UDM, SMF performing stage 2 verification, UPF detecting traffic, SMF performing stage 3 verification, and finally AM-PCF adjusting URSP rules in the UE.](43979979715bb3304389a0cb18f34444_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UPF + participant AM-PCF + participant SM-PCF + participant UDM + + Note left of UE: 1. UE uses URSP rules to apply application traffic to PDU session + UE->>AMF: 2. UL NAS (used URSP rules and PDU session ID) + AMF->>AM-PCF: 3. Npcf_UEPolicyControl_Update request (used URSP rules and PDU session ID) + AM-PCF-->>AMF: 4. Npcf_UEPolicyControl_Update response + Note right of AM-PCF: 5. AM-PCF performs the stage 1 verification + AM-PCF->>UDM: 6. Nudm_SDM_Get or Nudm_SDM_Subscribe (Key: SUPI, sub key: S-NSSAI) + UDM-->>AM-PCF: 7. Nudm_SDM_Get response or Nudm_SDM_Subscribe response (PDU session ID, SMF ID, SM-PCF ID) + AM-PCF->>SM-PCF: 8. Npcf_PolicyAuthorization Subscribe (SMF ID, PDU session ID, used URSP rules) + SM-PCF->>SMF: 9. Nsmf_EventExposure Subscribe (Packet detector and URSP rules enforcement feedback) + Note right of SMF: 10. Stage 2 verification: SMF recovers the PDU session parameters and compare with the parameters in URSP rules + SMF-->>SM-PCF: 11. Nsmf_EventExposure Notify + SM-PCF-->>AM-PCF: 12. Npcf_PolicyAuthorization Notify + Note right of SMF: 13. SMF derives PDR according to Traffic Descriptor in used URSP rules + Note right of SMF: 14. SMF determines the UPF or PSA that the PDU session ID related + SMF->>UPF: 15. N4 rules to deliver PDR into UPF for traffic detection + Note right of UPF: 16. UPF or PSA detects the traffic in PDU session + UPF-->>SMF: 17. N4 reporting + SMF-->>SM-PCF: 18. Nsmf_EventExposure Notify (stage 3 results) + SM-PCF-->>AM-PCF: 19. Npcf_PolicyAuthorization Notify + Note right of AM-PCF: 20. AM-PCF performs the stage 2 and stage 3 verification + Note bottom: 21. AM-PCF adjusts the URSP rules in UE + +``` + +Sequence diagram for Network based URSP rules enforcement verification with UE assistance. Lifelines: UE, AMF, SMF, UPF, AM-PCF, SM-PCF, UDM. The process involves UE applying traffic, AMF sending an update request to AM-PCF, AM-PCF performing stage 1 verification with UDM, SMF performing stage 2 verification, UPF detecting traffic, SMF performing stage 3 verification, and finally AM-PCF adjusting URSP rules in the UE. + +Figure 6.10.2-2: Network based URSP rules enforcement feedback with UE assistance + +1. UE performs the URSP rules to apply application traffic to a PDU session, including newly establish a PDU session or apply the application traffic to existing PDU session. + +2. The UE delivers the URSP rules enforcement results to AM-PCF via AMF by UL NAS messages, including the used URSP rules (represented by Traffic Descriptor precedence or RSD precedence, or, represented by details of Traffic Descriptor or RSD), PDU session ID that the application traffic applied to. +3. The AMF delivers the URSP rules enforcement results to AM-PCF by Npcf\_UEPolicyControl\_Update request, including the used URSP rules (represented by Traffic Descriptor precedence or RSD precedence, or, represented by details of Traffic Descriptor or RSD), PDU session ID that the application traffic applied to. +4. The AM-PCF responses to AMF. +5. The AM-PCF performs the stage 1 verification. The AM-PCF can check the URSP rules that UE notifies with the URSP rules AM-PCF delivers to UE. If the URSP rule reported by the UE is inconsistent with the rule delivered by the network, the AM-PCF determines that the UE doesn't use the URSP rules correctly. + +If the AM-PCF determines the UE doesn't use the URSP rules correctly, the step from step 6 to step 19 are skipped. + +NOTE 1: For example, the UE reports the URSP rules is: TD = "FQDN = ABC.com", RSD 1 = "SSC mode 2, DNN = DNN1", but the AM-PCF checks that the real URSP rules delivered to UE is: TD = "FQDN = ABC.com", RSD 1 = "SSC mode 3, DNN = DNN1". So the AM-PCF determines that the UE doesn't use the URSP rules correctly + +- 6-7. The AM-PCF recovers the SMF ID, SM-PCF ID from UDM, with Key = SUPI, Subkey = S-NSSAI or DNN. +8. The AM-PCF triggers the procedure Npcf\_PolicyAuthorization Subscribe to subscribe the packet detection results in certain PDU session. In the subscription, the AM-PCF provides SMF ID, used URSP rules (represented by Traffic Descriptor precedence or RSD precedence, or, represented by details of Traffic Descriptor or RSD), PDU session ID to SM-PCF. +9. The SM-PCF subscribes the service in SMF for packet detection. The PCF provides the monitored Traffic Descriptor to SMF via Nsmf\_EventExposure\_Subscribe. The PCF will be notified with the PDU session parameters that the application traffic applied to. +10. The SMF recovers the PDU session parameters according to PDU session ID, for example, SSC mode, DNN, S-NSSAI, PDU session type and etc. The SMF can have two options to perform stage 2 verification: + - Option 1: The SMF can compare the PDU session parameters with the parameters in RSD. If either one of the parameters is not the same, the SMF notifies the SM-PCF by Nsmf\_EventExposure Notify in step 11, and SM-PCF notifies AM-PCF by Npcf\_PolicyAuthorization\_Notify with the failure results. And the AM-PCF determines that the UE doesn't use the URSP rules correctly. From step 13 to step 19 are skipped. + - Option 2: The SMF only delivers the recovered PDU session parameters to AM-PCF, via SM-PCF in step 11 and step 12. The AM-PCF compares the PDU session parameters with the parameters in RSD. If either one of the parameters is not the same, the AM-PCF determines that the UE doesn't use the URSP rules correctly. From step 13 to step 19 are skipped. +11. (optional) After the SMF compares the PDU session parameters with the parameters in RSD, if either one of the parameters is not the same, the SMF notifies the SM-PCF by Nsmf\_EventExposure Notify with the stage 2 verification failure. +12. (optional) The SM-PCF notifies AM-PCF by Npcf\_PolicyAuthorization\_Notify with the stage 2 verification failure results. +13. The SMF receives the parameters of Traffic Descriptor from SM-PCF and generate the PDR. And the SMF should derive the IP descriptor which the Traffic Descriptor corresponds to. + +And in the Traffic Descriptor, the IP descriptor can be directly used for the construction of PDR, that the IP descriptor describes the destination IP address. If for other kinds of Traffic Descriptor, for example, the Application Descriptor, DNN, Domain Descriptor or Connection Capabilities, the SMF derives the 3-IP-tuple which the Application Descriptor, DNN, Domain Descriptor or Connection Capabilities corresponds to by the maintained mapping table between non-IP related Traffic Descriptor and 3-IP-tuple. + +14. The SMF determines the UPF or PSA that serves the PDU session which indicated by PDU session ID. + +NOTE 2: The SMF triggers the packet detection procedure only after the UE report that a URSP rule have been applied or enforced. + +15. The SMF applies the PDR to the UPF that serves the UE via N4 session procedure. +16. The UPF detects the application traffic by PDR in a PDU session in the certain time range. The results can be either successfully detected or not detected. +17. The UPF reports the packet detection results to SMF, either successfully detected or not detected in the certain time range. +18. The SMF reports the packet detection results to SM-PCF by Nsmf\_EventExposure\_Notify. This packet detection results are used for stage 3 verification. +19. The SM-PCF notifies AM-PCF by Npcf\_PolicyAuthorization\_Notify with packet detection results. +20. The AM-PCF performs stage 2 verification and stage 3 verification: + - Stage 2 verification: The AM-PCF compares the PDU session parameters with the parameters in RSD. If either one of the parameters is not the same, the AM-PCF determines that the UE doesn't use the URSP rules correctly. + - Stage 3: The AM-PCF receives the packet detection results from SMF via SM-PCF. If no packets are detected from the PDU session which indicated by the PDU session ID that UE reports, it means that the real application traffic doesn't exist in the PDU session, and the UE doesn't use the URSP rules correctly. If the packets are detected from the PDU session, the UE uses the URSP rules correctly. +21. The PCF updates the re-evaluated URSP rules to UE, according to the step from step 5 to step 9 described in clause 4.16.12.2 of TS 23.502 [3]. + +### 6.10.3 Impacts on services, entities and interfaces + +**Editor's note:** This clause lists impacts to services and interfaces. + +PCF (AM-PCF or SM-PCF): + +- Decides the monitored URSP rules, and provides the parameters in Traffic Descriptor to SMF to generate PDR. +- Subscribe the packet detection results from SMF to verify the URSP rules enforcement in UE. +- Re-evaluates the URSP rules to the UE and update the URSP rules in UE, if the URSP rules are not enforced correctly according to the notification from SMF. + +SMF: + +- Transition of the Application Descriptor, DNN, Domain Descriptor or Connection Capabilities in Traffic Descriptor to IP descriptor to construct 3-IP-tuple in PDR. +- Receives the monitored Traffic Descriptor which is included in the monitored URSP rules from PCF. +- Provide the traffic detection results to PCF. + +UE: + +- Reports the enforced URSP rules and PDU session ID that the application traffic applied to, to AM-PCF by UL NAS messages. + +## 6.11 Solution #11: 5GC awareness of URSP recognition by UE + +### 6.11.1 Description + +This solution is proposed to address KI#2 to assist 5GC awareness of URSP enforcement. It is beneficial for both the UE and the 5GC to ensure that the URSP rules provisioned to the UE are enforceable. With enforceable + +URSP rules, the mechanisms that allow 5GC to determine when the UE enforces the URSP rules can be followed efficiently. + +Currently the UCU procedure is used to provision UE policy (including URSP policy) to UE. However, the result in the UCU Response message only indicates whether the UE supports the type of UE policy per Policy Section. + +Meanwhile, if UE supports URSP but does not recognize a URSP rule (e.g. due to not recognize the TD parameter in a URSP rule), the UE will ignore(skip) the URSP rule without any notification to the network side. This implicit ignoring will result in the inefficiency for the UE to perform URSP rules evaluation and enforcement and for the 5GC to configure enforceable URSP rules at the UE for routing specific application traffic to a specific route, e.g. expected slice as described in an RSD of a URSP rule. + +Therefore, it is proposed to enhance the UCU procedure so that the UE can indicate in the UL NAS Transport message if and which TD type(s) of the URSP rule are not recognized by UE. + +## 6.11.2 Procedures + +![Sequence diagram illustrating the procedure for delivering UE policies and indicating URSP rule support. The diagram shows interactions between UE, (R)AN, AMF, and PCF. The process starts with the PCF deciding to update the UE Policy (step 0). The PCF sends a Namf_Communication_N1N2MessageTransfer to the AMF (step 1). The AMF then initiates a Network Triggered Service Request to the UE (step 2). The AMF sends a Delivery of UE policies to the UE (step 3). The UE responds with the Result of the delivery of UE policies to the AMF (step 4). The AMF then sends a Namf_Communication_N1MessageNotify to the PCF (step 5). Finally, the UE sends a UL NAS Transport message (status info for URSP) to the AMF (step 6a), which is then forwarded to the PCF (step 6b).](a97518a839da75f8379c578562b01bc2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant PCF + + Note right of PCF: 0. PCF decides to update UE Policy + PCF-->>AMF: 1. Namf_Communication_N1N2MessageTransfer + Note over UE, AMF: 2. Network Triggered Service Request + AMF->>UE: 3. Delivery of UE policies + UE->>AMF: 4. Result of the delivery of UE policies + AMF-->>PCF: 5. Namf_Communication_N1MessageNotify + UE->>AMF: 6a. UL NAS Transport (status info for URSP) + AMF-->>PCF: 6b. Namf_Communication_N1MessageNotify (status info for URSP) + +``` + +Sequence diagram illustrating the procedure for delivering UE policies and indicating URSP rule support. The diagram shows interactions between UE, (R)AN, AMF, and PCF. The process starts with the PCF deciding to update the UE Policy (step 0). The PCF sends a Namf\_Communication\_N1N2MessageTransfer to the AMF (step 1). The AMF then initiates a Network Triggered Service Request to the UE (step 2). The AMF sends a Delivery of UE policies to the UE (step 3). The UE responds with the Result of the delivery of UE policies to the AMF (step 4). The AMF then sends a Namf\_Communication\_N1MessageNotify to the PCF (step 5). Finally, the UE sends a UL NAS Transport message (status info for URSP) to the AMF (step 6a), which is then forwarded to the PCF (step 6b). + +**Figure 6.11.2-1: Result of the delivery of UE policies indicate if and which URSP rule is supported by UE** + +The procedure above is extended from the UCU procedure in clause 4.2.4.3 of TS 23.502 [3]: + +- In step 3, the PCF indicates to the UE via AMF to obtain information from the UE for URSP policy in the UE policy container. +- When receiving the indication, the UE will evaluate each URSP rule in the UE policy container received in step 3, and identify which component(s) of the URSP rule (i.e. TD types) are not recognized by UE. +- The UE indicates corresponding status information of the UE for URSP policy in step 6a. + +Based on the feedback from UE, the PCF may update the parameters (e.g. if some parameters in TD are wrongly configured) and provision the updated URSP to UE again. Whether and how to determine the URSP Rules to be sent to UE based on the feedback received is implementation specific. + +## 6.11.3 Impacts on services, entities and interfaces + +UE: + +- Receive the indication and check the URSP rules when it is provisioned in "Delivery of UE policies" message for reporting unrecognized URSP rules; and +- Provide feedback about which TD type(s) that cannot be recognized in the URSP rule in NAS Transport message. + +PCF: + +- Store TD types that are not recognized by the UE, use them for URSP Rule generation. +- Be configured with local policies to enable checking if the UE recognizes TD types. + +## 6.12 Solution #12: URSP rule enforcement validation via gating control + +### 6.12.1 Description + +This solution addresses Key Issue #2 on validation of URSP rule enforcement. + +For newly detected application, the UE is required to evaluate the URSP rules and associate the application to a specific PDU Session, by initiating PDU Session Establishment procedure or PDU Session Modification procedure, depending on whether existing PDU session can be reused or not. + +While, the core network is not aware of which URSP rule is matched in the UE, not to mention what the detected application is. As the URSP rule is only known to the core network at PSI granularity. + +To resolve the validation of URSP rule enforcement, URSP rule ID is introduced to uniquely identify the URSP rule sent to a UE. When the PCF provides URSP rules to the UE, a rule ID is allocated for each URSP rule and sent to the UE together with the URSP rules, apart from the PSI. When the UE initiates a PDU Session Establishment/Modification request, the UE indicates the URSP rule ID it uses for the request to the network, the network is able to know which URSP rule is enforced by the UE for the request. Further the PCF for the PDU Session when receiving the URSP rule ID transferred by the SMF can retrieve the content of the URSP rule identified by the rule ID from the PCF for the UE or the UDR, and then check if the requested S-NSSAI and DNN requested by the UE matches with the components of the Route Selection Descriptors of the URSP rule, and generate the policy for the session management e.g. allow the application traffic identified by the corresponding Traffic descriptor of the URSP rule, to be transferred via the PDU Session. + +The enhancement is to add a Rule Identifier to URSP rule as defined in the Table 6.6.2.1-2 of the TS 23.503 [4]. + +| | | | | | +|-----------------|----------------------------------------------------------------------------------------------------------------|-------------|-----|------------| +| Rule Identifier | Uniquely identifies the URSP rule, within the UE.<br>It is used between PCF and UE for referencing URSP rules. | Conditional | Yes | UE Context | +|-----------------|----------------------------------------------------------------------------------------------------------------|-------------|-----|------------| + +When detecting there is an unmatched application in the PDU Session, the PCF for the PDU Session may notify the PCF for the UE and the PCF for the UE may decide to update the URSP in the UE. + +NOTE: The UE may use wrong URSP since the URSP in UE is not updated in time. + +Editor's note: It is FFS whether the URSP rule identifier is mandatory. + +Editor's note: User consent is needed for URSP rule ID reporting and the detailed descriptions and procedures of user consent is FFS. + +### 6.12.2 Procedure + +When the UE triggers the PDU Session Establishment procedure or PDU Session Modification Procedure, the rule identifier of the matched URSP rule will be provided to the SMF, and then further provided by the SMF to the PCF for + +validation of the enforcement of the corresponding URSP rule and generate corresponding policy for the session management. + +![Sequence diagram illustrating the PDU Session Establishment/Modification Procedure for URSP enforcement validation. The diagram shows interactions between UE, SMF, UPF, AM PCF, UDR, and SM PCF. The steps are: 1. UE sends PDU Session Establishment/Modification Request to SMF. 2. SMF sends Npcf_SMPolicyControl_Create/Update Request to SM PCF. 3a. SM PCF sends Nudr_DM_Query to UDR. 3b. SM PCF sends Npcf_EventExposure_Subscribe to AM PCF. 4. SM PCF performs Policy Decision based on queried URSP rule. 5. SM PCF sends Npcf_SMPolicyControl_Create/Update Response to SMF. 6. SMF performs PCC Rule enforcement. 7. SMF sends PDU Session Establishment/Modification Accept to UE.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant UPF + participant AM_PCF as AM PCF + participant UDR + participant SM_PCF as SM PCF + + Note right of SM_PCF: 4. Policy Decision based on queried URSP rule + + UE->>SMF: 1. PDU Session Establishment/Modification Request + SMF->>SM_PCF: 2. Npcf_SMPolicyControl_Create/Update Request + SM_PCF->>UDR: 3a. Nudr_DM_Query + SM_PCF->>AM_PCF: 3b. Npcf_EventExposure_Subscribe + SM_PCF->>SMF: 5. Npcf_SMPolicyControl_Create/Update Response + SMF->>UPF: 6. PCC Rule enforcement + SMF->>UE: 7. PDU Session Establishment/Modification Accept + +``` + +Sequence diagram illustrating the PDU Session Establishment/Modification Procedure for URSP enforcement validation. The diagram shows interactions between UE, SMF, UPF, AM PCF, UDR, and SM PCF. The steps are: 1. UE sends PDU Session Establishment/Modification Request to SMF. 2. SMF sends Npcf\_SMPolicyControl\_Create/Update Request to SM PCF. 3a. SM PCF sends Nudr\_DM\_Query to UDR. 3b. SM PCF sends Npcf\_EventExposure\_Subscribe to AM PCF. 4. SM PCF performs Policy Decision based on queried URSP rule. 5. SM PCF sends Npcf\_SMPolicyControl\_Create/Update Response to SMF. 6. SMF performs PCC Rule enforcement. 7. SMF sends PDU Session Establishment/Modification Accept to UE. + +**Figure 6.12.2-1: PDU Session Establishment/Modification Procedure for URSP enforcement validation** + +1. During the PDU Session Establishment/Modification procedure, the URSP rule ID related to the application which triggers the procedure is contained within the SM NAS request message by the UE. +2. The SMF sends Npcf\_SMPolicyControl\_Create/Update request message to the PCF, which includes the URSP rule ID received from the UE. +3. Upon receiving the URSP rule ID, the PCF for the PDU Session can retrieve the content of the corresponding URSP rule by either interacting with PCF for the UE via Npcf\_EventExposure\_Subscribe service operation or with the UDR via Nudr\_DM\_Query service operation (e.g. Policy Set Entry). +4. Based on the received URSP rule, the PCF for the PDU Session first checks whether the PDU Session is associated correctly, e.g. whether the DNN/S-NSSAI or the SSC mode matches with the components of the RSD(s) of the URSP rule. If the PDU Session is associated correctly, the PCF can make policy decision by generating PCC rule(s) corresponding to the application traffic identified by the Traffic descriptor. If the PDU Session is associated incorrectly, the PCF may reject the request message from the SMF. +5. The PCF provides the generated PCC rule(s) based on the URSP received in step 3 to the SMF. In addition, the PCF may set "unmatched application" PCR trigger to the SMF, and the SMF shall report to the PCF for the PDU Session when it determines the application transferred in the PDU Session does not match the URSP rule. +6. The SMF enforces the received PCC rule(s) by providing corresponding N4 rule(s) to the UPF, thus the application traffic of the Traffic descriptor can be transferred via this PDU Session. +7. The SMF responds to the UE with PDU Session Establishment/Modification Accept message, which may contain QoS rule(s) corresponding to the received PCC rule(s). + +After this procedure, upon receiving the service packets, if the UPF determines that the service packets are not aligned with the instruction in N4 rules received from SMF, the UPF will drop the packet and report the unmatched application event (i.e. there is an unmatched packet) to the SMF, then the SMF notifies the PCF for the PDU Session. The PCF for the UE updates the URSP in the UE when receiving the event notification of unmatched application from the PCF for the PDU Session. + +### 6.12.3 Impacts on existing Functions + +The solution has impacts on the following entities: + +#### UE: + +- Supports the reporting of URSP rule ID in PDU Session establishment/modification request. + +#### SMF: + +- Supports procedures for transferring of URSP rule ID to the PCF. +- Reports to the PCF about whether there is an unmatched application event. + +#### UPF: + +- Reports to the SMF about whether there is an unmatched application event. + +#### PCF: + +- Supports procedures for querying the content of the URSP rule from the PCF for the UE. +- Generates the policy for the session management based on the URSP rule. +- Rejects the transmission of application traffic not matching the Traffic descriptor of the URSP. +- Subscribes to PCF for the PDU Session and SMF for notification about whether there is an unmatched application event. +- triggers URSP update based on the unmatched application event. + +## 6.13 Solution #13: URSP enforcement via PDU Session authorization/authentication when UE associating with application + +### 6.13.1 Description + +This solution addresses Key Issue #2 5GC awareness of URSP enforcement. + +Currently for every newly detected application, the UE evaluates the URSP rules to select a Route Selection Descriptor. UE determines to reuse an existing PDU Session or establish a new PDU Session to associate the application, depending on whether an existing PDU Session matches all components in the selected Route Selection Descriptor or not. + +However, 5GC is not aware of which URSP rule the UE matches, and what application the UE detects. To resolve the key issue, a PDU Session authorization/authentication when UE detecting and associating with application is introduced to verify whether the UE should route the specific application traffic to the PDU session or not. + +After UE evaluates the URSP rules to select a Route Selection Descriptor for newly detected application, if UE determines to initiate a PDU Session Establishment, the UE indicates the Rule Precedence of URSP rule it uses for the request to the network, and the application identity. + +NOTE 1: The DN-AAA server may belong to the 5GC or to the DN. + +If the UE provides authentication/authorization information corresponding to an application 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 triggers a PDU Session Establishment authentication/authorization procedure with the DN-AAA Server without involving the UPF if the DN-AAA Server is located in the 5GC and reachable directly. If the SMF determines that authentication/authorization of the PDU Session Establishment is required but the UE has not provided an application identity as part of the PDU Session Establishment request, the SMF requests the UE to indicate an application identity using EAP procedures. If the authentication/authorization of the PDU Session Establishment fails, the SMF rejects the PDU Session Establishment. + +Before the UE reports application identity in PDU Session Establishment request or NAS Authentication Message, the UE shall first obtain user consent. + +NOTE 2: The scenario where to get user intention and consent for UE to report the application identity, which involves UI interaction or message exchanges between UE and user, is not in scope. + +**Editor's note:** The procedures to obtain user consent need to be studied by SA WG3. + +If UE determines to reuse the existing PDU Session for the newly detected application, UE shall initiate a PDU Session Establishment Request and includes the Rule Precedence of URSP rule and application identity. The SMF may trigger the PDU Session establishment authentication/authorization procedure with the DN-AAA Server. DN-AAA Server based on the SMF policy associated with the DN confirms the successful authentication/authorization of the PDU Session for the specific application. The SMF shall reuse the existing PDU Session and accept the PDU Session Establishment, without establish a new PDU session. + +NOTE 3: Application identity is the subscription identity of Network Slice Customer (NSC), and able to map to the DN-AAA server. + +Further, the PCF for SM policy control, when receiving the Rule Precedence of URSP rule transferred by the SMF, can retrieve the content of the URSP rule identified by the Rule Precedence from the PCF for AM policy control, and then check if the requested S-NSSAI and DNN requested by the UE matches with the components of the Route Selection Descriptors of the URSP rule, and generate the policy for the session management e.g. allow the application traffic identified by the corresponding Traffic descriptor of the URSP rule. + +## 6.13.2 Procedures + +![Sequence diagram illustrating the PDU Session Establishment Procedure for URSP enforcement. The diagram shows interactions between UE, SMF, PCF, and DN. The steps are: 1. UE sends PDU session Establishment Request (Rule Precedence, APP identity) to SMF. 2. SMF sends Authentication/Authorization Request to DN. 3. DN sends NAS Authentication Request Message (APP identity) to SMF. 4. SMF sends NAS Authentication Response Message to UE. 5. DN sends Authentication/Authorization Response to SMF. 6. SMF sends Npcf_SMPolicyControl_Create/Update Request (Rule Precedence) to PCF. 7. PCF makes a Policy decision. 8. PCF sends Npcf_SMPolicyControl_Create/Update Response to SMF. 9. SMF performs PCC enforcement. 10. SMF sends PDU session Establishment Accept to UE.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant PCF + participant DN + Note right of PCF: 7. Policy decision + Note right of SMF: 9. PCC enforcement + + UE->>SMF: 1. PDU session Establishment Request (Rule Precedence, APP identity) + SMF->>DN: 2. Authentication/Authorization Request + DN-->>SMF: 3. NAS Authentication Request Message (APP identity) + SMF-->>UE: 4. NAS Authentication Response Message + DN-->>SMF: 5. Authentication/Authorization Response + SMF->>PCF: 6. Npcf_SMPolicyControl_Create/Update Request (Rule Precedence) + PCF-->>SMF: 8. Npcf_SMPolicyControl_Create/Update Response + SMF-->>UE: 10. PDU session Establishment Accept + +``` + +Sequence diagram illustrating the PDU Session Establishment Procedure for URSP enforcement. The diagram shows interactions between UE, SMF, PCF, and DN. The steps are: 1. UE sends PDU session Establishment Request (Rule Precedence, APP identity) to SMF. 2. SMF sends Authentication/Authorization Request to DN. 3. DN sends NAS Authentication Request Message (APP identity) to SMF. 4. SMF sends NAS Authentication Response Message to UE. 5. DN sends Authentication/Authorization Response to SMF. 6. SMF sends Npcf\_SMPolicyControl\_Create/Update Request (Rule Precedence) to PCF. 7. PCF makes a Policy decision. 8. PCF sends Npcf\_SMPolicyControl\_Create/Update Response to SMF. 9. SMF performs PCC enforcement. 10. SMF sends PDU session Establishment Accept to UE. + +**Figure 6.13.2-1: PDU Session Establishment Procedure for URSP enforcement** + +1. During the PDU Session Establishment procedure, UE includes Rule Precedence of URSP rule and application identity in SM NAS request message. +2. SMF triggers the PDU Session establishment authentication/authorization directly with DN-AAA Server based on the SMF policy associated with the DN. +3. DN-AAA Server sends an Authentication/Authorization message towards UE including application identity. +4. Transfer of DN Request Container information received from UE towards the DN-AAA. +5. The DN-AAA Server confirms the successful authentication/authorization of the PDU Session associating with the application. +6. Within the Npcf\_SMPolicyControl\_Create/Update request message, SMF provide the Rule Precedence to the PCF. +7. Upon receiving the Rule Precedence of URSP rule, the PCF can retrieve the content of the corresponding URSP rule directly or from the UDR. Based on the received URSP rule, the PCF checks whether the UE associated the correct PDU Session according to the Route Selection Descriptor of the URSP rule. If the PDU Session is associated correctly, the PCF can make policy decision by generating PCC rule(s). If the PDU Session is associated incorrectly, the PCF may reject the request message from SMF. + +8. The PCF provides the generated PCC rule(s) to the SMF. +9. The SMF enforces the received PCC rule(s) by providing corresponding N4 rule(s) to the UPF, thus the traffic can be transferred via this PDU Session. +10. The SMF responds to the UE with PDU Session Establishment Accept message, which may contain QoS rule(s) corresponding to the received PCC rule(s). + +### 6.13.3 Impacts on services, entities and interfaces + +The solution has impacts in the following entities: + +#### UE: + +- Needs to support the reporting of Rule Precedence and application identity in PDU Session Establishment request. +- Needs to support secondary Authentication/Authorization based on the application identity. +- Needs to support to initiate a PDU session Establishment request if UE determines to reuse the existing PDU Session for the newly detected application after UE evaluates the URSP rules to select a Route Selection Descriptor. + +#### SMF: + +- Needs to support procedures for transferring of Rule Precedence to the PCF. +- Needs to support procedures for transferring of application identity to the DN-AAA Server in Authentication/Authorization Request in PDU session establishment procedure. + +#### PCF: + +- Needs to support procedures for querying the content of the URSP rule based on received Rule Precedence of URSP rule. +- Needs to generate the policy for the session management based on the URSP rule, and reject the transmission of application traffic if not matching with the Traffic descriptor of the URSP. + +## 6.14 Solution #14: 5GC awareness of URSP rule evaluation and verification of network slice usage + +### 6.14.1 Description + +This solution addresses Key Issue #2: "5GC awareness of URSP enforcement". + +This solution is intended to be used when a specific network slice has been deployed for the exclusive usage of an application service provider. Business agreements between the MNO and the application service provider guarantee that the network slice only carries traffic from the applications of the application service provider. + +URSP rules are enhanced with an optional indication that a URSP rule is subject to application registration along with the address of an Application Function. When receiving a URSP rule with this indication, the UE verifies that the user consents to application registration (e.g. based on pre-configuration by the user or interaction with the user); if not, then the UE rejects this URSP rule and discards it. + +When the evaluation of a URSP rule subject to application registration triggers the establishment of a new PDU Session, the UE first performs application registration with the indicated AF (unless this has been done previously for the application requesting data transmission), and then initiates PDU Session Establishment, including in the PDU Session Establishment Request the Traffic Descriptor of the matched URSP rule, and the application identity obtained during application registration. The SMF may verify that the indicated application identity is trusted and that the S-NSSAI is allowed for this application identity according to operator policy. If this verification fails, the SMF rejects the PDU Session Establishment Request with a proper cause value and the UE evaluates remaining URSP rules for routing the user data from this application. + +When the evaluation of a URSP rule subject to application registration leads to routing the user data from a new application in an already established PDU Session, the same as above applies except that PDU Session Modification is used instead of PDU Session Establishment. + +Application registration takes place between the UE and the AF, and the UE provides to the AF an identifier recognized by the AF, that is linked with the business agreement between the MNO and the application service provider, and known to the application running in the UE, but that does not need to reveal the exact application used as multiple applications involved with the application service provider may use the same identifier with the AF. Then, the AF provides the UE with the application identity that the UE will present to the SMF at PDU Establishment Request. + +NOTE: A mechanism for verification of the application identity needs to be defined by SA WG3. + +Editor's note: The SMF verification of the application identity based on local policies needs to be detailed. + +## 6.14.2 Procedures + +### 6.14.2.1 Overall procedure + +![Sequence diagram illustrating the overall procedure for 5GC awareness of URSP rule evaluation and verification of network slice usage. The diagram shows interactions between UE, AMF, PCF (AM/UE), SMF, and AF.](9e9104f9ba7eec1259a7893c6380ca1b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF as PCF (AM/UE) + participant SMF + participant AF + + Note left of UE: 1. Delivery of URSP rule(s) including an indication that it is subject to application registration along with AF address + Note left of UE: 2. URSP rule evaluation + UE-->>AF: 3. Application registration + Note left of AMF: 4a. PDU Session Establishment/Modification Request (SM container containing Traffic Descriptor of the matched URSP rule, application identity) + AMF->>SMF: 4b. Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_CreateSMContext (SM container) + Note right of SMF: 5. Verification + SMF->>AMF: 6. PDU Session Establishment/Modification accept/reject + +``` + +Sequence diagram illustrating the overall procedure for 5GC awareness of URSP rule evaluation and verification of network slice usage. The diagram shows interactions between UE, AMF, PCF (AM/UE), SMF, and AF. + +Figure 6.14.2.1-1: 5GC awareness of URSP rule evaluation and verification of network slice usage + +1. UE Policies are delivered to the UE using the current, existing mechanism of UE Configuration Update procedure for transparent UE Policy delivery, see clause 4.2.4.3 of TS 23.502 [3]. One or more URSP Rule contains an indication that it is subject to application registration along with the address of an AF. The UE may, based on local privacy settings and/or interaction with the user, reject URSP rules containing an indication that it is subject to application registration; in this case the UE indicates to the AMF the URSP rule(s) that it rejects due to not allowing application registration for this URSP rule. +2. The evaluation of a URSP rule subject to application registration triggers the establishment of a new PDU Session (case a) or leads to routing the user data from a new application in an already established PDU Session (case b). +3. If the UE had previously performed application registration for the application requesting data transmission and for this URSP rule, the procedure continues with step 4. Otherwise, the UE performs application registration (see clause 6.14.2.2) with the AF which address was indicated in the URSP rule. + +4. The UE sends a PDU Session establishment request (case a) or a PDU Session Modification request (case b), including the Traffic Descriptor of the matched URSP rule, and the application identity obtained during application registration. +5. The SMF verifies that the indicated application identity is valid and that the S-NSSAI is allowed for this application identity according to operator policy. +6. Depending on the outcome of step 5, the PDU Session establishment or modification is accepted or rejected with a cause value indicating that the S-NSSAI is not allowed for this application identity; in the latter case, the UE evaluates remaining URSP rules for routing the user data from this application. + +#### 6.14.2.2 Application registration + +This call flow depicts an expanded view of step 3 in clause 6.14.2.1. + +**Editor's note:** Whether this procedure uses CP or UP is FFS. + +![Sequence diagram for Application registration showing interactions between UE and AF.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +``` +sequenceDiagram + participant UE + participant AF + Note right of AF: 2. Authentication/authorization + UE->>AF: 1. Application registration request + AF-->>UE: 3. Application registration response +``` + +The diagram illustrates the application registration process between a User Equipment (UE) and an Application Function (AF). The sequence of messages is as follows: 1. The UE sends an 'Application registration request' to the AF. 2. A dashed box labeled 'Authentication/authorization' indicates a process occurring between the UE and the AF. 3. The AF sends an 'Application registration response' back to the UE. + +Sequence diagram for Application registration showing interactions between UE and AF. + +**Figure 6.14.2.2-1: Application registration** + +1. The UE sends an application registration request to the AF, including an identifier recognized by the AF (which need not be the AppID used in the UE's OS). User identity is not included. +2. The AF authenticates and authorizes the request. This may involve one or more additional messages between the UE and the AF. +3. The AF sends a registration response to the UE, including an application identifier that can be used at step 4 of clause 6.14.2.1. + +#### 6.14.3 Impacts on services, entities and interfaces + +UE: + +- Support URSP rules subject to application registration and related procedures. + +PCF: + +- Support URSP rules subject to with application registration. +- Nsmf\_PDUSession\_UpdateSMContext and Nsmf\_PDUSession\_CreateSMContext: support application identity verification. + +AF: + +- New service if CP is used for application registration. + +## 6.15 Solution #15: UE URSP enforcement validation by the network + +### 6.15.1 Description + +This solution addresses the bellow requirements from Key Issue #2: 5GC awareness of URSP enforcement. + +- Whether and how the 5GC can be made aware whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on the URSP rule provisioned by 5GC. +- Whether there are any actions the 5GS can take after 5GC is aware whether the UE enforces a URSP rule for specific application traffic or not. If any, what action 5GC should take? + +The solution allows for UE enforcement to follow correctly the URSP rules for traffic matching. It introduces Application identity parameter provisioned to the PCF by the UE during PDU Session Establishment procedure. The PCF performs URSP validity check in order to validate whether the UE correctly enforces the traffic matching rules in the URSP for the Application requiring the service. If the PCF finds out that the URSP rules are not correctly followed by the UE, the PDU Session is rejected with a new cause to indicate that the URSP rules in general or a specific URSP rules are not followed. Also, the PCF may optionally trigger UE Policy Update procedure to refresh the URSP rules in the UE with the latest version of the URSP rules. + +### 6.15.2 Procedures + +![Sequence diagram illustrating the UE's URSP enforcement validation by the network. The diagram shows the interaction between UE, AMF, SMF, and PCF. The UE sends a PDU Session Establishment Request (step 1) to the AMF. The AMF performs SMF selection (step 2) and sends an Nsmf_PDUSession_CreateSMContext Request (step 3) to the SMF. The SMF initiates the PDU Session Establishment procedure (step 4) as per TS23.502, clause 4.3.2.2.1, steps 4 to 7a. The SMF then sends an Npcf_SMPolicy_Control_Create (step 5) to the PCF. The PCF performs a UE URSP rules validity check (step 6). If the check fails, the PCF sends an Npcf_SMPolicy_Control_Create Response (step 7) with a failure cause of 'URSP rules not followed'. The SMF then sends an Nsmf_PDUSession_CreateSMContext Response (step 8) with the same reject cause to the AMF. The AMF sends a PDU Session Establishment Reject (step 9) to the UE. The PCF also triggers a UE Policy update (step 10) as per TS23.502, clause 4.2.4.3.](9e4f582a5d5f6742d1372956db0f8f0b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant PCF + Note right of PCF: 6. UE URSP rules validity check fails + UE->>AMF: 1. PDU Session Establishment Request (PDU_Session_ID, DNN, S -NSSAI, App_ID) + AMF->>AMF: 2. SMF selection + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request (UE_ID, PDU_Session_ID, DNN, S -NSSAI, User location, App_ID) + Note over AMF, SMF: 4. PDU Session Establishment procedure as per TS23.502, clause 4.3.2.2.1, steps 4 to 7a + SMF->>PCF: 5. Npcf_SMPolicy_Control_Create (UE_ID, PDU_Session_ID, DNN, S -NSSAI, App_ID, UE_location) + Note right of PCF: 6. UE URSP rules validity check fails + PCF->>SMF: 7. Npcf_SMPolicy_Control_Create Response (Failure, reject cause = URSP rules not followed) + SMF->>AMF: 8. Nsmf_PDUSession_CreateSMContext Response (reject cause = URSP rules not followed) + AMF->>UE: 9. PDU Session Establishment Reject (reject cause = URSP rules not followed) + Note right of PCF: 10. URSP rules in the UE update trigger + Note over UE, AMF, SMF, PCF: 11. UE Policy update as per TS23.502, clause 4.2.4.3 + +``` + +Sequence diagram illustrating the UE's URSP enforcement validation by the network. The diagram shows the interaction between UE, AMF, SMF, and PCF. The UE sends a PDU Session Establishment Request (step 1) to the AMF. The AMF performs SMF selection (step 2) and sends an Nsmf\_PDUSession\_CreateSMContext Request (step 3) to the SMF. The SMF initiates the PDU Session Establishment procedure (step 4) as per TS23.502, clause 4.3.2.2.1, steps 4 to 7a. The SMF then sends an Npcf\_SMPolicy\_Control\_Create (step 5) to the PCF. The PCF performs a UE URSP rules validity check (step 6). If the check fails, the PCF sends an Npcf\_SMPolicy\_Control\_Create Response (step 7) with a failure cause of 'URSP rules not followed'. The SMF then sends an Nsmf\_PDUSession\_CreateSMContext Response (step 8) with the same reject cause to the AMF. The AMF sends a PDU Session Establishment Reject (step 9) to the UE. The PCF also triggers a UE Policy update (step 10) as per TS23.502, clause 4.2.4.3. + +Figure 6.15.2-1: UE's URSP enforcement validation by the network + +1. An Application in the UE requires service. The UE initiates PDU Session Establishment Request message in which the UE includes the UE\_ID, the PDU\_Session\_ID, the S-NSSAI and the DNN. The UE selects the S-NSSAI and the DNN based on the URSP rules applicable for the Application requiring service. The UE also includes the App\_ID of the Application in the PDU Session Establishment Request message. + +NOTE: The UE obtains the App\_ID when the Application is registered with the AF (Service provider) and it is not in the scope of this study. The link between the App\_ID and the Application on the UE itself is only known to the Service provider. + +2. SMF selection by the AMF. +3. The AMF invokes either Nsmf\_PDUSession\_CreateSMContext\_Request message to the SMF if there is no association with it or Nsmf\_PDUSession\_UpdateSMContext\_Request message if the AMF is already associated with a SMF. Along with the UE\_ID, the S-NSSAI, the DNN and the User location parameters, the AMF also forwards to the SMF the App\_ID received by the UE. +4. Continue with PDU Session Establishment procedure according to steps 4 to 7a of clause 4.3.2.2.1 of TS 23.502 [3]. +5. The SMF initiates the SM Policy Association Establishment procedure and the SMF sends the Npcf\_SMPolicy\_Control\_Create message to the PCF in which the SMF includes the UE\_ID, the S-NSSAI, the DNN, the User location and the App\_ID parameters. +6. The PCF performs URSP validity check for the UE. The PCF retrieves the stored latest version of the URSP rules for the UE and the PCF verifies whether the UE is following correctly the S-NSSAI selection rules, the DNN selector rules, the Time window criteria and the Location criteria. +7. If the result from the URSP validity check by the PCF is that one or more of the traffic matching rules in the latest version of the URSP are not correctly followed by the UE, the PCF returns Failure parameter in the Npcf\_SMPolicy\_Control\_Create response to the SMF. The PCF may also include the cause for the failure, e.g. URSP rules not followed or a more specific reject cause identifying the specific URSP rule that is not followed by the UE. +8. The SMF forwards the reject cause to the AMF in the Nsmf\_PDUSession\_CreateSMContext\_Response message. +9. The AMF rejects the PDU Session Establishment Request from the UE and the AMF includes a rejection cause URSP rules not followed or a more specific reject cause pointing to which URSP rules are not followed (e.g. S-NSSAI selection rules not followed or DNN selection rules not followed or Time windows criteria not followed or Location criteria not followed). +10. If at step 6 the URSP validity check by the PCF fails, the PCF may assume the UE may not have the latest URSP rules so, the PCF may trigger UE Policy update procedure according to clause 4.2.4.3 of TS 23.502 [3] to refresh the UE with the latest URSP rules. +11. UE Policy update according to clause 4.2.4.3 of TS 23.502 [3]. + +### 6.15.3 Impacts on services, entities and interfaces + +UE, AMF, SMF: + +- New App\_ID parameter and a new PDU Session Establishment reject cause. + +PCF: + +- New App\_ID parameter and URSP validity check functionality. + +## 6.16 Solution #16: URSPs into PCO for EPC + +### 6.16.1 Description + +The solution address KI#3. In this solution, two different aspects are covered: + +- Provide the use case examples and scenarios where the UE may need URSP when in EPS. +- How to provision the URSP to UE when served by the EPS. + +#### 6.16.1.1 Use cases and scenarios + +When a UE attaches initially in EPC or when the UE handovers from 5GC to EPC, PCF may need to update the URSPs in the UE: + +- During Initial attach procedure in EPS due to for example: + - New AF guidance on URSP request applicable to the UE was sent by an AF while the UE is deregistered and prior to the EPC attach procedure, so the corresponding URSP rules were not delivered yet to the UE. + - Operator policies configured with time, location or any other condition are met when the UE attaches to EPC, implying new or updated URSP rules apply under those conditions. + - Operator policies for determining URSPs were updated by the operator while the UE is deregistered and prior to the EPC attach procedure, so the corresponding URSP rules were not delivered yet to the UE. +- At any time a URSP is changed while the UE is registered in EPC (coming from EPC initial attachment or after handover from 5GC) due to for example: + - New AF guidance on URSP request applicable to the UE is sent by an AF. + - Due to time, location change or other network condition the PCF determines that an operator policy configured for the operator for URSP determination applies in the new network conditions, implying new or updated URSP rules apply to the UE. + +### 6.16.1.2 Background: URSP provisioning to a UE in 5GS + +In 5GC URSP updates are delivered from the PCF to the UEs following the procedure defined in clause 6.1.2.2.2 of TS 23.503 [4] for the distribution of the policies to UE. The distribution of UE policies is based on a protocol defined between the UE and the PCF described in TS 24.501 [7] and called UPDP protocol (UE Policy Delivery Protocol) and summarized in the figure below. The UPDP messages are then encapsulated into N1 Policy Containers and transferred transparently by the AMF from/to the UEs. + +![Sequence diagram illustrating URSP provisioning to a UE in 5GS. The diagram shows two main procedures between a UE and a PCF. The first is a 'UE-initiated UE state indication procedure' where the UE sends a 'UE STATE INDICATION' message to the PCF. The second is a 'Network-requested UE policy management procedure' where the PCF sends a 'MANAGE UE POLICY COMMAND' to the UE. The UE then responds with either 'MANAGE UE POLICY COMPLETE' or 'MANAGE UE POLICY COMMAND REJECT'. The PCF starts a timer T3501 upon sending the command and stops it upon receiving either response.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCF + Note over UE, PCF: UE-initiated UE state indication procedure + UE->>PCF: UE STATE INDICATION + Note over UE, PCF: Network-requested UE policy management procedure + PCF->>UE: MANAGE UE POLICY COMMAND + Note right of PCF: Start T3501 + UE-->>PCF: MANAGE UE POLICY COMPLETE + Note right of PCF: Stop T3501 + Note right of PCF: OR + UE-->>PCF: MANAGE UE POLICY COMMAND REJECT + Note right of PCF: Stop T3501 + +``` + +Sequence diagram illustrating URSP provisioning to a UE in 5GS. The diagram shows two main procedures between a UE and a PCF. The first is a 'UE-initiated UE state indication procedure' where the UE sends a 'UE STATE INDICATION' message to the PCF. The second is a 'Network-requested UE policy management procedure' where the PCF sends a 'MANAGE UE POLICY COMMAND' to the UE. The UE then responds with either 'MANAGE UE POLICY COMPLETE' or 'MANAGE UE POLICY COMMAND REJECT'. The PCF starts a timer T3501 upon sending the command and stops it upon receiving either response. + +**Figure 6.16.1.2-1: URSP provisioning to a UE in 5GS** + +The operation UE STATE INDICATION is used by the UE to provide to the PCF the list of stored PSIs which identify the Policy Sections stored in the UE. + +The Network-requested UE Policy management procedure is used by the PCF to deliver an update of UE Policies to the UE. First the PCF sends the operation MANAGE UE POLICY COMMAND including the update of UE policies to the UE. Then the UE answer to the PCF with MANAGE UE POLICY COMPLETE or MANAGE UE POLICY COMMAND REJECT. + +### 6.16.1.3 How to provision URSP to a UE in EPC + +This solution proposes a mechanism that allows the network to update the URSPs for a UE in EPC, by encapsulating UPDP messages into a new ePCO parameter (from now on UE Policy Container ePCO) and transfer them to the UE via PDN connection. + +In this clause, the PCF refers to a deployment where the PCF serving the UE and the PCF serving each of the PDU Sessions for this UE are the same PCF. + +The solution assumes the same protocol (UPDP protocol) for URSP delivery between the PCF and the UE than in 5GC, although the final decision on this is up to stage 3. + +The mechanism reuses the existing capability of the EPC network for sending ePCO from the UE to the SMF+PGW-C (and vice versa) and in addition it proposes a way to transport the UE Policy Container from the SMF+PGW-C to the PCF (and vice versa) based on reusing existing PDU session procedures. + +For the delivery of URSPs to UEs in EPC, this solution assumes the standard solution for interworking architecture between EPC and 5GC as described in TS 23.501 [2]. + +When the PCF needs to send a UE Policy update towards the UE in EPC, it invokes a SM Policy Association Modification including the corresponding UPDP message into a new IE (UE Policy Container) in the N7 interface. When the SMF+PGW-C receives this new IE the SMF+PGW-C encapsulates it into UE Policy Container ePCO and transfers them to the UE by using existing procedure of PDN GW initiated bearer modification without bearer QoS update as defined in clause 5.4.3 of TS 23.401 [8]. + +When the UE in EPC needs to send a UPDP message towards the PCF in relation to UE Policy handling the UE first encapsulates the UPDP message into a UE Policy Container ePCO and then transfers it towards the SMF+PGW-C by reusing existing mechanisms. When the SMF+PGW-C receives such UE Policy Container ePCO from the UE, just forwards transparently the UE Policy Container towards the PCF by reusing SMF initiated SM Policy Association procedure (establishment or modification). + +The solution also proposes that the UE has to be able to handle the reception of such UPDP messages received over EPC NAS signalling in a similar way than when received over 5GC NAS signalling in 5GC. + +In addition, for those events happening in PCF which may trigger the sending of a URSP update for a UE (as described in clause 6.16.1.1), the PCF will check if the UE is currently in EPC, and if so will use one of these PDU sessions to trigger the delivery of the URSP updates, by invoking PCF initiated SM Policy Association modification procedure including the proper UE Policy Container. + +Clause 6.16.1.4 describes the solution for deployments where the PCF for the UE (PCF-UE from now on) and the PCF for the PDU Session (PCF-SM from now on) are different PCFs and there are multiple PCFs for the PDU session. + +### 6.16.1.4 Deployments where the PCF for the PDU session and the PCF for the UE are different PCFs + +The solution utilizes the establishment of a UE Policy Association between the PCF-SM and the PCF-UE for the purpose of the delivery and handling of URSP updates for a UE in EPC. Therefore, the PCF-SM is responsible to transfer UE Policy Containers received from the UE over N7 towards PCF-UE and also to receive those UE Policy Containers from the PCF-UE and to transfer them towards the UE via SMF+PGW-C over N7 procedures. + +The PCF-SM is a new consumer of the Npcf\_UEPolicyControl service for the purpose of providing URSP updates to the UE in EPC. The communication between the PCF-SM and the SMF+PGW-C for the sending and reception of UE Policy Containers from/to the UE is according to the existing proposal for deployments where the PCF serving the UE and the PCF serving each of the PDU Sessions of this UE are the same PCF as described in clause 6.16.1.3. + +For the initial attach of a UE in EPC it is proposed the PCF-SM triggers the establishment of a UE Policy Association towards PCF-UE upon a PDU session establishment is requested by SMF+PGW-C including a UE Policy Container. + +For the case where the UE moves from 5GS to EPC it is proposed the PCF-SM triggers the establishment of a UE Policy Association towards the PCF-UE upon the SMF+PGW-C notifies the PCF-SM about the UE is moved to EPC. + +For the case where the UE moves from EPC to 5GS the proposal is that the PCF-SM terminates any ongoing UE Policy Association established towards the PCF-UE when it is notified from the SMF+PGW-C. + +Once the UE Policy Association is established between the PCF-SM and the PCF-UE, the PCF-UE may decide at any time to send an update of URSPs to the UE in EPC, e.g. triggered by an AF guidance on URSP request. In addition, the PCF-UE is also able to provide an URSP update at UE Policy Association from PCF-SM when the UE initially attaches in EPC or when the UE moves from 5GS to EPC. + +For the case where the UE moves from 5GS to EPC the following is proposed in relation with the establishment of a UE Policy Association from the PCF-SM: + +- It is proposed to add an extension of the UE Policy Container which the UE sends at 5GS initial registration, so the UE may include an indication about whether the UE supports URSP delivery when in EPC. Then the PCF-UE stores that indication in UDR for the UE during 5GS initial registration as part of UE context policy control subscription information. When the UE moves to EPC, the PCF-SM determines whether the UE supports URSP delivery in EPC by checking UE context policy control subscription information in UDR and uses such indication to decide whether to establish a UE Policy Association towards the PCF-UE. +- If there are multiple ongoing PDU sessions for the UE handled in the same PCF-SM (e.g. in a deployment where the same PCF-SM handles all the PDU sessions for an S-NSSAI), the PCF-SM controls that only one UE Policy Association is established and maintained for the same UE. That is, the PCF-SM will establish the UE Policy Association only for the first PDU session which reports the change to EPC. In addition, the PCF-SM will terminate the UE Policy Association at the time the last PDU session for this UE is terminated. + +The PCF-UE is able to send a URSP update to a UE which has moved from 5GS to EPC if there is at least one ongoing PDU session for the UE in the PCF-SM, no matter if some PDU sessions have been terminated after the UE moves to EPC. + +- For the case where there are multiple PCF-SMs handling PDU sessions for the UE it is proposed to extend the operation Npcf\_UEPolicyControl\_Create with an indication (e.g. "Handover5GtoEPC") about whether the scenario triggering the establishment of the UE Policy Association is due to a handover from 5GS to EPC. + +With such indication the PCF-UE is able to correlate all these UE Policy Associations from different PCF-SMs and avoid the re-sending of URSP updates for each of the UE Policy associations. At the time the PCF-UE determines an update of URSP is needed for a UE, the PCF-UE will first select one of the UE Policy Associations for this UE including the new indication and use it for the URSP update delivery. + +With this proposal the PCF-UE is able to send a URSP update to a UE which has moved from 5GS to EPC if there is at least one ongoing PDU session for the UE in at least one PCF-SM, no matter if some PDU sessions have been terminated in some PCF-SMs after the UE moves to EPC. + +- Upon the reception of UE Policy Association establishment from PCF-SM including an empty UE Policy Container (the PCF-SM doesn't receive the UE Policy Container from the UE at 5GS to EPC) and the new indication (i.e. "Handover5GtoEPC"), the PCF-UE gets the information about the PSIs stored in the UE (and other info that the UE includes in the UE Policy Container in Initial Registration in 5GS) from the former UE Policy Association for this UE which was established when the UE was in 5GS. + +For scenarios with N26, according to clause 4.11.1.2.1 of TS 23.502 [3], the AMF deletes the UE Policy Association when the UE moves to EPC and it is not clear whether this deletion happens after or before the SMF+PGW-UE notifies the PCF-SM about the change to EPC. So, it is unknown whether the PCF-UE deletes the ongoing UE Policy Association (from 5GS) before the new one from PCF-SM (from EPC) is established. + +In order to avoid that the information included in the former UE Policy association from 5GS is deleted in PCF-UE before the new one from PCF-SM is established, it is proposed to extend the operation for deletion of the UE Policy Association (Npcf\_UEPolicyControl\_Delete) with a new indication (e.g. "Handover5GtoEPC") about whether the scenario triggering the deletion of the UE Policy Association is due to a handover from 5GS to EPC. When the AMF initiates the deletion because a handover from 5GS to EPC, the AMF includes such indication so the PCF-UE may delay the removal of the associated information for the ongoing UE Policy Association during a while, to wait for the establishment of the new UE Policy Associations from the PCF-SM. + +In addition, when the PCF-UE delays the removal of the UE Policy Association, the PCF-UE delays other additional actions related with the removal of the association as the unbinding from the BSF or un-subscription to receive notifications from UDR, therefore unnecessary signalling due to the unbinding and immediate binding from BSF and un-subscription and immediate subscription to UDR again is avoided. + +- When the PCF-SM needs to establish a UE Policy Association triggered by a 5GS to EPC handover, the PCF-SM first discovers the address of the PCF-UE by querying the BSF. This together with the one in previous bullet + +(i.e. "Handover5GtoEPC"), makes possible that the PCF-SM selects the same PCF-UE handling the UE Policy Association in 5GS, therefore the PCF-UE that receives the new UE Policy Association from the PCF-SM is able to get the list of PSIs stored in the UE from the former UE Policy Association in 5GS. + +In the case of different PCF-SMs are handling PDU sessions for the same UE, the PCF-UE selected by all of them will be the same PCF-UE. For the case of EPC initial attach the PCF-SM selects the PCF-UE based on the information retrieved from NRF query. + +## 6.16.2 Procedures + +### 6.16.2.1 Initial Attach procedure in EPC + +For the initial attachment of a UE in EPC, the procedure follows the one defined in clause 5.3.2.1 of TS 23.401 [8] with the following additions summarized in the figure below for the support of URSP deliveries to the UE: + +![Sequence diagram of the Initial Attach procedure in EPC. The diagram shows interactions between UE, eNB, MME, SGW, SMF/PGW-C, and PCF. The UE sends an Attach Request with UE STATE INDICATION to the eNB. The eNB forwards it to the MME. The MME sends a Create Session Request to the SGW. The SGW forwards it to the SMF/PGW-C. The SMF/PGW-C sends an Npcf_SMPolicyControl_Create req to the PCF. The PCF responds with Npcf_SMPolicyControl_Create Ans. The diagram also indicates a standard continuation of E-UTRAN Initial Attach and subsequent steps for URSPs update initiated by PCF.](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNB + participant MME + participant SGW + participant SMF/PGW-C + participant PCF + + Note left of UE: UE generates UE STATE INDICATION UPDP message + UE->>eNB: 1. Attach Request (UE STATE INDICATION) + eNB->>MME: 2. Attach Request (UE STATE INDICATION) + MME->>SGW: 3. Create Session Request (UE STATE INDICATION) + SGW->>SMF/PGW-C: 4. Create Session Request (UE STATE INDICATION) + SMF/PGW-C->>PCF: 5. Npcf_SMPolicyControl_Create req (UE STATE INDICATION) + PCF-->>SMF/PGW-C: 6. Npcf_SMPolicyControl_Create Ans (...) + Note right of SMF/PGW-C: 7. Standard continuation of E-UTRAN Initial Attach as described in 23.401 5.3.2.1 + Note right of PCF: 8. PCF processes UE STATE INDICATION + Note right of SMF/PGW-C: Steps 2-14 of the procedure described in section 6.X.2.2 for URSPs update initiated by PCF + +``` + +Sequence diagram of the Initial Attach procedure in EPC. The diagram shows interactions between UE, eNB, MME, SGW, SMF/PGW-C, and PCF. The UE sends an Attach Request with UE STATE INDICATION to the eNB. The eNB forwards it to the MME. The MME sends a Create Session Request to the SGW. The SGW forwards it to the SMF/PGW-C. The SMF/PGW-C sends an Npcf\_SMPolicyControl\_Create req to the PCF. The PCF responds with Npcf\_SMPolicyControl\_Create Ans. The diagram also indicates a standard continuation of E-UTRAN Initial Attach and subsequent steps for URSPs update initiated by PCF. + +Figure 6.16.2-1: Initial Attach procedure in EPC + +1. The UE generates UE STATE INDICATION UPDP message (including the list of PSIs stored in the UE) in the same way that it is done for the registration in 5GC. Then the UE includes this UE STATE INDICATION UPDP message into UE Policy Container ePCO in PDN Connectivity Request encapsulated in Attach Request. + +NOTE 1: For those cases where the UE attaches to EPC but doesn't request the establishment of a default bearer the procedure just follows the steps defined in clause 5.3.2.1 of TS 23.401 [8] and there is no PCF interaction. However, for those cases, the UE will include UE STATE INDICATION within a UE Policy Container ePCO during the first request for PDN connectivity. Then the PCF will be able to update the URSPs to the UE only after the establishment of the first PDU session establishment for the UE. + +- 2-4. These steps follow the existing procedure as defined in TS 23.401 [8], so the UE Policy Container ePCO is sent towards the SMF+PGW-C. + +5. The SMF+PGW-C forwards transparently the UE Policy Container ePCO to the PCF as a new IE in the PDU Session Establishment (Npcf\_SMPolicyControl\_Create Request). + +NOTE 2: Upon the reception of this UE Policy Container ePCO, the SMF+PGW-C shall establish the corresponding SM Policy Association even in case the network configuration for the APN of the PDN connection does not require PCF involvement. + +6. The PCF answers to the SMF with Npcf\_SMPolicyControl\_Create Response. + +7. The procedure for initial attach continues as defined in clause 5.3.2.1 of TS 23.401 [8]. + +8. the PCF gets the content of the UE STATE INDICATION included in new IE and processes it in a similar way than it does when it is received in 5GC during the UE Policy Association establishment, i.e. uses the list of + +UPSI included in the UE STATE INDICATION to determine if an update of UE policies is required for this UE. If no update is determined the procedure finishes here. If an update is needed, then the PCF generates the corresponding UPDP message MANAGE UE POLICY COMMAND in a similar way than it is done in 5GC and then includes the message into a UPDP Container ePCO. + +NOTE 3: The interactions toward UDR in relation with the retrieving and storage of UPSIs into UDR are not shown in the diagram. + +- The flow follows the steps 2-14 defined in clause 6.16.2.2 for URSP update initiated by PCF. + +## 6.16.2.2 URSP update initiated by PCF + +For the procedure for URSP update initiated by the PCF when the UE is in EPC, the procedure follows the steps described in the figure below: + +![Sequence diagram of the PCF initiated URSP update procedure. The diagram shows interactions between UE, MME, SGW, SMF/PGW-C, and PCF. The PCF triggers the re-evaluation of URSPs and sends a MANAGE UE POLICY COMMAND to the SMF/PGW-C. The SMF/PGW-C then initiates a bearer modification procedure with the MME and SGW, eventually reaching the UE. The UE processes the command and sends a MANAGE UE POLICY COMPLETE response back to the PCF.](e90b25c8d90cadc3f76c376701cf27ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant SGW + participant SMF/PGW-C + participant PCF + + Note right of PCF: 1. Trigger to re-evaluate URSPs + PCF->>SMF/PGW-C: 2. Npcf_SMPolicyControl_UpdateNotifyreq (MANAGE UE POL) + Note right of PCF: 3. Start T3501 + SMF/PGW-C->>PCF: 4. Npcf_SMPolicyControl_UpdateNotifyans (OK) + SMF/PGW-C->>SGW: 5. Update Bearer Request (MANAGE UE POL) + SGW->>MME: 6. Update Bearer Request (MANAGE UE POL) + MME->>UE: 7. EPS Bearer Context Request (MANAGE UE POL) + Note left of UE: 8. UE handles MANAGE UE POLICY COMMAND + UE->>MME: 9. EPS Bearer Context Response (MANAGE UE POL ACK) + MME->>SGW: 10. Update Bearer Response (MANAGE UE POL ACK) + SGW->>SMF/PGW-C: 11. Update Bearer Response (MANAGE UE POL ACK) + SMF/PGW-C->>PCF: 12. Npcf_SMPolicyControl_Update req (MANAGE UE POL) + SMF/PGW-C->>PCF: 14. Npcf_SMPolicyControl_Update ans + Note right of PCF: 13. Stop T3501 + +``` + +Sequence diagram of the PCF initiated URSP update procedure. The diagram shows interactions between UE, MME, SGW, SMF/PGW-C, and PCF. The PCF triggers the re-evaluation of URSPs and sends a MANAGE UE POLICY COMMAND to the SMF/PGW-C. The SMF/PGW-C then initiates a bearer modification procedure with the MME and SGW, eventually reaching the UE. The UE processes the command and sends a MANAGE UE POLICY COMPLETE response back to the PCF. + +Figure 6.16.2.2-1: PCF initiated URSP update procedure + +1. An event as described in clause 6.16.1.1 happens in PCF. The PCF triggers the re-evaluation of applicable URSPs for the UE and determines an update of URSP is needed for the UE. The PCF selects one of the PDN connection/PDU sessions associated to EPC for the delivery of the URSP update. Then the PCF generates the corresponding UPDP message MANAGE UE POLICY COMMAND in a similar way than it is done in 5GC and then includes the message into a new IE for sending it to the SMF over N7. +2. The UPDP message is then provided to the SMF+PGW-C by invoking Npcf\_SMPolicyControl\_UpdateNotify request. +3. The PCF starts timer T3501 to monitor the reception of an answer for UPDP MANAGE UE POLICY COMMAND. +4. The SMF+PGW-C, upon reception of the new IE with UPDP message, answers the PCF with Npcf\_SMPolicyControl\_UpdateNotify response and initiates a bearer modification procedure without bearer QoS update (as defined in clause 5.4.3 of TS 23.401 [8]) to provide the UE Policy Container ePCO towards the UE. +- 5-7. These steps follow the existing procedure for bearer modification procedure without bearer QoS +8. When the UE gets the UE Policy Container ePCO including a MANAGE UE POLICY COMMAND UPDP message, the UE processes that message in a similar way than when it is received in 5GC, i.e. stores the URSP updates, optionally re-evaluates the mapping of applications into PDN connections according to the mapping of URSP values into EPC, and generates UPDP message MANAGE UE POLICY COMMAND COMPLETE with the result to the PCF. + +9. The UE then generates a UE Policy Container UPDP including the MANAGE UE POLICY COMMAND COMPLETE, and include it in the EPS Bearer Context Response sent to the MME. +- 10-11. These steps follow the existing procedure defined for Update Bearer Response +12. Upon reception of UE Policy Container ePCO in Update Bearer Response, the SMF+PGW-C then invokes Npcf\_SMPolicyControl\_Update Request including the content of the UE Policy Container ePCO. +13. The PCF processes the MANAGE UE POLICY COMMAND COMPLETE in a similar way than in 5GC as defined in TS 29.525 [9] and stops timer T3501. +14. The PCF sends Npcf\_SMPolicyControl\_Update Response. + +### 6.16.2.3 Procedures for deployments where the PCF for the PDU session and the PCF for the UE are different PCFs + +#### 6.16.2.3.1 Initial Attach Procedure in EPC + +This clause extends the procedure in clause 6.16.2.1 when the PCF for a PDU session is different than the PCF for a UE. + +![Sequence diagram for Initial Attach Procedure in EPC where PCF for PDU session and PCF for UE are different. Lifelines: UE, eNodeB, MME, Serving GW, SMF + PGW-C, PCF-SM, PCF-UE. The diagram shows five steps: 1. Steps 1-7 from section 6.16.2.3.1 Initial Attach Procedure in EPC (between UE and SMF+PGW-C); 2. Npcf_UEPolicyControl_Create Req (SUPI, UE Policy Container(UE STATE IND),...) from SMF+PGW-C to PCF-UE; 3. UE policy container creation as described in TS 23.502, 4.16.11. (internal to PCF-UE); 4. Npcf_UEPolicyControl_Create Ans (UE Policy Container (MANAGE UE POL), ...) from PCF-UE to SMF+PGW-C; 5. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF (between SMF+PGW-C and UE).](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant Serving GW + participant SMF+PGW-C + participant PCF-SM + participant PCF-UE + + rect rgb(255, 255, 255) + Note over UE, PCF-SM: 1. Steps 1-7 from section 6.16.2.3.1 Initial Attach Procedure in EPC + end + PCF-SM->>PCF-UE: 2. Npcf_UEPolicyControl_Create Req (SUPI, UE Policy Container(UE STATE IND),...) + Note right of PCF-UE: 3. UE policy container creation as described in TS 23.502, 4.16.11. + PCF-UE-->>PCF-SM: 4. Npcf_UEPolicyControl_Create Ans (UE Policy Container (MANAGE UE POL), ...) + rect rgb(255, 255, 255) + Note over UE, PCF-SM: 5. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF + end + +``` + +Sequence diagram for Initial Attach Procedure in EPC where PCF for PDU session and PCF for UE are different. Lifelines: UE, eNodeB, MME, Serving GW, SMF + PGW-C, PCF-SM, PCF-UE. The diagram shows five steps: 1. Steps 1-7 from section 6.16.2.3.1 Initial Attach Procedure in EPC (between UE and SMF+PGW-C); 2. Npcf\_UEPolicyControl\_Create Req (SUPI, UE Policy Container(UE STATE IND),...) from SMF+PGW-C to PCF-UE; 3. UE policy container creation as described in TS 23.502, 4.16.11. (internal to PCF-UE); 4. Npcf\_UEPolicyControl\_Create Ans (UE Policy Container (MANAGE UE POL), ...) from PCF-UE to SMF+PGW-C; 5. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF (between SMF+PGW-C and UE). + +**Figure 6.16.2.3.1-1** + +- 1-7. They are the same than the ones described for deployments with a collocated PCF in clause 6.16.2.1, with the difference that in step 5 the SMF+PGW-C selects a PCF for a PDU session (PCF-SM) +2. The PCF-SM checks that the SMF+PGW-C provided a UE Policy Container in step 1 and then request the establishment of a UE Policy Association towards PCF-UE providing the UE Policy Container received from the SMF+PGW-C. +3. The PCF-UE follows standard procedure to handle the UE Policy establishment as defined in clause 4.16.11 of TS 23.502 [3] for the roaming case. It determines whether an update of URSP is needed and in such a case generates a UE Policy Container including the URSP update (UPDP message MANAGE UE POLICY COMMAND). +4. The PCF-UE answers the UE Policy Association establishment request. + +5. If a UE Policy Container is provided to the PCF-SM in step 4, the flow continues with steps 2-14 from procedure defined in clause 6.16.2.2 for deployments with a collocated PCF and the PCF-SM forwards the UE Policy Container to the UE via SMF+PGW-C. + +### 6.16.2.3.2 URSP update initiated by PCF + +This clause extends the procedure in 6.16.2.2 for URSP updates initiated by the PCF when the PCF for a PDU session is different than the PCF for a UE. + +![Sequence diagram for URSP update initiated by PCF. Lifelines: UE, eNodeB, MME, Serving GW, SMF + PGW-C, PCF-SM, PCF-UE. The sequence starts with a trigger in PCF-UE, followed by policy association selection, then a notification from PCF-UE to PCF-SM. A block labeled '4. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF' spans across the main entities. After this block, PCF-SM sends an update request to PCF-UE, which responds with an update answer.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant Serving GW + participant SMF + PGW-C + participant PCF-SM + participant PCF-UE + + Note right of PCF-UE: 0. Trigger for URSP update + Note right of PCF-UE: 1. UE Policy Association selection + PCF-UE->>PCF-SM: 2. Npcf_UEPolicyControl_UpdateNotify Req (UE Policy Container(MANAGE UE POL),...) + PCF-SM-->>PCF-UE: 3. Npcf_UEPolicyControl_UpdateNotify Ans (...) + Note over UE, SMF + PGW-C: 4. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF + PCF-SM->>PCF-UE: 5. Npcf_UEPolicyControl_Update Req (UE Policy Container(MANAGE UE POL ACK),...) + PCF-UE-->>PCF-SM: 6. Npcf_UEPolicyControl_Update Ans (...) + +``` + +Sequence diagram for URSP update initiated by PCF. Lifelines: UE, eNodeB, MME, Serving GW, SMF + PGW-C, PCF-SM, PCF-UE. The sequence starts with a trigger in PCF-UE, followed by policy association selection, then a notification from PCF-UE to PCF-SM. A block labeled '4. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF' spans across the main entities. After this block, PCF-SM sends an update request to PCF-UE, which responds with an update answer. + +Figure 6.16.2.3.2-1 + +- 0: An event as described in clause 6.16.1.1 happens in the PCF-UE. The PCF-UE triggers the re-evaluation of applicable URSPs for the UE and determines an update of URSP is needed for the UE. +1. If several ongoing UE Policy Associations with new indication "5GS to EPC handover" exists in the PCF-UE this selects one of them for the delivery of the URSP update. +2. The PCF-UE generates the corresponding UE Policy Container (UPDP message MANAGE UE POLICY COMMAND) in a similar way than it is done in 5GC (according to clause 4.16.12.2 of TS 23.502 [3]) and then invokes Npcf\_UEPolicyControl\_UpdateNotify including the UE Policy Container. +3. PCF-SM answers Npcf\_UEPolicyControl\_UpdateNotify. +4. It follows the steps 2-14 from clause 6.16.2.2 for a deployment with a collocated PCF. +5. The PCF-SM sends Npcf\_UEPolicyControl\_Update to provide the received UE Policy Container (including MANAGE UE POLICY COMMAND COMPLETE UPDP message from the UE) to the PCF-UE. +6. The PCF-UE processes the MANAGE UE POLICY COMMAND COMPLETE in a similar way than in 5GC as defined in TS 29.525 [9] and answers Npcf\_UEPolicyControl\_Update. + +### 6.16.2.3.3 Handover from 5GS to EPC + +This clause shows the impact in the procedure for 5GS to EPC handover when the PCF for a PDU session is different than the PCF for a UE. + +![Sequence diagram for 5GS to EPS handover for single-registration mode with N26 interface. Lifelines: UE, eNodeB + MME + SGW, AMF, SMF + PGW-C, PCF-SM, PCF-UE. The diagram shows the flow of policy control messages between the AMF, SMF+PGW-C, and PCF-SM/UE during a handover.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + MME + SGW + participant AMF + participant SMF + PGW-C + participant PCF-SM + participant PCF-UE + + Note over UE, eNodeB + MME + SGW: 1: 5GS to EPS handover for single-registration mode with N26 interface as from 23.502 4.11.1.2.1-1 + + AMF->>PCF-UE: 2. Npcf_UEPolicyControl_Delete Req ("5GSHandoverToEPC") + Note right of PCF-UE: 3. UE Policy Association is kept for a configured period + PCF-UE-->>AMF: 4. Npcf_UEPolicyControl_Delete Ans (..) + SMF + PGW-C->>PCF-SM: 5. Npcf_SMPolicyControl_Update Req (RAT-Type=EPC,..) + PCF-SM-->>SMF + PGW-C: 6. Npcf_SMPolicyControl_Update Ans (..) + Note right of PCF-SM: 7. Check whether new UE Policy Association is needed + Note right of PCF-SM: 8. PCF-UE selection + PCF-SM->>PCF-UE: 9. Npcf_UEPolicyControl_Create Req ("5GSHandoverToEPC", UEPolicyContainer(Empty) ..) + Note right of PCF-UE: 10. Get PSIs from former UE Policy Association (5GS) + Note right of PCF-UE: 11. UE policy container creation as described in TS 23.502, 4.16.11. + PCF-UE-->>PCF-SM: 12. Npcf_UEPolicyControl_Create Ans (UEPolicyContainer (MANAGE UE POL),..) + + Note over UE, eNodeB + MME + SGW: 13: Steps 2-14 of 4. Steps 2-14 from section 6.16.2.2 URSP update initiated by PCF + +``` + +Sequence diagram for 5GS to EPS handover for single-registration mode with N26 interface. Lifelines: UE, eNodeB + MME + SGW, AMF, SMF + PGW-C, PCF-SM, PCF-UE. The diagram shows the flow of policy control messages between the AMF, SMF+PGW-C, and PCF-SM/UE during a handover. + +Figure 6.16.2.3.3-1 + +1. It follows standard procedure for 5GS to EPC handover as described in clause 4.11.1.2.1 of TS 23.502 [3] (similar for handover with idle mobility). + 2. For the scenarios with N26 the AMF invokes the deletion of UE Policy Association including a new indication "5GS handover to EPC". + - 3-4. Based on the new indication ("5GS handover to EPC") the PCF-UE, after the PCF-UE answers the AMF, the PCF-UE decides to maintain the UE Policy association for a configurable period (e.g. 20s), until the new UE Policy Association from the PCF-SM is received. In addition, during this period, no other actions associated to the removal of the UE Policy Association (e.g. unbinding from BSF or un-subscription from UDR notifications for this UE) are executed. +- NOTE 1: If step 2 happens after step 8 the PCF-UE may remove directly the former UE Policy Association. +5. SMF+PGW-C notifies PCF-SM about the handover to EPC invoking Npcf\_SMPolicyControl\_Update Request. +This step happens for every ongoing PDU session handled by the PCF-SM. + 6. PCF-SM answers SMF+PGW-C as in standard procedure. + 7. The PCF-SM determines whether the UE supports URSP delivery in EPC by checking UE context policy control subscription information in UDR and based on that decides to establish a UE Policy Association towards the PCF-UE. + +- NOTE 2: For those deployments where the solution is restricted to a specific combination of S-NSSAI/DNN the PCF-SM also checks if the PDU session being notified by SMF+PGW-C is established towards the specific S-NSSAI/DNN. In other case the PCF-SM controls that only one UE Policy Association Establishment is established and maintained for the same UE. In case the same PCF-SM maintains several PDU sessions for the same UE the PCF-SM will establish the UE Policy Association only for the first PDU session establishment which reports the change of RAT-Type. +8. The PCF-SM discovers the address of the PCF-UE handling the UE by querying BSF. + 9. The PCF-SM establishes a UE Policy Association towards the PCF-UE including an empty UE Policy Container, i.e. no information about PSI list in the UE is provided to the PCF-UE and an indication about the trigger for the UE Policy association establishment ("5GS to EPC handover"). +- NOTE 3: If the removal of associated information for the former UE Policy Association was delayed, the PCF-UE can now delete it. Since additional UE Policy Associations are still ongoing for this UE (the one from PCF-SM) the PCF-UE doesn't execute other additional actions associated to the removal of the UE Policy Association (e.g. unbinding from BSF or un-subscription from UDR notifications for this UE). +10. Based on the indication received in step 9, the PCF-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. +- NOTE 4: If the removal of associated information for the former UE Policy Association was delayed, the PCF-UE can now delete it. Since additional UE Policy Associations are still ongoing for this UE (the one from PCF-SM) the PCF-UE does not execute other additional actions associated to the removal of the UE Policy Association (e.g. unbinding from BSF or un-subscription from UDR notifications for this UE). +11. The PCF-UE follows standard procedure to handle the UE Policy establishment as defined in clause 4.16.11 of TS 23.502 [3] for the roaming case. It determines whether an update of URSP is needed and in such a case generates a UE Policy Container including the URSP update (UPDP message MANAGE UE POLICY COMMAND). + 12. The PCF-UE sends Npcf\_UEPolicyControl create answer including a UE Policy Container with the URSP updates if needed and the list of PCRTs, obtained from the former UE Policy Association for the UE in 5GS. +- NOTE 5: Note that only the list of supported PCRTs over N7 will be supported for the UE Policy Association (e.g. Connectivity State changes event trigger is not supported over N7). +13. Follows steps 2-14 of the procedure described in clause 6.16.2.2.1 for URSPs update initiated by PCF. + +### 6.16.3 Impacts + +Impact on interface: + +N7: + +- Introduce additional IE for the transfer of UE Policy Container between SMF+PGW-C and PCF. + +NAS, S11, S5/S8(?): + +- Introduce new parameter UE Policy Container in ePCO. + +Impact on PCF: + +- Handling of UE Policy Container within SM Policy Association procedures. +- For those cases where PCF initiates the sending of URSP update for a UE in EPC, the triggering of SM Policy Association modification including the new IE with MANAGE UE POLICY COMMAND UPDP message. +- PCF-SM establishes UE Policy Association towards PCF-UE upon EPC initial attach and 5GS to EPC handover. +- PCF-UE handles new indication in UE Policy association deletion so it may delay the removal of UE Policy Association in PCF-UE during a short configured period, waiting for the new one established from PCF-SM. +- PCF-UE handles new indication in UE Policy Association establishment from PCF-SM at handover to EPC, so it may get the list of PSIs stored in the UE from former UE Policy Association from 5GS. + +Impact on SMF+PGW-C: + +- Upon reception of UE Policy Container ePCO in Create Session Request, the SMF+PGW-C forwards the UE Policy Container to the PCF at SM Policy Association establishment. Use the reception of UPDP Container as an additional reason to establish the SM Policy Association, even in case the network configuration for the APN of the PDN connection does not require PCF involvement. +- Upon reception of UE Policy Container from PCF during SM Policy Association initiated by PCF, SMF+PGW-C performs a Bearer Modification Procedure without bearer QoS update including the UE Policy Container ePCO. +- Upon reception of Update Bearer Response from MME including UE Policy Container ePCO, the SMF+PGW-C forwards the received UE Policy Container to PCF. + +Impact on UE: + +- During initial attach in EPC, the UE includes UE STATE INDICATION UPDP message into UE Policy Container ePCO in PDN Connectivity Request encapsulated in Attach Request. +- The UE receives MANAGE UE POLICY COMMAND in UE Policy Container ePCO during EPS Bearer Context Request and process it as in 5GC. The UE generates MANAGE UE POLICY COMPLETE UPDP message and send it to the MME encapsulated into a UE Policy Container ePCO in EPS Bearer Context Response. +- The UE includes additional parameter in UE Policy Container at 5GS initial registration about whether it supports URSP provisioning via EPC. + +Impact on AMF: + +- For deployments with N26 the AMF includes a new indication when the UE Policy Association is deleted due to a 5GS to EPC handover. +- Impact on UDR: +- The information in UE context policy control subscription information is extended with a new attribute which indicates whether the UE supports URSP delivery in EPC. + +## 6.17 Solution #17: Indication of applicability of URSP to UE in EPS + +### 6.17.1 Description + +Support of URSPs in EPS was introduced in 3GPP Rel-16. A Rel-16 UE can use URSPs while in EPS (S1 mode) by translating the various parameters in the Traffic Descriptors and Route Selection Descriptors to corresponding EPS parameters as defined in clause 4.4.2 of TS 24.526 [10]. URSPs are still provisioned via 5GC. Whereas for the Traffic Descriptors (TD) a 1-to-1 mapping can be derived, certain 5GS parameters of a Route Selection Descriptor (RSD) do not have an exact equivalent in EPS e.g. SSC mode selection, Network Slice selection, DNN selection, Time Window, Location criteria etc. For this purpose, a static mapping of 5GS parameters to EPS was specified in the Table 4.4.2.2 of TS 24.526 [10], with certain parameters marked as not applicable in EPS. A UE in EPS currently ignores an RSD if it contains any such parameter that are marked as not applicable in Table 4.4.2.2 of TS 24.526 [10]. + +Although this static mapping enables the use of certain URSPs in EPS, i.e. the ones that do not contain any of the non-applicable parameters, this static mapping of what is applicable in EPS is very limiting. Essentially, a network operator, to ensure that the UEs in EPS behave as desired, has to design and provision EPS-specific RSDs that avoid any non-applicable parameter. This results to unnecessary signalling, storage and processing overheads at both UE and network sides, and network management overheads. + +Additionally, with this static mapping none of those parameters can be used by a UE while in EPS. However, for certain features like edge computing, "Time Window" and "Location Criteria" are spatial and temporal criteria which could be used to determine the validity of URSP rules. + +In this solution, it is proposed to introduce a new optional parameter "EPS applicability" in the Route Selection Descriptor component of a URSP rule. The new parameter, if present in the RSD, will provide an indication to the UE, whether the RSD parameter is applicable in EPS. + +In order to ensure backwards compatibility and avoid any unnecessary signalling, at registration the UE shall indicate whether it supports this new feature. If the UE includes the "EPS RSD support indication" during registration, the PCF may then include the additional parameter "EPS applicability" in the RSD component to indicate how the UE should use each RSD parameter in EPS. This design ensures that the optional applicability indication can be used only if needed, and supported by both the UE and the network. + +## 6.17.2 Procedures + +### 6.17.2.1 URSP provisioning with EPS applicability indication + +Figure 6.16.2.1-1 explains the procedure for URSP provisioning with EPS applicability indication. + +![Sequence diagram showing URSP provisioning with EPS applicability indication between UE, AMF, and PCF.](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF + Note right of AMF: 1. UE REGISTRATION + AM Policy Association Establishment. +UE STATE INDICATION (UPSI List, UE Policy classmark (ANSDP, EPS RSD support indication), [UE Os Id]) + AMF->>PCF: 2. MANAGE UE POLICY COMMAND (...UE policy section management list(... +EPS applicability indication)) + PCF->>UE: 3. MANAGE UE POLICY COMPLETE (...) + +``` + +The diagram illustrates a three-step sequence of interactions between the User Equipment (UE), the Access and Management Function (AMF), and the Policy Control Function (PCF). + Step 1: UE REGISTRATION + AM Policy Association Establishment. The UE sends a UE STATE INDICATION to the AMF, which includes the UPSI List, UE Policy classmark (ANSDP, EPS RSD support indication), and [UE Os Id]. + Step 2: MANAGE UE POLICY COMMAND. The AMF sends a command to the PCF, containing the UE policy section management list, which includes the EPS applicability indication. + Step 3: MANAGE UE POLICY COMPLETE. The PCF sends a response back to the UE. + +Sequence diagram showing URSP provisioning with EPS applicability indication between UE, AMF, and PCF. + +Figure 6.17.2.1-1: URSP provisioning with EPS applicability indication + +1. At registration the UE indicates support of the feature by including the "EPS RSD support indication". +2. If the UE has indicated support for "EPS RSD support indication" then the PCF generates the URSP rules including the applicability of certain parameters to EPS. For each Route Selection Descriptor component, the PCF shall include the new optional parameter "EPS applicability". +3. UE indicates the success or failure of update. + +The Route Selection Descriptor component is extended as shown in Table 6.17.2.1-1 below to support the "EPS applicability" indication. + +**Editor's note:** It is FFS whether the EPS applicability indication is included to all components or only to the ones for which the handling over the static mapping of "4.4.2 Use of URSP in EPS" of TS 24.526 [10] as per Rel-16 is to be overridden. + +**Table 6.17.2.1-1: Route Selection Descriptor component** + +| Parameter name | Description | Mandatory/Optional | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| RSD component type | This indicates the route selection descriptor component type e.g. SSC mode or DNN type etc. as specified in Table 5.2.1 of TS 24.526 [10]. This parameter is transmitted first. | M | +| RSD component value | This indicates the value corresponding to the route selection descriptor component type. | M | +| EPS applicability | Indicates how to handle this RSD when in EPS. This parameter may be included only if UE has indicated support. One of the following values can be included:<br>1) Not applicable (backward compatible handling)<br>2) To be ignored in EPS<br>3) Applies to EPS<br>4) reserved | O | + +## 6.17.2.2 Evaluation of URSP rules with EPS applicability indication + +When the UE is in S1 mode, during URSP evaluation the UE shall: + +- ignore the complete RSD if any RSD component has EPS applicability parameter set to "Not applicable". +- only ignore the specific RSD component (i.e. not the whole RSD) when the EPS applicability parameter is set to "To be ignored in EPS". +- consider the RSD component in EPS also if the EPS applicability parameter in the RSD component is set to "Applicable to EPS". + +## 6.17.3 Impacts on services, entities and interfaces + +The solution has the following impacts: + +PCF: + +- PCF shall support the additional parameter (EPS applicability indication) in RSD component of URSP rule as explained in clause 6.16.2.1. +- PCF shall include the "EPS applicability indication" in RSD component only if UE has provided "EPS RSD support indication" during registration. + +UE: + +- UE shall include "EPS RSD support indication" during registration. +- UE shall support evaluation of the URSP rules as described in clause 6.16.2.2. + +# 6.18 Solution #18: Provisioning consistent URSP to UE across 5GS and EPS for Collocated PCF Deployment + +## 6.18.1 Description + +This solution addresses KI#3 and assumes a collocated PCF deployment where the PCF serving the UE and PCF serving each of the PDU Sessions of the UE are the same. The solution aims to solve the issue when ANDSF is not deployed in EPS. + +With regard to the scenarios and gaps (first two bullets in the KI#3), if a UE has used the Route Selection component (e.g. DNN) in a URSP rule in EPS and the Route Selection component (e.g. DNN) has been changed when the UE stays in EPS, the updated URSP rule needs to be provisioned to UE in EPS, otherwise the UE in EPS may use outdated DNN to establish PDN connection in EPS. In 5GS the UE may be provisioned with URSP rules for both 5GS and EPS by the PCF of the HPLMN. Only the rules provisioned by the PCF are used by the UE, if both URSP rules provisioned by the + +PCF and pre-configured URSP rules are present. The URSP rules are provisioned in UE using NAS messages. The AMF transparently transfers the UE Policy container (UE policy information) received from the PCF to the UE (using DL NAS TRANSPORT message). The UE Policy container includes the list of Policy Sections as described in TS 23.503 [4]. Similar mechanism can be used to provision URSP rules in EPS. + +Since the URSP usage is not supported by a Rel-15 UE supporting interworking between EPS and 5GS, it's not necessary to provision/update the URSP to such UE, which will cause additional signalling overload. Thus, the EPS needs to be aware whether a 4G interworking UE supports the URSP usage or not. + +To realize provisioning of consistent URSP rules in UE, this solution follows the below two principles: + +- 1) The same set of URSP is provisioned to UE regardless of UE attaching to EPS or registering to 5GS. +- 2) The UE in EPS uses the components in RSD of a URSP rule according to Rel-16 specification defined in clause 5.17.1.2 of TS 23.501 [2]. + +The EPS and 5GS interworking architecture defined in TS 23.501 [2] is reused, the solution addresses the collocated PCF deployment scenario where the SM-PCF and UE-PCF are collocated, N7 interface is reused to provision URSP from PCF to PGW-C and no new interface is introduced. The solution proposes a mechanism for the network to provision and update the URSP for a UE in EPS by encapsulating UE Policy Container in ePCO via one of the PDN connections. The UE Policy Container is transparently forwarded via SMF+PGW-C. The communication between SMF+PGW-C and PCF reuses the SM Policy Association procedures. + +## 6.18.2 Procedures + +### 6.18.2.1 UE triggered UE Policy provisioning procedure in EPS + +1. The UE sends the UE Policy Container including URSP Support indication in EPS which is indicating whether a UE supports URSP usage or not in EPS (defined in TS 23.501 [2] clause 5.17.1.2) and the PSIs (Policy Set Identifier) in ePCO (extended PCO) to SMF+PGW-C during Initial Attach procedure (in the Attach Request) as described in clause 5.3.2.1 of TS 23.401 [8] and the UE requested PDN connectivity procedure (PDN Connectivity Request) as described in clause 5.10.2 of TS 23.401 [8]. +2. The SMF+PGW-C transparently forwards the UE Policy Container in ePCO to the PCF as a new IE in the PDU Session Establishment (Npcf\_SMPolicyControl\_Create Request). + +NOTE: If the PCF involvement for a PDN connection is not required, the SMF+PGW-C should still establish SM Policy Association with PCF and forward the UE Policy Container to PCF based on local configuration. + +3. The PCF gets policy subscription related information and the updated list of PSIs from the UDR. The PCF creates the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503 [4]. Then it sends the latest UE policy information in the UE Policy Container to SMF+PGW-C. +4. The SMF+PGW-C sends the UE Policy Container in ePCO to UE in Activate Default EPS Bearer Context message which may be encapsulated in Attach Accept message. +5. The UE sends a response to SMF+PGW-C by acknowledging the reception of the UE Policy reusing existing messages (e.g. Attach Complete, Modify Bearer Request) as defined in clause 5.3.2 of TS 23.401 [8]. +6. The SMF+PGW-C forwards the acknowledgement of UE reception of the UE Policy to PCF using Npcf\_SMPolicyControl\_Update request. + +### 6.18.2.2 PCF triggered UE Policy provisioning procedure in EPS + +1. When the PCF is notified by UDR that the URSP is updated, it triggers the UE Policy update procedure towards the SMF+PGW-C using Npcf\_SMPolicyControl\_UpdateNotify request. The PCF selects one of the PDN connections for the UE in EPS for the delivery of the updated URSP rules. +2. The SMF+PGW-C transparently forwards the updated URSP rules to UE in UE Policy Container via ePCO, which can be achieved by reusing existing messages (e.g. Update Bearer Request, Downlink NAS Transport) as defined in clause 5.4.3 of TS 23.401 [8]. + +3. When the UE receives the updated URSP rules, it updates the URSP rules and sends a response to SMF+PGW-C by acknowledging the reception of the UE Policy reusing existing messages (e.g. Uplink NAS Transport, Update Bearer Response,) as defined in clause 5.4.3 of TS 23.401 [8]. +4. The SMF+PGW-C forwards the acknowledgement of UE reception of the UE Policy to PCF using Npcf\_SMPolicyControl\_Update request. + +### 6.18.3 Impacts on services, entities and interfaces + +UE: + +- Send the UE Policy Container including UE capability to support URSP Support indication in EPS and PSIs to PGW-C via ePCO. +- Receive the URSP rules in the UE Policy Container from PGW-C via ePCO. +- Sends an acknowledgement of UE Policy reception. + +SMF+PGW-C: + +- Transparently forward the UE Policy Container in ePCO to PCF. +- Transparently forward the UE Policy Container in ePCO to UE. + +PCF: + +- Receive the UE Policy Container from SMF+PGW-C. +- Initiates transfer of URSP rules in UE Policy Container to UE via SMF+PGW-C. + +## 6.19 Solution #19: Provision of URSP to UE when the UE attaches in the EPS + +### 6.19.1 Introduction + +This solution addresses key issue#3 'Provision consistent URSP to UE across 5GS and EPS'. + +When the UE is attaching to the EPS system, the PGW-C+SMF node requests the PCF to provide the URSP information. The PCF provides the URSP information after interacting with the UDR. + +## 6.19.2 Procedures + +![Sequence diagram illustrating the Transfer of URSP procedure when the UE is registering to the EPS system. The diagram shows interactions between UE, MME, S-GW, PGW-C+SMF, PCF, and UDR. The UE sends an Attach Request to the MME. The MME sends a Create session Request to the S-GW. The S-GW sends a Create Session Request to the PGW-C+SMF. The PGW-C+SMF sends Npcf_get_UEpolicy and Nudr_get_UEpolicy requests to the PCF and UDR respectively. The PCF and UDR return responses. The PGW-C+SMF sends a Create Session Response to the S-GW. The S-GW sends a Create Session Response to the MME. The MME sends an Attach Accept to the UE. The UE stores the UE policy and applies it in EPS or 5GS.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant S-GW + participant PGW-C+SMF + participant PCF + participant UDR + + Note left of UE: 11. The UE stores the UE policy and applies in EPS or 5GS. + + UE->>MME: 1. Attach Request (PDN Connectivity Request(UE policy list, UE policy classmark, UE OS ID)) + MME->>S-GW: 2. Create session Request (UE policy list, UE policy classmark, UE OS ID, UE status) + S-GW->>PGW-C+SMF: 3. Create Session Request (UE policy list, UE policy classmark, UE OS ID, UE status) + PGW-C+SMF->>PCF: 4. Npcf_get_UEpolicy Request (Policy type, S1 mode supported, N1 mode supported, UE policy list, UE policy classmark, UE OS ID, UE status) + PGW-C+SMF->>UDR: 5. Nudr_get_UEpolicy Request (Policy type, S1 mode supported, N1 mode supported, UE policy list, UE policy classmark, UE OS ID, UE status) + UDR->>PCF: 6. Nudr_get_UEpolicy Response (UE Policy) + PCF->>PGW-C+SMF: 7. Npcf_get_UEpolicy Response (UE Policy) + PGW-C+SMF->>S-GW: 8. Create Session Response(UE policy) + S-GW->>MME: 9. Create Session Response(UE policy) + Note right of MME: 10a. Attach Accept (Activate Default EPS Bearer Context Request (UE policy)) + Note right of MME: or + Note right of MME: 10b. Attach Accept (UE Policy, Activate Default EPS Bearer Context Request()) + MME->>UE: 10a. Attach Accept (Activate Default EPS Bearer Context Request (UE policy)) + MME->>UE: 10b. Attach Accept (UE Policy, Activate Default EPS Bearer Context Request()) + +``` + +Sequence diagram illustrating the Transfer of URSP procedure when the UE is registering to the EPS system. The diagram shows interactions between UE, MME, S-GW, PGW-C+SMF, PCF, and UDR. The UE sends an Attach Request to the MME. The MME sends a Create session Request to the S-GW. The S-GW sends a Create Session Request to the PGW-C+SMF. The PGW-C+SMF sends Npcf\_get\_UEpolicy and Nudr\_get\_UEpolicy requests to the PCF and UDR respectively. The PCF and UDR return responses. The PGW-C+SMF sends a Create Session Response to the S-GW. The S-GW sends a Create Session Response to the MME. The MME sends an Attach Accept to the UE. The UE stores the UE policy and applies it in EPS or 5GS. + +**Figure 6.19.2-1: Transfer of URSP procedure when the UE is registering to the EPS system** + +The detailed steps of the procedure are defined below: + +- The UE initiates attach procedure to a PLMN by sending an attach request message to the MME. The UE includes the UE policy list, UE policy classmark and UE OS ID Information Element (IE) either in a PDN connectivity request message or in the attach request message. The UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) may be set in the PCO parameter in the attach request message. + +NOTE 1: UE policy list, the UE policy classmark and the UE OS ID are defined in TS 24.501 [7]. + +- Upon reception of the attach request message, the MME sends a create session request message containing PCO, UE status and the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) to the S-GW. The UE status may be added to the create session request message by the MME. The UE status may include following information: + +- CN type: It indicates a CN type, core network type, that the UE is being or has attached. E.g. EPC or 5GC. +- Access Type: It indicates an access that the UE is accessing. E.g. 3GPP access or Non-3GPP access. +- RAT type: It indicates a Radio Access Technology that the UE is accessing. E.g. EUTRAN, EUTRAN-NB-IoT, LTE-M, or NR. +- Serving Network (PLMN ID, or PLMN ID and NID). + +In this solution, the MME may determine the UE status based on local information regarding the UE in the MME or received information regarding the UE from other network node(s). + +- Upon reception of the create session request message the S-GW sends the create session request message containing the PCO, the UE status and the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) to the PGW-C+SMF. +- Upon reception of the create session request message the PGW-C+SMF sends Npcf\_get\_UEpolicy Request message containing Policy type, S1 mode supported, N1 mode supported, the UE policy list, the UE policy classmark, the UE OS ID IE and the UE status. The Policy type indicates a type of UE policy that the PGW-C+SMF wants to fetch for the UE. If the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) are encapsulated in the PCO, the PGW-C+SMF extracts the UE policy list, the UE policy classmark and the UE OS ID Information Element (IE) from the PCO. + +If policy list is not contained in the create session request message, the PGW-C+SMF includes Policy type information element. In this solution, the PGW-C+SMF may determine the Policy type information element based on the UE policy list. In this solution, the PGW-C+SMF may determine the Policy type information element based on a local configuration in the PGW-C+SMF or stored information regarding policy list of the UE. + +The PGW-C+SMF may obtain the "S1 mode supported" and the "N1 mode supported" based on information regarding the UE stored in the PGW-C+SMF or received information regarding the UE from other network node(s). + +NOTE 2: The PGW-C+SMF can discover and select the UE PCF according to clause 6.3.7.1 of TS 23.501 [2]. The UE PCF can be colocated with SMF PCF or can be a separate PCF than the SMF PCF. + +5. Upon reception of the message from the PGW-C+SMF, the PCF sends Nudr\_get\_UEpolicy Request message containing the Policy type, the S1 mode supported, the N1 mode supported, the UE policy list, the UE policy classmark, the UE OS ID and the UE status to the UDR. +6. Upon reception of the message from the PCF, the UDR transfers the UE policy to the PCF in the Nudr\_get\_UEpolicy Response message. +7. Upon reception of the UE policy in the response message from the UDR, the PCF sends Npcf\_get\_UE policy response message to the PGW-C+SMF. +8. Upon reception of the UE policy in the response message from the PCF, the PGW-C+SMF sends a Create session response message containing the UE policy to the S-GW. The UE policy may be stored in the PCO. The UE policy may be stored in the PCO of the Create session response message. +9. Upon reception of the Create session response message, the S-GW sends a Create session response message containing PCO and the UE policy to the MME. + +Upon reception of the Create session response message the MME takes either step 10a or step 10b. + +- 10a. The MME sends an attach accept message containing the PCO and Activate Default EPS Bearer Context Request message which contains the UE policy. If the UE policy is encapsulated in the PCO, the UE extracts the UE policy from the PCO. + - 10b. The MME sends an attach accept message containing the PCO and the UE policy and an Activate Default EPS Bearer Context Request message. +11. The UE upon reception of the UE policy applies the UE policy when the UE is registered in the EPS or when the UE registers to the 5GS as defined in TS 24.526 [10]. + +## 6.20 Solution #20: URSP delivery for the UE in EPS + +### 6.20.1 Description + +According to clause 5.2.1 of TS 23.503 [4], the SM-PCF does not support N15 reference point while the UE-PCF does not support N7 reference point. In this solution, for URSP delivery from UE-PCF in 5GC to the UE in EPS, the UE Policy Association establishment between SM-PCF and UE-PCF is proposed. The URSP can be transparently delivered to the UE via SM-PCF, SMF+PGW-C, SGW, and MME. The architecture is shown in Figure 6.20.1-1. + +![Figure 6.20.1-1: Non-roaming architecture for URSP delivery to the UE in EPS. The diagram shows a mobile network architecture with two User Equipment (UE) units. The left UE is connected to an E-UTRAN, which is connected to an MME via S1-MME and S1-U interfaces. The MME is connected to an SGW via S11. The SGW is connected to an SMF + PGW-C via S5-C and S5-U interfaces. The SMF + PGW-C is connected to an HSS + UDM via N10 and to an UPF + PGW-U via N4. The UPF + PGW-U is connected to an AMF via N11. The AMF is connected to the HSS + UDM via N8 and to the SMF + PGW-C via N7. The SMF + PGW-C is also connected to a UE-PCF via Nx. The UE-PCF is connected to the AMF via N15. The AMF is connected to an NG-RAN, which is connected to the right UE via N1 and N2 interfaces. The NG-RAN is also connected to the AMF via N3. The HSS + UDM is connected to the SMF + PGW-C via N10. 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 HSS + UDM via N8. The HSS + UDM is connected to the SMF + PGW-C via N10. The SMF + PGW-C is connected to the UE-PCF via Nx. The UE-PCF is connected to the AMF via N15. The AMF is connected to the NG-RAN via N3. The NG-RAN is connected to the UE via N1 and N2 interfaces.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +Figure 6.20.1-1: Non-roaming architecture for URSP delivery to the UE in EPS. The diagram shows a mobile network architecture with two User Equipment (UE) units. The left UE is connected to an E-UTRAN, which is connected to an MME via S1-MME and S1-U interfaces. The MME is connected to an SGW via S11. The SGW is connected to an SMF + PGW-C via S5-C and S5-U interfaces. The SMF + PGW-C is connected to an HSS + UDM via N10 and to an UPF + PGW-U via N4. The UPF + PGW-U is connected to an AMF via N11. The AMF is connected to the HSS + UDM via N8 and to the SMF + PGW-C via N7. The SMF + PGW-C is also connected to a UE-PCF via Nx. The UE-PCF is connected to the AMF via N15. The AMF is connected to an NG-RAN, which is connected to the right UE via N1 and N2 interfaces. The NG-RAN is also connected to the AMF via N3. The HSS + UDM is connected to the SMF + PGW-C via N10. 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 HSS + UDM via N8. The HSS + UDM is connected to the SMF + PGW-C via N10. The SMF + PGW-C is connected to the UE-PCF via Nx. The UE-PCF is connected to the AMF via N15. The AMF is connected to the NG-RAN via N3. The NG-RAN is connected to the UE via N1 and N2 interfaces. + +**Figure 6.20.1-1: Non-roaming architecture for URSP delivery to the UE in EPS** + +As depicted in Figure 6.20.1-1, an interface (Nx) needs to be specified between SM-PCF and UE-PCF for establish an UE Policy Association. N15 interface can be reused as Nx. + +When the UE sends Attach Request in EPS (e.g. Initial Attach procedure, 5GS to EPS Mobility procedure without N26), the UE sends UE Policy Container including list of PSIs and URSP delivery over EPS Indication in PCO to UE-PCF. The detail procedure is introduced in clause 6.20.2.1. + +When the UE policy has been updated in PCF while UE is in EPS, the UE-PCF sends UE Policy Container to SMF+PGW-C. The SMF+PGW-C sends PCO including UE Policy Container to the UE. The detail procedure is introduced in clause 6.20.2.2. + +When the UE sends Registration Request in 5GS, UE Policy Container including list of PSIs and URSP delivery over EPS Indication to UE-PCF. The detail procedure is introduced in clause 6.20.2.3. + +In 5GS to EPS Handover/Idle mode mobility using N26, the UE Policy Association established in 5GS can be maintained in EPS. The detail procedures are introduced in clauses 6.20.2.4, 6.20.2.5, 6.20.2.6. + +## 6.20.2 Procedures + +### 6.20.2.1 UE Policy delivery procedure initiated by the UE in EPS + +![Sequence diagram of UE Policy delivery procedure initiated by the UE in EPS. The diagram shows interactions between UE, eNodeB, MME, Serving GW, SMF+PGW-C, PCF (SM-PCF), and PCF (UE-PCF).](aa6e28822419dba9f22129fee66c9c4c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant Serving GW + participant SMF+PGW-C + participant SM-PCF as PCF (SM-PCF) + participant UE-PCF as PCF (UE-PCF) + + Note left of SMF+PGW-C: 1. Step 1-12 described in TS 23.401, 5.3.2.1-1 (Attach Request, Create Session Request). UE sends UE Policy Container (the list of PSIs, URSP delivery over EPS Indication) in PCO to SMF+PGW-C. + SMF+PGW-C->>SM-PCF: 2. Npcf_SMPolicyControl_Update Request (SUPI, UE Policy Container, UE-PCF ID) + SM-PCF->>UE-PCF: 3. UE-PCF Association Establishment Request (SUPI, UE Policy Container) + UE-PCF->>SM-PCF: 4. UE-PCF Association Establishment Response + Note right of UE-PCF: 5. UE policy container creation as described in TS 23.502, 4.16.11. + UE-PCF->>SM-PCF: 6. UE-PCF sends the UE Policy Container to SM-PCF + SM-PCF->>SMF+PGW-C: 7. Npcf_SMPolicyControl_Update Response (UE Policy Container) + Note left of SMF+PGW-C: 8. Additional steps for completion of Initial Attach procedure as described in TS 23.401, 5.3.2.1-1. SMF+PGW-C sends UE Policy Container in PCO to UE. The UE sends the acknowledgement on reception of the UE Policy. + SMF+PGW-C->>SM-PCF: 9. Npcf_SMPolicyControl_Update Request (acknowledgement) + SM-PCF->>UE-PCF: 10. SM-PCF forwards the acknowledgement from the UE. + +``` + +Sequence diagram of UE Policy delivery procedure initiated by the UE in EPS. The diagram shows interactions between UE, eNodeB, MME, Serving GW, SMF+PGW-C, PCF (SM-PCF), and PCF (UE-PCF). + +Figure 6.20.2-1: UE Policy delivery procedure initiated by the UE in EPS + +1. UE sends UE Policy Container including the list of PSIs and URSP delivery over EPS Indication SMF+PGW-C. The PCO can be included in Attach Request and Create Session Request as described in Figure 5.3.2.1-1 of TS 23.401 [8]. +2. The SMF+PGW-C invokes Npcf\_SMPolicyControl\_Update Request to the SM-PCF to forwards the UE Policy Container to the SM-PCF. The SMF+PGW-C provides SUPI, UE Policy Container and UE-PCF ID to the SM-PCF. The SM-PCF can notice that the UE-PCF Association Establishment with UE-PCF is allowed in this network by the presence of UE Policy Container in PCO and UE-PCF ID. + +NOTE: The SMF+PGW-C discovers and selects the UE-PCF as described in clause 6.3.7.1 of TS 23.501 [2]. + +3. The SM-PCF establishes the UE-PCF Association with the UE-PCF which is identified UE-PCF ID received from the SMF+PGW-C, and forwards the UE Policy Container to the UE-PCF. +4. The UE-PCF sends to SM-PCF the UE-PCF Association Establishment Response with result of UE-PCF Association establishment result. +5. The UE-PCF gets policy subscription related information and the latest list of PSIs from the UDR using Nudr\_DM\_Query service operation. The UE-PCF creates the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503 [4] (step 6 of Figure 4.16.11-1 of TS 23.502 [3] can be reused). +6. When the UE-PCF decides to provide the UE policy to the UE, the UE-PCF sends to SM-PCF the UE Policy Container. +7. The SM-PCF forwards the UE Policy Container to the SMF+PGW-C by Npcf\_SMPolicyControl\_Update Response. +8. The Initial Attach procedure is continued as described in Figure 5.3.2.1-1 of TS 23.401 [8]. The SMF+PGW-C sends the PCO which is including the UE Policy Container to the UE. The PCO can be included in Attach Accept. The UE sends the acknowledgement on successful reception of the UE Policy to the SMF+PGW-C, this acknowledgement can be included in the Attach Complete and Modify Bearer Request. +9. The SMF+PGW-C forwards the UE's acknowledgement by invoking Npcf\_SMPolicyControl\_Update Request to the SM-PCF. + +10. The SM-PCF forwards the UE's acknowledgement to the UE-PCF. + +### 6.20.2.2 UE Policy delivery procedure initiated by the PCF + +![Sequence diagram for UE Policy delivery procedure initiated by the PCF. The diagram shows interactions between UE, eNodeB, MME, Serving GW, SMF + PGW-C, PCF (SM-PCF), and PCF (UE-PCF).](a634891d16b60b21df90a35c2af72c67_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant Serving GW + participant SMF + PGW-C + participant PCF as PCF (SM-PCF) + participant UE-PCF as PCF (UE-PCF) + + Note right of UE-PCF: 1. URSP updates decision + UE-PCF->>PCF: 2. UE-PCF sends the UE Policy Container to SM-PCF + PCF->>SMF + PGW-C: 3. Npcf_SMPolicyControl_UpdateNotify Request (UE Policy Container) + Note left of SMF + PGW-C: 4. Step 2 to 5 described in TS 23.401, 5.4.3 (Update Bearer Request). The SMF+PGW-C sends the PCO which is including the UE Policy Container to the UE. The UE sends the acknowledgement on reception of the UE Policy + SMF + PGW-C->>PCF: 5. Npcf_SMPolicyControl_Update Request (acknowledgement) + PCF->>UE-PCF: 6. SM-PCF forwards the acknowledgement from the UE. + +``` + +Sequence diagram for UE Policy delivery procedure initiated by the PCF. The diagram shows interactions between UE, eNodeB, MME, Serving GW, SMF + PGW-C, PCF (SM-PCF), and PCF (UE-PCF). + +Figure 6.20.2-2: UE Policy delivery procedure initiated by the PCF + +1. The UE-PCF is notified from the UDR that the URSP is updated. +2. The UE-PCF sends to SM-PCF the UE Policy Container which includes the updated URSP. +3. The SM-PCF forwards the UE Policy Container to the SMF+PGW-C by Npcf\_SMPolicyControl\_UpdateNotify Request. +4. The SMF+PGW-C sends the PCO which is including the UE Policy Container to the UE. The step 2 to 5 described in Figure 5.4.3-1 of TS 23.401 [8] is used. The PCO can be included in Update Bearer Request, Downlink NAS Transport, and Direct Transfer. The UE sends the acknowledgement on successful reception of the UE Policy to the SMF+PGW-C, this acknowledgement can be included in Direct Transfer, Uplink NAS Transport, and Update Bearer Response. +5. The SMF+PGW-C forwards the UE's acknowledgement by invoking Npcf\_SMPolicyControl\_Update Request to the SM-PCF. +6. The SM-PCF forwards the UE's acknowledgement to the UE-PCF. + +### 6.20.2.3 URSP delivery over EPS Indication in 5GS + +During Registration procedure in 5GS, the UE sends UE Policy Container including the list of PSIs and URSP delivery over EPS Indication to AMF in Registration request as described in clause 4.2.2 of TS 23.502 [3]. + +AMF transparently forwards UE Policy Container to UE-PCF during UE Policy Association Establishment as described in clause 4.16.11. UE-PCF stores URSP delivery over EPS Indication. The UE-PCF determines whether the UE Policy Association established in 5GS can be maintained in EPS based on this indication as described in clauses 6.20.2.4 and 6.20.2.5. + +## 6.20.2.4 5GS to EPS Handover using N26 interface + +![Sequence diagram for 5GS to EPS Handover using N26 interface. The diagram shows the interaction between UE, E-UTRAN, NG-RAN, AMF, MME, SGW, V-SMF, V-UPF, SMF+PGW-C, and PGW-U+UPF. The process starts with a PDU Session and QoS flow setup in 5GS. The handover procedure involves several steps: 1. Handover required (NG-RAN to AMF), 2a. Nsmf_PDUSession_ContextRequest (AMF to MME), 2c. Nsmf_PDUSession_ContextRsp (MME to AMF), 3. Relocation request (AMF to MME), 4. Create session request (MME to SGW), 5. Create session response (SGW to MME), 6. Handover request (MME to NG-RAN), 7. Handover request ACK (NG-RAN to MME), 8. Create indirect data forwarding tunnel request/response (MME to SGW), 9. Relocation response (MME to AMF), 10a. Nsmf_PDUSession_UpdateSMContextRequest (AMF to V-SMF), 10c. Nsmf_PDUSession_UpdateSMContextResponse (V-SMF to AMF), 10b. N4 Session Modification (V-SMF to SMF+PGW-C), 11a. Handover command (AMF to NG-RAN), 11b. Handover command (NG-RAN to UE), DL Data forwarding (Home routed roaming case) (AMF to V-UPF), DL Data forwarding (non-roaming or local breakout roaming case) (AMF to PGW-U+UPF), 12a. Handover Complete (UE to NG-RAN), DL Data forwarding (NG-RAN to SGW), UL data (prepared bearers) (SGW to MME), 12b. Handover Notify (MME to AMF), 12c. Relocation Complete (AMF to MME), 12d. Relocation Complete Ack (MME to AMF), 12e. Nsmf_PDUSession_ReleaseSMContext (AMF to V-SMF), 13. Modify bearer Request (MME to SGW), 14a. Modify bearer Request (SGW to SMF+PGW-C), 15. N4 Session Modification (SMF+PGW-C to PGW-U+UPF), 16. Modify bearer Response (SMF+PGW-C to SGW), DL data (prepared bearers) (SGW to MME), 17. Modify bearer Response (MME to AMF), 18. TAU procedure (MME to SGW), 19. PGW initiated dedicated bearer activation (SGW to SMF+PGW-C), 20. Delete indirect data forwarding Tunnel request/response (MME to SGW), 21a. Delete indirect data forwarding tunnel (SGW to V-UPF), 21c. UE Context Release Command/Complete (AMF to NG-RAN), 21b. N4 Session Modification (SMF+PGW-C to PGW-U+UPF).](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +Sequence diagram for 5GS to EPS Handover using N26 interface. The diagram shows the interaction between UE, E-UTRAN, NG-RAN, AMF, MME, SGW, V-SMF, V-UPF, SMF+PGW-C, and PGW-U+UPF. The process starts with a PDU Session and QoS flow setup in 5GS. The handover procedure involves several steps: 1. Handover required (NG-RAN to AMF), 2a. Nsmf\_PDUSession\_ContextRequest (AMF to MME), 2c. Nsmf\_PDUSession\_ContextRsp (MME to AMF), 3. Relocation request (AMF to MME), 4. Create session request (MME to SGW), 5. Create session response (SGW to MME), 6. Handover request (MME to NG-RAN), 7. Handover request ACK (NG-RAN to MME), 8. Create indirect data forwarding tunnel request/response (MME to SGW), 9. Relocation response (MME to AMF), 10a. Nsmf\_PDUSession\_UpdateSMContextRequest (AMF to V-SMF), 10c. Nsmf\_PDUSession\_UpdateSMContextResponse (V-SMF to AMF), 10b. N4 Session Modification (V-SMF to SMF+PGW-C), 11a. Handover command (AMF to NG-RAN), 11b. Handover command (NG-RAN to UE), DL Data forwarding (Home routed roaming case) (AMF to V-UPF), DL Data forwarding (non-roaming or local breakout roaming case) (AMF to PGW-U+UPF), 12a. Handover Complete (UE to NG-RAN), DL Data forwarding (NG-RAN to SGW), UL data (prepared bearers) (SGW to MME), 12b. Handover Notify (MME to AMF), 12c. Relocation Complete (AMF to MME), 12d. Relocation Complete Ack (MME to AMF), 12e. Nsmf\_PDUSession\_ReleaseSMContext (AMF to V-SMF), 13. Modify bearer Request (MME to SGW), 14a. Modify bearer Request (SGW to SMF+PGW-C), 15. N4 Session Modification (SMF+PGW-C to PGW-U+UPF), 16. Modify bearer Response (SMF+PGW-C to SGW), DL data (prepared bearers) (SGW to MME), 17. Modify bearer Response (MME to AMF), 18. TAU procedure (MME to SGW), 19. PGW initiated dedicated bearer activation (SGW to SMF+PGW-C), 20. Delete indirect data forwarding Tunnel request/response (MME to SGW), 21a. Delete indirect data forwarding tunnel (SGW to V-UPF), 21c. UE Context Release Command/Complete (AMF to NG-RAN), 21b. N4 Session Modification (SMF+PGW-C to PGW-U+UPF). + +**Figure 6.20.2-3: (Figure 4.11.1.2.1-1 of TS 23.502 [3]) 5GS to EPS handover for single-registration mode with N26 interface** + +Step 18 includes the deregistration of the old AMF for 3GPP access from the HSS+UDM as specified in clause 4.11.1.5.3 in TS 23.502 [3]. The registered AMF for 3GPP access initiates UE Policy Association Termination procedure as defined in clause 4.16.13.1 in TS 23.502 [3]. The UE-PCF determines whether to terminate the UE Policy Association based on URSP delivery over EPS Indication received from UE (as described in clause 6.20.2.1 and 6.20.2.3). The UE-PCF rejects the Npcf\_UEPolicyControl\_Delete request from the AMF and informs to the AMF that the UE Policy Association can be maintained in EPS. In this case, the AMF initiates the procedure to move the UE Policy Association established between the AMF and UE-PCF to between SM-PCF and UE-PCF as described in clause 6.20.2.6. + +## 6.20.2.5 5GS to EPS Idle mode mobility using N26 interface + +![Sequence diagram for 5GS to EPS Idle mode mobility using N26 interface. The diagram shows the interaction between UE, eNB, NG-RAN, MME, AMF, SGW, V-SMF, V-UPF, SMF+PGW-C, PGW-U+UPF, PCF, and HSS+UDM. The process starts with a TAU trigger from the UE, followed by TAU Request and Response messages. The AMF sends a Context Request to the MME, which responds with Context Response. The AMF then sends a Create Session Request to the SGW, which responds with Create Session Response. The AMF also sends an Update Location Request to the HSS+UDM, which responds with Update Location Ack. The AMF sends a Nsmf_PDUSession_ContextRequest to the V-SMF, which responds with Nsmf_PDUSession_ContextResponse. The V-SMF sends a N4 Session Modification to the PGW-U+UPF, which responds with N4 Session Modification. The AMF sends a Nudm_UECM_DeregistrationNotification to the HSS+UDM, which responds with Nudm_UECM_DeregistrationResponse. The AMF also sends a Nudm_SDM_Unsubscribe to the HSS+UDM, which responds with Nudm_SDM_UnsubscribeResponse. The AMF sends a Nsmf_PDUSession_ReleaseSMContextRequest to the V-SMF, which responds with Nsmf_PDUSession_ReleaseSMContextResponse. The V-SMF sends a N4 Session Termination to the PGW-U+UPF, which responds with N4 Session Termination. The AMF sends a TAU Accept to the UE, which responds with TAU Complete. The AMF also sends a PGW initiated dedicated bearer setup if needed to the UE.](7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg) + +Sequence diagram for 5GS to EPS Idle mode mobility using N26 interface. The diagram shows the interaction between UE, eNB, NG-RAN, MME, AMF, SGW, V-SMF, V-UPF, SMF+PGW-C, PGW-U+UPF, PCF, and HSS+UDM. The process starts with a TAU trigger from the UE, followed by TAU Request and Response messages. The AMF sends a Context Request to the MME, which responds with Context Response. The AMF then sends a Create Session Request to the SGW, which responds with Create Session Response. The AMF also sends an Update Location Request to the HSS+UDM, which responds with Update Location Ack. The AMF sends a Nsmf\_PDUSession\_ContextRequest to the V-SMF, which responds with Nsmf\_PDUSession\_ContextResponse. The V-SMF sends a N4 Session Modification to the PGW-U+UPF, which responds with N4 Session Modification. The AMF sends a Nudm\_UECM\_DeregistrationNotification to the HSS+UDM, which responds with Nudm\_UECM\_DeregistrationResponse. The AMF also sends a Nudm\_SDM\_Unsubscribe to the HSS+UDM, which responds with Nudm\_SDM\_UnsubscribeResponse. The AMF sends a Nsmf\_PDUSession\_ReleaseSMContextRequest to the V-SMF, which responds with Nsmf\_PDUSession\_ReleaseSMContextResponse. The V-SMF sends a N4 Session Termination to the PGW-U+UPF, which responds with N4 Session Termination. The AMF sends a TAU Accept to the UE, which responds with TAU Complete. The AMF also sends a PGW initiated dedicated bearer setup if needed to the UE. + +Figure 6.20.2-4: (Figure 4.11.1.3.2-1 in TS 23.502 [3]) 5GS to EPS Idle mode mobility using N26 interface + +In step 15, The UE-PCF determines whether to terminate the UE Policy Association based on URSP delivery over EPS Indication received from UE (as described in clause 6.20.2.1 and 6.20.2.3). The UE-PCF rejects the Npcf\_UEPolicyControl\_Delete request from the AMF and informs to the AMF that the UE Policy Association can be maintained in EPS. In this case, the AMF initiates the procedure to move the UE Policy Association established between the AMF and UE-PCF to between SM-PCF and UE-PCF as described in clause 6.20.2.6. + +## 6.20.2.6 Relocate an established UE Policy Association to SM-PCF + +![Sequence diagram for Relocate an established UE Policy Association to SM-PCF. The diagram shows the interaction between AMF, SMF+PGW-C, SM-PCF, and UE-PCF. The AMF sends an Npcf_UEPolicyControl_Delete Request to the UE-PCF. The UE-PCF responds with Npcf_UEPolicyControl_Delete Response (Reject, UE Policy Association can be maintained in EPS). The AMF then determines which Policy Control Request Trigger(s) can be re-used in SMF. The AMF sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF+PGW-C. The SMF+PGW-C sends an Npcf_SMPolicyControl_Update Request to the SM-PCF. The SM-PCF sends an Npcf_UEPolicyControl_Update Request to the UE-PCF. The UE-PCF updates the stored UE Policy Association information and responds with Npcf_UEPolicyControl_Update Response. The SM-PCF responds with Npcf_SMPolicyControl_Update Response. The SMF+PGW-C responds with Nsmf_PDUSession_UpdateSMContext Response.](6984a27b2b89e0995d5216ec29b41d1c_img.jpg) + +Sequence diagram for Relocate an established UE Policy Association to SM-PCF. The diagram shows the interaction between AMF, SMF+PGW-C, SM-PCF, and UE-PCF. The AMF sends an Npcf\_UEPolicyControl\_Delete Request to the UE-PCF. The UE-PCF responds with Npcf\_UEPolicyControl\_Delete Response (Reject, UE Policy Association can be maintained in EPS). The AMF then determines which Policy Control Request Trigger(s) can be re-used in SMF. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Request to the SMF+PGW-C. The SMF+PGW-C sends an Npcf\_SMPolicyControl\_Update Request to the SM-PCF. The SM-PCF sends an Npcf\_UEPolicyControl\_Update Request to the UE-PCF. The UE-PCF updates the stored UE Policy Association information and responds with Npcf\_UEPolicyControl\_Update Response. The SM-PCF responds with Npcf\_SMPolicyControl\_Update Response. The SMF+PGW-C responds with Nsmf\_PDUSession\_UpdateSMContext Response. + +Figure 6.20.2-5: Relocation of an established UE Policy Association to SM-PCF + +1. As described in clauses 6.20.2.4 and 6.20.2.5, the AMF requests to UE-PCF to terminate the UE Policy Association, when the UE moves from 5GS to EPS. +2. The UE-PCF determines whether to terminate the UE Policy Association based on URSP delivery over EPS Indication received from UE (as described in clauses 6.20.2.1 and 6.20.2.3). The UE-PCF rejects the + +Npcf\_UEPolicyControl\_Delete request from the AMF and informs to the AMF that the UE Policy Association can be maintained in EPS. + +3. When the AMF is informed that the UE Policy Association can be reused in EPS, the AMF determines which Policy Control Request Triggers can be supported in SMF (e.g. Location change, PLMN change) among the PCRTs of the UE Policy Association. +4. The AMF sends UE-PCF ID, UE Policy Association ID, Policy Control Request Triggers for UE Policy Association (determined in step 3), and Information on the UE policy related Policy Control Request Trigger condition that can be met in Nsmf\_PDUSession\_UpdateSMContext Request to SMF+PGW-C. +5. The SMF+PGW-C transfers UE Policy Association information received from the AMF in step 4 to SM-PCF by Npcf\_SMPolicyControl\_Update Request. +6. The SM-PCF notices the UE Policy Association established in 5GS is moved from the AMF to the SM-PCF when SM-PCF receives UE-PCF ID and UE Policy Association ID from SMF+PGW-C. The SM-PCF sends UE Policy Association ID and Information on the UE policy related Policy Control Request Trigger condition that can be met in Npcf\_UEPolicyControl\_Update Request to UE-PCF. The UE-PCF updates the stored information provided by the AMF with the information provided by the SM-PCF. +7. The UE-PCF updates the policy decision based on the information provided by SM-PCF. Step 4 in clause 4.16.2.1.2 of TS 23.502 [3] can be reused. The UE-PCF updates Policy Control Request Trigger parameters for UE Policy Association to be supported in SMF+PGW-C (e.g. remove PCRTs that cannot be supported in SMF+PGW-C). +8. The UE-PCF sends UE Policy Container, Policy Control Request Triggers of UE Policy Association in Npcf\_UEPolicyControl\_Update Response to SM-PCF. SM-PCF stores the updated Policy Control Request Triggers of UE Policy Association. The UE Policy Container is delivered to the UE (as described in clause 6.20.2) after TAU procedure. +9. The SMF+PGW-C updates the PCRTs of UE Policy Association received from the AMF (in step 4) with the PCRTs of UE Policy Association received from the SM-PCF (in step 8). After this step, when a PCRT of UE Policy Association condition is met, the SMF+PGW-C sends Information on the UE policy related Policy Control Request Trigger condition that can be met to the SM-PCF and the SM-PCF reports it to the UE-PCF. +10. The SMF+PGW-C sends Nsmf\_PDUSession\_UpdateSMContext Response to AMF. The AMF notices the UE Policy Association is successfully moved to SM-PCF. + +### 6.20.3 Impacts on services, entities and interfaces + +#### SMF+PGW-C: + +- Shall be able to include the UE Policy Container received from the PCF into the PCO, and forward to the UE via SGW and MME transparently. +- Shall be able to forward the UE Policy Container from the UE to the UE-PCF. +- Shall be able to provide the UE-PCF ID to SM-PCF. +- Shall be able to forward the acknowledgement of UE reception of the UE Policy to the PCF. +- Shall be able to provide Information on the UE policy related Policy Control Request Trigger condition that can be met to SM-PCF when the condition is met. + +#### SM-PCF: + +- Shall be able to handle UE Policy Association with UE-PCF. +- Shall be able to provide to SMF+PGW-C, the UE Policy Container which includes the UE Policy for the UE in EPS. +- Shall be able to relocate the UE Policy Association established in 5GS from AMF to SM-PCF. + +#### UE-PCF: + +- Shall be able to handle UE Policy Association with SM-PCF. +- Shall be able to handle UE Policy Association for the UE in EPS based on the URSP delivery over EPS Indication provided by the UE. + +AMF: + +- Shall be able to relocate the UE Policy Association established in 5GS from AMF to SM-PCF. + +MME: + +- No impact. + +UE: + +- Shall be able to store the URSP received over EPS entities. +- Shall be able to send the acknowledgement of UE reception of the UE Policy to the PCF over EPS entities. +- Shall be able to send the list of PSIs stored in the UE to the PCF by encapsulating in UE Policy Container, and by including the UE Policy Container into PCO over EPS entities. + +## 6.21 Solution #21: Traffic Category with existing mechanism + +### 6.21.1 Description + +It is proposed to reuse the current Traffic Descriptor (TD) type to represent Traffic Category. + +#### Option 1: + +Introduce new special DNN in the TD to represent Traffic Category. DNN is composed of Network Identifier and optionally Operator Identifier. Network Identifier has a maximum length of 63 octets. It is enough to have standardized traffic categories. If it is an operator specific traffic category, Operator Identifier is involved. + +The applications that shares the same traffic category should be mapped to the same DNN in the TD. + +It is proposed to have DNNs considering the requirement from GSMA as described in clause 5.4. + +Some more DNN containing multiple bullets of GSMA requirement as described in clause 5.4 can also be introduced. + +NOTE 1: The DNN in corresponding Route Selection (RSD) could be different if the real DNN of the application is not the same as the one in TD as described in clause 6.6.2.1, TS 23.503 [4]. + +NOTE 2: It is assumed that the operator will allocate proper DNN to an application with considering its traffic category. How to allocate DNN to an application is based on current mechanism. It is assumed the operator will have agreement with the Application Service Providers to generate the URSP. + +NOTE 3: To cover the case that an application may share different traffic categories, DNN could be combination of different categories. + +#### Option 2: + +Introduce new standardized Application descriptor. A new OS Id value which means "Traffic Category" Type should be defined. the maximum length of OS App Id is 256 octets. It is enough to have standardized traffic categories and operator specific Traffic Categories. + +It is proposed to have following application descriptors considering the requirement from GSMA as described in clause 5.4. + +NOTE 4: More than one application descriptors can be provided in TD as described in clause 6.6.2.1, TS 23.503 [4]. Thus no need to introduce new application descriptors as combination of different categories. + +NOTE 5: It is assumed the operator will have agreement with the Application Service Providers to generate the URSP. + +## 6.21.2 Procedures + +No new procedure will be introduced. The PCF will transfer the URSP to the UE via UE Configuration Update procedure as defined in clause 4.2.4.3 of TS 23.502 [3]. + +## 6.21.3 Impacts on services, entities and interfaces + +UE/PCF: + +- Need to support the new standardized value of DNN/Application Descriptor in the Traffic descriptor. + +# 6.22 Solution #22: UE provisioned/configured with a mapping of application traffic to traffic categories + +## 6.22.1 Description + +A general description of the solution is as follows: + +- A UE is provisioned/configured with a mapping of Application Traffic to a Traffic Category (or one or more traffic categories). The UE may be configured with such mapping from an Application Function or from the PCF or based on pre-configuration. If provisioned by the PCF this mapping information is sent outside of a URSP rule, i.e. a new rule within UE policy information (ATC rule): +- When the UE receives such mapping, when the UE detects new Application Traffic the UE associates the application to the corresponding traffic category: + - The existing traffic descriptors defined in URSP rules can be used to map Application Traffic to one or more Traffic Categories. For example: + - An application with Application Descriptor (com.android.app1) is mapped to Traffic Category: "Gaming". + - An application sending traffic to a specific destination IP 3 tuple mapped to Traffic Category: "Streaming". + - Domain Descriptors (e.g. FQDN requested) mapped to one or more traffic categories: + - In such case the UE associates the destination IP addresses received in a DNS response to a traffic category. + - Non-IP descriptors mapped to one or more traffic categories. + - An application requesting DNN "IMS" is mapped to Traffic Category "Voice". + - An Application requesting connection capability for MMS is mapped to Traffic Category "Media". +- The URSP rule is enhanced with a Traffic Category Traffic Descriptor: + - When the UE receives URSP rules with Traffic Categories traffic descriptor then the UE uses the configuration received from the AF/PCF to associate detected application traffic to a traffic category and consider the URSP rule matched when the Traffic Category of the URSP rule matches the traffic category of the application. + +The solution can support both MNO specific and standardised traffic categories. The encoding of the Traffic Category can be defined in stage 3. For example, standardised traffic category can be encoded as a bit map as follows: + +- Bitmap: 00000001 --> Gaming (Standardised). +- Bitmap: 00000002 --> Voice (Standardised). +- Bitmap: 00000003 --> Reserved for operators (MNO specific). + +The solution has the advantage that the rules to associate an application (or application traffic) are provided by the MNO and does not rely on the application in the UE or the OS layer in the UE to indicate a traffic category for an application traffic. + +The procedures are shown in the next clause. + +## 6.22.2 Procedures + +### 6.22.2.1 Association of application traffic to a Traffic Category + +The UE associates application traffic to a traffic category based on "Application to Traffic Category" (ATC) rules received from the AF or the PCF. The rules provide information on how Application Traffic is mapped to a traffic category. + +The PCF can provide ATC rules to the UE using the UE configuration update for transparent policy deliver. The ATC rules are sent outside of URSP rule as a new type of rule within UE policies provisioned by the PCF. The UE can include ATC rules within a specific Policy Section identified by a Policy Section Identifier. The PCF may determine the ATC rules the UE requires based on the operating system supported by the UE. The procedure is shown in the figure below. + +![Sequence diagram showing the PCF provisioning Application to Traffic Categories Rules. The diagram involves four entities: UE, (R)AN, AMF, and PCF. The sequence starts with the UE registering with the PLMN. The PCF then decides to provide ATC rules to the UE. The PCF sends these rules to the AMF via Namf_Communication_N1N2MessageTransfer. The AMF then triggers a Network Triggered Service Request to the UE. The AMF delivers the ATC rules to the UE via a NAS Downlink transport message. The UE then associates the application traffic to a Traffic Category and sends a result back to the AMF. Finally, the AMF sends a Namf_Communication_N1MessageNotify to the PCF.](8adc21ec44b6c7debe36fed5b1bb044f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant PCF + + Note over UE, (R)AN, AMF, PCF: 0. UE registers with PLMN as per section 4.2.2.2 of 3GPP TS 23.502. May include OSId. + Note right of PCF: 1. PCF decides to Provide ATC rules to the UE + PCF->>AMF: 2. Namf_Communication_N1N2MessageTransfer + Note over UE, (R)AN, AMF: 3. Network Triggered Service Request + AMF->>UE: 4. Delivery of ATC rules within a Policy Section + UE->>AMF: 5. Result of the delivery + AMF->>PCF: 6. Namf_Communication_N1MessageNotify + Note left of UE: 7. UE associates application traffic to a Traffic Category + +``` + +Sequence diagram showing the PCF provisioning Application to Traffic Categories Rules. The diagram involves four entities: UE, (R)AN, AMF, and PCF. The sequence starts with the UE registering with the PLMN. The PCF then decides to provide ATC rules to the UE. The PCF sends these rules to the AMF via Namf\_Communication\_N1N2MessageTransfer. The AMF then triggers a Network Triggered Service Request to the UE. The AMF delivers the ATC rules to the UE via a NAS Downlink transport message. The UE then associates the application traffic to a Traffic Category and sends a result back to the AMF. Finally, the AMF sends a Namf\_Communication\_N1MessageNotify to the PCF. + +**Figure 6.22.2.1-1: PCF provisioning Application to Traffic Categories Rules** + +0. UE registers to the PLMN as per TS 23.502 [3]. The UE may include OSId of its operating system and a list of Policy Sections (identified by a PSI) installed at the UE. During registration the AMF selects a PCF for AM and SM policies. +1. The PCF determines that ATC rules are needed to be provided to the UE. The PCF determines based on: + - A Policy Section identified by a PSI is not installed at the UE or the Policy Section Identifier provided by the UE that includes ATC rules requires updating. + - A trigger from the UDM/UDR. +2. The PCF sends ATC rules to the AMF via an Namf\_Communication\_N1N2Message transfer service operation based on the UE Configuration Update for transparent policy delivery. +3. The AMF transparently sends the ATC rules to the UE. If the UE is in IDLE the AMF triggers a network triggered service request. +4. The ATC rules are sent to the UE via a NAS Downlink transport message + +5. The UE installs the rules and provides the result to the AMF via a NAS Uplink transport message. +6. The AMF forwards the ack to the PCF. +7. The UE associates applications to a traffic category based on the ATC rules. + +An Application Function may also provide ATC rules to the UE as shown in the figure below. + +![Sequence diagram showing AF provisioning ATC rules to a UE. The diagram illustrates the interaction between UE, (R)AN, AMF, PCF, UDM, UDR, NEF, and AF. The process starts with UE registration (1), followed by PCF subscribing to UDR for ATC rules (2). The AF creates an update request (3), which is sent to NEF (4). NEF authorizes and stores the request (5), and UDR determines PCF needs notification (6). UDR notifies PCF (7), PCF delivers policy via NAS (8), and UE associates application to traffic category (9).](a70e0adcabc973b01b413b6a141884f3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant PCF + participant UDM + participant UDR + participant NEF + participant AF + + Note left of UE: 1. UE registration + UE->>AMF: + Note right of PCF: 2. Nudr_DM_Subscribe (ATC rules) + PCF->>UDR: + Note right of AF: 3. Creation of the AF request (update ATC rules) + AF->>NEF: 4. Nnef_ServiceParameter_Create / Update / Delete Request + Note right of NEF: 5. NEF authorizes request. Storing / Updating / Removing the information + NEF->>UDR: + Note right of UDR: 6. Determines PCF is subscribed to be notified of ATC rule change + UDR->>PCF: 7. Nudr_DM_Notify (ATC rules) + Note left of UE: 8. UE Policy delivery Via NAS + UE->>AMF: + Note left of UE: 9. UE associates an application to a traffic category + +``` + +Sequence diagram showing AF provisioning ATC rules to a UE. The diagram illustrates the interaction between UE, (R)AN, AMF, PCF, UDM, UDR, NEF, and AF. The process starts with UE registration (1), followed by PCF subscribing to UDR for ATC rules (2). The AF creates an update request (3), which is sent to NEF (4). NEF authorizes and stores the request (5), and UDR determines PCF needs notification (6). UDR notifies PCF (7), PCF delivers policy via NAS (8), and UE associates application to traffic category (9). + +**Figure 6.22.2.1-2: AF provisioning ATC rules to a UE** + +1. The UE registers with the PLMN network as per TS 23.502 [3]. +2. The PCF subscribes from the UDR to be notified of change/update of ATC rules. +3. The AF decides to update ATC rules for a UE. +4. The AF sends an Nnef\_ServiceParameterCreate request including parameters for ATC rules determination. +5. The NEF authorizes the request and stores the ATC rules in the UDR. The NEF stores the AF request information in the UDR as the "Application Data" (Data Subset setting to "Service specific information") together with the assigned Transaction Reference ID. +6. The UDR determines that the PCF needs to be notified. +7. The UDR notifies the PCF in a Nudr\_DM\_Notify service operation. +8. The PCF sends update ATC rules using the UE Configuration Update procedure for transparent policy delivery (as per steps 2-6 of Figure 2.3). +9. The UE associates application to an application category based on the ATC rules. + +Alternatively (instead of steps 2-7), the UPF may also be configured to perform traffic classification and report back to the PCF (via the SMF) the traffic category mapping. In this case, during the SM Policy Association Establishment procedure, the PCF may provide Usage Reporting Rules that include one or more traffic classification triggers to the UPF. The attributes in the "Usage Report" as defined in Table 5.8.2.11.7-1 of TS 23.501 [2] are extended to support traffic classification and the "traffic category" is reported by the UPF in a new attribute in the report. + +## 6.22.2.2 Enhancing URSP rule with a Traffic Category Traffic Descriptor + +The URSP rule is enhanced to include a Traffic Category Traffic Descriptor. How the Traffic Category Traffic Descriptor is encoded is up to stage 3 design. + +When the UE is provisioned with a URSP rule containing a Traffic Category traffic descriptor then for every detected application traffic the UE considers this URSP rule applicable when the Traffic Category of the application detected matches the Traffic Category of the Traffic Descriptor in the URSP rule. + +If the UE has received URSP rules with Traffic Category traffic descriptors but the UE did not receive ATC rules or cannot identify the traffic category of the application traffic detected (i.e. the ATC rules do not provide any association for the application traffic detected) the UE considers the rule not applicable and moves to the next URSP rule in the order of precedence. + +An example implementation is shown in the figure below. + +![Figure 6.22.2.2-1: Example implementation for Traffic Classification and matching a URSP rule based on Traffic Category. The diagram shows a sequence of interactions between a UE Application, Upper Layer (Mobile OS), NAS layer, and external rule sets (URSP Rules and ATC rules).](4537891530c9f6f139a2e1ebf544edc4_img.jpg) + +``` + +sequenceDiagram + participant UE Application + participant Upper Layer (Mobile OS) + participant NAS layer (6. Find matching URSP rule for Traffic Category ID) + participant URSP Rules + participant ATC rules + + Note right of UE Application: 1. Request network connection + UE Application->>Upper Layer: + Note right of Upper Layer: 2. Traffic Descriptor (AppID) + Upper Layer->>NAS layer: + Note right of NAS layer: 3. Traffic Descriptor (AppID) + NAS layer->>ATC rules: + Note right of ATC rules: 4. Finds Traffic Category for App ID + ATC rules->>NAS layer: 5. Traffic Category ID + Note right of NAS layer: 6. Find matching URSP rule for Traffic Category ID + NAS layer->>URSP Rules: + Note right of NAS layer: 7. Matching Route Selection Descriptor (DNN, S-NSSAI) + NAS layer->>Upper Layer: + Note right of Upper Layer: 8. Establish PDU Session + Upper Layer->>UE Application: 9. Connection established + +``` + +Figure 6.22.2.2-1: Example implementation for Traffic Classification and matching a URSP rule based on Traffic Category. The diagram shows a sequence of interactions between a UE Application, Upper Layer (Mobile OS), NAS layer, and external rule sets (URSP Rules and ATC rules). + +**Figure 6.22.2.2-1: Example implementation for Traffic Classification and matching a URSP rule based on Traffic Category** + +1. An application in a UE requests a network connection from the operating system in the UE. +2. The mobile operating system requests a network connection including the AppID of the application. +3. The UE determines that URSP rules include Traffic Categories Traffic Descriptor and determines a Traffic Category. +4. The UE finds the traffic category based on the ATC rules. +- 5-6. The UE finds a matching URSP rules based on the Traffic Category ID. +- 7-8. A PDU session is established based on the RSD of the matched URSP rule. +9. The Mobile OS notifies the application that a connection is established. + +## 6.22.3 Impacts on services, entities and interfaces + +**Editor's note:** This clause captures impacts on existing 3GPP nodes and functional elements. + +- URSP rule is enhanced with a new Traffic Descriptor for supporting Traffic Category. +- New Policy Section is defined to include ATC rules. + +PCF: + +- Determine and provision updated UE Policy (ATC rules) based on detected traffic category. + +SMF: + +- Install URR (Usage Reporting Rules) that include traffic classification trigger on the UPF. +- Indicate the traffic category information based on Usage Reports to PCF. + +UPF: + +- Determine the Traffic category based on URR and provide Usage Reports including the traffic category mapping to the SMF. + +## 6.23 Solution #23: Support standardized and operator-specific traffic categories in URSP + +### 6.23.1 Description + +As per the LS received from GSMA, the traffic generated by a UE could be grouped into various traffic categories, enabling each traffic category to be handled differently, e.g. mapped to a different slice. Some example traffic categories are as below: + +Enterprise: Traffic from one or more applications related to an Enterprise service. + +Gaming: Traffic from one or more applications related to Gaming service, e.g. with low latency requirement. + +Video Streaming: Traffic from one or more applications related to Video Streaming, e.g. HD video streaming, 4K video streaming. + +A new component "traffic category" is introduced in the traffic descriptor part of the URSP rule. The "traffic category" shall support standardized values specified by 3GPP and values that are reserved for operator specific traffic categories. For example, the Traffic category can be encoded as below (this is a stage 3 decision): + +``` + +Bits +8 7 6 5 4 3 2 1 +0 0 0 0 0 0 0 1 Enterprise +0 0 0 0 0 0 1 0 Gaming +0 0 0 0 0 0 1 1 Video Streaming +0 0 0 0 0 1 0 0 +to +0 1 1 1 1 1 1 1 Spare for standardized traffic categories +1 0 0 0 0 0 0 0 +to +1 1 1 1 1 1 1 1 Reserved for Operator specific traffic categories + +``` + +**Editor's note:** It is FFS whether a new TD component "traffic category" is introduced or to re-use/extend an existing TD component e.g. Connection capabilities to support the new standardized and operator defined traffic categories. + +An application can indicate a traffic category in its request which the UE then matches with the traffic category component in the Traffic Descriptor of the URSP rule. Only one traffic category can be included in a single request. However, a single application may indicate different traffic category in different requests, for example, an application may indicate one traffic category in the traffic descriptor for IM or chat session while it may indicate a different traffic category in the traffic descriptor for live video or streaming etc. A given traffic category can be simultaneously used by multiple applications. + +An application may request any traffic category from the traffic category values standardized by 3GPP or from the operator specific traffic category values. + +**Editor's note:** It is FFS whether and how the UE or the Network verifies that an application is requesting for the correct traffic category. + +## 6.23.2 Procedures + +When an application starts, or at a later time, it may request for a specific traffic category. The traffic categories are defined by the 3GPP and are independent of the Operating System used in the UE. The traffic category requested by an application may be either a traffic category standardized by the 3GPP or a value that is specified by the MNO. The application requests a traffic category in a way similar to existing traffic descriptors, which is then pushed to the URSP layer transparently through the OS layer. Traffic categories shall be transparent to the OS layer to allow MNOs to define operator-specific traffic categories and still enable the application to request for such traffic categories. + +NOTE 1: The implementation details of how the application indicates the requested traffic category are outside the scope of 3GPP. + +A UE of a previous release that does not support "Traffic Category" shall ignore the URSP rules with "Traffic Category" according to clause 4.2.3 of TS 24.526 [10] "Unknown or unexpected URSP rules". + +NOTE 2: Based on UE implementation, if the UE does not support "Traffic category" TD request for "Traffic category" by an application can be disabled. + +## 6.23.3 Impacts on services, entities and interfaces + +The solution has the following impacts: + +PCF: + +- PCF shall support the new parameter "traffic category" in traffic descriptor part of the URSP rule. + +UE: + +- UE shall support receiving "traffic category" from the application and match it with the "traffic category" component in the Traffic Descriptor provided as part of the URSP rule. + +# 6.24 Solution #24: Introduction of Traffic Category into URSP rules + +## 6.24.1 Description + +In order to have no impact or further work to application layer, a new mapping rules can be introduced to UE of traffic category. + +The application on UE still use the original parameters in Traffic Descriptor to describe the features of application traffic, for example, the FQDN, DNN or IP-5-tuple. But the Traffic Category in TD, can be the set the combination of multiple traffic characteristic identification filter to identify the traffic from different application. And before the UE maps the application traffic to specific PDU session that RSDs corresponds to, the UE can map the application traffic to a specific traffic category in TD. + +For example, according to the FQDNs, the UE can identify this traffic to a specific traffic category for video or music. Another example, according to the destination IP address and DNN of application traffic, the UE can identify the traffic category as enterprise because the IP address located in the IP range that the enterprise served and the DNN is a local DN. + +According to this design, one of the examples of introducing traffic category are listed below: + +**Table 6.24.1-1: Example of URSP rules contains traffic category** + +| <b>Traffic Descriptor</b> | <b>Route Selection Descriptor</b> | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rule Precedence =1<br><br>Traffic Descriptor: Application descriptor=App1 | Route Selection Descriptor Precedence=1<br>Network Slice Selection: S-NSSAI-a<br>SSC Mode Selection: SSC Mode 3<br>DNN Selection: internet<br>Access Type preference: 3GPP access | +| Rule Precedence =2<br><br>Traffic Descriptor: Traffic Category = Video = {Application Descriptor = App2} or {IP Descriptor = 10.1.1.1} | Route Selection Descriptor Precedence =2<br>Network Slice Selection: S-NSSAI-a<br>Access Type preference: Non-3GPP access | +| Rule Precedence =3<br><br>Traffic Descriptor: Traffic Category = Game = {Domain Descriptor = ABC.com} + {DNN = DNN1} + {Connection Capabilities = "ims"} | Route Selection Descriptor Precedence=1<br>Network Slice Selection: S-NSSAI-b<br>SSC Mode Selection: SSC Mode 2 | +| Rule Precedence =4<br><br>DNN = local.DN.1 | Route Selection Descriptor Precedence =2<br>Access Type preference: Non-3GPP access | + +NOTE 1: It is up to operator's configuration that how to design the combination of traffic characteristic identification filter in a certain Traffic Category. The original Traffic Descriptor can be co-existed with newly introduced Traffic category in TD. + +NOTE 2: As the example above, the operators can set the different precedence of TD, including the Traffic Category. For example, if the traffic from an application can both satisfy the original TD and Traffic Category, which has the higher precedence will be performed first. + +NOTE 3: The Traffic Category can be the combination of multiple traffic characteristic identification filter. It is also possible that the application traffic can meet one of the Traffic characteristics in the Traffic Category. + +NOTE 4: For a certain application traffic, it is possible to be classified as different traffic category. The final result of traffic category depends on the design of TD, for example, the precedence of TD, and the UE implementation. + +And after mapping to specific traffic category, how to apply the application traffic to RSDs are reuse the mechanism in current URSP rules. + +Also, one application traffic can be mapped to multiple Traffic category. For example, one application traffic which has the feature of Application descriptor, can be mapped to Traffic Category = Enterprise or Traffic Category = Game at the same time. + +## 6.24.2 Procedure + +After UE receives the URSP rules from PCF, the UE should do the following steps: + +- Mapping the application traffic to Traffic Descriptor, as the existing URSP rules mechanism. +- According to the Traffic Descriptor that the application mapping to, the UE has the two selection according to the URSP rules delivered by PCF: + - (Existing mechanism in URSP rules) The application traffic is matched to a certain Traffic Descriptor; + - The application traffic is matched to a certain Traffic Descriptor, and there exists the Traffic Category in this Traffic Descriptor. But for the Traffic Category, it can be the combination of multiple traffic characteristic identification filter. It is up to operator's configuration that how to design the combination of traffic characteristic identification filter in a certain Traffic Category. + +3. After determination of the Traffic Descriptor, the UE applies the application traffic to specific PDU sessions according to the RSDs. This is the same procedure as defined in URSP rules. + +### 6.24.3 Impacts on services, entities and interfaces + +**Editor's note:** This clause lists impacts to services and interfaces. + +PCF: + +- Introduce Traffic Category into URSP rules. The Traffic Category in TD, can be the set the combination of multiple traffic characteristic identification filter to identify the traffic from different application into the same traffic category. It is also ok that the application traffic can meet one of the Traffic characteristics in the Traffic Category. + +UE: + +- Mapping the application traffic which belongs to the specific Traffic Category in Traffic Descriptor according to the traffic characteristic identification filter in Traffic Category. + +## 6.25 Solution #25: Support standardized and operator-specific traffic categories in URSP + +### 6.25.1 Description + +In the current specification, application descriptors (short for 'APP ID') is defined as one TD in URSP rules. Application descriptors is used to identify the Application(s) that is(are) running on the UE's OS as specified in clause 6.6.2 of TS 23.503 [4] "UE Route Selection Policy information". + +To resolve the KI#4, application descriptors as one TD in URSP rules is to leverage for supporting standardized and operator-specific traffic categories in URSP. The special value of application descriptors can be defined or used for standardized and operator-specific traffic categories, and other value of application descriptor can be used for non-special application(s). + +For example: + +- Assuming that there are standardized and operator-specific traffic categories like "video", "games", "streaming" and "enterprise"; +- So the following application descriptors value can be defined or used for standardized and operator-specific traffic categories: + +**Table 6.25.1-1** + +| Special value of application descriptors (short for 'APP ID') | standardized and operator-specific traffic categories | +|---------------------------------------------------------------|-------------------------------------------------------| +| APP ID= aaaa | video | +| APP ID= bbbb | games | +| APP ID= cccc | streaming | +| APP ID= dddd | enterprise | +| ..... | ..... | + +So the solution to reuse the application descriptors as one TD in URSP rules to define special value for standardized and operator-specific traffic categories in URSP has meet the Key issue#4. + +### 6.25.2 Procedures + +The solution reuses existing procedures. + +## 6.25.3 Impacts on Existing Nodes and Functionality + +None. + +## 6.26 Solution #26: Traffic categories based on 5G QoS characteristics + +### 6.26.1 Description + +The 5G QoS characteristics describe the edge-to-edge packet treatment received by a QoS flow between the UE and UPF as described in clause 5.7.3 of TS 23.501 [2] in terms of various performance characteristics. These performance characteristics include Resource type (GBR, non-GBR), Priority level, Packet delay budget, Packet error rate, Averaging window, Maximum data burst volume, etc. Standardized 5QI values are specified for services that are frequently used and the one-to-one mapping between standardized 5QI values and the 5G QoS performance characteristics is specified in table 5.7.4-1 of TS 23.501 [2]. + +A new component "traffic category" is introduced in the traffic descriptor part of the URSP rules to support standardized values specified by 3GPP and values that are reserved for operator specific traffic categories. The encoding of these traffic categories can be specified in stage 3 in TS 24.526 [10]. + +#### 6.26.1.1 Traffic categories based on service type + +Traffic categories can be defined based on type of service handled by an application. As an example, enterprise class applications could include traffic categories for email, browsing, chat, conferencing, voice, etc. Similarly gaming applications could include real-time gaming, interactive gaming and other games which could include XR type of traffic as well. Similarly, video streaming class of applications could also include live or buffered streaming, HD streaming, 4K streaming traffic, etc. For each of these service types, the traffic categories can then be mapped to specific 5G QoS performance characteristics as specified in table 5.7.4-1 of TS 23.501 [2]. In addition to different well-known services, traffic categories can also be operator specific or even have specific QoS attributes or parameters that may not map to a well-known service. + +The traffic category values depend on the intended granularity of the categorization. They can be either defined based on different high level application classes or service types such as Enterprise, Gaming, Streaming, Operator specific, etc. or they can be defined with finer granularities, e.g. voice, conferencing, real-time gaming, interactive gaming, live streaming, buffered streaming, etc. These finer granular values may belong to one or more high level application classes or service types and can better assist in mapping specific application traffic or flows to appropriate slices. + +The values of 5G QoS performance characteristics are reproduced below from table 5.7.4-1 of TS 23.501 [2] for easy reference. + +**Table 6.26.1.1-1: Traffic categories based on Service type of different applications** + +| Traffic Category | 5QI Value | Resource Type | Default Priority Level | Packet Delay Budget | Packet Error Rate | Default Maximum Data Burst Volume | Default Averaging Window | +|------------------------------|-----------|--------------------|------------------------|---------------------|-------------------|-----------------------------------|--------------------------| +| <b>Enterprise Class</b> | | | | | | | | +| Voice traffic | 1 | GBR | 20 | 100 ms | $10^{-2}$ | N/A | 2000 ms | +| Email, browser, chat | 6 | Non-GBR | 60 | 300 ms | $10^{-6}$ | N/A | N/A | +| Conferencing | 2 | GBR | 40 | 150 ms | $10^{-3}$ | N/A | 2000 ms | +| <b>Gaming Class</b> | | | | | | | | +| Real time Gaming | 3 | GBR | 30 | 50 ms | $10^{-3}$ | N/A | 2000 ms | +| Interactive Gaming | 7 | GBR | 70 | 100 ms | $10^{-3}$ | N/A | N/A | +| Augmented Reality | 80 | GBR | 68 | 10 ms | $10^{-6}$ | N/A | N/A | +| <b>Video Streaming Class</b> | | | | | | | | +| Live streaming | 71 | GBR | 56 | 150 ms | $10^{-6}$ | N/A | 2000 ms | +| Buffered Streaming | 8 | Non-GBR | 80 | 300 ms | $10^{-6}$ | N/A | N/A | +| HD Streaming | 90 | Delay-critical GBR | 25 | 20 ms | $10^{-4}$ | 63000 bytes | 2000 ms | + +NOTE: The above traffic categories are just illustrative examples, other traffic categories may be added as needed. + +### 6.26.1.2 Traffic categories based on Traffic characteristics + +Traffic categories can also be defined directly based on traffic characteristics and the specific QoS attributes could have a relative priority level. As an example, for a certain class of traffic, there could be relative priority among the QoS attributes latency and bandwidth (e.g. low latency and high bandwidth with latency as higher priority). Priority can be given to single or multiple QoS attributes (e.g. prioritize latency and packet error rate over bandwidth for voice traffic, prioritize latency and bandwidth over packet error rate for gaming or video streaming traffic, etc.). + +The traffic categories could be defined as follows based on different traffic characteristics. + +**Table 6.26.1.2-1: Traffic categories based on Traffic characteristics of different applications** + +| Traffic Category | | | Service Type | Usage examples | +|------------------|--------|-----------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Latency | Loss | Bandwidth | | | +| Low | Normal | Low | Real-time online interaction | Games | +| Normal | Normal | Normal | Default bearer | Best Effort. Default service class; pretty much a mix of everything. | +| High | Low | High | Video Streaming | Youtube, Netflix, Hulu | +| High | Normal | High | AR/VR | | +| High | Normal | Normal | Background | Bulk data upload | +| High | High | Normal | Background (alt) | "Background", user-initiated, high delay tolerant, high loss tolerant, elastic flow, variable size. e.g. user-initiated iCloud synching or Time Capsule backup; or traffics of background applications, for which there is some progress feedback. | +| Any | Any | Any | Off Peak Data/Cost | Push traffic | + +NOTE: The above traffic categories are just illustrative examples, other traffic categories may be added as needed. + +### 6.26.2 Procedures + +Different applications know the kind of traffic they can generate, and they can classify the traffic based on the above defined traffic categories. An application may request for a specific traffic category from the execution environment (OS). Such a request triggers the UE to determine whether this new application traffic can be associated to an established PDU session, or the UE needs to establish a new PDU session based on URSP rules including the matching traffic category in the traffic descriptor. The requested traffic category by the application may be either a standardized value specified by 3GPP or an operator specific value. Traffic categories are transparent to the execution environment (OS) to allow operators to define operator specific traffic categories. + +NOTE: The implementation details of how the application indicates the requested traffic category to the execution environment (OS) are outside the scope of 3GPP. + +### 6.26.3 Impacts on services, entities and interfaces + +UE: + +- Able to process application requested traffic category and match it with the traffic category component of the traffic descriptor provided as part of the URSP rule. + +PCF: + +- Introduce traffic category into URSP rules and design the mapping rules of traffic categories. + +## 6.27 Solution #27: URSP provisioning and updating in roaming + +### 6.27.1 Description + +This is a solution related to the Key Issue #1 URSP in VPLMN, that aims to address the following aspects: + +- How to provide URSP Rules in roaming to the UE. How the HPLMN and VPLMN are involved in such procedure. +- Whether and how to support URSP enhancements to support routing of the application traffic with different URSP rules in different PLMNs. + +In addition, backward compatibility with the existing framework of policy control based on HPLMN will be maintained as stated in the KI description. + +This solution proposes that when the UE is roaming, the HPLMN may provide URSP Rules to the UE as in the existing baseline, in addition the VPLMN can provide URSP Rules. For the handling at the UE, a similar behaviour as for ANDSP Rules is proposed: When the UE is roaming, and the UE has valid URSP rules from both HPLMN and VPLMN the UE gives priority to the valid URSP rules from the VPLMN. + +The VPLMN provides URSP Rules to UE that contain RSD components that comply with the S-NSSAI subscription information defined in Table 6.2-1 in TS 23.503, then extended with the indication of LBO allowed as follows: + +**Table 6.27.1-1: UE context policy control subscription information** + +| Information name | Description | Category | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Subscriber categories | List of category identifiers associated with the subscriber | Optional | +| Tracing Requirements | Tracing requirements as defined in TS 32.421 [13] | Optional | +| PEI | The Permanent Equipment Identifier of the UE. | Optional | +| OSId | Identifies the operating system supported by UE. | Optional | +| Indication of UE support for ANDSP | Indicates the UE support for ANDSP. | Optional | +| S-NSSAI subscription information | Contains the list of subscribed S-NSSAIs, its associated subscribed DNNs. For each DNN, it includes the Allowed PDU Session types, the Allowed SSC modes, the ATSSS information and the LBO roaming information (NOTE). | Optional | +| NOTE: ATSSS information is defined in Table 5.2.3.3.1-1 of TS 23.502 [3] and Indicates whether MA PDU Session establishment is allowed. LBO roaming is defined in Table 5.2.3.3.1-1 of TS 23.502 [3] and Indicates whether LBO roaming is allowed per DNN or per (S-NSSAI and DNN) | | | + +The S-NSSAI subscription information is stored at the UDR at the HPLMN, provided to the H-PCF. The H-PCF sends the S-NSSAI subscription information to the VPLMN based on local policies that states whether VPLMN can provide URSP Rules to the UE and whether the LBO roaming is allowed. The H-PCF only provides S-NSSAI subscription information for this DNNs or (S-NSSAI and DNN) combinations that has LBO roaming allowed set. The V-PCF maps the DNN,S-NSSAI value in the VPLMN to the DNN,S-NSSAI values in the HPLMN either retrieving this from NSSF or from AMF. + +The V-PCF generates URSP Rules for traffic that will be offloaded at the VPLMN, either due to AF providing Application guidance for URSP rules determination defined in clause 6.6 of TS 23.548 [5] or due to local policies at the V-PCF. The V-PCF may decide to offload application traffic to a certain DNN, S-NSSAI in the VPLMN based on e.g. load in the network that can be derived from analytics at certain time of day. The V-PCF provides the list of PSIs including the VPLMN ID to identify them at the UE. + +The H-PCF can instruct the UE not to accept URSP Rules from the VPLMN, The H-PLMN provides this indication to the UE when the UE Policy Authorization is established. + +### 6.27.1.1 Characteristics of the solution + +These are some of the characteristics of this solution that aims to motivate the advantages to allow the VPLMN to provide URSP Rules to roamers. + +- 1- Enables the VPLMN to have better control on how to route traffic in their network while complying with the HPLMN S-NSSAI subscription information and the Application guidance, if provided. +- 2- Reduces the amount of configuration information that is needed at the HPLMN, e.g. a NEF or at the H-PCF to map the validity conditions on location to the TAIs or Cell IDs at the VPLMN. +- 3- Reduces the amount of signalling to report subscribed PCRTs to the HPLMN, in the most efficient way the HPLMN requires no PCRTs. +- 4- It is backward compatible with the existing policy framework given that the HPLMN provides URSP Rules for its subscribers as in the design base, then enhanced to the possibility for the VPLMN to provide URSP Rules for those subscribers that have LBO roaming allowed in their HPLMN subscription. + +Some scenarios: + +- Certain corporate application reachable via a DNN, S-NSSAI only in some locations, some of these locations are at the VPLMN. A HPLMN may decide to allow LBO roaming for this DNN, S-NSSAI for the corporate users, then the VPLMN provide URSP Rules to route application traffic to a DNN, S-NSSAI when the UE is at that location. In this scenario the AF can provide guidance for URSP and the location where the corporate network is accessible will be mapped by NEF at the VPLMN to the list of TAIs and Cell IDs in the access network. +- A HPLMN may decide not to allow the VPLMN to provide URSP Rules, then the S-NSSAI subscription information is not sent to the V-PCF. If no S-NSSAI subscription data is received or if received but the LBO roaming allowed indication is set to "not allowed", then the V-PCF generates no URSP Rules. + +## 6.27.2 Procedure for UE Policy Association Establishment with VPLMN provided URSP Rules + +![Sequence diagram for UE Policy Association Establishment when roaming (VPLMN provides URSP Rules). The diagram shows interactions between AMF, V-PCF, and H-PCF. The AMF initiates the process with a decision to establish a UE policy association. The V-PCF sends a request to the H-PCF, which responds. The V-PCF then responds to the AMF. The H-PCF generates HPLMN provided URSP Rule(s) and sends an update notify request to the V-PCF. The V-PCF generates VPLMN provided URSP Rule(s) and triggers a UE configuration update procedure. Finally, the V-PCF sends an update request to the H-PCF, which responds.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant V-PCF + participant H-PCF + + Note left of AMF: 1. Decision to establish UE policy Association + AMF->>V-PCF: 2. Npcf_UEPolicyControl create Request + V-PCF->>H-PCF: 3. Npcf_UEPolicyControl create Request + H-PCF-->>V-PCF: 4. Npcf_UEPolicyControl create Response + V-PCF-->>AMF: 5. Npcf_UEPolicyControl create Response + Note right of H-PCF: 6a. Generate HPLMN provided URSP Rule(s) + H-PCF-->>V-PCF: 7. Npcf_UEPolicyControl UpdateNotify request + V-PCF-->>H-PCF: 8. Npcf_UEPolicyControl UpdateNotify Response + Note left of V-PCF: 6b. Generate VPLMN provided URSP Rule(s) + Note left of AMF: 9. UE configuration update procedure + V-PCF-->>H-PCF: 10. Npcf_UEPolicyControl Update Request + H-PCF-->>V-PCF: 11. Npcf_UEPolicyControl Update Response + +``` + +Sequence diagram for UE Policy Association Establishment when roaming (VPLMN provides URSP Rules). The diagram shows interactions between AMF, V-PCF, and H-PCF. The AMF initiates the process with a decision to establish a UE policy association. The V-PCF sends a request to the H-PCF, which responds. The V-PCF then responds to the AMF. The H-PCF generates HPLMN provided URSP Rule(s) and sends an update notify request to the V-PCF. The V-PCF generates VPLMN provided URSP Rule(s) and triggers a UE configuration update procedure. Finally, the V-PCF sends an update request to the H-PCF, which responds. + +**Figure 6.27.2-1: UE Policy Association Establishment when roaming (VPLMN provides URSP Rules)** + +This procedure takes the UE Policy Association Establishment procedure in roaming case as specified in clause 4.16.11 of TS 23.502 [3] as basis: + +- 1,2, 3. Same as steps 1, 2 and 3 in clause 4.16.11 of TS 23.502 [3]. + 4. Same as step 4 in in clause 4.16.11 of TS 23.502 [3], in addition the H-PCF may include the S-NSSAI subscription information defined in Table 6.27.1-1. + 5. Same as step 5 in in clause 4.16.11 of TS 23.502 [3], in addition the V-PCF stores the S-NSSAI subscription information as part of the UE Context and may provide additional PCRTs to the AMF. + - 6a,7,8. The (H-)PCF may create a UE Policy Container to be sent to the UE as defined in steps 7 and 8 in clause 4.16.11 of TS 23.502 [3]. + - 6b. The (V-)PCF may create a UE Policy Container to be delivered to the UE. +- NOTE: If step 6b happens it takes place at any time after step 5. +9. The (V-)PCF triggers UE Configuration Update Procedure to send the UE policy container as defined in step 8 in clause 4.5.11 of TS 23.502 [3]. + 10. The V-PCF checks if the notification response is treated it locally or is to be sent to the H-PCF, if so step 9 in clause 4.5.11 of TS 23.502 [3] occurs. + +11. Same as step 10 in H-PCF clause 4.5.11 of TS 23.502 [3]. + +### 6.27.3 PDU Session establishment for LBO + +The procedure for PDU Session establishment for LBO specified in clause in TS 23.502 [3] remains unchanged with the following clarifications: + +The UE checks the validity of the RSD in the URSP Rule for VPLMN provided URSP Rules as follows: + +- If any S-NSSAI(s) is present, the S-NSSAI(s) is in the Allowed NSSAI. + +The UE checks the validity of the RSD in the URSP Rule for HPLMN provided URSP Rules as follows: + +- If any S-NSSAI(s) is present, the mapping of the Allowed NSSAI to HPLMN S-NSSAI(s) for the roaming case. + +In both cases the UE provides both the S-NSSAIs of the Home PLMN and Visited PLMN at PDU Session establishment as described in clause 5.15.5.3 of TS 23.501 [2]. The UE provides the PDU Session parameters as provided in the selected RSD of the URSP Rule, i.e. for VPLMN provided URSP Rules the PDU Session parameters are related to the VPLMN. + +For those URSP Rules provided by the VPLMN, the V-PCF subscribes to DNN replacement PCRT to the AMF. Then, the AMF sends the DNN to the PCF to replace the DNN of the serving PLMN to the DNN of the HPLMN. The AMF sends both the serving PLMN DNN if provided and the DNN of the HPLMN to the SMF then SMF checks the SMF subscription data retrieved from UDM. + +NOTE: It is assumed that a serving S-NSSAI maps to only one HPLMN S-NSSAI. It is assumed that a serving DNN maps to only one PLMN S-NSSAI. + +### 6.27.4 AF guidance for URSP determination + +![Sequence diagram for AF guidance for URSP determination. The diagram shows interactions between UE, (R)AN, AMF, V-PCF, UDR, NEF, and AF. The process starts with UE registration and policy association. The AF sends a creation request to the NEF, which is stored in the UDR. The UDR then notifies the V-PCF, which in turn notifies the AMF. The AMF then handles UE policy delivery. Finally, the V-PCF sends an event exposure notification to the AF, and the AF sends a service parameter notification to the NEF.](55048d730ad7a041082df5cc76d53219_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant V-PCF + participant UDR + participant NEF + participant AF + + Note right of AF: 1. Creation of the AF request + AF->>NEF: 2. Nnef_ServiceParameter_Create / Update / Delete Request + NEF->>UDR: 3. Storing / Updating / Removing the information + UDR->>V-PCF: 4. Nnef_ServiceParameter_Create / Update / Delete Response + V-PCF->>AMF: 5. Nudr_DM_Notify + AMF->>UE: 6. UE Policy delivery as specified in clause 4.2.4.3 + V-PCF-->>AF: 7. Npcf_EventExposure_Notify + AF-->>NEF: 8. Nnef_ServiceParameter_Notify + +``` + +Sequence diagram for AF guidance for URSP determination. The diagram shows interactions between UE, (R)AN, AMF, V-PCF, UDR, NEF, and AF. The process starts with UE registration and policy association. The AF sends a creation request to the NEF, which is stored in the UDR. The UDR then notifies the V-PCF, which in turn notifies the AMF. The AMF then handles UE policy delivery. Finally, the V-PCF sends an event exposure notification to the AF, and the AF sends a service parameter notification to the NEF. + +Figure 6.27.4-1: AF guidance for URSP determination + +This procedure takes the Service Parameter provisioning as specified in clause 4.16.12.2 of TS 23.502 [3] as a basis. The difference is that the AF checks the PLMNs that has an agreement with, then provide AF guidance to all these PLMNs, in this case the VPLMN where the UE is roaming. The AF sends the Service Parameter containing AF guidance on URSP Rule determination for any UE at the VPLMN. Then the HPLMN has set LBO roaming allowed flag for those users that are allowed to offload their application traffic to certain DNN, S-NSSAI used to access the AF. + +## 6.27.5 Impacts on Existing Nodes and Functionality + +The solution has impacts on the following entities: + +### V-PCF: + +- to store S-NSSAI subscription information from the HPLMN. +- to subscribe to notification from the V-UDR on Service Parameters. +- to generate URSP Rules with RSD components that contain VPLMN DNN, S-NSSAIs. +- to subscribe to DNN replacement for those UE Policy associations for UEs that has VPLMN provided URSP Rules. + +### H.PCF: + +- to provide S-NSSAI subscription information for a SUPI, per DNN and S-NSSAI that has LBO roaming allowed set. + +### UDR: + +- UE Policy subscription data includes the S-NSSAI subscription information includes the LBO roaming information, i.e. Indicates whether LBO roaming is allowed per DNN, or per (S-NSSAI, subscribed DNN). + +### UE: + +- Check PLMN ID in the list of PSIs, for those including the VPLMN ID the UE checks the validity of the RSD as for non-roaming case, i.e. the S-NSSAI is in the list of Allowed S-NSSAIs. + +## 6.28 Solution #28: Provisioning VPLMN URSP + +### 6.28.1 Description + +This solution is proposed to address technical issues for supporting URSP delivery in VPLMN have been identified in Key Issue #1 particularly on "How to provide URSP Rules in roaming to the UE. In particular, how the HPLMN and VPLMN are involved in such procedure". + +This solution identifies three scenarios from the perspective of which operator generate the URSP. For each scenario, how H-PCF and V-PCF behave is described as follows: + +#### Scenario A. HPLMN URSP Generation: + +- The H-PCF in HPLMN generates the URSP rules for the UE on VPLMN request. The V-PCF in VPLMN requests the H-PCF to generate URSP rules for VPLMN with appropriate parameters. +- When V-PCF requests H-PCF to generate URSP rules for VPLMN, the V-PCF use LBO information (DNN/S-NSSAI and SSC mode) received from UDM of the HPLMN via AMF to provide the parameters for H-PCF to generate the URSP rules. + +#### Scenario B. VPLMN URSP Generation with HPLMN permission: + +- In this scenario, the V-PCF generates the VPLMN URSP rules with HPLMN permission. +- When V-PCF generates the VPLMN URSP rules, the V-PCF uses the LBO information via AMF from UDM in HPLMN so that the V-PCF can derive the Route Selection Descriptors for URSP rules. V-PCF also use VPLMN precedence range provided by H-PCF to avoid the conflict URSP from PLMN and HPLMN. + +With this solution, the H-PCF can assign the precedence range that HPLMN provides to VPLMN during the establishing the UE policy association between V-PCF and H-PCF in order to avoid the conflict to avoid the conflict between the HPLMN generated URSP rules and VPLMN URSP rules. The V-PCF can map the pre-assigned precedence values to the HPLMN assigned precedence values. + +## 6.28.2 Procedures + +### 6.28.2.1 Provisioning VPLMN URSP rules for roaming scenario + +With this procedure, the solution provides three different scenarios for provisioning the VPLMN URSP rules to the UE. + +#### 1) HPLMN generation of URSP for VPLMN request. + +This solution supports the HPLMN generation of VPLMN URSP rules based on the V-PCF request as depicted in the Figure 6.28.2-1. During the UE registration, the UDM in HPLMN provides the LBO information along with HPLMN URSP Generation indication. The LBO information includes HPLMN's subscription information such as DNN/S-NSSAI and SSC mode to be used for generation of the Route Selection Components within the URSP rules. The AMF sends LBO information to the V-PCF so that V-PCF can request for HPLMN generation of the VPLMN URSP rules with the requested parameters. + +![Sequence diagram for HPLMN generation of URSP for VPLMN request. The diagram shows interactions between UE, AMF, V-PCF, UDM, and H-PCF across VPLMN and HPLMN domains. The sequence is: 1. UE to AMF: Request Request; 2. AMF to UDM: SDM Get Request; 3. UDM to AMF: SDM Get Response (DNN/S-NSSAI for LBO); 4. AMF to V-PCF: UEPolicyControlCreate Request (LBO Info); 5. V-PCF to H-PCF: UEPolicyControl_Create Request (The parameters for URSP rules); 6. H-PCF: Generation of VPLMN URSP in H-PCF; 7. H-PCF to V-PCF: UEPolicyControl_UpdateNotify (H-URSP, V-URSP); 8. V-PCF to AMF: N1N2MessageTransfer (V-URSP, H-URSP); 9. AMF to UE: UE Configuration Update (V-URSP, H-URSP).](4a5c6fefcac9340ea7f9df373873cae9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-PCF + participant UDM + participant H-PCF + + Note right of H-PCF: VPLMN | HPLMN + UE->>AMF: 1. Request Request + AMF->>UDM: 2. SDM Get Request + UDM-->>AMF: 3. SDM Get Response (DNN/S-NSSAI for LBO) + AMF->>V-PCF: 4. UEPolicyControlCreate Request (LBO Info) + V-PCF->>H-PCF: 5. UEPolicyControl_Create Request (The parameters for URSP rules) + Note right of H-PCF: 6. Generation of VPLMN URSP in H-PCF + H-PCF-->>V-PCF: 7. UEPolicyControl_UpdateNotify (H-URSP, V-URSP) + V-PCF->>AMF: 8. N1N2MessageTransfer (V-URSP, H-URSP) + AMF-->>UE: 9. UE Configuration Update (V-URSP, H-URSP) + +``` + +Sequence diagram for HPLMN generation of URSP for VPLMN request. The diagram shows interactions between UE, AMF, V-PCF, UDM, and H-PCF across VPLMN and HPLMN domains. The sequence is: 1. UE to AMF: Request Request; 2. AMF to UDM: SDM Get Request; 3. UDM to AMF: SDM Get Response (DNN/S-NSSAI for LBO); 4. AMF to V-PCF: UEPolicyControlCreate Request (LBO Info); 5. V-PCF to H-PCF: UEPolicyControl\_Create Request (The parameters for URSP rules); 6. H-PCF: Generation of VPLMN URSP in H-PCF; 7. H-PCF to V-PCF: UEPolicyControl\_UpdateNotify (H-URSP, V-URSP); 8. V-PCF to AMF: N1N2MessageTransfer (V-URSP, H-URSP); 9. AMF to UE: UE Configuration Update (V-URSP, H-URSP). + +**Figure 6.28.2.1-1: HPLMN generation of URSP for VPLMN request** + +H-PCF may authorize whether the parameters requested by the V-PCF by checking UDR. The H-PCF generates the VPLMN URSP in H-PCF with the authorized Route Selection Components. H-PCF takes the relative precedence values sent by V-PCF when generating the VPLMN URSP rules. + +#### 2) VPLMN generation of VPLMN URSP based on HPLMN permission. + +This solution supports the VPLMN generation of VPLMN URSP rules based on the HPLMN's permission as depicted in the Figure 6.28.2.1-2. During the UE registration, the UDM in HPLMN provides the VPLMN URSP generation allowed indication to the AMF in VPLMN. The UDM also sends the LBO information such as DNN/S-NSSAI and SSC mode to be used for the generation of the Route Selection Components within the URSP rules. The AMF sends LBO information to the V-PCF so that V-PCF can generate VPLMN URSP rules. + +![Sequence diagram showing the VPLMN generation of VPLMN URSP based on HPLMN permission. The diagram involves UE, AMF, V-PCF, UDM, and H-PCF. The process starts with a Request Request from UE to AMF. AMF sends an SDM Get Request to UDM, which responds with an SDM Get Response (DNN/S-NSSAI for LBO). AMF then sends a UEPolicyControl_Create Request (LBO Info) to V-PCF. V-PCF sends a UEPolicyControl_Create Request (VPLMN URSP generation) to H-PCF. H-PCF responds with a UEPolicyControl_Create Response (VPLMN precedence range). V-PCF then performs the generation of VPLMN URSP in V-PCF. Finally, AMF sends an N1N2MessageTransfer (V-URSP, H-URSP) to UE, and UE sends a UE Configuration Update (V-URSP, H-URSP) to AMF.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-PCF + participant UDM + participant H-PCF + + Note right of H-PCF: VPLMN | HPLMN + UE->>AMF: 1. Request Request + AMF->>UDM: 2. SDM Get Request + UDM-->>AMF: 3. SDM Get Response (DNN/S-NSSAI for LBO) + AMF->>V-PCF: 4. UEPolicyControl_Create Request (LBO Info) + V-PCF->>H-PCF: 5. UEPolicyControl_Create Request (VPLMN URSP generation) + H-PCF-->>V-PCF: 6. UEPolicyControl_Create Response (VPLMN precedence range) + Note left of V-PCF: 8. Generation of VPLMN URSP in V-PCF + V-PCF->>H-PCF: 7. UEPolicyControl_UpdateNotify (H-URSP) + AMF->>UE: 9. N1N2MessageTransfer (V-URSP, H-URSP) + UE-->>AMF: 10. UE Configuration Update (V-URSP, H-URSP) + +``` + +Sequence diagram showing the VPLMN generation of VPLMN URSP based on HPLMN permission. The diagram involves UE, AMF, V-PCF, UDM, and H-PCF. The process starts with a Request Request from UE to AMF. AMF sends an SDM Get Request to UDM, which responds with an SDM Get Response (DNN/S-NSSAI for LBO). AMF then sends a UEPolicyControl\_Create Request (LBO Info) to V-PCF. V-PCF sends a UEPolicyControl\_Create Request (VPLMN URSP generation) to H-PCF. H-PCF responds with a UEPolicyControl\_Create Response (VPLMN precedence range). V-PCF then performs the generation of VPLMN URSP in V-PCF. Finally, AMF sends an N1N2MessageTransfer (V-URSP, H-URSP) to UE, and UE sends a UE Configuration Update (V-URSP, H-URSP) to AMF. + +**Figure 6.28.2.1-2: VPLMN generation of VPLMN URSP based on HPLMN permission** + +To avoid the conflict between URSP rules from HPLMN and VPLMN, H-PCF provides the VPLMN precedence range to the V-PCF. The H-PCF assigns the range of the precedence of URSP rules for VPLMN URSP rules and provides the range to the V-PCF. The V-PCF maps the pre-defined VPLMN URSP's precedence values to the VPLMN range provided by the H-PCF. + +With an example is as in the Table 6.28.2.1-1, the H-PCF in HPLMN can assign the VPLMN precedence range to 5~6 for the V-PCF to use. HPLMN can use the high priority values precedence for the application in the HPLMN's URSP rules so that HPLMN can control those applications in high order. For example, HPLMN's rule#1 for the App#1 is higher priority than VPLMN's rule #6 for the same application. On the other hands, HPLMN can give more control for HPLMN rule #3, #4, #5 to VPLMN. VPLMN can take those precedence provided by HPLMN to use them for App#1 and abc.com. Rule #6 for App#1 is lower precedence of Rule#1 of HPLMN, however, Rule#7 for the abc.com of VPLMN can have higher priority than rule #4 of HPLMN. With this solution, HPLMN can take a control of URSP rules that they care and also give a flexibility for VPLMN to use those within the range. + +**Table 6.28.2.1-1: Example usage of URSP rule precedence** + +| PLMN | PSI | URSP Rule | Rule Precedence | Traffic Descriptor | Route Selection Descriptor | +|----------|-----|-----------|-----------------|---------------------|----------------------------| +| HPLMN ID | 1 | Rule #1 | 1 | App#1 | DNN#1, S-NSSAI#1 | +| | | Rule #2 | 2 | App#2 | DNN#1, S-NSSAI#2 | +| | | Rule #3 | 7 | IP 1.1.1.* | DNN#1, S-NSSAI#3 | +| | 2 | Rule #4 | 8 | Abc.com | DNN#1, S-NSSAI#4 | +| | | Rule #5 | 9 | Match-all | DNN#1, S-NSSAI#4 | +| VPLMN ID | 3 | Rule #6 | 5 | App#1, App#3, App#3 | DNN#1, S-NSSAI#5 | +| | 4 | Rule #7 | 6 | Abc.com | DNN#1, S-NSSAI#5 | + +How the H-PCF provides VPLMN precedence range to the V-PLMN is described in the step 6 and 7 of Figure 6.28.2.1-4: Procedure of provisioning VPLMN URSP rules for roaming scenario. + +The procedure of provisioning VPLMN URSP rules for roaming scenario is described in Figure 6.28.2.1-3. The procedure consolidates the all scenarios described in the description. + +![Sequence diagram showing the procedure of provisioning VPLMN URSP rules for roaming scenario. The diagram is split into Visited PLMN (left) and Home PLMN (right) by a dashed vertical line. Lifelines include UE, (R)AN, AMF, V-PCF, H-PCF, and UDM. The sequence starts with UE sending a Registration Request to AMF. AMF sends a Nudm_SDM_Get request to UDM. UDM responds with Nudm_SDM_Get response. AMF sends a Npcf_UEPolicyControl_Create Request to V-PCF. V-PCF sends a Npcf_UEPolicyControl_Create Request to H-PCF. H-PCF responds with Npcf_UEPolicyControl_Create Response. V-PCF responds with Npcf_UEPolicyControl_Create Response. AMF sends a Namf_Communication_N1N2MessageTransfer to (R)AN. (R)AN sends a Network Triggered Service Request to UE. UE sends a Delivery of UE policies to (R)AN. (R)AN sends a Result of the delivery of UE Policies to AMF. AMF sends a Namf_N1MessageNotify to V-PCF. V-PCF sends a Npcf_UEPolicyControl_Update Request to H-PCF. H-PCF responds with Npcf_UEPolicyControl_Update Response.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant VPCF as V-PCF + participant HPCF as H-PCF + participant UDM + + Note right of VPCF: Visited PLMN | Home PLMN + + UE->>AMF: 1. Registration Request + AMF->>UDM: 2. Nudm_SDM_Get request + UDM-->>AMF: 3. Nudm_SDM_Get response + AMF-->>UE: 4. Registration Accept + AMF->>VPCF: 5. Npcf_UEPolicyControl_Create Request + VPCF->>HPCF: 6. Npcf_UEPolicyControl_Create Request + HPCF-->>VPCF: 7. Npcf_UEPolicyControl_Create Response + VPCF-->>AMF: 8. Npcf_UEPolicyControl_Create Response + VPCF->>HPCF: 9. Npcf_UEPolicyControl_UpdateNotify Request + HPCF-->>VPCF: 10. Npcf_UEPolicyControl_UpdateNotify Response + AMF->>RAN: 11. Namf_Communication_N1N2MessageTransfer + Note left of RAN: + RAN-->>UE: 12. Network Triggered Service Request + UE-->>RAN: 13. Delivery of UE policies + RAN-->>AMF: 14. Result of the delivery of UE Policies + AMF->>VPCF: 15. Namf_N1MessageNotify + VPCF->>HPCF: 16. Npcf_UEPolicyControl_Update Request + HPCF-->>VPCF: 17. Npcf_UEPolicyControl_Update Response + +``` + +Sequence diagram showing the procedure of provisioning VPLMN URSP rules for roaming scenario. The diagram is split into Visited PLMN (left) and Home PLMN (right) by a dashed vertical line. Lifelines include UE, (R)AN, AMF, V-PCF, H-PCF, and UDM. The sequence starts with UE sending a Registration Request to AMF. AMF sends a Nudm\_SDM\_Get request to UDM. UDM responds with Nudm\_SDM\_Get response. AMF sends a Npcf\_UEPolicyControl\_Create Request to V-PCF. V-PCF sends a Npcf\_UEPolicyControl\_Create Request to H-PCF. H-PCF responds with Npcf\_UEPolicyControl\_Create Response. V-PCF responds with Npcf\_UEPolicyControl\_Create Response. AMF sends a Namf\_Communication\_N1N2MessageTransfer to (R)AN. (R)AN sends a Network Triggered Service Request to UE. UE sends a Delivery of UE policies to (R)AN. (R)AN sends a Result of the delivery of UE Policies to AMF. AMF sends a Namf\_N1MessageNotify to V-PCF. V-PCF sends a Npcf\_UEPolicyControl\_Update Request to H-PCF. H-PCF responds with Npcf\_UEPolicyControl\_Update Response. + +**Figure 6.28.2.1-3: Procedure of provisioning VPLMN URSP rules for roaming scenario** + +From step 1 to 4 describes the procedure for the UE to register the serving PLMN (i.e. VPLMN) in roaming scenario. + +1. During the registration procedure, the UE sends registration request to the AMF in VPLMN. The UE sends in the UE Policy Container the Policy Section Identifiers that are stored in the UE. +2. The AMF identifies the HPLMN of the UE with SUCI and requests the subscription information from UDM in HPLMN. +3. The UDM in HPLMN sends the URSP generation information such as HPLMN URSP Generation indication or VPLMN URSP Generation allowed indication to the AMF. The AMF also receives the LBO information that includes DNN/S-NSSAI and SSC mode from the UDM. + +**Table 6.28.2.1-2** + +| Subscription data type | Field | Description | +|-------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LBO Roaming Subscription data | LBO Roaming Allowed Parameters | This information includes SSC Mode, PDU Session Type, Access Mode Type, This information is used for V-PCF to check the Home subscription data if Visited URSP Generation Allowed indication is present. | +| | Visited URSP Generation Allowed | Indicates whether the V-PCF generates the URSP rules for VPLMN. The absence of this indication means that VPLMN is not allowed to generate URSP rules. | +| | HPLMN URSP Generation Required Indication | Indicates HPLMN can generate the URSP rules for VPLMN. If this indication is included, the V-PCF is allowed to request H-PCF to generate the URSP rules for VPLMN. | + +4. The AMF sends the Registration Accept to the UE. +5. The AMF sends the UEPolicyControl\_Create request to the V-PCF with the UE Policy Container received from the UE. The AMF sends HPLMN URSP Generation or VPLMN URSP Generation allowed indication along with the LBO information (e.g. DNN/S-NSSAI and SSC mode) the V-PCF either to request to HPLMN URSP generation or to generate VPLMN URSP rules by V-PCF itself. +6. The V-PCF either requests HPLMN to generate URSP for VPLMN or generates VPLMN URSP by itself based on the HPLMN URSP Generation or VPLMN URSP Generation allowed indication received from the AMF respectively. + +If HPLMN URSP Generation is indicated, the V-PCF sends the parameters to request H-PCF to generate URSP rules for VPLMN. The parameters includes the information for H-PCF to generate URSP rules for VPLMN such as traffic descriptor and Route Selection Descriptors. If there are multiple rules, the information also includes relative precedence values. + +If VPLMN URSP Generation allowed is indicated, the V-PCF sends the request for H-PCF to allow the V-PCF to generate URSP rules for VPLMN. It requests implicitly the precedence value ranges for the V-PCF to generate the URSP rules. + +After identifying the parameters, the V-PCF sends the Npcf\_UEPolicyControl\_Create request to the H-PCF. + +NOTE: In a scenario where no UE-PCF is deployed in HPLMN as depicted in Figure 6.28.2.1-3, the steps 6, 7, 8, 9, 11, 12, 18, 19 are not performed. + +If V-PCF requests H-PCF to generate URSP for VPLMN with its parameters, the H-PCF authorizes the requested parameters to be used as Route Selection Components of the URSP rules by checking the subscription information by accessing the UDR. + +If V-PCF requests H-PCF to allow the V-PCF to generate the VPLMN URSP, the H-PCF authorizes the request by checking the subscription information by accessing the UDR. + +7. The H-PCF sends the authorization result to the V-PCF by sending Npcf\_UEPolicyControl\_Create response. + +If H-PCF receives the VPLMN URSP generation request, the H-PCF also assigns the VPLMN precedence range and sends it to the V-PCF so that the V-PCF uses the VPLMN precedence range when generating URSP rules in order to avoid the conflict between the HPLMN generated URSP rules and VPLMN URSP rules. + +8. The V-PCF responds to the AMF with sending Npcf\_UEPolicyControl\_Create response. +9. If V-PCF requested HPLMN URSP generation for the VPLMN, the H-PCF generates both the URSP rules of HPLMN and URSP rules for VPLMN using the parameters provided by the V-PCF. If V-PCF requests to allow V-PCF to generate VPLMN URSP rules, the H-PCF generates only URSP rules of HPLMN. + +The H-PCF invokes the UEPolicyControl\_UpdateNotify to send the generated URSP rule to the V-PCF. + +10. The V-PCF acknowledges the UEPolicyControl\_UpdateNotify. +11. The V-PCF generates the VPLMN URSP rules by itself and sends both HPLMN URSP rules and VPLMN URSL rules to the AMF. When generating VPLMN URSP rules, V-PCF uses the LBO information (such as DNN/S-NSSAI and SSC mode) received from the AMF to derive Route Selection Descriptors. If the V-PCF receives the VPLMN precedence range from the H-PCF at the step 7, the V-PCF assigns the precedence values of VPLMN URSP rules within the received range. +- 12-14. The AMF sends the UE policy container to the UE using the UE configuration update procedure. +15. The AMF reports the UE policy delivery result to the V-PCF. +16. The V-PCF sends the Npcf\_UEPolicyControl\_UpdateNotify to the H-PCF to inform the UE policy delivery result. +17. The H-PCF acknowledges the Npcf\_UEPolicyControl\_UpdateNotify. + +## 6.28.2.2 Application Guidance of URSP determination in VPLMN + +With this procedure, the solution provides three different scenarios for AF in VPLMN to provide application guidance for URSP determination. Similar to clause 6.28.2.1, three different scenarios for VPLMN URSP generation are described. + +### 1) HPLMN generation of URSP for VPLMN request (Figure 6.28.2.2-1) + +When the AF requests the application guidance for URSP determination, NEF stores the service parameters in V-UDR. The V-UDR notify the V-PCF. Since the V-PCF has received LBO information from the AMF during the UE registration procedure as in step 5 of Figure 6.28.2.1-3, the V-PCF is aware of available home subscription values for the UE. The V-PCF sends the parameters to request the H-PCF to generate the URSP rules for VPLMN. The rest of steps are similar to the procedures of Figure 6.28.2.1-4. + +![Sequence diagram for HPLMN generation of URSP for VPLMN request. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, NEF, AF, and H-PCF across VPLMN and HPLMN domains. Steps include ServiceParameter, DM Store, DMNotify, UEPolicyControl_Update, Generation of VPLMN URSP in H-PCF, UEPolicyControl_UpdateNotify, and UE Policy Delivery.](4390b89fdb95cba102ee1f88e218b07b_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant V-UDR + participant V-PCF + participant AMF + participant UE + participant H-PCF + + Note right of AF: VPLMN + Note right of H-PCF: HPLMN + + AF->>NEF: 1. ServiceParameter + NEF->>V-UDR: 2. DM Store + V-UDR->>V-PCF: 3. DMNotify + V-PCF->>H-PCF: 4. UEPolicyControl_Update (The parameters for URSP rules) + Note right of H-PCF: 5. Generation of VPLMN URSP in H-PCF + H-PCF->>V-PCF: 6. UEPolicyControl_UpdateNotify (URSP rules) + V-PCF->>AMF: 7. UE Policy Delivery (URSP rules) + AMF->>UE: + +``` + +Sequence diagram for HPLMN generation of URSP for VPLMN request. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, NEF, AF, and H-PCF across VPLMN and HPLMN domains. Steps include ServiceParameter, DM Store, DMNotify, UEPolicyControl\_Update, Generation of VPLMN URSP in H-PCF, UEPolicyControl\_UpdateNotify, and UE Policy Delivery. + +Figure 6.28.2.2-1: HPLMN Generation of URSP for VPLMN request + +### 2) VPLMN generation of URSP rules (Figure 6.28.2.2-2) + +When the AF requests the application guidance for URSP determination, NEF stores the service parameters in V-UDR. The V-UDR notify the V-PCF. Since the V-PCF has received LBO information from the AMF during the UE registration procedure as in step 5 of Figure 6.28.2.1-4, the V-PCF is aware of available home subscription values for the UE. + +![Sequence diagram for VPLMN generation of URSP. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, NEF, and AF within the VPLMN domain. Steps include ServiceParameter, DM Store, DMNotify, Generation of VPLMN URSP in V-PCF, and UE Policy Delivery.](1593d118ca6d8c78c91eec7f2b8adf47_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant V-UDR + participant V-PCF + participant AMF + participant UE + + Note right of AF: VPLMN + + AF->>NEF: 1. ServiceParameter + NEF->>V-UDR: 2. DM Store + V-UDR->>V-PCF: 3. DMNotify + Note right of V-PCF: 4. Generation of VPLMN URSP in V-PCF + V-PCF->>AMF: 5. UE Policy Delivery (URSP rules) + AMF->>UE: + +``` + +Sequence diagram for VPLMN generation of URSP. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, NEF, and AF within the VPLMN domain. Steps include ServiceParameter, DM Store, DMNotify, Generation of VPLMN URSP in V-PCF, and UE Policy Delivery. + +Figure 6.28.2.2-2: VPLMN Generation of URSP + +The procedure of application guidance for URSP determination in VPLMN for roaming scenario is described in Figure 6.28.2.2-4. The procedure consolidates the all three scenarios described above. + +![Sequence diagram illustrating the procedure of application guidance for URSP determination in VPLMN. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, NEF, AF, and H-PCF across Visited PLMN and Home PLMN boundaries.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-PCF + participant V-UDR + participant NEF + participant AF + participant H-PCF + + Note right of AF: Visited PLMN + Note right of H-PCF: Home PLMN + + UE->>AMF: UE registration + AMF->>V-PCF: 0a. UE Policy Association + V-PCF->>V-UDR: 0b. Nudr_Subscribe + AF->>AF: 1. Creation of the AF request + AF->>NEF: 2. Nnef_ServiceParameter_Create Update / Delete Request + NEF->>V-UDR: 3. Storing / Updating / Removing the information + NEF->>AF: 4. Nnef_ServiceParameter_Create Update / Delete Response + V-UDR->>V-PCF: 5. Nudr_DM_Notify + V-PCF->>H-PCF: 6. Npcf_UEPolicyControl_Update Request + H-PCF-->>V-PCF: 7. Npcf_UEPolicyControl_Update Response + V-PCF->>H-PCF: 8. Npcf_UEPolicyControl_UpdateNotify Request + H-PCF-->>V-PCF: 9. Npcf_UEPolicyControl_UpdateNotify Response + Note left of V-PCF: 10. UE Policy delivery procedure + V-PCF->>H-PCF: 11. Npcf_UEPolicyControl_Update Request + H-PCF-->>V-PCF: 12. Npcf_UEPolicyControl_Update Response + V-PCF->>NEF: 13. Npcf_EventExposure_Notify + NEF->>AF: 14. Nnef_ServiceParameter_Notify + +``` + +Sequence diagram illustrating the procedure of application guidance for URSP determination in VPLMN. The diagram shows interactions between UE, AMF, V-PCF, V-UDR, NEF, AF, and H-PCF across Visited PLMN and Home PLMN boundaries. + +**Figure 6.28.2.2-4: Procedure of application guidance for URSP determination in VPLMN** + +0. UE performs the registration procedure with the AMF in VPLMN. The AMF retrieves HPLMN URSP Generation indication or VPLMN URSP Generation allowed indication and the LBO information in UDM and provides them to the V-PCF during creation of UE Policy Association. +1. The AF in VPLMN creates an AF request for application guidance for URSP determination in VPLMN +2. The AF sends the AF request to the NEF. +3. The NEF stores the service parameters to the UDR in VPLMN. +4. NEF acknowledges the AF request. The parameters of AF request is checked in the step 6. +5. The V-UDR notifies V-PCF of DM information. +6. Based on the HPLMN URSP Generation indication or VPLMN URSP Generation allowed indication received from the AMF when creating the UE Policy association, the V-PCF either requests HPLMN to generate URSP for VPLMN or generates VPLMN URSP by sending Npcf\_UEPolicyControl\_Create to the H-PCF. + +If the VPLMN URSP Generation is allowed, the V-PCF checks the parameters of AF request to URSP rules with LBO roaming subscription data received from the UDM. + +If HPLMN URSP Generation is indicated, the V-PCF sends the parameters to request H-PCF to generate URSP rules for VPLMN. The parameters includes the information for H-PCF to generate URSP rules for VPLMN such as traffic descriptor and Route Selection Descriptors. If there are multiple rules, the information also includes relative precedence values. + +NOTE: For the scenarios as depicted in Figure 6.28.2.2-2, the steps 6, 7, 8, 9, 11, 12, 18, 19 are not performed. + +7. H-PCF sends the response to the V-PCF. +- 8-12. The steps are the same as the step 11 to step 19 of the Figure 6.28.2.1-4. +13. The V-PCF notifies the outcome of UE policy delivery result to the NEF. +14. The NEF notifies the outcome of UE policy delivery result to the AF. + +## 6.28.3 Impacts on services, entities and interfaces + +AMF: + +- The AMF is required to support HPLMN URSP Generation and VPLMN URSP Generation indication and forward LBO information (e.g. DNN/S-NSSAI and SSC mode) to the V-PCF. + +V-PCF: + +- The V-PCF is required to provide the parameters for H-PCF to generate URSP, generate VPLMN URSP triggered by UE registration and support the AF request for application guidance of URSP determination in VPLMN. + +H-PCF: + +- The H-PCF is required to support the generation of URSP for VPLMN request. The H-PCF is required to assign the VPLMN precedence range if the V-PCF requests VPLMN generation of URSP rules. + +UDM: + +- The UDM is required to provide the HPLMN URSP generation indication or VPLMN URSP generation allowed indication. + +## 6.29 Solution #29: Using Location Criteria to Control Routing of Application Traffic + +### 6.29.1 Description + +This solution addresses the following aspect of Key Issue #1: + +- Whether and how to support URSP enhancements to support routing of the application traffic with different URSP rules in different PLMNs. + +Other Key Issue #1 solutions in this TR explain what might trigger the PCF to send URSP rules to the UE. This solution does not address this aspect of Key Issue #1. Rather, this solution proposes how to use Location Criteria to support routing of the application traffic with different URSP rules in different PLMNs. In this solution the RSDs can be VPLMN dependent and can be sent to the UE by the HPLMN before the UE registers to the VPLMN. An indication in the RSD is used by the UE to help detect when URSP re-evaluation should be considered. In other words, this solution does not require that new URSP Rules be sent to the UE each time the UE registers in a different PLMN. + +The principles of this solution are: + +- In Rel-17, a URSP rule can already be configured with Location Criteria that indicates to the UE that the route (i.e. PDU Session) should only be established, or used, when the UE served by certain cell(s), RAN node(s), or TAIs. This feature can be used to cause the UE to select a DNN/S-NSSAI combination that is appropriate for the PLMN where the UE is registered (e.g. an LBO Session). Location criteria is defined in TS 24.526 [10] and may be a list of cell(s), RAN node(s), or TAI(s). This solution proposes that Location Criteria can also include PLMN ID(s). + +NOTE 1: Whether PLMN ID(s) can be encoded as part of Location Criteria or encoded as a new validation criteria information element is left to stage 3. + +- When a route includes Location Criteria, a "Revaluation Suggested" indication can be added to the RSD. A "Revaluation Suggested" indication in the RSD indicates to the UE that the UE should re-evaluate URSP rules for traffic that uses the PDU Session if the Location Criteria becomes invalid and release the PDU Session if no traffic is using the PDU Session after re-evaluation. In other words, the PDU Session may be released when the UE leaves the PLMN, cell(s), RAN node(s), or TAI(s) where the location criteria is valid and all traffic is moved to a different PDU Session (e.g. an LBO PDU Session). + +Triggering re-evaluation will cause the UE to select a new route. The new route may include location criteria for the UE's new location and a PDU Session will be established with a DNN/S-NSSAI combination that is better suited for the UE's new location (e.g. for the PLMN where the UE is now registered). + +NOTE 2: It is a UE implementation decision when to re-evaluate URSP Rules. The indication is used to by the UE to help determine if it should re-evaluate. + +## 6.29.2 Procedures + +The UE receives URSP rules. Some URSP rules may have Traffic Descriptors that are associated with traffic that should preferably use a certain DNN/S-NSSAI combination when the UE is in a certain PLMN. The RSDs of these URSP rules may include Location Criteria. By including Location Criteria, the URSP rule can be configured such that the UE will select a DNN/S-NSSAI combination for PDU Session Establishment based on the UE's cell, RAN Node, TAI or PLMN ID. Thus, the UE will use a DNN/S-NSSAI combination based on the PLMN that the UE is registered with. For example, the route will only be considered valid if the PLMN ID in the Location Criteria matches the PLMN ID of the PLMN where the UE is currently registered or if the PLMN ID in the Location Criteria is an equivalent PLMN of the PLMN where the UE is currently registered. + +Existing Rel-17 behaviour is that when the UE leaves the cell, RAN Node, or tracking area, the UE will continue to use the PDU Session until URSP Rules are re-evaluated. However, the UE is not required to re-evaluate URSP rules for the traffic. + +This solution proposes that the RSD(s) also include a "Revaluation Suggested" indication. When a change of cell, RAN node, TAI, or PLMN occurs, the existing PDU Session will be released if no longer needed and the UE will re-evaluate URSP rules. URSP re-evaluation will cause the UE to choose a new RSD for the traffic. The location criteria in the new RSD will cause the UE to select a DNN/S-NSSAI that is associated with the PLMN where the UE is currently registered. + +## 6.29.3 Impacts on services, entities and interfaces + +PCF: + +- can include the "Revaluation Suggested" indication with location criteria in RSDs; +- can include a PLMN ID(s) in location criteria. + +UE: + +- can receive the "Revaluation Suggested" indication with location criteria in RSDs; +- can use the "Revaluation Suggested" indication to decide when to trigger URSP Re-evaluation; +- can receive a PLMN ID(s) in location criteria. + +## 6.30 Solution #30: Leveraging NWDAF to determine UEs that enforce URSP rules incorrectly. + +### 6.30.1 Description + +This solution is related with KI#6 of the eNA study and also KI#2 of FS\_eUEPO on how the 5GC can be aware that the UE enforces a URSP rules correctly. + +The solution proposes to leverage the NWDAF to identify cases where a UE routes traffic to a PDU session (of a specific S-NSSAI/DNN) that is not according to the routing policies configured to the UE based on a provisioned URSP rule. + +The consumer ( i.e.) PCF is aware of the correct application traffic that needs to be routed over a specific S-NSSAI/DNN by inspecting the URSP rule that needs to be determined if it is enforced correctly by UEs. The Traffic Descriptor of the URSP rule will identify the application traffic and the Route Selection Descriptor component will denote the correct S-NSSAI/DNN to route the application traffic. + +The PCF determines to request analytics to identify if UEs enforce URSP rules correctly to a PDU session of a specific S-NSSAI/DNN based on local configuration. + +The request to the NWDAF to provide analytics to detect UEs that do not enforce URSP correctly include the following: + +- An analytic ID denoting a request for URSP enforcement analytics. +- Analytic Filters: + - The S-NSSAI/DNN of the PDU session established by a UE. + - The Allowed application traffic towards the PDU session according to the URSP rule. Allowed application traffic may include the Traffic Descriptor of the URSP rule (e.g. Application ID, FQDN) or may include allowed service data flows (i.e. the PCF may determine the allowed service data flows based on the Traffic Descriptor). + - Area of interest. + - Any UE or list of UEs. + +The NWDAF subscribes to the UPF using a new Nupf event based subscription to report "non-matching traffic" for a PDU session established to a specific S-NSSAI/DNN. The Nupf\_EventExposure\_Subscribe requests includes the following: + +- A new event ID: e.g. "Non-matching traffic"; +- Traffic Filters indicating the allowed traffic. This can be a 5-tuple or an application id; +- S-NSSAI or DNN of the PDU session to be inspected; +- Target of Event Reporting (e.g. a single UE, a group of UE or any UE); +- Notification Target Address (+ Notification Correlation ID); and +- Event Reporting Information defined in Table 4.15.1-1 of TS 23.502 [3]. + +The NWDAF determines the UPF that support the requested S-NSSAI/DNN either by interfacing with the NRF or the UDM (if the request includes a list of UE(s)). + +When the UPF detect non-matching traffic the UPF reports to the NWDAF, traffic filters indicating the traffic detected and a UE identifier (UE ID or UE IP address) of the UE that routed non-matching traffic to a PDU session established to a specific S-NSSAI/DNN. + +NOTE 1: The UPF can use the usage reporting capabilities as described in clause 5.4.6 of TS 29.244 [14] to determine and report non-matching traffic. + +NOTE 2: It is assumed that the UPF has received S-NSSAI/DNN information from the SMF when the SMF establishes an N4 session for a requested PDU session. + +NOTE 3: To control the signalling load of the UPF the UPF can be configured to report usage periodically to the NWDAF by re-using the event reporting information defined in Table 4.15.1-1 of TS 23.502 [3]. + +Based on the information collected the NWDAF reports to the PCF a list of UEs that route traffic incorrectly and application traffic that is routed incorrectly over the S-NSSAI/DNN. The PCF uses the information to determine if such UEs require updated URSP rules (e.g. route specific application traffic over a default DNN) (if the consumer is the UE PCF) or block traffic by providing updated PCC rules for the established PDU session (if the consumer is the SM PCF). + +## 6.30.2 Input Data + +The following input data are required by the NWDAF to identify UEs that enforce URSP rules incorrectly. + +**Table 6.30.2-1: Input data for URSP enforcement analytics** + +| Information | Source | Description | +|----------------------|-------------|--------------------------------------------------------------------------------------------------| +| S-NSSAI | UPF<br>/SMF | The S-NSSAI that the UE has established a PDU session | +| DNN | UPF<br>/SMF | The DNN that the UE has established a PDU session | +| UE ID | UPF<br>/SMF | The identity of the UE that has established a PDU session to a specific S-NSSAI/DNN | +| non-matching traffic | UPF | The traffic detected that is not matched against the allowed traffic over a specific S-NSSAI/DNN | + +## 6.30.3 Output Analytics + +The NWDAF only provides to the PCF statistics on UEs that do not enforce URSP correctly as shown in the table below. For this scenario the NWDAF does not provide any predictions. + +**Table 6.30.3-1: "URSP enforcement" statistics** + +| Information | Description | +|---------------------------------------------|-----------------------------------------------------------------------------------| +| List of URSP enforcement Analytics (1..max) | | +| > Non-matching traffic | The traffic detected that is not matched against the allowed traffic | +| >Applicable DNN | The DNN that the UE has established a PDU session | +| >Applicable S-NSSAI | The S-NSSAI that the UE has established a PDU session | +| > List of SUPIs | A list of UE that route the same non-matching traffic over a specific S-NSSAI/DNN | + +## 6.30.4 Procedures + +The procedure is shown in the figure below. + +![Sequence diagram illustrating the NWDAF providing analytics for URSP rules enforcement. The diagram shows interactions between UE, PCF, NWDAF, SMF, and UPF. The PCF determines a URSP rule and requests analytics from the NWDAF. The NWDAF determines a UPF and subscribes to events from the SMF. The UE establishes a PDU session, and the SMF selects a UPF. The UPF reports non-matching traffic to the SMF, which then reports to the NWDAF. The NWDAF determines if the UE is misbehaving and reports it to the PCF, which may construct a URSP rule.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCF + participant NWDAF + participant SMF + participant UPF + + Note right of PCF: 1. Determines to identify enforcement of a URSP rule. + PCF->>NWDAF: 2. Request Analytics for URSP enforcement (Analytic Filters: Allowed Traffic (based on URSP rule), Area of interest S-NSSAI, DNN, Any UE or list of UEs) + Note right of NWDAF: 3. Determines UPF + NWDAF->>SMF: 4. Nupf_EventExposure_Subscribe (Event ID, Event Filters, Allowed Traffic, S-NSSAI/DNN, List of UE ID or UE IP address(es)) + Note left of UE: 5. UE determines to establish a PDU session due to matched URSP rule + Note right of SMF: 6. UE requests a PDU session to the SMF as per 3GPP TS 23.502. The SMF selects a UPF for the PDU session as per 3GPP TS 23.502. + Note right of SMF: UE Application Traffic + Note right of UPF: UE Application Traffic + Note right of SMF: 7. Nupf_EventExposure_Notify (reports non-matching traffic, data used, serving SMF, UE IP address or UE ID*) + Note right of NWDAF: 8. Determines UE that do not enforce URSP rules correctly + Note right of NWDAF: 9. Reports misbehaving UE (UE ID, non-matching traffic) + Note right of PCF: 10. May construct URSP rule to indicate the UE to route this traffic via a default DNN + +``` + +Sequence diagram illustrating the NWDAF providing analytics for URSP rules enforcement. The diagram shows interactions between UE, PCF, NWDAF, SMF, and UPF. The PCF determines a URSP rule and requests analytics from the NWDAF. The NWDAF determines a UPF and subscribes to events from the SMF. The UE establishes a PDU session, and the SMF selects a UPF. The UPF reports non-matching traffic to the SMF, which then reports to the NWDAF. The NWDAF determines if the UE is misbehaving and reports it to the PCF, which may construct a URSP rule. + +**Figure 6.30.4-1: NWDAF providing analytics for URSP rules enforcement** + +The procedure is as follows: + +1. The consumer (i.e. PCF) needs to identify if a URSP rule is enforced correctly by UEs. The PCF is locally configured to determine which URSP rule needs to be checked if enforced correctly by UEs. +2. The consumer request analytics for URSP enforcement by the NWDAF. The consumer includes a specific Analytic ID (that is associated to the URSP enforcement analytics) and includes as analytics filters the following information: + - An analytic ID denoting a request for URSP enforcement analytics. + - Analytic Filters: + - The S-NSSAI/DNN of the PDU session established by a UE. + - The Allowed application traffic towards the PDU session according to the URSP rule. Allowed application traffic may include the Traffic Descriptor of the URSP rule (e.g. Application ID, FQDN) or may include allowed service data flows (i.e. the consumer may determine the allowed service data flows based on the Traffic Descriptor). + - Area of interest. + - Any UE or list of UEs. +- 3. + +**If the request includes Any UE:** + +- The NWDAF subscribes from all SMFs supporting the S-NSSAI/DNN requested, to be notified when a UE establishes a PDU session to the S-NSSAI/DNN requested in step 2. The SMF provides the UE ID and UE IP address to the NWDAF. + +#### **If the request includes a list of UEs** + +- The NWDAF finds the UPF serving the UE for the requested S-NSSAI/DNN by querying the UDM to identify SMF serving UE for the S-NSSAI/DNN and then querying the SMF to identify the UPF serving the UE. + - Alternatively the NWDAF may query the UDM to find the UPF serving the UE for an S-NSSAI/DNN +4. The NWDAF subscribes from the UPF to report non-matching traffic. The NWDAF subscribes to the UPF using a new Nupf event based subscription to report "non-matching traffic" for a PDU session established to a specific S-NSSAI/DNN. The Nupf\_EventExposure\_Subscribe requests includes the following: + - A new event ID: e.g. "Non-matching traffic"; + - Traffic Filters indicating the allowed traffic. This can be a 5-tuple or an application id; + - S-NSSAI or DNN of the PDU session to be inspected; + - Target of Event Reporting (e.g. a single UE, a group of UE or any UE); + - Notification Target Address (+ Notification Correlation ID); and + - Event Reporting Information defined in Table 4.15.1-1 of TS 23.502 [3]. + 5. A UE determines to request a PDU session based on application traffic matching a URSP rule. + 6. The UE requests establishment of a PDU session to the SMF according to TS 23.502 [3]. + 7. When the UPF receives traffic (either in downlink or uplink) for a UE the UPF reports non-matching traffic and includes the service data flows of the traffic detected. + 8. The NWDAF compiles a list of UEs where application traffic is sent to the wrong S-NSSAI/DNN. + 9. The NWDAF provides a list of UE IDs and a list of non-matching traffic that is wrongly sent to this S-NSSAI/DNN. + 10. The PCF may construct a new URSP rule to route traffic detected via a different S-NSSAI/DNN, e.g. via a default DNN. + +### **6.30.5 Impacts on services, entities and interfaces** + +**Editor's note:** This clause captures impacts on existing 3GPP nodes and functional elements. + +- NWDAF supporting new analytic id to identify UEs that do not enforce URSP rule correctly. +- UPF reporting to NWDAF application traffic that is not matched against allowed traffic to a specific S-NSSAI/DNN. + +## **6.31 Solution #31: New URSP Notification Component** + +### **6.31.1 Description** + +This solution describes an extension to the Route Selection Descriptors listed in clause 6.6.2 of TS 23.503 [4] with a new category: URSP Notification component. The solution allows the 5GC to be made aware of whether a URSP rule is enforced and considers as well user privacy by allowing the UE/user to reject URSP rules with a notification component and notify the 5GC of the rejection. + +Examples are provided in clause 6.31.2.4 of how this solution can enable action from the 5GS to be taken after the 5GC is aware whether the UE enforces a URSP rule for specific application traffic or not. However, the focus of the solution is on making the 5GC aware of URSP rule enforcement. + +A URSP Notification component instructs the URSP rule to, under certain trigger conditions, generate a notification towards the core network. If the component is not included in the URSP rule, it is not required by the network to generate notifications towards the core network (i.e. URSP functionality as it is now). + +Similarly to how SBI notifications contain a subscription identifier, URSP Notification component contain an identifier, which is included in notifications and are used by the core network to map the notification to a URSP rule and trigger. + +In order not to overload existing identifiers (e.g. PSI, precedence), the identifier introduced in this solution is coupled to the notification component. This also allows that more than one notification trigger can be linked to a given URSP rule. + +The table below, based on Table 6.6.2.1-3 of TS 23.503 [4] includes the current Route Selection Descriptor and the new URSP Rule Notification Descriptor. Existing URSP descriptors are shown greyed-out, new URSP Notification Component highlighted. + +| Information name | Description | Category | +|---------------------------------------|----------------------------------------------------------------------------------|-----------| +| Route Selection Descriptor Precedence | Determines the order in which the Route Selection Descriptors are to be applied. | Mandatory | +| Route selection components | At least one of the route selection components | Mandatory | +| Route Selection Validation Criteria | Optional Route Validation Criteria components | Optional | +| [NEW] URSP Notification Component | Optional Route Selection Notification Component(s) | Optional | + +The URSP Notification Component indicates the UE that, under certain conditions, the UE is to notify the PCF. URSP Notifications are sent towards the PCF responsible for the UE indirectly via the AMF via a UL NAS TRANSPORT message carrying a UE Policy Container (URSP Notification) to the AMF. The UL NAS TRANSPORT mechanism used to reach the PCF uses the same mechanics as the Procedure for UE triggered ProSe Policy provisioning described in clause 6.2.4 of TS 23.304 [12]. + +NOTE 1: URSP Notification component(s) are not used with match-all rules. + +The AMF at the receiving end maps the PCF responsible for the UE and forwards the Notification towards the PCF. The PCF at the receiving end will be able to map the generating UE, URSP rule and trigger based on the URSP Notification Component ID without the information having to be explicitly signalled. + +So that the 5GC can be made aware whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on the URSP rule provisioned by 5GC, the following trigger conditions are considered as part of a URSP Notification Component: + +- First use of the URSP rule. +- Data sent over given period of time (i.e. periodic reporting). +- If a certain amount of data has been sent over a specific period of time (i.e. Bandwidth threshold). + +Examples of possible applications of the above-mentioned triggers would be (a) first activation of a service, (b) the network ascertaining if the URSP rule is still in use (i.e. a sort of "service Up/Down" indicator) or (c) for some services (e.g. video) a bandwidth threshold could be setup so that signalling (e.g. HTTP requests to the web itself, not the video) do not trigger a "used" indication, but rather only if a bandwidth-intensive usage is seen. + +Note that the 5GC specifies how to detect the data sent and received over a given period, using usage monitoring reporting and can provide bandwidth parameters to limit the amount of data sent over a period, using the QoS framework defined in 23.501, and the MBR parameter. + +For the use of the URSP Rule, this is a solution while other solutions exist to this KI#2 that enables detection of the URSP Rule in use (first or subsequent use) either at the SMF or PCF. + +User privacy is considered by allowing the UE to reject URSP policies including notifications based on UE security policies. However, if a UE accepts a URSP rule, it is expected to apply it fully, including URSP Notification Component(s). + +Procedures are shown for the following cases: + +- URSP rule delivery, URSP Notification sent to 5GC. +- Detail of UE policy delivery and user content. +- Applicability to (pre-)configured URSP rules and changes in privacy settings. + +NOTE 2: How the preconfigured URSP Rules are used and for what purpose is detailed in clause 6.31.2.3. + +## 6.31.2 Procedures + +A call flow of the procedure is shown below. + +### 6.31.2.1 URSP Notification procedure flow + +![Sequence diagram illustrating the URSP Notification procedure flow between UE, AMF, and PCF (AM/UE).](3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF as PCF (AM/UE) + + Note right of AMF: 1. UE Policy Association Establishment as per TS 23.502 [3], clause 4.16.11 + AMF->>PCF: + Note right of PCF: 2. Delivery of URSP rule(s) including Route Selection Notification Component(s) via UE Configuration Update + PCF->>UE: + Note left of UE: 3. Trigger for URSP Notification A set + UE->>AMF: 4. UL NAS TRANSPORT (URSP Notification) + AMF->>PCF: 5. Namf_Communication_N1MessageNotify + Note right of PCF: 6. Map URSP Notification Component ID to UE, URSP rule, trigger + +``` + +Sequence diagram illustrating the URSP Notification procedure flow between UE, AMF, and PCF (AM/UE). + +Figure 6.31.2.1-1: URSP Notification procedure flow + +- As part of the UE policy association establishment, as per TS 23.502 [3], clause 4.16.11, the PCF is assumed to register to the BSF as the PCF serving this UE. The PCF is subscribed to be notified of the reception of the UE Policy container then the AMF forwards the response of the UE to the PCF using Namf\_Communication\_N1MessageNotify. + +NOTE 1: According to clause 6.3.7.1 of TS 23.501 [2], the same PCF instance is assumed for AM policy association and UE policy association. + +- UE Policies are delivered to the UE using the current, existing mechanism of UE Configuration Update procedure for transparent UE Policy delivery, see clause 4.2.4.3 of TS 23.502 [3]. URSP Rule(s) contain one or more Route Selection Notification Components. The UE can, based on local security/privacy settings, reject URSP rules containing URSP notification component(s). Each Route Selection Notification Components contains: + - Identifier: Similarly to how a SBI subscription has a subscription identifier, a Notification component contains an identifier to be included in subsequent notifications. The identifier is used by the PCF to map the notification to a UE, URSP rule and trigger. + - Trigger condition: Following trigger conditions are considered: + - First use of the URSP rule. + +- Data sent over given period of time (i.e. periodic reporting). +- If a certain amount of data has been sent over a specific period of time (i.e. Bandwidth threshold). + +NOTE 2: Details of the UE policy delivery including privacy-related aspects and user consent are detailed in the next call flow in clause 6.31.2.1. + +3. Trigger condition for a notification (Notification Component A) is set +4. The UE sends the URSP notification via a UL NAS TRANSPORT message. The included UE Policy Container is of type URSP Notification and contains: + - Identifier of Notification Component A. + - Notification information (depending on trigger condition). +5. The AMF sends Namf\_Communication\_N1MessageNotify request to the PCF including the UE Policy Container received from UE as described in step 2 of clause 6.2.4 of TS 23.304 [12]. +6. The PCF uses the URSP Notification Component ID to map the incoming notification information to a UE, URSP rule (if the URSP rule is known) and trigger condition. + +### 6.31.2.2 Detail of UE policy delivery and user consent + +This call flow depicts an expanded view of step 2. The flow is based on clause 4.2.4.3 of TS 23.502 [3]. + +![Sequence diagram illustrating the UE Configuration Update procedure for transparent UE Policy delivery including URSP Notification component and privacy aspects. The diagram shows interactions between User, UE, (R)AN, AMF, and PCF. The process starts with the PCF deciding to update the UE Policy (step 0). The PCF sends a Namf_Communication_N1N2MessageTransfer to the AMF (step 1). The AMF sends a Network Triggered Service Request to the UE (step 2). The UE delivers the UE policies to the AMF (step 3). The UE applies the URSP security/privacy policy (step 4). The UE sends the result of the delivery of UE policies to the AMF (step 5). The AMF sends a Namf_Communication_N1MessageNotify to the PCF (step 6).](23d9fcc2863a6b0548d6b4e8abf15106_img.jpg) + +``` + +sequenceDiagram + participant User + participant UE + participant RAN as (R)AN + participant AMF + participant PCF + Note right of PCF: 0. PCF decides to update UE Policy + PCF-->>AMF: 1. Namf_Communication_N1N2MessageTransfer + Note over UE, RAN: 2. Network Triggered Service Request + UE->>AMF: 3. Delivery of UE policies + Note over User, UE: 4. UE applies URSP security/privacy policy + UE->>AMF: 5. Result of the delivery of UE policies + AMF-->>PCF: 6. Namf_Communication_N1MessageNotify + +``` + +Sequence diagram illustrating the UE Configuration Update procedure for transparent UE Policy delivery including URSP Notification component and privacy aspects. The diagram shows interactions between User, UE, (R)AN, AMF, and PCF. The process starts with the PCF deciding to update the UE Policy (step 0). The PCF sends a Namf\_Communication\_N1N2MessageTransfer to the AMF (step 1). The AMF sends a Network Triggered Service Request to the UE (step 2). The UE delivers the UE policies to the AMF (step 3). The UE applies the URSP security/privacy policy (step 4). The UE sends the result of the delivery of UE policies to the AMF (step 5). The AMF sends a Namf\_Communication\_N1MessageNotify to the PCF (step 6). + +**Figure 6.31.2.2-1: UE Configuration Update procedure for transparent UE Policy delivery including URSP Notification component and privacy aspects** + +- 0-2. Same as in clause 4.2.4.3 of TS 23.502 [3]. +3. Delivery of the UE policy content described in clause 6.31.2.1, step 2. The UE policy content is delivered as for step 3 in clause 4.2.4.3 of TS 23.502 [3]. +4. For URSP rules containing a URSP Notification component, the UE can be configured to allow said reporting. Examples of security/privacy configuration: + - User is to be prompted whether a given URSP rule including a notification component should be allowed when the URSP rule is received. + - Certain applications are allowed to use URSP notification components (e.g. UE configuration, configured by user). + +If the Notification component is not allowed, the URSP rule is rejected and not stored in the UE. + +NOTE 1: If the URSP rule is rejected, as a result, certain traffic will not be able to use enhanced functionality. Thus, the user has the option to allow enhanced routing for certain application with the knowledge that traffic reports may be sent or disallow such reporting and use other routing (e.g. default slice/PDU session). + +5. Same as step 4 in clause 4.2.4.3 of TS 23.502 [3], with the addition that in case the URSP rule was rejected due to one or more URSP Notification component(s) not being allowed. The UE includes this information in the result. + +NOTE 2: For the case when an already-accepted URSP rule is rejected after being accepted (e.g. privacy/security settings were changed), see clause 6.31.2.3. + +6. Same as step 5 in clause 4.2.4.3 of TS 23.502 [3]. + +If a URSP rule is rejected by the UE, the PCF can use the returned URSP rejection reason to produce an alternative set of URSP rule(s). The logic how the PCF can produce an alternative set of URSP rule(s) or whether no alternative URSP rule is produced is not in scope of this solution. + +### 6.31.2.3 URSP Rule rejection for pre-configured URSP rules or already-accepted URSP rules (e.g. change in privacy/security settings) + +Pre-configured URSP rules are covered by the current specification. As stated in TS 23.503 [4], clause 6.1.2.2, "*ANDSP and URSP may be pre-configured in the UE or may be provisioned to UE from PCF*". + +If the solution does not consider user privacy for the case of pre-configured URSP rules (e.g. a UE pre-configured for use of a certain slice), it would be possible by design to circumvent the functionality in clause 6.31.2.2 simply by means of pre-configuring URSP rules. Pre-configuration of URSP rules would either result in the UE not having a chance of rejecting the URSP rule (the rejection mechanism described in clause 6.31.2.2 is based on "Result of the delivery of UE policies") or the UE not applying the given URSP rule while the network is not aware that the URSP rule has been rejected. + +While it is possible that a pre-configured URSP rule is not known to the PCF, it is assumed that it, as well as any associated URSP notification identifier, is known to the operator. As such, this solution does not propose that the UE-PCF performs any action based on this (not known) URSP rule besides forwarding it to a 3rd party (e.g. see clause 6.31.2.4.2). + +Additionally, a similar case occurs if, after the UE accepted a URSP rule (see clause 6.31.2.2), UE configuration is changed (e.g. if security/privacy settings are changed so that a given URSP rule should now be rejected by the UE). + +For pre-configured URSP rules or already-accepted URSP rules, there is no possibility for the UE to respond with a "Result of the delivery of UE policies". In this case, the UE's URSP security/privacy policy is configured with a URSP rule to be used for rejected URSP rules (e.g. the default URSP rule). The UE notifies the PCF via UL NAS TRANSPORT: + +- Identifier of Notification Component. +- Notification information indicating that the pre-configured URSP rule does not conform to the security/privacy policy and as such it is rejected. + +![Sequence diagram illustrating URSP rule rejection for existing URSP rules. The diagram shows interactions between UE, AMF, and PCF (AM/UE).](a5404b7275b06497eecf9b5883604753_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant PCF as PCF (AM/UE) + + Note left of UE: 0. URSP rule A present in UE (e.g. pre-configured or signaled by PCF). Includes URSP Notification X component. Security/privacy setting do not allow URSP Notification X. + Note left of UE: 1. URSP rule A match for traffic. UE does not apply URSP rule A + UE->>AMF: 2. UL NAS TRANSPORT (URSP Rule A Rejected, Notification X not allowed) + AMF->>PCF: 3. Namf_Communication_N1MessageNotify + Note right of PCF: 4. Map URSP Notification Component ID to UE, URSP rule, trigger + +``` + +Sequence diagram illustrating URSP rule rejection for existing URSP rules. The diagram shows interactions between UE, AMF, and PCF (AM/UE). + +**Figure 6.31.2.1-1: URSP rule rejection for existing URSP rules** + +0. The initial assumption is a URSP rule (URSP rule A) provisioned in the UE containing a URSP notification component (URSP Notification X), e.g. a pre-configured URSP rule or a URSP rule that has been signalled by the PCF and accepted (see 6.31.2.2). Privacy/security settings from the UE do not allow URSP Notification X1. +Traffic matches URSP rule A. URSP rule A is not applied due to the privacy/security settings, e.g. first use of a pre-configured URSP rule, change of security/privacy settings since the URSP rule was received from UE-PCF and accepted by the UE. +2. The UE sends the a URSP Notification via a UL NAS TRANSPORT message. The included UE Policy Container is of type URSP Notification and contains: + - URSP rule A rejection. + - Reason for rejection: URSP Notification Component A not allowed. +3. The AMF sends Namf\_Communication\_N1MessageNotify request to the PCF including the UE Policy Container received from UE as described in TS 23.304 [12], clause 6.2.4, step 2. +4. The PCF uses the URSP Notification Component ID to map the incoming notification information to a UE, URSP rule (if the URSP rule is known) and trigger condition. + +NOTE: The UE can report that a URSP Rule provided in the UE Configuration Update for UE Policies was not installed, this procedure could also be enhanced to allow the UE to report that a URSP Rule was removed to the network. + +#### 6.31.2.4 Example of PCF actions on receiving URSP Notifications + +This clause lists some examples of actions the PCF could take on reception of URSP notifications. While the solution focuses on asserting the URSP usage by the UE, the examples shown in this clause show possible uses of this information and that the solution is compatible with the current 5GC architecture and design principles. + +The examples focus on how SM-PCF, AF and/or NEF can be notified of URSP Notifications received by the UE-PCF. The mapping of a URSP notification to a URSP rule by the UE-PCF is only considered for URSP rules known to the UE-PCF. + +This solution focuses on how the 5GC can be made aware of URSP rule enforcement, but following actions are possible based on reception of URSP Notifications: + +- Sending an alternative URSP rule to the UE (or removing an existing one) without notification capability and/or modifying the applied SM policy. +- Rejecting the UE (e.g. the service requires a specific SLA and part of the SLA can only be fulfilled if the URSP rule is applied) +- Notifying the application owner, when the URSP Rule was generated based on Service Parameters provided by the AF. + +Related to possible triggers, an example use case for sending an alternative URSP rule to the UE (or removing an existing one) would be a combination with transmission of a certain amount of data, whereas only a certain amount of data would be using a specific slice (e.g. with resource reservation), whereas after that the URSP rule could be removed by the UE-PCF. + +#### 6.31.2.4.1 Example action: Storage of received notification on the UDR linked to the triggered UE + +In this example, the PCF receiving the URSP Notification performs storage of the received notification on the UDR linked to the triggered UE (e.g. via `Nudr_DR/policy-data/ues/{ueId}/`) and, if available, to the generating URSP rule. Pre-configured URSP rules may not be known to the PCF but known to the operator. + +**NOTE:** There is already a procedure for the PCF to report to the AF via UDR, per current procedures, the UDR is a repository not handling reporting of events but rather PCF or AMF can do it directly. This example could alternatively (and with less need for changes) be realized in such a way. + +Based on the received information, the UDR can generate notifications towards SM-PCF(s) subscribed to notifications related to a given URSP policy rule. With the information that a given application linked to the URSP is active, the SM-PCF can steer the session policy to e.g., increase the QoS associated to a PDU session. + +Specific (example) use cases related to this example would be a PDU session used by an application (e.g. slice offering GBR services) where a second application is now first used (and so signalled by the UE). The existing PDU session's GBR could now be updated so that it can also accommodate the additional application. Similarly, if it is detected that the second application is not used anymore (e.g. via periodic reporting), the GBR could be adjusted down. + +For the realization of this example, it is considered that the UDR contains a mapping between the URSP rules (accessed via `/policy-data/ues/{ueId}/am-data`) and SM policy data (accessed via `/policy-data/ues/{ueId}/sm-data`). In this way, a SM-PCF can subscribe to events related to its SM policies without requiring any explicit knowledge of what URSP rules are related to its SM policies. + +For URSP Notifications where the associated URSP rule is not known by the UE-PCF (e.g. possible in the case of a UE with pre-configured URSP rules), a subscription based on the URSP Notification identifier can be realized. + +![Sequence diagram for Figure 6.31.2.4.1-1 showing the flow between AMF, UE-PCF, UDR, and SM-PCF.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UE-PCF + participant UDR + participant SM-PCF + + Note right of UDR: 1. URSP rule A related to SM policy A. +Traffic Descriptor contains App A + + SM-PCF->>UDR: 2. Subscribe to URSP notifications for URSP rule X, which is related to SM policy A + AMF-->>UE-PCF: 3. Namf_Communication_N1MessageNotify (URSP notification data for URSP rule X) + UE-PCF->>UDR: 4. Store URSP notification data for URSP rule X + UDR->>SM-PCF: 5. Notify (URSP notification for URSP rule X) + Note right of SM-PCF: 6. Adjust SM policy A after being aware that application A is triggered + +``` + +Sequence diagram for Figure 6.31.2.4.1-1 showing the flow between AMF, UE-PCF, UDR, and SM-PCF. + +**Figure 6.31.2.4.1-1: Example flow for Storage of received notification on the UDR linked to the triggered UE and notification to SM-PCF based on SM policy** + +![Sequence diagram for Figure 6.31.2.4.1-2 showing the flow between AMF, UE-PCF, UDR, and AF/NEF.](64bec4cd45e47e1976245711f702aca2_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UE-PCF + participant UDR + participant AF/NEF + + AF/NEF->>UDR: 1. Subscribe to URSP notifications for URSP Notification ID=X + AMF-->>UE-PCF: 2. Namf_Communication_N1MessageNotify (URSP notification X for URSP rule A) + UE-PCF->>UDR: 3. Store URSP notification + UDR->>AF/NEF: 4. Notify (URSP Notification with ID=X) + +``` + +Sequence diagram for Figure 6.31.2.4.1-2 showing the flow between AMF, UE-PCF, UDR, and AF/NEF. + +**Figure 6.31.2.4.1-2: Example flow for Storage of received notification on the UDR linked to the triggered UE for URSP rule not known to UE-PCF and notification to AF/NEF based on URSP notification ID** + +Impacts related to this example: + +PCF: + +- UE-PCF: Add received URSP notification to UDR. +- SM-PCF: Subscribe to UDR for URSP notifications related to a SM policy. + +AF/NEF: + +- Subscribe to UDR for URSP notifications related to a given application ID and/or notification ID. + +UDR: + +- Storage of URSP notification data in UDR + +- Add link in UDR between the existing /policy-data/ues/{ueId}/am-data and /policy-data/ues/{ueId}/sm-data so that a SM-PCF can subscribe to events related to SM policies without having to refer to UE policy-related data +- Map received URSP notification data to a SM policy +- Probably add subscription procedure for insertion of URSP Notifications to UE policy data for a given SM policy, URSP notification ID and/or application ID. Current subs-to-notify information contained in PolicyDataSubscription is geared towards changes in elements, not insertion of related elements + +#### 6.31.2.4.2 Example action: Notification via Event exposure to other NFs + +In this example, the PCF receiving the URSP Notification generates a notification via Event exposure to other NFs (e.g. NWDAF for analytics, anomaly detection, SM-PCF to steer policies applied to PDU sessions) or AF. + +NOTE: It is assumed the subscriber (e.g. SM-PCF, AF, NEF) can locate the UE-PCF, e.g. via the BSF and that UE-PCF and subscriber have connectivity. + +![Sequence diagram illustrating the notification flow between AMF, UE-PCF, and SM-PCF based on URSP rule ID.](034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg) + +``` +sequenceDiagram + participant AMF + participant UE-PCF + participant SM-PCF + + Note right of SM-PCF: 1. URSP rule A known from UDR. SM-PCF locates UE-PCF for UE A + SM-PCF->>UE-PCF: 2. Subscribe to URSP notifications related to URSP rule A + Note left of AMF: 3. Namf_Communication_NIMessageNotify (URSP notification data for URSP rule A) + AMF-->>UE-PCF: + UE-PCF->>SM-PCF: 4. Notify (URSP notification for URSP rule A) + Note right of SM-PCF: 5. Adjust SM policy A after being aware that application A is triggered +``` + +The sequence diagram shows the interaction between three Network Functions (NFs): AMF, UE-PCF, and SM-PCF. The process starts with the SM-PCF (Step 1) knowing about URSP rule A from the UDR and locating the UE-PCF for UE A. The SM-PCF then sends a subscription request (Step 2) to the UE-PCF for URSP notifications related to URSP rule A. The AMF sends a notification message (Step 3) to the UE-PCF. The UE-PCF then sends a notification (Step 4) to the SM-PCF. Finally, the SM-PCF adjusts its SM policy A (Step 5) after being aware that application A is triggered. + +Sequence diagram illustrating the notification flow between AMF, UE-PCF, and SM-PCF based on URSP rule ID. + +Figure 6.31.2.4.2-1: Example flow for Notification via Event exposure to SM-PCF based on URSP rule ID + +![Sequence diagram showing the flow for Notification via Event exposure to AF/NEF based on URSP Notification ID. The diagram involves three entities: AMF, UE-PCF, and AF/NEF. The sequence is: 1. AF/NEF sends a 'Subscribe to URSP notifications of URSP Notification ID=X' message to UE-PCF. 2. AMF sends a 'Namf_Communication_N1MessageNotify (URSP notification ID=X)' message to UE-PCF. 3. UE-PCF sends a 'Notify (URSP notification for URSP notification ID=X)' message to AF/NEF.](6e9d059430baba0c363e33749f68b107_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UE-PCF + participant AF/NEF + Note right of AF/NEF: 1. Subscribe to URSP notifications of URSP Notification ID=X + AF/NEF->>UE-PCF: 1. Subscribe to URSP notifications of URSP Notification ID=X + Note right of AMF: 2. Namf_Communication_N1MessageNotify (URSP notification ID=X) + AMF-->>UE-PCF: 2. Namf_Communication_N1MessageNotify (URSP notification ID=X) + Note right of UE-PCF: 3. Notify (URSP notification for URSP notification ID=X) + UE-PCF->>AF/NEF: 3. Notify (URSP notification for URSP notification ID=X) + +``` + +Sequence diagram showing the flow for Notification via Event exposure to AF/NEF based on URSP Notification ID. The diagram involves three entities: AMF, UE-PCF, and AF/NEF. The sequence is: 1. AF/NEF sends a 'Subscribe to URSP notifications of URSP Notification ID=X' message to UE-PCF. 2. AMF sends a 'Namf\_Communication\_N1MessageNotify (URSP notification ID=X)' message to UE-PCF. 3. UE-PCF sends a 'Notify (URSP notification for URSP notification ID=X)' message to AF/NEF. + +**Figure 6.31.2.4.2-1: Example flow for Notification via Event exposure to AF/NEF based on URSP Notification ID** + +Impacts related to this example: + +PCF: + +- UE-PCF: Addition of EventExposure to Npcf\_UEPolicyControl to send received URSP notification to subscribed NFs based on URSP rule identifier +- SM-PCF: Subscribe to UE-PCF for URSP notifications related to a SM policy rule +- SM-PCF: Identify UE-PCF for a given UE + +AF/NEF: + +- Subscribe to UDR for URSP notifications related to a given application ID and/or notification ID +- Identify UE-PCF for a given UE + +UDR: + +- Add link in UDR between the existing /policy-data/ues/{ueId}/am-data and /policy-data/ues/{ueId}/sm-data so that a SM-PCF can subscribe to events related to SM policies without having to know UE policy-related data + +#### 6.31.2.4.3 Example action: Notification of Application owner via NEF + +Based on the examples shown in clauses 6.31.2.4.1 and 6.31.2.4.2, the awareness of whether a UE enforces a URSP rule for specific application traffic can be used to convey information to the application owner. While an application owner can be aware whether its application is running, it may be interested to know via notifications from the 5GC whether a URSP rule associated with the application is active (e.g. as a relevant KPI part of an SLA). + +![Sequence diagram illustrating the example flow for Notification of Application owner via NEF. The diagram shows five lifelines: AMF, UE-PCF, UDR, NEF, and Application Owner. The sequence of messages is: 1. Subscription to notifications related to App A's URSP rules from Application Owner to NEF; 2. Subscription for URSP notifications related to App A (either directly to UE-PCF or via UDR) from NEF to UE-PCF; 4. Namf_Communication_NIMessageNotify (URSP notification data for URSP rule A) from AMF to UE-PCF; 5. Notify (URSP notification for URSP rule A) from UE-PCF to NEF; 6. Notify (URSP notification for App A) from NEF to Application Owner.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UE-PCF + participant UDR + participant NEF + participant Application Owner + + Note right of Application Owner: 1. Subscription to notifications related to App A's URSP rules + Application Owner->>NEF: 1. Subscription to notifications related to App A's URSP rules + Note right of NEF: 2. Subscription for URSP notifications related to App A (either directly to UE-PCF or via UDR) + NEF->>UE-PCF: 2. Subscription for URSP notifications related to App A (either directly to UE-PCF or via UDR) + Note left of AMF: 4. Namf_Communication_NIMessageNotify (URSP notification data for URSP rule A) + AMF-->>UE-PCF: 4. Namf_Communication_NIMessageNotify (URSP notification data for URSP rule A) + Note right of UE-PCF: 5. Notify (URSP notification for URSP rule A) + UE-PCF->>NEF: 5. Notify (URSP notification for URSP rule A) + Note right of NEF: 6. Notify (URSP notification for App A) + NEF->>Application Owner: 6. Notify (URSP notification for App A) + +``` + +Sequence diagram illustrating the example flow for Notification of Application owner via NEF. The diagram shows five lifelines: AMF, UE-PCF, UDR, NEF, and Application Owner. The sequence of messages is: 1. Subscription to notifications related to App A's URSP rules from Application Owner to NEF; 2. Subscription for URSP notifications related to App A (either directly to UE-PCF or via UDR) from NEF to UE-PCF; 4. Namf\_Communication\_NIMessageNotify (URSP notification data for URSP rule A) from AMF to UE-PCF; 5. Notify (URSP notification for URSP rule A) from UE-PCF to NEF; 6. Notify (URSP notification for App A) from NEF to Application Owner. + +**Figure 6.31.2.4.2-1: Example flow for Notification of Application owner via NEF** + +Impacts related to this example additionally to those in clauses 6.31.2.4.1 or 6.31.2.4.2: + +NEF: + +- Subscription from application owner to URSP usage by a given application or URSP notification ID (e.g. for pre-configured URSP rules), subscription to UDR or UE-PCF to URSP notifications related to a given application + +PCF or UDR: + +- Allow subscription to URSP notifications related to a given Application ID + +### 6.31.3 Impacts on Existing Nodes and Functionality + +UE: + +- Support for additional URSP Notification Component in received UE policy container via UE Configuration Update. +- Support for acceptance/rejection of URSP rules containing URSP Notification component(s) based on URSP security/privacy. +- Support for triggering of URSP notifications sent via UL NAS TRANSPORT and a new UE Policy Container of type URSP Notification. + +AMF: + +- Forward URSP rule notifications to PCF received via UL NAS TRANSPORT. + +PCF: + +- Support for URSP rule notifications forwarded from AMF via Namf\_Communication\_NIMessageNotify. + +NOTE: Impacts regarding the different examples of PCF actions on receiving URSP notifications are not necessary to realize the solution and are informatively included in each corresponding example clause. + +## 6.32 Solution #32: Application Detection using Domain Descriptor + +### 6.32.1 Description + +This solution addresses the following technical issues of the KI#2: + +- Whether and how the 5GC can be made aware whether or when the UE enforces a URSP rule to route an application traffic to a PDU Session based on the URSP rule provisioned by 5GC. + +This solution provides a part of solution to address the above key issue only for the case where the Domain Descriptor is used in the URSP rule. This solution can be used with other application detection solution. + +Among various traffic descriptors are listed in URSP rules, the domain descriptor is one of useful descriptors to identify the application traffic. + +Today, UPF-based mechanism to detect the FQDN-based application traffic can be used, however, it has the following limitations: + +- It may not work if DNS over TLS or DNS over HTTPS is used. +- It may not guarantee the same IP address is resolved since the EAS IP address may be different based on EDNS Client Subnet option is used. Since the specifications do not specify how the UPF detect the domain name, based on the UPF implementations, the different IP address for the same FQDN can be resolved. + +Therefore, the current mechanism is not enough to check whether the application traffic from the UE is compliant with the URSP if the domain traffic descriptor is used. + +This solution provides a mechanism for the UE-PCF to detect application traffic detection using domain descriptor to check whether the UE is compliant with the traffic descriptor for the case when the EASDF is used for edge computing. This solution assumes that the EASDF for edge computing is deployed and SMF can be notified when the EASDF detects the DNS messages. + +The UE-PCF is notified the PDU Session establishment of the target UE to be checked for the URSP compliance. The UE-PCF subscribes SM-PCF for the reporting of application traffic detection for FQDN based the flow descriptor. The SM-PCF updates the PCC rules with FQDN-based flow descriptor for the SMF to report if DNS message exchanges are detected or DNS resolved traffic identified by the FQDN is detected. + +Figure 6.32.1-1 shows an abstract operation of 5GC for DNS message detection and reporting. The UE-PCF subscribes the application detection indicating DNS message detection and reporting with FQDN to the SM-PCF. The SM-PCF updates the PCC rules indicating the DNS message reporting with FQDN-based SDF template. + +In addition to the existing IP-based or Ethernet-based service data flow filters and in a PCC rule or an application identifier, it is proposed to define additional service data flow filter which identifies a FQDN or FQDN range with regular expression. In this solution, it is also called as a FQDN-based SDF template. + +The SMF updates DNS message handling rule with EASDF. When the UE, EASDF and the DNS server exchanges the DNS message, the EASDF detects and reports the DNS message to the SMF. The SMF notifies the detected application information to the SM-PCF. SM-PCF forwards the information to the UE-PCF. + +![Figure 6.32.1-1: FQDN based Application Detection (DNS message detection and reporting) diagram. The diagram shows the interaction between UE, UPF, SMF, PCF (SM), UE-PCF (or NEF), EASDF, and DNS Server. The flow is as follows: 1. UE-PCF (or NEF) sends '1. Application detection (FQDN)' to PCF (SM). 2. PCF (SM) sends '2. PCC Rule (SDF-FQDN, Application Detection)' to SMF. 3. SMF sends '3. EASDF Context Update (FQDN)' to EASDF. 4. UE sends '4. DNS Query' to UPF. 5. UPF sends '5. Reporting' to EASDF. 6. EASDF sends '6. Notify' to SMF. 7. SMF sends '7. Notify' to PCF (SM).](9eba62b255ea4757497c72582d0fa54e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UPF + participant SMF + participant PCF as PCF (SM) + participant UE-PCF as UE-PCF (or NEF) + participant EASDF + participant DNS Server + + Note right of UE-PCF: 1. Application detection (FQDN) + UE-PCF->>PCF: 1. Application detection (FQDN) + Note right of PCF: 2. PCC Rule (SDF-FQDN, Application Detection) + PCF->>SMF: 2. PCC Rule (SDF-FQDN, Application Detection) + Note right of SMF: 3. EASDF Context Update (FQDN) + SMF->>EASDF: 3. EASDF Context Update (FQDN) + Note right of UE: 4. DNS Query + UE->>UPF: 4. DNS Query + Note right of UPF: 5. Reporting + UPF->>EASDF: 5. Reporting + Note right of EASDF: 6. Notify + EASDF->>SMF: 6. Notify + Note right of SMF: 7. Notify + SMF->>PCF: 7. Notify + +``` + +Figure 6.32.1-1: FQDN based Application Detection (DNS message detection and reporting) diagram. The diagram shows the interaction between UE, UPF, SMF, PCF (SM), UE-PCF (or NEF), EASDF, and DNS Server. The flow is as follows: 1. UE-PCF (or NEF) sends '1. Application detection (FQDN)' to PCF (SM). 2. PCF (SM) sends '2. PCC Rule (SDF-FQDN, Application Detection)' to SMF. 3. SMF sends '3. EASDF Context Update (FQDN)' to EASDF. 4. UE sends '4. DNS Query' to UPF. 5. UPF sends '5. Reporting' to EASDF. 6. EASDF sends '6. Notify' to SMF. 7. SMF sends '7. Notify' to PCF (SM). + +Figure 6.32.1-1. FQDN based Application Detection (DNS message detection and reporting) + +The Figure 6.32.1-1 shows an abstract operation of 5GC for DNS resolved traffic detection and reporting. The UE-PCF subscribes the application detection indicating DNS resolved traffic detection and reporting with FQDN to the SM-PCF. The SM-PCF updates the PCC rules indicating the DNS resolved traffic detection and reporting with FQDN-based SDF template. The SMF updates DNS message handling rule with EASDF. When the UE, EASDF and the DNS server exchanges the DNS message, the EASDF detects and reports the DNS message to the SMF. The SMF updates N4 rule (e.g. PDU and URR) to the UPF. When the UPF detects the application traffic, it notifies the SMF of the detected traffic. The SMF notifies the detected application information to the SM-PCF. SM-PCF forwards the information to the UE-PCF. + +![Figure 6.32.1-2: FQDN based Application Detection (DNS resolved traffic detection and reporting). This sequence diagram shows the interaction between UE, UPF, SMF, PCF (SM), UE-PCF (or NEF), EASDF, AS, and DNS Server. The process starts with UE-PCF sending an 'Application detection (FQDN)' to PCF (SM). PCF (SM) sends a 'PCC Rule (SDF-FQDN, Application Detection)' to SMF. SMF sends an 'N4 Update (PDR, URR)' to UPF. UE sends a 'DNS Query and Response' to UPF. UPF sends 'Application traffic between UE and AF' to EASDF. EASDF sends 'Reporting (FQDN, IP)' to SMF. SMF sends a 'Notify' to PCF (SM). PCF (SM) sends a 'Notify' to UE-PCF (or NEF). SMF also sends an 'EASDF Context Update (FQDN)' to EASDF.](6348f4fc8b3848158fcfbe85e26a731d_img.jpg) + +Figure 6.32.1-2: FQDN based Application Detection (DNS resolved traffic detection and reporting). This sequence diagram shows the interaction between UE, UPF, SMF, PCF (SM), UE-PCF (or NEF), EASDF, AS, and DNS Server. The process starts with UE-PCF sending an 'Application detection (FQDN)' to PCF (SM). PCF (SM) sends a 'PCC Rule (SDF-FQDN, Application Detection)' to SMF. SMF sends an 'N4 Update (PDR, URR)' to UPF. UE sends a 'DNS Query and Response' to UPF. UPF sends 'Application traffic between UE and AF' to EASDF. EASDF sends 'Reporting (FQDN, IP)' to SMF. SMF sends a 'Notify' to PCF (SM). PCF (SM) sends a 'Notify' to UE-PCF (or NEF). SMF also sends an 'EASDF Context Update (FQDN)' to EASDF. + +Figure 6.32.1-2. FQDN based Application Detection (DNS resolved traffic detection and reporting) + +## 6.32.2 Procedures + +### 6.32.2.1 Procedure of application detection for domain (e.g. FQDN) traffic descriptor + +This procedure describes the FQDN-based application detection + +![Figure 6.32.2-1: FQDN-based Application Detection. This sequence diagram shows the interaction between UE, SMF, UPF, EASDF, SM-PCF, UE-PCF, DNS Server, and AS. The process starts with UE-PCF sending a 'PolicyAuthorization_Subscribe' to SM-PCF. SM-PCF sends an 'SM Policy Association UpdateNotify' to SMF. SMF generates a 'DNS Message Handling Rule using FQDN-based Flow description' and updates the 'DNS Message Handling Rule (DNS-Response, FQDN)' to EASDF. UE sends a 'DNS Query' to EASDF. EASDF sends a 'DNS Query (FQDN in Question Field)' to DNS Server. DNS Server sends a 'DNS Response (IP address in Answer Field)' to EASDF. EASDF sends a 'Notify FQDN, IP address' to SMF. SMF generates 'N4 Rules using IP address (PDR, URR)' and sends an 'N4 Update Request (PDR, URR)' to UPF. UPF sends an 'N4 Update Response' to SMF. SMF sends an 'SM Policy Association Update (A. DNS message reporting: FQDN, IP address)' to SM-PCF. SM-PCF sends a 'PolicyAuthorization_Notification (A. DNS message reporting)' to UE-PCF. UE receives a 'DNS Response (IP address in Answer Field)' from EASDF. UE sends 'Application Traffic (e.g. TCP SYN exchange, HTTP Request)' to AS. UPF sends a 'Reporting of Application Detection (IP address)' to SMF. SMF sends an 'SM Policy Association Update (B. DNS resolved traffic detection: IP address)' to SM-PCF. SM-PCF sends a 'PolicyAuthorization_Notification (B. DNS resolved traffic detection)' to UE-PCF.](56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg) + +Figure 6.32.2-1: FQDN-based Application Detection. This sequence diagram shows the interaction between UE, SMF, UPF, EASDF, SM-PCF, UE-PCF, DNS Server, and AS. The process starts with UE-PCF sending a 'PolicyAuthorization\_Subscribe' to SM-PCF. SM-PCF sends an 'SM Policy Association UpdateNotify' to SMF. SMF generates a 'DNS Message Handling Rule using FQDN-based Flow description' and updates the 'DNS Message Handling Rule (DNS-Response, FQDN)' to EASDF. UE sends a 'DNS Query' to EASDF. EASDF sends a 'DNS Query (FQDN in Question Field)' to DNS Server. DNS Server sends a 'DNS Response (IP address in Answer Field)' to EASDF. EASDF sends a 'Notify FQDN, IP address' to SMF. SMF generates 'N4 Rules using IP address (PDR, URR)' and sends an 'N4 Update Request (PDR, URR)' to UPF. UPF sends an 'N4 Update Response' to SMF. SMF sends an 'SM Policy Association Update (A. DNS message reporting: FQDN, IP address)' to SM-PCF. SM-PCF sends a 'PolicyAuthorization\_Notification (A. DNS message reporting)' to UE-PCF. UE receives a 'DNS Response (IP address in Answer Field)' from EASDF. UE sends 'Application Traffic (e.g. TCP SYN exchange, HTTP Request)' to AS. UPF sends a 'Reporting of Application Detection (IP address)' to SMF. SMF sends an 'SM Policy Association Update (B. DNS resolved traffic detection: IP address)' to SM-PCF. SM-PCF sends a 'PolicyAuthorization\_Notification (B. DNS resolved traffic detection)' to UE-PCF. + +Figure 6.32.2-1: FQDN-based Application Detection + +1. UE-PCF subscribes the reporting of application detection to the SM-PCF. The message includes the FQDN-based SDF template to identify the application traffic matching the domain descriptor of the target UE. The + +subscription request may also request either DNS reporting indication or DNS resolved traffic detection if FQDN-based service data flow template is used. + +2. SM-PCF updates the PCC rules with FQDN-based SDF template for the SMF to report the detected application. The FQDN-based SDF template can represent one or more FQDN such as abc.asp1.com, abcd.asp1.com or FQDN range in regular expression such as \*.asp1.com. The PCC rules indicates either 1) DNS message reporting or 2) DNS resolved traffic detection. +3. The SMF generates DNS message handling rules using FQDN-based SDF template. +4. The SMF sends the DNS message handling rule for the EASDF to report the DNS message when the EASDF detects the DNS messages. +- 5-7. The UE exchanges the DNS Query and DNS Response with the DNS server via EASDF. +8. When detecting the DNS Response, the EASDF notifies the FQDN and resolved address for the FQDN to the SMF. +9. If the PCC rules indicates DNS resolved traffic detection, the SMF generates the corresponding N4 rules, e.g. PDR and URR in order for the UPF to report the traffic identified by IP address. +- 10-11. The SMF updates the N4 rules to the UPF. +12. If the PCC rule indicates DNS message reporting and the SMF is notified DNS message detection from the EASDF, the SMF notifies the detected FQDN and its IP address to the SM-PCF. +13. The SM-PCF notifies the notification address of the UE-PCF of the DNS message detection received from the SMF. +14. The EASDF forwards the DNS Response message to the UE. +15. After resolving the IP address of the application, the UE and the application server exchanges the application traffic (e.g. TCP SYN or HTTP transactions). +16. The UPF detects the traffic matching PDR and reports it to the SMF. +17. If the PCC rule indicates DNS resolved traffic detection and the SMF is notified the packet detection associated with the FQDN-based template from the UPF, the SMF notifies the DNS resolved traffic detection to the SM-PCF. +18. The SM-PCF notifies the notification address of the UE-PCF of the DNS resolved traffic detection received from the SMF. + +### 6.32.3 Impacts on services, entities and interfaces + +UE-PCF (The PCF for the UE): + +- The UE-PCF is able to utilize the SM-PCF service for FQDN-based application detection. + +SM-PCF (The PCF for the Session): + +- The SM-PCF is required to support the notification and PCC rules for FQDN-based application detection. +- The SM-PCF is required to understand the proposed FQDN-based service data flow filter with DNS reporting indication and DNS resolved traffic detection options. + +SMF: + +- The SMF is required to support the PCC rules indicating FQDN-based application detection identified FQDN-based SDF template. +- The SMF is required to understand the proposed FQDN-based service data flow filter with DNS reporting indication and DNS resolved traffic detection options. +- The SMF is required to generate and update the DNS message handling rule using FQDN-based service data flow template. + +- The SMF is required to report the DNS message reporting to the SM-PCF if the DNS reporting option is indicated in the PCC rules. +- The SMF is required to update N4 rules with the UPF based on the reporting from the EASDF and report the DNS resolved traffic detection to the SM-PCF if DNS resolved traffic detection option is indicated in the PCC rules. + +## 6.33 Solution #33: Consistent URSP Provisioning across 5GS and EPS + +### 6.33.1 Description + +This solution addresses KI#3. + +With regard to the scenarios and gaps (first two bullets in the KI#3), if a UE has used the Route Selection component (e.g. DNN) in a URSP rule in EPS and the Route Selection component (e.g. DNN) has been changed when the UE stays in EPS, the updated URSP rule needs to be provisioned to UE in EPS, otherwise the UE in EPS may use outdated DNN to establish PDN connection in EPS. In 5GS the UE may be provisioned with URSP rules for both 5GS and EPS by the PCF of the HPLMN. Only the rules provisioned by the PCF are used by the UE, if both URSP rules provisioned by the PCF and pre-configured URSP rules are present. The URSP rules are provisioned in UE using NAS messages. The AMF transparently transfers the UE Policy container (UE policy information) received from the PCF to the UE (using DL NAS TRANSPORT message). The UE Policy container includes the list of Policy Sections as described in TS 23.503 [4]. Similar mechanism can be used to provision URSP rules in EPS. + +For the pre-Rel-18 UE, when it's attached to EPC, even if the UE-PCF provisions/updates the URSP rule to it, it will silently discard the URSP rule in the ePCO since the new ePCO cannot be recognized by the pre-Rel-18 UE. In order to avoid unnecessary signalling overload for URSP provisioning/updating for pre-Rel-18 UE, UE-PCF needs to be aware whether a UE supports the URSP Provisioning in EPS or not. + +To realize provisioning of consistent URSP rules in UE, this solution follows the below two principles: + +- 1) The same set of URSP is provisioned to UE regardless of UE attaching to EPS or registering to 5GS. +- 2) The UE in EPS uses the components in RSD of a URSP rule according to Rel-16 specification defined in clause 5.17.1.2 of TS 23.501 [2]. + +The EPS and 5GS interworking architecture defined in TS 23.501 [2] is reused, the solution addresses both the collocated and separate SM-PCF and UE-PCF deployment scenario, N7 interface is reused to provision URSP from SM-PCF to SMF+PGW-C and no new interface is introduced. The solution proposes a mechanism for the network to provision and update the URSP for a UE in EPS by encapsulating UE Policy Container in ePCO via one of the PDN connections. The UE Policy Container is transparently forwarded via SMF+PGW-C. The communication between SMF+PGW-C and SM-PCF reuses the SM Policy Association procedures. + +#### 6.33.1.1 Use Cases and Scenarios + +When a UE attaches initially in EPC or when the UE handovers from 5GC to EPC, UE-PCF may need to update the URSPs in the UE: + +- During Initial attach procedure in EPS due to for example: + - New AF guidance on URSP request applicable to the UE was sent by an AF while the UE is deregistered and prior to the EPC attach procedure, so the corresponding URSP rules were not delivered yet to the UE. + - Operator policies configured with time, location or any other condition are met when the UE attaches to EPC, implying new or updated URSP rules apply under those conditions. + - Operator policies for determining URSPs were updated by the operator while the UE is deregistered and prior to the EPC attach procedure, so the corresponding URSP rules were not delivered yet to the UE. +- At any time a URSP is changed while the UE is registered in EPC (coming from EPC initial attachment or after handover from 5GC) due to for example: + +- New AF guidance on URSP request applicable to the UE is sent by an AF. +- Due to time, location change or other network condition the PCF determines that an operator policy configured for the operator for URSP determination applies in the new network conditions, implying new or updated URSP rules apply to the UE. + +### 6.33.1.2 Provision URSP to a UE in EPC + +The solution in this paper proposes a mechanism that allows the network to update the URSPs for a UE in EPC, by encapsulating UPDP messages into a new ePCO parameter (from now on UE Policy Container ePCO) and transfer them to the UE via PDN connection. + +The solution assumes the same protocol (UPDP protocol) for URSP Provisioning between the PCF and the UE than in 5GC, although the final decision on this is up to stage 3. + +The mechanism reuses the existing capability of the EPC network for sending ePCO from the UE to the SMF+PGW-C (and vice versa) and in addition it proposes a way to transport the UE Policy Container from the SMF+PGW-C to the PCF (and vice versa) based on reusing existing PDU session procedures. + +For the delivery of URSPs to UEs in EPC, this solution assumes the standard solution for interworking architecture between EPC and 5GC as described in TS 23.501 [2]. + +When the PCF needs to send a UE Policy update towards the UE in EPC, it invokes a SM Policy Association Modification including the corresponding UPDP message into a new IE (UE Policy Container) in the N7 interface. When the SMF+PGW-C receives this new IE the SMF+PGW-C encapsulates it into UE Policy Container ePCO and transfers them to the UE by using existing procedure of PDN GW initiated bearer modification without bearer QoS update as defined in clause 5.4.3 of TS 23.401 [8]. + +When the UE in EPC needs to send a UPDP message towards the UE-PCF in relation to UE Policy handling the UE first encapsulates the UPDP message into a UE Policy Container ePCO and then transfers it towards the SMF+PGW-C by reusing existing mechanisms. When the SMF+PGW-C receives such UE Policy Container ePCO from the UE, just forwards transparently the UE Policy Container towards the PCF by reusing SMF initiated SM Policy Association procedure (establishment or modification). + +The solution also proposes that the UE has to be able to handle the reception of such UPDP messages received over EPC NAS signalling in a similar way than when received over 5GC NAS signalling in 5GC. + +In addition, for those events happening in PCF which may trigger the sending of a URSP update for a UE (as described in clause 6.33.1.1), the PCF will check if the UE is currently in EPC, and if so will use one of these PDU sessions to trigger the delivery of the URSP updates, by invoking PCF initiated SM Policy Association modification procedure including the proper UE Policy Container. + +### 6.33.1.3 Handle the UE Policy Association during mobility from 5GS to EPS with N26 + +During initial Registration procedure, the UE needs to indicate its URSP Provisioning Support Indication in EPS in the 5GMM Capability to AMF. + +If the AMF knows that the UE supports URSP Provisioning in EPS and target EPC supports URSP provisioning to UE, the AMF doesn't terminate the UE Policy Association with UE-PCF and sends the UE Policy Association information for EPS (i.e. URSP Provisioning Support Indication in EPS, UE-PCF ID in 5GS, PCRTs) to MME during mobility (i.e. Handover, Idle mode mobility) from 5GS to EPS with N26. + +The PCRTs (Policy Control Request Trigger) for UE Policy include Location change (tracking area), Change of UE presence in Presence Reporting Area, Connectivity stage changes. The MME enforces the received PCRTs for UE Policy. + +When the MME receives the URSP Provisioning Support Indication in EPS, it creates a UE Policy Container for the UE including only the indication of MME Created UE Policy Container for 5GS to EPS Mobility and selects one of the PDN Connections serving the UE to establish the UE Policy association between SM-PCF and UE-PCF. The UE Policy Container and UE-PCF ID are included in the Modify bearer Request message sent to SGW and SMF+PGW-C. + +When the SMF receives the UE Policy Container, it initiates SM Policy Association Modification procedure by sending Npcf\_SMPolicyControl\_Update request to SM-PCF including UE-PCF ID and UE Policy Container. + +Based on the received UE-PCF ID, the SM-PCF knows it's a request for updating the UE Policy Association with UE-PCF identified by UE-PCF ID. The SM-PCF sends a Npcf\_UEPolicyControl\_Update request including the UE Policy Container to UE-PCF to modify the UE Policy Association for the UE. + +Based on the indication of MME Created UE Policy Container, the UE-PCF knows it's an MME initiated UE Policy Association update procedure after mobility from 5GS to EPS and updates the UE Policy Association with SM-PCF. For any subsequent URSP update, the UE-PCF contacts with SM-PCF. + +The UE-PCF may notify the AMF of the removal of the UE Policy Association via Npcf\_UEPolicyControl\_UpdateNotify service operation. + +## 6.33.2 Procedures + +### 6.33.2.1 UE Policy provisioning procedure with explicit URSP Support Indication in EPS + +For all pre-Rel-18 UEs, it would be impossible to provision/update the URSP to them since the new ePCO cannot be recognized by pre-Rel-18 UEs attached to EPC. Provisioning/updating URSP to pre-Rel-18 UEs in EPC will cause unnecessary signalling overload. Thus, the UE-PCF needs to be aware whether a UE supports the URSP Provisioning in EPS or not. + +For the cases that PDN Connectivity Request is sent by UE (i.e. Initial Attach procedure, UE requested PDN connectivity procedure, 5GS to EPS Mobility procedure without N26), the UE reports the UE Policy Container including URSP Provisioning Support indication in EPS in ePCO. + +![Sequence diagram of UE Policy provisioning procedure with explicit URSP Support Indication in EPS. The diagram shows interactions between UE, eNodeB, MME, S-GW, SMF+PGW-C, SM-PCF, and UE-PCF. The procedure involves an initial request from the UE, followed by policy control creation and update messages between the SMF+PGW-C, SM-PCF, and UE-PCF.](2914642fbfe4ae35924bdf4beb189c1f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant S-GW + participant SMF+PGW-C + participant SM-PCF + participant UE-PCF + + Note left of UE: 1. Attach Request or PDN Connectivity Request + UE->>SMF+PGW-C: 1. Attach Request or PDN Connectivity Request + SMF+PGW-C->>SM-PCF: 2. Npcf_SMPolicyControl_Create Request + SM-PCF->>UE-PCF: 3. Npcf_UEPolicyControl_Create Request + UE-PCF-->>SM-PCF: 4. Npcf_UEPolicyControl_Create Response + SM-PCF-->>SMF+PGW-C: 5. Npcf_SMPolicyControl_Create Response + SMF+PGW-C-->>UE: 6. Response + UE->>SMF+PGW-C: 7. Acknowledgement + SMF+PGW-C->>SM-PCF: 8. Npcf_SMPolicyControl_Create Update + SM-PCF->>UE-PCF: 9. Npcf_UEPolicyControl_Create Update + +``` + +Sequence diagram of UE Policy provisioning procedure with explicit URSP Support Indication in EPS. The diagram shows interactions between UE, eNodeB, MME, S-GW, SMF+PGW-C, SM-PCF, and UE-PCF. The procedure involves an initial request from the UE, followed by policy control creation and update messages between the SMF+PGW-C, SM-PCF, and UE-PCF. + +**Figure 6.33.2.1-1: UE Policy provisioning procedure with explicit URSP Provisioning Support Indication in EPS** + +1. The UE sends the UE Policy Container including URSP Provisioning Support indication in EPS which is indicating whether a UE supports URSP Provisioning or not in EPS (defined in clause 5.17.1.2 of TS 23.501 [2]) and the PSIs (Policy Set Identifier) in ePCO (extended PCO) to SMF+PGW-C during Initial Attach procedure (in the Attach Request) as described in clause 5.3.2.1 of TS 23.401 [8] or the UE requested PDN connectivity procedure (PDN Connectivity Request) as described in clause 5.10.2 of TS 23.401 [8]. +2. The SMF+PGW-C transparently forwards the UE Policy Container in ePCO to the SM-PCF as a new IE in the PDU Session Establishment (Npcf\_SMPolicyControl\_Create Request). + +NOTE 1: If the PCF involvement for a PDN connection is not required, the SMF+PGW-C should still establish SM Policy Association with SM-PCF and forward the UE Policy Container to SM-PCF based on local configuration. + +- The SM-PCF establishes the UE Policy Association with UE-PCF when a UE Policy Container is received from the UE and forwards the UE Policy Container to UE-PCF in Npcf\_UEPolicyControl\_Create Request. When a UE Policy Container is received at initial registration, the UE-PCF stores the URSP Provisioning Support indication in EPS in the UDR using Nudr\_DM\_Create including DataSet "Policy Data" and Data Subset "UE context policy control data". + +NOTE 2: UE-PCF is discovered and selected according to clause 6.3.7.1 of TS 23.501 [2]. + +- The UE-PCF gets policy subscription related information and the updated list of PSIs from the UDR. The UE-PCF creates the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503 [4]. Then it sends the latest UE policy information in the UE Policy Container to SM-PCF in Npcf\_UEPolicyControl\_Create Response. +- The SM-PCF forwards the UE Policy Container to the SMF+PGW-C in Npcf\_SMPolicyControl\_Create Response. +- The SMF+PGW-C sends the UE Policy Container in ePCO to UE in Activate Default EPS Bearer Context message which may be encapsulated in Attach Accept message. +- The UE sends a response to SMF+PGW-C by acknowledging the reception of the UE Policy reusing existing messages (e.g. Attach Complete, Modify Bearer Request) as defined in clause 5.3.2 of TS 23.401 [8]. +- The SMF+PGW-C forwards the acknowledgement of UE reception of the UE Policy to SM-PCF using Npcf\_SMPolicyControl\_Update request. +- The SM-PCF forwards the acknowledgement of UE reception of the UE Policy to UE-PCF using Npcf\_UEPolicyControl\_Update request. + +For the cases that PDN Connectivity Request is not sent by UE in EPS (i.e. 5GS to EPS handover using N26 interface, 5GS to EPS Idle mode mobility using N26 interface), UE reported URSP Provisioning Support indication in EPS during 5GS Registration procedure can be used by UE-PCF to determine whether to provision URSP to UE in EPS. This requires the UE to include the URSP Provisioning Support indication in EPS in the UE Policy Container in the initial Registration Request message. + +![Sequence diagram for Initial Registration in 5GS showing interactions between UE, NG-RAN, AMF, and UE-PCF.](9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant UE-PCF + Note left of UE: + UE->>AMF: 1. Registration Request + AMF->>UE-PCF: 2. Npcf_UEPolicyControl_Create Request + Note right of AMF: 3. UE Configuration Update procedure for transparent UE Policy delivery as defined in clause 4.2.4.3 of TS 23.502 + +``` + +Sequence diagram for Initial Registration in 5GS showing interactions between UE, NG-RAN, AMF, and UE-PCF. + +Figure 6.33.2.1-2: Initial Registration in 5GS + +- In the Registration Request message, the UE reports the URSP Support indication in EPS in the UE Policy Container to AMF. + +In order to allow the AMF to be aware of UE's Capability of URSP Provisioning Support in EPS, the UE needs to include the URSP Provisioning Support indication in EPS in the 5GMM Capability in the Registration Request message. This indication will be used by AMF to determine whether to terminate the UE Policy Association for the UE and whether to send the UE Policy Association information to MME during 5GS to EPS mobility with N26. The AMF stores the URSP Provisioning Support indication in EPS as part of the MM Context. + +- AMF establishes UE Policy Association with UE-PCF and forwards the UE Policy Container to UE-PCF. The UE-PCF stores the URSP Provisioning Support indication in EPS in the UDR using Nudr\_DM\_Create including DataSet "Policy Data" and Data Subset "UE context policy control data". + +3. The UE Configuration Update procedure for transparent UE Policy delivery as defined in clause 4.2.4.3 of TS 23.502 [3]. + +### 6.33.2.2 PCF triggered UE Policy provisioning procedure + +For the procedure for URSP update initiated by the PCF when the UE is in EPC, the procedure follows the steps described in the figure below: + +![Sequence diagram of PCF triggered URSP provisioning procedure. Lifelines: UE, MME, S-GW, SMF+PGW-C, SM-PCF, UE-PCF. The sequence starts with a trigger in UE-PCF, followed by a notification to SM-PCF, then to SMF+PGW-C. SMF+PGW-C initiates a bearer modification procedure with S-GW, MME, and UE. Finally, SMF+PGW-C sends another notification to SM-PCF, which then sends a response to UE-PCF.](a166566092dd84196c2ec048ca175290_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant S-GW + participant SMF+PGW-C + participant SM-PCF + participant UE-PCF + + Note right of UE-PCF: 1. Trigger to re-evaluate URSPs + UE-PCF->>SM-PCF: 2a. Npcf_UEPolicyControl_UpdateNotify Req + SM-PCF->>SMF+PGW-C: 3. Npcf_SMPolicyControl_UpdateNotify req + SMF+PGW-C->>S-GW: 4. Update Bearer Request + S-GW->>MME: 5. Update Bearer Request + MME->>UE: 6. EPS Bearer Context Request + UE->>MME: 7. EPS Bearer Context Response + MME->>S-GW: 8. Update Bearer Response + S-GW->>SMF+PGW-C: 9. Update Bearer Response + SMF+PGW-C->>SM-PCF: 10. Npcf_SMPolicyControl_Update req + SM-PCF->>UE-PCF: 11a. Npcf_UEPolicyControl_Update req + UE-PCF->>SM-PCF: 11b. Npcf_UEPolicyControl_Update ans + +``` + +Sequence diagram of PCF triggered URSP provisioning procedure. Lifelines: UE, MME, S-GW, SMF+PGW-C, SM-PCF, UE-PCF. The sequence starts with a trigger in UE-PCF, followed by a notification to SM-PCF, then to SMF+PGW-C. SMF+PGW-C initiates a bearer modification procedure with S-GW, MME, and UE. Finally, SMF+PGW-C sends another notification to SM-PCF, which then sends a response to UE-PCF. + +**Figure 6.33.2.2-1: PCF triggered URSP provisioning procedure** + +- 1: An event as described in clause 6.33.1.1 happens in UE-PCF. The UE-PCF triggers the re-evaluation of applicable URSPs for the UE and determines an update of URSP is needed for the UE. +- 2: The UE-PCF generates the URSP and send it to SM-PCF in the UE Policy Container via Npcf\_UEPolicyControl\_UpdateNotify Request. + +NOTE 1: It is assumed the UE Policy Association has been established and is maintained between the SM-PCF and UE-PCF after initial attach or 5GS to EPS mobility. + +- 3: The UE Policy Container is then provided to the SMF+PGW-C by invoking Npcf\_SMPolicyControl\_UpdateNotify request. + +NOTE 2: It is assumed the SM Policy Association has been established and is maintained between SMF and SM-PCF after initial attach or 5GS to EPS mobility. + +- 4, 5, 6: The SMF+PGW-C initiates a bearer modification procedure without bearer QoS update (as defined in clause 5.4.3 of TS 23.401 [8]) to provide the UE Policy Container in ePCO towards the UE. + +- 7: When the UE gets the UE Policy Container in ePCO, the UE processes that message in a similar way as it is received in 5GC, i.e. stores the URSP updates, optionally re-evaluates the mapping of applications into PDN connections according to the mapping of URSP values into EPC, and acknowledges the delivery result in UE Policy Container to the MME. + +- 8, 9: These steps follow the existing procedure defined for Update Bearer Response. + +- 10: Upon reception of UE Policy Container in ePCO in Update Bearer Response, the SMF+PGW-C then invokes Npcf\_SMPolicyControl\_Update Request including the content of the UE Policy Container in ePCO. + +11: The SM-PCF forwards the UE Policy Container to UE-PCF via Npcf\_UEPolicyControl\_Update request. + +### 6.33.2.3 5GS to EPS Handover using N26 interface + +![Sequence diagram for 5GS to EPS Handover using N26 interface. The diagram shows the interaction between UE, E-UTRAN, NG RAN, AMF, MME, SGW, V-SMF, V-UPF, SMF+PGW-C, and PGW-U+UPF. The process starts with a PDU Session and QoS flow setup in 5GS. The handover is initiated by the AMF sending a Handover required message to the MME. The MME then sends a Relocation request to the SGW, which in turn sends a Create session request to the V-SMF. The V-SMF sends a N4 Session Modification to the SMF+PGW-C. The SMF+PGW-C sends a N4 Session Modification to the PGW-U+UPF. The MME sends a Handover request to the E-UTRAN, which sends a Handover request ACK to the AMF. The AMF sends a Relocation response to the MME. The MME sends a Nsmf_PDUSession_UpdateSMContext Request to the V-SMF, which sends a Nsmf_PDUSession_UpdateSMContext Response to the SMF+PGW-C. The SMF+PGW-C sends a N4 Session Modification to the PGW-U+UPF. The AMF sends a Handover command to the E-UTRAN, which sends a Handover Complete message to the AMF. The AMF sends a Handover Notify to the MME. The MME sends a Relocation Complete Notification to the AMF, which sends a Relocation Complete Ack to the MME. The MME sends a Nsmf_PDUSession_ReleaseSMContext to the V-SMF. The MME sends a Modify bearer Request to the SGW, which sends a Modify bearer Request to the V-SMF. The V-SMF sends a N4 Session Modification to the SMF+PGW-C. The SMF+PGW-C sends a Modify bearer Response to the V-SMF, which sends a Modify bearer Response to the SGW. The SGW sends a Modify bearer Response to the MME. The MME sends a TAU procedure to the AMF. The AMF sends a PGW initiated dedicated bearer activation to the MME. The MME sends a Delete indirect data forwarding Tunnel request/response to the SGW, which sends a Delete indirect data forwarding tunnel to the V-SMF. The AMF sends a UE Context Release Command/Complete to the NG RAN. The SMF+PGW-C sends a N4 Session Modification to the PGW-U+UPF.](5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg) + +Sequence diagram for 5GS to EPS Handover using N26 interface. The diagram shows the interaction between UE, E-UTRAN, NG RAN, AMF, MME, SGW, V-SMF, V-UPF, SMF+PGW-C, and PGW-U+UPF. The process starts with a PDU Session and QoS flow setup in 5GS. The handover is initiated by the AMF sending a Handover required message to the MME. The MME then sends a Relocation request to the SGW, which in turn sends a Create session request to the V-SMF. The V-SMF sends a N4 Session Modification to the SMF+PGW-C. The SMF+PGW-C sends a N4 Session Modification to the PGW-U+UPF. The MME sends a Handover request to the E-UTRAN, which sends a Handover request ACK to the AMF. The AMF sends a Relocation response to the MME. The MME sends a Nsmf\_PDUSession\_UpdateSMContext Request to the V-SMF, which sends a Nsmf\_PDUSession\_UpdateSMContext Response to the SMF+PGW-C. The SMF+PGW-C sends a N4 Session Modification to the PGW-U+UPF. The AMF sends a Handover command to the E-UTRAN, which sends a Handover Complete message to the AMF. The AMF sends a Handover Notify to the MME. The MME sends a Relocation Complete Notification to the AMF, which sends a Relocation Complete Ack to the MME. The MME sends a Nsmf\_PDUSession\_ReleaseSMContext to the V-SMF. The MME sends a Modify bearer Request to the SGW, which sends a Modify bearer Request to the V-SMF. The V-SMF sends a N4 Session Modification to the SMF+PGW-C. The SMF+PGW-C sends a Modify bearer Response to the V-SMF, which sends a Modify bearer Response to the SGW. The SGW sends a Modify bearer Response to the MME. The MME sends a TAU procedure to the AMF. The AMF sends a PGW initiated dedicated bearer activation to the MME. The MME sends a Delete indirect data forwarding Tunnel request/response to the SGW, which sends a Delete indirect data forwarding tunnel to the V-SMF. The AMF sends a UE Context Release Command/Complete to the NG RAN. The SMF+PGW-C sends a N4 Session Modification to the PGW-U+UPF. + +**Figure 6.33.2.3-1: 5GS to EPS handover for single-registration mode with N26 interface defined in clause 4.11.1.2.1 of TS 23.502 [3]** + +In the Relocation Request message of step 3, the AMF includes the UE Policy Association information (i.e. URSP Provisioning Support Indication in EPS, UE-PCF ID selected in 5GS, PCRTs). MME stores this information. + +**NOTE:** The PCRTs (Policy Control Request Trigger) include Location change (tracking area), Change of UE presence in Presence Reporting Area, Connectivity state changes. + +In step 13 and 14a, MME selects one of the PDN Connections serving the UE to establish the UE Policy association between SM-PCF and UE-PCF. The MME creates and includes a UE Policy Container for UE including only the indication of MME Created UE Policy Container for 5GS to EPS Mobility in the Modify bearer Request. UE-PCF ID is also included in Modify bearer Request message. + +## 6.33.2.4 5GS to EPS Idle mode mobility using N26 interface + +![Sequence diagram for 5GS to EPS Idle mode mobility using N26 interface. The diagram shows the interaction between UE, eNB, NG-RAN, MME, AMF, SGW, V-SMF, V-UPF, SMF+PGW-C, PGW-U+UPF, PCF, and HSS+UDM. A shaded area labeled 'Home routed roaming' includes V-SMF, V-UPF, SMF+PGW-C, and PGW-U+UPF. The sequence starts with a TAU trigger in the UE, followed by TAU Request messages to the eNB and NG-RAN. The NG-RAN sends a TAU Request to the MME. The MME sends a Context Request to the AMF. The AMF sends an Nsmf_PDUSession_ContextRequest to the V-SMF. The V-SMF sends an N4 Session Modification to the PGW-U+UPF. The AMF sends a Context Response to the MME. The MME sends an Authentication/Security message to the UE. The AMF sends an Authentication/Security message to the MME. The MME sends a Context Ack to the AMF. The MME sends a Create Session Request to the SGW. The SGW sends a Modify Bearer Request to the SMF+PGW-C. The SMF+PGW-C sends an N4 Session Modification to the PGW-U+UPF. The SMF+PGW-C sends an SMF initiated SM Policy Association Modification to the PCF. The MME sends a Create Session Response to the SGW. The AMF sends an Update Location Request to the HSS+UDM. The HSS+UDM sends a Nudm_UECM_DeregistrationNotification to the AMF. The AMF sends a Nudm_SDM_Unsubscribe to the HSS+UDM. The AMF sends an Nsmf_PDUSession_ReleaseSMContext Request to the V-SMF. The V-SMF sends an N4 Session Termination to the PGW-U+UPF. The MME sends an Update Location Ack to the AMF. The NG-RAN sends a TAU Accept to the eNB. The eNB sends a TAU Complete to the UE. A dashed line at the bottom indicates a PGW initiated dedicated bearer setup if needed.](9874e3ac6f14360133f8e1674f79824f_img.jpg) + +Sequence diagram for 5GS to EPS Idle mode mobility using N26 interface. The diagram shows the interaction between UE, eNB, NG-RAN, MME, AMF, SGW, V-SMF, V-UPF, SMF+PGW-C, PGW-U+UPF, PCF, and HSS+UDM. A shaded area labeled 'Home routed roaming' includes V-SMF, V-UPF, SMF+PGW-C, and PGW-U+UPF. The sequence starts with a TAU trigger in the UE, followed by TAU Request messages to the eNB and NG-RAN. The NG-RAN sends a TAU Request to the MME. The MME sends a Context Request to the AMF. The AMF sends an Nsmf\_PDUSession\_ContextRequest to the V-SMF. The V-SMF sends an N4 Session Modification to the PGW-U+UPF. The AMF sends a Context Response to the MME. The MME sends an Authentication/Security message to the UE. The AMF sends an Authentication/Security message to the MME. The MME sends a Context Ack to the AMF. The MME sends a Create Session Request to the SGW. The SGW sends a Modify Bearer Request to the SMF+PGW-C. The SMF+PGW-C sends an N4 Session Modification to the PGW-U+UPF. The SMF+PGW-C sends an SMF initiated SM Policy Association Modification to the PCF. The MME sends a Create Session Response to the SGW. The AMF sends an Update Location Request to the HSS+UDM. The HSS+UDM sends a Nudm\_UECM\_DeregistrationNotification to the AMF. The AMF sends a Nudm\_SDM\_Unsubscribe to the HSS+UDM. The AMF sends an Nsmf\_PDUSession\_ReleaseSMContext Request to the V-SMF. The V-SMF sends an N4 Session Termination to the PGW-U+UPF. The MME sends an Update Location Ack to the AMF. The NG-RAN sends a TAU Accept to the eNB. The eNB sends a TAU Complete to the UE. A dashed line at the bottom indicates a PGW initiated dedicated bearer setup if needed. + +**Figure 6.33.2.4-1: 5GS to EPS Idle mode mobility using N26 interface defined in clause 4.11.1.3.2 of 23.502 [3]** + +In the Context Ack message of step 8, the AMF includes the UE Policy Association information (i.e. URSP Provisioning Support Indication in EPS, UE-PCF ID selected in 5GS, PCRTs for UE Policy). MME stores the UE Policy Association information. + +In step 9 and 10, MME selects one of the PDN Connections serving the UE to establish the UE Policy association between SM-PCF and UE-PCF. The MME creates and includes a UE Policy Container for UE including only the indication of MME Created UE Policy Container for 5GS to EPS Mobility in the Modify bearer Request. UE-PCF ID is also included in Modify bearer Request message. + +### 6.33.2.5 SM Policy and UE Policy Association Update after 5GS to EPS mobility using N26 interface + +![Sequence diagram showing the SM Policy and UE Policy Association update after 5GS to EPS mobility using N26 interface. The diagram involves three entities: SMF+PGW-C, SM-PCF, and UE-PCF. The sequence of messages is: 1. SMF+PGW-C sends Npcf_SMPolicyControl_Update Request to SM-PCF; 2. SM-PCF sends Npcf_UEPolicyControl_Update Request to UE-PCF; 3. UE-PCF sends Npcf_UEPolicyControl_Update Response to SM-PCF; 4. SM-PCF sends Npcf_SMPolicyControl_Update Response to SMF+PGW-C.](f5698523df298c80a0c6b5d4ca657993_img.jpg) + +``` + +sequenceDiagram + participant SMF+PGW-C + participant SM-PCF + participant UE-PCF + Note left of SMF+PGW-C: 1. Npcf_SMPolicyControl_Update Request + SMF+PGW-C->>SM-PCF: 1. Npcf_SMPolicyControl_Update Request + Note right of SM-PCF: 2. Npcf_UEPolicyControl_Update Request + SM-PCF->>UE-PCF: 2. Npcf_UEPolicyControl_Update Request + Note right of UE-PCF: 3. Npcf_UEPolicyControl_Update Response + UE-PCF->>SM-PCF: 3. Npcf_UEPolicyControl_Update Response + Note left of SMF+PGW-C: 4. Npcf_SMPolicyControl_Update Response + SM-PCF->>SMF+PGW-C: 4. Npcf_SMPolicyControl_Update Response + +``` + +Sequence diagram showing the SM Policy and UE Policy Association update after 5GS to EPS mobility using N26 interface. The diagram involves three entities: SMF+PGW-C, SM-PCF, and UE-PCF. The sequence of messages is: 1. SMF+PGW-C sends Npcf\_SMPolicyControl\_Update Request to SM-PCF; 2. SM-PCF sends Npcf\_UEPolicyControl\_Update Request to UE-PCF; 3. UE-PCF sends Npcf\_UEPolicyControl\_Update Response to SM-PCF; 4. SM-PCF sends Npcf\_SMPolicyControl\_Update Response to SMF+PGW-C. + +**Figure 6.33.2.5-1: SM Policy and UE Policy Association update after 5GS to EPS mobility** + +1. When the SMF receives the UE Policy Container or URSP Provisioning Support Indication in EPS, it initiates SM Policy Association Modification procedure by sending Npcf\_SMPolicyControl\_Update request to SM-PCF including UE-PCF ID, the UE Policy Container. +2. Based on the UE-PCF ID, the SM-PCF knows it's a request for establishing UE Policy Association with UE-PCF. The SM-PCF sends a Npcf\_UEPolicyControl\_Update request to UE-PCF including the UE Policy Container to modify the UE Policy Association for the UE. +3. From the Indication of MME Created UE Policy Container, the UE-PCF knows it's an MME initiated UE Policy Association update procedure after mobility from 5GS to EPS and updates the UE Policy Association with SM-PCF. For any subsequent URSP update, the UE-PCF contacts with SM-PCF. The UE-PCF responds to SM-PCF with Npcf\_UEPolicyControl\_Update Response. +4. The SM-PCF responds to SMF with Npcf\_SMPolicyControl\_Update Response. + +### 6.33.2.6 UE Policy Association handling after EPS to 5GS mobility + +When the UE moves from EPS to 5GS, UE Policy Association Establishment procedure will be initiated. When UE-PCF detects that a UE Policy Association for the UE exists in EPS, the UE-PCF will initiate the UE Policy Association Termination procedure to terminate the UE Policy Association in EPS. + +## 6.33.3 Impacts on services, entities and interfaces + +N7: Introduce additional IE for the transfer of UE Policy Container between SMF+PGW-C and SM-PCF. + +NAS, S11, S5/S8: Introduce new parameter UE Policy Container in ePCO. + +Impact on SM-PCF: + +- Handling of UE Policy Container within SM Policy Association and UE Policy Association procedures. +- For those cases where PCF initiates the sending of URSP update for a UE in EPC, the triggering of SM Policy Association modification including the new IE with MANAGE UE POLICY COMMAND UPDP message. + +Impact on UE-PCF: + +- Handing the URSP Provisioning Support indication in EPS and stores it into UDR. +- Based on the URSP Provisioning Support indication in EPS, determines whether to provision UE with URSP when the UE is in EPS. +- For those cases where PCF initiates the sending of URSP update for a UE in EPC, the triggering of UE Policy Association modification with SM-PCF. + +#### Impact on SMF+PGW-C: + +- Upon reception of UE Policy Container ePCO in Create Session Request, the SMF+PGW-C forwards the UE Policy Container to the PCF at SM Policy Association establishment. Use the reception of UPDP Container as an additional reason to establish the SM Policy Association, even in case the network configuration for the APN of the PDN connection does not require PCF involvement. +- Upon reception of UE Policy Container from SM-PCF during SM Policy Association initiated by UE-PCF, SMF+PGW-C performs a Bearer Modification Procedure without bearer QoS update including the UE Policy Container ePCO. +- Upon reception of Update Bearer Response from MME including UE Policy Container ePCO, the SMF+PGW-C forwards the received UE Policy Container to PCF. + +#### Impact on UE: + +- During initial attach in EPS, the UE includes UE STATE INDICATION UPDP message into UE Policy Container ePCO in PDN Connectivity Request encapsulated in Attach Request. +- The UE receives MANAGE UE POLICY COMMAND in UE Policy Container ePCO during EPS Bearer Context Request and process it as in 5GC. The UE generates MANAGE UE POLICY COMPLETE UPDP message and send it to the MME encapsulated into a UE Policy Container ePCO in EPS Bearer Context Response. +- The UE also needs to include the URSP Provisioning Support indication in EPS in the UE Policy Container. +- During initial Registration in 5GS, the UE includes the URSP Provisioning Support indication in EPS in both 5GMM Capability and the UE Policy Container. + +#### Impact on AMF: + +- Receives and stores the URSP Provisioning Support indication in EPS as part of the MM Context; +- Sends the UE Policy Association information to MME. + +#### Impact on MME: + +- Receives and stores the UE Policy Association information (i.e. URSP Provisioning Support Indication in EPS, UE-PCF ID selected in 5GS, PCRTs for UE Policy) from AMF; +- Creates a UE Policy Container for UE including only the indication of MME Created UE Policy Container for 5GS to EPS Mobility. +- Includes the UE Policy Container and UE-PCF ID in Modify bearer Request message sent to SMF. + +## 6.34 Solution #34: Provisioning UE policy in EPS via N3IWF + +### 6.34.1 Description + +This solution addresses the Key Issue#3 'Provision consistent URSP to UE across 5GS and EPS'. + +When the UE is in EPS, the UE may use the route selection component (e.g. DNN) in a URSP rule to derive EPS parameters for PDN connection. Note that: + +- a) If UE keeps connectivity with 5GS, then the UE Policy can be updated via 5GS; and +- b) If UE does not need to use URSP in EPS, there is no need for UE to update the policy. + +Thus, the UE updates UE policy in EPS only when it is going to use URSP to derive EPS parameters. + +A solution (i.e. access 5GS via N3IWF) is proposed in this paper, which follows the two principles: + +- minimize the impact on network and UE, reuse the existing mechanism only if the non-3GPP access is supported; and +- no restriction for whether UE has registered in 5GS or not. + +Given that if UE has not registered to 5GS, then the UE does not have any serving NF (e.g. AMF, UDM). In this case, if the 5GS wants to update UE policy for UE in EPS, 5GS needs to temporarily establish 5G connections for UE to update UE policies. On the other hand, if there is no 5GS access, in order to support deliver the URSP rules to the UE in EPS, it has a huge impact to the current design of 5GS. + +Besides, even if the UE has registered in 5GS, whether AMF or UE-PCF would keep the UE context is not ensured. The AMF can implicitly detach the UE upon reachability time-out. + +The registration via untrusted non-3GPP access as described in clause 4.12.2.2 of TS 23.502 [3] and procedure for UE Policy Association Establishment or Modification procedure as described in clauses 4.16.11 or 4.16.12 of TS 23.502 [3] is reused for provisioning UE policy to UE via N3IWF. No extra new signalling or interface is required in this solution. + +This solution relies on the scenario that the operator deploys the N3IWF and the UE can register to N3IWF via non-3GPP access. + +**Editor's note:** It is FFS on how to update the URSP from AM-PCF to UE in case the UE has URSP and doesn't register to 5GS via N3WIF. + +## 6.34.2 Procedures + +![Sequence diagram of UE Policy delivery procedure initiated by the UE in EPS. The diagram shows interactions between UE, eNodeB, MME, Serving GW, SMF + PGW-C, N3IWF, AMF, and PCF (AM-PCF).](3d93290f9e6e9083f27ba5c914fe1e62_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant Serving GW + participant SMF + PGW-C + participant N3IWF + participant AMF + participant PCF (AM-PCF) + + Note over UE, SMF + PGW-C: 1. UE needs to use URSP in EPS to derive EPS parameters. + SMF + PGW-C->>UE: 2. SMF+PGW-C may send N3IWF selection info to the UE during step 1. + Note over UE, PCF (AM-PCF): 3. Registration via untrusted non-3GPP access as described in TS 23.502, clause 4.12.2.2. UE provides PSIs in UE policy container. + UE->>N3IWF: + N3IWF->>AMF: + AMF->>PCF (AM-PCF): + Note over UE, PCF (AM-PCF): 4. Updates UE policy via N3IWF using procedure as described in TS 23.502, cl. 4.16.11 or 4.16.12 for UE Policy Association Establishment or Modification procedure if needed. + PCF (AM-PCF)->>N3IWF: + N3IWF->>AMF: + AMF->>Serving GW: + Serving GW->>MME: + MME->>eNodeB: + eNodeB->>UE: + +``` + +Sequence diagram of UE Policy delivery procedure initiated by the UE in EPS. The diagram shows interactions between UE, eNodeB, MME, Serving GW, SMF + PGW-C, N3IWF, AMF, and PCF (AM-PCF). + +Figure 6.34.2-1: UE Policy delivery procedure initiated by the UE in EPS + +The detailed steps of the procedure are defined below: + +- The UE needs to use URSP in EPS to derive EPS parameters. This may happen when UE is performing an initial attach procedure as described in clause 5.3.2.1 of TS 23.401 [8], interworking procedures from 5GS to EPS as described in clause 4.11 of TS 23.502 [3], or when UE is going to use URSP to derive EPS parameters (e.g. when UE performs the requested PDN connectivity) or when UE is expected to receive the updated URSP rules. + +The UE shall indicate its N1 mode capability, and provides a native 4G-GUTI or a 4G-GUTI mapped from 5G GUTI (indicated as native GUTI), if available, otherwise the IMSI in Attach Request message in its initial attach procedure. + +The HSS selects one of the SMF+PGW-C FQDN for one APN based on operator's policy. The MME may indicate HSS to select a SMF+PGW-C FQDN based on the UE identity (e.g. a 4G-GUTI mapped from 5G GUTI). + +- 2: SMF+PGW-C may send N3IWF selection info to the UE in ePCO during step 1 in using existing messages (e.g. Activate Default EPS Bearer Context message, DOWNLINK NAS TRANSPORT message). The N3IWF selection info contains the following info: + - 1) N3IWF identifier configuration (either FQDN or IP address); and + - 2) Access node selection information consists of a prioritized list of PLMNs for N3IWF selection and an indication that the selection of an N3IWF in a PLMN should be based on Tracking Area Identity FQDN or on Operator Identifier FQDN. +- 3: When the default PDN connection is established, the UE performs Registration via untrusted non-3GPP access as described in clause 4.12.2.2 of TS 23.502 [3]. If PCF determines to update UE policy, it will trigger a UE Policy Association Establishment procedure as described in clause 4.16.11 of TS 23.502 [3] during step 3. +- 4: Any time PCF needs to update the UE policy, it triggers a UE Policy Association Modification as described in clause 4.16.12 of TS 23.502 [3] via N3IWF. + +### 6.34.3 Impacts on services, entities and interfaces + +UE: + +- receive the N3IWF selection info via ePCO. +- UE needs to simultaneously register to 5GS via non-3GPP access through N3IWF and attach to EPS. + +SMF+PGW-C: + +- send the N3IWF selection info via ePCO. + +MME: + +- indicate UDM to select a collocated SMF+PGW-C node. + +## 6.35 Solution #35: Support standardized and operator-specific traffic categories using existing URSP traffic descriptors + +### 6.35.1 Description + +3GPP CT1 has agreed operator specific values for the Connection Capabilities traffic descriptor, with a specific meaning and association to slices only within the MNO domain. + +At the same time, the LS received from GSMA, S2-220365, indicates that the traffic categories agreed are accommodating connectivity requirements that are shared by different applications traffic, being those categories the following: + +- IMS traffic. +- Internet. +- IoT and machine to machine type of traffic. +- On demand downlink streaming. +- On demand uplink streaming. +- Vehicular communications. +- Real time interactive traffic. + +- Unified communications traffic. +- Background traffic. +- Location-based traffic. +- Critical Communications. + +This solution makes use of Connection Capabilities traffic descriptor to support the list of GSMA agreed categories, so that both standard and operator specific categories are dealt with in the same descriptor. + +Although encoding of the Connection Capabilities is a stage 3 decision, the following is an example how to code it: + +``` + +Bits +8 7 6 5 4 3 2 1 +0 0 0 0 0 0 0 1 IMS +0 0 0 0 0 0 1 0 MMS +0 0 0 0 0 0 1 1 SUPL +0 0 0 0 0 1 0 0 Internet +0 0 0 0 0 1 0 1 IoT and M2M traffic +0 0 0 0 0 1 1 0 On demand downlink streaming +0 0 0 0 0 1 1 1 On demand uplink streaming +0 0 0 0 1 0 0 0 Vehicular communications +0 0 0 0 1 0 0 1 Real time interactive traffic +0 0 0 0 1 0 1 0 Unified communications traffic +0 0 0 0 1 0 1 1 Background traffic +0 0 0 0 1 1 0 0 Location-based traffic +0 0 0 0 1 1 0 1 Critical communications +0 0 0 0 1 1 1 0 +To Available for further standard capabilities +0 0 0 1 1 1 1 1 +0 0 1 0 0 0 0 0 +To Operator specific connection capabilities +0 0 1 1 1 1 1 1 +1 0 0 0 0 0 0 0 +To Spare values +1 1 1 1 1 1 1 1 + +``` + +An application can indicate it belonging to a specific category in its request, or for some application implementations the OS may know the application category without explicit signalling from the application. The URSP layer then matches this with the Connection Capability Traffic Descriptor of the URSP rule. + +A single application may indicate different categories in different requests, for example, an application may indicate real time interactive traffic for a gaming session while it may indicate an operator specific capability for a different session. + +Any URSP rule can contain a Connection Capabilities TD (to be matched with the traffic category) together with any other descriptor; e.g. it may include an AppID in addition to the category, or a DNN and a category, or any other descriptor together with the category. The UE shall then need to match all the Traffic Descriptors of the URSP rule. + +A given traffic category can be simultaneously used by multiple applications. + +## 6.35.2 Procedures + +When an application attempts to initiate a session, it may indicate it belongs to a specific traffic category. The traffic category requested by an application may be either a traffic category as agreed by GSMA or a value that is specified by the MNO. + +The URSP layer then uses the application indication of a traffic category, either as the only indication, or accompanied by other information like AppID, DNN, etc, depending on the URSP rules. + +NOTE 1: A traffic category for an application can be accompanied by other indication in scenarios where the operator has agreements with the Application Service Providers to generate the URSP. + +NOTE 2: The use of traffic categories does not preclude that other traffic descriptors are used alone to be matched with a given URSP rule. + +The URSP layer shall then scan the URSP rules configured by the MNO to find the matching rule containing the Connection Capabilities traffic descriptor matching the traffic category indicated by the application/OS layer. If the URSP rules contain a Connection Capability Traffic Descriptor together with another descriptor, the URSP layer shall then need to find the matching rule containing a traffic descriptor listing the same components. + +Operator-specific traffic categories can be supported by defining MNO specific values within the Connection Capabilities Traffic Descriptor. It is assumed that the application and/or OS layer in the UE supports providing MNO specific traffic categories to the URSP layer. The type of MNO traffic category is transparent to the OS layer + +### 6.35.3 Impacts on services, entities and interfaces + +The solution has the following impacts: + +PCF: + +- PCF shall support the new values for the Connection Capabilities traffic descriptor in the URSP rules. + +UE: + +- UE shall support indications of traffic category from the application and match it with the Connection Capabilities component in the Traffic Descriptor provided as part of the URSP rule. + +## 6.X Solution #X: <Solution Title> + +### 6.X.1 Description + +*Editor's note: This clause will describe the solution principles and architecture assumptions for corresponding key issue(s) which should be explicitly stated. (Sub) clause(s) may be added to capture details.* + +### 6.X.2 Procedures + +*Editor's note: This clause describes high-level procedures and information flows for the solution.* + +### 6.X.3 Impacts on services, entities and interfaces + +*Editor's note: This clause captures impacts on existing 3GPP nodes and functional elements.* + +--- + +## 7 Overall Evaluation + +*Editor's note: This clause will provide evaluation of different solutions.* + +### 7.1 Evaluation of solutions to KI#1 + +The KI description listed the following issues to be resolved: + +- Whether and how to support URSP enhancements to support routing of the application traffic with different URSP rules in different PLMNs. +- Whether the HPLMN needs any information from the VPLMN to generate URSP Rules in roaming. If so, which information and how to provide it. + +- How to provide URSP Rules in roaming to the UE. How the HPLMN and VPLMN are involved in such procedure. + +### 7.1.1 How to identify PLMN specific URSP Rules + +This is related to the following description in KI#1: "Whether and how to support URSP enhancements to support routing of the application traffic with different URSP rules in different PLMNs." + +There are different solutions: + +- a) The RSD is extended to include the PLMN ID(s) as validation criteria, a URSP Rule can contain RSD for different PLMN ID(s). (Solution#2, #4 and #29). +- b) The Traffic Descriptor in the URSP Rule is extended to include the PLMN ID.(Solution#3). +- c) The PCF provides a list of PSIs associated to the HPLMN and a list of PSIs associated to each of the VPLMN with roaming agreements. (Solution#6). +- d) No extensions to the RSD or URSP rule. The PCF provides the URSP Rules and RSD components that are applicable in the VPLMN where the UE is registered and removes them when the UE deregisters. (Solution#1, #2, #3 and 5). + +Table 7.1-1: Evaluation of solutions on how to identify VPLMN specific URSP Rules evaluates solutions listing the benefits and drawback, any open issue that makes the solution complete and the system impact. + +**Table 7.1-1: Evaluation of solutions on how to identify VPLMN specific URSP Rules** + +| What is the problem to solve? | How it is solved | Benefit, drawback | System impact | Open issues | Reference | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|--------------------------------| +| KI#1 - Whether and how to support URSP enhancements to support routing of the application traffic with different URSP rules in different PLMNs. | <p>The URSP rules are provided with its associated PLMN ID(s).</p> <p>The UE considers URSP rules associated to the PLMN where the UE is registered</p> | <p>Benefit:<br/>Minimum processing in the UE to find the URSP Rules associated to a PLMN.</p> <p>Drawback:</p> | Impacts the H-PCF and V-PCF and the UE. | How the PLMN IDs are signalled with the Policy Sections is not resolved yet. | Sol#6 option 1 | +| | The PCF provides the list PSIs that apply in the PLMN where the UE is registered. | <p>Benefit:<br/>PCF internal logic only. UE does not need to store the complete list of URSP Rules for any VPLMN, reducing storage.</p> <p>Drawback:<br/>signalling increases when the UE moves between PLMNs, the PCF needs to remove the list of PLMN specific URSP rules and sends URSP rules for another PLMN even some or most of the rules are the same.</p> <p>UE may not have the available URSP to use if the H-PCF does not provision the URSP to UE timely</p> | <p>Based on the existing Release 17 procedures to provision UE policies.</p> <p>UE may need to remove all URSP rules when it registers to a new PLMN except an equivalent PLMN.</p> | None | Sol#1,#3_Option2,5, 6 option 2 | +| | <p>The RSD is extended to include the PLMN ID(s) as validation criteria.</p> <p>The UE considers the RSD if the PLMN identity of the validity condition matches the PLMN identity of the registered PLMN</p> | <p>Benefit: it follows the existing mechanism to provide validation criteria per RSD extends the validity conditions with new conditions.</p> <p>Drawback:</p> | <p>Impacts both the PCF and the UE.</p> <p>Adds the validity conditions per RSD except HPLMN specific RSD in a URSP Rule.</p> | None | Sol#2, #4 and #29 | + +| What is the problem to solve? | How it is solved | Benefit, drawback | System impact | Open issues | Reference | +|-------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------| +| | The Traffic Descriptor in the URSP Rule is extended to include the PLMN ID | <p>Benefit: Reduces processing at the UE to determine the list of VPLMN specific URSP Rules compared with the extensions of the location criteria per RSC.</p> <p>Drawback: Impacts the UE procedure for associating applications to PDU Sessions based on URSP, the UE cannot associate application traffic to a URSP Rule using the PLMN ID.</p> | <p>Extends the Traffic Descriptor in the URSP Rule.</p> <p>Extends the UE procedure to associate application traffic to a PDU Session using the traffic descriptor.</p> <p>Impacts both the PCF and the UE.</p> | None | Sol#3_Option 1 | + +### 7.1.2 Which PLMN determines the VPLMN specific URSP Rules + +- Whether the HPLMN needs any information from the VPLMN to generate URSP Rules in roaming. If so, which information and how to provide it. +- How to provide URSP Rules in roaming to the UE. In particular, how the HPLMN and VPLMN are involved in such procedure. + +This is related to the following description in KI#1: *"How to provide URSP Rules in roaming to the UE. In particular, how the HPLMN and VPLMN are involved in such procedure" and "Whether the HPLMN needs any information from the VPLMN to generate URSP Rules in roaming. If so, which information and how to provide it"*. + +Table 7.1-2: Evaluation of solutions on how to identify VPLMN specific URSP Rules evaluates solutions listing the benefits and drawback, any open issue that makes the solution complete and the system impact. + +**Table 7.1.2-1: Evaluation of solutions on which PLMN determines the VPLMN specific URSP Rules** + +| What is the problem to solve? | How it is solved | Benefit, drawback | System impact | Open issues | Reference | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| KI#1 - Whether the HPLMN needs any information from the VPLMN to generate URSP Rules in roaming. If so, which information and how to provide it. | An AF in the VPLMN provides to the HPLMN how to route the traffic via e.g. DNN in the VPLMN | Benefit:<br><br>Drawback: | <ul style="list-style-type: none"> <li>- UDM to include the DNN, S-NSSAI of the VPLMN in the list of Subscribed S-NSSAIs and to allow the DNN, S-NSSAI to work in LBO mode in the user subscription.</li> <li>- Additional configuration in the HPLMN that needs to define DNN and S-NSSAI of VPLMNs in UDM subscribed values.</li> <li>- An SLA needs to be defined for the AF outside the MNO to find the HPLMN of a SUPI roaming in the VPLMN.</li> </ul> | | Sol.#1,#2, #6 | +| | The V-PCF provides the UE policy assistant information (NOTE 1) of VPLMN to the H-PCF. The H-PCF provides URSP Rules to the UE. | Benefit: VPLMN can aid information to the HPLMN while the HPLMN still decides if the URSP Rule is to be provisioned to the UE.<br><br>Drawback: | Impacts the UE, V-PCF, H-PCF and UDR. | It is unspecified whether the HPLMN sends VPLMN specific URSP Rules to the UE.<br><br>It is not defined how the UE policy assistant information is stored in UDR. | Sol.#3 | +| | The V-PCF generates URSP Rules that are sent to the H-PCF for validation and distribution. The URSP rule contains S-NSSAI of the HPLMN. | Benefit: VPLMN can decide which traffic to route in its PLMN while the HPLMN can check both the roaming agreements and the subscribed values in the RSD.<br><br>Drawback: URSP Rules are for the UE to route application traffic then it has no sense to send the complete URSP rule to the HPLMN. | Impacts V-PCF and H-PCF. | | Sol.#4 | + +| What is the problem to solve? | How it is solved | Benefit, drawback | System impact | Open issues | Reference | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------|-----------| +| | <p>The V-PCF provides service information to the H-PCF.</p> <p>The H-PCF provides URSP Rules with VPLMN values for the DNN and S-NSSAI</p> | <p>Benefit: VPLMN can decide which traffic to route in its PLMN while the HPLMN can check both the roaming agreements and the subscribed values in the RSD.</p> <p>Drawback: -</p> | Impacts UE, H-PCF, V-PCF. | None. | Sol.#5 | + +NOTE 1: UE assistance information contains the mapping from traffic descriptor to DNN, NSSAI, SSC mode, PLMN ID, etc. in VPLMN. + +Table 7.1.2-2 + +| What is the problem to solve? | How it is solved | Benefit, drawback | System impact | Open issues | Reference | +|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------------| +| KI#1 - How to provide URSP Rules in roaming to the UE. In particular, how the HPLMN and VPLMN are involved in such procedure. | <p>Only HPLMN provides URSP Rules to the UE. (NOTE 1)</p> <p>Assumes that the HPLMN trusts the VPLMN to provide URSP Rules unchanged.</p> | <p>Benefit:</p> <p>Drawback:</p> | - UDM to include the DNN, S-NSSAI of the VPLMN in the list of Subscribed S-NSSAIs and to allow the DNN, S-NSSAI to work in LBO mode in the user subscription. | It is not defined how a AF outside the MNO can find the HPLMN of a SUPI roaming in the VPLMN. | Sol.#1,#2, #6 | +| | <p>Both HPLMN and VPLMN provides URSP Rules to the UE. (NOTE 1) (NOTE 2)</p> | <p>Benefit:</p> <p>Drawback:</p> | Impacts the UE, V-PCF, H-PCF and UDR. | | Sol.#3 | + +NOTE 1: Assumes that the HPLMN trusts the VPLMN to provide unchanged URSP Rules to the UE. + +NOTE 2: Assumes that the HPLMN trusts the VPLMN to provide URSP Rules to the UE to route traffic in the VPLMN. + +## 7.2 Evaluation on Solutions for KI#2 + +**Table 7.2-1: Summary of solutions for KI#2** + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #7 | PDU Session establish/mod includes the URSP Rule ID.<br>PCF-SM sends URSP ID and PDU Session Parameters to UE-PCF. UE-PCF checks that the PDU Session Parameters comply with the URSP Rule. | +| Solution #9 | PDU Session establ./mod. includes the URSP Rule Precedence.<br><br>SMF gets the URSP Rule and RSD from the PCF. SMF checks the PDU Session parameters are according to the RSD(s) in the URSP Rule, otherwise it rejects the PDU Session Establishment.<br><br>UPF reports “incorrect application traffic” to SMF and then to PCF. The PCF decides if the UE should be updated to route the application traffic to the “correct” PDU Session. | +| Solution #10 | (with UE assistance)<br>UE notifies PCF-UE the URSP Rules in use and its PDU Session ID(s).<br>The PCF-UE uses the PDU Session to find the SMF for the PDU Session, then asks SMF or the PCF-SM (depending on the option) to check that the PDU Session parameters are the same as in the RSD. The SMF derives the N4 rules to detect the traffic in the TD of the URSP Rule. If no packet is detected, the SMF notifies the PCF-UE via PCF-SM, the PCF-AM sends URSP Rules to the UE to route traffic.<br>SMF maps Application Descriptor, DNN, Domain Descriptor or Connection Capabilities in Traffic Descriptor to IP descriptor to construct 3-IP-tuple in PDR.<br>(without UE assistance)<br>The PCF decides to monitor some URSP Rules provided to a UE, then finds the PDU Sessions established for this UE (DNN, S-NSSAI) contacting UDM, then provides the Traffic Descriptors to be monitored to the SMF. | +| Solution #11 | UE reports the URSP Rules that contain unsupported values to the PCF, then the PCF can adjust URSP Rules including only supported values. | +| Solution #12 | The URSP Rule is extended with URSP ID, the UE includes the URSP Rule ID in the PDU Session Establishment, the PCF generates PCC Rules based on the content of the URSP Rule ID.<br>The UPF reports unmatched traffic to the PCF, the PCF generates URSP Rules for this unmatched traffic. | +| Solution #13 | The UE provides the application identity, that triggers a secondary authentication/authorization to the DN-AAA. Then, once the DN-AAA authorizes the UE to use this application, the SMF establishes the SM Policy Association, provides the URSP Rule precedence to the PCF, then PCC Rules according to the traffic descriptor and the RSD are provided to the SMF. | +| Solution #14 | URSP Rules are extended with an indication of application registration and the identity of the AF is needed. The UE registers to the AF, if the indication is set, the AF authorizes the UE to use this PDU Session. Then if the AF authorizes the use of this PDU Session for this application traffic, then the AF provides an application identity to the UE that sends it in the PDU Session establishment for the SMF to verify.<br>There are still Editor's Notes on the procedure for application registration. | +| Solution #15 | The UE gets the the App_ID from the ASP, the UE provides the App_ID at PDU Session Est/mod. The SMF forwards the App_ID to the PCF that checks if the UE route the App_ID over the correct PDU Session, and if not informs the UE that e.g. S-NSSAI selection rule or Time window was not followed. The PDU Session Est/mod. Is rejected. | +| Solution #30 | The NWDAF requests the UPF to report “unmatched traffic”, then the NWDAF identifies the “unmatched traffic” per S-NSSAI and DNN, compares with the list of allowed services per DNN, S-NSSAI provided by the PCF, then determines which UEs routed the traffic incorrectly, i.e. no according to the URSP Rules sent to the UE and informs the PCF. The PCF updates URSP Rules or provides PCC Rules to e.g., block this traffic. | +| Solution #31 | URSP Rule is extended with the URSP Notification Component that indicates the conditions that trigger reporting to the PCF, such as a) First use of the URSP rule, b) Data sent over given period of time (i.e. periodic reporting) or c) If a certain amount of data has been sent over a specific period of time (i.e. Bandwidth threshold). The reporting to PCF-UE is performed over NAS signalling.<br>The URSP Notification Component applies to both URSP Rules preconfigured in the UE and those provided by the PCF. Possible actions are to reject the UE, if the service requires a SLA such a slice offering GBR services or to trigger SM Policies to accommodate the traffic into the PDU Session at reporting of start of service and ends of service by the UE. | +| Solution #32 | When the TD in the URSP includes a domain description, then the PCC Rules also includes a FQDN in the SDF template to identify the application traffic matching the domain descriptor of the target UE. The SMF generates DNS message handling rules using FQDN-based SDF template. The SMF sends the DNS message handling rule for the EASDF , when detecting the DNS Response, the EASDF notifies the FQDN and resolved address for the FQDN to the SMF. The SMF generates the corresponding N4 rules, e.g. PDR and URR in order for the UPF to report the traffic identified by IP address. | + +Some of the solutions, Sol#12, #13, #31 states that the network ensures that the application traffic sent by the UE in a PDU Session established according to the URSP Rule is treated according to the SLA, e.g. ensuring that the application traffic is routed over a slice for GBR services. For that the PCF provisions PCC Rule to the SMF to provide Session Management policies for the Traffic Descriptors sent in the URSP Rule. This process is applicable to preconfigured URSP Rules and those URSP Rules signalled by the UE as proposed in Sol#31. + +**Observation 1: There is a need to describe how to ensure that the application traffic sent by the UE is routed over a PDU Session according to SLAs, this will be done using PCC Rules.** + +Most of the solution proposes that the UE provides the URSP ID or the URSP Precedence or includes the Application ID in the PDU Session Est. or Modification or in NAS signalling from UE to PCF. This may help the PCF to determine the RSD component that the UE used, potentially validate it and then provide PCC Rules with Session Management policies for the Traffic Descriptors. However, the PCF can also do this determination based on internal logic, such as checking the PDU Session Parameters provided at SM Policy Association Est./Mod. to identify the URSP Rule that the UE enforced. + +**Observation 2: The PCF can determine the URSP Rule used by the UE analysing the PDU Session parameters to find the candidate RSD(s) and the Traffic Descriptors. If the UE sends the URSP Rule ID, this will also be used in the process to identify the URSP Rule.** + +There is a mismatch between the SDF template and the Traffic Descriptor, and then some solutions, such as Sol#10 or Sol#32, proposes to configure the SMF with the mapping of a DNN, Connection Capabilities, Domain descriptor to IP descriptors. This can be a solution for some specific DNNs that the operator knows the Application server IP addresses, however if the DNN allows for multiple applications, the list of IP addresses to configure can be quite dynamic and difficult to configure in the SMF. For the Connection Capabilities, given that this identifies the traffic category, it is also difficult to know all the IP address of possible servers that belong to traffic category. + +**Observation 3: The PCC Rules include the Application ID or the IP/non-IP descriptor in a SDF template.** + +There are solutions that aim to identify the traffic that was routed not following the URSP Rule to the UE, in order to prevent that Sol#11 proposes that the UE reports to the PCF unsupported values, then the PCF provides URSP Rules with only supported values, this will reduce unnecessary signalling and prevent storing in the UE URSP Rules that are not used or even reject it. A solution using NWDAF to try to identify this traffic and possible ask the UE to send it over a different PDU Session is also proposed in Sol#30. + +**Observation 4: NWDAF can be used to identify the unknown traffic, this is also addressed in eNA\_Ph2.** + +**Observation 5: The UE reports unsupported values to the PCF at the time the URSP Rules are provisioned.** + +## 7.3 Evaluation on Solutions for KI#3 + +The Key Issue #3 includes three aspects: + +- #1: Identify the use cases and scenarios where the UE may need URSP that is consistent across 5GC and EPC. +- #2: Study whether there are any issues and gaps in the existing URSP mapping mechanism described in clause 5.17.1.2 of TS 23.501 [2], if so, identify them and propose solutions. +- #3: Whether, when and how to provision the URSP to UE when served by the EPC and ANDSF is not deployed in the network. For the Rel-15 UEs not supporting the URSP mapping in EPS, whether the URSP updating/provisioning to such UEs in EPS should be supported. + +For bullet #2, there is only one solution (Solution#17) on the table. For this solution, there is very restricted applicability for the dynamic mapping. EPS only supports SSC mode 1; APN is always equivalent to DNN; The mapping to PDN connection need to follow what 5GS has; and S-NSSAI is not applicable in EPS. For Multi-Access preference, Time window, Location criteria, they are already setting as "not applicable in EPS". The only two parameters that may have different mapping settings are Access Type preference and Non-seamless Offload indication. However, there was no identified scenario that requiring setting a value dynamically and differently from the 5G URSP RSD. + +The advantages in adopting Sol#17 are that there are certain aspects in the URSP that are currently only applicable to 5GS due to the static mapping make the URSPs (RSDs) invalid in EPS. For example: a rule that has an S-NSSAI in its + +RSD will simply be considered invalid in EPS by the UE as S-NSSAI is not applicable in EPS. With Sol#17 S-NSSAI parameter of the RDS can be simply set as "to be ignored in EPS" and hence the rule will be applied identically to EPS. This will ensure URSP rule consistency. + +The additional advantage of adopting Sol #17 is that we can enable support of certain parameters that currently are not supported in EPS. For example, in FS\_eIMS5G2 it is discussed that S-NSSAI may be used in EPS to indicate the IMS slice to be used. + +For bullet #1 and #3, there are 6 solutions (Solution#16, #18, #19, #20, #33, #34) in total, but solution #18, #19 and #20 have been covered in the consolidated solution #33 (for PCRT handling, #20 is covered by #16), so only three solutions (Sol#16, #33, #34) should be evaluated. + +Solution #34 proposes to provision the URSP to UE in EPS by registering the UE to 5GC via E-UTRAN with N3IWF, which relies on the deployment of N3IWF in 5GC and UE triggering the registration. There are some aspects unclear for this solution: + +- If the URSP update happens before the UE triggers the URSP provisioning request, how does UE-PCF update the URSP rule to UE? +- Accessing to 5GC via N3IWF was defined to use non-3GPP access, while this proposal uses the 3GPP access (E-UTRAN), which was never studied in early releases and may have significant architecture change. +- The design requires the UE to do dual registration to both EPS and 5GS, it's very questionable in real deployment. + +However, Sol #34 has many advantages over Sol#16, #33 and the rest of the solutions that are proposing similar mechanisms. Sol #34 has minimum impact on the network as network operators need to only deploy N3IWF (if not already deployed). There is also minimal impact on the UE to support registering to 5GC via N3IWF using a PDN connection in the EPC as underlay. + +Based on above analysis, it's proposed not to proceed with Solution#34. + +For Solution#16 and #33, the major parts of the two solutions are same (i.e. using ePCO for URSP Delivery in EPS, relying on UE-PCF to terminate the UE Policy Association during 5GS to EPS mobility, UE indicating the URSP Delivery Support indication in UE Policy Container in Registration Request in 5GS) but with following difference: + +- Sol#33 requires UE to indicate URSP Support Indication in EPS in the ePCO carried in PDN Connectivity Request message. During mobility from 5GS to EPS with N26, +- Sol#33 doesn't require AMF to initiate to terminate the UE Policy Association with UE-PCF, the UE Policy Association can be terminated by UE-PCF after the UE Policy Association is updated by SM-PCF in EPS for the UE, while this solution would require the AMF to be able to differentiate the UE supporting URSP delivery in EPS or not, which means the UE needs to report its capability of URSP Delivery Support Indication in EPS in the MM Capability in Registration Request. Sol#16 doesn't require AMF to initiate to terminate the UE Policy Association with UE-PCF either, but it further proposes the AMF to indicate to UE-PCF to delay the UE Policy Association termination for a configured period, the UE-PCF will remove the UE Policy Association either after the configured period or after receiving the UE Policy Association establishment request from SM-PCF for this UE. +- In Sol#16, AMF doesn't provide any new information to MME and let SM-PCF determine whether the UE supports URSP delivery in EPC by checking UE context policy control subscription information in UDR. In solution#33, by providing the UE Policy Association information (i.e. URSP Provisioning Support Indication in EPS, UE-PCF ID in 5GS, PCRTs) to MME by AMF, the MME can determine to create a UE Policy Container only including the indication of MME Created UE Policy Container for 5GS to EPS Mobility, based on this indication, the UE-PCF knows it's an MME initiated UE Policy Association update procedure and updates the UE Policy Association with SM-PCF and terminates the UE Policy Association with AMF for this UE. Based on the UE-PCF ID, the SM-PCF knows to select the same UE-PCF serving the UE in 5GS. In order to avoid impact to MME, Sol #16 proposed mechanism can be used as a way forward. + +For Solution#16 and #33, however there are many drawbacks and technically unclear. For example: + +- +- It is also not clear what happens if the UE is Dual registered e.g. with a N3IWF and thus already having an UE PCF. + +Based on above analysis on Sol #16 and Sol #33, both solutions work from technical viewpoint to address bullet #1 and #3 for KI #3. + +**Conclusion Proposal #1:** The ePCO based URSP delivery to UE in EPS is selected as baseline mechanism for normative work. + +**Conclusion Proposal #2:** In order to avoid unnecessary signalling overload for the purpose of delivery URSP to pre-Rel-18 UEs in EPS, the UE needs to indicate the URSP Delivery Support Indication in EPS in the UE Policy **Container to UE-PCF in EPS and 5GS.** + +**Conclusion Proposal #3:** During 5GS to EPS mobility with N26, the AMF doesn't initiate the UE Policy Association termination procedure, instead the AMF will request the UE-PCF to delay the termination of UE Policy Association for a configured period. The UE-PCF can initiate the UE Policy Association Termination procedure either after it receives the UE Policy Association Establishment from SM-PCF or after the configured period. + +**Conclusion Proposal #4:** AMF doesn't provide any new information to MME during 5GS to EPS mobility with N26, the SM-PCF determines whether the UE supports URSP delivery in EPS by checking UE context policy control subscription information in UDR. The SM-PCF discovers the address of UE-PCF serving the UE by querying BSF. The UE-PCF 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 handover"). + +**Conclusion Proposal #5:** When the UE is attached to EPS, the SM-PCF can retrieve the PCRTs for UE Policy from UE-PCF and subscribe to the applicable PCRTs in EPC to SMF+PGW-C. + +## 7.4 Evaluation on Solutions for KI#4 + +Solutions for Key issue #4 address different approaches to support traffic categories in the traffic descriptor of URSP. + +The investigations were to consider several main aspects: + +1. Definition of traffic categories +2. How to support standard and operator specific traffic categories, +3. Whether the current URSP design can be used to support the standard and operator specific traffic categories. If not, how to support traffic category in the traffic descriptor of a URSP rule. + +The first aspect has been addressed basically by the GSMA, by defining categories considering application traffic characteristics and based on latency, unidirectional or bidirectional bandwidth requirements, availability requirements and particular priorities over specific QoS components (e.g. loss, jitter.). The following table summarises the evaluation of each solution considering how those address the support of traffic category in the current URSP design, or support traffic category in the traffic descriptor of a URSP rule. It also adds advantages and disadvantages seen relevant for the conclusion phase. + +**Table 7.4-1** + +| Solution | Reuse current URSP design | URSP TD to support Traffic Category | Number of categories | Advantages | Disadvantages | +|----------|---------------------------|-------------------------------------------------------------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| #21 | Yes | Option 1 - DNN<br>Option 2 – AppId and fixed value to OS Id | Variable | <ul style="list-style-type: none"> <li>- Reuses URSP design although re-interpreting some component types.</li> </ul> | <ul style="list-style-type: none"> <li>- DNN has a very different meaning from network perspective.</li> <li>- DNNs need to be coded on a per application basis.</li> <li>- It requires network and subscriber configuration to change the DNN=traffic category to a real DNN.</li> <li>- AppId has also different meaning from the network perspective as well as the OS Id and requires Application and OS adaptation.</li> <li>- It disables the use of real App IDs.</li> </ul> | +| #22 | No | New TD | No assumption | | <ul style="list-style-type: none"> <li>- It requires additional rules to be sent to the terminal as UE policy.</li> <li>- Need to redesign the URSP format to define new component type in the TD.</li> <li>- The applications to be categorized and the type of traffic by those applications need to be known in advance by the operator making difficult to properly categorize all applications used by a UE.</li> </ul> | +| #23 | No | New TD | Max. 256 (According to an example in TR) | <ul style="list-style-type: none"> <li>- Can be used with other TDs for more granularity (e.g. for enterprise).</li> <li>- Not many values to be assumed as the example, however, no concern on backward-compatibility if encoding changes from the assumption.</li> </ul> | <ul style="list-style-type: none"> <li>- Need to redesign the URSP format to define new component type in the TD.</li> <li>- Current implementations of URSP rules need to be updated.</li> </ul> | + +| | | | | | | +|-----|-----|--------------------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| #24 | No | New component in URSP or new components type in the TD | No Assumption | | <ul style="list-style-type: none"> <li>- It is unclear how a TD to TC mapping is supposed to work in the UE.</li> <li>- Need to redesign the URSP rule format to define new component in addition to the TD and list of RSD or to define a new component type in the TDs.</li> <li>- It adds unnecessary complexity in the PCF to design mappings between TDs and TCs and between TCs and RSDs. If PCF can know the TDs, the traffic categories are irrelevant.</li> <li>- Current implementations of URSP rules need to be updated</li> </ul> | +| #25 | Yes | App ID | Variable | <ul style="list-style-type: none"> <li>- Reuses URSP design although re-interpreting the AppID component type.</li> </ul> | <ul style="list-style-type: none"> <li>- App ID has different meaning from the network, application and OS perspective</li> <li>- It disables the use of real App IDs</li> <li>- It requires mapping of (real) AppID to TC at application client level, OS or URSP level in the UE. It is unclear which layer would make the mapping.</li> <li>- It requires the operator to know which applications should map to which category.</li> </ul> | +| #26 | No | New TD | No Assumption | <ul style="list-style-type: none"> <li>- Can be used with other TDs for more granularity (e.g. for enterprise).</li> </ul> | <ul style="list-style-type: none"> <li>- Need to redesign the URSP format to define new component type in the TD.</li> <li>- Current implementations of URSP rules need to be updated.</li> </ul> | +| #35 | Yes | Connection Capabilities | Max. 256 | <ul style="list-style-type: none"> <li>- Reuses URSP design and concept</li> <li>- No impact on the network equipment signaling.</li> <li>- In line with Rel-17 updates of URSP for operator specific capabilities.</li> <li>- Can be used with other TDs for more granularity (e.g. for enterprise).</li> </ul> | <ul style="list-style-type: none"> <li>- Current length of Connection Capabilities is 1 octet.</li> </ul> | + +## 8 Conclusions + +Editor's note: This clause will list conclusions that have been agreed during the course of the study item activities. + +## 8.1 Conclusions on KI#1 + +### 8.1.1 General + +The following definitions will be included as part of the normative work on URSP Rules in roaming: + +**VPLMN specific URSP Rules:** A VPLMN specific URSP Rule is applicable when the UE is registered in the VPLMN or its equivalent VPLMN only. VPLMN specific URSP rules are provided from the HPLMN and contains, based on agreements with VPLMN, HPLMN values for Network Slice Selection Policies and DNN Selection Policies. When provided, the Time and Location criteria in each of the RSD contain VPLMN values.. It is provided to the UE to route traffic on a PDU Session to a SMF and UPF in the VPLMN. + +VPLMN configuration is used to ensure that the local VPLMN values are used when a PDU Session is established for a roaming UE. + +When the UE sends a PDU Session Establishment the HPLMN values that are included in the S-NSSAI and DNN may need to be translated to VPLMN values to be able to select a SMF at the VPLMN. This means that the AMF may select a local DNN that is used to select a SMF in the VPLMN. How the AMF selects a local DNN is to be decided during normative phase. The AMF also sends the local DNN, if decided, as "Selected DNN" to the SMF, while the DNN requested by the UE is sent as "Requested DNN". + +The VPLMN provides the service parameters to HPLMN for HPLMN to generate the VPLMN specific URSP rules. The H-PCF creates VPLMN specific URSP rules corresponding to different VPLMN. The H-PCF may provide the VPLMN specific URSP rules to the UE. This can be triggered by the UE's registration in the VPLMN or it can happen before UE roams into the VPLMN. The URSP Rules received by UE in VPLMN are only applicable when the UE is registered in that VPLMN or its equivalent VPLMNs. If the UE does not find a match using the URSP rules associated with the VPLMN ID or equivalent VPLMN ID, it uses the URSP rules associated with the HPLMN. + +NOTE: The PCF may provide VPLMN specific URSP rules based on existing PCRT report from PCF such as PLMN Change or other triggers. + +### 8.1.2 Conclusions on the how to identify PLMN specific URSP Rules + +To enable the PCF to provide and the UE to identify the PLMN specific URSP Rules, the following conclusion principles apply: + +- VPLMN ID is provided to UE along with the URSP. +- The PCF provides to UE a list of PSIs associated to the HPLMN ID and a list of PSIs associated to each VPLMN ID with roaming agreements (following the principles of Solution #6). + +### 8.1.3 Conclusions on which PLMN determines the VPLMN specific URSP Rules + +The scenario where the network provides the UE with URSP rules applicable in the VPLMN It is proposed to adopt the following interim conclusion principles: + +- The H-PCF provides VPLMN specific URSP Rules to the UE. +- The H-PCF generates VPLMN specific URSP rules by taking Service Parameters from V-PCF or the V-AF into account. + - The Service Parameters provided by the V-AF are either provided to: + - V-NEF and stored in V-UDR so that the V-PCF can obtain the Service Parameters from V-UDR. + - H-NEF and stored in the H-UDR. H-PCF retrieves the service parameters directly from the H-UDR. + - The Service Parameters are AF guidance for URSP Rule determination for subscribers of a certain PLMN. + +### 8.1.4 Conclusions on Re-evaluation Triggers + +Upon PLMN change, the UE (re-)evaluates URSP rules. + +## 8.2 Conclusion on KI#2 + +New Analytics ID will be discussed to be supported by the NWDAF to monitor the traffic in one or multiple PDU Session for statistics of URSP enforcement. The analytics request includes the expected traffic according to provisioned URSP rules via the S-NSSAI/DNN. Consumer of new analytic ID can be a PCF. A PCF that provisions URSP rule for a UE may use the NWDAF output to determine updated URSP rules for UE(s). + +NOTE: Further details on the new analytic ID will be determined during the normative phase. + +The process to generate URSP Rules to the UE and corresponding PCC rules for the traffic matching the Traffic Description in the URSP Rule does not require the UE to send the URSP ID or the App ID. The PCF for the UE can derive the candidate RSD components using the PDU Session parameters sent by the UE, if no URSP Rule ID or App ID is sent as defined in Sol#9. + +During UE registration procedure, the UE should indicate the capability of reporting URSP rule enforcement based on UE configuration to network and the 5GC indicates to the UE to report URSP rule enforcement to network, and if the UE URSP rule includes Connection Capabilities contained in the TD (see clause 6.6.2.1 of TS 23.503 [4]), when newly-appeared application traffic is matched to the TD during URSP evaluation, the UE reports the Connection Capabilities contained in the TD, which will be included in the PDU Session Establishment or Modification (i.e. when the URSP rule is matched), then to the PCF for the PDU Session and to PCF for the UE. The UE does not report information to the 5GC when a "match-all" URSP rule is enforced. No service degradation for legacy UEs shall result from this functionality in Rel-18. + +NOTE 2: Traffic categories will be further discussed during the normative phase. + +NOTE 3: By including Connection capabilities, the network indicates to the UE for which URSP rule enforcement in UE should be reported. It will waste UE resource to report all of the URSP rule enforcement to network side including the uninterested URSP rule enforcement. + +NOTE 4: UE reporting the enforced URSP rule information in PDU Session Establishment/Modification can significantly increase the amount of signalling in the network. Limiting the signalling impact of usage of using PDU Session Modification while keeping functionality is a matter of operational trade-off, e.g. UE reporting can be limited to specific application traffic on specific UEs. The mentioned aspects in this NOTE requiring normative work will be limited to minor modifications of existing solutions. + +NOTE 5: PDU Session Modification Accept/Reject, PDU Session Establishment Accept/Reject messages will not be impacted. + +NOTE 6: If SA WG3 feedbacks that it sees an issue with privacy and that it cannot be solved, work on UE assistance won't proceed. Feedback has been asked from SA WG3 and will be included regarding the following aspects: + +- Whether SA WG3 sees an issue with privacy regarding the UE sending information to the 5GC via NAS to identify an enforced URSP rule +- Whether SA WG3 see an issue with user consent regarding the UE sending information to the 5GC via NAS to identify an enforced URSP rule that SA2 would need to consider and if yes, whether SA WG2 is correct to assume that details regarding user consent would fall under the scope of SA WG3 (e.g. FS\_ UC3S\_Ph2) + +The PCF for the UE knows the list of URSP Rules sent to the UE and its RSDs, this allows the PCF for the UE to check the PDU Session parameters and request the PCF for the PDU Session to generate PCC Rules to apply policies for a PDU Session established with preconfigured URSP Rules. This is defined in Sol#32. + +The PCF for the PDU Session provisions PCC rules to the SMF that includes in the SDF template based on the Application identifier, or the IP/non-IP Flow descriptions as defined in the TD of the URSP Rule. For example, the mapping of other TD such as DNN, Connection Capabilities and Domain Descriptors can be done for certain cases such as specific DNNs using local configuration in the SMF, and the Connection Capability that contains a traffic category + +can be mapped in some cases into the Application Identifier (e.g. Connection Capability=IMS assumes IMS application identifier). + +Already existing mechanisms, which do not require additional normative work, can be used and are not precluded, e.g. so that the PCF can provide SDF Templates in PCC rules which correspond to traffic that is not expected to occur in a PDU session, so that if the UPF detects such traffic, the PCF for a PDU Session gets notified from the SMF and can then notify the PCF for a UE about the detected traffic and the relevant parameters of the PDU Session. Based on this information, the PCF for a UE can adjust the URSP rules. + +NOTE 7: Exposure of UPF events towards NWDAF is part of UPEAS. + +## 8.3 Conclusion on KI#3: + +- The ePCO based URSP delivery to UE in EPS is selected as baseline mechanism for normative work. +- In order to avoid unnecessary signalling overload for the purpose of delivery URSP to pre-Rel-18 UEs in EPS, the UE needs to indicate the URSP Provisioning Support Indication in EPS in the UE Policy Container to UE-PCF in 5GS. +- During 5GS to EPS mobility with N26, the AMF doesn't initiate the UE Policy Association termination procedure, instead the AMF will request the UE-PCF to delay the termination of UE Policy Association for a configured period. The UE-PCF can initiate the UE Policy Association Termination procedure either after it receives the UE Policy Association Establishment from SM-PCF or after the configured period. The mobility procedure from 5GS to EPC described in clause 6.16.2.3.3 is selected as the baseline procedure for 5GS to EPS mobility with N26. +- AMF doesn't provide any new information to MME during 5GS to EPS mobility with N26, the SM-PCF determines whether the UE supports URSP delivery in EPS by checking UE context policy control subscription information in UDR. The SM-PCF discovers the address of UE-PCF serving the UE by querying BSF. The UE-PCF 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 handover"). +- When the UE is attached to EPS, the SM-PCF can retrieve the PCRTs for UE Policy from UE-PCF and subscribe to the applicable PCRTs in EPC to SMF+PGW-C. +- When the UE returns from EPS to 5GS, the old UE policy association in EPS should be terminated after the new UE policy association established in 5GS. +- When the UE does Initial Attach to EPC, in the default PDN connection is requested to established, the UE includes the UE Policy Container ePCO in PDN Connectivity Request encapsulated in Attach Request; otherwise, the UE will include the UE Policy Container ePCO in the PDN Connectivity Request during the first request for PDN connectivity as described (i.e. as described in Sol#16). The PDN Connection used by UE and SMF/PGW-C to convey UE Policy Container ePCO shall be kept when the UE is in the CONNECTED mode. +- The PCF triggers the re-evaluation of applicable URSPs for the UE and determines an update of URSP is needed for the UE when an event as described in clause 6.16.11 happens in PCF. The PCF selects one of the PDN connection/PDU sessions associated to EPC for the delivery of the URSP update. Then the PCF generates the corresponding UPDP message MANAGE UE POLICY COMMAND in a similar way than it is done in 5GC and then includes the message into a new IE for sending it to the SMF over N7, then further to UE as described in clause 6.16.2.2. + +NOTE: How to discover the same PCF for UE Policy serving the UE in both EPS and 5GS will be determined in normative phase. + +## 8.4 Conclusion on KI#4 + +The following principles are proposed to be used for conclusion: + +- a) Application in the UE may select a standardized traffic category and informs the lower layer (e.g., OS layer). MNOs should not be assumed to assign the traffic category used by all the specific applications in a UE: + +- i. Some implementations may rely on OS to assign the traffic category. +- b) For standardized and operator-specific traffic categories, how this is selected by the application is out of scope of this specification. +- c) Traffic categories are independent of the Operating System. This allows operators to define operator-specific traffic categories and permit applications setting and classifying the traffic according to categories. +- d) Implementation details on applications indicating a particular traffic category to the OS and/or URSP layer are outside the scope of this work. +- e) The existing traffic descriptors shall not modify their definition or use due to the use of traffic categories. +- f) Traffic categories shall be able to be used together with any other traffic descriptor in the same URSP rule, and traffic must match to all TDs (an AND function and not OR function) to trigger the URSP rule processing as described in current TS 23.503 [4]. +- g) The existing TD component types should be able to be reused either alone or in combination with other TD component types as a way to implicitly determining the category of an application. +- h) The URSP design should be able to associate traffic categories to slices in such a way that it is possible to address large enough operator-specific categories required by operator scenarios, e.g. the length of the component type to accommodate the traffic category to be 2 or more octets. +- Solution #35 is recommended for normative work to use Connection Capability in order to support standardized and operator-specific traffic categories in URSP. Stage 3 should consider extending the length of the Connection Capabilities component type of the URSP TD so as to secure enough number of traffic categories. + +NOTE: Besides the standardized traffic category defined by GSMA, additional traffic categories may be defined by 3GPP. This may be defined/discussed during stage 3. + +SA WG2 recommends stage-3 normative work to proceed based on the above principles. + +## Annex A: Change history + +| Change history | | | | | | | | +|----------------|------------|------------|----|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149e | S2-2200665 | - | - | - | First Skeleton TR | 0.0.0 | +| 2022-03 | SA2#149e | - | - | - | - | Implement following approved papers at SA2#149e: S2-2200665, S2-2200662, S2-2200663, S2-2201362, S2-2201363, S2-2201364, S2-2201858. | 0.1.0 | +| 2022-04 | SA2#150e | - | - | - | - | Implement following approved papers at SA2#150e: S2-2203610, S2-2203609, S2-2202476, S2-2202557, S2-2203112, S2-2203594, S2-2203113, S2-2203114, S2-2203115, S2-2202475, S2-2203116, S2-2203117, S2-2203118, S2-2203119, S2-2203120, S2-2203121, S2-2202452, S2-2203122, S2-2203123, S2-2203124, S2-2203125, S2-2203126, S2-2203127, S2-2203128, S2-2202701, S2-2203129. | 0.2.0 | +| 2022-05 | SA2#151e | - | - | - | - | Implement editorial changes and following approved papers at SA2#151e:<br>S2-2203893, S2-2204821, S2-2204822, S2-2204823, S2-2204824, S2-2204405, S2-2204461, S2-2204825, S2-2204826, S2-2204496, S2-2204827, S2-2204828, S2-2204193, S2-2204829, S2-2204830, S2-2204831, S2-2204417, S2-2204832, S2-2204833, S2-2204834, S2-2203892, S2-2204835, S2-2204836, S2-2204837, S2-2204839, S2-2204653, S2-2204840 | 0.3.0 | +| 2022-09 | SA2#152e | - | - | - | - | Implement editorial changes and following approved papers at SA2#152e:<br>S2-2205528, S2-2207499, S2-2206834, S2-2207500, S2-2207501, S2-2205569, S2-2207502, S2-2205669, S2-2206402, S2-2206833, S2-2206837, S2-2205530, S2-2207503, S2-2206923, S2-2207883, S2-2205518, S2-2206253, S2-2206307, S2-2207504 | 0.4.0 | +| 2022-09 | SA#97-e | SP-220832 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.0.0 | +| 2022-10 | SA2#153e | - | - | - | - | Implement editorial changes and following approved papers at SA2#153e:<br>S2-2209321, S2-2209322, S2-2209323, S2-2209324, S2-2209325, S2-2209326, S2-2209328, S2-2209946, S2-2208172 | 1.1.0 | +| 2022-11 | SA#98-e | SP-221107 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.2.0 | +| 2023-01 | SA2#154AHE | - | - | - | - | Implement following approved papers at SA2#154AHE:<br>S2-2301616, S2-2301617, S2-2301618, S2-2301619, S2-2301485 | 1.3.0 | +| 2023-03 | SA#99 | SP-230086 | - | - | - | MCC editorial update for presentation to TSG SA 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/23958/raw.md b/raw/rel-18/23_series/23958/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..97eddd2311ac27712183e866ece0f23b61a5face --- /dev/null +++ b/raw/rel-18/23_series/23958/raw.md @@ -0,0 +1,615 @@ + + +# 3GPP TR 23.958 V18.0.0 (2023-12) --- + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Edge Application Standards in 3GPP and Alignment with External Organizations; (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring a stylized '5G' in black with three green curved lines above the '5'. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal icon below the 'G'. Below 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 + +--- + +<http://www.3gpp.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. + +© 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 ..... | 4 | +| Introduction ..... | 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 Related work in other SDOs ..... | 8 | +| 4.1 General ..... | 8 | +| 4.2 GSMA OPG ..... | 8 | +| 4.3 ETSI ISG MEC ..... | 8 | +| 5 Alignment of EDGEAPP with ETSI MEC ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Relationship between EDGEAPP and ETSI MEC architectures ..... | 10 | +| 5.3 EDGE-3 and Mp1 reference points..... | 11 | +| 5.3.1 EASProfile and AppInfo ..... | 11 | +| 5.4 EDGE-9 and Mp3 reference points..... | 12 | +| 5.5 CAPIF and MEC service API management..... | 13 | +| 5.6 Support for Federation ..... | 13 | +| 5.6.1 EDGEAPP ..... | 13 | +| 5.6.2 ETSI MEC ..... | 13 | +| 6 Alignment of EDGEAPP with GSMA OP ..... | 13 | +| 6.1 General ..... | 13 | +| 6.2 Relationship between EDGEAPP architecture and GSMA OPG reference architecture ..... | 13 | +| 7 Deployment Considerations..... | 14 | +| 7.1 General ..... | 14 | +| 7.2 Deployment option of EDGEAPP and ETSI MEC using CAPIF..... | 15 | +| 8 Conclusions..... | 17 | +| <b>Annex A: Mapping roles between EDGEAPP architecture and GSMA OPG architecture.....</b> | <b>19</b> | +| <b>Annex B(informative): Change history .....</b> | <b>21</b> | + +# --- 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 + +| | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <b>might</b> | 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 | +| <b>might not</b> | 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: + +| | | +|---------------|-----------------------------------------------------------------------------------| +| <b>is</b> | (or any other verb in the indicative mood) indicates a statement of fact | +| <b>is not</b> | (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 + +This TR provides recommendations on alignment and deployment aspects of EDGEAPP with ETSI MEC and GSMA Operator Platform (OP). + +# --- 1 Scope + +This TR provides the recommendations for the alignment of EDGEAPP architecture with ETSI MEC reference architecture and GSMA Operator Platform (OP) for the industry stakeholders. + +This document provides recommendations of using specifications from 3GPP, ETSI ISG MEC and GSMA OPG to deploy an aligned edge system. + +The present document is based on 3GPP TS 23.558 [2]. + +# --- 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.558: "Architecture for enabling Edge Applications". +- [3] GSMA PRD OPG.02 - "Operator Platform Telco Edge Requirements Version 5.0", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/07/OPG.02-v5.0-Operator-Platform-Requirements-and-Architecture.pdf>. +- [4] ETSI GS MEC 003 (V3.1.1), "Multi-access Edge Computing (MEC); Framework and Reference Architecture". +- [5] ETSI GS MEC 011 (V3.1.1), "Multi-access Edge Computing (MEC); Edge Platform Application Enablement ". +- [6] ETSI GS MEC 040 (V3.1.1), "Multi-access Edge Computing (MEC); Federation enablement APIs ". +- [7] ETSI GS MEC 021 (V2.2.1), "Multi-access Edge Computing (MEC); Application Mobility Service API". +- [8] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management". +- [9] ETSI GS MEC 010-2 (V2.2.1), "Multi-access Edge Computing (MEC); MEC Management; Part 2: Application lifecycle, rules and requirements management". +- [10] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs ". +- [11] ETSI GR MEC 031 (V3.1.1), "Multi-access Edge Computing (MEC); MEC 5G Integration ". +- [12] GSMA PRD OPG.03 - "Southbound Interface Network Resources APIs Version 3.0 ", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/07/OPG.03-v3.0-Southbound-Interface-Network-Resources-APIs.pdf>. +- [13] GSMA PRD OPG.04 - "East-Westbound Interface APIs Version 3.0 ", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/07/OPG.04-v3.0-GSMA-Operator-Platform-Group-East-Westbound-Interface-APIs-Version-3.0.pdf>. + +- [14] GSMA PRD OPG.05 - "User-Network Interface APIs Version 1.0 ", <https://www.gsma.com/futurenetworks/wp-content/uploads/2023/03/GSMA-Operator-Platform-Group-User-Network-Interface-APIs-v1.pdf>. +- [15] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". +- [16] ETSI White Paper #36 – "Harmonizing standards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications", [https://www.etsi.org/images/files/ETSIWhitePapers/ETSI\\_wp36\\_Harmonizing-standards-for-edge-computing.pdf](https://www.etsi.org/images/files/ETSIWhitePapers/ETSI_wp36_Harmonizing-standards-for-edge-computing.pdf). +- [17] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management". + +# --- 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: + +| | | +|----------|---------------| +| <symbol> | <Explanation> | +|----------|---------------| + +## 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]. + +| | | +|-------|-------------------------------------------------| +| AC | Application Client | +| AEF | API Exposing Function | +| AF | Application Function | +| AMF | API Management Function | +| API | Application Program Interface | +| APF | API Publishing Function | +| AS | Application Server | +| CAPIF | Common API Framework | +| CCF | CAPIF Core Function | +| CER | Capabilities Exposure Role | +| EAS | Edge Application Server | +| ECS | Edge Configuration Server | +| ECSP | Edge Computing Service Provider | +| EDN | Edge Data Network | +| EEC | Edge Enabler Client | +| EEL | Edge Enabler layer | +| EES | Edge Enabler Server | +| ETSI | European Telecommunications Standards Institute | +| MEC | Multi-access Edge Computing | +| MEP | MEC Platform | +| NaaS | Network-as-a-Service | +| NSaaS | Network Slice-as-a-Service | +| OP | Operator Platform | +| OPG | Operator Platform Group | + +| | | +|--------|----------------------------------------| +| SBI-NR | Southbound Interface-Network Resources | +| SNMP | Stand-Alone Non-Public Network | +| SRM | Service Resource Manager | +| UC | User Client | +| UNI | User-to-Network Interface | + +# --- 4 Related work in other SDOs + +## 4.1 General + +This section provides an overview on the existing work in GSMA and ETSI MEC relevant to the EDGEAPP architecture describing the OP roles, existing mapping and alignment aspects provided by GSMA OP and ETSI MEC in clause 4.2 and clause 4.3 respectively. + +## 4.2 GSMA OPG + +The Operator Platform (OP) as defined by GSMA OPG in GSMA PRD OPG.02 [3], guides the industry to define a common solution for exposing network capabilities and edge compute resources to enterprise customers and developers allowing monetization of those capabilities. The technical requirements, functional blocks and interfaces characteristics of such a generic platform to facilitate access to the Edge Cloud capability of an operator or federation of operators and their partners are provided in GSMA PRD OPG.02 [3]. GSMA PRD OPG.02 [3] also provides mapping of these requirements and architectures to the specifications from certain SDOs. + +The integration of OP with the mobile network takes place using the Southbound Interface-Network Resources (SBI-NR) through the set of APIs specified in GSMA PRD OPG.03 [12] which is linked to the corresponding 3GPP-defined APIs. GSMA PRD OPG.04 [13] specifies the set of APIs for the interactions/operations over the East/West Bound Interface (E/WBI), which enables an OP to share network and edge capabilities with other OP(s). The E/WBI interactions enable the management of a federation (i.e. creation/update/removal), management of the application onboarding in the federation, edge node discovery, etc. The APIs for the interactions between OP and the User Client (UC) are provided in GSMA PRD OPG.05 [14]. The interactions between OP and the User Client (UC) are supported by the User-to-Network Interface (UNI), allowing the UC to discover the existence of an Edge Cloud service, to register to the OP's Service Resource Manager (SRM), to trigger the selection of a cloudlet (a point of presence for the Edge Cloud offering a set of resources at a particular location as specified in GSMA PRD OPG.02 [3]) by the OP, to trigger the instantiation of an application instance on the selected cloudlet. + +## 4.3 ETSI ISG MEC + +Figure 4.3-1 shows the MEC reference architecture as specified by ETSI ISG MEC. This reference architecture describes the functional elements that comprise the multi-access edge system and the reference points between them. It consists of MEC host and MEC management system necessary to run MEC Applications within an operator network or a subset of an operator network. + +The MEC platform is the collection of essential functionalities required to run MEC applications on a particular Virtualisation infrastructure and enable them to provide and consume MEC services. + +MEC applications are instantiated on the Virtualisation infrastructure of the MEC host based on configuration or requests validated by the MEC management. An already instantiated MEC application can optionally register with MEC platform. The application registration procedure allows an authorized MEC application instance to provide its information to the MEC platform [5]. + +The Mp1 reference point between the MEC platform and the MEC applications provides service registration, service discovery, and communication support for services. It also provides other functionality such as application availability, session state relocation support procedures, traffic rules and DNS rules activation, access to persistent storage and time of day information, etc. + +The Mp3 reference point between MEC platforms is used for control communication between MEC platforms. + +ETSI ISG MEC also provides Multi-access system reference architecture variants for the deployment in an NFV environment and for MEC federation [4] as shown in Figure 4.3-2. In [6], ETSI ISG MEC specifies "Federation enablement APIs " that enable the shared usage of MEC services and applications across different systems (e.g., MEC system, Cloud system). + +![Figure 4.3-1: Multi-access Edge System reference architecture diagram showing the hierarchy from CFS portal and Device app down to MEC host and Virtualisation infrastructure manager.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +This diagram illustrates the Multi-access Edge System reference architecture. It is divided into two main levels: the **MEC system level** and the **MEC host level**. + +- MEC system level:** + - At the top, the **CFS portal** connects to the **Operations Support System** via the **Mx1** interface. + - A **Device app** connects to a **User app LCM proxy** via the **Mx2** interface. + - The **User app LCM proxy** connects to the **Operations Support System** via the **Mm8** interface and to the **MEC orchestrator** via the **Mm9** interface. + - The **Operations Support System** connects to the **MEC orchestrator** via the **Mm1** interface. +- MEC host level:** + - The **MEC orchestrator** connects to the **MEC platform manager** via the **Mm2** and **Mm3** interfaces. + - The **MEC platform manager** connects to the **Virtualisation infrastructure manager** via the **Mm6** and **Mm4** interfaces. + - The **Virtualisation infrastructure manager** connects to the **MEC host** via the **Mm7** interface. + - The **MEC host** contains a **MEC platform** which includes a **Service registry**, **Traffic rules control**, and **DNS handling** components. + - On the **MEC platform**, there are three **MEC App** instances, one of which is labeled **Service MEC App**. These connect to the **Service registry** via the **Mp1** interface. + - The **MEC platform** also contains a **Data plane** component. + - The **Data plane** connects to the **Virtualisation infrastructure** via the **Mp2** interface. + - An **Other MEC platform** connects to the **MEC host** via the **Mp3** interface. + +Figure 4.3-1: Multi-access Edge System reference architecture diagram showing the hierarchy from CFS portal and Device app down to MEC host and Virtualisation infrastructure manager. + +Figure 4.3-1: Multi-access Edge System reference architecture + +![Figure 4.3-2: Multi-access Edge System reference architecture variant for MEC federation, adding MEC federator components and interfaces (Mfm, Mff) to the architecture.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +This diagram shows a variant of the reference architecture for MEC federation. It builds upon the structure of Figure 4.3-1 with additional components and interfaces: + +- The **MEC orchestrator** now connects to a **MEC federator** via the **Mfm** interface. +- The **MEC federator** contains two sub-components: **MEC federation manager** and **MEC federation broker**. +- The **MEC federator** connects to an **Other MEC federator** via the **Mff** interface. +- The **Other MEC federator** is part of an **Other MEC system**. +- All other interfaces and components remain consistent with Figure 4.3-1. + +Figure 4.3-2: Multi-access Edge System reference architecture variant for MEC federation, adding MEC federator components and interfaces (Mfm, Mff) to the architecture. + +Figure 4.3-2: Multi-access Edge System reference architecture variant for MEC federation + +# 5 Alignment of EDGEAPP with ETSI MEC + +## 5.1 General + +An early effort on alignment between 3GPP EDGEAPP and ETSI MEC was initiated during Rel-17, and a summary is available in a white paper published by ETSI - "Harmonizing standards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications" [16]. + +Clause 5.2 provides the relationship between EDGEAPP and ETSI MEC architectures. Clause 5.3 provides the mapping of EAS Profile and AppInfo to allow application registration across the platforms. Clause 5.4 provides description for EDGE-9 and Mp3 reference points. Clause 5.5 provides the description for CAPIF and MEC service API management. + +## 5.2 Relationship between EDGEAPP and ETSI MEC architectures + +Figure 5.2-1 provides the relationship of ETSI ISG MEC architecture with EDGEAPP architecture. + +![Figure 5.2-1: Relationship between EDGEAPP and ETSI MEC architectures. The diagram shows the interaction between a UE (User Equipment) and a 3GPP Core Network, and an ETSI MEC architecture. The UE contains Application Clients(s) and an Edge Enabler Client (EEC). The 3GPP Core Network contains EAS (Edge Application Server) and MEC Application. The ETSI MEC architecture includes MEC Platform Manager, MEC Orchestrator, MEC Federator, User app LCM proxy, Operation Support System (OSS), Customer Facing Service (CFS) Portal, and Device app. Interfaces are labeled as EDGE-7, EDGE-1, EDGE-2, EDGE-6, EDGE-9/Mp3, EDGE-4, EDGE-8, EDGE-10, Mm5, Mm3, Mm2, Mm1, Mm8, Mm9, Mx1, Mx2, and Mff. A legend indicates that ellipses group two interfaces, EDGE* depicts 3GPP SA6 interfaces, and Mp*, Mx*, Mm* and Mf* depict ETSI MEC interfaces.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +Figure 5.2-1: Relationship between EDGEAPP and ETSI MEC architectures. The diagram shows the interaction between a UE (User Equipment) and a 3GPP Core Network, and an ETSI MEC architecture. The UE contains Application Clients(s) and an Edge Enabler Client (EEC). The 3GPP Core Network contains EAS (Edge Application Server) and MEC Application. The ETSI MEC architecture includes MEC Platform Manager, MEC Orchestrator, MEC Federator, User app LCM proxy, Operation Support System (OSS), Customer Facing Service (CFS) Portal, and Device app. Interfaces are labeled as EDGE-7, EDGE-1, EDGE-2, EDGE-6, EDGE-9/Mp3, EDGE-4, EDGE-8, EDGE-10, Mm5, Mm3, Mm2, Mm1, Mm8, Mm9, Mx1, Mx2, and Mff. A legend indicates that ellipses group two interfaces, EDGE\* depicts 3GPP SA6 interfaces, and Mp\*, Mx\*, Mm\* and Mf\* depict ETSI MEC interfaces. + +**Figure 5.2-1: Relationship between EDGEAPP and ETSI MEC architectures** + +Details about MEC entities (MEC Platform, MEC Application, MEC Platform Manager, MEC Orchestrator, MEC Federator, OSS and CFS) can be found in ETSI GS MEC 003 [4]. + +In ETSI MEC, MEC Applications and MEC Platform can expose services which can include network services, subject to their availability at the core or access network level. + +Both EAS and MEC application are application servers and can provide similar application specific functionalities. EAS utilizes the services of EES as specified in 3GPP TS 23.558 [2] whereas MEC application utilizes the services provided by MEC platform as specified in ETSI GS MEC 003 [4]. The EAS and MEC application can be aligned in an implementation. + +**NOTE 1:** The details of the functionalities of application servers are implementation specific. + +Both EES and MEC platform provide application support capabilities towards the application servers. The EES and MEC platform and their interfaces can be aligned in an implementation. + +The orchestration and management aspects of architecture for enabling edge applications are specified in 3GPP TS 28.538 [8]. + +## 5.3 EDGE-3 and Mp1 reference points + +### 5.3.1 EASProfile and AppInfo + +Both EDGEAPP and ETSI MEC supports registration of EAS and MEC application instance with EES and MEC platform respectively. In order to support MEC application instance registration on EES, it is required that 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 [5] the application registration request must include appName. + +AppInfo is the data type describing the information exchanged by a MEC application instance at registration to a MEC platform. It is defined in clause 7.1.2.6 of ETSI GS MEC 011 [5] and includes appName as a mandatory IE and endpoint as an optional IE. However, endpoint is mandatory when the AppInfo IE isInsByMec is FALSE and, as stated above, would have to be provided for MEC application instance registration to an EES. The isInsByMec IE of the AppInfo, with type Boolean, indicates whether the application instance is instantiated by a MEC management system. The IE appName can be considered equivalent to EAS ID. Furthermore endpoint can be directly mapped to EAS endpoint and that mapping is explicitly stated in note 2 of Table 7.1.2.6-1 of ETSI GS MEC 011 [5]. + +Table 5.3.1-1 provides a mapping of MEC attributes to those in the EAS Profile for MEC application registration with EES. + +**Table 5.3.1-1: Mapping with EASProfile for MEC application registration with EES** + +| Information element | Status/ Cardinality | Description | Mapped with | +|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| EASID | M | The identifier of the EAS | AppInfo<br>>appName | +| 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. | AppInfo<br>>endpoint | +| ACID(s) | O | Identifies the AC(s) that can be served by the EAS | Not available in case of MEC application registration | +| EAS Provider Identifier | O | The identifier of the ASP that provides the EAS. | AppInfo<br>>appProvider | +| EAS Type | O | The category or type of EAS (e.g. V2X) | AppInfo<br>>appCategory | +| EAS description | O | Human-readable description of the EAS | AppD<br>>appDescriptor | +| EAS Schedule | O | The availability schedule of the EAS (e.g. time windows) | Not available in case of MEC application registration | +| 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. | Not available in case of MEC application registration | +| 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 | Not available in case of MEC application registration | + +| | | | | +|-----------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| | | formats in Table 8.2.7-1. | | +| EAS Service KPIs | O | Service characteristics provided by EAS, detailed in Table 8.2.5-1 | Not available in case of MEC application registration | +| EAS service permission level | O | Level of service permissions e.g. trial, gold-class supported by the EAS | Not available in case of MEC application registration | +| EAS Feature(s) | O | Service features e.g. single vs. multi-player gaming service supported by the EAS | Not available in case of MEC application registration | +| 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. | Not available in case of MEC application registration | +| General context holding time duration | O | The time duration 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. | Not available in case of MEC application registration | +| 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 [15]. It is a subset of the DNAI(s) associated with the EDN where the EAS resides. | Not available in case of MEC application registration | +| List of N6 Traffic Routing requirements | O | The N6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI. | Not available in case of MEC application registration | +| 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. | Not available in case of MEC application registration | +| EAS Status | O | The status of the EAS (e.g. enabled, disabled, etc.) | Not available in case of MEC application registration | + +## 5.4 EDGE-9 and Mp3 reference points + +EDGE-9 reference point in EDGEAPP architecture is used to provide target EAS discovery to support ACR in case of mobility of user from one EES to another EES. On the other hand, Mp3 reference point between MEC platforms is used for control communication between MEC platforms [4] with a separate application mobility service [7] being provided in support of mobility of users between MEC hosts within a MEC system. Currently, ETSI MEC has not specified APIs over Mp3. + +## 5.5 CAPIF and MEC service API management + +CAPIF is the Common API Framework for northbound APIs specified in 3GPP TS 23.222 [10]. The Edge Enabler Layer supports CAPIF for northbound API exposure of edge service APIs as specified in 3GPP TS 23.558 [2]. The MEC platform supports CAPIF in the form of MEC service management API as specified in ETSI GS MEC 011 [5]. The CAPIF APIs are similar to the MEC service management APIs and the mapping is described in ETSI GS MEC 011 [5]. + +## 5.6 Support for Federation + +### 5.6.1 EDGEAPP + +EDGE-9 and EDGE-10 reference points are used to support federation functionalities as per clause 8.17 and clause 8.18 of 3GPP TS 23.558 [2]. EDGE-9 reference point in EDGEAPP architecture is used to discover EAS from the EES of the partner ECSP for edge node sharing. EDGE-10 reference point in EDGEAPP architecture is used for ECS registration, ECS discovery via ECS-ER and Service provisioning information retrieval from ECS-ER in order to provide support for roaming, federation and edge node sharing. EDN information is exchanged between ECSs/ECS-ERs using EDGE-10 reference point. + +Further, application life cycle management for federation is specified in 3GPP TS 28.538 [17]. Once application server is instantiated, it registers with EES, which in turn registers with ECS. The EDN information contains EDN connection information, list of EES along with EASIDs, provider's ID, endpoint information and other required details. + +### 5.6.2 ETSI MEC + +The MEC federator (MEF) as described in clause 7.1.9 of ETSI GS MEC 003 [4] enables a MEC federation between MEC systems. Mff reference point is defined between MEFs within the MEC federation for sharing information, such as MEC system information that includes MEC system ID, MEC system name, MEC system provider and MEF endpoint information. The federation enablement service is summarised in clause 5.2.1 of ETSI GS MEC 040 [6] and enables the shared usage of MEC services and applications across different systems. + +# --- 6 Alignment of EDGEAPP with GSMA OP + +## 6.1 General + +Clause 6 describes the alignment between 3GPP EDGEAPP and GSMA OP by illustrating the mapping relationship between 3GPP EDGEAPP architecture and GSMA OP architecture (which includes ECS, EES and Edge management system) as described in clause 6.2. + +## 6.2 Relationship between EDGEAPP architecture and GSMA OPG reference architecture + +Figure 6.2-1 illustrates the relationship between EDGEAPP architecture and GSMA OPG reference architecture [3]. + +![Figure 6.2-1: Relationship between EDGEAPP architecture and GSMA OPG reference architecture. The diagram shows the interaction between a UE, 3GPP CN, and Operator platforms. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP CN is connected to the UE via EDGE-7 and to the Operator platform via EDGE-2 and EDGE-8. The Operator platform contains an Edge Enabler Server(s) and an Edge Configuration Server. The Edge Enabler Server(s) is connected to the UE via EDGE-1 and EDGE-4, and to the 3GPP CN via EDGE-3. The Edge Configuration Server is connected to the UE via EDGE-5 and to the 3GPP CN via EDGE-6. The ECSP Management system is connected to the Edge Enabler Server(s) via EDGE-9 and EDGE-10. The diagram also shows the relationship between the Operator platform and the ECSP Management system via the OP SBI-CR interface.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 6.2-1: Relationship between EDGEAPP architecture and GSMA OPG reference architecture. The diagram shows the interaction between a UE, 3GPP CN, and Operator platforms. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP CN is connected to the UE via EDGE-7 and to the Operator platform via EDGE-2 and EDGE-8. The Operator platform contains an Edge Enabler Server(s) and an Edge Configuration Server. The Edge Enabler Server(s) is connected to the UE via EDGE-1 and EDGE-4, and to the 3GPP CN via EDGE-3. The Edge Configuration Server is connected to the UE via EDGE-5 and to the 3GPP CN via EDGE-6. The ECSP Management system is connected to the Edge Enabler Server(s) via EDGE-9 and EDGE-10. The diagram also shows the relationship between the Operator platform and the ECSP Management system via the OP SBI-CR interface. + +**Figure 6.2-1: Relationship between EDGEAPP architecture and GSMA OPG reference architecture** + +EDGE-1 and EDGE-4 reference points can support similar function(s) as OP's User-Network interface (UNI), providing the Edge Enabler Client (corresponding to Edge/User Client in OP) with the information required to access the edge services. EDGE-1/EDGE-4 neither impact nor overlap with other existing 3GPP interfaces between the UE and the network, catering to the OP's requirements on UNI. + +EDGE-2 and EDGE-8 reference points can support similar function(s) as OP's Southbound interface (SBI), through which the edge enabler layer (corresponding to the operator platform) access the 3GPP network capabilities and services (e.g. SCEF/NEF). Specifically, EDGE-2 and EDGE-8 cater to the requirements of the SBI-NetworkResource interface. ECSP management system as specified in 3GPP TS 28.538 [8] caters to the requirements of OP's SBI-CloudResource interface. + +EDGE-3 reference point can support similar function(s) as OP's Northbound interface (NBI), exposing the capabilities of Edge Enabler Server to the Edge Application Servers (EAS) hosted on the edge. OP's NBI also expands capabilities exposure to ASPs, for example to on-board applications to be deployed as EASs based on specific criteria. + +EDGE-9 and EDGE-10 reference point can support similar function(s) as OP's East/Westbound interface (E/WBI), allowing the edge enabler layer to interact within and beyond its domains e.g., between operator platforms. OP's E/WBI focuses on use cases like user and application roaming or resource sharing across domains. + +# 7 Deployment Considerations + +## 7.1 General + +Figure 7.1-1 shows the EDGEAPP and ETSI MEC aligned Application Server and platform deployment. The depicted Edge platform consists of functionalities provided by both EES and MEC platform. The EES and MEC platform are functionally aligned in the implementation of the Edge platform. The depicted Application Server implements the functionalities of an Edge Application Server or MEC application instance or both. + +![Diagram of EDGEAPP and ETSI MEC aligned Application Server and platform deployment. Two Application Servers (EAS and/or MEC app instance) are connected to Edge platforms via CAPIF-1(e) & CAPIF-2(e) interfaces. The Edge platforms are interconnected via EDGE-9/Mp3 and CAPIF-6(e) interfaces.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates a deployment scenario where two Application Servers (EAS and/or MEC app instance) are connected to Edge platforms. Each Application Server is connected to an Edge platform via a CAPIF-1(e) & CAPIF-2(e) interface, which is also labeled as EDGE-3/Mp1. The two Edge platforms are interconnected via an EDGE-9/Mp3 interface, which is also labeled as CAPIF-6(e). + +Diagram of EDGEAPP and ETSI MEC aligned Application Server and platform deployment. Two Application Servers (EAS and/or MEC app instance) are connected to Edge platforms via CAPIF-1(e) & CAPIF-2(e) interfaces. The Edge platforms are interconnected via EDGE-9/Mp3 and CAPIF-6(e) interfaces. + +**Figure 7.1-1: EDGEAPP and ETSI MEC aligned Application Server and platform deployment.** + +EDGE-3 is provided to Application Servers presenting themselves to the Edge platform as Edge Application Servers. Mp1 is provided for Application Servers presenting themselves to the Edge platform as MEC application instances. + +An Edge platform adopting the CAPIF framework could provide the capabilities offered by EDGE-3 and Mp1 through utilisation of CAPIF-1 (/CAPIF-1e) and CAPIF-2 (/CAPIF-2e) to provide a unified service. For instance, a mapping of the MEC service management API to the 3GPP CAPIF API is presented in Annex B of ETSI GS MEC 011 [5]. + +EDGE-9 and Mp3 provide services required for interconnectivity between Edge platforms. EDGE-9 provides the interconnectivity required by Edge Enabler Servers, whilst Mp3 provides the interconnectivity required by MEC platforms. + +An Edge platform adopting the CAPIF framework could provide the capabilities offered by EDGE-9 and Mp3 through utilisation of CAPIF-6 (/CAPIF-6e) to provide a unified service. + +NOTE: APIs supported over Mp3 have not currently been specified by ETSI MEC. + +Management aspects relating to application server and platform management are captured in 3GPP TS 28.538 [8] (EDGEAPP entity specific) and ETSI GS MEC 010-2 [9] (MEC entity specific), where the commonality is that both specify ETSI NFV MANO for performing lifecycle management functions. Management related interfaces are not depicted in Figure 7.1-1. + +## 7.2 Deployment option of EDGEAPP and ETSI MEC using CAPIF + +3GPP provides a framework for supporting common capabilities for northbound APIs (e.g., onboarding, authentication, authorization, discovery, auditing, etc.) through the common API framework (CAPIF) as specified in 3GPP TS 23.222 [10]. The functional model of CAPIF enables an API invoker to access (and invoke) service APIs and supports API exposing functions in publishing the API towards the API invokers. To enable the common supporting capabilities among API invokers and API providers, the CCF is introduced as the functional entity in charge of, among other tasks, authenticating an API invoker, providing authorization for the API invoker prior to accessing the service API, publishing, storing, and supporting the discovery of service APIs information, etc. + +As from Annex A in TS 23.558 [2], an EAS may assume the role of: + +- API invoker: for accessing northbound APIs exposed by SCEF/NEF or consuming service APIs offered by other EASs or EES, or +- API provider: exposing its service APIs for consumption by other API invokers, + +whereas the EES may act like AEF and CCF (the latter being dispensable if, e.g., a centralized instance of CCF is available, see Clause A.5.3 in 3GPP TS 23.558 [2]). + +Additionally, as from Annex B in ETSI GR MEC 031 [11], a MEC App may assume the role of: + +- API invoker: for accessing northbound APIs exposed by SCEF/NEF or consuming MEC services advertised by the MEP, or +- API provider: registering (publishing) its service APIs and exposing them for consumption by other API invokers, + +whereas the MEP may assume the role of API provider, CCF, and API invoker. A MEC service produced by a MEC App or MEP can be mapped into the API provider domain in CAPIF. + +Since the different functional entities of both EDGEAPP and ETSI MEC may assume several roles, the number of scenario combinations is high. Therefore, rather than providing an exhaustive study of possible CAPIF-based deployments, some generic scenarios are presented in Figure 7.2-1. + +In Figure 7.2-1, it is assumed that: + +- Edge Platforms (e.g., complying with MEC platform and/or EDGEAPP) can co-exist in the network within the same PLMN trust domain, +- API invokers want to access MEC services, or API invokers want to consume EDGEAPP services, +- Extensible transport for service invocations (Different protocol and data formats including REST-HTTP are supported) is used. + +![Figure 7.2-1: Illustration of deployment option using CAPIF. The diagram shows a central (API invoker) e.g., EAS/MEC App at the top. Below it, two Edge platforms are shown. The left Edge platform contains CCF 1, which manages Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to EAS (Edge App Server) via CAPIF-3, CAPIF-4, and CAPIF-5. The right Edge platform contains CCF 2, which manages MEC Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to MEC App via CAPIF-2, CAPIF-3, CAPIF-4, and CAPIF-5. Both CCF 1 and CCF 2 connect to the central API invoker via CAPIF-2 and CAPIF-1. CCF 1 and CCF 2 are also connected via CAPIF-6. The entire system is within a PLMN trust domain.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Figure 7.2-1: Illustration of deployment option using CAPIF. The diagram shows a central (API invoker) e.g., EAS/MEC App at the top. Below it, two Edge platforms are shown. The left Edge platform contains CCF 1, which manages Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to EAS (Edge App Server) via CAPIF-3, CAPIF-4, and CAPIF-5. The right Edge platform contains CCF 2, which manages MEC Service APIs (API exposing, API publishing, API management) and CAPIF APIs. It connects to MEC App via CAPIF-2, CAPIF-3, CAPIF-4, and CAPIF-5. Both CCF 1 and CCF 2 connect to the central API invoker via CAPIF-2 and CAPIF-1. CCF 1 and CCF 2 are also connected via CAPIF-6. The entire system is within a PLMN trust domain. + +**Figure 7.2-1: Illustration of deployment option using CAPIF** + +On the left-hand side of Figure 7.2-1, the Edge Platform implements CCF 1 to manage the Service APIs exposed by EAS and EES. EAS implements the API Provider domain functions to expose EAS Service APIs to EASs (and ETSI MEC Applications acting as API invokers). The Edge Platform implements API Provider domain functions to expose EES Service APIs (e.g., UE location API, AC information exposure API, etc.) to API invokers (e.g., EASs, ETSI MEC Applications). + +On the right-hand side of Figure 7.2-1, the Edge Platform implements an instance of CCF (i.e., CCF 2) to manage the MEC Services exposed by MEP and MEC App. Both MEP and MEC App implement API Provider domain functions to expose MEC Services via CAPIF-2. + +CCF 1 and CCF 2 interact via CAPIF-6 reference point, which supports publishing the service APIs information and discovering the service APIs information on both platforms. The CCF 1 and the CCF 2 publish the service API provided by its connected API exposing function(s) and obtains the service API information provided by other CCF. + +An API invoker (e.g., EAS or MEC App) connected to the any of the CCF can discover and invoke service APIs provided by the API exposing function connected to the other CCF. + +In Figure 7.2-2, another possible deployment scenario (out-of-many) is illustrated in which: + +- Two ECSPs are present with different trust domains, +- A PLMN operator (or SNPN provider) deploys API provider functions via the NEF to expose northbound APIs, as illustrated in Section B.2.2.3 in 3GPP TS 23.222 [10], +- An API invoker wants to access MEC services or EES services or wants to consume network capabilities, + +Extensible for service invocations (Different protocol and data formats including REST-HTTP are supported) transport is used. + +![Figure 7.2-2: Illustration of deployment MEC using CAPIF across several trust domains. The diagram shows two Edge Service Providers (ECSP #1 and ECSP #2) connected via a central API invoker (MEC App). ECSP #1 contains an Edge platform with Service APIs, CAPIF APIs, and EAS Service APIs, connected to EDGE-3 and EDGE-9. ECSP #2 contains an Edge platform with MEC Service APIs, CAPIF APIs, and Service APIs, connected to EDGE-2 and EDGE-9. The API invoker connects to ECSP #1 via CAPIF-2e and to ECSP #2 via CAPIF-1e and CAPIF-2e. The NEF - 5GS is shown within the PLMN/SNPN trust domain, connected to EDGE-2 via CAPIF-7e.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +The diagram illustrates a deployment scenario for MEC using CAPIF across multiple trust domains. At the top, an (API invoker) MEC App is shown. It has connections to two Edge Service Providers (ECSPs). ECSP #1 is on the left and contains an 'Edge platform' box. Inside this box, there are three groups: 'Service APIs' (with API exposing, publishing, and management functions), 'CAPIF APIs' (containing 'CCF 1'), and 'EAS Service APIs' (with API exposing, publishing, and management functions). This platform is connected to 'EDGE-3' and 'EDGE-9'. ECSP #2 is on the right and also contains an 'Edge platform' box. Inside, there are 'MEC Service APIs' (with API exposing, publishing, and management functions, connected to a 'MEC App'), 'CAPIF APIs' (containing 'CCF 2'), and 'Service APIs' (with API exposing, publishing, and management functions). This platform is connected to 'EDGE-2' and 'EDGE-9'. The API invoker connects to ECSP #1 via 'CAPIF-2e' and to ECSP #2 via 'CAPIF-1e' and 'CAPIF-2e'. Reference points 'Mp1' and 'Mp3' are indicated. Below ECSP #1, 'EDGE-2' is connected to a 'NEF - 5GS' box. The NEF contains 'Service APIs' (with API exposing, publishing, and management functions) and is connected to 'EDGE-2' via 'CAPIF-7e'. A vertical double-headed arrow labeled 'PLMN/SNPN trust domain' spans the NEF and EDGE-2 area. + +Figure 7.2-2: Illustration of deployment MEC using CAPIF across several trust domains. The diagram shows two Edge Service Providers (ECSP #1 and ECSP #2) connected via a central API invoker (MEC App). ECSP #1 contains an Edge platform with Service APIs, CAPIF APIs, and EAS Service APIs, connected to EDGE-3 and EDGE-9. ECSP #2 contains an Edge platform with MEC Service APIs, CAPIF APIs, and Service APIs, connected to EDGE-2 and EDGE-9. The API invoker connects to ECSP #1 via CAPIF-2e and to ECSP #2 via CAPIF-1e and CAPIF-2e. The NEF - 5GS is shown within the PLMN/SNPN trust domain, connected to EDGE-2 via CAPIF-7e. + +**Figure 7.2-2: Illustration of deployment MEC using CAPIF across several trust domains** + +In this scenario, Edge platform deployed by ECSP#1 acts as a proxy for accessing 5GS capabilities, enabling in that manner topology hiding for the API invoker accessing the service APIs from outside the PLMN/SNPN trust domain. + +NOTE: The details about CAPIF-related reference points within the same trust domains have been removed for the sake of readability. + +ECSP#1 applies topology hiding and provides the AEF details of the Edge platform for invocation of NEF services to ECSP#2. The API invoker onboarded on ECSP#2 is able to discover the NEF services offered by ECSP#1 (supported by CAPIF-1 and CAPIF-6e). The API invoker performs API invocation on the AEF in ECSP#1's Edge platform which further forwards or routes the API invocation to the NEF. + +# 8 Conclusions + +The following is the conclusion on the alignment of 3GPP Edge Enabler Layer, ETSI MEC and GSMA OP architectures: + +1. CAPIF framework is aligned between 3GPP EDGEAPP and ETSI MEC architectures. An Edge application acting as a CAPIF API invoker can discover and invoke Edge platform services from 3GPP EDGEAPP, and ETSI MEC. +2. For Alignment of 3GPP EDGEAPP with ETSI MEC: + +- a) EAProfile and AppInfo are mapped for mandatory information elements. The mapping between EAProfile and AppInfo can be used for aligning EES and MEC platform and their interfaces in an implementation. + - b) Using mapping between EAProfile and AppInfo, MEC application instance can register to EES by providing mandatory IEs. + - c) 3GPP EDGEAPP architecture and ETSI MEC architecture are functionally aligned. +3. For Alignment of 3GPP EDGEAPP with GSMA OP: +- a) GSMA OPG specified edge computing related use cases, requirements (e.g. roaming, federation and edge node sharing) for Operator Platform can be realized by 3GPP EDGEAPP. + +# Annex A: Mapping roles between EDGEAPP architecture and GSMA OPG architecture + +GSMA Operator Platform Group has published their edge requirements in Operator Platform Telco Edge Requirements [3]. + +Clause 3 of Operator Platform Telco Edge Requirements [3] provides the OP Roles and Interfaces Reference Architecture. Clause 3.2 of Operator Platform Telco Edge Requirements [3] defines roles along with their key functions. + +**Editor's note:** Inputs from 3GPP SA5 is FFS. Below mapping tables will be updated based on the input received from SA5. + +The three main roles in the GSMA OP architecture and their mapping with EDGEAPP architecture entity is as follows: + +- 1) Capabilities Exposure Role: It enables an Application Provider to operate their applications. Table A-1 shows the scenarios enabled by Capabilities exposure role as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture. + +**Table A-1: Capabilities exposure role** + +| Interface | Scenario | Description | Mapping to 3GPP EDGEAPP | +|-----------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| NBI | Edge Cloud Infrastructure Endpoint Exposure | The Application Provider uses an authenticated and authorized endpoint to carry out scenarios involving application instances on edge clouds; | | +| | Application Onboarding | The Application Provider uses the NBI to provide application images and metadata to the OP Federation Broker/Manager Role | | +| | Application Metadata/Manifest Submission | The Application Provider uses the NBI and the metadata model to submit application metadata to the OP and follows defined procedures to extend the metadata model specification | | +| | Application CI/CD Management DevOps | The Application Provider integrates the CI/CD framework used to create an application with the OP via NBI APIs (which implies an integration between a CI/CD framework and Application Onboarding and Lifecycle Management) | | +| | Application Lifecycle Management | The Application Provider observes and changes the operational state of application instances, including the geographical/network extent of the OP on which application instances may run; | | +| | Application Resource Consumption Monitoring | The Application Provider observes resource consumption of application instances, using the resource data model | | +| | Edge Cloud Resource Catalogue exposure | The Application Provider inventories edge cloud resources nominally available to application instances | | +| | Network Capabilities exposure | The Application Provider inventories network capabilities, like Network Analytics, nominally available to application instances | EES (as per clause 8.7.3) | + +- 2) Service Resource Manager Role: The Service Resource Manager role in the OP is responsible for managing Cloud and Network resources from the Edge Cloud(s) via the SBI and UNI interfaces. Table A-2 shows typical scenarios enabled by the Service Resource Manager role towards the different interfaces as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture. + +**Table A-2: Service Resource Manager Role** + +| Interface | Scenario | Mapping to 3GPP EDGEAPP | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| SBI | Inventory, Allocation and Monitoring of Compute resources from Edge Cloud Infrastructure via the Southbound Interface – Cloud Resources (SBI-CR); | | +| | Orchestration of Application instances on the Edge Cloud Infrastructure via the SBI-CR interface | | +| | Cloud resource reservation managed by the OP | | +| | Configuring UE traffic management policies to accomplish the application's requirements, or the UE's IP address shall be maintained | | +| | Exposure of usage and monitoring information to operator's charging engine via the Southbound Interface – Charging functions (SBI-CHF) to enable operators to charge for the OP's services. | | +| Southbound Interface – Network Resources (SBI-NR) | Fetch Cloudlet locations based on the mobile network data-plane breakout location | | +| | Subscribe and receive notifications on UE Mobility events from the network to assist applications | UE mobility events are exposed by NEF (TS 23.502) and EES and ECS subscribes to receive UE mobility notification to assist applications for ACR | +| | Configure traffic steering in the Mobile Network towards Applications orchestrated in Edge Clouds | NEF exposes TrafficInfluence service (TS 23.502), EES uses the TrafficInfluence service to steer the traffic (related to traffic influence) | +| | Receive statistics/analytics, e.g. to influence Application placement or mobility decisions | | +| | Receive information related to the network capabilities, such as QoS, policy, network information, etc | NEF exposes events related to network capabilities, EES and ECS subscribes to receive network capability related information. | +| UNI | Application Instantiation/Termination, e.g. based on triggers from the UNI | | +| | Application Endpoint exposure towards User Clients (UC) via the UNI | EES (clause 8.4.2 and clause 8.5) | +| | Application Placement decisions, e.g. based on measurements/triggers from the UNI | | + +- 3) Federation Broker and Federation Manager Roles: The Federation Broker and Manager Roles in the OP are responsible for interfacing with other OPs via the East-West Bound Interface. Table A-3 shows typical scenarios enabled by the Federation Broker and Federation Manager Roles as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture. + +**Table A-3: Federation Broker and Federation Manager Roles** + +| Interface | Scenario | Mapping to 3GPP EDGEAPP | +|-----------|--------------------------------------------------------------------------|---------------------------------------------------------------------| +| EWBI | Federation Interconnection Management | | +| | Edge Cloud Resource Exposure and Monitoring towards partner OPs | | +| | Network and Analytics Capabilities Exposure towards partner OPs | | +| | Application Images and Application metadata transfer towards partner OPs | | +| | Application Instantiation/Termination towards partner OPs | | +| | Application Monitoring towards partner OPs | | +| | Edge Cloud Resource Catalogue exposure | EES (Exposing EAS profile) (See NOTE 1) | +| | Service Availability in visited networks | ECS (Table 8.3.3.3-2 and clause 8.17.2.4 of TS 23.558) (See NOTE 2) | + +NOTE 1: Edge Cloud Resource Catalogue may contain information other than EAS profile which is within scope of SA5. +NOTE 2: EASIDs are considered as available services in partner ECSP and are exchanged between ECSs of home ECSP and partner ECSP. + +Based on the mapping tables in this clause, EES and ECS of 3GPP EDGEAPP architecture can be mapped to take responsibilities of the some roles as defined in GSMA OPG reference architecture. + +**Editor's note:** Alignment of EDGEAPP and GSMA OP for ECSP Management System is FFS and requires inputs from SA5. + +# Annex B(informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | SA6#50-e | | | | | TR Initial Version | 0.0.0 | +| 2022-09 | SA6#50-e | | | | | TR Skeleton (as per TR template) | 0.0.1 | +| 2022-09 | SA6#50-e | | | | | Implementation of the following pCRs approved by SA6: S6-222591, S6-222592 | 0.1.0 | +| 2022-10 | SA6#51-e | | | | | Added Introduction through pCR: S6-222662 | 0.2.0 | +| 2023-03 | SA6#53 | | | | | Added background and updated index through pCR: S6-231043 and S6-231078 | 0.3.0 | +| 2023-03 | SA6#53 | | | | | Corrected the mistake in implementing S6-231043 | 0.3.1 | +| 2023-04 | SA6#54-e | | | | | Implemented pCR: S6-231508 | 0.4.0 | +| 2023-08 | SA6#56 | | | | | Implemented pCRs: S6-232648, S6-232370, S6-232651, S6-232649, S6-232471, S6-232664, S6-232473 | 0.6.0 | +| 2023-09 | SA#101 | SP-230986 | | | | Submitted to SA#101 for information | 1.0.0 | +| 2023-10 | SA6#57 | | | | | Implemented pCRs: S6-233419, S6-233341, S6-233404, S6-233343, S6-233344 | 1.1.0 | +| 2023-10 | SA6#57 | | | | | Editorial correction to add missing version v1.0.0 in the present history table | 1.1.1 | +| 2023-11 | SA6#58 | | | | | Implemented pCRs: S6-233988, S6-233960, S6-233990, S6-233991, S6-233490, S6-234032, S6-234099, S6-233997, S6-233998, S6-233698, S6-234066, S6-234070 | 1.2.0 | +| 2023-12 | SA#102 | SP-231538 | | | | Submitted to SA#102 for approval | 2.0.0 | +| 2023-12 | SA#102 | SP-231538 | | | | MCC Editorial update for publication after TSG SA approval (SA#102) | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/27_series/27007/00ba55671b1a33474972d73577000bff_img.jpg b/raw/rel-18/27_series/27007/00ba55671b1a33474972d73577000bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37c50fe5c18187f4c1311433ae0e23ca1444fa49 --- /dev/null +++ b/raw/rel-18/27_series/27007/00ba55671b1a33474972d73577000bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:621a1becb07571e14737b7d4711f29924d10a97504c6aa98d99579446750da1a +size 137221 diff --git a/raw/rel-18/27_series/27007/19d2407a2ba78e0bc5de8db07448b309_img.jpg b/raw/rel-18/27_series/27007/19d2407a2ba78e0bc5de8db07448b309_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25a0a3a85c61c86745dc84426542b91811c18fc6 --- /dev/null +++ b/raw/rel-18/27_series/27007/19d2407a2ba78e0bc5de8db07448b309_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:480df90b3b1714ad9993f5e492251b4a67c325112dae23026b1a1f96e1bc3432 +size 182286 diff --git a/raw/rel-18/27_series/27007/1bc5e91471a7c3accdadb0b5b446e244_img.jpg b/raw/rel-18/27_series/27007/1bc5e91471a7c3accdadb0b5b446e244_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bdf3add7adea0d2053623730ae60598e64e8159 --- /dev/null +++ b/raw/rel-18/27_series/27007/1bc5e91471a7c3accdadb0b5b446e244_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8eec8810b22e3fe2e9f7e3fab2e76b0a11ea20c7d15bf65e34dc6ea7e64859b +size 113952 diff --git a/raw/rel-18/27_series/27007/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/27_series/27007/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09f35f43ecc93a6a417dbdc99480bbae6477b19b --- /dev/null +++ b/raw/rel-18/27_series/27007/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68434a84a22d5b968d5fdaf2fc4bf4e4b55a8a9fc715a44d3f6d5f7464387619 +size 20005 diff --git a/raw/rel-18/27_series/27007/2f903f194dbf70f3aa6c281a6f96db03_img.jpg b/raw/rel-18/27_series/27007/2f903f194dbf70f3aa6c281a6f96db03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a0dfc89be630e00e8e26234421f006b132a13c5 --- /dev/null +++ b/raw/rel-18/27_series/27007/2f903f194dbf70f3aa6c281a6f96db03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab14f993b3af36cc1adefa17288cc2bc118802f22012d845598589b540035551 +size 29595 diff --git a/raw/rel-18/27_series/27007/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/raw/rel-18/27_series/27007/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c92180c061bf62a911a5773279e7d6a8d4c2777 --- /dev/null +++ b/raw/rel-18/27_series/27007/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0732b9342fc8f52a32de963450beb3e81b3d84a2c809f158f06ce05e44cf9254 +size 39905 diff --git a/raw/rel-18/27_series/27007/3a31a89b46f6eed5da9738f05f81441a_img.jpg b/raw/rel-18/27_series/27007/3a31a89b46f6eed5da9738f05f81441a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8c906ac52d0ccc5cd67cd9a74e90b0beb3b4f98 --- /dev/null +++ b/raw/rel-18/27_series/27007/3a31a89b46f6eed5da9738f05f81441a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1d431f6899804e5b994dd8fbdb7284520db7620adc619ba94593e090b14fa0b +size 36641 diff --git a/raw/rel-18/27_series/27007/40b80ef077f6151a9fbb593b8ad4864d_img.jpg b/raw/rel-18/27_series/27007/40b80ef077f6151a9fbb593b8ad4864d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d124bb1e95d3499a109d72ebd6e77dc9d2ef001b --- /dev/null +++ b/raw/rel-18/27_series/27007/40b80ef077f6151a9fbb593b8ad4864d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e3c9d1bd8cf34347b9daf31bd25ce2d8b960d809ca7740889721b47e8aae080 +size 65052 diff --git a/raw/rel-18/27_series/27007/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/27_series/27007/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..196042f134f059d680613738c56174b08854bddd --- /dev/null +++ b/raw/rel-18/27_series/27007/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e52154b80735b7b00b241822c6d25528cbec3034c2e09d4b0edecd0a6fd246d +size 9427 diff --git a/raw/rel-18/27_series/27007/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/27_series/27007/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f1fa7c649bee5d41a573801455addb23ec39bb4 --- /dev/null +++ b/raw/rel-18/27_series/27007/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d2cc7c04487df8e269649ab22ebb2abe543f434c79eef6818310c18c318bf82 +size 5657 diff --git a/raw/rel-18/27_series/27007/85a19ac17d00b360442b597f581b5f83_img.jpg b/raw/rel-18/27_series/27007/85a19ac17d00b360442b597f581b5f83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43c177f76ba0ab0dd74d9e2f34ee4bc0c9970de6 --- /dev/null +++ b/raw/rel-18/27_series/27007/85a19ac17d00b360442b597f581b5f83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5aa5e675eae8e5de8fab3d1e3b05e4bbd72e267837fc3d90622fec84bc5dea8f +size 36047 diff --git a/raw/rel-18/27_series/27007/90ddf538ef276510e2b631f7b96654e6_img.jpg b/raw/rel-18/27_series/27007/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5bd6b621705d21737c31df595b8b71eb9c55b59 --- /dev/null +++ b/raw/rel-18/27_series/27007/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b854079171d1bfe9ebe2615c15cc63bf3272a6750bef5fc13d2964b775add304 +size 30804 diff --git a/raw/rel-18/27_series/27007/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/27_series/27007/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42ca99f7463d8a1dbf83a9dd4c96140a0db9f0fc --- /dev/null +++ b/raw/rel-18/27_series/27007/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c5e28e80a0f78b335b811bab606c95e7991ae0e43e16e8abfbaf0769fcdf248 +size 53173 diff --git a/raw/rel-18/27_series/27007/bb5e4bf4a5eeedff9a7db204a4488e86_img.jpg b/raw/rel-18/27_series/27007/bb5e4bf4a5eeedff9a7db204a4488e86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db8cccc68702be1ebae379fcceb92cc51bfb1b05 --- /dev/null +++ b/raw/rel-18/27_series/27007/bb5e4bf4a5eeedff9a7db204a4488e86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:833dae1af3be22df402e4d3d9c89af67cf3e05af1334c40c1bec00cbe4ea5b89 +size 4823 diff --git a/raw/rel-18/27_series/27007/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/raw/rel-18/27_series/27007/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..910d40d6e1ca2b914b7b9fc7274dfe1115519014 --- /dev/null +++ b/raw/rel-18/27_series/27007/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d65527fce6c8535b62512a3ce8968d6a4e64df44564c4b4e83611c8859367c8 +size 39424 diff --git a/raw/rel-18/27_series/27007/f1091147d93cee4dfa88498610e395a7_img.jpg b/raw/rel-18/27_series/27007/f1091147d93cee4dfa88498610e395a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8b0103ce8539eb97f7ae23e1deaca975e17204b --- /dev/null +++ b/raw/rel-18/27_series/27007/f1091147d93cee4dfa88498610e395a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b470cc04d1cd6e52068ac2be3f2ec6ab4758b88706370b4e900753c7c70f37f8 +size 54108 diff --git a/raw/rel-18/27_series/27007/f260c0f59aedbd9c6658e8ccdd7002d3_img.jpg b/raw/rel-18/27_series/27007/f260c0f59aedbd9c6658e8ccdd7002d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba842f63ae4e462f9abafd91f3efe9521d55570e --- /dev/null +++ b/raw/rel-18/27_series/27007/f260c0f59aedbd9c6658e8ccdd7002d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7cdf1880b2997af29c69768168ebb430c65429092b8b1f632aec987363dde1f +size 6352 diff --git a/raw/rel-18/27_series/27007/raw.md b/raw/rel-18/27_series/27007/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fc80a348ef1ff7d24059b96b627645df65119f75 --- /dev/null +++ b/raw/rel-18/27_series/27007/raw.md @@ -0,0 +1,20990 @@ + + +# 3GPP TS 27.007 V18.5.0 (2023-12) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; AT command set for User Equipment (UE) (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 logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. There is a small red signal wave icon under the 'G'. + +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 + +--- + +<http://www.3gpp.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. + +© 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..... | 11 | +| 1 Scope..... | 11 | +| 2 References..... | 12 | +| 3 Definitions and abbreviations..... | 19 | +| 3.1 Definitions..... | 19 | +| 3.2 Abbreviations..... | 19 | +| 4 AT command syntax..... | 20 | +| 4.0 General..... | 20 | +| 4.1 Command line..... | 21 | +| 4.2 Information responses and result codes..... | 22 | +| 4.3 ITU-T Recommendation V.250 [14] TE-TA interface commands..... | 22 | +| 5 General commands..... | 23 | +| 5.0 General..... | 23 | +| 5.1 Request manufacturer identification +CGMI..... | 23 | +| 5.2 Request model identification +CGMM..... | 23 | +| 5.3 Request revision identification +CGMR..... | 24 | +| 5.4 Request product serial number identification +CGSN..... | 25 | +| 5.5 Select TE character set +CSCS..... | 26 | +| 5.6 Request international mobile subscriber identity +CIMI..... | 27 | +| 5.7 Multiplexing mode +CMUX..... | 28 | +| 5.8 ITU-T Recommendation V.250 [14] generic TA control commands..... | 30 | +| 5.9 PCCA STD-101 [17] select wireless network +WS46..... | 30 | +| 5.10 Request 5G subscription permanent identifier +CSUPI..... | 32 | +| 5.11 Request 5G network specific identifier +CNAI..... | 32 | +| 5.12 Informative examples..... | 33 | +| 6 Call control commands and methods..... | 34 | +| 6.0 General..... | 34 | +| 6.1 Select type of address +CSTA..... | 34 | +| 6.2 ITU-T Recommendation V.250 [14] dial command D..... | 34 | +| 6.3 Direct dialling from phonebooks..... | 35 | +| 6.4 Call mode +CMOD..... | 36 | +| 6.4A Voice call mode +CVMOD..... | 36 | +| 6.5 Hangup call +CHUP..... | 37 | +| 6.6 Alternating mode call control method..... | 38 | +| 6.7 Select bearer service type +CBST..... | 39 | +| 6.8 Radio link protocol +CRLP..... | 42 | +| 6.9 Service reporting control +CR..... | 43 | +| 6.10 Extended error report +CEER..... | 44 | +| 6.11 Cellular result codes +CRC..... | 44 | +| 6.12 HSCSD device parameters +CHSD..... | 46 | +| 6.13 HSCSD transparent call configuration +CHST..... | 47 | +| 6.14 HSCSD non-transparent call configuration +CHSN..... | 47 | +| 6.15 HSCSD current call parameters +CHSC..... | 48 | +| 6.16 HSCSD parameters report +CHSR..... | 49 | +| 6.17 HSCSD automatic user initiated upgrading +CHSU..... | 49 | +| 6.18 HSCSD non-transparent asymmetry configuration +CHSA..... | 50 | +| 6.19 Single numbering scheme +CSNS..... | 51 | +| 6.20 Voice hangup control +CVHU..... | 51 | +| 6.21 CCITT V.120 [36] rate adaption protocol +CV120..... | 52 | +| 6.22 Settings date format +CSDF..... | 53 | +| 6.23 Silence command +CSIL..... | 54 | +| 6.24 Settings time format +CSTF..... | 55 | +| 6.25 ITU-T Recommendation V.250 [14] call control commands..... | 56 | +| 6.26 ITU-T Recommendation V.250 [14] data compression commands..... | 56 | + +| | | | +|------|---------------------------------------------------------------------------------------------------|-----| +| 6.27 | Initiate eCall +CECALL..... | 56 | +| 6.28 | eCall Notification +CECN..... | 57 | +| 6.29 | Informative examples..... | 58 | +| 7 | Network service related commands..... | 59 | +| 7.0 | General..... | 59 | +| 7.1 | Subscriber number +CNUM..... | 59 | +| 7.2 | Network registration +CREG..... | 60 | +| 7.3 | PLMN selection +COPS..... | 63 | +| 7.4 | Facility lock +CLCK..... | 65 | +| 7.5 | Change password +CPWD..... | 67 | +| 7.6 | Calling line identification presentation +CLIP..... | 68 | +| 7.7 | Calling line identification restriction +CLIR..... | 69 | +| 7.8 | Connected line identification presentation +COLP..... | 70 | +| 7.9 | Called line identification presentation +CDIP..... | 71 | +| 7.10 | Closed user group +CCUG..... | 72 | +| 7.11 | Call forwarding number and conditions +CCFC..... | 73 | +| 7.12 | Call waiting +CCWA..... | 74 | +| 7.13 | Call related supplementary services +CHLD..... | 76 | +| 7.14 | Call deflection +CTFR..... | 77 | +| 7.15 | Unstructured supplementary service data +CUSD..... | 78 | +| 7.16 | Advice of charge +CAOC..... | 79 | +| 7.17 | Supplementary service notifications +CSSN..... | 80 | +| 7.18 | List current calls +CLCC..... | 82 | +| 7.19 | Preferred PLMN list +CPOL..... | 84 | +| 7.20 | Selection of preferred PLMN list +CPLS..... | 85 | +| 7.21 | Read operator names +COPN..... | 86 | +| 7.22 | eMLPP priority registration and interrogation +CAEMLPP..... | 86 | +| 7.23 | eMLPP subscriptions +CPPS..... | 87 | +| 7.24 | Fast call setup conditions +CFCS..... | 87 | +| 7.25 | Automatic answer for eMLPP service +CAAP..... | 88 | +| 7.26 | User to user signalling service 1 +CUUS1..... | 89 | +| 7.27 | Preferred network indication +CPNET..... | 90 | +| 7.28 | Preferred network status +CPNSTAT..... | 91 | +| 7.29 | Current packet switched bearer +CPSB..... | 92 | +| 7.30 | Calling name identification presentation +CNAP..... | 93 | +| 7.31 | Connected line identification restriction status +COLR..... | 94 | +| 7.32 | Service specific access control restriction status +CSSAC..... | 95 | +| 7.33 | Network emergency (bearer) services support +CNEM..... | 97 | +| 7.34 | Enhanced closed user group +CECUG..... | 98 | +| 7.35 | Communication forwarding number and conditions with URI support +CCFCU..... | 100 | +| 7.36 | Message waiting indication control +CMWI..... | 101 | +| 7.37 | Session start and stop for MMTEL and SMSoverIP applications +CSCM..... | 102 | +| 7.38 | Power saving mode setting +CPSMS..... | 104 | +| 7.39 | Application Start and Stop indication for applications other than MMTEL and SMSoverIP +CACDC..... | 105 | +| 7.40 | eDRX setting +CEDRXS..... | 106 | +| 7.41 | eDRX read dynamic parameters +CEDRXRDP..... | 107 | +| 7.42 | CIoT optimization configuration +CCIOTOPT..... | 108 | +| 7.43 | CSG selection +CCSGS..... | 110 | +| 7.44 | CAG selection +CCAGS..... | 112 | +| 7.45 | Informative examples..... | 113 | +| 7.46 | Ciphering key request +CCKEYREQ..... | 115 | +| 8 | Mobile termination control and status commands..... | 116 | +| 8.0 | General..... | 116 | +| 8.1 | Phone activity status +CPAS..... | 117 | +| 8.2 | Set phone functionality +CFUN..... | 118 | +| 8.3 | Enter PIN +CPIN..... | 119 | +| 8.4 | Battery charge +CBC..... | 121 | +| 8.5 | Signal quality +CSQ..... | 121 | +| 8.6 | Mobile termination control mode +CMEC..... | 122 | +| 8.7 | Keypad control +CKPD..... | 123 | + +| | | | +|-------|----------------------------------------------------------------------|-----| +| 8.8 | Display control +CDIS..... | 124 | +| 8.9 | Indicator control +CIND..... | 125 | +| 8.10 | Mobile termination event reporting +CMER..... | 126 | +| 8.11 | Select phonebook memory storage +CPBS..... | 129 | +| 8.12 | Read phonebook entries +CPBR..... | 130 | +| 8.13 | Find phonebook entries +CPBF..... | 131 | +| 8.14 | Write phonebook entry +CPBW..... | 134 | +| 8.15 | Clock +CCLK..... | 135 | +| 8.16 | Alarm +CALA..... | 136 | +| 8.17 | Generic SIM access +CSIM..... | 137 | +| 8.18 | Restricted SIM access +CRSM..... | 138 | +| 8.19 | Secure control command +CSCC..... | 139 | +| 8.20 | Alert sound mode +CALM..... | 140 | +| 8.21 | Ringer sound level +CRSL..... | 140 | +| 8.22 | Vibrator mode +CVIB..... | 141 | +| 8.23 | Loudspeaker volume level +CLVL..... | 142 | +| 8.24 | Mute control +CMUT..... | 142 | +| 8.25 | Accumulated call meter +CACM..... | 143 | +| 8.26 | Accumulated call meter maximum +CAMM..... | 143 | +| 8.27 | Price per unit and currency table +CPUC..... | 144 | +| 8.28 | Call meter maximum event +CCWE..... | 144 | +| 8.29 | Power class +CPWC..... | 145 | +| 8.30 | Set language +CLAN..... | 146 | +| 8.31 | Language event +CLAE..... | 147 | +| 8.32 | Set greeting text +CSGT..... | 147 | +| 8.33 | Set voice mail number +CSVM..... | 148 | +| 8.34 | Ring melody control +CRMC..... | 149 | +| 8.35 | Ring melody playback +CRMP..... | 150 | +| 8.36 | Master reset +CMAR..... | 150 | +| 8.37 | List all available AT commands +CLAC..... | 151 | +| 8.38 | Delete alarm +CALD..... | 151 | +| 8.39 | Postpone or dismiss an alarm +CAPD..... | 152 | +| 8.40 | Automatic time zone update +CTZU..... | 152 | +| 8.41 | Time zone reporting +CTZR..... | 153 | +| 8.42 | Enter protocol mode+CPROT..... | 154 | +| 8.43 | Generic UICC logical channel access +CGLA..... | 155 | +| 8.44 | Restricted UICC logical channel access +CRLA..... | 156 | +| 8.45 | Open logical channel +CCHO..... | 158 | +| 8.46 | Close logical channel +CCHC..... | 158 | +| 8.47 | EAP authentication +CEAP..... | 159 | +| 8.48 | EAP retrieve parameters +CERP..... | 161 | +| 8.49 | UICC application discovery +CUAD..... | 161 | +| 8.50 | Mobile originated location request +CMOLR..... | 162 | +| 8.51 | Backlight +CBKLT..... | 166 | +| 8.52 | Command touch screen action +CTSA..... | 167 | +| 8.53 | Command screen orientation +CSO..... | 169 | +| 8.54 | Command screen size +CSS..... | 171 | +| 8.54A | Command display screen boundary +CDSB..... | 172 | +| 8.55 | Positioning control +CPOS..... | 172 | +| 8.56 | Positioning reporting +CPOSR..... | 190 | +| 8.57 | Mobile terminated location request notification +CMTLR..... | 192 | +| 8.58 | Mobile terminated location request disclosure allowance +CMTLRA..... | 193 | +| 8.59 | Battery capacity +CBCAP..... | 193 | +| 8.60 | Battery connection status +CBCON..... | 194 | +| 8.61 | Battery charger status +CBCHG..... | 195 | +| 8.62 | Printing IP address format +CGPIAF..... | 195 | +| 8.63 | IMS single radio voice call continuity +CISRVCC..... | 197 | +| 8.64 | IMS network reporting +CIREP..... | 197 | +| 8.65 | Remaining PIN retries +CPINR..... | 199 | +| 8.66 | Set card slot +CSUS..... | 200 | +| 8.67 | Emergency numbers +CEN..... | 200 | + +| | | | +|-----------|----------------------------------------------------------------------------------|-----| +| 8.68 | Availability for voice calls with IMS +CAVIMS..... | 202 | +| 8.69 | Extended signal quality +CESQ..... | 202 | +| 8.70 | Primary notification event reporting +CPNER..... | 205 | +| 8.71 | IMS registration information +CIREG..... | 206 | +| 8.72 | Availability for SMS using IMS +CASIMS..... | 207 | +| 8.73 | Monitor of current calls +CMCCS..... | 208 | +| 8.74 | List of current calls +CLCCS..... | 214 | +| 8.75 | Supported radio accesses +CSRA..... | 217 | +| 8.76 | Circuit switched fallback +CCSFB..... | 219 | +| 8.77 | Reading coverage enhancement status +CRCES..... | 221 | +| 8.78 | Application level measurement configuration +CAPPLEVMC..... | 222 | +| 8.79 | Application level measurement report +CAPPLEVMR..... | 223 | +| 8.80 | Consent for requesting access to restricted local operator services +CCRLOS..... | 223 | +| 8.81 | EPS fallback status +CEPSFBS..... | 224 | +| 8.82 | Mobile originated location privacy setting +CMOLPS..... | 225 | +| 8.83 | Void..... | 226 | +| 8.84 | Application level measurement configuration for NR +CAPPLEVMCNR..... | 226 | +| 8.85 | Application level measurement report for NR +CAPPLEVMRNR..... | 228 | +| 8.86 | Unavailability Period +CUNPER..... | 229 | +| 8.87 | Discontinuous Coverage +CDISCO..... | 230 | +| 8.88 | Informative examples..... | 231 | +| 8.89 | Signal level enhanced network selection +CSENSE..... | 235 | +| 9 | Mobile termination errors..... | 236 | +| 9.1 | Report mobile termination error +CMEE..... | 236 | +| 9.1A | Report mobile originated location request error +CMOLRE..... | 236 | +| 9.1B | Report network error codes +CNEC..... | 237 | +| 9.2 | Mobile termination error result code +CME ERROR..... | 239 | +| 9.2.0 | General..... | 239 | +| 9.2.1 | General errors..... | 239 | +| 9.2.2 | CS, GPRS, UMTS, EPS and 5GS-related errors..... | 240 | +| 9.2.2.1 | Errors related to a failure to perform an attach..... | 240 | +| 9.2.2.1.1 | Errors for CS, GPRS and UMTS..... | 240 | +| 9.2.2.1.2 | Errors for EPS..... | 241 | +| 9.2.2.1.3 | Errors for 5GS..... | 241 | +| 9.2.2.2 | Errors related to a failure to activate a context..... | 242 | +| 9.2.2.2.1 | Errors for GPRS and UMTS..... | 242 | +| 9.2.2.2.2 | Errors for EPS..... | 244 | +| 9.2.2.2.3 | Errors for 5GS..... | 245 | +| 9.2.2.3 | Void..... | 245 | +| 9.2.2.4 | Void..... | 245 | +| 9.2.3 | VBS, VGCS and eMLPP-related errors..... | 245 | +| 9.3 | Mobile termination error result code +CMOLRE..... | 246 | +| 9.3.1 | General..... | 246 | +| 9.3.2 | Errors..... | 246 | +| 9.4 | Informative examples..... | 246 | +| 10 | Commands for packet domain..... | 247 | +| 10.0 | General..... | 247 | +| 10.1 | Commands specific to MTs supporting the packet domain..... | 247 | +| 10.1.0 | General remark about EPS bearer contexts and PDP contexts..... | 247 | +| 10.1.0.0 | General remark about 5GS PDU sessions and EPS PDN connections..... | 249 | +| 10.1.1 | Define PDP context +CGDCONT..... | 250 | +| 10.1.2 | Define secondary PDP context +CGDSCONT..... | 257 | +| 10.1.3 | Traffic flow template +CGTFT..... | 260 | +| 10.1.4 | Quality of service profile (requested) +CGQREQ..... | 263 | +| 10.1.5 | Quality of service profile (minimum acceptable) +CGQMIN..... | 265 | +| 10.1.6 | 3G quality of service profile (requested) +CGEQREQ..... | 266 | +| 10.1.7 | 3G quality of service profile (minimum acceptable) +CGEQMIN..... | 269 | +| 10.1.8 | 3G quality of service profile (negotiated) +CGEQNEG..... | 273 | +| 10.1.9 | PS attach or detach +CGATT..... | 275 | +| 10.1.10 | PDP context activate or deactivate +CGACT..... | 275 | + +| | | | +|---------|---------------------------------------------------------------------------------------------------|-----| +| 10.1.11 | PDP context modify +CGCMOD..... | 276 | +| 10.1.12 | Enter data state +CGDATA..... | 277 | +| 10.1.13 | Configure local octet stream PAD parameters +CGCLOSP (Obsolete)..... | 279 | +| 10.1.14 | Show PDP address(es) +CGPADDR..... | 279 | +| 10.1.15 | Automatic response to a network request for PDP context activation +CGAUTO..... | 280 | +| 10.1.16 | Manual response to a network request for PDP context activation +CGANS..... | 281 | +| 10.1.17 | GPRS mobile station class +CGCLASS..... | 282 | +| 10.1.18 | Configure local triple-X PAD parameters +CGCLPAD (GPRS only) (Obsolete)..... | 283 | +| 10.1.19 | Packet domain event reporting +CGEREP..... | 283 | +| 10.1.20 | GPRS network registration status +CGREG..... | 288 | +| 10.1.21 | Select service for MO SMS messages +CGSMS..... | 291 | +| 10.1.22 | EPS network registration status +CEREG..... | 292 | +| 10.1.23 | PDP context read dynamic parameters +CGCONTRDP..... | 296 | +| 10.1.24 | Secondary PDP context read dynamic parameters +CGSCONTRDP..... | 300 | +| 10.1.25 | Traffic flow template read dynamic parameters +CGTFTRDP..... | 301 | +| 10.1.26 | Define EPS quality of service +CGEQOS..... | 303 | +| 10.1.27 | EPS quality of service read dynamic parameters +CGEQOSRDP..... | 304 | +| 10.1.28 | UE modes of operation for EPS +CEMODE..... | 306 | +| 10.1.29 | Delete non-active PDP contexts +CGDEL..... | 306 | +| 10.1.30 | Signalling connection status +CSCON..... | 307 | +| 10.1.31 | Define PDP context authentication parameters +CGAUTH..... | 309 | +| 10.1.32 | Initial PDP context activation +CIPCA..... | 310 | +| 10.1.33 | No more PS data +CNMPSD..... | 311 | +| 10.1.34 | UE's usage setting for EPS and 5GS +CEUS..... | 311 | +| 10.1.35 | UE's voice domain preference E-UTRAN +CEVDP..... | 312 | +| 10.1.36 | UE's voice domain preference UTRAN +CVDP..... | 313 | +| 10.1.37 | UE's mobility management IMS voice termination +CMMIVT..... | 313 | +| 10.1.38 | Power preference indication for EPS and 5GS +CEPPI..... | 314 | +| 10.1.39 | WLAN offload assistance data +CWLANOLAD..... | 314 | +| 10.1.40 | WLAN offload cell measurement +CWLANOLCM..... | 317 | +| 10.1.41 | APN back-off timer status reporting +CABTSR..... | 317 | +| 10.1.42 | APN back-off timer read dynamic parameters +CABTRDP..... | 319 | +| 10.1.43 | Sending of originating data via the control plane +CSODCP..... | 320 | +| 10.1.44 | Reporting of terminating data via the control plane +CRTDCP..... | 321 | +| 10.1.45 | APN rate control +CGAPNRC..... | 322 | +| 10.1.46 | PS data off status +CPSDO..... | 323 | +| 10.1.47 | 5GS network registration status +C5GREG..... | 324 | +| 10.1.48 | Bandwidth preference indication +CBPI..... | 327 | +| 10.1.49 | Define 5GS quality of service +C5GQOS..... | 328 | +| 10.1.50 | 5GS quality of service read dynamic parameters +C5GQOSRDP..... | 329 | +| 10.1.51 | Receive UE policy +CRUEPOLICY..... | 331 | +| 10.1.52 | Send UE policy +CSUEPOLICY..... | 331 | +| 10.1.53 | 5GS access selection preference for MO SMS +C5GSMS..... | 332 | +| 10.1.54 | Mobile initiated connection only mode +CMICO..... | 333 | +| 10.1.55 | S-NSSAI based back-off timer status reporting +CSBTSR..... | 335 | +| 10.1.56 | S-NSSAI based back-off timer read dynamic parameters +CSBTRDP..... | 336 | +| 10.1.57 | S-NSSAI and DNN based back-off timer status reporting +CSDBTSR..... | 337 | +| 10.1.58 | S-NSSAI and DNN based back-off timer read dynamic parameters +CSDBTRDP..... | 338 | +| 10.1.59 | 5GS use of SMS over NAS +C5GUSMS..... | 340 | +| 10.1.60 | Request LADN information +CRLADN..... | 341 | +| 10.1.61 | LADN information +CLADN..... | 342 | +| 10.1.62 | 5GS NSSAI setting +C5GNSSAI..... | 344 | +| 10.1.63 | 5GS NSSAI read dynamic parameters +C5GNSSAIRDP..... | 345 | +| 10.1.64 | 5GS Preferred NSSAI +C5GPNSSAI..... | 348 | +| 10.1.65 | Indicating the selected PLMN for access to restricted local operator services (RLOS) +CRLOSP..... | 349 | +| 10.1.66 | Link packet filters +CGLNKPF..... | 350 | +| 10.1.67 | Delete packet filters +CGDELFP..... | 351 | +| 10.1.68 | Bit rate recommendation request +CGBRRREQ..... | 352 | +| 10.1.69 | Bit rate recommendation reporting +CGBRRREP..... | 352 | +| 10.1.70 | 5GS ATSSS Rules read dynamic parameters +C5GATSSSRDP..... | 353 | +| 10.1.71 | 5GS network steering functionalities information read dynamic parameters +C5GNSFIRDP..... | 354 | + +| | | | +|----------|------------------------------------------------------------------------------|-----| +| 10.1.72 | Context State Change Request +CCSTATREQ..... | 354 | +| 10.1.73 | 5G PDU Session Authentication Setting +C5GPDUAUTHS..... | 355 | +| 10.1.74 | 5G PDU Session Authentication Response +C5GPDUAUTHR..... | 356 | +| 10.1.75 | 5GS URSP query +C5GURSPQRY..... | 357 | +| 10.1.76 | NAS connection release +CNASCREL..... | 361 | +| 10.1.77 | Reject paging +CREJPAG..... | 361 | +| 10.1.78 | Paging restrictions +CPAGRES..... | 363 | +| 10.1.79 | Paging timing collision control +CPAGTCC..... | 364 | +| 10.1.80 | DNS server address reporting +CDNSADD..... | 365 | +| 10.1.81 | Access domain selection preference for MO SMS +CADSMS..... | 366 | +| 10.1.82 | 5G ProSe UE-to-network Relay Authentication Setting +C5GPU2NRAUTHS..... | 366 | +| 10.1.83 | 5G ProSe UE-to-network Relay Authentication Response +C5GPU2NRAUTHR..... | 367 | +| 10.1.84 | ECS Configuration information +CECSADDRCONF..... | 368 | +| 10.1.85 | 5GS network registration status over non-3GPP access +C5GREGN3GPP..... | 369 | +| 10.1.86 | 5GS network register or deregister over non-3GPP access +C5GRDN3GPP..... | 370 | +| 10.1.87 | Define MBS session context +CMSCONT..... | 371 | +| 10.1.88 | MBS session read dynamic parameters +CMSRDP ..... | 372 | +| 10.1.89 | MBS session status reporting +CMSSR..... | 373 | +| 10.1.90 | Information for reflective QoS for ESP +CIRQE..... | 374 | +| 10.2 | Modem compatibility commands..... | 377 | +| 10.2.0 | General..... | 377 | +| 10.2.1 | MT originated PDP context activation..... | 377 | +| 10.2.1.0 | General..... | 377 | +| 10.2.1.1 | Request packet domain service 'D'..... | 377 | +| 10.2.1.2 | Request packet domain IP service 'D'..... | 378 | +| 10.2.2 | Network requested PDP context activation..... | 379 | +| 10.2.2.0 | General..... | 379 | +| 10.2.2.1 | Automatic response to a network request for PDP context activation 'S0'..... | 379 | +| 10.2.2.2 | Manual acceptance of a network request for PDP context activation 'A'..... | 379 | +| 10.2.2.3 | Manual rejection of a network request for PDP context activation 'H'..... | 380 | +| 11 | Commands for VGCS and VBS..... | 380 | +| 11.0 | General..... | 380 | +| 11.1 | Commands specific to MTs supporting the VGCS and VBS..... | 380 | +| 11.1.1 | Accept an incoming voice group or voice broadcast call +CAJOIN..... | 380 | +| 11.1.2 | Reject an incoming voice group or voice broadcast call +CAREJ..... | 381 | +| 11.1.3 | Leave an ongoing voice group or voice broadcast call +CAHLD..... | 381 | +| 11.1.4 | Talker access for voice group call +CAPTT..... | 382 | +| 11.1.5 | Voice group call uplink status presentation +CAULEV..... | 383 | +| 11.1.6 | List current voice group and voice broadcast calls +CALCC..... | 383 | +| 11.1.7 | Voice group or voice broadcast call state attribute presentation +CACSP..... | 384 | +| 11.1.8 | NCH support indication +CANCHEV..... | 385 | +| 11.1.9 | Originator to dispatcher information +COTDI..... | 386 | +| 11.1.10 | Short data transmission during ongoing VGCS +CEPTT..... | 387 | +| 11.1.11 | Group Id prefixes capability +CGIPC..... | 388 | +| 11.2 | Modem compatibility commands..... | 388 | +| 11.2.0 | General..... | 388 | +| 11.2.1 | Request VGCS or VBS service 'D'..... | 388 | +| 11.2.2 | Termination of an voice group or voice broadcast call 'H'..... | 389 | +| 11.3.1 | VGCS subscriptions and GId status +CGCS..... | 389 | +| 11.3.2 | VBS subscriptions and GId status +CBCS..... | 390 | +| 11.4 | Informative examples..... | 391 | +| 12 | Commands for USIM application toolkit..... | 391 | +| 12.1 | General..... | 391 | +| 12.2 | Commands specific to MTs supporting USAT..... | 392 | +| 12.2.1 | Read USAT profile +CUSATR..... | 392 | +| 12.2.2 | Write USAT profile +CUSATW..... | 393 | +| 12.2.3 | Profile download upon start-up +CUSATD..... | 394 | +| 12.2.4 | Activate USAT profile +CUSATA..... | 395 | +| 12.2.5 | Send USAT terminal response +CUSATT..... | 396 | +| 12.2.6 | Send USAT envelope command +CUSATE..... | 397 | + +| | | | +|--------|---------------------------------------------------|-----| +| 12.3 | Informative examples..... | 397 | +| 13 | Commands for enhanced support of dialling..... | 399 | +| 13.1 | General..... | 399 | +| 13.2 | Commands for dialling..... | 400 | +| 13.2.1 | Dial URI +CDU..... | 400 | +| 13.2.2 | Dial URI from phonebook +CDUP..... | 402 | +| 13.2.3 | Hangup of current calls +CHCCS..... | 404 | +| 13.2.4 | Define media profile +CDEFMP..... | 405 | +| 13.2.5 | Control and modify media description +CCMMD..... | 406 | +| 13.3 | Informative examples..... | 407 | +| 14 | Commands for eMBMS configuration..... | 411 | +| 14.1 | General..... | 411 | +| 14.2 | Commands specific to eMBMS..... | 412 | +| 14.2.1 | eMBMS configuration in MT +CEMBMSCFG..... | 412 | +| 14.2.2 | eMBMS status reporting in MT +CEMBMSR..... | 412 | +| 14.2.3 | eMBMS service configuration +CEMBMSSRV..... | 414 | +| 14.2.4 | Enter eMBMS data state +CEMBMSDATA..... | 415 | +| 14.2.5 | eMBMS counting procedure +CEMBMSCNT..... | 415 | +| 14.2.6 | eMBMS Service Area Identities +CEMBMSSAI..... | 416 | +| 15 | Commands for UE test functions..... | 417 | +| 15.1 | General..... | 417 | +| 15.2 | Activate test mode +CATM..... | 417 | +| 15.3 | Close UE test loop mode E +CCUTLE..... | 418 | +| 15.4 | UE sidelink packet counter request +CUSPCREQ..... | 420 | +| 15.5 | UTC time reset +CUTCR..... | 421 | +| 15.6 | Channel busy ratio request +CCBRREQ..... | 421 | +| 15.7 | V2X data transmission over PC5 +CV2XDTS..... | 422 | +| 15.8 | SPS assistance information request +CSPSAIR..... | 423 | +| 16 | Commands for VAE layer configuration..... | 424 | +| 16.1 | General..... | 424 | +| 16.2 | Commands specific to VAE layer..... | 424 | +| 16.2.1 | VAE layer configuration in MT +CVAEACT..... | 424 | +| 16.2.2 | VAE layer registration +CVAEREG..... | 425 | +| 17 | Commands for UAE layer configuration..... | 426 | +| 17.1 | General..... | 426 | +| 17.2 | Commands specific to UAE layer..... | 426 | +| 17.2.1 | UAE layer configuration in MT +CUAEACT..... | 426 | +| 17.2.2 | UAE layer registration +CUAEREG..... | 427 | +| 18 | Commands for UAS configuration and operation..... | 428 | +| 18.1 | General..... | 428 | +| 18.2 | Commands specific to UAS services..... | 428 | +| 18.2.1 | UUAA parameter transport +CUUAAPT..... | 428 | +| 18.2.2 | C2 authorization parameter transport +CC2APT..... | 429 | +| 19 | Commands for edge enabling layer operation..... | 430 | +| 19.1 | General..... | 430 | +| 19.2 | Commands specific to edge enabling layer..... | 430 | +| 19.2.1 | Edge-5 EAS discovery +CE5EASD..... | 430 | +| 19.2.2 | Edge-5 ACR trigger request +CE5ACRREQ..... | 431 | +| 19.2.3 | Edge-5 EEC services subscription +CE5EECSRV..... | 432 | +| 19.2.4 | Edge-5 UE ID request +CE5UEIDREQ..... | 434 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|------------| +| <b>Annex A (normative):</b> | <b>Summary of commands from other standards.....</b> | <b>437</b> | +| <b>Annex B (normative):</b> | <b>Summary of result codes.....</b> | <b>439</b> | +| <b>Annex C (informative):</b> | <b>Commands from TIA IS-101.....</b> | <b>442</b> | +| C.1 | Introduction..... | 442 | +| C.2 | Commands..... | 443 | +| C.2.1 | Select mode +FCLASS..... | 443 | +| C.2.2 | Buffer threshold setting +VBT..... | 443 | +| C.2.3 | Calling number ID presentation +VCID..... | 444 | +| C.2.4 | Receive gain selection +VGR..... | 444 | +| C.2.5 | Transmit gain selection +VGT..... | 444 | +| C.2.6 | Initialise voice parameters +VIP..... | 445 | +| C.2.7 | Inactivity timer +VIT..... | 445 | +| C.2.8 | Line selection +VLS..... | 445 | +| C.2.9 | Receive data state +VRX..... | 447 | +| C.2.10 | Select compression method +VSM..... | 447 | +| C.2.11 | DTMF and tone generation +VTS..... | 448 | +| C.2.12 | Tone duration +VTD..... | 448 | +| C.2.13 | Transmit data state +VTX..... | 449 | +| <b>Annex D (informative):</b> | <b>Bibliography.....</b> | <b>450</b> | +| <b>Annex E (informative):</b> | <b>Mobile originated alternating voice/data call example.....</b> | <b>451</b> | +| <b>Annex F (informative):</b> | <b>Mobile terminated voice followed by data call example.....</b> | <b>452</b> | +| <b>Annex G (informative):</b> | <b>Voice call example.....</b> | <b>453</b> | +| <b>Annex H (informative):</b> | <b>Change history.....</b> | <b>454</b> | + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 specifies a profile of AT commands and recommends that this profile be used for controlling Mobile Termination (MT) functions and network services from a Terminal Equipment (TE) through Terminal Adaptor (TA). The command prefix +C is reserved for Digital Cellular in ITU-T Recommendation V.250 [14]. The present document has also the syntax details used to construct extended commands. Commands from ITU-T Recommendation V.250 [14] and existing digital cellular standards (TIA IS-99 [15] and TIA IS-135 [16]) are used whenever applicable. Some of the new commands are defined such way that they can be easily applied to MT of other networks. + +NOTE: The terms GSM and GSM/UMTS are used whenever appropriate for SIM/UICC GSM applications or GSM/UMTS bearer services or to represent specific mobile accesses covered by the present specification. + +ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12] fax AT commands may be used for GSM/UMTS fax transmission from TE. Short Message Service AT commands are defined in 3GPP TS 27.005 [24]. AT commands for packet systems are defined in clause 10 of this specification. The present document assumes an abstract architecture comprising a TE (e.g. a computer) and a MT interfaced by a TA (see figure 1). The span of control of the defined commands should allow handling of any physical implementation that this abstract architecture may lead to: + +- TA, MT and TE as three separate entities; +- TA integrated under the MT cover, and the TE implemented as a separate entity; +- TA integrated under the TE cover, and the MT implemented as a separate entity; and +- TA and MT integrated under the TE cover as a single entity. + +The commands described in the present document may be observed on the link between the TE and the TA. However, most of the commands retrieve information about the MT, not about the TA. + +![Figure 1: Setup diagram showing the interaction between TE, TA, and MT blocks. TE (Terminal Equipment) is connected to USER & APPLICATIONS and sends AT cmds to TA (Terminal Adapter). TA sends responses to TE and MT control to MT (Mobile Terminal). MT sends MT status to TA and network messages to NETWORK.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph LR + TE[TE] <--> |responses| TA[TA] + TE --> |AT cmds| TA + TA --> |MT control| MT[MT] + MT --> |MT status| TA + TE --> |USER & APPLICATIONS| UA[USER & APPLICATIONS] + MT --> |network messages| N[NETWORK] + +``` + +Figure 1: Setup diagram showing the interaction between TE, TA, and MT blocks. TE (Terminal Equipment) is connected to USER & APPLICATIONS and sends AT cmds to TA (Terminal Adapter). TA sends responses to TE and MT control to MT (Mobile Terminal). MT sends MT status to TA and network messages to NETWORK. + +**Figure 1: Setup** + +Interface between TE and TA is intended to operate over existing serial (ITU-T Recommendation V.24) cables, infrared link, and all link types with similar behaviour. For correct operation many of the defined commands require eight bit data and therefore it is recommended that TE-TA link is set to eight bits/ byte mode. (For infrared operation implementation, refer informative references IrDA. For embedding AT commands and data during on-line data state, refer TIA-617/ITU-T V.80.) Interface between TA and MT is dependent on the interface in the MT. + +The functional blocks shown in figure 1, using AT commands, shall follow the principles described in the interactions handling framework 3GPP TS 23.227 [63]. + +## 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 TS 22.002: "Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". +- [2] 3GPP TS 22.003: "Teleservices supported by a GSM Public Land Mobile Network (PLMN)". +- [3] 3GPP TS 22.081: "Line identification supplementary services - Stage 1". +- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". +- [5] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". +- [6] 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1". +- [7] 3GPP TS 23.003: "Numbering, addressing and identification". +- [8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols- Stage 3". +- [9] GSM MoU SE.13, GSM MoU Permanent Reference Document SE.13: "GSM Mobile Network Codes and Names". +- [10] ITU-T Recommendation E.212: "Identification plan for land mobile stations". +- [11] ITU-T Recommendation T.31: "Asynchronous facsimile DCE control, service class 1". + +- [12] ITU-T Recommendation T.32: "Asynchronous facsimile DCE control, service class 2". +- [13] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information exchange". +- [14] ITU-T Recommendation V.250: "Serial asynchronous automatic dialling and control". +- [15] TTA IS-99: "Data Services Option Standard for Wideband Spread Spectrum Digital Cellular System". +- [16] TTA IS-135: "800 MHz Cellular Systems, TDMA Services, Async Data and Fax". +- [17] PCCA STD-101 Data Transmission Systems and Equipment: "Serial Asynchronous Automatic Dialling and Control for Character Mode DCE on Wireless Data Services". +- [18] 3GPP TS 24.022: "Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [19] 3GPP TS 22.030: "Man Machine Interface (MMI) of the Mobile Station (MS)". +- [20] 3GPP TS 45.008: "Radio subsystem link control". +- [21] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". +- [22] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services - Stage 1". +- [23] 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD) - Stage 1". +- [24] 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". +- [25] 3GPP TS 23.038: "Alphabet and language specific information". +- [26] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". +- [27] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1". +- [28] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface". +- [29] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD) - Stage 1". +- [30] 3GPP TS 22.091: "Explicit Call Transfer (ECT) supplementary service - Stage 1". +- [31] 3GPP TS 22.072: "Call Deflection (CD) supplementary service - Stage 1". +- [32] ISO/IEC 10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding. +- [33] 3GPP TS 22.022: "Personalization of GSM Mobile Equipment (ME) Mobile functionality specification". +- [34] 3GPP TS 27.060: "General requirements on Mobile Stations (MS) supporting General Packet Radio Bearer Service (GPRS)". +- [35] Void. +- [36] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [37] Void. +- [38] 3GPP TS 45.005: "Radio transmission and reception". +- [39] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting GPRS and Packet Data Networks (PDN)". + +- [40] 3GPP TS 23.081: "Line identification supplementary services - Stage 2". +- [41] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [42] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [43] Infrared Data Association; Specification of Ir Mobile Communications (IrMC). +- [44] IrDA Object Exchange Protocol. +- [45] 3GPP TS 27.010: "Terminal Equipment to User Equipment (TE-UE) multiplexer protocol User Equipment (UE)". +- [46] 3GPP TS 23.107: "Quality of Service, Concept and Architecture". +- [47] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". +- [48] Void. +- [49] 3GPP TS 43.068: "Voice Group Call service (VGCS) - Stage 2". +- [50] 3GPP TS 43.069: "Voice Broadcast Service (VBS) - Stage 2". +- [51] Void. +- [52] 3GPP TS 44.068: "Voice Group Call service (VGCS) - Stage 3". +- [53] 3GPP TS 44.069: "Voice Broadcast Service (VBS) - Stage 3". +- [54] 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 1". +- [55] 3GPP TS 42.068: "Voice Group Call service (VGCS) - Stage 1". +- [56] 3GPP TS 42.069: "Voice Broadcast Service (VBS) - Stage 1". +- [57] Void. +- [58] 3GPP TS 22.087: "User-to-User Signalling (UUS) - Stage 1". +- [59] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) Application". +- [60] ETSI TS 102 221 "Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 1999)". +- [61] 3GPP TS 44.065: "Mobile Station (MS) – Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDPCP)". +- [62] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP)". +- [63] 3GPP TS 23.227 "Applications and User interaction in the UE-Principles and specific requirements", Release 5. +- [64] Void. +- [65] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics." +- [66] ETSI TS 102 310: "Smart Cards; Extensible Authentication Protocol support in the UICC". +- [67] Void. +- [68] RFC 3748: "Extensible Authentication Protocol (EAP)". +- [69] RFC 3629: "UTF-8, a transformation format of ISO 10646". + +- [70] 3GPP TS 44.318: "Generic Access (GA) to the A/Gb interface; Mobile GA interface layer 3 specification". +- [71] 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". +- [72] 3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA): Overall Description; Stage 2". +- [73] 3GPP TS 25.319: "Enhanced Uplink; Overall Description; Stage 2". +- [74] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [75] 3GPP TS 24.216: "Communication Continuity Management Object (MO)". +- [76] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [77] 3GPP TS 25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN); Stage 2". +- [78] IEC 61162: "Maritime navigation and radio communication equipment and systems – Digital interfaces". +- [79] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC), Radio Resource LCS Protocol (RRLP)". +- [80] 3GPP TS 49.031: "Base Station System Application Part, LCS Extension (BSSAP-LE)". +- [81] Void. +- [82] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access". +- [83] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)". +- [84] Void. +- [85] 3GPP TS 23.203: "Policy and charging control architecture". +- [86] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [87] 3GPP TS 24.173: "IMS multimedia telephony communication service and supplementary services; Stage 3". +- [88] RFC 4291: "IP Version 6 Addressing Architecture". +- [89] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)". +- [90] 3GPP TS 23.221: "Architectural requirements". +- [91] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity". +- [92] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)". +- [93] 3GPP TS 22.096: "Name identification supplementary services - Stage 1". +- [94] 3GPP TS 23.096: "Name identification supplementary services - Stage 2". +- [95] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [96] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [97] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". +- [98] Void. + +- [99] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [100] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [101] 3GPP TS 24.341: "Support of SMS over IP networks". +- [102] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3". +- [103] IETF STD 5: "Internet Protocol". +- [104] IETF STD 51: "The Point-to-Point Protocol (PPP)". +- [105] RFC 1144: "Compressing TCP/IP Headers for Low-Speed Serial Links". +- [106] RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [107] RFC 2507: "IP Header Compression". +- [108] RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed". +- [109] 3GPP TS 24.080: "Mobile radio interface Layer 3 supplementary service specification; Formats and coding". +- [110] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [111] RFC 3261: "SIP: Session Initiation Protocol". +- [112] RFC 3966: "The tel URI for Telephone Numbers". +- [113] RFC 3969: "The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)". +- [114] RFC 5341: "The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry". +- [115] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [116] RFC 2141: "URN Syntax". +- [117] RFC 3406: "Uniform Resource Names (URN) Namespace Definition Mechanisms". +- [118] RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services". +- [119] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [120] 3GPP TS 24.608: "Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [121] 3GPP TS 24.654: "Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification". +- [122] RFC 4715: "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI". +- [123] 3GPP TS 22.093: "Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1". +- [124] 3GPP TS 22.094: "Follow Me service description; Stage 1". +- [125] 3GPP TS 22.097: "Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1". +- [126] 3GPP TS 22.135: "Multicall; Service description; Stage 1". + +- [127] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification". +- [128] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification". +- [129] 3GPP TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [130] 3GPP TS 24.259: "Personal Network Management (PNM)". +- [131] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS". +- [132] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [133] 3GPP TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [134] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [135] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [136] 3GPP TS 24.611: "Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [137] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification". +- [138] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [139] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [140] 3GPP TS 24.642: "Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [141] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem". +- [142] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE)". +- [143] 3GPP TS 25.102: "Multiplexing and channel coding (TDD)". +- [144] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [145] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description". +- [146] 3GPP TS 45.001: "Physical layer on the radio path; General description". +- [147] 3GPP TS 22.101: "Service aspects; Service principles". +- [148] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD); Stage 3". +- [149] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications". +- [150] 3GPP TS 36.443: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2 Application Protocol (M2AP)". + +- [151] Wi-Fi Alliance: "Hotspot 2.0 (Release 2) Technical Specification, version 1.0.0", 2014-08-08. +- [152] IEEE Std 802.11<sup>TM</sup>-2012: "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". +- [153] 3GPP TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)". +- [154] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [155] RFC 4122: "A Universally Unique Identifier (UUID) URN Namespace". +- [156] 3GPP TS 44.018: "GSM/EDGE Radio Resource Control (RRC) protocol". +- [157] CEN EN 15722:2015 (April 2015): "Intelligent transport systems - ESafety - ECall minimum set of data". +- [158] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification". +- [159] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description". +- [160] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [161] 3GPP TS 24.501: "Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [162] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-Connectivity; Stage 2". +- [163] 3GPP TS 24.196: "Enhanced Calling Name (eCNAM)". +- [164] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services". +- [165] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [166] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". +- [167] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements". +- [168] 3GPP TS 24.250: "Protocol for Reliable Data Service between UE and SCEF; Stage 3". +- [169] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [170] 3GPP TS 22.011: "Service accessibility". +- [171] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [172] 3GPP TS 24.486: "Vehicle-to-Everything (V2X) Application Enabler (VAE) layer; Protocol aspects; Stage 3". +- [173] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [174] RFC 3339: "Date and Time on the Internet: Timestamps". +- [175] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3". +- [176] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [177] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting; Stage 3". +- [178] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment". + +- [179] 3GPP TS 38.215: "NR; Physical layer measurements". +- [180] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS)". +- [181] IEEE Std 802.1Q-2018: "IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks". +- [182] IEEE 1003.1-2004: "IEEE Standard for Information Technology - Portable Operating System Interface (POSIX(R)) - Base Definitions". +- [183] RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification". +- [184] 3GPP TS 23.503: "Policy and charging control framework for the 5G System; Stage 2". +- [185] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [186] 3GPP TS 24.257: "Uncrewed Aerial System (UAS) Application Enabler (UAE) layer; Protocol aspects; Stage 3". +- [187] 3GPP TS 23.558 "Architecture for enabling Edge Applications; Stage 2". +- [188] 3GPP TS 33.246: "Security of Multimedia Broadcast/Multicast Service (MBMS)". +- [189] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets". +- [190] 3GPP TS 24.558 "Enabling Edge Applications; Protocol specification" +- [191] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the following syntactical definitions apply (refer also clause 4): + +- <CR>** Carriage return character, which value is specified with command S3. +- <LF>** Linefeed character, which value is specified with command S4. +- <...>** Name enclosed in angle brackets is a syntactical element. Brackets themselves do not appear in the command line. +- [...]** Optional subparameter of a command or an optional part of TA information response is enclosed in square brackets. Brackets themselves do not appear in the command line. When subparameter is not given in *parameter type* commands, new value equals to its previous value. In *action type* commands, action should be done on the basis of the recommended default setting of the subparameter. +- underline** Underlined defined subparameter value is the recommended default setting of this subparameter. In *parameter type* commands, this value should be used in factory settings which are configured by ITU-T Recommendation V.250 [14] command &F0. In *action type* commands, this value should be used when subparameter is not given. + +### 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|-----------------| +| 5GCN | 5G Core Network | +| 5GS | 5G System | + +| | | +|--------|------------------------------------------------------------------------------------------------------------| +| AT | ATtention; this two-character abbreviation is always used to start a command line to be sent from TE to TA | +| ASCI | Advanced Speech Call Items, including VGCS, VBS and eMLPP | +| BCD | Binary Coded Decimal | +| BL | Bandwidth reduced Low complexity | +| CAG | Closed Access Group | +| CBR | Channel Busy Ratio | +| CSG | Closed Subscriber Group | +| EDC | Edge DNS Client | +| eMLPP | Enhanced Multi-Level Precedence and Pre-emption Service | +| ETSI | European Telecommunications Standards Institute | +| FTM | Frame Tunnelling Mode (refer 3GPP TS 27.001 [41] and 3GPP TS 29.007 [42]) | +| HRNN | Human-Readable Network Name | +| HSCSD | High Speed Circuit Switched Data | +| IMEI | International Mobile station Equipment Identity | +| IRA | International Reference Alphabet (ITU-T Recommendation T.50 [13]) | +| IrDA | Infrared Data Association | +| ISO | International Standards Organization | +| ITU-T | International Telecommunication Union - Telecommunications Standardization Sector | +| MBS | Multicast/Broadcast Services | +| ME | Mobile Equipment | +| MMTEL | Multimedia Telephony | +| MoU | Memorandum of Understanding (GSM operator joint) | +| MT | Mobile Termination | +| MTU | Maximum Transfer Unit | +| NB-IoT | NarrowBand Internet of Things | +| NG-RAN | Next Generation Radio Access Network | +| NSLPI | NAS Signalling Low Priority Indication | +| PCCA | Portable Computer and Communications Association | +| PIN | Personal IoT Network | +| PTT | Push to Talk | +| RDI | Restricted Digital Information | +| RLP | Radio Link Protocol | +| RSN | Redundancy Sequence Number | +| SIM | Subscriber Identity Module | +| TA | Terminal Adaptor, e.g. a GSM data card (equal to DCE; Data Circuit terminating Equipment) | +| TE | Terminal Equipment, e.g. a computer (equal to DTE; Data Terminal Equipment) | +| TIA | Telecommunications Industry Association | +| UAE | UAS Application Enabler | +| UAS | UAS Application System | +| UAV | UAS Application Vehicle | +| UAS | Uncrewed Aerial System | +| UAV | Uncrewed Aerial Vehicle UDI      Unrestricted Digital Information | +| UE | User Equipment | +| UICC | Universal Integrated Circuit Card | +| USAT | USIM Application Toolkit | +| USIM | Universal Subscriber Identity Module | +| USS | UAS Service Supplier | +| UUAA | USS UAV Authorization and Authentication | +| VAE | V2X Application Enabler | +| VBS | Voice Broadcast Service | +| VGCS | Voice Group Call Service | + +## 4 AT command syntax + +### 4.0 General + +This clause summarizes general aspects on AT commands and issues related to them. + +TE software implementors must take into account that future versions of this specification may include additional parameters beyond what is expected in any (final or intermediate) response to an AT set command, read command or test command, and beyond what is expected in any unsolicited result code. Implementations must therefore analyse all parameters provided from the TA and discard (ignore) any parameters received following the parameters expected by the TE software. + +For further information refer ITU-T Recommendation V.250 [14]. + +In the tables for the commands syntaxes, the possible response(s) are outlined as follows: + +- the responses from ITU-T Recommendation V.250 [14] (like *OK* and *ERROR*) are normally not shown; and +- the final response *+CME ERROR* is shown when a final result code in clause 9.2 can be provided. + +In certain implementations, AT commands are used as an internal interface within the physical handset, e.g. between the application and the radio interface layer 3 stack implemented on different processors. Certain AT commands transfer information in the clear that can be regarded as sensitive with regards to security or privacy. Care must be exercised in AT commands that: + +- transfer passwords (e.g. *+CLICK*, *+CPWD* or *+CPBS*); +- transfer identities (e.g. IMSI) or details of a call (e.g. *+COLP*); +- transfer the current location of the phone (e.g. *+CMOIR*); +- reveal the IMEI (e.g. *+CGSN*); +- allow the TE to take unintentionally control over the SIM-MT interface (e.g. *+CSIM*); +- enable/disable access to commands protected by security mechanism (e.g. *+CSCC*); or +- exchange security related parameters and keys with the UICC (e.g. *+CEAP* and *+CERP*). + +The above mentioned AT commands and parameters are examples to illustrate the concerns and is not meant to be a comprehensive list. + +## 4.1 Command line + +See figure 2 for general structure of a command line. Standardized *basic* commands are found only in ITU-T Recommendation V.250 [14]. The commands in this specification use syntax rules of *extended* commands. Every extended command has a *test command* (trailing *=?*) to test the existence of the command and to give information about the type of its subparameters. *Parameter type* commands also have a *read command* (trailing *?*) to check the current values of subparameters. *Action type* commands do not store the values of any of their possible subparameters, and therefore do not have a read command. + +![Diagram illustrating the basic structure of a command line. The command line shown is: ATCMD1 CMD2=12; +CMD1; +CMD2=,,15; +CMD2?; +CMD2=?<CR>. Annotations explain the parts: 'AT' is the command line prefix; 'CMD1' is a basic command (no prefix); 'CMD2=12' is a subparameter; '+' indicates an extended command (prefixed with +); ';' delimits extended commands; '?' indicates a test command for checking possible subparameter values; '<CR>' is the command line termination character. Other annotations point to parts of the command like 'read command for checking current subparameter values' pointing to the '?' in '+CMD2?' and 'subparameters may be omitted' pointing to the empty subparameters in '+CMD2=,,15'.](35127fe87029df6f5f0b2ee85f6193f1_img.jpg) + +Diagram illustrating the basic structure of a command line. The command line shown is: ATCMD1 CMD2=12; +CMD1; +CMD2=,,15; +CMD2?; +CMD2=?. Annotations explain the parts: 'AT' is the command line prefix; 'CMD1' is a basic command (no prefix); 'CMD2=12' is a subparameter; '+' indicates an extended command (prefixed with +); ';' delimits extended commands; '?' indicates a test command for checking possible subparameter values; '' is the command line termination character. Other annotations point to parts of the command like 'read command for checking current subparameter values' pointing to the '?' in '+CMD2?' and 'subparameters may be omitted' pointing to the empty subparameters in '+CMD2=,,15'. + +**Figure 2: Basic structure of a command line** + +If verbose responses are enabled with command V1 and all commands in a command line has been performed successfully, result code <CR><LF>OK<CR><LF> is sent from the TA to the TE. If numeric responses are enabled with command V0, result code 0<CR> is sent instead. + +If verbose responses are enabled with command V1 and subparameter values of a command are not accepted by the TA (or command itself is invalid, or command cannot be performed for some reason), result code <CR><LF>ERROR<CR><LF> is sent to the TE and no subsequent commands in the command line are processed. If numeric responses are enabled with command V0, result code 4<CR> is sent instead. ERROR (or 4) response may be replaced by +CME ERROR: <err> (refer clause 9) when command was not processed due to an error related to MT operation. + +## 4.2 Information responses and result codes + +The TA response for the example command line of figure 2 could be as shown in figure 3. Here, verbose response format is enabled with command V1. If numeric format V0 would have been used, <CR><LF> headers of *information responses* would have been left out and *final result code* changed to 0<CR>. + +![Figure 3: Response to a command line. The diagram shows a sequence of responses to the command '+CMD2=?'. The responses are: 1. '+CMD2: 3,0,15,\](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +information response to +CMD2=? also string type subparameters possible +information response to +CMD2? +| +|> <CR><LF>+CMD2: 3,0,15,"GSM"<CR><LF> +|> <CR><LF>+CMD2: (0-3),(0,1),(0-12,15),("GSM","IRA")<CR><LF> +|> <CR><LF>OK<CR><LF> +| +final result code shows acceptable ranges of each subparameter + +``` + +Figure 3: Response to a command line. The diagram shows a sequence of responses to the command '+CMD2=?'. The responses are: 1. '+CMD2: 3,0,15,\ + +Figure 3: Response to a command line + +So called *intermediate result codes* inform about progress of TA operation (e.g. connection establishment CONNECT), and so called *unsolicited result codes* indicate occurrence of an event not directly associated with issuance of a command from TE (e.g. ring indication RING). + +## 4.3 ITU-T Recommendation V.250 [14] TE-TA interface commands + +Table 1 summarizes ITU-T Recommendation V.250 [14] commands relating to command line and response formatting, and TA-TE interface operation. All are applicable to terminals specified by the present document. + +Table 1: V.250 commands relating to TE-TA interface + +| Command | Clause | Impl. | Used in the present document | +|--------------|--------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| S3=[<value>] | 6.2.1 | mand. | command line termination character (mandatory default setting IRA 13) | +| S4=[<value>] | 6.2.2 | mand. | response formatting character (recommended default IRA 10) | +| S5=[<value>] | 6.2.3 | mand. | command line editing character (recommended default IRA 8) | +| E[<value>] | 6.2.4 | mand. | command echo (recommended default 1 i.e. TA echoes commands back) | +| Q[<value>] | 6.2.5 | mand. | result code suppression (recommended default 0 i.e. TA transmits result codes) | +| V[<value>] | 6.2.6 | mand. | TA response format (recommended default 1 i.e. verbose format) | +| X[<value>] | 6.2.7 | mand. | defines CONNECT result code format; values manufacturer specific | +| &C[<value>] | 6.2.8 | mand. | determines how ITU-T V.24 circuit 109 (or equivalent) relates to the detection of received line signal from remote end (recommended default 1 i.e. 109 operation relates to detection of received signal) | +| &D[<value>] | 6.2.9 | mand. | determines how TA responds when ITU-T V.24 circuit 108/2 (or equivalent) is changed from ON to OFF condition during online data | + +| | | | | +|----------------------------|--------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | state | +| +IPR=[<value>] | 6.2.10 | opt. | fixed TE data rate (recommended default 0 i.e. automatic detection) | +| +ICF=[<format>[,<parity>]] | 6.2.11 | opt. | TE-TA character framing (recommended default 3,3 i.e. eight data bits, no parity, 1 stop bit) | +| +IFC=[<by_te>[,<by_ta>]] | 6.2.12 | opt. | TE-TA local flow control (recommended default 2,2 i.e. TE uses ITU-T V.24 circuit 133 (or equivalent), and TA circuit 106 (or equivalent)) | +| +ILRR=[<value>] | 6.2.13 | opt. | determines whether the used local TE-TA data rate is informed using intermediate result code +ILRR: <rate> before going online data state after call answering or originating | + +## 5 General commands + +### 5.0 General + +ITU-T Recommendation V.250 [14] includes "Generic DCE Control" commands with the prefix +G. These commands are for the identification of the TA. Four of those commands are adapted here to be the identification commands of the MT. Syntax is otherwise similar, but the prefix is +CG. TTA IS-99 [15] uses same commands for base station identification. + +### 5.1 Request manufacturer identification +CGMI + +**Table 2: +CGMI action command syntax** + +| Command | Possible response(s) | +|---------|-----------------------------------------| +| +CGMI | <manufacturer><br><br>+CME ERROR: <err> | +| +CGMI=? | | + +#### Description + +Execution command causes the TA to return one or more lines of information text <manufacturer>, determined by the MT manufacturer, which is intended to permit the user of the TA to identify the manufacturer of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the manufacturer, but manufacturers may choose to provide more information if desired. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<manufacturer>: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0<CR> or OK<CR>. + +#### Implementation + +Optional. + +## 5.2 Request model identification +CGMM + +**Table 3: +CGMM action command syntax** + +| Command | Possible response(s) | +|---------|----------------------------------| +| +CGMM | <model><br><br>+CME ERROR: <err> | +| +CGMM=? | | + +### Description + +Execution command causes the TA to return one or more lines of information text <model>, determined by the MT manufacturer, which is intended to permit the user of the TA to identify the specific model of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the product, but manufacturers may choose to provide more information if desired. Refer clause 9.2 for possible <err> values. + +### Defined values + +<model>: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0<CR> or OK<CR>. + +### Implementation + +Optional. + +## 5.3 Request revision identification +CGMR + +**Table 4: +CGMR action command syntax** + +| Command | Possible response(s) | +|---------|-------------------------------------| +| +CGMR | <revision><br><br>+CME ERROR: <err> | +| +CGMR=? | | + +### Description + +Execution command causes the TA to return one or more lines of information text <revision>, determined by the MT manufacturer, which is intended to permit the user of the TA to identify the version, revision level or date, or other pertinent information of the MT to which it is connected to. Typically, the text will consist of a single line containing the version of the product, but manufacturers may choose to provide more information if desired. Refer clause 9.2 for possible <err> values. + +### Defined values + +<revision>: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0<CR> or OK<CR>. + +### Implementation + +Optional. + +## 5.4 Request product serial number identification +CGSN + +**Table 5: +CGSN action command syntax** + +| Command | Possible response(s) | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGSN[=<snt>] | <b>when <snt>=0 (or omitted) and command successful:</b><br><sn><br><br><b>when <snt>=1 and command successful:</b><br>+CGSN: <imei><br><br><b>when <snt>=2 and command successful:</b><br>+CGSN: <imeisv><br><br><b>when <snt>=3 and command successful:</b><br>+CGSN: <svn><br><br>+CME ERROR: <err> | +| +CGSN=? | <b>when TE supports <snt> and command successful:</b><br>+CGSN: (list of supported <snt>s) | + +### Description + +Execution command causes the TA to return IMEI (International Mobile station Equipment Identity number) and related information to identify the MT that the TE is connected to. + +Refer clause 9.2 for possible <err> values. + +Test command returns values supported as a compound value. For a TA which does not support <snt>, only OK is returned. + +### Defined values + +<snt>: integer type indicating the serial number type that has been requested. + +- 0 returns <sn> +- 1 returns the IMEI (International Mobile station Equipment Identity) +- 2 returns the IMEISV (International Mobile station Equipment Identity and Software Version number) +- 3 returns the SVN (Software Version Number) + +<sn>: one or more lines of information text determined by the MT manufacturer. Typically, the text will consist of a single line containing the IMEI number of the MT, but manufacturers may choose to provide more information if desired. The total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0<CR> or OK<CR>. + +<imei>: string type in decimal format indicating the IMEI; refer 3GPP TS 23.003 [7], clause 6.2.1. IMEI is composed of Type Allocation Code (TAC) (8 digits), Serial Number (SNR) (6 digits) and the Check Digit (CD) (1 digit). Character set used in <imei> is as specified by command select TE character set +CSCS. + +<imeisv>: string type in decimal format indicating the IMEISV; refer 3GPP TS 23.003 [7], clause 6.2.2. The 16 digits of IMEISV are composed of Type Allocation Code (TAC) (8 digits), Serial Number (SNR) (6 digits) and the software version (SVN) (2 digits). Character set used in <imeisv> is as specified by command select TE character set +CSCS. + +<svn>: string type in decimal format indicating the current SVN which is a part of IMEISV; refer 3GPP TS 23.003 [7], clause 6.2.2. This allows identifying different software versions of a given mobile. Character set used in <svn> is as specified by command select TE character set +CSCS. + +NOTE: The default value `<snt>=0` returns the information text `<sn>` with no command name prefixed. This has been done to retain backward compatibility. All other values of `<snt>` return the information text including command name prefix. + +### Informative examples + +To get `<sn>` which returns IMEI of the MT: + +``` +AT+CGSN +490154203237518 +OK +``` + +To get `<imei>` which returns IMEI of the MT: + +``` +AT+CGSN=1 ++CGSN: "490154203237518" +OK +``` + +### Implementation + +Optional. + +## 5.5 Select TE character set +CSCS + +**Table 6: +CSCS parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------|----------------------------------------------------------| +| <code>+CSCS=<charset></code> | | +| <code>+CSCS?</code> | <code>+CSCS: <charset></code> | +| <code>+CSCS=?</code> | <code>+CSCS: (list of supported <charset>s)</code> | + +### Description + +Set command informs TA which character set `<charset>` is used by the TE. TA is then able to convert character strings correctly between TE and MT character sets. + +When TA-TE interface is set to 8-bit operation and used TE alphabet is 7-bit, the highest bit shall be set to zero. + +NOTE: It is manufacturer specific how the internal alphabet of MT is converted to/from the TE alphabet. + +Read command shows current setting and test command displays conversion schemes implemented in the TA. + +Test command returns values supported as a compound value. + +### Defined values + +`<charset>`: character set as a string type (conversion schemes not listed here can be defined by manufacturers). + +`"GSM"` GSM 7 bit default alphabet (3GPP TS 23.038 [25]); this setting causes easily software flow control (XON/XOFF) problems. + +`"HEX"` Character strings consist only of hexadecimal numbers from 00 to FF; e.g. "032FE6" equals three 8-bit characters with decimal values 3, 47 and 230; no conversions to the original MT character set shall be done. + +If MT is using GSM 7 bit default alphabet, its characters shall be padded with 8th bit (zero) before converting them to hexadecimal numbers (i.e. no SMS-style packing of 7-bit alphabet). + +`"IRA"` International reference alphabet (see ITU-T Recommendation T.50 [13]). + +`"PCCPxxx"` PC character set Code Page xxx. + +`"PCDN"` PC Danish/Norwegian character set. + +- "UCS2" 16-bit universal multiple-octet coded character set (see ISO/IEC10646 [32]); UCS2 character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. "004100620063" equals three 16-bit characters with decimal values 65, 98 and 99. +- "UTF-8" Octet (8-bit) lossless encoding of UCS characters (see RFC 3629 [69]); UTF-8 encodes each UCS character as a variable number of octets, where the number of octets depends on the integer value assigned to the UCS character. The input format shall be a stream of octets. It shall not be converted to hexadecimal numbers as in "HEX" or "UCS2". This character set requires an 8-bit TA – TE interface. +- "8859-n" ISO 8859 Latin *n* (1-6) character set. +- "8859-C" ISO 8859 Latin/Cyrillic character set. +- "8859-A" ISO 8859 Latin/Arabic character set. +- "8859-G" ISO 8859 Latin/Greek character set. +- "8859-H" ISO 8859 Latin/Hebrew character set. + +#### Implementation + +Mandatory when a command using the setting of this command is implemented. + +## 5.6 Request international mobile subscriber identity +CIMI + +**Table 7: +CIMI action command syntax** + +| Command | Possible response(s) | +|---------|---------------------------------| +| +CIMI | <IMSI><br><br>+CME ERROR: <err> | +| +CIMI=? | | + +#### Description + +Execution command causes the TA to return <IMSI>, which is intended to permit the TE to identify the individual SIM card or active application in the UICC (GSM or USIM) which is attached to MT. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<IMSI>: International Mobile Subscriber Identity (string without double quotes) + +#### Implementation + +Optional. + +## 5.7 Multiplexing mode +CMUX + +**Table 8: +CMUX parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMUX=<transparency>[, <subset>[, <port_speed>[, <N1>[, <T1>[, <N2>[, <T2>[, <T3>[, <k>]]]]]]] | +CME ERROR: <err> | +| +CMUX? | +CMUX: <transparency>,<br>[<subset>], <port_speed>, <N1>, <T1>, <N2>, <T2>, <T3>[, <k>]<br><br>+CME ERROR: <err> | +| +CMUX=? | +CMUX: (list of supported <transparency>s) , (list of supported <subset>s) , (list of supported <port_speed>s) , (list of supported <N1>s) , (list of supported <T1>s) , (list of supported <N2>s) , (list of supported <T2>s) , (list of supported <T3>s) , (list of supported <k>s) | + +### Description + +This command is used to enable/disable the 3GPP TS 27.010 [45] multiplexing protocol control channel. Refer clause 9.2 for possible <err> values. The AT command sets parameters for the Control Channel. If the parameters are left out, the default value is used. + +Read command returns the current settings. + +Test command returns the supported parameters as compound values. + +It is recommended that the MT/TA/TE should autobaud to the +CMUX command up to and including an interface speed of 9600 bits/s. + +The OK or +CME ERROR: <err> response is returned at the speed of the +CMUX command prior to entering <transparency>. + +It is recommended that whenever the multiplexer control channel is released the MT/TA/TE should assume an interface rate of up to and including 9600 bits/s for auto bauding purposes irrespective of any previous higher speed having been selected. + +If a +CMUX command is issued whilst in any multiplexer mode then that +CMUX command shall be ignored and the MT/TA shall return a +CME ERROR: <err> response. + +### Defined values + +<transparency>: integer type (multiplexer Transparency Mechanism). + +- 0 Basic option +- 1 Advanced option + +<subset>: integer type. This parameter defines the way in which the multiplexer **control channel** is set up. A virtual channel may subsequently be set up differently but in the absence of any negotiation for the settings of a virtual channel, the virtual channel shall be set up according to the control channel <subset> setting. + +- 0 UIH frames used only +- 1 UI frames used only +- 2 I frames used only + +<port\_speed> integer type (transmission rate). The default value is implementation specific. + +- 1 9 600 bit/s +- 2 19 200 bit/s +- 3 38 400 bit/s +- 4 57 600 bit/s +- 5 115 200 bit/s +- 6 230 400 bits/s + +<N1>: integer type (maximum frame size). + +- 1- 32768, where the 31 is default for Basic option and 64 is default for Advanced option (see <transparency>) + +<T1>: integer type (acknowledgement timer in units of ten milliseconds). + +- 1-255, where 10 is default (100 ms) + +<N2>: integer type (maximum number of re-transmissions). + +- 0-100, where 3 is default + +<T2>: integer type (response timer for the multiplexer control channel in units of ten milliseconds). + +- 2-255, where 30 is default (300 ms) + +NOTE: T2 must be longer than T1. + +<T3>: integer type (wake up response timer in seconds). + +- 1-255, where 10 is default + +<k>: integer type (window size, for Advanced option with Error-Recovery Mode). + +- 1-7, where 2 is default + +### Implementation + +Mandatory, if 3GPP TS 27.010 [45] supported in the MT/TA. + +## 5.8 ITU-T Recommendation V.250 [14] generic TA control commands + +**Table 9: V.250 generic TA control commands** + +| Command | Clause | Impl. | Used in the present document | +|--------------|--------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Z [<value>] | 6.1.1 | mand. | TA sets all parameters to their defaults as specified by a user memory profile or by the manufacturer, and resets TA | +| &F [<value>] | 6.1.2 | mand. | TA sets all parameters to their defaults as specified by the manufacturer | +| I [<value>] | 6.1.3 | opt. | request manufacturer specific information about the TA (software cannot use this command to determine the capabilities of a TA) | +| +GMI | 6.1.4 | mand. | request TA manufacturer identification (may equal to +CGMI) | +| +GMM | 6.1.5 | mand. | request TA model identification (may equal to +CGMM) | +| +GMR | 6.1.6 | mand. | request TA revision identification (may equal to +CGMR) | +| +GSN | 6.1.7 | opt. | request TA serial number identification (may equal to +CGSN) | +| +GOI | 6.1.8 | opt. | request ISO system global object identification of the TA (general format defined in ITU-T Recommendation X.208; encoding rules in ITU-T Recommendation X.209) | +| +GCAP | 6.1.9 | mand. | request overall capabilities of TA; the response code for a TA building on this document shall be +CGSM | +| +GCI=<T.35> | 6.1.10 | opt. | selects the country of installation for the TA using ITU-T Recommendation T.35 Annex A country codes | + +## 5.9 PCCA STD-101 [17] select wireless network +WS46 + +PCCA STD-101 [17] includes a command to select the cellular network (Wireless Data Service; WDS) to operate with the TA. PCCA calls this WDS-Side Stack Selection. This command may be used when TA is asked to indicate the networks in which it can operate. + +**Table 10: +WS46 parameter command syntax** + +| Command | Possible response(s) | +|-----------|--------------------------| +| +WS46=<n> | | +| +WS46? | <n> | +| +WS46=? | (list of supported <n>s) | + +### Description + +Set command selects the WDS side stack <n> to be used by the TA. Read command shows current setting and test command displays side stacks implemented in the TA. + +Read command (query) returns the current value of <n>. + +Test command returns values supported as a compound value. + +### Defined values for Query + +<n>: integer type + +12 GSM Digital Cellular Systems (GERAN only) + +22 UTRAN only + +25 3GPP Systems (GERAN, UTRAN and E-UTRAN) + +28 E-UTRAN only + +- 29 GERAN and UTRAN +- 30 GERAN and E-UTRAN +- 31 UTRAN and E-UTRAN +- 35 GERAN, UTRAN, E-UTRAN and NG-RAN +- 36 NG-RAN only +- 37 NG-RAN and E-UTRAN +- 38 NG-RAN, E-UTRAN and UTRAN +- 39 NG-RAN, E-UTRAN and GERAN +- 40 NG-RAN and UTRAN +- 41 NG-RAN, UTRAN and GERAN +- 42 NG-RAN and GERAN + +The values in <n> for Query are mutually exclusive. If one value (e.g. "25") is returned, other values shall not be returned. + +#### Defined values for Set + +<n>: integer type + +- 12 3GPP System + - 22 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 25 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 28 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 29 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 30 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 31 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 35 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 36 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 37 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 38 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 39 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 40 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 41 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. + - 42 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- refer PCCA STD-101 [17] for other values. + +#### Implementation + +Mandatory in PCCA STD-101 [17], but optional in the context of this specification. + +## 5.10 Request 5G subscription permanent identifier +CSUPI + +**Table 5.10-1: +CSUPI action command syntax** + +| Command | Possible response(s) | +|----------|---------------------------------| +| +CSUPI | <SUPI><br><br>+CME ERROR: <err> | +| +CSUPI=? | | + +### Description + +Execution command causes the TA to return <SUPI>, which is intended to permit the TE to identify the individual USIM card or active application in the UICC which is attached to 5G MT. Refer clause 9.2 for possible <err> values. + +### Defined values + +<SUPI>: 5G subscription permanent identifier (string without double quotes). + +### Implementation + +Optional. This command is superfluous when the command +CIMI or +CNAI is supported. + +## 5.11 Request 5G network specific identifier +CNAI + +**Table 5.11-1: +CNAI action command syntax** + +| Command | Possible response(s) | +|---------|--------------------------------| +| +CNAI | <NAI><br><br>+CME ERROR: <err> | +| +CNAI=? | | + +### Description + +Execution command causes the TA to return <NAI>, which is intended to permit the TE to identify the individual USIM card or active application in the UICC which is attached to 5G MT. Refer clause 9.2 for possible <err> values. + +### Defined values + +<NAI>: Network Access Identifier (NAI), as specified in 3GPP TS 23.003 [7], when SUPI is in NAI format (string without double quotes) consisting of: + +- network specific identifier (NSI), as specified in 3GPP TS 23.003 [7], when SUPI type is NSI; +- Global Line Identifier (GLI), as specified in 3GPP TS 23.003 [7] clause 28.15.2, when SUPI type is GLI; or +- Global Cable Identifier (GCI), as specified in 3GPP TS 23.003 [7] clause 28.16.2, when SUPI type is GCI. + +### Implementation + +Optional. + +## 5.12 Informative examples + +When beginning to build a communication link, a general TE application controlling a TA needs to determine the TA and the MT to which it is connected. ITU-T Recommendation V.250 [14] has seven commands for TA identification from which four are mandatory to be implemented in a TA. An example of this command sequence requesting manufacturer (+GMI), model (+GMM), revision (+GMR) and serial number (+GSN) information would be: + +``` +AT+GMI +Manufacturer ABC +OK +AT+GMM +GSM Ultimate Data Device +OK +AT+GMR +1.00 +OK +AT+GSN +987612345-123 +OK +``` + +The maximum lengths of the information responses are defined to be 2048 characters, but it is recommended that they are kept as simple as in the example. The serial number command is defined as optional. Another optional command is Global Object Identification command (+GOI) which should return the object identifiers of ITU-T Recommendation X.208 as numeric strings delimited by periods. The Complete Capabilities List command (+GCAP) indicates the major capability areas of the TA. The support of different areas is presented in the response of +GCAP command. Each area can be presented by the selection command name of a specific capability area (e.g. +FCLASS for fax support) or some other predefined response. For instance, a GSM TA with fax capabilities could respond as follows: + +``` +AT+GCAP ++GCAP: +CGSM,+FCLASS,+W +OK +``` + +The first supported area in the response is presented with +CGSM. It is the response text to show that some or all GSM commands of the present document are supported. Second response text (+FCLASS) informs that some fax or voice capabilities are present, and the third text (+W) about the presence of wireless commands as specified by PCCA STD-101 [17]. Command +FCLASS=? (refer e.g. ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12]) can be used to query the supported fax capabilities and +WS46=? to query the wireless data services available: + +``` +AT+FCLASS=?;+WS46=? +0,1,2,2.0 +(12) +OK +``` + +The TA of this example supports GSM data services, and fax service class 1 (TIA-578-A), 2 (manufacturer specific) and 2.0 (ITU-T Recommendation T.32 [12] / TIA-592). + +The present document defines commands for MT identification which are similar to those for TA identification in ITU-T Recommendation V.250 [14], for an example: + +``` +AT+CGMI +Mobile Manufacturer XYZ +OK +AT+CGMM +GSM Phone 1234 +OK +AT+CGMR +1.00 +OK +AT+CGSN +123456121234561 +OK +``` + +Manufacturer, model and version commands work similarly as for TA, except that the serial number query returns the International Mobile Station Equipment Identity (IMEI) number. IMEI is fifteen digits long and consists of a type approval code, a final assembly code, a serial number and a spare digit (refer 3GPP TS 23.003 [7]). When the TA is implemented inside MT, the responses for both TA and MT queries will most likely follow the responses of MT identification. + +## 6 Call control commands and methods + +### 6.0 General + +This clause describes the control of calls. Normal data and fax call control is done as in ITU-T Recommendation V.250 [14], ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12]. For voice call originating, refer clause "ITU-T Recommendation V.250 dial command D" and clause "Commands for enhanced support of dialling". + +### 6.1 Select type of address +CSTA + +**Table 11: +CSTA parameter command syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CSTA= [<type>] | | +| +CSTA? | +CSTA: <type> | +| +CSTA=? | +CSTA: (list of supported <type>s) | + +#### Description + +Set command selects the type of number for further dialling commands (D) according to 3GPP TS 24.008 [8]. + +Read command returns the current value of <type>. + +Test command returns values supported as a compound value. + +#### Defined values + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129. + +#### Implementation + +Mandatory when other than default value allowed. + +### 6.2 ITU-T Recommendation V.250 [14] dial command D + +ITU-T Recommendation V.250 [14] dial command D lists characters that may be used in a dialling string for making a call or controlling supplementary services in accordance with 3GPP TS 22.030 [19]. Their use is listed in this clause, as well as new dial modifiers are introduced. For an MT supporting AT commands only, it is mandatory to support the control of supplementary services in accordance with 3GPP TS 22.030 [19] through the dial command or through the specific supplementary service commands (+CCFC, +CLCK, etc.), where 3GPP TS 22.030 [19] identifies the supplementary services as mandatory. See also the AT commands for enhanced support of dialling as well as +CMCCS and +CLCCS. + +#### V.250 dialling digits + +1 2 3 4 5 6 7 8 9 0 \* # + A B C (implementation of these characters is mandatory) + +D (implementation of this character is optional, and it is ignored) + +#### V.250 modifier characters + +, (implementation of this character is mandatory, but it may be ignored) + +T P (implementation of these characters is mandatory, but they are ignored) + +! W @ (implementation of these characters is optional, and they are ignored) + +### V.250 semicolon character + +When semicolon character is given after dialling digits (or modifiers), a voice call originated to the given address. TA returns to command state immediately (or after possible +COLP result code; refer clause "Connected line identification presentation +COLP"). Refer Annex G for a detailed example. + +### Modifier characters + +> (refer clause "Direct dialling from phonebooks") + +I or i (override the CLIR supplementary service subscription default value for this call; I = invocation (restrict CLI presentation) and i = suppression (allow CLI presentation); refer clause "Calling line identification restriction +CLIR"). + +G or g (control the CUG supplementary service information for this call; uses index and info values set with command +CCUG or +CECUG; refer clause "Closed user group +CCUG" and clause "Enhanced closed user group +CECUG"). + +## 6.3 Direct dialling from phonebooks + +MT and SIM/UICC can contain phonebooks which have a phone number and an alphanumeric field for each phonebook entry location. The use of ITU-T Recommendation V.250 [14] dialling command ensures that direct dialling from MT and SIM/UICC phonebook is possible through ordinary communications software which just gives the phone number field to be filled and then use the D command to originate the call. Available memories may be queried with Select Phonebook Storage test command +CPBS=?, and location range for example with Read Phonebook Entries test command +CPBR=?. + +### Execute commands + +1. D><str>[I][G][;] originate call to phone number which corresponding alphanumeric field is <str> (if possible, all available memories should be searched for the correct entry). +2. D>mem<n>[I][G][;] originate call to phone number in memory *mem* entry location <n> (available memories may be queried with Select Phonebook Storage test command +CPBS=?; *mem* could be e.g. ME). +3. D><n>[I][G][;] originate call to phone number in entry location <n> (it is manufacturer specific which memory storage of MT, SIM/UICC in the currently selected card slot and TA is used; command Select Phonebook Memory Storage +CPBS setting is recommended to be used). + +Semicolon character shall be added when voice call is originated. CLIR and CUG per call base modifiers may also be present. + +### Responses + +Possible error responses include +CME ERROR: <err> when error is related to MT functionality. Refer clause 9.2 for possible <err> values. Otherwise TA responses can have values defined by ITU-T Recommendation V.250 [14] and commands Service Reporting Control +CR and Connected Line Identification Presentation +COLP. Detailed error report of an unsuccessful originated call failed in the network error can be obtained with command Extended Error Report +CEER (if implemented). + +### Defined values + +<str>: string type value, which should equal to an alphanumeric field in at least one phonebook entry in the searched memories; used character set should be the one selected with command select TE character set +CSCS. + +<n>: integer type memory location should be in the range of locations available in the memory used. + +### Implementation + +Mandatory when direct dialling is implemented. Also phonebook commands implementation is required. + +## 6.4 Call mode +CMOD + +**Table 12: +CMOD parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CMOD=<mode> | | +| +CMOD? | +CMOD: <mode> | +| +CMOD=? | +CMOD: (list of supported <mode>s) | + +### Description + +Set command selects the call mode of further dialling commands (D) or for next answering command (A). Mode can be either single or alternating (in the present document, terms "alternating mode" and "alternating call" refer to all GSM/UMTS bearer and teleservices that incorporate more than one basic service (voice, data, fax) within one call). When single mode is selected the call originating and hangup procedures are similar to procedures specified in ITU-T Recommendations V.250 [14], T.31 [11] and T.32 [12]. In GSM/UMTS there can be voice followed by data (refer 3GPP TS 22.002 [1]), alternating voice/data (refer 3GPP TS 22.002 [1]) and alternating voice/fax calls (refer 3GPP TS 22.003 [2]). See following clauses for alternating call control methods. + +Read command returns the current value of <mode>. + +Test command returns values supported as a compound value. + +NOTE: +CMOD shall be set to zero after a successfully completed alternating mode call. It shall be set to zero also after a failed answering. The power-up, factory (&F) and user resets (Z) shall also set the value to zero. This reduces the possibility that alternating mode calls are originated or answered accidentally. + +### Defined values + +<mode>: integer type + +- 0 single mode +- 1 alternating voice/fax (teleservice 61) +- 2 alternating voice/data (bearer service 61) +- 3 voice followed by data (bearer service 81) + +all other values below 128 are reserved by the present document. + +### Implementation + +Mandatory when alternating mode calls are implemented in the TA. + +## 6.4A Voice call mode +CVMOD + +**Table 13: +CVMOD parameter command syntax** + +| Command | Possible response(s) | +|---------------------|-------------------------------------------| +| +CVMOD=<voice_mode> | | +| +CVMOD? | +CVMOD: <voice_mode> | +| +CVMOD=? | +CVMOD: (list of supported <voice_mode>s) | + +## Description + +Set command selects the voice call mode for making a Mobile Originated voice call from the UE. The voice call mode can be CS\_ONLY, VOIP\_ONLY, CS\_PREFERRED or VOIP\_PREFERRED. Type of VoIP session preferred (e.g. SIP VoIP, IMS VoIP) is manufacturer specific issue. + +NOTE 1: If the Call Mode is set to CS\_ONLY, then the ATD command will make a call in CS mode. + +If the Call Mode is set to VOIP\_ONLY, then the ATD command will make a call in VoIP mode. + +If the Call Mode is set to CS\_PREFERRED, then the ATD command gives preference for CS based voice call. + +If the Call Mode is set to VOIP\_PREFERRED, then the ATD command gives preference for VoIP based voice call + +NOTE 2: As an alternative to the ATD command, the command Dial URI +CDU can be used if supported. + +NOTE 3: The preferences are not applicable for the emergency call. + +NOTE 4: The preferences are not applicable if operator has set preferences for UE originated calls/sessions, 3GPP TS 24.216 [75] clause 5.6. + +Read command returns the current value of <voice\_mode>. + +Test command returns the values supported by the UE as a compound value. + +## Defined values + +<voice\_mode>: integer type. The default value is manufacturer specific. + +- 0 CS\_ONLY +- 1 VOIP\_ONLY +- 2 CS\_PREFERRED +- 3 VOIP\_PREFERRED + +## Implementation + +Optional. + +# 6.5 Hangup call +CHUP + +**Table 13a: +CHUP action command syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +CHUP | | +| +CHUP=? | | + +## Description + +Execution command causes the TA to hangup the current call of the MT. + +NOTE: The purpose of this command is not to replace the ITU-T Recommendation V.250 [14] command H, but to give an assured procedure to terminate an alternating mode call. Refer next clause. + +## Implementation + +Mandatory when alternating mode calls implemented in the TA. + +## 6.6 Alternating mode call control method + +This clause describes the procedure to handle alternating mode calls with AT commands. Procedures are mandatory when alternating mode calls are implemented in the TA. + +NOTE 1: ATH and drop DTR will not necessarily cause a hangup from voice mode. If the +CVHU is implemented the behaviour shall be controlled by its setting. + +### Voice followed by data call (bearer service 81) + +Figure 4 shows commands to start the call, to switch from voice to data (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. Refer clause "Cellular result codes +CRC" for possible +CRING result code values. Refer Annex F for a detailed example. + +![Figure 4: Voice followed by data call. A state transition diagram showing three states: MO (Mobile Originated), MT (Mobile Terminated), and DATA. Transitions are triggered by AT commands or remote events.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MO : MO AT+CMOD=3 AT+FCLASS=0 + [*] --> MT : MT +CRING: VOICE/XXX AT+CMOD=3;+FCLASS=0 + MO --> VOICE : ATDxxx; + MT --> VOICE : ATA + VOICE --> DATA : ATD or ATA or remote initiated + VOICE --> HANGUP : AT+CHUP or remote initiated hangup (or ATH or drop DTR) + DATA --> HANGUP : ATH or drop DTR or AT+CHUP or remote initiated hangup + HANGUP --> [*] : TA sets +CMOD=0 + +``` + +The diagram illustrates the state transitions for the alternating mode call control method. It starts with two initial states: MO (Mobile Originated) and MT (Mobile Terminated). Both states lead to the VOICE state. From the VOICE state, a transition to the DATA state occurs via ATD or ATA or remote initiated commands. Both the VOICE and DATA states lead to the HANGUP state via AT+CHUP or remote initiated hangup (or ATH or drop DTR) and ATH or drop DTR or AT+CHUP or remote initiated hangup commands respectively. The HANGUP state then leads back to the initial state, with the TA setting +CMOD=0. + +Figure 4: Voice followed by data call. A state transition diagram showing three states: MO (Mobile Originated), MT (Mobile Terminated), and DATA. Transitions are triggered by AT commands or remote events. + +Figure 4: Voice followed by data call + +### Voice/ data call (bearer service number 61) + +Figure 5 shows the commands to start the call, to switch between modes (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. Refer clause "Cellular result codes +CRC" for possible +CRING result code values. Refer Annex E for a detailed example. + +![Figure 5: Alternating voice and data call flowchart. It shows transitions between VOICE and DATA states. MT voice first: +CRING: ALT VOICE/XXX, AT+CMOD=2;+FCLASS=0. MO: AT+CMOD=2, AT+FCLASS=0. MT data first: +CRING: ALT XXX/VOICE, AT+CMOD=2;+FCLASS=0. Transitions are initiated by ATDxxx, ATA, ATD or ATA or remote initiated, ATH or drop DTR or remote initiated, and AT+CHUP or remote initiated hangup (or ATH or drop DTR). HANGUP state: TA sets +CMOD=0.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + + graph TD + subgraph MT_voice_first [MT voice first] + M1["+CRING: ALT VOICE/XXX +AT+CMOD=2;+FCLASS=0"] + end + subgraph MO [MO] + M2["AT+CMOD=2 +AT+FCLASS=0"] + end + subgraph MT_data_first [MT data first] + M3["+CRING: ALT XXX/VOICE +AT+CMOD=2;+FCLASS=0"] + end + VOICE[VOICE] + DATA[DATA] + HANGUP["HANGUP +TA sets +CMOD=0"] + + M1 -- ATA --> VOICE + M2 -- ATDxxx --> VOICE + M2 -- ATDxxx --> DATA + M3 -- ATA --> DATA + VOICE -- "ATD or ATA or remote initiated" --> DATA + DATA -- "ATH or drop DTR or remote initiated" --> VOICE + VOICE -- "AT+CHUP or remote initiated hangup +(or ATH or drop DTR)" --> HANGUP + DATA -- "AT+CHUP or remote initiated hangup" --> HANGUP + +``` + +Figure 5: Alternating voice and data call flowchart. It shows transitions between VOICE and DATA states. MT voice first: +CRING: ALT VOICE/XXX, AT+CMOD=2;+FCLASS=0. MO: AT+CMOD=2, AT+FCLASS=0. MT data first: +CRING: ALT XXX/VOICE, AT+CMOD=2;+FCLASS=0. Transitions are initiated by ATDxxx, ATA, ATD or ATA or remote initiated, ATH or drop DTR or remote initiated, and AT+CHUP or remote initiated hangup (or ATH or drop DTR). HANGUP state: TA sets +CMOD=0. + +Figure 5: Alternating voice and data call + +Voice/ fax call (teleservice number 61) + +Figure 6 shows the commands to start the call, to switch between modes (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. The parameter "x" of +FCLASS command can be 1, 1.0, 2 or 2.0. + +NOTE 2: The transition from fax mode to voice mode is for further study. + +![Figure 6: Alternating voice and fax call flowchart. It shows transitions between VOICE and FAX states. MT voice first: +CRING: ALT VOICE/FAX, AT+CMOD=1;+FCLASS=x. MO: AT+CMOD=1, AT+FCLASS=x. MT fax first: +CRING: ALT FAX/VOICE, AT+CMOD=1;+FCLASS=x. Transitions are initiated by ATDxxx, ATA, ATD or remote initiated, AT+CHUP or remote initiated hangup (or ATH or drop DTR), and refer ITU-T T.31 [11] and T.32 [12] for different hangup possibilities (also AT+CHUP shall hangup). HANGUP state: TA sets +CMOD=0.](f1091147d93cee4dfa88498610e395a7_img.jpg) + +``` + + graph TD + subgraph MT_voice_first [MT voice first] + M1["+CRING: ALT VOICE/FAX +AT+CMOD=1;+FCLASS=x"] + end + subgraph MO [MO] + M2["AT+CMOD=1 +AT+FCLASS=x"] + end + subgraph MT_fax_first [MT fax first] + M3["+CRING: ALT FAX/VOICE +AT+CMOD=1;+FCLASS=x"] + end + VOICE[VOICE] + FAX[FAX] + HANGUP["HANGUP +TA sets +CMOD=0"] + + M1 -- ATA --> VOICE + M2 -- ATDxxx --> VOICE + M2 -- ATDxxx --> FAX + M3 -- ATA --> FAX + VOICE -- "ATD or remote initiated" --> FAX + FAX -- "refer ITU-T T.31 [11] and T.32 [12] +for different hangup possibilities +(also AT+CHUP shall hangup)" --> HANGUP + VOICE -- "AT+CHUP or remote initiated hangup +(or ATH or drop DTR)" --> HANGUP + +``` + +Figure 6: Alternating voice and fax call flowchart. It shows transitions between VOICE and FAX states. MT voice first: +CRING: ALT VOICE/FAX, AT+CMOD=1;+FCLASS=x. MO: AT+CMOD=1, AT+FCLASS=x. MT fax first: +CRING: ALT FAX/VOICE, AT+CMOD=1;+FCLASS=x. Transitions are initiated by ATDxxx, ATA, ATD or remote initiated, AT+CHUP or remote initiated hangup (or ATH or drop DTR), and refer ITU-T T.31 [11] and T.32 [12] for different hangup possibilities (also AT+CHUP shall hangup). HANGUP state: TA sets +CMOD=0. + +Figure 6: Alternating voice and fax call + +## 6.7 Select bearer service type +CBST + +Table 14: +CBST parameter command syntax + +| Command | Possible response(s) | +|-----------------------------------|------------------------------| +| +CBST=[<speed>[, <name>[, <ce>]]] | | +| +CBST? | +CBST: <speed>, <name>, <ce> | + +| | | +|---------|-----------------------------------------------------------------------------------------------| +| +CBST=? | +CBST: (list of supported <speed>s) , (list of supported <name>s) , (list of supported <ce>s) | +|---------|-----------------------------------------------------------------------------------------------| + +### Description + +Set command selects the bearer service <name> with data rate <speed>, and the connection element <ce> to be used when data calls are originated (refer 3GPP TS 22.002 [1]). Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls (refer +CSNS). + +Read command returns the current parameter values. + +Test command returns values supported as compound values. + +### Defined values + +NOTE: The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations of these subparameters are supported by GSM/UMTS (refer 3GPP TS 22.002 [1]). + +<speed>: integer type + +- 0 autobauding (automatic selection of the speed; this setting is possible in case of 3.1 kHz modem and non-transparent service) +- 1 300 bps (V.21) +- 2 1200 bps (V.22) +- 3 1200/75 bps (V.23) +- 4 2400 bps (V.22bis) +- 5 2400 bps (V.26ter) +- 6 4800 bps (V.32) +- 7 9600 bps (V.32) +- 12 9600 bps (V.34) +- 14 14400 bps (V.34) +- 15 19200 bps (V.34) +- 16 28800 bps (V.34) +- 17 33600 bps (V.34) +- 34 1200 bps (V.120) +- 36 2400 bps (V.120) +- 38 4800 bps (V.120) +- 39 9600 bps (V.120) +- 43 14400 bps (V.120) +- 47 19200 bps (V.120) +- 48 28800 bps (V.120) +- 49 38400 bps (V.120) +- 50 48000 bps (V.120) + +- 51 56000 bps (V.120) +- 65 300 bps (V.110) +- 66 1200 bps (V.110) +- 68 2400 bps (V.110 or X.31 flag stuffing) +- 70 4800 bps (V.110 or X.31 flag stuffing) +- 71 9600 bps (V.110 or X.31 flag stuffing) +- 75 14400 bps (V.110 or X.31 flag stuffing) +- 79 19200 bps (V.110 or X.31 flag stuffing) +- 80 28800 bps (V.110 or X.31 flag stuffing) +- 81 38400 bps (V.110 or X.31 flag stuffing) +- 82 48000 bps (V.110 or X.31 flag stuffing) +- 83 56000 bps (V.110 or X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI or RDI service in order to get FTM) +- 84 64000 bps (X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI service in order to get FTM) +- 115 56000 bps (bit transparent) +- 116 64000 bps (bit transparent) +- 120 32000 bps (PIAFS32k) +- 121 64000 bps (PIAFS64k) +- 130 28800 bps (multimedia) +- 131 32000 bps (multimedia) +- 132 33600 bps (multimedia) +- 133 56000 bps (multimedia) +- 134 64000 bps (multimedia) + +all other values below 256 are reserved by the present document. + +<name>: integer type + +- 0 data circuit asynchronous (UDI or 3.1 kHz modem) +- 1 data circuit synchronous (UDI or 3.1 kHz modem) +- 2 PAD Access (asynchronous) (UDI) +- 3 Packet Access (synchronous) (UDI) +- 4 data circuit asynchronous (RDI) +- 5 data circuit synchronous (RDI) +- 6 PAD Access (asynchronous) (RDI) +- 7 Packet Access (synchronous) (RDI) + +all other values below 128 are reserved by the present document. + +<ce>: integer type + +- 0 transparent +- 1 non-transparent +- 2 both, transparent preferred +- 3 both, non-transparent preferred + +### Implementation + +Mandatory when data calls implemented. + +## 6.8 Radio link protocol +CRLP + +**Table 15: +CRLP parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CRLP=[<iws>[, <mws>[, <T1>[, <N2>[, <ver>[, <T4>]]]]] | | +| +CRLP? | +CRLP: <iws>, <mws>, <T1>, <N2>[, <ver1>[, <T4>]]<br>[<CR><LF>+CRLP: <iws>, <mws>, <T1>, <N2>[, <ver2>[, <T4>]]<br>[...]] | +| +CRLP=? | +CRLP: (list of supported <iws>s) , (list of supported <mws>s) ,<br>(list of supported <T1>s) , (list of supported <N2>s) [, <ver1><br>[, (list of supported <T4>s) ] ]<br>[<CR><LF>+CRLP: (list of supported <iws>s) , (list of supported<br><mws>s) , (list of supported <T1>s) , (list of supported <N2>s)<br>[, <ver2>[, (list of supported <T4>s) ] ]<br>[...]] | + +### Description + +Radio link protocol (RLP) parameters used when non-transparent data calls are originated may be altered with set command. Available command subparameters depend on the RLP versions implemented by the device (e.g. <ver> may not be available if device supports only versions 0 and 1). + +NOTE 1: If radio link protocol is not used, but some other error correcting protocol (for transparent data calls), ITU-T Recommendation V.250 [14] Error Control Selection test command +ES=? may be used to indicate the presence of the protocol. + +Read command returns current settings for each supported RLP version <verx>. Only RLP parameters applicable to the corresponding <verx> are returned. + +Test command returns values supported as compound values. If MT/TA supports several RLP versions <verx>, the RLP parameter value ranges for each <verx> are returned on a separate line. + +### Defined values + +<ver>, <verx>: RLP version number in integer format; when version indication is not present it shall equal 0 + +NOTE 2: Versions 0 and 1 share the same parameter set. Read and test commands shall return only one line for this set (where <verx> is not present). + +<iws>, <mws>, <T1>, <N2>, <T4>: IWF to MS window size, MS to IWF window size, acknowledgement timer T1, retransmission attempts N2, re-sequencing period T4 in integer format (default values and value ranges depend on RLP version; refer 3GPP TS 24.022 [18]): T1 and T4 are in units of 10 ms. + +### Implementation + +Mandatory when RLP implemented. + +## 6.9 Service reporting control +CR + +**Table 16: +CR parameter command syntax** + +| Command | Possible response(s) | +|---------------|----------------------------------| +| +CR= [<mode>] | | +| +CR? | +CR: <mode> | +| +CR=? | +CR: (list of supported <mode>s) | + +### Description + +Set command controls whether or not intermediate result code +CR: <serv> is returned from the TA to the TE. If enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has determined which speed and quality of service will be used, before any error control or data compression reports are transmitted, and before the intermediate result code CONNECT is transmitted. + +NOTE: This command replaces ITU-T Recommendation V.250 [14] command Modulation Reporting Control +MR, which is not appropriate for use in the GSM/UMTS network. Possible error control (other than radio link protocol) and data compression reporting can be enabled with V.250 commands Error Control Reporting +ER and Data Compression Reporting +DR. + +Read command returns the current value of <mode>. + +Test command returns values supported as a compound value. + +### Defined values + +<mode>: integer type + +- 0 disables reporting +- 1 enables reporting + +<serv>: + +- ASYNC asynchronous transparent +- SYNC synchronous transparent +- REL ASYNC asynchronous non-transparent +- REL SYNC synchronous non-transparent +- GPRS [<L2P>] GPRS + +<L2P>: proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. + +### Implementation + +Mandatory when data calls implemented. + +## 6.10 Extended error report +CEER + +**Table 17: +CEER action command syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +CEER | +CEER: <report> | +| +CEER=? | | + +### Description + +Execution command causes the TA to return one or more lines of information text <report>, determined by the MT manufacturer, which should offer the user of the TA an extended report of the reason for + +- the failure in the last unsuccessful call setup (originating or answering) or in-call modification; +- the last call release; +- the last unsuccessful GPRS attach or unsuccessful PDP context activation; +- the last GPRS detach or PDP context deactivation. + +Typically, the text will consist of a single line containing the cause information given by the network in textual format. + +### Defined values + +<report>: the total number of characters, including line terminators, in the information text shall not exceed 2041 characters. + +Text shall not contain the sequence 0<CR> or OK<CR>. + +### Implementation + +Optional. + +## 6.11 Cellular result codes +CRC + +**Table 18: +CRC parameter command syntax** + +| Command | Possible response(s) | +|-----------------|-----------------------------------| +| +CRC=[ <mode> ] | | +| +CRC? | +CRC: <mode> | +| +CRC=? | +CRC: (list of supported <mode>s) | + +### Description + +Set command controls whether or not the extended format of incoming call indication or GPRS network request for PDP context activation or notification for VBS/VGCS calls is used. When enabled, an incoming call is indicated to the TE with unsolicited result code +CRING: <type> instead of the normal RING. + +Read command returns the current value of <mode>. + +Test command returns values supported as a compound value. + +NOTE 1: Similar command may be found in TTA IS-99 [15] and TTA IS-135 [16]. + +### Defined values + +<mode>: integer type + +0 disables extended format + +1 enables extended format + +<type>: + +ASYNC [, <priority> [, <subaddr>, <satype>]] asynchronous transparent + +SYNC [, <priority> [, <subaddr>, <satype>]] synchronous transparent + +REL ASYNC [, <priority> [, <subaddr>, <satype>]] asynchronous non-transparent + +REL SYNC [, <priority> [, <subaddr>, <satype>]] synchronous non-transparent + +FAX [, <priority> [, <subaddr>, <satype>]] facsimile (TS 62) + +VOICE [, <priority> [, <subaddr>, <satype>]] normal voice (TS 11) (see NOTE 2) + +VOICE/VIDEO [, <ccidx> [, <priority> [, <subaddr>, <satype>]]] voice or video call (see NOTE 2) + +VOICE/XXX [, <priority> [, <subaddr>, <satype>]] voice followed by data (BS 81) +(XXX is ASYNC, SYNC, REL ASYNC or REL SYNC) + +ALT VOICE/XXX [, <priority> [, <subaddr>, <satype>]] alternating voice/data, voice first (BS 61) + +ALT XXX/VOICE [, <priority> [, <subaddr>, <satype>]] alternating voice/data, data first (BS 61) + +ALT VOICE/FAX [, <priority> [, <subaddr>, <satype>]] alternating voice/fax, voice first (TS 61) + +ALT FAX/VOICE [, <priority> [, <subaddr>, <satype>]] alternating voice/fax, fax first (TS 61) + +GPRS <PDP\_type>, <PDP\_addr> [, [<L2P>] [, <APN>]] GPRS network request for PDP context activation + +VGC <GCA>, <GId>, <ackflag> [, <priority>] voice group call (TS 91) + +VBC <GCA>, <GId>, <ackflag> [, <priority>] voice broadcast call (TS 92) + +NOTE 2: The <type>=VOICE/VIDEO is used for voice and/or video calls. It is implementation specific whether this type will replace the <type>=VOICE or if both the types <type>=VOICE/VIDEO and <type>=VOICE are supported. + +<priority>: indicates the eMLPP priority level of the incoming call by paging, notification or setup message. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. + +<subaddr>: string type subaddress of format specified by <satype>. + +<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8) or RFC 4715 [122] appendix A. + +<ccidx>: integer type. Call identification number, see +CLCCS. + +<PDP\_type>, <PDP\_addr> and <APN>: string types as defined in the Define PDP Context (+CGDCONT) command. + +<L2P>: string type proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. If the MT is unable to announce to the TE the network's request (for example it is in V.250 online data state) the MT shall reject the request. No corresponding unsolicited result code shall be issued when the MT returns to a command state. + +<GCA>: string type (consisting of digits only) is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call area. See the commands +CAJOIN, +CAREJ and +CALCC. + +<GID>: string type (consisting of digits only) is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call identification. See the commands +CAJOIN, +CAREJ and +CALCC. + +<ackflag>: integer type proposes that a predefined confirmation procedure is to be used after the call is ended. The value 1 indicates that a predefined confirmation procedure is to be used after the call is ended. The value 0 indicates that no confirmation procedure is required. See the parameter <ack\_flag> of command +CALCC. + +### Implementation + +Mandatory when data or fax circuit mode calls are implemented, or for an MT supporting AT commands only and eMLPP or VGCS or VBS is implemented. + +## 6.12 HSCSD device parameters +CHSD + +**Table 19: +CHSD action command syntax** + +| Command | Possible response(s) | +|---------|--------------------------------------------------------------------------| +| +CHSD | +CHSD: <mclass>, <maxRx>, <maxTx>, <sum>, <codings><br>+CME ERROR: <err> | +| +CHSD=? | | + +### Description + +Execution command returns information about HSCSD features (refer 3GPP TS 22.034 [29]) supported by the MT/TA. Refer clause 9.2 for possible <err> values. + +The return information is only applicable in GERAN. + +### Defined values + +<mclass>: integer type; multislot class + +<maxRx>: integer type; maximum number of receive timeslots that MT can use + +<maxTx>: integer type; maximum number of transmit timeslots that MT can use + +<sum>: integer type; total number of receive and transmit timeslots that MT can use at the same time (per TDMA frame). The following applies in a HSCSD call: $1 \leq (\text{receive slots}) + (\text{transmit slots}) \leq \text{<sum>}$ + +<codings>: is a sum of integers each representing a supported channel coding (e.g. value 5 indicates that 4,8k and 9,6k channel codings are supported): + +- 1 4,8k full rate data traffic channel +- 4 9,6k full rate data traffic channel +- 8 14,4k full rate data traffic channel +- 16 28,8k full rate data traffic channel (only possible when 14.4k is supported) +- 32 32,0k full rate data traffic channel (only possible in a two-timeslot configuration) +- 64 43,2k full rate data traffic channel (only possible when 14.4k is supported) + +### Implementation + +Mandatory when HSCSD implemented. + +This command is only applicable to GERAN UEs. + +## 6.13 HSCSD transparent call configuration +CHST + +**Table 20: +CHST parameter command syntax** + +| Command | Possible response(s) | +|----------------------------|-------------------------| +| +CHST=[<wRx>[, <codings>]] | | +| +CHST? | +CHST: <wRx>, <codings> | +| +CHST=? | | + +### Description + +Set command controls parameters for transparent HSCSD calls in GERAN. Changing them during a call does not affect the current call. + +Read command returns the current values. + +NOTE: In UTRAN or E-UTRAN, values set with this command are not needed. The only applicable parameter is <SPEED>, which is set with +CBST command. + +### Defined values + +<wRx>: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate (<speed> subparameter from +CBST command) and <codings> + +<codings>: a sum of integers each representing a channel coding that is accepted for transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values) + +### Implementation + +Mandatory when transparent HSCSD implemented. + +This command is only applicable to GERAN UEs. + +## 6.14 HSCSD non-transparent call configuration +CHSN + +**Table 21: +CHSN parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| +CHSN=[<wAiur>[, <wRx>[, <topRx>[, <codings>]]]] | | +| +CHSN? | +CHSN: <wAiur>, <wRx>, <topRx>, <codings> | +| +CHSN=? | +CHSN: (list of supported <wAiur>s) , (list of supported <wRx>s) , (list of supported <topRx>s) , (list of supported <codings>s) | + +### Description + +Set command controls parameters for originating non-transparent HSCSD calls. Values may also be used during mobile terminated data call setup. In GERAN, changing <topRx> or <codings> value during a call does not affect the current call. In GERAN, changing of <wAiur> or <wRx> affects the current call only if <topRx> was non-zero when call was established. + +Read command returns the current values. + +Test command returns values supported as compound values. + +### Defined values + +<wAiur>: integer type; wanted air interface user rate. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate (<speed> subparameter from +CBST command), <codings>, and <wRx> (or <maxRx> from +CHSD command if <wRx>=0). Other values: + +- 1 9600 bps +- 2 14400 bps +- 3 19200 bps +- 4 28800 bps +- 5 38400 bps +- 6 43200 bps +- 7 57600 bps + +<wRx>: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected <wAiur> and <codings>. This parameter is only applicable to GERAN UEs. + +<topRx>: integer type; top value for <wRx> that user is going to request during the next established non-transparent HSCSD call. Default value 0 indicates that user is not going to change <wAiur>/<wRx> during the next call. This parameter is only applicable to GERAN UEs. + +<codings>: a sum of integers each representing a channel coding that is accepted for non-transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values). This parameter is only applicable to GERAN UEs. + +### Implementation + +Mandatory when non-transparent HSCSD implemented. + +## 6.15 HSCSD current call parameters +CHSC + +**Table 22: +CHSC action command syntax** + +| Command | Possible response(s) | +|---------|-------------------------------------| +| +CHSC | +CHSC: <rx>, <tx>, <aiur>, <coding> | +| +CHSC=? | | + +### Description + +Execution command returns information about current HSCSD call. If no HSCSD call is active, all parameters returned shall equal zero. If HSCSD call is active in UTRAN, all non-applicable parameters returned shall be equal to zero. (It is manufacturer specific whether non-zero information is returned in case of an active normal single-slot data call.) + +### Defined values + +<rx>: integer type; number of receive timeslots currently in use. This parameter is only applicable to GERAN UEs. + +<tx>: integer type; number of transmit timeslots currently in use. This parameter is only applicable to GERAN UEs. + +<aiur>: integer type; current air interface user rate (in case of transparent service this equals fixed network user rate) (refer +CHSN command for possible values). For the two-timeslot ECSD bit transparent configuration the following additional values apply: + +- 8 56000 bps + +9 64000 bps + +<coding>: is a sum of integers each representing the current channel coding (refer +CHSD command for possible values). This parameter is only applicable to GERAN UEs. + +#### Implementation + +Optional. + +## 6.16 HSCSD parameters report +CHSR + +**Table 23: +CHSR parameter command syntax** + +| Command | Possible response(s) | +|----------------|------------------------------------| +| +CHSR=[<mode>] | | +| +CHSR? | +CHSR: <mode> | +| +CHSR=? | +CHSR: (list of supported <mode>s) | + +#### Description + +Enabled command returns intermediate result code +CHSR: <type> from the TA to the TE when an HSCSD call is being set up. The result code represents the current (negotiated or renegotiated) HSCSD parameters. If enabled, the intermediate result code is transmitted at the point of the call setup negotiation where the TA has determined what type of an HSCSD connection will be used. Result code transmission is done after possible service (+CR), error control (+ER), and/or compression (+DR) reporting but before possible TE-TA rate (+ILRR) reporting and before the intermediate result code CONNECT is transmitted. The format of the intermediate result code is: + ++CHSR: <rx>, <tx>, <aiur>, <coding> + +For the value definitions, refer to +CHSN and +CHSC commands. For instance, for a non-transparent HSCSD call, result code '+CHSR: 2, 2, 4, 8' means that the call has two timeslots in both up- and downlink, the air interface user rate is 28800 bps, and the used channel coding TCH/F14.4. + +For HSCSD in UTRAN, all non-applicable parameters returned shall be equal to zero. + +Read command returns the current value of <mode>. + +Test command returns the values supported by the UE as a compound value. + +#### Defined values + +<mode>: integer type + +0 disables reporting + +1 enables reporting + +#### Implementation + +Mandatory when HSCSD implemented. + +## 6.17 HSCSD automatic user initiated upgrading +CHSU + +**Table 24: +CHSU parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CHSU=<mode> | | +| +CHSU? | +CHSU: <mode> | +| +CHSU=? | +CHSU: (list of supported <mode>s) | + +### Description + +Set command controls whether or not automatic user initiated service level upgrading shall be used for non-transparent HSCSD calls. "Automatic" means that, if enabled, the ME/TA shall use the UP bit in the received RLP frames to determine when to initiate user initiated service level upgrading (i.e. when to modify the +CHSN parameters <wAiur> and/or <wRx> for the current call). Refer to 3GPP TS 27.001 [41] for details on the interpretation of the UP bit(s). + +Read command returns the current value of <mode>. + +Test command returns values supported as a compound value. + +NOTE 1: The validity of the UP bit in the RLP frames depends on the result of the RLP negotiations. The UP bit shall only be used if the result of the RLP negotiations were successful with respect to the UP bit. + +NOTE 2: This command is only applicable in GERAN. + +### Defined values + +<mode>: integer type + +- 0 disables use of UP bit for upgrading +- 1 enables use of UP bit for upgrading + +### Implementation + +Optional. + +This command is only applicable to GERAN UEs. + +## 6.18 HSCSD non-transparent asymmetry configuration +CHSA + +**Table 25: +CHSA parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CHSA=<mode> | | +| +CHSA? | +CHSA: <mode> | +| +CHSA=? | +CHSA: (list of supported <mode>s) | + +### Description + +Set command controls the preferred asymmetry bias for non-transparent ECSD calls. Downlink biased asymmetry means that 8-PSK modulation is preferred downlink and GMSK modulation uplink. Uplink based asymmetry means that 8-PSK modulation is preferred uplink and GMSK downlink. Changing of <mode> affects the current call only if <topRx> (refer +CHSN) was non-zero when call was established. + +Read command returns the current value of <type>. + +Test command returns values supported by the MT/TA as a compound value. The <mode> subparameter range indirectly indicates the UE Type; range (0-1) indicates UE Type A and range (0-2) indicates UE Type B. + +NOTE 1: ECSD is also controlled by +CHSD, +CHSN and +CHST. + +NOTE 2: This command is only applicable in GERAN. + +### Defined values + +<mode>: integer type + +- 0 No preference +- 1 Downlink biased asymmetry + +## 2 Uplink biased asymmetry + +### Implementation + +Mandatory when non-transparent ECSD is implemented. + +This command is only applicable to GERAN UEs. + +## 6.19 Single numbering scheme +CSNS + +**Table 26: +CSNS parameter command syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CSNS= [<mode>] | | +| +CSNS? | +CSNS: <mode> | +| +CSNS=? | +CSNS: (list of supported <mode>s) | + +### Description + +Set command selects the bearer or teleservice to be used when mobile terminated single numbering scheme call is established. Parameter values set with +CBST command shall be used when <mode> equals to a data service. + +Read command returns the current value of <mode>. + +Test command returns values supported as a compound value. + +### Defined values + +<mode>: integer type + +- 0 voice +- 1 alternating voice/fax, voice first (TS 61) +- 2 fax (TS 62) +- 3 alternating voice/data, voice first (BS 61) +- 4 data +- 5 alternating voice/fax, fax first (TS 61) +- 6 alternating voice/data, data first (BS 61) +- 7 voice followed by data (BS 81) + +### Implementation + +Optional. + +## 6.20 Voice hangup control +CVHU + +**Table 27: +CVHU parameter command syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CVHU= [<mode>] | | +| +CVHU? | +CVHU: <mode> | +| +CVHU=? | +CVHU: (list of supported <mode>s) | + +### Description + +Set command selects whether ATH or "drop DTR" shall cause a voice connection to be disconnected or not. By voice connection is also meant alternating mode calls that are currently in voice mode. (See clause 6.6). + +Read command returns the current value of <mode>. + +Test command returns values supported as a compound value. + +NOTE: When <mode>=2, this command must be seen in conjunction with the ITU-T Recommendation V.250 [14] command &D. Else &D shall be ignored. + +### Defined values + +<mode>: integer type + +- 0 "Drop DTR" ignored but OK response given. ATH disconnects. +- 1 "Drop DTR" and ATH ignored but OK response given. +- 2 "Drop DTR" behaviour according to &D setting. ATH disconnects. + +### Implementation + +Optional + +## 6.21 CCITT V.120 [36] rate adaption protocol +CV120 + +**Table 28: +CV120 parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CV120=[<rah>[, <mfm>[, <mode>[, <llineg>[, <assign>[, <negtype>]]]]] | | +| +CV120? | +CV120: <rah>, <mfm>, <mode>, <llineg>, <assign>, <negtype> | +| +CV120=? | +CV120: (list of supported <rah>s), (list of supported <mfm>s), (list of supported <mode>s), (list of supported <llineg>s), (list of supported <assign>s), (list of supported <negtype>s) | + +### Description + +Set command sets the values of the V.120 protocol parameters (defined in CCITT Recommendation V.120 [36]) that are carried in the GSM BC and/or LLC information elements. + +Read command returns current settings for the V.120 parameters. + +Test command returns values supported as compound values. + +### Defined values + +<rah>: integer type + +- 0 rate adaption header not included +- 1 rate adaption header included (mandatory for protocol sensitive modes). + +<mfm>: integer type + +- 0 multiple frame establishment not supported, only UI frames allowed +- 1 multiple frame establishment supported, both I and UI frames allowed. + +<mode>: integer type + +0 bit transparent mode of operation + +1 protocol sensitive mode of operation. + +<llineg>: integer type + +0 no negotiation, LLI = 256 only + +1 negotiation allowed. + +NOTE: <negtype> indicates the connection over which the negotiation is performed. + +<assign>: integer type + +0 message originator is "default assignee" + +1 message originator is "assignor only". + +<negtype>: integer type + +0 negotiation is done using logical link zero + +1 negotiation is done with USER INFORMATION messages on a temporary signalling connection. + +All possible modes of V.120 operation are not supported. However, in order to accommodate possible future additions, the complete set of parameters is included in the command. + +The permitted values are: 1, 1 or 0, 1, 0, 0, 0. + +A recommended set of default values is: 1, 1, 1, 0, 0, 0. + +#### Implementation + +Mandatory, if the MT supports V.120 interworking. + +## 6.22 Settings date format +CSDF + +**Table 29: +CSDF parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------|------------------------------------------------------------------------------------------------| +| +CSDF=[ [<mode>] [, <auxmode>] ] | +CME ERROR: <err> | +| +CSDF? | +CSDF: <mode> [, <auxmode>]<br>+CME ERROR: <err> | +| +CSDF=? | +CSDF: (list of supported <mode>s)<br>[, (list of supported <auxmode>s) ]<br>+CME ERROR: <err> | + +#### Description + +This command sets the date format via MMI of the date information presented to the user, which is specified by use of the <mode> parameter. The <mode> affects the date format on the phone display and doesn't affect the date format of the AT command serial interface. The command also sets the date format of the TE-TA interface, which is specified by use of the <auxmode> parameter (e.g. the <auxmode> affects the <time> of +CCLK and +CALA). If the parameter is omitted ("+CSDF=","+CSDF=<mode>","+CSDF=, <auxmode>"), then this sets the default value. Refer clause 9.2 for possible <err> values. + +Read command returns the current settings. + +Test command returns values supported as compound values. + +**Defined values** + +<mode>: integer type + +NOTE 1: It is manufacturer specific which modes that are supported. + +1 DD-MMM-YYYY + +NOTE 2: Presentation of MMM is language dependent. + +2 DD-MM-YY + +3 MM/DD/YY + +4 DD/MM/YY + +5 DD.MM.YY + +6 YYMMDD + +7 YY-MM-DD + +8-255 Manufacturer specific + +<auxmode>: integer type + +1 yy/MM/dd + +2 yyyy/MM/dd + +all other values are reserved by the present document. + +NOTE 3: The <time> format of +CCLK and +CALA "yy/MM/dd,hh:mm:ss±zz" when <auxmode>=1 and it is "yyyy/MM/dd,hh:mm:ss±zz" when <auxmode>=2. If the MT does not support time zone information then the three last characters may be omitted (see +CCLK command). + +**Implementation** + +Optional + +## 6.23 Silence command +CSIL + +**Table 30: +CSIL parameter command syntax** + +| Command | Possible response(s) | +|----------------|---------------------------------------------------------| +| +CSIL=[<mode>] | +CME ERROR: <err> | +| +CSIL? | +CSIL: <mode><br>+CME ERROR: <err> | +| +CSIL=? | +CSIL: (list of supported <mode>s)<br>+CME ERROR: <err> | + +**Description** + +Set command enables/disables the silent mode. When the phone is in silent mode, all sounds from MT are suppressed except voice. Refer clause 9.2 for possible <err> values. + +Read command reads the current setting. + +Test command lists the supported modes as a compound value. + +**Defined values** + +<mode>: integer type. The default value is manufacturer specific. + +- 0 Silent mode off +- 1 Silent mode on + +**Implementation** + +Optional + +## 6.24 Settings time format +CSTF + +**Table 31: +CSTF parameter command syntax** + +| Command | Possible response(s) | +|----------------|---------------------------------------------------------| +| +CSTF=[<mode>] | +CME ERROR: <err> | +| +CSTF? | +CSTF: <mode><br>+CME ERROR: <err> | +| +CSTF=? | +CSTF: (list of supported <mode>s)<br>+CME ERROR: <err> | + +**Description** + +Set command sets the time format of the time information presented to the user. Refer clause 9.2 for possible <err> values. + +Read command reads the current setting. + +Test command reads the supported <modes>s as a compound value. + +**Defined values** + +<mode>: integer type. The default value is manufacturer specific. + +- 1 HH:MM (24 hour clock) +- 2 HH:MM a.m./p.m. +- 3-7 Manufacturer specific + +**Implementation** + +Optional + +## 6.25 ITU-T Recommendation V.250 [14] call control commands + +**Table 32: V.250 call control commands** + +| Command | Clause | Impl. | Used in the present document | +|----------------------|--------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| D[<dial_string>] [;] | 6.3.1 | mand. | originates a call | +| T | 6.3.2 | mand. | ignored (select tone dialling) | +| P | 6.3.3 | mand. | ignored (select pulse dialling) | +| A | 6.3.5 | mand. | answer a call | +| H[<value>] | 6.3.6 | mand. | hang-up a single mode call; for alternate mode call refer clause "Hangup call +CHUP" (only value equal to zero needed) | +| O[<value>] | 6.3.7 | mand. | returns TA to online data state from online command mode (only value equal to zero needed) | +| S0=[<value>] | 6.3.8 | mand. | sets the number of call indications (rings) before automatically answering the call; value equalling zero disables automatic answering and is the default | +| S6=[<value>] | 6.3.9 | mand. | ignored (pause before blind dialling) | +| S7=[<value>] | 6.3.10 | mand. | sets number of seconds to wait for completion of call answering or originating procedure before giving up and disconnecting | +| S8=[<value>] | 6.3.11 | mand. | sets number of seconds to wait when comma dial modifier encountered in dial string of D command (default is 2 seconds) | +| S10=[<value>] | 6.3.12 | mand. | sets number of tenths of seconds to wait before disconnecting after TA has indicated the absence of received line signal | +| L[<value>] | 6.3.13 | mand. | ignored (monitor speaker loudness) | +| M[<value>] | 6.3.14 | mand. | ignored (monitor speaker mode) | + +Implementation of commands marked as mandatory is mandatory only if call control functionality is supported. + +## 6.26 ITU-T Recommendation V.250 [14] data compression commands + +**Table 33: V.250 data compression commands** + +| Command | Clause | Impl. | Used in the present document | +|--------------------------------------|--------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +DS=[<dir>[, <neg>[, <P1>[, <P2>]]]] | 6.6.1 | mand.<br>when<br>V.42bis | controls ITU-T Recommendation V.42bis data compression functions; for subparameter defaults refer 3GPP TS 24.022 [18] | +| +DR=[<value>] | 6.6.2 | mand.<br>when<br>V.42bis | determines whether the use of V.42bis is informed using intermediate result code +DR: <type> before going online data state after call answering or originating | + +## 6.27 Initiate eCall +CECALL + +**Table 6.27-1: +CECALL parameter command syntax** + +| Command | Possible response | +|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| +CECALL=<type_of_eCall>[, <format>, <msd_data_length>, <msd_data>] | | +| +CECALL? | +CECALL: [<type_of_eCall>[, <format>, <msd_data_length>, <msd_data>[, <format>, <msd_data>, [...]]]] | + +| | | +|-----------|---------------------------------------------------------------------------------| +| +CECALL=? | +CECALL: (list of supported <type_of_eCall>s)[, (list of supported <format>s) ] | +|-----------|---------------------------------------------------------------------------------| + +### Description + +Set command is used to trigger an eCall to the network or to provide an updated MSD to the network during an ongoing eCall. Based on the configuration selected, it can be used to either trigger a test call, a reconfiguration call, a manually initiated eCall or an automatically initiated eCall. The parameters <format>, <msd\_data\_length> and <msd\_data> are included if the MSD is provided by the application. If the parameters are not included, the MSD is provided to the network by the MT. + +Read command returns the <type\_of\_eCall> that is currently in progress, if any. The MT may also return the <format>s and the <msd\_data>s of the eCall as provided to the network. The parameters of the response to the read command will be cleared when the eCall in progress is terminated. + +Test command returns the supported values as compound values. + +### Defined values + +<type\_of\_eCall>: integer type. Indicates the type of eCall. + +- 0 test call +- 1 reconfiguration call eCall +- 2 manually initiated eCall +- 3 automatically initiated eCall + +<format>: integer type. Indicates the format of the provided eCall MSD. + +- 1 binary format + +<msd\_data\_length>: integer type. Indicates the number of octets of the <msd\_data> information element. + +<msd\_data>: string type. Minimum set of data, see CEN EN 15722:2015 [157]. The type of string is in the format specified by <format>. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. + +## 6.28 eCall Notification +CECN + +**Table 6.28-1: +CECN parameter command syntax** + +| Command | Possible response | +|--------------|---------------------------------| +| +CECN= [<n>] | | +| +CECN? | +CECN: <n> | +| +CECN=? | +CECN: (list of supported <n>s) | + +### Description + +Set command is used to control the presentation of an unsolicited result code +CECN: <data\_type> when <n>=1 and the network requests an updated MSD during an eCall. As a result of the unsolicited result code +CECN, the AT-command +CECALL can be used to provide an updated MSD for the eCall. + +NOTE: The parameter <data\_type>=0 is used to inform that the updated MSD will be provided to the network by the MT. + +Read command returns the status of result code presentation <n>. + +Test command returns the supported values as a compound value. + +#### Defined values + +<n>: integer type. Enables or disables reporting of unsolicited result code +CECN. + +- 0 disable presentation of the unsolicited result code +- 1 enable presentation of the unsolicited result code + +<data\_type>: integer type. Indicates the type of additional data for the eCall. + +- 0 updated MSD for the eCall is provided to the network by the MT +- 1 request for updated MSD + +#### Implementation + +Optional. + +## 6.29 Informative examples + +The alternating mode call handling (voice and fax, or voice and data) and the data call setup commands are defined such that the dialling command of ITU-T Recommendation V.250 [14] (D) still always originates a call. The purpose is to support all current TE applications using the dialling command as default. Fax calls are controlled following the rules of ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12] standards. + +An example where a voice call is originated: + +``` +ATD+1 812 555673I; (type of address defaults to 145, CLI presentation is restricted for this call) +OK (call setup was successful) +``` + +An example where a voice call is attempted from a phonebook: + +``` +ATD>"Doe Joe"G; (enable CUG control for this call) ++CME ERROR: 22 (entry "Doe Joe" is not found) +``` + +Also supplementary services can be controlled using dial command according to 3GPP TS 22.030 [19]. An example of call forwarding on no reply for telephony with the adjustment of the no reply condition timer on 25 seconds: + +``` +ATD**61*+1812555673*11*25# +OK (modification was successful) +``` + +Two new commands are created for controlling the alternating mode calls. First one, Call Mode (+CMOD), selects between single and alternating mode. Because this is a crucial command, it is defined that the value is set back to zero (single mode) after every successfully originated alternating mode call. Also on power-up and factory or user resets, the value is set to zero. The second new command, Hangup Call (+CHUP), is not a replacement of ITU-T Recommendation V.250 [14] command H, but a command which reliably disconnects the call in GSM/UMTS network. This is defined because the H command is used to switch from fax or data mode to voice mode. + +The setting of GSM/UMTS bearer service (data circuit duplex asynchronous and synchronous, PAD access circuit asynchronous, or data packet duplex synchronous), is done with Select Bearer Service Type (+CBST). It chooses one of the four mentioned bearer services, the data rate of the service (or actually the modulation when modem IWFs are used), and enables or disables RLP. Command Radio Link Protocol (+CRLP) is used to set the RLP parameters in the radio path. + +Service Reporting Control command (+CR) is defined similarly as the reporting of modulation, V.18, error control, and data compression which are ITU-T Recommendation V.250 [14] features used to show information about the type of the established connection before the CONNECT intermediate result code. +CR command has one subparameter which specifies whether the intermediate result code +CR: <serv> is returned or not. The result code is typically returned before any ITU-T Recommendation V.250 [14] reporting result codes. An example of setting up an asynchronous 9600 bit/s modem connection with service reporting: + +``` + +AT+CBST=7,0,1 (asynchronous modem 9600 bit/s and RLP) +OK +AT+CR=1 (enable reporting) +OK +ATD1234567890 ++CR: REL ASYNC +CONNECT 9600 + +``` + +As GSM/UMTS network offers more information about the reason of the failure in call originating and answering than normal PSTN, it is useful to add an extra command to return this information to the TE. This information should not be returned always after unsuccessful call originating or answering, because many TE applications look for just the regular NO CARRIER, BUSY, NO ANSWER and CONNECT messages. Action command Extended Error Report (+CEER) does not have any subparameters, and it returns the cause of the latest call setup failure. This information can be the textual presentation of the GSM/UMTS network failure code (refer 3GPP TS 24.008 [8] Annex H), or some other information defined by the TA manufacturer. + +## 7 Network service related commands + +### 7.0 General + +This clause describes network related commands, which are not covered in call control clause of the present document. Commands include supplementary service handling, MSISDN query, MT and network facility locking, and network registration information query. + +### 7.1 Subscriber number +CNUM + +**Table 34: +CNUM action command syntax** + +| Command | Possible response(s) | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CNUM | +CNUM: [<alpha1>], <number1>, <type1>[, <speed>, <service>[, <itc>]]<br>[<CR><LF>+CNUM: [<alpha2>], <number2>, <type2>[, <speed>, <service><br>[, <itc>]]<br>[...]]<br><br>+CME ERROR: <err> | +| +CNUM=? | | + +#### Description + +Action command returns the MSISDNs related to the subscriber (this information can be stored in the SIM/UICC or in the MT). When storing information in the SIM/UICC, if the currently selected card slot contains a SIM card or a UICC with an active GSM application, the information is stored in the EF<sub>MSISDN</sub> under DF<sub>Telecom</sub>. If the currently selected card slot contains a UICC with an active USIM application, the information is stored in the EF<sub>MSISDN</sub> under ADF<sub>USIM</sub>. If subscriber has different MSISDN for different services, each MSISDN is returned on a separate line. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<alphax>: optional alphanumeric string associated with <numberx>; used character set should be the one selected with command select TE character set +CSCS + +<numberx>: string type phone number of format specified by <typex> + +<typex>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<speed>: integer type as defined in clause 6.7 + +<service>: integer type (service related to the phone number) + +- 0 asynchronous modem +- 1 synchronous modem +- 2 PAD Access (asynchronous) +- 3 Packet Access (synchronous) +- 4 voice +- 5 fax + +all other values below 128 are reserved by the present document + +<itc>: integer type (information transfer capability) + +- 0 3,1 kHz +- 1 UDI + +### Implementation + +Optional. + +## 7.2 Network registration +CREG + +**Table 35: +CREG parameter command syntax** + +| Command | Possible response(s) | +|-------------|-----------------------------------------------------------------------------------| +| +CREG=[<n>] | +CME ERROR: <err> | +| +CREG? | +CREG: <n>,<stat>[, [<lac>], [<ci>], [<AcT>]<br>[, <cause_type>, <reject_cause>]] | +| +CREG=? | +CREG: (list of supported <n>s) | + +### Description + +Set command controls the presentation of an unsolicited result code +CREG: <stat> when <n>=1 and there is a change in the MT's circuit mode network registration status in GERAN/UTRAN/E-UTRAN, or unsolicited result code +CREG: <stat>[, [<lac>], [<ci>], [<AcT>]] when <n>=2 and there is a change of the network cell in GERAN/UTRAN/E-UTRAN. The parameters <AcT>, <lac> and <ci> are sent only if available. The value <n>=3 further extends the unsolicited result code with [, <cause\_type>, <reject\_cause>], when available, when the value of <stat> changes. + +NOTE 1: If the MT also supports one or more of the GPRS services, EPS services or 5G services, the +CGREG command and +CGREG: result codes, the +CEREG command and +CEREG: result codes and the +C5GREG command and +C5GREG: result codes apply to the registration status and location information for those services. + +Read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. Location information elements <lac>, <ci> and <AcT>, if available, are returned only when <n>=2 and MT is registered in the network. The parameters [, <cause\_type>, <reject\_cause>], if available, are returned when <n>=3. Refer clause 9.2 for possible <err> values. + +The access technology of the serving cell parameter, <AcT>, should not be used in terminals capable of only one access technology. + +Test command returns values supported as a compound value. + +## Defined values + +<n>: integer type + +- 0 disable network registration unsolicited result code +- 1 enable network registration unsolicited result code +CREG: <stat> +- 2 enable network registration and location information unsolicited result code +CREG: <stat>[, [<lac>], [<ci>], [<AcT>]] +- 3 enable network registration, location information and cause value information unsolicited result code +CREG: <stat>[, [<lac>], [<ci>], [<AcT>][, <cause\_type>, <reject\_cause>]] + +<stat>: integer type; circuit mode registration status. + +- 0 not registered, MT is not currently searching a new operator to register to +- 1 registered, home network +- 2 not registered, but MT is currently searching a new operator to register to +- 3 registration denied +- 4 unknown (e.g. out of GERAN/UTRAN/E-UTRAN coverage) +- 5 registered, roaming +- 6 registered for "SMS only", home network (applicable only when <AcT> indicates E-UTRAN) +- 7 registered for "SMS only", roaming (applicable only when <AcT> indicates E-UTRAN) +- 8 attached for emergency bearer services only (see NOTE 2) (not applicable) +- 9 registered for "CSFB not preferred", home network (applicable only when <AcT> indicates E-UTRAN) +- 10 registered for "CSFB not preferred", roaming (applicable only when <AcT> indicates E-UTRAN) +- 11 attached for access to RLOS (see NOTE 2a) (applicable only when <AcT> indicates E-UTRAN) + +NOTE 2: 3GPP TS 24.008 [8] and 3GPP TS 24.301 [83] specify the condition when the MT is considered as attached for emergency bearer services. + +NOTE 2a: 3GPP TS 24.301 [83] specifies the condition when the MT is considered as attached for access to RLOS. + +<lac>: string type; two byte location area code (when <AcT> indicates value 0 to 6), or tracking area code (when <AcT> indicates value 7). In hexadecimal format (e.g. "00C3" equals 195 in decimal). + +<ci>: string type; four byte GERAN/UTRAN/E-UTRAN cell ID in hexadecimal format. + +<AcT>: integer type; access technology of the serving cell. + +- 0 GSM +- 1 GSM Compact +- 2 UTRAN +- 3 GSM w/EGPRS (see NOTE 3) +- 4 UTRAN w/HSDPA (see NOTE 4) +- 5 UTRAN w/HSUPA (see NOTE 4) +- 6 UTRAN w/HSDPA and HSUPA (see NOTE 4) +- 7 E-UTRAN + +- 8 EC-GSM-IoT (A/Gb mode) (see NOTE 5) +- 9 E-UTRAN (NB-S1 mode) (see NOTE 6) +- 10 E-UTRA connected to a 5GCN (see NOTE 7) (not applicable) +- 11 NR connected to a 5GCN (see NOTE 7) (not applicable) +- 12 NG-RAN (not applicable) +- 13 E-UTRA-NR dual connectivity (see NOTE 8) +- 14 satellite E-UTRAN (NB-S1 mode) (see NOTE 9) +- 15 satellite E-UTRAN (WB-S1 mode) +- 16 satellite NG-RAN (not applicable) + +NOTE 3: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS. + +NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA. + +NOTE 5: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT. + +NOTE 6: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode). + +NOTE 7: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5GCN. + +NOTE 8: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core. + +NOTE 9: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving satellite cell supports satellite NB-IoT, which corresponds to E-UTRAN in NB-S1 mode. + +<cause\_type>: integer type; indicates the type of <reject\_cause>. + +- 0 Indicates that <reject\_cause> contains an MM cause value, see 3GPP TS 24.008 [8] Annex G. +- 1 Indicates that <reject\_cause> contains a manufacturer specific cause. + +<reject\_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by <cause\_type>. + +## Implementation + +Optional. + +This command is not applicable to UEs in NG-RAN or satellite NG-RAN. + +## 7.3 PLMN selection +COPS + +**Table 36: +COPS parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +COPS=[<mode>[, <format>[, <oper>[, <AcT>[, <regtype>]]]]] | +CME ERROR: <err> | +| +COPS? | +COPS: <mode>[, <format>, <oper>[, <AcT>]]<br>+CME ERROR: <err> | +| +COPS=? | +COPS: [list of supported (<stat>, long alphanumeric <oper>, short alphanumeric <oper>, numeric <oper>[, <AcT>]) s] [, , (list of supported <mode>s) , (list of supported <format>s) ]<br>+CME ERROR: <err> | + +### Description + +Set command forces an attempt to select and register to the GSM/UMTS/EPS/5GS network operator using the SIM/USIM card installed in the currently selected card slot. <mode> is used to select whether the selection is done automatically by the MT or is forced by this command to operator <oper> (it shall be given in format <format>) to a certain access technology, indicated in <AcT>. <regtype> indicates if the registration procedure shall be performed for disaster roaming service (see 3GPP TS 24.501 [161]). If <regtype> is not included then the UE performs a normal registration i.e. a registration not for disaster roaming service (see 3GPP TS 24.501 [161]). If the selected operator is not available, no other operator shall be selected (except <mode>=4). If the selected access technology is not available, then the same operator shall be selected in other access technology. The selected operator name format shall apply to further read commands (+COPS?) also. <mode>=2 forces an attempt to deregister from the network. The selected mode affects to all further network registration (e.g. after <mode>=2, MT shall be unregistered until <mode>=0 or 1 is selected). Refer clause 9.2 for possible <err> values. This command should be abortable when registration/deregistration attempt is made. + +Read command returns the current mode, the currently selected operator and the current Access Technology. If no operator is selected, <format>, <oper> and <AcT> are omitted. + +Test command returns a set of five parameters, each representing an operator present in the network. A set consists of an integer indicating the availability of the operator <stat>, long and short alphanumeric format of the name of the operator, numeric format representation of the operator and access technology. Any of the formats may be unavailable and should then be an empty field. The list of operators shall be in order: home network, networks referenced in SIM or active application in the UICC (GSM or USIM) in the following order: HPLMN selector, User controlled PLMN selector, Operator controlled PLMN selector and PLMN selector (in the SIM or GSM application), and other networks. + +It is recommended (although optional) that after the operator list TA returns lists of supported <mode>s and <format>s. These lists shall be delimited from the operator list by two commas. + +The access technology selected parameters, <AcT>, should not be used in terminals capable of only one access technology. Selection of <AcT> does not limit the capability to cell reselections, even though an attempt is made to select an access technology, the phone may still re-select a cell in another access technology. + +### Defined values + +<mode>: integer type + +- 0 automatic (<oper> field is ignored) +- 1 manual (<oper> field shall be present, and <AcT> optionally) +- 2 deregister from network + +- 3 set only <format> (for read command +COPS?), do not attempt registration/deregistration (<oper> and <AcT> fields are ignored); this value is not applicable in read command response +- 4 manual/automatic (<oper> field shall be present); if manual selection fails, automatic mode (<mode>=0) is entered + +<format>: integer type + +- 0 long format alphanumeric <oper> +- 1 short format alphanumeric <oper> +- 2 numeric <oper> + +<regtype>: integer type + +- 0 register not for disaster roaming service. +- 1 register for disaster roaming service. + +<oper>: string type; <format> indicates if the format is alphanumeric or numeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [9]); numeric format is the Location Area Identification number (refer 3GPP TS 24.008 [8] clause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU-T Recommendation E.212 [10] Annex A, plus a two BCD digit network code, which is administration specific; returned <oper> shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 3)(network code digit 2)(network code digit 1) + +<stat>: integer type + +- 0 unknown +- 1 available +- 2 current +- 3 forbidden +- 4 forbidden and supports disaster roaming + +<AcT>: integer type; access technology selected + +- 0 GSM +- 1 GSM Compact +- 2 UTRAN +- 3 GSM w/EGPRS (see NOTE 1) +- 4 UTRAN w/HSDPA (see NOTE 2) +- 5 UTRAN w/HSUPA (see NOTE 2) +- 6 UTRAN w/HSDPA and HSUPA (see NOTE 2) +- 7 E-UTRAN +- 8 EC-GSM-IoT (A/Gb mode) (see NOTE 3) +- 9 E-UTRAN (NB-S1 mode) (see NOTE 4) +- 10 E-UTRA connected to a 5GCN (see NOTE 5) +- 11 NR connected to a 5GCN (see NOTE 5) +- 12 NG-RAN + +- 13 E-UTRA-NR dual connectivity (see NOTE 6) +- 14 satellite E-UTRAN (NB-S1 mode) (see NOTE 7) +- 15 satellite E-UTRAN (WB-S1 mode) +- 16 satellite NG-RAN + +NOTE 1: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS. + +NOTE 2: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA. + +NOTE 3: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT. + +NOTE 4: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode). + +NOTE 5: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5G CN. This value is not applicable in set command. + +NOTE 6: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core. + +NOTE 7: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving satellite cell supports satellite NB-IoT, which corresponds to E-UTRAN in NB-S1 mode. + +## Implementation + +Optional. + +## 7.4 Facility lock +CLCK + +**Table 37: +CLCK action command syntax** + +| Command | Possible response(s) | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CLCK=<fac>, <mode> [, <passwd> [, <class>]] | +CME ERROR: <err><br><br><b>when <mode>=2 and command successful:</b><br>+CLCK: <status> [, <class1>]<br>[<CR><LF>+CLCK: <status>, <class2>]<br>[...]] | +| +CLCK=? | +CLCK: (list of supported <fac>s)<br><br>+CME ERROR: <err> | + +### Description + +Execute command is used to lock, unlock or interrogate a MT or a network facility <fac>. Password is normally needed to do such actions. When querying the status of a network service (<mode>=2) the response line for 'not active' case (<status>=0) should be returned only if service is not active for any <class>. Refer clause 9.2 for possible <err> values. This command should be abortable when network facilities are set or interrogated. + +Call barring facilities are based on supplementary services (refer 3GPP TS 22.088 [6]). The interaction of these with other commands based on other supplementary services is described in the specification of the relevant supplementary service. + +Test command returns facility values supported as a compound value. + +### Defined values + +3GPP + +<fac> values reserved by the present document: + +- "CS" CNTRL (lock CoNTRoL surface (e.g. phone keyboard)) +- "PS" PH-SIM (lock PHone to SIM/UICC card installed in the currently selected card slot) (MT asks password when other than current SIM/UICC card inserted; MT may remember certain amount of previously used cards thus not requiring password when they are inserted) +- "PF" lock Phone to the very First inserted SIM/UICC card (also referred in the present document as PH-FSIM) (MT asks password when other than the first SIM/UICC card is inserted) +- "SC" SIM (lock SIM/UICC card installed in the currently selected card slot) (SIM/UICC asks password in MT power-up and when this lock command issued) +- "AO" BAOC (Barr All Outgoing Calls) (refer 3GPP TS 22.088 [6] clause 1) +- "OI" BOIC (Barr Outgoing International Calls) (refer 3GPP TS 22.088 [6] clause 1) +- "OX" BOIC-exHC (Barr Outgoing International Calls except to Home Country) (refer 3GPP TS 22.088 [6] clause 1) +- "AI" BAIC (Barr All Incoming Calls) (refer 3GPP TS 22.088 [6] clause 2) +- "IR" BIC-Roam (Barr Incoming Calls when Roaming outside the home country) (refer 3GPP TS 22.088 [6] clause 2) +- "NT" barr incoming calls from numbers Not stored to TA memory +- "NM" barr incoming calls from numbers Not stored to MT memory +- "NS" barr incoming calls from numbers Not stored to SIM/UICC memory +- "NA" barr incoming calls from numbers Not stored in Any memory +- "AB" All Barring services (refer 3GPP TS 22.030 [19]) (applicable only for <mode>=0) +- "AG" All outGoing barring services (refer 3GPP TS 22.030 [19]) (applicable only for <mode>=0) +- "AC" All inComing barring services (refer 3GPP TS 22.030 [19]) (applicable only for <mode>=0) +- "FD" SIM card or active application in the UICC (GSM or USIM) fixed dialling memory feature (if PIN2 authentication has not been done during the current session, PIN2 is required as <passwd>) +- "PN" Network Personalization (refer 3GPP TS 22.022 [33]) +- "PU" network sUset Personalization (refer 3GPP TS 22.022 [33]) +- "PP" service Provider Personalization (refer 3GPP TS 22.022 [33]) +- "PC" Corporate Personalization (refer 3GPP TS 22.022 [33]) + +<mode>: integer type + +- 0 unlock +- 1 lock +- 2 query status + +<status>: integer type + +- 0 not active +- 1 active + +<passwd>: string type; shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD + +<classx> is a sum of integers each representing a class of information (default 7 - voice, data and fax): + +- 1 voice (telephony) +- 2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) +- 4 fax (facsimile services) +- 8 short message service +- 16 data circuit sync +- 32 data circuit async +- 64 dedicated packet access +- 128 dedicated PAD access + +### Implementation + +The call barring supplementary service control is mandatory for MT supporting AT commands only and not supporting the control through dial command D. + +## 7.5 Change password +CPWD + +**Table 38: +CPWD action command syntax** + +| Command | Possible response(s) | +|-------------------------------|--------------------------------------------------------------------| +| +CPWD=<fac>,<oldpwd>,<newpwd> | +CME ERROR: <err> | +| +CPWD=? | +CPWD: list of supported (<fac>,<pwdlength>)s<br>+CME ERROR: <err> | + +### Description + +Action command sets a new password for the facility lock function defined by command Facility Lock +CLICK. Refer clause 9.2 for possible <err> values. + +Test command returns a list of pairs which present the available facilities and the maximum length of their password. + +### Defined values + +<fac>: + +"P2" SIM PIN2 + +refer Facility Lock +CLICK for other values + +<oldpwd>, <newpwd>: string type; <oldpwd> shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD and <newpwd> is the new password; maximum length of password can be determined with <pwdlength> + +<pwdlength>: integer type maximum length of the password for the facility + +### Implementation + +Optional. + +## 7.6 Calling line identification presentation +CLIP + +**Table 39: +CLIP parameter command syntax** + +| Command | Possible response(s) | +|-------------|---------------------------------| +| +CLIP=[<n>] | | +| +CLIP? | +CLIP: <n>, <m> | +| +CLIP=? | +CLIP: (list of supported <n>s) | + +### Description + +This command refers to the supplementary service CLIP (Calling Line Identification Presentation) according to 3GPP TS 22.081 [3] and OIP (Originating Identification Presentation) according to 3GPP TS 24.607 [119] that enables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP / OIP in the network. + +When <n>=1, the presentation of the calling line identity at the TE is enabled and when the calling subscriber allows, the unsolicited result code +CLIP: <number>, <type>[, <subaddr>, <stype>[, [<alpha>] [, <CLI\_validity>]]] is returned after every RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. The unsolicited result code +CLIP does not support numbers of the SIP URI format. + +When <n>=0, the presentation of the calling line identity at the TE with unsolicited result code +CLIP is disabled. + +The calling line identity can also be reported in unsolicited result codes +CMCCSS<x>/ +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x>/ +CMCCSSEND support numbers of the SIP URI format. Read command gives the status of <n>, and also triggers an interrogation of the provision status of the CLIP supplementary service according to 3GPP TS 22.081 [3] and OIP supplementary service according to 3GPP TS 24.607 [119] (given in <m>). + +Read command returns the current settings. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type (parameter sets/shows the result code presentation status to the TE). + +- 0 disable +- 1 enable + +<m>: integer type (parameter shows the subscriber CLIP / OIP service status in the network). + +- 0 CLIP / OIP not provisioned +- 1 CLIP / OIP provisioned +- 2 unknown (e.g. no network, etc.) + +<number>: string type phone number of format specified by <type>. + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). + +<subaddr>: string type subaddress of format specified by <stype> + +<stype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8). + +<alpha>: optional string type alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command select TE character set +CSCS. + +<CLI\_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). + +- 0 CLI valid +- 1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user") +- 2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service") +- 3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone") +- 4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable"). + +When CLI is not available (<CLI\_validity>=2, <CLI\_validity>=3 or <CLI\_validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7). + +When CLI has been withheld by the originator, (<CLI\_validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. + +#### Implementation + +Optional. + +## 7.7 Calling line identification restriction +CLIR + +**Table 40: +CLIR parameter command syntax** + +| Command | Possible response(s) | +|-------------|---------------------------------| +| +CLIR=[<n>] | | +| +CLIR? | +CLIR: <n>, <m> | +| +CLIR=? | +CLIR: (list of supported <n>s) | + +#### Description + +This command refers to the supplementary service CLIR (Calling Line Identification Restriction) according to 3GPP TS 22.081 [3] and OIR (Originating Identification Restriction) according to 3GPP TS 24.607 [119] that allows a calling subscriber to enable or disable the presentation of the calling line identity (CLI) to the called party when originating a call. + +Set command overrides the CLIR / OIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command. If this command is used by a subscriber without provision of CLIR / OIR in permanent mode the network will act according to 3GPP TS 22.081 [3] and 3GPP TS 24.607 [119]. + +Read command gives the default adjustment for all outgoing calls (given in <n>), and also triggers an interrogation of the provision status of the CLIR / OIR service (given in <m>). + +Test command returns values supported as a compound value. + +NOTE: On a per call basis CLIR / OIR functionality is explained in clauses "ITU-T Recommendation V.250 [14] dial command D" and "Dial URI +CDU". + +### Defined values + +<n>: integer type (parameter sets the adjustment for outgoing calls). + +- 0 presentation indicator is used according to the subscription of the CLIR / OIR service. +- 1 CLIR / OIR invocation +- 2 CLIR / OIR suppression + +<m>: integer type (parameter shows the subscriber CLIR / OIR service status in the network). + +- 0 CLIR / OIR not provisioned +- 1 CLIR / OIR provisioned in permanent mode +- 2 unknown (e.g. no network, etc.) +- 3 CLIR / OIR temporary mode presentation restricted +- 4 CLIR / OIR temporary mode presentation allowed + +### Implementation + +Optional. + +## 7.8 Connected line identification presentation +COLP + +**Table 41: +COLP parameter command syntax** + +| Command | Possible response(s) | +|---------------|---------------------------------| +| +COLP=[ <n> ] | | +| +COLP? | +COLP: <n>, <m> | +| +COLP=? | +COLP: (list of supported <n>s) | + +### Description + +This command refers to the supplementary service COLP (Connected Line Identification Presentation) according to 3GPP TS 22.081 [3] and TIP (Terminating Identification Presentation) according to 3GPP TS 24.608 [120] that enables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobile originated call. The command enables or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR / TIR in the network. + +When <n>=1, the presentation of the connected line identity at the TE enabled and when the called subscriber allows the intermediate result code, +COLP: <number>, <type> [, <subaddr>, <satype> [, <alpha>]] is returned from TA to TE before any +CR or ITU-T Recommendation V.250 [14] responses. It is manufacturer specific if this response is used when normal voice call is established. The intermediate result code +COLP does not support numbers of the SIP URI format. + +NOTE: If the connected line identity is available in the TE after reception of the final response to the call setup, +COLP is not returned as an intermediate result code but as an unsolicited result code. + +When <n>=0, the presentation of the connected line identity at the TE is disabled. + +The connected line identity can also be reported in unsolicited result codes +CMCSS<x>/ +CMCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCSS<x>/ +CMCSSEND support numbers of the SIP URI format. + +Read command gives the status of <n>, and also triggers an interrogation of the provision status of the COLP supplementary service according 3GPP TS 22.081 [3] and TIP supplementary service according to 3GPP TS 24.608 [120] (given in <m>). + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type (parameter sets/shows the result code presentation status to the TE). + +0 disable + +1 enable + +<m>: integer type (parameter shows the subscriber COLP service status in the network). + +0 COLP / TIP not provisioned + +1 COLP / TIP provisioned + +2 unknown (e.g. no network, etc.) + +<number>, <type>, <subaddr>, <satype>, <alpha>: refer +CLIP. + +#### Implementation + +Optional. + +## 7.9 Called line identification presentation +CDIP + +**Table 42: +CDIP parameter command syntax** + +| Command | Possible response(s) | +|-------------|---------------------------------| +| +CDIP=[<n>] | | +| +CDIP? | +CDIP: <n>, <m> | +| +CDIP=? | +CDIP: (list of supported <n>s) | + +#### Description + +This command related to a network service that provides "multiple called numbers (called line identifications) service" to an MT. This command enables a called subscriber to get the called line identification of the called party when receiving a mobile terminated call. Set command enables or disables the presentation of the called line identifications at the TE. + +When <n>=1, the presentation of the called line identification at the TE is enabled, the unsolicited result code +CDIP: <number>, <type>[, <subaddr>, <satype>] is returned after every RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. The unsolicited result code +CDIP does not support numbers of the SIP URI format. + +When <n>=0, the presentation of the called line identification at the TE is disabled. + +The called line identification can also be reported in unsolicited result codes +CMCSS<x>/ +CMCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCSS<x>/ +CMCSSEND support numbers of the SIP URI format. + +Read command gives the status of <n>, and also triggers an interrogation of the provision status of the "multiple called numbers" service. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type (parameter sets/shows the result code presentation status to the TE) + +0 disable + +1 enable + +<m>: integer type (parameter shows the subscriber "multiple called numbers" service status in the network) + +0 "multiple called numbers service" is not provisioned + +1 "multiple called numbers service" is provisioned + +2 unknown (e.g. no network, etc.) + +<number>: string type phone number of format specified by <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<subaddr>: string type subaddress of format specified by <satype> + +<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8) + +### Implementation + +Optional. + +## 7.10 Closed user group +CCUG + +**Table 43: +CCUG parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------|-----------------------------| +| +CCUG=[<n>[, <index>[, <info>]]] | | +| +CCUG? | +CCUG: <n>, <index>, <info> | +| +CCUG=? | | + +### Description + +This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21]). Set command enables the served subscriber to select a CUG index, to suppress the Outgoing Access (OA), and to suppress the preferential CUG. + +Set command with <n>=1 enables to control the CUG information on the air interface as a default adjustment for all following outgoing calls. The interaction of this command with other commands based on other supplementary services is described in the specification of the relevant supplementary service. + +NOTE: On a per call basis CUG functionality is explained in clause "ITU-T Recommendation V.250 [14] dial command D". + +Read command returns the current settings. + +### Defined values + +<n>: integer type + +0 disable CUG temporary mode + +1 enable CUG temporary mode + +<index>: integer type + +0..9 CUG index + +10 no index (preferred CUG taken from subscriber data) + +<info>: integer type + +0 no information + +- 1 suppress OA +- 2 suppress preferential CUG +- 3 suppress OA and preferential CUG + +### Implementation + +Optional. This command is superfluous when the command +CECUG is supported. + +## 7.11 Call forwarding number and conditions +CCFC + +**Table 44: +CCFC action command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CCFC=<reason>,<mode>[,<number>[,<type>[,<class>[,<subaddr>[,<satype>[,<time>]]]]]] | +CME ERROR: <err><br><br><b>when <mode>=2 and command successful:</b><br>+CCFC: <status>,<class1>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]]<br>[<CR><LF>+CCFC: <status>,<class2>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]]<br>[...]] | +| +CCFC=? | +CCFC: (list of supported <reason>s) | + +### Description + +This command allows control of the call forwarding supplementary service according to 3GPP TS 22.082 [4]. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service (<mode>=2) the response line for 'not active' case (<status>=0) should be returned only if service is not active for any <class>. Refer clause 9.2 for possible <err> values. + +Test command returns reason values supported as a compound value. + +NOTE: This command cannot be used with URIs. For communication forwarding control with URI support see AT command call forwarding number and conditions with URI support +CCFCU. + +### Defined values + +<reason>: integer type + +- 0 unconditional +- 1 mobile busy +- 2 no reply +- 3 not reachable +- 4 all call forwarding (refer 3GPP TS 22.030 [19]) +- 5 all conditional call forwarding (refer 3GPP TS 22.030 [19]) + +<mode>: integer type + +- 0 disable +- 1 enable +- 2 query status +- 3 registration + +4 erasure + +<number>: string type phone number of forwarding address in format specified by <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129 + +<subaddr>: string type subaddress of format specified by <satype> + +<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8); default 128 + +<classx> is a sum of integers each representing a class of information (default 7 - voice, data and fax): + +- 1 voice (telephony) +- 2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) +- 4 fax (facsimile services) +- 8 short message service +- 16 data circuit sync +- 32 data circuit async +- 64 dedicated packet access +- 128 dedicated PAD access + +<time>: integer type + +- 1...30 when "no reply", "all call forwarding" or "all conditional call forwarding" is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value 20 + +<status>: integer type + +- 0 not active +- 1 active + +#### Implementation + +Mandatory for MT supporting AT commands only and not supporting the control through dial command D. + +## 7.12 Call waiting +CCWA + +Table 45: +CCWA parameter command syntax + +| Command | Possible response(s) | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CCWA=[<n>[, <mode>[, <class>]]] | +CME ERROR: <err><br><br><b>when <mode>=2 and command successful</b><br>+CCWA: <status>, <class1><br>[<CR><LF>+CCWA: <status>, <class2><br>[...]] | +| +CCWA? | +CCWA: <n> | +| +CCWA=? | +CCWA: (list of supported <n>s) | + +#### Description + +This command allows control of the supplementary service Call Waiting according to 3GPP TS 22.083 [5] and Communication Waiting according to 3GPP TS 24.607 [137]. Activation, deactivation and status query are supported. When querying the status of a network service (<mode>=2) the response line for 'not active' case (<status>=0) should be returned only if service is not active for any <class>. Refer clause 9.2 for possible <err> values. + +Parameter <n> is used to disable/enable the presentation of an unsolicited result code + ++CCWA: <number>, <type>, <class>, [<alpha>] + +[, <CLI\_validity>, [<subaddr>, <stype>, [<priority>]]] to the TE when call waiting service is enabled. The unsolicited result code +CCWA does not support numbers of the SIP URI format. + +The call waiting information can also be reported in unsolicited result codes +CMCCSS<x>/ +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x>/ +CMCCSSEND support numbers of the SIP URI format. + +Command should be abortable when network is interrogated. + +Read command returns the current value of <n>. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type (sets/shows the result code presentation status to the TE). + +0 disable + +1 enable + +<mode>: integer type (when <mode> parameter is not given, network is not interrogated). + +0 disable + +1 enable + +2 query status + +<classx>: is a sum of integers each representing a class of information (default 7 - voice, data and fax). + +1 voice (telephony) + +2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) + +4 fax (facsimile services) + +8 short message service + +16 data circuit sync + +32 data circuit async + +64 dedicated packet access + +128 dedicated PAD access + +<status>: integer type + +0 not active + +1 active + +<number>: string type phone number of calling address in format specified by <type>. + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). + +<alpha>: optional string type alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command select TE character set +CSCS. + +<CLI\_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). + +- 0 CLI valid +- 1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user") +- 2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service") +- 3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone") +- 4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable") + +When CLI is not available (<CLI\_validity>=2, <CLI\_validity>=3 or <CLI\_validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> ((TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7)). + +When CLI has been withheld by the originator, (<CLI\_validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. + +<subaddr>: string type subaddress of format specified by <satype>. + +<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8). + +<priority>: optional digit type parameter indicating that the eMLPP priority level of the incoming call. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. + +## Implementation + +Optional. + +## 7.13 Call related supplementary services +CHLD + +**Table 46: +CHLD action command syntax** + +| Command | Possible response(s) | +|-----------|---------------------------------| +| +CHLD=<n> | +CME ERROR: <err> | +| +CHLD=? | +CHLD: (list of supported <n>s) | + +### Description + +This command allows the control of the following call related services: + +- a call can be temporarily disconnected from the MT but the connection is retained by the network; +- multiparty conversation (conference calls); +- the served subscriber who has two calls (one held and the other either active or alerting) can connect the other parties and release the served subscriber's own connection. + +Calls can be put on hold, recovered, released, added to conversation, and transferred similarly as defined in 3GPP TS 22.030 [19]. Refer clause 9.2 for possible <err> values. + +This is based on the supplementary services HOLD (Call Hold; refer 3GPP TS 22.083 [5] clause 2 and 3GPP TS 24.610 [135]), MPTY / CONF (MultiParty; refer 3GPP TS 22.084 [22] and Conference; refer 3GPP TS 24.605 [133]) and ECT (Explicit Call Transfer; refer 3GPP TS 22.091 [30] and 3GPP TS 24.629 [139]). + +NOTE 1: In the CS-domain, Call Hold, MultiParty and Explicit Call Transfer are only applicable to teleservice 11. + +Test command returns a list of operations which are supported. The call number required by some operations shall be denoted by "x" (e.g. +CHLD: (0, 1, 1x, 2, 2x, 3)). + +#### Defined values + +<n>: integer type; equals to numbers entered before SEND button in 3GPP TS 22.030 [19] clause 6.5.5.1. + +NOTE 2: The "directory number" case shall be handled with dial command D, and the END case with hangup command H (or +CHUP). The 4\*"directory number" case is handled with +CTFR command. + +#### Implementation + +Optional. + +## 7.14 Call deflection +CTFR + +**Table 47: +CTFR action command syntax** + +| Command | Possible response(s) | +|--------------------------------------------------|----------------------| +| +CTFR=<number>[, <type>[, <subaddr>[, <stype>]]] | +CME ERROR: <err> | +| +CTFR=? | | + +#### Description + +This refers to a service that causes an incoming alerting call to be forwarded to a specified number. Action command does this. Refer clause 9.2 for possible <err> values. + +This is based on the supplementary service CD (Call Deflection; refer 3GPP TS 22.072 [31]). The interaction of this command with other commands based on other supplementary services is described in the specification of the relevant supplementary service. + +NOTE 1: Call Deflection is only applicable to teleservice 11. + +NOTE 2: This command cannot be used with URIs. For communication forwarding control with URI support see AT command call forwarding number and conditions with URI support +CCFCU. + +#### Defined values + +<number>: string type phone number of format specified by <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129 + +<subaddr>: string type subaddress of format specified by <stype> + +<stype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8); default 128 + +#### Implementation + +Optional. + +## 7.15 Unstructured supplementary service data +CUSD + +**Table 48: +CUSD parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------|---------------------------------| +| +CUSD=[<n>[, <str>[, <dcs>]]] | +CME ERROR: <err> | +| +CUSD? | +CUSD: <n> | +| +CUSD=? | +CUSD: (list of supported <n>s) | + +### Description + +This command allows control of the Unstructured Supplementary Service Data (USSD) according to 3GPP TS 22.090 [23], 3GPP TS 24.090 [148] and 3GPP TS 24.390 [131]. Both network and mobile initiated operations are supported. Parameter <n> is used to disable/enable the presentation of an unsolicited result code. The value <n>=2 is used to cancel an ongoing USSD session. For an USSD response from the network, or a network initiated operation, the format is: +CUSD: <m>[, <str>, <dcs>]. + +NOTE 1: If the MT supports USSD according to 3GPP TS 24.090 [148] and USSD according to 3GPP TS 24.390 [131] then the MT decides which to invoke. The decision is out of scope of this specification. + +When <str> is given, a mobile initiated USSD-string or a response USSD-string to a network initiated operation is sent to the network. The response USSD-string from the network is returned in a subsequent unsolicited +CUSD result code. Refer clause 9.2 for possible <err> values. + +NOTE 2: In case of successful mobile initiated operation, TA implemented according to a version prior to 6 of this standard, waits the USSD response from the network and sends it to the TE before the final result code. This will block the AT command interface for the period of the operation. Such TA does not support <n> value 2. + +The interaction of this command with other commands based on other supplementary services is described in the specification of the relevant supplementary service. + +Read command returns the current value of <n>. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type (sets/shows the result code presentation status to the TE). + +- 0 disable the result code presentation to the TE +- 1 enable the result code presentation to the TE +- 2 cancel session (not applicable to read command response) + +<str>: string type USSD-string (when <str> parameter is not given, network is not interrogated): + +- if <dcs> indicates that 3GPP TS 23.038 [25] 7 bit default alphabet is used: + - if TE character set other than "HEX" (refer command select TE character set +CSCS): MT/TA converts GSM alphabet into current TE character set according to rules of 3GPP TS 27.005 [24] Annex A + - if TE character set is "HEX": MT/TA converts each 7-bit character of GSM alphabet into two IRA character long hexadecimal number (e.g. character II (GSM 23) is presented as 17 (IRA 49 and 55)) +- if <dcs> indicates that 8-bit data coding scheme is used: MT/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) + +- if <dcs> indicates that 16-bit data coding scheme (UCS2) is used: MT/TA splits the 16 bits into two 8-bit octets. Each of those octets are converted as per the 8-bit data coding scheme, with the most significant octet first (e.g. decimal value 4906 is presented to TE as four characters 132A (IRA 49, 51, 50 and 65)) + +<dcs>: integer type (shows Cell Broadcast Data Coding Scheme, see 3GPP TS 23.038 [25]). Default value is 0. + +<m>: integer type (shows the USSD response from the network or the network initiated operation). + +- 0 no further user action required (network initiated USSD-Notify, or no further information needed after mobile initiated operation) +- 1 further user action required (network initiated USSD-Request, or further information needed after mobile initiated operation) +- 2 USSD terminated by network +- 3 other local client has responded +- 4 operation not supported +- 5 network time out + +### Implementation + +Optional. + +## 7.16 Advice of charge +CAOC + +**Table 49: +CAOC parameter command syntax** + +| Command | Possible response(s) | +|----------------|-----------------------------------------| +| +CAOC[=<mode>] | [+CAOC: <ccm>]<br><br>+CME ERROR: <err> | +| +CAOC? | +CAOC: <mode> | +| +CAOC=? | +CAOC: (list of supported <mode>s) | + +### Description + +This refers to Advice of Charge supplementary service (3GPP TS 22.024 [26] and 3GPP TS 22.086 [27]) that enables subscriber to get information about the cost of calls. With <mode>=0, the execute command returns the current call meter value from the MT. + +The command also includes the possibility to enable/disable reporting of the CCM information with unsolicited result code +CCCM: <ccm>. When enabled, this unsolicited result code is sent when the CCM value changes, but not more frequently than at every 10 seconds. + +Refer clause 9.2 for possible <err> values. + +NOTE: Advice of Charge values stored in the SIM card or in the active application in the UICC (GSM or USIM) (ACM, ACMmax, PUCT) can be accessed with generic or restricted SIM access command (+CSIM or +CRSM). Those values can be more readily accessed with commands +CACM, +CAMM and +CPUC. + +Read command indicates whether the unsolicited reporting is activated or not. + +Test command returns the supported mode values as a compound value. + +### Defined values + +<mode>: integer type + +- 0 query CCM value + +- 1 deactivate the unsolicited reporting of CCM value +- 2 activate the unsolicited reporting of CCM value + +<ccm>: string type; three bytes of the current call meter value in hexadecimal format (e.g. "00001E" indicates decimal value 30); value is in home units and bytes are similarly coded as ACMmax value in the SIM card or in the active application in the UICC (GSM or USIM) + +### Implementation + +Optional. + +## 7.17 Supplementary service notifications +CSSN + +**Table 50: +CSSN parameter command syntax** + +| Command | Possible response(s) | +|--------------------|------------------------------------------------------------| +| +CSSN=[<n>[, <m>]] | | +| +CSSN? | +CSSN: <n>, <m> | +| +CSSN=? | +CSSN: (list of supported <n>s) , (list of supported <m>s) | + +### Description + +This command refers to supplementary service related network initiated notifications. The set command enables/disables the presentation of notification result codes from TA to TE. + +When <n>=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code +CSSI: <code1>[, [<index>] [, <SS\_code>]] is sent to TE before any other MO call setup result codes presented in the present document or in ITU-T Recommendation V.250 [14]. When several different <code1>s are received from the network, each of them shall have its own +CSSI result code. + +NOTE: If the supplementary service notification is available in the TE after reception of the final response to the call setup, +CSSI is not returned as an intermediate result code but as an unsolicited result code. + +When <m>=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU: <code2>[, [<index>] [, [<number>] [, <type>] [, <subaddr>] [, <satype>] [, <SS\_code>]]] is sent to TE. In case of MT call setup, result code is sent after every +CLIP result code (refer command Calling line identification presentation +CLIP) and when several different <code2>s are received from the network, each of them shall have its own +CSSU result code. <code2>=5 does not reflect any supplementary service, and the parameter <SS\_code> will not be provided. + +The supplementary service notification can also be reported in unsolicited result codes +CMCCSS<x>/ +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x>/ +CMCCSSEND support numbers of the SIP URI format. + +Read command returns the current settings. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type (parameter sets/shows the +CSSI intermediate result code presentation status to the TE) + +- 0 disable +- 1 enable + +<m>: integer type (parameter sets/shows the +CSSU unsolicited result code presentation status to the TE) + +- 0 disable + +1 enable + +<code1>: integer type (it is manufacturer specific, which of these codes are supported) + +- 0 unconditional call forwarding is active +- 1 some of the conditional call forwardings are active +- 2 call has been forwarded +- 3 call is waiting +- 4 this is a CUG call (also <index> present) +- 5 outgoing calls are barred +- 6 incoming calls are barred +- 7 CLIR suppression rejected +- 8 call has been deflected + +<index>: integer type (refer Closed user group +CCUG command) + +<SS\_code>: integer type used to present the code identifying a single supplementary service (see 3GPP TS 24.080 [109] and 3GPP TS 29.002 [110] clause 17.7.5) + +<code2>: integer type (it is manufacturer specific, which of these codes are supported) + +- 0 this is a forwarded call (MT call setup) +- 1 this is a CUG call (also <index> present) (MT call setup) +- 2 call has been put on hold (during a voice call) +- 3 call has been retrieved (during a voice call) +- 4 multiparty call entered (during a voice call) +- 5 call on hold has been released (this is not a SS notification) (during a voice call) +- 6 forward check SS message received (can be received whenever) +- 7 call is being connected (alerting) with the remote party in alerting state in explicit call transfer operation (during a voice call) +- 8 call has been connected with the other remote party in explicit call transfer operation (also number and subaddress parameters may be present) (during a voice call or MT call setup) +- 9 this is a deflected call (MT call setup) +- 10 additional incoming call forwarded + +<number>: string type phone number of format specified by <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<subaddr>: string type subaddress of format specified by <stype> + +<stype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8) + +## Implementation + +Optional. + +## 7.18 List current calls +CLCC + +**Table 51: +CLCC action command syntax** + +| Command | Possible response(s) | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CLCC | [+CLCC: <ccid1>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>[,<priority>[,<CLI validity>]]]]<br>[<CR><LF>+CLCC: <ccid2>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>[,<priority>[,<CLI validity>]]]]<br>[...]]]<br><br>+CME ERROR: <err> | +| +CLCC=? | | + +### Description + +Returns list of current calls of MT. If command succeeds but no calls are available, no information response is sent to TE. Refer clause 9.2 for possible <err> values. See also AT command +CLCCS. + +### Defined values + +<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. + +<dir>: integer type + +- 0 mobile originated (MO) call +- 1 mobile terminated (MT) call + +<stat>: integer type (state of the call) + +- 0 active +- 1 held +- 2 dialing (MO call) +- 3 alerting (MO call) +- 4 incoming (MT call) +- 5 waiting (MT call) + +<mode>: integer type (bearer/teleservice) + +- 0 voice +- 1 data +- 2 fax +- 3 voice followed by data, voice mode +- 4 alternating voice/data, voice mode +- 5 alternating voice/fax, voice mode +- 6 voice followed by data, data mode +- 7 alternating voice/data, data mode + +8 alternating voice/fax, fax mode + +9 unknown + +<mpty>: integer type + +0 call is not one of multiparty (conference) call parties + +1 call is one of multiparty (conference) call parties + +<number>: string type phone number in format specified by <type>. + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). + +<alpha>: string type alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command select TE character set +CSCS. + +<priority>: integer type parameter indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54]. + +<CLI validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). The parameter is not present for MO call types. + +0 CLI valid + +1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user") + +2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service") + +3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone") + +4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable") + +When CLI is not available (<CLI validity>=2, <CLI validity>=3 or <CLI validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7). + +When CLI has been withheld by the originator, (<CLI validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. + +## Implementation + +Optional. Recommended when +CHLD command is implemented. + +When +CDU is supported and SIP URIs are used in the MT, the AT command +CLCC is fully replaced by +CLCCS. + +## 7.19 Preferred PLMN list +CPOL + +**Table 52: +CPOL parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPOL=[<index>]<br>[, <format> [, <oper> [, <<br>GSM_AcT>, <GSM_Compact<br>_AcT>, <UTRAN_AcT>, <E-<br>UTRAN_AcT>, <NG-<br>RAN_AcT> ] ] ] | +CME ERROR: <err> | +| +CPOL? | +CPOL: <index1>, <format>, <oper1> [, <GSM_AcT1>, <<br>GSM_Compact_AcT1>, <UTRAN_AcT1>, <E-<br>UTRAN_AcT1>, <NG-RAN_AcT1>]<br>[<CR><LF>+CPOL: <index2>, <format>, <oper2> [, <GS<br>M_AcT2>, <GSM_Compact_AcT2>, <UTRAN_AcT2>, <E-<br>UTRAN_AcT2>, <NG-RAN_AcT2>>]<br>[...]]<br><br>+CME ERROR: <err> | +| +CPOL=? | +CPOL: (list of supported <index>s) , (list of supported<br><format>s)<br><br>+CME ERROR: <err> | + +### Description + +This command is used to edit the PLMN selector with Access Technology lists in the SIM card or active application in the UICC (GSM or USIM). + +Execute command writes an entry in the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS. If no list has been previously selected, the User controlled PLMN selector with Access Technology, EF<sub>PLMNwAcT</sub>, is the one accessed by default. If <index> is given but <oper> is left out, entry is deleted. If <oper> is given but <index> is left out, <oper> is put in the next free location. If only <format> is given, the format of the <oper> in the read command is changed. The Access Technology selection parameters, <GSM\_AcT>, <GSM\_Compact\_AcT>, <UTRAN\_AcT>, <E-UTRAN\_AcT> and <NG-RAN\_AcT> are required when writing User controlled PLMN selector with Access Technology, EF<sub>PLMNwAcT</sub>, Operator controlled PLMN selector with Access Technology EF<sub>OPLMNwAcT</sub> and HPLMN selector with Access Technology EF<sub>HPLMNwAcT</sub>, see 3GPP TS 31.102 [59]. Refer clause 9.2 for possible <err> values. + +NOTE 1: MT can also update the User controlled PLMN selector with Access Technology, EF<sub>PLMNwAcT</sub>, automatically when new networks are selected. + +NOTE 2: The Operator controlled PLMN selector with Access Technology EF<sub>OPLMNwAcT</sub>, can only be written if the write access condition in the SIM/USIM has been previously verified. + +Read command returns all used entries from the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS, with the Access Technologies for each PLMN in the list. + +Test command returns the whole index range supported by the SIM as compound values. + +### Defined values + +<indexn>: integer type; the order number of operator in the SIM/USIM preferred operator list + +<format>: integer type + +0 long format alphanumeric <oper> + +1 short format alphanumeric <oper> + +2 numeric <oper> + +<opern>: string type; <format> indicates if the format is alphanumeric or numeric (see +COPS) + +<GSM\_AcTn>: integer type; GSM access technology: + +- 0 access technology not selected +- 1 access technology selected + +<GSM\_Compact\_AcTn>: integer type; GSM compact access technology + +- 0 access technology not selected +- 1 access technology selected + +<UTRAN\_AcTn>: integer type; UTRAN access technology + +- 0 access technology not selected +- 1 access technology selected + +<E-UTRAN\_AcTn>: integer type; E-UTRAN access technology + +- 0 access technology not selected +- 1 access technology selected + +<NG-RAN\_AcTn>: integer type; NG-RAN access technology + +- 0 access technology not selected +- 1 access technology selected + +#### Implementation + +Optional. + +## 7.20 Selection of preferred PLMN list +CPLS + +**Table 53: +CPLS parameter command syntax** + +| Command | Possible response(s) | +|----------------|---------------------------------------------------------| +| +CPLS=[<list>] | +CME ERROR: <err> | +| +CPLS? | +CPLS: <list><br>+CME ERROR: <err> | +| +CPLS=? | +CPLS: (list of supported <list>s)<br>+CME ERROR: <err> | + +#### Description + +This command is used to select one PLMN selector with Access Technology list in the SIM card or active application in the UICC (GSM or USIM), that is used by +CPOL command. + +Execute command selects a list in the SIM/USIM. Refer clause 9.2 for possible <err> values. + +Read command returns the selected PLMN selector list from the SIM/USIM. + +Test command returns the whole index range supported lists by the SIM/USIM as a compound value. + +#### Defined values + +3GPP + +<list>: integer type + +- 0 User controlled PLMN selector with Access Technology EF<sub>PLMNNwAct</sub>, if not found in the SIM/UICC then PLMN preferred list EF<sub>PLMNSel</sub> (this file is only available in SIM card or GSM application selected in UICC) +- 1 Operator controlled PLMN selector with Access Technology EF<sub>OPLMNNwAct</sub> +- 2 HPLMN selector with Access Technology EF<sub>HPLMNNwAct</sub> + +#### Implementation + +Optional. + +## 7.21 Read operator names +COPN + +Table 54: +COPN action command syntax + +| Command | Possible response(s) | +|---------|--------------------------------------------------------------------------------------------------------| +| +COPN | +COPN: <numeric1>, <alpha1><br>[<CR><LF>+COPN: <numeric2>, <alpha2><br>[...]]<br><br>+CME ERROR: <err> | +| +COPN=? | | + +#### Description + +Execute command returns the list of operator names from the MT. Each operator code <numericn> that has an alphanumeric equivalent <alphann> in the MT memory shall be returned. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<numericn>: string type; operator in numeric format (see +COPS) + +<alphann>: string type; operator in long alphanumeric format (see +COPS) + +#### Implementation + +Optional. + +## 7.22 eMLPP priority registration and interrogation +CAEMLPP + +Table 55: +CAEMLPP parameter command syntax + +| Command | Possible Response(s) | +|---------------------|-----------------------------------------------------------------------| +| +CAEMLPP=<priority> | +CME ERROR: <err> | +| +CAEMLPP? | +CAEMLPP: <default_priority>, <max_priority><br><br>+CME ERROR: <err> | +| +CAEMLPP=? | | + +#### Description + +The execute command is used to change the default priority level of the user in the network. The requested priority level is checked against the eMLPP subscription of the user stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>eMLPP</sub>. If the user doesn't have subscription for the requested priority level an ERROR or +CME ERROR result code is returned. Refer clause 9.2 for possible <err> values. + +The read command triggers an interrogation of the provision of the maximum priority level which the service subscriber is allowed to use and default priority level activated by the user. + +If the service is not provisioned, a result code including the SS-Status (?) parameter is returned. + +#### Defined values + +<priority>: integer type parameter which identifies the default priority level to be activated in the network, values specified in 3GPP TS 22.067 [54] + +<default\_priority>: integer type parameter which identifies the default priority level which is activated in the network, values specified in 3GPP TS 22.067 [54] + +<max\_priority>: integer type parameter which identifies the maximum priority level for which the service subscriber has a subscription in the network, values specified in 3GPP TS 22.067 [54] + +#### Implementation + +Mandatory for an MT supporting AT commands only and supplementary service eMLPP is implemented. + +### 7.23 eMLPP subscriptions +CPPS + +Table 56: +CPPS action command syntax + +| Command | Possible response(s) | +|---------|---------------------------------------------------------------------| +| +CPPS | [+CPPS: <priority>[, <priority><br>[...]]]<br><br>+CME ERROR: <err> | +| +CPPS=? | | + +#### Description + +This command returns all eMLPP priority subscriptions of the user stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>eMLPP</sub>. If no explicit priority level subscription is stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>eMLPP</sub> the result code OK is returned. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<priority>: integer type, eMLPP subscription to priority level {0,1,...,4} as defined in 3GPP TS 22.067 [54]. + +#### Implementation + +Mandatory for a MT supporting AT commands only and eMLPP is implemented. + +### 7.24 Fast call setup conditions +CFCS + +Table 57: +CFCS parameter command syntax + +| Command | Possible response(s) | +|---------------------------|---------------------------------------------------------------------| +| +CFCS=<priority>,<status> | +CME ERROR: <err> | +| +CFCS? | [+CFCS: <priority>[, <priority><br>[...]]]<br><br>+CME ERROR: <err> | + +| | | +|---------|-----------------------------------------------------| +| +CFCS=? | +CFCS: (list of supported<br><priority>, <status>s) | +|---------|-----------------------------------------------------| + +### Description + +The set command is used to edit the status of the priority level for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>eMLPP</sub>. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. Refer clause 9.2 for possible <err> values. + +The read command returns all enabled priority levels for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>eMLPP</sub>. If no priority level is enabled for fast call set-up, the result code OK is returned. + +Test command returns the values supported by the UE. + +### Defined values + +<priority>: integer type, eMLPP fast call set-up priority level {0,1,...,4} as defined in 3GPP TS 22.067 [54] + +<status>: integer type + +0 disable <priority> for fast call set-up + +1 enable <priority> for fast call set-up + +### Implementation + +Mandatory for a MT supporting AT commands only and eMLPP is implemented. + +## 7.25 Automatic answer for eMLPP service +CAAP + +**Table 58: +CAAP parameter command syntax** + +| Command | Possible response(s) | +|----------------------------|---------------------------------------------------------------------| +| +CAAP=<priority>, <status> | +CME ERROR: <err> | +| +CAAP? | [+CAAP: <priority>[, <priority><br>[...]]]<br><br>+CME ERROR: <err> | +| +CAAP=? | +CAAP: (list of supported<br><priority>, <status>s) | + +### Description + +The set command is used to edit the status of the priority level for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>AAeM</sub>. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. Refer clause 9.2 for possible <err> values. + +The read command returns all enabled priority levels for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EF<sub>AAeM</sub>. If no priority level is enabled for automatic answering for eMLPP, the result code OK is returned. + +Test command returns the values supported by the UE. + +### Defined values + +<priority>: eMLPP automatic answer priority level value {A,B,0,1,...,4} as defined in 3GPP TS 22.067 [54] + +<status>: integer type + +0 disable eMLPP <priority> for automatic answering + +1 enable eMLPP <priority> for automatic answering + +## Implementation + +Mandatory for a MT supporting AT commands only and eMLPP is implemented. + +## 7.26 User to user signalling service 1 +CUUS1 + +**Table 59: +CUUS1 parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CUUS1=[<n>[, <m>[, <message>[, <UIE>[, <message>[, <UIE>[, . . . ]]]]]]] | +CME ERROR: <err> | +| +CUUS1? | +CUUS1: <n>, <m>[, <message>, <UIE>[, <message>, <UIE>[, . . . ]]] | +| +CUUS1=? | +CUUS1: (list of supported <n>s) , (list of supported <m>s) , (list of supported <message>s) , (list of supported <messageI>s) , (list of supported <messageU>s) | + +### Description + +This command allows control of the User-to-User Signalling Supplementary Service 1 (UUS1) according to 3GPP TS 22.087 [58]. + +Parameters <message> and <UIE> are used to activate/deactivate the implicit request of the User-to-User Signalling Supplementary Service 1. + +When <message> and <UIE> are both present the string specified in <UIE> is included as the value part of the User-to-User Information Element (as defined in 3GPP TS 24.008 [8]) into all subsequent messages of type <message>. If parameter <message> is present but parameter <UIE> is not present then the User-to-User Information Element shall not be present in subsequent messages of type <message>. + +Parameters <n> and <m> are used to enable/disable the presentation of incoming User-to-User Information Elements. + +When <n>=1 and a User-to-User Information is received after a mobile originated call setup or after hanging up a call, intermediate result code +CUUS1I: <messageI>, <UIE> is sent to the TE. + +When <m>=1 and a User-to-User Information is received during a mobile terminated call setup or during a remote party call hangup, unsolicited result code +CUUS1U: <messageU>, <UIE> is sent to the TE. + +Refer clause 9.2 for possible <err> values. + +Test command returns values supported as compound values. + +### Defined values + +<n>: integer type (parameter sets/shows the +CUUS1I result code presentation status in the TA). + +0 disable. + +1 enable. + +<m>: integer type (parameter sets/shows the +CUUS1U result code presentation status in the TA). + +0 disable. + +1 enable. + +<message>: integer type (type of message containing the outgoing User-to-User Information Element). + +0 ANY + +1 SETUP + +- 2 ALERT +- 3 CONNECT +- 4 DISCONNECT +- 5 RELEASE +- 6 RELEASE\_COMPLETE + +<messageI>: integer type (type of message containing the intermediate User-to-User Information Element). + +- 0 ANY +- 1 ALERT +- 2 PROGRESS +- 3 CONNECT (sent after +COLP if enabled) +- 4 RELEASE + +<messageU>: integer type (type of message containing the unsolicited User-to-User Information Element). + +- 0 ANY +- 1 SETUP (returned after +CLIP if presented, otherwise after every RING or +CRING) +- 2 DISCONNECT +- 3 RELEASE\_COMPLETE + +<UUITE>: the User-user Information Element (as defined in 3GPP TS 24.008 [8]) in hexadecimal character format (for hexadecimal format, refer +CSCS). + +NOTE: If the TA does not distinguish the type of message containing the User-to-user Information Element, it can use the value for ANY message. + +#### Implementation + +Optional. + +## 7.27 Preferred network indication +CPNET + +**Table 59A: +CPNET parameter command syntax** + +| Command | Possible response(s) | +|---------------------|-----------------------------------------| +| +CPNET=[<Pref_net>] | | +| +CPNET? | +CPNET: <Pref_net> | +| +CPNET=? | +CPNET: (list of supported <Pref_net>s) | + +#### Description + +This command indicates whether the terminal has preference <Pref\_net> for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN, see 3GPP TS 44.318 [70]. + +Read command returns the current preference for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN. + +Test command returns the parameter indicating preference <Pref\_net> for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN as a compound value. + +#### Defined values + +<Pref\_net>: integer type; indicates the preference for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN. + +- 0 GERAN/UTRAN/E-UTRAN/NG-RAN shall be used. The terminal uses GERAN/UTRAN/E-UTRAN/NG-RAN coverage only. +- 1 GAN shall be used. The terminal used GAN coverage only. +- 2 GERAN/UTRAN/E-UTRAN/NG-RAN preferred. The terminal prefers to stay in GERAN/UTRAN/E-UTRAN/NG-RAN rather than GAN. +- 3 GAN preferred. The terminal prefers to stay in GAN rather than GERAN/UTRAN/E-UTRAN/NG-RAN. + +NOTE: Usage of value 0 or 1 will prevent the terminal from changing between GERAN/UTRAN/E-UTRAN/NG-RAN and GAN. E.g. setting <Pref\_net> to 1 indicates that only GAN will be used, and prevents the terminal from using available GERAN/UTRAN/E-UTRAN/NG-RAN coverage. + +### Implementation + +Optional. + +## 7.28 Preferred network status +CPNSTAT + +**Table 59B: +CPNSTAT parameter command syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CPNSTAT= [<n>] | | +| +CPNSTAT? | +CPNSTAT: <n>, <stat> | +| +CPNSTAT=? | +CPNSTAT: (list of supported <n>s) | + +### Description + +Set command controls the presentation of an unsolicited result code +CPNSTAT: <stat> when <n>=1 and there is a change in the preferred network indication status. + +Read command returns the status of result code presentation <n> and an integer <stat> which shows whether the terminal is in GERAN/UTRAN/E-UTRAN/NG-RAN or GAN, see 3GPP TS 44.318 [70]. + +NOTE: Further details about registration status are available using commands +CREG (see clause 7.2), +CGREG (see clause 10.1.19), +CEREG (see clause 10.1.21) and +CNRREG (see clause 10.1.47). + +Test command returns the list of supported unsolicited result codes as a compound value. + +### Defined values + +<n>: integer type + +- 0 disable preferred network indication unsolicited result code. +- 1 enable preferred network indication unsolicited result code +CPNSTAT: <stat>. + +<stat>: integer type; preferred network indication status. + +- 0 Requested network not available. +- 1 GERAN/UTRAN/E-UTRAN/NG-RAN used. +- 2 GAN used. + +### Implementation + +Optional. + +## 7.29 Current packet switched bearer +CPSB + +**Table 59C: +CPSB parameter command syntax** + +| Command | Possible response(s) | +|-------------|----------------------------------------------------------------------------------------------------------------| +| +CPSB=[<n>] | +CME ERROR: <err> | +| +CPSB? | +CPSB: <n>[, <cid>, <curr_bearer>]<br>[<CR><LF>+CPSB: <n>, <cid>, <curr_bearer>]<br>[...]<br>+CME ERROR: <err> | +| +CPSB=? | +CPSB: (list of supported <n>s) | + +### Description + +Set command controls the presentation of an unsolicited result code +CPSB: <cid>, <curr\_bearer> when <n>=1 and the <cid> corresponds to a PDP context in the PDP-ACTIVE state, to an EPS bearer context in the BEARER CONTEXT ACTIVE state or to a 5GS QoS flow of a PDU session in the PDU SESSION ACTIVE state and there is a change in the current value of <curr\_bearer> due to the reception of a control or signalling message from the network as specified in 3GPP TS 44.060 [71], 3GPP TS 25.331 [74], 3GPP TS 36.331 [86] or 3GPP TS 38.331 [160]. + +Read command returns the current status of the unsolicited result code presentation <n>. The parameters <cid> and <curr\_bearer> are returned for each defined context when <n>=1 for <cid>s that correspond to a PDP context in the PDP-ACTIVE state, to an EPS bearer context in the BEARER CONTEXT ACTIVE state or to a 5GS QoS flow of a PDU session in the PDU SESSION ACTIVE state. + +Refer clause 9.2 for possible <err> values. + +Test command returns the list of supported <n>s as a compound value. + +### Defined values + +<n>: integer type + +- 0 disable the presentation of the unsolicited result code +- 1 enable the presentation of the unsolicited result code ++CPSB: <cid>, <curr\_bearer> + +<cid>: A numeric parameter which specifies a particular PDP context, an EPS bearer context or a 5GS QoS flow. + +The <cid> parameter is local to the TE-MT interface and identifies only those PDP contexts, EPS bearer contexts or 5GS QoS flows which have been setup via AT command (see the +CGDCONT and +CGDSCONT commands). + +<curr\_bearer>: integer type; the current packet switched bearer which is established between the UE and network. + +- 0 There is currently no packet switched bearer between the UE and the network (e.g. RAB is released in UMTS or the TBF is released in GSM). This would mean that there is no bearer associated to the PDP context referred to by the <cid> parameter and hence no data transfer is currently occurring on that particular PDP context. This result code covers the case where the PDP context is active but there is no bearer associated with it. +- 1 GPRS. (See 3GPP TS 44.060 [71] for definition of GPRS TBF Mode) +- 2 EGPRS. (See 3GPP TS 44.060 [71] for definition of EGPRS TBF Mode) +- 3 Non-HSUPA in uplink and non-HSDPA in downlink. (See NOTE 1 to NOTE 3) + +- 4 HSUPA in uplink and non-HSDPA in downlink. (See NOTE 1 to NOTE 4) +- 5 Non-HSUPA in uplink and HSDPA in downlink. (See NOTE 1 to NOTE 4) +- 6 HSUPA in uplink and HSDPA in downlink. (See NOTE 1 to NOTE 4) +- 7 EPS (See NOTE 5) +- 8 5GS (See NOTE 6) + +NOTE 1: The term "non-HSDPA" means a non-HSDPA UMTS bearer. 3GPP TS 25.331 [74] specifies the criterion to be satisfied in order for a downlink UMTS RAB to be termed as HSDPA. If those criterion are not met, then the downlink UMTS RAB would be termed as "non-HSDPA" by this AT command. + +NOTE 2: The term "non-HSUPA" means a non-HSUPA UMTS bearer. 3GPP TS 25.331 [74] specifies the criterion to be satisfied in order for an uplink UMTS RAB to be termed as HSUPA (or Enhanced uplink DCH). If those criterion are not met, then the uplink UMTS RAB would be termed as "non-HSUPA" by this AT command. + +NOTE 3: The terms "non-HSDPA", "non-HSUPA" indicate R99 to pre- HSDPA or pre-HSUPA UMTS bearers. They do not imply GPRS or EGPRS bearers. + +NOTE 4: See 3GPP TS 25.308 [72] for HSDPA and 3GPP TS 25.319 [73] for HSUPA. + +NOTE 5: The term "EPS" means an EPS bearer (see 3GPP TS 36.331 [86]). + +NOTE 6: The term "5GS" means a 5GS QoS flow (see 3GPP TS 38.331 [160]). + +#### Implementation + +Optional. + +## 7.30 Calling name identification presentation +CNAP + +**Table 59D: +CNAP parameter command syntax** + +| Command | Possible response(s) | +|--------------|---------------------------------| +| +CNAP= [<n>] | | +| +CNAP? | +CNAP: <n>, <m> | +| +CNAP=? | +CNAP: (list of supported <n>s) | + +#### Description + +This command refers to the supplementary service CNAP (Calling Name Presentation) according to 3GPP TS 22.096 [93] that enables a called subscriber to get a calling name indication (CNI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CNI at the TE. It has no effect on the execution of the supplementary service CNAP in the network. + +When <n>=1, the presentation of the calling name indication at the TE is enabled and CNI is provided the unsolicited result code, +CNAP: <name>[, <CNI\_validity>] is returned after every RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. + +The calling name indication can also be reported in unsolicited result codes +CMCSS<x>/ +CMCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCSS<x>/ +CMCSSEND support numbers of the SIP URI format. + +Read command gives the status of <n>, and also triggers an interrogation of the provision status of the CNAP service according 3GPP TS 22.096 [93] (given in <m>). + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type (parameter sets/shows the result code presentation status to the TE) + +- 0 disable +- 1 enable + +<m>: integer type (parameter shows the subscriber CNAP service status in the network) + +- 0 CNAP not provisioned +- 1 CNAP provisioned +- 2 unknown (e.g. no network, etc.) + +<name>: string type, up to 80 characters long string containing the calling name + +<CNI\_validity>: integer type + +- 0 CNI valid +- 1 CNI has been withheld by the originator. +- 2 CNI is not available due to interworking problems or limitations of originating network. + +When CNI is not available (<CNI\_validity>=2), <name> shall be an empty string (""). + +When CNI has been withheld by the originator, (<CNI\_validity>=1) and the CNAP is provisioned with the "override category" option (refer 3GPP TS 22.096 [93] and 3GPP TS 23.096 [94]), <name> is provided. Otherwise, TA shall return the same setting for <name> as if the CNI was not available. + +### Implementation + +Optional. + +## 7.31 Connected line identification restriction status +COLR + +**Table 59E: +COLR action command syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +COLR | +COLR: <m> | +| +COLR=? | | + +### Description + +This command refers to the supplementary service COLR (Connected Line Identification Restriction) according to 3GPP TS 22.081 [3] and supplementary service TIR (Terminating Identification Restriction) according to 3GPP TS 24.608 [120] that enables a called subscriber to restrict the possibility of presentation of connected line identity (COL) to the calling party after receiving a mobile terminated call. The command displays the status of the COL presentation in the network. It has no effect on the execution of the supplementary services COLR / TIR in the network. + +The command triggers an interrogation of the activation status of the COLR supplementary service according to 3GPP TS 22.081 [3] and the TIR supplementary service according to 3GPP TS 24.608 [120] (given in <m>). + +Activation, deactivation, registration and erasure of the supplementary service COLR / TIR are not applicable. + +### Defined values + +<m>: integer type (parameter shows the subscriber COLR / TIR service status in the network). + +- 0 COLR / TIR not provisioned + +- 1 COLR / TIR provisioned +- 2 unknown (e.g. no network, etc.) + +#### Implementation + +Optional. + +## 7.32 Service specific access control restriction status +CSSAC + +**Table 7.32-1: +CSSAC action command syntax** + +| Command | Possible response(s) | +|----------|----------------------------------------------------| +| +CSSAC | +CSSAC: <BFVoice>, <BFVideo>, <BTVoice>, <BTVideo> | +| +CSSAC=? | | + +#### Description + +This command refers to SSAC (Service Specific Access Control) related information which is used by MMTEL application (see 3GPP TS 24.173 [87]). The command provides the current status of the parameters for SSAC, <BFVoice>, <BFVideo>, <BTVoice> and <BTVideo>. The AT command has no effect on the execution of SSAC. + +#### Defined values + +<BFVoice> integer type; parameter shows the barring factor for MMTEL voice. <BFVoice> is mapped to the BarringFactorForMMTEL-Voice as in table 7.32-2. + +**Table 7.32-2: Value of BFVoice and its interpretation by MMTEL application** + +| <BFVoice> | BarringFactorForMMTEL-Voice as specified in 3GPP TS 24.173 [87] | +|-----------|-----------------------------------------------------------------| +| 0 | 0 | +| 1 | 0,05 | +| 2 | 0,1 | +| 3 | 0,15 | +| 4 | 0,2 | +| 5 | 0,25 | +| 6 | 0,3 | +| 7 | 0,4 | +| 8 | 0,5 | +| 9 | 0,6 | +| 10 | 0,7 | +| 11 | 0,75 | +| 12 | 0,8 | +| 13 | 0,85 | +| 14 | 0,9 | +| 15 | 0,95 | +| 16 | 1 | + +<BFVideo> integer type; parameter shows the barring factor for MMTEL video. <BFVideo> is mapped to the BarringFactorForMMTEL-Video as in table 7.32-3. + +**Table 7.32-3: Value of BFVideo and its interpretation by MMTEL application** + +| <BFVideo> | BarringFactorForMMTEL-Video as specified in 3GPP TS 24.173 [87] | +|-----------|-----------------------------------------------------------------| +| 0 | 0 | +| 1 | 0,05 | +| 2 | 0,1 | +| 3 | 0,15 | +| 4 | 0,2 | +| 5 | 0,25 | +| 6 | 0,3 | +| 7 | 0,4 | +| 8 | 0,5 | +| 9 | 0,6 | +| 10 | 0,7 | +| 11 | 0,75 | +| 12 | 0,8 | +| 13 | 0,85 | +| 14 | 0,9 | +| 15 | 0,95 | +| 16 | 1 | + +<BTVoice> integer type; parameter shows the barring timer for MMTEL voice. <BTVoice> is mapped to the BarringTimeForMMTEL-Voice as in table 7.32-4. + +**Table 7.32-4: Value of BTVoice and its interpretation by MMTEL application** + +| <BTVoice> | BarringTimeForMMTEL-Voice as specified in 3GPP TS 24.173 [87] | +|-----------|---------------------------------------------------------------| +| 0 | 0 | +| 1 | 4 | +| 2 | 8 | +| 3 | 16 | +| 4 | 32 | +| 5 | 64 | +| 6 | 128 | +| 7 | 256 | +| 8 | 512 | + +<BTVideo> integer type; parameter shows the barring timer for MMTEL video. <BTVideo> is mapped to the BarringTimeForMMTEL-Video as in table 7.32-5. + +**Table 7.32-5: Value of BTVideo and its interpretation by MMTEL application** + +| <BTVideo> | BarringTimeForMMTEL-Video as specified in 3GPP TS 24.173 [87] | +|-----------|---------------------------------------------------------------| +| 0 | 0 | +| 1 | 4 | +| 2 | 8 | +| 3 | 16 | +| 4 | 32 | +| 5 | 64 | +| 6 | 128 | +| 7 | 256 | +| 8 | 512 | + +## Implementation + +Optional. + +This command is only applicable to UEs in E-UTRAN. + +## 7.33 Network emergency (bearer) services support +CNEM + +**Table 7.33-1: +CNEM parameter command syntax** + +| Command | Possible response(s) | +|-------------------|-------------------------------------------------------------------------------------------------------| +| +CNEM=<reporting> | +CME ERROR: <err> | +| +CNEM? | +CNEM: <reporting>[, <emb_Iu_supp>[, <emb_S1_supp>[, <ems_5G_supp>, <emf_5G_supp>, <emcn3_5G_supp>]]] | +| +CNEM=? | +CNEM: (list of supported <reporting>s) | + +### Description + +Set command enables reporting of changes in the emergency (bearer) services support indicators and emergency services fallback indicator with the unsolicited result code +CNEMIU: <emb\_Iu\_supp> according to the network feature support information element, see 3GPP TS 24.008 [8] clause 10.5.5.23, the unsolicited result code +CNEMS1: <emb\_S1\_supp> according to the EPS network feature support information element, see 3GPP TS 24.301 [83] clause 9.9.3.12A, and the unsolicited result code +CNEM5G: <ems\_5G\_supp>, <emf\_5G\_supp>, <emcn3\_5G\_supp> according to the 5GS network feature support information element, see 3GPP TS 24.501 [161] clause 9.11.3.5. Refer clause 9.2 for possible <err> values. + +Read command returns current command setting and if enabled, the settings of the emergency bearer services support indicator in Iu mode and the emergency bearer services support indicator in S1 mode for the network where the UE is attached. The read command also returns the emergency services support indicator in 5G and the emergency services fallback indicator in 5G for the network where the UE is registered. + +Test command returns values supported as a compound value. + +### Defined values + +<reporting>: integer type + +- 0 Reporting not enabled +- 1 Reporting enabled + +<emb\_Iu\_supp>: integer type. Emergency bearer services support indicator for Iu mode (See NOTE). + +- 0 Emergency bearer services in Iu mode and A/Gb mode not supported +- 1 Emergency bearer services supported in Iu mode, but not supported in A/Gb mode + +<emb\_S1\_supp>: integer type. Emergency bearer services support indicator for S1 mode (See NOTE). + +- 0 Emergency bearer services in S1 mode not supported +- 1 Emergency bearer services in S1 mode supported + +<ems\_5G\_supp>: integer type. Emergency services support indicator for 5G (See NOTE). + +- 0 Emergency services in 5G not supported +- 1 Emergency services supported in NR connected to 5GC only +- 2 Emergency services supported in E-UTRA connected to 5GC only +- 3 Emergency services supported in NR connected to 5GC and E-UTRA connected to 5GC + +<emf\_5G\_supp>: integer type. Emergency services fallback indicator for 5G (See NOTE). + +- 0 Emergency services fallback in 5G not supported +- 1 Emergency services fallback supported in NR connected to 5GC only + +- 2 Emergency services fallback supported in E-UTRA connected to 5GC only +- 3 Emergency services fallback supported in NR connected to 5GC and E-UTRA connected to 5GC + +<emcn3\_5G\_supp>: integer type. Emergency services support indicator for non-3GPP access (See NOTE). + +- 0 Emergency services not supported over non-3GPP access +- 1 Emergency services supported over non-3GPP access + +NOTE: The indicators <emb\_Iu\_supp>, <emb\_S1\_supp>, <ems\_5G\_supp>, <emf\_5G\_supp> and <emcn3\_5G\_supp> are only set to supported when explicitly signalled from the network. When an emergency (bearer) services support indicator is not signalled from the network or if no network is available, this is interpreted as "Emergency (bearer) services not supported". When the emergency services fallback indicator is not signalled from the network or if no network is available, this is interpreted as "Emergency services fallback in 5G not supported". + +### Implementation + +Optional. + +## 7.34 Enhanced closed user group +CECUG + +Table 7.34-1: +CECUG parameter command syntax + +| Command | Possible response(s) | +|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| +CECUG=<n>,<br>[<CUG_pointer>[, <CUG_index><br>, <CUG_info>]] | | +| +CECUG? | [+CECUG: <n>, <CUG_pointer>, <CUG_index>, <CUG_info><br><br>[<CR><LF>+CECUG: <n>, <CUG_pointer>, <CUG_index>, <CUG_info><br><br>[...]]] | +| +CECUG=? | +CECUG: (list of supported <n>s) , (range of supported <CUG_pointer>s) | + +### Description + +This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21] and 3GPP TS 24.654 [121]). Set command enables the served subscriber to create a number of <CUG\_pointer>s that each define a <CUG\_index> and a <CUG\_info> to define how the preferential CUG and the Outgoing Access (OA) is handled for outgoing calls. + +Set command with <n>=0 disable settings in the MT and use the subscribed settings, while <n>=1 enables to control the CUG information on the air interface as adjustments for outgoing calls according to the settings defined by the parameters <CUG\_pointer>s, <CUG\_index> and <CUG\_info>. For calls initiated using the dial command D, the dial string modifiers 'G' or 'g' can not indicate a <CUG\_pointer> and the <CUG\_index> and <CUG\_info> as defined for <CUG\_pointer>=1 shall be used. + +NOTE 1: On a per call basis CUG functionality is explained in the clauses "ITU-T Recommendation V.250 [14] dial command D" and "Dial URI +CDU". + +A special form of the set command, +CECUG=<n>, <CUG\_pointer> causes the value of <CUG\_index> and <CUG\_info> for the CUG pointer <CUG\_pointer> to become undefined. The set command, +CECUG=0 that can be used to disable the CUG temporary mode will not make previously defined CUG pointers and the corresponding defined <CUG\_index> and <CUG\_info> undefined. + +The read command returns the current settings for each defined CUG pointer. + +The test command returns values supported as compound values. + +### Defined values + +<n>: integer type. This parameter sets CUG activation on a per call basis. + +- 0 disable CUG temporary mode. All calls initiated using the dial command D or +CDU use the subscribed CUG settings. The parameters <CUG\_index> and <CUG\_info> are ignored at call initiation. For calls initiated using the dial command D, the dial string modifiers 'G' or 'g' have no effect (see clause "ITU T Recommendation V.250 [14] dial command D"). For calls initiated using +CDU, the parameter <CUG\_pointer> has no effect (see clause "Dial URI +CDU"). +- 1 enable CUG temporary mode. Values for <CUG\_index> and <CUG\_info> are applied for: + - all calls initiated using the dial command D where the dial modifier 'G' or 'g' (see clause "ITU T Recommendation V.250 [14] dial command D") is present as part of the dial string. + - all calls initiated using +CDU where parameter <CUG\_pointer> is set to 1 (see clause "Dial URI +CDU") + +If 'G' or 'g' is not applied (for the dial command D) or <CUG\_pointer> is set to 0 (for +CDU) <CUG\_index> and <CUG\_info> are ignored. In that case only the subscribed CUG settings apply. + +<CUG\_pointer>: integer type. A numeric parameter which specifies a particular set of CUG data. The <CUG\_pointer> is local to the TE-MT interface and identifies a particular <CUG\_index> and <CUG\_info> which indicates per call basis changes provided to the supplementary service closed user group. The range of permitted values is from 1-n. The maximum value of n is implementation specific. + +NOTE 2: 3GPP TS 22.085 [21] indicates that each individual subscriber can be a member of a maximum of 10 CUGs. + +<CUG\_index>: string type. The parameter sets the CUG index for this <CUG\_pointer>. + +"0" ... "32767" CUG index + +"" no CUG index, indicated by empty string. Preferential CUG taken from subscriber data. + +<CUG\_info>: integer type. The parameter sets the CUG information for this <CUG\_pointer>. + +- 0 no information +- 1 suppress OA +- 2 suppress preferential CUG +- 3 suppress OA and preferential CUG + +### Implementation + +Optional. This command can replace the command +CCUG. + +## 7.35 Communication forwarding number and conditions with URI support +CCFCU + +**Table 7.35-1: +CCFCU action command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CCFCU=<reason>,<mode>[,<nubertype>,<ton>,<number>[,<class>,<ruleset>[,<subaddr>[,<satype>[,<time>]]]]] | +CME ERROR: <err><br><br><b>when <mode>=2 and command successful:</b><br>+CCFCU: <status>,<class1>[,<nubertype>,<ton>,<number>[,<subaddr>,<satype>[,<time>]]]<br>[<CR><LF>+CCFCU: <status>,<class2>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]]<br>[...]] | +| +CCFCU=? | +CCFCU: (list of supported <reason>s) | + +### Description + +The command allows control of the communication forwarding supplementary service according to 3GPP TS 22.072 [31], 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]. This command is an extended version of AT commands +CCFC and +CTFR which also supports numbers of the SIP URI format. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service (<mode>=2) the response line for 'not active' case (<status>=0) should be returned only if service is not active for any <class>. + +Test command returns reason values supported as a compound value. + +### Defined values + +<reason>: integer type + +- 0 communication forwarding unconditional – CFU, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 1 communication forwarding on busy user – CFB, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 2 communication forwarding on no reply – CFNR, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 3 communication forwarding on subscriber not reachable – CFNRc, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 4 all call forwarding (refer to "all CF" in 3GPP TS 22.030 [19]) +- 5 all conditional call forwarding (refer to "all conditional CF" in 3GPP TS 22.030 [19]) +- 6 communication deflection – CD, refer 3GPP TS 22.072 [31] and 3GPP TS 24.604 [132] +- 7 communication forwarding on not logged-in – CFNL, refer 3GPP TS 24.604 [132] + +<mode>: integer type + +- 0 disable +- 1 enable +- 2 query status +- 3 registration +- 4 erasure + +<nubertype>: integer type. Indicating type of information in parameter <number>. + +- 0 No valid information in parameter <number>. <number> shall then be set to empty string (""). + +- 1 Number in <number> according to URI including the prefix specifying the URI type (see command +CDU). Parameter <ton> has no relevant information and is set to zero. +- 2 Number in <number> according to one of the formats supported by 3GPP TS 24.008 [8] clause 10.5.4.7) + +<ton>: type of number in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). The parameter is also set to zero when it has no meaningful content, e.g. when <numbertype>=1. + +<number>: string type phone number in format specified by <numbertype>. The used character set should be the one selected with command select TE character set +CSCS. When no number is available, <number> shall be set to empty string (""). + +<subaddr>: string type subaddress of format specified by <satype>. + +<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8); default 128. + +<classx> is a sum of integers each representing a class of information (default 7 - voice, data and fax): + +- 0 communication forwarding without differentiation on class of information +- 1 voice (telephony) +- 2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) +- 4 fax (facsimile services) +- 8 short message service +- 16 data circuit sync +- 32 data circuit async +- 64 dedicated packet access +- 128 dedicated PAD access + +<ruleset>: string type ruleset value of XML element of communication diversion XML document (refer 3GPP TS 24.604 [132]). If XML ruleset values are not supported or intended to be used, the parameter shall be set to an empty string (""). + +<time>: integer type + +- 1...30 when "no reply", "all call forwarding" or "all conditional call forwarding" is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value 20. + +<status>: integer type + +- 0 not active +- 1 active + +## Implementation + +Optional. + +## 7.36 Message waiting indication control +CMWI + +**Table 7.36-1: +CMWI parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------|---------------------------------| +| +CMWI=[<state>[, <expiry_time>]] | +CME ERROR: <err> | +| +CMWI? | +CMWI: <state>[, <expiry_time>] | + +| | | +|---------|---------------------------------------------------------------| +| +CMWI=? | +CMWI: (list of supported <state>s) , (maximum <expiry_time>) | +|---------|---------------------------------------------------------------| + +### Description + +The command allows to control the message waiting indication service according to 3GPP TS 24.606 [134]. + +The set command invokes the service for a certain <expiry\_time> or deactivates the service. Refer clause 9.2 for possible <err> values. + +When the message waiting indication service is activated the unsolicited result code +CMWN: <mw\_notification> is provided to indicate waiting messages. + +The read command returns the message waiting indication service state and the time remaining for the service to be active if available. + +Test command returns values supported as compound values. <expiry\_time>s are supported from 0 to (maximum <expiry\_time>) in seconds. + +### Defined values + +<state>: integer type. Indicates the state of the message waiting indication service. + +- 0 not active +- 1 active + +<expiry\_time>: integer type. Indicates the time in seconds after which the message waiting indication service will become inactive. The range of permitted values is from 0 to (2\*\*32)-1. The default value is implementation specific. + +<mw\_notification>: string type. Indicates waiting message information in application/simple-message-summary MIME type format according to 3GPP TS 24.606 [134]. + +### Implementation + +Optional. + +## 7.37 Session start and stop for MMTEL and SMSoverIP applications +CSCM + +**Table 7.37-1: +CSCM action command syntax** + +| Command | Possible response(s) | +|--------------------------------------------|-----------------------------------------------------------------------------------------| +| +CSCM=<application>,<start-end_indication> | +CME ERROR: <err> | +| +CSCM=? | +CSCM: (list of supported <application>s) , (list of supported <start-end_indication>s) | + +### Description + +This command allows the MMTEL and SMS over IP applications to provide start and stop indications to the MT, for MMTEL voice, MMTEL video or SMSoverIP sessions, in support of + +- SCM (smart congestion mitigation) in E-UTRAN; and +- ACDC (Application specific Congestion control for Data Communications) in E-UTRAN and UTRAN. + +The set command allows the: + +- MMTEL application to provide an indication to the MT when an originating multimedia telephony session for voice communication is started or ended according to the conditions in 3GPP TS 24.173 [87]). +- MMTEL application to provide an indication to the MT when an originating multimedia telephony session for video communication is started or ended according to the conditions in 3GPP TS 24.173 [87]). +- SMS over IP application to provide an indication to the MT when an originating SMS over IP is started or ended according to the conditions in 3GPP TS 24.341 [101]. + +Refer clause 9.2 for possible <err> values. + +The test command returns the supported values as compound values. + +#### Defined values + +<application>: integer type. Type of application. + +- 0 MMTEL voice +- 1 MMTEL video +- 2 SMS over IP + +<start-end\_indication>: integer type. Indication of the start or the end of the session as indicated by <application>. + +- 1 Start indication +- 2 End indication + +#### Implementation + +Optional. + +For SCM, this command is only applicable to UEs in E-UTRAN. + +For ACDC, this command is only applicable to UEs in UTRAN and E-UTRAN. + +## 7.38 Power saving mode setting +CPSMS + +**Table 7.38-1: +CPSMS parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPSMS=[<mode>[, <Requested_Periodic-RAU>[, <Requested_GPRS-READY-timer>[, <Requested_Periodic-TAU>[, <Requested_Active-Time>]]]]] | +CME ERROR: <err> | +| +CPSMS? | +CPSMS: <mode>, [<Requested_Periodic-RAU>], [<Requested_GPRS-READY-timer>], [<Requested_Periodic-TAU>], [<Requested_Active-Time>] | +| +CPSMS=? | +CPSMS: (list of supported <mode>s), (list of supported <Requested_Periodic-RAU>s), (list of supported <Requested_GPRS-READY-timer>s), (list of supported <Requested_Periodic-TAU>s), (list of supported <Requested_Active-Time>s) | + +## Description + +The set command controls the setting of the UE's power saving mode (PSM) parameters. The command controls whether the UE wants to apply PSM or not, as well as the requested extended periodic RAU value and the requested GPRS READY timer value in GERAN/UTRAN, the requested extended periodic TAU value in E-UTRAN and the requested Active Time value. See the unsolicited result codes provided by commands +CGREG for the Active Time value, the extended periodic RAU value and the GPRS READY timer value that are allocated to the UE by the network in GERAN/UTRAN and +CEREG for the Active Time value and the extended periodic TAU value that are allocated to the UE by the network in E-UTRAN. + +A special form of the command can be given as +CPSMS=2. In this form, the use of PSM will be disabled and data for all parameters in the command +CPSMS will be removed or, if available, set to the manufacturer specific default values. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current parameter values. + +The test command returns the supported <mode>s and the value ranges for the requested extended periodic RAU value and the requested GPRS READY timer value in GERAN/UTRAN, the requested extended periodic TAU value in E-UTRAN and the requested Active Time value as compound values. + +## Defined values + +<mode>: integer type. Indication to disable or enable the use of PSM in the UE. + +- 0 Disable the use of PSM +- 1 Enable the use of PSM +- 2 Disable the use of PSM and discard all parameters for PSM or, if available, reset to the manufacturer specific default values. + +<Requested\_Periodic-RAU>: string type; one byte in an 8 bit format. Requested extended periodic RAU value (T3312) to be allocated to the UE in GERAN/UTRAN. The requested extended periodic RAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.060 [47]. The default value, if available, is manufacturer specific. + +<Requested\_GPRS-READY-timer>: string type; one byte in an 8 bit format. Requested GPRS READY timer value (T3314) to be allocated to the UE in GERAN/UTRAN. The requested GPRS READY timer value is coded as one byte (octet 2) of the GPRS Timer information element coded as bit format (e.g. "01000011" equals 3 decihours or 18 minutes). For the coding and the value range, see the GPRS Timer IE in 3GPP TS 24.008 [8] Table 10.5.172/3GPP TS 24.008. See also 3GPP TS 23.060 [47]. The default value, if available, is manufacturer specific. + +<Requested\_Periodic-TAU>: string type; one byte in an 8 bit format. Requested extended periodic TAU value (T3412) to be allocated to the UE in E-UTRAN. The requested extended periodic TAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.401 [82]. The default value, if available, is manufacturer specific. + +<Requested\_Active-Time>: string type; one byte in an 8 bit format. Requested Active Time value (T3324) to be allocated to the UE. The requested Active Time value is coded as one byte (octet 3) of the GPRS Timer 2 information element coded as bit format (e.g. "00100100" equals 4 minutes). For the coding and the value range, see the GPRS Timer 2 IE in 3GPP TS 24.008 [8] Table 10.5.163/3GPP TS 24.008. See also 3GPP TS 23.682 [149], 3GPP TS 23.060 [47] and 3GPP TS 23.401 [82]. The default value, if available, is manufacturer specific. + +## Implementation + +Optional. + +This command is not applicable to UEs in NG-RAN in this release of the specification. + +## 7.39 Application Start and Stop indication for applications other than MMTEL and SMSOverIP +CACDC + +**Table 7.39-1: +CACDC action command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------| +| +CACDC=<OSid>,<OSappid>,<start-stop-indication> | +CME ERROR: <err> | +| +CACDC=? | +CACDC: (list of supported <OSid>,<OSappid> pairs) , (list of supported <start-stop-indication>s) | + +### Description + +This command allows the operating system on the TE to provide start and stop indications other than MMTEL and SMSOverIP to the MT for a particular application in support of ACDC. Each application is identified by an application identity which consists of two parts: + +<OSid> an operating system identifier. This identifier identifies the operating system. + +<OSappid> an OS specific application identifier. This identifier is associated with a given application and uniquely identifies the application within the UE for a given operating system. + +The supported <OSid>s and <OSappid>s are manufacturer specific. + +Refer clause 9.2 for possible <err> values. + +The test command returns the supported values as compound values. + +### Defined values + +<OSid>: string type. Operating system identifier. The format of the OS ID is a Universally Unique Identifier (UUID) as specified in RFC 4122 [155]. + +<OSappid>: string type. A string containing the OS specific application identifier. The format of the OS specific application identifier is manufacturer specific. + +<start-stop-indication>: integer type. Indication to start sending data and the indication to stop sending data, for the application identified by <OSid> and <OSappid>. + +0 indication to start sending data + +1 indication to stop sending data + +### Implementation + +Optional. + +This command is only applicable to UEs in UTRAN and E-UTRAN. + +## 7.40 eDRX setting +CEDRXS + +**Table 7.40-1: +CEDRXS parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| +CEDRXS=[<mode>, [, <AcT-type>, [<Requested_eDRX_value>]]]<br>] | +CME ERROR: <err> | +| +CEDRXS? | [+CEDRXS: <AcT-type>, <Requested_eDRX_value><br><br>[<CR><LF>+CEDRXS: <AcT-type>, <Requested_eDRX_value><br><br>[...]]] | +| +CEDRXS=? | +CEDRXS: (list of supported <mode>s) , (list of supported <AcT-type>s) , (list of supported <Requested_eDRX_value>s) | + +### Description + +The set command controls the setting of the UEs eDRX parameters. The command controls whether the UE wants to apply eDRX or not, as well as the requested eDRX value for each specified type of access technology. + +The set command also controls the presentation of an unsolicited result code +CEDRXP: <AcT-type>, [<Requested\_eDRX\_value>, [<NW-provided\_eDRX\_value>, [<Paging\_time\_window>]]] when <n>=2 and there is a change in the eDRX parameters provided by the network. + +A special form of the command can be given as +CEDRXS=3. In this form, eDRX will be disabled and data for all parameters in the command +CEDRXS will be removed or, if available, set to the manufacturer specific default values. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current settings for each defined value of <AcT-type>. The access technology type parameter <AcT-type>, should not be used in terminals capable of only one access technology. + +The test command returns the supported <mode>s and the value ranges for the access technology and the requested eDRX value as compound values. + +### Defined values + +<mode>: integer type, indicates to disable or enable the use of eDRX in the UE. This parameter is applicable to all specified types of access technology, i.e. the most recent setting of <mode> will take effect for all specified values of <AcT>. + +- 0 Disable the use of eDRX +- 1 Enable the use of eDRX +- 2 Enable the use of eDRX and enable the unsolicited result code ++CEDRXP: <AcT-type>, [<Requested\_eDRX\_value>, [<NW-provided\_eDRX\_value>, [<Paging\_time\_window>]]] +- 3 Disable the use of eDRX and discard all parameters for eDRX or, if available, reset to the manufacturer specific default values. + +<AcT-type>: integer type, indicates the type of access technology. This AT-command is used to specify the relationship between the type of access technology and the requested eDRX value. + +- 0 Access technology is not using eDRX. This parameter value is only used in the unsolicited result code. +- 1 EC-GSM-IoT (A/Gb mode) + +- 2 GSM (A/Gb mode) +- 3 UTRAN (Iu mode) +- 4 E-UTRAN (WB-S1 mode) +- 5 E-UTRAN (NB-S1 mode) +- 6 satellite E-UTRAN (NB-S1 mode) +- 7 satellite E-UTRAN (WB-S1 mode) +- 8 NG-RAN (N1 mode) +- 9 satellite NG-RAN (N1 mode) + +<Requested\_eDRX\_value>: string type; half a byte in a 4 bit format. The eDRX value refers to bit 4 to 1 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. The default value, if available, is manufacturer specific. + +<NW-provided\_eDRX\_value>: string type; half a byte in a 4 bit format. The eDRX value refers to bit 4 to 1 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. + +<Paging\_time\_window>: string type; half a byte in a 4 bit format. The paging time window refers to bit 8 to 5 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see the Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. + +## Implementation + +Optional. + +## 7.41 eDRX read dynamic parameters +CEDRXRDP + +**Table 7.41-1: +CEDRXRDP action command syntax** + +| Command | Possible response(s) | +|-------------|-----------------------------------------------------------------------------------------------------| +| +CEDRXRDP | +CEDRXRDP: <Act-type>[, <Requested_eDRX_value>[, <NW-provided_eDRX_value>[, <Paging_time_window>]]] | +| +CEDRXRDP=? | | + +## Description + +The execution command returns <Act-type> and <Requested\_eDRX\_value>, <NW-provided\_eDRX\_value> and <Paging\_time\_window> if eDRX is used for the cell that the MS is currently registered to. + +If the cell that the MS is currently registered to is not using eDRX, Act-type=0 is returned. + +## Defined values + +<Act-type>: integer type, indicates the type of access technology. This AT-command is used to specify the relationship between the type of access technology and the requested eDRX value. + +- 0 Access technology is not using eDRX +- 1 EC-GSM-IoT (A/Gb mode) + +- 2 GSM (A/Gb mode) +- 3 UTRAN (Iu mode) +- 4 E-UTRAN (WB-S1 mode) +- 5 E-UTRAN (NB-S1 mode) +- 6 satellite E-UTRAN (NB-S1 mode) +- 7 satellite E-UTRAN (WB-S1 mode) +- 8 NG-RAN (N1 mode) +- 9 satellite NG-RAN (N1 mode) + +<Requested\_eDRX\_value>: string type; half a byte in a 4 bit format. The eDRX value refers to bit 4 to 1 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. + +<NW-provided\_eDRX\_value>: string type; half a byte in a 4 bit format. The eDRX value refers to bit 4 to 1 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. + +<Paging\_time\_window>: string type; half a byte in a 4 bit format. The paging time window refers to bit 8 to 5 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see the Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. + +## Implementation + +Optional. + +## 7.42 CIoT optimization configuration +CCIOTOPT + +**Table 7.42-1: CCIOTOPT parameter command syntax** + +| Command | Possible Response(s) | +|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| +CCIOTOPT=[<n>,<br>[<supported_UE_opt>[, <preferred_UE_opt>]]] | +CME ERROR: <err> | +| +CCIOTOPT? | +CCIOTOPT :<n>,<supported_UE_opt>,<preferred_UE_opt> | +| +CCIOTOPT=? | +CCIOTOPT: (list of supported <n>s) , (list of supported <supported_UE_opt>s) , (list of supported <preferred_UE_opt>s) | + +## Description + +The set command controls which CIoT optimizations the UE indicates as supported and preferred in EPS and in 5GS. + +A UE supporting CIoT functionality may support, + +- control plane CIoT EPS optimization or user plane CIoT EPS optimization or both (see 3GPP TS 24.301 [83], clause 9.9.3.34) when the UE is connected to EPC; or +- control plane CIoT 5GS optimization or user plane CIoT 5GS optimization or both (see 3GPP TS 24.501 [161], clause 5.3.21) when the UE is connected to 5GCN. + +Based on the application characteristics the UE may prefer to be registered for, + +- control plane CIoT EPS optimization or for user plane CIoT EPS optimization (see 3GPP TS 24.301 [83], clause 9.9.3.0B) when the UE is connected to EPC; or +- control plane CIoT 5GS optimization or for user plane CIoT 5GS optimization (see 3GPP TS 24.501 [161], clause 5.3.21) when the UE is connected to 5GCN. + +Further, + +- in EPS the network can support control plane CIoT EPS optimization or user plane CIoT EPS optimization or both (see 3GPP TS 24.301 [83], clause 9.9.3.12A); and +- in 5GS the network can support control plane CIoT 5GS optimization or user plane CIoT 5GS optimization or both (see 3GPP TS 24.501 [161], clause 5.3.21) + +The set command is also used to control the reporting of the unsolicited result code +CCIOTOPTI. The unsolicited result code +CCIOTOPTI: <supported\_Network\_opt> is used to indicate the CIoT optimizations supported by the network in EPS and in 5GS. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current settings for supported and preferred CIoT optimizations in EPS, the current settings for supported and preferred CIoT optimizations in 5GS and the current status of unsolicited result code +CCIOTOPTI. + +The test command returns values supported as compound values. + +#### Defined values + +<n>: integer type. Enables or disables reporting of unsolicited result code +CCIOTOPTI. + +- 0 Disable reporting. +- 1 Enable reporting. +- 3 Disable reporting and reset the parameters for supported and preferred CIoT optimizations in EPS and in 5GS to the default values. + +<supported\_UE\_opt>: integer type; a decimal value of the bitmap that indicates the UE's support for CIoT optimizations in EPS and in 5GS. The <supported\_UE\_opt> value is determined by summing all the applicable bits in Table 7.42-2. + +**Table 7.42-2:CIoT optimizations** + +| Bit-number | | | | Description | +|------------|-------|-------|-------|-------------------------------------------------| +| | | | Bit 1 | Support for control plane CIoT EPS optimization | +| | | Bit 2 | | Support for user plane CIoT EPS optimization | +| | Bit 3 | | | Support for control plane CIoT 5GS optimization | +| Bit 4 | | | | Support for user plane CIoT 5GS optimization | + +EXAMPLE If the values of Support for control plane CIoT EPS optimization (Bit 1) and Support for user plane CIoT EPS optimization (Bit 2) are supported, then the <supported\_UE\_opt> value is 3. If the values of Support for user plane CIoT EPS optimization (Bit 2) and Support for user plane CIoT 5GS optimization (Bit 4) are supported, then the <supported\_UE\_opt> value is 10. + +- 0 No support. + +all other values are a decimal value of the bitmap (Bit 1, Bit 2, Bit 3 and Bit 4), see Table 7.42-2. + +<preferred\_UE\_opt>: integer type; indicates the UE's preference for CIoT optimizations in EPS or in 5GS. + +- 0 No preference. + +- 1 Preference for control plane CIoT EPS optimization. +- 2 Preference for user plane CIoT EPS optimization. +- 3 Preference for control plane CIoT 5GS optimization. +- 4 Preference for user plane CIoT 5GS optimization. + +<supported\_Network\_opt>: integer type; indicates the Network support for CIoT optimizations in EPS or in 5GS. + +- 0 No support. +- 1 Support for control plane CIoT EPS optimization. +- 2 Support for user plane CIoT EPS optimization. +- 3 Support for both control plane CIoT EPS optimization and user plane CIoT EPS optimization. +- 4 Support for control plane CIoT 5GS optimization. +- 5 Support for user plane CIoT 5GS optimization. +- 6 Support for both control plane CIoT 5GS optimization and user plane CIoT 5GS optimization. + +## Implementation + +Optional. + +## 7.43 CSG selection +CCSGS + +**Table 7.43: +CCSGS parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------|------------------------------------------------| +| +CCSGS=[<mode>[, <format>[, <CSGinfo>[, <AcT>]]]] | +CCSGS: <AcT> | +| +CCSGS? | +CCSGS: <mode>[, <format>, <CSGinfo>[, <AcT>]] | +| +CCSGS=? | +CCSGS: (list of supported <mode>s) | + +## Description + +Set command forces an attempt to select and register to the CSG Cell in UMTS/EPS network. <mode> is used to determine whether the selection is done automatically by the MT or is forced by this command to select CSG Cell in CSGinfo <CSGinfo> (it shall be given in format <format>) to a certain access technology, indicated in <AcT>. If the selected access technology is not available, then the same CSG id and associated PLMN shall be selected in other access technology. If the selected CSG cell is not available in all supported RATs, then MT shall follow the procedures described in 3GPP TS 23.122 [191] clause 4.4.3.1.3. The selected CSG info format shall apply to further read commands (+CCSGS?) also. <mode>=0 forces an attempt to register to the CSG cell in UMTS/EPS network. <mode>=1 forces an attempt to do manual CSG selection to a CSG cell as per information in CSGinfo <CSGinfo>. <mode>. + +This command is used when the ME performs successfully registered to a PLMN i.e. the UE executed Operator Selection (+COPS) command successfully. + +Read command returns the current CSG selection mode, the currently selected CSG Cell information <CSGinfo> and the current Access Technology. If ME is not camped on CSG Cell when read command is issued, +CME ERROR: XX (Not camped on CSG Cell) shall be issued. + +Test command returns a set of four parameters. A set consists of an integer indicating the availability of the CSG in Operator CSG list or Allowed CSG list <stat>, alphanumeric format of the CSG Type, HNB name, CSG ID and Associated PLMN MCC MNC<CSGinfo>, numeric format representation of the CSG ID and Associated PLMN MCC MNC <CSGinfo> and access technology <AcT>. <CSGinfo> consist of CSGType (if available from SIM), HNB + +name, CSG ID each delimited by comma. CSG Type shall provide the type of a CSG identity in a human readable form. See 3GPP TS 22.011 [170], 3GPP TS 23.003 [7] for details of CSG Type, HNB name and CSG ID representation. Any of the formats may be unavailable and should then be an empty field. The list of found CSG's shall be in order: CSG's in the Operator CSG list, CSG's in the Allowed CSG list, other CSG's. + +It is recommended (although optional) that after the CSG list TA returns lists of supported <mode>s and <format>s. These lists shall be delimited from the CSG list by two commas. + +The access technology selected parameters, <AcT>, should only be used in terminals capable to support CSG selection in more than one access technology. Selection of <AcT> does not limit the capability to cell reselections, even though an attempt is made to select a CSG id in an access technology, the phone may still select the same CSG id and associated PLMN in another access technology. + +### Defined values + +<mode>: integer type + +- 0 automatic CSG Selection mode (<CSGinfo> field is ignored) +- 1 manual CSG Selection mode (<CSGinfo> field shall be present, and <AcT> optionally) +- 2 set only <format> (for read command +CCSGS?), (<CSGinfo> and <AcT> fields are ignored) + +<format>: integer type + +- 0 alphanumeric <CSGinfo> +- 1 numeric <CSGinfo> + +<CSGinfo>: string type; <format> indicates if the format is alphanumeric or numeric + +CSGinfo consists of CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC each delimited by a comma and in this particular order only. If any of the CSGType, HNB Name, CSGID is unavailable, it shall be an empty field. See 3GPP TS 22.011 [170], 3GPP TS 23.003 [7] for details of CSG Type, HNB name and CSG ID representation. When selecting the CSG using the set command with <mode> as 1, the CSGID and associated PLMN MCC MNC are mandatory while CSG Type and HNB name are optional. + +In the alphanumeric format CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC would be displayed while in numeric format only CSGID and CSG Associated PLMN MCC MNC would be displayed. + +<stat>: integer type + +- 0 unknown CSG +- 1 present in Allowed CSG list +- 2 present in Operator CSG list +- 3 forbidden (Reject cause #25 (Not Authorized for this CSG) has been received for the CSGID which is in Operator CSG List) + +<AcT>: integer type; access technology selected + +- 0 UTRAN +- 1 E-UTRAN + +### Implementation + +Optional. + +This command is only applicable to UEs in UTRAN and E-UTRAN. + +## 7.44 CAG selection +CCAGS + +**Table 7.44: +CCAGS parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CCAGS=[<mode>[, <format>[, <CAGinfo>[, <AcT>]]]] | +CCAGS: <AcT> | +| +CCAGS? | +CCAGS: <mode>[, <format>, <CAGinfo>[, <AcT>]] | +| +CCAGS=? | +CCAGS: [<stat>, <format>, <CAGinfo>, <AcT>]<br>[<CR><LF>+CCAGS:<stat>, <format>, <CAGinfo>, <AcT>]<br>[...]]]<br><br>[<CR><LF>+CCAGS: (list of supported <mode>s), (list of supported <format>s)] | + +### Description + +Set command triggers the MT to select and register on a CAG cell. <mode> is used to determine whether the selection is done automatically by the MT or is done in manual selection mode on the CAG cell identified by <CAGinfo> (which shall be given in format <format>) to a certain access technology, indicated in <AcT>. If the selected CAG cell is not available, then the MT shall follow the procedures described in 3GPP TS 23.122 [191] clause 4.4.3.1.2. The selected CAG info format shall apply to further read commands (+CCAGS?) also. <mode>=0 forces an attempt to register to the CAG cell in NR/5GS network. <mode>=1 forces an attempt to do manual CAG selection to a CAG cell as per information in CAGinfo <CAGinfo> + +This command is used when the ME has successfully registered to a PLMN i.e. the UE executed Operator Selection (+COPS) command successfully. + +Read command returns the current CAG selection mode, the currently selected CAG cell information <CAGinfo> and the current Access Technology. If the ME is not camped on a CAG cell when read command is issued, +CME ERROR: XX (Not camped on CAG cell) shall be issued. + +Test command returns a set of four parameters. A set consists of an integer indicating whether the CAG-ID is present in the "Allowed CAG list" <stat>, HRNN, CAG ID and Associated PLMN MCC MNC <CAGinfo>, numeric format representation of the CAG ID and Associated PLMN MCC MNC <CAGinfo> and access technology <AcT>. <CAGinfo> consist of HRNN, CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells, each delimited by a comma. See 3GPP TS 23.003 [7] for details of HRNN and CAG ID representation. Any of the formats may be unavailable and should then be an empty field. + +It is recommended (although optional) that after the CAG list TA returns lists of supported <mode>s and <format>s. These lists shall be delimited from the CAG list by two commas. + +### Defined values + +<mode>: integer type + +- 0 automatic CAG selection mode (<CAGinfo> field is ignored) +- 1 manual CAG selection mode (<CAGinfo> field shall be present, and <AcT> optionally) + +<format>: integer type + +- 0 alphanumeric <CAGinfo> +- 1 numeric <CAGinfo> + +<CAGinfo>: string type; <format> indicates if the format is alphanumeric or numeric + +CAGinfo consists of HRNN, CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells, each delimited by a comma and in this particular order only. If HRNN is unavailable, it shall be an empty field. When selecting the CAG using the set command with <mode> as 1, the CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells are mandatory while the HRNN is optional. + +In the alphanumeric format HRNN, CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells would be displayed while in numeric format only CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells would be displayed. + +<stat>: integer type + +- 0 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 +- 1 Present in "Allowed CAG list" + +<AcT>: integer type; access technology selected + +- 0 NR + +## Implementation + +Optional. + +This command is only applicable to UEs in NG-RAN. + +## 7.45 Informative examples + +This clause includes all the GSM/UMTS supplementary service related commands, additional commands to lock MT and SIM/UICC capabilities, and commands to check the network registration status. + +An example where MSISDNs of a MT are queried, calls are forwarded to different numbers when mobile is busy (CFB) or when it does not answer (CFNRy). The status of CFNRy is read: + +``` +AT+CNUM ++CNUM: ,"358501234567",145,,4 (voice number) +OK +AT+CCFC=1,1,"931123456" (enable CFB) +OK +AT+CCFC=2,1,"921654321" (enable CFNRy) +OK +AT+CCFC=1,2 (query CFNRy) ++CCFC: 1,7,"35821654321",145,,20 (forward after 20 seconds) +OK +``` + +An example of Call Waiting (+CCWA), Call Related Supplementary Services (+CHLD), and Connected Line Identification Presentation (+COLP) usage: + +``` +AT+CCWA=1,1;+COLP=1 (enable call waiting and COLP result codes) +OK +ATD9311234567; (originate a voice call) ++COLP: "+358311234567",145 +OK +...conversation... ++CCWA: "+358317654321",145 (another call is waiting) +AT+CHLD=2 (put first call on hold and answer the second one) +OK +...conversation... +AT+CHLD=1 (release the second (active) call and recover the first (held) call) +OK +ATH (release the first call) +OK +``` + +Call barring supplementary services are combined in one command, Facility Lock (+CLICK), which is also used to restrict MT and SIM/UICC functionality. Some of the facilities require a password when enabled or disabled. An additional command, Change Password (+CPWD), is defined for changing the password of different barring and restriction facilities. An example where locking status of outgoing international calls is interrogated and then barred, and the password of the SIM/UICC card lock (Personal Identity Number, PIN) is changed: + +``` +AT+CLICK="OI", 2 ++CLICK: 0, 7 +OK +AT+CLICK="OI", 1, "1234" +OK +AT+CPWD="SC", "4321", "1234" +OK +``` + +Operator Selection (+COPS) command is used for querying the status of all GSM/UMTS operators detected in the area, and switching between operators. + +Following example illustrates a network selection sequence in Finland. Two operators are found, the status of Tele is unknown and Radiolinja is currently selected. Read command shows that automatic selection mode is on and that Radiolinja is selected. Then an attempt is made to access Tele, but it is denied (shown by +CME ERROR). + +``` +AT+COPS=? ++COPS: (2, "RADIOLINJA", "RL", "24405"), (0, "TELE", "TELE", "24491") +OK +AT+COPS? ++COPS: 0, 0, "RADIOLINJA" +OK +AT+COPS=1, 0, "TELE" ++CME ERROR: 3 +``` + +When a terminal wanders between countries (i.e. networks), an application may follow this e.g. with the following scenario: + +``` +AT+CREG=1 (enable +CREG: <stat> unsolicited result code) +OK +AT+CREG? ++CREG: 1, 1 (MT is registered in home PLMN) +OK +AT+COPS=3, 2; +COPS?; +COPS=3, 0; +COPS? ++COPS: 0, 2, "24405" (get the country... ++COPS: 0, 0, "RADIOLINJA" ...and operator name) +OK +...user wanders to another PLMN... ++CREG: 2 (deregistered, roaming ongoing) ++CREG: 5 (registered again, not home PLMN) +AT+COPS=3, 2; +COPS?; +COPS=3, 0; +COPS? ++COPS: 0, 2, "24001" (get the country... ++COPS: 0, 0, "TELIA MOBITEL" ...and operator name) +OK +...user loses connection, no other PLMNs around... ++CREG: 0 +``` + +An example of eMLPP Supplementary Service usage for a ptp voice call: + +``` +ATD*752#+436644101453; (originate a voice call with the priority level 2, see for priority level definitions GSM 02.30) +OK (call setup was successful) +``` + +## 7.46 Ciphering key request +CCKEYREQ + +**Table 7.46: +CCKEYREQ parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------|-----------------------------------------------------------------------| +| +CCKEYREQ=<n>[, <ciph_req>] | +CME ERROR: <err> | +| +CCKEYREQ? | +CCKEYREQ: <n>, <ciph_req> | +| +CCKEYREQ=? | +CCKEYREQ: (list of supported <n>s) , (list of supported <ciph_req>s) | + +## Description + +The set command controls the presentation of an unsolicited result code + ++CCKEYREQ: <result>[, <no\_of\_ciph\_key\_data\_set>] when <n>=1 and there is a response received from the network for a request to provide new ciphering keys in the registration procedure. The purpose of requesting the ciphering keys is to obtain the list of ciphering data sets from the network that can be used by the UE for deciphering of ciphered broadcast data. The request to obtain the ciphering keys is made through the parameter which will be sent to the network in the registration procedure. + +Read command returns the current set values. + +Test command values supported as a compound value. + +## Defined values + +<n>: integer type + +- 0 disable unsolicited result code +CCKEYREQ: <result>[, <no\_of\_ciph\_key\_data\_set>] +- 1 enable unsolicited result code +CCKEYREQ: <result>[, <no\_of\_ciph\_key\_data\_set>] +- 2 setting unchanged, shall be used by the set command to request ciphering key information from the network + +<ciph\_req>: integer type, indicates whether the UE wants to request ciphering keys for deciphering the broadcast data. + +- 0 do not request ciphering key data set +- 1 request ciphering key data set + +<result>: integer type, indicates whether the registration procedure was successful or not in requesting the ciphering key information. + +- 0 registration procedure requesting the ciphering keys was not successful +- 1 registration procedure requesting the ciphering keys was successful + +<no\_of\_ciph\_key\_data\_set>: integer type, indicates the number of ciphering key data sets received from the network. This field has a valid range of values from (0-16) where 0 indicates that the registration procedure may have been successful, but no ciphering key data set was received. + +## Implementation + +Optional. + +This command is only applicable to UEs supporting 5GS. + +# 8 Mobile termination control and status commands + +## 8.0 General + +This clause includes commands for MT power, keypad, touch screen, display and indicator handling. Also commands for selecting, reading and writing of phonebooks, and setting real-time clock facilities are specified. Two commands are specified for accessing SIM/UICC database records in a general way. + +Figure 7 illustrates the effect of these commands. Command Phone Activity Status +CPAS indicates the current general activity status of the MT. Command Set Phone Functionality +CFUN is used to set the MT to different power consumption states. Command Enter PIN +CPIN is used to enter MT passwords which are needed before any other functionality of the MT can be used (e.g. SIM PIN, PUK). Commands Generic SIM Access +CSIM and Restricted SIM Access +CRSM can be used to access all data in SIM/UICC. Commands Battery Charge +CBC and Signal Quality +CSQ + +are same as in TIA IS-135 [16] and they are used to query the battery charge of the MT and the current RSSI of the MT. Command Mobile Termination Control Mode +CMEC is used to select the controlling unit of MT keypad, display touch screen, and indicators. Controlling commands for the TE are Keypad Emulation +CKPD, Display Control +CDIS, Touch Screen Emulation +CTSA, and Indicator Control +CIND. If corresponding event reporting is enabled with command Mobile Termination Event Reporting +CMER, +CKEV is the result code of a keypad event, +CDEV is the result code of a display event, +CTEV is the result code of a touch screen event, +COEV is the result code of a display orientation event, and +CIEV is the result code of an indicator event. Phonebook commands are Select Phonebook Memory Storage +CPBS, Read Phonebook Entries +CPBR, Find Phonebook Entries +CPBF and Write Phonebook Entry +CPBW. Additional command Clock +CCLK can be used to control the real-time clock of the MT if available. Command Alarm +CALA sets possible alarm clock facilities of the MT. + +![Sequence diagram showing Mobile Termination Control and Status Commands between MT, TA, and TE. The diagram illustrates various command and response exchanges for SIM facilities, keypad, display, indicators, and phonebooks.](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +``` + +sequenceDiagram + participant MT + participant TA + participant TE + + TE->>TA: +CPAS + TE->>TA: +CFUN + TE->>TA: +CPIN, +CSIM, +CRSM + TA->>MT: SIM IF, PASSWORD FACILITIES + MT->>TA: + TE->>TA: +CBC + TE->>TA: +CSQ + TE->>TA: +CMEC + TE->>TA: +CKPD + TA->>MT: KEYPAD + MT->>TA: +CKEV + TA->>TE: + TE->>TA: +CDIS + TA->>MT: DISPLAY + MT->>TA: +CDEV + TA->>TE: + TE->>TA: +CIND + TA->>MT: INDICATORS + MT->>TA: +CIEV + TA->>TE: + TE->>TA: +CIND + TA->>MT: INDICATORS + MT->>TA: +CIEV + TA->>TE: + TE->>TA: +CMER + TE->>TA: +CPBS + TE->>TA: +CPBR, +CPBF + TA->>MT: PHONE-BOOKS + MT->>TA: + TE->>TA: +CPBW + TE->>TA: +CCLK, +CALA + TA->>MT: + MT->>TA: + +``` + +Sequence diagram showing Mobile Termination Control and Status Commands between MT, TA, and TE. The diagram illustrates various command and response exchanges for SIM facilities, keypad, display, indicators, and phonebooks. + +Figure 7: Mobile termination control and status commands + +## 8.1 Phone activity status +CPAS + +**Table 60: +CPAS action command syntax** + +| Command | Possible response(s) | +|---------|------------------------------------------------------------| +| +CPAS | +CPAS: <pas><br><br>+CME ERROR: <err> | +| +CPAS=? | +CPAS: (list of supported <pas>s)<br><br>+CME ERROR: <err> | + +### Description + +Execution command returns the activity status <pas> of the MT. It can be used to interrogate the MT before requesting action from the phone. Refer clause 9.2 for possible <err> values. + +Test command returns values supported by the MT as a compound value. + +### Defined values + +<pas>: integer type + +- 0 ready (MT allows commands from TA/TE) + - 1 unavailable (MT does not allow commands from TA/TE) + - 2 unknown (MT is not guaranteed to respond to instructions) + - 3 ringing (MT is ready for commands from TA/TE, but the ringer is active) + - 4 call in progress (MT is ready for commands from TA/TE, but a call is in progress) + - 5 asleep (MT is unable to process commands from TA/TE because it is in a low functionality state) +- all other values below 128 are reserved by the present document. + +### Implementation + +Mandatory when MT can be operated from TE (refer clause "Mobile termination control mode +CMEC"). + +## 8.2 Set phone functionality +CFUN + +**Table 61: +CFUN parameter command syntax** + +| Command | Possible response(s) | +|-------------------------|-----------------------------------------------------------------------------------------| +| +CFUN=[<fun>[, <rst>] ] | +CME ERROR: <err> | +| +CFUN? | +CFUN: <fun><br><br>+CME ERROR: <err> | +| +CFUN=? | +CFUN: (list of supported <fun>s) , (list of supported <rst>s)<br><br>+CME ERROR: <err> | + +### Description + +Set command selects the level of functionality <fun> in the MT. Level "full functionality" is where the highest level of power is drawn. "Minimum functionality" is where minimum power is drawn. Level of functionality between these may + +also be specified by manufacturers. When supported by manufacturers, MT resetting with `<rst>` parameter may be utilized. Refer clause 9.2 for possible `<err>` values. + +NOTE 1: It is manufacturer specific if this command affects network registration. Command Operator Selection `+COPS` is used to force registration/deregistration. + +Read command returns the current setting of `<fun>`. + +Test command returns values supported by the MT as compound values. + +#### Defined values + +`<fun>`: integer type + +- 0 minimum functionality +- 1 full functionality. Enable (turn on) the transmit and receive RF circuits for all supported radio access technologies. For MTs supporting `+CSRA`, this equals the RATs indicated by the response of `+CSRA=?`. Current `+CSRA` setting is ignored. It is not required that the MT transmit and receive RF circuits are in a disabled state for this setting to have effect. +- 2 disable (turn off) MT transmit RF circuits only +- 3 disable (turn off) MT receive RF circuits only +- 4 disable (turn off) both MT transmit and receive RF circuits +- 5...127 reserved for manufacturers as intermediate states between full and minimum functionality +- 128 Full functionality with radio access support according to the setting of `+CSRA`. Enables (turns on) the transmit and receive RF circuits if not already enabled. This `<fun>` setting is applicable for MTs supporting `+CSRA`. +- 129 Prepare for shutdown. This setting has its prime use when some of the MT's resources (e.g. file system) are located on a tightly integrated TE (host). The MT will execute pending actions resulting in "permanent" changes, e.g. execute pending file system operations. The MT will also make an orderly network detach. After this action and `+CFUN` has returned OK, the MT can be shut down with `<fun>=0`, or by other means. After setting `<fun>=129`, only `<fun>=0` is valid. All other values will make `+CFUN` return ERROR. + +`<rst>`: integer type + +- 0 do not reset the MT before setting it to `<fun>` power level + +NOTE 2: This shall be always default when `<rst>` is not given. + +- 1 reset the MT before setting it to `<fun>` power level + +#### Implementation + +Optional. When `<fun>=128`, is supported, `+CSRA` is required. + +## 8.3 Enter PIN `+CPIN` + +Table 62: `+CPIN` parameter command syntax + +| Command | Possible response(s) | +|--------------------------------------------------|--------------------------------------------------------------------------| +| <code>+CPIN=<pin>[, <newpin>]</code> | <code>+CME ERROR: <err></code> | +| <code>+CPIN?</code> | <code>+CPIN: <code></code><br><code>+CME ERROR: <err></code> | +| <code>+CPIN=?</code> | | + +## Description + +Set command sends to the MT a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH-SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards MT and an error message, +CME ERROR, is returned to TE. Refer clause 9.2 for possible <err> values. + +NOTE 1: SIM PIN, SIM PUK, PH-SIM PIN, PH-FSIM PIN, PH-FSIM PUK, SIM PIN2 and SIM PUK2 refer to the PIN of the selected application on the UICC. For example, in an UTRAN context, the selected application on the currently selected UICC should be a USIM and the SIM PIN then represents the PIN of the selected USIM. See 3GPP TS 31.101 [65] for further details on application selection on the UICC. + +If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, <newpin>, is used to replace the old pin in the SIM. + +NOTE 2: Commands which interact with MT that are accepted when MT is pending SIM PIN, SIM PUK, or PH-SIM are: +CGMI, +CGMM, +CGMR, +CGSN, D112; (emergency call), +CPAS, +CFUN, +CPIN, +CPINR, +CDIS (read and test command only), and +CIND (read and test command only). It is implementation specific whether additional commands can be accepted when MT is pending SIM PIN, SIM PUK, or PH-SIM. + +Read command returns an alphanumeric string indicating whether some password is required or not. + +## Defined values + +<pin>, <newpin>: string type values + +<code> values reserved by the present document: + +| | | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| READY | MT is not pending for any password | +| SIM PIN | MT is waiting SIM PIN to be given | +| SIM PUK | MT is waiting SIM PUK to be given | +| PH-SIM PIN | MT is waiting phone-to-SIM card password to be given | +| PH-FSIM PIN | MT is waiting phone-to-very first SIM card password to be given | +| PH-FSIM PUK | MT is waiting phone-to-very first SIM card unblocking password to be given | +| SIM PIN2 | MT is waiting SIM PIN2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that MT does not block its operation) | +| SIM PUK2 | MT is waiting SIM PUK2 to be given (this <code> is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that MT does not block its operation) | +| PH-NET PIN | MT is waiting network personalization password to be given | +| PH-NET PUK | MT is waiting network personalization unblocking password to be given | +| PH-NETSUB PIN | MT is waiting network subset personalization password to be given | +| PH-NETSUB PUK | MT is waiting network subset personalization unblocking password to be given | +| PH-SP PIN | MT is waiting service provider personalization password to be given | +| PH-SP PUK | MT is waiting service provider personalization unblocking password to be given | + +PH-CORP PIN MT is waiting corporate personalization password to be given + +PH-CORP PUK MT is waiting corporate personalization unblocking password to be given + +### Implementation + +Mandatory for MT not supporting the +CKPD command and supporting AT commands only. + +## 8.4 Battery charge +CBC + +**Table 63: +CBC action command syntax** + +| Command | Possible response(s) | +|---------|---------------------------------------------------------------| +| +CBC | +CBC: <bcs>,<bcl><br><br>+CME ERROR: <err> | +| +CBC=? | +CBC: (list of supported <bcs>s) , (list of supported <bcl>s) | + +### Description + +Execution command returns battery connection status <bcs> and battery charge level <bcl> of the MT. Refer clause 9.2 for possible <err> values. + +Test command returns values supported as compound values. + +### Defined values + +<bcs>: integer type + +- 0 MT is powered by the battery +- 1 MT has a battery connected, but is not powered by it +- 2 MT does not have a battery connected +- 3 Recognized power fault, calls inhibited + +<bcl>: integer type + +- 0 battery is exhausted, or MT does not have a battery connected +- 1...100 battery has 1-100 percent of capacity remaining + +### Implementation + +Optional. + +## 8.5 Signal quality +CSQ + +**Table 64: +CSQ action command syntax** + +| Command | Possible response(s) | +|---------|----------------------------------------------------------------| +| +CSQ | +CSQ: <rssi>,<ber><br><br>+CME ERROR: <err> | +| +CSQ=? | +CSQ: (list of supported <rssi>s) , (list of supported <ber>s) | + +### Description + +Execution command returns received signal strength indication <rssi> and channel bit error rate <ber> from the MT. Refer clause 9.2 for possible <err> values. + +Test command returns values supported as compound values. + +#### Defined values + +<rssi>: integer type + +- 0 -113 dBm or less +- 1 -111 dBm +- 2...30 -109... -53 dBm +- 31 -51 dBm or greater +- 99 not known or not detectable + +<ber>: integer type; channel bit error rate (in percent) + +- 0...7 as RXQUAL values in the table in 3GPP TS 45.008 [20] clause 8.2.4 +- 99 not known or not detectable + +#### Implementation + +Optional. + +## 8.6 Mobile termination control mode +CMEC + +Table 65: +CMEC parameter command syntax + +| Command | Possible response(s) | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| +CMEC=[<keyp>[, <disp>[, <ind>[, <tscrn>]]] | +CME ERROR: <err> | +| +CMEC? | +CMEC: <keyp>, <disp>, <ind>, <tscrn> | +| +CMEC=? | +CMEC: (list of supported <keyp>s) , (list of supported <disp>s) , (list of supported <ind>s) , (list of supported <tscrn>s) | + +#### Description + +Set command selects the equipment, which operates MT keypad, writes to MT display and sets MT indicators. If operation mode is not allowed by the MT, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current settings. + +Test command returns the modes supported as compound values. + +#### Defined values + +<keyp>: integer type + +- 0 MT can be operated only through its keypad (execute command of +CKPD cannot be used) +- 1 MT can be operated only from TE (with command +CKPD) +- 2 MT can be operated from both MT keypad and TE + +<disp>: integer type + +- 0 only MT can write to its display (command +CDIS can only be used to read the display) +- 1 only TE can write to MT display (with command +CDIS) +- 2 MT display can be written by both MT and TE + +<ind>: integer type + +- 0 only MT can set the status of its indicators (command +CIND can only be used to read the indicators) +- 1 only TE can set the status of MT indicators (with command +CIND) +- 2 MT indicators can be set by both MT and TE + +<tscrn>: integer type + +- 0 only MT can set the status of its indicators (execute command of +CTSA cannot be used) +- 1 only TE can set the status of MT indicators (with command +CTSA) +- 2 MT indicators can be set by both MT and TE + +### Implementation + +Mandatory when any of keypad, display or indicator or touch screen commands is implemented. + +## 8.7 Keypad control +CKPD + +**Table 66: +CKPD action command syntax** + +| Command | Possible response(s) | +|-----------------------------------|----------------------| +| +CKPD=<keys>[, <time>[, <pause>]] | +CME ERROR: <err> | +| +CKPD=? | | + +### Description + +Execution command emulates MT keypad by giving each keystroke as a character in a string <keys>. <time>\*0.1 seconds is the time to stroke each key and <pause>\*0.1 seconds is the length of pause between two strokes. If emulating fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. This command should be accepted (OK returned) before actually starting to press the keys. Thus unsolicited result codes of key pressings and display events can be returned (refer clause "Mobile termination event reporting +CMER"). + +### Defined values + +<keys>: string of characters representing keys as listed in the following table 67 (based on PCCA STD-101 [17] Annex I table I-3). Colon character (IRA 58) followed by one character can be used to indicate a manufacturer specific key not listed here. All characters from a semicolon character (IRA 59) to the next single semicolon character are treated as alpha entries and are not converted to key equivalents. All semicolon characters inside alpha entries should be duplicated in the TE and stripped to one before entering to the MT. Pause character (IRA 87 or 119) can be used to pause between key pressings for a time specified by <pause>. All IRA values not listed here are reserved. + +**Table 67: Character codes** + +| Char | IRA (dec) | Comment (+ some known key symbols) | +|--------|-----------|-------------------------------------------------| +| # | 35 | hash (number sign) | +| % | 37 | percent sign (P) | +| * | 42 | star (*) | +| 0... 9 | 48... 57 | number keys | +| : | 58 | escape character for manufacturer specific keys | + +| Char | IRA (dec) | Comment (+ some known key symbols) | +|------|-----------|--------------------------------------| +| ; | 59 | escape character for string entering | +| < | 60 | left arrow | +| > | 62 | right arrow | +| @ | 64 | alpha key (α/ABC) | +| A/a | 65/97 | channel A (A) | +| B/b | 66/98 | channel B (B) | +| C/c | 67/99 | clear display (C/CLR) | +| D/d | 68/100 | volume down | +| E/e | 69/101 | connection end (END) | +| F/f | 70/102 | function (FCN) | +| L/l | 76/108 | phone lock (LOCK) | +| M/m | 77/109 | menu (MENU) | +| P/p | 80/112 | power (PWR) | +| Q/q | 81/113 | quiet/mute (MUTE) | +| R/r | 82/114 | recall last number (R/RCL/MR) | +| S/s | 83/115 | connection start (SEND) | +| T/t | 84/116 | store/ memory (STO/M/M+) | +| U/u | 85/117 | volume up | +| V/v | 86/118 | down arrow | +| W/w | 87/119 | pause character | +| X/x | 88/120 | auxiliary (AUX) | +| Y/y | 89/121 | delete last character (C) | +| [ | 91 | soft key 1 | +| ] | 93 | soft key 2 | +| ^ | 94 | up arrow | + +<time>, <pause>: integer type + +0...255      0... 25.5 seconds (default values are manufacturer specific, but should be so long that a normal MT can handle keystrokes correctly) + +### Implementation + +Mandatory for MT not supporting the +CPIN command and supporting AT commands only. + +## 8.8 Display control +CDIS + +**Table 68: +CDIS parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------|---------------------------------------------------------| +| +CDIS=[<text>[, <text>[, ...]]] | +CME ERROR: <err> | +| +CDIS? | +CDIS: <text>[, <text>[, ...]]<br>+CME ERROR: <err> | +| +CDIS=? | +CDIS: <length>[, <length>[, ...]]<br>+CME ERROR: <err> | + +### Description + +Set command is used to write the contents of MT text type display elements. An element can consist of one character or several characters. The order of element parameters <text> should follow the rule: first is the element in upper left corner, second is the next element to the right and so on. The last element is the element in lower right corner. The number of elements is MT specific. If MT does not allow writing to its display or MT is not currently reachable, + ++CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. If certain element is not writable, setting of it should be ignored. If element parameter is empty field, element shall remain in the previous value. + +NOTE 1: This command cannot be used to write to a display which sum of element lengths exceed the length of the command line buffer of the TA. + +Read command returns the contents of MT display elements. If <text> field is empty (not empty string), MT does not allow the reading of corresponding element. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Test command returns maximum length of each display element. If MT does not offer the length of elements, <length> fields should be empty. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +NOTE 2: MT manufacturer should offer the order and maximum length of elements. + +#### Defined values + +<text>: string type parameter using character set specified by command select TE character set +CSCS + +<length>: integer type parameter giving the maximum length of corresponding <text> parameter + +#### Implementation + +Optional. + +## 8.9 Indicator control +CIND + +Table 69: +CIND parameter command syntax + +| Command | Possible response(s) | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------| +| +CIND=[<ind>[, <ind>[, ...]]] | +CME ERROR: <err> | +| +CIND? | +CIND: <ind>[, <ind>[, ...]]<br>+CME ERROR: <err> | +| +CIND=? | +CIND: (<descr>, (list of supported <ind>s)) [, (<descr>, (list of supported <ind>s)) [, ...]]<br>+CME ERROR: <err> | + +#### Description + +Set command is used to set the values of MT indicators. <ind> value 0 means that the indicator is off (or in state which can be identified as "off"-state), 1 means that indicator is on (or in a state which is more substantial than "off"-state), 2 is more substantial than 1, and so on. If the indicator is a simple on/off style element, it has values 0 and 1. The number of elements is MT specific. If MT does not allow setting of indicators or MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. If certain indicator is not writable, setting of it should be ignored. If parameter is empty field, indicator shall remain in the previous value. + +Read command returns the status of MT indicators. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Test command returns pairs, where string value <descr> is a maximum 16 character description of the indicator and compound value is the allowed values for the indicator. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +NOTE: MT manufacturer should offer the description of supported indicators not listed here and their value ranges and default values. + +#### Defined values + +<ind>: integer type value, which shall be in range of corresponding <descr> + +<descr> values reserved by the present document and their <ind> ranges: + +| | | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| "battchg" | battery charge level (0-5) | +| "signal" | signal quality (0-5) | +| "service" | service availability (0-1) | +| "sounder" | sounder activity (0-1) | +| "message" | message received (0-1) | +| "call" | call in progress (0-1) | +| "vox" | transmit activated by voice activity (0-1) | +| "roam" | roaming indicator (0-1) | +| "smsfull" | a short message memory storage in the MT has become full and a short message has been rejected (2), has become full (1), or memory locations are available (0); i.e. the range is (0-2) | +| "inputstatus" | keypad/touch screen status (0-1) | + +#### Implementation + +Optional. + +## 8.10 Mobile termination event reporting +CMER + +**Table 70: +CMER parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMER=[<mode>[, <keyp>[, <disp>[, <ind>[, <bfr>[, <tscrn>[, <orientation>]]]]]] | +CME ERROR: <err> | +| +CMER? | +CMER: <mode>, <keyp>, <disp>, <ind>, <bfr>, <tscrn>, <orientation> | +| +CMER=? | +CMER: (list of supported <mode>s), (list of supported <keyp>s), (list of supported <disp>s), (list of supported <ind>s), (list of supported <bfr>s), (list of supported <tscrn>s), (list of supported <orientation>s) | + +#### Description + +Set command enables or disables sending of unsolicited result codes from TA to TE in the case of key pressings, display changes, and indicator state changes. <mode> controls the processing of unsolicited result codes specified within this command. <bfr> controls the effect on buffered codes when <mode> 1, 2 or 3 is entered. If setting is not supported by the MT, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current settings. + +Test command returns the modes supported as compound values. + +#### Defined values + +<mode>: integer type + +- 0 buffer unsolicited result codes in the TA; if TA result code buffer is full, codes can be buffered in some other place or the oldest ones can be discarded + +- 1 discard unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode); otherwise forward them directly to the TE +- 2 buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush them to the TE after reservation; otherwise forward them directly to the TE +- 3 forward unsolicited result codes directly to the TE; TA-TE link specific inband technique used to embed result codes and data when TA is in on-line data mode + +<keyp>: integer type + +- 0 no keypad event reporting +- 1 keypad event reporting using unsolicited result code +CKEV: <key>, <press>. <key> indicates the key (refer IRA values defined in table 67 in clause "Keypad control +CKPD") and <press> if the key is pressed or released (1 for pressing and 0 for releasing). Only those key pressings, which are not caused by +CKPD shall be indicated by the TA to the TE. + +NOTE 1: When this mode is enabled, corresponding result codes of all keys currently pressed are flushed to the TA regardless of <bfr> setting. + +- 2 keypad event reporting using unsolicited result code +CKEV: <key>, <press>. All key pressings shall be directed from TA to TE. + +NOTE 2: When this mode is enabled, corresponding result codes of all keys currently pressed are flushed to the TA regardless of <bfr> setting. + +<disp>: integer type + +- 0 no display event reporting +- 1 display event reporting using unsolicited result code +CDEV: <elem>, <text>. <elem> indicates the element order number (as specified for +CDIS) and <text> is the new value of text element. Only those display events, which are not caused by +CDIS shall be indicated by the TA to the TE. Character set used in <text> is as specified by command select TE character set +CSCS +- 2 display event reporting using unsolicited result code +CDEV: <elem>, <text>. All display events shall be directed from TA to TE. Character set used in <text> is as specified by command Select TE Character Set +CSCS + +<ind>: integer type + +- 0 no indicator event reporting +- 1 indicator event reporting using unsolicited result code +CIEV: <ind>, <value>. <ind> indicates the indicator order number (as specified for +CIND) and <value> is the new value of indicator. Only those indicator events, which are not caused by +CIND shall be indicated by the TA to the TE +- 2 indicator event reporting using unsolicited result code +CIEV: <ind>, <value>. All indicator events shall be directed from TA to TE + +<bfr>: integer type + +- 0 TA buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered +- 1 TA buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1...3 is entered (OK response shall be given before flushing the codes) + +<tscrn>: integer type + +- 0 no touch screen event reporting +- 1 touch screen event reporting using unsolicited result code +CTEV: <action>, <x>, <y>. The <x>, <y> parameters indicate the x, y coordinates on the touch screen device (as specified for +CTSA), and + +<action> indicates the action performed on the screen (0 for screen released, 1 for screen depressed, 2 for single tap, and 3 for double tap). Only those touch screen events, which are not caused by +CTSA shall be indicated by the TA to the TE. + +NOTE 3: When this mode is enabled, corresponding result codes of all touch screen actions are flushed to the TA regardless of <bfr> setting. + +- 2 touch screen event reporting using unsolicited result code +CTEV: <action>, <x>, <y>. All touch screen events shall be directed from the TA to the TE. + +NOTE 4: When this mode is enabled, corresponding result codes of all touch screen actions are flushed to the TA regardless of <bfr> setting. + +- 3 Verbose mode. Touch screen event reporting using unsolicited result code +CTEV: <action>, <x>, <y>. This is a special mode where intermediate depressed result codes (+CTEV: 1, <x>, <y>) are generated for each new <x>, <y> coordinate detected while a user is dragging a touch to a new location. All other touch screen actions shall be directed from the TA to the TE normally. Only those touch screen events which are not caused by +CTSA shall be indicated by the TA to the TE. + +NOTE 5: When this mode is enabled, corresponding result codes of all touch screen actions are flushed to the TA regardless of <bfr> setting. + +- 4 enhanced touch screen event reporting using unsolicited result code +CTEV: <action>, <x>, <y>, <id>[, <duration>]. The <x>, <y> parameters indicate the x, y coordinates on the touch screen device (as specified for +CTSA), the <duration> parameter indicates the duration of the touch (as specified for +CTSA) and, the <id> identifies any simultaneous touch (as specified for +CTSA). Only those touch screen events, which are not caused by +CTSA shall be indicated by the TA to the TE. The <action> parameter indicates the action performed on the screen, if the <duration> parameter is: + - 0, it is valid for the <action> parameter to indicate 0 for screen released, 1 for screen depressed, 2 for single tap, and 3 for double tap; + - a positive, non-zero integer, it is valid for the <action> parameter to indicate 0 for screen released. + +NOTE 6: When this mode is enabled, corresponding result codes of all touch screen actions are flushed to the TA regardless of <bfr> setting. + +- 5 enhanced touch screen event reporting using unsolicited result code +CTEV: <action>, <x>, <y>, <id>[, <duration>]. See description of <tscrn> set to 4 for the valid for the <action> parameter. All touch screen events shall be directed from the TA to the TE. + +NOTE 7: When this mode is enabled, corresponding result codes of all touch screen actions are flushed to the TA regardless of <bfr> setting. + +- 6 Verbose mode. enhanced touch screen event reporting using unsolicited result code +CTEV: <action>, <x>, <y>, <id>[, <duration>]. This is a special mode where intermediate depressed result codes (+CTEV: 1, <x>, <y>, <id>[, <duration>]) are generated for each new <x>, <y> coordinate detected while a user is dragging a touch to a new location. All other touch screen actions shall be directed from the TA to the TE normally. See description of <tscrn> set to 4 for the valid for the <action> parameter. Only those touch screen events which are not caused by +CTSA shall be indicated by the TA to the TE. + +NOTE 8: When this mode is enabled, corresponding result codes of all touch screen actions are flushed to the TA regardless of <bfr> setting. + +<orientation>: integer type: Parameter to enable display orientation event reporting from the TA to the TE, using unsolicited result code +COEV: <CurrentTopSide>. The <CurrentTopSide> parameter indicates the top of the ME's screen (as specified for +CSO). + +- 0 No display orientation event reporting. + +- 1 Only those display orientation events, which are not caused by +CSO shall be indicated. +- 2 All display orientation events shall be indicated. + +### Implementation + +Mandatory when any of the keypad, display, or indicator, or touch screen result codes is implemented. + +## 8.11 Select phonebook memory storage +CPBS + +**Table 71: +CPBS parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------|----------------------------------------------------------| +| +CPBS=<storage>[, <password>] | +CME ERROR: <err> | +| +CPBS? | +CPBS: <storage>[, <used>, <total>]<br>+CME ERROR: <err> | +| +CPBS=? | +CPBS: (list of supported <storage>s) | + +### Description + +Set command selects phonebook memory storage <storage>, which is used by other phonebook commands. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns currently selected memory, and when supported by manufacturer, number of used locations and total number of locations in the memory. + +Test command returns supported storages as a compound value. + +### Defined values + +<storage> values reserved by the present document: + +- "DC" MT dialled calls list (+CPBW may not be applicable for this storage) +- "EN" SIM/USIM (or MT) emergency number (+CPBW is not applicable for this storage) +- "FD" SIM/USIM fixdialling-phonebook. In the currently selected card slot, if a SIM card is present or if a UICC with an active GSM application is present, the information in EF<sub>FDN</sub> under DF<sub>Telecom</sub> is selected. If a UICC with an active USIM application is present, the information in EF<sub>FDN</sub> under ADF<sub>USIM</sub> is selected. +- "LD" SIM/UICC last-dialling-phonebook +- "MC" MT missed (unanswered received) calls list (+CPBW may not be applicable for this storage) +- "ME" MT phonebook +- "MT" combined MT and SIM/USIM phonebook +- "ON" SIM (or MT) own numbers (MSISDNs) list (reading of this storage may be available through +CNUM also). When storing information in the SIM/UICC, if a SIM card is present or if a UICC with an active GSM application is present, the information in EF<sub>MSISDN</sub> under DF<sub>Telecom</sub> is selected. If a UICC with an active USIM application is present, the information in EF<sub>MSISDN</sub> under ADF<sub>USIM</sub> is selected. +- "RC" MT received calls list (+CPBW may not be applicable for this storage) +- "SM" SIM/UICC phonebook. In the currently selected card slot, if a SIM card is present or if a UICC with an active GSM application is present, the EF<sub>ADN</sub> under DF<sub>Telecom</sub> is selected. If a UICC with an active USIM application is present, the global phonebook, DF<sub>PHONEBOOK</sub> under DF<sub>Telecom</sub> is selected. +- "TA" TA phonebook + +"AP" Selected application phonebook. In the currently selected card slot, if a UICC with an active USIM application is present, the application phonebook, DF<sub>PHONEBOOK</sub> under ADF<sub>USIM</sub> is selected. + +<password>: string type value representing the PIN2-code required when selecting PIN2-code locked <storage>s above, e.g. "FD" or the hidden key to be verified in order to access to the hidden phonebook entries in the UICC/USIM or any other phonebook with hidden entries. + +If the combined phonebook is selected, "MT", the <password> will correspond to the hidden key of the USIM phonebook. + +<used>: integer type value indicating the number of used locations in selected memory. + +<total>: integer type value indicating the total number of locations in selected memory. + +### Implementation + +Mandatory when phonebook read, find or write command, or direct dialling (refer clause "Direct dialling from phonebooks") is implemented. + +## 8.12 Read phonebook entries +CPBR + +Table 72: +CPBR action command syntax + +| Command | Possible response(s) | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPBR=<index1>[, <index2>] | [+CPBR: <index1>, <number>, <type>, <text>[, <hidden>]<br>[, <group>] [, <adnumber>] [, <adtype>] [, <secondtext>]<br>[, <email>] [, <sip_uri>] [, <tel_uri>]]<br>[...]<br>[<CR><LF>+CPBR: <index2>, <number>, <type>, <text>[, <hidden>]<br>[, <group>] [, <adnumber>] [, <adtype>] [, <secondtext>]<br>[, <email>] [, <sip_uri>] [, <tel_uri>]]]<br><br>+CME ERROR: <err> | +| +CPBR=? | +CPBR: (list of supported <index>s), [<nlength>], [<tlength>],<br>[<glength>], [<slength>], [<elength>], [<siplength>],<br>[<tellength>]<br><br>+CME ERROR: <err> | + +### Description + +Execution command returns phonebook entries in location number range <index1>...<index2> from the current phonebook memory storage selected with +CPBS. If <index2> is left out, only location <index1> is returned. Entry fields returned are location number <indexn>, phone number stored there <number> (of format <type>), text <text> associated with the number, if the selected phonebook supports hidden entries, <hidden> indicating if the entry is hidden, <group> indicating a group the entry may belong to, <adnumber> an additional number (of format <adtype>), <secondtext> a second text field associated with the number, <email> an email field, <sip\_uri> SIP number and <tel\_uri> TEL number. If all queried locations are empty (but available), no information text lines may be returned. If listing fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Test command returns location range supported by the current storage as a compound value and the maximum lengths of <number>, <text>, <group>, <secondtext>, <email>, <sip\_uri> and <tel\_uri> fields. In case of (U)SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +### Defined values + +<index1>, <index2>, <index>: integer type values in the range of location numbers of phonebook memory + +<number>: string type phone number of format <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<text>: string type field of maximum length <tlength>; character set as specified by command select TE character set +CSCS + +<group>: string type field of maximum length <glength>; character set as specified by command select TE character set +CSCS + +<adnumber>: string type phone number of format <adtype> + +<adtype>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<secondtext>: string type field of maximum length <slength>; character set as specified by command select TE character set +CSCS + +<email>: string type field of maximum length <elength>; character set as specified by command select TE character set +CSCS + +<sip\_uri>: string type field of maximum length <siplength>; character set as specified by command select TE character set +CSCS + +<tel\_uri>: string type phone number of maximum length <tellength>; character set as specified by command select TE character set +CSCS + +<nlength>: integer type value indicating the maximum length of field <number> + +<tlength>: integer type value indicating the maximum length of field <text> + +<glength>: integer type value indicating the maximum length of field <group> + +<slength>: integer type value indicating the maximum length of field <secondtext> + +<elength>: integer type value indicating the maximum length of field <email> + +<siplength>: integer type value indicating the maximum length of field <sip\_uri> + +<tellength>: integer type value indicating the maximum length of field <tel\_uri> + +<hidden>: integer type value indicates if the entry is hidden or not + +- 0: phonebook entry not hidden +- 1: phonebook entry hidden + +## Implementation + +Optional. + +## 8.13 Find phonebook entries +CPBF + +**Table 73: +CPBF action command syntax** + +| Command | Possible response(s) | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPBF=<findtext> | [+CPBF: <index1>, <number>, <type>, <text>[, <hidden>]<br>[, <group>] [, <adnumber>] [, <adtype>] [, <secondtext>] [, <email>]<br>[, <sip_uri>] [, <tel_uri>]]<br>[<CR><LF>+CPBF: <index2>, <number>, <type>, <text>[, <hidden>]<br>[, <group>] [, <adnumber>] [, <adtype>] [, <secondtext>] [, <email>]<br>[, <sip_uri>] [, <tel_uri>]]<br>[...]]<br><br>+CME ERROR: <err> | +| +CPBF=? | +CPBF: [<nlength>], [<tlength>], [<glength>], [<slength>],<br>[<elength>], [<siplength>], [<tellength>]<br><br>+CME ERROR: <err> | + +### Description + +Execution command returns phonebook entries (from the current phonebook memory storage selected with +CPBS) which alphanumeric field start with string <findtext>. Entry fields returned are location number <indexn>, phone number stored there <number> (of format <type>), text <text> associated with the number, if the selected phonebook supports hidden entries, <hidden> indicating if the entry is hidden, <group> indicating a group the entry may belong to, <adnumber> an additional number (of format <adtype>), <secondtext> a second text field associated with the number, <email> an email field, <sip\_uri> SIP number and <tel\_uri> TEL number. If listing fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Test command returns the maximum lengths of <number>, <text>, <group>, <secondtext>, <email>, <sip\_uri> and <tel\_uri> fields. In case of (U)SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +### Defined values + +<index1>, <index2>: integer type values in the range of location numbers of phonebook memory + +<number>: string type phone number of format <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<group>: string type field of maximum length <glength>; character set as specified by command select TE character set +CSCS + +<adnumber>: string type phone number of format <adtype> + +<adtype>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<secondtext>: string type field of maximum length <slength>; character set as specified by command select TE character set +CSCS + +<email>: string type field of maximum length <elength>; character set as specified by command select TE character set +CSCS + +<findtext>, <text>: string type field of maximum length <tlength>; character set as specified by command select TE character set +CSCS + +<sip\_uri>: string type field of maximum length <siplength>; character set as specified by command select TE character set +CSCS + +<tel\_uri>: string type phone number of maximum length <tellength>; character set as specified by +command select TE character set +CSCS + +<nlength>: integer type value indicating the maximum length of field <number> + +<tlength>: integer type value indicating the maximum length of field <text> + +<glength>: integer type value indicating the maximum length of field <group> + +<slength>: integer type value indicating the maximum length of field <secondtext> + +<elength>: integer type value indicating the maximum length of field <email> + +<siplength>: integer type value indicating the maximum length of field <sip\_uri> + +<tellength>: integer type value indicating the maximum length of field <tel\_uri> + +<hidden>: integer type value indicates if the entry is hidden or not + +- 0: phonebook entry not hidden +- 1: phonebook entry hidden + +### Implementation + +Optional. + +## 8.14 Write phonebook entry +CPBW + +**Table 74: +CPBW parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPBW=<index>[,<number>[,<type>[,<text>[,<group>[,<adnumber>[,<adtype>[,<secondtext>[,<email>[,<sip_uri>[,<tel_uri>[,<hidden>]]]]]]]]] | +CPBW: <written_index><br><br>+CME ERROR: <err> | +| +CPBW? | +CPBW: <written_index> | +| +CPBW=? | +CPBW: (list of supported <index>s), [<nlength>], (list of supported <type>s), [<tlength>], [<glength>], [<slength>], [<elength>], [<siplength>], [<tellength>]<br><br>+CME ERROR: <err> | + +### Description + +Execution command writes phonebook entry in location number <index> in the current phonebook memory storage selected with +CPBS. Entry fields written are phone number <number> (in the format <type>), text <text> associated with the number, if the selected phonebook supports hidden entries, <hidden> parameter, which indicates if the entry is hidden or not, <group> indicating a group the entry may belong to, <adnumber> an additional number (of format <adtype>), <secondtext> a second text field associated with the number, <email> an email field, <sip\_uri> SIP number and <tel\_uri> TEL number. If all those fields are omitted, the phonebook entry is deleted. If <index> is left out, but <number> is given, the entry is written to the first free location in the phonebook (the implementation of this feature is manufacturer specific). For successful writes where <index> is not given, the intermediate result code +CPBW: <written\_index> may be provided to indicate the location the entry was written to. If writing fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the last <written\_index> value, or -1 if information about previous value is not available. + +NOTE: Changing the current phonebook memory storage with +CPBS to another storage invalidates the last <written\_index> value. + +Test command returns location range supported by the current storage and types of address as compound values, the maximum length of <number> field, supported number formats of the storage, the maximum length of <text> field, the maximum length of <group>, the maximum length of <secondtext>, the maximum length of <email>, the maximum length of <sip\_uri> and the maximum length of <tel\_uri>. In case of SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. If storage does not offer format information, the format list should be empty parenthesis. + +### Defined values + +<index>: integer type values in the range of location numbers of phonebook memory + +<number>: string type phone number of format <type> + +<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) ; default 145 when dialling string includes international access code character "+", otherwise 129 + +<text>: string type field of maximum length <tlength>; character set as specified by command select TE character set +CSCS + +<group>: string type field of maximum length <glength>; character set as specified by command select TE character set +CSCS + +<adnumber>: string type phone number of format <adtype> + +<adtype>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7) + +<secondtext>: string type field of maximum length <slength>; character set as specified by command select TE character set +CSCS + +<email>: string type field of maximum length <elength>; character set as specified by command select TE character set +CSCS + +<sip\_uri>: string type field of maximum length <siplength>; character set as specified by command select TE character set +CSCS + +<tel\_uri>: string type phone number of maximum length <tellength>; character set as specified by command select TE character set +CSCS + +<nlength>: integer type value indicating the maximum length of field <number> + +<tlength>: integer type value indicating the maximum length of field <text> + +<glength>: integer type value indicating the maximum length of field <group> + +<slength>: integer type value indicating the maximum length of field <secondtext> + +<elength>: integer type value indicating the maximum length of field <email> + +<siplength>: integer type value indicating the maximum length of field <sip\_uri> + +<tellength>: integer type value indicating the maximum length of field <tel\_uri> + +<hidden>: integer type value indicates if the entry is hidden or not + +0: phonebook entry not hidden + +1: phonebook entry hidden + +<written\_index>: integer type value indicating the last location number <index> of the written phonebook entry + +## Implementation + +Optional. + +## 8.15 Clock +CCLK + +**Table 75: +CCLK parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CCLK=<time> | +CME ERROR: <err> | +| +CCLK? | +CCLK: <time><br>+CME ERROR: <err> | +| +CCLK=? | | + +### Description + +Set command sets the real-time clock of the MT. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current setting of the clock. + +### Defined values + +3GPP + +<time>: string type value; format is "yy/MM/dd,hh:mm:ss±zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone (indicates the difference, expressed in quarters of an hour, between the local time and GMT; range -96...+96). E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to "94/05/06,22:10:00+08" + +NOTE: If MT does not support time zone information then the three last characters of <time> are not returned by +CCLK?. The format of <time> is specified by use of the +CSDF command. + +### Implementation + +Optional. + +## 8.16 Alarm +CALA + +**Table 76: +CALA parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CALA=<time>[, <n>[, <type>[, <text>[, <recur>[, <silent>]]]]] | +CME ERROR: <err> | +| +CALA? | [+CALA: <time>, <n1>, <type>, [<text>], [<recur>], <silent>]<br>[<CR><LF>+CALA: <time>, <n2>, <type>, [<text>], [<recur>], <silent>]<br>[...]<br><br>+CME ERROR: <err> | +| +CALA=? | +CALA: (list of supported <n>s), (list of supported <type>s), <tlength>, <rlength>, (list of supported <silent>s)<br><br>+CME ERROR: <err> | + +### Description + +Set command sets an alarm time in the MT. There can be an array of different types of alarms, and each alarm may cause different text to be displayed in the MT display. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +To set up a recurrent alarm for one or more days in the week, the <recur>-parameter may be used. + +When an alarm is timed out and executed, the unsolicited result code +CALV: <n> is always returned, even if the alarm is set up to be silent. + +Read command returns the list of current active alarm settings in the MT. + +Test command returns supported array index values, alarm types, and maximum length of the text to be displayed as compound values. + +### Defined values + +<time>: refer +CCLK, +CSDF + +NOTE: If the <recur>-parameter is used, the <time>-parameter must not contain a date. + +<n>, <n1>, <n2>: integer type value indicating the index of the alarm; default is manufacturer specific. + +<type>: integer type value indicating the type of the alarm (e.g. sound, volume, LED); values and default are manufacturer specific. + +<text>: string type value indicating the text to be displayed when alarm time is reached; maximum length <tlength>; values and default are manufacturer specific. + +<tlength>: integer type value indicating the maximum length of <text>. + +<recurr>: string type value indicating day of week for the alarm in one of the following formats (values and default are manufacturer specific): + +"<1..7>[, <1..7> [...]]" Sets a recurrent alarm for one or more days in the week. The digits 1 to 7 corresponds to the days in the week, Monday (1), ..., Sunday (7). + +Example: The string "1, 2, 3, 4, 5" is used to set an alarm for all weekdays. + +"0" Sets a recurrent alarm for all days in the week. + +<rlength>: integer type value indicating the maximum length of <recurr>. + +<silent>: Integer type value indicating if the alarm is silent or not. The default value is manufacturer specific. + +0 the alarm will not be silent + +1 the alarm will be silent and the only result from the alarm is the unsolicited result code +CALV + +## Implementation + +Optional. + +## 8.17 Generic SIM access +CSIM + +**Table 77: +CSIM action command syntax** + +| Command | Possible response(s) | +|--------------------------|-------------------------------------------------| +| +CSIM=<length>,<command> | +CSIM: <length>,<response><br>+CME ERROR: <err> | +| +CSIM=? | | + +## Description + +Set command transmits to the MT the <command> it then shall send as it is to the SIM. In the same manner, the SIM <response> shall be sent back by the MT to the TA as it is. Refer clause 9.2 for possible <err> values. + +This command allows a direct control of the SIM that is installed in the currently selected card slot, by a distant application on the TE. The TE shall then take care of processing SIM information within the frame specified by GSM/UMTS. + +NOTE: Compared to Restricted SIM Access command +CRSM, the definition of +CSIM allows TE to take more control over the SIM-MT interface. The locking and unlocking of the interface may be done by a special <command> value or automatically by TA/MT (by interpreting <command> parameter). In case that TE application does not use the unlock command (or does not send a <command> causing automatic unlock) in a certain timeout value, MT may release the locking. + +## Defined values + +<length>: integer type; length of the characters that are sent to TE in <command> or <response> (two times the actual length of the command or response) + +<command>: command passed on by the MT to the SIM in the format as described in 3GPP TS 51.011 [28] (hexadecimal character format; refer +CSCS) + +<response>: response to the command passed on by the SIM to the MT in the format as described in 3GPP TS 51.011 [28] (hexadecimal character format; refer +CSCS) + +### Implementation + +Optional. + +## 8.18 Restricted SIM access +CRSM + +**Table 78: +CRSM action command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------|--------------------------------------------------------| +| +CRSM=<command>[, <fileid>[, <P1>, <P2>, <P3>[, <data>[, <pathid>]]]] | +CRSM: <sw1>, <sw2>[, <response>]<br>+CME ERROR: <err> | +| +CRSM=? | | + +### Description + +By using this command instead of Generic SIM Access +CSIM TE application has easier but more limited access to the SIM database. Set command transmits to the MT the SIM <command> and its required parameters. If a SIM installed in the currently selected card slot, the MT handles internally all SIM-MT interface locking and file selection routines. As response to the command, MT sends the actual SIM information parameters and response data. MT error result code +CME ERROR may be returned when the command cannot be passed to the SIM, but failure in the execution of the command in the SIM is reported in <sw1> and <sw2> parameters. Refer clause 9.2 for possible <err> values. + +Coordination of command requests to SIM and the ones issued by GSM/UMTS application inside the MT is implementation dependent. However the TE should be aware of the precedence of the GSM/UMTS application commands to the TE commands. + +### Defined values + +<command>: (command passed on by the MT to the SIM; refer 3GPP TS 51.011 [28]): + +| | | +|-------------------------------|---------------| +| 176 | READ BINARY | +| 178 | READ RECORD | +| 192 | GET RESPONSE | +| 214 | UPDATE BINARY | +| 220 | UPDATE RECORD | +| 242 | STATUS | +| 203 | RETRIEVE DATA | +| 219 | SET DATA | +| all other values are reserved | | + +NOTE 1: The MT internally executes all commands necessary for selecting the desired file, before performing the actual command. + +<fileid>: integer type; this is the identifier of a elementary datafile on SIM. Mandatory for every command except STATUS. + +NOTE 2: The range of valid file identifiers depends on the actual SIM and is defined in 3GPP TS 51.011 [28]. Optional files may not be present at all. + +<P1>, <P2>, <P3>: integer type; parameters passed on by the MT to the SIM. These parameters are mandatory for every command, except GET RESPONSE and STATUS. The values are described in 3GPP TS 51.011 [28]. + +<data>: information which shall be written to the SIM (hexadecimal character format; refer +CSCS). + +<pathid>: string type; contains the path of an elementary file on the SIM/UICC in hexadecimal format as defined in ETSI TS 102 221 [60] (e.g. "7F205F70" in SIM and UICC case). The <pathid> shall only be used in the mode "select by path from MF" as defined in ETSI TS 102 221 [60]. + +NOTE 3: Since valid elementary file identifiers may not be unique over all valid dedicated file identifiers the <pathid> indicates the targeted UICC/SIM directory path in case of ambiguous file identifiers. For earlier versions of this specification or if <pathid> is omitted, it could be implementation specific which one will be selected. + +<sw1>, <sw2>: integer type; information from the SIM about the execution of the actual command. These parameters are delivered to the TE in both cases, on successful or failed execution of the command. + +<response>: response of a successful completion of the command previously issued (hexadecimal character format; refer +CSCS). STATUS and GET RESPONSE return data, which gives information about the current elementary datafield. This information includes the type of file and its size (refer 3GPP TS 51.011 [28]). After READ BINARY, READ RECORD or RETRIEVE DATA command the requested data will be returned. <response> is not returned after a successful UPDATE BINARY, UPDATE RECORD or SET DATA command. + +#### Implementation + +Optional. + +## 8.19 Secure control command +CSCC + +**Table 79: +CSCC parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------------|------------------------------------------------------------------------------------------------| +| +CSCC=<mode>[, <cmd_set>[, <token>]] | +CSCC: <challenge><br>+CME ERROR: <err> | +| +CSCC? | +CSCC: <mode>, <cmd_set1><br>[<CR><LF>+CSCC: <mode>, <cmd_set2><br>[...]]<br>+CME ERROR: <err> | +| +CSCC=? | +CSCC: (list of supported <mode>s) , (list of supported <cmd_set>s) | + +#### Description + +This command is used to enable/disable access to commands protected by security mechanism. This enables/disables access to command sets designated as "secure" such as programming of MT. Refer clause 9.2 for possible <err> values. + +The TE asks for a <challenge> with <mode>=1 and one specific command set (<cmd\_set>), the MT replies with the <challenge>, which should be inserted into the identification algorithm in both entities (TE and MT). The algorithm output <token> is sent to the MT with <mode>=2 to enable the specified command set. <mode>=3 is used to disable the command set. + +The read command returns the status (<mode> 2 or 3) of each supported command set. + +Test command returns the values supported as compound values. + +#### Defined values + +3GPP + +<mode>: integer type + +- 1 request challenge token to enable access to specified command set +- 2 enable access to specified command set (<token> required) +- 3 disable access to specified command set + +<cmd\_set>, <cmd\_set1>, <cmd\_set2>: + +- 0 MT/TA code re-programming command set. + +other values below 128 are reserved by the present document. + +<token>: string type; a variable length bit string represented with IRA characters 0 - 9 and A - F, each character representing a nibble; e.g. bit string "0110 1100 1001 1010" is represented by the IRA string "6C9A". The length of the required bit string varies depending on the value of <cmd\_set>. + +<challenge>: same format as token + +### Implementation + +Optional. + +## 8.20 Alert sound mode +CALM + +**Table 80: +CALM parameter command syntax** + +| Command | Possible response(s) | +|----------------|---------------------------------------------------------| +| +CALM=[<mode>] | +CME ERROR: <err> | +| +CALM? | +CALM: <mode><br>+CME ERROR: <err> | +| +CALM=? | +CALM: (list of supported <mode>s)<br>+CME ERROR: <err> | + +### Description + +This command is used to select the general alert sound mode of the MT. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <mode>. + +Test command returns supported values as a compound value. + +### Defined values + +<mode>: integer type + +- 0 normal mode +- 1 silent mode (all sounds from MT are prevented) +- 2... manufacturer specific + +### Implementation + +Optional. + +## 8.21 Ringer sound level +CRSL + +**Table 81: +CRSL parameter command syntax** + +| Command | Possible response(s) | +|---------------|--------------------------------------------------------------| +| +CRSL=<level> | +CME ERROR: <err> | +| +CRSL? | +CRSL: <level><br><br>+CME ERROR: <err> | +| +CRSL=? | +CRSL: (list of supported <level>s)<br><br>+CME ERROR: <err> | + +### Description + +This command is used to select the incoming call ringer sound level of the MT. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <level>. + +Test command returns supported values as a compound value. + +### Defined values + +<level>: integer type value with manufacturer specific range (smallest value represents the lowest sound level) + +### Implementation + +Optional. + +## 8.22 Vibrator mode +CVIB + +**Table 82: +CVIB parameter command syntax** + +| Command | Possible response(s) | +|----------------|-------------------------------------------------------------| +| +CVIB=[<mode>] | +CME ERROR: <err> | +| +CVIB? | +CVIB: <mode><br><br>+CME ERROR: <err> | +| +CVIB=? | +CVIB: (list of supported <mode>s)<br><br>+CME ERROR: <err> | + +### Description + +This command is used to enable and disable the vibrator alert feature of the MT. It is manufacturer specific how this interacts with +CALM command. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <mode>. + +Test command returns supported values as a compound value. + +### Defined values + +<mode>: integer type + +| | | +|---|---------| +| 0 | disable | +| 1 | enable | + +...15 reserved by the present document + +16... manufacturer specific + +#### Implementation + +Optional. + +## 8.23 Loudspeaker volume level +CLVL + +**Table 83: +CLVL parameter command syntax** + +| Command | Possible response(s) | +|---------------|----------------------------------------------------------| +| +CLVL=<level> | +CME ERROR: <err> | +| +CLVL? | +CLVL: <level><br>+CME ERROR: <err> | +| +CLVL=? | +CLVL: (list of supported <level>s)<br>+CME ERROR: <err> | + +#### Description + +This command is used to select the volume of the internal loudspeaker of the MT. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <level>. + +Test command returns supported values as a compound value. + +#### Defined values + +<level>: integer type value with manufacturer specific range (smallest value represents the lowest sound level) + +#### Implementation + +Optional. + +## 8.24 Mute control +CMUT + +**Table 84: +CMUT parameter command syntax** + +| Command | Possible response(s) | +|-------------|---------------------------------| +| +CMUT=[<n>] | +CME ERROR: <err> | +| +CMUT? | +CMUT: <n><br>+CME ERROR: <err> | +| +CMUT=? | +CMUT: (list of supported <n>s) | + +#### Description + +This command is used to enable and disable the uplink voice muting during a voice call. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <n>. + +Test command returns supported values as a compound value. + +#### Defined values + +3GPP + +<n>: integer type + +0 mute off + +1 mute on + +#### Implementation + +Optional. + +## 8.25 Accumulated call meter +CACM + +**Table 85: +CACM parameter command syntax** + +| Command | Possible response(s) | +|------------------|-----------------------------------| +| +CACM=[<passwd>] | +CME ERROR: <err> | +| +CACM? | +CACM: <acm><br>+CME ERROR: <err> | +| +CACM=? | | + +#### Description + +Set command resets the Advice of Charge related accumulated call meter value in SIM card or in the active application in the UICC (GSM or USIM) file EF<sub>ACM</sub>. ACM contains the total number of home units for both the current and preceding calls. SIM PIN2 is usually required to reset the value. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of ACM. + +#### Defined values + +<passwd>: string type; SIM PIN2 + +<acm>: string type; accumulated call meter value similarly coded as <ccm> under +CAOC + +#### Implementation + +Optional. + +## 8.26 Accumulated call meter maximum +CAMM + +**Table 86: +CAMM parameter command syntax** + +| Command | Possible response(s) | +|------------------------------|--------------------------------------| +| +CAMM=[<acmmax>[, <passwd>]] | +CME ERROR: <err> | +| +CAMM? | +CAMM: <acmmax><br>+CME ERROR: <err> | +| +CAMM=? | | + +#### Description + +Set command sets the Advice of Charge related accumulated call meter maximum value in SIM card or in the active application in the UICC (GSM or USIM) file EF<sub>ACMmax</sub>. ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. When ACM (refer +CACM) reaches ACMmax calls are prohibited (see also 3GPP TS 22.024 [26]). SIM PIN2 is usually required to set the value. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of ACMmax. + +#### Defined values + +<acmmax>: string type; accumulated call meter maximum value similarly coded as <ccm> under +CAOC; value zero disables ACMmax feature + +<passwd>: string type; SIM PIN2 + +#### Implementation + +Optional. + +## 8.27 Price per unit and currency table +CPUC + +Table 87: +CPUC parameter command syntax + +| Command | Possible response(s) | +|------------------------------------|----------------------------------------------| +| +CPUC=<currency>,<ppu>[, <passwd>] | +CME ERROR: <err> | +| +CPUC? | +CPUC: <currency>,<ppu><br>+CME ERROR: <err> | +| +CPUC=? | | + +#### Description + +Set command sets the parameters of Advice of Charge related price per unit and currency table in SIM card or in the active application in the UICC (GSM or USIM) file EF<sub>PUCT</sub>. PUCT information can be used to convert the home units (as used in +CAOC, +CACM and +CAMM) into currency units. SIM PIN2 is usually required to set the parameters. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current parameters of PUCT. + +#### Defined values + +<currency>: string type; three-character currency code (e.g. "GBP", "DEM"); character set as specified by command select TE character set +CSCS + +<ppu>: string type; price per unit; dot is used as a decimal separator (e.g. "2.66") + +<passwd>: string type; SIM PIN2 + +#### Implementation + +Optional. + +## 8.28 Call meter maximum event +CCWE + +Table 88: +CCWE parameter command syntax + +| Command | Possible response(s) | +|-------------------|---------------------------------------------------------| +| +CCWE= [ <mode> ] | +CME ERROR: <err> | +| +CCWE? | +CCWE: <mode><br>+CME ERROR: <err> | +| +CCWE=? | +CCWE: (list of supported <mode>s)<br>+CME ERROR: <err> | + +### Description + +Shortly before the ACM (Accumulated Call Meter) maximum value is reached, an unsolicited result code +CCWV will be sent, if enabled by this command. The warning is issued approximately when 30 seconds call time remains. It is also issued when starting a call if less than 30 s call time remains. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current setting. + +Test command returns supported settings as a compound value. + +### Defined values + +<mode>: integer type + +- 0 Disable the call meter warning event +- 1 Enable the call meter warning event + +### Implementation + +Optional. + +## 8.29 Power class +CPWC + +**Table 89: +CPWC parameter command syntax** + +| Command | Possible response(s) | +|---------------------------|---------------------------------------------------------------------------------------------------------------| +| +CPWC=<class>[, <band>] ] | +CME ERROR: <err> | +| +CPWC? | +CPWC: <curr_class1>, <def_class1>, <band1>[, <curr_class2>, <def_class2>, <band2>[...]]<br>+CME ERROR: <err> | +| +CPWC=? | +CPWC: list of supported (<band>, (list of <class>s)) pairs<br>+CME ERROR: <err> | + +### Description + +This command is used to set the preferred MT power class for each GSM frequency band supported. The interaction of this setting with the selected bearer service (+CBST and HSCSD commands) is manufacturer specific (for example, selecting a multislot operation might reduce the power class automatically). If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the currently selected output power class and default output power class for each supported frequency band (as defined by MT manufacturer). Parameter <band1> and its associated power class parameters refer to the currently used frequency band. + +Example: +CPWC: 2, 1, 1, 5, 4, 0 indicates a dual-band MT currently using band GSM1800, for which the power class is currently set to 2, the default being class 1, and for which the currently set power class value for GSM900 is class 5 the default being class 4. + +Test command returns supported bands and their power classes as compound values. + +Example: +CPWC: (0, (0, 4, 5)), (1, (0-2)) indicates a dual-band handheld MT. + +### Defined values + +<class>, <curr\_classn>s, <def\_classn>s: integer type + +- 0 default (not applicable to <curr\_class>s or <def\_classn>s) +- 1... MT output power class as in 3GPP TS 45.005 [38] + +<band>, <bandn>s: + +- 0 GSM900 +- 1 GSM1800 +- 2 reserved for GSM1900 +- 3 GSM 400 + +#### Implementation + +Optional. + +## 8.30 Set language +CLAN + +**Table 90: +CLAN parameter command syntax** + +| Command | Possible response(s) | +|--------------|---------------------------------------------------------| +| +CLAN=<code> | +CME ERROR: <err> | +| +CLAN? | +CLAN: <code><br>+CME ERROR: <err> | +| +CLAN=? | +CLAN: (list of supported <code>s)<br>+CME ERROR: <err> | + +#### Description + +This command sets the language in the MT. The set-command must confirm the selected language with the MMI-module in the MT. If setting fails, a MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +The <code>-parameter is a two-letter abbreviation of the language. The language codes, as defined in ISO 639, consists of two characters, e.g. "sv", "en" etc. + +The complete set of language codes to be used are manufacturer specific and should all be possible to use with the command. Some examples are described under <code>. For a complete list see ISO 639. + +The read command gives the current language as output. If the language has been set to "AUTO", the read command returns the current language set from the currently selected SIM-card /UICC. Hence, the "AUTO"-code is never returned by the read-command. + +Test command returns supported <code>s as a compound value. + +#### Defined values + +<code>: (not all language codes are present in this list) + +- "AUTO" Read language from SIM-card /UICC. "Auto" is not returned by the read-command. +- "sw" Swedish +- "fi" Finnish +- "da" Danish + +"no" Norwegian + "de" German + "fr" French + "es" Spanish + "it" Italian + "en" English + +#### Implementation + +Optional. + +### 8.31 Language event +CLAE + +Table 91: +CLAE parameter command syntax + +| Command | Possible response(s) | +|----------------|---------------------------------------------------------| +| +CLAE=[<mode>] | +CME ERROR: <err> | +| +CLAE? | +CLAE: <mode><br>+CME ERROR: <err> | +| +CLAE=? | +CLAE: (list of supported <mode>s)<br>+CME ERROR: <err> | + +#### Description + +This command is used to enable/disable unsolicited result code +CLAV: <code>. If <mode>=1, +CLAV: <code> is sent from the MT when the language in the MT is changed. If setting fails, a MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current status for <mode>. + +Test command returns supported <mode>s as a compound value. + +#### Defined values + +<mode>: integer type + +- 0 Disable unsolicited result code +CLAV +- 1 Enable unsolicited result code +CLAV + +<code>: For description see +CLAN. + +#### Implementation + +Optional. + +### 8.32 Set greeting text +CSGT + +Table 92: +CSGT parameter command syntax + +| Command | Possible response(s) | +|------------------------|----------------------| +| +CSGT=<mode>[, <text>] | +CME ERROR: <err> | + +| | | +|---------|------------------------------------------------------------------| +| +CSGT? | +CSGT: <text>, <mode><br>+CME ERROR: <err> | +| +CSGT=? | +CSGT: (list of supported <mode>s), <ltext><br>+CME ERROR: <err> | + +### Description + +This command sets and activates the greeting text in the MT. The greeting text is shown in the MT display when the MT is turned on. The command can also be used to deactivate a text. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +The read command queries the current <text> and the status of the <mode> parameter + +Test command returns supported <mode>s as a compound value and the maximum number of characters in <text>. + +Example: +CSGT: (0-1), 20 + +### Defined values + +<mode>: integer type + +- 0 Turn off greeting text +- 1 Turn on greeting text + +<text>: string type. A manufacturer specific free text that can be displayed. The text can not include <CR>. + +<mode>: integer type. Maximum number of characters in <text>. + +### Implementation + +Optional. + +## 8.33 Set voice mail number +CSVM + +Table 93: +CSVM parameter command syntax + +| Command | Possible response(s) | +|------------------------------------|--------------------------------------------------------------------------------------| +| +CSVM=<mode>[, <number>[, <type>]] | +CME ERROR: <err> | +| +CSVM? | +CSVM: <mode>, <number>, <type><br>+CME ERROR: <err> | +| +CSVM=? | +CSVM: (list of supported <mode>s), (list of supported <type>s)<br>+CME ERROR: <err> | + +### Description + +The number to the voice mail server is set with this command. The parameters <number> and <type> can be left out if the parameter <mode> is set to 0. If setting fails, an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the currently selected voice mail number and the status (i.e. enabled/disabled). + +Test command returns supported <mode>s and <type>s as compound values. + +### Defined values + +<mode>: integer type + +- 0 Disable the voice mail number. +- 1 Enable the voice mail number. + +<number>: string type; Character string <0..9,+> + +<type>: integer type; Type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129. + +- 129 ISDN / telephony numbering plan, national / international unknown +- 145 ISDN / telephony numbering plan, international number +- 161 ISDN / telephony numbering plan, national number +- 128 - 255 Other values refer 3GPP TS 24.008 [8] clause 10.5.4.7 + +### Implementation + +Optional. + +## 8.34 Ring melody control +CRMC + +**Table 94: +CRMC parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CRMC=<index>,<volume>[, [<call type>] [, <profile>]] | +CME ERROR: <err> | +| +CRMC? | +CRMC: <index>,<volume>[, [<call type1>] [, <profile1>]]<br>[<CR><LF>+CRMC: <index>,<volume>[, [<call type2>] [, <profile1>]] [...]]<br>[<CR><LF>+CRMC: <index>,<volume>[, [<call type1>] [, <profile2>]]]<br>[<CR><LF>+CRMC: <index>,<volume>[, [<call type2>] [, <profile2>]] [...]]<br><br>+CME ERROR: <err> | +| +CRMC=? | +CRMC: (list of supported <index>s) , (list of supported <volume>s) [, [ (list of supported <call type>s) ] [, (list of supported <profile>s) ]]<br><br>+CME ERROR: <err> | + +### Description + +Write command causes the MT to set a specific ring melody and volume for the selected call type and profile. The default values for the optional parameters are defined by the manufacturer. + +Read command queries the settings for the ring melody. If call types and profiles are available, the corresponding ring melodies are listed. Starting with call type1 and profile1 the ring melody settings for each available profile and call type is issued. + +Test command returns the list of supported indexes, volumes, call types and profiles as compound values. + +Refer clause 9.2 for possible <err> values. + +**Defined values** + +<index>: integer type; manufacturer specific number to identify a certain ring melody + +<volume>: integer type value with manufacturer specific range (smallest value represents the lowest sound level) + +<call type>: integer type; manufacturer specific number for a call type + +<profile>: integer type; manufacturer specific number for a profile + +**Implementation** + +Optional. + +## 8.35 Ring melody playback +CRMP + +**Table 95: +CRMP action command syntax** + +| Command | Possible response(s) | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CRMP=<call type>[, <volume>[, <type>, <index>]] | +CME ERROR: <err> | +| +CRMP=? | +CRMP: (list of supported <call type>s),<br>(list of supported <volume>s), (<type0>),<br>(list of supported <index>s)<br>[<CR><LF>+CRMP: (list of supported <call type>s),<br>(list of supported <volume>s),<br>(<type1>), (list of supported <index>s)]<br><br>+CME ERROR: <err> | + +**Description** + +Execution command causes the MT to playback a specific ring type. The default values for the optional parameters are the current selected in the MT. + +Test command returns the supported call types, volumes, types and indexes as compound values. The manufacturer defined and the user defined values are returned on separate lines. + +Refer clause 9.2 for possible <err> values. + +**Defined values** + +<call type>: integer type; manufacturer specific + +<volume>: integer type value with manufacturer specific range (smallest value represents the lowest sound level) + +<type>: integer type + +0 Manufacturer defined + +1 User defined + +<index>: integer type + +**Implementation** + +Optional. + +## 8.36 Master reset +CMAR + +**Table 96: +CMAR action command syntax** + +| Command | Possible response(s) | +|-------------------------|----------------------| +| +CMAR=<phone lock code> | +CME ERROR: <err> | +| +CMAR=? | +CME ERROR: <err> | + +### Description + +This command requests the MT to reset user data. The user data in the phone will be reset to default values. If setting fails, a MT error, +CME ERROR: <err>, is returned. Refer clause 9.2 for possible <err> values. + +If the MT is locked and this command is used, then the MT will be unlocked after the master reset. + +Test command returns OK. + +### Defined values + +<phone lock code> string type; Security code (Phone Lock code) must be verified before performing the master reset. + +### Implementation + +Optional. + +## 8.37 List all available AT commands +CLAC + +**Table 97: +CLAC action command syntax** + +| Command | Possible response(s) | +|---------|----------------------------------------------------------------------------| +| +CLAC | <AT Command1><br>[<CR><LF><AT Command2><br>[...]]<br><br>+CME ERROR: <err> | +| +CLAC=? | +CME ERROR: <err> | + +### Description + +Execution command causes the MT to return one or more lines of AT Commands. Refer clause 9.2 for possible <err> values. + +NOTE: This command only returns the AT commands that are available for the user. + +### Defined values + +<AT Command>: Defines the AT command including the prefix AT. Text shall not contain the sequence 0<CR> or OK<CR> + +### Implementation + +Optional. + +## 8.38 Delete alarm +CALD + +**Table 98: +CALD action command syntax** + +| Command | Possible response(s) | +|-----------|------------------------------------------------------| +| +CALD=<n> | +CME ERROR: <err> | +| +CALD=? | +CALD: (list of supported <n>s)<br>+CME ERROR: <err> | + +### Description + +Action command deletes an alarm in the MT. If the command fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Test command returns supported array index values as a compound value. + +### Defined values + +<n>: integer type value indicating the index of the alarm; default is manufacturer specific + +### Implementation + +Optional. + +## 8.39 Postpone or dismiss an alarm +CAPD + +**Table 99: +CAPD action command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| +CAPD[=<sec>] | +CME ERROR: <err> | +| +CAPD=? | +CAPD: (list of supported <sec>s)<br>+CME ERROR: <err> | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CAPD=[<sec>]. | | + +### Description + +Set command postpones or dismisses a currently active alarm. If the command fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Test command returns supported <sec>-parameter values as a compound value. + +### Defined values + +<sec>: integer type value indicating the number of seconds to postpone the alarm. If <sec> is set to 0 (default), the alarm is dismissed. + +### Implementation + +Optional. + +## 8.40 Automatic time zone update +CTZU + +**Table 100: +CTZU parameter command syntax** + +| Command | Possible response(s) | +|-----------------|----------------------------------------------------------| +| +CTZU=[<onoff>] | +CME ERROR: <err> | +| +CTZU? | +CTZU: <onoff><br>+CME ERROR: <err> | +| +CTZU=? | +CTZU: (list of supported <onoff>s)<br>+CME ERROR: <err> | + +### Description + +Set command enables and disables automatic time zone update via NITZ. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current settings in the MT. + +Test command returns supported on- and off-values as a compound value. + +### Defined values + +<onoff>: integer type value indicating + +- 0 Disable automatic time zone update via NITZ. +- 1 Enable automatic time zone update via NITZ. + +### Implementation + +Optional. + +## 8.41 Time zone reporting +CTZR + +**Table 101: +CTZR parameter command syntax** + +| Command | Possible response(s) | +|---------------------|--------------------------------------------------------------| +| +CTZR=[<reporting>] | +CME ERROR: <err> | +| +CTZR? | +CTZR:<reporting><br>+CME ERROR: <err> | +| +CTZR=? | +CTZR: (list of supported <reporting>s)<br>+CME ERROR: <err> | + +### Description + +This set command controls the time zone change event reporting. If reporting is enabled the MT returns the unsolicited result code +CTZV: <tz>, +CTZE: <tz>, <dst>, [<time>], or +CTZEU: <tz>, <dst>, [<utime>] whenever the time zone is changed. The MT also provides the time zone upon network registration if provided by the network. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current reporting settings in the MT. + +Test command returns supported <reporting>-values as a compound value. + +NOTE: The Time Zone reporting is not affected by the Automatic Time Zone setting command, +CTZU. + +#### Defined values + +<reporting>: integer type value indicating: + +- 0 disable time zone change event reporting. +- 1 Enable time zone change event reporting by unsolicited result code +CTZV: <tz>. +- 2 Enable extended time zone and local time reporting by unsolicited result code +CTZE: <tz>, <dst>, [<time>]. +- 3 Enable extended time zone and universal time reporting by unsolicited result code +CTZEU: <tz>, <dst>, [<utime>]. + +<tz>: string type value representing the sum of the local time zone (difference between the local time and GMT expressed in quarters of an hour) plus daylight saving time. The format is "±zz", expressed as a fixed width, two digit integer with the range -48 ... +56. To maintain a fixed width, numbers in the range -9 ... +9 are expressed with a leading zero, e.g. "-09", "+00" and "+09". + +<dst>: integer type value indicating whether <tz> includes daylight savings adjustment; + +- 0 <tz> includes no adjustment for Daylight Saving Time +- 1 <tz> includes +1 hour (equals 4 quarters in <tz>) adjustment for daylight saving time +- 2 <tz> includes +2 hours (equals 8 quarters in <tz>) adjustment for daylight saving time + +<time>: string type value representing the local time. The format is "YYYY/MM/DD,hh:mm:ss", expressed as integers representing year (YYYY), month (MM), date (DD), hour (hh), minute (mm) and second (ss). The local time can be derived by the MT from information provided by the network at the time of delivering time zone information and will be present in the unsolicited result code for extended time zone and local time reporting if the universal time is provided by the network. + +<utime>: string type value representing the universal time. The format is "YYYY/MM/DD,hh:mm:ss", expressed as integers representing year (YYYY), month (MM), date (DD), hour (hh), minute (mm) and second (ss). The universal time can be provided by the network at the time of delivering time zone information and will be present in the unsolicited result code for extended time zone and universal time reporting if provided by the network. + +#### Implementation + +Optional. + +## 8.42 Enter protocol mode+CPROT + +Table 102: +CPROT action command syntax + +| Command | Possible response(s) | +|------------------------------------------------|-----------------------------------------------------------| +| +CPROT=<proto>[,<version>[,<lsap1>[,<lsapN>]]] | CONNECT<br>NO CARRIER<br>OK<br>ERROR<br>+CME ERROR: <err> | + +| | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPROT=? | +CPROT: <proto1>[, (list of supported <version>s) [, (list of supported <lsap1>s) [, ... [, (list of supported <lsapN>s) ]]]]<br>[<CR><LF>+CPROT: <proto2>[, (list of supported <version>s) [, (list of supported <lsap1>s) [, ... [, (list of supported <lsapN>s) ]]]]<br>[...]] | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +Set command informs TA that TE wants to establish a peer-to-peer protocol <proto> or upper layer connection (indicating by the <lsap>s setting) with the MT on the link from which the command was received. This command can be used in case the link between TE and MT does not provide itself such a mechanism. + +If MT has succeeded in establishing a logical link between application protocols and external interface, it will send CONNECT message to the TE. Otherwise, the NO CARRIER response will be returned. + +If the CONNECT response is received, TE can start sending <proto> or upper layer frames. + +The connection shall always return for <proto> mode when the protocol session is ended. When the MT receives a disconnect request from its peer entity, it will process it and send OK response to the TE indicating its capability for receiving new AT commands. Since <proto> or upper layers can be accessed in other ways, TA must have pre-knowledge of the fact that connection is initiated with AT+CPROT command. This means that switch to <proto> mode must include some sort of notification to the protocol entity. + +This command can be aborted by sending a <proto> or upper layer disconnection frame. In that case, MT will return in command mode by sending the OK response. + +Refer clause 9.2 for possible <err> values. + +Test command returns values supported as compound values. + +## Defined values + +<proto>: integer type + +- 0 OBEX (refer IrDA Object Exchange Protocol [44]). +- ...15 reserved by the present document +- 16... manufacturer specific + +<version>: version number of <proto>: string type + +<lsap1>: integer type; defines a level of service or application protocol on the top of <proto> layer. It may refer to services or protocols defined in other standards development organizations (SDOs). + +- 1 IrMC level 1 (Minimum Level) Only .(refer [43] clause 2.9.4) +- 2 IrMC level 1 and 2 (Minimum and Access Levels) Only. .(refer [43] clause 2.9.4) +- 4 IrMC level 1, 2 and 3 (Minimum, Access, Index Levels) Only- implies static index support. .(refer [43] clause 2.9.4) +- 8 IrMC level 1, 2 and 4 (Minimum, Access and Sync Levels) Only-implies unique index support. .(refer [43] clause 2.9.4) +- 10 IrMC level 1, 2, 3 and 4 (Minimum, Access, Index and Sync Levels)-implies support of static and unique index. .(refer [43] clause 2.9.4) +- ...15 reserved by the present document +- 16... manufacturer specific + +<lsap2>...<lsapN>: integer type + +In case <lsapN>, <lsapN+1> received in the +CPROT command identifies protocol layers, the protocol identified by N+1 shall be on the top of the protocol identified by N on a framework point of view. + +0...15 reserved by the present document + +16... manufacturer specific + +## Implementation + +Optional. + +## 8.43 Generic UICC logical channel access +CGLA + +**Table 103: +CGLA action command syntax** + +| Command | Possible response(s) | +|----------------------------------------|------------------------------------------------------| +| +CGLA=<sessionid>, <length>, <command> | +CGLA: <length>, <response><br><br>+CME ERROR: <err> | +| +CGLA=? | | + +### Description + +Set command transmits to the MT the <command> it then shall send as it is to the selected UICC. In the same manner the UICC <response> shall be sent back by the MT to the TA as it is. Refer clause 9.2 for possible <err> values. + +This command allows a direct control of the currently selected UICC by a distant application on the TE. The TE shall then take care of processing UICC information within the frame specified by GSM/UMTS. + +Although Generic UICC Logical Channel Access command +CGLA allows TE to take control over the UICC-MT interface, there are some functions of the UICC-MT interface that logically do not need to be accessed from outside the TA/MT. Moreover, for security reason the GSM network authentication should not be handled outside the TA/MT. Therefore it shall not be allowed to execute a Run GSM Algorithm command or an Authenticate command in GSM context from the TE using +CGLA at all time whether the +CGLA is locked or unlocked. This shall not forbid the TE to send Authenticate commands in other security contexts (e.g. EAP security context). + +For example, the TA/MT shall forbid the transfer of the Authenticate command to a USIM application when parameters P2 = 0 (GSM security context). See 3GPP TS 31.102 [59] for USIM authenticate command definition. + +**NOTE:** Compared to Restricted UICC Access command +CRLA, the definition of +CGLA allows TE to take more control over the UICC-MT interface. The locking and unlocking of the interface may be done by a special <command> value or automatically by TA/MT (by interpreting <command> parameter). In case that TE application does not use the unlock command (or does not send a <command> causing automatic unlock) in a certain timeout value, MT may release the locking. + +### Defined values + +<sessionid>: integer type; this is the identifier of the session to be used in order to send the APDU commands to the UICC. It is mandatory in order to send commands to the UICC when targeting applications on the smart card using a logical channel other than the default channel (channel "0"). + +<length>: integer type; length of the characters that are sent to TE in <command> or <response> (two times the actual length of the command or response). + +<command>: command passed on by the MT to the UICC in the format as described in 3GPP TS 31.101 [65] (hexadecimal character format; refer +CSCS). + +<response>: response to the command passed on by the UICC to the MT in the format as described in 3GPP TS 31.101 [65] (hexadecimal character format; refer +CSCS). + +## Implementation + +Optional. + +## 8.44 Restricted UICC logical channel access +CRLA + +**Table 104: +CRLA action command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------|------------------------------------------------------| +| +CRLA=<sessionid>,<command>[,<fileid>[,<P1>,<P2>,<P3>[,<data>[,<pathid>]]]] | +CRLA: <sw1>,<sw2>[,<response>]<br>+CME ERROR: <err> | +| +CRLA=? | | + +### Description + +By using this command instead of Generic UICC Access +CGLA TE application has easier but more limited access to the UICC database. Set command transmits to the MT the UICC <command> and its required parameters. MT handles internally, for the selected UICC, all UICC-MT interface locking and file selection routines. As response to the command, MT sends the actual UICC information parameters and response data. MT error result code +CME ERROR may be returned when the command cannot be passed to the UICC, but failure in the execution of the command in the UICC is reported in <sw1> and <sw2> parameters. Refer clause 9.2 for possible <err> values. + +Coordination of command requests to UICC and the ones issued by GSM/UMTS application inside the MT is implementation dependent. However the TE should be aware of the precedence of the GSM/UMTS application commands to the TE commands. + +### Defined values + +<sessionid>: integer type; this is the identifier of the session to be used in order to send the APDU commands to the UICC. It is mandatory in order to send commands to the UICC when targeting applications on the smart card using a logical channel other than the default channel (channel "0"). + +<command>: (command passed on by the MT to the UICC; refer 3GPP TS 31.101 [65]): + +- 176 READ BINARY +- 178 READ RECORD +- 192 GET RESPONSE +- 214 UPDATE BINARY +- 220 UPDATE RECORD +- 242 STATUS +- 203 RETRIEVE DATA +- 219 SET DATA + +all other values are reserved + +NOTE 1: The MT internally executes all commands necessary for selecting the desired file, before performing the actual command. + +<fileid>: integer type; this is the identifier of an elementary datafile on UICC. Mandatory for every command except STATUS. + +NOTE 2: The range of valid file identifiers depends on the actual UICC and is defined in 3GPP TS 31.101 [65]. Optional files may not be present at all. + +<P1>, <P2>, <P3>: integer type; parameters passed on by the MT to the UICC. These parameters are mandatory for every command, except GET RESPONSE and STATUS. The values are described in 3GPP TS 31.101 [65]. + +<data>: information which shall be written to the SIM (hexadecimal character format; refer +CSCS). + +<pathid>: string type; contains the path of an elementary file on the UICC in hexadecimal format (e.g. "5F704F30" for DF<sub>SoLSA/EF<sub>SAI</sub></sub>). The <pathid> shall only be used in the mode "select by path from current DF" as defined in ETSI TS 102 221 [60]. + +<sw1>, <sw2>: integer type; information from the UICC about the execution of the actual command. These parameters are delivered to the TE in both cases, on successful or failed execution of the command. + +<response>: response of a successful completion of the command previously issued (hexadecimal character format; refer +CSCS). STATUS and GET RESPONSE return data, which gives information about the current elementary datafield. This information includes the type of file and its size (refer 3GPP TS 31.101 [65]). After READ BINARY, READ RECORD or RETRIEVE DATA command the requested data will be returned. + +<response> is not returned after a successful UPDATE BINARY, UPDATE RECORD or SET DATA command. + +### Implementation + +Optional. + +## 8.45 Open logical channel +CCHO + +**Table 105: +CCHO action command syntax** + +| Command | Possible response(s) | +|----------------|--------------------------------------| +| +CCHO=<dfname> | <sessionid><br><br>+CME ERROR: <err> | +| +CCHO=? | | + +### Description + +Execution of the command causes the MT to return <sessionid> to allow the TE to identify a channel that is being allocated by the currently selected UICC, which is attached to ME. The currently selected UICC will open a new logical channel; select the application identified by the <dfname> received with this command and return a session Id as the response. The ME shall restrict the communication between the TE and the UICC to this logical channel. + +This <sessionid> is to be used when sending commands with Restricted UICC Logical Channel access +CRLA or Generic UICC Logical Channel access +CGLA commands. + +NOTE: The logical channel number is contained in the CLASS byte of an APDU command, thus implicitly contained in all APDU commands sent to a UICC. In this case it will be up to the MT to manage the logical channel part of the APDU CLASS byte and to ensure that the chosen logical channel is relevant to the <sessionid> indicated in the AT command. See 3GPP TS 31.101 [65] for further information on logical channels in APDU commands protocol. + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<dfname>: all selectable applications in the UICC are referenced by a DF name coded on 1 to 16 bytes + +<sessionid>: integer type; a session Id to be used in order to target a specific application on the smart card (e.g. (U)SIM, WIM, ISIM) using logical channels mechanism + +See 3GPP TS 31.101 [65] for more information about defined values. + +### Implementation + +Optional. + +## 8.46 Close logical channel +CCHC + +**Table 106: +CCHC action command syntax** + +| Command | Possible response(s) | +|-------------------|--------------------------------| +| +CCHC=<sessionid> | +CCHC<br><br>+CME ERROR: <err> | +| +CCHC=? | | + +### Description + +This command asks the ME to close a communication session with the active UICC. The ME shall close the previously opened logical channel. The TE will no longer be able to send commands on this logical channel. The UICC will close the logical channel when receiving this command. Refer clause 9.2 for possible <err> values. + +### Defined values + +<sessionid>: integer type; a session Id to be used in order to target a specific application on the smart card (e.g. (U)SIM, WIM, ISIM) using logical channels mechanism + +### Implementation + +Optional. + +## 8.47 EAP authentication +CEAP + +**Table 107: +CEAP action command syntax** + +| Command | Possible response(s) | +|--------------------------------------------------------|----------------------------------------------------------------------| +| +CEAP=<dfname>,<EAPMethod>,<EAP packet data>[,<DFeap>] | +CEAP: <EAPsessionid>,<EAP packet response><br><br>+CME ERROR: <err> | +| +CEAP=? | | + +### Description + +This command allows a TE to exchange EAP packets with the UICC or the ME. + +Prior to the execution of this command, the TE shall retrieve the available AIDs using the +CUAD command. The TE shall select one appropriate AID to be addressed. Selection may include asking the user, and considering EAP methods supported by the AIDs. The TE shall set the <dfname> value using the selected AID and shall set the <EAPMethod> value to the requested EAP method. The TE may set the <DFeap> value to the directory file identifier that is applicable to the <EAPMethod>; which is derived from the discretionary data returned by +CUAD. The parameter is mandatory for EAP terminated in UICC. + +If the targeted application on the UICC does support the requested EAP method, the MT shall use the value provided in <DFeap>, and it shall transmit the <EAP packet data> to the UICC application using the Authenticate APDU command as defined in ETSI TS 102 310 [66]. The appropriate DF<sub>EAP</sub> in the ADF must be selected prior to the submission of an EAP Authenticate command with the <EAP packet data>. Then the EAP Response data sent by the UICC application in its response to the Authenticate command shall be provided to the TE in <EAP packet response>. + +If the targeted application on the UICC does not support the requested EAP method and if the MT does support this method then the <EAP packet data> shall be handled by the MT. During the handling of the EAP method, the MT shall run the authentication algorithm on the SIM or USIM, respectively. + +Also the MT has to allocate an <EAPsessionid> in order to identify an EAP session and its corresponding keys and parameters. + +If neither the MT nor the appropriate UICC application support the requested EAP method, the MT shall respond with +CME ERROR: 49 (EAP method not supported). + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<dfname>: string type in hexadecimal character format. All selectable applications are represented in the UICC by an AID coded on 1 to 16 bytes. + +<EAPMethod>: string type in hexadecimal character format. This is the EAP Method Type as defined in RFC 3748 [68] in 1 byte format or 8 bytes expanded format. The value range for 1 byte format and for 8 bytes expanded format is defined in RFC 3748 [68]. + +<EAP packet data>: string type in hexadecimal character format. This is the EAP packet data in hexadecimal character as defined in ETSI TS 102 310 [66]. + +<DFeap>: string type in hexadecimal character format. Contains the DF(EAP) associated with the specified <EAPMethod> on the SIM/UICC as defined in ETSI TS 102 310 [66] (e.g. "6D34"). + +<EAPsessionid>: integer type. This is the identifier of the EAP session to be used in order to retrieve the EAP parameters with EAP Retrieve Parameters +CERP command. Value range is from 1 to 4294967295. + +<EAP packet response>: string type in hexadecimal character format. Defined in ETSI TS 102 310 [66]. + +#### Implementation + +Optional. + +## 8.48 EAP retrieve parameters +CERP + +**Table 108: +CERP action command syntax** + +| Command | Possible response(s) | +|-----------------------------------------|-------------------------------------------------------------| +| +CERP=<EAPsessionid>,<br><EAPparameter> | +CERP: <EAP parameter<br>response><br><br>+CME ERROR: <err> | +| +CERP=? | | + +### Description + +This command allows a TE to retrieve EAP session parameters / derived keys after a run of the +CEAP command. If the EAP session is handled by the UICC then the MT shall return the content of the elementary file corresponding to the indicated <EAPparameter>. Those EFs are defined in ETSI TS 102 310 [66]. + +If the MT handles the EAP session then the MT shall return the corresponding parameter encoded as defined for EAP files, see ETSI TS 102 310 [66]. + +For example, the keys shall be retrieved in the TLV format described in ETSI TS 102 310 [66]. + +If neither the MT nor the appropriate UICC application can provide the requested information (e.g. because the requested EAP session ID does not exist), the MT shall respond with +CME ERROR: 50 (Incorrect parameters). + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<EAPparameter>: integer type. + +- 1 Keys +- 2 Status +- 3 Identity +- 4 Pseudonym + +<EAPsessionid>: integer type; this is the identifier of the EAP session to be used in order to retrieve the EAP parameters corresponding to an active EAP session. Value range is from 1 to 4294967295. + +<EAP parameter response>: string type in hexadecimal character format. The format of the parameter is defined in ETSI TS 102 310 [66]. The <EAP parameter response> depends on the value of the <EAPparameter>. + +### Implementation + +Optional. + +## 8.49 UICC application discovery +CUAD + +**Table 109: +CUAD action command syntax** + +| Command | Possible response(s) | +|------------------|-----------------------------------------------------------------------------| +| +CUAD[=<option>] | +CUAD: <response>[, <active_application>[, <AID>]]<br><br>+CME ERROR: <err> | +| +CUAD=? | +CUAD: (list of supported <option>s) | + +## Description + +This command asks the MT to discover what applications are available for selection on the UICC. According to ETSI TS 102 221 [60], the ME shall access and read the EF<sub>DIR</sub> file in the UICC and return the values that are stored in its records. Each record contains the AID and optionally application parameters of one of the applications available on the UICC. + +If optional parameter(s) are requested and the EF<sub>DIR</sub> file is not present in the UICC, <response> shall be empty. + +Refer clause 9.2 for possible <err> values. + +Test command returns the supported option values as a compound value. + +## Defined values + +<response>: string type in hexadecimal character format. The response is the content of the EF<sub>DIR</sub>. + +<option>: integer type. + +0: no parameters requested in addition to <response>. + +1: include <active\_application>. + +<active\_application>: integer type. + +0: no SIM or USIM active. + +1: active application is SIM. + +2: active application is USIM, followed by <AID>. + +<AID>: string type in hexadecimal character format. AID of active USIM. + +## Implementation + +Optional. + +## 8.50 Mobile originated location request +CMOLR + +**Table 8.50-1: +CMOLR parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMOLR=[<enable>[, <method>[, <hor-acc-set>[, <hor-acc>[, <ver-req>[, <ver-acc-set>[, <ver-acc>[, <vel-req>[, <rep-mode>[, <timeout>[, <interval>[, <shape-rep>[, <plane>[, <NMEA-rep>[, <third-party-address>]]]]]]]]]]]]]]]]] | +CME ERROR: <err> | +| +CMOLR? | +CMOLR: <enable>, <method>, <hor-acc-set>, [<hor-acc>], <ver-req>, [<ver-acc-set>], [<ver-acc>], <vel-req>, <rep-mode>, <timeout>, [<interval>], <shape-rep>, [<plane>], [<NMEA-rep>], [<third-party-address>]<br><br>+CME ERROR: <err> | + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMOLR=? | +CMOLR: (list of supported <enable>s) , (list of supported <method>s) , (list of supported <hor-acc-set>s) , (list of supported <hor-acc>s) , (list of supported <ver-req>s) , (list of supported <ver-acc-set>s) , (list of supported <ver-acc>s) , (list of supported <vel-req>s) , (list of supported <rep-mode>s) , (list of supported <timeout>s) , (list of supported <interval>s) , (list of supported <shape-rep>s) , (list of supported <plane>s) , (list of supported <NMEA-rep>s) , (list of supported <third-party-address>s) | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +Set command initiates a mobile originated location request (MO-LR). The parameter <enable> enables or disables positioning and reporting by unsolicited result codes. Reporting can be performed in the format of GAD shapes <location\_parameters> or in the format of NMEA strings <NMEA-string> or both. The unsolicited result codes that can be provided are +CMOLRG: <location\_parameters> and/or +CMOLRN: <NMEA-string>. + +The method to use for positioning is decided by the parameter <method>. The parameters <hor-acc-set>, <hor-acc>, <ver-req>, <ver-acc-set>, <ver-acc> and <vel-req> indicate accuracy for the MO-LR. The parameter <timeout> indicates how long the MS will wait for a report before an unsolicited result code is provided. A single report or periodic reports can be requested by the parameter <rep-mode>. If periodic reports are requested, the time interval between the reports is specified by the parameter <interval>. If GAD shapes are requested, the GAD shapes that will be accepted in the unsolicited result code +CMOLRG: <location\_parameters> are defined by the parameter <shape-rep>. The parameter <plane> specifies the signalling to use for MO-LR. The parameter <NMEA-rep> indicates possible restrictions in supported NMEA strings that will be accepted in the unsolicited result code +CMOLRN: <NMEA-string>. The parameter <third-party-address> is used to specify the address when reporting to a third party is specified. Additional information about positioning can be found in 3GPP TS 25.305 [77]. If positioning-data cannot be provided at a timeout, the unsolicited result +CMOLRE is provided. Refer clause 9.2 and clause 9.3 for possible <err> values. + +Read command returns the current settings of the parameters <enable>, <method>, <hor-acc-set>, <hor-acc>, <ver-req>, <ver-acc-set>, <ver-acc>, <vel-req>, <rep-mode>, <timeout>, <interval>, <shape-rep>, <plane>, <NMEA-rep> and <third-party-address>. The parameters <hor-acc>, <ver-acc-set>, <ver-acc> and <plane> are only applicable in certain configurations. The parameter <interval> is only applicable if periodic reporting is specified. The parameter <NMEA-rep> is only applicable if reporting is specified by NMEA strings. The parameter <third-party-address> is only applicable if reporting to third party is specified. + +Test command returns the supported values and ranges. + +## Defined values + +<enable>: integer type. Enables and disables reporting location as a result of a MO-LR. Only one <method> can be enabled at any given time. + +- 0 Disables reporting and positioning. +- 1 Enables reporting of NMEA strings by unsolicited result code +CMOLRN: <NMEA-string>. Lack of data at each timeout is indicated by an unsolicited result code +CMOLRE. +- 2 Enables reporting of GAD shapes by unsolicited result code +CMOLRG: <location\_parameters>. Lack of data at each timeout is indicated by an unsolicited result code +CMOLRE. +- 3 Enables reporting of NMEA strings and GAD shapes by unsolicited result codes +CMOLRG: <location\_parameters> and +CMOLRN: <NMEA-string>. Lack of data at each timeout is indicated by an unsolicited result code +CMOLRE. + +NOTE 1: The string of `<location_parameters>` intended for `+CMOLR` can be split into multiple unsolicited result codes e.g. in order to prevent that the string in the unsolicited result code becomes too long. How to split the string is implementation specific. + +`<method>`: integer type. Method for MO-LR. The default value is implementation specific. + +- 0 Unassisted GPS. Autonomous GPS only, no use of assistance data. +- 1 Assisted GPS (see NOTE 2). +- 2 Assisted GANSS (see NOTE 2). +- 3 Assisted GPS and GANSS (see NOTE 2). +- 4 Basic self location (the network determines the position technology). +- 5 Transfer to third party. This method makes the parameters `<shape-rep>` and `<NMEA-rep>` irrelevant (any values are accepted and disregarded). The third party address is given in the parameter `<third-party-address>` (see NOTE 3). +- 6 Retrieval from third party. This method is to get the position estimate of the third party. The third party address is given in the parameter `<third-party-address>`. + +NOTE 2: For the methods that require assistance data, the assistance data obtained from the network is used for a UE-based GPS location procedure. + +NOTE 3: Lack of data at each timeout is not indicated by an unsolicited result code `+CMOLRE` if reporting to third party is specified. + +`<hor-acc-set>`: integer type. + +- 0 Horizontal accuracy not set/specified. +- 1 Horizontal accuracy set in parameter `<hor-acc>`. + +`<hor-acc>`: integer type. Requested accuracy as horizontal uncertainty exponent (refer to 3GPP TS 23.032 [76] clause 6.2). The value range is 0-127. The default value is implementation specific. + +`<ver-req>`: integer type. + +- 0 Vertical coordinate (altitude) is not requested, 2D location fix is acceptable. The parameters `<ver-acc-set>` and `<ver-acc>` do not apply. +- 1 Vertical coordinate (altitude) is requested, 3D location fix is required. + +`<ver-acc-set>`: integer type. + +- 0 Vertical accuracy not set/specified. +- 1 Vertical accuracy set/specified in parameter `<ver-acc>`. + +`<ver-acc>`: integer type. Requested accuracy as vertical uncertainty exponent (refer to 3GPP TS 23.032 [76] clause 6.4). The value range is 0-127. The default value is implementation specific. + +`<vel-req>`: integer type. Requested velocity type (refer to 3GPP TS 23.032 [76] clause 8.6). + +- 0 Velocity not requested. +- 1 Horizontal velocity requested. +- 2 Horizontal velocity and vertical velocity requested. +- 3 Horizontal velocity with uncertainty requested. +- 4 Horizontal velocity with uncertainty and vertical velocity with uncertainty requested. + +<rep-mode>: integer type. Reporting mode. The default value is implementation specific. + +- 0 Single report, the timeout for the MO-LR response request is specified by <timeout>. +- 1 Periodic reporting, the timeout for each MO-LR response request is specified by <timeout> and the interval between each MO-LR is specified by <interval>. + +<timeout>: integer type. Indicates how long the MS will wait for a response after a MO-LR. The value range is in seconds from 1 to 65535. The default value is implementation specific. + +<interval>: integer type. The parameter is applicable to periodic reporting only. Determine the interval between periodic MO-LRs. The value range is in seconds from 1 to 65535, and must be greater than or equal to <timeout>. The default value is implementation specific. + +<shape-rep>: integer type. This parameter is a sum of integers each representing a certain GAD shape that will be accepted in the unsolicited result code +CMOLRG: <location\_parameters>. Note that only one GAD shape is present per unsolicited result code. The default value is implementation specific. + +- 1 Ellipsoid point. +- 2 Ellipsoid point with uncertainty circle. +- 4 Ellipsoid point with uncertainty ellipse. +- 8 Polygon. +- 16 Ellipsoid point with altitude. +- 32 Ellipsoid point with altitude and uncertainty ellipsoid. +- 64 Ellipsoid arc. + +<plane>: integer type. The parameter specifies whether the control plane or SUPL will be used for MO-LR. + +- 0 Control plane. +- 1 Secure user plane (SUPL). + +<NMEA-rep>: string type. The supported NMEA strings that will be accepted in the unsolicited result code +CMOLRN: <NMEA-string> are specified as a comma separated values inside one string. If the parameter is omitted or an empty string is given, no restrictions apply and all NMEA strings are supported. The default value is that all strings are supported. + +Example of NMEA strings: "\$GPRMC,\$GPGSA,\$GPGSV" + +<third-party-address>: string type. The parameter is applicable to reporting to third party only, and specifies the address to the third party. This parameter has to be specified when <method> value is set to 5 or 6. + +<location\_parameters>: string type in UTF-8. This parameter provides XML-formatted strings of GAD-shape positioning data as defined in table 8.50-2. This parameter shall not be subject to conventional character conversion as per +CSCS. The XML according to the DTD in table 8.50-2 may be provided in one or multiple unsolicited result codes. + +**Table 8.50-2: XML DTD for <location\_parameters>** + +``` +<?xml version="1.0" ?> +<!DOCTYPE location_parameters [ +<!ELEMENT location_parameters (time?,direction?,shape_data,velocity_data?)> + <!ELEMENT time (#PCDATA)> + <!ELEMENT direction (#PCDATA)> + <!ELEMENT shape_data (ellipsoid_point|ellipsoid_point_uncert_circle| +ellipsoid_point_uncert_ellipse|polygon|ellipsoid_point_alt| +ellipsoid_point_alt_uncertellipse|ellips_arc)> +``` + +``` + +<!ELEMENT ellipsoid_point (coordinate)> + <!ELEMENT coordinate (latitude,longitude)> + <!ELEMENT latitude (north,degrees)> + <!ELEMENT north (#PCDATA)> + <!ELEMENT degrees (#PCDATA)> + <!ELEMENT longitude (#PCDATA)> + <!ELEMENT ellipsoid_point_uncert_circle (coordinate,uncert_circle)> + <!ELEMENT uncert_circle (#PCDATA)> + <!ELEMENT ellipsoid_point_uncert_ellipse (coordinate,uncert_ellipse)> + <!ELEMENT uncert_ellipse +(uncert_semi_major,uncert_semi_minor,orient_major,confidence)> + <!ELEMENT uncert_semi_major (#PCDATA)> + <!ELEMENT uncert_semi_minor (#PCDATA)> + <!ELEMENT orient_major (#PCDATA)> + <!ELEMENT confidence (#PCDATA)> + <!ELEMENT polygon (coordinate+)> + <!ELEMENT ellipsoid_point_alt (coordinate,altitude)> + <!ELEMENT altitude (height_above_surface,height)> + <!ELEMENT height_above_surface (#PCDATA)> + <!ELEMENT height (#PCDATA)> + <!ELEMENT ellipsoid_point_alt_uncertellipse +(coordinate,altitude,uncert_semi_major,uncert_semi_minor,orient_major,confidence +,uncert_alt)> + <!ELEMENT uncert_alt (#PCDATA)> + <!ELEMENT ellips_arc +(coordinate,inner_rad,uncert_rad,offset_angle,included_angle,confidence)> + <!ELEMENT inner_rad (#PCDATA)> + <!ELEMENT uncert_rad (#PCDATA)> + <!ELEMENT offset_angle (#PCDATA)> + <!ELEMENT included_angle (#PCDATA)> + <!ELEMENT velocity_data +(hor_velocity?,vert_velocity?,vert_velocity_direction?,hor_uncert?,vert_uncert?) +> + <!ELEMENT hor_velocity (#PCDATA)> + <!ELEMENT vert_velocity (#PCDATA)> + <!ELEMENT vert_velocity_direction (#PCDATA)> + <!ELEMENT hor_uncert (#PCDATA)> + <!ELEMENT vert_uncert (#PCDATA)> +] > + +``` + +<NMEA-string>: string type in UTF-8. This parameter provides an NMEA-string as defined in IEC 61162 [78]. This parameter shall not be subject to conventional character conversion as per +CSCS. + +Example:+CMOLRN: "\$GPRMC,235947.000,V,0000.0000,N,00000.0000,E,,,041299,,\*1D<CR><LF>&" + +## Implementation + +Optional. + +## 8.51 Backlight +CBKLT + +Table 8.51-1: +CBKLT parameter command syntax + +| Command | Possible response(s) | +|-------------------------------|---------------------------------------------------| +| +CBKLT=[<state>[,<duration>]] | +CME ERROR: <err> | +| +CBKLT? | +CBKLT: <state>,[<duration>]<br>+CME ERROR: <err> | + +| | | +|----------|---------------------------------------------------------------| +| +CBKLT=? | +CBKLT: (list of supported <state>s)<br><br>+CME ERROR: <err> | +|----------|---------------------------------------------------------------| + +### Description + +This command is used to enable or disable the backlight of the MT's main display. The backlight can be enabled indefinitely or the duration shall be indicated as a specified period of time (in seconds). Refer clause 9.2 for possible <err> values. + +Read command returns the current state and duration (in seconds) if applicable. + +Test command returns supported values as a compound value. + +### Defined values + +<state>: integer type + +- 0 disable +- 1 enable for the duration specified +- 2 enable indefinitely +- 3 enable for a short duration specified by the UE manufacturer + +<duration>: integer type. The range (if seconds) is manufacturer specific. + +xxxx in seconds + +### Implementation + +Optional. + +## 8.52 Command touch screen action +CTSA + +**Table 8.52-1: +CTSA action command syntax** + +| Command | Possible response(s) | +|------------------------------------------|--------------------------------------| +| +CTSA=<action>,<x>,<y>,<id>[,<duration>] | +CME ERROR: <err> | +| +CTSA=? | +CTSA: (list of supported <action>s) | + +### Description: + +This command is used to emulate a touch screen action on the mobile equipment (ME). If emulation fails with an ME error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +This command should be accepted (OK returned) before actually emulating the touch screen action. + +Test command returns the list of supported actions for the mobile equipment. + +The top left corner of the touch screen is defined as the 0, 0 point, see figure 8.52-1. This coordinate does not change regardless of the display mode (portrait or landscape). All coordinate values are non-negative integers. + +![Figure 8.52-1: ME screen outline. The diagram shows two mobile device outlines. The left device has a screen with a red dot at the top-left corner. A vertical double-headed arrow labeled 'Y' and a horizontal double-headed arrow labeled 'X' are shown on the screen. Below the screen are three rows of four small squares each. The right device also has a screen with a red dot at the top-left corner, labeled '0.0'. It has similar 'X' and 'Y' arrows. Below its screen are two rows of eight small squares each. A line connects the red dot on the left device to the '0.0' label on the right device.](3a31a89b46f6eed5da9738f05f81441a_img.jpg) + +Figure 8.52-1: ME screen outline. The diagram shows two mobile device outlines. The left device has a screen with a red dot at the top-left corner. A vertical double-headed arrow labeled 'Y' and a horizontal double-headed arrow labeled 'X' are shown on the screen. Below the screen are three rows of four small squares each. The right device also has a screen with a red dot at the top-left corner, labeled '0.0'. It has similar 'X' and 'Y' arrows. Below its screen are two rows of eight small squares each. A line connects the red dot on the left device to the '0.0' label on the right device. + +**Figure 8.52-1: ME screen outline** + +#### Defined values + +<action>: integer type + +- 0 Release. Emulates the user releasing the touch screen at the <x>, <y> coordinates. +- 1 Depress. Emulates the user depressing the touch screen at location <x>, <y>. + +NOTE 1: Consecutive Depress actions will emulate dragging a stylus on the touch device to the new location. + +- 2 Single Tap. Emulates the user performing a single tap action at the <x>, <y> location. The timing required to emulate a single tap shall be handled by the mobile equipment. +- 3 Double Tap. Emulates the user performing a double tap action at the <x>, <y> location. The timing required to emulate a double tap shall be handled by the mobile equipment. + +<x>: integer type. The horizontal x coordinate location of the action performed on the touch screen. + +<y>: integer type. The vertical y coordinate location of the action performed on the touch screen. + +<id>: integer type. A positive integer value. If *id* is a non-zero integer value *N*, then it represents, or correlates with, the *N*<sup>th</sup> simultaneous touch action performed on the touch screen. If *id* is 0 then the touch screen action is an initial touch screen action or the touch screen action is correlated with the initial touch action. + +NOTE 2: The number of possible simultaneous touch actions is implementation specific. + +<duration>: integer type (the value range is in milliseconds from 1 to 65535). Emulates the user releasing the touch screen at the <x>, <y> coordinates after *duration* milliseconds. If the value is set to 0, then a duration is not indicated. + +Examples: + +**Table 8.52-2: Examples of syntax for various user actions** + +| User Action | Syntax | Description | +|--------------|---------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Depress | AT+CTSA=1, 25, 45 | This will emulate a user pressing down on the ME touch screen at the 25, 45 coordinates. | +| Release | AT+CTSA=0, 25, 45 | This will emulate a user releasing the touch screen at the 25, 45 coordinates. | +| Single Tap | AT+CTSA=2, 25, 45 | This will emulate a user single tapping the touch screen at the 25, 45 coordinates. | +| Double Tap | AT+CTSA=3, 25, 45 | This will emulate a user double tapping the touch screen at the 25, 45 coordinates. | +| Drag | AT+CTSA=1, 10, 10;<br>+CTSA=0, 50, 50 | This will emulate a user touching at 10,10, dragging to 50,50, and releasing. | +| Draw | AT+CTSA=1, 10, 10;<br>+CTSA=1, 50, 50;<br>+CTSA=0, 100, 100 | This will emulate a user touching at 10,10, then dragging to 50,50, then dragging to 100,100 and finally releasing the touch screen at 100,100. | +| Multi Touch | AT+CTSA=1, 10, 10, 0;<br>+CTSA=1, 50, 50, 1;<br>+CTSA=0, 60, 60, 1;<br>+CTSA=0, 100, 100, 0 | This will emulate a user initiating a first gesture touching at 10,10, then simultaneously initiating a second gesture at 50,50, then dragging the second gesture from 50, 50 to 60,60. The user releases the second gesture at 60, 60 while simultaneously dragging the first gesture from 10,10 to 100,100 and finally releasing the touch screen at 100,100. | +| Long Depress | AT+CTSA=1, 10, 10, 0;<br>+CTSA=0, 10, 10, 0, 3000 | This will emulate a user touching at coordinates 10,10, and releasing the touch screen at coordinates 10, 10, after 3 seconds. | + +**Implementation** + +Optional. + +**8.53 Command screen orientation +CSO****Table 8.53-1: +CSO parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------|---------------------------------------------------------------| +| +CSO=<orientation>[, <Current TopSide>] | +CME ERROR: <err> | +| +CSO? | +CSO: <orientation>[, <Current TopSide>]<br>+CME ERROR: <err> | +| +CSO=? | +CSO: (list of supported <orientation>s)<br>+CME ERROR: <err> | + +**Description** + +This command is used to set or read back the orientation of the screen on the mobile equipment (ME). The ME may override the setting via a key press or touch screen action. In addition to setting portrait mode and landscape mode, the command is used by the TE to set a reference orientation for the screen on the ME. The physical orientation of the ME + +shall not override this command. If emulation fails with an ME error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +![A diagram showing a rectangle representing a mobile equipment screen. A single arrow points downwards from the bottom center of the rectangle, indicating the 'Top' side in the normal operating mode.](f260c0f59aedbd9c6658e8ccdd7002d3_img.jpg) + +A diagram showing a rectangle representing a mobile equipment screen. A single arrow points downwards from the bottom center of the rectangle, indicating the 'Top' side in the normal operating mode. + +**Figure 8.53-1: Labelled ME sides when the ME is in the normal operating mode** + +This command should be accepted (OK returned) before actually performing the action. + +Read command returns the current settings. + +Test command returns the list of supported orientations for the mobile equipment as a compound value. + +#### Defined values + +<orientation>: integer type + +- 0 Portrait. The device is in portrait mode. +- 1 Landscape. The device is in landscape mode. +- 2 Any. The top of the ME's screen is identified by <CurrentTopSide> parameter, identifying a side of the screen of the ME. + +<CurrentTopSide>: integer type, representing the label of the side that is the top of the screen. The default value is manufacturer specific. + +- 0 Top. The ME is in the normal operating mode (see figure 8.53-1). +- 1 Right side. The side labelled right side is the side that is the top of the screen. +- 2 Bottom. The side labelled bottom is the side that is the top of the screen. +- 3 Left side. The side labelled left side is the side that is the top of the screen. + +Examples: + +**Table 8.53-2: Examples of syntax for various actions** + +| Action | Syntax | Description | +|-----------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Get Orientation | AT+CSO? | This will return the current orientation of the screen device. | +| Set Orientation | AT+CSO=0 | This will set the current orientation of the screen device to portrait. | +| Set Orientation | AT+CSO=2, 3 | The right side is the current top side (e.g. the top can be determined relative to gravitational forces) and identifies the TE's reference orientation for the screen on the device. | + +#### Implementation + +Optional. + +## 8.54 Command screen size +CSS + +**Table 8.54-1: +CSS action command syntax** + +| Command | Possible response(s) | +|---------|-------------------------------------------------| +| +CSS | +CSS: <Max_X>, <Max_Y><br><br>+CME ERROR: <err> | +| +CSS=? | | + +### Description + +The execution of this command will get the size (in pixels) of the ME's (touch) screen. + +The x-axis and y-axis will be based on a single normal operating mode of the ME, see figure 8.54-1. The 0,0 point will always be located at the top left corner of the screen in the normal operating mode. Changing the ME's mode from e.g. portrait mode to landscape mode does not change the physical location of 0,0 or how the x and y axes are interpreted. + +If emulation fails with an ME error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. This command should be accepted (OK returned) before returning the screen size of the device. + +![Figure 8.54-1: ME screen outline. The diagram shows two views of a mobile device screen. On the left, the screen is in portrait orientation, showing a grid of 12 small squares (3 rows by 4 columns). On the right, the screen is in landscape orientation, showing a grid of 16 small squares (2 rows by 8 columns). Both views have a coordinate system overlaid: a vertical Y-axis pointing downwards and a horizontal X-axis pointing to the right. A red dot at the top-left corner of the screen area is labeled '0,0' with an arrow pointing to it. The device's physical outline, including a small rectangular notch at the top, is also shown.](85a19ac17d00b360442b597f581b5f83_img.jpg) + +Figure 8.54-1: ME screen outline. The diagram shows two views of a mobile device screen. On the left, the screen is in portrait orientation, showing a grid of 12 small squares (3 rows by 4 columns). On the right, the screen is in landscape orientation, showing a grid of 16 small squares (2 rows by 8 columns). Both views have a coordinate system overlaid: a vertical Y-axis pointing downwards and a horizontal X-axis pointing to the right. A red dot at the top-left corner of the screen area is labeled '0,0' with an arrow pointing to it. The device's physical outline, including a small rectangular notch at the top, is also shown. + +**Figure 8.54-1: ME screen outline** + +### Defined values + +<Max\_X>: integer type. Must be a positive integer representing the maximum width of the screen. + +<Max\_Y>: integer type. Must be a positive integer representing the maximum height of the screen + +### Implementation + +Optional. + +## 8.54A Command display screen boundary +CDSB + +**Table 8.54A-1: +CDSB action command syntax** + +| Command | Possible response(s) | +|---------|---------------------------------------------------------------------------------------------------------------------------| +| +CDSB | +CDSB: <Top_Left_X>, <Top_Left_Y>, <Bottom_Right_X>, <Bottom_Right_Y>[, <Width_of_the_Boundary>]<br><br>+CME ERROR: <err> | +| +CDSB=? | | + +### Description + +The execution of this command will identify the boundary between a display area and a non-display area of the ME's (touch) screen. If the display area of the (touch) screen is the same size as the (touch) screen, the values <Top\_Left\_X>, <Top\_Left\_Y> are set to 0, and the values <Bottom\_Right\_X>, <Bottom\_Right\_Y> match the values returned by the command +CSS (see clause 8.54). + +As in clause 8.54, the x-axis and y-axis will be based on a single normal operating mode of the ME. + +If emulation fails with an ME error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +### Defined values + +<Top\_Left\_X>: integer type. Must be a positive integer representing the top left pixel X coordinate of the boundary. + +<Top\_Left\_Y>: integer type. Must be a positive integer representing the top left pixel Y coordinate of the boundary. + +<Bottom\_Right\_X>: integer type. Must be a positive integer representing the bottom right pixel X coordinate of the boundary. + +<Bottom\_Right\_Y>: integer type. Must be a positive integer representing the bottom right pixel Y coordinate of the boundary. + +<Width\_of\_the\_Boundary>: integer type (the value range is in pixels, and starts at 1. The maximum value is implementation specific). Representing the width of the boundary, by default the width is 1 pixel. If the integer value is positive, the boundary is part of the display area of the ME's (touch) screen. If the integer value is negative, the boundary is part of the non-display area of the ME's (touch) screen. + +### Implementation + +Optional. + +## 8.55 Positioning control +CPOS + +**Table 8.55-1: +CPOS Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------------|----------------------| +| +CPOS<CR><br><br>text is entered <ctrl-Z/ESC> | +CME ERROR: <err> | +| +CPOS=? | | + +### Description + +Execution command causes the TE to enter a transparent mode for sending XML formatted data according to table 8.55-2: XML DTD for <pos>. + +Subsequent to +CPOS: + +- the TA shall send a two character sequence <CR><LF> after command line is terminated with <CR>. Then text can be entered from TE to ME/TA. +- the echoing of entered characters back from the TA is controlled by V.25ter echo command E. +- sending may be cancelled by giving <ESC> character (IRA 27). +- <ctrl-Z> (IRA 26) shall be used to indicate the ending of the message body. + +Refer clause 9.2 for possible <err> values. + +### Defined events + +<location>: string type in UTF-8. This parameter provides an XML-formatted string of GAD-shape positioning data similar to what is defined in table 8.55-3. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<assist\_data>: string type in UTF-8. This parameter provides an XML-formatted string of assistance data as defined in table 8.55-5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<GPS\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of GPS measurement data as defined in table 8.55-10. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<GNSS\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of GPS measurement data as defined in table 8.55-11 for LPP procedures and GANSS procedures in RRLP and RRC. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<GPS\_assist\_req>: string type in UTF-8. This parameter provides an XML-formatted string for requesting GPS assistance data as defined in table 8.55-12. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<Strobe>: string type in UTF-8. This parameter provides an XML-formatted string for triggering the generation of strobe as defined in table 8.55-25. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<GNSS\_assist\_req>: string type in UTF-8. This parameter provides an XML-formatted string for requesting GNSS assistance data as defined in table 8.55-15. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<capability\_req> string type in UTF-8. This parameter provides an XML-formatted string for requesting capability data as defined in table 8.55-4. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<msg>: string type in UTF-8. This parameter provides an XML-formatted string for communicating simple messages as defined in table 8.55-13. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<pos\_err>: string type in UTF-8. This parameter provides an XML-formatted string of positioning error parameters as defined in table 8.55-14. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<reset\_assist\_data>: string type in UTF-8. This parameter provides an XML-formatted string for resetting GNSS/OTDOA/Sensor/TBS assistance data as defined in table 8.55-22. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<OTDOA\_ECID\_req>: string type in UTF-8. This parameter provides an XML-formatted string for aborting/requesting location information for OTDOA/ECID method types as defined in table 8.55-23. This parameter shall not be subject to conventional character conversion as per +CSCS. + +NOTE 1: An XML-formatted string intended for +CPOS can be split e.g. in order to prevent that the string becomes too long. Where to split an XML-formatted string is implementation specific. + +<GNSS\_provided\_location\_information>: string type in UTF-8. This parameter provides an XML-formatted string of GAD-shape positioning data as defined in table 8.55-19. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<Add\_pos\_req>: string type in UTF-8. This parameter provides an XML-formatted string for aborting/requesting location information for Additional Positioning method types (Bluetooth/Sensor/TBS/WLAN) as defined in table 8.55-2. This parameter shall not be subject to conventional character conversion as per +CSCS. + +**Table 8.55-2: XML DTD for <pos>** + +``` +<?xml version="1.0" ?> +<!DOCTYPE pos[ +<!ELEMENT pos (location|GNSS_provided_location_information|assist_data|pos_meas|pos_meas_req| +GPS_meas|OTDOA_ECID_req|Add_pos_req|OTDOA_meas|ECID_meas|GNSS_meas|Bluetooth_meas|Sensor_meas| +TBS_meas|WLAN_meas|GPS_assist_req|GNSS_assist_req|OTDOA_assist_req|Sensor_assist_req|TBS_assist_req| +capability_req|capabilities|msg|pos_err|reset_assist_data|Strobe)> + <!ATTLIST pos protocol (RRLP|RRC|LPP) #IMPLIED + transaction_id CDATA #IMPLIED> +]> +``` + +NOTE 2: The XML DTD for 'pos' is the top-level definition of all positioning events, containing elements going in both directions between the MS and the network. The subelements of 'pos' are superset definitions of the positioning events. A variable amount of these elements can be sent. Sent elements must follow the rules for the XML, e.g. elements postfix by '?' can occur zero or more times. The total delivery must be a complete specification. Sub-elements cannot be delivered without being preceded with an element reference from the above level. + +**Table 8.55-3: XML DTD for <location>** + +``` +<!ELEMENT location (location_parameters,time_of_fix?,time_assistance?)> + <!ELEMENT time_of_fix (#PCDATA)> + <!ELEMENT time_assistance (GPS_time, (GSM_time|WCDMA_time|LTE_time) ?, TimeUnc?)> +``` + +NOTE 3: The element 'location\_parameters' provides one or more XML-formatted strings of GAD-shape positioning data as defined in table 8.50-2. + +NOTE 3a: The elements 'time\_of\_fix' of 'location' and 'time' of 'location\_parameters' (see Table 8.50-2) are both for holding time-stamp of the location information. Due to this, the parameter 'time\_of\_fix' can be omitted when 'time' is present or vice versa. + +**Table 8.55-4: XML DTD for <capability\_req>, <capabilities>** + +``` +<!ELEMENT capability_req EMPTY> + +<!ELEMENT capabilities +(GPS_method?, GNSS_method*, GPS_aid?, GNSS_aid?, OTDOA_capability?, ECID_capability?, Bluetooth_capability +?, Sensor_capability?, TBS_capability?, WLAN_capability?)> + <!ELEMENT GPS_Method (MSA_sup?, MSB_sup?, Standalone_sup?)> + <!ELEMENT MSA_sup EMPTY> + <!ATTLIST MSA_sup fta_sup CDATA "000"> <!-- as LPP fta-MeasSupport --> + <!ELEMENT MSB_sup EMPTY> + <!ATTLIST MSB_sup fta_sup CDATA "000" + velocity_sup (true|false) "false"> + <!ELEMENT Standalone_sup EMPTY> + <!ATTLIST Standalone_sup fta_sup CDATA "000" + <!-- as LPP fta-MeasSupport --> + velocity_sup (true|false) "false"> + <!ELEMENT GNSS_Method (MSA_sup?, MSB_sup?, Standalone_sup?)> +``` + +``` + +<!ATTLIST GNSS_Method supported_signal (GPS_L1|GPS_L1C|GPS_L2C|GPS_L5|SBAS_L1|GLO_G1|GLO_G2| +GLO_G3|BDS_B1I) "GPS_L1"> +<!ELEMENT GPS_aid +(almanac_sup?,UTC_model_sup?,ionospheric_sup?,nav_model_sup?,DGPS_sup?,ref_loc_sup?,ref_time_sup?,ac +quisition_sup?,rt_integr_sup?)> +<!ELEMENT almanac_sup EMPTY> +<!ELEMENT UTC_model_sup EMPTY> +<!ELEMENT ionospheric_sup EMPTY> +<!ELEMENT nav_model_sup EMPTY> +<!ELEMENT DGPS_sup EMPTY> +<!ELEMENT ref_loc_sup EMPTY> +<!ELEMENT ref_time_sup EMPTY> +<!ELEMENT acquisition_sup EMPTY> +<!ELEMENT rt_integr_sup EMPTY> +<!ELEMENT GNSS_aid (ionospheric_sup?,ref_loc_sup?,ref_time_sup?,earth_orient_sup?,GNSS_aid_for_on +e_gnss*)> +<!ELEMENT earth_orient_sup EMPTY> +<!ELEMENT GNSS_aid_for_one_gnss +(orbit_sup*,clock_sup*,acquisition_sup?,rt_integr_sup?,GNSS_auxiliary_info_sup?,GNSS_databitassista +nce_sup?,GNSS_almanac_sup?,GNSS_UTC_model_sup?,BDS_grid_model_sup?)> +<!ATTLIST GNSS_aid_for_one_gnss +gnss_id (SBAS|MGPS|QZSS|Glonass|GPS|BDS) #IMPLIED +sbas_id (WASS|EGNOS|MSAS|GAGAN) #IMPLIED> +<!ELEMENT orbit_sup EMPTY> +<!ATTLIST orbit_sup model (2|3|4|5|6) #REQUIRED> +<!-- 2=GPS NAV, 3=GPS CNAV, 4=Glonass, 5=SBAS, 6=BDS --> +<!ELEMENT clock_sup EMPTY> +<!ATTLIST clock_sup model (2|3|4|5|6) #REQUIRED> +<!ELEMENT GNSS_auxiliary_info_sup EMPTY> +<!ELEMENT GNSS_databitassistance_sup EMPTY> +<!ELEMENT GNSS_almanac_sup (almanac_model)> +<!ELEMENT almanac_model (#PCDATA)> <!-- Integer corresponds to bit string 1-8 where bit +at position if set, means particular almanac model is supported -bit6 set means BDS almanac model is +supported. --> +<!ELEMENT GNSS_UTC_model_sup (utc_model)> +<!ELEMENT utc_model (#PCDATA)> <!-- Integer corresponds to bit string 1-8 where bit at +position if set, means particular UTC model is supported -bit4 set means BDS UTC model is supported +--> +<!ELEMENT BDS_grid_model_sup EMPTY> +<!ELEMENT OTDOA_capability (otdoa_mode,supported_band_list_EUTRA,interFreqRSTDmeasurement-r10?)> +<!ELEMENT otdoa_mode #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at +position if set, means particular OTDOA mode is supported +bit0 -ue-assisted supported --> +<!ELEMENT supported_band_list_EUTRA (band_EUTRA+)> +<!ELEMENT band_EUTRA (#PCDATA)> <!-- 1..64 --> +<!ELEMENT interFreqRSTDmeasurement-r10 EMPTY> +<!ELEMENT ECID_capability (ECID_measSupported)> +<!ELEMENT ECID_measSupported (#PCDATA)> <!-- Integer corresponds to bit string 1-8 where bit +at position if set, means particular ECID mode is supported bit0-rsrp Supported,bit1-rsrq +Supported,bit2-ueRXTx Supported --> +<!ELEMENT Bluetooth_capability (bluetooth_modes,bluetooth_meas_sup)> +<!ELEMENT bluetooth_modes #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at +position if set, means particular bluetooth mode is supported bit0-standalone, bit1-ue-assisted +supported --> +<!ELEMENT bluetooth_meas_sup #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at +position if set, means particular bluetooth measurement is supported bit0-rssi --> +<!ELEMENT Sensor_capability (sensor_modes,sensor_databitassistance_sup)> +<!ELEMENT sensor_modes #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at +position if set, means particular Sensor mode is supported bit0-standalone, bit1-ue-assisted bit2- +ue-based supported --> +<!ELEMENT sensor_databitassistance_sup EMPTY> +<!ELEMENT TBS_capability (tbs_modes,tbs_databitassistance_sup)> +<!ELEMENT tbs_modes #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at position +if set, means particular TBS mode is supported bit0-standalone, bit1-ue-assisted bit2-ue-based +supported --> +<!ELEMENT tbs_databitassistance_sup (mbs_acq,mbs_almanac)> +<!ELEMENT mbs_acq #PCDATA> <!-- boolean --> +<!ELEMENT mbs_almanac #PCDATA> <!-- boolean --> +<!ELEMENT WLAN_capability (wlan_modes,wlan_meas_sup)> +<!ELEMENT wlan_modes #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at position +if set, means particular WLAN mode is supported bit0-standalone, bit1-ue-assisted --> +<!ELEMENT wlan_meas_sup #PCDATA> <!-- Integer corresponds to bit string 1-8 where bit at +position if set, means particular WLAN measurement is supported bit0-rssi, bit1-rtt --> + +``` + +NOTE 3b: For elements 'OTDOA\_capability' and 'ECID\_capability', refer to 3GPP TS 36.355 [115] (clause 6.5.1.7) and (clause 6.5.3.4) respectively. Additionally, for elements 'Bluetooth\_capability', 'Sensor\_capability', 'TBS\_capability' and 'WLAN\_capability', refer to 3GPP TS 36.355 [115]. + +**Table 8.55-5: XML DTD for <assist\_data>** + +``` + +<!ELEMENT assist_data +(GPS_assist?, GNSS_assist?, msr_assist_data?, system_info_assist_data?, more_assist_data?, ext_container? +, rel98_assist_data_ext?, rel5_assist_data_ext?, rel7_assist_data_ext?, OTDOA_assist_data?, GNSS_loc_serv +er_err?, OTDOA_loc_server_err?, Sensor_assist_data?, TBS_assist_data?, Sensor_loc_server_err?, TBS_loc_se +rver_err?)> + <!ELEMENT GPS_assist +(status_health?, BTS_clock_drift?, ref_time*, location_parameters?, DGPS_corrections?, nav_model_elem*, io +nospheric_model?, UTC_model?, almanac?, acqu_assist*, GPS_rt_integrity?)> + <!ELEMENT status_health (#PCDATA)> + <!ELEMENT BTS_clock_drift (#PCDATA)> + <!ELEMENT ref_time (GPS_time), (GSM_time|WCDMA_time|LTE_time)?, TimeUnc?, GPS_TOW_assist*)> + <!ELEMENT GPS_time (GPS_TOW_msec, GPS_week)> + <!ELEMENT GPS_TOW_msec (#PCDATA)> + <!ELEMENT GPS_week (#PCDATA)> + <!ELEMENT GPS_TOW_assist (sat_id, tlm_word, anti_sp, alert, tlm_res)> + <!ELEMENT sat_id (#PCDATA)> + <!ELEMENT tlm_word (#PCDATA)> + <!ELEMENT anti_sp (#PCDATA)> + <!ELEMENT alert (#PCDATA)> + <!ELEMENT tlm_res (#PCDATA)> + <!ELEMENT DGPS_corrections (sat_id, iode, UDRE, PRC, RRC, delta_PRC2?, delta_RRC2?)> + <!ELEMENT iode (#PCDATA)> + <!ELEMENT UDRE (#PCDATA)> + <!ELEMENT PRC (#PCDATA)> + <!ELEMENT RRC (#PCDATA)> + <!ELEMENT delta_PRC2 (#PCDATA)> + <!ELEMENT delta_RRC2 (#PCDATA)> + <!ELEMENT nav_model_elem (sat_id, sat_status, ephem_and_clock?)> + <!ELEMENT sat_status EMPTY> + <!ATTLIST sat_status literal (NS_NN-U|ES_NN-U|NS_NN|ES_SN|REVD) #REQUIRED> + <!ELEMENT ephem_and_clock +(l2_code, ura, sv_health, iodc, l2p_flag, esr1, esr2, esr3, esr4, tgd, toc, af2, af1, af0, crs, delta_n, m0, cuc, ecc, +cus, power_half, toe, fit_flag, aoda, cic, omega0, cis, i0, crc, omega, omega_dot, idot, derived?)> + <!ELEMENT l2_code (#PCDATA)> + <!ELEMENT ura (#PCDATA)> + <!ELEMENT sv_health (#PCDATA)> + <!ELEMENT iodc (#PCDATA)> + <!ELEMENT l2p_flag (#PCDATA)> + <!ELEMENT esr1 (#PCDATA)> + <!ELEMENT esr2 (#PCDATA)> + <!ELEMENT esr3 (#PCDATA)> + <!ELEMENT esr4 (#PCDATA)> + <!ELEMENT tgd (#PCDATA)> + <!ELEMENT toc (#PCDATA)> + <!ELEMENT af2 (#PCDATA)> + <!ELEMENT af1 (#PCDATA)> + <!ELEMENT af0 (#PCDATA)> + <!ELEMENT crs (#PCDATA)> + <!ELEMENT delta_n (#PCDATA)> + <!ELEMENT m0 (#PCDATA)> + <!ELEMENT cuc (#PCDATA)> + <!ELEMENT ecc (#PCDATA)> + <!ELEMENT cus (#PCDATA)> + <!ELEMENT power_half (#PCDATA)> + <!ELEMENT toe (#PCDATA)> + <!ELEMENT fit_flag (#PCDATA)> + <!ELEMENT aoda (#PCDATA)> + <!ELEMENT cic (#PCDATA)> + <!ELEMENT omega0 (#PCDATA)> + <!ELEMENT cis (#PCDATA)> + <!ELEMENT i0 (#PCDATA)> + <!ELEMENT crc (#PCDATA)> + <!ELEMENT omega (#PCDATA)> + <!ELEMENT omega_dot (#PCDATA)> + <!ELEMENT idot (#PCDATA)> + <!ELEMENT derived EMPTY> <!-- data derived locally, e.g from EE --> + <!ELEMENT ionospheric_model (alfa0, alfa1, alfa2, alfa3, beta0, beta1, beta2, beta3)> + <!ELEMENT alfa0 (#PCDATA)> + <!ELEMENT alfa1 (#PCDATA)> + +``` + +``` + + <!ELEMENT alfa2 (#PCDATA)> + <!ELEMENT alfa3 (#PCDATA)> + <!ELEMENT beta0 (#PCDATA)> + <!ELEMENT beta1 (#PCDATA)> + <!ELEMENT beta2 (#PCDATA)> + <!ELEMENT beta3 (#PCDATA)> + <!ELEMENT UTC_model (a1,a0,tot,wnt,dtls,wnlsf,dn,dtlsf)> + <!ELEMENT a1 (#PCDATA)> + <!ELEMENT a0 (#PCDATA)> + <!ELEMENT tot (#PCDATA)> + <!ELEMENT wnt (#PCDATA)> + <!ELEMENT dtls (#PCDATA)> + <!ELEMENT wnlsf (#PCDATA)> + <!ELEMENT dn (#PCDATA)> + <!ELEMENT dtlsf (#PCDATA)> +<!ELEMENT almanac (wna,alm_elem*)> + <!ELEMENT wna (#PCDATA)> + <!ELEMENT alm_elem +(data_id?,sat_id,alm_ecc,alm_toa,alm_ksii,alm_omega_dot,alm_sv_health,alm_power_half,alm_omega0,alm_ +omega,alm_m0,alm_af0,alm_af1)> + <!ELEMENT data_id (#PCDATA)> + <!ELEMENT alm_ecc (#PCDATA)> + <!ELEMENT alm_toa (#PCDATA)> + <!ELEMENT alm_ksii (#PCDATA)> + <!ELEMENT alm_omega_dot (#PCDATA)> + <!ELEMENT alm_sv_health (#PCDATA)> + <!ELEMENT alm_power_half (#PCDATA)> + <!ELEMENT alm_omega0 (#PCDATA)> + <!ELEMENT alm_omega (#PCDATA)> + <!ELEMENT alm_m0 (#PCDATA)> + <!ELEMENT alm_af0 (#PCDATA)> + <!ELEMENT alm_af1 (#PCDATA)> +<!ELEMENT GPS_rt_integrity (bad_satellite_set)> + <!ELEMENT bad_satellite_set (sat_id+)> <!-- 1..16 --> +<!ELEMENT msr_assist_data EMPTY> +<!ELEMENT system_info_assist_data EMPTY> +<!ELEMENT more_assist_data EMPTY> +<!ELEMENT ext_container EMPTY> +<!ELEMENT rel98_assist_data_ext EMPTY> +<!ELEMENT rel5_assist_data_ext EMPTY> +<!ELEMENT rel7_assist_data_ext EMPTY> +<!ELEMENT OTDOA_assist_data (OTDOA_ref_cell_info,OTDOA_neighbour_cell_info_list)> + <!ELEMENT OTDOA_ref_cell_info +(phys_cell_id,cell_global_id,earfcn_ref?,antenna_port_conf?,cp_length,prs_info?)> + <!ELEMENT phys_cell_id (#PCDATA)> <!-- 0..503 --> + <!ELEMENT cell_global_id (plmn_identity,cell_identity)> + <!ELEMENT plmn_identity (mcc,mnc)> + <!ELEMENT mcc (#PCDATA)> + <!ELEMENT mnc (#PCDATA)> + <!ELEMENT cell_identity #PCDATA> <!-- 32-bit extended UTRAN cell ID; in case the cell +ID is shorter, the most significant bits are set to 0. --> + <!ELEMENT earfcn_ref (#PCDATA)> <!-- 0..65535 --> + <!ELEMENT antenna_port_conf EMPTY> + <!ATTLIST antenna_port_conf ports(ports1-or-2|ports4) "ports1-or-2"> + <!ELEMENT cp_length EMPTY> + <!ATTLIST cp_length literal(normal|extended) #REQUIRED> + <!ELEMENT prs_info (prs_bandwidth,prs_conf_index,num_dl_frames,prs_muting_info_r9?)> + <!ELEMENT prs_bandwidth EMPTY> + <!ATTLIST prs_bandwidth literal(n6|n15|n25|n50|n75|n100)> + <!ELEMENT prs_conf_index (#PCDATA)> <!-- 0..4095 --> + <!ELEMENT num_dl_frames EMPTY> + <!ATTLIST num_dl_frames literal(sf-1|sf-2|sf-4|sf-6) #REQUIRED> + <!ELEMENT prs_muting_info_r9 muting_info> + <!ATTLIST prs_muting_info_r9 literal(po2-r9|po4-r9|po8-r9|po16-r9) #REQUIRED> + <!ELEMENT muting_info (#PCDATA)> +<!ELEMENT OTDOA_neighbour_cell_info_list (OTDOA_neighbour_freq_info)+> + <!ELEMENT OTDOA_neighbour_freq_info (OTDOA_neighbour_cell_info_element)+> + <!ELEMENT OTDOA_neighbour_cell_info_element +(phys_cell_id,cell_global_id?,earfcn?,cp_length?,prs_info?,antenna_port_conf?,slot_number_offset?,pr +s_subframe_offset?,expected_RSTD,expected_RSTD_uncertainty)> + <!ELEMENT phys_cell_id (#PCDATA)> <!-- 0..503 --> + <!ELEMENT cell_global_id (#PCDATA)> + <!ELEMENT earfcn (#PCDATA)> <!-- 0..65535 --> + <!ELEMENT cp_length EMPTY> + <!ATTLIST cp_length literal(normal|extended) #REQUIRED> + <!ELEMENT prs_info (prs_bandwidth,prs_conf_index,num_dl_frames,prs_muting_info_r9?)> + <!ELEMENT prs_bandwidth EMPTY> + <!ATTLIST prs_bandwidth literal(n6|n15|n25|n50|n75|n100)> + +``` + +``` + + <!ELEMENT prs_conf_index (#PCDATA)> <!-- 0..4095 --> + <!ELEMENT num_dl_frames EMPTY> + <!ATTLIST num_dl_frames literal(sf-1|sf-2|sf-4|sf-6) #REQUIRED> + <!ELEMENT prs_muting_info_r9 muting_info> + <!ATTLIST prs_muting_info_r9 literal(po2-r9|po4-r9|po8-r9|po16-r9) #REQUIRED> + <!ELEMENT muting_info (#PCDATA)> + <!ELEMENT antenna_port_conf EMPTY> + <!ATTLIST antenna_port_conf ports(ports1-or-2|ports4) "ports1-or-2"> + <!ELEMENT slot_number_offset (#PCDATA)> <!-- 0..19 --> + <!ELEMENT prs_subframe_offset (#PCDATA)> <!-- 0..1279 --> + <!ELEMENT expected_RSTD (#PCDATA)> <!-- 0..16383 --> + <!ELEMENT expected_RSTD_uncertainty (#PCDATA)> <!-- 0..1023 --> + <!ELEMENT GNSS_loc_server_err EMPTY> + <!ATTLIST GNSS_loc_server_err literal(undefined_error| + undelivered_assistance_data_not_supported| + undelivered_assistance_data_supported_but_currently_not_available| + undelivered_assistance_data_is_partly_not_supported_and_partly_not_available) #REQUIRED> + <!ELEMENT OTDOA_loc_server_err EMPTY> + <!ATTLIST OTDOA_loc_server_err literal(undefined_error|assistance_data_not_supported| + assistance_data_supported_but_currently_not_available) #REQUIRED> + <!ELEMENT Sensor_assist_data (ref_pressure?,ref_position?,ref_temperature?)> + <!ELEMENT ref_pressure (#PCDATA)> <!-- -20000..10000 --> + <!ELEMENT ref_position (ellipsoid point_alt_uncertellipse)> + <!ELEMENT ref_temperature (#PCDATA)> <!-- -64..63 --> + <!ELEMENT TBS_assist_data (almanac?,acqu_assist?)> + <!ELEMENT almanac (trans_id,trans_lat,trans_long,trans_alt,time_correct?)> + <!ELEMENT trans_id (#PCDATA)> <!-- 0..32767 --> + <!ELEMENT trans_lat (#PCDATA)> + <!ELEMENT trans_long (#PCDATA)> + <!ELEMENT trans_alt (#PCDATA)> + <!ELEMENT time_correct (#PCDATA)> <!-- 0..25 --> + <!ELEMENT acqu_assist (trans_id?,mbs_config?,pn_code?,freq?)> + <!ELEMENT trans_id (#PCDATA)> <!-- 0..32767 --> + <!ELEMENT mbs_config EMPTY> + <!ATTLIST mbs_config literal(tb1|tb2|tb3|tb4)> + <!ELEMENT pn_code (#PCDATA)> <!-- 1..128 --> + <!ELEMENT freq (#PCDATA)> <!-- 919750000..927250000 --> + <!ELEMENT Sensor_loc_server_err EMPTY> + <!ATTLIST Sensor_loc_server_err literal(undefined_error|assistance_data_not_supported| + assistance_data_supported_but_currently_not_available) #REQUIRED> + <!ELEMENT TBS_loc_server_err EMPTY> + <!ATTLIST TBS_loc_server_err literal(undefined_error|assistance_data_not_supported| + assistance_data_supported_but_currently_not_available) #REQUIRED> + +``` + +NOTE 4: For the elements and the value ranges of assistance data information delivered from the network, refer to 3GPP TS 25.331 [74] (clause 10.3.7.90), 3GPP TS 36.355 [115] (clause 6.5.1) and 3GPP TS 44.031 [79] (clause A.4.2.4). The value ranges of the relevant parameters are described in the ASN.1 syntax. + +NOTE 5: For the element 'location\_parameters', see table 8.50-2. In the context of this XML, the 'location\_parameters' will describe a reference location. + +NOTE 6: The elements ext\_container, rel98\_assist\_data\_ext, rel5\_assist\_data\_ext and rel7\_assist\_data\_ext are deprecated. + +**Table 8.55-6: XML DTD for <GSM\_time>, <WCDMA\_time>, <LTE\_time>, <TimeUnc>** + +``` + +<!ELEMENT GSM_time (frame_number,frame_number_msb,time_slot_number,bit_number,BCCH_carrier?,BSIC?)> + <!ELEMENT frame_number (#PCDATA)> + <!ELEMENT frame_number_msb (#PCDATA)> + <!ELEMENT time_slot_number (#PCDATA)> + <!ELEMENT bit_number (#PCDATA)> + <!ELEMENT BCCH_carrier (#PCDATA)> + <!ELEMENT BSIC (#PCDATA)> + +<!ELEMENT WCDMA_time (cell_timing_chips,(FDD_CPICH|TDD_cell_id|SFN),SFN_TOW_Unc?)> + <!ELEMENT cell_timing_chips (#PCDATA)> + <!ELEMENT FDD_CPICH (#PCDATA)> + <!ELEMENT TDD_cell_id (#PCDATA)> + <!ELEMENT SFN (#PCDATA)> + <!ELEMENT SFN_TOW_Unc (#PCDATA)> <!-- Integer 0..1 0- Uncertainty less than 10 ms, 1- + Uncertainty more than 10 ms --> + +``` + +``` + +<!ELEMENT LTE_time (secFromFrameStructStart, fractSecFromFrameStructStart, +frameDrift?, physCellId, cellGlobalIdEUTRA?, earfcn, TimeUnc)> + <!ELEMENT secFromFrameStructStart (#PCDATA)> <!-- 0..12533 --> + <!ELEMENT fractSecFromFrameStructStart (#PCDATA)> <!-- 0..3999999 --> + <!ELEMENT frameDrift (#PCDATA)> <!-- -64..63 --> + <!ELEMENT physCellId (#PCDATA)> + <!ELEMENT cellGlobalIdEUTRA (#PCDATA)> + <!ELEMENT earfcn (#PCDATA)> + +<!ELEMENT TimeUnc EMPTY> + <!ATTLIST TimeUnc + Value CDATA "127" + units (s|ms|us|rrlp_k|rrc_k|lpp_k) "rrc_k"> + +``` + +**Table 8.55-7: XML DTD for <acqu\_assist>** + +``` + +<!ELEMENT acqu_assist (tow_msec, sat_info*, confidence_r10?)> + <!ELEMENT tow_msec (#PCDATA)> + <!ELEMENT sat_info + (sat_id, dopl0, dopl_extra?, code_ph, code_ph_int, GPS_bitno, srch_w, az_el?, doppler_uncertainty_ext_r10?)> + <!ELEMENT dopl0 (#PCDATA)> + <!ATTLIST dopl0 units (rrlp|rrc|lpp|Hz|mps) "rrlp"> + <!-- rrlp gps is 2.5 Hz --> + <!-- rrc gps is 2.5 Hz --> + <!-- lpp gnss is 0.5 m/s --> + <!ELEMENT dopl_extra (dopl1, dopl1_uncert)> + <!ELEMENT dopl1 (#PCDATA)> + <!ATTLIST dopl1 units (rrlp|rrc|lpp) "rrlp"> + <!-- rrlp is 1/42 Hz/s --> + <!-- rrc is 0.023 Hz/s --> + <!-- lpp is 1/210 m/s/s --> + <!ELEMENT dopl1_uncert EMPTY> + <!ATTLIST dopl1_uncert literal (hz12-5|hz25|hz50|hz100|hz200) #REQUIRED> + <!ELEMENT code_ph (#PCDATA)> + <!ATTLIST code_ph units (chips|ms) "chips"> + <!-- chips used for GPS in RRLP and RRC, ms used for LPP --> + <!ELEMENT code_ph_int (#PCDATA)> + <!ELEMENT GPS_bitno (#PCDATA)> + <!ELEMENT srch_w (#PCDATA)> + <!ELEMENT az_el (az, elev)> + <!ELEMENT az (#PCDATA)> + <!ATTLIST az_el units (rrlp|lpp|degree) "rrlp"> + <!-- rrlp and rrc have units of 11.25 degree --> + <!-- lpp has units of 0.703125 degrees --> + <!ELEMENT elev (#PCDATA)> + <!ELEMENT doppler_uncertainty_ext_r10> + <!ATTLIST doppler_uncertainty_ext_r10 (d60|d80|d100|d120|no_information) #IMPLIED> + <!ELEMENT confidence_r10 (#PCDATA)> <!-- 0..100 --> + +``` + +NOTE 7: Units of mps, lpp and ms are used with GNSS procedures. + +**Table 8.55-8: XML DTD for <pos\_meas>** + +``` + +<!ELEMENT pos_meas (meas_abort|RRLP_meas|RRC_meas)> + <!ELEMENT meas_abort EMPTY> + <!ELEMENT RRLP_meas (RRLP_pos_instruct)> + <!ELEMENT RRLP_pos_instruct (RRLP_method_type, RRLP_method, resp_time_seconds, mult_sets)> + <!ELEMENT RRLP_method_type (ms_assisted|ms_assisted_no_accuracy|ms_based|ms_based_pref| + ms_assisted_pref)> + <!ELEMENT ms_assisted (method_accuracy)> + <!ELEMENT method_accuracy (#PCDATA)> + <!ELEMENT ms_assisted_no_accuracy EMPTY> + <!ELEMENT ms_based (method_accuracy)> + <!ELEMENT ms_based_pref (method_accuracy)> + <!ELEMENT ms_assisted_pref (method_accuracy)> + <!ELEMENT RRLP_method EMPTY> + <!ATTLIST RRLP_method literal (gps) #REQUIRED> + <!ELEMENT resp_time_seconds (#PCDATA)> + <!ELEMENT mult_sets EMPTY> + <!ATTLIST mult_sets literal (multiple|one) #REQUIRED> + <!ELEMENT RRC_meas (rep_quant, rep_crit)> + <!ELEMENT rep_quant (RRC_method_type, RRC_method, hor_acc?, vert_acc?)> + <!ATTLIST rep_quant + +``` + +``` + + gps_timing_of_cell_wanted (true|false) "false" + addl_assist_data_req (true|false) #REQUIRED> + <!ELEMENT RRC_method_type EMPTY> + <!ATTLIST RRC_method_type literal (ue_assisted|ue_based|ue_based_pref|ue_assisted_pref) +#REQUIRED> + <!ELEMENT RRC_method EMPTY> + <!ATTLIST RRC_method literal (otdoa|gps|otdoaOrGPS|cellID) #REQUIRED> + <!ELEMENT hor_acc (#PCDATA)> + <!ELEMENT vert_acc (#PCDATA)> + <!ELEMENT rep_crit (no_rep|event_rep_crit|period_rep_crit)> + <!ELEMENT no_rep EMPTY> + <!ELEMENT event_rep_crit (event_par*)> + <!ELEMENT event_par (rep_amount,meas_interval,event_specific_info?)> + <!ATTLIST event_par report_first_fix (true|false) #REQUIRED> + <!ELEMENT rep_amount EMPTY> + <!ATTLIST rep_amount literal (ra1|ra2|ra4|ra8|ra16|ra32|ra64|ra-Infinity) +#REQUIRED> + <!ELEMENT meas_interval EMPTY> + <!ATTLIST meas_interval literal (e5|e15|e60|e300|e900|e1800|e3600|e7200) +#REQUIRED> + <!ELEMENT event_specific_info (tr_pos_chg|tr_SFN_SFN_chg|tr_SFN_GPS_TOW)> + <!ELEMENT tr_pos_chg EMPTY> + <!ATTLIST tr_pos_chg literal (pc10|pc20|pc30|pc40|pc50|pc100|pc200|pc300|pc500| +pc1000|pc2000|pc5000|pc10000|pc20000|pc50000|pc100000) #REQUIRED> + <!ELEMENT tr_SFN_SFN_chg EMPTY> + <!ATTLIST tr_SFN_SFN_chg literal (c0-25|c0-5|c1|c2|c3|c4|c5|c10|c20|c50|c100| +c200|c500|c1000|c2000|c5000) #REQUIRED> + <!ELEMENT tr_SFN_GPS_TOW EMPTY> + <!ATTLIST tr_SFN_GPS_TOW literal (ms1|ms2|ms3|ms5|ms10|ms20|ms50|ms100) +#REQUIRED> + <!ELEMENT period_rep_crit EMPTY> + <!ATTLIST period_rep_crit rep_amount (ra1|ra2|ra4|ra8|ra16|ra32|ra64|ra-Infinity) "ra- +Infinity"> + <!ATTLIST period_rep_crit rep_interval_long (ri10|ri10-25|ri10-5|ri11|ri12|ri13|ri14| +ri16|ri18|ri112|ri116|ri120|ri124|ri128|ri132|ri164) #REQUIRED> + +``` + +NOTE 8: For the elements and the value ranges of position measurements data, refer to 3GPP TS 25.331 [74] (clause 10.3.7.100) and 3GPP TS 44.031 [79] (clause A.2). The value ranges of the relevant parameters are described in the ASN.1 syntax. + +**Table 8.55-9: XML DTD for <pos\_meas\_req>** + +``` + +<!-- Alternative to pos_meas, supports RRLP, RRC and LPP --> +<!ELEMENT pos_meas_req (abort|(req_info,qos,loc_coordinate_types?))> +<!ATTLIST pos_meas_req aid_req_allowed (yes|no) #IMPLIED> <!-- Present for RRC and LPP +procedures --> +<!ELEMENT abort EMPTY> +<!ELEMENT req_info (GNSS_allowed_methods?)> +<!ATTLIST req_info loc_info_type (loc_req|meas_req|loc_pref|MSB_req|MSA_req|MSB_pref|MSA_pref) +"loc_req" +velocity_req (true|false) "false" +time_req (true|false) "false" +multiple_sets (yes|no) "no" +additional_info (yes|no) "no"> <!-- lpp only --> <!-- MSB synonymous with loc_req --> +<!ELEMENT GNSS_allowed_methods +(gps_method?,sbas_method?,qzss_method?,glonass_method?,BDS_method?)> +<!ELEMENT gps_method EMPTY> +<!ELEMENT sbas_method EMPTY> +<!ELEMENT qzss_method EMPTY> +<!ELEMENT glonass_method EMPTY> +<!ELEMENT BDS_method EMPTY> +<!ELEMENT qos (response_time?,(reporting_interval,amount)?,hacc?,vacc?)> +<!-- The presence of reporting_interval implies a periodic procedure --> +<!-- The absence of reporting_interval implies a one-shot procedure --> +<!ELEMENT response_time (time,responseTimeEarlyFix-r12?)> +<!ELEMENT time (#PCDATA)> <!-- 1..128 --> +<!ELEMENT responseTimeEarlyFix-r12 (#PCDATA)> <!-- 1..128,value of responseTimeEarlyFix-r12 +should be less than time --> +<!ELEMENT reporting_interval EMPTY> +<!ATTLIST reporting_interval +ri_exp (ri11|ri12|ri13|ri14|ri16|ri18|ri112|ri116|ri120|ri124|ri128|ri132|ri164) "ri120" > +<!ELEMENT amount EMPTY> +<!ATTLIST amount amount (ra1|ra2|ra4|ra8|ra16|ra32|ra64|ra-Infinity) "ra-Infinity"> +<!ELEMENT hacc EMPTY> +<!ATTLIST hacc + +``` + +``` + + accuracy_k CDATA #IMPLIED + confidence CDATA #IMPLIED + <!ELEMENT vacc EMPTY> + <!ATTLIST vacc + accuracy_k CDATA #IMPLIED + confidence CDATA #IMPLIED> + <ELEMENT loc_coordinate_types(#PCDATA)> + <!-- Integer corresponds to bit string 1-8 where bit at position if set, means location co- +ordinate type is supported bit0=ellipsoidPoint supported,bit1=ellipsoidPointWithUncertaintyCircle +supported,bit2=ellipsoidPointWithUncertaintyEllipse supported,bit3=polygon +supported,bit4=ellipsoidPointWithAltitude +supported,bit5=ellipsoidPointWithAltitudeAndUncertaintyEllipsoid supported,bit6=ellipsoidArc +supported --> + +``` + +**Table 8.55-10: XML DTD for <GPS\_meas>** + +``` + +<!ELEMENT GPS_meas (ref_time_only,meas_params*)> +<!ELEMENT ref_time_only (tow msec)> +<!ELEMENT meas_params (sat_id,carr2_noise,dopl,whole_chips,fract_chips,multi_path,psr_rms_err)> +<!ELEMENT carr2_noise (#PCDATA)> +<!ELEMENT dopl (#PCDATA)> +<!ELEMENT whole_chips (#PCDATA)> +<!ELEMENT fract_chips (#PCDATA)> +<!ELEMENT multi_path EMPTY> +<!ATTLIST multi_path literal (not_measured|low|medium|high) #REQUIRED> +<!ELEMENT psr_rms_err (#PCDATA)> + +``` + +NOTE 9: For the elements and the value ranges of GPS measurement data, refer to 3GPP TS 25.331 [74] (clause 10.3.7.93) and 3GPP TS 44.031 [79] (clause A.3.2.5). The value ranges of the relevant parameters are described in the ASN.1 syntax. + +**Table 8.55-11: XML DTD for <GNSS\_meas>** + +``` + +<!ELEMENT GNSS_meas ( GNSS_meas_for_one_gnss+,TOD_ms|ref_time_only,earlyFixReport-r12?)> +<!ELEMENT GNSS_meas_for_one_gnss (GNSS_sgn_meas_element+)> +<!ATTLIST GNSS_meas_for_one_gnss gnss_id GPS|SBAS|QZSS|Galileo|Glonass|BDS) "GPS"> +<!ELEMENT GNSS_sgn_meas_element (code_phase_ambiguity?, GNSS_sat_meas_element+)> +<!ATTLIST GNSS_sgn_meas_element measured_signal (GPS_L1|GPS_L1C|GPS_L2C|GPS_L5|SBAS_L1|GLO_G1| +GLO_G2|GLO_G3|BDS_B1I) "GPS_L1"> +<!ELEMENT code_phase_ambiguity (#PCDATA)> <!-- 0..127 --> +<!ELEMENT GNSS_sat_meas_element +(sat_id,carr2_noise,doppler_mps?,code_phase_ms?,integer_code_phase?,multi_path,psr_rms_err,adr?,whol +e_chips?,fract_chips?,carrier_quality_ind?)> +<!ELEMENT doppler_mps (#PCDATA)> <!-- m/s Range -32768..32767 --> +<!ELEMENT code_phase_ms (#PCDATA)> <!-- ms Range 0..2097151 --> +<!ELEMENT integer_code_phase (#PCDATA)> +<!ELEMENT adr (#PCDATA)> +<!ELEMENT carrier_quality_ind (#PCDATA)> <!-- 0..3 --> +<!ELEMENT TOD_ms (gnss_TOD_msec,gnss_TOD_frac?,gnss_TOD_unc?) > +<!ATTLIST TOD_ms gnss_time_id (GPS|Glonass|QZSS|BDS) "GPS"> +<!ELEMENT earlyFixReport-r12 EMPTY> + +``` + +NOTE 10: 'GNSS\_meas' is used for reporting measurements results for GNSS procedures i.e. procedures where: 'GNSS\_allowed\_methods', 'GNSS\_assist' was received or where 'acqu\_assist' uses units of ms. + +NOTE 10a: 'ref\_time\_only' shall be provided by the TE for gnss\_id="GPS", refer to 3GPP TS 25.331 [74] (clause 10.3.7.93) and 3GPP TS 44.031 [79] (clause A.3). Usage of the element 'GNSS\_meas' in 'GNSS\_provided\_location\_information' can be omitted as 'GNSS\_meas' is already present in 'pos'. + +NOTE 10b: 'whole\_chips' and 'fract\_chips' to be provided for gnss\_id="GPS" + +**Table 8.55-12: XML DTD for <GPS\_assist\_req>** + +``` + +<!ELEMENT GPS_assist_req (nav_addl_data?)> +<!ATTLIST GPS_assist_req + +``` + +``` + +alm_req (true|false) "false" +UTC_model_req (true|false) "false" +ion_req (true|false) "false" +nav_model_req (true|false) "false" +DGPS_corr_req (true|false) "false" +ref_loc_req (true|false) "false" +ref_time_req (true|false) "false" +aqu_assist_req (true|false) "false" +rt_integer_req (true|false) "false"> +<!ELEMENT nav_addl_data (GPS_week,GPS_toe,ttoe_limit,addl_req_sat*)> + <!ELEMENT GPS_toe (#PCDATA)> + <!ELEMENT ttoe_limit (#PCDATA)> + <!ELEMENT addl_req_sat (sat_id,iode)> + +``` + +NOTE 11: For requesting assistance data, refer to 3GPP TS 25.331 [74] (clause 10.3.7.88a) and 3GPP TS 49.031 [80] (clause 10.10). + +**Table 8.55-13: XML DTD for <msg>** + +``` + +<!ELEMENT msg EMPTY> +<!ATTLIST msg status (assist_data_delivered|abort_confirm) #REQUIRED> + +``` + +NOTE 12: 'assist\_data\_delivered' can be used as an indication of completion of provision of assistance data. + +NOTE 12a: 'abort\_confirm' can be used as an indication for positioning abort confirmation. + +**Table 8.55-14: XML DTD for <pos\_err>** + +``` + +<!ELEMENT pos_err (err_reason,GPS_assist_req?,ECID_meas_error_cause?,GNSS_assist_req?)> + <!ELEMENT err_reason_EMPTY> + <!ATTLIST err_reason_literal (undefined_error|not_enough_gps_satellites| +gps_assist_data_missing|gnss_assist_data_missing|not_enough_gnss_satellites|OTDOA_undefined| +OTDOA_assistance_data_missing|OTDOA_unable_to_measure_referencecell| +OTDOA_unable_to_measure_any_neighbourcell|OTDOA_attempted_but_unable_to_measure_some_neighbourcells| +ECID_undefined|ECID_requested_measurement_not_available| +ECID_not_all_requested_measurements_possible|Bluetooth_undefined| +Bluetooth_not_all_requested_measurements_possible|Sensor_undefined|TBS_undefined| +TBS_not_enough_MBS_beacons|WLAN_undefined|WLAN_not_all_requested_measurements_possible) #REQUIRED> + <!ELEMENT ECID_meas_error_cause (#PCDATA)> <!-- Integer corresponds to bit string 1-8 where bit +at position represents ECID error cause. Only applicable, when value of err_reason = +"ECID_not_all_requested_measurements_possible" bit0-rsrpMeasurementNotPossible, bit1- +rsrqMeasurementNotPossible, bit2-ueRxBxMeasurementNotPossible --> + +``` + +NOTE 13: For reporting positioning error, refer to 3GPP TS 25.331 [74] (clause 10.3.7.87) and 3GPP TS 44.031 [79] (clause A.3.2.6). + +NOTE 13a: For reporting GNSS related positioning errors, refer to 3GPP TS 36.355 [115] (clause 6.5.2.12) for LPP, 3GPP TS 25.331 [74] (clause 10.3.7.87) for RRC and 3GPP TS 44.031 [79] (clause A.3.2.6) for RRLP. + +NOTE 13b: For reporting OTDOA and ECID errors, refer to 3GPP TS 36.355 [115] (clause 6.5.1.9) for OTDOA specific errors and 3GPP TS 36.355 [115] (clause 6.5.3.6) for ECID specific errors. + +NOTE 13c: For reporting Bluetooth, Sensor, TBS and WLAN errors, refer to 3GPP TS 36.355 [115] for specific errors. + +**Table 8.55-15: XML DTD for <GNSS\_assist>, <GNSS\_assist\_req>** + +``` + +<!ELEMENT GNSS_assist +(GNSS_ref_time?,GNSS_ref_location?,GNSS_ref_measurement_assist?,GNSS_ionospheric_model?,GNSS_earth_or +ient_param?,GNSS_additional_ion_model?,GNSS_time_model,GNSS_nav_model?,GNSS_integrity?,acqu_assist*, +GNSS_dataBitAssistance?,GNSS_almanac?,GNSS_UTC_model?,BDS-GridModel-r12?,GNSS_auxiliary_info?)> + <!ATTLIST GNSS_assist +gnss_id (SBAS|MGPS|QZSS|Glonass|GPS|BDS) #IMPLIED +sbas_id (WASS|EGNOS|MSAS|GAGAN) #IMPLIED> +<!ELEMENT GNSS_ref_time (GNSS_day,GNSS_TOD_s,notification_leap_sec?,GNSS_TOD_frac_ms?,TimeUnc?)> + +``` + +``` + +<!ATTLIST GNSS_ref_time gnss_time_id (GPS|Glonass|QZSS|BDS) #REQUIRED> +<!ELEMENT GNSS_day (#PCDATA)> +<!ELEMENT GNSS_TOD_s (#PCDATA)> <!-- 0..86399 seconds --> +<!ELEMENT GNSS_TOD_frac_ms (#PCDATA)> <!-- 0..999 milli-seconds --> +<!-- TOD Uncertainty presented in TimeUnc --> +<!ELEMENT notification_leap_sec (#PCDATA) > <!-- hex LPP only --> +<!ELEMENT GNSS_ref_location (location_parameters)> +<!ELEMENT GNSS_ref_measurement_assist (acqu_assist)> +<!ELEMENT GNSS_ionospheric_model (gnss_ion_ai0,gnss_ion_ai1,gnss_ion_ai2,gnss_ion_flags?)> +<!ELEMENT gnss_ion_ai0 (#PCDATA)> <!-- range 0..4095 --> +<!ELEMENT gnss_ion_ai1 (#PCDATA)> <!-- range 0..4095 --> +<!ELEMENT gnss_ion_ai2 (#PCDATA)> <!-- range 0..4095 --> +<!ELEMENT gnss_ion_flags EMPTY> +<!ATTLIST gnss_ion_flags + storm_flag1 (0|1) "0" + storm_flag2 (0|1) "0" + storm_flag3 (0|1) "0" + storm_flag4 (0|1) "0" + storm_flag5 (0|1) "0"> +<!ELEMENT GNSS_earth_orient_param + (gnss_eop_teop,gnss_eop_pmX,gnss_eop_pmX_d,gnss_eop_pmY,gnss_eop_pmY_d,gnss_eop_deltaUT1,gnss_eop_de + ltaUT1_d)> +<!ELEMENT gnss_eop_teop (#PCDATA)> <!-- range 0..65535 --> +<!ELEMENT gnss_eop_pmX (#PCDATA)> <!-- range -1048576..1048575 --> +<!ELEMENT gnss_eop_pmX_d (#PCDATA)> <!-- range -16384..16383 --> +<!ELEMENT gnss_eop_pmY (#PCDATA)> <!-- range -1048576..1048575 --> +<!ELEMENT gnss_eop_pmY_d (#PCDATA)> <!-- range -16384..16383 --> +<!ELEMENT gnss_eop_deltaUT1 (#PCDATA)> <!-- range -1073741824..1073741823 --> +<!ELEMENT gnss_eop_deltaUT1_d (#PCDATA)> <!-- range -262144..262143 --> +<!ELEMENT GNSS_additional_ion_model (ionospheric_model)> +<!ATTLIST GNSS_additional_ion_model + ion_model_data_id (00|11|01) "00"> <!-- from rrlp 11=QZSS 00=other 01=BDS --> +<!ELEMENT GNSS_time_model (tme_ref_time,tme_A0,tme_A1?,tme_A2?,tme_week?)> +<!ATTLIST GNSS_time_model gnss_time_id (GPS|Glonass|QZSS|BDS) #REQUIRED> +<!ELEMENT tme_ref_time (#PCDATA)> <!-- sec scale 2**4 --> +<!ELEMENT tme_A0 (#PCDATA)> <!--sec scale 2**35 --> +<!ELEMENT tme_A1 (#PCDATA)> <!-- sec/sec scale 2**51 --> +<!ELEMENT tme_A2 (#PCDATA)> <!-- sec/sec sec scale 2**68 --> +<!ELEMENT tme_week (#PCDATA)> <!-- 0..8191 --> +<!ELEMENT GNSS_nav_model (GNSS_satellite+)> +<!ATTLIST GNSS_nav_model + non_broadcast_ind_flag (0|1) "0"> +<!ELEMENT GNSS_satellite (sat_id,nms_health,nms_iod, + (nms_clock_nav,nms_orbit_nav)| + (nms_clock_cnav,nms_orbit_cnav)| + (nms_clock_glonass,nms_orbit_glonass)| + (nms_clock_sbas,nms_orbit_sbas)| + (nms_clock_bds,nms_orbit_bds))> +<!ELEMENT nms_health (#PCDATA)> <!-- in hexadecimal --> +<!ELEMENT nms_iod (#PCDATA)> <!-- includes iod_msb --> +<!ELEMENT GNSS_integrity (bad_signal*)> +<!ELEMENT bad_signal (sat_id,GNSS_signal?)> +<!ELEMENT GNSS_signal (#PCDATA)> +<!ELEMENT GNSS_databitassistance (gnss-TOD,gnss-TODfrac?,gnss-DataBitsSatList+)> +<!ELEMENT gnss-TOD (#PCDATA)> <!-- 0..3599 --> +<!ELEMENT gnss-TODfrac (#PCDATA)> <!-- 0..99 --> +<!ELEMENT gnss-DataBitsSatList (sat_id,gnss-DataBitsSgnList+)> +<!ATTLIST gnss-DataBitsSatList signal_id (GPS_L1|GPS_L1C|GPS_L2C|GPS_L5|SBAS_L1|GLO_G1|GLO_G2| + GLO_G3|BDS_B1I) "GPS_L1"> +<!ELEMENT gnss-DataBitsSgnList (GNSS_databits)> <> +<!ELEMENT GNSS_databits (#PCDATA)> <!-- 1..1024 --> +<!ELEMENT GNSS_almanac (week_number?,toa,ioda?,completeAlmanacProvided,gnss-AlmanacList+)> +<!ELEMENT week_number (#PCDATA)> <!-- 0..255 --> +<!ELEMENT toa (#PCDATA)> <!-- 0..255 --> +<!ELEMENT ioda (#PCDATA)> <!-- 0..3 --> +<!ELEMENT completeAlmanacProvided (#PCDATA)> +<!ELEMENT gnss-AlmanacList (keplerianBDS-Almanac-r12)> +<!ELEMENT keplerianBDS-Almanac-r12 (sat_id,bdsAlmToa-r12?,bdsAlmSqrtA-r12,bdsAlmE-r12,bdsAlmW- + r12,bdsAlmM0-r12,bdsAlmOmega0-r12,bdsAlmOmegaDot-r12,bdsAlmDeltaI-r12,bdsAlmA0-r12,bdsAlmA1- + r12,bdsSvHealth-r12?)> +<!ELEMENT bdsAlmToa-r12 (#PCDATA)> <!-- 0..256 --> +<!ELEMENT bdsAlmSqrtA-r12 (#PCDATA)> <!-- 0..16777215 --> +<!ELEMENT bdsAlmE-r12 (#PCDATA)> <!-- 0..131071 --> +<!ELEMENT bdsAlmW-r12 (#PCDATA)> <!-- -8388608..8388607 --> +<!ELEMENT bdsAlmM0-r12 (#PCDATA)> <!-- -8388608..8388607 --> +<!ELEMENT bdsAlmOmega0-r12 (#PCDATA)> <!-- -8388608..8388607 --> +<!ELEMENT bdsAlmOmegaDot-r12 (#PCDATA)> <!-- -65536..65535 --> +<!ELEMENT bdsAlmDeltaI-r12 (#PCDATA)> <!-- -32768..32767 --> + +``` + +``` + +<!ELEMENT bdsAlmA0-r12 (#PCDATA)> <!-- -1024..1023 --> +<!ELEMENT bdsAlmA1-r12 (#PCDATA)> <!-- -1024..1023 --> +<!ELEMENT bdsSvHealth-r12(#PCDATA)> <!-- 0..3599 --> + +<!ELEMENT GNSS_UTC_model (utcModel5-r12)> + <!ELEMENT utcModel5-r12 (utcA0-r12,utcA1-r12,utcDeltaTls-r12,utcWNlsf-r12,utcDN-r12,utcDeltaTlsf-r12)> + <!ELEMENT utcA0-r12 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT utcA1-r12 (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT utcDeltaTls-r12 (#PCDATA)> <!-- -128..127 --> + <!ELEMENT utcWNlsf-r12 (#PCDATA)> <!-- 0..255 --> + <!ELEMENT utcDN-r12(#PCDATA)> <!-- 0..255 --> + <!ELEMENT utcDeltaTlsf-r12 (#PCDATA)> <!-- -128..127 --> + +<!ELEMENT BDS-GridModel-r12(bds-Reftime-r12,gridIonList-r12+)> + <!ELEMENT bds-Reftime-r12 (#PCDATA)> <!-- 0..3599 --> + <!ELEMENT gridIonList-r12 (igp-ID-r12,dt-r12,givei-r12)> + <!ELEMENT igp-ID-r12 (#PCDATA)> <!-- 1..320 --> + <!ELEMENT dt-r12 (#PCDATA)> <!-- 0..511 --> + <!ELEMENT givei-r12 (#PCDATA)> <!-- 0..15 --> +<!ELEMENT GNSS_auxiliary_info (GNSS_id_glonass)> + <!ELEMENT GNSS_id_glonass (GNSS_id_glonass_sat_element+)> + <!ELEMENT GNSS_id_glonass_sat_element (sat_id,GNSS_signal_id,channel_number?)> <!-- sat_id 0..63 --> + <!ELEMENT GNSS_signal_id (#PCDATA)> + <!-- Integer corresponds to bit string 1-8 where bit at position if set, means particular signal is addressed; a zero-value at the particular bit position means the signal is not addressed --> + <!ELEMENT channel_number (#PCDATA)> <!-- -7..13 --> + +<!ELEMENT GNSS_assist_req (GNSS_assist_req_per_gnss*)> + <!-- common assist req --> + <!ELEMENT GNSS_ref_time_req EMPTY> + <!ATTLIST GNSS_ref_time_req + time_req_pref (SBAS|MGPS|QZSS|Glonass|GPS) #IMPLIED + tow_req (false|true) "false" + leap_sec_req (false|true) #IMPLIED> + <!ELEMENT GNSS_ref_loc_req EMPTY> + <!ELEMENT GNSS_ion_model_req EMPTY> + <!ELEMENT GNSS_earth_orient_req EMPTY> + + <!-- generic req --> + <!ELEMENT GNSS_assist_req_per_gnss + (GNSS_time_model_req?,GNSS_navigation_model_req?,GNSS_integrity_req?,GNSS_acquisition_req?,GNSS_auxiliary_info_req?,GNSS_databitassistance_req?,GNSS_Almanac_req?,GNSS_UTC_model_req?,BDS_grid_model_req_r12?)> + <!ATTLIST GNSS_assist_req_per_gnss + gnss_id (SBAS|MGPS|QZSS|Glonass|GPS) #REQUIRED + sbas_id (WASS|EGNOS|MSAS|GAGAN) #IMPLIED> + <!ELEMENT GNSS_time_model_req EMPTY> + <!-- For LPP gnss-TO-IDsReq is derived from gnss_id --> + <!ATTLIST GNSS_time_model_req delta_T_req (false|true) #IMPLIED> + <!ELEMENT GNSS_navigation_model_req (stored_nav_list?,requested_nav_list?) > + <!ELEMENT stored_nav_list + (snl_week_or_day,snl_toe,snl_toe_limit,stored_sat_list_element*,requested_nav_list?)> + <!ELEMENT snl_week_or_day (#PCDATA)> + <!ELEMENT snl_toe (#PCDATA)> + <!ELEMENT snl_toe_limit (#PCDATA)> + <!ELEMENT stored_sat_list_element EMPTY> + <!ATTLIST stored_sat_list_element + stored_id CDATA #REQUIRED + stored_iod CDATA #REQUIRED + stored_clock_model (2|3|4|5|6) #IMPLIED + stored_orbit_model (2|3|4|5|6) #IMPLIED> + <!ELEMENT requested_nav_list (requested_nav_list_info*)> + <!ELEMENT requested_nav_list_info EMPTY> + <!ATTLIST requested_nav_list_info + requested_sv CDATA "0000000000000000" + requested_clock_model (2|3|4|5|6) #IMPLIED + requested_orbit_model (2|3|4|5|6) #IMPLIED + requested_add_nav_param (false|true) #IMPLIED> + <!-- requested_sv is a bit string in hexadecimal, needed for LPP --> + <!ELEMENT GNSS_integrity_req EMPTY> + <!ELEMENT GNSS_acquisition_req EMPTY> + <!ATTLIST GNSS_acquisition_req signal (GPS_L1|GPS_L1C|GPS_L2C|GPS_L5|SBAS_L1|GLO_G1|GLO_G2|GLO_G3|BDS_B1I) "GPS_L1"> + <!ELEMENT GNSS_databitassistance_req + (gnss_TOD_req,gnss_TOD_fraq?,databit_interval,databit_reqsat_list+)> + +``` + +``` + +<!ATTLIST GNSS_databitassistance_req signal (GPS_L1|GPS_L1C|GPS_L2C|GPS_L5|SBAS_L1|GLO_G1| +GLO_G2|GLO_G3|BDS_B11) "GPS_L1"> + confidence_support (yes|no) #IMPLIED + doppler_uncertainty_ext_support (yes|no) #IMPLIED> + <!ELEMENT GNSS_auxiliary_info req EMPTY> + <!ELEMENT gnss_TOD_req (#PCDATA)> <!-- 0..3599 --> + <!ELEMENT gnss_TOD_fraq (#PCDATA)> <!-- 0..599 --> + <!ELEMENT databit_interval (#PCDATA)> <!-- 0..15 --> + <!ELEMENT databit_reqsat_list (sat_id)> <!-- sat_id 0..63 --> + <!ELEMENT GNSS_Almanac_req > + <!ATTLIST GNSS_Almanac_req model (7) #IMPLIED> + <!ELEMENT GNSS_UTC_model_req > + <!ATTLIST GNSS_UTC_model_req model (5) #IMPLIED> + <!ELEMENT BDS_grid_model_req_r12 EMPTY> + +``` + +NOTE 14: GNSS\_assist is used for assistance data received via an RRLP ASN.1 GANSSAssistanceSet element (refer to 3GPP TS 44.031 [79]), via an RRC GANSS assistance data element (refer to 3GPP TS 25.331 [74] clause 10.3.7.90b) or via LPP. + +NOTE 14a: The element 'GNSS\_ref\_measurement\_assist' of 'GNSS\_assist' and 'acqu\_assist' of 'GNSS\_assist', both hold 'acqu\_assist' data. Therefore 'GNSS\_ref\_measurement\_assist' can be omitted when 'acqu\_assist' is present or vice versa. + +**Table 8.55-16: XML DTD for <nms\_clock\_nav>, <nms\_orbit\_nav>, <nms\_clock\_cnav>, <nms\_orbit\_cnav>** + +``` + +<!ELEMENT nms_clock_nav (nav_Toc,nav_af2,nav_af1,nav_af0,nav_Tgd)> + <!ELEMENT nav_Toc (#PCDATA)> <!-- 0..37799 --> + <!ELEMENT nav_af2 (#PCDATA)> <!-- -128..127 --> + <!ELEMENT nav_af1 (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_af0 (#PCDATA)> <!-- -2097152..2097151 --> + <!ELEMENT nav_Tgd (#PCDATA)> <!-- -128..127 --> + +<!ELEMENT nms_orbit_nav +(nav_URA,nav_FitFlag,nav Toe,nav_Omega,nav_DeltaN,nav_M0,nav_OmegaA_d,nav_E,nav_I_d,nav_APowerHalf,n +av_I0,nav_OmegaA0,nav_Crs,nav_Cis,nav_Cus,nav_Crc,nav_Cic,nav_Cuc, +(nav_CodeOnL2,nav_L2Pflag,nav_sfl_1,nav_sfl_2,nav_sfl_3,nav_sfl_4,nav_AODA) ?)> + <!ELEMENT nav_URA (#PCDATA)> <!-- 0..15 --> + <!ELEMENT nav_FitFlag (#PCDATA)> <!-- 0..1 --> + <!ELEMENT nav Toe (#PCDATA)> <!-- 0..37799 --> + <!ELEMENT nav_Omega (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT nav_DeltaN (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_M0 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT nav_OmegaA_d (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT nav_E (#PCDATA)> <!-- 0..4294967295 --> + <!ELEMENT nav_I_d (#PCDATA)> <!-- -8192..8191 --> + <!ELEMENT nav_APowerHalf (#PCDATA)> <!-- 0..4294967295 --> + <!ELEMENT nav_I0 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT nav_OmegaA0 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT nav_Crs (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_Cis (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_Cus (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_Crc (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_Cic (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_Cuc (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT nav_CodeOnL2 (#PCDATA)> <!-- 0..3 --> + <!ELEMENT nav_L2Pflag (#PCDATA)> <!-- 0..1 --> + <!ELEMENT nav_sfl_1 (#PCDATA)> <!-- 0..8388607 --> + <!ELEMENT nav_sfl_2 (#PCDATA)> <!-- 0..16777215 --> + <!ELEMENT nav_sfl_3 (#PCDATA)> <!-- 0..16777215 --> + <!ELEMENT nav_sfl_4 (#PCDATA)> <!-- 0..65535 --> + <!ELEMENT nav_AODA (#PCDATA)> <!-- 0..31 --> + +<!ELEMENT nms_clock_cnav +(cnav_Toc,cnav_Top,cnav_URA0,cnav_URA1,cnav_URA2,cnav_Af2,cnav_Af1,cnav_Af0,cnav_Tgd,cnav_ISC11cp?,c +nav_ISC11cd?,cnav_ISC11ca?,cnav_ISC12c?,cnav_ISC15i5?,cnav_ISC15q5?)> + <!ELEMENT cnav_Toc (#PCDATA)> <!-- 0..2015 --> + <!ELEMENT cnav_Top (#PCDATA)> <!-- 0..2015 --> + <!ELEMENT cnav_URA0 (#PCDATA)> <!-- -16..15 --> + <!ELEMENT cnav_URA1 (#PCDATA)> <!-- 0..7 --> + <!ELEMENT cnav_URA2 (#PCDATA)> <!-- 0..7 --> + <!ELEMENT cnav_Af2 (#PCDATA)> <!-- -512..511 --> + +``` + +``` + +<!ELEMENT cnav_Af1 (#PCDATA)> <!-- -524288..524287 --> +<!ELEMENT cnav_Af0 (#PCDATA)> <!-- -33554432..33554431 --> +<!ELEMENT cnav_Tgd (#PCDATA)> <!-- -4096..4095 --> +<!ELEMENT cnav_ISCl1cp (#PCDATA)> <!-- -4096..4095 --> +<!ELEMENT cnav_ISCl1cd (#PCDATA)> <!-- -4096..4095 --> +<!ELEMENT cnav_ISCl1ca (#PCDATA)> <!-- -4096..4095 --> +<!ELEMENT cnav_ISCl2c (#PCDATA)> <!-- -4096..4095 --> +<!ELEMENT cnav_ISCl5i5 (#PCDATA)> <!-- -4096..4095 --> +<!ELEMENT cnav_ISCl5q5 (#PCDATA)> <!-- -4096..4095 --> + +<!ELEMENT nms_orbit_cnav +(cnav_Top,cnav_URAindex,cnav_DeltaA,cnav_Adot,cnav_DeltaNo,cnav_DeltaNoDot,cnav_Mo,cnav_E,cnav_Omega +,cnav_OMEGA0,cnav_DeltaOmegaDot,cnav_Io,cnav_IoDot,cnav_Cis,cnav_Cic,cnav_Crs,cnav_Crc,cnav_Cus,cnav +_Cuc)> + <!ELEMENT cnav_URAindex (#PCDATA)> <!-- -16..15 --> + <!ELEMENT cnav_DeltaA (#PCDATA)> <!-- -33554432..33554431 --> + <!ELEMENT cnav_Adot (#PCDATA)> <!-- -16777216..16777215 --> + <!ELEMENT cnav_DeltaNo (#PCDATA)> <!-- -65536..65535 --> + <!ELEMENT cnav_DeltaNoDot (#PCDATA)> <!-- -4194304..4194303 --> + <!ELEMENT cnav_Mo (#PCDATA)> <!-- -4294967296..4294967295 --> + <!ELEMENT cnav_E (#PCDATA)> <!-- 0..8589934591 --> + <!ELEMENT cnav_Omega (#PCDATA)> <!-- -4294967296..4294967295 --> + <!ELEMENT cnav_OMEGA0 (#PCDATA)> <!-- -4294967296..4294967295 --> + <!ELEMENT cnav_DeltaOmegaDot (#PCDATA)> <!-- -65536..65535 --> + <!ELEMENT cnav_Io (#PCDATA)> <!-- -4294967296..4294967295 --> + <!ELEMENT cnav_IoDot (#PCDATA)> <!-- -16384..16383 --> + <!ELEMENT cnav_Cis (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT cnav_Cic (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT cnav_Crs (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT cnav_Crc (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT cnav_Cus (#PCDATA)> <!-- -1048576..1048575 --> + <!ELEMENT cnav_Cuc (#PCDATA)> <!-- -1048576..1048575 --> + +``` + +**Table 8.55-17: XML DTD for <nms\_orbit\_glonass>, <nms\_clock\_glonass>** + +``` + +<!ELEMENT nms_orbit_glonass +(glo_En,glo_P1,glo_P2,glo_M,glo_X,glo_X_d,glo_X_dd,glo_Y,glo_Y_d,glo_Y_dd,glo_Z_d,glo_Z_dd)> + <!ELEMENT glo_En (#PCDATA)> <!-- 0..31 --> + <!ELEMENT glo_P1 (#PCDATA)> <!-- hex --> + <!ELEMENT glo_P2 (#PCDATA)> <!-- 0..1 --> + <!ELEMENT glo_M (#PCDATA)> <!-- 0..3 --> + <!ELEMENT glo_X (#PCDATA)> <!-- -67108864..67108863 --> + <!ELEMENT glo_X_d (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT glo_X_dd (#PCDATA)> <!-- -16..15 --> + <!ELEMENT glo_Y (#PCDATA)> <!-- -67108864..67108863 --> + <!ELEMENT glo_Y_d (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT glo_Y_dd (#PCDATA)> <!-- -16..15 --> + <!ELEMENT glo_Z (#PCDATA)> <!-- -67108864..67108863 --> + <!ELEMENT glo_Z_d (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT glo_Z_dd (#PCDATA)> <!-- -16..15 --> + +<!ELEMENT nms_clock_glonass (glo_Tau,glo_Gamma,glo_DeltaTau)> + <!ELEMENT glo_Tau (#PCDATA)> <!-- -2097152..2097151 --> + <!ELEMENT glo_Gamma (#PCDATA)> <!-- -1024..1023 --> + <!ELEMENT glo_DeltaTau (#PCDATA)> <!-- -16..15 --> + +``` + +**Table 8.55-18: XML DTD for <nms\_clock\_sbas>, <nms\_orbit\_sbas>** + +``` + +<!ELEMENT nms_clock_sbas (sbas_To,sbas_Agfo,sbas_Agf1)> <!-- model 4 --> + <!ELEMENT sbas_To (#PCDATA)> + <!ELEMENT sbas_Agfo (#PCDATA)> + <!ELEMENT sbas_Agf1 (#PCDATA)> + +<!ELEMENT nms_orbit_sbas +(sbas_To,sbas_accuracy,sbas_Xg,sbas_Yg,sbas_Zg,sbas_Xg_d,sbas_Yg_d,sbas_Zg_d,sbas_Xg_dd,sbas_Yg_dd,sbas_Zg_dd)> <!-- model 4 --> + <!ELEMENT sbas_accuracy (#PCDATA)> <!-- hex --> + <!ELEMENT sbas_Xg (#PCDATA)> + <!ELEMENT sbas_Yg (#PCDATA)> + <!ELEMENT sbas_Zg (#PCDATA)> + <!ELEMENT sbas_Xg_d (#PCDATA)> + <!ELEMENT sbas_Yg_d (#PCDATA)> + <!ELEMENT sbas_Zg_d (#PCDATA)> + +``` + +``` + +<!ELEMENT sbas_Xg_dd (#PCDATA)> +<!ELEMENT sbas_Yg_dd (#PCDATA)> +<!ELEMENT sbas_Zg_dd (#PCDATA)> + +``` + +**Table 8.55-19: XML DTD for <GNSS\_provided\_location\_information>** + +``` + +<!ELEMENT GNSS_provided_location_information (GNSS_meas*| +(agnss_list,GNSS_meas_ref_time,locationparameters,earlyFixReport-r12?))> +<!ELEMENT agnss_list (#PCDATA) <!-- Integer corresponds to bit string 1-8 where bit at position +if set, means particular GNSS id is supported bit0-GPS,bit1-sbas,bit2-qzss,bit3-galileo,bit4- +glonass,bit5-bds --> +<!ELEMENT GNSS_meas_ref_time (gnss TOD msec,gnss TOD_frac?,gnss TOD_unc?)> +<!ATTLIST GNSS_meas_ref_time time_id (SBAS|MGPS|QZSS|Glonass|GPS|BDS) #IMPLIED> +<!ELEMENT gnss TOD msec (#PCDATA)> <!-- 0..3599999 --> +<!ELEMENT gnss TOD_frac (#PCDATA)> <!-- 0..39999 --> +<!ELEMENT gnss TOD_unc (#PCDATA)> <!-- 0..127 --> + +``` + +NOTE 15:GNSS\_provide\_location\_information is used for reporting location information for GNSS procedures i.e. procedures where GNSS\_allowed\_methods or GNSS\_assist is received. This element matches the ASN.1 element GANSSLocationInfo for RRLP procedures; UE positioning measured results information element for RRC or ASN.1 A-GNSS-ProvideLocationInformation for LPP. + +NOTE 15a: Both in 'pos\_meas' and 'pos\_meas\_req', either MS-Based or MS-Assisted positioning can be specified requiring either 'location\_parameters' or 'GNSS\_meas' elements respectively. + +**Table 8.55-20: XML DTD for <OTDOA\_meas>** + +``` + +<!ELEMENT OTDOA_meas +(system_frame_number,phys_cell_id_ref,cell_global_id_ref?,earfcn_ref?,ref_quality?,neighbour_meas_li +st,earlyFixReport-r12?))> +<!ELEMENT system_frame_number (#PCDATA)> +<!ELEMENT phys_cell_id_ref (#PCDATA)> <!-- 0..503 --> +<!ELEMENT cell_global_id_ref (mcc,mnc,cell_id)> +<!ELEMENT mcc (#PCDATA)> +<!ELEMENT mnc (#PCDATA)> +<!ELEMENT cell_id (#PCDATA)> +<!ELEMENT earfcn_ref (#PCDATA)> <!-- 0..65535 --> +<!ELEMENT ref_quality (OTDOA_meas_quality)> +<!ELEMENT neighbour_meas_list (neighbour_meas_element)+> +<!ELEMENT neighbour_meas_element +(phys_cell_id_neighbour,cell_global_id_neighbour?,earfcn_neighbour?,rstd,rstd_quality)> +<!ELEMENT phys_cell_id_neighbour (#PCDATA)> +<!ELEMENT cell_global_id_neighbour (mcc,mnc,cell_identity)> +<!ELEMENT mcc (#PCDATA)> +<!ELEMENT mnc (#PCDATA)> +<!ELEMENT cell_identity (#PCDATA)> +<!ELEMENT earfcn_neighbour (#PCDATA)> <!-- 0..65535 --> +<!ELEMENT rstd (#PCDATA)> <!-- 0..12711 --> +<!ELEMENT rstd_quality (OTDOA_meas_quality)> +<!ELEMENT OTDOA_meas_quality (err_resolution,err_value,err_num_samples?)> +<!ELEMENT err_resolution (#PCDATA)> +<!ELEMENT err_value (#PCDATA)> +<!ELEMENT err_num_samples (#PCDATA)> + +``` + +NOTE 16:For the elements and the value ranges of OTDOA measurements refer to 3GPP TS 36.355 [115] (clause 6.5.1). The value ranges of relevant parameters are described in the ASN.1 syntax. + +**Table 8.55-21: XML DTD for <OTDOA\_assist\_req>** + +``` + +<!ELEMENT OTDOA_assist_req (phys_cell_id)> +<!ELEMENT phys_cell_id (#PCDATA)> <!-- 0..503 --> + +``` + +**Table 8.55-22: XML DTD for <reset\_assist\_data>** + +``` +<!ELEMENT reset_assist_data EMPTY> <!-- Reset UE positioning stored AGNSS/OTDOA/Sensor/TBS +assistance data --> +``` + +NOTE 17: For resetting UE positioning stored AGNSS assistance data refer to 3GPP TS 36.509 [142] (clause 6.9). + +**Table 8.55-23: XML DTD for <OTDOA\_ECID\_req>** + +``` +<!ELEMENT OTDOA_ECID_req (abort|request_location_info)> + <!ELEMENT abort EMPTY> + <!ATTLIST abort otdoa_meas_req (true|false) "false" + abort_ecid_meas_req (true|false) "false"> <!-- Session ID will be provided in Transaction ID +under root element <pos> --> + <!ELEMENT request_location_info (OTDOA_req_loc_info?, ECID_req_loc_info?, (response_time| +periodic_reporting|triggered_reporting)?)> <!-- triggered reporting for ECID_req_loc_info only --> + <!ATTLIST request_location_info emergency_call_indicator (true|false) "false"> + <!ELEMENT OTDOA_req_loc_info EMPTY> + <!ATTLIST OTDOA_req_loc_info assistance_available (true|false) #REQUIRED> + <!ELEMENT ECID_req_loc_info EMPTY> + <!ATTLIST ECID_req_loc_info + rs_rp_req (true|false) "false" + rs_rq_req (true|false) "false" + ue_rx_tx_req (true|false) "false"> + <!ELEMENT response_time (time, earlyFixReport-r12?)> + <!ELEMENT periodic_reporting (rep_amount, rep_interval)> + <!ELEMENT rep_amount EMPTY> + <!ATTLIST rep_amount literal (ra1|ra2|ra4|ra8|ra16|ra32|ra64|ra-Infinity) #REQUIRED> + <!ELEMENT rep_interval EMPTY> + <!ATTLIST rep_interval literal (ri1|ri2|ri4|ri8|ri16|ri32|ri64)> + <!ELEMENT triggered_reporting (rep_duration)> + <!ATTLIST triggered_reporting cell_change (true|false) #REQUIRED> + <!ELEMENT rep_duration #PCDATA> <!-- 0..255 --> +``` + +NOTE 18: 'emergency\_call\_indicator' indicates whether the OTDOA and/or ECID location request is due to an Emergency Call. + +**Table 8.55-24: XML DTD for <ECID\_meas>** + +``` +<!ELEMENT ECID_meas (primary_cell_measured_results?, measured_result_list)> + <!ELEMENT primary_cell_measured_results (measured_result_element)> + <!ELEMENT measured_result_element + (phys_cell_id, cell_global_id?, earfcn_eutra, sfn?, rsrp_result?, rsrq_result?, ue_rxtx_time_diff?)> + <!ELEMENT phys_cell_id (#PCDATA)> <!-- 0..503 --> + <!ELEMENT cell_global_id (mcc, mnc, cell_id)> + <!ELEMENT mcc (#PCDATA)> + <!ELEMENT mnc (#PCDATA)> + <!ELEMENT cell_id (#PCDATA)> + <!ELEMENT earfcn_eutra (#PCDATA)> <!-- 0..262143 --> + <!ELEMENT sfn (#PCDATA)> + <!ELEMENT rsrp_result (#PCDATA)> <!-- 0..97 --> + <!ELEMENT rsrq_result (#PCDATA)> <!-- 0..34 --> + <!ELEMENT ue_rxtx_time_diff (#PCDATA)> <!-- -0..4095 --> + <!ELEMENT measured_result_list (measured_result_element+)> <!-- 1..32 --> +``` + +**Table 8.55-25: XML DTD for <Strobe>** + +``` +<!ELEMENT Strobe (#PCDATA)> <!-- Triggers the generation of a strobe --> +``` + +**Table 8.55-26: XML DTD for <nms\_clock\_bds>** + +``` +<!ELEMENT nms_clock_bds (bdsToc-r12, bdsA0-r12, bdsA1-r12, bdsA2-r12, bdsTgd1-r12)> + <!ELEMENT bdsToc-r12 (#PCDATA)> <!-- 0..131071 --> + <!ELEMENT bdsA0-r12 (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT bdsA1-r12 (#PCDATA)> <!-- -2097152..2097151 --> +``` + +``` +<!ELEMENT bdsA2-r12 (#PCDATA)> <!-- -1024..1023 --> +<!ELEMENT bdsTgd1-r12 (#PCDATA)> <!-- -512..511--> +``` + +**Table 8.55-27: XML DTD for <nms\_orbit\_bds>** + +``` +<!ELEMENT nms_orbit_bds(bdsURAI-r12,bdsToe-r12,bdsAPowerHalf-r12,bdsE-r12,bdsW-r12,bdsDeltaN- +r12,bdsM0-r12,bdsOmega0-r12,bdsOmegaDot-r12,bdsI0-r12, bdsIDot-r12,bdsCuc-r12,bdsCus-r12,bdsCrc- +r12,bdsCrs-r12,bdsCic-r12,bdsCis-r12)> + <!ELEMENT bdsURAI-r12 (#PCDATA)> <!-- 0..15 --> + <!ELEMENT bdsToe-r12 (#PCDATA)> <!-- 0..131071 --> + <!ELEMENT bdsAPowerHalf-r12 (#PCDATA)> <!-- 0..4294967295 --> + <!ELEMENT bdsE-r12 (#PCDATA)> <!-- 0..4294967295 --> + <!ELEMENT bdsW-r12 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT bdsDeltaN-r12 (#PCDATA)> <!-- -32768..32767 --> + <!ELEMENT bdsM0-r12 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT bdsOmega0-r12 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT bdsOmegaDot-r12 (#PCDATA)> <!-- -8388608..8388607 --> + <!ELEMENT bdsI0-r12 (#PCDATA)> <!-- -2147483648..2147483647 --> + <!ELEMENT bdsIDot-r12 (#PCDATA)> <!-- -8192..8191 --> + <!ELEMENT bdsCuc-r12 (#PCDATA)> <!-- -131072..131071 --> + <!ELEMENT bdsCus-r12 (#PCDATA)> <!-- -131072..131071 --> + <!ELEMENT bdsCrc-r12 (#PCDATA)> <!-- -131072..131071 --> + <!ELEMENT bdsCrs-r12 (#PCDATA)> <!-- -131072..131071 --> + <!ELEMENT bdsCic-r12 (#PCDATA)> <!-- -131072..131071 --> + <!ELEMENT bdsCis-r12 (#PCDATA)> <!-- -131072..131071 --> +``` + +**Table 8.55-28: XML DTD for <Bluetooth\_meas>** + +``` +<!ELEMENT Bluetooth_meas (meas_ref_time?,bt_meas?)> + <!ELEMENT meas_ref_time (#PCDATA)> <!-- ASN.1 data type UTCTime --> + <!ELEMENT bt_meas (bt_addr,rssi?)> + <!ELEMENT bt_addr (#PCDATA)> + <!ELEMENT rssi (#PCDATA)> +``` + +NOTE 19:For the elements and the value ranges of Bluetooth measurements refer to 3GPP TS 36.355 [115] (clause 6.5.7). The value ranges of relevant parameters are described in the ASN.1 syntax. + +**Table 8.55-29: XML DTD for <Sensor\_meas>** + +``` +<!ELEMENT Sensor_meas (meas_ref_time?,unc_baro_pressure?,uncertainty?)> + <!ELEMENT meas_ref_time (#PCDATA)> <!-- ASN.1 data type UTCTime --> + <!ELEMENT unc_baro_pressure (#PCDATA)> <!-- 30000..115000 --> + <!ELEMENT uncertainty (range,confidence)> + <!ELEMENT range (#PCDATA)> <!-- 0..1000 --> + <!ELEMENT confidence (#PCDATA)> <!-- 1..100 --> +``` + +NOTE 20:For the elements and the value ranges of Sensor measurements refer to 3GPP TS 36.355 [115] (clause 6.5.5). The value ranges of relevant parameters are described in the ASN.1 syntax. + +**Table 8.55-30: XML DTD for <Sensor\_assist\_req>** + +``` +<!ELEMENT Sensor_assist_req EMPTY> +``` + +**Table 8.55-31: XML DTD for <TBS\_meas>** + +``` +<!ELEMENT TBS_meas (meas_ref_time?,mbs_meas_list?)> + <!ELEMENT meas_ref_time (#PCDATA)> <!-- ASN.1 data type UTCTime --> + <!ELEMENT mbs_meas_list (trans_ID,code_phase,code_phase_rms_error)> + <!ELEMENT trans_ID (#PCDATA)> <!-- 0..32767 --> + <!ELEMENT code_phase (#PCDATA)> <!-- 0..2097151 --> + <!ELEMENT code_phase_rms_error (#PCDATA)> <!-- 0..63 --> +``` + +NOTE 21: For the elements and the value ranges of TBS measurements refer to 3GPP TS 36.355 [115] (clause 6.5.4). The value ranges of relevant parameters are described in the ASN.1 syntax. + +**Table 8.55-32: XML DTD for <TBS\_assist\_req>** + +``` +<!ELEMENT TBS_assist_req (mbs_almanac_assist_req,mbs_acqu_assist_req)> + <!ELEMENT mbs_almanac_assist_req EMPTY> + <!ELEMENT mbs_acqu_assist_req EMPTY> +``` + +**Table 8.55-33: XML DTD for <WLAN\_meas>** + +``` +<!ELEMENT WLAN_meas (meas_ref_time?,wlan_meas_list?)> + <!ELEMENT meas_ref_time (#PCDATA)> <!-- ASN.1 data type UTCTime --> + <!ELEMENT wlan_meas_list (wlan_AP_ID,rssi?,rtt?,ap_ch_freq?,serving_flag?)> + <!ELEMENT wlan_AP_ID (#PCDATA)> + <!ELEMENT rssi (#PCDATA)> + <!ELEMENT rtt (#PCDATA)> + <!ELEMENT ap_ch_freq (#PCDATA)> + <!ELEMENT serving_flag (true|false)> +``` + +NOTE 22: For the elements and the value ranges of WLAN measurements refer to 3GPP TS 36.355 [115] (clause 6.5.6). The value ranges of relevant parameters are described in the ASN.1 syntax. + +## Implementation + +Optional. + +## 8.56 Positioning reporting +CPOSR + +**Table 8.56-1: +CPOSR parameter command syntax** + +| Command | Possible response(s) | +|---------------|-------------------------------------| +| +CPOSR=<mode> | | +| +CPOSR? | +CPOSR: <mode> | +| +CPOSR=? | +CPOSR: (list of supported <mode>s) | + +### Description + +Set command enables or disables the sending of unsolicited result codes. The XML-formatted string may be sent as one or more unsolicited result codes. Each part of the XML-formatted string is sent as one unsolicited result code, prefixed with +CPOSR. + +NOTE: An XML-formatted string intended for +CPOSR can be split e.g. in order to prevent that the string becomes too long. Where to split an XML-formatted string is implementation specific. The characters <CR><LF>, <+CPOSR> and space(s) are ignored when re-constructing an XML-formatted string. + +Example: +CPOSR: <One line of positioning data sent on XML format>. + +Read command returns the current mode. + +Test command returns the supported values as a compound value. + +### Defined values + +<mode>: integer type + +0 disables reporting + +1 enables reporting + +## Defined events + +- <pos\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of position measurements data request as defined in table 8.55-8. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <pos\_meas\_req>: string type in UTF-8. This parameter provides an XML-formatted string of position measurements request data as defined in table 8.55-9. This is an alternative to <pos\_meas>. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <OTDOA\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of OTDOA measurement data as defined in table 8.55-20. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <ECID\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of ECID measurement data as defined in table 8.55-24. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <OTDOA\_assist\_req>: string type in UTF-8. This parameter provides an XML-formatted string for requesting OTDOA assistance data as defined in table 8.55-21. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <capabilities>: string type in UTF-8. This parameter provides an XML-formatted string for providing capability data as defined in table 8.55-4. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <msg>: string type in UTF-8. This parameter provides an XML-formatted string for communicating simple messages as defined in table 8.55-13. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <pos\_err>: string type in UTF-8. This parameter provides an XML-formatted string of positioning error parameters as defined in table 8.55-14. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <reset\_assist\_data>: string type in UTF-8. This parameter provides an XML-formatted string for resetting GNSS/OTDOA/Sensor/TBS assistance data as defined in table 8.55-22. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <Bluetooth\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of Bluetooth measurement data as defined in table 8.55-28. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <Sensor\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of Sensor measurement data as defined in table 8.55-29. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <Sensor\_assist\_req>: string type in UTF-8. This parameter provides an XML-formatted string for requesting Sensor assistance data as defined in table 8.55-30. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <TBS\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of TBS measurement data as defined in table 8.55-31. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <TBS\_assist\_req>: string type in UTF-8. This parameter provides an XML-formatted string for requesting TBS assistance data as defined in table 8.55-32. This parameter shall not be subject to conventional character conversion as per +CSCS. +- <WLAN\_meas>: string type in UTF-8. This parameter provides an XML-formatted string of WLAN measurement data as defined in table 8.55-33. This parameter shall not be subject to conventional character conversion as per +CSCS. + +**Implementation** + +Optional. + +## 8.57 Mobile terminated location request notification +CMTLR + +**Table 8.57-1: +CMTLR parameter command syntax** + +| Command | Possible response(s) | +|----------------------|------------------------------------------------| +| +CMTLR=[<subscribe>] | | +| +CMTLR? | +CMTLR: <subscribe> | +| +CMTLR=? | +CMTLR: (list of supported <subscribe> values) | + +### Description + +Set command enables Mobile Terminated Location Request (MT-LR) notifications to the TE. The parameter <subscribe> enables or disables notification by an unsolicited result code. It is possible to enable notification of MT-LR performed over the control plane or over SUPL or both. Relevant location request parameters are provided in the unsolicited result code +CMTLR: <handle-id>, <notification-type>, <location-type>, [<client-external-id>], [<client-name>] [, <plane>]. + +This unsolicited result code is reported upon arrival of a Mobile Terminated Location Request. In order to differentiate multiple requests, every request is given a different <handle-id>. This ID is used when allowing or denying location disclosure with +CMTLRA. + +Read command returns the current value of <subscribe>. + +Test command returns the supported values as a compound value. + +### Defined values + +<subscribe>: integer type. Enables and disables the subscription for MT-LR notifications. + +- 0 Disables reporting and positioning. +- 1 Subscribe for notifications of MT-LR over control plane. +- 2 Subscribe for notifications of MT-LR over SUPL. +- 3 Subscribe for notifications of MT-LR over control plane and SUPL. + +<handle-id>: integer type. ID associated with each MT-LR used to distinguish specific request in case of multiple requests. The value range is 0-255. + +<notification-type>: integer type. Information about the user's privacy. + +- 0 The subscription may stipulate that positioning the user by a third party is allowed and the network may choose to inform the user as a matter of courtesy. +- 1 Locating the user is permitted if the user ignores the notification. +- 2 Locating the user is forbidden if the user ignores the notification. + +<location-type>: integer type. Indicates what type of the location is requested. + +- 0 The current location. +- 1 The current or last known location. +- 2 The initial location. + +<client-external-id>: string type. Indicates the external client where the location information is sent to (if required). + +<client-name>: string type. Contains the string identifying the external client requesting the user's location. + +<plane>: integer type. The parameter specifies whether the MT-LR came over control plane or SUPL. + +- 0 Control plane. +- 1 Secure user plane (SUPL). + +#### Implementation + +Optional. + +## 8.58 Mobile terminated location request disclosure allowance +CMTLRA + +**Table 8.58-1: +CMTLRA parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------|---------------------------------------------| +| +CMTLRA=<allow>,<handle_id> | | +| +CMTLRA? | +CMTLRA: <allow>,<handle_id> | +| +CMTLRA=? | +CMTLRA: (list of supported <allow> values) | + +#### Description + +Set command allows or disallows disclosure of the location to the TE as a result of MT-LR by the parameter <allow>. + +Read command returns the current values. + +Test command returns the supported values. + +#### Defined values + +<allow>: integer type. Enables and disables the allowance for location disclosure. + +- 0 Location disclosure allowed. +- 1 Location disclosure not allowed. + +<handle-id>: integer type. ID associated with each MT-LR used to distinguish specific request in case of multiple requests. The value is given in +CMTLR. The value range is 0-255. + +#### Implementation + +Optional. + +## 8.59 Battery capacity +CBCAP + +**Table 8.59-1: CBCAP parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------------------|--------------------------------------------------------------------------------------| +| +CBCAP=[<reporting>[, <reporting_interval>]] | | +| +CBCAP? | +CBCAP: <reporting>,<reporting_interval>,<bcl> | +| +CBCAP=? | +CBCAP: (list of supported <reporting>s) , (list of supported <reporting_interval>s) | + +### Description + +Set command enables reporting upon change in battery capacity level, with unsolicited result code +CBCAP: <bcl>. Consecutive reports never show same value of <bcl>. + +Read command returns the status of result code presentation and the current battery capacity level. + +Test command returns values supported as compound values. + +### Defined values + +<reporting>: integer type. Enables and disables reporting of changes in the battery capacity level. + +0 Disable reporting + +1 Enable reporting + +<reporting\_interval>: integer type. Sets the reporting interval of the battery capacity level (in percentages). The default value is manufacturer specific. + +1...100 Amount that the remaining battery capacity must change before reporting. + +<bcl>: integer type. Gives the remaining relative battery capacity level (in percentages). + +0 The battery is exhausted or ME does not have a battery connected + +1...100 remaining battery capacity level (in percentages). The provided values are dependant on the parameter <reporting\_interval>. A value of 5 for parameter <reporting\_interval>, means that the following values of <bcl> are applicable: 0, 5, 10, 15, ... , 90, 95, 100. + +NOTE: 100% capacity is always reported, even if <reporting\_interval> is set to a value where no integer multiple equals 100. + +### Implementation + +Optional. + +## 8.60 Battery connection status +CBCON + +**Table 8.60-1: +CBCON parameter command syntax** + +| Command | Possible response(s) | +|----------------------|------------------------------------------| +| +CBCON=[<reporting>] | | +| +CBCON? | +CBCON: <reporting>, <bcs> | +| +CBCON=? | +CBCON: (list of supported <reporting>s) | + +### Description + +Set command enables reporting upon change in battery connection status, with unsolicited result code +CBCON: <bcs>. + +Read command returns the status of result code presentation and the current battery status. + +Test command returns values supported as a compound value. + +### Defined values + +<reporting>: integer type. Enables and disables reporting of changes in the battery connection status. + +0 disable reporting + +1 enable reporting + +<bcs>: integer type. Indicates the battery status. + +- 0 ME is powered by the battery +- 1 ME has a battery connected, but is not powered by it +- 2 ME does not have a battery connected +- 3 Recognized power fault, calls inhibited + +#### Implementation + +Optional. + +## 8.61 Battery charger status +CBCHG + +**Table 8.61-1: +CBCHG parameter command syntax** + +| Command | Possible response(s) | +|----------------------|------------------------------------------| +| +CBCHG=[<reporting>] | | +| +CBCHG? | +CBCHG: <reporting>, <chg_status> | +| +CBCHG=? | +CBCHG: (list of supported <reporting>s) | + +#### Description + +Set command enables reporting upon change in battery charger status, with unsolicited result code +CBCHG: <chg\_status>. + +Read command returns the status of result code presentation and the current battery charger status. + +Test command returns values supported as a compound value. + +#### Defined values + +<reporting>: integer type. Enables and disables reporting of changes in the battery charger status. + +- 0 disable reporting +- 1 enable reporting + +<chg\_status>: integer type. Indicates type of battery charger status. + +- 0 no charger connected +- 1 charger connected, normal type charger +- 2 charger connected, USB type charger + +#### Implementation + +Optional. + +## 8.62 Printing IP address format +CGPIAF + +**Table 8.62-1: +CGPIAF parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------------|----------------------| +| +CGPIAF=[<IPv6_AddressFormat>][, <IPv6_SubnetNotation>][, <IPv6_LeadingZeros>][, <IPv6_CompressZeros>]<br>]]] | | + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGPIAF? | +CGPIAF: <IPv6_AddressFormat>, <IPv6_SubnetNotation>, <IPv6_LeadingZeros>, <IPv6_CompressZeros> | +| +CGPIAF=? | +CGPIAF: (list of supported <IPv6_AddressFormat>s), (list of supported <IPv6_SubnetNotation>s), (list of supported <IPv6_LeadingZeros>s), (list of supported <IPv6_CompressZeros>s) | + +## Description + +Set command decides what format to print IPv6 address parameters of other AT commands. See RFC 4291 [88] for details of the IPv6 address format. + +The +CGPIAF parameters <IPv6\_AddressFormat>, <IPv6\_SubnetNotation>, <IPv6\_LeadingZeros> and <IPv6\_CompressedZeros> affect the following commands and parameters: + +- in +CGTFT and +CGTFTRDP, the <remote address and subnet mask>; +- in +CGDCONT, the <PDP\_addr>; +- in +CGPADDR, the <PDP\_addr\_1> and <PDP\_addr\_2>; +- in +CGCONTRDP, the <local address and subnet mask>, <DNS\_prim\_addr>, <DNS\_sec\_addr>, <P\_CSCF\_prim\_addr> and <P\_CSCF\_sec\_addr>; and +- in +CRC, the <PDP\_addr> of unsolicited result code +CRING: GPRS <PDP\_type>, <PDP\_addr>[, [<L2P>] [, <APN>] ] . + +Read command returns the current command parameter settings. + +Test command returns values supported as compound values. + +## Defined values + +<IPv6\_AddressFormat>: integer type, decides the IPv6 address format. Relevant for all AT command parameters that can hold an IPv6 address. + +- 0 Use IPv4-like dot-notation. IP address, and subnetwork mask if applicable, are dot-separated. + +Example: For <remote address and subnet mask>: + "32.1.13.184.0.0.205.48.0.0.0.0.0.0.0.255.255.255.255.255.255.240.0.0.0.0.0.0.0.0" + For other IP address parameters: + "32.1.13.184.0.0.205.48.0.0.0.0.0.0.0.0" + +- 1 Use IPv6-like colon-notation. IP address, and subnetwork mask if applicable and when given explicitly, are separated by a space. + +Example: For <remote address and subnet mask>: + "2001:0DB8:0000:CD30:0000:0000:0000:0000 FFFF:FFFF:FFFF:FFF0:0000:0000:0000:0000" + For other IP address parameters: + "2001:0DB8:0000:CD30:0000:0000:0000:0000" + +<IPv6\_SubnetNotation>: integer type, decides the subnet-notation for <remote address and subnet mask>. Setting does not apply if <IPv6\_AddressFormat>=0. + +- 0 Both IP Address and subnet mask are stated explicitly, separated by a space. + +Example: "2001:0DB8:0000:CD30:0000:0000:0000:0000 FFFF:FFFF:FFFF:FFF0:0000:0000:0000:0000" + +- 1 The printout format is applying / (forward slash) subnet-prefix Classless Inter-Domain Routing (CIDR) notation. + +Example: "2001:0DB8:0000:CD30:0000:0000:0000:0000/60" + +<IPv6\_LeadingZeros>: integer type, decides whether leading zeros are omitted or not. Setting does not apply if <IPv6\_AddressFormat>=0. + +0 Leading zeros are omitted. + +Example: "2001:DB8:0:CD30:0:0:0:0" + +1 Leading zeros are included. + +Example: "2001:0DB8:0000:CD30:0000:0000:0000:0000" + +<IPv6\_CompressZeros>: integer type, decides whether 1-n instances of 16-bit zero-values are replaced by only '::'. This applies only once. Setting does not apply if <IPv6\_AddressFormat>=0. + +0 No zero compression. + +Example: "2001:DB8:0:CD30:0:0:0:0" + +1 Use zero compression. + +Example: "2001:DB8:0:CD30::" + +#### Implementation + +Optional. + +### 8.63 IMS single radio voice call continuity +CISRVCC + +**Table 8.63-1: +CISRVCC parameter command syntax** + +| Command | Possible response(s) | +|----------------------|------------------------------------------| +| +CISRVCC=[<uesrvcc>] | +CME ERROR: <err> | +| +CISRVCC? | +CISRVCC: <uesrvcc> | +| +CISRVCC=? | +CISRVCC: (list of supported <uesrvcc>s) | + +#### Description + +SRVCC provides the ability to have a seamless handover of a voice call between the PS domain and the CS domain for calls that are anchored in IMS, when the UE is capable of transmitting/receiving on only one of those access networks (PS or CS) at a given time, see 3GPP TS 23.221 [90] clause 7.2a, annex A.1 and annex A.2. The SRVCC support also includes the support of 5G-SRVCC from NG-RAN to UTRAN as specified in 3GPP TS 23.216 [171] clause 6.5.4. + +Set command informs MT about the SRVCC Support. MT normally updates the network when changing this parameter. Refer clause 9.2 for possible <err> values. + +Read command returns the status of the MT stored SRVCC Support. + +Test command returns supported values as a compound value. + +#### Defined values + +<uesrvcc>: integer type. SRVCC support status + +0 The UE does not have SRVCC support + +1 The UE has SRVCC support + +#### Implementation + +Optional. + +## 8.64 IMS network reporting +CIREP + +**Table 8.64-1: +CIREP parameter command syntax** + +| Command | Possible response(s) | +|---------------------|-------------------------------------------------------| +| +CIREP=<reporting>] | | +| +CIREP? | +CIREP: <reporting>, <nwimsvops>[, <nwimsvops_n3gpp>] | +| +CIREP=? | +CIREP: (list of supported <reporting>s) | + +### Description + +Set command enables or disables reporting of PS to CS Single Radio Voice Call Continuity (SRVCC), PS to CS Single Radio Video Call Continuity (vSRVCC) handover information and CS to PS Single Radio Voice Call Continuity (see 3GPP TS 24.237 [91]), of IMS Voice Over PS sessions (IMSVOPS) indicator information and of IMS Voice Over PS sessions over non-3GPP (IMSVOPS-N3GPP) indicator information, by the following unsolicited result codes: + ++CIREPI: <nwimsvops>[, <nwimsvops\_n3gpp>] IMS Voice Over PS sessions (IMSVOPS) supported indication from the network and IMS Voice Over PS sessions over non-3GPP (IMSVOPS-N3GPP) supported indication. + ++CIREPH: <srcvch> Provides PS to CS SRVCC, PS to CS vSRVCC and CS to PS SRVCC handover information. + +Read command returns the status of result code presentation and the IMSVOPS supported indication. + +Test command returns supported values as a compound value. + +### Defined values + +<reporting>: integer type. Enables or disables reporting of changes in the IMSVOPS and the IMSVOPS-N3GPP supported indications received from the network and reporting of PS to CS SRVCC, PS to CS vSRVCC and CS to PS SRVCC handover information. + +- 0 Disable reporting +- 1 Enable reporting + +<nwimsvops>: integer type. Gives the last IMS Voice Over PS sessions (IMSVOPS) supported indication received from network. + +- 0 IMSVOPS support indication is not received from network, or is negative. +- 1 IMSVOPS support indication as received from network is positive. + +<nwimsvops\_n3gpp>: integer type. Gives the last IMS Voice Over PS sessions over non-3GPP (IMSVOPS-N3GPP) supported indication received from network. The parameter is only provided in a 5GS system. + +- 0 IMSVOPS-N3GPP support indication is not received from network, or is negative. +- 1 IMSVOPS-N3GPP support indication as received from network is positive. + +<srcvch>: integer type. PS to CS SRVCC, PS to CS vSRVCC and CS to PS SRVCC handover information. + +- 0 PS to CS SRVCC handover has started in the CS domain ("Handover Command" indicating PS to CS SRVCC received). +- 1 PS to CS SRVCC handover successful ("Handover Complete" sent). +- 2 PS to CS SRVCC or PS to CS vSRVCC handover cancelled ("Handover Failure" sent). +- 3 PS to CS SRVCC or PS to CS vSRVCC handover, general non-specific failure. + +- 4 PS to CS vSRVCC handover has started in the CS domain ("Handover Command" indicating vSRVCC received). +- 5 PS to CS vSRVCC handover successful ("Handover Complete" sent). +- 6 CS to PS SRVCC handover has started in the PS domain ("Handover Command" indicating CS to PS SRVCC received). +- 7 CS to PS SRVCC handover cancelled ("Handover Failure" sent). +- 8 CS to PS SRVCC handover, general non-specific failure. +- 9 CS to PS SRVCC handover successful ("Handover Complete" sent). + +NOTE 1: Value 3 and 8, general non-specific failure, might be used e.g. in the case of handover cancellation as specified in 3GPP TS 24.301 [83] clause 6.6.2. + +NOTE 2: The naming of SRVCC and vSRVCC handover information values is different from the naming of corresponding NAS session management notifications. + +NOTE 3: PS to CS SRVCC support also includes the support of 5G-SRVCC from NG-RAN to UTRAN as specified in 3GPP TS 23.216 [171] clause 6.5.4. + +## Implementation + +Optional. + +## 8.65 Remaining PIN retries +CPINR + +**Table 8.65-1: +CPINR action command syntax** + +| Command | Possible response(s) | +|---------------------|----------------------| +| +CPINR[=<sel_code>] | +CME ERROR: <err> | +| +CPINR=? | | + +## Description + +Execution command cause the MT to return the number of remaining PIN retries for the MT passwords with intermediate result code +CPINR: <code>, <retries>[, <default\_retries>] for standard PINs and +CPINRE: <ext\_code>, <retries>[, <default\_retries>] for manufacturer specific PINs. One line with one intermediate result code is returned for every <code> or <ext\_code> selected by <sel\_code>. + +When execution command is issued without the optional parameter <sel\_code>, intermediate result codes are returned for all <code>s and <ext\_code>s. + +In the intermediate result codes, the parameter <default\_retries> is an optional (manufacturer specific) parameter, per <code> and <ext\_code>. + +Refer clause 9.2 for possible <err> values. + +## Defined values + +<retries>: integer type. Number of remaining retries per PIN. + +<default\_retries>: integer type. Number of default/initial retries per PIN. + +<code>: Type of PIN. All values listed under the description of the AT+CPIN command, <code> parameter, except 'READY'. + +<ext\_code>: Extended, manufacturer specific codes. + +<sel\_code>: String type. Same values as for the <code> and <ext\_code> parameters. These values are strings and shall be indicated within double quotes. It is optional to support wildcard match by '\*', meaning match any (sub-)string. + +Example: AT+CPINR="SIM\*" will return the lines: + +``` ++CPINR: SIM PIN,<retries>,<default_retries> ++CPINR: SIM PUK,<retries>,<default_retries> ++CPINR: SIM PIN2,<retries>,<default_retries> ++CPINR: SIM PUK2,<retries>,<default_retries> +``` + +Example: AT+CPINR="\*SIM\*" will additionally return the lines: + +``` ++CPINR: PH-SIM PIN,<retries>,<default_retries> ++CPINR: PH-FSIM PIN,<retries>,<default_retries> ++CPINR: PH-FSIM PUK,<retries>,<default_retries> +``` + +## Implementation + +Optional. + +## 8.66 Set card slot +CSUS + +**Table 8.66-1: +CSUS parameter command syntax** + +| Command | Possible response(s) | +|---------------------|-------------------------------------------| +| +CSUS=[<card slot>] | +CME ERROR: <err> | +| +CSUS? | +CSUS: <card slot> | +| +CSUS=? | +CSUS: (number of supported <card slot>s) | + +## Description + +When a MT is equipped with multiple card slots, the set command directs the MT to select the SIM/UICC card installed in the indicated card slot in all future actions that require the use of SIM/UICC. + +If this command is issued when a SIM/UICC is active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +Read command returns the currently selected card slot. + +Test command returns the number of card slots in the MT as a compound value. + +The numbering of card slots is implementation dependent. + +## Defined values + +<card slot>: integer type. + +- 0 the SIM/UICC card installed in card slot 0 +- 1 the SIM/UICC card installed in card slot 1 +- 2 the SIM/UICC card installed in card slot 2 +- 3 the SIM/UICC card installed in card slot 3 + +## Implementation + +Optional. + +## 8.67 Emergency numbers +CEN + +**Table 8.67-1: +CEN parameter command syntax** + +| Command | Possible response(s) | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CEN=<reporting>] | | +| +CEN? | +CEN1: <reporting>[, <mcc>, <mnc>]<br><CR><LF> [+CEN2: <cat>, <number>]<br>[<CR><LF>+CEN2: <cat>, <number>]<br>[...]]]<br>[<CR><LF>+CEN3: <validity>]<br><CR><LF> [+CEN4: <number-ext>, <sub-services>]<br>[<CR><LF>+CEN4: <number-ext>, <sub-services>]<br>[...]]] | +| +CEN=? | +CEN: (list of supported <reporting>s) | + +### Description + +This command allows for reading and dynamical reporting of local emergency numbers and categories or emergency service URNs as received from the network in the Emergency Number List IE (see 3GPP TS 24.008 [8]) and the Extended Emergency Number List IE (see 3GPP TS 24.301 [83]). The emergency numbers are not necessarily received for the same <mcc> and <mnc> as currently registered to. + +Read command returns one line of intermediate result code +CEN1: <reporting>, <mcc>, <mnc> with the current <reporting> setting and the Mobile Country Code <mcc> and Mobile Network Code <mnc>. Then follows zero or more occurrences of the local emergency number received in the Emergency Number List IE with intermediate result code +CEN2: <cat>, <number>. This is followed by one line of intermediate result code +CEN3: <validity> with the current <validity> setting. This is followed by zero or more occurrences of the local emergency number received in the Extended Emergency Number List IE and an associated sub-service with intermediate result code +CEN4: <number-ext>, <sub-service>. + +Set command enables reporting of local emergency numbers received from the network with unsolicited result codes equal to the intermediate result codes of the read form of the command. + +Test command returns values supported as a compound value. + +### Defined values + +<reporting>: integer type. Enables and disables reporting of local emergency numbers received from the network. + +0 Disable reporting + +1 Enable reporting + +<mcc>: integer type. A three-digit value indicating mobile country code as defined in ITU-T Recommendation E.212 [10] Annex A. + +<mnc>: integer type. A three-digit value indicating the mobile network code. + +<cat>: integer type. A bitmap indicating the Emergency Service Category Value according to 3GPP TS 24.008 [8] table 10.5.135d. + +<number>: String type. Representing a local emergency number from the list received in the Emergency Number List IE in 3GPP TS 24.008 [8] clause 10.5.3.13. The <number> is encoded with one digit per character and is applicable to the country indicated by <mcc>. + +<validity>: integer type. Indicated validity of the local emergency number associated sub-service from the list received in the Extended Emergency Number List IE in 3GPP TS 24.301 [83] clause 9.9.3.37A. + +- 0 Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received +- 1 Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received + +<number-ext>: String type. Representing a local emergency number from the list received in the Extended Emergency Number List IE in 3GPP TS 24.301 [83] clause 9.9.3.37A. The <number-ext> is encoded with one digit per character and is applicable to the country indicated by <mcc>. + +<sub-service>: String type. Representing an associated sub-service to the <number-ext>. The <sub-service> is encoded in the GSM 7 bit default alphabet and is applicable to the country indicated by <mcc> or to the PLMN indicated by the <mcc> and <mnc>. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +### 8.68 Availability for voice calls with IMS +CAVIMS + +**Table 8.68-1: +CAVIMS parameter command syntax** + +| Command | Possible response(s) | +|-------------------|---------------------------------------| +| +CAVIMS=[<state>] | | +| +CAVIMS? | +CAVIMS: <state> | +| +CAVIMS=? | +CAVIMS: (list of supported <state>s) | + +#### Description + +Set command informs the MT whether the UE is currently available for voice calls with the IMS (see 3GPP TS 24.229 [89]). The information can be used by the MT to determine "IMS voice not available" as defined in 3GPP TS 24.301 [83] and 3GPP TS 24.501 [161], and for mobility management for IMS voice termination, see 3GPP TS 24.008 [20]. + +Read command returns the UEs IMS voice call availability status stored in the MT. + +Test command returns supported values as a compound value. + +#### Defined values + +<state>: integer type. The UEs IMS voice call availability status. + +- 0 Voice calls with the IMS are not available +- 1 Voice calls with the IMS are available + +#### Implementation + +Optional. + +### 8.69 Extended signal quality +CESQ + +**Table 8.69-1: +CESQ action command syntax** + +| Command | Possible response(s) | +|---------|-----------------------------------------------------------------------------------------------------------------| +| +CESQ | +CESQ: <rxlev>, <ber>, <rscp>, <ecno>, <rsrq>, <rsrp>, <ss_rsrq>, <ss_rsrp>, <ss_sinr><br><br>+CME ERROR: <err> | + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CESQ=? | +CESQ: (list of supported <rxlev>s) , (list of supported <ber>s) , (list of supported <rscp>s) , (list of supported <ecno>s) , (list of supported <rsrq>s) , (list of supported <rsrp>s) , (list of supported <ss_rsq>s) , (list of supported <ss_rsrp>s) , (list of supported <ss_sinr>s) | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +Execution command returns received signal quality parameters. If the current serving cell is not a GERAN cell, <rxlev> and <ber> are set to value 99. If the current serving cell is not a UTRA FDD or UTRA TDD cell, <rscp> is set to 255. If the current serving cell is not a UTRA FDD cell, <ecno> is set to 255. If the current serving cell is not an E-UTRA cell, <rsrq> and <rsrp> are set to 255. If the current serving cell is not an NR cell, <ss\_rsq>, <ss\_rsrp> and <ss\_sinr> are set to 255. + +Refer clause 9.2 for possible <err> values. + +Test command returns values supported as compound values. + +## Defined values + +<rxlev>: integer type, received signal strength level (see 3GPP TS 45.008 [20] clause 8.1.4). + +- 0 rssi < -110 dBm +- 1 -110 dBm $\leq$ rssi < -109 dBm +- 2 -109 dBm $\leq$ rssi < -108 dBm +- : : : : +- 61 -50 dBm $\leq$ rssi < -49 dBm +- 62 -49 dBm $\leq$ rssi < -48 dBm +- 63 -48 dBm $\leq$ rssi +- 99 not known or not detectable + +<ber>: integer type; channel bit error rate (in percent). + +- 0..7 as RXQUAL values in the table in 3GPP TS 45.008 [20] clause 8.2.4 +- 99 not known or not detectable + +<rscp>: integer type, received signal code power (see 3GPP TS 25.133 [95] clause 9.1.1.3 and 3GPP TS 25.123 [96] clause 9.1.1.1.3). + +- 0 rscp < -120 dBm +- 1 -120 dBm $\leq$ rscp < -119 dBm +- 2 -119 dBm $\leq$ rscp < -118 dBm +- : : : : +- 94 -27 dBm $\leq$ rscp < -26 dBm +- 95 -26 dBm $\leq$ rscp < -25 dBm +- 96 - 25 dBm $\leq$ rscp +- 255 not known or not detectable + +<ecno>: integer type, ratio of the received energy per PN chip to the total received power spectral density (see 3GPP TS 25.133 [95] clause). + +- 0 $E_c/I_o < -24$ dB +- 1 $-24$ dB $\leq E_c/I_o < -23.5$ dB +- 2 $-23.5$ dB $\leq E_c/I_o < -23$ dB +- : : : : +- 47 $-1$ dB $\leq E_c/I_o < -0.5$ dB +- 48 $-0.5$ dB $\leq E_c/I_o < 0$ dB +- 49 $0$ dB $\leq E_c/I_o$ +- 255 not known or not detectable + +<rsrq>: integer type, reference signal received quality (see 3GPP TS 36.133 [96] clause 9.1.7). + +- 0 $rsrq < -19.5$ dB +- 1 $-19.5$ dB $\leq rsrq < -19$ dB +- 2 $-19$ dB $\leq rsrq < -18.5$ dB +- : : : : +- 32 $-4$ dB $\leq rsrq < -3.5$ dB +- 33 $-3.5$ dB $\leq rsrq < -3$ dB +- 34 $-3$ dB $\leq rsrq$ +- 255 not known or not detectable + +<rsrp>: integer type, reference signal received power (see 3GPP TS 36.133 [96] clause 9.1.4). + +- 0 $rsrp < -140$ dBm +- 1 $-140$ dBm $\leq rsrp < -139$ dBm +- 2 $-139$ dBm $\leq rsrp < -138$ dBm +- : : : : +- 95 $-46$ dBm $\leq rsrp < -45$ dBm +- 96 $-45$ dBm $\leq rsrp < -44$ dBm +- 97 $-44$ dBm $\leq rsrp$ +- 255 not known or not detectable + +<ss\_rsrq>: integer type, synchronization signal based reference signal received quality (see 3GPP TS 38.133 [169] clause 10.1.11). + +- 0 $ss\_rsrq < -43$ dB +- 1 $-43$ dB $\leq ss\_rsrq < -42.5$ dB +- 2 $-42.5$ dB $\leq ss\_rsrq < -42$ dB +- : : : : +- 124 $18.5$ dB $\leq ss\_rsrq < 19$ dB +- 125 $19$ dB $\leq ss\_rsrq < 19.5$ dB +- 126 $19.5$ dB $\leq ss\_rsrq < 20$ dB + +255 not known or not detectable + +<ss\_rsrp>: integer type, synchronization signal based reference signal received power (see 3GPP TS 38.133 [169] clause 10.1.6). + +0 ss\_rsrp < -156 dBm + +1 -156 dBm $\leq$ ss\_rsrp < -155 dBm + +2 -155 dBm $\leq$ ss\_rsrp < -154 dBm + +: : : : + +125 -32 dBm $\leq$ ss\_rsrp < -31 dBm + +126 -31 dBm $\leq$ ss\_rsrp + +255 not known or not detectable + +<ss\_sinr>: integer type, synchronization signal based signal to noise and interference ratio (see 3GPP TS 38.133 [169] clause 10.1.16). + +0 ss\_sinr < -23 dB + +1 -23 dB $\leq$ ss\_sinr < -22.5 dB + +2 -22.5 dB $\leq$ ss\_sinr < -22 dB + +: : : : + +125 39 dB $\leq$ ss\_sinr < 39.5 dBm + +126 39.5 dB $\leq$ ss\_sinr < 40 dB + +127 40 dB $\leq$ ss\_sinr + +255 not known or not detectable + +### Implementation + +Optional. + +## 8.70 Primary notification event reporting +CPNER + +Table 8.70-1: +CPNER parameter command syntax + +| Command | Possible response(s) | +|----------------------|---------------------------------------------------------------| +| +CPNER=[<reporting>] | +CME ERROR: <err> | +| +CPNER? | +CPNER:<reporting><br>+CME ERROR: <err> | +| +CPNER=? | +CPNER: (list of supported <reporting>s)<br>+CME ERROR: <err> | + +### Description + +Set command enables and disables reporting of primary notification events when received from the network with unsolicited result code +CPNERU: <message\_identifier>, <serial\_number>, <warning\_type>. Primary notification events are used for public warning systems like ETWS (Earthquake and Tsunami Warning Systems). + +When <reporting>=1, duplicate primary notifications will be discarded by the UE. + +NOTE 1: The notification is considered a duplicate of the previous if it has equal <message\_identifier> and <serial\_number> and arrives from the same PLMN. A primary notification message stored to detect duplication is cleared automatically after three hours of not receiving any message. + +Read command returns the current settings. + +Test command returns supported values as a compound value. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<reporting>: integer type, controlling reporting of primary notification events + +- 0 Disable primary notification events. +- 1 Enable reporting of primary notification events without security information, unsolicited result code ++CPNERU: <message\_identifier>, <serial\_number>, <warning\_type>. + +NOTE 2: Provision of information for the digital signature authentication is referred to as "reporting of primary notification events with security information" in 3GPP TS 25.331 [74], 3GPP TS 36.331 [86] and 3GPP TS 23.041 [100]. This functionality is not fully implemented in this release, hence is not supported. + +<message\_identifier>: string type in hexadecimal character format. The parameter contains the message identifier (2 bytes) of the primary notification. For UTRAN see 3GPP TS 25.331 [74] clause 10.3.8.4.ea, for GERAN see 3GPP TS 23.041 [100] clause 9.4.1.3.2, for E-UTRAN see 3GPP TS 36.331 [86] clause 6.3.1 *SystemInformationBlockType10*, and for NG-RAN see 3GPP TS 38.331 [160] clause 6.3.1 *SystemInformationBlockType6*. + +<serial\_number>: string type in hexadecimal character format. The parameter contains the serial number (2 bytes) of the primary notification. For UTRAN see 3GPP TS 25.331 [74] clause 10.3.8.4.ea, for GERAN see 3GPP TS 23.041 [100] clause 9.4.1.3.2, for E-UTRAN see 3GPP TS 36.331 [86] clause 6.3.1 *SystemInformationBlockType10*, and for NG-RAN see 3GPP TS 38.331 [160] clause 6.3.1 *SystemInformationBlockType6*. + +<warning\_type>: string type in hexadecimal character format. The parameter contains the warning type (2 bytes) of the primary notification. For UTRAN see 3GPP TS 25.331 [74] clause 10.3.8.4.ea, for GERAN see 3GPP TS 23.041 [100] clause 9.4.1.3.2, for E-UTRAN see 3GPP TS 36.331 [86] clause 6.3.1 *SystemInformationBlockType10*, and for NG-RAN see 3GPP TS 38.331 [160] clause 6.3.1 *SystemInformationBlockType6*. + +#### Implementation + +Optional. + +## 8.71 IMS registration information +CIREG + +Table 8.71-1: +CIREG parameter command syntax + +| Command | Possible response(s) | +|--------------|---------------------------------------| +| +CIREG=[<n>] | +CME ERROR: <err> | +| +CIREG? | +CIREG: <n>, <reg_info>[, <ext_info>] | +| +CIREG=? | +CIREG: (list of supported <n>s) | + +#### Description + +The set command controls the presentation of an unsolicited result code +CIREGU: <reg\_info>[, <ext\_info>] when there is a change in the MT's IMS registration information. Refer clause 9.2 for possible <err> values. + +The read command returns <n>, that shows whether reporting is enabled or disabled, <reg\_info> that shows whether one or more of the public user identities are registered and optionally <ext\_info>, that shows the status of + +the MT's IMS capabilities. For <ext\_info>, all relevant values are always summarized and reported as a complete set of IMS capabilities in the unsolicited result code. + +The test command returns the supported values for <n> as a compound value. + +#### Defined values + +<n>: integer type. Enables or disables reporting of changes in the MT's IMS registration information. + +- 0 disable reporting. +- 1 enable reporting (parameter <reg\_info>). +- 2 enable extended reporting (parameters <reg\_info> and <ext\_info>). + +<reg\_info>: integer type. Indicates the IMS registration status. The UE is seen as registered as long as one or more of its public user identities are registered with any of its contact addresses, see 3GPP TS 24.229 [89]. + +- 0 not registered. +- 1 registered. + +<ext\_info>: numeric value in hexadecimal format. The value range is from 1 to FFFFFFFF. It is a sum of hexadecimal values, each representing a particular IMS capability of the MT. The MT can have IMS capabilities not covered by the below list. This parameter is not present if the IMS registration status is "not registered". + +- 1 RTP-based transfer of voice according to MMTEL, see 3GPP TS 24.173 [87]. This functionality can not be indicated if the UE is not available for voice over PS, see 3GPP TS 24.229 [89]. +- 2 RTP-based transfer of text according to MMTEL, see 3GPP TS 24.173 [87]. +- 4 SMS using IMS functionality, see 3GPP TS 24.341 [101]. +- 8 RTP-based transfer of video according to MMTEL, see 3GPP TS 24.173 [87]. + +The hexadecimal values 10, 20, 40 ... 80000 are reserved by the present document. + +Example: The parameter <ext\_info>=5 means that both RTP-based transfer of voice according to MMTEL and SMS using IMS functionality can be used. + +#### Implementation + +Optional. + +## 8.72 Availability for SMS using IMS +CASIMS + +**Table 8.72-1: +CASIMS parameter command syntax** + +| Command | Possible response(s) | +|-------------------|---------------------------------------| +| +CASIMS=[<state>] | | +| +CASIMS? | +CASIMS: <state> | +| +CASIMS=? | +CASIMS: (list of supported <state>s) | + +#### Description + +Set command informs the MT whether the UE is currently available for SMS using IMS (see 3GPP TS 24.229 [89]). In EPS, the information can be used by the MT to determine the need to remain attached for non-EPS services, as defined in 3GPP TS 24.301 [83]. In 5GS, the information can be used by the MT to determine whether to use SMS over IMS or SMS over NAS. + +Read command returns the UE's SMS using IMS availability status, as stored in the MT. + +Test command returns supported values as a compound value. + +### Defined values + +<state>: integer type. The UE's SMS using IMS availability status. + +- 0 SMS using IMS is not available +- 1 SMS using IMS is available + +### Implementation + +Optional. + +## 8.73 Monitor of current calls +CMCCS + +**Table 8.73-1: +CMCCS parameter command syntax** + +| Command | Possible response(s) | +|--------------|-------------------------------------------------------------------------------------| +| +CMCCS=[<n>] | <b>when <n>=1 and command successful:</b><br>+CMCCS: (list of supported <x>s) | +| +CMCCS? | +CMCCS: <n> | +| +CMCCS=? | +CMCCS: (list of supported <n>s) | + +### Description + +This command activates or deactivates a call monitoring function in the ME. When this function is activated in the ME, the ME informs about events for calls with unsolicited result codes. + +The purpose of the call monitoring function is to: + +- 1) gather relevant information for the detected calls in a TE; and +- 2) make it possible for the TE to display call state information for ongoing calls. + +The unsolicited result code +CMCCSI is used for basic call information. + ++CMCCSI: <ccidx>, <dir>, <neg\_status\_present>, <neg\_status>, <SDP\_md>, <cs\_mode>, <ccs status>, <mpty>, <number type>, <ton>, <number>, <exit type>, <exit cause> + +The unsolicited result code +CMCCSI is provided when <n>=2. For an originating call, the parameters <number type>, <ton> and <number> in +CMCCSI provide the number (line identity) information which has been dialled with +CDU or ATD. For a terminating call, the parameters <number type>, <ton> and <number> in +CMCCSI provide the number (line identity) information of the calling user. + +The unsolicited result codes +CMCCSS<x> / +CMCCSSEND are used for supplementary service related information. + +``` ++CMCCSS1: <ccidx>, <dir>, <service> +[+CMCCSS2: <number type>, <ton>, <number>] +[+CMCCSS3: <CLI_validity>] +[+CMCCSS4: <name>] +[+CMCCSS5: <subaddr>, <satype>] +[+CMCCSS6: <priority>] +[+CMCCSS7: <CUG_index>] +[+CMCCSS8: <eCNAM_meta>] ++CMCCSSEND +``` + +The unsolicited result codes +CMCCSS<x> / +CMCCSSEND are used for supplementary service related information and are reported when <n>=3. For every supplementary service related event, the unsolicited result codes +CMCCSS<x> shall be given in consecutive order, and the sequence of unsolicited result codes shall be terminated by +CMCCSSEND. + +It is manufacturer specific when and if this additional service reporting will be issued. Whenever a service event is to be reported using these unsolicited result codes, the codes +CMCCSS1 and +CMCCSSEND are mandatory. +CMCCSS1 contains essential information that is always needed (for example <ccidx>) and +CMCCSSEND indicates the end of this particular set of unsolicited result codes. The other unsolicited result codes (+CMCCSS2 to +CMCCSSn) are optional, intended to provide information related to a given service. E.g. for the supplementary service CNAP, the unsolicited result code +CMCCSS4 (containing <name>) may be issued. It is implementation specific which of the unsolicited result codes +CMCCSS<x> / +CMCCSSEND that are supported and provided to the TE. The unsolicited result codes should be provided to the TE as soon as the information is available in the ME. The parameters <nubertype>, <ton> and <number> in +CMCCSS2 are, if applicable, normally the line identity information that is related to the parameter <service>. + +NOTE 1: For situations where ringing is applicable, the unsolicited result codes +CMCCSS<x> / +CMCCSSEND are typically returned after the first RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. + +A subset of the information provided by the call monitoring function can be provided by the command +CLCCS. + +When the unsolicited result code +CMCCSI report that the <ccstatus>=1 (Idle), the call identification number is reset and the call identification number <ccidx> can be used by new calls. The logic for reuse of the parameter <ccidx> is implementation specific. + +Read command returns the current value of <n>. + +Test command returns the values supported as a compound value. + +#### Defined values + +<n>: integer type + +- 0 The call monitoring function is disabled +- 1 List the unsolicited result codes +CMCCSS<x> that are supported by the TE. The supported values for <x> are reported as a compound value, e.g. a TE supporting +CMCCSS1, +CMCCSS2 and +CMCCSS5 will report +CMCCS: (1, 2, 5) or +CMCCS: (1-2, 5) +- 2 The call monitoring function is enabled for basic call information (unsolicited result code +CMCCSI) +- 3 The call monitoring function is enabled for basic call information and supplementary service information (unsolicited result codes +CMCCSI and +CMCCSS<x> / +CMCCSSEND) + +<x>: integer type. <x> is the suffix in the unsolicited result codes +CMCCSS<x>. + +<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. The call identification number must not be reused until the unsolicited result code +CMCCSI has indicated that the <ccstatus>=1 (Idle). + +<dir>: integer type + +- 0 mobile originated (MO) call +- 1 mobile terminated (MT) call + +<neg\_status\_present>: integer type. Indicates whether parameter <neg\_status> has any valid information. + +- 0 No valid information in parameter <neg\_status>. Parameter <neg\_status> is set to zero. +- 1 Valid information in parameter <neg\_status>. + +<neg\_status>: integer type as defined in the +CCMD command. + +- 0 The parameter <neg\_status> has no valid content. Parameter <SDP\_md> is set to an empty string (""). +- 1 The <SDP\_md> parameter describes the active media in the call. +- 2 The <SDP\_md> parameter describes a proposed but not yet active new set of media for the call. +- 3 A proposed new set of media for the call was accepted by the remote party. The <SDP\_md> parameter describes the accepted media by the remote party. The accepted media can be same as proposed new set of media or a subset of proposed media. +- 4 A proposed new set of media for the call was rejected by the remote party. The <SDP\_md> parameter will be set to an empty string (""). + +<SDP\_md>: string type represented with IRA characters. Media description as per the +CDEFMP command. This parameter shall not be subject to conventional character conversion as per +CSCS. This parameter will be an empty string ("" if the call has no multimedia content. + +<cs\_mode>: integer type (bearer/teleservice). Applicable to CS calls only. + +- 0 no relevant information about bearer/teleservice +- 1 voice +- 2 data +- 3 fax +- 4 voice followed by data, voice mode +- 5 alternating voice/data, voice mode +- 6 alternating voice/fax, voice mode +- 7 voice followed by data, data mode +- 8 alternating voice/data, data mode +- 9 alternating voice/fax, fax mode +- 255 unknown + +<ccstatus>: integer type Indicating the state of the call. + +- 1 Idle +- 2 Calling (MO); the call setup has been started +- 3 Connecting (MO); the call is in progress +- 4 Alerting (MO); an alert indication has been received +- 5 Alerting (MT); an alert indication has been sent +- 6 Active; the connection is established +- 7 Released; an outgoing (MO) call is released. +- 8 Released; an incoming (MT) call is released +- 9 User busy +- 10 User determined user busy +- 11 Call waiting (MO) + +12 Call waiting (MT) + +13 Call hold (MO) + +14 Call hold (MT) + +<empty>: integer type + +- 0 call is not one of multiparty (conference) call parties +- 1 call is one of multiparty (conference) call parties + +<nubertype>: integer type. Indicating type of information in parameter <number>. + +- 0 No valid information in parameter <number>. <number> shall then be set to empty string (""). +- 1 Number in <number> according to URI including the prefix specifying the URI type (see command +CDU). Parameter <ton> has no relevant information and is set to zero. +- 2 Number in <number> according to one of the formats supported by 3GPP TS 24.008 [8] clause 10.5.4.7) + +<ton>: type of number in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). The parameter is also set to zero when it has no meaningful content, e.g. when <nubertype>=1. + +<number>: string type phone number in format specified by <nubertype>. The used character set should be the one selected with command select TE character set +CSCS. When no number is available, <number> shall be set to empty string (""). + +<exittype>: integer type. Indicating type of information in parameter <exitcause>. + +- 0 No valid information in parameter <exitcause> +- 1 Cause in <exitcause> according to 3GPP TS 24.008 [8], Annex H +- 2 Cause in <exitcause> according to 3GPP TS 24.229 [89], Annex A.2.1.4.1 + +<exitcause>: integer type. Additional information provided if relevant. If there is no relevant cause to report, or if <exittype>=0 the exitcause is set to 0 (<exitcause>=0). + +<service>: integer type. Indication of the indicated (supplementary) service. It is vendor specific which of the services that are provided. The related unsolicited result codes +CMCCSS<x> are provided as applicable for a given <service>, e.g. the +CMCCSS5: <subaddr>, <satype> can be omitted when it is not relevant for the service, but can also be omitted if this information is not provided for a relevant service or if a vendor does not support parameters <subaddr> and <satype>. + +- 0 No service +- 1 Originating identification presentation – CLIP / OIP, refer 3GPP TS 22.081 [3] and 3GPP TS 24.607 [119] +CLIP / OIP specific information can be provided in: ++CMCCSI (in parameters <nubertype>, <ton> and <number>) +Additional CLIP / OIP specific information can be provided in: ++CMCCSS1 (in parameter <service>) ++CMCCSS3 (in parameter <CLI\_validity>, typically used when no <number> is available) ++CMCCSS5 (in parameters <subaddr> and <satype>, when applicable) +- 2 Originating identification restriction – CLIR / OIR, refer 3GPP TS 22.081 [3] and 3GPP TS 24.607 [119] +- 3 Terminating identification presentation – COLP / TIP, refer 3GPP TS 22.081 [3] and 3GPP TS 24.608 [120] +COLP / TIP specific information can be provided in: ++CMCCSI (in parameters <nubertype>, <ton> and <number>) +Additional COLP / TIP specific information can be provided in: ++CMCCSS1 (in parameter <service>) ++CMCCSS5 (in parameters <subaddr> and <satype>, when applicable) + +- 4 Terminating identification restriction – COLR / TIR, refer 3GPP TS 22.081 [3] and 3GPP TS 24.608 [120] +- 5 Called line presentation – CDIP +Additional CDIP specific information can be provided in: + - +CMCCSS1 (in parameter <service>) + - +CMCCSS2 (in parameters <nubertype>, <ton> and <number>) + - +CMCCSS5 (in parameters <subaddr> and <satype>, when applicable) + +NOTE 2: The command +CDIP does not explicitly specify what "multiple called numbers" it is intended to support. +CMCCS can therefore not be more specific. The CDIP service in +CMCCS is therefore intended for manufacturers who already have chosen a manufacturer specific way to support +CDIP and needs to extend or replace +CDIP with support for SIP URIs. For manufacturers who do not already support the command +CDIP, the usage of the CDIP service in +CMCCS is deprecated. + +- 6 Calling name presentation – CNAP, refer 3GPP TS 22.096 [93] +Additional CNAP specific information can be provided in: + - +CMCCSS1 (in parameter <service>) + - +CMCCSS4 (in parameter <name>) +- 7 Communication deflection – CD, refer 3GPP TS 22.072 [31] and 3GPP TS 24.604 [132] +- 8 Communication forwarding unconditional – CFU, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 9 Communication forwarding on busy user – CFB, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 10 Communication forwarding on no reply – CFNR, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 11 Communication forwarding on subscriber not reachable – CFNRc, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132] +- 12 Communication forwarding on not logged-in – CFNL, refer 3GPP TS 24.604 [132] +- 13 Communication diversion notification – CDIVN, refer 3GPP TS 24.604 [132] +- 14 Communication waiting – CW, refer 3GPP TS 22.083 [5] and 3GPP TS 24.615 [137] +Additional CW specific information can be provided in: + - +CMCCSS1 (in parameter <service>) + - +CMCCSS6 (in parameter <priority>) +- 15 Communication hold – HOLD, refer 3GPP TS 22.083 [5] and 3GPP TS 24.610 [135] +- 16 Conference – MPTY / CONF, refer 3GPP TS 22.084 [22] and 3GPP TS 24.605 [133] +- 17 Explicit communication transfer – ECT, refer 3GPP TS 22.091 [30] and 3GPP TS 24.629 [139] +- 18 Completion of communications to busy subscriber – CCBS, refer 3GPP TS 22.093 [123] and 3GPP TS 24.642 [140] +- 19 Completion of communications by no reply – CCNR, refer 3GPP TS 24.642 [140] +- 20 Communication barring of all outgoing calls – BAOC, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136] +- 21 Communication barring of all international outgoing calls except those directed to the home PLMN country – BOIC-exHC, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136] +- 22 Communication barring of all incoming calls – BAIC, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136] +- 23 Communication barring of incoming calls when roaming outside the home PLMN country – BIC-Roam, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136] +- 24 All barring services, refer 3GPP TS 22.030 [19] +- 25 All outgoing barring services, refer 3GPP TS 22.030 [19] +- 26 All incoming barring services, refer 3GPP TS 22.030 [19] + +- 27 Anonymous communication rejection – ACR, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136] +- 28 Advice of charge – AOC, refer 3GPP TS 22.085 [21] and 3GPP TS 24.654 [121] +- 29 Message waiting indication – MWI, refer 3GPP TS 24.606 [134] +- 30 Malicious communication identification, all outgoing calls – MCID, refer 3GPP TS 24.616 [138] +- 31 Unstructured supplementary service data – USSD, refer 3GPP TS 22.090 [23] and 3GPP TS 24.390 [131] +- 32 Customized alerting tones – CAT, refer 3GPP TS 24.182 [127] +- 33 Customized ringing signal – CRS, refer 3GPP TS 24.183 [128] +- 34 Flexible alerting – FA, refer 3GPP TS 24.239 [129] +- 35 Personal network management – PNM, refer 3GPP TS 24.259 [130] +- 36 User-to-user signalling service 1 – UUS 1, refer 3GPP TS 22.087 [58] and 3GPP TS 24.229 [89] +- 37 User-to-user signalling service 2 – UUS 2, refer 3GPP TS 22.087 [58] +- 38 User-to-user signalling service 3 – UUS 3, refer 3GPP TS 22.087 [58] +- 39 All user-to-user signalling services, refer 3GPP TS 22.087 [58] +- 40 Follow me – FM, refer 3GPP TS 22.094 [124] +- 41 Multiple subscriber profile – MSP, refer 3GPP TS 22.097 [125] +- 42 Multicall – MC, refer 3GPP TS 22.135 [126] +- 43 enhanced multi-level precedence and pre-emption service – eMLPP, refer 3GPP TS 22.067 [54] +- 44 Closed user group – CUG, refer 3GPP TS 22.085 [21] and 3GPP TS 24.654 [121] + - Additional CUG specific information can be provided in: + - +CMCCSS1 (in parameter <service>) + - +CMCCSS7 (in parameter <CUG\_index>) +- 45 enhanced calling name – eCNAM, refer to 3GPP TS 24.196 [163] and 3GPP TS 22.173 [164]. + - eCNAM specific information can be provided in: + - +CMCCSS1 (in parameter <service>) + - Additional eCNAM specific information can be provided in: + - +CMCCSS4 (in parameter <name>) + - +CMCCSS8 (in parameter <eCNAM\_meta>, when available) + +256 - 511 Reserved for vendor specific services + +<CLI\_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). The parameter is not relevant for MO call types. + +- 0 CLI valid +- 1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user") +- 2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service") +- 3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone") +- 4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable") + +When CLI is not available (<CLI\_validity>=2, <CLI\_validity>=3 or <CLI\_validity>=4), <number> shall be an empty string ("") and <ton> value will not be significant. The parameter <number> will be set to 0. Nevertheless, TA may return the recommended value 128 for <ton> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7). + +When CLI has been withheld by the originator, (<CLI\_validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <ton> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. The parameter <number> shall be set as applicable. + +<name>: string type up to 80 characters long string containing the calling name. + +<subaddr>: string type subaddress of format specified by <stype>. + +<stype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8) or RFC 4715 [122] appendix A. + +<priority>: integer type indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54]. + +<CUG\_index>: string type. The parameter sets the CUG index for this <CUG\_pointer>. + +"0" ... "32767" CUG index + +"" no CUG index, indicated by empty string. Preferential CUG taken from subscriber data. + +<eCNAM\_meta>: string type up to 1000 characters long. The string contains additional information about the caller (such as language, location or results of analytics and verification of the caller – refer to 3GPP TS 24.196 [158] clause 4.5.3.3 about additional information in Call-Info header fields). + +NOTE 3: The eCNAM metadata can also include graphics (e.g., logos and symbols). Manufacturer specific commands are needed to upload such information. + +## Implementation + +Optional. + +## 8.74 List of current calls +CLCCS + +Table 8.74-1: +CLCCS action command syntax + +| Command | Possible response(s) | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CLCCS[=<ccidx>] | [+CLCCS: <ccid1>,<dir>,<neg_status_present>,<neg_status>,<SDP_md>,<cs_mode>,<ccstatus>,<mpty>,<number>,<ton>,<number>[,<priority_present>,<priority>[,<CLI_validity_present>,<CLI_validity>]]]<br>[<CR><LF>+CLCCS: <ccid2>,<dir>,<neg_status_present>,<neg_status>,<SDP_md>,<cs_mode>,<ccstatus>,<mpty>,<number>,<ton>,<number>[,<priority_present>,<priority>[,<CLI_validity_present>,<CLI_validity>]]]<br>[...]]]<br>+CME ERROR: <err> | +| +CLCCS=? | | + +## Description + +Returns a list of current calls controlled by the MT for which the <ccidx> is allocated. The information returned is a subset of the information provided by the call monitoring function, see +CMCCS and its unsolicited result codes + ++CMCCSI and +CMCCSS<x> / +CMCCSSEND. For an originating call, the parameters <number type>, <ton> and <number> provide the number (line identity) information which has been dialled with +CDU or ATD. For a terminating call, the parameters <number type>, <ton> and <number> provide the number (line identity) information of the calling user. If no particular <ccidx> is included in the request, data for all allocated <ccidx> are returned. If the command succeeds but no <ccidx> is allocated, no information response is sent to the TE. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<ccidx>: integer type. Call identification number (see 3GPP TS 22.030 [19] clause 6.5.5.1). This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. + +NOTE 1: The restrictions and limitations of the call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1 and 3GPP TS 22.084 [22] do not apply. + +NOTE 2: When +CMCCS is supported, the call identification number is not reset until the unsolicited result code +CMCCSI has indicated that the <ccstatus>=1 (Idle). + +<dir>: integer type + +- 0 mobile originated (MO) call +- 1 mobile terminated (MT) call + +<neg\_status\_present>: integer type. Indicates whether parameter <neg\_status> has any valid information. + +- 0 No valid information in parameter <neg\_status>. Parameter <neg\_status> is set to zero. +- 1 Valid information in parameter <neg\_status>. + +<neg\_status>: integer type as defined in the +CCMMD command. + +- 0 The parameter <neg\_status> has no valid content. Parameter <SDP\_md> is set to an empty string (""). +- 1 The <SDP\_md> parameter describes the active media in the call. +- 2 The <SDP\_md> parameter describes a proposed but not yet active new set of media for the call. +- 3 A proposed new set of media for the call was accepted by the remote party. The <SDP\_md> parameter describes the active media in the call (if any). +- 4 A proposed new set of media for the call was rejected by the remote party. The <SDP\_md> parameter describes the active media in the call (if any). + +<SDP\_md>: string type represented with IRA characters. SDP media description as per the +CDEFMP command. This parameter shall not be subject to conventional character conversion as per +CSCS. This parameter will be an empty string ("") if the call has no multimedia content. + +<cs\_mode>: integer type (bearer/teleservice) + +- 0 no relevant information about bearer/teleservice +- 1 voice +- 2 data +- 3 fax +- 4 voice followed by data, voice mode +- 5 alternating voice/data, voice mode +- 6 alternating voice/fax, voice mode + +- 7 voice followed by data, data mode +- 8 alternating voice/data, data mode +- 9 alternating voice/fax, fax mode +- 255 unknown + +<ccstatus>: integer type. Indicating the state of the call. + +- 1 Idle +- 2 Calling (MO); the call setup has been started +- 3 Connecting (MO); the call is in progress +- 4 Alerting (MO): an alert indication has been received +- 5 Alerting (MT); an alert indication has been sent +- 6 Active; the connection is established +- 7 Released; an outgoing (MO) call is released. +- 8 Released; an incoming (MT) call is released +- 9 User Busy +- 10 User Determined User Busy +- 11 Call Waiting (MO) +- 12 Call Waiting (MT) +- 13 Call Hold (MO) +- 14 Call Hold (MT) + +<mparty>: integer type + +- 0 call is not one of multiparty (conference) call parties +- 1 call is one of multiparty (conference) call parties + +<nubertype>: integer type. Indicating type of information in parameter <number>. + +- 0 No valid information in parameter <number> +- 1 Number in <number> according to URI including the prefix specifying the URI type (see command +CDU). Parameter <ton> has no relevant information and is set to zero. +- 2 Number in <number> according to one of the formats supported by 3GPP TS 24.008 [8] clause 10.5.4.7) + +<ton>: type of number in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). The parameter is also set to zero when it has no meaningful content, e.g. when <nubertype>=1. + +<number>: string type phone number in format specified by <nubertype>. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<priority\_present>: integer type. Indicates whether parameter <priority> has any valid information. + +- 0 No valid information in parameter <priority>. Parameter <priority> is set to zero. +- 1 Valid information in parameter <priority>. + +<priority>: integer type parameter indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54]. + +<CLI\_validity\_present>: integer type. Indicates whether parameter <CLI\_validity> has any valid information. + +- 0 No valid information in parameter <CLI\_validity>. Parameter <priority> is set to zero. +- 1 Valid information in parameter <CLI\_validity>. + +<CLI\_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). The parameter is not relevant for MO call types. + +- 0 CLI valid +- 1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user") +- 2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service") +- 3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone") +- 4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable") + +When CLI is not available (<CLI\_validity>=2, <CLI\_validity>=3 or <CLI\_validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. The parameter <nubertype> will be set to 0. Nevertheless, TA may return the recommended value 128 for <ton> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7). + +When CLI has been withheld by the originator, (<CLI\_validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. The parameter <nubertype> shall be set as applicable. + +## Implementation + +Optional. Recommended when +CHLD command is implement. + +This command supports all types of numbers (including SIP URIs) and can replace +CLCC. + +## 8.75 Supported radio accesses +CSRA + +**Table 8.75-1: +CSRA parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CSRA=<GERAN-TDMA>, <UTRAN-FDD>, <UTRAN-TDD-LCR>, <UTRAN-TDD-HCR>, <UTRAN-TDD-VHCR>, <E-UTRAN-FDD>, <E-UTRAN-TDD>, <NR-FDD>, <NR-TDD> | +CME ERROR: <err> | +| +CSRA? | +CSRAC: <GERAN-TDMA>, <UTRAN-FDD>, <UTRAN-TDD-LCR>, <UTRAN-TDD-HCR>, <UTRAN-TDD-VHCR>, <E-UTRAN-FDD>, <E-UTRAN-TDD>, <NR-FDD>, <NR-TDD><br><br><CR><LF>+CSRAA: <GERAN-TDMA>, <UTRAN-FDD>, <UTRAN-TDD-LCR>, <UTRAN-TDD-HCR>, <UTRAN-TDD-VHCR>, <E-UTRAN-FDD>, <E-UTRAN-TDD>, <NR-FDD>, <NR-TDD><br><br>+CME ERROR: <err> | + +| | | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CSRA=? | +CSRA: (indication of supported <GERAN-TDMA>s) , (indication of supported <UTRAN-FDD>s) , (indication of supported <UTRAN-TDD-LCR>s) , (indication of supported <UTRAN-TDD-HCR>s) , (indication of supported <UTRAN-TDD-VHCR>s) , (indication of supported <E-UTRAN-FDD>s) , (indication of supported <E-UTRAN-TDD>s) , (indication of supported <NR-FDD>s) , (indication of supported <NR-TDD>s) )<br><br>+CME ERROR: <err> | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +Set command is used to configure the availability of the radio accesses inherently supported by the MT. E.g. in a GSM-only environment, other radio access technologies could be disabled to reduce power-consumption. Settings are persistent over a power-cycle. It is not supported to set all parameters to indicate "Radio access is disabled", this will cause the MT to return ERROR. +CSRA only configures the requested parameters; no change in the transmit and receive RF circuits takes place by using +CSRA. The actual execution of the configuration is obtained by using +CFUN=128. + +Read command returns two lines of information text with two distinct prefixes: + +- a line prefixed with +CSRAC: displaying the currently configured +CSRA settings. These values are not activated until +CFUN=128 is executed, and this line does therefore not necessarily reflect the RATs currently activated on the radio interface; and +- a line prefixed with +CSRAA: displaying the RATs currently active on the radio interface. + +Read command returns the current settings in the MT. + +Refer clause 9.2 for possible <err> values. + +Test command returns values supported by the MT as compound values. The returned values do not reflect network capabilities. + +## Defined values + +<GERAN-TDMA>: integer type. Indicates usage of radio access of type GERAN TDMA, see 3GPP TS 45.001 [146]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<UTRAN-FDD>: integer type. Indicates usage of radio access of type UTRAN FDD, see 3GPP TS 25.212 [144]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<UTRAN-TDD-LCR>: integer type. Indicates usage of radio access of type UTRAN 1.28 Mcps TDD low chip rate (TD-SCDMA), see 3GPP TS 25.102 [143]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<UTRAN-TDD-HCR>: integer type. Indicates usage of radio access of type UTRAN 3.84 Mcps TDD high chip rate, see 3GPP TS 25.102 [143]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<UTRAN-TDD-VHCR>: integer type. Indicates usage of radio access of type UTRAN 7.68 Mcps TDD very high chip rate, see 3GPP TS 25.102 [143]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<E-UTRAN-FDD>: integer type. Indicates usage of radio access of type E-UTRAN FDD, see 3GPP TS 36.300 [145]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<E-UTRAN-TDD>: integer type. Indicates usage of radio access of type E-UTRAN TDD, see 3GPP TS 36.300 [145]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<NR-FDD>: integer type. Indicates usage of radio access of type NR-FDD, see 3GPP TS 38.300 [159]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +<NR-TDD>: integer type. Indicates usage of radio access of type NR-TDD, see 3GPP TS 38.300 [159]. The initial value is manufacturer specific. + +- 0 Radio access is disabled +- 1 Radio access is enabled + +### Implementation + +Optional. Mandatory when +CFUN supports <fun>=128. + +## 8.76 Circuit switched fallback +CCSFB + +**Table 8.76-1: +CCSFB parameter command syntax** + +| Command | Possible response(s) | +|--------------|----------------------------------| +| +CCSFB=[<n>] | +CME ERROR: <err> | +| +CCSFB? | +CCSFB: <n> | +| +CCSFB=? | +CCSFB: (list of supported <n>s) | + +### Description + +The set command is used to control circuit switched fallback (CSFB) operation. Reporting of CSFB related CS paging requests can be switched on or off. After reporting the command can be used to accept or reject the CSFB call. The command can also be used to control automatic acceptance/rejection of CSFB calls. Refer clause 9.2 for possible <err> values. + +CS paging requests are reported with unsolicited result code +CCSFBU in the format: + ++CCSFBU: <number type>, <ton>, <number>[, <ss\_code>[, <lcs\_indicator>[, <lcs\_client\_id entity>]]] + +NOTE 1: The command +CCSFB applies to connected mode. It does not apply to idle mode. + +Read command returns the current value of <n>. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type. + +- 0 disable reporting of CSFB related CS paging requests and disable automatic acceptance/rejection of CSFB calls. +- 1 enable reporting of CSFB related CS paging requests and disable automatic acceptance/rejection of CSFB calls. +- 2 enable reporting of CSFB related CS paging requests and enable automatic acceptance of CSFB calls. +- 3 enable reporting of CSFB related CS paging requests and enable automatic rejection of CSFB calls. +- 4 disable reporting of CSFB related CS paging requests and enable automatic acceptance of CSFB calls. +- 5 disable reporting of CSFB related CS paging requests and enable automatic rejection of CSFB calls. +- 6 accept CSFB call. This value can be used only after having received the unsolicited result code +CCSFB when automatic acceptance/rejection of CSFB calls has been disabled. +- 7 reject CSFB call. This value can be used only after having received the unsolicited result code +CCSFB when automatic acceptance/rejection of CSFB calls has been disabled. + +NOTE 2: The values <n>=6 and <n>=7 will not be reported by +CCSFB? as these values are not associated with any MT state. + +<numbertype>: integer type. Indicating type of information in parameter <number>. + +- 0 No valid information in parameter <number>. <number> shall then be set to empty string (""). +- 1 Number in <number> according to URI including the prefix specifying the URI type (see command +CDU). Parameter <ton> has no relevant information and is set to zero. +- 2 Number in <number> according to one of the formats supported by 3GPP TS 24.008 [8] clause 10.5.4.7. + +NOTE 3: In +CCSFB, the parameter <numbertype> can have value 2 only. + +<ton>: type of number in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). The parameter is also set to zero when it has no meaningful content, e.g. when <numbertype>=1. + +<number>: string type phone number in format specified by <numbertype>. The used character set should be the one selected with command select TE character set +CSCS. When no number is available, <number> shall be set to empty string (""). + +<ss\_code>: integer type. SS code (refer 3GPP TS 24.301 [83] clause 9.9.3.39). + +<lcs\_indicator>: integer type. LCS indicator value (refer 3GPP TS 24.301 [83] clause 9.9.3.40). + +<lcs\_client\_identity>: string type. LCS client identity information in hexadecimal format (refer 3GPP TS 24.301 [83] clause 9.9.3.41). + +#### Implementation + +Optional. + +## 8.77 Reading coverage enhancement status +CRCES + +**Table 8.77-1: +CRCES action command syntax** + +| Command | Possible Response(s) | +|----------|---------------------------------| +| +CRCES | +CRCES: <Act>, <CE_level>, <CC> | +| +CRCES=? | | + +### Description + +This command returns the coverage enhancement status of the MT. The terminal can consider the coverage enhancement status prior to deciding to transmit data (see e.g. clause 10.1.43). Depending on the coverage enhancement status the terminal can refrain from transmitting data. + +The coverage enhancement status is only provided by the MT if the access technology (mode) of the serving cell is E-UTRAN (WB-S1 mode), satellite E-UTRAN (WB-S1 mode) or satellite E-UTRAN (WB-S1 mode), EC-GSM-IoT, E-UTRAN (NB-S1 mode), E-UTRAN connected to a 5G CN (NB-N1 mode or WB-N1 mode). If the access technology (mode) of the serving cell is different, <Act>=0 is indicated. The access technology type parameter <Act>, should not be used in terminals capable of only one access technology. + +### Defined values + +<Act>: integer type; access technology (mode) of the serving cell. + +- 0 Serving cell has no coverage enhancement +- 1 E-UTRAN (WB-S1 mode or WB-N1 mode) +- 2 EC-GSM-IoT (A/Gb mode) (see NOTE 1) +- 3 E-UTRAN (NB-S1 mode or NB-N1 mode) (see NOTE 2) +- 4 satellite E-UTRAN (NB-S1 mode) (see NOTE 3) +- 5 satellite E-UTRAN (WB-S1 mode) + +NOTE 1: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT. + +NOTE 2: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode) or E-UTRAN (NB-N1 mode). + +NOTE 3: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving satellite cell supports NB-IoT, which corresponds to satellite E-UTRAN (NB-S1 mode). + +<CE\_level>: integer type; Coverage Enhancement (CE) level of the MT in the serving cell. Applicable only if <Act>=1 (E-UTRAN (WB-S1 mode or WB-N1 mode)) or <Act>=3 (E-UTRAN (NB-S1 mode or NB-N1 mode)). The Coverage Enhancement levels are defined and specified in 3GPP TS 36.331 [86]. + +- 0 Coverage Enhancement not used by the MT in the serving cell +- 1 Coverage Enhancement level 0 +- 2 Coverage Enhancement level 1 +- 3 Coverage Enhancement level 2 +- 4 Coverage Enhancement level 3 + +<CC>: integer type; Uplink Coverage Class (CC) of the MT in the serving cell. Applicable only if <Act>=2 (EC-GSM-IoT). The Coverage Classes are defined and specified in 3GPP TS 43.064 [13]. + +- 0 Coverage Class not used by the MT in the serving cell +- 1 Coverage Class 1 +- 2 Coverage Class 2 +- 3 Coverage Class 3 +- 4 Coverage Class 4 +- 5 Coverage Class 5 + +#### Implementation + +Optional. + +### 8.78 Application level measurement configuration +CAPPLEVMC + +**Table 8.78-1: +CAPPLEVMC parameter command syntax** + +| Command | Possible response(s) | +|------------------|--------------------------------------| +| +CAPPLEVMC=[<n>] | +CME ERROR: <err> | +| +CAPPLEVMC? | +CAPPLEVMC: <n> | +| +CAPPLEVMC=? | +CAPPLEVMC: (list of supported <n>s) | + +#### Description + +This command allows control of the application level measurement configuration according to 3GPP TS 25.331 [74] and 3GPP TS 36.331 [86]. The set command controls the presentation of the unsolicited result code +CAPPLEVMC: <app-meas\_service\_type>, <start-stop\_reporting>[, <app-meas\_config\_file\_length>, <app-meas\_config-file>] providing data for the configuration. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <n>. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type. Disable and enable presentation of the unsolicited result code +CAPPLEVMC to the TE. + +- 0 Disable presentation of the unsolicited result code +- 1 Enable presentation of the unsolicited result code + +<app-meas\_service\_type>: integer type. Contains the indication of what application that is target for the application level measurement configuration. + +- 1 QoE measurement collection for streaming services +- 2 QoE measurement collection for MTSI services + +<start-stop\_reporting>: integer type. Indicates the start and stop of the application level measurement reporting for the application indicated by the <app-meas\_service\_type>. + +- 0 start the application level measurement reporting +- 1 stop the application level measurement reporting + +<app-meas\_config\_file\_length>: integer type. Indicates the number of octets of the <app-meas\_config-file> parameter. + +<app-meas\_config-file>: string of octets. Contains the application level measurement configuration file for the application indicated by the <app-meas\_service\_type>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +## 8.79 Application level measurement report +CAPPLEVMR + +**Table 8.79-1: +CAPPLEVMR action command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------------------------------|----------------------| +| +CAPPLEVMR=<app-meas_service_type>,<app-meas_report_length>,<app-meas_report> | +CME ERROR: <err> | +| +CAPPLEVMR=? | | + +#### Description + +This command allows the MT to provide the application level measurement report according to 3GPP TS 25.331 [74] and 3GPP TS 36.331 [86]. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<app\_meas\_service\_type>: integer type. Contains the indication of what application that is providing the application level measurement report. + +- 1 QoE measurement collection for streaming services +- 2 QoE measurement collection for MTSI services + +<app-meas\_report\_length>: integer type. Indicates the number of octets of the <app-meas\_report> parameter. + +<app-meas\_report>: string of octets. Contains the application level measurement report for the application indicated by the <app-meas\_service\_type>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +## 8.80 Consent for requesting access to restricted local operator services +CCRLOS + +**Table 8.80-1: +CCRLOS parameter command syntax** + +| Command | Possible response(s) | +|-----------------------|-------------------------------------------| +| +CCRLOS=[<RLOS_cons>] | | +| +CCRLOS? | +CCRLOS: <RLOS_cons> | +| +CCRLOS=? | +CCRLOS: (list of supported <RLOS_cons>s) | + +### Description + +The set command allows the TE to indicate to the MT whether the user consents to requesting access to RLOS. The configuration of whether the user consents to requesting access to RLOS is kept by the MT until a new set command is received from the TE, i.e. it is not cleared upon the completion of an attach procedure for access to RLOS. + +The read command returns the current settings for the user's consent for requesting access to RLOS. + +The test command returns values supported as a compound value. + +### Defined values + +<RLOS\_cons>: integer type. Indicates the user's consent for requesting access to RLOS. + +- 0 user does not consent to requesting access to RLOS. +- 1 user consents to requesting access to RLOS. + +### Implementation + +Optional. This command is only applicable to UEs in E-UTRAN. + +## 8.81 EPS fallback status +CEPSFBS + +**Table 8.81-1: +CEPSFBS parameter command syntax** + +| Command | Possible Response(s) | +|----------------------|--------------------------------------------| +| +CEPSFBS=<reporting> | +CME ERROR: <err> | +| +CEPSFBS? | +CEPSFBS: <reporting>[, <stat>, <type>] | +| +CEPSFBS=? | +CEPSFBS: (list of supported <reporting>s) | + +### Description + +The set command controls the presentation of an unsolicited result code +CEPSFBS: <stat>, <type> when <reporting>=1 and there is a change due to EPS fallback(EPSFB) procedure triggered by the network. + +Read command returns <reporting> which indicates whether reporting of EPSFB status is enabled or disabled. When reporting is enabled, the parameters <stat> and <type> indicate the most recently received EPSFB status. When reporting is disabled, EPSFB status and EPSFB type are not provided. + +The test command returns values supported as a compound value. + +### Defined values + +<reporting>: integer type value. Disable and enable presentation of the unsolicited result code +CEPSFBS to the TE. + +- 0 Disable EPSFBS unsolicited result code. +- 1 Enable EPSFBS unsolicited result code +CEPSFBS: <stat>, <type>. + +<stat>: integer type; indicates the EPS fallback (EPSFB) status when MO/MT call is initiated in 5GS. + +- 0 5GS to EPS fallback started (applicable e.g. when handover (see NOTE 1) or redirection (see NOTE 2) is indicated by lower layers) +- 1 5GS to EPS fallback successful (applicable e.g. when change from 5GC to EPC is indicated by lower layers) (see NOTE 3) +- 2 5GS to EPS fallback failure (applicable e.g. when 5GS to EPS fallback was started but did not succeed in an implementation-specific time). + +<type>: integer type; indicates the EPSFB type. + +- 0 Handover (see NOTE 1) +- 1 Redirection (see NOTE 2) + +NOTE 1: 3GPP TS 38.331 [160] specifies e.g. *MobilityFromNRCommand*. + +NOTE 2: 3GPP TS 38.331 [160] specifies e.g. *RRRelease* indicating redirection to *eutra*. + +NOTE 3: 3GPP TS 36.331 [86] specifies e.g. *RRConnectionReconfiguration* with *handoverType* set to *fivegc-ToEPC*. + +### Implementation + +Optional. This command is only applicable to UEs supporting 5GS. + +## 8.82 Mobile originated location privacy setting +CMOLPS + +**Table 8.82-1: +CMOLPS parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| +CMOLPS=[<indication>[, <start_valid_time_period>, <end_valid_time_period>]] | +CME ERROR: <err> | +| +CMOLPS? | +CMOLPS: <indication>[, <start_valid_time_period>, <end_valid_time_period>]<br>+CME ERROR: <err> | +| +CMOLPS=? | +CMOLPS: (list of supported <indication>s) | + +### Description + +The set command is used to set the UE location privacy indication to allow or disallow location requests for the UE. The parameter <location> includes the UE location privacy indication to allow or disallow location requests for the UE. The parameters <start\_valid\_time\_period> and <end\_valid\_time\_period> include, respectively, the start time and the end time of the valid time period for the UE location privacy indication (see 3GPP TS 23.273 [173]). If these parameters are not defined, +CMOLPS=1 will disallow location requests without any time limitations. If <start\_valid\_time\_period> is provided but <end\_valid\_time\_period> is not provided, or <end\_valid\_time\_period> is provided but <start\_valid\_time\_period> is not provided, the MT shall return a +CME ERROR response. Refer clause 9.2 for possible <err> values. + +A special form of the command can be given as +CMOLPS=2. In this form, location requests will be allowed, and the value of the parameters <start\_valid\_time\_period> and <end\_valid\_time\_period> will be discarded. + +Read command returns the current settings. + +Test command returns the supported values as a compound value. + +### Defined values + +<indication>: integer type. Enables and disables allowing location requests for the UE. + +- 0 Location requests allowed. +- 1 Location requests disallowed. +- 2 Allow location requests and discard the parameters <start\_valid\_time\_period> and <end\_valid\_time\_period>. + +<start\_valid\_time\_period>: string type. This parameter contains the start time of the valid time period for the UE location privacy indication, encoded as specified in RFC 3339 [174]. + +<end\_valid\_time\_period>: string type. This parameter contains the end time of the valid time period for the UE location privacy indication, encoded as specified in RFC 3339 [174]. + +### Implementation + +Optional. + +## 8.83 Void + +## 8.84 Application level measurement configuration for NR +CAPPLEVMCNR + +**Table 8.84-1: +CAPPLEVMCNR parameter command syntax** + +| Command | Possible response(s) | +|------------------|----------------------------------------| +| +CAPPLEVMCNR=<n> | +CME ERROR: <err> | +| +CAPPLEVMCNR? | +CAPPLEVMCNR: <n> | +| +CAPPLEVMCNR=? | +CAPPLEVMCNR: (list of supported <n>s) | + +### Description + +This command allows control of the application level measurement configuration according to 3GPP TS 38.331 [160]. The set command controls the presentation of the unsolicited result code +CAPPLEVMCNR: (list of [<CR><LF>, <meas\_config\_app\_layer\_id>, [<start-stop\_measurement>, [<ran\_visible\_release\_only>]], [<app-meas\_config\_file\_length>, <app-meas\_config-file>], [<transmission\_of\_session\_start-end>], [<ran\_visible\_periodicity>], [<number\_of\_buffer\_level\_entries>], [<report\_playout\_delay\_for\_media\_startup>], [<app-meas\_service\_type>]) providing data for the configuration. Refer clause 9.2 for possible <err> values. + +Read command returns the current value of <n>. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type. Disable and enable presentation of the unsolicited result code +CAPPLEVMCNR to the TE. + +- 0 Disable presentation of the unsolicited result code +- 1 Enable presentation of the unsolicited result code + +<app-meas\_service\_type>: integer type. Contains the indication of what application that is target for the application level measurement configuration. + +- 1 QoE measurement collection for streaming services +- 2 QoE measurement collection for MTSI services +- 3 QoE measurement collection for VR services + +<start-stop\_measurement>: integer type. Indicates the start and stop of the application level measurement reporting for the application indicated by the <app-meas\_service\_type>. + +- 0 start the application level measurement +- 1 stop the application level measurement and release the application level measurement configuration + +<app-meas\_config\_file\_length>: integer type. Indicates the number of octets of the <app-meas\_config-file> parameter. + +<app-meas\_config-file>: string of octets. Contains the application level measurement configuration file for the application indicated by the <app-meas\_service\_type>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +<meas\_config\_app\_layer\_id>: integer type. At QoE measurement configuration the <meas\_config\_app\_layer\_id> indicates an identity for the QoE measurement configuration received in the <app-meas\_config-file>. At QoE measurement configuration release, the <meas\_config\_app\_layer\_id> indicates the measurement to be released. The absence of this parameter indicates that all measurement configurations are released. + +<transmission\_of\_session\_start-end>: integer type. Contains an indication of whether session start-end is required. + +- 0 Not required +- 1 Required + +<ran\_visible\_periodicity>: integer type. + +- 0 120 ms +- 1 240 ms +- 2 480 ms +- 3 640 ms +- 4 1024 ms + +<number\_of\_buffer\_level\_entries>: integer type. Contains the number of buffer level entries. + +- 1-8 + +<report\_playout\_delay\_for\_media\_startup>: integer type. Contains an indication of whether report of initial playout for media startup delay is required. + +- 0 Report of playout delay for media startup is not required +- 1 Report of playout delay for media startup is required + +<ran\_visible\_release\_only>: integer type. Indicates the RAN visible application level measurements to be released. + +- 0 Release the RAN visible application level measurements for this <meas\_config\_app\_layer\_id> + +## Implementation + +Optional. + +## 8.85 Application level measurement report for NR +CAPPLEVMRNR + +**Table 8.85-1: +CAPPLEVMRNR action command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| +CAPPLEVMR=(list of <CR><LF>, <meas_config_app_layer_id>, [<app-meas_report_length>, <app-meas_report>], [<number-of-pdu-session_id-entries>, (list of <pdu-session_id>s)], [<number_of_buffer_level_entries>, (list of <application_layer_buffer-level>s)], [<qoe_measurement_status>], [<playout_delay_for_media_startup>], [<number-of-pdu-session_id-entries>, (list of <pdu-session_id>, <number-of-qfi-entries>, (<list of <qfi>s>)]s) | +CME ERROR: <err> | +| +CAPPLEVMRNR=? | | + +### Description + +This command allows the MT to provide a list of application level measurement reports according to 3GPP TS 38.331 [160]. Refer clause 9.2 for possible <err> values. + +### Defined values + +<qoe\_measurement\_status>: Indicates whether a session has started or ended. + +0 started + +1 ended + +<app-meas\_report\_length>: integer type. Indicates the number of octets of the <app-meas\_report> parameter. + +<app-meas\_report>: string of octets. Contains the application level measurement report for the application indicated by the <app-meas\_service\_type>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +<meas\_config\_app\_layer\_id>: integer type. Identifies the QoE measurement configuration. + +<playout\_delay\_for\_media\_startup>: integer type. Indicates the application layer playout delay for media startup in ms. + +0-30000 + +<number\_of\_buffer\_level\_entries>: integer type. Contains the number of <application\_layer\_buffer-level> entries. + +1-8 + +<application\_layer\_buffer-level>: integer type. Indicates the application layer buffer level in ms in steps of 10 ms. + +0-30000 + +<number-of-pdu-session\_id-entries>: integer type. Indicates the number of entries in the list of <pdu-session\_id> + +<pdu-session\_id>: integer type. Identifies a PDU session ID. + +0-255 + +<number\_of\_qfi-entries>: integer type. Contains the number of <qfi> entries in the list of <qfi>s + +1-64 + +<qfi>: QoS Flow Identifier: integer type. Identifies a QoS Flow ID + +0-63 + +**Implementation** + +Optional. + +## 8.86 Unavailability Period +CUNPER + +**Table 8.86-1: +CUNPER parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| +CUNPER=<n>,<unavailability_type>,<requested_unper_duration>,<unper_start> | +CME ERROR: <err> | +| +CUNPER? | +CUNPER:<br><n>,<unper_support_nw>,<unavailability_type>,<requested_unper_duration>,<unper_start>,<result><br><br>+CME ERROR: <err> | +| +CUNPER=? | +CUNPER: (list of supported <requested_unper_duration>s) | + +**Description** + +The set command is used to provide the the unavailability type, unavailability period duration, and the start of the unavailability period that are sent to the network in the next registration or UE initiated de-registration procedure, see 3GPP TS 24.501 [161] clause 5.3.26 and 3GPP TS 24.301 [83]. The set command is also used to enable or disable the unsolicited response +CUNPER: <unper\_support\_nw>. The unavailability period specifies the period during which the UE may become unavailable when an event is triggered. + +Refer clause 9.2 for possible <err> values. + +Read command returns the <requested\_unper\_duration>, <unavailability\_type> and <unper\_start> that were provided to the network in the last registration or UE initiated de-registration procedure and <unper\_support\_nw> specifies whether the network indicated support for the unavailability period in the last registration procedure. + +Test command returns supported values as a compound value. + +**Defined values** + +<n>: integer type, to enable or disable the unsolicited response +CUNPER: <unper\_support\_nw>. + +0 disable the unsolicited response. + +1 enable the unsolicited response. + +<requested\_unper\_duration>: string type; three bytes. The <requested\_unper\_duration> value is coded as three bytes (octets 3 to 5) of the Time duration information element in 3GPP TS 24.301 [83]. The default value is "000000000000000000000000", which indicates that the unavailability period is not known. + +<unavailability\_type>: integer type. Indicates the reason for unavailability. + +- 0 UE reasons. +- 1 discontinuous coverage. + +The <unavailability\_type> is applicable only in NG-RAN. It shall be considered as set to "discontinuous coverage" by the MT in satellite E-UTRAN. + +<unper\_start>: string type; three bytes. The <unper\_start> value is coded as three bytes (octets 3 to 5) of the Time duration information element in 3GPP TS 24.301 [83]. The default value is "000000000000000000000000". + +<unper\_support\_nw>: integer type. Indicates the unavailability period feature support by the network see 3GPP TS 24.501 [161] clause 5.3.26 and 3GPP TS 24.301 [83]. + +- 0 indicates that the unavailability period feature is not supported by the network. +- 1 indicates that the unavailability period feature is supported by the network. + +<result>: integer type; indicates the final result of successful indication of unavailability period to network. + +- 0 de-registration procedure successful (see 3GPP TS 24.501 [161] clause 5.3.26) +- 1 registration procedure successful (see 3GPP TS 24.501 [161] clause 5.5.1.3.4) +- 2 registration procedure not successful (see 3GPP TS 24.501 [161] 5.5.1.3.5, clause 5.5.1.3.7). + +#### Implementation + +Optional. + +This command is only applicable to UEs in NG-RAN and in satellite E-UTRAN. + +## 8.87 Discontinuous Coverage +CDISCO + +**Table 8.87-1: +CDISCO parameter command syntax** + +| Command | Possible response(s) | +|---------------|------------------------------------------------------------------------------------------------------------------| +| +CDISCO=[<n>] | +CME ERROR: <err> | +| +CDISCO? | +CDISCO:<br><n>, <indicator>, <access_stratum_status>, <unavailability_period_duration><br><br>+CME ERROR: <err> | +| +CDISCO=? | +CDISCO: (list of supported <n>s)<br><br>+CME ERROR: <err> | + +#### Description + +The set command controls the presentation of unsolicited result code +CDISCO: <indicator> when <n>=1 indicator is indicating the discontinuous coverage situation. + +Refer clause 9.2 for possible <err> values. + +Read command returns the current settings of <n> and the indicator for discontinuous coverage situation. + +Test command returns supported <n>s values as a compound value. + +#### Defined values + +<n>: integer type. + +- 0 Disable presentation of the unsolicited result code +CDISCO: <indicator>. +- 1 Enable presentation of the unsolicited result code +CDISCO: <indicator>. + +<indicator>: integer type. Indicates the current discontinuous coverage situation status for the UE in the network. + +- 0 indicates that the UE is in satellite coverage. +- 1 indicates that the UE is out of satellite coverage (i.e., in discontinuous coverage). + +<access\_stratum\_status>: integer type. Indicates the active status of access stratum in the UE due to discontinuous coverage. + +- 0 indicates that access-stratum is not deactivated due to discontinuous coverage. +- 1 indicates that access-stratum is deactivated due to discontinuous coverage. + +<unavailability\_period\_duration>: string type; three bytes in an 8 bit format. The <unavailability\_period\_duration> value indicates remaining unavailability period duration (i.e., the time until the discontinuous coverage is over) in seconds. The value part of the Unavailability period duration is coded as octets 3 to 5 of the Time duration IE as defined in 3GPP TS 24.501 [161]. + +## Implementation + +Optional. + +This command is only applicable to UEs supporting satellite E-UTRAN access or satellite NR access. + +## 8.88 Informative examples + +Phone Activity Status (+CPAS) is a general command used to detect the presence of the MT, if there is an incoming call, or if there is a call in progress. This command is normally used before trying to operate the MT from the TE. Note that the activity status can change at any time after the execution of +CPAS, and hence the returned value can be obsolete. Detachment of the MT from the TA is indicated with a special final result code that indicates all errors related to the operation of the MT. Result code is +CME ERROR: <err>, where <err> is an integer or verbose value giving useful information about the reason for the command failure (refer clause "Mobile termination error result code +CME ERROR"). + +Set Phone Functionality (+CFUN) can be used to reset the MT or set the power consumption level of the MT by disabling certain parts of the MT (e.g. the transmit and receive RF circuits). Mobile Termination Control Mode (+CMEC) is a command which manages access sharing between the MT and the TE to operate the user interface of the MT. It has four subparameters which describe the access to keypad, display, indicators, and touch screen. Each subparameter has values for restricting the operation of the corresponding user interface part only to the MT or only to the TE, or to give the access for both of them. + +Keypad Control command (+CKPD) is used to operate the keypad of the MT. Here lies the problem of different keypad types between manufacturers, and also between their MT models. The keypresses are sent to the MT as a string type subparameter of this command. Each character in that string represents a key which will be logically pressed. A special character (colon) followed by any character can be used by manufacturers (or TE application programmers) to represent a key which is not defined in this profile. An escape character (semicolon) for direct string entering is also defined. All text between single semicolon characters is treated as an alphanumeric entry and is not converted to keypressings. All semicolon characters inside the text is duplicated in the TE and stripped back to one before entering them to the MT. Command has also optional second and third parameters which can be used to alter the time to strike each key, and the pause to wait between keystrokes (in tenths of a second). A special pause character (W or w) can be added in the string type subparameter for an extra pause of the same length as given by the third subparameter. In the following example alphanumeric mode is entered and a person predefined in the MT phonebook, "Ilkka", is called; each key is struck for half a second and pauses between strokes are a tenth of a second: + +``` +AT+CKPD="@:Ilkka:S",5,1 +OK +``` + +Display Control command (+CDIS) is used both for writing to the display text fields and for reading the current status of the fields. Mobile Termination usually has a character set of its own, so the TA will do a conversion between the TE and the MT character sets. TE can have several character sets and the TA must be informed of the character set in use before starting to write or read the display. Character set is set with general command select TE character set +CSCS. The +CDIS=? query command is a way to get information about the length of the fields. In the following example an MT is first queried about the supported conversions and the lengths of the fields. The response shows there are three ten character long and two six character long fields. Then the TE character set is set to be IRA and the current status of the display is read. The last command writes the text "Hello, I'm writing to display" in the three fields, and keeps the contents of the two other fields same (the last two commas could also be left out). + +``` +AT+CSCS=?;+CDIS=? ++CSCS: ("IRA","PCCP850","8859-1") ++CDIS: 10,10,10,6,6 +OK +AT+CSCS="IRA" +OK +AT+CDIS=? ++CDIS: "RADIOLINJA","","","","Menu","Memory" +OK +AT+CDIS="IRA","Hello, I'm","writing to","display",, +OK +``` + +The writing is possible only when it is permitted by the Mobile Termination Control Mode command (and by the manufacturer). If a certain field is not writable (but is readable), writing to it is ignored. The order of the text fields is determined by manufacturers and follow the rule: first field is in the upper left corner, second in the next field to the right, and so on, until to the last field in the lower right corner. + +Touch screen action Control command (+CTSA) is used to operate the touch screen of the MT. The x, y coordinates of the phone are fixed even if the device's orientation is changed. In the following example commands are sent to the MT to emulate a user drawing on the ME's touch screen; it is relevant that the gesture starts from the top of the touch screen. A gesture is emulated, starting at location 10,10 in a non-display area of the ME's (touch) screen, then dragged to 50,50 (during which the gesture crosses the boundary between the non-display area and a display area), then dragged to 100,100 and finally the touch screen is released at location 100,100. + +``` +AT+CSO=? obtain the touch screen orientation ++CSO=2,0 +AT+CSS=? obtain the touch screen size ++CSS=200,600 +AT+CDSB=? determine if a boundary between the non-display area and a display area exists, and its location ++CDSB=20,20,180,580 +AT+CTSA=1,10,10 start emulating a gesture +AT+CTSA=1,50,50 emulate that the gesture crosses the boundary between non-display area and a display area +AT+CTSA=0,100,100 end emulating the gesture +``` + +Indicators can be handled with Indicator Control command (+CIND). Its query command returns a short description (abbreviation) of the purpose of the indicators and the supported values for each indicator. The setting and reading is done similarly as with Display Control command. In the following example the indicators of a phone are queried, their current value is read, and the value of message indicator is tried to set (but it is forbidden): + +``` +AT+CIND=? ++CIND: ("memory", (0-2)), ("call", (0,1)), ("data", (0,1)), ("roam", (0,1)), +("alpha", (0,1)), ("message", (0,1)), ("index1", (0-11)), ("index2", (0-11)), +("index3", (0-11)), ("signal", (0-5)), ("service", (0,1)), ("sell", (0,1)), +("sel2", (0,1)), ("sel3", (0,1)), ("battchg", (0-5)) +OK +AT+CIND? ++CIND: 1,0,0,0,0,1,0,0,0,3,1,0,0,0,5 +OK +AT+CIND=,,, , ,0 ++CME ERROR: 10 +``` + +The subparameter order in the command is defined by the query command order, not by the actual display order. The zero value of an indicator means that it is off (or in state which can be identified as "off"-state), value one means that the indicator is on (or in a state which is more substantial than "off"-state), value two is more substantial than one, and so on. + +To this point, only operating through the TE is covered. But when MT can be operated also through its keypad, or touch screen, or there are changes in the status of the display elements, the information about these actions is given to the TE + +also. This can be solved only with unsolicited result codes which return keypad, display text and indicator, and touch screen events. Each event group has a result code of its own: +CKEV returns the key code and if the key pressed (1) or released (0), +CDEV returns the display text field running number (as specified by command +CDIS) and the new status of the field, and +CIEV returns the running number of the indicator (refer +CIND) and the new value of it, and +CTEV returns the location of the action performed on the touch screen. In the following example number key 1 is pressed, updated on the display, released, and signal strength changes its state to five, the touch screen is pressed at coordinates 10,10, and it is released at the same coordinates, 3 seconds after initially pressing the screen: + +``` ++CKEV: 49,1 ++CDEV: 1,"1" ++CKEV: 49,0 ++CIND: 10,5 ++CTEV: 1,10,10,0; ++CTEV: 0,10,10,0,3000 +``` + +Mobile Termination Event Reporting command (+CMER) has been specified for the purpose of controlling the sending of these unsolicited result codes to the TE. Four ways are provided to handle the buffering of the result codes (see figure 8). The first is to buffer them always. The second possibility is to discard them when in on-line data mode and otherwise forward them directly to the TE. The third possibility is to buffer them in data mode and otherwise forward them to the TE. The last possibility is to send them always to the TE (some inband technique - e.g. V.80 - is used in data mode to send the result codes within the data). This is the first subparameter of +CMER command. Next three subparameters are used to enable or disable each of the keypad, text field and indicator result codes. Sending codes can be enabled either so that only events generated from the MT user interface are returned, or so that also events caused by Keypad, Display and Indicator Control commands are returned. The fifth subparameter controls the flushing of the buffer when the value of the first subparameter is changed to a value from one to three. + +![Figure 8: Mobile termination event reporting diagram. The diagram shows the flow of MT events from the MT (Mobile Termination) to the TA (Terminal Adapter) and then to the TE (Terminal Equipment). The TA is divided into COMMAND MODE and DATA MODE. In COMMAND MODE, events are sent directly to the TE. In DATA MODE, events are sent to a Buffer, which then sends them to the TE. The +CMER first subparameter values 0, 1, 2, and 3 correspond to different buffering and sending behaviors. The diagram shows that in COMMAND MODE, events are sent directly to the TE. In DATA MODE, events are sent to a Buffer, which then sends them to the TE. The +CMER first subparameter values 0, 1, 2, and 3 correspond to different buffering and sending behaviors.](2f903f194dbf70f3aa6c281a6f96db03_img.jpg) + +The diagram illustrates the flow of Mobile Termination (MT) events to the Terminal Equipment (TE) through the Terminal Adapter (TA). The TA is split into COMMAND MODE and DATA MODE. In COMMAND MODE, MT events are sent directly to the TE. In DATA MODE, MT events are sent to a Buffer, which then sends them to the TE. The +CMER first subparameter values 0, 1, 2, and 3 correspond to different buffering and sending behaviors. The diagram shows that in COMMAND MODE, events are sent directly to the TE. In DATA MODE, events are sent to a Buffer, which then sends them to the TE. The +CMER first subparameter values 0, 1, 2, and 3 correspond to different buffering and sending behaviors. + +| +CMER first subparameter | COMMAND MODE | DATA MODE | +|--------------------------|--------------|-----------| +| 0 | Direct | Buffer | +| 1 | Direct | Direct | +| 2 | Direct | Buffer | +| 3 | Direct | Direct | + +Figure 8: Mobile termination event reporting diagram. The diagram shows the flow of MT events from the MT (Mobile Termination) to the TA (Terminal Adapter) and then to the TE (Terminal Equipment). The TA is divided into COMMAND MODE and DATA MODE. In COMMAND MODE, events are sent directly to the TE. In DATA MODE, events are sent to a Buffer, which then sends them to the TE. The +CMER first subparameter values 0, 1, 2, and 3 correspond to different buffering and sending behaviors. The diagram shows that in COMMAND MODE, events are sent directly to the TE. In DATA MODE, events are sent to a Buffer, which then sends them to the TE. The +CMER first subparameter values 0, 1, 2, and 3 correspond to different buffering and sending behaviors. + +Figure 8: Mobile termination event reporting + +An example of complete setup of the TA where TE takes the control of keypad, but does not want to write to display nor control the indicators (in the start MT is powered off): + +``` +AT+CMEE=2;+CREG=1 (use verbose <err> values; report registration) +OK +AT+CPAS (query MT status) ++CPAS: 5 (MT is asleep) +OK +AT+CFUN=1 (set MT to full functionality state) ++CME ERROR: SIM PIN required (SIM requests PIN) +AT+CPIN="1234" ++CME ERROR: incorrect password (user entered wrong PIN) +AT+CPIN="4321" +OK (correct PIN) +AT+COPS=0,0 (ask for automatic operator selection and registration) +OK ++CREG: 1 (registered in the network) +AT+COPS? ++COPS: 0,0,"RADIOLINJA" (get the operator name) +OK +AT+CMEC=1,0,0 (take over the keypad, leave display to MT) +OK +``` + +``` + +AT+CDIS=?;+CIND=? (query display text and indicator formats) ++CDIS: 10,10,10,6,6 ++CIND: ("memory", (0-2)), ("call", (0,1)), ("data", (0,1)), ("roam", (0,1)), +("alpha", (0,1)), ("message", (0,1)), ("index1", (0-11)), ("index2", (0-11)), +("index3", (0-11)), ("signal", (0-5)), ("service", (0,1)), ("sell", (0,1)), +("sel2", (0,1)), ("sel3", (0,1)), ("battchg", (0-5)) +OK +AT+CSCS="IRA" (set TE character set for display text results) +OK +AT+CMER=1,0,2,2,0 (return display text and indicator result codes when +in command state, in data mode discard them) +OK +AT+CDIS?;+CIND? (read current state of display texts and indicators) ++CDIS: "", "", " 12345", "Menu", "Memory" (user had pressed number buttons before) ++CIND: 1,0,0,0,0,1,0,0,0,3,1,0,0,0,5 TE took control with +CMEC) +OK +AT+CKPD="C",20 (clear main display text '12345' by holding the +'clear' button down two seconds) +OK ++CDEV: 3, "1234" (first only one character deleted) ++CDEV: 3, "" (while holding continues, whole display is cleared) ++CDEV: 1, "RADIOLINJA" (operator name comes to the display) + +``` + +The start of the previous example could go as follows when MT has already been powered on but is waiting for the PIN: + +``` + +AT+CME=2;+CREG=1 (use verbose <err> values; report registration) +OK +AT+CPAS (query MT status) ++CPAS: 0 (MT is ready to receive commands) +OK +AT+CPIN? (is MT asking passwords?) ++CPIN: SIM PIN (yes, SIM PIN required) +AT+CPIN="4321" +OK (correct PIN) + +``` + +One of the most regular operations done through the MT user interface is phonebook control. To lessen the workload of the TE, some direct commands for phonebook reading and writing are practical. Command Select Phonebook Memory Storage +CPBS query version returns supported phonebook memories, read version returns current settings, and set version selects the memory. For GSM, the normal storages are SIM, MT and TA. + +Read Phonebook Entries (+CPBR) can be used to read either one or many phonebook locations at the same time. A regular phonebook entry consists of three elements: memory index number, the phone number and its alphanumeric equivalent given by the user. Query version of this returns supported index values of the selected memory, and the maximum lengths of the number and alphanumeric elements. The query version of the Write Phonebook Entry command (+CPBW) is similar, but the action version sets or clears an entry in the phonebook. Find Phonebook Entries (+CPBF) can be used to search alphanumeric entries starting with specific string. An example where the whole phonebook of the MT is read, index number four is cleared, and number three is written: + +``` + +AT+CPBS=? ++CPBS: ("ME", "SM") (MT and SIM have phonebooks) +OK +AT+CPBS="ME" (select MT memory) +OK +AT+CPBR=? (read index range and element lengths) ++CPBR: (1-99), 30, 30 +OK +AT+CPBR=1,99 (read all entries but only the ones set are returned) ++CPBR: 1, "931123456", 129, "Ilkka" ++CPBR: 2, "9501234567", 129, "" ++CPBR: 4, "901234567", 129, "Hesari" +OK +AT+CPBW=4;+CPBW=3, "921123456", "TS" (clear index 4 and write index 3) +OK + +``` + +Circuit switched fallback (+CCSFB) can be used to control circuit switched fallback operation. Reporting of CSFB related CS paging requests can be switched on or off by +CCSFB=1 and +CCSFB=0. CSFB related CS paging requests are reported with unsolicited result code +CCSFB. CSFB calls can be automatically accepted or rejected by +CCSFB=2, +CCSFB=3, +CCSFB=4 and +CCSFB=5. CSFB calls can be manually accepted or rejected by +CCSFB=6 and +CCSFB=7. In the example the ME interrogates the current CSFB settings, enables reporting and accepts a CSFB call: + +``` + +AT+CCSFB=? ++CCSFB: 0 (reporting and automatic acceptance/rejection disabled) +OK +AT+CCSFB=1 (enable reporting) +OK ++CCSFBU: 2,1,12345678,17 (incoming CSFB paging request with clip supplementary service) +AT+CCSFB=6 (accept CSFB call) +OK + +``` + +## 8.89 Signal level enhanced network selection +CSENSE + +**Table 8.89-1: +CSENSE parameter command syntax** + +| Command | Possible response(s) | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| +CSENSE=[<reporting>] | | +| +CSENSE? | +CSENSE1: <reporting>,<enabled><br><CR><LF> [+CSENSE2: <Threshold>,<AcT>]<br>[<CR><LF> [+CSENSE3: <Threshold>,<AcT>]<br>[...]] | +| +CSENSE=? | +CSENSE: (list of supported <reporting>s) | + +### Description + +This command allows to retrieve "Operator controlled signal threshold per access technology" (as defined in 3GPP TS 23.122 [xxx]) parameters stored in the USIM (see 3GPP TS 31.102 [59]). + +Set command enables reporting upon change of "Operator controlled signal threshold per access technology" parameters. + +Read command returns one line of intermediate result code +CSENSE1: <reporting>,<enabled> with the information if the UE is configured for using signal level enhanced network selection. This follows by zero or more occurrences lines with intermediate result code +CSENSE2: <Threshold>,<AcT> with the home operator controlled signal threshold and an associated access technology. + +Test command returns values supported as a compound value. + +### Defined values + +<reporting>: integer type. Enables or disables reporting of changes in the "Operator controlled signal threshold per access technology". + +- 0 disable reporting +- 1 enable reporting + +<enabled>: integer type. Information if the UE is configured for using signal level enhanced network selection. Value according to 3GPP TS 31.102 [59]. + +- 0 UE is configured for not using signal level enhanced network selection. +- 1 UE is configured for using signal level enhanced network selection. + +<Threshold>: integer type. A home operator controlled signal threshold. Value according to 3GPP TS 31.102 [59]. + +<AcT>: integer type. The access technology associated to the home operator controlled signal threshold. Value according to 3GPP TS 31.102 [59]. + +- 0 E-UTRAN - NB-IoT (NB-S1 mode) +- 1 EC-GSM-IoT (A/Gb mode) + +- 2 E-UTRAN -Category M1 (NB-S1 mode) +- 3 E-UTRAN - Category M2 (WB-S1 mode) + +#### Implementation + +Optional. + +## 9 Mobile termination errors + +### 9.1 Report mobile termination error +CMEE + +**Table 110: +CMEE parameter command syntax** + +| Command | Possible response(s) | +|--------------|---------------------------------| +| +CMEE= [<n>] | | +| +CMEE? | +CMEE: <n> | +| +CMEE=? | +CMEE: (list of supported <n>s) | + +#### Description + +Set command disables or enables the use of final result code +CME ERROR: <err> as an indication of an error relating to the functionality of the MT. When enabled, MT related errors cause +CME ERROR: <err> final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality. + +Read command returns the current setting of <n>. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type. + +- 0 disable +CME ERROR: <err> result code and use ERROR instead +- 1 enable +CME ERROR: <err> result code and use numeric <err> values (refer clause 9.2) +- 2 enable +CME ERROR: <err> result code and use verbose <err> values (refer clause 9.2) + +#### Implementation + +Mandatory for <n> values 0 and 1. + +### 9.1A Report mobile originated location request error +CMOLRE + +**Table 9.1A-1: +CMOLRE parameter command syntax** + +| Command | Possible response(s) | +|----------------|-----------------------------------| +| +CMOLRE= [<n>] | | +| +CMOLRE? | +CMOLRE: <n> | +| +CMOLRE=? | +CMOLRE: (list of supported <n>s) | + +### Description + +Set command disables or enables the verbose format of unsolicited result code +CMOLRE: <err> as an indication of an error relating to the functionality for the mobile originated location request (MO-LR) error reporting format. When enabled, MT related verbose error cause is given. + +Read command returns the current setting of <n>. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type. + +0 disable. This will give +CMOLRE: <err> result code with numeric <err> values (refer clause 9.3) + +1 enable. This will give +CMOLRE: <err> result code with verbose <err> values (refer clause 9.3) + +### Implementation + +Optional. + +## 9.1B Report network error codes +CNEC + +**Table 9.1B-1: +CNEC parameter command syntax** + +| Command | Possible response(s) | +|--------------|---------------------------------| +| +CNEC= [<n>] | | +| +CNEC? | +CNEC: <n> | +| +CNEC=? | +CNEC: (list of supported <n>s) | + +### Description + +The command activates or deactivates unsolicited reporting of error codes sent by the network. When activated, based on the setting of <n>, the ME will report CS mobility management, GPRS mobility management, GPRS session management, EPS mobility management and EPS session management related error codes sent by the network. The following unsolicited result codes can be reported: + +- +CNEC\_MM: <error\_code> CS Mobility Management +- +CNEC\_GMM: <error\_code> GPRS Mobility Management +- +CNEC\_GSM: <error\_code>[, <cid>] GPRS Session Management +- +CNEC\_EMM: <error\_code>[, <cid>] EPS Mobility Management +- +CNEC\_ESM: <error\_code>[, <cid>] EPS Session Management +- +CNEC\_5GMM: <error\_code>[, <cid>] 5GS Mobility Management +- +CNEC\_5GSM: <error\_code>[, <cid>] 5GS Session Management + +The parameter <n> is specified as a sum of integers, each representing the category of error codes that the MT is interested in receiving. + +The read command returns the current setting of <n>. + +Test command returns the supported values as a compound value. + +### Parameters + +<n>: integer type. The parameter is a sum of integers each representing a certain category of error codes. The value consists of the sum of the individual values for <n> for the required unsolicited result codes. + +- 0 Disable unsolicited error reporting +- 1 Enable unsolicited result code +CNEC\_MM to report CS mobility management errors coded as specified in 3GPP TS 24.008 [8] Table 10.5.95/3GPP TS 24.008 +- 2 Enable unsolicited result code +CNEC\_GMM to report GPRS mobility management errors coded as specified in 3GPP TS 24.008 [8] Table 10.5.147/3GPP TS 24.008 +- 4 Enable unsolicited result code +CNEC\_GSM to report GPRS session management errors coded as specified in 3GPP TS 24.008 [8] Table 10.5.157/3GPP TS 24.008 +- 8 Enable unsolicited result code +CNEC\_EMM to report EPS mobility management errors coded as specified in 3GPP TS 24.301 [83] Table 9.9.3.9.1 +- 16 Enable unsolicited result code +CNEC\_ESM to report EPS session management errors coded as specified in 3GPP TS 24.301 [83] Table 9.9.4.4.1 +- 32 Enable unsolicited result code +CNEC\_5GMM to report 5GS mobility management errors coded as specified in 3GPP TS 24.501 [161] Table 9.11.3.2.1 +- 64 Enable unsolicited result code +CNEC\_5GSM to report 5GS session management errors coded as specified in 3GPP TS 24.501 [161] Table 9.11.4.2.1 + +NOTE: The sequence of entering +CNEC=1, followed by +CNEC=4 does not yield the same result as +CNEC=5, as +CNEC=4 overwrites the previous setting. + +Example: If the MT wants to receive only CS mobility management errors, then <n>=1 must be specified. + +AT+CNEC=1 + +If the MT wants to receive CS mobility management errors and GPRS session management errors, then <n>=5 must be specified (1 for enabling CS mobility management error and 4 for enabling GPRS session management error). + +AT+CNEC=5 + +To enable reporting of all error codes, then <n>=127 must be specified (equals 1+2+4+8+16+32+64). + +AT+CNEC=127 + +<error\_code>: integer type. Error codes as appropriate according to: + +- 3GPP TS 24.008 [8] Table 10.5.95/3GPP TS 24.008 for CS mobility management errors codes +- 3GPP TS 24.008 [8] Table 10.5.147/3GPP TS 24.008 for GPRS mobility management errors codes +- 3GPP TS 24.008 [8] Table 10.5.157/3GPP TS 24.008 for GPRS session management errors codes +- 3GPP TS 24.301 [83] Table 9.9.3.9.1 for EPS mobility management errors codes +- 3GPP TS 24.301 [83] Table 9.9.4.4.1 for EPS session management errors codes +- 3GPP TS 24.501 [161] Table 9.11.3.2.1 for 5GS mobility management errors codes +- 3GPP TS 24.501 [161] Table 9.11.4.2.1 for 5GS session management errors codes + +<cid>: integer type. Specifies a particular PDP context definition. + +## Implementation + +Optional. + +## 9.2 Mobile termination error result code +CME ERROR + +### 9.2.0 General + +The operation of +CME ERROR: <err> final result code is similar to the regular ERROR result code: if +CME ERROR: <err> is the result code for any of the commands in a command line, none of the following commands in the same command line is executed (neither ERROR nor OK result code shall be returned as a result of a completed command line execution). The format of <err> can be either numeric or verbose. This is set with command +CMEE (refer clause 9.1). + +NOTE: ITU-T Recommendation V.250 [14] command V does not affect the format of this result code. + +<err> values (numeric format followed by verbose format): + +All values below 256 are reserved. + +Values in the range 0 - 100 are reserved for general errors. + +Values in the range 101 - 150 are reserved for use by CS, GPRS, EPS and 5GS. + +Values in the range 151 - 170 are reserved for use by VBS/VGCS and eMLPP. + +Values in the range 171 - 256 can be used by GPRS, EPS and 5GS. + +### 9.2.1 General errors + +| Numeric | Text | +|---------|------| +|---------|------| + +| | | +|----|-----------------------------------------------| +| 0 | phone failure | +| 1 | no connection to phone | +| 2 | phone-adaptor link reserved | +| 3 | operation not allowed | +| 4 | operation not supported | +| 5 | PH-SIM PIN required | +| 6 | PH-FSIM PIN required | +| 7 | PH-FSIM PUK required | +| 10 | SIM not inserted (See NOTE 1) | +| 11 | SIM PIN required | +| 12 | SIM PUK required | +| 13 | SIM failure (See NOTE 1) | +| 14 | SIM busy (See NOTE 1) | +| 15 | SIM wrong (See NOTE 1) | +| 16 | incorrect password | +| 17 | SIM PIN2 required | +| 18 | SIM PUK2 required | +| 20 | memory full | +| 21 | invalid index | +| 22 | not found | +| 23 | memory failure | +| 24 | text string too long | +| 25 | invalid characters in text string | +| 26 | dial string too long | +| 27 | invalid characters in dial string | +| 30 | no network service | +| 31 | network timeout | +| 32 | network not allowed - emergency calls only | +| 40 | network personalization PIN required | +| 41 | network personalization PUK required | +| 42 | network subset personalization PIN required | +| 43 | network subset personalization PUK required | +| 44 | service provider personalization PIN required | + +- 45 service provider personalization PUK required +- 46 corporate personalization PIN required +- 47 corporate personalization PUK required +- 48 hidden key required (See NOTE 2) +- 49 EAP method not supported +- 50 Incorrect parameters +- 51 command implemented but currently disabled +- 52 command aborted by user +- 53 not attached to network due to MT functionality restrictions +- 54 modem not allowed - MT restricted to emergency calls only +- 55 operation not allowed because of MT functionality restrictions +- 56 fixed dial number only allowed - called number is not a fixed dial number (refer 3GPP TS 22.101 [147]) +- 57 temporarily out of service due to other MT usage +- 58 language/alphabet not supported +- 59 unexpected data value +- 60 system failure +- 61 data missing +- 62 call barred +- 63 message waiting indication subscription failure +- 100 unknown + +NOTE 1: This error code is also applicable to UICC. + +NOTE 2: This key is required when accessing hidden phonebook entries. + +## 9.2.2 CS, GPRS, UMTS, EPS and 5GS-related errors + +### 9.2.2.1 Errors related to a failure to perform an attach + +#### 9.2.2.1.1 Errors for CS, GPRS and UMTS + +| Numeric | Text | +|---------|----------------------------------------------------------| +| 102 | IMSI unknown in HLR (#2) NOTE 2 | +| 103 | Illegal MS (#3) | +| 104 | IMSI unknown in VLR (#4) NOTE 2 | +| 105 | IMEI not accepted (#5) NOTE 2 | +| 106 | Illegal ME (#6) | +| 107 | GPRS services not allowed (#7) | +| 108 | GPRS services and non-GPRS services not allowed (#8) | +| 109 | MS identity cannot be derived by the network (#9) NOTE 2 | +| 110 | Implicitly detached (#10) NOTE 2 | +| 111 | PLMN not allowed (#11) | +| 112 | Location area not allowed (#12) | +| 113 | Roaming not allowed in this location area (#13) | +| 114 | GPRS services not allowed in this PLMN (#14) | +| 115 | No Suitable Cells In Location Area (#15) | +| 116 | MSC temporarily not reachable (#16) NOTE 2 | +| 117 | Network failure (#17) NOTE 2 | +| 122 | Congestion (#22) | +| 125 | Not authorized for this CSG (#25) | +| 132 | Service option not supported (#32) NOTE 2 | +| 133 | Requested service option not subscribed (#33) NOTE 2 | +| 134 | Service option temporarily out of order (#34) NOTE 2 | +| 138 | Call cannot be identified (#38) NOTE 2 | +| 148 | Unspecified GPRS error NOTE 2 | +| 150 | Invalid mobile class | +| 172 | Semantically incorrect message (#95) | +| 173 | Invalid mandatory information (#96) | + +| | | +|-----|------------------------------------------------------------------| +| 174 | Message type non-existent or not implemented (#97) | +| 175 | Conditional IE error (#100) | +| 176 | Protocol error, unspecified (#111) | +| 183 | SMS provided via GPRS in this routing area (#28) NOTE 2 | +| 185 | No PDP context activated (#40) NOTE 2 | +| 186 | Message not compatible with protocol state (#101) NOTE 2 | +| 187 | Recovery on timer expiry (#102) NOTE 2 | +| 208 | Message type not compatible with protocol state (#98) NOTE 2 | +| 209 | Information element non-existent or not implemented (#99) NOTE 2 | + +NOTE 1: Values in parentheses are 3GPP TS 24.008 [8] cause codes. + +NOTE 2: This error code was given a numeric value in 3GPP Rel-15, but was introduced in an earlier release. + +#### 9.2.2.1.2 Errors for EPS + +| Numeric | Text | +|---------|-------------------------------------------------------------------| +| 102 | IMSI unknown in HSS (#2) NOTE 2 | +| 103 | Illegal UE (#3) | +| 105 | IMEI not accepted (#5) NOTE 2 | +| 106 | Illegal ME (#6) | +| 107 | EPS services not allowed (#7) | +| 108 | EPS services and non-EPS services not allowed (#8) | +| 109 | UE identity cannot be derived by the network (#9) NOTE 2 | +| 110 | Implicitly detached (#10) NOTE 2 | +| 111 | PLMN not allowed (#11) | +| 112 | Tracking area not allowed (#12) | +| 113 | Roaming not allowed in this tracking area (#13) | +| 114 | EPS services not allowed in this PLMN (#14) | +| 115 | No suitable cells in tracking area (#15) | +| 116 | MSC temporarily not reachable (#16) NOTE 2 | +| 117 | Network failure (#17) NOTE 2 | +| 118 | CS domain not available (#18) | +| 119 | ESM failure (#19) | +| 122 | Congestion (#22) | +| 125 | Not authorized for this CSG (#25) | +| 139 | CS service temporarily not available (#39) NOTE 2 | +| 172 | Semantically incorrect message (#95) | +| 173 | Invalid mandatory information (#96) | +| 174 | Message type non-existent or not implemented (#97) | +| 175 | Conditional IE error (#100) | +| 176 | Protocol error, unspecified (#111) | +| 185 | No EPS bearer context activated (#40) NOTE 2 | +| 186 | Message not compatible with protocol state (#101) NOTE 2 | +| 189 | Requested service option not authorized in this PLMN (#35) NOTE 2 | +| 204 | Severe network failure (#42) NOTE 2 | +| 208 | Message type not compatible with protocol state (#98) NOTE 2 | +| 209 | Information element non-existent or not implemented (#99) NOTE 2 | +| 226 | Redirection to 5GCN required (#31) | + +NOTE 1: Values in parentheses are 3GPP TS 24.301 [83] cause codes. + +NOTE 2: This error code was given a numeric value in 3GPP Rel-15, but was introduced in an earlier release. + +#### 9.2.2.1.3 Errors for 5GS + +| Numeric | Text | +|---------|-----------------------| +| 103 | Illegal UE (#3) | +| 105 | PEI not accepted (#5) | +| 106 | Illegal ME (#6) | + +107 5GS services not allowed (#7) + 109 UE identity cannot be derived by the network (#9) + 110 Implicitly deregistered (#10) + 111 PLMN not allowed (#11) + 112 Tracking area not allowed (#12) + 113 Roaming not allowed in this tracking area (#13) + 115 No suitable cells in tracking area (#15) + 122 Congestion (#22) + 172 Semantically incorrect message (#95) + 173 Invalid mandatory information (#96) + 174 Message type non-existent or not implemented (#97) + 175 Conditional IE error (#100) + 176 Protocol error, unspecified (#111) + 178 Maximum number of PDU sessions reached (#65) + 186 Message not compatible with protocol state (#101) + 205 Insufficient resources for specific slice and DNN (#67) + 207 Insufficient resources for specific slice (#69) + 208 Message type not compatible with protocol state (#98) + 209 Information element non-existent or not implemented (#99) + 210 N1 mode not allowed (#27) + 211 Restricted service area (#28) + 212 LADN not available (#43) + 214 ngKSI already in use (#71) + 215 Payload was not forwarded (#90) + 216 Non-3GPP access to 5GCN not allowed (#72) + 217 Serving network not authorized (#73) + 218 DNN not supported or not subscribed in the slice (#91) + 219 Insufficient user-plane resources for the PDU session (#92) + 227 Redirection to EPC required (#31) + 228 Temporarily not authorized for this SNPN (#74) + 229 Permanently not authorized for this SNPN (#75) + 231 Not authorized for this CAG or authorized for CAG cells only (#76) + 232 No network slices available (#62) + 233 Wireline access area not allowed (#77) + +NOTE: Values in parentheses are 3GPP TS 24.501 [161] cause codes. + +## 9.2.2.2 Errors related to a failure to activate a context + +### 9.2.2.2.1 Errors for GPRS and UMTS + +| Numeric | Text | +|---------|--------------------------------------------------------------------| +| 124 | MBMS bearer capabilities insufficient for the service (#24) NOTE 2 | +| 126 | Insufficient resources (#26) | +| 127 | Missing or unknown APN (#27) | +| 128 | Unknown PDP address or PDP type (#28) | +| 129 | User authentication or authorization failed (#29) | +| 130 | Activation rejected by GGSN, Serving GW or PDN GW (#30) | +| 131 | Activation rejected, unspecified (#31) | +| 132 | Service option not supported (#32) | +| 133 | Requested service option not subscribed (#33) | +| 134 | Service option temporarily out of order (#34) | +| 135 | NSAPI already used (#35) NOTE 2 | +| 136 | Regular deactivation (#36) NOTE 2 | +| 140 | Feature not supported (#40) | +| 141 | Semantic error in the TFT operation (#41) | +| 142 | Syntactical error in the TFT operation (#42) | +| 143 | Unknown PDP context (#43) | +| 144 | Semantic errors in packet filter(s) (#44) | +| 145 | Syntactical errors in packet filter(s) (#45) | + +146 PDP context without TFT already activated (#46) +147 Multicast group membership time-out (#47) NOTE 2 +148 Unspecified GPRS error +149 PDP authentication failure +150 Invalid mobile class +172 Semantically incorrect message (#95) NOTE 2 +173 Invalid mandatory information (#96) NOTE 2 +174 Message type non-existent or not implemented (#97) NOTE 2 +175 Conditional IE error (#100) NOTE 2 +176 Protocol error, unspecified (#111) NOTE 2 +177 Operator determined barring (#8) +178 Maximum number of PDP contexts reached (#65) +179 Requested APN not supported in current RAT and PLMN combination (#66) +180 Request rejected, bearer control mode violation (#48) +182 User data transmission via control plane is congested +186 Message not compatible with protocol state (#101) NOTE 2 +188 Invalid transaction identifier value (#81) NOTE 2 +190 Network failure (#38) NOTE 2 +191 Reactivation requested (#39) NOTE 2 +192 PDP type IPv4 only allowed (#50) NOTE 2 +193 PDP type IPv6 only allowed (#51) NOTE 2 +194 Single address bearers only allowed (#52) NOTE 2 +195 Collision with network initiated request (#56) NOTE 2 +196 PDP type IPv4v6 only allowed (#57) NOTE 2 +197 PDP type non IP only allowed (#58) NOTE 2 +198 Bearer handling not supported (#60) NOTE 2 +199 APN restriction value incompatible with active PDP context (#112) NOTE 2 +200 Multiple accesses to a PDN connection not allowed (#113) NOTE 2 +208 Message type not compatible with protocol state (#98) NOTE 2 +209 Information element non-existent or not implemented (#99) NOTE 2 + +NOTE 1: Values in parentheses are 3GPP TS 24.008 [8] cause codes. + +NOTE 2: This error code was given a numeric value in 3GPP Rel-15, but was introduced in an earlier release. + +### 9.2.2.2.2 Errors for EPS + +| Numeric | Text | +|---------|---------------------------------------------------------------------------------| +| 126 | Insufficient resources (#26) | +| 127 | Missing or unknown APN (#27) | +| 128 | Unknown PDN type (#28) | +| 129 | User authentication or authorization failed (#29) | +| 130 | Activation rejected by Serving GW or PDN GW (#30) | +| 131 | Request rejected, unspecified (#31) | +| 132 | Service option not supported (#32) | +| 133 | Requested service option not subscribed (#33) | +| 134 | Service option temporarily out of order (#34) | +| 135 | PTI already in use (#35) | +| 136 | Regular deactivation (#36) NOTE 2 | +| 137 | EPS QoS not accepted (#37) NOTE 2 | +| 141 | Semantic error in the TFT operation (#41) | +| 142 | Syntactical error in the TFT operation (#42) | +| 143 | Invalid EPS bearer identity (#43) | +| 144 | Semantic errors in packet filter(s) (#44) | +| 145 | Syntactical errors in packet filter(s) (#45) | +| 171 | Last PDN disconnection not allowed (#49) NOTE 3 | +| 172 | Semantically incorrect message (#95) NOTE 2 | +| 173 | Invalid mandatory information (#96) NOTE 2 | +| 174 | Message type non-existent or not implemented (#97) NOTE 2 | +| 175 | Conditional IE error (#100) NOTE 2 | +| 176 | Protocol error, unspecified (#111) NOTE 2 | +| 177 | Operator determined barring (#8) | +| 178 | Maximum number of EPS bearers reached (#65) | +| 179 | Requested APN not supported in current RAT and PLMN combination (#66) | +| 181 | unsupported QCI value (#59) | +| 184 | Invalid PTI value (#81) | +| 186 | Message not compatible with protocol state (#101) NOTE 2 | +| 190 | Network failure (#38) NOTE 2 | +| 191 | Reactivation requested (#39) NOTE 2 | +| 192 | PDN type IPv4 only allowed (#50) NOTE 2 | +| 193 | PDN type IPv6 only allowed (#51) NOTE 2 | +| 194 | Single address bearers only allowed (#52) NOTE 2 | +| 195 | Collision with network initiated request (#56) NOTE 2 | +| 196 | PDN type IPv4v6 only allowed (#57) NOTE 2 | +| 197 | PDN type non IP only allowed (#58) NOTE 2 | +| 198 | Bearer handling not supported (#60) NOTE 2 | +| 199 | APN restriction value incompatible with active EPS bearer context (#112) NOTE 2 | +| 200 | Multiple accesses to a PDN connection not allowed (#113) NOTE 2 | +| 201 | ESM information not received (#53) NOTE 2 | +| 202 | PDN connection does not exist (#54) NOTE 2 | +| 203 | Multiple PDN connections for a given APN not allowed (#55) NOTE 2 | +| 208 | Message type not compatible with protocol state (#98) NOTE 2 | +| 209 | Information element non-existent or not implemented (#99) NOTE 2 | +| 221 | PTI mismatch (#47) | +| 230 | PDN type Ethernet only allowed (#61) | + +NOTE 1: Values in parentheses are 3GPP TS 24.301 [83] cause codes. + +NOTE 2: This error code was given a numeric value in 3GPP Rel-15, but was introduced in an earlier release. + +NOTE 3: The numeric error code for "Last PDN disconnection not allowed (#49)" is returned when the MT detects an attempt to disconnect the last PDN or the network returns a response message with cause value #49. The numeric error code was changed to 171 in 3GPP Rel-11. + +### 9.2.2.2.3 Errors for 5GS + +| Numeric | Text | +|---------|-------------------------------------------------------------------------------| +| 126 | Insufficient resources (#26) | +| 127 | Missing or unknown DNN (#27) | +| 128 | Unknown PDU session type (#28) | +| 129 | User authentication or authorization failed (#29) | +| 131 | Request rejected, unspecified (#31) | +| 132 | Service option not supported (#32) | +| 133 | Requested service option not subscribed (#33) | +| 135 | PTI already in use (#35) | +| 136 | Regular deactivation (#36) | +| 137 | 5GS QoS not accepted (#37) | +| 141 | Semantic error in the TFT operation (#41) | +| 142 | Syntactical error in the TFT operation (#42) | +| 143 | Invalid PDU session identity (#43) | +| 144 | Semantic errors in packet filter(s) (#44) | +| 145 | Syntactical errors in packet filter(s) (#45) | +| 172 | Semantically incorrect message (#95) | +| 173 | Invalid mandatory information (#96) | +| 174 | Message type non-existent or not implemented (#97) | +| 175 | Conditional IE error (#100) | +| 176 | Protocol error, unspecified (#111) | +| 177 | Operator determined barring (#8) | +| 181 | Unsupported 5QI value (#59) | +| 184 | Invalid PTI value (#81) | +| 186 | Message not compatible with protocol state (#101) | +| 190 | Network failure (#38) | +| 191 | Reactivation requested (#39) | +| 192 | PDU session type IPv4 only allowed (#50) | +| 193 | PDU session type IPv6 only allowed (#51) | +| 196 | PDU session type IPv4v6 only allowed (#57) | +| 197 | PDU session type Unstructured only allowed (#58) | +| 202 | PDU session does not exist (#54) | +| 205 | Insufficient resources for specific slice and DNN (#67) | +| 206 | Not supported SSC mode (#68) | +| 207 | Insufficient resources for specific slice (#69) | +| 208 | Message type not compatible with protocol state (#98) | +| 209 | Information element non-existent or not implemented (#99) | +| 213 | Missing or unknown DNN in a slice (#70) | +| 220 | Out of LADN service area (#46) | +| 221 | PTI mismatch (#47) | +| 222 | Maximum data rate per UE for user-plane integrity protection is too low (#82) | +| 223 | Semantic error in the QoS operation (#83) | +| 224 | Syntactical error in the QoS operation (#84) | +| 225 | Invalid mapped EPS bearer identity (#85) | +| 230 | PDU session type Ethernet only allowed (#61) | + +NOTE: Values in parentheses are 3GPP TS 24.501 [161] cause codes. + +9.2.2.3 Void + +9.2.2.4 Void + +### 9.2.3 VBS, VGCS and eMLPP-related errors + +| Numeric | Text | +|---------|------| +|---------|------| + +- 151 VBS/VGCS not supported by the network +- 152 No service subscription on SIM +- 153 No subscription for group ID +- 154 Group Id not activated on SIM +- 155 No matching notification +- 156 VBS/VGCS call already present +- 157 Congestion +- 158 Network failure +- 159 Uplink busy +- 160 No access rights for SIM file +- 161 No subscription for priority +- 162 operation not applicable or not possible +- 163 Group Id prefixes not supported +- 164 Group Id prefixes not usable for VBS +- 165 Group Id prefix value invalid + +### Implementation + +Mandatory for numeric format codes applicable to implemented command set. + +## 9.3 Mobile termination error result code +CMOLRE + +### 9.3.1 General + +The operation of +CMOLRE: <err> unsolicited result code is similar to the regular ERROR result code. The format of <err> can be either numeric or verbose. This is set with command +CMOLRE (refer clause 9.1a). + +<err> values (numeric format followed by verbose format): + +### 9.3.2 Errors + +| Numeric | Text | +|---------|----------------------------------------------------------| +| 0 | Method not supported | +| 1 | Additional assistance data required | +| 2 | Not enough satellites | +| 3 | UE busy (See NOTE) | +| 4 | Network error | +| 5 | Failed to open internet connection, too many connections | +| 6 | Failed to open internet connection, too many users | +| 7 | Failure due to handover | +| 8 | Internet connection failure | +| 9 | Memory error | +| 255 | Unknown error | + +NOTE: Error code 3 (UE busy) indicates there is already one ongoing positioning session and the UE does not support multiple simultaneous sessions + +## 9.4 Informative examples + +An example of TA responses with all three +CMEE values when MT manufacturer identification is requested but MT is not connected to the TA: + +``` +AT+CMEE=0 (+CMEE ERROR shall not be used) +OK +AT+CGMI +ERROR +AT+CMEE=1 (use numeric <err>) +OK +AT+CGMI ++CME ERROR: 1 +AT+CMEE=2 (use verbose <err>) +``` + +OK +AT+CGMT ++CME ERROR: no connection to phone + +## 10 Commands for packet domain + +### 10.0 General + +This clause defines commands that a TE can use to control a MT supporting packet switched services. + +Packet Domain MTs vary widely in functionality. At one extreme, an advanced MT can support multiple PDP types, and use multiple external networks and QoS profiles. At the other extreme, an MT can support only a single PDP type using a single external network, and rely on the HLR to contain the PDP context definition. + +A comprehensive set of Packet Domain-specific commands is defined in clause 10.1 to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new PDP types and interface protocols, merely by defining new values for many of the parameters. Multiple contexts can be activated if the interface link-layer protocol is able to support them. The commands use the extended information and error message capabilities described in this specification. + +For MTs of intermediate complexity, most commands have simplified forms where certain parameters can be omitted. + +For certain simple MTs, and for backwards compatibility with existing communications software as defined in 3GPP TS 23.060 [47], it is possible to control access to the Packet Domain using existing modem-compatible commands. A special dial-string syntax is defined for use with the D command. This "modem compatible" mode of operation is described in clause 10.2. + +A discussion on the interaction of the AT commands, Packet Domain Management and Packet Data Protocols, together with examples of command sequences for some applications can be found in 3GPP TS 23.060 [47] and 3GPP TS 27.060 [34]. + +### 10.1 Commands specific to MTs supporting the packet domain + +#### 10.1.0 General remark about EPS bearer contexts and PDP contexts + +According to 3GPP TS 23.401 [82], there is a 1 to 1 mapping between active EPS bearer context and active PDP context: + +- An active default EPS bearer context is associated with an active non secondary PDP context. +- An active dedicated EPS bearer context is associated with an active secondary PDP context. + +In consequence to the implicit logical relation between EPS PDN connection and its associated Default EPS Bearer, hereafter a same non secondary PDP context identifier <p\_cid> can be used to refer either an EPS PDN connection context or its associated Default EPS Bearer context. + +As dedicated EPS bearer contexts are activated by the network, the network can then activate a new dedicated EPS bearer or modify an existing one to fulfil the request. For bearer resources activated by the network a context identifier is allocated by the MT/TA. + +For easy reading the term PDP context is used for PDP contexts in UMTS/GPRS as well as PDN/default EPS bearers and traffic flows in EPS. + +The feature "initial PDP context" may be supported and is a manufacturer specific option. For this option, the context with <cid>=0 (context number 0) is defined upon startup and does not need to be created with the +CGDCONT command. The initial PDP context has particular manufacturer specific default settings disassociated with any other default settings of +CGDCONT. When in E-UTRAN or according to the AT-command +CIPCA in GERAN and UTRAN, the initial PDP context is automatically activated by the MT following a successful registration to the + +network. If all active contexts are deactivated, the initial PDP context can be (re)established. This is manufacturer specific and depends on the current RAT as well as how the active contexts are deactivated. + +NOTE 1: Care must be taken to secure that repetitive PDP context activations / deactivations are not performed and that PDP contexts are not activated in situations where it is a determined choice by the terminal or the network to discontinue connectivity. Examples of such deliberate discontinuation of connectivity are the AT-commands +CGATT=0 or +CGACT=0, receipt of a detach request from the network with "re-attach not required" or when all PDP contexts are deactivated by the network. + +**Table 10.1.0-1: AT commands/results applicable for EPS +(equivalence between PDP context / PDN Connection or Default EPS Bearer)** + +| AT commands | Comments | +|----------------|----------------------------------------------------| +| +CGDCONT | Used to define PDN connection for EPS. | +| +CGACT | Used to activate a bearer resource for EPS. | +| +CGCONTRDP | Used to show dynamically allocated PDN parameters. | +| +CGEV: xxx ... | Used to indicate EPS bearers operations status. | + +**Table 10.1.0-2: AT commands/results applicable for EPS +(equivalence between PDP context / EPS Bearer Resources)** + +| AT commands | Comments | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGACT | Used to activate a modification of a PDP context or EPS bearer resource. | +| +CGDSCONT | Used to define EPS Bearer Resource for a specific PDN for EPS. | +| +CGSCONTRDP | Used to show dynamically allocated EPS Bearer Resource parameters. | +| +CGCMOD | Used to request a modification of a PDP context or EPS Bearer Resource. | +| +CGTFT | Used to define a Traffic Flow Template for a PDP context or a Traffic Flow Aggregate for an EPS bearer resource. | +| +CGTFTRDP | Used to show the network assigned Traffic Flow Template for an EPS bearer resource. | +| +CGEQOS | Used to define the EPS bearer resource Quality of Service parameter.<br>In UMTS/GPRS mode this would hold a mapping function to the UMTS/GPRS QoS parameters. | +| +CGEQOSRDP | Used to show the network assigned EPS QoS parameters for an EPS bearer resource.<br>In UMTS/GPRS mode this would hold a mapping function to the UMTS/GPRS QoS parameters. | +| +CGEV: xxx ... | Used to indicate EPS PDN connection and bearer resources operations status | + +**Table 10.1.0-3: AT commands applicable for EPS** + +| AT commands | Comments | +|-------------|--------------------------------------------------------------| +| +CGATT | Used to attach/detach the MT from the Packet Domain service. | + +NOTE 2: The above is not a complete list of AT commands for EPS but only those applicable to PDN connections and EPS bearer resources. + +## 10.1.00 General remark about 5GS PDU sessions and EPS PDN connections + +According to 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161] there exists a one to one mapping between a 5GS PDU session and an EPS PDN connection. A 5GS PDU session is a set of QoS flows consisting of one QoS flow of the default QoS rule and optionally one or more QoS flows of non-default QoS rule. A PDN connection is set of EPS bearer contexts and consists of at least one default EPS bearer context and optionally one or more dedicated EPS bearer contexts. A PDU session can be mapped to one default EPS bearer context and zero or more dedicated bearer EPS bearer contexts. An EPS bearer context can be mapped to one or more QoS flows. The mapping between a QoS flow and an EPS bearer context is not always one to one. + +**Table 10.1.00-1: AT commands/results applicable for 5GS PDU session (equivalence between PDU Session / PDN Connection)** + +| AT commands | Comments | +|----------------|----------------------------------------------------------------| +| +CGDCONT | Used to define a 5GS PDU session | +| +CGACT | Used to activate a 5GS PDU session. | +| +CCSTATE REQ | Used to change the state of a PDU session | +| +CGCMOD | Used to modify a 5GS PDU session | +| +CGCONTRDP | Used to show dynamically allocated 5GS PDU session parameters. | +| +CGEV: xxx ... | Used to indicate 5GS PDU session operations status. | + +**Table 10.1.00-2: AT commands/results applicable for 5GS QoS flow (equivalence between QoS flow / EPS bearer resources)** + +| AT commands | Comments | +|-------------|--------------------------------------------------------------------------------------| +| +CGDSCONT | Used to define a 5GS QoS flow | +| +CGSCONTRDP | Used to show dynamically allocated 5GS QoS flow parameters | +| +CGTFT | Used to define QoS rules for a 5GS QoS flow | +| +CGTFTRDP | Used to show the network assigned QoS rules for a 5GS QoS flow | +| +C5GQOS | Used to define QoS flows of a 5GS PDU session | +| +C5GQOSRDP | Used to show the dynamically allocated QoS flows corresponding to a 5GS PDU session. | + +| | | +|--------------|----------------------------------------------------------| +| +C5GPDUAUTHS | Used to define 5G PDU Session Authentication settings. | +| +C5GPDUAUTHR | Used to indicate 5G PDU Session Authentication Response. | + +**Table 10.1.00-3: AT commands applicable for 5GS** + +| AT commands | Comments | +|--------------|-----------------------------------------------------------------------------------------| +| +CGATT | Used to attach/detach the MT from the packet domain service. | +| +C5GREG | Indicates 5GS network registration status over 3GPP access | +| +C5GREGN3GPP | Indicates 5GS network registration status over non-3GPP access | +| +C5GRDN3GPP | Used to register the MT to, or deregister the MT from, 5GS network over non-3GPP access | + +NOTE: The above is not a complete list of AT commands for 5GS but only those applicable to 5GS PDU sessions and 5GS QoS flows. + +### 10.1.1 Define PDP context +CGDCONT + +**Table 111: +CGDCONT parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| +CGDCONT=<cid>[,<PDP_type>[,<APN>[,<PDP_addr>[,<d_comp>[,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_req>[,<old-cid>[,<ATSSS-ST>[,<LADN-DNN_ind>[,<MA-PDU-session-information>[,<Ethernet_MTU_discovery>[,<Unstructured_Link_MTU_discovery>[,<PDU_Pair_ID>[,<RSN>[,<ECSConf_info_ind>>[,<EDC_support>[,<SDNAEPC_support>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] | | + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGDCONT? | [+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_req>[,<old-cid>[,<ATSSS-ST>[,<LADN-DNN_ind>[,<MA-PDU-session-information>[,<Ethernet_MTU_discovery>[,<Unstructured_Link_MTU_discovery>[,<PDU_Pair_ID>[,<RSN>[,<ECSConf_info_ind>[,<EDC_support>[,<SDNAEPC_support>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]<br><br>[<CR><LF>+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_req>[,<old-cid>[,<ATSSS-ST>[,<LADN-DNN_ind>[,<MA-PDU-session-information>[,<Ethernet_MTU_discovery>[,<Unstructured_Link_MTU_discovery>[,<PDU_Pair_ID>[,<RSN>[,<ECSConf_info_ind>[,<EDC_support>[,<SDNAEPC_support>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]<br><br>[...]]] | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGDCONT=? | +CGDCONT: (range of supported <cid>s), <PDP_type>, , , (list of supported <d_comp>s), (list of supported <h_comp>s), (list of supported <IPv4AddrAlloc>s), (list of supported <request_type>s), (list of supported <P-CSCF_discovery>s), (list of supported <IM_CN_Signalling_Flag_Ind>s), (list of supported <NSLPI>s), (list of supported <securePCO>s), (list of supported <IPv4_MTU_discovery>s), (list of supported <Local_Addr_Ind>s), (list of supported <Non-IP_MTU_discovery>s), (list of supported <Reliable_Data_Service>s), (list of supported <SSC_mode>s), , , (list of supported <Pref_access_type>s), (list of supported <RQoS_ind>s), (list of supported <MH6-PDU>s), (list of supported <Always-on_req>s), (range of supported <old-cid>s), (list of supported <ATSSS-ST>s), (list of supported <LADN-DNN_ind>s), (list of supported <MA-PDU-session-information>s), (list of supported <Ethernet_MTU_discovery>s), (list of supported <Unstructured_Link_MTU_discovery>s), (range of supported <PDU_Pair_ID>s), (list of supported <RSN>s), (list of supported <ECSConf_info_ind>s) [<CR><LF>+CGDCONT: (range of supported <cid>s), <PDP_type>, , , (list of supported <d_comp>s), (list of supported <h_comp>s), (list of supported <IPv4AddrAlloc>s), (list of supported <request_type>s), (list of supported <P-CSCF_discovery>s), (list of supported <IM_CN_Signalling_Flag_Ind>s), (list of supported <NSLPI>s), (list of supported <securePCO>s), (list of supported <IPv4_MTU_discovery>s), (list of supported <Local_Addr_Ind>s), (list of supported <Non-IP_MTU_discovery>s), (list of supported <Reliable_Data_Service>s), (list of supported <SSC_mode>s), , , (list of supported <Pref_access_type>s), (list of supported <RQoS_ind>s), (list of supported <MH6-PDU>s), (list of supported <Always-on_req>s), (range of supported <old-cid>s), (list of supported <ATSSS-ST>s), (list of supported <LADN-DNN_ind>s), (list of supported <MA-PDU-session-information>s), (list of supported <Ethernet_MTU_discovery>s), (list of supported <Unstructured_Link_MTU_discovery>s), (range of supported <PDU_Pair_ID>s), (list of supported <RSN>s), (list of supported <ECSConf_info_ind>s), (list of supported <EDC_support>s), (list of supported <SDNAEPC_support>s) [...]] | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. + +## Description + +The set command specifies PDP context parameter values for a PDP context identified by the (local) context identification parameter, <cid> and also allows the TE to specify whether security protected transmission of ESM information is requested, because the PCO can include information that requires ciphering. There can be other reasons for the UE to use security protected transmission of ESM information, e.g. if the UE needs to transfer an APN. The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command. + +For EPS the PDN connection and its associated EPS default bearer is identified herewith. + +For 5GS the PDU session and its associated QoS flow of the default QoS rule is identified herewith. + +A special form of the set command, +CGDCONT=<cid> causes the values for context number <cid> to become undefined. + +If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0. As all other contexts, the parameters for <cid>=0 can be modified with +CGDCONT. If the initial PDP context is supported, +CGDCONT=0 resets context number 0 to its particular default settings. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. If the MT supports several PDP types, <PDP\_type>, the parameter value ranges for each <PDP\_type> are returned on a separate line. + +## Defined values + +<cid>: integer type; specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1 or if the initial PDP context is supported (see clause 10.1.0), minimum value = 0) is returned by the test form of the command. + +NOTE 1: The <cid>s for network-initiated PDP contexts will have values outside the ranges indicated for the <cid> in the test form of the commands +CGDCONT and +CGDSCONT. + +<PDP\_type>: string type; specifies the type of packet data protocol. The default value is manufacturer specific. + +| | | +|--------------|------------------------------------------------------------------------------------------------| +| X.25 | ITU-T/CCITT X.25 layer 3 (Obsolete) | +| IP | Internet Protocol (IETF STD 5 [103]) | +| IPv6 | Internet Protocol, version 6 (see RFC 2460 [106]) | +| IPv4V6 | Virtual <PDP_type> introduced to handle dual IP stack UE capability. (See 3GPP TS 24.301 [83]) | +| OSPIH | Internet Hosted Octet Stream Protocol (Obsolete) | +| PPP | Point to Point Protocol (IETF STD 51 [104]) | +| Non-IP | Transfer of Non-IP data to external packet data network (see 3GPP TS 23.401 [82]) | +| Ethernet | Ethernet protocol (IEEE 802.3) | +| Unstructured | Transfer of Unstructured data to the Data Network via N6 (see 3GPP TS 23.501 [165]) | + +NOTE 2: Only IP, IPv6, IPv4V6, Non-IP and Ethernet values are supported for EPS services. Only IP, IPv6, IPv4V6, Ethernet and Unstructured values are supported for 5GS service. + +<APN>: string type; a logical name that is used to select the GGSN or the external packet data network. + +If the value is null or omitted, then the subscription value will be requested. + +<PDP\_addr>: string type; identifies the MT in the address space applicable to the PDP. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +CGDCONT. + +NOTE 3: The value of this parameter is ignored with the set command. The parameter is included in the set command for backwards compatibility reasons only. + +<d\_comp>: integer type; controls PDP data compression (applicable for SNDPCP only) (refer 3GPP TS 44.065 [61]). + +- 0 off +- 1 on (manufacturer preferred compression) +- 2 V.42bis +- 3 V.44 + +<h\_comp>: integer type; controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]). + +- 0 off +- 1 on (manufacturer preferred compression) +- 2 RFC 1144 [105] (applicable for SNDPCP only) +- 3 RFC 2507 [107] +- 4 RFC 3095 [108] (applicable for PDCP only) + +<IPv4AddrAlloc>: integer type; controls how the MT/TA requests to get the IPv4 address information. + +- 0 IPv4 address allocation through NAS signalling +- 1 IPv4 address allocated through DHCP + +<request\_type>: integer type; indicates the type of PDP context activation request for the PDP context, see 3GPP TS 24.501 [161] (clause 6.4.1), 3GPP TS 24.301 [83] (clause 6.5.1.2) and 3GPP TS 24.008 [8] (clause 10.5.6.17). If the initial PDP context is supported (see clause 10.1.0) it is not allowed to assign <id>=0 for emergency (bearer) services. According to 3GPP TS 24.008 [8] (clause 4.2.4.2.2 and clause 4.2.5.1.4) and 3GPP TS 24.301 [83] (clause 5.2.2.3.3 and clause 5.2.3.2.2), a separate PDP context must be established for emergency (bearer) services. + +NOTE 4: If the PDP context for emergency (bearer) services is the only activated context, only emergency calls are allowed, see 3GPP TS 23.401 [82] clause 4.3.12.9. + +- 0 PDP context is for new PDP context establishment or for handover from a non-3GPP access network (how the MT decides whether the PDP context is for new PDP context establishment or for handover is implementation specific) +- 1 PDP context is for emergency (bearer) services +- 2 PDP context is for new PDP context establishment +- 3 PDP context is for handover from a non-3GPP access network +- 4 PDP context is for handover of emergency (bearer) services from a non-3GPP access network +- 5 context is for MA PDU session establishment + +NOTE 5: A PDP context established for handover of emergency (bearer) services from a non-3GPP access network has the same status as a PDP context for emergency (bearer) services. + +<P-CSCF\_discovery>: integer type; influences how the MT/TA requests to get the P-CSCF address, see 3GPP TS 24.229 [89] annex B and annex L. + +- 0 Preference of P-CSCF address discovery not influenced by +CGDCONT + +- 1 Preference of P-CSCF address discovery through NAS signalling +- 2 Preference of P-CSCF address discovery through DHCP + +<IM\_CN\_Signalling\_Flag\_Ind>: integer type; indicates to the network whether the PDP context is for IM CN subsystem-related signalling only or not. + +- 0 UE indicates that the PDP context is not for IM CN subsystem-related signalling only +- 1 UE indicates that the PDP context is for IM CN subsystem-related signalling only + +<NSLPI>: integer type; indicates the NAS signalling priority requested for this PDP context: + +- 0 indicates that this PDP context is to be activated with the value for the low priority indicator configured in the MT. +- 1 indicates that this PDP context is to be activated with the value for the low priority indicator set to "MS is not configured for NAS signalling low priority". + +NOTE 6: The MT utilises the provide NSLPI information as specified in 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8]. + +<securePCO>: integer type. Specifies if security protected transmission of PCO is requested or not (applicable for EPS only, see 3GPP TS 23.401 [82] clause 6.5.1.2). + +- 0 Security protected transmission of PCO is not requested +- 1 Security protected transmission of PCO is requested + +<IPv4\_MTU\_discovery>: integer type; influences how the MT/TA requests to get the IPv4 MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3. + +- 0 Preference of IPv4 MTU size discovery not influenced by +CGDCONT +- 1 Preference of IPv4 MTU size discovery through NAS signalling + +<Local\_Addr\_Ind>: integer type; indicates to the network whether or not the MS supports local IP address in TFTs (see 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8] clause 10.5.6.3). + +- 0 indicates that the MS does not support local IP address in TFTs +- 1 indicates that the MS supports local IP address in TFTs + +<Non-IP\_MTU\_discovery>: integer type; influences how the MT/TA requests to get the Non-IP MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3. + +- 0 Preference of Non-IP MTU size discovery not influenced by +CGDCONT +- 1 Preference of Non-IP MTU size discovery through NAS signalling + +<Reliable\_Data\_Service>: integer type; indicates whether the UE is using Reliable Data Service for a PDN connection or not, see 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8] clause 10.5.6.3. + +- 0 Reliable Data Service is not being used for the PDN connection +- 1 Reliable Data Service is being used for the PDN connection + +<SSC\_mode>: integer type; indicates the session and service continuity (SSC) mode for the PDU session in 5GS, see 3GPP TS 23.501 [165]. + +- 0 indicates that the PDU session is associated with SSC mode 1 +- 1 indicates that the PDU session is associated with SSC mode 2 +- 2 indicates that the PDU session is associated with SSC mode 3 + +<S-NSSAI>: string type in hexadecimal character format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the PDU session for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. For the format and the encoding of S-NSSAI, see also 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. The <S-NSSAI> has one of the forms: + +sst only slice/service type (SST) is present +sst;mapped\_sst SST and mapped configured SST are present +sst.sd SST and slice differentiator (SD) are present +sst.sd;mapped\_sst SST, SD and mapped configured SST are present +sst.sd;mapped\_sst.mapped\_sd SST, SD, mapped configured SST and mapped configured SD are present + +<Pref\_access\_type>: integer type; indicates the preferred access type for the PDU session in 5GS, see 3GPP TS 23.503 [184] and 3GPP TS 24.526 [185]. + +- 0 indicates that the preferred access type is 3GPP access +- 1 indicates that the preferred access type is non-3GPP access + +<RQoS\_ind>: integer type; indicates whether the UE supports reflective QoS for the PDU session, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +- 0 indicates that reflective QoS is not supported for the PDU session +- 1 indicates that reflective QoS is supported for the PDU session + +<MH6-PDU>: integer type; indicates whether the UE supports IPv6 multi-homing for the PDU session, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +- 0 indicates that IPv6 multi-homing is not supported for the PDU session +- 1 indicates that IPv6 multi-homing is supported for the PDU session + +<Always-on\_req>: integer type; indicates whether the UE requests to establish the PDU session as an always-on PDU session, see 3GPP TS 24.501 [161]. + +- 0 always-on PDU session is not requested +- 1 always-on PDU session is requested + +<old-cid>: integer type; indicates the context identifier of the QoS flow of the default QoS rule of the SSC mode 2 or SSC mode 3 PDU session where the network requests relocation of the PDU session anchor. + +<ATSSS-ST>: integer type; indicates the "Supported ATSSS steering functionalities and steering modes (ATSSS-ST)" for the PDU session in 5GS, see 3GPP TS 24.501 [161]. + +- 0 ATSSS not supported +- 1 ATSSS Low-Layer functionality with any steering mode supported +- 2 MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported +- 3 MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode supported + +<LADN-DNN\_ind>: integer type; indicates whether the PDP context is for a LADN DNN, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +- 0 indicates that the PDP context is not for a LADN DNN +- 1 indicates that the PDP context is for a LADN DNN + +<MA-PDU-session-information>: integer type; indicates the value of MA PDU session information, see 3GPP TS 24.501 [161]. + +- 1 MA PDU session network upgrade is allowed + +<Ethernet\_MTU\_discovery>: integer type; influences how the MT/TA requests to get the Ethernet frame payload MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3. + +0 Preference of Ethernet frame payload MTU size discovery not influenced by +CGDCONT + +1 Preference of Ethernet frame payload MTU size discovery through NAS signalling + +<Unstructured\_Link\_MTU\_discovery>: integer type; influences how the MT/TA requests to get the unstructured link MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3. + +0 Preference of unstructured link MTU size discovery not influenced by +CGDCONT + +1 Preference of unstructured link MTU size discovery through NAS signalling + +<PDU\_Pair\_ID>: integer type; indicates the value of PDU session pair ID, see 3GPP TS 24.501 [161] and 3GPP TS 24.526 [185]. + +<RSN>: integer type; indicates the value of RSN, see 3GPP TS 24.501 [161] and 3GPP TS 24.526 [185]. + +0 indicates that the RSN is set to v1 + +1 indicates that the RSN is set to v2 + +<ECSConf\_info\_ind>: integer type; indicates whether the PDP context is for an ECS Configuration information, see 3GPP TS 23.558 [187] and 3GPP TS 24.501 [161]. + +0 indicates that ECS Configuration information is requested in the PCO + +1 indicates that ECS Configuration information is not requested in the PCO + +<EDC\_support>: integer type; indicates whether UE supports EDC for the PDU session being established, see 3GPP TS 24.501 [161]. + +0 indicates that UE does not support EDC + +1 indicates that UE supports EDC + +<SDNAEPC\_support>: integer type; indicates if the UE supports Secondary DN authentication and authorization over EPC, see 3GPP TS 24.301 [83], clause 6.5.1.2 , 3GPP TS 24.501 [161], clause 9.11.4.1 and clause 6.4.1.2. + +0 Secondary DN authentication and authorization over EPC not supported + +1 Secondary DN authentication and authorization over EPC supported + +## Implementation + +Mandatory unless only a single subscribed context is supported. + +## 10.1.2 Define secondary PDP context +CGDSCONT + +**Table 112: +CGDSCONT parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGDSCONT=<cid>,<p_cid>[,<d_comp>[,<h_comp>[,<IM_CN_Signalling_Flag_Ind>]]] | | +| +CGDSCONT? | [+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>,<IM_CN_Signalling_Flag_Ind>]<br>[<CR><LF>+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>,<IM_CN_Signalling_Flag_Ind>]<br>[...]] | + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGDSCONT=? | +CGDSCONT: (range of supported <cid>s), (list of <p_cid>s for active primary contexts), (list of supported <d_comp>s), (list of supported <h_comp>s), (list of supported <IM_CN_Signalling_Flag_Ind>s) | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +## Description + +The set command specifies PDP context parameter values for a Secondary PDP context identified by the (local) context identification parameter, <cid>. The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command. + +In EPS the command is used to define traffic flows. + +In 5GS the command is used to define QoS flows of non-default QoS rule. + +A special form of the set command, +CGDSCONT=<cid> causes the values for context number <cid> to become undefined. + +NOTE: If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. + +## Defined values + +<cid>: integer type; which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command. + +NOTE: The <cid>s for network-initiated PDP contexts will have values outside the ranges indicated for the <cid> in the test form of the commands +CGDCONT and +CGDSCONT. + +<p\_cid>: integer type; specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values is returned by the test form of the command. + +<d\_comp>: integer type; controls PDP data compression (applicable for SNDPCP only) (refer 3GPP TS 44.065 [61]). + +- 0 off +- 1 on (manufacturer preferred compression) +- 2 V.42bis +- 3 V.44 + +<h\_comp>: integer type; controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]). + +- 0 off +- 1 on (manufacturer preferred compression) +- 2 RFC 1144 [105] (applicable for SNDPCP only) +- 3 RFC 2507 [107] +- 4 RFC 3095 [108] (applicable for PDCP only) + +<IM\_CN\_Signalling\_Flag\_Ind>: integer type; indicates to the network whether the PDP context is for IM CN subsystem-related signalling only or not. + +- 0 UE indicates that the PDP context is not for IM CN subsystem-related signalling only +- 1 UE indicates that the PDP context is for IM CN subsystem-related signalling only + +### **Implementation** + +Optional. + +### 10.1.3 Traffic flow template +CGTFT + +**Table 113: +CGTFT parameter command syntax** + +| Command | Possible Response(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <pre>+CGTFT=<cid>[,<packet filter identifier>,<evaluation precedence index>[,<remote address and subnet mask>[,<protocol number (ipv4) / next header (ipv6)>[,<local port range>[,<remote port range>[,<ipsec security parameter index (spi)>[,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>[,<flow label (ipv6)>[,<direction>[,<local address and subnet mask>[,<QRI>[,<traffic_segregation>[,<d estination MAC address>[,<source MAC address>[,<802.1Q C-TAG VID>[,<802.1Q S-TAG VID>[,<802.1Q C-TAG PCP/DEI>[,<802.1Q S-TAG PCP/DEI>[,<ethertype>]]]]]]]]]]]]]]]]]] ]</pre> | <pre>+CME ERROR: <err></pre> | +| <pre>+CGTFT?</pre> | <pre>[+CGTFT: <cid>,<packet filter identifier>,<evaluation precedence index>,<remote address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<local port range>,<remote port range>,<ipsec security parameter index (spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>,<local address and subnet mask>,<QRI>,<traffic_segregation>,<dest ination MAC address>,<source MAC address>,<802.1Q C-TAG VID>,<802.1Q S- TAG VID>,<802.1Q C-TAG PCP/DEI>,<802.1Q S-TAG PCP/DEI>,<ethertype>] [<CR><LF>+CGTFT: <cid>,<packet filter identifier>,<evaluation precedence index>,<remote address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<local port range>, <remote port range>,<ipsec security parameter index (spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>,<local address and subnet mask>,<QRI>,<traffic_segregation>,<dest ination MAC address>,<source MAC address>,<802.1Q C-TAG VID>,<802.1Q S- TAG VID>,<802.1Q C-TAG PCP/DEI>,<802.1Q S-TAG PCP/DEI>,<ethertype> [...]]</pre> | + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGTFT=? | <p>+CGTFT: <PDP_type>, (list of supported <packet filter identifier>s), (list of supported <evaluation precedence index>s), (list of supported <remote address and subnet mask>s), (list of supported <protocol number (ipv4) / next header (ipv6)>s), (list of supported <local port range>s), (list of supported <remote port range>s), (list of supported <ipsec security parameter index (spi)>s), (list of supported <type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>s), (list of supported <flow label (ipv6)>s), (list of supported <direction>s), (list of supported <local address and subnet mask>s), (range of supported <QRI>s), (list of supported <traffic_segregation>s), (range of supported <destination MAC address>s), (range of supported <source MAC address>s), (range of supported <802.1Q C-TAG VID>s), (range of supported <802.1Q S-TAG VID>s), (range of supported <802.1Q C-TAG PCP/DEI>s), (range of supported <802.1Q S-TAG PCP/DEI>s), (range of supported <ethertype>s)</p> <p>[<CR><LF>+CGTFT: <PDP_type>, (list of supported <packet filter identifier>s), (list of supported <evaluation precedence index>s), (list of supported <remote address and subnet mask>s), (list of supported <protocol number (ipv4) / next header (ipv6)>s), (list of supported <local port range>s), (list of supported <remote port range>s), (list of supported <ipsec security parameter index (spi)>s), (list of supported <type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>s), (list of supported <flow label (ipv6)>s), (list of supported <direction>s), (list of supported <local address and subnet mask>s), (range of supported <QRI>s), (list of supported <traffic_segregation>s), (range of supported <destination MAC address>s), (range of supported <source MAC address>s), (range of supported <802.1Q C-TAG VID>s), (range of supported <802.1Q S-TAG VID>s), (range of supported <802.1Q C-TAG PCP/DEI>s), (range of supported <802.1Q S-TAG PCP/DEI>s), (range of supported <ethertype>s)</p> <p>[...]</p> | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +## Description + +This command allows the TE to specify a Packet Filter - PF for a Traffic Flow Template - TFT that is used in the GGSN and in the Packet GW for routing of packets onto different QoS flows towards the TE. The concept is further + +described in the 3GPP TS 23.060 [47], 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. A TFT consists of from one and up to 16 Packet Filters, each identified by a unique <packet filter identifier>. A Packet Filter also has an <evaluation precedence index> that is unique within all TFTs associated with all PDP contexts that are associated with the same PDP address. + +The set command specifies a Packet Filter that is to be added to the TFT stored in the MT and used for the context identified by the (local) context identification parameter, <cid>. The specified TFT will be stored in the GGSN, the Packet GW and UPF only at activation or MS-initiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGTFT command is effectively an extension to these commands. The Packet Filters consist of a number of parameters, each of which may be set to a separate value. + +A special form of the set command, +CGTFT=<cid> causes all of the Packet Filters in the TFT for context number <cid> to become undefined. At any time there may exist only one PDP context with no associated TFT amongst all PDP contexts associated to one PDP address. At an attempt to delete a TFT, which would violate this rule, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer clause 9.2 for possible <err> values. + +The read command returns the current settings for all Packet Filters for each defined context. + +The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. TFTs shall be used for PDP-type IP and PPP only. For PDP-type PPP a TFT is applicable only when IP traffic is carried over PPP. If PPP carries header-compressed IP packets, then a TFT cannot be used. + +#### Defined values + +<cid>: integer type. Specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<PDP\_type>: string type. Specifies the type of packet data protocol (see the +CGDCONT command). + +For the following parameters, see also 3GPP TS 23.060 [47], 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]: + +<packet filter identifier>: integer type. Value range is from 1 to 16. + +NOTE: While the numbering of packet filter identifier in this specification ranges from 1 to 16, the numbering of packet filter identifier in 3GPP TS 24.008 [8] ranges from 0 to 15. It is up to MT implementation to perform a mapping between the two value ranges. + +<evaluation precedence index>: integer type. The value range is from 0 to 255. + +<remote address and subnet mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: + +"a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or + +"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16", for IPv6. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +CGTFT. + +<protocol number (ipv4) / next header (ipv6)>: integer type. Value range is from 0 to 255. + +<local port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t". + +<remote port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t". + +<ipsec security parameter index (spi)>: numeric value in hexadecimal format. The value range is from 00000000 to FFFFFFFF. + +<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form "t.m". + +<flow label (ipv6)>: numeric value in hexadecimal format. The value range is from 00000 to FFFFF. Valid for IPv6 only. + +<direction>: integer type. Specifies the transmission direction in which the packet filter shall be applied. + +0 Pre-Release 7 TFT filter (see 3GPP TS 24.008 [8], table 10.5.162) + +Reserved (see 3GPP TS 24.501 [161], table 9.11.4.13.1) + +1 Uplink + +2 Downlink + +3 Bidirectional (Up & Downlink) + +<local address and subnet mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: + +"a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or + +"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16", for IPv6. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +CGTFT. + +<QRI>: integer type. Identifies the QoS rule, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +<traffic\_segregation>: integer type; indicates to the network whether traffic segregation is requested or not, see 3GPP TS 24.501 [161]. + +0 traffic segregation is not requested + +1 traffic segregation is requested + +<destination MAC address>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: "a1.a2.a3.a4.a5.a6". + +<source MAC address>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: "a1.a2.a3.a4.a5.a6". + +<802.1Q C-TAG VID>: numeric value in hexadecimal format. The value range is from 000 to FFF. + +<802.1Q S-TAG VID>: numeric value in hexadecimal format. The value range is from 000 to FFF. + +<802.1Q C-TAG PCP/DEI>: numeric value in hexadecimal format. The value range is from 0 to F. + +<802.1Q S-TAG PCP/DEI>: numeric value in hexadecimal format. The value range is from 0 to F. + +<ethertype>: numeric value in hexadecimal format. The value range is from 0000 to FFFF. + +Some of the above listed attributes may coexist in a Packet Filter while others mutually exclude each other, the possible combinations are shown in 3GPP TS 23.060 [47], 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +### Implementation + +Optional. + +## 10.1.4 Quality of service profile (requested) +CGQREQ + +Table 114: +CGQREQ parameter command syntax + +| Command | Possible Response(s) | +|-------------------------------------------------------------------------------|--------------------------------------------| +| +CGQREQ=[<cid>[, <precedence>[, <delay>, <reliability>[, <peak>[, <mean>]]]]] | | +| +CGQREQ? | [+CGQREQ: <cid>, <precedence>, <delay>, <r | + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | <pre> reliability>,<peak>,<mean>] [<CR><LF>+CGQREQ: <cid>,<precedence>,<delay>,<reliability>,<peak>,<mean> [...]] </pre> | +| +CGQREQ=? | <pre> +CGQREQ: <PDP_type>, (list of supported <precedence>s) , (list of supported <delay>s) , (list of supported <reliability>s) , (list of supported <peak>s) , (list of supported <mean>s) [<CR><LF>+CGQREQ: <PDP_type>, (list of supported <precedence>s) , (list of supported <delay>s) , (list of supported <reliability>s) , (list of supported <peak>s) , (list of supported <mean>s) [...]] </pre> | + +### Description + +This command allows the TE to specify a Quality of Service Profile that is used when the MT activates a PDP context. + +The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGQREQ command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. + +A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid> to become undefined. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. + +### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<PDP\_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command). + +The following parameters are defined in 3GPP TS 23.107 [46]: + +<precedence>: integer type; specifies the precedence class + +<delay>: integer type; specifies the delay class + +<reliability>: integer type; specifies the reliability class + +<peak>: integer type; specifies the peak throughput class + +<mean>: integer type; specifies the mean throughput class + +If a value is omitted for a particular class then the value is considered to be unspecified. + +### Implementation + +Optional. If the command is not implemented then all the values are considered to be unspecified. + +## 10.1.5 Quality of service profile (minimum acceptable) +CGQMIN + +**Table 115: +CGQMIN parameter command syntax** + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGQMIN=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]] | | +| +CGQMIN? | [+CGQMIN: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>]<br><br>[<CR><LF>+CGQMIN: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean><br>[...]] | +| +CGQMIN=? | +CGQMIN: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)<br><br>[<CR><LF>+CGQMIN: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)<br>[...]] | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +### Description + +This command allows the TE to specify a minimum acceptable profile which is checked by the MT against the negotiated profile when the PDP context is activated. + +The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGQMIN command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. + +A special form of the set command, +CGQMIN=<cid> causes the minimum acceptable profile for context number <cid> to become undefined. In this case no check is made against the negotiated profile. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. + +### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<PDP\_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command). + +The following parameters are defined in 3GPP TS 23.107 [46]: + +<precedence>: integer type; specifies the precedence class + +<delay>: integer type; specifies the delay class + +<reliability>: integer type; specifies the reliability class + +<peak>: integer type; specifies the peak throughput class + +`<mean>`: integer type; specifies the mean throughput class + +If a value is omitted for a particular class then this class is not checked. + +## Implementation + +Optional. If the command is not implemented then no check is made against the negotiated profile. + +### 10.1.6 3G quality of service profile (requested) +CGEQREQ + +**Table 116: +CGEQREQ parameter command syntax** + +| Command | Possible Response(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <code>+CGEQREQ=<cid>[,<Traffic class>[,<Maximum bitrate UL>[,<Maximum bitrate DL>[,<Guaranteed bitrate UL>[,<Guaranteed bitrate DL>[,<Delivery order>[,<Maximum SDU size>[,<SDU error ratio>[,<Residual bit error ratio>[,<Delivery of erroneous SDUs>[,<Transfer delay>[,<Traffic handling priority>[,<Source statistics descriptor>[,<Signalling indication>]]]]]]]]]]]]]</code> | | +| <code>+CGEQREQ?</code> | <code>[+CGEQREQ: <cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum bitrate DL>,<Guaranteed bitrate UL>,<Guaranteed bitrate DL>,<Delivery order>,<Maximum SDU size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery of erroneous SDUs>,<Transfer delay>,<Traffic handling priority>,<Source statistics descriptor>,<Signalling indication>]<br/><br/>[<CR><LF>+CGEQREQ: <cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum bitrate DL>,<Guaranteed bitrate UL>,<Guaranteed bitrate DL>,<Delivery order>,<Maximum SDU size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery of erroneous SDUs>,<Transfer delay>,<Traffic handling priority>,<Source Statistics Descriptor>,<Signalling Indication><br/><br/>[...]]</code> | +| <code>+CGEQREQ=?</code> | <code>+CGEQREQ: <PDP_type>, (list of supported <Traffic class>s) , (list of supported <Maximum bitrate UL>s) , (list of supported <Maximum bitrate DL>s) , (list of supported <Guaranteed bitrate UL>s) , (list of supported <Guaranteed bitrate DL>s) , (list of supported <Delivery order>s) , (list of supported <Maximum SDU size>s) , (list of supported <SDU error ratio>s) , (list of supported <Residual bit error ratio>s) , (list of supported <Delivery of erroneous SDUs>s) , (list of supported <Transfer delay>s) , (list of supported <Traffic handling priority>s) , (list of supported <Source statistics descriptor>s) , (list of supported</code> | + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | <Signalling indication>s)<br><br>[<CR><LF>+CGEQREQ: <PDP_type>, (list of supported <Traffic class>s), (list of supported <Maximum bitrate UL>s), (list of supported <Maximum bitrate DL>s), (list of supported <Guaranteed bitrate UL>s), (list of supported <Guaranteed bitrate DL>s), (list of supported <Delivery order>s), (list of supported <Maximum SDU size>s), (list of supported <SDU error ratio>s), (list of supported <Residual bit error ratio>s), (list of supported <Delivery of erroneous SDUs>s), (list of supported <Transfer delay>s), (list of supported <Traffic handling priority>s), (list of supported <Source statistics descriptor>s), (list of supported <Signalling indication>s)<br><br>[...]] | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +## Description + +This command allows the TE to specify a UMTS Quality of Service Profile that is used when the MT activates a PDP context. + +The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. The specified profile will be stored in the MT and sent to the network only at activation or MS-initiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGEQREQ command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. + +A special form of the set command, +CGEQREQ=<cid> causes the requested profile for context number <cid> to become undefined. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. + +## Defined values + +<cid>: integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands). + +<PDP\_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command). + +For the following parameters, see also 3GPP TS 23.107 [46]. + +<Traffic class>: integer type; indicates the type of application for which the UMTS bearer service is optimised (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 conversational +- 1 streaming +- 2 interactive +- 3 background +- 4 subscribed value + +If the Traffic class is specified as conversational or streaming, then the Guaranteed and Maximum bitrate parameters should also be provided. + +<Maximum bitrate UL>: integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=..., 32, ...). This parameter should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Maximum bitrate DL>: integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=..., 32, ...). If the parameter is set to '0' the subscribed value will be requested. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Guaranteed bitrate UL>: integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=..., 32, ...). If the parameter is set to '0' the subscribed value will be requested. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Guaranteed bitrate DL>: integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=..., 32, ...). If the parameter is set to '0' the subscribed value will be requested. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Delivery order>: integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 no +- 1 yes +- 2 subscribed value + +<Maximum SDU size>: integer type; (1,2,3,...) indicates the maximum allowed SDU size in octets. If the parameter is set to '0' the subscribed value will be requested (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<SDU error ratio>: string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as 'mEe'. As an example a target SDU error ratio of $5 \cdot 10^{-3}$ would be specified as "5E3" (e.g. AT+CGEQREQ=..., "5E3", ...). "0E0" means subscribed value (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Residual bit error ratio>: string type; indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as "mEe". As an example a target residual bit error ratio of $5 \cdot 10^{-3}$ would be specified as "5E3" (e.g. AT+CGEQREQ=..., "5E3", ...). "0E0" means subscribed value (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Delivery of erroneous SDUs>: integer type; indicates whether SDUs detected as erroneous shall be delivered or not (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 no +- 1 yes +- 2 no detect +- 3 subscribed value + +<Transfer delay>: integer type; (0,1,2,...) indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds. If the parameter is set to '0' the subscribed value will be requested (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +`<Traffic handling priority>`: integer type; (1,2,3,...) specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers. If the parameter is set to '0' the subscribed value will be requested (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +`<Source Statistics Descriptor>`: integer type; specifies characteristics of the source of the submitted SDUs for a PDP context. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 Characteristics of SDUs is unknown +- 1 Characteristics of SDUs corresponds to a speech source + +`<Signalling Indication>`: integer type; indicates signalling content of submitted SDUs for a PDP context. This parameter should be provided if the Traffic class is specified as interactive (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 PDP context is not optimized for signalling +- 1 PDP context is optimized for signalling`<PDP_type>` (see +CGDCONT and +CGDSCONT commands). + +If a value is omitted for a particular class then the value is considered to be unspecified. + +NOTE: When in dual mode with EPS the MT provides a mapping function to EPS Quality of Service parameter used for an EPS bearer resource activation request. + +## Implementation + +Optional. If the command is not implemented then all the values are considered to be unspecified. + +### 10.1.7 3G quality of service profile (minimum acceptable) +CGEQMIN + +**Table 117: +CGEQMIN parameter command syntax** + +| <b>Command</b> | <b>Possible Response(s)</b> | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGEQMIN= <code><cid></code> [, <code><Traffic class></code> [, <code><Maximum bitrate UL></code> [, <code><Maximum bitrate DL></code> [, <code><Guaranteed bitrate UL></code> [, <code><Guaranteed bitrate DL></code> [, <code><Delivery order></code> [, <code><Maximum SDU size></code> [, <code><SDU error ratio></code> [, <code><Residual bit error ratio></code> [, <code><Delivery of erroneous SDUs></code> [, <code><Transfer delay></code> [, <code><Traffic handling priority></code> [, <code><Source statistics descriptor></code> [, <code><Signalling indication></code> ]]]]]]]]]]]]]]] | | +| +CGEQMIN? | [+CGEQMIN: <code><cid></code> , <code><Traffic class></code> , <code><Maximum bitrate UL></code> , <code><Maximum bitrate DL></code> , <code><Guaranteed bitrate UL></code> , <code><Guaranteed bitrate DL></code> , <code><Delivery order></code> , <code><Maximum SDU size></code> , <code><SDU error ratio></code> , <code><Residual bit error ratio></code> , <code><Delivery of erroneous SDUs></code> , <code><Transfer delay></code> , <code><Traffic handling priority></code> , <code><Source statistics descriptor></code> , <code><Signalling indication></code> ]<br><br>[<CR><LF>+CGEQMIN: <code><cid></code> , <code><Traffic class></code> , <code><Maximum bitrate UL></code> , <code><Maximum bitrate DL></code> , <code><Guaranteed bitrate UL></code> , <code><Guaranteed bitrate DL></code> , <code><Delivery order></code> , <code><Maximum SDU size></code> , <code><SDU error ratio></code> , <code><Residual bit error ratio></code> , <code><Delivery of erroneous</code> | + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | SDUs>,<Transfer delay>,<Traffic handling priority>,<Source statistics descriptor>,<Signalling indication><br><br>[...]] | +| +CGEQMIN=? | +CGEQMIN: <PDP_type>,(list of supported <Traffic class>s),(list of supported <Maximum bitrate UL>s),(list of supported <Maximum bitrate DL>s),(list of supported <Guaranteed bitrate UL>s),(list of supported <Guaranteed bitrate DL>s),(list of supported <Delivery order>s),(list of supported <Maximum SDU size>s),(list of supported <SDU error ratio>s),(list of supported <Residual bit error ratio>s),(list of supported <Delivery of erroneous SDUs>s),(list of supported <Transfer delay>s),(list of supported <Traffic handling priority>s),(list of supported <Source statistics descriptor>s),(list of supported <Signalling indication>s)<br><br>[<CR><LF>+CGEQMIN: <PDP_type>,(list of supported <Traffic class>s),(list of supported <Maximum bitrate UL>s),(list of supported <Maximum bitrate DL>s),(list of supported <Guaranteed bitrate UL>s),(list of supported <Guaranteed bitrate DL>s),(list of supported <Delivery order>s),(list of supported <Maximum SDU size>s),(list of supported <SDU error ratio>s),(list of supported <Residual bit error ratio>s),(list of supported <Delivery of erroneous SDUs>s),(list of supported <Transfer delay>s),(list of supported <Traffic handling priority>s),(list of supported <Source statistics descriptor>s),(list of supported <Signalling indication>s)<br><br>[...]] | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +## Description + +This command allows the TE to specify a minimum acceptable profile, which is checked by the MT against the negotiated profile returned in the PDP context establishment and PDP context modification procedures. + +The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>. The specified profile will be stored in the MT and checked against the negotiated profile only at activation or MS-initiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGEQMIN command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. + +A special form of the set command, +CGEQMIN=<cid> causes the minimum acceptable profile for context number <cid> to become undefined. In this case no check is made against the negotiated profile. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. + +### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands). + +<PDP\_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command). + +For the following parameters, see also 3GPP TS 23.107 [46]. + +<Traffic class>: integer type; indicates the type of application for which the UMTS bearer service is optimised (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 conversational +- 1 streaming +- 2 interactive +- 3 background + +<Maximum bitrate UL>: integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Maximum bitrate DL>: integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Guaranteed bitrate UL>: integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Guaranteed bitrate DL>: integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Delivery order>: integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 no +- 1 yes + +<Maximum SDU size>: integer type; (1,2,3,...) indicates the maximum allowed SDU size in octets (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<SDU error ratio>: string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratio of $5 \cdot 10^{-3}$ would be specified as "5E3" (e.g. AT+CGEQMIN=..., "5E3", ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Residual bit error ratio>: string type; indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as "mEe". As an example a target residual bit error ratio of $5 \cdot 10^{-3}$ would be specified as "5E3" (e.g. AT+CGEQMIN=..., "5E3", ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Delivery of erroneous SDUs>: integer type; indicates whether SDUs detected as erroneous shall be delivered or not (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 no +- 1 yes + +2 no detect + +<Transfer delay>: integer type; (0,1,2,...) indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Traffic handling priority>: integer type; (1,2,3,...) specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Source Statistics Descriptor>: integer type; specifies characteristics of the source of the submitted SDUs for a PDP context. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +0 Characteristics of SDUs is unknown + +1 Characteristics of SDUs corresponds to a speech source + +<Signalling Indication>: integer type; indicates signalling content of submitted SDUs for a PDP context. This parameter should be provided if the Traffic class is specified as interactive (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +0 PDP context is not optimized for signalling + +1 PDP context is optimized for signalling + +If a value is omitted for a particular class then the value is considered to be unspecified. + +### Implementation + +Optional. If the command is not implemented then no check is made against the negotiated profile. + +## 10.1.8 3G quality of service profile (negotiated) +CGEQNEG + +**Table 118: +CGEQNEG action command syntax** + +| Command | Possible Response(s) | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGEQNEG[=<cid>[, <cid>[, ...]]] | <p>[+CGEQNEG: <cid>, <Traffic class>, <Maximum bitrate UL>, <Maximum bitrate DL>, <Guaranteed bitrate UL>, <Guaranteed bitrate DL>, <Delivery order>, <Maximum SDU size>, <SDU error ratio>, <Residual bit error ratio>, <Delivery of erroneous SDUs>, <Transfer delay>, <Traffic handling priority>]</p> <p>[<CR><LF>+CGEQNEG: <cid>, <Traffic class>, <Maximum bitrate UL>, <Maximum bitrate DL>, <Guaranteed bitrate UL>, <Guaranteed bitrate DL>, <Delivery order>, <Maximum SDU size>, <SDU error ratio>, <Residual bit error ratio>, <Delivery of erroneous SDUs>, <Transfer delay>, <Traffic handling priority>]</p> <p>[...]</p> | +| +CGEQNEG=? | +CGEQNEG: (list of <cid>s associated with active contexts) | + +NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGEQNEG=[<cid>[, <cid>[, ...]]]. + +### Description + +This command allows the TE to retrieve the negotiated QoS profiles returned in the PDP context establishment procedure. + +The execution command returns the negotiated QoS profile for the specified context identifiers, <cid>s. The QoS profile consists of a number of parameters, each of which may have a separate value. + +If the parameter <cid> is omitted, the relevant information for all established PDP contexts are returned. + +The test command returns a list of <cid>s associated with active contexts. + +### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands). + +For the following parameters, see also 3GPP TS 23.107 [46]. + +<Traffic class>: integer type; indicates the type of application for which the UMTS bearer service is optimised (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +- 0 conversational +- 1 streaming +- 2 interactive +- 3 background + +<Maximum bitrate UL>: integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Maximum bitrate DL>: integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Guaranteed bitrate UL>: integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Guaranteed bitrate DL>: integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:..., 32, ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Delivery order>: integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +0 no + +1 yes + +<Maximum SDU size>: integer type; (1,2,3,...) indicates the maximum allowed SDU size in octets (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<SDU error ratio>: string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratio of $5 \cdot 10^{-3}$ would be specified as "5E3" (e.g. +CGEQNEG:..., "5E3", ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Residual bit error ratio>: string type; indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as "mEe". As an example a target residual bit error ratio of $5 \cdot 10^{-3}$ would be specified as "5E3" (e.g. +CGEQNEG:..., "5E3", ...) (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Delivery of erroneous SDUs>: integer type; indicates whether SDUs detected as erroneous shall be delivered or not (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +0 no + +1 yes + +2 no detect + +<Transfer delay>: integer type; (0,1,2,...) indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +<Traffic handling priority>: integer type; (1,2,3,...) specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers (refer 3GPP TS 24.008 [8] clause 10.5.6.5). + +If a value is omitted for a particular class then the value is considered to be unspecified. + +## Implementation + +Optional. + +## 10.1.9 PS attach or detach +CGATT + +**Table 119: +CGATT parameter command syntax** + +| Command | Possible Response(s) | +|----------------|--------------------------------------| +| +CGATT=<state> | +CME ERROR: <err> | +| +CGATT? | +CGATT: <state> | +| +CGATT=? | +CGATT: (list of supported <state>s) | + +### Description + +The execution command is used to attach the MT to, or detach the MT from, the Packet Domain service. After the command has completed, the MT remains in V.250 command state. If the MT is already in the requested state, the command is ignored and the OK response is returned. If the requested state cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer clause 9.2 for possible <err> values. + +NOTE 1: If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0. + +Any active PDP contexts will be automatically deactivated when the attachment state changes to detached. + +The read command returns the current Packet Domain service state. + +The test command is used for requesting information on the supported Packet Domain service states. + +NOTE 2: This command has the characteristics of both the V.250 action and parameter commands. Hence it has the read form in addition to the execution/set and test forms. + +### Defined values + +<state>: integer type; indicates the state of PS attachment + +0 detached + +1 attached + +### Implementation + +Optional. + +## 10.1.10 PDP context activate or deactivate +CGACT + +**Table 120: +CGACT parameter command syntax** + +| Command | Possible Response(s) | +|-------------------------------------------|-----------------------------------------------------------------------| +| +CGACT=[<state>[, <cid>[, <cid>[, ...]]]] | +CME ERROR: <err> | +| +CGACT? | [+CGACT: <cid>, <state>]<br>[<CR><LF>+CGACT: <cid>, <state>]<br>[...] | +| +CGACT=? | +CGATT: (list of supported <state>s) | + +### Description + +The execution command is used to activate or deactivate the specified PDP context (s). After the command has completed, the MT remains in V.250 command state. If any PDP context is already in the requested state, the state for that context remains unchanged. If the requested state for any specified context cannot be achieved, an ERROR or + ++CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. If the MT is not PS attached when the activation form of the command is executed, the MT first performs a PS attach and then attempts to activate the specified contexts. If the attach fails then the MT responds with ERROR or, if extended error responses are enabled, with the appropriate failure-to-attach error message. Refer clause 9.2 for possible <err> values. + +For EPS, if an attempt is made to disconnect the last PDN connection, then the MT responds with ERROR or, if extended error responses are enabled, a +CME ERROR. + +NOTE: If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0. + +For EPS, the activation request for an EPS bearer resource will be answered by the network by either an EPS dedicated bearer activation or EPS bearer modification request. The request must be accepted by the MT before the PDP context can be set in to established state. + +For 5GS, the command is used to request or delete the specified QoS flow. The request for a specific QoS flow will be answered by the network by a PDU session establishment accept message or a PDU session modification command message. The PDU session establishment accept message or a PDU session modification command message must be accepted by the MT before the QoS flow can be set to active state. + +If no <cid>s are specified the activation form of the command activates all defined non-emergency contexts. + +If no <cid>s are specified the deactivation form of the command deactivates all active contexts. + +The read command returns the current activation states for all the defined PDP contexts. + +The test command is used for requesting information on the supported PDP context activation states. + +NOTE: This command has the characteristics of both the V.250 action and parameter commands. Hence it has the read form in addition to the execution/set and test forms. + +#### Defined values + +<state>: integer type; indicates the state of PDP context activation. The default value is manufacturer specific. + +0 deactivated + +1 activated + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +#### Implementation + +Optional. + +### 10.1.11 PDP context modify +CGCMOD + +Table 121: +CGCMOD action command syntax + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| +| +CGCMOD[=<cid>[,<cid>[,...]]] | +CME ERROR: <err> | +| +CGCMOD=? | +CGCMOD: (list of <cid>s associated with active contexts) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGCMOD=[<cid>[,<cid>[,...]]]. | | + +#### Description + +The execution command is used to modify the specified PDP context (s) with respect to QoS profiles, TFTs and MBS sessions. After the command has completed, the MT returns to V.250 online data state. If the requested modification for any specified context cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer clause 9.2 for possible <err> values. + +For EPS, the modification request for an EPS bearer resource will be answered by the network by an EPS bearer modification request. The request must be accepted by the MT before the PDP context is effectively changed. + +For 5GS, the command is used to modify the specified QoS flow. The modification request for a QoS flow resource will be answered by the network by a PDU session modification command. The command must be accepted by the MT before the QoS flow is effectively changed. + +If no <cid>s are specified the activation form of the command modifies all active contexts. + +The test command returns a list of <cid>s associated with active contexts. + +#### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +#### Implementation + +Optional. + +### 10.1.12 Enter data state +CGDATA + +**Table 122: +CGDATA action command syntax** + +| Command | Possible Response(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| +CGDATA[=<L2P>[, <cid>[, <cid>[, ...]]]] | CONNECT<br>ERROR<br>+CME ERROR: <err> | +| +CGDATA=? | +CGDATA: (list of supported <L2P>s) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGDATA=[<L2P>[, <cid>[, <cid>[, ...]]]]. | | + +#### Description + +The execution command causes the MT to perform whatever actions are necessary to establish communication between the TE and the network using one or more Packet Domain PDP types. This may include performing a PS attach and one or more PDP context activations. If the <L2P> parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Refer clause 9.2 for possible <err> values. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. + +NOTE: If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0. + +Commands following +CGDATA command in the AT command line shall not be processed by the MT. + +The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in 3GPP TS 27.060 [34] and in more detail in 3GPP TS 29.061 [39] and the specifications for the relevant PDPs. PS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed using the +CGATT and +CGACT commands. + +If context activation takes place during the PDP startup, one or more <cid>s may be specified in order to provide the information needed for the context activation request(s). + +During each PDP startup procedure the MT may have access to some or all of the following information - + +The MT may have a priori knowledge, for example, it may implement only one PDP type. + +The command may have provided an <L2P> parameter value. + +The TE may provide a PDP type and/or PDP address to the MT during in the PDP startup procedure. + +If any of this information is in conflict, the command will fail. + +Any PDP type and/or PDP address present in the above information shall be compared with the PDP type and/or PDP address in any context definitions specified in the command in the order in which their <cid>s appear. For a context definition to match: + +The PDP type must match exactly. + +The PDP addresses are considered to match if they are identical or if either or both addresses are unspecified. For example, a PPP NCP request specifying PDP type = IP and no PDP address would cause the MT to search through the specified context definitions for one with PDP type = IP and any PDP address. + +The context shall be activated using the matched value for PDP type and a static PDP address if available, together with the other information found in the PDP context definition. If a static PDP address is not available then a dynamic address is requested. + +If no <cid> is given or if there is no matching context definition, the MT shall attempt to activate the context with whatever information is available to the MT. The other context parameters shall be set to their default values. + +If the activation is successful, data transfer may proceed. + +After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is re-entered and the MT returns the final result code OK. + +In the event of an erroneous termination or a failure to start up, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER or, if enabled, +CME ERROR. Refer clause 9.2 for possible <err> values. Attach, activate and other errors may be reported. + +The test command is used for requesting information on the supported layer 2 protocols. + +This command may be used in both normal and modem compatibility modes. + +#### Defined values + +<L2P>: string type; indicates the layer 2 protocol to be used between the TE and MT + +| | | +|--------|--------------------------------------------------------------------| +| NULL | none, for PDP type OSP:IHOSS (Obsolete) | +| PPP | Point-to-point protocol for a PDP such as IP | +| PAD | character stream for X.25 character (triple X PAD) mode (Obsolete) | +| X25 | X.25 L2 (LAPB) for X.25 packet mode (Obsolete) | +| M-xxxx | manufacturer-specific protocol (xxxx is an alphanumeric string) | + +If the value is omitted, the layer 2 protocol is unspecified. Other values are reserved and will result in an ERROR response. + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +#### Implementation + +Optional if the D (dial) command can be used to specify Packet Domain operation. + +### 10.1.13 Configure local octet stream PAD parameters +CGCLOSP (Obsolete) + +### 10.1.14 Show PDP address(es) +CGPADDR + +**Table 123: +CGPADDR action command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| +CGPADDR[=<cid>[, <cid>[, ...]]] | [+CGPADDR: <cid>[, <PDP_addr_1>[, <PDP_addr_2>]]]<br><br>[<CR><LF>+CGPADDR: <cid>,<br><PDP_addr_1>[, <PDP_addr_2>]]]<br><br>[...]] | +| +CGPADDR=? | +CGPADDR: (list of defined <cid>s) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGPADDR=[, <cid>[, <cid>[, ...]]]. | | + +#### Description + +The execution command returns a list of PDP addresses for the specified context identifiers. If no <cid> is specified, the addresses for all defined contexts are returned. + +The test command returns a list of defined <cid>s. + +#### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<PDP\_addr\_1> and <PDP\_addr\_2>: each is a string type that identifies the MT in the address space applicable to the PDP. The address may be static or dynamic. For a static address, it will be the one set by the +CGDCONT and +CGDSCONT commands when the context was defined. For a dynamic address it will be the one assigned during the last PDP context activation that used the context definition referred to by <cid>. Both <PDP\_addr\_1> and <PDP\_addr\_2> are omitted if none is available. Both <PDP\_addr\_1> and <PDP\_addr\_2> are included when both IPv4 and IPv6 addresses are assigned, with <PDP\_addr\_1> containing the IPv4 address and <PDP\_addr\_2> containing the IPv6 address. + +The string is given as dot-separated numeric (0-255) parameter of the form: + +a1.a2.a3.a4 for IPv4 and + +a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16 for IPv6. + +When +CGPIAF is supported, its settings can influence the format of the IPv6 address in parameter <PDP\_addr\_1> or <PDP\_addr\_2> returned with the execute form of +CGPADDR. + +NOTE: In dual-stack terminals (<PDP\_type> IPV4V6), the IPv6 address will be provided in <PDP\_addr\_2>. For terminals with a single IPv6 stack (<PDP\_type> IPV6) or due to backwards compatibility, the IPv6 address can be provided in parameter <PDP\_addr\_1>. + +#### Implementation + +Optional. + +## 10.1.15 Automatic response to a network request for PDP context activation +CGAUTO + +**Table 124: +CGAUTO parameter command syntax** + +| Command | Possible response(s) | +|---------------|-----------------------------------| +| +CGAUTO=[<n>] | +CME ERROR: <err> | +| +CGAUTO? | +CGAUTO: <n> | +| +CGAUTO=? | +CGAUTO: (list of supported <n>s) | + +### Description + +The set command disables or enables an automatic positive or negative response (auto-answer) to the receipt of a NW-initiated Request PDP Context Activation message, NW-initiated Request EPS Bearer Activation/ Modification Request messages and a NW-initiated PDU Session Modification Command message. It also provides control over the use of the V.250 basic commands 'S0', 'A' and 'H' for handling network requests for PDP context activation. The setting does not affect the issuing of the unsolicited result code RING or +CRING. + +When the +CGAUTO=0 command is received for GERAN, UTRAN or E-UTRAN RATs, the MT shall not perform a PS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING, the TE may manually accept or reject the request by issuing the +CGANS command or may simply ignore the network request. + +When the +CGAUTO=1 command is received for GERAN, UTRAN or E-UTRAN RATs, the MT shall attempt to perform a PS attach if it is not already attached. Failure will result in ERROR or, if enabled, +CME ERROR being returned to the TE. Refer clause 9.2 for possible <err> values. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING to the TE, this is followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified. + +The read command returns the current value of <n>. + +The test command returns the values of <n> supported by the MT as a compound value. + +### Defined values + +<n>: integer type + +- 0 turn off automatic response for Packet Domain only +- 1 turn on automatic response for Packet Domain only +- 2 modem compatibility mode, Packet Domain only +- 3 modem compatibility mode, Packet Domain and circuit switched calls +- 4 turn on automatic negative response for Packet Domain only + +For <n>=0 Packet Domain network requests are manually accepted or rejected by the +CGANS command. + +For <n>=1 Packet Domain network requests are automatically accepted according to the description above. + +For <n>=2, automatic acceptance of Packet Domain network requests is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Incoming circuit switched calls can be neither manually nor automatically answered. + +For <n>=3, automatic acceptance of both Packet Domain network requests and incoming circuit switched calls is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Circuit switched calls are handled as described elsewhere in this specification. + +For $\langle n \rangle = 4$ , Packet Domain network requests are automatically rejected. + +#### Implementation + +Optional. If not implemented, the MT shall behave according to the case of $\langle n \rangle = 3$ . + +### 10.1.16 Manual response to a network request for PDP context activation +CGANS + +**Table 125: +CGANS action command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| +CGANS=[<response>, [<L2P>, [<cid>]]] | +CME ERROR: <err> | +| +CGANS=? | +CGANS: (list of supported <response>s),<br>(list of supported <L2P>s) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGANS=[<response>, [<L2P>, [<cid>]]] | | + +#### Description + +The execution command requests the MT to respond to a network request for Packet Domain PDP context activation which has been signalled to the TE by the RING, +CRING or +CGEV unsolicited result code. The <response> parameter allows the TE to accept or reject the request. + +If <response> is 0, the request is rejected and the MT returns OK to the TE. + +If <response> is 1, the following procedure is followed by the MT. + +Commands following the +CGANS command in the AT command line shall not be processed by the MT. + +If the <L2P> parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Refer clause 9.2 for possible <err> values. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. + +The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in 3GPP TS 27.060 [34] and in more detail in 3GPP TS 29.061 [39] and the specifications for the relevant PDPs. PDP context activation procedures shall take place prior to or during the PDP startup. + +One or more <cid>s may be specified in order to provide the values needed for the context activation request. + +During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP Context Activation message. The MT may also have some or all of the following information: + +The MT may have a priori knowledge, for example, it may implement only one PDP type. + +The command may have provided an <L2P> parameter value. + +The TE may provide one or both of PDP type and PDP address to the MT in the PDP startup. + +If any of this information is in conflict, the command will fail. + +If one or more <cid> is given then an attempt shall be made to identify an appropriate context definition by matching the PDP type and PDP address in the network request with the PDP type and PDP address in each of the specified context definitions (in the order in which their <cid>s appear in the command) as follows: + +The PDP type must match exactly. + +The PDP addresses are considered to match if they are identical or if the address in the context definition is unspecified. + +The context shall be activated using the values for PDP type and PDP address provided by the network, together with the other information found in the PDP context definition. An APN may or may not be required, depending on the application. + +If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and PDP address provided by the network, together with any other relevant information known to the MT. The other context parameters will be set to their default values. + +If the activation is successful, data transfer may proceed. + +After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is re-entered and the MT returns the final result code OK + +In the event of an erroneous termination or a failure to startup, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER or, if enabled, +CME ERROR. Refer clause 9.2 for possible <err> values. Attach, activate and other errors may be reported. It is also an error to issue the +CGANS command when there is no outstanding network request. + +NOTE: This is not the same as if the MT issues a +CGDATA (or +CGACT) command after receiving a +CRING unsolicited result code. A +CGDATA (or +CGACT) does not command the MT to acknowledge the network request but rather to make a new request for context activation. The network request would be ignored. + +The test command returns the values of <response> and <L2P> supported by the MT as compound values. + +This command may be used in both normal and modem compatibility modes. + +#### Defined values + +<response>: integer type; specifies how the request should be responded to. + +- 0 reject the request +- 1 accept and request that the PDP context be activated + +If <response> is omitted it is assumed to be 0. + +<L2P>: string type; indicates the layer 2 protocol to be used (see +CGDATA command). + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +#### Implementation + +Optional. + +### 10.1.17 GPRS mobile station class +CGCLASS + +**Table 126: +CGCLASS parameter command syntax** + +| Command | Possible Response(s) | +|--------------------|----------------------------------------| +| +CGCLASS=[<class>] | +CME ERROR: <err> | +| +CGCLASS? | +CGCLASS: <class> | +| +CGCLASS=? | +CGCLASS: (list of supported <class>s) | + +## Description + +The set command is used to set the MT to operate according to the specified mode of operation, see 3GPP TS 23.060 [47]. If the requested mode of operation is not supported, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer clause 9.2 for possible <err> values. + +The read command returns the mode of operation set by the TE, independent of the current serving cell capability and independent of the current serving cell Access Technology. If no value has been set by the TE previously, the return value shall be the highest mode of operation that can be supported by the MT. + +The test command is used for requesting information on the supported MT modes of operation as a compound value. + +## Defined values + +<class>: string type; indicates the mode of operation. The default value is manufacturer specific. + +- A Class-A mode of operation (A/Gb mode), or CS/PS mode of operation (Iu mode) (highest mode of operation) +- B Class-B mode of operation (A/Gb mode), or CS/PS mode of operation (Iu mode) +- CG Class-C mode of operation in PS only mode (A/Gb mode), or PS mode of operation (Iu mode) +- CC Class-C mode of operation in CS only mode (A/Gb mode), or CS (Iu mode) (lowest mode of operation) + +NOTE: <class> A means that the MT would operate simultaneous PS and CS service + <class> B means that the MT would operate PS and CS services but not simultaneously in A/Gb mode + <class> CG means that the MT would only operate PS services + <class> CC means that the MT would only operate CS services + +If the MT is attached to the PS domain when the set command is issued with a <class>=CC specified, a PS detach shall be performed by the MT. + +## Implementation + +Optional. + +### 10.1.18 Configure local triple-X PAD parameters +CGCLPAD (GPRS only) (Obsolete) + +### 10.1.19 Packet domain event reporting +CGEREPP + +**Table 127: +CGEREPP parameter command syntax** + +| Command | Possible response(s) | +|----------------------------|--------------------------------------------------------------------| +| +CGEREPP=[<mode>[, <bfr>]] | +CME ERROR: <err> | +| +CGEREPP? | +CGEREPP: <mode>, <bfr> | +| +CGEREPP=? | +CGEREPP: (list of supported <mode>s) , (list of supported <bfr>s) | + +## Description + +Set command enables or disables sending of unsolicited result codes, +CGEV: XXX from MT to TE in the case of certain events occurring in the Packet Domain MT or the network. <mode> controls the processing of unsolicited result codes specified within this command. <bfr> controls the effect on buffered codes when <mode> 1 or 2 is entered. If a setting is not supported by the MT, ERROR or +CME ERROR: is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current mode and buffer settings. + +Test command returns the modes and buffer settings supported by the MT as compound values. + +## Defined values + +<mode>: integer type + +- 0 buffer unsolicited result codes in the MT; if MT result code buffer is full, the oldest ones can be discarded. No codes are forwarded to the TE. +- 1 discard unsolicited result codes when MT-TE link is reserved (e.g. in on-line data mode); otherwise forward them directly to the TE +- 2 buffer unsolicited result codes in the MT when MT-TE link is reserved (e.g. in on-line data mode) and flush them to the TE when MT-TE link becomes available; otherwise forward them directly to the TE + +<bfr>: integer type + +- 0 MT buffer of unsolicited result codes defined within this command is cleared when <mode> 1 or 2 is entered +- 1 MT buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1 or 2 is entered (OK response shall be given before flushing the codes) + +## Defined events + +The events are valid for all accesses unless explicitly mentioned. + +For network attachment, the following unsolicited result codes and the corresponding events are defined: + ++CGEV: NW DETACH + +The network has forced a PS detach. This implies that all active contexts have been deactivated. These are not reported separately. + ++CGEV: ME DETACH + +The mobile termination has forced a PS detach. This implies that all active contexts have been deactivated. These are not reported separately. + +For MT class, the following unsolicited result codes and the corresponding events are defined: + ++CGEV: NW CLASS <class> + +The network has forced a change of MT class. The highest available class is reported (see +CGCLASS). The format of the parameter <class> is found in command +CGCLASS. + ++CGEV: ME CLASS <class> + +The mobile termination has forced a change of MT class. The highest available class is reported (see +CGCLASS). The format of the parameter <class> is found in command +CGCLASS. + +For PDP context activation, the following unsolicited result codes and the corresponding events are defined: + ++CGEV: NW PDN ACT <cid>[, <WLAN\_Offload>] + +The network has activated a context. The context represents a Primary PDP context. The <cid> for this context is provided to the TE. The format of the parameter <cid> is found in command +CGDCONT. + +<WLAN\_Offload>: integer type. An integer that indicates whether traffic can be offloaded using the specified PDN connection via a WLAN or not. This refers to bit 1 (E-UTRAN offload acceptability value) and bit 2 (UTRAN offload acceptability value) in the WLAN offload acceptability IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.20. + +- 0 offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is not acceptable. +- 1 offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable, but not acceptable in Iu mode. + +- 2 offloading the traffic of the PDN connection via a WLAN when in Iu mode is acceptable, but not acceptable in S1 mode. +- 3 offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is acceptable. + +NOTE 1: This event is not applicable for EPS and 5GS. + ++CGEV: ME PDN ACT <cid>[, <reason>[, <cid\_other>[, <WLAN\_Offload>[, <SSC>, <old-cid>, [<MA\_3GPP>, <MA\_N3GPP>]]]]] + +The mobile termination has activated a context. The context represents a PDN connection or a Primary PDP context. The <cid> for this context is provided to the TE. This event is sent either in result of explicit context activation request (+CGACT), or in result of implicit context activation request associated to attach request (+CGATT=1). The format of the parameter <cid> is found in command +CGDCONT. The format of the parameter <WLAN\_Offload> is defined above. + +<reason>: integer type; indicates the reason why the context activation request for PDP type IPv4v6 was not granted. This parameter is only included if the requested PDP type associated with <cid> is IPv4v6, and the PDP type assigned by the network for <cid> is either IPv4 or IPv6. + +- 0 IPv4 only allowed +- 1 IPv6 only allowed +- 2 single address bearers only allowed. +- 3 single address bearers only allowed and MT initiated context activation for a second address type bearer was not successful. + +<cid\_other>: integer type; indicates the context identifier allocated by MT for an MT initiated context of a second address type. MT shall only include this parameter if <reason> parameter indicates single address bearers only allowed, and MT supports MT initiated context activation of a second address type without additional commands from TE, and MT has activated the PDN connection or PDP context associated with <cid\_other>. + +<SSC>: integer type; indicates whether the established PDU session is requested by the network for SSC mode 2 or SSC mode 3 PDU session anchor relocation as specified in 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +- 1 the established PDU session is requested by the network for SSC mode 2 PDU session anchor relocation. +- 2 the established PDU session is requested by the network for SSC mode 3 PDU session anchor relocation. + +<old-cid>: integer type; indicates the context identifier of the QoS flow of the default QoS rule of the SSC mode 2 or SSC mode 3 PDU session where the network requests relocation of the PDU session anchor. + +<MA\_3GPP>: integer type; + +- 0 the established PDU session is an MA PDU session and the user plane resources are not established over 3GPP access. +- 1 the established PDU session is an MA PDU session and the user plane resources are established over 3GPP access. + +<MA\_N3GPP>: integer type; + +- 0 the established PDU session is an MA PDU session and the user plane resources are not established over non-3GPP access. +- 1 the established PDU session is an MA PDU session and the user plane resources are established over non-3GPP access. + +NOTE 1A: For legacy TEs supporting MT initiated context activation without TE requests, there is also a subsequent event +CGEV: ME PDN ACT <cid\_other> returned to TE. + ++CGEV: NW ACT <p\_cid>, <cid>, <event\_type>[, <WLAN\_Offload>] + +The network has activated a context. The <cid> for this context is provided to the TE in addition to the associated primary <p\_cid>. The format of the parameters <p\_cid> and <cid> are found in command +CGDSCONT. The format of the parameter <WLAN\_Offload> is defined above. + +<event\_type>: integer type; indicates whether this is an informational event or whether the TE has to acknowledge it. + +0 Informational event + +1 Information request: Acknowledgement required. The acknowledgement can be accept or reject, see +CGANS. + ++CGEV: ME ACT <p\_cid>, <cid>, <event\_type>[, <WLAN\_Offload>] + +The network has responded to an ME initiated context activation. The <cid> for this context is provided to the TE in addition to the associated primary <p\_cid>. The format of the parameters <p\_cid> and <cid> are found in command +CGDSCONT. The format of the parameters <event\_type> and <WLAN\_Offload> are defined above. + +For PDP context deactivation, the following unsolicited result codes and the corresponding events are defined: + ++CGEV: NW DEACT <PDP\_type>, <PDP\_addr>, [<cid>] + +The network has forced a context deactivation. The <cid> that was used to activate the context is provided if known to the MT. The format of the parameters <PDP\_type>, <PDP\_addr> and <cid> are found in command +CGDCONT. + ++CGEV: ME DEACT <PDP\_type>, <PDP\_addr>, [<cid>] + +The mobile termination has forced a context deactivation. The <cid> that was used to activate the context is provided if known to the MT. The format of the parameters <PDP\_type>, <PDP\_addr> and <cid> are found in command +CGDCONT. + ++CGEV: NW PDN DEACT <cid>[, <WLAN\_Offload>[, <SSC>]] + +The network has deactivated a context. The context represents a PDN connection or a Primary PDP context. The associated <cid> for this context is provided to the TE. The format of the parameter <cid> is found in command +CGDCONT. The format of the parameters <WLAN\_Offload> and <SSC> are defined above. + +NOTE 2: Occurrence of this event replaces usage of the event + ++CGEV: NW DEACT <PDP\_type>, <PDP\_addr>, [<cid>]. + ++CGEV: ME PDN DEACT <cid> + +The mobile termination has deactivated a context. The context represents a PDN connection or a Primary PDP context. The <cid> for this context is provided to the TE. The format of the parameter <cid> is found in command +CGDCONT. + +NOTE 3: Occurrence of this event replaces usage of the event + ++CGEV: ME DEACT <PDP\_type>, <PDP\_addr>, [<cid>]. + ++CGEV: NW DEACT <p\_cid>, <cid>, <event\_type>[, <WLAN\_Offload>] + +The network has deactivated a context. The <cid> for this context is provided to the TE in addition to the associated primary <p\_cid>. The format of the parameters <p\_cid> and <cid> are found in command +CGDSCONT. The format of the parameters <event\_type> and <WLAN\_Offload> are defined above. + +NOTE 4: Occurrence of this event replaces usage of the event + ++CGEV: NW DEACT <PDP\_type>, <PDP\_addr>, [<cid>]. + ++CGEV: ME DEACT <p\_cid>, <cid>, <event\_type> + +The network has responded to an ME initiated context deactivation request. The associated <cid> is provided to the TE in addition to the associated primary <p\_cid>. The format of the parameters <p\_cid> and <cid> are found in command +CGDSCONT. The format of the parameter <event\_type> is defined above. + +NOTE 5: Occurrence of this event replaces usage of the event + ++CGEV: ME DEACT <PDP\_type>, <PDP\_addr>, [<cid>]. + +For PDP context modification, the following unsolicited result codes and the corresponding events are defined: + ++CGEV: NW MODIFY <cid>, <change\_reason>, <event\_type>[, <WLAN\_Offload>[, <PDU\_lifetime>]] + +The network has modified a context. The associated <cid> is provided to the TE in addition to the <change\_reason> and <event\_type>. The format of the parameter <cid> is found in command +CGDCONT or +CGDSCONT. The format of the parameters <change\_reason>, <event\_type>, and <WLAN\_Offload> are defined above. + +<change\_reason>: integer type; a bitmap that indicates what kind of change occurred. The <change\_reason> value is determined by summing all the applicable bits. For example if both the values of QoS changed (Bit 2) and WLAN\_Offload changed (Bit 3) have changed, then the <change\_reason> value is 6. + +NOTE 5A: The WLAN offload value will change when bit 1 or bit 2 or both of the indicators in the WLAN offload acceptability IE change, see the parameter <WLAN\_Offload> defined above. + +Bit 1 TFT changed + +Bit 2 Qos changed + +Bit 3 WLAN Offload changed + +Bit 4 Relocation of PDU session anchor requested + +Bit 5 PDP address or PDP type changed + +Bit 6 ATSSS parameters changed + +Bit 7 P-CSCF restoration requested + +<PDU\_lifetime>: integer type; indicates the PDU session address lifetime value in seconds for relocation of SSC mode 3 PDU session anchor, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + ++CGEV: ME MODIFY <cid>, <change\_reason>, <event\_type>[, <WLAN\_Offload>] + +The mobile termination has modified a context. The associated <cid> is provided to the TE in addition to the <change\_reason> and <event\_type>. The format of the parameter <cid> is found in command +CGDCONT or +CGDSCONT. The format of the parameters <change\_reason>, <event\_type> and <WLAN\_Offload> are defined above. + +For other PDP context handling, the following unsolicited result codes and the corresponding events are defined: + ++CGEV: REJECT <PDP\_type>, <PDP\_addr> + +A network request for context activation occurred when the MT was unable to report it to the TE with a +CRING unsolicited result code and was automatically rejected. The format of the parameters <PDP\_type> and <PDP\_addr> are found in command +CGDCONT. + +NOTE 6: This event is not applicable for EPS and 5GS. + ++CGEV: NW REACT <PDP\_type>, <PDP\_addr>, [<cid>] + +The network has requested a context reactivation. The <cid> that was used to reactivate the context is provided if known to the MT. The format of the parameters <PDP\_type>, <PDP\_addr> and <cid> are found in command +CGDCONT. + +NOTE 7: This event is not applicable for EPS and 5GS. + +### Implementation + +Optional. + +## 10.1.20 GPRS network registration status +CGREG + +**Table 128: +CGREG parameter command syntax** + +| Command | Possible response(s) | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGREG=<n> | +CME ERROR: <err> | +| +CGREG? | <b>when <n>=0, 1, 2 or 3 and command successful:</b><br>+CGREG: <n>, <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>] [, <cause_type>, <reject_cause>]]]<br><b>when <n>=4 or 5 and command successful:</b><br>+CGREG: <n>, <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>] [, <cause_type>, <reject_cause>] [, <Active-Time>], [<Periodic-RAU>], [<GPRS-READY-timer>]]]] | +| +CGREG=? | +CGREG: (list of supported <n>s) | + +### Description + +The set command controls the presentation of an unsolicited result code +CGREG: <stat> when <n>=1 and there is a change in the MT's GPRS network registration status in GERAN/UTRAN, or unsolicited result code +CGREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>]] when <n>=2 and there is a change of the network cell in GERAN/UTRAN. The parameters <AcT>, <lac>, <rac> and <ci> are provided only if available. The value <n>=3 further extends the unsolicited result code with [, <cause\_type>, <reject\_cause>], when available, when the value of <stat> changes. The value <n>=6 extends the unsolicited result code with [, <csg\_stat>] when the value of <csg\_stat> changes. The value <n>=7 extends the unsolicited result code with [, <csginfo>] when UE camps on a CSG cell. <csginfo> is displayed only when <csg\_stat> is 1. + +If the UE wants to apply PSM for reducing its power consumption, see +CPSMS command and 3GPP TS 23.682 [149], the set command controls the presentation of an unsolicited result code +CGREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>] [, <cause\_type>, <reject\_cause>] [, <Active-Time>], [<Periodic-RAU>], [<GPRS-READY-timer>]]]]. When <n>=4 the unsolicited result code will provide the UE with additional information for the Active Time value, the extended periodic RAU value and the GPRS READY timer value if there is a change of the network cell in GERAN/UTRAN. The value <n>=5 further enhances the unsolicited result code with <cause\_type> and <reject\_cause> when the value of <stat> changes. The parameters <AcT>, <lac>, <rac>, <ci>, <cause\_type>, <reject\_cause>, <Active-Time>, <Periodic-RAU> and <GPRS-READY-timer> are provided only if available. + +Refer clause 9.2 for possible <err> values. + +NOTE 1: If the GPRS MT also supports one or more of the circuit mode services in GERAN/UTRAN, EPS services in E-UTRAN or 5G services in NG-RAN, the +CREG command and +CREG: result codes, the +CEREG command and +CEREG: result codes and the +C5GREG command and +C5GREG: result codes apply to the registration status and location information for those services. + +The read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. Location information elements <lac>, <ci>, <AcT> and + +<rac>, if available, are returned only when <n>=2 and MT is registered in the network. The parameters [, <cause\_type>, <reject\_cause>], if available, are returned when <n>=3. + +Test command returns values supported as a compound value. The parameter [, <csg\_stat>], if available, is returned when <n>=6. The parameter [, <csginfo>], if available, is returned when <n>=7. + +### Defined values + +<n>: integer type + +- 0 disable network registration unsolicited result code +- 1 enable network registration unsolicited result code +CGREG: <stat> +- 2 enable network registration and location information unsolicited result code +CGREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>]] +- 3 enable network registration, location information and GMM cause value information unsolicited result code +CGREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>] [, <cause\_type>, <reject\_cause>]] +- 4 For a UE that wants to apply PSM, enable network registration and location information unsolicited result code +CGREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>] [, [, [<Active-Time>], [<Periodic-RAU>], [<GPRS-READY-timer>]]]] +- 5 For a UE that wants to apply PSM, enable network registration, location information and GMM cause value information unsolicited result code +CGREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<rac>] [, [<cause\_type>], [<reject\_cause>] [, [<Active-Time>], [<Periodic-RAU>], [<GPRS-READY-timer>]]]] +- 6 enable network registration, location information, cause value information, CSG cell status information unsolicited result code +CREG: <stat>[, [<lac>], [<ci>], [<AcT>] [, <cause\_type>, <reject\_cause>]] [, <csg\_stat>] +- 7 enable network registration, location information, cause value information, CSG cell status information and CSG cell information unsolicited result code +CREG: <stat>[, [<lac>], [<ci>], [<AcT>] [, <cause\_type>, <reject\_cause>]] [, <csg\_stat>] [, <csginfo>] + +<stat>: integer type; indicates the GPRS registration status. + +- 0 not registered, MT is not currently searching an operator to register to +- 1 registered, home network +- 2 not registered, but MT is currently trying to attach or searching an operator to register to +- 3 registration denied +- 4 unknown (e.g. out of GERAN/UTRAN coverage) +- 5 registered, roaming +- 6 registered for "SMS only", home network (not applicable) +- 7 registered for "SMS only", roaming (not applicable) +- 8 attached for emergency bearer services only (see NOTE 2) (applicable only when <AcT> indicates 2,4,5,6) +- 9 registered for "CSFB not preferred", home network (not applicable) +- 10 registered for "CSFB not preferred", roaming (not applicable) +- 11 attached for access to RLOS (See NOTE 2a) (not applicable) + +NOTE 2: 3GPP TS 24.008 [8] and 3GPP TS 24.301 [83] specify the condition when the MT is considered as attached for emergency bearer services. + +NOTE 2a: 3GPP TS 24.301 [83] specifies the condition when the MT is considered as attached for access to RLOS. + +<lac>: string type; two byte location area code in hexadecimal format (e.g. "00C3" equals 195 in decimal). + +<ci>: string type; four byte GERAN/UTRAN cell ID in hexadecimal format. + +<AcT>: integer type; indicates the access technology of the serving cell. + +- 0 GSM +- 1 GSM Compact +- 2 UTRAN +- 3 GSM w/EGPRS (see NOTE 3) +- 4 UTRAN w/HSDPA (see NOTE 4) +- 5 UTRAN w/HSUPA (see NOTE 4) +- 6 UTRAN w/HSDPA and HSUPA (see NOTE 4) +- 7 E-UTRAN (not applicable) +- 8 EC-GSM-IoT (A/Gb mode) (see NOTE 5) +- 9 E-UTRAN (NB-S1 mode) (see NOTE 6) (not applicable) +- 10 E-UTRA connected to a 5GCN (see NOTE 7) (not applicable) +- 11 NR connected to a 5GCN (see NOTE 7) (not applicable) +- 12 NG-RAN (not applicable) +- 13 E-UTRA-NR dual connectivity (see NOTE 8) (not applicable) + +NOTE 3: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS. + +NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA. + +NOTE 5: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT. + +NOTE 6: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode). + +NOTE 7: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5GCN. + +NOTE 8: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core. + +<rac>: string type; one byte routing area code in hexadecimal format. + +<cause\_type>: integer type; indicates the type of <reject\_cause>. + +- 0 Indicates that <reject\_cause> contains a GMM cause value, see 3GPP TS 24.008 [8] Annex G. +- 1 Indicates that <reject\_cause> contains a manufacturer-specific cause. + +<reject\_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by <cause\_type>. + +<Active-Time>: string type; one byte in an 8 bit format. Indicates the Active Time value (T3324) allocated to the UE in GERAN/UTRAN. The Active Time value is coded as one byte (octet 3) of the GPRS Timer 2 + +information element coded as bit format (e.g. "00100100" equals 4 minutes). For the coding and the value range, see the GPRS Timer 2 IE in 3GPP TS 24.008 [8] Table 10.5.163/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.060 [47]. + +<Periodic-RAU>: string type; one byte in an 8 bit format. Indicates the extended periodic RAU value (T3312) allocated to the UE in GERAN/UTRAN. The extended periodic RAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.060 [47]. + +<GPRS-READY-timer>: string type; one byte in an 8 bit format. Indicates the GPRS READY timer value (T3314) allocated to the UE in GERAN/UTRAN. The GPRS READY timer value is coded as one byte (octet 2) of the GPRS Timer information element coded as bit format (e.g. "01000011" equals 3 decihours or 18 minutes). For the coding and the value range, see the GPRS Timer IE in 3GPP TS 24.008 [8] Table 10.5.172/3GPP TS 24.008. See also 3GPP TS 23.060 [47]. + +<csg\_stat>: integer type; indicates the camping status on a CSG cell + +0 Indicates UE is not camped on CSG cell. + +1 Indicates UE is currently camped on CSG cell. + +<CSGinfo>: string type; + +CSGinfo consists of CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC each delimited by a comma and in this particular order only. If any of the CSGType, HNB Name, or CSGID is unavailable, it shall be an empty field. See 3GPP TS 22.011 [170], 3GPP TS 23.003 [7] for details of CSG Type, HNB name and CSG ID representation. + +The display format is based on <format> value in +CSSGS command. In the alphanumeric format CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC would be displayed while in numeric format only CSGID and CSG Associated PLMN MCC MNC would be displayed. + +## Implementation + +Optional. + +This command is not applicable to UEs in E-UTRAN or NG-RAN. + +## 10.1.21 Select service for MO SMS messages +CGSMS + +**Table 129: +CGSMS parameter command syntax** + +| Command | Possible Response(s) | +|--------------------|--------------------------------------------------| +| +CGSMS=[<service>] | | +| +CGSMS? | +CGSMS: <service> | +| +CGSMS=? | +CGSMS: (list of currently available <service>s) | + +## Description + +The set command is used to specify the service or service preference that the MT will use to send MO SMS messages. + +The read command returns the currently selected service or service preference. + +The test command is used for requesting information on the currently available services and service preferences as a compound value. + +## Defined values + +<service>: integer type; indicates the service or service preference to be used. The default value is manufacturer specific. + +- 0 Packet Domain +- 1 circuit switched +- 2 Packet Domain preferred (use circuit switched if GPRS not available) +- 3 circuit switched preferred (use Packet Domain if circuit switched not available) + +### Implementation + +Optional. + +This command is not applicable to UEs in E-UTRAN or NG-RAN. + +## 10.1.22 EPS network registration status +CEREG + +**Table 10.1.22-1: +CEREG parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CEREG=[<n>] | +CME ERROR: <err> | +| +CEREG? | <b>when <n>=0, 1, 2 or 3 and command successful:</b><br>+ <b>CEREG:</b> <n>,<stat>[, [<tac>], [<ci>], [<AcT>] [, <cause_type>, <reject_cause>] ] ] ]<br><b>when <n>=4 or 5 and command successful:</b><br>+ <b>CEREG:</b> <n>,<stat>[, [<tac>], [<ci>], [<AcT>] [, <cause_type>, <reject_cause>] [, <Active-Time>, <Periodic-TAU>] ] ] ] | +| +CEREG=? | + <b>CEREG:</b> (list of supported <n>s) | + +### Description + +The set command controls the presentation of an unsolicited result code +CEREG: <stat> when <n>=1 and there is a change in the MT's EPS network registration status in E-UTRAN, or unsolicited result code +CEREG: <stat>[, [<tac>], [<ci>], [<AcT>] ] when <n>=2 and there is a change of the network cell in E-UTRAN. The parameters <AcT>, <tac> and <ci> are provided only if available. The value <n>=3 further extends the unsolicited result code with [, <cause\_type>, <reject\_cause>], when available, when the value of <stat> changes. The value <n>=4 extends the unsolicited result code with [, <csg\_stat>] when the value of <csg\_stat> changes. The value <n>=5 extends the unsolicited result code with [, <csginfo>] when UE camps on a CSG cell. <csginfo> is displayed only when <csg\_stat> is 1. + +If the UE wants to apply PSM for reducing its power consumption, see +CPSMS command and 3GPP TS 23.682 [149], the set command controls the presentation of an unsolicited result code +CEREG: <stat>[, [<tac>], [<ci>], [<AcT>] [, <cause\_type>, <reject\_cause>] [, <Active-Time>, <Periodic-TAU>] ] ] ]]. When <n>=4 the unsolicited result code will provide the UE with additional information for the Active Time value and the extended periodic TAU value if there is a change of the network cell in E-UTRAN. The value <n>=5 further enhances the unsolicited result code with <cause\_type> and <reject\_cause> when the value of <stat> changes. The parameters <AcT>, <tac>, <ci>, <cause\_type>, <reject\_cause>, <Active-Time> and <Periodic-TAU> are provided only if available. + +Refer clause 9.2 for possible <err> values. + +**NOTE 1:** If the EPS MT in GERAN/UTRAN/E-UTRAN also supports one or more of the circuit mode services, GPRS services or 5G services, the +CREG command and +CREG: result codes, the +CGREG command and +CGREG: result codes and the +C5GREG command and +C5GREG: result codes apply to the registration status and location information for those services. + +The read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. Location information elements <tac>, <ci> and <AcT>, if available, are returned only when <n>=2 and MT is registered in the network. The parameters [, <cause\_type>, <reject\_cause>], if available, are returned when <n>=3. + +Test command returns values supported as a compound value. The parameter [, <csg\_stat>], if available, is returned when <n>=4. The parameter [, <csginfo>], if available, is returned when <n>=5. + +### Defined values + +<n>: integer type + +- 0 disable network registration unsolicited result code +- 1 enable network registration unsolicited result code +CEREQ: <stat> +- 2 enable network registration and location information unsolicited result code +CEREQ: <stat>[, [<tac>], [<ci>], [<AcT>]] +- 3 enable network registration, location information and EMM cause value information unsolicited result code +CEREQ: <stat>[, [<tac>], [<ci>], [<AcT>][, <cause\_type>, <reject\_cause>]] +- 4 For a UE that wants to apply PSM, enable network registration and location information unsolicited result code +CEREQ: <stat>[, [<tac>], [<ci>], [<AcT>][, [, [<Active-Time>], [<Periodic-TAU>]]]] +- 5 For a UE that wants to apply PSM, enable network registration, location information and EMM cause value information unsolicited result code +CEREQ: <stat>[, [<tac>], [<ci>], [<AcT>][, [<cause\_type>], [<reject\_cause>][, [<Active-Time>], [<Periodic-TAU>]]]]] +- 6 enable network registration, location information, cause value information, CSG cell status information unsolicited result code +CREQ: <stat>[, [<lac>], [<ci>], [<AcT>][, <cause\_type>, <reject\_cause>]][, <csg\_stat>] +- 7 enable network registration, location information, cause value information, CSG cell status information and CSG cell information unsolicited result code +CREQ: <stat>[, [<lac>], [<ci>], [<AcT>][, <cause\_type>, <reject\_cause>]][, <csg\_stat>][, <csginfo>] + +<stat>: integer type; indicates the EPS registration status. + +- 0 not registered, MT is not currently searching an operator to register to +- 1 registered, home network +- 2 not registered, but MT is currently trying to attach or searching an operator to register to +- 3 registration denied +- 4 unknown (e.g. out of E-UTRAN coverage) +- 5 registered, roaming +- 6 registered for "SMS only", home network (not applicable) +- 7 registered for "SMS only", roaming (not applicable) +- 8 attached for emergency bearer services only (See NOTE 2) +- 9 registered for "CSFB not preferred", home network (not applicable) +- 10 registered for "CSFB not preferred", roaming (not applicable) +- 11 attached for access to RLOS (See NOTE 2a) (applicable only when <AcT> indicates E-UTRAN) + +NOTE 2: 3GPP TS 24.008 [8] and 3GPP TS 24.301 [83] specify the condition when the MT is considered as attached for emergency bearer services. + +NOTE 2a: 3GPP TS 24.301 [83] specifies the condition when the MT is considered as attached for access to RLOS. + +<tac>: string type; two byte tracking area code in hexadecimal format (e.g. "00C3" equals 195 in decimal). + +<ci>: string type; four byte E-UTRAN cell ID in hexadecimal format. + +<AcT>: integer type; indicates the access technology of the serving cell. The access technology type parameter <AcT> should not be used in terminals capable of only one access technology. + +- 0 GSM (not applicable) +- 1 GSM Compact (not applicable) +- 2 UTRAN (not applicable) +- 3 GSM w/EGPRS (see NOTE 3) (not applicable) +- 4 UTRAN w/HSDPA (see NOTE 4) (not applicable) +- 5 UTRAN w/HSUPA (see NOTE 4) (not applicable) +- 6 UTRAN w/HSDPA and HSUPA (see NOTE 4) (not applicable) +- 7 E-UTRAN +- 8 EC-GSM-IoT (A/Gb mode) (see NOTE 5) (not applicable) +- 9 E-UTRAN (NB-S1 mode) (see NOTE 6) +- 10 E-UTRA connected to a 5GCN (see NOTE 7) (not applicable) +- 11 NR connected to a 5G CN (see NOTE 7) (not applicable) +- 12 NG-RAN (not applicable) +- 13 E-UTRA-NR dual connectivity (see NOTE 8) +- 14 satellite E-UTRAN (NB-S1 mode) (see NOTE 9) +- 15 satellite E-UTRAN (WB-S1 mode) +- 16 satellite NG-RAN + +NOTE 3: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS. + +NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA. + +NOTE 5: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT. + +NOTE 6: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode). + +NOTE 7: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5GCN. + +NOTE 8: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core. + +NOTE 9: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving satellite cell supports satellite NB-IoT, which corresponds to E-UTRAN in NB-S1 mode. + +<cause\_type>: integer type; indicates the type of <reject\_cause>. + +- 0 Indicates that <reject\_cause> contains an EMM cause value, see 3GPP TS 24.301 [83] Annex A. +- 1 Indicates that <reject\_cause> contains a manufacturer-specific cause. + +<reject\_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by <cause\_type>. + +<Active-Time>: string type; one byte in an 8 bit format. Indicates the Active Time value (T3324) allocated to the UE in E-UTRAN. The Active Time value is coded as one byte (octet 3) of the GPRS Timer 2 information element coded as bit format (e.g. "00100100" equals 4 minutes). For the coding and the value range, see the GPRS Timer 2 IE in 3GPP TS 24.008 [8] Table 10.5.163/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.401 [82]. + +<Periodic-TAU>: string type; one byte in an 8 bit format. Indicates the extended periodic TAU value (T3412) allocated to the UE in E-UTRAN. The extended periodic TAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.401 [82]. + +<csg\_stat>: integer type; indicates the camping status on a CSG cell + +- 0 Indicates UE is not camped on CSG cell. +- 1 Indicates UE is currently camped on CSG cell. + +<CSGinfo>: string type; + +CSGinfo consists of CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC each delimited by a comma and in this particular order only. If any of the CSGType, HNB Name, or CSGID is unavailable, it shall be an empty field. See 3GPP TS 22.011[170], 3GPP TS 23.003 [[7] for details of CSG Type, HNB name and CSG ID representation. + +The display format is based on <format> value in +CSSGS command. In the alphanumeric format CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC would be displayed while in numeric format only CSGID and CSG Associated PLMN MCC MNC would be displayed. + +## Implementation + +Optional. + +This command is only applicable to UEs in E-UTRAN. + +### 10.1.23 PDP context read dynamic parameters +CGCONTRDP + +**Table 10.1.23-1: +CGCONTRDP action command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGCONTRDP[=<cid>] | [+CGCONTRDP: <cid>,<bearer_id>,<apn>[,<local_addr and subnet_mask>[,<gw_addr>[,<DNS_prim_addr>[,<DNS_sec_addr>[,<P-CSCF_prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signalling_Flag>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_Offload>[,<Local_Addr_Ind>[,<Non-IP_MTU>[,<Serving_PLMN_rate_control_value>[,<Reliable_Data_Service>[,<PS_Data_Off_Support>[,<PDU_session_id>[,<QFI>[,<SSC_mode>[,<S-NSSAI>[,<Access_type>[,<RQ_timer>[,<Always-on_ind>[,<Ethernet_MTU>[,<Unstructured_Link_MTU>[,<PDP_type>[,<EDC_policy_ind>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]<br><br>[<CR><LF>+CGCONTRDP: <cid>,<bearer_id>,<apn>[,<local_addr and subnet_mask>[,<gw_addr>[,<DNS_prim_addr>[,<DNS_sec_addr>[,<P-CSCF_prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signalling_Flag>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_Offload>[,<Local_Addr_Ind>[,<Non-IP_MTU>[,<Serving_PLMN_rate_control_value>[,<Reliable_Data_Service>[,<PS_Data_Off_Support>[,<PDU_session_id>[,<QFI>[,<SSC_mode>[,<S-NSSAI>[,<Access_type>[,<RQ_timer>[,<Always-on_ind>[,<Ethernet_MTU>[,<Unstructured_Link_MTU>[,<PDP_type>[,<EDC_policy_ind>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]<br><br>[...]] | +| +CGCONTRDP=? | +CGCONTRDP: (list of <cid>s associated with active contexts) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGCONTRDP=[<cid>] | | + +## **Description** + +The execution command returns the relevant information <bearer\_id>, <apn>, <local\_addr and subnet\_mask>, <gw\_addr>, <DNS\_prim\_addr>, <DNS\_sec\_addr>, <P-CSCF\_prim\_addr>, <P-CSCF\_sec\_addr>, <IM\_CN\_Signalling\_Flag>, <LIPA\_indication>, <IPv4\_MTU>, <WLAN\_Offload>, <Non-IP\_MTU>, <Serving\_PLMN\_rate\_control\_value>, <Reliable\_Data\_Service>, <PS\_Data\_Off\_Support>, <PDU\_session\_id>, <QFI>, <SSC\_mode>, <S-NSSAI>, <Access\_type>, <RQ\_timer>, <Always-on\_ind>, <Ethernet\_MTU>, <Unstructured\_Link\_MTU>, <PDP\_type>, <EDC\_policy\_ind> and <ECSConf\_info\_ind> for an active non secondary PDP context or a QoS flow of the default QoS rule with the context identifier <cid>. + +If the MT indicates more than two IP addresses of P-CSCF servers or more than two IP addresses of DNS servers, multiple lines of information per <cid> will be returned. + +If the MT has dual stack capabilities, at least one pair of lines with information is returned per <cid>. First one line with the IPv4 parameters followed by one line with the IPv6 parameters. If this MT with dual stack capabilities indicates more than two IP addresses of P-CSCF servers or more than two IP addresses of DNS servers, multiple of such pairs of lines are returned. + +NOTE: If the MT doesn't have all the IP addresses to be included in a line, e.g. in case the UE received four IP addresses of DNS servers and two IP addresses of P-CSCF servers, the parameter value representing an IP address that can not be populated is set to an empty string or an absent string. + +If the parameter <cid> is omitted, the relevant information for all active non secondary PDP contexts is returned. + +The test command returns a list of <cid>s associated with active non secondary contexts. + +### Defined values + +<cid>: integer type; specifies a particular non secondary PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands (see the +CGDCONT and +CGDSCONT commands). + +<bearer\_id>: integer type; identifies the bearer, i.e. the EPS bearer and the NSAPI. + +<apn>: string type; a logical name that was used to select the GGSN or the external packet data network. + +<local\_addr and subnet\_mask>: string type; shows the IP address and subnet mask of the MT. The string is given as dot-separated numeric (0-255) parameters on the form: + +"a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or + +"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP. + +<gw\_addr>: string type; shows the Gateway Address of the MT. The string is given as dot-separated numeric (0-255) parameters. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP. + +<DNS\_prim\_addr>: string type; shows the IP address of the primary DNS server. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP. + +<DNS\_sec\_addr>: string type; shows the IP address of the secondary DNS server. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP. + +<P\_CSCF\_prim\_addr>: string type; shows the IP address of the primary P-CSCF server. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP. + +<P\_CSCF\_sec\_addr>: string type; shows the IP address of the secondary P-CSCF server. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP. + +<IM\_CN\_Signalling\_Flag>: integer type; shows whether the PDP context is for IM CN subsystem-related signalling only or not. + +0 PDP context is not for IM CN subsystem-related signalling only + +1 PDP context is for IM CN subsystem-related signalling only + +<LIPA\_indication>: integer type; indicates that the PDP context provides connectivity using a LIPA PDN connection. This parameter cannot be set by the TE. + +0 indication not received that the PDP context provides connectivity using a LIPA PDN connection + +1 indication received that the PDP context provides connectivity using a LIPA PDN connection + +<IPv4\_MTU>: integer type; shows the IPv4 MTU size in octets. + +<WLAN\_Offload>: integer type; indicates whether traffic can be offloaded using the specified PDN connection via a WLAN or not. This refers to bits 1 and 2 of the WLAN offload acceptability IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.20. + +0 offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is not acceptable. + +1 offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable, but not acceptable in Iu mode. + +2 offloading the traffic of the PDN connection via a WLAN when in Iu mode is acceptable, but not acceptable in S1 mode. + +3 offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is acceptable. + +<Local\_Addr\_Ind>: integer type; indicates whether or not the MS and the network support local IP address in TFTs (see 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8] clause 10.5.6.3). + +0 indicates that the MS or the network or both do not support local IP address in TFTs + +1 indicates that the MS and the network support local IP address in TFTs + +<Non-IP\_MTU>: integer type; shows the Non-IP MTU size in octets. + +<Serving\_PLMN\_rate\_control\_value>: integer type; indicates the maximum number of uplink messages the UE is allowed to send in a 6 minute interval. This refers to octet 3 to 4 of the Serving PLMN rate control IE as specified in 3GPP TS 24.301 [8] clause 9.9.4.28. + +<Reliable\_Data\_Service>: integer type; indicates whether the UE is using Reliable Data Service for a PDN connection or not, see 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8] clause 10.5.6.3. + +0 Reliable Data Service is not being used for the PDN connection + +1 Reliable Data Service is being used for the PDN connection + +<PS\_Data\_Off\_Support>: integer type; indicates whether the network supports PS data off or not, see 3GPP TS 24.008 [8] clause 4.7.1.10 and 3GPP TS 24.301 [83] clause 6.3.10. + +0 indicates that the network does not support PS data off + +1 indicates that the network supports PS data off + +<PDU\_session\_id>: integer type; identifies the PDU session, see 3GPP TS 24.501 [161]. + +<QFI>: integer type; identifies the QoS flow, see 3GPP TS 24.501 [161]. + +<SSC\_mode>: integer type; indicates the session and service continuity (SSC) mode for the PDU session in 5GS, see 3GPP TS 23.501 [165]. + +0 indicates that the PDU session is associated with SSC mode 1 + +1 indicates that the PDU session is associated with SSC mode 2 + +2 indicates that the PDU session is associated with SSC mode 3 + +<S-NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the PDU session for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<Access\_type>: integer type; indicates the access type over which the PDU session is established in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +0 indicates that the established PDU is associated with 3GPP access + +1 indicates that the established PDU is associated with non-3GPP access + +<RQ\_timer>: integer type; indicates the timer value in seconds for reflective QoS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +<Always-on\_ind>: integer type; indicates whether the PDU session is an always-on PDU session, see 3GPP TS 24.501 [161]. + +0 indicates that the PDU session is not an always-on PDU session + +1 indicates that the PDU session is an always-on PDU session + +<Ethernet\_MTU>: integer type; shows the Ethernet frame payload MTU size in octets. + +<Unstructure\_Link\_MTU>: integer type; shows the unstructured link MTU size in octets. + +<PDP\_type>: string type; indicates the type of packet data protocol (see the +CGDCONT command) + +<EDC\_policy\_ind>: integer type; indicates whether the network allows EDC for the PDU session or the network requires EDC for the PDU session, see 3GPP TS 24.501 [161]. + +0 indicates that the EDC is allowed for the PDU session + +1 indicates that the EDC is required for the PDU session + +<RSN>: integer type; indicates the value of RSN, see 3GPP TS 24.501 [161] and 3GPP TS 24.526 [185]. + +0 indicates that the RSN is set to v1 + +1 indicates that the RSN is set to v2 + +<ECSConf\_info\_ind>: integer type; indicates whether the PDP context is for an ECS Configuration information, see 3GPP TS 23.558 [187] and 3GPP TS 24.501 [161]. + +0 indicates that ECS Configuration information is requested in the PCO + +1 indicates that ECS Configuration information is not requested in the PCO + +## Implementation + +Optional. + +## 10.1.24 Secondary PDP context read dynamic parameters +CGSCONTRDP + +**Table 10.1.24-1: +CGSCONTRDP action command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGSCONTRDP[=<cid>] | [+CGSCONTRDP: <cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_Flag>[,<WLAN_Offload>[,<PDU_session_id>,<QFI>]]]]<br><br>[<CR><LF>+CGSCONTRDP: <cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_Flag>[,<WLAN_Offload>[,<PDU_session_id>,<QFI>]]]]<br><br>[...]] | +| +CGSCONTRDP=? | +CGSCONTRDP: (list of <cid>s associated with active contexts) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGSCONTRDP=[<cid>] | | + +### Description + +The execution command returns <p\_cid>, <bearer\_id>, <IM\_CN\_Signalling\_Flag>, <WLAN\_Offload>, <PDU\_session\_id> and <QFI> for an active secondary PDP context or a QoS flow of non-default QoS rule with the context identifier <cid>. + +If the parameter <cid> is omitted, the <cid>, <p\_cid>, <bearer\_id>, <IM\_CN\_Signalling\_Flag>, <WLAN\_Offload>, <PDU\_session\_id> and <QFI> are returned for all active secondary PDP contexts or all QoS flows of non-default QoS rule. + +In EPS, the Traffic Flow parameters are returned. + +NOTE: Parameters for UE initiated and network initiated PDP contexts are returned. + +The test command returns a list of <cid>s associated with active secondary PDP contexts. + +### Defined values + +<cid>: integer type; specifies a particular active secondary PDP context or Traffic Flows definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands (see the +CGDCONT and +CGDSCONT commands). + +<p\_cid>: integer type; specifies a particular PDP context definition or default EPS context Identifier which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface (see the +CGDSCONT command). + +<bearer\_id>: integer type; identifies the bearer, EPS Bearer and NSAPI. + +<IM\_CN\_Signalling\_Flag>: integer type; shows whether the PDP context is for IM CN subsystem-related signalling only or not. + +- 0 PDP context is not for IM CN subsystem-related signalling only +- 1 PDP context is for IM CN subsystem-related signalling only + +<WLAN\_Offload>: integer type. An integer that indicates whether traffic can be offloaded using the specified PDN connection via a WLAN or not. This refers to bits 1 and 2 of the WLAN offload acceptability IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.20. + +- 0 offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is not acceptable. + +- 1 offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable, but not acceptable in Iu mode. +- 2 offloading the traffic of the PDN connection via a WLAN when in Iu mode is acceptable, but not acceptable in S1 mode. +- 3 offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is acceptable. + +<PDU\_session\_id>: integer type; identifies the PDU session, see 3GPP TS 24.501 [161]. + +<QFI>: integer type; identifies the QoS flow, see 3GPP TS 24.501 [161]. + +## Implementation + +Optional. + +## 10.1.25 Traffic flow template read dynamic parameters +CGTFTRDP + +**Table 10.1.25-1: +CGTFTRDP action command syntax** + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGTFTRDP[=<cid>] | <p>[+CGTFTRDP: <cid>,<packet filter identifier>,<evaluation precedence index>,<remote address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<local port range>,<remote port range>,<ipsec security parameter index (spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>,<NW packet filter Identifier>,<local address and subnet mask>,<QRI>,<destination MAC address>,<source MAC address>,<802.1Q C-TAG VID>,<802.1Q S-TAG VID>,<802.1Q C-TAG PCP/DEI>,<802.1Q S-TAG PCP/DEI>,<ethertype>]</p> <p>[<CR><LF>+CGTFTRDP: <cid>,<packet filter identifier>,<evaluation precedence index>,<remote address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<local port range>,<remote port range>,<ipsec security parameter index (spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>,<NW packet filter Identifier>,<local address and subnetmask>,<QRI>,<destination MAC address>,<source MAC address>,<802.1Q C-TAG VID>,<802.1Q S-TAG VID>,<802.1Q C-TAG PCP/DEI>,<802.1Q S-TAG PCP/DEI>,<ethertype>]</p> <p>[...]</p> | +| +CGTFTRDP=? | +CGTFTRDP: (list of <cid>s associated with active contexts) | +| <b>NOTE:</b> The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGTFTRDP=[<cid>] | | + +## Description + +The execution command returns the relevant information about Traffic Flow Template for an active secondary or non secondary PDP context specified by <cid> together with the additional network assigned values when established by + +the network. If the parameter <cid> is omitted, the Traffic Flow Templates for all active secondary and non secondary PDP contexts are returned. + +Parameters of both network and MT/TA initiated PDP contexts will be returned. + +The test command returns a list of <cid>s associated with active secondary and non secondary contexts. + +#### Defined values + +<cid>: integer type; Specifies a particular secondary or non secondary PDP context definition or Traffic Flows definition (see +CGDCONT and +CGDSCONT commands). + +For the following parameters, see also 3GPP TS 23.060 [47], 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +<packet filter identifier>: integer type. The value range is from 1 to 16. + +NOTE 1: While the numbering of packet filter identifier in this specification ranges from 1 to 16, the numbering of packet filter identifier in 3GPP TS 24.008 [8] ranges from 0 to 15. It is up to MT implementation to perform a mapping between the two value ranges. + +<evaluation precedence index>: integer type. The value range is from 0 to 255. + +<remote address and subnet mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: + +"a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or + +"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16" for IPv6. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGTFTRDP. + +<protocol number (ipv4) / next header (ipv6)>: integer type. The value range is from 0 to 255. + +<local port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t". + +<remote port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t". + +<ipsec security parameter index (spi)>: numeric value in hexadecimal format. The value range is from 00000000 to FFFFFFFF. + +<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form "t.m". + +<flow label (ipv6)>: numeric value in hexadecimal format. The value range is from 00000 to FFFFF. Valid for IPv6 only. + +<direction> integer type. Specifies the transmission direction in which the Packet Filter shall be applied. + +- 0 Pre Release 7 TFT Filter (see 3GPP TS 24.008 [8], table 10.5.162) +- 1 Uplink +- 2 Downlink +- 3 Bidirectional (Used for Uplink and Downlink) + +<NW packet filter Identifier> integer type. The value range is from 1 to 16. In EPS the value is assigned by the network when established + +NOTE 2: While the numbering of packet filter identifier in this specification ranges from 1 to 16, the numbering of packet filter identifier in 3GPP TS 24.008 [8] ranges from 0 to 15. It is up to MT implementation to perform a mapping between the two value ranges. + +<local address and subnet mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: + "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or + "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16", for IPv6. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +CGTFTRDP. + +<QRI>: integer type. Identifies the QoS rule, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +<destination MAC address>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: "a1.a2.a3.a4.a5.a6". + +<source MAC address>: string type. The string is given as dot-separated numeric (0-255) parameters on the form: "a1.a2.a3.a4.a5.a6". + +<802.1Q C-TAG VID>: numeric value in hexadecimal format. The value range is from 000 to FFF. + +<802.1Q S-TAG VID>: numeric value in hexadecimal format. The value range is from 000 to FFF. + +<802.1Q C-TAG PCP/DEI>: numeric value in hexadecimal format. The value range is from 0 to F. + +<802.1Q S-TAG PCP/DEI>: numeric value in hexadecimal format. The value range is from 0 to F. + +<ethertype>: numeric value in hexadecimal format. The value range is from 0000 to FFFF. + +NOTE 3: Some of the above listed attributes can coexist in a Packet Filter while others mutually exclude each other. The possible combinations are shown in 3GPP TS 23.060 [47], 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +## Implementation + +Optional. + +## 10.1.26 Define EPS quality of service +CGEQOS + +**Table 10.1.26-1: +CGEQOS parameter command syntax** + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGEQOS=<cid>[, <QCI>[, <DL_GBR>, <UL_GBR>[, <DL_MBR>, <UL_MBR>]]] | +CME ERROR: <err> | +| +CGEQOS? | [+CGEQOS: <cid>, <QCI>, [<DL_GBR>, <UL_GBR>], [<DL_MBR>, <UL_MBR>]]<br><br>[<CR><LF>+CGEQOS: <cid>, <QCI>, [<DL_GBR>, <UL_GBR>], [<DL_MBR>, <UL_MBR>]<br>[...]] | +| +CGEQOS=? | +CGEQOS: (range of supported <cid>s) , (list of supported <QCI>s) , (list of supported <DL_GBR>s) , (list of supported <UL_GBR>s) , (list of supported <DL_MBR>s) , (list of supported <UL_MBR>s) | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +## Description + +The set command allows the TE to specify the EPS Quality of Service parameters <cid>, <QCI>, [<DL\_GBR> and <UL\_GBR>] and [<DL\_MBR> and <UL\_MBR>] for a PDP context or Traffic Flows (see 3GPP TS 24.301 [83] and 3GPP TS 23.203 [85]). When in UMTS/GPRS the MT applies a mapping function to UMTS/GPRS Quality of Service. Refer clause 9.2 for possible <err> values. + +A special form of the set command, +CGEQOS= <cid> causes the values for context number <cid> to become undefined. + +The read command returns the current settings for each defined QoS. + +The test command returns the ranges of the supported parameters as compound values. + +## Defined values + +<cid>: integer type; specifies a particular EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<QCI>: integer type; specifies a class of EPS QoS (see 3GPP TS 23.203 [85] and 3GPP TS 24.301 [83]). + +- 0 QCI is selected by network +- [1 – 4] value range for guaranteed bit rate Traffic Flows +- [71 – 76] value range for guaranteed bit rate Traffic Flows +- [82 – 85] value range for guaranteed bit rate Traffic Flows +- [5 – 10] value range for non-guaranteed bit rate Traffic Flows +- 79, 80 value for non-guaranteed bit rate Traffic Flows +- [128 – 254] value range for Operator-specific QCIs + +The QCI values 65, 66, 67, 69 and 70 are not allowed to be requested by the UE. If the TE requests a QCI parameter 65, 66, 67, 69 or 70, the MT responds with result code +CME ERROR: 181 (unsupported QCI value). + +The QCI value of 10 can be requested by the UE only when in satellite E-UTRAN access. If the TE requests a QCI value 10 over another access, the MT responds with result code +CME ERROR: 181 (unsupported QCI value). + +<DL\_GBR>: integer type; indicates DL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<UL\_GBR>: integer type; indicates UL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<DL\_MBR>: integer type; indicates DL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<UL\_MBR>: integer type; indicates UL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +## Implementation + +Optional. + +## 10.1.27 EPS quality of service read dynamic parameters +CGEQOSRDP + +**Table 10.1.27-1: +CGEQOSRDP action command syntax** + +| Command | Possible Response(s) | +|--------------------|------------------------------------------------------------------------| +| +CGEQOSRDP[=<cid>] | [+CGEQOSRDP: <cid>, <QCI>, [<DL_GBR>, <UL_GBR>], [<DL_MBR>, <UL_MBR>]] | + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| | [, <DL_AMBR>, <UL_AMBR>]]<br><br>[<CR><LF>+CGEQOSRDP: <cid>, <QCI>, [<DL_GBR>, <UL_GBR>], [<DL_MBR>, <UL_MBR>]<br>[, <DL_AMBR>, <UL_AMBR>]<br><br>[...]] | +| +CGEQOSRDP=? | +CGEQOSRDP: (list of <cid>s associated with active contexts) | +| NOTE: The syntax of the AT Set Command is corrected to be according to ITU-T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGEQOSRDP=[<cid>] | | + +## Description + +The execution command returns the Quality of Service parameters <QCI>, [<DL\_GBR> and <UL\_GBR>] and [<DL\_MBR> and <UL\_MBR>] of the active secondary or non secondary PDP context associated to the provided context identifier <cid>. + +If the parameter <cid> is omitted, the Quality of Service parameters for all secondary and non secondary active PDP contexts are returned. + +The test command returns a list of <cid>s associated with secondary or non secondary active PDP contexts. + +Parameters of both network and MT/TA initiated PDP contexts will be returned. + +## Defined values + +<cid>: integer type; specifies a particular Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<QCI>: integer type; specifies a class of EPS QoS (see 3GPP TS 23.203 [85] and 3GPP TS 24.301 [83]). + +- 0 QCI is selected by network +- [1 – 4] value range for guaranteed bit rate Traffic Flows +- 65, 66, 67 values for guaranteed bit rate Traffic Flows +- [71 – 76] value range for guaranteed bit rate Traffic Flows +- [82 – 85] value range for guaranteed bit rate Traffic Flows +- [5 – 10] value range for non-guaranteed bit rate Traffic Flows +- 69, 70, 79, 80 values for non-guaranteed bit rate Traffic Flows +- [128 – 254] value range for Operator-specific QCIs + +<DL\_GBR>: integer type; indicates DL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<UL\_GBR>: integer type; indicates UL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<DL\_MBR>: integer type; indicates DL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<UL\_MBR>: integer type; indicates UL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]). + +<DL\_AMBR>: integer type; indicates DL APN aggregate MBR (see 3GPP TS 24.301 [83]). The value is in kbit/s. + +<UL\_AMBR>: integer type; indicates UL APN aggregate MBR (see 3GPP TS 24.301 [83]). The value is in kbit/s. + +NOTE: If multiple lines in a response belong to the same PDN connection they contain the same <DL\_AMBR> <UL\_AMBR> values. + +#### Implementation + +Optional. + +### 10.1.28 UE modes of operation for EPS +CEMODE + +**Table 10.1.28-1: +CEMODE parameter command syntax** + +| Command | Possible Response(s) | +|------------------|--------------------------------------| +| +CEMODE=[<mode>] | +CME ERROR: <err> | +| +CEMODE? | +CEMODE: <mode> | +| +CEMODE=? | +CEMODE: (list of supported <mode>s) | + +#### Description + +The set command is used to set the MT to operate according to the specified mode of operation for EPS, see 3GPP TS 24.301 [83]. If the requested mode of operation is not supported, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer clause 9.2 for possible <err> values. + +The read command returns the mode of operation set by the TE, independent of the current serving cell capability and independent of the current serving cell Access Technology. + +The test command is used for requesting information on the supported MT modes of operation as a compound value. + +#### Defined values + +<mode>: integer type; indicates the mode of operation. The default value is manufacturer specific. + +- 0 PS mode 2 of operation +- 1 CS/PS mode 1 of operation +- 2 CS/PS mode 2 of operation +- 3 PS mode 1 of operation + +NOTE: the definition for UE modes of operation can be found in 3GPP TS 24.301 [83] + +#### Implementation + +Optional. + +### 10.1.29 Delete non-active PDP contexts +CGDEL + +**Table 10.1.29-1: +CGDEL action command syntax** + +| Command | Possible Response(s) | +|----------------|------------------------------------------------------| +| +CGDEL[=<cid>] | [+CGDEL: <cid>[, <cid>[, ...]]]<br>+CME ERROR: <err> | +| +CGDEL=? | | + +#### Description + +The execution command +CGDEL=<cid> removes the indicated PDP context and removes all associated data related to the indicated PDP contexts that are not activated. The AT command will not delete or remove information for activated PDP contexts. The removed PDP context is listed by the +CGDEL: <cid> intermediate result code. If the initial PDP context is supported (see clause 10.1.0), +CGDEL=0 will return ERROR and the context will not be removed. + +If <cid> points to a primary PDP context, the PDP context will be deleted together with all linked secondary PDP contexts if none of the PDP contexts are activated. + +If <cid> points to a secondary PDP context, the PDP context will be deleted if it is not activated. + +A special form of the command can be given as +CGDEL (with the =<cid> omitted). In this form, all primary PDP contexts that are not activated or have any activated secondary PDP contexts will be removed and all secondary PDP contexts that are not activated will be removed. The associated data of all the deleted PDP contexts will be removed, and the removed PDP context are listed by the +CGDEL: <cid>[, <cid>[, . . .]] intermediate result code. Activated PDP contexts will not cause this form of the command to return ERROR or +CME ERROR. Refer clause 9.2 for possible <err> values. + +If the initial PDP context is supported (see clause 10.1.0), +CGDEL (with the =<cid> omitted) will not cause the initial PDP context to be removed or cause +CGDEL to return ERROR. + +NOTE: +CGDEL will remove associated PDP context data that can be set by the AT commands +CGDCONT, +CGDSCONT, +CGTFT, +CGQREQ, +CGQMIN, +CGEQREQ, +CGEQMIN, +CGEQOS, +CGAUTH and +C5GQOS. + +For an attempt to delete PDP context(s) which would violate these rules, a +CME ERROR response is returned. Refer clause 9.2 for possible <err> values. + +#### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +#### Implementation + +Optional. + +### 10.1.30 Signalling connection status +CSCON + +Table 10.1.30-1: +CSCON parameter command syntax + +| Command | Possible response(s) | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CSCON=[<n>] | +CME ERROR: <err> | +| +CSCON? | +CSCON: <n>[, <mode>[, <state>[, <access>]]]<br>[<CR><LF>+CSCON: <n>[, <mode>[, <state>[, <access>[, <coreNetwork>]]]]]<br>[...]<br>+CME ERROR: <err> | +| +CSCON=? | +CSCON: (list of supported <n>s) | + +#### Description + +The set command controls the presentation of an unsolicited result code +CSCON. If <n>=1, +CSCON: <mode> is sent from the MT when the connection mode of the MT is changed. If <n>=2 and there is a state within the current mode, +CSCON: <mode>[, <state>] is sent from the MT when the connection mode or state information of the MT is changed. If <n>=3, +CSCON: <mode>[, <state>[, <access>]] is sent from the MT when the connection mode, state or access information of the MT is changed. If <n>=4, + ++CSCON: <mode>[, <state>[, <access>[, <coreNetwork>]]] is sent from the MT. If setting fails, an MT error, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +When the MT is in UTRAN, E-UTRAN or NG-RAN, the <mode> refers to idle when no PS signalling connection between UE and network is setup and to connected mode when a PS signalling connection between UE and network is setup. When the UE is in GERAN, the mode refers to idle when the MT is in either the IDLE state or the STANDBY state and to connected mode when the MT is in READY state. + +The <state> indicates the state of the MT when the MT is in GERAN, UTRAN connected mode, E-UTRAN or NG-RAN. + +The <access> indicates the current radio access type of the MT when the MT is in GERAN, UTRAN, E-UTRAN or NG-RAN. + +The <coreNetwork> indicates the core network type the MT is connected to when the MT is in E-UTRAN or NG-RAN. + +The read command returns the status of result code presentation and an integer <mode> which shows whether the MT is currently in idle mode or connected mode. State information <state> is returned only when <n>=2. Radio access type information <access> is returned only when <n>=3. Core network type information <coreNetwork> is returned only when <n>=4. For Multi-RAT Dual Connectivity (MR-DC) architecture (see 3GPP TS 37.340 [162]), information is presented for the master RAT followed by optionally, information for each of the secondary RATs on a separate line. + +Test command returns supported values as a compound value. + +#### Defined values + +<n>: integer type + +- 0 disable unsolicited result code +- 1 enable unsolicited result code +CSCON: <mode> +- 2 enable unsolicited result code +CSCON: <mode>[, <state>] +- 3 enable unsolicited result code +CSCON: <mode>[, <state>[, <access>]] +- 4 enable unsolicited result code +CSCON: <mode>[, <state>[, <access>[, <coreNetwork>]]] + +<mode>: integer type; indicates the signalling connection status + +- 0 idle +- 1 connected + +<state>: integer type; indicates the CS or PS state while in GERAN and the RRC state information if the MT is in connected mode while in UTRAN, E-UTRAN and NG-RAN. + +- 0 UTRAN URA\_PCH state +- 1 UTRAN Cell\_PCH state +- 2 UTRAN Cell\_FACH state +- 3 UTRAN Cell\_DCH state +- 4 GERAN CS connected state +- 5 GERAN PS connected state +- 6 GERAN CS and PS connected state +- 7 E-UTRAN connected state +- 8 NG-RAN connected state + +9 NG-RAN inactive state (see 3GPP TS 38.331 [160]). + +<access>: integer type; indicates the current radio access type. + +- 0 Indicates usage of radio access of type GERAN, see 3GPP TS 45.001 [146]. +- 1 Indicates usage of radio access of type UTRAN TDD, see 3GPP TS 25.212 [144]. +- 2 Indicates usage of radio access of type UTRAN FDD, see 3GPP TS 25.212 [144]. +- 3 Indicates usage of radio access of type E-UTRA TDD, see 3GPP TS 36.300 [145]. +- 4 Indicates usage of radio access of type E-UTRA FDD, see 3GPP TS 36.300 [145]. +- 5 Indicates usage of radio access of type NR, see 3GPP TS 38.300 [159]. + +<coreNetwork>: integer type; indicates the core network type the UE is connected to. + +- 0 Indicates MT is connected to EPC, see 3GPP TS 23.401 [82]. +- 1 Indicates MT is connected to 5GCN, see 3GPP TS 23.501 [165]. + +## Implementation + +Optional. + +### 10.1.31 Define PDP context authentication parameters +CGAUTH + +**Table 10.1.31-1: +CGAUTH parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CGAUTH=<cid>[, <auth_prot>[, <userid>[, <password>[, <DN_id>]]]] | +CME ERROR: <err> | +| +CGAUTH? | [+CGAUTH: <cid>, <auth_prot>[, <userid>, <password>], [<DN_id>]<br>[<CR><LF>+CGAUTH: <cid>, <auth_prot>, <userid>, <password>], [<DN_id>]<br>[...]]] | +| +CGAUTH=? | +CGAUTH: (range of supported <cid>s), (list of supported <auth_prot>s), (length of supported <userid>s), (length of supported <password>s) | + +## Description + +Set command allows the TE to specify authentication parameters for a PDP context identified by the (local) context identification parameter <cid> used during the PDP context activation and the PDP context modification procedures. Since the <cid> is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, +CGAUTH is effectively as an extension to these commands. Refer clause 9.2 for possible <err> values. + +A special form of the set command, +CGAUTH=<cid> causes the authentication parameters for context number <cid> to become undefined. + +The read command returns the current settings for each defined context. + +The test command returns values supported as compound values. + +## Defined values + +<cid>: integer type. Specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<auth\_prot>: integer type. Authentication protocol used for this PDP context. + +- 0 None. Used to indicate that no authentication protocol is used for this PDP context. Username and password are removed if previously specified. +- 1 PAP +- 2 CHAP +- 3 DN authentication (EAP authentication) + +<userid>: String type. Username for access to the IP network. + +<password>: String type. Password for access to the IP network. + +<DN\_id>: string type in UTF-8, indicates a Data Network (DN) specific identity of the UE in the network access identifier (NAI) format according to IETF RFC 7542 [37], encoded as UTF-8 string, see 3GPP TS 24.501 [161], clause 9.11.4.15. + +## Implementation + +Optional. + +## 10.1.32 Initial PDP context activation +CIPCA + +**Table 10.1.32-1: +CIPCA parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------|----------------------------------------------------------------------------| +| +CIPCA=[<n>[, <AttachWithoutPDN>] ] | | +| +CIPCA? | +CIPCA: <n>[, <AttachWithoutPDN>] | +| +CIPCA=? | +CIPCA: (list of supported <n>s) , (list of supported <AttachWithoutPDN>s) | + +## Description + +The set command controls whether an initial PDP context (see clause 10.1.0) shall be established automatically following an attach procedure when the UE is attached to GERAN or UTRAN RATs and whether the UE is attached to E-UTRAN with or without a PDN connection. + +For 5GS, the command controls whether an initial PDU session shall be established automatically following initial registration. + +For <n>≠0, deactivating the last (active) PDP context can lead to a (re)establishment of the initial PDP context. Changing setting of <n> from 0 to 1 will cause an immediate attempt to (re)establish the initial PDP context if no PDP context is active. Changing <n> from 0 to 2 will if not roaming cause an immediate attempt to (re)establish the initial PDP context if no other PDP context is active. The value of <n>=3 applies to E-UTRAN or NG-RAN RATs and does not change the setting of PDP context activation in GERAN or UTRAN RATs. Changing <n> will never cause a PDP context deactivation. + +For <AttachWithoutPDN>=1, the EPS Attach is performed without a PDN connection. + +NOTE: For this command, the term roaming corresponds to being registered to a VPLMN which is not equivalent to HPLMN or EHPLMN. + +The read command returns the current setting of the command. + +The test command returns values supported as a compound value. + +## Defined values + +<n>: integer type. Activation of PDP context upon attach. + +- 0 Do not activate +- 1 Always activate +- 2 Activate when not roaming +- 3 No change in current setting + +<AttachWithoutPDN>: integer type. EPS Attach with or without PDN connection. + +- 0 EPS Attach with PDN connection +- 1 EPS Attach without PDN connection + +### Implementation + +Optional. + +## 10.1.33 No more PS data +CNMPSD + +**Table 10.1.33-1: +CNMPSD action command syntax** + +| Command | Possible Response(s) | +|-----------|----------------------| +| +CNMPSD | | +| +CNMPSD=? | | + +### Description + +This command indicates that no application is expected to exchange data. + +When in UTRAN, if further conditions defined in 3GPP TS 25.331 [74] are met, this can cause transmission of a SIGNALLING CONNECTION RELEASE INDICATION message with the cause "UE Requested PS Data session end". + +When in E-UTRAN or E-UTRA connected to a 5GCN (see NOTE 2), if further conditions defined in 3GPP TS 36.331 [86] are met, this can cause transmission of a UEAssistanceInformation message with powerPrefIndication set to "lowPowerConsumption" to the network. For BL UEs or NB-IoT UEs, if further conditions defined in 3GPP TS 36.321 [158] and 3GPP TS 36.331 [86] are met, this can cause triggering of the Release Assistance Indication. + +NOTE 1: See clause 10.1.38 for a command applicable to an MT using E-UTRAN, where the MT has a preference for a configuration that is not optimized for power saving. + +NOTE 2: E-UTRA can be connected to EPC, 5GCN or both. + +When in NR, if further conditions defined in 3GPP TS 38.331 [160] are met, this can cause transmission to the network of a UEAssistanceInformation message including releasePreference with preferredRRC-State to transition out of RRC\_CONNECTED state. + +This command may be used in both normal and modem compatibility modes. + +### Implementation + +Optional. + +## 10.1.34 UE's usage setting for EPS and 5GS +CEUS + +**Table 10.1.34-1: +CEUS parameter command syntax** + +| Command | Possible Response(s) | +|-------------------|----------------------| +| +CEUS=[<setting>] | | + +| | | +|---------|---------------------------------------| +| +CEUS? | +CEUS: <setting> | +| +CEUS=? | +CEUS: (list of supported <setting>s) | + +### Description + +The set command is used to set the MT to operate according to the specified UE's usage setting for EPS (see 3GPP TS 24.301 [83]) and 5GS (see 3GPP TS 24.501 [161]). A UE that supports both S1 mode and N1 mode has a single UE's usage setting which applies to both EPS and 5GS. + +The read command returns the usage setting set by the TE. + +The test command is used for requesting information on the supported MT setting(s) as a compound value. + +### Defined values + +<setting>: integer type; indicates the usage setting of the UE. The default value is manufacturer specific. + +- 0 voice centric +- 1 data centric + +NOTE: The definition for UE's usage setting can be found in 3GPP TS 24.301 [83]. + +### Implementation + +Optional. + +## 10.1.35 UE's voice domain preference E-UTRAN +CEVDP + +**Table 10.1.35-1: +CEVDP parameter command syntax** + +| Command | Possible Response(s) | +|--------------------|----------------------------------------| +| +CEVDP=[<setting>] | | +| +CEVDP? | +CEVDP: <setting> | +| +CEVDP=? | +CEVDP: (list of supported <setting>s) | + +### Description + +The set command is used to set the MT to operate according to the specified voice domain preference for E-UTRAN. + +The read command returns the setting, independent of the current serving cell capability and independent of the current serving cell's access technology. + +Test command returns supported values as a compound value. + +### Defined values + +<setting>: integer type; indicates the voice domain preference of the UE. The default value is manufacturer specific. + +- 1 CS Voice only +- 2 CS Voice preferred, IMS PS Voice as secondary +- 3 IMS PS Voice preferred, CS Voice as secondary +- 4 IMS PS Voice only + +NOTE: The definition for the UE's voice domain preference for E-UTRAN can be found in 3GPP TS 24.167 [102], clause 5.27. + +**Implementation** + +Optional. + +**10.1.36 UE's voice domain preference UTRAN +CVDP****Table 10.1.36-1: +CVDP parameter command syntax** + +| Command | Possible Response(s) | +|-----------------|---------------------------------------| +| +CVDP=<setting> | | +| +CVDP? | +CVDP: <setting> | +| +CVDP=? | +CVDP: (list of supported <setting>s) | + +**Description** + +The set command is used to set the MT to operate according to the specified voice domain preference for UTRAN. + +The read command returns the setting, independent of the current serving cell capability and independent of the current serving cell's access technology. + +Test command returns supported values as a compound value. + +**Defined values** + +<setting>: integer type; indicates the voice domain preference of the UE. The default value is manufacturer specific. + +- 1 CS Voice only +- 2 CS Voice preferred, IMS PS Voice as secondary +- 3 IMS PS Voice preferred, CS Voice as secondary + +NOTE: The definition for the UE's voice domain preference for UTRAN can be found in 3GPP TS 24.167 [102], clause 5.30. + +**Implementation** + +Optional. + +**10.1.37 UE's mobility management IMS voice termination +CMMIVT****Table 10.1.QT3-1: +CMMIVT parameter command syntax** + +| Command | Possible Response(s) | +|-------------------|-----------------------------------------| +| +CMMIVT=<setting> | | +| +CMMIVT? | +CMMIVT: <setting> | +| +CMMIVT=? | +CMMIVT: (list of supported <setting>s) | + +**Description** + +The set command is used to set the MT to perform additional procedures as specified in 3GPP TS 24.008 [8] and 3GPP TS 24.301 [83] to support terminating access domain selection by the network. + +The read command returns the setting, independent of the current serving cell capability and independent of the current serving cell's access technology. + +Test command returns supported values as a compound value. + +**Defined values** + +<setting>: integer type; indicates the mobility management IMS voice termination preference of the UE. The default value is manufacturer specific. + +- 1 Mobility Management for IMS Voice Termination disabled +- 2 Mobility Management for IMS Voice Termination enabled + +NOTE: The definition of the UE's mobility management IMS voice termination values can be found in 3GPP TS 24.167 [102], clause 5.31. + +**Implementation** + +Optional. + +This command is only applicable to UEs in GERAN, UTRAN and E-UTRAN. + +## 10.1.38 Power preference indication for EPS and 5GS +CEPPI + +**Table 10.1.38-1: +CEPPI action command syntax** + +| Command | Possible Response(s) | +|---------------------------|-------------------------------------------------| +| +CEPPI=<power preference> | | +| +CEPPI=? | +CEPPI: (list of supported <power preference>s) | + +**Description** + +This command indicates whether the MT prefers a configuration primarily optimised for power saving or not. + +When in E-UTRAN or E-UTRA connected to a 5GCN (see NOTE), if further conditions defined in 3GPP TS 36.331 [86] are met, this can cause transmission of a UEAssistanceInformation message with powerPrefIndication set to <power preference> to the network. + +NOTE: E-UTRA can be connected to EPC, 5GCN or both. + +Test command returns the values supported as a compound value. + +**Defined values** + +<power preference>: integer type; indicates the power consumption preference of the MT. + +- 0 normal +- 1 low power consumption + +**Implementation** + +Optional. + +This command is not applicable to UEs camped on NR in this release of the specification. + +## 10.1.39 WLAN offload assistance data +CWLANOLAD + +**Table 10.1.39-1: +CWLANOLAD parameter command syntax** + +| Command | Possible response(s) | +|------------------|----------------------| +| +CWLANOLAD=[<n>] | +CME ERROR: <err> | + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CWLANOLAD? | +CWLANOLAD: <n>[,<threshRSCPLow>,<threshRSCPHigh>[,<threshEcnoLow>,<threshEcnoHigh>[,<threshRSRPLow>,<threshRSRPHigh>[,<threshRSRQLow>,<threshRSRQHigh>[,<threshChUtilLow>,<threshChUtilHigh>[,<threshBackhRateDLLow>,<threshBackhRateDLHigh>[,<threshBackhRateULLow>,<threshBackhRateULHigh>[,<threshBeaconRSSILow>,<threshBeaconRSSIHigh>[,<opi>[,<tSteering>[,<WLANIdentifierListLength>[,<ssid_1>,<bssid_1>,<hessid_1>[,<ssid_2>,<bssid_2>,<hessid_2>[,...]]]]]]]]]]]]]]]]] | +| +CWLANOLAD=? | +CWLANOLAD: (list of supported <n>s), (list of supported <threshRSCPLow>s), (list of supported <threshRSCPHigh>s), (list of supported <threshEcnoLow>s), (list of supported <threshEcnoHigh>s), (list of supported <threshRSRPLow>s), (list of supported <threshRSRPHigh>s), (list of supported <threshRSRQLow>s), (list of supported <threshRSRQHigh>s), (list of supported <threshChUtilLow>s), (list of supported <threshChUtilHigh>s), (list of supported <threshBackhRateDLLow>s), (list of supported <threshBackhRateDLHigh>s), (list of supported <threshBackhRateULLow>s), (list of supported <threshBackhRateULHigh>s), (list of supported <threshBeaconRSSILow>s), (list of supported <threshBeaconRSSIHigh>s), (list of supported <tSteering>s), (list of supported <WLANIdentifierListLength>s) | + +### **Description** + +Set command enables or disables the WLAN offload assistance data reporting. If reporting is enabled by <n>=1, the MT returns the following unsolicited result code from MT to TE whenever the WLAN offload assistance data changes at the MT: + ++CWLANOLADI: [,<threshRSCPLow>,<threshRSCPHigh>[,<threshEcnoLow>,<threshEcnoHigh>[,<threshRSRPLow>,<threshRSRPHigh>[,<threshRSRQLow>,<threshRSRQHigh>[,<threshChUtilLow>,<threshChUtilHigh>[,<threshBackhRateDLLow>,<threshBackhRateDLHigh>[,<threshBackhRateULLow>,<threshBackhRateULHigh>[,<threshBeaconRSSILow>,<threshBeaconRSSIHigh>[,<opi>[,<tSteering>[,<WLANIdentifierListLength>[,<ssid\_1>,<bssid\_1>,<hessid\_1>[,<ssid\_2>,<bssid\_2>,<hessid\_2>[,...]]]]]]]]]]]]]]]]] + +Refer IE *WLAN-OffloadConfig* in 3GPP TS 36.331 [86] clause 6.3.6. + +If a setting is not supported by the MT, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current status of <n> and the WLAN offload assistance data currently available at the MT. + +Test command returns the values supported by MT as compound values. + +### **Defined values** + +<n>: integer type + +- 0 disable WLAN offload assistance data unsolicited result code +- 1 enable WLAN offload assistance data unsolicited result code +CWLANOLADI + +<threshRSCPLow>: integer type; indicates the threshold for received signal code power for offloading traffic from UTRAN to WLAN. Refer parameter <rscp> in clause 8.69. + +<threshRSCPHigh>: integer type; indicates the threshold for received signal code power for offloading traffic from WLAN to UTRAN. Refer parameter <rscp> in clause 8.69. + +<threshEcnoLow>: integer type; indicates the threshold for ratio of the received energy per PN chip to the total received power spectral density for offloading traffic from UTRAN to WLAN. Refer parameter <ecno> in clause 8.69. + +<threshEcnoHigh>: integer type; indicates the threshold for ratio of the received energy per PN chip to the total received power spectral density for offloading traffic from WLAN to UTRAN. Refer parameter <ecno> in clause 8.69. + +<threshRSRPLow>: integer type; indicates the threshold for reference signal received power for offloading traffic from E-UTRAN to WLAN. Refer parameter <rsrp> in clause 8.69. + +<threshRSRPHigh>: integer type; indicates the threshold for reference signal received power for offloading traffic from WLAN to E-UTRAN. Refer parameter <rsrp> in clause 8.69. + +<threshRSRQLow>: integer type; indicates the threshold for reference signal received quality for offloading traffic from E-UTRAN to WLAN. Refer parameter <rsrq> in clause 8.69. + +<threshRSRQHigh>: integer type; indicates the threshold for reference signal received quality for offloading traffic from WLAN to E-UTRAN. Refer parameter <rsrq> in clause 8.69. + +<threshChUtilLow>: integer type; indicates the low threshold value of WLAN channel utilization (BSS load) obtained from 802.11 (Beacon or Probe Response) signalling, see IEEE 802.11 [152]. + +<threshChUtilHigh>: integer type; indicates the high threshold value of WLAN channel utilization (BSS load) obtained from 802.11 (Beacon or Probe Response) signalling, see IEEE 802.11 [152]. + +<threshBackhRateDLLow>: integer type; indicates the low threshold value of backhaul available downlink bandwidth for traffic offloading to UTRAN or E-UTRAN, see Hotspot 2.0 (Release 2) Technical Specification [151]. + +<threshBackhRateDLHigh>: integer type; indicates the high threshold value of backhaul available downlink bandwidth for traffic offloading to WLAN, see Hotspot 2.0 (Release 2) Technical Specification [151]. + +<threshBackhRateULLow>: integer type; indicates the low threshold value of backhaul available uplink bandwidth for traffic offloading to UTRAN or E-UTRAN, see Hotspot 2.0 (Release 2) Technical Specification [151]. + +<threshBackhRateDLHigh>: integer type; indicates the high threshold value of backhaul available uplink bandwidth for traffic offloading to WLAN. Refer to Hotspot 2.0 (Release 2) Technical Specification [151]. + +<threshBeaconRSSILow>: integer type; indicates the low threshold value of beacon RSSI used for traffic offloading to UTRAN or E-UTRAN see IEEE 802.11 [152]. + +<threshBeaconRSSIHigh>: integer type; indicates the high threshold value of beacon RSSI used for traffic offloading to WLAN, see IEEE 802.11 [152]. + +<opi>: integer type; A 16-bit integer formatted as a bitmap that specifies the Offload Preference Indicator, see 3GPP TS 24.312 [153] + +<tSteering>: integer type; indicates the timer value in seconds during which the rules should be fulfilled before starting traffic offloading between E-UTRAN and WLAN. + +<WLANIdentifierListLength>: integer type; indicates the number of entries in WLAN identifier list which is a tuple consisting of the <ssid>, the <bssid> and the <hssid> identifiers. If an identifier is not present for a tuple, it will be indicated as an empty string. + +<ssid>: string type; indicates the 802.11 Service Set Identifier (SSID), see IEEE 802.11 [152]. + +<bssid>: string type; indicates the 802.11 Basic Service Set Identifier (BSSID), see IEEE 802.11 [152]. + +<hssid>: string type; indicates the 802.11 Homogenous Extended Service Set Identifier (HESSID), see IEEE 802.11 [152]. + +## Implementation + +Optional. + +## 10.1.40 WLAN offload cell measurement +CWLANOLCM + +**Table 10.1.40-1: +CWLANOLCM parameter command syntax** + +| Command | Possible response(s) | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CWLANOLCM=[<n>] | +CME ERROR: <err> | +| +CWLANOLCM? | +CWLANOLCM: <n>,<rscp>,<ecno>,<rsrp>,<rsrq> | +| +CWLANOLCM=? | +CWLANOLCM: (list of supported <n>s) , (list of supported <rscp>s) , (list of supported <ecno>s) , (list of supported <rsrp>s) , (list of supported <rsrq>s) | + +### Description + +Set command enables or disables the indication for WLAN offloading based on the thresholds for cell measurement parameters. If reporting is enabled by <n>=1, the MT returns the following unsolicited result code from MT to TE whenever the cell measurement parameters meet the criteria for WLAN offloading based on configured thresholds: + ++CWLANOLCMI: <rscp>,<ecno>,<rsrp>,<rsrq> + +If a setting is not supported by the MT, +CME ERROR: <err> is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current status of result code presentation and the measurements from the current primary serving cell at the MT. + +Test command returns the values supported by MT as compound values. + +### Defined values + +<n>: integer type + +0 disable WLAN offload cell measurement unsolicited result code + +1 enable WLAN offload cell measurement unsolicited result code +CWLANOLCMI + +<rscp>: integer type; indicates the received signal code power. Refer parameter <rscp> in clause 8.69. + +<ecno>: integer type; indicates the ratio of the received energy per PN chip to the total received power spectral density. Refer parameter <ecno> in clause 8.69. + +<rsrp>: integer type; indicates the reference signal received power. Refer parameter <rsrp> in clause 8.69. + +<rsrq>: integer type; indicates the reference signal received quality. Refer parameter <rsrq> in clause 8.69. + +### Implementation + +Optional. + +## 10.1.41 APN back-off timer status reporting +CABTSR + +**Table 10.1.41-1: +CABTSR parameter command syntax** + +| Command | Possible response(s) | +|---------------|-----------------------------------| +| +CABTSR=[<n>] | +CME ERROR: <err> | +| +CABTSR? | +CABTSR: <n> | +| +CABTSR=? | +CABTSR: (list of supported <n>s) | + +## Description + +Set command controls the presentation of unsolicited result code + ++CABTSRI: <apn>, <event\_type>[, <residual\_backoff\_time>, <NSLPI>[, <procedure>]] +reporting the APN back-off timer parameter values from MT to TE if the back-off timer is started, stopped, deactivated or expires. Refer clause 9.2 for possible <err> values. + +Read command returns the current APN back-off timer unsolicited result code settings in the MT. + +Test command returns values supported as a compound value. + +## Defined values + +<n>: integer type. + +- 0 Disable presentation of the unsolicited result code +CABTSRI. +- 1 Enable presentation of the unsolicited result code +CABTSRI. + +<apn>: string type. A logical name that was used to select the GGSN or the external packet data network. + +<event\_type>: integer type. Indicates the event happened to the back-off timer. + +- 0 The back-off timer is started. +- 1 The back-off timer is stopped. +- 2 The back-off timer is expired. +- 3 The back-off timer is deactivated. + +<residual\_backoff\_time>: integer type. Indicates the remaining back-off time associated with the <apn> in seconds. When the back-off timer is deactivated, the parameter <residual\_backoff\_time> is omitted. + +<NSLPI>: integer type. Indicates the NAS signalling priority requested for this PDN connection. + +- 0 Indicates that this PDN connection was activated with the value for NAS signalling low priority indicator set to "MS is configured for NAS signalling low priority". +- 1 Indicates that this PDN connection was activated with the value for NAS signalling low priority indicator set to "MS is not configured for NAS signalling low priority". + +<procedure>: integer type. Indicates the procedure(s) for which the back-off timer applies. When <procedure>=0 the information returned is associated with timer T3396. For all other values of <procedure> the information returned is associated with the back-off timer as specified in 3GPP TS 24.008 [8], 3GPP TS 24.301 [83] or 3GPP TS 24.501 [161] for the various session management procedures or mobility management procedures. When the parameter <procedure> is omitted, the back-off timer is deactivated. + +- 0 All procedures. +- 1 Standalone PDN connectivity procedure as specified in 3GPP TS 24.301 [83], clause 6.5.1. +- 2 Bearer resource allocation procedure as specified in 3GPP TS 24.301 [83], clause 6.5.3. +- 3 Bearer modification procedure as specified in 3GPP TS 24.301 [83], clause 6.5.4. +- 4 PDP context activation procedure as specified in 3GPP TS 24.008 [8], clause 6.1.3.1. +- 5 Secondary PDP context activation procedure as specified in 3GPP TS 24.008 [8], clause 6.1.3.2. +- 6 PDP context modification procedure as specified in 3GPP TS 24.008 [8], clause 6.1.3.3. +- 7 PDU session establishment procedure (see 3GPP TS 24.501 [161], clause 6.4.1). + +- 8 PDU session modification procedure (see 3GPP TS 24.501 [161], clause 6.4.2). +- 9 EPS attach procedure piggybacked with PDN connectivity procedure as specified in 3GPP TS 24.301 [83], clause 5.5.1. + +NOTE: <procedure>=7 and <procedure>=8 apply to the DNN back-off timer as specified in N1 mode (see 3GPP TS 24.501 [161]). + +## Implementation + +Optional. + +## 10.1.42 APN back-off timer read dynamic parameters +CABTRDP + +**Table 10.1.42-1: +CABTRDP action command syntax** + +| Command | Possible response(s) | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CABTRDP[=<apn>] | [+CABTRDP: <apn>[, <residual_backoff_time>]<br>[, <NSLPI>[, <procedure>]]]<br><br>[<CR><LF>+CABTRDP :<apn>[, <residual_backoff_time>]<br>[, <NSLPI>[, <procedure>]]]<br><br>[...]]] | +| +CABTRDP=? | | + +## Description + +The execution command returns the relevant information in the MT for the APN back-off timer parameter values <residual\_backoff\_time>, <NSLPI> and <procedure> for an <apn> if the back-off timer is running. + +If the parameter <apn> is omitted, the relevant information for all APNs associated with running session management back-off timers is returned. + +## Defined values + +<apn>: string type. A logical name that was used to select the GGSN or the external packet data network. When <apn> indicates an empty string (""), the following parameters are associated with no APN as specified in 3GPP TS 24.301 [83]. + +<residual\_backoff\_time>: integer type. Indicates the remaining back-off time associated with the <apn> in seconds. When the parameter <residual\_backoff\_time> is omitted, the back-off timer is deactivated. + +<NSLPI>: integer type. Indicates the NAS signalling priority requested for this PDN connection. + +- 0 Indicates that this PDN connection was activated with the value for NAS signalling low priority indicator set to "MS is configured for NAS signalling low priority". +- 1 Indicates that this PDN connection was activated with the value for NAS signalling low priority indicator set to "MS is not configured for NAS signalling low priority". + +<procedure>: integer type. Indicates the procedure(s) for which the back-off timer applies. When <procedure>=0 the information returned is associated with timer T3396. For all other values of <procedure> the information returned is associated with the back-off timer as specified in 3GPP TS 24.008 [8], 3GPP TS 24.301 [83] or 3GPP TS 24.501 [161] for the various session management procedures or mobility management procedures. + +- 0 All procedures. +- 1 Standalone PDN connectivity procedure as specified in 3GPP TS 24.301 [83], clause 6.5.1. +- 2 Bearer resource allocation procedure as specified in 3GPP TS 24.301 [83], clause 6.5.3. + +- 3 Bearer modification procedure as specified in 3GPP TS 24.301 [83], clause 6.5.4. +- 4 PDP context activation procedure as specified in 3GPP TS 24.008 [8], clause 6.1.3.1. +- 5 Secondary PDP context activation procedure as specified in 3GPP TS 24.008 [8], clause 6.1.3.2. +- 6 PDP context modification procedure as specified in 3GPP TS 24.008 [8], clause 6.1.3.3. +- 7 PDU session establishment procedure (see 3GPP TS 24.501 [161], clause 6.4.1). +- 8 PDU session modification procedure (see 3GPP TS 24.501 [161], clause 6.4.2). +- 9 EPS attach procedure piggybacked with PDN connectivity procedure as specified in 3GPP TS 24.301 [83], clause 5.5.1. + +NOTE: <procedure>=7 and <procedure>=8 apply to the DNN back-off timer as specified in N1 mode (see 3GPP TS 24.501 [161]). + +### Implementation + +Optional. + +## 10.1.43 Sending of originating data via the control plane +CSODCP + +**Table 10.1.43-1: +CSODCP action command syntax** + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CSODCP=<cid>,<cpdata_length>,<cpdata>[,<RAI>[,<type_of_user_data>[,<sourcePort>[,<destinationPort>[,<ackRequest>]]]]]<br>] | +CME ERROR: <err> | +| +CSODCP=? | +CSODCP: (range of supported <cid>s) , (maximum number of octets of user data indicated by <cpdata_length>), (list of supported <RAI>s) , (list of supported <type_of_user_data>s), (list of supported <sourcePort>s), (list of supported <destinationPort>s), (list of supported <ackRequest>s) | + +### Description + +The set command is used by the TE to transmit data over control plane to network via MT. Context identifier <cid> is used to link the data to particular context. + +This command optionally indicates that the application on the MT expects that the exchange of data: + +- will be completed with this uplink data transfer; or +- will be completed with the next received downlink data. + +This command also optionally indicates whether or not the data to be transmitted is an exception data. + +If the UE is using Reliable Data Service to transmit data, then this command optionally also indicates the source port number used by the originator, the destination port number to be used by the receiver and whether the originator is soliciting an acknowledgement from the receiver as defined in 3GPP TS 24.250 [168]. + +This command causes transmission of an ESM DATA TRANSPORT message, as defined in 3GPP TS 24.301 [83]. + +Refer clause 9.2 for possible <err> values. + +Test command returns range of supported <cid>s, the maximum number of bytes of user data indicated by <cpdata\_length>, supported <RAI>s, supported <type\_of\_user\_data>s, supported <sourcePort>s, supported <destinationPort>s and supported <ackRequest>s as compound values. + +#### Defined values + +<cid>: integer type. A numeric parameter which specifies a particular PDP context or EPS bearer context definition. The <cid> parameter is local to the TE-MT interface and identifies the PDP or EPS bearer contexts which have been setup via AT command (see the +CGDCONT and +CGDSCONT commands). + +<cpdata\_length>: integer type. Indicates the number of octets of the <cpdata> information element. When there is no data to transmit, the value shall be set to zero. + +<cpdata>: string of octets. Contains the user data container contents (refer 3GPP TS 24.301 [83] clause 9.9.4.24). When there is no data to transmit, the <cpdata> shall be an empty string (""). This parameter shall not be subject to conventional character conversion as per +CSCS. The coding format of the user data container and the maximum length of <cpdata> are implementation specific. + +<RAI>: integer type. Indicates the value of the release assistance indication, refer 3GPP TS 24.301 [83] clause 9.9.4.25. + +- 0 No information available. +- 1 The MT expects that exchange of data will be completed with the transmission of the ESM DATA TRANSPORT message. +- 2 The MT expects that exchange of data will be completed with the receipt of an ESM DATA TRANSPORT message. + +<type\_of\_user\_data>: integer type. Indicates whether the user data that is transmitted is regular or exceptional. + +- 0 Regular data. +- 1 Exception data. + +<sourcePort>: integer type. Indicates the source port number on the originator entity (refer 3GPP TS 24.250 [168] clause 5.2.4). + +<destinationPort>: integer type. Indicates the destination port number on the receiver entity (refer 3GPP TS 24.250 [168] clause 5.2.5). + +<ackRequest>: integer type. Indicates whether the originator entity is soliciting an acknowledgement from the receiver entity (refer 3GPP TS 24.250 [168] clause 5.3.1). + +- 0 No acknowledgement is requested +- 1 Acknowledgement is requested. + +#### Implementation + +Optional. + +### 10.1.44 Reporting of terminating data via the control plane +CRTDCP + +**Table 10.1.44-1: +CRTDCP parameter command syntax** + +| Command | Possible response(s) | +|-----------------------|----------------------| +| +CRTDCP=[<reporting>] | +CME ERROR: <err> | +| +CRTDCP? | +CRTDCP: <reporting> | + +| | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CRTDCP=? | +CRTDCP: (list of supported <reporting>s), (range of supported <cid>s), (maximum number of octets of user data indicated by <cpdata_length>), (list of supported <sourcePort>s), (list of supported <destinationPort>s) | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +The set command is used to enable and disable reporting of data from the network to the MT that is transmitted via the control plane in downlink direction. If <reporting>=1, the MT returns the unsolicited result code +CRTDCP: <cid>, <cpdata\_length>, <cpdata> when data is received from the network. If <reporting>=2, the MT returns the unsolicited result code +CRTDCP: <cid>, <cpdata\_length>, <cpdata>, <sourcePort>, <destinationPort> when data is received from the network using the Reliable Data Service as defined in 3GPP TS 24.250 [168]. Refer clause 9.2 for possible <err> values. + +Read command returns the current settings. + +Test command returns supported values as compound values. + +## Defined values + +<reporting>: integer type, controlling reporting of mobile terminated control plane data events + +- 0 Disable reporting of MT control plane data. +- 1 Enable reporting of MT control plane data by the unsolicited result code ++CRTDCP: <cid>, <cpdata\_length>, <cpdata>. +- 2 Enable reporting of MT control plane data by the unsolicited result code ++CRTDCP: <cid>, <cpdata\_length>, <cpdata>, <sourcePort>, <destinationPort>. + +<cid>: integer type. A numeric parameter which specifies a particular PDP context or EPS bearer context definition. The <cid> parameter is local to the TE-MT interface and identifies the PDP or EPS bearer contexts which have been setup via AT command (see the +CGDCONT and +CGDSCONT commands). + +<cpdata\_length>: integer type. Indicates the number of octets of the <cpdata> information element. When there is no data to transmit, the value shall be set to zero. + +<cpdata>: string of octets. Contains the user data container contents (refer 3GPP TS 24.301 [83] clause 9.9.4.24). When there is no data to transmit, the <cpdata> shall be an empty string (""). This parameter shall not be subject to conventional character conversion as per +CSCS. The coding format of the user data container and the maximum length of <cpdata> are implementation specific. + +<sourcePort>: integer type. Indicates the source port number on the originator entity (refer 3GPP TS 24.250 [168] clause 5.2.4). + +<destinationPort>: integer type. Indicates the destination port number on the receiver entity (refer 3GPP TS 24.250 [168] clause 5.2.5). + +## Implementation + +Optional. + +## 10.1.45 APN rate control +CGAPNRC + +**Table 10.1.45-1: +CGAPNRC action command syntax** + +| Command | Possible Response(s) | +|------------------|-------------------------------------------------------------------------------------| +| +CGAPNRC[=<cid>] | [+CGAPNRC: <cid>[, <Additional_exception_reports>[, <Uplink_time_unit>[, <Maximum_u | + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | <pre> plink_rate>]]] [<CR><LF>+CGAPNRC: <cid>[, <Additional_exception_reports>[, <Uplink_time_unit>[, <Maximum_uplink_rate>]]] [...]]] </pre> | +| +CGAPNRC=? | +CGAPNRC: (list of <cid>s associated with active contexts) | + +### Description + +This execution command returns the APN rate control parameters (see 3GPP TS 24.008 [8]) associated to the provided context identifier <cid>. + +If the parameter <cid> is omitted, the APN rate control parameters for all active PDP contexts are returned. + +The test command returns a list of <cid>s associated with secondary and non secondary active PDP contexts. + +### Defined values + +<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<Additional\_exception\_reports>: integer type; indicates whether or not additional exception reports are allowed to be sent when the maximum uplink rate is reached. This refers to bit 4 of octet 1 of the APN rate control parameters IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.3.2. + +- 0 Additional\_exception\_reports at maximum rate reached are not allowed to be sent. +- 1 Additional\_exception\_reports at maximum rate reached are allowed to be sent. + +<Uplink\_time\_unit>: integer type; specifies the time unit to be used for the maximum uplink rate. This refers to bits 1 to 3 of octet 1 of the APN rate control parameters IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.3.2. + +- 0 unrestricted +- 1 minute +- 2 hour +- 3 day +- 4 week + +<Maximum\_uplink\_rate>: integer type; specifies the maximum number of messages the UE is restricted to send per uplink time unit. This refers to octet 2 to 4 of the APN rate control parameters IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.3.2. + +### Implementation + +Optional. + +## 10.1.46 PS data off status +CPSDO + +**Table 10.1.46-1: +CPSDO parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------|----------------------| +| +CPSDO=[<PS_Data_Off_Status >] | +CME ERROR: <err> | + +| | | +|----------|---------------------------------------------------| +| +CPSDO? | +CPSDO: <PS_Data_Off_Status> | +| +CPSDO=? | +CPSDO: (list of supported <PS_Data_Off_Status>s) | + +## Description + +The set command enables the UE to specify the PS data off UE status to the network during UE-requested PDP context activation and UE-requested PDP context modification procedure (see 3GPP TS 24.008 [8], clause 4.7.1.10 and clauses 6.1.3.1 and 6.1.3.3), during attach, UE-requested PDN connectivity, and UE-requested bearer modification procedure (see 3GPP TS 24.301 [83], clause 6.3.10 and clauses 5.5.1, 6.5.1, and 6.5.4), and during UE-requested PDU session establishment, and UE-requested PDU session modification procedure (see 3GPP TS 24.501 [161], clause 6.2.10 and clauses 6.4.1 and 6.4.2). The PS data off UE status may be activated or deactivated. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current settings for PS data off UE status. + +The test command returns values supported as a compound value. + +## Defined values + +<PS\_Data\_Off\_Status>: integer type; indicates the PS data off UE status, see 3GPP TS 24.008 [8], clause 4.7.1.10, 3GPP TS 24.301 [83], clause 6.3.10, and 3GPP TS 24.501 [161], clause 6.2.10. + +- 0 indicates to the network that PS data off UE status is deactivated +- 1 indicates to the network that PS data off UE status is activated + +## Implementation + +Optional. + +## 10.1.47 5GS network registration status +C5GREG + +**Table 10.1.47-1: +C5GREG parameter command syntax** + +| Command | Possible response(s) | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GREG=<n> | +CME ERROR: <err> | +| +C5GREG? | <b>when <n>=0, 1, 2, 3, 4 or 5 and command successful:</b><br>+C5GREG: <n>,<stat>[,<tac>],[<ci>],[<AcT>],[<Allowed_NSSAI_length>],[<Allowed_NSSAI>]<br>[,<cause_type>,<reject_cause>]<br>[,<cag_stat>][,<caginfo>] | +| +C5GREG=? | +C5GREG: (list of supported <n>s) | + +## Description + +The set command controls the presentation of an unsolicited result code +C5GREG: <stat> when <n>=1 and there is a change in the MT's network registration status in 5GS, or unsolicited result code +C5GREG: <stat>[,<tac>],[<ci>],[<AcT>],[<Allowed\_NSSAI\_length>],[<Allowed\_NSSAI>] when <n>=2 and there is a change of the network cell in 5GS or the network provided an Allowed NSSAI for 3GPP access. The parameters <AcT>, <tac>, <ci>, <Allowed\_NSSAI\_length> and <Allowed\_NSSAI> are provided only if available. The value <n>=3 further extends the unsolicited result code with [,<cause\_type>,<reject\_cause>], when available, when the value of <stat> changes. The value <n>=4 extends the unsolicited result code with [,<cag\_stat>] when the value of <cag\_stat> changes. The value <n>=5 extends the unsolicited result code with [,<caginfo>] when UE camps on a CAG cell. <caginfo> is displayed only when <cag\_stat> is 1. + +Refer clause 9.2 for possible <err> values. + +NOTE 1: If the 5G MT in GERAN/UTRAN/E-UTRAN also supports one or more of the circuit mode services, GPRS services or EPS services, the +CREG command and +CREG: result codes, the +CGREG command and +CGREG: result codes and the +CEREG command and +CEREG: result codes apply to the registration status and location information for those services. + +The read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. Location information elements <tac>, <ci> and <AcT>, and parameters <Allowed\_NSSAI\_length>, <Allowed\_NSSAI>, if available, are returned only when <n>=2 and MT is registered in the network. The parameters [, <cause\_type>, <reject\_cause>], if available, are returned when <n>=3. + +Test command returns values supported as a compound value. The parameter [, <cag\_stat>], if available, is returned when <n>=4. The parameter [, <caginfo>], if available, is returned when <n>=5. + +### Defined values + +<n>: integer type + +- 0 disable network registration unsolicited result code +- 1 enable network registration unsolicited result code +C5GREG: <stat> +- 2 enable network registration and location information unsolicited result code +C5GREG: <stat>[, [<tac>], [<ci>], [<AcT>], [<Allowed\_NSSAI\_length>], [<Allowed\_NSSAI>]] +- 3 enable network registration, location information and 5GMM cause value information unsolicited result code +C5GREG: <stat>[, [<tac>], [<ci>], [<AcT>], [<Allowed\_NSSAI\_length>], [<Allowed\_NSSAI>] [, <cause\_type>, <reject\_cause>]] +- 4 enable network registration, location information, cause value information, CAG cell status information unsolicited result code +C5GREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<Allowed\_NSSAI\_length>], [<Allowed\_NSSAI>] [, <cause\_type>, <reject\_cause>]] [, <cag\_stat>] +- 5 enable network registration, location information, cause value information, CAG cell status information and CAG cell information unsolicited result code +C5GREG: <stat>[, [<lac>], [<ci>], [<AcT>], [<Allowed\_NSSAI\_length>], [<Allowed\_NSSAI>] [, <cause\_type>, <reject\_cause>]] [, <cag\_stat>] [, <caginfo>] + +<stat>: integer type; indicates the NR registration status. + +- 0 not registered, MT is not currently searching an operator to register to +- 1 registered, home network +- 2 not registered, but MT is currently trying to attach or searching an operator to register to +- 3 registration denied +- 4 unknown (e.g. out of NR coverage) +- 5 registered, roaming +- 6 registered for "SMS only", home network (not applicable) +- 7 registered for "SMS only", roaming (not applicable) +- 8 registered for emergency services only (See NOTE 2) +- 9 registered for "CSFB not preferred", home network (not applicable) +- 10 registered for "CSFB not preferred", roaming (not applicable) + +11 attached for access to RLOS (See NOTE 2a) (not applicable) + +12 registered for "disaster roaming services" + +13 disaster condition applied to the current PLMN + +NOTE 2: 3GPP TS 24.501 [161] specifies the condition when the MT is considered as registered for emergency services. + +NOTE 2a: 3GPP TS 24.301 [83] specifies the condition when the MT is considered as attached for access to RLOS. + +<tac>: string type; three byte tracking area code in hexadecimal format (e.g. "0000C3" equals 195 in decimal). + +<ci>: string type; five byte NR cell ID in hexadecimal format. + +<Allowed\_NSSAI\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <Allowed\_NSSAI> parameter. + +<Allowed\_NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of allowed S-NSSAIs for 3GPP access received from the network. The <Allowed\_NSSAI> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<AcT>: integer type; indicates the access technology of the serving cell. + +0 GSM (not applicable) + +1 GSM Compact (not applicable) + +2 UTRAN (not applicable) + +3 GSM w/EGPRS (see NOTE 3) (not applicable) + +4 UTRAN w/HSDPA (see NOTE 4) (not applicable) + +5 UTRAN w/HSUPA (see NOTE 4) (not applicable) + +6 UTRAN w/HSDPA and HSUPA (see NOTE 4) (not applicable) + +7 E-UTRAN (not applicable) + +8 EC-GSM-IoT (A/Gb mode) (see NOTE 5) (not applicable) + +9 E-UTRAN (NB-S1 mode) (see NOTE 6) (not applicable) + +10 E-UTRA connected to a 5GCN (see NOTE 7) + +11 NR connected to a 5GCN (see NOTE 7) + +12 NG-RAN (not applicable) + +13 E-UTRA-NR dual connectivity (see NOTE 8) (not applicable) + +14 satellite E-UTRAN (NB-S1 mode) (not applicable) + +15 satellite E-UTRAN (WB-S1 mode) (not applicable) + +16 satellite NG-RAN + +NOTE 3: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS. + +NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA. + +NOTE 5: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT. + +NOTE 6: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode). + +NOTE 7: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5GCN. + +NOTE 8: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core. + +<cause\_type>: integer type; indicates the type of <reject\_cause>. + +0 Indicates that <reject\_cause> contains an 5GMM cause value, see 3GPP TS 24.501 [161] Annex A. + +1 Indicates that <reject\_cause> contains a manufacturer-specific cause. + +<reject\_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by <cause\_type>. + +<cag\_stat>: integer type; indicates the camping status on a CAG cell + +0 Indicates UE is not camped on CAG cell. + +1 Indicates UE is currently camped on CAG cell. + +<CAGinfo>: string type; + +CAGinfo consists of HRNN, CAG ID and Associated PLMN MCC MNC each delimited by a comma and in this particular order only. If HRNN is unavailable, it shall be an empty field. + +The display format is based on <format> value in +CCAGS command. In the alphanumeric format HRNN, CAG ID and Associated PLMN MCC MNC would be displayed while in numeric format only CAG ID and Associated PLMN MCC MNC would be displayed. See 3GPP TS 23.003 [7] for details of HRNN and CAG ID representation. + +## Implementation + +Optional. This command is only applicable to UEs supporting 5GS. + +## 10.1.48 Bandwidth preference indication +CBPI + +**Table 10.1.48-1: +CBPI action command syntax** + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| +CBPI[=<uplink_bandwidth_preference>[, <downlink_bandwidth_preference>]] | +CME ERROR: <err> | +| +CBPI=? | +CBPI: (list of supported <uplink_bandwidth_preference>s), (list of supported <downlink_bandwidth_preference>s) | + +## Description + +This command indicates to the MT the frequency bandwidth preference for uplink or for downlink. + +For BL UEs or for UEs operating in coverage enhancement mode. If further conditions defined in 3GPP TS 36.331 [86] are met, this may cause transmission to the network of a UEAssistanceInformation message with *bw-Preference* set to <uplink\_bandwidth\_preference> and <downlink\_bandwidth\_preference>. + +Test command returns the values supported as compound values. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<uplink\_bandwidth\_preference>: integer type; indicates the TE's preference on configuration on maximum Physical Uplink Shared Channel bandwidth. + +- 0 no preference indicated by the TE +- 1 CE mode usage in 1.4MHz +- 2 CE mode usage in 5MHz + +<downlink\_bandwidth\_preference>: integer type; indicates the TE's preference on configuration on maximum Physical Downlink Shared Channel bandwidth. + +- 0 no preference indicated by the TE +- 1 CE mode usage in 1.4MHz +- 2 CE mode usage in 5MHz +- 3 CE mode usage in 20MHz (normal coverage) + +#### Implementation + +Optional. + +### 10.1.49 Define 5GS quality of service +C5GQOS + +**Table 10.1.49-1: +C5GQOS parameter command syntax** + +| Command | Possible Response(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GQOS=<cid>[, <5QI>[, [<DL_GFBR>], [<UL_GFBR>] [, [<DL_MFBR>], [<UL_MFBR>]]]] | +CME ERROR: <err> | +| +C5GQOS? | [+C5GQOS: <cid>, <5QI>[, <DL_GFBR>, <UL_GFBR>[, <DL_MFBR>, <UL_MFBR>]]]<br><br>[<CR><LF>+C5GQOS: <cid>, <5QI>, [<DL_GFBR>, <UL_GFBR>[, <DL_MFBR>, <UL_MFBR>]]]<br><br>[...]] | +| +C5GQOS=? | +C5GQOS: (range of supported <cid>s) , (list of supported <5QI>s) , (list of supported <DL_GFBR>s) , (list of supported <UL_GFBR>s) , (list of supported <DL_MFBR>s) , (list of supported <UL_MFBR>s) | +| NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined. | | + +#### Description + +The set command allows the TE to specify the 5GS Quality of Service parameters <cid>, <5QI>, [<DL\_GFBR> and <UL\_GFBR>] and [<DL\_MFBR> and <UL\_MFBR>] for a QoS flow (see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]). Refer clause 9.2 for possible <err> values. + +A special form of the set command, +C5GQOS= <cid> causes the values for context number <cid> to become undefined. + +The read command returns the current settings for each defined QoS. + +The test command returns the ranges of the supported parameters as compound values. + +#### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<5QI>: integer type; specifies a class of 5GS QoS (see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]). + +- 0 5QI is selected by network +- [1 – 4] value range for guaranteed bit rate QoS flows +- [71 – 76] value range for guaranteed bit rate QoS flows +- [5 – 10] value range for non-guaranteed bit rate QoS flows +- 79, 80 values for non-guaranteed bit rate QoS flows +- [87 – 90] value range for Advanced Interactive Services bit rate QoS flows +- [82 – 86] value range for delay critical guaranteed bit rate QoS flows +- [128 – 254] value range for Operator-specific 5QIs + +The 5QI values 65, 66, 67, 69 and 70 are not allowed to be requested by the UE. If the TE requests a 5QI value 65, 66, 67, 69 or 70, the MT responds with result code +CME ERROR: 181 (unsupported 5QI value). + +The 5QI value of 10 can be requested by the UE only over NR satellite access. If the TE requests a 5QI value 10 over another access, the MT responds with result code +CME ERROR: 181 (unsupported 5QI value). + +<DL\_GFBR>: integer type; indicates DL GFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). For a GBR 5QI, this parameter can be omitted to indicate subscribed DL GFBR. + +<UL\_GFBR>: integer type; indicates UL GFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). For a GBR 5QI, this parameter can be omitted to indicate subscribed UL GFBR. + +<DL\_MFBR>: integer type; indicates DL MFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). For a GBR 5QI, this parameter can be omitted to indicate subscribed DL MFBR. + +<UL\_MFBR>: integer type; indicates UL MFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). For a GBR 5QI, this parameter can be omitted to indicate subscribed UL MFBR. + +#### Implementation + +Optional. + +### 10.1.50 5GS quality of service read dynamic parameters +C5GQOSRDP + +**Table 10.1.50-1: +C5GQOSRDP action command syntax** + +| Command | Possible Response(s) | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GQOSRDP[=<cid>] | <p>[+C5GQOSRDP: <cid>, <5QI>[, <DL_GFBR>, <UL_GFBR>[, <DL_MFBR>, <UL_MFBR>[, <DL_SAMBR>, <UL_SAMBR>[, <Averaging_window>]]]]]</p> <p>[<CR><LF>+C5GQOSRDP: <cid>, <5QI>[, <DL_GFBR>, <UL_GFBR>[, <DL_MFBR>, <UL_MFBR>[, <DL_SAMBR>, <UL_SAMBR>[, <Averaging_window>]]]]]</p> | + +| Command | Possible Response(s) | +|--------------|--------------------------------------------------------| +| | [...] | +| +C5GQOSRDP=? | +C5GQOSRDP: (list of <cid>s associated with QoS flows) | + +## Description + +The execution command returns the Quality of Service parameters <5QI>, [<DL\_GFBR> and <UL\_GFBR>], [<DL\_MFBR> and <UL\_MFBR>], [<DL\_SAMBR> and <UL\_SAMBR>] and <Averaging\_window> of the QoS flow associated to the provided context identifier <cid>. + +If the parameter <cid> is omitted, the Quality of Service parameters for all QoS flows are returned. + +The test command returns a list of <cid>s associated with all QoS flows. + +Parameters of both network and MT/TA initiated QoS flows will be returned. + +## Defined values + +<cid>: integer type; specifies a particular QoS flow definition, Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<5QI>: integer type; specifies a class of 5GS QoS (see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]). + +0 5QI is selected by network + +[1 – 4] value range for guaranteed bit rate QoS flows + +65, 66, 67 values for guaranteed bit rate QoS flows + +[71 – 76] value range for guaranteed bit rate QoS flows + +[5 – 10] value range for non-guaranteed bit rate QoS flows + +69, 70, 79, 80 values for non-guaranteed bit rate QoS flows + +[82 – 86] value range for delay critical guaranteed bit rate QoS flows + +[87 – 90] value range for Advanced Interactive Services bit rate QoS flows + +[128 – 254] value range for Operator-specific 5QIs + +<DL\_GFBR>: integer type; indicates DL GFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). + +<UL\_GFBR>: integer type; indicates UL GFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). + +<DL\_MFBR>: integer type; indicates DL MFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). + +<UL\_MFBR>: integer type; indicates UL MFBR in case of GBR 5QI. The value is in kbit/s. This parameter is omitted for a non-GBR 5QI (see 3GPP TS 24.501 [161]). + +<UL\_SAMBR>: integer type; indicates the UL session AMBR (see 3GPP TS 24.501 [161]). The value is in kbit/s. + +<DL\_SAMBR>: integer type; indicates the DL session AMBR (see 3GPP TS 24.501 [161]). The value is in kbit/s. + +<Averaging\_window>: integer type; indicates the averaging window (see 3GPP TS 24.501 [161]). The value is in milliseconds. + +## Implementation + +Optional. + +## 10.1.51 Receive UE policy +CRUEPOLICY + +**Table 10.1.51-1: +CRUEPOLICY parameter command syntax** + +| Command | Possible response(s) | +|---------------------------|-------------------------------------------------------------------------------------------------------------| +| +CRUEPOLICY=[<reporting>] | | +| +CRUEPOLICY? | +CRUEPOLICY: <reporting>[, <UE_policy_section_management_list_length>, <UE_policy_section_management_list>] | +| +CRUEPOLICY=? | +CRUEPOLICY: (list of supported <reporting>s) | + +### Description + +The set command controls the presentation of policy information to the TE by an unsolicited result code +CRUEPOLICYU: <UE\_policy\_section\_management\_list\_length>, <UE\_policy\_section\_management\_list> when policy information is received from the network. + +Read command returns <reporting> which indicates whether reporting of policy information is enabled or disabled. When reporting is enabled, the parameters <UE\_policy\_section\_management\_list\_length> and <UE\_policy\_section\_management\_list> indicates the most recently received policy information at the MT. When reporting is disabled, no policy information is provided. + +Test command returns values supported as a compound value. + +### Defined values + +<reporting>: integer type. Enables and disables reporting of policy information received from the network. + +- 0 Disable reporting +- 1 Enable reporting + +<UE\_policy\_section\_management\_list\_length>: integer type; indicates the number of octets of the <UE\_policy\_section\_management\_list> information element. + +<UE\_policy\_section\_management\_list>: string type; coded as the value part of the UE policy section management list information element in 3GPP TS 24.501 [161] clause D.6.2, table D.6.2.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. + +## 10.1.52 Send UE policy +CSUEPOLICY + +**Table 10.1.52-1: +CSUEPOLICY action command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------------------------------------------------------|----------------------| +| +CSUEPOLICY=<message_type>[, <UE_policy_information_length>, <UE_policy_information>[, <UE_policy_classmark>]] | +CME ERROR: <err> | +| +CSUEPOLICY=? | | + +### Description + +Execution command allows the TE to send the UE policy section management result or the UPSI list and UE policy classmark to the MT. + +The UE policy information information element contains the UE policy section management result or the UPSI list as specified in 3GPP TS 24.501 [161] clause D.6.3 and clause D.6.4. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<message\_type>: integer type. Indicates which type of message the MT is requested to send. + +- 0 MANAGE UE POLICY COMPLETE +- 1 MANAGE UE POLICY COMMAND REJECT +- 2 UE STATE INDICATION +- 3 UE POLICY PROVISIONING REQUEST + +<UE\_policy\_information\_length>: integer type; only present if <message\_type>=1 or <message\_type>=2. It indicates the number of octets of the <UE\_policy\_information> information element. + +<UE\_policy\_information>: string type; only present if <message\_type>=1, <message\_type>=2 or <message\_type>=3. + +If <message\_type>=1, it is coded as the value part of the UE policy section management result information element in 3GPP TS 24.501 [161] clause D.6.3, table D.6.3.1. + +If <message\_type>=2, it is coded as the value part of the UPSI list information element in 3GPP TS 24.501 [161] clause D.6.4, table D.6.4.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If <message\_type>=3, it is coded as the value part of the Requested UE policies information element in 3GPP TS 24.587 [175] clause 8.3.2, table 8.3.2.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<UE\_policy\_classmark>: string type; one byte in an 8 bit format; only present if <message\_type>=2. It is coded as octet 3 of the UE policy classmark information element in 3GPP TS 24.501 [161] clause D.6.5, table D.6.5.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +### 10.1.53 5GS access selection preference for MO SMS +C5GSMS + +**Table 10.1.53-1: +C5GSMS parameter command syntax** + +| Command | Possible Response(s) | +|-------------------------|-------------------------------------------------------| +| +C5GSMS=[<access_pref>] | | +| +C5GSMS? | +C5GSMS: <access_pref> | +| +C5GSMS=? | +C5GSMS: (list of currently supported <access_pref>s) | + +#### Description + +The set command is used to specify the access preference that the MT will use to send MO SMS over NAS messages in 5GS. + +The read command returns the currently selected access preference. + +The test command returns the supported access preferences as a compound value. + +#### Defined values + +<access\_pref>: integer type; indicates the access preference to use to send MO SMS over NAS messages. + +- 0 3GPP access preferred, non-3GPP access is used if 3GPP access is not available + +- 1 non-3GPP access preferred, 3GPP access is used if non-3GPP access is not available + +### Implementation + +Optional. + +## 10.1.54 Mobile initiated connection only mode +CMICO + +**Table 10.1.54-1: +CMICO parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMICO=[<n>[, <Requested_MICO_Mode>[, <Requested_Active_Time>>[, <Requested_SPRT>]]]] | +CME ERROR: <err><br><b>when <n>=2 and command successful</b><br>+CMICO: <Current_MICO_Mode>[, <RAAI>, <SPRT>[, <Allocated_Active_Time>]] | +| +CMICO? | +CMICO: <n>, <Requested_MICO_Mode>[, <Current_MICO_Mode>[, <RAAI>, [<SPRT>, <Requested_SPRT>[, <Requested_Active_Time>, <Allocated_Active_Time>]]]] | +| +CMICO=? | +CMICO: (list of supported <n>s) , (list of supported <Requested_MICO_Mode>s) , (list of supported <Requested_SPRT>s) | + +### Description + +The set command controls the presentation of unsolicited result code + ++CMICO: <Current\_MICO\_Mode>[, <RAAI>, <SPRT>[, <Allocated\_Active\_Time>]] when <n>=1 and there is a change in the current MICO mode. The parameters <RAAI> and <SPRT> and optionally <Allocated\_Active\_Time>, are returned when <Current\_MICO\_Mode>=1. When <n>=2, a special form of the set command enables the UE to request the use of MICO mode from the network or re-negotiate the use of MICO mode from the network and optionally request an active timer value along with the indication of support for strictly periodic registration timer (SPRT), during the registration procedure (see 3GPP TS 24.501 [161], clause 5.3.6 and clause 5.5.1). When MICO mode is requested with <n>=2, the UE will attempt to trigger the mobility registration immediately. When MICO mode is requested with <n>=3, the UE will request MICO mode during initial registration and the negotiated values from the network will be displayed through the unsolicited response when received. + +Refer clause 9.2 for possible <err> values. + +The command should be abortable when <n>=2, when the use of MICO mode is requested or re-negotiated from the network. + +The read command returns the current settings of <n>, <Requested\_MICO\_Mode> and <Requested\_Active\_Time>. The command also returns the current values of <Current\_MICO\_Mode>, <RAAI>, <SPRT>, <Requested\_Active\_Time>, <Requested\_SPRT> and <Allocated\_Active\_Time> if available (see 3GPP TS 24.501 [161] clause 9.11.3.31). + +The test command returns values of supported <n>s, <Requested\_MICO\_Mode>s and <Requested\_SPRT>s as compound values. + +### Defined values + +<n>: integer type + +- 0 disable unsolicited result code ++CMICO: <Current\_MICO\_Mode>[, <RAAI>, <SPRT>[, <Allocated\_Active\_Time>]] +- 1 enable unsolicited result code ++CMICO: <Current\_MICO\_Mode>[, <RAAI>, <SPRT>[, <Allocated\_Active\_Time>]] + +- 2 MICO mode is requested or re-negotiated from the network. There will be no change in the current setting of <n>, enabling or disabling of unsolicited result code ++CMICO: <Current\_MICO\_Mode>[, <RAAI>, <SPRT>[, <Allocated\_Active\_Time>]] + +- 3 MICO mode is requested during initial registration + +<Requested\_MICO\_Mode>: integer type; indicates the requested MICO mode, see 3GPP TS 24.501 [161], clause 5.5.1. + +- 0 triggers the UE to request stopping the use of MICO mode +- 1 triggers the UE to request the use of MICO mode + +<Requested\_Active\_Time>: string type; one byte in an 8 bit format. Requested Active Time value (T3324) to be allocated to the UE. The <Requested\_Active\_Time> value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 24.501 [161] clauses 5.3.6 and 5.5.1. The default value, if available, is manufacturer specific.<Current\_MICO\_Mode>: integer type; indicates the current MICO mode, see 3GPP TS 24.501 [161], clause 5.3.6. + +- 0 indicates that the use of MICO mode is not allowed by the network +- 1 indicates that the use of MICO mode is allowed by the network + +<RAAI>: integer type; only present when <Current\_MICO\_Mode>=1. Indicates the registration area allocation indication, see 3GPP TS 24.501 [161] clause 9.11.3.31. + +- 0 indicates to the UE that all PLMN registration areas are not allocated +- 1 indicates to the UE that all PLMN registration areas are allocated + +<Requested\_SPRT>: integer type; Indicates if strictly periodic registration timer is supported by the UE or not, see 3GPP TS 24.501 [161] clause 9.11.3.31. + +- 0 indicates that the strictly periodic registration timer is not supported by the UE +- 1 indicates that the strictly periodic registration timer is supported by the UE + +<SPRT>: integer type; only present when <Current\_MICO\_Mode>=1. Indicates the use of the strictly periodic registration timer, see 3GPP TS 24.501 [161] clause 9.11.3.31. If the UE indicated support for strictly periodic registration timer in the MICO indication IE to the network, the network may include a "strictly periodic registration timer supported" indication in the MICO indication IE to the UE. + +- 0 indicates to the UE that the strictly periodic registration timer is not being used +- 1 indicates to the UE that the strictly periodic registration timer is being used + +<Allocated\_Active\_Time>: string type; one byte in an 8 bit format. Only present when <Current\_MICO\_Mode>=1. Indicates the Active Time value (T3324) assigned by the network. The <Allocated\_Active\_Time> value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 24.501 [161] clauses 5.3.6 and 5.5.1. + +## Implementation + +Optional. This command is only applicable to UEs supporting 5GS. + +## 10.1.55 S-NSSAI based back-off timer status reporting +CSBTSR + +**Table 10.1.55-1: +CSBTSR parameter command syntax** + +| Command | Possible response(s) | +|-------------|-----------------------------------| +| +CSBTSR=<n> | +CME ERROR: <err> | +| +CSBTSR? | +CSBTSR: <n> | +| +CSBTSR=? | +CSBTSR: (list of supported <n>s) | + +### Description + +Set command controls the presentation of unsolicited result code +CSBTSRI: <S-NSSAI>, <event\_type>[, <S-NSSAI\_backoff\_time>, <5GSM\_congestion\_re-attempt\_abo\_indicator>, <5GSM\_congestion\_re-attempt\_catbo\_indicator>[, <procedure>]] reporting the S-NSSAI based back-off timer parameter values from MT to TE if the back-off timer is started, stopped, deactivated or expires. Refer clause 9.2 for possible <err> values. + +Read command returns the current S-NSSAI based back-off timer unsolicited result code settings in the MT. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type. + +- 0 Disable presentation of the unsolicited result code +CSBTSRI. +- 1 Enable presentation of the unsolicited result code +CSBTSRI. + +<S-NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the back-off timer for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<event\_type>: integer type. Indicates the event happened to the back-off timer. + +- 0 The back-off timer is started. +- 1 The back-off timer is stopped. +- 2 The back-off timer is expired. +- 3 The back-off timer is deactivated. + +<S-NSSAI\_backoff\_time>: integer type; indicates the remaining back-off time associated with the <S-NSSAI> in seconds. When the back-off timer is deactivated, the parameter <S-NSSAI\_backoff\_time> is omitted. When the back-off timer is stopped or expired, 0 is indicated. + +<5GSM\_congestion\_re-attempt\_abo\_indicator>: integer type. Indicates whether the back-off timer is applied in the registered PLMN or all PLMNs. + +- 0 The back-off timer is applied in the registered PLMN. +- 1 The back-off timer is applied in all PLMNs. + +<5GSM\_congestion\_re-attempt\_catbo\_indicator>: integer type. Indicates whether the back-off timer is applied in the current access type or both 3GPP access type and non-3GPP access type. + +- 0 The back-off timer is applied in both 3GPP access type and non-3GPP access type. +- 1 The back-off timer is applied in the current access type. + +<procedure>: integer type. Indicates the procedure(s) for which the back-off timer applies. When <procedure>=0 the information returned is associated with timer T3585. When the parameter <procedure> is omitted, the back-off timer is deactivated. + +0 All procedures. + +### Implementation + +Optional. + +## 10.1.56 S-NSSAI based back-off timer read dynamic parameters +CSBTRDP + +**Table 10.1.56-1: +CSBTRDP action command syntax** + +| Command | Possible response(s) | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CSBTRDP[=<S-NSSAI>] | [+CSBTRDP: <S-NSSAI>[, <S-NSSAI_backoff_time>]<br>[, <5GSM_congestion_re-attempt_abo_indicator>, <5GSM_congestion_re-attempt_catbo_indicator>] [, <procedure>]<br><br>[<CR><LF>+CSBTRDP: <S-NSSAI>[, <S-NSSAI_backoff_time>]<br>[, <5GSM_congestion_re-attempt_abo_indicator>, <5GSM_congestion_re-attempt_catbo_indicator>] [, <procedure>]<br><br>[...]]] | +| +CSBTRDP=? | | + +### Description + +The execution command returns the relevant information in the MT for the S-NSSAI based back-off timer parameter value <S-NSSAI\_backoff\_time>, <5GSM\_congestion\_re-attempt\_abo\_indicator>, <5GSM\_congestion\_re-attempt\_catbo\_indicator> and <procedure> for an <S-NSSAI> if the back-off timer is running. + +If the parameter <S-NSSAI> in the execution command is omitted, the relevant information for all S-NSSAIs associated with running back-off timers are returned. + +### Defined values + +<S-NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the back-off timer for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. When <S-NSSAI> indicates an empty string (""), the following parameter is associated with no S-NSSAI as specified in 3GPP TS 24.501 [161]. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<S-NSSAI\_backoff\_time>: integer type; indicates the remaining back-off time associated with the <S-NSSAI> in seconds. When the back-off timer is deactivated, the parameter <S-NSSAI\_backoff\_time> is omitted. + +<5GSM\_congestion\_re-attempt\_abo\_indicator>: integer type. Indicates whether the back-off timer is applied in the registered PLMN or all PLMNs. + +0 The back-off timer is applied in the registered PLMN. + +1 The back-off timer is applied in all PLMNs. + +<5GSM\_congestion\_re-attempt\_catbo\_indicator>: integer type. Indicates whether the back-off timer is applied in the current access type or both 3GPP access type and non-3GPP access type. + +- 0 The back-off timer is applied in both 3GPP access type and non-3GPP access type. +- 1 The back-off timer is applied in the current access type. + +<procedure>: integer type. Indicates the procedure(s) for which the back-off timer applies. When <procedure>=0 the information returned is associated with timer T3585. When the parameter <procedure> is omitted, the back-off timer is deactivated. + +- 0 All procedures. + +### Implementation + +Optional. + +## 10.1.57 S-NSSAI and DNN based back-off timer status reporting +CSDBTSR + +**Table 10.1.57-1: +CSDBTSR parameter command syntax** + +| Command | Possible response(s) | +|----------------|------------------------------------| +| +CSDBTSR=[<n>] | +CME ERROR: <err> | +| +CSDBTSR? | +CSDBTSR: <n> | +| +CSDBTSR=? | +CSDBTSR: (list of supported <n>s) | + +### Description + +Set command controls the presentation of unsolicited result code +CSDBTSRI: <S-NSSAI>, <DNN>, <event\_type>[, <S-NSSAI\_DNN\_backoff\_time>, <5GSM\_congestion\_re-attempt\_catbo\_indicator>, <5GSM\_congestion\_re-attempt\_abo\_indicator>[, <procedure>]] reporting the S-NSSAI and DNN based back-off timer parameter values from MT to TE if the back-off timer is started, stopped, deactivated or expires. Refer clause 9.2 for possible <err> values. + +Read command returns the current S-NSSAI and DNN based back-off timer unsolicited result code settings in the MT. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type. + +- 0 Disable presentation of the unsolicited result code +CSDBTSRI. +- 1 Enable presentation of the unsolicited result code +CSDBTSRI. + +<S-NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the back-off timer for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<DNN>: string type; indicates the DNN associated with the back-off timer for identifying a data network in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<event\_type>: integer type. Indicates the event happened to the back-off timer. + +- 0 The back-off timer is started. +- 1 The back-off timer is stopped. + +- 2 The back-off timer is expired. +- 3 The back-off timer is deactivated. + +<S-NSSAI\_DNN\_backoff\_time>: integer type; indicates the remaining back-off time associated with the <S-NSSAI> and <DNN> in seconds. When the back-off timer is deactivated, the parameter <S-NSSAI\_DNN\_backoff\_time> is omitted. + +<5GSM\_congestion\_re-attempt\_abo\_indicator>: integer type. Indicates whether the back-off timer is applied in the registered PLMN or all PLMNs. + +- 0 The back-off timer is applied in the registered PLMN. +- 1 The back-off timer is applied in all PLMNs. + +<5GSM\_congestion\_re-attempt\_catbo\_indicator>: integer type. Indicates whether the back-off timer is applied in the current access type or both 3GPP access type and non-3GPP access type. + +- 0 The back-off timer is applied in both 3GPP access type and non-3GPP access type. +- 1 The back-off timer is applied in the current access type. + +<procedure>: integer type. Indicates the procedure(s) for which the back-off timer applies. When <procedure>=0 the information returned is associated with timer T3584. For all other values of <procedure> the information returned is associated with the back-off timer as specified in 3GPP TS 24.501 [161] for the various session management procedures. When the parameter <procedure> is omitted, the back-off timer is deactivated. + +- 0 All procedures. +- 1 PDU session establishment procedure (see 3GPP TS 24.501 [161], clause 6.4.1) +- 2 PDU session modification procedure (see 3GPP TS 24.501 [161], clause 6.4.2). + +#### Implementation + +Optional. + +### 10.1.58 S-NSSAI and DNN based back-off timer read dynamic parameters +CSDBTRDP + +**Table 10.1.58-1: +CSDBTRDP action command syntax** + +| Command | Possible response(s) | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CSDBTRDP[=<S-NSSAI>,<DNN>] | <p>[+CSDBTRDP: <S-NSSAI>,<DNN>[, <S-NSSAI_DNN_backoff_time>][, <5GSM_congestion_re-attempt_abo_indicator>,<5GSM_congestion_re-attempt_catbo_indicator>[, <procedure>]]]</p> <p>[<CR><LF>+CSDBTRDP: <S-NSSAI>,<DNN>[, <S-NSSAI_DNN_backoff_time>][, <5GSM_congestion_re-attempt_abo_indicator>,<5GSM_congestion_re-attempt_catbo_indicator>[, <procedure>]]]</p> <p>[...]]]</p> | +| +CSDBTRDP=? | | + +#### Description + +The execution command returns the relevant information in the MT for the S-NSSAI and DNN based back-off timer parameter value <S-NSSAI\_DNN\_backoff\_time>, <5GSM\_congestion\_re- + +attempt\_abo\_indicator>, <5GSM\_congestion\_re-attempt\_catbo\_indicator> and <procedure> for the <S-NSSAI> and <DNN> combination if the back-off timer is running. + +If the parameter <S-NSSAI> in the execution command is omitted, the DNN specific information for all S-NSSAIs associated with running back-off timers are returned. + +If the parameter <DNN> in the execution command is omitted, the S-NSSAI specific information for all DNNs associated with running back-off timers are returned. + +If both the parameters <S-NSSAI> and <DNN> are omitted, the relevant information for all S-NSSAI and DNN combinations associated with running back-off timers are returned. + +#### Defined values + +<S-NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the back-off timer for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. When <S-NSSAI> indicates an empty string (""), the parameter <S-NSSAI\_DNN\_backoff\_time> in the response is associated with no S-NSSAI as specified in 3GPP TS 24.501 [161]. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<DNN>: string type; indicates the DNN associated with the back-off timer for identifying a data network in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. When <DNN> indicates an empty string (""), the parameter <S-NSSAI\_DNN\_backoff\_time> in the response is associated with no DNN as specified in 3GPP TS 24.501 [161]. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<S-NSSAI\_DNN\_backoff\_time>: integer type; indicates the remaining back-off time associated with the <S-NSSAI> and <DNN> combination in seconds. When the back-off timer is deactivated, the parameter <S-NSSAI\_DNN\_backoff\_time> is omitted. + +<5GSM\_congestion\_re-attempt\_abo\_indicator>: integer type. Indicates whether the back-off timer is applied in the registered PLMN or all PLMNs. + +- 0 The back-off timer is applied in the registered PLMN. +- 1 The back-off timer is applied in all PLMNs. + +<5GSM\_congestion\_re-attempt\_catbo\_indicator>: integer type. Indicates whether the back-off timer is applied in the current access type or both 3GPP access type and non-3GPP access type. + +- 0 The back-off timer is applied in both 3GPP access type and non-3GPP access type. +- 1 The back-off timer is applied in the current access type. + +<procedure>: integer type. Indicates the procedure(s) for which the back-off timer applies. When <procedure>=0 the information returned is associated with timer T3584. For all other values of <procedure> the information returned is associated with the back-off timer as specified in 3GPP TS 24.501 [161] for the various session management procedures. When the parameter <procedure> is omitted, the back-off timer is deactivated. + +- 0 All procedures. +- 1 PDU session establishment procedure (see 3GPP TS 24.501 [161], clause 6.4.1) +- 2 PDU session modification procedure (see 3GPP TS 24.501 [161], clause 6.4.2). + +#### Implementation + +Optional. + +## 10.1.59 5GS use of SMS over NAS +C5GUSMS + +**Table 10.1.59-1: +C5GUSMS parameter command syntax** + +| Command | Possible Response(s) | +|-----------------------------------|---------------------------------------------------------------------------| +| +C5GUSMS=[<n>[, <sms_requested>]] | +CME ERROR: <err> | +| +C5GUSMS? | +C5GUSMS: <sms_available>, <sms_allowed> | +| +C5GUSMS=? | +C5GUSMS: (list of supported <n>s) , (list of supported <sms_requested>s) | + +### Description + +The set command enables the UE to request the use of SMS over NAS in 5GS or to request stopping the use of SMS over NAS in 5GS. Additionally, the set command controls the presentation of the unsolicited result code +C5GUSMS: <sms\_available>, <sms\_allowed> when <n>=2 and SMS over NAS in 5GS allowed status information or SMS over NAS in 5GS availability status information is received from the network, for the UE (see 3GPP TS 24.501 [161] clauses 5.4.4.3, 5.5.1.2.4 and 5.5.1.3.4). + +Refer to clause 9.2 for possible <err> values. + +The read command returns the current SMS over NAS in 5GS availability status for the UE and the current SMS over NAS in 5GS allowed status for the UE. + +The test command returns the values supported as compound values. + +### Defined values + +<n>: integer type + +- 0 no change in current setting of <n> +- 1 disable unsolicited result code +C5GUSMS <sms\_available>, <sms\_allowed> +- 2 enable unsolicited result code +C5GUSMS: <sms\_available>, <sms\_allowed> + +<sms\_requested>: integer type; indicates the UE's request for SMS over NAS in 5GS. + +- 0 triggers the UE to request the use of SMS over NAS in 5GS +- 1 triggers the UE to request stopping the use of SMS over NAS in 5GS + +<sms\_available>: integer type; indicates the current SMS over NAS in 5GS availability status for the UE in the network. + +- 0 indicates that the SMS over NAS in 5GS availability status for the UE is unknown +- 1 indicates that SMS over NAS in 5GS is not available in the network for the UE (see 3GPP TS 24.501 [161] clause 5.4.4.3) +- 2 indicates that SMS over NAS in 5GS is available in the network for the UE (see 3GPP TS 24.501 [161] clause 5.4.4.3) + +<sms\_allowed>: integer type; indicates the current SMS over NAS in 5GS allowed status for UE in the network. + +- 0 indicates that SMS over NAS in 5GS allowed status for the UE is unknown +- 1 indicates that the UE is not allowed by the network to use SMS over NAS in 5GS (see 3GPP TS 24.501 [161] clauses 5.4.4.3, 5.5.1.2.4 and 5.5.1.3.4) +- 2 indicates that the UE is allowed by the network to use SMS over NAS in 5GS (see 3GPP TS 24.501 [161] clauses 5.5.1.2.4 and 5.5.1.3.4) + +## Implementation + +Optional. + +### 10.1.60 Request LADN information +CRLADN + +**Table 10.1.60-1: +CRLADN action command syntax** + +| Command | Possible response(s) | +|-------------------------------------------|---------------------------------------------------------------------------------| +| +CRLADN[=<ladn_dnn>[, <ladn_dnn>[, ...]]] | +CME ERROR: <err><br><br>+CRLADN: <ladn_information_length>, <ladn_information> | +| +CRLADN=? | | + +## Description + +The execution command enables the TE to request LADN information from the MT for the specified LADN DNN(s). If the parameter <ladn\_dnn> in the execution command is omitted, it indicates a request to the MT for LADN information for all LADN(s) available in the current registration area. If <ladn\_information\_length> has a value of zero and <ladn\_information> consists of an empty string, no LADN information is stored on the MT. + +The command should be abortable as the LADN information is provided by the network. + +Refer clause 9.2 for possible <err> values. + +## Defined values + +<ladn\_dnn>: string type; included when the TE wants to request LADN information for specific LADN DNN(s). + +The <ladn\_dnn> is encoded as the value part of the DNN information element in 3GPP TS 24.501 [161], clause 9.11.2.1B. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<ladn\_information\_length>: integer type; indicates the number of octets of the <ladn\_information> information element. + +If the value is zero, no LADN information is stored on the MT. + +<ladn\_information>: string type; indicates the LADN information for one or more LADNs, where each LADN consists of a DNN and a tracking area identity list. The <ladn\_information> is encoded as the value part of the LADN information information element in 3GPP TS 24.501 [161], clause 9.11.3.30, where each DNN is encoded as the value part of the DNN information element in 3GPP TS 24.501 [161], clause 9.11.2.1B, and each tracking area identity list is encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161], clause 9.11.3.9. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no LADN information is stored on the MT. + +## Implementation + +Optional. + +### 10.1.60a Request extended LADN information +CRELADN + +**Table 10.1.60a-1: +CRELADN action command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| +CRELADN[=<ladn_dnn>, <s-nssai>[, <ladn_dnn>, <s-nssai>[, ...]]] | +CME ERROR: <err><br><br>+CRELADN: <extended_ladn_information_length>, <extended_ladn_information> | + +| | | +|------------|--| +| +CRELADN=? | | +|------------|--| + +## Description + +The execution command enables the TE to request extended LADN information from the MT for the specified LADN DNN(s) and S-NSSAI(s) associated with the LADN. If the parameters <ladn\_dnn> and <s-nssai> in the execution command are omitted, it indicates a request to the MT for extended LADN information for all LADN(s) available in the current registration area. If <extended\_ladn\_information\_length> has a value of zero and <extended\_ladn\_information> consists of an empty string, no extended LADN information is stored on the MT. + +The command should be abortable as the extended LADN information is provided by the network. + +Refer clause 9.2 for possible <err> values. + +## Defined values + +<ladn\_dnn>: string type; included when the TE wants to request extended LADN information for specific LADN DNN(s). The <ladn\_dnn> is encoded as the value part of the DNN information element in 3GPP TS 24.501 [161], clause 9.11.2.1B. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<s-nssai>: string type in hexadecimal format; included when the TE wants to request extended LADN information for specific S-NSSAI(s). Dependent of the form, the string can be separated by dot(s) and semicolon(s). Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<extended\_ladn\_information\_length>: integer type; indicates the number of octets of the <extended\_ladn\_information> information element. + +If the value is zero, no extended LADN information is stored on the MT. + +<extended\_ladn\_information>: string type; indicates the extended LADN information for one or more LADNs, where each LADN consists of a DNN, an S-NSSAI and a tracking area identity list. The <extended\_ladn\_information> is encoded as the value part of the Extended LADN information information element in 3GPP TS 24.501 [161], clause 9.11.3.96, where each DNN is encoded as the value part of the DNN information element in 3GPP TS 24.501 [161], clause 9.11.2.1B, each S-NSSAI is coded as the length and value part of S-NSSAI information element as specified in 3GPP TS 24.501 [161], clause 9.11.2.8 starting with the second octet, and each tracking area identity list is encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161], clause 9.11.3.9. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no extended LADN information is stored on the MT. + +## Implementation + +Optional. + +### 10.1.61 LADN information +CLADN + +**Table 10.1.61-1: +CLADN parameter command syntax** + +| Command | Possible response(s) | +|--------------|----------------------------------------------------------| +| +CLADN=[<n>] | +CME ERROR: <err> | +| +CLADN? | +CLADN: <n>,<ladn_information_length>,<ladn_information> | +| +CLADN=? | +CLADN: (list of supported <n>s) | + +## Description + +The set command controls the presentation of LADN information to the TE by an unsolicited result code +CLADNU: <ladn\_information\_length>, <ladn\_information> when there is a change in the LADN information stored at the MT. For each LADN, the LADN information consists of a DNN and a tracking identity list, as specified in 3GPP TS 24.501 [161], clause 9.11.3.30. If <ladn\_information\_length> has a value of zero and <ladn\_information> consists of an empty string, no LADN information is stored on the MT. + +Read command returns <n> which indicates whether reporting of LADN information is enabled or disabled. The read command also returns the current values of <ladn\_information\_length> and <ladn\_information> if available. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type. + +0 disable unsolicited result code + ++CLADNU: <ladn\_information\_length>, <ladn\_information> + +1 enable unsolicited result code +CLADNU: <ladn\_information\_length>, <ladn\_information> + +<ladn\_information\_length>: integer type; indicates the number of octets of the <ladn\_information> information element. + +If the value is zero, no LADN information is stored on the MT. + +<ladn\_information>: string type in hexadecimal format; indicates the LADN information for one or more LADNs, where each LADN consists of a DNN and a tracking area identity list. The <ladn\_information> is encoded as the value part of the LADN information information element in 3GPP TS 24.501 [161], clause 9.11.3.30, where each DNN is encoded as the value part of the DNN information element in 3GPP TS 24.501 [161], clause 9.11.2.1B, and each tracking area identity list is encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161], clause 9.11.3.9. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no LADN information is stored on the MT. + +#### Implementation + +Optional. + +### 10.1.61a Extended LADN information +CELADN + +**Table 10.1.61a-1: +CELADN parameter command syntax** + +| Command | Possible response(s) | +|---------------|-------------------------------------------------------------------------------| +| +CELADN=[<n>] | +CME ERROR: <err> | +| +CELADN? | +CELADN: <n>, <extended_ladn_information_length>, <extended_ladn_information> | +| +CELADN=? | +CELADN: (list of supported <n>s) | + +#### Description + +The set command controls the presentation of extended LADN information to the TE by an unsolicited result code +CELADNU: <extended\_ladn\_information\_length>, <extended\_ladn\_information> when there is a change in the extended LADN information stored at the MT. For each LADN, the extended LADN information consists of a DNN, an S-NSSAI and a tracking identity list, as specified in 3GPP TS 24.501 [161], clause 9.11.3.96. If <extended\_ladn\_information\_length> has a value of zero and <extended\_ladn\_information> consists of an empty string, no extended LADN information is stored on the MT. + +Read command returns <n> which indicates whether reporting of extended LADN information is enabled or disabled. The read command also returns the current values of <extended\_ladn\_information\_length> and <extended\_ladn\_information> if available. + +Test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type. + +- 0 disable unsolicited result code ++CELADNU: <extended\_ladn\_information\_length>, <extended\_ladn\_information> +- 1 enable unsolicited result code ++CELADNU: <extended\_ladn\_information\_length>, <extended\_ladn\_information> + +<extended\_ladn\_information\_length>: integer type; indicates the number of octets of the <extended\_ladn\_information> information element. + +If the value is zero, no extended LADN information is stored on the MT. + +<extended\_ladn\_information>: string type in hexadecimal format; indicates the extended LADN information for one or more LADNs, where each LADN consists of a DNN, an S-NSSAI and a tracking area identity list. The <extended\_ladn\_information> is encoded as the value part of the Extended LADN information information element in 3GPP TS 24.501 [161], clause 9.11.3.96, where each DNN is encoded as the value part of the DNN information element in 3GPP TS 24.501 [161], clause 9.11.2.1B, each S-NSSAI is coded as the length and value part of S-NSSAI information element as specified in 3GPP TS 24.501 [161], clause 9.11.2.8 starting with the second octet, and each tracking area identity list is encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161], clause 9.11.3.9. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no extended LADN information is stored on the MT. + +#### Implementation + +Optional. + +### 10.1.62 5GS NSSAI setting +C5GNSSAI + +**Table 10.1.62-1: +C5GNSSAI parameter command syntax** + +| Command | Possible Response(s) | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| +C5GNSSAI=<default_configured_nssai_length>, <default_configured_nssai> | +CME ERROR: <err> | +| +C5GNSSAI? | +C5GNSSAI: [<default_configured_nssai_length>, <default_configured_nssai>] | +| +C5GNSSAI=? | +C5GNSSAI: (range of supported <default_configured_nssai_length>s) , (range of supported <default_configured_nssai>s) | + +#### Description + +The set command enables updating the default configured NSSAI stored at the MT (see 3GPP TS 24.501 [161] clause 4.6.2.2). If <default\_configured\_nssai\_length> has a value of zero and <default\_configured\_nssai> consists of an empty string, the default configured NSSAI stored at the MT, if any, shall be deleted by the MT. If the MT has previously received a default configured NSSAI from the network via NAS signalling as specified in 3GPP TS 24.501 [161], the default configured NSSAI stored at the MT is not updated and an error message, +CME ERROR, is returned to TE. Refer clause 9.2 for possible <err> values. + +The read command returns the current parameter values. + +The test command returns the values supported as compound values. + +#### Defined values + +<default\_configured\_nssai\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <default\_configured\_nssai> parameter. + +<default\_configured\_nssai>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of S-NSSAIs included in the default configured NSSAI to be stored by the MT. The <default\_configured\_nssai> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no default configured NSSAI is stored at the MT. + +#### Implementation + +Optional. + +### 10.1.63 5GS NSSAI read dynamic parameters +C5GNSSAIRDP + +Table 10.1.63-1: +C5GNSSAIRDP action command syntax + +| Command | Possible Response(s) | +|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GNSSAIRDP[=<nssai_type>[, <plmn_id>]] | <p>[+C5GNSSAIRDP: [<default_configured_nssai_length>, <default_configured_nssai>[, <rejected_nssai_3gpp_length>, <rejected_nssai_3gpp>[, <rejected_nssai_non3gpp_length>, <rejected_nssai_non3gpp>[, <extended_rejected_nssai_3gpp_length>, <extended_rejected_nssai_3gpp>[, <extended_rejected_nssai_non3gpp_length>, <extended_rejected_nssai_non3gpp>]]]]]</p> <p>[<CR><LF>+C5GNSSAIRDP: <plmn_id>[, <configured_nssai_length>, <configured_nssai>[, <allowed_nssai_3gpp_length>, <allowed_nssai_3gpp>, <allowed_nssai_non3gpp_length>, <allowed_nssai_non3gpp>[, <no_of_partially_allowed_nssais>[, <partially_allowed_nssai1>, <TAI_list1>[, <partially_allowed_nssai2>, <TAI_list2>[...]]]]]]]</p> <p>[<CR><LF>+C5GNSSAIRDP: <plmn_id>[, <configured_nssai_length>, <configured_nssai>[, <allowed_nssai_3gpp_length>, <allowed_nssai_3gpp>, <allowed_nssai_non3gpp_length>, <allowed_nssai_non3gpp>]]]</p> <p>[...]]]]]</p> | +| +C5GNSSAIRDP=? | +C5GNSSAIRDP: (list of supported <nssai_type>s) , (range of supported <plmn_id>s) | + +## Description + +The execution command returns the default configured NSSAI, rejected NSSAI for 3GPP access and rejected NSSAI for non-3GPP access stored at the MT, if any, as well as the configured NSSAI, allowed NSSAI, and partially allowed NSSAI for 3GPP access and allowed NSSAI for non-3GPP access stored at the MT, if any for the PLMN identified by <plmn\_id>. + +If the parameter <plmn\_id> is omitted, the NSSAIs for all PLMNs for which the MT has stored NSSAI information are returned. + +The test command returns the values supported as compound values. + +## Defined values + +<nssai\_type>: integer type; specifies the type of NSSAI to be returned. + +- 0 return stored default configured NSSAI only +- 1 return stored default configured NSSAI and rejected NSSAI +- 2 return stored default configured NSSAI, rejected NSSAI and configured NSSAI +- 3 return stored default configured NSSAI, rejected NSSAI, configured NSSAI and allowed NSSAI +- 4 return stored default configured NSSAI, rejected NSSAI, configured NSSAI allowed NSSAI and partially allowed NSSAI + +<plmn\_id>: string type; indicates the MCC and MNC of the PLMN to which the NSSAI information applies. For the format and the encoding of the MCC and MNC, see 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<default\_configured\_nssai\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <default\_configured\_nssai> parameter. + +<default\_configured\_nssai>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of S-NSSAIs included in the default configured NSSAI stored at the MT for the PLMN. The <default\_configured\_nssai> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<rejected\_nssai\_3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <rejected\_nssai\_3gpp> parameter. + +<rejected\_nssai\_3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), colon(s) and hash(es). This parameter indicates the list of rejected S-NSSAIs associated with 3GPP access stored at the MT for the serving PLMN. The <rejected\_nssai\_3gpp> is coded as a list of rejected S-NSSAIs separated by colons. For the format and the encoding of S-NSSAI, see also 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. The rejected S-NSSAI has one of the forms: + +- sst#cause only slice/service type (SST) and reject cause are present +- sst.sd#cause SST and slice differentiator (SD) and reject cause are present + +where cause is a cause value according to 3GPP TS 24.501 [161] table 9.11.3.46.1. + +<rejected\_nssai\_non3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <rejected\_nssai\_non3gpp> parameter. + +<rejected\_nssai\_non3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), colon(s) and hash(es). This parameter indicates the list of rejected S-NSSAIs associated with non-3GPP access stored at the MT for the serving PLMN. The <rejected\_nssai\_non3gpp> is coded as a list of rejected S-NSSAIs separated by colon. For the format and the encoding of S-NSSAI, see also 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. The rejected S-NSSAI has one of the forms: + +sst#cause      only slice/service type (SST) and reject cause are present + sst.sd#cause SST and slice differentiator (SD) and reject cause are present + +where cause is a cause value according to 3GPP TS 24.501 [161] table 9.11.3.46.1. + +<configured\_nssai\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <configured\_nssai> parameter. + +<configured\_nssai>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of configured S-NSSAIs stored at the MT for the PLMN identified by <plmn\_id>. The <configured\_nssai> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<allowed\_nssai\_3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <allowed\_nssai\_3gpp> parameter. + +<allowed\_nssai\_3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of allowed S-NSSAIs associated with 3GPP access stored at the MT for the PLMN identified by <plmn\_id>. The <allowed\_nssai\_3gpp> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<allowed\_nssai\_non3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <allowed\_nssai\_non3gpp> parameter. + +<allowed\_nssai\_non3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of allowed S-NSSAIs associated with non-3GPP access stored at the MT for the PLMN identified by <plmn\_id>. The <allowed\_nssai\_non3gpp> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<extended\_rejected\_nssai\_3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <extended\_rejected\_nssai\_3gpp> parameter. + +<extended\_rejected\_nssai\_3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s), colon(s) and hash(es). This parameter indicates the list of rejected S-NSSAIs associated with 3GPP access stored at the MT for the serving PLMN. The <extended\_rejected\_nssai\_3gpp> is coded as a list of rejected S-NSSAIs separated by colons. For the format and the encoding of S-NSSAI, see also 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. The rejected S-NSSAI has one of the forms: + +sst#cause      only slice/service type (SST) and reject cause are present + sst;mapped\_sst#cause      SST, mapped HPLMN SST and reject cause are present + sst.sd#cause      SST and slice differentiator (SD) and reject cause are present + sst.sd;mapped\_sst#cause      SST, SD, mapped HPLMN SST and reject cause are present + sst.sd;mapped\_sst.mapped\_sd#cause      SST, slice differentiator (SD), mapped HPLMN SST, mapped HPLMN SD and reject cause are present + +where cause is a cause value according to 3GPP TS 24.501 [161] table 9.11.3.75.1. + +<extended\_rejected\_nssai\_non3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <extended\_rejected\_nssai\_non3gpp> parameter. + +<extended\_rejected\_nssai\_non3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s), colon(s) and hash(es). This parameter indicates the list of rejected S-NSSAIs associated with non-3GPP access stored at the MT for the serving PLMN. The <extended\_rejected\_nssai\_non3gpp> is coded as a list of rejected S-NSSAIs separated by colon. For the format and the encoding of S-NSSAI, see also 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. The rejected S-NSSAI has one of the forms: + +sst#cause        only slice/service type (SST) and reject cause are present + sst;mapped\_sst#cause        SST, mapped HPLMN SST and reject cause are present + sst.sd#cause        SST and slice differentiator (SD) and reject cause are present + sst.sd;mapped\_sst#cause        SST, SD, mapped HPLMN SST and reject cause are present + sst.sd;mapped\_sst.mapped\_sd#cause        SST, slice differentiator (SD), mapped HPLMN SST, mapped HPLMN SD and reject cause are present + +where cause is a cause value according to 3GPP TS 24.501 [161] table 9.11.3.75.1. + +<no\_of\_partially\_allowed\_nssais>: integer type; indicates the number of S-NSSAIs present in partially allowed NSSAI. The value can range from 0 to 8. + +<partially\_allowed\_nssai>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of partially allowed S-NSSAIs associated with the 3GPP access stored at the MT for the PLMN identified by <plmn\_id>. The <partially\_allowed\_nssai> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<TAI\_list>: string type in hexadecimal format; encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161] clause 9.11.3.9. + +## Implementation + +Optional. + +## 10.1.64 5GS Preferred NSSAI +C5GPNSSAI + +**Table 10.1.64-1: +C5GPNSSAI parameter command syntax** + +| Command | Possible Response(s) | +|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| +C5GPNSSAI=[<Preferred_NSSAI_3gpp_length>, [<Preferred_NSSAI_3gpp>]], [<Preferred_NSSAI_non3gpp_length>, [<Preferred_NSSAI_non3gpp>]] | +CME ERROR: <err> | +| +C5GPNSSAI? | +C5GPNSSAI: <Preferred_NSSAI_3gpp_length>, <Preferred_NSSAI_3gpp>, <Preferred_NSSAI_non3gpp_length>, <Preferred_NSSAI_non3gpp> | +| +C5GPNSSAI=? | +C5GPNSSAI: (range of supported <Preferred_NSSAI_3gpp_length>s), (range of supported <Preferred_NSSAI_non3gpp_length>s) | + +## Description + +The set command specifies the preferred NSSAI as a list of S-NSSAIs matching the preference of the TE. The preferred NSSAI is coded as a list of HPLMN values of S-NSSAIs. Its content is independent of the selected or registered PLMNs. MT takes the preferred NSSAI into account when selecting the requested NSSAI. + +NOTE: It is the MT responsibility to ensure that the Requested NSSAI IE sent to the network during 5GS registration is set according to the rules in 3GPP TS 24.501 [161]. MT takes into account the configured NSSAI for the current PLMN, the allowed NSSAI for the current PLMN and access type, and the rejected NSSAI for the current PLMN, rejected NSSAI for the current PLMN and registration area combination, rejected NSSAI for the failed or revoked NSSAA or rejected NSSAI for the maximum number of UEs reached. + +Refer to clause 9.2 for possible <err> values. + +A special form of the set command can be given as +C5GPNSSAI= without any parameters. In this form, no preferred NSSAI for 3GPP access and no preferred NSSAI for non-3GPP access are stored in the MT. + +The read command returns the current values. + +The test command returns the values supported as compound values. + +#### Defined values + +<Preferred\_NSSAI\_3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <Preferred\_NSSAI\_3gpp> parameter + +<Preferred\_NSSAI\_3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of preferred S-NSSAIs for 3GPP access. The <Preferred\_NSSAI\_3gpp> is coded as a list of S-NSSAIs separated by colons. The TE includes the HPLMN values of the S-NSSAIs; therefore, no mapped S-NSSAIs are included. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no preferred NSSAI for 3GPP access is stored in the MT. + +<Preferred\_NSSAI\_non3gpp\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <Preferred\_NSSAI\_non3gpp> parameter. + +<Preferred\_NSSAI\_non3gpp>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of preferred S-NSSAIs for non-3GPP access. The <Preferred\_NSSAI\_non3gpp> is coded as a list of S-NSSAIs separated by colons. The TE includes the HPLMN values of the S-NSSAIs; therefore, no mapped S-NSSAIs are included. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +### 10.1.65 Indicating the selected PLMN for access to restricted local operator services (RLOS) +CRLOSP + +**Table 10.1.65-1: +CRLOSP parameter command syntax** + +| Command | Possible response(s) | +|-------------|-----------------------------------| +| +CRLOSP=<n> | +CME ERROR: <err> | +| +CRLOSP? | +CRLOSP: <n>[, <RLOS_plmn>] | +| +CRLOSP=? | +CRLOSP: (list of supported <n>s) | + +#### Description + +The set command controls the presentation of unsolicited result code +CRLOSPU: <RLOS\_plmn> when <n>=1 indicating the PLMN that the UE has selected for access to RLOS. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current settings of <n> and the currently selected PLMN for access to RLOS (if available). + +The test command returns values supported as a compound value. + +#### Defined values + +<n>: integer type. + +- 0 Disable presentation of the unsolicited result code +CRLOSPU. +- 1 Enable presentation of the unsolicited result code +CRLOSPU. + +<RLOS\_plmn>: string type; indicates the MCC and MNC of the PLMN that the UE has selected for access to RLOS. For the format and the encoding of the MCC and MNC, see 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. This command is only applicable to UEs in E-UTRAN. + +## 10.1.66 Link packet filters +CGLNKPF + +**Table 10.1.66-1: +CGLNKPF parameter command syntax** + +| Command | Possible Response(s) | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| +CGLNKPF=[<cid>[, <packet filter identifier>]] | +CME ERROR: <err> | +| +CGLNKPF? | [+CGLNKPF: <cid>, <packet filter identifier>]<br>[<CR><LF>+CGLNKPF: <cid>, <packet filter identifier>]<br>[...]] | +| +CGLNKPF=? | +CGLNKPF: (range of supported <cid>s) , (list of supported <packet filter identifier>s) | + +### Description + +The set command allows the TE to specify the existing packet filter identified by the packet filter identifier <packet filter identifier> of the TFT + +- which is linked to the new packet filter(s) to be added; or +- for which a change of the GBR is to be requested + +(i.e. the packet filter identifier(s) indicated in the Parameters list of the Traffic flow aggregate IE, see 3GPP TS 24.301 [83] clause 6.5.4.2). Refer clause 9.2 for possible <err> values. + +A special form of the set command, +CGLNKPF=<cid> causes the packet filter identifier for context number <cid> to become undefined. A special form of the set command, +CGLNKPF= causes the linked packet filter identifiers for all the contexts to become undefined. + +The read command returns the current settings for each defined context. + +The test command returns the ranges of the supported parameters as compound values. + +### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<packet filter identifier>: integer type. Value range is from 1 to 16. + +NOTE: While the numbering of packet filter identifier in this specification ranges from 1 to 16, the numbering of packet filter identifier in 3GPP TS 24.008 [8] ranges from 0 to 15. It is up to MT implementation to perform a mapping between the two value ranges. + +## Implementation + +Optional. + +### 10.1.67 Delete packet filters +CGDELFP + +**Table 10.1.67-1: +CGDELFP parameter command syntax** + +| Command | Possible Response(s) | +|---------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| +CGDELFP=[<cid>[, <packet filter identifier>[, <QRI>]]] | +CME ERROR: <err> | +| +CGDELFP? | [+CGDELFP: <cid>, <packet filter identifier>[, <QRI>]]<br>[<CR><LF>+CGDELFP: <cid>, <packet filter identifier>[, <QRI>]]<br>[...]] | +| +CGDELFP=? | +CGDELFP: (range of supported <cid>s), (list of supported <packet filter identifier>s), (range of supported <QRI>s) | + +#### Description + +The set command allows the TE to specify the packet filter identified by the packet filter identifier <packet filter identifier> to be deleted, or the QoS rule identified by the QoS rule identifier <QRI> to be deleted. To delete a packet filter in 5GS, both the filter identifier <packet filter identifier> and the corresponding QoS rule identifier <QRI> are required. Refer clause 9.2 for possible <err> values. + +A special form of the set command, +CGDELFP=<cid> causes the values for context number <cid> to become undefined. A special form of the set command, +CGDELFP= causes the current settings for each packet filter and QoS rule to become undefined. + +The read command returns the current settings for each defined context. + +The test command returns the ranges of the supported parameters as compound values. + +#### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<packet filter identifier>: integer type. Value range is from 1 to 16. + +NOTE: While the numbering of packet filter identifier in this specification ranges from 1 to 16, the numbering of packet filter identifier in 3GPP TS 24.008 [8] ranges from 0 to 15. It is up to MT implementation to perform a mapping between the two value ranges. + +<QRI>: integer type. Identifies the QoS rule, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. + +## Implementation + +Optional. + +## 10.1.68 Bit rate recommendation request +CGBRRREQ + +**Table 10.1.68-1: +CGBRRREQ action command syntax** + +| Command | Possible response(s) | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| +CGBRRREQ=<cid>,<reqBitrate>,<direction> | +CME ERROR: <err> | +| +CGBRRREQ=? | +CGBRRREQ: (range of supported <cid>s), (range of supported <reqBitrate>s), (list of supported <direction>s) | + +### Description + +The command is used to request the UE to transmit a MAC Control Element containing a Recommended bit rate query to the serving eNB or gNB for the EPS bearer context or the 5GS QoS flow identified by <cid> and the direction (uplink or downlink) indicated in <direction> as specified in 3GPP TS 36.321 [158] and in 3GPP TS 38.321 [176]. Refer clause 9.2 for possible <err> values. + +The test command returns the values supported as a compound value. + +### Defined values + +<cid>: A numeric parameter which specifies a particular EPS bearer context or a 5GS QoS flow. The <cid> parameter is local to the TE-MT interface and identifies only EPS bearer contexts or 5GS QoS flows which have been setup via AT command (see the +CGDCONT and +CGDSCONT commands). + +<reqBitrate>: integer type; indicates the aggregate requested bit rate in kbit/s for the EPS bearer context or the 5GQoS flow identified by <cid>. + +<direction>: integer type; indicates the direction to which the recommended bit rate query applies. + +- 1 The recommended bit rate query is for the uplink direction +- 2 The recommended bit rate query is for the downlink direction + +### Implementation + +Optional. + +## 10.1.69 Bit rate recommendation reporting +CGBRRREP + +**Table 10.1.69-1: +CGBRRREP parameter command syntax** + +| Command | Possible Response(s) | +|-------------------------|---------------------------------------------| +| +CGBRRREP=[<reporting>] | +CME ERROR: <err> | +| +CGBRRREP? | +CGBRRREP: <reporting> | +| +CGBRRREP=? | +CGBRRREP: (list of supported <reporting>s) | + +### Description + +The set command enables reporting of the recommended bit rate received by the UE from the serving eNB or gNB in a MAC Control Element as specified in 3GPP TS 36.321 [158] and in 3GPP TS 38.321 [176] with the unsolicited result code +CGBRRREP: <recmBitrate>,<direction>,<num\_of\_cids>,<cid>[,<cid>[, . . . ]]. Refer clause 9.2 for possible <err> values. + +The read command returns current command setting. + +The test command returns the values supported as a compound value. + +#### Defined values + +<reporting>: integer type. + +- 0 Reporting not enabled +- 1 Reporting enabled + +<recmBitrate>: integer type; indicates the recommended bit rate in kbit/s received from the serving eNB or gNB. + +<direction>: integer type; indicates the direction to which the recommended bit rate received from the serving eNB or gNB applies. + +- 1 The recommended bit rate is for the uplink direction +- 2 The recommended bit rate is for the downlink direction + +<num\_of\_cids>: integer type; indicates the number of <cid>s mapped to the LCID (Logical Channel ID) to which the recommended bit rate received from the serving eNB or gNB applies. + +NOTE: In 5GS, multiple 5G QoS flows can be mapped to the same LCID. In EPS, there is a one-to-one mapping between an EPS bearer context and an LCID. + +<cid>: A numeric parameter which specifies a particular EPS bearer context or a 5GS QoS flow mapped to the LCID to which the recommended bit rate received from the serving eNB or gNB applies. The <cid> parameter is local to the TE-MT interface. + +#### Implementation + +Optional. + +### 10.1.70 5GS ATSSS Rules read dynamic parameters +C5GATSSSRDP + +**Table 10.1.70-1: + C5GATSSSRDP action command syntax** + +| Command | Possible Response(s) | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| +C5GATSSSRDP[=<cid>] | [+C5GATSSSRDP: <cid>[, <ATSSS_rule-l>, <ATSSS_rule-c>]]<br><br>[<CR><LF>+C5GATSSSRDP: <cid>[, <ATSSS_rule-l>, <ATSSS_rule-c>]<br>[...]] | +| +C5GATSSSRDP=? | +C5GATSSSRDP: (list of <cid>s associated with QoS flows) | + +#### Description + +The execution command returns the ATSSS rules <ATSSS\_rule-l> and <ATSSS\_rule-c> of the QoS flow of the default QoS rule associated to the provided context identifier <cid>. + +If the parameter <cid> is omitted, the ATSSS parameters for all QoS flows are returned. + +The test command returns a list of <cid>s associated with all QoS flows. + +#### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<ATSSS\_rule-l>: integer type; indicates the length in octets of the <ATSSS\_rule-c>. + +<ATSSS\_rule-c>: string type; coded as defined in 3GPP TS 24.193 [177] clause 6.1.3.2. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. This AT-cmd is applicable to UEs that support ATSSS. + +### 10.1.71 5GS network steering functionalities information read dynamic parameters +C5GNSFIRDP + +**Table 10.1.71-1: + C5GNSFIRDP action command syntax** + +| Command | Possible Response(s) | +|---------------------|-------------------------------------------------------------------------------------------------------------| +| +C5GNSFIRDP[=<cid>] | [+C5GNSFIRDP: <cid>[, <NSFI-l>, <NSFI-c>]]<br>[<CR><LF>+ C5GNSFIRDP: <cid>[, <NSFI-l>, <NSFI-c>]]<br>[...]] | +| +C5GNSFIRDP=? | +C5GNSFIRDP: (list of <cid>s associated with QoS flows) | + +#### Description + +The execution command returns the network steering functionalities information <NSFI-l> and <NSFI-c> of the QoS flow of the default QoS rule associated with the provided context identifier <cid>. + +If the parameter <cid> is omitted, the network steering functionalities information for all QoS flows are returned. + +The test command returns a list of <cid>s associated with all QoS flows. + +#### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<NSFI-l>: integer type; indicates the length in octets of the <NSFI-c>. + +<NSFI-c>: string type; coded as defined in 3GPP TS 24.193 [177] clause 6.1.4.2. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +### 10.1.72 Context State Change Request +CCSTATREQ + +**Table 10.1.72-1: +CCSTATREQ parameter command syntax** + +| Command | Possible Response(s) | +|---------------------------------------------|--------------------------------------------------------------------------------| +| +CCSTATREQ=<state>[, <cid>[, <cid>[, ...]]] | +CME ERROR: <err> | +| +CCSTATREQ? | [+CCSTATREQ: <cid>, <state>]<br>[<CR><LF>+CCSTATREQ: <cid>, <state>]<br>[...]] | +| +CCSTATREQ=? | +CCSTATREQ: (list of supported <state>s) | + +## Description + +The execution command is used to activate the specified PDP context(s) or to request for the specified QoS flow. The command is also used to deactivate the context or to delete the QoS flow. The command returns with the response depending upon whether the request is successfully sent to the lower layers or not. + +The actual result for the PDU session establishment from the network will be displayed through the unsolicited result code +CCSTATEEREQU: <result>, <cid> once the indication is received from the network. + +The request for a specific QoS flow will be answered by the network by a PDU session establishment accept message or a PDU session modification command message. This PDU establishment procedure may require several sessions of request-response of EAP authentication messages between the MT and the network to complete the procedure (see the +C5GPDUAUTHR and +C5GPDUAUTHS commands), see 3GPP TS 24.501 [161] clause 6.3.1. + +For EPS, if an attempt is made to disconnect the last PDN connection, then the MT responds with ERROR or, if extended error responses are enabled, a +CME ERROR. + +For EPS, the activation request for an EPS bearer resource will be answered by the network by either an EPS dedicated bearer activation or EPS bearer modification request. The request must be accepted by the MT before the PDP context can be set in to established state. + +If the MT is not PS attached when the request for QoS flow command is executed, the MT first performs a PS attach and then attempts to activate the context or request the specific QoS flow. + +If no <cid>s are specified, the activation form of the command activates all defined non-emergency contexts. + +If no <cid>s are specified, the deactivation form of the command deactivates all active contexts. + +The read command returns the current activation states for all the defined PDP contexts. The state displayed for each context is the previous state until the next state is completely accepted by the MT. + +The test command is used for requesting information on the supported PDP context activation states. + +## Defined values + +<cid>: integer type; specifies a particular QoS flow definition (see the +CGDCONT and +CGDSCONT commands). + +<state>: integer type; indicates the state of PDP context activation. + +0 deactivated + +1 activated + +<result>: integer type; indicates the final result for PDU session establishment procedure. + +0 Successfully established. + +1 Failed to establish. + +## Implementation + +Optional. + +## 10.1.73 5G PDU Session Authentication Setting +C5GPDUAUTHS + +**Table 10.1.73-1: +C5GPDUAUTHS parameter command syntax** + +| Command | Possible response(s) | +|------------------|----------------------------------------| +| +C5GPDUAUTHS=<n> | +CME ERROR: <err> | +| +C5GPDUAUTHS? | +C5GPDUAUTHS: <n> | +| +C5GPDUAUTHS=? | +C5GPDUAUTHS: (list of supported <n>s) | + +## Description + +3GPP + +The set command controls the presentation of an unsolicited result code +C5GPDUAUTHU: <cid>, <len>, <eap\_msg> which will be displayed on receiving an authentication message in the form of Extensible Authentication Protocol (EAP) message from network during or after a UE-requested non-emergency PDU establishment request has been sent. The purpose of the PDU session authentication and authorization is to enable the data network (DN) to authenticate and authorize the upper layers of UE. This procedure happens through EAP as specified in IETF RFC 3748 [32] and 3GPP TS 24.501 [161] clause 6.3.1. + +There can be several sessions of exchange of an EAP-request and EAP-response message for the DN to complete the authentication and authorization of the request for a PDU session. The network shall start a timer (T3590) once the EAP-request message has been sent and expects the EAP-response message from UE to stop the timer. On expiry of the timer, network shall re-transmit the message after restarting the timer. This can be retransmitted for four times. + +Read command returns the current setting of value <n>. + +Test command returns the range of supported <n>. + +#### Defined values + +<n>: integer type. Enables or disables reporting of authentication indication from network consisting of the EAP-message for a particular <cid>. + +0 disable reporting. + +1 enable reporting. + +<cid>: integer type, specifies a particular QoS flow definition (see the +CGDCONT and +CGDSCONT commands). + +<len>: integer type, indicates the length of the EAP message content. It can be of max 1500 according to 3GPP TS 24.501 [161] clause 9.11.2.2. + +<eap\_msg>: string type in hexadecimal format, consists of the EAP message from network, as defined in IETF RFC 3748, IETF RFC 4187 and IETF RFC 5448. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +### 10.1.74 5G PDU Session Authentication Response +C5GPDUAUTHR + +**Table 10.1.74-1: +C5GPDUAUTHR action command syntax** + +| Command | Possible response(s) | +|--------------------------------------|----------------------| +| +C5GPDUAUTHR=<cid>, <len>, <eap_msg> | +CME ERROR: <err> | +| +C5GPDUAUTHR=? | | + +#### Description + +Execution command allows the UE to send the EAP-response message to the EAP-request made by network for a particular PDU session. The EAP-request message is received through the unsolicited result code +C5GPDUAUTHU. The authentication request is sent by the network to authenticate and authorize the upper layers of UE when a UE-requested non-emergency PDU session establishment request is sent. The response to the execution command only indicates if the EAP-response message has been successfully sent to lower layers or not. + +NOTE: Calculating the EAP response for the request received can be implementation specific. + +#### Defined values + +<cid>: integer type, specifies a particular QoS flow definition (see the +CGDCONT and +CGDSCONT commands). + +<len>: integer type, indicates the length of the EAP message content. It can be of max 1500 according to 3GPP TS 24.501 [161] clause 9.11.2.2. + +<eap\_msg>: string type in hexadecimal format, consists of the EAP message from network as defined in IETF RFC 3748 , IETF RFC 4187 and IETF RFC 5448. This parameter shall not be subject to conventional character conversion as per +CSCS. + +## Implementation + +Optional. + +## 10.1.75 5GS URSP query +C5GURSPQRY + +**Table 10.1.75-1: +C5GURSPQRY parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GURSPQRY=[<APPID>]<br>[,<OSID&APPID>] [,<DNNs>]<br>[,<FQDN>]<br>[,<Connection_capabilities>]<br>[,<remote_ipv4_address_and_m<br>ask>]<br>[,<remote_ipv6_address_and_p<br>refix_length>] [,<protocol<br>number (ipv4)/next header<br>(ipv6)>]<br>[,<single_remote_port>]<br>[,<remote port range>]<br>[,<security para index>]<br>[,<type of service (tos)<br>(ipv4) and mask / traffic<br>class (ipv6) and mask>]<br>[,<flow label>]<br>[,<ether_type>]<br>[,<destination_mac_address>]<br>[,<cTagVid>] [,<sTagVid>]<br>[,<cTagPcpDei>]<br>[,<sTagPcpDei>]<br>[,<Regular_expression>]<br>[,<PIN ID>] [,<Connectivity<br>group ID>] | +C5GURSPQRY: [<ursp_rule_type>],<br>[<ursp_rule_precedence>],<br>[<route_selection_descriptor_precedence>], [<SSC_mode>],<br>[<NSSAI>], [<DNNs>], [<pdp_type>],<br>[<preferred_access_type>], [<Non-<br>seamless_non-3GPP_offload_indication>],<br>[<Location_criteria_type>], [<Time_window_type>]<br><br>[<CR><LF>+C5GURSPQRY: [<ursp_rule_type>],<br>[<ursp_rule_precedence>],<br>[<route_selection_descriptor_precedence>], [<SSC_mode>],<br>[<NSSAI>], [<DNNs>], [<pdp_type>],<br>[<preferred_access_type>], [<Non-<br>seamless_non-3GPP_offload_indication>],<br>[<Location_criteria_type>], [<Time_window_type>]<br><br>[...]] | + +| | | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GURSPQRY? | <p>+C5GURSPQRY: [<ursp_rule_type>], [<ursp_rule_precedence>], [<APPID>], [<OSID&APPID>], [<DNNs>], [<FQDN>], [<Connection_capabilities>], [<remote_ipv4_address_and_mask>], [<remote_ipv6_address_and_prefix_length>], [<protocol number (ipv4)/next header (ipv6)>], [<single_remote_port>], [<remote port range>], [<security para index>], [<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>], [<flow label>], [<ether_type>], [<destination_mac_address>], [<cTagVid>], [<sTagVid>], [<cTagPcpDei>], [<sTagPcpDei>], [<Regular_expression>], [<PIN ID>], [<Connectivity group ID>], [<route_selection_descriptor_precedence>], [<SSC_mode>], [<NSSAI>], [<DNNs>], [<pdp_type>], [<preferred_access_type>], [<Non-seamless_non-3GPP_offload_indication>], [<Location_criteria_type>], [<Time_window_type>]</p> <p>[<CR><LF>+C5GURSPQRY: [<ursp_rule_type>], [<ursp_rule_precedence>], [<APPID>], [<OSID&APPID>], [<DNNs>], [<FQDN>], [<Connection_capabilities>], [<remote_ipv4_address_and_mask>], [<remote_ipv6_address_and_prefix_length>], [<protocol number (ipv4)/next header (ipv6)>], [<single_remote_port>], [<remote port range>], [<security para index>], [<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>], [<flow label>], [<ether_type>], [<destination_mac_address>], [<cTagVid>], [<sTagVid>], [<cTagPcpDei>], [<sTagPcpDei>], [<Regular_expression>], [<route_selection_descriptor_precedence>], [<SSC_mode>], [<NSSAI>], [<DNNs>], [<pdp_type>], [<preferred_access_type>], [<Non-seamless_non-3GPP_offload_indication>], [<Location_criteria_type>], [<Time_window_type>]</p> <p>[...] ]</p> | +| +C5GURSPQRY=? | <p>+C5GURSPQRY: (list of supported<Connection_capabilities>s), (list of supported <remote_ipv4_address_and_mask>s), (list of supported <remote_ipv6_address_and_prefix_length>s), (list of supported <protocol number (ipv4) / next header (ipv6)>s), (list of supported<single_remote_port>s), (list of supported<remote port range>s), (list of supported<security para index>s), (list of supported<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>s), (list of supported<flow label>s), (list of supported<ether_type>s), (list of supported<destination_mac_address>s), (list of supported<cTagVid>s), (list of supported<sTagVid>s), (list of supported<cTagPcpDei>s), (list of supported<sTagPcpDei>s), list of supported<PIN ID>s), list of supported<connectivity group ID>s)</p> | + +### Description + +The set command is used to request the MT to return all the route selection descriptors for the URSP rules with different precedence values matching the traffic descriptor indicated by the input parameters in <APPID>, <OSID&APPID>, <DNNs>, <FQDN>, <Connection\_capabilities>, <remote\_ipv4\_address\_and\_mask>, <remote\_ipv6\_address\_and\_prefix\_length>, <protocol number (ipv4)/next + +header (ipv6)>,<single\_remote\_port>,<remote port range>,<security para index>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label>,<ether\_type>,<destination\_mac\_address>,<cTagVid>,<sTagVid>,<cTagPcpDei>,<sTagPcpDei>,<Regular\_expression>,<PIN ID>,<Connectivity group ID>. + +A special form of the set command can be given as +C5GURSPQRY=. This form can be used as Match-all type to request the MT to return the default URSP rule. + +The read command is used to return all of the URSP rules stored at MT. + +Test command returns values supported as compound values. + +### Defined values + +<APPID>: string type. Indicates an application. + +<OSID&APPID>: string type. Indicates an operating system and an associated application. + +<DNNs>: string type. The string can be separated by semicolon(s), indicates the list of <DNN> referred in clause 10.1.57. + +<FQDN>: string type. Indicates a fully qualified Domain Name. + +<Connection\_capabilities>: integer type. A decimal value indicates the connection's supported services according to Table 5.2.1 of TS 24.526 [180]. + +<remote\_ipv4\_address\_and\_mask>: string type. The string is given as dot-separated numeric (0-255) parameters which indicates a remote IPv4 address and the associated mask, on the form of "a1.a2.a3.a4.m1.m2.m3.m4". + +<remote\_ipv6\_address\_and\_prefix\_length>: string type. The string is given as dot-separated numeric (0-255) parameters which indicates a remote IPv6 address and the associated length of the prefix, on the form of "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16". + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +C5GURSPQRY. + +<protocol number (ipv4) / next header (ipv6)>: integer type. Value range is from 0 to 255. + +<single\_remote\_port>: integer type. Value range is from 0 to 65535. + +<remote port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t". + +<security para index>: numeric value in hexadecimal format. Value range is from 00000000 to FFFFFFFF. + +<type of service (tos) (ipv4) and mask/traffic class (ipv6) and mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the form "t.m". + +<flow label>: numeric value in hexadecimal format. The value range is from 00000 to FFFFF. Valid for IPv6 only. + +<ether\_type>: integer type. Value range is from 0 to 65535 + +<destination\_mac\_address>: string type, on the form of "a1.a2.a3.a4.a5.a6". + +<cTagVid>: integer type. See IEEE 802.1Q [181]. + +<sTagVid>: integer type. See IEEE 802.1Q [181]. + +<cTagPcpDei>: integer type. See IEEE 802.1Q [181]. + +<sTagPcpDei>: integer type. See IEEE 802.1Q [181]. + +<PIN\_ID>: string type. Indicates a PIN. + +<Connectivity group ID>: string type. Indicates a connectivity group configured in the 5G-RG. + +<Regular\_expression>: string type. The regular expression value field shall take the form of Extended Regular expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [182]. + +<ursp\_rule\_type>: integer type. Indicates if the type of the URSP rule. + +0 non-default URSP rule + +1 default URSP rule + +<ursp\_rule\_precedence>: integer type. Indicates the precedence of the URSP rule. + +<route\_selection\_descriptor\_precedence>: Indicates the precedence of the route selection descriptor. + +<SSC\_mode>: integer type. Indicates the session and service continuity (SSC) mode for the PDU session in 5GS, see 3GPP TS 23.501 [165]. + +0 indicates that the PDU session is associated with SSC mode 1 + +1 indicates that the PDU session is associated with SSC mode 2 + +2 indicates that the PDU session is associated with SSC mode 3 + +<NSSAI>: string type in hexadecimal character format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). The <NSSAI> is coded as a list of <S-NSSAI>s separated by colons. This parameter shall not be subject to conventional character conversion as per +CSCS. The <S-NSSAI> has one of the forms: + +sst only slice/service type (SST) is present + +sst;mapped\_sst SST and mapped configured SST are present + +sst.sd SST and slice differentiator (SD) are present + +sst.sd;mapped\_sst SST, SD and mapped configured SST are present + +sst.sd;mapped\_sst.mapped\_sd SST, SD, mapped configured SST and mapped configured SD are present + +<pdp\_type>: string type. Indicates the type of the PDU session. Specifies the type of packet data protocol. + +IP Internet Protocol (IETF STD 5 [103]). Indicates that the PDU session type is IPv4 only + +IPv6 Internet Protocol, version 6 (see RFC 2460 [106]). Indicates that the PDU session type is IPv6 only + +IPv4v6 Virtual <PDP\_type> introduced to handle dual IP stack UE capability. (See 3GPP TS 24.301 [83]). Indicates that the PDU session type is IPv4v6 + +Unstructured Transfer of Unstructured data to the Data Network via N6 (see 3GPP TS 23.501 [165]). Indicates that the PDU session type is Unstructured only + +Ethernet Ethernet protocol (IEEE 802.3). Indicates that the PDU session type is Ethernet only + +<preferred\_access\_type>: integer type. Indicates the preferred access type for the PDU session in 5GS, see 3GPP TS 24.526 [180]. + +0 indicates that the preferred access type is 3GPP access + +1 indicates that the preferred access type is non-3GPP access + +<Non-seamless\_non-3GPP\_offload\_indication>: integer type. + +0 indicates that the non-seamless non-3GPP offload is invalid + +1 indicates that the non-seamless non-3GPP offload is valid + +<Location\_criteria\_type>: string type. The route selection descriptor component value field may contain one or more types of location area and is encoded as shown in Figure 5.2.5 and Table 5.2.2 of 3GPP TS 24.526 [180]. + +<Time\_window\_type>: string type. The Time window type value field shall be encoded as a sequence of a Starttime field followed by a Stoptime field. The Starttime field is represented by the number of seconds since 00:00:00 on 1 January 1970 and is encoded as the 64-bit NTP timestamp format defined in RFC 5905 [183], where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The encoding of the Stoptime field is the same as the Starttime field. The Starttime field and the Stoptime field are separated by a dot. + +#### Implementation + +Optional. + +### 10.1.76 NAS connection release +CNASCREL + +**Table 10.1.76-1: +CNASCREL parameter command syntax** + +| Command | Possible response(s) | +|-----------|----------------------| +| +CNASCREL | +CME ERROR: <err> | + +#### Description + +This command triggers the MUSIM capable UE to request the network to release the NAS signalling connection for 3GPP access in EPS (see 3GPP TS 24.301 [83], clause 5.5.3.2 and clause 5.6.1), or 5GS (see 3GPP TS 24.501 [161], clause 5.5.1 and clause 5.6.1) due to activity on another USIM. When the TE sends this command to MT, the MT immediately returns OK and triggers the release of the NAS signalling connection. + +Refer clause 9.2 for possible <err> values. + +#### Implementation + +Optional. + +### 10.1.77 Reject paging +CREJPAG + +**Table 10.1.77-1: +CREJPAG parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CREJPAG=[<n>[, <rejpage_pgcause_unknown>[, <rejpage_pgcause_not_voice>[, <rejpage_pgcause_voice>]]] | +CME ERROR: <err><br><b>when <n>=2 and command successful</b><br>+CREJPAG:<br><rejpage_pgcause_unknown>, <rejpage_pgcause_not_voice>, <rejpage_pgcause_voice> | +| +CREJPAG? | +CREJPAG:<br><n>, <rejpage_pgcause_unknown>, <rejpage_pgcause_not_voice>, <rejpage_pgcause_voice> | +| +CREJPAG=? | +CREJPAG: (list of supported <n>s) , (list of supported <rejpage_pgcause_unknown>s) , (list of supported <rejpage_pgcause_not_voice>s) , (list of supported <rejpage_pgcause_voice>s) | + +## Description + +The set command controls the presentation of unsolicited result code +CREJPAG: <paging\_cause> when <n>=1 reporting the paging cause indication for which the MUSIM capable UE has received a page. The following cases are applicable in EPS (see 3GPP TS 24.301 [83], clause 5.5.1) and 5GS (see 3GPP TS 24.501 [161], clause 5.5.1). + +- a) UE receives page from a network that does not support paging cause indication for voice services; or +- b) UE receives page from a network that supports paging cause indication for voice services and page is not related to voice service; or +- c) UE receives page from a network that supports paging cause indication for voice services and page is related to voice service. + +When <n>=2, a special form of the set command +CREJPAG: + +<rejpage\_pgcause\_unknown>, <rejpage\_pgcause\_not\_voice>, <rejpage\_pgcause\_voice> enables the MUSIM capable UE to reject the paging request from the network in EPS (see 3GPP TS 24.301 [83], clause 5.6.1), and 5GS (see 3GPP TS 24.501 [161], clause 5.6.1). The TE sends this command (when <n>=2) to the MT in anticipation of MT receiving indication of paging from the network. + +The read command returns the current settings of <n> and indicates whether currently the paging request received from the network is set to be rejected or not for the different cases described above. + +Refer clause 9.2 for possible <err> values. + +The test command returns values of supported <n>s. + +## Defined values + +<n>: integer type + +- 0 Disable presentation of unsolicited result code +CREJPAG: <paging\_cause> +- 1 Enable presentation of unsolicited result code +CREJPAG: <paging\_cause> +- 2 Reject paging request from the network. There will be no change in the current setting of <n>, enabling or disabling of unsolicited result code +CREJPAG: <paging\_cause> + +<paging\_cause>: integer type; indicates the paging cause. + +- 0 Page is received from a network that does not support paging cause indication for voice services +- 1 Page is received from a network that supports paging cause indication for voice services and page is not related to voice service +- 2 Page is received from a network that supports paging cause indication for voice services and page is related to voice service + +<rejpage\_pgcause\_unknown>: integer type; indicates whether the paging request is set to be rejected when the UE receives page from a network that does not support paging cause indication for voice services. + +- 0 Paging request is not set to be rejected +- 1 Paging request is set to be rejected + +<rejpage\_pgcause\_not\_voice>: integer type; indicates whether the paging request is set to be rejected when the UE receives page from a network that supports paging cause indication for voice services and page is not related to voice service. + +- 0 Paging request is not set to be rejected +- 1 Paging request is set to be rejected + +<rejpage\_pgcause\_voice>: integer type; indicates whether the paging request is set to be rejected when the UE receives page from a network that supports paging cause indication for voice services and page is related to voice service. + +- 0 Paging request is not set to be rejected +- 1 Paging request is set to be rejected + +### Implementation + +Optional. + +## 10.1.78 Paging restrictions +CPAGRES + +**Table 10.1.78-1: +CPAGRES parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CPAGRES=<n>[, <paging_restrictions>[, <n number_of_restricted_cid>[, <cid>[, <cid>[, <cid>[, <cid>[, ...]]]]]]] | +CME ERROR: <err> | +| +CPAGRES? | +CPAGRES: <n>, <paging_restrictions>[, <number_of_restricted_cid>[, <cid>[, <cid>[, <cid>[, <cid>[, ...]]]]]]] | +| +CPAGRES=? | +CPAGRES: (list of supported <n>s), (list of supported <paging_restrictions>s), (list of supported <number_of_restricted_cid>s), (list of supported <cid>s) | + +### Description + +The set command controls the presentation of unsolicited result code +CPAGRES: <paging\_restrict\_result> when <n>=1 reporting that the paging restriction preferences specified by the MUSIM capable UE have been accepted by the network or not. When <n>=2, a special form of the set command enables the MUSIM capable UE to specify the paging restriction preferences to the network for 3GPP access in EPS (see 3GPP TS 24.301 [83], clause 5.5.3.2 and clause 5.6.1) and 5GS (see 3GPP TS 24.501 [161], clause 5.5.1 and clause 5.6.1). The paging restriction preferences can be set or removed. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current settings of <n> and paging restrictions. + +The test command returns values supported as a compound value. + +### Defined values + +<n>: integer type + +- 0 Disable presentation of unsolicited result code +CPAGRES: <paging\_restrict\_result> +- 1 Enable presentation of unsolicited result code +CPAGRES: <paging\_restrict\_result> +- 2 Reject paging request from the network. There will be no change in the current setting of <n>, enabling or disabling of unsolicited result code +CPAGRES: <paging\_restrict\_result> + +<paging\_restrict\_result>: integer type; indicates whether the requested paging restriction preferences of the UE are accepted or not, see 3GPP TS 24.301 [83], clause 9.9.3.66. + +- 0 indicates that paging restriction is rejected +- 1 indicates that paging restriction is accepted + +<paging\_restrictions>: integer type; indicates the paging restriction preferences of the UE, see 3GPP TS 24.301 [83], clause 9.9.3.66, and 3GPP TS 24.501 [161], clause 9.11.3.77. + +- 0 indicates that paging is not restricted +- 1 indicates that all paging is restricted +- 2 indicates that all paging is restricted except for voice service +- 3 indicates that all paging is restricted except for specified PDN connection(s) in EPS or PDU session(s) in 5GS +- 4 indicates that all paging is restricted except for voice service and specified PDN connection(s) in EPS or PDU session(s) in 5GS + +<number\_of\_restricted\_cid>: integer type; indicates the number of <cid>s for which paging is restricted + +<cid>: integer type; A numeric parameter which specifies a particular EPS bearer context or a 5GS QoS flow. The <cid> parameter is local to the TE-MT interface and identifies only EPS bearer contexts or 5GS QoS flows which have been setup via AT command (see the +CGDCONT and +CGDSCONT commands). + +### Implementation + +Optional. + +## 10.1.79 Paging timing collision control +CPAGTCC + +**Table 10.1.79-1: +CPAGTCC parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------| +| +CPAGTCC=<n>[, <IMSI_offset>] | +CME ERROR: <err> | +| +CPAGTCC? | +CPAGTCC: <n>, <mobile_identity>[, <IMSI_offset>] | +| +CPAGTCC=? | +CPAGTCC: (list of supported <n>s) , (list of supported <mobile_identity>s), (list of supported <IMSI_offset>s) | + +### Description + +The set command controls the presentation of unsolicited result code + ++CPAGTCC: <mobile\_identity>[, <IMSI\_offset>] when <n>=1 reporting the mobile identity of the UE and the negotiated alternative IMSI value offset that have been specified by the network for a MUSIM capable UE that supports paging timing collision control. When <n>=2, a special form of the set command enables the MUSIM capable UE to specify the requested alternative IMSI offset value to the network for 3GPP access in EPS (see 3GPP TS 24.301 [83], clause 5.5.1.2 and clause 5.5.3.2). When the TE sends this command to MT, the MT immediately returns OK. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current settings of <n>, <mobile\_identity> and <IMSI\_offset>. + +The test command returns values supported as a compound value. + +### Defined values + +<n>: integer type + +- 0 Disable presentation of unsolicited result code ++CPAGTCC: <mobile\_identity>[, <IMSI\_offset>] +- 1 Enable presentation of unsolicited result code ++CPAGTCC: <mobile\_identity>[, <IMSI\_offset>] + +- 2 Specify the requested IMSI offset <IMSI\_offset> to the network in case of EPS. There will be no change in the current setting of <n>, enabling or disabling of unsolicited result code + +CPAGTCC: <mobile\_identity>[, <IMSI\_offset>] + +<mobile\_identity>: indicates the mobile identity information of the UE in EPS (see 3GPP TS 24.301 [83], clause 9.9.3.12) and 5GS (see 3GPP TS 24.501 [161], clause 9.11.3.4). + +<IMSI\_offset>: indicates a value that is used for calculating an alternative IMSI offset value that is used for deriving the paging occasion (see 3GPP TS 24.301 [83], clause 9.9.3.64). + +## Implementation + +Optional. + +## 10.1.80 DNS server address reporting +CDNSADD + +**Table 10.1.80-1: +CDNSADD parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------|---------------------------------------------| +| + CDNSADD<br>=[<reporting>] | | +| + CDNSADD? | + CDNSADD: <reporting> | +| + CDNSADD =? | + CDNSADD: (list of supported <reporting>s) | + +## Description + +The set command controls the presentation of DNS server address to the TE by an unsolicited result code + CDNSADD: <cid>, <DNS\_prim\_addr>, <DNS\_sec\_addr> when DNS server address is received from the network. + +Read command returns <reporting> which indicates whether reporting of DNS server address is enabled or disabled. When reporting is enabled, the parameters <DNS\_prim\_addr> and <DNS\_sec\_addr> indicate the most recently received DNS server addresses at the MT. When reporting is disabled, no DNS server address is provided. + +Test command returns values supported as a compound value. + +## Defined values + +<reporting>: integer type. Enables and disables reporting of DNS server address received from the network. + +0 disable reporting + +1 enable reporting + +<cid>: integer type; specifies a particular non secondary PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands (see the +CGDCONT and +CGDSCONT commands). + +<DNS\_prim\_addr>: string type; shows the IP address of the primary DNS server. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of + CDNSADD. + +<DNS\_sec\_addr>: string type; shows the IP address of the secondary DNS server. + +When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of + CDNSADD. + +**Implementation** + +Optional. + +**10.1.81 Access domain selection preference for MO SMS +CADSMS****Table 10.1.81-1: +CADSMS parameter command syntax** + +| Command | Possible Response(s) | +|--------------------------------|--------------------------------------------------------------| +| +CADSMS=[<access_domain_pref>] | | +| +CADSMS? | +CADSMS: <access_domain_pref> | +| +CADSMS=? | +CADSMS: (list of currently supported <access_domain_pref>s) | + +**Description** + +The set command is used to specify the preferred access domain for the MT to use for MO SMS over NAS messages when the UE supports non-3GPP access in 5GS and a 3GPP access (e.g., in EPS or 5GS). + +The read command returns the currently selected access domain preference. + +The test command returns the supported access domain preferences as a compound value. + +**Defined values** + +<access\_domain\_pref>: integer type; indicates the access domain preference for MO SMS over NAS messages. + +- 0 a 3GPP access preferred, non-3GPP access in 5GS is used if no 3GPP access available +- 1 non-3GPP access in 5GS preferred, a 3GPP access is used if no non-3GPP access available + +**Implementation** + +Optional. + +This command is only applicable to UEs supporting a 3GPP access and non-3GPP access in 5GS. + +**10.1.82 5G ProSe UE-to-network Relay Authentication Setting +C5GPU2NRAUTHS****Table 10.1.82-1: +C5GPU2NRAUTHS parameter command syntax** + +| Command | Possible response(s) | +|--------------------|------------------------------------------| +| +C5GPU2NRAUTHS=<n> | +CME ERROR: <err> | +| +C5GPU2NRAUTHS? | +C5GPU2NRAUTHS: <n> | +| +C5GPU2NRAUTHS=? | +C5GPU2NRAUTHS: (list of supported <n>s) | + +**Description** + +The set command controls the presentation of an unsolicited result code +C5GPU2NRAUTH: <rmid>, <len>, <eap\_msg> which will be displayed on receiving an authentication message in the form of Extensible Authentication Protocol (EAP) message from network during a UE-initiated authentication and key agreement procedure for 5G ProSe UE-to-network relay. The purpose of the UE-initiated authentication and key agreement procedure for 5G ProSe UE-to-network relay is to enable the data network (DN) to authenticate and authorize the upper layers of 5G ProSe remote UE. This procedure happens through EAP as specified in IETF RFC 3748 [32] and 3GPP TS 24.501 [161] clause 5.5.4. + +There can be several sessions of exchange of an EAP-request and EAP-response message for the DN to complete the authentication and authorization. + +Read command returns the current setting of value <n>. + +Test command returns the range of supported <n>. + +#### Defined values + +<n>: integer type. Enables or disables reporting of authentication indication from network consisting of the EAP-message for a particular <rmid>. + +0 disable reporting. + +1 enable reporting. + +<rmid>: integer type, identifies a particular 5G ProSe remote UE. The <rmid> parameter is local to the TE-MT interface. + +<len>: integer type, indicates the length of the EAP message content. It can be of max 1500 according to 3GPP TS 24.501 [161] clause 9.11.2.2. + +<eap\_msg>: string type in hexadecimal format, consists of the EAP message from network, as defined in IETF RFC 3748 , IETF RFC 4187 and IETF RFC 5448. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +### 10.1.83 5G ProSe UE-to-network Relay Authentication Response +C5GPU2NRAUTHR + +**Table 10.1.83-1: +C5GPU2NRAUTHR action command syntax** + +| Command | Possible response(s) | +|---------------------------------------|----------------------| +| +C5GPU2NRAUTHR=<rmid>,<len>,<eap_msg> | +CME ERROR: <err> | +| +C5GPU2NRAUTHR=? | | + +#### Description + +Execution command allows the UE to send the EAP-response message to the EAP-request made by network for a particular 5G ProSe remote UE. The EAP-request message is received through the unsolicited result code +C5GPU2NRAUTH. The response to the execution command only indicates if the EAP-response message has been successfully sent to lower layers or not. + +NOTE: Calculating the EAP response for the request received can be implementation specific. + +#### Defined values + +<rmid>: integer type, identifies a particular 5G ProSe remote UE. The <rmid> parameter is a local to the TE-MT interface. + +<len>: integer type, indicates the length of the EAP message content. It can be of max 1500 according to 3GPP TS 24.501 [161] clause 9.11.2.2. + +<eap\_msg>: string type in hexadecimal format, consists of the EAP message from 5G ProSe remote UE as defined in IETF RFC 3748 , IETF RFC 4187 and IETF RFC 5448. This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +## 10.1.84 ECS Configuration information +CECSADDRCONF + +**Table 10.1.84-1: +CECSADDRCONF parameter command syntax** + +| Command | Possible response(s) | +|-----------------|-----------------------------------------------------| +| +CECSCONF=[<n>] | +CME ERROR: <err> | +| +CECSCONF? | +CECSCONF: <n>,<ECSConf_info_length>,<ECSConf_info> | +| +CECSCONF=? | +CECSCONF: (list of supported <n>s) | + +### Description + +The set command controls the presentation of ECS Configuration information to the TE by an unsolicited result code +CECSCONFU: <ECSConf\_info\_length>,<ECSConf\_info> when there is a change in the ECS Configuration information stored at the MT. For each ECS, the ECS Configuration information consists of an ECS FQDN, ECS IP Address, ECSP ID, and/or Spatial Validity Conditions, as specified in 3GPP TS 23.558 [187], clause 8.3.2. If <ECSConf\_info\_length> has a value of zero or is omitted, and <ECSConf\_info> consists of an empty string, no ECS Configuration information is stored on the MT. + +Read command returns <n> which indicates whether requesting ECS Configuration information is enabled or disabled. The read command also returns the current values of <ECSConf\_info\_length> and <ECSConf\_info> if available. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type. + +- 0 disable unsolicited result code +CECSCONFU: <ECSConf\_info\_length>,<ECSConf\_info> +- 1 enable unsolicited result code +CECSCONFU: <ECSConf\_info\_length>,<ECSConf\_info> + +<ECSConf\_info\_length>: integer type; indicates the number of octets of the <ECSConf\_info> information element. + +If the value is zero or is omitted, no ECS Configuration information is stored on the MT. + +<ECSConf\_info>: string type in hexadecimal format; indicates the ECS Configuration Information for one or more ECSs, where each ECS Configuration Information consists of an ECS address, spatial validity conditions, and an ECS provider identifier. The <ECSConf\_info> is encoded as the value part of the ECS information element in 3GPP TS 24.501 [161], clause 9.11.4.34, followed by the ECSP ID encoded as a UTF-8 string as described in 3GPP TS 24.008 [8]. This parameter shall not be subject to conventional character conversion as per +CSCS. + +If the value is an empty string (""), no ECS Configuration information is stored on the MT. + +**Implementation** + +Optional. + +## 10.1.85 5GS network registration status over non-3GPP access +C5GREGN3GPP + +**Table 10.1.85-1: +C5GREGN3GPP parameter command syntax** + +| Command | Possible response(s) | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +C5GREGN3GPP=<n>] | +CME ERROR: <err> | +| +C5GREGN3GPP? | <b>when <n>=0, 1, 2, or 3 and command successful:</b><br>+C5GREGN3GPP: <n>,<stat>[, <Allowed_NSSAI_length>, <Allowed_NSSAI>[, <cause_type>, <reject_cause>]] | +| +C5GREGN3GPP=? | +C5GREGN3GPP: (list of supported <n>s) | + +**Description** + +The set command controls the presentation of an unsolicited result code +C5GREGN3GPP: <stat> when <n>=1 and there is a change in the MT's network registration status in 5GS over non-3GPP access, or unsolicited result code +C5GREGN3GPP: <stat>[, <Allowed\_NSSAI\_length>, <Allowed\_NSSAI>] when <n>=2 and there is a change of the allowed NSSAI for non-3GPP access. The value <n>=3 further extends the unsolicited result code with [, <cause\_type>, <reject\_cause>], when available, when the value of <stat> changes. + +Refer clause 9.2 for possible <err> values. + +The read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. The parameters <Allowed\_NSSAI\_length>, <Allowed\_NSSAI>, if available, are returned only when <n>=2 and MT is registered in the network. The parameters [, <cause\_type>, <reject\_cause>], if available, are returned when <n>=3. + +Test command returns values supported as a compound value. + +**Defined values** + +<n>: integer type + +- 0 disable network registration unsolicited result code +- 1 enable network registration unsolicited result code +C5GREGN3GPP: <stat> +- 2 enable network registration and NSSAI information unsolicited result code ++C5GREGN3GPP: <stat>[, <Allowed\_NSSAI\_length>, <Allowed\_NSSAI>] +- 3 enable network registration, NSSAI information and 5GMM cause value information unsolicited result code ++C5GREGN3GPP: <stat>[, <Allowed\_NSSAI\_length>, <Allowed\_NSSAI>[, <cause\_type>, <reject\_cause>]] + +<stat>: integer type; indicates the 5GS network registration status over non-3GPP access. + +- 0 not registered, MT is not currently searching an operator to register to +- 1 registered, home network +- 2 not registered, but MT is currently trying to attach or searching an operator to register to +- 3 registration denied +- 4 unknown (e.g. out of non-3GPP access coverage) + +- 5 registered, roaming +- 6 registered for emergency services + +<Allowed\_NSSAI\_length>: integer type; the Terminal Adaptor (TA) can determine the value by parsing the <Allowed\_NSSAI> parameter. + +<Allowed\_NSSAI>: string type in hexadecimal format. Dependent of the form, the string can be separated by dot(s), semicolon(s) and colon(s). This parameter indicates the list of allowed S-NSSAIs for non-3GPP access received from the network. The <Allowed\_NSSAI> is coded as a list of <S-NSSAI>s separated by colons. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<cause\_type>: integer type; indicates the type of <reject\_cause>. + +- 0 Indicates that <reject\_cause> contains an 5GMM cause value, see 3GPP TS 24.501 [161] Annex A. +- 1 Indicates that <reject\_cause> contains a manufacturer-specific cause. + +<reject\_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by <cause\_type>. + +## Implementation + +Optional. + +## 10.1.86 5GS network register or deregister over non-3GPP access +C5GRDN3GPP + +**Table 10.1.86-1: +C5GRDN3GPP parameter command syntax** + +| Command | Possible Response(s) | +|---------------------|-------------------------------------------| +| +C5GRDN3GPP=<state> | +CME ERROR: <err> | +| +C5GRDN3GPP? | +C5GRDN3GPP: <state> | +| +C5GRDN3GPP=? | +C5GRDN3GPP: (list of supported <state>s) | + +## Description + +The execution command is used to register the MT to, or deregister the MT from, 5GS network over non-3GPP access. If the MT is already in the requested state, the command is ignored and the OK response is returned. If the requested state cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer clause 9.2 for possible <err> values. + +Any active PDP contexts will be automatically deactivated when the registration state changes to deregistered. + +The read command returns the current 5GS registration state over non-3GPP access. + +The test command is used for requesting information on the supported 5GS registration states over non-3GPP access. + +## Defined values + +<state>: integer type; indicates the state of 5GS registration over non-3GPP access + +- 0 deregistered +- 1 registered + +## Implementation + +Optional. + +## 10.1.87 Define MBS session context +CMSCONT + +**Table 10.1.87-1: +CMSCONT parameter command syntax** + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMSCONT=<cid>,<MBS_session_id_type>,<MBS_session_id>,<MBS_operation> | +CME ERROR: <err> | +| +CMSCONT? | [+CMSCONT: <cid>,<MBS_session_id>,<MBS_session_id_type>,<MBS_operation>]<br>[<CR><LF>+CMSCONT: <cid>,<MBS_session_id>,<MBS_session_id_type>,<MBS_operation>]<br>[...] | +| +CMSCONT=? | +CMSCONT: (range of supported <cid>s) , (range of supported <MBS_session_id>s) , (list of supported <MBS_session_id_type>s) , (list of supported <MBS_operation>s) | + +### Description + +The set command allows the TE to specify the MBS session context <cid>, <MBS\_session\_id>, <MBS\_session\_id\_type> and <MBS\_operation> for a QoS flow (see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]). Refer clause 9.2 for possible <err> values. + +The read command returns the current settings for each defined MBS session. + +The test command returns the ranges of the supported parameters as compound values. + +### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<MBS\_session\_id\_type>: integer type; indicates the type of the MBS session ID + +- 0 Temporary Mobile Group Identity (TMGI) +- 1 Source specific IP multicast address for IPv4 +- 2 Source specific IP multicast address for IPv6 + +<MBS\_session\_id>: string type. For IPv4 and IPv6 multicast addresses, the <MBS\_session\_id> has the form: "source\_IP\_address;destination\_IP\_address". For IPv4, the source\_IP\_address and destination\_IP\_address are given as dot-separated numeric (0-255) parameters on the form: "a1.a2.a3.a4". For IPv6, the source\_IP\_address and destination\_IP\_address are given as dot-separated numeric parameters on the form: "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16". For TMGI, the string is in hex format (refer 3GPP TS 23.003 [7], clause 30.2). + +<MBS\_operation>: integer type; indicates the MBS operations + +- 0 Join MBS session +- 1 Leave MBS session + +## 10.1.88 MBS session read dynamic parameters +CMSRDP + +**Table 10.1.88-1: +CMSRDP action command syntax** + +| Command | Possible response(s) | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMSRDP[=<cid>] | <p>[+CMSRDP: <cid>, <tmgi>, <MBS_TAI_list>, <MBS_CGI_list>, <Source_IP>, <Destination_IP>, <MBS_start_time>, <MBS_timer>, <MSK_ID>, <MSK>, <MTK_ID>, <Enc_MTK>]</p> <p>[<CR><LF>+CMSRDP: <cid>, <tmgi>, <MBS_TAI_list>, <MBS_CGI_list>, <Source_IP>, <Destination_IP>, <MBS_start_time>, <MBS_timer>, <MSK_ID>, <MSK>, <MTK_ID>, <Enc_MTK>]</p> <p>[...]</p> | +| +CMSRDP=? | +CMSRDP: (list of <cid>s associated with active MBS sessions) | + +### Description + +<cid>, <tmgi>, <MBS\_TAI\_list>, <MBS\_CGI\_list>, <Source\_IP>, <Destination\_IP>, <MBS\_start\_time>, <MBS\_timer>, <MSK\_ID>, <MSK>, <MTK\_ID>, <Enc\_MTK> for the active MBS sessions associated with <cid>. + +If the parameter <cid> is omitted, the MBS session parameters for all active MBS sessions are returned. + +The test command returns a list of <cid>s associated with active MBS sessions. + +### Defined values + +<cid>: integer type; specifies a particular QoS flow definition, EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<tmgi>: string type in hex format; value is the Temporary Mobile Group Identity allocated to a particular MBS session. Refer 3GPP TS 23.003 [7], clause 30.2. + +<MBS\_TAI\_list>: string type in hex format; encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161] clause 9.11.3.9. + +<MBS\_CGI\_list>: string type in hex format; encoded as the length and the value part of the NR CGI list in the Requested MBS container information element as specified in 3GPP TS 24.501 [161] clause 9.11.4.31. + +<Source\_IP>: string type; indicates the IP unicast address used as the source address of the MBS session (see 3GPP TS 24.501 [161] clause 9.11.4.31). The string is given as dot-separated numeric (0-255) parameters. + +<Destination\_IP>: string type; indicates the IP multicast address used as destination address for the MBS session (see 3GPP TS 24.501 [161] clause 9.11.4.31). The string is given as dot-separated numeric (0-255) parameters. + +<MBS\_start\_time>: string type in format "yy/MM/dd,hh:mm:ss±zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone; indicates the time when the MBS session starts, see 3GPP TS 24.501 [161] clause 9.11.4.31. + +<MBS\_timer>: string type; one byte in an 8 bit format; indicates the back-off timer associated with the MBS session, see 3GPP TS 24.501 [161] clause 9.11.4.31. The timer value is coded as one byte (octet 2) of the GPRS Timer information element coded as bit format (e.g. "01000011" equals 3 decihours or 18 minutes). For the coding and the value range, see the GPRS Timer IE in 3GPP TS 24.008 [8]. + +<MSK\_ID>: string type in hex format; indicates the MBS service key ID as defined in 3GPP TS 33.246 [188]. + +<MSK>: string type in hex format; indicates the MBS service key as defined in 3GPP TS 33.246 [188]. + +<MTK\_ID>: string type in hex format; indicates the MBS traffic key ID as defined in 3GPP TS 33.246 [188]. + +<Enc\_MTK>: string type in hex format; indicates the encrypted MBS traffic key as defined in 3GPP TS 33.246 [188]. + +### Implementation + +Optional. + +## 10.1.89 MBS session status reporting +CMSSR + +**Table 10.1.89-1: +CMSSR parameter command syntax** + +| Command | Possible response(s) | +|----------------|----------------------------------| +| +CMSSR=[ <n> ] | +CME ERROR: <err> | +| +CMSSR? | +CMSSR: <n> | +| +CMSSR=? | +CMSSR: (list of supported <n>s) | + +### Description + +Set command controls the presentation of MBS unsolicited result code + ++CMSSR: <cid>, <tmgi>, <MBS\_decision>, <MBS\_reject\_cause>, <MBS\_TAI\_list>, <MBS\_CGI\_list>, <Source\_IP>, <Destination\_IP>, <MBS\_start\_time>, <MBS\_timer>, <MSK\_ID>, <MSK>, <MTK\_ID>, <Enc\_MTK> reporting the MBS session status. + +Read command returns the current MBS unsolicited result code settings in the MT. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type + +- 0 Disable presentation of the unsolicited result code +CMSSR. +- 1 Enable presentation of the unsolicited result code +CMSSR. + +<cid>: integer type; specifies a particular QoS flow definition, EPS Traffic Flows definition and a PDP Context definition (see the +CGDCONT and +CGDSCONT commands). + +<tmgi>: string type in hex format; value is the Temporary Mobile Group Identity allocated to a particular MBS session. Refer 3GPP TS 23.003 [7], clause 30.2. + +<MBS\_decision>: integer type; indicates the network decision to a particular MBS session. Refer 3GPP TS 24.501 [161], clause 9.11.4.31. + +- 0 MBS service area update +- 1 MBS join is accepted +- 2 MBS join is rejected +- 3 Remove UE from MBS session + +<MBS\_reject\_cause>: integer type; indicates the reason of rejecting the MBS session join request or the reason of removing the UE from the MBS session, see 3GPP TS 24.501 [161] clause 9.11.4.30. + +- 0 No additional information provided +- 1 Insufficient resources +- 2 User is not authorized to use MBS service + +- 3 MBS session has not started or will not start soon +- 4 User is outside of local MBS service area +- 5 Session context not found +- 6 MBS session is released + +<MBS\_TAI\_list>: string type in hex format; encoded as the length and the value part of the 5GS Tracking area identity list information element as specified in 3GPP TS 24.501 [161] clause 9.11.3.9. + +<MBS\_CGI\_list>: string type in hex format; encoded as the length and the value part of the NR CGI list in the Requested MBS container information element as specified in 3GPP TS 24.501 [161] clause 9.11.4.31. + +<Source\_IP>: string type; indicates the IP unicast address used as the source address of the MBS session (see 3GPP TS 24.501 [161] clause 9.11.4.31). The string is given as dot-separated numeric (0-255) parameters. + +<Destination\_IP>: string type; indicates the IP multicast address used as destination address for the MBS session (see 3GPP TS 24.501 [161] clause 9.11.4.31). The string is given as dot-separated numeric (0-255) parameters. + +<MBS\_start\_time>: string type in hex format; indicates the time when the MBS session starts, see 3GPP TS 24.501 [161] clause 9.11.4.31. + +<MBS\_timer>: integer type; indicates the back-off timer associated with the MBS session, see 3GPP TS 24.501 [161] clause 9.11.4.31. + +<MSK\_ID>: string type in hex format; indicates the MBS service key ID as defined in 3GPP TS 33.246 [188]. + +<MSK>: string type in hex format; indicates the MBS service key as defined in 3GPP TS 33.246 [188]. + +<MTK\_ID>: string type in hex format; indicates the MBS traffic key ID as defined in 3GPP TS 33.246 [188]. + +<Enc\_MTK>: string type in hex format; indicates the encrypted MBS traffic key as defined in 3GPP TS 33.246 [188]. + +## Implementation + +Optional + +## 10.1.90 Information for reflective QoS for ESP +CIRQE + +**Table 10.1.90-1: +CIRQE parameter command syntax** + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| +CIRQE=<cid> [, <mode>, <protocol number (ipv4) / next header (ipv6)>, <local_address>, <remote_address>, <DL_IPsec_SA_SPI>, <UL_IPsec_SA_SPI> [, <local_UDP_port>, <remote_UDP_port>]] | +CME ERROR: <err> | +| +CIRQE=? | | + +## Description + +This command allows the TE to provide information about an uplink IP security (IPSec) security association (SA) corresponding to a downlink IPsec SA, in the TE, for the reflective QoS for ESP, along with other required information for an UL packet filter of a derived QoS rule for ESP, see 3GPP TS 24.501 [161], to TA/MT, depending whether the UDP encapsulation of ESP packets as specified in IETF RFC3948 [189] is used. + +A special form of the set command, +CIRQE=<cid> indicates that no uplink IPsec SA corresponds to any downlink IPsec SA for the particular <cid>. + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<cid>: integer type, specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +<mode>: integer type, identifies mode of provided information: + +- 1 a new association between the uplink IPsec SA and the downlink IPsec SA is created. +- 2 an existing association between the uplink IPsec SA and the downlink IPsec SA is removed. + +<protocol number (ipv4) / next header (ipv6)>: integer type, indicating the next level protocol, with value range from 0 to 255, where value 50 (decimal) indicates "ESP", value 17 (decimal) indicates "UDP". When <protocol number (ipv4) / next header (ipv6)> is set to "UDP", the UDP encapsulation of ESP packets as specified in IETF RFC3948 [189] is used for user data packets of the downlink and uplink IPsec SAs. + +<local\_address>: string type, given as dot-separated numeric (0-255) parameters which indicate a local address, in the form of: + +- "a1.a2.a3.a4", for IPv4; or +- "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16", for IPv6. + +<remote\_address>: string type, given as dot-separated numeric (0-255) parameters which indicate a remote address, in the form of: + +- "a1.a2.a3.a4", for IPv4; or +- "a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16", for IPv6. + +<DL\_IPsec\_SA\_SPI>: string type, contains an SPI of the downlink IPsec SA, encoded using eight hexadecimal digits. The first digit is the most significant digit. + +<UL\_IPsec\_SA\_SPI>: string type, contains an SPI of the uplink IPsec SA, encoded using eight hexadecimal digits. The first digit is the most significant digit. + +<local\_UDP\_port>: integer type, with value range from 0 to 65535, which indicates a local UDP port. When the <protocol number (ipv4) / next header (ipv6)> indicates "UDP" then the <local\_UDP\_port> parameter is present otherwise the <local\_UDP\_port> parameter is absent. + +<remote\_UDP\_port>: integer type, with value range from 0 to 65535, which indicates a remote UDP port. When the <protocol number (ipv4) / next header (ipv6)> indicates "UDP" then the <remote\_UDP\_port> parameter is present otherwise the <remote\_UDP\_port> parameter is absent. + +### Implementation + +Optional. + +## 10.1.91 Non3gpp QoS assistance information read dynamic parameters +CN3QAIRDP + +**Table 10.1.91-1: + CN3QAIRDP action command syntax** + +| Command | Possible Response(s) | +|--------------------|----------------------------------------------------| +| +CN3QAIRDP [<cid>] | [+CN3QAIRDP: <cid>[, <N3QAI>]<br>[...]] | +| +CN3QAIRDP=? | +CN3QAIRDP: (list of <cid>s associated with active | + +| Command | Possible Response(s) | +|---------|----------------------| +| | contexts) | + +### Description + +The execution command returns the N3QAI information (see 3GPP TS 24.501 [161]) associated to the provided context identifier <cid>. + +If the parameter <cid> is omitted, the N3QAI information for all active PDP contexts are returned. + +The test command returns a list of <cid>s associated with all active PDP contexts. + +### Defined values + +<cid>: integer type; specifies a particular PDP Context definition for the PDU session (see the +CGDCONT and +CGDSCONT commands). + +<N3QAI>: string type; coded as octet 4 to x of 3GPP TS 24.501 [161] figure 9.11.4.36.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. + +## 10.1.92 Non3gpp delay budget +CN3DB + +**Table 10.1.92-1: +CN3DB parameter command syntax** + +| Command | Possible Response(s) | +|-------------------------------------|----------------------| +| +CN3DB=<cid>,<non3gpp_delay_budget> | +CME ERROR: <err> | +| +CN3DB=? | | + +### Description + +The set command allows the TE to provide the non-3GPP delay budget information (see 3GPP TS 24.501 [161]) associated to the provided context identifier <cid>. + +If the parameter <cid> is omitted, the N3QAI information for all active PDP contexts are returned. + +A special form of the set command, +CN3DB=<cid> indicates that no non-3GPP delay budget information provided for the particular <cid>. + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<cid>: integer type; specifies a particular PDP Context definition for the PDU session (see the +CGDCONT and +CGDSCONT commands). + +<non3gpp\_delay\_budget>: string type; coded as octet 4 to x of 3GPP TS 24.501 [161] figure 9.11.4.37.1. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. + +## 10.2 Modem compatibility commands + +### 10.2.0 General + +This clause describes how existing AT commands, designed for use with a modem, may be used to control a Packet Domain MT. This is to provide backwards compatibility with existing communications software. For new applications it is recommended that the Packet Domain-specific commands, described in previous clauses, be used. + +### 10.2.1 MT originated PDP context activation + +#### 10.2.1.0 General + +In this mode of operation, the MT behaves like an originating modem and accepts the normal V.250 commands associated with placing and clearing a call. If Packet Domain-specific configuration commands are required, they may be sent to the MT as part of the modem initialization commands. + +#### 10.2.1.1 Request packet domain service 'D' + +**Table 130: D command syntax** + +| Command | Possible Response(s) | +|---------------------------------------------------------------------------|----------------------| +| D*<GPRS_SC>[* [<called address>] [* [<L2P>] [* [<cid>[, <cid>[, ...]]]]]# | CONNECT<br>ERROR | + +#### Description + +This command causes the MT to perform whatever actions are necessary to establish communication between the TE and the external PDN. + +The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start the specified layer 2 protocol. The MT shall return CONNECT to confirm acceptance of the command prior to entering the V.250 online data state. No further commands may follow on the AT command line. + +The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in clause 9 (for IP) of 3GPP TS 27.060 [34]. PS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed using the +CGATT and +CGACT commands. + +When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the MT shall enter V.250 command state and return the NO CARRIER final result code. + +If <called address> is supported and provided, the MT shall automatically set up a virtual call to the specified address after the PDP context has been activated. + +If <L2P> and <cid> are supported, their usage shall be the same as in the +CGDATA command. The +CGDCONT, +CGQREQ, etc. commands may be used in the modem initialization AT command string to set values for PDP type, APN, QoS etc.. + +If <L2P> is not supported or is supported but omitted, the MT shall use a layer 2 protocol appropriate to the PDP type. + +If <cid> is not supported or is supported but omitted, the MT shall attempt to activate the context using: + +- any information provided by the TE during the PDP startup procedure, e.g. the TE may provide a PDP type and/or PDP address to the MT; +- a priori knowledge, e.g. the MT may implement only one PDP type; or +- using the 'Empty PDP type' (3GPP TS 24.008 [8]). (No PDP address or APN shall be sent in this case and only one PDP context subscription record shall be present in the HLR for this subscriber.) + +This command may be used in both normal and modem compatibility modes. + +NOTE: The dial string conforms to the syntax specified in 3GPP TS 22.030 [19]. + +#### Defined values + +<GPRS\_SC>: (GPRS Service Code) a string of digits (value 99) which identifies a request to use the Packet Domain service. + +<called\_address>: a string that identifies the called party in the address space applicable to the PDP. For communications software that does not support arbitrary characters in the dial string, a numeric equivalent may be used. Also, the character comma ',' may be used as a substitute for the character period '.'. + +<L2P>: a string which indicates the layer 2 protocol to be used (see +CGDATA command). For communications software that does not support arbitrary characters in the dial string, the following numeric equivalents shall be used: + +| | | +|-------|-----------------| +| 0 | NULL (Obsolete) | +| 1 | PPP | +| 2 | PAD (Obsolete) | +| 3 | X25 (Obsolete) | +| 9yyyy | M-xxxx | + +Other values are reserved and will result in an ERROR response + +<cid>: a string of digits which specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). + +#### Implementation + +Optional if the +CGDATA command is supported. If the D command is provided, then support for <called\_address>, <L2P> and <cid> are optional. If they are not supported but values are provided by the TE, the values shall be ignored and this shall not constitute an error. + +### 10.2.1.2 Request packet domain IP service 'D' + +**Table 131: D command syntax** + +| Command | Possible Response(s) | +|--------------------------------------------|----------------------| +| D*<GPRS_SC_IP>[*<cid>[, <cid>[, . . . ]]]# | CONNECT<br>ERROR | + +#### Description + +This command causes the MT to perform whatever actions are necessary to establish communication between the TE and the external PDN. + +The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start the specified layer 2 protocol. The MT shall return CONNECT to confirm acceptance of the command prior to entering the V.250 online data state. No further commands may follow on the AT command line. + +The detailed behaviour after the online data state has been entered is described briefly in clause 9, for IP, of 3GPP TS 27.060 [34]. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed using the +CGATT and +CGACT commands. + +When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, the MT shall enter V.250 command state and return the NO CARRIER final result code. + +If <cid> is supported, its usage shall be the same as in the +CGDDATA command. The +CGDDCONT, +CGQREQ, etc. commands may be used in the modem initialization AT command string to set values for PDP type, APN, QoS etc. + +If <cid> is not supported or is supported but omitted, the MT shall attempt to activate the context using: + +- (a) any information provided by the TE during the PDP startup procedure, e.g. the TE may provide a PDP type and/or PDP address to the MT; +- (b) a priori knowledge, e.g. the MT may implement only one PDP type; or +- (c) using the 'Empty PDP type' (3GPP TS 24.008 [8]). (No PDP address or APN shall be sent in this case and only one PDP context subscription record shall be present in the HLR for this subscriber.) + +This command may be used in both normal and modem compatibility modes. + +NOTE. The dial string conforms to the syntax specified in 3GPP TS 22.030 [19]. + +#### Defined values + +<GPRS\_SC\_IP>: (GPRS Service Code for IP) a string of digits (value 98) which identifies a request to use the GPRS with IP (PDP types IP and PPP). + +<cid>: a string of digits which specifies a particular PDP context definition (see +CGDDCONT command). + +#### Implementation + +Optional if the +CGDDATA command is supported. If the D command is provided, then support for <cid> is optional. If it is not supported but a value is provided by the TE, the value shall be ignored and this shall not constitute an error. + +## 10.2.2 Network requested PDP context activation + +### 10.2.2.0 General + +In this mode of operation, the MT behaves like an answering modem and accepts the normal V.250 commands associated with answering a call. If Packet Domain-specific configuration commands are required, they may be sent to the MT as part of the modem initialization commands. + +The +CGAUTO command is used to select modem compatibility mode. + +### 10.2.2.1 Automatic response to a network request for PDP context activation 'S0' + +The V.250 'S0=n' (Automatic answer) command may be used to turn off (n=0) and on (n>0) the automatic response to a network request for a PDP context activation. + +When the 'S0=n' (n>0) command is received, the MT shall attempt to perform a PS attach if it is not already attached. Failure will result in ERROR being returned to the TE. Subsequently, the MT will announce a network request for PDP context activation by issuing the unsolicited result code RING to the TE, followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified. + +NOTE: The 'S0=n' (n=0) command does not perform an automatic PS detach. + +#### Implementation + +Optional. + +### 10.2.2.2 Manual acceptance of a network request for PDP context activation 'A' + +The V.250 'A' (Answer) command may be used to accept a network request for a PDP context activation announced by the unsolicited result code RING. The MT responds with CONNECT, enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified. It is an error to issue the 'A' command when there is no outstanding network request. + +**Implementation** + +Optional. + +**10.2.2.3 Manual rejection of a network request for PDP context activation 'H'** + +The V.250 'H' or 'H0' (On-hook) command may be used to reject a network request for PDP context activation announced by the unsolicited result code RING. The MT responds with OK. It is an error to issue the 'H' command when there is no outstanding network request. + +NOTE: This is an extension to the usage of the 'H' command that is described in ITU-T Recommendation V.250 [14]. + +**Implementation** + +Optional. + +# 11 Commands for VGCS and VBS + +## 11.0 General + +This clause defines commands that a TE may use to control a VGCS or VBS supporting MT. The requirements for the VGCS and VBS are included in the following specifications: + +- Voice Group Call service (VGCS): 3GPP TS 42.068 [55], 3GPP TS 43.068 [49] and 3GPP TS 44.068 [52]; +- Voice Broadcast Service (VBS): 3GPP TS 42.069 [56], 3GPP TS 43.069 [50] and 3GPP TS 44.069 [53]. + +It is anticipated that VGCS or VBS supporting MTs will vary widely in functionality. + +A comprehensive set of VGCS and VBS-specific commands is defined in clause 11.1 to provide the flexibility needed by the more complex MT. The commands use the extended information and error message capabilities described in this specification. + +For the simplest MTs, and for backwards compatibility with existing communications software, it is possible to control access to the VGCS and VBS using existing modem-compatible commands. A special dial-string syntax is defined for use with the D command. This "modem compatible" mode of operation is described in clause 11.2. + +## 11.1 Commands specific to MTs supporting the VGCS and VBS + +### 11.1.1 Accept an incoming voice group or voice broadcast call +CAJOIN + +**Table 132: +CAJOIN action command syntax** + +| Command | Possible Response(s) | +|-------------------------------|----------------------| +| +CAJOIN=<service>,<GId>,<GCA> | +CME ERROR: <err> | +| +CAJOIN=? | | + +**Description** + +The execute command accepts an incoming or ongoing voice group or voice broadcast call. Refer clause 9.2 for possible <err> values. + +See command +CALCC to get a list of current voice group or voice broadcast calls. + +**Defined values** + +<GId>: string of digits that specifies the group identification for the incoming voice group or voice broadcast call. + +<GCA>: string of digits that specifies the group call area identification for the incoming voice group or voice broadcast call. + +<service>: integer type (tele-service) + +17 voice group call + +18 voice broadcast call + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS or VBS is implemented. + +### 11.1.2 Reject an incoming voice group or voice broadcast call +CAREJ + +**Table 133: +CAREJ action command syntax** + +| Command | Possible Response(s) | +|------------------------------|----------------------| +| +CAREJ=<service>,<GId>,<GCA> | +CME ERROR: <err> | +| +CAREJ=? | | + +#### Description + +The execute command rejects an incoming voice group or voice broadcast call indicated by RING or +CRING, the command is applicable as long as the indication is pending. Refer clause 9.2 for possible <err> values. + +If the call is once rejected the RING or +CRING indication is not repeated to TE although the call is still running and notifications for the call are received. + +See command +CALCC to get a list of current voice group or voice broadcast calls. + +#### Defined values + +<GId>: string of digits that specifies the group identification for the incoming voice group or voice broadcast call. + +<GCA>: string of digits that specifies the group call area identification for the incoming voice group or voice broadcast call. + +<service>: integer type (tele-service) + +17 voice group call + +18 voice broadcast call + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS or VBS is implemented. + +### 11.1.3 Leave an ongoing voice group or voice broadcast call +CAHLD + +**Table 134: +CAHLD action command syntax** + +| Command | Possible Response(s) | +|----------|----------------------| +| +CAHLD | +CME ERROR: <err> | +| +CAHLD=? | | + +#### Description + +The execute command forces the MT to leave the active voice group or voice broadcast call without terminating it. The command is only applicable if the MT is in group receive mode. The MT returns to idle mode. Refer clause 9.2 for possible <err> values. + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS or VBS is implemented. + +### 11.1.4 Talker access for voice group call +CAPTT + +**Table 135: +CAPTT parameter command syntax** + +| Command | Possible Response(s) | +|---------------------------|-------------------------------------------------------------------| +| +CAPTT=[<mode>[, <time>]] | +CME ERROR: <err> | +| +CAPTT? | +CAPTT: <mode><br>+CME ERROR: <err> | +| +CAPTT=? | +CAPTT: (list of supported <mode>s) , (list of supported <time>s) | + +#### Description + +The execute command emulates the Push To Talk function for VGCS talker access. If the parameter <mode> is set to value "0" i.e. "RELEASED" the PTT key is assumed to be released immediately. If the parameter <mode> is set to value "1" i.e. "PUSHED" the PTT key is assumed to be pushed immediately for the period of <time> in seconds. If the command execution is repeated before the <time> expires the PTT timer will be loaded with the new <time> value and the PTT key remains "PUSHED" for the period of new <time> in seconds. + +If the parameter <mode> is set to value "2" i.e. "PUSHED" the PTT key is assumed to be pushed immediately for an infinite period of time and can be released by <mode> value 0. For <mode>=0 if the parameter <time> is issued it is ignored. + +If the PTT timer expires after <time> seconds during <mode> "PUSHED" an unsolicited result code +CAPTT: 0 is issued to the TE. + +Refer clause 9.2 for possible <err> values. + +The read command returns the current <mode>. + +The test command returns values supported as compound values. + +#### Defined values + +<mode>: integer type. + +- 0 status of the PTT key is RELEASED +- 1 status of the PTT key is PUSHED for a limited time by <time> in seconds +- 2 status of the PTT key is PUSHED for an infinite time + +<time>: integer type. + +3.255 this gives the time in seconds to wait before the PTT key is released, default value 10 + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS is implemented. + +### 11.1.5 Voice group call uplink status presentation +CAULEV + +**Table 136: +CAULEV parameter command syntax** + +| Command | Possible Response(s) | +|------------------|--------------------------------------------------| +| +CAULEV=[<mode>] | +CME ERROR: <err> | +| +CAULEV? | +CAULEV: <mode>, [<status>]<br>+CME ERROR: <err> | +| +CAULEV=? | +CAULEV: (list of supported <mode>s) | + +#### Description + +The set command enables or disables the presentation of uplink access status for an active VGCS call. When enabled the unsolicited result code +CAULEV: <status> is returned from MT to TE whenever the call uplink status changes. + +Refer clause 9.2 for possible <err> values. + +Read command returns the current uplink <status> and the selected <mode>. + +The test command returns values supported as a compound value. + +#### Defined values + +<mode>: integer type; status of unsolicited result code presentation. + +- 0 disabled +- 1 enabled + +<status>: integer type; network uplink access status. + +- 0 uplink free +- 1 uplink busy + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS is implemented. + +### 11.1.6 List current voice group and voice broadcast calls +CALCC + +**Table 137: +CALCC action command syntax** + +| Command | Possible response(s) | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CALCC=<mode> | [+CALCC: <GId>, <GCA>, <service>, <stat>, <dir>, <ack_flag>[, <priority>]]<br>[<CR><LF>+CALCC: <GId>, <GCA>, <service>, <stat>, <dir>, <ack_flag>[, <priority>]]<br>[...]<br>+CME ERROR: <err> | +| +CALCC=? | +CALCC: (list of supported <mode>s) | + +#### Description + +The set command returns for <mode>=1 the active voice group or voice broadcast call and for <mode>=0 a list of all current running voice group and voice broadcast calls for which the user has a subscription and the GId is activated on + +the SIM. If the command succeeds but no calls are available, OK response is returned. Refer clause 9.2 for possible <err> values. + +Test command returns the values supported as a compound value. + +#### Defined values + +<mode>: integer type. + +- 0 return a list of all current running voice group and voice broadcast calls for which the user has a subscription and the GId is activated on the SIM +- 1 return the active voice group or voice broadcast call + +<GId>: string of digits that specifies the group identification of the voice group or voice broadcast call. + +<GCA>: string of digits that specifies the group call area of the voice group or voice broadcast call. + +<service>: integer type (tele-service). + +- 17 voice group call +- 18 voice broadcast call + +<stat>: integer type (state of the call). + +- 0 active, i.e. user participating at the call as talker or listener +- 1 held, the call is running but put to background, notifications ignored +- 2 incoming (MT call), the user doesn't respond to notifications of this call yet + +<dir>: integer type (direction of the call). + +- 0 mobile originated (MO) call, the user is the originator of the call +- 1 mobile terminated (MT) call, the user is not the originator of the call + +<ack\_flag>: integer type; proposes that a predefined confirmation procedure is to be used after the call is ended. + +- 0 confirmation procedure is not required +- 1 confirmation procedure is required + +<priority>: integer type; identifies the priority level of the voice group or voice broadcast call. The values are specified in 3GPP TS 22.067 [54]. + +#### Implementation + +Optional. Recommended for an MT supporting AT commands only and VGCS or VBS is implemented. + +### 11.1.7 Voice group or voice broadcast call state attribute presentation +CACSP + +**Table 138: +CACSP parameter command syntax** + +| Command | Possible Response(s) | +|---------------|-----------------------------------------------------------------| +| +CACSP=<mode> | +CME ERROR: <err> | +| +CACSP? | +CACSP: <mode>[, <da>, <ua>, <comm>, <oi>]<br>+CME ERROR: <err> | +| +CACSP=? | +CACSP: (list of supported <mode>s) | + +## Description + +The set command enables or disables the presentation of unsolicited result code + ++CACSP: <da>, <ua>, <comm>, <oi> from MT to TE if the call control state attributes of the active voice group or voice broadcast call changes. + +Read command returns the current call control state attributes <da>, <ua>, <comm>, <oi> and selected <mode>. + +Refer clause 9.2 for possible <err> values. + +The test command returns values supported as a compound value. + +## Defined values + +<mode>: integer type; status of unsolicited result code presentation + +0 disabled + +1 enabled + +<da>: integer type. User connection in the downlink + +0 not attached + +1 attached + +<ua>: integer type. User connection in the uplink + +0 not attached + +1 attached + +<comm>: integer type. The MT assumes that communication with its peer entity is + +0 not enabled in both directions + +1 enabled in both directions + +<oi>: integer type. The MT assumes to be + +0 not the originator of the call + +1 the originator of the call + +## Implementation + +Optional. Recommended for a MT supporting AT commands only and VGCS or VBS is implemented. + +## 11.1.8 NCH support indication +CANCHEV + +**Table 139: +CANCHEV parameter command syntax** + +| Command | Possible Response(s) | +|-------------------|-------------------------------------------------| +| +CANCHEV=[<mode>] | +CME ERROR: <err> | +| +CANCHEV? | +CANCHEV: <status>, <mode><br>+CME ERROR: <err> | +| +CANCHEV=? | +CANCHEV: (list of supported <mode>s) | + +## Description + +The set command enables or disables the presentation of unsolicited result code +CANCHEV: <status> from MT to TE if the status of the network NCH support information changes. + +Read command returns in parameter <status> the network NCH support information in the selected cell and the selected <mode>. + +Refer clause 9.2 for possible <err> values. + +The test command returns values supported as a compound value. + +#### Defined values + +<mode>: integer type; status of unsolicited result code presentation + +- 0 disabled +- 1 enabled + +<status>: integer type; network NCH support information + +- 0 NCH not available +- 1 NCH available + +#### Implementation + +Optional. Recommended for a MT supporting AT commands only and VGCS or VBS is implemented. + +### 11.1.9 Originator to dispatcher information +COTDI + +**Table 140: +COTDI parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------|-----------------------------------------------------| +| +COTDI=<message>[, <OTDIE>[, <message>[, <OTDIE>]]] | +CME ERROR: <err> | +| +COTDI? | [+COTDI: <message>, <OTDIE>[, <message>, <OTDIE>]]] | +| +COTDI=? | +COTDI: (list of supported <message>s) | + +#### Description + +This command allows control of the Originator-to-Dispatcher Information and Compressed Originator-to-Dispatcher Information according to 3GPP TS 44.068 [52] and 3GPP TS 44.069 [53]. + +When <message> and <OTDIE> are both present the string specified in <OTDIE> is included in the corresponding group or broadcast control <message> as the value part of the Originator-to-Dispatcher Information Element or Compressed Originator-to-Dispatcher Information Element (as defined in 3GPP TS 44.068 [52] and 3GPP TS 44.069 [53]) into all subsequent messages of type <message>. If parameter <message> is present but parameter <OTDIE> is not present then the Originator-to-Dispatcher Information Element shall not be present in subsequent messages of type <message>. Refer clause 9.2 for possible <err> values. + +The read command returns the content of <message> and of <OTDIE>. If no <OTDIE> is available, no information text shall be returned. + +Test command returns values supported as a compound value. + +#### Defined values + +<message>: integer type + +- 0 SETUP message containing the outgoing Originator-to-Dispatcher Information Element + +- 1 IMMEDIATE SETUP 2 message containing the outgoing Compressed Originator-to-Dispatcher Information Element + +<OTDIE>: the Originator-to-Dispatcher Information Element or Compressed Originator-to-Dispatcher Information Element (as defined in 3GPP TS 44.068 [52] and 3GPP TS 44.069 [53]) in hexadecimal character format (for hexadecimal format, refer +CSCS). + +### Implementation + +Optional. + +## 11.1.10 Short data transmission during ongoing VGCS +CEPTT + +**Table 141: +CEPTT action command syntax** + +| Command | Possible response(s) | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------| +| +CEPTT=<mode>,<data>,<dataid>,<dist-param> | +CME ERROR: <err> | +| +CEPTT=? | +CEPTT: (list of supported <mode>s) , (list of supported <dataid>s) , (list of supported <dist-param>s) | + +### Description + +The execute command emulates the Short Data Transmission during ongoing VGCS according to 3GPP TS 42.068 [55] and 3GPP TS 43.068 [49]. + +The application indicator <mode> is used to identify whether the application data is an application-specific data or is a confirmation. The data identifier <dataid> is to provide a sequence number of the sending of application data. The value of the data identifier <dataid> is dependent on the value of the application indicator <mode>. If the application indicator <mode> indicates sending application data to the network, the data identifier <dataid> contains a number from the range between 0 and 15 which is generated by the mobile station. If the application indicator <mode> indicates sending confirmation of the reception of the application data, the data identifier <dataid> shall contain the data identifier which was received in the data identity sent by the previous sender. The distribution parameter <dist-param> contains information to which participants shall be transferred the short data. + +The response CEPTT string from the network to the other participants is returned in a subsequent unsolicited result code +CEPTT: <mode>,<data>,<dataid>,<dist-param>[, <number>]. + +Refer clause 9.2 for possible <err> values. + +Test command returns values supported as compound values. + +### Defined values + +<mode>: integer type. + +- 0 sending of application-specific data +- 1 confirmation of receiving application-specific data + +<data>: 9 bytes application-specific data in hexadecimal character format (for hexadecimal character format, refer +CSCS). + +<dataid>: integer type, a number from the range between 0 and 15. + +<dist-param>: integer type, a number from the range between 1 and 7. + +- 1 data shall be distributed only to network application +- 2 data shall be distributed only to dispatchers + +- 3 data shall be distributed to network application and to dispatchers +- 4 data shall be distributed to talkers and listeners +- 5 data shall be distributed to talkers and listeners and to network application +- 6 data shall be distributed to talkers and listeners and to dispatchers +- 7 data shall be distributed to network application, to talkers and listeners and to dispatchers + +<mode>: integer type. + +### Implementation + +Optional. + +## 11.1.11 Group Id prefixes capability +CGIPC + +**Table 11.1.11-1: +CGIPC action command syntax** + +| Command | Possible Response(s) | +|----------|-------------------------------------------| +| +CGIPC | +CGIPC: <status><br><br>+CME ERROR: <err> | +| +CGIPC=? | | + +### Description + +Execution command returns the MT Group Id prefix management capability, according to 3GPP TS 43.068 [49]. Refer clause 9.2 for possible <err> values. + +### Defined values + +<status>: integer type, value + +- 0 MT is not able to manage Group Id prefixes +- 1 MT is able to manage Group Id prefixes + +### Implementation + +Optional. + +## 11.2 Modem compatibility commands + +### 11.2.0 General + +This clause describes how existing AT commands, designed for use with a modem, may be used to control a VGCS or VBS supporting MT. This is to provide backwards compatibility with existing communications software. + +### 11.2.1 Request VGCS or VBS service 'D' + +**Table 141a: D command syntax** + +| Command | Possible Response(s) | +|-----------------------------------------------------------------------|----------------------| +| D*<SC <sub>1</sub> >[*<SC <sub>2</sub> >[*<SC <sub>3</sub> >]]#<GId>; | +CME ERROR: <err> | + +### Description + +This Dial command extension is a service request application according to 3GPP TS 22.030 [19]. No further commands may follow on the AT command line. + +#### Responses + +When the call has terminated, either as a result of an orderly termination or an error, the MT shall return the NO CARRIER final result code. + +Possible error responses include +CME ERROR: <err> when error is related to MT functionality. The requested service, GId and priority level are checked against the subscriptions of the user and the status of the GId stored on the SIM. In case if no subscription is available for this service, GId or priority level or the GId is deactivated an ERROR or +CME ERROR result code is returned. The requested Group Id prefix is not checked against subscription. The Group Id prefixes are not stored in the SIM/USIM card. If Service Code for Group Id prefix is used, but is not managed by MT, an ERROR or +CME ERROR result code is returned. See +CME ERROR extensions for VGCS, VBS and eMLPP in clause 9.2.3. + +Detailed error report of an unsuccessful originated call can be obtained with command Extended Error Report +CEER (if implemented). + +NOTE 1: The dial string conforms to the syntax specified in 3GPP TS 22.030 [19]. + +#### Defined values + +<SC<sub>1</sub>>: Service Code is a string of digits which identifies a request to use. + +17 Voice Group Call Service + +18 Voice Broadcast Service + +<SC<sub>2</sub>>: Service Code is a string of digits which identifies a request to use eMLPP priority. Service Code values for different priority levels are specified in 3GPP TS 22.030 [19]. + +<GId>: a string of digits that specifies the group identification of a called party as specified in 3GPP TS 43.068 [49]. + +<SC<sub>3</sub>>: a digit that specifies a Group Id prefix as specified in 3GPP TS 43.068 [49]. + +NOTE 2: <SC<sub>3</sub>> is only applicable when <SC<sub>1</sub>> defines Voice Group Call Service. + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS or VBS is implemented. + +### 11.2.2 Termination of an voice group or voice broadcast call 'H' + +The V.250 'H' or 'H0' (On-hook) command may be used to terminate an ongoing voice group or voice broadcast call. The MT responds with OK. It is an error to issue the 'H' command when there is no outstanding network request. + +It is an error to issue the 'H' command if the user is in group receive mode or the user is not the originator of the call and an ERROR or +CME ERROR result code is returned to the TE. Refer clause 9.2 for possible <err> values. + +NOTE: This is an extension to the usage of the 'H' command that is described in ITU-T Recommendation V.250 [14]. + +#### Implementation + +Mandatory for a MT supporting AT commands only and VGCS or VBS is implemented. + +#### 11.3 SIM commands supporting the VGCS and VBS + +### 11.3.1 VGCS subscriptions and GId status +CGCS + +**Table 142: +CGCS parameter command syntax** + +| Command | Possible response(s) | +|----------------------|--------------------------------------------------------------------------------------------| +| +CGCS=<GId>,<status> | +CME ERROR: <err> | +| +CGCS? | +CGCS: <GId>,<status><br>[<CR><LF>+CGCS: <GId>,<status><br>[...]]<br><br>+CME ERROR: <err> | +| +CGCS=? | +CGCS: (list of supported <GId>s) , (list of supported <status>s) | + +#### Description + +This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EF<sub>VGCS</sub> on the SIM. + +The read command returns all subscribed GIds in EF<sub>VGCS</sub> and their status in EF<sub>VGCS</sub> from the SIM. + +Refer clause 9.2 for possible <err> values. + +The test command returns the values supported by the UE as compound values. + +#### Defined values + +<GId> integer type, group Id as specified in 3GPP TS 22.030 [19] + +<status>: integer type, value + +0 deactivated + +1 activated + +#### Implementation + +Mandatory for a MT supporting AT commands only and supporting VGCS. + +### 11.3.2 VBS subscriptions and GId status +CBCS + +**Table 143: +CBCS parameter command syntax** + +| Command | Possible response(s) | +|----------------------|--------------------------------------------------------------------------------------------| +| +CBCS=<GId>,<status> | +CME ERROR: <err> | +| +CBCS? | +CBCS: <GId>,<status><br>[<CR><LF>+CBCS: <GId>,<status><br>[...]]<br><br>+CME ERROR: <err> | +| +CBCS=? | +CBCS: (list of supported <GId>s) , (list of supported <status>s) | + +#### Description + +This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EF<sub>VBS</sub> on the SIM. + +The read command returns all subscribed GIDs in EF<sub>VBS</sub> and their status in EF<sub>VBS</sub> from the SIM. + +Refer clause 9.2 for possible <err> values. + +The test command returns the values supported by the UE as compound values. + +#### Defined values + +<GID> integer type, group Id as specified in 3GPP TS 22.030 [19] + +<status>: integer type, value + +0 deactivated + +1 activated + +#### Implementation + +Mandatory for a MT supporting AT commands only and supporting VBS. + +## 11.4 Informative examples + +As supplementary services may be invoked and controlled using dial command according to 3GPP TS 22.030 [19]. + +Examples of voice group call service request usage: + +``` +ATD*17*753#500; (originate voice group call with the priority level 3) +OK (voice group call setup was successful) +``` + +``` +ATD*17*750*3#299; (originate voice group call for Group Id 299, with Group Id prefix 3 and priority level 0) +OK (voice group call setup was successful) +``` + +``` +ATD*17**6#599; (originate voice group call for Group Id 599, with Group Id prefix 6 and default priority selected by the network) +OK (voice group call setup was successful) +``` + +--- + +## 12 Commands for USIM application toolkit + +### 12.1 General + +If a UICC connected to an MT uses USIM Application Toolkit (USAT), some USAT features can be provided by the MT itself, whereas other features can be implemented in the TE. This applies especially to MTs with limited capabilities, where the user interface could be provided by the TE. + +If there are multiple entities inside the TE providing USAT services, for the purpose of this specification, the TE is visible as one entity handling AT commands and responses on the interface to the TA/MT, see figure 12.1-1. + +![Figure 12.1-1: Overview of the interfaces between TE, TA/MT and UICC for USAT. The diagram shows two blue rectangular blocks representing the TE/TA/MT and UICC components.](bb5e4bf4a5eeedff9a7db204a4488e86_img.jpg) + +Figure 12.1-1: Overview of the interfaces between TE, TA/MT and UICC for USAT. The diagram shows two blue rectangular blocks representing the TE/TA/MT and UICC components. + +**Figure 12.1-1: Overview of the interfaces between TE, TA/MT and UICC for USAT** + +The AT commands for definition of the USAT profiles and transmission of USAT proactive commands, USAT terminal responses and USAT envelope commands between the TE and UICC are specified in the subsequent clauses. + +Compared to APDUs, where the MT is the initiator, USAT defines logic where the UICC is the initiator of the USAT proactive commands and the MT sends responses to these commands. Due to that, USAT proactive commands are sent in unsolicited result codes, whereas the associated responses are transported in subsequent AT commands. + +## 12.2 Commands specific to MTs supporting USAT + +### 12.2.1 Read USAT profile +CUSATR + +**Table 12.2.1-1: +CUSATR action command syntax** + +| Command | Possible response(s) | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------| +| +CUSATR[=<profile_storage>] | [+CUSATR: <profile_storage>, <profile>]<br>[<CR><LF>+CUSATR: <profile_storage>, <profile>]<br>[...]<br>+CME ERROR: <err> | +| +CUSATR=? | +CUSATR: (list of supported <profile_storage>s) | + +Execution command +CUSATR=<profile\_storage> returns the profile specified by <profile\_storage>. Execution command issued without parameter; +CUSATR, returns all profiles. + +Test command returns values supported as a compound value. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<profile\_storage>: integer type. + +- 0 TE profile that can be set with +CUSATW. +- 1 MT profile that can be set with +CUSATW. +- 2 MT default profile that reflects the inherent, default supported facilities of the MT. + +- 3 UICC profile that reflects the currently active UICC profile that was sent to the UICC in the last TERMINAL PROFILE command. +- 4 UICC EF<sub>UST</sub>. The elementary file that indicates services available in the USIM. +- 5 List of MT only facilities (facilities that are not allowed to be assigned to the TE, see 3GPP TS 31.111 [92]). + +<profile>: string type in hexadecimal character format. The profile describing the supported facilities of the referenced <profile\_storage> as specified for the Terminal Profile in 3GPP TS 31.111 [92] or for the related EF in 3GPP TS 31.102 [59]. + +### Implementation + +Optional. + +## 12.2.2 Write USAT profile +CUSATW + +**Table 12.2.2-1: +CUSATW action command syntax** + +| Command | Possible response(s) | +|------------------------------------------|---------------------------------------------------------------------| +| +CUSATW[=<profile_storage>[, <profile>]] | +CUSATW: <profile_storage>, <conflict_profile><br>+CME ERROR: <err> | +| +CUSATW=? | +CUSATW: (list of supported <profile_storage>s) | + +### Description + +Execution command without parameters resets stored TE and MT profiles to their default values. Adding parameter <profile\_storage> to the AT command resets only the referred storage to its default value. Execution command issued with accompanied parameter <profile>, stores the given <profile> to non-volatile memory in the MT. + +Upon an attempt to store or reset a profile that conflicts with an already stored profile or the list of MT only facilities, the operation fails and the profile referred to by command parameter <profile\_storage> remains unchanged. The MT responds with +CUSATW: <profile\_storage>, <conflict\_profile> where <profile\_storage> refers the conflicting profile followed by the final result code +CME ERROR: 3 (Operation not allowed). If there is a conflict with the MT only facilities, <profile\_storage> is set to 5; otherwise <profile\_storage> indicates the profile already stored for the TE or for the MT. The rules for detecting conflicts are defined in 3GPP TS 31.111 [92]. + +Successful execution of the command does not result in any information response. + +Test command returns supported values as a compound value. + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<profile\_storage>: integer type. + +- 0 TE. Refers profile storage for the facilities supported by the TE. Default value is a blank profile with all bits set to zero. This value is applicable both in the execution command and in the information response. +- 1 MT. Refers profile storage for the facilities to be supported by MT, which can be a subset of the default MT facilities. The TE can choose to register a subset of the MT default profile, typically omitting facilities also supported by the TE profile. Default value is the MT default profile. This value is applicable both in the execution command and in the information response. +- 5 Refers to a conflict between the TE profile and the list of MT only facilities. This value is not applicable in the execution command. + +<profile>: string type in hexadecimal character format. The profile describing the supported USAT facilities of the referenced <profile\_storage> as specified for the Terminal Profile in 3GPP TS 31.111 [92]. + +<conflict\_profile>: string type in hexadecimal character format. A bitwise AND of two profiles, showing the conflicts, that is, USAT facilities supported by both profiles. See description of Terminal Profile in 3GPP TS 31.111 [92]. + +### Implementation + +Optional. + +## 12.2.3 Profile download upon start-up +CUSATD + +**Table 12.2.3-1: +CUSATD parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------|-----------------------------------------------------------------------------| +| +CUSATD=[<download>[, <reporting>]] | +CME ERROR: <err> | +| +CUSATD? | +CUSATD: <download>, <reporting> | +| +CUSATD=? | +CUSATD: (list of supported <download>s) , (list of supported <reporting>s) | + +### Description + +This command determines if, and optionally which profile should be downloaded to the UICC automatically upon start-up. If, prior to a restart/start-up, the +CUSATD settings have not been altered, then the default settings determine the behaviour upon start-up. However, if the parameters of +CUSATD has been set to other than default and then a restart is performed (e.g. by +CFUN), these values determine the behaviour. This is true for one restart only after altering +CUSATD parameters as they are always reset to default at the end of the next UICC start-up (i.e. when the USIM initialisation as specified in 3GPP TS 31.102 [59] has been completed). + +The command without parameters resets the parameters to their default values. + +The command can only be used if the UICC is already in active state (<UICC\_state> 4, e.g. upon +CUSATA) or in download completed state (<UICC\_state> 2) and the UICC does not support the "Additional TERMINAL PROFILE after UICC activation" feature (see 3GPP TS 31.111 [92]). In all other cases the command responds with +CME ERROR: 14 (SIM busy). + ++CUSATD=<download>, 1 also enables the unsolicited result code +CUSATS: <UICC\_state>. The MT uses this unsolicited result code to indicate that a profile download is performed (setting +CUSATD=0, 1 or +CUSATD=1, 1) or that it is ready for profile download (setting +CUSATD=2, 1). In both cases, the MT also indicates the end of UICC start-up by the unsolicited result code +CUSATS: 4. If the UICC is awaiting PIN verification during start-up, this is also reported. + +When using +CUSATD=1, the +CUSATA=1 command has to be used to enable TE profile facility handling after restart. In the time between profile download and issuance of +CUSATA=1, the UICC may already attempt to issue proactive commands. The MT will not send these to the TE, but rather give the UICC the response "terminal currently unable to process command" autonomously. The UICC may implement only a limited number of retries, which can potentially leave USAT in an unwanted state if the +CUSATA=1 command arrives late. + +NOTE: Care has to be taken when using +CUSATD=2. If no +CUSATA=2 or +CUSATA=3 is sent during start-up, USAT is also blocked for the MT. + +Test command returns supported values as compound values. + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<download>: integer type. Parameter decides when/if to perform a profile download to UICC and which profile to download. The default value is implementation specific. + +- 0 Download MT default profile automatically during next start-up. + +- 1 Download the combined TE and MT profile (merger of the profiles written by +CUSATW) automatically during next start-up. The rules for merging profiles are defined in 3GPP TS 31.111 [92]. +- 2 Halt next UICC start-up when ready for profile download. Profile to download will be selected and download will be triggered by +CUSATA. + +<reporting>: integer type. Parameter enables unsolicited result code +CUSATS: <UICC\_state> to notify the TE about a new state during start-up. + +- 0 Disable +CUSATS, i.e. no notification. +- 1 Enable +CUSATS, i.e. notify TE. + +<UICC\_state>: integer type. Parameter reports that the UICC entered a new state during start-up or that the UICC ended startup and entered active state. + +- 0 UICC start-up in progress, before profile download. +- 1 UICC start-up halted and ready for profile download. This state is reached if +CUSATD=2 was issued before restart. UICC start-up will continue upon +CUSATA=2 or +CUSATA=3. +- 2 Profile download completed, UICC startup continuing. +- 3 UICC awaiting PIN verification. +- 4 UICC active. + +## Implementation + +Optional. + +## 12.2.4 Activate USAT profile +CUSATA + +**Table 12.2.4-1: +CUSATA action command syntax** + +| Command | Possible response(s) | +|------------------------|--------------------------------------------------------------------------------| +| +CUSATA[=<activation>] | +CUSATA: <UICC_state>[, <additional_profile_support>]<br><br>+CME ERROR: <err> | +| +CUSATA=? | +CUSATA: (list of supported <activation>s) | + +## Description + +Execution command +CUSATA retrieves the current UICC state or downloads a profile to the UICC and/or activates handling of the TE profile facilities. + +A positive result upon a +CUSATA=1 or +CUSATA=3 command (also) enables TE profile facility handling via unsolicited result codes +CUSATP: <proactive\_command> and +CUSATEND. The MT uses the unsolicited result code +CUSATP: <proactive\_command> to forward to the TE proactive commands issued by the UICC. The unsolicited result code +CUSATEND is issued by the MT when the UICC indicates that the proactive command session is terminated, i.e. in response to a USAT terminal response, the UICC indicates that no other USAT proactive command is pending. Lastly, terminal responses to the proactive commands can now be issued with +CUSATT=<terminal\_response> and envelope commands can be issued with +CUSATE=<envelope\_command>. + +If the action requested by the +CUSATA command can not be performed, the information response +CUSATA: <UICC\_state>, [<additional\_profile\_support>] is returned with appropriate values, followed by the final result code +CME ERROR: 4 (Operation not supported) in case the UICC does not support USAT at all, or the final result code +CME ERROR: 3 (Operation not allowed) in all other cases. + +If the UICC is already in active state and the UICC does not support the "Additional TERMINAL PROFILE after UICC activation" feature (see 3GPP TS 31.111 [92]), the TE has the option to perform a reset of the UICC or use +CFUN to get back to an initial non-active UICC state. The +CUSATD command can be used to set profile handling upon the next restart. + +All USAT proactive commands that the MT does not process itself and all terminal responses from the TE are transparently forwarded by the MT. The routing mechanism for USAT commands supported by both entities is specified in 3GPP TS 31.111 [92]. + +Test command returns values supported as a compound value. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<activation>: integer type. + +- 0 Return status information only, in information response: ++CUSATA: <UICC\_state>[, <additional\_profile\_support>]. +- 1 Enable TE profile facility handling only, no profile download. This action can only be used if the combined TE and MT profile was downloaded during start-up (setting +CUSATD=1). +- 2 Download MT default profile. +- 3 Download the combined TE and MT profile (merger of the profiles written by +CUSATW) and enable TE profile facility handling. The rules for merging profiles are defined in 3GPP TS 31.111 [92]. + +<UICC\_state>: integer type. Parameter reports that the UICC entered a new state during start-up or that the UICC ended startup and entered active state. + +- 0 UICC start-up in progress, before profile download. +- 1 UICC start-up halted and ready for profile download. This state is reached if +CUSATD=2 was issued before restart. UICC start-up will continue upon +CUSATA=2 or +CUSATA=3. +- 2 Profile download completed, UICC startup continuing. +- 3 UICC awaiting PIN verification. +- 4 UICC active. + +<additional\_profile\_support>: integer type. Indicates whether the UICC supports the "Additional TERMINAL PROFILE after UICC activation" feature (see 3GPP TS 31.111 [92]). The value may not be available during early phases of start-up. + +- 0 No support. +- 1 Supported. + +<proactive\_command>: string type in hexadecimal character format. Proactive command as defined in 3GPP TS 31.111 [92], consisting of the full BER-TLV data object. + +#### Implementation + +Optional. + +### 12.2.5 Send USAT terminal response +CUSATT + +**Table 12.2.5-1: +CUSATT action command syntax** + +| Command | Possible response(s) | +|-----------------------------|----------------------| +| +CUSATT=<terminal_response> | +CME ERROR: <err> | +| +CUSATT=? | | + +## Description + +Execution command sends a USAT terminal response to the MT as an answer to a preceding USAT proactive command sent from the UICC with unsolicited result code +CUSATP: <proactive\_command> (see +CUSATA command description). + +Refer clause 9.2 for possible <err> values. + +## Defined values + +<terminal\_response>: string type in hexadecimal character format. Terminal response to a proactive command as defined in 3GPP TS 31.111 [92], consisting of the full BER-TLV data object. + +## Implementation + +Optional. + +## 12.2.6 Send USAT envelope command +CUSATE + +**Table 12.2.6-1: +CUSATE action command syntax** + +| Command | Possible response(s) | +|----------------------------|-----------------------------------------------------------------------------------------------------| +| +CUSATE=<envelope_command> | +CUSATE: <envelope_response>[, <busy>]<br>[<CR><LF>+CUSATE2: <sw1>, <sw2>]<br><br>+CME ERROR: <err> | +| +CUSATE=? | | + +## Description + +Execution command allows the TE to send a USAT envelope command to the MT. If the UICC provides response data to the command or indicates that USAT is busy, the information response + ++CUSATE: <envelope\_response>[, <busy>] is returned. A second line of information response +CUSATE2: <sw1>, <sw2> may be provided if the MT presents the status words provided by the UICC. + +Refer clause 9.2 for possible <err> values. + +## Defined values + +<envelope\_command>: string type in hexadecimal character format. Envelope command as defined in 3GPP TS 31.111 [92], consisting of the full BER-TLV data object. + +<envelope\_response>: string type in hexadecimal character format. Response to the envelope command as defined in 3GPP TS 31.111 [92], consisting of the full BER-TLV data object. An empty string is provided if the UICC does not have any response data to provide. + +<busy>: integer type. + +- 0 UICC indicated normal ending of the command. +- 1 UICC responded with USAT is busy, no retry by the MT. +- 2 UICC responded with USAT is busy even after one or more retries by the MT. + +<sw1>: integer type. Status word information from the envelope response returned by the UICC as defined in ETSI TS 102 221 [60], clause 10.2. The parameter can be delivered to the TE both in the case of successful and failed execution of the envelope command. + +<sw2>: integer type. For description see <sw1>. + +## Implementation + +Optional. + +## 12.3 Informative examples + +These examples provide a sequence of interactions where USAT commands and responses are transmitted in AT commands. As it would make the examples unreadable, USAT data is not given in its hexadecimal representation (which is found in 3GPP TS 31.111 [92]), but in abstract textual form. For readability, only a subset of USAT facilities typically provided in a profile is given in the examples. Resulting or triggering actions on the MT-UICC interface are also indicated in the examples. + +First, the TE reads the MT default profile: + +``` +AT+CUSATR=2 ++CUSATR: 2,<PLAY TONE, SET UP MENU, DISPLAY TEXT, EVENT MENU SELECTION, ...> +OK +``` + +The TE removes some USAT facilities in the MT by writing a new MT profile, which contains those facilities that are to be handled by the MT: + +``` +AT+CUSATW=1,<PLAY TONE, ...> +OK +``` + +Now the TE tries to write a TE profile that conflicts with the MT profile. The MT responds with the conflict information and rejects the command. + +``` +AT+CUSATW=0,<PLAY TONE, SET UP MENU, DISPLAY TEXT, EVENT MENU SELECTION, ...> ++CUSATW: 1,<PLAY TONE> ++CME ERROR: 3 +``` + +The next attempt to write a TE profile is successful and the TE activates the profiles. + +``` +AT+CUSATW=0,<SET UP MENU, DISPLAY TEXT, EVENT MENU SELECTION, ...> +OK +AT+CUSATA=3 + MT -> UICC: TERMINAL PROFILE + UICC -> ME: proactive command pending +OK +``` + +The UICC sends a SET UP MENU proactive command, resulting in the command being transferred to the TE and the latter confirming it with a terminal response; thereafter the proactive session ends. + +``` + UICC -> MT: SET UP MENU ++CUSATP: <SET UP MENU> +AT+CUSATT=<OK> + MT -> UICC: TERMINAL RESPONSE: OK + UICC -> ME: no proactive command pending +OK ++CUSATEND +``` + +A selection by the subscriber in the menu results in an ENVELOPE being sent to the MT and forwarded to the UICC. The UICC responds with the next proactive command DISPLAY TEXT. After the terminal response, the proactive session ends. + +``` +AT+CUSATE=<MENU SELECTION, item=1> + MT -> UICC: ENVELOPE(MENU SELECTION, item=1) + UICC -> ME: proactive command pending +OK + UICC -> MT: DISPLAY TEXT ++CUSATP: <DISPLAY TEXT> +AT+CUSATT=<OK> + MT -> UICC: TERMINAL RESPONSE: OK + UICC -> ME: no proactive command pending +OK ++CUSATEND +``` + +The TE defines UICC profile download options. The definition is effective for the next UICC start-up. + +``` +AT+CUSATD=1,1 +OK +``` + +The UICC restarts. The MT reports the start-up. During start-up the profile download definition cannot be altered and the MT responds error code 14 (SIM busy). + +``` ++CUSATS: 0 +AT+CUSATD=2,1 ++CME ERROR: 14 +``` + +The UICC is awaiting PIN verification. During PIN verification the profile download definition cannot be altered and the MT responds error code 14 (SIM busy). + +``` ++CUSATS: 3 +AT+CUSATD=2,1 ++CME ERROR: 14 +``` + +The UICC becomes active and the profile download definition can be changed. + +``` ++CUSATS: 4 +AT+CUSATD=2,1 +OK +``` + +The TE enables the downloaded profile. + +``` +AT+CUSATA=1 +OK +``` + +The TE reads the TE profile: + +``` +AT+CUSATR=0 ++CUSATR: 0,<PLAY TONE, SET UP MENU, DISPLAY TEXT, EVENT MENU SELECTION, ...> +OK +``` + +Now the TE tries to write a MT profile that conflicts with the TE profile. The MT responds with the conflict information and rejects the command. + +``` +AT+CUSATW=1,<DISPLAY TEXT, ...> ++CUSATW: 0,<DISPLAY TEXT> ++CME ERROR: 3 +``` + +The next attempt to write a MT profile is successful. + +``` +AT+CUSATW=1,<SET UP MENU, EVENT MENU SELECTION, ...> +OK +``` + +The TE reads the List of MT only facilities: + +``` +AT+CUSATR=5 ++CUSATR: 5,<POLL INTERVAL, POLLING OFF, PROVIDE LOCAL INFORMATION (NMR), ...> +OK +``` + +Now the TE tries to write a TE profile that conflicts with the MT only facilities. The MT responds with the conflict information and rejects the command. + +``` +AT+CUSATW=0,<POLL INTERVAL, ...> ++CUSATW: 5,<POLL INTERVAL> ++CME ERROR: 3 +``` + +The next attempt to write a TE profile is successful. + +``` +AT+CUSATW=0,<SET UP MENU, DISPLAY TEXT, EVENT MENU SELECTION, ...> +OK +``` + +## 13 Commands for enhanced support of dialling + +### 13.1 General + +This clause defines commands that a TE may use when dialling. These commands can be used instead of ATD that does not support dialling of URIs. + +Clause 13.2 defines commands for dialling (direct dialling and dialling from phonebook) as well as hangup of these calls. + +Clause 13.3 contains relevant examples. + +### 13.2 Commands for dialling + +#### 13.2.1 Dial URI +CDU + +**Table 13.2.1-1: +CDU action command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CDU=<action>[, <URI>[, <client>[, <mpidx>[, <CLIR_OIR>[, <CUG_pointer>[, <type_of_call>]]]]] | <p>+CME ERROR: <err></p> <p><b>when <action>=0 and command successful:</b></p> <p>[+CDUT: <URI_scheme>[, <client>]<br/> [<CR><LF>+CDUT: <URI_scheme>[, <client>]]<br/> [...]]</p> <p><b>when <action>=1 and command successful:</b></p> <p>[+CDU: <ccidx>]</p> <p><b>when <action>=1 and command unsuccessful:</b></p> <p>[+CDUI: <cause>]</p> | +| +CDU=? | +CDU: (list of supported <URI_scheme>s) | + +#### Description + +Execution command can be used to dial a URI (with <action>=1) for initiating communication using the specified communication client with the specified media profile. With <action>=0 the command can query which clients are supported for the URI types supported. + +When the command is used to query the supported URI types (i.e. <action>=0), the URI types are provided by +CDUT: <URI\_scheme>. When the command is used to dial a URI (i.e. <action>=1) and the dialling succeeds the command is terminated by +CDU: <ccidx> and OK. The parameters <CLIR\_OIR> and <CUG\_pointer> are used to set the per call basis values of the supplementary services CLIR / OIR and CUG. + +The unsolicited result code +CDUU: <ccidx>, <code> can be subsequently provided to give further basic information about the call as it progresses. The value of the <ccidx> is kept until the call is released. See command +CMCCS and unsolicited result code +CMCCSI for provision of additional information about the call setup. + +If "Call control by USIM" see 3GPP TS 31.111 [92] clause 4.5 is activated by the USIM, it is the responsibility of the communication client to perform any required call control verification according to the procedures defined in 3GPP TS 31.111 [92] clause 7.3 prior to the execution of the call setup. + +When call control by USIM is applicable, the communication client shall perform the call control (for example by using the Commands for USIM application toolkit, see clause 12) and act upon the result of the call control as follows: + +- if call control by USIM performs no modifications to the call request, the call setup shall be executed without any changes to the data; +- if call control by USIM modifies the call request, the call setup shall be executed using the modified data as provided by the call control; +- if call control by USIM modifies the call request to a different service, the appropriate AT command(s) for that service shall be executed; and +- if call control by USIM rejects the call request, the call setup shall not be executed. + +If the attempt to dial does not succeed, the command is terminated by `ERROR / +CME ERROR` or `+CDUI: <cause>` and `OK`. Refer clause 9.2 for possible `<err>` values. + +Test command returns values supported as a compound value. + +### Defined values + +`<action>`: integer type + +- 0 Query supported communication clients for the supported URI types. Execution command `+CDU=0` returns a line of intermediate result code `+CDUT: <URI_scheme>[, <client>]` for every supported `<URI_scheme>`. +- 1 Dial `<URI>` using the indicated communication client with the indicated media profile. + +`<URI>`: string type. URI including the prefix specifying the URI type. The URI may include URI parameters. The used character set should be the one selected with command select TE character set `+CSCS`. + +`<CLIR_OIR>`: integer type. Indicates per call basis changes provided to the supplementary service CLIR / OIR. See `+CLIR` for further information of the related parameters. + +- 0 No per call based changes to CLIR / OIR, the settings with `+CLIR` apply +- 1 Restrict the CLI presentation for the current call (CLIR / OIR invocation) +- 2 Allow CLI presentation for the current call (CLIR / OIR suppression) + +`<CUG_pointer>`: integer type. Indicates per call basis changes provided to the supplementary service closed user group. See `+CECUG` for further information of the related parameters. + +- 0 No per call basis changes to CUG +- 1-n Indicates the CUG index to use for this call. The CUG index and corresponding values used as set with command `+CECUG` (enable CUG temporary mode). The maximum value of n is implementation specific. + +NOTE 1: 3GPP TS 22.085 [21] indicates that each individual subscriber can be a member of a maximum of 10 CUGs. + +`<type_of_call>`: integer type. Indicates type of call on per call basis. + +- 0 Normal call +- 1 Dual radio voice call continuity call. + +`<URI_scheme>`: string type represented with IRA characters. Parameter identifies supported URI scheme. This parameter shall not be subject to conventional character conversion as per `+CSCS`. + +- `"sip"` Internet Assigned Number Authority (IANA) registry as per RFC 3969 [113], used with Session Initiation Protocol (SIP), see RFC 3261 [111]. + +"tel" Internet Assigned Number Authority (IANA) registry as per RFC 5341 [114], used with SIP, see RFC 3966 [112]. + +"urn" Internet Assigned Number Authority (IANA) registry according to RFC 2141 [116], only used with SIP in combination with a suitable uniform resource name (URN) namespace. + +NOTE 2: The URN namespace "service" listed in the Internet Assigned Number Authority (IANA) registry according to RFC 3406 [117] is an example of a namespace that can be used in SIP in combination with the URI scheme "urn". Not all top-level service labels listed in the Internet Assigned Number Authority (IANA) registry according to RFC 5031 [118] need to be supported in combination with the URN namespace "service". + +<client>: integer type. Communication client indication. The default value is implementation specific. + +1 MMTel. The UE procedures in 3GPP TS 24.173 [87] apply. + +128 – 255 Reserved for vendor specific communication clients. + +<mpidx>: integer type. Media profile identification number. The parameter is local to the TE-MT interface. The range of permitted values (minimum value = 1) is returned by the test form of the command +CDEFMP. When +CDU is used for dialling (i.e. with <action>=1) this number can be provided to point to a particular media profile. The provided media profile identification number is the number being returned by +CDEFMP when defining the media profile. Usage and value of a default media profile is implementation specific. + +<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. + +NOTE 3: When +CMCCS is supported, the call identification number is not reset until the unsolicited result code +CMCCSI has indicated that the <ccstatus>=1 (Idle). + +<code>: string type represented with IRA characters. Cause codes giving main call state information. Intermediate call status responses can be reported using the unsolicited result code +CMCCSI (see command +CMCCS). This parameter shall not be subject to conventional character conversion as per +CSCS. + +"BUSY" Busy signal detected + +"ANSWERED" Remote party has answered and the connection between A and B has been established + +"NO ANSWER" Connection completion timeout + +"CONNECTION TERMINATED" The connection is terminated from either the remote party or the network, or the attempt to establish the call setup is unsuccessful + +NOTE 4: The cause code "CONNECTION TERMINATED" also covers all other situations where a call is unsuccessfully terminated. Examples of this are all types of network congestion or lack of radio coverage. + +<cause>: integer type. Reason code providing further details why the call setup fails in the terminal before signalling towards the network is initiated. + +0 Outgoing call attempt rejected by (U)SIM/ME, unspecified + +1 Outgoing call attempt rejected by barring services in the SIM/ME + +## Implementation + +Optional. + +## 13.2.2 Dial URI from phonebook +CDUP + +**Table 13.2.2-1: +CDUP action command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------|----------------------------------------------------------------------------------| +| +CDUP=<pb_field>,<str>[,<client>[,<mpidx>[,<storage>]]] | +CME ERROR: <err><br><br><b>when command successful:</b><br><br>[+CDUP: <ccidx>] | +| +CDUP=? | | + +### Description + +Execution command dials a URI for initiating communication using the specified communication client with the specified media profile by referencing either the alphanumeric phonebook field, or the index or entry-number in the phonebook. Supported clients URI schemes are those returned with +CDU=0. If parameter <storage> is not included, the relevant phonebook is specified by the current +CPBS setting. If the referenced URI is not found, OK is returned and nothing is dialled. + ++CDUP=0, <str> originates a call to the first URI found in the selected phonebook which has a partial or full match to <str>. The mechanism to search for the first match through a phonebook is implementation specific. Upon no match in the selected phonebook, it is manufacturer specific if and what further phonebook memories are searched. + ++CDUP=1, <str> originates a call to the URI in memory location <str>, where <str> must contain a decimal number. The index or entry-number in the phonebook is expressed by <str>. + +How the string of digits or the index or entry-number is associated with entries is implementation specific. + +The command is terminated by +CDUP: <ccidx> and OK or ERROR / +CME ERROR. Refer clause 9.2 for possible <err> values. + +### Defined values + +<pb\_field>: integer type + +- 0 Refers alphanumeric field of the phonebook. <str> may contain valid characters for alphanumeric field of the selected phonebook. +- 1 Refers index or entry-number in the phonebook. + +<str>: string type. Valid characters are governed by <pb\_field>. + +<storage>: string type. Supported values are the same as that supported for <storage> of +CPBS. + +<client>: integer type. Communication client indication. + +- 1 MMTel. The UE procedures in 3GPP TS 24.173 [87] apply. +- 128 – 255 Reserved for vendor specific communication clients. + +<mpidx>: integer type. Media profile identification number. The parameter is local to the TE-MT interface. The range of permitted values (minimum value = 1) is returned by the test form of the command +CDEFMP. The provided media profile identification number is the number being returned by +CDEFMP when defining the media profile. Usage and value of a default media profile is implementation specific. + +<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. + +### Implementation + +Optional. + +### 13.2.3 Hangup of current calls +CHCCS + +**Table 13.2.3-1: +CHCCS action command syntax** + +| Command | Possible response(s) | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CHCCS=<ccidx>[, <cause>] | <p>+CME ERROR: <err></p> <p><b>when <ccidx>=value>0 is inserted and command successful:</b></p> <p>[+CHCCSI: <ccidx>]</p> <p><b>when <ccidx>=0 is inserted and command successful:</b></p> <p>[+CHCCSI: <ccidx><br/> [<CR><LF>+CHCCSI: <ccidx>]<br/> [...]]</p> | +| +CHCS=? | | + +#### Description + +Execution command causes the TA to initiate hangup and subsequently perform call clearing of the call for which a <ccidx> was provided when the call was detected in the MT. The parameter <cause> can be added to indicate particular information on the cause for call clearing. Setting the parameter <cause> to values 2 or 3 is typically relevant for call clearing before a call has been established (e.g. an incoming or waiting call). The parameter <cause> is ignored by the lower layers if it is not according to the signalling procedures in question. + +A special form of the execution command, +CHCCS=0, causes the TA to initiate hangup and subsequently perform call clearing of all calls for which a <ccidx> was provided when the call was detected in the MT. The parameter <cause> will be ignored if <ccidx>=0. + +The information text +CHCCSI: <ccidx> is provided for each call where a successful hangup is initiated as result of the +CHCCS. If no hangup is initiated, no information text is provided before OK is returned. + +NOTE 1: The command +CHCCS=0 will initiate hangup of all calls with a <ccid>. This also applies to calls on hold and call waiting calls. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. + +NOTE 2: When +CMCCS is supported, the call identification number is not reset until the unsolicited result code +CMCCSI has indicated that the <ccstatus>=1 (Idle). + +<cause>: integer type. Proposed cause value for call clearing. + +- 0 No particular cause indicated +- 1 Cause "Normal call clearing" (value 16), see 3GPP TS 24.008 [8] table 10.5.123 or BYE request, see RFC 3261 [111] clause 15.1 +- 2 Cause "Call rejected" (value 21), see 3GPP TS 24.008 [8] table 10.5.123 or "488 Not Acceptable Here", see RFC 3261 [111] clause 21.4.26 + +- 3 Cause "User busy" (value 17), see 3GPP TS 24.008 [8] table 10.5.123 or "486 Busy Here", see RFC 3261 [111] clause 21.4.24 + +### Implementation + +Mandatory when +CDU is implemented in the TA. + +## 13.2.4 Define media profile +CDEFMP + +**Table 13.2.4-1: +CDEFMP parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| +CDEFMP=[<mpidx>] [, <SDP_md>] | +CME ERROR: <err><br><br><b>When no <mpidx> but <SDP_md> provided and command successful:</b><br><br>[+CDEFMP: <mpidx>] | +| +CDEFMP? | [+CDEFMP: <mpidx>, <SDP_md>]<br>[<CR><LF>+CDEFMP: <mpidx>, <SDP_md>]<br>[...]]] | +| +CDEFMP=? | +CDEFMP: (range of supported <mpidx>s) | + +### Description + +A media profile is identified by its media profile identification number. A media profile defines an SDP media description to be used in SDP offers and SDP answers. Media profiles can be used with +CDU and +CDUP when dialling URIs. + +The set command specifies the SDP media description for a media profile identified by the (local) media profile identification number, <mpidx>. When no <mpidx> value is provided then a new SDP media description is defined and the media profile's identification number is returned by the command's response. When an <mpidx> value is provided, the definition of the SDP media description identified by the media profile identification number <mpidx> is replaced with the SDP media description provided by the command. + +A special form of the set command, +CDEFMP=<mpidx> causes the SDP media description for the indicated media profile to become undefined. Further, +CDEFMP= causes the SDP media description for all defined media profiles to become undefined. + +The read command returns a list of all defined media profiles. + +The test command returns values supported as a compound value. + +Refer clause 9.2 for possible <err> values. + +### Defined values + +<mpidx>: integer type. Media profile identification number. The parameter is local to the TE-MT interface. The range of permitted values (minimum value = 1) is returned by the test form of the command. The MT shall use the indicated SDP media description for the <mpidx> in the initial SDP offer for a call setup. + +<SDP\_md>: string type represented with IRA characters. SDP media description including media level SDP lines. This parameter shall not be subject to conventional character conversion as per +CSCS. + +This parameter can contain the following types of SDP lines: SDP m-lines, SDP a-lines and partial SDP m-lines. + +The communication client in the MT shall take into account SDP a-line rtpmap and fmtp attributes when negotiating media. Which other attributes in media level SDP a-lines are taken into account by the communication client is implementation specific. + +Partial SDP m-lines include nothing but a media type. + +For every media either an SDP m-line or a partial SDP m-line must be provided. + +SDP m-lines indicate that the described media is encoded/decoded outside the MT. + +Partial SDP m-lines indicate that the described media is encoded/decoded by the MT. When negotiating media the MT adds payload information to the partial SDP m-line. + +The communication client in the MT shall use the provided SDP line information when negotiating media. The communication client shall add other SDP lines required for negotiating media. + +### Informative examples + +The MT handles encoding and decoding of audio media, and the TE supports two types of video media, as described by the following SDP lines: + +``` +m=audio +m=video 99 98 +a=rtpmap:99 H264/90000 +a=fmtp:99 profile-level-id=4D4033 +a=rtpmap:98 MP4V-ES/90000 +a=fmtp:98 profile-level-id=1 +``` + +To indicate its support for both audio and video media for an incoming or outgoing call, the TE uses the following <SDP\_md>: + +``` +"m=audio\0D\0Am=video 99 98\0D\0Aa=rtpmap:99 H264/90000\0D\0Aa=fmtp:99 profile-level-id=4D4033\0D\0Aa=rtpmap:98 MP4V-ES/90000\0D\0Aa=fmtp:98 profile-level-id=1" +``` + +The TE intends to offer a file transfer over MSRP, as described by the following SDP lines: + +``` +m=message 7654 TCP/MSRP * +i=This is my latest picture +a=sendonly +a=accept-types:message/cpim +a=accept-wrapped-types:* +a=path:msrp://atlanta.example.com:7654/jshA7we;tcp +a=file-selector:name:"My cool picture.jpg" type:image/jpeg +``` + +When proposing the MSRP file transfer to the remote party, the TE uses the following <SDP\_md>: + +``` +"m=message 7654 TCP/MSRP *\0D\0Aa=sendonly\0D\0Aa=accept-types:message/cpim\0D\0Aa=accept-wrapped-types:*\0D\0Aa=path:msrp://atlanta.example.com:7654/jshA7we;tcp\0D\0Aa=file-selector:name:\22My cool picture.jpg\22 type:image/jpeg" +``` + +NOTE: The SDP i-line is not provided as part of the <SDP\_md> value. + +### Implementation + +Optional. + +## 13.2.5 Control and modify media description +CCMMD + +**Table 13.2.5-1: +CCMMD parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------------|----------------------| +| +CCMMD=<ccidx>, <neg_status> [, <SDP_md>] | | +| +CCMMD? | | +| +CCMMD=? | | + +### Description + +This command allows control of the media used in a multimedia call. The command can be used to initiate modification of the media of an ongoing call, to accept, modify or reject incoming changes in media or to accept, modify or reject the media for an incoming call. Supported media types are typically audio, video and messaging (MSRP). + +When <ccidx> matches the index of an ongoing call, the TA/MT will attempt to add or remove media to the call by triggering an SDP renegotiation over the SIP protocol. + +When <neg\_status>=1, the set command requests an unconditional change the media of the call to that described by <SDP\_md>. + +When <neg\_status>=2, the set command proposes a change of media to that described by <SDP\_md>, to which the remote party has to respond before the media of the call is changed. The response from the remote party will be indicated in a +CMCCSI unsolicited result code. If the remote party accepts the change of media, the <neg\_status> value in +CMCCSI will be set to 3. If the remote party rejects the change of media, <neg\_status> will be set to 4. In both cases the <SDP\_md> value in +CMCCSI will describe the currently active media of the call (if any). + +If the remote party unconditionally changes the media of the call, this will be indicated in a +CMCCSI unsolicited result code, with <neg\_status>=1 and <SDP\_md> containing the updated (and now active) media description. + +If the remote party proposes to change the media of an ongoing call, this will be indicated in a +CMCCSI unsolicited result code, with <neg\_status>=2. The set command is used to respond to the proposal, either by accepting it by setting <neg\_status>=3, by rejecting it by setting <neg\_status>=4, or indicate that a subset of the incoming proposal is accepted by setting the <neg\_status>=3 along with the <SDP\_md> containing the subset of the incoming proposal is acceptable. + +When the MT receives an incoming call from a remote party, the +CMCCSI unsolicited result code will be sent to the TE with <neg\_status>=2. This proposed media for the new call is either accepted, modified or rejected as described above. + +### Defined values + +<ccidx>: integer type. Call identification number as defined in the +CMCCS and +CLCCS commands. + +<neg\_status>: integer type + +- 1 The <SDP\_md> parameter describes the desired set of media for the call. +- 2 The <SDP\_md> parameter describes a proposal for a new set of media for the call. +- 3 Accept the most recently received media proposal. The <SDP\_md> parameter describes the accepted media for the call. +- 4 Reject the most recently received media proposal. + +<SDP\_md>: string type represented with IRA characters. Media description as per the +CDEFMP command. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. + +## 13.3 Informative examples + +Below is an example where a voice call originated with +CDU is placed to a tel-URI. This example outlines how the call is initiated by the AT command +CDU, and how the unsolicited result code +CDUU is used to indicate how the call-setup progress until it is terminated. Both successful and unsuccessful outcome of a call attempt is shown in the example. + +``` +AT+CDU=1,"tel:+47-123-45678" (Voice call initiated) ++CDU: 2 (Call initiated, call identification number 2 provided) +OK (Call initiation successful) + +(Call setup progress, unsolicited result codes appear as appropriate) + +(If call is answered by the remote party) ++CDUU: 2,"ANSWERED" (Remote party has answered) + +(If remote party does not answer) ++CDUU: 2,"NO ANSWER" (Connection completion timeout) + +(If remote party is busy) ++CDUU: 2,"BUSY" (Busy signal detected) + +(If call is terminated from remote party) ++CDUU: 2,"CONNECTION TERMINATED" (Connection terminated from remote party) + +(If call is terminated from calling party) +AT+CHCCS=2 (Connection with call identification number 2 terminated from calling party) ++CHCCS: 2 +OK +``` + +Below is an example where a multimedia-call (voice) originated with +CDU is placed to a SIP-URI. This example outlines how the call is initiated by the AT command +CDU, and how the unsolicited result codes +CDUU and +CMCCSI are used to indicate how the call-setup progress until it is terminated. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. + +``` +AT+CDU=1,"sip:veronica@university.org" (Multimedia-call (voice) initiated) ++CDU: 4 (Call initiated, call identification number 4 provided) +OK (Call initiation successful) + +(+CDUU and +CMCCSI appear as appropriate) + ++CMCCSI: 4,0,0,0,0,"",0,2,0,1,0,"sip:veronica@university.org",0,0 (Call setup is started) ++CMCCSI: 4,0,0,0,0,"",0,3,0,1,0,"sip:veronica@university.org",0,0 (Call is in progress) ++CMCCSI: 4,0,0,0,0,"",0,4,0,1,0,"sip:veronica@university.org",0,0 (Alert indication received) + +CDUU: 4,"ANSWERED" (Remote party answered) + ++CMCCSI: 4,0,0,0,0,"",0,6,0,1,0,"sip:veronica@university.org",0,0 (Connection established) + +AT+CHCCS=4 (Connection with call identification number 4 terminated) ++CHCCS: 4 +OK + ++CMCCSI: 4,0,0,0,0,"",0,7,0,1,0,"sip:veronica@university.org",2,200 (Outgoing connection released) ++CMCCSI: 4,0,0,0,0,"",0,0,0,1,0,"sip:veronica@university.org",0,0 (Idle) +``` + +Below is an example where a multimedia-call originated with +CDU is placed to a SIP-URI. This example outlines how the call is initiated by the AT command +CDU, and how the unsolicited result codes +CDUU and +CMCCSI are used to indicate how the call-setup progresses until it is terminated. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. This example illustrates the use of the +CDEFMP and +CCMMD commands to define and control the types of media that are used in the call. + +``` +AT+CDEFMP=,"m=audio" (Media profile defined, offering only audio) ++CDEFMP=3 (Media profile index number 3 provided) +OK +``` + +``` + +AT+CDU=1, "sip:veronica@university.org", 1, 3 (Multimedia-call initiated, using media profile number 3) ++CDU: 5 (Call initiated, call identification number 5 provided) +OK (Call initiation successful) + +(+CDUU and +CMCCSI appear as appropriate) + ++CMCCSI: 5, 0, 0, 0, "", 0, 2, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Call setup is started) ++CMCCSI: 5, 0, 0, 0, "", 0, 3, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Call is in progress) ++CMCCSI: 5, 0, 0, 1, "m=audio", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Alert indication received and played back) ++CMCCSI: 5, 0, 1, 3, "m=audio", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Remote party accepted the proposal for audio media) ++CDUU: 5, "ANSWERED" (Remote party answered) ++CMCCSI: 5, 0, 1, 1, "m=audio", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Connection established, audio media is active) ++CMCCSI: 5, 0, 1, 2, "m=audio\0D\0Am=video 99 98\0D\0Aa=rtpmap:99 H264/90000\0D\0Aa=fmtp:99 profile-level-id=4D4033\0D\0Aa=rtpmap:98 MP4V-ES/90000\0D\0Aa=fmtp:98 profile-level-id=1", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Remote party proposed adding video to the call, offering two different formats) +AT+CCMDC=5, 3, "m=audio\0D\0Am=video 99 98\0D\0Aa=rtpmap:99 H264/90000\0D\0Aa=fmtp:99 profile-level-id=4D4033\0D\0Aa=rtpmap:98 MP4V-ES/90000\0D\0Aa=fmtp:98 profile-level-id=1" +(Proposal accepted, indicating support for both formats offered) +OK ++CMCCSI: 5, 0, 1, 1, "m=audio\0D\0Am=video 99 98\0D\0Aa=rtpmap:99 H264/90000\0D\0Aa=fmtp:99 profile-level-id=4D4033", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Call media changed to audio and video on a format selected by the TE) +AT+CCMDC=5, 1, "m=audio" (Video media removed, unconditionally) +OK ++CMCCSI: 5, 0, 1, 1, "m=audio", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Call media changed to audio only) +AT+CHCCS=5 (Connection with call identification number 5 terminated) ++CHCCSI: 5 +OK ++CMCCSI: 5, 0, 0, 0, "", 0, 7, 0, 1, 0, "sip:veronica@university.org", 2, 200 (Outgoing connection released) ++CMCCSI: 5, 0, 0, 0, "", 0, 1, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Idle) + +``` + +Below is an example where an incoming multimedia-call is received, but the initially offered media audio+video is accepted as audio+video-recv-only, which is subset of the initial offer. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. The terms "<audio>", "<audio+video>" and "<audio+video-recv-only>" are used to illustrate respective SDP media descriptions of audio, audio+video and audio+video-recv-only in the example. + +``` + +RING (Ringing call) ++CMCCSI: 3, 1, 1, 2, "<audio+video>", 0, 5, 0, 1, 0, "sip:archie@university.org", 0, 0 +(Incoming ringing call with call identification number 3 and a proposal for audio+video media) +AT+CCMMD=3, 3, " <audio+video-recv-only>" (Media proposal accepted as audio+video-recv-only) +OK +ATA (Call answered) +OK ++CMCCSI: 3, 1, 1, 1, "< Audio+video-recv-only >", 0, 6, 0, 1, 0, "sip:archie@university.org", 0, 0 +(Active call established with audio media) + +``` + +Below is an example where a multimedia-call originated with +CDU is placed to a SIP-URI. In this example, the remote party proposes to add video to the call, the local UE accepts the incoming proposal as audio+video-recv-only. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. The terms "<audio>", "<audio+video>" and "<audio+video-recv-only>" are used to illustrate respective SDP media descriptions of audio, audio+video and audio+video-recv-only in the example. + +``` + +AT+CDEFMP=, "m=audio" (Media profile defined, offering only audio) + ++CDEFMP=3 (Media profile index number 3 provided) +OK + +AT+CDU=1, "sip:veronica@university.org", 1, 3 (Multimedia-call initiated, using media profile number 3) ++CDU: 5 (Call initiated, call identification number 5 provided) +OK (Call initiation successful) + +(+CDUU and +CMCCSI appear as appropriate) + ++CMCCSI: 5, 0, 0, 0, "", 0, 2, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Call setup is started) + ++CMCCSI: 5, 0, 0, 0, "", 0, 3, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Call is in progress) + ++CMCCSI: 5, 0, 0, 1, "m=audio", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Alert indication received and played back) + ++CMCCSI: 5, 0, 1, 3, "m=audio", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Remote party accepted the proposal for audio media) + ++CDUU: 5, "ANSWERED" (Remote party answered) + ++CMCCSI: 5, 0, 1, 1, "m=audio", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Connection established, audio media is active) + ++CMCCSI: 5, 0, 1, 2, "<audio+video>", 0, 5, 0, 1, 0, "sip:archie@university.org", 0, 0 +(Remote party propose to add video to the call) + +AT+CCMDC=5, 3, "<audio+video-recv-only>" (Proposal accepted as audio and video (recv-only)) +OK ++CMCCSI: 5, 0, 1, 1, "<audio+video-recv-only>", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Call media changed to audio and video-recv-only) + +``` + +Below is an example where a multimedia-call originated with +CDU is placed to a SIP-URI. In this example, the remote party rejects the proposed media and makes a counterproposal, which is then accepted by the originating party before the call is established. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. The terms "<audio>" and "<audio+video>" are used to illustrate respective SDP media descriptions of audio and audio+video in the example. + +``` + +AT+CDEFMP=, "<audio+video>" (Media profile defined, offering both audio and video) ++CDEFMP=4 (Media profile index number 4 provided) +OK +AT+CDU=1, "sip:veronica@university.org", 1, 4 (Multimedia-call initiated, using media profile number 4) ++CDU: 6 (Call initiated, call identification number 6 provided) +OK (Call initiation successful) + +(+CDUU and +CMCCSI appear as appropriate) + ++CMCCSI: 6, 0, 0, 0, "", 0, 2, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Call setup is started) ++CMCCSI: 6, 0, 0, 0, "", 0, 3, 0, 1, 0, "sip:veronica@university.org", 0, 0 (Call is in progress) ++CMCCSI: 6, 0, 0, 1, "<audio>", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Alert indication received and played back) + ++CMCCSI: 6, 0, 1, 4, "", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Remote party rejected the proposal for audio+video media) + ++CMCCSI: 6, 0, 1, 2, "<audio>", 0, 4, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Remote party proposed audio-only media for the call) + +AT+CCMMD=6, 3, "<audio>" (Proposal accepted) +OK + ++CDUU: 6, "ANSWERED" (Remote party answered the call) + ++CMCCSI: 6, 0, 1, 1, "<audio>", 0, 6, 0, 1, 0, "sip:veronica@university.org", 0, 0 +(Connection established, audio media is active) + +``` + +Below is the same scenario as above from the terminating party's perspective. An incoming multimedia-call is received, but the initially offered media is rejected and a successful counterproposal is made. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. The terms "<audio>" + +and "<audio+video>" are used to illustrate respective SDP media descriptions of audio and audio+video in the example. + +RING (Ringing call) + ++CMCCSI: 3,1,1,2,"<audio+video>",0,5,0,1,0,"sip:archie@university.org",0,0 +(Incoming ringing call with call identification number 3 and a proposal for audio+video media) + +AT+CCMMD=3,4 (Media proposal rejected) +OK + +AT+CCMMD=3,2,"<audio>" (Audio-only media for the call proposed) +OK + ++CMCCSI: 3,1,1,3,"<audio>",0,5,0,1,0,"sip:archie@university.org",0,0 +(Originating party accepted the proposed, and now active, audio media) + +ATA (Call answered) +OK + ++CMCCSI: 3,1,1,1,"<audio>",0,6,0,1,0,"sip:archie@university.org",0,0 (Active call established with audio media) + +Below is an example where a multimedia-call originated with +CDU is placed to a SIP-URI. In this example, both the proposed media and the call is rejected by the remote party. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. The terms "<audio>" and "<audio+video>" are used to illustrate SDP media description of audio and audio+video in the example. + +AT+CDEFMP="<audio+video>" (Media profile defined, offering both audio and video) + ++CDEFMP=5 (Media profile index number 5 provided) +OK + +AT+CDU=1,"sip:veronica@university.org",1,5 (Multimedia-call initiated, using media profile number 5) + ++CDU: 7 (Call initiated, call identification number 7 provided) +OK (Call initiation successful) + +(+CDUU and +CMCCSI appear as appropriate) + ++CMCCSI: 7,0,0,0,"",0,2,0,1,0,"sip:veronica@university.org",0,0 (Call setup is started) + ++CMCCSI: 7,0,0,0,"",0,3,0,1,0,"sip:veronica@university.org",0,0 (Call is in progress) + ++CMCCSI: 7,0,0,1,"<audio>",0,4,0,1,0,"sip:veronica@university.org",0,0 +(Alert indication received and played back) + ++CMCCSI: 7,0,1,4,"",0,4,0,1,0,"sip:veronica@university.org",0,0 +(Remote party rejected the proposal for audio+video media) + ++CDUU: 7,"CONNECTION TERMINATED" (Remote party rejected the call) + ++CMCCSI: 7,0,0,0,"",0,7,0,1,0,"sip:veronica@university.org",2,488 (Outgoing connection released) + ++CMCCSI: 7,0,0,0,"",0,1,0,1,0,"sip:veronica@university.org",0,0 (Idle) + +Below is the same scenario as above from the terminating party's perspective. An incoming multimedia-call is received, but both the initially offered media and the call are rejected. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. The term "<audio+video>" is used to illustrate SDP media description of audio+video in the example. + +RING (Ringing call) + ++CMCCSI: 4,1,1,2,"<audio+video>",0,5,0,1,0,"sip:archie@university.org",0,0 +(Incoming ringing call with call identification number 4 and a proposal for audio+video media) + +AT+CCMMD=4,4 (Media proposal rejected) +OK + +AT+CHCCS=4,2 (Connection with identification number 4 rejected) ++CHCCSI: 4 +OK + ++CMCCSI: 4,0,0,0,"",0,8,0,1,0,"sip:veronica@university.org",2,488 (Incoming connection released) + ++CMCCSI: 4,0,0,0,"",0,1,0,1,0,"sip:veronica@university.org",0,0 (Idle) + +## 14 Commands for eMBMS configuration + +### 14.1 General + +This clause defines AT commands that a TE may use to control MT supporting evolved Multimedia Broadcast Multicast Service (eMBMS). eMBMS is a unidirectional point-to-multipoint service in which data is transmitted from a single source entity to a group of users in a specific area. eMBMS services are transmitted on the same carrier frequencies used by mobile operators to provide other typical services such as voice calls and internet. There are various types of eMBMS services that can be provided to the end user such as Mobile TV, streaming, file download, etc. + +eMBMS information is sent over SystemInformationBlockType13 information element (SIB-13) according to 3GPP TS 36.331 [86] clause 6.3.1. Information on eMBMS parameters can be found in 3GPP TS 36.443 [150] and 3GPP TS 29.061 [39]. + +A comprehensive set of eMBMS-specific commands is defined to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new eMBMS feature options and interface protocols, merely by defining new values for many of the parameters. The commands use the extended information and error message capabilities described in this specification. + +The +CEMBMSCFG command enables or disables the eMBMS support in the MT. Once the eMBMS service is enabled then the status of the eMBMS session can be received by enabling the URC using the +CEMBMSR command. The +CEMBMSR command also provides information about the TMGI and eMBMS session being used by the MT. The +CEMBMSDATA command can be used by the MT to configure the data channel to use for receiving eMBMS services. The +CEMBMSSRV command is used to configure and activate the eMBMS service for a specific TMGI and listen for any service change indications. The +CEMBMSCNT command can be used to set the list of TMGIs from which the MT can receive eMBMS services. + +### 14.2 Commands specific to eMBMS + +#### 14.2.1 eMBMS configuration in MT +CEMBMSCFG + +**Table 14.2.1-1: +CEMBMSCFG parameter command syntax** + +| Command | Possible response(s) | +|------------------------|----------------------------------------------| +| +CEMBMSCFG=<setup_cfg> | +CME ERROR: <err> | +| +CEMBMSCFG? | +CEMBMSCFG: <setup_cfg> | +| +CEMBMSCFG=? | +CEMBMSCFG: (list of supported <setup_cfg>s) | + +#### Description + +Set command enables and disables the eMBMS support. + +When eMBMS is enabled the MT reads the SystemInformationBlockType13 information element (SIB-13) according to 3GPP TS 36.331 [86] clause 6.3.1. + +If this command is issued when eMBMS is not active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +Read command returns the current eMBMS configuration settings in the MT. + +Test command returns values supported as a compound value. + +#### Defined values + +<setup\_cfg>: integer type; specifies if eMBMS support is to be enabled or disabled in the MT. + +- 0 disable eMBMS support in MT. When eMBMS support is disabled MT is not receiving or consuming any eMBMS service nor monitoring any Multicast Control Channel + +- 1 enable eMBMS support in MT + +### Implementation + +Optional + +## 14.2.2 eMBMS status reporting in MT +CEMBMSR + +**Table 14.2.2-1: +CEMBMSR parameter command syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CEMBMSR= [<n>] | | +| +CEMBMSR? | +CEMBMSR: <n> | +| +CEMBMSR=? | +CEMBMSR: (list of supported <n>s) | + +### Description + +Set command controls the presentation of unsolicited result code + ++CEMBMSRI: <session\_status>, <tmgi>, <embms\_session\_id> [, <tmgi>, <embms\_session\_id> [...]] reporting eMBMS session parameter values. The eMBMS session parameter values are reported only if the eMBMS service is enabled using the +CEMBMSCFG command. Set command does not trigger a request in the MT to read the SystemInformationBlockType13 information element (SIB-13) information. + +Read command returns the current eMBMS unsolicited result code settings in the MT. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type + +- 0 disable presentation of the unsolicited result code + +- 1 enable presentation of the unsolicited result code + ++CEMBMSRI: <session\_status>, <tmgi>, <embms\_session\_id> [, <tmgi>, <embms\_session\_id> [...]] + +<session\_status>: integer type; if eMBMS support is enabled, this parameter indicates whether an eMBMS session is activated or deactivated. When the eMBMS session is activated, +CEMBMSDATA command can be used to enter into data state. + +- 0 eMBMS session is deactivated. When eMBMS session is deactivated MT is not receiving or consuming any eMBMS service but the MT is monitoring Multicast Control Channels + +- 1 eMBMS session is activated + +<tmgi>: string type in hex format; value is the Temporary Mobile Group Identity allocated to a particular eMBMS bearer service. Refer 3GPP TS 24.008 [8], clause 10.5.6.13. + +<embms\_session\_id>: integer type; value is the eMBMS Session Identity, which together with TMGI identifies a specific eMBMS session. Refer 3GPP TS 29.061 [39], clause 17.7.11. + +### Implementation + +Optional + +## 14.2.3 eMBMS service configuration +CEMBMSSRV + +**Table 14.2.3-1: + CEMBMSRV parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CEMBMSSRV=<n>[, <embms_service>[, <tmgi>]]] | [+CEMBMSSRV: <service_type>, <no_services_info>, <tmgi>[, <embms_session_id>[, <tmgi>[, <embms_session_id>[...]]]]]<br><br>[<CR><LF>[+CEMBMSSRV: <service_type>, <no_services_info>, <tmgi>[, <embms_session_id>[, <tmgi>[, <embms_session_id>[...]]]]]<br><br>[...]]]]]<br><br>+CME ERROR: <err> | +| +CEMBMSSRV? | +CEMBMSSRV: <n> | +| +CEMBMSSRV=? | +CEMBMSSRV: (list of supported <n>s) ,<br>(list of supported <embms_service>s) | + +Set command is used for querying and listening for service change indications and to control the presentation of following unsolicited service result code in the terminal + ++CEMBMSSRVI: <service\_type>, <no\_services\_info>, <tmgi>[, <embms\_session\_id>[, <tmgi>[, <embms\_session\_id>[...]]]] reporting eMBMS service information TMGI and eMBMS Session Identity. + +If this command is issued when eMBMS is not active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +Read command returns the result code settings of the terminal. + +Test command returns values supported as a compound value. + +### Defined values + +<n>: integer type; provides an option to control the unsolicited presentation on TE/MT. + +- 0 disable eMBMS unsolicited result code +- 1 enable eMBMS unsolicited result code + +<embms\_service>: integer type; provides an option to query and configure eMBMS services. The MT should use the value 4 as the default value. + +- 0 query eMBMS services available for use by the MT +- 1 query eMBMS services being used by the MT +- 2 configure eMBMS service for use by the MT +- 3 deconfigure eMBMS service for use by the MT +- 4 keep current configuration of eMBMS services used by the MT + +<service\_type>: integer type; indicates whether the eMBMS service is available for use or is being used by the mobile + +- 0 eMBMS service available for use by the MT + +- 1 eMBMS service being used by the MT + +<no\_services\_info>: integer type; number of eMBMS services for which information is reported for a particular <service\_type> + +<tmgi>: string type in hex format; value is the Temporary Mobile Group Identity allocated to a particular eMBMS bearer service. Refer 3GPP TS 24.008 [8], clause 10.5.6.13. + +<embms\_session\_id>: integer type; value is the optional MBMS Session Identity, which together with TMGI identifies a specific MBMS session. Refer 3GPP TS 29.061 [39], clause 17.7.11. + +## Implementation + +Optional + +### 14.2.4 Enter eMBMS data state +CEMBMSDATA + +**Table 14.2.4-1: +CEMBMSDATA parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------|----------------------| +| +CEMBMSDATA=<embms_session_id>[, <tmgi>] | +CME ERROR: <err> | +| +CEMBMSDATA=? | | + +## Description + +Set command is used to enter eMBMS data state by configuring the channel for data transfer for the specified eMBMS session. MT does not process any further AT commands after entering the eMBMS data state. The MT exits the eMBMS data state once the eMBMS data transfer is complete or the eMBMS session becomes inactive. + +If this command is issued when <embms\_session\_id> or <tmgi> fail to identify an existing eMBMS session, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +If this command is issued when eMBMS is not active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +## Defined values + +<embms\_session\_id>: integer type; value is the eMBMS Session Identity, which together with TMGI identifies a specific eMBMS session. Refer 3GPP TS 29.061 [39], clause 17.7.11. + +<tmgi>: string type in hex format; value is the Temporary Mobile Group Identity allocated to a particular eMBMS bearer service. Refer 3GPP TS 24.008 [8], clause 10.5.6.13. + +## Implementation + +Optional + +### 14.2.5 eMBMS counting procedure +CEMBMSCNT + +**Table 14.2.5-1: +CEMBMSCNT parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------|---------------------------------------| +| CEMBMSCNT=<tmgi>[, <tmgi>[, ...]] | +CME ERROR: <err> | +| CEMBMSCNT? | +CEMBMSCNT: <tmgi>, [, <tmgi>[, ...]] | +| CEMBMSCNT=? | | + +## Description + +Set command is used to set the list of TMGIs for which the user is interested in receiving eMBMS services. Refer to 3GPP TS 36.331 [86] clause 5.8.4.1 for MBMS Counting Procedure. + +If this command is issued when eMBMS is not active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +Read command is used to get the list of TMGI's from which the user is interested in receiving eMBMS services. + +#### Defined values + +<tmgi>: string type in hex format; value is the Temporary Mobile Group Identity allocated to a particular eMBMS bearer service. Refer 3GPP TS 24.008 [8], clause 10.5.6.13. + +#### Implementation + +Optional + +### 14.2.6 eMBMS Service Area Identities +CEMBMSSAI + +**Table 14.2.6-1: +CEMBMSSAI parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CEMBMSSAI=[<n>[, <embms_priority_flag>[, <earfcn_cnt>[, <earfcn>[, <earfcn>[, ...]]]]]<br>[, <sai_cnt>[, <sai>[, <sai>[, ...]]]]] | +CME ERROR: <err> | +| +CEMBMSSAI? | +CEMBMSSAI: USERDEF <n>, <embms_priority_flag>, <earfcn_cnt>[, <earfcn>[, <earfcn>[, ...]]]<br>+CEMBMSSAI: FCNT <embms_priority_flag>, <inter_frequency_cnt><br>+CEMBMSSAI: INTER <earfcn>, <sai_cnt>[, <sai>[, <sai>[, ...]]]<br>+CEMBMSSAI: INTRA <sai_cnt>, <sai>[, <sai>[, ...]] | +| +CEMBMSSAI=? | +CEMBMSSAI: (list of supported <n>s) , (list of supported <embms_priority_flag>s) | + +Set command sets the priority of eMBMS reception over unicast reception, the eMBMS frequencies the user is interested to receive and the SAIs corresponding to neighbor frequencies. When <n=1>, unsolicited result codes report the SAI of the current and the neighboring carrier frequencies provided by the network through SystemInformationBlockType15 (SIB-15) according to 3GPP TS 36.331 [86] clause 6.3.1. + +The unsolicited result code +CEMBMSSAI: FCNT <embms\_priority\_flag>, <inter\_frequency\_cnt> reports the priority of eMBMS reception over unicast reception and the number of neighboring frequencies that provide eMBMS services. + +The unsolicited result code +CEMBMSSAI: INTER <earfcn>, <sai\_cnt>[, <sai>[, <sai>[, ...]]] reports the SAI in the neighboring frequencies. + +The unsolicited result code +CEMBMSSAI: INTRA <sai\_cnt>, <sai>[, <sai>[, ...]] reports the SAI in the current frequency. + +If this command is issued when eMBMS is not active, +CME ERROR is returned. Refer clause 9.2 for possible <err> values. + +Read command returns the current settings of <n> and <embms\_priority\_flag> in the MT. + +Test command returns values supported as compound values. + +## Defined values + +<n>: integer type; provides an option to control the unsolicited presentation on TE/MT. + +- 0 disable eMBMS unsolicited result code +- 1 enable eMBMS unsolicited result code + +<embms\_priority\_flag>: integer type; indicates the priority of eMBMS reception over unicast reception. + +- 0 the unicast reception shall have priority over eMBMS reception +- 1 the eMBMS reception shall have priority over unicast reception + +<earfcn>: integer type; indicates the eMBMS frequency the user is interested to receive. It's the carrier frequency of the LTE cell designated by the EUTRA Absolute Radio Frequency Channel Number (EARFCN), valid range: 0..0xFFFF (refer 3GPP TS 36.101 [154], clause 5.7.3). + +<earfcn\_cnt>: integer type; indicates the count of <earfcn> reported. The maximum possible value is 32. + +<inter\_frequency\_cnt>: integer type; indicates the number of inter frequencies that will be set or reported. + +<sai>: integer type; indicates the SAI in corresponding downlink carrier frequencies. + +<sai\_cnt>: integer type; indicates the count of <sai> being set or reported. The maximum value is 128. + +## Implementation + +Optional. + +--- + +# 15 Commands for UE test functions + +## 15.1 General + +This clause defines AT commands that a TE can use to control MT test loop function for UE test loop and UTC time reset as specified in 3GPP TS 36.509 [142]. + +The UE test loop function provides access to isolated functions of the UE via the radio interface without introducing new physical interfaces just for the reason of conformance testing. The UE test loop function is activated by transmitting the appropriate TC message to the UE. The +CATM command activates and deactivates the UE test mode procedure and sets the UE into test loop mode. The +CCUTLE command opens and closes the UE test loop mode E function in the UE for either transmitting or receiving of V2X communication packets. Only UE test loop mode E is supported by AT commands. + +The +CUSPCREQ command requests the UE to report the counter of successful reception of sidelink PSCCH transport blocks, STCH PDCP SDU packets and PSSCH transport blocks. + +The +CUTCR command resets the UTC time previously calculated from GNSS in the UE. + +The +CCBRREQ command requests the UE to report the channel busy ratio (CBR). + +The +CV2XDTs command triggers the UE to start or stop sending V2X data over E-UTRA or NR PC5. + +The +CSPSAIR command requests the UE to send E-UTRA or NR UEAssistanceInformation message to request SPS grant from eNB. + +## 15.2 Activate test mode +CATM + +**Table 15.2-1: +CATM parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------------|------------------------------------------------------------------------------| +| +CATM=[<status>[, <test_loop_mode>]] | +CME ERROR: <err> | +| +CATM? | +CATM: <status>[, <test_loop_mode>] | +| +CATM=? | +CATM: (list of supported <status>s) , (list of supported <test_loop_mode>s) | + +### Description + +The set command is used to activate or deactivate the UE test mode according to UE test mode procedures as defined in 3GPP TS 36.509 [142] clause 5.3.2 and clause 5.3.3 for V2X over E-UTRA PC5, and in 3GPP TS 38.509 [178] clause 5.2.2 and clause 5.2.3 for V2X over NR PC5. When <status>=1, the set command activates the UE test mode and sets the UE in test loop mode. The parameter <test\_loop\_mode> must be included to indicate the UE test loop mode. When <status>=0, the set command deactivates the UE test mode. Refer clause 9.2 for possible <err> values. + +NOTE: Only UE test loop mode E is supported by AT commands. + +The read command returns the current UE test mode activation and UE test loop mode statuses. + +The test command returns values supported as compound values. + +### Defined values + +<status>: integer type. Indicates the state of UE test mode. + +- 0 deactivated +- 1 activated + +<test\_loop\_mode>: integer type. Indicates the UE test loop mode. + +- 1 UE test loop mode E + +### Implementation + +Optional. + +## 15.3 Close UE test loop mode E +CCUTLE + +**Table 15.3-1: +CCUTLE parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CCUTLE=<status>[, <direction>[, <format>, <length>, <monitor_list>]] | +CME ERROR: <err> | +| +CCUTLE? | +CCUTLE: <status>[, <direction>[, <format>, <length>, <monitor_list>, <sl_mimo>]] | +| +CCUTLE=? | +CCUTLE: (list of supported <status>s) , (list of supported <direction>s) , (list of supported <format>s) (maximum supported <length>), (list of supported <sl_mimo>s) | + +## Description + +The set command is used to close or open the UE test loop mode E according to UE test loop procedures as defined in 3GPP TS 36.509 [142] clause 5.4.2, clause 5.4.4c and clause 5.4.5 for V2X over E-UTRA PC5, and in 3GPP TS 38.509 [178] clause 5.3.2, clause 5.3.3 and clause 5.3.4.3. The AT command is only applicable when test mode is activated, see clause 15.2. The <status> indicates whether the UE test loop mode E is closed or opened. If <status>=0, the parameters <direction>, <format>, <length> and <monitor\_list> are as required provided to configure UE test loop mode E. + +The UE test loop mode E provides means for either transmitting or receiving of V2X communication packets, and the <direction> indicates the direction of communication under test. For communication receive operation, <direction>=0 and the UE test loop mode E provides counting of successfully received STCH PDCP SDUs for V2X over E-UTRA PC5 or STCH SDAP SDUs for V2X over NR PC5, PSCCH transport blocks and PSSCH transport blocks. The parameters <format>, <length> and <monitor\_list> must be provided. For communication transmit operation, <direction>=1 and the UE test loop mode E provides trigger for transmission of IP packets for V2X communication message on STCH. The parameters <format>, <length> and <monitor\_list> are not used and ignored if received. The parameter <sl\_mimo> indicates the number of spatial layer(s) used for NR PSSCH transmission for UE which supports SL MIMO, and is not used and ignored if UE doesn't support SL MIMO. All parameters are discarded when <status>=1 or when the UE test mode is deactivated. + +The read command returns the current settings. + +The test command returns values supported as compound values. + +## Defined values + +<status>: integer type. Indicates the state of UE test loop E. + +- 0 closed +- 1 opened + +<direction>: integer type. Indicates the direction of communication under test. + +- 0 communication receive +- 1 communication transmit + +<format>: integer type. Indicates the format of the <monitor\_list> parameter. + +- 1 binary format + +<length>: integer type. Indicates the number of 24 bit Destination Layer-2 IDs in the parameter <monitor\_list>. + +<monitor\_list>: string of octets. This parameter contains all 24 bit Destination Layer-2 IDs to monitor for V2X communication. The type of string is in the format as specified by <format>. The number of 24 bit Destination Layer-2 IDs is given by <length>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +<sl\_mimo>: integer type. Indicates the number of spatial layer(s) used for NR PSSCH transmission when <direction>=1. + +- 0 1 layer +- 1 2 layers + +## Implementation + +Optional. + +## 15.4 UE sidelink packet counter request +CUSPCREQ + +**Table 15.4-1: +CUSPCREQ action command syntax** + +| Command | Possible response(s) | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CUSPCREQ | +CUSPCREQ: [<type1>, <format>, <length1>, <counter1>],<br>[<type2>, <format>, <length2>, <counter2>]<br>,<br>[<type3>, <format>, <length3>, <counter3>]<br><br>+CME ERROR: <err> | +| +CUSPCREQ=? | | + +### Description + +The set command is used to request the UE to report the counter of successful reception of sidelink PSCCH transport blocks, STCH PDCP SDU packets and PSSCH transport blocks according to the ProSe Packet Counter reporting procedure as defined in 3GPP TS 36.509 [142] clause 5.7 for ProSe or V2X over E-UTRA PC5 and/or sidelink PSCCH transport blocks, STCH SDAP SDU packets and/or PSSCH transport blocks according to the ProSe Packet Counter reporting procedure as defined in 3GPP TS 38.509 [178] clause 5.9 for V2X over NR PC5. The AT command is only applicable when test mode is activated, see clause 15.2. Refer clause 9.2 for possible <err> values. + +### Defined values + +<type1>: integer type. Indicates the type of V2X communication. + +- 1 E-UTRA PSCCH transport blocks +- 2 NR PSCCH transport blocks + +<type2>: integer type. Indicates the type of V2X communication. + +- 1 E-UTRA STCH PDCP SDU packets +- 2 NR STCH SDAP SDU packets + +<type3>: integer type. Indicates the type of V2X communication. + +- 1 E-UTRA PSSCH transport blocks +- 2 NR PSSCH transport blocks + +<format>: integer type. Indicates the format of the requested packet counter. + +- 1 binary format + +<length1>: integer type. Indicates the number of octets of the <counter1> information element. + +<length2>: integer type. Indicates the number of octets of the <counter2> information element. + +<length3>: integer type. Indicates the number of octets of the <counter3> information element. + +<counter1>: string of octets. Indicates the counter value of E-UTRA PSCCH transport blocks when <type1>=1 and of NR PSCCH transport blocks when <type1>=2. The type of string is in the format as specified by <format>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +<counter2>: string of octets. Indicates the counter value of E-UTRA STCH PDCP SDU packets when <type2>=1 and of NR STCH SDAP SDU packets when <type2>=2. The type of string is in the format as specified by <format>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +<counter3>: string of octets. Indicates the counter value of E-UTRA PSSCH transport blocks when <type3>=1 and of NR PSSCH transport blocks when <type3>=2. The type of string is in the format as specified by <format>. The parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +## 15.5 UTC time reset +CUTCR + +**Table 15.5-1: +CUTCR action command syntax** + +| Command | Possible response(s) | +|----------|----------------------| +| +CUTCR | +CME ERROR: <err> | +| +CUTCR=? | | + +#### Description + +The set command is used to reset the current UTC time that has been calculated from GNSS in the UE as defined in 3GPP TS 36.509 [142] clause 5.5.3. This allows the UE to rapidly reacquire GNSS and calculate a new value of UTC time. The UE can optionally retain the information that may aid rapid reacquisition of GNSS and the calculation of a new value of UTC time. The AT command is only applicable when test mode is activated, see clause 15.2. Refer clause 9.2 for possible <err> values. + +NOTE: This command does not affect functionality provided by other AT commands defined in clauses other than clause 15. + +#### Defined values + +None. + +#### Implementation + +Optional. + +## 15.6 Channel busy ratio request +CCBRREQ + +**Table 15.6-1: +CCBRREQ action command syntax** + +| Command | Possible response(s) | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CCBRREQ[=<pc5_type>] | when <pc5_type>=0 (or omitted) and command successful:<br>+CCBRREQ: <cbr-pssch>[, <cbr-pscch>]<br><br>when <pc5_type>=1 and command successful:<br>+CCBRREQ: <nr-cbr><br><br>+CME ERROR: <err> | +| +CCBRREQ=? | | + +#### Description + +The set command is used to request the UE to report the Channel busy ratio (CBR) for V2X communication over E-UTRA PC5 measured as specified in 3GPP TS 36.214 [167] clause 5.1.30 or over NR PC5 measured as specified in 3GPP TS 38.215 [179] clause 5.1.27. The AT command is only applicable when test mode is activated, see clause 15.2. Refer clause 9.2 for possible <err> values. + +### Defined values + +<PC5\_type>: integer type. Indicates the RAT type of PC5 interface. + +- 0 E-UTRA PC5 +- 1 NR PC5 + +<cbr-pssch>: integer type. Indicates the CBR measured on the PSSCH for V2X communication over E-UTRA PC5. Value 0 corresponds to CBR=0.0, value 1 corresponds to CBR=0.01, value 2 corresponds to CBR=0.02 and so on. + +<cbr-pscch>: integer type. Indicates the CBR measured on the E-UTRA PSCCH. Value 0 corresponds to CBR=0.0, value 1 corresponds to CBR=0.01, value 2 corresponds to CBR=0.02 and so on. This parameter is only returned by the UE if the PSSCH and the PSCCH are transmitted in non-adjacent resource blocks as specified in 3GPP TS 36.214 [167] clause 5.1.30. + +<nr-cbr>: integer type. Indicates the CBR measured on the PSSCH for V2X communication over NR PC5. Value 0 corresponds to CBR=0.0, value 1 corresponds to CBR=0.01, value 2 corresponds to CBR=0.02 and so on. + +### Implementation + +Optional. + +## 15.7 V2X data transmission over PC5 +CV2XDTs + +**Table 15.7-1: +CV2XDTs parameter command syntax** + +| Command | Possible response(s) | +|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| +CV2XDTs=<action>[, <data_size>, <periodicity>, <pc5_type>] | +CME ERROR: <err> | +| +CV2XDTs? | +CV2XDTs: <action>[, <data_size>, <periodicity>] [, <pc5_type>] | +| +CV2XDTs=? | +CV2XDTs: (list of supported <action>s) [, (maximum supported <data_size>), (minimum supported <periodicity>)] [, list of supported <pc5_type> s] | + +### Description + +The set command is used to trigger the UE to start or stop sending V2X data over PC5 as defined in 3GPP TS 36.213 [166] clause 14. The AT command is only applicable when test mode is activated, see clause 15.2. The <action> indicates whether the UE shall start or stop sending data. If <action>=1, the parameters <data\_size> and <periodicity> must be provided. All parameters are discarded when <action>=0 or when the UE test mode is deactivated. + +The read command returns the current settings. + +The test command returns values supported as compound values. + +### Defined values + +<action>: integer type. Indicates whether the UE shall start or stop sending V2X data over PC5. + +- 0 stop sending data +- 1 start sending data + +<data\_size>: integer type. Indicates how many bytes of data the UE shall send over PC5. + +NOTE: The data sent by the UE consists of a random bit string. How it is generated is up to UE implementation. + +<periodicity>: integer type. Indicates with which periodicity, in milliseconds, the UE shall transmit the number of bytes indicated in <data\_size>. + +<pc5\_type>: integer type. indicates with the RAT type of PC5 over which the UE shall transmit V2X data. + +- 0 E-UTRA PC5 +- 1 NR PC5 + +### Implementation + +Optional. + +## 15.8 SPS assistance information request +CSPSAIR + +**Table 15.8-1: +CSPSAIR action command syntax** + +| Command | Possible Response(s) | +|----------------------|--------------------------------------------| +| +CSPSAIR=<interface> | +CME ERROR: <err> | +| +CSPSAIR=? | +CSPSAIR: (list of supported <interface>s) | + +### Description + +The set command is used to request the UE to send the UEAssistanceInformation message to request SPS grant from eNB as specified in 3GPP TS 36.331 [86] clause 5.6.10.2 or from gNB as specified in 3GPP TS 38.331 [160] clause 5.7.4.2. The set command is only applicable when test mode is activated, see clause 15.2. When <interface>=0, the UE shall send the UEAssistanceInformation message to request UL SPS grant for V2X communication over LTE-Uu from eNB. When <interface>=1, the UE shall send the UEAssistanceInformation message to request SL SPS grant for V2X communication over E-UTRA PC5 from eNB. When <interface>=2, the UE shall send the UEAssistanceInformation message to request UL SPS grant for V2X communication over NR-Uu from gNB. When <interface>=1, the UE shall send the UEAssistanceInformation message to request SL SPS grant for V2X communication over NR PC5 from gNB. + +Refer clause 9.2 for possible <err> values. + +Test command returns the values supported as a compound value. + +### Defined values + +<interface>: integer type. Indicates the interface type for which UE requests SPS grant from eNB. + +- 0 request UL SPS grant for V2X communication over LTE-Uu from eNB +- 1 request SL SPS grant for V2X communication over E-UTRA PC5 from eNB +- 2 request UL SPS grant for V2X communication over NR-Uu from gNB +- 3 request SL SPS grant for V2X communication over NR PC5 from gNB + +### Implementation + +Optional. + +# 16 Commands for VAE layer configuration + +## 16.1 General + +This clause defines AT commands that a TE may use to control MT supporting VAE layer. The VAE layer supports V2X communication over LTE-Uu as defined in 3GPP TS 24.486 [172]. + +A comprehensive set of VAE layer-specific commands is defined to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new VAE layer feature options and interface protocols, merely by defining new values for many of the parameters. The commands use the extended information and error message capabilities described in the present specification. + +The +CVAEACT command activate or deactivate the VAE layer support in the MT by performing the V2X service discovery procedure according to 3GPP TS 24.486 [172] clause 6.6. Once the VAE layer is enabled, then the MT can request the registration of V2X service identifier(s) by performing the V2X UE registration procedure according to 3GPP TS 24.486 [172] clause 6.2 using the +CVAEREG command. + +## 16.2 Commands specific to VAE layer + +### 16.2.1 VAE layer configuration in MT +CVAEACT + +**Table 16.2.1-1: +CVAEACT parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------|------------------------------------------------| +| +CVAEACT=<state>[, <V2X_UE_id> ] ] | +CME ERROR: <err> | +| +CVAEACT? | +CVAEACT: <state>, <setup_cfg> | +| +CVAEACT=? | +CVAEACT: <result>[, <service_discovery_data>] | + +#### Description + +Set command activates or deactivates the VAE layer support. + +When VAE layer support is activated the MT performs the V2X service discovery procedure according to 3GPP TS 24.486 [172] clause 6.6. + +When the MT announces that the MT's network registration status is "not registered, MT is not currently searching an operator to register" to EPS or "unknown" by issuing the unsolicited result code +CEREG to the TE, the TE deactivates the VAE layer support if it is activated. + +When the MT announces that the MT's network registration status is registered or attached to 5GS by issuing the unsolicited result code +C5GREG to the TE, the TE deactivates the VAE layer support if it is activated. + +If the V2X service discovery procedure fails, then +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +The read command returns the current activation states for all the defined PDP contexts. + +Read command returns the state of the VAE layer support and the current VAE layer configuration information in the MT according to 3GPP TS 24.486 [172] (e.g. the V2X UE service discovery data). + +If the requested state for any specified context cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. If the MT is not PS attached when the activation form of the command is executed, the MT first performs a PS attach and then attempts to activate the specified contexts. If the attach fails then the MT responds with ERROR or, if extended error responses are enabled, with the appropriate failure-to-attach error message. Refer clause 9.2 for possible <err> values. + +## Defined values + +<state>: integer type; specifies if VAE layer support is to be enabled or disabled in the MT. + +- 0 activate/active VAE layer support in MT. When VAE layer support is disabled MT is not receiving or consuming any VAE layer service +- 1 deactivate/deactivated VAE layer support in MT + +<V2X\_UE\_id>: string type; indicates the V2X UE identity to be used for enabling the VAE layer support. The <V2X\_UE\_id> is encoded as the value part of the V2X-UE-id element in 3GPP TS 24.486 [172], clause 8.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<result>: string type; indicates the result of enabling the VAE layer. The <result> is encoded as the value part of result element in 3GPP TS 24.486 [172], clause 8.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<service\_discovery\_data>: string type; indicates the service discovery data information when enabling the VAE layer support has been successful. The <service\_discovery\_data> is encoded as the value part of the service-discovery-data element in 3GPP TS 24.486 [172], clause 8.5, and each V2X service identifier is encoded as the value part of the V2X-service-id element as specified in clause 8.5, and each V2X application server address is encoded as the value part of the V2X-app-server-address element as specified in clause 8.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +## Implementation + +Optional. This command is only applicable to UEs supporting EPS. + +## 16.2.2 VAE layer registration +CVAEREG + +**Table 16.2.2-1: +CVAEREG parameter command syntax** + +| Command | Possible response(s) | +|----------------------------------------------------------------|---------------------------------------------| +| +CVAEREG=<V2X_UE_id>,<V2X_service_id>[,<V2X_service_id>[,...]] | +CME ERROR: <err><br><br>+CVAEREG: <result> | +| +CVAEREG=? | | + +## Description + +Set command enables the TE to request the registration of V2X service identifier(s) by using the VAE layer. + +When VAE layer support is active the MT performs the V2X UE registration procedure according to 3GPP TS 24.486 [172] clause 6.2. + +When the MT announces that the MT's network registration status is "not registered, MT is not currently searching an operator to register" to EPS or "unknown" by issuing the unsolicited result code +CEREG to the TE, the TE deactivates the VAE layer support if it is activated by using +CVAEACT. + +When the MT announces that the MT's network registration status is registered or attached to 5GS by issuing the unsolicited result code +C5GREG to the TE, the TE deactivates the VAE layer support if it is activated by using +CVAEACT. + +If this command is issued when VAE layer support is not active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +Test command returns values supported as a compound value. + +## Defined values + +<V2X\_UE\_id>: string type; indicates the V2X UE identity to be used for the registration of V2X service identifier(s). The <V2X\_UE\_id> is encoded as the value part of the V2X-UE-id element in + +3GPP TS 24.486 [172], clause 8.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<V2X\_service\_id>: string type; indicates the V2X service identifiers to be registered. The <V2X\_service\_id> is encoded as the value part of the V2X-service-id element in 3GPP TS 24.486 [172], clause 8.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<result>: string type; indicates the result of the registration of a V2X service which indicates a value either "success" or "fail". The <result> is encoded as the value part of result element in 3GPP TS 24.486 [172], clause 8.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +### Implementation + +Optional. This command is only applicable to UEs supporting EPS. + +--- + +## 17 Commands for UAE layer configuration + +### 17.1 General + +This clause defines AT commands that a TE may use to control MT supporting UAE layer. The UAE layer supports UAS application communication between the UE and the UAE server and UAS application communication among UEs over LTE-Uu or NR-Uu as defined in 3GPP TS 24.257 [186]. + +A comprehensive set of UAE layer-specific commands is defined to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new UAE layer feature options and interface protocols, merely by defining new values for many of the parameters. The commands use the extended information and error message capabilities described in the present specification. + +The +CUAEACT command activate or deactivate the UAE layer support in the MT. Once the UAE layer is enabled, then the MT can request the registration for receiving UAV application messages from the UAS application specific server by performing the UAS UE registration procedure according to 3GPP TS 24.257 [186] clause 6.4 using the +CUAEREG command. + +| | +|---------------------| +| *** Next Change *** | +|---------------------| + +### 17.2 Commands specific to UAE layer + +#### 17.2.1 UAE layer configuration in MT +CUAEACT + +**Table 17.2.1-1: +CUAEACT parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------|----------------------| +| +CUAEACT=[<state>[, <UAV_id>]] | +CME ERROR: <err> | +| +CUAEACT? | +CUAEACT: <state> | +| +CUAEACT=? | +CUAEACT: <result> | + +#### Description + +Set command activates or deactivates the UAE layer support in the MT. + +When the MT announces that the MT's network registration status is "not registered, MT is not currently searching an operator to register to" to EPS or 5GS, or "unknown" by issuing the unsolicited result code +CEREG or +C5GREG to the TE, the TE deactivates the UAE layer support if it is activated. + +Read command returns the state of the UAE layer support in the MT. + +Refer clause 9.2 for possible <err> values. + +#### Defined values + +<state>: integer type; specifies if UAE layer support is to be enabled or disabled in the MT. + +0 activate/active UAE layer support in MT. + +1 deactivate/deactivated UAE layer support in MT. When UAE layer support is disabled, the MT is not receiving or consuming any UAE layer services + +<UAV\_id>: string type; indicates the UAV identity to be used for enabling the UAE layer support. The <UAV\_id> is encoded as the value part of the UAV-id element in 3GPP TS 24.257 [186], clause 7.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<result>: string type; indicates the result of enabling the UAE layer support which indicates a value either "success" or "fail". This parameter shall not be subject to conventional character conversion as per +CSCS. + +#### Implementation + +Optional. + +\*\*\* Next Change \*\*\* + +## 17.2.2 UAE layer registration +CUAEREG + +**Table 17.2.2-1: +CUAEREG parameter command syntax** + +| Command | Possible response(s) | +|-------------------|-----------------------------------------| +| +CUAEREG=<UAV_id> | +CME ERROR: <err><br>+CUAEREG: <result> | +| +CUAEREG=? | | + +#### Description + +Set command enables the TE to request the registration for receiving UAV application messages from the UAS application specific server by using the UAE layer. + +When UAE layer support is active, the MT performs the UAS UE registration procedure according to 3GPP TS 24.257 [186] clause 6.4. + +When the MT announces that the MT's network registration status is "not registered, MT is not currently searching an operator to register to" to EPS or 5GS, or "unknown" by issuing the unsolicited result code +CEREG or +C5GREG to the TE, the TE deactivates the UAE layer support if it is activated by using +CUAEACT. + +If this command is issued when UAE layer support is not active, +CME ERROR is returned. Refer to clause 9.2 for possible <err> values. + +Test command returns values supported as a compound value. + +#### Defined values + +<UAV\_id>: string type; indicates the UAV identity to be used for the registration for receiving UAV application messages from the UAS application specific server. The <UAV\_id> is encoded as the value part of the UAV-id element in 3GPP TS 24.257 [186], clause 7.5. This parameter shall not be subject to conventional character conversion as per +CSCS. + +<result>: string type; indicates the result of the registration for receiving UAV application messages from the UAS application specific server which indicates a value either "success" or "fail". This parameter shall not be subject to conventional character conversion as per +CSCS. + +**Implementation** + +Optional. + +## 18 Commands for UAS configuration and operation + +### 18.1 General + +This clause defines AT commands that a TE may use to control MT supporting UAS services. The MT supporting UAS supports UUAA procedure and C2 authorization procedure as defined in 3GPP TS 24.501 [161] for 5GS and in 3GPP TS 24.301 [83] for EPS. + +A comprehensive set of UAS specific commands is defined to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new UAS feature options and interface protocols, merely by defining new values for many of the parameters. The commands use the extended information and error message capabilities described in this specification. + +The +CUUAAPT command requests the UE to transport the UUAA parameters to the network and to report the UUAA parameters received from the network as defined in 3GPP TS 24.501 [161] for 5GS and in 3GPP TS 24.301 [83] for EPS. + +The +CC2APT command requests the UE to transport the C2 authorization parameters to the network and to report the C2 authorization parameters received from the network as defined in 3GPP TS 24.501 [161] for 5GS and in 3GPP TS 24.301 [83] for EPS + +### 18.2 Commands specific to UAS services + +#### 18.2.1 UUAA parameter transport +CUUAAPT + +**Table 18.2.1-1: +CUUAAPT parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------|------------------------------------------------------------------| +| +CUUAAPT<br>=<n>,<CAA_level_UAV_id><br>[,<USS_addr>[,<UUAA_payload>]] | +CME ERROR: <err> | +| +CUUAAPT? | +CUUAAPT: [,<CAA_level_UAV_id>[,<UUAA_result>[,<UUAA_payload>]]] | +| +CUUAAPT=? | | + +#### Description + +The set command is used to request the MT to transport UUAA parameters to the network as specified in 3GPP TS 24.501 [161] for 5GS and in 3GPP TS 24.301 [83] for EPS. The unsolicited result code +CUUAAPT: [,<CAA\_level\_UAV\_id>[,<UUAA\_result>[,<UUAA\_payload>]]] reports the UUAA parameters received from the network. + +The read command is used to return the current value of unsolicited result code +CUUAAPT. + +Test command returns values supported as a compound value. + +#### Defined values + +<n> : Integer type + +0 disable presentation of the unsolicited result code + +- 1 enable presentation of the unsolicited result code ++CUUAAPT: [, <CAA\_level\_UAV\_id> [, <UUAA\_result> [, <UUAA\_payload>]]] +- <CAA\_level\_UAV\_id>: string type; contains the CAA-level UAV ID. <CAA\_level\_UAV\_id> is encoded as the value part of the Service-level device ID as specified in 3GPP TS 24.501 [161] clause 9.11.2.11. +- <USS\_addr>: string type; contains the IP address or FQDN. <USS\_addr> is encoded as the value part of the Service-level-AA server address as specified in 3GPP TS 24.501 [161] clause 9.11.2.12. +- <UUAA\_payload>: string type; contains the application-level payload for UUAA procedure. <UUAA\_payload> is encoded as the value part of the Service-level-AA payload as specified in 3GPP TS 24.501 [161] clause 9.11.2.13. +- <UUAA\_result>: integer type; contains the result of UUAA procedure. <UUAA\_result> is encoded corresponding to the value part of the SLAR bits of the Service-level-AA response as specified in 3GPP TS 24.501 [161] clause 9.11.2.14. +- 0 UUAA completed successfully + - 1 UUAA was not successful or revoked + +## Implementation + +Optional. + +## 18.2.2 C2 authorization parameter transport +CC2APT + +**Table 18.2.2-1: +CC2APT parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| + CC2APT<br>=<n>, <CAA_level_UAV_id><br>[, <C2_authorization_payload>] | +CME ERROR: <err> | +| + CC2APT? | +CC2APT: [, <CAA_level_UAV_id> [, <C2_authorization_payload> [, <C2_auth_result>]]] | +| + CC2APT=? | | + +## Description + +The set command is used to request the MT to transport C2 authorization parameters to the network as specified in 3GPP TS 24.501 [161] for 5GS and in 3GPP TS 24.301 [83] for EPS. The unsolicited result code +CC2APT: [, <CAA\_level\_UAV\_id> [, <C2\_authorization\_payload> [, <C2\_auth\_result>]]] reports the C2 authorization parameters received from the network. + +The read command is used to return the current value of unsolicited result code +CC2APT. + +Test command returns values supported as a compound value. + +## Defined values + +- <n>: Integer type +- 0 disable presentation of the unsolicited result code + - 1 enable presentation of the unsolicited result code ++CC2APT: [, <CAA\_level\_UAV\_id> [, <C2\_authorization\_payload> [, <C2\_auth\_result>]]] +- <CAA\_level\_UAV\_id>: string type; contains the CAA-level UAV ID. <CAA\_level\_UAV\_id> is encoded as the value part of the Service-level device ID as specified in 3GPP TS 24.501 [161] clause 9.11.2.11. + +<C2\_authorization\_payload>: string type; contains the application-level payload which may include UAV-C pairing information, flight authorization information, C2 session security information, if available. + +<C2\_authorization\_payload> is encoded as the value part of Service-level-AA payload as specified in 3GPP TS 24.501 [161] clause 9.11.2.13. + +<C2\_auth\_result>: integer type; contains the result of C2 authorization procedure. <C2\_auth\_result> is encoded corresponding to the value part of the C2AR bits of the Service-level-AA response as specified in 3GPP TS 24.501 [161] clause 9.11.2.14. + +- 0 C2 authorization completed successfully +- 1 C2 authorization was not successful or revoked + +#### Implementation + +Optional. + +## 19 Commands for edge enabling layer operation + +### 19.1 General + +This clause defines AT commands that a TE may use to control MT supporting the edge enabling layer and EDGE-5 interface as specified in 3GPP TS 23.558 [187]. + +A comprehensive set of edge enabling layer-specific commands is defined to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new edge enabling layer feature options and interface protocols, merely by defining new values for many of the parameters. The commands use the extended information and error message capabilities described in the present specification. + +The +CE5EASD command provides the edge enabling layer with an application client profile and optionally EAS discovery filter(s) to be used for performing EAS discovery by the MT as specified in 3GPP TS 24.558 [190]. The +CE5ACRREQ command requests the edge enabling layer to initiate an ACR procedure by the MT as specified in 3GPP TS 24.558 [190]. The +CE5EECSRV command enables or disables the edge enabling layer to notify a list of EEC service(s) available at the edge enabling layer in the MT as specified in 3GPP TS 23.558 [187]. The +CE5UEIDREQ command requests the edge enabling layer to perform a UE identifier API procedure by the MT as specified in 3GPP TS 23.558 [187]. + +### 19.2 Commands specific to edge enabling layer + +#### 19.2.1 Edge-5 EAS discovery +CE5EASD + +**Table 19.2.1-1: +CE5EASD parameter command syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------|-------------------------------------------------| +| +CE5EASD=<AC-profile>,<AC-security-credential>[,<EAS-characteristics>] | +CME ERROR: <err><br>+CE5EASD: <discovered-EAS> | +| +CE5EASD? | | +| +CE5EASD=? | | + +#### Description + +Set command provides an application client profile and the security credential associated with the application client profile, and optionally EAS discovery filter. If the security credential associated with the application client is valid, then the edge enabling layer performs an EAS discovery procedure and returns the EAS profile as defined in 3GPP TS 23.558 [187] clause 8.14.2.3. + +If the edge enabling layer fails to check the validity of the set command based on the security credential of the application client, then +CME ERROR: 3 (Operation not allowed) is returned. For other reason for failure of processing the request, refer to clause 9.2.1 for possible <err> values. + +#### Defined values + +<AC-profile>: string type; indicate the application client profile to be used for performing EAS discovery procedure by the edge enabling layer in the MT. The <AC-profile> is encoded as ACProfile data type defined in 3GPP TS 24.558 [190] clause 6.2.5.2.3. + +<AC-security-credential>: string type; indicates the security credential associated with the application client profile to be used for checking validity of the request by the edge enabling layer in the MT. Encoding of the <AC-security-credential> is out of scope of this specification. + +<EAS-characteristics>: string type; indicates the list of the EAS characteristics that the TE is interested in. The <EAS-characteristics> is encoded as EasCharacteristics data type defined in 3GPP TS 24.558 [190] clause 6.3.5.2.7. + +<discovered-EAS>: string type; indicates the result of EAS discovery procedure performed by the edge enabling layer in the MT for the request of the TE, as specified in 3GPP TS 24.558 [190] clause 5.3. the <discovered-EAS> is encoded as DiscoveredEas data type defined in 3GPP TS 24.558 [190] clause 6.3.5.2.8. + +#### Implementation + +Optional. This command is only applicable to UEs supporting edge enabling layer. + +### 19.2.2 Edge-5 ACR trigger request +CE5ACRREQ + +**Table 19.2.2-1: +CE5ACRREQ parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------|-------------------------------------------| +| +CE5ACRREQ=<AC-profile>,<AC-security-credential>,<Requested-ACR-action>,<S-EAS-info>[,<T-EAS-endpoint>] | +CME ERROR: <err><br>+CE5ACRREQ: <result> | +| +CE5ACRREQ? | | +| +CE5ACRREQ=? | | + +#### Description + +Set command provides an application client profile, the security credential associated with the application client profile, the indication of ACR action (i.e., whether ACR detection or ACR initiation is requested), the EAS identifier to which the ACR request is related, and optionally the selected target EAS endpoint address. If the security credential associated with the application client is valid, then the edge enabling layer in the MT performs ACR procedure according to the indication of ACR action in the request as defined in 3GPP TS 23.558 [187] clause 8.14.2.4. + +If the edge enabling layer fails to check the validity of the set command based on the security credential of the application client, then +CME ERROR: 3 (Operation not allowed) is returned. For other reason for failure of processing the request, refer to clause 9.2.1 for possible <err> values. + +#### Defined values + +<AC-profile>: string type; indicate the application client profile to be used for performing EAS discovery procedure by the edge enabling layer in the MT. The <AC-profile> is encoded as ACProfile data type defined in 3GPP TS 24.558 [190] clause 6.2.5.2.3. + +<AC-security-credential>: string type; indicates the security credential associated with the application client profile to be used for checking validity of the request by the edge enabling layer in the MT. Encoding of the <AC-security-credential> is out of scope of this specification. + +<Requested-ACR-action>: integer type; indicates whether the request is for ACR detection or for ACR initiation. The edge enabling layer in the MT determines takes this indication into account for performing ACR procedure as specified in 3GPP TS 23.558 [187] clause 8.14.2.4. + +- 0 ACR detection is requested +- 1 ACR initiation is requested + +<S-EAS-info>: string type; indicates the identifier of EAS to which the ACR request is related. + +<T-EAS-endpoint>: string type; indicates the endpoint address of the selected EAS by the TE. <T-EAS-endpoint> is encoded as tEASEndpoint of the AcrInitReq data type defined in 3GPP TS 24.558 [190] clause 6.5.5.2.3. + +<result>: integer type; indicates the result of ACR request for the requested ACR action. + +- 0 the ACR request was successful and the edge enabling layer in the MT is processing the requested ACR operation +- 1 the ACR request failed + +### Implementation + +Optional. This command is only applicable to UEs supporting edge enabling layer. + +## 19.2.3 Edge-5 EEC services subscription +CE5EECSRv + +**Table 19.2.3-1: +CE5EECSRv parameter command syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| +CE5EECSRv=<subscribe>, <AC-profile>, <AC-security-credential>, <required-EEC-services>[, <ACR-operation-type>, <CAS-info>] | +CE5EECSRv: <response>[, <subs-id>, <expiry-time>, <EAS-discovery-ind>, <EAS-dynamic-info-ind>, <ACR-ind>[, <EAS-info-list>]]<br>+CME ERROR: <err> | +| +CE5EECSRv? | +CE5EECSRv: <subscribe> | +| +CE5EECSRv=? | +CE5EECSRv: (list of supported <subscribe> values), <EAS-discovery-ind>, <EAS-dynamic-info-ind>, <ACR-ind> | + +### Description + +Set command enables the edge enabling layer in the MT to send notifications to the TE. The parameter <subscribe> enables or disables notification by an unsolicited result code. Relevant parameters for the EEC services subscription are provided in the unsolicited result code +CE5EECSRv: <subs-id>[, <EAS-discovery-info>, <EAS-dynamic-info>, <EAS-info-list>[, <ACR-status>[, <target-EAS-info>]]]. + +Refer to clause 9.2.1 for possible <err> values. + +Read command returns the current value. + +Test command returns the supported values as a compound value. + +### Defined values + +<subscribe>: integer type. Enables and disables the subscription for EEC services. + +- 0 Disables the subscription request. +- 1 Subscribe for notifications of EAS discovery. +- 2 Subscribe for notifications of ACR. + +<AC-profile>: string type; indicate the application client profile to be used for performing EAS discovery procedure by the edge enabling layer in the MT. The <AC-profile> is encoded as ACProfile data type defined in 3GPP TS 24.558 [190] clause 6.2.5.2.3. + +<AC-security-credential>: string type; indicates the security credential associated with the application client profile to be used for checking validity of the request by the edge enabling layer in the MT. Encoding of the <AC-security-credential> is out of scope of this specification. + +<required-EEC-services>: string type. If the value of <subscribe> is set to 1, <required-EEC-services> contains either or both: + +- the list of EAS characteristics which is encoded as EasCharacteristics data type defined in 3GPP TS 24.558 [190] clause 6.3.5.2.7; and +- the list of EAS dynamic information filter which is encoded as EasDynamicInfoFilter data type defined in 3GPP TS 24.558 [190] clause 6.3.5.2.9 + +If the value of <subscribe> is set to 2, <required-EEC-services> contains: + +- the list of EAS information including the identifier of the EAS encoded as a easId of the AcrInitReq data type defined in 3GPP TS 24.558 [190] clause 6.5.5.2.3 and the endpoint address of the EAS encoded as a sEASEndpoint of the AcrInitReq data type defined in 3GPP TS 24.558 [190] clause 6.5.5.2.3; and +- optionally <ACR-operation-type> or <CAS-info>, or both. + +<ACR-operation-type>: integer type; indicates the requested ACR operation as specified in 3GPP TS 23.558 [187] clause 8.14.2.5.2. + +- 0 ACR notification +- 1 ACR monitoring +- 2 the edge enabling layer managed ACR + +<CAS-info>: string type; indicates the address of cloud application server encoded as URI. + +<response>: integer type; indicates the successful subscription or the failure of subscription. + +- 0 the subscription request was successful +- 1 the subscription request fails + +<subs-id>: integer type; indicates the subscription identifier corresponding to the subscription request + +<expiry-time>: integer type; indicates the time for subscription expiration with unit of seconds. The default value is implementation specific. + +<EAS-discovery-ind>: integer type; indicates that the edge enabling layer supports handling of EAS discovery to the TE. + +- 0 no support of EAS discovery handling +- 1 support of EAS discovery handling + +<EAS-dynamic-info-ind>: integer type; indicates that the edge enabling layer supports handling of EAS dynamic information subscription to the TE. + +- 0 no support of EAS dynamic information subscription handling +- 1 support of EAS dynamic information subscription handling + +<ACR-ind>: integer type; indicates that the edge enabling layer supports handling of ACR operation to the TE + +- 0 no support of ACR operation handling +- 1 support of ACR operation handling + +<EAS-info-list>: string type; contains the list of EAS information for ACR operation including the identifier of the EAS encoded as a easId of the AcrInitReq data type defined in 3GPP TS 24.558 [190] clause 6.5.5.2.3 and the endpoint address of the EAS encoded as a sEASEndpoint of the AcrInitReq data type defined in 3GPP TS 24.558 [190] clause 6.5.5.2.3. + +<EAS-discovery-info>: string type; contains a list of a discoveredEas data type as defined in 3GPP TS 24.558 [190] clause 6.3.5.2.8. + +<EAS-dynamic-info>: string type; contains a list of a discoveredEas data type as defined in 3GPP TS 24.558 [190] clause 6.3.5.2.8. + +<ACR-status>: integer type; indicates the status of ACR operation. + +- 0 the edge enabling layer in the MT detects a need for ACR +- 1 the edge enabling layer in the MT decides to perform ACR +- 2 the ACR is initiated +- 3 the ACR is in-progress +- 4 the ACR is completed + +<target-EAS-info>: string type. If the value of <ACR-status> is set to 4, it contains the information of target EAS as a result of ACR operation, which is encoded as a discoveredEas data type defined in 3GPP TS 24.558 [190] clause 6.3.5.2.8. + +## Implementation + +Optional. This command is only applicable to UEs supporting edge enabling layer. + +## 19.2.4 Edge-5 UE ID request +CE5UEIDREQ + +**Table 19.2.4-1: +CE5UEIDREQparameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| +CE5UEIDREQ=<security-credential>,<EAS-id1>[, <EAS-id2>[...]] | +CE5UEIDREQ: <response>[, list of <CR><LF><UE-ID>, <UE-ID-type>, <EAS-id>]<br>+CME ERROR: <err> | +| +CE5UEIDREQ? | | +| +CE5UEIDREQ=? | | + +## Description + +Set command provides the security credential of the TE for requesting +CE5UEIDREQ, and the list of EAS identifier(s) to retrieve the associated application specific UE identifier. If the security credential is valid, then the edge enabling layer in the MT performs UE identifier API procedure for the EAS indicated in the request as defined in 3GPP TS 23.558 [187] clause 8.14.2.6. + +If the edge enabling layer fails to check the validity of the set command based on the security credential in the request, then +CME ERROR: 3 (Operation not allowed) is returned. For other reason for failure of processing the request, refer to clause 9.2.1 for possible <err> values. + +## Defined values + +<security-credential>: string type; indicates the security credential of the TE for requesting +CE5UEIDREQ to be used for checking validity of the request by the edge enabling layer in the MT. Encoding of the <security-credential> is out of scope of this specification. + +<EAS-id>: string type; indicates application identifier of the EAS. + +<response>: integer type; indicates the result of the request. + +0 the UE identifier API procedure performed by the edge enabling layer in the MT was successful + +1 the UE identifier API procedure performed by the edge enabling layer in the MT failed + +<UE-ID>: string type; indicates the UE identifier corresponding to the <EAS-id>. + +<UE-ID-type>: integer type; indicates whether <UE-ID> is a 3GPP Core Network assigned UE ID (see 3GPP TS 23.501 clause 5.20) or Edge UE ID (see 3GPP TS 23.558 [187] clause 7.2.9) + +### Implementation + +Optional. This command is only applicable to UEs supporting edge enabling layer. + +## 19.2.5 Edge-5 AC registration +CE5REG + +**Table 19.2.5-1: +CE5REG parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| +CE5REG=<reg_req>,<AC-profile>,<AC-security-credential>[, [<EAS-characteristics>] [, <EEC-service-req>] [, <ECS-information>] [, <reg-id>]] | +CE5REG: <response>,<reg-id>,<allowed-EAS-service>[, <expiry-time>]<br>+CME ERROR: <err> | +| +CE5REG? | | +| +CE5REG=? | | + +### Description + +Set command provides an application client profile and the security credential associated with the application client profile, optionally a list of EAS discovery filter, optionally a list of the requested EEC services, and optionally an ECS address. If it is requested for AC registration update or for AC deregistration, the registration identifier allocated during the previous registration is included in the set command. + +If the edge enabling layer fails to check the validity of the set command based on the security credential of the application client, then +CME ERROR: 3 (Operation not allowed) is returned. For other reason for failure of processing the request, refer to clause 9.2.1 for possible <err> values. + +### Defined values + +<reg\_req>: integer type, indicates the type of the AC registration request: + +0 AC registration request + +1 AC registration update request + +2 AC deregistration request + +<AC-profile>: string type; indicate the application client profile to be used by the edge enabling layer in the MT. The <AC-profile> is encoded as ACProfile data type defined in 3GPP TS 24.558 [190] clause 6.2.5.2.3. + +<AC-security-credential>: string type; indicates the security credential associated with the application client profile to be used for checking validity of the request by the edge enabling layer in the MT. Encoding of the <AC-security-credential> is out of scope of this specification. + +<EAS-characteristics>: string type; indicates the list of the EAS characteristics that the TE is interested in. The <EAS-characteristics> is encoded as EasCharacteristics data type defined in 3GPP TS 24.558 [190] clause 6.3.5.2.7. + +<EEC-service-req>: integer type, indicates the requested EEC services: + +- 0 Request edge enabling layer to handle EAS discovery. +- 1 Request edge enabling layer to handle ACR. +- 2 Request edge enabling layer to handle both EAS discovery and ACR. + +<ECS-address>: string type which include a URI of the ECS endpoint address. + +<reg\_id>: string type, indicates the identifier of AC registration assigned by the edge enabling layer. + +<response>: integer type; indicates the result of the request. + +- 0 the request of AC registration indicated in <reg\_req> was successful +- 1 the request of AC registration indicated in <reg\_req> failed + +<allowed-EEC-service>: integer type, indicates the EEC services allowed to the AC: + +- 0 AC is allowed to use EAS discovery. +- 1 AC is allowed to use ACR. +- 2 AC is allowed to use both EAS discovery and ACR. + +<expiry-time>: integer type; indicates the time for AC registration expiration with unit of seconds. The default value is implementation specific. + +### Implementation + +Optional. This command is only applicable to UEs supporting edge enabling layer. + +## Annex A (normative): Summary of commands from other standards + +Summary of ITU-T Recommendation V.250 [14] commands applicable to the present document: + +**Table A.1: V.250 commands applicable to the present document** + +| Name | V.250 clause | Description | Clauses in the present document | +|-------|--------------|------------------------------------------------------------|---------------------------------| +| &C | 6.2.8 | Circuit 109 (Received line signal detector) Behaviour | 4.3 | +| &D | 6.2.9 | Circuit 108 (Data terminal ready) Behaviour | 4.3 | +| &F | 6.1.2 | Set to Factory-defined Configuration | 5.8/ 3 | +| +DR | 6.6.2 | Data Compression Reporting | 6.20 | +| +DS | 6.6.1 | Data Compression | 6.20 | +| +GCAP | 6.1.9 | Request Complete Capabilities List | 5.8 | +| +GCI | 6.1.10 | Country of Installation | 5.8 | +| +GMI | 6.1.4 | Request Manufacturer Identification | 5.8/ 5.1 | +| +GMM | 6.1.5 | Request Model Identification | 5.8/ 5.2 | +| +GMR | 6.1.6 | Request Revision Identification | 5.8/ 5.3 | +| +GOI | 6.1.8 | Request Global Object Identification | 5.8 | +| +GSN | 6.1.7 | Request Product Serial Number Identification | 5.8/ 5.4 | +| +ICF | 6.2.11 | DTE-DCE Character Framing | 4.3 | +| +IFC | 6.2.12 | DTE-DCE Local Flow Control | 4.3 | +| +ILRR | 6.2.13 | DTE-DCE Local Rate Reporting | 4.3 | +| +IPR | 6.2.10 | Fixed DTE Rate | 4.3 | +| A | 6.3.5 | Answer | 6.19/ 6.6 | +| D | 6.3.1 | Dial | 6.1-6.4/ 6.6 | +| E | 6.2.4 | Command Echo | 4.3 | +| H | 6.3.6 | Hook Control | 6.19/ 6.5/ 6.6 | +| I | 6.1.3 | Request Identification Information | 5.8 | +| L | 6.3.13 | Monitor Speaker Loudness | 6.19 | +| M | 6.3.14 | Monitor Speaker Mode | 6.19 | +| O | 6.3.7 | Return to Online Data State | 6.19 | +| P | 6.3.3 | Select Pulse Dialling | 6.19 | +| Q | 6.2.5 | Result Code Suppression | 4.3 | +| S0 | 6.3.8 | Automatic Answer | 6.19 | +| S10 | 6.3.12 | Automatic Disconnect Delay | 6.19 | +| S3 | 6.2.1 | Command Line Termination Character | 4.3 | +| S4 | 6.2.2 | Response Formatting Character | 4.3 | +| S5 | 6.2.3 | Command Line Editing Character | 4.3 | +| S6 | 6.3.9 | Pause Before Blind Dialling | 6.19 | +| S7 | 6.3.10 | Connection Completion Timeout | 6.19 | +| S8 | 6.3.11 | Comma Dial Modifier Time | 6.19 | +| T | 6.3.2 | Select Tone Dialling | 6.19 | +| V | 6.2.6 | DCE Response Format | 4.3/ 3/ 4.1/ 4.2 | +| X | 6.2.7 | Result Code Selection and Call Progress Monitoring Control | 4.3 | +| Z | 6.1.1 | Reset To Default Configuration | 5.8 | + +The use of ITU-T Recommendation V.42 error control protocol is not specified in the present document, but if a manufacturer chooses to implement it over transparent data service, +E prefixed commands of ITU-T Recommendation V.250 [14] shall be used. + +ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12] may be used as facsimile TA-TE protocols without deletions or additions to the command set. + +TIA IS-99 [15] commands referenced in the present document: + +**Table A.2: TIA IS-99 commands in the present document** + +| Command | IS-99 clause | Description | Clause in the present document | +|---------|--------------|----------------------------------------------|--------------------------------| +| +CBC | 5.6.5 | Battery Charge | 8.4 | +| +CGMI | 5.6.10 | Request Manufacturer Identification | 5.1 | +| +CGMM | 5.6.10 | Request Model Identification | 5.2 | +| +CGMR | 5.6.10 | Request Revision Identification | 5.3 | +| +CGSN | 5.6.10 | Request Product Serial Number Identification | 5.4 | +| +CRC | 5.6.7 | Cellular Result Codes | 6.11 | + +TIA IS-135 [16] commands referenced in the present document: + +**Table A.3: TIA IS-135 commands in the present document** + +| Command | IS-135 clause | Description | Clause in the present document | +|---------|---------------|-----------------------|--------------------------------| +| +CBC | 4.1.24 | Battery Charge | 8.4 | +| +CRC | 4.1.29 | Cellular Result Codes | 6.11 | +| +CSQ | 4.1.31 | Signal Quality | 8.5 | + +PCCA STD-101 [17] commands referenced in the present document: + +**Table A.4: PCCA STD-101 commands in the present document** + +| Command | STD-101 clause | Description | Clause in the present document | +|---------|----------------|--------------------------|--------------------------------| +| +WS46 | 5.2.4.6 | WDS-side Stack Selection | 5.9 | + +## Annex B (normative): Summary of result codes + +ITU-T Recommendation V.250 [14] result codes which can be used in the present document and result codes defined in the present document: + +**Table B.1: Result codes** + +| Verbose result code<br>(V.250 command V1 set) | Numeric<br>(V0 set) | Type | Description | +|-----------------------------------------------|---------------------|-----------------------------|----------------------| +| +C5GPDUAUTHU | as verbose | unsolicited | refer clause 10.1.73 | +| +C5GREG | as verbose | unsolicited | refer clause 10.1.47 | +| +C5GREGN3GPP | as verbose | unsolicited | refer clause 10.1.85 | +| +C5GUSMS | as verbose | unsolicited | refer clause 10.1.59 | +| +CABTSRI | as verbose | unsolicited | refer clause 10.1.41 | +| +CACSP | as verbose | unsolicited | refer clause 11.1.7 | +| +CALV | as verbose | unsolicited | refer clause 8.16 | +| +CANCHEV | as verbose | unsolicited | refer clause 11.1.8 | +| +CAPPLEVMC | as verbose | unsolicited | refer clause 8.78 | +| +CAPTT | as verbose | unsolicited | refer clause 11.1.4 | +| +CAULEV | as verbose | unsolicited | refer clause 11.1.5 | +| +CBCAP | as verbose | unsolicited | refer clause 8.59 | +| +CBCHG | as verbose | unsolicited | refer clause 8.61 | +| +CBCON | as verbose | unsolicited | refer clause 8.60 | +| +CC2APT | as verbose | unsolicited | refer clause 18.2.2 | +| +CCCM | as verbose | unsolicited | refer clause 7.16 | +| +CCKEYREQ | as verbose | unsolicited | refer clause 7.46 | +| +CCSFBU | as verbose | unsolicited | refer clause 8.76 | +| +CCSTATEREQU | as verbose | unsolicited | refer clause 10.1.72 | +| +CCWA | as verbose | unsolicited | refer clause 7.12 | +| +CCWV | as verbose | unsolicited | refer clause 8.28 | +| +CDEV | as verbose | unsolicited | refer clause 8.10 | +| +CDIP | as verbose | unsolicited | refer clause 7.9 | +| +CDISCO | as verbose | unsolicited | refer clause 8.87 | +| +CDNSADD | as verbose | unsolicited | refer clause 10.1.80 | +| +CDUT | as verbose | intermediate | refer clause 13.2.1 | +| +CDUU | as verbose | unsolicited | refer clause 13.2.1 | +| +CECN | as verbose | unsolicited | refer clause 6.28 | +| +CECSCONFU | as verbose | unsolicited | refer clause 10.1.84 | +| +CEDRXSP | as verbose | unsolicited | refer clause 7.40 | +| +CEMBMSRI | as verbose | unsolicited | refer clause 14.2.2 | +| +CEMBMSSAIT | as verbose | unsolicited | refer clause 14.2.6 | +| +CEMBMSSRVI | as verbose | unsolicited | refer clause 14.2.3 | +| +CEN1 | as verbose | intermediate<br>unsolicited | refer clause 8.67 | +| +CEN2 | as verbose | intermediate<br>unsolicited | refer clause 8.67 | +| +CEN3 | as verbose | intermediate<br>unsolicited | refer clause 8.67 | +| +CEN4 | as verbose | intermediate<br>unsolicited | refer clause 8.67 | +| +CEPTT | as verbose | unsolicited | refer clause 11.1.10 | +| +CEPSFBS | as verbose | unsolicited | refer clause 8.81 | + +| | | | | +|------------|------------|-----------------------------|-----------------------| +| +CEREG | as verbose | unsolicited | refer clause 10.1.22 | +| +CPBW | as verbose | intermediate | refer clause 8.14 | +| +CPNERU | as verbose | unsolicited | refer clause 8.70 | +| +CGBRRREP | as verbose | unsolicited | refer clause 10.1.69 | +| +CGDEL | as verbose | intermediate | refer clause 10.1.29 | +| +CGEV | as verbose | unsolicited | refer clause 10.1.19 | +| +CGREG | as verbose | unsolicited | refer clause 10.1.20 | +| +CHSR | as verbose | intermediate | refer clause 6.16 | +| +CIEV | as verbose | unsolicited | refer clause 8.10 | +| +CCIOTOPTI | as verbose | unsolicited | refer clause 7.42 | +| +CIREGU | as verbose | unsolicited | refer clause 8.71 | +| +CIREPH | as verbose | unsolicited | refer clause 8.64 | +| +CIREPI | as verbose | unsolicited | refer clause 8.64 | +| +CKEV | as verbose | unsolicited | refer clause 8.10 | +| +CLADNU | as verbose | unsolicited | refer clause 10.1.61 | +| +CELADNU | as verbose | unsolicited | refer clause 10.1.61a | +| +CLAV | as verbose | unsolicited | refer clause 8.31 | +| +CLIP | as verbose | unsolicited | refer clause 7.6 | +| +CMCCSI | as verbose | unsolicited | refer clause 8.73 | +| +CMCSSS<x> | as verbose | unsolicited | refer clause 8.73 | +| +CMCCSSEND | as verbose | unsolicited | refer clause 8.73 | +| +CME_ERROR | as verbose | final | refer clause 9.2.0 | +| +CMICO | as verbose | unsolicited | refer clause 10.1.55 | +| +CMOLRE | as verbose | unsolicited | refer clause 9.3.1 | +| +CMOLRG | as verbose | unsolicited | refer clause 8.50 | +| +CMOLRN | as verbose | unsolicited | refer clause 8.50 | +| +CMSSRI | as verbose | unsolicited | refer clause 10.1.89 | +| +CMTLR | as verbose | unsolicited | refer clause 8.57 | +| +CRTDCP | as verbose | unsolicited | refer clause 10.1.44 | +| +CMWN | as verbose | unsolicited | refer clause 7.36 | +| +CNAP | as verbose | intermediate<br>unsolicited | refer clause 7.30 | +| +CNEC_MM | as verbose | unsolicited | refer clause 9.1b | +| +CNEC_GMM | as verbose | unsolicited | refer clause 9.1b | +| +CNEC_GSM | as verbose | unsolicited | refer clause 9.1b | +| +CNEC_EMM | as verbose | unsolicited | refer clause 9.1b | +| +CNEC_ESM | as verbose | unsolicited | refer clause 9.1b | +| +CNEMIU | as verbose | unsolicited | refer clause 7.33 | +| +CNEMS1 | as verbose | unsolicited | refer clause 7.33 | +| +CNEM5G | as verbose | unsolicited | refer clause 7.33 | +| +CNRREG | as verbose | unsolicited | refer clause 10.1.47 | +| +COEV | as verbose | unsolicited | refer clause 8.10 | +| +COLP | as verbose | intermediate<br>unsolicited | refer clause 7.8 | +| +CPAGTCC | as verbose | unsolicited | refer clause 10.1.79 | +| +CPAGERES | as verbose | unsolicited | refer clause 10.1.78 | +| +CPINR | as verbose | intermediate | refer clause 8.65 | +| +CPINRE | as verbose | intermediate | refer clause 8.65 | +| +CPOSR | as verbose | unsolicited | refer clause 8.56 | +| +CPNERU | as verbose | unsolicited | refer clause 8.70 | +| +CPNSTAT | as verbose | unsolicited | refer clause 7.28 | +| +CPSB | as verbose | unsolicited | refer clause 7.29 | +| +CR | as verbose | intermediate | refer clause 6.9 | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------|------------------------------------------------------------------------------------------------------| +| +CREG | as verbose | unsolicited | refer clause 7.2 | +| +CREJPAG | as verbose | unsolicited | refer clause 10.1.77 | +| +CRING | as verbose | unsolicited | refer clause 6.11 | +| +CRLOSPU | as verbose | unsolicited | refer clause 10.1.65 | +| +CRTDCP | as verbose | unsolicited | refer clause 10.1.44 | +| +CRUEPOLICYU | as verbose | unsolicited | refer clause 10.1.51 | +| +CSBTSRI | as verbose | unsolicited | refer clause 10.1.56 | +| +CSCON | as verbose | unsolicited | refer clause 10.1.30 | +| +CSDBTSRI | as verbose | unsolicited | refer clause 10.1.58 | +| +CSENSE | as verbose | unsolicited | refer clause 8.x | +| +CSSI | as verbose | intermediate | refer clause 7.17 | +| +CSSU | as verbose | unsolicited | refer clause 7.17 | +| +CTEV | as verbose | unsolicited | refer clause 8.10 | +| +CTZE | as verbose | unsolicited | refer clause 8.41 | +| +CTZEU | as verbose | unsolicited | refer clause 8.41 | +| +CTZV | as verbose | unsolicited | refer clause 8.41 | +| +CUNPER | as verbose | unsolicited | refer clause 8.86 | +| +CUSATEND | as verbose | unsolicited | refer clause 12.2.4 | +| +CUSATP | as verbose | unsolicited | refer clause 12.2.4 | +| +CUSATS | as verbose | unsolicited | refer clause 12.2.3 | +| +CUSD | as verbose | unsolicited | refer clause 7.15 | +| +CUUAAPT | as verbose | unsolicited | refer clause 18.2.1 | +| +CUUS1I | as verbose | intermediate | refer clause 7.26 | +| +CUUS1U | as verbose | unsolicited | refer clause 7.26 | +| +CE5EECSR | as verbose | unsolicited | refer clause 19.2.3 | +| +CWLANOLADI | as verbose | unsolicited | refer clause 10.1.39 | +| +CWLANOLCMI | as verbose | unsolicited | refer clause 10.1.40 | +| +DR | as verbose | intermediate | refer clause 6.26 | +| +ILRR | as verbose | intermediate | refer clause 4.3 | +| BUSY | 7 | final | busy signal detected | +| CONNECT | 1 | intermediate | connection has been established | +| CONNECT <text> | manufacturer specific | intermediate | as CONNECT but manufacturer specific <text> gives additional information (e.g. connection data rate) | +| ERROR | 4 | final | command not accepted | +| NO ANSWER | 8 | final | connection completion timeout | +| NO CARRIER | 3 | final | connection terminated | +| NO DIALTONE | 6 | final | no dialtone detected | +| OK | 0 | final | acknowledges execution of a command line | +| RING | 2 | unsolicited | incoming call signal from network | +| NOTE: From v6.2.0 onwards, ATV0 numeric result codes 5, 6, 7 for NO DIALTONE, BUSY and NO ANSWER respectively, have been replaced by numeric result codes 6, 7, 8 respectively, to be aligned with the values listed in ITU-T Recommendation V.250 [14] (previously V.25ter). | | | | + +NOTE: The table B.1 is as an overview of the result codes, hence the complete syntax of the result codes is not shown. + +## Annex C (informative): Commands from TIA IS-101 + +### C.1 Introduction + +The "Voice Control Interim Standard for Asynchronous DCE", TIA IS-101, contains some commands that are useful when passing audio "data" (that is, data which represents audio information) between the computer and the TA. + +Some of the following clauses describe commands from IS-101 which are central to this TA application. However, with the exception of necessary extensions, these descriptions are not intended to replace the definitions found in IS-101. Other novel commands from the interim standard are not included because they are peripheral to TA operation. + +NOTE 1: IS-101 also uses ITU-T Recommendation V.250 [14] AT commands, but these are not mentioned here. + +The standard specifies the following modes: + +- command mode, where there is no transfer of audio "data" between the TA and the computer. In command mode, the computer is neither sending audio data to the TA nor receiving audio data from the TA. +- transmit mode, where audio "data" is being transferred from the computer to the TA. No audio "data" is transferred from the TA to the computer in this state. A transition back to command mode occurs when an embedded command indicates "end of play" or "flush data", or an inactivity timer times out. +- receive mode, where audio "data" is being transferred from the TA to the computer. No audio "data" is transferred from the computer to the TA in this state. A transition back to command mode occurs when any command is sent from the computer, or an inactivity timer times out. During the receive mode, the TA embeds result codes into the audio "data". These result codes indicate pertinent events such as "silence detected", "busy detected", and so on. + +Strictly, the standard specifies another mode (translation), but this is not directly of interest here. + +NOTE 2: The TA "knows" the type of an incoming call (whether it is voice, data, fax, whatever), and certain POTS events cannot occur. Hence some standard result codes for indication of events and discrimination of call type are unnecessary. + +There are three possible levels of service: + +- a TA supporting level A performs the following operations and detects the following events: audio transmit, audio receive, DTMF detection, DTMF generation and single tone generation. The following indications are supported: + +| Event | Description | Handset state | +|-------|--------------------------|---------------| +| 3 | ring | idle | +| 4 | DTMF received | idle | +| 5 | receive buffer overrun | receive | +| 6 | unsolicited fax request | idle | +| 8 | phone on/off hook | idle | +| 9 | presumed hangup | receive | +| 10 | presumed end of message | receive | +| 18 | ringback | idle | +| 19 | busy | idle | +| 23 | playback buffer underrun | transmit | + +25 fax or data request acknowledged idle + +- a TA supporting level B performs the operations and events of level A, and also supports DTMF detection while in the transmit state. +- a TA supporting level C performs the operations and events of level B, and also supports double DTMF tone generation. + +Since DTMF detection and generation cannot be guaranteed over current digital networks, it follows that none of the three levels of service can be supported. + +## C.2 Commands + +### C.2.1 Select mode +FCLASS + +This command puts the TA into a particular mode of operation (data, fax, voice etc.). This causes the TA to process information in a manner suitable for that type of information (rather than for other types of information). The values and meanings of parameter <n> are specified in the following table. + +| <n> | Mode | +|---------|----------------------------------------------------------| +| 0 | data | +| 1 | fax class 1 (TIA-578-A) | +| 1.0 | fax class 1 (ITU-T Recommendation T.31 [11]) | +| 2 | fax (manufacturer specific) | +| 2.0 | fax class 2 (ITU-T Recommendation T.32 [12] and TIA-592) | +| 3..7 | reserved for other fax modes | +| 8 | voice | +| 9..15 | reserved for other voice modes | +| 16..79 | reserved | +| 80 | VoiceView (Radish) | +| 81..255 | reserved | + +**Table C.1: +FCLASS parameter command syntax** + +| Command | Return | +|-------------|--------------------------| +| +FCLASS=<n> | | +| +FCLASS? | <n> | +| +FCLASS=? | (list of supported <n>s) | + +Voice mode is of particular interest here, and has an additional result code +VCON. Specifically, +VCON indicates that the TA is entering the voice command mode and there is a voice connection to at least one audio input or output. This presupposes that some mechanism has previously initiated a connection to that audio I/O. + +### C.2.2 Buffer threshold setting +VBT + +This refers to integers <lo> and <hi> that indicate levels within the TA transmit buffer at which flow control is asserted and deasserted. The buffer is used for averaging out the irregular timing of data from the computer, so that the data becomes synchronous and may be sent to some audio device. + +**Table C.2: +VBT parameter command syntax** + +| Command | Return | +|-----------------|-----------------------------------------------------------------------| +| +VBT=<lo>, <hi> | | +| +VBT? | <lo>, <hi> | +| +VBT=? | (list of supported <lo>s) , (list of supported <hi>s) , (buffer size) | + +## C.2.3 Calling number ID presentation +VCID + +The command refers to an integer that allows a called party to enable or disable (<n>=0) the reporting of the ID of calling parties, and specifies the method of presentation of the ID. This is basically the same as the supplementary service CLIP (Calling Line Identification Presentation). The presentation may be either formatted (<n>=1) or unformatted (<n>=2): + +- Formatted presentation: data items are reported in the form of <tag>=<value> pairs. + - <tag> <value> + - DATE MMDD (month, day) + - TIME HHMM (hour, minute) + - NMBR calling number or P or O (P = number is private, O = number is unavailable) + - NAME subscription listing name + - MESG data from other (unknown) tags +- Unformatted presentation: the data is presented in ASCII hex as printable numbers. + +**Table C.3: +VCID parameter command syntax** + +| Command | Return | +|-----------|--------| +| +VCID=<n> | | +| +VCID? | <n> | +| +VCID=? | (0-2) | + +## C.2.4 Receive gain selection +VGR + +This refers to the amplification by the TA of audio samples sent from the TA to the computer. The command operates on an integer <n>, range 0..255. Values larger than 128 indicate a larger gain than nominal. Values less than 128 indicate a smaller gain than nominal. The entire range of 0..255 does not have to be provided. A value of zero implies the use of automatic gain control by the TA. + +**Table C.4: +VGR parameter command syntax** + +| Command | Return | +|----------|--------------------------| +| +VGR=<n> | | +| +VGR? | <n> | +| +VGR=? | (list of supported <n>s) | + +## C.2.5 Transmit gain selection +VGT + +This refers to the amplification by the TA of audio samples sent from the computer to the TA. The command operates on an integer <n>, range 0..255. Values larger than 128 indicate a larger gain than nominal. Values less than 128 + +indicate a smaller gain than nominal. The entire range of 0...255 does not have to be provided. A value of zero implies the uses of automatic gain control by the TA. + +**Table C.5: +VGT parameter command syntax** + +| Command | Return | +|----------|--------------------------| +| +VGT=<n> | | +| +VGT? | <n> | +| +VGT=? | (list of supported <n>s) | + +## C.2.6 Initialise voice parameters +VIP + +This recalls manufacturer determined settings <n> of voice parameters. The command is write only. The effect of the command is manufacturer specific. + +**Table C.6: +VIP action command syntax** + +| Command | Return | +|----------|--------------------------| +| +VIP=<n> | | +| +VIP=? | (list of supported <n>s) | + +## C.2.7 Inactivity timer +VIT + +This refers to the value of the inactivity timer in the TA. It is used to monitor activity on the connection between the computer and the TA when the computer is in "transmit" mode and sending audio data to the TA. When the connection has been inactive for the time set by this command, the TA leaves "transmit" mode and reverts to command mode. An integer <n> different than zero implies a time of <n>/10 seconds. A value of zero disables the timer. + +**Table C.7: +VIT parameter command syntax** + +| Command | Return | +|----------|--------------------------| +| +VIT=<n> | | +| +VIT? | <n> | +| +VIT=? | (list of supported <n>s) | + +## C.2.8 Line selection +VLS + +This determines the selection of sources and destinations of audio samples. An integer is used to label a particular combination of sources and destinations. The integer is defined in an entry in IS-101 which assumes as a model a TA, a local phone and a phone line. Two additional "manufacturer specific" configurations (16,17) are defined. + +- label=0: this is the idle state - the phone is not connected to the radio network and no audio paths are used. +- label=1: the phone is connected to the radio network and no audio paths involving the internal microphone or internal loudspeaker are selected. This allows the computer to transmit audio data over the radio transmitter by selecting "transmit mode": + +**Table C.8: +VLS label 1a** + +| | loudspeaker | computer i/p | transmit stage | +|--------------------|-------------|--------------|----------------| +| microphone --> | | | | +| computer o/p --> | | | * | +| receiver stage --> | | | | + +This also allows the computer to receive audio data from the radio receiver by selecting "receive mode": + +**Table C.9: +VLS label 1b** + +| | <b>loudspeaker</b> | <b>computer i/p</b> | <b>transmit stage</b> | +|--------------------|--------------------|---------------------|-----------------------| +| microphone --> | | | | +| computer o/p --> | | | | +| receiver stage --> | | * | | + +- label=4: the phone is not connected to the radio network but there is an audio path to the internal speaker. This allows the computer to play sound by selecting "transmit mode". + +**Table C.10: +VLS label 4** + +| | <b>loudspeaker</b> | <b>computer i/p</b> | <b>transmit stage</b> | +|--------------------|--------------------|---------------------|-----------------------| +| microphone --> | | | | +| computer o/p --> | * | | | +| receiver stage --> | | | | + +- label=6: the phone is not connected to the radio network but there is an audio path to the internal microphone. This allows the computer to record sound by selecting "receive mode". + +**Table C.11: +VLS label 6** + +| | <b>loudspeaker</b> | <b>computer i/p</b> | <b>transmit stage</b> | +|--------------------|--------------------|---------------------|-----------------------| +| microphone --> | | * | | +| computer o/p --> | | | | +| receiver stage --> | | | | + +- label=7: the phone is connected to the radio network. The internal microphone is connected to the radio transmitter. The radio receiver is connected to the internal loudspeaker. This allows the computer to enable normal phone operation (a human holding a conversation) by selecting command mode. + +**Table C.12: +VLS label 7** + +| | <b>loudspeaker</b> | <b>computer i/p</b> | <b>transmit stage</b> | +|--------------------|--------------------|---------------------|-----------------------| +| microphone --> | | | * | +| computer o/p --> | | | | +| receiver stage --> | * | | | + +**Table C.13: +VLS parameter command syntax** + +| <b>Command</b> | <b>Return</b> | +|----------------|------------------------------| +| +VLS=<n> | +VCON | +| +VLS? | <n> | +| +VLS=? | <i>complex; refer IS-101</i> | + ++VCON is returned if an audio path is established or if a connection is made to the radio network. + +#### **Manufacturer specific extension (reserved as such by IS-101)** + +- label=16: the phone is connected to the radio network. There is a path to the internal microphone, which is also connected to the radio transmitter. There is a path to the radio receiver, which is also connected to the internal loudspeaker. This allows the computer to record the sum of transmitted and received audio by selecting "receive mode". + +**Table C.14: +VLS label 16** + +| | <b>loudspeaker</b> | <b>computer i/p</b> | <b>transmit stage</b> | +|--------------------|--------------------|---------------------|-----------------------| +| microphone --> | | * | * | +| computer o/p --> | | | | +| receiver stage --> | * | * | | + +- label=17: the phone is connected to the radio system and there is a path to the internal loudspeaker and to the radio transmitter. This allows the computer to simultaneously play sound and send audio over the radio by selecting "transmit mode". + +**Table C.15: +VLS label 17** + +| | <b>loudspeaker</b> | <b>computer i/p</b> | <b>transmit stage</b> | +|--------------------|--------------------|---------------------|-----------------------| +| microphone --> | | | | +| computer o/p --> | * | | * | +| receiver stage --> | | | | + +## C.2.9 Receive data state +VRX + +This action command causes the TA to get audio data from a source determined by the +VLS command, and send it to the computer. Once the datastream has started, any result codes will be embedded in the data and shielded using the normal <DLE> methods. The receive process is terminated when the computer sends any command to the TA, or by time-out of the inactivity timer. The command is write only. + +**Table C.16: +VRX action command syntax** + +| <b>Command</b> | <b>Return</b> | +|----------------|---------------| +| +VRX | CONNECT | + +## C.2.10 Select compression method +VSM + +This selects the voice compression method <n1>, the voice sampling rate <n2>, the silence compression sensitivity <n3>, and a parameter related to silence expansion <n4>. There are several choices of compression method. IS-101 does not specify methods, but here is a list of some usual compression methods: + +| Name | Communications system | +|---------------|-----------------------| +| GSM/full-rate | GSM | +| GSM/half-rate | GSM | +| ADPCM/G.721 | DECT, CT2 | +| ADPCM/G.723 | DECT, CT2 | +| ADPCM/G.726 | DECT, CT2 | +| ADPCM/G.727 | DECT, CT2 | +| SIGNED PCM | POTS | + +**Table C.17: +VSM parameter command syntax** + +| <b>Command</b> | <b>Return</b> | +|-----------------------------|------------------------------| +| +VSM=<n1>, <n2>, <n3>, <n4> | | +| +VSM? | <n1>, <n2>, <n3>, <n4> | +| +VSM=? | <i>complex; refer IS-101</i> | + +NOTE: A value of <n3>=0 implies no silence compression sensitivity. A value of <n4>=0 implies no silence expansion. + +## C.2.11 DTMF and tone generation +VTS + +This command allows the transmission of DTMF tones and arbitrary tones (see NOTE 1). These tones may be used (for example) when announcing the start of a recording period. The command is write only. In this profile of commands, this command does not operate in data or fax modes of operation (+FCLASS=0,1,2-7). + +NOTE 1: D is used only for dialling. + +The string parameter of the command consists of combinations of the following separated by commas: + +1. <DTMF>. A single ASCII character in the set 0-9, #, \*, A-D. This is interpreted as a single ACSII character whose duration is set by the +VTD command. + +NOTE 2: In GSM this operates only in voice mode. + +2. [<tone1>, <tone2>, <duration>]. This is interpreted as a dual tone of frequencies <tone1> and <tone2>, lasting for a time <duration> (in 10 ms multiples). + +NOTE 3: This does not operate in GSM. + +3. {<DTMF>, <duration>}. This is interpreted as a DTMF tone of different duration from that mandated by the +VTD command. + +NOTE 4: In GSM this operates only in voice mode. + +**Table C.18: +VTS action command syntax** + +| Command | Return | +|-----------------------|-----------------------------------------------------------------------------------------------| +| +VTS= <i>as above</i> | | +| +VTS=? | (list of supported <tone1>s) , (list of supported <tone2>s) , (list of supported <duration>s) | + +## C.2.12 Tone duration +VTD + +This refers to an integer <n> that defines the length of tones emitted as a result of the +VTS command. This does not affect the D command. A value different than zero causes a tone of duration <n>/10 seconds. The value zero causes a "manufacturer specific" value. + +**Table C.19: +VTD parameter command syntax** + +| Command | Return | +|----------|--------------------------| +| +VTD=<n> | | +| +VTD? | <n> | +| +VTD=? | (list of supported <n>s) | + +NOTE: In GSM/UMTS the value of tone duration is preset and cannot be altered. + +## C.2.13 Transmit data state +VTX + +This action command causes the TA to receive audio data from the computer and send it to a destination determined by the +VLS command. Once the audio datastream has started, commands to the TA shall be embedded in the data stream, and shielded using the normal <DLE> methods. The transmit process is terminated by the use of embedded commands or by the time-out of an inactivity timer. It is recommended that the TA has a buffer to allow the TA to convert potentially bursty data from the computer into synchronous data for "transmission". The command is write only. + +**Table C.20: +VTX action command syntax** + +| Command | Return | +|---------|---------| +| +VTX | CONNECT | + +--- + +## Annex D (informative): Bibliography + +### Informative references: + +- 1) IrDA Serial Infrared Physical Layer Specification. +IrDA Serial Infrared MAC and Link Protocol. +IrDA Serial Infrared Link Access Protocol. +- 2) PCCA STD-101 Annex I: Data Transmission Systems and Equipment - Serial Asynchronous Automatic Dialling and Control for Character Mode DCE on Wireless Data Services - Annex I: Command Extensions for Analog Cellular Data Modems. +- 3) TIA IS-101 Facsimile Digital Interfaces - Voice Control Interim Standard for Asynchronous DCE. +- 4) TIA-578-A Facsimile Digital Interfaces - Asynchronous Facsimile DCE Control Standard, Service Class 1. +- 5) TIA-592 Facsimile Digital Interfaces - Asynchronous Facsimile DCE Control Standard, Service Class 2. +- 6) TIA-617 Data Transmission Systems and Equipment - In-Band DCE Control. +- 7) ITU-T Recommendation V.80: In-band DCE control and synchronous data modes for asynchronous DTE. + +# Annex E (informative): Mobile originated alternating voice/data call example + +Figure E.1 illustrates the possible transitions in MO BS 61 call. Responses and result codes generated by TA are in bold face. In this example, data part of the call is asynchronous non-transparent 9600 bps service. + +![State transition diagram for MO BS 61 call showing transitions between OFF-LINE, VOICE, and DATA states with AT commands and responses.](19d2407a2ba78e0bc5de8db07448b309_img.jpg) + +The diagram illustrates the state transitions for a Mobile Originated (MO) BS 61 call, alternating between VOICE and DATA states from an OFF-LINE state. + +- OFF-LINE State:** + - Initial configuration: + - AT+CBST=7,0,1 → **OK** + - AT+COLP=1; +CR=1; +DR=1; +ILRR=1 → **OK** + - AT+CMOD=2; +FCLASS=0 → **OK** + - Transition to VOICE or DATA: + - Command: **ATD12345;** (to VOICE) or **ATD12345** (to DATA) + - success** response: **+COLP: +35812345,145** → **OK** + - connection failure** response: **NO CARRIER** → **AT+CEER** → **+CEER: failure cause** → **OK**. Other possible failure codes: **BUSY/NO ANSWER/ERROR**. + - RLP negotiation failure response: **+COLP: +35812345,145** → **+CR: REL ASYNC** → **NO CARRIER**. +- VOICE State:** + - Entry point: From OFF-LINE via **ATD12345;**. + - Internal command: **ATD (or ATA)**. + - Modification from VOICE to DATA: + - Command: **in-call modification success** → **+CR: REL ASYNC** → **+DR: NONE** → **+ILRR: 19200** → **CONNECT 9600**. + - Failure: **in-call modification failure** → **ERROR** → **AT+CEER** → **+CEER: failure cause** → **OK**. + - Remote initiated modification successful: → **CONNECT 9600**. + - Remote hangup: → **AT+CHUP (or ATH or drop DTR)** → **OK** → **NO CARRIER** → OFF-LINE. +- DATA State (V.24 circuit 109 ON):** + - Entry point: From OFF-LINE via **ATD12345**. + - Internal command: **ATH (or drop DTR)**. + - Modification from DATA to VOICE: + - Command: **in-call modification success** → **OK**. + - Failure: **in-call modification failure** → **ERROR** → **AT+CEER** → **+CEER: failure cause** → **OK**. + - Remote initiated modification successful: → **OK**. + - Remote hangup: → **AT+CHUP** → **OK** → **NO CARRIER** → OFF-LINE. +- Return to OFF-LINE:** + - From both VOICE and DATA states via **NO CARRIER** → **OFF-LINE** → **TA sets +CMOD=0**. + +State transition diagram for MO BS 61 call showing transitions between OFF-LINE, VOICE, and DATA states with AT commands and responses. + +Figure E.1: MO BS 61 call + +# Annex F (informative): Mobile terminated voice followed by data call example + +Figure F.1 illustrates the possible transitions in MT BS 81 call. Responses and result codes generated by TA are in bold face. In this example, data part of the call is asynchronous non-transparent 9600 bps service. + +![State transition diagram for MT BS 81 call showing transitions between OFF-LINE, VOICE, and DATA states with AT commands and responses.](00ba55671b1a33474972d73577000bff_img.jpg) + +``` + +stateDiagram-v2 + [*] --> OFFLINE_1: OFF-LINE + state "OFF-LINE" as OFFLINE_1 { + AT+CLIP=1; +CR=1; +DR=1; +ILRR=1; +CRC=1 + OK + +CRING: VOICE/REL ASYNC + +CLIP: +35812345,145 + AT+C MOD=3; +FCLASS=0; A + } + OFFLINE_1 --> VOICE: success OK + OFFLINE_1 --> OFFLINE_2: connection failure NO CARRIER + state "OFF-LINE" as OFFLINE_2 { + TA sets +CMOD=0 + } + VOICE --> DATA: in-call modification success +CR: REL ASYNC +DR: NONE +ILRR: 19200 CONNECT 9600 + VOICE --> VOICE: in-call modification failure ERROR AT+CEER +CEER: failure cause OK + VOICE --> DATA: remote initiated in-call modification successful +CR: REL ASYNC +DR: NONE +ILRR: 19200 CONNECT 9600 + VOICE --> OFFLINE_2: remote hangup AT+CHUP (or ATH or drop DTR) NO CARRIER + DATA --> VOICE: in-call modification success +CR: REL ASYNC +DR: NONE +ILRR: 19200 CONNECT 9600 + DATA --> VOICE: in-call modification failure ERROR AT+CEER +CEER: failure cause OK + DATA --> OFFLINE_2: remote hangup ATH (or AT+CHUP or drop DTR) NO CARRIER + +``` + +The diagram illustrates the state transitions for an MT BS 81 call. It starts in the **OFF-LINE** state, where various AT commands are set (e.g., `AT+CLIP=1; +CR=1; +DR=1; +ILRR=1; +CRC=1`). A **success OK** response leads to the **VOICE** state. From **VOICE**, an **ATD (or ATA)** command is used to initiate a call. Successful in-call modifications (e.g., `+CR: REL ASYNC +DR: NONE +ILRR: 19200 CONNECT 9600`) lead to the **DATA** state (V.24 circuit 109 ON). Remote hangups or connection failures lead back to the **OFF-LINE** state, where the TA sets `+CMOD=0`. + +State transition diagram for MT BS 81 call showing transitions between OFF-LINE, VOICE, and DATA states with AT commands and responses. + +Figure F.1: MT BS 81 call + +# Annex G (informative): Voice call example + +Figure G.1 illustrates the possible transitions in both MT and MO TS 11 calls. Responses and result codes generated by TA are in bold face. + +![Flowchart illustrating voice call transitions for MT and MO TS 11 calls. The diagram shows initial states for MT, MO without COLP, and MO with COLP, leading to a 'VOICE call active' state, and finally to hangup options.](1bc5e91471a7c3accdadb0b5b446e244_img.jpg) + +``` + +graph TD + subgraph MT + MT1["AT+CLIP=1; +CRC=1 +OK + ++CRING: VOICE + ++CLIP: +35812345,145 + +ATA"] + end + subgraph MO_without_COLP ["MO without COLP"] + MO1["AT+COLP=0 +OK +ATD12345;"] + end + subgraph MO_with_COLP ["MO with COLP"] + MO2["AT+COLP=1 +OK +ATD12345;"] + end + MT1 -- "connection failure +NO CARRIER +AT+CEER ++CEER: failure cause +OK" --> MT_fail1 + MT1 -- "success +OK" --> VOICE_active + MO1 -- "call setup started +OK" --> VOICE_active + MO1 -- "general failure +ERROR" --> MO1_fail + MO2 -- "success ++COLP: +35812345,145 +OK" --> VOICE_active + MO2 -- "connection failure +NO CARRIER +AT+CEER ++CEER: failure cause +OK" --> MO2_fail1 + MO2 -- "remote busy +BUSY" --> MO2_fail2 + MO2 -- "general failure +ERROR" --> MO2_fail3 + VOICE_active["VOICE call active + +(remote ring or other network generated tones)"] --> Hangup["remote hangup +AT+CHUP (or ATH or drop DTR)"] + Hangup --> Hangup1["NO CARRIER"] + Hangup --> Hangup2["OK"] + +``` + +The diagram illustrates the state transitions for MT (Mobile Terminating) and MO (Mobile Originating) voice calls. + +**MT State:** Initial state includes AT+CLIP=1; +CRC=1 (OK), +CRING: VOICE, +CLIP: +35812345,145, and ATA. A 'connection failure' leads to NO CARRIER, AT+CEER, and +CEER: failure cause (OK). A 'success' transition leads to the active call state. + +**MO without COLP State:** Initial state includes AT+COLP=0 (OK) and ATD12345;. A 'call setup started' (OK) transition leads to the active call state. A 'general failure' (ERROR) is also possible. + +**MO with COLP State:** Initial state includes AT+COLP=1 (OK) and ATD12345;. A 'success' transition with +COLP: +35812345,145 (OK) leads to the active call state. Other possible transitions include 'connection failure' (NO CARRIER, AT+CEER, +CEER: failure cause, OK), 'remote busy' (BUSY), and 'general failure' (ERROR). + +**VOICE call active State:** This state is reached from any successful call setup. It includes a note about '(remote ring or other network generated tones)'. From here, a 'remote hangup' followed by AT+CHUP (or ATH or drop DTR) leads to either 'NO CARRIER' or 'OK'. + +Flowchart illustrating voice call transitions for MT and MO TS 11 calls. The diagram shows initial states for MT, MO without COLP, and MO with COLP, leading to a 'VOICE call active' state, and finally to hangup options. + +Figure G.1: TS 11 calls + +## Annex H (informative): Change history + +| TSG | TDoc | CR | R<br>E<br>V | PH | CAT | SUBJECT | WORKITEM | NEW<br>_VERS | +|------|-----------|-----|-------------|-------|-----|-----------------------------------------------------------------------------------------------------|------------------------------|--------------| +| T#4 | TP-99118 | New | | | | Creation of 3GPP 27.007 v3.0.0 out of GSM 07.07 v7.2.0 | | 3.0.0 | +| T#4 | TP-99124 | 001 | | R99 | A | Additional result codes for +CLIP +CCWA | TEI | 3.1.0 | +| T#4 | TP-99124 | 002 | | R99 | B | ECSD additions | EDGE | 3.1.0 | +| T#4 | TP-99124 | 003 | | R99 | B | ECSD asymmetry (new command +CHSA) | EDGE | 3.1.0 | +| T#4 | TP-99146 | 004 | | R99 | A | Syntax error in +CHSN command | TEI | 3.1.0 | +| T#4 | TP-99146 | 005 | | R99 | A | Moving AT commands to 07.07 for 07.60 handover to SMG3 / 3GPP TSG CN WG3 | GPRS | 3.1.0 | +| T#5 | TP-99177 | 006 | | R99 | D | ECSD AT command correction | EDGE | 3.2.0 | +| T#5 | TP-99177 | 007 | | R99 | B | Alarm functionality | TEI | 3.2.0 | +| T#5 | TP-99177 | 008 | | R99 | B | Phonebook storage | TEI | 3.2.0 | +| T#5 | TP-99177 | 009 | | R99 | B | Time Zone | TEI | 3.2.0 | +| T#5 | TP-99177 | 010 | | R99 | B | Additional result code for +CSSN | TEI | 3.2.0 | +| T#5 | TP-99177 | 011 | | R99 | B | New command for setting of Date format | TEI | 3.2.0 | +| T#5 | TP-99177 | 012 | | R99 | B | New command for Silent mode | TEI | 3.2.0 | +| T#5 | TP-99177 | 013 | | R99 | B | New command for setting of Time format | TEI | 3.2.0 | +| T#5 | TP-99177 | 014 | | R99 | B | GSM 400 Spectrum update | GSM 400 | 3.2.0 | +| T#5 | TP-99177 | 015 | | R99 | A | AT command - Request GPRS service 'D' | GPRS | 3.2.0 | +| T#6 | TP-99237 | 016 | | R99 | F | Clarification to result codes for +CLIP +CCWA | TEI | 3.3.0 | +| T#6 | TP-99237 | 017 | | R99 | B | AT command for Frame Tunnelling Mode (FTM) | Frame Tunnelling Mode | 3.3.0 | +| T#6 | TP-99237 | 018 | | R99 | B | New AT command for application protocols activation | TEI | 3.3.0 | +| T#6 | TP-99237 | 022 | | R99 | B | Add new AT command (+CDIP) to inform the called line identification | TEI | 3.3.0 | +| T#6 | TP-99237 | 020 | | R99 | C | Packet Domain ATD command syntax | GPRS | 3.3.0 | +| T#6 | TP-99237 | 021 | | R99 | B | Additional parameter for +CBST | TEI | 3.3.0 | +| T#6 | TP-99237 | 019 | | R99 | B | AT-commands for Enhanced QoS Support management | Enhanced QoS Support in GPRS | 3.3.0 | +| T#7 | TP-000024 | 024 | | R99 | F | Deletion of the AT+CPROT? read command | TEI | 3.4.0 | +| T#7 | TP-000024 | 025 | | R99 | F | Adaptations for UMTS | TEI | 3.4.0 | +| T#7 | TP-000024 | 026 | | R99 | D | References to ASCI Specifications | ASCI | 3.4.0 | +| T#7 | TP-000024 | 027 | | R99 | D | Abbreviations related to ASCI | ASCI | 3.4.0 | +| T#7 | TP-000024 | 028 | | R99 | B | Priority indication in +CLCC, List Current Calls | ASCI | 3.4.0 | +| T#7 | TP-000024 | 029 | | R99 | B | Indication of priority, sub-address, sub-address type and TS 91/TS92 in +CRC, Cellular Result Codes | ASCI | 3.4.0 | +| T#7 | TP-000024 | 030 | | R99 | B | Commands for ASCI | ASCI | 3.4.0 | +| T#7 | TP-000024 | 031 | | R99 | B | Commands for eMLPP | eMLPP | 3.4.0 | +| T#7 | TP-000024 | 032 | | R99 | B | Example for usage of priority | eMLPP | 3.4.0 | +| T#8 | TP-000073 | 033 | | R99 | B | +CSDF, +CCLK and +CALA(4 digits for year field) | TEI | 3.5.0 | +| T#8 | TP-000073 | 034 | | R99 | F | APN presentation | TEI | 3.5.0 | +| T#8 | TP-000073 | 035 | | R99 | F | +CAJOIN also serves to join an ongoing group or a broadcast call | ASCI | 3.5.0 | +| T#8 | TP-000073 | 036 | | R99 | F | +CAULEV, the uplink status presentation in a Voice Group Call | ASCI | 3.5.0 | +| T#8 | TP-000073 | 037 | | R99 | F | CME ERROR extensions for ASCI Commands | ASCI | 3.5.0 | +| T#8 | TP-000073 | 038 | | R99 | F | Correction of the description of the +CRC | ASCI | 3.5.0 | +| T#8 | TP-000073 | 039 | | R99 | F | Definition of the abbreviation of MT | ASCI | 3.5.0 | +| T#8 | TP-000073 | 040 | | R99 | F | Packet Domain QoS AT-commands | TEI | 3.5.0 | +| T#9 | TP-000143 | 041 | | R99 | F | TE software implementations must take account of extra parameters | TEI | 3.6.0 | +| T#9 | TP-000143 | 042 | | R99 | F | APN presentation | TEI | 3.6.0 | +| T#9 | TP-000144 | 043 | | R00 | B | Introduction of a new AT command +CUUS1 to manage User-to-User Information element | ASCI | 4.0.0 | +| T#9 | TP-000144 | 044 | | R00 | B | Indication of priority and/or sub-address in the unsolicited result code CCWA | ASCI | 4.0.0 | +| T#9 | TP-000144 | 045 | | R00 | B | eMLPP SIM Commands | ASCI | 4.0.0 | +| T#9 | TP-000144 | 046 | | R00 | B | VBS, VGCS SIM Commands | ASCI | 4.0.0 | +| T#9 | TP-000144 | 047 | | R00 | A | Extension of dial command for VBS and VGCS | ASCI | 4.0.0 | +| T#9 | TP-000144 | 048 | | R00 | A | Introduction of a new AT command +COTDI to manage Originator-to-dispatcher information element | ASCI | 4.0.0 | +| T#11 | TP-010028 | 053 | | Rel-4 | A | Clarification of the specification to incorporate UICC/USIM references | TI-ATC | 4.1.0 | +| T#11 | TP-010028 | 054 | | Rel-4 | F | Update the AT command, +CPBS, that select the phonebooks in the SIM/UICC | TI-ATC | 4.1.0 | +| T#11 | TP-010028 | 055 | | Rel-4 | F | Correction of GSM references | TI-ATC | 4.1.0 | + +| | | | | | | | | | +|-------|-----------|------|---|-------|---|-------------------------------------------------------------------------------------------------------|--------|-------| +| T#11 | TP-010028 | 056 | | Rel-4 | F | Update the AT commands that access the PLMN preferred list in the SIM/UICC | TI-ATC | 4.1.0 | +| T#11 | TP-010028 | 057 | | Rel-4 | F | Update of phonebook AT commands, +CBBS,+CPBR, +CPBF and +CPBW, to access the hidden phonebook entries | TI-ATC | 4.1.0 | +| T#11 | TP-010028 | 058 | | Rel-4 | A | Addition of explicit subscribed value to QoS command | TI-ATC | 4.1.0 | +| T#11 | TP-010028 | 059 | | Rel-4 | A | Corresponding GMM states for +CGREG command | TI-ATC | 4.1.0 | +| T#11 | TP-010028 | 060 | | Rel-4 | F | Definition of "class C in GPRS and circuit switched alternate mode" | TI-ATC | 4.1.0 | +| T#12 | TP-010127 | 061 | | Rel-4 | A | Aligning command AT+CSNS with changes introduced to single numbering scheme | TEI4 | 4.2.0 | +| T#12 | TP-010127 | 064 | | Rel-4 | A | Inclusion of multimedia values to command AT+CBST | TEI4 | 4.2.0 | +| T#12 | TP-010127 | 066 | | Rel-4 | A | Modification to Request Packet Domain service 'D' command | TEI4 | 4.2.0 | +| T#12 | TP-010127 | 068 | | Rel-4 | A | Inclusion of IPv6 and removal of X.25 and OSPIH <PDP_type> values | TEI4 | 4.2.0 | +| T#14 | TP-010269 | 070 | 1 | Rel-4 | A | Obsolete +CGGCLOSP and corrections due to IHOSS and OSP removal | TI-ATC | 4.3.0 | +| T#14 | TP-010269 | 072 | | Rel-4 | A | Obsolete +CGCLPAD and corrections due to X.25 removal | TI-ATC | 4.3.0 | +| T#14 | TP-010269 | 074 | | Rel-4 | A | Clarifications to AT commands used with circuit switched data | TI-ATC | 4.3.0 | +| T#14 | TP-010269 | 076 | | Rel-4 | A | Correction in the +CGACT command explanation | TI-ATC | 4.3.0 | +| T#14 | TP-010269 | 077 | | Rel-4 | F | Correction of chapter heading and references | TI-ATC | 4.3.0 | +| T#14 | TP-010269 | 079 | | Rel-4 | A | Different compression algorithms in AT commands +CGDCONT and +CGDSCONT | TI-ATC | 4.3.0 | +| T#14 | TP-010269 | 080 | | Rel-5 | B | New AT command +CRMC (Ring Melody Control) | TEI5 | 5.0.0 | +| T#14 | TP-010269 | 081 | | Rel-5 | B | Added reference to 23.227 | TEI5 | 5.0.0 | +| T#15 | TP-020014 | 084 | | Rel-5 | A | Alignment of UE architecture with 23.101 | TEI5 | 5.1.0 | +| T#16 | TP-020103 | 085 | | Rel-6 | B | Enhancement of AT command +CIND to indicate SMS rejection | TEI6 | 6.0.0 | +| T#17 | TP-020272 | 089 | | Rel-6 | A | Clarification in the behaviour of AT+W46 | TEI6 | 6.1.0 | +| T#19 | TP-030067 | 097 | 1 | Rel-6 | A | Clarification in the behaviour of AT+CGCLASS | TEI6 | 6.2.0 | +| T#19 | TP-030037 | 101 | | Rel-6 | A | Correction ATV0 result codes | TEI6 | 6.2.0 | +| T#19 | TP-030071 | 105 | 1 | Rel-6 | A | Correction of AT+WS46 parameter values | TEI6 | 6.2.0 | +| T#19 | TP-030037 | 109 | | Rel-6 | A | AT +CGEQREQ - Required Parameters for Streaming / Conversational Traffic Class | TEI6 | 6.2.0 | +| T#20 | TP-030113 | 110 | | Rel-6 | F | Correction of references | TEI6 | 6.3.0 | +| T#21 | TP-030212 | 111 | | Rel-6 | A | Adding reference to 24.008 for the 3G QoS AT-commands | TEI5 | 6.4.0 | +| T#24 | TP-040134 | 116 | 1 | Rel-6 | C | Updating error codes description to support UICC | TEI6 | 6.5.0 | +| T#25 | TP-040170 | 117 | | Rel-6 | F | Correction to AT command +CHSN | HSCSD | 6.6.0 | +| T#25 | TP-040170 | 118 | | Rel-6 | B | Support of logical channels in AT commands | TEI6 | 6.6.0 | +| T#26 | TP-040225 | 120 | | Rel-6 | A | Additional parameter for AT command +CRSM (Restricted SIM access) | TEI5 | 6.7.0 | +| T#26 | TP-040225 | 122 | | Rel-6 | A | Corrections to AcTs of PLMN Selection | TEI5 | 6.7.0 | +| T#26 | TP-040225 | 123 | | Rel-6 | C | Improve security in UICC generic access command +CGLA | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 124 | | Rel-6 | B | Support of EAP authentication command | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 125 | | Rel-6 | F | Correction of file identification in +CRLA command | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 126 | | Rel-6 | B | UICC Application Discovery Command +CUAD | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 127 | | Rel-6 | F | Clarification on the use of PIN with (U)SIM | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 128 | | Rel-6 | D | Editorial modifications to +CGLA and +CRLA commands | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 129 | | Rel-6 | B | Add RETRIEVE DATA and SET DATA APDU commands in +CRSM and +CRLA AT commands | TEI6 | 6.7.0 | +| T#26 | TP-040225 | 130 | | Rel-6 | B | Extension of read, write and find phonebook entry commands for 3G phonebooks | TEI6 | 6.7.0 | +| T#27 | TP-050012 | 131 | | Rel-6 | F | Align time zone range of AT+CCLK (CLOCK) | TEI | 6.8.0 | +| T#27 | TP-050012 | 132 | | Rel-6 | A | Illogical response in +CGDSCONT test command ( REL 6) | TEI5 | 6.8.0 | +| CT#31 | CP-060126 | 137 | | Rel-7 | F | QoS additions for the AT commands +CGEQREQ and +CGEQMIN | TEI7 | 7.0.0 | +| CT#32 | CP-060276 | 0138 | | Rel-7 | F | Access technology added to AT commands +CREG and +CGREG | TEI7 | 7.1.0 | +| CT#32 | CP-060276 | 0139 | | Rel-7 | F | Enhancement of parameter CI in AT commands +CREG and +CGREG | TEI7 | 7.1.0 | +| CT#33 | CP-060506 | 0140 | 1 | Rel-7 | F | Support for UTF-8 in AT-command +CSCS | TEI7 | 7.2.0 | +| CT#35 | CP-070155 | 0141 | 2 | Rel-7 | B | Addition of preferred network in AT command | TEI7 | 7.3.0 | +| CT#36 | CP-070371 | 0147 | - | Rel-7 | A | Extension of AT-command +CEAP | TEI6 | 7.4.0 | +| CT#36 | CP-070458 | 0145 | 1 | Rel-7 | A | Correction for AT-commands +CEAP, +CERP and +CUAD | TEI6 | 7.4.0 | +| CT#36 | CP-070395 | 0144 | 3 | Rel-8 | B | Introduction of the new AT command AT+CPSB | TEI8 | 8.0.0 | +| CT#36 | CP-070395 | 0148 | 2 | Rel-8 | B | Extension of parameter <Act> to include HSDPA- & HSUPA- capability | TEI8 | 8.0.0 | +| CT#37 | CP-070604 | 0149 | 3 | Rel-8 | C | Extension for AT-commands +CPBW, +CPBF and +CPBR | TEI8 | 8.1.0 | +| CT#37 | CP-070604 | 0150 | 3 | Rel-8 | B | AT-command +CVMOD to set the voice call preference | TEI8 | 8.1.0 | +| CT#38 | CP-070815 | 0152 | 2 | Rel-8 | B | AT-commands for location handling | TEI8 | 8.2.0 | +| CT#39 | CP-080136 | 0153 | | Rel-8 | F | Corrections to +CMOLRG | TEI8 | 8.3.0 | +| CT#40 | CP-080361 | 0156 | | Rel-8 | B | AT command for enabling/disabling the backlight | TEI8 | 8.4.0 | +| CT#40 | CP-080351 | 0158 | 1 | Rel-8 | B | TCRT: Short Data Transmission during ongoing VGCS | EVA | 8.4.0 | +| | | | | | | Editorial change: sub clauses 8.51 and 8.52 swapped | | 8.4.1 | +| CT#41 | CP-080536 | 0159 | 1 | Rel-8 | B | Adding and extending AT-commands to support touch screen functions | TEI8 | 8.5.0 | +| CT#41 | CP-080536 | 0160 | 1 | Rel-8 | B | Setting of display resolution and screen orientation for touch screen functions | TEI8 | 8.5.0 | +| CT#41 | CP-080536 | 0161 | 1 | Rel-8 | C | AT Backlight command. CBKLT Default setting | TEI8 | 8.5.0 | +| CT#42 | CP-080873 | 0162 | 3 | Rel-8 | F | Corrections to +CMOLRG | TEI8 | 8.6.0 | +| CT#42 | CP-080887 | 0163 | 3 | Rel-8 | B | AT-Commands for positioning assistance | TEI8 | 8.6.0 | + +| | | | | | | | | | | +|-------|-----------|------|---|--------|---|---------------------------------------------------------------------------------------|-----------------------|--------|--| +| 3 | | | | | | | | | | +| CT#42 | CP-080866 | 0164 | 1 | Rel-8 | B | Introduction of new RAT-type for SAE | SAES | 8.6.0 | | +| CT#42 | CP-080866 | 0165 | 2 | Rel-8 | B | Additional AT commands for LTE/SAE | SAES | 8.6.0 | | +| CT#42 | CP-080872 | 0167 | | Rel-8 | A | Restoring default value for TE character set | TEI7 | 8.6.0 | | +| CT#42 | CP-080872 | 0168 | 2 | Rel-8 | A | Introduction of RAC to CGREG | TEI7 | 8.6.0 | | +| CT#43 | CP-090159 | 0170 | 1 | Rel-8 | F | Correction of AT-Commands for positioning | TEI8 | 8.7.0 | | +| CT#43 | CP-090130 | 0171 | 1 | Rel-8 | F | Support of dedicated bearer related AT command | SAES | 8.7.0 | | +| CT#43 | CP-090153 | 0172 | | Rel-8 | B | AT-command for UE modes of operation in SAE | SAES-CSFB | 8.7.0 | | +| CT#43 | CP-090159 | 0174 | 1 | Rel-8 | F | Corrections for +CGCLASS | TEI8 | 8.7.0 | | +| CT#43 | | | | Rel-8 | | Editorial cleanup by MCC | | 8.7.0 | | +| CT#44 | CP-090413 | 0178 | 1 | Rel-8 | F | Adding E-UTRAN to the Current Packet Switched Bearer AT command | SAES | 8.8.0 | | +| CT#44 | CP-090391 | 0177 | 2 | Rel-8 | F | Common AT Command Set for EPS and UMTS/GPRS for the PS Domain | SAES | 8.8.0 | | +| CT#44 | CP-090430 | 0175 | 1 | Rel-9 | B | AT command for CNAP (Calling Name Presentation) | TEI9 | 9.0.0 | | +| CT#44 | CP-090430 | 0176 | 2 | Rel-9 | B | AT command for COLR ( Connected Line Identification Restriction Status ) | TEI9 | 9.0.0 | | +| CT#45 | CP-090679 | 0181 | | Rel-9 | A | Corrections of AT-command for originated location request | TEI8 | 9.1.0 | | +| CT#45 | CP-090679 | 0183 | | Rel-9 | A | Origin for assist_data is corrected | TEI8 | 9.1.0 | | +| CT#45 | CP-090682 | 0184 | | Rel-9 | B | "non-GPS" enhancements of AT-command for originated location request | TEI9 | 9.1.0 | | +| CT#45 | CP-090682 | 0185 | | Rel-9 | F | Corrections to UCS2 coding of +CUSD | TEI9 | 9.1.0 | | +| CT#45 | CP-090682 | 0186 | 1 | Rel-9 | B | New AT-commands for mobile terminated location request and disclosure | TEI9 | 9.1.0 | | +| CT#45 | CP-090655 | 0188 | 1 | Rel-9 | A | Correct alignment of notes for +CEREG | SAES | 9.1.0 | | +| CT#45 | CP-090682 | 0189 | | Rel-9 | B | Addition of intermediate result code for +CPBW | TEI9 | 9.1.0 | | +| CT#45 | CP-090682 | 0190 | | Rel-9 | B | New AT-commands for administration of battery | TEI9 | 9.1.0 | | +| CT#45 | CP-090674 | 0192 | 1 | Rel-9 | A | Corrections to +CEMODE | SAES-CSFB,SAES | 9.1.0 | | +| CT#46 | CP-090920 | 0196 | | Rel-9 | A | Correction of direction of data for +CPOS | TEI8 | 9.2.0 | | +| CT#46 | CP-090922 | 0197 | 1 | Rel-9 | F | Correction of usage of underscore (default values) for 27.007 | TEI9 | 9.2.0 | | +| CT#46 | CP-090900 | 0200 | 1 | Rel-9 | A | Correction of outstanding Editor's note on +WS46 | SAES | 9.2.0 | | +| CT#47 | CP-100135 | 0209 | 2 | Rel-9 | D | Correction of minor drafting rule issues for TS 27.007 | TEI9 | 9.3.0 | | +| CT#47 | CP-100102 | 0207 | | Rel-9 | A | Removal of [,<pd1>[,...[,<pdN>]]] in +CGDCONT | TEI | 9.3.0 | | +| CT#47 | CP-100135 | 0208 | | Rel-9 | F | Clarification of parameter type for +CCHO and +CCHC | TEI9 | 9.3.0 | | +| CT#47 | CP-100131 | 0211 | | Rel-9 | A | Incorrect indication of AT commands as parameter commands | TEI8, SAES | 9.3.0 | | +| CT#47 | CP-100135 | 0212 | 1 | Rel-9 | B | +CGDEL – AT-command for deletion of non-active PDP contexts and associated parameters | TEI9 | 9.3.0 | | +| CT#47 | CP-100135 | 0214 | | Rel-9 | A | Incorrect name for test command version of +CGTFTRDP | SAES | 9.3.0 | | +| CT#47 | CP-100107 | 0216 | | Rel-9 | A | Correction of the packet domain event reporting +CGEV | SAES | 9.3.0 | | +| CT#47 | CP-100135 | 0217 | | Rel-9 | F | The value range of <cid> for network initiated PDP contexts is clarified | TEI9 | 9.3.0 | | +| CT#47 | CP-100145 | 0218 | 1 | Rel-9 | B | Addition of new AT-Command related to SSAC | SSAC | 9.3.0 | | +| CT#47 | CP-100144 | 0219 | 1 | Rel-9 | F | Correction of AT command for emergency bearer services | IMS_EMER_G<br>PRS_EPS | 9.3.0 | | +| CT#47 | | | | Rel-9 | | Editorial cleanup by MCC | | 9.3.0 | | +| CT#48 | CP-100339 | 0221 | | Rel-9 | A | Correction of unsolicited result codes for packet domain event reporting | SAES | 9.4.0 | | +| CT#48 | CP-100339 | 0223 | | Rel-9 | A | +CGCONTRDP, alignment of with +CGTFT and +CGTFTRDP | SAES | 9.4.0 | | +| CT#48 | CP-100339 | 0228 | 1 | Rel-9 | A | Description of handling a request to disconnect when only connected to a single PDN | SAES | 9.4.0 | | +| CT#48 | CP-100339 | 0230 | 1 | Rel-9 | A | Support for +CGPADDR returning both IPv4 and IPv6 addresses | SAES | 9.4.0 | | +| CT#48 | CP-100339 | 0232 | 1 | Rel-9 | A | Clarification of relationship between CREG, CEREG and CGREG | SAES | 9.4.0 | | +| CT#48 | CP-100355 | 0234 | | Rel-9 | F | Removal of remaining [,<pd1>[,...[,<pdN>]]] in +CGDCONT | TEI9 | 9.4.0 | | +| CT#48 | CP-100355 | 0238 | | Rel-9 | F | Addition of missing parameter in +CNAP | TEI9 | 9.4.0 | | +| CT#48 | CP-100371 | 0226 | | Rel-10 | B | Support of compressed IPv6 format in AT-commands | TEI10 | 10.0.0 | | +| CT#48 | CP-100369 | 0224 | 2 | Rel-10 | B | Control of P-CSCF address discovery | AT IMS | 10.0.0 | | +| CT#48 | CP-100369 | 0225 | 1 | Rel-10 | B | +CISRVCC and +CIREP, new AT-commands for support of SRVCC | AT IMS | 10.0.0 | | +| CT#48 | CP-100369 | 0233 | 1 | Rel-10 | B | Control of IM CN Subsystem Signalling Flag | AT IMS | 10.0.0 | | +| CT#49 | CP-100520 | 0240 | 1 | Rel-10 | F | Alignment of table headers with AT-command names | TEI10 | 10.1.0 | | +| CT#49 | CP-100492 | 0243 | 2 | Rel-10 | A | AT commands for eCall | eData | 10.1.0 | | +| CT#49 | CP-100485 | 0248 | 1 | Rel-10 | A | Clarification of AcT parameter in CREG, CGREG and CEREG | SAES | 10.1.0 | | +| CT#49 | CP-100571 | 0249 | 4 | Rel-10 | B | USAT over AT | AT_UICC | 10.1.0 | | +| CT#49 | CP-100518 | 0250 | | Rel-10 | F | Clarification to +COPS. | TEI10 | 10.1.0 | | +| CT#49 | CP-100520 | 0251 | 1 | Rel-10 | B | AT command for remaining PIN retries for MT passwords, +CPINR | TEI10 | 10.1.0 | | +| CT#49 | CP-100520 | 0252 | 2 | Rel-10 | B | AT command for supporting multiple cards installed in a ME | TEI10 | 10.1.0 | | +| CT#49 | CP-100520 | 0253 | 1 | Rel-10 | B | AT command for Emergency Numbers +CEN | TEI10 | 10.1.0 | | +| CT#50 | CP-100763 | 0254 | 2 | Rel-10 | B | TC-RT: Introduction of group IDs with prefix | TEI10 | 10.2.0 | | +| CT#50 | CP-100742 | 0256 | 1 | Rel-10 | A | Correction of Table 8.58-1 for +CMTLRA | TEI9 | 10.2.0 | | +| CT#50 | CP-100763 | 0257 | | Rel-10 | F | Correction of terminology for result codes and alignment of Annex B | TEI10 | 10.2.0 | | +| CT#50 | CP-100757 | 0258 | 1 | Rel-10 | B | Examples of AT-commands for USAT | AT_UICC | 10.2.0 | | +| CT#50 | CP-100757 | 0259 | 1 | Rel-10 | C | Multiple corrections to AT-commands for USAT | AT_UICC | 10.2.0 | | +| CT#50 | CP-100757 | 0260 | 2 | Rel-10 | F | Removal of editor's note on security mechanism for AT-commands for USAT | AT_UICC | 10.2.0 | | + +| | | | | | | | | | +|-------|-----------|------|---|--------|---|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------| +| CT#50 | CP-100747 | 0262 | 2 | Rel-10 | A | +CGDCONT syntax | IMS_EMER_G<br>PRS_EPS | 10.2.0 | +| CT#50 | CP-100763 | 0263 | 1 | Rel-10 | F | +CGEV for IP address types | TEI10 | 10.2.0 | +| CT#50 | CP-100763 | 0265 | | Rel-10 | F | Correction of references for +CNAP | TEI10 | 10.2.0 | +| CT#50 | CP-100763 | 0266 | | Rel-10 | F | Correction of action versus parameter commands | TEI10 | 10.2.0 | +| CT#50 | CP-100763 | 0267 | 1 | Rel-10 | | Correction of print of the IP address format | TEI10 | 10.2.0 | +| CT#50 | CP-100763 | 0268 | 1 | Rel-10 | B | New AT-command for Network Emergency Bearer Services Support +CNEM | TEI10 | 10.2.0 | +| CT#50 | CP-100763 | 0270 | 3 | Rel-10 | | AT command for creating connection status event | TEI10 | 10.2.0 | +| CT#51 | CP-110197 | 0271 | 1 | Rel-10 | B | Enhancement of +CPOS and +CPOSR for LPP, capability request and velocity request, GLONASS and SBAS | TEI10 | 10.3.0 | +| CT#51 | CP-110197 | 0272 | | Rel-10 | B | Enhancement and alignment of +CLIP, +CCWA and +CLCC when CLI is not available | TEI10 | 10.3.0 | +| CT#51 | CP-110197 | 0273 | 1 | Rel-10 | F | Support of AT commands for voice | TEI10 | 10.3.0 | +| CT#51 | CP-110188 | 0274 | 1 | Rel-10 | F | Correction of USAT profile activation | AT_UICC | 10.3.0 | +| CT#51 | CP-110188 | 0275 | 1 | Rel-10 | B | Detection of currently active SIM or USIM | AT_UICC | 10.3.0 | +| CT#51 | CP-110188 | 0277 | 1 | Rel-10 | C | Modification of default profiles and write response | AT_UICC | 10.3.0 | +| CT#51 | CP-110188 | 0278 | 1 | Rel-10 | F | Correction of USAT event response | AT_UICC | 10.3.0 | +| CT#51 | CP-110197 | 0279 | 1 | Rel-10 | F | Clarification of relationship between CREG, CEREG and CGREG. Introduction of registration for EPS and non-EPS services for 'SMS only' in CREG. | TEI10 | 10.3.0 | +| CT#51 | CP-110186 | 0280 | 1 | Rel-10 | B | +CAVIMS, availability for voice calls with the IMS | AT IMS | 10.3.0 | +| CT#51 | CP-110197 | 0281 | | Rel-10 | B | Addition of registration status to CREG, CGREG, CEREG command for emergency attached UE | TEI10 | 10.3.0 | +| CT#51 | CP-110197 | 0282 | 2 | Rel-10 | B | +CESQ, new AT-command on extended signal quality | TEI10 | 10.3.0 | +| CT#52 | CP-110454 | 0286 | | Rel-10 | A | +CGDATA, correction of syntax | TEI8 | 10.4.0 | +| CT#52 | CP-110461 | 0287 | 1 | Rel-10 | F | Cleanups for WI AT_UICC | AT_UICC | 10.4.0 | +| CT#52 | CP-110466 | 0291 | 1 | Rel-10 | F | CREG, CEREG and CGREG: clarification for 'out of coverage' | TEI10 | 10.4.0 | +| CT#53 | CP-110669 | 0292 | 2 | Rel-10 | F | Clarifying the indication of availability for voice calls in the IMS and in the PS | AT IMS | 10.5.0 | +| CT#53 | CP-110695 | 0288 | 4 | Rel-11 | B | +CGAUTH, new AT-command for definition of PDP context authentication parameters | TEI11 | 11.0.0 | +| CT#53 | CP-110695 | 0293 | 3 | Rel-11 | B | Enhancements to Event Reporting due to CBS primary notifications | TEI11 | 11.0.0 | +| CT#53 | CP-110695 | 0294 | 1 | Rel-11 | C | Enhancing touch screen actions and events | TEI11 | 11.0.0 | +| CT#53 | CP-110695 | 0295 | 1 | Rel-11 | C | Enhancing supported orientations by AT command +CSO | TEI11 | 11.0.0 | +| CT#53 | CP-110695 | 0296 | 1 | Rel-11 | C | Enhancing the assumption that touch screen size is equal to display screen size | TEI11 | 11.0.0 | +| CT#54 | CP-110875 | 0298 | | Rel-11 | A | Corrections to +VIP | TEI10 | 11.1.0 | +| CT#54 | CP-110865 | 0303 | | Rel-11 | A | +CMOLR: Third Party Address should be specified when Method value set to 5 | TEI9 | 11.1.0 | +| CT#54 | CP-110882 | 0304 | 1 | Rel-11 | C | Add support for display orientation event reporting | TEI11 | 11.1.0 | +| CT#54 | CP-110864 | 0308 | | Rel-11 | A | Correcting syntax of +CMER | TEI8 | 11.1.0 | +| CT#54 | CP-110882 | 0309 | 1 | Rel-11 | B | Introduction of a default PDP context (cid=0) | TEI11 | 11.1.0 | +| CT#54 | CP-110881 | 0310 | 1 | Rel-11 | B | IMS registration information, +CIREG | TEI11 | 11.1.0 | +| CT#54 | CP-110882 | 0311 | | Rel-11 | F | Corrections to +CGCONTRDP and +CGSCONTRDP | TEI11 | 11.1.0 | +| CT#54 | CP-110882 | 0312 | | Rel-11 | F | Addition of missing brackets to make responses optional | TEI11 | 11.1.0 | +| CT#54 | CP-110882 | 0313 | | Rel-11 | F | Correction to +CRLP | TEI11 | 11.1.0 | +| CT#54 | CP-110864 | 0317 | 1 | Rel-11 | A | Corrections to +CGCONTRDP | TEI8 | 11.1.0 | +| CT#54 | CP-110882 | 0318 | | Rel-11 | B | No More PS Data, +CNMPSD | TEI11 | 11.1.0 | +| CT#54 | CP-110882 | 0319 | 2 | Rel-11 | B | Setting UE Usage Setting, +CEUS | TEI11 | 11.1.0 | +| CT#54 | CP-110882 | 0320 | 1 | Rel-11 | C | Modifying +CGCONTRDP to indicate that connectivity is provided by a LIPA PDN connection | TEI11 | 11.1.0 | +| CT#55 | CP-120113 | 0322 | | Rel-11 | A | +CESQ=?, removal of non-existing parameter <rep> | TEI10 | 11.2.0 | +| CT#55 | CP-120113 | 0324 | 1 | Rel-11 | A | +CESQ, alignment of parameters with value ranges in 3GPP TSs | TEI10 | 11.2.0 | +| CT#55 | CP-120113 | 0326 | | Rel-11 | A | Correction of +CSUS | TEI10 | 11.2.0 | +| CT#55 | CP-120125 | 0327 | 1 | Rel-11 | F | Correction of action command syntax according to V.250 | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0328 | | Rel-11 | F | Usage of AT-commands in insecure scenarios | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0329 | | Rel-11 | F | Correction of AT-command +CALCC | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0330 | | Rel-11 | F | Response to test version of AT- commands shall not be optional | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0331 | 1 | Rel-11 | C | +CREG, +CGREG and +CEREG, addition of cause values | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0332 | | Rel-11 | F | Indication of optional parameter in AT-command syntax | TEI11 | 11.2.0 | +| CT#55 | CP-120124 | 0333 | 1 | Rel-11 | F | Clarification of SRVCC handover information in +CIREPH AT command | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0335 | | Rel-11 | F | Alignment of descriptions for context parameters | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0337 | 2 | Rel-11 | B | Setting configuration values specified in TS 24.167, +CEVDP, +CVD, +CMMIVT | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0338 | 1 | Rel-11 | B | Adding +CASIMS: SMS using IMS support indication | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0340 | | Rel-11 | F | Correct +CREG reported status | TEI11 | 11.2.0 | +| CT#55 | CP-120125 | 0342 | | Rel-11 | F | Corrections to CPNER parameters | TEI11 | 11.2.0 | +| CT#56 | CP-120309 | 0343 | 1 | Rel-11 | F | Alignment of response codes | TEI11 | 11.3.0 | +| CT#56 | CP-120309 | 0344 | | Rel-11 | F | Removal of editor's note for security aspects of public warning systems in Rel-11 | TEI11 | 11.3.0 | + +| | | | | | | | | | +|-------|-----------|------|---|--------|---|-----------------------------------------------------------------------------------|---------------------|--------| +| CT#56 | CP-120309 | 0345 | | Rel-11 | F | Response to +CNEM=? is missing | TEI11 | 11.3.0 | +| CT#56 | CP-120309 | 0346 | | Rel-11 | F | Correction of value range for <QCI> | TEI11 | 11.3.0 | +| CT#56 | CP-120309 | 0347 | 1 | Rel-11 | B | <SS_code> added to result codes +CSSI and +CSSU | TEI11 | 11.3.0 | +| CT#56 | CP-120309 | 0348 | | Rel-11 | F | Update of AT command +CMUX | TEI11 | 11.3.0 | +| CT#56 | CP-120313 | 0349 | 2 | Rel-11 | F | Modifications to UR code for SRVCC due to introduction of vSRVCC | vSRVCC-CT | 11.3.0 | +| CT#56 | CP-120309 | 0354 | 2 | Rel-11 | F | Correction of TFT description | TEI11 | 11.3.0 | +| CT#56 | CP-120325 | 0355 | 3 | Rel-11 | B | AT commands for URI dialling | ATUREI | 11.3.0 | +| CT#56 | CP-120309 | 0356 | | Rel-11 | F | Correction of response to +CPSB? | TEI11 | 11.3.0 | +| CT#57 | CP-120584 | 0357 | 2 | Rel-11 | B | +CPOS and +CPOSR, enhancement for OTDOA | TEI11 | 11.4.0 | +| CT#57 | CP-120604 | 0359 | 1 | Rel-11 | B | Completion of basic dialup scenarios with +CDU | ATUREI | 11.4.0 | +| CT#57 | CP-120584 | 0360 | | Rel-11 | F | Clarification of time-information elements of +CPOS | TEI11 | 11.4.0 | +| CT#57 | CP-120604 | 0362 | 1 | Rel-11 | B | Service URNs in AT commands | ATUREI | 11.4.0 | +| CT#58 | CP-120794 | 0364 | 1 | Rel-11 | F | Parameters missing for response to +CUSATE | TEI11 | 11.5.0 | +| CT#58 | CP-120813 | 0365 | 3 | Rel-11 | B | Addition of per-call based SS-parameters to +CDU | ATUREI | 11.5.0 | +| CT#58 | CP-120813 | 0366 | 3 | Rel-11 | F | Completion of AT command for hangup | ATUREI | 11.5.0 | +| CT#58 | CP-120813 | 0367 | 3 | Rel-11 | B | Further refinement of the call monitoring command and its responses | ATUREI | 11.5.0 | +| CT#58 | CP-120794 | 0368 | 1 | Rel-11 | F | Inclusion of APN aggregate maximum bit rate in +CGEQOSRDP | TEI11 | 11.5.0 | +| CT#58 | CP-120814 | 0369 | 7 | Rel-11 | B | Communication service indication in AT commands | ATUREI | 11.5.0 | +| CT#58 | CP-120794 | 0370 | | Rel-11 | B | New method introduced for +CMOLRE | TEI11 | 11.5.0 | +| CT#58 | CP-120794 | 0371 | 1 | Rel-11 | F | +CGCONTRDP: support providing more or less than 2 IP addresses | TEI11 | 11.5.0 | +| CT#58 | CP-120861 | 0373 | 3 | Rel-11 | B | Extension of +CPOSR | TEI11 | 11.5.0 | +| CT#58 | CP-120794 | 0374 | 1 | Rel-11 | B | Time of day inclusion for +CPOS | TEI11 | 11.5.0 | +| CT#58 | CP-120794 | 0376 | 1 | Rel-11 | F | DTD corrections for +CPOS and +CPOSR | TEI11 | 11.5.0 | +| CT#58 | CP-120813 | 0377 | 2 | Rel-11 | B | ATUREI editor's notes | ATUREI | 11.5.0 | +| CT#58 | CP-120795 | 0379 | 2 | Rel-11 | F | +CEPPI: Power Preference Indication for EPS | TEI11 | 11.5.0 | +| CT#58 | CP-120806 | 0380 | 2 | Rel-11 | F | AT command support for rSRVCC handover | rSRVCC-CT | 11.5.0 | +| CT#59 | | | | Rel-11 | | Enabling upper layers to deal with GPRS, EPS, VBS / VGCS and eMLPP related errors | | 11.6.0 | +| CT#59 | CP-130115 | 0378 | 3 | Rel-11 | F | Completion of presentation-related supplementary services wrt SIP-URIs | TEI11 | 11.6.0 | +| CT#59 | CP-130120 | 0381 | 2 | Rel-11 | B | Completion of mid-call related SSs for SIP-URIs | ATUREI | 11.6.0 | +| CT#59 | CP-130120 | 0382 | 1 | Rel-11 | B | Corrections to +CECUG | ATUREI | 11.6.0 | +| CT#59 | CP-130120 | 0383 | | Rel-11 | F | SDP in media profiles | ATUREI | 11.6.0 | +| CT#59 | CP-130120 | 0386 | 3 | Rel-11 | B | Renaming of 'voice client' | ATUREI | 11.6.0 | +| CT#59 | CP-130120 | 0388 | 1 | Rel-11 | F | Update of media during a call | ATUREI | 11.6.0 | +| CT#59 | CP-130120 | 0390 | 1 | Rel-11 | B | Clarification to PDP context for emergency services | TEI12 | 12.0.0 | +| CT#59 | CP-130129 | 0384 | 1 | Rel-12 | F | New AT command - Report network error codes +CNEC | TEI12 | 12.0.0 | +| CT#60 | CP-130234 | 0385 | | Rel-12 | B | Corrections of +CSSAC | SSAC | 12.1.0 | +| CT#60 | CP-130264 | 0394 | 1 | Rel-12 | A | Enhancement of +CGSN | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0395 | | Rel-12 | B | Supported radio accesses, +CSRA | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0396 | 4 | Rel-12 | B | Correction to media for SIP-URI | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0398 | 1 | Rel-12 | F | MSRP as media for SIP-URI | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0400 | 1 | Rel-12 | C | Minor correction for +CUSATW | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0401 | 1 | Rel-12 | F | AT command for Circuit Switched Fallback Support | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0402 | 2 | Rel-12 | B | Removal of Editors note for ATURI | ATUREI | 12.1.0 | +| CT#60 | CP-130254 | 0405 | 1 | Rel-12 | A | Missing optionality for UR-code +CMCCSS7: <CUG_index> | ATUREI, TEI11 | 12.1.0 | +| CT#60 | CP-130254 | 0407 | 1 | Rel-12 | A | Alignments and corrections of descriptions and parameters | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0408 | | Rel-12 | F | Call Forwarding URI support | ATUREI | 12.1.0 | +| CT#60 | CP-130264 | 0410 | 2 | Rel-12 | A | General error extensions to +CMEE | TEI12 | 12.1.0 | +| CT#60 | CP-130264 | 0411 | 1 | Rel-12 | B | +CCSFB informative example correction | TEI12 | 12.2.0 | +| CT#61 | CP-130510 | 0413 | | Rel-12 | F | +CDEFMP error response | ATUREI | 12.2.0 | +| CT#61 | CP-130510 | 0415 | 1 | Rel-12 | A | +CPOS and +CPOSR Enhancements for LTE ECID and OTDOA | TEI12 | 12.2.0 | +| CT#61 | CP-130510 | 0416 | | Rel-12 | B | +CGDCONT handover indication | TEI12 | 12.3.0 | +| CT#62 | CP-130762 | 0417 | 1 | Rel-12 | B | New AT command to control message waiting indication | TEI12 | 12.3.0 | +| CT#62 | CP-130762 | 0418 | 2 | Rel-12 | B | Update of +CNMPSD AT command | TEI12 | 12.3.0 | +| CT#62 | CP-130762 | 0419 | 2 | Rel-12 | F | Update of +CCFC AT command | TEI12 | 12.3.0 | +| CT#62 | CP-130762 | 0420 | 1 | Rel-12 | F | USSI support for +CUSD | TEI12 | 12.3.0 | +| CT#62 | CP-130762 | 0421 | 1 | Rel-12 | B | MS initiated PDP Context Activation without PDP address | TEI12 | 12.3.0 | +| CT#62 | CP-130762 | 0422 | 1 | Rel-12 | C | +CCFCU time conditions | TEI12, ATURI | 12.4.0 | +| CT#63 | | | | Rel-12 | | +CGDCONT - missing parameters for NAS signalling low priority indications and EAB | TEI12, SIMTC-RAN_OC | 12.4.0 | +| CT#63 | CP-140144 | 0425 | 2 | Rel-12 | F | Update of AT commands accepted when MT is pending SIM PIN, SIM PUK, or PH-SIM | TEI12 | 12.4.0 | +| CT#64 | CP-140331 | 0426 | 1 | Rel-12 | F | Multiple PDP context activation using +CGACT | TEI12 | 12.5.0 | +| CT#64 | CP-140331 | 0428 | 1 | Rel-12 | F | +CUSATD and +CUSATA alignment | TEI12 | 12.5.0 | +| CT#64 | CP-140331 | 0429 | 1 | Rel-12 | F | Clarifications for +CUSATD | TEI12 | 12.5.0 | +| CT#64 | CP-140331 | 0430 | 2 | Rel-12 | F | Message waiting indication subscription failure error code | TEI12 | 12.5.0 | +| CT#64 | CP-140331 | 0432 | 1 | Rel-12 | F | Removal of redundant "EAB override" in +CGDCONT | TEI12, SIMTC-RAN_OC | 12.5.0 | +| CT#65 | | | | Rel-12 | | Corrupted fonts fixed by MCC | | 12.6.0 | +| CT#65 | CP-140662 | 0435 | | Rel-12 | B | AT commands in support of ACB-skip | SCM_LTE-CT | 12.6.0 | + +| | | | | | | | | | +|-------|-----------|------|---|--------|---|------------------------------------------------------------------------------------------------|----------------|--------| +| CT#65 | CP-140664 | 0436 | | Rel-12 | F | Remove support of CDIVN from +CCFCU | TEI12 | 12.6.0 | +| CT#65 | CP-140664 | 0437 | 1 | Rel-12 | F | +CPOS Modifications for OTDOA and ECID | TEI12 | 12.6.0 | +| CT#66 | | | | Rel-12 | | Misalignment of +CMWI between the AT-command syntax in the table and the parameter description | | 12.7.0 | +| | CP-140836 | 0438 | 1 | | F | | TEI12 | | +| CT#66 | CP-140836 | 0439 | | Rel-12 | F | Alignment of parameter description in +CCSFB | TEI12 | 12.7.0 | +| CT#66 | | | | Rel-12 | | Misalignment of +CSCM between the AT-command syntax in the table and the parameter description | | 12.7.0 | +| | CP-140855 | 0440 | | | F | | SCM_LTE-CT | | +| CT#66 | | | | Rel-12 | | Updates to +CGDCONT to allow security protected transmission of ESM information | | 12.7.0 | +| | CP-140836 | 0441 | 3 | | F | | TEI12 | | +| CT#66 | CP-140836 | 0442 | 4 | Rel-12 | F | Clean split of 'Defined Events' between CPOS and +CPOSR | TEI12 | 12.7.0 | +| CT#66 | CP-140836 | 0443 | | Rel-12 | F | Correction of ECID measurements parameters in +CPOS | TEI12 | 12.7.0 | +| CT#66 | CP-140836 | 0444 | | Rel-12 | F | Modification of <Strobe> element usage in +CPOS | TEI12 | 12.7.0 | +| CT#66 | CP-140836 | 0446 | 1 | Rel-12 | F | AT command update for Extended TFT | TEI12 | 12.7.0 | +| CT#66 | | | | Rel-12 | | | | 12.7.0 | +| | CP-140843 | 0447 | 2 | | B | Addition of AT-commands for UE Power Saving Mode | MTCe-UEPCOP-CT | | +| CT#66 | CP-140850 | 0448 | | Rel-12 | F | Alignment of value range for QCI | GCSE_LTE-CT | 12.7.0 | +| CT#66 | CP-140836 | 0449 | | Rel-12 | F | Corrections to +CUSATW AT Command | TEI12 | 12.7.0 | +| CT#67 | | | | Rel-12 | | BeiDou System (BDS) support in +CPOS and +CPOSR positioning commands | | 12.8.0 | +| | CP-150064 | 0456 | 1 | | F | | TEI12 | | +| CT#67 | CP-150083 | 0457 | 2 | Rel-13 | B | +CEMBMSCFG: AT command for eMBMS Configuration | TEI13 | 13.0.0 | +| CT#67 | CP-150083 | 0458 | 2 | Rel-13 | B | +CEMBMSR: AT command for eMBMS Status Reporting | TEI13 | 13.0.0 | +| CT#67 | CP-150083 | 0459 | 2 | Rel-13 | B | +CEMBMSSRV: AT command for eMBMS Service Configuration | TEI13 | 13.0.0 | +| CT#67 | CP-150083 | 0460 | 3 | Rel-13 | B | +CEMBMSDATA: AT command for eMBMS Data State | TEI13 | 13.0.0 | +| CT#67 | CP-150083 | 0461 | 3 | Rel-13 | B | +CEMBMSCNT: AT command for eMBMS Counting Procedure | TEI13 | 13.0.0 | +| CT#67 | CP-150083 | 0462 | 2 | Rel-13 | B | Enhance +CGCONTRDP for MTU size indication | TEI13 | 13.0.0 | +| CT#67 | CP-150083 | 0463 | 2 | Rel-13 | B | Enhance +CGDCONT for MTU size discovery configuration | TEI13 | 13.0.0 | +| CT#68 | CP-150329 | 0469 | | Rel-13 | C | AT Command +CTZR: enhancement to extended time zone reporting | TEI13 | 13.1.0 | +| CT#68 | | | | Rel-13 | | GNSS related corrections in CPOS and +CPOSR positioning commands | | 13.1.0 | +| | CP-150310 | 0471 | | | A | | TEI12 | | +| CT#68 | CP-150329 | 0472 | 1 | Rel-13 | B | Support for WLAN Offload Indication | TEI13 | 13.1.0 | +| CT#68 | CP-150310 | 0473 | 1 | Rel-13 | A | Type correction for +CGDCONT | TEI12 | 13.1.0 | +| CT#69 | CP-150529 | 0476 | 2 | Rel-13 | B | Update to +CSCON AT command | TEI13 | 13.2.0 | +| CT#69 | | | | Rel-13 | | Missing parameter definitions and support for 'Early Position Fix' in +CPOS | | 13.2.0 | +| | CP-150511 | 0478 | 1 | | A | | TEI12 | | +| CT#69 | CP-150529 | 0479 | 1 | Rel-13 | B | New AT command for WLAN Offload Assistance Data | TEI13 | 13.2.0 | +| CT#69 | CP-150529 | 0480 | 1 | Rel-13 | B | New AT command for WLAN Offload based on cell measurements | TEI13 | 13.2.0 | +| CT#70 | | | | Rel-13 | | AT command in support of Application-specific congestion control for data communication (ACDC) | | 13.3.0 | +| | CP-150719 | 0464 | 3 | | C | | ACDC-CT | | +| CT#70 | | | | Rel-13 | | MS support of Local address in TFT indicator for +CGDCONT and +CGCONTRDP | | 13.3.0 | +| | CP-150710 | 0481 | 1 | | F | | TEI13 | | +| CT#70 | | | | Rel-13 | | +CEMBMSSAI: AT command to determine available eMBMS Service Area Identities | | 13.3.0 | +| | CP-150710 | 0482 | 1 | | B | | TEI13 | | +| CT#70 | | | | Rel-13 | | AT Command +CGEQOS (Define EPS quality of service): correction of value range for CQI | | 13.3.0 | +| | CP-150694 | 0484 | 2 | | A | | GCSE_LTE-CT | | +| CT#71 | CP-160085 | 0485 | 1 | Rel-13 | F | ToD related corrections for +CPOS and +CPOSR commands | TEI13 | 13.4.0 | +| CT#72 | | | | Rel-13 | | Correction of indicator for support of Local address in TFT for +CGCONTRDP | | 13.5.0 | +| | CP-160318 | 0486 | 1 | | F | | TEI13 | | +| CT#72 | CP-160307 | 0487 | 1 | Rel-13 | F | Correction to +CSCM in support of ACDC | ACDC-CT | 13.5.0 | +| CT#72 | CP-160331 | 0488 | 2 | Rel-14 | B | +CABTSR: AT command for SM back-off timer status reporting | TEI14 | 14.0.0 | +| CT#72 | CP-160331 | 0489 | 2 | Rel-14 | B | +CABTRDP: AT command for SM back-off timer query | TEI14 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | CT#73 | CP-160589 | 0491 | 3 | B | Transport of Data via the Control Plane, +CTDCP | 14.1.0 | +| 2016-09 | CT#73 | CP-160511 | 0492 | 1 | B | AT Command for Non-IP Link MTU of non-IP connection | 14.1.0 | +| 2016-12 | CT#74 | CP-160737 | 0493 | | B | AT Command for rate control | 14.2.0 | +| 2016-12 | CT#74 | CP-160737 | 0494 | 3 | B | Adding NB-IoT and EC-GSM-IoT as new access technologies | 14.2.0 | +| 2016-12 | CT#74 | CP-160737 | 0495 | 2 | C | Correction to MO data via control plane AT-command | 14.2.0 | +| 2016-12 | CT#74 | CP-160737 | 0469 | | B | Mobile terminated CP data reporting +CRTDCP | 14.2.0 | +| 2016-12 | CT#74 | CP-160737 | 0498 | 1 | B | AT Command for EPS Attach without PDN Connection | 14.2.0 | +| 2016-12 | CT#74 | CP-160754 | 0499 | 1 | F | New QCI values for V2X services | 14.2.0 | +| 2016-12 | CT#74 | CP-160737 | 0500 | 1 | B | AT Command for eDRX setting | 14.2.0 | +| 2016-12 | CT#74 | CP-160798 | 0501 | | B | Indication of access transfer of PDN for emergency bearer services from non-3GPP access network | 14.2.0 | +| 2016-12 | CT#74 | CP-160753 | 0502 | | F | Corrections and improvements for +CPSMS | 14.2.0 | +| 2016-12 | CT#74 | CP-160753 | 0503 | | F | Alignment of +CEPPI with other AT-commands | 14.2.0 | +| 2016-12 | CT#74 | CP-160753 | 0504 | 1 | F | AT commands for indoor positioning | 14.2.0 | +| 2016-12 | CT#74 | CP-160737 | 0505 | 2 | B | CIOT Optimization Configuration | 14.2.0 | +| 2017-03 | CT#75 | CP-170136 | 0490 | 4 | B | AT command for DRVCC indication | 14.3.0 | +| 2017-03 | CT#75 | CP-170126 | 0506 | 3 | F | Addition of cid in +CSODCP and +CRTDCP and editor's note removal | 14.3.0 | +| 2017-03 | CT#75 | CP-170136 | 0507 | 5 | F | +CECALL changes for provision of MSD for eCall and eCall Notification +CECN | 14.3.0 | +| 2017-03 | CT#75 | CP-170126 | 0509 | 3 | B | +CRCES: read coverage (enhancement) status | 14.3.0 | +| 2017-06 | CT#76 | CP-171071 | 0510 | | F | +CRCES: Fixing syntax error | 14.4.0 | +| 2017-06 | CT#76 | CP-171073 | 0511 | | F | CP Data path congestion AT CMD error response | 14.4.0 | +| 2017-06 | CT#76 | CP-171069 | 0513 | 1 | A | Addition of TMGI in +CEMBMSDATA | 14.4.0 | +| 2017-09 | CT#77 | CP-172114 | 0514 | 1 | F | Using a single +CCMMD to accept a subset of incoming proposed set of media | 14.5.0 | +| 2017-09 | CT#77 | CP-172114 | 0515 | 1 | F | Updates to +CABTRDP AT command | 14.5.0 | +| 2017-09 | CT#77 | CP-172114 | 0516 | 1 | F | Updates to +CABTSR AT command | 14.5.0 | +| 2017-09 | CT#77 | CP-172110 | 0518 | 3 | B | Addition of AT commands for V2X UE conformance test | 14.5.0 | +| 2017-12 | CT#78 | CP-173067 | 0521 | 1 | F | Clarifications on +CABTSR & +CABTRDP | 14.6.0 | +| 2017-12 | CT#78 | CP-173056 | 0522 | 3 | F | Clarifications on commands for UE test loop function | 14.6.0 | +| 2017-12 | CT#78 | CP-173067 | 0523 | 3 | F | Update to +CGDCONT and +CGCONTRDP for Reliable Data Service | 14.6.0 | +| 2017-12 | CT#78 | CP-173069 | 0519 | 1 | B | Preparation for the 5G access | 15.0.0 | +| 2017-12 | CT#78 | CP-173079 | 0520 | | F | Misalignment between running text and Annex B for result codes | 15.0.0 | +| 2017-12 | CT#78 | CP-173081 | 0524 | 1 | B | AT-commands for application level measurement reporting | 15.0.0 | +| 2017-12 | CT#78 | CP-173069 | 0525 | | B | Enhancements to +WS46 for the 5G-system | 15.0.0 | +| 2018-03 | CT#79 | CP-180062 | 0527 | | A | Corrections to UE test commands +CATM and +CCUTLE | 15.1.0 | +| 2018-03 | CT#79 | CP-180065 | 0529 | | A | Corrections to test form of +CABTRDP | 15.1.0 | +| 2018-03 | CT#79 | CP-180089 | 0534 | 1 | F | Correct description of +CNNMPSD | 15.1.0 | +| 2018-03 | CT#79 | CP-180092 | 0535 | 1 | B | Enhancement to +CNNMPSD for BL UEs and NB-IoT UEs | 15.1.0 | +| 2018-03 | CT#79 | CP-180065 | 0537 | | A | Corrections to +CGDCONT for Reliable Data Service | 15.1.0 | +| 2018-03 | CT#79 | CP-180089 | 0538 | 2 | B | Support for PS Data Off in AT Commands | 15.1.0 | +| 2018-03 | CT#79 | CP-180089 | 0539 | | F | Update to +CEMBMSSAI to include Frequency and Service area identity | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0540 | 2 | B | Support for 5G in AT-commands +CPNET and +CSRA | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0541 | | B | Support for 5G in AT-command +CPOL | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0542 | 1 | B | 5G in AT-command for preferred network status | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0543 | 3 | B | 5G in AT-commands for network registration and PLMN selection | 15.1.0 | +| 2018-03 | CT#79 | CP-180060 | 0547 | | A | Correction to read command of +CEREG when <n>=4 and <n>=5 | 15.1.0 | +| 2018-03 | CT#79 | CP-180113 | 0549 | 3 | A | Addition of AT command for V2X UTC time reset for UE conformance test | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0550 | | B | Applicability of service specific access control restriction status, +CSSAC, for 5G | 15.1.0 | +| 2018-03 | CT#79 | CP-180089 | 0551 | | F | Fix reference to 3GPP TS 23.227 | 15.1.0 | +| 2018-03 | CT#79 | CP-180089 | 0552 | 1 | F | Fix "unsolicited result code" confusion | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0553 | | B | Applicability for Session start and stop for MMTEL and SMSOverIP applications, +CSCM, for 5G | 15.1.0 | +| 2018-03 | CT#79 | CP-180076 | 0554 | | B | Applicability for Application Start and Stop indication for applications other than MMTEL and SMSOverIP, +CACDC, for 5G | 15.1.0 | +| 2018-06 | CT#80 | CP-181050 | 0556 | | A | Update of +CUSPCREQ AT command | 15.2.0 | +| 2018-06 | CT#80 | CP-181076 | 0557 | | F | Clarification in use of <SDP_md> in +CMCCS | 15.2.0 | +| 2018-06 | CT#80 | CP-181076 | 0558 | | F | Corrections to +CEMBMSSAI | 15.2.0 | +| 2018-06 | CT#80 | CP-181076 | 0559 | | F | Support of +CDU in +CVMOD | 15.2.0 | +| 2018-06 | CT#80 | CP-181076 | 0560 | | F | CME ERROR is misspelt in +CAEMLPP | 15.2.0 | +| 2018-06 | CT#80 | CP-181058 | 0561 | 3 | B | Inclusion of error codes for 5G, and update of error codes for CS, GPRS and EPS | 15.2.0 | +| 2018-06 | CT#80 | CP-181057 | 0562 | 1 | F | Corrections to AT-commands on network registration | 15.2.0 | +| 2018-06 | CT#80 | CP-181057 | 0563 | | F | Support of +CNEM in 5G | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------------|--------| +| 2018-06 | CT#80 | CP-181058 | 0565 | 1 | B | Removal of Editor's Notes for 5G on commands for alignment between 5GS and EPS | 15.2.0 | +| 2018-06 | CT#80 | CP-181057 | 0566 | | B | Extend +CSCON for 5G and Multi-RAT Dual Connectivity | 15.2.0 | +| 2018-06 | CT#80 | CP-181061 | 0567 | 1 | B | [+CBPI] Bandwidth Preference indication for BL UEs and UEs in coverage enhancement mode | 15.2.0 | +| 2018-06 | CT#80 | CP-181062 | 0568 | 1 | B | AT commands for Enhanced Calling Name (eCNAM) | 15.2.0 | +| 2018-06 | CT#80 | CP-181058 | 0569 | 1 | F | Clarification to registration commands for 5GS | 15.2.0 | +| 2018-06 | CT#80 | CP-181058 | 0570 | 2 | B | AT+CSUPI | 15.2.0 | +| 2018-06 | CT#80 | CP-181058 | 0571 | 2 | B | Support for 5G in AT-commands +CGDCONT | 15.2.0 | +| 2018-06 | CT#80 | CP-181057 | 0572 | 1 | B | Support for 5G in AT-commands +CGCONTRDP and +CGSCONTRDP | 15.2.0 | +| 2018-06 | CT#80 | CP-181058 | 0573 | 2 | B | Support for 5G in AT-commands +CGTFT and +CGTFTRDP | 15.2.0 | +| 2018-06 | CT#80 | CP-181058 | 0574 | 2 | B | AT-commands +CG5QOS and +CG5QOSRDP for 5G QoS | 15.2.0 | +| 2018-09 | CT#81 | CP-182144 | 0575 | | B | Inclusion and alignment of error codes for GPRS, UMTS, EPS and 5G | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0576 | | F | Removal of TBDs and editor's notes in registration and PLMN selection commands | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0577 | 2 | B | AT command for UE policy delivery | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0578 | 1 | B | AT Command for Allowed NSSAI | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0579 | | B | +CGSMS not applicable to UE in E-UTRAN or NG-RAN | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0580 | 1 | B | New AT command to set access selection preferences for MO SMS over NAS in 5GS | 15.3.0 | +| 2018-09 | CT#81 | CP-182232 | 0582 | 3 | A | Addition of new AT commands +CCBRREQ and +CV2XDTDS for V2X testing | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0583 | 3 | F | General remark about 5GS PDU Sessions and EPS PDN Connections | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0584 | 2 | F | AT Command to enable MICO mode | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0585 | 3 | F | Adding RRC Inactive and CN type in CSCON | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0586 | | F | Correction to AT+CSCON when MT connected to NR | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0587 | | B | AT-commands for IMS in 5G | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0588 | | B | AT-command for primary notification event reporting in 5G | 15.3.0 | +| 2018-09 | CT#81 | CP-182159 | 0589 | | B | Completion of AT-commands for application level measurement reporting | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0590 | | F | Extend +CGTFT test command for QRI | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0591 | | F | Correction to +CG5QOS and +CG5QOSRDP | 15.3.0 | +| 2018-09 | CT#81 | CP-182148 | 0592 | | B | New QCI for MCVideo | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0593 | 1 | F | Extend +CGDCONT for always-on PDU session | 15.3.0 | +| 2018-09 | CT#81 | CP-182120 | 0595 | 1 | A | Addition of new AT command +CSPSAIR for V2X testing | 15.3.0 | +| 2018-09 | CT#81 | CP-182146 | 0596 | | F | +CBPI: fix syntax | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0597 | 1 | F | Update +CNEM to include support for emergency services fallback | 15.3.0 | +| 2018-09 | CT#81 | CP-182158 | 0598 | 1 | F | Adding support for RDS port numbers and Acknowledgement | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0599 | | B | AT commands +CSBTSR and +CSBTRDP for supporting S-NSSAI based backoff timer report | 15.3.0 | +| 2018-09 | CT#81 | CP-182144 | 0600 | | B | AT commands +CSDBTSR and +CSDBTRDP for supporting S-NSSAI and DNN based backoff timer report | 15.3.0 | +| 2018-09 | CT#81 | CP-182122 | 0602 | | A | Correction on +CABTSR and +CABTRDP | 15.3.0 | +| 2018-12 | CT#82 | CP-183043 | 0564 | 3 | B | Addition of the extended emergency number list in AT-command +CEN | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0603 | | B | Alignment of error codes with TS 24.501 | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0604 | 2 | F | Correcting +CNMPSD for 5G | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0605 | 2 | F | Correcting +CPSMS for 5G | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0606 | 2 | F | Correcting +CEPPI for 5G | 15.4.0 | +| 2018-12 | CT#82 | CP-183075 | 0608 | | A | Update of description of AT command +CUSPCREQ | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0609 | 1 | F | Resolving Editor Note regarding NR cell connected to EPS core | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0610 | 1 | B | Update +CGDCONT and +CGCONTRDP to support always-on PDU session | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0611 | 1 | F | Definition of S-NSSAI parameter format | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0612 | | F | Removal of the EN on "New AT-command(s) for 5G UE settings like e.g. voice, data & power" | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0613 | | F | Assignment of values for +WS46 | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0614 | | F | Removal of the EN on "Delete non-active PDP contexts" | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0615 | 1 | F | Removal of editor's notes on eMBMS and 5G | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0616 | 1 | F | Removal of editor's note for +CAVIMS and 5G | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0617 | 2 | F | Updates to TS 24.501 clause references | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0618 | 1 | F | Corrections to +CMICO | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0619 | 1 | F | New AT command to use SMS over NAS +C5GUSMS | 15.4.0 | +| 2018-12 | CT#82 | CP-183043 | 0622 | 1 | F | Definition of Allowed_NSSAI parameter format | 15.4.0 | +| 2019-03 | CT#83 | CP-190091 | 0620 | 6 | F | New AT Command to request LADN information from the network +CRLADN | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0621 | 5 | F | New AT Command for enabling reporting of LADN information from the MT +CLADN | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0624 | | F | Alignment of error codes with TS 24.501 v15.2.0 | 15.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------|--------| +| 2019-03 | CT#83 | CP-190091 | 0625 | 6 | F | New AT command for supporting UE requested NSSAI | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0626 | 2 | F | Inclusion of 5G in +CPBS | 15.5.0 | +| 2019-03 | CT#83 | CP-190100 | 0627 | | F | Update of the general clause for AT-commands for the PS-domain | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0628 | 4 | F | New AT commands for network slicing | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0630 | | F | Corrections to +CMICO command | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0632 | 1 | F | Support for Traffic Segregation | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0633 | | F | Correction on the general remark about 5GS | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0634 | 1 | F | Support for 5G NR signal quality indicator | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0635 | | F | Corrections for access technology connectivity to core network in +CEREG | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0636 | 1 | F | Resolve Editor's Note in +CGACT | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0637 | | F | Resolve Editor's Note in +CGAUTO | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0638 | 1 | F | Resolve Editor's Note in +CGCMOD | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0639 | | F | Resolve Editor's Note in +CIPCA | 15.5.0 | +| 2019-03 | CT#83 | CP-190100 | 0641 | 1 | F | Addition of missing QCIs and 5QCIs | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0642 | | F | Removal of text on applicability to 5GS | 15.5.0 | +| 2019-03 | CT#83 | CP-190091 | 0643 | | F | Alignment on description of NSSAI | 15.5.0 | +| 2019-03 | CT#83 | CP-190108 | 0640 | | B | Addition of new QCIs and new 5QCIs for Enhanced Framework for Uplink Streaming (E-FLUS) | 16.0.0 | +| 2019-06 | CT#84 | CP-191125 | 0645 | | A | Correction of numeric error code values | 16.1.0 | +| 2019-06 | CT#84 | CP-191125 | 0647 | | A | Alignment of error codes with TS 24.501 v15.3.0 | 16.1.0 | +| 2019-06 | CT#84 | CP-191125 | 0649 | | A | Correction of parameter name <MICO_Mode> | 16.1.0 | +| 2019-06 | CT#84 | CP-191069 | 0652 | 2 | B | Indicating to the TE whether the UE is EPS attached for access to RLOS | 16.1.0 | +| 2019-06 | CT#84 | CP-191144 | 0653 | | B | Indicating the selected PLMN for access to restricted local operator services | 16.1.0 | +| 2019-06 | CT#84 | CP-191125 | 0655 | | A | Correction to access technology selected in +COPS | 16.1.0 | +| 2019-06 | CT#84 | CP-191144 | 0656 | 1 | B | Indicating to the MT the user's intention for requesting access to RLOS | 16.1.0 | +| 2019-06 | CT#84 | CP-191125 | 0658 | 1 | A | Correction to AT-command +CIREPI to support non-3GPP VoPS indication | 16.1.0 | +| 2019-06 | CT#84 | CP-191125 | 0660 | 2 | A | Removal of editor's note for +CABTSR and +CABTRDPt | 16.1.0 | +| 2019-06 | CT#84 | CP-191128 | 0661 | | B | Add Active Time And Strictly Periodic Registration Timer indication to +CMICO command | 16.1.0 | +| 2019-06 | CT#84 | CP-191128 | 0662 | 1 | B | Support for 5GS CIoT in +CCIOTOPT | 16.1.0 | +| 2019-09 | CT#85 | CP-192072 | 0665 | | F | Alignment of error codes with 3GPP TS 24.301 and 3GPP TS 24.501 | 16.2.0 | +| 2019-09 | CT#85 | CP-192051 | 0666 | 1 | F | Clarification of the bitmap for CIoT optimization | 16.2.0 | +| 2019-09 | CT#85 | CP-192055 | 0670 | 1 | F | Correction on PS data off indicator and status | 16.2.0 | +| 2019-09 | CT#85 | CP-192045 | 0672 | 1 | A | Support for SSC mode 2 and SSC mode 3 | 16.2.0 | +| 2019-09 | CT#85 | CP-192071 | 0673 | 1 | B | EPS fallback status +CEPSFBS | 16.2.0 | +| 2019-12 | CT#86 | CP-193116 | 0663 | 9 | B | AT Command for CSG Feature Support | 16.3.0 | +| 2019-12 | CT#86 | CP-193116 | 0664 | 9 | B | AT Command for CSG support indication | 16.3.0 | +| 2019-12 | CT#86 | CP-193104 | 0674 | 1 | F | Alignment of error codes with 3GPP TS 24.501 | 16.3.0 | +| 2019-12 | CT#86 | CP-193115 | 0677 | 2 | F | AT command update for SINE_5G | 16.3.0 | +| 2019-12 | CT#86 | CP-193092 | 0679 | 1 | F | Correction to +CGDCONT | 16.3.0 | +| 2019-12 | CT#86 | CP-193091 | 0680 | | B | AT Command for 5G-SRVCC | 16.3.0 | +| 2020-03 | CT#87e | CP-200126 | 0681 | 1 | F | +CGEV amendment to indicate PDP address/type change | 16.4.0 | +| 2020-03 | CT#87e | CP-200110 | 0682 | | F | Correction to AT+CLADN string type | 16.4.0 | +| 2020-03 | CT#87e | CP-200127 | 0683 | 3 | F | Alignment of error codes with 3GPP TS 24.501 | 16.4.0 | +| 2020-03 | CT#87e | CP-200107 | 0684 | 1 | B | Update of Reading coverage enhancement status +CRCES for Connection to 5G Core Network | 16.4.0 | +| 2020-03 | CT#87e | CP-200107 | 0685 | | B | Update of +CNMPSD for NR | 16.4.0 | +| 2020-06 | CT#88e | CP-201100 | 0686 | 1 | F | Unsupported 5QI values | 16.5.0 | +| 2020-06 | CT#88e | CP-201132 | 0687 | 1 | F | New AT command for linking packet filters +CGLNKPF | 16.5.0 | +| 2020-06 | CT#88e | CP-201132 | 0688 | 1 | F | New AT command for deleting packet filters +CGDELCPF | 16.5.0 | +| 2020-06 | CT#88e | CP-201134 | 0690 | 1 | B | Introduction of commands for VAE layer configuration clause | 16.5.0 | +| 2020-06 | CT#88e | CP-201095 | 0693 | | F | Correction to +CNMPSD for NR | 16.5.0 | +| 2020-06 | CT#88e | CP-201351 | 0694 | 2 | B | New AT command supporting for 5G Location Services | 16.5.0 | +| 2020-06 | CT#88e | CP-201353 | 0698 | 1 | A | Removing the ENs for the enhancement to 5G Location Service | 16.5.0 | +| 2020-09 | CT#89e | CP-202158 | 0700 | | F | Add UE requested V2XP message into +CSUEPOLICY | 16.6.0 | +| 2020-09 | CT#89e | CP-202166 | 0701 | 1 | F | Addition of AT commands for exchange of bit rate recommendation and bit rate recommendation queries | 16.6.0 | +| 2020-09 | CT#89e | CP-202166 | 0702 | 1 | F | Scope of +CSUPI | 16.6.0 | +| 2020-09 | CT#89e | CP-202164 | 0703 | 1 | F | Procedure indication for back-off timer | 16.6.0 | +| 2020-12 | CT#90e | CP-203189 | 0691 | 2 | F | Introduction of +CVAECT; AT command for VAE layer activation | 16.7.0 | +| 2020-12 | CT#90e | CP-203189 | 0692 | 2 | F | Introduction of +CVAEREG; AT command for VAE layer | 16.7.0 | + +| | | | | | | | | +|--|--|--|--|--|--|--------------|--| +| | | | | | | registration | | +|--|--|--|--|--|--|--------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | CT#90e | CP-203167 | 0704 | | D | Editorial correction for QoS commands | 16.7.0 | +| 2020-12 | CT#90e | CP-203213 | 0706 | | F | Correction of AT commands for exchange of bit rate recommendation and bit rate recommendation queries | 16.7.0 | +| 2020-12 | CT#90e | CP-203211 | 0708 | 1 | C | Correction on AT CMDs for retry restriction back-off timer under SINE | 16.7.0 | +| 2020-12 | CT#90e | CP-203179 | 0709 | 1 | F | AT command for ATSSS parameters | 16.7.0 | +| 2020-12 | CT#90e | CP-203175 | 0705 | 1 | F | Addition of 5GSM causes #37 and #59 | 17.0.0 | +| 2020-12 | CT#90e | CP-203175 | 0707 | | F | Missing parameter <reporting> in +CEPSFBS | 17.0.0 | +| 2021-03 | CT#91 | CP-210116 | 0710 | 1 | B | Addition of AT commands for PDU Session Context State Change and PDU Session Authentication and Authorization | 17.1.0 | +| 2021-03 | CT#91 | CP-210116 | 0711 | 1 | F | Addition of LADN DNN indication in +CGDCONT | 17.1.0 | +| 2021-03 | CT#91 | CP-210133 | 0712 | | F | Addition of P-CSCF restoration indication in +CGEV | 17.1.0 | +| 2021-03 | CT#91 | CP-210179 | 0713 | 2 | F | AT command for CAG selection | 17.1.0 | +| 2021-03 | CT#91 | CP-210133 | 0714 | | F | Update of C5GQOS for Subscribed maximum bit rate | 17.1.0 | +| 2021-03 | CT#91 | CP-210112 | 0716 | | A | Value range of NW packet filter identifier | 17.1.0 | +| 2021-03 | CT#91 | CP-210133 | 0717 | | F | Correction to the reference of DNN IE | 17.1.0 | +| 2021-03 | CT#91 | CP-210109 | 0719 | 1 | A | AT command for activate an MA PDU session | 17.1.0 | +| 2021-03 | CT#91 | CP-210133 | 0720 | 1 | F | Clarification in scope of "nwimsvops_n3gpp" parameter in +CIREP AT command | 17.1.0 | +| 2021-06 | CT#92e | CP-211129 | 0732 | 1 | A | Correction to AT Commands for NR V2X | 17.2.0 | +| 2021-06 | CT#92e | CP-211144 | 0723 | - | F | Adding the missing Emergency service support over non-3GPP access in CNEM command | 17.2.0 | +| 2021-06 | CT#92e | CP-211144 | 0724 | - | F | Add Ethernet pdp type to a NOTE | 17.2.0 | +| 2021-06 | CT#92e | CP-211144 | 0725 | - | F | Correction on re-attempt indicator for S-NSSAI/DNN congestion control | 17.2.0 | +| 2021-06 | CT#92e | CP-211144 | 0727 | - | F | AT Command to support MA PDU session network upgrade is allowed | 17.2.0 | +| 2021-06 | CT#92e | CP-211146 | 0726 | 1 | F | Clarification on NSSAI related AT commands | 17.2.0 | +| 2021-06 | CT#92e | CP-211146 | 0728 | 1 | F | Correction to +CGLNKPF | 17.2.0 | +| 2021-06 | CT#92e | CP-211152 | 0721 | - | C | New 5QI 10 | 17.2.0 | +| 2021-09 | CT#93e | CP-212154 | 0730 | 3 | F | AT command for URSP | 17.3.0 | +| 2021-09 | CT#93e | CP-212155 | 0736 | 1 | F | Clarifications of preferred access type and access type in AT commands | 17.3.0 | +| 2021-09 | CT#93e | CP-212119 | 0738 | 1 | A | PFI numbering in 27.007 and in 24.008 | 17.3.0 | +| 2021-09 | CT#93e | CP-212140 | 0739 | 1 | F | AT commands with semantical mandatory parameter CID | 17.3.0 | +| 2021-09 | CT#93e | CP-212154 | 0741 | 1 | F | Handling of <S-NSSAI_backoff_time> in +CSBTSR | 17.3.0 | +| 2021-09 | CT#93e | CP-212152 | 0742 | - | F | Editorial corrections of +C5GNSSAIRDP | 17.3.0 | +| 2021-09 | CT#93e | CP-212153 | 0743 | 1 | F | Add the missing unit | 17.3.0 | +| 2021-09 | CT#93e | CP-212126 | 0744 | 1 | F | Add the missing QCI and PTI mismatch | 17.3.0 | +| 2021-09 | CT#93e | CP-212154 | 0745 | 1 | F | +CGCONTRDP amendment to indicate the PDP type | 17.3.0 | +| 2021-09 | CT#93e | CP-212152 | 0746 | - | F | +CGTFT and +CGTFTRDP amendments to support Ethernet PDU session | 17.3.0 | +| 2021-09 | CT#93e | CP-212154 | 0747 | 1 | F | +CGDCONT and +CGCONTRDP amendments to support MTU for Ethernet/ unstructured PDU session | 17.3.0 | +| 2021-12 | CT#94e | CP-213054 | 0749 | 1 | B | +CGDCONT amendment to support redundant PDU session | 17.4.0 | +| 2021-12 | CT#94e | CP-213040 | 0751 | 1 | B | AT Command for MUSIM NAS Connection Release | 17.4.0 | +| 2021-12 | CT#94e | CP-213040 | 0752 | 1 | B | AT Command for MUSIM Reject Paging | 17.4.0 | +| 2021-12 | CT#94e | CP-213040 | 0753 | 1 | B | AT Command for MUSIM Paging Restrictions | 17.4.0 | +| 2021-12 | CT#94e | CP-213030 | 0754 | - | F | Error in +CAPPLEVMR | 17.4.0 | +| 2021-12 | CT#94e | CP-213030 | 0756 | - | F | Correction on AT command +C5GPDUAUTHS | 17.4.0 | +| 2022-03 | CT#95e | CP-220222 | 0765 | - | A | Resolution of editor's note under clause 16.1 | 17.5.0 | +| 2022-03 | CT#95e | CP-220222 | 0769 | - | A | Correction to missing TS reference | 17.5.0 | +| 2022-03 | CT#95e | CP-220223 | 0767 | - | A | Correction to AT command for SL MIMO test for R17 | 17.5.0 | +| 2022-03 | CT#95e | CP-220240 | 0759 | 1 | B | AT Command for MUSIM Paging Timing Collision Control | 17.5.0 | +| 2022-03 | CT#95e | CP-220244 | 0763 | 1 | B | Adding AT commands for ID_UAS | 17.5.0 | +| 2022-03 | CT#95e | CP-220247 | 0762 | - | F | Corrections to brackets in +CGDCONT | 17.5.0 | +| 2022-03 | CT#95e | CP-220248 | 0761 | 1 | F | <5GSM congestion re-attempt indicator> description | 17.5.0 | +| 2022-03 | CT#95e | CP-220248 | 0760 | 1 | F | Incorrect parameter <reporting> in unsolicited result code of +CEPSFBS | 17.5.0 | +| 2022-03 | CT#95e | CP-220252 | 0757 | 1 | B | Adding new AT command for DNS server address reporting | 17.5.0 | +| 2022-03 | CT#95e | CP-220252 | 0758 | 1 | B | Adding new parameter for EDC policy indication | 17.5.0 | +| 2022-03 | CT#95e | CP-220253 | 0770 | - | B | Introduction of AT commands for UAE layer configuration clause | 17.5.0 | +| 2022-03 | CT#95e | CP-220260 | 0771 | 1 | F | AT command updation for MINT in manual selection mode. | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------|--------| +| 2022-03 | CT#95e | CP-220264 | 0772 | - | B | AT command for QoE measurement in NR | 17.5.0 | +| 2022-06 | CT#96 | CP-221195 | 0775 | - | A | Removal of remaining Editor's Notes for WI 5GS_Ph1 | 17.6.0 | +| 2022-06 | CT#96 | CP-221211 | 0778 | - | F | Correction on AT command +C5GPDUAUTHS | 17.6.0 | +| 2022-06 | CT#96 | CP-221212 | 0779 | 1 | F | Correction on AT command +C5GURSPQRY | 17.6.0 | +| 2022-06 | CT#96 | CP-221213 | 0776 | 1 | B | 5GSM congestion re-attempt indicator with ABO bit and CATBO bit | 17.6.0 | +| 2022-06 | CT#96 | CP-221223 | 0781 | 1 | B | Support of RV QoE | 17.6.0 | +| 2022-06 | CT#96 | CP-221223 | 0782 | 1 | B | AT Command for MO SMS access domain preference selection | 17.6.0 | +| 2022-09 | CT#97e | CP-222145 | 0785 | 1 | B | Add command for EAP message for relay authentication | 17.7.0 | +| 2022-09 | CT#97e | CP-222148 | 0788 | 1 | B | AT Command for ECS Address Provisioning | 17.7.0 | +| 2022-09 | CT#97e | CP-222147 | 0789 | 1 | C | New 5QI values to support Advance Interactive Services (AIS) in 5G | 17.7.0 | +| 2022-09 | CT#97e | CP-222169 | 0786 | - | F | Clarify that +CASIMS is applicable to NG-RAN | 18.0.0 | +| 2022-09 | CT#97e | CP-222169 | 0787 | 1 | C | Addition of DN authentication in +CGAUTH | 18.0.0 | +| 2022-09 | CT#97e | CP-222169 | 0790 | 1 | F | AT command for 5GS network registration over non-3GPP access | 18.0.0 | +| 2022-09 | CT#97e | CP-222169 | 0791 | 1 | F | AT command for 5GS network registration status over non-3GPP access | 18.0.0 | +| 2022-12 | CT#98e | CP-223157 | 0792 | 1 | F | Updation to AT command to include CAG only information | 18.1.0 | +| 2022-12 | CT#98e | CP-223143 | 0794 | 1 | A | Corrections to NR QoE AT commands | 18.1.0 | +| 2022-12 | CT#98e | CP-223157 | 0795 | 1 | F | Sync the meaning of direction in CGTFT based on 24.501 | 18.1.0 | +| 2022-12 | CT#98e | CP-223129 | 0797 | 3 | A | New QCI 10 for QoS control for satellite access – Cat A | 18.1.0 | +| 2022-12 | CT#98e | CP-223144 | 0799 | 1 | B | AT commands for defining and reading MBS sessions | 18.1.0 | +| 2022-12 | CT#98e | CP-223144 | 0801 | 1 | B | AT command for MBS session status reporting | 18.1.0 | +| 2023-03 | CT#99 | CP-230250 | 0803 | 2 | B | AT Command for Unavailability Period | 18.2.0 | +| 2023-03 | CT#99 | CP-230220 | 0806 | 1 | C | Add code points for satellite E-UTRAN RATs | 18.2.0 | +| 2023-03 | CT#99 | CP-230220 | 0807 | 1 | C | Add code point for satellite satellite NG-RAN RATs | 18.2.0 | +| 2023-06 | CT#100 | CP-231232 | 0809 | - | F | Correction on 5GS TAI list reference | 18.3.0 | +| 2023-06 | CT#100 | CP-231217 | 0810 | - | F | Corrections to +CMSRDP | 18.3.0 | +| 2023-06 | CT#100 | CP-231217 | 0813 | - | F | Updation to the note on conditions for requested NSSAI | 18.3.0 | +| 2023-06 | CT#100 | CP-231233 | 0814 | - | F | Adding missing reference for TS 33.246 | 18.3.0 | +| 2023-06 | CT#100 | CP-231217 | 0802 | 3 | B | Providing information for derived QoS for ESP packets | 18.3.0 | +| 2023-06 | CT#100 | CP-231232 | 0816 | - | F | Implementation error in clause 8.85 | 18.3.0 | +| 2023-06 | CT#100 | CP-231245 | 0808 | 2 | B | AT command update for LADN per DNN & S-NSSAI | 18.3.0 | +| 2023-06 | CT#100 | CP-231232 | 0817 | - | F | Correction to +CGAUTH | 18.3.0 | +| 2023-06 | CT#100 | CP-231257 | 0819 | 1 | A | Adding missing part of the agreed CR 771 | 18.3.0 | +| 2023-06 | CT#100 | CP-231271 | 0821 | 1 | F | AT command correction for unavailability period | 18.3.0 | +| 2023-06 | CT#100 | CP-231225 | 0815 | 1 | F | Corrections to 5G and satellite RATs | 18.3.0 | +| 2023-06 | CT#100 | CP-231233 | 0820 | 1 | F | Adding QFI to +CAPPLEVMRNR | 18.3.0 | +| 2023-09 | CT#101 | CP-232195 | 0826 | - | F | Updates to +C5GNSSAIRDP for partially allowed NSSAI | 18.4.0 | +| 2023-09 | CT#101 | CP-232195 | 0827 | - | F | New AT command +CCKEYREQ to request for the ciphering keys | 18.4.0 | +| 2023-09 | CT#101 | CP-232203 | 0824 | 1 | B | AT commands for EDGE-5 API | 18.4.0 | +| 2023-09 | CT#101 | CP-232198 | 0822 | 1 | B | New AT-command CDISCO for discontinuous coverage | 18.4.0 | +| 2023-09 | CT#101 | CP-232195 | 0825 | 1 | F | Updates to 5GS network registration status +C5GREG for disaster condition | 18.4.0 | +| 2023-12 | CT#102 | CP-233189 | 0829 | - | F | Informative examples in Clause 8 needs to be shifted | 18.5.0 | +| 2023-12 | CT#102 | CP-233152 | 0830 | - | B | AT command for EDGE-5 AC registration | 18.5.0 | +| 2023-12 | CT#102 | CP-233180 | 0831 | - | B | AT command for N3QAI | 18.5.0 | +| 2023-12 | CT#102 | CP-233189 | 0832 | - | F | Updates to +CGDCONT for EDC and SDNAEPC support indicator | 18.5.0 | +| 2023-12 | CT#102 | CP-233189 | 0837 | - | F | Correction on AT command +C5GPDUAUTHR and +C5GPU2NRAUTHR | 18.5.0 | +| 2023-12 | CT#102 | CP-233163 | 0840 | 1 | A | Extended rejected NSSAI IE in +C5GNSSAIRDP command | 18.5.0 | +| 2023-12 | CT#102 | CP-233145 | 0828 | 1 | C | Updates to the +CUNPER command | 18.5.0 | +| 2023-12 | CT#102 | CP-233184 | 0823 | 3 | B | AT command for Signal level enhanced network selection | 18.5.0 | +| 2023-12 | CT#102 | CP-233180 | 0841 | - | F | AT command for non-3GPP delay budget | 18.5.0 | +| 2023-12 | CT#102 | CP-233150 | 0842 | - | F | Correction to +C5GURSPQRY command | 18.5.0 | +| 2023-12 | CT#102 | CP-233142 | 0844 | - | F | Correction to CMSSR command | 18.5.0 | +| 2023-12 | CT#102 | CP-233189 | 0846 | 1 | F | Updates to +CMICO AT Command | 18.5.0 | +| 2023-12 | CT#102 | CP-233145 | 0845 | 1 | B | Out of coverage duration for +CDISCO | 18.5.0 | +| 2023-12 | CT#102 | CP-233189 | 0847 | 1 | F | Correction on the reference to TS 23.122 | 18.5.0 | \ No newline at end of file diff --git a/raw/rel-18/29_series/29116/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29116/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c08222255fc313aa621eb86964b5a8b302367f0 --- /dev/null +++ b/raw/rel-18/29_series/29116/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d29bb9cb25f3e232fa3e588a1471970fc3086d500f80c4717863da395e8f4ab1 +size 9523 diff --git a/raw/rel-18/29_series/29116/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29116/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d083aa81a530792b5d20885b08a2dd2b083db08 --- /dev/null +++ b/raw/rel-18/29_series/29116/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f08762bf0827e8ca4fb9d42ff43418403e164494f201ea57dfdc023c239bdf4 +size 5695 diff --git a/raw/rel-18/29_series/29116/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/raw/rel-18/29_series/29116/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a872e0f2d150c916db0ebaf5772cd4df2a10d1b8 --- /dev/null +++ b/raw/rel-18/29_series/29116/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e28f9e2243d4b8a2361c6044c3019b870253d615cb28593639078bfc0b6bee76 +size 234785 diff --git a/raw/rel-18/29_series/29116/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/raw/rel-18/29_series/29116/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acb235a6ea0a67fb88753ba87225e49909de7f13 --- /dev/null +++ b/raw/rel-18/29_series/29116/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:634fc14160e11bee80044e990ee66c782a12dc31a1c03c5a5e7f04fe55438e27 +size 231873 diff --git a/raw/rel-18/29_series/29116/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/raw/rel-18/29_series/29116/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ff58872d05d25860db039a1eb121a0c14a033d --- /dev/null +++ b/raw/rel-18/29_series/29116/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85eca5fc9079694ab7c6516a86810b1eb0d0d1819e5f366b0189c1c16ca02757 +size 9472 diff --git a/raw/rel-18/29_series/29118/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29118/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9272c47258e76b7478ae2f4b61e4b2c445ac4b7a --- /dev/null +++ b/raw/rel-18/29_series/29118/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:131e795bd678cdb9ad94676f87eb4cd98ce2988fe2261137572a0ff08d214645 +size 7693 diff --git a/raw/rel-18/29_series/29118/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29118/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f956ffbb4636b6cf33af6be3a9d4a8844059c92c --- /dev/null +++ b/raw/rel-18/29_series/29118/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0605e8a39943ff3f3c159fd8ebc3b5f9d828486d1ae2c9733eb6780343d6a39f +size 5782 diff --git a/raw/rel-18/29_series/29118/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/29_series/29118/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb8412f64627cd2f6b535fe42f97799482549c7b --- /dev/null +++ b/raw/rel-18/29_series/29118/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f24067d5ccd1be328b9a1f4c1c73baa9b567777d4bc00a3aa74df8637cdc83 +size 88301 diff --git a/raw/rel-18/29_series/29118/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/raw/rel-18/29_series/29118/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17912cc18238014c6ad7f2a6699951125446b85f --- /dev/null +++ b/raw/rel-18/29_series/29118/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85dcaa75cd3b83e9471cdf9cebd72e73a29569223d0bd347c191c431e61011ce +size 85767 diff --git a/raw/rel-18/29_series/29128/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29128/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0384b52849c0b8bdf9ab09c34bbac6c933420758 --- /dev/null +++ b/raw/rel-18/29_series/29128/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/29_series/29128/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29128/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..474088002f241fff2759ad877d40cef5e0d85323 --- /dev/null +++ b/raw/rel-18/29_series/29128/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/29_series/29128/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/raw/rel-18/29_series/29128/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ea068e25b985c83114c634e1842185bc6e5ede1 --- /dev/null +++ b/raw/rel-18/29_series/29128/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2a4fcf24677742f82a6785062f643e3dc2d8a73ff8ef6a517df01d1a610d72b +size 35827 diff --git a/raw/rel-18/29_series/29172/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29172/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98fed0257178e13c792dc02dadc5d9a8c4c9e41 --- /dev/null +++ b/raw/rel-18/29_series/29172/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd44a49898b2672ddf3a02e6a6e3990fb0e752f00555f3cfe6b668d62ca3e53f +size 6336 diff --git a/raw/rel-18/29_series/29172/99bae07626f60f9ede10e2e387ef7051_img.jpg b/raw/rel-18/29_series/29172/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b29fa08c8e3d52c4a3f1645d3e3ca5971948ba91 --- /dev/null +++ b/raw/rel-18/29_series/29172/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db1298b148677587c132c64f8e3187076b04ff4e5355794340b840dc1437b362 +size 26389 diff --git a/raw/rel-18/29_series/29244/06faefab7f20d05bf410e9a250268f64_img.jpg b/raw/rel-18/29_series/29244/06faefab7f20d05bf410e9a250268f64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdccefc0dc73ee7a1388752d88ea8560fabc9298 --- /dev/null +++ b/raw/rel-18/29_series/29244/06faefab7f20d05bf410e9a250268f64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6309df354f15379e58a6ee98d8a91be3e6420e18e487e63c206d25eb6efc128e +size 18624 diff --git a/raw/rel-18/29_series/29244/09dfc56e36400ce30e66f21f777a4ad6_img.jpg b/raw/rel-18/29_series/29244/09dfc56e36400ce30e66f21f777a4ad6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d92bfaf67aca78b769a5162c94edbbb90038699d --- /dev/null +++ b/raw/rel-18/29_series/29244/09dfc56e36400ce30e66f21f777a4ad6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1801b2e93415960b43e2894ba217bd61c7a84c56dc07401b631696a805904c45 +size 33899 diff --git a/raw/rel-18/29_series/29244/0cfa8dfcebbb1e09ba4e0353ad037192_img.jpg b/raw/rel-18/29_series/29244/0cfa8dfcebbb1e09ba4e0353ad037192_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84659b9a20b55f6c667c067aa85e41be62025bee --- /dev/null +++ b/raw/rel-18/29_series/29244/0cfa8dfcebbb1e09ba4e0353ad037192_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db451df0ac1488a1246cf700675335cb119f9cb2737c29779949070d2c0e42d9 +size 17562 diff --git a/raw/rel-18/29_series/29244/1240ac770bfb4a7805029c473fdaadd6_img.jpg b/raw/rel-18/29_series/29244/1240ac770bfb4a7805029c473fdaadd6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd64ac9424b1f63556a957a4e8453054e0b99b7c --- /dev/null +++ b/raw/rel-18/29_series/29244/1240ac770bfb4a7805029c473fdaadd6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f31b60eecb17e7b09b02db5ea625250a4a8226a989f5eda52281e69a54c88a3d +size 28220 diff --git a/raw/rel-18/29_series/29244/15142e678003c56ade1fe2a4f3f5a7a2_img.jpg b/raw/rel-18/29_series/29244/15142e678003c56ade1fe2a4f3f5a7a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2bbcfd3f5167f241e87e2ffe5dd1135cecccd75 --- /dev/null +++ b/raw/rel-18/29_series/29244/15142e678003c56ade1fe2a4f3f5a7a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:004f87224a72ed1f51304a674184c9f8bf35d45aa36a8f3a96483d58c2d6dee5 +size 26966 diff --git a/raw/rel-18/29_series/29244/15d5c901284409186049549eec95c4a4_img.jpg b/raw/rel-18/29_series/29244/15d5c901284409186049549eec95c4a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..228e1557fe7a1cadaa15731b7289dc35e73f4296 --- /dev/null +++ b/raw/rel-18/29_series/29244/15d5c901284409186049549eec95c4a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97d9d287ec5c5cff66a8a626099d3f43788e12524372cb768160713d66774d55 +size 19325 diff --git a/raw/rel-18/29_series/29244/1ba9045eb6dc22039a16b92b1427e696_img.jpg b/raw/rel-18/29_series/29244/1ba9045eb6dc22039a16b92b1427e696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32be4bdb0f0d97aa495946acf7cc042bcf064bb7 --- /dev/null +++ b/raw/rel-18/29_series/29244/1ba9045eb6dc22039a16b92b1427e696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e5c33b86d7ab02c8a48c3a0ec712558cb1e483ac8a514e7c098a60469a87059 +size 29916 diff --git a/raw/rel-18/29_series/29244/2686cc35669b140d74b134b0c673adf8_img.jpg b/raw/rel-18/29_series/29244/2686cc35669b140d74b134b0c673adf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..776f3b0a35da6c5a7eba265e0f8ec6032627a063 --- /dev/null +++ b/raw/rel-18/29_series/29244/2686cc35669b140d74b134b0c673adf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2a2962aacc3671420b766f079a0bb772c3ee194f23854e5f517e440dd29942f +size 19588 diff --git a/raw/rel-18/29_series/29244/37a7503d01fdb9775036d415ccf102d1_img.jpg b/raw/rel-18/29_series/29244/37a7503d01fdb9775036d415ccf102d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf733cf739f74c48d995ea483a95c664037f6638 --- /dev/null +++ b/raw/rel-18/29_series/29244/37a7503d01fdb9775036d415ccf102d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62d03bfec9401df1c46d6aedf8416fb37a56f6586e44915052c95655ed201920 +size 230871 diff --git a/raw/rel-18/29_series/29244/39e4a7d7b06791117dcacd19cedb400b_img.jpg b/raw/rel-18/29_series/29244/39e4a7d7b06791117dcacd19cedb400b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ac720374c5ca3ad0659dc260c52aca6f734825b --- /dev/null +++ b/raw/rel-18/29_series/29244/39e4a7d7b06791117dcacd19cedb400b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0b651bc843bd150b3303be2b67243efe4a7f16405226b707188e75712fc0dd1 +size 85066 diff --git a/raw/rel-18/29_series/29244/402dbdc2f0620d095c93e21d5296ae99_img.jpg b/raw/rel-18/29_series/29244/402dbdc2f0620d095c93e21d5296ae99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc62297da6ba66a726fd0c0641d80a424e6b924e --- /dev/null +++ b/raw/rel-18/29_series/29244/402dbdc2f0620d095c93e21d5296ae99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d258fbdf13f85fb0d5850fa110f33c46524601ddadb6613bd9dedfe487dc0370 +size 33206 diff --git a/raw/rel-18/29_series/29244/40602f4e56e7323850ca7d63082cb4ad_img.jpg b/raw/rel-18/29_series/29244/40602f4e56e7323850ca7d63082cb4ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e9e130c73da75832a108aedec5bc5e3c65e489 --- /dev/null +++ b/raw/rel-18/29_series/29244/40602f4e56e7323850ca7d63082cb4ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cced95aa963bf9467516a4a08ea5453fb5d53dd57ee8ed1f22ff2c08197418f2 +size 35570 diff --git a/raw/rel-18/29_series/29244/4753dd817f88f9e8bc58fcce3df36ea6_img.jpg b/raw/rel-18/29_series/29244/4753dd817f88f9e8bc58fcce3df36ea6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..213bd1653dbeaa83d0a1eb8838f80445102dd501 --- /dev/null +++ b/raw/rel-18/29_series/29244/4753dd817f88f9e8bc58fcce3df36ea6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b962f755363869c2d28cb1d0d4d39e6efbd0246b431afe9d4ed3f27d1ecd88cf +size 109941 diff --git a/raw/rel-18/29_series/29244/49940b22f9b199244563fe83653b1bac_img.jpg b/raw/rel-18/29_series/29244/49940b22f9b199244563fe83653b1bac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53f057590259d5c90161fed80d28c119b2d1b079 --- /dev/null +++ b/raw/rel-18/29_series/29244/49940b22f9b199244563fe83653b1bac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58cdc91007ee8e780c590f7db208c39c5fea1e0d3bc1dfba473d631ce8abc3b9 +size 26683 diff --git a/raw/rel-18/29_series/29244/5952630aecd107d61c526cda06d3a723_img.jpg b/raw/rel-18/29_series/29244/5952630aecd107d61c526cda06d3a723_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9354be1d4548a9974bbea533fbbe7cce8049ca1c --- /dev/null +++ b/raw/rel-18/29_series/29244/5952630aecd107d61c526cda06d3a723_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58717e6b9afa89579ff2e8031a89ef75fcc317271d7b4069c9f0ca7cc0cbbd26 +size 31277 diff --git a/raw/rel-18/29_series/29244/5a6c0922072257806a1985a761f2abd6_img.jpg b/raw/rel-18/29_series/29244/5a6c0922072257806a1985a761f2abd6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4882fe5e8c9ae1bbc9e51f91fcf0f810fde53c9 --- /dev/null +++ b/raw/rel-18/29_series/29244/5a6c0922072257806a1985a761f2abd6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73a9d2b2230272433cdd1594055555f431690da8ee6131f4597f8c20183b38b2 +size 20961 diff --git a/raw/rel-18/29_series/29244/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29244/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c84717fc9832f1402fb25d8ad4596d56fde3d762 --- /dev/null +++ b/raw/rel-18/29_series/29244/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a048f1057cc19897dc4bb0fc6647da7fcafaa774d5e2a63a411c1d20b05096 +size 9544 diff --git a/raw/rel-18/29_series/29244/642182b1c4431ad5fb0e911fcb892d08_img.jpg b/raw/rel-18/29_series/29244/642182b1c4431ad5fb0e911fcb892d08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2757f251130ddc66487b8422bc41626d40725f0 --- /dev/null +++ b/raw/rel-18/29_series/29244/642182b1c4431ad5fb0e911fcb892d08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c3b0b7df02cb342883dac9f10f902659b0737c604f7af7cd324839926402caa +size 100040 diff --git a/raw/rel-18/29_series/29244/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29244/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11028fd328e1a961c129fc415779c7f574aacd44 --- /dev/null +++ b/raw/rel-18/29_series/29244/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd948258da9aac809a209fb8641323ce539218b125ddb5f38eedd4f4fef3d8af +size 5554 diff --git a/raw/rel-18/29_series/29244/6d1910bc8db5fd0b035d17f7d15eed1a_img.jpg b/raw/rel-18/29_series/29244/6d1910bc8db5fd0b035d17f7d15eed1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7e73028cedf017e56cc92de339c53d0d21b586f --- /dev/null +++ b/raw/rel-18/29_series/29244/6d1910bc8db5fd0b035d17f7d15eed1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e8136ce434c65c8bcac605756a57b68ca6aabcf01f0e24b437c5293b46f2b62 +size 20166 diff --git a/raw/rel-18/29_series/29244/72b43e2f42ffc000f9f9b21bff9b6191_img.jpg b/raw/rel-18/29_series/29244/72b43e2f42ffc000f9f9b21bff9b6191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f1b7e0e9345022bdcf5cfc15b3c737d33b5305e --- /dev/null +++ b/raw/rel-18/29_series/29244/72b43e2f42ffc000f9f9b21bff9b6191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4751eda62d6d01ab4a622ba7c2640d4e9514a66852df196b8c41ec237c5a83f +size 30796 diff --git a/raw/rel-18/29_series/29244/761efbc82a397a77e5e4a0afc95a3d44_img.jpg b/raw/rel-18/29_series/29244/761efbc82a397a77e5e4a0afc95a3d44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da2f51a0c6173ae47847b4026eddc775a44ffd46 --- /dev/null +++ b/raw/rel-18/29_series/29244/761efbc82a397a77e5e4a0afc95a3d44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69ba62270cec6290daea7f26330c1ac0689f719f15e31783317b9c6e98281b0f +size 56745 diff --git a/raw/rel-18/29_series/29244/82645d0210baf1751f9ed2a4d3a9e5d7_img.jpg b/raw/rel-18/29_series/29244/82645d0210baf1751f9ed2a4d3a9e5d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcc6d6e20ba60c9b15ef58e47027924a64e5fc8b --- /dev/null +++ b/raw/rel-18/29_series/29244/82645d0210baf1751f9ed2a4d3a9e5d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6626cf099425209638c391ee0219f49ca8c35f412c07f4528adace5cf6db2698 +size 26986 diff --git a/raw/rel-18/29_series/29244/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/raw/rel-18/29_series/29244/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5deff2f42d01588ee06b3be2ed1f058716e8893a --- /dev/null +++ b/raw/rel-18/29_series/29244/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e2bd6aac66f91cd278961f57c2c73c5574ea9ba5ca4f8e8b0d343294a6ec214 +size 43440 diff --git a/raw/rel-18/29_series/29244/8b6f7b51bc160aa80e286e818baa7998_img.jpg b/raw/rel-18/29_series/29244/8b6f7b51bc160aa80e286e818baa7998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab74c0542478c518ca4739ca66faf075fc3dabb8 --- /dev/null +++ b/raw/rel-18/29_series/29244/8b6f7b51bc160aa80e286e818baa7998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3fe4e11d1003133ec7938afa3231c6e21708e93df3d982f3d4d3dd363a19d67 +size 61387 diff --git a/raw/rel-18/29_series/29244/91a2fec5de093d2a9bc345ff56794fa4_img.jpg b/raw/rel-18/29_series/29244/91a2fec5de093d2a9bc345ff56794fa4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c8d8117662f704bdf1f4fc38b05053846d8feee --- /dev/null +++ b/raw/rel-18/29_series/29244/91a2fec5de093d2a9bc345ff56794fa4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30fc9cb25c8803dab578b884799459e08d4060d398f7924e7e04bbce9fd7be45 +size 32780 diff --git a/raw/rel-18/29_series/29244/94fd137860c16c8dfd75512f10161fe8_img.jpg b/raw/rel-18/29_series/29244/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d173882f7f85c5d5ae0a60ac162fdb6b918271f7 --- /dev/null +++ b/raw/rel-18/29_series/29244/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7964f718410d6b9a01d4112dffe9c490226e33ceb2809826f00c2deb8264cea +size 6249 diff --git a/raw/rel-18/29_series/29244/9a76d0bd12a2f17f110914f18fa7ceac_img.jpg b/raw/rel-18/29_series/29244/9a76d0bd12a2f17f110914f18fa7ceac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a3d01a491839f417959c4c45254a3d1441cd4a7 --- /dev/null +++ b/raw/rel-18/29_series/29244/9a76d0bd12a2f17f110914f18fa7ceac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:748edc22012d3f222f046f733e0593290b1085d26a6d686871854c50bfd1d510 +size 17624 diff --git a/raw/rel-18/29_series/29244/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/29_series/29244/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7edbc8c09465b8133c3327846c52048531985dd --- /dev/null +++ b/raw/rel-18/29_series/29244/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a77261a31e20897377e5cbe84b3c52a7155a2d8db91725642c1fc6410fc0e0 +size 71633 diff --git a/raw/rel-18/29_series/29244/9e2b890eb1af21240ec68d210241d0d5_img.jpg b/raw/rel-18/29_series/29244/9e2b890eb1af21240ec68d210241d0d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7afc3ff7cbccc6a6b1487ff515b26c869d66619d --- /dev/null +++ b/raw/rel-18/29_series/29244/9e2b890eb1af21240ec68d210241d0d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b26b63fc3d2cb2fffcccd69d06209ee7a58aab08bbe76407a9b1077cd036bf67 +size 16717 diff --git a/raw/rel-18/29_series/29244/9fc763d186fb9af5895be87e5cf29c76_img.jpg b/raw/rel-18/29_series/29244/9fc763d186fb9af5895be87e5cf29c76_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6e7fcd8d500552fd759dc0cb400975e93d141ca --- /dev/null +++ b/raw/rel-18/29_series/29244/9fc763d186fb9af5895be87e5cf29c76_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5836e98fee323ed0c07f11a3e7b287b448e7a89ebaa6d22f43ab36ad3b6c9763 +size 25372 diff --git a/raw/rel-18/29_series/29244/a1fad9ca0c696e710c9a7ae5622401e4_img.jpg b/raw/rel-18/29_series/29244/a1fad9ca0c696e710c9a7ae5622401e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ecb190767453c59f495ea21e3723f03ffed8617 --- /dev/null +++ b/raw/rel-18/29_series/29244/a1fad9ca0c696e710c9a7ae5622401e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:983b861c3fe32604a214d9f3cae7191feef8b9485e05f31804f4c2134be1ea5e +size 6051 diff --git a/raw/rel-18/29_series/29244/a2d2099bcb354ddc581de00483177038_img.jpg b/raw/rel-18/29_series/29244/a2d2099bcb354ddc581de00483177038_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eb0281fd7216347fa869b05fa430d427236d87b --- /dev/null +++ b/raw/rel-18/29_series/29244/a2d2099bcb354ddc581de00483177038_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:187d5946042e31f88c15b076a118f60f24c66709b332f9990b5aa711586777ce +size 103996 diff --git a/raw/rel-18/29_series/29244/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/29_series/29244/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9a68d0c1c2d98b14883ae37337505440dd04d89 --- /dev/null +++ b/raw/rel-18/29_series/29244/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:550a840fccf55c99012ee1e27e58f28998c557d474ab0191321112f7abc4fc2d +size 40493 diff --git a/raw/rel-18/29_series/29244/b64babfa113eff6e42e921574eea285e_img.jpg b/raw/rel-18/29_series/29244/b64babfa113eff6e42e921574eea285e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0352a2d1a47adf8d9ce0db1c97ff60ff07753f13 --- /dev/null +++ b/raw/rel-18/29_series/29244/b64babfa113eff6e42e921574eea285e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee5a1f09501db5157265518c5249b30dc9957f6cac427d1b58a6527497652526 +size 29371 diff --git a/raw/rel-18/29_series/29244/c2c14da2db540fd84f355e71c9085b4a_img.jpg b/raw/rel-18/29_series/29244/c2c14da2db540fd84f355e71c9085b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eec425709d3cfe5a138c908e41de56223fc39265 --- /dev/null +++ b/raw/rel-18/29_series/29244/c2c14da2db540fd84f355e71c9085b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e7b4f7572684d8448e8640b3f4af893ac270302451e0427c763c713a9168d53 +size 29915 diff --git a/raw/rel-18/29_series/29244/c84f48e1ab022f08a2b2bfd914dbe9bb_img.jpg b/raw/rel-18/29_series/29244/c84f48e1ab022f08a2b2bfd914dbe9bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04320b29b685d8765e264c5308e22c131f9d5e1e --- /dev/null +++ b/raw/rel-18/29_series/29244/c84f48e1ab022f08a2b2bfd914dbe9bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e64794556c83b016e5bb9341f7a68b8e17d833ff36203299e3ba338cfef3255e +size 18952 diff --git a/raw/rel-18/29_series/29244/d0c2ae6a2b305d2b68d836fac2cb5726_img.jpg b/raw/rel-18/29_series/29244/d0c2ae6a2b305d2b68d836fac2cb5726_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9209eaddde2b1781181ec1d1db93e943007bd2e --- /dev/null +++ b/raw/rel-18/29_series/29244/d0c2ae6a2b305d2b68d836fac2cb5726_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93dc23b801edb3bf69ea19b0b9513f9f914e63d43dc8be13fd2e8d52c5073485 +size 35999 diff --git a/raw/rel-18/29_series/29244/d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg b/raw/rel-18/29_series/29244/d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea36c25f8ddf5b3933734a822d5b8682c70e723d --- /dev/null +++ b/raw/rel-18/29_series/29244/d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:102b11e2a344b81c2dd476a23713bfae8906f58e1f0f589a711295b58224e24a +size 45544 diff --git a/raw/rel-18/29_series/29244/d39bf9db880dcbdd181b1ef80491d21c_img.jpg b/raw/rel-18/29_series/29244/d39bf9db880dcbdd181b1ef80491d21c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b6a19670509614dd8e8dd855efa170dbbb71d68 --- /dev/null +++ b/raw/rel-18/29_series/29244/d39bf9db880dcbdd181b1ef80491d21c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:238191ed522d39e58284dc655881896196eb036e163d58531309d2957456c1a2 +size 7597 diff --git a/raw/rel-18/29_series/29244/d74d903882c523e543dea290b1033e48_img.jpg b/raw/rel-18/29_series/29244/d74d903882c523e543dea290b1033e48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..630acf3a8f63c26e6ebb809f1bd8929a148e2a5d --- /dev/null +++ b/raw/rel-18/29_series/29244/d74d903882c523e543dea290b1033e48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd4a1119a0bb14cfc8844874794282aba777878d24ce97dcba0baa69622cbf51 +size 27641 diff --git a/raw/rel-18/29_series/29244/d857a816663b2bb31fd8fe42b2016004_img.jpg b/raw/rel-18/29_series/29244/d857a816663b2bb31fd8fe42b2016004_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e485099caeafb9c259d75926ed0ea00df0f6c96 --- /dev/null +++ b/raw/rel-18/29_series/29244/d857a816663b2bb31fd8fe42b2016004_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edc4d78ace569e4c6004c124bdfafdb7625eb9062f420274d72ee13148453e77 +size 68219 diff --git a/raw/rel-18/29_series/29244/e05b36c0d46549e681ce6581422c66b2_img.jpg b/raw/rel-18/29_series/29244/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61287308482f7e2b81bfa47f70ab0411dcb2f2ef --- /dev/null +++ b/raw/rel-18/29_series/29244/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f679466316ba46b977496f5e5a7868a9dd82148b07635b1708e24dc27d71c3d1 +size 12975 diff --git a/raw/rel-18/29_series/29244/e896e0bdda91f258fa9ce577d1264465_img.jpg b/raw/rel-18/29_series/29244/e896e0bdda91f258fa9ce577d1264465_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c65db5197d9e8e3cf34855d22ec7e387795ab432 --- /dev/null +++ b/raw/rel-18/29_series/29244/e896e0bdda91f258fa9ce577d1264465_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0d5a0356b11bcf3d484659bb36009cbd2ae651aab0b17b3f16d32e10c5d4984 +size 32758 diff --git a/raw/rel-18/29_series/29244/e8fb82f1c4527079e81cd9c572eb1602_img.jpg b/raw/rel-18/29_series/29244/e8fb82f1c4527079e81cd9c572eb1602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb9239261717814c1e5e173d66bf31e2f466c7bd --- /dev/null +++ b/raw/rel-18/29_series/29244/e8fb82f1c4527079e81cd9c572eb1602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1c744a3f4aafece5c60e9d96a9bffb9bdecf5f692b89f24870bf698ad2c9d3c +size 28761 diff --git a/raw/rel-18/29_series/29244/e914e488b454719738e15f6273374f85_img.jpg b/raw/rel-18/29_series/29244/e914e488b454719738e15f6273374f85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b2bb4ab51dd32c8bec19e5ab72962779aec5cb5 --- /dev/null +++ b/raw/rel-18/29_series/29244/e914e488b454719738e15f6273374f85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17551d1e55fcbcf7655abd490717577417c33f3925945b032c4e86bf194a650 +size 29708 diff --git a/raw/rel-18/29_series/29244/e97277b95d25bb9cfe8581800948ddeb_img.jpg b/raw/rel-18/29_series/29244/e97277b95d25bb9cfe8581800948ddeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13c0bd5d71bf7abd2b0e020e0ad7006a7450becd --- /dev/null +++ b/raw/rel-18/29_series/29244/e97277b95d25bb9cfe8581800948ddeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58a0a5b51cdedf1c57ffd452efcd8ea5d1e4491634a8ad858e352269d5e34816 +size 38595 diff --git a/raw/rel-18/29_series/29244/ec16d4b5fcf05287a18d5a155bf7e8d7_img.jpg b/raw/rel-18/29_series/29244/ec16d4b5fcf05287a18d5a155bf7e8d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79b423cdf6173f23606a446900273b69310c7f12 --- /dev/null +++ b/raw/rel-18/29_series/29244/ec16d4b5fcf05287a18d5a155bf7e8d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa5f59d6410010df82b6cd2d3927edc5ff49e3247410dc1c1c697bc6370afe73 +size 144739 diff --git a/raw/rel-18/29_series/29244/f06e043693c439659f060fba960881ea_img.jpg b/raw/rel-18/29_series/29244/f06e043693c439659f060fba960881ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2692c831ee9c96a1d634a32c273b37493a4d18d6 --- /dev/null +++ b/raw/rel-18/29_series/29244/f06e043693c439659f060fba960881ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c5ed28dc7477eb8d22400236ec11726ae049f9ebc002c6cbe66e0c343b99708 +size 150653 diff --git a/raw/rel-18/29_series/29244/f482942742e47fc04606f7a4a4c2f1d9_img.jpg b/raw/rel-18/29_series/29244/f482942742e47fc04606f7a4a4c2f1d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3d428e8fdcbcc5279937424fe8c1f9913ef522a --- /dev/null +++ b/raw/rel-18/29_series/29244/f482942742e47fc04606f7a4a4c2f1d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:751c0e86f1c2fdc456865a31a3159ce9c94f2209081ee10e73c5f26b2da43750 +size 25016 diff --git a/raw/rel-18/29_series/29244/f62ba37363dd9dcfdaeea93164bc21b9_img.jpg b/raw/rel-18/29_series/29244/f62ba37363dd9dcfdaeea93164bc21b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6322f315deaa34bbc82ab6a3f0bfa5e5c7c0510a --- /dev/null +++ b/raw/rel-18/29_series/29244/f62ba37363dd9dcfdaeea93164bc21b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dba316415b3a417176aada31c2682497df10b23c489ea507b7530a1a3ef3bc22 +size 27418 diff --git a/raw/rel-18/29_series/29244/fb085ecd97845ca0c4cdbdea1ed28196_img.jpg b/raw/rel-18/29_series/29244/fb085ecd97845ca0c4cdbdea1ed28196_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..954fb35c819db0bea99dbb61d6f6c8f154194f57 --- /dev/null +++ b/raw/rel-18/29_series/29244/fb085ecd97845ca0c4cdbdea1ed28196_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:258ad159879a7113d4a57c7f64f404f7e4cdb475240952a4213b8d84f70e9f13 +size 33524 diff --git a/raw/rel-18/29_series/29244/fda8b5cd85f7ff5e4a29dd0dbee1279d_img.jpg b/raw/rel-18/29_series/29244/fda8b5cd85f7ff5e4a29dd0dbee1279d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c4a6a877c0fb0288d720ffd143284d79cf907af --- /dev/null +++ b/raw/rel-18/29_series/29244/fda8b5cd85f7ff5e4a29dd0dbee1279d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00ee22e536b3d65bff6ce1a49371521c89cec4a33ec72a5528260ab3b2a7ff8 +size 30031 diff --git a/raw/rel-18/29_series/29256/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29256/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40a9c22e02bb4a71ffb514941e7262d91eea18db --- /dev/null +++ b/raw/rel-18/29_series/29256/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d5a8981bf999a4c044f0f10ac294385b5e186d1928dfc4b6bddf75cbab35efe +size 9504 diff --git a/raw/rel-18/29_series/29256/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29256/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8100a15c900e98697870ba4c1afddbe7c9b3ee68 --- /dev/null +++ b/raw/rel-18/29_series/29256/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb40bc9f76c66728d07c34b52e7e2c983ae7e9e2ffb632d60220ebfd237c17a3 +size 5694 diff --git a/raw/rel-18/29_series/29256/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/raw/rel-18/29_series/29256/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e252773dc5658e538479bd95d9927976ef8ab838 --- /dev/null +++ b/raw/rel-18/29_series/29256/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:586f7694b4675dea8ebccc625f8d3d0c9490599228353f3146d0800ac2e2e0ab +size 35123 diff --git a/raw/rel-18/29_series/29256/c52116487ab4b76a2415714183c9a14a_img.jpg b/raw/rel-18/29_series/29256/c52116487ab4b76a2415714183c9a14a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcf6eb2e5d43b90cf052a67881bf2921b4f55931 --- /dev/null +++ b/raw/rel-18/29_series/29256/c52116487ab4b76a2415714183c9a14a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d10b55503f0713a1b461b3e78d6bdc646975f7a1975486841fbb0832a1599666 +size 9340 diff --git a/raw/rel-18/29_series/29256/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/29_series/29256/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d8381c32406b6f3474e064911520d42e92b3a07 --- /dev/null +++ b/raw/rel-18/29_series/29256/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8ddee30c9058d5c2d4b229ebd2b0dd7fb462cca69951c60405f0664a48ce538 +size 26325 diff --git a/raw/rel-18/29_series/29256/e787e02d9214556476d95941bda1d350_img.jpg b/raw/rel-18/29_series/29256/e787e02d9214556476d95941bda1d350_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ec10f01f08390a4d1e917ab9ce13ab31dc0ad5b --- /dev/null +++ b/raw/rel-18/29_series/29256/e787e02d9214556476d95941bda1d350_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46f5834c699b46f35bf3422cc8d754908d2406cc550166493dfe61bd70485844 +size 34308 diff --git a/raw/rel-18/29_series/29257/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/29_series/29257/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44c4c989fed7b78af2ac2326f425a1b634cdb6c3 --- /dev/null +++ b/raw/rel-18/29_series/29257/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:748703ff5030da56caa1c148a916a65c1ae38dcf983fbf200954499ca1bccdae +size 25526 diff --git a/raw/rel-18/29_series/29257/0a83cda688278bb05ef5134e66bdaf6e_img.jpg b/raw/rel-18/29_series/29257/0a83cda688278bb05ef5134e66bdaf6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..491bc10494858ed6d0d160938177b16d68e9b663 --- /dev/null +++ b/raw/rel-18/29_series/29257/0a83cda688278bb05ef5134e66bdaf6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56f7d9e264d51b01093f0d8a00356b3ebf191375ac884d9ee4febe6edd47f62c +size 20108 diff --git a/raw/rel-18/29_series/29257/147f857b06606c016ce376b7a89934d2_img.jpg b/raw/rel-18/29_series/29257/147f857b06606c016ce376b7a89934d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ca879c8e20ed99190feedb910ee115e9a9ff919 --- /dev/null +++ b/raw/rel-18/29_series/29257/147f857b06606c016ce376b7a89934d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52ef90b3eec57764d4e1bcd0a4aaab922be4a944d4b659e364829337824056c3 +size 19708 diff --git a/raw/rel-18/29_series/29257/1f5279ac241813966be03158ad92142b_img.jpg b/raw/rel-18/29_series/29257/1f5279ac241813966be03158ad92142b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404ce705e1d4d9fd877e1dec16e5e88b37faa173 --- /dev/null +++ b/raw/rel-18/29_series/29257/1f5279ac241813966be03158ad92142b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:370af3e4f8a4eb87cbb13684fd8490a6d3fbe830c0723c826f2a4b1767940c5a +size 15822 diff --git a/raw/rel-18/29_series/29257/20136850feb70fd71c7d41cdae203ebb_img.jpg b/raw/rel-18/29_series/29257/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58a629961ddabd2d242a99b6f26695fe26e5c469 --- /dev/null +++ b/raw/rel-18/29_series/29257/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:738865ac6c1f536354cdd2fb150fbda839290113c02b23eab02fa43603fe98cd +size 24006 diff --git a/raw/rel-18/29_series/29257/220869911a1ecfa1dd4aa6d750319aad_img.jpg b/raw/rel-18/29_series/29257/220869911a1ecfa1dd4aa6d750319aad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dfabe76097a4ed9fa6edb33909f81c4d1d388df --- /dev/null +++ b/raw/rel-18/29_series/29257/220869911a1ecfa1dd4aa6d750319aad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31dcd3f62355df0724f6fe8c5b46c258c8a1d234b97a233a307aaf312326fbef +size 25970 diff --git a/raw/rel-18/29_series/29257/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/29_series/29257/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..017915820e8447e1f3e8a0dc349703de68dca406 --- /dev/null +++ b/raw/rel-18/29_series/29257/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09bed08497be02e2ad8ad4217299da6f275b8c1b859ea3295f79d1eb36228f85 +size 27635 diff --git a/raw/rel-18/29_series/29257/2834bdd6eb8540277e609decbb924003_img.jpg b/raw/rel-18/29_series/29257/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab4d7af37893864e41001fceeaeffdbc63e23e93 --- /dev/null +++ b/raw/rel-18/29_series/29257/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5970247813c1c2ffe4dc07fed0fcbff2978b298eab6e02df730414e8320f6a58 +size 26974 diff --git a/raw/rel-18/29_series/29257/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/raw/rel-18/29_series/29257/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f751996c2c5b15413d264c096bb9393784f3c743 --- /dev/null +++ b/raw/rel-18/29_series/29257/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c92ba3faf3555f951fbb12aa513a0cdad447918b1d5356526a63d4efadeebaf6 +size 15481 diff --git a/raw/rel-18/29_series/29257/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/29_series/29257/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5215afafdc41aff6be01b65a72719b5725e6f63f --- /dev/null +++ b/raw/rel-18/29_series/29257/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6a5935c9110a6163455e3495251d4c883ebef6a09bbf97897c1223f62442f4b +size 25506 diff --git a/raw/rel-18/29_series/29257/3d53d3bbe5b70dfc8d612c63b9587837_img.jpg b/raw/rel-18/29_series/29257/3d53d3bbe5b70dfc8d612c63b9587837_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..558ba0897cf2c7b2ca8478df3dce564fcd0a0c7c --- /dev/null +++ b/raw/rel-18/29_series/29257/3d53d3bbe5b70dfc8d612c63b9587837_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2190b3643b48376ee244eff38584356d7f1a1088b840bd9b72bbca97fc6eec68 +size 17251 diff --git a/raw/rel-18/29_series/29257/4b935d396d60146aaa66ac7372c758b7_img.jpg b/raw/rel-18/29_series/29257/4b935d396d60146aaa66ac7372c758b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a84ab006e00987c6bf21adfd6b3accfd644a103 --- /dev/null +++ b/raw/rel-18/29_series/29257/4b935d396d60146aaa66ac7372c758b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8203fb8f7afcd497585f8dc1b0a287c41b5b212d65eb898c805aab484edbf221 +size 27523 diff --git a/raw/rel-18/29_series/29257/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29257/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbb75f7096d06a13b95c89d5a53204e581f95b34 --- /dev/null +++ b/raw/rel-18/29_series/29257/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24a176844728ff17e6131dce62591f4544951a47ad652bcccaf9c41334e3fdb3 +size 9474 diff --git a/raw/rel-18/29_series/29257/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29257/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b26c72c647c879e9569a7eb0f96fdfe43b7d680f --- /dev/null +++ b/raw/rel-18/29_series/29257/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52e7c98e5228bddd8b9056a2ff53a80a983c33d9e856148de84bce01a70d2b27 +size 5729 diff --git a/raw/rel-18/29_series/29257/75e4b78ee25f885d73120e3066a5253e_img.jpg b/raw/rel-18/29_series/29257/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2093faaef42f1f180fecf3b663d764a64495991 --- /dev/null +++ b/raw/rel-18/29_series/29257/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b418f849b2cbeccd70035c19559a5b102f87587ad5e71fe9dc91aded4ae9cfc +size 31169 diff --git a/raw/rel-18/29_series/29257/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29257/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63bdae3309e467a0fee81a8fe025b1b3bb9ded37 --- /dev/null +++ b/raw/rel-18/29_series/29257/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c33e11818e621d23616174d5f89a4527855391e0682999596d64ccafac8fd03d +size 30570 diff --git a/raw/rel-18/29_series/29257/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/raw/rel-18/29_series/29257/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..506a8ad94385788835d527fc481e52c8add861a1 --- /dev/null +++ b/raw/rel-18/29_series/29257/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:656220553400c243106e2a5462f5c4abbfa9125ccf091146c00c05291b60f47c +size 26392 diff --git a/raw/rel-18/29_series/29257/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/29_series/29257/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57d485d99ad3fd22a96b1c9dbbc0ef70fab16090 --- /dev/null +++ b/raw/rel-18/29_series/29257/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:701a20ba6d67aca5d3a95bcd9022c2b2a5f08d216d1ad841bc824b4c109a624d +size 31704 diff --git a/raw/rel-18/29_series/29257/836b0790cef5469a167fa8931df4e408_img.jpg b/raw/rel-18/29_series/29257/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7531f7fc27a66d1d81c74fccb35b3f1b5de0e35 --- /dev/null +++ b/raw/rel-18/29_series/29257/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95477eca41bda770df962358d755283459863388384f43bfd0cd0fe6ba2fd18d +size 28198 diff --git a/raw/rel-18/29_series/29257/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/raw/rel-18/29_series/29257/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a66d9c815819eb2fcd34b16f556ed50ad9b03407 --- /dev/null +++ b/raw/rel-18/29_series/29257/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42adbb7352d4ef249f7f57a6f60d256679bbb8d63e3fa3036ef0aed5b3c9085a +size 26708 diff --git a/raw/rel-18/29_series/29257/94fd137860c16c8dfd75512f10161fe8_img.jpg b/raw/rel-18/29_series/29257/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02c04184b289dc4ab22eb4487cf99c84ea1f92e4 --- /dev/null +++ b/raw/rel-18/29_series/29257/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b76c97317b0a2722fab7fd52696c99465623de9ddcd834707681ef4c64c3919 +size 23578 diff --git a/raw/rel-18/29_series/29257/96b5a08abda472c0c3838ecf1357f57f_img.jpg b/raw/rel-18/29_series/29257/96b5a08abda472c0c3838ecf1357f57f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45d3e1463b725a91e58b6dcb9c94166b2dc505ed --- /dev/null +++ b/raw/rel-18/29_series/29257/96b5a08abda472c0c3838ecf1357f57f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70e89dfdefd783b77681f80449374252064d12b76e193dae2276735992807730 +size 12199 diff --git a/raw/rel-18/29_series/29257/9b62a616c7a1097c5da57f001ab6dd64_img.jpg b/raw/rel-18/29_series/29257/9b62a616c7a1097c5da57f001ab6dd64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b5027df3b0e41b83f12b8e6307942ebeac5dea2 --- /dev/null +++ b/raw/rel-18/29_series/29257/9b62a616c7a1097c5da57f001ab6dd64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305fdf48de5bd779fa19a2e80271555ca53f7b9473d0e5611510da7ca1de620f +size 30535 diff --git a/raw/rel-18/29_series/29257/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/29_series/29257/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08e7ef8ebdbd911ef241012abaa5752d9bd340a4 --- /dev/null +++ b/raw/rel-18/29_series/29257/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:466b019f7ed701bc1a7f92e3090b8cd8ed9f38362fba4587b366a7c9b7f44ac4 +size 28444 diff --git a/raw/rel-18/29_series/29257/b5335262987c819d7f71ce40f99cb71b_img.jpg b/raw/rel-18/29_series/29257/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b3d66b39de7779e4f346fd39c41b5187af3da33 --- /dev/null +++ b/raw/rel-18/29_series/29257/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:688d04568f3e9ba0c285af43764b5303ece9111a7a6128cf39d3694c7a072a30 +size 24872 diff --git a/raw/rel-18/29_series/29257/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/raw/rel-18/29_series/29257/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f64329655320b4dca320755fb7a2ff76fe32a8bb --- /dev/null +++ b/raw/rel-18/29_series/29257/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25f63c27f39b38a6df2010cd6d25cd6ec49df1f143d2bed3de9505b485fb1f53 +size 32878 diff --git a/raw/rel-18/29_series/29257/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/raw/rel-18/29_series/29257/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ddfb79718072880a544192d3a1db066709df21 --- /dev/null +++ b/raw/rel-18/29_series/29257/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00fa7adbd6bb7975fe26b8f41a2d23c79781a743aab32e65fe507fa7fe9f2c79 +size 35829 diff --git a/raw/rel-18/29_series/29257/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/29_series/29257/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ff1aa679be0bdca119db9105e4de1572d372147 --- /dev/null +++ b/raw/rel-18/29_series/29257/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cb35954ea6a2c9625973bbb273b4f12ca290f8ee18a2b44a7e8a2203730f27c +size 31295 diff --git a/raw/rel-18/29_series/29257/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/raw/rel-18/29_series/29257/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ed30ec4dcc5e5143b6eb827690108a2a7fd275 --- /dev/null +++ b/raw/rel-18/29_series/29257/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08459dfb7aeea416da0fc9b3e4243dbdc67889e8232e8d950c9be6de3e654ce5 +size 59971 diff --git a/raw/rel-18/29_series/29257/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/raw/rel-18/29_series/29257/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d316d36f10ae3c66b7d75810bfad30304758b8d --- /dev/null +++ b/raw/rel-18/29_series/29257/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f19811d8bc568bf534b2ea8b37acea98f012fa7622f5f7d33a51caaf38909479 +size 28780 diff --git a/raw/rel-18/29_series/29272/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29272/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c14fc913120a041401f0b0c55f4523f97b14ce6a --- /dev/null +++ b/raw/rel-18/29_series/29272/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c0ba0b096ac610db2a96c3489cc29fe11917c4740bbc7b80a9ce27127455250 +size 9423 diff --git a/raw/rel-18/29_series/29272/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29272/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad7843a7d2fa2d4e9282e77a45f286ae20523511 --- /dev/null +++ b/raw/rel-18/29_series/29272/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:585a0d7292f705b372394a87200f0c3098312eb888111ce4c7de4be4613e60c7 +size 5523 diff --git a/raw/rel-18/29_series/29273/05c032edd038c8ac33e4cec9d7e9f1be_img.jpg b/raw/rel-18/29_series/29273/05c032edd038c8ac33e4cec9d7e9f1be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..739865f25c6debd063376a6a2ac0af116344008c --- /dev/null +++ b/raw/rel-18/29_series/29273/05c032edd038c8ac33e4cec9d7e9f1be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e1a53d7acadb379ceedfdd43f76672cf9f30fd6a8c8d661887c9fc31309361 +size 144779 diff --git a/raw/rel-18/29_series/29273/476b627f69146cf2c394a1f1f697b24e_img.jpg b/raw/rel-18/29_series/29273/476b627f69146cf2c394a1f1f697b24e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..609d0115e9d6152a5b9e822f16ab9a250919973d --- /dev/null +++ b/raw/rel-18/29_series/29273/476b627f69146cf2c394a1f1f697b24e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70c30a2e9073493ea5de6b3c8398688e2eef8246814767729065c7935fe87d12 +size 143116 diff --git a/raw/rel-18/29_series/29273/535f1ef9b1085c01063ee20d0f1942b7_img.jpg b/raw/rel-18/29_series/29273/535f1ef9b1085c01063ee20d0f1942b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4223917f2e3f85ac32ca26907db2c79831a6ab6c --- /dev/null +++ b/raw/rel-18/29_series/29273/535f1ef9b1085c01063ee20d0f1942b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0674f5a4da09cf670f9b49cd129452b6e0ebadc87b241280d8674a59f633b7d +size 108089 diff --git a/raw/rel-18/29_series/29273/54d030ecf3f147af8773b8a23549856e_img.jpg b/raw/rel-18/29_series/29273/54d030ecf3f147af8773b8a23549856e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb0e1b2d95d1ae446787f6df5ac934f119d36825 --- /dev/null +++ b/raw/rel-18/29_series/29273/54d030ecf3f147af8773b8a23549856e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cffee829d94b590a625da41bbc2c7f70a11d5fb320a75b7cca8b74839c543b75 +size 103188 diff --git a/raw/rel-18/29_series/29273/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29273/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..411e6b5a33a422caa6b676a3577ff5a6a0403ea6 --- /dev/null +++ b/raw/rel-18/29_series/29273/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d884caf26ffdef609306a8770f2cd9dd740e345b9b17ad73383241ab1fb1a9cb +size 9654 diff --git a/raw/rel-18/29_series/29273/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29273/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcd04a4a8c9f3575d584421a2b9e14ee3b6f51b1 --- /dev/null +++ b/raw/rel-18/29_series/29273/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c34831b9b062356ce4a9a031d533714b0b511817a3b162f2ba10d8857ff4459a +size 6430 diff --git a/raw/rel-18/29_series/29273/74340c36eadb11d858e925d7b77260bf_img.jpg b/raw/rel-18/29_series/29273/74340c36eadb11d858e925d7b77260bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81b35b169f40c374dfa7d21ad1d155391fdc2e96 --- /dev/null +++ b/raw/rel-18/29_series/29273/74340c36eadb11d858e925d7b77260bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ae0884a373762149edc89ad5c9caab648205d464943b37195570ace710c1311 +size 151388 diff --git a/raw/rel-18/29_series/29273/7474a6dfb4787da442d12dcaec98fd04_img.jpg b/raw/rel-18/29_series/29273/7474a6dfb4787da442d12dcaec98fd04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0ba372b7068c531eab229af9a42a5f17b8d26f6 --- /dev/null +++ b/raw/rel-18/29_series/29273/7474a6dfb4787da442d12dcaec98fd04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52495997b67480d89c42a4f06f254a2fd069a1a530f7ed412e5a417dedf352c5 +size 167736 diff --git a/raw/rel-18/29_series/29273/83fd0d406cba6f9c189e77e05859a600_img.jpg b/raw/rel-18/29_series/29273/83fd0d406cba6f9c189e77e05859a600_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..299cc036875fe642f294e4c48eebe840903e7ea1 --- /dev/null +++ b/raw/rel-18/29_series/29273/83fd0d406cba6f9c189e77e05859a600_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4001699ccc785a9f6bb551bc268c953d0cf9d76c4e2eae00f0f9ee5e76f56d93 +size 133541 diff --git a/raw/rel-18/29_series/29273/8650b869a9e7291ac2caad3d008e1770_img.jpg b/raw/rel-18/29_series/29273/8650b869a9e7291ac2caad3d008e1770_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faae691e77042f3a0baf42687e7ba3ff816e6333 --- /dev/null +++ b/raw/rel-18/29_series/29273/8650b869a9e7291ac2caad3d008e1770_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3552584858815d9e8eba396ed68a877f076e2cbeeca614497a218719579eaf9 +size 142184 diff --git a/raw/rel-18/29_series/29274/0f758e9df33317ae55b3bd118241475a_img.jpg b/raw/rel-18/29_series/29274/0f758e9df33317ae55b3bd118241475a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55a53b4ef59ea50d997c623d78ec6237d282fb38 --- /dev/null +++ b/raw/rel-18/29_series/29274/0f758e9df33317ae55b3bd118241475a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58052c35e506bbdcbea4c7bca78ed0c4af507b49cf8ff9dfa22920b03aa1526c +size 50576 diff --git a/raw/rel-18/29_series/29274/1665662b273f8ed3917945aee28d40ce_img.jpg b/raw/rel-18/29_series/29274/1665662b273f8ed3917945aee28d40ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..199f50e8d4b44ef6759544b5f24a9f4b600fe9ed --- /dev/null +++ b/raw/rel-18/29_series/29274/1665662b273f8ed3917945aee28d40ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db741b670f1c91fc7d3f17b4359770354f8a4a0b5c65b74dbdd743ff047e685e +size 36626 diff --git a/raw/rel-18/29_series/29274/172ff468eac72a2e1ec81d06fa3b96b1_img.jpg b/raw/rel-18/29_series/29274/172ff468eac72a2e1ec81d06fa3b96b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2c2757ee11f0f8acc30d5d4529434583e692c36 --- /dev/null +++ b/raw/rel-18/29_series/29274/172ff468eac72a2e1ec81d06fa3b96b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aa0075591120625df051df02d1746696de3a3d916c52e3fbdbe30b0e6c6b390 +size 20539 diff --git a/raw/rel-18/29_series/29274/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/raw/rel-18/29_series/29274/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f397a1b09cfb3a38f07fbdaf4c67c4c1050245 --- /dev/null +++ b/raw/rel-18/29_series/29274/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0201891c0ab80ac80db4190a029e6af7135ad21d07d903432e634755de6301dd +size 41119 diff --git a/raw/rel-18/29_series/29274/1f94fa97697122830275fb74bbe6f718_img.jpg b/raw/rel-18/29_series/29274/1f94fa97697122830275fb74bbe6f718_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bc345c5bc2b6018523478bc2ba6fce81270ff0f --- /dev/null +++ b/raw/rel-18/29_series/29274/1f94fa97697122830275fb74bbe6f718_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:015d00a22929e0506cf1edd07628e4d3d28d8707b19eb275c123f77c0bf221ff +size 59883 diff --git a/raw/rel-18/29_series/29274/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/29_series/29274/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..348f834f04e5c59ac4b1c541f0841115b2e8e46c --- /dev/null +++ b/raw/rel-18/29_series/29274/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76e6b08c8f35bd8aa72d997e53a891a0b2cdcfcd9a978bf94c4c319aaa50e044 +size 19134 diff --git a/raw/rel-18/29_series/29274/2cd72d2716bc151a96eb4e6dd0f17f00_img.jpg b/raw/rel-18/29_series/29274/2cd72d2716bc151a96eb4e6dd0f17f00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea6366342ec9dcab61eb50e28431e0f51b835b7 --- /dev/null +++ b/raw/rel-18/29_series/29274/2cd72d2716bc151a96eb4e6dd0f17f00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38eb3195870df1c0318be060e0477ead44dbeda5c0afdb1fe0836ab8b12a5abe +size 35150 diff --git a/raw/rel-18/29_series/29274/553cc3a9fcac62aaa93bb0f2693909c3_img.jpg b/raw/rel-18/29_series/29274/553cc3a9fcac62aaa93bb0f2693909c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..588d35e41018c1bd4460029f8d0c28f6c9e729f4 --- /dev/null +++ b/raw/rel-18/29_series/29274/553cc3a9fcac62aaa93bb0f2693909c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:341fd90d2b0291994cf6fa93ec30db8802873c1d6da646081a68b76ed7c1f987 +size 30375 diff --git a/raw/rel-18/29_series/29274/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29274/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cc0de77afa395cc74155c50fc3e06325fab2a20 --- /dev/null +++ b/raw/rel-18/29_series/29274/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20a284ef348b84f0d1e025101260119cbaf9bd9ad047e886141b2cc9d3628318 +size 9506 diff --git a/raw/rel-18/29_series/29274/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29274/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51db6ee2acad02f38bceff5a52805c4b694d151d --- /dev/null +++ b/raw/rel-18/29_series/29274/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9cdd8d1ac62e415e4c9722b88b5b3a0be1b32e3900723469280f3276b1fe547 +size 5504 diff --git a/raw/rel-18/29_series/29274/6d7989325053731fda7ae4de0e946b24_img.jpg b/raw/rel-18/29_series/29274/6d7989325053731fda7ae4de0e946b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb4be5043e3bebe33431cc478bc9545e10953bd --- /dev/null +++ b/raw/rel-18/29_series/29274/6d7989325053731fda7ae4de0e946b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92f28db7af85d0a1ecc9366cf7c36e8d361bc485527d5009ab9aa6e0a4cf7651 +size 21843 diff --git a/raw/rel-18/29_series/29274/80e77ddd48fe0d85dfa940d745a36dd1_img.jpg b/raw/rel-18/29_series/29274/80e77ddd48fe0d85dfa940d745a36dd1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08e95a5d1444e810894e13df73c0f0c1a7819c0e --- /dev/null +++ b/raw/rel-18/29_series/29274/80e77ddd48fe0d85dfa940d745a36dd1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3668330fc8d12e9bf16f259ae02d1b742121b6edc6e966b4c69347c96126f43f +size 42846 diff --git a/raw/rel-18/29_series/29274/8977040947701adcb87cbb816b50e8a6_img.jpg b/raw/rel-18/29_series/29274/8977040947701adcb87cbb816b50e8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6f225ef0fd0934efdeae78b769777c343d2ff33 --- /dev/null +++ b/raw/rel-18/29_series/29274/8977040947701adcb87cbb816b50e8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:048a442efab4acd9ee47f214a781576d9638f791f5733bd8568ef74b9ed9b2a0 +size 29196 diff --git a/raw/rel-18/29_series/29274/8de50ab594c6c0e62405239e3d0c4a1c_img.jpg b/raw/rel-18/29_series/29274/8de50ab594c6c0e62405239e3d0c4a1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597d56914050525ff1ffdf392114e86346a752c6 --- /dev/null +++ b/raw/rel-18/29_series/29274/8de50ab594c6c0e62405239e3d0c4a1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d47845e7035784881189f2a2e1ba63d42d60834907dc09cfa4be80ec8ace65a +size 22768 diff --git a/raw/rel-18/29_series/29274/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/29_series/29274/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba21dc8d57ade24265009d51831b873f0b4601c6 --- /dev/null +++ b/raw/rel-18/29_series/29274/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a9b4bd6a88416e36d5e0033ea4889e5151a7678252840847f370667f63dd616 +size 43096 diff --git a/raw/rel-18/29_series/29274/93f97cde167486965f0c9f9466fdb92a_img.jpg b/raw/rel-18/29_series/29274/93f97cde167486965f0c9f9466fdb92a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dba18bdbff7eef531d7e566bf73764e7c0d3a52b --- /dev/null +++ b/raw/rel-18/29_series/29274/93f97cde167486965f0c9f9466fdb92a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36edd21699a562896f5a1b8a07d47411188da8c084cdb9835f35a380e8a984ec +size 28739 diff --git a/raw/rel-18/29_series/29274/9c575767fe4409cdd2898df6f70139f5_img.jpg b/raw/rel-18/29_series/29274/9c575767fe4409cdd2898df6f70139f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c49d85116592cfdcdb8af91e7ca1b71468dd138 --- /dev/null +++ b/raw/rel-18/29_series/29274/9c575767fe4409cdd2898df6f70139f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3f509da3494d6548bc112c0fc940f11b52808944bd2741460c1997497030b25 +size 52486 diff --git a/raw/rel-18/29_series/29274/9d3809e32331234c2e4d0a77622834e1_img.jpg b/raw/rel-18/29_series/29274/9d3809e32331234c2e4d0a77622834e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b1182c45be6ae0445234bbebd799e77dce90cb2 --- /dev/null +++ b/raw/rel-18/29_series/29274/9d3809e32331234c2e4d0a77622834e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1fef313c3ebed66e77c9113b49cd1d6f7f802273a41ad46e6d259fc45c96bcf +size 31116 diff --git a/raw/rel-18/29_series/29274/a01025ddfe10b3070f348bbedf8244db_img.jpg b/raw/rel-18/29_series/29274/a01025ddfe10b3070f348bbedf8244db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3b90580396193814644bd0b44f9bea4d6aeee25 --- /dev/null +++ b/raw/rel-18/29_series/29274/a01025ddfe10b3070f348bbedf8244db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e924440f54fb35defa8dd6ec034e249a458229f8d182f451fa84130a2adfcf27 +size 91807 diff --git a/raw/rel-18/29_series/29274/abd25ff60b59fa64f0bc0e5c6ba6e67e_img.jpg b/raw/rel-18/29_series/29274/abd25ff60b59fa64f0bc0e5c6ba6e67e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d664f780e7743ad16aba631215e212a7bbaf5bf0 --- /dev/null +++ b/raw/rel-18/29_series/29274/abd25ff60b59fa64f0bc0e5c6ba6e67e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3efb2c8f0de24adb8700ff5ff28d56a17bd4485520790b4048edbc32027fac10 +size 29970 diff --git a/raw/rel-18/29_series/29274/adeeb4d1a6c2e47321b8166cab396dea_img.jpg b/raw/rel-18/29_series/29274/adeeb4d1a6c2e47321b8166cab396dea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98794a416f0409a9e2a8f10acecae777c2eac476 --- /dev/null +++ b/raw/rel-18/29_series/29274/adeeb4d1a6c2e47321b8166cab396dea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29095b83025e66f0c6068a5f728ff32932fabf87b72c2f0d3d47691f486a2e32 +size 31170 diff --git a/raw/rel-18/29_series/29274/b1ec498620251169dcfc839e18443154_img.jpg b/raw/rel-18/29_series/29274/b1ec498620251169dcfc839e18443154_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c746773223e0ddbdca6016916ccdb20022c0a1e --- /dev/null +++ b/raw/rel-18/29_series/29274/b1ec498620251169dcfc839e18443154_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9894a58e251a3c5a868704dab10a0c84521bf1e70934eefcf0e1eeec8547b177 +size 172759 diff --git a/raw/rel-18/29_series/29274/b38817d867550ae783546d5910d4db22_img.jpg b/raw/rel-18/29_series/29274/b38817d867550ae783546d5910d4db22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e9e4a847ad04accd93a83163fdaacecb4552790 --- /dev/null +++ b/raw/rel-18/29_series/29274/b38817d867550ae783546d5910d4db22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99600ea6148f9bf118efe6fa12b3e10cf80d2d1d659a72a5f2a7c41f93c8dd9b +size 30429 diff --git a/raw/rel-18/29_series/29274/bc70ba57738f609407ddaf4f2acbf51e_img.jpg b/raw/rel-18/29_series/29274/bc70ba57738f609407ddaf4f2acbf51e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c624fcd6f6775873a186d34374dd8cb083e7c4a0 --- /dev/null +++ b/raw/rel-18/29_series/29274/bc70ba57738f609407ddaf4f2acbf51e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e27675a6d7cb7ba3807447770040a4193a2fc28aff08a8ea5a50a2d42a39f084 +size 34868 diff --git a/raw/rel-18/29_series/29274/bcc8fecc8798383960e1a5990fd88889_img.jpg b/raw/rel-18/29_series/29274/bcc8fecc8798383960e1a5990fd88889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff103b7b3d92c889f22242e8aaf93fb539f51656 --- /dev/null +++ b/raw/rel-18/29_series/29274/bcc8fecc8798383960e1a5990fd88889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d744171db455a6d29ad6a835d2fb0f50267d7b711c1235f51b9a455302f44de +size 107981 diff --git a/raw/rel-18/29_series/29274/c49149f8f81706aab83bea5771ffb867_img.jpg b/raw/rel-18/29_series/29274/c49149f8f81706aab83bea5771ffb867_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1fc656bea49a72b4020f6af7dab3c6851cda4c8 --- /dev/null +++ b/raw/rel-18/29_series/29274/c49149f8f81706aab83bea5771ffb867_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0fd4877653d0ab33219aeb715d8d0ffb682b95ac3c08e952917e4c6a56bb112 +size 24446 diff --git a/raw/rel-18/29_series/29274/c7bb86c1e9320a155c0e66a3f26f9643_img.jpg b/raw/rel-18/29_series/29274/c7bb86c1e9320a155c0e66a3f26f9643_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2dc5b98df57fe9ce5de5693a276a89d5c0d932b1 --- /dev/null +++ b/raw/rel-18/29_series/29274/c7bb86c1e9320a155c0e66a3f26f9643_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f5d18920d0ff630ceb41af3febfe90a648d1dc8958ffad6a7b8fdc3ee967035 +size 28797 diff --git a/raw/rel-18/29_series/29274/dda72b6afeac47479e0746d4eaf6745a_img.jpg b/raw/rel-18/29_series/29274/dda72b6afeac47479e0746d4eaf6745a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6692e5e145069e18bdc5597bf01b9889d3d12c35 --- /dev/null +++ b/raw/rel-18/29_series/29274/dda72b6afeac47479e0746d4eaf6745a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4749db906fc4f9314c6395ed1655fc23eb52c0ef923108715d73105c458c7035 +size 23987 diff --git a/raw/rel-18/29_series/29274/e3734a615e069a3923c72f1ef4608fa9_img.jpg b/raw/rel-18/29_series/29274/e3734a615e069a3923c72f1ef4608fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85ab11726e55652f68b14ffe22879e057ce7ef87 --- /dev/null +++ b/raw/rel-18/29_series/29274/e3734a615e069a3923c72f1ef4608fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d41bf6cefc92eee61fb25363a5c2a72d786116b79e74972da32fdce4222262d3 +size 51297 diff --git a/raw/rel-18/29_series/29274/ec27906099ab5da32f29b89d2764cf0c_img.jpg b/raw/rel-18/29_series/29274/ec27906099ab5da32f29b89d2764cf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ad85d03b7875985ec03f2b88e700dc3288de6c5 --- /dev/null +++ b/raw/rel-18/29_series/29274/ec27906099ab5da32f29b89d2764cf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa77d59f8776caf012577c2fc8a2a037b1ffcc4fa8c74f87c97974a79f557f85 +size 34910 diff --git a/raw/rel-18/29_series/29281/15e4a144a88176b71ea3eff2722253b0_img.jpg b/raw/rel-18/29_series/29281/15e4a144a88176b71ea3eff2722253b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5560e6e818e3b33f07b5352facd42a6d1c19f5c9 --- /dev/null +++ b/raw/rel-18/29_series/29281/15e4a144a88176b71ea3eff2722253b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93ad74be3076fe1d60842cee7a887b7974d96315c690ae8ea570230e30796382 +size 23426 diff --git a/raw/rel-18/29_series/29281/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/raw/rel-18/29_series/29281/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ee2ccf8ee16071fd45148b6d3e1586eae593935 --- /dev/null +++ b/raw/rel-18/29_series/29281/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ce1a6e83ed68c8be6ba4a80e07e8b5bc268d901560686b7cfa60040efd33e48 +size 17544 diff --git a/raw/rel-18/29_series/29281/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29281/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e2f03a263ae80fcf00fc13beb86c221ea850eaa --- /dev/null +++ b/raw/rel-18/29_series/29281/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c91a21c6652f18f3ea311c78badfc242bbeea2c547ee5114744787d42be81ee +size 9419 diff --git a/raw/rel-18/29_series/29281/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29281/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03ab4621b74a3c922c4767e49171eee6d0047a1a --- /dev/null +++ b/raw/rel-18/29_series/29281/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77ac585c84eb5a6a49bceea3274bd8b52032eefec2c7f0afdc158843c6275aab +size 5681 diff --git a/raw/rel-18/29_series/29281/68d8089266ace7197304b43dcaf5d08e_img.jpg b/raw/rel-18/29_series/29281/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..013018fb8470de3330b58644c9546ff57b1ee67c --- /dev/null +++ b/raw/rel-18/29_series/29281/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b0ae328ac282d1fd2eb8c5e7f19d5e73eab642bbb39188cc417e6b0f472b0cf +size 27535 diff --git a/raw/rel-18/29_series/29281/805c475f0859e607af0530ba43194bf1_img.jpg b/raw/rel-18/29_series/29281/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39055d7de9b9ecfc090c213c7c7f4287ad58175f --- /dev/null +++ b/raw/rel-18/29_series/29281/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c18cdc80a09a53a0b6ea0fbc227eabf4b06a751d596ec63b8d860203d2aff10d +size 20248 diff --git a/raw/rel-18/29_series/29281/9a159e2112eac7be06bdb97e84a0c49a_img.jpg b/raw/rel-18/29_series/29281/9a159e2112eac7be06bdb97e84a0c49a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddb71aed151c4d1691c242f0d9668beeca268685 --- /dev/null +++ b/raw/rel-18/29_series/29281/9a159e2112eac7be06bdb97e84a0c49a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d31fb48739f26bc7d4b3eb87211dd61b2541684b7a622d181b79dbe83ea34371 +size 19498 diff --git a/raw/rel-18/29_series/29281/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/29_series/29281/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce31643130e710329c31adc11a8061b8c970aa9c --- /dev/null +++ b/raw/rel-18/29_series/29281/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec4e31e537eb1b5dcb00f80a43349468539026e703ab14e1735dcbbdb4105f5a +size 17404 diff --git a/raw/rel-18/29_series/29281/ddc7460821484f1ae2835c67955c554c_img.jpg b/raw/rel-18/29_series/29281/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e21bc7845c111d60d84833e949d2caf848621794 --- /dev/null +++ b/raw/rel-18/29_series/29281/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efee3eff02b52fd3c87391471bfc5f502c1d83cfb2dcda7377b50f0ba85782c0 +size 24270 diff --git a/raw/rel-18/29_series/29281/f2ea0f64a770b22b902820457d262265_img.jpg b/raw/rel-18/29_series/29281/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6ef342909001413348d5dca7dff602992254ee4 --- /dev/null +++ b/raw/rel-18/29_series/29281/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305e4b49cf0d8eeb3cadb213185d2e9b65db202c3d2144ef08c9b652f3771f7c +size 26056 diff --git a/raw/rel-18/29_series/29281/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29281/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d91e808478fc76c07c79da3134e2087c79d25d99 --- /dev/null +++ b/raw/rel-18/29_series/29281/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7bc005ff5626abc9f30a0381dad1e769dd480eddb4deba30ae7dd9a821a6ccb +size 14458 diff --git a/raw/rel-18/29_series/29309/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/raw/rel-18/29_series/29309/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24d459bc5718fa588bcab525e5beedea3c6ee462 --- /dev/null +++ b/raw/rel-18/29_series/29309/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ede73eb315dd80ff38527cc5a687d6e7462c773e584c06e15ad2bc090a390693 +size 38741 diff --git a/raw/rel-18/29_series/29309/5a4e62bead259c258d069fd3663ea670_img.jpg b/raw/rel-18/29_series/29309/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a4b3a31a49dec56d65c20bf17824d2188b68a8f --- /dev/null +++ b/raw/rel-18/29_series/29309/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d5a5abf923caa007bb1f38dfe326dde2ec7b86bb62d66c384c2b961627767c2 +size 36476 diff --git a/raw/rel-18/29_series/29309/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29309/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5c4bb2ecfef6c86e01e0aab6c736b862f97a493 --- /dev/null +++ b/raw/rel-18/29_series/29309/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a61ef5d05f5cce63ff4d5e25863c89f46bf13e645ca881710dd24e263492e4a +size 9539 diff --git a/raw/rel-18/29_series/29309/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29309/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03ab4621b74a3c922c4767e49171eee6d0047a1a --- /dev/null +++ b/raw/rel-18/29_series/29309/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77ac585c84eb5a6a49bceea3274bd8b52032eefec2c7f0afdc158843c6275aab +size 5681 diff --git a/raw/rel-18/29_series/29309/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/raw/rel-18/29_series/29309/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89dc953a78be09b4c144e5146bd5765fb9dbc0bb --- /dev/null +++ b/raw/rel-18/29_series/29309/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffc4f0c037517a61d8a2bf3dc72fc08d00f34a809908cf6740295de491da0150 +size 17025 diff --git a/raw/rel-18/29_series/29309/ddde3ebb7c1a58ec96bd5cc64e664ab0_img.jpg b/raw/rel-18/29_series/29309/ddde3ebb7c1a58ec96bd5cc64e664ab0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6b01c671fe3da9e8c3a509af317a15ff5529e36 --- /dev/null +++ b/raw/rel-18/29_series/29309/ddde3ebb7c1a58ec96bd5cc64e664ab0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2831ce040a7548076ab82e3c781ca4eb61f2abecc1aa76c996f315519d3a1bc0 +size 18663 diff --git a/raw/rel-18/29_series/29336/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29336/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab59340b5c11d22d51f85b5dbbb62af0e0b2df96 --- /dev/null +++ b/raw/rel-18/29_series/29336/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6085ab8b0d5564a4e15de551ba72ded529e528abc3327cce7e22af5bf387fa7 +size 9656 diff --git a/raw/rel-18/29_series/29336/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29336/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48283abdd2b35d1b7e4a8350252750d8fc2dcad6 --- /dev/null +++ b/raw/rel-18/29_series/29336/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fee9319181e7c4638be29ce69f78a39875576c6377ed8de23269e6cc0646fe71 +size 5738 diff --git a/raw/rel-18/29_series/29336/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/raw/rel-18/29_series/29336/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bef4ed520c6dc81bcbd37227cfd3acd7d4aa9b5 --- /dev/null +++ b/raw/rel-18/29_series/29336/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65c99b017e9e272e6ec98cd056c6ab39cf10ab7c8ff3f3771908773ace12e1ce +size 66205 diff --git a/raw/rel-18/29_series/29338/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29338/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa0f6162392f63b9c580768362593fd197d9d369 --- /dev/null +++ b/raw/rel-18/29_series/29338/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:596516b4810641ea56ec4a55491e55e3330af1f819795cc43955c3b6ab9a19b3 +size 9520 diff --git a/raw/rel-18/29_series/29338/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29338/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea2f0e77465a5e5bba9492dfd5a294d37c542738 --- /dev/null +++ b/raw/rel-18/29_series/29338/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f58cc7de156266f341ca75f4ebaa9fe009bf423563e64a9f5e26029bed893f58 +size 5629 diff --git a/raw/rel-18/29_series/29413/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29413/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adf37a3ac12b21d23f8b0e33a122ce2b320e21ac --- /dev/null +++ b/raw/rel-18/29_series/29413/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e26c04424e25e72decbc6c5085aabdfce97d16b5b5647f88e6562cec1b3a62a +size 9556 diff --git a/raw/rel-18/29_series/29413/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29413/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..048cca521772e16f670ecbe52ba38123384d73ec --- /dev/null +++ b/raw/rel-18/29_series/29413/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6776e9c77c0f64f470fa40a62ddda0157de8ffb3f588de21820aea3061d9496b +size 5687 diff --git a/raw/rel-18/29_series/29502/1033dc9fde75540d224c907681b1b7aa_img.jpg b/raw/rel-18/29_series/29502/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9b943e12af16418281a49f9ef62e889eccb61cf --- /dev/null +++ b/raw/rel-18/29_series/29502/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c8c23aad73389c5fb9bb0623717d5deb70c19eb3c2c3bdd5d920ebe2b6051da +size 36770 diff --git a/raw/rel-18/29_series/29502/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/raw/rel-18/29_series/29502/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c110330a2ba2b716f6086d89bb6c840563dc051f --- /dev/null +++ b/raw/rel-18/29_series/29502/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa7fde26072fb9a3f256167ba752aac91bf6c1746f7758875963704bee3c6b2c +size 13320 diff --git a/raw/rel-18/29_series/29502/11f18bf0233d812ad2604f88f3385d60_img.jpg b/raw/rel-18/29_series/29502/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef3f0c73cb60958eb1e06ea84a5ba861bb8effbc --- /dev/null +++ b/raw/rel-18/29_series/29502/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c43bbacf9bd93c2301eead22b03908a21971ef40bacdde4ff9db6733e6e15b2c +size 41598 diff --git a/raw/rel-18/29_series/29502/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/raw/rel-18/29_series/29502/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90392f58af77ce0cced41879bbaf0b15e024b4da --- /dev/null +++ b/raw/rel-18/29_series/29502/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dceb90408f9811d8ab51913d0f96f4a8633f3bdac08b7df7c7b78aa38085e7d9 +size 13309 diff --git a/raw/rel-18/29_series/29502/21327313f7b18a481da0c87a6472a80d_img.jpg b/raw/rel-18/29_series/29502/21327313f7b18a481da0c87a6472a80d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5250efe1fe9378c44fe15457baf1317224a590b --- /dev/null +++ b/raw/rel-18/29_series/29502/21327313f7b18a481da0c87a6472a80d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c5d23df2c673257eaa6f69bea66a3d19707ed3cd2c658563dd7f5496d70404a +size 45266 diff --git a/raw/rel-18/29_series/29502/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/raw/rel-18/29_series/29502/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b50feae1e8c08bb87423c278b1879a1f022b02f1 --- /dev/null +++ b/raw/rel-18/29_series/29502/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cfe2a5e96db989a6bd81b132c0e7f81cf5288a9b27e757f4dcff9e05e9676f8 +size 37748 diff --git a/raw/rel-18/29_series/29502/2f587210e4f97c32758c5972e2e83d20_img.jpg b/raw/rel-18/29_series/29502/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde44470cc6ace8973de097dea4a3bc86cf28e8b --- /dev/null +++ b/raw/rel-18/29_series/29502/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bd6da357024b5fc70f3fd61158354b64ec55c0443f4190ec39694812db7c859 +size 69688 diff --git a/raw/rel-18/29_series/29502/303fadfb9def251d1575d6221199b158_img.jpg b/raw/rel-18/29_series/29502/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46ab89a08e3b532c68ed2b21456fbf8db4d74c03 --- /dev/null +++ b/raw/rel-18/29_series/29502/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe6ebab628fb4f84b4dfb669801bf1cf1160dced6c1ceb8c0ff2f5c1038f9e8b +size 56409 diff --git a/raw/rel-18/29_series/29502/333992a0b3b7a9d826f72f7bf199221b_img.jpg b/raw/rel-18/29_series/29502/333992a0b3b7a9d826f72f7bf199221b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0d69e9fe904c0336ab5b8782c295932f8d41e9 --- /dev/null +++ b/raw/rel-18/29_series/29502/333992a0b3b7a9d826f72f7bf199221b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3765b1fb44c975c390d3f2bef2fd7e244aa1d2f4ea0eff949df3930422bb3504 +size 39076 diff --git a/raw/rel-18/29_series/29502/384ca4ed072674dbb16642cd334b1c15_img.jpg b/raw/rel-18/29_series/29502/384ca4ed072674dbb16642cd334b1c15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53a77a5f289b345596e1aa56374a790f89996e6c --- /dev/null +++ b/raw/rel-18/29_series/29502/384ca4ed072674dbb16642cd334b1c15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a5487d50a73e4acc665cb0369badc9ff2f76a1ea6d0b414bc13ab80cfab12e +size 42189 diff --git a/raw/rel-18/29_series/29502/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/raw/rel-18/29_series/29502/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d29f52c687e3aee1fc0a0d26d8cbc89e28879713 --- /dev/null +++ b/raw/rel-18/29_series/29502/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d7aba2301fe79e14ff418a2d697c53a537eea38ef713c7a43ac7bb27dc84134 +size 44802 diff --git a/raw/rel-18/29_series/29502/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/raw/rel-18/29_series/29502/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74fb3a9c7711232050badfde0f280f122f4b70fe --- /dev/null +++ b/raw/rel-18/29_series/29502/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f02496fecf404d27868ebbd39cb521315b745a1b2d42e0b921454978032275c +size 48079 diff --git a/raw/rel-18/29_series/29502/4356776ca004ecba5d599667a155d7d4_img.jpg b/raw/rel-18/29_series/29502/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d5eee8df7f3be454a53bfb6dcae7ce112433c71 --- /dev/null +++ b/raw/rel-18/29_series/29502/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcdf4c8dca1441f2f07d6fa0efa8fd95715065ec3505e2a9be98f0f22a1cbaeb +size 12683 diff --git a/raw/rel-18/29_series/29502/4aeaa51a3999fab21171224e238cb571_img.jpg b/raw/rel-18/29_series/29502/4aeaa51a3999fab21171224e238cb571_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fca61d58f4ecbd883a6ae3ca01c181964835a1f7 --- /dev/null +++ b/raw/rel-18/29_series/29502/4aeaa51a3999fab21171224e238cb571_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bda5b6fc2aeac64b684db5f37039ee26560f4b94c8e8984a93d2330c77f12c2 +size 44919 diff --git a/raw/rel-18/29_series/29502/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/raw/rel-18/29_series/29502/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba56b86d1b250cec3b1d7d9b5f18e6237bf072e --- /dev/null +++ b/raw/rel-18/29_series/29502/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:970c5d7d45a11a0ca58dd7a63ca77e7350ef5cc1c4d87df681466dde61bbbca9 +size 39438 diff --git a/raw/rel-18/29_series/29502/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg b/raw/rel-18/29_series/29502/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..729c27d8505f4715a4e3914885f10eb8942dc794 --- /dev/null +++ b/raw/rel-18/29_series/29502/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1662d0a4520e39d15cd0d8ec21c0a79b3ac6819041e9e008cd31e7314339e12f +size 39804 diff --git a/raw/rel-18/29_series/29502/507e8bc710c80563f5ee9e2f0ebb603d_img.jpg b/raw/rel-18/29_series/29502/507e8bc710c80563f5ee9e2f0ebb603d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e06ae8e60aca9d37c29e78321607a1aa13f590dc --- /dev/null +++ b/raw/rel-18/29_series/29502/507e8bc710c80563f5ee9e2f0ebb603d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb1057ca2dc2944238590c219380efed7fea5cec52c50a0ee099b8f17720470 +size 45507 diff --git a/raw/rel-18/29_series/29502/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg b/raw/rel-18/29_series/29502/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b589ba48b011d7018123c73a0e24257872b43e2 --- /dev/null +++ b/raw/rel-18/29_series/29502/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b555d4e9f4ec10b3398d6e9091d1b7cd8ce3cdcf61fa886b4773c952933cc3e5 +size 33328 diff --git a/raw/rel-18/29_series/29502/5e9af8986a5845504f251d3079da8078_img.jpg b/raw/rel-18/29_series/29502/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47180acbe4e38871a7a526af8a5c8f48f495140b --- /dev/null +++ b/raw/rel-18/29_series/29502/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9dc5152bf97256fd3b622e0d0a26661c93c3a8a89ef34ef67d3a22cd0403234 +size 45416 diff --git a/raw/rel-18/29_series/29502/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29502/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9001c357b301a8104f7286cc2ba4b66ad787fd24 --- /dev/null +++ b/raw/rel-18/29_series/29502/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6dd0c083aa207fff37744dadf097e8acaa000137fc2b3810f18c75881be9bcd +size 9594 diff --git a/raw/rel-18/29_series/29502/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29502/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9faeb1b34650f4b95d3e98209314bbbd517e16b0 --- /dev/null +++ b/raw/rel-18/29_series/29502/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13bcea13c5ffa7dfa11d1d82c133c14c162babbbd5530e71a22c2ae9d9d931e7 +size 5493 diff --git a/raw/rel-18/29_series/29502/678ac9faaa56bb929499cebeea83a110_img.jpg b/raw/rel-18/29_series/29502/678ac9faaa56bb929499cebeea83a110_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da7ae53ea991cd7c55ae59d871986620a054972f --- /dev/null +++ b/raw/rel-18/29_series/29502/678ac9faaa56bb929499cebeea83a110_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5be5bac378df8fc9b7c106a283cccfd271c64eec42273608ea1f4db6a87f721 +size 10719 diff --git a/raw/rel-18/29_series/29502/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/raw/rel-18/29_series/29502/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bab60da49fb965b64c5f43087fd59499ae376dcf --- /dev/null +++ b/raw/rel-18/29_series/29502/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83356e87ea020644cb612f0dfeabd156d2aca7015d771ada560753ef9ff72544 +size 42537 diff --git a/raw/rel-18/29_series/29502/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/raw/rel-18/29_series/29502/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62ef6bf680632861e137bb259eb40e49640e2954 --- /dev/null +++ b/raw/rel-18/29_series/29502/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74a62b9caf3815024fd9ad6f95907fcb989e98e6492acca479b1ccb2e1710ad8 +size 36283 diff --git a/raw/rel-18/29_series/29502/78de09c382ab51b5c3e87979204228c8_img.jpg b/raw/rel-18/29_series/29502/78de09c382ab51b5c3e87979204228c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1da8abfd58e6b8ef68d62d333cd5dfa0f9dcb4ec --- /dev/null +++ b/raw/rel-18/29_series/29502/78de09c382ab51b5c3e87979204228c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3427231d0d7527886380d7c14cdafdde46aa38bfcd04a84e9174062ae5f654e +size 53569 diff --git a/raw/rel-18/29_series/29502/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/raw/rel-18/29_series/29502/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..113bf98bb7505d95f6d80f07a59f2c835c5d5ccd --- /dev/null +++ b/raw/rel-18/29_series/29502/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3e27d62107a549411a61cb4133c09874b0dde473e9b188604a550947ed4883c +size 33919 diff --git a/raw/rel-18/29_series/29502/7ede87328f6b696dcffa65ebc4570cc8_img.jpg b/raw/rel-18/29_series/29502/7ede87328f6b696dcffa65ebc4570cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99a352ae96863b0dd50997aa88360ce5a8fab998 --- /dev/null +++ b/raw/rel-18/29_series/29502/7ede87328f6b696dcffa65ebc4570cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9af5cac410a1e390d991b0644648b0a5e38626b807ffc387971107dc834e2d4d +size 57643 diff --git a/raw/rel-18/29_series/29502/8269648391c59363ea61243864a2adf7_img.jpg b/raw/rel-18/29_series/29502/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb394fd9f21913e3e81a0cc5eadf2b9a7f764e88 --- /dev/null +++ b/raw/rel-18/29_series/29502/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09b6c4b916ab766793f4b50d47bbb8b18ec26e30ede825ab4e711f20f5a34b5b +size 58176 diff --git a/raw/rel-18/29_series/29502/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/raw/rel-18/29_series/29502/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fa5fd6a84c912ad890ce8944d7467adb75bcdea --- /dev/null +++ b/raw/rel-18/29_series/29502/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f4887faa8d306510354e0a1919e97c59a540e8bf86a2dcbccf0ec22229e5690 +size 37103 diff --git a/raw/rel-18/29_series/29502/87b70d2e8951032d28b4412d82cf1413_img.jpg b/raw/rel-18/29_series/29502/87b70d2e8951032d28b4412d82cf1413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e088382502e2c253a77a58db4b1e0508da862a9 --- /dev/null +++ b/raw/rel-18/29_series/29502/87b70d2e8951032d28b4412d82cf1413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1e6465f9d7c5d1610372bbe7c2f8505735560a6b8654cff5c19f27ae0cfccf0 +size 41994 diff --git a/raw/rel-18/29_series/29502/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/raw/rel-18/29_series/29502/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b69d8099f9df405202eb95dff71057ebc8648d01 --- /dev/null +++ b/raw/rel-18/29_series/29502/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b534dd472c871aa4ace0fb42bf235c6d6117577b7cbb237e9b10c950e35222a6 +size 41057 diff --git a/raw/rel-18/29_series/29502/a4b963a07cc368283154762c4b156fe7_img.jpg b/raw/rel-18/29_series/29502/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4669b38e18a1e3b8e9ac2889291123d63d14e9ae --- /dev/null +++ b/raw/rel-18/29_series/29502/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1b7e527bd3d81f69f37220167c652183e081b6e65195d23dc033e9ce466a3fb +size 13985 diff --git a/raw/rel-18/29_series/29502/a4c8a0374a5b7405a4cdbb6906a2a750_img.jpg b/raw/rel-18/29_series/29502/a4c8a0374a5b7405a4cdbb6906a2a750_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e9c4206bff1ce671cf5f297ab492fc8f96c71cf --- /dev/null +++ b/raw/rel-18/29_series/29502/a4c8a0374a5b7405a4cdbb6906a2a750_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4625259004f8bf73e832203c899e788799cec9f9f6b020edb39e985a2b9ac40b +size 45432 diff --git a/raw/rel-18/29_series/29502/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/raw/rel-18/29_series/29502/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed2c6b0bad52acf364616bcc5e16f553e5a3620a --- /dev/null +++ b/raw/rel-18/29_series/29502/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89cd213a73ca69231a862ec407c4fb84b4fb9771bf080418fdf0cd292093b832 +size 32931 diff --git a/raw/rel-18/29_series/29502/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/raw/rel-18/29_series/29502/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfc3b5c60a37c94399df7d50c9a9a08ed8e42746 --- /dev/null +++ b/raw/rel-18/29_series/29502/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc41b873e1557c0be9f6484a742ecf788d98d5828e2492fcd21ed98379dcca88 +size 46288 diff --git a/raw/rel-18/29_series/29502/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg b/raw/rel-18/29_series/29502/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db605ff1989261a98847a561c3c07bfc39c17710 --- /dev/null +++ b/raw/rel-18/29_series/29502/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dcc0edf612d08580bec6fcfc99399dc5d0763fea03567d753914898363cd5f3 +size 42852 diff --git a/raw/rel-18/29_series/29502/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/raw/rel-18/29_series/29502/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9642aa828c1c5998851bcaf1b56cbf02672d343c --- /dev/null +++ b/raw/rel-18/29_series/29502/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:914cce47900e6173cc28c74ef29c0d6ea7b8bea9d417bb619daccac0281015da +size 36547 diff --git a/raw/rel-18/29_series/29502/d116934392360da963e91d840d1e45a8_img.jpg b/raw/rel-18/29_series/29502/d116934392360da963e91d840d1e45a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c83a84fbbe189007fbe1b9b2562a75090084220f --- /dev/null +++ b/raw/rel-18/29_series/29502/d116934392360da963e91d840d1e45a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97cd50dff0ef370d43ef142bc3300f8e0d85281415ed046f1b930165b159ccde +size 28602 diff --git a/raw/rel-18/29_series/29502/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/raw/rel-18/29_series/29502/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06142ea73882a77ed68fd27bb286009d01166f0f --- /dev/null +++ b/raw/rel-18/29_series/29502/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dfa268034fb8b24e645b1509ed9efe6a4d8c5160daaf31d077e1e72769a6f85 +size 59694 diff --git a/raw/rel-18/29_series/29502/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/raw/rel-18/29_series/29502/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e571fe5aaa30e2e0a6c6d125b587bda203fbf9 --- /dev/null +++ b/raw/rel-18/29_series/29502/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9eaddfba22c49cdf0a87a806766c554d345cd7a6dc056618acc266ec394afc2 +size 39628 diff --git a/raw/rel-18/29_series/29502/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/raw/rel-18/29_series/29502/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71da5745bf3ca6d313219b361dcd9fc4876e0ee1 --- /dev/null +++ b/raw/rel-18/29_series/29502/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea496dff7a06a8499be86d7e641550dce6fa0c149b6c910f61cf5c4ec9a3e5d2 +size 48723 diff --git a/raw/rel-18/29_series/29502/e38206fcefa2045af01d494b2956775a_img.jpg b/raw/rel-18/29_series/29502/e38206fcefa2045af01d494b2956775a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4440b52c7b6507f26e376ae9d60a94a6c7bd185e --- /dev/null +++ b/raw/rel-18/29_series/29502/e38206fcefa2045af01d494b2956775a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ec3c439f554ed27845d98f9066b3b87e68068ca83adf751bd41aab2575dac24 +size 84409 diff --git a/raw/rel-18/29_series/29502/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/raw/rel-18/29_series/29502/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c50575323a2fcad7b1b7ba123af01b3c3c302f25 --- /dev/null +++ b/raw/rel-18/29_series/29502/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85eb6c5326114750c7f98c259e4e0659797504cfe358f565416af1ed85a91907 +size 36829 diff --git a/raw/rel-18/29_series/29502/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/raw/rel-18/29_series/29502/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56be2e87720a35315d0a6ac62418d77ea2783e3e --- /dev/null +++ b/raw/rel-18/29_series/29502/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca4dcb1087e2ac67ca0b7272798774675852ac51abb349e1c9e0d555ad3287d6 +size 70348 diff --git a/raw/rel-18/29_series/29502/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/raw/rel-18/29_series/29502/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc54083771f64b4478d545b5a0f1f3869ea18fae --- /dev/null +++ b/raw/rel-18/29_series/29502/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52eb53b9dbeea12e7ff8ecc3ab2c080b6f90c4a924ddd8f924c7471f9b3800df +size 41927 diff --git a/raw/rel-18/29_series/29503/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/raw/rel-18/29_series/29503/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5982bfdbfdf18f44dcdc23e7fa98b453e21505f5 --- /dev/null +++ b/raw/rel-18/29_series/29503/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dd39b74a2cfc6672faace3729cac9fd5c426d39ab9a8adb3acb4038df9d12b3 +size 34852 diff --git a/raw/rel-18/29_series/29503/062ad684575a714449a7e040c0e1ec00_img.jpg b/raw/rel-18/29_series/29503/062ad684575a714449a7e040c0e1ec00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01aea7ae65659af9f547172961d89fa1298debe8 --- /dev/null +++ b/raw/rel-18/29_series/29503/062ad684575a714449a7e040c0e1ec00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90890f51648e57b5d301ae1774be4308c942d971da0b1009e3485b88365f8014 +size 47587 diff --git a/raw/rel-18/29_series/29503/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/raw/rel-18/29_series/29503/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e4d705d9ceeb8c616ce323b4b541aa413ec46de --- /dev/null +++ b/raw/rel-18/29_series/29503/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0f0e862c0a7e3425d8d715f1b2fe84349c0aa8ef5ff5c50df1ba592530827d8 +size 13454 diff --git a/raw/rel-18/29_series/29503/0a83cda688278bb05ef5134e66bdaf6e_img.jpg b/raw/rel-18/29_series/29503/0a83cda688278bb05ef5134e66bdaf6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f76a6d6244fcdc378ac23d9ac0ebdf0b16c1f1a --- /dev/null +++ b/raw/rel-18/29_series/29503/0a83cda688278bb05ef5134e66bdaf6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e71219a5dec8c8c56a2c256c9ba4014fdf87eed2dd04d6e8d81bc0d1116f5a0c +size 16489 diff --git a/raw/rel-18/29_series/29503/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/raw/rel-18/29_series/29503/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e12c2a334d55aecb06d7f0bcc8be978d43312ea3 --- /dev/null +++ b/raw/rel-18/29_series/29503/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae95ff64e71aa971a8b6037d59354375b3900afa541b9bbb0b00827bd16b35db +size 34333 diff --git a/raw/rel-18/29_series/29503/0c9723d1620cf51bc2b7a380ce7e23c0_img.jpg b/raw/rel-18/29_series/29503/0c9723d1620cf51bc2b7a380ce7e23c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e019225cace027b969b97df9635aceda75cdba11 --- /dev/null +++ b/raw/rel-18/29_series/29503/0c9723d1620cf51bc2b7a380ce7e23c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3f0512c5d76aed34de2a43362651f6b98a6dd2efd0c85faf98a7c9b13b40f5d +size 38610 diff --git a/raw/rel-18/29_series/29503/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/raw/rel-18/29_series/29503/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..505a72f0dfcac9dc7d0396d841f04abf1dfad301 --- /dev/null +++ b/raw/rel-18/29_series/29503/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50e61a974b4f6747940715fa7757e67ecbfee43da8b96edd134e343a782797f6 +size 26940 diff --git a/raw/rel-18/29_series/29503/14515d82ffeec9475b9add3036ff26ab_img.jpg b/raw/rel-18/29_series/29503/14515d82ffeec9475b9add3036ff26ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827aee6a0152815036f6f5a66507133ecaf506e2 --- /dev/null +++ b/raw/rel-18/29_series/29503/14515d82ffeec9475b9add3036ff26ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86cb79f19da3b1c9c8d43a55b0736fb01d44993d62b58116f7b4ba437f1db85e +size 29270 diff --git a/raw/rel-18/29_series/29503/16152cf1d84aea10848758f51a91ff6a_img.jpg b/raw/rel-18/29_series/29503/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d38777b3680474f1a39765a589fc55a5e90f551 --- /dev/null +++ b/raw/rel-18/29_series/29503/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14dbd817fefcdec8b856428809d1f64580deef044d6dcbd5493362fbb1f3ce19 +size 63010 diff --git a/raw/rel-18/29_series/29503/171115f072e42b379238ed0dd438e9d7_img.jpg b/raw/rel-18/29_series/29503/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66b27b01fcb3acba8326d91e411060c0412d3cb7 --- /dev/null +++ b/raw/rel-18/29_series/29503/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3977381bf5c614b8ebb84ee0022d59ec7ec0d230c8a78a898a2f3e9cb035f75 +size 28331 diff --git a/raw/rel-18/29_series/29503/1878426572e3fcbc4483578a685d7c7d_img.jpg b/raw/rel-18/29_series/29503/1878426572e3fcbc4483578a685d7c7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab3e0b67cd57c352fdbe62670fb6fb6c9de31544 --- /dev/null +++ b/raw/rel-18/29_series/29503/1878426572e3fcbc4483578a685d7c7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef4fe7866d34fd2c8fda0acd483473de60945e7257bb51b522d058c3b377de13 +size 24507 diff --git a/raw/rel-18/29_series/29503/19d7a7ce68d3e9036613910b761c4b24_img.jpg b/raw/rel-18/29_series/29503/19d7a7ce68d3e9036613910b761c4b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18c917e23a041f3531e37b849f14c3706f3367a8 --- /dev/null +++ b/raw/rel-18/29_series/29503/19d7a7ce68d3e9036613910b761c4b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45502a288afecfd1f8dbfe176413c217f7b6693075dfb93d482f882eaa20182c +size 37001 diff --git a/raw/rel-18/29_series/29503/1c29dadab94c3fa552d270434db09c81_img.jpg b/raw/rel-18/29_series/29503/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5609902870d42217f9bc9bc38f0d59029dcb2b1a --- /dev/null +++ b/raw/rel-18/29_series/29503/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:895a362b9dd52fba1d12673f6d8b4707a3ea69932452d3d932387c1913f207ec +size 29100 diff --git a/raw/rel-18/29_series/29503/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/raw/rel-18/29_series/29503/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1192ff9c134a8065a8e420c417b8b624fc431d0 --- /dev/null +++ b/raw/rel-18/29_series/29503/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdcd184bfcb33fc114707574712fbb0feef93db05cd43051d562dbd4646a39cd +size 28285 diff --git a/raw/rel-18/29_series/29503/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/29_series/29503/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..683d656fd86d501e66071e83ba3572412c23806e --- /dev/null +++ b/raw/rel-18/29_series/29503/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a33cb82a48489c9a2f1a6119ea19e32df2f1fe1e61c5e110a53c837dd739dd67 +size 35062 diff --git a/raw/rel-18/29_series/29503/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/raw/rel-18/29_series/29503/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b683017f610c3a63ac8d16655f8eb0bf24ccc80c --- /dev/null +++ b/raw/rel-18/29_series/29503/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d4b3973c8c727b5771f72ffbc1c164adeee895544c11be44e853a0c55877d6c +size 30260 diff --git a/raw/rel-18/29_series/29503/2aa94b70ba3fadcba8420d9e3128253a_img.jpg b/raw/rel-18/29_series/29503/2aa94b70ba3fadcba8420d9e3128253a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67937134e0361bf9736ff77172e4583e9431e900 --- /dev/null +++ b/raw/rel-18/29_series/29503/2aa94b70ba3fadcba8420d9e3128253a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a028c4d518a2bb494709363b479c5ea49243363c43e6c35fcc9561721d991b97 +size 28799 diff --git a/raw/rel-18/29_series/29503/2dfd7b53bd3c518fc1f68921ed2bf441_img.jpg b/raw/rel-18/29_series/29503/2dfd7b53bd3c518fc1f68921ed2bf441_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e460ea53b1c9a29335bd76db7f4f6e9b320f828 --- /dev/null +++ b/raw/rel-18/29_series/29503/2dfd7b53bd3c518fc1f68921ed2bf441_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6941400c0049e566ccabda941ce43d9ea9363302bdec6753759607adcd2c345 +size 36160 diff --git a/raw/rel-18/29_series/29503/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/raw/rel-18/29_series/29503/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a422a12f48ecb1aebf8005218b838a5b0a745c86 --- /dev/null +++ b/raw/rel-18/29_series/29503/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49426b76ad14b672892ba5c8440582df7dd82e729d0e33dc75a312d374b6b8f6 +size 30331 diff --git a/raw/rel-18/29_series/29503/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/raw/rel-18/29_series/29503/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bd64982420d1604440c20e61258c081b73eee21 --- /dev/null +++ b/raw/rel-18/29_series/29503/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:277cafb1507b66f16a802369bb7a9025b9732b8d48fbdcdaf2eec5b2d7bc6241 +size 26375 diff --git a/raw/rel-18/29_series/29503/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/raw/rel-18/29_series/29503/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8839550cd8692855026e5eabf42d2ba98a5c8a1c --- /dev/null +++ b/raw/rel-18/29_series/29503/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f41411e5e628811ded21378d8d113395f7449050b48ef97a3f36d0cddba5d5c5 +size 27954 diff --git a/raw/rel-18/29_series/29503/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/raw/rel-18/29_series/29503/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fe642fea73446539b5527a0aa0c3e13629b8e6c --- /dev/null +++ b/raw/rel-18/29_series/29503/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a97be32e3da765ffbff70317e99505166b63a2fbbda01c094657d138b62470f4 +size 29086 diff --git a/raw/rel-18/29_series/29503/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/raw/rel-18/29_series/29503/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24faacb16bc56d6d8a583348793ee7779d3f70d5 --- /dev/null +++ b/raw/rel-18/29_series/29503/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85e4ea95330037b35407ec16ae9bc00c45d7bcdb850599fcc3edac863f147bd0 +size 28350 diff --git a/raw/rel-18/29_series/29503/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/raw/rel-18/29_series/29503/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fe75a652bc621bf6a7befc9d1c8b65befe5663f --- /dev/null +++ b/raw/rel-18/29_series/29503/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:527c47f6fa7255a00d055e65cea6a1d52d1c8311b7d46f6752c71e4123f7fa7b +size 35079 diff --git a/raw/rel-18/29_series/29503/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/raw/rel-18/29_series/29503/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55fd95b50cbe48add559ad5f3611a7e2c8e897a5 --- /dev/null +++ b/raw/rel-18/29_series/29503/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:236d111dfb3402fbe07d584e588b74c241bc05565f2c2a0906bd73c36fe0ae64 +size 31135 diff --git a/raw/rel-18/29_series/29503/410562339ce067fdc6fa41940c118658_img.jpg b/raw/rel-18/29_series/29503/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ec6e67245a45993ce4b4c25634b747d065a75a9 --- /dev/null +++ b/raw/rel-18/29_series/29503/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a659d867941cde127b8831e1c699cdf7f04357e9302b55aff736eb8a52e887e3 +size 27876 diff --git a/raw/rel-18/29_series/29503/47e8c2042061e08a14e012472e9fdbaa_img.jpg b/raw/rel-18/29_series/29503/47e8c2042061e08a14e012472e9fdbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..444faf60cbc132dc6bb1b66656716fb0fc955c49 --- /dev/null +++ b/raw/rel-18/29_series/29503/47e8c2042061e08a14e012472e9fdbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62d1bc66d996b49e59b5ca7e5304a430364321a9d5d65d82db5fa07b5d2f136d +size 34481 diff --git a/raw/rel-18/29_series/29503/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/raw/rel-18/29_series/29503/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f708264bcb6f656fab7f782bef09a5035fd5ab1b --- /dev/null +++ b/raw/rel-18/29_series/29503/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12e6223150b5ff1f10d84be87cfffee6502fa7fee62202455119a793bd7a9c12 +size 29257 diff --git a/raw/rel-18/29_series/29503/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/raw/rel-18/29_series/29503/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23bdae4bc647576c83f07770118e135296d3c607 --- /dev/null +++ b/raw/rel-18/29_series/29503/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57964e2b73b49d1271d31d368d88d12a84ebcb7d1d8ca1ab136838a81d4dd13f +size 27986 diff --git a/raw/rel-18/29_series/29503/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/raw/rel-18/29_series/29503/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f00091de828f70204ccacb3eb348476035242e0 --- /dev/null +++ b/raw/rel-18/29_series/29503/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e362641870b601690709f29b26497713bd67f062633666dcca4dd5efaa5914da +size 27127 diff --git a/raw/rel-18/29_series/29503/5837d4aa3bb1d08bbebcd757248f5515_img.jpg b/raw/rel-18/29_series/29503/5837d4aa3bb1d08bbebcd757248f5515_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7f3199a44cd3db15ce23beaa506330077ccab65 --- /dev/null +++ b/raw/rel-18/29_series/29503/5837d4aa3bb1d08bbebcd757248f5515_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80aad2dc407f1bf0e5db18f01cad500ddaeba1829ee15fd360559a4f743d8d2d +size 34795 diff --git a/raw/rel-18/29_series/29503/5879500ca01e1a2521654beff6c289a4_img.jpg b/raw/rel-18/29_series/29503/5879500ca01e1a2521654beff6c289a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d5ada41f7d3e5470cd87cc4a73ab60befb4bb08 --- /dev/null +++ b/raw/rel-18/29_series/29503/5879500ca01e1a2521654beff6c289a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55553fd7bedf8b9f1df425ee80ca41cb779ad16dee4730964fa8185aca118714 +size 34764 diff --git a/raw/rel-18/29_series/29503/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29503/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..982dd7904f77211a20fb2ff3d04c1fb791541092 --- /dev/null +++ b/raw/rel-18/29_series/29503/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fcdcff65847eccaf5bd4f81d3237aa9337fdeb7af1ad4c0c2646e37145e70fb +size 9812 diff --git a/raw/rel-18/29_series/29503/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/raw/rel-18/29_series/29503/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aa932dcf183c386419e50e93d5708154c3e2de6 --- /dev/null +++ b/raw/rel-18/29_series/29503/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf4d7be8c47c5e3f1678a4d5363d178bd1f9afa3503b53a61caa0dce78bc99fc +size 28050 diff --git a/raw/rel-18/29_series/29503/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29503/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5c196cd8dfa3feb1aa5a148aab3f55f445cbda1 --- /dev/null +++ b/raw/rel-18/29_series/29503/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1121f70c6ab5be33e4a1e6f72e905528f1192e3517d0869aa8950ff922b58a2b +size 5634 diff --git a/raw/rel-18/29_series/29503/659a041a7997f9eea79f4e2f3ba265a5_img.jpg b/raw/rel-18/29_series/29503/659a041a7997f9eea79f4e2f3ba265a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54181f56065b53146c76755cb112dce5ab7508ac --- /dev/null +++ b/raw/rel-18/29_series/29503/659a041a7997f9eea79f4e2f3ba265a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af8d83725df38cc844bb1a662307af663ec9326cf83bceaafd94c009b1e07516 +size 30362 diff --git a/raw/rel-18/29_series/29503/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/raw/rel-18/29_series/29503/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..289ffe238f969b1d10c4c088b8984d19422b52dd --- /dev/null +++ b/raw/rel-18/29_series/29503/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad633b93bf4f503eab63504d9c325a972569bae3df45b8f7c6c3e7aad66a5b30 +size 7323 diff --git a/raw/rel-18/29_series/29503/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/raw/rel-18/29_series/29503/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c11fe8c44b03a561795fac09e653770c671f7b65 --- /dev/null +++ b/raw/rel-18/29_series/29503/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7dc7c35f3914aa72d6aa064417c3967250d46f834ba7b19c528ce1fa10a2c4 +size 33748 diff --git a/raw/rel-18/29_series/29503/6757222e979ee95c44354a897c5cc1c1_img.jpg b/raw/rel-18/29_series/29503/6757222e979ee95c44354a897c5cc1c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..570f47bdfbaa43126dfce940490a9048944f09f2 --- /dev/null +++ b/raw/rel-18/29_series/29503/6757222e979ee95c44354a897c5cc1c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6e36c253cd5d0056e2cea431f4ee88b24cf46193193fe2a2e7d9fd688f5e845 +size 33184 diff --git a/raw/rel-18/29_series/29503/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg b/raw/rel-18/29_series/29503/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffd2788db99dd375d5683b1746b003de30d03157 --- /dev/null +++ b/raw/rel-18/29_series/29503/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b9bac2228cbd259e325a4aec8a20bc008fc7571087c86f39d54e7359abf2380 +size 27837 diff --git a/raw/rel-18/29_series/29503/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/raw/rel-18/29_series/29503/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f9cbf52dfb1cbc7f64a78cb686a76c4a97c938c --- /dev/null +++ b/raw/rel-18/29_series/29503/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:681cd26f55c81656569566b19704d6aaccaaca4474c76517d2f3dbef79fbbc5a +size 29001 diff --git a/raw/rel-18/29_series/29503/69edc2887e907309499ac95b47ab6905_img.jpg b/raw/rel-18/29_series/29503/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95e8de49b4239a721e56190b55ca24f4a9b43295 --- /dev/null +++ b/raw/rel-18/29_series/29503/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd10ab5a5b934cf7940d7ea850717ba4d29e18b6f09ae12eafaf421f0048e527 +size 40737 diff --git a/raw/rel-18/29_series/29503/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/raw/rel-18/29_series/29503/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..532e94cd31d7f51171691045ca6cdb2f9ca50f86 --- /dev/null +++ b/raw/rel-18/29_series/29503/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8b8d9823bede418a3a69844bfe741f44a84597c20e1e3921714991d6bd6309c +size 30030 diff --git a/raw/rel-18/29_series/29503/6e612452d995bb03cc3f3d004493f7bf_img.jpg b/raw/rel-18/29_series/29503/6e612452d995bb03cc3f3d004493f7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ce57c11b2be163624b2be7acc4d5d08fbd61488 --- /dev/null +++ b/raw/rel-18/29_series/29503/6e612452d995bb03cc3f3d004493f7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b7dccec4b55f3068b80436e22a5b86bff409d53b4e38211b73c350c751d7788 +size 34108 diff --git a/raw/rel-18/29_series/29503/6f659142d4789aa889184459f884787e_img.jpg b/raw/rel-18/29_series/29503/6f659142d4789aa889184459f884787e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8436287e0e0ce8d240aeef323bd93a4aeae94c73 --- /dev/null +++ b/raw/rel-18/29_series/29503/6f659142d4789aa889184459f884787e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a565bc8d2a72f0fa9c67190256a4b0765842959da79baf328729527c97d8d4b +size 46128 diff --git a/raw/rel-18/29_series/29503/6ff6e507698d693fcd1ae210ac1ab954_img.jpg b/raw/rel-18/29_series/29503/6ff6e507698d693fcd1ae210ac1ab954_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acb2c312215f22294e737c758743e3b7caa730f1 --- /dev/null +++ b/raw/rel-18/29_series/29503/6ff6e507698d693fcd1ae210ac1ab954_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcad5dc7c7652cd602f1193df5276a95bc8307034c898f11c69cae31df695f0c +size 35306 diff --git a/raw/rel-18/29_series/29503/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/raw/rel-18/29_series/29503/70de8885bd7de15723aaad5eb5c5febf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2236b77a8c906add008f8276f71fe991d546b6d2 --- /dev/null +++ b/raw/rel-18/29_series/29503/70de8885bd7de15723aaad5eb5c5febf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a7fa068f429321cc452f1eeeec182de67a29a5fdc9ffd60fe1360f1557e86e5 +size 31391 diff --git a/raw/rel-18/29_series/29503/718be1eb075833deb7a3b80729a06264_img.jpg b/raw/rel-18/29_series/29503/718be1eb075833deb7a3b80729a06264_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..babb7bac9ba1622112c879d4a92f0eda9bdf9529 --- /dev/null +++ b/raw/rel-18/29_series/29503/718be1eb075833deb7a3b80729a06264_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a75a66ed2ed56a502df29c818aa7d6e6e58352cd5cb36d139dc326a1c49bb14 +size 35176 diff --git a/raw/rel-18/29_series/29503/731f533b0599c8e42a063f06e4332045_img.jpg b/raw/rel-18/29_series/29503/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..781fbf12a204474231645e78d48a0626869c136c --- /dev/null +++ b/raw/rel-18/29_series/29503/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:277bb4b613e3d9a7149557c896aa62a66aad48359d6cb92e46f63a818eebe777 +size 30020 diff --git a/raw/rel-18/29_series/29503/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/raw/rel-18/29_series/29503/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85f37d62255c6e271427d66c8c3f59759540a301 --- /dev/null +++ b/raw/rel-18/29_series/29503/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d148b4f03660ea0fd6c5e5118204a87f775f6544f9f419f97e522b0447ae38a +size 30143 diff --git a/raw/rel-18/29_series/29503/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/raw/rel-18/29_series/29503/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53a02a493d94380de12fb06c9f83c73cb484444b --- /dev/null +++ b/raw/rel-18/29_series/29503/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de45240778bf465d936c1a1d00637b9fbd5f968fffd3a0e2adcace0b3309c003 +size 32310 diff --git a/raw/rel-18/29_series/29503/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/raw/rel-18/29_series/29503/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2278cdf8f8cae3bc1f86aeaaf42cfac9d041d36e --- /dev/null +++ b/raw/rel-18/29_series/29503/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f91a5d0238e4fbafe39ae53f81e8983d704ec2f56923813db7758ef603e64ea0 +size 32470 diff --git a/raw/rel-18/29_series/29503/759c7d62402f0b4651ddce292be5bdef_img.jpg b/raw/rel-18/29_series/29503/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..762825c4b003e8284ff745c37fde0afa77ef8a0e --- /dev/null +++ b/raw/rel-18/29_series/29503/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27d0b70d1fe1cca0adfba8df060c5601f3cf12d0ad090c38cfc58e6aed20a9d6 +size 29019 diff --git a/raw/rel-18/29_series/29503/762a17cd79880dbca172bcbbe9375223_img.jpg b/raw/rel-18/29_series/29503/762a17cd79880dbca172bcbbe9375223_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3bae1c184de411c34f72e1e51ed38a792f5f6bd --- /dev/null +++ b/raw/rel-18/29_series/29503/762a17cd79880dbca172bcbbe9375223_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d5c73c15e6f145ff07b57c1da41b37d1fbfce15973109321bd838483081641 +size 32820 diff --git a/raw/rel-18/29_series/29503/772cc583a60eeb058cc19de48269ad22_img.jpg b/raw/rel-18/29_series/29503/772cc583a60eeb058cc19de48269ad22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6392a040f64d1858fbf5534b8f02086015d05a40 --- /dev/null +++ b/raw/rel-18/29_series/29503/772cc583a60eeb058cc19de48269ad22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52f4e1960d2de555ac8086b31a7f07e6e31065fed3ebc3d9f497e64d260174c2 +size 23211 diff --git a/raw/rel-18/29_series/29503/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/raw/rel-18/29_series/29503/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6fd954ac67434e9c431bb5e1a15e557f50e6919 --- /dev/null +++ b/raw/rel-18/29_series/29503/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b0e306309b0b4a169e9c0e7bfd6740b5529e5d4637ac6f7e6cfc89e04f315d1 +size 27900 diff --git a/raw/rel-18/29_series/29503/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/29_series/29503/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aca59d49f82a8bb0bcaf28495167885fd8954733 --- /dev/null +++ b/raw/rel-18/29_series/29503/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b4313f0fbb4884e652d954b87f6d23c3834abd2a0ab378b39d4b10debbddfad +size 29665 diff --git a/raw/rel-18/29_series/29503/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/raw/rel-18/29_series/29503/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ff391b18627e6be5cb21a3d6bbad1a9247941bc --- /dev/null +++ b/raw/rel-18/29_series/29503/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c82354d8dbff214a1e643e0942ab0026ae383a45880785440a305fd606e82063 +size 177487 diff --git a/raw/rel-18/29_series/29503/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/raw/rel-18/29_series/29503/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..983d250c6d3f27c532b884ae4c432bb2cfa92625 --- /dev/null +++ b/raw/rel-18/29_series/29503/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:194f1806609ad6aab8e7854d824b122982cbcfeeda11a327137df6fa924701f3 +size 34466 diff --git a/raw/rel-18/29_series/29503/8269648391c59363ea61243864a2adf7_img.jpg b/raw/rel-18/29_series/29503/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51555b359911b2ace670642c934e970e70ce8302 --- /dev/null +++ b/raw/rel-18/29_series/29503/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68e2017da56cbe4408e10889b18f09e5779d05e7c588cbed66f778f781985020 +size 19573 diff --git a/raw/rel-18/29_series/29503/82755aa51734b65461f50bf3361c8ab2_img.jpg b/raw/rel-18/29_series/29503/82755aa51734b65461f50bf3361c8ab2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a644ee38622bd48b5a5cfd3eb09136f3a7d532c8 --- /dev/null +++ b/raw/rel-18/29_series/29503/82755aa51734b65461f50bf3361c8ab2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba50e016dde354aa93a3cf7a9e4d88538244151e93f98c9dce7e1f0859d938d8 +size 9454 diff --git a/raw/rel-18/29_series/29503/82b40cb8b2a5ac361973859400fa128a_img.jpg b/raw/rel-18/29_series/29503/82b40cb8b2a5ac361973859400fa128a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78f3be9f1d92338e873c37345de1e0bc308e03fa --- /dev/null +++ b/raw/rel-18/29_series/29503/82b40cb8b2a5ac361973859400fa128a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53fd88b2b24276e84cad11c3e1b4c75daacc423f4c00b3ea5d0fd8cc63804c63 +size 29364 diff --git a/raw/rel-18/29_series/29503/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/29_series/29503/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15d60c81721d2836e2b4157e65eb530f9797ba05 --- /dev/null +++ b/raw/rel-18/29_series/29503/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a679c87b31d9f8b6622ef51f8e5a25bb37114ac803819a8acfcc280deb4eae5 +size 49764 diff --git a/raw/rel-18/29_series/29503/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/raw/rel-18/29_series/29503/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5304ba298a380d62520e1ea4eeaadda3d148943 --- /dev/null +++ b/raw/rel-18/29_series/29503/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44d0695032501e1b5e4960594259951045176def70534a3f202017e0bd2bcca8 +size 27373 diff --git a/raw/rel-18/29_series/29503/868ef3e0abb37916a7af1e923995f329_img.jpg b/raw/rel-18/29_series/29503/868ef3e0abb37916a7af1e923995f329_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54dc6b815ad98c39c587135d537710f57d2c29df --- /dev/null +++ b/raw/rel-18/29_series/29503/868ef3e0abb37916a7af1e923995f329_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:379309c2d052decfde7300917454558cb0a879c044264a51b4658de632e8a3b2 +size 30390 diff --git a/raw/rel-18/29_series/29503/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/raw/rel-18/29_series/29503/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f6e8c0c1cd133c48095b544f5c65d4cfb58d4ea --- /dev/null +++ b/raw/rel-18/29_series/29503/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1edc6d6a9c07f6987b59eb9d7a8a32c7610ebac1130446d01060b491491678fc +size 30399 diff --git a/raw/rel-18/29_series/29503/895d588a848d9963890c938763de9ecf_img.jpg b/raw/rel-18/29_series/29503/895d588a848d9963890c938763de9ecf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4efb7c0e43ea5a5f5ae12409e805f4532ad12f6d --- /dev/null +++ b/raw/rel-18/29_series/29503/895d588a848d9963890c938763de9ecf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5decff218497023b113938db349caccf04133b20296d6ceba63059729755af44 +size 41056 diff --git a/raw/rel-18/29_series/29503/896e86ed12aff206d302c64f2e3091fa_img.jpg b/raw/rel-18/29_series/29503/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10c55d2464a044801750dc9b297661ccac6ff87b --- /dev/null +++ b/raw/rel-18/29_series/29503/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de5d44b0586c0d622ecdb04c76a15f70636e37dcc383f99f17b91319705c89e1 +size 34895 diff --git a/raw/rel-18/29_series/29503/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/raw/rel-18/29_series/29503/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5c9145de63cc6ec90ea76e81c2d042093e3ad39 --- /dev/null +++ b/raw/rel-18/29_series/29503/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14ec4feab654652ef764855aa71093b6f300c962372552ed24fe8b3dbd7621e3 +size 34522 diff --git a/raw/rel-18/29_series/29503/8bc528a620af2b7f493359b4ddbd8c7e_img.jpg b/raw/rel-18/29_series/29503/8bc528a620af2b7f493359b4ddbd8c7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a0b72eedd89aa9c81bfad9d35c9fce3113ca325 --- /dev/null +++ b/raw/rel-18/29_series/29503/8bc528a620af2b7f493359b4ddbd8c7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21727bfb4f91bb07c7c985c70a0e09e86750dd1c2bccddbb7a7d6eefdd8dceac +size 8463 diff --git a/raw/rel-18/29_series/29503/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/29_series/29503/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c43848ebd106d850b1cc90bf92d10eedd252941 --- /dev/null +++ b/raw/rel-18/29_series/29503/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c145ec430873513da76063d8db9809347abf7bb4d5bfdc55720b72221d90254c +size 31044 diff --git a/raw/rel-18/29_series/29503/914919be6b64b1c8bb74e12616c85f71_img.jpg b/raw/rel-18/29_series/29503/914919be6b64b1c8bb74e12616c85f71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0987faf4ccba205d195aa6d35441b2edbef6c427 --- /dev/null +++ b/raw/rel-18/29_series/29503/914919be6b64b1c8bb74e12616c85f71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb8d84968cb8917e1113d9f9da4c805a24c3fe7bf9bfe5fc3ff65a538b2c7e89 +size 30447 diff --git a/raw/rel-18/29_series/29503/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/raw/rel-18/29_series/29503/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20e8a12280527e132a103ad6dbba9a165ba1275b --- /dev/null +++ b/raw/rel-18/29_series/29503/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7b99f0020669a7499c3267a261f20aa195d96621ea5b26d9b5fa6dc4e5cc72d +size 31402 diff --git a/raw/rel-18/29_series/29503/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/raw/rel-18/29_series/29503/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1bb6878af8255215acfdc72c31cce3d34849510 --- /dev/null +++ b/raw/rel-18/29_series/29503/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd02a85f9dffe0dd5dc45f6cf16aa77d50e7905e559a65c6c4af62d5a69dfa51 +size 25366 diff --git a/raw/rel-18/29_series/29503/997233d405f0d4b89ddeb7683e047f66_img.jpg b/raw/rel-18/29_series/29503/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4890051eab71629780fcad42b2ad1232f427c389 --- /dev/null +++ b/raw/rel-18/29_series/29503/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:533aa245458ab9c1e2b226fe91e09842c7fea7d69b9494a192062d2a83323e0f +size 21509 diff --git a/raw/rel-18/29_series/29503/9b686adccf125267a013fa25721231a3_img.jpg b/raw/rel-18/29_series/29503/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdca25a54f79703361a0ec3f1904bb411e9dd82c --- /dev/null +++ b/raw/rel-18/29_series/29503/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4679cbe1c50dca2dd0ae3611e33b7ac386787abf8ca467c6b84571799aa9b8f5 +size 36714 diff --git a/raw/rel-18/29_series/29503/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/raw/rel-18/29_series/29503/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32287df61fbefd13dcedd29346460344b9c1a810 --- /dev/null +++ b/raw/rel-18/29_series/29503/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2e7888b849e872eb5b34219eb6884e68bea23067c77a60f9b54b902d10f5d4d +size 59941 diff --git a/raw/rel-18/29_series/29503/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/29_series/29503/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79d99dabc8ef41d3e82c00ebf6b6df5f26cf34e7 --- /dev/null +++ b/raw/rel-18/29_series/29503/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:775d4db6d7edd4a1c90e98f0ed8b35157c82a6efda56f5cc31665a81a8015d6b +size 30878 diff --git a/raw/rel-18/29_series/29503/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/29_series/29503/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd0961f24aac888681cad6ae8176bf07705a5bc0 --- /dev/null +++ b/raw/rel-18/29_series/29503/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6f7e5c839965581d10e7b407462af2129f6c61c3f73017dd1cce31437a6cff8 +size 114013 diff --git a/raw/rel-18/29_series/29503/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/raw/rel-18/29_series/29503/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf15048346824e585daa30de487552ec26cc8ad --- /dev/null +++ b/raw/rel-18/29_series/29503/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a6a0064ba6d4f5a27d46a6df144b657b7eab2fbc16d0f18a7ceae99313512b6 +size 34321 diff --git a/raw/rel-18/29_series/29503/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/raw/rel-18/29_series/29503/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bba776c46ea45418616c4752768cae0c28c525c --- /dev/null +++ b/raw/rel-18/29_series/29503/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e967fbdb69705f234838eaf3853d41f2554766b088345cffb77dcab3b8b6bd26 +size 33881 diff --git a/raw/rel-18/29_series/29503/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/raw/rel-18/29_series/29503/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01c2002a0baac40c4987a56c4aa2ea9e1c975d34 --- /dev/null +++ b/raw/rel-18/29_series/29503/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89b23473bd459b71fa98c9258234f1213c0ebcfa34861b8a6757510c4dc0b7ee +size 39206 diff --git a/raw/rel-18/29_series/29503/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/29_series/29503/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d2e6ff24582e4430d360b989bd61c3dee7bc7e1 --- /dev/null +++ b/raw/rel-18/29_series/29503/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51a99aebbeaf980c1f99c7fbcba8a72438ce240ea241f150315b11fcfc91598d +size 62137 diff --git a/raw/rel-18/29_series/29503/a4b963a07cc368283154762c4b156fe7_img.jpg b/raw/rel-18/29_series/29503/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..263d259ff3b83093fea19e1223d4ab177c1ba59f --- /dev/null +++ b/raw/rel-18/29_series/29503/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0162ca3208974d40eeaa8970a7d9ddfca0cf448a7c38ffc105f4833fac6095c +size 34977 diff --git a/raw/rel-18/29_series/29503/a5184899f915014fa38608754efcc9c7_img.jpg b/raw/rel-18/29_series/29503/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..102b133ae18fbadf6507cd89508b012aa0055bba --- /dev/null +++ b/raw/rel-18/29_series/29503/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f7c7e6518d9ee3d73260fcca6e9a1aed75a14b746643cdc4903e6b1df43eb1b +size 33044 diff --git a/raw/rel-18/29_series/29503/a796a6e439fe5969697f79dc5e124acc_img.jpg b/raw/rel-18/29_series/29503/a796a6e439fe5969697f79dc5e124acc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99ab7a2af5d6294d3c2a9db8d859ab3113683c69 --- /dev/null +++ b/raw/rel-18/29_series/29503/a796a6e439fe5969697f79dc5e124acc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf10ede539cac8334c2a15299597ebe71c0cf71242670e3c25e01b587e903f52 +size 32146 diff --git a/raw/rel-18/29_series/29503/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/raw/rel-18/29_series/29503/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..910b761840a071f29564aec4f2859fc223bb3812 --- /dev/null +++ b/raw/rel-18/29_series/29503/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:446ef244390b7b80753b38b64e8690be74cd5772de7aace2fd9ae142a75cce16 +size 28965 diff --git a/raw/rel-18/29_series/29503/a89d151b67109378baed0c117830cf78_img.jpg b/raw/rel-18/29_series/29503/a89d151b67109378baed0c117830cf78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecef1e410e8303c267a7f9c70268305726f9c828 --- /dev/null +++ b/raw/rel-18/29_series/29503/a89d151b67109378baed0c117830cf78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c50120d364444acfcf7a445a41efc2f5a2d9403cc63b850541b99375c5e7c93f +size 25448 diff --git a/raw/rel-18/29_series/29503/a97518a839da75f8379c578562b01bc2_img.jpg b/raw/rel-18/29_series/29503/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed28ad97dba333aab4ba088aefe4a765e508ae73 --- /dev/null +++ b/raw/rel-18/29_series/29503/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81470909e51efd21c31034f54599d7c8c0f942e09831600d715ff4bb087d4330 +size 36453 diff --git a/raw/rel-18/29_series/29503/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/raw/rel-18/29_series/29503/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97f8e968102745ab3d4862ca9d7dbbd1071f6b68 --- /dev/null +++ b/raw/rel-18/29_series/29503/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bac15458f4be261adf4f73fd6a06646c3c8e86062a6308ef1923b1c420ae063 +size 36636 diff --git a/raw/rel-18/29_series/29503/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg b/raw/rel-18/29_series/29503/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..687b827b033075cee4f7ea942684bfeb60f66c94 --- /dev/null +++ b/raw/rel-18/29_series/29503/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a63152402ddc140f674a3b0919a48e9f1f695c2b2e53da2f31e9d297959b46b8 +size 31824 diff --git a/raw/rel-18/29_series/29503/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/raw/rel-18/29_series/29503/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e22bb4509be6ad8a235aa1980585f658e800d2a --- /dev/null +++ b/raw/rel-18/29_series/29503/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cadadc14f95986f7fe9c33089b5b709225d6e9dc5f8f0100bd9a94898ad56b33 +size 27603 diff --git a/raw/rel-18/29_series/29503/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/raw/rel-18/29_series/29503/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..196cc4e65a774a982ebadba18d66a4f31e7778e9 --- /dev/null +++ b/raw/rel-18/29_series/29503/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28d61317ed84ec2a9bb2ba9e22dafb57223708b40b4238942c89a62e1a4d497c +size 29614 diff --git a/raw/rel-18/29_series/29503/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/raw/rel-18/29_series/29503/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e591604a594393716deb568a689d996f4c6b1aea --- /dev/null +++ b/raw/rel-18/29_series/29503/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f51de398896b66c341ba045146569f51f75f980424f7604b91b54276adb3cbb +size 88299 diff --git a/raw/rel-18/29_series/29503/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg b/raw/rel-18/29_series/29503/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ee956402d4176b20b6106e784b9ae99b00ab0c1 --- /dev/null +++ b/raw/rel-18/29_series/29503/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb0cb6c1f09a0f0c16663ce2690edf7d6f06c7994e4fb6faea98af265a188185 +size 37997 diff --git a/raw/rel-18/29_series/29503/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/raw/rel-18/29_series/29503/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95dd20fe391ac5140a063217cecbf8fce057195a --- /dev/null +++ b/raw/rel-18/29_series/29503/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:498d59c5457f013527d8bd1c0c2056cdfcb8cbbf7ddf25dd56ea6c856d0cea20 +size 84213 diff --git a/raw/rel-18/29_series/29503/b6b53a74ad203c01b81e5427e9d6a898_img.jpg b/raw/rel-18/29_series/29503/b6b53a74ad203c01b81e5427e9d6a898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46da5febec183c19ef1f566aa1975d2b3335ad0a --- /dev/null +++ b/raw/rel-18/29_series/29503/b6b53a74ad203c01b81e5427e9d6a898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:054c369b72eadf9825ec38b0813e5fd8e1149a8a45e75041842d9162de833b6d +size 28764 diff --git a/raw/rel-18/29_series/29503/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/raw/rel-18/29_series/29503/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8195964ef97f61f4964e36c5b5fa3232122c6b66 --- /dev/null +++ b/raw/rel-18/29_series/29503/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b46917bb28eb9a2f677396234aead36eaceef8abf1809c4f77bc1dbf2c16f12 +size 25863 diff --git a/raw/rel-18/29_series/29503/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/raw/rel-18/29_series/29503/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07fdc278cca1be918797e51d4e07a5fbb6efff2c --- /dev/null +++ b/raw/rel-18/29_series/29503/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9f87686234e30f144d3807a4ff23926645f075f2058f7731262ad1376ee20de +size 14696 diff --git a/raw/rel-18/29_series/29503/c036e2540a94b31357ceb0002f0cacab_img.jpg b/raw/rel-18/29_series/29503/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be53a7450f57b75f4f778a34e7eed61d8f58a1a5 --- /dev/null +++ b/raw/rel-18/29_series/29503/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:953c4f5f65635e9e7416c4ba2b2314d773f9de2de78272d2ef404e8d79eb9abf +size 35193 diff --git a/raw/rel-18/29_series/29503/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg b/raw/rel-18/29_series/29503/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad20df28ea19d2896b2f956ba876d68fabc7336 --- /dev/null +++ b/raw/rel-18/29_series/29503/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ce12e04d9caf177e2406292ad84f87acf26b15d319151631a878848f4628e7b +size 40982 diff --git a/raw/rel-18/29_series/29503/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/raw/rel-18/29_series/29503/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd7d6aafa7609e4d5d8fcdc9128d061a9a700b60 --- /dev/null +++ b/raw/rel-18/29_series/29503/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ab497a39ee84905617b5ffc97e194e5d313f2f3843e2f8b61711892b5f37303 +size 31762 diff --git a/raw/rel-18/29_series/29503/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/raw/rel-18/29_series/29503/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0a7dff5fbaa97dbfc0571aa006555b9a5c73181 --- /dev/null +++ b/raw/rel-18/29_series/29503/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24c4e6b1ee04d77f6bfc12bbc5b10c1afb1e960193e19f09de0a34e5e6ec0643 +size 31637 diff --git a/raw/rel-18/29_series/29503/cd141897aa368dbbaa398ace230cdd85_img.jpg b/raw/rel-18/29_series/29503/cd141897aa368dbbaa398ace230cdd85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29a4045c8e26fa522c098e4d18f236a81a10458d --- /dev/null +++ b/raw/rel-18/29_series/29503/cd141897aa368dbbaa398ace230cdd85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:903041a9d9938f579eee86c5ad3b6705d4af1fffe44eebe8a440e8063c334311 +size 35357 diff --git a/raw/rel-18/29_series/29503/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg b/raw/rel-18/29_series/29503/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd9fda3d2ce33d395f3f67a626ba0a338314319d --- /dev/null +++ b/raw/rel-18/29_series/29503/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3900ca884f083bd23b4fd6c7f8e429e5527d0e788bfc9fdab0ed3d1b1cd9739 +size 29214 diff --git a/raw/rel-18/29_series/29503/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/raw/rel-18/29_series/29503/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22bb411afef2e5be2baef9353e4ed22127559282 --- /dev/null +++ b/raw/rel-18/29_series/29503/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:231d25f024bf54a7586288ba41a8ab75a528f1d4fbfbf9132d2f4cb16cdbdb74 +size 62812 diff --git a/raw/rel-18/29_series/29503/d26959f4514c26ca19c3d6f00da85956_img.jpg b/raw/rel-18/29_series/29503/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0ddfcf270e04688907ddeac7f8e78f139e381ce --- /dev/null +++ b/raw/rel-18/29_series/29503/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8b121f04cda51603600b3083ad374f9f5fa3c2b92a2552420815f2fd2214563 +size 36838 diff --git a/raw/rel-18/29_series/29503/d5918cee231b536f20789a18d861fae3_img.jpg b/raw/rel-18/29_series/29503/d5918cee231b536f20789a18d861fae3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5d869cdafc8de4ae152a685b2ab9381f65238de --- /dev/null +++ b/raw/rel-18/29_series/29503/d5918cee231b536f20789a18d861fae3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49bfa3bd270ae09ded6d2914314f97d385fd978eb0e21b446cad3accf9857a40 +size 36735 diff --git a/raw/rel-18/29_series/29503/d6015fcef74bce83d04acd2e17b4fc15_img.jpg b/raw/rel-18/29_series/29503/d6015fcef74bce83d04acd2e17b4fc15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdca51571249bf7989369ed1d2436ba99aac6f24 --- /dev/null +++ b/raw/rel-18/29_series/29503/d6015fcef74bce83d04acd2e17b4fc15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d5224cee88c4d0b526aa207640ae3b22b16b579c5656765843730b01eed1f1a +size 31861 diff --git a/raw/rel-18/29_series/29503/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/raw/rel-18/29_series/29503/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cbcc37756a5313167ea5fa63cf4a6b497ea0735 --- /dev/null +++ b/raw/rel-18/29_series/29503/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb0c92e15e08c9821abfe0a36ba136bfc5acb3accedd2fcc534fefa64daad847 +size 26524 diff --git a/raw/rel-18/29_series/29503/db5deafdae53dbc7d5972957f708c691_img.jpg b/raw/rel-18/29_series/29503/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4002047e7652a3a109c41989e8f7a65fbe90b79b --- /dev/null +++ b/raw/rel-18/29_series/29503/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2539b450c14a12f80ebfbe47a0d588356eeb34d990572ab73a160c01ae38b86b +size 33672 diff --git a/raw/rel-18/29_series/29503/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/raw/rel-18/29_series/29503/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..683d4d6bc73d904902e001c377809379463c1814 --- /dev/null +++ b/raw/rel-18/29_series/29503/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:528d88e029929d4bc216100fffe3ab20b2289b84dc49d71ddfd06745cd659a78 +size 28018 diff --git a/raw/rel-18/29_series/29503/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg b/raw/rel-18/29_series/29503/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33ee6d6f00049383a96c2b89d7949e54ff8c3241 --- /dev/null +++ b/raw/rel-18/29_series/29503/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64b613022c0ceb7ccc32f833f92cb47d4aa32c1c78beedd5a4540dff96be473c +size 32423 diff --git a/raw/rel-18/29_series/29503/ddfa5b18550d1a022a941e3c31843814_img.jpg b/raw/rel-18/29_series/29503/ddfa5b18550d1a022a941e3c31843814_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e096effc6fed69f7275ec4421837ab7de09fdc78 --- /dev/null +++ b/raw/rel-18/29_series/29503/ddfa5b18550d1a022a941e3c31843814_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75cd7d0c1754488774da0d44c24ee6ae6e9d0edd9f685eb46fe3e1c0b80fe649 +size 30730 diff --git a/raw/rel-18/29_series/29503/dec689324b075952626a86da862b9549_img.jpg b/raw/rel-18/29_series/29503/dec689324b075952626a86da862b9549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77570567429715287737cd83eadfc069ce88df66 --- /dev/null +++ b/raw/rel-18/29_series/29503/dec689324b075952626a86da862b9549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99602df33bae28711278d591de490162bd9b4f8099d7f680e2bc5fbfd4790382 +size 29614 diff --git a/raw/rel-18/29_series/29503/df1966d80c74bc127f159a48f38b13ee_img.jpg b/raw/rel-18/29_series/29503/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97ababd069e76063f5c331940ddeff60b87d00ff --- /dev/null +++ b/raw/rel-18/29_series/29503/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81e6424eb8373fbb5e74b68dfbd11f945bc6233a8b4f0f3678fa749d87562ef6 +size 31242 diff --git a/raw/rel-18/29_series/29503/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/raw/rel-18/29_series/29503/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0291b2a7c02ee0e25388d5c56ccbb092b8fdb981 --- /dev/null +++ b/raw/rel-18/29_series/29503/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed909683c7e6c4b92cd6474f0001ee56c9a07c69b6c9fa680880a9b4d2f864c +size 27244 diff --git a/raw/rel-18/29_series/29503/dfaa8b98082261913dac00eae86b2889_img.jpg b/raw/rel-18/29_series/29503/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efe42d1c1b076279b086bfd22158a5e871edabb0 --- /dev/null +++ b/raw/rel-18/29_series/29503/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4ceb9d7583230be1c3e8c1327e23eddb4472e0e5e57ca5056eb9df49fd866d1 +size 32188 diff --git a/raw/rel-18/29_series/29503/e05b36c0d46549e681ce6581422c66b2_img.jpg b/raw/rel-18/29_series/29503/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a697838b9a40bee92f9e33af4d4605bfb2e23458 --- /dev/null +++ b/raw/rel-18/29_series/29503/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ecd00673239a7383c7ec5a1d640c291d2f57b38ab779796989e7deac6d8d396 +size 29391 diff --git a/raw/rel-18/29_series/29503/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/raw/rel-18/29_series/29503/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..783e8e29eb27c804ee29e6728d4fdef7a07c1af2 --- /dev/null +++ b/raw/rel-18/29_series/29503/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a58cdec87e85c5506e813eff961af5d26fcfae8e93049e9f63a3343d6051082 +size 28870 diff --git a/raw/rel-18/29_series/29503/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/29_series/29503/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f8c17bb015c6a54881432ccb14f03edced5b8f4 --- /dev/null +++ b/raw/rel-18/29_series/29503/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd0a6f7840212d7d05a35d13f15b8549f148336e3da4fb7384233d83abd7bff3 +size 33996 diff --git a/raw/rel-18/29_series/29503/e4a14961bdc9882e296b25f7ae5f9760_img.jpg b/raw/rel-18/29_series/29503/e4a14961bdc9882e296b25f7ae5f9760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2b41fc1b02c8ca775d75628a78c4766b4630fc6 --- /dev/null +++ b/raw/rel-18/29_series/29503/e4a14961bdc9882e296b25f7ae5f9760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfc915663e2a6f278fcaa623272553fbab94a0c39c25c4ad81cfe90b32a04d1a +size 30251 diff --git a/raw/rel-18/29_series/29503/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/raw/rel-18/29_series/29503/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03442754050d594459e370a9a0498f8438d9ecb3 --- /dev/null +++ b/raw/rel-18/29_series/29503/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19ba70be7c4fb1349ba5ba15879c01e3b006bc20c9b64eacb99a442ff262daa8 +size 37732 diff --git a/raw/rel-18/29_series/29503/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/29_series/29503/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bee25129a524f0e932af0d7d11f36e5de3181b7c --- /dev/null +++ b/raw/rel-18/29_series/29503/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ee4d0fde489828025a4684b0fc5e47ffa03f462f913f9c0a4ba69478df35137 +size 41497 diff --git a/raw/rel-18/29_series/29503/e9b43ac020435f8121e8592f31afdc52_img.jpg b/raw/rel-18/29_series/29503/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5535959c93203e89774d4e87975ab1ea3b48c116 --- /dev/null +++ b/raw/rel-18/29_series/29503/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cc0271391f64cfbe9483f553f2817789f4b118486ee2bf3065f18f28abe570f +size 26874 diff --git a/raw/rel-18/29_series/29503/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/29_series/29503/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d13f892f3fa4e6f6310b7cf5b535d2a018c70c7 --- /dev/null +++ b/raw/rel-18/29_series/29503/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58f434b6417b7aaa86688105809dc3eda9fde79078efa40088c355bb6611b293 +size 29720 diff --git a/raw/rel-18/29_series/29503/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/raw/rel-18/29_series/29503/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae8e511e6989dbd6e38000fe9951d9a1e72a66c3 --- /dev/null +++ b/raw/rel-18/29_series/29503/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52ce7b06b0887cdf86b535443bbab510e8097a7f3c2be17a24f45f7dd9d6b68b +size 32234 diff --git a/raw/rel-18/29_series/29503/f1cbfa3fc27f58581615654fec4335d8_img.jpg b/raw/rel-18/29_series/29503/f1cbfa3fc27f58581615654fec4335d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..781baf463103d9ef9518b50d30abc564416d999e --- /dev/null +++ b/raw/rel-18/29_series/29503/f1cbfa3fc27f58581615654fec4335d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e154e5c58297f81dc1869b7e5b0ac3bdac140b2df5ac771551081e0ea3da51ed +size 25916 diff --git a/raw/rel-18/29_series/29503/f4535959316aea381fb56b9225d8e4bd_img.jpg b/raw/rel-18/29_series/29503/f4535959316aea381fb56b9225d8e4bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56d9398011c4a1807bea298a21b33180edb165bd --- /dev/null +++ b/raw/rel-18/29_series/29503/f4535959316aea381fb56b9225d8e4bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ff1e2f1f55f7988f51e90a2c7d90bda0bb4d0d0af92be7e91d821139367a377 +size 32397 diff --git a/raw/rel-18/29_series/29503/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/raw/rel-18/29_series/29503/f5d2a88925807080157c7cfb1d41cf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bca649d25ba62ed87eb44bfe7c5f152ccdb67d0b --- /dev/null +++ b/raw/rel-18/29_series/29503/f5d2a88925807080157c7cfb1d41cf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98bb6c20e9dbf3b3349fed6ce2d276bca5ee9dd61564387046103b16fef15a9a +size 30216 diff --git a/raw/rel-18/29_series/29503/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg b/raw/rel-18/29_series/29503/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a18049f6bd52d8b856133085c22e040ef3c0936 --- /dev/null +++ b/raw/rel-18/29_series/29503/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:322382fd9fe9d692dadffb2a5abc2a437ca751a72ae1608f77ab9f288d7166bc +size 27787 diff --git a/raw/rel-18/29_series/29503/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/raw/rel-18/29_series/29503/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fa5782d43fcc0c22a2b67bbdbaae37d3e586e4f --- /dev/null +++ b/raw/rel-18/29_series/29503/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88c62614b4fb2b07df7aa55132944f4345866e15010ede8befa21d8ba26ddeb6 +size 34343 diff --git a/raw/rel-18/29_series/29503/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/raw/rel-18/29_series/29503/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..440a543be808696f8f50fa801cacbddfc26856e5 --- /dev/null +++ b/raw/rel-18/29_series/29503/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36bce3ffcba61a33ef1c26aa867042b6dc137ee26d7f827dba49fbe8e1dc323f +size 22731 diff --git a/raw/rel-18/29_series/29504/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/29_series/29504/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76832c8c2f1b5090a784de371dcaafa2ef2e8aff --- /dev/null +++ b/raw/rel-18/29_series/29504/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a314f682fe6990b3b7a680866f842031daf408abc602719c2b604ad189864b6 +size 32324 diff --git a/raw/rel-18/29_series/29504/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/raw/rel-18/29_series/29504/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba0046a2073a3cd19fb22406d763e04ac8eafb8 --- /dev/null +++ b/raw/rel-18/29_series/29504/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7220ca5fa877e6b5653dfebdfade48b40ec86633b19100ae034c791243b072a2 +size 26961 diff --git a/raw/rel-18/29_series/29504/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/raw/rel-18/29_series/29504/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a9ee7c846388129496a3796fc6a80f276702cfc --- /dev/null +++ b/raw/rel-18/29_series/29504/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcd2bb740fd258f52952046c0760eed1993c5ae255b896c7fd2afecbf94b5acb +size 18318 diff --git a/raw/rel-18/29_series/29504/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/29_series/29504/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af512a80ad96503a2aadd02a12c7396fdfa514be --- /dev/null +++ b/raw/rel-18/29_series/29504/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df035aacb6efd01319c1763313fb6dd1afe4d47a6db11c99525a992688932477 +size 31154 diff --git a/raw/rel-18/29_series/29504/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/raw/rel-18/29_series/29504/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..806ef17b35c441dff05ce1ffd977272d3b3d990c --- /dev/null +++ b/raw/rel-18/29_series/29504/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f85d96b0dbfacf2f7afe26b58a9cfdbd06bc65e2790fcd0e2f3df9a5342156fb +size 27165 diff --git a/raw/rel-18/29_series/29504/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/raw/rel-18/29_series/29504/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bfa28ff31b1784f9648fd59e1c97d6e2541b9d8 --- /dev/null +++ b/raw/rel-18/29_series/29504/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc3b96045589e0e8c9c36b0e4079e9fe3592fd961cdadebaaf5d8ea674b1f83c +size 27576 diff --git a/raw/rel-18/29_series/29504/4356776ca004ecba5d599667a155d7d4_img.jpg b/raw/rel-18/29_series/29504/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66afbffb4e139c04d815f21b37b85799be462884 --- /dev/null +++ b/raw/rel-18/29_series/29504/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a61ee46f1700ba20f1dbdbe68a2d79e5f80547ec8683ffcf9f4355bf0728d76 +size 20239 diff --git a/raw/rel-18/29_series/29504/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29504/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..780d49046afae70d9cf5d0db8b706f60dfd406cf --- /dev/null +++ b/raw/rel-18/29_series/29504/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:014b846e8ce668d1741f6743d69652826a0f8618748f00b1cb5df49656c086fc +size 9927 diff --git a/raw/rel-18/29_series/29504/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29504/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8e6824f4487bf97ef0911c2b26db855a11a1b1c --- /dev/null +++ b/raw/rel-18/29_series/29504/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fd013bfb6fe5a36083ddc4d6b2f835587159e29126a18c6b536631aff39f0b3 +size 5691 diff --git a/raw/rel-18/29_series/29504/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/raw/rel-18/29_series/29504/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3793e0e9e3ad0cbdd371570d19ae0238567a6625 --- /dev/null +++ b/raw/rel-18/29_series/29504/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b3ebc9a81388ccfec8fd912770b5a19d22fdc8cb17876d61937cc681173cadc +size 26935 diff --git a/raw/rel-18/29_series/29504/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/raw/rel-18/29_series/29504/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47ffb8200c7a87c8355b3e0a5dbd4f26e2d91978 --- /dev/null +++ b/raw/rel-18/29_series/29504/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4021faca07be701307b4f93a913d20aab2365ab493f0227e1f061f013fab8757 +size 33230 diff --git a/raw/rel-18/29_series/29504/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29504/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..498106d48eff30aec200c2858a89b394d320f44b --- /dev/null +++ b/raw/rel-18/29_series/29504/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6bc6570cc98182a49a2967f3a5ef101a85bd44abda3f0edc1d36df80c0b8891 +size 27279 diff --git a/raw/rel-18/29_series/29504/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/raw/rel-18/29_series/29504/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e00ae7dd78b73e76e6870cbc7642f75a77470e20 --- /dev/null +++ b/raw/rel-18/29_series/29504/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0b700e58d9fb4e0b1215f55941ad78d84a74943d49b19843f63e54e91c48d11 +size 47878 diff --git a/raw/rel-18/29_series/29504/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/raw/rel-18/29_series/29504/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5bf117fbb86f66f74033fe0308d7c9d8f0670f --- /dev/null +++ b/raw/rel-18/29_series/29504/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2fa8771292fe5022a9c1e7570950fd3f3fc2f305d7589193bf719b31594516d +size 30139 diff --git a/raw/rel-18/29_series/29504/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/raw/rel-18/29_series/29504/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..489711d283bbee85bfb6ccd2f44076833fa53971 --- /dev/null +++ b/raw/rel-18/29_series/29504/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bf87c229c87390ff9590f6147f7b347485c232bd7bdf969ec99366b991485e8 +size 21297 diff --git a/raw/rel-18/29_series/29504/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/29_series/29504/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80d616d49656b516270d07c884bb39eb03e7fa7d --- /dev/null +++ b/raw/rel-18/29_series/29504/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34ab0dda6403f2db80fadfd4b1cf48607be38ddd128e1041992241393d1d42da +size 28048 diff --git a/raw/rel-18/29_series/29504/db7cb51aac8519daab50e2171cecae82_img.jpg b/raw/rel-18/29_series/29504/db7cb51aac8519daab50e2171cecae82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afb43e62f817cb64b5cb7d98d3bc1f0d3946beeb --- /dev/null +++ b/raw/rel-18/29_series/29504/db7cb51aac8519daab50e2171cecae82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36cd15bc207c96bacf13d157caf4c89644fe3568e555c348f928c109f8632e09 +size 29065 diff --git a/raw/rel-18/29_series/29504/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/raw/rel-18/29_series/29504/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..294ddbe3ce10302be589fe0c4d8c366cb15de422 --- /dev/null +++ b/raw/rel-18/29_series/29504/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be4f6580a88bc047e57a1246fc6a7e2a0bb3fa27c4005b9f653dc65f9acbc27e +size 52963 diff --git a/raw/rel-18/29_series/29504/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/raw/rel-18/29_series/29504/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44c805ff138cbed30bb1d0daec20263675704212 --- /dev/null +++ b/raw/rel-18/29_series/29504/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6868428e5016fa234faa44980bde8cdad9cf491ffc58bc436e05ef47eb101fbc +size 25479 diff --git a/raw/rel-18/29_series/29505/4356776ca004ecba5d599667a155d7d4_img.jpg b/raw/rel-18/29_series/29505/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..685ce90bf2b4d11381a7692770c592a61ae02ff2 --- /dev/null +++ b/raw/rel-18/29_series/29505/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce2a2a543248aa59ac84bea56079a4d42971d6683900a93fa20ccaa34ae089b9 +size 164604 diff --git a/raw/rel-18/29_series/29505/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29505/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c079603ac8a2737ecf1671e362b249bfdb380589 --- /dev/null +++ b/raw/rel-18/29_series/29505/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43b0debde0df112e340c490da2a01455a051550d8d7e35305179bb2b9a2e8024 +size 9416 diff --git a/raw/rel-18/29_series/29505/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29505/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79ad2b3f7151f431956cd498927dbca6b0025024 --- /dev/null +++ b/raw/rel-18/29_series/29505/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2143733bad8e7bd47682013d3c1a4c99f2531571fe0b03583ab4cc2b15020c3 +size 5556 diff --git a/raw/rel-18/29_series/29505/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/raw/rel-18/29_series/29505/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4f27567ae999af0bb316d3a1cbb48f9039c6034 --- /dev/null +++ b/raw/rel-18/29_series/29505/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5afe844580495e608701d949e0d8fd302972358482d9db668349c611fa74feb +size 157082 diff --git a/raw/rel-18/29_series/29505/a3472689858b068ef469213682965325_img.jpg b/raw/rel-18/29_series/29505/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20426eb39a68c3cbd6335e30e72cf84109fb4ac8 --- /dev/null +++ b/raw/rel-18/29_series/29505/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1bb365c2cc7795e219a537b6375f0d234b709db9452eab2d4748700fa8b6cd2 +size 103575 diff --git a/raw/rel-18/29_series/29510/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/raw/rel-18/29_series/29510/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83a566813cc6448dec09e98b2b8f060c06ead55b --- /dev/null +++ b/raw/rel-18/29_series/29510/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cdc9c84e6ce55a66c1c2dd13d661182d5c152cc3b9e84831429354d529ecdb5 +size 34537 diff --git a/raw/rel-18/29_series/29510/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/raw/rel-18/29_series/29510/080a7af02bc47cf21ebfae4e0be39745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82b57ec80a2a6f2307a1f285d5fee65d13bec149 --- /dev/null +++ b/raw/rel-18/29_series/29510/080a7af02bc47cf21ebfae4e0be39745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:713dad643f8fe692999cc5f4cea90a16689f56fdcc8f5d42d24a84bfd43db787 +size 40300 diff --git a/raw/rel-18/29_series/29510/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/raw/rel-18/29_series/29510/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..051734a8164f1f1bd7ce16d334185152cd383d0b --- /dev/null +++ b/raw/rel-18/29_series/29510/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04619326df4a0ec6c0a02e17af229a40ab6a785e664bf450f59afa1c67f75945 +size 34219 diff --git a/raw/rel-18/29_series/29510/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/raw/rel-18/29_series/29510/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01f00e0cf32e7d91faff97ac6ab493482adb8dbe --- /dev/null +++ b/raw/rel-18/29_series/29510/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f806a2b1d0ca3bf47b98eb9e4c9d730a345ecea44f71978be717bb79e79b7fa +size 33425 diff --git a/raw/rel-18/29_series/29510/132cff7e872feb31f629703959beddd7_img.jpg b/raw/rel-18/29_series/29510/132cff7e872feb31f629703959beddd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be3d719af35a46c6a6c498d239ecb0aa776887f4 --- /dev/null +++ b/raw/rel-18/29_series/29510/132cff7e872feb31f629703959beddd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ae9eaa6c81ebe2d331c2b7df6ad6a591fd65de8b4db73b66fd737e32c8cffb3 +size 46586 diff --git a/raw/rel-18/29_series/29510/14515d82ffeec9475b9add3036ff26ab_img.jpg b/raw/rel-18/29_series/29510/14515d82ffeec9475b9add3036ff26ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df581ef4fef83b62435964f377f61c7634158ef4 --- /dev/null +++ b/raw/rel-18/29_series/29510/14515d82ffeec9475b9add3036ff26ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8c9f4872cf99a88c640d6b52eab779625beb71cc3b28e059e81ac57a460cdd9 +size 36392 diff --git a/raw/rel-18/29_series/29510/1841f348dfa81a3438d4e1f8465d9ac7_img.jpg b/raw/rel-18/29_series/29510/1841f348dfa81a3438d4e1f8465d9ac7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aada97744cb851a9a83cf3ec9fca8961cee9897 --- /dev/null +++ b/raw/rel-18/29_series/29510/1841f348dfa81a3438d4e1f8465d9ac7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df58667a482b566e09f894313fe7d584edc5228343163f1cd58d72eccf202b8 +size 32397 diff --git a/raw/rel-18/29_series/29510/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/raw/rel-18/29_series/29510/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dea00a7f7853ad1f4e833216eb6edc86a23b88ea --- /dev/null +++ b/raw/rel-18/29_series/29510/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8fe3508fdbde1315fac41d3d905c164d54aed1198ebe16fc90bf405cdb4e735 +size 35574 diff --git a/raw/rel-18/29_series/29510/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/29_series/29510/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e9a0f6b1547aa05e10f65137166fe985a743223 --- /dev/null +++ b/raw/rel-18/29_series/29510/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75f372638ea7c4ca82180514dd6d9c41fe092081d9bb78859c3f5bbdfa515965 +size 49629 diff --git a/raw/rel-18/29_series/29510/32ff77da4286b58c4778033acaa10836_img.jpg b/raw/rel-18/29_series/29510/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d8b3b99183c03bc85826260b80536c7a9865a2c --- /dev/null +++ b/raw/rel-18/29_series/29510/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ccbbbcf372ba7e41490dc352e406795bbc398e59b5097bbd3cf4a9391834679 +size 38439 diff --git a/raw/rel-18/29_series/29510/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/raw/rel-18/29_series/29510/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6152b5cbfffcacb945937e8d65b41eb40d4db89c --- /dev/null +++ b/raw/rel-18/29_series/29510/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55d6598b1da2ee210bb29ceae889d677be76e7ab424d6b945da99e69b8ea267f +size 36225 diff --git a/raw/rel-18/29_series/29510/3b00a61116faef21d3a6009fd350b46a_img.jpg b/raw/rel-18/29_series/29510/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56410e0d41e19462398ed13de31f24fed8977544 --- /dev/null +++ b/raw/rel-18/29_series/29510/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00ae7b6fc5852ba273b91f745967ceb2c5b85eb97221e1e8f362073be8266b79 +size 45780 diff --git a/raw/rel-18/29_series/29510/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/raw/rel-18/29_series/29510/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcaa4b316b76f7e5f2717e4a9a4a89760071ec6b --- /dev/null +++ b/raw/rel-18/29_series/29510/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1eeb3b0326fd7def8b39da41e596731ffc0e2541e954cc063f7edbf6fb8547f3 +size 29613 diff --git a/raw/rel-18/29_series/29510/43979979715bb3304389a0cb18f34444_img.jpg b/raw/rel-18/29_series/29510/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76ebbdb68921b80b3f7d31ba9ec3b144109231b0 --- /dev/null +++ b/raw/rel-18/29_series/29510/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1770a58aee39b4bfb6798d1a353a7d8f2e50b97c571df9943bf4e3192da858c +size 34126 diff --git a/raw/rel-18/29_series/29510/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/raw/rel-18/29_series/29510/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0674253c247f736381d1c2ccdefafb4ccd29dbdc --- /dev/null +++ b/raw/rel-18/29_series/29510/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fe51b6acd5ce79c780af30a3b7c68895ed9d7cbc5bc62a6e84dfea67dbf003d +size 49589 diff --git a/raw/rel-18/29_series/29510/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/raw/rel-18/29_series/29510/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dda6479529ee21c0f2a706c0c692e8ecbb9028c2 --- /dev/null +++ b/raw/rel-18/29_series/29510/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:208587d50bba09807511477511472ef227e9e9870b287b98ad180357c00bf50e +size 35896 diff --git a/raw/rel-18/29_series/29510/523ab7b925beb555f88b2e1e1336974f_img.jpg b/raw/rel-18/29_series/29510/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8dffe2c00d6a509639b34d0ca6403a0cc54f126 --- /dev/null +++ b/raw/rel-18/29_series/29510/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a460f4e672e9ffa69d9311c0e5840f13f7fef8c9db9b8479aaa79baf46e8242 +size 32968 diff --git a/raw/rel-18/29_series/29510/5a0427b4033881484e387d85b8d8fa77_img.jpg b/raw/rel-18/29_series/29510/5a0427b4033881484e387d85b8d8fa77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fdf99c3c3bca54468a817d52909d8a611d380a6 --- /dev/null +++ b/raw/rel-18/29_series/29510/5a0427b4033881484e387d85b8d8fa77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:388b3fed3a39c3fcfb834f3620e8d0dbeca96c10d17f3cf42ea7a2dee32f31ca +size 4522 diff --git a/raw/rel-18/29_series/29510/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29510/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d512b12ef170e2993d02cfcee3def7180b68ecda --- /dev/null +++ b/raw/rel-18/29_series/29510/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fef469d1e1a64fd234c5e5e19ed87ebef023bdb48a45437fbc147f5d1011181a +size 9609 diff --git a/raw/rel-18/29_series/29510/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29510/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85a120edd88a8ca0629a285679b0567c9ff0dfa2 --- /dev/null +++ b/raw/rel-18/29_series/29510/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a9e6bd8e60dc7c6bab53e75645c337b136f4b0afca17d29f84c151f568627d1 +size 5487 diff --git a/raw/rel-18/29_series/29510/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/raw/rel-18/29_series/29510/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11c6a889e3bd5ac98f5f64eb7756dc63896b7ab8 --- /dev/null +++ b/raw/rel-18/29_series/29510/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a98e9d41bd42d86b67812eb399dcdd6cc83df8e5960ab4890c34111d49067d62 +size 42283 diff --git a/raw/rel-18/29_series/29510/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/raw/rel-18/29_series/29510/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9b3ff151b97a5938baafca473592366788da0cd --- /dev/null +++ b/raw/rel-18/29_series/29510/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e870e62b8cc4b949772b2a4e12a7bf89d44dec13337a6795f77ac009aad361e6 +size 32042 diff --git a/raw/rel-18/29_series/29510/90ddb84c323b956e2d50a54d3f870566_img.jpg b/raw/rel-18/29_series/29510/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c71b6749c72ee3b818d89192bd55b6504a2158a --- /dev/null +++ b/raw/rel-18/29_series/29510/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97398f08389b6338770d07ebe26700d1ed0fbb4364b45308560f5dc5084a181f +size 46209 diff --git a/raw/rel-18/29_series/29510/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/raw/rel-18/29_series/29510/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c4072f760e77c4d692dec8b186eb680016ba3a4 --- /dev/null +++ b/raw/rel-18/29_series/29510/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c3fc116c3810d891f9f27f0db75d692785b990e1be619271ef45b8ffdce2476 +size 48738 diff --git a/raw/rel-18/29_series/29510/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/29_series/29510/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01e4ac6939b899f17b95be4a664842c687c8eddb --- /dev/null +++ b/raw/rel-18/29_series/29510/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71eb2382bc1f050e572525373b402b7a9a94284e2bf786b2bd700964eb661c91 +size 40355 diff --git a/raw/rel-18/29_series/29510/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/29_series/29510/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d53fc7f45f8ad5f12f881ada80cee35c579a31a3 --- /dev/null +++ b/raw/rel-18/29_series/29510/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:823d9ea20634b193263efcb775472743f1f385828806812aff6c3e6d28f4bc77 +size 35404 diff --git a/raw/rel-18/29_series/29510/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/raw/rel-18/29_series/29510/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba9ba5eb18529851df50abf7bb91615546fc3eed --- /dev/null +++ b/raw/rel-18/29_series/29510/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f154b249a8527726d003145c36f5b65b2d6b4e2ae2c927c83857fe8c26dbaaf2 +size 36127 diff --git a/raw/rel-18/29_series/29510/9ff1b32449ea068bba9647d71904bd59_img.jpg b/raw/rel-18/29_series/29510/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3175a088289cc442b25bad8180b87e730bbab302 --- /dev/null +++ b/raw/rel-18/29_series/29510/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07b2b1ff664e2a1f2b0be079e0bc6cf36bf3bdfaae699e065b6701a379f55239 +size 39381 diff --git a/raw/rel-18/29_series/29510/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/raw/rel-18/29_series/29510/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30f792fbc335894ca316a715553727d05ab84c46 --- /dev/null +++ b/raw/rel-18/29_series/29510/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:867573f4a8f71c7edc75ea864da351cc5555aec89038445a5d70ef495ba5486c +size 47993 diff --git a/raw/rel-18/29_series/29510/b560268ea8f6526970f23f0da225b099_img.jpg b/raw/rel-18/29_series/29510/b560268ea8f6526970f23f0da225b099_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94ec07c8712e18f7bcf13c922b3b6bc346b20727 --- /dev/null +++ b/raw/rel-18/29_series/29510/b560268ea8f6526970f23f0da225b099_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3419d79d4e7a311f7b293e6eb71b4dd8b077e569af9198fbac89d2d0d86d5e6 +size 46400 diff --git a/raw/rel-18/29_series/29510/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/raw/rel-18/29_series/29510/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba85f8be3ee497309392bd187fc6b4e0723ed474 --- /dev/null +++ b/raw/rel-18/29_series/29510/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c742bc9e37bc34d80741304ffc2641b9dcd5e940e03e8107d5fce92dd2dfb46 +size 49513 diff --git a/raw/rel-18/29_series/29510/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/raw/rel-18/29_series/29510/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c41289fd4753d7860932e869f409702f0651282 --- /dev/null +++ b/raw/rel-18/29_series/29510/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38b539c02838730f2f317f1296a4efee14836a0f01e3be4f0ee97a97b9e5c390 +size 38631 diff --git a/raw/rel-18/29_series/29510/cf734b5645d3e02a8df25f67904cd2d3_img.jpg b/raw/rel-18/29_series/29510/cf734b5645d3e02a8df25f67904cd2d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db4f33ceff075eeb7c83f5cabe1fda5e5938a49 --- /dev/null +++ b/raw/rel-18/29_series/29510/cf734b5645d3e02a8df25f67904cd2d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8e51dde10f0ee063e26e539d6b782d66f374a936b2f89a33226112729720a1a +size 41831 diff --git a/raw/rel-18/29_series/29510/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/29_series/29510/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da63c1af7ef195b786224f8e5050ae8cb3385552 --- /dev/null +++ b/raw/rel-18/29_series/29510/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7504d01a1e4bde3fbd4f858890545314dcade738e65d279833426fc552df8ec6 +size 39652 diff --git a/raw/rel-18/29_series/29510/dfaa8b98082261913dac00eae86b2889_img.jpg b/raw/rel-18/29_series/29510/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..730e834dfba0eb2f36e22797123a7c6775b1b51f --- /dev/null +++ b/raw/rel-18/29_series/29510/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:020659772a4e9a45e0add35e4a30ede766ccdccec5934eddedc6c404553290cd +size 33440 diff --git a/raw/rel-18/29_series/29510/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg b/raw/rel-18/29_series/29510/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9385c78616ab045960d65d7d9a6423beef811c35 --- /dev/null +++ b/raw/rel-18/29_series/29510/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5d70a7965e5c046156cbb68f2f563620542c6dc5dcaed657d322794fbe214ff +size 36062 diff --git a/raw/rel-18/29_series/29510/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/29_series/29510/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ac5bbef305052cc1a8346773d22e7786733c0a --- /dev/null +++ b/raw/rel-18/29_series/29510/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:957faa1538b7def98938b14121a0f867f736f8cb3069b95a7f3496a535179ab2 +size 32830 diff --git a/raw/rel-18/29_series/29510/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/raw/rel-18/29_series/29510/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66818db6943e2803823548012780c37c65513293 --- /dev/null +++ b/raw/rel-18/29_series/29510/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e271b7f733be3df102887efe718770f202d8c7a779fd4aa06aa48be11fdac5 +size 40334 diff --git a/raw/rel-18/29_series/29511/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/raw/rel-18/29_series/29511/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14d8d380f03fd61c7e73c857b9de207d03fe39ca --- /dev/null +++ b/raw/rel-18/29_series/29511/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81dffd70f99edd54111738a430e848bd6e2d0e656f8dca5c64a6951558066ae4 +size 36205 diff --git a/raw/rel-18/29_series/29511/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29511/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40a9c22e02bb4a71ffb514941e7262d91eea18db --- /dev/null +++ b/raw/rel-18/29_series/29511/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d5a8981bf999a4c044f0f10ac294385b5e186d1928dfc4b6bddf75cbab35efe +size 9504 diff --git a/raw/rel-18/29_series/29511/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29511/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8100a15c900e98697870ba4c1afddbe7c9b3ee68 --- /dev/null +++ b/raw/rel-18/29_series/29511/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb40bc9f76c66728d07c34b52e7e2c983ae7e9e2ffb632d60220ebfd237c17a3 +size 5694 diff --git a/raw/rel-18/29_series/29511/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/raw/rel-18/29_series/29511/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3bc26e75d04b00ebcf61c56dd1dfbc31707a58f --- /dev/null +++ b/raw/rel-18/29_series/29511/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b51aff4aa4a971aaf23d39171c259f0b0b9e552f392d74a807aac8bf35c1df00 +size 12799 diff --git a/raw/rel-18/29_series/29511/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg b/raw/rel-18/29_series/29511/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..363abe009bc550c8bb540f57917b2f67dd1b6e93 --- /dev/null +++ b/raw/rel-18/29_series/29511/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:604618c1fe7d128064c3977208355a4251592a6d4831df39893cb0cac18780f8 +size 12093 diff --git a/raw/rel-18/29_series/29511/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/raw/rel-18/29_series/29511/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efdddb00bb1babc8f23fd3bacca39a9890e462c7 --- /dev/null +++ b/raw/rel-18/29_series/29511/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a3e41d94615a4caa0cbbb2b5ee6a8eaf63c7a5f55b97fd0d89e9221f28e94c6 +size 12904 diff --git a/raw/rel-18/29_series/29517/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/raw/rel-18/29_series/29517/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fca94f5fa410f0d0ea89a2de5025871a44506fec --- /dev/null +++ b/raw/rel-18/29_series/29517/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4507e6900b46debdfe1bf129dcd6ad475a3f90bc74c39900d4cf5e1c02a3498c +size 31636 diff --git a/raw/rel-18/29_series/29517/426efb7efdc753a13f2fa16f7bff9429_img.jpg b/raw/rel-18/29_series/29517/426efb7efdc753a13f2fa16f7bff9429_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcadf04cd04e144ceddc1442ea074507902055e1 --- /dev/null +++ b/raw/rel-18/29_series/29517/426efb7efdc753a13f2fa16f7bff9429_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beab815299eb6681f90e06f8ed91861fd87d35d890b559cc25956af2bd0b972c +size 27986 diff --git a/raw/rel-18/29_series/29517/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg b/raw/rel-18/29_series/29517/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ba6351693b4ce97c0105d6c36332f13e778404a --- /dev/null +++ b/raw/rel-18/29_series/29517/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a819b2fed87cc4e3de4e15fc58b23aeeeb7111fb363f1c748a11e6a32fe795 +size 33128 diff --git a/raw/rel-18/29_series/29517/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/raw/rel-18/29_series/29517/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f88edb7e70fa1f548fa3e386d3187497487b8761 --- /dev/null +++ b/raw/rel-18/29_series/29517/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83686d2eb6a5f1824f2c7a66dce01b1a334ed4e487417e6111454a70e3490a61 +size 29976 diff --git a/raw/rel-18/29_series/29517/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29517/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de --- /dev/null +++ b/raw/rel-18/29_series/29517/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7 +size 9370 diff --git a/raw/rel-18/29_series/29517/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29517/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfa0d229082ecb7f2e23102ee7673d2a2cf03c76 --- /dev/null +++ b/raw/rel-18/29_series/29517/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb776af0de14b4c8128e6942a0e4c9865e7e854af32e2934cb82ad5032d68eb +size 5342 diff --git a/raw/rel-18/29_series/29517/aa9441a5971655a79987d70fc551b26a_img.jpg b/raw/rel-18/29_series/29517/aa9441a5971655a79987d70fc551b26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d1446a5c45b3e4ff8dc67a5ec9f51700f96c834 --- /dev/null +++ b/raw/rel-18/29_series/29517/aa9441a5971655a79987d70fc551b26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fc4ee514af087a84d2577f581e8dba06cf74712e11e0d76efc06386d7699869 +size 28760 diff --git a/raw/rel-18/29_series/29517/b0211cee4b20034939d883ac0d70f696_img.jpg b/raw/rel-18/29_series/29517/b0211cee4b20034939d883ac0d70f696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fde8db9c793b85968e5a0969f2bee60d1625c23e --- /dev/null +++ b/raw/rel-18/29_series/29517/b0211cee4b20034939d883ac0d70f696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:680decb9293174cbf44a22ee013b3b1f5da1135ed114b16f985f69d77365ffeb +size 25971 diff --git a/raw/rel-18/29_series/29517/c42e926097d01653b793c04b49e764b2_img.jpg b/raw/rel-18/29_series/29517/c42e926097d01653b793c04b49e764b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fab34f045c16876fc204a3e72e8aaffbd916627d --- /dev/null +++ b/raw/rel-18/29_series/29517/c42e926097d01653b793c04b49e764b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fc96db9254fd8243543a221d2327a0c8e6a136379b55c3794b5186e74cec04a +size 20134 diff --git a/raw/rel-18/29_series/29518/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/29_series/29518/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b26e126e954085a55c33fd9d36f05692f89b10b5 --- /dev/null +++ b/raw/rel-18/29_series/29518/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82faeef6e0725c6f81f7d1f6209757c8b4402976165c3dabf0756bc556aac96e +size 33099 diff --git a/raw/rel-18/29_series/29518/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/raw/rel-18/29_series/29518/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56824d246c90d062145d28884ec30c5f705cc4f9 --- /dev/null +++ b/raw/rel-18/29_series/29518/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78aa2a75c5a429f03ac8a1f658fd949a8cf0e78779efc8bd9d32fca7dae5badf +size 36841 diff --git a/raw/rel-18/29_series/29518/04cfca33e3fc26513abe649d7474f733_img.jpg b/raw/rel-18/29_series/29518/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b946960053be4a193016b5fc5477402d277b594 --- /dev/null +++ b/raw/rel-18/29_series/29518/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:198eb580e9d575bdbedeccfcd9bb7d87bae2250f73d3586a2d1a3d5d4a34213e +size 33004 diff --git a/raw/rel-18/29_series/29518/0977b81510f7649846289ee785d20e74_img.jpg b/raw/rel-18/29_series/29518/0977b81510f7649846289ee785d20e74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e50daab578223094ceea13b771b99e172507bc6f --- /dev/null +++ b/raw/rel-18/29_series/29518/0977b81510f7649846289ee785d20e74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9572e423fece491d5172068fdda45caa85624d29d0f60c63871babf47979137a +size 17364 diff --git a/raw/rel-18/29_series/29518/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/raw/rel-18/29_series/29518/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7194f914a9ab2ea0c478b94d73c32c9a6415d29 --- /dev/null +++ b/raw/rel-18/29_series/29518/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d19ffbcb072f90286065d59fa8abc6069d3d117a00b6254532b2d50b9b8415a +size 36797 diff --git a/raw/rel-18/29_series/29518/187d05bf7ead21e1394b61320d8b3632_img.jpg b/raw/rel-18/29_series/29518/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42006d69dc7b2a47eab3bb29913cab13aeab0774 --- /dev/null +++ b/raw/rel-18/29_series/29518/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fdd703369928f53c4bd7f4793f1ea8e85d0c589b6c41b0ccede89f28b8ffd1a +size 41052 diff --git a/raw/rel-18/29_series/29518/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg b/raw/rel-18/29_series/29518/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fca5e240e3aec558ba235f7fb13b616d6b6d833 --- /dev/null +++ b/raw/rel-18/29_series/29518/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2408a88f305e850182d9c72145db0dd98b72223aa76767a3fbf3c96cd25c5af7 +size 36486 diff --git a/raw/rel-18/29_series/29518/26e334e61dd059cff029338a2a604d8d_img.jpg b/raw/rel-18/29_series/29518/26e334e61dd059cff029338a2a604d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c25643c1ab3be063b5d43834dd2d343d651a49ac --- /dev/null +++ b/raw/rel-18/29_series/29518/26e334e61dd059cff029338a2a604d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccc647002a4d4879d4bf438ebafaa12979a2f40d9bca7151b463b4143b687c64 +size 34333 diff --git a/raw/rel-18/29_series/29518/314da473d582c4327e1e3d56fcba19dd_img.jpg b/raw/rel-18/29_series/29518/314da473d582c4327e1e3d56fcba19dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ade8a1d6e5fb3767236c0aee1e2df0249e0256c2 --- /dev/null +++ b/raw/rel-18/29_series/29518/314da473d582c4327e1e3d56fcba19dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37ab6e18d65a0d905d2a256f5baacea61754d8ab79b058e68337a0d8ae734d1c +size 37595 diff --git a/raw/rel-18/29_series/29518/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/raw/rel-18/29_series/29518/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d01591d73f24114946a5d7c3cc5c5bd04e65a8c5 --- /dev/null +++ b/raw/rel-18/29_series/29518/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c66d04ccfd461c76dab9ab0a6d9351ef005cb9742cb7c14ecd089c488b0ebe4 +size 32752 diff --git a/raw/rel-18/29_series/29518/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg b/raw/rel-18/29_series/29518/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78e6444b6d29f09595c3d7facb73854e72655485 --- /dev/null +++ b/raw/rel-18/29_series/29518/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba00e707136ba46f0ad46afaf2e1ee0b96f0e28f7a54fce107176064e2ff391c +size 32193 diff --git a/raw/rel-18/29_series/29518/44b5421412b6a548e6e32adda52dfeab_img.jpg b/raw/rel-18/29_series/29518/44b5421412b6a548e6e32adda52dfeab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3b5474042e5c70fe8ec109409f151227a9c9e95 --- /dev/null +++ b/raw/rel-18/29_series/29518/44b5421412b6a548e6e32adda52dfeab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a58411ef408450ff4a6ca7c5bc7a18d568b230f0eb080f8618de458b1ffd871 +size 27920 diff --git a/raw/rel-18/29_series/29518/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/raw/rel-18/29_series/29518/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e7e792ca25ba01eba97d171d6498201746a79a9 --- /dev/null +++ b/raw/rel-18/29_series/29518/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbc7a8270a9b142535375591f33a5e0f9b09cffd947cfac40b7d985f3d56e134 +size 34571 diff --git a/raw/rel-18/29_series/29518/4f2887d5043c0923cf5b37ca0d80c60b_img.jpg b/raw/rel-18/29_series/29518/4f2887d5043c0923cf5b37ca0d80c60b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34388d85f85226e5b6866a7d4bc6315b9db0563e --- /dev/null +++ b/raw/rel-18/29_series/29518/4f2887d5043c0923cf5b37ca0d80c60b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:289e361f6c07aaf199f22d76bda90178134e01435578d90c0c9fbd7fd1dafdca +size 33097 diff --git a/raw/rel-18/29_series/29518/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/raw/rel-18/29_series/29518/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4efcf7aaf8e09398c8690b104a29e7e4978355e --- /dev/null +++ b/raw/rel-18/29_series/29518/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4616fa2319f4a99b67ff00273827cc14ca5c2378b603e49c6e631ce4d480132e +size 34830 diff --git a/raw/rel-18/29_series/29518/5e9af8986a5845504f251d3079da8078_img.jpg b/raw/rel-18/29_series/29518/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e2211afc40535a2f634524593a7816b3469b0cc --- /dev/null +++ b/raw/rel-18/29_series/29518/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1be3da9fb1f5c71613d0f32abd6ab621101c6206d70bca57631c0074ebc76bc +size 35338 diff --git a/raw/rel-18/29_series/29518/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29518/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c84717fc9832f1402fb25d8ad4596d56fde3d762 --- /dev/null +++ b/raw/rel-18/29_series/29518/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a048f1057cc19897dc4bb0fc6647da7fcafaa774d5e2a63a411c1d20b05096 +size 9544 diff --git a/raw/rel-18/29_series/29518/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29518/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e98b7579ce2a82399d39e0c4bd627c45aaf1ef5 --- /dev/null +++ b/raw/rel-18/29_series/29518/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1356eef000c0103bf107ac7c565d563c59021cce0095a80390310fd6814f949c +size 5490 diff --git a/raw/rel-18/29_series/29518/6470d350326789d5306eabcb76533951_img.jpg b/raw/rel-18/29_series/29518/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff6e2f40e458a62e466bac68ed32f9302258241d --- /dev/null +++ b/raw/rel-18/29_series/29518/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc9acceb7abd6f776a682552ad52b103b1e8338c562d3ccc6bdc207e0e522da0 +size 44601 diff --git a/raw/rel-18/29_series/29518/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/raw/rel-18/29_series/29518/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcc3304b8f22fd033bf6b4a6546dce5bf1b71dc5 --- /dev/null +++ b/raw/rel-18/29_series/29518/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c6d1a7b717853774f17a70cd5e54250d587050070c6c4c0921f2add5fa8fa48 +size 43123 diff --git a/raw/rel-18/29_series/29518/681dffd423541f7ba0c17aedcbef4959_img.jpg b/raw/rel-18/29_series/29518/681dffd423541f7ba0c17aedcbef4959_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af25e04da8d8b774f9f15f77a91471e5511a97d6 --- /dev/null +++ b/raw/rel-18/29_series/29518/681dffd423541f7ba0c17aedcbef4959_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e1072df73b1631354e4e67f0230516d135c2cf712a5b0aa960b6848202db8fb +size 39058 diff --git a/raw/rel-18/29_series/29518/6835f8f6a39e5504463c9a73f0c58674_img.jpg b/raw/rel-18/29_series/29518/6835f8f6a39e5504463c9a73f0c58674_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e6afc22963a18363d57cc00dd2383d89006ad2a --- /dev/null +++ b/raw/rel-18/29_series/29518/6835f8f6a39e5504463c9a73f0c58674_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:899a161580e233ee32097a8f8301a1b2fb3f3378bcb86cfa148088b34af9be67 +size 30427 diff --git a/raw/rel-18/29_series/29518/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/raw/rel-18/29_series/29518/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62fc90a85f22340e7921acbf9b172ab454396536 --- /dev/null +++ b/raw/rel-18/29_series/29518/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31e0ca528a83d0f371c5919c3ed3c9ff14f1f3fd8f4c792d2dfb17344384aca8 +size 39542 diff --git a/raw/rel-18/29_series/29518/7355f66b8620d44cf566215621addb74_img.jpg b/raw/rel-18/29_series/29518/7355f66b8620d44cf566215621addb74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c1a1774a64213d734f868a2f3cadaf1bef98b52 --- /dev/null +++ b/raw/rel-18/29_series/29518/7355f66b8620d44cf566215621addb74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fca9eb3b26d2d9ecf23ea42778f1c0e3e39200f08673eabefe0a4d91a60ba24 +size 30530 diff --git a/raw/rel-18/29_series/29518/78de09c382ab51b5c3e87979204228c8_img.jpg b/raw/rel-18/29_series/29518/78de09c382ab51b5c3e87979204228c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7dc4dc91c5f6724c103c5bdd5cc8076d558195c --- /dev/null +++ b/raw/rel-18/29_series/29518/78de09c382ab51b5c3e87979204228c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d73c52f68336b6c6a211b838972bc6532bf0bee15c12f7a3c86f2d24bb82bce +size 86110 diff --git a/raw/rel-18/29_series/29518/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29518/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc08a5809cdac44b87a60a6e7302d5bc7f68b221 --- /dev/null +++ b/raw/rel-18/29_series/29518/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f55557445f88572c5b3c1c0a8528ce6a1290641749b044f1dcebdf2f6fd2986 +size 45400 diff --git a/raw/rel-18/29_series/29518/8269648391c59363ea61243864a2adf7_img.jpg b/raw/rel-18/29_series/29518/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0057ff34b29c45284236ac04a015831e5408a1ca --- /dev/null +++ b/raw/rel-18/29_series/29518/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d533521a525c39a655942ca6bc7fb3bb9d3673c1c5aee980f7fcd60828ec167 +size 37796 diff --git a/raw/rel-18/29_series/29518/921458d4fc1b778c2450592ac9745b48_img.jpg b/raw/rel-18/29_series/29518/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4fe6ea97189f4044c525f95bd0687b7be0ce0de --- /dev/null +++ b/raw/rel-18/29_series/29518/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c20408dc3693d403cffad0e428df408bea5e0a54d0f7262cbbb28c444b41b7d6 +size 39665 diff --git a/raw/rel-18/29_series/29518/9cd7ec4a653f07d02def283cb6f2309e_img.jpg b/raw/rel-18/29_series/29518/9cd7ec4a653f07d02def283cb6f2309e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc4dd5aef884e1aa41f9fe37e0f88312870fad1c --- /dev/null +++ b/raw/rel-18/29_series/29518/9cd7ec4a653f07d02def283cb6f2309e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bea6d0afec18093f4e979338e8c1dcb23b1b872a88d8b8e677b429e3eae15ab +size 32226 diff --git a/raw/rel-18/29_series/29518/9e5ebd04b22b9fa09c82a10a81129278_img.jpg b/raw/rel-18/29_series/29518/9e5ebd04b22b9fa09c82a10a81129278_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86d116bcc145a9ce1b9313e5069b034954de7f9b --- /dev/null +++ b/raw/rel-18/29_series/29518/9e5ebd04b22b9fa09c82a10a81129278_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db81380d82ce9cf141614059e1fec937fad440b74528e4fbfa44255fbf91c2f0 +size 41816 diff --git a/raw/rel-18/29_series/29518/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg b/raw/rel-18/29_series/29518/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bd210146696afb6e1a54e9fe1c297b5c583de64 --- /dev/null +++ b/raw/rel-18/29_series/29518/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e6d35ededc30637fc7120e6a33ce39bdd89e1826a9c286eb6a05bc674814cfb +size 37841 diff --git a/raw/rel-18/29_series/29518/9edb407536d4d4d4a6ac391527af047c_img.jpg b/raw/rel-18/29_series/29518/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9cd2fe8c7b4eaea300e6685093ea8b556abcb61 --- /dev/null +++ b/raw/rel-18/29_series/29518/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:927cc93980947a61d512182ef746f66705841d26e927ac30bcfd50565085b40f +size 37983 diff --git a/raw/rel-18/29_series/29518/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/29_series/29518/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d11fb8c44d89b6046443723701c3997bd381226 --- /dev/null +++ b/raw/rel-18/29_series/29518/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e2e8341a043bfe3918dce0e9623ffa9054b1b3527ee50227a24b2cc0213cb24 +size 45190 diff --git a/raw/rel-18/29_series/29518/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg b/raw/rel-18/29_series/29518/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86cd5bae169a10fb26827027981ba199c92a0f22 --- /dev/null +++ b/raw/rel-18/29_series/29518/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7dc5f8bf079e6c69ca5d9ad30a25a23ad34bea60ba7707b05a7f4e70c5f7384 +size 35535 diff --git a/raw/rel-18/29_series/29518/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg b/raw/rel-18/29_series/29518/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b82a299e6dfe693999d80df9c97394071c202e81 --- /dev/null +++ b/raw/rel-18/29_series/29518/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0741c5cd93ad8565476553f7b706402539b75cc67d42b66805d62f9e92d0e2c +size 33341 diff --git a/raw/rel-18/29_series/29518/ae375ead8aa673286b534e079e9a8533_img.jpg b/raw/rel-18/29_series/29518/ae375ead8aa673286b534e079e9a8533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1387876c139d3021f4dc0593123794a083060cd3 --- /dev/null +++ b/raw/rel-18/29_series/29518/ae375ead8aa673286b534e079e9a8533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b364515b7466062fb8f6edd69fe251b3af2b176e2dd7f0d694a027789e8828e +size 33614 diff --git a/raw/rel-18/29_series/29518/b303fb8b2c64e30aac9c32b5753d3670_img.jpg b/raw/rel-18/29_series/29518/b303fb8b2c64e30aac9c32b5753d3670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd0e9c0fc0307291cf69e6080fb904d3da811226 --- /dev/null +++ b/raw/rel-18/29_series/29518/b303fb8b2c64e30aac9c32b5753d3670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c309e4079106c207346256dcec64502071bac4dbd3cbe2767f490d25d15ff656 +size 14492 diff --git a/raw/rel-18/29_series/29518/b97737027bd1b2effd7ca4dba8914877_img.jpg b/raw/rel-18/29_series/29518/b97737027bd1b2effd7ca4dba8914877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9652148f44f23fa433baaa59d5a28524aa8eb77b --- /dev/null +++ b/raw/rel-18/29_series/29518/b97737027bd1b2effd7ca4dba8914877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:164618c72a8c49f847c539afe613dcefc961b0798732dda2797585e81fc66b9a +size 39986 diff --git a/raw/rel-18/29_series/29518/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/raw/rel-18/29_series/29518/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..096ae94c7b02c5dcee66d63cebf3c0663f64e1bc --- /dev/null +++ b/raw/rel-18/29_series/29518/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac8dafa17bcfe32c5812185a12e45c60e6743cb34e0ec4c08a9b49437cd3150e +size 40539 diff --git a/raw/rel-18/29_series/29518/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/raw/rel-18/29_series/29518/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa7531da644cad203f0800552db0ac9e42945e8d --- /dev/null +++ b/raw/rel-18/29_series/29518/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4881832930b8bc521aee73e092335cbac27af348ff98eb97937d9285f7f0930c +size 14426 diff --git a/raw/rel-18/29_series/29518/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg b/raw/rel-18/29_series/29518/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3283b5feda60fb35733ec535a3aa4d9444144db6 --- /dev/null +++ b/raw/rel-18/29_series/29518/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94a6b9524788c7f0f55c003ab8cc76c668b5b8562c557a1cfc62296713856fa9 +size 32626 diff --git a/raw/rel-18/29_series/29518/dbcb760c24ceea4fb409492e549777e5_img.jpg b/raw/rel-18/29_series/29518/dbcb760c24ceea4fb409492e549777e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..740babce0cde6f864f6da5c5c6039c9ae79d6a75 --- /dev/null +++ b/raw/rel-18/29_series/29518/dbcb760c24ceea4fb409492e549777e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:272c2ca9019bc72f890482a96c5f2243379f7d81fb710d539627f8089df75cda +size 36986 diff --git a/raw/rel-18/29_series/29518/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg b/raw/rel-18/29_series/29518/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e36c300cf3237306118358a773d8ebf0c86d7f3f --- /dev/null +++ b/raw/rel-18/29_series/29518/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08edbe5660f8b671f95105fcd8628ebac64068859ae8fe58b959697490429a61 +size 15160 diff --git a/raw/rel-18/29_series/29518/e59fc6db8cfc5ea2b861f3c59a03eaf3_img.jpg b/raw/rel-18/29_series/29518/e59fc6db8cfc5ea2b861f3c59a03eaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15a0d58c3d31741c306ab37f1bb436849cabd7d --- /dev/null +++ b/raw/rel-18/29_series/29518/e59fc6db8cfc5ea2b861f3c59a03eaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af63247f027747e29ea0ddc07d01587be494b936f4d8c623031322bb8343e853 +size 6512 diff --git a/raw/rel-18/29_series/29518/e90987faabad6a6665cd8ed1151dc474_img.jpg b/raw/rel-18/29_series/29518/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2454405b8e3593f654f5d1b77732f8953825cfa4 --- /dev/null +++ b/raw/rel-18/29_series/29518/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1148331523ea2e2f49fb54c452c24113a84539149b71987ed8d2c7222c9fb3e3 +size 39498 diff --git a/raw/rel-18/29_series/29518/f00bfb547ad2bc48f7d04944cbedcb8e_img.jpg b/raw/rel-18/29_series/29518/f00bfb547ad2bc48f7d04944cbedcb8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28650aa04704c1571fb7c7f242138bb0e529b4d2 --- /dev/null +++ b/raw/rel-18/29_series/29518/f00bfb547ad2bc48f7d04944cbedcb8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:752a967615841ca368fd7bb4c6bd6c1be78ed914a17536ff0b2ad17de6fbd159 +size 18235 diff --git a/raw/rel-18/29_series/29518/f10dc32e3673e1392029a49e958a9d6c_img.jpg b/raw/rel-18/29_series/29518/f10dc32e3673e1392029a49e958a9d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54696a431387dc6e53a6b53678c51600ab4e3247 --- /dev/null +++ b/raw/rel-18/29_series/29518/f10dc32e3673e1392029a49e958a9d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3133918eed130779a2fd7c7bdb3ce1201f5125ec45c42436b0f8013739f5d636 +size 38111 diff --git a/raw/rel-18/29_series/29518/f14f0843f9944e61124817d06809d7ad_img.jpg b/raw/rel-18/29_series/29518/f14f0843f9944e61124817d06809d7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c8df3d87e87bb5233282a32d53e399891b1aab6 --- /dev/null +++ b/raw/rel-18/29_series/29518/f14f0843f9944e61124817d06809d7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21fdddd731225ce2ba2ac58aa9eb107fe06496fef5b1605f2cd26a41dcc439f0 +size 32369 diff --git a/raw/rel-18/29_series/29518/f609bd3fda53d5be094991a96addbf84_img.jpg b/raw/rel-18/29_series/29518/f609bd3fda53d5be094991a96addbf84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b224caabcfaad75aa851be8f4b3c8ffd70578d71 --- /dev/null +++ b/raw/rel-18/29_series/29518/f609bd3fda53d5be094991a96addbf84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:393dc017177add4b8104b01aa99066804f25c18bc80cfd032d778c89c347781c +size 33885 diff --git a/raw/rel-18/29_series/29518/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg b/raw/rel-18/29_series/29518/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f646f367878e99b93a720b71d1e5aa6f43e472bb --- /dev/null +++ b/raw/rel-18/29_series/29518/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a21c1b1a532294760032673cf6537a001133b30e67aa49f1f4b66e1b49071ae +size 37250 diff --git a/raw/rel-18/29_series/29518/ffb6acd27b8e3a54392840948a75869f_img.jpg b/raw/rel-18/29_series/29518/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed1758486c73567270fbb9b9ebc2995a8664b5bc --- /dev/null +++ b/raw/rel-18/29_series/29518/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48ccb3f4fb6a8ddeeff5c95e1dc3f770d40cdb8b59458ea4bdb55007b185f99f +size 43951 diff --git a/raw/rel-18/29_series/29519/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/29_series/29519/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8289f5bcda4aade790489f610f5a57fd9a03e19c --- /dev/null +++ b/raw/rel-18/29_series/29519/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d63651a6167e5b021190d78c61e030d760fe66efc8d09422ba6b5ca4d0b5bf28 +size 110635 diff --git a/raw/rel-18/29_series/29519/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29519/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f05292f7828cf69ee875a85eb0c64ef7288ddf4d --- /dev/null +++ b/raw/rel-18/29_series/29519/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:338cf2ce29350c6b629433f9cd0b0c35025bdc96800b7a0f955b590d768c0890 +size 9324 diff --git a/raw/rel-18/29_series/29519/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29519/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..165d6b2a32ff675437cf1cd496a43e1671dcadca --- /dev/null +++ b/raw/rel-18/29_series/29519/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1f8db982a32b56e11f20e3a53415766a194668048f6c29d2c7b8d9c92b45c8a +size 5672 diff --git a/raw/rel-18/29_series/29519/e7010c66da16316c2935dfbbef5056b3_img.jpg b/raw/rel-18/29_series/29519/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc31c6a0c5f5de3f6a29e8b4e476e9a593020dfa --- /dev/null +++ b/raw/rel-18/29_series/29519/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3d082db0b6277e537c5239047d1aed4ce4187594253858c5bcff726126d608e +size 97448 diff --git a/raw/rel-18/29_series/29519/ec838a9b247a8176f8dec125c9d198ab_img.jpg b/raw/rel-18/29_series/29519/ec838a9b247a8176f8dec125c9d198ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e5fd18b9a0f3c91acb9523cb6f641fc4e8662fa --- /dev/null +++ b/raw/rel-18/29_series/29519/ec838a9b247a8176f8dec125c9d198ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecb71505d5ddec6a2a60c8ca93e29fde1f3ea059bf780d25ff4babb68d119580 +size 49642 diff --git a/raw/rel-18/29_series/29520/00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg b/raw/rel-18/29_series/29520/00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a08f25d3d82e36bf07de44c45cdc0227c4d8b42 --- /dev/null +++ b/raw/rel-18/29_series/29520/00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd6721386aa8be32b1f7022c3ad4c4db607a32d86d99c54ee3d5c2eb6c47ee7e +size 24952 diff --git a/raw/rel-18/29_series/29520/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/raw/rel-18/29_series/29520/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..089a0532f816e6b1591e6523a67eaabd3be00e92 --- /dev/null +++ b/raw/rel-18/29_series/29520/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4639fb00f550ec81a523773c4c8fb465690cfa09b6307c43441aed1a1a900d4e +size 28019 diff --git a/raw/rel-18/29_series/29520/05da2a3257316bbf6f448a830dc0380a_img.jpg b/raw/rel-18/29_series/29520/05da2a3257316bbf6f448a830dc0380a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..058a8d9efd9927d21fcb19d8d20bf44a5cebfdb4 --- /dev/null +++ b/raw/rel-18/29_series/29520/05da2a3257316bbf6f448a830dc0380a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6ea3df077bb104d68e136c1e13578ceb630ded36daf22a07406680a34ac81e6 +size 30553 diff --git a/raw/rel-18/29_series/29520/0931f3e098bd4539041de11c50cec2d2_img.jpg b/raw/rel-18/29_series/29520/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18926f04a19c76d3d52e23b3dc5a538da8ebbdfe --- /dev/null +++ b/raw/rel-18/29_series/29520/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c920bc2dafa2bdd6ca796af15a4a658395a7a90d5d40eabdedcbff1b9cfe391 +size 7101 diff --git a/raw/rel-18/29_series/29520/0a73b03fba21af142d619a9a662e6490_img.jpg b/raw/rel-18/29_series/29520/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01ced34701feba0d7ad0f19b728563e2eee7c890 --- /dev/null +++ b/raw/rel-18/29_series/29520/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2ddac8a5662f3ea2be1e8864924ca569e2daecd10dcdf7d6e5389b79af42a83 +size 32329 diff --git a/raw/rel-18/29_series/29520/11f18bf0233d812ad2604f88f3385d60_img.jpg b/raw/rel-18/29_series/29520/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0c228dea52fe4f6d86143daaff9bb2f03a8bf7e --- /dev/null +++ b/raw/rel-18/29_series/29520/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07b4eabe8f61b9c93594727ffb3fee496adf4786252c9155c98fd49aa321bc1f +size 32823 diff --git a/raw/rel-18/29_series/29520/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/raw/rel-18/29_series/29520/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47a61025cad3a0cf1e6c60e6f7b14d323d09015e --- /dev/null +++ b/raw/rel-18/29_series/29520/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19f6c6d47eee495f448fe53850c2b4c90c14c72eb6c4aee3a408cfb6f203e025 +size 25645 diff --git a/raw/rel-18/29_series/29520/1878426572e3fcbc4483578a685d7c7d_img.jpg b/raw/rel-18/29_series/29520/1878426572e3fcbc4483578a685d7c7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42f45b972d9869463011da224ecbe0a1cfcd97c9 --- /dev/null +++ b/raw/rel-18/29_series/29520/1878426572e3fcbc4483578a685d7c7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94bcb86573efadf9c20214ef7317b7b20fe92447833228c2c3e33a9711f5e098 +size 32862 diff --git a/raw/rel-18/29_series/29520/187d05bf7ead21e1394b61320d8b3632_img.jpg b/raw/rel-18/29_series/29520/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a0abfbf0ab29feb001e2b2bfac5b20159e7d367 --- /dev/null +++ b/raw/rel-18/29_series/29520/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8466e5a462f09ccf2615aaf332fa6e46229d1f478d4d184431dedf7655185cf8 +size 34455 diff --git a/raw/rel-18/29_series/29520/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/raw/rel-18/29_series/29520/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a6ed26af582541e078dadcb9950786dc4415c8c --- /dev/null +++ b/raw/rel-18/29_series/29520/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed0c23810859a48b886a01282648b94ba76eb48f41f07b6613369d14a55c7bf +size 26443 diff --git a/raw/rel-18/29_series/29520/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg b/raw/rel-18/29_series/29520/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9d82092982f65d353339da3d501a26d87820cfb --- /dev/null +++ b/raw/rel-18/29_series/29520/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32696d8addf4e8f74d83145008add2201a77a4caea7a5875c9730bc530bed148 +size 30861 diff --git a/raw/rel-18/29_series/29520/1ba9045eb6dc22039a16b92b1427e696_img.jpg b/raw/rel-18/29_series/29520/1ba9045eb6dc22039a16b92b1427e696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8173902857f9eddd2aa2d65c701efb5d5dc729b3 --- /dev/null +++ b/raw/rel-18/29_series/29520/1ba9045eb6dc22039a16b92b1427e696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18630ce16653afff8fd93a290b9d2f28290c1510ae11c6f2fb5428c247b15057 +size 27479 diff --git a/raw/rel-18/29_series/29520/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/raw/rel-18/29_series/29520/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99ee97e20623c093ae313237c5f3e19b0095b12a --- /dev/null +++ b/raw/rel-18/29_series/29520/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc3c4f849823601ceb9684a4e05023e8f389dcfdc32332f080eb6cb9e777c2bc +size 29572 diff --git a/raw/rel-18/29_series/29520/20cb2d2cc18d663dc1b82453c67250bb_img.jpg b/raw/rel-18/29_series/29520/20cb2d2cc18d663dc1b82453c67250bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46b53ed6f3dcb67e635bd32d5fcea97568f5ef27 --- /dev/null +++ b/raw/rel-18/29_series/29520/20cb2d2cc18d663dc1b82453c67250bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cebb89ed3fb41c7746353688585cb25c2fd6e1ce70299654f0af3f608dc4309 +size 8514 diff --git a/raw/rel-18/29_series/29520/2a52834ffb60a618738d21bcc3ace1e3_img.jpg b/raw/rel-18/29_series/29520/2a52834ffb60a618738d21bcc3ace1e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab891f8f7fc9ca5f280db2451ca9a75cf8e4f0c5 --- /dev/null +++ b/raw/rel-18/29_series/29520/2a52834ffb60a618738d21bcc3ace1e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45f59acb990e55aed50733348fc65273b027ea03ab0a5d619a281b71a376b10c +size 30430 diff --git a/raw/rel-18/29_series/29520/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/raw/rel-18/29_series/29520/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f619efffe9d51a2f62d5c9725ca58cfe398acd1c --- /dev/null +++ b/raw/rel-18/29_series/29520/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acd150dba80f04697a54126186132c5ff4e8f1483b07909fb214a1e3b469df4b +size 29137 diff --git a/raw/rel-18/29_series/29520/3750b0149a6380885998ab3ca6a8787c_img.jpg b/raw/rel-18/29_series/29520/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d57cbcc86477edb6ec8cf549ed5dc37e487d8673 --- /dev/null +++ b/raw/rel-18/29_series/29520/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a0d532ca31e0cec7e998e24a2fd30305d2e1e038d7df2c9d904a7a60d233ed7 +size 29909 diff --git a/raw/rel-18/29_series/29520/38d82ffe820e339811b396206f40a201_img.jpg b/raw/rel-18/29_series/29520/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37a306c893d8638e2c90413f429fa356c20f9f41 --- /dev/null +++ b/raw/rel-18/29_series/29520/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9edb1b08ed682c485c05231cdfd92ee8bf6676dc8b7812b210d3ce2e00d0f741 +size 27001 diff --git a/raw/rel-18/29_series/29520/4390b89fdb95cba102ee1f88e218b07b_img.jpg b/raw/rel-18/29_series/29520/4390b89fdb95cba102ee1f88e218b07b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53a2e1eae5130453105f3344b901c679e498b1f4 --- /dev/null +++ b/raw/rel-18/29_series/29520/4390b89fdb95cba102ee1f88e218b07b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:042e801e9e6da57e1d1a6c5d09cf78eeaca76ad79120f49647aca8f6205a973b +size 34030 diff --git a/raw/rel-18/29_series/29520/4767b6e106f34fe8b63a6838810bf913_img.jpg b/raw/rel-18/29_series/29520/4767b6e106f34fe8b63a6838810bf913_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c735a28a77ad970d57f58b8b67165dac00e470d --- /dev/null +++ b/raw/rel-18/29_series/29520/4767b6e106f34fe8b63a6838810bf913_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e32a41f0d108ca6cee13106af943323b3cc7196731078807f4826dedfd19fab0 +size 27078 diff --git a/raw/rel-18/29_series/29520/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/raw/rel-18/29_series/29520/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7f4b1204d21944eec2316b686cb00ec8f3501f1 --- /dev/null +++ b/raw/rel-18/29_series/29520/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e2eef17a132500c4f3a6a8b3ea6c33d6748edf8bc56e7d28ccce2456e70bfa5 +size 23760 diff --git a/raw/rel-18/29_series/29520/57939c16065211317c5442cf2a4009e0_img.jpg b/raw/rel-18/29_series/29520/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd624cbbbb19487a4f39470c15254e54d784089a --- /dev/null +++ b/raw/rel-18/29_series/29520/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a98ad4fee76b53c8fd48ac7d3ab57afde437417b66e27962f0ac6c69680e323a +size 4387 diff --git a/raw/rel-18/29_series/29520/5ba26df60eea8e9b4688559e47cd9c0f_img.jpg b/raw/rel-18/29_series/29520/5ba26df60eea8e9b4688559e47cd9c0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cc51aebe942a3668e2b7d5e23af4a816617881d --- /dev/null +++ b/raw/rel-18/29_series/29520/5ba26df60eea8e9b4688559e47cd9c0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04c93a4be22f1e80b692d4f9b7a06c53d9aec8183e1766074ce522ddaf287037 +size 8052 diff --git a/raw/rel-18/29_series/29520/5e9af8986a5845504f251d3079da8078_img.jpg b/raw/rel-18/29_series/29520/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381cbb5035a6d6d3ec80f1774afc86092e0034fc --- /dev/null +++ b/raw/rel-18/29_series/29520/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04a5bf7aa195d867d62dc21aba00c727b120dc173729693a66be8b4674e32f28 +size 28881 diff --git a/raw/rel-18/29_series/29520/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29520/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd0dba2327d56c9161dd174d516c5dfb04f7a18d --- /dev/null +++ b/raw/rel-18/29_series/29520/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ccf0f596d3a3d048f37b20804a35c9363046328c3493f158bda02bf14f2cd3d +size 9853 diff --git a/raw/rel-18/29_series/29520/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29520/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2462c26d25276ed6653e714b9185c24d638b88c --- /dev/null +++ b/raw/rel-18/29_series/29520/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2feb07c62cc34319f5445c3c0780ddfaa444e08eddc64e8860c04602d53dc137 +size 5580 diff --git a/raw/rel-18/29_series/29520/67c5b121b58d497a6de5addf4e7bd555_img.jpg b/raw/rel-18/29_series/29520/67c5b121b58d497a6de5addf4e7bd555_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7242783910725cdfda181350eeb378d6ab555088 --- /dev/null +++ b/raw/rel-18/29_series/29520/67c5b121b58d497a6de5addf4e7bd555_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51b9108119a5b67107a59831222abff9088811b0e7e976e0fe818ec93a91f4b8 +size 30179 diff --git a/raw/rel-18/29_series/29520/67d03c9e89620d73e3786c869e559752_img.jpg b/raw/rel-18/29_series/29520/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa8a17401d3c3bb76783263440d483a84965f460 --- /dev/null +++ b/raw/rel-18/29_series/29520/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cd5468665f6064dfeb4c043b77da8449c72a0be55aa866f9f4fec3a901b20ff +size 35517 diff --git a/raw/rel-18/29_series/29520/688031e51a9a74ed869aa8405aab4e74_img.jpg b/raw/rel-18/29_series/29520/688031e51a9a74ed869aa8405aab4e74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03f95c5d19b9fb2e1bb9b59950df1ce226fc57ba --- /dev/null +++ b/raw/rel-18/29_series/29520/688031e51a9a74ed869aa8405aab4e74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98017a78d5376a319551a6c02e04d741836bfddd0801a4eb406bd3c3ad0a2ac6 +size 24195 diff --git a/raw/rel-18/29_series/29520/691626a7032a642bb74793336c37e274_img.jpg b/raw/rel-18/29_series/29520/691626a7032a642bb74793336c37e274_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1e57a3df2b383a425124b9ed9c31f3f5df8e51e --- /dev/null +++ b/raw/rel-18/29_series/29520/691626a7032a642bb74793336c37e274_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9db2d9971cf0611e5c59a0c4373c239566422890125c2095da1805f9a9fa2372 +size 10509 diff --git a/raw/rel-18/29_series/29520/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/raw/rel-18/29_series/29520/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5ef0a18f3ec393e3033eab8a48849c65caf6b76 --- /dev/null +++ b/raw/rel-18/29_series/29520/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1053389e78fe6090527ea4f3dc1b2f83d404856d0e89687e8daba089080c7612 +size 32789 diff --git a/raw/rel-18/29_series/29520/746339de60a18834270b45f3928c3e8a_img.jpg b/raw/rel-18/29_series/29520/746339de60a18834270b45f3928c3e8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..816cdc161c460965b0cda5f3e02ee60140328bee --- /dev/null +++ b/raw/rel-18/29_series/29520/746339de60a18834270b45f3928c3e8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15851a19120a26f8aeaf8750589c1f894dc2642a96a9a129e535225ded5474f0 +size 17089 diff --git a/raw/rel-18/29_series/29520/7afb1fd052c6df368128542f16088890_img.jpg b/raw/rel-18/29_series/29520/7afb1fd052c6df368128542f16088890_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381d1a2811cd7cea2c63dbec8ea6859e038c5ef4 --- /dev/null +++ b/raw/rel-18/29_series/29520/7afb1fd052c6df368128542f16088890_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e13f4d83575b4584f68ad5609774a3b3a559814576915e8b680b0c521ff2143b +size 23745 diff --git a/raw/rel-18/29_series/29520/7f663b2f8632236c6e40ca16272d62df_img.jpg b/raw/rel-18/29_series/29520/7f663b2f8632236c6e40ca16272d62df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59a4c81a8ea18073434e2bad120d232f8adc4140 --- /dev/null +++ b/raw/rel-18/29_series/29520/7f663b2f8632236c6e40ca16272d62df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3b77de3c69234874275dab00d46f3c39a171acae573542e358343ab2587cacc +size 23185 diff --git a/raw/rel-18/29_series/29520/8a94796989f4fcba2688c4faa7991538_img.jpg b/raw/rel-18/29_series/29520/8a94796989f4fcba2688c4faa7991538_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df5adac2bdb261fba508e89db3750d0ae7fd4c28 --- /dev/null +++ b/raw/rel-18/29_series/29520/8a94796989f4fcba2688c4faa7991538_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68c592e7532810d0f9da4f66854866af1018d291a7116e27e516441d3e4337f1 +size 24493 diff --git a/raw/rel-18/29_series/29520/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/raw/rel-18/29_series/29520/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a5ba7b819ab7b317bf0b9ddfa0dd91419444578 --- /dev/null +++ b/raw/rel-18/29_series/29520/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec116a967dcda96e23f8c9c76ca3f0c32c06e34b9c9a6c29183c76c1015ee1b8 +size 29676 diff --git a/raw/rel-18/29_series/29520/a3c1310e720178d2450a3748c7c75422_img.jpg b/raw/rel-18/29_series/29520/a3c1310e720178d2450a3748c7c75422_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..307cce88c71fef909de97d14f984e768e0f0713d --- /dev/null +++ b/raw/rel-18/29_series/29520/a3c1310e720178d2450a3748c7c75422_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36bbeca9c1f9afd4c71b8fb1db698d6fd41fa3360f0557d733ebe5e3a33fa6b9 +size 21632 diff --git a/raw/rel-18/29_series/29520/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg b/raw/rel-18/29_series/29520/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f90e1d08d5d065fd397d958a069241d01c11aad5 --- /dev/null +++ b/raw/rel-18/29_series/29520/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:190d473e4cd0b1a93846b778863ec48e02cd10c580423a66d29ffae6df7ca55b +size 8244 diff --git a/raw/rel-18/29_series/29520/aeb2a26a07219661191294dba528067a_img.jpg b/raw/rel-18/29_series/29520/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..598156ce6cecadffcbac5958b2051c30de7e8955 --- /dev/null +++ b/raw/rel-18/29_series/29520/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:638f1e04c6d7eb8ac8401485856738d43d861ae3ac1f43ea5056d78652dcae60 +size 32253 diff --git a/raw/rel-18/29_series/29520/b327d9f0565f7e032fc82b4322c844dc_img.jpg b/raw/rel-18/29_series/29520/b327d9f0565f7e032fc82b4322c844dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..521fda3e37c892da92773781097bdb032f490ba5 --- /dev/null +++ b/raw/rel-18/29_series/29520/b327d9f0565f7e032fc82b4322c844dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00107fb8caf5b099d04e541626fb8155c97fbdaeb17729d1c582470e499000d4 +size 13197 diff --git a/raw/rel-18/29_series/29520/b49477e8f148b5ef044a2fd5a43528f6_img.jpg b/raw/rel-18/29_series/29520/b49477e8f148b5ef044a2fd5a43528f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f741a6d3eaaa329d4ab957e7a256b5fc7ba26d4f --- /dev/null +++ b/raw/rel-18/29_series/29520/b49477e8f148b5ef044a2fd5a43528f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f334ace28b896fffe137ac0f2abb74fad549218e7b090e3c4175bdb682fcd2a8 +size 28543 diff --git a/raw/rel-18/29_series/29520/b816e7bb064d3bfa02761aa679eb3726_img.jpg b/raw/rel-18/29_series/29520/b816e7bb064d3bfa02761aa679eb3726_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f812968f9b0d8d6bf23455ace8beda8ca403a4ec --- /dev/null +++ b/raw/rel-18/29_series/29520/b816e7bb064d3bfa02761aa679eb3726_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9d79022cfc423efdf22cbc3ed1988438cee916e53c67bb36c617556b278aab2 +size 28776 diff --git a/raw/rel-18/29_series/29520/b97737027bd1b2effd7ca4dba8914877_img.jpg b/raw/rel-18/29_series/29520/b97737027bd1b2effd7ca4dba8914877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcf027d1217d4453fe6c0e9d4b797f783cd81782 --- /dev/null +++ b/raw/rel-18/29_series/29520/b97737027bd1b2effd7ca4dba8914877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:238f528a650005cb5aaf3c5e047b3c6785f9c302dbbb1e0184d40fa7f743fa76 +size 22542 diff --git a/raw/rel-18/29_series/29520/bbe5fb08522c43eab0afefcac30e719b_img.jpg b/raw/rel-18/29_series/29520/bbe5fb08522c43eab0afefcac30e719b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..776f5e0926813993edd780ce360e09af085ac1d9 --- /dev/null +++ b/raw/rel-18/29_series/29520/bbe5fb08522c43eab0afefcac30e719b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:739ca1f252d824f67822755216cb0609b9eed336b1be26ee4c94620ecb0e33a0 +size 9404 diff --git a/raw/rel-18/29_series/29520/bdb44cc8120caccddc2adf0c3db54261_img.jpg b/raw/rel-18/29_series/29520/bdb44cc8120caccddc2adf0c3db54261_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40ec7c2bf40e652945abac9ac467cea9fa1f5d04 --- /dev/null +++ b/raw/rel-18/29_series/29520/bdb44cc8120caccddc2adf0c3db54261_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d70d85b40cb25ba0b7321530c52cbe804704442006e0efe85ce7029c6f3c51aa +size 17007 diff --git a/raw/rel-18/29_series/29520/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg b/raw/rel-18/29_series/29520/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..265bf11ac53e04a90a81a9bf727e3f918e547db9 --- /dev/null +++ b/raw/rel-18/29_series/29520/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273f008db7f56cae2dc403916aba236d877be6866ed16b3bda2f39a2669f75d0 +size 28287 diff --git a/raw/rel-18/29_series/29520/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/raw/rel-18/29_series/29520/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..caa39949eef3ed74c303fd9be9f93169d3043a7e --- /dev/null +++ b/raw/rel-18/29_series/29520/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa391a06cc6be547314e4c9f89b698ef98f8a9141154a6ca7636dd5d4bff7455 +size 24143 diff --git a/raw/rel-18/29_series/29520/c54223b4f1a31104507af83ef6ee5392_img.jpg b/raw/rel-18/29_series/29520/c54223b4f1a31104507af83ef6ee5392_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d4df005af02fb8f9c28bbd285f559e826131ed9 --- /dev/null +++ b/raw/rel-18/29_series/29520/c54223b4f1a31104507af83ef6ee5392_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b04c14e968144241911ad4ba40366e774ba3da7a2598ec73a462e4db589895c +size 20966 diff --git a/raw/rel-18/29_series/29520/c8eb5f8c1faa149b1aaa0d5e4a5c0e66_img.jpg b/raw/rel-18/29_series/29520/c8eb5f8c1faa149b1aaa0d5e4a5c0e66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779969c1cc85403bd70c83b81eac446ccca4c4dd --- /dev/null +++ b/raw/rel-18/29_series/29520/c8eb5f8c1faa149b1aaa0d5e4a5c0e66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4868c7246d0b365f14facd9371e109d9adf10725245bac589bf02fe65903ae80 +size 17702 diff --git a/raw/rel-18/29_series/29520/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/raw/rel-18/29_series/29520/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6462a4ffc4fdd2aa2b3023e72368a483f94e286 --- /dev/null +++ b/raw/rel-18/29_series/29520/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e30524ded095a65791fa96472925edf5ecf732de831fedaef500458fb061c65 +size 27995 diff --git a/raw/rel-18/29_series/29520/cc468dcda006ef315536400517a09ad3_img.jpg b/raw/rel-18/29_series/29520/cc468dcda006ef315536400517a09ad3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c64a890a8ded7300e0761ce3712771b6079d9ff --- /dev/null +++ b/raw/rel-18/29_series/29520/cc468dcda006ef315536400517a09ad3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4c8d0ca1cce48c5e32c82a0060b92c4d4fa9e35c6f49dedc56dc755c486f0a9 +size 26756 diff --git a/raw/rel-18/29_series/29520/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg b/raw/rel-18/29_series/29520/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9847bfeb7785b1252781cab2d4882037b69f157 --- /dev/null +++ b/raw/rel-18/29_series/29520/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21bd28f7ff51b3f19639631f9d6247caff7fd8d436cccd3b6e48d4205bfd1cf4 +size 29783 diff --git a/raw/rel-18/29_series/29520/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/raw/rel-18/29_series/29520/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..962c43d2a21f66275805e6577297da855e0eb7c9 --- /dev/null +++ b/raw/rel-18/29_series/29520/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9efb0a11e815ed4db2bd69ca342c5b51d217085b282e73433593345f94c4b934 +size 26082 diff --git a/raw/rel-18/29_series/29520/e05b36c0d46549e681ce6581422c66b2_img.jpg b/raw/rel-18/29_series/29520/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7eeaa7141d234468fe49cd24aa2a781f73e73589 --- /dev/null +++ b/raw/rel-18/29_series/29520/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0659b2eab45f76ff089af980d79005a1fe3af61d8c93a4ff3180d4bea728cff +size 36266 diff --git a/raw/rel-18/29_series/29520/e18841eb4a995df8354a793459e12fd0_img.jpg b/raw/rel-18/29_series/29520/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c224e68e169fc983cb7d5adcbe6fb84cb7fa82a2 --- /dev/null +++ b/raw/rel-18/29_series/29520/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74c4d2fd6a0c70bdb09469ac389d34518202e4ee7e55394a0d96ad069bde1cf5 +size 26067 diff --git a/raw/rel-18/29_series/29520/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/raw/rel-18/29_series/29520/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce9ab0751b27b55576248e3f7c9f52ce19448c06 --- /dev/null +++ b/raw/rel-18/29_series/29520/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a38437f818dd6cfc042f49dbd782e1bd77bf9ace5fe9aa75ee57d22a6ec4ffec +size 23332 diff --git a/raw/rel-18/29_series/29520/e7010c66da16316c2935dfbbef5056b3_img.jpg b/raw/rel-18/29_series/29520/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..804452f0a6fd004e916155ecd13a283ee7e21c42 --- /dev/null +++ b/raw/rel-18/29_series/29520/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b54c2f7b342f67d54f7ee3ed78c9d7621c3bd33fa075b3165b9851f3fd22b1b +size 13124 diff --git a/raw/rel-18/29_series/29520/eabcc5363ff05be5b1ec4bf0aa360d2f_img.jpg b/raw/rel-18/29_series/29520/eabcc5363ff05be5b1ec4bf0aa360d2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7587d2850d52bc4bb3d83952b9b1b83c6658d28d --- /dev/null +++ b/raw/rel-18/29_series/29520/eabcc5363ff05be5b1ec4bf0aa360d2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41a8ad509da91445585fca157a2c4afea5ba6c28fd271216ed2e3b5ad8a02a61 +size 19567 diff --git a/raw/rel-18/29_series/29520/f40480872b021d2ac7c29202c199b695_img.jpg b/raw/rel-18/29_series/29520/f40480872b021d2ac7c29202c199b695_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72ac6b309655915811d5d76bb841331d32f6ecea --- /dev/null +++ b/raw/rel-18/29_series/29520/f40480872b021d2ac7c29202c199b695_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af27614837553c27cde01b892168cd3d1a06cc2b281e9243a45ff7bdab5bce6e +size 31647 diff --git a/raw/rel-18/29_series/29520/f59ced6eaab3181501fc23fdfb52297e_img.jpg b/raw/rel-18/29_series/29520/f59ced6eaab3181501fc23fdfb52297e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a13cd1f10a9e9f7eeaf6ee375748d789a202cc14 --- /dev/null +++ b/raw/rel-18/29_series/29520/f59ced6eaab3181501fc23fdfb52297e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:283d4d1774e5ff015f17df01485f283761ac20f2576b0c11a8a4faa7d1036245 +size 25208 diff --git a/raw/rel-18/29_series/29520/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/raw/rel-18/29_series/29520/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52b326cab7a94dce4d35e943d469f321a20ef689 --- /dev/null +++ b/raw/rel-18/29_series/29520/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:999be79b19d95a305b12f8b7192927ab83c54b408702ddd0b5ad034d581797f9 +size 26983 diff --git a/raw/rel-18/29_series/29520/f92e919c70b7adda2d0e778889f44fae_img.jpg b/raw/rel-18/29_series/29520/f92e919c70b7adda2d0e778889f44fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d0c1359f0dbb7fe852df2bdc67c461d6eafff70 --- /dev/null +++ b/raw/rel-18/29_series/29520/f92e919c70b7adda2d0e778889f44fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1892464c41a00c84bc8d8c204d726754ca7aa03adc6715ca4c7b414309616a6e +size 6325 diff --git a/raw/rel-18/29_series/29520/fcc757566216206ceddbd6c775e8db02_img.jpg b/raw/rel-18/29_series/29520/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff4b87608b29df79d90dc4ee99e1a456cc0abdc --- /dev/null +++ b/raw/rel-18/29_series/29520/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbb867a3f9a09f8d9b1a2628e6b42ddc1b1fd3d2ef3e244208178025ed0b017f +size 29030 diff --git a/raw/rel-18/29_series/29521/1320668e9151c5144f7e3696ae57e07f_img.jpg b/raw/rel-18/29_series/29521/1320668e9151c5144f7e3696ae57e07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0ab0162950b05d8c44257c637d68de09353eea1 --- /dev/null +++ b/raw/rel-18/29_series/29521/1320668e9151c5144f7e3696ae57e07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d85655fd2194efb230f464b1d50691536e1ca9ebadbdc7740a3eeeb50380ac2b +size 30670 diff --git a/raw/rel-18/29_series/29521/2876be3592c7b4878400b85f209b2b6a_img.jpg b/raw/rel-18/29_series/29521/2876be3592c7b4878400b85f209b2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c04a95c638df8a57eaa740efe302625620832f9c --- /dev/null +++ b/raw/rel-18/29_series/29521/2876be3592c7b4878400b85f209b2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e2294448398232d44f03a8c5cfa1a4a23e63f2d2153823a0ea5fba0760ee5e1 +size 25534 diff --git a/raw/rel-18/29_series/29521/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/raw/rel-18/29_series/29521/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2033ffe4bbe0aecfd358621c77ccda9ba48d329a --- /dev/null +++ b/raw/rel-18/29_series/29521/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:954077b46aa21f9242276be20d5b3db6bf44caaadef9a9fe3c3af514e5e5776a +size 25158 diff --git a/raw/rel-18/29_series/29521/410562339ce067fdc6fa41940c118658_img.jpg b/raw/rel-18/29_series/29521/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..988847c2b3d550b58e77bbaa67edf08b10af6f4c --- /dev/null +++ b/raw/rel-18/29_series/29521/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36434ad1d49468256cd94b96623f4db9ad0d353b00cadb7572f55bd46f4bba43 +size 21439 diff --git a/raw/rel-18/29_series/29521/523ab7b925beb555f88b2e1e1336974f_img.jpg b/raw/rel-18/29_series/29521/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1686e8563c053fa0f390950a2a0f9548520f1d2d --- /dev/null +++ b/raw/rel-18/29_series/29521/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f898a36bc39c4faee92277d28e7a5777952b46646737b966c9eeb3e95e35e95e +size 24939 diff --git a/raw/rel-18/29_series/29521/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29521/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c2108a4c632e5b5a60c2bca9f6ff599ddbb937 --- /dev/null +++ b/raw/rel-18/29_series/29521/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f775473eb10d3f47e5c7e6206bad3d842bea49e39759a4f9ea325b733838a66 +size 9694 diff --git a/raw/rel-18/29_series/29521/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29521/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e49dcab3f0ab6421f227cc028f6c0a91e5eae78 --- /dev/null +++ b/raw/rel-18/29_series/29521/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66daaecbf758911f14526dd8e8018f710d78880f694e8295de17c24afc0eb2fd +size 5333 diff --git a/raw/rel-18/29_series/29521/68d8089266ace7197304b43dcaf5d08e_img.jpg b/raw/rel-18/29_series/29521/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0a2db332b87f85e44fdb131989fe8e5dfcbb294 --- /dev/null +++ b/raw/rel-18/29_series/29521/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02dad7ae894e29027e6afdddde5bdb92d0af8d55b7d337f9c12fe7cddd8744ed +size 29665 diff --git a/raw/rel-18/29_series/29521/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/raw/rel-18/29_series/29521/70de8885bd7de15723aaad5eb5c5febf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e02c3e2e3d4f68d6221e091c877135def3ecc03 --- /dev/null +++ b/raw/rel-18/29_series/29521/70de8885bd7de15723aaad5eb5c5febf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ed62fa7f625cb9c67af6e714dd869087e1b766b8dd21ceca452c88f1948342d +size 26280 diff --git a/raw/rel-18/29_series/29521/844077b3034f0030b404207db0ad76b4_img.jpg b/raw/rel-18/29_series/29521/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0008cbe46f61a843169989be40b3d3f56e4df90 --- /dev/null +++ b/raw/rel-18/29_series/29521/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25ad2f205d618916adead03b8edff928a38fc63fddabcef20d59bc0f6742330d +size 23439 diff --git a/raw/rel-18/29_series/29521/9cd90f495b95ad2116ff780248c26d95_img.jpg b/raw/rel-18/29_series/29521/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc9f49ec64ec278a82b3fa6f8a1cfad2408c412b --- /dev/null +++ b/raw/rel-18/29_series/29521/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d3ea67f3fdd4dfdf54f8f37530f0e4637098abf0736eaaef580d3d1add0a1a +size 26844 diff --git a/raw/rel-18/29_series/29521/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/raw/rel-18/29_series/29521/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f4555644b83bce88d0f3f4174c72b6549e21bcb --- /dev/null +++ b/raw/rel-18/29_series/29521/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a25f01e0871d53c47054de9b2df0c175da037ce6a68c482943f0469fdfefaf71 +size 32450 diff --git a/raw/rel-18/29_series/29521/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/raw/rel-18/29_series/29521/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be53269b2d94bf7a3653ec91091afd1c5fdf8e93 --- /dev/null +++ b/raw/rel-18/29_series/29521/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5f015dc68ee29b047febffe93b10ef17a9f1273edecde3c1b2092b31fbc459e +size 23795 diff --git a/raw/rel-18/29_series/29521/d3b5eac55166fc428a223bba5c46961b_img.jpg b/raw/rel-18/29_series/29521/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2d0d426c2e5bcf4f7d2ecb1356d0207ccff650b --- /dev/null +++ b/raw/rel-18/29_series/29521/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45f42d8da841283d2c35258c79d0690a3b018a0dcfbb028a9d37eff5337b8d6d +size 28296 diff --git a/raw/rel-18/29_series/29521/d5918cee231b536f20789a18d861fae3_img.jpg b/raw/rel-18/29_series/29521/d5918cee231b536f20789a18d861fae3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d846912f680f87e3e29f3afb396e1fb13df83e0 --- /dev/null +++ b/raw/rel-18/29_series/29521/d5918cee231b536f20789a18d861fae3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4968c5e27e9fba53f201f84659dc66fcddc58a786eae9b299ab2458730861a2a +size 31176 diff --git a/raw/rel-18/29_series/29521/db7ae70402c81d140ae7df14b002e057_img.jpg b/raw/rel-18/29_series/29521/db7ae70402c81d140ae7df14b002e057_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06a5a6b4772c72ea4b0e498316d0e6a6bd75e416 --- /dev/null +++ b/raw/rel-18/29_series/29521/db7ae70402c81d140ae7df14b002e057_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36f08e9691d54756b21ac4b59f8e4af1e24ecfc81c951f553209738b28ff237e +size 33981 diff --git a/raw/rel-18/29_series/29521/dd380ccd5aca1151074fede04826f1a4_img.jpg b/raw/rel-18/29_series/29521/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6035470dff3daebd7972e5ed0a5b272b15427933 --- /dev/null +++ b/raw/rel-18/29_series/29521/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62bfa4c56e8f3f96b8cb1cc58222494b5983364b6a35a63e4b96eeaa17d2def5 +size 27966 diff --git a/raw/rel-18/29_series/29521/e05b36c0d46549e681ce6581422c66b2_img.jpg b/raw/rel-18/29_series/29521/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53db90ea4c392cf899bc86925859eb5de7202ead --- /dev/null +++ b/raw/rel-18/29_series/29521/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf9e951d44c6cb61f2a47c36818c1d79a726381b068629f6956bd7610a125736 +size 55473 diff --git a/raw/rel-18/29_series/29521/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/29_series/29521/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90b55a22747794aa1a91f3b30773e266b784e247 --- /dev/null +++ b/raw/rel-18/29_series/29521/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c901df0579fe14e25530ddca68f03192a8da4a7832497cd53fa93d39211ff030 +size 46393 diff --git a/raw/rel-18/29_series/29521/f1fbb1287d999c7034742de35bdab836_img.jpg b/raw/rel-18/29_series/29521/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4aef75a1be1be763af2da2886be1e5ade7a112 --- /dev/null +++ b/raw/rel-18/29_series/29521/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9123d35b05898772e80f8fa0a99c944abc7d2bad92c303f49c3b5cef1bb101dc +size 29908 diff --git a/raw/rel-18/29_series/29526/262a3a1913ff07a5129940d6903b53f1_img.jpg b/raw/rel-18/29_series/29526/262a3a1913ff07a5129940d6903b53f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4957baa7932ca6a40515346a913dd0fcf898455a --- /dev/null +++ b/raw/rel-18/29_series/29526/262a3a1913ff07a5129940d6903b53f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5891a8df5aef1146fdacfba5753061599f57b9bc3a044ab079aa28f3847a543c +size 12166 diff --git a/raw/rel-18/29_series/29526/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29526/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b6740ad3a354fb8d06bb8eb8273300c2e5933c2 --- /dev/null +++ b/raw/rel-18/29_series/29526/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8268c517be49b9be400b246863f6590836b9d026b292ea0cc2dd394dddf419a6 +size 7553 diff --git a/raw/rel-18/29_series/29526/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29526/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa7f5d54fb8718393ce37684c06a55c0ab3147da --- /dev/null +++ b/raw/rel-18/29_series/29526/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28a9ed511d56cef182d23a2746aeaa3713e96eb7d178052b1b7049b108196d0a +size 5635 diff --git a/raw/rel-18/29_series/29526/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/29_series/29526/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..163333fe61d9e101d89ccc0306f57cff4dd84611 --- /dev/null +++ b/raw/rel-18/29_series/29526/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49434ba2b05686c4985b8be874e7e5bbfa63e43006288e7470255f5a91900e9a +size 125132 diff --git a/raw/rel-18/29_series/29526/8e14350b4b669119a3bdfca7869110ca_img.jpg b/raw/rel-18/29_series/29526/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21374f878e3c8b4e4c0004eba52786649467c3a2 --- /dev/null +++ b/raw/rel-18/29_series/29526/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24a918a87b8774a884730300aa6979463e2890249eb1ae7ca05ce8597ac6336f +size 116637 diff --git a/raw/rel-18/29_series/29526/a04d24ddad7620a923d3895a834d71a8_img.jpg b/raw/rel-18/29_series/29526/a04d24ddad7620a923d3895a834d71a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbdcae3a87649d63445f24ffd15eb881844f48b9 --- /dev/null +++ b/raw/rel-18/29_series/29526/a04d24ddad7620a923d3895a834d71a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00d63c7c20baacdb2e45ab6145a14dc5a4bd18fba64c88fd0c8739ca18206b7 +size 17949 diff --git a/raw/rel-18/29_series/29526/a92b1fdf37a74b707e9f03087c8f1377_img.jpg b/raw/rel-18/29_series/29526/a92b1fdf37a74b707e9f03087c8f1377_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c28eb4d83e325fa365739b7a73bf89a88bcfd416 --- /dev/null +++ b/raw/rel-18/29_series/29526/a92b1fdf37a74b707e9f03087c8f1377_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da9c9fe61fdc5d70e3e40bbf55e5bc98a3c4f5f14df6e88c4b8f7b17d47ee72d +size 12930 diff --git a/raw/rel-18/29_series/29526/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/raw/rel-18/29_series/29526/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7030e3103915fcb10593762402be0aa49eedaa11 --- /dev/null +++ b/raw/rel-18/29_series/29526/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f78ac47928cde57a67dd45880b24f5a32dd5bd2213ed678092770866034a523 +size 35803 diff --git a/raw/rel-18/29_series/29526/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/raw/rel-18/29_series/29526/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..911a095fb77067a91065efaad89221322f89eb83 --- /dev/null +++ b/raw/rel-18/29_series/29526/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeb29fba39384b4fb56bc024f37ef49220fe67a6295c6d453ffcfc95f8b53678 +size 37382 diff --git a/raw/rel-18/29_series/29532/10781f43062bf3e9601a1e086710556c_img.jpg b/raw/rel-18/29_series/29532/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..994af7d5589bcd3c770cba0736a5dca8cf202c74 --- /dev/null +++ b/raw/rel-18/29_series/29532/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aa78f67c59277a54863773d2d3b4bac72b44967aaaaec39d2cf09f86e86d63a +size 33772 diff --git a/raw/rel-18/29_series/29532/144e1d61e8738b22dcf4a683f869ac6f_img.jpg b/raw/rel-18/29_series/29532/144e1d61e8738b22dcf4a683f869ac6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1322b897a1f5c7df3e286b44e80a0d5ad17ae37c --- /dev/null +++ b/raw/rel-18/29_series/29532/144e1d61e8738b22dcf4a683f869ac6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2304fcc9ffcea476834b0b1803c7c8083ae76499fda9f806e91abc3c2e385047 +size 35951 diff --git a/raw/rel-18/29_series/29532/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/29_series/29532/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18e2d5351889d2b7fde9307b9a0f14b17e55eef5 --- /dev/null +++ b/raw/rel-18/29_series/29532/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94381fac3318d2d031cc396ac1b73d45071ab61d7373bbcfb6cf362ef4e4580f +size 33595 diff --git a/raw/rel-18/29_series/29532/20136850feb70fd71c7d41cdae203ebb_img.jpg b/raw/rel-18/29_series/29532/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b623c5819f72927a251fe6c56134c84bc132b212 --- /dev/null +++ b/raw/rel-18/29_series/29532/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c666390c5768229b35b49837ff8d803f53a79a74f033f4c222b03b3a5cbc6df5 +size 37952 diff --git a/raw/rel-18/29_series/29532/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/raw/rel-18/29_series/29532/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6d9dc2e2c809f6236503d4ec4dbcfaa7cccfc0b --- /dev/null +++ b/raw/rel-18/29_series/29532/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f612665ab5eb677d00c998d609322a21aa1d50332331a1c748c55aff8eedd34d +size 34660 diff --git a/raw/rel-18/29_series/29532/356eb99ab9489bbd647223390a913903_img.jpg b/raw/rel-18/29_series/29532/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8176b264a8fbecd39f713fbe45948045e1ef2e2 --- /dev/null +++ b/raw/rel-18/29_series/29532/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36fa09b405560fc248449455582bcdc9dc26d7b3050e9614e41ef35bfbfa61a7 +size 36068 diff --git a/raw/rel-18/29_series/29532/4356776ca004ecba5d599667a155d7d4_img.jpg b/raw/rel-18/29_series/29532/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef6cfe8af4c0f00672a270cb2ebc1f3dccdc0002 --- /dev/null +++ b/raw/rel-18/29_series/29532/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20487c51bf7d1eaeb4ce4f64577e5ce8339a9cb501bc18aa53ec4f69bf9d7094 +size 40123 diff --git a/raw/rel-18/29_series/29532/4412857e90dfaa9a3df8836bcbde534b_img.jpg b/raw/rel-18/29_series/29532/4412857e90dfaa9a3df8836bcbde534b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..366fcba3db4d78165ae8e85add8689d2cae08bf3 --- /dev/null +++ b/raw/rel-18/29_series/29532/4412857e90dfaa9a3df8836bcbde534b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:774bf37ef12cb93a5f6d3d42a443dc14cc2f4a70bcfd764d5bd2ea2972bd0169 +size 40719 diff --git a/raw/rel-18/29_series/29532/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/raw/rel-18/29_series/29532/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5094c24c0b9679486cb27e2dba1f5b8b9bde845 --- /dev/null +++ b/raw/rel-18/29_series/29532/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:561910ba651969f97d432380333a3d98bf9285b653b2130dfb808a6eba7eed2d +size 38635 diff --git a/raw/rel-18/29_series/29532/5dfc130b129ace4df375839020a5700d_img.jpg b/raw/rel-18/29_series/29532/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..deb37a8540dd7821ec8b43f27a1f1587250f23cc --- /dev/null +++ b/raw/rel-18/29_series/29532/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60b32a6615a536a7fbabe934d180a3d1cb69e8a98df55d3ec4d0442fbdc577c2 +size 31143 diff --git a/raw/rel-18/29_series/29532/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29532/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b114565d1f52c4ac8d7fe293590c6c9ec30074c1 --- /dev/null +++ b/raw/rel-18/29_series/29532/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad50bb21807f12c1f5cc0bb2f5d82a774853fbde8b71fc4a59635a07cbcf430e +size 10421 diff --git a/raw/rel-18/29_series/29532/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29532/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..474088002f241fff2759ad877d40cef5e0d85323 --- /dev/null +++ b/raw/rel-18/29_series/29532/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/29_series/29532/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/raw/rel-18/29_series/29532/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecc7e958bbceef431cdefb90807d83e8b3d7febd --- /dev/null +++ b/raw/rel-18/29_series/29532/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a42d55281f2844f2a3d62a29bae187102ee04c3c06193369637a771a7aba544 +size 34848 diff --git a/raw/rel-18/29_series/29532/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/raw/rel-18/29_series/29532/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca30c282edb5503f47f256e52335bc1f080e138a --- /dev/null +++ b/raw/rel-18/29_series/29532/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e4c1195979584ae992ee2a3e312d655eef5cce38737a49db040cffbd914059f +size 41400 diff --git a/raw/rel-18/29_series/29532/836008eb3303ade9e269f93c04dc0a2e_img.jpg b/raw/rel-18/29_series/29532/836008eb3303ade9e269f93c04dc0a2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..973637e04947117836ffaaa6ded591317df672ea --- /dev/null +++ b/raw/rel-18/29_series/29532/836008eb3303ade9e269f93c04dc0a2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af19a4bba328fd6f8849d39d62b72172338ca4d0132ae298e4c6af1acdde619e +size 32297 diff --git a/raw/rel-18/29_series/29532/8e14350b4b669119a3bdfca7869110ca_img.jpg b/raw/rel-18/29_series/29532/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5b8b8087055fa6195124f3d1156dc888258f85c --- /dev/null +++ b/raw/rel-18/29_series/29532/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a9de6e3bf227ffb89364a7f86a82b8b0dc848d285571c367b930ff57199bd2f +size 28612 diff --git a/raw/rel-18/29_series/29532/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/29_series/29532/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c26bbd441c6cabce5983622b6aabb4ba5d0af68c --- /dev/null +++ b/raw/rel-18/29_series/29532/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:880d165fb078f2f45f58965323d9e088ff72134c5c5cd35f85c6a815a27dd39d +size 34416 diff --git a/raw/rel-18/29_series/29532/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/raw/rel-18/29_series/29532/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8be88a13a2023e1161d3b4b258071116a82c7aab --- /dev/null +++ b/raw/rel-18/29_series/29532/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3249242566a02ffe1c9c2aef05fb22d1a8498e998a750b8e138ff8c90ddbaf6 +size 30665 diff --git a/raw/rel-18/29_series/29532/e50de31fbc76748a552755ee72dfbf2f_img.jpg b/raw/rel-18/29_series/29532/e50de31fbc76748a552755ee72dfbf2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f60b8f867039f9075f68ed62f400012776b71f3a --- /dev/null +++ b/raw/rel-18/29_series/29532/e50de31fbc76748a552755ee72dfbf2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7579e9500d97f79c944312812a779f64ee6704b867ece330d1b14a1f55d62129 +size 7679 diff --git a/raw/rel-18/29_series/29534/12de9b926df0384ec07702671827c9cd_img.jpg b/raw/rel-18/29_series/29534/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c081f355206f4b16ccdf05fbfd526f96cf90b6df --- /dev/null +++ b/raw/rel-18/29_series/29534/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0a38deda72ac6f62d36172c095159bb5f455500b3591deaeea98434d44a96d5 +size 34314 diff --git a/raw/rel-18/29_series/29534/220869911a1ecfa1dd4aa6d750319aad_img.jpg b/raw/rel-18/29_series/29534/220869911a1ecfa1dd4aa6d750319aad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24467ac85444b5cb3e0795ce90404dfd605f32eb --- /dev/null +++ b/raw/rel-18/29_series/29534/220869911a1ecfa1dd4aa6d750319aad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a27b5f84c1d482366034cfc33d637fecbf277f606b65ef9016b5b6aa00377ac1 +size 30740 diff --git a/raw/rel-18/29_series/29534/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/29_series/29534/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b943e8844f1dc78cfad5e34ac4684b7112bc9af --- /dev/null +++ b/raw/rel-18/29_series/29534/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a0b5d578a7f195b805e55693c348c1cce6404df09e85102a5a2a046a2238ae9 +size 28369 diff --git a/raw/rel-18/29_series/29534/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/raw/rel-18/29_series/29534/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..026a4e706b1a509a71c25d94e428bbc845b30472 --- /dev/null +++ b/raw/rel-18/29_series/29534/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9f29fba021f32592ad9d57c0404307ad677a2dda05a7ed43bd87b03523a5756 +size 33534 diff --git a/raw/rel-18/29_series/29534/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/raw/rel-18/29_series/29534/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7845b0197fe1a10f856fb44d41362e4fb0ee8b83 --- /dev/null +++ b/raw/rel-18/29_series/29534/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b37cab1d1fba6a670fb679f56238e0136df79863171df1648cdad10396ec92c +size 37265 diff --git a/raw/rel-18/29_series/29534/5a4e62bead259c258d069fd3663ea670_img.jpg b/raw/rel-18/29_series/29534/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60915d88b59cd9b17928b77ebdb03d92bf597fe4 --- /dev/null +++ b/raw/rel-18/29_series/29534/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14e98eb55305e11067020c763c5dbe1a7d8782850e8fc68429e341425d2ad2b3 +size 22753 diff --git a/raw/rel-18/29_series/29534/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29534/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc6946e5d81914a299107091bc4da619962a7237 --- /dev/null +++ b/raw/rel-18/29_series/29534/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5537e933497e18ae87c050b0a77905bcb6dbcbba438f7ac0ea59e781dc14ab7d +size 9897 diff --git a/raw/rel-18/29_series/29534/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29534/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8925f48571de8283f948356bc48e9440a9c6ceb --- /dev/null +++ b/raw/rel-18/29_series/29534/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf812684ab7790d56954732483edbcbb4775081bb48c5fabcf2d6c7881f555b7 +size 5687 diff --git a/raw/rel-18/29_series/29534/75e4b78ee25f885d73120e3066a5253e_img.jpg b/raw/rel-18/29_series/29534/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d687dd70e5922308ed6580f6fbfd9415e7408644 --- /dev/null +++ b/raw/rel-18/29_series/29534/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fa3405ab7eb2ae21c1015b7c1de26f07bec46c46a564c5ada98ab80e41e4074 +size 30278 diff --git a/raw/rel-18/29_series/29534/90ddb84c323b956e2d50a54d3f870566_img.jpg b/raw/rel-18/29_series/29534/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26379081eb2942858eed6229ab884703ec9363cb --- /dev/null +++ b/raw/rel-18/29_series/29534/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a68f1944bc8e423dbc8b67b5ea0bcc03c04d6bd069ea216122e240cfb04ba9c9 +size 29934 diff --git a/raw/rel-18/29_series/29534/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/raw/rel-18/29_series/29534/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b31f9ccc20d5e7b0534be3cf5781f18b7c45e687 --- /dev/null +++ b/raw/rel-18/29_series/29534/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:592d0c40230115e37165f9c78f5a4767f8bb885aeb31e43680bff586b0451d41 +size 33610 diff --git a/raw/rel-18/29_series/29534/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/raw/rel-18/29_series/29534/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c043aca1326ed333c78afdb44d3e6001ee22a92e --- /dev/null +++ b/raw/rel-18/29_series/29534/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c28b5193295bbaabb0c3bc093597361cf69724c9eca555d327d60da02a9e916 +size 35466 diff --git a/raw/rel-18/29_series/29534/ddc7460821484f1ae2835c67955c554c_img.jpg b/raw/rel-18/29_series/29534/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..944dfd81faec881bd4d56b7b9a58a558cac5c98a --- /dev/null +++ b/raw/rel-18/29_series/29534/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e39391b19f40e0cacb945d99933caa20b1d0e5658cd767aed08433c54782242e +size 28719 diff --git a/raw/rel-18/29_series/29534/ee8536b235eb6aad21e2048fd5308900_img.jpg b/raw/rel-18/29_series/29534/ee8536b235eb6aad21e2048fd5308900_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..663aaf9ed3c76e41c5381c224a2e646dbe5e4145 --- /dev/null +++ b/raw/rel-18/29_series/29534/ee8536b235eb6aad21e2048fd5308900_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:085598065cf58d99c92c7e8e178f7e707f3ae4e9d6f96298714f597a3ad752c1 +size 20689 diff --git a/raw/rel-18/29_series/29534/raw.md b/raw/rel-18/29_series/29534/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..965db1dc566d1b398926dce9cb9919612f292732 --- /dev/null +++ b/raw/rel-18/29_series/29534/raw.md @@ -0,0 +1,2736 @@ + + +# 3GPP TS 29.534 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Access and Mobility Policy Authorization Service; Stage 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 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 + +--- + +<http://www.3gpp.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. + +© 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..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Npcf_AMPolicyAuthorization Service..... | 10 | +| 4.1 Service Description ..... | 10 | +| 4.1.1 Overview ..... | 10 | +| 4.1.2 Service Architecture ..... | 10 | +| 4.1.3 Network Functions ..... | 11 | +| 4.1.3.1 Policy Control Function (PCF)..... | 11 | +| 4.1.3.2 NF Service Consumers ..... | 11 | +| 4.2 Service Operations ..... | 12 | +| 4.2.1 Introduction ..... | 12 | +| 4.2.2 Npcf_AMPolicyAuthorization_Create service operation ..... | 12 | +| 4.2.2.1 General..... | 12 | +| 4.2.2.2 Initial provisioning of access and mobility related service information..... | 13 | +| 4.2.2.3 Creation of the subscription to service area coverage change outcome ..... | 14 | +| 4.2.3 Npcf_AMPolicyAuthorization_Update service operation ..... | 15 | +| 4.2.3.1 General..... | 15 | +| 4.2.3.2 Modification of AM related service information..... | 15 | +| 4.2.3.3 Modification of the subscription to service area coverage change outcome ..... | 17 | +| 4.2.4 Npcf_AMPolicyAuthorization_Delete service operation ..... | 17 | +| 4.2.4.1 General..... | 17 | +| 4.2.4.2 AF application AM context termination ..... | 17 | +| 4.2.5 Npcf_AMPolicyAuthorization_Subscribe service operation ..... | 18 | +| 4.2.5.1 General..... | 18 | +| 4.2.5.2 Handling of subscription to events for the existing AF application AM context..... | 19 | +| 4.2.5.3 Subscription to events without an existing AF application AM context ..... | 21 | +| 4.2.5.4 Subscription to PDUID changes ..... | 22 | +| 4.2.6 Npcf_AMPolicyAuthorization_Unsubscribe service operation..... | 23 | +| 4.2.6.1 General..... | 23 | +| 4.2.6.2 Unsubscription to events, Access and Mobility related service information exists ..... | 23 | +| 4.2.6.3 Unsubscription to events, Access and Mobility related service information does not exist ..... | 24 | +| 4.2.7 Npcf_AMPolicyAuthorization_Notify service operation ..... | 24 | +| 4.2.7.1 General..... | 24 | +| 4.2.7.2 Notification about AF application AM context event ..... | 24 | +| 4.2.7.3 Notification about AF application AM context termination..... | 25 | +| 4.2.7.4 Notification about service area coverage change outcome..... | 26 | +| 4.2.7.5 Notification about PDUID changes ..... | 27 | +| 5 Npcf_AMPolicyAuthorization Service API ..... | 27 | +| 5.1 Introduction ..... | 27 | +| 5.2 Usage of HTTP..... | 28 | +| 5.2.1 General ..... | 28 | +| 5.2.2 HTTP standard headers ..... | 28 | +| 5.2.2.1 General..... | 28 | +| 5.2.2.2 Content type..... | 28 | +| 5.2.3 HTTP custom headers ..... | 28 | +| 5.2.3.1 General..... | 28 | +| 5.3 Resources ..... | 28 | +| 5.3.1 Overview ..... | 28 | +| 5.3.2 Resource: Application AM contexts (Collection) ..... | 29 | + +| | | | +|-----------|----------------------------------------------------------------------------------|----| +| 5.3.2.1 | Description..... | 29 | +| 5.3.2.2 | Resource Definition ..... | 30 | +| 5.3.2.3 | Resource Standard Methods ..... | 30 | +| 5.3.2.3.1 | POST ..... | 30 | +| 5.3.2.4 | Resource Custom Operations..... | 30 | +| 5.3.3 | Resource: Individual application AM context (Document) ..... | 31 | +| 5.3.3.1 | Description..... | 31 | +| 5.3.3.2 | Resource Definition ..... | 31 | +| 5.3.3.3 | Resource Standard Methods ..... | 31 | +| 5.3.3.3.1 | GET ..... | 31 | +| 5.3.3.3.2 | PATCH..... | 32 | +| 5.3.3.3.3 | DELETE..... | 33 | +| 5.3.3.4 | Resource Custom Operations..... | 34 | +| 5.3.4 | Resource: AM Policy Events Subscription (Document) ..... | 35 | +| 5.3.4.1 | Description..... | 35 | +| 5.3.4.2 | Resource definition..... | 35 | +| 5.3.4.3 | Resource Standard Methods ..... | 35 | +| 5.3.4.3.1 | PUT ..... | 35 | +| 5.3.4.3.2 | DELETE..... | 37 | +| 5.3.4.4 | Resource Custom Operations..... | 38 | +| 5.4 | Custom Operations without associated resources ..... | 38 | +| 5.5 | Notifications ..... | 38 | +| 5.5.1 | General ..... | 38 | +| 5.5.2 | AM Event Notification ..... | 38 | +| 5.5.2.1 | Description..... | 38 | +| 5.5.2.2 | Target URI..... | 39 | +| 5.5.2.3 | Standard Methods ..... | 39 | +| 5.5.2.3.1 | POST ..... | 39 | +| 5.5.3 | Termination Request ..... | 40 | +| 5.5.3.1 | Description..... | 40 | +| 5.5.3.2 | Target URI..... | 40 | +| 5.5.3.3 | Standard Methods ..... | 40 | +| 5.5.3.3.1 | POST ..... | 40 | +| 5.6 | Data Model..... | 41 | +| 5.6.1 | General ..... | 41 | +| 5.6.2 | Structured data types ..... | 43 | +| 5.6.2.1 | Introduction..... | 43 | +| 5.6.2.2 | Type: AppAmContextData ..... | 44 | +| 5.6.2.3 | Type: AppAmContextUpdateData ..... | 45 | +| 5.6.2.4 | Type: AmEventsSubscData ..... | 45 | +| 5.6.2.5 | Type: AmEventsNotification..... | 45 | +| 5.6.2.6 | Type: AmTerminationInfo..... | 46 | +| 5.6.2.7 | Type AmEventsSubscDataRm ..... | 46 | +| 5.6.2.8 | Type AmEventData ..... | 47 | +| 5.6.2.9 | Type: AmEventNotification ..... | 47 | +| 5.6.2.10 | Type: PduidInformation..... | 48 | +| 5.6.2.11 | Type: ServiceAreaCoverageInfo ..... | 48 | +| 5.6.3 | Simple data types and enumerations ..... | 48 | +| 5.6.3.1 | Introduction..... | 48 | +| 5.6.3.2 | Simple data types..... | 48 | +| 5.6.3.3 | Enumeration: AmEvent ..... | 48 | +| 5.6.3.4 | Enumeration: AmTerminationCause ..... | 49 | +| 5.6.4 | Data types describing alternative data types or combinations of data types ..... | 49 | +| 5.6.4.1 | Type: AppAmContextRespData ..... | 49 | +| 5.6.4.2 | Type: AmEventsSubscRespData ..... | 49 | +| 5.6.5 | Binary data..... | 49 | +| 5.6.5.1 | Binary Data Types ..... | 49 | +| 5.7 | Error Handling..... | 50 | +| 5.7.1 | General ..... | 50 | +| 5.7.2 | Protocol Errors..... | 50 | +| 5.7.3 | Application Errors ..... | 50 | +| 5.8 | Feature negotiation..... | 50 | + +5.9 Security..... 50 + +**Annex A (normative): OpenAPI specification..... 52** + +A.1 General..... 52 + +A.2 Npcf\_AMPolicyAuthorization API ..... 52 + +**Annex B (informative): Change history ..... 63** + +# 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 3 protocol and data model for the Access and Mobility Policy Authorization service (Npcf\_AMPolicyAuthorization) of the 5G System. + +The 5G System stage 2 architecture of the Access and Mobility Policy Authorization service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. The 5G System Architecture is defined in 3GPP TS 23.501 [2]. + +Stage 3 call flows for policy and charging control use cases are provided in 3GPP TS 29.513 [15]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. + +The Access and Mobility Policy Authorization service is provided by the Policy Control Function (PCF). This service creates access and mobility policies (e.g. service area restrictions, or access stratum time distribution information) as requested by an authorized NF service consumer (e.g. AF, NEF, or TSCTSF) for the Access and Mobility Policy Context to which the related NF service consumer's context (e.g. AF, NEF, or TSCTSF) is bound. This service also enables subscription/notifications on UE 5G ProSe Policy event(s) related to the UE context to which the NF service consumer's context (e.g. 5G DDNMF) is bound. + +# --- 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 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", <https://spec.openapis.org/oas/v3.0.0>. +- [7] 3GPP TR 21.900: "Technical Specification Group working methods". +- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [11] IETF RFC 9113: "HTTP/2". +- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [13] IETF RFC 9457: "Problem Details for HTTP APIs". +- [14] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". + +- [15] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3". +- [16] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3". +- [17] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3". +- [18] IETF RFC 7396: "JSON Merge Patch". +- [19] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". +- [20] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [21] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3". +- [22] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [23] 3GPP TS 24.555: "Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3". +- [24] 3GPP TS 29.555: "5G System; 5G Direct Discovery Name Management Services; Stage 3". +- [25] 3GPP TS 29.565: "5G System; Time Sensitive Communication and Time Synchronization Function Services; Stage 3". + +# --- 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]. + +**Application Function (AF):** Element acting on behalf of applications(s) that require the control of the Access and Mobility context of a UE, which can in turn lead to e.g. Service Area Restrictions and/or RFSP changes. + +**AF application AM context:** Information about the capabilities that an AF application requires from the access network for a registered UE. It is established by the AF before or during the use of the service that requires it. + +**NF service consumer AM context:** Information about the capabilities that a NF service consumer requires from the access network for a registered UE. + +## 3.2 Symbols + +None. + +## 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]. + +| | | +|----------|----------------------------------------------| +| 5G DDNMF | 5G Direct Discovery Name Management Function | +| AF | Application Function | +| AMF | Access and Mobility Management Function | +| JSON | JavaScript Object Notation | +| NEF | Network Exposure Function | +| NF | Network Function | + +| | | +|--------|----------------------------------------------------------------| +| PCF | Policy Control Function | +| PDUID | ProSe Discovery UE ID | +| ProSe | Proximity Services | +| RFSP | RAT Frequency Selection Priority | +| SMF | Session Management Function | +| TSCTSF | Time Sensitive Communication and Time Synchronization Function | + +# 4 Npcf\_AMPolicyAuthorization Service + +## 4.1 Service Description + +### 4.1.1 Overview + +The Npcf\_AMPolicyAuthorization service, as defined in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14], is provided by the Policy Control Function (PCF) and enables an authorized NF service consumer to influence access and mobility policies for a UE and to subscribe to notifications on UE 5G ProSe Policy event(s). + +The Npcf\_AMPolicyAuthorization service enables to authorize a NF service consumer's request and create/update the associated access and mobility policies as requested by the authorized NF service consumer for the Access and Mobility policy association to which the NF service consumer AM context (e.g. the AF application AM context) is bound. + +This service also allows the NF service consumer to subscribe/unsubscribe to notifications on AM Policy event(s) (e.g. service area restrictions policy change) and to subscribe/unsubscribe to notifications on UE 5G ProSe Policy event(s) (e.g. PDUID change event). + +### 4.1.2 Service Architecture + +The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The Policy and Charging control related 5G architecture is also defined in 3GPP TS 23.503 [14] and 3GPP TS 29.513 [15]. + +The known NF service consumers of the Npcf\_AMPolicyAuthorization service are the Application Function (AF), the Network Exposure Function (NEF), the 5G Direct Discovery Name Management Function (5G DDNMF) and the Time Sensitive Communication and Time Synchronization Function (TSCTSF). + +The Npcf\_AMPolicyAuthorization service is provided by the PCF and consumed by the NF service consumers (e.g. AF, NEF), as shown in figure 4.1.2-1 for the SBI representation model and in figure 4.1.2-2 for the reference point representation model. + +![Diagram of Npcf_AMPolicyAuthorization service architecture, SBI representation. The PCF (Policy Control Function) is shown at the top, with the Npcf service interface. Below it, the Npcf_AMPolicyAuthorization service is represented by a vertical line. This service is consumed by four NF service consumers: NEF (Network Exposure Function), AF (Application Function), 5G DDNMF (5G Direct Discovery Name Management Function), and TSCTSF (Time Sensitive Communication and Time Synchronization Function), which are shown in a horizontal row at the bottom.](ee8536b235eb6aad21e2048fd5308900_img.jpg) + +``` +graph TD; PCF[PCF] -- Npcf --> Npcf_AMPolicyAuthorization[Npcf_AMPolicyAuthorization]; Npcf_AMPolicyAuthorization --> NEF[NEF]; Npcf_AMPolicyAuthorization --> AF[AF]; Npcf_AMPolicyAuthorization --> 5G_DDNMF[5G DDNMF]; Npcf_AMPolicyAuthorization --> TSCTSF[TSCTSF]; +``` + +Diagram of Npcf\_AMPolicyAuthorization service architecture, SBI representation. The PCF (Policy Control Function) is shown at the top, with the Npcf service interface. Below it, the Npcf\_AMPolicyAuthorization service is represented by a vertical line. This service is consumed by four NF service consumers: NEF (Network Exposure Function), AF (Application Function), 5G DDNMF (5G Direct Discovery Name Management Function), and TSCTSF (Time Sensitive Communication and Time Synchronization Function), which are shown in a horizontal row at the bottom. + +Figure 4.1.2-1: Npcf\_AMPolicyAuthorization service architecture, SBI representation + +![Diagram of Npcf_AMPolicyAuthorization service architecture, reference point representation. A central PCF box is connected to four boxes on the right: NEF, AF, 5G DDNMF, and TSCTSF. The connections are labeled with reference points: N30 (to NEF), N5 (to AF), Npd (to 5G DDNMF), and N84 (to TSCTSF).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` +graph LR; PCF[PCF] ---|N30| NEF[NEF]; PCF ---|N5| AF[AF]; PCF ---|Npd| 5GDDNMF[5G DDNMF]; PCF ---|N84| TSCTSF[TSCTSF]; +``` + +Diagram of Npcf\_AMPolicyAuthorization service architecture, reference point representation. A central PCF box is connected to four boxes on the right: NEF, AF, 5G DDNMF, and TSCTSF. The connections are labeled with reference points: N30 (to NEF), N5 (to AF), Npd (to 5G DDNMF), and N84 (to TSCTSF). + +**Figure 4.1.2-2: Npcf\_AMPolicyAuthorization service architecture, reference point representation** + +In the case of an Untrusted AF, i.e. when the AF interacts with the PCF via the NEF, the NEF may interact with the PCF via the N30 reference point in the same way that the AF interacts with the PCF via the N5 reference point. + +### 4.1.3 Network Functions + +#### 4.1.3.1 Policy Control Function (PCF) + +The PCF (Policy Control Function) is a functional element that encompasses, among other functionalities, access and mobility policy decisions for the control of e.g. the UE Service Area Restrictions and RAT/RFSP control, and the delivery of UE Policies (e.g. UE 5G ProSe Policies) to the UE. + +The PCF receives from a NF service consumer (e.g. AF, NEF) access and mobility service requirements related to a registered UE and notifies it about the outcome of the requested access and mobility policy changes, if applicable, if the NF service consumer previously subscribed, via the Npcf\_AMPolicyAuthorization service. + +The PCF derives access and mobility policies and provisions them to the AMF via the Npcf\_AMPolicyControl as described in 3GPP TS 29.507 [16]. + +When the PCF that handles the AM Policy Associations (PCF for the UE) is different from the PCF that handles the SM Policy Associations (PCF for the PDU session) for a UE, the PCF subscribes to application traffic detection event(s) using the Npcf\_PolicyAuthorization service as described in 3GPP TS 29.514 [17]. + +The PCF receives from a NF service consumer (e.g. 5G DDNMF) subscriptions to notifications on events related to the delivered UE 5G ProSe Policies for a SUPI. + +#### 4.1.3.2 NF Service Consumers + +The known NF service consumers are the AF, the NEF, the 5G DDNMF, and the TSCTSF as defined in 3GPP TS 23.502 [3]. + +The Application Function (AF) is a network function offering, among other functionalities, control to applications for the dynamic change of access and mobility policies for a registered UE. The AF uses the Npcf\_AMPolicyAuthorization service to provide to the PCF service information related to the required access and mobility context (e.g. access and mobility required policies) for the concerned service(s). + +The AFs can be deployed by the same operator offering the access services or be provided by an external third-party service provider. If the AF is not allowed by the operator to directly access the PCF, the AF uses the 3GPP external network exposure framework via the NEF to interact with the PCF, as described in clause 5.20 of 3GPP TS 23.501 [2]. + +The Network Exposure Function (NEF) supports external exposure of the capabilities of 5GC network functions. + +The 5G DDNMF is a network function that handles the network related actions required for dynamic 5G ProSe Direct Discovery, as defined in 3GPP TS 23.304 [22]. + +The AF trusted by the operator, or the NEF can use the TSCTSF to interface with the PCF to support the delivery of access stratum time distribution information to the AMF as defined in 3GPP TS 29.565 [25]. + +## 4.2 Service Operations + +### 4.2.1 Introduction + +Service operations defined for the Npcf\_AMPolicyAuthorization service are shown in table 4.2.1-1. + +**Table 4.2.1-1: Npcf\_AMPolicyAuthorization Service Operations** + +| Service Operation Name | Description | Initiated by | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| Npcf_AMPolicyAuthorization_Create | Creates an AF application AM context in the PCF as per request from an authorized NF service consumer, and determines and installs the access and mobility policy according to the service information provided by the NF service consumer. It also allows the subscription to event notifications. | NF service consumer (e.g. AF, NEF, TSCTSF) | +| Npcf_AMPolicyAuthorization_Update | Updates the AF application AM context in the PCF as per request from an authorized NF service consumer, and determines and updates the access and mobility policy according to the modified service information provided by the NF service consumer. It also allows the update of the associated subscription to event notifications. | NF service consumer (e.g. AF, NEF, TSCTSF) | +| Npcf_AMPolicyAuthorization_Delete | Provides means to the concerned NF service consumer to delete the AF application AM context in the PCF. | NF service consumer (e.g. AF, NEF, TSCTSF) | +| Npcf_AMPolicyAuthorization_Subscribe | Allows NF service consumers to subscribe to event notifications. | NF service consumer (e.g. AF, NEF, 5G DDNMF) | +| Npcf_AMPolicyAuthorization_Unsubscribe | Allows NF service consumers to unsubscribe from event notifications. | NF service consumer (e.g. AF, NEF, 5G DDNMF) | +| Npcf_AMPolicyAuthorization_Notify | Notifies NF service consumers of the subscribed events. | PCF | + +NOTE 1: The NEF and the AF use the Npcf\_AMPolicyAuthorization service in the same way. + +NOTE 2: The 5G DDNMF only uses the Npcf\_AMPolicyAuthorization subscribe, unsubscribe and notify service operations. + +NOTE 3: The TSCTSF only uses the Npcf\_AMPolicyAuthorization create, update and delete service operations. + +### 4.2.2 Npcf\_AMPolicyAuthorization\_Create service operation + +#### 4.2.2.1 General + +The Npcf\_AMPolicyAuthorization\_Create service operation authorizes the request from the NF service consumer, and optionally communicates with Npcf\_AMPolicyControl service to determine and install in the AMF the access and mobility policies according to the information provided by the NF service consumer. + +The Npcf\_AMPolicyAuthorization\_Create service operation creates a NF service consumer related AM context in the PCF. + +The following procedures using the Npcf\_AMPolicyAuthorization\_Create service operation are supported: + +- Initial provisioning of access and mobility related service information. +- Creation of the subscription to service area coverage change outcome. + +#### 4.2.2.2 Initial provisioning of access and mobility related service information + +This procedure is used to set up an NF service consumer AM context (e.g. an AF application AM context) for the service as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. + +Figure 4.2.2.2-1 illustrates the initial provisioning of service information for the AM context. + +![Sequence diagram showing the initial provisioning of service information for the AM context between an NF service consumer and a PCF.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` + +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. POST .../app-am-contexts + NF service consumer->>PCF: Request + Note left of PCF: 2. "201 Created" + PCF-->>NF service consumer: Response + +``` + +The diagram illustrates a sequence of two messages between an NF service consumer and a PCF. The first message, labeled '1. POST .../app-am-contexts', is sent from the NF service consumer to the PCF. The second message, labeled '2. "201 Created"', is sent from the PCF back to the NF service consumer. + +Sequence diagram showing the initial provisioning of service information for the AM context between an NF service consumer and a PCF. + +**Figure 4.2.2.2-1: Initial provisioning of service information for the AM context** + +When a NF service consumer requires an AM context is being established in the 5GS and the related access and mobility requirements are available at the NF service consumer, the NF service consumer shall invoke the Npcf\_AMPolicyAuthorization\_Create service operation by sending the HTTP POST request to the resource URI representing the "Application AM contexts" collection resource of the PCF, as shown in figure 4.2.2.2-1, step 1. + +The NF service consumer shall include in the "AppAmContextData" data type in the content of the HTTP POST request a partial representation of the "Individual Application AM Context" resource, that shall include: + +- the notification URI where the PCF requests to the NF service consumer the termination of the application AM context encoded as "termNotifUri" attribute; +- the SUPI of the UE to which the AF requested policy shall apply encoded as "supi" attribute; +- when the NF service consumer is the NEF or the AF: + - a. the indication that high throughput policy is desired for the indicated UE encoded as "highThruInd" attribute; and/or + - b. the service area coverage desired for the indicated UE encoded as "covReq" attribute, that contains a list of Tracking Area codes per serving network where the requested service shall be allowed; +- when the NF service consumer is the TSCTSF: + - a. the access stratum time distribution parameters (5G access stratum time distribution indication (enable, disable), and/or Uu time synchronization error budget,, and optionally the clock quality detail level as "clkQltDetLvl" attribute and the clock quality acceptance criteria as "clkQltAcptCri" attribute if the feature "NetTimeSyncStatus" is supported) encoded as "asTimeDisParam" attribute. In the "AppAmContextData" data type in the content of the HTTP POST request the NF service consumer may include, when the NF service consumer is the NEF or the AF: + - the GPSI of the UE encoded as "gpsi" attribute; and/or + - the expiration time of the AF requested policy encoded as "expiry" attribute. + +The NF service consumer may also include the "evSubsc" attribute of "AmEventsSubscData" data type to request the notification of access and mobility policy changes events. The NF service consumer shall include within the "evSubsc" attribute: + +- the notification URI where the NF service consumer receives the events notification encoded as "eventNotifUri" attribute; and + +- the events to subscribe to in the "events" attribute. For each subscribed event in the "events" attribute, the NF service consumer shall include the event identifier within the "event" attribute and may include the description of the event reporting mode as specified in clause 4.2.5.2. + +The events subscription data is provisioned in the "AM Policy Events Subscription" sub-resource. + +The NF service consumer may include within the "evSubsc" attribute specific per event subscription information, if applicable, and as described in clause 4.2.2.3. + +If the PCF cannot successfully fulfil the received HTTP POST request due to the internal PCF error or due to the error in the HTTP POST request, the PCF shall send the HTTP error response as specified in clause 5.7. + +Otherwise, when the PCF receives the HTTP POST request from the NF service consumer, the PCF shall bind the Individual application AM context to the concerned AM policy association. The PCF identifies the AM policy association for which the HTTP POST request applies with the SUPI provided in the "supi" attribute within the body of the HTTP POST request: + +If the PCF fails in executing the binding with the AM policy association, the PCF shall reject the HTTP POST request with an HTTP "500 Internal Server Error" response and may include the "cause" attribute set to "POLICY\_ASSOCIATION\_NOT\_AVAILABLE". + +The PCF shall check whether the received access and mobility related service information requires access and mobility policies to be created and provisioned in the AMF. Provisioning of access and mobility policies shall be carried out as specified at 3GPP TS 29.507 [16]. + +If the PCF created an "Individual Application AM Context" resource, the PCF shall send to the NF service consumer a "201 Created" response to the HTTP POST request, as shown in figure 4.2.2.2-1, step 2. The PCF shall include in the "201 Created" response: + +- a Location header field; and +- an "AppAmContextRespData" data type in the content. + +The Location header field shall contain the URI of the created Individual application AM context resource i.e. "{apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId}". + +The "AppAmContextRespData" data type in the response content shall contain the representation of the created "Individual application AM context" resource within the "AppAmContextData" data type. When the request included event subscription information: + +- the "AppAmContextData" data type shall also include the "AM Policy Events Subscription" sub-resource representation within the "evSubsc" attribute; and +- when the NF service consumer requested the immediate reporting and the current value is available, the "AppAmContextRespData" data type shall include the corresponding event(s) notification, encoding the event identifier within the "repEvents" attribute and the applicable event(s) information as specified within the "AmEventsNotification" data type. + +The acknowledgement towards the NF service consumer should take place before or in parallel with any required access and mobility policy provisioning towards the AMF. + +NOTE: The behaviour when the NF service consumer does not receive the HTTP response message, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than a success indication, are outside the scope of this specification and is based on operator policy. + +#### 4.2.2.3 Creation of the subscription to service area coverage change outcome + +This procedure is used by a NF service consumer to subscribe to notifications about whether the requested service area coverage provided in the access and mobility service information has been provisioned as the corresponding Service Area Restrictions to the AMF or cannot be provisioned to the AMF. This procedure also enables the subscription to notifications about subsequent changes on the service area coverage result of changes of the provisioned Service Area Restrictions (e.g. due to changes in the subscribed Service Area Restrictions). + +To request to the PCF to provide a notification when a service area coverage (which may be same or different service area coverage from the service area coverage provided by the NF service consumer) has been determined (and the + +related policy for Service Area Restrictions is applied) based on the request or when a service area coverage cannot be determined and, additionally, when the service area coverage subsequently changes within the AM Policy Association, the NF service consumer shall provide in the HTTP POST request message described in clause 4.2.2.2 the "evSubsc" attribute including an event entry within the "events" attribute with the "event" attribute set to "SAC\_CH" and the "notifMethod" set to "ON\_EVENT\_DETECTION" (or omitted). + +The PCF shall reply to the NF service consumer as described in clause 4.2.2.2. + +When the service area coverage change event is met in the PCF, the PCF notifies to the NF service consumer as described in clause 4.2.7.4. + +### 4.2.3 Npcf\_AMPolicyAuthorization\_Update service operation + +#### 4.2.3.1 General + +The Npcf\_AMPolicyAuthorization\_Update service operation provides updated application level information from the NF service consumer and optionally communicates with the Npcf\_AMPolicyControl service to determine and install the access and mobility policies according to the information provided by the NF service consumer. + +The Npcf\_AMPolicyAuthorization\_Update service operation updates an AF application AM context in the PCF. + +The following procedures using the Npcf\_AMPolicyAuthorization\_Update service operation are supported: + +- Modification of AM related service information. +- Modification of the subscription to service area coverage change outcome. + +#### 4.2.3.2 Modification of AM related service information + +This procedure is used to modify an existing AF application AM context as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. + +Figure 4.2.3.2-1 illustrates the modification of access and mobility service information using HTTP PATCH method. + +![Sequence diagram showing the modification of access and mobility service information using HTTP PATCH. The NF service consumer sends a PATCH request to the PCF, and the PCF responds with a 200 OK status.](220869911a1ecfa1dd4aa6d750319aad_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. PATCH .../app-am-contexts/{appAmContextId} + NF service consumer->>PCF: Request + Note left of PCF: 2. "200 OK" + PCF-->>NF service consumer: Response +``` + +Sequence diagram showing the modification of access and mobility service information using HTTP PATCH. The NF service consumer sends a PATCH request to the PCF, and the PCF responds with a 200 OK status. + +**Figure 4.2.3.2-1: Modification of access and mobility service information using HTTP PATCH** + +The NF service consumer may modify the AF application AM context information at any time (e.g. due to an AF application AM context modification or an internal NF service consumer trigger) and invoke the Npcf\_AMPolicyAuthorization\_Update service operation by sending an HTTP PATCH request message to the resource URI representing the concerned "Individual application AM context" resource, as shown in figure 4.2.3.2-1, step 1, with the modifications to apply. + +The JSON body within the PATCH request shall include the "AppAmContextUpdateData" data type and shall be encoded according to "JSON Merge Patch", as defined in IETF RFC 7396 [18]. + +The NF service consumer may create, modify or remove access and mobility service information by including updated values within the "AppAmContextUpdateData" data type as follows: + +- the NF service consumer may update the "termNotifUri" attribute, to request that subsequent termination notifications are sent to a new NF service consumer; +- the NF service consumer may create or update the previously provided access and mobility service information, e.g. when the NF service consumer is the AF/NEF, expiration time, high throughput indication and/or service area coverage information, or, when the NF service consumer is the TSCTSF, 5G access stratum time distribution indication (enable, disable), and/or Uu time synchronization error budget, and optionally the clock quality detail level as "clkQltDetLvl" attribute and the clock quality acceptance criteria as "clkQltAcptCri" attribute if the feature "NetTimeSyncStatus" is supported (see clause 4.2.2.2); and- the NF service consumer may delete the previously provided attribute(s), e.g. when the NF service consumer is the AF/NEF, expiration time, high throughput indication and/or service area coverage information, or, when the NF service consumer is the TSCTSF, Uu time synchronization error budget, by setting them to null value, to indicate that the previously provided access and mobility service information no longer applies. + +The NF service consumer may also create, modify or remove events subscription information by sending an HTTP PATCH request message to the resource URI representing the concerned "Individual application AM context" resource. + +The NF service consumer shall create event subscription information by including the "evSubsc" attribute of "AmEventsSubscDataRm" data type with the corresponding list of events to subscribe to within the "events" attribute, and the callback URI where to receive the event notifications within the "eventNotifUri" attribute. For each subscribed event in the "events" attribute, the NF service consumer shall include the event identifier within the "event" attribute and may include the description of the event reporting mode as specified in clause 4.2.5.2. + +The NF service consumer shall update existing event subscription information by including an updated value of the "evSubsc" attribute of the "AmEventsSubscDataRm" data type as follows: + +- the "eventNotifUri" attribute may include an updated value of the callback URI; +- the "events" attribute shall include the new complete list of subscribed events; and + +NOTE: When the NF service consumer requests to remove an event, this event is not included in the "events" attribute. + +- the per specific event subscription information is included/removed, if applicable, and as described in clause 4.2.3.3. + +The NF service consumer shall remove existing event subscription information by setting to null the "evSubsc" attribute. + +If the service information provided in the body of the HTTP PATCH request is rejected because the requested policy for the AM context is invalid or insufficient for the PCF to perform the requested action because the service area coverage and/or high throughput policies present in the request result in an Individual application AM context without service area coverage and high throughput requested policies, or the request indicates the deletion of the 5G access stratum time distribution parameters resulting in an Individual application AM context without 5G access stratum time distribution and Uu time synchronization error budget requested policies, the PCF may indicate in an HTTP "400 Bad Request" response message the cause for the rejection including the "cause" attribute set to "INVALID\_POLICY\_REQUEST". + +If the PCF cannot successfully fulfil the received HTTP PATCH request due to the internal PCF error or due to the error in the HTTP PATCH request, the PCF shall send the HTTP error response as specified in clause 5.7. + +If the PCF determines the received HTTP PATCH request needs to be redirected, the PCF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +If the request is accepted, the PCF shall update the AM related service information with the new information received and/or update the associated AM events subscription. Due to the updated service information and/or AM events subscription, the PCF may need to create, modify or delete the related access and mobility policies and provide the updated information towards the AMF following the corresponding procedures specified in 3GPP TS 29.507 [16]. + +The PCF shall reply to the NF service consumer with an HTTP "200 OK" response message and include the "AppAmContextRespData" data type in the content which shall include: + +- the representation of the modified "Individual Application AM Context" resource within the "AppAmContextData" data type; and +- when the request included the creation or the update of the subscription to notification event(s): + +- a) the representation of the "AM Policy Events Subscription" sub-resource within the "evSubsc" attribute included in the "AppAmContextData" data type; and +- b) when the NF service consumer requested the immediate reporting of the new subscribed event(s) and the current value(s) is available, "AppAmContextRespData" data type shall include the corresponding event(s) notification encoding the event identifier within "repEvents" attribute and the applicable event(s) information as specified within the "AmEventsNotification" data type. + +The HTTP response message towards the NF service consumer should take place before or in parallel with any required access and mobility policy provisioning towards the SMF. + +#### 4.2.3.3 Modification of the subscription to service area coverage change outcome + +This procedure is used by a NF service consumer to subscribe to notifications about whether an updated service area coverage (which may be same or different service area coverage from the service area coverage provided by the NF service consumer) determined from the requested service area coverage provided in the access and mobility service information has been applied as the corresponding Service Area Restrictions or whether an updated service area coverage cannot be provisioned. This procedure also enables to modify or remove a previous subscription to service area coverage changes. + +The NF service consumer shall include in the HTTP PATCH request message described in clause 4.2.3.2 the "evSubsc" attribute as encoded as follows: + +- To create a subscription (i.e., the subscription to the "SAC\_CH" event does not exist in the PCF) the NF service consumer shall include the "evSubsc" attribute encoded as specified in clause 4.2.2.3. +- To modify an existing subscription, (i.e., the subscription to the "SAC\_CH" event exists in the PCF) the NF service consumer shall include within the "evSubsc" attribute the "events" attribute with the updated subscription information for the "event" attribute set to "SAC\_CH" as specified in clause 4.2.2.3. +- To remove an existing subscription (i.e., the subscription to the "SAC\_CH" event exists in the PCF): + - a. If there are other events whose subscription the NF service consumer wants to keep, the NF service consumer shall include the "events" attribute without any event entry with the "event" attribute set to "SAC\_CH". + - b. If there are no other events whose subscription the NF service consumer wants to keep, the NF service consumer shall set to null the "evSubsc" attribute. + +The PCF shall reply to the NF service consumer as described in clause 4.2.3.2. + +When the service area coverage change event is met in the PCF, the PCF notifies to the NF service consumer as described in clause 4.2.7.4. + +NOTE: When the previously provided service area coverage requirements are completely removed by the NF service consumer, or the requested service area coverage policy expires, the NF service consumer should also unsubscribe to SAC\_CH event to prevent the stale subscription information from remaining on the PCF. + +### 4.2.4 Npcf\_AMPolicyAuthorization\_Delete service operation + +#### 4.2.4.1 General + +The Npcf\_AMPolicyAuthorization\_Delete service operation provides means for the NF service consumer to delete the AF application AM context. + +The following procedures using the Npcf\_AMPolicyAuthorization\_Delete service operation are supported: + +- AF application AM context termination. + +#### 4.2.4.2 AF application AM context termination + +This procedure is used to terminate an AF application AM context as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. + +Figure 4.2.4.2-1 illustrates the AF application AM context termination. + +![Sequence diagram showing AF application AM context termination between NF service consumer and PCF.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. DELETE .../app-am-contexts/{appAmContextId} + NF service consumer->>PCF: 1. DELETE .../app-am-contexts/{appAmContextId} + Note left of PCF: 2. "204 No Content" + PCF-->>NF service consumer: 2. "204 No Content" +``` + +The diagram illustrates the interaction for AF application AM context termination. It features two lifelines: 'NF service consumer' on the left and 'PCF' on the right. Step 1 shows a solid arrow pointing from the NF service consumer to the PCF, labeled '1. DELETE .../app-am-contexts/{appAmContextId}'. Step 2 shows a solid arrow pointing from the PCF back to the NF service consumer, labeled '2. "204 No Content"'. Vertical lines extend downwards from each box to indicate the timeline of the sequence. + +Sequence diagram showing AF application AM context termination between NF service consumer and PCF. + +**Figure 4.2.4.2-1: AF application AM context termination** + +When an AF session is terminated, and if the AF application AM context was created as described in clause 4.2.2, the NF service consumer shall invoke the Npcf\_AMPolicyAuthorization\_Delete service operation to the PCF using an HTTP DELETE request, as shown in figure 4.2.4.2-1, step 1. + +The NF service consumer shall set the request URI to "{apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId}". + +When the PCF receives the HTTP DELETE request from the NF service consumer, indicating the termination of the AF application AM context information, if the HTTP DELETE request from the NF service consumer is accepted, the PCF shall acknowledge that request by sending to the NF service consumer a "204 No Content". + +Afterwards, the PCF shall determine whether the access and mobility policies of the concerned UE need to be updated or not. If the PCF determines that an update is needed, the PCF shall initiate the update of the access and mobility policies of the concerned UE as per the procedures specified in 3GPP TS 29.507 [16]. + +If the HTTP DELETE request from the NF service consumer is not accepted, the PCF shall indicate in the response to HTTP DELETE request the cause for the rejection as specified in clause 5.7. + +If the PCF determines the received HTTP DELETE request needs to be redirected, the PCF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +### 4.2.5 Npcf\_AMPolicyAuthorization\_Subscribe service operation + +#### 4.2.5.1 General + +The Npcf\_AMPolicyAuthorization\_Subscribe service operation enables to manage subscriptions to events for an existing AF application AM context. The Npcf\_AMPolicyAuthorization\_Subscribe service operation also enables to manage subscriptions to events without an existing AF application AM context. + +Such subscriptions to events shall be created: + +- within the AF application AM context establishment procedure by invoking the Npcf\_AMPolicyAuthorization\_Create service operation, as described in clause 4.2.2; +- within the AF application AM context modification procedure by invoking the Npcf\_AMPolicyAuthorization\_Update service operation, as described in clause 4.2.3; or +- by invoking the Npcf\_AMPolicyAuthorization\_Subscribe service operation for the existing AF application AM context, as described in clause 4.2.5.2. +- by invoking the Npcf\_AMPolicyAuthorization\_Subscribe service operation when there is no existing Individual application AM context and the NF service consumer does not provide Access and Mobility related service information, as described in clause 4.2.5.3. + +The following procedures using the Npcf\_AMPolicyAuthorization\_Subscribe service operation is supported: + +- Subscription to events for an existing AF application AM context. +- Subscription to events without an existing AF application AM context. +- Subscription to PDUID changes. + +#### 4.2.5.2 Handling of subscription to events for the existing AF application AM context + +This procedure is used to create a subscription to events for the existing AF application AM context or to modify an existing subscription, as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. + +Figure 4.2.5.2-1 illustrates the creation of events subscription information using HTTP PUT method. + +![Sequence diagram showing the creation of events subscription information using HTTP PUT method.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. PUT .../app-am-contexts/{appAmContextId}/events-subscription + NF service consumer->>PCF: 1. PUT .../app-am-contexts/{appAmContextId}/events-subscription + Note left of PCF: 2. "201 Created" + PCF-->>NF service consumer: 2. "201 Created" +``` + +The diagram illustrates the interaction between an NF service consumer and a PCF for creating an events subscription. The NF service consumer sends a PUT request to the PCF at the URI `.../app-am-contexts/{appAmContextId}/events-subscription`. The PCF responds with a "201 Created" status. + +Sequence diagram showing the creation of events subscription information using HTTP PUT method. + +Figure 4.2.5.2-1: Creation of events subscription information using HTTP PUT + +Figure 4.2.5.2-2 illustrates the modification of events subscription information using HTTP PUT method. + +![Sequence diagram showing the modification of events subscription information using HTTP PUT method.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. PUT .../app-am-contexts/{appAmContextId}/events-subscription + NF service consumer->>PCF: 1. PUT .../app-am-contexts/{appAmContextId}/events-subscription + Note left of PCF: 2a. "204 No Content" +2b. "200 OK" + PCF-->>NF service consumer: 2a. "204 No Content" +2b. "200 OK" +``` + +The diagram illustrates the interaction between an NF service consumer and a PCF for modifying an events subscription. The NF service consumer sends a PUT request to the PCF at the URI `.../app-am-contexts/{appAmContextId}/events-subscription`. The PCF responds with either a "204 No Content" or a "200 OK" status. A blue arrow points from the PCF box to the response message, indicating the return path. + +Sequence diagram showing the modification of events subscription information using HTTP PUT method. + +Figure 4.2.5.2-2: Modification of events subscription information using HTTP PUT + +When the NF service consumer decides to create a subscription to one or more events for the existing AF application AM context or to modify an existing subscription previously created by itself at the PCF, the NF service consumer shall invoke the Npcf\_AMPolicyAuthorization\_Subscribe service operation by sending the HTTP PUT request to the resource URI representing the "AM Policy Events Subscription" sub-resource in the PCF, as shown in figure 4.2.5.2-1, step 1 and figure 4.2.5.2-2, step 1. + +NOTE 1: The NF service consumer builds the "AM Policy Events Subscription" sub-resource URI by adding the path segment "/events-subscription" at the end of the resource URI of the "Individual application AM context" resource, received in the Location header field of the resource creation response as specified in clause 4.2.2.2. + +The NF service consumer shall provide in the "AmEventsSubscData" data type of the body of the HTTP PUT request: + +- the "events" attribute with the list of events to be subscribed; and + +- the "eventNotifUri" attribute, that includes the callback URI where the PCF shall send the notification of the subscribed events. + +NOTE 2: The "eventNotifUri" attribute within the "AmEventsSubscData" data structure can be modified to request that subsequent notifications are sent to a new NF service consumer. + +For each subscribed event included in the "events" attribute, the NF service consumer type shall include the event identifier within the "event" attribute and may include the description of the event reporting mode, as follows: + +- immediate reporting indication as "immRep" attribute; +- event notification method (periodic, one time, on event detection) as "notifMethod" attribute; +- maximum number of reports as "maxReportNbr" attribute; +- monitoring Duration as "monDur" attribute; and/or +- repetition period for periodic reporting as "repPeriod" attribute. + +The NF service consumer may provide within the "AmEventsSubscData" data type specific per event subscription information, if applicable, and as described in clause 4.2.2.3. + +NOTE: The NF service consumer can use this service operation to subscribe/unsubscribe to events that matched based on the provided requested policy related to the AM context (e.g. SAC\_CH event, which is matched based on the requested service area coverage). In these cases, to avoid the PCF keeping stale subscription information, the NF service consumer needs to ensure that the concerned requested policy exists together with the event subscription, i.e. the event subscription is removed when the related policy is removed. + +Upon the reception of the HTTP PUT request from the NF service consumer, the PCF shall decide whether the received HTTP PUT request is accepted. + +If the HTTP PUT request from the NF service consumer is not accepted, the PCF shall indicate in the response to HTTP PUT request the cause for the rejection as specified in clause 5.7. + +If the PCF determines the received HTTP PUT request needs to be redirected, the PCF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +If the PCF accepted the HTTP PUT request to create a subscription to events, the PCF shall create the "AM Policy Events Subscription" sub-resource and shall send the HTTP response message to the NF service consumer as shown in figure 4.2.5.2-1, step 2. The PCF shall include in the "201 Created" response: + +- a Location header field that shall contain the URI of the created "AM Policy Events Subscription" sub-resource i.e. "{apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId}/events-subscription"; and +- a response body with the "AmEventsSubscRespData" data type, which: + - shall contain the created "AM Policy Events Subscription" sub-resource encoded in the attributes of the "AmEventsSubscData" data type; and + - if the NF service consumer requested the immediate reporting and the current value is available, may contain the corresponding event(s) notification by encoding event identifier within the "repEvents" the attribute and the applicable event(s) information as specified within the "AmEventsNotification" data type. + +If the PCF accepted the HTTP PUT request to modify the events subscription, the PCF shall modify the "AM Policy Events Subscription" sub-resource and shall send to the NF service consumer: + +- the HTTP "204 No Content" response (as shown in figure 4.2.5.2-2, step 2a); or +- the HTTP "200 OK" response (as shown in figure 4.2.5.2-2, step 2b) including in the "AmEventsSubscRespData" data type: + - the updated representation of the "AM Policy Events Subscription" sub-resource encoded within the attributes of the "AmEventsSubscData" data type; and + +- b) if one or more of the updated subscribed events are already met in the PCF, the notification of these events by including the event identifier within the "repEvents" attribute and the applicable event(s) information as specified within the "AmEventsNotification" data type. + +When the "monDur" attribute is included in the response, it represents a server selected expiry time that is equal or less than a possible expiry time in the request. + +#### 4.2.5.3 Subscription to events without an existing AF application AM context + +This procedure is used by an NF service consumer (e.g. 5G DDNMF) to request the creation of a subscription to event(s) in the PCF when no "Individual application AM context" exists, and the NF service consumer does not provide Access and Mobility related service information, i.e., does not create an AF application AM context. + +Figure 4.2.5.3-1 illustrates the subscription to event(s) without an existing AF application AM context. + +![Sequence diagram showing the subscription process between an NF service consumer and a PCF.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of NF service consumer: 1. POST .../app-am-contexts + NF service consumer->>PCF: Request + Note left of PCF: 2. "201 Created" + PCF-->>NF service consumer: Response +``` + +The diagram illustrates a sequence of two messages between an NF service consumer and a PCF. The first message, labeled "1. POST .../app-am-contexts", is sent from the NF service consumer to the PCF. The second message, labeled "2. '201 Created'", is sent from the PCF back to the NF service consumer. + +Sequence diagram showing the subscription process between an NF service consumer and a PCF. + +**Figure 4.2.5.3-1: Subscription to events without an existing AF application AM context** + +When an NF service consumer (e.g. 5G DDNMF) decides to create a subscription to one or more event(s), and the NF service consumer is not providing Access and Mobility related service information and the "Individual application AM context" resource does not exist, the NF service consumer shall invoke the Npcf\_AMPolicyAuthorization\_Subscribe service operation to create an "Individual application AM context" resource and the corresponding "AM Policy Events Subscription" sub-resource by sending an HTTP POST request to the resource URI representing the "Application AM contexts" collection resource of the PCF, as shown in figure 4.2.5.3-1, step 1. + +The NF service consumer shall include in the AppAmContextData data type in the content of the HTTP POST request a partial representation of the "Individual Application AM Context" resource, which shall include: + +- the notification URI where the PCF shall request the termination of the application AM context to the NF service consumer, encoded as "termNotifUri" attribute; +- the SUPI encoded as "supi" attribute; and +- the "evSubsc" attribute to subscribe to notifications of access and mobility policy changes events. The NF service consumer shall include within the associated AmEventsSubscData data type: + - a. the notification URI where the NF service consumer wants to receive the event notifications, encoded as "eventNotifUri" attribute; and + - b. the event(s) to subscribe to within the "events" attribute. For each subscribed event, the AmEventData data type shall include the event identifier in the "event" attribute and may include the description of the event reporting mode as specified in clause 4.2.5.2. + +The event(s) subscription data is provisioned in the "AM Policy Events Subscription" sub-resource. + +If the PCF cannot successfully fulfil the received HTTP POST request due to the internal PCF error or due to the error in the HTTP POST request, the PCF shall send the HTTP error response as specified in clause 5.7. + +Otherwise, the PCF shall perform the association of the AF request to one and only one AM policy association or UE policy association. If the PCF fails in executing the binding with the AM policy association or UE policy association, + +the PCF shall reject the HTTP POST request with an HTTP "500 Internal Server Error" response and may include the "cause" attribute set to "POLICY\_ASSOCIATION\_NOT\_AVAILABLE". + +NOTE 1: In this release of the specification whether the AF request is associated to an AM policy association or to a UE policy association is determined per specific event, e.g., a subscription to PDUID changes implies the binding to a UE policy association. + +If the PCF created an "Individual Application AM Context" resource and the corresponding "AM Policy Events Subscription" sub-resource, the PCF shall send to the NF service consumer a "201 Created" response to the HTTP POST request, as shown in figure 4.2.5.3-1, step 2. The PCF shall include in the "201 Created" response: + +- a Location header field; and +- an AppAmContextRespData data type in the content. + +The Location header field shall contain the URI of the created "AM Policy Events Subscription" sub-resource, i.e., "{apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId}/events-subscription". + +The AppAmContextRespData data type in the response content shall contain: + +- the representation of the created "Individual application AM context" resource within the AppAmContextData data type, which shall also include the "AM Policy Events Subscription" sub-resource representation within the "evSubsc" attribute; and +- when the PCF determines that the subscribed event(s) is already met and/or the NF service consumer requested immediate reporting and the current value is available, the AppAmContextRespData data type shall include the corresponding event(s) notification within the "repEvents" attribute of the AmEventsNotification data type. + +NOTE 2: The created "Individual application AM context" resource does not include Access and Mobility related service information, only includes the information supplied by the NF service consumer to perform the association to the concerned AM policy association or UE policy association, i.e., the "supi" attribute, the SBI handling specific properties, i.e. the "suppFeat" attribute and the "termNotifUri" attribute, together with the "evSubsc" attribute. + +#### 4.2.5.4 Subscription to PDUID changes + +This procedure is used by a NF service consumer to request to subscribe to notifications of PDUID change event. + +The NF service consumer requests the subscription to notifications of PDUID change without providing (Access and Mobility or 5G ProSe) service information at initial subscription to event(s), using the HTTP POST request message as described in clause 4.2.5.3. + +The NF service consumer shall include within the "events" array attribute of the "evSubsc" attribute of the AppAmContextData data type: + +- an event with the "event" attribute set to "PDUID\_CH"; and +- to retrieve the current value of the PCF allocated PDUID for the UE, the request for immediate reporting by setting the "immRep" attribute to true. + +The PCF shall perform the association of the AF request to the UE policy association and shall retrieve the internally stored PDUID value allocated to the UE for the UE 5G ProSe Policy. + +Upon success, the PCF creates an "Individual Application AM Context" resource and the corresponding "AM Policy Events Subscription" sub-resource. The PCF shall then send a "201 Created" response to the HTTP POST request received from the NF service consumer, as described in clause 4.2.5.3, including the retrieved PDUID value within the AmEventsNotification data type as described in clause 4.2.7.5. + +### 4.2.6 Npcf\_AMPolicyAuthorization\_Unsubscribe service operation + +#### 4.2.6.1 General + +The Npcf\_AMPolicyAuthorization\_Unsubscribe service operation enables an NF service consumer to remove an existing subscription to event(s) for an existing AF application AM context. The Npcf\_AMPolicyAuthorization\_Unsubscribe service operation also enables an NF service consumers to remove an existing subscription to event(s) without an existing AF application AM context. + +Such subscription to events shall be removed: + +- by invoking the Npcf\_AMPolicyAuthorization\_Unsubscribe service operation for an existing AF application AM context, as described in clause 4.2.6.2; or +- within the AF application AM context modification procedure by invoking the Npcf\_AMPolicyAuthorization\_Update service operation, as described in clause 4.2.3; or +- within the AF application AM context termination procedure by invoking the Npcf\_AMPolicyAuthorization\_Delete service operation, as described in clause 4.2.4. +- by invoking the Npcf\_AMPolicyAuthorization\_Unsubscribe service operation when there is no existing Individual application AM context, as described in clause 4.2.6.3. + +The following procedures using the Npcf\_AMPolicyAuthorization\_Unsubscribe service operation are supported: + +- Unsubscription to events, Access and Mobility related service information exists. +- Unsubscription to events, Access and Mobility related service information does not exist. + +#### 4.2.6.2 Unsubscription to events, Access and Mobility related service information exists + +This procedure is used to unsubscribe to all subscribed events when the NF service consumer previously provided access and mobility related service information for the existing AF application AM context, as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. As result of this procedure, the "AM Policy Events Subscription" sub-resource is removed but the "Individual application AM context" remains with the access and mobility related service information. + +Figure 4.2.6.2-1 illustrates the procedure to unsubscribe from AM Policy Authorization event(s) using the HTTP DELETE method. + +![Sequence diagram showing the removal of events subscription information using HTTP DELETE. The NF service consumer sends a DELETE request to the PCF, and the PCF responds with a 204 No Content status.](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note left of NF service consumer: NF service consumer + Note right of PCF: PCF + NF service consumer->>PCF: 1. DELETE .../app-am-contexts/{appAmContextId}/events-subscription + PCF-->>NF service consumer: 2. "204 No Content" +``` + +Sequence diagram showing the removal of events subscription information using HTTP DELETE. The NF service consumer sends a DELETE request to the PCF, and the PCF responds with a 204 No Content status. + +**Figure 4.2.6.2-1: Removal of events subscription information using HTTP DELETE** + +When the NF service consumer decides to unsubscribe to all subscribed event(s) for an existing AF application AM context, and the NF service consumer previously provided access and mobility service information to the PCF, the NF service consumer shall invoke the Npcf\_AMPolicyAuthorization\_Unsubscribe service operation by sending an HTTP DELETE request message to the resource URI representing the concerned "AM Policy Events Subscription" sub-resource in the PCF, as shown in figure 4.2.6.2-1, step 1. + +Upon the reception of the HTTP DELETE request message from the NF service consumer, the PCF shall decide whether the received HTTP request message is accepted. + +If the HTTP DELETE request message from the NF service consumer is accepted, the PCF shall delete the "AM Policy Events Subscription" sub-resource and shall send to the NF service consumer a HTTP "204 No Content" response message. + +If the HTTP DELETE request message from the NF service consumer is rejected, the PCF shall indicate in the HTTP response message the cause for the rejection as specified in clause 5.7. + +If the PCF determines the received HTTP DELETE request needs to be redirected, the PCF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +#### 4.2.6.3 Unsubscription to events, Access and Mobility related service information does not exist + +This procedure is used by the NF service consumer to unsubscribe to all subscribed event(s) when the AF application AM context does not contain access and mobility related service information, i.e. only contains the "supi" attribute, the SBI handling specific properties, i.e. the "suppFeat" attribute and the "termNotifUri", together with the subscription information encoded in the "evSubsc" attribute. As a result of this procedure, the "AM Policy Events Subscription" sub-resource and the parent "Individual application AM context" resource are both removed. + +The procedure to unsubscribe from AM Policy Authorization events when the AF application AM context does not contain access and mobility related service information is the same as the procedure to delete the AF application AM context defined in clause 4.2.4.2. + +### 4.2.7 Npcf\_AMPolicyAuthorization\_Notify service operation + +#### 4.2.7.1 General + +The Npcf\_AMPolicyAuthorization\_Notify service operation enables to notify to the NF service consumers that the previously subscribed event for the existing AF application AM context occurred or that the AF application AM context is no longer valid. + +The following procedures using the Npcf\_AMPolicyAuthorization\_Notify service operation are supported: + +- Notification about AF application AM context event. +- Notification about AF application AM context termination. +- Notification about service area coverage change outcome. +- Notification about PDUID changes. + +#### 4.2.7.2 Notification about AF application AM context event + +This procedure is invoked by the PCF to notify the NF service consumer when a certain, previously subscribed, AF application AM context event occurs, as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. + +Figure 4.2.7.2-1 illustrates the notification about AF application AM context event. + +![Sequence diagram showing notification about AF application AM context event between NF service consumer and PCF.](26d664119ad25250780f554633444e54_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant PCF + Note right of PCF: 1. POST .../{eventNotifUri} + PCF->>NF service consumer: 1. POST .../{eventNotifUri} + Note left of NF service consumer: 2. "204 No Content" + NF service consumer-->>PCF: 2. "204 No Content" +``` + +The diagram illustrates a sequence of two messages between an NF service consumer and a PCF. The first message, labeled '1. POST .../{eventNotifUri}', is sent from the PCF to the NF service consumer. The second message, labeled '2. "204 No Content"', is sent from the NF service consumer back to the PCF. + +Sequence diagram showing notification about AF application AM context event between NF service consumer and PCF. + +**Figure 4.2.7.2-1: Notification about AF application AM context event** + +When the PCF determines that the event for the existing AF application AM context, to which the NF service consumer has subscribed to, occurred, the PCF shall invoke the Npcf\_AMPolicyAuthorization\_Notify service operation by sending the HTTP POST request (as shown in figure 4.2.7.2-1, step 1) to the NF service consumer using the callback URI received in the subscription creation (or modification), as specified in clauses 4.2.2.2, 4.2.3.2 and 4.2.5.2. The PCF shall provide in the body of the HTTP POST request the "AmEventsNotification" data type including: + +- the AM Policy Events Subscription resource identifier related with the notification in the "appAmContextId" attribute; and +- the list of the reported events in the "repEvents" attribute. For each reported event, the "AmEventNotification" data type may include additional event information. + +The notification of other specific events using the Npcf\_AMPolicyAuthorization\_Notify request is described in the related clauses. + +Upon the reception of the HTTP POST request from the PCF indicating that the subscribed event occurred, the NF service consumer shall acknowledge that request by sending an HTTP response message with the corresponding status code. + +If the HTTP POST request from the PCF is not accepted, the NF service consumer shall indicate in the response to HTTP POST request the cause for the rejection as specified in clause 5.7. + +If the HTTP POST request from the PCF is accepted, the NF service consumer shall acknowledge the receipt of the event notification with a "204 No Content" response to HTTP POST request, as shown in figure 4.2.7.2-1, step 2. + +If the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +#### 4.2.7.3 Notification about AF application AM context termination + +This procedure is invoked by the PCF to notify the NF service consumer that the AF application AM context is no longer valid, as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. + +Figure 4.2.7.3-1 illustrates the notification about AF application AM context termination. + +![Sequence diagram showing notification about AF application AM context termination. The diagram involves two participants: NF service consumer and PCF. Step 1: The PCF sends a POST request to the NF service consumer using the callback URI. Step 2: The NF service consumer responds with a '204 No Content' status code.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant PCF + participant NF as NF service consumer + Note right of PCF: 1. POST .../{termNotifUri} + PCF->>NF: Request + Note left of NF: 2. "204 No Content" + NF-->>PCF: Response + +``` + +Sequence diagram showing notification about AF application AM context termination. The diagram involves two participants: NF service consumer and PCF. Step 1: The PCF sends a POST request to the NF service consumer using the callback URI. Step 2: The NF service consumer responds with a '204 No Content' status code. + +**Figure 4.2.7.3-1: Notification about AF application AM context termination** + +When the PCF determines that the AF application AM context is no longer valid, the PCF shall invoke the Npcf\_AMPolicyAuthorization\_Notify service operation by sending the HTTP POST request (as shown in figure 4.2.7.3-1, step 1) using the callback URI received in the "Individual application AM context" resource creation, as specified in clause 4.2.2.2. The PCF shall provide in the body of the HTTP POST request the "AmTerminationInfo" data type including: + +- the Individual application AM context resource identifier related to the termination notification within the "appAmContextId" attribute; and +- the AF application AM context termination cause within the "termCause" attribute encoded using of the "AmTerminationCause" data type, indicating the termination cause. + +Upon the reception of the HTTP POST request from the PCF requesting the AF application AM context termination, the NF service consumer shall acknowledge that request by sending an HTTP response message with the corresponding status code. + +If the HTTP POST request from the PCF is not accepted, the NF service consumer shall indicate in the response to HTTP POST request the cause for the rejection as specified in clause 5.7. + +If the HTTP POST request from the PCF is accepted, the NF service consumer shall acknowledge the receipt of the AF application AM context termination request with a "204 No Content" response (as shown in figure 4.2.7.3-1, step 2) and shall invoke the Npcf\_AMPolicyAuthorization\_Delete service operation to the PCF as described in clause 4.2.4. + +If the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4]. + +#### 4.2.7.4 Notification about service area coverage change outcome + +When the PCF becomes aware that the request received from the NF service consumer to change the service area coverage is performed, it shall inform the NF service consumer accordingly if the NF service consumer has previously subscribed to the "SAC\_CH" event as described in clauses 4.2.2.3 and 4.2.3.3. + +The PCF shall notify the NF service consumer by including the AmEventsNotification data type in the body of the HTTP POST request as described in clause 4.2.7.2. The PCF shall include within an entry of the "repEvents" attribute: + +- the "event" attribute set to "SAC\_CH" in the "event" attribute; +- the applied service area coverage (same or different service area coverage from the service area coverage provided by the NF service consumer) in the "appliedCov" attribute. + +When the result of the execution of the request of service area coverage is that the service is allowed in one or more of the requested Tracking Areas in the serving network where the UE is camping, the "appliedCov" attribute shall encode within the "tacList" attribute the list of NF consumer provided Tracking Area codes where the requested service shall be allowed and within the "servingNetwork" attribute the serving network where the UE is camping. + +When the result of the execution of the request of service area coverage change is that the service is restricted in the whole NF requested service area coverage, the "appliedCov" attribute shall encode an empty array within the "tacList" attribute. + +NOTE: The actual service area coverage for the UE might be larger than the one reported within "appliedCov" attribute. The "appliedCov" attribute provides to the NF consumer feedback about where the service is allowed in relation to the NF consumer provided service area coverage. + +When the NF service consumer indicated that the notification method is "ON\_EVENT\_DETECTION" (or omitted it) during the subscription, the subscription to this event is kept in the PCF until the NF service consumer terminates the subscription as described in clause 4.2.3.2 or 4.2.6.2. The NF service consumer shall be notified of subsequent service area coverage changes (i.e., changes in the applied service area coverage, which may indicate e.g. no service area coverage is allowed) as specified in bullets above without requiring a new subscription, both, when the service area coverage change is triggered by the NF service consumer and/or triggered by other events (e.g. based on PCF internal policies and/or changes in the subscribed service area restrictions), and as long as the requested service area coverage requirements exist (e.g. they have not expired). + +Upon receipt of the HTTP POST request from the PCF, the NF service consumer shall acknowledge the request by sending a "204 No Content" response as described in clause 4.2.7.2. + +#### 4.2.7.5 Notification about PDUID changes + +When the PCF allocates a new PDUID (ProSe Discovery UE ID) for the UE 5G ProSe Policy of a SUPI, the PCF shall inform the NF service consumer that previously subscribed as described in clause 4.2.5.4. + +The PCF shall notify the NF service consumer by including the AmEventsNotification data type in the body of the HTTP POST request as described in clause 4.2.7.2, which shall include within an entry of the "repEvents" attribute: + +- the "PDUID\_CH" event within the "event" attribute; and +- the "pduidInfo" attribute, with the allocated PDUID within the "pduid" attribute and its validity timer within the "expiry" attribute. + +When the NF service consumer receives the notification in the HTTP POST request, it shall acknowledge the request by sending a "204 No Content" response to the PCF as specified in clause 4.2.7.2. + +# --- 5 Npcf\_AMPolicyAuthorization Service API + +## 5.1 Introduction + +The Npcf\_AMPolicyAuthorization shall use the Npcf\_AMPolicyAuthorization API. + +The API URI of the Npcf\_AMPolicyAuthorization API shall be: + +**{apiRoot}/<apiName>/<apiVersion>** + +The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The <apiName> shall be "npcf-am-policyauthorization". +- The <apiVersion> shall be "v1". +- The <apiSpecificResourceUriPart> shall be set as described in clause 5.3. + +## 5.2 Usage of HTTP + +### 5.2.1 General + +HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Npcf\_AMPolicyAuthorization API is contained in Annex A. + +### 5.2.2 HTTP standard headers + +#### 5.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +#### 5.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13]. + +JSON object used in the HTTP PATCH request shall be encoded according to "JSON Merge Patch" and shall be signalled by the content type "application/merge-patch+json", as defined in IETF RFC 7396 [18]. + +### 5.2.3 HTTP custom headers + +#### 5.2.3.1 General + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported. + +In this Release of the specification, no specific custom headers are defined for the Npcf\_AMPolicyAuthorization API. + +## 5.3 Resources + +### 5.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 5.3.1-1 depicts the resource URIs structure for the Npcf\_AMPolicyAuthorization API. + +![A hierarchical diagram showing the resource URI structure. The root is {apiRoot}/npcf-am-policyauthorization/<apiVersion>. A line descends from this root to a box containing /app-am-contexts. From this box, a line descends to another box containing /{appAmContextId}. From this second box, a line descends to a third box containing /events-subscription.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +{apiRoot}/npcf-am-policyauthorization/<apiVersion> + +``` + +graph TD + Root["{apiRoot}/npcf-am-policyauthorization/<apiVersion>"] --> Box1["/app-am-contexts"] + Box1 --> Box2["/{appAmContextId}"] + Box2 --> Box3["/events-subscription"] + +``` + +A hierarchical diagram showing the resource URI structure. The root is {apiRoot}/npcf-am-policyauthorization/. A line descends from this root to a box containing /app-am-contexts. From this box, a line descends to another box containing /{appAmContextId}. From this second box, a line descends to a third box containing /events-subscription. + +**Figure 5.3.1-1: Resource URI structure of the Npcf\_AMPolicyAuthorization API** + +Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 5.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|-----------------------------------|-------------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Application AM contexts | /app-am-contexts | POST | Npcf_AMPolicyAuthorization_Create.<br>Creates a new Individual application AM context resource and may create the child AM Policy Events Subscription sub-resource. | +| Individual application AM context | /app-am-contexts/{appAmContextId} | PATCH | Npcf_AMPolicyAuthorization_Update.<br>Updates an existing Individual application AM context resource. It can also create or update an AM Policy Events Subscription sub-resource. | +| | | GET | Reads an existing Individual application AM context resource. | +| | | DELETE | Npcf_AMPolicyAuthorization_Delete.<br>Deletes an existing Individual application AM context resource and the child AM Policy Events Subscription sub-resource. | +| AM Policy Events Subscription | /app-am-contexts/{appAmContextId}/events-subscription | PUT | Npcf_AMPolicyAuthorization_Subscribe.<br>Creates a new AM Policy Events Subscription sub-resource or modifies an existing AM Policy Events Subscription sub-resource. | +| | | DELETE | Npcf_AMPolicyAuthorization_Unsubscribe.<br>Deletes an AM Policy Events Subscription sub-resource. | + +### 5.3.2 Resource: Application AM contexts (Collection) + +#### 5.3.2.1 Description + +The Application AM contexts resource represents all application AM contexts that exist in the Npcf\_AMPolicyAuthorization service at a given PCF instance. + +#### 5.3.2.2 Resource Definition + +Resource URI: {apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts + +This resource shall support the resource URI variables defined in table 5.3.2.2-1. + +**Table 5.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 5.1 | + +#### 5.3.2.3 Resource Standard Methods + +##### 5.3.2.3.1 POST + +This method shall support the URI query parameters specified in table 5.3.2.3.1-1. + +**Table 5.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 5.3.2.3.1-2 and the response data structures and response codes specified in table 5.3.2.3.1-3. + +**Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------|---|-------------|------------------------------------------------------------------------------------------------| +| AppAmContextData | M | 1 | Contains the information for the creation of a new Individual application AM context resource. | + +**Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AppAmContextResp Data | M | 1 | 201 Created | Successful case.<br>The creation of an Individual application AM context resource is confirmed and a representation of that resource is returned, together with event subscription and event notification information, if available, as specified in clause 4.2.2.2. | +| ProblemDetails | O | 0..1 | 500 Internal Server Error | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +NOTE 2: Failure cases are described in clause 5.7. + +**Table 5.3.2.3.1-4: Headers supported by the 201 response code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:<br>{apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId} | + +#### 5.3.2.4 Resource Custom Operations + +None. + +### 5.3.3 Resource: Individual application AM context (Document) + +#### 5.3.3.1 Description + +The Individual application AM context resource represents a single application AM context that exists in the Npcf\_AMPolicyAuthorization. + +#### 5.3.3.2 Resource Definition + +Resource URI: {apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId} + +This resource shall support the resource URI variables defined in table 5.3.3.2-1. + +**Table 5.3.3.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|----------------|-----------|---------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.1 | +| appAmContextId | string | Identifies an application AM context formatted according to IETF RFC 3986 [19]. | + +#### 5.3.3.3 Resource Standard Methods + +##### 5.3.3.3.1 GET + +This method shall support the URI query parameters specified in table 5.3.3.3.1-1. + +**Table 5.3.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 5.3.3.3.1-2 and the response data structures and response codes specified in table 5.3.3.3.1-3. + +**Table 5.3.3.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 5.3.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------| +| AppAmContextData | M | 1 | 200 OK | Successful case.<br>A representation of an Individual application AM context resource is returned. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during an Individual application AM context retrieval.<br>(NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during an Individual application AM context resource retrieval.<br>(NOTE 3) | +| ProblemDetails | O | 0..1 | 404 Not Found | (NOTE 2) | +| NOTE 1: The mandatory HTTP error status code for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. | | | | | +| NOTE 2: Failure cases are described in clause 5.7. | | | | | +| NOTE 3: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). | | | | | + +**Table 5.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +**Table 5.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +##### 5.3.3.3.2 PATCH + +This method shall support the URI query parameters specified in table 5.3.3.3.2-1. + +**Table 5.3.3.3.2-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 5.3.3.3.2-2 and the response data structures and response codes specified in table 5.3.3.3.2-3. + +**Table 5.3.3.3.2-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|------------------------------------------------------------------------------------------| +| AppAmContextUpdateData | M | 1 | Contains the modification(s) to apply to the Individual application AM context resource. | + +**Table 5.3.3.3.2-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|--------------------------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AppAmContextResponseData | M | 1 | 200 OK | Successful case.<br>A representation of an Individual application AM context resource, together with event subscription and event notification information, if available, as specified in clause 4.2.3.2. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during an Individual application AM context modification.<br>(NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during an Individual application AM context modification.<br>(NOTE 3) | +| ProblemDetails | O | 0..1 | 400 Bad Request | (NOTE 2) | +| ProblemDetails | O | 0..1 | 404 Not Found | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the PATCH method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: Failure cases are described in clause 5.7. +NOTE 3: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.3.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +**Table 5.3.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +##### 5.3.3.3.3 DELETE + +This method shall support the URI query parameters specified in table 5.3.3.3.3-1. + +**Table 5.3.3.3.3-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 5.3.3.3.3-2 and the response data structures and response codes specified in table 5.3.3.3.3-3. + +**Table 5.3.3.3.3-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 5.3.3.3.3-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case.<br>The Individual application AM context resource is deleted. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Individual application AM context termination.<br><br>(NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Individual application AM context termination.<br><br>(NOTE 3) | +| ProblemDetails | O | 0..1 | 404 Not Found | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: Failure cases are described in clause 5.7. +NOTE 3: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.3.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +**Table 5.3.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +#### 5.3.3.4 Resource Custom Operations + +None. + +### 5.3.4 Resource: AM Policy Events Subscription (Document) + +#### 5.3.4.1 Description + +The AM Policy Events Subscription resource represents a subscription to access and mobility policy events for an application AM context that exists in the Npcf\_AMPolicyAuthorization service. + +#### 5.3.4.2 Resource definition + +Resource URI: {apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId}/events-subscription + +This resource shall support the resource URI variables defined in table 5.3.4.2-1. + +**Table 5.3.4.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|----------------|-----------|---------------------------------------------------------------------------------| +| apiRoot | string | See clause 5.1 | +| appAmContextId | string | Identifies an application AM context formatted according to IETF RFC 3986 [19]. | + +#### 5.3.4.3 Resource Standard Methods + +##### 5.3.4.3.1 PUT + +This method shall support the URI query parameters specified in table 5.3.4.3.1-1. + +**Table 5.3.4.3.1-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 5.3.4.3.1-2 and the response data structures and response codes specified in table 5.3.4.3.1-3. + +**Table 5.3.4.3.1-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|------------------------------------------------------------------------------------------------------------------| +| AmEventsSubscData | M | 1 | Contains the information for the creation and/or modification of the AM Policy Events Subscription sub-resource. | + +Table 5.3.4.3.1-3: Data structures supported by the PUT Response Body on this resource + +| Data type | P | Cardinality | Response codes | Description | +|------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AmEventsSubscResp Data | M | 1 | 201 Created | Successful case.<br>The AM Policy Events Subscription sub-resource was created. The representation of the AM Policy Events Subscription sub-resource is included within the properties of the AmEventsSubscData data type. The one or more matched events, if available, are included within the properties of the AmEventsNotification data type. | +| AmEventsSubscResp Data | M | 1 | 200 OK | Successful case.<br>The AM Policy Events Subscription sub-resource was modified and a representation of the sub-resource is returned. The representation of the AM Policy Events Subscription sub-resource is included within the properties of the AmEventsSubscData data type. The one or more matched events, if available, are included within the properties of the AmEventsNotification data type. | +| n/a | | | 204 No Content | Successful case.<br>The AM Policy Events Subscription sub-resource was modified. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during AM Policy Events Subscription modification.<br><br>(NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during AM Policy Events Subscription modification.<br><br>(NOTE 3) | +| ProblemDetails | O | 0..1 | 404 Not Found | (NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the PUT method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +NOTE 2: Failure cases are described in clause 5.7. + +NOTE 3: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +Table 5.3.4.3.1-4: Headers supported by the 201 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:<br>{apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId}/events-subscription | + +Table 5.3.4.3.1-5: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +**Table 5.3.4.3.1-6: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +##### 5.3.4.3.2 DELETE + +This method shall support the URI query parameters specified in table 5.3.4.3.2-1. + +**Table 5.3.4.3.2-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 5.3.4.3.2-2 and the response data structures and response codes specified in table 5.3.4.3.2-3. + +**Table 5.3.4.3.2-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 5.3.4.3.2-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|--------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case.<br>The AM Policy Events Subscription resource is deleted. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during AM Policy Events Subscription termination.<br><br>(NOTE 3) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during AM Policy Events Subscription termination.<br><br>(NOTE 3) | +| ProblemDetails | O | 0..1 | 404 Not Found | (NOTE 2) | +| NOTE 1: The mandatory HTTP error status code for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. | | | | | +| NOTE 2: Failure cases are described in clause 5.7. | | | | | +| NOTE 3: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). | | | | | + +**Table 5.3.4.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +**Table 5.3.4.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI of the resource located in an alternative PCF (service) instance towards which the request is redirected.<br><br>For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target PCF (service) instance towards which the request is redirected. | + +#### 5.3.4.4 Resource Custom Operations + +None. + +## 5.4 Custom Operations without associated resources + +None. + +## 5.5 Notifications + +### 5.5.1 General + +Notifications shall comply to clause 6.2 of 3GPP TS 29.500 [4] and clause 4.6.2.3 of 3GPP TS 29.501 [5]. + +**Table 5.5.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|-----------------------|-----------------|---------------------------------|------------------------------------------------------------------| +| AM Event Notification | {eventNotifUri} | POST | Notification of access and mobility policy changes event(s). | +| Termination Request | {termNotifUri} | POST | Request for termination of an Individual application AM context. | + +### 5.5.2 AM Event Notification + +#### 5.5.2.1 Description + +The AM Event Notification is used by the NF service producer to report one or several observed Access and Mobility policy change Events to a NF service consumer that has subscribed to such Notifications via the AM Policy Events Subscription Resource. + +#### 5.5.2.2 Target URI + +The Callback URI "{eventNotifUri}" shall be used with the callback URI variables defined in table 5.5.2.2-1. + +**Table 5.5.2.2-1: Callback URI variables** + +| Name | Definition | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| eventNotifUri | String formatted as URI with the Callback Uri.<br>The Callback Uri is assigned within the AM Policy Events Subscription sub-resource and described within the AmEventsSubscData data type (see table 5.6.2.4-1) or AmEventsSubscDataRm data type (see table 5.6.2.7-1). | + +#### 5.5.2.3 Standard Methods + +##### 5.5.2.3.1 POST + +This method shall support the request data structures specified in table 5.5.2.3.1-1 and the response data structures and response codes specified in table 5.5.2.3.1-2. + +**Table 5.5.2.3.1-1: Data structures supported by the POST Request Body** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|-----------------------------------------------------------------------------------| +| AmEventsNotification | M | 1 | Provides information about the observed access and mobility policy change events. | + +**Table 5.5.2.3.1-2: Data structures supported by the POST Response Body** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|------------------------------------------------------------------| +| n/a | | | 204 No content | The receipt of the Notification is acknowledged. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during AM event notification.<br>(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during AM event notification.<br>(NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. + +NOTE 2: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +**Table 5.5.2.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification is redirected.<br><br>For the case where the notification is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected. | + +**Table 5.5.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification is redirected.<br><br>For the case where the notification is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected. | + +### 5.5.3 Termination Request + +#### 5.5.3.1 Description + +The Termination request is used by the NF service producer to request the NF service consumer the deletion of the Individual Application AM context Resource. + +#### 5.5.3.2 Target URI + +The Callback URI "{termNotifUri}" shall be used with the callback URI variables defined in table 5.5.3.2-1. + +**Table 5.5.3.2-1: Callback URI variables** + +| Name | Definition | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| termNotifUri | String formatted as URI with the Callback Uri.<br>The Callback Uri is assigned within the Individual application AM Context resource and described within the AppAmContextData data type (see table 5.6.2.2-1) or AppAmContextUpdateData data type (see table 5.6.2.3-1). | + +#### 5.5.3.3 Standard Methods + +##### 5.5.3.3.1 POST + +This method shall support the request data structures specified in table 5.5.3.3.1-1 and the response data structures and response codes specified in table 5.5.3.3.1-1. + +**Table 5.5.3.3.1-2: Data structures supported by the POST Request Body** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|------------------------------------------------------------------| +| AmTerminationInfo | M | 1 | Provides information about the cause of the termination request. | + +Table 5.5.3.3.1-3: Data structures supported by the POST Response Body + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|----------------------------------------------------------------------| +| n/a | | | 204 No content | The receipt of the Notification is acknowledged. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during AM event notification.<br><br>(NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during AM event notification.<br><br>(NOTE 2) | + +NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: The RedirectResponse data structure may be provided by an SCP (see clause 6.10.9.1 of 3GPP TS 29.500 [4]). + +Table 5.5.3.3.1-4: Headers supported by the 307 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification is redirected.<br><br>For the case where the notification is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected. | + +Table 5.5.3.3.1-5: Headers supported by the 308 Response Code on this resource + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification is redirected.<br><br>For the case where the notification is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4]. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected. | + +## 5.6 Data Model + +### 5.6.1 General + +This clause specifies the application data model supported by the API. + +Table 5.6.1-1 specifies the data types defined for the Npcf\_AMPolicyAuthorization service based interface protocol. + +Table 5.6.1-1: Npcf\_AMPolicyAuthorization specific Data Types + +| Data type | Clause defined | Description | Applicability | +|-----------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| AmEvent | 5.6.3.3 | It represents the event the PCF can notify to the NF service consumer. | | +| AmEventNotification | 5.6.2.9 | Represents the notification of an event. | | +| AmEventData | 5.6.2.8 | It contains the event identifier and the related event reporting information. | | +| AmEventsNotification | 5.6.2.5 | It describes the notification about the events occurred within an Individual application AM context resource. | | +| AmEventsSubscData | 5.6.2.4 | It represents the AM Policy Events Subscription resource and identifies the events the application subscribes to. | | +| AmEventsSubscDataRm | 5.6.2.7 | This data type is defined in the same way as the "AmEventsSubscData" data type, but with the OpenAPI "nullable: true" property. | | +| AmEventsSubscRespData | 5.6.4.2 | It represents a response to an AM Policy Events Subscription request and contains the created/updated AM Policy Events Subscription resource. It may also include the Notification of the events met at the time of subscription.<br>It is represented as a non-exclusive list of two data types: AmEventsSubscData and AmEventsNotification. | | +| AmTerminationCause | 5.6.3.5 | It represents the cause values that the PCF should report when requesting to an NF service consumer the deletion of an "AF application AM context" resource. | | +| AmTerminationInfo | 5.6.2.6 | It includes information related to the termination of the Individual Application AM Context resource. | | +| AppAmContextData | 5.6.2.2 | It represents an Individual application AM context resource. | | +| AppAmContextRespData | 5.6.4.1 | It represents a response to a modification or creation request of an Individual application AM context resource.<br>It is represented as a non-exclusive list of two data types AppAmContextData and AmEventsNotification. | | +| AppAmContextUpdateData | 5.6.2.3 | It describes the modifications to an Individual application AM context resource. | | +| PduidInformation | 5.6.2.10 | It contains the PDUID and its validity timer. | | +| ServiceAreaCovera<br>geInfo | 5.6.2.11 | It represents a list of Tracking Areas within a serving network. | | + +Table 5.6.1-2 specifies data types re-used by the Npcf\_AMPolicyAuthorization service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Npcf\_AMPolicyAuthorization service based interface. + +**Table 5.6.1-2: Npcf\_AMPolicyAuthorization re-used Data Types** + +| <b>Data type</b> | <b>Reference</b> | <b>Comments</b> | <b>Applicability</b> | +|-------------------------|---------------------|--------------------------------------------------------------------------------------------------------------|----------------------| +| AsTimeDistributionParam | 3GPP TS 29.507 [16] | Contains the 5G access stratum time distribution parameters. | | +| DurationSec | 3GPP TS 29.571 [20] | Indicates a period of time in units of seconds. | | +| DurationSecRm | 3GPP TS 29.571 [20] | It is defined as DurationSec but with the nullable property set to "true". | | +| Gpsi | 3GPP TS 29.571 [20] | Identifies a GPSI. | | +| NotificationMethod | 3GPP TS 29.508 [21] | It includes information about the notification methods that can be subscribed by the NF service consumer. | | +| Pduid | 3GPP TS 29.555 [24] | String containing a PDUID | | +| RedirectResponse | 3GPP TS 29.571 [20] | It contains redirection related information. | | +| Supi | 3GPP TS 29.571 [20] | Identifies the SUPI. | | +| SupportedFeatures | 3GPP TS 29.571 [20] | Used to negotiate the applicability of the optional features defined in table 5.8-1. | | +| Tac | 3GPP TS 29.571 [20] | It contains a Tracking Area Code | | +| PlmnIdNid | 3GPP TS 29.571 [20] | It contains the serving PLMN ID and, for a SNPN, the NID that together with the PLMN ID identifies the SNPN. | | +| Uinteger | 3GPP TS 29.571 [20] | Unsigned integer. | | +| Uri | 3GPP TS 29.571 [20] | String providing a URI. | | + +### 5.6.2 Structured data types + +#### 5.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +#### 5.6.2.2 Type: AppAmContextData + +Table 5.6.2.2-1: Definition of type AppAmContextData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| evSubsc | AmEventsSubscData | O | 0..1 | Represents the subscription to one or more AM policy events. (NOTE 1) | | +| supi | Supi | M | 1 | Identifies the SUPI. | | +| gpsi | Gpsi | O | 0..1 | Identifies the GPSI. | | +| suppFeat | SupportedFeatures | C | 0..1 | This IE represents a list of Supported features used as described in clause 5.8. It shall be supplied by the NF service consumer in the POST request that requests a creation of an Individual application AM context resource. It shall be supplied by the PCF in the response to the POST request that requests a creation of an Individual application AM context resource. | | +| termNotifUri | Uri | M | 1 | Identifies the callback URI where the PCF notifies termination requests. | | +| expiry | DurationSec | O | 0..1 | Indicates the time duration that the requested policy shall last. If omitted, it indicates that the requested policy lasts till the Individual Application AM context resource is deleted. | | +| highThruInd | boolean | C | 0..1 | Indicates whether high throughput is desired for the indicated UE traffic. Set to "true" if high throughput is desired; otherwise set to "false". Default value is "false" if omitted. (NOTE 1) | | +| covReq | array(ServiceAreaCoverageInfo) | C | 1..N | Identifies a list of Tracking Areas per serving network where the service is allowed. (NOTE 1) | | +| asTimeDisParam | AsTimeDistributionParam | C | 0..1 | Contains the 5G access stratum time distribution parameters. (NOTE 1) (NOTE 2) | | + +NOTE 1: When neither the "asTimeDisParam" attribute is included nor the "evSubsc" is provided to subscribe to events without an existing AF application AM context, the "highThruInd" attribute, the "covReq" attribute or both of them shall be included. When neither the "highThruInd" attribute nor the "covReq" attribute is included, then the "asTimeDisParam" attribute shall be included, unless the data type is used for subscribing to events without an existing AF application AM context as described in clause 4.2.5.3, in which case it is sufficient to provide the "evSubsc" attribute. + +NOTE 2: The "clkQltDetLvl" attribute and the "clkQltAcptCri" attribute within "asTimeDisParam" attribute may be provided only if the "NetTimeSyncStatus" feature is supported. + +#### 5.6.2.3 Type: AppAmContextUpdateData + +Table 5.6.2.3-1: Definition of type AppAmContextUpdateData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| evSubsc | AmEventsSubscDataRm | O | 0..1 | Represents the subscription to one or more AM policy events. | | +| termNotifUri | Uri | O | 0..1 | Identifies the callback URI where the PCF notifies termination requests. | | +| expiry | DurationSecRm | O | 0..1 | The expiration time of the AM related policy. If removed (i.e. set to "NULL"), it indicates that the requested policy lasts till the Individual Application AM context resource is deleted. | | +| highThrUInd | boolean | O | 0..1 | Indicates whether high throughput is desired for the indicated UE traffic. Set to "true" if high throughput is desired; otherwise set to "false". | | +| covReq | array(ServiceAreaCoverageInfo) | O | 1..N | Identifies a list of Tracking Areas per serving network where the service is allowed. | | +| asTimeDisParam | AsTimeDistributionParam | O | 0..1 | Contains the 5G access stratum time distribution parameters. (NOTE) | | + +NOTE: The "clkQltDetLvl" attribute and "clkQltAcptCri" within "asTimeDisParam" attribute may be provided only if the "NetTimeSyncStatus" feature is supported. + +#### 5.6.2.4 Type: AmEventsSubscData + +Table 5.6.2.4-1: Definition of type AmEventsSubscData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------|---|-------------|--------------------------------------------------------------------------------------------|---------------| +| eventNotifUri | Uri | M | 1 | Indicates the callback URI where the PCF sends the access and mobility changes events met. | | +| events | array(AmEventData) | O | 1..N | Indicates the one or more access and mobility related events. | | + +#### 5.6.2.5 Type: AmEventsNotification + +Table 5.6.2.5-1: Definition of type AmEventsNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|----------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| repEvents | array(AmEventNotification) | M | 1..N | The list of the reported events. | | +| appAmContextId | string | C | 0..1 | Contains the AM Policy Events Subscription resource identifier related to the event notification. It shall be included in the notification requests. It may be omitted in the resource creation/update replies. (NOTE) | | + +NOTE: The complete resource URI defined in clause 5.3.4.2 is included. + +#### 5.6.2.6 Type: AmTerminationInfo + +**Table 5.6.2.6-1: Definition of type AmTerminationInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------|---------------| +| appAmContextId | string | M | 1 | Contains the Individual application AM context resource identifier related to the termination notification. (NOTE) | | +| termCause | AmTerminationCause | M | 1 | Indicates the cause for requesting the termination of the Individual application AM context resource. | | + +NOTE: The complete resource URI defined in clause 5.3.3.2 is included. + +#### 5.6.2.7 Type AmEventsSubscDataRm + +This data type is defined as the AmEventsSubscData type, but: + +- with the OpenAPI "nullable: true" property; and +- the attributes are defined as optional. + +**Table 5.6.2.7-1: Definition of type AmEventsSubscDataRm** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------|---|-------------|--------------------------------------------------------------------------------------------|---------------| +| eventNotifUri | Uri | O | 0..1 | Indicates the callback URI where the PCF sends the access and mobility changes events met. | | +| events | array(AmEventData) | O | 1..N | Indicates the one or more access and mobility related events. | | + +#### 5.6.2.8 Type AmEventData + +Table 5.6.2.8-1: Definition of type AmEventData + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| event | AmEvent | M | 1 | Subscribed Event. | | +| immRep | boolean | O | 0..1 | Indication of immediate reporting:<br>- true: requires the immediate reporting of the current value of the subscribed event, if available.<br>- false (default): event report occurs when the event is met. | | +| notifMethod | NotificationMethod | O | 0..1 | Represents the notification method (periodic, one time, on event detection). If "notifMethod" attribute is not supplied, the default value "ON_EVENT_DETECTION" applies. | | +| maxReportNbr | UInteger | O | 0..1 | Represents the maximum number of reports, after which the subscription ceases to exist (i.e., the reporting ends). It may be present for the "PERIODIC" and on "ON_EVENT_DETECTION" notification methods. If omitted, there is no limit. | | +| monDur | DateTime | C | 0..1 | Represents the time at which the subscription ceases to exist (i.e the subscription becomes invalid and the reporting ends). If omitted, there is no time limit. If present in the subscription request, it shall be present in the subscription response. | | +| repPeriod | DurationSec | O | 0..1 | Indicates the time interval between successive event notifications. It is supplied for notification method "PERIODIC". | | + +#### 5.6.2.9 Type: AmEventNotification + +Table 5.6.2.9-1: Definition of type AmEventNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| event | AmEvent | M | 1 | Notified event. | | +| appliedCov | ServiceAreaCoverageInfo | C | 0..1 | The list of applied Tracking Areas for the serving network where the UE is camping. It shall be present when the notified event is "SAC_CH". | | +| pduidInfo | PduidInformation | C | 0..1 | Contains the PDUID and its validity timer. It shall be included when the "PDUID_CH" event is reported. | | + +#### 5.6.2.10 Type: PduidInformation + +Table 5.6.2.10-1: Definition of type PduidInformation + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|----------------------------------------------------------------------------------------|---------------| +| expiry | DateTime | M | 1 | Contains the expiration time of validity of UE policies for 5G Prose direct discovery. | | +| pduid | Pduid | M | 1 | Contains the PDUID as defined in Table 5.3.1.1 of 3GPP TS 24.555 [23]. | | + +#### 5.6.2.11 Type: ServiceAreaCoverageInfo + +Table 5.6.2.11-1: Definition of type ServiceAreaCoverageInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| tacList | array(Tac) | M | 0..N | It contains a list of the Tracking Area codes where the requested service shall be allowed. An empty array may be included within the AmEventNotification data type and indicates the service is restricted in the serving network. | | +| servingNetwork | PlmnIdNid | O | 0..1 | It contains the serving PLMN ID and, for a SNPN, the NID that together with the PLMN ID identifies the SNPN. It may be omitted when serving network is the UE H-PLMN. | | + +### 5.6.3 Simple data types and enumerations + +#### 5.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +#### 5.6.3.2 Simple data types + +The simple data types defined in table 5.6.3.2-1 shall be supported. + +Table 5.6.3.2-1: Simple data types + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| | | | | + +#### 5.6.3.3 Enumeration: AmEvent + +The enumeration "AmEvent" represents the events the PCF can notify to the NF service consumer. + +**Table 5.6.3.3-1: Enumeration AmEvent** + +| Enumeration value | Description | Applicability | +|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------| +| SAC_CH | This trigger indicates a service area coverage change for a UE. | | +| PDUID_CH | The PDUID assigned to a UE for the UE ProSe Policies has changed.<br>(NOTE) | | +| NOTE: This event can only be subscribed using the Npcf_AMPolicyAuthorization_Subscribe service operation. | | | + +#### 5.6.3.4 Enumeration: AmTerminationCause + +The enumeration "AmTerminationCause" represents the cause values that the PCF should report when requesting to the NF service consumer the deletion of the "AF application AM context" resource. It shall comply with the provisions of table 5.6.3.4-1. + +**Table 5.6.3.4-1: Enumeration AmTerminationCause** + +| Enumeration value | Description | Applicability | +|------------------------|------------------------------------------------------------------------------------------------------|---------------| +| UE_DEREGISTERED | UE initiates the deregistration procedure. | | +| UNSPECIFIED | This value is used for unspecified reasons. | | +| INSUFFICIENT_RESOURCES | Indicates that the server is overloaded and needs to release the AF application AM context resource. | | + +### 5.6.4 Data types describing alternative data types or combinations of data types + +#### 5.6.4.1 Type: AppAmContextRespData + +**Table 5.6.4.1-1: Definition of type AppAmContextRespData as a list of non-exclusive alternatives** + +| Data type | Cardinality | Description | Applicability | +|----------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------|---------------| +| AmEventsNotification | 0..1 | It represents the notification of a match event during the creation or modification of the Individual application AM context data. | | +| AppAmContextData | 1 | It represents the Individual application AM context resource. | | + +#### 5.6.4.2 Type: AmEventsSubscRespData + +**Table 5.6.4.2-1: Definition of type AmEventsSubscRespData as a list of non-exclusive alternatives** + +| Data type | Cardinality | Description | Applicability | +|----------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------|---------------| +| AmEventsSubscData | 1 | It represents the AM Policy Events subscription resource. | | +| AmEventsNotification | 0..1 | It represents the notification of a match event during the creation or modification of the AM Policy Events Subscription resource. | | + +### 5.6.5 Binary data + +#### 5.6.5.1 Binary Data Types + +None. + +## 5.7 Error Handling + +### 5.7.1 General + +HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [5]. + +For the Npcf\_AMPolicyAuthorization API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Npcf\_AMPolicyAuthorization API. + +### 5.7.2 Protocol Errors + +No specific procedures for the Npcf\_AMPolicyAuthorization service are specified. + +### 5.7.3 Application Errors + +The application errors defined for the Npcf\_AMPolicyAuthorization service are listed in Table 5.7.3-1. + +**Table 5.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|----------------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| INVALID_POLICY_REQUEST | 400 Bad Request | The HTTP request is rejected because the service information for the AM context is invalid or insufficient for the PCF to perform the requested action. (NOTE 1) | +| APPLICATION_AM_CONTEXT_NOT_FOUND | 404 Not Found | The HTTP request is rejected because the specified Individual Application AM Context does not exist. (NOTE 3) | +| POLICY_ASSOCIATION_NOT_AVAILABLE | 500 Internal Server Error | The PCF failed in executing binding with the UE/AM Policy Context. (NOTE 2) | + +NOTE 1: This application error is included in the response to the PATCH request (see clauses 4.2.3.2). +NOTE 2: This application error is included in the response to the POST request (see clauses 4.2.2.2 and 4.2.5.3). +NOTE 3: This application error is included in the responses to the GET, PATCH and DELETE requests to the Individual Application AM Context resource, and to the PUT and DELETE requests to the AM Policy Events Subscription resource. + +## 5.8 Feature negotiation + +The optional features in table 5.8-1 are defined for the Npcf\_AMPolicyAuthorization API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 5.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|-------------------|--------------------------------------------------------------------------------------------| +| 1 | NetTimeSyncStatus | This feature indicates the support of network timing synchronization status and reporting. | + +## 5.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Npcf\_AMPolicyAuthorization API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Npcf\_AMPolicyAuthorization API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Npcf\_AMPolicyAuthorization service. + +The Npcf\_AMPolicyAuthorization API defines a single scope "npcf-am-policyauthorization" for the entire service, and it does not define any additional scopes at resource or operation level. + +# Annex A (normative): OpenAPI specification + +## A.1 General + +This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format. + +This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see 3GPP TS 29.501 [5] clause 5.3.1 and 3GPP TR 21.900 [7] clause 5B). + +## A.2 Npcf\_AMPolicyAuthorization API + +``` +openapi: 3.0.0 +# +info: + title: Npcf_AMPolicyAuthorization Service API + version: 1.1.0-alpha.2 + description: | + PCF Access and Mobility Policy Authorization Service. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: > + 3GPP TS 29.534 V18.1.0; + 5G System; Access and Mobility Policy Authorization Service; Stage 3. + url: 'https://www.3gpp.org/ftp/Specs/archive/29_series/29.534/' +# +servers: + - url: '{apiRoot}/npcf-am-policyauthorization/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501 +# +security: + - {} + - oAuth2ClientCredentials: + - npcf-am-policyauthorization +# +paths: + /app-am-contexts: + post: + summary: Creates a new Individual Application AM Context resource + operationId: PostAppAmContexts + tags: + - Application AM contexts (Collection) + requestBody: + description: Contains the information for the creation the resource. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AppAmContextData' + responses: + '201': + description: Successful creation of the resource. +``` + +``` + +content: + application/json: + schema: + $ref: '#/components/schemas/AppAmContextRespData' +headers: + Location: + description: > + Contains the URI of the created individual application AM context resource, + according to the structure + {apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am-contexts/{appAmContextId} + or the URI of the created AM Policy events subscription subresource, + according to the structure + {apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am- +contexts/{appAmContextId}/events-subscription} + required: true + schema: + type: string + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +callbacks: + terminationRequest: + "{$request.body#/termNotifUri}": + post: + requestBody: + description: Request of the termination of the Individual Application AM Context. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AmTerminationInfo' +responses: + '204': + description: The receipt of the notification is acknowledged. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +amEventNotification: + '{ $request.body#/evSubsc/eventNotifUri }': + post: + requestBody: + description: Notification of an event occurrence in the PCF. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AmEventsNotification' + responses: + '204': + description: The receipt of the notification is acknowledged. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +# +/app-am-contexts/{appAmContextId}: + get: + summary: "Reads an existing Individual Application AM Context" + operationId: GetAppAmContext + tags: + - Individual Application AM Context (Document) + parameters: + - name: appAmContextId + description: String identifying the resource. + in: path + required: true + schema: + type: string + responses: + '200': + description: A representation of the resource is returned. + content: + application/json: + schema: + $ref: '#/components/schemas/AppAmContextData' + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29571_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +# +patch: + summary: "Modifies an existing Individual Application AM Context" + operationId: ModAppAmContext + tags: + - Individual Application AM Context (Document) + parameters: + - name: appAmContextId + description: String identifying the resource. + in: path + required: true + schema: + type: string + requestBody: + description: Modification of the resource. + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/AppAmContextUpdateData' + responses: + '200': + description: > + Successful modification of the resource and a representation of that resource is + returned. If a subscribed event is matched, the event notification is also included + in the response. + content: + application/json: + schema: + $ref: '#/components/schemas/AppAmContextRespData' + '204': + description: The successful modification. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + callbacks: + amEventNotification: + '{ $request.body#/evSubsc/eventNotifUri }': + post: + requestBody: + +``` + +``` + description: Notification of an event occurrence in the PCF. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AmEventsNotification' + responses: + '204': + description: The receipt of the notification is acknowledged. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +# +delete: + summary: Deletes an existing Individual Application AM Context + operationId: DeleteAppAmContext + tags: + - Individual Application AM Context (Document) + parameters: + - name: appAmContextId + description: String identifying the Individual Application AM Context resource. + in: path + required: true + schema: + type: string + responses: + '204': + description: The deletion is confirmed without returning additional data. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +# +/app-am-contexts/{appAmContextId}/events-subscription: + put: +``` + +``` +summary: creates or modifies an AM Policy Events Subscription subresource. +operationId: updateAmEventsSubsc +tags: + - AM Policy Events Subscription (Document) +parameters: + - name: appAmContextId + description: String identifying the AM Policy Events Subscription subresource. + in: path + required: true + schema: + type: string +requestBody: + description: Creation or modification of an AM Policy Events Subscription subresource. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AmEventsSubscData' +responses: + '201': + description: > + The creation of the AM Policy Events Subscription subresource is confirmed and its + representation is returned. If an AM Event is matched, the response also includes the + notification. + content: + application/json: + schema: + $ref: '#/components/schemas/AmEventsSubscRespData' + headers: + Location: + description: > + Contains the URI of the created AM Policy Events Subscription subresource, + according to the structure + {apiRoot}/npcf-am-policyauthorization/<apiVersion>/app-am- + contexts/{appAmContextId}/events-subscription} + required: true + schema: + type: string + '200': + description: > + The modification of the AM Policy Events Subscription subresource is confirmed and + its representation is returned. If an AM Event is matched, the response also includes + the notification. + content: + application/json: + schema: + $ref: '#/components/schemas/AmEventsSubscRespData' + '204': + description: > + The modification of the AM Policy Events Subscription subresource is confirmed + without returning additional data. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: +``` + +``` +$ref: 'TS29571_CommonData.yaml#/components/responses/default' +callbacks: + amEventNotification: + '{$request.body#/evSubsc/eventNotifUri}': + post: + requestBody: + description: > + Contains the information for the notification of an event occurrence in the PCF. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/AmEventsNotification' + responses: + '204': + description: The receipt of the notification is acknowledged. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +delete: + summary: deletes the AM Policy Events Subscription subresource + operationId: DeleteAmEventsSubsc + tags: + - AM Policy Events Subscription (Document) + parameters: + - name: appAmContextId + description: String identifying the Individual Application AM Context resource. + in: path + required: true + schema: + type: string + responses: + '204': + description: > + The deletion of the of the AM Policy Events Subscription subresource + is confirmed without returning additional data. + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '502': +``` + +``` + $ref: 'TS29571_CommonData.yaml#/components/responses/502' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +# +# +components: +# + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + npcF-am-policyauthorization: Access to the Npcf_AMPolicyAuthorization API +# +schemas: +# + AppAmContextData: + description: Represents an Individual Application AM Context resource. + type: object + required: + - supi + - termNotifUri + properties: + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + gpsi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + termNotifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + evSubsc: + $ref: '#/components/schemas/AmEventsSubscData' + suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + expiry: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' + highThruInd: + type: boolean + description: Indicates whether high throughput is desired for the indicated UE traffic. + covReq: + type: array + description: > + Identifies a list of Tracking Areas per serving network where service is allowed. + items: + $ref: '#/components/schemas/ServiceAreaCoverageInfo' + minItems: 1 + asTimeDisParam: + $ref: 'TS29507_Npcf_AMPolicyControl.yaml#/components/schemas/AsTimeDistributionParam' + anyOf: + - anyOf: + - required: [highThruInd] + - required: [covReq] + - required: [asTimeDisParam] + - required: [evSubsc] +# +# + AppAmContextUpdateData: + description: Describes the modifications to an Individual Application AM resource. + type: object + properties: + termNotifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + evSubsc: + $ref: '#/components/schemas/AmEventsSubscDataRm' + expiry: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' + highThruInd: + description: Indicates whether high throughput is desired for the indicated UE traffic. + type: boolean + nullable: true + covReq: + type: array + description: > + Identifies a list of Tracking Areas per serving network where service is allowed. + items: +``` + +``` + $ref: '#/components/schemas/ServiceAreaCoverageInfo' + minItems: 1 + nullable: true + asTimeDisParam: + $ref: 'TS29507_Npcf_AMPolicyControl.yaml#/components/schemas/AsTimeDistributionParam' +# +AmEventsSubscData: + description: > + It represents the AM Policy Events Subscription subresource and identifies the events + the application subscribes to. + type: object + required: + - eventNotifUri + properties: + eventNotifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + events: + type: array + items: + $ref: '#/components/schemas/AmEventData' + minItems: 1 +# +AmEventsNotification: + description: > + Describes the notification about the events occurred within an Individual Application + AM Context resource. + type: object + required: + - repEvents + properties: + appAmContextId: + type: string + description: > + Contains the AM Policy Events Subscription resource identifier related to the event + notification. + repEvents: + type: array + items: + $ref: '#/components/schemas/AmEventNotification' + minItems: 1 +# +AmTerminationInfo: + description: > + Includes information related to the termination of the Individual Application AM + Context resource. + type: object + required: + - appAmContextId + - termCause + properties: + appAmContextId: + type: string + description: > + Contains the Individual application AM context resource identifier related to + the termination notification. + termCause: + $ref: '#/components/schemas/AmTerminationCause' +# +AmEventsSubscDataRm: + description: > + This data type is defined in the same way as the AmEventsSubscData but with the OpenAPI + nullable property set to true. + type: object + properties: + eventNotifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + events: + type: array + items: + $ref: '#/components/schemas/AmEventData' + minItems: 1 + nullable: true +# +AmEventData: + description: > + This data type contains the event identifier and the related event reporting information. + type: object + required: +``` + +``` +- event +properties: + event: + $ref: '#/components/schemas/AmEvent' + immRep: + type: boolean + notifMethod: + $ref: 'TS29508_Nsmf_EventExposure.yaml#/components/schemas/NotificationMethod' + maxReportNbr: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + monDur: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + repPeriod: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' +# +AmEventNotification: + description: Describes the notification of a subscription. + type: object + required: + - event + properties: + event: + $ref: '#/components/schemas/AmEvent' + appliedCov: + $ref: '#/components/schemas/ServiceAreaCoverageInfo' + pduidInfo: + $ref: '#/components/schemas/PduidInformation' +# +PduidInformation: + description: Contains the ProSe Discovery UE ID and its validity timer. + type: object + required: + - expiry + - pduid + properties: + expiry: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + pduid: + $ref: 'TS29555_N5g-ddnmf_Discovery.yaml#/components/schemas/Pduid' +# +ServiceAreaCoverageInfo: + description: It represents a list of Tracking Areas within a serving network. + type: object + required: + - tacList + properties: + tacList: + type: array + description: Indicates a list of Tracking Areas where the service is allowed. + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Tac' + servingNetwork: + $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' +# +# ENUMERATIONS DATA TYPES +# +AmTerminationCause: + description: > + It represents the cause values that the PCF should report when requesting from an NF + service consumer the deletion of an "AF application AM context" resource. + anyOf: + - type: string + enum: + - UE_DEREGISTERED + - UNSPECIFIED + - INSUFFICIENT_RESOURCES + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration but + is not used to encode content defined in the present version of this API. +# +AmEvent: + anyOf: + - type: string + enum: + - SAC_CH + - PDUID_CH + - type: string +``` + +``` + description: > + This string provides forward-compatibility with future extensions to the enumeration but + is not used to encode content defined in the present version of this API. + description: | + Represents the PCF notification event to the NF service consumer. + Possible values are: + - SAC_CH: Service Area Coverage Change. + - PDUID_CH: The PDUID assigned to a UE for the UE ProSe Policies changed. +# +# +AppAmContextRespData: + description: It represents a response to a modification or creation request of an Individual +Application AM resource. It may contain the notification of the already met events. + anyOf: + - $ref: '#/components/schemas/AppAmContextData' + - $ref: '#/components/schemas/AmEventsNotification' +# +AmEventsSubscRespData: + description: Identifies the events the application subscribes to within an AM Policy Events +Subscription subresource data. It may contain the notification of the already met events. + anyOf: + - $ref: '#/components/schemas/AmEventsSubscData' + - $ref: '#/components/schemas/AmEventsNotification' +# +``` + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-04 | | | | | | TS skeleton | 0.0.0 | +| 2021-04 | CT3#115e | C3-212565 | | | | Inclusion of documents agreed in CT3#115e:<br>C3-212111, C3-212411, C3-212515, C3-212516, C3-212517, C3-212303, C3-212412, C3-212306, C3-212518, C3-212308, C3-212413, C3-212555, C3-212556, C3-212557, C3-212558, C3-212559, C3-212560, C3-212561, C3-212562. | 0.1.0 | +| 2021-06 | CT3#116e | C3-213498 | | | | Inclusion of documents agreed in CT3#116e:<br>C3-213358. | 0.2.0 | +| 2021-09 | CT3#117e | C3-214574 | | | | Inclusion of documents agreed in CT3#117e:<br>C3-214427, C3-214428, C3-214429, C3-214431, C3-214618, C3-214430, C3-214134, C3-214305, C3-214493, C3-214494, C3-214495, C3-214496 | 0.3.0 | +| 2021-10 | CT3#118e | C3-215472 | | | | Inclusion of documents agreed in CT3#118e:<br>C3-215306, C3-215396 | 0.4.0 | +| 2021-12 | CT3#119e | C3-216516 | | | | Inclusion of documents agreed in CT3#119e:<br>C3-216187, C3-216404, C3-216405, C3-216380, C3-216206, C3-216406, C3-216409, C3-216407 | 0.5.0 | +| 2021-12 | CT#94e | CP-213253 | | | | Presentation for information | 1.0.0 | +| 2022-01 | CT3#119bis-e | C3-220448 | | | | Inclusion of documents agreed in CT3#119bis-e:<br>C3-220230, C3-220247, C3-220395, C3-220469, C3-220448 | 1.1.0 | +| 2022-02 | CT3#120e | C3-221511 | | | | Inclusion of documents agreed in CT3#120e:<br>C3-221704, C3-221479 | 1.2.0 | +| 2022-03 | CT#95e | CP-220155 | | | | Presentation to TSG CT for approval | 2.0.0 | +| 2022-03 | CT#95e | CP-220155 | | | | Approved by TSG CT | 17.0.0 | +| 2022-06 | CT#96 | CP-221159 | 0002 | | F | Correction to required properties in the OpenAPI file | 17.1.0 | +| 2022-06 | CT#96 | CP-221159 | 0003 | | F | Data type in PATCH request body | 17.1.0 | +| 2022-06 | CT#96 | CP-221144 | 0004 | 1 | B | Support of AS Time Distribution, general clauses | 17.1.0 | +| 2022-06 | CT#96 | CP-221144 | 0005 | 1 | B | Support of AS Time Distribution, service procedures | 17.1.0 | +| 2022-06 | CT#96 | CP-221095 | 0006 | 1 | F | Alignment with the SBI template | 17.1.0 | +| 2022-06 | CT#96 | CP-221151 | 0007 | | F | Update of info and externalDocs fields | 17.1.0 | +| 2022-09 | CT#97e | CP-222127 | 0008 | | F | Correction to notification about AF application AM context event | 17.2.0 | +| 2022-09 | CT#97e | CP-222127 | 0009 | 1 | F | Correction to notification about AF application AM context termination | 17.2.0 | +| 2022-09 | CT#97e | CP-222127 | 0010 | 1 | F | Correction of wrong interface name | 17.2.0 | +| 2022-09 | CT#97e | CP-222127 | 0011 | 1 | F | Missing description field for enumeration data types | 17.2.0 | +| 2022-09 | CT#97e | CP-222121 | 0012 | | F | Update of info and externalDocs fields | 17.2.0 | +| 2022-12 | CT#98e | CP-223197 | 0015 | 1 | F | Corrections of presence conditions for the case of plain event subscriptions | 17.3.0 | +| 2022-12 | CT#98e | CP-223197 | 0017 | 1 | F | Corrections for Npcf_AMPolicyAuthorization service | 17.3.0 | +| 2022-12 | CT#98e | CP-223188 | 0020 | | F | Update of info and externalDocs fields | 17.3.0 | +| 2022-12 | CT#98e | CP-223191 | 0013 | | F | Adding the mandatory error code 502 Bad Gateway | 18.0.0 | +| 2022-12 | CT#98e | CP-223198 | 0016 | | F | Adding the N30 reference poin | 18.0.0 | +| 2022-12 | CT#98e | CP-223189 | 0018 | | F | Update of info and externalDocs fields | 18.0.0 | +| 2023-03 | CT#99 | CP-230166 | 021 | | F | Correction of the description fields in enumerations | 18.1.0 | +| 2023-03 | CT#99 | CP-230174 | 022 | | F | Correction of service operation name | 18.1.0 | +| 2023-03 | CT#99 | CP-230161 | 024 | | F | Update of info and externalDocs fields | 18.1.0 | +| 2023-06 | CT#100 | CP-231143 | 0025 | 3 | B | Support for network timing synchronization status and reporting | 18.2.0 | +| 2023-06 | CT#100 | CP-231131 | 0026 | | F | Corrections to the redirection mechanism description | 18.2.0 | +| 2023-12 | CT#102 | CP-233229 | 0028 | 1 | F | Reference update: IETF RFC 9113 | 18.3.0 | +| 2023-12 | CT#102 | CP-233228 | 0029 | | F | ProblemDetails RFC 7807 obsoleted by RFC 9457 | 18.3.0 | \ No newline at end of file diff --git a/raw/rel-18/29_series/29535/1ce753126302304d15aa14ed37e8ac15_img.jpg b/raw/rel-18/29_series/29535/1ce753126302304d15aa14ed37e8ac15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8d7a5fc436221c00a3c2ef4164b9246addb7fca --- /dev/null +++ b/raw/rel-18/29_series/29535/1ce753126302304d15aa14ed37e8ac15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fdcccfdec6bcbcdc7269a534c469a8162d0d8f646c36e1e88cb39e4a50a95be +size 27518 diff --git a/raw/rel-18/29_series/29535/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/29_series/29535/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..052a2b7effd9846d2b40c579fca0c69b5ca9ff45 --- /dev/null +++ b/raw/rel-18/29_series/29535/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13204274f692d23a46b613a3e6e191a0f293550498977234cecb22c4d92f26ba +size 29642 diff --git a/raw/rel-18/29_series/29535/410562339ce067fdc6fa41940c118658_img.jpg b/raw/rel-18/29_series/29535/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5011299d37484c441e872c4036d98e11b90f9fdd --- /dev/null +++ b/raw/rel-18/29_series/29535/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:877fbb97cf03815447509cd4bf849f65e98a0aaeed51f50ca29d26a5f59668cc +size 32137 diff --git a/raw/rel-18/29_series/29535/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29535/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f64ae305b56ddf01d0993fdc45c761b5fe0a204 --- /dev/null +++ b/raw/rel-18/29_series/29535/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b337c0dcba4aa2c230f1bbf8e9957cb6da70e83695dd5e4d230906c10ede784 +size 9505 diff --git a/raw/rel-18/29_series/29535/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29535/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..163aadbc13e275a7b52c18e9b2646ea1d0d7e042 --- /dev/null +++ b/raw/rel-18/29_series/29535/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a0c32c9684a613befae0cb6ef99b849f24bbdca698743b66c19a1e8b4ebe2b4 +size 5657 diff --git a/raw/rel-18/29_series/29535/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/raw/rel-18/29_series/29535/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ebf4160c339b9d8c2495ae5c0c47085922f0ead --- /dev/null +++ b/raw/rel-18/29_series/29535/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71c964555bb45440589ff501adcd054bef08f48cd5e544552ba5dd0d08262ed9 +size 31173 diff --git a/raw/rel-18/29_series/29535/a92b1fdf37a74b707e9f03087c8f1377_img.jpg b/raw/rel-18/29_series/29535/a92b1fdf37a74b707e9f03087c8f1377_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b953cbdee7dbfca7780fbb2ca3539b38ce4240bd --- /dev/null +++ b/raw/rel-18/29_series/29535/a92b1fdf37a74b707e9f03087c8f1377_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5424963c718139bc54be3dbfddabb579a1a2cae213935d11cf901cc5ed079c5a +size 18044 diff --git a/raw/rel-18/29_series/29535/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/29_series/29535/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51b0233e10c97feea8a508a2bae6e16bc7731a4d --- /dev/null +++ b/raw/rel-18/29_series/29535/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8260da6d5eac37c547aa1fe6d25453d36f69f7a1fdaed482da6f98a856e9c4c8 +size 17252 diff --git a/raw/rel-18/29_series/29542/06da11ab76cacc38bbcd714e437797ea_img.jpg b/raw/rel-18/29_series/29542/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..565c455fc3376aba00440c2513ea469e677b0a08 --- /dev/null +++ b/raw/rel-18/29_series/29542/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d8f92548a094e971ac995b0e549059985affcfaf237d7b979c2923e63d66a20 +size 7255 diff --git a/raw/rel-18/29_series/29542/562f471e8153729557e6a4ee6343c32c_img.jpg b/raw/rel-18/29_series/29542/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c71477c2282b3c8eba0aaaf2f79b202fe2b54715 --- /dev/null +++ b/raw/rel-18/29_series/29542/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c13b2e9429c61bcaec95c13ac67ea511ee227d843b74ca57c6f7d57206c1805 +size 37440 diff --git a/raw/rel-18/29_series/29542/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29542/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d8da8decc418c0cbf3d933846fde6ea5a45ce36 --- /dev/null +++ b/raw/rel-18/29_series/29542/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5108e98c70574cefe057960463836f7f285ee626dcd4f13cb0419eaca2a234be +size 9689 diff --git a/raw/rel-18/29_series/29542/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29542/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16e9aae63150f49556e71ac272e7764e1b1a910c --- /dev/null +++ b/raw/rel-18/29_series/29542/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:068a3c982ec053b54abb9d30d010da1c41ea30b19ed1d417e1e371feb6f6181e +size 5746 diff --git a/raw/rel-18/29_series/29542/e9314c83043183351ed74908e9bf2f90_img.jpg b/raw/rel-18/29_series/29542/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bd56628e0cfd4f4523ac8afef517de3fa4ce186 --- /dev/null +++ b/raw/rel-18/29_series/29542/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65f92b748ae8f94d84832c2aa3e5a88c9f53489338c11410e0b601c07738ada3 +size 12517 diff --git a/raw/rel-18/29_series/29544/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29544/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca4ff28268e59941494dac09eb1e4c046f01c0b --- /dev/null +++ b/raw/rel-18/29_series/29544/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c748d83cec2e58ed80507256b448c31cd2c5c833fb9f059b88d980312939c598 +size 9606 diff --git a/raw/rel-18/29_series/29544/6078636a87fbe0e699aab4a6fddd15d7_img.jpg b/raw/rel-18/29_series/29544/6078636a87fbe0e699aab4a6fddd15d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f622e1b921197c578f3aa1f1dd241fcb2a1cfdfb --- /dev/null +++ b/raw/rel-18/29_series/29544/6078636a87fbe0e699aab4a6fddd15d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:399b230e70ad3899f6a5fed43e946ec7062dcc018358187c4cd78236c8b21201 +size 12391 diff --git a/raw/rel-18/29_series/29544/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29544/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7377f549b5c8e084e6d38bcea5d5b198b121233 --- /dev/null +++ b/raw/rel-18/29_series/29544/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:050f49e05df79ea3a955ee6f0bab7849fde1950466aaaf4ed74b81d36f1ad0d6 +size 5724 diff --git a/raw/rel-18/29_series/29544/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/raw/rel-18/29_series/29544/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5c8a133c6081e893d9b6f89ce1f23a7ec506a8f --- /dev/null +++ b/raw/rel-18/29_series/29544/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1efa6bcb1e5e04b1d0761a36918fd714fbf1a6696ced5cde22769c4c389232ef +size 16582 diff --git a/raw/rel-18/29_series/29544/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/29_series/29544/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9d8c18c36c92d3adf047ed30940f51b763dd4eb --- /dev/null +++ b/raw/rel-18/29_series/29544/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c8277d4757e338d39cfb55efb26ef3025904bcd159f8975f8bb44330286185e +size 31966 diff --git a/raw/rel-18/29_series/29550/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg b/raw/rel-18/29_series/29550/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45fdeb10442669e6b1ac7b47d41d79e8725c5ead --- /dev/null +++ b/raw/rel-18/29_series/29550/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4e18194ff7aa92f9db58d65f70ea59e41240e0283c1b5fb4f6967737abb69e6 +size 29861 diff --git a/raw/rel-18/29_series/29550/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29550/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..149e523b221fc5fc468e2f8de6cb5237392be8d3 --- /dev/null +++ b/raw/rel-18/29_series/29550/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:725d95d168abde136f59cd2ee2469e441213ad17a05c6d8fc8c00a91cb1ec94b +size 9514 diff --git a/raw/rel-18/29_series/29550/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29550/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8100a15c900e98697870ba4c1afddbe7c9b3ee68 --- /dev/null +++ b/raw/rel-18/29_series/29550/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb40bc9f76c66728d07c34b52e7e2c983ae7e9e2ffb632d60220ebfd237c17a3 +size 5694 diff --git a/raw/rel-18/29_series/29550/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/raw/rel-18/29_series/29550/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60cc95031f286ecd191164ebaa67f7a64c1fc916 --- /dev/null +++ b/raw/rel-18/29_series/29550/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61d07f1144c4a8c8280e05a63ebc88d250a4e05ff59ce806a252f609c7fd8e18 +size 32527 diff --git a/raw/rel-18/29_series/29550/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg b/raw/rel-18/29_series/29550/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e739e70fe4693609ad37aea500db25ae08c60fa6 --- /dev/null +++ b/raw/rel-18/29_series/29550/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1007633b4b23460492cd491c3f4f1a7933d9d73ceaf65e070d6311f2a542fd1b +size 31003 diff --git a/raw/rel-18/29_series/29550/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/raw/rel-18/29_series/29550/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f14916e55ed0f44d0789b73291968889e782d4b --- /dev/null +++ b/raw/rel-18/29_series/29550/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b87ce7affba75ac8c44b2204eb897b51ac0e2a799c331abafc71606e0745253f +size 9892 diff --git a/raw/rel-18/29_series/29551/18722c46c9e8475524e634dedd08bac2_img.jpg b/raw/rel-18/29_series/29551/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00602d27548e76b02984f35092cffd76c45ddfe6 --- /dev/null +++ b/raw/rel-18/29_series/29551/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17a26bd5bc37dc79d7b89f6cc67c3495100ad81eeb65c073210db44e2b18b3f +size 24832 diff --git a/raw/rel-18/29_series/29551/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/29_series/29551/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69790e93e8b4b50669108be48d597aab60f86eff --- /dev/null +++ b/raw/rel-18/29_series/29551/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee554048d6e48c2ba4c576f96cf3d888ae00e3334e2955e394cd1a90074bf802 +size 23280 diff --git a/raw/rel-18/29_series/29551/2a0f333f04f8e672bebf288c511c1db5_img.jpg b/raw/rel-18/29_series/29551/2a0f333f04f8e672bebf288c511c1db5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb1f604e983fc064d27e67c6f68ddfebd318792f --- /dev/null +++ b/raw/rel-18/29_series/29551/2a0f333f04f8e672bebf288c511c1db5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3c3112e81aaa75b4e81d172fa44b0d395fc9a094e0d27484bfe2dadb222377f +size 23740 diff --git a/raw/rel-18/29_series/29551/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/raw/rel-18/29_series/29551/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f187c3d8b76d83a473257dac164e6cad01acd5bd --- /dev/null +++ b/raw/rel-18/29_series/29551/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aea10672eb92369213f33383e2701fe249f94710bf24a0d3986684db29cad884 +size 34958 diff --git a/raw/rel-18/29_series/29551/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg b/raw/rel-18/29_series/29551/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..795c33421f5a54b96bdad17145c13ebb59aad89d --- /dev/null +++ b/raw/rel-18/29_series/29551/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db196c7e4e3c689c485630c30c84bc101c48da0137fbb8c78c792b896de7ef97 +size 13736 diff --git a/raw/rel-18/29_series/29551/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/raw/rel-18/29_series/29551/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daf433dcad19809f6f25a943ca2346cf2f0cf6a7 --- /dev/null +++ b/raw/rel-18/29_series/29551/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f8bd2f790092e1ab4096cd815067b9ec4673cd1d02822558610f2af446af9b8 +size 24797 diff --git a/raw/rel-18/29_series/29551/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29551/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de --- /dev/null +++ b/raw/rel-18/29_series/29551/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7 +size 9370 diff --git a/raw/rel-18/29_series/29551/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29551/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfa0d229082ecb7f2e23102ee7673d2a2cf03c76 --- /dev/null +++ b/raw/rel-18/29_series/29551/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb776af0de14b4c8128e6942a0e4c9865e7e854af32e2934cb82ad5032d68eb +size 5342 diff --git a/raw/rel-18/29_series/29551/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/raw/rel-18/29_series/29551/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4973b4fdaf699ee4e23a3cdeb10fed64a6b70896 --- /dev/null +++ b/raw/rel-18/29_series/29551/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35dc9b835be5ad57323f5df636e7196e4e801ae75158454d16baebecf072c14d +size 23579 diff --git a/raw/rel-18/29_series/29551/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg b/raw/rel-18/29_series/29551/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7244bf8dfd45ee64b139c5b0b8860ea21553174 --- /dev/null +++ b/raw/rel-18/29_series/29551/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71ba65d7a35065b5adb018aa50dea51b5f3e74f26710da3646a344c54903f97d +size 11591 diff --git a/raw/rel-18/29_series/29551/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg b/raw/rel-18/29_series/29551/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a6d25dd8c1e9e47d1a81c3c28896bcd4f6f6f2d --- /dev/null +++ b/raw/rel-18/29_series/29551/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cca896b23eedf6634f30ac40f474ec7a907a970540d163b2793c9bb95782385 +size 25691 diff --git a/raw/rel-18/29_series/29551/f6e8acf9f931452d01688d311b5c0364_img.jpg b/raw/rel-18/29_series/29551/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39735f07dce347100ff30a29a8e5529cfeb53213 --- /dev/null +++ b/raw/rel-18/29_series/29551/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4a2e1de5ff489ba2555bd75eb6ae95aa442eee89254dcef230e142a97015d2a +size 22359 diff --git a/raw/rel-18/29_series/29556/08441fa90c5fd11994626f662ac13f19_img.jpg b/raw/rel-18/29_series/29556/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d8538f24e1e0f8e454fda97fc45ed31f84397c3 --- /dev/null +++ b/raw/rel-18/29_series/29556/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:760934cc25d273eaee6c22fe1d4b0851174dfb40e2c89d1dd27fd049f6cd4dea +size 37393 diff --git a/raw/rel-18/29_series/29556/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/raw/rel-18/29_series/29556/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70729a9e1b86c7dbcdc125d413792b5cbd247060 --- /dev/null +++ b/raw/rel-18/29_series/29556/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:904513f6c81faa22cf6e71356ee0c47185a464beae1d04fb7ebedca4a8ad0488 +size 14129 diff --git a/raw/rel-18/29_series/29556/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/raw/rel-18/29_series/29556/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff200dfe9854906c67c0943bd58cc3598f441f2 --- /dev/null +++ b/raw/rel-18/29_series/29556/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3303655ca4c22bc8e9ec1156c35b3608d80546395bd580aa3d1af942000de4bd +size 19664 diff --git a/raw/rel-18/29_series/29556/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/raw/rel-18/29_series/29556/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ac2e2a9f0f1a7b635dc34e0dae1204b9758da14 --- /dev/null +++ b/raw/rel-18/29_series/29556/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0927e21f8f760d5d39a53652d89c4eb69cf227eb62255ef80cd5b533ca766e03 +size 35344 diff --git a/raw/rel-18/29_series/29556/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/raw/rel-18/29_series/29556/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779787b0df75d651c11dfae5e714d71079ccc770 --- /dev/null +++ b/raw/rel-18/29_series/29556/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e78e966a114d6ae4b333c3e0361273ba0f27f112dbb739c9ca87146efb9ed511 +size 35000 diff --git a/raw/rel-18/29_series/29556/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29556/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..421b04ae6f80c38b49d2e10345751c92c2590b77 --- /dev/null +++ b/raw/rel-18/29_series/29556/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d776d8b5eefaade8e7782337746f06edb22d3c216455f6e6db8300ab78b8645 +size 9657 diff --git a/raw/rel-18/29_series/29556/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29556/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..437793674e6c15e0b035b5f88d1184f85af1d21b --- /dev/null +++ b/raw/rel-18/29_series/29556/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56da42677988c23f9143400b9d5ba6eb8291bbd260baf4ae16be4b16e6a9edf0 +size 5671 diff --git a/raw/rel-18/29_series/29556/6efcea66501271e9ea36cf33982f08d5_img.jpg b/raw/rel-18/29_series/29556/6efcea66501271e9ea36cf33982f08d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8400bb5e61515accdbcce12f715ceb2fd88e3dce --- /dev/null +++ b/raw/rel-18/29_series/29556/6efcea66501271e9ea36cf33982f08d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7b8bf78f9433a167d94dfc6dce65eb0e96bdfef0c6c8bd0a29d86a3e0e78932 +size 31667 diff --git a/raw/rel-18/29_series/29556/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29556/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc4d14c07b9854ac8a205aa72c42c846f82ae44 --- /dev/null +++ b/raw/rel-18/29_series/29556/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e903bde9b1c751a9fd6e9f958d49c099afa1082dec0069380a1fe939803f5bce +size 36117 diff --git a/raw/rel-18/29_series/29556/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/29_series/29556/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9e5141a9dc02b6a341e6028cec1b7f758b6e786 --- /dev/null +++ b/raw/rel-18/29_series/29556/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6065c59c991019116269cfa36e86f754363ed870ffe3037ab63727624fb56d71 +size 98191 diff --git a/raw/rel-18/29_series/29556/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/29_series/29556/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b42a032661da7c235d82a6ff7f824bd8bee5eb1 --- /dev/null +++ b/raw/rel-18/29_series/29556/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e50fbc5653cf8ead1222781cbcc29635ded2275686a6774a197eb88669ee145 +size 43080 diff --git a/raw/rel-18/29_series/29556/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/raw/rel-18/29_series/29556/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3725b495cc91c688e41f988540f6d7796cfabd17 --- /dev/null +++ b/raw/rel-18/29_series/29556/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b670840b9fb8034cc8f3d8cf7be3b080dcab1c51769118b83d6696a4fef73ec +size 33259 diff --git a/raw/rel-18/29_series/29556/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/raw/rel-18/29_series/29556/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..068ca3968c88a86e00d007c11a5f69b4752cb2bd --- /dev/null +++ b/raw/rel-18/29_series/29556/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1202f9ff5c7854768fc6159a0ff66e46e5a20453b301ca3bd0250af6e1d817c5 +size 36226 diff --git a/raw/rel-18/29_series/29556/df1d0e45191302de72176e4390224c16_img.jpg b/raw/rel-18/29_series/29556/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5612577a7a8e63badbbab06c174926b4022e154e --- /dev/null +++ b/raw/rel-18/29_series/29556/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c1fc27a10ccf7f0e46726b987771b7d8e44eae1fe3bc33be23741e5e2942d88 +size 38706 diff --git a/raw/rel-18/29_series/29556/e58a867750e4ae01604318506b79df7a_img.jpg b/raw/rel-18/29_series/29556/e58a867750e4ae01604318506b79df7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79892ca142b41f49d6dccfaa774499d450eeb8d0 --- /dev/null +++ b/raw/rel-18/29_series/29556/e58a867750e4ae01604318506b79df7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:062b9ad2d554d02c02b57d01c6340f73c82271145f676d1959573d9124030af3 +size 38296 diff --git a/raw/rel-18/29_series/29556/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/raw/rel-18/29_series/29556/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..866691ef72745ffbc695728c0818545e4415fb75 --- /dev/null +++ b/raw/rel-18/29_series/29556/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70958f455a58c9686a94389ac644845c78f5cd68a2cc22a1ae3ec63dc75fff44 +size 34852 diff --git a/raw/rel-18/29_series/29556/ef7a88e04d1939ee09bafd5c3072adf8_img.jpg b/raw/rel-18/29_series/29556/ef7a88e04d1939ee09bafd5c3072adf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d18d536818cc2043e811061ab3afa7139acd9f66 --- /dev/null +++ b/raw/rel-18/29_series/29556/ef7a88e04d1939ee09bafd5c3072adf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdb6bf36caa3f4b81b67c142bbf8fa72aa975c78322d14df60ad0c887d29be26 +size 7713 diff --git a/raw/rel-18/29_series/29557/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/29_series/29557/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e27840db4f95110088d70da579dae1bcc7b8d136 --- /dev/null +++ b/raw/rel-18/29_series/29557/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:818bc6f193e2b6b67972cadbd854d6bc7b61d84686cdd929801fb8fccd98e1dc +size 30918 diff --git a/raw/rel-18/29_series/29557/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/raw/rel-18/29_series/29557/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e68c717c1c02c6677813b68799d8eb592915543 --- /dev/null +++ b/raw/rel-18/29_series/29557/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fbfc5d499a6d4f799641e20cb60c96aac022d8f631d09a56b177fbab4439383 +size 31397 diff --git a/raw/rel-18/29_series/29557/51db757d054ce1ce83c436a3578b56ca_img.jpg b/raw/rel-18/29_series/29557/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28f04bc4935d895b0ce1efaf5191dc9c386f5908 --- /dev/null +++ b/raw/rel-18/29_series/29557/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2899a39c0b10204d966c01825057e4184965b8ac9aca588bda0664b56b8d1c27 +size 27038 diff --git a/raw/rel-18/29_series/29557/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29557/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..753252fc34975c48733894a1b1fcc87fd29e6217 --- /dev/null +++ b/raw/rel-18/29_series/29557/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb1bd20efe6cfb7fe7d7e67a0c3da51da2c187aabbd25a897d785446d6139d68 +size 9466 diff --git a/raw/rel-18/29_series/29557/6078636a87fbe0e699aab4a6fddd15d7_img.jpg b/raw/rel-18/29_series/29557/6078636a87fbe0e699aab4a6fddd15d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b38f9bf136c9de7e5924d2599eaefde5bbf1ad --- /dev/null +++ b/raw/rel-18/29_series/29557/6078636a87fbe0e699aab4a6fddd15d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbb7a4325ebdb181f720ec52cec6d4b4b85f7cdd54ff1d1b5bf2738ed92652ac +size 20027 diff --git a/raw/rel-18/29_series/29557/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29557/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..605fd4a1304b71b32adfa277634c61359389b1ef --- /dev/null +++ b/raw/rel-18/29_series/29557/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8e9ddf3be3ae0f0aabe6cbd546dc8e64f791bafcd1fcc3a8ea27aa3827f9ff2 +size 5655 diff --git a/raw/rel-18/29_series/29557/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/raw/rel-18/29_series/29557/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a273feb0a2f93f15e4a9cc214199c451fe230d5d --- /dev/null +++ b/raw/rel-18/29_series/29557/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a7b008a656836321108f7f3cdcd5e29c0f13ee8dc236969e89c281c77d4206d +size 13311 diff --git a/raw/rel-18/29_series/29557/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/raw/rel-18/29_series/29557/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30c4e632a7868534b8afb1ac71de61f5535c6038 --- /dev/null +++ b/raw/rel-18/29_series/29557/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bdd9aedc1db085b54986bdf57cc3c3662227734ec4115e1922aa5020859df5d +size 32786 diff --git a/raw/rel-18/29_series/29558/0bad255f79e25d544189cfab0e84bf3a_img.jpg b/raw/rel-18/29_series/29558/0bad255f79e25d544189cfab0e84bf3a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b18e198fdeea390a0e628f7e6078197156e8c9b --- /dev/null +++ b/raw/rel-18/29_series/29558/0bad255f79e25d544189cfab0e84bf3a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f689b27637930fcf755d74e51c94443ed8fd40c44e1a15771269bea0a22fb3d9 +size 19806 diff --git a/raw/rel-18/29_series/29558/1750e325061d2206b5af0af175793d79_img.jpg b/raw/rel-18/29_series/29558/1750e325061d2206b5af0af175793d79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e41da85528b72c059aebdd65b1db7bb7ac0c58f1 --- /dev/null +++ b/raw/rel-18/29_series/29558/1750e325061d2206b5af0af175793d79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c1f2fb22784186f41f6b9c4c29c86b6928e4dd20f995cba27f31e32c79701de +size 21560 diff --git a/raw/rel-18/29_series/29558/1b2ce053624064d94a4143854da46702_img.jpg b/raw/rel-18/29_series/29558/1b2ce053624064d94a4143854da46702_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f31899bfa3c3df87b2c6532efcfa4927142b5347 --- /dev/null +++ b/raw/rel-18/29_series/29558/1b2ce053624064d94a4143854da46702_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8b586a4cee52cac2b51fe0ccab03381247e71723a182badb89c761a4c88c545 +size 20946 diff --git a/raw/rel-18/29_series/29558/1c051a3d61003bc7d513e03015245317_img.jpg b/raw/rel-18/29_series/29558/1c051a3d61003bc7d513e03015245317_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..398d9164ec5fa72b093e2e3568192e10a5d9e7f4 --- /dev/null +++ b/raw/rel-18/29_series/29558/1c051a3d61003bc7d513e03015245317_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b8db69dff58b19df872d8ab52e0691f7967ea89fd42d15ff2e4e496790fae2c +size 18464 diff --git a/raw/rel-18/29_series/29558/33a69b428f4353e782c54a7aaa4eb260_img.jpg b/raw/rel-18/29_series/29558/33a69b428f4353e782c54a7aaa4eb260_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99266073d8036e286fee0d99ae4854e148167fd4 --- /dev/null +++ b/raw/rel-18/29_series/29558/33a69b428f4353e782c54a7aaa4eb260_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8eebde84c08f0d4689e6340f96345001d5bd9f23dc41f5f06801a2f9675f063c +size 15404 diff --git a/raw/rel-18/29_series/29558/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29558/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af8ae300fdca530519de4c1b5dfd19e8c3f7cf10 --- /dev/null +++ b/raw/rel-18/29_series/29558/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6e0025ed4a872e54677c8559c27c5ff4b186736bb2689f0cef7944f611798ce +size 9477 diff --git a/raw/rel-18/29_series/29558/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29558/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6188a099ee93a42a13c5e25403ae5e9685bab99f --- /dev/null +++ b/raw/rel-18/29_series/29558/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af4b5e5330c2f773409c27f613b5e452e33e2d1a026da4915e372c1182eaf95e +size 5480 diff --git a/raw/rel-18/29_series/29558/92171b3c1fa1c46db587486e1a4a260f_img.jpg b/raw/rel-18/29_series/29558/92171b3c1fa1c46db587486e1a4a260f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e73bf4d83297b2a4fc60c646f76f6c003c0ec9e6 --- /dev/null +++ b/raw/rel-18/29_series/29558/92171b3c1fa1c46db587486e1a4a260f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0867fff40107d1d1ec09cda3ab16494383f9bd30ad3ad2958ff5e9444b1fd8f9 +size 11336 diff --git a/raw/rel-18/29_series/29558/ad555483986d7170a46ce72d164b5bc8_img.jpg b/raw/rel-18/29_series/29558/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..936eb6d4d08c3c7ac5e2922b12e376764b9a48f8 --- /dev/null +++ b/raw/rel-18/29_series/29558/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:709772963155176068ef496116986d5ac01b9a0a243440f455d6cff1f2051ea6 +size 23191 diff --git a/raw/rel-18/29_series/29558/b882c54d92390b4ca523f230e3e07617_img.jpg b/raw/rel-18/29_series/29558/b882c54d92390b4ca523f230e3e07617_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7bfe619d60c4302dc08c67b1523f2ca04694574 --- /dev/null +++ b/raw/rel-18/29_series/29558/b882c54d92390b4ca523f230e3e07617_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ac6b05d1f52d14a0d6c6b7900ef89262e4452bc823fa3bbc938c52c587f2763 +size 21063 diff --git a/raw/rel-18/29_series/29558/d2417b04116c354deccb25d98a84a0fb_img.jpg b/raw/rel-18/29_series/29558/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e57d9c38a08d5f9a57b56454327e04b44312c1ae --- /dev/null +++ b/raw/rel-18/29_series/29558/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c2eef3555f457450f814fbbcac9d546604c33f6618db28b01a1927d0c3e4b9b +size 19006 diff --git a/raw/rel-18/29_series/29558/d6f4ba0e72f3631816d733b5cff14c3f_img.jpg b/raw/rel-18/29_series/29558/d6f4ba0e72f3631816d733b5cff14c3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a96f4f95b53ed6ebe6d09a44a18542e618459aeb --- /dev/null +++ b/raw/rel-18/29_series/29558/d6f4ba0e72f3631816d733b5cff14c3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b191dd34747afa6c2bb1f356f99f173c919bf8da1adbbe4e10aa77806c37e92 +size 23087 diff --git a/raw/rel-18/29_series/29558/d884367c84ba50f250499f79c4b4b950_img.jpg b/raw/rel-18/29_series/29558/d884367c84ba50f250499f79c4b4b950_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ef5c9c15e875236d1fa6cca34efafc13d678514 --- /dev/null +++ b/raw/rel-18/29_series/29558/d884367c84ba50f250499f79c4b4b950_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f67e972b14d90123f1a0345e2a201a63e828969fc43f113390ab92cae40112d5 +size 18488 diff --git a/raw/rel-18/29_series/29558/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/raw/rel-18/29_series/29558/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd4c1d42738371e6f848d9436a3f69b563281ee0 --- /dev/null +++ b/raw/rel-18/29_series/29558/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed41d37d4361c91ad89c1a2ec5147156b6eeb97c48b00b5a07691c0ed795ac3e +size 13824 diff --git a/raw/rel-18/29_series/29558/dfd09f348b50c9255f3cfe67985db9bc_img.jpg b/raw/rel-18/29_series/29558/dfd09f348b50c9255f3cfe67985db9bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f115e5fc97ec82d55683b497ce8a83d08ae639b --- /dev/null +++ b/raw/rel-18/29_series/29558/dfd09f348b50c9255f3cfe67985db9bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0834a25a2b1585e0722ad2f62c538a93ceb2777d30557b57feb46d879f8c9a3a +size 18245 diff --git a/raw/rel-18/29_series/29558/ede4f38e16d526d5b1af095b73d72713_img.jpg b/raw/rel-18/29_series/29558/ede4f38e16d526d5b1af095b73d72713_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62e47fc6b02dab21a73af2a9bf6cfc60dfc5b0f9 --- /dev/null +++ b/raw/rel-18/29_series/29558/ede4f38e16d526d5b1af095b73d72713_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:324bd29557f4c61b9adeb50391802841404ab58bc425aefc20bf971a137bbdae +size 22371 diff --git a/raw/rel-18/29_series/29558/f19a4dced8649e66cfd4d71fff6463d4_img.jpg b/raw/rel-18/29_series/29558/f19a4dced8649e66cfd4d71fff6463d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..295f1d73fa9710e2c816ceb5864f453c1405c3fb --- /dev/null +++ b/raw/rel-18/29_series/29558/f19a4dced8649e66cfd4d71fff6463d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e689ce5e333c1c660a1d6105e0c66f5c2fd18771645214b7e5506ca7d734f3c +size 15751 diff --git a/raw/rel-18/29_series/29558/fadb105fd6214a1deb66e4d35b94f3e3_img.jpg b/raw/rel-18/29_series/29558/fadb105fd6214a1deb66e4d35b94f3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..164226efcdcc7c8ccd53c1fe01e4bcf575b3be20 --- /dev/null +++ b/raw/rel-18/29_series/29558/fadb105fd6214a1deb66e4d35b94f3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dba51759e28d7cf19a85564e89bf088b875f46c6ab4c1cacb456f34ede71bc0 +size 16803 diff --git a/raw/rel-18/29_series/29559/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg b/raw/rel-18/29_series/29559/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c5c745ff6c46f8f660b9c50c16ab5f5bb859fea --- /dev/null +++ b/raw/rel-18/29_series/29559/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2154478f7bc8d1199c6a580d00f5517033e3ff80b3e6854a42a1d77fd8c6f145 +size 11820 diff --git a/raw/rel-18/29_series/29559/2e399449b7f62d40167a65ca88888917_img.jpg b/raw/rel-18/29_series/29559/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..459767dd8d2059bd99c78c5917d9d8e9b25e5e1e --- /dev/null +++ b/raw/rel-18/29_series/29559/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3f5515be0fdbf1b0d0fb14f4689f5bca5e76109cdb8bc6b34a5bccdfe069390 +size 40589 diff --git a/raw/rel-18/29_series/29559/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29559/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e028e376a2971d06c4aa4f7bafc7d643c6cd4cdd --- /dev/null +++ b/raw/rel-18/29_series/29559/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:419ffcadfa3a9d3567c211f3019fc47713f6fac70d7aac1f498b2bc09203bb81 +size 7600 diff --git a/raw/rel-18/29_series/29559/63e0c22852c26699d0bd095a2d796bab_img.jpg b/raw/rel-18/29_series/29559/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae0f0da35604865d8eff70af088c1d7ab0b52912 --- /dev/null +++ b/raw/rel-18/29_series/29559/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f11ef36f417f80c173f2f61cf00ce5a96bfa85d0e645a704decc7a8444b0c5bb +size 41545 diff --git a/raw/rel-18/29_series/29559/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29559/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c35ee83755c6558048028d6d4bffd58600a9557 --- /dev/null +++ b/raw/rel-18/29_series/29559/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90e7837a3b0cfadf530e6c4e414f06384072ed839d9e39260d73ece317b4f010 +size 5620 diff --git a/raw/rel-18/29_series/29559/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/raw/rel-18/29_series/29559/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc1549ad4ad09e98bb878e0eef15d8da4bcb6f27 --- /dev/null +++ b/raw/rel-18/29_series/29559/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c625dda306754db2213410e08c5e7220e667c26c9837267e7618e80b0a526eb5 +size 13241 diff --git a/raw/rel-18/29_series/29559/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/raw/rel-18/29_series/29559/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afb7eca4706578ea0073f64e20ff69c2613b7940 --- /dev/null +++ b/raw/rel-18/29_series/29559/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e9a03cc0fd112db81a650cccfaf30cdfb3e194128f02b08fb9b6f42a318c449 +size 39932 diff --git a/raw/rel-18/29_series/29559/a7c51c18111139f9aca2805114108565_img.jpg b/raw/rel-18/29_series/29559/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceb5080d69e8c3b9a7e0a906103f5f3ef9fcd1ec --- /dev/null +++ b/raw/rel-18/29_series/29559/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5125a059b5e752892077aa03babaa80812c3a3ec7a2104d67a14112dddb98244 +size 14414 diff --git a/raw/rel-18/29_series/29559/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/raw/rel-18/29_series/29559/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa101eed0d754e3230fe8b866c670957fc9dc628 --- /dev/null +++ b/raw/rel-18/29_series/29559/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae1dfaf7c5cd427c3a1dd4106a0b9b8c978df5dd894111037d32bfbf38994b97 +size 30341 diff --git a/raw/rel-18/29_series/29559/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/29_series/29559/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53f4dab272aea773acb46b49756e5cfc883e4bd5 --- /dev/null +++ b/raw/rel-18/29_series/29559/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a72432262673c896ec219e08f284abbfe90ad85d262c9d5265a074365c498da1 +size 62862 diff --git a/raw/rel-18/29_series/29559/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29559/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a1b4e131c911dca8c01e71ef37267dd0f49fd80 --- /dev/null +++ b/raw/rel-18/29_series/29559/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06b9fb1a0aebab03483bcfe87dda65f996277d59ba1f1d819210f09d59723a7a +size 38808 diff --git a/raw/rel-18/29_series/29561/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/29_series/29561/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b7859b053b8c414d3a8f6e5d022d848ae28a671 --- /dev/null +++ b/raw/rel-18/29_series/29561/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aba0d0c673809b5dd69a7f8bf83a8cd3c45696adf9a0149ed969490465eaff7e +size 121928 diff --git a/raw/rel-18/29_series/29561/02d0c8a07c481d880b73a25d02050fad_img.jpg b/raw/rel-18/29_series/29561/02d0c8a07c481d880b73a25d02050fad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f186d751a9297fa76ec80f9cafe90879d4d78c --- /dev/null +++ b/raw/rel-18/29_series/29561/02d0c8a07c481d880b73a25d02050fad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:514f28e963df34e8d472a44be151f6e3f3856fb518ee4eda91ccb958fd83442b +size 27381 diff --git a/raw/rel-18/29_series/29561/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/raw/rel-18/29_series/29561/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2429c3ad0171301fd7b98e076c55110092f94393 --- /dev/null +++ b/raw/rel-18/29_series/29561/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a86f3524cc7290c5d084ab479f6ec4abafa19ada879e70fb2ad55b87080bb061 +size 22333 diff --git a/raw/rel-18/29_series/29561/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/raw/rel-18/29_series/29561/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e570b21cfc7140696283b085d9cd63c026d6bc62 --- /dev/null +++ b/raw/rel-18/29_series/29561/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:299bc1e3b10ffb7ec3c6bd92e3fd16b4559451690e236fa9428de700a3ff4fe0 +size 26222 diff --git a/raw/rel-18/29_series/29561/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/raw/rel-18/29_series/29561/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5976bafedf0b3368c3e977205ca651f954937fe --- /dev/null +++ b/raw/rel-18/29_series/29561/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca4c8a692021e3fd13beb38dc79743e4f9c1d6fbef39f0a346513476539e1b5d +size 19316 diff --git a/raw/rel-18/29_series/29561/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/raw/rel-18/29_series/29561/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1688021d6e6a0bd2337de195e46e23ca04f29341 --- /dev/null +++ b/raw/rel-18/29_series/29561/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fd79ba7d84f9726652eadfdda5136d1d37ac32cb63086d818c1b7f13d3f1414 +size 25777 diff --git a/raw/rel-18/29_series/29561/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/raw/rel-18/29_series/29561/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80efc45db31bd7257721005c52e0f39433da0cce --- /dev/null +++ b/raw/rel-18/29_series/29561/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd0efee91427b1f0d8f6205d6ea89dff01a433891b50287655666f33de7b9418 +size 77677 diff --git a/raw/rel-18/29_series/29561/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/29_series/29561/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfeefc945f6f89bd55ac003a02c6d3380e09b7e5 --- /dev/null +++ b/raw/rel-18/29_series/29561/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b574413470425d266c9c54546c1ecc8b7fb94483527f2d7b928882ac0ed68fb4 +size 44429 diff --git a/raw/rel-18/29_series/29561/2e399449b7f62d40167a65ca88888917_img.jpg b/raw/rel-18/29_series/29561/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba118029f545134bfb3220f372d99946c8ee9382 --- /dev/null +++ b/raw/rel-18/29_series/29561/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a2e5b8bfd1470590f7cdcdb4da1bf2764dc08e22f762a69ffee54ddefb579f0 +size 30281 diff --git a/raw/rel-18/29_series/29561/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg b/raw/rel-18/29_series/29561/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2b5170cbc9767e841185e38206a3ea1a5d1987b --- /dev/null +++ b/raw/rel-18/29_series/29561/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbfc51447ba93d2c400bc14aff8bc5d3537a3b3a0d062ca2f65671af55fc6c28 +size 25054 diff --git a/raw/rel-18/29_series/29561/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/raw/rel-18/29_series/29561/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..687472d3a86a61ad3d2bf58b67e22594d73cfe0c --- /dev/null +++ b/raw/rel-18/29_series/29561/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60c2278996ac55e337b1f581c2c064145cd4fa0c7abcd0e9e6ba76ee811d55f0 +size 32150 diff --git a/raw/rel-18/29_series/29561/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/raw/rel-18/29_series/29561/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57d6b143f0a8e9abc6115a88516f9f7c31536d7a --- /dev/null +++ b/raw/rel-18/29_series/29561/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbb462dfe4144c540f3edc4c898d6d399186f3075f1f14a3297feb36da833634 +size 44926 diff --git a/raw/rel-18/29_series/29561/3750b0149a6380885998ab3ca6a8787c_img.jpg b/raw/rel-18/29_series/29561/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea7cde0c54a207dcd83637485a0c963fc3341bb3 --- /dev/null +++ b/raw/rel-18/29_series/29561/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdef895fdb17155bad3360abb962761a4b77f63fcdde5c284263e9ef266873d1 +size 132495 diff --git a/raw/rel-18/29_series/29561/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/raw/rel-18/29_series/29561/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb4b3dcfe137e0c0ef9188de2cd0c71b0a59df61 --- /dev/null +++ b/raw/rel-18/29_series/29561/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db8511bb09331d5a7c585fd073495e037045bbed0d6dd5fcb756a15cd6caa78c +size 33931 diff --git a/raw/rel-18/29_series/29561/552ca016af3d6240648ab5a2cad97f60_img.jpg b/raw/rel-18/29_series/29561/552ca016af3d6240648ab5a2cad97f60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c72622a795850e6e410f44bfff8260f814b7e32 --- /dev/null +++ b/raw/rel-18/29_series/29561/552ca016af3d6240648ab5a2cad97f60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6348cec06455dff25466f8f3e4e14566af24b83cc38b0da7cd1c7aa44514124 +size 26681 diff --git a/raw/rel-18/29_series/29561/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/raw/rel-18/29_series/29561/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c41cb3037497d6c383f0934b449e80711147303 --- /dev/null +++ b/raw/rel-18/29_series/29561/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05618664cb76ac2a87ef256502a1c1cbdadc184de7ddd7ff7a7c9406f6e5531b +size 186711 diff --git a/raw/rel-18/29_series/29561/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29561/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d96f3f60573f738f13ac4b8e2d0970412a5d651 --- /dev/null +++ b/raw/rel-18/29_series/29561/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15bd801abca0e74f4311f792927a13e05d1eb264e32aa289242e33c2b3a9306a +size 9410 diff --git a/raw/rel-18/29_series/29561/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29561/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca3cacbd1e48e90ba3afa514e38268e1a638490a --- /dev/null +++ b/raw/rel-18/29_series/29561/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32b1d5939b0314e0f7660a2de286c8c7eeedc8033837c0172d93677a15a3123d +size 5726 diff --git a/raw/rel-18/29_series/29561/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/raw/rel-18/29_series/29561/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e9620ffbbbc7b3f5de23a9054f101e8d0c81514 --- /dev/null +++ b/raw/rel-18/29_series/29561/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19abec563bda48079167c75e579cf15d1e5536d3a7863b13109e7a778b136ed9 +size 32754 diff --git a/raw/rel-18/29_series/29561/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/raw/rel-18/29_series/29561/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2b3885f5f8d35ead10a01899523d4364b3ed027 --- /dev/null +++ b/raw/rel-18/29_series/29561/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:994f75921a439083517ee86f5ce497b76b92665ea687dc546b6e1d2192a1338e +size 87764 diff --git a/raw/rel-18/29_series/29561/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/raw/rel-18/29_series/29561/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82a09d92fd054b36cd037f0eef307d0ad6b3f6f --- /dev/null +++ b/raw/rel-18/29_series/29561/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:949edd8575fddb154fd2cb71cec14c24e376296cdf1d1760dc05ab1cdfe6ff69 +size 31463 diff --git a/raw/rel-18/29_series/29561/91134b9a38d7f73f03375473e7b706f9_img.jpg b/raw/rel-18/29_series/29561/91134b9a38d7f73f03375473e7b706f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0101db28cd56ec80d319b1dfa6901cf4068f39 --- /dev/null +++ b/raw/rel-18/29_series/29561/91134b9a38d7f73f03375473e7b706f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdc7e196e99aff8de443943726e36bc4afae5a43cd5ea684deaf23c784ba2747 +size 31223 diff --git a/raw/rel-18/29_series/29561/9c45844d796e85ae05505870a54e4eb4_img.jpg b/raw/rel-18/29_series/29561/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5326220d18238a1747d5641cd3150f1a5fed6c09 --- /dev/null +++ b/raw/rel-18/29_series/29561/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b7c418f5153c1f5fc71e5039b88fb198da11908274e3fe2f77f115504e8df8 +size 95043 diff --git a/raw/rel-18/29_series/29561/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/raw/rel-18/29_series/29561/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5725cf8eaaac410b73e58c1c3d908fad37e8fe44 --- /dev/null +++ b/raw/rel-18/29_series/29561/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64a123db9351cafdec559102cc005de5b9198b1a937f8080f5ae48320a1f2a69 +size 22599 diff --git a/raw/rel-18/29_series/29561/a3472689858b068ef469213682965325_img.jpg b/raw/rel-18/29_series/29561/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec520fa59a435995471f972823a9e6d1e2a852fc --- /dev/null +++ b/raw/rel-18/29_series/29561/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00176b932d1280a5df0e3824ab4ba6675474ebee9e6365e3863d3040cc76286 +size 15899 diff --git a/raw/rel-18/29_series/29561/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/raw/rel-18/29_series/29561/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..950cc7d86d6f68590f925ded29800f7c662b315d --- /dev/null +++ b/raw/rel-18/29_series/29561/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0be8fc4047e07eed0538c386269b0c433d61d03a3087d68a9db5f63e9ab79cc +size 36329 diff --git a/raw/rel-18/29_series/29561/b5335262987c819d7f71ce40f99cb71b_img.jpg b/raw/rel-18/29_series/29561/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b10631c3873dc4458e5f4532bbf3fed9d25637f5 --- /dev/null +++ b/raw/rel-18/29_series/29561/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e176c106f2acc6695e21b799b51c0a3dc51d4f10f27be52699366dd3f703e4e0 +size 195311 diff --git a/raw/rel-18/29_series/29561/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg b/raw/rel-18/29_series/29561/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c70f8fb09944d6274cceeafd02fb3266a56b48f --- /dev/null +++ b/raw/rel-18/29_series/29561/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e100d40ce1bccf3a9804e60ff7be53f7708c6e4a031485bc2c2afacea286e9c +size 26751 diff --git a/raw/rel-18/29_series/29561/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/raw/rel-18/29_series/29561/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea041ca6a9ec9e6b4aa099985d42ac6aa702dff --- /dev/null +++ b/raw/rel-18/29_series/29561/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6a098ad76f8df8d3fc1654516ff2766895f7e1aeddb692130739168b803cfa0 +size 24648 diff --git a/raw/rel-18/29_series/29561/c5c767928d086da5347036f88309fc7a_img.jpg b/raw/rel-18/29_series/29561/c5c767928d086da5347036f88309fc7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d760f0f0baa04122c69e79265c20c7f1d9163ba --- /dev/null +++ b/raw/rel-18/29_series/29561/c5c767928d086da5347036f88309fc7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a2dfa9d1bd10d0c68916f428f3f9ffc4705e3fc3b2bfa52bea9d16d96a91b62 +size 24755 diff --git a/raw/rel-18/29_series/29561/cc542843836eecb036b99cb270b54a1e_img.jpg b/raw/rel-18/29_series/29561/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827acfaa3c8ad708b84a3e4604fc4caf78a85c1a --- /dev/null +++ b/raw/rel-18/29_series/29561/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf19cac93fabfd7c88323b901bbdf5616b53511d3e7a3c3e22185a63de20aa56 +size 34753 diff --git a/raw/rel-18/29_series/29561/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg b/raw/rel-18/29_series/29561/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..580453a1dec322014ab21e44ae1b2ab4a6f91131 --- /dev/null +++ b/raw/rel-18/29_series/29561/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d108f14d2f0d468335bd2e5be38054eb0a94c6a61b956d2eb5768f907b3f75df +size 31055 diff --git a/raw/rel-18/29_series/29561/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg b/raw/rel-18/29_series/29561/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86b639c254bb973a9490625c54332ed4ba394229 --- /dev/null +++ b/raw/rel-18/29_series/29561/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7f6e148d69f0424a0937e5e87fbfbd4a41bcc8578aa61d32b7e398a4be63157 +size 47377 diff --git a/raw/rel-18/29_series/29561/d2417b04116c354deccb25d98a84a0fb_img.jpg b/raw/rel-18/29_series/29561/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abb27688d043ea8f75d3cdd3ea84ced1ace0598c --- /dev/null +++ b/raw/rel-18/29_series/29561/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6df497b4839c84986b9d200487990f8fa0d38ec33d7e3d74d3a81d3e7daec73b +size 19518 diff --git a/raw/rel-18/29_series/29561/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/raw/rel-18/29_series/29561/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6cdd6df0449af0696bd0a58b8bb28dd9348cb2b --- /dev/null +++ b/raw/rel-18/29_series/29561/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78c3e7bd720d8543421fc85d30ae9c1493666d90d23bb157da00948392e64759 +size 37441 diff --git a/raw/rel-18/29_series/29561/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/raw/rel-18/29_series/29561/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70e5dd9ff671afbfca35f605618ad80a3f07f582 --- /dev/null +++ b/raw/rel-18/29_series/29561/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ea86ee78d391ab7b04cedfb4c780df03af4b35b0e621c085c8fbdaf4a187169 +size 35881 diff --git a/raw/rel-18/29_series/29561/e38f0349f1b6094626cbfeab7105f029_img.jpg b/raw/rel-18/29_series/29561/e38f0349f1b6094626cbfeab7105f029_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4964cdaa2dc83506877fa92ac17da582292c775d --- /dev/null +++ b/raw/rel-18/29_series/29561/e38f0349f1b6094626cbfeab7105f029_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb1f11ba8ac0bfd18a6a0560e7b2db2ad027272e3bc5f05550e0398bb8e33ab9 +size 41912 diff --git a/raw/rel-18/29_series/29561/e58a867750e4ae01604318506b79df7a_img.jpg b/raw/rel-18/29_series/29561/e58a867750e4ae01604318506b79df7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75c6285f76e8cd546b0e48ae6bf328874ca1ce12 --- /dev/null +++ b/raw/rel-18/29_series/29561/e58a867750e4ae01604318506b79df7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4d20cf75ea2e8ad152cad75660a6bb0f8939e410de006f856a8d5aede98032 +size 36038 diff --git a/raw/rel-18/29_series/29561/e7010c66da16316c2935dfbbef5056b3_img.jpg b/raw/rel-18/29_series/29561/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14054a674ec255c317b70f0dad690ffe2948f26d --- /dev/null +++ b/raw/rel-18/29_series/29561/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d32a169585f111bdfe13c5580c75a4b750e0e06e2f5707e41cca9a24f65fed1b +size 100968 diff --git a/raw/rel-18/29_series/29561/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/raw/rel-18/29_series/29561/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15bb98d3842b53720584af813292728d22c524f9 --- /dev/null +++ b/raw/rel-18/29_series/29561/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a13db2f6f0a9598c0f7abab211b2db557c9ee1694f7452ec780f4d63d5e9c8ad +size 123237 diff --git a/raw/rel-18/29_series/29561/fcc757566216206ceddbd6c775e8db02_img.jpg b/raw/rel-18/29_series/29561/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..817d1e41280f0b995eefbd4263b54a06f1966207 --- /dev/null +++ b/raw/rel-18/29_series/29561/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d0e806aaafdaa678217179681cf7ac0ad69dfead4164cd890a1b91acfcd397d +size 31829 diff --git a/raw/rel-18/29_series/29561/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29561/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a91eeb394fe53a0091ba4278c65b74bc1ed0b1f --- /dev/null +++ b/raw/rel-18/29_series/29561/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6622f8bd72fd4a548223ccacebcaad084ade5bbc0167102bc1e7b4ffe37519e5 +size 33328 diff --git a/raw/rel-18/29_series/29572/124c6108c63173818afb8ed49521e22d_img.jpg b/raw/rel-18/29_series/29572/124c6108c63173818afb8ed49521e22d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87935e4bddcd96d9c7cc6688982b6198eb613135 --- /dev/null +++ b/raw/rel-18/29_series/29572/124c6108c63173818afb8ed49521e22d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d105a31db06f7a123329729a1a016c3c184a43e977733d90113f5cbbabe27f64 +size 30605 diff --git a/raw/rel-18/29_series/29572/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29572/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd9f730e250d4ccf47fbc8f40b48f4bae4e47a18 --- /dev/null +++ b/raw/rel-18/29_series/29572/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c92a568f6bce1428a12ace390dd5b6f20dac9e0cace1f3a9ea248ed45208cbc +size 9485 diff --git a/raw/rel-18/29_series/29572/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/raw/rel-18/29_series/29572/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08da3693a5a625cbf84acbae8cb6635a3b4ca62f --- /dev/null +++ b/raw/rel-18/29_series/29572/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f32c9f282b2945b83b0c966e4742bb57f1bcdce5cc3baa98082dba91e3a917f9 +size 33470 diff --git a/raw/rel-18/29_series/29572/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29572/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02e354b3e11f23e2b2c4af0eaf00d712d2cb0b5a --- /dev/null +++ b/raw/rel-18/29_series/29572/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbe2e904eb9329b8b5c5f38eb07b621b371696cb545491d24da445a883a094a6 +size 5646 diff --git a/raw/rel-18/29_series/29572/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/raw/rel-18/29_series/29572/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a07ec40675abdcbc744b360ad3d9be836ff7d0e7 --- /dev/null +++ b/raw/rel-18/29_series/29572/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28d6a1fc9aeab409c866effdf8b3efc3f3f9c1ce023f0be8c7c693b8159df289 +size 28470 diff --git a/raw/rel-18/29_series/29572/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/29_series/29572/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9317f0f7b05e2e40c391b54e5da33e444420d5f --- /dev/null +++ b/raw/rel-18/29_series/29572/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18843a8161e1730568d4724cf6469448a25b656cc88f749921e3b6fb8e297eb1 +size 31401 diff --git a/raw/rel-18/29_series/29572/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/29_series/29572/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4467b08b4e40c617170e8ea6b694bda001ddb26 --- /dev/null +++ b/raw/rel-18/29_series/29572/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e3815327388514e58ca0aafbfb2aaff9ec086e574a0c216b9e385e440ecce92 +size 30575 diff --git a/raw/rel-18/29_series/29572/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/29_series/29572/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..068334f9f304274362e3bf8be10186f0217c4141 --- /dev/null +++ b/raw/rel-18/29_series/29572/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0940061dea39e9219f93c39fc78aa3ca04639c980f5bb897c7e0d4e13248cb51 +size 31697 diff --git a/raw/rel-18/29_series/29572/9a047c6501a487b3f18cfff971bcb33f_img.jpg b/raw/rel-18/29_series/29572/9a047c6501a487b3f18cfff971bcb33f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81e00d4007c96186efd81f499be79e6065bc13eb --- /dev/null +++ b/raw/rel-18/29_series/29572/9a047c6501a487b3f18cfff971bcb33f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:effc66d123453615f7667b5816fc6bb7a9ca7af7aa58577b9ae207d10141c383 +size 33045 diff --git a/raw/rel-18/29_series/29572/9b62a616c7a1097c5da57f001ab6dd64_img.jpg b/raw/rel-18/29_series/29572/9b62a616c7a1097c5da57f001ab6dd64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310b0a6b49d99b21f5bb09d1d8e30f41a12cbc5c --- /dev/null +++ b/raw/rel-18/29_series/29572/9b62a616c7a1097c5da57f001ab6dd64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4364d263c8fde67fd9de8d0ab141a2d789abaf575f48d433aedf6e9cfd1d346f +size 32429 diff --git a/raw/rel-18/29_series/29572/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/29_series/29572/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd276dee9fb83c6ab2fed126d1fe425997d348d7 --- /dev/null +++ b/raw/rel-18/29_series/29572/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:936d79cb5d47419f7c061f90393051428e41d182a1478f56a9502d72c2047a69 +size 34380 diff --git a/raw/rel-18/29_series/29572/a7c51c18111139f9aca2805114108565_img.jpg b/raw/rel-18/29_series/29572/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eb722e63fdde94424bd05ba2ca10cb4055b9288 --- /dev/null +++ b/raw/rel-18/29_series/29572/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13ca8f2aa7c43ac1a8c15fe9c69694f6e68d6feb8a55d20756ba9c6b468eea15 +size 30968 diff --git a/raw/rel-18/29_series/29572/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/29_series/29572/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80c0956f33dd088be1cbbfc01ea0cc8c9984e8c3 --- /dev/null +++ b/raw/rel-18/29_series/29572/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8426848247ecc34b9278154a612586eceb76224438f131bf7b64fb7668976e8b +size 52237 diff --git a/raw/rel-18/29_series/29572/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/raw/rel-18/29_series/29572/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d38a0ddae01f690f347f2cd4d3a67d548f6a07b8 --- /dev/null +++ b/raw/rel-18/29_series/29572/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb3af2646501a0a647517ce88c33fdda75f76bec0fdeb94b539052462d473e67 +size 12036 diff --git a/raw/rel-18/29_series/29572/ebebcfd45155572c64483e069ed43320_img.jpg b/raw/rel-18/29_series/29572/ebebcfd45155572c64483e069ed43320_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdca46039f622e386dbb022321fcfb91dea13c51 --- /dev/null +++ b/raw/rel-18/29_series/29572/ebebcfd45155572c64483e069ed43320_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69154b1e5d7c8da94583be2cf95144462c4d8114382c6f96014fbbf43f2baa65 +size 13373 diff --git a/raw/rel-18/29_series/29572/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/raw/rel-18/29_series/29572/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f821371f336611c1d2ecb9e2ec4394f1d5f3b1c1 --- /dev/null +++ b/raw/rel-18/29_series/29572/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07436e83923a689728a11e6380a003fcaa0732cc3bd071b89b6adf6bf6764cc9 +size 29713 diff --git a/raw/rel-18/29_series/29572/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29572/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..718f11d16e94ebe003a394e0bc88ad20b776de7f --- /dev/null +++ b/raw/rel-18/29_series/29572/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f41e9aca283485140535912a98c7e0cf90cae0a23ee6b24bf154fe9e57e94e9 +size 31617 diff --git a/raw/rel-18/29_series/29573/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/29_series/29573/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cdd92af71f24e493fcb11512f29a6386dac1844 --- /dev/null +++ b/raw/rel-18/29_series/29573/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21de504359b3539569c71d02abbdf07f573a37cf19067b55e3f6712e09555202 +size 32876 diff --git a/raw/rel-18/29_series/29573/088921fa3f5a44c8551815122517eefd_img.jpg b/raw/rel-18/29_series/29573/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab3be752e9c10de110e6cf2434f38e953622358f --- /dev/null +++ b/raw/rel-18/29_series/29573/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e8ba0d9ba4a94d78a1963345d8cc7967cc21863c2ccb08ead65452f94894b31 +size 33904 diff --git a/raw/rel-18/29_series/29573/0b998e3ad8f9d104768642612605cb35_img.jpg b/raw/rel-18/29_series/29573/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6545261e0c2b5197687888600bfd0db45535728 --- /dev/null +++ b/raw/rel-18/29_series/29573/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c8147a629559d36172deaf1719f02434587ab30f3604d071903de8be794bdd6 +size 207260 diff --git a/raw/rel-18/29_series/29573/16152cf1d84aea10848758f51a91ff6a_img.jpg b/raw/rel-18/29_series/29573/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6eda47b96f0516871a3ea7d76176cc0186f93cd9 --- /dev/null +++ b/raw/rel-18/29_series/29573/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad4880b02af700384a03fcd22b819da8d495447ef53b1078647b29409ea4bf7e +size 39154 diff --git a/raw/rel-18/29_series/29573/17431d8b59408f09df7552d8bdbaa015_img.jpg b/raw/rel-18/29_series/29573/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45e24b337feba53b452ba1aa1543f5eb47662f44 --- /dev/null +++ b/raw/rel-18/29_series/29573/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5edde89f94c25d24dd7a68f32d93aaf3be2094545db9ae4cbca830d02cd8973d +size 213153 diff --git a/raw/rel-18/29_series/29573/187bba66c887c745c512add37a577c5e_img.jpg b/raw/rel-18/29_series/29573/187bba66c887c745c512add37a577c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff91387a634986c6a2af787a9ef6cfae2792c40f --- /dev/null +++ b/raw/rel-18/29_series/29573/187bba66c887c745c512add37a577c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:178d5d9e079316396006bc42f740ae20a012427ad0ced282bc30f1a24ede0617 +size 45498 diff --git a/raw/rel-18/29_series/29573/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/raw/rel-18/29_series/29573/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6df19503c713df940381629532e8c505abd11dc --- /dev/null +++ b/raw/rel-18/29_series/29573/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb2896a0d7eb082146cd99717d23c3394387af36284a5ece25d5b3cb3d92b161 +size 39926 diff --git a/raw/rel-18/29_series/29573/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/29_series/29573/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66be9bae8f01e73a0dc843a61aaecf4030a7d265 --- /dev/null +++ b/raw/rel-18/29_series/29573/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9816e90e1d3929c92f733f62e81b3e3de3bf434cd7a63ee5144c25d23cc30c0c +size 122076 diff --git a/raw/rel-18/29_series/29573/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/raw/rel-18/29_series/29573/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..521d5376661bcde89af8f0343b41c6c2b9437576 --- /dev/null +++ b/raw/rel-18/29_series/29573/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58db073425f3aa51518570f73330934017fe65fd7ff680bacc25164296864f0d +size 105701 diff --git a/raw/rel-18/29_series/29573/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29573/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4160dee77b15caee0d84b640c9b327d95431f17c --- /dev/null +++ b/raw/rel-18/29_series/29573/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:652a60eab146559880e82139684502043b347c1be4cc2d29c09a086e89ca2468 +size 10145 diff --git a/raw/rel-18/29_series/29573/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29573/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc741a09576d9aa0886262e150f47239aa14d609 --- /dev/null +++ b/raw/rel-18/29_series/29573/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cd3f583e2e481b67e1cbfee3ad65ebf53a721feec0d2775d622a3a23b59dc68 +size 5684 diff --git a/raw/rel-18/29_series/29573/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/raw/rel-18/29_series/29573/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d92451984a3f33d1a56d50ef12a1201a0057342 --- /dev/null +++ b/raw/rel-18/29_series/29573/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da8c02547312ed8ee02fb4fd5c4060383d7a6ca2e500e2e5b98f9b582f8f49e2 +size 36139 diff --git a/raw/rel-18/29_series/29573/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29573/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d55f799b51c29a78c881012bf5df82d46fa7624b --- /dev/null +++ b/raw/rel-18/29_series/29573/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08aaf8a9815bef53ad998f0f9921bcd3c061f45caadce7e7787a6a246dd43efe +size 140514 diff --git a/raw/rel-18/29_series/29573/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/raw/rel-18/29_series/29573/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a7880e952d4f35d447092f4b937ff224d43e7cb --- /dev/null +++ b/raw/rel-18/29_series/29573/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7adaa298b8a2684b2ec01d541e267b900b60b9f16eb965c1f0fb7f319128fc92 +size 37013 diff --git a/raw/rel-18/29_series/29573/7f17c430b9598e4d748a8041457810b3_img.jpg b/raw/rel-18/29_series/29573/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bd04800901ee6d4c3ce117529fc5f8299876e81 --- /dev/null +++ b/raw/rel-18/29_series/29573/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3815ab42c1f39205a9930d031301149741508dd21eb120e1e45270e52b6664b6 +size 27121 diff --git a/raw/rel-18/29_series/29573/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/raw/rel-18/29_series/29573/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14bbd4cf2d93c76e1d546cca5915e0f7d2afeaa7 --- /dev/null +++ b/raw/rel-18/29_series/29573/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50ae00207b4d6c341950ce97f0292c991c90a3602d7332292544b19504f2820f +size 33105 diff --git a/raw/rel-18/29_series/29573/853f59c89931a666c07903b31d098277_img.jpg b/raw/rel-18/29_series/29573/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d59c0276a571605a8cdd46d9390dc02d370d4ea0 --- /dev/null +++ b/raw/rel-18/29_series/29573/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b06a4a06f1334035f59c9c9df3a7a269d9d3126b8d855b8d49a5d664136314b +size 26927 diff --git a/raw/rel-18/29_series/29573/8d3bccba4f386e419559f07e332176fb_img.jpg b/raw/rel-18/29_series/29573/8d3bccba4f386e419559f07e332176fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..747012bc62cfb84c6538f253fa6715fecf40469f --- /dev/null +++ b/raw/rel-18/29_series/29573/8d3bccba4f386e419559f07e332176fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7b0d41d39ed2f6faa41e12338b246ce5aa933657cac217dd4d1bbfd31916239 +size 11828 diff --git a/raw/rel-18/29_series/29573/a4b963a07cc368283154762c4b156fe7_img.jpg b/raw/rel-18/29_series/29573/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3dfc1f829fc6a25e463f3cc02af01cb2f8540628 --- /dev/null +++ b/raw/rel-18/29_series/29573/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21a530d188df153862b5990a07e8cc372c5c7c9626b46b6a4be13896c68632c6 +size 95883 diff --git a/raw/rel-18/29_series/29573/a5404b7275b06497eecf9b5883604753_img.jpg b/raw/rel-18/29_series/29573/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9040f0dc84d8265d31478cd2134e9a4b01f1be6 --- /dev/null +++ b/raw/rel-18/29_series/29573/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f52e779db62d57d409990b56d929e65617244b3a360e95753d94e0908e30c25a +size 210257 diff --git a/raw/rel-18/29_series/29573/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/raw/rel-18/29_series/29573/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6cc5d905ebb85660f5665eb21dcf9a158e3e794 --- /dev/null +++ b/raw/rel-18/29_series/29573/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c72b8cb343c6ed73a7f587300aae8830ed384bad9142ed912a6940836b097249 +size 110209 diff --git a/raw/rel-18/29_series/29573/a963ca41bde1669b18a4b783616f228b_img.jpg b/raw/rel-18/29_series/29573/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..060491259472737ef3a0c191e8b8290718afe120 --- /dev/null +++ b/raw/rel-18/29_series/29573/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:949e092b03ee4e488e73a03f863186b397c27934e29fc5b292095a03793e7198 +size 140951 diff --git a/raw/rel-18/29_series/29573/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/29_series/29573/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe2d21676fe4b849bd767331b5c815d4002a7204 --- /dev/null +++ b/raw/rel-18/29_series/29573/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76a5390b99ee942ad42d951c2633695d28482de16b069380ed032e73afaf969a +size 31096 diff --git a/raw/rel-18/29_series/29573/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg b/raw/rel-18/29_series/29573/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d10daee0faf5f909bd93ee610603aa1ec27ac62 --- /dev/null +++ b/raw/rel-18/29_series/29573/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ff963d9f553a27c79c4b384b017b01e2a7701d37cb5921cb33381ba65ed72fc +size 142222 diff --git a/raw/rel-18/29_series/29573/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/raw/rel-18/29_series/29573/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ba10896b3378e3b3c9570e6a159ba82a82cd0d5 --- /dev/null +++ b/raw/rel-18/29_series/29573/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77f7dca591b2836a61f3eafbc3b0a2b81474f54e73907b79e62fba49534954a +size 204101 diff --git a/raw/rel-18/29_series/29573/e58a867750e4ae01604318506b79df7a_img.jpg b/raw/rel-18/29_series/29573/e58a867750e4ae01604318506b79df7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c7462aa135ae255d14efe4c79a29a4169ce9f94 --- /dev/null +++ b/raw/rel-18/29_series/29573/e58a867750e4ae01604318506b79df7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b6c29b111db8e6bc7edb9ab39f75dd510afe8578f647523d00383ea5365f142 +size 10637 diff --git a/raw/rel-18/29_series/29573/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/29_series/29573/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66bfdf4120588de6651811cfa3fe5e7f948e0766 --- /dev/null +++ b/raw/rel-18/29_series/29573/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02c3e6dce1082349a8f65fa447b6c9c370b7e0ba0fdf8e531474af70b75c921b +size 36696 diff --git a/raw/rel-18/29_series/29573/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/raw/rel-18/29_series/29573/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a24e53b9b4ef645b9d1be00ff2a599dfed09fc1 --- /dev/null +++ b/raw/rel-18/29_series/29573/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36c2a923f4d54f150e04960a6fd70a5c0c6b5db1006155e6486e36671b8dd325 +size 139659 diff --git a/raw/rel-18/29_series/29573/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/29_series/29573/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e899431e8e0372e991300227aa8185e1f18f29f --- /dev/null +++ b/raw/rel-18/29_series/29573/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b718ece5de444d8a59b57d898a0d1ae1fe18df158dd2635e93556bd1f98263f0 +size 34518 diff --git a/raw/rel-18/29_series/29573/ef45b00396c293be0b18d32b97118bf4_img.jpg b/raw/rel-18/29_series/29573/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..033ba65fe47c62aa00d0cb83554552ffdd91f8a3 --- /dev/null +++ b/raw/rel-18/29_series/29573/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05b657653894d1fcd9de09ffe3a4ffc2b5fe85cbe33a352280539e09cb080b24 +size 206416 diff --git a/raw/rel-18/29_series/29573/f2ea0f64a770b22b902820457d262265_img.jpg b/raw/rel-18/29_series/29573/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbcf43221360a6d8a868f99521ce5a97de1785db --- /dev/null +++ b/raw/rel-18/29_series/29573/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1d208acdca41e2d003394f3324f680f7e101a7ffb3f3f627723b311acff0d73 +size 29068 diff --git a/raw/rel-18/29_series/29573/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/raw/rel-18/29_series/29573/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0da5ea96b4b013e8d11e6c4769227512d658c184 --- /dev/null +++ b/raw/rel-18/29_series/29573/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14c3ccad3323d023d0eca2f355f99dbc5b006b96f6aaa8e53d55578feb97efd3 +size 36757 diff --git a/raw/rel-18/29_series/29573/fc3e2b49a9f850951570e502393b697f_img.jpg b/raw/rel-18/29_series/29573/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e274b68c77685b1af4be95d3d5729126f364f3ce --- /dev/null +++ b/raw/rel-18/29_series/29573/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a1fc6e92c3a6fd91f524719006e3cfc1d8b64cd4d3f1fc59165c9c9837ab0e5 +size 204080 diff --git a/raw/rel-18/29_series/29573/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29573/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58898743131754947af592725613c09938311564 --- /dev/null +++ b/raw/rel-18/29_series/29573/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:227730d28b6bbda631dd87d6c5215709884605649d503beeb9f829184cf1b8f3 +size 22198 diff --git a/raw/rel-18/29_series/29574/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/29_series/29574/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd78e5e7508e8eeb576e3eb1ab1efab33b2eaaac --- /dev/null +++ b/raw/rel-18/29_series/29574/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d63bf5a72241548fabc6c21872164877dd5d4bef07f5fa724bf255952759c65d +size 33739 diff --git a/raw/rel-18/29_series/29574/0fa26005ab105a07af4fda20b2554987_img.jpg b/raw/rel-18/29_series/29574/0fa26005ab105a07af4fda20b2554987_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..954095b46c6ca9d12f28d5f9a9bb10fb8a700a14 --- /dev/null +++ b/raw/rel-18/29_series/29574/0fa26005ab105a07af4fda20b2554987_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8458a96ff9ac881ca1001fb98e8afb62092e4a65e7287de4957822dea8ef935e +size 25504 diff --git a/raw/rel-18/29_series/29574/16152cf1d84aea10848758f51a91ff6a_img.jpg b/raw/rel-18/29_series/29574/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19ad779fd240a54e5fa0f46c9ff791704532cb1d --- /dev/null +++ b/raw/rel-18/29_series/29574/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f2c731921d57454e4adf34546f1ec70be95d6a0c7f9a6b7de8b2734bb8b60e3 +size 35622 diff --git a/raw/rel-18/29_series/29574/2119293733c74fc64de88aefd597f4bb_img.jpg b/raw/rel-18/29_series/29574/2119293733c74fc64de88aefd597f4bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..937173552f9bab480f7ea603614373523002c6bd --- /dev/null +++ b/raw/rel-18/29_series/29574/2119293733c74fc64de88aefd597f4bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2361376577f93880868fe677ee6652b64d4e6fb580e66f27535cd6a71712e3dc +size 26912 diff --git a/raw/rel-18/29_series/29574/421fc75480c21e7ebb25756826652367_img.jpg b/raw/rel-18/29_series/29574/421fc75480c21e7ebb25756826652367_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..296bd5f8623853a96314332142de320812e052c2 --- /dev/null +++ b/raw/rel-18/29_series/29574/421fc75480c21e7ebb25756826652367_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cea7056d3e175ae479d11e51c276239e9ae9a5035d2d8a2885414e4eb11a502 +size 31028 diff --git a/raw/rel-18/29_series/29574/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/raw/rel-18/29_series/29574/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc5180434478b0e852425310b1a9618354d9874d --- /dev/null +++ b/raw/rel-18/29_series/29574/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a82dad1fe3cbda0c92f1da8c147d21698e8b2dbf52f684180e97a49d7d51bc35 +size 30077 diff --git a/raw/rel-18/29_series/29574/523ab7b925beb555f88b2e1e1336974f_img.jpg b/raw/rel-18/29_series/29574/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a416fc666d63298099af15a049209faba0a36f6 --- /dev/null +++ b/raw/rel-18/29_series/29574/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a922a4c4f3d473a4c7e0bad1587dc14bb057d4c55cb1d18173c84da46bdbefd +size 30706 diff --git a/raw/rel-18/29_series/29574/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29574/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47c0a9c363da693f180c8fba070e1c72c7e06bf9 --- /dev/null +++ b/raw/rel-18/29_series/29574/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5add53e98bf1ef1b86c1e9981c6213e3529878ee11a7c986d419886e125e3fda +size 9505 diff --git a/raw/rel-18/29_series/29574/63e0c22852c26699d0bd095a2d796bab_img.jpg b/raw/rel-18/29_series/29574/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83f55b0ffd1211c4a7b1022ff55fe12a4d081e24 --- /dev/null +++ b/raw/rel-18/29_series/29574/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:474fff8c90c1b19eb682194e61135ca6d0e3ef00171cba3bf3810e6381a049c3 +size 33281 diff --git a/raw/rel-18/29_series/29574/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29574/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c77cb99eb6bcad16e249216d90d2b2fc4826eb72 --- /dev/null +++ b/raw/rel-18/29_series/29574/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a4692109fac06c1ded0ee9d67fa66d06f653bb88fb5fba868bb51714a9816d2 +size 5703 diff --git a/raw/rel-18/29_series/29574/6929132b4964d52244da61d4614bc4d6_img.jpg b/raw/rel-18/29_series/29574/6929132b4964d52244da61d4614bc4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3e70ee6ada07d4e6364b2d32f46be5b5ec761e0 --- /dev/null +++ b/raw/rel-18/29_series/29574/6929132b4964d52244da61d4614bc4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae99410277691ffd4a20951d5dcc383fd8a58c6b09d8467e3bb81ee4124eafd0 +size 11747 diff --git a/raw/rel-18/29_series/29574/6f659142d4789aa889184459f884787e_img.jpg b/raw/rel-18/29_series/29574/6f659142d4789aa889184459f884787e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b43307c2768569531021cfaf0575376b2899003 --- /dev/null +++ b/raw/rel-18/29_series/29574/6f659142d4789aa889184459f884787e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b16582b58aca530c8fc25182615ce015ef539b6ed1c92f89b9d7102c493fe78 +size 28384 diff --git a/raw/rel-18/29_series/29574/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/29_series/29574/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f2301fa244029f85c9427fbb930d448e9f8b27d --- /dev/null +++ b/raw/rel-18/29_series/29574/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f2ee1c647fe365380b7c1e2bf1075e9dbebdd1e48174a6f983ce229c6dee815 +size 31984 diff --git a/raw/rel-18/29_series/29574/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/raw/rel-18/29_series/29574/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ffb5afb29aee33961397b963430dc4e6b1bd934 --- /dev/null +++ b/raw/rel-18/29_series/29574/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15c8963ffd329fb69c959c9a25cd14d358bc179d302be42931904d3337987212 +size 19513 diff --git a/raw/rel-18/29_series/29574/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/raw/rel-18/29_series/29574/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d5a82e20ae2d25921ff844cbe6f91b2ba76e0c8 --- /dev/null +++ b/raw/rel-18/29_series/29574/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e1cab5631b704a41798a34c4a2443d978bd9af37fd6e823585550feb2f88725 +size 14311 diff --git a/raw/rel-18/29_series/29574/db5d70841d5b72a53235d7156a8e4c84_img.jpg b/raw/rel-18/29_series/29574/db5d70841d5b72a53235d7156a8e4c84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66bf0e272b1cae941eb94d66fa7ac54eaf6e6eb3 --- /dev/null +++ b/raw/rel-18/29_series/29574/db5d70841d5b72a53235d7156a8e4c84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a0980277d47883b05911de07c7c7549c3e9bc6fbd9f01b805b220d201301b64 +size 30613 diff --git a/raw/rel-18/29_series/29574/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/29_series/29574/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c3b6b9e0f7c779ea5720094dbca5791f075f7ff --- /dev/null +++ b/raw/rel-18/29_series/29574/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fef3b7399e3a473f3816aea69dcbb2db14b31a2e565c0cc06b10d18cc17025b0 +size 35334 diff --git a/raw/rel-18/29_series/29574/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/29_series/29574/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04ec1bdfc8c50e652113dbf501ec237b393e11e8 --- /dev/null +++ b/raw/rel-18/29_series/29574/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97ee57f6e1bbb1e3495d30667ac4a8821ce3695b9ff976e19a69b769b01be5ab +size 34571 diff --git a/raw/rel-18/29_series/29574/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/raw/rel-18/29_series/29574/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7f6efdb5d33e75f0b4ecedaa15aa53101547696 --- /dev/null +++ b/raw/rel-18/29_series/29574/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efa7bc26ad8a952351eb5bb7eed94c204f69453980e9ef64a1106ac3637d73b9 +size 28555 diff --git a/raw/rel-18/29_series/29574/fbfa653853daf5541118a9ddecb92284_img.jpg b/raw/rel-18/29_series/29574/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdd6c3120bf8aeedc8c9beca944b76ca8c25d3f8 --- /dev/null +++ b/raw/rel-18/29_series/29574/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7fde50f537233daec58c3b3177defc694223f5f50f295f180e69e8f893f5c87 +size 28862 diff --git a/raw/rel-18/29_series/29575/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/29_series/29575/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36498d4ec7c468e4fbea52733e9a59a00fa865f7 --- /dev/null +++ b/raw/rel-18/29_series/29575/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:181024ed48517cd95d10d1eb0871217ba3f22174d52982eaa592e1cbcc8852f4 +size 36623 diff --git a/raw/rel-18/29_series/29575/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/raw/rel-18/29_series/29575/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3f6da784d7713fb765203d450f736dcec1171aa --- /dev/null +++ b/raw/rel-18/29_series/29575/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bdad8ce2121cba055112569c3a5133df8c60eccba0c1be843046cea1abcbfe1 +size 6727 diff --git a/raw/rel-18/29_series/29575/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/raw/rel-18/29_series/29575/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6553ca1c51ee70dcd4718de6bc6d634d4512771a --- /dev/null +++ b/raw/rel-18/29_series/29575/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e11a61cdab862d9580d00851ace0434accc5477d920a570e5aa06a0dbd4f5a7 +size 35006 diff --git a/raw/rel-18/29_series/29575/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/raw/rel-18/29_series/29575/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4af6bfa83470fda49fc9c4509dbf5ca52b18ce9a --- /dev/null +++ b/raw/rel-18/29_series/29575/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0dcdfa158dc089b1ed641de864facdef103acd29443a01cb661d8868417f234 +size 33590 diff --git a/raw/rel-18/29_series/29575/4356776ca004ecba5d599667a155d7d4_img.jpg b/raw/rel-18/29_series/29575/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccabc319b4f8f6a9a4adf4b6c1cd03a7e82ee10e --- /dev/null +++ b/raw/rel-18/29_series/29575/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13349cb8255221f73cfab22bd4687cc7361a3e3077f82dc2a645bb982b8a6d99 +size 33235 diff --git a/raw/rel-18/29_series/29575/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/raw/rel-18/29_series/29575/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b22c2d0a9657bd6da85706ec104f29df0c1f585 --- /dev/null +++ b/raw/rel-18/29_series/29575/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c320b152e229f86e235e4abff9afc73fcf5907b0bfed0ce53d767ad754f52b3 +size 41958 diff --git a/raw/rel-18/29_series/29575/55136bc716146672fc680fa05989f1d2_img.jpg b/raw/rel-18/29_series/29575/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a39e78caf618dc5911beaeef5a98d7ef640bf60 --- /dev/null +++ b/raw/rel-18/29_series/29575/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:480254e3efbfa5e5ff59eb139b275e4a942c3d626a64995f9a253984afa9be96 +size 35370 diff --git a/raw/rel-18/29_series/29575/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29575/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f64ae305b56ddf01d0993fdc45c761b5fe0a204 --- /dev/null +++ b/raw/rel-18/29_series/29575/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b337c0dcba4aa2c230f1bbf8e9957cb6da70e83695dd5e4d230906c10ede784 +size 9505 diff --git a/raw/rel-18/29_series/29575/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29575/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b484e58c6eef48ebf932b2e8b616630ed923cb36 --- /dev/null +++ b/raw/rel-18/29_series/29575/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0677d107a762042fb52fe9caf19349e0879c7ae88bdab39674e9a1ad56818860 +size 5674 diff --git a/raw/rel-18/29_series/29575/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/raw/rel-18/29_series/29575/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e301075dc0a9629b562e376bf4303be4d08417ce --- /dev/null +++ b/raw/rel-18/29_series/29575/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c0f51266a2f883dd76139e43b1ac4e46680fb37bbe5f4ef76b59edab1259d90 +size 33118 diff --git a/raw/rel-18/29_series/29575/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/raw/rel-18/29_series/29575/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96ccd326a5cd91ec578cd1e77f957fb06f7f39cc --- /dev/null +++ b/raw/rel-18/29_series/29575/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:252116448f15af200457c6b8e3065ae0238f4fce9257fae25f99e9ae0f0b6656 +size 33836 diff --git a/raw/rel-18/29_series/29575/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29575/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..617093a0377a56838604b6ea8d6300206ada4c91 --- /dev/null +++ b/raw/rel-18/29_series/29575/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8a3de99f0dd233648991971f1827fb4d623a6c3a26cb76cb691537a38ed3815 +size 30428 diff --git a/raw/rel-18/29_series/29575/803776dff64331076ffc951fc95358ee_img.jpg b/raw/rel-18/29_series/29575/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b12add54594d94358bf33e4ec2c76e2deb0cb8c9 --- /dev/null +++ b/raw/rel-18/29_series/29575/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f65feaaa57733f723853376b99db5989c871821e760c6f913b18936170c43b41 +size 38435 diff --git a/raw/rel-18/29_series/29575/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/raw/rel-18/29_series/29575/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2949cce3e30be54ffeca9abb6df39d5886b70243 --- /dev/null +++ b/raw/rel-18/29_series/29575/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb67a12221de4c5057375963f0224b3fa51a679f3e93c222ab40986e24596f0c +size 31306 diff --git a/raw/rel-18/29_series/29575/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/raw/rel-18/29_series/29575/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d5b3fbab93a6a8908eab9938cf43d2a52d4474b --- /dev/null +++ b/raw/rel-18/29_series/29575/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faaee986559f0c5c0e6672855d5dc5cbb7f108a9a5b9a87512fb117b8299ebfc +size 12262 diff --git a/raw/rel-18/29_series/29575/90ddf538ef276510e2b631f7b96654e6_img.jpg b/raw/rel-18/29_series/29575/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..333877b628801a20d0b0c372cfb333bb18258f64 --- /dev/null +++ b/raw/rel-18/29_series/29575/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:140d802d90cd02a827a3a9671fd77d42847f67010bf500efddbb7db1872b1367 +size 37412 diff --git a/raw/rel-18/29_series/29575/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/29_series/29575/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4596501cf86aa426ced63289b227e76ebbbfffc1 --- /dev/null +++ b/raw/rel-18/29_series/29575/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af2578d684d8f874c6ee662a1461e1accd480109da6f0246edb8fd1e8ed65670 +size 32414 diff --git a/raw/rel-18/29_series/29575/bdfe4e1058d1a0e14bb838771b57254c_img.jpg b/raw/rel-18/29_series/29575/bdfe4e1058d1a0e14bb838771b57254c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7456431103bb70aeb3223c9e24d1499700c4237 --- /dev/null +++ b/raw/rel-18/29_series/29575/bdfe4e1058d1a0e14bb838771b57254c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:156e817aa0275d3d65396a391b5144570bff815968c1837602ab84b70889443a +size 14715 diff --git a/raw/rel-18/29_series/29575/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/raw/rel-18/29_series/29575/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7cf5678f8533d85b66ca44308916b5f74b31c1f --- /dev/null +++ b/raw/rel-18/29_series/29575/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63ff723c02630610189921e82a38b90aedcfbdea8f42fd94269498b3ac7ca7aa +size 16063 diff --git a/raw/rel-18/29_series/29575/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/raw/rel-18/29_series/29575/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5537b75d8ce7e97c584914548682bfb0c7b0cbc8 --- /dev/null +++ b/raw/rel-18/29_series/29575/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b990f91266e49797fa8301504d9e88c7854a9efaa98b3f78d9e8cf45ac887aec +size 36179 diff --git a/raw/rel-18/29_series/29575/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/raw/rel-18/29_series/29575/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01acf66ae04370effbaaf00bfa403f5bb26c4727 --- /dev/null +++ b/raw/rel-18/29_series/29575/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2afa8b0e7cebee5ea7e6c2b2faee7dd7ec5a71e754eb303f159bfa09ca26b0da +size 30184 diff --git a/raw/rel-18/29_series/29575/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/raw/rel-18/29_series/29575/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cbc080a9e2c14663d621d87248f5f6c9518dbde --- /dev/null +++ b/raw/rel-18/29_series/29575/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f5b00371ae6aea70239c81249d5bbbb6e2aaa98aa78501eb2270ed329c9285a +size 5792 diff --git a/raw/rel-18/29_series/29575/f6e8acf9f931452d01688d311b5c0364_img.jpg b/raw/rel-18/29_series/29575/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68d03786d0182c0257b8a43a1aedbe53f9dcb9ea --- /dev/null +++ b/raw/rel-18/29_series/29575/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f1610db75d13ff0d96a03946f533af5d6ef08c3d08ebb3bb0d8c3b1376ffeda +size 29915 diff --git a/raw/rel-18/29_series/29575/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/raw/rel-18/29_series/29575/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..379169c509dfa8cc66f2d2a3949a859f285df4a2 --- /dev/null +++ b/raw/rel-18/29_series/29575/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe969e790a9f5045ed46b33ea5725f8ab4825f8ac11763cc0d62bbda0f971ec3 +size 22581 diff --git a/raw/rel-18/29_series/29580/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/29_series/29580/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6119bc09ba4f23fbaa6cbfe466cd21f7a02110a --- /dev/null +++ b/raw/rel-18/29_series/29580/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c38c77ae8546f5d7802b1506652849c2ab06888110cc2f1a46f61ca2efbaa0c0 +size 34544 diff --git a/raw/rel-18/29_series/29580/2834bdd6eb8540277e609decbb924003_img.jpg b/raw/rel-18/29_series/29580/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bb097357b04017de3a8557b16ca04d8bf0d4cb1 --- /dev/null +++ b/raw/rel-18/29_series/29580/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc2c648509fe326371bc8c7ff4353287537efc8c0e50df8a381633a03cb13ba8 +size 30396 diff --git a/raw/rel-18/29_series/29580/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/raw/rel-18/29_series/29580/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99a3b2d50a383a23c6a7690f8cc0055941363204 --- /dev/null +++ b/raw/rel-18/29_series/29580/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e340a19cafde65276e6c89b8e7e3dfee7b18f7f4b4aa19c45a016e0775bb55c +size 30406 diff --git a/raw/rel-18/29_series/29580/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/raw/rel-18/29_series/29580/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be08f150747244ccb993132398007334062bee2d --- /dev/null +++ b/raw/rel-18/29_series/29580/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e356e9ebe691685d94b2d07f8915fbf85b08c16b1aee53b9ce9d56c00ea908b0 +size 34674 diff --git a/raw/rel-18/29_series/29580/43979979715bb3304389a0cb18f34444_img.jpg b/raw/rel-18/29_series/29580/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b8e56db23875a491f7e34ed0b15a93ea415779e --- /dev/null +++ b/raw/rel-18/29_series/29580/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:386859924efa8639f17c57ce417c98b7ccdb4cdc8344a522d9f7b836644b6f43 +size 25985 diff --git a/raw/rel-18/29_series/29580/5dfc130b129ace4df375839020a5700d_img.jpg b/raw/rel-18/29_series/29580/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..317697f8f7a8e1213ac217c29f0d2ee42120c059 --- /dev/null +++ b/raw/rel-18/29_series/29580/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab44e0ce4612c42ffa9dad1ac23540e197779ab75941aa1a0c184746a450a0cf +size 33017 diff --git a/raw/rel-18/29_series/29580/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/raw/rel-18/29_series/29580/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f92ac6d764ae272f857fd2e8d54931a9e80260a --- /dev/null +++ b/raw/rel-18/29_series/29580/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deabcdad2f8535b3e6673cd2c6e508cc2605812e598a17918e28967021322e5b +size 9663 diff --git a/raw/rel-18/29_series/29580/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29580/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11d251aa39ec6580c4be6a1169b291138a9840b8 --- /dev/null +++ b/raw/rel-18/29_series/29580/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c85891ebd6b48aadf1171f2f3e0077abed3c899a62e90ebb31b90c9cd24f505 +size 7764 diff --git a/raw/rel-18/29_series/29580/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29580/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be5235aabfde526a3feebfb7989afa264c65bd3a --- /dev/null +++ b/raw/rel-18/29_series/29580/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee3c809cfcd8344e70fd369978b4c10ff1072e9b290381a01ddab4b418b46440 +size 5629 diff --git a/raw/rel-18/29_series/29580/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/raw/rel-18/29_series/29580/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4253ac2d31df977e4558bde14df55bd2d928549 --- /dev/null +++ b/raw/rel-18/29_series/29580/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cac08b27a5e3cd3e4456752e55f38cf073684261ce588fb38c13c8800381ddab +size 31838 diff --git a/raw/rel-18/29_series/29580/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/29_series/29580/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e564d89d6ab7a258b17dbfcdaf832e0c45a11006 --- /dev/null +++ b/raw/rel-18/29_series/29580/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afb971fb59e8ebf7f41fc40c3d77f9eb1a8ac7548a56e9695c9bc190717098a3 +size 35591 diff --git a/raw/rel-18/29_series/29580/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/29_series/29580/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5557cf03847cbc47f5f413473cf6a0c4acb83802 --- /dev/null +++ b/raw/rel-18/29_series/29580/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3baaddc4d88acbe9506cacbbf6561757ef442fbddc51138083b5d4ed22f68919 +size 29823 diff --git a/raw/rel-18/29_series/29580/90ddb84c323b956e2d50a54d3f870566_img.jpg b/raw/rel-18/29_series/29580/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2afe0b6b4637511b1c80be1d8c8089a72605d23 --- /dev/null +++ b/raw/rel-18/29_series/29580/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be5d01cde3fd1c6da04a56224e5c289b7cacfd45be2534cdaf61bf57b5223c1e +size 30644 diff --git a/raw/rel-18/29_series/29580/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/raw/rel-18/29_series/29580/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba8f607bbf332083b688b4c5263cfb15291f288f --- /dev/null +++ b/raw/rel-18/29_series/29580/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac8c5bd225c4447dcd8508ef5bde69545917224b4b6d37a4dfb70e3a3393d032 +size 16557 diff --git a/raw/rel-18/29_series/29580/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/raw/rel-18/29_series/29580/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..014130a3c36b6746d6c7a7e5f7c08ba580d24082 --- /dev/null +++ b/raw/rel-18/29_series/29580/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e241f3cbd96694cfaf09c8b53615596481aa65a5dd0108cf52bb1c8a7515b12 +size 30751 diff --git a/raw/rel-18/29_series/29580/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/29_series/29580/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6950390b1c7ee6ba407b0973cabb545de54c9fe0 --- /dev/null +++ b/raw/rel-18/29_series/29580/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:135249cfa127911a677ec2f054832588ba6506d6b27911c098de97e807ef82c5 +size 39372 diff --git a/raw/rel-18/29_series/29580/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/raw/rel-18/29_series/29580/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e41efa5002bfc83726fd57d70df6aabe1d1ff42 --- /dev/null +++ b/raw/rel-18/29_series/29580/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:037ba193a0ca735acdaf14064499f004f041f1437033567ddb3f482f7827a2ce +size 11622 diff --git a/raw/rel-18/29_series/29580/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/raw/rel-18/29_series/29580/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71b3118d9bb2e803350da28370331610ee7cae23 --- /dev/null +++ b/raw/rel-18/29_series/29580/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b2e266f9ca9aa5a60f698da9fce94b22fd5926bd0f03c00962957cce0a739e5 +size 32457 diff --git a/raw/rel-18/29_series/29581/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/29_series/29581/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c316f1846667c18389fda81833ea75384d46006d --- /dev/null +++ b/raw/rel-18/29_series/29581/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab27307fee6ca8c0a01d002eade36f5848915f93dd9240855ebcaff3f4a820b7 +size 44451 diff --git a/raw/rel-18/29_series/29581/2e399449b7f62d40167a65ca88888917_img.jpg b/raw/rel-18/29_series/29581/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa0fbc66df04e9acd9613787fa93472006d45fbd --- /dev/null +++ b/raw/rel-18/29_series/29581/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b2d204f317806cdad88e0bb0e872cea90869e5ee8312b9f1d69482d045c25bc +size 37696 diff --git a/raw/rel-18/29_series/29581/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29581/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98d4504080908f92cdcb1728e54ad7c7d691d3a9 --- /dev/null +++ b/raw/rel-18/29_series/29581/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1949430c5cf08b02010ad57528b11bc81767ee5b5d3db90fd554d5612843160d +size 8175 diff --git a/raw/rel-18/29_series/29581/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29581/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..474088002f241fff2759ad877d40cef5e0d85323 --- /dev/null +++ b/raw/rel-18/29_series/29581/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/29_series/29581/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/raw/rel-18/29_series/29581/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ca299b5c4745c44d830d981dba8748c63a1c2e8 --- /dev/null +++ b/raw/rel-18/29_series/29581/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ca29c97fbc0b515409a106b6b60230b522a5ece1d67aaaa330265be3781ac9e +size 45545 diff --git a/raw/rel-18/29_series/29581/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/raw/rel-18/29_series/29581/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4f1fb171fdb472e1e40721b612194c990b5e79b --- /dev/null +++ b/raw/rel-18/29_series/29581/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a61064afc61fec6292f169ebdb8eb43c38ed4a3176a21aff2a8ecfaf73dbfa0 +size 45979 diff --git a/raw/rel-18/29_series/29581/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/raw/rel-18/29_series/29581/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5da8fcbeb0f9228bdbe56b8fdfac5f46bc959bcf --- /dev/null +++ b/raw/rel-18/29_series/29581/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ae360985ab0769e69d41cb2223d0d24c779c5afb0a0589079a31710bfb6f228 +size 38407 diff --git a/raw/rel-18/29_series/29581/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/29_series/29581/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c5a689ced393159e0e3f2544b5ac7374689df71 --- /dev/null +++ b/raw/rel-18/29_series/29581/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0089479eae36400d8636de4d16aad62d52e8b4951c8a577dab051e322fde8f95 +size 7044 diff --git a/raw/rel-18/29_series/29581/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/29_series/29581/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5037f7aabdef56a914d1ec56848bd5532e5b80f --- /dev/null +++ b/raw/rel-18/29_series/29581/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:594a9f2716f77513b1d8b894b729fb53aa45d103bed104c5ddc340509036ed1a +size 22157 diff --git a/raw/rel-18/29_series/29581/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/raw/rel-18/29_series/29581/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a0b680ec60cebfe3e6543ca18f410a675574e88 --- /dev/null +++ b/raw/rel-18/29_series/29581/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8968729c28ff1550b10113717f4da61570adbc54c63474ab034f9b0cace9218d +size 38100 diff --git a/raw/rel-18/29_series/29581/f6e8acf9f931452d01688d311b5c0364_img.jpg b/raw/rel-18/29_series/29581/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fec08a0a30038666107c5d041262c3ae79ea826 --- /dev/null +++ b/raw/rel-18/29_series/29581/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a92324229e6510f6e953ffffe00857b9d74f8bb2a0b7bf66c181bbc60951ab04 +size 42954 diff --git a/raw/rel-18/29_series/29581/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29581/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78882359f3b1356a1dd59c7815a5afb122d3af25 --- /dev/null +++ b/raw/rel-18/29_series/29581/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4b4fc06e4392b4c7d2ef488a0478c544c53bedd916b9dc0c5aa2e60adbc8bce +size 38533 diff --git a/raw/rel-18/29_series/29594/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/29_series/29594/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..097c46e2293be14dc1fc026939b7053ea0fae90f --- /dev/null +++ b/raw/rel-18/29_series/29594/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f676b67a5a4cbe94f842ba40e0586a6ce179d696e5ea612765f27776384d6e1 +size 19731 diff --git a/raw/rel-18/29_series/29594/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/raw/rel-18/29_series/29594/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..436a83205c70af59fd6f11a97ec8f463de663b27 --- /dev/null +++ b/raw/rel-18/29_series/29594/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f585695c19aa02af207b3a80f2aea40327df7f630133059e9674f72d638453b +size 11155 diff --git a/raw/rel-18/29_series/29594/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/raw/rel-18/29_series/29594/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7486488739df09c07aeb54d3b2a3a114e6fae6dd --- /dev/null +++ b/raw/rel-18/29_series/29594/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5350bca1eb5d0cf8e4a3ab82095c6edb30b7c4afc9f26f222029a81b0ad0b0b +size 16528 diff --git a/raw/rel-18/29_series/29594/43837b056625d3d6ce615e4c02f163bb_img.jpg b/raw/rel-18/29_series/29594/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6492d10ce1bd25697f51ced60ce84b092c12df96 --- /dev/null +++ b/raw/rel-18/29_series/29594/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71ed6f8982441eaeb332b4f4851838b37dd7e5d185a15136426d0c6b8baa080f +size 19815 diff --git a/raw/rel-18/29_series/29594/5a24ac755b962fd5f0183f13de0726de_img.jpg b/raw/rel-18/29_series/29594/5a24ac755b962fd5f0183f13de0726de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3866de976315cf51c43dc6ab6171b92edc076a8d --- /dev/null +++ b/raw/rel-18/29_series/29594/5a24ac755b962fd5f0183f13de0726de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad2e97e3226d34134332b43e100ea9d375b99225da9cc85ebaf62a278eb06bd4 +size 6669 diff --git a/raw/rel-18/29_series/29594/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29594/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de --- /dev/null +++ b/raw/rel-18/29_series/29594/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7 +size 9370 diff --git a/raw/rel-18/29_series/29594/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29594/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfa0d229082ecb7f2e23102ee7673d2a2cf03c76 --- /dev/null +++ b/raw/rel-18/29_series/29594/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb776af0de14b4c8128e6942a0e4c9865e7e854af32e2934cb82ad5032d68eb +size 5342 diff --git a/raw/rel-18/29_series/29594/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/raw/rel-18/29_series/29594/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a408500b95e9d128a25f01a34522b9e35a5fad98 --- /dev/null +++ b/raw/rel-18/29_series/29594/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2de4b5d331c9e233efc1077e49c940235b7f61586620607e4f60daf0a3fe63d8 +size 18172 diff --git a/raw/rel-18/29_series/29594/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/29_series/29594/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eff830b09e771a98e966861240251c39806eaafd --- /dev/null +++ b/raw/rel-18/29_series/29594/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7f363b0bab0bc2829b900b2113be8b44dd6d811bcfc30952c2bc6f51a34d5a9 +size 21444 diff --git a/raw/rel-18/29_series/29594/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/29_series/29594/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e3a5ddc076086d5ec9e117f176b10069e434311 --- /dev/null +++ b/raw/rel-18/29_series/29594/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e113b769b43a66ee66a56c4c39b62d38c9f4d4230b608e8836fef9fb9ae4a541 +size 19901 diff --git a/raw/rel-18/29_series/29673/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/raw/rel-18/29_series/29673/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c0bc9d7aa8b4f304a7bbb515e430f0b293146ed --- /dev/null +++ b/raw/rel-18/29_series/29673/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:018c230f585a2486cc2b86ba46a6c005cb681aaa1235fb197e2bc1ff6d1f4bcf +size 28279 diff --git a/raw/rel-18/29_series/29673/06da11ab76cacc38bbcd714e437797ea_img.jpg b/raw/rel-18/29_series/29673/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..094b46666f4ba23956455f4cb5b4cafb26de7335 --- /dev/null +++ b/raw/rel-18/29_series/29673/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ace0302e96b1f711f742fea6bdb702bf3ba3f4fb0d60f1df3dab5eebadca27b +size 19307 diff --git a/raw/rel-18/29_series/29673/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/raw/rel-18/29_series/29673/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae80698d9899b2866cd5e8dd5bb70406837b55f7 --- /dev/null +++ b/raw/rel-18/29_series/29673/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f009e46f9510d4d89edf35e1e95af5e8be5265207c3088db531a491935582c6 +size 28116 diff --git a/raw/rel-18/29_series/29673/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29673/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e37c752b9bdcb17bab4861e111a0cf12e2dec14c --- /dev/null +++ b/raw/rel-18/29_series/29673/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e508fdd99fdb03fc63f3620e2677581febecd2f8aca8f28dbd14f968a78f0f4 +size 9856 diff --git a/raw/rel-18/29_series/29673/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29673/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be7b2da67f1bb1db5a7e57a6b3e8af368ce5bf8f --- /dev/null +++ b/raw/rel-18/29_series/29673/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0ddf27f1abe435349f8edaea52ad73f481edcab604826e2f8fc112d38509e59 +size 5700 diff --git a/raw/rel-18/29_series/29673/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/raw/rel-18/29_series/29673/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54b4bd767f2011b96797cf7dc0ba24dc6c401ac4 --- /dev/null +++ b/raw/rel-18/29_series/29673/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b232facf0e9e3fa0f514c4765e13c7e7f89cc5e149283286e69e8870c6191c16 +size 30038 diff --git a/raw/rel-18/29_series/29673/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/raw/rel-18/29_series/29673/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..886ab3a2a2baaa06898c5e560d4f8031e1603f8e --- /dev/null +++ b/raw/rel-18/29_series/29673/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbe3f150e73514736d9ad9af506bd52822a7a6897b9bfa942e2e33c1a595e3fd +size 29061 diff --git a/raw/rel-18/29_series/29673/8e14350b4b669119a3bdfca7869110ca_img.jpg b/raw/rel-18/29_series/29673/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cfe77c3a600e2b21b44d6107879689809f6dd86 --- /dev/null +++ b/raw/rel-18/29_series/29673/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19620901ef684ef75f8e09e66866a34b980a2d706bf50f77ff0ec8bc68453353 +size 31536 diff --git a/raw/rel-18/29_series/29673/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/raw/rel-18/29_series/29673/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cad293afe88817203824c7a34117e0e7d5521fe --- /dev/null +++ b/raw/rel-18/29_series/29673/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61aea00bcd0caaddc1d758b5ed2b191a023262db9707bab55575c8f7611672e6 +size 29651 diff --git a/raw/rel-18/29_series/29673/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/raw/rel-18/29_series/29673/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6a74a7b7b56bf8d08839096ad15822f1694cf5b --- /dev/null +++ b/raw/rel-18/29_series/29673/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a4da4c84b6157d29918da92a94245078647c2f4c32255fabc09327e5abdf3ae +size 37553 diff --git a/raw/rel-18/29_series/29675/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/raw/rel-18/29_series/29675/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9718096e5fada1823f2af61c2fdcdb56a55be54 --- /dev/null +++ b/raw/rel-18/29_series/29675/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b0c618b62f5a6f3d9b992f8126e0e4df63e1c2644e247fda638fb50d61a0ee1 +size 15144 diff --git a/raw/rel-18/29_series/29675/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/raw/rel-18/29_series/29675/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0183a7821a745d9c0084a82d871d5178c7575479 --- /dev/null +++ b/raw/rel-18/29_series/29675/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c55ee68142d81a4a5bd3347293d2928d70757f338b29f850cde75a271e43753e +size 32896 diff --git a/raw/rel-18/29_series/29675/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/raw/rel-18/29_series/29675/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..178f5b04a128037b2f9a5eb8f805d433afb12e03 --- /dev/null +++ b/raw/rel-18/29_series/29675/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74b580cdb15198fa1a8f4b7955bd2b7bfa47e0811b8b5fbc55b853d12d70d8c8 +size 11933 diff --git a/raw/rel-18/29_series/29675/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29675/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de --- /dev/null +++ b/raw/rel-18/29_series/29675/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7 +size 9370 diff --git a/raw/rel-18/29_series/29675/63e0c22852c26699d0bd095a2d796bab_img.jpg b/raw/rel-18/29_series/29675/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..054f5146ce8f97eb4313e504c41eb23fcf85b862 --- /dev/null +++ b/raw/rel-18/29_series/29675/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:729b6d44ff0f87e8f8012f691a2ce2187b1e183fa4ff0601825b22888f9a8385 +size 31973 diff --git a/raw/rel-18/29_series/29675/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29675/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ffa2cdd380f6b40c6e6cf14b748ebd595878994 --- /dev/null +++ b/raw/rel-18/29_series/29675/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9a9bd52e70e450b8eca170f2e60fd3e87a7a06407b8d7d2a845dd2c84606e40 +size 5698 diff --git a/raw/rel-18/29_series/29675/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/raw/rel-18/29_series/29675/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d1c0ced8ad26b54d7f62777fbe06ed93430b1e --- /dev/null +++ b/raw/rel-18/29_series/29675/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca24a550e7badbec8a6341e1cf150e6d945fd9dd474b073c2c862a9d5a7a7fe5 +size 15409 diff --git a/raw/rel-18/29_series/29675/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/raw/rel-18/29_series/29675/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af1825a524e378230590734ffc8b192b184e3bd1 --- /dev/null +++ b/raw/rel-18/29_series/29675/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0f3c85b14f2fd9168b6cd2bfb6e303f0a67c8d285decdef72f3fa3c3fed0060 +size 31391 diff --git a/raw/rel-18/29_series/29893/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/29_series/29893/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4041011dc3aaee06e0bf15f451da0fcce3513a18 --- /dev/null +++ b/raw/rel-18/29_series/29893/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17ed572d6ad236ecc10a405af97fc4703ae6ea001f175f15ce1978f5265cfb7f +size 72533 diff --git a/raw/rel-18/29_series/29893/303fadfb9def251d1575d6221199b158_img.jpg b/raw/rel-18/29_series/29893/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72d7794def2bab403e66ed8211b310fd6e6cdcda --- /dev/null +++ b/raw/rel-18/29_series/29893/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:979c23757af02e6a3ce451ca2dd63af956db859a52f971349d5646758ec129ef +size 47724 diff --git a/raw/rel-18/29_series/29893/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/29_series/29893/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4014a5cdbdcb1a501f9c882df47fc210a6ec7e9 --- /dev/null +++ b/raw/rel-18/29_series/29893/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e44f709706416ddcce9cd33bdb1583b7ce1695428cffd5b1bc27646997d5083 +size 9442 diff --git a/raw/rel-18/29_series/29893/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/29_series/29893/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8100a15c900e98697870ba4c1afddbe7c9b3ee68 --- /dev/null +++ b/raw/rel-18/29_series/29893/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb40bc9f76c66728d07c34b52e7e2c983ae7e9e2ffb632d60220ebfd237c17a3 +size 5694 diff --git a/raw/rel-18/29_series/29893/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/raw/rel-18/29_series/29893/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bdf927f0689b1c7f587a64b430fe9408ea6524d --- /dev/null +++ b/raw/rel-18/29_series/29893/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:483a5943e516cd2235ca1d4ce6c958b6da001e1b0f5d1a6b63b5c4134cab3258 +size 75661 diff --git a/raw/rel-18/29_series/29893/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/29_series/29893/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02f9bfca276ebe98070ff1a6c010f21109cd81c1 --- /dev/null +++ b/raw/rel-18/29_series/29893/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:081b0cb91814d2c041e4e2cf4d9254d2e0c4e6e75407388f12daf9f2c1c7f9d5 +size 103427 diff --git a/raw/rel-18/29_series/29893/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/29_series/29893/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca7e247cb3226befb0ddffae3357d4ff7d575037 --- /dev/null +++ b/raw/rel-18/29_series/29893/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bfbbcedbfcd81289969f9d2bec0414d289847672e9187b56dfe28b25a6edf35 +size 59078